Hey @Alex_R I have a new version 2026.8.3
Hi Brian,
Thanks for the update.
Unfortunately when trying to connect the doorbell I get the following error upon clicking on “test connection” (see image below). The IP, username and password are correct and working with the other HikVision app (I can see my doorbell live video in there). The doorbell is not on NVR like the rest of my cameras. Not sure what the error means.
Thanks!
Why I have the problem to see the camera? I hear the cam but it is black. Also with the dashboard app from you. I have seen heer online that it is a iPhone, iPad problem with homey.
When someone can see the cam and have an Apple device, let me know how. Thank you.
Ive been testing this and works well. Ive added my NVR which shows my 8 cameras and I can see a live feed from them.
How do I say get a snapshot from a camera and send it to my phone I don’t see a flow card to do this? Thanks
Thanks for testing and for confirming that all eight NVR channels and their live feeds work.
I have added the snapshot Flow functionality in test version 2026.8.6, which is available now:
The motion, line-crossing, intrusion and doorbell triggers now provide a Snapshot image tag for the channel that caused the event. You can use that tag in Homey’s image-notification action to send the image to your phone.
For a manually requested snapshot, Advanced Flow now has a Hikvision action named Take a snapshot. Select your NVR, enter the camera channel number (1–8 in your case), and use the returned Snapshot tag in the next image-notification card.
The manual action is available in Advanced Flow because Homey only supports output tags from Then cards there. The Snapshot tag supplied directly by an event trigger can also be used in a standard Flow.
Please let me know whether the channel numbering and image notification work as expected with your NVR.
83
Thanks , Works perfectly
Ik blijf het vreemd vinden. Heb nu al een paar keer de app in Homey Pro geplaatst en ik krijg geen directe beelden op mijn iPhone en/of iPad. Als ik niet via de app bekijk maar via browser dan zie ik wel direct beeld. Blijf dat toch vreemd vinden en ik zie het anders niet.
Hi, thank you very much for the Hikvision app. I have a door station (camera with a doorbell). The addition was successful, the preview and livestream work. Only the notification when pressing the doorbell does not work, even though I used flow. I have a Hikvision DS-KD8003-IME1(B)/Flush DS-KD8003-IME1(B)/Flush | Domovní videotelefony - Hikvision, Commax | EUROALARM Could something be done about it? Thank you very much.
Hi,
Just wanted to follow up on this. I managed to connect the doorbell by doing exactly the same thing I tried a few days ago. I’m not sure whether the app was updated or something else changed, but it’s working now.
Thanks.
Hey @Mithrandir86 I updated the app vo 2026.8.7
Update 2026.8.7
- Improved video-doorbell detection with the official Hikvision ISAPI call-status fallback
- Added a privacy-safe diagnostic bug report under Repair device
- Unknown ISAPI event types are recorded safely to help diagnose model- and firmware-specific behaviour
- Existing
CallButtonPressdetection remains available and duplicate doorbell triggers are suppressed
This is excellent. Can you expose Region Entrance Detection?
Hi @Monell_Page,
Region Entrance Detection is now available in Test version 2026.8.9.
It includes:
- separate start and stop Flow triggers
- a Snapshot image tag on the start trigger
- live device status and Insights
- a Flow condition
- activation of the standard Homey camera tile and zone
Please enable Notify Surveillance Center for Region Entrance Detection in the Hikvision configuration. Support still depends on the camera model and firmware. If the event does not arrive, please create a privacy-safe bug report through Repair device and share it here.
Thank you! Region Entrance Detection work perfectly, but I learned that I also need Region Exiting Detection for my flow to work properly. Would it be possible to add this to a future version?
Hi @Monell_Page,
Region Exiting Detection has now been added to the upcoming Test version 2026.8.10.
It mirrors the Region Entrance support and includes:
- separate start and stop Flow triggers
- a Snapshot image tag on the start trigger
- live device status and Insights
- a Flow condition
- activation of the standard Homey camera tile and zone
Please also enable Notify Surveillance Center for Region Exiting Detection in the Hikvision configuration. Version 2026.8.10 has passed the app tests and Homey publish validation and will be included in the next Test release.
Hi Brian,
Follow-up on my DS-KD8003-IME1(B)/Flush (FW V2.2.76), test version 2026.8.10. I spent an evening testing this properly, so here is everything in one place.
ISAPI is non-functional on this firmware, independently of authentication.
| Endpoint | Auth prompt | Response |
|---|---|---|
/ISAPI/Security/userCheck |
yes | statusCode 3 “Device Error” |
/ISAPI/System/deviceInfo |
no | statusCode 3 “Device Error” |
/ISAPI/VideoIntercom/callStatus |
no | statusCode 3 “Device Error” |
/ISAPI/System/status |
no | statusCode 4 “Invalid Operation” (errorCode 1073741830) |
The important detail: userCheck does trigger the auth prompt, but returns a byte-identical “Device Error” whether I enter the correct password or a deliberately wrong one. The handler fails before credentials are ever evaluated. System/status returning “Invalid Operation” confirms the device does distinguish unsupported endpoints from endpoints that exist but return nothing — it is not blanket-failing everything. All tested in a fresh incognito session.
The device is otherwise healthy: web UI, live view, door release and Hik-Connect all work, and it survived a reboot.
What would help in the app
-
Availability appears to be based on
deviceInfo. On this model that call always fails, so the device drops to unavailable and reconnects in a loop. If a failing optional probe were non-fatal, the device would stay usable for live view and door release. Note that switching to a different endpoint won’t help — the whole layer is dead. -
My device reports
hik_type: VISbut now carrieshik_alarm_region_entranceandhik_alarm_region_exiting, added in 2026.8.9/8.10. An intercom has no region detection; skipping camera-only capabilities for VIS devices may also help.
On the doorbell trigger — I don’t think this is fixable from your side
I went through the entire config tree on the door station:
- Network → Advanced contains only FTP. No HTTP Listening, no Alarm Server.
- Event Linkage offers only Major Type “Device Event” (→ Tampering Alarm) and “Door Event” (→ Door Open Timed Out). No call or doorbell event.
- Intercom → I/O Settings: Output1 and Output2 both offer “Electric Lock” as the only function, so no relay can be linked to a call.
- The door station is not exposed via ONVIF, and my NVR offers no Smart Event on its channel.
So on this firmware there is no local path by which the button press leaves the device.
One idea, not a request: the call does reach Hik-Connect reliably enough that I get a proper ring notification on my phone with accept/decline. If a cloud path is ever worth exploring for intercoms where local ISAPI is dead, this model would be a candidate — though I understand the downsides of an unofficial API.
Happy to test any build. Thanks for the work you’ve put into this app.
To be clear about the impact: on earlier versions the device stayed connected and I had a working camera stream from the door station in Homey. That regressed — the doorbell trigger never worked, but the live view did, and that’s what I’ve lost.
Hi Mithrandir86,
Your test results identified the regression: the app treated /ISAPI/System/deviceInfo as mandatory for both startup and connection health. Test version 2026.8.11 is now published. For an already recognised VIS door station, a failing ISAPI layer now switches the app to a limited RTSP-only mode, so Live video remains registered and the ISAPI reconnect loop is not started. I also removed Region Entrance/Exiting statuses from VIS devices.
This does not add a doorbell trigger: with no local call event exposed by this firmware, the app has nothing reliable to subscribe to. Please update/restart the app and let me know whether Live view is restored.
Hi Brian,
Thank you for the quick turnaround, and for the explanation — that matches exactly what I was seeing.
**Partial success.** After updating to 2026.8.11 the RTSP Live view did come back and worked for a couple of minutes. I could see the gate camera in Homey again, which is the functionality I had lost.
**But it then degraded.** First “The connection is temporarily unavailable. Retrying automatically (2/3)”, then “Device unavailable — Invalid username or password”. Shortly after that **my entire Homey froze** and only recovered once I disabled the app.
The freeze is the part I’d flag. Whatever happens after the RTSP stream drops seems to block or loop hard enough to take the whole hub down — so it may not be the ISAPI reconnect loop you removed, but something on the RTSP side.
**One caveat on the 401:** earlier that day I hammered the door station with a lot of manual ISAPI requests from a browser, including deliberately wrong passwords on Security/userCheck. A Hikvision Illegal Login Lock on the device could plausibly explain the “Invalid username or password”. So the 401 may well be my own doing. The freeze, though, looks like something the app should survive regardless of why authentication fails.
I’ll retest tomorrow once any lockout has expired and report back with a clean result.
And understood on the doorbell trigger — I reached the same conclusion after going through the entire config tree. No local call event leaves this firmware by any route. Not your problem to solve.
Thanks again for acting on this so quickly.
