Skip to content
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

Several logging of "Centrale non connessa" and sensors unavailable during reconnection #121

Closed
coserotondo opened this issue Jan 22, 2024 · 2 comments
Assignees
Milestone

Comments

@coserotondo
Copy link

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

  • Operating System (OS): HAOS 11.4
  • Library version (commit or version number): 2.2.1
  • Home Assistant version: 2024.1.3
  • Last working Home Assistant release (if known): -
@palazzem
Copy link
Owner

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:

  • Be 100% sure we can downgrade the message from ERROR to INFO (if it's expected, you should not be worried about).
  • Avoid sensors to be unavailable for a very short amount of time. This improves the user experience.

Thanks again! I'll try to go at the bottom of it!

@palazzem palazzem self-assigned this Feb 1, 2024
@palazzem palazzem moved this to In Progress in e-Connect Roadmap Feb 1, 2024
@palazzem palazzem added this to the 2.3.0 milestone Feb 1, 2024
@palazzem
Copy link
Owner

palazzem commented Feb 1, 2024

This is partially solved in #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 #76 .

@palazzem palazzem closed this as completed Feb 1, 2024
@github-project-automation github-project-automation bot moved this from In Progress to Done in e-Connect Roadmap Feb 1, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Archived in project
Development

No branches or pull requests

2 participants