-
Notifications
You must be signed in to change notification settings - Fork 121
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Native WebRTC and URL Template #797
Comments
When I enable it, the template URL is ignored. |
It is not completely ignored. It is still used for legacy HLS playing, like when you cast your camera to a Chromecast. But this is a different topic. Your issue is that you are creating streams in go2rtc with different names. This is unsupported. Just make sure the H264 stream name in go2rtc is the same as your Frigate camera name. go2rtc:
streams:
camera_name_here: rtsp://something
cameras:
camera_name_here:
[...] These names must match. |
The exact same expectation is used by the Frigate UI as well, when streaming the camera. |
Yes, I assumed so. The fact is that I wanted to retain the native H265 stream for recording and use the transcoded H264 one just for WebRTC. What I don't understand is the stream name matching: it has to match the stream that has
|
You are free to write whatever URL in the camera ffmpeg inputs, the URL there doesn't need to match anything at all. What matters is the camera name under Frigate cameras, and under go2rtc streams. They must match. |
I mean, in the example, in go2rtc there are 2 streams In go2rtc there s only 1 camera with name So the match has to be on the on the go2rtc stream used for WebRTC? Otherwise, I could choose in Frigate as camera_name either |
Yes, the go2rtc stream whose name is the same as the camera name in Frigate is the stream where Frigate and Home Assistant will use for live streaming, including WebRTC. |
Home Assistant:
Core 2024.11.3
Supervisor 2024.11.4
Operating System 13.2
Frontend 20241106.2
Frigate (standalone):
0.14.1
frigate-hass-integration:
5.5.1
To leverage WebRTC, I created new streams with go2rtc in frigate configuration with H264 transcoding. The streams are not used by Frigate itself but I put this RTSP URL template in the integration configuration to point to the new "live" streams:
rtsp://frigate.home.arpa:8554/{{name}}_live
aiohttp.client_exceptions.ContentTypeError: 500, message='Attempt to decode JSON with unexpected mimetype: text/plain; charset=utf-8', url='http://frigate.home.arpa:5000/api/go2rtc/webrtc?src=<camera_name>'
Effectively the stream does not exist neither if I manually add the "_live" stream that exist in go2rtc inside frigate.
Go2rtc configuration in Frigate:
The text was updated successfully, but these errors were encountered: