Can ELK M1 alarm trigger Homekit automation #41
Comments
|
It doesn't seem possible to create automation triggers in HomeKit based on the state of an alarm (which I think would be a useful feature - You can submit it to Apple as a feature request). I haven't investigated too much, but it certainly seems like the sort of thing you could build with Homebridge pretty easily. using a logic plug in. You may need to use some M1 wiring and configuration so that you have an output that changes state when the alarm sounds and this is connected to an input. You could then write a HomeKit rule that controlled lights based on that input state changing (It would be a movements sensor in HomeKit for example). Unfortunately my day job keeps me pretty busy, but I can see how I could add a support for a "phantom" output from this plugin that would avoid the M1 config and wiring. I will keep this issue open to track that as an idea |
|
Thank you!Sent from my iPhoneOn Nov 1, 2022, at 1:57 AM, Paul Wilkinson ***@***.***> wrote:
It doesn't seem possible to create automation triggers in HomeKit based on the state of an alarm (which I think would be a useful feature - You can submit it to Apple as a feature request).
I haven't investigated too much, but it certainly seems like the sort of thing you could build with Homebridge pretty easily. using a logic plug in. You may need to use some M1 wiring and configuration so that you have an output that changes state when the alarm sounds and this is connected to an input. You could then write a HomeKit rule that controlled lights based on that input state changing (It would be a movements sensor in HomeKit for example).
Unfortunately my day job keeps me pretty busy, but I can see how I could add a support for a "phantom" output from this plugin that would avoid the M1 config and wiring.
I will keep this issue open to track that as an idea
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: ***@***.***>
|
|
Here's a possible work-around for you. This was a little trick I used over on HAI, which had "Flags" (virtual "switches") before I started using HomeBridge... Of course, as I was typing this out, I discovered that Counter status doesn't appear to be extended to the Plugin. If the plugin could be updated to support Counter status, that would be great, as it would give you the ability to extend whatever flags/data you like between non-compatible systems (or missing HomeKit features). You may also be able to use the higher-end outputs that don't have physical hardware to achieve this (thus, making them virtual) - you'd have to test - but it lists 64 on the core controller, and there's really only like 16, so if you don't have expansion output modules, you might be able to use 17-64 as "virtual"). Create the following Counter/Output: Then create the following rules: Whenever Security Armed to Any Mode>Set Counter_Armed = 1 (or Output ON) Whenever Security Armed-Stay > Set Counter_Armed-Stay = 1 (or Output ON) Whenever Security Armed-Away > Set Counter_Armed-Away = 1 (or Output ON) Whenever Security Armed-Night > Set Counter_Armed-Night = 1 (or Output ON) Whenever Security Armed-Vacation > Set Counter_Armed-Vacation = 1 (or Output ON) All the extra counters to 0 may seem redundant, but I've had weird situations in the past where the controller got out of sync with reality (a power cycle, a crash, whatever), so since you'd have other things relying on these status modes, I always just true up the status every time there's a change. Heck, even running it every few minutes to ensure the status is correct is something I've done before. :) I also create a "room" in HomeKit called "SYSTEM - DO NOT EDIT" (with a red background), and that's where I store all these virtual items for programming. You'd put all these Counters/Outputs in there, then program away. Hopefully the customer understands "Do Not Edit" means "don't effin' touch it". It's also where I sometimes put fire zones (if it's structured fire/smoke and contains several rooms in the zone). So, if you're able to do the above, then you'll have a handful of switches that are extending the security status into HomeKit for you to do other things with. The downside is, these are switches, not sensors. In an ideal world, you could actually see these as sensors instead (so you couldn't control them - we had that option over on HAI). That's how I'd envision the counters working (versus outputs): If 0, consider as off/closed, if greater than 0, consider as on/open (no ability to edit, just a sensor, so delivering status only). Now, here's a fun additional one for you: Create a counter called: Rules: (The "wait" on Elk may need to be achieved by a counter/custom setting timer that counts down from 10, then the rule clears the AlarmHistory) Now, you have a flag/indicator when the alarm had been tripped in your absence. So now, in HomeKit you make a Shortcut: When Security Armed So now, when you disarm your home, if it's been set off while you were gone, you'll see a special light flash and know to possibly enter with caution. Yeah, I know this was long, and probably not the right place for it, but this was to hopefully give you a work around while HomeKit gives you what you want. |
|
Does your key code begin with a 0 by any chance? I just noticed an inconsistency in the plugin between defining the keypad code as an integer and a string. As an integer any leading 0 would be lost. |
|
It does not. It starts with a 1 and ends in a 1It’s actually a dedicated code I use for the integration (so the log shows integration triggered the arm/disarm, but I have tried our general use code too. Also, the other oddity is, arming from the panel (even when the countdown ends), the status doesn’t appear in HomeKit either. So literally, it’s like nothing with security is actually making it into HomeKit, arm requests or status. On Sep 11, 2023, at 7:37 PM, Paul Wilkinson ***@***.***> wrote:
Does your key code begin with a 0 by any chance? I just noticed an inconsistency in the plugin between defining the keypad code as an integer and a string. As an integer any leading 0 would be lost.
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you commented.Message ID: ***@***.***>
|
Hello,
Would like to be able to trigger Homekit automation (turn on lights, etc.)when ELK alarm is triggered. Is this possible using this plugin?
Thank you!
The text was updated successfully, but these errors were encountered: