v3.1.0-beta.X - Autoreconnect when inverter power-cycles without log spam #76
alexdelprete
announced in
Announcements
Replies: 1 comment
-
Please test beta.5. I'm testing it since 24h without disabling the integration or any external automation. The solution was to test if Modbus TCP was available at socket level before trying the modbus connect (pymodbus call). This avoids all the errors etc. The retry mechanism is managed by HA itself, and the integration will be online automatically as soon as the TCP port is available (inverter on) and the Modbus TCP connect is processed correctly. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
First beta regarding the old issue that I wasn't able to solve in the past regarding the log spamming when inverter is powered off and the integration tried repeatedly to setup again, spamming HA log. Now the integration relies on HA internal services to automatically retry setup with just one warning initially and that's it (details here: https://developers.home-assistant.io/docs/integration_setup_failures#handling-offline-or-unavailable-devices-and-services).
This is a first major attempt to solve the issue, hoping I finally fixed it. Will test for a couple of days before releasing a new stable version...
Also...next version will require HA 2023.9.2 (pymodbus 3.5.2).
This discussion was created from the release v3.1.0-beta.1 - Autoreconnect when inverter power-cycles without log spam.
Beta Was this translation helpful? Give feedback.
All reactions