Tamper Detection from Bosch Camera is not listed in available Events
Completed
Hi,
With Bosch Flexidome 8000i on 7.90.0098 firmware which is the latest on website, I cannot get the Tamper detection, i.e. Scene Change, ExcessiveBrightness, Insufficient Brightness, etc. events despite they are supported. https://support.networkoptix.com/hc/en-us/articles/17311762973079-Bosch-in-camera-analytics-integration
Plugin - Bosch 1.0.0
No change if I add the camera whether MOTION+ is activated or Intelligent Video Analytics ( IVA)
How can I get them appearing as you have documented in the guide here:
https://resources.vmsproxy.com/nx_6.0_help/bosch-analytics.html
-
Hi T H ,
The list of supported analytics we support, might differ from what the camera offers.
When a cameras is added to the VMS, a request is send from the VMS to the camera to list the available analytics events, and the camera provides a response and the content of this response populate the list of Event Type in the VMS.That being said, as far as I know, Bosch is capable of sending HTTP requests as a Action, so when the device is tampered, it can send a Generic Event to the VMS, and activate the desired action.
0 -
Hi Norman,
Here is the output of the Wireshark.
I can see that the camera is queried for Get Profiles and GetCapabilities but actually Tampering is a part of Analytics Service, presented here by onvif.org:
https://www.onvif.org/specs/srv/analytics/ONVIF-Analytics-Service-Spec.pdf
That query is never happening. By the way, the list of IVA events also is preset in VMS are not reflecting the camera response either. The camera lists only Object detection with “Detect Any Object” topic, where the list in VMS is like in my first question, including Traffic Incidents, line crossing and more…
Moreover, a query to the onvif event service also listed in response from Bosch camera is never queried.
GetEventProperties query response will return the Tampering response.
The HTTP Command can be sent out via Alarm Task Scription Language at Bosch Camera but how could it be received at NX Witness ?
If I am not missing anything, upon an Event received from the camera side , one can send out HTTP requests but not the other way around. If there is such a way then that could definetely be a workaround.
The Bosch interface is outdated and needs an update for sure. If the documentation does not match the actual functionality, then the combination does not make sense.
0 -
Hi T H ,
We don't use the Onvif Events (yet). For Bosch we use their API.
Can you share the Wireshark output as a pcapng file, made during the discovery process of the device, so we can check what events are reported.Regarding:
The HTTP Command can be sent out via Alarm Task Scription Language at Bosch Camera but how could it be received at NX Witness ?
It can be received as a Generic Event.
And:
If I am not missing anything, upon an Event received from the camera side , one can send out HTTP requests but not the other way around. If there is such a way then that could definetely be a workaround.
This can be done with the Do HTTPS request action.
I hope this helps.
0 -
Hi Norman,
The file is ~ 50 MB. How shall I share? I cannot put in here.
Generic Event could be of a choice for an interim resolution.
Do HTTPS request is NX Witness triggering it to the Camera I guess by accessing the camera Web server but I was more into Camera side sending a POST to NX Witness web server for that case. I guess my way would be Generic Event with a text in the name included.
0 -
Hi T H,
You can share the file with email address nx.verify@gmail.com.
Do HTTP request is to send an request from the VMS to another source.
Generic Events are used to receive the event from the Bosch cameras.0
Post is closed for comments.
Comments
5 comments