-
Notifications
You must be signed in to change notification settings - Fork 13
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
Integration Times out when Polling Optimizers during Setup #68
Comments
Well, restarted. It started working. We'll see. |
Reopened. Much more often than not, the integration fails as reported in the first post. |
i will check this with my own integration. problem remains that the connection to the site it self is unstable at times. |
we now see:
which might be the same but worded differently? Not sure. this is running 2024.5.0b2 btw @ProudElm would you please check the PR by BDraco? It might help streamlining the startup proces |
I installed BDraco's refactored version #67 in HA 2024.5.2 and just now using 2024.6.2 and the problem persists - timeouts on connecting to the solaredge cloud. Occasionally a panel or two, or all 30, will connect, but then they all go off-line pretty quickly. The solaredge app works fine. |
I have whitelisted the following IP addresses and the integration loads and acquires panel level data. I will monitor this, but it seems to work. You may or may not have to add all of these. The last one I added, and that finally got it working is:
|
Nope, the endpoints seem to hop about. Now, I've whitelisted all of |
(May be related to #67).
The integration finds the inverter, knows that there are 30 panels, tries to get data for the first one, then times out doing so. Occasionally, the process will complete, but then will quit working after a bit of time. This used to be very solid. I'm on HA v2024.3.3 in Docker, and v1.2.4 of this integration. The same issue shows up in HA v2014.2.2.
My SolarEdge App sees the data and my credentials have not changed.
Here are the log data:
The text was updated successfully, but these errors were encountered: