Major Changes for 0.10.0

Stationary objects

Frigate will now continue to track objects after they are stationary. This enables use cases such as presence detection. After an object has been stationary for 10 frames, object detection for the object will be throttled to 1 frame every 10 seconds (this is adjustable with the new stationary_interval setting) until there is new movement. An object is determined to be stationary if the bounding box in the current frame overlaps almost entirely with the previous frame. I have been testing this in my home office, and it works quite well.

I expect this to disrupt the way a few people are using Frigate. For example, a car that enters the driveway, parks, and then leaves 5 hours later will be one continuous event. This means that the recording segments will be retained for all 5 hours the car was tracked. In addition, the zones will stay with the tracked object over this lifetime, so when the car leaves, it will still have zones associated from when it first arrived.

Depending on the specifics of your room, you may need to tune your resolution and motion settings to get the results you want. In my office, I reduced the resolution to 640x360 and increased the contour_area setting for motion detection up to 125 to reduce the sensitivity. I recommend watching the debug view and adjusting as needed.

fixes #841

In progress events and cache handling

Events are now stored in the database while in progress, so you can expect to see In progress for some events under end time in the Events view.

Recording segments written to the cache are now only moved to the recordings folder if they overlap with an event (in-progress events too). For those with retain_days set to 0, this eliminates disk I/O when there are no events. Frigate will no longer store a minimum of 5 minutes of recording segments for each camera, so no you can enable recording without worrying about SD/SSD wear.

Lastly, more proactive cache maintenance was implemented to prevent the cache disk from filling up. If too many cache segments exist, they will be deleted and a warning message (Proactively cleaning cache. Your recordings disk may be too slow.) will be printed to the logs. You can also see the time it takes to copy to the recordings disk by setting frigate.record: debug in the logger config. Additional error handling was also implemented to prevent the cache maintenance thread from stopping on errors.

fixes #1885

Motion detection improvements

0.9.0 introduced dynamic motion sensitivity which didn't work out well. For many users, this made motion detection too sensitive which increased CPU usage due to more motion causing more object detection. It also increased false positive detections due to the increased frequency for detections on areas without substantial motion.

In this release, motion detection has been reset back to better defaults for frame_height and contour_area. For most users, the sensitivity can be tuned by adjusting contour_area. For very high resolutions with very small objects, the frame_height may need to be increased.

In addition, this release brings about dynamic contrast adjustment for motion detection. Based on my testing, this substantially improves night time detection with IR lights and other low contrast situations.

Other changes

• Improved logic for merging motion, bounding boxes, and regions

Fixes

• fixes #2129

Full Changelog: https://github.com/blakeblackshear/frigate/compare/v0.9.4...v0.10.0-beta1

Images:

• x86: blakeblackshear/frigate:0.10.0-beta1-amd64
• x86 w/ nvidia (for ffmpeg only): blakeblackshear/frigate:0.10.0-beta1-amd64nvidia
• Raspberry Pi 3/4 (32bit): blakeblackshear/frigate:0.10.0-beta1-armv7
• Raspberry Pi 4 (64bit): blakeblackshear/frigate:0.10.0-beta1-aarch64