Closed danpowell88 closed 4 years ago
Hey there @squishykid, mind taking a look at this issue as its been labeled with a integration (solax
) you are listed as a codeowner for? Thanks!
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. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue now has been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.
Yes, the integration will need to be changed to poll until the inverter is discovered.
Yes, the integration will need to be changed to poll until the inverter is discovered.
Could you make a PR with the code needed to make this "bug" go away, please?
Home Assistant release with the issue:
Home Assistant 0.103.6
Last working Home Assistant release (if known):
Operating environment (Hass.io/Docker/Windows/etc.):
Docker **Integration:**https://www.home-assistant.io/integrations/solax/
Description of problem: Some (possibly all?) of the solax inverters power off overnight when there is not enough light to sustain the inverter itself, the inverter will power up the next day when there is enough sunlight to power it.
If home assistant is restarted while the inverter is off the sensor is not able to be discovered and it is not tried again.
Problem-relevant
configuration.yaml
entries and (fill out even if it seems unimportant):Traceback (if applicable):
Additional information: Is it possible to modify it so that it continues to try to connect to the inverter even when not getting a response initially?