You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The SolarEdge local integration utilizes a local API which has been disabled by the manufacturer on recent firmware updates. See additional details and user reports here and here. This will likely continue to work forever on inverters which were manufactured during a certain period and do not receive firmware updates, but is unlikely to work for the majority of users.
I have updated the documentation to clarify the issue, but am wondering if this integration should be deprecated or hidden in someway to reduce user confusion.
Environment
Home Assistant Core release with the issue:
Last working Home Assistant Core release (if known):
Hey there @scheric, mind taking a look at this issue as its been labeled with a integration (solaredge_local) 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.
The problem
The SolarEdge local integration utilizes a local API which has been disabled by the manufacturer on recent firmware updates. See additional details and user reports here and here. This will likely continue to work forever on inverters which were manufactured during a certain period and do not receive firmware updates, but is unlikely to work for the majority of users.
I have updated the documentation to clarify the issue, but am wondering if this integration should be deprecated or hidden in someway to reduce user confusion.
Environment
Problem-relevant
configuration.yaml
Traceback/Error logs
Additional information
The text was updated successfully, but these errors were encountered: