04 Sep 11:07

blakeblackshear

e664cb2

0.16.1 Release Latest

Latest

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)

Assets 2

16 Aug 12:30

blakeblackshear

v0.16.0

c2f8de9

0.16.0 Release

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:

Simply copy your current config file to a new location
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...

Assets 2

78 Join discussion

12 Jul 01:14

blakeblackshear

v0.15.2

3bda638

0.15.2 Release

This is a maintenance release for Frigate 0.15 that includes fixes for HAOS 16 "too many open files" errors.

What's Changed

Set ulimit by @NickM-27 in #19086
Fix ulimit setting by @NickM-27 in #19087
Fix ulimit script by @hawkeye217 in #19095
Set ulimit with Python by @hawkeye217 in #19105

Images

Full Changelog: v0.15.1...v0.15.2

Contributors

NickM-27 and hawkeye217

Assets 2

15 Apr 01:30

blakeblackshear

v0.15.1

6cb5cfb

0.15.1 Release

This is a maintenance release for Frigate 0.15 that includes two bugfixes.

What's Changed

Fix crash in get_current_frame() (#16594)
Fix trt model prepare script (#17661)

Images

Assets 2

08 Feb 18:45

blakeblackshear

v0.15.0

cea210d

0.15.0 Release

Images

Changes since RC2

None

Major Changes for 0.15.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:

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

Rewritten SHM system
- The SHM system has been rewritten to be more stable. This means that a large % of shared memory (SHM) will be used by default but the total usage will not fluctuate, and Frigate will not fail from SHM overflowing. However, this also means that having the correct SHM size for your cameras, detector, and hardware is more important to having a smooth experience with Frigate. A new calculation is done on startup, so if your shm_size is too low then a warning will be printed in the log stating that it needs to be increased.
Recording configuration changed
- The record config has been refactored to allow for direct control of how long alerts and detections are retained. These values will be automatically populated from your current config, but you may want to adjust the values that are set after updating. See the updated docs here and ensure your updated config retains the footage you want it to.
ffmpeg updates
- ffmpeg has been updated to version 7. Some Intel users may need to change what hwaccel preset they are using (preset-vaapi may need to now be preset-intel-qsv-h264 or preset-intel-qsv-h265) if camera feeds are not functioning correctly after upgrading. This may need to be adjusted on a per-camera basis. If a qsv preset is not working properly, you may still need to use a preset-vaapi or revert to the previous ffmpeg version as described below.
- The new version provides many improvements, but the old version can still be run if needed by specifying path: "5.0" in your ffmpeg: config entry. For example:
```
ffmpeg:
  path: "5.0"
```
- ffmpeg presets have been updated. It is always recommended to use ffmpeg presets rather than manual arguments.
- ffmpeg is no longer part of $PATH. In most cases this is handled automatically.
  - go2rtc exec streams will need to add the full path for ffmpeg which in most cases will be /usr/lib/ffmpeg/7.0/bin/ffmpeg.
  - If the go2rtc config has bin: ffmpeg defined, it needs to be removed.
The nested model config under a detector has been simplified to just model_path as a string value. This change will be handled automatically through config migration.
Submitting to Frigate+
- The Frigate+ view in the UI has been replaced by the new Explore view. See the notes below.

Explore

The new Explore pane in Frigate 0.15 makes it easy to explore every object tracked by Frigate. It offers a variety of filters and supports keyword and phrase-based text search, searching for similar images, and searching through descriptive text generated by AI models.

The default Explore pane shows a summary of your most recent tracked objects organized by label. Clicking the small arrow icon at the end of the list will bring you to an infinitely scrolling grid view. The grid view can also be set as the default by changing the view type from the Settings button in the top right corner of the pane.

The Explore pane also serves as the new way to submit images to Frigate+. Filters can be applied to only display tracked objects with snapshots that have not been submitted to Frigate+. The left/right arrow keys on the keyboard allow quick navigation between tracked object snapshots when looking at the Tracked Object Details pane from the grid view.

AI/ML Search

Frigate 0.15 introduces two powerful search features: Semantic Search and GenAI Search. Semantic Search can be enabled on its own, while GenAI Search works in addition to Semantic Search.

Semantic Search

Semantic Search uses a CLIP model to generate embeddings (numerical representations of images) for the thumbnails of your tracked objects, enabling searches based on text descriptions or visual similarity. This is all done locally.

For instance, if Frigate detects and tracks a car, you can use similarity search to see other instances where Frigate detected and tracked that same car. You can also quickly search your tracked objects using an "image caption" approach. Searching for "red car driving on a residential street" or "person in a blue shirt walking on the sidewalk at dawn" or even "a person wearing a black t-shirt with the word 'SPORT' on it" will produce some stunning results.

Semantic Search works by running an AI model locally on your system. Small or underpowered systems like a Raspberry Pi will not run Semantic Search reliably or at all. A dedicated GPU and 16GB of RAM is recommended for best performance.

See the Semantic Search docs for system requirements, setup instructions, and usage tips.

Generative AI

GenAI Search employs generative AI models to create descriptive text for the thumbnails of your tracked objects, which are stored in the Frigate database to enhance future searches. Supported providers include Google Gemini, Ollama, and OpenAI, so you can choose whether you want to send data to the cloud or use a locally hosted provider.

See the GenAI docs for setup instructions and use case suggestions.

Improved Tools for Debugging

Review Item Details Pane

A new Review Item Details pane can be viewed by clicking / tapping on the gray chip on a review item in the Review pane. This shows more information about the review item as well as thumbnails or snapshots for individual objects (if enabled). The pane also provides links to share the review item, download it, submit images to Frigate+, view object lifecycles, and more.

Object Lifecycle Pane

The Recordings Timeline from Frigate 0.13 has been improved upon and returns to 0.15 as the Object Lifecycle, viewable in the Review Details pane as well as the new Explore page. The new pane shows the significant moments during the object's lifecycle: when it was first seen, when it entered a zone, became stationary, etc. It also provides information about the object's area and size ratio to assist in configuring Frigate to tune out false positives.

Native Notifications

Frigate now supports notifications using the WebPush protocol. This allows Frigate to deliver notifications to devices that have registered to receive notifications in the Frigate settings, delivering them in a timely and secure manner. Currently, notifications will be delivered for all review items marked as alerts. More options for native notifications will be supported in the future.

See the notifications docs.

New Object Detectors

ONNX

ONNX is an open model standard which allows for a single model format that can run on different types of GPUs. The default, tensorrt, and rocm Frigate build variants include GPU support for efficient object detection via ONNX models, simplifying configuration and support more models. There are no default included ONNX models for object detection.

AMD MiGraphX

Support has been added for AMD GPUs via ROCm and MiGraphX. Currently there is no default included model for this detector.

Hailo-8

Support has been added for the Hailo8 and Hailo-8L hardware for object detection on both arm64 and amd64 platforms.

Other UI Changes

Rework the Storage metrics pane to be more clear how much storage each camera is using
Camera stream info button has been added to the camera metrics page allowing easy access to see camera codec information
Add button for downloading the full set of logs
The time...

Assets 2

88 Join discussion

29 Aug 22:32

blakeblackshear

v0.14.1

f4f3cfa

0.14.1 Release

Images

This is a maintenance release for Frigate 0.14 that includes bugfixes as well as performance and stability improvements.

What's Changed

Fix auth when serving Frigate at a subpath (#12815)
Fix iOS export buttons (#12755)
Ensure review cameras are sorted by config UI order if specified (#12789)
Fix default model for rknn detector (#12807)
Add button to mark alert as reviewed in filmstrip (#12878)
Add confirmation dialog before deleting review items (#12950)
Fix manual events (#12951)
Add pan/pinch/zoom capability on Frigate+ view snapshots (#12953)
Hide recording button when disabled in config (#12997)
Recordings view fixes (#13005)
Fix missing last hour preview in recordings view (#13027)
Fix export name and NaN showing in Frigate+ slider (#13030)
Prevent error when github sends bad data (#13077)
Add shortcut key "r" to mark items as reviewed in Review pane (#13087)
Fix Frigate+ view from inadvertently reloading (#13160)
Fix live player from getting stuck while loading streams and from lagging behind in poor network conditions (#13143)
Ensure previews that are generated late are not falsely excluded (#13193)
Ensure only enabled birdseye cameras are considered active (#13194)
UI fixes (#13246)
Fix cgroup detecting 0 cpu cores (#13271)
Add tooltip for icons in review event list (#13334)
Don't allow periods in zone or camera group names (#13400)
Add portal to the live player tooltip (#13389)

Assets 2

08 Aug 13:18

blakeblackshear

v0.14.0

da913d8

0.14.0 Release

Images

ghcr.io/blakeblackshear/frigate:0.14.0
ghcr.io/blakeblackshear/frigate:0.14.0-standard-arm64
ghcr.io/blakeblackshear/frigate:0.14.0-tensorrt
ghcr.io/blakeblackshear/frigate:0.14.0-tensorrt-jp4
ghcr.io/blakeblackshear/frigate:0.14.0-tensorrt-jp5
ghcr.io/blakeblackshear/frigate:0.14.0-rk

Changes since RC2

None

Major Changes for 0.14.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 backup your current config and database before upgrading:

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

Your existing events will not be visible in Frigate's new UI

An entirely new way of reviewing camera footage has been implemented in Frigate 0.14, and existing events could not be migrated
Recordings can still be viewed in the new UI using the recordings viewer (From Live view, click/tap on a camera and select the History button at the top left)
You may want to export any starred/favorite events before upgrading
If you are using the Home Assistant integration, events can still be viewed there
Recording (enabled: True for record in your config) is required to see review items and motion data in the UI

Zone/mask coordinates are now stored in the config as relative values

Frigate's configuration migrator will read your existing mask/zone coordinates and convert them for relative use internally on startup
Using the built-in mask/zone editor will make your config file incompatible with prior versions of Frigate
If you have mask/zone coordinate values that exceed the detect resolution, it will be ignored and you will see warnings in the log. Delete the mask or zone from your config and then use the editor in the UI to recreate it.

The UI's live mode is now intelligently selected

The live_mode config option is now deprecated and should be removed.

Backwards incompatible database changes

There are a number of changes made to Frigate's database, which are not backwards compatible. A backup of the database is automatically made on startup, but a manual backup is highly recommended.

Other breaking changes

RTMP was deprecated in 0.13 and has been fully removed in 0.14. You will need to remove any rtmp references in your config file.
OpenVINO has been upgraded, and Intel Neural Compute sticks are no longer supported. Support for YOLO-NAS models has been added. Additionally, AUTO mode now maps to GPU internally to avoid some unresolved issues with AUTO. The existing YOLO-X model will not work in this version.

Brand New UI

Frigate 0.14's UI has been completely rewritten (helpful walkthrough video from a user) and optimized for desktop and mobile devices, aiming to simplify the user experience by focusing on two specific goals:

Allow you to quickly see what's currently happening or what just happened on your cameras. The new Live view features a real-time dashboard with live camera feeds and a filmstrip of animated thumbnails showing recent activity.
Make reviewing video footage more efficient. Frigate intelligently identifies parts of your timeline for review by leveraging the underlying data about motion and tracked objects. The new Review area implements a scrollable grid of thumbnails alongside a timeline where a hover or swipe begins a preview playback. Review items can be configured to be pre-categorized into alerts or detections based on cameras and/or zones. The review area also provides a motion review mode, allowing real-time scrubbing of video footage for any objects of interest that Frigate may have missed.

Frigate 0.14's UI will likely change the way you review your camera footage. It's a big change, but we love it and hope you do too. See the announcement post for more information regarding the motivation, ideas, and design decisions behind the new UI.

Dashboard

The new home page for Frigate is intended to be a real-time dashboard for your cameras. Recent alerts are represented by animated thumbnails in a filmstrip view above your camera feeds. Your camera images update once per minute when no detectable activity is occurring to conserve bandwidth and resources. As soon as any motion is detected, cameras seamlessly switch to a full-resolution live stream.

Custom camera groups are now supported. Add any of your cameras (including the Birdseye camera) to user-definable groups and easily toggle between them.
On desktops and tablets, cameras in a camera group can be resized and rearranged via dragging.

Live View

Clicking a camera from the dashboard will bring up a full-resolution live view where you can quickly access historical footage, use PTZ controls, toggle camera audio, use two-way talk, and more. Zooming with pinch or a scroll wheel is also supported.

Review

The Review area of Frigate 0.14 is for quickly reviewing historical footage of interest from your cameras. Review items are indicated on a vertical timeline and displayed as a grid of previews - bandwidth-optimized, low frame rate, low resolution videos. Hovering over or swiping a preview plays the video and marks it as reviewed. If more in-depth analysis is required, the preview can be clicked/tapped and the full frame rate, full resolution recording is displayed. Review items are filterable by date, object type, and camera.

Alerts and Detections

Not every segment of video captured by Frigate may be of the same level of interest to you. Video of people who enter your property are a different priority than those walking by on the sidewalk. For this reason, Frigate 0.14 categorizes review items as alerts or detections. By default, all person and car objects are considered alerts. You can refine categorization of your review items by configuring required zones for them.

See the review docs for more information

Motion review

In Frigate 0.13, there isn’t a way to see motion activity on a timeline and watch video at that time. The ability to scrub video for things Frigate missed has been one of the most common feature requests. Within the Motion tab of the Review section, you can now scrub through the timeline for all cameras simultaneously with a timeline showing relative motion activity. In order to avoid scrubbing over time periods already included in alerts and detections, you can also scrub in motion only mode.

History

In Frigate 0.14, full frame rate, full resolution camera footage (called "recordings" in earlier versions) can be viewed and scrubbed via a timeline. Previews of your other cameras are displayed and scrubbed alongside the main selected camera.

Exporting footage from the History view has been drastically improved. Choose predefined time periods, enter a time directly, or drag handles on the timeline to select an export range.
Past exports can be viewed, renamed, deleted, and downloaded from the dedicated Export pane, accessible from the navigation bar.

Other Notable UI Changes

System stats - New charts and graphs with colored segments to track system usage history and more quickly identify problems or issues.
Status bar - A new status bar gives at-a-glance CPU/GPU usage as well as any problems or issues with Frigate.
New log viewer - The log viewer now provides a pane with links to solutions for common issues.
Real-time motion tuning - Tune motion detection settings for your cameras without editing your config file and restarting.
New mask and zone editor - Edit your masks and zones with a much-improved editor.

Authentication

Frigate now supports authentication. Frigate manages users and authentication using JWT tokens via a cookie or authorization header. Additionally, a new proxy section in the config allows you to use the user header passed from common authentication proxies such as authelia, authentik, oauth2_proxy, etc.

Authentication is enforced on a new port 8971, and port 5000 is still unauthenticated for backwards compatibility. If you want to use Frigate's authentication, update your reverse proxy to point at port 8971 instead of 5000.
Support for role based authorization (admin/user roles) will come in a future release and will support upstream authentication proxies.
The Home Assistant integration needs to be pointed at port 5000. Some recommended configuration examples are in the updated docs.

See the documentation for more information.

TLS

Since Authentication should really be used over secure connections, TLS is also enabled by default for port 8971. It can be disabled in the config file with the following yaml:

tls:
  enabled: False

Custom certificates can also be used following the tls docs.

Frigate+

Frigate 0.14 now offers a dedicated page for Frigate+ submissions, allowing more spec...

Assets 2

213 Join discussion

17 Feb 14:54

blakeblackshear

v0.13.2

6476f8a

0.13.2 Release

What's Changed

Update Makefile for 0.13.2 by @NickM-27 in #9687
Nms optimize for stationary cars by @NickM-27 in #9684
More robust onvif handling by @hawkeye217 in #9635
Don't fail if message is received before websocket start by @NickM-27 in #9634
Birdseye enhancements by @NickM-27 in #9778
Add detailed errors for unsupported label uploading to frigate+ by @Maximo-Guk in #9775
Onvif: skip non-video profiles in setup by @hawkeye217 in #9708
Mention that AMD CPUs work just fine with OpenVINO by @svenstaro in #9740
Revise VSCode hostname info in docs by @printplaatreparatie in #9709
Docs: Fix and clarify which /dev/video devices to use with Raspberry Pi by @m-d-brown in #9509
remove reference to the term credit by @blakeblackshear in #9799
Added documentation for time-lapse export (master) by @mike2307 in #9804
docs: fix links to full configuration reference by @lawm in #9808
Fix builds by @blakeblackshear in #9852
Use zoom space id in Onvif RelativeMove setup by @hawkeye217 in #9859
Fix birdseye camera comparison by @NickM-27 in #9887
Format by @NickM-27 in #9889

New Contributors

@Maximo-Guk made their first contribution in #9775
@svenstaro made their first contribution in #9740
@printplaatreparatie made their first contribution in #9709
@m-d-brown made their first contribution in #9509
@mike2307 made their first contribution in #9804
@lawm made their first contribution in #9808

Full Changelog: v0.13.1...v0.13.2

Contributors

svenstaro, m-d-brown, and 7 other contributors

Assets 2

31 Jan 23:34

blakeblackshear

v0.13.1

34fb1c2

0.13.1 Release

What's Changed

Quick fix docs by @NickM-27 in #9506
Increase hash map size by @blakeblackshear in #9515

Full Changelog: v0.13.0...v0.13.1

Contributors

blakeblackshear and NickM-27

Assets 2

31 Jan 01:24

blakeblackshear

v0.13.0

01e2d20

0.13.0 Release

Major Changes For 0.13.0

Security Advisories

The Github Security Lab team reached out to report the following security vulnerabilities.

Exploiting these vulnerabilities requires the attacker to both know very specific information about a user's Frigate server and requires an authenticated user to be tricked into clicking a specially crafted link to their Frigate instance.

This vulnerability could exploited by an attacker under the following circumstances:

Frigate publicly exposed to the internet (even with some authentication methods implemented)
Attacker knows the public address of a user's Frigate instance
Attacker crafts a specialized page which links to the user's Frigate instance
Attacker finds a way to get an authenticated user to visit their specialized page and click the button/link

If you haven't click any links to your Frigate server from unknown sources, there is no reason to believe that you have been compromised.

I have enabled the private vulnerability disclosure features inside Github for the project as well as the automated CodeQL scanning features to identify future issues.

Breaking Changes

ARM 32-bit support has officially been removed. If you are running on a Raspberry Pi with a 32-bit OS, you will need to switch to 64-bit.
You will likely experience some additional CPU usage because motion detection is now more sensitive and improve_contrast is now enabled by default. If you have specific values set in your config, it is recommended to remove them and re-calibrate as necessary.
If no detect resolution is defined then frigate will now run detect at the native camera resolution. This means if you did not explicitly set the detect width / height AND your sub stream is not 1280x720, then your masks and zones will be configured incorrectly.
Stationary object validation is now required, anyone who manually set interval: 0 will need to delete this field from the config or increase the value
Changes have been made to the DB schema, downgrading to 0.12 will require restoring from a backup or deleting the DB and existing recordings / snapshots.
NOTE: Some users have reported migrations taking a while and frigate frontend is not available until the migrations are complete.
New location for frigate.db: Due to the support for network shares in HA OS and the popularity of storing recordings on a NAS in general, the database has a new default location of /config/frigate.db. This change is going to be done for existing users too, so frigate will automatically move the db for you.
- For Frigate Addon Users:
  The migration is handled automatically and no action is required from the user.
- For Docker Container Users:
  The migration is handled for you, but you must make sure that the docker CLI or docker-compose binds the entire /config directory and not just the /config/config.yml file.
  
  For example, if your current volume mapping is - /host/path/config_folder/config.yml:/config/config.yml it should now be - /host/path/config_folder/:/config/
The previously deprecated record -> retain_days config has been removed, this should be migrated to record -> retain -> days if you have not already.
HomeAssistant Integration 5.0 is required for the new features introduced in this release.
TensorRT has been updated and the model generation has been refactored. New models will need to be generated for 0.13 and have a new path, check the detector docs for more info.
TensorRT now requires Nvidia Driver Version 530+
The cameras in /stats have been moved to their own cameras block. This only affects users that were directly reading from the /stats data via the API or MQTT.
Removed direct access to the go2rtc http API to mitigate potential remote code execution via the exec source, you will need to map port 1984 and access directly if using go2rtc http api outside of frigate

Frigate+

Frigate+ Model Launch

Frigate+ models are now rolling out by invitation. If you would like to be invited for early access to purchase a subscription, please send an email to [email protected] from the email address on your Frigate+ account. For more information, see this discussion.

False positive submissions

You can now submit false positive detections to Frigate+ for training feedback. Note that you will still need to login to your Frigate+ account and verify the images to ensure all relevant objects are labeled before the image will be used during training. Confirming the object is a true positive will also upload the image.

Models

This release has support for Frigate+ models. The model and related information are stored at /config/model_cache. Once Frigate+ models are launched, you will be able to use the model id in your config.

model:
  path: plus://your_model_id

Community Supported Boards

In version 0.12 Frigate gained support for Intel iGPUs via OpenVINO and for Nvidia GPUs, this was a great step forward for compatibility and for more users being able to use Frigate effectively. There are many other devices, including dedicated SBCs (Small Board Computers), that Frigate could support but the maintainers do not have the time or hardware to support.

The community supported boards framework will allow community members who want to contribute to create and manage support for a particular board. This will allow Frigate to support more devices while allowing the maintainers to focus on improving the core of Frigate.

Nvidia Jetson Support

@madsciencetist has contributed a community supported board build by adding support for Jetson 4.6 and Jetson 5 devices!

More information can be found in the detector docs on how to set this up.

https://docs.frigate.video/configuration/object_detectors#nvidia-tensorrt-detector

@MarcA711 has contributed a community supported board build by adding support for devices with RockChip SoCs:

RK3566/RK3568
RK3588/RK3588S
RV1103/RV1106
RK3562

https://docs.frigate.video/configuration/object_detectors#rockchip-rknn-toolkit-lite2

Object Tracking & Motion Detection

There have been many improvements to object tracking and motion detection which make Frigate more efficient and can reduce false positives.

New Object Tracker

Frigate now uses Norfair for object tracking, this means that object attributes like size, width/height ratio, and position are used to intelligently track objects. ID swapping between tracked objects is greatly reduced in situations where a car in the driveway was confused with a car passing in the street.

Improved Motion Detection

Frigate's motion detection is now more efficient. Motion detection will also re-calibrate for flashes like lightning or when the camera switches from color to IR mode or it is moved via PTZ. This reduces CPU usage during these changes and reduces false positives caused by excessive motion.

Historical Data

Frigate now uses the recordings timeline data to generate an 8x8 grid for each camera. This grid holds the range of expected regions (portions of the image sent to detection) for that area of the camera frame. This helps to improve accuracy of detection after motion has occurred and can reduce false positives in some cases.

The grid is updated on each startup and every day at 2 AM for each camera that is enabled.

Minimum Time For Zone Presence

Frigate now has a configurable field for the minimum amount of time an object needs to be in a zone before it is considered in a zone. For example, currently in Frigate if you have a front_yard zone and someone is walking by and briefly steps into the front yard Frigate would create an event for this. However, you may prefer for events to only be created if a person is in the front yard for multiple frames before creating an event.

zones:
  my_zone:
    inertia: 3  # <- 3 consecutive frames needed to consider object in zone
    coordinates: ...

Recordings Improvements

There have been a number of improvements to the management of recordings

Recordings Exporting

Frigate now supports exporting recordings in standard format or as a time-lapse. Exported recordings are stored in /media/frigate/exports and are downloadable from the UI.

Recordings Timeline Metadata

Frigate now saves metadata for key moments in an event such as when the tracked object is detected, enters or exits zone, becomes active / stationary, and leaves. This metadata is used to overlay on top of the recordings so it is easy to see what was detected and where. Note that the timing of the bounding boxes will likely be slightly off because it is based on the detect stream, but overlayed on the record stream. The annotation_offset value in the config can be used to adjust for any differences.

![Screen Shot 2023-07-27 ...