Motion detection not working
Answered
I've just installed Nx; motion detection is not working at all.
Two of the cameras are linked to Synology's Surveillance Station - this correctly picks up motion detection (using the camera's own motion detection rather than anything server side) and sends me a push notification
On Nx, I've left the camera settings to auto (so the secondary stream is 640x480).
Nx server is 4.1.0.30731 R5
The cameras are newly installed - I believe white label Dahua 6mp cameras
Anything else I'm missing ?
-
i'd probably start by checking a few things.
1) check firmware version of the camera against the compatibility directory. http://ipvd.networkoptix.com/#!/
2) toggle the resolution of your stream between high and low with the information for the stream turned on in desktop. see if the res actually switches between high and low. I had a similar problem with some Dahua cameras in the past and i had to change firmware versions to get the high and low res streams to correctly come into witness.
Good luck
-
Hi R DS,
Doug Makino already made some good suggestions.
I would also look in the Camera Settings, tab General if there is actually a secondary stream available.
Also, in the tab motion detection there relevant field should be selected at level 1 at least or more.Lastly, when the scene lacks in contrast (very dark scene with an individual with dark clothing), motion detection might fail, but this situation is pretty rare.
-
Hi R DS
That is nice to hear. And you are right, currently you can change the URLs when they were added automatically.
If they are white label Dahua cameras we might resolve it, but it requires unique vendor and model names and from my experience Dahua often uses the vendor name General and model name IP_Camera for their OEM models and in that case there is nothing we can do.
-
Hi Norman Graafsma, thanks for that
I presume all motion detection is done server side, as I can't see an option to just use camera based triggering ?
If so, is it possible to enable it retrospectively ? Ie have it off, but if there's an event I want to look for, turn it on and then have the server analyse for it ?
I'm running Nx on a NAS, so was wondering if doing it this way might lower processing requirements. To be honest the CPU usage is pretty good with motion detection on all my (albeit only 6) cameras currently, but just trying to be the most efficient with resources...
-
One other comment about the camera and firmware. I had the exact same problem that you had where both streams were showing the exact same address. I had to try a few different firmware versions until i found one that worked correctly. On a newer firmware the cameras were showing up as a "general ip camera" type label with both streams being the same. Once i downgraded to an older firmware it showed up with the correct ID and two separate streams.
Do you have the exact model number of your cameras?
-
Doug Makino they are DH-IPC-HDW4631EMP
-
Thanks Doug Makino
My cameras came with V2.800.12SD000.0.R, Build Date: 2019-06-18
The Dahua firmware website is horrible; I can't find that exact build date of 2019-04-24, or anything for the 2.800.12SD around those dates
Plus what are Rhea, Volt, Mao_Molec, Leo etc in the filenames ? The list of supported devices under each file is also rather sparse, and I couldn't find my model after going through all 8 pages...
Having said all that, the only thing I appear to miss by adding them manually as RTSP streams is Nx auto configuring the stream settings - is there any other downside ?
-
R DS
the Dahua firmware site is certainly not the best. Someone from Network Optix is probably more well suited to answer your question about RTSP streams. if there is a significant disadvantage to how you're currently bringing streams in then it might be worth spending time and effort tracking down / testing different firmware.
-
Hi R DS
If you add them manually as RTSP streams, you determine the streams and the camera settings are used.
Downside of add RTSP stream is that you can't benefit from additional features like PTZ, audio, camera settings, and in-camera analytics.If you can arrange that the name of the Vendor and Model becomes unique, we can modify our software to provide the same features as original Dahua cameras.
If you add them manually of automatically, Nx Witness optimizes the camera settings.
In general this should work just fine for Dahua OEMs. There are tons of them in the field and many are connected to Nx Witness VMS.Most easy way to check is to connect the camera to the Onvif Device Manager. If it works there, it should work in Nx Witness as well.
-
Is there a way for me to first explicitly specify the model number for Nx to then provide the feature set (rather than model auto-detection only) ?
None of the firmwares I've tried have loaded successfully, so it looks like I can't change the Vendor/Model details that are presented...
The audio out feature would be nice to have
-
There is nothing we can do from our side. The camera vendor is the only one who can provide you with the correct firmware.
Regarding audio, we do support audio, but also it should be available according to the Onvif API.
You can verify this with the Onvif Device Testing Tool which is officially not available, but can be found online by anyone with a search engine on his computer. -
Sorry, didn't read the whole thread: but I found that Camera's with 3 streams, Nx Witness chooses Stream 0 (HD) and Stream 2 (3rd stream on camera, usually under second stream dropdown on Dahua cameras).
Regardless of what stream 3 is set for resolution, Nx won't do motion on it properly, so you have go into the advanced settings and use the option to "force motion on stream" and set it to Nx stream 2.
fixed my motion detection issues on cameras with 3 streams.
-
Hi Marc R,
Are these Dahua cameras or Dahua OEM cameras (=same camera, different name)?
-
Norman Graafsma re firmware - is there any way to manually tell Nx to use a specific model's firmware if it can't recognise the camera (eg for these OEM models that it can't correctly identify) ?
-
Hi R DS,
There is a way to allow OEMs to mimic the original manufacturer, but in order to resolve this, the name of the Vendor and Model name should be unique. For Dahua OEMs we frequently see Vendor name 'General' and model name 'IP_Camera' and if we add these, it would break compatibility with other brands which use the same names.
Please sign in to leave a comment.
Comments
19 comments