Frigate 0.15.0 → 0.16.0

There are several breaking changes in this release, Frigate will attempt to update the configuration automatically. In some cases manual changes may be required. It is always recommended to back up your current config and database before upgrading:

1. Simply copy your current config file to a new location
2. Stop Frigate and make a copy of the frigate.db file

• The TensorRT detector has been removed for Nvidia GPUs, the ONNX detector should be used instead. Nvidia recently pushed newer packages and dropped compatibility for older versions of TensorRT. Supporting native TensorRT detector directly has shown to be a large burden, making supporting newer hardware more difficult and increasing the difficulty in updating ONNX runtime. The decision has been made to remove the TensorRT detector which will allow us to focus on supporting more models and bringing more features to the Nvidia platform through ONNX runtime. Users who were running the TensorRT detector will need to update their configuration to use the ONNX detector, and download a new model. YOLO-NAS or YOLOv9 are recommended as they provide superior performance and accuracy compared to the models supported by TensorRT. Documentation

• The go2rtc audio handling has been updated to accept any audio codec instead of only AAC. This makes it easier to get audio from cameras that use PCMA/U audio. However, if the recording ffmpeg preset preset-record-generic-audio-copy is currently used it likely will need to be changed to preset-record-generic-audio-aac to continue to support audio in recordings.

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

• Object detection is now disabled by default. A config migrator will update your config globally with enabled: true for detect:. If you use Frigate with a read-only config, you may need to edit your own config to enable object detection manually.

    detect:
      enabled: true

• Frigate will no longer fall back to look for a ffmpeg binary in PATH. If you are extending the Frigate image or somehow injecting a custom ffmpeg binary in a place like /usr/local/bin, please read the custom ffmpeg build guide.
• Home Assistant Add-on users will need to be aware of several important breaking changes. See the Important Notes for Home Assistant Add-on Users section below.
• The base image for Frigate has been updated to Debian Bookworm. The Jetpack 4 (jp4) and Jetpack 5 (jp5) images have been removed due to not being compatible with the new base image. A new Jetson Jetpack 6 (jp6) build has been contributed by a community member.
• The camera group icon pack has been updated. Some of your camera group icons may need to be re-selected.
• The Hailo driver and firmware has been updated to 4.21.0. The standard Docker image now provides Hailo support. If you are using Home Assistant Operating System, version 16.0 is required. Other users will need to update the Hailo driver and firmware on their system using the user installation script.
• The ROCm migraphx detector has been removed: Instead of separately supporting ROCm via MigraphX and via ONNX, the ROCm (rocm) detector has been removed, and the onnx detector should be used instead. This change should only require changing the type: rocm to type: onnx in detectors
• An additional parameter has been added to movement_weights for autotracking users. A config migrator will add the new value so that Frigate starts, but if this fails or you are using relative zooming with autotracking, you should remove movement_weights from your config and recalibrate.
• Proxy header mapping for user roles is now required or setting the default_role to admin is required to achieve the same functionality as previous versions. This version implements a Viewer role, which is now the default for authenticated users without a role header map defined in the config. If you are using a proxy, you must include admin in your mapped role header in order for admin users to retain their elevated privileges. See the documentation.
• The strftime_fmt config option is now deprecated and will be removed in a future version. The UI will now define time formats based on your language and locale.
• Some API routes are now protected and require credentials or changes. With the introduction of the Viewer role and the ability to mark review items as reviewed separately per-user, changes may be needed to any services making calls to Frigate's API.
• Some users may need to adjust the tls_insecure onvif config if ONVIF PTZ controls were previously working in past versions but fail to work in 0.16. The ONVIF package was upgraded for 0.16, and several users have reported that setting tls_insecure: false fixed their issues.

Important Notes for Home Assistant Add-on Users

For Home Assistant add-on users only

The Frigate config directory for add-on users was changed from the Home Assistant config directory to the add-on config directory. With this change, the Frigate config file and database are now part of the add-on backup taken by Home Assistant, no longer needing to backup them manually. Note that only backups after 0.16 will benefit of this change. If you took a backup of Frigate 0.15 when updating to 0.16, the Frigate config file and database will not be part of it. In that case, you should still backup them manually before updating to Frigate 0.16.

Automatic migration

Upon the first Frigate 0.16 initialization, all Frigate-related files will be moved from the Home Assistant config directory to the Frigate add-on config directory. This will mean these files will no longer be accessible through your Home Assistant /config directory. They will now be found in the /addon_configs directory, which can also be accessed through the Terminal or VS Code add-ons.

In the new directory, the Frigate config file will be named config.yml rather than frigate.yml. This aligns with people running Frigate through other means. If you want to move back to Frigate 0.15 and did not backup the config file, you can copy the config.yml from the /addons_config back to /config/frigate.yml before restoring the add-on. Consider copying back other files as well, like custom model, custom ffmpeg, and custom go2rtc. Note that the database from 0.16 is not compatible with Frigate 0.15 anyway and thus should not be copied back. To restore the database, you must restore it from a manual backup.

Moving the config directory between add-on variants

The /addon_configs directory contains the config directories of all add-ons. You can move files from one addon config directory to another, like from Frigate Beta to the stable one, or vice-versa. Make sure you do that before uninstalling the add-on, unless you do not select the Also permanently delete this addon's data when uninstalling it.

Breaking change

If your Frigate config file refers to any arbitrary files in the Home Assistant config dir, like echo:/config/ scripts, their references must be manually updated to from /config/ to /homeassistant/.

• The base image for Frigate has been updated to Debian 12 ("Bookworm") and Python 3.11, bringing many backend performance improvements. WARNING: The popular tteck Proxmox LXC script won't automatically support Frigate 0.16. Changes will need to be made to the script. Proxmox remains an officially unsupported installation method.