From b1bf31fe55ed4fdf8139d5fa322b84c892050f6b Mon Sep 17 00:00:00 2001 From: Robert Resch Date: Tue, 5 Nov 2024 12:46:15 +0100 Subject: [PATCH] Add info about go2rtc ports (#35580) * Add info about go2rtc ports * Apply suggestions from code review Co-authored-by: Martin Hjelmare --------- Co-authored-by: Martin Hjelmare --- source/_integrations/go2rtc.markdown | 8 ++++++-- 1 file changed, 6 insertions(+), 2 deletions(-) diff --git a/source/_integrations/go2rtc.markdown b/source/_integrations/go2rtc.markdown index 523f6112d31..780d7970c58 100644 --- a/source/_integrations/go2rtc.markdown +++ b/source/_integrations/go2rtc.markdown @@ -31,7 +31,7 @@ The following YAML options are available: {% configuration %} debug_ui: required: false - description: Enables the UI of the go2rtc, which helps debugging WebRTC issues. The `debug_ui` should only be enabled during debugging as it will expose port 1984 without any authentication! + description: Enables the UI of the go2rtc, which helps debugging WebRTC issues. The `debug_ui` should only be enabled during debugging as it will expose port 11984 without any authentication! default: false type: boolean url: @@ -40,9 +40,13 @@ url: type: string {% endconfiguration %} +If you using the go2rtc server managed by Home Assistant, please be aware that all ports are prefixed by `1` compared to the default port settings to avoid port conflicts: +- Api port `1984` becomes `11984` +- WebRTC port `8555` becomes `18555` + {% warning %} -The `debug_ui` should only be enabled during debugging as it will expose port 1984 without any authentication! +The `debug_ui` should only be enabled during debugging as it will expose port 11984 without any authentication! Please disable the `debug_ui` immediately after debugging. {% endwarning %}