Solaredge Binding not getting data

Hello,
Since a couple of days I don’t get proper data from my solaredge system. The data just does not update. I think the historical data does update properly, I can see the monthly production increase during the day. Sometimes it works, especially just after a reboot, then it just stopps.
The thing just shows a “server error”. I have set the binding to debug logging mode, but as far as I can see it seems to log normal.behaviour. http answer is 500 and no errors. Nevertheless it does not show items changing in the logs. This is visible if the items do update properly.

I seriously have no idea, as the error is not even specific or thrown in the logs.
Any idea where I could dig for more info on this error?

Also solaredge had some problems with their servers a couple of days ago. The app also did not update, but this seems to be fixed. Also I would think any bad response from the server would result in an entry in the logs reflecting the problem.

Does anyone else have problems with the solaredge Binding in the last couple of days? Or any ideas how to solve this?

Thanks for any advice!
EDIT: It seems it actually is a server error on SolarEdges servers. I used their manual to get the API working in the browser and while I am able to get historical data, I cannot get the live data from my site. The answer is “internal server error” with HTTP code 500, so probably nothing on the bindings side. Will keep this thread updated. Also, I found this error in the logs, just had to search a little bit, as every update generates an entry, and the requests concerning historical data get executed without any issues. Would love to hear if other users have the same issue.

Hi @javamaster10000 ,

I have the same issue using Openhab 4.0.3 and 4.1M1.

Same situation: The binding is announcing COMMUNICATION_ERROR while historic and live data is collected successfully via API calls. Strange…

Same here. Cumulated data is arriving, live data only every now and then, about once or twice a day.

2023-10-17 13:49:58.764 [INFO ] [openhab.event.ItemStateChangedEvent ] - Item 'SolarEdge_Web_Battery_Level' changed from NULL to 0.8
2023-10-17 14:09:58.739 [INFO ] [openhab.event.ItemStateChangedEvent ] - Item 'SolarEdge_Web_Battery_Level' changed from 0.8 to 0.79
2023-10-17 14:39:58.795 [INFO ] [openhab.event.ItemStateChangedEvent ] - Item 'SolarEdge_Web_Battery_Level' changed from 0.79 to 0.78
2023-10-18 00:00:00.132 [INFO ] [openhab.event.ItemStateChangedEvent ] - Item 'SolarEdge_Web_Battery_Level' changed from 0.78 to 7 %

Actually in the SolarEdge app, there was a message yesterday about them being sorry about the servers being slow and them working on it.
I think this might be related to this. Also yesterday I got somewhat good data, so I think it will get solved, but might take some time.

Any updates on this? I’m seeing the same error. I’ve had to update my password, but after update the tokenAPI key (SPRING_SECURITY_REMEMBER_ME_COOKIE) it still doesn’t work. This is what I’m getting from the logs:

2023-11-24 08:44:48.617 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing 'solaredge:generic:7678c42a' changed from OFFLINE (COMMUNICATION_ERROR): HttpConnectionOverHTTP@c5cdb9::DecryptedEndPoint@1774b23{l=/192.168.1.134:35246,r=monitoring.solaredge.com/XXXXXXX,OPEN,fill=-,flush=-,to=524825/0} to UNINITIALIZED
2023-11-24 08:44:48.645 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing 'solaredge:generic:7678c42a' changed from UNINITIALIZED to UNINITIALIZED (DISABLED)
2023-11-24 08:44:50.239 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing 'solaredge:generic:7678c42a' changed from UNINITIALIZED (DISABLED) to INITIALIZING
2023-11-24 08:44:50.263 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing 'solaredge:generic:7678c42a' changed from INITIALIZING to UNKNOWN: Waiting for web api login.
2023-11-24 08:45:20.577 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing 'solaredge:generic:7678c42a' changed from UNKNOWN: Waiting for web api login. to ONLINE
2023-11-24 08:55:50.752 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing 'solaredge:generic:7678c42a' changed from ONLINE to OFFLINE (COMMUNICATION_ERROR): HTTP protocol violation: Authentication challenge without WWW-Authenticate header
2023-11-24 08:58:51.032 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing 'solaredge:generic:7678c42a' changed from OFFLINE (COMMUNICATION_ERROR): HTTP protocol violation: Authentication challenge without WWW-Authenticate header to UNKNOWN: Waiting for web api login.
2023-11-24 08:59:21.330 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing 'solaredge:generic:7678c42a' changed from UNKNOWN: Waiting for web api login. to OFFLINE (COMMUNICATION_ERROR): HTTP protocol violation: Authentication challenge without WWW-Authenticate header
2023-11-24 08:59:49.697 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing 'solaredge:generic:7678c42a' changed from OFFLINE (COMMUNICATION_ERROR): HTTP protocol violation: Authentication challenge without WWW-Authenticate header to UNINITIALIZED
2023-11-24 08:59:49.717 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing 'solaredge:generic:7678c42a' changed from UNINITIALIZED to UNINITIALIZED (DISABLED)
2023-11-24 08:59:52.887 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing 'solaredge:generic:7678c42a' changed from UNINITIALIZED (DISABLED) to INITIALIZING
2023-11-24 08:59:52.894 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing 'solaredge:generic:7678c42a' changed from INITIALIZING to UNKNOWN: Waiting for web api login.
2023-11-24 09:00:25.027 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing 'solaredge:generic:7678c42a' changed from UNKNOWN: Waiting for web api login. to OFFLINE (COMMUNICATION_ERROR): HTTP protocol violation: Authentication challenge without WWW-Authenticate header
2023-11-24 09:02:16.748 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing 'solaredge:generic:7678c42a' changed from OFFLINE (COMMUNICATION_ERROR): HTTP protocol violation: Authentication challenge without WWW-Authenticate header to UNKNOWN: Waiting for web api login.
2023-11-24 09:03:06.902 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing 'solaredge:generic:7678c42a' changed from UNKNOWN: Waiting for web api login. to OFFLINE (COMMUNICATION_ERROR): HTTP protocol violation: Authentication challenge without WWW-Authenticate header

same here - since about one week:

2023-12-18 20:21:39.446 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing 'solaredge:generic:se8k' changed from UNINITIALIZED to INITIALIZING
2023-12-18 20:21:39.458 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing 'solaredge:generic:se8k' changed from INITIALIZING to UNKNOWN: waiting for web api login
2023-12-18 20:22:10.052 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing 'solaredge:generic:se8k' changed from UNKNOWN: waiting for web api login to OFFLINE (COMMUNICATION_ERROR): Server Error

before i got the message “too many requests” - so i disabled the binding for two days, now there is only the “server errror”.
live poll: 15min
aggregate data: 60min

Are you using the token for the inofficial private API (SPRING_SECURITY_REMEMBER_ME_COOKIE)?

I had to renew the token, that did the trick for me.

i’m using the official api key from the se portal, and i renewed it already 2 times. :frowning:

Actually I opened a case with solaredge. They are working on it.

1 Like

UPDATE: They solved it. After hopping on their WhatsApp support they opened a case and after a couple of weeks they solved it. Just turned the binding back on a couple of days ago and now it is working perfectly. No idea why…

Yes :slight_smile: Thanks for opening the ticket.
Just tried and the binding is back online.

Since a couple of days my binding doesn’t login again.
Logfile says “waiting for web api login”
Does anyone else have the same problem?
Thanks
Andy

Binding is working here. try to renew your api key in the SE Portal

Thanks for your reply. I’m using the private API because I need more than 300 requests per day. Already tried to update the private API token, but it’s still not working.
Is anyone else using the private API?
Thanks
Andy

Have you tried restarting OH? I had the same problem and restarting OH solved it.

Thanks!
Restart solved it!!