Kwikset wont add to HS3 - Solved!

[surovich]

Using the Zwave 3 plugin and 3.0.0.13 - Any attempt to add my Zwave lock fails with the security :

Done. Node 53 Added.
Synchronizing node information with HomeSeer and creating new device(s) as necessary...
Synchronize nodes finished. Number of device nodes to be created/added = 1
Device synchronization does not need to create any new SECURE devices.
Negotiating or Verifying SECURITY SCHEME for node 53
Warning: Failed to get a SECURITY SCHEME or verify the key from node 53. Device may not be added properly to HomeSeer.
Warning: The security device may have a timeout when adding to the network, bring the device close to HomeSeer and use the Add Node button to add it (remove it first)
Warning: If this device was previously added to the network, the device may need to be removed from the network and re-added.
Warning: In case the device was previously added successfully, an attempt will be made to continue the import.
Getting SECURITY class information for node 53
Error: Security class information is NOT present - cannot continue loading node 53
Device synchronization needs to create 1 Non-Secure device.

This did work previously in HS2 - Any ideas? I have the Aeon Stick right next to the lock, direct connect to the PC

[cleanclothes26]

Stumbled into a work around

I had the same problem that surovich mentioned and pretty sure this was mentioned before. I'm running HS3 3.0.0.34 with ZWave 3.0.0.8 and was unable to sucessfully add the Kwikset locks to the network. I kept getting the same Security class error. I would do exactly what the instructions say, detach your usb controller (Aeon Labs and Z-Troller) from your PC, include the device, reattach add... etc... that doesn't even get close to working.

I guess the range on the Z-Troller is good enough so when I used the Add/Include Node through the web-interface; it negotiated and communicated with the lock. I dunno if all of the functionality is working (as it is my first lock, sigh) but it seems to be working ok.

Just an FYI as to what seemed to work for me.

[Kmehring]

I've done it all through the interface with the lock 3" away from ztroller and get the following error:

Operational messages will appear here...
Add Node started...
Activate the 'Add to Network' (Send NodeInfo) function on the node while it is close to your HomeSeer interface...
A new node has been found and is being added...
Adding a new SLAVE NODE...
Replication protocol transfer done - waiting for application specific replication (if any) to finish.
Node 92 Added.
DONE - Add Node Operation is Complete.
Done. Node 92 Added.
Synchronizing node information with HomeSeer and creating new device(s) as necessary...
Synchronize nodes finished. Number of device nodes to be created/added = 1
Device synchronization needs to create 1 SECURE device.
Z-Wave manufacturer information for node 92, ID: 144=90H (Black & Decker), Type: 1=1H, ID: 1=1H
Negotiating or Verifying SECURITY SCHEME for node 92
Warning: Failed to get a SECURITY SCHEME or verify the key from node 92. Device may not be added properly to HomeSeer.
Warning: The security device may have a timeout when adding to the network, bring the device close to HomeSeer and use the Add Node button to add it (remove it first)
Warning: If this device was previously added to the network, the device may need to be removed from the network and re-added.
Warning: In case the device was previously added successfully, an attempt will be made to continue the import.
Getting SECURITY class information for node 92
Error: Security class information is NOT present - cannot continue loading node 92
Device synchronization does not need to create any new Non-Secure devices.
Enabling Lock status for Kwikset device Z-Wave Node 92 Z-Wave Interface Black & Decker Door Lock Node 92 (92)
Reloading (importing) node information from the controller...
Finished with Replication process.
Saving network information to file: C:\Program Files (x86)\HomeSeer HS3\Data\Z-Wave\ZNet_Network 003D23CD_003D23CD_2013-11-24_13.40.38.ZWave. Please wait...
Done!


with the following system:

System Information
Current Date/Time: 11/24/2013 1:43:18 PM US Mountain Standard Time
HomeSeer Version: HS3 Pro Edition 3.0.0.44 (Windows)
HomeSeer: Is Registered
HomeSeer Localization: English (United States)
Operating System: Microsoft Windows 7 Ultimate - Work Station
OS Version: 6.1.7601 Service Pack: 1.0
System Uptime: 0 Days 2 Hours 26 Minutes 5 Seconds
User Name and Access Level: default (Admin)
LAN IP Address: 192.168.168.95 (Media-PC)
Client IP Address: 192.168.168.95 (Media-PC.main.miski.int)
External IP Address: 208.86.126.120 (cc_p3_prem_s1_dhcp21.westernwimax.net)
Network Adapter: HomeSeer Adapter -> Realtek PCIe GBE Family Controller IP: 192.168.168.95/24 MAC: C8:60:00:CF:007
Network Adapter: HomeSeer Adapter -> Loopback Address (localhost) IP: 127.0.0.1
Web Server Port: 80
Number of Devices: 140
Number of Events: 23
Event Last Ran: Lights : GarageHallLightOn, Ran at 11/24/2013 12:20:01 PM
Number of unique event scripts used: 0

Connected Speaker Clients: MEDIA-PC (127.0.0.1)EFAULT
Plug-Ins Enabled: HSTouch Server:,GlobalCache:,Z-Wave:,BLFloorplan:,BLVolume:
Processor Type and Speed: AMD64 Family 21 Model 1 Stepping 2 at 3.35 GHz
Modules/Threads: 124 Modules, 69 Threads
System Processes/Load: 81 Processes, 15% Load
Free / Total Physical Memory: 12.39 GBytes / 15.73 GBytes (79% free)
Free / Total Virtual Memory: 27.80 GBytes / 31.46 GBytes (88% free)
HomeSeer Memory Used: 89 Mbytes
Plug-In Memory Used: 5 EXE Plug-Ins using 130 Mbytes

[Rupp]

I got the same issue. Did you ever get this to work? Very frustrating.

What version of HS are you running?

[Raptor]

I had the same issue. updating to zwave .150 beta allowed me to add the lock.

[CodeCaptain]

I've tried to pair the device through the Z-Stick as well as bringing the lock right next to the HS device. No luck either way. When I clicked 'Rescan' in the Z-Wave tab under the device, it was able to pull in the correct graphic, but I still have no options.

HomeTroller SE3: HS3 version 3.0.0.96

- Z-Wave Warning Product Information did not identify a polling interval to be set for Z-Wave Node 28 Z-Wave Interface Sigma Door Lock Node 28 and it does not appear to be associated with the interface Z-Wave Interface.
- Z-Wave Enabling Lock status for Kwikset device Z-Wave Node 28 Z-Wave Interface Sigma Door Lock Node 28 (28)
- Z-Wave Device synchronization does not need to create any new Non-Secure devices.
- Z-Wave Error Security class information is NOT present - cannot continue loading node 28
- Z-Wave Getting SECURITY class information for node 28
- Z-Wave Warning In case the device was previously added successfully, an attempt will be made to continue the import.
- Z-Wave Warning If this device was previously added to the network, the device may need to be removed from the network and re-added.
- Z-Wave Warning The security device may have a timeout when adding to the network, bring the device close to HomeSeer and use the Add Node button to add it (remove it first)
- Z-Wave Warning Failed to get a SECURITY SCHEME or verify the key from node 28. Device may not be added properly to HomeSeer.
- Z-Wave Error Z-Wave was unable to negotiate a compatible security scheme with node 28
- Z-Wave Negotiating or Verifying SECURITY SCHEME for node 28
- Z-Wave Device synchronization needs to create 1 SECURE device.

[CodeCaptain]

FYI - I also tried with the Beta version of the Z-Wave plugin - currently 3.0.0.158. No luck.

For what it's worth this connects fine through my micasaverde unit.

[Rupp]

These locks are very hard to add as the security scheme takes a bit of time to negotiate. As Rick (the Z-Wave developer) stated in another thread tonight, if you have issues adding this lock turn off any Z-Wave polling that may be taking place as this can interrupt the process. It may take several tries to add but these do work with HS. Also ensure the unit is awake when adding and only add locks using the add node software function within HS.

[CodeCaptain]

Thanks Rupp.

I finally got it working by:

1. Removing the node from HS3 through the user interface (keeping the lock close to the unit)
2. Adding the Kwikset lock back in to the micasaverde gateway
3. Removing the node from the micasaverde gateway z-wave controller (instead of just deleting it from the UI)
4. Added the node from the HS3 UI as I had tried before (keeping the lock close to the unit). This still gave me the security class error.
5. I then went into the device settings and clicked Audit Node
6. I then clicked on Rescan

For what it is worth, I thought I reset the Kwikset lock by removing the battery pack and pressing the program button 3x, but perhaps that didn't really clear everything I needed...?

All is good now. Thank you.

[bgrice33]

I tried all of that

All,

I have tried adding these locks repeatedly and never have they added to homeseer 3. I basically am at a point where these things do not work with homeseer. I can see that other people have added them with success however I have not. There was a time in HS2 when I could do this, but not now. I have tried the up close include method hundreds of times. It never negotiates the security scheme. Is there a better lock that is more compatible with HS3?

I'm running Hs3 3.0.0.96
Ztroller with latest firmware
Zwave 3.0.0.136

Thanks for any help you guys can give.

[CodeCaptain]

bgrice33, have you tried installing the Z-Wave Beta plugin? (3.0.0.158)

[sparkman]

All,

I have tried adding these locks repeatedly and never have they added to homeseer 3. I basically am at a point where these things do not work with homeseer. I can see that other people have added them with success however I have not. There was a time in HS2 when I could do this, but not now. I have tried the up close include method hundreds of times. It never negotiates the security scheme. Is there a better lock that is more compatible with HS3?

I'm running Hs3 3.0.0.96
Ztroller with latest firmware
Zwave 3.0.0.136

Thanks for any help you guys can give.

Have you tried the steps in post #4 of this thread: http://board.homeseer.com/showthread.php?t=167500? I would also recommend upgrading to a later version of the z-wave plugin as there were quite a few fixes since .136.

Cheers
Al

[dbrunt]

Using the Zwave 3 plugin and 3.0.0.13 - Any attempt to add my Zwave lock fails with the security :

Done. Node 53 Added.
Synchronizing node information with HomeSeer and creating new device(s) as necessary...
Synchronize nodes finished. Number of device nodes to be created/added = 1
Device synchronization does not need to create any new SECURE devices.
Negotiating or Verifying SECURITY SCHEME for node 53
Warning: Failed to get a SECURITY SCHEME or verify the key from node 53. Device may not be added properly to HomeSeer.
Warning: The security device may have a timeout when adding to the network, bring the device close to HomeSeer and use the Add Node button to add it (remove it first)
Warning: If this device was previously added to the network, the device may need to be removed from the network and re-added.
Warning: In case the device was previously added successfully, an attempt will be made to continue the import.
Getting SECURITY class information for node 53
Error: Security class information is NOT present - cannot continue loading node 53
Device synchronization needs to create 1 Non-Secure device.

This did work previously in HS2 - Any ideas? I have the Aeon Stick right next to the lock, direct connect to the PC

I just went through this with my Kwikset Spectrum Brands Deadbolt in HS4...device failed to negotiate security scheme. I could add it non-secure but I was perplexed and continued research. A factory reset was suggested somewhere so I found this post at Kwikset support on how to do it. After the factory reset the device added properly in secure mode AND via z-tool+.