0.8.0 Beta 1

This is a beta version because I still plan to include several additional changes in this release. This beta includes the enhancments necessary for the new HomeAssistant integration. There are many breaking changes. Please see the updated readme.

Changes:

• New HomeAssistant integration should replace all of your previous MQTT and REST sensors
• Up to 4 unique streams can be provided for each camera and assigned the following roles:
  • detect: stream used for object detection
  • clips: stream used for clips
  • record: stream used for 24/7 recording
  • rtmp: stream re-broadcasted by frigate as a RTMP feed for homeassistant
• 24/7 recording of video streams with retention management
• Clips are maintained in a local database and served up via an api
• Clip retention policy (per camera/object)
• Complete revamp of MQTT event messages for easy notification setup
• Improved calculation for best images
• MQTT topics now publish object type counts rather than just on/off
• Support for mesa va drivers for AMD hwaccel in ffmpeg
• New image with nvidia acceleration for ffmpeg decoding (this will not use your GPU for object detection)
• Config validation at startup

Breaking Changes:

• There are several breaking changes to the config. See updated example.
• The web_port is no longer configurable and is fixed at 5000
• For RTMP support, port 1935 needs to be made available
• All previous automations built around frigate/<camera>/events/start|end will need to be replaced
• The clips_dir is now at /media/frigate/clips and the cache_dir now at /tmp/cache. These are no longer configurable.
• /debug/stats is now /stats
• probably more...

Images:

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

0.7.3 Release

• Fixes a few bugs with cache handling and fps tracking introduced in 0.7.2

0.7.2 Release

• Improve frame management and update shm_size calculations in docs
• Run ffmpeg capture in its own process
• Fix Invalid number of channels in input image in some scenarios
• Add support for VAAPI on 10th gen Intel processors

0.7.1 Release

• Fixing bug with cache/clips directories after adding config options

0.7.0 Release

Changes:

• Raspberry Pi 3/4 Support
• Update ffmpeg to 4.3.1
• Support multiple coral devices
• Reduce CPU usage of ffmpeg and motion detection
• Replace underlying memory store with shared_memory and update to Python 3.8
• Smaller docker images due to switch to multistage builds
• shm-size parameter no longer necessary for the majority of scenarios
• Improve zone status calculations

Breaking Changes:

• Default output_args for cameras have changed. If you specified custom output parameters, you will need to update.
• Updated config for specifying coral device. See new detectors section in the example config.
• New json structure at /debug/stats to handle multiple detectors

Images:

• x86: blakeblackshear/frigate:0.7.0-amd64
• Raspberry Pi 3/4 (32bit): blakeblackshear/frigate:0.7.0-armv7
• Raspberry Pi 4 (64bit): blakeblackshear/frigate:0.7.0-aarch64

0.7.0 Release Candidate 3

• Prevent zone status from bouncing while object is in zone
• Add timestamps to snapshot images
• Allow bounding boxes to be drawn on snapshots with draw_bounding_boxes option

Images:

• x86: blakeblackshear/frigate:0.7.0-rc3
• Raspberry Pi 3/4 (32bit): blakeblackshear/frigate:0.7.0-rc3-armv7hf
• Raspberry Pi 4 (64bit): blakeblackshear/frigate:0.7.0-rc3-arm64

0.7.0 Release Candidate 2

• Prevent the camera process from hanging if the detection process is restarted

Images:

• x86: blakeblackshear/frigate:0.7.0-rc2
• Raspberry Pi 3/4 (32bit): blakeblackshear/frigate:0.7.0-rc2-armv7hf
• Raspberry Pi 4 (64bit): blakeblackshear/frigate:0.7.0-rc2-arm64

0.7.0 Release Candidate 1

Changes:

• Raspberry Pi 3/4 Support
• Update ffmpeg to 4.3.1
• Support multiple coral devices
• Reduce CPU usage of ffmpeg and motion detection
• Replace underlying memory store with shared_memory and update to Python 3.8
• Smaller docker images due to switch to multistage builds
• shm-size parameter no longer necessary for the majority of scenarios

Breaking Changes:

• MQTT snapshots no longer draw regions or bounding boxes
• Default output_args for cameras have changed. If you specified custom output parameters, you will need to update.
• Updated config for specifying coral device. See new detectors section in the example config.
• New json structure at /debug/stats to handle multiple detectors

Images:

• x86: blakeblackshear/frigate:0.7.0-rc1
• Raspberry Pi 3/4 (32bit): blakeblackshear/frigate:0.7.0-rc1-armv7hf
• Raspberry Pi 4 (64bit): blakeblackshear/frigate:0.7.0-rc1-arm64

0.6.1 Release

• Remove car and truck from default list
• Replace configs instead of merge to avoid confusion
• Fix zone filter issue #218

0.6.0 - Zones, Clips, and Less False Positives

Changes:

• Ability to save a video clip of each tracked object
• New event mqtt topics
• An updated snapshot is now sent via MQTT when a higher scoring object is detected
• Ability to define a zone to detect objects in specific parts of the image
• Mask can now be specified as base64 in the config file for easier k8s config
• Frigate now exits gracefully for SIGINT and SIGTERM
• New latest.jpg endpoint for fetching the current frame
• Best images can now be resized with a query string parameter to grab lower resolution images for notifications
• Updated method for computing a median score that reduces false positives
• New min_score and threshold definitions
• Allows configuring a specific EdgeTPU device for the container
• Modified labelmap to treat trucks as car to avoid confusion between the two
• Crop and resize the best.jpg endpoint
• Made best.jpg image timeout configurable
• Crop and resize images before sending to MQTT
• Limit what object types trigger recordings
• Limit cache size
• Polygon mask type
• Added affiliate links to the readme

Breaking Changes:

• In previous versions, ffmpeg used -vsync drop as an input parameter. It is incompatible with the new save_clips feature, so you will need to remove it if you added it directly to your config.

Image available at docker pull blakeblackshear/frigate:0.6.0.