Hi @AlexxIT - i thought it better to spawn a new thread in here for your go2rtc project (as opposed the now rather large webRTC thread.
i had a fiddle today - it worked great - i think!?! (thats the problem, im not quite sure).
Maybe you can clarify. Heres what i did - im in a docker environment:
- Made my docker-compose (like your example), spun up the container… verified it was up on http://x.x.x.x:1984 (it was - i could browse to it… there was no camera, but in that simple web page i could add my rtsp://xxxxxxx cameras and click in on them and the cam feed would show in the browser
- I tried adding the following in the go2rtc.yaml file to see if i needed to do that so the cams would be there when i rebooted… but it didnt seem to work (after reboot when i came back to the :1984 webpage, there was no cams). Not sure if this is a problem?
streams: - kph_sonoff: rtsp://xxxxxx:[email protected]:554/av_stream/ch0 - kpk_hikvision: rtsp://xxxxxx:[email protected]:554/Streaming/channels/2
- In HASS, added the RTSPtoWebRTC integration, and linked it to your API listener http://my.main.host.ip:1984
- When i look at my picture glance cards - i think they might load faster… is that possible? (as i havent done anything else im a bit confused). I saw on the RTSPtoWebRTC integration page - the video they link there - at timecode 11:45 - he says a way to test if you are using webRTC successfully was to look for the ‘preload stream’ checkbox when you click into your picture glance card… well when i do that, its not there, so does that mean im working through your go2rtc container?