Open rpfile opened 3 years ago
Would also be interested in this!
What would be the purpose of this that wouldn't be possible with other homebridge plugins?
what other alarmdecoder plugins are there?
part of the reason i set this all up was to be able to arm the alarm remotely. but if someone left a window open by accident, the alarm can not be armed. so i thought it would be useful to have a button that bypasses all faulted zones.
so we could add a 'switch' that when active adds additional digits to the 'set pin' to do the override. Issue is I don't have a Honeywell system to test on anymore and I'd really need to run it through it's paces to not break anything. You're welcome to fork it, create a brach and submit a pull back. I can guide on what I think you'd need to do but I just can't test it.
i can test this for sure, but not in the short term. probably sometime next week.
What would be the purpose of this that wouldn't be possible with other homebridge plugins?
what other alarmdecoder plugins are there?
part of the reason i set this all up was to be able to arm the alarm remotely. but if someone left a window open by accident, the alarm can not be armed. so i thought it would be useful to have a button that bypasses all faulted zones.
I have a similar use case where sometimes I would like to arm the alarm but bypass a specific zone. I have setup custom buttons to bypass certain zones on my alarm pannel, but I can’t access these buttons via homebridge.
sorry about leaving this hanging, had some serious family issues. let me know if you're still interested in this and i will do the fork.
is there a way to add homekit switches for custom buttons? naively i thought that if i created and named a custom button "foo" in the alarm decoder configuration interface and then referenced "foo" in the useSwitches line of config.json that homekit would be able to trigger that button. however, homekit says "no response" from that switch and nothing happens when i press it.
is this something that is supported? if so is there some other way the button needs to be referred to in config.json?
thanks