-
-
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! |
hey, did you try the approach? i get more and more questions about users that dont have an indoor panel or hikconnect.... if the script works to get the doorbell event... we can usee frigate to start the two way audio |
maybe i can add an extra guide for it .. |
maybe usefull , with this addon you can do a register on the outdoor, it will probabbly receive the incoming call event... no need to run s script then didnt test it yet PS: when using the script/plugin, make sure to register on port 5065! the sip server on the hikvision device runs on 5065 |
i quicly tried the addon, it works, i added a fake second indoor to my outdoor, with using config below
after starting addon, it registered, and i was able to make a call! to the addon ... here is log: it registered:
incoming call:
|
Sounds great! Thanks for taking some time for these tests. I will try this as soon as my New Year’s Eve hangover dissapears. 😅 Will give feedback asap. Happy New Year!
|
Hi Fabio, happy new year. You are a real genius with your great ideas. The addon works! Unfortunately the call state is still not changing :( |
Np! But you can probably see the event on that addon, and then use the webhook |
right, that's my plan. At the moment I'm doing it with the asterisk addon and observing the line state of the extension to which the intercom is registered. Next step is to find a possibility to activate/deactivate the FaceID Feature of the station during 2-way-audio call. Otherwise the intercom throws an authorization error every 5 seconds, while an unregistered person stands in front of the station and speaking via 2-way-audio. Of course this is only a problem because of the unusual way how we are using the intercom. A lot of workarounds involved to get the cloud free experience :) |
Good luck! ;-) |
Hey! Just checking in to confirm that this workaround works for the purpose I originally open this issue for! After setting up ha-sip as follows, addon registers and webhook reports button press regardless of what schedule is selected, so I can "disable" calls on the doorbell for siesta time or whatever, but I still can get a notification of whatever action upon doorbell call. Strange that I had to enable "Enable Protocol 1.0" under INTERCOM > SESSION SETTINGS for ha-sip to register correctly (200).
Good to know that it is not necessary to have an indoor station (although I have one) so everything can work straight from the doorbell. I don't like the idea of using two devices if not strictly necessary because if I do so, there will be more points of failures. I use Asterisk, so just tried with ha-sip because it is simpler to setup and I will have to figure out how to setup a webhook in Asterisk. But now that I know that it works, I hope I can make this work on Asterisk. Thanks! |
Thnx for the update, can be indeed usefull for others |
Sad to tell that it doesn't work, or at least it is not consistent. I did some additional tests and webhook is not always delivered if the call button is pressed while Link Time Scheduled setting is set to an empty schedule (calls disabled). Actually, I can't make it work now with the same settings I had a couple of days ago. Will keep doing some additional tests to see whether there is any way to achieve this (just in case I am missing anything/setting I had before), but I guess I won't win. I guess the button press does not do anything that could be captured when an actual call is placed. :(
|
Remember that you can only have 1 active Registation with the same number on the outdoor, for instance,10010110001 can only be registered once, the last registration will replace the previous one... Maybe that's your issue? |
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: