-
Notifications
You must be signed in to change notification settings - Fork 295
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
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:password@192.168.10.51: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:password@192.168.10.51: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. |
You'll have to be more specific as to what you need help with |
Hi Nprez83, Sorry for not indicating well with my issue. Basically,I got myself a Reolink door Camera POE version and would like to integrate to Home assistant. My target for this integration, as follows:-
Please allow me to aligned myself to be same page as you. Could you advise what are the adds-on is needed:-
####### FYI######################## |
@NdR91 my frigate is not working( mic button is there and i am able to switch on/off but no audio output).. and I did manually update frigate ( go2rtc version from 1.2 to 1.5) Could you advise what are the actual adds on is needed? And I confused some of codes you guys are talking about: like where this code is located,need to manually created( like what we did when we installed the frigate) So this is the reason why I ask what are the add on is needed so will be easier to understand and raise my question/issue properly. |
Is my setup correct:
Webrtc: lovelace card
|
|
@jovanyeo can you say how? I can't seem to find the way to solve it |
Hello @mpeterson , What components has you installed to your HA. You only need go2rtc and webrtc. Basically go2rtc is to pull the stream( video/ audio) from camera. And Webrtc is the user GUI to interact with the camera. Which part do you got stuck with? |
@jovanyeo thanks for the good predisposition! I just got it to work (partially), it was a networking configuration issue, the ports were not exposed correctly. Now I can do 2-way audio from the card, however the |
Hi @jovanyeo ! |
Hello Max, Fyi. v3.0.0.2033_23041302, this firmware is fine too |
What is the media player for? |
@jovanyeo this is my configuration in "configuration.yaml"
My go2rtc version is 1.8.5. My frigate docker-compose
You have an error when you play sound with the |
I can't see codec name in your config |
Oups thx @AlexxIT !
|
Is 2-way audio still working for people after upgrading to firmware v3.0.0.3215_2401262240? No longer working for me, would love not having to downgrade the firmware if possible. @jovanyeo |
I have confirmed that the 2-way audio broke between version v3.0.0.2033_23041302 and v3.0.0.3215_2401262240. When I reverted to v3.0.0.2033_23041302 using this firmware archive repository, I managed to get it working. |
Thank u!!!! |
Thanks. I only realized because I was trying to get 2-way audio working on a new Reolink E1 Zoom, which I figured would be the same setup as the doorbell, only to find out neither of them work 😕 |
Hi All, using the latest version (1.9.2) of go2rtc, I have managed to use the 2 way talk functionality in QuantumEntangledAndy/neolink with the Here is the script I'm using ( #!/usr/bin/env bash
ffmpeg -fflags nobuffer -f alaw -ar 8000 -i - -f wav - | ./neolink talk Doorbell -c config.toml --volume=1.0 -m -i "fdsrc fd=0" go2rtc.yaml: streams:
doorbell_sub:
- ffmpeg:http://doorbell_ip/flv?port=1935&app=bcs&stream=channel0_sub.bcs&user=admin&password=PASS#video=copy#audio=opus
- exec:/config/neolink/neolink_talk.sh#backchannel=1 I'm using it now with frigate, but that involves installing gstreamer, etc into the docker container, as well as using the latest go2rtc instead of the included v1.8.4. An easier way to test is using Alex's WebRTC card/integration and setting The ffmpeg pipe into neolink is faster than using |
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: