Closed coserotondo closed 7 months ago
Thank for raising the issue! This error is expected if the central unit or the cloud API decide to reset the connection. I will investigate more to:
Thanks again! I'll try to go at the bottom of it!
This is partially solved in https://github.com/palazzem/ha-econnect-alarm/pull/130 where these log messages are now considered DEBUG
. I'd say we can close this issue as sensors are set to "Unavailable" if the integration can't communicate with the main unit, that makes sense if there is an actual connection issue.
Anyway, I'm planning to rewrite the collector logic to solve the actual root cause, meaning keep the connection as much stable as possibile. This is going to be solved in https://github.com/palazzem/ha-econnect-alarm/issues/76 .
Describe the bug Several logging of "Centrale non connessa" and sensors unavailable during reconnection.
Error message
2024-01-22 11:13:13.883 ERROR (SyncWorker_3) [custom_components.econnect_metronet.devices] Device | Error during the update: "Centrale non connessa" 2024-01-22 11:13:18.816 ERROR (MainThread) [custom_components.econnect_metronet.coordinator] Coordinator | Central unit disconnected, forcing a full update
Environment