0.16.0 Release #19536
Replies: 22 comments 56 replies
-
|
Beta Was this translation helpful? Give feedback.
-
|
That im sure it wasnt. First time im hearing about hailo. 🤷♂️ |
Beta Was this translation helpful? Give feedback.
-
|
Happened to me too. Was running 0.15.1. Update option to 0.15.2 disappeared and after deleting add-on 0.15.1, removing repository and adding it again, now it is not possible to install Frigate again. |
Beta Was this translation helpful? Give feedback.
-
The one i was using its not showing from the Repo. :/
|
Beta Was this translation helpful? Give feedback.
-
|
Beta Was this translation helpful? Give feedback.
-
|
I have found the issue here |
Beta Was this translation helpful? Give feedback.
-
|
In 16.0 RC 4 I had problems with event clips, when sending them to Telegram - they were of an incomprehensible length and often did not play at all. After rolling back to the latest release version (15) the problem went away. Was this fixed in the 16.0 release? |
Beta Was this translation helpful? Give feedback.
-
|
We had no reports of this behavior, and like it says there have been no changes between RC4 and the release |
Beta Was this translation helpful? Give feedback.
-
|
@NickM-27 Got it, i belive there was some changes in ffmpeg pipeline, i would probably report my issue soon, whenewer i have time. There was nothing interesting in logs regarding to this behaviour. |
Beta Was this translation helpful? Give feedback.
-
|
Just a heads up.. Steps I took
Tried to start frigate, however it would not boot and referenced a 10.10.0.10 camera that I do not own nor a subnet I use. Referenced "Automatic migration" section of 16.0 readme..
My fix
Log file now contains Hope this helps others. |
Beta Was this translation helpful? Give feedback.
-
|
Thanks, this will be fixed soon |
Beta Was this translation helpful? Give feedback.
-
|
I started to get this error |
Beta Was this translation helpful? Give feedback.
-
|
You should create a support discussion |
Beta Was this translation helpful? Give feedback.
-
|
Probably just a config issue but i cant seem to get object detection to work anymore. Not sure if changing over to onnx detectors from tensor or if something else is wrong. Config is attached. Any help is appreciated. |
Beta Was this translation helpful? Give feedback.
-
|
You're missing a https://docs.frigate.video/configuration/object_detectors#yolox-1 |
Beta Was this translation helpful? Give feedback.
-
|
I was hoping it was something simple like that but unfortunately object detection is still not working. Im gonna move this over to the issues section. |
Beta Was this translation helpful? Give feedback.
-
|
Feel free to open your own support discussion with your updated config and a full copy of the logs from startup. |
Beta Was this translation helpful? Give feedback.
-
|
It does not download model files automatically anymore. |
Beta Was this translation helpful? Give feedback.
-
|
If I change camera in review, timeline jumps to 1200hrs instead of the time which I am viewing. |
Beta Was this translation helpful? Give feedback.
-
|
Just came here to give a BIG THANK YOU! |
Beta Was this translation helpful? Give feedback.
-
|
Rpi4 (still) upgrade from 15.2 and Coral |
Beta Was this translation helpful? Give feedback.
-
|
My upgrade from 0.15.2, on TrueNAS, was painless. I forgot where the database file is stored in TN but I backed up my config and then simply told TN to upgrade. All is well; I need to start playing with number plate recognition and bird recognition soon (I tried one of the betas on a different platform - docker compose - so I know it isn't too hard). Frigate is great! |
Beta Was this translation helpful? Give feedback.
-
|
I am reporting regression related to 0.15.2 to 0.16.0 upgrade: I know you were stating in docs that HEVC/H265 is not supported but it was working fine for me with hardware acceleration making use of go2rtc via ffmpeg. But not anymore when upgraded to 0.16.0. Spent 2 days debugging. And here is the cause: On 0.15.2 hardware info: On 0.16.0 hardware info: So the version of libva changed from 2,10.0 to 2.12.0 but its missing critical function for my setup: How come it was compiled with lesser function support even tho updated? For now I reverted HA addon to 0.15.2 as this one works. I might provide logs and config snippet. But reason is obvious now as error logs clearly say function not implemented. |
Beta Was this translation helpful? Give feedback.
-
|
Now i suspect that its related to switch to bookworm as base for frigate. So https://wiki.debian.org/HardwareVideoAcceleration#VA-API So kindly ask to replace: And Or provide separate non-free image/addon |
Beta Was this translation helpful? Give feedback.
-
|
Ok it was addressed already https://github.com/blakeblackshear/frigate/pull/19590/files |
Beta Was this translation helpful? Give feedback.
-
|
Does anyone use Docker images and have updated from 0.15.x? Any issues? |
Beta Was this translation helpful? Give feedback.
-
|
Just updated from 0.15.2 (I use Docker) with 0 issue. Make sure to back up your config as instructed in the release notes though. |
Beta Was this translation helpful? Give feedback.
-
|
Just updated to 0.16.0 (Docker) without issue. Had to update scripts that relied on Go2RTC to check which cameras are online and offline but that was expected. I enabled face recognition and it seems to work. Is this expected behavior. |
Beta Was this translation helpful? Give feedback.
-
|
The names show in the debug view but they won't show in the snapshot |
Beta Was this translation helpful? Give feedback.
-
|
Thanks. It'd be nice if sublabels could be added to snapshots :-) |
Beta Was this translation helpful? Give feedback.
-
|
@jerome71, which script that relies on go2rtc are you mentioning? Not sure I'm following |
Beta Was this translation helpful? Give feedback.
-
They're talking about their own personal scripts |
Beta Was this translation helpful? Give feedback.
-
|
As @NickM-27 said, those are scripts outside of Frigate, which I made to make sure the cameras were working correctly. |
Beta Was this translation helpful? Give feedback.
-
|
Why do i get this when autotracking enabled on one of my cameras? 
I also get this when running test py script for camera capabilities for autotracking. YES - GetServiceCapabilities shows that the camera supports MoveStatus. |
Beta Was this translation helpful? Give feedback.
-
|
I have this onvif set for the camera: |
Beta Was this translation helpful? Give feedback.
-
|
Thanks. Do you already have a I've improved this in #19614 You can test it in this build: |
Beta Was this translation helpful? Give feedback.
-
|
As a side note, I'm not sure if thingino firmware correctly supports autotracking, even though it says it does. I do recall past issues from other users. |
Beta Was this translation helpful? Give feedback.
-
|
Hi, so i fixed some missing things, like zone not being created in the first place,.. Now i've turn on debug to see what is the issues and i see this:
This is how my onvif look now: |
Beta Was this translation helpful? Give feedback.
-
|
Scratch that. There seem to be an issue with thingino when you change the pass for onvif that this is not set correctly. I've reset the system, leave the pass as default and now it has connected. |
Beta Was this translation helpful? Give feedback.
-
|
I was training a new face and got a NaN% result when I refreshed the score. 
|
Beta Was this translation helpful? Give feedback.
-
|
After updating to 16 today I was getting error: Could not find tag for codec pcm_alaw in stream #1, codec not currently supported in container I had to change from To this as ffmpeg was crashing It's working fine now |
Beta Was this translation helpful? Give feedback.
-
|
Right, this is noted in the breaking changes in the release notes. |
Beta Was this translation helpful? Give feedback.
-
|
I can't get face recognition TY here is my config `mqtt: ov_0:type: openvinodevice: GPUov_1:type: openvinodevice: GPUdetectors: usb_camera:- "ffmpeg:device?video=/dev/video1&video_size=1280x720#video=mjpeg"#ffmpeg: hwaccel_args: preset-vaapi#path: '5.0' #Global Object Settings snapshots: #record: enabled: trueretain:days: 10record: cameras: drivewaydown: drivewayup: frontyard: frontlab: midroad: skyview: entrylab: garage: backyard: usb_camera:ffmpeg:inputs:# High Resolution Stream- path: rtsp://127.0.0.1:8554/usb_camerainput_args: preset-rtsp-restreamroles:- recordversion: 0.16-0 semantic_search: model_size: small |
Beta Was this translation helpful? Give feedback.
-
|
You should follow the debugging steps from the official documentation: https://docs.frigate.video/configuration/face_recognition/#how-do-i-debug-face-recognition-issues |
Beta Was this translation helpful? Give feedback.
-
|
Hello, I noticed earlier that the input fields have been moved out of the frame. Also, the time can be entered in pm, but is subsequently displayed in am. This is the export window. I'm using version 0.16. |
Beta Was this translation helpful? Give feedback.
-
|
Thanks, this is just because of the i18n changes in 0.16. I've put up a PR to fix it for 0.16.1. #19736 |
Beta Was this translation helpful? Give feedback.
-
|
I‘ve updated from 0.15 (flawlessly running) to 0.16 on my Raspi 5 and am now getting the following python / numpy errors. Does anyone have an idea on why this is triggered and how it can be fixed? frigate does start, but the errors look odd… |
Beta Was this translation helpful? Give feedback.
-
|
They are not errors, just warnings. Nothing to worry about. |
Beta Was this translation helpful? Give feedback.
-
|
Good morning, after updating my Frigate (Full Access) Beta Update 0.16.0 RC4 to the latest release of 0.16.0, the application stopped working and continues to crash in a loop. The problem seems to be in the detection of the TPU, in my case, Coral plugged into rPI. Reverting to RC4 restores the services. |
Beta Was this translation helpful? Give feedback.
-
|
RC4 and 0.16.0 are bit-for-bit identical. We didn't even run a new docker build, they are the same image just referenced by different tags. So it is impossible for the image to be making a difference. |
Beta Was this translation helpful? Give feedback.
-
|
I often find after a reboot of my Frigate machine, the first time docker compose starts frigate it doesn't detect the Coral. I have to stop and start the container for it to work. I think there might be something funny the Coral does with it's USD ID. It might appear to you that RC4 fixed it because you restarted the container. If you move back to 0.16.0 you'll probably find it "just works". |
Beta Was this translation helpful? Give feedback.
-
|
I never had any issues with my Coral. After updating to 0.16.0, I've tried rebooting, restarting containers, but nothing helped; I just restored to RC4. I've updated the HA OS to the latest versions, but still the same behaviour. |
Beta Was this translation helpful? Give feedback.
-
|
Are you running full access version of the add-on with protection mode disabled? As the docs indicate, this is required. Perhaps HA defaults to disabling protection mode for newly installed add-ons? |
Beta Was this translation helpful? Give feedback.
-
|
Hi! I was having the same loop crash issue with Frigate (Full Access) 0.16.1 and Coral while the Protection mode was enabled. However, when I disabled the protection mode, the add-on started up nicely. |
Beta Was this translation helpful? Give feedback.
-
|
i tried to upgrade my home assistant version to 0.16 from 0.15.2 and it didnt migrate the config at all, i tried to copy the config into a blank config but it refused to accept it, can i get some help on what is wrong with the existing config and why it would not work? happy to paste config here if that would help identify the issue? |
Beta Was this translation helpful? Give feedback.
-
|
nothing about breaking changes other than where the files have moved to, it didnt mention anything about your old config file will not work etc etc, hence me coming here to ask the specialists if there is something in my config file that is not allowed inn 0.16 |
Beta Was this translation helpful? Give feedback.
-
|
The breaking changes list everything in the config that no longer works. In order for us to help you we will need more information like logs, a screenshot, etc. |
Beta Was this translation helpful? Give feedback.
-
|
ive uploaded my config so you can take a look and see if there is anything in there that doesnt work in 0.16 |
Beta Was this translation helpful? Give feedback.
-
|
that might not be relevant, we need to see logs to know what is actually the problem (it could be the contents of the config, or it could be something else) |
Beta Was this translation helpful? Give feedback.
-
|
i will have to retry the upgrade again at some point then, will get another machine to test this out first as im not going through the system being down again and having to roll back to get everything back, but thanks for your insight |
Beta Was this translation helpful? Give feedback.
-
|
Technically a |
Beta Was this translation helpful? Give feedback.
-
|
we've already reverted that change for 0.16.1 |
Beta Was this translation helpful? Give feedback.
-
|
Huh, still happens to me on latest master commit, but digging deeper seems I have some caching going on somewhere as it occurs when I go via my Cloudflare tunnel but not when bypassing it locally. Weird as most of the files in Devtools look to have hashes in the filename to prevent caching. Will have to have a dig. |
Beta Was this translation helpful? Give feedback.
-
|
0.16.0 unraid In 0.16.0 it gets to 97% complete and just craps out
-- |
Beta Was this translation helpful? Give feedback.
-
|
the error has nothing to do with tls, looks like autotracking calibration failed, this might be something that is already fixed for 0.16.1 |
Beta Was this translation helpful? Give feedback.
-
|
This particular crash has been fixed for 0.16.1. #19776 |
Beta Was this translation helpful? Give feedback.
and others
Uh oh!
There was an error while loading. Please reload this page.
-
Images
ghcr.io/blakeblackshear/frigate:0.16.0ghcr.io/blakeblackshear/frigate:0.16.0-standard-arm64ghcr.io/blakeblackshear/frigate:0.16.0-tensorrtghcr.io/blakeblackshear/frigate:0.16.0-rkghcr.io/blakeblackshear/frigate:0.16.0-rocmghcr.io/blakeblackshear/frigate:0.16.0-tensorrt-jp6Changes 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:
frigate.dbfileThe 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-copyis currently used it likely will need to be changed topreset-record-generic-audio-aacto continue to support audio in recordings.Object detection is now disabled by default. A config migrator will update your config globally with
enabled: truefordetect:. If you use Frigate with a read-only config, you may need to edit your own config to enable object detection manually.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 theonnxdetector should be used instead. This change should only require changing thetype: rocmtotype: onnxindetectorsAn additional parameter has been added to
movement_weightsfor autotracking users. A config migrator will add the new value so that Frigate starts, but if this fails or you are usingrelativezooming with autotracking, you should removemovement_weightsfrom your config and recalibrate.Proxy header mapping for user roles is now required or setting the
default_roletoadminis required to achieve the same functionality as previous versions. This version implements a Viewer role, which is now the default for authenticated users without aroleheader map defined in the config. If you are using a proxy, you must includeadminin your mapped role header in order for admin users to retain their elevated privileges. See the documentation.The
strftime_fmtconfig 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_insecureonvifconfig 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 settingtls_insecure: falsefixed 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
/configdirectory. They will now be found in the/addon_configsdirectory, 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.ymlfrom the/addons_configback to/config/frigate.ymlbefore 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_configsdirectory 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
facenatively) 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_platenatively) 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
RockChip (RKNN)
RockChip has had the following improvements:
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_offservices 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.
Camera groups now include per-camera settings to further customize the live streaming behavior of that camera in that camera group.
Other noteworthy live streaming improvements:
Other UI Changes
There are many other notable improvements to the Frigate UI:
Ctrl+ scroll wheel on desktop.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
Zones and Object Area
min_areaandmax_areaas 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.Semantic Search
Bird Classification
ONVIF and Autotracking
personobject.Other notable changes
/recordings/summary, to return true/false for each day that recordings are available.This discussion was created from the release 0.16.0 Release.
Beta Was this translation helpful? Give feedback.
All reactions