[Camera Support]: Reolink

[Coryrichter94]

Describe the problem you are having

I have tried everything but get the error logs attached
I have connected to the stream from the config file using vlc media player without issues.

Version

0.13.2-6476F8A

Frigate config file

mqtt:
  enabled: False

go2rtc:
  streams:
    Front:
      - rtsp://admin:[email protected]:554/h265Preview_01_main
    Front_sub:
      - rtsp://admin:[email protected]:554/h265Preview_01_sub

cameras:
  Front:
    ffmpeg:
      inputs:
        - path: rtsp://127.0.0.1:8554/Front # Reference the go2rtc stream name
          roles:
            - record
        - path: rtsp://127.0.0.1:8554/Front_sub # Reference the go2rtc stream name
          roles:
            - detect

Relevant log output

`2024-07-25 22:54:22.886030161  [INFO] Preparing new go2rtc config...
2024-07-25 22:54:23.177020327  [INFO] Starting go2rtc...
2024-07-25 22:54:23.257270891  22:54:23.257 INF go2rtc version 1.8.4 linux/amd64
2024-07-25 22:54:23.257571813  22:54:23.257 INF [rtsp] listen addr=:8554
2024-07-25 22:54:23.257677470  22:54:23.257 INF [webrtc] listen addr=:8555
2024-07-25 22:54:23.260173732  22:54:23.260 INF [api] listen addr=:1984
2024-07-25 22:54:27.419961939  22:54:27.419 WRN [rtsp] error="streams: dial tcp 192.168.1.254:554: i/o timeout, dial tcp 192.168.1.254:554: connect: no route to host" stream=Front_sub
2024-07-25 22:54:32.958127643  [INFO] Starting go2rtc healthcheck service...
2024-07-25 22:54:33.373096645  22:54:33.372 WRN [rtsp] error="streams: dial tcp 192.168.1.254:554: i/o timeout, dial tcp 192.168.1.254:554: connect: no route to host" stream=Front_sub`

FFprobe output from your camera

not sure how sorry

Frigate stats

No response

Operating system

Other Linux

Install method

Docker Compose

Object Detector

CPU (no coral)

Network connection

Wired

Camera make and model

Reolink RLC-1240A

Any other information that may be helpful

No response

[NickM-27]

No route to host means the camera doesn't exist or is not reachable from the frigate container.

[Coryrichter94]

What could be causing this? It's on the same network. I also setup the docker in host network mode. I have temporarily disabled firewalls and still have the same problem

[NickM-27]

Maybe try using ffmpeg and see how that goes

go2rtc:
  streams:
    Front:
      - "ffmpeg:rtsp://admin:[email protected]:554/h265Preview_01_main"
    Front_sub:
      - "ffmpeg:rtsp://admin:[email protected]:554/h265Preview_01_sub"

[Coryrichter94]

Get the following errors now :/ p.s. I really appreciate all your help!

2024-07-25 23:18:35.036910735  23:18:35.036 WRN [rtsp] error="streams: exec: exit status 1" stream=Front_sub
2024-07-25 23:18:36.610354025  [INFO] Starting go2rtc healthcheck service...
2024-07-25 23:18:41.181921817  23:18:41.181 WRN [rtsp] error="streams: exec: exit status 1" stream=Front_sub
2024-07-25 23:19:01.277321347  23:19:01.277 WRN [rtsp] error="streams: exec: exit status 1" stream=Front_sub
2024-07-25 23:19:11.324617114  23:19:11.324 WRN [rtsp] error="streams: exec: exit status 1" stream=Front_sub
2024-07-25 23:19:20.540993489  23:19:20.540 WRN [rtsp] error="streams: exec: exit status 1" stream=Front_sub
2024-07-25 23:19:29.756648920  23:19:29.756 WRN [rtsp] error="streams: exec: exit status 1" stream=Front_sub

[NickM-27]

I'd suggest a different ip address, something not at the very end of the mask like 110

[Coryrichter94]

same issue with both ffmpeg and my original config with 192.168.1.12 still same errors :(

[paulzwarts]

I cant speak for all reolinks, but I have had a few over the years. On my RLC-811a the Preview_01_main is h265 encoding and the Preview_01_sub is h264. This config works for me. And I'm not sure the hwaccel_args=hevc_cuvid part does anything becuase it worked without that definition.

To debug that you should run an ffmpeg -i with your connection string in a shell to see if it connects and the probe is able to detect the stream. At that point you use if uses h264 and h265

go2rtc:
  rtsp:
  streams:
    border:
    - rtsp://user:[email protected]:554/Preview_01_main
    - ffmpeg:border#audio=aac#hwaccel_args=hevc_cuvid 

cameras:
  border:
    enabled: true
    ffmpeg:
      inputs:
      - path: rtsp://127.0.0.1:8554/border
        input_args: preset-rtsp-restream
        roles:
        - detect
        - audio
        - record
    detect:
      width: 4608
      height: 1728

[NickM-27]

to be clear here #hwaccel_args=hevc_cuvid is doing nothing, go2rtc does not know what this means

[Coryrichter94]

I cant speak for all reolinks, but I have had a few over the years. On my RLC-811a the Preview_01_main is h265 encoding and the Preview_01_sub is h264. This config works for me. And I'm not sure the hwaccel_args=hevc_cuvid part does anything becuase it worked without that definition.

To debug that you should run an ffmpeg -i with your connection string in a shell to see if it connects and the probe is able to detect the stream. At that point you use if uses h264 and h265

go2rtc:
  rtsp:
  streams:
    border:
    - rtsp://user:[email protected]:554/Preview_01_main
    - ffmpeg:border#audio=aac#hwaccel_args=hevc_cuvid 

cameras:
  border:
    enabled: true
    ffmpeg:
      inputs:
      - path: rtsp://127.0.0.1:8554/border
        input_args: preset-rtsp-restream
        roles:
        - detect
        - audio
        - record
    detect:
      width: 4608
      height: 1728

Still getting an error :( 2024-08-01 17:21:56.235989023 17:21:56.235 WRN [rtsp] error="streams: dial tcp 192.168.18.12:554: i/o timeout, exec: exit status 1" stream=border 2024-08-01 17:21:56.236055574 17:21:56.236 WRN github.com/AlexxIT/go2rtc/internal/rtsp/rtsp.go:225 > error="write tcp 127.0.0.1:8554->127.0.0.1:38706: write: broken pipe" 2024-08-01 17:22:06.458303599 17:22:06.457 WRN [rtsp] error="streams: dial tcp 192.168.18.12:554: i/o timeout, exec: exit status 1" stream=border 2024-08-01 17:22:06.458773001 17:22:06.458 WRN github.com/AlexxIT/go2rtc/internal/rtsp/rtsp.go:225 > error="write tcp 127.0.0.1:8554->127.0.0.1:37884: write: broken pipe"

[Coryrichter94]

I solved it. There was a routing issue with the docker server preventing it from accessing any lan ips except the router itself. Thank you everyone