# \[APP\]\[Pro\]\[TEST\] Hikvision SDK v3
**URL:** https://community.homey.app/t/app-pro-test-hikvision-sdk-v3/157226
**Category:** Apps
**Tags:** advancedflow
**Created:** [July 15, 2026, 6:25pm UTC](https://community.homey.app/t/app-pro-test-hikvision-sdk-v3/157226 "2026-07-15T18:25:28Z")
**Posts on this page:** 20
**Page:** 5
### Author:  [@Don\_Buijsen](https://community.homey.app/u/Don_Buijsen)
#### Post date: [August 30, 2026, 12:27pm UTC](https://community.homey.app/t/app-pro-test-hikvision-sdk-v3/157226/84 "2026-08-30T12:27:56Z")
Hi Brian,
Tested 2026.8.18 as requested. I restarted the app, waited more than one minute and then pressed the physical call button. Unfortunately the Flow still did not trigger.
The door station itself remains available and connected. The bug report was created immediately after the test and still reports isapiAvailable: false, polling: false and recovery-unavailable with Invalid username or password.
Full report below:
{ “reportType”: “Hikvision device bug report”, “createdAt”: “2026-08-30T12:26:34.706Z”, “privacy”: { “note”: “Passwords, IP addresses, hostnames and usernames are removed before this report is shown.”, “addressConfigured”: true, “addressHash”: “abee9c3593bc”, “usernameConfigured”: true, “passwordConfigured”: true }, “app”: { “id”: “nl.nobrainer.hikvision”, “version”: “2026.8.18”, “sdk”: 3 }, “driver”: { “id”: “hikvision-camnvr”, “connection”: “local\_isapi” }, “device”: { “idHash”: “da7a357b8194” }, “settings”: { “port”: 80, “rtspPort”: 554, “ssl”: false, “strictTls”: false, “motionHoldSeconds”: 10, “liveStream”: “automatic”, “rtspOnly”: false }, “capabilities”: { “alarm\_motion”: false, “alarm\_tamper”: false, “hik\_alarm\_local”: false, “hik\_alarm\_video\_loss”: false, “hik\_alarm\_line\_crossing”: false, “hik\_alarm\_intrusion”: false, “hik\_type”: “VIS”, “hik\_version”: “V2.2.77”, “hik\_status”: true }, “diagnostics”: { “success”: true, “device”: { “type”: “VIS”, “firmwareVersion”: “V2.2.77”, “connected”: true, “available”: true, “isapiAvailable”: false, “rtspOnlyConfigured”: false }, “videoProfiles”: { “1”: { “streamId”: 102, “codec”: “H.264”, “width”: null, “height”: null, “preference”: “automatic”, “rtspOnly”: true } }, “doorbell”: { “eligible”: true, “supported”: false, “polling”: false, “detection”: “recovery-unavailable”, “lastStatus”: null, “lastChecked”: “2026-08-30T12:26:13.246Z”, “lastError”: “Ongeldige gebruikersnaam of ongeldig wachtwoord.” }, “unhandledEvents”: } }
---
### Author:  [@Brian\_Monninkhof](https://community.homey.app/u/Brian_Monninkhof)
#### Post date: [August 30, 2026, 2:06pm UTC](https://community.homey.app/t/app-pro-test-hikvision-sdk-v3/157226/85 "2026-08-30T14:06:22Z")
Hi Don, version 2026.8.19 is ready for testing:
- Install or update the app: [Hikvision | Homey](https://homey.app/a/nl.nobrainer.hikvision/test/)
- Open the Hikvision device settings.
- Set **Authentication method** to **Basic (forced)**.
- Keep HTTP port **80** , RTSP port **554** , and RTSP-only disabled.
- Save the settings and allow the app to reconnect.
- Press the physical call button and test the Flow again.
- If it still fails, create a new bug report through **Repair device** and post it here.
---
### Author:  [@Don\_Buijsen](https://community.homey.app/u/Don_Buijsen)
#### Post date: [August 30, 2026, 2:36pm UTC](https://community.homey.app/t/app-pro-test-hikvision-sdk-v3/157226/86 "2026-08-30T14:36:28Z")
> [@Brian\_Monninkhof](#):
>
> Don, version 2026.8.19 is ready for testing:
>
> - Install or update the app: [Hikvision | Homey](https://homey.app/a/nl.nobrainer.hikvision/test/)
> - Open the Hikvision device settings.
> - Set **Authentication method** to **Basic (forced)**.
> - Keep HTTP port **80** , RTSP port **554** , and RTSP-only disabled.
> - Save the settings and allow the app to reconnect.
> - Press the physical call button and test the Flow again.
> - If it still fails, create a new bug report through **Repair device** and post it here.
Hi Brian,
Tested 2026.8.19 with Authentication method set to **Basic (forced)**. The physical call button still does not trigger the Flow.
The new authentication diagnostics seem very clear: both /ISAPI/VideoIntercom/capabilities and /ISAPI/VideoIntercom/callStatus?format=json consistently return **401** , but without a WWW-Authenticate header (headerPresent: false, schemes: []).
Browser login and RTSP still work, and the device remains connected/available in Homey.
Full report below:{ “reportType”: “Hikvision device bug report”, “createdAt”: “2026-08-30T14:33:12.827Z”, “privacy”: { “note”: “Passwords, IP addresses, hostnames and usernames are removed before this report is shown.”, “addressConfigured”: true, “addressHash”: “abee9c3593bc”, “usernameConfigured”: true, “passwordConfigured”: true }, “app”: { “id”: “nl.nobrainer.hikvision”, “version”: “2026.8.19”, “sdk”: 3 }, “driver”: { “id”: “hikvision-camnvr”, “connection”: “local\_isapi” }, “device”: { “idHash”: “da7a357b8194” }, “settings”: { “port”: 80, “rtspPort”: 554, “ssl”: false, “strictTls”: false, “authMethod”: “basic”, “motionHoldSeconds”: 10, “liveStream”: “automatic”, “rtspOnly”: false }, “capabilities”: { “alarm\_motion”: false, “alarm\_tamper”: false, “hik\_alarm\_local”: false, “hik\_alarm\_video\_loss”: false, “hik\_alarm\_line\_crossing”: false, “hik\_alarm\_intrusion”: false, “hik\_type”: “VIS”, “hik\_version”: “V2.2.77”, “hik\_status”: true }, “diagnostics”: { “success”: true, “device”: { “type”: “VIS”, “firmwareVersion”: “V2.2.77”, “connected”: true, “available”: true, “isapiAvailable”: false, “rtspOnlyConfigured”: false }, “videoProfiles”: { “1”: { “streamId”: 102, “codec”: “H.264”, “width”: null, “height”: null, “preference”: “automatic”, “rtspOnly”: true } }, “doorbell”: { “eligible”: true, “supported”: false, “polling”: false, “detection”: “recovery-unavailable”, “lastStatus”: null, “lastChecked”: “2026-08-30T14:32:51.762Z”, “lastError”: “Ongeldige gebruikersnaam of ongeldig wachtwoord.” }, “authentication”: { “preference”: “basic”, “activeMode”: “basic”, “recentRequests”: [{ “endpoint”: “/ISAPI/VideoIntercom/capabilities”, “method”: “GET”, “preference”: “basic”, “attempts”: [ { “mode”: “basic”, “statusCode”: 401, “challenge”: { “headerPresent”: false, “schemes”: , “digest”: null } }] }, { “endpoint”: “/ISAPI/VideoIntercom/callStatus?format=json”, “method”: “GET”, “preference”: “basic”, “attempts”: [{ “mode”: “basic”, “statusCode”: 401, “challenge”: { “headerPresent”: false, “schemes”: , “digest”: null } }] }, { “endpoint”: “/ISAPI/VideoIntercom/capabilities”, “method”: “GET”, “preference”: “basic”, “attempts”: [{ “mode”: “basic”, “statusCode”: 401, “challenge”: { “headerPresent”: false, “schemes”: , “digest”: null } }] }, { “endpoint”: “/ISAPI/VideoIntercom/callStatus?format=json”, “method”: “GET”, “preference”: “basic”, “attempts”: [{ “mode”: “basic”, “statusCode”: 401, “challenge”: { “headerPresent”: false, “schemes”: , “digest”: null } }] }, { “endpoint”: “/ISAPI/VideoIntercom/capabilities”, “method”: “GET”, “preference”: “basic”, “attempts”: [{ “mode”: “basic”, “statusCode”: 401, “challenge”: { “headerPresent”: false, “schemes”: , “digest”: null } }] }, { “endpoint”: “/ISAPI/VideoIntercom/callStatus?format=json”, “method”: “GET”, “preference”: “basic”, “attempts”: [{ “mode”: “basic”, “statusCode”: 401, “challenge”: { “headerPresent”: false, “schemes”: , “digest”: null } }] }, { “endpoint”: “/ISAPI/VideoIntercom/capabilities”, “method”: “GET”, “preference”: “basic”, “attempts”: [{ “mode”: “basic”, “statusCode”: 401, “challenge”: { “headerPresent”: false, “schemes”: , “digest”: null } }] }, { “endpoint”: “/ISAPI/VideoIntercom/callStatus?format=json”, “method”: “GET”, “preference”: “basic”, “attempts”: [{ “mode”: “basic”, “statusCode”: 401, “challenge”: { “headerPresent”: false, “schemes”: , “digest”: null } }] }, { “endpoint”: “/ISAPI/VideoIntercom/capabilities”, “method”: “GET”, “preference”: “basic”, “attempts”: [{ “mode”: “basic”, “statusCode”: 401, “challenge”: { “headerPresent”: false, “schemes”: , “digest”: null } }] }, { “endpoint”: “/ISAPI/VideoIntercom/callStatus?format=json”, “method”: “GET”, “preference”: “basic”, “attempts”: [{ “mode”: “basic”, “statusCode”: 401, “challenge”: { “headerPresent”: false, “schemes”: , “digest”: null } }] }, { “endpoint”: “/ISAPI/VideoIntercom/capabilities”, “method”: “GET”, “preference”: “basic”, “attempts”: [{ “mode”: “basic”, “statusCode”: 401, “challenge”: { “headerPresent”: false, “schemes”: , “digest”: null } }] }, { “endpoint”: “/ISAPI/VideoIntercom/callStatus?format=json”, “method”: “GET”, “preference”: “basic”, “attempts”: [{ “mode”: “basic”, “statusCode”: 401, “challenge”: { “headerPresent”: false, “schemes”: , “digest”: null } }] } ] }, “unhandledEvents”: } }
---
### Author:  [@Mithrandir86](https://community.homey.app/u/Mithrandir86)
#### Post date: [August 31, 2026, 6:47pm UTC](https://community.homey.app/t/app-pro-test-hikvision-sdk-v3/157226/87 "2026-08-31T18:47:27Z")
Hi Brian,
Same issue as Don on my DS-KD8003 (FW V2.2.76), app 2026.8.15.
With RTSP-only enabled: doorbell.lastError = “ISAPI disabled by the RTSP-only setting” (expected).
Temporarily disabled RTSP-only to test ISAPI directly — device stayed connected/available (no flapping this time), but VideoIntercom auth fails the same way as Don’s:
doorbell.detection: “recovery-unavailable”
lastError: “Invalid username or password.”
isapiAvailable: false
Credentials are correct — web UI and RTSP login work fine with the same account. Re-enabled RTSP-only afterward.
Just confirming this isn’t isolated to Don’s unit — looks like a shared VideoIntercom auth problem across V2.2.76/77.
---
### Author:  [@Brian\_Monninkhof](https://community.homey.app/u/Brian_Monninkhof)
#### Post date: [August 31, 2026, 8:52pm UTC](https://community.homey.app/t/app-pro-test-hikvision-sdk-v3/157226/88 "2026-08-31T20:52:13Z")
@Mithrandir86 @Don_Buijsen, version 2026.8.20 is now available for testing:
> **[Hikvision | Homey](https://homey.app/en-us/app/nl.nobrainer.hikvision/Hikvision/test/)**
>
> Keep an eye on what matters, live and locally.
- Update the app to **2026.8.20**.
- Set **Authentication method** to **Automatic**.
- Disable **RTSP-only mode**.
- Save the settings and restart the app.
- Wait about one minute, then press the physical call button.
- If the Flow still does not trigger, create a new bug report through **Repair device** and post it here.
I added a Hikvision web-session fallback specifically for the HTTP 401 behaviour reported on firmware V2.2.76 and V2.2.77.
---
### Author:  [@Mithrandir86](https://community.homey.app/u/Mithrandir86)
#### Post date: [September 1, 2026, 2:38pm UTC](https://community.homey.app/t/app-pro-test-hikvision-sdk-v3/157226/89 "2026-09-01T14:38:06Z")
Hi Brian,
Update on my DS-KD8003 (FW V2.2.76): tested 2026.8.20 with Authentication method = Automatic and RTSP-only disabled.
The doorbell Flow now triggers reliably on physical button press, and the device has stayed connected/available with no flapping.
Thanks for the quick fix — much appreciated!
You are great.
---
### Author:  [@Brian\_Monninkhof](https://community.homey.app/u/Brian_Monninkhof)
#### Post date: [September 1, 2026, 6:18pm UTC](https://community.homey.app/t/app-pro-test-hikvision-sdk-v3/157226/90 "2026-09-01T18:18:24Z")
Thank you for testing this thoroughly and for confirming the result, @Mithrandir86. I’m glad to hear that the doorbell Flow now triggers reliably and that the connection remains stable. Your detailed reports helped me pinpoint and fix this firmware-specific authentication issue.
---
### Author:  [@Don\_Buijsen](https://community.homey.app/u/Don_Buijsen)
#### Post date: [September 2, 2026, 9:18am UTC](https://community.homey.app/t/app-pro-test-hikvision-sdk-v3/157226/91 "2026-09-02T09:18:13Z")
Hi Brian,
Just wanted to say a big thank you for all the effort you put into this.
After running version **2026.8.20 for a full day** , I can confirm that the **DS-KV6113-WPE1(C)** is now working reliably. The door station stays available, the physical call button is detected correctly and my Homey Flow triggers every time.
Really appreciated how quickly you picked up the bug reports and kept pushing new test versions until the issue was solved. Great support and a great addition to Homey.
Thanks again!
Don
---
### Author:  [@Don\_Buijsen](https://community.homey.app/u/Don_Buijsen)
#### Post date: [September 2, 2026, 6:28pm UTC](https://community.homey.app/t/app-pro-test-hikvision-sdk-v3/157226/92 "2026-09-02T18:28:35Z")
Hi Brian,
Version 2026.8.20 has been working reliably with my DS-KV6113-WPE1(C), so I have now started looking at some additional automation possibilities.
I have one feature request that might be useful for other Hikvision intercom users as well.
When the physical call button is pressed, the KV6113 starts its normal intercom call. Homey correctly detects the ring state and triggers the “The doorbell was pressed” Flow card.
I tried disabling the actual call by assigning an empty time schedule to “Press Button to Call”. This does stop the call, but it also prevents the ring state from occurring, so Homey no longer detects the button press. The minimum Ring Duration in the KV6113 is 65 seconds, so shortening it in the Hikvision configuration isn’t an option either.
Would it be possible to add a **Then Flow card to end/hang up the current intercom call**?
My intended Flow would be:
Physical button press → Homey detects ring → doorbell Flow triggers → Sonos announcement + snapshot/push notification → Homey immediately hangs up the Hikvision call.
Hikvision ISAPI appears to expose call control through /ISAPI/VideoIntercom/callSignal?format=json with a hangUp command. Since the app already has a working authenticated ISAPI session with the KV6113, I wondered if this could be exposed as a Flow action.
Ideally this would only terminate the call generated by the physical doorbell press. I would still like to be able to open Hik-Connect myself and use live view/two-way audio normally.
Would this be possible with the current implementation?
Thanks again!
Don
---
### Author:  [@Brian\_Monninkhof](https://community.homey.app/u/Brian_Monninkhof)
#### Post date: [September 2, 2026, 8:27pm UTC](https://community.homey.app/t/app-pro-test-hikvision-sdk-v3/157226/93 "2026-09-02T20:27:06Z")
Hi Don,
Thank you for the detailed explanation and clear Flow example. I have added this in test version **2026.9.4** :
- A new **Then** card: **End current intercom call**.
- The app first verifies that the door station supports the hang-up command.
- It only sends the command while the intercom is ringing, so later Hik-Connect live view and two-way audio remain available.
Please install/update the test version: [Hikvision | Homey](https://homey.app/a/nl.nobrainer.hikvision/test/)
Then test this order:
1. **When:** The doorbell was pressed
2. Your Sonos announcement and snapshot/push actions
3. **Then:** End current intercom call
Please let me know whether the DS-KV6113 stops calling immediately. If it fails, please send a new privacy-safe bug report through **Repair device** ; version 2026.9.4 includes the call-control result and error code in that report.
---
### Author:  [@Alex\_R](https://community.homey.app/u/Alex_R)
#### Post date: [September 2, 2026, 11:38pm UTC](https://community.homey.app/t/app-pro-test-hikvision-sdk-v3/157226/94 "2026-09-02T23:38:32Z")
> [@Mithrandir86](#):
>
> The same happens on all my ONVIF cameras — black live video, snapshots still fine. Homey updated its firmware yesterday and everything worked before that, so this looks like a regression in Homey’s video pipeline. Others are reporting it on the forum too. I’ll report it to Athom.
Just wanted to add I have the same issue with all my cameras (not just HikVision) but only on some of my devices. It looks like the “black stream” bug is mostly happening on Qualcomm Snapdragon devices. In my case, out of 6 tablets in my home, the most powerful one (the only one with Snapdragon) can’t display camera video streams unless I set them to substream, which is low quality 720p or even less.
Athom knows about the problem, it’s been going on for months, still nothing done about it.
---
### Author:  [@EdNL](https://community.homey.app/u/EdNL)
#### Post date: [September 3, 2026, 11:25am UTC](https://community.homey.app/t/app-pro-test-hikvision-sdk-v3/157226/95 "2026-09-03T11:25:26Z")
Sorry @Brian_Monninkhof, It’s surprising that I’m only responding now. I was out of action for a while, but I’m already feeling a bit better. That’s why I downloaded your test version just now; my cameras are working and the screen no longer goes black.
It looks good to me, at least initially. I’m quite happy with it!
---
### Author:  [@Don\_Buijsen](https://community.homey.app/u/Don_Buijsen)
#### Post date: [September 3, 2026, 12:28pm UTC](https://community.homey.app/t/app-pro-test-hikvision-sdk-v3/157226/96 "2026-09-03T12:28:55Z")
Hi Brian,
Just tested version 2026.9.4 and I can confirm that it works perfectly on the DS-KV6113-WPE1(C).
The physical button press is detected by Homey, my Sonos announcement and snapshot/push are triggered, and the new **End current intercom call** action immediately terminates the Hikvision call afterwards.
Exactly what I was hoping to achieve. Really nice implementation, especially with the check that only ends the call while the intercom is actually ringing, so normal Hik-Connect use remains unaffected.
Thanks again for picking this up and implementing it so quickly. Much appreciated!
Don
---
### Author:  [@Don\_Buijsen](https://community.homey.app/u/Don_Buijsen)
#### Post date: [September 3, 2026, 1:03pm UTC](https://community.homey.app/t/app-pro-test-hikvision-sdk-v3/157226/97 "2026-09-03T13:03:26Z")
Hi Brian,
Another one for you 🙂. The doorbell is still working perfectly, but I’ve now started testing Line Crossing on my Hikvision NVR.
I configured Line Crossing on **D3 (Front)** directly on the NVR:
- Line Crossing enabled
- Direction A → B
- Human detection only
- Sensitivity 50
- Armed 24/7
The Hikvision side appears to be working correctly. When I physically cross the line, the NVR records an event with:
**Event type: Line Crossing**
It also stores the correct snapshot showing me crossing the line at that exact moment.
In Homey I created a simple Flow:
**When:** Hikvision NVR → Line crossing is detected
**Then:** Send the supplied Snapshot tag as a mobile notification
Unfortunately, the Flow does not trigger.
I initially discovered that my existing NVR was still installed through the older app ID nl.nobrainerhomey.Hikvision, version **2026.8.15**. So, to rule that out, I added the NVR again using the current/new Hikvision test app — the same app installation I’m using successfully for the door station — and changed the test Flow to use this newly added NVR.
The result is the same: the NVR detects and records the Line Crossing event, but Homey does not trigger the Line Crossing Flow card.
I then tried generating a new bug report immediately after reproducing the event. Unfortunately, on the newly added NVR the **Bug report screen remains completely empty** , so I’m unable to provide the diagnostic report from this installation.
NVR details:
- Device: Network Video Recorder
- Firmware: **V4.84.101**
- HTTP: 80
- RTSP: 554
- ISAPI connection works
- Three active camera channels; Front is **D3**
I can provide screenshots of the NVR Line Crossing event/snapshot and the empty bug-report screen if useful.
Thanks again for looking into this!
Don
---
### Author:  [@Marcelo\_Leite](https://community.homey.app/u/Marcelo_Leite)
#### Post date: [September 3, 2026, 2:43pm UTC](https://community.homey.app/t/app-pro-test-hikvision-sdk-v3/157226/98 "2026-09-03T14:43:23Z")
Hi Don\_Buijsen
Could you send me a screenshot of your flow so I can test it here?
---
### Author:  [@Don\_Buijsen](https://community.homey.app/u/Don_Buijsen)
#### Post date: [September 3, 2026, 3:00pm UTC](https://community.homey.app/t/app-pro-test-hikvision-sdk-v3/157226/99 "2026-09-03T15:00:14Z")
---
### Author:  [@Brian\_Monninkhof](https://community.homey.app/u/Brian_Monninkhof)
#### Post date: [September 3, 2026, 8:29pm UTC](https://community.homey.app/t/app-pro-test-hikvision-sdk-v3/157226/100 "2026-09-03T20:29:36Z")
Hi Don,
Thank you for the detailed test and the Flow screenshot. Your Flow is configured correctly. I have published **test version 2026.9.5** because the app already handles the standard `linedetection` event and channel D3, so we need to see what this NVR actually sends to Homey.
This version:
- fixes the empty **Repair device** bug-report screen;
- creates the report automatically;
- records the last twenty privacy-safe ISAPI event details, including event type, status and channel.
Please test again:
1. Update to 2026.9.5: [Hikvision | Homey](https://homey.app/a/nl.nobrainer.hikvision/test/)
2. On the NVR, verify that **Notify Surveillance Center** is enabled as the linkage method for Line Crossing on D3.
3. Cross the line once.
4. If the Flow still does not trigger, immediately open **Repair device** , copy the new report and post it here.
That report should show whether no event reaches Homey or whether firmware V4.84.101 uses a different event name.
---
### Author:  [@EdNL](https://community.homey.app/u/EdNL)
#### Post date: [September 4, 2026, 7:38am UTC](https://community.homey.app/t/app-pro-test-hikvision-sdk-v3/157226/101 "2026-09-04T07:38:11Z")
Hi @Brian_Monninkhof
Sorry, I have been sick and haven’t been able to keep following the entire topic.
I need to correct my message because I can see the live feed on my iMac, but not on my iPad and iPhone. Do I need to do something to make it work, or has that problem not been resolved yet?
Hopefully you can help me with this. Thank you.
---
### Author:  [@J273](https://community.homey.app/u/J273)
#### Post date: [September 5, 2026, 6:24pm UTC](https://community.homey.app/t/app-pro-test-hikvision-sdk-v3/157226/102 "2026-09-05T18:24:31Z")
Ive been using your old app for a while with no issues. Am I best t0 switch over to this new App ID for further updates. Delete my current devices and start a fresh?
Thanks
---
### Author:  [@Brian\_Monninkhof](https://community.homey.app/u/Brian_Monninkhof)
#### Post date: [September 5, 2026, 8:19pm UTC](https://community.homey.app/t/app-pro-test-hikvision-sdk-v3/157226/103 "2026-09-05T20:19:55Z")
Hi J273,
Yes, please switch to the new app with ID `nl.nobrainer.hikvision` to receive future updates. Install the new app first, add your devices again and recreate or update the related Flows. Test everything before removing the old app.
New version: [Hikvision | Homey](https://homey.app/en-us/app/nl.nobrainer.hikvision/Hikvision/test/)
The old test app will be withdrawn at the end of September 2026.
[Previous page](https://community.homey.app/t/app-pro-test-hikvision-sdk-v3/157226.md?page=4)
[Next page](https://community.homey.app/t/app-pro-test-hikvision-sdk-v3/157226.md?page=6)