-
-
Notifications
You must be signed in to change notification settings - Fork 54
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
Doorbell press event support #339
Comments
It's a nice enhancement and I wouldn't mind tackling it. But I'd need access to the wireshark packets to reverse engineer the protocol |
If you can provide some steps on how I should setup an environment to capture those packets I can provide them to you. |
I have also been looking at how the button press event is implemented in the official HomeAssistant Reolink integration. There the package https://github.com/starkillerOG/reolink_aio/blob/main/reolink_aio/baichuan/baichuan.py#L423 Not sure if this could be of any help... |
Oh we have CMD 33 already done. It will pop up as a motion alert but we filter it out. |
How would you expect it to be integrated? Are you using the mqtt to read events? |
Yes I use MQTT to receive everything on HomeAssistant so that would be ideal :) |
I'm working on a build for this to test. Are you using docker or bare metal neolink? |
I use the neolink package on a debian LXC in proxmox. Thanks for the quick implementation!
Sent from Outlook for Android<https://aka.ms/AAb9ysg>
…________________________________
From: Andrew King ***@***.***>
Sent: Friday, January 24, 2025 10:38:29 AM
To: QuantumEntangledAndy/neolink ***@***.***>
Cc: ruben-janssens ***@***.***>; Author ***@***.***>
Subject: Re: [QuantumEntangledAndy/neolink] Doorbell press event support (Issue #339)
I'm working on a build for this to test. Are you using docker or bare metal neolink?
—
Reply to this email directly, view it on GitHub<#339 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/ARFNT3ULORTFCROHMUIGSGL2MICZLAVCNFSM6AAAAABUJ6ZIHCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMMJSGA3TONJUGA>.
You are receiving this because you authored the thread.Message ID: ***@***.***>
|
Ok I have the build happening here hopefully it will work and then the binaries will be available |
I'm currently not home so I can test this in 3 ish hours.
Sent from Outlook for Android<https://aka.ms/AAb9ysg>
…________________________________
From: Andrew King ***@***.***>
Sent: Friday, January 24, 2025 11:04:14 AM
To: QuantumEntangledAndy/neolink ***@***.***>
Cc: ruben-janssens ***@***.***>; Author ***@***.***>
Subject: Re: [QuantumEntangledAndy/neolink] Doorbell press event support (Issue #339)
Ok I have the build happening here<https://github.com/QuantumEntangledAndy/neolink/actions/runs/12947382929> hopefully it will work and then the binaries will be available
—
Reply to this email directly, view it on GitHub<#339 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/ARFNT3THNEUUI7QJ52IZDWD2MIFZ5AVCNFSM6AAAAABUJ6ZIHCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMMJSGEZTEMJYGI>.
You are receiving this because you authored the thread.Message ID: ***@***.***>
|
Build will take an hour anyways so no rush |
Ok build of the binaries are here https://github.com/QuantumEntangledAndy/neolink/actions/runs/12947507860 Docker is here |
Talk about perfectly timed, will test them now |
Do I have to modify any config to add the visitor functionality ? |
Alright got the event! A small problem dho
Neolink has send the event almost 140000 times |
Same with the AI event and something is wrong with the motion event no longer coming through |
https://github.com/QuantumEntangledAndy/neolink/actions/runs/12961197957 next build Should fix the repeating notifications, couldnt replicate the motion stopping on mine but I don't have ai or visitor |
I will be able to test the next build in a week
…________________________________
From: Andrew King ***@***.***>
Sent: Saturday, January 25, 2025 6:42:23 AM
To: QuantumEntangledAndy/neolink ***@***.***>
Cc: ruben-janssens ***@***.***>; Author ***@***.***>
Subject: Re: [QuantumEntangledAndy/neolink] Doorbell press event support (Issue #339)
https://github.com/QuantumEntangledAndy/neolink/actions/runs/12961197957 next build
Should fix the repeating notifications, couldnt replicate the motion stopping on mine but I don't have ai or visitor
—
Reply to this email directly, view it on GitHub<#339 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/ARFNT3UZGQTUYDCYYQQU2X32MMP37AVCNFSM6AAAAABUJ6ZIHCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMMJTG44TINZRGI>.
You are receiving this because you authored the thread.Message ID: ***@***.***>
|
I see that the issue is now fixed. Thanks! But for some reason motion events are still not pushed through. |
Is the motion on your camera PIR? |
Reolink has some different ways to detect motion.
The motion detection in Neolink is for the third kind, changed frames Did it work before? I'd like to get a wireshark dump so I can examine the packets and see what is coming from the cameras can you provide one? |
Ah then I think it is not working because of the lost push notifications. I have it setup to disconnect when no motion is detected after a certain amount of time because it is a battery powered doorbell. |
Since there's no push notifications it won't reconnect by itself anymore. P.s. do you have an NVR? I think I can reverse engineer their protocol to hook into its notification system. But I don't have one myself to find out |
Sadly I don't have the NVR or the home hub. I have thought about buying one of them if neolink didn't work out. If we can solve it in 30 days I could theoretically send it back even. |
I'm not sure about the less than 30 days thing. (Work is always busy and would require a lot of effort to reverse engineer) I'm hoping to find something to help or maybe try other experiments. |
Is your feature request related to a problem? Please describe.
I am using Neolink to connect to the new WiFi battery doorbell. Everything works like expected (after some fiddling of course) but now I need to know when someone presses the bell.
I would implement it myself but then I would need to learn Rust from scratch :)
The text was updated successfully, but these errors were encountered: