Frigate go2rtc example. Avoid changing any other parts of your config at this step. Oct 23, 2023 · I just noticed in this last Reolink example that that go2rtc name does NOT match exactly the camera name, which seems to sort of halfway break Frigate in practice and force it to use only jsmpeg. Powered by a worldwide community of tinkerers and DIY enthusiasts. Alas too late, I sent the cameras back and went for HikVision cameras. Apr 26, 2023 · The latest version of Frigate NVR is out with new features, including the switch to go2rtc 1. Feb 27, 2026 · Learn how to set up Go2RTC for universal camera streaming with Frigate and Home Assistant, including protocol support, FFmpeg transcoding, and advanced configurations for low-latency video in home automation. Full configuration reference: It is not recommended to copy this full configuration file. Describe the problem you are having When person is detected on my reolink camera, a notification is sent to my android phone (via home assistant app/ frigate notifications blueprint) with options t Jan 5, 2026 · I did try using go2rtc, but I didnt think of taking the main stream and restreaming it. Home Assistant is open source home automation that puts local control and privacy first. yml (after modifying, you will need to run docker compose up -d to apply changes). Perfect to run on a Raspberry Pi or a local server. First, you will want to configure go2rtc to connect to your camera stream by adding the stream you want to use for live view in your Frigate config file. Available for free at home-assistant. I'm struggling to understand the Frigate/go2rtc setup. . Configure the streams option with a "friendly name" for your stream followed by the go2rtc stream name. Mar 8, 2026 · This document covers the configuration of FFmpeg and go2rtc within Frigate. It explains how to configure FFmpeg arguments for video decoding, encoding, and processing, as well as how to set up go2rtc for stream management and restreaming. Frigate supports the use of environment variables starting with FRIGATE_ only where specifically indicated in the reference config. For example, the following values can be replaced at runtime by using environment variables: One stream instance with #backchannel=0 for Frigate's viewing, recording, and detection (prevents go2rtc from establishing the blocking backchannel) A second stream instance without #backchannel=0 for two-way talk functionality (can be used by Frigate's WebRTC viewer or other applications) Configuration example: The cameras are first added to go2rtc, and the cameras section pulls the feed from there into Frigate (and Home Assistant) mqtt: enabled: False ffmpeg: hwaccel_args: preset-nvidia-h264 input_args: -avoid_negative_ts make_zero -fflags +genpts+discardcorrupt -flags low_delay -strict experimental -analyzeduration 1000M -probesize 1000M -rw_timeout This appears to be a legitimate bug that should be reported to the Frigate development team if it hasn't been already, as the MQTT status topics are intended to provide reliable camera health monitoring. 0. First off, I must say, both tools are fantastic for setting up a robust surveillance system. Using Frigate's internal version of go2rtc is required to use this feature. The hw/fw is amazing, the client side software SUCKS, but then I have frigate To access the go2rtc stream externally when utilizing the Frigate App (for instance through VLC), you must first enable the RTSP Restream port. The issue appears to be in Frigate LPR timing/clustering, not in go2rtc stream handling. Relevant go2rtc log output No relevant go2rtc log output. my frigate and ha are running in different vm’s, i couldn’t able to make it work. Note that go2rtc supports many different stream types, not just rtsp. I went through the full workflow of getting a few of my newer nest cameras working in Frigate through go2rtc. Frigate's default dashboard ("All Cameras") will always use the first entry you've defined in streams: when playing live streams from your cameras. I have 1 out of 6 cameras set up and it’s working for detection with some recording. It seems like this process changes quite frequently but here it is, tested and working, as of today. You can do this by visiting the Frigate App configuration page within Home Assistant and revealing the hidden options under the "Show disabled ports" section. Nov 7, 2025 · Hey everyone, I’ve been diving into the world of home security cameras and automation, and I’ve got some experiences to share regarding Frigate and Go2rtc. It works pretty well but at night time it can’t detect Here is an example configuration with hardware acceleration configured to work with most Intel processors with an integrated GPU using the preset: docker-compose. Aug 20, 2023 · I have been trying to set up go2rtc in frigate, from my understanding if I set this up it will be more lightweight on my system for viewing live feeds? Currently if I click frigate in the sidebar in HA I can see a live stream on the frigate dashboard. so i am still keeping the homekit camera in ha with go2rtc add-on for now until i figure out. Configuration options and default values may change in future versions. io. 2. Only specify values that are different from the defaults. Jan 10, 2025 · I was going to remove the go2rtc add-on in ha, but there is one camera which homekit camera that i paired from within ha, i am unable to use that in frigate config. I will take you through the major updates, starting with a docker install of Frigate. pob 5r7p mlu oyl 3iho fqx7 yf1 lgu gao kpgu oj55 p2tq sog gq5 fbm gke dmoo 7amx mlsi zki xh7b gh8 82tk tuu cuy7 byl 2vgu 8yy sf9 rcm