Sungrow SH Series Hybrid Inverter (grid)

Installation

1. 1Enable Modbus TCP on the Sungrow SH Series inverter: connect to the inverter via the iSolarCloud local access portal, navigate to the communication or Modbus section, and confirm Modbus TCP is active on port 502.
2. 2Connect the inverter's LAN port (or WiNet-S Ethernet port) to the same network segment as the ModbusCloud Gateway, ensuring the inverter has a reachable static or reserved IP address.
3. 3In the ModbusCloud portal, add a new device, import the Sungrow SH Series Hybrid Inverter (grid) template, and enter the inverter's IP address and unit ID (default unit ID is 1, as per Sungrow documentation).
4. 4Verify the connection by checking that the portal displays a live, non-zero reading on the power register (13009); a value near zero at night or a negative value during grid import confirms correct communication.

Things to watch for

01

Register 13009 always reads zero even when the system is running.

Register 13009 reports smart meter data, not inverter output directly. If the Sungrow DTSU666 energy meter is not wired correctly or its Modbus address conflicts, the inverter cannot relay meter values. Check the meter's RS485 wiring and confirm the meter is communicating with the inverter in the iSolarCloud app before polling over Modbus TCP.

02

The gateway connects but per-phase current values look wrong.

Per-phase currents are derived by dividing per-phase active power (5602, 5604, 5606) by the corresponding phase voltage (5018, 5019, 5020). If voltage registers return scaled raw counts rather than volts, check that your client applies the 0.1 V scaling factor documented for those uint16 registers. A missing scaling step produces currents that are 10 times too high.

03

Why do I get intermittent timeouts when polling the inverter over the WiNet-S dongle?

The WiNet-S Wi-Fi and Ethernet bridge introduces additional latency compared to a direct LAN connection to the inverter's built-in port. Increase the Modbus inter-message delay to at least 20 ms when using WiNet-S. For stable polling, use the inverter's internal LAN port directly where available.

04

Energy values at register 13036 appear to reset or jump unexpectedly after a firmware update.

Sungrow has modified register content and data types across firmware versions; version 1.0.15 of the communication protocol changed registers 13008 and 13009 from U32 to S32. After a firmware update, verify the register data type and scaling still match the template. If values are implausible, reconnect and cross-check against the iSolarCloud app readout.

Registers (8)

8 read / 0 write

More Sungrow templates

SUNGROW Hybrid Inverter

Sungrow

Modbus TCP

Reads energy, battery, and power data from Sungrow hybrid inverters via Modbus TCP.

14 registers251

Sungrow SH Series Hybrid Inverter (pv)

Sungrow

Modbus TCP

2 registers

SU

Sungrow New Hybrid 2024 SH15-25T Modbus RTU

Sungrow

Modbus RTU

Monitors Sungrow hybrid inverter data via Modbus RTU over RS-485

0 registers92

SUNGROW Inverter

Sungrow

Modbus TCP

Reads power and energy data from Sungrow solar inverters via Modbus TCP.

4 registers108

Sungrow iHomeManager (iHM) (battery)

Sungrow

Modbus TCP

2 registers

Sungrow iHomeManager (iHM) (pv)

Sungrow

Modbus TCP

1 registers

More TCP templates

Domekt R 400 V

Komfovent

Modbus TCP

Controls Komfovent Domekt recuperator ventilation via Modbus TCP

25 registers118

Fronius - Modbus TCP

Fronius

Modbus TCP

Monitors Fronius Symo and Primo inverters via Modbus TCP

15 registers597

NIBE Nibe S-Series (SG Ready)

NIBE

Modbus TCP

5 registers1

SunSpec Model 709 — DER Trip LF

SunSpec

Modbus TCP

9 registers

Victron Meter AcOut

Victron

Modbus TCP

16 registers

FoxESS Avocado (grid)

FoxESS

Modbus TCP

8 registers