Hello,
My system is set for human line-crossing detection, using camera detection (not NVR), with linkage to phone notification and recording.
The motion sensing is excellent with almost no false alarms for phone notification, but there are numerous false recordings without notification. This doesn't make sense as any detection should give both a notification and a recording, as per the linkage. During the false recordings, genuine human detections are blocked from making a notification, compromising security.
All other motion detection is off. I have the same problem with both cameras, with any smart detection (such as intrusion detection).
It seems that the 'event' recording schedule responds to all events, human or otherwise, rather than just alarm events. It is ignoring the 'human' tickbox. I think this is a bug.
I have made a workaround using the alarm out (which correctly responds to human detection) to trigger the alarm in, with the recording schedule set to alarm. This works perfectly, but it shouldn't be necessary to do this.
Has anyone experienced the same problem, and/or can suggest a more elegant solution?
Thanks,
Paul.
My system is set for human line-crossing detection, using camera detection (not NVR), with linkage to phone notification and recording.
The motion sensing is excellent with almost no false alarms for phone notification, but there are numerous false recordings without notification. This doesn't make sense as any detection should give both a notification and a recording, as per the linkage. During the false recordings, genuine human detections are blocked from making a notification, compromising security.
All other motion detection is off. I have the same problem with both cameras, with any smart detection (such as intrusion detection).
It seems that the 'event' recording schedule responds to all events, human or otherwise, rather than just alarm events. It is ignoring the 'human' tickbox. I think this is a bug.
I have made a workaround using the alarm out (which correctly responds to human detection) to trigger the alarm in, with the recording schedule set to alarm. This works perfectly, but it shouldn't be necessary to do this.
Has anyone experienced the same problem, and/or can suggest a more elegant solution?
Thanks,
Paul.