0.9.0 Release

This version is not compatible with the current version of the Home Assistant integration for clips in notifications or the media browser. You will need to use the v2.0.0 pre-release of the integration.

Major Changes for 0.9.0

There are quite a few significant changes to the config for this release. Updated config reference is available here.

BREAKING: Clips have been merged into Recordings

Frigate now records footage from the camera one time. You define retention settings to determine what you want to keep. You can set it to retain all footage for the number of days you want and/or have a different retention setting for recorded footage that contains detected objects. When you view footage for an event, you are viewing the recorded footage for the time where the event occurred. The "Download Clip" button on the event view will dynamically create an mp4 from the recordings for download.

Separating events and recording this way has significant benefits. Overlapping events no longer mean that the same video footage is stored multiple times on disk. Also, the issue with the cache expiring for long running events is eliminated.

If I used clips without 24/7 recording before, does this mean I have to now record 24/7?

No. If you only want to store footage of events, the following config should be used:

record:
  enabled: true
  retain_days: 0
  events:
    retain:
      default: 10

BREAKING: width/height/fps moved under detect

Due to regular confusion about which input the height/width/fps applied to, these settings have been moved under the detect section of the config. Here is an example of a simple config:

cameras:
  back:
    ffmpeg:
      inputs:
        - path: rtsp://viewer:{FRIGATE_RTSP_PASSWORD}@10.0.10.10:554/cam/realmonitor?channel=1&subtype=2
          roles:
            - detect
    detect:
      width: 1280
      height: 720
      fps: 5

Recordings Viewer

There is now a way to view recorded footage directly in the WebUI. Browse your recordings and events with a collapsible timeline view.

Fullscreen	Desktop (Collapsed)

Mobile	Mobile Fullscreen

Birdseye

A live, dynamic grid view of all cameras with activity. It has 3 modes:

• objects: includes any cameras with detected objects
• motion: includes any cameras with detected motion
• continuous: all cameras all the time

It is designed to minimize the bandwidth used, so when there are no active cameras, you just get a black screen with the frigate logo.

Live View

When selecting a camera, the live view now uses JSMpeg, which results in about an 80% reduction in bandwidth required vs mjpeg. This view does not support adding overlay information. Tapping on the feed supports full screen viewing on some devices. The mjpeg debug view with overlays is still available at the top right.

Other changes

• Remove tmpfs_cache_size setting as it is no longer needed for hassos
• Delete events from the UI
• Code cleanup and refactors
• Convert config to pydantic to support future config editor
• Support for self signed certs and key auth with MQTT
• has_clip and has_snapshot added to events mqtt topic payload
• snapshot_time added to events mqtt topic to determine if an updated snapshot is available
• Clean PNG snapshots alongside jpg for future training purposes
• Ability to customize timestamp drawn on snapshots and the debug video feed
• Dynamic motion detection defaults based on resolution (#1176)
• Adds option to specify jpeg quality on various http endpoints and in config (#821)
• Trigger a restart from WebUI or via MQTT
• Labelmap can now be customized via config (#507)
• Add version to the logs on startup
• Improve reliability of restart handling
• Allow partial days in retention settings (0.5 will now save half of a day)
• Add region/box/area to the database and api endpoints for events
• Run nginx as root (this resolves permissions issues for many users)
• Change theme color from red for iOS and Android

Images:

0.9.0 was published with a bug. Please use 0.9.1.

0.8.4 Release

Fixes:

• Prevent mjpeg streams from blocking the web server
• WebUI: Prevent reflow for scrollbars
• WebUI: Increase API limit for smoother scrolling on events

Images:

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

0.8.3 Release

Fixes:

• Update baseUrl handling for addon ingress and websockets

Images:

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

0.8.2 Release

Features:

• Lots of frontend improvements
• Switches in WebUI for detection/clips/snapshots
• Proactive cache cleanup when >90% full
• Attempt to cleanup overlapping events from the database
• Add disk usage stats
• Global object masks
• Try to avoid detection of stationary objects
• required_zones setting for snapshots/clips/mqtt

Changes:

• max_disappeared is now 5x FPS by default
• Implement mqtt via websockets for frontend use
• Reduce jpg image sizes to reduce bandwidth
• Unit tests and automated tests for webUI

Fixes:

• Resubscribe to MQTT topics on reconnect

Images:

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

0.8.1 Release

Core:

• Improved FFmpeg log capturing when a failure occurs

Web UI:

• Fix live view for Firefox
• Add activity spinner to WebUI
• Improved events page
• Improve performance of WebUI

Images:

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

0.8.0 Release

This release is a monster. If upgrading from 0.7.x, I recommend starting with a fresh config file. There are several breaking changes to the config. See updated docs linked in the readme.

Breaking Changes:

• 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 /api/stats
• If you are specifying your thresholds for person detection, 0.85 will now be WAY too high. Update them to 0.7 or remove from your config and use the default. The new model doesn’t score detections as high, but has a much lower false positive rate.
• The previous mask value is now under the motion config section
• Masks are now configured like zones and image masks are no longer supported
• Fallback to CPU if the EdgeTPU is not detected has been disabled. It will now keep trying to detect your EdgeTPU.

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
• Ability to configure model dimensions
• Handle portrait cameras better
• Update model to mobiledet and update default threshold to .7
• Make motion detection configurable
• Make object tracking configurable
• Add a version endpoint
• Mask can now be a list of masks
• Mjpeg and latest.jpg now support dynamic drawing of bounding boxes, regions, zones, motion, mask, and timestamp via query string parameters
• Update crop of thumbnail based on object box rather than detection region
• post_capture setting for clips
• Allow num_threads for CPU detectors
• Add qsv hwaccel for ffmpeg (should help 10th gen intel processors)
• Updates for events on zone changes
• A basic web UI
• Environment variables can be set via the config file
• Optionally save snapshot jpg files alongside clips
• New mqtt options for configuring the images sent via MQTT
• Disable/enable detection, clips, snapshots via MQTT (retained in MQTT to persist setting on restart)
• Stats also now published via MQTT
• Object detection masks by object type
• Version and uptime added to stats

Images:

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

0.8.0 Release Candidate 6

Changes:

• UI: Make image size responsive to reduce load time on smaller screens
• UI: fix some relative paths when used with ingress

Images:

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

0.8.0 Release Candidate 5

Changes:

• Use the SqliteQueueDatabase to avoid database is locked errors for systems with many cameras

Images:

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

0.8.0 Release Candidate 4

Changes:

• Handle missing cache files rather than waiting indefinitely
• Fix the /events/<id>/thumbnail.jpg endpoint when event in progress
• Add a /events/<id>/snapshot.jpg endpoint that works during and after events
• Rate limit event update notifications published to frigate/events to once per 5s
• Beautiful new docs (thanks @paularmstrong)
• If the detection process stops, exit the entire container rather than try and restart within the container

Images:

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

0.8.0 Release Candidate 3

Changes:

• Quite possibly fixing ingress for addon users (or at least until the next bug is found)
• Fix initial state of mqtt switches
• Gracefully handle edge case when frame is no longer in cache

Images:

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