I am super excited about this release as it brings some great examples of how we are refining the system to become more customizable and, at the same time, user friendly. The first thing that I am really excited about is a new experimental user interface that we call Lovelace. Check this awesome rundown of all the features by @ciotlosm. The TL;DR: a faster, more customizable and more extensible UI with the same look and feel as the old one.
Be aware, this is experimental, so things will change. However, we felt like we didnât want to keep this away from you any longer. Check the Lovelace UI docs on how to get started. Make sure to share your creations!
Thanks to all the people that have been hanging out in the #beta channel on Discord helping development, finding and squashing bugs and making suggestions. Especially thanks to @c727 for all his development work and @arsaboo for being the first guinea pig.
Example user interface created using Lovelace (source)
Another change is that Nest, Sonos and Cast will now have to be configured using a config entry. Config entries can be created via the integrations page in the config panel. This is a concept that we have been developing for a couple of months now and itâs our goal to eventually use this as the way to configure all components.
Screenshot of the Nest config entry.
And as if this releases even needs more cool stuff, the Insteon integration now supports X10 thanks to @teharris1. It was a frequent requested feature from the Insteon community.
And finally, weâll be extending the open beta for Home Assistant Cloud until the first of September.
Enjoy this release and have a good weekend all!
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.
Excellent work.
A small suggestion. Although all this work greatly benefits the old users, we need to consider a bit more the learning curve for Home Assistant. Even keeping up with the new developments requires a bunch of time and keeping an eye on the git.
A new user will be overwhelmed - especially when there are parallel options and nothing is phased out. I would highly recommend that the frontend should also provide friendly configuration options (from the frontend) and not using exclusively more and more yaml files.
So I see I canât specify my 4 google homes/miniâs under the media players by IPs. I tried to specify them as indicated on the warning/info log under the cast piece it still wouldnât work. I ended up having to turn on discovery for them and they showed up but now I still canât specify them by IP if I turn discovery off. Any workarounds other than rolling back a version?
Looks like it throws an error if I a specify an IP even for just one of the speakers:
Error while setting up platform cast
Traceback (most recent call last):
File â/usr/src/app/homeassistant/helpers/entity_platform.pyâ, line 129, in _async_setup_platform
SLOW_SETUP_MAX_WAIT, loop=hass.loop)
File â/usr/local/lib/python3.6/asyncio/tasks.pyâ, line 358, in wait_for
return fut.result()
File â/usr/src/app/homeassistant/components/media_player/cast.pyâ, line 205, in async_setup_entry
async_add_devices, None)
File â/usr/src/app/homeassistant/components/media_player/cast.pyâ, line 214, in _async_setup_platform
pychromecast.IGNORE_CEC += config.get(CONF_IGNORE_CEC, [])
AttributeError: âNodeListClassâ object has no attribute âgetâ
I did that as well to get them configured but then when I turn discovery back off and specify the IPs of each it throws the errors. Iâll open an issue on github.
My Lovelace cards are rendering in one big vertical column, not three cards across like the pic in post one. Any ideas? Updated to 0.72 via hassbian-config today. Everything else seems to be working. My very simple Lovelace config file is:
name: Our Place
views:
- name: Test
theme: dark-mode
cards:
- type: entity-filter
title: Lights
filter:
- domain: light
state: 'on'
card: glance
card_config:
title: Lights which are on
- type: entity-filter
filter:
- domain: light
state: 'off'
card: glance
card_config:
title: Lights which are off
- type: media-control
entity: media_player.kitchen
- tab_icon: mdi:settings
name: Debugging
cards:
- type: entity-filter
filter: [{}]
card_config:
title: All entities
Apparently it only works if you have a Nest security product, when it first updates the attribute is set. I only have a thermostat so it never updates.
