Sigenergy SigenStore EC (battery)
The Sigenergy SigenStore EC is a modular LiFePO4 home and small-commercial energy storage controller, compatible with Sigen Hybrid and Sigen PV Max inverters. This template connects over Modbus TCP and reads the plant-level battery state of charge, ESS power flow (charge or discharge direction), and cumulative energy throughput. The writable minimum-SOC setpoint lets an external EMS hold a reserve for backup. With the ModbusCloud Gateway polling these registers, operators gain continuous visibility into storage behaviour across one or multiple sites.
- Protocol
- Modbus TCP
- Connection
- Ethernet, Modbus TCP
- Registers
- 4, read and write
- Brand
- Sigenergy
- Compatible models
- Sigen Hybrid · Sigen PV Max · SigenStore EC
- Last updated
Registers (4)
3 read, 1 write
| Name | Unit | Access | Address (Hidden until you enter your email) | Function (hidden) | Type (hidden) |
|---|---|---|---|---|---|
| power | W | Read | |||
| energy | Wh | Read | |||
| soc | % | Read | |||
| limitsoc | % | Write |
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 battery charge and discharge power to verify the SigenStore EC follows the expected EMS dispatch schedule.
- Track state of charge continuously to detect gradual capacity fade across months of operation.
- Alert on SOC dropping below a defined threshold during evening peak hours to catch grid-import overruns.
- Report cumulative energy throughput over time to validate warranty cycle-count claims for the SigenStore EC.
- Verify that the minimum-SOC setpoint register reflects the value written by your EMS, confirming successful remote control.
Installation
Enable Modbus TCP on the SigenStore EC: open the mySigen app, navigate to the Device panel, select SigenStor Settings, and turn on the Modbus TCP Server Enable switch, then save.
Connect the SigenStore EC to the same LAN as the ModbusCloud Gateway and confirm port 502 is reachable from the Gateway's IP address.
In the ModbusCloud portal, add your Gateway, import the Sigenergy SigenStore EC (battery) template, and set the Modbus unit ID to 247, which is the plant-level address for ESS registers.
Spot-check the integration by reading the SOC register (address 30014) in the portal's live register view and comparing the displayed value, divided by 10, against the percentage shown in the mySigen app.
Things to watch for
SOC values appear ten times too high. What is wrong?
Register 30014 returns SOC scaled by a factor of 10, so a raw value of 750 represents 75.0%. The template applies this scaling automatically. If you are reading the register with a custom tool and see raw values, divide by 10 to obtain the correct percentage.
All registers return errors, but the network connection looks fine.
The ESS plant-level registers on the SigenStore EC are only accessible at Modbus slave address 247. Queries sent to any other unit ID will be rejected. Confirm the unit ID in your ModbusCloud portal is set to 247, and verify that Modbus TCP is enabled in the mySigen app.
The Gateway connects but no live values appear in the dashboard.
Confirm port 502 is open and not blocked by the local router or a VLAN. The SigenStore EC and the ModbusCloud Gateway must be on the same network segment. Also verify the mySigen Modbus TCP Server Enable switch is on and has been saved, as the device will not respond without it.
Is it safe to write to the minimum-SOC setpoint register during normal operation?
Use caution when writing to register 40048. Setting the minimum SOC too high can prevent the battery from discharging and may conflict with the inverter's internal EMS mode. Setting it too low may violate manufacturer recommendations. Always test setpoint changes during low-load periods and confirm the resulting behaviour in the mySigen app before automating writes.
Want to see how it works?
