New Solar Edge Battery informartion does not update

[lbreggi]

The problem

Hi! just updated to:Installation method
Home Assistant OS
Core
2026.5.0
Supervisor
2026.04.2
Operating System
17.3
Frontend
20260429.3

and the new sersors related to Solar Edge battery are not getting update, the only way to update is restarting the integration. everything else works fine.

What version of Home Assistant Core has the issue?

2026.5.0

What was the last working version of Home Assistant Core?

2026.4.4

What type of installation are you running?

Home Assistant OS

Integration causing the issue

Solar Edge

Link to integration documentation on our website

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

Diagnostics information

home-assistant_solaredge_2026-05-07T00-40-51.955Z.log

Example YAML snippet

Anything in the logs that might be useful for us?

Additional information

No response

[home-assistant]

Hey there @frenck, @bdraco, @tronikos, 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, problem in config, problem in device, feature-request) to the issue.
• @home-assistant remove-label needs-more-information Remove a label (needs-more-information, problem in dependency, problem in custom component, problem in config, problem in device, feature-request) on the issue.

_{^{(message by CodeOwnersMention)}}

---

@lbreggi Thanks for reporting this issue!

Before we dive in, please make sure this isn't a duplicate by searching through existing issues. Also check recently closed issues, as your problem might already be fixed but not yet released.

https://github.com/home-assistant/core/issues?q=%20label%3A%22integration%3A%20solaredge%22%20
_{^{(message by IssueContext)}}

---

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

[tronikos]

@it-rec since you added battery support, can you take a look?

[it-rec]

Sure.

[it-rec]

Ok when reading your comment I think there might be a misunderstanding.

SolarEdge has a a hard limit on requests per time unit. This limit spans across all API requests. So every new feature that needs to invoke new APIs or existing, called APIs, more frequently pushes us against this limit.

The limit is 300 calls per day.

That said: I had to implement this new feature very defensively that it only asks every 4 hours for the battery interval data. This means it only updates every four hours.

That said: in the response are however the values for the entire timespan of those four hours.

So its not a bug. It's by design.

[it-rec]

The clean solution that I would whish is that SolarEdge would allow to subscribe to a local event stream to get live data but that is simply not supported.

[it-rec]

@tronikos are you aware of if we use the web API of your lib we can get around it? In general I ask myself what the differences and consequences there are in detail

[tronikos]

@tronikos are you aware of if we use the web API of your lib we can get around it? In general I ask myself what the differences and consequences there are in detail

No I don't but I would strongly recommend not trying to get around it. They have the limits to keep their server resources manageable.

What I recommend is users switch to one of the two solaredge modbus integrations. You can pull data every second locally via modbus.

[lbreggi]

Thanks for all the inputs! Really appreciate. Would you think that we could have an option to set the pooling frequency instead? Also I see that the integration has already a battery % sensor (now we have 2) - maybe we can stick with the original one and give more bandwidth for the other 2 battery sensors (charging / discharging)
Unfortunately Solar Edge does not enable battery information through modbus in most of cases (including myself) so I need to stick with the cloud integration.

[it-rec]

Unfortunately not. The issue is that both come from different apis. You can with one API get all the information about your energy which includes your battery percentage and from the other API you get the consumption of the battery or how much it charges or discharged.

From consumption perspective very bad.

Before I implemented the feature at the beginning I was thinking that I could write a little logic that always observes how much percentage is consumed over time and by that compute the discharge or charge. But that would be very unstable in a historical correct. And consumes a lot of complexity, storage and all. Getting it directly from an API is stable, accurate and the right way. Sadly we have to use two apis.

If you want only one then you loose relevant information. That is it in a nutshell

[nico-pinnecke]

Ok when reading your comment I think there might be a misunderstanding.

SolarEdge has a a hard limit on requests per time unit. This limit spans across all API requests. So every new feature that needs to invoke new APIs or existing, called APIs, more frequently pushes us against this limit.

The limit is 300 calls per day.

That said: I had to implement this new feature very defensively that it only asks every 4 hours for the battery interval data. This means it only updates every four hours.

That said: in the response are however the values for the entire timespan of those four hours.

So its not a bug. It's by design.

For me, my sensor datapoints do not update at all. The integration is running for about 2 weeks now and energy levels for the battery never went over 0kWh. I don't mind updates only every 4 ours, but I think it is not working as intended. This is the case for both the battery and inverter sensors.

[it-rec]

Let me revisit it