Reolink doorbell two-way talk via neolink (MUCH lower delay) #11924
Replies: 15 comments 44 replies
-
Your go2rtc release is amd64 but your neolink release is arm64, is that correct? |
Beta Was this translation helpful? Give feedback.
-
@bezmi I was able to get the above working on my frigate docker compose. First issue I had was that go2rtc was in '/usr/local/go2rtc/bin/go2rtc' for me, so I have move the newer version there. The second issue I had was that I needed to add the following to /config/neolink/neolink_talk.sh Otherwise it would not find the config file |
Beta Was this translation helpful? Give feedback.
-
Does this overcome the 2way audio not working issue introduced in firmware v3.0.0.3215_2401262240? |
Beta Was this translation helpful? Give feedback.
-
Beta Was this translation helpful? Give feedback.
-
I tried to get the neolink 2 way audio working on my Reolink doorbell. I'm able to play the audio using the command But when i try and use the mic button in home assistant app no 2 way audio come out, also I notice that my stream is not as fast when using neolink. here is my config `root@frigate:/config/neolink# cat config.toml [[cameras]] `root@frigate:/config/neolink# cat neolink_talk.sh ffmpeg -fflags nobuffer -f alaw -ar 8000 -i - -f wav - | /config/neolink/neolink talk front_door -c config.toml --volume=1.0 -m -i "fdsrc fd=0"` |
Beta Was this translation helpful? Give feedback.
-
Any idea if this is still possible with the latest frigate 0.14 release? It appears as though I no longer have a /config folder in my docker container:
|
Beta Was this translation helpful? Give feedback.
-
The volume is a little low for me. What is the maximum that I can safely put for volume in the neolink script? Also, I have a frigate container with integrated neolink. It's on docker hub at My repo is here: https://github.com/BEFH/docker_frigate/ In order to configure, you can use the scripts and config files in the repo, changing IP addresses and passwords. Instructions are in the repo. |
Beta Was this translation helpful? Give feedback.
-
@bezmi where are you seeing the MIC icon. im connected to HA via HTTPS, i did everything you did above. im showing the video, i can hear. but i dont have a mic enable icon. my firmware is : my model # is DB_566128M5MP_P |
Beta Was this translation helpful? Give feedback.
-
Gday everyoe. the sample test works fine, but i jsut cnat speak to it. Everytime i try the micbutton it errors with this below. UnicodeDecodeError: 'ascii' codec can't decode byte 0xe2 in position 31: ordinal not in range(128) my go2rtc line:
|
Beta Was this translation helpful? Give feedback.
-
The GitHub actions were the hard part of the repo. Don’t forget to set your
secrets!
…On Fri, Aug 30, 2024 at 10:20 AM PetePeter ***@***.***> wrote:
ah. now's a good time to learn how to build my own docker based on your
copy of his but with stable only. yay i learnt dockerfile tonight
—
Reply to this email directly, view it on GitHub
<#11924 (reply in thread)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAZ2Z2E7IDNJ6TSR7EJN4DLZUB5TZAVCNFSM6AAAAABJHODVQWVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTANBZHE4DCNA>
.
You are receiving this because you were mentioned.Message ID:
***@***.***
com>
|
Beta Was this translation helpful? Give feedback.
-
I have updated https://github.com/BEFH/docker_frigate/ with a matrix strategy so that it stays up-to-date with |
Beta Was this translation helpful? Give feedback.
-
A few months in, have you noticed any issues running libcairo2 as 1.16.0-5? What are the errors you're getting? |
Beta Was this translation helpful? Give feedback.
-
has anyone experienced homeasistant/go2rtc/neolink causing the mic to stay on and the camera getting stuck and doing no more 2way audio? |
Beta Was this translation helpful? Give feedback.
-
Give this a try:
|
Beta Was this translation helpful? Give feedback.
-
I'm using Neolink talk command with a non-doorbell reolink camera. The test command works, But I am now trying to get my frigate hass card with the microphone button working.
|
Beta Was this translation helpful? Give feedback.
-
Extending my comment which was originally posted on the go2rtc issue
Here are some detailed instructions to get reolink doorbell two-way talk working via QuantumEntangledAndy/neolink which offers much lower latency than the rtsp backchannel. It's pretty much the same latency as the reolink app. Obviously, this is highly experimental and might break things so use at your own risk!
First, some commands to install neolink and deps in the frigate docker container. see footnote
Make sure you enter the frigate container first:
docker exec -it frigate bash
Now create the file
/config/neolink/config.toml
:and the file
/config/neolink/neolink_talk.sh
Make it executable
Finally, edit the go2rtc streams section in your frigate config file,
/config/config.yml
:The first entry is the regular stream, second entry
exec:...
is the backchannel magic.note: I remove libcairo2 and install a different version to make gstreamer happy. I think this might be the cause of some errors in the frigate log, but I haven't noticed anything actually going wrong. Use at your own risk.
edit: use the full path to neolink executable in
neolink_talk.sh
Beta Was this translation helpful? Give feedback.
All reactions