Kwikset Zwave Locks won't actuate

Configuration Z-Wave
1

I have 2 Kwikset 888 Zwave deadbolts. I am trying to get them to lock and unlock over zwave as well as report status. I think I have my zwave security set up properly and the locks do appear after doing the add node secure. However they always state they are unlocked and I cannot lock or unlock them from HA. Any ideas where to start?

Zwave configuration.yaml:
zwave:
usb_path: /dev/ttyUSB0
network_key: “0x49, 0x43, 0x1D, 0xBD, 0x03, 0x6D, 0x9D, 0x8C, 0x39, 0x67, 0x16, 0x82, 0xA8, 0x67, 0xEE, 0x91”

Log when I send the lock command:

2020-06-30 15:38:28.166 Info, Node010, Value::Set - COMMAND_CLASS_DOOR_LOCK - Locked - 0 - 1 - True
2020-06-30 15:38:28.166 Info, Node010, Value_Lock::Set - Requesting lock to be Locked
2020-06-30 15:38:28.166 Detail, Node010, Queuing (Send) DoorLockCmd_Set (Node=10): 0x01, 0x0a, 0x00, 0x13, 0x0a, 0x03, 0x62, 0x01, 0xff, 0x25, 0x39, 0x6f
2020-06-30 15:38:28.166 Detail, Node010, Queuing (Send) DoorLockCmd_Get (Node=10): 0x01, 0x09, 0x00, 0x13, 0x0a, 0x02, 0x62, 0x02, 0x25, 0x3a, 0x92
2020-06-30 15:38:28.166 Detail,
2020-06-30 15:38:28.166 Info, Node010, Sending (Send) message (Callback ID=0x39, Expected Reply=0x04) - DoorLockCmd_Set (Node=10): 0x01, 0x0a, 0x00, 0x13, 0x0a, 0x03, 0x62, 0x01, 0xff, 0x25, 0x39, 0x6f
2020-06-30 15:38:28.172 Detail, Node010, Received: 0x01, 0x04, 0x01, 0x13, 0x01, 0xe8
2020-06-30 15:38:28.172 Detail, Node010, ZW_SEND_DATA delivered to Z-Wave stack
2020-06-30 15:38:29.418 Detail, Node010, Received: 0x01, 0x05, 0x00, 0x13, 0x39, 0x00, 0xd0
2020-06-30 15:38:29.418 Detail, Node010, ZW_SEND_DATA Request with callback ID 0x39 received (expected 0x39)
2020-06-30 15:38:29.418 Info, Node010, Request RTT 1251 Average Request RTT 1261
2020-06-30 15:38:29.418 Detail, Expected callbackId was received
2020-06-30 15:38:38.167 Error, Node010, ERROR: Dropping command, expected response not received after 1 attempt(s)
2020-06-30 15:38:38.167 Detail, Node010, Removing current message
2020-06-30 15:38:38.167 Detail, Node010, Notification: Notification - TimeOut
2020-06-30 15:38:38.168 Detail,
2020-06-30 15:38:38.168 Info, Node010, Sending (Send) message (Callback ID=0x3a, Expected Reply=0x04) - DoorLockCmd_Get (Node=10): 0x01, 0x09, 0x00, 0x13, 0x0a, 0x02, 0x62, 0x02, 0x25, 0x3a, 0x92
2020-06-30 15:38:38.174 Detail, Node010, Received: 0x01, 0x04, 0x01, 0x13, 0x01, 0xe8
2020-06-30 15:38:38.174 Detail, Node010, ZW_SEND_DATA delivered to Z-Wave stack
2020-06-30 15:38:39.464 Detail, Node010, Received: 0x01, 0x05, 0x00, 0x13, 0x3a, 0x00, 0xd3
2020-06-30 15:38:39.464 Detail, Node010, ZW_SEND_DATA Request with callback ID 0x3a received (expected 0x3a)
2020-06-30 15:38:39.464 Info, Node010, Request RTT 1295 Average Request RTT 1278
2020-06-30 15:38:39.464 Detail, Expected callbackId was received
2020-06-30 15:38:48.169 Error, Node010, ERROR: Dropping command, expected response not received after 1 attempt(s)
2020-06-30 15:38:48.169 Detail, Node010, Removing current message
2020-06-30 15:38:48.169 Detail, Node010, Notification: Notification - TimeOut

2

Did you pair the locks using Add Secure Node ?

3

Yes I did, though mine only has the option for “Add Node Secure”. I’m assuming that’s the same thing?

4

Yes same thing, are these the only zwave devices you have?

5

It doesn’t appear the Network Key was set.

1 Like
6

Looking at my config file, can you point out what I did wrong? I was lost on how to make the network key so I just copied an example. I thought that would work.

7

I have zwave motion lights and switches that work perfectly, but they are not set up secure.

8

Don’t do that the docs tell you how to generate a key.

You should be configuring the zwave from the integrations menu not in the config file.

9

I see that command but where do I run it? In the SSH? I will go ahead and delete the zwave from the config file and go back to the integration menu. I had it there before but wanted to try it in the config file to see if it made it work better.

10

I ran it in the SSH and then manually typed it into a text document. It won’t let you copy from that window for some reason. I pasted into the Zwave integration. I also realized I missed that in the options file, so I removed the commenting from there and added the updated key. I’m assuming I will have to remove the locks from the network and re-add them?

11

Correct, make sure to use the secure add :slight_smile:

13

Most of the docs point you at the config files … the thing you linked says to edit the config files.
How do you even enter a key from the integration web page?

14

You don’t, you enter the config into your configuration.yaml as the docs instruct.

15

Did you ever get this working?
I also have a Kwikset 888 and cannot get it to actuate.
I’ve tried both the Zwave and new OpenZWave beta and both have the same results.
I have paired the device, add node secure, with the lock ~2" from the base transmitter.

I have a suspicion of what the issue is. These locks were mass produced for Vivint (and possibly other OEMs) and they have anti-theft enabled on them. Connecting it to a Vivint panel it goes through an anti-theft step and then the lock will actuate.

I got it! That was the problem. Also note that it was always showing 100% battery when it was added to the new z-wave network but anti-theft was in effect.

If you re-pair the lock with the Vivint panel then remove it it should disable anti-theft.
I added it back to the Vivint panel and verified it would lock/unlock.
I removed it from the Vivint panel.
I added it back to the Vivint panel - this time it asked me to name the device and prompted me to enable anit-theft which I declined to do.
I removed it from the Vivint panel.
I added it to my hassio z-wave and now it will lock and unlock.

I am currently running MQTT w/ the new OpenZWave but I suspect it would work with the released zwave as-long-as you update the zwave config files and get the kwikset 888.xml.

On my Vivint panel I touch the … on the Home screen then touch Software Version.
It prompts for the Install PIN which by default is 2203.
Smart Home Devices -> Zwave

16

I could never figure them out. I ended up returning them.