Solaredge API problem

[McMieras]

Hello,

I use the Solar Edge API for years.
Since Friday i getting the next error: "PV SolarEdge: Error getting http data (Sites)!"

Alle line for the web, mentioned in this post, works like it use to.
Retarting Domoticz or the RPI does not help.

Installed on a second system, gives the same error.

Anybody any suggestions?

Greetings
Mark

Edit
On the web browser everything works, when entering the site-ID in the line.
The lines without site-ID and only the API-key like (https://monitoringapi.solaredge.com/sit ... i_key=<key>) returns "access denied"

[Doler]

Same problem here (SolarEdge: Error getting http data (Sites)!).

[Relbel]

On my site with 2 Solaredge with diverent API-KEYs the same result.
On browser :https://monitoringapi.solaredge.com/sit ... i_key=<key>
Result: Access Denied
With Domoticz 'SolarEdge via Web API"
Result in the log:
2026-03-09 22:00:57.311 Error: omvormer schuur: Error getting http data (Sites)!
2026-03-09 22:00:57.315 Error: omvormer dak: Error getting http data (Sites)!
Did the change something on the other site?

[jannl]

hm, in Domoticz I get the error and no data, while the direct api call in a browser gives result.
Must be something off in the code.

[Doler]

In the Domoticz code the sites request is

Code: Select all

https://monitoringapi.solaredge.com/sites/list.json?size=1&api_key=yourkey

Using this in the browser returns Access Denied. Looking at the api description the 'list.json' should be only 'list' (json is the now the only format that is used by the api). But changing that does give the same result. Apparently SolarEdge is doing something wrong.

[jannl]

Also that url works fine in my browser (Microsoft Edge in this case).

But now Domoticz also gets updates. Still not sure Solaredge is the problem, may be they changed something.

Edit: checked the outcome, that url only provides general data about the site, no live data.

[Kedi]

I get the folowing responses:

Code: Select all

https://monitoringapi.solaredge.com/sites/list.json?size=1&api_key=<key>
Access Denied
https://monitoringapi.solaredge.com/site/<siteid>/inventory.json?api_key=<key>
Valid response with Inverter data
https://monitoringapi.solaredge.com/equipment/<siteid>/list.json?api_key=<key>
Valid response with Inverter data

I did not check the real data yet, but I suppose that that is OK too, and that the first response ( Access Denied ) is the problem.
This one on the SolarEdge website also went wrong

Code: Select all

https://monitoring.solaredge.com/one#/residential/site-admin/siteDetails/details?siteId=<siteid>

Other api calls went OK too.

Edit:

Code: Select all

https://monitoringapi.solaredge.com/equipment/<siteid>/<invertersn>>/data.json?startTime=2026-03-11%2009:00:00&endTime=2026-03-11%2010:00:00&api_key=

Went OK too. SO it is likely that everything goes wrong on the first API call mentioned

Edit again:
This is in the latest API document from 2026-03 in the revision part.

Revision History
▪ March 2026 –
•
Removed deprecated endpoints: Site Image, Installer Logo Image, Equipment Change Log, Account List, Sensors
(List and Data), and API Versions (Current and Supported).
•
Removed CSV and XML response format support across all remaining endpoints - only JSON is now supported.
•
Updated Sites List API: "Full address" is no longer supported in searchText, and "CreationTime" sort option has
been removed.

I wonder if that might impact the Domoticz SolarEdge hardware.

[Doler]

Maybe there should be a few adaptations to the updated api but I think it's Solaredge. My guess is that the first query is for sites in order to obtain the siteID. When that goes wrong (Access Denied) all subsequent queries will fail so the program will escape.
Someone with connections at SolarEdge could ask what is going on.

[gizmocuz]

Just use the build in hardware support in Domoticz?

[Kedi]

I am using the SolarEdge via Web API native hardware in Domoticz.
I think it is the 'GetSite' which gets the answer from SolarEdge that Access is denied.
I know my siteId but can't fill it in.
Or simply put, this from the Wiki does not show anymore.

Add_hardware.png (60.99 KiB) Viewed 34539 times

[Bjornen]

Hi!
I have used the built in "Solaredge via Web API" all this time. No problem until this year.
Also did a feth for de-domoticz from Github and did a complete make according to the "build Domoticz from source" on the wiki. On a different brand new PI 5 and fresh install. Not docker version.
I also did a tcpdump on the traffic to check that the right server was called and yes it was.
I am no wiz at C++ but I did try to add some "debug" in the c code and make it again. sResult says Access denied.
So except from really display every request and response I am wondering if either Domoticz/Cloudflare has set some checks in place. Or some update on the Debian/Raspbian OS webparts has tricked the request in some way. Do not know if one can put in a trace just before the data is encrypted.
Or third option: I am totally wrong up the creek without the paddle. But is still do not work properly.
Some times it can just start to work. Sometimes a restart of either hardware or a complete reboot does not solve the problem.
But I am open to sugestions on how to debug if you have som clue on where to put the "debug".

Best regards Bjornen

[Doler]

Just use the build in hardware support in Domoticz?

That is just the problem: Domoticz hardware queries for sites and doesn't get a proper answer (just Access Denied) from Solaredge.

[gizmocuz]

If it does not work, then the web api does not work. It is the same endpoint as the python version?

I just made some additions to the native hardware version

[Doler]

I don't know about the Python version, I'm using the native hardware version. Looking at the code it queries for sites using the url

Code: Select all

https://monitoringapi.solaredge.com/sites/list?api_key=[your_key]

where it gets no answer. Thus sideID is unknown and the hardware stops here because all other queries will fail (siteID is needed argument).
So the problem resides at Solaredge, the sites api doesn't work. All other api url's with correct siteID will give a correct answer.

[Bjornen]

Hi!
DId a git pull and a new make. Since this a testsystem without anything else but Solaredge, this is the startup log. Se third line from bottom.
Is there anything else I can supply or do on this case, I am fine with that.

2026-03-11 18:55:32.875 Status: Domoticz V2025.2 (build 17358)-beta (c)2012-2026 GizMoCuz
2026-03-11 18:55:32.875 Status: Build Hash: e90cc62a6, Date: 2026-03-11 16:13:42
2026-03-11 18:55:32.875 Status: Startup Path: /home/kusinvitamin/domoticz/
2026-03-11 18:55:32.889 Error: Default admin password has NOT been changed! Change it asap!
2026-03-11 18:55:32.892 Sunrise: 06:15:00 SunSet: 17:40:00
2026-03-11 18:55:32.892 Day length: 11:25:00 Sun at south: 11:58:00
2026-03-11 18:55:32.892 Civil twilight start: 05:35:00 Civil twilight end: 18:20:00
2026-03-11 18:55:32.892 Nautical twilight start: 04:47:00 Nautical twilight end: 19:08:00
2026-03-11 18:55:32.892 Astronomical twilight start: 03:58:00 Astronomical twilight end: 19:58:00
2026-03-11 18:55:32.915 Status: PluginSystem: Started, Python version '3.11.2', 1 plugin definitions loaded.
2026-03-11 18:55:32.918 Active notification Subsystems: (0/13)
2026-03-11 18:55:32.918 Status: WebServer(HTTP) started on address: :: with port 8080
2026-03-11 18:55:32.923 Status: WebServer(SSL) started on address: :: with port 443
2026-03-11 18:55:32.924 Starting shared server on: :::6144
2026-03-11 18:55:32.924 Status: TCPServer: shared server started...
2026-03-11 18:55:32.924 Status: mDNS: Service started
2026-03-11 18:55:32.924 mDNS: Service: _http._tcp.local.:443 for Hostname: stockholm test (1 socket)
2026-03-11 18:55:32.924 Status: RxQueue: queue worker started...
2026-03-11 18:55:34.926 Status: NotificationSystem: thread started...
2026-03-11 18:55:34.926 Status: EventSystem: reset all events...
2026-03-11 18:55:34.927 Status: EventSystem: reset all device statuses...
2026-03-11 18:55:34.940 Status: Python EventSystem: Initializing event module.
2026-03-11 18:55:34.941 Status: EventSystem: Started
2026-03-11 18:55:34.941 Status: EventSystem: Queue thread started...
2026-03-11 18:55:53.825 Status: [web:8080] Incoming connection from: 192.168.50.53
2026-03-11 18:56:31.068 Status: Sunpanel: Worker started...
2026-03-11 18:56:36.220 Error: Sunpanel: Error getting http data (Sites)!
2026-03-11 18:56:57.812 Status: Sunpanel: Worker stopped...
2026-03-11 18:59:05.631 Status: [web:8080] Incoming connection from: 192.168.50.91

Regards
Bjornen

[Bjornen]

Hi!
Hold your horses!! I think I discovered something fishy. Want to investigate it a little bit and I'll be back.

Best regards
Bjornen

[Kedi]

I downloaded the latest. This error message is still there: Error: SolarEdge: Error getting http data (Sites)!
Error is 'obsolete' now the continue; is in place.
Have to see tomorrow if data is coming in. I checked the new functions GetOverview() GetEnergyDetails() and they work.
No 'Access Denied'

[gizmocuz]

Please discard my previous comments... Sorry about that! I implemented the SolarEdge polling a long long time ago for a friend.
First we hacked the local protocol (TCP), that was a big challenge as there was no data available, but after weeks of deciphering big blocks of raw binary returns we made it.
Next we found out that we could poll it via the API that he got from the installer.

But... I thought that now/then it did not work anymore, until I received a message this morning that it does not work for over a week now.

After doing more research, it seems HASS users also have this issue (GitHub issue #134208)

This seems to be the steps to solve it:

How to fix SolarEdge API "Access Denied"

SolarEdge updated their Terms of Service around March 9, 2026. Until you accept the new terms, the API will return "access denied" for all requests.

Steps:

Code: Select all

 1. Open a browser and go to https://monitoring.solaredge.com
  2. Log in with your SolarEdge account credentials
  3. You should see a pop-up or banner asking you to accept the new Terms of Service and Privacy Policy — accept it
  4. Navigate to Admin (top menu) > Site Access
  5. Find the API Access section
  6. Make sure API access is enabled/activated
  7. Re-check the checkbox "I have read, understood and agree to the API Terms & Conditions"
  8. Click Save
  9. If it still doesn't work after the above steps:
    - Click Generate API Key to create a new key
    - Copy the new API key
    - Update the API key in your Domoticz hardware configuration (Setup > Hardware > your SolarEdge entry)
  10. You may also need to repeat the TOS acceptance in the SolarEdge mobile app if you use one

After completing these steps, the API should start responding normally again. It may take a few minutes for the changes to take effect.

[Kedi]

The SolarEdge still did not work.
I followed (partially) the suggestions from @gizmocuz and found out that there was on other API-key present on the website from SolarEdge.
Used that key and 6 new SolarEdge devices were created. All the old ones except 1 one (PV Power) were updated too.
So it is working again. B.t.w. no more errors in the logging.

[JaapB]

Please discard my previous comments... Sorry about that! I implemented the SolarEdge polling a long long time ago for a friend.
First we hacked the local protocol (TCP), that was a big challenge as there was no data available, but after weeks of deciphering big blocks of raw binary returns we made it.
Next we found out that we could poll it via the API that he got from the installer.

But... I thought that now/then it did not work anymore, until I received a message this morning that it does not work for over a week now.

After doing more research, it seems HASS users also have this issue (GitHub issue #134208)

This seems to be the steps to solve it:

How to fix SolarEdge API "Access Denied"

SolarEdge updated their Terms of Service around March 9, 2026. Until you accept the new terms, the API will return "access denied" for all requests.

Steps:

Code: Select all

 1. Open a browser and go to https://monitoring.solaredge.com
  2. Log in with your SolarEdge account credentials
  3. You should see a pop-up or banner asking you to accept the new Terms of Service and Privacy Policy — accept it
  4. Navigate to Admin (top menu) > Site Access
  5. Find the API Access section
  6. Make sure API access is enabled/activated
  7. Re-check the checkbox "I have read, understood and agree to the API Terms & Conditions"
  8. Click Save
  9. If it still doesn't work after the above steps:
    - Click Generate API Key to create a new key
    - Copy the new API key
    - Update the API key in your Domoticz hardware configuration (Setup > Hardware > your SolarEdge entry)
  10. You may also need to repeat the TOS acceptance in the SolarEdge mobile app if you use one

After completing these steps, the API should start responding normally again. It may take a few minutes for the changes to take effect.

I do not have the part in my menu for site access and I noticed the direct method with the API allong with usernumber from the browser does work.
So I used my shadowsysteem where I also have OpenHAB installed and OpenHAB does need usernumber and API key and workst fine.

I guess the new terms from solaredge now need both to work again within Domoticz.