Equipment List for ElkM1 ZWave Door Lock Support

[wuench]

So I am reading up on the whole M1 support for ZWave door locks and thinking about if it would be a good fit for my setup. I have an almost complete Insteon installation, so zero current ZWave devices and not really looking to replace what I have.

Right now I understand I would need:

Elk ZWave Interface - M1XSLZW
Leviton VRCOP+3 ZWave Interface - VRC0P-1LW

Would I need any other equipment besides the locks? And when kind of range could I expect with only the VRCOP and no other repeaters to help me select the best location?

 

[gatchel]

Not to discourage, but for whaterver reason the manual for the M1XSLZW discourages using diffrent "lighting" technologies being used. It probably has to do with overlapping ID's in the system and accidentally unlocking a door or something similar.

I also think you need a primary zwave controller as the VRCOP+3 is only a secondary controller.


I would recommend downloading the manual for the M1 zwave interface and reading it 2 or 3 times as it is more complex than on would think, especially if you are not familliar with Zwave.

I have to say that I expected more from the Elk interface for direct control of Zwave products but I guess it is designed to play nice in an existing zwave system not be the main controller.

As for range, YMMV from what other posts I have read.

I really wanted to use the zwave locks also, but after considering the costs involved, I decided it wasn't worth it to unlock and lock 3 doors total. I could do it better with other proven, hardwired technologies.

Locks $200 to $300 each.
Zwave interface $150
VRCOP+3 $100 to $150
Primary controller VRUSB-1US $75 to $150
Other costs?

 

[wuench]

I have checked out the manual and it's many caveats. I am not thinking of using ZWave for lighting so the conflict may not be a problem, and I might be able to offload all lighting control to the ISY, I think I am almost there. This may all be academic if it ends up costing $1000+ just to control my door locks. I would bet by Elk not doing direct support, they would avoid all the ZWave licensing/certification fees/process issues.

So what would a primary controller be, one of those ZWave remote thingies?

EDIT: Crosspost Got it, I see the manual specifies the USB controller and software. I wish SH would just get it's act together and find some direction on two-way lock support. If I would've know I was gonna end up putting in "dualband" Insteon and needing wireless communication anyway I would've looked at ZWave a little deeper in the first place. It's just all seemed so complicated with needing a separate remote, and differences in brands, etc.

 

[video321]

I agree with the whole Zwave thing being complicated, especially at first. I was/am looking into using it to start off with a few lights and thermostat control, but then you have setup issues, controller compatability, mesh issues, and so on. The only thing I realized is I would not be installing a controller on the Elk panel itself as all that would accomplish is adding $150 to the cost for the serial adapter. For a few dollars more than the serial adapter alone I could just buy a Vera3 Lite, but their support forum has me steering away at this time. Since I have a 24/7 server I was looking to utilize that with Premise, but I would still need a primary controller and the Leviton serial controller since Premise doesn't support a USB controller.

 

[wuench]

Well I was looking at adding some keypad locks anyway, just thought I would get the zwave version if I did. Maybe i'll let you other guys be the guinnea pigs...
It also sucks the Schlage's don't support status updates, I expect more from them.

So this whole primary/secondary controller business... Is the primary controller just used for setup, or does it need to be running for the M1 Zwave to talk to the locks?

EDIT: Nevermind, I guess this answers that, Primary only needed for setup in my case...

Z-Wave Secondary Controller: A Secondary Controller (e.g. VRC0P+3) is able to communicate with and control devices
but it cannot be used to setup or configure devices. A Secondary Controller must receive a copy of the network configuration
from the Primary Controller in a step called Update Controller. I.E. The VRCOP+3 Controller must be Updated.

 

[gatchel]

I agree with all of you.
I am not trying to discourage anyone or offend anyone with the "read the manual" stuff but this is the first time I have read a manual in a long time and felt like "Wow I'd better read this a few times and highlight stuff"

I was definitely interested until I realized the scope of such a "simple" project.

I wish I had more answers. I don't. Maybe other zwaver's can help out on this one.



Its a darn shame that kwikset discontinued the old RF fob locks they used to have(ironically just before the Zwave stuff was released).

If they still had them it would be a simple RF remote hack to an Elk relay similar to BSR's garage door remote hack.

Those were the days...

I have actually considered using one of the keypad only deadbolts and hacking it so that I could used the "lock" button only. Since the lock button is a single press, one would just have to core the door, run some wire through a wire transfer hinge or door cord and tie it to a relay. That would at least lock the door which is about 70% for me...and potentially more reliable than the wireless options.

I could even direct solder power wires to the barrery terminals to power the device without using batteries...

 

[Del91574]

Gat,

I basically did the hack you mentioned on one of my doors. I didn't core the door, since it's solid wood and a transfer hinge wouldn't get me anywhere.

I have, besides Elk's weigand readers dumped into the keypads, Securitron Unlatch's (1 is for a tubular lockset, the other I have is for my old Yale mortise locks). I ran a long door loop into the lock itself, tied that to a 6V supply to do away with the alkaline's, then I have a MS-Sedco TDM wired into a trigger point off the M1. The trigger first fires the deadbolt, then fires the strike to unlock. There's a little other logic and outputs involved so the deadbolt can re-extend, but the basics work great.

We normally use the TDM's on Stanley automatic doors and access control to sequence them properly with the lock with many variation of the theme.

 

[ddennerline]

It will be expensive to setup Z-Wave lock only system – probably around $500 for single lock. Configuring a Z-Wave network is really not that big of a deal. You just have to get Leviton RF Installer, Leviton VRUSB, a laptop, and some good pair sneakers. The hardest part now is updating ElkRP lighting configuration as described in M1XSLZW manual. This procedure is more difficult compared to other technologies because Leviton RFIT configuration file cannot currently be imported as is the case with other lighting technologies.

I have not configured my Kwikset lock for Z-Wave control yet, but the motorized lock is quite handy even if just using the keypad. I was waiting until Elk released new Z-Wave module.

My only problem with Kwikset lock's design is only one lock (deadbolt or latch) can be controlled. Trying to install two motorized locks with keypads may present a tight fit (and look awkward). As a result, keys are frequently required. Ideally, Kwikset should have designed system so that one keypad could control two motorized locks.

I suspect I can install a Securitron Unlatch to fully eliminate keys. Once the Elk M1XSLZW receives the door unlock notification, a command can be sent to Unlatch.

The Kwikset Z-Wave lock uses the SmartLock keys. Locks can periodically be rekeyed without locksmith intervention. I switch all the locks over to SmartLock as they supposedly have a high level of security compared to older locks.