Reolink Doorbell Two Way Talk [Camera Support]: #18748
-
Describe the problem you are havingI'm sure I have made some configuration error or missed something in the documentation. I have tried to resolve my Relink doorbell, which has two-way audio, but I keep getting the message. Two-way talk is unavailable for this stream Version16.0.2 What browser(s) are you using?No response Frigate config filego2rtc:
streams:
reolink_doorbell:
- "ffmpeg:http://10.0.1.14/flv?port=1935&app=bcs&stream=channel0_main.bcs&user=.....&password=......#video=copy#audio=copy#audio=opus"
- rtsp://10.0.1.14/Preview_01_sub
reolink_doorbell_sub:
- "ffmpeg:http://10.0.1.14/flv?port=1935&app=bcs&stream=channel0_ext.bcs&user=....&password=......"
webrtc:
candidates:
- 10.0.1.217:8555
- 100.122.143.72:8555
- stun:8555
cameras :
reolink_doorbell:
ffmpeg:
inputs:
- path: rtsp://127.0.0.1:8554/reolink_doorbell_sub
input_args: preset-rtsp-restream
roles:
- detect
- path: rtsp://127.0.0.1:8554/reolink_doorbell
input_args: preset-rtsp-restream
roles:
- record
- audioRelevant Frigate log outputinfo | 2025-06-16 10:33:48 | startup | Preparing new go2rtc config...
info | 2025-06-16 10:33:48 | startup | Starting go2rtc...
info | 2025-06-16 10:33:48 | startup | go2rtc platform=linux/amd64 revision=fa580c5 version=1.9.9
info | 2025-06-16 10:33:48 | startup | config path=/dev/shm/go2rtc.yaml
info | 2025-06-16 10:33:48 | api | listen addr=:1984
info | 2025-06-16 10:33:48 | rtsp | listen addr=:8554
info | 2025-06-16 10:33:48 | webrtc | listen addr=:8555
info | 2025-06-16 10:33:58 | |Relevant go2rtc log outputinfo | 2025-06-16 10:33:48 | startup | Preparing new go2rtc config...
info | 2025-06-16 10:33:48 | startup | Starting go2rtc...
info | 2025-06-16 10:33:48 | startup | go2rtc platform=linux/amd64 revision=fa580c5 version=1.9.9
info | 2025-06-16 10:33:48 | startup | config path=/dev/shm/go2rtc.yaml
info | 2025-06-16 10:33:48 | api | listen addr=:1984
info | 2025-06-16 10:33:48 | rtsp | listen addr=:8554
info | 2025-06-16 10:33:48 | webrtc | listen addr=:8555
info | 2025-06-16 10:33:58 | |FFprobe output from your cameraInput #0, rtsp, from 'rtsp://127.0.0.1:8554/reolink_doorbell':
Metadata:
title : go2rtc/1.9.9
Duration: N/A, start: 0.000000, bitrate: N/A
Stream #0:0: Video: h264 (High), yuv420p(progressive), 2560x1920, 20 tbr, 90k tbn
Stream #0:1: Audio: aac (LC), 16000 Hz, mono, fltp
matt@greenai:~/frigate$Frigate statsNo response Operating systemDebian Install methodDocker Compose Object DetectorCoral Network connectionWired Camera make and modelReo Link Doorbell PoE Screenshots of the Frigate UI's System metrics pages
Any other information that may be helpfulNo response |
Beta Was this translation helpful? Give feedback.
Replies: 8 comments 19 replies
-
|
Difficult to help without complete log, config and docker-compose file. How do you access the Stream (https)? |
Beta Was this translation helpful? Give feedback.
-
|
Frigate Logs |
Beta Was this translation helpful? Give feedback.
-
|
Nginx Logs |
Beta Was this translation helpful? Give feedback.
-
|
Go2rtc Logs |
Beta Was this translation helpful? Give feedback.
-
|
Docker Compose services: |
Beta Was this translation helpful? Give feedback.
-
|
Here is my full config minus additional cameras that are working. My doorbell is the only one that uses go2rtc |
Beta Was this translation helpful? Give feedback.
-
|
View from camera showing the note on 2 way talking not being enabled |
Beta Was this translation helpful? Give feedback.
-
|
See the official documentation on two-way talk: https://docs.frigate.video/configuration/live/#two-way-talk You need to be accessing Frigate securely on port 8971. It seems like this is your missing step since you don't have the port enabled in your docker compose file. |
Beta Was this translation helpful? Give feedback.
-
|
V3.0.0.4662_2503122271 |
Beta Was this translation helpful? Give feedback.
-
|
So I'm having a similar issue -> I notice that on my producers I only have I assume if I can get |
Beta Was this translation helpful? Give feedback.
-
|
@jeeftor, there are several go2rtc discussions that point to having a specific firmware where you have to ask Reolink to get it because it is an older version.... I do not suggest trying to chat with them it took me three hours for them to tell me that they would send it to senior support and email me back in 24 hrs. |
Beta Was this translation helpful? Give feedback.
-
|
Okay I got it here is an example of my go2rec config for a working Reolink and a working Amcrest. streams:
|
Beta Was this translation helpful? Give feedback.
-
|
Here is my camera Info for the reolink @ |
Beta Was this translation helpful? Give feedback.
-
I think you mean: streams:
amcrest_doorbell:
- rtsp://username:[email protected]:554/cam/realmonitor?channel=1&subtype=0#backchannel=1 - ffmpeg:doorbell#audio=aac
- ffmpeg:doorbell_mic#audio=pcma
amcrest_doorbell_sub:
- rtsp://username:[email protected]:554/cam/realmonitor?channel=1&subtype=1
- ffmpeg:doorbell_sub#audio=aac
your_reolink_doorbell:
- rtsp://username:[email protected]:554/h264Preview_01_main#backchannel=1
- rtsp://10.0.1.14/Preview_01_sub
your_reolink_doorbell_sub:
- ffmpeg:http://10.0.1.14/flv?port=1935&app=bcs&stream=channel0_ext.bcs&user=user&password=password
webrtc:
candidates:
- INternalfirgateIP:8555
- tailscaleIP:8555
- stun:8555
restream:
enabled: true
streams:
- video
- audio
- microphoneHow are you accessing frigate? By IP or Reverse Proxy? Which port (5000 or the authenticated port?) I'm thinking we have to go via a reverse proxy to handle HTTPs is that correct? |
Beta Was this translation helpful? Give feedback.
-
|
@jeeftor yes I talk through the HA app using the proxy frigate addon. I did mess around with my set up and found something that works even better. I use three streams now two that use the recommended settings for recording and detection and then one that is just for two way talk. go2rtc: cameras: reolink_doorbell: |
Beta Was this translation helpful? Give feedback.
-
|
I have a wifi doorbell - and I'm not sure I see the advantage of using the I'm assuming your 3 stun address are:
fyi if you wrap your "YAML" in You will get formatted yaml
yaml:
- formatted(it will make that blurb above MUCH easier to read :) ... I'll give your settings a go now) |
Beta Was this translation helpful? Give feedback.
Okay I got it here is an example of my go2rec config for a working Reolink and a working Amcrest.
streams:
amcrest_doorbell:
- rtsp://username:[email protected]:554/cam/realmonitor?channel=1&subtype=0#backchannel=1
- ffmpeg:doorbell#audio=aac
- ffmpeg:doorbell_mic#audio=pcma
amcrest_doorbell_sub:
- rtsp://username:[email protected]:554/cam/realmonitor?channel=1&subtype=1
- ffmpeg:doorbell_sub#audio=aac
your_reolink_doorbell:
- rtsp://username:[email protected]:554/h264Preview_01_main#backchannel=1
- rtsp://10.0.1.14/Preview_01_sub
your_reolink_doorbell_sub:
- ffmpeg:http://10.0.1.14/flv?port=1935&app=bcs&stream=channel0_ext.bcs&user=user&password=password
webrtc:
candidates: