Zhongxin protocol integration
ZenovaConnect integrates Zhongxin devices via 中鑫数字化平台 OpenAPI V2.0, normalizes fields, and pushes to your channel.
Integration details
- API source
- 中鑫数字化平台 OpenAPI V2.0
- Category
- 逆变器
- Auth method
- api-key
- Data resolution
- 5min
- Downlink control
- No
- Applied at
- 2024-Q4
已拿到 OpenAPI V2.0 文档,对接进行中
Production observations
OpenAPI V2.0 with HmacSHA256 six-header signing (timestamp + nonce + apiKey + secretKey + path + body). Uses a "point-driven" model — each data point is defined independently, organized into 11 collection groups (power, energy, env, alarm, etc.). Point-driven gives fine granularity control but increases integration work — every point's field mapping needs explicit definition upfront.
Field mapping
| Vendor field | BaseData field | Note |
|---|---|---|
| stationCode | PlantId | Plant code |
| deviceCode | InverterSN | Device code |
| power.activeToday | EDay | kWh · dotted point path |
| power.activeTotal | ETotal | kWh |
| power.activeNow | PowerACOutputActive | kW |
| env.tempInner | Temperature | Celsius |
| alarm.list | AlertArray | Array |
Integration gotchas
- Point-driven model is upfront-heavy — all point mappings must be defined before integration
- 11-group naming convention must be memorized (power / energy / env / alarm, etc.)
- Six-header signature (including path + body) is complex — first-time debugging is hard
- No public changelog — field changes must be proactively requested
⏳ ZENOVACONNECT INTEGRATION IN PROGRESS
API docs in hand, integration in progress · source 中鑫数字化平台 OpenAPI V2.0
Field observations
We documented 9 vendor integrations in detail. This brand is covered.
Read the article →Zhongxin integration — request priority
We can prioritize. Tell us your timeline and device scale.