Good idea, will have to wait until next Saturday unfortunately as we’re away for the week now 
1 Like
There aren’t any settings in the inverter that affect the solaredge monitoring platform, unless you disconnected it from the internet.
2 Likes
Hmm ok - it’s odd though that the sensor.solaredge_solar_power entity is so high when you compare it to the sensor.solaredge_i1_ac_power and sensor.solaredge_i2_ac_power sensor which seem to be fine. It’s definitely the inverter side though as the monitoring app is showing the same as the first gauge here.
Can you show the history graphs for those entities as it may give a better indication of what is happening over time?
Maybe raise a job with SolarEdge support as well as they will take at least a week to get back to you.
Something is wrong because the meter power doesn’t match what your equipment is capable of. Your meter CT value might be incorrect compared to the actual CT installed in the panel and causing it to return an inflated value.
Inverter SE10K-AUB* is maximum 10000 watts AC and SE8250H-* is maximum 8250 watts AC. That’s a total of 18250 watts AC, or 18.25 kW. A solar export of 34kW is impossible with those two inverters.
Agreed - I believe the 34kW is in reality 16kW, somehow things are getting doubled by the meter.
The “CT Rating” value tells it what ratio to apply to the displayed meter values. That value needs to match whatever is printed on the CT inside the panel.
This may be it, although I did take not that before the changes it had 200A ratings in the config so had made sure that was the same when I re-configured. Will have to wait until I get back home to test out changing that to 60A, unless you know of a way to do it remotely / through your network?
CT rating can’t be changed through modbus.
1 Like
I had a problem where, on a se10k rws, i was setting the ct rating (via web page, i have no access via setapp) to 100a (correct value) and after few weeks it reverted back to 70a, causing a false self consumption reading. I’ve opened a ticket on solaredge, and they found a problem in the config of the inverter leaved by my installer. I hope that now is fixed 
Hello everyone,
I recently installed the Solaredge Modbus integration and enabled Modbus TCP on the inverter (SE10K).
Connected to the IP address and correct port, but I only receive partial sensor data.
I can see current production, but not current usage, import and export…
Most M1 sensor data shows -0,1
Is there anything else I need to configure to show the correct M1 data, and to show current use, import/export?
Thanks in advance for any help.
This is my connected meter:
That doesn’t look like my integration, so I can’t say.
I was trying to set the modbus integration, but can’t find the settings on the inverter. Where and how can I set the modbus connection on? I have a solaredge se2000m-rw002 n 4 inverter.
I’ve searched Google, but it seems I’m missing some settings menu in the app
You need to use the Set-App - not the SolarEdge End-Consumer app. Normally, the Set-App is something an installer uses. However, you can do that on your own.
Just google “Set-App SolarEdge ModBus” - and you’ll find the manual (in your language) that explains how you can do that. Best way, of course, is to ask the installer to activate ModBus during installation.
I would add that on some solaredge inverters (for sure on the RWS SExxK series - as i’ve done it) you can set the modbus via wifi. Once connected to the inverter hotspot, you can access to a webpage that allow the configuration of most of the parameters available via setapp
1 Like
Thanks! I’ve made an installer account to access the second app, since I wasn’t allowed to login as end user. The inverter was also not setup as leading, but as following. After I changed those settings it all connected smoothly!
Hello,
sorry for my bad english… Great work, almost everything works!
But when i try restart Hass it wont work. A error pop up. Some weeks ago i didnt have any problems.
Any idea?
Thx!
I see there is a Modbus related breaking change in HA 2023.10.
Will this have any impact on the Modbus integration used here?
That’s a YAML configuration option specific to the modbus integration.
1 Like