0.15.0 Release

[blakeblackshear]

Images

• ghcr.io/blakeblackshear/frigate:0.15.0
• ghcr.io/blakeblackshear/frigate:0.15.0-standard-arm64
• ghcr.io/blakeblackshear/frigate:0.15.0-tensorrt
• ghcr.io/blakeblackshear/frigate:0.15.0-tensorrt-jp4
• ghcr.io/blakeblackshear/frigate:0.15.0-tensorrt-jp5
• ghcr.io/blakeblackshear/frigate:0.15.0-rk
• ghcr.io/blakeblackshear/frigate:0.15.0-rocm
• ghcr.io/blakeblackshear/frigate:0.15.0-h8l

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.

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 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: v0.14.1...v0.15.0

---

This discussion was created from the release 0.15.0 Release.

[tomerh2001]

When will 0.15 be available in the stable version? Cause stable is still 0.14.1

[NickM-27]

it already is, you likely just need to have docker pull down the latest and rebuild the container

[sinamics]

Thank you devs, for your outstanding work!
⭐ ⭐ ⭐ ⭐ ⭐

[yayitazale]

Thanks all for your work!!

[detroitgoose]

Devs, this update is incredible. Semantic search alone is blowing my mind. Loving new explore UI... so much info!

Thank you!

[vw-kombi]

OMG - I was messing (struggling) with a few AI blueprints for HomeAssistant, then this popped up and just worked. How cool.
Not sure why notifications have to have an https connection to frigate though before they can be enabled - I use the HA addon and dont have that. Id like to create those so my browser can be informed - way cool.

[hawkeye217]

Not sure why notifications have to have an https connection to frigate though before they can be enabled

A secure context (https) is actually a browser-enforced requirement for the notifications API.

[ammgws]

The dev docker-compose file has this (introduced in #14865):

    environment:
      YOLO_MODELS: ""

Do we need to consider this when upgrading from v0.14?

[hawkeye217]

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.

[NickM-27]

To be clear this isn't required if yolonas is being used for object detection with tensorrt

[ammgws]

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:

https://github.com/blakeblackshear/frigate/blob/v0.15.0/docs/docs/frigate/installation.md#calculating-required-shm-size

[hawkeye217]

These docs are correct, they were updated in this PR.

[dmitriykhait]

i still cant export timelapse videos

2025-02-08 19:04:54.289635822  [2025-02-08 19:04:54] frigate.record.export          ERROR   : Failed to export recordings for command /usr/lib/ffmpeg/7.0/bin/ffmpeg -hide_banner -an -y -protocol_whitelist pipe,file,http,tcp -i http://127.0.0.1:5000/vod/garage-wide/start/1739044800/end/1739046000/index.m3u8 -c:v hevc_qsv -profile:v main -level:v 4.1 -async_depth:v 1 -vf setpts=PTS/60 -r 25 -movflags +faststart /media/frigate/exports/garage-wide_x58cuq.mp4
2025-02-08 19:04:54.289672258  [2025-02-08 19:04:54] frigate.record.export          ERROR   : [hls @ 0x5bf41c87ae40] Skip ('#EXT-X-ALLOW-CACHE:YES')
2025-02-08 19:04:54.289674289  [hls @ 0x5bf41c87ae40] Skip ('#EXT-X-VERSION:6')
2025-02-08 19:04:54.289676094  [hls @ 0x5bf41c87ae40] Opening 'http://127.0.0.1:5000/vod/garage-wide/start/1739044800/end/1739046000/init-v1-a1.mp4' for reading
2025-02-08 19:04:54.289677955  [hls @ 0x5bf41c87ae40] Opening 'http://127.0.0.1:5000/vod/garage-wide/start/1739044800/end/1739046000/seg-1-v1-a1.m4s' for reading
2025-02-08 19:04:54.289679973  [hls @ 0x5bf41c87ae40] Opening 'http://127.0.0.1:5000/vod/garage-wide/start/1739044800/end/1739046000/seg-2-v1-a1.m4s' for reading
2025-02-08 19:04:54.289700534  Input #0, hls, from 'http://127.0.0.1:5000/vod/garage-wide/start/1739044800/end/1739046000/index.m3u8':
2025-02-08 19:04:54.289702145    Duration: 00:00:39.96, start: 0.000000, bitrate: N/A
2025-02-08 19:04:54.289703219    Program 0
2025-02-08 19:04:54.289720063      Metadata:
2025-02-08 19:04:54.289721370        variant_bitrate : 0
2025-02-08 19:04:54.289722752    Stream #0:0(eng): Video: hevc (Main) (hev1 / 0x31766568), yuv420p(tv), 4608x1728, 946 kb/s, 90k tbr, 90k tbn (default)
2025-02-08 19:04:54.289734377        Metadata:
2025-02-08 19:04:54.289735706          variant_bitrate : 0
2025-02-08 19:04:54.289736925          handler_name    : VideoHandler
2025-02-08 19:04:54.289738248          vendor_id       : [0][0][0][0]
2025-02-08 19:04:54.289739393          major_brand     : isom
2025-02-08 19:04:54.289740500          minor_version   : 1
2025-02-08 19:04:54.289741765          compatible_brands: isomavc1
2025-02-08 19:04:54.289743369    Stream #0:1(eng): Audio: aac (LC) (mp4a / 0x6134706D), 16000 Hz, mono, fltp, 25 kb/s (default)
2025-02-08 19:04:54.289744462        Metadata:
2025-02-08 19:04:54.289756493          variant_bitrate : 0
2025-02-08 19:04:54.289757903          handler_name    : SoundHandler
2025-02-08 19:04:54.289759000          vendor_id       : [0][0][0][0]
2025-02-08 19:04:54.289759963  Stream mapping:
2025-02-08 19:04:54.289761351    Stream #0:0 -> #0:0 (hevc (native) -> hevc (hevc_qsv))
2025-02-08 19:04:54.289762495  Press [q] to stop, [?] for help
2025-02-08 19:04:54.289763562  libva info: VA-API version 1.22.0
2025-02-08 19:04:54.289764760  libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so
2025-02-08 19:04:54.289778824  libva info: Found init function __vaDriverInit_1_22
2025-02-08 19:04:54.289780135  libva info: va_openDriver() returns 0
2025-02-08 19:04:54.289782104  [hevc_qsv @ 0x5bf41c8c5140] Using the constant quantization parameter (CQP) by default. Please use the global_quality option and other options for a quality-based mode or the b option and other options for a bitrate-based mode if the default is not the desired choice.
2025-02-08 19:04:54.289783600  [hevc_qsv @ 0x5bf41c8c5140] Low power mode is unsupported
2025-02-08 19:04:54.289785461  [hevc_qsv @ 0x5bf41c8c5140] some encoding parameters are not supported by the QSV runtime. Please double check the input parameters.
2025-02-08 19:04:54.289787270  [vost#0:0/hevc_qsv @ 0x5bf41c8c4dc0] Error while opening encoder - maybe incorrect parameters such as bit_rate, rate, width or height.
2025-02-08 19:04:54.289788997  [vf#0:0 @ 0x5bf41c8c2540] Error sending frames to consumers: Function not implemented
2025-02-08 19:04:54.289790681  [vf#0:0 @ 0x5bf41c8c2540] Task finished with error code: -38 (Function not implemented)
2025-02-08 19:04:54.289792417  [vf#0:0 @ 0x5bf41c8c2540] Terminating thread with return code -38 (Function not implemented)
2025-02-08 19:04:54.289793759  [vost#0:0/hevc_qsv @ 0x5bf41c8c4dc0] Could not open encoder before EOF
2025-02-08 19:04:54.289812516  [vost#0:0/hevc_qsv @ 0x5bf41c8c4dc0] Task finished with error code: -22 (Invalid argument)
2025-02-08 19:04:54.289814069  [vost#0:0/hevc_qsv @ 0x5bf41c8c4dc0] Terminating thread with return code -22 (Invalid argument)
2025-02-08 19:04:54.289815632  [out#0/mp4 @ 0x5bf41c8e9280] Nothing was written into output file, because at least one of its streams received no packets.
2025-02-08 19:04:54.289816974  frame=    0 fps=0.0 q=0.0 Lsize=       0KiB time=N/A bitrate=N/A speed=N/A
2025-02-08 19:04:54.289818195  Conversion failed!
2025-02-08 19:04:54.289819213

[devanteweary]

Guess I'm one of the ones the update broke.

Just keep getting this in the logs over and over, among other things.
I tried deleting the DB but leaving the config file.

Here's my config: config file

Logs

2025-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)
2025-02-08 21:35:19.313206748 [2025-02-08 21:35:19] ffmpeg.Back_Yard.detect ERROR : [out#1/rawvideo @ 0x56086fbe65c0] Nothing was written into output file, because at least one of its streams received no packets.
2025-02-08 21:35:19.335481125 [2025-02-08 21:35:19] watchdog.Living_Room ERROR : Ffmpeg process crashed unexpectedly for Living_Room.
2025-02-08 21:35:19.335500781 [2025-02-08 21:35:19] watchdog.Living_Room ERROR : The following ffmpeg logs include the last 100 lines prior to exit.
2025-02-08 21:35:19.335525620 [2025-02-08 21:35:19] ffmpeg.Living_Room.detect ERROR : libva info: VA-API version 1.22.0
2025-02-08 21:35:19.335561241 [2025-02-08 21:35:19] ffmpeg.Living_Room.detect ERROR : libva info: User environment variable requested driver 'iHD'
2025-02-08 21:35:19.335770165 [2025-02-08 21:35:19] ffmpeg.Living_Room.detect ERROR : libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so
2025-02-08 21:35:19.335773314 [2025-02-08 21:35:19] ffmpeg.Living_Room.detect ERROR : libva info: Found init function __vaDriverInit_1_22
2025-02-08 21:35:19.335774547 [2025-02-08 21:35:19] ffmpeg.Living_Room.detect ERROR : libva info: va_openDriver() returns 0
2025-02-08 21:35:19.336578667 [2025-02-08 21:35:19] ffmpeg.Living_Room.detect ERROR : libva info: VA-API version 1.22.0
2025-02-08 21:35:19.336581645 [2025-02-08 21:35:19] ffmpeg.Living_Room.detect ERROR : libva info: User environment variable requested driver 'iHD'
2025-02-08 21:35:19.336582984 [2025-02-08 21:35:19] ffmpeg.Living_Room.detect ERROR : libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so
2025-02-08 21:35:19.336584049 [2025-02-08 21:35:19] ffmpeg.Living_Room.detect ERROR : libva info: Found init function __vaDriverInit_1_22
2025-02-08 21:35:19.336585040 [2025-02-08 21:35:19] ffmpeg.Living_Room.detect ERROR : libva info: va_openDriver() returns 0
2025-02-08 21:35:19.336586406 [2025-02-08 21:35:19] ffmpeg.Living_Room.detect ERROR : [vist#0:0/h264 @ 0x5604d2f3c740] WARNING: defaulting hwaccel_output_format to qsv for compatibility with old commandlines. This behaviour is DEPRECATED and will be removed in the future. Please explicitly set "-hwaccel_output_format qsv".
2025-02-08 21:35:19.336587850 [2025-02-08 21:35:19] ffmpeg.Living_Room.detect ERROR : [segment @ 0x5604d2f34cc0] Timestamps are unset in a packet for stream 0. This is deprecated and will stop working in the future. Fix your code to set the timestamps properly
2025-02-08 21:35:19.336589044 [2025-02-08 21:35:19] ffmpeg.Living_Room.detect ERROR : [vost#0:0/copy @ 0x5604d2f11240] Non-monotonic DTS; previous: 1039, current: 1039; changing to 1040. This may result in incorrect timestamps in the output file.
2025-02-08 21:35:19.336590287 [2025-02-08 21:35:19] ffmpeg.Living_Room.detect ERROR : [vost#0:0/copy @ 0x5604d2f11240] Non-monotonic DTS; previous: 1040, current: 1039; changing to 1041. This may result in incorrect timestamps in the output file.
2025-02-08 21:35:19.336591552 [2025-02-08 21:35:19] ffmpeg.Living_Room.detect ERROR : [vost#0:0/copy @ 0x5604d2f11240] Non-monotonic DTS; previous: 1541, current: 1541; changing to 1542. This may result in incorrect timestamps in the output file.
2025-02-08 21:35:19.336592585 [2025-02-08 21:35:19] ffmpeg.Living_Room.detect ERROR : [vost#0:0/copy @ 0x5604d2f11240] Non-monotonic DTS; previous: 1863, current: 1863; changing to 1864. This may result in incorrect timestamps in the output file.
2025-02-08 21:35:19.336593902 [2025-02-08 21:35:19] ffmpeg.Living_Room.detect ERROR : Impossible to convert between the formats supported by the filter 'Parsed_fps_0' and the filter 'auto_scale_0'
2025-02-08 21:35:19.336595026 [2025-02-08 21:35:19] ffmpeg.Living_Room.detect ERROR : [vf#1:0 @ 0x5604d2fadb00] Error reinitializing filters!
2025-02-08 21:35:19.336596136 [2025-02-08 21:35:19] ffmpeg.Living_Room.detect ERROR : [vf#1:0 @ 0x5604d2fadb00] Task finished with error code: -38 (Function not implemented)
2025-02-08 21:35:19.336597393 [2025-02-08 21:35:19] ffmpeg.Living_Room.detect ERROR : [vf#1:0 @ 0x5604d2fadb00] Terminating thread with return code -38 (Function not implemented)
2025-02-08 21:35:19.336598673 [2025-02-08 21:35:19] ffmpeg.Living_Room.detect ERROR : [vost#1:0/rawvideo @ 0x5604d3002d40] Could not open encoder before EOF
2025-02-08 21:35:19.336600001 [2025-02-08 21:35:19] ffmpeg.Living_Room.detect ERROR : [vost#1:0/rawvideo @ 0x5604d3002d40] Task finished with error code: -22 (Invalid argument)
2025-02-08 21:35:19.336601090 [2025-02-08 21:35:19] ffmpeg.Living_Room.detect ERROR : [vost#1:0/rawvideo @ 0x5604d3002d40] Terminating thread with return code -22 (Invalid argument)
2025-02-08 21:35:19.336602284 [2025-02-08 21:35:19] ffmpeg.Living_Room.detect ERROR : [vost#0:0/copy @ 0x5604d2f11240] Non-monotonic DTS; previous: 2823, current: 2823; changing to 2824. This may result in incorrect timestamps in the output file.
2025-02-08 21:35:19.336603604 [2025-02-08 21:35:19] ffmpeg.Living_Room.detect ERROR : [vost#0:0/copy @ 0x5604d2f11240] Non-monotonic DTS; previous: 3542, current: 3542; changing to 3543. This may result in incorrect timestamps in the output file.
2025-02-08 21:35:19.336605134 [2025-02-08 21:35:19] ffmpeg.Living_Room.detect ERROR : [out#1/rawvideo @ 0x5604d2eef700] Nothing was written into output file, because at least one of its streams received no packets.
2025-02-08 21:35:19.365665060 [2025-02-08 21:35:19] watchdog.Garage ERROR : Ffmpeg process crashed unexpectedly for Garage.
2025-02-08 21:35:19.365669577 [2025-02-08 21:35:19] watchdog.Garage ERROR : The following ffmpeg logs include the last 100 lines prior to exit.
2025-02-08 21:35:19.365671195 [2025-02-08 21:35:19] ffmpeg.Garage.detect ERROR : libva info: VA-API version 1.22.0
2025-02-08 21:35:19.365672607 [2025-02-08 21:35:19] ffmpeg.Garage.detect ERROR : libva info: User environment variable requested driver 'iHD'
2025-02-08 21:35:19.365673837 [2025-02-08 21:35:19] ffmpeg.Garage.detect ERROR : libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so
2025-02-08 21:35:19.365675372 [2025-02-08 21:35:19] ffmpeg.Garage.detect ERROR : libva info: Found init function __vaDriverInit_1_22
2025-02-08 21:35:19.365676487 [2025-02-08 21:35:19] ffmpeg.Garage.detect ERROR : libva info: va_openDriver() returns 0
2025-02-08 21:35:19.365677650 [2025-02-08 21:35:19] ffmpeg.Garage.detect ERROR : libva info: VA-API version 1.22.0
2025-02-08 21:35:19.365678944 [2025-02-08 21:35:19] ffmpeg.Garage.detect ERROR : libva info: User environment variable requested driver 'iHD'
2025-02-08 21:35:19.365680101 [2025-02-08 21:35:19] ffmpeg.Garage.detect ERROR : libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so
2025-02-08 21:35:19.365681325 [2025-02-08 21:35:19] ffmpeg.Garage.detect ERROR : libva info: Found init function __vaDriverInit_1_22
2025-02-08 21:35:19.365697566 [2025-02-08 21:35:19] ffmpeg.Garage.detect ERROR : libva info: va_openDriver() returns 0
2025-02-08 21:35:19.365699430 [2025-02-08 21:35:19] ffmpeg.Garage.detect ERROR : [vist#0:0/h264 @ 0x55b58f842540] WARNING: defaulting hwaccel_output_format to qsv for compatibility with old commandlines. This behaviour is DEPRECATED and will be removed in the future. Please explicitly set "-hwaccel_output_format qsv".
2025-02-08 21:35:19.365708179 [2025-02-08 21:35:19] ffmpeg.Garage.detect ERROR : [segment @ 0x55b58f87efc0] Timestamps are unset in a packet for stream 0. This is deprecated and will stop working in the future. Fix your code to set the timestamps properly
2025-02-08 21:35:19.365830769 [2025-02-08 21:35:19] ffmpeg.Garage.detect ERROR : Impossible to convert between the formats supported by the filter 'Parsed_fps_0' and the filter 'auto_scale_0'
2025-02-08 21:35:19.365832707 [2025-02-08 21:35:19] ffmpeg.Garage.detect ERROR : [vf#1:0 @ 0x55b58f877600] Error reinitializing filters!
2025-02-08 21:35:19.365833938 [2025-02-08 21:35:19] ffmpeg.Garage.detect ERROR : [vf#1:0 @ 0x55b58f877600] Task finished with error code: -38 (Function not implemented)
2025-02-08 21:35:19.365835136 [2025-02-08 21:35:19] ffmpeg.Garage.detect ERROR : [vf#1:0 @ 0x55b58f877600] Terminating thread with return code -38 (Function not implemented)
2025-02-08 21:35:19.365836008 [2025-02-08 21:35:19] ffmpeg.Garage.detect ERROR : [vost#1:0/rawvideo @ 0x55b58f80a640] Could not open encoder before EOF
2025-02-08 21:35:19.365836896 [2025-02-08 21:35:19] ffmpeg.Garage.detect ERROR : [vost#1:0/rawvideo @ 0x55b58f80a640] Task finished with error code: -22 (Invalid argument)
2025-02-08 21:35:19.365837904 [2025-02-08 21:35:19] ffmpeg.Garage.detect ERROR : [vost#1:0/rawvideo @ 0x55b58f80a640] Terminating thread with return code -22 (Invalid argument)
2025-02-08 21:35:19.365839035 [2025-02-08 21:35:19] ffmpeg.Garage.detect ERROR : [out#1/rawvideo @ 0x55b58f87b600] Nothing was written into output file, because at least one of its streams received no packets.
2025-02-08 21:35:20.264288383 [2025-02-08 21:35:20] frigate.video ERROR : Living_Room: Unable to read frames from ffmpeg process.
2025-02-08 21:35:20.264427031 [2025-02-08 21:35:20] frigate.video ERROR : Living_Room: ffmpeg process is not running. exiting capture thread...
2025-02-08 21:35:20.951516662 [2025-02-08 21:35:20] frigate.video ERROR : Garage: Unable to read frames from ffmpeg process.
2025-02-08 21:35:20.951519376 [2025-02-08 21:35:20] frigate.video ERROR : Garage: ffmpeg process is not running. exiting capture thread...
2025-02-08 21:35:21.172014526 [2025-02-08 21:35:21] frigate.video ERROR : Back_Yard: Unable to read frames from ffmpeg process.
2025-02-08 21:35:21.172042514 [2025-02-08 21:35:21] frigate.video ERROR : Back_Yard: ffmpeg process is not running. exiting capture thread...
2025-02-08 21:35:21.250542872 [2025-02-08 21:35:21] frigate.video ERROR : Front_Yard: Unable to read frames from ffmpeg process.
2025-02-08 21:35:21.250607596 [2025-02-08 21:35:21] frigate.video ERROR : Front_Yard: ffmpeg process is not running. exiting capture thread...

[NickM-27]

You should create a support discussion

[devanteweary]

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
to: preset-intel-qsv-h264

and now it seems to be working. :P'
Imagine what a little reading can do!

[nickspacemonkey]

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?

[hawkeye217]

You should open a support discussion with your config and logs.

[NoOneReally2021]

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?

[NickM-27]

Is it a secure connection? If the browser doesn't say it's secure then it won't work

[NoOneReally2021]

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.
Do I actually need an ssl cert or is there a workaround?

[NickM-27]

I'm assuming it's required for Safari to mark the connection secure, which is what the notification API being available is based on

[NoOneReally2021]

Ok thanks, HA for now

[Marcoluca56]

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

[hawkeye217]

Many users have found it easier, actually. See the FAQ, Usage question 1.

[NickM-27]

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+

[dansharpy]

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-

1. I've got a Nvidia GTX750ti passed into the container but when using the large model for Semantic Search I get ONNXRuntimeError: CUDA error cudaErrorNoKernelImageForDevice:no kernel image is available for execution on the device in the logs. Is the 750ti too old for the Jina AI model? The GPU is definitely passed into the container ok as it's being used for inference. I've got the 550.120 drivers installed on the host if that makes a difference. If I switch to the small model it runs on CPU fine.
2. I also get very random descriptions when using Ollama (which is using an RTX 2060 super on the same host) for the Generative AI, but the descriptions are fine if I use the regenerate button in the UI? This is an example of one of the auto generated descriptions- The tree. Bunch The ben These car The street in the park, Th How a tree. Cars. A building. A number, What: Another to house. Par

[NickM-27]

1. Need to see what Hardware Info says in the system metrics page
2. it is possible that using multiple images is causing ollama to be confused. You can try setting genai to use a snapshot instead of thumbnails

[dansharpy]

Thanks for the quick response!

1. Here is the output from Hardware Info

Nvidia SMI Output
Name: NVIDIA GeForce GTX 750 Ti

Driver: 550.120

Cuda Compute Capability: 5

VBios Info: 82.07.32.00.20

2. Thanks for that, I was looking for a way to get genai to use a snapshot but completely missed it! I also missed the option to set required_zones as well which I wanted to do. As a suggestion, maybe those options would be better suited in the Configuration section rather than under Custom Prompts?

[NikoGrub]

My camera stream is not working anymore since this update.
Lots of ffmpeg issues in log.

ffmpeg:rtsp://admin:[email protected]:554/Streaming/Channels/101#video=copy

I had to add "path: '5.0'" in ffmpeg section.
Now it works again.

Is there any possibility to use version 7 in my case?
Or what could be the reason for this issue?

[NickM-27]

there's no way to say without seeing the config and logs, you should create a support discussion

[jjth]

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.

[kirsch33]

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.

[NickM-27]

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

[vw-kombi]

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.

[jvrobert]

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:
2025-02-09 22:21:33.051646305 [2025-02-09 22:21:33] frigate.util.services ERROR : Unable to poll vainfo: b"error: XDG_RUNTIME_DIR is invalid or not set in the environment.\nerror: can't connect to X server!\nlibva info: VA-API version 1.22.0\nlibva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/nvidia_drv_video.so\nlibva info: va_openDriver() returns -1\nvaInitialize failed with error code -1 (unknown libva error),exit\n"

[NickM-27]

what hwaccel do you have enabled?

[vw-kombi]

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.

[richardfoley]

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!