Mocord, Nodect: Should mocord trigger monitors linked to it?
Posted: Fri Dec 07, 2018 4:24 pm
I'm trying to understand the operation of ZM and need some help.
I have a dual-stream IP camera, with the low-res and high-res streams configured. I have been doing MODECT on the low-res stream and have linked the high-res monitor to the low-res so that a high-res recording will be triggered when motion id detected on the low-res monitor. All that has been working fine.
I decided I wanted to have a 24/7 history of the video, from the low-res stream, so I set the low-res monitor to MOCORD. However, when I do this, motion IS detected, but the high-res monitor that is linked to it no longer gets triggered.
Is this expected behavior? I saw in the github issues that, a while back, there was a request to NOT have MOCORD monitors 10-minute new-event creation trigger an alert on linked monitors, but does this also stop motion-detection from triggering a separate event for linked monitors?
I have a dual-stream IP camera, with the low-res and high-res streams configured. I have been doing MODECT on the low-res stream and have linked the high-res monitor to the low-res so that a high-res recording will be triggered when motion id detected on the low-res monitor. All that has been working fine.
I decided I wanted to have a 24/7 history of the video, from the low-res stream, so I set the low-res monitor to MOCORD. However, when I do this, motion IS detected, but the high-res monitor that is linked to it no longer gets triggered.
Is this expected behavior? I saw in the github issues that, a while back, there was a request to NOT have MOCORD monitors 10-minute new-event creation trigger an alert on linked monitors, but does this also stop motion-detection from triggering a separate event for linked monitors?