Sigenergy SigenStor Slave
Monitors energy flow and battery data from SigenStor inverters via Modbus TCP.
This template reads energy flow and battery data from Sigenergy SigenStor inverters (5 to 25 kW) via Modbus TCP. It provides live values for energy export, energy import, battery charge, battery discharge, active power, and PV power. No control registers are included.
- Protocol
- Modbus TCP
- Connection
- Ethernet, Modbus TCP
- Registers
- 6, read only
- Brand
- Sigenergy
- Key readings
- Energy Export · Energy Import · Battery Charge · Battery Discharge · Active Power · PV Power
- Compatible models
- SigenStor 5-25KW
- Last updated
Registers (6)
6 read, 0 write
| Name | Unit | Access | Address (Hidden until you enter your email) | Function (hidden) | Type (hidden) |
|---|---|---|---|---|---|
| Energy Export | kwh | Read | |||
| Energy Import | kwh | Read | |||
| Battery charge | kwh | Read | |||
| Battery discharge | kwh | Read | |||
| Active Power | W | Read | |||
| PV 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 real-time PV power and active power on a live cloud dashboard for each SigenStor installation.
- Track daily energy export and import totals to verify grid feed-in and consumption patterns.
- Create an alert when battery discharge exceeds a defined threshold over a sustained period.
- Compare battery charge and discharge cycles to assess battery health and usage over time.
- Generate weekly or monthly energy reports for customers showing self-consumption and export ratios.
- Add multiple SigenStor slave units to a single project for fleet-level monitoring across sites.
Installation
Enable Modbus TCP on the SigenStor inverter through its local configuration interface or app.
Connect the ModbusCloud Gateway to the same local network as the SigenStor inverter.
Note the IP address of the SigenStor inverter and the Modbus unit ID (slave address) assigned to it.
Import the Sigenergy SigenStor Slave template in the ModbusCloud platform and enter the IP address and unit ID.
Verify that register values for energy export, active power, and PV power appear correctly on the dashboard.
If multiple SigenStor slave units exist on site, repeat the template import for each unit with its own unit ID.
Things to watch for
I cannot connect to the SigenStor via Modbus TCP. What should I check?
Confirm that Modbus TCP is enabled on the inverter. Check that the gateway and the inverter are on the same network subnet. Verify the correct IP address and that the default Modbus TCP port (502) is not blocked by a firewall.
Energy register values seem extremely large. Is this normal?
The energy registers (export, import, battery charge, battery discharge) use uint64 data types spanning four consecutive registers each. Ensure your gateway is reading all four registers and applying the correct byte and word order. A misconfigured word order will produce inflated or nonsensical values.
Active Power shows a negative value. Is the template configured correctly?
Active Power is stored as a signed int32 value. A negative reading typically indicates power flowing in the opposite direction, such as export to the grid. This is expected behaviour.
Can I use this template to control the battery charge or discharge schedule?
No. This template is read only and does not include any writable registers. Battery management must be configured directly on the SigenStor inverter or through the Sigenergy app.
Want to see how it works?
