Skip to content
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

Get doorbell button press state change #235

Open
1 task done
sesardelaisla opened this issue Nov 21, 2024 · 6 comments
Open
1 task done

Get doorbell button press state change #235

sesardelaisla opened this issue Nov 21, 2024 · 6 comments
Labels
enhancement New feature or request

Comments

@sesardelaisla
Copy link

Is there an existing feature request for this?

  • I have searched the existing issues

Add-on

Doorbell

Your feature request

Hello,

Would it be possible to get some sort of status/entity change when the doorbell BUTTON is pushed, regardless of the calling state? What I would like to achieve is to have some sort of "silent" notification or partial DnD mode. The idea is to enable a "disabled" schedule/template in the doorbell so no calls are executed according to #231. Caller will hear the "not available" message upon button press. However, selected doorbell users could get a push notification through an automation, so they can call the doorbell back if they really want to respond. A SIP dashboard card would work great for this, because the notification could actionable and have an URI to call the doorbell on the fly.

@sesardelaisla sesardelaisla added the enhancement New feature or request label Nov 21, 2024
@pergolafabio
Copy link
Owner

hmm, not sure if that will work, if you hear a "not avaible" message, it means the outdoor unit isnt able to call something, and i dont think there is any event then logged ... you could maybe setup the sip script at scheduled times , so you dont have the "calling failed/unaavaible" message, that way the sensor / event is fired and you can start your automation

this script below, was intented to fake/simulate an indoor extensions, that register on your primary indoor station, but you can change it , so it can register on your outdoor station at the time intervals you need... but remember, if the script is activated, it wont be able to call your real indoor station/hikconnect ...

https://github.com/pergolafabio/Hikvision-Addons/blob/main/asterisk/hikvision_register.py

@pergolafabio
Copy link
Owner

use this sip nr 10010110001 as username instead of the 10000000005 as in the script
10010110001 is the sip number from your indoor extension (faked)
also change line 69 , change 5061 to 5060 ... the hikvision devices are hardcoded to send the invite back to port 5060 , so then your script intercepts the incoming call too , you can then trigger an sensor ...

@pergolafabio
Copy link
Owner

in example 0.17 is the IP from your OS, where you run the script on, 0.71 should be your outdoor station

@sesardelaisla
Copy link
Author

Interesting workaround... Will check that fake indoor panel approach to see whether I can achieve what I want. Will share feedback if I move forward. Thanks!

@pergolafabio
Copy link
Owner

How did it go?

@sesardelaisla
Copy link
Author

Honestly, I’ve had no time to test it. Will probably find some time by Xmas holidays. Will give an update when able. Thanks for following up!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants