Hi all,
I used to have the custom Atag component, but now it is integrated in the core. Great! So I thought I’d give it a try. And it worked immediately. However, when I did a restart. It became unavailable. Has anybody seen this?
The log says:
Failed to update Atag Data: [Errno None] Can not write request body for http://192.168.2.15:10000/retrieve
TIA
you cant ‘fix’ this as it is per design. You have to listen for event, hue_events probably on the events page, and can create automations using the device_automation.
Or, install the CC eventsensor by @azogue, or the now stalled CC huesensor/remote by @robmarkcole which both will create sensors with the last button_event for you. Each with their own merits, and disadvantages.
Very good Release. Just a small question - should the new Panasonic Viera Component work with all TV’s that workd before? I’m not able to setup the new component.
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.
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.
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 
