From 06e0c3abb2ee1f00e38d638d0d43ceec0e031650 Mon Sep 17 00:00:00 2001 From: Felipe Santos Date: Tue, 17 Jan 2023 10:37:59 -0300 Subject: [PATCH] Update docs/docs/configuration/live.md Co-authored-by: Nicolas Mowen --- docs/docs/configuration/live.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/docs/configuration/live.md b/docs/docs/configuration/live.md index 5a317539e..878e41a8b 100644 --- a/docs/docs/configuration/live.md +++ b/docs/docs/configuration/live.md @@ -92,7 +92,7 @@ WebRTC works by creating a TCP or UDP connection on port `8555`. However, it req :::tip -This extra configuration is probably not required if you installed Frigate through the Home Assistant add-on, as Frigate uses the Supervisor's API to get both the local IP of the device and the port that go2rtc's WebRTC interface has been forwarded to. +This extra configuration may not be required if Frigate has been installed as a Home Assistant add-on, as Frigate uses the Supervisor's API to generate a WebRTC candidate. However, defining the candidates manually will not hurt even if you are using the Home Assistant add-on. You should do this if the Frigate add-on fails to detect this information. If it's the case, you will see some warnings like the below in the add-on logs page during the initialization: