-
Notifications
You must be signed in to change notification settings - Fork 5
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
Plugin gets into a tight connection loop #8
Comments
@nberardi I am not planning to support third party proxies like this. This wouldn't happen on a real device, which already handles a 10 second delay between attempts to reconnect. Your proxy that you developed is probably accepting the connection and then dropping it, which triggers a different flow. |
This tool was developed originally to log the connection information only. It was purely by accident I discovered this issue, while trying to work out why the device connection was dying on startup when connected to the HA plugin. The plugin was not handling a 10 second delay, on startup while the thermostat was booting up. And the spamming of the connection, causes it to go back into the state where it doesn’t accept a connection. |
@nberardi FYI, I think I see where the issue is, and it will be fixed in the next release. Your proxy did a thing where it accepted and dropped the connection, which I hadn't seen happen before. The logic didn't properly handle the case where a disconnect would happen in that state. I'm going to reopen this, it should be fixed in general with the next release. |
That is great to hear regarding the fix. That connecting and dropping is something I have observed and logged on my 8840 above as well. It seems to happen when the thermostat gets overwhelmed with connections.
The proxy’s logic is whenever the thermostat would disconnect, I would send a disconnect to the client as well. |
@nberardi The change described has been released in 0.5.0. Thanks! |
The plugin gets into a tight connection loop when it cannot connect and ends up overwhelming the device. I discovered this with the proxy client that I messaged you about.
In the below logs
10.10.0.24
is my thermostat, and10.10.0.52
is my HA box. You can see how often the HA box is trying to reconnect to establish a connection.The text was updated successfully, but these errors were encountered: