Skip to content

chore(deps): update dependency blakeblackshear/frigate to v0.16.3 #518

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Open
renovate wants to merge 1 commit into
base: main
Choose a base branch
from
Open

chore(deps): update dependency blakeblackshear/frigate to v0.16.3 #518

renovate wants to merge 1 commit into from

Conversation

@renovate
Copy link
Contributor

@renovate renovate bot commented Aug 8, 2024 •
edited
Loading

Note: This PR body was truncated due to platform limits.

This PR contains the following updates:

Package Update Change
blakeblackshear/frigate minor 0.13.2 -> 0.16.3

Warning

Some dependencies could not be looked up. Check the Dependency Dashboard for more information.

Release Notes

blakeblackshear/frigate (blakeblackshear/frigate)

v0.16.3: 0.16.3 Release

Compare Source

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: blakeblackshear/frigate@v0.16.2...v0.16.3

v0.16.2: 0.16.2 Release

Compare Source

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: blakeblackshear/frigate@v0.16.1...v0.16.2

v0.16.1: 0.16.1 Release

Compare Source

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)

v0.16.0: 0.16.0 Release

Compare Source

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 eliminating the need for a separate detection model.

For additional features such as regex-based matching, refer to the License Plate Recognition documentation.

Viewer Role

Frigate 0.16 introduces a Viewer role that restricts access to system features, the configuration editor, and the Frigate HTTP API. Viewers have permissions to use the Live view, Review, and Explore.

Additionally, each user can mark review items as reviewed independently so that one user's action will not hide the review items from others.

The Users tab in Settings can be used to create users and assign roles, and these roles are enforced when accessing Frigate through the authenticated port. Documentation

More fine-grained permissions (like denying access to specific cameras, for example) will come in a future version.

Proxies can also now map user roles. See the Proxy configuration documentation.

Improved Support For Object Detection Hardware and Models

Hailo8

The Hailo8 detector has been refactored by the Hailo team to greatly improve object detection performance and to add support for more model types. Documentation

ONNX & OpenVINO

Support has been added for a variety of new models for ONNX and OpenVINO detectors

  • Frigate now supports state-of-the-art D-FINE and RF-DETR models via the ONNX and OpenVINO detectors. Documentation
  • Add YOLOv3, YOLOv4, and YOLOv9 model support. Documentation
  • Add YOLOx model support. Documentation
RockChip (RKNN)

RockChip has had the following improvements:

  • GPU and NPU stats are now supported in the UI (this requires mapping /sys as read-only, see the docs for more information)
  • RKNN Toolkit has been updated to 2.3.2
  • There is now built in support for converting custom ONNX models to RKNN format
  • Support has been added to the RKNN detector:

Camera Improvements

Dynamically Enable and Disable Cameras

Frigate now offers the ability to enable / disable cameras dynamically, including buttons in the UI, MQTT, and using the camera.turn_on / camera.turn_off services in the Home Assistant Integration. Disabling a camera stops all of Frigate's decoding and processing for that camera. See the documentation.

Live Stream Selection

Frigate now allows configuring multiple streams per camera, so that any number of streams for a single camera can be created and selected in the UI. See the Live view documentation.

Screenshot 2025-03-22 at 7 49 51 AM

Camera groups now include per-camera settings to further customize the live streaming behavior of that camera in that camera group.

Screenshot 2025-03-22 at 7 53 44 AM

Other noteworthy live streaming improvements:

  • Create on demand recordings from the single camera Live view in the UI
  • Audio can be enabled on Live view dashboards through a right-click context menu
  • Streaming statistics make it easy to view live stream mode and performance

Other UI Changes

There are many other notable improvements to the Frigate UI:

  • The review timeline has been rewritten to be more performant and support zooming using pinch-to-zoom on mobile and Ctrl + scroll wheel on desktop.
  • Plot object paths in the Object Lifecycle pane.
  • Add ability to create object masks from bounding boxes in the Object Lifecycle pane by right clicking.
  • Add edge/point snapping to the Mask/Zone editor.
  • Add the earliest recording date from the database to the Storage Metrics page.
  • Add an underline for each day that recordings are available in the History calendar pane.
  • Add a scroll bar to Logs pane and stream logs live as they are recorded.
  • Add a Frigate+ pane to Settings to show model information and allow selection of a new model from the UI.
  • Add the ability to draw a rectangle on the debug view to obtain an area (in pixels and percentage) and size ratio.
  • Add the ability to edit sub labels directly in the Tracked Object Details pane.
  • Ensure the mute/unmute state is persisted for the HLS player.
  • Add camera selection to History view.

i18n Support

Frigate now supports internationalization and localization, making it possible to change the language of the UI. The language is auto-selected based on your browser locale and can also be changed via the Languages menu in the UI.

Some languages are not fully translated. Translation contributions are welcomed and can be made using Weblate.

Backend Features and Performance Improvements

New Base Image
  • 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.
Zones and Object Area
  • Add the ability to estimate the speed of objects passing through zones and set a speed threshold to trigger zones. Documentation
  • Adds the ability to specify min_area and max_area as a decimal between 0.000001 and .99 to represent a percentage of the frame. Numbers above 1 will still represent areas in pixels. For reference, 0.000001 represents ~1 pixel at 1280x720.
  • The object area decimal value is now displayed wherever area pixels are displayed in the UI.
Semantic Search
  • Semantic Search is now optional and no longer required to be enabled to use Generative AI.
  • Jina V2 can now be used for Semantic Search, providing multi-lingual support. Documentation
  • Add the ability to trigger the reindexing of tracked object embeddings directly from the UI.
Bird Classification
  • Add the ability to classify detected birds and add the name to the tracked object's sub label. Documentation
ONVIF and Autotracking
  • Implement ONVIF reconnect if a camera goes offline.
  • Improve responsiveness of zooming when using relative zooming with autotracking.
  • Refined object tracking parameters and use re-identification when autotracking the person object.
Other notable changes
  • Export filenames now include the start and end date/time.
  • Add title as mp4 metadata to exports.
  • Add ability to specify cooldown time and suspend native notifications per camera. Documentation
  • Add an API endpoint, /recordings/summary, to return true/false for each day that recordings are available.
  • Implement de-duplication of log entries to prevent log flooding from the same message.
  • Add support for SR-IOV GPU stats.

v0.15.2: 0.15.2 Release

Compare Source

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

What's Changed

Images

Full Changelog: blakeblackshear/frigate@v0.15.1...v0.15.2

v0.15.1: 0.15.1 Release

Compare Source

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

What's Changed

Images

v0.15.0: 0.15.0 Release

Compare Source

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:

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

Screen Shot 2024-10-15 at 07 38 16 AM

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.

image

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.

image

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.

image

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 timeline handlebar will now automatically scroll while viewing recordings
  • Review items and exports can now be shared via your browser's sharing pane or via direct link url. A secure context is required for the browser/OS sharing pane to function
  • Add the ability to rename camera groups
  • Add middle mouse button support in the Review pane to open full recordings view in a new tab
  • Add Nvidia GPU encode and decode stats to system metrics
  • New desktop keyboard shortcuts. In addition to the numerous keyboard shortcuts available with 0.14, 0.15 adds several more. In Live view, the numeric keys (1-9) will move PTZ cameras to presets. In Review, Page Up and Page Down will scroll through review items
  • Accessibility updates for users with screen readers

Other Backend Changes

  • FFMPEG updated to 7.0
  • OpenVINO updated to 2024.3
  • Use FastAPI instead of Flask for the Frigate API
  • Add service manager infrastructure
  • Install onevpl tools and update drivers for Intel
  • If record is disabled for a camera then that camera will not save frames to the preview during that time
  • Fix stalled connections to certain onvif cameras
  • Fix autotracking absolute zoom interpolation logic
  • TensorRT models are no longer generated by default, the ENV var must be set

Full Changelog: blakeblackshear/frigate@v0.14.1...v0.15.0

v0.14.1: 0.14.1 Release

Compare Source

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)

v0.14.0: 0.14.0 Release

Compare Source

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:

  1. 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.
  2. 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 Birdsey

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate bot force-pushed the renovate/blakeblackshear-frigate-0.x branch from 75ca250 to 52dcc74 Compare August 30, 2024 00:04
@renovate renovate bot changed the title chore(deps): update dependency blakeblackshear/frigate to v0.14.0 chore(deps): update dependency blakeblackshear/frigate to v0.14.1 Aug 30, 2024
@renovate renovate bot force-pushed the renovate/blakeblackshear-frigate-0.x branch from 52dcc74 to e3edba8 Compare January 5, 2025 23:05
@renovate renovate bot force-pushed the renovate/blakeblackshear-frigate-0.x branch from e3edba8 to 64ccfc4 Compare February 8, 2025 21:14
@renovate renovate bot changed the title chore(deps): update dependency blakeblackshear/frigate to v0.14.1 chore(deps): update dependency blakeblackshear/frigate to v0.15.0 Feb 8, 2025
@renovate renovate bot force-pushed the renovate/blakeblackshear-frigate-0.x branch from 64ccfc4 to b90a3fc Compare April 15, 2025 02:51
@renovate renovate bot changed the title chore(deps): update dependency blakeblackshear/frigate to v0.15.0 chore(deps): update dependency blakeblackshear/frigate to v0.15.1 Apr 15, 2025
@renovate renovate bot force-pushed the renovate/blakeblackshear-frigate-0.x branch from b90a3fc to 77b1eca Compare July 12, 2025 03:29
@renovate renovate bot changed the title chore(deps): update dependency blakeblackshear/frigate to v0.15.1 chore(deps): update dependency blakeblackshear/frigate to v0.15.2 Jul 12, 2025
@renovate renovate bot force-pushed the renovate/blakeblackshear-frigate-0.x branch from 77b1eca to a9d7cc0 Compare August 16, 2025 14:14
@renovate renovate bot changed the title chore(deps): update dependency blakeblackshear/frigate to v0.15.2 chore(deps): update dependency blakeblackshear/frigate to v0.16.0 Aug 16, 2025
@renovate renovate bot force-pushed the renovate/blakeblackshear-frigate-0.x branch from a9d7cc0 to 9951dcd Compare September 4, 2025 14:15
@renovate renovate bot changed the title chore(deps): update dependency blakeblackshear/frigate to v0.16.0 chore(deps): update dependency blakeblackshear/frigate to v0.16.1 Sep 4, 2025
@renovate renovate bot force-pushed the renovate/blakeblackshear-frigate-0.x branch from 9951dcd to b632bb9 Compare October 15, 2025 14:53
@renovate renovate bot changed the title chore(deps): update dependency blakeblackshear/frigate to v0.16.1 chore(deps): update dependency blakeblackshear/frigate to v0.16.2 Oct 15, 2025
@renovate renovate bot force-pushed the renovate/blakeblackshear-frigate-0.x branch from b632bb9 to 76383e3 Compare December 6, 2025 22:29
@renovate renovate bot changed the title chore(deps): update dependency blakeblackshear/frigate to v0.16.2 chore(deps): update dependency blakeblackshear/frigate to v0.16.3 Dec 6, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

1 participant