Modect stopped working on one of three cameras.

[4edo]

Hello,

I just installed ZoneMinder 1.34.23 on a Dell Latitude E7250 with 8GB of RAM. Install went okay. I used the ONVIF probing process to install the first camera and then cloned it twice for the other two. (The make and model of all three cameras is identical.) I practiced triggering the filters to get the options right. The filter itself simply fires when Alarm Frames is greater than 20. The filter triggered for all three cameras. I shut the system down overnight and now this morning one of the cameras won't trigger on motion. I can see the video fine but I cannot get the motion detection to work on that one camera. I deleted and re-added it. Still not working. I can force an alarm and the filter works. I set the logging level to DEBUG and tried to trigger an alarm by walking in front of the camera. No errors or warnings showed up in the ZM log. Nothing helpful in syslog either. Question I have is what might have happened to cause the Modect to apparently just stop working when I can see the video just fine? How do I debug this?

Thank you very much for any assistance.

thanks,
4edo

[Andyrh]

My first thought is the threshold is too low. It happened to me when I first started with ZM. I figured out a little trick:

Draw a new zone a little smaller than you appear in the video. The zone will tell you the number of pixels or the percent of the whole frame. Compare that to the size you have setup to detect. If you are using percent try changing to pixels, that will not require the math to adjust the percent.

[4edo]

Ok. Thanks. Yes I'll try that. Interesting point because the camera that is having the problem has the most cluttered and complicated scene to deal with.