0.81: new Lovelace cards, LG soundbars, Dyson fans, Elk-M1

Yeah I’m not getting the new Thermostat card to display either for my Netatmo, thought it was just me. Look out for 0.81.1 soon :slight_smile:

3 Likes

I’m getting the same. It’s a real hassle to need to run chmod g+w ui-lovelace.yaml almost every time I make changes to the file. It’s not every time, it seems to happen when new cards have been added since this is triggering the creation of autogenerated ids. It seems a massive oversight if writing to the file is changing the permissions.

I’m also getting the “Cannot read property ‘states’ of undefined” error on all my views, since they all consist of a vertical-stack containing other cards, so my entire interface is a mess of red currently.

2 Likes

Remove the space between “user” and “name” in your config, so that it reads “username”

I can‘t change that but after several retries it‘s working now. Don‘t know why.

it is now added to the docs, works for me now

I assume to get the icons properly working on the new thermostat card the modes must be set to something in particular?

I have hot, cold, vent and off. Everything but vent is fine, but vent is invisible but I can still click it and it works. I assume if I change ‘vent’ to ‘fan’ that might work?

Anyway to change the title of the thermostat card?
Additionally after the update my weather card is not responding.
image

2 Likes

my conditionalcard it’s the same after the 0.81 update…
Immagine

1 Like

Same here:
media-control inside vertical-stack is crashing LovelaceUI. Pulling out the media-control of the stack ist just working fine.


3
The same happens to weather-forecast and sensor inside vertical-stack.

Looks like some of it is explained/discussed here: https://github.com/home-assistant/home-assistant/pull/17498

I have the same with tado


after the update .81

1 Like

I think there are enough “red pictures” in this topic.
This will be fixed in 0.81.1.

2 Likes

Has anyone else seen an issue where a majority of their MQTT devices disappear? The ones running esphomeyaml and espuna seem to be alright, but anything being sent over by the SmartThings MQTT Bridge and Blue Iris are gone with the 0.81.0 release. I’ve got an issue open here. If I downgrade to 0.80.3 then everything comes back as expected.

Running 0.81.1 and still no Thermostat card showing in my Lovelace config :frowning:

2 Likes

Thanks, that is certainly the explanation. As a user, this freaking sucks. As a lifelong developer, the attitude of the developers freaking sucks. There is no need to rewrite the file, it should be opened and modified instead. I’ll be commenting on the issueThe issue is locked and can’t be commented on (outside the collaborators).

Ok, that’s the reason behind the modification inside the file. No issues with that (although some say it’s modifying the structure of the file too).

However there is no need to delete the original file and write a brand new file that happens to have the same name. And thereby set the change the file permissions and ownership. The file can be opened for rw and modified, as explained in this StackOverflow answer. This method preserves the ownership, permissions and link aspects (eg if the file is in another location, but is linked into the ~homeassistant/.homeassistant directory).

Ahhhhhm, no…:confused:
Sorry to say, but: 0.81.1 and same as above.

Edit: Have to clarify: Installed 0.81.1 from Docker (on Synology) but Version is showing as “0.81.0.dev0” :thinking:

0.81.1 fixed it for me.
All my cards/entities work within a vertical or horizontal stack.
Browser cache?

Are you using latest tag? I did the same on my Synology with docker and it’s not showing dev for me.