You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Once a while I noticed that domoticz was not updating the p1/watermeter counter anymore. It also shows an error that the p1/watermeter worker thread was not responsive. The only way to fix this was to restart the domoticz server
In once such case I used gdb to learn the worker thread was blocking in a call to urllib.request.urlopen
By adding a timeout argument to this call the blocked problem is fixed.
I now see once a while a log message regarding failed communications but that's a benign condition which is most likely fixed in the next update request.
2025-01-06 10:13:41.529 Status: Watermeter: Started.
2025-01-06 10:13:41.530 Status: Watermeter: Entering work loop.
2025-01-06 10:13:42.321 Status: Watermeter: Initialized version 1.0.0, author 'Eraser'
2025-01-06 11:26:41.138 Error: Watermeter: Failed to communicate with Wi-Fi Watermeter at ip 192.168.1.4 with port 80
2025-01-06 14:16:11.088 Error: Watermeter: Failed to communicate with Wi-Fi Watermeter at ip 192.168.1.4 with port 80
2025-01-06 17:48:31.115 Error: Watermeter: Failed to communicate with Wi-Fi Watermeter at ip 192.168.1.4 with port 80
2025-01-06 20:19:42.359 Error: Watermeter: Failed to communicate with Wi-Fi Watermeter at ip 192.168.1.4 with port 80
2025-01-06 21:55:42.813 Error: Watermeter: Failed to communicate with Wi-Fi Watermeter at ip 192.168.1.4 with port 80
2025-01-06 23:18:32.107 Error: Watermeter: Failed to communicate with Wi-Fi Watermeter at ip 192.168.1.4 with port 80
Once a while I noticed that domoticz was not updating the p1/watermeter counter anymore. It also shows an error that the p1/watermeter worker thread was not responsive. The only way to fix this was to restart the domoticz server
In once such case I used gdb to learn the worker thread was blocking in a call to
urllib.request.urlopen
By adding a timeout argument to this call the blocked problem is fixed.
I now see once a while a log message regarding failed communications but that's a benign condition which is most likely fixed in the next update request.
See also my fix at:
gettevan@6f0be08
The text was updated successfully, but these errors were encountered: