![]() ![]() So mine doesn't really have a panic button but it has the police, fire and emergency buttons on it. ![]() It would help me to implement a useful I am actually using the Ring v2 keypad for my alarm system have have it linked to Alarmo using Node-red. I'd like to your thoughts on my considerations. Which would mean it doesn't require anything to be added to Alarmo, it can be achieved by a normal HA automation which is triggered on the button press. My conclusion would be that pressing this button should just trigger some automation, without affecting the Alarmo state. In this case I wouldn't want the alarm to be disarmed (with or without duress mode), as this would bypass the mandatory pin code to be entered for the disarming. I have never used it, but I suppose it is intended to have a direct effect without requiring to enter a pin code first. ![]() The keypad I use for Alarmo also has a panic/SOS button. If not, this goal could be easily achieved by creating an automation (outside of Alarmo) which is triggered on a button press and executes the alarmo.disarm service with the duress pin code provided in the service data. I am not sure if we should be distinguish between panic and duress. The original request by is for a "panic button". I would also say that in duress mode, the normal Alarmo actions/notifications and HA automations should also be triggered, such that all appears normal. Next steps would be to add the option to configure Alarmo actions/notifications and HA automations to be triggered specifically in the case of disarming under duress. ![]() I am wondering if there is any practical use-case for being able to arm the system under duress, I guess disarming under duress is a more realistic scenario. Instead I am considering to add an extra property to the alarm_control_panel entity, like duress_mode which can be true/false.Īs a consequence the alarm could theoretically be both armed or disarmed into duress mode. The main reason is that I want to limit to the states defined by HA to ensure compliance with the frontend and other integrations. adding a DURESS_DISARMED is not gonna happen). I don't want to add an extra state to the alarm (i.e. Now obviously, the effect should be different. The user is able to disarm the alarm as normally, so via whatever keypad they already use. I am considering add the property proposed by to mark a code as "duress code". I think my proposal would be better suited for duress and allow other triggers based on the codes entered. One of my examples is to handle a duress situation. Please see #521 which I just opened suggesting improvements around codes.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |