[Config Support]: problem with go2rtc in Frigate #22601
-
Describe the problem you are havingHi, Running frigate app on HA on Lenovo m710Q. looked for solutions, without success Thanks in advance BR VersionMéthode d'installation Home Assistant OS Core 2026.3.3 Supervisor 2026.03.2 Operating System 17.1 Interface utilisateur 20260312.0 Frigate config filemqtt:
enabled: true
host: 192.168.1.25
user: ******
password: *******
detectors:
ov:
type: openvino
device: GPU
model:
width: 300
height: 300
input_tensor: nhwc
input_pixel_format: bgr
path: /openvino-model/ssdlite_mobilenet_v2.xml
labelmap_path: /openvino-model/coco_91cl_bkgr.txt
ffmpeg:
hwaccel_args: preset-vaapi
detect:
enabled: true
width: 640
height: 360
fps: 5
record:
enabled: True
motion:
days: 7
alerts:
retain:
days: 30
mode: motion
detections:
retain:
days: 30
mode: motion
snapshots:
enabled: True
retain:
default: 30
go2rtc:
streams:
camera_salon_1:
- rtsp://*****:*****@192.168.1.137:554/Preview_01_main
camera_salon_2:
- rtsp://*****:******@192.168.1.137:554/Preview_01_sub
webrtc:
listen: 8555
candidates:
- 127.0.0.1:8555
- 192.168.1.25:8555
cameras:
camera_salon:
enabled: true
friendly_name: Camera Salon
ffmpeg:
inputs:
- path: rtsp://127.0.0.1:8554/camera_salon_1
roles:
- record
- path: rtsp://127.0.0.1:8554/camera_salon_2
roles:
- detect
live:
streams:
Stream 1: camera_salon_1
Stream 2: camera_salon_2
objects:
track:
- person
- dogRelevant Frigate log output2026-03-24 09:59:53.191956869 [INFO] Preparing Frigate...
2026-03-24 09:59:53.531433289 [INFO] Starting Frigate...
2026-03-24 09:59:58.401294363 [2026-03-24 10:59:58] frigate.util.config INFO : Checking if frigate config needs migration...
2026-03-24 09:59:58.412854120 [2026-03-24 10:59:58] frigate.util.config INFO : copying config as backup...
2026-03-24 09:59:58.413512958 [2026-03-24 10:59:58] frigate.util.config INFO : Finished frigate config migration...
2026-03-24 09:59:58.429775702 [2026-03-24 10:59:58] frigate.app INFO : Starting Frigate (0.17.1-416a9b7)
2026-03-24 09:59:58.430419687 [2026-03-24 10:59:58] frigate.app INFO : Creating directory: /tmp/cache
2026-03-24 09:59:58.448647500 [2026-03-24 10:59:58] peewee_migrate.logs INFO : Starting migrations
2026-03-24 09:59:58.449173071 [2026-03-24 10:59:58] peewee_migrate.logs INFO : There is nothing to migrate
2026-03-24 09:59:58.634981732 [2026-03-24 10:59:58] frigate.app INFO : Recording process started: 458
2026-03-24 09:59:58.648958196 [2026-03-24 10:59:58] frigate.app INFO : Review process started: 461
2026-03-24 09:59:58.651397551 [2026-03-24 10:59:58] frigate.app INFO : go2rtc process pid: 119
2026-03-24 09:59:58.917745223 [2026-03-24 10:59:58] frigate.app INFO : Embedding process started: 481
2026-03-24 09:59:58.958234884 [2026-03-24 10:59:58] frigate.app INFO : Output process started: 531
2026-03-24 09:59:59.050497497 [2026-03-24 10:59:59] frigate.api.fastapi_app INFO : Starting FastAPI app
2026-03-24 09:59:59.231470002 [2026-03-24 10:59:59] frigate.api.fastapi_app INFO : FastAPI started
2026-03-24 09:59:59.248915688 [2026-03-24 10:59:59] frigate.camera.maintainer INFO : Camera processor started for camera_salon: 596
2026-03-24 09:59:59.287586360 [2026-03-24 10:59:59] frigate.camera.maintainer INFO : Capture process started for camera_salon: 657Relevant go2rtc log output2026-03-24 09:59:53.453994684 [INFO] Preparing new go2rtc config...
2026-03-24 09:59:53.486131710 [INFO] Got IP address from supervisor: 192.168.1.25
2026-03-24 09:59:53.524541004 [INFO] Got WebRTC port from supervisor: 8555
2026-03-24 09:59:53.836510290 [WARNING] Failed to convert HomeKit config to JSON, skipping cleanup
2026-03-24 09:59:53.836546939 [INFO] Starting go2rtc...
2026-03-24 09:59:54.217973571 10:59:54.217 INF go2rtc platform=linux/amd64 revision=df95ce3 version=1.9.10
2026-03-24 09:59:54.217989391 10:59:54.217 INF config path=/config/go2rtc_homekit.yml
2026-03-24 09:59:54.218845432 10:59:54.218 INF [rtsp] listen addr=:8554
2026-03-24 09:59:54.218847727 10:59:54.218 INF [api] listen addr=:1984
2026-03-24 09:59:54.219121825 10:59:54.219 ERR github.com/AlexxIT/go2rtc/internal/webrtc/webrtc.go:48 > error="listen udp: address 8555: missing port in address"
2026-03-24 10:00:02.926436018 [INFO] Starting go2rtc healthcheck service...Frigate statsNo response Operating systemHome Assistant OS Install methodHome Assistant Add-on docker-compose file or Docker CLI command?Object DetectorCPU (no coral) Screenshots of the Frigate UI's System metrics pagesNo response Any other information that may be helpfulNo response |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 1 reply
-
|
The error in your go2rtc logs indicates the issue: The problem is with your Remove the go2rtc:
streams:
camera_salon_1:
- rtsp://*****:*****@192.168.1.137:554/Preview_01_main
camera_salon_2:
- rtsp://*****:******@192.168.1.137:554/Preview_01_sub
webrtc:
candidates:
- 192.168.1.25:8555
- stun:8555Note that Since you're running Frigate as a Home Assistant add-on, the add-on typically handles WebRTC candidate generation automatically via the Supervisor's API. The logs show it successfully got the IP address and WebRTC port from the supervisor, so you may not even need to manually specify candidates unless you're experiencing issues. 📚 Sources: Have another question? Just tag @inkeep. |
Beta Was this translation helpful? Give feedback.
-
|
@inkeep thanks a lot it has worked I have an issue now in advance camera card, it is blocked to load the live flow when in frigate I have very low latency. Probably it is my Lenovo that is not enough powerfull too. looks like the gpu is not really working. I will continue to dig ;) BR |
Beta Was this translation helpful? Give feedback.
-
|
Glad the WebRTC issue is resolved! For the Advanced Camera Card live stream loading issues, there are a few things to check: Verify VAAPI hardware acceleration is working: Your config uses Camera stream settings to optimize: For best Live view performance with go2rtc, configure your camera firmware with: (2)
For the Advanced Camera Card specifically: If using go2rtc as the source in the card, ensure you're following the card's two-way audio documentation for the correct source configuration. (2) Live view fallback behavior: If your browser struggles to decode the stream, Frigate will fall back to "low bandwidth mode" (jsmpeg). This can happen when loading multiple high-resolution streams or if there are codec incompatibilities. (2) To confirm GPU utilization for decoding, you can check Intel GPU stats, though this requires either running the container in privileged mode or adding the 📚 Sources: Have another question? Just tag @inkeep. |
Beta Was this translation helpful? Give feedback.
The error in your go2rtc logs indicates the issue:
(1)
The problem is with your
webrtc.listenconfiguration. You're usinglisten: 8555but this format is incorrect. Thelistenoption expects a full address with host and port, not just the port number.Remove the
listenline from your go2rtc webrtc configuration. The WebRTC candidates configuration is what you need for internal/local access. Your config should look like this: