Frigate 0.15 FAQ

[hawkeye217]

This FAQ is maintained by the Frigate developers to help answer some of the common questions with Frigate 0.15. If you have a question that's not answered here, be sure to read the release notes, the official documentation, and search the recent discussions first. If you still need help, open a support discussion.

Updated February 11, 2025

Upgrade issues

1. My cameras are not working and I am seeing many ffmpeg errors in my logs. But didn't change anything from my 0.14 config. What is the problem?
   As the breaking changes in the release notes indicate, ffmpeg was updated and you likely need to use preset-intel-qsv-h264 or preset-intel-qsv-h265 instead of preset-vaapi for your cameras' hwaccel_args now. Some older Intel CPUs may still need preset-vaapi and/or ffmpeg 5.0 so you should experiment to see what works for your particular setup. See the release notes for more details.

2. I installed Frigate using the tteck script for Proxmox LXC, but I am seeing sqlite3.OperationalError: /usr/local/lib/vec0.so: cannot open shared object file: No such file or directory in my logs. Is this a bug?
   No, this is not a bug, and Proxmox is not an officially supported install method. The tteck script is essentially a port of Frigate's Dockerfile, and every update to Frigate will require extensive changes to that script. Someone will have to fork the script and modify it with all the changes for 0.15 or set the version to 0.14.

3. I am trying to install and configure Hailo-8L, but the driver version (4.20.0) is different than the library version (4.19.0). What can I do?
   See this discussion.

4. I'm seeing the error OSError: [Errno 24] Too many open files and the container won't start.

   This is a result of the SHM refactor for 0.15. If you have a fairly large number of cameras, you'll need to increase your file limits in your Docker compose file:

   services:
     frigate:
       ...
       ulimits:
         nofile:
           soft: 65535
           hard: 65535
   

   Alternatively, you can lower the number of frames in SHM per camera with an environment variable SHM_MAX_FRAMES. The default value is 50. Depending on your system speed, you may want to increase the max files with Docker rather than decrease the max frames with the env var.

   You can get a shell in the Frigate container and run

   lsof | grep shm | wc -l

   to get an idea on how many open files you have.

Usage

1. How do I submit images to Frigate+? I have set up my API key but I don't see a Frigate+ tab anymore like I did in 0.14.
   This was detailed in the release notes. The Frigate+ view has been consolidated with 0.15's new Explore view. From the More Filters button in Explore, choose Yes for "Has a snapshot?" and No for "Submitted to Frigate+?", and then press Apply at the bottom of the pane. Then click on one of the thumbnails to bring up the Tracked Object Details pane, and press the Snapshot tab where you'll see the familiar Frigate+ buttons. You can then use the arrow keys on your keyboard to quickly navigate back and forth between the tracked objects in the view, and the Snapshot tab will remain active for each object. Closing the Tracked Object Details pane will cause a momentary blue highlight to appear around the last tracked object you viewed. Additionally, if you have Semantic Search enabled, you can save a search with these filters already enabled to quickly return to it later.

2. Can I use Deepseek, Local AI, or... (insert AI provider name here) for Generative AI?
   If your AI provides an OpenAI-compatible endpoint, you can use it with the openai provider by setting the environment variable OPENAI_BASE_URL to your endpoint url. See the documentation.

3. I am getting this 400 error every minute in my nginx log. Is this a problem?
   127.0.0.1 - - [01/Jan/2025:11:24:17 +0000] "" 400 0 "-" "-" "-"
   This is not an error and is the result of a routine call every minute to the nginx server, checking for a valid certificate. You can safely ignore it. Disabling TLS will stop this from showing in the nginx log.

4. I am seeing errors like [error] 170#170: 2 connect() failed (111: Connection refused) while connecting to upstream, client: 127.0.0.1, server: , request: "GET /api/version HTTP/1.1", subrequest: "/auth", upstream: "http://127.0.0.1:5001/auth", host: "127.0.0.1:5000" in my log, is this a problem?
   No, this is not a problem or concern. These log messages are normal and expected when Frigate is starting up and you have the UI open on your browser.

5. How can I view snapshots with bounding boxes and debug object tracking?
   In addition to the Debug view in Settings for live objects, you can see historical data from object tracking in two main ways:

   • From Review: use the new Review Item Details pane in the UI. Click/tap on the gray "chip" in the upper left corner of a review item. Thumbnails and/or snapshots will be shown, each having their own set of icons (shown on hover on desktop devices) for downloading, submitting to Frigate+, viewing the object lifecycle, and finding similar objects (if Semantic Search is enabled).
   • From Explore: filter and/or search for tracked objects, and then click/tap the thumbnail. The Tracked Object Details pane will show several tabs with various details.

6. Are there any mouse/touch/keyboard shortcuts in the UI?
   Yes, see this tip post.

7. How can I set the format of the time (12 hour/24 hour) in the UI?
   Use the config file option:

   ui:
     time_format: 24hour
   

8. I'm having trouble using the mask/zone editor, I can't click points.
   This is due to Brave Browser's underlying extreme anti-fingerprinting code. To use Brave Browser with Frigate, you should disable Brave Shields.

9. It doesn't seem like my cameras are streaming on the Live dashboard. Why?
   On the Live dashboard, your cameras use "smart streaming". Images will 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. See the Live view documentation.

10. I see a strange diagonal line on my live view, but my recordings look fine. How can I fix it?
    This is caused by incorrect dimensions set in your detect width or height (or incorrectly auto-detected) that don’t match your camera, causing the jsmpeg player's rendering engine to display a slightly distorted image. See this discussion, this discussion and this discussion. You should set your detect width and height to a standard aspect ratio by changing one or both dimensions (example: 640x352 becomes 640x360, and 800x443 becomes 800x450, a standard 16:9 aspect ratio). If you have not yet configured go2rtc, we highly recommend using go2rtc for live views as it provides a superior experience with much more fluent and clear video. Using go2rtc may make the artifacts appear less often, so you still should adjust your detect dimensions. Some cameras (especially vertically oriented ones) may continue to exhibit this issue even after making the suggested changes, so Frigate 0.16 will have additional features to rectify this issue.

11. I have set up go2rtc but my live view is not loading. Why?
    This is often caused by using a codec on your camera that your browser doesn't support - either a video or audio codec. For the most compatibility, you should change your camera's firmware to output your stream as H.264 video and AAC audio, or transcode the stream using go2rtc. See the official documentation for camera settings recommendations. Browser support for various codecs varies greatly due to copyrights and patents. See this chart in go2rtc's readme.