New User, Trouble with Kwikset 910 locks

Configuration Z-Wave
1

I am brand new to Home Assistant but coming from Smartthings, so not new to IoT and Home Automation.

I was able to successfully transfer all my devices from my Smartthings setup to HA without issue (various bulbs, switches, Hue Hub, plugs, etc. with Z-Wave, Zigbee, and WiFi).

However, I have two Kwikset smart locks (Kwikset 910’s) that were working fine with ST, but which I can’t get to work in HA:

  • One of them immediately gets recognized by HA and added as a new node, but it has two entities which are both greyed out (one with no additional “name” with a state of “LOCK” and the other is “state” with a state of “unavailable”). HA status says “Dead” for this Node. I tried to “re-interview” it, but it only gets as far as “ProtocolInfo” before giving the message: “The device interview failed. Additional information may be available in the logs.”
  • The second lock isn’t recognized at all. When choosing to add a node, whether I use “Secure” or not, it just sits in the “Add A Z-Wave Node” screen. For this one, I did try moving the HA about 1 ft from the lock and retrying without success.

I reset both of them so they were not associated with a Z-Wave network and then added to HA:

I am using an RPi 4 with an SSD and RASSIO with a GoControl HUSBZB-1 Zigbee/ZWave hub.

I’m not sure where to look for the logs from the ZWave activities, nor what I should be looking for.

Any ideas on what to look at or where to go from here would be greatly appreciated.

Thanks in advance!

2

Did you use “add secure

Also must set Zwave network key

3

I tried both add secure and without. Also, I’m using Z-Wave JS, which sets a network key.

This is the log for re-interviewing the lock that is found but not responsive:

2021-05-25T02:37:20.053Z CNTRLR   [Node 011] Beginning interview - last completed stage: None
2021-05-25T02:37:20.054Z CNTRLR   [Node 011] new node, doing a full interview...
2021-05-25T02:37:20.055Z CNTRLR » [Node 011] querying protocol info...
2021-05-25T02:37:20.078Z CNTRLR « [Node 011] 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:     40000 kbps
                                  protocol version:      3
2021-05-25T02:37:20.082Z CNTRLR   [Node 011] Interview stage completed: ProtocolInfo
2021-05-25T02:37:20.083Z CNTRLR » [Node 011] querying node info...
2021-05-25T02:37:20.198Z DRIVER     no handlers registered!
2021-05-25T02:37:21.467Z DRIVER   Dropping message with invalid data (Reason: Invalid auth code, won't accept se
                                  curity encapsulated command.):
                                  0x011e0004000b18988148ff1250da9d1eaa27476ce58ff5c9eae2765a16010b8b
2021-05-25T02:37:21.485Z CNTRLR « [Node 011] node info received
                                  supported CCs:
                                  · Manufacturer Specific
                                  · Version
                                  · Security
                                  controlled CCs:
2021-05-25T02:37:21.494Z CNTRLR   [Node 011] Interview stage completed: NodeInfo
2021-05-25T02:37:21.495Z CNTRLR » [Node 011] querying securely supported commands...
2021-05-25T02:37:32.993Z CNTRLR   [Node 011] did not respond after 1/3 attempts. Scheduling next try in 500 ms.
2021-05-25T02:37:41.029Z CNTRLR   [Node 011] did not respond after 2/3 attempts. Scheduling next try in 500 ms.
2021-05-25T02:37:49.060Z CNTRLR   [Node 011] Node 11 did not respond after 3 attempts, it is presumed dead
2021-05-25T02:37:49.062Z CNTRLR   [Node 011] The node is now dead.
2021-05-25T02:37:49.067Z CNTRLR   [Node 011] Interviewing Manufacturer Specific...
2021-05-25T02:37:49.067Z CNTRLR » [Node 011] querying manufacturer information...
2021-05-25T02:37:49.069Z CNTRLR » [Node 011] pinging the node...
2021-05-25T02:37:49.785Z CNTRLR   starting inclusion process...
2021-05-25T02:37:56.571Z CNTRLR   [Node 011] Node 11 did not respond after 1 attempts, it is presumed dead
2021-05-25T02:37:56.579Z CNTRLR   [Node 011] ping failed: Failed to send the command after 1 attempts (Status No
                                  Ack)
2021-05-25T02:37:56.580Z CNTRLR   [Node 011] Interview attempt (1/5) failed, node is dead.

Paul

4

And here is the log for the unresponsive one (not much to see):

2021-05-25T02:38:33.029Z CNTRLR   starting inclusion process...
2021-05-25T02:38:33.050Z CNTRLR   handling add node request (status = Ready)
2021-05-25T02:38:33.051Z CNTRLR     the controller is now ready to add nodes
2021-05-25T02:39:02.461Z CNTRLR   stopping inclusion process...
2021-05-25T02:39:02.527Z CNTRLR   handling add node request (status = Done)
2021-05-25T02:39:02.528Z CNTRLR   done called for 11
2021-05-25T02:39:02.529Z CNTRLR   the inclusion process was stopped

Paul

5

Add secure is what you want. Don’t bother trying other way

Factory reset and readd would be my suggestion but loookd like you tried that.

The one connected in first log was Not added as secure?

Could distance from controller be an issue here? Don’t use Zwave js but I’d expect it may show some stat for “response time” or “message retry”, things that indicate communication trouble. Specifically in case of second since it never connect