[Camera Support]: Troubleshooting 2-way audio with Reolink Doorbell #10619
-
Describe the problem you are havingI haven't been able to get 2-way audio working with my Reolink Doorbell WiFi and at this point I'm unsure what else to try. It seems like I'm quite close. In my Frigate lovelace card, I get audio and video. And I see the microphone button. My browser and OS reports that it's using my microphone. When I click the button, it turns red as if its in use. However, when I speak into my microphone, no audio comes out of the doorbell speaker. This feature works via the official Reolink iOS app. go2rtc version 1.8.4 Here are my server settings in the Reolink Doorbell: I am accessing through https using Nabu Casa. I have not done anything else regarding https. I believe I have WebRTC set up correctly. I did the WebRTC extra configuration including forwarding port 8555 in my router for TCP and UDP. Here is my Frigate lovelace card config: Version2024.3.3 Frigate config filemqtt:
host: core-mosquitto
user:
xxxx
password:
xxxx
go2rtc:
streams:
doorbell_camera:
- ffmpeg:http://xxx.xxx.xx.xxx/flv?port=1935&app=bcs&stream=channel0_ext.bcs&user=xxxx&password=xxxx#video=copy#audio=copy#audio=opus
- rtsp://xxxx:[email protected]:554/h264Preview_01_sub
ffmpeg:
bin: ffmpeg
volume: "-af \"volume=30dB\""
webrtc:
candidates:
- http://xxx.xxx.xx.xxx:8555
- stun:8555
cameras:
doorbell_camera:
ffmpeg:
inputs:
- path: rtsp://127.0.0.1:8554/doorbell_camera
input_args: preset-rtsp-restream
roles:
- record
- detect
- audio
output_args:
record: preset-record-generic-audio-copy
detect:
width: 1280
height: 720
fps: 5
zones:
front_porch_zone:
coordinates: 0,87,0,264,0,720,1034,720,864,388,453,385,455,265
motion:
mask:
- 949,411,450,401,455,244,389,168,987,82
- 935,0,935,50,325,50,325,0
- 735,424,733,545,538,542,545,446
record:
enabled: True
events:
retain:
default: 7
mode: all
snapshots:
enabled: True
retain:
default: 14
audio:
enabled:
true
listen:
- bark
- speech
objects:
track:
- person
- dog
- car
filters:
person:
min_score: 0.8
dog:
min_score: 0.75
car:
min_score: 0.7
detectors:
coral:
type: edgetpu
device: usbRelevant log output2024-03-22 22:00:57.687202270 172.30.32.1 - - [22/Mar/2024:17:00:57 -0500] "GET /api/events?cameras=doorbell_camera&limit=50&include_thumbnails=0 HTTP/1.1" 200 25437 "-" "HomeAssistant/2024.3.3 aiohttp/3.9.3 Python/3.12" "-"
2024-03-22 22:00:59.452236781 172.30.32.1 - - [22/Mar/2024:17:00:59 -0500] "GET /live/mse/api/ws?src=doorbell_camera&authSig=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiI4NzA2YTdiNjFlOTA0YmIwYTMyMDlkMjE5NzczMDJiZSIsInBhdGgiOiIvYXBpL2ZyaWdhdGUvZnJpZ2F0ZS9tc2UvYXBpL3dzIiwicGFyYW1zIjpbWyJzcmMiLCJkb29yYmVsbF9jYW1lcmEiXV0sImlhdCI6MTcxMTE0NDg1NywiZXhwIjoxNzExMjMxMjU3fQ.QbC5cHtz5nd_OHEpnf0WO1AjNKY642cLzx5TfHVHJ1Y HTTP/1.1" 101 3141 "-" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/123.0.0.0 Safari/537.36" "127.0.0.1"
2024-03-22 22:00:59.456189914 172.30.32.1 - - [22/Mar/2024:17:00:59 -0500] "GET /live/mse/api/ws?src=doorbell_camera&authSig=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiI4NzA2YTdiNjFlOTA0YmIwYTMyMDlkMjE5NzczMDJiZSIsInBhdGgiOiIvYXBpL2ZyaWdhdGUvZnJpZ2F0ZS9tc2UvYXBpL3dzIiwicGFyYW1zIjpbWyJzcmMiLCJkb29yYmVsbF9jYW1lcmEiXV0sImlhdCI6MTcxMTE0NDg1NywiZXhwIjoxNzExMjMxMjU3fQ.QbC5cHtz5nd_OHEpnf0WO1AjNKY642cLzx5TfHVHJ1Y HTTP/1.1" 101 3144 "-" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/123.0.0.0 Safari/537.36" "127.0.0.1"FFprobe output from your cameraInput #0, rtsp, from 'rtsp://xxxx:[email protected]:554/h264Preview_01_sub':
Metadata:
title : Session streamed by "preview"
Duration: N/A, start: 0.000750, bitrate: N/A
Stream #0:0: Video: h264 (High), yuv420p(progressive), 640x480, 15 fps, 25 tbr, 90k tbn
Stream #0:1: Audio: aac (LC), 16000 Hz, mono, fltpFrigate statsNo response Operating systemHassOS Install methodHassOS Addon Coral versionUSB Network connectionWireless Camera make and modelReolink Doorbell WiFi Any other information that may be helpfulStream info from go2rtc while microphone is active: |
Beta Was this translation helpful? Give feedback.
Replies: 10 comments 34 replies
-
|
What firmware is your doorbell running |
Beta Was this translation helpful? Give feedback.
-
|
v3.0.0.3215_2401262240 |
Beta Was this translation helpful? Give feedback.
-
|
This firmware broke two way talk via rtsp |
Beta Was this translation helpful? Give feedback.
-
|
Which firmware version do I need? |
Beta Was this translation helpful? Give feedback.
-
|
A user said the August version works |
Beta Was this translation helpful? Give feedback.
-
|
It works now! Thank you! I downgraded to v.3.0.0.2033 using this unofficial archive: |
Beta Was this translation helpful? Give feedback.
-
|
Hi, thanks for this detailed troubleshooting and the highlighted solution! I had exactly the same issue, with Firmware Version: v3.0.0.3215_2401262241, and the downlgrade solve it (Firmware Version: v3.0.0.2033_23041302). Thanks again! |
Beta Was this translation helpful? Give feedback.
-
|
Hey soonerfan237, I am having a problem getting this to work. What I am trying to do is get my Reolink POE Doorbell working as a Media Player in HA so that I can either send an audio file or do Text to Speech to it. I have installed Go2RTC, setup a stream(s) there, created a Media player entry for the stream, but when I try to use it, I get an error message "Failed to call service media_player/play_media. 'webrtc'". My setting for DoorbellRTSP in Go2TRC: My setup in configuration.yaml of the media player
I have installed WebRTC from HACS but don't know what to do with it. When I tried to create a customer card with the Go2RTC stream, it didn't work, so I am not sure what I am supposed to do with it. Can you (or anyone else reading this) provide any direction in getting this to work? |
Beta Was this translation helpful? Give feedback.
-
|
I did downgrade to the April 2023 version of the firmware on the camera, btw. |
Beta Was this translation helpful? Give feedback.
-
|
Maybe I'm mitaken and I didn't pick the proper version to downgrade, but it seems to me version 3215 does not work for 2way audio as mentionned here but when I downgraded to If someone has the 2 features working (on wifi version preferably) please do correct me and share what firmware version you have, either the download link or at least the version number so I can ask for it to the reolink support tams ;) Else I fear I can only wayt for the vendor to fix the bug and release a new firmware ;) |
Beta Was this translation helpful? Give feedback.
-
|
For anyone following the reolink doorbell firmware issues - I've found some issues with chime pairing after downgrading my v2 Doorbell to v3.0.0.2033. There are multiple versions of the Reolink Chime
On my v2 Doorbell running v3.0.0.2033 with v2 Chime, I was not able to pair |
Beta Was this translation helpful? Give feedback.
-
I've bricked 2 V2 doorbells trying to downgrade them, has Reolink made another update to prevent it? |
Beta Was this translation helpful? Give feedback.
-
|
@reg98643t |
Beta Was this translation helpful? Give feedback.
-
|
I am experiencing exactly the same issue as described by @soonerfan237 above. However, I have downgraded the firmware on the Reolink Video Doorbell WiFi to v3.0.0.2033 and I still cannot get 2-way audio working. I am receiving audio from the doorbell but I am not able to get sound back to the doorbell. My microphone is working in the Frigate Card (my Android phone is showing a green dot to indicate it is on) but there is no sound out. Also, firmware v3,0,0,2033 broke the connection to my Chime as discussed by @PrplHaz4. This problem is driving me crazy. I would appreciate any help.
Frigate card configuration.txt I would really appreciate some help. Thanks in advance. |
Beta Was this translation helpful? Give feedback.
-
|
You ever figure this out? |
Beta Was this translation helpful? Give feedback.
-
|
No unfortunately not. I have given up and use the Reolink app for 2-way audio and Frigate to record video. The Reolink app is very good and I have found its reaction time is about the same as Home-Assistant so there did not seem much point in carrying on. |
Beta Was this translation helpful? Give feedback.
-
|
Unfortunately not. I think we are stuck waiting for a firmware update from Reolink.
Could try contacting support but I haven't had the time for that at the moment.
…-------- Original Message --------
On 15/7/24 1:49 pm, KMudedla wrote:
***@***.***(https://github.com/reg98643t)
Are you able find any solution to downgrade? I bricked 2 sofar v2 door bell POE
Seems who ever had success, using v1 maybe ?
—
Reply to this email directly, [view it on GitHub](#10619 (reply in thread)), or [unsubscribe](https://github.com/notifications/unsubscribe-auth/AVMRBQN6KRB74DI6WIDY37LZMNBEVAVCNFSM6AAAAABFEBMQIOVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTAMBUGY3TOMI).
You are receiving this because you were mentioned.Message ID: ***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
|
I m having the same issue. I talk to my phone app and sound does not come out from the camera. when I talk to the camera, I can hear from my phone (Samsung Fold 5) But when I use my Samsung Note 20 Ultra, the 2 way audio works. but the live feed may freeze when I talk to the camera. So 1 phone works and 1 phone does not. Anyone find a fix ? |
Beta Was this translation helpful? Give feedback.
-
|
Have you figure it out ? I'm having the same issue on SM-T733 |
Beta Was this translation helpful? Give feedback.
-
|
How does the 2-way audio actually work? Is a microphone symbol displayed in the camera's live feed under Home Assistant and can I then press it to speak? |
Beta Was this translation helpful? Give feedback.
-
|
I just installed the v3.0.0.2033_23041302 firmware on a PoE doorbell purchased in June and it has entered an unstoppable bootloop (alive for 15 to 20 seconds, then unavailable 15 to 20 seconds). Factory reset took (when it's alive for a few seconds, the windows app shows it is not initialized), but did not help. I think this thing just became an expensive paperweight, unless anyone has a recovery mechanism they'd advise. |
Beta Was this translation helpful? Give feedback.
-
|
Nope - best I was able to do was to have it RMAd by Reolink since it was still under warranty. |
Beta Was this translation helpful? Give feedback.
-
|
I just bought one today because I was under the impression that this would work. Is there another option that you're aware of for HA/Frigate users or are we SOL at the moment? |
Beta Was this translation helpful? Give feedback.
-
|
If you just bought one you shouldn't have any issues, mine has been working fine for 2 years |
Beta Was this translation helpful? Give feedback.
-
I was Trying to get it set up for two way audio last night and could not even get one way audio working (can't hear the doorbell) should I open a new discussion to try and troubleshoot my issue? I figured what this guy was talking about would've been the problem |
Beta Was this translation helpful? Give feedback.
-
|
As can probably be gathered from others here, v3.0.0.4110_2410111120 does not cause the camera to enter into a bootloop. I'm still working to find a successful formula, but at least this firmware works with the RMA'd device Reolink sent. |
Beta Was this translation helpful? Give feedback.
-
|
I'm getting lost in this discussion, I think everyone should try to be more specific, so I'll attempt to start : With the latest home assistant.
I am not running the latest firmware as you can see, that is because upgrading caused one of the above feature to break, don't remember which one. I would like to be able to speak to frigate and have my voice output by the camera speaker, either live or by playing a media from HA onto a "speaker" entity of the camera device in HA, but that's lower on my priority than the above features, so I have downgraded to the above "old" 2401262240 firmware to get back these features and I'm monitoring this thread hoping someone tells us the latest firmware is all good. Did someone manage to get 2 way audio (your voice into frigate coming out of the camera, or recorded media from HA) without breaking one of the above like loosing sound or the ability to select the prerecorded message? And if yes with which firmware version? Hope we can sort it out. |
Beta Was this translation helpful? Give feedback.
-
|
Two-way audio works in the firmware released on October 23 for PoE doorbell: v3.0.0.4110_2410111120 |
Beta Was this translation helpful? Give feedback.
-
|
Both were still webrtc. Changed to go2rtc and the option popped up. You sir win the Internet for the day! |
Beta Was this translation helpful? Give feedback.
-
So, for y'all that everything is working for... what was the magic formula that got you there? Looking at my frigate config, I have a second go2rtc stream like so (from the docs): In various posts here, I see another example that looks like this, though: I'm a little lost in the difference between the two, which user/password to pass, the hosts, etc... all the redacting in the post has made things super vague :-). |
Beta Was this translation helpful? Give feedback.
-
|
Beta Was this translation helpful? Give feedback.
-
|
This has been a useful thread, thanks all! Does anyone have suggestions on how to to debug this when it's not working? I'm on the latest firmware, and the Frigate UI is showing a microphone. Trying configurations like the above doesn't actually lead to anything being audible. I've noticed that I can't even get the go2rtc microphone stream working, which I suspect is fairly fundamental. Any tips would be much appreciated as I'm at a bit of a dead end. |
Beta Was this translation helpful? Give feedback.
-
|
if frigate shows the microphone then the device is advertising the feature, if the device is not outputting audio that is a device issue so maybe restart it |
Beta Was this translation helpful? Give feedback.
and others
A user said the August version works