Warning to anyone reading this thread now: I have attempted the firmware rollback twice now, and it bricked both cameras. New cameras might not be compatible.
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?