probe webrtc before reporting it as not configured

The WebRTC gate read only the Frigate config, so an install with no go2rtc candidates showed WebRTC as not configured, even though go2rtc fills in default candidates at startup (including the internal one under the HA app) and WebRTC often worked. Unset candidates now run the connectivity probe first, and only a failed probe reports not configured. The not-configured reason shows as a neutral note that names the setting and says WebRTC is optional, rather than as a red error.
This commit is contained in:
Josh Hawkins
2026-10-15 21:16:44 -05:00
parent 3cd4c9c55c
commit 87a7551aaa
5 changed files with 106 additions and 12 deletions
+2 -1
View File
@@ -187,7 +187,8 @@
},
"unavailable": {
"browser": "Your browser does not support WebRTC.",
"not-configured": "WebRTC is not configured. Set go2rtc webrtc candidates or ice_servers.",
"not-configured": "To enable, add this server's IP:8555 under go2rtc → webrtc → candidates.",
"notConfiguredOptional": "Optional: live view works without it. WebRTC is mainly needed for two-way talk.",
"unreachable": "WebRTC could not connect. Check that port 8555 is reachable and any STUN/TURN server is correct.",
"video-codec": "This stream's video codec is not supported by WebRTC in this browser.",
"audio-codec": "This stream's audio codec is not supported by WebRTC. Transcode to opus or G.711 with go2rtc.",