I'm having issues in trying to add a third Kwikset lock to my setup. I have a zwave network with over 50 nodes. The lock enrolls fine in my network, but I can not control it via a VRC0P interface (which is one the latest firmware). I control the other two fine via HAI OP2, but also can run the terminal program on my laptop and control it by sending the appropriate commands. I have done two others about a year ago and never had an issue (unless I'm forgetting something). The lock is line of site and I can swap out a zwave card from another unit and it works fine. This led me to get a replacement card from Kwikset. Same issue. It enrolls but is not controllable (via RF beaming). I use the Vizia RF+ installer tool to enroll and create the associations with the lock. I believe only oneway works using this setup (not reverse). I'm figuring it can't be another bad card, so maybe th size of my network, etc. might be an issue? Any help would be appreciated. Thanks. SJ
Kwikset Zwave Lock Problems
- Thread starter sjht
- Start date
ddennerline
Active Member
Have you tried to use some of the diagnostics from Leviton RFIT. I found that I my second lock (farthest from controller) is not reliably responding to commands. You can test communication between two devices.
What's frustrating is that Leviton RFIT doesn't have option to manipulate lock as is the case with lights.
After playing around with diagnostics, I am pretty certain I need to add a beaming node. I purchased a EV-LOM-15 this week instead of VRP03+3 dimmer. Maybe it will work just a good - if not back to VRP03+3.
What's frustrating is that Leviton RFIT doesn't have option to manipulate lock as is the case with lights.
After playing around with diagnostics, I am pretty certain I need to add a beaming node. I purchased a EV-LOM-15 this week instead of VRP03+3 dimmer. Maybe it will work just a good - if not back to VRP03+3.
Well, still no luck. I unrolled/enrolled the VRC0P, tried disconnecting from HAI. I can control the other two locks via HAI or my laptop sending commands directly to the interface. Something must be going on as I can't believe I would end up with two bad cards. The new card enrolls fine, I can show the network info including neighboring nodes, etc. Seems fine in my network. Just not able to control. I'm not reinstalling my network as that would be a huge undertaking. Any other ideas? I do have a couple of other VRC0Ps in the system. Wonder if they are causing issues....
Yes. I have tried disconnecting from HAI during updates. I have two VRC0Ps (+3s). One I used connected via serial to my HAI system. I used serial commands to directly control my two locks via serial commands dirctly from the HAI to the VRC0P. Always worked great. Got another VRC0P to hook up to replace an older (non +3 version) that I would use as the main zwave interface. This would allow me to use HAI Access Control to integrate the locks vs. serial commands. I bricked this unit in upgrading once and decided to get a backup. I upgraded the new VRC0P with the latest firmware (took several attempts, but it finally upgraded the firmware). I then enrolled the new unit into my network. When I do the RS232 assocations, both units fail during the association. My assumption is that the fail really occurs during the reverse association (which I know I can create using serial commands, but decided to do that later after things were working). However, either VRC0P can control the original two locks. The new one connected as my primary zwave interface and the old unit which I could control the locks via serial commands. Neither could control the new lock either using access control or serial commands. The serial commands are really straghtforward, but the new lock just does not respond back to the VRC0P which I can watch via my laptop terminal program. I can swap the zwave cards out of the locks and no matter what lock I put the original two cards into works fine. The new card does not. This led Kwikset to send me a new zwave card (from one of their engineers). The new card also does not work. Now the odds of getting two cards that are bad is not very likely. So, I'm at a loss at what is going on. Very strange. Assume there are no restrictions in the number of locks in a system. The new lock shows up fine in my network, I can get network information showing surrounding nodes, etc. Thanks for any suggestions.... SJ
Well I went back to square 1 which didn't help. Unenrolled both the new lock and both VRC0Ps. Enrolled the new lock, updated controllers,factory reset the VRC0P and the enrolled it. Updated the RS232 associations which gave error messages again. However, the VRC0P can still control the first two locks but not the new one. This is very strange. Think I will work on something else for awhile. 
. SJ
. SJdrvnbysound
Senior Member
I've had (2) Kwikset locks which I haven't been able to read into the Installer Tool software by the VRUSB. The first one I installed worked fine. The second one wouldn't respond or connect - so I had it exchanged. Upon receiving the second one... it wouldn't connect either. I haven't had time to mess with it anymore - it's been a while
This is obviously before I even get to the point of trying to update the VRCOP.
This is obviously before I even get to the point of trying to update the VRCOP.
Wouldn't connect to your network or couldn't control? My new one connects to my network just fine (shows up as a lock, etc.). However, I can not control the lock. Also, the new version of the installer tool seems to bomb out when I try and use it. Had to go back to the previous version to get things working for some reason. Wonder if that is an issue for me.... SJ
drvnbysound
Senior Member
I couldn't get the additional locks to connect to my network at all. Actually, I recall when I would set my laptop to add an additional device, and would press the button on the lock.. that I would get no indication (on the laptop) that I pressed the button at all. When adding other devices, there was always a blue indicator that showed that data was being transferred from the device to the VRUSB. I couldn't even get this with the additional locks... after getting the first one to be added properly without an issue.
Similar threads
