diff --git a/source/_posts/2019-01-23-lovelace-released.markdown b/source/_posts/2019-01-23-lovelace-released.markdown
index 4cac5aa2c8a..0d52b11ff62 100644
--- a/source/_posts/2019-01-23-lovelace-released.markdown
+++ b/source/_posts/2019-01-23-lovelace-released.markdown
@@ -11,25 +11,60 @@ categories: Release-Notes
og_image: /images/blog/2019-01-release-86/components.png
---
-Lovelace is the default, yay!
+Today we're happy to announce that our new Lovelace UI, which has been in beta for the last 8 months, is becoming the new default interface of Home Assistant. With Lovelace we're taking a new approach to building user interfaces for Home Assistant. We're no longer storing the look and feel of your UI in your configuration.yaml, requiring restarts for changes. With Lovelace we're keeping the UI concerns in the UI1, unlocking a whole new set of features:
-Started originally inspired by @andrey-git who added Custom UI. [Initial PR](https://github.com/home-assistant/home-assistant-polymer/pull/1205)
+ - A configuration UI to manage your Lovelace UI including live preview when editing cards.
+ - Full support for custom cards.
+ - Fast. Using a static config allows us to build up the UI once.
+ - Customizable. Each card has many options to configure how it shows it's data. Change themes on a per card basis or override the name or icon of an entity.
-Learned that homes are who people are, thinking that we could magically sort it out and build a UI was a naive approach. To work around the magic, components started to store options to influence the magic.
+In case you're reading this and want to give it a try right now: we've updated [the Home Assistant demo](https://demo.home-assistant.io). It now features multiple Lovelace configuration examples. The demo is fully interactive, including the configuration UI (accessible via the menu in the top right).
-Lovelace is a re-do, we allow users to get full control. Every card, every entity, all yours. Including custom cards.
+TODO - rephrase: Interview with Zac about the Lovelace release on the Home Assistant Podcast: https://hasspodcast.io/ha042 .
-Thank a ton to the current and former members of the Lovelace team:
+1: If you prefer YAML, Lovelace also includes a [YAML mode](/lovelace/yaml-mode/).
- - @bramkragten
- - @c727
- - @ciotlosm
- - @iantrich
- - @jeradM
- - @thomasloven
- - @zsarnett
+## {% linkable_title History %}
-Because of the ease to customize and share customizations, we've seen a big community be created around Lovelace. They are very active in the #lovelace channel on our chat, and work is shared on [ShareTheLove.io](https://sharethelove.io/) and the [Lovelace section on Awesome HA](https://www.awesome-ha.com/#lovelace-ui).
+With Lovelace we've build a foundation that improves things bigly today, but will also allow us add many new exciting features in the future. The main difference with the old UI is that we no longer store any UI concerns in the state machine.
+When Home Assistant was started, I came up with an algorithm that would automatically organize the available entities in badges, cards and tabs and show that on the screen. Users demanded more influence so over time, we've added a bunch of components and features who'se main or sole purpose is to influence how the algorithm shows and organizes the UI.
-Interview with Zac about the Lovelace release on the Home Assistant Podcast: https://hasspodcast.io/ha042 .
+As this kept growing, I realized that we made a mistake: the backend shouldn't be aware of anything in the frontend. It should just deliver the entities and the frontend should figure it out together with the user.
+
+At the same time as this was happening, we've also had some discussions in the frontend. Users wanted more control on what is shown, when it's shown and how it's shown. Eventually, [@andrey-git] came up with Custom UI for the old interface. This allowed users to do whatever we want.
+
+Lovelace was built [from the start](https://github.com/home-assistant/architecture/issues/14) to tackle these problems. The inital version completely dropped the algorithm and required users to add each card to their configuration. We went from full automatic UI to nothing. We launched it under the nomer "experimental UI" and it quickly gained traction. People loved the control and the ability to inject custom cards or entity rows at will.
+
+The enthusiasm was great among our power users, however by going to no automatic UI, we were no longer beginner friendly. A new user would open Home Assistant and it would see a blank, unconfigured UI. This had to be solved or else we would not be able to retain any new users.
+
+To make the Lovelace UI beginner friendly again, we actually re-introduced our automatic algorithm. However, this time the algorithm will generate a Lovelace configuration. However, this time, if the user no longer agrees with the algorithm, they can take control. By taking control, we'll copy the automatically generated configuration and store it for the user. Now the user is in control and can make any change that it wants.
+
+To make configuration as easy as possible, Lovelace UI allows (custom) cards to include a config editor. This way the user will be able to quickly edit a card while a live preview shows how the changes look. If a card does not include an editor, the user will be presented with a YAML editor in the browser.
+
+Because of the ease to customize and share customizations, we've already seen a big community be created around Lovelace. They are very active in the #lovelace channel on [our chat](/join-chat/), and work is shared on [ShareTheLove.io](https://sharethelove.io/) and the [Lovelace section on Awesome HA](https://www.awesome-ha.com/#lovelace-ui).
+
+## {% linkable_title Credits %}
+
+Lovelace UI has been 8 months in the making and it has been a big undertaking. We've worked hard and are proud of being able to ship this first version. Lovelace UI would not have been possible without the following current and former members of the Lovelace team:
+
+ - [@balloob] / Paulus Schoutsen
+ - [@bramkragten] / Bram Kragten
+ - [@c727]
+ - [@ciotlosm]
+ - [@iantrich]
+ - [@jeradM]
+ - [@thomasloven]
+ - [@zsarnett]
+
+I also want to thank the community for adopting this so eagerly, building a ton of helpful tooling and examples and helping one another to create beautiful UIs for their homes.
+
+[@andrey-git]: https://github.com/andrey-git
+[@balloob]: https://github.com/balloob
+[@bramkragten]: https://github.com/bramkragten
+[@c727]: https://github.com/c727
+[@ciotlosm]: https://github.com/ciotlosm
+[@iantrich]: https://github.com/iantrich
+[@jeradM]: https://github.com/jeradM
+[@thomasloven]: https://github.com/thomasloven
+[@zsarnett]: https://github.com/zsarnett
diff --git a/source/_posts/2019-01-23-release-86.markdown b/source/_posts/2019-01-23-release-86.markdown
index df97f746626..3f0a039f7e2 100644
--- a/source/_posts/2019-01-23-release-86.markdown
+++ b/source/_posts/2019-01-23-release-86.markdown
@@ -1,7 +1,7 @@
---
layout: post
-title: "0.86: New Lovelace UI! - TBD UPDATE DATE"
-description: "Lovelace is in, Zigbee Control Panel is in."
+title: "0.86: New Lovelace UI and Zigbee Management Panel! - TBD UPDATE DATE"
+description: "Lovelace is in, Zigbee Control Panel is in. New demo is in."
date: 2019-01-16 00:01:00
date_formatted: "January 23, 2019"
author: Paulus Schoutsen
@@ -11,9 +11,23 @@ categories: Release-Notes
og_image: /images/blog/2019-01-release-86/components.png
---
-Lovelace is the default! Such a great achievement that it warranted it's own [blog post](#).
+Today we're releasing Home Assistant 0.86. And oh boy, this is an amazing release. First awesome thing: Lovelace is now the default. We have a lot to talk about, so we created a separate blog post just for the Lovelace release [here](/2019/01/16/lovelace-released/).
+
+Next up, we've updated the [Home Assistant demo](https://demo.home-assistant.io). It's snappier, it's sazzier, and best of all: it contains four fully functional Lovelace user interfaces that you can play with: change the states or go in config mode and add, edit or re-organize the cards. We've set it up in such a way now that the demo will be build on every release of the frontend. Right now the demo only includes Lovelace, but we'll add support for the other panels in the future.
+
+Talking about panels in the frontend. This release includes a brand new Zigbee Management panel to manage your Zigbee network thanks to the hard work by [@dmulcahey] and [@Adminiuga]. XXX-PLACEHOLDER-XXX.
+
+
+ 
+ Screenshot of the Zigbee management panel.
+
+
+This release also includes two noteworthy breaking changes. One is a follow-up on the slugify breaking change from last release. We did not update the validation check for config options that need to be valid slugs. This means that some of your config values might be invalid. Keep an eye at the console as we have a new message to tell you which ones are wrong.
+
+This issue also impacts the entity registry, which could contain in some rare cases invalid entity IDs. Expect entity IDs to change if they contained a double underscore (which becomes 1) or if they ended in an underscore (which will be removed).
+
+Another noteworthy breaking change (sorry!), is that the automation `time` trigger has been split into two: `time` and `time_pattern`. If you had a time trigger containing the keys `hours`, `minutes` or `seconds`, update the platform from `name` to `time_pattern`.
-New Zigbee control panel.
## {% linkable_title New Platforms %}