Domoticz Community Forum - Support & Discussion

hi

just did the update to V2026.3

got the solaredge api running and get an error every second what never happend before:

2026-08-07 10:19:11.992 Error: zonnepanelen: Web portal: Error getting site layout!
2026-08-07 10:19:13.145 Error: zonnepanelen: Web portal: Error getting site layout!
2026-08-07 10:19:14.365 Error: zonnepanelen: Web portal: Error getting site layout!
2026-08-07 10:19:15.522 Error: zonnepanelen: Web portal: Error getting site layout!

how to fix this?
other data from api is working just fine

thanks!

What SolarEdge api? The build in SolarEdge integration of a python plugin or script?

sorry for not beeing clear

i use the build in "SolarEdge via Web API"

thanks

Perhaps check your SolarEdge configuration in Domoticz.
Else check if the API key is still correct.
Did you upgrade from 2026.2 or an earlier version as there was a change in March this year.

all other data is coming in nice from the inverter.

it is working fine exept this one error.ik keeps coming every second.
so api key is good.
i am worried it keeps the pi unwanted bussy

i dont remember what version i am coming from.i have multiple raspberry's running domoticz.

one died due to a power outage, i had to update all couse of communication errors with older en newer domoticz versions.

so all pi's are running V2026.3 now.

Could it be related to new/changed API endpoints from SolarEdge?

SolarEdge2mqtt made some adjustments too last week:
https://github.com/DerOetzi/solaredge2mqtt/pull/418

i got the mail today about the apiV2.

will the build in solaredge web api be useless after november?(end of V1)

It indeed seems changes are required; https://api-docs.solaredge.com/docs/bas ... m-v1-to-v2

At least base url and authentication change. Summary in the attached image

I will have a look at this today, but when I asked a current Solaredge API user if he experienced any issues, the answer was ''no''
Hope to have an answer this afternoon, unless someone else beats me to it (via a PR)

The Solaredge website mentions:

V1 is currently planned for deprecation on November 1, 2026. Until that date, V1 remains operational and existing integrations continue to function. After November 3, 2026, V1 endpoints will stop responding and only V2 will be available

So it should indeed still function

Thanks for the report, and for the link to the V1/V2 migration notes.

That link turns out to be a red herring for this particular error, so to be clear about what is going on:

There are two independent things in this hardware type.

1. The API key polling (site overview, inverter telemetry, energy details, battery) is fine. That uses the documented monitoringapi.solaredge.com endpoints, which is what the V1 to V2 announcement applies to. I verified it still returns data today. V1 stays up until 1 November 2026, so we will migrate that part well before the deadline.

2. The "Web portal" part is what is broken, and it is not the V1/V2 change. That feature (site layout, strings, per optimizer data) used undocumented endpoints on monitoring.solaredge.com with plain username/password authentication. SolarEdge has now switched those off completely. They answer:
410 means permanently removed, and the page they redirect to is their "Legacy API, sign up for interest" form. So no credential or setting on your side can fix it.

What has been fixed

The web portal login now uses the same OAuth2 sign-in flow the SolarEdge monitoring website itself uses, and reads the layout and optimizer data from the current endpoints. Site layout, strings and optimizers work again.

The once per second error spam is fixed too. That was a separate bug where a failed layout fetch retried on every worker loop instead of every 2 hours. As a bonus, all optimizers are now fetched in one call per cycle instead of one call per optimizer, which is roughly 1680 calls per day down to about 84 on my test system.

Two things to be aware of after updating

• Per optimizer voltage and current are no longer available. SolarEdge does not expose them on the new endpoints at all. Neither Home Assistant nor solaredge2mqtt can read them from the cloud either, the only way to get them is a local Modbus TCP connection to the inverter. Those existing sub devices will stop updating and can be deleted.
• Optimizer power is now an hourly value rather than instantaneous, because that is what the replacement endpoint provides. This means the optimizer and string power figures will not exactly match the live inverter power from the API key side, since they come from different sources and time bases.

This will be in the next beta.