Reolink Video Doorbell discussion #331
Labels
camera
Discussion on a particular camera model
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. |
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 |
|
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. |
|
Does anyone know if the new firmware |
|
Today I updated my Doorbel PoE to version v3.0.0.4110_2410111120 and two way audio is working for me. I’m on Frigate 0.14 with updated go2rtc 1.9.7, and fully updated latest Home Assistant. |
Can you share your config for me and other users? |
|
That would be amazing if you could share your config 🙏
…On Sat, 16 Nov 2024 at 00:05, Alfons-Hetler ***@***.***> wrote:
Today I updated my Doorbel PoE to version v3.0.0.4110_2410111120 and two
way audio is working for me. I’m on Frigate 0.14 with updated go2rtc 1.9.7,
and fully updated latest Home Assistant. Also I just tried via my
CloudFlare Zero Trust tunnel (https) and it’s working fine inside HA iOS
companion app via mobile data.
Can you share your config for me and other users?
Thanks
—
Reply to this email directly, view it on GitHub
<#331 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AB47W44N3QHSLZAP4YJSC332AZVZRAVCNFSM6AAAAAAWSFVP4SVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIOBQGAYTEMZYGQ>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
|
@Alfons-Hetler and @vexersa |
|
I managed to get my WiFi doorbell working with 2-way audio both using RTSP and FLV after a lot of playing around. This is the RTSP one: And this is the FLV setup: But I have a few questions.
@bagobones Mind sharing how do you call the PIPup HA action? I'm trying camera URLs, but can't make it work. I'm ALMOST there. |
Note there seem to be various forks of PIPup with the original being broken IIRC, I don't recall which one I ended up using. Setup a rest command Automation call in HA with the direct go2rtc URL to the camera stream. |
|
Amazing! Thanks! I'm using the original PIPup app as it's the only apk I could find. The fork doesn't have it available atm. It's working fine though. I managed to make it work using this amazing tutorial: https://seanblanchfield.com/2023/06/realtime-pip-cameras-on-tv-with-home-assistant-v2 But tbh for this use case your URL works straight away without the need of WebRTC or it's action to create a link. My only bother now is that the notification shows perfect and instant, but the stream takes a couple seconds to load. See here. . Ignore the RTC/MSE switch. It does the same when loading directly into MSE. Were you able to reduce/remove this load time? |
Sorry I just realized I have two automations one FORCES WebRTC which reduces load time, the first URL does detection which is a little slower.. I will also note I intentionally use the SUB stream as it is smaller and seems to load faster. |
|
I have 3 differences:
|
|
Ya my host is literally named frigate, that is just specific to my config. Also in my case I am not using a chrome cast but a Google TV is my target. so it may be slightly different. Both sort of out of scope here. FYI I DON'T use the FLV stream I use RTSP, other than a frame drop here or there it works fine as long as you aren't on really old firmware on the doorbell. |
|
So... somehow I managed to make RTC work. No clue how but it works. Which turns into these 2 links: Both of them work on RTC when opening in the PC. But when sending them to PIPup, only the first one loads. The FLV one won't load for some reason. No clue. Also, it's true that the load delay was reduced a bit, but it's still noticeable. Is it that way for you? Any chance you can record it? |
Try this instead |
I tried, but no difference. One attempt it actually loaded after like 10s or so, but then it didn't happen again. I'll leave it like that since the YAML looks cleaner to me. |
|
I don't use the FLV stream. Make sure your I frame setting is set to 1x on the doorbell for both streams . That impacts delay the most on the camera side. |
|
I know, I'm also using the sub RTSP now, but there's still a decent time to load. That's what I'd like to see yours. Maybe it's the best it can be and I'm worrying over nothing. Can you record it? |
Record what? How long http://xxxxxxx:1984/stream.html?src=doorbell_sub&mode=webrtc takes to load? it is variable, cold (after a frigate/go2rtc reboot) can take 7s, however after I have loaded it once the next load tends to be more like 3s or less sometimes near instant. |
I mean a video like this one, showing the notification loading the stream. This one is the sub stream on RTSP, on 1x. Just want to know if I can get better than that. |
That is as fast as I have ever gotten. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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: