01304 827609 info@use-ip.co.uk Find us

Firmware M-Series Firmware v5.03 Released

Update on this issue - Hikvision have told me that this fix has been postponed until the next M-Series firmware update.

Here's their reply to me:


I'll test and confirm when the new version is released.
Just an update to say that the intercom device compatibility has been fixed on V5.04.050 build 250124.

You now need to add the doorbell as an Access Control Device rather than a Video Device and use the 'HIKVISION' protocol type, which should allow you to set motion detection and motion-based recording on the doorbell's camera:

1741087517368.png


If you have any feedback about this firmware, please feel free to post in this dedicated thread:
 
Just an update to say that the intercom device compatibility has been fixed on V5.04.050 build 250124.

You now need to add the doorbell as an Access Control Device rather than a Video Device and use the 'HIKVISION' protocol type, which should allow you to set motion detection and motion-based recording on the doorbell's camera:

View attachment 12591

If you have any feedback about this firmware, please feel free to post in this dedicated thread:

Great to see a release with a fix. Just about to update myself.

To confirm, the intercom needs to be added as an access device for motion detection, but to have it record the video the NVR, it still needs to be added as a video device correct? And is it still added as a "manual" device using HIKVISION protocol, and not plug-and-play?
Also, should the motion detection be enabled through the NVR, or directly on the intercom?
 
Last edited:
Great to see a release with a fix. Just about to update myself.

To confirm, the intercom needs to be added as an access device for motion detection, but to have it record the video the NVR, it still needs to be added as a video device correct? And is it still added as a "manual" device using HIKVISION protocol, and not plug-and-play?
Also, should the motion detection be enabled through the NVR, or directly on the intercom?
Nope, there is no need to add it as a video device now, you just add it as an Access Control device which will let you record video and set up motion detection.

And is it still added as a "manual" device using HIKVISION protocol, and not plug-and-play?
Correct, this will always be the case for intercom devices as they need to have their own connection to the network to work (via a POE switch or WiFi).

Also, should the motion detection be enabled through the NVR, or directly on the intercom?
Through the NVR :)
 
Nope, there is no need to add it as a video device now, you just add it as an Access Control device which will let you record video and set up motion detection.


Correct, this will always be the case for intercom devices as they need to have their own connection to the network to work (via a POE switch or WiFi).


Through the NVR :)
Thanks. Added and now the doorbell is both recording and motion detection options are available.

One thing to be aware, by default, all channels on the NVR are set to POE so when you add the device as an "access control device" it won't be added automatically as a "video device". I had to go into Devices > Poe and disable one of the channels from being POE, and then this time it worked as expected.
Makes sense I guess, since we don't need POE for the intercom/doorbell since it's powered by it's own poe switch.

Will try the basic motion detection setting tomorrow, to see if any good and worth keeping enabled.
 
Ive added mine as an Access control device however it shows as Offline in my access control device list, If I add it as a Video device it shows as 'Online"

Any ideas?
Screenshot 2025-03-28 at 12.06.40.png
 
Ive added mine as an Access control device however it shows as Offline in my access control device list, If I add it as a Video device it shows as 'Online"

Any ideas?View attachment 12702
@stuhope123 - it might be best to copy and paste your post to the dedicated 5.04.050 thread - I've just posted similar there as it seems that the new intercom firmware has broke it again. I've also mentioned it in another thread.
 
Back
Top