From a92074bc8dac8f4eae25476f5337e5ca994cd034 Mon Sep 17 00:00:00 2001 From: Dermot Duffy Date: Sat, 8 Feb 2025 12:14:23 -0800 Subject: [PATCH] docs: Add troubleshooting entry for unknown frigate instance (#1881) - Related to #1879 --- docs/troubleshooting.md | 21 +++++++++++++++++++++ 1 file changed, 21 insertions(+) diff --git a/docs/troubleshooting.md b/docs/troubleshooting.md index fc4881dd..3ff901d6 100644 --- a/docs/troubleshooting.md +++ b/docs/troubleshooting.md @@ -248,6 +248,27 @@ status_bar: style: none ``` +### Unknown Frigate instance `frigate` + +e.g. `API error whilst subscribing to events for unknown Frigate instance frigate` + +If you are using a custom `client_id` setting in your `frigate.yml` file (the +configuration file for the Frigate backend itself), you must tell the card about +it via the `client_id` parameter: + +```yaml +cameras: + - camera_entity: camera.my_frigate_camera + frigate: + client_id: my-frigate +``` + +See [Frigate engine configuration](configuration/cameras/engine.md?id=frigate) +for more details. + +If you're not using a custom `client_id`, your Frigate integration is likely not +installed correct. + ### `webrtc_card` unloads in the background [AlexxIT's WebRTC Card](https://github.com/AlexxIT/WebRTC) which is embedded by