-
Notifications
You must be signed in to change notification settings - Fork 19
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
ht_proxy.py never recovers from USB disconnect #23
Comments
I'll check this. Best to throw an exception and try to reconnect that interface n-times. |
@joed74
After this update stop and restart that processes with:
Above mentioned problem is fixed with this modification. |
ht_proxy now connects wonderfully again, but the basic problem that no more graphs are drawn and no more data is transmitted via mqtt is still there as before ;(
What is the difference between: before: USB disconnect, reconnect ht_proxy_if.py stops working, ht_collgate.py stops working -> no graphs update, no mqtt upate (frozen) now: USB disconnect, reconnect ht_proxy_if.py still working, ht_collgate.py stops working -> no graphs update, no mqtt update (frozen) Isn't it possible to hold the client connections up and running an only reconnect to the USB data source? Additional observation: The status in the MQTT remains online, although no data has been sent for half an hour... |
The MQTT-status 'online' is assigned to the MQTT-client availabilty itself and not to any data-transfer. The 'ht_collgate.py' and it's included mqtt-client are still running, so that MQTT-status must be 'online'.
Yes, this should be possible and a solution. But keep in mind also that socket- and thread-handling is my aim to be improved. |
I am using a pitiny adapter with an ttl USB converter.
I am using an udev-rule so that the USB device always shows up as /dev/heatronic3 symlink.
If i disconnect the USB port and reconnect it, ht_proxy just freezes and i must restart ht_proxy and ht_collgate.
Would be nice, if ht_proxy could try to reconnect every second or so...
The text was updated successfully, but these errors were encountered: