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

Feedback

I want to use the data about the api to use it in evcc to control the charging of my car. First I tried to get the actual data from my inverters (I have 2 Inverters with seperate batteries) by Modbus TCP, but I only get the data from the master inverter. The data from the slave inverter are not available. So I intend to use the data about the API connection. The polling time 15 min is to long at day. At night it is ok and be longer, but at day (app. from 6am to 8pm) I need data minimum in 5 minutes. Is it possible to shorten the polling intervall? If yes, how can I do it?

URL

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

Version

2025.4.2

Additional information

No response

Hi,

I have a similar setup like you with two inverters. I use in addition to the solaredge api/app modbus tcp and the "solaredge multi" integration.
As stated in the documentation of "solaredge multi", the modbus device id is usually for all invertes 1 in the beginning, if the installateur does not already 'repair' this. Thats why you only see the first inverter via modbus. (since each modbus device needs to have its own id).
I was able at my site to change the modbus device Id of the second inverter, and now I can see both inverters.
Some of the example template sensors need to be adapter for multiple inverters, but this was not too difficult...

since the solaredge API has a rate limit, I don't think you can reduce the time between API calls to a level which you want or need for evcc. ("Data is updated every 15 minutes to stay within the daily rate limit of 300 requests per day.")

So depending on your use case I think either some clamp sensor on your power line e.g. to measure live outgoing power or getting all inverters via modbus is the more desireble and robust solution...

Greetings,
Uno

Thank you for your answer. I solved the problem to use the dates from slave-inverter by modbus tcp. The slave-inverter has now id2 und the master-inverter id1.