I figured this might be the case. I just bought a white doorbell and noticed the hardware id and firmware it has is just slightly different from what I’ve been seeing. I am also still running into issue with using the Mic through the Frigate card.
Hi,
Please note that this is the first time for me posting on the HA community page and the second time on a Github like site. Excuse me if I’m not aware of any rules.
I just bought a Reolink doorbell. (PoE White version) with the latest firmware.
At first it did’nt work, however I did read your comments and checked if other may have the same issues.
I’ve found the following github thread: https://github.com/koush/scrypted/discussions/1115 and got it working again with the firmware posted there and the following code:
Firmware PoE Only!
Black
https://support-d.reolink.com/attachments/token/u6B3AlhKl9rc1S2Y141mNP5f7/?name=DB_566128M5MP_P.3308_2407041184.Reolink-Video-Doorbell-PoE.OV05A10.5MP.REOLINK.pak
Go2RTC config
streams:
camera.reolink_doorbell:
- "ffmpeg:https://192.168.0.0/flv?port=1935&app=bcs&stream=channel0_main.bcs&user=admin&password=password#video=copy#audio=copy#audio=opus"
- rtsp://admin:[email protected]:554/h264Preview_01_sub
Custom card
type: custom:webrtc-camera
streams:
- url: camera.reolink_doorbell
mode: webrtc
media: video,audio,microphone
Please note as state above, when using the custom card, the mic is always on when the card is presented and auto reply messages over REST commands does not work with this FW, but using the HA intergration it still does.
Hope this can help any of you, currently having issues with the two way audio and latest fw. I’m sure this will also be of help for you that are using Frigate.
2 Likes
Here’s a link support sent me for my black wifi v2 model that got 2 way audio working in Frigate if anyone wants it
Reolink released new firmware publicly with the two way audio and some other fixes
v3.0.0.3308_2407315183 fixed auto reply messages over REST commands for me.
3 Likes
Could you paste a working frigate and hA card config please?
I keep seeing people mix between onvif HTTP, flv and rtsp
Thanks in advance
Only Onvif/RTSP support two way audio in go2rtc.
ONVIF is the standard and RTSP is the protocol. Http/FLV are the same stream and doesn’t support two way audio in go2rtc.
When you see other using the flv stream they also have the RTSP sub stream for just the mic.
Frigate docs mentions this
1 Like
This is the config that works for me
Frigate config:
cameras:
front_door_camera:
ffmpeg:
inputs:
- path: rtsp://127.0.0.1:8554/front_door_camera?video=copy&audio=aac
input_args: preset-rtsp-restream-low-latency
roles:
- record
- path: rtsp://127.0.0.1:8554/front_door_camera_sub?video=copy&audio=aac
input_args: preset-rtsp-restream-low-latency
roles:
- detect
- audio
Go2RTC config:
go2rtc:
streams:
front_door_camera:
- rtsp://{FRIGATE_RTSP_USER}:{FRIGATE_RTSP_PASSWORD}@192.168.86.11:554/Preview_01_main#backchannel=0
- rtsp://{FRIGATE_RTSP_USER}:{FRIGATE_RTSP_PASSWORD}@192.168.86.11:554/Preview_01_sub
- ffmpeg:front_door_camera#audio=opus#hardware
front_door_camera_sub:
- rtsp://{FRIGATE_RTSP_USER}:{FRIGATE_RTSP_PASSWORD}@192.168.86.11:554/Preview_01_sub
- ffmpeg:front_door_camera_sub#audio=opus#hardware
webrtc:
candidates:
- 192.168.86.32:8555
- stun:8555
Frigate card:
type: custom:frigate-card
cameras:
- camera_entity: camera.front_door_camera
live_provider: go2rtc
go2rtc:
modes:
- webrtc
stream: front_door_camera
menu:
buttons:
microphone:
enabled: true
type: toggle
1 Like
Hi,
Are you experiencing any delay?
From my computer and the HA companion app, I’m noticing a 3-second delay when I speak into my microphone to my doorbell. The sound from my doorbell is good with no delay.
Do you have any idea how I can solve this?
hey @qonfusion90 thanks a lot for the config, got it working with that! but the audio is only 1 way right? it doesnt take the audio from the HA-device so that you can speak with the guys in front of the door or am I doing something wrong?
Using the config I’ve shared two way audio should work.
Please note that the Mic only works when the connection is secured using an SSL cert. for example using LetsEncrypt!
ah, thanks @qonfusion90 for that hint. is https only for the browser needed or also for the HA android app? I thought that maybe the app does not need https so I can test if it works in general
Hey all,
got now HomeAssistant on HTTPS and microfone works now via the browser 
but is HTTPS also needed so that the microfone works on the HA-App? i read somewhere that microfone in general does not work with the HA-App? did someone get it running on the App?
besides that my HA-App does not work anymore after switching to HTTPS 
I’ve managed to get a media_player entity working on my Reolink Wifi doorbell- details here in case anyone needs them:
https://community.home-assistant.io/t/go2rtc-send-audio-to-cam/587937/29?u=redonionking
2 Likes
Hi all,
Did you manage to do it via the app or browser? I am struggling to get the mic working via the app. My connection is HTTPS, but still doesn’t work.
Hi @Lev,
Have you tried always using Preview_01_sub instead of Preview_01_main ?
I had the same problem and this solved it for me.
Hi all,
I recently bought a Reolink Doorbell (firmware version : v3.3.3.3308) which I have juste integrated into frigate.
The 2 ways audio works with this configuration (a more experienced friend gave it to me):
mqtt:
host: 192.168.1.193
port: 1883
user: mqtt
password: password
topic_prefix: frigate
stats_interval: 60
##########################################################################
go2rtc:
streams:
reolink:
- rtsp://admin:[email protected]:554/Preview_01_sub#backchannel=0
- rtsp://admin:[email protected]:554/Preview_01_sub
- ffmpeg:reolink#audio=opus#hardware
##########################################################################
cameras:
reolink:
ffmpeg:
inputs:
- path: rtsp://127.0.0.1:8554/reolink?video=copy&audio=copy&audio=opus
input_args: preset-rtsp-restream-low-latency
roles:
- audio
version: 0.14
However, like some of you, I have a latency issue: when i speak, I hear myself back (and loud engouh to be disturbing) about 2 ou 3 seconds later.
I’ve tried to change the configuration but so far I haven’t found anything that corrects the problem.
Do you have any ideas?
CPU usage can be as high as 80%, could this be the problem ? My configuration for HA : MINIS FORUM PC - Celeron N4020 (up to 2.8 GHz) 4 Go DDR4 / 64 Go eMMC
Any help is welcome
Hi @seheiahs ,
I am using the “Preview_01_sub”. And the strange thing is that I am able to use mic when using the iPad with HA app, but with Android tablet it doesn’t work.
Hi @Lev,
Indeed, it’s astonishing. For my part, I had this problem on my phone and my tablet.
Do you have the possibility to test on another more powerful Android tablet? Have you tested configuration file I posted (by adapting it to your context) ?
I have weird issues as well. On a Windows 10 PC I don’t see the microphone or audio mute buttons at all on the Frigate Card, and it’s the same on a Samsung Galaxy S20 Android phone. However, on a Samsung Galaxy Tablet I do see the microphone and audio mute buttons, but the microphone button does not appear to work. I have my config and some pictures below. Anyone have any ideas?
##########################################################################
cameras:
front_door_doorbell:
ffmpeg:
inputs:
- path: rtsp://127.0.0.1:8554/front_door_doorbell?video=copy&audio=aac
input_args: preset-rtsp-restream-low-latency
roles:
- record
- path: rtsp://127.0.0.1:8554/front_door_doorbell_sub?video=copy&audio=aac
input_args: preset-rtsp-restream-low-latency
roles:
- detect
- audio
##########################################################################
go2rtc:
streams:
front_door_doorbell:
- rtsp://<username>:<password>@<ip address>:554/Preview_01_main#backchannel=0
- ffmpeg:front_door_doorbell#audio=opus#hardware
front_door_doorbell_sub:
- rtsp://<username>:<password>@<ip address>:554/Preview_01_sub
- ffmpeg:front_door_doorbell_sub#audio=opus#hardware
webrtc:
candidates:
- <ip address>:8555
- stun:8555
version: 0.14
Here is my Frigate Card Configuration:
type: custom:frigate-card
cameras:
- camera_entity: camera.front_door_doorbell
live_provider: go2rtc
go2rtc:
modes:
- webrtc
menu:
buttons:
microphone:
enabled: true
alignment: matching
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: right
button_size: 66
alignment: right
live:
controls:
thumbnails:
mode: none
auto_mute: all
preload: false
dimensions: {}
media_gallery:
controls:
thumbnails:
size: 140
show_favorite_control: false
show_timeline_control: false
show_download_control: false
filter:
mode: none
Frigate Card on Samsung Galaxy Tablet shows microphone and audio button:
Frigate Card on Samsung Galaxy Tablet with microphone button on:
