Reolink Video Doorbell discussion #331
Comments
|
You need to enable trace logs for rtsp and send that here, looks like they changed the rtsp format from what I saw back in February new one is here: |
|
@NickM-27 Is this the log you mean? I traced with Home assitant when opening the links.html in the go2rtc web ui. |
|
No, the log I mean is the log I posted above. |
|
Where can I find the log? |
|
My bad looks like those logs are them, but they don't show the third audio track like mine do. Maybe you didn't copy all of them? |
|
ah ok now I get it, this log seams to be complete, it contains a third audio track: |
|
So you are seeing the same thing I am which is that when go2rtc requests the backchannel audio, the doorbell responds with |
|
Yes the same for me, I tried to play a sound file via curl and got: |
|
I wonder if there is a setting or special permission that needs to be enabled in settings |
|
I am trying the same thing with scrypted and looks like it's getting further. However, it is still not working. This is the trace from scrypted. |
|
How do you have configured your go2rtc.yaml in Home Assistant ? go2rtc.yaml reolink_1: ffmpeg:rtsp://admin:[email protected]:554/Preview_01_sub#audio=opus#video=h264#backchannel=0 log: 2 ways audio doesn't work either but I cannot get a verbose log like you have, how did you manage to get all these informations in your log ? configuration.yaml logger: |
|
@spawn451 you can't use ffmpeg, that does not support 2 way audio |
|
@NickM-27 But if I don’t use ffmpeg and for example set this : |
|
@spawn451 you need to set it up like this: streams:
reolink:
- rtsp://admin:[email protected]:554/Preview_01_sub
- ffmpeg:reolink#audio=opus |
|
@NickM-27 Thanks! I’m gonna change my config. |
|
Scrypted is updated and 2-way audio is working with the ONVIF plugin |
|
This is the commit that added support koush/scrypted@ec3e16f |
|
@luisiam could you post a trace from scrypted with 2-way audio working? I want to compare it with the log you posted above to see if there are any differences. |
|
If you check go2rtc's commit history, there's a recent patch to fix
the issue.
…On Wed, Apr 12, 2023, 5:01 PM kevdliu ***@***.***> wrote:
@luisiam <https://github.com/luisiam> could you post a trace from
scrypted with 2-way audio working? I want to compare it with the log you
posted above to see if there are any differences.
—
Reply to this email directly, view it on GitHub
<#331 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAILPFAVNRE6QKNFETMJJITXA4X45ANCNFSM6AAAAAAWSFVP4Q>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
|
|
@rbray89 more work is needed, the doorbell does not play audio in my testing |
|
It could be a transcoding issue. Reolink only uses AAC, and Opus/PCM is used by webrtc. |
|
@rbray89 that is also incorrect. If you check the sendonly audio channel on the reolink doorbell, it is PCMA/8000 which you can see from the RTSP DESCRIBE response in an earlier comment #331 (comment) |
Here it is |
|
@NickM-27 Not sure if helpful but Reolink just released a new build |
|
@SilverHazeLazers any idea where to get that build? as far as I can tell, reolink has removed the doorbell firmware builds from their website. Perhaps that is a sign that things are not ready yet. |
|
… On Thu, Apr 13, 2023, 6:42 AM Nicolas Mowen ***@***.***> wrote:
@SilverHazeLazers <https://github.com/SilverHazeLazers> any idea where to
get that build? as far as I can tell, reolink has removed the doorbell
firmware builds from their website. Perhaps that is a sign that things are
not ready yet.
—
Reply to this email directly, view it on GitHub
<#331 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAILPFBWDVMN3YAYD5HCWSTXA7YDRANCNFSM6AAAAAAWSFVP4Q>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
|
Just tried it, seeing some errors in go2rtc: |
|
@NickM-27 Are you sure this logs from go2rtc? I don't know what is |
|
I agree it is a weird format and doesn't match go2rtc logs, but it definitely came from the process running go2rtc and it happened right when I tried to play the two way talk with the doorbell. That being said, I did a handful of refreshes trying to get it to work so it may not be related to the reason two way talk isn't working with the doorbell. |
|
Indeed HTTPS is also a requirement for 2-way audio to work. |
|
Browsers disable mic for HTTP sites. This is default behaviour. Hass mobile app is also a browser. |
This makes sense, reverse proxy it is. Do you know if webrtc is required if SSL is present? |
Thank you 🙏 I will try and do this and update the thread if it works. |
WebRTC can work on HTTP sites. |
|
You can skip HTTPS requirements for testing purpose |
|
I'm able use the reolink doorbell flv with two way audio using go2rtc webrtc-camera card. |
I use dashcast that comes with webrtc camera integration and I can cast it to any nest hub or chromecast w/ google tv. |
|
I use PIPup on android TV and use Home Assistant to trigger a picture in picture feed when the doorbell rings. I am just using rtsp, I am not using FLV on any of my newer reolink devices. |
|
Reolink RTSP problem depends on device firmware. They know how to fix it. But the firmware upgrade process is laid out horribly. Only by contacting technical support. |
|
The current public firmware for the black wifi doorbell fully works over RTSP and has working two way The duo2 poe also fully works over RTSP. |
Would it be possible to share your config please? 🙏 I've tried many different configs and I just can't get the two way audio to work. I can hear the audio from the doorbell, but can't send audio back to it. |
This is my lovelace card config that works for me |
|
I've got 2 way audio working with the frigate lovelace card but when I try to play an audio file whether it's through webrtc or on the go2rtc server inside frigate (port 1984) it just doesn't work. This is what the logs say:
And chrome console gives
Does anyone have an idea why it won't work? Edit: I manually updated the go2rtc binary in frigate and now I can send an mp3 through this url: The only thing I still need to get working is using webrtc as a media player in home assistant |
@b0ddu could you share your go2rtc.yaml config? I can only get 2way audio on rtsp, not flv. |
|
Hi, i'm not able to use 2-way-audio with my Reolink Doorbell wifi (white). thanks in advance |
Have you read the thread? There's many configurations you can use. Also make sure you're using https not http |
yes, i have did i miss somenthing? 🤔 |
Do you have a rtsp stream configured also? I don't think the flv stream supports two way audio |
|
https://frigate-docs.netlify.app/configuration/camera_specific#reolink-cameras This is how Frigate recommends setting up Reolink cameras with go2rtc for 2way audio to work |
yes, i made exactly what frigate recommends in its doc. |
|
after looking at Frigate docs, I made it work. 2 way audio with flv video stream. |
|
thanks @tasiotas and here are links in frigate: 2-way-audio doesnt work :/ thanks go2rtc; Version: 1.9.4 |
|
Your frigate config is wrong If you're using the internal go2rtc you should be using 127.0.0.1 , right now you have it set to go2rtc which won't connect to anything as it's not an IP address. The docs show you how to set up |
|
A few weeks ago my 2 way audio was working, don't know why it isn't anymore, maybe a Home Assistant update stopped it? My config: When it was working, I was able to enable the 2 way audio by pressing the mic button when the I click the stream (not present in the screenshot below): go2rtc probe logs: What could I check to troubleshoot? |
|
i have 2 docker container in the same stack:
should i use the internal go2rtc instance? |
|
Ok, using go2rtc integrated in frigate seems to be working. I see microphone button. |
Is your home assistant companion app Internal AND External URL set to use HTTPS, it is essentially a browser wrapper and if the HA site isn't HTTPS the mic will not appear. Edit: to clarify both the frigate interface imbedded in HA, and the frigate custom card in HA work fine for me in the companion app and present the mic. |
|
thanks @bagobones EDIT: i see the mic button, but it doesnt work :/ |
I dont think the Cloudflare tunnel will proxy the WebRTC comms. Those are often UDP on a negotiated port. |
and others
The latest FW 1859 enables 2-way audio via ONVIF profile T. I checked with Happytimesoft ONVIF client and 2-way audio works. Is there any chance to get it working in go2rtc?
Output from info page
The text was updated successfully, but these errors were encountered: