# \[APP\]\[Pro\] Hikvision NVR & DVR - Every camera. One recorder. Full control - looking for testers

**URL:** <https://community.homey.app/t/app-pro-hikvision-nvr-dvr-every-camera-one-recorder-full-control-looking-for-testers/159939>\
**Category:** Apps\
**Tags:** app, community-app\
**Created:** [September 23, 2026, 7:14pm UTC](https://community.homey.app/t/app-pro-hikvision-nvr-dvr-every-camera-one-recorder-full-control-looking-for-testers/159939 "2026-09-23T19:14:57Z")\
**Posts on this page:** 20\
**Page:** 2

<div class="post-metadata">

**Author:** ![Mithrandir86](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/mithrandir86/32/89825_2.png) [@Mithrandir86](https://community.homey.app/u/Mithrandir86)\
**Post date:** [November 8, 2026, 8:38am UTC](https://community.homey.app/t/app-pro-hikvision-nvr-dvr-every-camera-one-recorder-full-control-looking-for-testers/159939/21 "2026-11-08T08:38:28Z")

</div>

Thanks, I’ll report anything odd.

One more idea for the ring event: Brian’s Hikvision app for Homey works with my door station including ringing, and his changelog (2026.8.7) mentions an “official Hikvision ISAPI call-status fallback”. Other DS-KD8003 users report that polling /ISAPI/VideoIntercom/callStatus?format=json returns idle / ring / onCall. Would polling that endpoint be possible in your app as an optional ring trigger? I can test it on my door station (FW V2.2.76).

---

<div class="post-metadata">

**Author:** ![TheWiZZz](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/thewizzz/32/173014_2.png) [@TheWiZZz](https://community.homey.app/u/TheWiZZz)\
**Post date:** [November 8, 2026, 9:06am UTC](https://community.homey.app/t/app-pro-hikvision-nvr-dvr-every-camera-one-recorder-full-control-looking-for-testers/159939/22 "2026-11-08T09:06:27Z")

</div>

Hi Zdenda,

Thanks for the tip, that was exactly the pointer I needed. I have built it as an optional ring detection for video-only door stations, in version 5.2.0:

[https://homey.app/a/com.wisse.hikvision/test/](https://homey.app/a/com.wisse.hikvision/test/)

- The app asks your door station for /ISAPI/VideoIntercom/callStatus?format=json once. Only if it answers with a call status (idle / ring / onCall), the app starts checking it every 2 seconds.
- When the status goes to “ring”, the normal “doorbell pressed” Flow trigger fires, with a snapshot.
- If your door station does not answer that address properly, nothing changes and the doorbell keeps working as video-only as it does now.

You can install the test version via [https://homey.app/a/com.wisse.hikvision/test/](https://homey.app/a/com.wisse.hikvision/test/) (version 5.2.0, it appears once Homey has finished processing it). No need to remove the doorbell; just update, wait a minute, and press the ring button. Please let me know:

1. Does the “doorbell pressed” Flow trigger fire when you ring?
2. If not: copy the app diagnostics report again; it will have a line “call status” that shows what your door station answered.

This one is experimental, because I have no door station like yours to test with, so your feedback is what makes it work.

Kind regards,  
Wisse

---

<div class="post-metadata">

**Author:** ![Mithrandir86](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/mithrandir86/32/89825_2.png) [@Mithrandir86](https://community.homey.app/u/Mithrandir86)\
**Post date:** [November 8, 2026, 10:47am UTC](https://community.homey.app/t/app-pro-hikvision-nvr-dvr-every-camera-one-recorder-full-control-looking-for-testers/159939/23 "2026-11-08T10:47:33Z")

</div>

Hi Wisse,  
thanks for 5.2.0. I tested on my door station (FW V2.2.76): pressing the ring button did not fire the “doorbell pressed” trigger, no notification arrived. The copied report is below.  
One more observation: right after adding the Doorbell it is unavailable. If I open Repair and just leave it without finishing, the device becomes available and stays that way. So the first start seems to leave it unavailable until something re-initialises it.  
Best regards,  
Zdenda

> Hikvision for Homey: diagnostics report  
> App 5.2.0 / Homey 13.5.3 / 2026-11-08T10:46:47.073Z  
> No addresses, passwords or camera pictures are included.
> 
> == NVR-Skalicky (Recorder) ==
> 
> - Model DS-7608NI-I2, firmware V4.61.030
> - Cameras: 6 (6 IP, 0 analog)
> - Available: yes
> - Event connection: connected, last sign of life 1 s ago
> - Hard disk: ok, free 0%
> - Armed: yes
> - Notify Surveillance Center problems: 0
> - Events since the app started: VMD 17
> - Last self-test: 2 min ago
> - Self-test login: ok — DS-7608NI-I2, firmware V4.61.030
> - Self-test channels: ok — 6 found (6 IP, 0 analog)
> - Self-test events: ok — Connected; the recorder is sending signs of life.
> - Self-test notify: ok — Every enabled detection type notifies Homey.
> - Self-test snapshot: ok — Camera 1: 63 kB in 434 ms
> - Self-test video-main: ok — Camera 1: H265 on port 554; the experimental H.265 option is enabled (open the live view to check that this Homey can play it).
> - Self-test video-sub: ok — Camera 1: H.264 on port 554
> - Self-test hdd: ok — Working
> - Self-test clock: ok — Matches Homey
> 
> == Kamera 1 ZAHRADA (Camera via recorder) ==
> 
> - Available: yes
> - Live video: OK (H265, no audio, port 554). If the picture still stays black, press “Turn off stream encryption” in this app’s settings (or turn it off on the recorder under Network \> Platform Access); Homey cannot play encrypted streams
> 
> == Kamera 2 VJEZD (Camera via recorder) ==
> 
> - Available: yes
> - Live video: OK (H265, no audio, port 554). If the picture still stays black, press “Turn off stream encryption” in this app’s settings (or turn it off on the recorder under Network \> Platform Access); Homey cannot play encrypted streams
> 
> == Kamera 3 BAZEN (Camera via recorder) ==
> 
> - Available: yes
> - Live video: OK (H265, no audio, port 554). If the picture still stays black, press “Turn off stream encryption” in this app’s settings (or turn it off on the recorder under Network \> Platform Access); Homey cannot play encrypted streams
> 
> == Kamera 4 DOMEK (Camera via recorder) ==
> 
> - Available: yes
> - Live video: OK (H265, no audio, port 554). If the picture still stays black, press “Turn off stream encryption” in this app’s settings (or turn it off on the recorder under Network \> Platform Access); Homey cannot play encrypted streams
> 
> == Kamera 5 CERPADLO (Camera via recorder) ==
> 
> - Available: yes
> - Live video: OK (H265, no audio, port 554). If the picture still stays black, press “Turn off stream encryption” in this app’s settings (or turn it off on the recorder under Network \> Platform Access); Homey cannot play encrypted streams
> 
> == BRANKA (Camera via recorder) ==
> 
> - Available: yes
> - Live video: OK (H264, audio PCMU, port 554). If the picture still stays black, press “Turn off stream encryption” in this app’s settings (or turn it off on the recorder under Network \> Platform Access); Homey cannot play encrypted streams
> 
> == OUTDOOR STATION (Doorbell) ==
> 
> - Available: yes
> - Saved connection mode: video only (RTSP)
> - Usable connection: rtspOnly
> - Event connection: disconnected
> - Saved setup identity: ok DEVICE\_INFO\_READY status 200
> - Saved setup events: unavailable EVENT\_STREAM\_NOT\_MULTIPART status 200
> - Saved setup video: ok status 200 port 554 Streaming/Channels video H264 audio PCMU
> - Current event check: skipped VIDEO\_ONLY\_MODE
> - Homey RTSP probe: ok status 200 port 554 Streaming/Channels video H264 audio PCMU
> - Last event-stream error: VIDEO\_ONLY\_MODE
> - The RTSP probe checks Homey-to-doorbell access, not remote app playback.
> 
> == Recent connection checks (Diagnostics) ==
> 
> - 68 min ago: Doorbell / connection video / ok / status 200 port 554 Streaming/Channels video H264 audio PCMU
> - 67 min ago: Doorbell / connection events / skipped / VIDEO\_ONLY\_MODE
> - 67 min ago: Doorbell / connection video / ok / status 200 port 554 Streaming/Channels video H264 audio PCMU
> - 66 min ago: Doorbell / connection events / skipped / VIDEO\_ONLY\_MODE
> - 66 min ago: Doorbell / connection video / ok / status 200 port 554 Streaming/Channels video H264 audio PCMU
> - 65 min ago: Doorbell / connection events / skipped / VIDEO\_ONLY\_MODE
> - 65 min ago: Doorbell / connection video / ok / status 200 port 554 Streaming/Channels video H264 audio PCMU
> - 64 min ago: Doorbell / connection events / skipped / VIDEO\_ONLY\_MODE
> - 64 min ago: Doorbell / connection video / auth\_failed / status 401 port 554 Streaming/Channels Digest MD5
> - 34 min ago: Doorbell / connection events / skipped / VIDEO\_ONLY\_MODE
> - 34 min ago: Doorbell / connection video / ok / status 200 port 554 Streaming/Channels video H264 audio PCMU
> - 33 min ago: Doorbell / connection events / skipped / VIDEO\_ONLY\_MODE
> - 33 min ago: Doorbell / connection video / auth\_failed / status 401 port 554 Streaming/Channels Digest MD5
> - 3 min ago: Doorbell / connection events / skipped / VIDEO\_ONLY\_MODE
> - 3 min ago: Doorbell / connection video / ok / status 200 port 554 Streaming/Channels video H264 audio PCMU
> - 2 min ago: Doorbell / connection events / skipped / VIDEO\_ONLY\_MODE
> - 2 min ago: Doorbell / connection video / ok / status 200 port 554 Streaming/Channels video H264 audio PCMU
> - 2 min ago: Recorder / self-test / completed
> - 60 s ago: Doorbell / connection events / skipped / VIDEO\_ONLY\_MODE
> - 60 s ago: Doorbell / connection video / ok / status 200 port 554 Streaming/Channels video H264 audio PCMU

---

<div class="post-metadata">

**Author:** ![Mithrandir86](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/mithrandir86/32/89825_2.png) [@Mithrandir86](https://community.homey.app/u/Mithrandir86)\
**Post date:** [November 8, 2026, 10:57am UTC](https://community.homey.app/t/app-pro-hikvision-nvr-dvr-every-camera-one-recorder-full-control-looking-for-testers/159939/24 "2026-11-08T10:57:52Z")

</div>

I found the cause. In Brian’s Hikvision SDK v3 thread (posts 81–86, Aug 30 – Sep 1) he fixed exactly my door station (DS-KD8003-IME1(B)/Flush, FW V2.2.76) in version 2026.8.20 by adding a “Hikvision web-session fallback” for the HTTP 401 behaviour on V2.2.76. The station rejects normal Digest and Basic ISAPI login, so every ISAPI call (including /ISAPI/VideoIntercom/callStatus) returned “Device Error” and “Invalid username or password” even with correct credentials. With the web-session login the doorbell Flow triggers reliably on the physical button and the device stays available. That would also explain why 5.2.0 didn’t see any ring.  
His app is open source ( [GitHub - bmonninkhof/nl.nobrainer.hikvision: Homey SDK v3 integration for local Hikvision cameras, video doorbells and NVRs using ISAPI and RTSP. · GitHub](http://github.com/bmonninkhof/nl.nobrainer.hikvision) ), so you could look at how the web-session login works. I’m happy to test any build.  
Best regards,  
Zdenda

---

<div class="post-metadata">

**Author:** ![TheWiZZz](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/thewizzz/32/173014_2.png) [@TheWiZZz](https://community.homey.app/u/TheWiZZz)\
**Post date:** [November 8, 2026, 12:12pm UTC](https://community.homey.app/t/app-pro-hikvision-nvr-dvr-every-camera-one-recorder-full-control-looking-for-testers/159939/25 "2026-11-08T12:12:26Z")

</div>

Hi Zdenda,

That is a very useful find, thank you for digging that up. It fits what we saw: your door station answers the normal web login with “invalid username or password”, even though the details are correct.

I have built it into version 5.2.1: if the door station refuses the normal login, the app now logs in the way the door station’s own web page does (a session login), and then uses that for the ring check as well. I wrote this myself from the protocol, so nothing was copied from Brian’s app. Wrong passwords are only retried once a minute, so the account cannot get locked by this.

You can install the test version via [https://homey.app/a/com.wisse.hikvision/test/](https://homey.app/a/com.wisse.hikvision/test/) (version 5.2.1; it can take a few minutes before it shows up). No need to remove the doorbell: update, wait a minute, then press the ring button. Please let me know:

1. Does the “doorbell pressed” Flow trigger fire?
2. If not: the app diagnostics report again. It now contains a “call status” line with a “web-login” result (ok / rejected / unsupported), which tells me exactly where it stops.

I have no door station like yours to test with, so your test is what decides if this works.

Thanks again for all the effort.

Kind regards,  
Wisse

---

<div class="post-metadata">

**Author:** ![Mithrandir86](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/mithrandir86/32/89825_2.png) [@Mithrandir86](https://community.homey.app/u/Mithrandir86)\
**Post date:** [November 8, 2026, 12:36pm UTC](https://community.homey.app/t/app-pro-hikvision-nvr-dvr-every-camera-one-recorder-full-control-looking-for-testers/159939/26 "2026-11-08T12:36:17Z")

</div>

Hi Wisse,  
thanks for 5.2.1. I updated, waited a few minutes, removed the Doorbell and added it again, then pressed the ring button on the DS-KD8003 (FW V2.2.76). The “doorbell pressed” Flow trigger still does not fire, same as with 5.2.0. The copied report with the “call status” / “web-login” line is below.  
Best regards,  
Zdenda

> Hikvision for Homey: diagnostics report  
> App 5.2.1 / Homey 13.5.3 / 2026-11-08T12:35:51.431Z  
> No addresses, passwords or camera pictures are included.
> 
> == NVR-Skalicky (Recorder) ==
> 
> - Model DS-7608NI-I2, firmware V4.61.030
> - Cameras: 6 (6 IP, 0 analog)
> - Available: yes
> - Event connection: connected, last sign of life 6 s ago
> - Hard disk: ok, free 0%
> - Armed: yes
> - Notify Surveillance Center problems: 0
> - Events since the app started: VMD 3
> - Last self-test: 80 s ago
> - Self-test login: ok — DS-7608NI-I2, firmware V4.61.030
> - Self-test channels: ok — 6 found (6 IP, 0 analog)
> - Self-test events: ok — Connected; the recorder is sending signs of life.
> - Self-test notify: ok — Every enabled detection type notifies Homey.
> - Self-test snapshot: ok — Camera 1: 62 kB in 331 ms
> - Self-test video-main: ok — Camera 1: H265 on port 554; the experimental H.265 option is enabled (open the live view to check that this Homey can play it).
> - Self-test video-sub: ok — Camera 1: H.264 on port 554
> - Self-test hdd: ok — Working
> - Self-test clock: ok — Matches Homey
> 
> == Kamera 1 ZAHRADA (Camera via recorder) ==
> 
> - Available: yes
> - Live video: OK (H265, no audio, port 554). If the picture still stays black, press “Turn off stream encryption” in this app’s settings (or turn it off on the recorder under Network \> Platform Access); Homey cannot play encrypted streams
> 
> == Kamera 2 VJEZD (Camera via recorder) ==
> 
> - Available: yes
> - Live video: OK (H265, no audio, port 554). If the picture still stays black, press “Turn off stream encryption” in this app’s settings (or turn it off on the recorder under Network \> Platform Access); Homey cannot play encrypted streams
> 
> == Kamera 3 BAZEN (Camera via recorder) ==
> 
> - Available: yes
> - Live video: OK (H265, no audio, port 554). If the picture still stays black, press “Turn off stream encryption” in this app’s settings (or turn it off on the recorder under Network \> Platform Access); Homey cannot play encrypted streams
> 
> == Kamera 4 DOMEK (Camera via recorder) ==
> 
> - Available: yes
> - Live video: OK (H265, no audio, port 554). If the picture still stays black, press “Turn off stream encryption” in this app’s settings (or turn it off on the recorder under Network \> Platform Access); Homey cannot play encrypted streams
> 
> == Kamera 5 CERPADLO (Camera via recorder) ==
> 
> - Available: yes
> - Live video: OK (H265, no audio, port 554). If the picture still stays black, press “Turn off stream encryption” in this app’s settings (or turn it off on the recorder under Network \> Platform Access); Homey cannot play encrypted streams
> 
> == BRANKA (Camera via recorder) ==
> 
> - Available: yes
> - Live video: OK (H264, audio PCMU, port 554). If the picture still stays black, press “Turn off stream encryption” in this app’s settings (or turn it off on the recorder under Network \> Platform Access); Homey cannot play encrypted streams
> 
> == OUTDOOR STATION (Doorbell) ==
> 
> - Available: yes
> - Saved connection mode: video only (RTSP)
> - Usable connection: rtspOnly
> - Event connection: disconnected
> - Saved setup identity: skipped VIDEO\_ONLY\_MODE
> - Saved setup events: skipped VIDEO\_ONLY\_MODE
> - Saved setup video: ok status 200 port 554 Streaming/Channels video H264 audio PCMU
> - Current event check: skipped VIDEO\_ONLY\_MODE
> - Homey RTSP probe: ok status 200 port 554 Streaming/Channels video H264 audio PCMU
> - Last event-stream error: VIDEO\_ONLY\_MODE
> - The RTSP probe checks Homey-to-doorbell access, not remote app playback.
> 
> == Recent connection checks (Diagnostics) ==
> 
> - 5 min ago: Doorbell / pairing identity / ok / DEVICE\_INFO\_READY status 200
> - 5 min ago: Doorbell / pairing events / unavailable / EVENT\_STREAM\_NOT\_MULTIPART status 200
> - 5 min ago: Doorbell / pairing video / ok / status 200 port 554 Streaming/Channels video H264 audio PCMU
> - 5 min ago: Doorbell / connection events / skipped / VIDEO\_ONLY\_MODE
> - 5 min ago: Doorbell / connection video / ok / status 200 port 554 Streaming/Channels video H264 audio PCMU
> - 5 min ago: Doorbell / pairing identity / skipped / VIDEO\_ONLY\_MODE
> - 5 min ago: Doorbell / pairing events / skipped / VIDEO\_ONLY\_MODE
> - 5 min ago: Doorbell / pairing video / ok / status 200 port 554 Streaming/Channels video H264 audio PCMU
> - 5 min ago: Doorbell / connection events / skipped / VIDEO\_ONLY\_MODE
> - 5 min ago: Doorbell / connection video / ok / status 200 port 554 Streaming/Channels video H264 audio PCMU
> - 4 min ago: Doorbell / connection events / skipped / VIDEO\_ONLY\_MODE
> - 4 min ago: Doorbell / connection video / ok / status 200 port 554 Streaming/Channels video H264 audio PCMU
> - 3 min ago: Doorbell / connection events / skipped / VIDEO\_ONLY\_MODE
> - 3 min ago: Doorbell / connection video / ok / status 200 port 554 Streaming/Channels video H264 audio PCMU
> - 2 min ago: Doorbell / connection events / skipped / VIDEO\_ONLY\_MODE
> - 2 min ago: Doorbell / connection video / ok / status 200 port 554 Streaming/Channels video H264 audio PCMU
> - 80 s ago: Recorder / self-test / completed
> - 48 s ago: Doorbell / connection events / skipped / VIDEO\_ONLY\_MODE
> - 48 s ago: Doorbell / connection video / ok / status 200 port 554 Streaming/Channels video H264 audio PCMU

---

<div class="post-metadata">

**Author:** ![TheWiZZz](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/thewizzz/32/173014_2.png) [@TheWiZZz](https://community.homey.app/u/TheWiZZz)\
**Post date:** [November 8, 2026, 3:22pm UTC](https://community.homey.app/t/app-pro-hikvision-nvr-dvr-every-camera-one-recorder-full-control-looking-for-testers/159939/27 "2026-11-08T15:22:09Z")

</div>

Hi Zdenda,

Thank you for the detailed report from 13:46. I found a bug in my code that explains why 5.2.1 still did not detect the ring button.

[https://homey.app/a/com.wisse.hikvision/test/](https://homey.app/a/com.wisse.hikvision/test/)

Your doorbell was saved in RTSP video mode. In that mode, the app skipped creating the local API connection altogether, so it never reached the call-status check or the web-session login added in 5.2.1. That also explains why the expected “call status” and “web-login” lines were missing from your report.

I have prepared version **5.2.2** to fix this. It starts call-status monitoring for existing RTSP doorbells as well, using the web-session login when needed. You should not need to remove and add the doorbell again. The diagnostics report now always shows the call-status check, web-login result, polling activity and the result of the doorbell Flow trigger.

I tested the complete startup and ring-trigger path against a simulated door station that rejects Digest authentication and accepts a web-session login. Repeated ringing samples produced one Flow trigger. Your DS-KD8003 with firmware V2.2.76 still needs a real-device test.

Once 5.2.2 is available on the test channel:

1. Update using [the Homey test link](https://homey.app/a/com.wisse.hikvision/test/) and check that the installed app version is 5.2.2.
2. Leave the existing doorbell paired, wait about 15 seconds, then press its ring button and check your “doorbell pressed” Flow.
3. If it still does not trigger, please copy a fresh diagnostics report immediately afterwards. It will now include the call-status, web-login, polling samples and Flow-trigger result needed to see exactly where it stops.

Best regards,  
Wisse

---

<div class="post-metadata">

**Author:** ![Mithrandir86](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/mithrandir86/32/89825_2.png) [@Mithrandir86](https://community.homey.app/u/Mithrandir86)\
**Post date:** [November 8, 2026, 4:13pm UTC](https://community.homey.app/t/app-pro-hikvision-nvr-dvr-every-camera-one-recorder-full-control-looking-for-testers/159939/28 "2026-11-08T16:13:31Z")

</div>

Hi Wisse,  
thanks for 5.2.2. I updated (the banner now says live video and doorbell notifications are active), but the “doorbell button was pressed” Flow still does not fire when I press the ring button on the DS-KD8003 (FW V2.2.76). The Flow has no conditions, it just sends a push with the Snapshot tag from the trigger (the same kind of Flow works with Brian’s app on this door station, including the snapshot).  
One more observation: after every app restart the Doorbell shows “Device unavailable” at first, and only becomes available after “Try to Repair”.  
The copied report, created right after pressing the button, is below.  
Best regards,  
Zdenda

> Hikvision for Homey: diagnostics report  
> App 5.2.2 / Homey 13.5.3 / 2026-11-08T16:13:08.054Z  
> No addresses, passwords or camera pictures are included.
> 
> == NVR-Skalicky (Recorder) ==
> 
> - Model DS-7608NI-I2, firmware V4.61.030
> - Cameras: 6 (6 IP, 0 analog)
> - Available: yes
> - Event connection: connected, last sign of life 6 s ago
> - Hard disk: ok, free 0%
> - Armed: yes
> - Notify Surveillance Center problems: 0
> - Events since the app started: VMD 19
> - Last self-test: 8 s ago
> - Self-test login: ok — DS-7608NI-I2, firmware V4.61.030
> - Self-test channels: ok — 6 found (6 IP, 0 analog)
> - Self-test events: ok — Connected; the recorder is sending signs of life.
> - Self-test notify: ok — Every enabled detection type notifies Homey.
> - Self-test snapshot: ok — Camera 1: 36 kB in 424 ms
> - Self-test video-main: ok — Camera 1: H265 on port 554; the experimental H.265 option is enabled (open the live view to check that this Homey can play it).
> - Self-test video-sub: ok — Camera 1: H.264 on port 554
> - Self-test hdd: ok — Working
> - Self-test clock: ok — Matches Homey
> 
> == Kamera 1 ZAHRADA (Camera via recorder) ==
> 
> - Available: yes
> - Live video: OK (H265, no audio, port 554). If the picture still stays black, press “Turn off stream encryption” in this app’s settings (or turn it off on the recorder under Network \> Platform Access); Homey cannot play encrypted streams
> 
> == Kamera 2 VJEZD (Camera via recorder) ==
> 
> - Available: yes
> - Live video: OK (H265, no audio, port 554). If the picture still stays black, press “Turn off stream encryption” in this app’s settings (or turn it off on the recorder under Network \> Platform Access); Homey cannot play encrypted streams
> 
> == Kamera 3 BAZEN (Camera via recorder) ==
> 
> - Available: yes
> - Live video: OK (H265, no audio, port 554). If the picture still stays black, press “Turn off stream encryption” in this app’s settings (or turn it off on the recorder under Network \> Platform Access); Homey cannot play encrypted streams
> 
> == Kamera 4 DOMEK (Camera via recorder) ==
> 
> - Available: yes
> - Live video: OK (H265, no audio, port 554). If the picture still stays black, press “Turn off stream encryption” in this app’s settings (or turn it off on the recorder under Network \> Platform Access); Homey cannot play encrypted streams
> 
> == Kamera 5 CERPADLO (Camera via recorder) ==
> 
> - Available: yes
> - Live video: OK (H265, no audio, port 554). If the picture still stays black, press “Turn off stream encryption” in this app’s settings (or turn it off on the recorder under Network \> Platform Access); Homey cannot play encrypted streams
> 
> == BRANKA (Camera via recorder) ==
> 
> - Available: yes
> - Live video: OK (H264, audio PCMU, port 554). If the picture still stays black, press “Turn off stream encryption” in this app’s settings (or turn it off on the recorder under Network \> Platform Access); Homey cannot play encrypted streams
> 
> == OUTDOOR STATION (Doorbell) ==
> 
> - Available: yes
> - Saved connection mode: RTSP video with optional call-status monitoring
> - Usable connection: callStatus
> - Event connection: disconnected
> - Saved setup identity: skipped VIDEO\_ONLY\_MODE
> - Saved setup events: skipped VIDEO\_ONLY\_MODE
> - Saved setup video: ok status 200 port 554 Streaming/Channels video H264 audio PCMU
> - Current event check: skipped VIDEO\_ONLY\_MODE
> - Homey RTSP probe: auth\_failed status 401 port 554 Streaming/Channels Digest MD5
> - Call status check: ok CALL\_STATUS\_READY status 200
> - Web login: ok
> - Call status polling: active
> - Call status samples: 1053, rings 1, latest idle, result CALL\_STATUS\_READY
> - Last call status sample: 2026-11-08T16:13:08.046Z
> - Last doorbell ring: 2026-11-08T15:41:20.794Z, Flow trigger Error
> - The RTSP probe checks Homey-to-doorbell access, not remote app playback.
> 
> == Recent connection checks (Diagnostics) ==
> 
> - 28 min ago: Doorbell / connection video / ok / status 200 port 554 Streaming/Channels video H264 audio PCMU
> - 27 min ago: Doorbell / connection events / skipped / VIDEO\_ONLY\_MODE
> - 27 min ago: Doorbell / connection video / ok / status 200 port 554 Streaming/Channels video H264 audio PCMU
> - 26 min ago: Doorbell / connection events / skipped / VIDEO\_ONLY\_MODE
> - 26 min ago: Doorbell / connection video / ok / status 200 port 554 Streaming/Channels video H264 audio PCMU
> - 25 min ago: Doorbell / connection events / skipped / VIDEO\_ONLY\_MODE
> - 25 min ago: Doorbell / connection video / ok / status 200 port 554 Streaming/Channels video H264 audio PCMU
> - 24 min ago: Doorbell / connection events / skipped / VIDEO\_ONLY\_MODE
> - 24 min ago: Doorbell / connection video / ok / status 200 port 554 Streaming/Channels video H264 audio PCMU
> - 23 min ago: Doorbell / connection events / skipped / VIDEO\_ONLY\_MODE
> - 23 min ago: Doorbell / connection video / ok / status 200 port 554 Streaming/Channels video H264 audio PCMU
> - 22 min ago: Doorbell / connection events / skipped / VIDEO\_ONLY\_MODE
> - 22 min ago: Doorbell / connection video / ok / status 200 port 554 Streaming/Channels video H264 audio PCMU
> - 21 min ago: Doorbell / connection events / skipped / VIDEO\_ONLY\_MODE
> - 21 min ago: Doorbell / connection video / ok / status 200 port 554 Streaming/Channels video H264 audio PCMU
> - 20 min ago: Doorbell / connection events / skipped / VIDEO\_ONLY\_MODE
> - 20 min ago: Doorbell / connection video / ok / status 200 port 554 Streaming/Channels video H264 audio PCMU
> - 19 min ago: Doorbell / connection events / skipped / VIDEO\_ONLY\_MODE
> - 19 min ago: Doorbell / connection video / auth\_failed / status 401 port 554 Streaming/Channels Digest MD5
> - 8 s ago: Recorder / self-test / completed

 ![Screenshot_20261108_163742_Homey](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/6/b/6bbebdaf20efbd5816bd75eaf4269e0b0dfbeff8.jpeg)

 ![Screenshot_20261108_171410_Homey](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/0/8/084e63c8b798cd851fe26e6974dfae70666e6077.jpeg)

 ![Screenshot_20261108_163845_Homey](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/b/c/bc724ef7b1646c11c49087af2c4a2c8faa0cbb26.jpeg)

---

<div class="post-metadata">

**Author:** ![TheWiZZz](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/thewizzz/32/173014_2.png) [@TheWiZZz](https://community.homey.app/u/TheWiZZz)\
**Post date:** [November 8, 2026, 7:20pm UTC](https://community.homey.app/t/app-pro-hikvision-nvr-dvr-every-camera-one-recorder-full-control-looking-for-testers/159939/29 "2026-11-08T19:20:50Z")

</div>

Hi Zdenda,

Thank you for the clear report and the screenshots, it showed exactly where it went wrong. The good news first: your door station now reports the button press correctly (the report says “rings 1”). The step that failed was the last one: starting the Flow. The “doorbell was pressed” Flow card always expects a picture (the Snapshot tag), and for a door station in this mode the app did not hand one over, so Homey refused to start the Flow. That also explains why your Flow with the Snapshot tag stayed silent.

[https://homey.app/a/com.wisse.hikvision/test/](https://homey.app/a/com.wisse.hikvision/test/)

Version 5.2.3 fixes this:

- The Flow now always starts with a picture. The app first tries to take a real snapshot from the door station; if that is not possible it uses the live picture, and as a last resort a plain grey placeholder picture. So the Flow will fire either way. If you get the grey picture, please tell me, then I know the door station does not give snapshots this way and I can look for another route.
- The doorbell stays available after the app restarts. Before, one failed check at startup left it “unavailable” until you pressed Repair. Now it only becomes unavailable after several failed checks in a row.
- The login is more careful: once the door station has accepted the app, the app no longer sends logins it refuses, so your door station’s account cannot get locked by repeated wrong attempts.
- The diagnostics report now also shows what status your door station reported around a press (for example idle \> ring \> idle), and it is less cluttered.

You can install the test version via [https://homey.app/a/com.wisse.hikvision/test/](https://homey.app/a/com.wisse.hikvision/test/) (version 5.2.3, it can take a few minutes to appear). No need to remove the doorbell. Please:

1. Update, wait a minute, and press the ring button.
2. Tell me if the Flow starts and what the snapshot looks like (real picture or grey).
3. If anything is off, copy the diagnostics report right after pressing; the new “Call status changes” and “Flow trigger” lines tell me what happened.

Thank you for all your patience and testing. We are close now.

Kind regards,  
Wisse

---

<div class="post-metadata">

**Author:** ![Mithrandir86](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/mithrandir86/32/89825_2.png) [@Mithrandir86](https://community.homey.app/u/Mithrandir86)\
**Post date:** [November 8, 2026, 7:46pm UTC](https://community.homey.app/t/app-pro-hikvision-nvr-dvr-every-camera-one-recorder-full-control-looking-for-testers/159939/30 "2026-11-08T19:46:04Z")

</div>

Hi Wisse,  
5.2.3 works: the ring button now triggers my Flow and the notification arrived with a real snapshot of the gate (not the grey placeholder). Thank you!  
One thing remains: after restarting the app the Doorbell is still “Device unavailable” and only becomes available after “Try to Repair”, even with 5.2.3.  
Best regards,  
Zdenda

---

<div class="post-metadata">

**Author:** ![Mithrandir86](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/mithrandir86/32/89825_2.png) [@Mithrandir86](https://community.homey.app/u/Mithrandir86)\
**Post date:** [November 8, 2026, 8:05pm UTC](https://community.homey.app/t/app-pro-hikvision-nvr-dvr-every-camera-one-recorder-full-control-looking-for-testers/159939/31 "2026-11-08T20:05:22Z")

</div>

Hi Wisse,  
a correction to my last message: the Doorbell does not need “Try to Repair”. After an app restart it is “Device unavailable” for about 1–2 minutes and then becomes available on its own.  
In the reports I took right after the restart, the device showed “Available: no” while the checks were all fine: call status ok (CALL\_STATUS\_READY, web login ok), polling active (3, later 24 and 63 samples), RTSP probe ok and connection video ok, with no failed check in the list. So the checks succeed and only the device state seems to lag behind. Could it be marked available as soon as the first check succeeds? I can send the reports if you want to see them.

Best regards,  
Zdenda

---

<div class="post-metadata">

**Author:** ![TheWiZZz](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/thewizzz/32/173014_2.png) [@TheWiZZz](https://community.homey.app/u/TheWiZZz)\
**Post date:** [November 8, 2026, 8:23pm UTC](https://community.homey.app/t/app-pro-hikvision-nvr-dvr-every-camera-one-recorder-full-control-looking-for-testers/159939/32 "2026-11-08T20:23:07Z")

</div>

Hi Zdenda,

Thank you for the correction. I understand now: Repair is not needed, but after an app restart the doorbell stays “Device unavailable” for about one to two minutes even though video, web login and call-status polling are already working. It then becomes available on its own.

[https://homey.app/a/com.wisse.hikvision/test/](https://homey.app/a/com.wisse.hikvision/test/)

It is also good to have your confirmation that 5.2.3 triggers the Flow and delivers a real snapshot of the gate.

I found a remaining dependency in the code: the doorbell driver was still linked to Homey’s automatic network discovery, which also manages device availability. That could override the healthy connection state during startup. In addition, the app waited to save connection history before applying the successful connection result.

I have prepared **5.2.4**. The doorbell now updates its availability as soon as a connection check succeeds. Network discovery is optional and is only used to follow IP address changes when the MAC address is known. Saving the connection history no longer delays the availability update. I also fixed the saved web-login preference so it is respected immediately after a restart.

The automated tests cover a fresh restart without any discovery result, availability while other startup work is still pending, and a new ring with a snapshot. They pass, but the restart behaviour on your actual Homey still needs your test.

Once 5.2.4 is published to Test:

1. Update through [the Homey test link](https://homey.app/a/com.wisse.hikvision/test/) and check that the installed version is 5.2.4.
2. Restart the Hikvision app and check whether the doorbell becomes available after its initial connection checks, without opening Repair.
3. Press the ring button once to confirm that the Flow and gate snapshot still work.

If the availability still lags behind successful checks, please send a fresh Copy report taken while it says unavailable. The report now also shows the availability source, optional address-discovery state and failed-check count. Your existing reports are welcome too, but you do not need to repeat the pairing process.

Best regards,  
Wisse

---

<div class="post-metadata">

**Author:** ![Mithrandir86](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/mithrandir86/32/89825_2.png) [@Mithrandir86](https://community.homey.app/u/Mithrandir86)\
**Post date:** [November 8, 2026, 8:42pm UTC](https://community.homey.app/t/app-pro-hikvision-nvr-dvr-every-camera-one-recorder-full-control-looking-for-testers/159939/33 "2026-11-08T20:42:27Z")

</div>

Hi Wisse,  
5.2.4 works: after a restart the Doorbell connects normally and the ring triggers the Flow with a real snapshot. Thank you!  
One small cosmetic thing remains: in the device’s Insights the “CallButtonPress” value does not update when I press the ring button (it keeps showing an old time, hours back), although the Flow fires correctly. I assume the Insights only follow the ISAPI event stream, which this door station doesn’t use, and the call-status path doesn’t write to them.

 ![Screenshot_20261108_211306_Homey](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/4/7/471ad6db435827f6490ba0fada8d5c95c5bba6a1.jpeg)

 ![Screenshot_20261108_211314_Homey](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/2/2/22e82bb449436f255f80c245636678c079b8b3aa.jpeg)

The red banner “Motion controls are unavailable in RTSP-only mode…” is also still shown.  
Best regards  
Zdenda

---

<div class="post-metadata">

**Author:** ![TheWiZZz](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/thewizzz/32/173014_2.png) [@TheWiZZz](https://community.homey.app/u/TheWiZZz)\
**Post date:** [November 9, 2026, 6:11am UTC](https://community.homey.app/t/app-pro-hikvision-nvr-dvr-every-camera-one-recorder-full-control-looking-for-testers/159939/34 "2026-11-09T06:11:09Z")

</div>

Hi Zdenda,

Thank you for confirming that 5.2.4 reconnects normally after a restart and that the ring Flow still delivers the real gate snapshot. I have also reviewed both screenshots.

[https://homey.app/a/com.wisse.hikvision/test/](https://homey.app/a/com.wisse.hikvision/test/)

I found the reason for the old “CallButtonPress” time: the call-status path wrote exactly the same event text on every press. Homey therefore kept showing the time of the last changed value. In **5.2.5** , each separate ring updates that value with its own timestamp in Homey’s local time.

I have addressed the other items in the screenshots as well:

- Active call-status monitoring is shown as “Monitoring doorbell”, instead of “Disconnected”.
- The unsupported motion switch and unused motion/video-loss sensor tiles are automatically removed in RTSP compatibility mode. This removes the control that caused the red motion-control error.
- A healthy video and ring connection no longer shows an unnecessary warning.

Your existing doorbell and “doorbell pressed” Flow are kept. I tested repeated presses, repeated samples during the same ring, migration of an existing device, restarts, native-event mode and failure handling. A display-update failure is recorded in diagnostics and does not stop the ring Flow.

I have prepared 5.2.5. Once it is published to Test, please update using [the Homey test link](https://homey.app/a/com.wisse.hikvision/test/) and reopen the doorbell screen. Press the ring button, let that call end, then press it again. The latest-event time should refresh for both presses, and both notifications should still include the gate picture.

If the screen still differs, a fresh Copy report and screenshot will help: the report now includes the monitoring-status update, last-ring display result and any control-migration errors. The code checks pass; the updated screen still needs confirmation on your Homey.

Best regards,  
Wisse

---

<div class="post-metadata">

**Author:** ![Mithrandir86](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/mithrandir86/32/89825_2.png) [@Mithrandir86](https://community.homey.app/u/Mithrandir86)\
**Post date:** [November 9, 2026, 2:38pm UTC](https://community.homey.app/t/app-pro-hikvision-nvr-dvr-every-camera-one-recorder-full-control-looking-for-testers/159939/35 "2026-11-09T14:38:56Z")

</div>

Hi Wisse,  
5.2.5 works: the ring updates “Doorbell pressed” with a new time on every press, “Monitoring doorbell” is shown, the red banner is gone and both notifications arrive with the gate picture. Thank you!  
One last cosmetic thing: the two Insights entries on the doorbell screen (“Doorbell pressed” and “Monitoring doorbell”) show empty dashed-square icons (Homey’s placeholder for a capability without an icon). A screenshot is attached.  
Best regards,  
Zdenda

 ![Screenshot_20261109_151225_Homey](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/8/1/81f658c4b732c4c17993619ac4cea180759e5c99.jpeg)

---

<div class="post-metadata">

**Author:** ![TheWiZZz](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/thewizzz/32/173014_2.png) [@TheWiZZz](https://community.homey.app/u/TheWiZZz)\
**Post date:** [November 9, 2026, 3:03pm UTC](https://community.homey.app/t/app-pro-hikvision-nvr-dvr-every-camera-one-recorder-full-control-looking-for-testers/159939/36 "2026-11-09T15:03:24Z")

</div>

Hi Zdenda,

Thank you for confirming the time, monitoring status and gate snapshots in 5.2.5. The two status fields were missing their icons. I’ve added a clock for the latest event and a pulse for the monitoring status in **5.2.6**.

[https://homey.app/a/com.wisse.hikvision/test/](https://homey.app/a/com.wisse.hikvision/test/)

Once 5.2.6 is on Test, please update via [the Homey test link](https://homey.app/a/com.wisse.hikvision/test/) and reopen the doorbell screen. The two icons should appear on the existing device.

Best regards,  
Wisse

---

<div class="post-metadata">

**Author:** ![Mithrandir86](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/mithrandir86/32/89825_2.png) [@Mithrandir86](https://community.homey.app/u/Mithrandir86)\
**Post date:** [November 9, 2026, 4:57pm UTC](https://community.homey.app/t/app-pro-hikvision-nvr-dvr-every-camera-one-recorder-full-control-looking-for-testers/159939/37 "2026-11-09T16:57:51Z")

</div>

Hi Wisse,  
5.2.6 works. The clock and pulse icons are showing on the doorbell screen. Everything else is fine too: the ring triggers my Flow every time, both notifications arrive with a real gate snapshot, the doorbell connects normally after an app restart and the red banner is gone.  
Thank you very much for all the work and the quick fixes, especially for building the session login for this door station. It’s great to have the cameras, the recorder and the doorbell in one app now. I’ll let you know if I notice anything odd over the next days.  
Best regards,  
Zdenda

 ![Screenshot_20261109_174925_Homey](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/6/6/664ee58730be660ca5abeeeddaa05c7641752a85.jpeg)

---

<div class="post-metadata">

**Author:** ![TheWiZZz](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/thewizzz/32/173014_2.png) [@TheWiZZz](https://community.homey.app/u/TheWiZZz)\
**Post date:** [November 9, 2026, 5:25pm UTC](https://community.homey.app/t/app-pro-hikvision-nvr-dvr-every-camera-one-recorder-full-control-looking-for-testers/159939/38 "2026-11-09T17:25:52Z")

</div>

Hi Zdenda,

I’m glad everything is working with 5.2.6. Thank you for all the testing and support you’ve given me along the way. I don’t have a door station like yours to test on, so I couldn’t have built reliable support for it on my own. Your detailed reports and patience with each new version made it possible.

If you ever need a Homey app for an unusual device or a particular setup, feel free to get in touch. I’d be happy to see what I can build for you.

Thanks again,  
Wisse

---

<div class="post-metadata">

**Author:** ![Mithrandir86](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/mithrandir86/32/89825_2.png) [@Mithrandir86](https://community.homey.app/u/Mithrandir86)\
**Post date:** [November 10, 2026, 7:02am UTC](https://community.homey.app/t/app-pro-hikvision-nvr-dvr-every-camera-one-recorder-full-control-looking-for-testers/159939/39 "2026-11-10T07:02:24Z")

</div>

Hi Wisse,

thanks again for everything. One feature idea for the Doorbell, if it’s easy to do: since the app already takes a snapshot when the ring is detected, could it also keep that picture as a separate “Last ring” image on the device, overwritten by the next ring? That way I could look back later and see who rang last, even if I missed the notification. It would be great if the current live snapshot, which refreshes when I open the device, stays as it is, and the “Last ring” image is an additional one next to it. No rush, it’s only a nice-to-have.

Best regards,  
Zdenda

---

<div class="post-metadata">

**Author:** ![TheWiZZz](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/thewizzz/32/173014_2.png) [@TheWiZZz](https://community.homey.app/u/TheWiZZz)\
**Post date:** [November 10, 2026, 1:00pm UTC](https://community.homey.app/t/app-pro-hikvision-nvr-dvr-every-camera-one-recorder-full-control-looking-for-testers/159939/40 "2026-11-10T13:00:23Z")

</div>

Hi Zdenda,

Thanks for the suggestion. I’ve added a separate **Last ring** image in version **5.3.0**. It appears next to **Snapshot** after the first successful capture. Snapshot shows a current view, and Last ring lets you see who rang when you missed the notification.

[https://homey.app/a/com.wisse.hikvision/test/](https://homey.app/a/com.wisse.hikvision/test/)

Your doorbell saves the photo automatically. The same successful capture goes to your Flow and to Last ring. Homey stores one encrypted photo per device and restores it after an app restart. The next successful capture replaces it. If a capture fails, the previous successful photo stays available.

I also added a Flow card for setups where a separate doorbell sensor triggers a camera. Both those setups and doorbells with native button events can now use Last ring.

Once 5.3.0 is on Test, please update through [the Homey test link](https://homey.app/a/com.wisse.hikvision/test/), ring the bell once and open Last ring on your existing doorbell. If you get a chance, restart the Hikvision app to check that the photo is still there.

Best regards,  
Wisse

[Previous page](https://community.homey.app/t/app-pro-hikvision-nvr-dvr-every-camera-one-recorder-full-control-looking-for-testers/159939.md?page=1)

[Next page](https://community.homey.app/t/app-pro-hikvision-nvr-dvr-every-camera-one-recorder-full-control-looking-for-testers/159939.md?page=3)
