Change the default log level for troubleshooting purposes.
# Optional: default log level (default: shown below)
# Optional: module by module log level configuration
Available log levels are:
Examples of available modules are:
ffmpeg.<camera_name>.<sorted_roles>NOTE: All FFmpeg logs are sent as
This section can be used to set environment variables for those unable to modify the environment of the container (ie. within HassOS)
Event and recording information is managed in a sqlite database at
/config/frigate.db. If that database is deleted, recordings will be orphaned and will need to be cleaned up manually. They also won't show up in the Media Browser within Home Assistant.
If you are storing your database on a network share (SMB, NFS, etc), you may get a
database is locked error message on startup. You can customize the location of the database in the config if necessary.
This may need to be in a custom location if network storage is used for the media folder.
If using a custom model, the width and height will need to be specified.
Custom models may also require different input tensor formats. The colorspace conversion supports RGB, BGR, or YUV frames to be sent to the object detector. The input tensor shape parameter is an enumeration to match what specified by the model.
|Available Input Tensor Shapes
# Optional: model config
The labelmap can be customized to your needs. A common reason to do this is to combine multiple object types that are easily confused when you don't need to be as granular such as car/truck. By default, truck is renamed to car because they are often confused. You cannot add new object types, but you can change the names of existing objects in the model.
Note that if you rename objects in the labelmap, you will also need to update your
objects -> track list as well.
Some labels have special handling and modifications can disable functionality.
person objects are associated with
car objects are associated with
Custom ffmpeg build
Included with Frigate is a build of ffmpeg that works for the vast majority of users. However, there exists some hardware setups which have incompatibilities with the included build. In this case, a docker volume mapping can be used to overwrite the included ffmpeg build with an ffmpeg build that works for your specific hardware setup.
To do this:
- Download your ffmpeg build and uncompress to a folder on the host (let's use
/home/appdata/frigate/custom-ffmpegfor this example).
- Update your docker-compose or docker CLI to include
'/home/appdata/frigate/custom-ffmpeg':'/usr/lib/btbn-ffmpeg':'ro'in the volume mappings.
- Restart Frigate and the custom version will be used if the mapping was done correctly.
NOTE: The folder that is mapped from the host needs to be the folder that contains
/bin. So if the full structure is
/home/appdata/frigate/custom-ffmpeg needs to be mapped to
Custom go2rtc version
Frigate currently includes go2rtc v1.8.4, there may be certain cases where you want to run a different version of go2rtc.
To do this:
- Download the go2rtc build to the /config folder.
- Rename the build to
- Restart Frigate and the custom version will be used, you can verify by checking go2rtc logs.
Validating your config.yaml file updates
When frigate starts up, it checks whether your config file is valid, and if it is not, the process exits. To minimize interruptions when updating your config, you have three options -- you can edit the config via the WebUI which has built in validation, use the config API, or you can validate on the command line using the frigate docker container.
Frigate can accept a new configuration file as JSON at the
/config/save endpoint. When updating the config this way, Frigate will validate the config before saving it, and return a
400 if the config is not valid.
curl -X POST http://frigate_host:5000/config/save -d @config.json
if you'd like you can use your yaml config directly by using
yq to convert it to json:
yq r -j config.yml | curl -X POST http://frigate_host:5000/config/save -d @-
Via Command Line
You can also validate your config at the command line by using the docker container itself. In CI/CD, you leverage the return code to determine if your config is valid, Frigate will return
1 if the config is invalid, or
0 if it's valid.
docker run \
-v $(pwd)/config.yml:/config/config.yml \
--entrypoint python3 \
-u -m frigate \