0.15.0 Release #16387
Replies: 22 comments 28 replies
-
|
When will 0.15 be available in the |
Beta Was this translation helpful? Give feedback.
-
|
it already is, you likely just need to have docker pull down the latest and rebuild the container |
Beta Was this translation helpful? Give feedback.
-
|
Thank you devs, for your outstanding work! |
Beta Was this translation helpful? Give feedback.
-
|
Thanks all for your work!! |
Beta Was this translation helpful? Give feedback.
-
|
Devs, this update is incredible. Semantic search alone is blowing my mind. Loving new explore UI... so much info! Thank you! |
Beta Was this translation helpful? Give feedback.
-
|
OMG - I was messing (struggling) with a few AI blueprints for HomeAssistant, then this popped up and just worked. How cool. |
Beta Was this translation helpful? Give feedback.
-
A secure context (https) is actually a browser-enforced requirement for the notifications API. |
Beta Was this translation helpful? Give feedback.
-
|
The dev docker-compose file has this (introduced in #14865): Do we need to consider this when upgrading from v0.14? |
Beta Was this translation helpful? Give feedback.
-
|
If you plan to use the tensorrt docker image for object detection, you need to define this env var. See the docs. This is explicitly set to an empty string for users who are not using tensorrt for object detection but want to use Semantic Search on an nvidia GPU. |
Beta Was this translation helpful? Give feedback.
-
|
To be clear this isn't required if yolonas is being used for object detection with tensorrt |
Beta Was this translation helpful? Give feedback.
-
|
Also given the SHM changes, is this section of the docs up to date? From my understanding of the release docs, Frigate will no longer exit if it is not set high enough: |
Beta Was this translation helpful? Give feedback.
-
|
These docs are correct, they were updated in this PR. |
Beta Was this translation helpful? Give feedback.
-
|
i still cant export timelapse videos |
Beta Was this translation helpful? Give feedback.
-
|
Guess I'm one of the ones the update broke. Just keep getting this in the logs over and over, among other things. Here's my config: config file Logs2025-02-08 21:35:19.313194470 [2025-02-08 21:35:19] ffmpeg.Back_Yard.detect ERROR : [vost#1:0/rawvideo @ 0x56086fc9bb00] Terminating thread with return code -22 (Invalid argument) |
Beta Was this translation helpful? Give feedback.
-
|
You should create a support discussion |
Beta Was this translation helpful? Give feedback.
-
|
Going back I re-read everything twice and saw that we had to perhaps change our hwaccel setting so I changed it from: -hwaccel vaapi -hwaccel_device /dev/dri/renderD128 and now it seems to be working. :P' |
Beta Was this translation helpful? Give feedback.
-
|
My camera feed broke also. Changed from "preset-vaapi" to both h265 and h264 presets stated in the release notes, neither worked. So I changed it back to "preset-vaapi" and set ffmpeg to "5.0", still didn't work. So I've just reverted to 0.14.1 for now and maybe forever? |
Beta Was this translation helpful? Give feedback.
-
|
You should open a support discussion with your config and logs. |
Beta Was this translation helpful? Give feedback.
-
|
I was looking forward to notifications, unfortunately they are not available in settings menu when i logon using the ssl port and credentials, am i missing something? |
Beta Was this translation helpful? Give feedback.
-
|
Is it a secure connection? If the browser doesn't say it's secure then it won't work |
Beta Was this translation helpful? Give feedback.
-
|
I don't have an ssl cert so its not secure, however if i access it via edge browser on pc, i get the notification menu but not on ipad safari. |
Beta Was this translation helpful? Give feedback.
-
|
I'm assuming it's required for Safari to mark the connection secure, which is what the notification API being available is based on |
Beta Was this translation helpful? Give feedback.
-
|
Ok thanks, HA for now |
Beta Was this translation helpful? Give feedback.
-
|
Hello thanks for the update. Sending images to Frigate+ is now much more cumbersome and complicated... is it not possible to improve the process as it was before? It was much easier before |
Beta Was this translation helpful? Give feedback.
-
|
Many users have found it easier, actually. See the FAQ, Usage question 1. |
Beta Was this translation helpful? Give feedback.
-
|
Hi, have you read the release notes on the recommended workflow for submitting to frigate+? Because following that workflow it is actually fewer clicks to submit to Frigate+ |
Beta Was this translation helpful? Give feedback.
-
|
Thanks for this update! I've read the docs on Semantic Search and Generative AI and enabled them both. Seems I've got a couple of problems, which I don't know if they're related-
|
Beta Was this translation helpful? Give feedback.
-
|
Beta Was this translation helpful? Give feedback.
-
|
Thanks for the quick response!
|
Beta Was this translation helpful? Give feedback.
-
|
My camera stream is not working anymore since this update. ffmpeg:rtsp://admin:[email protected]:554/Streaming/Channels/101#video=copy I had to add "path: '5.0'" in ffmpeg section. Is there any possibility to use version 7 in my case? |
Beta Was this translation helpful? Give feedback.
-
|
there's no way to say without seeing the config and logs, you should create a support discussion |
Beta Was this translation helpful? Give feedback.
-
|
Thanks for your work I've been using Frigate for a while now and I'm impressed with its lightweightness, simplicity and reliability. I have updated to 0.15 yesterday seamlessly and my detector inference speed has significantly improved (from 80ms to about 20ms) using Openvino on Intel 5th generation i3 with 3 cameras and Mobilenet. Maybe due to the SHM change, ffmpeg update or Openvino version update. |
Beta Was this translation helpful? Give feedback.
-
|
Not sure the best place to ask, but is there a roadmap or just general idea of what 0.16 will be focused on? Just curious. |
Beta Was this translation helpful? Give feedback.
-
|
The main features are updating the base image to Debian 12 (including python 3.11), face recognition, license plate recognition, and many improvements to the live streaming and other parts of the UI |
Beta Was this translation helpful? Give feedback.
-
|
My HA backups went from 750-800 to 1.4GB a day after implementing this. I assume that’s cost of all the extra ai stuff ? I’m not backup up the media folder. Be interesting to see what it will be tomorrow. |
Beta Was this translation helpful? Give feedback.
-
|
Looking good, I am continually amazed by how good this NVR is. Extremely minor question - I know these are harmless but they bug me, any way to get these out of the logs in the future: |
Beta Was this translation helpful? Give feedback.
-
|
what hwaccel do you have enabled? |
Beta Was this translation helpful? Give feedback.
-
|
just preset-vaapi |
Beta Was this translation helpful? Give feedback.
-
|
I was a Shinobi user until year before last and thought I would try frigate as a few clicks from home assistant and I was amazed at how stable it was. Shinobi needed a restart of cameras regularly for some reason (weekly) but Frigate - just worked from day 1 - and I did the setup remotely while I was on holiday! I have said it before - it is bulletproof. |
Beta Was this translation helpful? Give feedback.
-
|
Just a shout-out here, to the developers of Frigate with HA. Excellent piece of software, really robust, fast (with a USB coral). It's so good to have this available to us. Much kudos for your work! |
Beta Was this translation helpful? Give feedback.
-
|
Adding to this shout-out: This release is just fantastic. Very stable and I love the vision you all have for what Frigate can achieve. Semantic search is blowing my mind, and to think it works with 8 cameras on my old Intel E3-1230L v3 lol. CCTV hasn't been this fun for me in a long time. 👍 |
Beta Was this translation helpful? Give feedback.
-
|
Hi all and thanks to the developers for this new version!!! I have Frigate 0.14.1 installed in a Proxmox container installed using PVE scripts, no Docker I have installed 0.15 version in a new container using same script, so starting from scratch, and I've copied config.yml and frigate.db to a safe location, from 0.14.1, stopped it. I see the Frigate interface, but I don't see any camera, in the camera page I just see the left side icons and a black page on the right If I go to Configuration Editor, I see just a spinning wheel, same thing if I go into he Log page What can I check? This is my config,yml This is in the /var/log/syslog after I've added in the config file Thanks |
Beta Was this translation helpful? Give feedback.
-
|
See the FAQ, Upgrade issues question 2. |
Beta Was this translation helpful? Give feedback.
-
|
Thanks @hawkeye217 ok, so for now I will stay on 0.14 the tteck script does not install Frigate in Docker, so my question is, if I install a Docker container and follow the installation method for docker, do you think it will work? |
Beta Was this translation helpful? Give feedback.
-
|
If you want to use Proxmox, a VM is the suggested installation method at this point. |
Beta Was this translation helpful? Give feedback.
-
|
So, I've installed a Docker container using tteck script. Then modified the container config with the bus number in the row Then, I've installed Frigate using the documentation for Docker compose And now it's working fine, with coral detected. |
Beta Was this translation helpful? Give feedback.
-
|
The issue users were having trouble with was using the semantic search feature. That's what requires changes to the script. |
Beta Was this translation helpful? Give feedback.
-
|
Could I leave out of my config the genAI and semantic search aspects, so that my Frigate 0.15 would more-or-less be the same as 0.14 (albeit with a slightly different UI) ? (I might be resource limited/I'm having trouble with Frigate on TrueNAS/both) |
Beta Was this translation helpful? Give feedback.
-
|
Yes, they are disabled by default |
Beta Was this translation helpful? Give feedback.
-
|
nice - thanks. I had 0.14 running on TrueNAS, then I upgraded to 0.15 on TrueNAS yesterday evening and it ran fine, so then I started to add genAI and semantic search and I ended somehow up with a Frigate UI "framework" but none of the pages populated. I have got into a terrible muddle and I am now starting from scratch (I think - not sure - this is all via an obfuscated docker process internal to TN apps!). edit: I looked at the various mounts and mappings, deleted everything inside and started from scratch and built up to my full config a camera at a time, so it is all working now. Now that my earlier tears of dismay have fully dried, I can "baseline" it and start adding semantic search and maybe genAI to see if my h/w can cope. edit again: yes: genAI and semsearch are "fitted" ... Frigate is running and I shall wait until later to see if they work ....yes, they do! |
Beta Was this translation helpful? Give feedback.
and others
-
Images
ghcr.io/blakeblackshear/frigate:0.15.0ghcr.io/blakeblackshear/frigate:0.15.0-standard-arm64ghcr.io/blakeblackshear/frigate:0.15.0-tensorrtghcr.io/blakeblackshear/frigate:0.15.0-tensorrt-jp4ghcr.io/blakeblackshear/frigate:0.15.0-tensorrt-jp5ghcr.io/blakeblackshear/frigate:0.15.0-rkghcr.io/blakeblackshear/frigate:0.15.0-rocmghcr.io/blakeblackshear/frigate:0.15.0-h8lChanges since RC2
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:
frigate.dbfileshm_sizeis too low then a warning will be printed in the log stating that it needs to be increased.recordconfig has been refactored to allow for direct control of how longalertsanddetectionsare 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.hwaccelpreset they are using (preset-vaapimay need to now bepreset-intel-qsv-h264orpreset-intel-qsv-h265) if camera feeds are not functioning correctly after upgrading. This may need to be adjusted on a per-camera basis. If aqsvpreset is not working properly, you may still need to use apreset-vaapior revert to the previous ffmpeg version as described below.path: "5.0"in yourffmpeg:config entry. For example:ffmpegis no longer part of$PATH. In most cases this is handled automatically.execstreams will need to add the full path for ffmpeg which in most cases will be/usr/lib/ffmpeg/7.0/bin/ffmpeg.bin: ffmpegdefined, it needs to be removed.modelconfig under adetectorhas been simplified to justmodel_pathas a string value. This change will be handled automatically through config migration.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, androcmFrigate 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
Other Backend Changes
Full Changelog: v0.14.1...v0.15.0
This discussion was created from the release 0.15.0 Release.
Beta Was this translation helpful? Give feedback.
All reactions