topic Motion detection test and actual triggering performance don't match in Features

Motion detection test and actual triggering performance don't match

Ricknau — Mon, 03 Oct 2016 03:40:20 GMT

I have my garage camera set so it triggers very nicely when I run the motion detection test. Yellow LED flashes consistantly for specific motion paterns. Then, when I change to armed camera mode I have to get like half as close to the camera to trigger a recording. What's with that? Very frustrating.

Went back an forth between the two modes and the behavior difference is consistant. BTW, detection sensitivity is set at 100%.

How can this be? Anybody else seen this behaviour?

Re: Motion detection test and actual triggering performance don't match

Ricknau — Mon, 25 Jul 2016 13:57:14 GMT

Uhh... May be operator error. Have test set to 100% sensitivity but now see that camera is at 50%. That is, adjusting the sensitivity in test mode doesn't set the camera's sensitivity. Must exit the test and go to "armed" screen to actually set the camera sensitivity.

Will test this afternoon.

Re: Motion detection test and actual triggering performance don't match

JamesC — Tue, 26 Jul 2016 20:46:13 GMT

Ricknau,

Correct, camera sensitivity can be adjusted per the rules within the mode. Motion detection test sensitivity does not dictate the sensitivity for an "Armed" camera, only for the test.

Let us know your results!

JamesC

Re: Motion detection test and actual triggering performance don't match

Ricknau — Wed, 27 Jul 2016 01:46:26 GMT

Yeah, the behavior now matches. "facepalm"