ZenovaConnect
Back to full matrix

Huawei protocol integration

ZenovaConnect integrates Huawei devices via FusionSolar / SmartPVMS 北向接口, normalizes fields, and pushes to your channel.

✓ Production

Integration details

API source
FusionSolar / SmartPVMS 北向接口
Category
逆变器
Auth method
oauth2
Data resolution
5min
Downlink control
Yes
Applied at
2024-02
Production since
2024-Q3

覆盖商用 + 户用 + 储能整线

Production observations

One of the earliest vendors we integrated (Q1 2024). FusionSolar OpenAPI v2 has complete docs, consistent field naming, and changelog-tracked revisions. Biggest pitfall: a specific model's EDay (daily energy) unit silently changed from kWh to kWh × 10, making dashboard numbers 10x. Fix cost: 6 months of historical data resent + customer trust repair + monitoring rules updated to enforce unit verification. Alarm code dictionary is deep — 3-4 weeks to cover completely. OAuth2 credentials issued via business process; tokens are short-lived and require retry + auto-refresh logic.

Field mapping

Vendor fieldBaseData fieldNote
stationCodePlantId1:1
devSnInverterSN1:1, requires stationCode context
dayEnergyEDaykWh (note: unit was once silently changed to ×10)
totalEnergyETotalCumulative kWh
invtActivePowerPowerACOutputActivekW
tempInsideTemperatureCelsius
gridFreqFrqACHz
vGridPhaseAUAC1V · three-phase split
iGridPhaseAIAC1A · three-phase split
alarmsAlertArrayArray — needs alarm-code mapping

Integration gotchas

  • API minor versions 2-4 times/year — full test suite re-run + changelog cross-reference each time
  • EDay unit silently changed from kWh to kWh×10 with no changelog — we now enforce unit verification in monitoring
  • Alarm code dictionary is deep — 3-4 weeks to map all vendor alarms to BaseData's AlertArray
  • OAuth2 tokens are short-lived — retry + auto-refresh required; credential rotation every 6-12 months

✓ INTEGRATED IN ZENOVACONNECT

Production integration since 2024-Q3 · source FusionSolar / SmartPVMS 北向接口

Field observations

We documented 9 vendor integrations in detail. This brand is covered.

Read the article

Ready to integrate Huawei?

Onboard once, then field normalization, API revision tracking, and alarm semantics stay handled.