-
Notifications
You must be signed in to change notification settings - Fork 75
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Devices that go offline do not fetch the alarm state after returning #196
Comments
Yeah, more logs should be useful. We're continuously querying all devices. When it come back online, alarms should be fetched. |
@KapJI So here are my steps that i can reproduce the problem with:
Specifically:
I see regular polling:
But i do not see the problem device being queried here. Strangely, I notice that this one device has this log:
EDIT: A second reboot seems to make the device show up. So this feels like it's something timing related. |
Right now we only run zeroconf discovery once during HA startup. If device was not found, it won't get any updates. |
hmm, we perhaps after introducing |
Yeah, that's actually pretty similar to #122 |
Describe the bug
Every morning at around 02:50 my google homes go offline for some reason for about 10 minutes. I get the log: "maybe it is offline" and then they come back online.
However. If i have any alarms set, these alarms do not show back up. After restarting home assistant they still show as unavailable. It appears that alarms do not show up in the state unless they are set while the integration is running and connected.
Version of the integration
1.4.1
Logs
I can get more logs, currently typing this from phone as this just happened a few minutes ago.
The text was updated successfully, but these errors were encountered: