0.9.3 Release

Bug Fixes:

• Fix cleanup of legacy recordings
• Prevent config validation failure when rtmp disabled globally
• Revert switch to mpegts for default segment format (0.9.2 issues)
• Revert default to including audio (0.9.2 issues)

Changes:

• Improve performance of cache loop

Full Changelog: v0.9.2...v0.9.3

Images:

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

0.9.2 Release

NOTICE: There are some known issues with this release.

• #2055
• #1755 (comment)

Bug Fixes:

• Fix bug causing some recording segments to expire early within an event

Changes:

• Switch to mpegts container type for recording cache to reduce lost footage if ffmpeg exits
• Clearer log messages on invalid config
• Assume default roles when a single input is specified
• Restrict max size of live view to specified resolution
• Audio is included by default in recordings

Images:

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

0.9.1 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.x

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

0.9.1 Bugfixes

• Fix logo load for birdseye view

Images:

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

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.9.0 Release Candidate 6

Getting very close to an official release.

Docs will be moving to a dedicated domain with this release. See here: https://docs.frigate.video/

Changes since RC5:

• Revert support for Rockchip hardware acceleration with ffmpeg (aarch64 only)
• Ensure clean png snapshots are cleaned up in all cases
• Docs updates
• Clarify log message for bad segments

Images:

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

0.9.0 Release Candidate 5

Getting very close to an official release.

Docs will be moving to a dedicated domain with this release. See here: https://docs.frigate.video/

Changes since RC4:

• 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)
• Support for Rockchip hardware acceleration with ffmpeg (aarch64 only)
• Change theme color from red for iOS and Android

Images:

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

0.9.0 Release Candidate 4

NOTICE
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.

Release discussion

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)

Changes since RC3:

Breaking Changes:

• Replace clip_ready event type with a has_clip attribute in the data on the end event

Other Changes:

• Fix global live config option
• Add version to the logs on startup
• Fix bug with expiration of recordings that caused some segments to expire within events in certain scenarios
• Improve reliability of restart handling

Images:

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

0.9.0 Release Candidate 3

NOTICE
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.

Release discussion

Changes since RC2:

Breaking Changes:

• Invalid or extra keys in config files will now cause Frigate to error out and exit
• The enabled setting under record -> events has been removed (docs)
• scale is no longer an option for timestamp_style. The scale is calculated dynamically based on the image size now.

Other Changes:

• Reverse sort events within the hour for recordings timeline
• Fix edge case when expiring recordings when there are none yet
• Revamp recordings expiration for efficiency
• RTMP/Timestamp/Live all available as global config settings
• Fix timestamp_style config colors
• Fix timestamp_style font scale issue
• Ensure pre/post capture time is not expired from recordings

Images:

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

0.9.0 Release Candidate 2

NOTICE
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.

Release discussion

Changes since RC1:

• Reverse sort the hours within a day for recordings so most recent events are at the top
• Fix live view bug when one camera is named the same as the ending of another
• Fix bug with cache cleanup of old camera name files
• Revert to the frogfish Mobiledet model (fixes #1614)
• Enable all detect and snapshot settings to be defined globally or at the camera level
• Adjust nginx VOD parameters to improve handling of varying iframe intervals

Images:

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

0.9.0 Release Candidate 1

NOTICE
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.

Release discussion

Breaking Changes:

• Because clips are now assembled from recordings, any custom output args will need to be moved from clips to record. The clips role has been removed.
• CPU detector is now the default to lower the barrier for those testing frigate prior to ordering a Coral. You must specify a detector with an edgetpu if you have one.
• height/width/fps are now nested under detect in the config and all are required to avoid confusion about which role they apply to docs
• Clips config is no longer deprecated, but is removed. The previous clips section needs to be moved to record -> events instead. docs

Changes:

• New Recordings UI to view 24/7 recordings with an event timeline selector
• New live view JSMpeg camera streams, ~80% reduction in bandwidth required vs mjpeg
• Birdseye camera view (description)
• Remove tmpfs_cache_size setting as it is no longer needed for hassos
• Delete events from the UI
• Code cleanup and refactors for best practices
• Convert config to pydantic to support future config editor
• Support for self signed certs and key auth with MQTT
• clip_ready event type published to events topic when clip has been saved
• 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)
• Clips and recordings are merged and clips are now dynamically created based on recordings
• Events view now shows expands in place for viewing event footage

Images:

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