Hide config   Changes don't take effect until you restart the motion detection.

The logic compares the latest snapshot with the previous snapshot. It calculates what percentage of the pixels are different. If the percentage is above a threshold, then that is considered "motion".

Enable downloading snapshots where motion is detected. This will trigger two quick downloads at start in order to get Chrome to ask your permission to download multiple files.

Throttle reporting. After motion is first detected and reported, if there is still motion, keep reporting motion after these intervals (in seconds). For example, for "10 10 20 60 300 3600", report motion, then report again 10 seconds later (if there's motion detected), then 10 seconds later again, then 20 seconds after that, then 60 seconds after that, then 5 minutes after that, then one hour after that. Then return to initial state of detecting motion right away.

Snapshot interval in milliseconds (0-1000):

Pixel threshold - how different must a pixel (r + g + b values) be to be considered different from previous snapshot? (1-765):

Image threshold - percent of image pixels that must be different from previous snapshot to be considered motion (1-80):

Image threshold ceiling - there seem to be glitches where the logic reports 90%+ of the pixels changing. This is to prevent false alarms (81-100):

Downscale full image for on screen display this factor (.1 to 1.0):

Downscale full image for pixel analysis by this factor. Bigger is slower. (.1 to 1.0):