Sofar protocol integration
ZenovaConnect integrates Sofar devices via Solarman Open API v1.1.7, normalizes fields, and pushes to your channel.
Integration details
- API source
- Solarman Open API v1.1.7
- Category
- 逆变器
- Auth method
- signed-request
- Data resolution
- 5min
- Downlink control
- No
- Applied at
- 2024-Q4
- Production since
- 2024-Q4
走 Solarman 开放平台接入
Production observations
Integrated via Solarman OpenAPI v1.1.7. OAuth2 + SHA256 password hashing; tokens live for 2 months — significantly longer than other vendors. Custom Modbus field mapping is flexible — customers can define their own fields in the Solarman dashboard. But this also means field sets can differ per customer, requiring per-customer polling. Rate limits are strict: 300 req/10s + 50 req/min for control operations.
Field mapping
| Vendor field | BaseData field | Note |
|---|---|---|
| stationId | PlantId | Plant ID |
| deviceSn | InverterSN | Device SN |
| generation_today | EDay | kWh |
| cumulative_generation | ETotal | kWh |
| power_output | PowerACOutputActive | W |
| internal_temp | Temperature | Celsius |
| grid_freq | FrqAC | Hz |
| alarms_array | AlertArray | Array with code + description |
Integration gotchas
- OAuth2 tokens last 2 months — long but can fail at version-upgrade boundaries; retry fallback needed
- Custom Modbus field mapping is flexible — per-customer field sets differ; integration must be customer-specific
- Rate limits 300 req/10s + 50 req/min for control — large fleets need batching
- Solarman platform covers multiple vendors (not just Sofar); field naming style isn't fully consistent
✓ INTEGRATED IN ZENOVACONNECT
Production integration since 2024-Q4 · source Solarman Open API v1.1.7
Field observations
We documented 9 vendor integrations in detail. This brand is covered.
Read the article →Ready to integrate Sofar?
Onboard once, then field normalization, API revision tracking, and alarm semantics stay handled.