Camera ONVIF motion binary sensor doesn't clear

[Nikotine]

I have a Hikvision DS-2CD2087G2-L(U) and have ONVIF enabled.
The camera has been setup to do intrusion detection and inform the surveillance center.



In Home Assistant there’s a binary sensor called binary_sensor.myfielddetector1_field_detection and that goes from clear to detected when there is intrusion detected, but only once…
It never resets:



I can only get it to reset if I reboot the camera or Home Assistant.
Would this be something wrong with the camera, or home assistant?
Any way of testing this?

 

[alastairstevenson]

Any way of testing this?

You can review the ONVIF events generated by the camera in the 'Events' page of ONVIF Device Manager.
Give ODM some valid logon credentials, top left of the window, and it will automatically find any ONVIF device on the same IP address range as the PC.

Onvif Device Manager v2.2.250

Neat program for finding multiple brands of cameras that are ONVIF conformant on your network. You can also type in the username and password of your device at the top of the program to connect to a device. Once connected it displays multiple fields to edit such as image quality, picture...

ipcamtalk.com

 

[IAmATeaf]

Isn’t the problem that you are using a binary sensor which can only have an on/off state?

Don’t have or use Home Assistant but is that not another sensor that can be used?

 

[Nikotine]

You can review the ONVIF events generated by the camera in the 'Events' page of ONVIF Device Manager.
Give ODM some valid logon credentials, top left of the window, and it will automatically find any ONVIF device on the same IP address range as the PC.

Thanks. This learned me that the camera is indeed sending both messages when the detection starts and stops:

Isn’t the problem that you are using a binary sensor which can only have an on/off state?

Yes, but that's the point I guess? It needs to go to true when a person is detected and go back to false shortly after the person is gone.

But since the message seems to be sending the correct messages, I guess it's an issue with Home Assistant. I will take it up on their forum.

 

[Nikotine]

After some further testing, it seems that the camera actually never sends the "IsInside: false" change message, only when initialized.
You can see it retriggering the "IsInside: true" message when I'm walking in front of the camera, but it never sends the "false" again...
I don't know if this is intended behaviour, but it makes that I can't program any actions for when a human is detected.

 

[Mike A.]

I don't use HA either, but Is there a "false" event sent by the cam after a typical trigger? That is, the camera may send a false back when queried as a test during initialization. And it obviously sends an alert when triggered. But I don't know that most ever actively send an end-state for that same event? Assuming that's the case, then you'd need to handle that outside of the camera through whatever scripting is done for HA using some time-out interval and/or test sent to the cam again as during the initialization. It obviously can be tested since it's reported back during the initialization.

 

[Nikotine]

Thanks, I'll check if Home Assistant can reset the state after x seconds.

 

[alastairstevenson]

After some further testing, it seems that the camera actually never sends the "IsInside: false" change message, only when initialized.

For curiosity, I tried this on a totally different camera/firmware, an R0 5.4.5 device, and the ONVIF notification did provide a 'false' status for intrusion detection / aka Field detection.
Maybe what you're seeing is down to a firmware flaw.
See below :

 

[Nikotine]

Yes, my Amcrest doorbell does this as well correctly:


But the Hikvision camera does not unfortunately.
I'm more and more regretting having gone for Hikvision.

 

[alastairstevenson]

But the Hikvision camera does not unfortunately.
I'm more and more regretting having gone for Hikvision.

I tested this on a DS-2CD2087G2-LU and got the same result as you, no 'IsInside : false' events
The firmware is IPC_G3_EN_STD_5.5.160_210209

There are multiple versions of the G3 firmware, some associated with hardware variations, so it's a bit of a minefield.

 

[Nikotine]

I recently updated to V5.5.800 build 210628, after a needlessly complex hunt for the right firmware.
Our camera is one of those affected by this security leak, so make sure you update yours as well.
I don't believe it's critical when you don't expose your camera to the internet, but still.

Mine is the "worldwide region" version, but none of the firmwares published on Hikvision Global, Hikvision Europe, Hikvision UK... worked.
It simply didn't want to flash it.
Eventually, after an epic dig through numerous websites, I ended up here:

https://www.hikvisioneurope.com/eu/portal/

The firmware that worked was dug in several layers deep:
Home » portal » Technical Materials » 00 Network Camera » 00 Product Firmware » G3 platform(2XX6G2 3XX6G2 2XX7G2 2XX6G0) » DS-2CD2XX6G2,2XX7G2 Models » V5.5.800 build210628

Along the way, they try to divert you into dead-end paths, it's incredible how ill-documented this all is.

 

[Nikotine]

Solution for resetting detected motion with Home Assistant is given here: Add off_delay to binary sensor added via UI

 

[spammenotinoz]

I recently updated to V5.5.800 build 210628, after a needlessly complex hunt for the right firmware.
Our camera is one of those affected by this security leak, so make sure you update yours as well.
I don't believe it's critical when you don't expose your camera to the internet, but still.

Mine is the "worldwide region" version, but none of the firmwares published on Hikvision Global, Hikvision Europe, Hikvision UK... worked.
It simply didn't want to flash it.
Eventually, after an epic dig through numerous websites, I ended up here:

https://www.hikvisioneurope.com/eu/portal/

The firmware that worked was dug in several layers deep:
Home » portal » Technical Materials » 00 Network Camera » 00 Product Firmware » G3 platform(2XX6G2 3XX6G2 2XX7G2 2XX6G0) » DS-2CD2XX6G2,2XX7G2 Models » V5.5.800 build210628

Along the way, they try to divert you into dead-end paths, it's incredible how ill-documented this all is.

Thank-you, I spent hours downloading and trying different firmware. I have the WR version, but they call failed with "mismatch". You are a legend for finding this.

 

[Nikotine]

Thank-you, I spent hours downloading and trying different firmware. I have the WR version, but they call failed with "mismatch". You are a legend for finding this.

Glad I could help!