Originally posted by sparkman
View Post
Announcement
Collapse
No announcement yet.
Kwikset Lock cannot add security class - Solution!
Collapse
X
-
Originally posted by jschiesser View PostAny good ideas on how to work-a-round this? I swapped zwave cards between locks, rolled back to the production plug-in, installed from scratch on a fast windows PC, etc... No luck... Is there any debugging I can turn-on to provide the support team clues as to the source of the issue? Trade my usb stick for a z-net device?
Thanks!
(1). Call HST. Not email them -- call them.
(2). Trade your USB stick for a SmartStick or a Z-NET.
Comment
-
Z-Net is the solution
Originally posted by jschiesser View PostI ordered a Z-Net... I hope it works!
Comment
-
Originally posted by jschiesser View PostProblem solved! Old Aeon Labs network imported perfectly into my new znet, and I was immediately able to add my new lock! The only issue I noticed was I could not add the Z-Net interface unless I used a static IP. (not a big deal)
Comment
-
Originally posted by reidfo View PostI had a similar problem the last time I tried to include my Kwikset lock. I had added it many times before. I tried all the things previously mentioned but kept getting timeouts. What ended up working was bringing the lock to the controller, adding it, and pressing the inclusion button on the lock every couple of seconds while adding to keep it from timing out.
Wow ... that was crazy ... until I came across this thread. Thanks! It WORKED!
Comment
-
This worked for me
Slight bump here as this is a good thread on the Kwikset problems ....
Well, this approach worked for me (unfortunately, after I just bought a new Home Connect card for the problem lock/card).
I kept getting the following error message upon adding the lock.
Security class information is NOT present
HS3 would ONLY add the root device. So, I finally decided to RESCAN the device while pressing the program button (upper left of lock). The rescan then added the additional devices (lock, battery, notification, logging). Now the lock is working!
Painful process to say the least.
Comment
-
Hello,
Re-bumping this older thread as it is still viable in regards to what issues I'm having here.
I migrated my ZWave network from Vera Plus controllers over the past month. As expected, door locks were a chore to migrate, in particular with the security scheme. I got two Kwikset 910 (deadbolt) and one 912 (door knob) devices to successfully migrate over and have been working OK. The last 912 has seen the exact same issues as described in this thread. Parent device only. Cannot get the scheme/children devices to connect, making the entire unit useless on Homeseer.
So, I ordered a brand new 912. Same issues with not carrying over the security scheme. I tried with disabling polling, increasing timeout setting on ZWave interface, exclude, include, reset at the lock... Over and over and over.
Oddly, the same device that I have issues with in Homeseer bind quite nicely and with no issues with Vera Plus controller. Lockset is immediately adjacent to the ZStick+ while trying to perform the tasks. Tried this now no less than dozens of times.
This is super frustrating, as I'm trying to remove Vera from my automated set up. Now I have one door lock on Vera just because it just will not bind properly in Homeseer.
I'm using a brand new S6 Pro Hometroller and a Homeseer Smartstick +. My ZWave network is sizeable at just under 100 nodes, but my other nodes and devices have been settling in and functioning fairly well.
Any additional ideas on this issue?
Thanks!
Comment
-
So, I got a Z-Net just to see if it would help with these dang Kwikset locks. Same results. Just cannot pass the security scheme (tried 2 brand new locks).
It's hard to say if it's a Kwikset issue or a HomeSeer issue since I got three of the older ones to port over. Now, I have 3 more that won't.
Super frustrating. I pinged HS support and got a really poor canned reply displaying that whoever read my support request didn't even click on the link to this thread to see what I was talking about.
After dumping nearly $2000 in HS hardware/software, this is the level of support we get from them?
Comment
-
Kwikset Lock cannot add security class - Solution!
Originally posted by ududidj View PostYes, it is sitting right next to it. The lock is not even installed at this point.
Bringing the lock with fresh batteries an inch from the controller and using the z-net with the latest beta of the z-wave plug in is what did the trick for me. I wish I could be more helpful, sorry.
HS Tech support was very helpful in running it to ground with me, though, so if you have not called them yet (rather than email) that might be a good idea too?
Comment
-
Kwikset Lock Inclusion Issues
I recently had a mechanical issue with my 912 Kwikset lock set and Kwikset changed it out under warranty. When I tried to include the new lock, I ran into several of the issues raised in this forum. I have a Zee S2 which has the newer 500 series chip that allows including devices that are not immediately adjacent to the controller. My controller is about 8 ft from the lock but there is a wall corner between it and the controller. After working through them, I concluded that I had the following three issues to deal with:
1. Getting the lock security process to add successfully. The issue was, as reidfo suggested in an earlier posting, the lock was dropping out of program mode before the process was complete. I kept pressing the program button on the lock for about 30 seconds and the lock successfully included on the first try.
2. The child entries for the lock did not show up in the device list. I opened the Zwave node info page and found that the child entries were showing up in the Zwave interface. I clicked on one of the child entries to open it and that caused all the child entries to load into the device list in the controller. Alternatively you could do an import from the zwave interface to the controller.
3. The last issue was that once included, the lock immediately became non-contactable by the controller. In looking in the node information list, I saw that the route from the lock to the controller was not a direct route. I suspected that the route that showed was the route that the controller used when it found the lock during the inclusion process. The inclusion process appears to be a two step process where the lock is first found and added. In the second step, the encrypted signaling(beaming) is activated. I suspect that the route used during inclusion was set to travel through a device that did not support beaming and thus while the controller found and included the lock, the route did not support the beaming mode and the route between the lock and the controller broke as soon as it started using the beaming mode. A single device optimization try failed. I then performed a full optimization for the entire network. A new route showed in the node info list and the lock started working and has worked continued to work without further issue.
Comment
Comment