Dahua video analytics support
AnsweredI like to see support for Dahua IVS as they call it. Dahua cameras don’t have any way to send http requests, so I’m not able to set it up manually. A direct I integration with NX would be great!
-
@Norman/Tony:
I have 4 OEM Dahua cameras with IVS support on latest Dahua firmware and would like to use the In-Camera Analytics once 4.0 is released.
The cameras are OEM'd from Empire Tech https://www.amazon.com/gp/product/B07B7K1P28/ref=ppx_yo_dt_b_asin_title_o01_s00?ie=UTF8&psc=1
and run Dahua software but Nx Server discovers them as follows...
Model - IP Camera
Firmware - 2.800.0000005.0.R, Build Date 2019-03-25
Vendor - GeneralNote the camera model does not report and the vendor is not reported as Dahua but it is running the latest Dahua software and has IVS for sure. Can I edit some configuration somewhere to force camera as Danua with the 4.0 Beta? Or does your software figure it out and I should not worry?
/dan
-
Thanks Norman,
I just realized that bascially, this is the same question you are tracking down for Ryan in another thread https://support.networkoptix.com/hc/en-us/community/posts/360020948493-Camera-Analytics-for-HIKVision-OEM?page=1#community_comment_360008824893.
Somehow I missed it since that thread was about HIKVision.
The ability to set my Vendor as Dahua for my OEM camera would likely solve the issue.
/dan
-
Norman,
I've updated to the V4.0 Beta (so I would have the Dahua In-Camera Analytics feature).
I updated my database as follows so that my OEM Dahua camera entries would show up with vendor=Dahua and I restarted the server. My cameras have the latest firmware that support IVS Analytics capabilities.
dan@nuclear:/opt/networkoptix/mediaserver/var$ sudo sqlite3 ecs.sqlite
SQLite version 3.22.0 2018-01-22 18:45:57
Enter ".help" for usage hints.
sqlite> update vms_camera set vendor="Dahua" where physical_id="A0-BD-1D-10-93-B8";
sqlite> update vms_camera set vendor="Dahua" where physical_id="A0-BD-1D-10-94-0A";
sqlite> .quitCamera inventory is updated in the GUI after server restart.
I see that the camera has the "Dahua analytics plugin" enabled.
I am now able to create an Analytics camera rule.
I created a trip-wire on the Camera.
The trip-wire works on the Camera...
But no Analytics event shows up in Nx Witness.
Am I missing some other required configuration?
I am willing to work with support or send logs.
/dan
-
Yes Jasper,
The following Dahua analytics should work in v4.0.
Dahua in-camera analytics - tested with firmware 2.622.0000000.31.R, Build Date 2018-08-13
- Motion detection
- Face detection
- Alarm detection
- Storage absence detection
- Storage failure detection
- Storage low space detection
- Video blind detection
- Scene change detection (Video abnormal detection)
- Audio anomaly detection (Audio input abnormal detection)
- Login error detection
Dahua in-camera analytics - Not tested, but potentially supported:
- Video loss detection
- Defocus detection
- Tripwire detection (Cross line detection)
- Intrusion detection (Cross-region detection)
- Abandoned object detection (Left object detection)
- Missing object detection (Taken away detection)
- Audio intensity change detection (Audio mutation detection)
- High-temperature detection
- Alarm output detection
-
In the meantime I have a Dahua camera with analytics functions to test with NX.
It all worked well till I updated the camera. Before I had 10+ event to chose from in the camera rules. Now when I try to ad a new rule I get an error saying the camera doesn’t support the analytics rules. If I look at the existing rules they are all coloured red but they still work tough. I still get notifications from analytics events.
It is a Dahua firmware, not a OEM version.
Would there be a solution/workarround for this problem -
Hi Jasper,
Please share the script here so anyone can download it. If you can't provide a permanent download link, I can host it instead an provide a download link for anyone.
That being said, in v4.0 the Dahua analytics should be supported and if you encounter any issues, please let us know.
-
Gentlemen,
Here is the script I use for the Dahua IVS: https://drive.google.com/file/d/1CoANgSWmBhpdxxCgAU1yLPP-w35_WhLe/view?usp=sharing
The only thing you need to change is ALARM_DELAY, the camera configuration (IP, username and password) and the URL for the generic event for the NX server.
It is based on this Github project: https://github.com/AblazeWoland/dahua-ivs-watcherI only changed the script so it works with NWX I am no developer at all.
Like I said before the IVS worked with NX 4.0 but after updating the camera to the following firmware 2.800.0000000.8.R, Build Date 2019-09-02 the analytics events are not even recognized in the rules configuration. If this could be fixed there is no need for the script anymore.
-
Yes. it works
In Dahua cameras:- Set Smart Plan to IVS
- Create a IVS rule (Tripwire or Intrusion)
- Check that you got a updated/supported firmware
Some times you need to factory default the camera after a update to get IVS to work with Nx.
In Nx on PC:
1. Create a InCamera Analytics rule for the given camera. Set it to the same tye as the rule in the camera (Tripwire or Intrusion)
2. Set the action for that rule to push / mobile notification add select the userIn Nx App on phone:
- Make sure you have allowed push notifications for the app.
- Make sure you have enabled push notifications in Nx App under settings
-
Hi Stefan Dekkers,
One thing to check; the cameras should be branded as Dahua.
OEM models of Dahua won't work without some tricks.Can you share a screenshot of the Vendor and Modelname, so I might be able to create a fix for you.
-
They are branded as Dahua.
There are several different models used at this costumer.
This is the one i tested.
In total there are 60 camera's online currently (we will add about 40 more in the near future).
Current camera's are 60/70% Dahua, the others are old Geovision Camera's but we aren't putting any energy in them ;-)
So if there are other models that perhaps work better, let me know.
-
Hi Stefan Dekkers,
I tried to make a quick fix. Could you try it? You can download the file HERE.
Please follow the steps as described below:
-
Remove the camera from the system
-
Stop the mediaserver application and paste the resource_data.json file from the download link at the following location:
For Windows: C:\Program Files\Network Optix\Nx Witness\MediaServer
For Linux: /opt/networkoptix/mediaserver/bin/ -
Now start the mediaserver application again.
-
(Add the camera again)
To stop and start the media server, please do it as follows:
For Windows: Open the task manager, select tab ‘Services’ find the mediaserver application, right-click and select; Stop or Start
For Linux: Open the terminal (Ctrl+Alt+T) and enter the following command; sudo service networkoptix-mediaserver stop or sudo service networkoptix-mediaserver start.
After this, the request should be fulfilled.
Please confirm if this works, so we can create a permanent fix. -
-
Can you tell me what tricks need to be done if you changed the firmware from Dahua to something different?
I had Dahua Firmware, but there was a newer firmware from empire tech (that helped with SMD) I updated and well of course it doesn't see the Plugin.
-
Hi David King,
Share a screenshot as shown HERE, and we will see what we can do.
-
I tried to make a quick fix. Could you try it? You can download the file HERE.
Please follow the steps as described below:
-
Remove the camera from the system
-
Stop the mediaserver application and paste the resource_data.json file from the download link at the following location:
For Windows: C:\Program Files\Network Optix\Nx Witness\MediaServer
For Linux: /opt/networkoptix/mediaserver/bin/ -
Now start the mediaserver application again.
-
Add the camera again
To stop and start the media server, please do it as follows:
For Windows: Open the task manager, select tab ‘Services’ find the mediaserver application, right-click and select; Stop or Start
For Linux: Open the terminal (Ctrl+Alt+T) and enter the following command; sudo service networkoptix-mediaserver stop or sudo service networkoptix-mediaserver start.
After this, the request should be fulfilled.
Please confirm if this works, so we can create a permanent fix. -
-
Hi David King,
Is it possible to forward the device for further investigation?
If so, I'll open a support ticket on your behalf, so you can share the login credentials privately.
-
Hi David King,
I just created the ticket on your behalf, so you can share the login credentials of the device privately.
Please sign in to leave a comment.
Comments
34 comments