From 54d6ba3ba5ed44a541b93253888e44e3cc30aad6 Mon Sep 17 00:00:00 2001 From: Felipe Santos Date: Tue, 17 Jan 2023 10:38:20 -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 878e41a8b..0499b069d 100644 --- a/docs/docs/configuration/live.md +++ b/docs/docs/configuration/live.md @@ -94,7 +94,7 @@ WebRTC works by creating a TCP or UDP connection on port `8555`. However, it req 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: +However, it is recommended if issues occur to define the candidates manually. You should do this if the Frigate add-on fails to generate a valid candidate. If an error occurs you will see some warnings like the below in the add-on logs page during the initialization: ```log [WARN] Failed to get IP address from supervisor