Skip to content

Releases: blakeblackshear/frigate

Release list

0.18.0 Beta 2

0.18.0 Beta 2 Pre-release
Pre-release

Choose a tag to compare

View all tags
@blakeblackshear blakeblackshear released this 26 Jul 20:58
v0.18.0-beta2
7e08f7b
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

Images

Changes since Beta 1

Security

  • GHSA-q8jx-q884-jcq9: bound REGEXP evaluation with a per-eval timeout to prevent ReDoS on the database thread
  • Fix JWT exp claim (use max_age per JWT_SESSION_LENGTH) and prevent a new token being issued on logout

Backend

  • GenAI: fix Gemini tool calling, catch an OpenAI error, expose whether a provider supports embeddings, clean up llama.cpp and use the API key when configured, and restrict the semantic search tool to English on JinaV1
  • Zones: resolve friendly names against the correct camera and render zones with friendly name + ID in the chat prompt
  • Face recognition: convert crops to RGB before embedding and catch faces that become empty after cropping
  • Runtime camera toggles: persist across config saves, re-apply overrides on save/delete without re-broadcasting, and stop dropping batched add/remove config updates in object processing
  • Embeddings and event cleanup: always clean up embeddings so they don't outlive their events, and prune object filters for unsupported labels when cleaning tracked objects
  • Various autotracking and ONVIF fixes
  • Add -vaapi_device to the birdseye restream vaapi encode preset so hwupload can init on ffmpeg 8
  • Resolve export hwaccel args global value against the correct config path
  • Don't report auto-populated object/audio filters as camera overrides
  • Derive stale replay cameras from bounded directory listings to avoid scanning all clips at startup
  • Improve error messages for Intel GPU stats
  • Fix notification test button being blocked by websocket auth
  • Replace deprecated openvino-dev with a modern package for OpenVINO model generation
  • Ensure preview and review directories are valid after deleting a camera from the UI
  • Handle indefinite events when a segment needs to forcibly be ended for a camera
  • Bump sqlite-vec to 0.1.9
  • Documentation updates

Frontend

  • Zone editing: disable the ID field when a zone is referenced in any required_zones, and delete all required_zones references when the zone is deleted
  • Exports: center the multi-camera export range on the current playback position and fix a crash when camera group icons are invalid
  • Motion search/preview: fix motion-preview playback rate and don't stay on the page when the flow is cancelled
  • Improve the classification model edit dialog (edit enabled/save_attempts, plus state/motion/interval configs)
  • Show a numeric keyboard on mobile for number-specific fields in Settings
  • Fix the birdseye reordering widget in Settings
  • Update several object icons for Frigate+ 2026.2
  • Pin react-zoom-pan-pinch to fix History zooming reset
  • Fix minor export/review activity calendar timezone handling bug
  • Various frontend tweaks and fixes (logger i18n, scrollbar, overflowing text, etc.)

Full changelog: v0.18.0-beta1...v0.18.0-beta2

Major Changes for 0.18.0

Breaking Changes

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
  • GenAI now supports multiple providers. As a result, the global genai config is now a mapping of keys to GenAI provider setups, and a new roles field defines what tasks each provider will be used for (object descriptions, review summaries, embeddings, chat, etc.). Existing configs will be automatically migrated. Documentation
  • Frigate no longer saves annotated JPEG snapshots (.jpg) to disk. Only a clean, unannotated WebP snapshot (<camera>-<id>-clean.webp) is now stored in /media/frigate/clips/. The clean_copy configuration option has been removed — clean snapshots are always saved when snapshots are enabled. The snapshots.quality default has changed from 70 to 60, reflecting the switch from JPEG to WebP encoding. Users who previously relied on the annotated .jpg files on disk should instead use the /api/events/<id>/snapshot.jpg endpoint, which now honors timestamp, bounding_box, crop, height, and quality query parameters for both in-progress and completed tracked objects. When query parameters are omitted, the camera's snapshots config values are used as defaults. Existing configs containing clean_copy will be automatically migrated. Documentation
  • The config format for zones and masks has changed to add enabled and friendly_name fields. A config migrator will make the necessary changes, but if migration fails you may need to edit your masks and zones manually.
  • Intel GPU stats reporting has changed to no longer require intel_gpu_top and now reads directly from the kernel's per-client DRM usage counters. This removes the need for CAP_PERFMON, privileged mode, or perf_event_paranoid tuning, and adds support for newer Intel GPUs (including Battlemage). Reported usage values may differ from previous versions because the measurement method has changed; the underlying GPU workload is unchanged for the same configuration.
    • Note that this change will require a Linux kernel version of 6.5 or newer on your host. Kernels older than 6.5 do not expose per-engine counters for GPUs using GuC submission.
  • FFmpeg has been updated to version 8.
    • FFmpeg 5 is deprecated and will be removed from Frigate in 0.19.
    • FFmpeg 8 introduces a known issue with go2rtc streams that transcode video using hardware acceleration. A small change to the go2rtc config is required. Documentation
  • The /api/export DELETE HTTP API endpoint has been removed and refactored to support bulk deletion of exports. A POST to /api/exports should be used instead. Documentation
  • The sync_recordings config option has been removed and replaced by the new Media Sync pane in Settings.
  • The timelapse_args export config option has been removed and replaced by custom exporting ffmpeg arguments. Documentation
  • The ui.date_format and ui.time_format config options have been removed as these fields have been unused since date/time format and handling has been determined by i18n.

New Features

Frigate 0.18 introduces several major new features.

Full UI Configuration

Frigate 0.18 introduces complete UI-based configuration management. The new Settings experience provides:

  • A categorized sidebar covering every section of the config (cameras, detectors, motion, recording, review, GenAI, semantic search, face recognition, LPR, classification models, networking, authentication, and more).
  • Per-field validation, inline descriptions, and links back to the documentation.
  • A clear distinction between global and camera-level configuration, with the ability to override global values per camera and reset back to defaults at any time.
  • Highlighting of unsaved changes, a "Save All" button that summarizes pending edits across sections, and a Reset to Default/Global button on each section.
  • Indicators showing which fields require a restart to take effect, with a one-click restart prompt when a restart-required field is changed.
  • Most of Frigate's configuration options can now be saved and applied dynamically without restarting, including most enrichment, motion, ONVIF, GenAI, and go2rtc stream settings.
  • Manual YAML file configuration is still fully supported. Documentation pages now include "Frigate UI" tabs alongside YAML examples to show exactly where each option lives in the new Settings UI.

See the documentation.

Profiles

Profiles let you define named overrides on top of your base camera configuration and switch between them on the fly — without restarting Frigate. Profiles can override a camera's detection, motion, recording, snapshots, review, zones, notifications, objects (including masks and filters), enrichments (face recognition, LPR), audio, and birdseye settings, as well as the camera's enabled state.

  • Profiles are defined at the top level of the config with optional friendly names, and per-camera overrides...
Read more
Loading
16 Join discussion

0.18.0 Beta 1

0.18.0 Beta 1 Pre-release
Pre-release

Choose a tag to compare

View all tags
@blakeblackshear blakeblackshear released this 12 Jul 17:58
v0.18.0-beta1
5f6043a
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

Images

Major Changes for 0.18.0

Breaking Changes

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
  • GenAI now supports multiple providers. As a result, the global genai config is now a mapping of keys to GenAI provider setups, and a new roles field defines what tasks each provider will be used for (object descriptions, review summaries, embeddings, chat, etc.). Existing configs will be automatically migrated. Documentation
  • Frigate no longer saves annotated JPEG snapshots (.jpg) to disk. Only a clean, unannotated WebP snapshot (<camera>-<id>-clean.webp) is now stored in /media/frigate/clips/. The clean_copy configuration option has been removed — clean snapshots are always saved when snapshots are enabled. The snapshots.quality default has changed from 70 to 60, reflecting the switch from JPEG to WebP encoding. Users who previously relied on the annotated .jpg files on disk should instead use the /api/events/<id>/snapshot.jpg endpoint, which now honors timestamp, bounding_box, crop, height, and quality query parameters for both in-progress and completed tracked objects. When query parameters are omitted, the camera's snapshots config values are used as defaults. Existing configs containing clean_copy will be automatically migrated. Documentation
  • The config format for zones and masks has changed to add enabled and friendly_name fields. A config migrator will make the necessary changes, but if migration fails you may need to edit your masks and zones manually.
  • Intel GPU stats reporting has changed to no longer require intel_gpu_top and now reads directly from the kernel's per-client DRM usage counters. This removes the need for CAP_PERFMON, privileged mode, or perf_event_paranoid tuning, and adds support for newer Intel GPUs (including Battlemage). Reported usage values may differ from previous versions because the measurement method has changed; the underlying GPU workload is unchanged for the same configuration.
  • FFmpeg has been updated to version 8.
    • FFmpeg 5 is deprecated and will be removed from Frigate in 0.19.
    • FFmpeg 8 introduces a known issue with go2rtc streams that transcode video using hardware acceleration. A small change to the go2rtc config is required. Documentation
  • The /api/export DELETE HTTP API endpoint has been removed and refactored to support bulk deletion of exports. A POST to /api/exports should be used instead. Documentation
  • The sync_recordings config option has been removed and replaced by the new Media Sync pane in Settings.
  • The timelapse_args export config option has been removed and replaced by custom exporting ffmpeg arguments. Documentation
  • The ui.date_format and ui.time_format config options have been removed as these fields have been unused since date/time format and handling has been determined by i18n.

New Features

Frigate 0.18 introduces several major new features.

Full UI Configuration

Frigate 0.18 introduces complete UI-based configuration management. The new Settings experience provides:

  • A categorized sidebar covering every section of the config (cameras, detectors, motion, recording, review, GenAI, semantic search, face recognition, LPR, classification models, networking, authentication, and more).
  • Per-field validation, inline descriptions, and links back to the documentation.
  • A clear distinction between global and camera-level configuration, with the ability to override global values per camera and reset back to defaults at any time.
  • Highlighting of unsaved changes, a "Save All" button that summarizes pending edits across sections, and a Reset to Default/Global button on each section.
  • Indicators showing which fields require a restart to take effect, with a one-click restart prompt when a restart-required field is changed.
  • Most of Frigate's configuration options can now be saved and applied dynamically without restarting, including most enrichment, motion, ONVIF, GenAI, and go2rtc stream settings.
  • Manual YAML file configuration is still fully supported. Documentation pages now include "Frigate UI" tabs alongside YAML examples to show exactly where each option lives in the new Settings UI.

See the documentation.

Profiles

Profiles let you define named overrides on top of your base camera configuration and switch between them on the fly — without restarting Frigate. Profiles can override a camera's detection, motion, recording, snapshots, review, zones, notifications, objects (including masks and filters), enrichments (face recognition, LPR), audio, and birdseye settings, as well as the camera's enabled state.

  • Profiles are defined at the top level of the config with optional friendly names, and per-camera overrides are defined under each camera.
  • The active profile is persisted across restarts and can be changed from the UI or via the frigate/profile/set MQTT topic.
  • The current profile state and the list of available profiles are published over MQTT.
  • The Settings UI shows which fields are overridden by the active profile, supports editing the base config independently from any profile, and provides per-profile camera enable/disable from the camera management view.
  • A dedicated Profiles page in the main menu shows a card-based summary of all configured profiles and their overrides.

See the documentation.

GenAI

Frigate 0.18 includes a major expansion of GenAI capabilities. In addition to multi-provider support (see Breaking Changes), there is a new dedicated llama.cpp provider with automatic model probing and context sizing, and GenAI configuration can now be updated dynamically without restarting Frigate.

See the documentation.

Chat

Frigate 0.18 introduces a Chat interface for talking to your configured GenAI provider directly from the Frigate UI. Chat is implemented as a tool-calling LLM agent with access to Frigate-specific tools, so you can ask natural language questions about your cameras, tracked objects, and review activity.

  • Streaming responses with markdown support (including tables), per-message copy buttons, message editing, and the ability to stop a streaming response.
  • Tool calls are grouped and displayed inline as the agent works, with quick links to relevant tracked objects and review items.
  • Tools include searching tracked objects, finding similar objects via semantic search, inspecting live camera context, toggling camera features, starting VLM monitoring on a camera, and a recap tool for summarizing recent activity.
  • Tracked object thumbnails and similarity results render as cards in the chat, and any event can be attached to a chat message via the paperclip button or by clicking a thumbnail.
  • A persistent quick-replies row makes it easy to start common queries from a fresh chat.

Remote Embeddings

Semantic Search embeddings can now be generated by an external GenAI provider instead of running locally. This is especially useful when you would prefer to offload embedding work to another machine or to a hosted provider.

  • Any configured GenAI provider that supports an embeddings endpoint can be selected as the embedding provider for Semantic Search.
  • The semantic search settings UI includes a dropdown for choosing which configured GenAI provider should produce embeddings.

See the documentation.

Motion Review and Motion Search

Frigate 0.18 introduces a redesigned Motion Review experience along with a new Motion Search feature.

  • Motion Search. A new motion search workflow lets you draw or select a region on a camera image and find time periods where motion occurred in that area...
Read more
Loading
195 Join discussion

0.17.2 Release

0.17.2 Release Latest
Latest

Choose a tag to compare

View all tags
@blakeblackshear blakeblackshear released this 28 Jun 12:12
v0.17.2
3d4dd3a
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

This is a maintenance release for Frigate 0.17 that includes fixes and minor changes.

Images

What's Changed

Security Advisories

These advisories impact users with publicly exposed instances with no authentication and users with viewer roles where it is important to restrict access to some cameras.

Addressed in this release:

To be addressed in future versions:

Notable Changes

  • Exports can optionally include recording segment information as chapters in mp4 metadata
  • Performance improvements when displaying previews in the live page

All Commits

New Contributors

Full Changelog: v0.17.1...v0.17.2

Contributors

NickM-27, Feni85, and 2 other contributors
Assets 2
Loading

0.17.1 Release

0.17.1 Release

Choose a tag to compare

View all tags
@blakeblackshear blakeblackshear released this 22 Mar 20:29
v0.17.1
416a9b7
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

This is a maintenance release for Frigate 0.17 that includes bugfixes and minor changes.

Images

What's Changed

Security Fixes

Notable Changes

Other Changes

New Contributors

Full Changelog: v0.17.0...v0.17.1

Contributors

tremby, f0ff886f, and 10 other contributors
Loading

0.17.0 Release

0.17.0 Release

Choose a tag to compare

View all tags
@blakeblackshear blakeblackshear released this 27 Feb 03:03
v0.17.0
f0d69f7

Images

Changes since RC3

  • None

Major Changes for 0.17.0

Breaking Changes

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
  • GenAI now supports reviews and object descriptions. As a result, the global genai config now only configures the provider. Other fields have moved under objects -> genai. See the new GenAI documentation.
  • Recordings retention is now fully tiered. This means that record -> continuous and record -> motion are separate config fields. See the examples in the documentation.
  • Some of the LPR models have been updated, and most users should manually switch to the small model, which performs well on both CPU and GPU. The large model is the same as 0.16's and is not as accurate as the upgraded small model in 0.17. Use large only if you live in a region with multi-line plates and you are having issues detecting text on them with the small model.
  • strftime_fmt was deprecated in 0.16, and should now be fully removed from the config in 0.17. Date/time formatting is based on the language selected in the UI.
  • The auto detection logic for camera resolution has changed. Some cameras fail to correctly advertise their resolution, and in previous versions, a default value was assumed that was not always correct. You may need to explicitly define detect resolution width and height for cameras in your config if Frigate hangs on startup.
  • The exec, expr, and echo sources for go2rtc are now removed by default to reduce the security risk if an attacker has access to the configuration. This can be disabled using an environment variable GO2RTC_ALLOW_ARBITRARY_EXEC A separate configuration for this for HA addon users will come in a later beta. See the documentation.
  • Nvidia GTX 900 series GPUs are no longer supported due to updates to ONNX Runtime

New Features

Frigate 0.17 introduces several major new features.

Classification Model Training

Frigate 0.17 supports classification models in two separate types: state classification and object classification. These models are trained locally on your machine using ImageNet via MobileNetV2.

State Classification

State classification allows you to choose a certain region of camera(s) with multiple states, and train on images showing these states. For example, you could create a state classification model to determine if a gate is currently open or closed.

Screen Shot 2025-10-27 at 07 51 47 AM

See the documentation.

Object Classification

Object classification allows you to choose an object type, like dog, and classify specific dogs. For example, you can train the model to classify your dog Fido and add a sub label, while not labeling unknown dogs. Another example would be classifying if a person in a construction site is wearing a helmet or not.

Screen Shot 2025-10-27 at 07 50 56 AM

See the documentation.

Custom Viewer Roles

Frigate 0.17 now has the ability to create additional viewer user roles to limit access to specific cameras. Users with the admin role can create a uniquely named role from the UI (or auth --> roles in the config) and assign at least one camera to it. Users assigned to the new role will have:

  • Guarded API access
  • Limited frontend access, following what the viewer role has access to (Live, Review/History, Explore, Exports), but only to the assigned cameras

See the documentation.

Review Item Summary with GenAI

Frigate 0.17 supports using GenAI to summarize review items. Unlike object descriptions which add a searchable description, review summaries have a structured output that instruct the AI provider to generate a title, description, and classify the activity as dangerous, suspicious, or normal.

This information is displayed in the UI automatically making it easier to see when activity requires further review and easier to understand what is happening during a particular video segment.

See the documentation.

Semantic Search Triggers

Triggers utilize Semantic Search to automate actions when a tracked object matches a specified image or description. Triggers can be configured so that Frigate executes a specific actions when a tracked object's image or description matches a predefined image or text, based on a similarity threshold. Triggers are managed per camera and can be configured via the Frigate UI in the Settings page under the Triggers tab.

See the documentation.

Object Detector Improvements

Frigate 0.17 brings performance increases for many detectors as well as support for new object detection hardware.

Nvidia GPU Performance

Support for Nvidia GPUs has been enhanced by implementing CUDA Graphs. CUDA Graphs work to reduce the involvement of the CPU for each inference, leading to faster inference times and lower CPU usage. CUDA graphs do have some limitations based on the complexity of the model, which means that YOLO-NAS, Semantic Search, and LPR models are not accelerated with CUDA Graphs. They will still continue to run on GPU as they did before.

Intel OpenVINO

Frigate 0.17 supports running models on Intel NPUs, for many models performance on NPU is similar to GPU but more efficient, leaving room to run more enrichment features on the GPU.

OpenVINO has also had many optimizations put in place to reduce memory and CPU utilization for object detection.

RKNN

Frigate 0.17 brings several improvements to RKNN platform including:

  • Automatic Model Conversion: automatically convert ONNX models to RKNN format. This allows Frigate+ and other models to be seamlessly configured and converted on startup.
  • Accelerated Enrichment Support: convert and run Semantic Search and Face Recognition models using the NPU. This greatly enhances performance while maintaining high accuracy with large model sizes.

Apple Silicon

Frigate 0.17 supports running object detection on Apple Silicon NPU. This is provided through the Apple Silicon Detector which runs on the host and connects via IPC proxy to Frigate, providing fast and efficient inferences when run within the same Apple device.

See the documentation.

YOLOv9 on Google Coral

Frigate 0.17 supports running a quantized version of YOLOv9 on Coral devices, bringing improved accuracy over the default mobiledet model. Note that due to hardware limitations, only a subset of the objects on the standard COCO labelmap is included. Frigate+ has also added support for YOLOv9 models on the Google Coral and includes support for all 41 Frigate+ labels.

See the documentation.

New Community Supported Detectors

Frigate 0.17 has community support for several new object detectors:

Frontend Improvements

In addition to supporting the new features, the frontend has many improvements.

Detail Stream

History view in 0.17 supports an additional view mode, Detail. This mode shows a card for each review item, and expanding a card reveals all tracked objects and their lifecycle events. Selecting any lifecycle event seeks the video to that exact timestamp. You can also ...

Read more
Loading
112 Join discussion

0.16.4 Release

0.16.4 Release

Choose a tag to compare

View all tags
@blakeblackshear blakeblackshear released this 29 Jan 00:42
v0.16.4
4131252
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

Images

Security Advisory

A security vulnerability was reported and addressed with this release. Exploiting this vulnerability requires authenticated access to Frigate.

What's Changed

New Contributors

Full Changelog: v0.16.3...v0.16.4

Contributors

blakeblackshear, ZhaiSoul, and 2 other contributors
Loading

0.16.3 Release

0.16.3 Release

Choose a tag to compare

View all tags
@blakeblackshear blakeblackshear released this 06 Dec 18:15
v0.16.3
9034454
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

Images

Security Advisory

A security vulnerability was reported and addressed with this release.

Exploiting this vulnerability requires authenticated access to Frigate.

Improvements

  • Improve recording playback efficiency
  • Fix certificate generation crash when using webpush notifications

What's Changed

New Contributors

Full Changelog: v0.16.2...v0.16.3

Contributors

ZhaiSoul, NickM-27, and 3 other contributors
Loading

0.16.2 Release

0.16.2 Release

Choose a tag to compare

View all tags
@blakeblackshear blakeblackshear released this 15 Oct 11:30
v0.16.2
4d58206
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

Images

Security Advisory

A security vulnerability was reported and addressed with this release.

Exploiting this vulnerability requires authenticated access to Frigate.

What's Changed

New Contributors

Full Changelog: v0.16.1...v0.16.2

Contributors

laviddichterman, ZhaiSoul, and 4 other contributors
Loading

0.16.1 Release

0.16.1 Release

Choose a tag to compare

View all tags
@blakeblackshear blakeblackshear released this 04 Sep 11:07
v0.16.1
e664cb2
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

This is a maintenance release for Frigate 0.16 that includes bugfixes and minor changes.

Images

What's Changed

Frontend Changes

  • Improve recording playback startup time on slow connections (#19503)
  • Fix export dialog overflowing due to i18n time lengths (#19736)
  • Ensure audio support is correctly queried from go2rtc streams (#19708)
  • Allow users with the viewer role to register for webpush notifications (#19640)
  • Video dimension layout fix for Chrome (#19636, #19805)
  • Remind users to restart after enabling face recognition (#19601)
  • Always allow sorting by score in Explore page (#19501)
  • Fix recognized license plate filter being incorrectly hidden in Explore filters in certain circumstances (#19491)
  • Fix unscrollable languages menu on small mobile devices (#19797)
  • Fix label in streaming stats (#19874)

Backend Changes

  • Fix i965 hwaccel driver for older Intel iGPUs (#19590)
  • Return correct mime type for some image endpoints (#19708)
  • Cleanup vod clip handling and add padding arg (#19813)
  • Catch invalid keys in genai prompts (#19657)
  • Run autotracking setup method in asyncio coroutine (#19614)
  • Fix autotracking calibration crash when zooming is disabled (#19776)
  • Fix autotracking hang for some cameras (#19873, #19879)
  • Deprecate include_thumbnails field in events API (#19584)
  • Ensure bird classification still runs if no other enrichments are enabled (#19576)
  • Latest image API endpoint fixes (#19573 and #19555)
  • Fix percentage display in recording emergency cleanup logs (#19525)
  • Support input-dtype config for Frigate+ models (#19799)
  • Set lower bound on retry_interval (#19883)
Loading

0.16.0 Release

0.16.0 Release

Choose a tag to compare

View all tags
@blakeblackshear blakeblackshear released this 16 Aug 12:30
v0.16.0
c2f8de9
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

Images

Changes since RC 4

None

Major Changes for 0.16.0

Breaking Changes

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

New Features

Frigate 0.16 introduces several major new features.

Face Recognition

Frigate utilizes face detection and recognition to apply sub-labels to known faces. Recognized faces can be included in built-in notifications and integrated into third-party notifications.

Frigate+ is not required to use Face Recognition. However, using a Frigate+ model (or a custom model that detects face natively) enhances efficiency by eliminating the need for separate face detection per person.

The accuracy of face recognition heavily depends on the quality of the images used for training. It is highly recommended to follow the training guide to achieve the best results.

Refer to the Face Recognition documentation for more.

License Plate Recognition (LPR)

Frigate detects and recognizes license plates, saving recognized plates to tracked car objects. Known license plates can also be assigned custom labels (e.g., AB12345 --> Bob's Car).

Frigate+ is not required for License Plate Recognition. However, using a Frigate+ model (or a custom model that detects license_plate natively) improves efficiency by eliminati...

Read more
Loading
78 Join discussion