From 35ddc896faf1a1f78f1e03f2390851e8e3fa1b43 Mon Sep 17 00:00:00 2001 From: David Buezas Date: Sun, 23 Apr 2023 14:41:22 +0200 Subject: [PATCH] Docs: access go2rtc stream externally while using add-on #6208 (#6209) It took me quite a while to figure out why I couldn't access the go2rtc streams, maybe this saves others some time too. Original question: #6148 --- docs/docs/guides/configuring_go2rtc.md | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/docs/docs/guides/configuring_go2rtc.md b/docs/docs/guides/configuring_go2rtc.md index fa4c30782..7c7bf663d 100644 --- a/docs/docs/guides/configuring_go2rtc.md +++ b/docs/docs/guides/configuring_go2rtc.md @@ -71,6 +71,12 @@ go2rtc: - "ffmpeg:rtsp://user:password@10.0.10.10:554/cam/realmonitor?channel=1&subtype=2#video=copy#audio=copy#audio=aac" ``` +:::caution + +To access the go2rtc stream externally when utilizing the Frigate Add-On, for instance, through a WebRTC card or VLC, you must first enable the RTSP Restream port. You can do this by visiting the Frigate Add-On configuration page within Home Assistant and revealing the hidden options under the "Show disabled ports" section. + +::: + ## Next steps 1. If the stream you added to go2rtc is also used by Frigate for the `record` or `detect` role, you can migrate your config to pull from the RTSP restream to reduce the number of connections to your camera as shown [here](/configuration/restream#reduce-connections-to-camera).