Yale Lock - Detected but can't control it

So, I’m brand new to home assistant. I played around for a few days until I came to the wave integration. I ordered the Yale Lock and can’t get it to run. I use the S2 (ZST10) stick and started off with adding switches. All good with the switches, added a few more and no issues. Today I wanted to add the brand new Yale Lock. I paired it, it showed up. It shows me status locked (which does not change when I manually lock the door) and the control button for unlock is gray. Network key is set and I used secure inclusion (also tested it without, result exact the same).

So far:

  • I reseted the S2 stick
  • uninstalled Zwave JS and reinstalled it
  • added and removed the Lock a few times
  • googled and googled and not a step closer to a solution
  • I tested the lock with a 2GIG panel and it works fine when I add it there
  • tested multiple zwave+ switches without issue
  • started from scratch the zwave network, now only lock and USB stick

Home Assistant OS 5.13
core-2021.4.6
Z-Wave JS: 0.1.19
Driver Version: 7.2.3
Server Version: 1.4.0

2021-04-21T00:15:31.352Z DRIVER « [Node 002] [REQ] [ApplicationCommand]
                                  └─[ZWavePlusCCReport]
                                      version:      1
                                      node type:    Node
                                      role type:    SleepingListeningSlave
                                      icon (mgmt.): 0x0300
                                      icon (user):  0x0300
2021-04-21T00:15:41.157Z CNTRLR   [Node 002] Timed out while waiting for a response from the node
2021-04-21T00:15:41.157Z CNTRLR » [Node 002] requesting current lock status...
2021-04-21T00:15:41.173Z SERIAL » 0x01<removed partially>                                            (11 bytes)
2021-04-21T00:15:41.174Z DRIVER » [Node 002] [REQ] [SendData]
                                  │ transmit options: 0x25
                                  │ callback id:      25
                                  └─[DoorLockCCOperationGet]
2021-04-21T00:15:41.177Z SERIAL « [ACK]                                                                   (0x06)
2021-04-21T00:15:41.183Z SERIAL « 0x01<removed partially>                                           (6 bytes)
2021-04-21T00:15:41.184Z SERIAL » [ACK]                                                                   (0x06)
2021-04-21T00:15:41.186Z DRIVER « [RES] [SendData]
                                    was sent: true
2021-04-21T00:15:42.689Z SERIAL « 0x01<removed partially>00f5              (26 bytes)
2021-04-21T00:15:42.690Z SERIAL » [ACK]                                                                   (0x06)
2021-04-21T00:15:42.693Z DRIVER « [REQ] [SendData]
                                    callback id:     25
                                    transmit status: OK
2021-04-21T00:15:52.706Z CNTRLR   [Node 002] Timed out while waiting for a response from the node
2021-04-21T00:15:52.708Z CNTRLR   [Node 002] [+] [Door Lock] interviewComplete: true     [Endpoint 0] [internal]
2021-04-21T00:15:52.716Z CNTRLR   [Node 002] Interviewing User Code...
2021-04-21T00:15:52.717Z CNTRLR » [Node 002] querying number of user codes...
2021-04-21T00:15:52.773Z SERIAL » 0x010<removed partially>                                            (11 bytes)
2021-04-21T00:15:52.774Z DRIVER » [Node 002] [REQ] [SendData]
                                  │ transmit options: 0x25
                                  │ callback id:      26
                                  └─[UserCodeCCUsersNumberGet]
2021-04-21T00:15:52.777Z SERIAL « [ACK]                                                                   (0x06)
2021-04-21T00:15:52.784Z SERIAL « 0x01<removed partially>                                                       (6 bytes)
2021-04-21T00:15:52.785Z SERIAL » [ACK]                                                                   (0x06)
2021-04-21T00:15:52.787Z DRIVER « [RES] [SendData]
                                    was sent: true
2021-04-21T00:15:54.055Z SERIAL « 0x011<removed partially>0001b              (26 bytes)
2021-04-21T00:15:54.057Z SERIAL » [ACK]                                                                   (0x06)
2021-04-21T00:15:54.059Z DRIVER « [REQ] [SendData]
                                    callback id:     26
                                    transmit status: OK
2021-04-21T00:16:04.079Z CNTRLR   [Node 002] Timed out while waiting for a response from the node
2021-04-21T00:16:04.080Z CNTRLR   [Node 002] Querying number of user codes timed out, skipping interview...
2021-04-21T00:16:04.086Z CNTRLR   [Node 002] Interview stage completed: CommandClasses
2021-04-21T00:16:04.088Z CNTRLR   [Node 002] Interview stage completed: OverwriteConfig
2021-04-21T00:16:04.090Z CNTRLR » [Node 002] requesting node neighbors...
2021-04-21T00:16:04.102Z SERIAL » 0x010700<removed partially>                            (9 bytes)
2021-04-21T00:16:04.103Z DRIVER » [Node 002] [REQ] [GetRoutingInfo]
                                    remove non-repeaters: false
                                    remove bad links:     false
2021-04-21T00:16:04.106Z SERIAL « [ACK]                                                                   (0x06)
2021-04-21T00:16:04.109Z SERIAL « 0x012<removed partially>0000 (34 bytes)
                                  05f
2021-04-21T00:16:04.110Z SERIAL » [ACK]                                                                   (0x06)
2021-04-21T00:16:04.112Z DRIVER « [RES] [GetRoutingInfo]
                                    node ids: 1
2021-04-21T00:16:04.118Z CNTRLR « [Node 002]   node neighbors received: 1
2021-04-21T00:16:04.118Z CNTRLR   [Node 002] Interview stage completed: Neighbors
2021-04-21T00:16:04.118Z CNTRLR   [Node 002] Interview completed
2021-04-21T00:16:04.120Z CNTRLR   [Node 002] The node is ready to be used

I would greatly appreciate any info. This is letting my hair turn gray :smiley:

1 Like

Alright … After I posted that here I did another uninstall and I created a new network key … difference this time all CAPITAL … is works … OMG … I am not sure if that really was the issue and I don’t want to try lol but that was the only difference to the previous zwave config.