Yes we definitely need to get 2-way audio working!
I was expecting this would work

What's the latest on adding this feature? Thanks!

@roero_622506978795586 Yes you can report it to Reolink by writing an e-mail to support[at]reolink.com I had to replace @ with [at] as the forum doesn't allow links.

Here's an example that you can adjust to your needs:

I just received the Reolink doorbell PoE.
The android app has a major problem on my Samsung A53 and I have found reviews on multiple forums where others report the same problem with their Samsung smartphones. And I know others have written to you about this problem as well. Like many other smartphones, the A53 has a microphone at the bottom (used to speak when holding the phone to the ear) and a microphone at the top of the smartphone (used when talking in "speaker mode"). The reolink app unfortunately uses the wrong microphone (the one at the bottom) instead of the one at the top. Can you please fix this?
I don't know why but even when I talk while holding the phone to my ear the sound on the doorbell is still far to low.
I really hold that microphone right in front of my mouth to be somewhat audible.
On my partner's Oneplus Nord everything works just fine.

Your firmware update a while ago to boost the volume helped a little bit, but as it still uses the wrong microphone it is still not acceptable.

@user_680655709737145_680655709737145 Here you can see how I set up the actionable notifications in Home A*sistant: https://community.home-a*sistant.io/t/homea*sistant-and-reolink-doorbell-poe/485857/69?u=quizzical

Concerning the notifications I have this working. I get different types of notifications depending on whether someone pressed the doorbell, a person was detected, it's night,... However I use Home A*sistant for the notifications instead of the Reolink app.

Here's my list of wishes:

• Allow activating the “quick replies” from Home A*sistant or other third-party solutions. If you want that as well please ask Reolink to enable it in their API. This has many uses. e.g. when you can configure home a*sistant to send you a notification with a picture when someone presses the doorbell (or even when it detects a person) and the notification can have several options that you can click on for what the speaker should say (e.g. leave the package at the door).
• face recognition: When the camera sees a person I have Home A*sistant send me a notification with a screenshot. I’d like to be able to not send me those screenshots when it’s my wife etc.
• Allow activating the alarm sound from Home A*sistant or other third party solutions. Again this needs to be enabled in the Reolink API.
• 2-way audio: would be great to have this working in Home A*sistant and Synology Surveillance Station and other third-party solutions.
• Full integration with Synology Surveillance Station: (play custom sounds trough the doorbell, detect person, detect doorbell press, 2-way audio)

And list of issues:

• Important information to make the Reolink work remotely with a VPN if you’ve blocked it from accessing the internet: by default the Reolink app adds the doorbell based on the ‘UID’ rather than it’s IP address and then it only works using the cloud once you have excited the app and open it again. To make sure you add the doorbell based on it’s IP address you need to delete the device if you already added it. Then disable wifi on your smartphone so that you are on mobile data. Then activate the VPN. Then add the doorbell using the option ‘input UID/IP’ then choose the IP option and enter the camera’s IP address.
• When the doorbell switches to Infrared mode and vice-versa it is falsely reported as a motion detected event. That’s a bit amateuristic.
• The android app has a major problem on Samsung smartphones. On Samsung smartphones it uses the microphone at the bottom (used to speak when holding the phone to the ear) and not the microphone at the top of the smartphone (used when talking in “speaker mode”). The update (not released yet officially) helps a bit with the problem because you can set the audio volume of the built-in speaker. Would still be far better if it uses the right microphone because I still have to hold my mouth at 1 cm distance from the smartphone so I can’t really watch the screen and talk at the same time.

@joseph-chircop_497308027822318 I'm sorry but that is not correct.
That new version (which I received as a beta) improves the situation a bit. However the difference with my wife's OnePlus brand smartphone is still nigth and day. She can hold the phone in front of her and watch the videostream on her smartphone while talking and it is loud and clear.
On my Samsung I have to speak directly into the bottom microphone holding it 1 cm from my mouth and then it is audible (but not more than that).
As I wrote above, the Reolink app should use the right microphone (the one at the top of the smartphone which is made for speakerphone mode, not the one at the bottom which is intended to be used when holding the phone against your ear).

@user_679217629425876_679217629425876
thank you! the Reolink android app falsely informed me that I am on the latest firmware.
I downloaded the firmware on the reolink website and installed it. However it does not enable two way audio
Looking at the changelog it says they enabled it for Alexa, so I guess they didn't enable it in ONVIF...

Are there others that are still facing this issue like me on their Samsung device?
With the added feature to crank up the volume I'm able to have a conversation by holding the microphone right to my mouth, but not while holding it at a distance (which works with other brand Smartphones).
Would be great if Reolink could use the correct microphone on samsung devices...(the one used when in speakerphone mode).

@roero_622506978795586 Yes you can report it to Reolink by writing an e-mail to support[at]reolink.com I had to replace @ with [at] as the forum doesn't allow links.

Here's an example that you can adjust to your needs:

I just received the Reolink doorbell PoE.
The android app has a major problem on my Samsung A53 and I have found reviews on multiple forums where others report the same problem with their Samsung smartphones. And I know others have written to you about this problem as well. Like many other smartphones, the A53 has a microphone at the bottom (used to speak when holding the phone to the ear) and a microphone at the top of the smartphone (used when talking in "speaker mode"). The reolink app unfortunately uses the wrong microphone (the one at the bottom) instead of the one at the top. Can you please fix this?
I don't know why but even when I talk while holding the phone to my ear the sound on the doorbell is still far to low.
I really hold that microphone right in front of my mouth to be somewhat audible.
On my partner's Oneplus Nord everything works just fine.

Your firmware update a while ago to boost the volume helped a little bit, but as it still uses the wrong microphone it is still not acceptable.

@user_680655709737145_680655709737145 Here you can see how I set up the actionable notifications in Home A*sistant: https://community.home-a*sistant.io/t/homea*sistant-and-reolink-doorbell-poe/485857/69?u=quizzical

@joseph-chircop_497308027822318 looks like they pulled it again as there is no firmware for the doorbell anymore in the download center at the moment.

@user_679217629425876_679217629425876
thank you! the Reolink android app falsely informed me that I am on the latest firmware.
I downloaded the firmware on the reolink website and installed it. However it does not enable two way audio
Looking at the changelog it says they enabled it for Alexa, so I guess they didn't enable it in ONVIF...

Are there others that are still facing this issue like me on their Samsung device?
With the added feature to crank up the volume I'm able to have a conversation by holding the microphone right to my mouth, but not while holding it at a distance (which works with other brand Smartphones).
Would be great if Reolink could use the correct microphone on samsung devices...(the one used when in speakerphone mode).

Hi, It would really be great if the APÏ for the doorbell would Allow activating the “quick replies” from Home A*sistant or other third-party solutions. This has many uses. e.g. when you can configure home a*sistant to send you a notification with a picture when someone presses the doorbell (or even when it detects a person) and the notification can have several options that you can click on for what the speaker should say (e.g. leave the package at the door).

What's the latest on adding this feature? Thanks!

yes, I have the POE version with rich notifications. However I integrated the doorbell with "Home A*sistant" and it is this smarthome solution that sends me a snapshot of the doorbell camera when someone rings the door.

@reolink-fiona excellent! I already bought the doorbell and have been waiting for the RLC-1224a to be available for pre-order.
The only thing holding me back to do so is that I need to know whether it will support two way Audio when I integrate it with Synology surveillance station.
For the doorbell this is not the case, it supports profile T and I've seen posts from you that it will be extended to support two way Audio which is great.

If you could confirm that the RLC-1224a already works with two way Audio in Synology surveillance station or at least will work in the near future (e.g. this year) then I will immediately purchase this camera.

Many thanks!

If you integrate the doorbell with home A*sistant you have loads more Options in terms of when you get a notification, what sound it should make etc.
Here's what I did:
https://community.home-a*sistant.io/t/homea*sistant-and-reolink-doorbell-poe/485857/69?u=quizzical

So I only get relevant notifications (e.g. not that it detects my wife when she comes home) and the ones for person detected are silent.