Sungrow iHomeManager (iHM) (pv)

Installation

1. 1Enable Modbus TCP on the Sungrow iHomeManager: open the iSolarCloud app or the local web interface, navigate to the communication or Modbus section, and confirm that Modbus TCP is active on port 502 with unit ID 247.
2. 2Connect the iHomeManager to the same LAN segment as the ModbusCloud Gateway, either via its Ethernet port or by confirming the existing network path; note the iHM's IP address for the next step.
3. 3In the ModbusCloud portal, add a new TCP device, enter the iHM's IP address and port 502, set the unit ID to 247, then import this template to map register 8154 automatically.
4. 4After import, open the live register view in the portal and spot-check the power register: confirm the value matches the current PV yield shown in the iSolarCloud app to verify the connection is working.

Things to watch for

01

Why does the power register return zero or nonsense values?

The iHomeManager transfers 32-bit registers in little-endian word order. Ensure your Modbus client applies a word-swap when reading the int32 value at address 8154. Without the swap, the two 16-bit words are combined in the wrong order, producing incorrect or zero readings.

02

The gateway connects but no values appear after import. What now?

The iHM accepts only one Modbus TCP connection at a time on port 502. Disconnect any other Modbus clients such as Home Assistant or third-party monitoring tools before polling from the ModbusCloud Gateway. Also confirm the unit ID is set to 247, not the default of 1.

03

PV power reads correctly on the inverter but not on the iHM. Why?

When an iHomeManager is added to a Sungrow system, the inverter stops exposing generation and grid data on its own Modbus interface. The iHM takes over measurement at the grid connection point. You must poll the iHM directly at its own IP address for PV power data.

04

The iHM's IP address changes and breaks the connection. How do I prevent this?

Assign a static IP address to the iHomeManager in your router's DHCP settings using the device's MAC address. Alternatively, if your router supports hostname-based routing, use the iHM's hostname. Update the IP in the ModbusCloud portal device configuration after any change.

Registers (1)

1 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 SH Series Hybrid Inverter (grid)

Sungrow

Modbus TCP

8 registers

More TCP templates

Algodue Energy meter UEM80-2D E

Algodue Elettronica S.r.l.

Modbus TCP

Measures single-phase energy consumption and production via Modbus TCP.

12 registers46

Sigenergy SigenStore EC (grid)

Sigenergy

Modbus TCP

5 registers1

Fronius GEN24

Fronius

Modbus TCP

Monitors and controls Fronius GEN24 inverters and PV batteries via SunSpec Modbus TCP

0 registers762

HUAWEI SUN2000 Inverter & LUNA2000 battery

Huawei

Modbus TCP

Monitors HUAWEI SUN2000 inverter, LUNA2000 battery, and Smart Power Sensor via Modbus TCP.

4 registers1248

NIBE Nibe S-Series (SG Ready)

NIBE

Modbus TCP

5 registers1

Fronius - Modbus TCP

Fronius

Modbus TCP

Monitors Fronius Symo and Primo inverters via Modbus TCP

15 registers597