20s delay between two cameras (Reolink/Frigate/go2rtc)

I have two Reolink cameras. Doorbell and RLC-823A. When I restarted Frigate everything seems to be okay. But after a while, the RLC-823A experiences a delay that becomes larger and larger. up to 20 seconds.

Frigate + go2rtc Version 1.7.1 +

Frigate Config:

go2rtc:
  streams:

    haustur:
      - rtsp://admin:[email protected]:554/h264Preview_01_sub
      
      - "ffmpeg:haustur#audio=opus"
    haustur_main:
      - rtsp://admin:[email protected]:554/h264Preview_01_main
      - "ffmpeg:haustur#audio=opus"
      
    garten:
    - rtsp://admin:[email protected]:554/h264Preview_01_sub
  
  ffmpeg:
    bin: ffmpeg
    volume: "-af \"volume=30dB\""
  webrtc:
    listen: "192.168.2.100:8555"  
    # address of your local server and port (TCP/UDP)  listen: ":8555"  # address of your local server and port (TCP/UDP)
    candidates:
      - stun:8555  # if you have dynamic public IP-address. This allows you to connect to the stream when you're not home.
      #- 127.0.0.1:8555
      - 192.168.2.100:8555
    
  webtorrent:
    shares:
      xxxxx:  # share name, should be unique among all go2rtc users!
        pwd: xxxx
        src: haustur   # stream name from streams section    
        #src: rtsp://192.168.2.100:8554/haustur
        
  log: # Here you define what you want to see in the logging section in the addon page (where you install/configure the go2rtc addon).
    level: info  # default level
    api: info
    exec: info
    ngrok: info
    rtsp: debug
    streams: debug
    webrtc: debug
##########################################################################



cameras:

  haustur:
    ffmpeg:
      inputs:

        - path: rtsp://192.168.2.100:8554/haustur
          roles:
            - detect
            #- record
            #- rtmp
  garten:
    ffmpeg:
      inputs:
        - path: rtsp://192.168.2.100:8554/garten
          roles:
            - detect
            #- record 
            #- rtmp
  


#################################
##    Standard Konfiguration   ##
#################################

objects:
  track:
    - person
  filters:
    person:
      threshold: 0.7

detect:
  width: 800
  height: 480
  enabled: false

snapshots:
  enabled: true
  timestamp: true
  bounding_box: true
  retain:
    default: 14

record:
  enabled: true
  retain_days: 0
  events:
    retain:
      default: 7

ui:
  live_mode: webrtc

is the delay in frigate or when viewing live in home assistant? home assistant uses HLS which is known to have high amounts of latency

I use frigate Card with RTC. There is no delay after a fresh start.

1 Like

I have this delay also, with a reolink cx-410. No errors in frigate but once noticeable delay sets in (>1s) it rapidly increases to c.10s.

I’ve updated go2rtc to latest version and the delay remains with 0.13 beta 3. A restart fixes it until it starts again.

Did you find a fix?

Yes, I don’t use the RTSP stream.

- "ffmpeg:http://192.168.2.111/flv?port=1935&app=bcs&stream=channel0_main.bcs&user=admin&password=XXX#video=copy#audio=copy#audio=opus"

I have this same problem with my Reolink E1 PoE Outdoor too.

It only takes one day and 20 seconds delay is already there. And if I don’t restart HA-OS, the delay gets worse and worse.

That’s not normal. Don’t know what to do. This delay can be seen in Frigate, in the HA-OS Dashboard and HA-Android App.

My other Camera (Upcam Tornado HD S) has no delay.

Same issue here.
Running:
Frigate 0.13.2-6476f8a
RLC-833A
E1 Outdoor PoE

And the RLC-833A gets like 20s delay, but not instantly. If I restart Frigate, the delay is gone for few hours, then it catches up gradually.

It is not a network issue, if I check both cameras stream simultaneously (reolink web interface or VLC) there is no delay between them.

Config for both cameras is identical. Physical connection in network is also same.

Just can’t figure it out…

EDIT 24.07.2024
I replaced the E1 with RLC-520A, as I want to move the E1 to other part of house and the situation is still the same.
I also did some trial’n error regarding connections in network.
The 833A is connected to server via 2 switches and one AP, and although I ruled out the network issue I had to try direct connection to have it on the same topology level like the E1/520A and no change either…

Using go2rtc has been great for me. But I’ve noticed it will be deprecated in HA next year (think June '25). Does anyone else have any other suggestions ahead of this?

I have the same problem with my IP cameras (h.265). Latency is increasing. After reloading the page in the browser, the latency is low but increases.