ELK-7TS How Can I identify Which keep the native W7TS interface armed the system

[Eli Yaron]

Hello,

My M1Gold is integrated with HomeSeer Home automation system.  When using regular keypads I can trigger event on HomeSeer “When Keypad X Exit button was pressed”.  With the the W7TS interface this function does not work.  I need to create a rule that when the W7TS exit button was pressed, turn on virtual output Y for 1 minute.  This would let the HomeSeer know that Output Y was triggered, and it will be able to execute a script to unlock front door, turn on outside light if at night) and so on.  When I look at the M1 log, I see Area 1 armed by user 203.  User 203 is the default user that is passed since I am not requesting a user code when arming the system.  It is NOT the user # I assigned to the W7TS.

How can I set the W7TS to a specific user code, so I can trigger on it, or any other way to set the system to report to HomeSeer that the specific W7TS Armed the M! in away mode?

[Brad Weeks]

Are you wanting the Rule/Script to run based upon a specific User arming/disarming the system? If so under Areas un-check the “Quick Arm” option which will require a Code Entry to Arm the system instead of simple pressing Away/Stay. Under the 7TS setup a Valid User Code is required to validate the connection to the system but is not the Code that is logged when Arming/Disarming.

[Eli Yaron]

Thank you Brad for the answer.  What I am trying to do is identify which W7ts armed the system.  The one by the front door needs to unlock the front door and turn on front light at night  via integration to HomeSeer.  I can detect which keypad armed the system.  I am trying to do the same functionality using the W7TS.

[Brad Weeks]

The ELK 7TS is not an M1 Bus Devices so it isn’t possible to tell which 7TS Armed/Disarmed the system.

[Eli Yaron]

Brad,

Thank you for the answer.  I believe that the requirement for which keypad armed the system is obvious, and I wonder if we can bind a task to each W7ts Arm away, Arm Stay and also the function keys so based on the rules engine (Whenever Task X, then…).  This way we can identify the W7ts that called for the event.

[Author]

Posts