Einrichtungsfehler, wird erneut versucht: 429, message='', url='https://monitoringapi.solaredge.com/site

[stefanMenschel]

The problem

all SolarEdge sensors not available

no connection to SolarEdge API !

What version of Home Assistant Core has the issue?

HA Core 2025.4.4

What was the last working version of Home Assistant Core?

No response

What type of installation are you running?

Home Assistant OS

Integration causing the issue

No response

Link to integration documentation on our website

No response

Diagnostics information

No response

Example YAML snippet

Anything in the logs that might be useful for us?

Additional information

No response

[home-assistant[bot]]

Hey there @frenck, @bdraco, mind taking a look at this issue as it has been labeled with an integration (solaredge) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of solaredge can trigger bot actions by commenting:

• @home-assistant close Closes the issue.
• @home-assistant rename Awesome new title Renames the issue.
• @home-assistant reopen Reopen the issue.
• @home-assistant unassign solaredge Removes the current integration label and assignees on the issue, add the integration domain after the command.
• @home-assistant add-label needs-more-information Add a label (needs-more-information, problem in dependency, problem in custom component) to the issue.
• @home-assistant remove-label needs-more-information Remove a label (needs-more-information, problem in dependency, problem in custom component) on the issue.

_{^{(message by CodeOwnersMention)}}

---

solaredge documentation solaredge source _{^{(message by IssueLinks)}}

[mib1185]

please provide the full log messages as a comment, thx 👍

[mib1185]

did you change the data update interval? error 429 means "too many requests"

Daily Limitation Use of the monitoring server API is subject to a query limit of 300 requests for a specific account token and a parallel query limit of 300 requests for each specific site ID from the same source IP. APIs that do not have a specific ID (e.g. Site List, Account List) will be counted as part of the account query limit. Any additional site or account level request will result in HTTP 429 error – too many requests.

source: https://knowledge-center.solaredge.com/sites/kc/files/se_monitoring_api.pdf

[stefanMenschel]

Michael,

thx for your Feedback.

I removed SolarEdge integration from my devices and re-installed. Now it works.

I dont know, what was going on. No changes in my code, but today after 4pm all sensors deactivated.

Thx

Stefan

Am 04.05.2025 um 21:02 schrieb Michael @.***>:

mib1185 left a comment (home-assistant/core#144215) https://github.com/home-assistant/core/issues/144215#issuecomment-2849368599 did you change the data update interval? error 429 means "too many requests"

Daily Limitation Use of the monitoring server API is subject to a query limit of 300 requests for a specific account token and a parallel query limit of 300 requests for each specific site ID from the same source IP. APIs that do not have a specific ID (e.g. Site List, Account List) will be counted as part of the account query limit. Any additional site or account level request will result in HTTP 429 error – too many requests.

source: https://knowledge-center.solaredge.com/sites/kc/files/se_monitoring_api.pdf

— Reply to this email directly, view it on GitHub https://github.com/home-assistant/core/issues/144215#issuecomment-2849368599, or unsubscribe https://github.com/notifications/unsubscribe-auth/BNGTIEXRLLHPXKEMHIL4A3T24ZP2TAVCNFSM6AAAAAB4NC2S7KVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDQNBZGM3DQNJZHE. You are receiving this because you authored the thread.

[stefan088]

same problem, since yesterday it freezes at times with no data, then it restarts sometimes

Timeout fetching <homeassistant.components.solaredge.coordinator.SolarEdgeOverviewDataService object at 0x7f59415fce90> data

[meldjan]

same problem, since yesterday it freezes at times with no data, then it restarts sometimes

Timeout fetching <homeassistant.components.solaredge.coordinator.SolarEdgeOverviewDataService object at 0x7f59415fce90> data

Same over here. Home -assistants is reporting: The unit has changed The unit of 'solaredge_zonpanelen Produced energy' (sensor.solaredge_zonpanelen_production_energy) changed to 'Wh' which can't be converted to the previously stored unit, ''. If the historic statistic values have a wrong unit, you can update the units of the old values. The values will not be updated. Otherwise you can choose to delete all historic statistic values, and start over.

How do you want to fix this issue?

Update the unit of the historic statistic values from '' to 'Wh', without converting.

Delete all old statistic data for this entity

CLOSE

FIX ISSUE

[fernbrun]

Same here,

Yesterday and today unable to accecc api from 98:48 CET.

Error message : retry: 429, message='', url='https://monitoringapi.solaredge.com

[N3331N]

Same here. Stopped working 2 hours ago

It’s the 429 error mentioned above.

[mib1185]

feel free to answer my question from https://github.com/home-assistant/core/issues/144215#issuecomment-2849368599

[fernbrun]

did you change the data update interval? error 429 means "too many requests"

Daily Limitation Use of the monitoring server API is subject to a query limit of 300 requests for a specific account token and a parallel query limit of 300 requests for each specific site ID from the same source IP. APIs that do not have a specific ID (e.g. Site List, Account List) will be counted as part of the account query limit. Any additional site or account level request will result in HTTP 429 error – too many requests.

source: https://knowledge-center.solaredge.com/sites/kc/files/se_monitoring_api.pdf

Hello,

I didn't change anything, it stopped working since this morning

[Oliv4nder]

Same problem for me, started yesterday. I do not have any error message 429. Have not changed from default update every 15 min. I have created a workaround with a automation that reloads the integration when it goes unavailble, seems to work so far. The log message I get is posted below. (no internet problems at the house as far I can tell)

Timeout fetching <homeassistant.components.solaredge.coordinator.SolarEdgeOverviewDataService object at 0x7f4c68c640> data Timeout fetching <homeassistant.components.solaredge.coordinator.SolarEdgeEnergyDetailsService object at 0x7f4cdc8510> data Timeout fetching <homeassistant.components.solaredge.coordinator.SolarEdgeOverviewDataService object at 0x7f4cdc8180> data Timeout fetching <homeassistant.components.solaredge.coordinator.SolarEdgeEnergyDetailsService object at 0x7f4d008830> data Timeout fetching <homeassistant.components.solaredge.coordinator.SolarEdgeOverviewDataService object at 0x7f4c031b50> data

[jurajjh]

Same problem for 2 days. Yesterday some interuptions, today afternoon no data completly for half of the day. Reloading the integration now gives this result: solaredge [1 device] and [21 entities] Failed setup, will retry: 429, message='', url='https://monitoringapi.solaredge.com/site/..../details?api_key=G....

Data can be accesed via application or dashboard on monitoring.solaredge.com, but Admin section to generate new API key is missing. It seems to be server API problem with incorrect limitations. Direct acces to API over the web gives this: HTTP Status 429 – Too Many Requests Type Status Report Message Daily limit quota exceeded Description The user has sent too many requests in a given amount of time ("rate limiting"). Apache Tomcat/8.5.46

There were some changes in the API and in the official application. Now I can see changes in power from inventor almost instantly (within seconds). Previously it was in 5 min period max.

[Oliv4nder]

Im starting to wonder if there has been some problems with the Solaredge portal/API. I noticed once yesterday when I tried to reach Solaredge portal through the internet browser I got that the site I wanted to reach was unresponding.

My automation to reload the integration hasn't triggered for the last 16 hours, so no more "unavailable" during that time.

[BufuMerlin]

I have had the same issue, seems to been stable the last 24h now. But good to know that it´s not just me having this problem.

[iantye]

I'm having the same problem can't access the data through the API intermittently throughout the day. Has been doing this for a couple of weeks.

[juronja]

I have a similar problem I think. The dropouts seem to be in a time pattern most of the time (see image). I did not make any changes.

Reading the documentation seems like exactly this is happening. Is it possible SolarEdge changed the api rate limit without notice?

[lampra1]

Same issue here. This is probably home assistant related. I also upload to pvoutput via the api and all seems fine there.

[issue-triage-workflows[bot]]

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 has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.