Ginlong Solis protocol integration
ZenovaConnect integrates Ginlong Solis devices via 锦浪云平台 API V2.0, normalizes fields, and pushes to your channel.
✓ Production
Integration details
- API source
- 锦浪云平台 API V2.0
- Category
- 逆变器
- Auth method
- signed-request
- Data resolution
- 5min
- Downlink control
- Yes
- Applied at
- 2024-05
- Production since
- 2024-Q4
HMAC 签名认证
Production observations
Solis Cloud API V2.0 uses HmacSHA1 + Content-MD5 + Date signature with ±15 min clock tolerance. Alarm schema isn't stable — we recommend normalization: pass-through the vendor alarm and additionally provide a parsed BaseData AlertArray representation. Supports on/off downlink control, but field coverage varies by model.
Field mapping
| Vendor field | BaseData field | Note |
|---|---|---|
| stationId | PlantId | Plant ID |
| sn | InverterSN | Device SN |
| eToday | EDay | kWh |
| eTotal | ETotal | kWh |
| pac | PowerACOutputActive | W |
| temperature | Temperature | Celsius |
| fac | FrqAC | Hz |
| alarmList | AlertArray | Schema unstable — normalize |
Integration gotchas
- HmacSHA1 + Date signature — 401 if clock drift exceeds ±15 min
- Alarm schema is unstable — version changes aren't pre-announced; normalization layer protects downstream
- Rate limit 2 req/s — large fleets need batching
- Weather (EPM) and meter data live on different endpoints — manage separately
✓ INTEGRATED IN ZENOVACONNECT
Production integration since 2024-Q4 · source 锦浪云平台 API V2.0
Field observations
We documented 9 vendor integrations in detail. This brand is covered.
Read the article →Ready to integrate Ginlong Solis?
Onboard once, then field normalization, API revision tracking, and alarm semantics stay handled.