How to detect elk users in the isy.

[jwddsinc]

This is a poor man's approach, but given the programming limitations it will suffice as a workaround.

 

The approach is very straight forward and can be adapted to getting other information from the elk that isnt yet available though the ISY interface. This technique involves using outputs from the elk system to trigger events in the ISY. So for this example to determine which user disarmed the system try the following:

 

Create or modify an existing rule in the elk system:

WHENEVER yoursystem (Area #) ARM STATE BECOMES DISARMED

AND LAST USER WAS employee (User #)

THEN TURN Output # ON FOR 10 SECS, RESTART TIMER IF RUNNING

 

Output # is whatever you want to assign to that employee I started at output 100 and used 101 for employee 1 etc.

 

Next step is to create a notification and program in the ISY to catch the output trigger in the elk, like this:

 

Custom Notification:

 

Subject: hard code your employee's name here,

 

Body: employee's name disarmed the system, status:${elk.area.1.alarmState} ${elk.area.1.armedState}

 

${sys.date}

${sys.time12}

 

____________________________________________________________________

 

ISY PROGRAM

 

IF

Elk Area 'your system' 'Armed State' is Disarmed

And Elk Output 'Output # you used for that employee' is On

 

Then

 

Send Notification to 'you' content 'custom message for that employee'

 

 

_____________________________________________________________________

 

using this approach you can capture almost any data in the elk not yet visible in the ISY though it could be a bit laborious if you have a lot of employees. If you are limited by the number of outputs available consider using more than one output to define an employee for example with only 5 outputs available you could control 2 to the 5th power or 32 employees, then just change your rules and program's to reflect the additional outputs.

 

I also receive a text message from the isy instead of an email by using this format for the email: 310#######@txt.att.net you can check with your own service provider on their format for converting emails to text messages.

 

Good luck

[PurdueGuy]

Ah, another 310 guy here? Or at least, you were!

 

Just a quick tip...if you use 310#######@mms.att.net you might like the format better.

[jwddsinc]

Thats a great tip about the mms. Thanks!