Help with frigate, ffmpeg and reolink doorbell

Configuration
1

i have recently been having huge troubles with trying to connect my reolink doorbell to frigate and am completely unsure as to why, i used to have it connected but after loosing internet connection to it it took me some time to getting round to re connecting it but i am having constant issues trying to get it to load frames this is what appears in the error log

image
image1322Ă—841 91.2 KB

i know for a fact i have the password and username correct for the stream and its identical to a second reolink camera i have set up that has been working perfectly here is my config as you can tell i got it from following a youtube video a long time ago but even trying to refollow the video i cant wrap my head around whatever problem is happening

mqtt:
  host:        # YOUR MQTT IP
  port: 
  topic_prefix: frigate
  client_id: frigate
  user:                # YOUR MQTT USERNAME
  password:         # YOUT MQTT PASSWORD
  stats_interval: 60

##########################################################################

go2rtc:
  streams:
                    ## CHANGE RTSP USERNAME AND PASSWORD
    front_door:
      - rtsp://user:pass192.168.1.106:554/h264Preview_01_sub
      - ffmpeg:rtsp://user:pass192.168.1.106:554/h264Preview_01_sub#audio=pcm#audio=volume

    doorbell:
      - rtsp://user:pass192.168.1.238:554/h264Preview_01_sub
      - ffmpeg:rtsp://user:pass192.168.1.238:554/h264Preview_01_sub#audio=pcm#audio=volume


## THIS PREVENTS THE AUDIO COMING OUT FROM THE DOORBELL SOUNDING MUFFLED
  ffmpeg:
    bin: ffmpeg
    volume: -af "volume=5dB"

##########################################################################

cameras:

  front_door:
    ffmpeg:
      inputs:
                    ## CHANGE RTSP USERNAME AND PASSWORD 
        - path: rtsp://user:[email protected]:554/h264Preview_01_sub
          roles:
            - detect
      output_args:
        record: preset-record-generic-audio-copy
    zones:
      top_down_drive:
        coordinates: 
          0,720,470,720,1280,720,1280,294,1280,101,1099,73,805,47,579,38,472,48,439,106,304,225,116,488,37,569,0,535                # WATCH MY FRIGATE VIDEO SHOWING YOU WHAT THIS IS
      # WATCH MY FRIGATE VIDEO SHOWING YOU WHAT THIS 

  doorbell:
    ffmpeg:
      inputs:
                    ## CHANGE RTSP USERNAME AND PASSWORD 
        - path: rtsp://user:[email protected]:554/h264Preview_01_sub
          roles:
            - detect
      output_args:
        record: preset-record-generic-audio-copy
    zones:
      doorbell_drive:
        coordinates: 0,720,470,720,1061,720,1087,666,1146,553,1165,458,844,487,564,503,316,497,0,571   # WATCH MY FRIGATE VIDEO SHOWING YOU WHAT THIS IS
    motion:
      mask:
        - 0,374,79,351,103,278,144,241,110,226,0,229



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


detectors:
  ov:
    type: openvino
    device: AUTO
    model:
      path: /openvino-model/ssdlite_mobilenet_v2.xml

model:
  width: 300
  height: 300
  input_tensor: nhwc
  input_pixel_format: bgr
  labelmap_path: /openvino-model/coco_91cl_bkgr.txt

version: 0.14

I’m probably missing something obvious but any help is appreciated thanks

2

401 unauthorized only means 1 thing, incorrect credentials or invalid auth token.

IIRC, someone else had theor reolink product loose all info after being powered down for a period of time and had to do the whole dance of turning RTSP onvif and http web front back on.

I would recommend to factory reset and go through setup again.

2 Likes
3

so reconnect the doorbell to reolink right? i know i have the credentials correct since ive used them a hundred times in other places and i know everything is enabled that should be as far as i am aware i know it kept the ip and everything it should all be the same as far as i can scope out

4

The reolink mobile app doesn’t allow to control RTSP, onvif and http frontend options (afaik). The only way to get to that stuff from my experience (I have reolink doorbell Poe v2) is to use the windows desktop app that reolink provides.

I’m pretty sure it was on ipcamtalk forum that the user posted about the reolink doorbell loosing it’s credentials and/or RTSP settings after being powered down for a few days/weeks, which caused them to factory reset and then do the whole setup again.

1 Like
5

image
image1920Ă—1040 95 KB

these?? i am not very smart when it comes to camera stuff heh i guess ill have to try and factory reset in the morning?

6

Yes, those are the settings you’ll need to toggle.

Here is the post I was referencing: New Reolink Wired POE Doorbell Cam ? | Page 66 | IP Cam Talk

7

they have been on the whole time which is what i dont understand and its a static ip so thats not changed at all

8

That is strange. Have you removed power from the doorbell briefly to see if the old “turn it off and on” trick works?

1 Like
9

tried that along with resetting the wifi router and still the same

10

Go ahead and create another (non-admin) user here and use that in your go2rtc config:

image
image1293Ă—1300 55.9 KB

Also, you should probably just disable everything but RTSP/ONVIF unless you are going to use them elsewhere.

For the go2rtc config, you don’t need to double up on the direct URL for ffmpeg, just reference the name of the camera:

  streams:
    front_door:
      - rtsp://<user>:<pass>@192.168.1.106:554/h264Preview_01_sub
      - ffmpeg:front_door#audio=pcm#audio=volume

In the “camera” section, you can now use the go2rtc stream vs. the camera stream (go2rtc is 127.0.0.1). One of the benefits of using go2rtc is that you won’t have multiple open sessions on the camera itself, thus saving resources.

  front_door:
    ffmpeg:
      inputs:
        - path: rtsp://127.0.0.1:8554/front_door
          roles:
            - detect
1 Like
11

ok well it still doesn’t work i assume I’m doing something wrong because i wasn’t entirely understanding but i do have a different error now here is what i got down

image
image845Ă—241 12.9 KB

image
image844Ă—233 9.15 KB

image

image
image1328Ă—830 90.7 KB

12

anddd now the front door cam is refusing to work even though i didn’t touch anything of that

image
image1336Ă—850 90.8 KB

13

I’m fine with the doorbell not connecting but now the front door cam is gone too that’s a huge issue for some of my automations i have no clue what’s going on at this point

I’ve tried to change everything back at this point and its just not working i dont know what is different i dont know what to change

image
image1379Ă—851 90.7 KB

the cameras are connected to home assistant directly so thankfully non of my automations are broken its just something to do with frigate but i cant find any points that wouldn’t be working i changed everything back to how they were and even the front door cam which has always been working is no longer connecting

–

as a final attempt i realised some port numbers didn’t look right so i changed them and now its just giving an auth error, like before i know they are right unless there is some hidden line of config somewhere i am missing, everything is the same as it was so i do not understand what is going wrong

image
image1354Ă—873 92.5 KB

14

Why do you have a separate go2rtc config file? Is that typical in a HASS installation? (I run in a separate docker instance)

Frigate has a built in implementation of go2rtc so that config should be part of frigate.yml.

1 Like
15

i dont remember setting it up but I’m sure it was a part of whatever tutorial i was following, its just a secondary addon would it help deleting it then?

16

probably. Move your go2rtc config to the frigate.yml and go from there. Having a separate add-on probably complicates things unnecessarily.

Also, I’m PMing you my complete config. Could help as a reference.

1 Like
17

Don’t delete the add-on yet. wait until you get the other config working first. :slight_smile:

18

thanks so much upon trying to change the password it now seems to be trying to idk? merge the end of the password with the ip adress? i feel like if i can stop that it might work?

image
image1241Ă—847 90.4 KB

19

it should be rtsp://user:pass@IPADDRESS…

But looking at your log… don’t use special characters in your password.

2 Likes
20

YES I GOT IT the original password ended with an @ so it wasn’t registering it as the password it was using it as the split oh my god thank you so much!!!

1 Like