core: SolarEdge integration reports errors with SolarEdgeInventoryDataService

The problem

Just updated to 2021.10.6 and the previously working SolarEdge integration now reports errors to the log.

What version of Home Assistant Core has the issue?

core-2021.10.6

What was the last working version of Home Assistant Core?

core-2021.09.6

What type of installation are you running?

Home Assistant OS

Integration causing the issue

SolarEdge

Link to integration documentation on our website

https://www.home-assistant.io/integrations/solaredge/

Example YAML snippet

No response

Anything in the logs that might be useful for us?

Error requesting <homeassistant.components.solaredge.coordinator.SolarEdgeInventoryDataService object at 0x7f381d3978b0> data: 429 Client Error: for url: https://monitoringapi.solaredge.com/site/nnnn/inventory?api_key=XXXX
Error requesting <homeassistant.components.solaredge.coordinator.SolarEdgeOverviewDataService object at 0x7f381d397880> data: 429 Client Error: for url: https://monitoringapi.solaredge.com/site/nnnn/overview?api_key=XXXX

Additional information

No response

About this issue

Original URL
State: closed
Created 3 years ago
Reactions: 1
Comments: 25 (2 by maintainers)

Most upvoted comments

Quoting the SolarEdge API Documentation (https://www.solaredge.com/sites/default/files/se_monitoring_api.pdf)

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. Concurrency Limitation The monitoring server API allows up to 3 concurrent API calls from the same source IP. Any additional concurrent calls will return HTTP 429 error – too many requests. To execute APIs concurrently without exceeding the above limitation, it is the client responsibility to implement a throttling mechanism on the client side.

Are you sending API requests too quickly?

It could also be that the solaredge server is taking too long to handle requests leading to the multiple requests now being concurrent.

If it was purely a config issue at HA hitting a concurrency limit because of the HA polling pattern I would expect a more consistent pattern of 429’s. Based on the incidents I grepped from my log I was unable to spot such a pattern (doesn’t mean it’s not there, just less likely).

Personally I suspect server load or software issues at SolarEdge are causing the response times to be overly long.

I received a reply from SolarEdge, confirming that it was a software bug on their end which has now been resolved. Will check in a few days to confirm my experience.

JelleKoster on Nov 29, 2021

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.

github-actions[bot] on Feb 27, 2022

+1 reliability of this integration has reduced for me here as well.

purcell-lab on Nov 19, 2021