Frigate - Konfiguration für Reolink (Troubleshooting)

Add-ons
, ,
1

Hallo Zusammen, ich habe gestern meine neue Reolink-Kamera (Reolink RLC-823S1) installiert und will diese jetzt in Frigate integrieren.

Ich habe mir hierzu einige Videos und Blockbeiträge angeschaut und eine Konfig erstellt:

mqtt:
  enabled: true
  host: core-mosquitto
  port: 1883
  topic_prefix: frigate
  client_id: frigate
  user: 'XXXX'
  password: 'XXXX'
  stats_interval: 30

database:
  path: /config/frigate.db

ffmpeg:
  hwaccel_args: preset-vaapi

detectors:
  coral:
    type: edgetpu
    device: usb

cameras:
  Haustür:                                                            #Kameraname
    ffmpeg:
      inputs:
        - path: 'rtsp://Frigate:XXX@192.168.178.XXX:554/h264Preview_01_main'    #RTSP Stream High Res
          input_args: preset-rtsp-restream
          roles:
            - record
        - path: 'rtsp://Frigate:XXXX@192.168.178.XXX:554/h264Preview_01_sub'          #RTPS Stream Low Res
          input_args: preset-rtsp-restream
          roles:
            - detect
    detect:
      width: 2560
      height: 1440
      fps: 20
    objects:
      track:
        - person
        - cat
    snapshots:
      enabled: true
      timestamp: true
      bounding_box: true
      retain:
        default: 30
    record:
      enabled: true
      events:
        retain:
          default: 14

Leider startet Frigate nicht einmal und es erscheint folgendes im Log:

s6-rc: info: service s6rc-fdholder: starting
s6-rc: info: service s6rc-oneshot-runner: starting
s6-rc: info: service s6rc-oneshot-runner successfully started
s6-rc: info: service fix-attrs: starting
s6-rc: info: service s6rc-fdholder successfully started
s6-rc: info: service fix-attrs successfully started
s6-rc: info: service legacy-cont-init: starting
s6-rc: info: service legacy-cont-init successfully started
s6-rc: info: service log-prepare: starting
s6-rc: info: service log-prepare successfully started
s6-rc: info: service nginx-log: starting
s6-rc: info: service go2rtc-log: starting
s6-rc: info: service frigate-log: starting
s6-rc: info: service certsync-log: starting
s6-rc: info: service nginx-log successfully started
s6-rc: info: service frigate-log successfully started
s6-rc: info: service certsync-log successfully started
s6-rc: info: service go2rtc-log successfully started
s6-rc: info: service go2rtc: starting
s6-rc: info: service go2rtc successfully started
s6-rc: info: service go2rtc-healthcheck: starting
s6-rc: info: service frigate: starting
s6-rc: info: service frigate successfully started
s6-rc: info: service nginx: starting
s6-rc: info: service go2rtc-healthcheck successfully started
2025-01-20 11:39:03.714882720  [INFO] Starting NGINX...
2025-01-20 11:39:03.715217271  [INFO] Preparing Frigate...
2025-01-20 11:39:03.755031987  [INFO] No TLS certificate found. Generating a self signed certificate...
2025-01-20 11:39:04.032693015  [INFO] Preparing new go2rtc config...
2025-01-20 11:39:04.047400604  [INFO] Starting Frigate...
2025-01-20 11:39:04.178839731  [INFO] Got IP address from supervisor: 192.168.178.71
2025-01-20 11:39:04.322728257  [INFO] Got WebRTC port from supervisor: 8555
2025-01-20 11:39:05.634590958  [INFO] Starting go2rtc...
2025-01-20 11:39:05.826681230  12:39:05.826 INF go2rtc platform=linux/arm64 revision=b2399f3 version=1.9.2
2025-01-20 11:39:05.826733488  12:39:05.826 INF config path=/dev/shm/go2rtc.yaml
2025-01-20 11:39:05.830311419  12:39:05.828 INF [rtsp] listen addr=:8554
2025-01-20 11:39:05.830321419  12:39:05.829 INF [webrtc] listen addr=:8555/tcp
2025-01-20 11:39:05.830453380  12:39:05.828 INF [api] listen addr=:1984
s6-rc: info: service nginx successfully started
s6-rc: info: service certsync: starting
2025-01-20 11:39:08.539906738  2025/01/20 12:39:08 [error] 185#185: *1 connect() failed (111: Connection refused) while connecting to upstream, client: 127.0.0.1, server: , request: "GET /api/version HTTP/1.1", subrequest: "/auth", upstream: "http://127.0.0.1:5001/auth", host: "127.0.0.1:5000"
2025-01-20 11:39:08.539923164  2025/01/20 12:39:08 [error] 185#185: *1 auth request unexpected status: 502 while sending to client, client: 127.0.0.1, server: , request: "GET /api/version HTTP/1.1", host: "127.0.0.1:5000"
s6-rc: info: service certsync successfully started
s6-rc: info: service legacy-services: starting
2025-01-20 11:39:08.557305215  [INFO] Starting certsync...
s6-rc: info: service legacy-services successfully started
2025-01-20 11:39:08.902642196  127.0.0.1 - - [20/Jan/2025:12:39:08 +0100] "" 400 0 "-" "-" "-"
2025-01-20 11:39:09.523601697  [2025-01-20 12:39:09] frigate.app                    INFO    : Starting Frigate (0.14.1-f4f3cfa)
2025-01-20 11:39:09.525141860  [2025-01-20 12:39:09] frigate.app                    INFO    : Creating directory: /tmp/cache
2025-01-20 11:39:09.525285914  [2025-01-20 12:39:09] frigate.util.config            INFO    : Checking if frigate config needs migration...
2025-01-20 11:39:09.567371116  [2025-01-20 12:39:09] frigate.util.config            INFO    : copying config as backup...
2025-01-20 11:39:09.569050519  [2025-01-20 12:39:09] frigate.util.config            INFO    : Migrating frigate config from 0.13 to 0.14...
2025-01-20 11:39:09.588327228  [2025-01-20 12:39:09] frigate.util.config            INFO    : Migrating export file names...
2025-01-20 11:39:09.594608121  [2025-01-20 12:39:09] frigate.util.config            INFO    : Finished frigate config migration...
2025-01-20 11:39:09.619933245  *************************************************************
2025-01-20 11:39:09.619943412  *************************************************************
2025-01-20 11:39:09.619945819  ***    Your config file is not valid!                     ***
2025-01-20 11:39:09.619948005  ***    Please check the docs at                           ***
2025-01-20 11:39:09.619959912  ***    https://docs.frigate.video/configuration/index     ***
2025-01-20 11:39:09.620080447  *************************************************************
2025-01-20 11:39:09.620083947  *************************************************************
2025-01-20 11:39:09.620085947  ***    Config Validation Errors                           ***
2025-01-20 11:39:09.620087836  *************************************************************
2025-01-20 11:39:09.620100428  name: String should match pattern '^[a-zA-Z0-9_-]+$'
2025-01-20 11:39:09.620102743  *************************************************************
2025-01-20 11:39:09.620104613  ***    End Config Validation Errors                       ***
2025-01-20 11:39:09.620106484  *************************************************************
2025-01-20 11:39:11.300196620  [INFO] Service Frigate exited with code 1 (by signal 0)
s6-rc: info: service legacy-services: stopping
s6-rc: info: service legacy-services successfully stopped
s6-rc: info: service go2rtc-healthcheck: stopping
s6-rc: info: service certsync: stopping
2025-01-20 11:39:11.332345685  [INFO] The go2rtc-healthcheck service exited with code 256 (by signal 15)
s6-rc: info: service go2rtc-healthcheck successfully stopped
2025-01-20 11:39:11.336076614  [INFO] Service CERTSYNC exited with code 256 (by signal 15)
s6-rc: info: service certsync successfully stopped
s6-rc: info: service nginx: stopping
s6-rc: info: service certsync-log: stopping
s6-rc: info: service certsync-log successfully stopped
2025-01-20 11:39:11.414194882  [INFO] Service NGINX exited with code 0 (by signal 0)
s6-rc: info: service nginx successfully stopped
s6-rc: info: service nginx-log: stopping
s6-rc: info: service frigate: stopping
s6-rc: info: service frigate successfully stopped
s6-rc: info: service go2rtc: stopping
s6-rc: info: service frigate-log: stopping
s6-rc: info: service nginx-log successfully stopped
2025-01-20 11:39:11.425631869  exit with signal: terminated
s6-rc: info: service frigate-log successfully stopped
2025-01-20 11:39:11.443728521  [INFO] The go2rtc service exited with code 0 (by signal 0)
s6-rc: info: service go2rtc successfully stopped
s6-rc: info: service go2rtc-log: stopping
s6-rc: info: service go2rtc-log successfully stopped
s6-rc: info: service log-prepare: stopping
s6-rc: info: service s6rc-fdholder: stopping
s6-rc: info: service log-prepare successfully stopped
s6-rc: info: service legacy-cont-init: stopping
s6-rc: info: service s6rc-fdholder successfully stopped
s6-rc: info: service legacy-cont-init successfully stopped
s6-rc: info: service fix-attrs: stopping
s6-rc: info: service fix-attrs successfully stopped
s6-rc: info: service s6rc-oneshot-runner: stopping
s6-rc: info: service s6rc-oneshot-runner successfully stopped

Hat jemand eine Idee warum das nicht klappt? Ich habe Frigate auf dem Rasp4 installiert und “läuft” als HA Add-On.

2

Gib mal die IP Adresse deines HomeAssistant ein und lasse den Port weg, außer du hast ihn explizit im Frigate Addon definiert.

3

Es scheint so, als ob die mqtt Einstellungen funktionieren. Es gibt Probleme bei der Kamera.

4

Versuche es mal mit der Frigate.Yml zu starten

5

Wie soll ich denn Frigate sonst starten? Ich nutze hier die frigate.yaml.

7 
mqtt:

  host: 192.168.xxx.xxx
  port: 1883
  topic_prefix: frigate
  client_id: frigate
  user: mqttuser
  password: password # für den mqttuser

detectors:
  coral:
    type: edgetpu
    device: usb


cameras:
#
##################### Kamerasetup ###############################################
#  
  hof:
    ffmpeg:
      hwaccel_args: preset-vaapi
      inputs:
        - path: rtsp://user:password@192.168.xxx.xxx:554/h264Preview_01_main    #RTSP Stream High Res
          input_args: preset-rtsp-restream
          roles:
            - record
        - path: rtsp://user:password@192.168.xxx.xxx:554/h264Preview_01_sub     #RTPS Stream Low Res
          input_args: preset-rtsp-restream
          roles:
            - detect

diese Werte übertrage ich deine Frigate.yml (ich habe yml und nicht yaml im HA angelegt). So läuft Frigate bei mir mit 3 Reolink Kameras ohne Probleme. Die Konfiguration kannst du dann später unter Frigate - Setup - Configuration Editor weiter bearbeiten und optimieren.

:crayon:by HarryP:
. Zusammenführung Doppelpost (bitte “bearbeiten” Funktion nutzen)
. Codezeilen formatiert (bitte immer in </> einbinden)

8

ich glaube die Hochkommas bei path sind falsch und gehören weg

falsch:

- path: 'rtsp://Frigate:XXX@192.168.178.XXX:554/h264Preview_01_main'    #RTSP Stream High Res

richtig:

- path: rtsp://Frigate:XXX@192.168.178.XXX:554/h264Preview_01_main    #RTSP Stream High Res
9

Sorry, ich sehe gerade, dass es mit dem Blockzitat nicht geklappt hat. Hier nochmal mein Yml File

mqtt:

  host: 192.168.xxx.xxx
  port: 1883
  topic_prefix: frigate
  client_id: frigate
  user: mqttuser
  password: password

detectors:
  coral:
    type: edgetpu
    device: usb


cameras:
#
##################### Kamerasetup ###############################################
#  
  hof:
    ffmpeg:
      hwaccel_args: preset-vaapi
      inputs:
        - path: rtsp://user:password@192.168.xxx.xxx:554/h264Preview_01_main    #RTSP Stream High Res
          input_args: preset-rtsp-restream
          roles:
            - record
        - path: rtsp://user:password@192.168.xxx.xxx:554/h264Preview_01_sub     #RTPS Stream Low Res
          input_args: preset-rtsp-restream
          roles:
            - detect

Versuche mal, die komplette Adresse unter “rtsp” im VLC Player einzugeben, also so “rtsp://user:password@192.168.xxx.xxx:554”. Wenn dann dort das Livevideo läuft, sollte es auch in Frigate funktionieren.

10

Jetzt sehe ich immerhin den Stream… der Fehler war, dass ich preset-vaapi unter hwaccel Presets eingestellt hatte, und nicht preset-rpi-64-h265

11

Prima! Danke für die Rückmeldung.

12

Habt ihr Camera Autotracking bei der Reolink versucht?

13

Nein, ich habe zwei Duo 2 WIFI und eine RLC-810WA

14

Vielen Dank an dieser Stelle für deinen Post. Er hat mir dabei geholfen, meine TAPO c320cw zum Laufen zu bringen (nachdem ich bald verzeifelt bin, da es immer wieder zu Problemen mit ffmpeg gekommen war).

15

Danke für die Rückmeldung! Freut mich, dass ich dir helfen konnte.

1 „Gefällt mir“