Sungrow protocol integration
ZenovaConnect integrates Sungrow devices via iSolarCloud OpenAPI, normalizes fields, and pushes to your channel.
Integration details
- API source
- iSolarCloud OpenAPI
- Category
- 逆变器
- Auth method
- api-key
- Data resolution
- 5min
- Downlink control
- Yes
- Applied at
- 2024-03
- Production since
- 2024-Q3
支持遥控开关 + 有功无功调节
Production observations
Production memory: iSolarCloud has relatively complete docs, with API Key + signed-request auth (signature + Content-MD5 + Date synchronization). The easiest trap is units: some fields (like dayEnergy) return as "kWh × 10" — needs manual division. We once missed this and the night-shift dashboard numbers were 10x. A subset of SKUs supports downlink control (on/off, power capping) — only on specific models.
Field mapping
| Vendor field | BaseData field | Note |
|---|---|---|
| ps_id | PlantId | Plant ID |
| ps_key | InverterSN | Device key |
| today_energy | EDay | Returned as kWh × 10 — divide by 10 |
| total_energy | ETotal | kWh |
| total_active_power | PowerACOutputActive | kW |
| internal_temperature | Temperature | Celsius |
| grid_frequency | FrqAC | Hz |
| grid_voltage_uab | UAC1 | V · three-phase split |
| current_a | IAC1 | A · three-phase split |
| fault_code | AlertArray | Maps to unified alarm array |
Integration gotchas
- Some fields use 'kWh × 10' units — needs manual division; we once missed this and dashboard numbers 10x'd
- API Key + Content-MD5 + Date signature scheme; clock drift causes 401 (±15 min tolerance)
- Downlink control only on specific SKUs — verify device model list before integration
- Rate limit 2 req/s — large-fleet plants require batching + caching
✓ INTEGRATED IN ZENOVACONNECT
Production integration since 2024-Q3 · source iSolarCloud OpenAPI
Field observations
We documented 9 vendor integrations in detail. This brand is covered.
Read the article →Ready to integrate Sungrow?
Onboard once, then field normalization, API revision tracking, and alarm semantics stay handled.