Frigate 0.18 beta FAQ

[hawkeye217]

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

If you still need help, open a beta support discussion.

Some questions may also be answered in the older version, Frigate 0.17 FAQ, so be sure to read those as well.

Updated July 12, 2026

Beta documentation

1. Where can I find the documentation for the beta release?
   The most updated documentation for beta releases can always be found at https://docs-dev.frigate.video. The main docs site (docs.frigate.video) is for the stable (0.17) release.

2. The AI on the docs site answers some of my questions incorrectly or gives outdated information. Why?
   The docs AI is not trained on the beta documentation. Once 0.18 becomes stable, the AI will be re-trained.

3. The links to the documentation in the UI do not work.
   The links point to the stable documentation site by design, which will be updated when 0.18 moves out of beta. You can simply add a -dev to the hostname and the links will take you to the correct documentation page. For example, if you are trying to access docs.frigate.video/configuration/live/, just add -dev, eg: docs-dev.frigate.video/configuration/live/.

Upgrade issues

1. I just upgraded my Home Assistant App and now my Coral TPU is not being detected.
   The app's protection mode switch may be re-enabled by Home Assistant after upgrading. You need to disable protection mode for the app or use the standard app (not "Frigate Full Access").

2. The heatmap is not working in Motion Search. Is this a bug?
   No. Motion data is a new feature and is only saved for new recordings since upgrading to the beta. Wait a while and try again later.

3. I've set my preferred language from the Settings menu, but there are areas of the UI that are not translated. Is this a bug?
   No. Frigate provides English by default, all other translations are user-contributed. If your language is missing or specific strings are not translated from English, you can help translate using Weblate. Contributed translations will be a part of future betas and the final release.

4. My Intel GPU stats are not working, and the logs indicate a problem with my iGPU.
   As the breaking changes in the release notes indicate, the measurement method for Intel GPU stats has changed. The error message will indicate what is required, though generally if measurement is failing, you'll want to make sure your Linux kernel version is up to date on your host. A kernel version of 6.5 or higher is required to support iGPU stats. On Debian bookworm, you can run a few simple commands. You will need to adapt these for your particular Linux distribution or installation method.

   uname -a
   echo 'deb http://deb.debian.org/debian bookworm-backports main' | sudo tee /etc/apt/sources.list.d/backports.list
   sudo apt update
   sudo apt install -t bookworm-backports linux-image-amd64
   sudo reboot
   

5. I just upgraded and my CPU usage with my Intel processor is much higher. Why?
   This was covered in the breaking changes in the release notes. If you are running Frigate on an Intel CPU and you are transcoding streams in go2rtc, you need to make a small adjustment to your go2rtc config. Documentation