Modbus Register für Sungrow Wechselrichter zum Import in Iobroker

sungrow_modbus_register.tsv

Based on this post by user Atlantis in the iobroker board: https://forum.iobroker.net/post/520225

Updated to match most recent TSV format of modbus adapter, mostly by removing the first column, renaming the second + adding formula, room, cw, isScale

A reduced set of sungrow registers can be found here => https://gist.github.com/dnoegel/6ac76fdbd3dd4e2425162207508cbd53

I have done installation of Sungrow in the last days with post of Atlantis, but I had to add column deviceId behind _adress with value 1

Thanks for this very helpful list. One remark:

13007 | Load power actually is a signed int32sw instead of uint32sw. Can have negative values, f.e. if storage is charged from AC side. Also according to spec: https://github.com/bohdan-s/Sungrow-Inverter/blob/main/Modbus%20Information/communication-protocol-of-residential-hybrid-inverterv1.0.20-1.pdf page 9 row 52

I think in line 57 (13002, Total PV Generation, PV-Stromerzeugung gesamt) the factor is not OK, the value is 0.1 in my case. I don't use all lines and so I don't checked other lines.

Does anybody know if there are also registers for the DTSU666 power meter? I'm specifically looking to get some values directly from there, like current of the phases at the grid handover point, which are not included in what I can get from the inverter. As far as I understand, the power meter has modbus ID 254 (in my case), but I don't know if it possible to query the device through the modbus implementation on the inverter.

13004 seems to need a factor of 0.1 as per my testing with my SH6.0RT.

I have done installation of Sungrow in the last days with post of Atlantis, but I had to add column deviceId behind _adress with value 1

You need to do this if you have checked Multiple device IDs in the Modbus Adapter.

Which is advisable to do, since now we can also read some interesting battery metrics from the battery itself - assuming you have updated your battery firmware to 21.

If you did that it shows up as a separate entity, which makes it adressable in modbus at device ID 200 (the device ID may differ and can be checked on the WinetS under Device Monitoring).

These Registers are taken from this github for home assistant.
Here are the registers formatted for the ioBroker modbus adapter (Multiple device IDs needs to be checked).

On my Sungrow SH5.0RT, the factor of 13004 is 0.1.

Interesting finding (for me): I cannot set the max discharge power to 0. I can set the value to 0 - but it will be ignored. To disable discharging, I have to set the value to 10 - which sets it to 10 - but essentially disables discharging.

Took me a while to wrap my head around it and understand, why it perfectly scales up the discharge power, but does not set it to 0.

Thanks for the feedback so far, changed the factors for 13002 and 13004 - and also changed to signed int for 13007.

I was missing a few more values to use them in the openWB wallbox. Did a lot of adress dump + search, since also the latest Sunggrow modbus specs are incomplete. Have a look at https://github.com/Mantelinho/core/blob/patch_sungrow_modbus/packages/modules/devices/sungrow/modbus.md.

Most interesting maybe (for SH inverter connected via LAN):

• Register 5030 for AC load power at inverter (useful for effective delivered power)
• Register 13009 for total AC load power at smart meter, negative values if power consumed from net, positive if exported
• Register 5602, 5604, 5606 (int32sw) for load power per phase at smart meter
• Register 5740, 5741, 5742 for voltages per phase at smart meter. Attention: 5018/19/20 contain the voltages delivered at inverter!

I was missing a few more values to use them in the openWB wallbox. Did a lot of adress dump + search, since also the latest Sunggrow modbus specs are incomplete. Have a look at https://github.com/Mantelinho/core/blob/patch_sungrow_modbus/packages/modules/devices/sungrow/modbus.md.

Most interesting maybe (for SH inverter connected via LAN):

• Register 5030 for AC load power at inverter (useful for effective delivered power)
• Register 13009 for total AC load power at smart meter, negative values if power consumed from net, positive if exported
• Register 5602, 5604, 5606 (int32sw) for load power per phase at smart meter
• Register 5740, 5741, 5742 for voltages per phase at smart meter. Attention: 5018/19/20 contain the voltages delivered at inverter!

Quick question: Is 5030 actually different from 13007?

The other ones I already listed here, in case you still need some more.

I was missing a few more values to use them in the openWB wallbox. Did a lot of adress dump + search, since also the latest Sunggrow modbus specs are incomplete. Have a look at https://github.com/Mantelinho/core/blob/patch_sungrow_modbus/packages/modules/devices/sungrow/modbus.md.
Most interesting maybe (for SH inverter connected via LAN):

• Register 5030 for AC load power at inverter (useful for effective delivered power)
• Register 13009 for total AC load power at smart meter, negative values if power consumed from net, positive if exported
• Register 5602, 5604, 5606 (int32sw) for load power per phase at smart meter
• Register 5740, 5741, 5742 for voltages per phase at smart meter. Attention: 5018/19/20 contain the voltages delivered at inverter!

Quick question: Is 5030 actually different from 13007?

The other ones I already listed here, in case you still need some more.

(edit: Sorry, I mixed this up with 13033)

13007 is the load in the local net (sum of AC consumption), in other words the sum of 13007 and 13009 equals 5030. But: if you have more than one producer (another inverter), 13007 may be negative since the SH does not consider other inverters in retrofit modus for register 13007.

So if you are looking for a 5030 alternative (e.g. if your SH is connected via WiNet), take 13033. They have the same value:
13033: SH via LAN and WiNet-S dongle
5030: SH via LAN and SG via WiNet-S dongle
Both hold the AC active power delivered by the inverter, the value you see as "Wirkleistung gesamt" in iSolarCloud Live-Data.