-
Notifications
You must be signed in to change notification settings - Fork 32
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
Online entities stay disconnected after wifi-router boot #362
Comments
Hmm... |
My HA is not open to internet (HA is connected to the same wifi as Easee Home and Equalizer). Attributes before testing, HA was rebooted earlier, both devices's online status = connected. Rebooted wifi box, actually two times. Rebooted HA, both devices's online status = connected. |
That is not what I meant with internet connection, I mean the access from HA to internet (and to Easee cloud specifically). So there seems like there are 2 issues:
I do not think it has anything to do with the chargers connection to WiFi, it probably the fact that HA looses the connection that triggers the problem. |
One more thing... At least sometimes, after wifi reboot, easee online entities are in state 'connected' for some time. And only after x minutes their state canges to 'disconnected'. |
There is a 17 minute timeout compared to the lastestPulse timestamp before a device is considered to be offline. |
Might be, not sure if the delay was that long |
My initial attempt to reproduce this failed, for me the SignalR stream reconnected automatically after HA:s internet connection returned. |
This is just a guess, but normal reboot maybe 2-3 minutes? Less than 5 min, I guess. Maybe you can try to unplug power cable from your router for 5 min, maybe 10 min? |
I have ' When Easee Home Online changes to Disconnected for 1:00' automation, which notifies my phone. I most probably wouldn't notice these disconnections without this automation. |
I think I have some idea why the online logic does not work in polling mode, the polling logic has changed some time ago and how to detect if the charger is online in this mode was overlooked when that was changed. But it is a mystery to me why on your end the SignalR stream does not reconnect after router reboot. I think to get any further on that we need to see some log files from your system.
And then trigger the error, maybe we could get some hints from the log file... |
I have today rebooted my wifi router more than 10 times. HA/Easee logging enabled and disabled. And Easee Home & Equalizer both stay all the time connected to HA. The problem described in my initial bug report has happened for me multiple times since May 2023. What is different now? |
Ok. Maybe some of the libraries that HA installs (and we use) could cause something like this. The behaviour I expect (and that I have) is that signalRconnected goes false pretty soon after internet connection is lost. Well, if it happens again, please try to capture a log file. |
This happened again today. I enabled logging and made similar changes to wifi router settings and rebooted router few times. Just guessing, maybe this happens only after HA has been running longer time? Few days maybe? |
Ok, depending on what hardware you are running your HA on it might be good if you leave debug logging on. I do not think we will be able to deduct what your problem is by guessing, so we really need a log file to look at. |
The problem
I have seen this problem few times (maybe always when I reboot my wifi-router, not sure).
When I reboot my wifi-box, then my Easee Home and Equalizer binary_sensor.xxx_online entities will be marked as disconnected in HA.
When the wifi-box has rebooted and Easee Home and Equalizer have been connected again to my wifi network (I see it in Easee app), these entities stay in disconnected state in HA.
Everything else works, I can see correct states of all other entities and their values update correctly.
Rebooting HA changes these entities back to connected state.
Version of Easee integration having the issue?
0.9.55
Version of Home Assistant Core having the issue?
2023.10.1
Anything in the logs that might be useful for us?
No response
Additional information
No response
The text was updated successfully, but these errors were encountered: