Hikvision PIR Alarm NULL in OH

Add-ons Bindings
1

Hi,
i have a configuration of a few Hikvision cameras and for avoiding fals alarm I use the motion detection and PIR alarm for lightning up the room.
Te issue is, that with model DS-2CD2443G2-I the PIR Alarm channel is not working, it is NULL, while with the same settings on DS-2CD2432F-IW it works perfectly.

Do anyone has experienced, solved this?

P.S. latest firmware on the cameras.

Thank you

2

What does the trace log show? Since you have one working and one not working you can compare the trace level log and narrow it down.

3

Thank you for your reply matt1!

I made a little research on Hikvision website and I found the explanation:
„Beginning in June of 2022, the product(s) below will no longer contain the CGI protocol: All Hikvision IP cameras, including PTZ cameras.
There are two alternatives to the CGI protocol:

  • ISAPI (Hikvision’s proprietary protocol), enabled by default, which is an open, secure and
    effective protocol that is more flexible to develop and has been supported largely by numerous
    partners around the world. Furthermore, it is the best way to get the most advanced
    functionalities from Hikvision hardware.
  • ONVIF, disabled by default beginning with firmware version 5.5.0 or later, but can be enabled by users via the camera’s web interface”

So, my camera sending the PIR alarm is version 5.4.5, the ones not working are 5.5.0.
I checked in Hik-connect software and there the PIR alarm is received from ALL cameras.

This leads to my conclusion, that the Hikvision IP Cam Binding should be adjusted, so it is line with the changes of Hikvision on their IP cameras.

Should I post this under a particular topic?

thanks

4

Always post in a new thread which you have done already here, thanks.

The binding already is using ISAPI, all events are getting streamed to the binding from this URL

/ISAPI/Event/notification/alertStream

I would first contact HIK support, as this may be a bug in their firmware and letting them know to look into it whilst the camera is still getting updates is very important to do.

Also since you have not posted any TRACE level logs from when your trying to trigger the PIR, I can not comment on if the camera is or is not sending any data. Its possible it is any something needs to be changed in the binding. Without log output we are only guessing and wasting time.

5

Thanks Skinah

The camera is sending it for sure, since i see it in the Hik-connect software, regardelss the fw version of the cameras, it is just that for the newer version is sending it somehow differently.
Anyway, how do i enable the trace.log? I use the OH in docker on a Qnap Nas.

Thanks

6

It’s the very first section of the bindings manual on how to get trace logs.

7

14:35:22.084 [INFO ] [openhab.event.ItemStateChangedEvent ] - Item ‘Cam_Kitchen_Motion_Alarm’ changed from OFF to ON
14:35:22.229 [TRACE] [ng.ipcamera.internal.HikvisionHandler] - HTTP Result back from camera is :–boundary
Content-Type: application/xml; charset=“UTF-8”
Content-Length: 480

192.168.1.15 80 HTTP c4:2f:90:20:c2:97 1 2024-10-12T14:35:21+02:00 0 videoloss inactive videoloss alarm : 14:35:22.531 [TRACE] [ng.ipcamera.internal.HikvisionHandler] - HTTP Result back from camera is :--boundary Content-Type: application/xml; charset="UTF-8" Content-Length: 480 192.168.1.15 80 HTTP c4:2f:90:20:c2:97 1 2024-10-12T14:35:22+02:00 0 videoloss inactive videoloss alarm : 14:35:22.685 [TRACE] [ng.ipcamera.internal.HikvisionHandler] - HTTP Result back from camera is :--boundary-- --boundary Content-Type: application/xml; charset="UTF-8" Content-Length: 574 192.168.1.13 ::ffff:192.168.1.13 80 HTTP bc:9b:5e:74:d3:99 1 2024-10-12T14:35:22+02:00 1 fielddetection inactive fielddetection alarm Kitchen

:
14:35:22.686 [INFO ] [openhab.event.ItemStateChangedEvent ] - Item ‘Cam_Kitchen_Field_Alarm’ changed from OFF to ON
14:35:22.686 [INFO ] [openhab.event.ItemCommandEvent ] - Item ‘LED_Kitchen_Color’ received command 25,65,100
14:35:22.687 [INFO ] [openhab.event.ItemStatePredictedEvent] - Item ‘LED_Kitchen_Color’ predicted to become 25,65,100
14:35:22.838 [TRACE] [ng.ipcamera.internal.HikvisionHandler] - HTTP Result back from camera is :–boundary
Content-Type: application/xml; charset=“UTF-8”
Content-Length: 480

192.168.1.15 80 HTTP c4:2f:90:20:c2:97 1 2024-10-12T14:35:22+02:00 0 videoloss inactive videoloss alarm : 14:35:23.081 [TRACE] [ng.ipcamera.internal.HikvisionHandler] - HTTP Result back from camera is :--boundary --boundary Content-Type: application/xml; charset="UTF-8" Content-Length: 593 <?xml version="1.0" encoding="UTF-8"?> 192.168.1.13 ::ffff:192.168.1.13 80 HTTP bc:9b:5e:74:d3:99 1 2024-10-12T14:35:22+02:00 1 VMD active Motion alarm Kitchen

:
14:35:23.145 [TRACE] [ng.ipcamera.internal.HikvisionHandler] - HTTP Result back from camera is :–boundary
Content-Type: application/xml; charset=“UTF-8”
Content-Length: 480

192.168.1.15 80 HTTP c4:2f:90:20:c2:97 1 2024-10-12T14:35:22+02:00 0 videoloss inactive videoloss alarm : 14:35:23.449 [TRACE] [ng.ipcamera.internal.HikvisionHandler] - HTTP Result back from camera is :--boundary Content-Type: application/xml; charset="UTF-8" Content-Length: 480 192.168.1.15 80 HTTP c4:2f:90:20:c2:97 1 2024-10-12T14:35:23+02:00 0 videoloss inactive videoloss alarm : 14:35:23.751 [TRACE] [ng.ipcamera.internal.HikvisionHandler] - HTTP Result back from camera is :--boundary Content-Type: application/xml; charset="UTF-8" Content-Length: 480 192.168.1.15 80 HTTP c4:2f:90:20:c2:97 1 2024-10-12T14:35:23+02:00 0 videoloss inactive videoloss alarm : 14:35:24.053 [TRACE] [ng.ipcamera.internal.HikvisionHandler] - HTTP Result back from camera is :--boundary Content-Type: application/xml; charset="UTF-8" Content-Length: 480 192.168.1.15 80 HTTP c4:2f:90:20:c2:97 1 2024-10-12T14:35:23+02:00 0 videoloss inactive videoloss alarm : 14:35:24.094 [TRACE] [ng.ipcamera.internal.HikvisionHandler] - HTTP Result back from camera is :--boundary-- --boundary Content-Type: application/xml; charset="UTF-8" Content-Length: 593 <?xml version="1.0" encoding="UTF-8"?> 192.168.1.13 ::ffff:192.168.1.13 80 HTTP bc:9b:5e:74:d3:99 1 2024-10-12T14:35:23+02:00 1 VMD active Motion alarm Kitchen

:
14:35:24.095 [INFO ] [openhab.event.ItemStateChangedEvent ] - Item ‘Cam_Kitchen_Field_Alarm’ changed from ON to OFF
14:35:24.354 [TRACE] [ng.ipcamera.internal.HikvisionHandler] - HTTP Result back from camera is :–boundary
Content-Type: application/xml; charset=“UTF-8”
Content-Length: 480

192.168.1.15 80 HTTP c4:2f:90:20:c2:97 1 2024-10-12T14:35:24+02:00 0 videoloss inactive videoloss alarm : 14:35:24.656 [TRACE] [ng.ipcamera.internal.HikvisionHandler] - HTTP Result back from camera is :--boundary Content-Type: application/xml; charset="UTF-8" Content-Length: 480 192.168.1.15 80 HTTP c4:2f:90:20:c2:97 1 2024-10-12T14:35:24+02:00 0 videoloss inactive videoloss alarm : 14:35:24.703 [TRACE] [mera.internal.handler.IpCameraHandler] - Sending camera: GET: http://192.168.1.13:80/ISAPI/System/IO/inputs/1/status 14:35:24.710 [WARN ] [.ipcamera.internal.MyNettyAuthHandler] - 403 Forbidden: Check camera setup or has the camera activated the illegal login lock? 14:35:24.711 [TRACE] [ng.ipcamera.internal.HikvisionHandler] - HTTP Result back from camera is :<?xml version="1.0" encoding="UTF-8"?> 4 Invalid Operation invalidOperation : 14:35:24.958 [TRACE] [ng.ipcamera.internal.HikvisionHandler] - HTTP Result back from camera is :--boundary Content-Type: application/xml; charset="UTF-8" Content-Length: 480 192.168.1.15 80 HTTP c4:2f:90:20:c2:97 1 2024-10-12T14:35:24+02:00 0 videoloss inactive videoloss alarm : 14:35:25.100 [TRACE] [ng.ipcamera.internal.HikvisionHandler] - HTTP Result back from camera is :--boundary-- --boundary Content-Type: application/xml; charset="UTF-8" Content-Length: 593 <?xml version="1.0" encoding="UTF-8"?> 192.168.1.13 ::ffff:192.168.1.13 80 HTTP bc:9b:5e:74:d3:99 1 2024-10-12T14:35:24+02:00 1 VMD active Motion alarm Kitchen

:
14:35:25.260 [TRACE] [ng.ipcamera.internal.HikvisionHandler] - HTTP Result back from camera is :–boundary
Content-Type: application/xml; charset=“UTF-8”
Content-Length: 480

192.168.1.15 80 HTTP c4:2f:90:20:c2:97 1 2024-10-12T14:35:25+02:00 0 videoloss inactive videoloss alarm : 14:35:25.566 [TRACE] [ng.ipcamera.internal.HikvisionHandler] - HTTP Result back from camera is :--boundary Content-Type: application/xml; charset="UTF-8" Content-Length: 480 192.168.1.15 80 HTTP c4:2f:90:20:c2:97 1 2024-10-12T14:35:25+02:00 0 videoloss inactive videoloss alarm : 14:35:25.869 [TRACE] [ng.ipcamera.internal.HikvisionHandler] - HTTP Result back from camera is :--boundary Content-Type: application/xml; charset="UTF-8" Content-Length: 480 192.168.1.15 80 HTTP c4:2f:90:20:c2:97 1 2024-10-12T14:35:25+02:00 0 videoloss inactive videoloss alarm : 14:35:26.172 [TRACE] [ng.ipcamera.internal.HikvisionHandler] - HTTP Result back from camera is :--boundary Content-Type: application/xml; charset="UTF-8" Content-Length: 480 192.168.1.15 80 HTTP c4:2f:90:20:c2:97 1 2024-10-12T14:35:25+02:00 0 videoloss inactive videoloss alarm : 14:35:26.475 [TRACE] [ng.ipcamera.internal.HikvisionHandler] - HTTP Result back from camera is :--boundary Content-Type: application/xml; charset="UTF-8" Content-Length: 480 192.168.1.15 80 HTTP c4:2f:90:20:c2:97 1 2024-10-12T14:35:26+02:00 0 videoloss inactive videoloss alarm : 14:35:26.779 [TRACE] [ng.ipcamera.internal.HikvisionHandler] - HTTP Result back from camera is :--boundary Content-Type: application/xml; charset="UTF-8" Content-Length: 480 192.168.1.15 80 HTTP c4:2f:90:20:c2:97 1 2024-10-12T14:35:26+02:00 0 videoloss inactive videoloss alarm : 14:35:27.082 [TRACE] [ng.ipcamera.internal.HikvisionHandler] - HTTP Result back from camera is :--boundary Content-Type: application/xml; charset="UTF-8" Content-Length: 480 192.168.1.15 80 HTTP c4:2f:90:20:c2:97 1 2024-10-12T14:35:26+02:00 0 videoloss inactive videoloss alarm : 14:35:27.384 [TRACE] [ng.ipcamera.internal.HikvisionHandler] - HTTP Result back from camera is :--boundary Content-Type: application/xml; charset="UTF-8" Content-Length: 480 192.168.1.15 80 HTTP c4:2f:90:20:c2:97 1 2024-10-12T14:35:27+02:00 0 videoloss inactive videoloss alarm : 14:35:27.688 [TRACE] [ng.ipcamera.internal.HikvisionHandler] - HTTP Result back from camera is :--boundary Content-Type: application/xml; charset="UTF-8" Content-Length: 480 192.168.1.15 80 HTTP c4:2f:90:20:c2:97 1 2024-10-12T14:35:27+02:00 0 videoloss inactive videoloss alarm : 14:35:27.993 [TRACE] [ng.ipcamera.internal.HikvisionHandler] - HTTP Result back from camera is :--boundary Content-Type: application/xml; charset="UTF-8" Content-Length: 480 192.168.1.15 80 HTTP c4:2f:90:20:c2:97 1 2024-10-12T14:35:27+02:00 0 videoloss inactive videoloss alarm : 14:35:28.296 [TRACE] [ng.ipcamera.internal.HikvisionHandler] - HTTP Result back from camera is :--boundary Content-Type: application/xml; charset="UTF-8" Content-Length: 480 192.168.1.15 80 HTTP c4:2f:90:20:c2:97 1 2024-10-12T14:35:28+02:00 0 videoloss inactive videoloss alarm : 14:35:28.598 [TRACE] [ng.ipcamera.internal.HikvisionHandler] - HTTP Result back from camera is :--boundary Content-Type: application/xml; charset="UTF-8" Content-Length: 480 192.168.1.15 80 HTTP c4:2f:90:20:c2:97 1 2024-10-12T14:35:28+02:00 0 videoloss inactive videoloss alarm : 14:35:28.901 [TRACE] [ng.ipcamera.internal.HikvisionHandler] - HTTP Result back from camera is :--boundary Content-Type: application/xml; charset="UTF-8" Content-Length: 480 192.168.1.15 80 HTTP c4:2f:90:20:c2:97 1 2024-10-12T14:35:28+02:00 0 videoloss inactive videoloss alarm : 14:35:29.207 [TRACE] [ng.ipcamera.internal.HikvisionHandler] - HTTP Result back from camera is :--boundary Content-Type: application/xml; charset="UTF-8" Content-Length: 480 192.168.1.15 80 HTTP c4:2f:90:20:c2:97 1 2024-10-12T14:35:28+02:00 0 videoloss inactive videoloss alarm : 14:35:29.508 [TRACE] [ng.ipcamera.internal.HikvisionHandler] - HTTP Result back from camera is :--boundary Content-Type: application/xml; charset="UTF-8" Content-Length: 480 192.168.1.15 80 HTTP c4:2f:90:20:c2:97 1 2024-10-12T14:35:29+02:00 0 videoloss inactive videoloss alarm : 14:35:29.811 [TRACE] [ng.ipcamera.internal.HikvisionHandler] - HTTP Result back from camera is :--boundary Content-Type: application/xml; charset="UTF-8" Content-Length: 480 192.168.1.15 80 HTTP c4:2f:90:20:c2:97 1 2024-10-12T14:35:29+02:00 0 videoloss inactive videoloss alarm : 14:35:30.012 [TRACE] [mera.internal.handler.IpCameraHandler] - Sending camera: GET: http://192.168.1.15:80/ISAPI/System/IO/inputs/1/status 14:35:30.033 [TRACE] [ng.ipcamera.internal.HikvisionHandler] - HTTP Result back from camera is :<?xml version="1.0" encoding="UTF-8"?> 1 input inactive : 14:35:30.113 [TRACE] [ng.ipcamera.internal.HikvisionHandler] - HTTP Result back from camera is :--boundary Content-Type: application/xml; charset="UTF-8" Content-Length: 520 192.168.1.15 80 HTTP c4:2f:90:20:c2:97 1 2024-10-12T14:35:29+02:00 51128 VMD active Motion alarm : 14:35:30.114 [INFO ] [openhab.event.ItemStateChangedEvent ] - Item 'Cam_test_Motion_Alarm' changed from OFF to ON 14:35:30.417 [TRACE] [ng.ipcamera.internal.HikvisionHandler] - HTTP Result back from camera is :--boundary Content-Type: application/xml; charset="UTF-8" Content-Length: 520 192.168.1.15 80 HTTP c4:2f:90:20:c2:97 1 2024-10-12T14:35:30+02:00 51129 VMD active Motion alarm : 14:35:30.723 [TRACE] [ng.ipcamera.internal.HikvisionHandler] - HTTP Result back from camera is :--boundary Content-Type: application/xml; charset="UTF-8" Content-Length: 520 192.168.1.15 80 HTTP c4:2f:90:20:c2:97 1 2024-10-12T14:35:30+02:00 51130 VMD active Motion alarm : 14:35:31.029 [TRACE] [ng.ipcamera.internal.HikvisionHandler] - HTTP Result back from camera is :--boundary Content-Type: application/xml; charset="UTF-8" Content-Length: 520 192.168.1.15 80 HTTP c4:2f:90:20:c2:97 1 2024-10-12T14:35:30+02:00 51131 VMD active Motion alarm : 14:35:31.331 [TRACE] [ng.ipcamera.internal.HikvisionHandler] - HTTP Result back from camera is :--boundary Content-Type: application/xml; charset="UTF-8" Content-Length: 520 192.168.1.15 80 HTTP c4:2f:90:20:c2:97 1 2024-10-12T14:35:31+02:00 51132 VMD active Motion alarm : 14:35:31.633 [TRACE] [ng.ipcamera.internal.HikvisionHandler] - HTTP Result back from camera is :--boundary Content-Type: application/xml; charset="UTF-8" Content-Length: 520 192.168.1.15 80 HTTP c4:2f:90:20:c2:97 1 2024-10-12T14:35:31+02:00 51133 VMD active Motion alarm : 14:35:31.931 [TRACE] [ng.ipcamera.internal.HikvisionHandler] - HTTP Result back from camera is :--boundary-- --boundary Content-Type: application/xml; charset="UTF-8" Content-Length: 547 192.168.1.13 :: 80 HTTP bc:9b:5e:74:d3:99 1 2024-10-12T14:35:31+02:00 1 videoloss inactive videoloss alarm Kitchen : 14:35:31.932 [INFO ] [openhab.event.ItemStateChangedEvent ] - Item 'Cam_Kitchen_Motion_Alarm' changed from ON to OFF 14:35:31.936 [TRACE] [ng.ipcamera.internal.HikvisionHandler] - HTTP Result back from camera is :--boundary Content-Type: application/xml; charset="UTF-8" Content-Length: 520 192.168.1.15 80 HTTP c4:2f:90:20:c2:97 1 2024-10-12T14:35:31+02:00 51134 VMD active Motion alarm : 14:35:32.237 [TRACE] [ng.ipcamera.internal.HikvisionHandler] - HTTP Result back from camera is :--boundary Content-Type: application/xml; charset="UTF-8" Content-Length: 520 192.168.1.15 80 HTTP c4:2f:90:20:c2:97 1 2024-10-12T14:35:31+02:00 51135 VMD active Motion alarm : 14:35:32.541 [TRACE] [ng.ipcamera.internal.HikvisionHandler] - HTTP Result back from camera is :--boundary Content-Type: application/xml; charset="UTF-8" Content-Length: 520 192.168.1.15 80 HTTP c4:2f:90:20:c2:97 1 2024-10-12T14:35:32+02:00 51136 VMD active Motion alarm : 14:35:32.705 [TRACE] [mera.internal.handler.IpCameraHandler] - Sending camera: GET: http://192.168.1.13:80/ISAPI/System/IO/inputs/1/status 14:35:32.710 [WARN ] [.ipcamera.internal.MyNettyAuthHandler] - 403 Forbidden: Check camera setup or has the camera activated the illegal login lock? 14:35:32.710 [TRACE] [ng.ipcamera.internal.HikvisionHandler] - HTTP Result back from camera is :<?xml version="1.0" encoding="UTF-8"?> 4 Invalid Operation invalidOperation : 14:35:32.844 [TRACE] [ng.ipcamera.internal.HikvisionHandler] - HTTP Result back from camera is :--boundary Content-Type: application/xml; charset="UTF-8" Content-Length: 520 192.168.1.15 80 HTTP c4:2f:90:20:c2:97 1 2024-10-12T14:35:32+02:00 51137 VMD active Motion alarm : 14:35:33.146 [TRACE] [ng.ipcamera.internal.HikvisionHandler] - HTTP Result back from camera is :--boundary Content-Type: application/xml; charset="UTF-8" Content-Length: 520 192.168.1.15 80 HTTP c4:2f:90:20:c2:97 1 2024-10-12T14:35:32+02:00 51138 VMD active Motion alarm : 14:35:33.452 [TRACE] [ng.ipcamera.internal.HikvisionHandler] - HTTP Result back from camera is :--boundary Content-Type: application/xml; charset="UTF-8" Content-Length: 520 192.168.1.15 80 HTTP c4:2f:90:20:c2:97 1 2024-10-12T14:35:33+02:00 51139 VMD active Motion alarm : 14:35:33.756 [TRACE] [ng.ipcamera.internal.HikvisionHandler] - HTTP Result back from camera is :--boundary Content-Type: application/xml; charset="UTF-8" Content-Length: 520 192.168.1.15 80 HTTP c4:2f:90:20:c2:97 1 2024-10-12T14:35:33+02:00 51140 VMD active Motion alarm : 14:35:33.993 [INFO ] [openhab.event.ItemStateChangedEvent ] - Item 'LED_Kitchen_Color' changed from 25,65,100 to 24.939758777618408203125000,65.098041296005249023437500,100 14:35:34.063 [TRACE] [ng.ipcamera.internal.HikvisionHandler] - HTTP Result back from camera is :--boundary Content-Type: application/xml; charset="UTF-8" Content-Length: 520 192.168.1.15 80 HTTP c4:2f:90:20:c2:97 1 2024-10-12T14:35:33+02:00 51141 VMD active Motion alarm : 14:35:34.256 [INFO ] [openhab.event.ItemCommandEvent ] - Item 'LED_Kitchen_Color' received command 280,100,1 14:35:34.256 [INFO ] [openhab.event.ItemStatePredictedEvent] - Item 'LED_Kitchen_Color' predicted to become 280,100,1 14:35:34.260 [INFO ] [openhab.event.ItemStateChangedEvent ] - Item 'LED_Kitchen_Color' changed from 24.939758777618408203125000,65.098041296005249023437500,100 to 280,100,1 14:35:34.364 [TRACE] [ng.ipcamera.internal.HikvisionHandler] - HTTP Result back from camera is :--boundary Content-Type: application/xml; charset="UTF-8" Content-Length: 520 192.168.1.15 80 HTTP c4:2f:90:20:c2:97 1 2024-10-12T14:35:34+02:00 51142 VMD active Motion alarm : 14:35:34.669 [TRACE] [ng.ipcamera.internal.HikvisionHandler] - HTTP Result back from camera is :--boundary Content-Type: application/xml; charset="UTF-8" Content-Length: 520 192.168.1.15 80 HTTP c4:2f:90:20:c2:97 1 2024-10-12T14:35:34+02:00 51143 VMD active Motion alarm : 14:35:34.975 [TRACE] [ng.ipcamera.internal.HikvisionHandler] - HTTP Result back from camera is :--boundary Content-Type: application/xml; charset="UTF-8" Content-Length: 520 192.168.1.15 80 HTTP c4:2f:90:20:c2:97 1 2024-10-12T14:35:34+02:00 51144 VMD active Motion alarm : 14:35:35.279 [TRACE] [ng.ipcamera.internal.HikvisionHandler] - HTTP Result back from camera is :--boundary Content-Type: application/xml; charset="UTF-8" Content-Length: 520 192.168.1.15 80 HTTP c4:2f:90:20:c2:97 1 2024-10-12T14:35:35+02:00 51145 VMD active Motion alarm : 14:35:35.581 [TRACE] [ng.ipcamera.internal.HikvisionHandler] - HTTP Result back from camera is :--boundary Content-Type: application/xml; charset="UTF-8" Content-Length: 520 192.168.1.15 80 HTTP c4:2f:90:20:c2:97 1 2024-10-12T14:35:35+02:00 51146 VMD active Motion alarm : 14:35:35.884 [TRACE] [ng.ipcamera.internal.HikvisionHandler] - HTTP Result back from camera is :--boundary Content-Type: application/xml; charset="UTF-8" Content-Length: 480 192.168.1.15 80 HTTP c4:2f:90:20:c2:97 1 2024-10-12T14:35:35+02:00 0 videoloss inactive videoloss alarm : 14:35:35.885 [INFO ] [openhab.event.ItemStateChangedEvent ] - Item 'Cam_test_Motion_Alarm' changed from ON to OFF 14:35:36.185 [TRACE] [ng.ipcamera.internal.HikvisionHandler] - HTTP Result back from camera is :--boundary Content-Type: application/xml; charset="UTF-8" Content-Length: 480 192.168.1.15 80 HTTP c4:2f:90:20:c2:97 1 2024-10-12T14:35:35+02:00 0 videoloss inactive videoloss alarm : 14:35:36.488 [TRACE] [ng.ipcamera.internal.HikvisionHandler] - HTTP Result back from camera is :--boundary Content-Type: application/xml; charset="UTF-8" Content-Length: 480 192.168.1.15 80 HTTP c4:2f:90:20:c2:97 1 2024-10-12T14:35:36+02:00 0 videoloss inactive videoloss alarm : 14:35:36.789 [TRACE] [ng.ipcamera.internal.HikvisionHandler] - HTTP Result back from camera is :--boundary Content-Type: application/xml; charset="UTF-8" Content-Length: 480 192.168.1.15 80 HTTP c4:2f:90:20:c2:97 1 2024-10-12T14:35:36+02:00 0 videoloss inactive videoloss alarm : 14:35:37.093 [TRACE] [ng.ipcamera.internal.HikvisionHandler] - HTTP Result back from camera is :--boundary Content-Type: application/xml; charset="UTF-8" Content-Length: 480 192.168.1.15 80 HTTP c4:2f:90:20:c2:97 1 2024-10-12T14:35:36+02:00 0 videoloss inactive videoloss alarm : 14:35:37.397 [TRACE] [ng.ipcamera.internal.HikvisionHandler] - HTTP Result back from camera is :--boundary Content-Type: application/xml; charset="UTF-8" Content-Length: 480 192.168.1.15 80 HTTP c4:2f:90:20:c2:97 1 2024-10-12T14:35:37+02:00 0 videoloss inactive videoloss alarm : openhab>

openhab>

14:42:28.794 [TRACE] [ng.ipcamera.internal.HikvisionHandler] - HTTP Result back from camera is :–boundary
Content-Type: application/xml; charset=“UTF-8”
Content-Length: 470

192.168.1.15 80 HTTP c4:2f:90:20:c2:97 1 2024-10-12T14:42:28+02:00 21517 PIR active PIR alarm : 14:42:28.796 [INFO ] [openhab.event.ItemStateChangedEvent ] - Item 'Cam_test_PIR_Alarm' changed from OFF to ON 14:42:29.096 [TRACE] [ng.ipcamera.internal.HikvisionHandler] - HTTP Result back from camera is :--boundary Content-Type: application/xml; charset="UTF-8" Content-Length: 520 192.168.1.15 80 HTTP c4:2f:90:20:c2:97 1 2024-10-12T14:42:29+02:00 51274 VMD active Motion alarm
8

Dear Skinah, this is what you reffered to?
The IPcam I dont get the PIR alarm from in OH has the IP ending in 13 (Cam_Kitchen), while the one working flawlessly is ending in 15 (Cam_test).

Thank you

9

I haven’t find a solution yet. Are this the trace logs helpful/ complete for you to have an opinion?

PIR_not_working.txt (942 Bytes)
PIR_working.txt (1.5 KB)

10

The logs are short so I’m guessing you have sesrched for PIR being mentioned in the non working camera? It would appear the camera does not send the event so it may need to be turned in in the cameras settings or the firmware changed. Hikvision is known for Grey imports and preventing firmware from going into cheap imports and unlocking gestures, so make sure you know the camera and firmware is correct.

11

Thanks for your answer.
Indeed, I searched for PIR and camera is not sending it. I seems it is a firmware issue, from ver. 5.5.0 onwards.
I`ll try Hikvision support and post back here if other solution then downgrade is applicable.
Thanks for you help for now.

Also, one more question popped out my head, ONVIF should be capable of sending also PIR alarm? I noticed that the generic ONVIF camera binding doesn’t have such channel. Thanks

12

that is up to the camera firmware, some cameras do send PIR alarms to onvif, whilst others sometimes use the PIR to ensure the motion alarm triggers less often as the PIR has to agree with the movement. Completely up to the person writting the firmware of the camera.

13

Thank you for your support

14

Ok. But i didn’t find any reference to PIR channel in the generic ONVIF binding. If the camera would send the PIR, how is the binding reading it ?

15

The binding will log any unknown alarms and you just need to report what is in the logs and the alarm type can be added very quickly. I guess no one has reported their camera does this for PIR yet. For your working camera do you mind looking to see if it does this when setup as a ONVIF thing type with DEBUG level logs? You can leave your camera paused and un-touched, just set up a ONVIF thing quickly and then delete the extra thing.

The log should get this with the data I need filled in
ONVIF Event Topic: {}, Data: {}, Value: {}