search

motioneye-project / motioneyeos

A Video Surveillance OS For Single-board Computers
Other
7.85k stars 897 forks source link

Motion detection does not trigger video file creation #2792

Open faocrates opened 3 years ago

faocrates commented 3 years ago

I've recently setup motioneyeos on my Raspberry 3B+ (using the R3B+ OS image) and use it along with a USB camera equipped with a Sony IMX291 image sensor. Configuration changes I made were to add files to a Samba network folder, enable Movies (motion triggered) and Motion Detection (threshold left at 2.6%). All other configurations were left to the initial defaults. Connectivity is through WIFI.

The camera looks over a parking lot, sometimes there will be three cars parked (distance to the cars ~8-10 meters). I'll have a stored video in the remote SMB folder showing three cars parked (all idle) then the next video shows two cars parked (again all idle) but the video in between that should show one of the cars moving out of the parking lot is never stored! Somehow it seems like any major movement does not result in a stored video file, while some minute changes are stored (with main subjects captured remaining idle). Really puzzled by this issue, any help or advice would be greatly appreciated.

Preliminary Docs

I confirm that I have read the CONTRIBUTING guide before opening this issue.

I confirm that I have read the FAQ before opening this issue.

motionEyeOS Version

I am running motionEyeOS version: 0.42.1 20200606

Board Model

I am using the following board/model: Raspberry PI 3B+

Camera

I am using the following type of camera: V4L2

My camera model is: UVC-compliant USB camera of the Arducam USB camera family, based on the 1/2.8” Sony IMX291 image sensor.

Network Connection

My motionEyeOS unit is connected to the network via: WiFi

Peripherals

I am using the following peripherals that I consider relevant to this issue: None

Log Files

I consider the following log files relevant to this issue: motioneye.log motion.log messages.log dmesg.log boot.log

starbasessd commented 3 years ago

I usually start with Frame Change Threshold set to 0.1% and move it up until I don't get very many 'false positives'. I also turn on 'Show Frame Changes' until I get to the settings I want. To minimize false positives, especially in twilight and dawn, I turn on Despeckle and Auto Noise Detection. I do not turn on Auto Threshold Tuning. I set Motion Gap to 2 seconds Capture Before 10 frames Capture After 10 frames Minimum Motion Frames 2 have always been a good place to start, too.