0.12.0 Beta 5

Major Changes for 0.12.0

❗❗Notice❗❗
I want to recognize @NickM-27 for all the contributions he made on this release and all the support he helps provide in the issues. If you have been considering sponsoring this project with either a one time contribution or a recurring contribution, I would request that you do so at his sponsors page.

Link to updated docs: https://deploy-preview-4055--frigate-docs.netlify.app/

Changes Since Beta 4

• Fix early exit of Frigate container on restart and handle process exits more gracefully
• Improve handling of embedded go2rtc config
• Attempt to automatically populate WebRTC candidates for addon installs
• Enable variable substitution for streams within the go2rtc config for env vars beginning with FRIGATE_
• Use configured live view stream

BREAKING CHANGES

• If using the Frigate-HomeAssistant Integration it will need to be updated to 4.0.0 beta01 to avoid breaking changes with Frigate 0.12
• Changes have been made to the database, a backup of the database will need to be made before updating if you want to roll-back.
• Some deployment approaches are overwriting the PATH environment value to an old value. If you see errors like ./run: line 7: exec: nginx: not found, then you need to stop overriding your PATH. This happens with both Proxmox LXC and Portainer (#3223 the database will need to be deleted to roll-back successfully.
• The shm storage requirements have changed for 0.12, they will likely need to be recalculated and adjusted in the config, see the docs for how to calculate this new value. NOTE: This does not apply to addon users which are unable to configure this value.
• More config validation checks have been added, it is possible that Frigate will fail to start due to an error that has been caught, the error will need to be fixed before frigate can start.
• RTMP is now disabled by default and the role is not automatically added. It is highly recommend to move to the new RTSP streams via the bundled go2rtc.
• Changes have been made to the way recordings segments are stored, external scripts which access the recordings file structure directly may be broken.

Retention limited by available storage

Frigate now limits its recordings to available storage, if the storage for recordings gets below 1 hour left then Frigate will delete the oldest recording segments to make room for newer ones. Frigate will also not fail if there is no space to save recordings.

go2rtc restreaming

go2rtc has been bundled inside Frigate. The configuration can be set directly inside Frigate's config file nested under the go2rtc section.

Due to many issues with RTMP, it is now deprecated in favor of using the bundled go2rtc to provide an RTSP stream. Streams configured in go2rtc can also be used by Frigate to reduce connections to the camera, see the restream docs for more info.

Birdseye restreaming is also now supported at rtsp://frigate_ip:8554/birdseye

NOTE: Port 8554 will need to be mapped in the docker run or docker compose file for the restream to be accessed outside the container.

New live stream options

The bundled go2rtc also enables new MSE and WebRTC live view options in the frontend which enable low-latency full-framerate live views that support audio.

NOTES:

• MSE is not supported on iPhones but is supported on all other devices.
• WebRTC will likely require additional setup, see the live view docs for more info

The live view options are set in the Frigate WebUI for each camera individually.

New detector types

Frigate now supports new detector types along with the Google Coral TPU.

OpenVINO

The OpenVINO detector type runs an OpenVINO IR model on Intel CPU, GPU and VPU hardware. OpenVINO is supported on 6th Gen Intel platforms (Skylake) and newer. A supported Intel platform is required to use the GPU device with OpenVINO. The MYRIAD device may be run on any platform, including Arm devices. For detailed system requirements, see OpenVINO System Requirements

TensorRT

NVidia GPUs may be used for object detection using the TensorRT libraries. Due to the size of the additional libraries, this detector is only provided in images with the -tensorrt tag suffix. The TensortRT detector is able to run on x86 hosts that have an Nvidia GPU which supports the 11.x series of CUDA libraries. The minimum driver version on the host system must be >=450.80.02. Also the GPU must support a Compute Capability of 5.0 or greater. This generally correlates to a Maxwell-era GPU or newer, check the TensorRT docs for more info.

NOTE: The link in the docs is for the final release location, for the beta the script is located at https://raw.githubusercontent.com/blakeblackshear/frigate/dev/docker/tensorrt_models.sh

New system page

The Debug page has been renamed to System. It now includes much more information and links to easily get vainfo and ffprobe data.

The GPUs section will show each GPU based on the hwaccel args, depending on the type of GPU different information is supported. For example Nvidia GPUs will have the name while others will be generic, also intel does not support memory usage. There is also a VAINFO button which will make it easier to diagnose hwaccel issues and verify that the hwaccel driver is being used correctly.

Each camera will have their own process CPU & memory usage so it will be easier to see which process is using those resources. There is also an FFPROBE button which will be helpful to understand what each stream is presenting and make it easier to include that in support issues.

The debug config has also been removed, the config can be copied using the config page in the WebUI.

New storage page

Frigate WebUI now has a built in storage page which shows the general usage for both storage and memory. It also shows a per-camera storage usage and stream bandwidth. This should make it a lot easier to have a general idea how much storage is being used by each camera.

New logs page

Frigate WebUI now has built in logs, this will make copying and viewing logs much easier. Currently the logs are static meaning the page must be refreshed to view new logs.

New config editor

Frigate WebUI now has a built in config editor with syntax highlighting and schema validation. This means that the config will be validated before it can be saved which will make yaml config much easier to manage.

NOTE: The previous docker-compose or docker CLI may have had the /config.yml set to :ro or read-only. That will need to be removed for the config editor to be able to save the new file.

MQTT is now optional

Frigate no longer requires MQTT to function, MQTT is also setup asynchronously so errors will be more clear and frigate won't stop when mqtt is enabled but not setup correctly.

NOTE: MQTT is still required for the Frigate-HomeAssistant Integration

No changes are needed for existing users.

FFMpeg presets

FFMPEG presets for common configurations are now added, making the config cleaner and allowing the underlying args to be changed between releases without being a breaking change. It is highly recommended to update the configuration to use these presets.

See https://deploy-preview-4055--frigate-docs.netlify.app/configuration/ffmpeg_presets for more info on how these should be used.

Example: Enabling Audio In Recordings

before:

output_args:
    record: -f segment -segment_time 10 -segment_format mp4 -reset_timestamps 1 -strftime 1 -c:v copy -c:a aac

after:

output_args:
  record: preset-record-generic-audio-aac

This also enables presets for hardware acceleration which will be used to further reduce CPU usage by using the GPU to optimize scaling and other workloads.

Improved events filters

• Multi Select Filters: Each filter now supports multi select so multiple cameras, labels, etc. can be viewed at the same time.
• Favorited Event Filter: Events can now be filtered to only show favorited events along with the existing filters.

Recordings updates

Recording segments are now stored in UTC to avoid issues with DST. In order to avoid a breaking change, the path of the stored segm...

0.12.0 Beta 4

Major Changes for 0.12.0

❗❗Notice❗❗
I want to recognize @NickM-27 for all the contributions he made on this release and all the support he helps provide in the issues. If you have been considering sponsoring this project with either a one time contribution or a recurring contribution, I would request that you do so at his sponsors page.

Link to updated docs: https://deploy-preview-4055--frigate-docs.netlify.app/

Changes Since Beta 3

• Restream config has been rewritten. There is no longer a restream role and instead the full go2rtc config is supported under the go2rtc config. We realized it didn't make sense to have restream under the ffmpeg config and the cross referencing between inputs was difficult to understand.

So your existing config which looks like:

cameras:
  test_cam:
    ffmpeg:
      output_args:
        record: preset-record-generic-audio-copy
      inputs:
        - path: rtsp://127.0.0.1:8554/test_cam?video=copy&audio=aac # <--- the name here must match the name of the camera
          input_args: preset-rtsp-restream
          roles:
            - record
            - detect
        - path: rtsp://192.168.1.5:554/live0 # <--- 1 connection to camera stream
          roles:
            - restream

will now look like

go2rtc:
  streams:
    test_cam: ffmpeg:rtsp://192.168.1.5:554/live0#video=copy#audio=aac#audio=opus

cameras:
  test_cam:
    ffmpeg:
      output_args:
        record: preset-record-generic-audio-copy
      inputs:
        - path: rtsp://127.0.0.1:8554/test_cam?video=copy&audio=aac # <--- the name here must match the name of the camera in restream
          input_args: preset-rtsp-restream
          roles:
            - record
            - detect

NOTE: The go2rtc config does not currently support env var substitution.

• Ability to set which stream is used for live view live -> stream_name
• preset-record-generic-audio has been renamed to preset-record-generic-audio-aac
• restream -> jsmpeg has been moved back to live
• New ui -> timezone and ui -> live_mode configurations
• Show snapshot and reocrdings storage individually if not using the same drive
• Storage page now shows storage sizes in relevant units
• new presets and fixes for existing presets
• update docs that 127.0.0.1 should be used instead of localhost for restream streams
• tensorrt detector fixed with certain models
• Events page now shows how long ago an event occurred on desktop

BREAKING CHANGES

• If using the Frigate-HomeAssistant Integration it will need to be updated to 4.0.0 beta01 to avoid breaking changes with Frigate 0.12
• Changes have been made to the database, a backup of the database will need to be made before updating if you want to roll-back.
• Some deployment approaches are overwriting the PATH environment value to an old value. If you see errors like ./run: line 7: exec: nginx: not found, then you need to stop overriding your PATH. This happens with both Proxmox LXC and Portainer (#3223 the database will need to be deleted to roll-back successfully.
• More config validation checks have been added, it is possible that Frigate will fail to start due to an error that has been caught, the error will need to be fixed before frigate can start.
• RTMP is now disabled by default and the role is not automatically added. It is highly recommend to move to the new RTSP based restream.
• Changes have been made to the way recordings segments are stored, external scripts which access the recordings file structure directly may be broken.

Retention limited by available storage

Frigate now limits its recordings to available storage, if the storage for recordings gets below 1 hour left then Frigate will delete the oldest recording segments to make room for newer ones. Frigate will also not fail if there is no space to save recordings.

RTSP restreaming

Due to many issues with RTMP based restream, RTMP is now deprecated in favor of a new RTSP restream. The restream of a camera can be accessed at rtsp://frigate_ip:8554/config_camera_name. The restream can also be used inside Frigate to reduce connections to the camera, see the restream docs for more info.

Birdseye restreaming is also now supported at rtsp://frigate_ip:8554/birdseye

NOTE: Port 8554 will need to be mapped in the docker run or docker compose file for the restream to be accessed outside the container.

New live stream options

The new RTSP restream also enables new MSE and WebRTC live view options in the frontend which enable low-latency full-framerate live views that support audio.

NOTES:

• MSE is not supported on iPhones but is supported on all other devices.
• WebRTC will likely require additional setup, see the live view docs for more info

The live view options are set in the Frigate WebUI for each camera individually.

New detector types

Frigate now supports new detector types along with the Google Coral TPU.

OpenVINO

The OpenVINO detector type runs an OpenVINO IR model on Intel CPU, GPU and VPU hardware. OpenVINO is supported on 6th Gen Intel platforms (Skylake) and newer. A supported Intel platform is required to use the GPU device with OpenVINO. The MYRIAD device may be run on any platform, including Arm devices. For detailed system requirements, see OpenVINO System Requirements

TensorRT

NVidia GPUs may be used for object detection using the TensorRT libraries. Due to the size of the additional libraries, this detector is only provided in images with the -tensorrt tag suffix. The TensortRT detector is able to run on x86 hosts that have an Nvidia GPU which supports the 11.x series of CUDA libraries. The minimum driver version on the host system must be >=450.80.02. Also the GPU must support a Compute Capability of 5.0 or greater. This generally correlates to a Maxwell-era GPU or newer, check the TensorRT docs for more info.

NOTE: The link in the docs is for the final release location, for the beta the script is located at https://raw.githubusercontent.com/blakeblackshear/frigate/dev/docker/tensorrt_models.sh

New system page

The Debug page has been renamed to System. It now includes much more information and links to easily get vainfo and ffprobe data.

The GPUs section will show each GPU based on the hwaccel args, depending on the type of GPU different information is supported. For example Nvidia GPUs will have the name while others will be generic, also intel does not support memory usage. There is also a VAINFO button which will make it easier to diagnose hwaccel issues and verify that the hwaccel driver is being used correctly.

Each camera will have their own process CPU & memory usage so it will be easier to see which process is using those resources. There is also an FFPROBE button which will be helpful to understand what each stream is presenting and make it easier to include that in support issues.

The debug config has also been removed, the config can be copied using the config page in the WebUI.

New storage page

Frigate WebUI now has a built in storage page which shows the general usage for both storage and memory. It also shows a per-camera storage usage and stream bandwidth. This should make it a lot easier to have a general idea how much storage is being used by each camera.

New logs page

Frigate WebUI now has built in logs, this will make copying and viewing logs much easier. Currently the logs are static meaning the page must be refreshed to view new logs.

New config editor

Frigate WebUI now has a built in config editor with syntax highlighting and schema validation. This means that the config will be validated before it can be saved which will make yaml config much easier to manage.

NOTE: The previous docker-compose or docker CLI may have had the /config.yml set to :ro or read-only. That will need to be removed for the config editor to be able to save the new file.

MQTT is now optional

Frigate no longer requires MQTT to function, MQTT is also setup asynchronously so errors will be more clear and frigate won't stop when mqtt is enabled but not setup correctly.

NOTE: MQTT is still required for the Frigate-HomeAssistant Integration

No changes are needed for existing users.

FFMpeg presets

FFMPEG presets for common configurations are now added, making the config cleaner and allowing the underlying args to be changed between releases without being...

0.12.0 Beta 3

Major Changes for 0.12.0

❗❗Notice❗❗
I want to recognize @NickM-27 for all the contributions he made on this release and all the support he helps provide in the issues. If you have been considering sponsoring this project with either a one time contribution or a recurring contribution, I would request that you do so at his sponsors page.

Link to updated docs: https://deploy-preview-4055--frigate-docs.netlify.app/

Changes Since Beta 2

• We have decided to stop publishing builds to Dockerhub and new builds will be available exclusively on GHCR going forward. Please update to use the new image locations by adding ghcr.io/ in front of your image names. (blakeblackshear/frigate:0.12.0-beta3 needs to be changed to ghcr.io/blakeblackshear/frigate:0.12.0-beta3)
• There was a bug that meant recordings were not stored in UTC, this has been fixed. For users with timezones behind UTC there will be no effect, for users ahead of UTC the first X hours frigate will not overwrite the recordings but after that will continue as normal.
• Rework ffmpeg to fix broken hwaccel for RPi. If you are currently setting args manually you should switch to the new ffmpeg presets
• Show CPU usage of detector processes
• Simplify QSV args and fix bug that caused fps to be higher than specified
• Fix go2rtc logs please update your custom frigate-go2rtc file to make logs plaintext
• Fix copying to clipboard in WebUI
• Improve clarity of gpu stats error messages

BREAKING CHANGES

• If using the Frigate-HomeAssistant Integration it will need to be updated to 4.0.0 beta01 to avoid breaking changes with Frigate 0.12
• Changes have been made to the database, a backup of the database will need to be made before updating if you want to roll-back.
• Some deployment approaches are overwriting the PATH environment value to an old value. If you see errors like ./run: line 7: exec: nginx: not found, then you need to stop overriding your PATH. This happens with both Proxmox LXC and Portainer (#3223 the database will need to be deleted to roll-back successfully.
• live configuration has been moved to restream -> jsmpeg
• More config validation checks have been added, it is possible that Frigate will fail to start due to an error that has been caught, the error will need to be fixed before frigate can start.
• RTMP is now disabled by default and the role is not automatically added. It is highly recommend to move to the new RTSP based restream.
• Changes have been made to the way recordings segments are stored, external scripts which access the recordings file structure directly may be broken.

Retention limited by available storage

Frigate now limits its recordings to available storage, if the storage for recordings gets below 1 hour left then Frigate will delete the oldest recording segments to make room for newer ones. Frigate will also not fail if there is no space to save recordings.

RTSP restreaming

Due to many issues with RTMP based restream, RTMP is now deprecated in favor of a new RTSP restream. This also comes with a new restream role which is enabled by default. The restream of a camera can be accessed at rtsp://frigate_ip:8554/config_camera_name. The restream can also be used inside Frigate to reduce connections to the camera, see the restream docs for more info.

Birdseye restreaming is also now supported at rtsp://frigate_ip:8554/birdseye

NOTE: Port 8554 will need to be mapped in the docker run or docker compose file for the restream to be accessed outside the container.

New live stream options

The new RTSP restream also enables new MSE and WebRTC live view options in the frontend which enable low-latency full-framerate live views that support audio.

NOTES:

• MSE is not supported on iPhones but is supported on all other devices.
• WebRTC will likely require additional setup, see the live view docs for more info

The live view options are set in the Frigate WebUI for each camera individually.

New detector types

Frigate now supports new detector types along with the Google Coral TPU.

OpenVINO

The OpenVINO detector type runs an OpenVINO IR model on Intel CPU, GPU and VPU hardware. OpenVINO is supported on 6th Gen Intel platforms (Skylake) and newer. A supported Intel platform is required to use the GPU device with OpenVINO. The MYRIAD device may be run on any platform, including Arm devices. For detailed system requirements, see OpenVINO System Requirements

TensorRT

NVidia GPUs may be used for object detection using the TensorRT libraries. Due to the size of the additional libraries, this detector is only provided in images with the -tensorrt tag suffix. The TensortRT detector is able to run on x86 hosts that have an Nvidia GPU which supports the 11.x series of CUDA libraries. The minimum driver version on the host system must be >=450.80.02. Also the GPU must support a Compute Capability of 5.0 or greater. This generally correlates to a Maxwell-era GPU or newer, check the TensorRT docs for more info.

NOTE: The link in the docs is for the final release location, for the beta the script is located at https://raw.githubusercontent.com/blakeblackshear/frigate/dev/docker/tensorrt_models.sh

New system page

The Debug page has been renamed to System. It now includes much more information and links to easily get vainfo and ffprobe data.

The GPUs section will show each GPU based on the hwaccel args, depending on the type of GPU different information is supported. For example Nvidia GPUs will have the name while others will be generic, also intel does not support memory usage. There is also a VAINFO button which will make it easier to diagnose hwaccel issues and verify that the hwaccel driver is being used correctly.

Each camera will have their own process CPU & memory usage so it will be easier to see which process is using those resources. There is also an FFPROBE button which will be helpful to understand what each stream is presenting and make it easier to include that in support issues.

The debug config has also been removed, the config can be copied using the config page in the WebUI.

New storage page

Frigate WebUI now has a built in storage page which shows the general usage for both storage and memory. It also shows a per-camera storage usage and stream bandwidth. This should make it a lot easier to have a general idea how much storage is being used by each camera.

New logs page

Frigate WebUI now has built in logs, this will make copying and viewing logs much easier. Currently the logs are static meaning the page must be refreshed to view new logs.

New config editor

Frigate WebUI now has a built in config editor with syntax highlighting and schema validation. This means that the config will be validated before it can be saved which will make yaml config much easier to manage.

NOTE: The previous docker-compose or docker CLI may have had the /config.yml set to :ro or read-only. That will need to be removed for the config editor to be able to save the new file.

MQTT is now optional

Frigate no longer requires MQTT to function, MQTT is also setup asynchronously so errors will be more clear and frigate won't stop when mqtt is enabled but not setup correctly.

NOTE: MQTT is still required for the Frigate-HomeAssistant Integration

No changes are needed for existing users.

FFMpeg presets

FFMPEG presets for common configurations are now added, making the config cleaner and allowing the underlying args to be changed between releases without being a breaking change. It is highly recommended to update the configuration to use these presets.

See https://deploy-preview-4055--frigate-docs.netlify.app/configuration/ffmpeg_presets for more info on how these should be used.

Example: Enabling Audio In Recordings

before:

output_args:
    record: -f segment -segment_time 10 -segment_format mp4 -reset_timestamps 1 -strftime 1 -c:v copy -c:a aac

after:

output_args:
  record: preset-record-generic-audio

This also enables presets for hardware acceleration which will be used to further reduce CPU usage by using the GPU to optimize scaling and other workloads.

Improved events filters

• **M...

0.12.0 Beta 2

Major Changes for 0.12.0

❗❗Notice❗❗
I want to recognize @NickM-27 for all the contributions he made on this release and all the support he helps provide in the issues. If you have been considering sponsoring this project with either a one time contribution or a recurring contribution, I would request that you do so at his sponsors page.

Link to updated docs: https://deploy-preview-4055--frigate-docs.netlify.app/

Changes Since Beta 1

• preset-intel-vaapi and preset-amd-vaapi have been renamed to preset-vaapi due to there being no differences between them
• new restream -> video_encoding option which can be used to re-encode the restream
• Events zone & sub label filter have None option
• vainfo stderr won't be returned if return code is 0
• many preset & restream bug fixes

BREAKING CHANGES

• If using the Frigate-HomeAssistant Integration it will need to be updated to 4.0.0 beta01 to avoid breaking changes with Frigate 0.12
• Changes have been made to the database, a backup of the database will need to be made before updating if you want to roll-back.
• Some deployment approaches are overwriting the PATH environment value to an old value. If you see errors like ./run: line 7: exec: nginx: not found, then you need to stop overriding your PATH. This happens with both Proxmox LXC and Portainer (#3223 the database will need to be deleted to roll-back successfully.
• live configuration has been moved to restream -> jsmpeg
• More config validation checks have been added, it is possible that Frigate will fail to start due to an error that has been caught, the error will need to be fixed before frigate can start.
• RTMP is now disabled by default and the role is not automatically added. It is highly recommend to move to the new RTSP based restream.
• Changes have been made to the way recordings segments are stored, external scripts which access the recordings file structure directly may be broken.

Retention limited by available storage

Frigate now limits its recordings to available storage, if the storage for recordings gets below 1 hour left then Frigate will delete the oldest recording segments to make room for newer ones. Frigate will also not fail if there is no space to save recordings.

RTSP restreaming

Due to many issues with RTMP based restream, RTMP is now deprecated in favor of a new RTSP restream. This also comes with a new restream role which is enabled by default. The restream of a camera can be accessed at rtsp://frigate_ip:8554/config_camera_name. The restream can also be used inside Frigate to reduce connections to the camera, see the restream docs for more info.

Birdseye restreaming is also now supported at rtsp://frigate_ip:8554/birdseye

NOTE: Port 8554 will need to be mapped in the docker run or docker compose file for the restream to be accessed outside the container.

New live stream options

The new RTSP restream also enables new MSE and WebRTC live view options in the frontend which enable low-latency full-framerate live views that support audio.

NOTES:

• MSE is not supported on iPhones but is supported on all other devices.
• WebRTC will likely require additional setup, see the live view docs for more info

The live view options are set in the Frigate WebUI for each camera individually.

New detector types

Frigate now supports new detector types along with the Google Coral TPU.

OpenVINO

The OpenVINO detector type runs an OpenVINO IR model on Intel CPU, GPU and VPU hardware. OpenVINO is supported on 6th Gen Intel platforms (Skylake) and newer. A supported Intel platform is required to use the GPU device with OpenVINO. The MYRIAD device may be run on any platform, including Arm devices. For detailed system requirements, see OpenVINO System Requirements

TensorRT

NVidia GPUs may be used for object detection using the TensorRT libraries. Due to the size of the additional libraries, this detector is only provided in images with the -tensorrt tag suffix. The TensortRT detector is able to run on x86 hosts that have an Nvidia GPU which supports the 11.x series of CUDA libraries. The minimum driver version on the host system must be >=450.80.02. Also the GPU must support a Compute Capability of 5.0 or greater. This generally correlates to a Maxwell-era GPU or newer, check the TensorRT docs for more info.

NOTE: The link in the docs is for the final release location, for the beta the script is located at https://raw.githubusercontent.com/blakeblackshear/frigate/dev/docker/tensorrt_models.sh

New system page

The Debug page has been renamed to System. It now includes much more information and links to easily get vainfo and ffprobe data.

The GPUs section will show each GPU based on the hwaccel args, depending on the type of GPU different information is supported. For example Nvidia GPUs will have the name while others will be generic, also intel does not support memory usage. There is also a VAINFO button which will make it easier to diagnose hwaccel issues and verify that the hwaccel driver is being used correctly.

Each camera will have their own process CPU & memory usage so it will be easier to see which process is using those resources. There is also an FFPROBE button which will be helpful to understand what each stream is presenting and make it easier to include that in support issues.

The debug config has also been removed, the config can be copied using the config page in the WebUI.

New storage page

Frigate WebUI now has a built in storage page which shows the general usage for both storage and memory. It also shows a per-camera storage usage and stream bandwidth. This should make it a lot easier to have a general idea how much storage is being used by each camera.

New logs page

Frigate WebUI now has built in logs, this will make copying and viewing logs much easier. Currently the logs are static meaning the page must be refreshed to view new logs.

New config editor

Frigate WebUI now has a built in config editor with syntax highlighting and schema validation. This means that the config will be validated before it can be saved which will make yaml config much easier to manage.

NOTE: The previous docker-compose or docker CLI may have had the /config.yml set to :ro or read-only. That will need to be removed for the config editor to be able to save the new file.

MQTT is now optional

Frigate no longer requires MQTT to function, MQTT is also setup asynchronously so errors will be more clear and frigate won't stop when mqtt is enabled but not setup correctly.

NOTE: MQTT is still required for the Frigate-HomeAssistant Integration

No changes are needed for existing users.

FFMpeg presets

FFMPEG presets for common configurations are now added, making the config cleaner and allowing the underlying args to be changed between releases without being a breaking change. It is highly recommended to update the configuration to use these presets.

See https://deploy-preview-4055--frigate-docs.netlify.app/configuration/ffmpeg_presets for more info on how these should be used.

Example: Enabling Audio In Recordings

before:

output_args:
    record: -f segment -segment_time 10 -segment_format mp4 -reset_timestamps 1 -strftime 1 -c:v copy -c:a aac

after:

output_args:
  record: preset-record-generic-audio

This also enables presets for hardware acceleration which will be used to further reduce CPU usage by using the GPU to optimize scaling and other workloads.

Improved events filters

• Multi Select Filters: Each filter now supports multi select so multiple cameras, labels, etc. can be viewed at the same time.
• Favorited Event Filter: Events can now be filtered to only show favorited events along with the existing filters.

Recordings updates

Recording segments are now stored in UTC to avoid issues with DST. In order to avoid a breaking change, the path of the stored segments has changed from /media/frigate/recordings/%Y-%m/%d/%H-%s.mp4 to /media/frigate/recordings/%Y-%m-%d/%H-%s.mp4.

Recordings in the frontend are now shown in the timezone of the device viewing frigate, so the timezone set on the server running frigate is irrelevant.

No changes are needed for existing users.

What's Changed

• Storage Based Ret...

0.12.0 Beta 1

Major Changes for 0.12.0

❗❗Notice❗❗
I want to recognize @NickM-27 for all the contributions he made on this release and all the support he helps provide in the issues. If you have been considering sponsoring this project with either a one time contribution or a recurring contribution, I would request that you do so at his sponsors page.

Link to updated docs: https://deploy-preview-4055--frigate-docs.netlify.app/

BREAKING CHANGES

• Changes have been made to the database, a backup of the database will need to be made before updating if you want to roll-back. Otherwise the database will need to be deleted to roll-back successfully.
• More config validation checks have been added, it is possible that Frigate will fail to start due to an error that has been caught, the error will need to be fixed before frigate can start.
• RTMP is now disabled by default and the role is not automatically added. It is highly recommend to move to the new RTSP based restream.
• live configuration has been moved to restream -> jsmpeg
• Changes have been made to the way recordings segments are stored, external scripts which access the recordings file structure directly may be broken.
• If using the Frigate-HomeAssistant Integration it will need to be updated to 4.0.0 beta01 to avoid breaking changes with Frigate 0.12
• Some deployment approaches are overwriting the PATH environment value to an old value. If you see errors like ./run: line 7: exec: nginx: not found, then you need to stop overriding your PATH. This happens with both Proxmox LXC and Portainer (#3223)

Retention limited by available storage

Frigate now limits its recordings to available storage, if the storage for recordings gets below 1 hour left then Frigate will delete the oldest recording segments to make room for newer ones. Frigate will also not fail if there is no space to save recordings.

RTSP restreaming

Due to many issues with RTMP based restream, RTMP is now deprecated in favor of a new RTSP restream. This also comes with a new restream role which is enabled by default. The restream of a camera can be accessed at rtsp://frigate_ip:8554/config_camera_name. The restream can also be used inside Frigate to reduce connections to the camera, see the restream docs for more info.

Birdseye restreaming is also now supported at rtsp://frigate_ip:8554/birdseye

NOTE: Port 8554 will need to be mapped in the docker run or docker compose file for the restream to be accessed outside the container.

New live stream options

The new RTSP restream also enables new MSE and WebRTC live view options in the frontend which enable low-latency full-framerate live views that support audio.

NOTES:

• MSE is not supported on iPhones but is supported on all other devices.
• WebRTC will likely require additional setup, see the live view docs for more info

The live view options are set in the Frigate WebUI for each camera individually.

New detector types

Frigate now supports new detector types along with the Google Coral TPU.

OpenVINO

The OpenVINO detector type runs an OpenVINO IR model on Intel CPU, GPU and VPU hardware. OpenVINO is supported on 6th Gen Intel platforms (Skylake) and newer. A supported Intel platform is required to use the GPU device with OpenVINO. The MYRIAD device may be run on any platform, including Arm devices. For detailed system requirements, see OpenVINO System Requirements

TensorRT

NVidia GPUs may be used for object detection using the TensorRT libraries. Due to the size of the additional libraries, this detector is only provided in images with the -tensorrt tag suffix. The TensortRT detector is able to run on x86 hosts that have an Nvidia GPU which supports the 11.x series of CUDA libraries. The minimum driver version on the host system must be >=450.80.02. Also the GPU must support a Compute Capability of 5.0 or greater. This generally correlates to a Maxwell-era GPU or newer, check the TensorRT docs for more info.

NOTE: The link in the docs is for the final release location, for the beta the script is located at https://raw.githubusercontent.com/blakeblackshear/frigate/dev/docker/tensorrt_models.sh

New system page

The Debug page has been renamed to System. It now includes much more information and links to easily get vainfo and ffprobe data.

The GPUs section will show each GPU based on the hwaccel args, depending on the type of GPU different information is supported. For example Nvidia GPUs will have the name while others will be generic, also intel does not support memory usage. There is also a VAINFO button which will make it easier to diagnose hwaccel issues and verify that the hwaccel driver is being used correctly.

Each camera will have their own process CPU & memory usage so it will be easier to see which process is using those resources. There is also an FFPROBE button which will be helpful to understand what each stream is presenting and make it easier to include that in support issues.

The debug config has also been removed, the config can be copied using the config page in the WebUI.

New storage page

Frigate WebUI now has a built in storage page which shows the general usage for both storage and memory. It also shows a per-camera storage usage and stream bandwidth. This should make it a lot easier to have a general idea how much storage is being used by each camera.

New logs page

Frigate WebUI now has built in logs, this will make copying and viewing logs much easier. Currently the logs are static meaning the page must be refreshed to view new logs.

New config editor

Frigate WebUI now has a built in config editor with syntax highlighting and schema validation. This means that the config will be validated before it can be saved which will make yaml config much easier to manage.

NOTE: The previous docker-compose or docker CLI may have had the /config.yml set to :ro or read-only. That will need to be removed for the config editor to be able to save the new file.

MQTT is now optional

Frigate no longer requires MQTT to function, MQTT is also setup asynchronously so errors will be more clear and frigate won't stop when mqtt is enabled but not setup correctly.

NOTE: MQTT is still required for the Frigate-HomeAssistant Integration

No changes are needed for existing users.

FFMpeg presets

FFMPEG presets for common configurations are now added, making the config cleaner and allowing the underlying args to be changed between releases without being a breaking change. It is highly recommended to update the configuration to use these presets.

Example: Enabling Audio In Recordings

before:

output_args:
    record: -f segment -segment_time 10 -segment_format mp4 -reset_timestamps 1 -strftime 1 -c:v copy -c:a aac

after:

output_args:
  record: preset-record-generic-audio

This also enables presets for hardware acceleration which will be used to further reduce CPU usage by using the GPU to optimize scaling and other workloads.

Improved events filters

• Multi Select Filters: Each filter now supports multi select so multiple cameras, labels, etc. can be viewed at the same time.
• Favorited Event Filter: Events can now be filtered to only show favorited events along with the existing filters.

Recordings updates

Recording segments are now stored in UTC to avoid issues with DST. In order to avoid a breaking change, the path of the stored segments has changed from /media/frigate/recordings/%Y-%m/%d/%H-%s.mp4 to /media/frigate/recordings/%Y-%m-%d/%H-%s.mp4.

Recordings in the frontend are now shown in the timezone of the device viewing frigate, so the timezone set on the server running frigate is irrelevant.

No changes are needed for existing users.

What's Changed

• Storage Based Retention by @NickM-27 in #3942
• Docs update: Update camera specific input_agrs for ESP32-cam using ESPHome by @MariusMueller in #4171
• Add go2rtc and add restream role / live source by @NickM-27 in #4082
• Catch case where segment is bad length by @NickM-27 in #4228
• Add option enabled for each camera in config by @banthungpron...

0.11.1 Release

What's Changed

• FIX: Set a timeout on github release check by @NickM-27 in #3969
• FEAT: Mqtt sub labels by @NickM-27 in #3899
• FIX: Update motion topic when enabling due to detect topic by @NickM-27 in #3898
• DOCS: Add an example for birdseye override at camera level by @Mincka in #3922
• DOCS: indentation, device Id by @kamahat in #3921
• FIX: don't overwrite segments that already exist by @blakeblackshear in #3995
• FIX: Fix sub label access by @NickM-27 in #4015
• FIX: Catch ffprobe empty stdout by @NickM-27 in #4016
• DOCS: Fix some typos in docs by @xconverge in #4020
• FIX: Remove snapshot requirement for thumbnail event query by @NickM-27 in #4039
• DOCS: Link to env var option by @NickM-27 in #4032
• DOCS: Restructured camera specific documentation by @menkej in #4005

New Contributors

• @Mincka made their first contribution in #3922
• @kamahat made their first contribution in #3921
• @xconverge made their first contribution in #4020
• @menkej made their first contribution in #4005

Full Changelog: v0.11.0...v0.11.1

Image: blakeblackshear/frigate:0.11.1

0.11.0 Release

Major Changes for 0.11.0

🚨 🚨 BREAKING CHANGES 🚨 🚨

• Several addon users have reported that a full uninstall and reinstall is necessary. In place upgrades are failing with a "Invalid build environment, can't build this add-on!" message in the supervisor logs.
• If you are using the Home Assistant integration and/or custom lovelace card, be sure to update those to their latest releases as well.
• Update to ffmpeg5 will break any custom input arguments using the stimeout parameter. This needs to be renamed to timeout in your config.
• Some amd64 users may need to set the environment variable LIBVA_DRIVER_NAME=i965 to get similar hardware acceleration performance to previous versions.
• Upgrading will run migrations on the database file that are not backwards compatible. In order to rollback to 0.10.0, you will either need to restore an old database file or delete the database files so they can be recreated.
• This version includes a significant rework of the docker build. This may have broken ffmpeg hardware acceleration for some hardware that was working previously. Please open an issue if this happens so we can try and track down what's missing.
• Some deployment approaches are overwriting the PATH environment value to an old value. If you see errors like No such file or directory: 'ffmpeg', then you need to stop overriding your PATH. This happens with both Proxmox LXC and Portainer (#3223)
• The max_seconds config setting under events has been removed as it no longer has any effect

Frigate+ Integration

With this release, users can easily send snapshots to Frigate+ for labeling directly from the Events view. Note that Frigate+ is still in development, and custom models are not yet available. There is no cost to create an account and submit labeled images. Making it simpler to submit images should accelerate the build out of a robust training set.

To enable the Frigate+ functionality, you need to obtain an API Key from your Frigate+ account on the settings page and set it via the PLUS_API_KEY environment variable or in the addon configuration page. Note that this cannot be set in the yml configuration file. It must be set in your compose file or docker command.

Here is the roadmap for Frigate+:

• Launch web version allowing manual upload of training examples and labeling
• Integrate submission in Frigate
• Launch Frigate optimized models
• Launch individually optimized models
• Integrate labeling and suggestions in Frigate

Updated Events View

• Speed. The events view has been completely revamped and should be much faster than it was before.
• Slightly larger thumbnails.
• You no longer have to refresh the page to see the latest events.
• You can "star" or "favorite" events to tell Frigate to keep associated recordings and the snapshot indefinitely.
• Sub labels have been added to allow setting arbitrary labels on events. For example, you can use deepstack to run facial recognition and update the event with the name of the person detected. (#2949)

Updated Recordings View

• Speed. The recordings view doesn't look different, but it has been completely overhauled. It should be much faster, and event data and thumbnails are lazy loaded to reduce the amount of data that is loaded when visiting the page.
• Smoother seeking and transitions. Re-renders of the player have been reduced and you should see smoother seek behavior when selecting events.
• 16x playback was added for browsers other than Firefox.

Updated Dockerbuild

• Frigate is now built on top of plain Debian containers and consolidated into a single multiarch image. Support for nvidia decoding is built into the single image. There is no longer a need for a special tag.

Experimental Timeline UI

Not recommended for use yet, but an alternative timeline UI has been added. It has very limited browser/device support. #2830

Other changes

• MQTT sensors for any object type #2908
• Update latest object endpoints to reference most recent event from database (you will no longer see black images for objects under the camera in live view) #2944
• Added a new ratio filter for object filters #2952
• Camera recordings always in sidebar #2846
• Enable and set mode per camera for birdseye #3083
• Customize order and hide cameras from the UI #2981
• Enable improve_contrast via MQTT #3011
• Enable/disable motion detection independent of object detection via MQTT #3117
• MQTT topic for motion detection #3152
• Batch deletes of recordings when more than 100,000 recordings need to be deleted
• Switch to Btbn ffmpeg builds
• Improve cache handling for thumbnails and snapshots of completed events
• Fixes hwaccel issues for Raspberry Pi users
• Updates to debian 11 as a base image
• Consolidate Dockerfile to enable multiarch images
• Birdseye icon can now be customized #2979
• Frigate now checks for a newer release on startup and exposes that in the stats endpoint #3038
• Initial implementation of mypy and type checking
• Images from backend now have appropriate cache headers
• Motion contour_area and threshold values can now be adjusted dynamically via mqtt (#3154)
• Fix bug with bounding boxes outside of frame
• Ensure playlist is in front of error messages in videojs
• Fixes for H265 events and recordings in browsers with native support for H265 (thanks @uvjustin)
• Fixes for stuttering playback issues in some circumstances (thanks @uvjustin)

Full Changelog: v0.10.1...v0.11.0

Image: blakeblackshear/frigate:0.11.0

0.11.0 Release Candidate 3

Major Changes for 0.11.0

Link to updated docs: https://deploy-preview-2829--frigate-docs.netlify.app/

Changes since rc2

• Fix bug when multiple requests to download clip are initiated
• Fix bug with bounding boxes outside of frame (round 2)
• Add ability to view snapshots in UI when video exists
• Ensure playlist is in front of error messages in videojs

Changes since rc1

• Switch to using BtbN ffmpeg builds to resolve AAC errors with rtsp-simple-server (now at version 5.1)
  • NOTE: Those who set the LIBVA_DRIVER_NAME_JELLYFIN variable now need to update it to LIBVA_DRIVER_NAME
• Fixes for H265 events and recordings in browsers with native support for H265 (thanks @uvjustin)
• Fixes for stuttering playback issues in some circumstances (thanks @uvjustin)
• Fix bug where bounding box sometimes outside of frame
• Ensure labels with spaces work properly
• Update videojs

BREAKING CHANGES

• Update to ffmpeg5 will break any custom input arguments using the stimeout parameter. This needs to be renamed to timeout in your config.
• Some amd64 users may need to set the environment variable LIBVA_DRIVER_NAME=i965 to get similar hardware acceleration performance to previous builds.
• Upgrading to the beta will run migrations on the database file that are not backwards compatible. In order to rollback to 0.10.0, you will either need to restore an old database file or delete the database files so they can be recreated.
• This version includes a significant rework of the docker build. This may have broken ffmpeg hardware acceleration for some hardware that was working previously. Please open an issue if this happens so we can try and track down what's missing.
• Some deployment approaches are overwriting the PATH environment value to an old value. If you see errors like No such file or directory: 'ffmpeg', then you need to stop overriding your PATH. This happens with both Proxmox LXC and Portainer (#3223)
• The max_seconds config setting under events has been removed as it no longer has any effect

Frigate+ Integration

With this release, users can easily send snapshots to Frigate+ for labeling directly from the Events view. Note that Frigate+ is still in development, and custom models are not yet available. There is no cost to create an account and submit labeled images. Making it simpler to submit images should accelerate the build out of a robust training set.

To enable the Frigate+ functionality, you need to obtain an API Key from your Frigate+ account on the settings page and set it via the PLUS_API_KEY environment variable. I am working on getting this added into the Home Assistant Addon as well.

Here is the roadmap for Frigate+:

• Launch web version allowing manual upload of training examples and labeling
• Integrate submission in Frigate
• Launch Frigate optimized models
• Launch individually optimized models
• Integrate labeling and suggestions in Frigate

Updated Events View

• Speed. The events view has been completely revamped and should be much faster than it was before.
• Slightly larger thumbnails.
• You no longer have to refresh the page to see the latest events.
• You can "star" or "favorite" events to tell Frigate to keep associated recordings and the snapshot indefinitely.
• Sub labels have been added to allow setting arbitrary labels on events. For example, you can use deepstack to run facial recognition and update the event with the name of the person detected. (#2949)

Updated Recordings View

• Speed. The recordings view doesn't look different, but it has been completely overhauled. It should be much faster, and event data and thumbnails are lazy loaded to reduce the amount of data that is loaded when visiting the page.
• Smoother seeking and transitions. Re-renders of the player have been reduced and you should see smoother seek behavior when selecting events.
• 16x playback was added for browsers other than Firefox.

Updated Dockerbuild

• Frigate is now built on top of plain Debian containers and consolidated into a single multiarch image.

Experimental Timeline UI

Not recommended for use yet, but an alternative UI has been added. It has very limited browser/device support. #2830

Other changes

• MQTT sensors for any object type #2908
• Update latest object endpoints to reference most recent event from database (you will no longer see black images for objects under the camera in live view) #2944
• Added a new ratio filter for object filters #2952
• Camera recordings always in sidebar #2846
• Enable and set mode per camera for birdseye #3083
• Customize order and hide cameras from the UI #2981
• Enable improve_contrast via MQTT #3011
• Enable/disable motion detection independent of object detection via MQTT #3117
• MQTT topic for motion detection #3152
• Batch deletes of recordings when more than 100,000 recordings need to be deleted
• Switch to Btbn ffmpeg builds
• Improve cache handling for thumbnails and snapshots of completed events
• Fixes hwaccel issues for Raspberry Pi users
• Updates to debian 11 as a base image
• Consolidate Dockerfile to enable multiarch images
• Birdseye icon can now be customized #2979
• Frigate now checks for a newer release on startup and exposes that in the stats endpoint #3038
• Initial implementation of mypy and type checking
• Images from backend now have appropriate cache headers
• Motion contour_area and threshold values can now be adjusted dynamically via mqtt (#3154)

Full Changelog: v0.10.0...v0.11.0-rc3

Image: blakeblackshear/frigate:0.11.0-rc3

0.11.0 Release Candidate 2

Major Changes for 0.11.0

Link to updated docs: https://deploy-preview-2829--frigate-docs.netlify.app/

Changes since rc1

• Switch to using BtbN ffmpeg builds to resolve AAC errors with rtsp-simple-server (now at version 5.1)
  • NOTE: Those who set the LIBVA_DRIVER_NAME_JELLYFIN variable now need to update it to LIBVA_DRIVER_NAME
• Fixes for H265 events and recordings in browsers with native support for H265 (thanks @uvjustin)
• Fixes for stuttering playback issues in some circumstances (thanks @uvjustin)
• Fix bug where bounding box sometimes outside of frame
• Ensure labels with spaces work properly
• Update videojs

BREAKING CHANGES

• Update to ffmpeg5 will break any custom input arguments using the stimeout parameter. This needs to be renamed to timeout in your config.
• Some amd64 users may need to set the environment variable LIBVA_DRIVER_NAME=i965 to get similar hardware acceleration performance to previous builds.
• Upgrading to the beta will run migrations on the database file that are not backwards compatible. In order to rollback to 0.10.0, you will either need to restore an old database file or delete the database files so they can be recreated.
• This version includes a significant rework of the docker build. This may have broken ffmpeg hardware acceleration for some hardware that was working previously. Please open an issue if this happens so we can try and track down what's missing.
• Some deployment approaches are overwriting the PATH environment value to an old value. If you see errors like No such file or directory: 'ffmpeg', then you need to stop overriding your PATH. This happens with both Proxmox LXC and Portainer (#3223)
• The max_seconds config setting under events has been removed as it no longer has any effect

Frigate+ Integration

With this release, users can easily send snapshots to Frigate+ for labeling directly from the Events view. Note that Frigate+ is still in development, and custom models are not yet available. There is no cost to create an account and submit labeled images. Making it simpler to submit images should accelerate the build out of a robust training set.

To enable the Frigate+ functionality, you need to obtain an API Key from your Frigate+ account on the settings page and set it via the PLUS_API_KEY environment variable. I am working on getting this added into the Home Assistant Addon as well.

Here is the roadmap for Frigate+:

• Launch web version allowing manual upload of training examples and labeling
• Integrate submission in Frigate
• Launch Frigate optimized models
• Launch individually optimized models
• Integrate labeling and suggestions in Frigate

Updated Events View

• Speed. The events view has been completely revamped and should be much faster than it was before.
• Slightly larger thumbnails.
• You no longer have to refresh the page to see the latest events.
• You can "star" or "favorite" events to tell Frigate to keep associated recordings and the snapshot indefinitely.
• Sub labels have been added to allow setting arbitrary labels on events. For example, you can use deepstack to run facial recognition and update the event with the name of the person detected. (#2949)

Updated Recordings View

• Speed. The recordings view doesn't look different, but it has been completely overhauled. It should be much faster, and event data and thumbnails are lazy loaded to reduce the amount of data that is loaded when visiting the page.
• Smoother seeking and transitions. Re-renders of the player have been reduced and you should see smoother seek behavior when selecting events.
• 16x playback was added for browsers other than Firefox.

Updated Dockerbuild

• Frigate is now built on top of plain Debian containers and consolidated into a single multiarch image.

Experimental Timeline UI

Not recommended for use yet, but an alternative UI has been added. It has very limited browser/device support. #2830

Other changes

• MQTT sensors for any object type #2908
• Update latest object endpoints to reference most recent event from database (you will no longer see black images for objects under the camera in live view) #2944
• Added a new ratio filter for object filters #2952
• Camera recordings always in sidebar #2846
• Enable and set mode per camera for birdseye #3083
• Customize order and hide cameras from the UI #2981
• Enable improve_contrast via MQTT #3011
• Enable/disable motion detection independent of object detection via MQTT #3117
• MQTT topic for motion detection #3152
• Batch deletes of recordings when more than 100,000 recordings need to be deleted
• Switch to jellyfin ffmpeg
• Improve cache handling for thumbnails and snapshots of completed events
• Fixes hwaccel issues for Raspberry Pi users
• Updates to debian 11 as a base image
• Consolidate Dockerfile to enable multiarch images
• Birdseye icno can now be customized #2979
• Frigate now checks for a newer release on startup and exposes that in the stats endpoint #3038
• Initial implementation of mypy and type checking
• Images from backend now have appropriate cache headers
• Motion contour_area and threshold values can now be adjusted dynamically via mqtt (#3154)

Full Changelog: v0.10.0...v0.11.0-rc2

Image: blakeblackshear/frigate:0.11.0-rc2

0.11.0 Release Candidate 1

Major Changes for 0.11.0

Link to updated docs: https://deploy-preview-2829--frigate-docs.netlify.app/

Changes since beta 7

• Fixed "Send to Frigate+" for addon users

BREAKING CHANGES

• Update to ffmpeg5 will break any custom input arguments using the stimeout parameter. This needs to be renamed to timeout in your config.
• Some amd64 users may need to set the environment variable LIBVA_DRIVER_NAME_JELLYFIN=i965 to get similar hardware acceleration performance to previous builds.
• Upgrading to the beta will run migrations on the database file that are not backwards compatible. In order to rollback to 0.10.0, you will either need to restore an old database file or delete the database files so they can be recreated.
• This version includes a significant rework of the docker build. This may have broken ffmpeg hardware acceleration for some hardware that was working previously. Please open an issue if this happens so we can try and track down what's missing.
• Some deployment approaches are overwriting the PATH environment value to an old value. If you see errors like No such file or directory: 'ffmpeg', then you need to stop overriding your PATH. This happens with both Proxmox LXC and Portainer (#3223)
• The max_seconds config setting under events has been removed as it no longer has any effect

Frigate+ Integration

With this release, users can easily send snapshots to Frigate+ for labeling directly from the Events view. Note that Frigate+ is still in development, and custom models are not yet available. There is no cost to create an account and submit labeled images. Making it simpler to submit images should accelerate the build out of a robust training set.

To enable the Frigate+ functionality, you need to obtain an API Key from your Frigate+ account on the settings page and set it via the PLUS_API_KEY environment variable. I am working on getting this added into the Home Assistant Addon as well.

Here is the roadmap for Frigate+:

• Launch web version allowing manual upload of training examples and labeling
• Integrate submission in Frigate
• Launch Frigate optimized models
• Launch individually optimized models
• Integrate labeling and suggestions in Frigate

Updated Events View

• Speed. The events view has been completely revamped and should be much faster than it was before.
• Slightly larger thumbnails.
• You no longer have to refresh the page to see the latest events.
• You can "star" or "favorite" events to tell Frigate to keep associated recordings and the snapshot indefinitely.
• Sub labels have been added to allow setting arbitrary labels on events. For example, you can use deepstack to run facial recognition and update the event with the name of the person detected. (#2949)

Updated Recordings View

• Speed. The recordings view doesn't look different, but it has been completely overhauled. It should be much faster, and event data and thumbnails are lazy loaded to reduce the amount of data that is loaded when visiting the page.
• Smoother seeking and transitions. Re-renders of the player have been reduced and you should see smoother seek behavior when selecting events.
• 16x playback was added for browsers other than Firefox.

Updated Dockerbuild

• Frigate is now built on top of plain Debian containers and consolidated into a single multiarch image.

Experimental Timeline UI

Not recommended for use yet, but an alternative UI has been added. It has very limited browser/device support. #2830

Other changes

• MQTT sensors for any object type #2908
• Update latest object endpoints to reference most recent event from database (you will no longer see black images for objects under the camera in live view) #2944
• Added a new ratio filter for object filters #2952
• Camera recordings always in sidebar #2846
• Enable and set mode per camera for birdseye #3083
• Customize order and hide cameras from the UI #2981
• Enable improve_contrast via MQTT #3011
• Enable/disable motion detection independent of object detection via MQTT #3117
• MQTT topic for motion detection #3152
• Batch deletes of recordings when more than 100,000 recordings need to be deleted
• Switch to jellyfin ffmpeg
• Improve cache handling for thumbnails and snapshots of completed events
• Fixes hwaccel issues for Raspberry Pi users
• Updates to debian 11 as a base image
• Consolidate Dockerfile to enable multiarch images
• Birdseye icno can now be customized #2979
• Frigate now checks for a newer release on startup and exposes that in the stats endpoint #3038
• Initial implementation of mypy and type checking
• Images from backend now have appropriate cache headers
• Motion contour_area and threshold values can now be adjusted dynamically via mqtt (#3154)

Full Changelog: v0.10.0...v0.11.0-rc1

Image: blakeblackshear/frigate:0.11.0-rc1