0.79: Device Registry, Logi Circle, Huawei LTE routers, GeoJSON


#1

In case you missed it two weeks ago, check our plans for the future.

It’s time for another great release and we’re introducing a brand new feature: device registry. This allows integrations to tell Home Assistant not only about entities, but also which devices the entities represent. It also allows integrations to tell Home Assistant how a device is connected to Home Assistant. For example, a Hue light bulb is connected to Home Assistant via the Hue hub.

Screenshot showing several configured integrations in the configuration panel.

Adding devices to the mix allows us to do a lot of cool things. It allows us to group entities and show how they relate to one another. It will also allow us to inform the user if data leaves the home network and shows the firmware version that the device is running on.

Screenshot showing the devices of the iOS integration.

Devices can only be added by integrations that are configured via the integrations panel in the config panel. So we’ve also been expanding the integrations that support that. This release brings support to iOS, MQTT and Tradfri.

Screenshot showing how to configure MQTT via UI

And this is not all! There is so much more. In an effort to make the quality of an integration more clear, we’ve added an Integration Quality Scale. With this scale we’ll be able to clearly communicate to the user how good an integration is and it gives developers a list on how to improve it. Expect these levels to pop up in the integration list soon.

And did you think we forgot about auth? We did not. @awarecan has added a new multi-factor auth module that will send you a one-time authentication code to finish your login, with a notification service of your choice. PushBullet, Hangouts, iOS app, some obscure custom notification service using a shell script? It’s possible.

Oh, and yes, there is also some cool new integrations. Support has been added for Logi Circle camera’s, GeoJSON events and even a bank. More below 👇

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

  • Netdata configuration change: Allows multiple elements per group. Specify the data_group as part of the sensor description. See docs for details. (@reefab - #16656) (sensor.netdata docs) (breaking change)
  • The Dyson sensor Air Quality Index is now named AQI following Dyson’s mobile app (@glpatcern - #14550) (sensor.dyson docs) (breaking change)

Beta Fixes

All changes


This is a companion discussion topic for the original entry at https://www.home-assistant.io/blog/2018/09/28/release-79/

#2

Met.no is also a new weather component in this release. Uses the same data as the yr.no sensor.


#3

…and there IKEA tradfri breaks, yet again … its alredy configured, why does it always insist on discovery after updates?

…works after removing tradfri config and configure in gui, but really…should be listed under breaking changes.


#4

Great work with the integration part. I really like it, as a long time user, I believe that this is a move in the right direction; making Home Assistant easy to configure. Keep the good work!


#5

Are these new integration features also available if configured from the config file? (Is this even possible? Still searching for how to auto add the chromecast integration Edit: seems to be fixed in a later release thx @balloob for letting me try again )


#6

Just add cast: to your config file


#7

Looks like it’s not possible to use met.no as a Weather Forecast Card in Lovelace.
When i try following error message is display in the UI:

No state available for weather.met
{
“type”: “weather-forecast”
“entity”: “weather.met”
}

Works great in the standard UI.


#8

What new does met.no offer? Is there any reason to use it over yr? Unable to test it myself atm.


#9

I think it is because there are no forecast data:

But anyway it is great progress and I’m looking forward for next update :wink:


#10

How does Mqtt: Configuration.yaml work?

Al it says is: This integration has no devices.


#11

I moved over to hass.io back on .75 and had a issue with auto discovery of my G-Homes causing the front page not to load.

I could only resolve this by adding cast devices manually.

While on .78 I had the issue where my G-Homes and minis would appear unavailable. Removing the manual config and allowing auto discovery resolved this issue.

I updated to .79 and again the front page wouldn’t load. Adding cast manually, again resolved the issue.

This means I’m unable to see my groups which are found via discovery :frowning:


#12

In the integration panel, i have OpenUV, and all the entities for it. Then it givs a list of “entities without devices…”, but seems pretty useless. What’s the point of this?


#13

There is currently no forecast data, but I am working on it: https://github.com/home-assistant/home-assistant/compare/met_weather?expand=1


#14

A weather component has a different view in the frontend


#15

0.79 reverted the change made in 0.78 regarding chromecast discovery logic. Only fixed one issue related with cast manually configuration. Some user reported that under 0.77/0.79 logic, your system startup might be blocked for 5 minutes, but eventually it will give up and resume the startup.


#16

am I the only one who has problems with zoneminder after upgrading to 0.79? I get " Connection error logging into ZoneMinder".
I see that some changes have been made to the ZoneMinder component, are any changes to the configuration required?


#17

Sorry, are you saying discovery will work?
And would this 5mins delay happen every time I restart?


#18

Is anyone else having problems starting after upgrading? Seems the startup is hung on “Collecting restrictedpython==4.0b5”. A manual install results in the same thing.

Tried yesterday and again this morning in case it was a server issue. Thoughts?

Edit: the fix was to dump the ~/.cache folder. Something must have gotten corrupt.


#19

I am as well. I reverted back to 78.0 and it is working again.


#20

My working Zoneminder setup broke when I updated to 0.79.

Clarification: My ZM server (running ZM 1.32.0) is still working fine, i just get login errors from Home Assistant.

2018-09-29 14:20:02 ERROR (SyncWorker_6) [zoneminder.zm] Connection error logging into ZoneMinder

2018-09-29 14:20:02 ERROR (MainThread) [homeassistant.setup] Setup failed for zoneminder: Component failed to initialize.
2018-09-29 14:20:02 ERROR (MainThread) [homeassistant.setup] Unable to set up dependencies of camera.zoneminder. Setup failed for dependencies: zoneminder
2018-09-29 14:20:02 ERROR (MainThread) [homeassistant.setup] Unable to prepare setup for platform camera.zoneminder: Could not set up all dependencies.