Yuexiang Solar protocol integration
ZenovaConnect integrates Yuexiang Solar devices via 悦享 Solar 数据转发接口 v2.0.0, normalizes fields, and pushes to your channel.
Integration details
- API source
- 悦享 Solar 数据转发接口 v2.0.0
- Category
- 逆变器
- Auth method
- api-key
- Data resolution
- 5min
- Downlink control
- No
- Applied at
- 2024-Q4
已拿到数据转发接口说明书 v2.0.0
Production observations
Yuexiang Solar (Sineng Electric) data-forwarding API v2.0.0 (domestic standard edition, released 2024-11). We have the full integration doc; integration is in progress. Architecture is notable: realtime data flows through Aliyun Lightweight Message Queue (SMQ, formerly MNS) — third-party systems act as queue consumers and pull periodically, not via passive Webhook delivery. Our side must run an SMQ SDK consumer (Java/Python/Go available). The lightweight query API is REST over HTTPS with an `sn-sign` token header; rate-limited to 30 req/min. Field structure is deeply nested: top-level `Inverters` array, each inverter contains `pv_mppt`, `pv_string`, `ac` sub-lists (one object per MPPT / per phase) — needs flattening on the BaseData side.
Field mapping
| Vendor field | BaseData field | Note |
|---|---|---|
| stationCode | PlantId | Plant ID |
| Inverters[].isn | InverterSN | Inverter SN |
| e_today | EDay | kWh · daily energy |
| e_total | ETotal | kWh · cumulative energy |
| pac | PowerACOutputActive | W · AC active power |
| rac | PowerACOutputReactive | Var · AC reactive power |
| ac[].u | UAC1, UAC2, UAC3 | V · per-phase AC voltage (list) |
| ac[].i | IAC1, IAC2, IAC3 | A · per-phase AC current (list) |
| ac[].fre | FrqAC | Hz · grid frequency |
| temp | Temperature | Celsius · internal temperature |
| warning[].w | AlertArray | Alarm code array — absence == recovered |
| communStatus | (状态字段) | 1 online / 2 offline / 4 unknown |
Integration gotchas
- Realtime data flows via Aliyun SMQ queue, not webhooks — our side must run a queue consumer and respect SMQ flow-control
- Field structure is deeply nested (Inverters[].pv_mppt[].u etc) — BaseData side needs flattening logic
- Alarm mechanism uses 'absence of code == recovered' — no explicit recovery event; we maintain an in-memory alarm state machine
- Query API rate-limited to 30 req/min — paginated plant-list queries at scale need throttling
- Queue messages discarded after 4 days unconsumed — consumer downtime over 4 days creates history gaps
⏳ ZENOVACONNECT INTEGRATION IN PROGRESS
API docs in hand, integration in progress · source 悦享 Solar 数据转发接口 v2.0.0
Field observations
We documented 9 vendor integrations in detail. Useful comparison for this brand.
Read the article →Yuexiang Solar integration — request priority
We can prioritize. Tell us your timeline and device scale.