ELK M1G, Access Control and Multiple Keypads...?

[Invent]

So, here's something I can't seem to figure out, after reading here quite a bit. If I have an M1G with a couple of ELK keypads deployed (and used for what they typically are used for), then want to add a new ELK keypad that is specifically for access control (such as firing a door strike etc) - can this new keypad fire the door strike without disarming the alarm? Can the ELK identify unique codes for users from this new keypad, for use in rules?

In other words, can a specific ELK keypad be used for access control only, with unique user identification to control allowed access times, email access events with user identities in them, etc? All without affecting the rest of the system's operation?

Thanks in advance!

 

[Steve]

Welcome to CocoonTech! You should be able to do at least most of what you want. You may not be able to do the email with variables in it right now as email strings are fixed. Take a look at this and see if it is kind of what you're after...

 

[Digger]

If you use nextalarm you can pick up some of the email features you are looking for.

 

[Invent]

Steve - thanks for the welcome! And thanks for that link - it is close to what I want to do - but I'm trying to do this with actual keypads, not keyfobs of any type. Wife is concerned that the kids will lose them. Also we might want to give someone a code while we're away, to let them into the house, etc. So, I'd like to put a small ELK keypad in the front door jamb (to keep it safe from weather, but accessible when the storm door is opened).

Then, be able to give people access codes that unlock the door (standard output, used to fire a relay that drives the door release latch). I don't want this external keypad to actually disarm the system though - I have an interior ELK keypad for that. (I don't want a keypad openly accessible outside of the monitored/alarmed zone that could be used to disarm the system - for security)

So basically I assumed that I need to use an ELK keypad to get on the RS-485 bus (to get the individual codes to be recognized, which would not be possible with a 3rd party keypad) - but then could not figure out if you could just use this type of code

WHENEVER ACCESS Keypad 01(KP1) IS TRIGGERED
THEN TURN Door Strike (Out 7) ON FOR 10 SECS

to get what I want done - but modify it so that there is some recognition of unique user codes.

Perhaps this can be done with LAST USER? Something like this;

WHENEVER Area One (Area 1) ARMED STATE BECOMES DISARMED
AND THE LAST USER WAS Little Johnny (User 2)
THEN ARM AREA(S) 1 TO STAY IMMEDIATELY
THEN DIAL Mrs. Smith (5551234) AND ANNOUNCE Miscellaneous 1 (vm239)

this one is from this ELk newsletter: link

So, combining the two into

WHENEVER Area One (Area 1) ARMED STATE BECOMES DISARMED
AND THE LAST USER WAS Little Johnny (User 2)
THEN TURN Door Strike (Out 7) ON FOR 10 SECS

I guess the question then becomes, can I define a keypad to be in its own unique "Area" so that this area is being "disarmed" (although, there is nothing else in that "Area"), thereby using the above logic? i.e., for example "Area 1" has the entry keypad, and "Area 2" has several keypads used for arming/disarming the main house?

Feel like I'm getting closer, but still can't quite figure it out. (I'll forget about the email stuff for now, I'll start by figuring out this basic access control first)

Also thanks both Steve and Digger for your fast responses!

 

[Digger]

We wanted to let the kids get into the house without a key so I put in a Schlage keyless Access lock. Then once they are in they disarm the alarm and by their user code I know they are home (through an email from NextAlarm. If you have a maid etc you could restrict the times their user code would work to disarm the panel.

I think you dont even want the door opening during certian hours depending on who the person is and that is why you want the ELK to control the access. While I think it can be done it will not be cheap or as easy as the Schlage lock etc.

 

[mustangcoupe]

Im not sure but I think you could put this new keypad in a seperate "area" and then have the need to disarm the main area once they are in from a keypad in that area

 

[Spanky]

Invent,
You should be able to disable the Arm and Disarm capability of the Prox Card User Code. Make sure that single button arming is disabled.

Write Rules to control an output connected to the door strike for specific people and times of day.

You can use the M1KAM Access Module if you do not need an additional keypad. It has Prox and iButton reader capability as well as a relay output and switch input for access applications.

 

[Invent]

How 'bout this....

Seems like the ELK M!G is built to really use Weigand for access events.

What if I use something like this; click here

These appear to use a 26-bit Weigand compliant format. There are a bunch of them on the market, actually. I could then effectively have the keypad code entries look just like Weigand access fob events?

A little out of the box, I know, but perhaps this is a better path? The link that Steve supplied above hints at this, "One 26 bit Wiegand proximity reader or keypad can be installed "

 

[Spanky]

Any 26 bit Weigand reader keypad works with the M1. IEI, Rosslaire, etc.