HomeAssistant and Reolink Doorbell POE

Third party integrations
210

Are there any differences between the custom integration vs official HA integration?

212

Hello guys, Iā€™m testing this doorbell and Iā€™m quite disappointed.

First of all I noticed that Alexa fails a lot of time while opening the stream. So I loose a lot of time to answer at the doorbell.

The second point is that: if I use WebRTC to integrate the 2wayaudio, I cannot talk via the Reolink app. It fails ā€œopening the conversationā€.

Do you have the same behavior?

Thanks

213

That would be a configuration error

214

Can you help me going deeper in this configuration error?

215

If you share the go2rtc config that would be good to see

216

Sure:

streams:
  campanello:
    - ffmpeg:rtsp://admin:[email protected]:554/h264Preview_01_sub#audio=pcm#audio=volume
    - rtsp://admin:[email protected]:554/h264Preview_01_sub

ffmpeg:
  bin: ffmpeg
  volume: "-af \"volume=30dB\""    
    
webrtc:
  candidates:
    - stun:8555
217

Iā€™d suggest Camera Specific Configurations | Frigate

219

Can someone share their WORKING 2-way audio for:

  1. Frigate configuration.yaml settings for:
    a) go2rtc settings (include webrtc under streams and do you have ffmpeg settings)
    b) camera section corresponding to the streams in the go2rtc section
  2. frigate-card settings for the cameras section

Thanks

2 Likes
220

See Camera Specific Configurations | Frigate

221

The following mostly works for me, aside from occasional ffmepg errors that require me to restart Frigate that may be due to my own hwaccel issues that I omitted:

go2rtc:
  streams:
    reolink_doorbell_camera_main: 
      - "rtsp://username:password@ip:554/h264Preview_01_main"
      - "ffmpeg:reolink_doorbell_camera_main#audio=opus"
    reolink_doorbell_camera_sub: 
      - "rtsp://username:password@ip:554/h264Preview_01_sub"
      - "ffmpeg:reolink_doorbell_camera_sub#audio=opus"

cameras:
  reolink_doorbell:
    ffmpeg:
      output_args:
        record: preset-record-generic-audio-copy
      inputs:
        - path: rtsp://127.0.0.1:8554/reolink_doorbell_camera_main
          input_args: preset-rtsp-restream
          roles:
            - record
        - path: rtsp://127.0.0.1:8554/reolink_doorbell_camera_sub
          input_args: preset-rtsp-restream
          roles:
            - detect
    live:
      stream_name: reolink_doorbell_camera_sub

type: custom:frigate-card
cameras:
  - camera_entity: camera.doorbell
    live_provider: go2rtc
    go2rtc:
      modes:
        - webrtc
      stream: reolink_doorbell_camera_sub
menu:
  buttons:
    microphone:
      enabled: true
      type: toggle
live:
  microphone:
    always_connected: false

Important items:

  1. ffmpeg with #audio=opus and without #audio=volume, maybe #audio=copy, and some other options that broke 2way
  2. Defining stream or else 2way doesnā€™t work
5 Likes
222

Whoop whoop, finally got it working. Only thing which was different compared to my orignial config was the output args in the camera section. Have tried lots and lots of configs and this one works. Love this!!

1 Like
223

Itā€™s already been mentioned before, but Iā€™ll say it too.

Use Scrypted. Itā€™s the only way Iā€™ve ever had reliable camera feeds in Home Assistant. Including with the Reolink PoE doorbell.

224

Will Scrypted work with a ReoLink TrackMix to play sound or 2-way?

225

I donā€™t know, but it would be worth trying the two different plugins that support those cameras. In my case, for the doorbell, Iā€™m using Scryptedā€™s ONVIF plugin (where I can use 2-way audio) and for the other ReoLink cameras Iā€™m using its Reolink plugin.

You can ask Reolink if that camera supports ONVIF-T which is needed for 2-way audio over ONVIF.

1 Like
226

Hero!

I never got it to work before and now it works perfectly!

227

I switched to the HTTP stream as detailed in the Frigate documentation and it has made my connection very stable:
Camera Specific Configurations

Reolink Doorbellā€‹

ā€œThe reolink doorbell supports 2-way audio via go2rtc and other applications. It is important that the http-flv stream is still used for stability, a secondary rtsp stream can be added that will be using for the two way audio only.ā€

go2rtc:
  streams:
    your_reolink_doorbell:
      - "ffmpeg:http://reolink_ip/flv?port=1935&app=bcs&stream=channel0_main.bcs&user=username&password=password#video=copy#audio=copy#audio=opus"
      - rtsp://reolink_ip/Preview_01_sub
    your_reolink_doorbell_sub:
      - "ffmpeg:http://reolink_ip/flv?port=1935&app=bcs&stream=channel0_ext.bcs&user=username&password=password"
5 Likes
228

For me this worked to get the microphone button to show up but iā€™m still having troubles getting the mic to work. I can push the button but it still doesnā€™t work. Iā€™m using home assistant companion app on a local ip using http and not https. Does this solution work without https for you guys or only trough https?

For myself it would be enough if only the companion app would work. Not to concerned if it wouldnā€™t work using a browser. Offcourse I can get home assistant to get a https adress but that would mean opening my home assistant server to the outside world and that in my usecase has no use.

229

HTTPS is required!

230

You have 2way audio working with this config? What does your custom:frigate-card conf look like please?

231

Whatā€™s the best way to get the camera feed to pop-up in PIP mode on Android (Shield) TV when the doorbell is pressed?

Iā€™m using Frigate and Scripted on Proxmox integrated with HA.

Thanks