Hik-Connect
tomasbedrich/home-assistant-hikconnect · v3.1.4
A Home Assistant integration to communicate with Hikvision smart doorbells via Hik-Connect cloud.
In Apple Home through HomeKit Bridge
What HomeKit Bridge makes of each kind of entity this integration creates, read from its source code. A device only gets the ones that apply to it.
| Entity | Shows up as | Note |
|---|---|---|
lock | Lock | Needs its own HomeKit Bridge in accessory mode |
alarm_control_panel | Security system | |
binary_sensor | Sensor (motion, contact, leak, smoke…) | |
sensor | Sensor (temperature, humidity, air quality…) | |
button | Button (as a switch) |
What people report
Hik-Connect cloud integration covers door stations, indoor units and alarm areas; live camera view is not available. Some DS-KH63xx indoor units registered phantom channels before a fix.
- Works1
- Partly works2
- Requested1
| Device | In Home Assistant | In Apple Home | What they said | Source |
|---|---|---|---|---|
| Hikvision DS-KH63xx indoor unit | Works Cloud | Phantom camera-channel devices fixedSaved copySummary - Closes #60, stop registering phantom camera-channel devices (DS-KH63xx indoor units returned ~49 empty entries per device). - Closes #62, skip devices with malformed `lockNum` instead of aborting setup. - May help #54, same filter (no locks → no HA device) prunes camera-channel pollution under intercom devices. NVR / standalone-camera filtering is not included. - New diagnostic entities: local IP, WAN IP, WiFi signal, online, update available, all `EntityCategory.DIAGNOSTIC`, disabled by default, fall back to *unavailable* when the cloud omits the field. IP / signal values are … Excerpt saved from GitHub on 2026-10-23. | PR #68 · 2026-06 | |
| Hikvision DS-KD series outdoor door station | Partly works Cloud | Cloud call status unreliable; ISAPI mode PR closedSaved copyAdd ISAPI-based call status mode for outdoor door stations (DS-KD series) ### Problem The existing `CallStatusSensor` uses `api.get_call_status()` which polls the Hik-Connect cloud API. For many users, particularly those with outdoor door stations like the DS-KD series, this endpoint consistently returns errors and leaves the call status entity permanently unavailable. See the open issues around call status failures. ### Solution This PR adds an alternative call status implementation using the Hik-Connect ISAPI cloud tunnel (`/api/device/isapi`), which proxies ISAPI requests through the cloud … Excerpt saved from GitHub on 2026-10-23. | PR #72 · 2026-07 | |
| Hikvision NVR area management | Partly works Cloud | Not all NVR firmware exposes area API; polled every 30 minSaved copyLimitations: Area status is polled on the coordinator schedule (default 30 min). It is not updated in real-time. After arm/disarm the integration immediately triggers a refresh, so state should update within seconds. updatearea changes the groupid (delete + recreate). The entity re-appears after the next coordinator refresh. Not all NVR firmware versions expose the area API. If no area entities appear, your device may not support area management over the Hik-Connect cloud. Recommendation: Because of how area creation and updates work (requiring entity recreation and polling refreshes), it is … Excerpt saved from the README on 2026-10-23. | README | |
| Hik-Connect cameras live view | Requested Cloud | Cloud live view not implemented; issue open since 2021Saved copyI'm only looking for cloud-based camera stream. My goal is to mirror functionality available through Hik-Connect mobile application. Focusing of local connection, you may be interested in the official integration or this thread. Excerpt saved from GitHub on 2026-10-23. | Issue #6 · 2021-09 |
Gathered from GitHub issues, pull requests, discussions and docs, and from r/homeassistant. These are individual reports, so check the linked thread and the date before you buy.
How it connects
Cloud polling
Goes through the maker’s cloud, asking it for updates every so often. Needs the internet and an account.
Details
| Installs (analytics) | 1,080 (0.15%) |
|---|---|
| GitHub stars | 74 |
| Latest version | 3.1.4 (2026-10-12) |
| Set up in the UI | Yes |
| Maintainers | @tomasbedrich |
Limitations from the README
- Area status is polled on the coordinator schedule (default 30 min). It is not updated in real-time.
- After arm/disarm the integration immediately triggers a refresh, so state should update within seconds.
- updatearea changes the groupid (delete + recreate). The entity re-appears after the next coordinator refresh.
- Not all NVR firmware versions expose the area API. If no area entities appear, your device may not support area management over the Hik-Connect cloud.
- Recommendation: Because of how area creation and updates work (requiring entity recreation and polling refreshes), it is highly recommended to manage your areas in the official Hik-Connect application, unless you specifically need to automate their creation/modification via Home Assistant.
In ReReHome
Whatever HomeKit Bridge shares reaches Apple Home as normal HomeKit accessories behind your Home Assistant bridge, so ReReHome shows and controls them like any other.
Bridges get their own settings page listing the accessories behind them.
