Monitor and control your Sigenergy Energy Storage System (ESS) from Home Assistant.
- UI‑Driven Setup with DHCP discovery of inverters and chargers
- Dynamic Device Management (Plants, Inverters, AC/DC Chargers)
- Real‑Time Metrics for power flows, energy statistics, SoC/SoH
- Control Capabilities for EMS (energy management system) work modes and more
- Configurable update interval in three update frequencies for faster updates
Take your setup further with community add-ons and tools:
More add-ons and enhancements are coming; stay tuned!
- Sigenergy ESS firmware
SPC109
or newer is required starting with versionv1.1.0
of the integration. If your device runs older firmware and does not auto-update, upgrade the firmware or use a previous integration release until you have updated the firmware. - Home Assistant at least version
2025.2
. - Sigenergy ESS with Modbus‑TCP enabled by your installer. And preferably confirmed with a screenshot of your
DeviceID
. If using an AC Charger, that will have the id1
and the inverter has to be set to a higher ID, for example2
. - Preferably assign a static IP to your Sigenergy device in your router to ensure it always receives the same IP address.
The Home Assistant Community Store (HACS) is a custom integration that provides a UI to manage custom elements such as Sigenergy ESS in Home Assistant. You first need to install and configure it before following these instructions below.
- Go to HACS > Integrations in Home Assistant
- Search and install Sigenergy ESS Integration
- Restart Home Assistant
- Download the latest
.zip
from the Releases page - Extract and copy
custom_components/sigen
into your HAcustom_components/
folder - Restart Home Assistant
Central Plant entry groups devices by Host/IP and Port where the Port is by default 502
and the IP is the one of the first Inverter.
Plant (IP:Port)
├─ Inverter 1 (ID 2)
│ └─ DC Charger (via Inverter 2)
├─ Inverter 2 (ID 3)
└─ AC Charger (ID 1) ** Is 1 by default and very hard to change **
- Navigate to Settings > Devices & Services
- If your Sigenergy device is discovered automatically on the network, it will appear under Discovered.
- If not discovered, try unplugging and replugging the network cable of your Sigenergy system.
- If discovery still fails, see the Troubleshooting section below.
Note
Controls are read-only by default. To enable control features, you must explicitly activate them in the integration configuration and allow them in Home Assistant. This precaution helps prevent unintended changes or adverse effects.
- Navigate to Settings > Devices & Services > Add Integration
- Search for Sigenergy
- If discovered, click Configure; otherwise select manually
- Enter Host IP, Port (default 502), and first Device ID
- Add additional Inverters/Chargers via the same Plant entry
- Navigate to Settings > Devices & Services.
- Find your Sigenergy integration entry and click Configure.
- From the configuration menu, you can:
- Adjust Plant settings (e.g., read-only, refresh intervals).
- Modify settings for individual Inverters or Chargers.
Note
While it is technically possible to assign different IP addresses and ports to devices, it is not advised. For best results and more reliable operation, all devices within a plant should use the same IP address and port.
- Navigate to Settings > Devices & Services.
- Select the Sigenergy integration and click Add Device.
- Follow the prompts to add extra inverters, chargers, or a new plant.
- Plant Entities: active/reactive power, PV power, SoC, grid flows, EMS mode
- Inverter Entities: MPPT metrics, battery SoC/SoH, phase data
- AC Charger: charging power, total energy, system state
- Controls: EMS work modes are exposed via
select
entities, and optionalbutton
/switch
controls are available
Note
Controls are read-only by default unless explicitly enabled in the integration configuration.
alias: "Notify on Low Battery"
trigger:
- platform: state
entity_id: sensor.plant_battery_soc
to: "<20"
action:
- service: notify.mobile_app
data:
title: "Battery Low"
message: "SoC dropped below 20%"
- Ensure your installer tapped SAVE after enabling Modbus‑TCP on your device.
- Verify IP and firewall settings.
- Ensure again Modbus‑TCP is enabled on your ESS.
- Check Home Assistant logs for
sigen
errors.
Contributions welcome!
- Fork the repo and create a branch
- Add tests under
tests/components/sigen/
- Follow Home Assistant coding and config‑flow patterns
- Submit a Pull Request to this repository