Software Version: 2.460.1.0.R, Build Date: 2018-06-26
WEB Version 3.2.1.474688
ONVIF Version 16.12(V2.4.0.485616)
S/N: AMC039626C79619A17
Camera does not save motion detection settings or resets them entirely ... or takes several "cancel -> Detection Area" key presses to function properly.
No cloud account in the picture to speak of.
If you're looking to offload motion detection from a software based solution to the camera don't waste your time.
From reading the forums it's clear amcrest has made no indication that they are interested in fixing this issue.
The latest version of this software is from '18 and here we are already nearing '21.
To reproduce (right after a factory reset):
Go To: Setup -> Event -> Video Detection -> Detection area
Remove all and save.
Save again, once window closes.
Detection Area (again) -> Sensativity to 100% -> Threshold to 1 -> Mask "in" half the screen -> Save
Before clicking save, verify it's picking up motion in the squares .... it is.
Save again, once window closes.
Save again.
Detection Area (again) -> verify motion is working .... it isn't.
Cancel -> Detection Area (again) -> verify motion is working .... it isn't.
Cancel -> Detection Area (again) -> verify motion is working .... it IS!
Cancel -> Detection Area (again) -> verify motion is working .... it isn't.
Cancel -> Detection Area (again) -> verify motion is working .... it isn't.
Cancel -> Detection Area (again) -> verify motion is working .... it IS!.
So, that's how I am reproducing this problem. Next up is the event manager. Without motion being detected properly, the event manager too will suffer from not being able to report events properly.
% curl -s --no-buffer \
--digest --user user:pass \
"http://192.168.70.5/cgi-bin/eventManage ... ideoMotion]" |\
sed -nlE '/^Code/s/.*n=([^;]+).*/\1/p'
Start
Stop
Start
Stop
Start
Stop
...
...
You guessed it. That's a working example. Just by hitting cancel, and clicking on Detection Area again ... causing the above output to simply stop. It's not producing any events any longer. If you hit the sequence "cancel -> Detection Area" enough times to get it to actually work ... the above starts registering events again.
This is a real problem ... please release something that fixes this issue because hitting the button sequence "cancel -> Detection Area" over and over again shouldn't cause motion detection to work ~30% of the time.