Sigenergy Sigen Hybrid (pv)
The Sigenergy Sigen Hybrid is a residential and commercial hybrid solar inverter that combines PV generation and battery storage management in a single unit. This template connects to the Sigen Hybrid, Sigen PV Max, and SigenStore EC over Modbus TCP and reads the inverter active power register, giving your portal a live view of generation output. Use it to track production trends, build export reports, and feed energy-balance dashboards without additional hardware.
- Protocol
- Modbus TCP
- Connection
- Ethernet, Modbus TCP
- Registers
- 1, read only
- Brand
- Sigenergy
- Compatible models
- Sigen Hybrid · Sigen PV Max · SigenStore EC
- 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 from the Sigen Hybrid to verify system output against forecast irradiance.
- Track daily and seasonal power output trends on the Sigen PV Max to detect performance degradation early.
- Alert on unexpected drops in active power from the SigenStore EC to identify shading or inverter faults.
- Compare power readings across multiple Sigenergy sites in a single ModbusCloud multi-site overview.
- Report generation data from the Sigen Hybrid for feed-in tariff reconciliation or energy audit submissions.
Installation
Enable Modbus TCP on the inverter: open the mySigen app, go to the Device panel, enter the inverter settings, turn on the Modbus TCP Server Enable switch, and save.
Connect the Sigenergy inverter to the same LAN as the ModbusCloud Gateway using a standard Ethernet cable into the inverter's Fast Ethernet port; the device listens on TCP port 502.
In the ModbusCloud portal, add your Gateway, import the Sigenergy Sigen Hybrid (pv) template, and assign the correct Modbus slave address (1 to 246) that matches the address configured in the mySigen app.
Verify the connection by checking the live value of the power register in the portal; a non-zero reading during daylight hours confirms successful polling.
Things to watch for
Modbus TCP is enabled but the portal shows no data. Why?
Confirm the inverter's IP address is reachable from the ModbusCloud Gateway on port 502. The inverter must be on the same LAN segment. If a firewall or VLAN separates them, port 502 TCP must be explicitly allowed. Also verify the slave address in the portal matches the one set in the mySigen app.
The power register returns zero even when panels are producing. What is wrong?
Check that the Modbus TCP Server Enable switch is saved and still active in the mySigen app, as it can revert after a firmware update. Also confirm you are polling slave address 247 for plant-level data or the individual inverter's slave address for device-level data, as mixing these returns zeros or errors.
Why does register 30035 return a large negative number at night?
The power register is a signed int32. A negative value at night is normal if the inverter reports a small standby draw or measurement offset. Treat values near zero as idle, and apply a threshold in your alert rule rather than treating any negative reading as a fault.
Modbus stops responding after a few hours. What should I check?
Sigenergy inverters can drop the Modbus TCP connection if the polling interval is too aggressive or if the connection is not cleanly closed between requests. Set the ModbusCloud Gateway poll interval to at least 10 seconds and ensure the TCP session is closed after each transaction to avoid exhausting the inverter's connection slots.
Want to see how it works?
