2 Way audio Intercom for Reolink doorbell made easy

Share your Projects! Dashboards & Frontend
,
45

Yes, or at least it’s not creating them with my config.
You are right, looks like the NAT traverse might be another issue. I can see the stream when running in docker with host net access. I will dig more and update here if I find a solution, thanks.

46

OK, it was way easier than I thought. I enabled the integrated go2rtc web UI in HA config and added the doorbell as generic camera in integration panel. The go2rtc now shows:
image
…and I have the entity.
The doorbell now light’s up, but I can’t hear myself. I’m accessing HA via domain with Let’s Encrypt certificate. Any idea what’s wrong?

Edit: modifying the go2rtc to include #audio=opus#audio=copy didn’t help.

47

That I would say is an issue with ffmpeg. Check what the original post to make sure the ffmpeg command is the exactly the same. I see you have a bad query parameter at the end.

48

browser-mod is only used to create the popups. This is using the default picture card (for the first popup without 2way audio) and the webrtc card (for the second popup with 2 way audio).
I’m uncertain if the card you shared provides 2 way audio but you could modify the existing blueprint code to use it.

2 Likes
49

Ok, so as @victorigualada suggested: my issue was networking. HA is running in a docker with limited exposed ports. go2rtc need to be run with a big range of UDP ports exposed, or with network_mode: host.
The only solution I was able to find is to run go2rtc in separate docker with `network_mode: host and with this in HA config:

go2rtc:
  url: http://172.17.0.1:1984

This go2rtc can be standalone or from frigate. With standalone, it’s not possible to use custom:advanced-camera-card as it’s not creating entities, but one can still use custom:webrtc-camera like in this blueprint. Just remove the webrtc integration and set the correct go2rtc’s ip when adding it back again.
To make it work outside my network I also had to forward the WebRTC port (8555) to my server and this to go2rtc config:

  webrtc:
    candidates:
      - stun:8555  # if you have dynamic public IP-address

The blueprint’s custom:webrtc-camera defaulted to MSE mode, so I had to add mode: webrtc. Thanks @victorigualada :slight_smile:

1 Like
50

Hi everyone,

I’m not an expert, but I recently bought a Reolink WiFi doorbell after reading this post. It seemed like the perfect solution I had been looking for years.

After spending a whole day working on the integration, I was able to see the video and receive a popup notification on my Home Assistant device when the doorbell rings, along with hearing what is said on the doorbell. However, I couldn’t find any way to talk back from my device to the doorbell.

I tried several configurations, and after all that, my good friend ChatGPT explained the following to me:
"This doorbell does NOT support two-way audio (talkback) via RTSP, ONVIF, or HTTP.
You can only send audio to it using the official Reolink app or the Reolink Client for Windows.

This is because Reolink uses a proprietary protocol for the audio return channel (talkback).

Although it exposes an RTSP stream for incoming video and audio, it does not provide an RTSP channel for outgoing audio."

If anyone has managed to talk to the doorbell, a detailed explanation of how it was done would be greatly appreciated.

51

That seems to me like LLM alucination.
Is the device you are showing the popup on connected to the HA instance through HTTPS? That’s required in order to use the device’s microphone.

52

Established a connection through Nabu Casa.

53

Ok, I managed to get two-way audio working with the following configuration in go2rtc, but the delay is high and the audio cuts out after the first word.

Well, ChatGPT was partly wrong, it is possible to send audio to the doorbell, but the results are still not good enough for me to install the device at home.

54

I’d suggest not trust any LLM with information analysis at that level.
About your configuration:

  1. You should be able to use ffmpeg:camera.2way_audio_doorbell#audio=opus#audio=copy where camera.2way_audio_doorbell is the name of your stream as in the example.
  2. You are not using audio=copy, which tells ffmpeg to preserve the original audio without encoding it, which is faster and might be the reason why you see experience the delay. Mainly if you have a slow server like a RPi.
  3. I see you have a WiFi doorbell, so ensure you have a good connection to it.

ChatGPT was not just “partly wrong”, it was 100% wrong about all the afirmations you posted. I would consider not trusting it for anything you are not ready to manually verify.

55

Has anybody been able to get this working with a Unifi Protect G4 Doorbell? I’m able to view the feed but when accepting the call I get a configuration error on the second popup

image
image1222×1248 26 KB

Thanks!

56

This was reported already by another issue, but he stopped responding so no way to dive deeper on the issue.
I would say that this is a problem with the go2rtc stream. If you are using Docker you should check a few comments above on how @RipperChile fixed it.
If you are not, check that the name of the stream names matches the one in the blueprint.