APsystems protocol integration
ZenovaConnect integrates APsystems devices via APsystems OpenAPI v1.6, normalizes fields, and pushes to your channel.
Integration details
- API source
- APsystems OpenAPI v1.6
- Category
- 逆变器
- Auth method
- api-key
- Data resolution
- 5min
- Downlink control
- No
- Applied at
- 2024-Q4
- Production since
- 2024-Q4
组件级 / 微逆数据
Production observations
Apsystems OpenAPI v1.6 (English docs). HmacSHA256/SHA1 five-header signing scheme (timestamp + nonce + access_key + secret_key + signed body) — the signature scheme itself is robust. No 5-minute endpoint — only hourly / daily / monthly / yearly aggregation. Monitoring customers need to interpolate or pick another vendor. Accounts close after 6 months of inactivity — credential rotation needs proactive pings.
Field mapping
| Vendor field | BaseData field | Note |
|---|---|---|
| systemId | PlantId | System ID |
| ecuId | InverterSN | ECU = micro-inverter gateway |
| energyDay | EDay | kWh · hourly aggregation |
| energyTotal | ETotal | kWh |
| power | PowerACOutputActive | W · hourly average |
| temperature | Temperature | Celsius |
| alerts | AlertArray | code + message |
Integration gotchas
- No 5-min endpoint — finest granularity is hourly; manage realtime-monitoring expectations
- Accounts close after 6 months of inactivity — proactively ping the API to keep alive
- ECU (micro-inverter gateway) concept differs from traditional inverters — model separately
- Five-header signature is complex — expect to debug signature mismatch on first integration
✓ INTEGRATED IN ZENOVACONNECT
Production integration since 2024-Q4 · source APsystems OpenAPI v1.6
Field observations
We documented 9 vendor integrations in detail. This brand is covered.
Read the article →Ready to integrate APsystems?
Onboard once, then field normalization, API revision tracking, and alarm semantics stay handled.