Frigate ignores my custom frigate.yml and defaults to 10.0.10.10 #20138
Replies: 1 comment 1 reply
-
|
In the Home Assistant Add-on, Frigate does not use /config/frigate.yml inside the container. Instead, the configuration directory is mapped to /addon_configs/<addon_directory>/ on the host, and the expected config file name is config.yml or config.yaml (with config.yml taking priority if both exist)(1)(2). For the standard Frigate Add-on, the correct path is: or for the Full Access variant: You should place your configuration in config.yml (not frigate.yml) in the appropriate directory for your specific add-on variant(1)(2). There is a known issue reported by users where the add-on references frigate.yml instead of config.yml, but the official documentation and most installations expect config.yml(1)(3). If you have both frigate.yml and config.yml, only config.yml will be used according to the documentation(1). To resolve your issue:
You can also use the built-in configuration editor in the Frigate UI to edit and validate your configuration(1). References:
📚 Sources:
Have another question? Just tag @inkeep. |
Beta Was this translation helpful? Give feedback.
-
|
The AI's response is correct here. You just need to put your config file in the correct directory for your particular add-on variant. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Describe the problem you are having
Hi,
I am struggling with getting Frigate to use my own configuration in Home Assistant.
Problem
No matter what I do, Frigate keeps ignoring my custom /config/frigate.yml.
Instead, it falls back to the demo/default config which points to rtsp://10.0.10.10:554/rtsp.
The log repeatedly shows errors with 10.0.10.10, even though I have replaced it everywhere.
What I tried
Created /config/frigate.yml manually with my Reolink camera RTSP paths.
Verified RTSP URLs work fine in VLC (rtsp://admin:password@192.168.68.xxx/...).
Set config_path: /config/frigate.yml in the add-on options.
Tried placing the file also in /homeassistant/frigate.yml.
Cleaned up old configs and restarted add-on + HA multiple times.
Deleted/reinstalled the add-on.
Checked that cameras work fine when added directly in HA (outside of Frigate).
Despite all this, Frigate logs always show attempts to connect to 10.0.10.10.
Equipment
Server: Beelink Mini S12 Pro (Intel N100, 16GB RAM, 500GB SSD)
OS: Home Assistant OS (2025.9.x, Supervisor 2025.09.0)
Add-ons: Mosquitto broker, Frigate 0.16.1
Cameras: 2 × Reolink PoE RLC series (working fine in VLC and HA directly)
Example of my frigate.yml
mqtt:
enabled: true
host: core-mosquitto
port: 1883
user: mqttuser
password: "password"
topic_prefix: frigate
cameras:
reolink1:
ffmpeg:
inputs:
- path: rtsp://admin:PASS@192.168.68.128:554/h264Preview_01_sub
roles:
- detect
detect:
width: 640
height: 360
fps: 5
reolink2:
ffmpeg:
inputs:
- path: rtsp://admin:PASS@192.168.68.129:554/h264Preview_01_sub
roles:
- detect
detect:
width: 640
height: 360
fps: 5
Goal
I just want Frigate to respect my config file and use the real camera IPs, not the demo defaults. Later I want to enable detection and recordings, but for now the basic RTSP connection is all I need.
Question
How can I force the HA add-on to load my /config/frigate.yml instead of the built-in demo config?
Is there another location/path I should be using inside HAOS for the add-on to pick up the file?
Any advice would be much appreciated 🙏
Version
Core: 2025.9.3 Supervisor: 2025.09.0 Operating System: 16.2 Frontend/Brugerflade: 20250903.5 Frigate 0.16.1
Frigate config file
Relevant Frigate log output
Relevant go2rtc log output
Frigate stats
"Not available – I don’t know how to access /api/stats."Operating system
Home Assistant OS
Install method
Home Assistant Add-on
docker-compose file or Docker CLI command
Object Detector
Coral
Screenshots of the Frigate UI's System metrics pages
Frigate UI metrics not available at the moment (cannot access System → Metrics or no data shown). Please advise if there is an alternate way to export metrics.
Any other information that may be helpful
Setup: Beelink Mini S12 Pro running Home Assistant OS.
Frigate installed as HA Add-on.
Cameras: 2x Reolink PoE.
Problem: Config file ignored, defaults back to 10.0.10.10 example.
Tried: editing YAML config directly, restarting add-on, validating RTSP in VLC.
Cameras work in VLC and HA directly, but not in Frigate.
Beta Was this translation helpful? Give feedback.
All reactions