Enabling ELK M1G System with garage exit door open

[williamspl]

With my old security system, we could activate the system with the garage exit door open.

I though that the Force Armable feature would do the trick with the M1G, but when I tried it, I saw no change. The M1G system required the door to be closed to arm.

Am I missing something?

Thanks, Paul

 

[wuench]

You have to enter your code first, when arming the system, if any zones are violated. Force-armable just means it will come out of bypass automatically when the zone becomes secure.

 

[williamspl]

Great! Thanks for the feedback.

 

[video321]

FYI....
If you set a task for Arm Away you can do it without entering your code.
I have a slew of rules that work for arm/disarm, along with garage door control, tied into tasks that are triggered by a keyfob.

 

[apostolakisl]

FYI....
If you set a task for Arm Away you can do it without entering your code.
I have a slew of rules that work for arm/disarm, along with garage door control, tied into tasks that are triggered by a keyfob.

Really any rule for arming works with a force-arm zone open. I have some keyfobs which close a zone which trips an Elk rule to arm the system.

 

[video321]

Really any rule for arming works with a force-arm zone open. I have some keyfobs which close a zone which trips an Elk rule to arm the system.

Very true and that is how I had it setup until a few days ago when I realized that if I wanted more devices than just my keyfobs to trigger the actions I would need to basically duplicate every rule which led me to using a task instead. Now anything I desire can run down the list of arm/disarm rules. It just more efficient, but didn't think about it beyond what I was using at the time. So by saying "tasks" to the OP I was sort of planting that seed

 

[video321]

Forgot one thing - if you do use a rule to arm the system it will bypass any violated zones and arm anyway.
I have a rule to check for this before arming.

 

[apostolakisl]

Very true and that is how I had it setup until a few days ago when I realized that if I wanted more devices than just my keyfobs to trigger the actions I would need to basically duplicate every rule which led me to using a task instead. Now anything I desire can run down the list of arm/disarm rules. It just more efficient, but didn't think about it beyond what I was using at the time. So by saying "tasks" to the OP I was sort of planting that seed

Tasks are just callable subroutines. Since Elk has no "or" statements in the "if (whenever)" section, anytime you want more than one thing to have the same "then", and the "then" is more than one line long, you would save time and programming space defining it as a task. Plus tasks can be run from a keypad.

But if the "then" is only one line long and you don't care to execute the "then" from a keypad (or similar), then defining something as a task wastes space. And since space is fairly limited in Elk, saving space is pretty important. Although now that ISY has essentially full control of Elk, no more worries for us ISY owners.

 

[video321]

Good explanation, Lou.
My rule count for arm/disarm via the keyfob is somewhere around 15. All of this was being triggered by an input change tied to the keyfob and worked great until I thought.....hey, how am I going to do this if I want to use my smart phone (or any other device)? That's when I thought to change the keyfob input to trigger the "task" instead of the rules directly. So now anything can be tied into the system and start the "Arm Away" task and run down all the rules.