go2rtc v1.9.13 adds HTTP-FLV with H265 from new Reolink cameras as well as native Tuya and Xiaomi sources

[bagobones]

I have not tried to add it to test yet but might be a significant update / improvement for those that get lots of errors even with newer cameras on RTSP.

[hawkeye217]

As we've said elsewhere, we won't include newer go2rtc versions in the official builds without significant testing first. But users can always install a custom go2rtc version and use it with Frigate: https://docs.frigate.video/configuration/advanced/#custom-go2rtc-version

[bagobones]

Exactly why I posted this as a separate discussion item, not a feature request.

Just figured it was worth a heads up.

[NickM-27]

I'm hoping things are improved, I know previously the go2rtc reolink implementation had some issues which is why we recommend using ffmpeg in go2rtc

[bagobones]

I'm hoping things are improved, I know previously the go2rtc reolink implementation had some issues which is why we recommend using ffmpeg in go2rtc

I have several newer reolink cameras, and they still occasionally produce bursts error messages in the detect log but don't actually disconnect / restart.

That and model specific like the doorbell the flv may not drop as many frames in some cases.

There is a separate go2rtc feature request to implement the NATIVE reolink protocol which another project has done so that might happen some time... Would be nice if Reolink just continued to improve RTSP stability, which they have been but not consistently.

[bagobones]

So I had a chance to play with this over the holidays, and it isn't worth looking at at this point, probably best to wate for the NATIVE reolink protocol feature that may be worked on SOON? AlexxIT/go2rtc#755 (comment)

But for those curious HTTP-FLV with H265 does works with SOME cameras however it produced MORE stream errors than rtsp.

The camera has to already support the CLEAR stream in the web interface.. It appears web interface 2.0.5 is the earliest that works in my cameras. I have several cameras that still report a 1.0.x web interface and will tell you CLEAR is not available in the web UI.

Note the web interface version is what appears in the browser tab when you connect to the camera. it is loosely related to the cameras firmware version, as I have some cameras with 3.1.x firmware but the older web UI and some with the newer. I suspect cameras with firmware 3.2.x and hither will have the newer web UI but cant confirm.