Goodwe protocol integration
ZenovaConnect integrates Goodwe devices via 固德威国内 OpenAPI 1.0, normalizes fields, and pushes to your channel.
Integration details
- API source
- 固德威国内 OpenAPI 1.0
- Category
- 逆变器
- Auth method
- api-key
- Data resolution
- 5min
- Downlink control
- No
- Applied at
- 2024-04
- Production since
- 2024-Q4
户用 + 商用全覆盖,下行控制规划中
Production observations
SEMS Portal domestic OpenAPI v1.0.1.2. Account + password exchanged for a 2-hour token; strict tenant isolation (each customer account sees only its own plants). No 5-minute realtime endpoint — finest historical granularity is 15 minutes. Customers needing realtime monitoring need to align expectations upfront. Timezone is per-plant dynamic — must be looked up via device metadata second query.
Field mapping
| Vendor field | BaseData field | Note |
|---|---|---|
| powerstation_id | PlantId | Plant ID |
| sn | InverterSN | Device SN |
| eday | EDay | kWh |
| etotal | ETotal | kWh |
| pac | PowerACOutputActive | W (note: W, not kW) |
| tempperature | Temperature | Note vendor typo; Celsius |
| fac | FrqAC | Hz |
| vac1, vac2, vac3 | UAC1, UAC2, UAC3 | V · three-phase |
| iac1, iac2, iac3 | IAC1, IAC2, IAC3 | A · three-phase |
Integration gotchas
- No 5-min endpoint — finest realtime is 15 min; manage realtime-monitoring expectations upfront
- Timezone is per-plant dynamic — requires a metadata lookup
- pac unit is W not kW — easy to confuse with other vendors
- Vendor field 'tempperature' has a typo — pin the mapping in the adapter layer
✓ INTEGRATED IN ZENOVACONNECT
Production integration since 2024-Q4 · source 固德威国内 OpenAPI 1.0
Field observations
We documented 9 vendor integrations in detail. This brand is covered.
Read the article →Ready to integrate Goodwe?
Onboard once, then field normalization, API revision tracking, and alarm semantics stay handled.