How can I with Elk M1, have a rule run based on which user entered the code?

ghurty

Active Member
I am looking through the rules on the Elk RP, to see if there is a way of triggering an html link based on which user entered the code.
Is this doable? I cant find in the elk rules how to see which user it was that entered the code.
 
Thanks
 
ghurty said:
I am looking through the rules on the Elk RP, to see if there is a way of triggering an html link based on which user entered the code.
Is this doable? I cant find in the elk rules how to see which user it was that entered the code.
 
Thanks
 
Whenever system is disarmed, and the last user was...
 
drvnbysound said:
Whenever system is disarmed, and the last user was...
Thank you. That should work. But what if the door is closed, but the alarm is not armed. What would the first whenever be? Also, I thought there was a way to have it run a url, but I dont see an option fir that
 
You can't have it run a html anything, you can send data out the serial port to another device that does as you wish (or triggered via rules).
 
You need to determine the conditions that would generate what you want it to do....whenever XX happens (change state, disarmed, etc).
 
Based on your initial post the rule would be whenever armed or disarmed and last user was XX. System doesn't care about state of the door but only if a code was used to cause it to change state. Another rule for "no code" would need to be used or disable quick arming.
 
Depends on the number of users of course... but you could create a flag for whenever alarm is disarmed and user is XXX then Set Counter 1 to 3; whenever alarm is disarmed and user is YYY then Set Counter 1 to 5
 
Without testing and/or being in front of RP I don't know if there's a "Last User" but at least that's a workaround that could set a flag letting you know who the last person was.
 
@ Work, there is a last user conditional as an AND boolean, but you'd need to do a conditional for armed and disarmed and the same for a quick arm (no code)
 
Maybe no html directly, but you could have the rule trigger a phantom output and that should show up in CQC with the current driver...  you should be able to get a CQC event off of that, not sure if there is an automatic event, but if not you can set a trigger on the Outputxxx field.
 
@DEL - makes sense - of course I have no idea of the use case so I don't know what the conditional trigger would be. 
 
Back
Top