Sigenergy protocol integration
ZenovaConnect integrates Sigenergy devices via Sigenergy Northbound API, normalizes fields, and pushes to your channel.
✓ Production
Integration details
- API source
- Sigenergy Northbound API
- Category
- 逆变器
- Auth method
- api-key
- Data resolution
- 5min
- Downlink control
- No
- Applied at
- 2024-Q4
- Production since
- 2024-Q4
光储一体机平台
Production observations
Sigenergy Northbound API designed around Modbus-TCP over HTTPS. The doc is image-heavy with limited text — many key parameters need clarification through direct engineering contact with the vendor. Best suited for integrated "storage + inverter" devices (Sigenergy's core product). Slight over-engineering for pure-inverter scenarios.
Field mapping
| Vendor field | BaseData field | Note |
|---|---|---|
| plantId | PlantId | Plant ID |
| deviceId | InverterSN | Device ID |
| dailyEnergy | EDay | kWh |
| totalEnergy | ETotal | kWh |
| activePower | PowerACOutputActive | kW |
| batterySoc | (储能专属字段) | Percentage · battery SoC |
| alarmList | AlertArray | Array |
Integration gotchas
- Doc is image-heavy — key parameters require direct engineering contact with the vendor
- Integrated storage devices include SoC and charge/discharge fields not yet covered by BaseData — extension needed
- Modbus-TCP over HTTPS design differs from traditional REST/JSON — first-integration learning curve
✓ INTEGRATED IN ZENOVACONNECT
Production integration since 2024-Q4 · source Sigenergy Northbound API
Field observations
We documented 9 vendor integrations in detail. This brand is covered.
Read the article →Ready to integrate Sigenergy?
Onboard once, then field normalization, API revision tracking, and alarm semantics stay handled.