Sungrow iHomeManager (iHM) (pv)
The Sungrow iHomeManager (iHM) is a residential home energy management system that coordinates PV generation, battery storage, EV charging, and load control within a Sungrow installation. This template reads the iHM's PV power register via Modbus TCP, giving the ModbusCloud Gateway a direct source for live solar yield data. When the iHM is installed, the connected inverter no longer exposes grid and generation data on its own Modbus interface, making direct iHM polling essential. Tracking PV power through this template keeps your portal's energy dashboards accurate without relying on the iSolarCloud API.
- Protocol
- Modbus TCP
- Connection
- Ethernet, Modbus TCP
- Registers
- 1, read only
- Brand
- Sungrow
- Last updated
Registers (1)
1 read, 0 write
| Name | Unit | Access | Address (Hidden until you enter your email) | Function (hidden) | Type (hidden) |
|---|---|---|---|---|---|
| power | W | Read |
Loading registers…
Send your device list
If a device is not in the library yet, we build the template for free as soon as we have the register data.
Use cases
- Monitor live PV generation power to verify that solar yield matches expected output for the installation size.
- Track daily PV power trends in the ModbusCloud portal to detect module soiling or shading that reduces yield.
- Alert on sustained low PV power during daylight hours to identify inverter communication or generation faults early.
- Compare PV power readings against household load data to calculate and report self-consumption rates over time.
- Verify that PV power reported by the iHomeManager stays consistent after firmware updates or iHM replacements.
Installation
Enable 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.
Connect 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.
In 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.
After 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
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.
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.
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.
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.
Want to see how it works?
