-
-
Notifications
You must be signed in to change notification settings - Fork 41
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
Comments
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 |
use this sip nr 10010110001 as username instead of the 10000000005 as in the script |
in example 0.17 is the IP from your OS, where you run the script on, 0.71 should be your outdoor station |
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! |
How did it go? |
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! |
Is there an existing feature request for this?
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.
The text was updated successfully, but these errors were encountered: