New firmware for reolink RLC-410-5MP

[dison4linux]

I have two reolink RLC-410-5MP cameras that I was just about ready to throw in the bin, but I just went out and checked and they do have a new firmware (v3.0.0.2356_23062000) on their site.
In the past I had been using the recommended HTTP-FLV config for these cameras but still had the occasional hiccup in the logs and I was tired of it so I was just going to toss them. I'm wondering if anyone has any experience with this new version and Frigate?
Are you still using HTTP-FLV or are you trying RTSP?
I'm going to give these a try with RTSP for a few days just to see what happens.
I will caution anyone thinking of upgrading their cameras, this seems to be a pretty major upgrade and the cameras lose HTTP access after the upgrade. You have to use the reolink client on Windows to change the config to enable HTTP (and RTSP).
If it helps, here's the output of FFProbe in RTSP mode:

FFPROBE OUTPUT
Stream 0:
Return Code: 0

Video:

Codec: H.264 / AVC / MPEG-4 AVC / MPEG-4 part 10
Resolution: 2560x1920
FPS: Unknown

Audio:

Codec: AAC (Advanced Audio Coding)

Stream 1:
Return Code: 0

Video:

Codec: H.264 / AVC / MPEG-4 AVC / MPEG-4 part 10
Resolution: 640x480
FPS: Unknown

Audio:

Codec: AAC (Advanced Audio Coding)

[bluearcher-bc]

Reolink firmware is a rabbit hole mixed with a train wreck, and it's unclear from your post what your exact concerns are, but there is a beta firmware link floating around (at least for the RLC-520, which I think are the same or similar firmware) where they fixed the iframes issues that were plaguing a lot of NVRs. It makes iframe configurable to 1 so that you don't have issues with smearing just because you miss an iframe. It's important to note, that even after the update, this setting is not available on the HTTP admin page, you can only set it using the Reolink app under Device > Stream. I use the Windows app, not sure if it's applicable to other OS.

firmware on my 520s is v3.0.0.660_21111507, which is not available on their public downloads site, and it may never be, since the non-A cameras aren't supported anymore. your 23062000 looks like it might be "newer" but I don't know anything about that one or what is supposed to be fixed. the iframe setting is important, though.

[bluearcher-bc]

Also, this is my config in Frigate, I am using go2rtc:

go2rtc:
  ffmpeg:
    http-reolink: "-avoid_negative_ts make_zero -fflags +genpts+discardcorrupt -flags low_delay -strict experimental -analyzeduration 1000M -probesize 1000M -rw_timeout 5000000 -i {input}"

[bluearcher-bc]

https://github.com/AT0myks/reolink-fw-archive/

[dison4linux]

it's unclear from your post what your exact concerns are

I had tried using RTSP in the past and things looked promising for the first 12-18 hours but then I experienced the "train wreck" you mentioned. I'm trying RTSP again on the newer firmware and again things look promising out of the gate, but if someone else has already tried and encountered the same issues, that would save me the attempt.

[dison4linux]

Unfortunately RTSP is still unreliable with the new firmware.
On the plus side, I've had them configured as HTTP-FLV for a couple days now and I don't have any errors in the Frigate logs yet.

[lawrence-jeff]

Have you tried the RTMP feed, I generally have better luck with that on mine. RTSP seems to go wonky with green blocks frequently, and HTTP works but seems to use more CPU (with all settings the same).

I'm upgrading my firmware now to this new version to see if that changes anything.