Kwikset 910 no longer working after Z-Wave JS upgrade

Hardware
1

I just upgraded my system from the deprecated to to the Z-Wave JS integration. Everything went smoothing except that I didn’t take note of my network key (yeah, I know!). So my Kwikset locks are currently recognized by the system, but I just cannot get them to work. I figured I just need to re-pair them, but nothing has worked. The Z-Wave JS server has a generated network key. I have tried re-pairing the lock, factory reseting the lock, restarting HA, the integration and server after excluding and re-pairing. I have brought the locks to within 6" of the controller when pairing (I’m using a Aotech stick and a Synology/Docker as my server). I just cannot get this to work.

Here is the log. Says it is not secure, but I don’t know why.

2021-09-06T17:33:02.104Z CNTRLR [Node 020] Beginning interview - last completed stage: None
2021-09-06T17:33:02.104Z CNTRLR [Node 020] new node, doing a full interview…
2021-09-06T17:33:02.105Z CNTRLR » [Node 020] querying protocol info…
2021-09-06T17:33:02.164Z CNTRLR « [Node 020] received response for protocol info:
basic device class: Routing Slave
generic device class: Entry Control
specific device class: Secure Keypad Door Lock
node type: Routing End Node
is always listening: false
is frequent listening: 1000ms
can route messages: true
supports security: false
supports beaming: true
maximum data rate: 100000 kbps
protocol version: 3
2021-09-06T17:33:02.253Z CNTRLR [Node 020] Interview stage completed: ProtocolInfo
2021-09-06T17:33:02.253Z CNTRLR » [Node 020] querying node info…
2021-09-06T17:33:02.309Z CNTRLR « [Node 020] node info received
supported CCs:
· Z-Wave Plus Info
· Manufacturer Specific
· Device Reset Locally
· Security
· Powerlevel
· Firmware Update Meta Data
controlled CCs:
2021-09-06T17:33:02.312Z CNTRLR [Node 020] Interview stage completed: NodeInfo
2021-09-06T17:33:02.313Z CNTRLR » [Node 020] Querying securely supported commands (S0)…
2021-09-06T17:33:12.474Z CNTRLR [Node 020] Timed out while waiting for a response from the node
2021-09-06T17:33:12.474Z CNTRLR [Node 020] The node was not granted the S0 security class. Continuing intervie
w non-securely.
2021-09-06T17:33:12.489Z CNTRLR [Node 020] Interviewing Manufacturer Specific…
2021-09-06T17:33:12.490Z CNTRLR » [Node 020] querying manufacturer information…
2021-09-06T17:33:12.544Z CNTRLR « [Node 020] received response for manufacturer information:
manufacturer: Spectrum Brands (0x90)
product type: 0x03
product id: 0x0238
2021-09-06T17:33:12.546Z CNTRLR [Node 020] Interviewing Version…
2021-09-06T17:33:12.546Z CNTRLR » [Node 020] querying the CC version for Version…
2021-09-06T17:33:22.593Z CNTRLR [Node 020] Timed out while waiting for a response from the node
2021-09-06T17:33:22.594Z CNTRLR [Node 020] CC version query for Version timed out - assuming the node supports
version 1…
2021-09-06T17:33:22.595Z CNTRLR » [Node 020] querying node versions…
2021-09-06T17:33:33.934Z CNTRLR [Node 020] Timed out while waiting for a response from the node
2021-09-06T17:33:33.936Z CNTRLR » [Node 020] querying CC versions…
2021-09-06T17:33:33.936Z CNTRLR » [Node 020] querying the CC version for Basic…
2021-09-06T17:33:45.197Z CNTRLR [Node 020] Timed out while waiting for a response from the node
2021-09-06T17:33:45.197Z CNTRLR [Node 020] CC version query for Basic timed out - assuming the node supports v
ersion 1…
2021-09-06T17:33:45.197Z CNTRLR » [Node 020] querying the CC version for Door Lock…
2021-09-06T17:33:56.530Z CNTRLR [Node 020] Timed out while waiting for a response from the node
2021-09-06T17:33:56.530Z CNTRLR [Node 020] CC version query for Door Lock timed out - assuming the node suppor
ts version 1…
2021-09-06T17:33:56.530Z CNTRLR » [Node 020] querying the CC version for User Code…
2021-09-06T17:34:07.806Z CNTRLR [Node 020] Timed out while waiting for a response from the node
2021-09-06T17:34:07.808Z CNTRLR [Node 020] CC version query for User Code timed out - assuming the node suppor
ts version 1…
2021-09-06T17:34:07.808Z CNTRLR » [Node 020] querying the CC version for Manufacturer Specific…
2021-09-06T17:34:19.084Z CNTRLR [Node 020] Timed out while waiting for a response from the node
2021-09-06T17:34:19.085Z CNTRLR [Node 020] CC version query for Manufacturer Specific timed out - assuming the
node supports version 1…
2021-09-06T17:34:19.086Z CNTRLR [Node 020] skipping query for Security (0x98) because max implemented versio
n is 1
2021-09-06T17:34:19.086Z CNTRLR » [Node 020] querying the CC version for Z-Wave Plus Info…
2021-09-06T17:34:30.394Z CNTRLR [Node 020] Timed out while waiting for a response from the node
2021-09-06T17:34:30.396Z CNTRLR [Node 020] CC version query for Z-Wave Plus Info timed out - assuming the node
supports version 1…
2021-09-06T17:34:30.396Z CNTRLR [Node 020] skipping query for Device Reset Locally (0x5a) because max implem
ented version is 1
2021-09-06T17:34:30.397Z CNTRLR [Node 020] skipping query for Powerlevel (0x73) because max implemented vers
ion is 0
2021-09-06T17:34:30.397Z CNTRLR » [Node 020] querying the CC version for Firmware Update Meta Data…
2021-09-06T17:34:41.670Z CNTRLR [Node 020] Timed out while waiting for a response from the node
2021-09-06T17:34:41.671Z CNTRLR [Node 020] CC version query for Firmware Update Meta Data timed out - assuming
the node supports version 1…
2021-09-06T17:34:41.821Z CNTRLR [Node 020] Embedded device config loaded
2021-09-06T17:34:41.823Z CNTRLR [Node 020] Interviewing Z-Wave Plus Info…
2021-09-06T17:34:41.824Z CNTRLR » [Node 020] querying Z-Wave+ information…
2021-09-06T17:34:43.108Z CNTRLR « [Node 020] received response for Z-Wave+ information:
Z-Wave+ version: 1
role type: SleepingListeningSlave
node type: Node
installer icon: 0x0300
user icon: 0x0300
2021-09-06T17:34:43.127Z CNTRLR [Node 020] Interviewing Door Lock…
2021-09-06T17:34:43.128Z CNTRLR » [Node 020] requesting lock configuration…
2021-09-06T17:34:53.194Z CNTRLR [Node 020] Timed out while waiting for a response from the node
2021-09-06T17:34:53.195Z CNTRLR » [Node 020] requesting current lock status…
2021-09-06T17:35:04.499Z CNTRLR [Node 020] Timed out while waiting for a response from the node
2021-09-06T17:35:04.512Z CNTRLR [Node 020] Interviewing User Code…
2021-09-06T17:35:04.513Z CNTRLR » [Node 020] querying number of user codes…
2021-09-06T17:35:15.801Z CNTRLR [Node 020] Timed out while waiting for a response from the node
2021-09-06T17:35:15.802Z CNTRLR [Node 020] Querying number of user codes timed out, skipping interview…
2021-09-06T17:35:15.825Z CNTRLR [Node 020] Interview stage completed: CommandClasses
2021-09-06T17:35:15.827Z CNTRLR [Node 020] Interview stage completed: OverwriteConfig
2021-09-06T17:35:15.828Z CNTRLR [Node 020] Interview completed
2021-09-06T17:35:15.829Z CNTRLR [Node 020] The node is ready to be used
2021-09-06T17:38:12.762Z CNTRLR [Node 020] Timed out while waiting for a response from the node
2021-09-06T17:38:31.514Z CNTRLR [Node 020] Timed out while waiting for a response from the node
2021-09-06T17:38:49.075Z CNTRLR [Node 020] Timed out while waiting for a response from the node

2

In order to include a device securely you must factory reset it first and the inclusion must complete within 15 seconds of starting. Some devices need a stronger than usual signal to meet these restrictions set by the standard.

3

I have tried reseting the lock and running the inclusion process as close and as fast as possible with the controller. It doesn’t seem to make any difference.

The log appears to initially show that it recognizes the lock as a secure device. However, between adding the node and the initial interview, “supports security” changed to “false”. There is something in that timeframe about Lifeline not being configured (not sure what this is).

2021-09-06T20:34:19.350Z CNTRLR handling add node request (status = Ready)
2021-09-06T20:34:19.351Z CNTRLR the controller is now ready to add nodes
2021-09-06T20:34:21.318Z CNTRLR handling add node request (status = NodeFound)
2021-09-06T20:34:21.550Z CNTRLR handling add node request (status = AddingSlave)
2021-09-06T20:34:22.275Z CNTRLR handling add node request (status = ProtocolDone)
2021-09-06T20:34:22.276Z CNTRLR stopping inclusion process…
2021-09-06T20:34:22.336Z CNTRLR handling add node request (status = Done)
2021-09-06T20:34:22.336Z CNTRLR done called for 24
2021-09-06T20:34:22.337Z CNTRLR finished adding node 24:
basic device class: Routing Slave
generic device class: Entry Control
specific device class: Secure Keypad Door Lock
supported CCs:
· Basic (0x20)
· Door Lock (0x62)
· User Code (0x63)
· Manufacturer Specific (0x72)
· Security (0x98)
· Version (0x86)
· Z-Wave Plus Info (0x5e)
· Device Reset Locally (0x5a)
· Powerlevel (0x73)
· Firmware Update Meta Data (0x7a)
controlled CCs:
2021-09-06T20:34:22.338Z CNTRLR » [Node 024] Assigning SUC return route…
2021-09-06T20:34:22.346Z CNTRLR the inclusion process was stopped
2021-09-06T20:34:24.184Z CNTRLR [Node 024] Cannot configure Z-Wave+ Lifeline association: Node does not suppor
t associations…
2021-09-06T20:34:24.188Z CNTRLR [Node 024] Beginning interview - last completed stage: None
2021-09-06T20:34:24.189Z CNTRLR [Node 024] new node, doing a full interview…
2021-09-06T20:34:24.189Z CNTRLR » [Node 024] querying protocol info…
2021-09-06T20:34:24.207Z CNTRLR « [Node 024] received response for protocol info:
basic device class: Routing Slave
generic device class: Entry Control
specific device class: Secure Keypad Door Lock
node type: Routing End Node
is always listening: false
is frequent listening: 1000ms
can route messages: true
supports security: false
supports beaming: true
maximum data rate: 100000 kbps
protocol version: 3
2021-09-06T20:34:24.224Z CNTRLR [Node 024] Interview stage completed: ProtocolInfo
2021-09-06T20:34:24.225Z CNTRLR » [Node 024] querying node info…
2021-09-06T20:34:24.278Z CNTRLR « [Node 024] node info received
supported CCs:
· Z-Wave Plus Info
· Manufacturer Specific
· Device Reset Locally
· Security
· Powerlevel
· Firmware Update Meta Data
controlled CCs:
2021-09-06T20:34:24.279Z CNTRLR [Node 024] Interview stage completed: NodeInfo
2021-09-06T20:34:24.280Z CNTRLR » [Node 024] Querying securely supported commands (S0)…
2021-09-06T20:34:34.381Z CNTRLR [Node 024] Timed out while waiting for a response from the node
2021-09-06T20:34:34.381Z CNTRLR [Node 024] The node was not granted the S0 security class. Continuing intervie
w non-securely.

4

I would try opening a discussion on the node-zwavejs GitHub repo.