search

home-assistant / core

:house_with_garden: Open source home automation that puts local control and privacy first.
https://www.home-assistant.io
Apache License 2.0
71.11k stars 29.79k forks source link

OTGW: devices doesn't go offline even without gateway #30167

Closed andriej closed 4 years ago

andriej commented 4 years ago

Home Assistant release with the issue: 0.103.4 Last working Home Assistant release (if known): n/a

Operating environment (Hass.io/Docker/Windows/etc.): hass.io

Integration: https://www.home-assistant.io/integrations/opentherm_gw/

Description of problem: Even after disconnecting power from LAN connected OTGW all entities are still available in UI, just not updating the values. I've turned off whole boiler/thermostat too. RIght now all sensors show latest gathered data, which is wrong.

Problem-relevant configuration.yaml entries and (fill out even if it seems unimportant): n/a

Traceback (if applicable): no errors

Additional information: Gateway after loosing connection should become unavailable (and it's entities) so it can be tracked.

probot-home-assistant[bot] commented 4 years ago

Hey there @mvn23, mind taking a look at this issue as its been labeled with a integration (opentherm_gw) you are listed as a codeowner for? Thanks!

mvn23 commented 4 years ago

This is not a supported feature at this time and would need to be implemented in the pyotgw library first. I will consider implementing it in a future release, but I can't give an ETA at the moment.

andriej commented 4 years ago

Right now there's no way to make automation detecting lost connectivity and manage potential issue with gateway, so please put it on to-implement list.

andriej commented 4 years ago

Still an issue, I had problem with power and didn't know about the problem as entities were still available in UI.

mvn23 commented 4 years ago

This should be fixed in 0.109 by #32408 and #33529, but I forgot to mention it in the PRs. Please check and provide feedback once 0.109 is out. Thanks!

andriej commented 4 years ago

So nice!

stale[bot] commented 4 years ago

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue now has been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

andriej commented 4 years ago

Has been fixed by mentioned PRs