Hikvision protocol integration
ZenovaConnect integrates Hikvision devices via 海康威视设备 API, normalizes fields, and pushes to your channel.
Integration details
- API source
- 海康威视设备 API
- Category
- 摄像头
- Auth method
- api-key
- Data resolution
- 5min
- Downlink control
- No
- Applied at
- 2024-Q4
- Production since
- 2024-Q4
ZenovaConnect 不止接入逆变器 · 摄像头数据也可走同一通道
Production observations
Hikvision cameras are the "non-inverter" proof point of our BaseData integration layer. Same delivery channels (Webhook / Kafka / MQTT), same unified schema, same permission model — only the `deviceType` field changes from "inverter" to "camera". The integration value lies in unifying on-site monitoring with the plant dashboard — device video streams stop being a separate system. Event-triggered scenarios (inverter alarm → associated camera snapshot) are a common pattern.
Field mapping
| Vendor field | BaseData field | Note |
|---|---|---|
| deviceSerial | InverterSN | Reuses InverterSN field name |
| channelNo | (扩展字段 channelNo) | Camera channel · camera-only |
| alarmType | AlertArray | Motion / boundary / offline |
| snapshotUrl | (扩展字段) | Event-triggered snapshot URL |
Integration gotchas
- deviceType differs from inverter; field set diverges — BaseData extensions are needed
- Hikvision ISUP protocol is proprietary; credential flow differs from inverter cloud APIs — adapter is separate
- Realtime video streams are out of scope; only events + metadata flow through this pipeline
- Customers with centralized Hikvision NVR deployments must decide: ZenovaConnect → device direct, or via NVR
✓ INTEGRATED IN ZENOVACONNECT
Production integration since 2024-Q4 · source 海康威视设备 API
Field observations
We documented 9 vendor integrations in detail. Useful comparison for this brand.
Read the article →Ready to integrate Hikvision?
Onboard once, then field normalization, API revision tracking, and alarm semantics stay handled.