Page 1 of 1

[FEATURE REQUEST] Notifications of Who Disarmed?

PostPosted: Tue Mar 22, 2016 6:02 am
by pyrodex
I am not sure this is possible or not but today with ADT I am able to setup different codes based on users and receive SMS messages when they disarm/arm the system. I get the disarm/arm functionality with AlarmDecoder but I would like to know is it possible to map User's to IDs or Codes so when a specific code is used it could be used to map to friendly names?

For example:

Code 1234 = ID 1 = John Smith

Disarm Alert could be "$ID has disarmed the system at $TIME" and then in turn be "John Smith has disarmed system at 10:01AM on 3/22/2016"

Is this a feasible option to parse from the panel output the AlarmDecoder sees in the data stream?

Re: [FEATURE REQUEST] Notifications of Who Disarmed?

PostPosted: Tue Mar 22, 2016 8:45 am
by kevin
This has been on our todo list for a while - it is possible to get this information - with an LRR (Long Range Radio) present or emulated - we just have not found a good way to incorporate it yet where it would work for everybody.

Re: [FEATURE REQUEST] Notifications of Who Disarmed?

PostPosted: Mon Dec 26, 2016 9:51 pm
by R305
+1 on this feature request.

It might help to know that Envisalink gets this info from the panel. I dont know where it grabs this from though - maybe it flashes on the keypad quickly during disarm?. The disarm notification includes which user code did it, such as "User Code 2". Since the AD2PI is a computer rather than a microcontroller, it seems like a lookup table is feasible to put real names in as a field.

Re: [FEATURE REQUEST] Notifications of Who Disarmed?

PostPosted: Thu Dec 29, 2016 8:33 am
by kevin
The user data is only available in the LRR messages, period. While we could do a hackaround and have user inputted data into the webapp to do a "lookup table" it is not the solution we are going for in this case. We will use actual data from the panel and LRR messages to do so - the information is already there, just need time to implement it into the webapp itself. If you want this information, enable LRR and emulate it.