-
-
Notifications
You must be signed in to change notification settings - Fork 32.5k
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
Solax remains in initialization on reboot #99421
Comments
Hey there @squishykid, mind taking a look at this issue as it has been labeled with an integration ( Code owner commandsCode owners of
(message by CodeOwnersMention) solax documentation |
I've been getting this bug for a few months as well. Once it has timed out and failed at start up, going into devices and running a reload typically brings it up for me. |
Hi @greengumbyaus , I tried it too but it didn't work, the only way I found working is just deactivate the component, reboot and then when finished reactivate it |
There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. |
The issue still exists. |
Can also confirm this still exists, upgrade from 2023.12.0 to 2023.12.1 and had to manually reload the solax integration after the initial timeout. |
The discovery code in the upstream library is most likely at fault. For some reason, some inverters fail / crash when getting hit by multiple query attempts, which is what the discovery code does: it tries all the variants in turn. If your inverter is far down the list (like the X1HybridGen4) it will get hit multiple times with invalid requests and may start timing out. The hack to make this go away is to modify the integration code to try your particular inverter first. You need to modify solax/discovery.py in HA's site-packages directory and change the order of the REGISTRY array. |
See more details here as well #66617 |
in the case where the Inverter type is already known. Some inverters at the end of the REGISTRY (e.g. X1HybridGen4) randomly crash because the discovery code issues too many incorrect requests before sending the correct one. This patch adds a variant of the entry point in which one can specify the name of the inverter type. This addresses home-assistant/core#66617 and home-assistant/core#99421
The problem
When I run the server restart, the Solax integration stays in the initialization state and then goes to error
I am forced to deactivate it, restart the server and reactivate it
What version of Home Assistant Core has the issue?
core-2023.8.4
What was the last working version of Home Assistant Core?
No response
What type of installation are you running?
Home Assistant OS
Integration causing the issue
solax
Link to integration documentation on our website
https://www.home-assistant.io/integrations/solax
Diagnostics information
home-assistant_solax_2023-08-31T19-08-13.872Z.log
Example YAML snippet
No response
Anything in the logs that might be useful for us?
Additional information
No response
The text was updated successfully, but these errors were encountered: