Same issue with command line cover, buttons greyed out. I have to manually set the state after a reboot then ok. Major pain… hope there is a fix soon.
I hope this is the right place: After upgrading to 0.109 (and 0.109.3) the integration with TP Link smartplugs has changed: When switched on/off from elsewhere (e.g. by voice (google) or manuel), the Home Assistant takes about 15 seconds to recognize the change. Before it was instant. Hope you can help with this. Thanks. BR.
it has been fixed. install 0.109.3
Thanks Mate, I just did and yes its been fixed. Happy now 
.
totally agree, Windspeed was very useful, now have to click. Hope there will be an option.
Mostly ok update.
The Panasonic Viera UI only integration has many issues compared to the YAML version, but the issues seem to be being addressed by the author.
With firefox I initially didn’t see any logos on the integration page. I quickly worked out it was EFF’s privacy badger addon blocking them. Must have been triggered by the word “brands”.
For clarity and ease of use the logos should be smaller than the entity_id. A page full of logos may look great but functionally it leaves a lot to be desired. It’s difficult to find what I’m looking for amongst all that clutter.
No blocking I/O in the event loop detected yet. Which is good.
5 Likes
Much easier than that, use device triggers from that same screen (device details). It is documented in the docs, and working since HA v0.108
I have the same issue with Google Cast devices, after upgrading to 0.109, all cast devices went offline.
Running Docker Home Assistant Core (with --net=host ), all devices on the same network, all devices with fixed IP, no VLAN, no custom components installed (only HACS, last version),
Last version it worked was 0.108.x.
Do you have mDNS enabled for your network? The recent update now relies on this method for discovery.
Is anyone having issue with Homekit? I am getting duplicate devices. I only have one contact sensor on home assistant but HomeKit on the phone is showing 2 devices. 1 of which is unavailable.
Update: It seems only Samsung smartthings devices were affected. Maybe an issue with samsung integration? I already tried deleting and readding smartthings integration.
2 Likes
Same problem here with Jarolift covers.
Hope this will be fixed soon
Same problem here with Devolo z-wave thermostats! Any solution?
I just used working alternatives in HACS.
0.109 my wall tablet stay very slow every time I need to turn on or off a light I need to wait x sec to start working it freezes
Same here!
Has anyone tried to check configuration validation? It is so fast that it looks like it does not actully check if everything is ok. It makes me feel uncertain 
Hm, I don’t see where you can set up triggers on that screen.What am I missing?
The Automation-link is only offering changes of battery level:
Got some problems with ikea tradfri lights and the transition command in scenes.
A scene turn_on command with transition sets the brightness of the bulbs most of the time to the minimum brightness level. Sending the command twice with a pause doesn’t work either.
But another scene command without transition works well and sets the brightness on the bulbs correctly.
Another thing is that mired isn’t saved in the scenes editor and manually set in the yaml doesn’t work as well. The bulbs behave with the last mired setting they’ve got.
I would really like windspeed back on the card. I use windspeed and wind direction a couple times a day.
Good feedback, this had already been implemented in the 0.110 dev builds a few days ago. Integrations with multiple entries will be grouped together in 0.110. So you’ll have just one ESPHome card / logo with those 4 entries (doorbell_upstairs, ensuite_dht, etc) shown inside the card in a list format. Should cut down on clutter and make things quicker to find.
3 Likes