From 1bf3b83ef38d25238d5d6ef1bcbbf28dc9386815 Mon Sep 17 00:00:00 2001 From: Chris Cox Date: Thu, 23 Mar 2023 00:48:24 +0000 Subject: [PATCH] Fixed extension of config file (#5803) * Fixed extension of config file Using frigate.yml as the config file for the HA addon gives a validation error, the same contents in frigate.yaml work. * More accurate description of config file handling. * Update docs/docs/configuration/index.md Co-authored-by: Nicolas Mowen --------- Co-authored-by: Nicolas Mowen --- docs/docs/configuration/index.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/docs/configuration/index.md b/docs/docs/configuration/index.md index 62c3a5dee..b633174d1 100644 --- a/docs/docs/configuration/index.md +++ b/docs/docs/configuration/index.md @@ -3,7 +3,7 @@ id: index title: Configuration File --- -For Home Assistant Addon installations, the config file needs to be in the root of your Home Assistant config directory (same location as `configuration.yaml`) and named `frigate.yml`. +For Home Assistant Addon installations, the config file needs to be in the root of your Home Assistant config directory (same location as `configuration.yaml`). It can be named `frigate.yml` or `frigate.yaml`, but if both files exist `frigate.yaml` will be preferred and `frigate.yml` will be ignored. For all other installation types, the config file should be mapped to `/config/config.yml` inside the container.