Kehua protocol integration
ZenovaConnect integrates Kehua devices via 科华接口文档(中文版), normalizes fields, and pushes to your channel.
Integration details
- API source
- 科华接口文档(中文版)
- Category
- 逆变器
- Auth method
- api-key
- Data resolution
- 5min
- Downlink control
- No
- Applied at
- 2024-Q4
已拿到接口文档,对接进行中
Production observations
Kehua Energy Cloud HTTP API V1.02. Login (account + password) returns a token; 3-section payload structure (device metadata + realtime data + historical data) is clearly organized. Historical granularity is 5 minutes; single-day history was only added in June 2024 — older requirements need separate negotiation. Downlink control schema is complete but only available on selected models.
Field mapping
| Vendor field | BaseData field | Note |
|---|---|---|
| stationId | PlantId | Plant ID |
| deviceSn | InverterSN | Device SN |
| dayEnergy | EDay | kWh |
| totalEnergy | ETotal | kWh |
| activePower | PowerACOutputActive | kW |
| inverterTemp | Temperature | Celsius |
| gridFreq | FrqAC | Hz |
| alarmList | AlertArray | Array |
Integration gotchas
- Single-day history was only added June 2024 — earlier integrations need re-negotiation
- Downlink control schema only supported on a subset of models — confirm target SKU before integration
- Token expiry isn't proactively notified — retry on 401
- 3-section payload can be large at scale — streaming processing recommended
⏳ ZENOVACONNECT INTEGRATION IN PROGRESS
API docs in hand, integration in progress · source 科华接口文档(中文版)
Field observations
We documented 9 vendor integrations in detail. This brand is covered.
Read the article →Kehua integration — request priority
We can prioritize. Tell us your timeline and device scale.