Config help for Reolink doorbell (Frigate + HA integration at the same time) #7791

celodnb · 2023-09-13T18:23:26Z

celodnb
Sep 13, 2023

Hi, I'm hoping someone could help me finalize my config, as I'm so close to getting the set up I want, but there's something I don't have quite right. I'll explain my set up below.

I',m running Home Assistant in a VM on Proxmos, and Frigate in an LXC. I've had Frigate set up for about two months now, with a total of 4 Reolink cameras, where everything generally worked great. A couple of weeks ago, I found that it was possible to add 2-way audio via the HA Frigate Lovelace card. I got this all set up, and it seems to work fine except for with the doorbell. I've since found with lots of testing (and as is mentioned in the HA Reolink integration docs), that some Reolink cameras don't like broadcasting multiple streams, as it can lead to dropouts. I've found that with the Reolink doorbell, if I want the HA integration to work, then I need the https port open, and if I want the 2-way audio via the Frigate Lovelace card, then I need the rtsp port open. But when these are open together, I get dropouts in Frigate regularly. These problems are only with the doorbell.

I've now figured out with the help of @NickM-27 (thanks), that I could use the https stream feed, and the rtsp together in the Frigate config, then in HA, disable all stream entities, and this seems to have stopped the dropouts in Frigate. But, I've now lost the 2-way audio in the Lovelace card on the doorbell.

Is this a Frigate config issue, or a Lovelace card config issue? I was hoping someone could look at my Frigate config, and let me know if it looks correct.

mqtt:
  host: 192.168.x.xxx
  user: xxx
  password: xxx
  
detectors:
  coral:
    type: edgetpu
    device: usb

go2rtc:
  streams:
    front_door:
      - http://192.168.x.xxx/flv?port=1935&app=bcs&stream=channel0_ext.bcs&user=xxx&password=xxx!
      #- rtsp://xxx:xxx!@192.168.x.xxx:554/h264Preview_01_sub
      - ffmpeg:rtsp://xxx:xxx!@192.168.x.xxx:554/h264Preview_01_sub#audio=pcm#audio=volume
    kitchen:
      - rtsp://xxx:xxx!@192.168.x.xxx:554/h264Preview_01_sub
      - ffmpeg:xxx:xxx!@192.168.x.xxx:554/h264Preview_01_sub#audio=pcm#audio=volume
    garage_cam:
      - rtsp://xxx:xxx!@192.168.x.xxx:554/h264Preview_01_sub
      - ffmpeg:xxx:xxx!@192.168.x.xxx:554/h264Preview_01_sub#audio=pcm#audio=volume
    battery_cam:
      - rtsp://xxx:xxx@192.168.x.xxx:8554/battery_cam_1
      - ffmpeg:rtsp://xxx:xxx@192.168.x.xxx:8554/battery_cam_1#audio=pcm#audio=volume


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

cameras:
  front_door:
    enabled: True
    ffmpeg:
      inputs:
        # High Res Stream
        - path: rtsp://xxx:xxx!@192.168.x.xxx:554/h264Preview_01_main
          roles:
            - record
        # Low Res Stream
        #- path: rtsp://192.168.x.xxx:8554/front_door
        - path: rtsp://xxx:xxx!@192.168.x.xxx:554/h264Preview_01_sub
          #input_args: preset-rtsp-restream
          roles:
            - detect
    detect:
      width: 640
      height: 480
      fps: 10
    objects:
      track:
        - person
        - cat
        - bird
    rtmp:
      enabled: false
    snapshots:
      enabled: true
    record:
      enabled: true
      retain:
        days: 5
      events:
        retain:
          default: 10
    motion:
      mask:
        - 0,0,640,0,640,74,0,76
  kitchen:
    enabled: True
    ffmpeg:
      inputs:
        # High Res Stream
        - path: rtsp://xxx:xxx!@192.168.x.xxx:554/h264Preview_01_main
          roles:
            - record
        # Low Res Stream
        - path: rtsp://192.168.x.xxx:8554/kitchen
          input_args: preset-rtsp-restream
          roles:
            - detect
    detect:
      width: 640
      height: 360
      fps: 7
    objects:
      track:
        - person
        - cat
        - bird
    snapshots:
      enabled: true
    record:
      enabled: true
      retain:
        days: 5
      events:
        retain:
          default: 10

  garage_cam:
    enabled: True
    ffmpeg:
      inputs:
        # High Res Stream
        - path: rtsp://xxx:xxx!@192.168.x.xxx:554/h264Preview_01_sub
          roles:
            - record
        # Low Res Stream
        - path: rtsp://192.168.x.xxx:8554/garage_cam
          input_args: preset-rtsp-restream
          roles:
            - detect
    detect:
      width: 640
      height: 360
      fps: 7
    objects:
      track:
        - person
        - cat
        - car
    snapshots:
      enabled: true
    record:
      enabled: true
      retain:
        days: 5
      events:
        retain:
          default: 10

  battery_cam:
    enabled: True
    ffmpeg:
      inputs:
        # High Res Stream
        - path: rtsp://xxx:xxx@192.168.x.xxx:8554/battery_cam_1
          input_args: preset-rtsp-restream
          roles:
            - record
            - detect
    detect:
      width: 640
      height: 360
      fps: 5
    objects:
      track:
        - person
        - cat
    snapshots:
      enabled: true
    record:
      enabled: true
      retain:
        days: 5
      events:
        retain:
          default: 10

My HA Lovelace card config looks as follows.

type: custom:frigate-card
cameras:
  - camera_entity: camera.front_door
    live_provider: go2rtc
    go2rtc:
      modes:
        - webrtc
      stream: front_door
    triggers:
      occupancy: false
  - camera_entity: camera.kitchen
    live_provider: go2rtc
    go2rtc:
      modes:
        - webrtc
  - camera_entity: camera.battery_cam
    live_provider: go2rtc
    go2rtc:
      modes:
        - webrtc
  - camera_entity: camera.garage_cam
    live_provider: go2rtc
    go2rtc:
      modes:
        - webrtc
menu:
  buttons:
    microphone:
      enabled: true
      alignment: opposing
      type: toggle
      priority: 50
    timeline:
      enabled: false
    cameras:
      enabled: false
    frigate:
      enabled: false
    download:
      enabled: false
    media_player:
      enabled: false
    mute:
      enabled: true
      alignment: opposing
    camera_ui:
      enabled: false
  style: outside
  position: bottom
  button_size: 50
live:
  controls:
    thumbnails:
      mode: none
  auto_mute: all
  preload: true
  transition_effect: slide
dimensions: {}
media_gallery:
  controls:
    thumbnails:
      size: 140
      show_favorite_control: false
      show_timeline_control: false
      show_download_control: false
    filter:
      mode: none
performance:
  profile: high

Any help would be greatly appreciated, as I'm still learning about how to set up Frigate.

NickM-27 · 2023-09-13T18:26:50Z

NickM-27
Sep 13, 2023
Collaborator Sponsor

This is not what I was suggesting. You should still be using the go2rtc restream for the cameras section.

All you need to do in go2rtc for two way talk is

    front_door:
      - "ffmpeg:http://192.168.x.xxx/flv?port=1935&app=bcs&stream=channel0_ext.bcs&user=xxx&password=xxx!#video=copy#audio=copy#audio=opus"
      - rtsp://xxx:xxx!@192.168.x.xxx:554/h264Preview_01_sub

that way it will only use rtsp when necessary

20 replies

NickM-27 Sep 13, 2023
Collaborator Sponsor

what version of go2rtc are you running?

celodnb Sep 13, 2023
Author

1.5.0

The 2-way audio works fine if I only use rtsp streams in my config.

NickM-27 Sep 13, 2023
Collaborator Sponsor

I'd suggest updating go2rtc, if the rtsp streams work as expected without dropping a connection that is fine, reolinks generally have problems when running with the rtsp streams

celodnb Sep 13, 2023
Author

Thanks, I'll try and update and see what happens.

For now, I'll just use the rtsp streams in my config, and think of an alternative to the HA Reolink integration (I only actually need it for the visitor entity).

Thanks for all your help, much appreciated :-)

celodnb Sep 16, 2023
Author

Hi Nick, just a quick follow up. I updated go2rtc to 1.7.1, and tried to use the http stream in my config as you described, but still couldn't get the speaker audio to work. However, I've used purely the rtsp streams for a few days now, and still have the HA Reolink integration active (streams deactivated), and I've not had any dropouts or errors. Thanks again for your help and patience, greatly appreciated.

PRS1192 · 2023-10-28T13:44:14Z

PRS1192
Oct 28, 2023

This is not what I was suggesting. You should still be using the go2rtc restream for the cameras section.

All you need to do in go2rtc for two way talk is
    front_door:
      - "ffmpeg:http://192.168.x.xxx/flv?port=1935&app=bcs&stream=channel0_ext.bcs&user=xxx&password=xxx!#video=copy#audio=copy#audio=opus"
      - rtsp://xxx:xxx!@192.168.x.xxx:554/h264Preview_01_sub
that way it will only use rtsp when necessary

I tried using this as . Sometimes the 2-way audio works and other times it freezes the stream and gives an error message stating "No frames have been detected".

If I type the following into a web browser it successfully takes me to the camera stream but, I do have to login first with my Reolink password.

"ffmpeg:http://192.168.x.xxx/flv?port=1935&app=bcs&stream=channel0_ext.bcs&user=xxx&password=xxx!#video=copy#audio=copy#audio=opus"

I just can't get any stability when trying the 2 way audio functionality on the Frigate card within Home Assistant though. And also the ffmpeg part when I include it in the config under the go2rtc stream on it's own (i.e. without the rtsp line) also returns the same error message about no frames being detected.

I'm quite new to all of this (and coding in general) but have tried to follow documentation and threads on GitHub. I think I will just stick without the 2 way audio as I have managed to get everything else working fine which I'm so grateful for. You creators of Frigate have done a fantastic job!!

0 replies

mvn23 · 2023-12-12T21:52:13Z

mvn23
Dec 12, 2023

Better late than never I guess, I had to change http:// to https:// for the stream to show up...

0 replies

rysm83 · 2024-02-02T17:07:48Z

rysm83
Feb 2, 2024

Do you have to change the http port to 1935 in the camera? All my Reolink cameras have port 80 for http. I have been trying to get http address working on all of them and nothing is working.
My door bell is the same and to make things more interesting is that if I use the RTSP address for the door bell it only works while to app on my phone is up an streaming the feed. as soon as I close the app the camera cuts out.
I have been using Frigate for a while and like it now I'm hesitant and maybe thinking of alternative or just get a DVR and record 24/7 and forget the rest.
This address does not work even when entering in my camera IP and camera user name and password
"ffmpeg:http://192.168.x.xxx/flv?port=1935&app=bcs&stream=channel0_ext.bcs&user=xxx&password=xxx!#video=copy#audio=copy#audio=opus"

1 reply

sapstar Feb 21, 2024

you need to enable rtmp in reolink web ui. Then change the url to https if you don't have http enabled. Or you can also enable http in the settings.

soonerfan237 · 2024-02-25T17:39:23Z

soonerfan237
Feb 25, 2024

I'm trying to accomplish the same thing, but I can't seem to get the microphone button to appear in the Frigate card at all.

Here are my server settings in the reolink doorbell:

Here is my config:


mqtt:
  host: core-mosquitto
  user:
    xxx
  password:
    xxxx

go2rtc:
  streams:
    doorbell_camera_main:
      - "ffmpeg:http://xxx.xxx.xx.xxx/flv?port=1935&app=bcs&stream=channel0_ext.bcs&user=xxx&password=xxxx!#video=copy#audio=copy#audio=opus"
      - rtsp://xxx:xxx@xxx.xxx.xx.xxx:554/h264Preview_01_main
  ffmpeg:
    bin: ffmpeg
    volume: "-af \"volume=30dB\""
    

cameras:
  doorbell_camera:
    ffmpeg:
      inputs:
        - path: rtsp://127.0.0.1:8554/doorbell_camera_main
          input_args: preset-rtsp-restream
          roles:
            - record
        - path: rtsp://127.0.0.1:8554/doorbell_camera_sub
          input_args: preset-rtsp-restream
          roles:
            - detect
      output_args:
        record: preset-record-generic-audio-aac
    live:
      stream_name: doorbell_camera_main
    detect:
      width: 1280
      height: 720
      fps: 5
    record:
      enabled: True
      retain:
        days: 2 
        mode: active_objects
    snapshots:
      enabled: True
      retain:
        default: 14
 
objects:
  track:
    - person
    - dog
  filters:
    person:
      min_score: 0.8
    dog:
      min_score: 0.75

detectors:
  coral:
    type: edgetpu
    device: usb

1 reply

supermarkert Mar 7, 2024

FYI, you don't have a "doorbell_camera_sub" configured in your go2rtc section. So that Camera item is being ignored.
And also, the "ext" stream is the substream. Check my link below for working streams.

That being said, see my comment here for what works for me to get 2-way audio working in the card with my Doorbell.

soonerfan237 · 2024-03-07T20:07:03Z

soonerfan237
Mar 7, 2024

@supermarkert I had a doorbell_camera_sub configured in go2rtc, but accidentally excluded it when copying over the config. I also fixed my config to use "main" instead of "ext" in my main. Here are the updated configs.

go2rtc section

go2rtc:
  streams:
    doorbell_camera_main:
      - "ffmpeg:http://xxx.xxx.xx.xxx/flv?port=1935&app=bcs&stream=channel0_main.bcs&user=xxxx&password=xxxx#video=copy#audio=copy#audio=opus"
      - rtsp://xxxx:xxxx@xxx.xxx.xx.xxx:554/h264Preview_01_main
    doorbell_camera_sub:
      - "ffmpeg:http://xxx.xxx.xx.xxx/flv?port=1935&app=bcs&stream=channel0_ext.bcs&user=xxxx&password=xxxx"
      - rtsp://xxxx:xxxx@xxx.xxx.xx.xxx:554/h264Preview_01_sub
  ffmpeg:
    bin: ffmpeg
    volume: "-af \"volume=30dB\""

I noticed that you included this in your go2rtc config. Is this necessary?

webrtc:
    candidates:
    - 192.168.40.5:8555
    - stun:8555

cameras section

cameras:
  doorbell_camera:
    ffmpeg:
      inputs:
        - path: rtsp://xxx.x.x.x:8554/doorbell_camera_main
          input_args: preset-rtsp-restream
          roles:
            - record
        - path: rtsp://xxx.x.x.x:8554/doorbell_camera_sub
          input_args: preset-rtsp-restream
          roles:
            - detect
      output_args:
        record: preset-record-generic-audio-aac
    live:
      stream_name: doorbell_camera_main

lovelace card

type: custom:frigate-card
cameras:
  - camera_entity: camera.doorbell_camera
    engine: frigate
    live_provider: go2rtc
    icon: mdi:doorbell-video
    go2rtc:
      modes:
        - webrtc
live:
  auto_mute: all
  transition_effect: slide
  microphone:
    always_connected: true
  controls:
    builtin: true
    title:
      mode: none
menu:
  buttons:
    microphone:
      enabled: true
    frigate:
      enabled: false
    cameras:
      enabled: false
    substreams:
      enabled: false
    live:
      enabled: false
    clips:
      enabled: false
    snapshots:
      enabled: false
    download:
      enabled: false
    camera_ui:
      enabled: false
    timeline:
      enabled: false
  style: outside

I still don't see a microphone button showing up on my lovelace card. However, I have noticed that when I access HA through nabu casa, my Chrome reports that the tab is using my microphone. However, without the microphone button showing up I don't actually hear anything through the doorbell. My microphone is not getting used when I access through http://homeassistant.local which makes sense.

25 replies

soonerfan237 Mar 22, 2024

@supermarkert Looks like the same user that reported the issue with Nabu Casa, posted this same thread on reddit. He got it working after forwarding port 8555, which I'm already doing. So I guess that's also not the issue.

soonerfan237 Mar 23, 2024

@supermarkert I just got this working! Thanks for all your help along the way!

In case anyone reads through this thread in the future, firmware version 3.0.0.3215 broke two way talk via rtsp. Downgrading the firmware to 3.0.0.2033 fixed the issue. I used this unofficial archive to get the old firmware version:
https://github.com/AT0myks/reolink-fw-archive/tree/main

Additional details about my config and settings can be found in this other discussion:
#10619

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Config help for Reolink doorbell (Frigate + HA integration at the same time) #7791

{{title}}

Replies: 6 comments 47 replies

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{editor}}'s edit

{{editor}}'s edit

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{editor}}'s edit

{{editor}}'s edit

{{title}}

{{editor}}'s edit

{{editor}}'s edit

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

Select a reply

Config help for Reolink doorbell (Frigate + HA integration at the same time) #7791

Replies: 6 comments · 47 replies

NickM-27 Sep 13, 2023 Collaborator Sponsor

NickM-27 Sep 13, 2023 Collaborator Sponsor

celodnb Sep 13, 2023 Author

NickM-27 Sep 13, 2023 Collaborator Sponsor

celodnb Sep 13, 2023 Author

celodnb Sep 16, 2023 Author

Replies: 6 comments 47 replies

NickM-27
Sep 13, 2023
Collaborator Sponsor

NickM-27 Sep 13, 2023
Collaborator Sponsor

celodnb Sep 13, 2023
Author

NickM-27 Sep 13, 2023
Collaborator Sponsor

celodnb Sep 13, 2023
Author

celodnb Sep 16, 2023
Author