0.86: New Lovelace UI and Zigbee Management Panel!


#1

Today we’re releasing Home Assistant 0.86. And oh wow, this is an amazing release. First awesome thing: the Lovelace user interface, which we’ve been working on for the last 8 months, is now the default in Home Assistant. We have a lot to talk about, so we created a separate blog post just for the Lovelace release here.

Next up, we’ve updated the Home Assistant demo. It’s snappier, it’s snazzier, 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 automatically updated with the latest release of Home Assistant, so it will always feature the latest things.

Screenshot of Lovelace in the new demo.

Zigbee management panel

This release includes a brand new Zigbee management panel to manage your Zigbee network thanks to the hard work by @dmulcahey with the help of @Adminiuga and @damarco. The new panel makes it easy to:

  • Issue Permit and Remove operations
  • Reconfigure Node, which will rebind and reconfigure the reporting for a device. Which can help solve issues.
  • Reading and setting cluster attributes. This is useful for viewing and setting things such as device sensitivity levels.
  • View and issue cluster commands. Note on this feature: support for commands with arguments is coming soon.

The Zigbee team is also planning a bunch of cool things for 2019. Direct device binding (directly pairing remotes to lights) is already in development and they are planning support for group management as well. Targeted and broadcast joins are also right around the corner (we’re waiting for a new Zigpy release). Exciting times for Zigbee users!

Screenshot of the Zigbee management panel.

Noteworthy breaking changes

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 started/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 Platforms

If you need help…

…don’t hesitate to use our very active forums or join us for a little chat. The release notes have comments enabled but it’s preferred if you use the former communication channels. Thanks.

Reporting Issues

Experiencing issues introduced by this release? Please report them in our issue tracker. Make sure to fill in all fields of the issue template.

Breaking Changes

  • Automation: Split time_pattern triggers from time trigger (@armills - #19825) (automation.interval docs) (automation.time docs) (breaking change)
  • Each instance of Home Assistant will now generate it’s own unique webhook url for Geofencyto use. One will need to be generated and provided to the iOS app to replace the existing url: https://myhome.duckdns.org/api/geofency?api_password=HA_PASSWORD (@rohankapoorcom - #18951) (geofency docs) (breaking change)
  • Nest sensor: Correctly map hvac_state to Home Assistant states. Heating -> heat, Cooling -> cool. (@mitchellrj - #19895) (sensor.nest docs) (breaking change)
  • Add nad telnet media player and merge nadtcp into media_player.nad (@rymsha - #19704) (media_player.nad docs) (breaking change)
  • Prezzi Benzina: Added the service type to the name of the sensor to better differentiate between different service tiers. (@eliseomartelli - #19980) (sensor.prezzibenzina docs) (breaking change)
  • PostNL attributes are updated, contain now more information (@basbl - #18334) (sensor.postnl docs) (breaking change)
  • Support for multiple Fibaro gateways. A list of gateways is expected instead of a single config. (@pbalogh77 - #19705) (fibaro docs) (binary_sensor.fibaro docs) (cover.fibaro docs) (light.fibaro docs) (scene.fibaro docs) (sensor.fibaro docs) (switch.fibaro docs) (breaking change)
  • Upgrade greeneye_monitor to 1.0. It now requires the full 8 digit serial number. (@jkeljo - #19631) (greeneye_monitor docs) (breaking change)
  • Previous “manual” registration of roku devices will need to be updated or removed (discovery should discover all rokus on your network). (@soberstadt - #17548) (roku docs) (media_player.roku docs) (remote.roku docs) (breaking change) (new-platform)
  • Alarm control panel entities will now use number as their code_format instead of Number (@balloob - #20077) (alarm_control_panel docs) (breaking change)
  • OpenUV: users will now need to use the openuv.update_data service to request new data from the API. (@bachya - #19949) (openuv docs) (breaking change)
  • Add support for connecting to multiple zoneminder instances (@rohankapoorcom - #19955) (zoneminder docs) (camera.zoneminder docs) (sensor.zoneminder docs) (switch.zoneminder docs) (breaking change)
  • The gpslogger device_tracker platform no longer takes any configuration. The configuration needs to be applied to the component gpslogger instead. The platform will be automatically loaded with the component and should not be specified in configuration.yaml. Each instance of Home Assistant will now generate it’s own unique webhook for GPSLogger to use. One will need to be generated and provided to the mobile app to the replace the existing url: https://myhome.duckdns.org/api/gpslogger?api_password=HA_PASSWORD. Home Assistant only supports using POST (no longer GET) for GPSLogger. The long lived access token is also no longer needed. (@rohankapoorcom - #20044 - #20079) (device_tracker docs) (gpslogger docs) (breaking change)
  • The locative device_tracker platform no longer takes any configuration. The configuration needs to be applied to the component locative instead. The platform will be automatically loaded with the component and should not be specified in configuration.yaml. Each instance of Home Assistant will now generate it’s own unique webhook url for Locative to use. One will need to be generated and provided to the mobile app to replace the existing url: https://myhome.duckdns.org/api/locative?api_password=HA_PASSWORD. Home Assistant only supports using POST (no longer GET) for Locative. (@rohankapoorcom - #19964 - #20043) (device_tracker docs) (locative docs) (breaking change)
  • Sensibo to adhere to the operation mode states in HA climate component. (@balloob - #20180) (climate.sensibo docs) (breaking change) (beta fix)
  • Any registered entity that started/ended with an underscore (will be removed) or had 2 subsequent underscores (1 will be removed) will be updated. (@balloob - #20328) (breaking change) (beta fix)
  • The SMA sensor can monitor several new sensors. Unfortunately some of the existing sensors were renamed: current_power is now grid_power and grid_voltage is now voltage_l1 (the voltage from all three phases are available). The sensors also support the entity registry, making editing their names a breeze from the frontend. (@kellerza - #19753) (sensor.sma docs)

Beta Fixes

All changes


This is a companion discussion topic for the original entry at https://www.home-assistant.io/blog/2019/01/23/release-86/

Another component for ZiGate
Roku devices not being discovered after 0.86
#2

Great work guys


#3

Good work, people.

It would have been nice though if the reported Lovelace UI bugs would have been fixed beforehand.


#4

update the platform from name to time_pattern .

Should this be from time?


#5

A huge release, thanks to everyone involved in this !

Can someone explain me what’s the difference between using zigbee2mqtt and the inner component explain in the article ? Or point at me some documentation ?


#6

I’m wondering this as well.


#7

Awesome work to everyone involved the lovelace demo’s look great will wait to see any fallout from the community before upgrading to this release.


#8

I believe the blog post refers to the native zigbee component. Configuring zogbee2mqtt entities is via the MQTT configuration, I think.


#9

FIXED: I got the new time_pattern bit backwards and updated the wrong items. LOL!!! :rofl::joy:

Just updated. Went through the breaking changes and fixed up everything, but now I have a bunch of components that fail to load and a bunch of yellow boxes around my UI. I get this in the persistant notification area:

Annotation%202019-01-24%20090538

and this in the error log. It’s not very helpful, and I’m not exactly sure where to start.

2019-01-24 08:58:16 ERROR (MainThread) [homeassistant.setup] Setup failed for group: Invalid config.
2019-01-24 08:58:16 ERROR (MainThread) [homeassistant.setup] Unable to set up dependencies of remote. Setup failed for dependencies: group
2019-01-24 08:58:16 ERROR (MainThread) [homeassistant.setup] Setup failed for remote: Could not set up all dependencies.
2019-01-24 08:58:16 ERROR (MainThread) [homeassistant.setup] Unable to set up dependencies of script. Setup failed for dependencies: group
2019-01-24 08:58:16 ERROR (MainThread) [homeassistant.setup] Setup failed for script: Could not set up all dependencies.
2019-01-24 08:58:16 ERROR (MainThread) [homeassistant.setup] Unable to set up dependencies of switch. Setup failed for dependencies: group
2019-01-24 08:58:16 ERROR (MainThread) [homeassistant.setup] Setup failed for switch: Could not set up all dependencies.
2019-01-24 08:58:16 ERROR (MainThread) [homeassistant.setup] Unable to set up dependencies of automation. Setup failed for dependencies: group
2019-01-24 08:58:16 ERROR (MainThread) [homeassistant.setup] Setup failed for automation: Could not set up all dependencies.
2019-01-24 08:58:16 ERROR (MainThread) [homeassistant.setup] Unable to set up dependencies of device_tracker. Setup failed for dependencies: group
2019-01-24 08:58:16 ERROR (MainThread) [homeassistant.setup] Setup failed for device_tracker: Could not set up all dependencies.
2019-01-24 08:58:36 ERROR (MainThread) [homeassistant.setup] Unable to set up dependencies of light. Setup failed for dependencies: group
2019-01-24 08:58:36 ERROR (MainThread) [homeassistant.setup] Setup failed for light: Could not set up all dependencies.
2019-01-24 08:58:37 ERROR (MainThread) [homeassistant.setup] Unable to set up dependencies of ios. Setup failed for dependencies: device_tracker
2019-01-24 08:58:37 ERROR (MainThread) [homeassistant.setup] Setup failed for ios: Could not set up all dependencies.

#10

I was wondering the same thing, I assume it was a typo?!


#11

where were they reported?
on the github page?


#12

Try another restart


#13

I’ve got the same problem, many components have not loaded including iOS, light, group etc.


#14

Restart doesn’t help.


#15

Make sure you don’t have customize entry with invalid slugs


#16

Fixed it. Updated the time_pattern to the wrong automations. :rofl:

@robertpe Make sure you’ve updated everything properly. I had to update my automation time triggers that used a pattern (example minutes: '/10') rather than a specific time. Once I fixed that, everything worked.


#17

I missed a few and HA just refused to load, so if he is getting HA to load, I don’t think it’s a slug issue, though if it is, you can look in the log before restarting again and see where it’s getting stuck. That’s where I found the one I missed.


#18

Hi,

the docker container with LATEST tag has still 0.85

https://hub.docker.com/r/homeassistant/home-assistant/tags

Can you please ugrade it?

Thank you!


#19

Any samples? Could help finding.


#20

You mean like sensor.disk_use_percent_ became sensor.disk_use_percent?