Trouble adding schlage door lock with ZwaveJS

Dudenell · March 28, 2021, 4:21am

Let me start out by saying I have a network that I migrated from open zwave 1.4 to ZwaveJS. I have two existing secure locks on the zwave network including another schlage lock.

I’m able to put the lock into inclusion mode, and my zwave network attempts to connect however it seems to be failing on creating a secure connection with the node which isn’t allowing it to be controlled via home assistant.

Some of my logs:

2021-03-28T04:11:28.757Z CNTRLR   [Node 061] Interview stage completed: ProtocolInfo
2021-03-28T04:11:28.757Z CNTRLR » [Node 061] pinging the node...
2021-03-28T04:11:28.789Z CNTRLR « [Node 061] ping successful
2021-03-28T04:11:28.789Z CNTRLR » [Node 061] querying node info...
2021-03-28T04:11:28.842Z CNTRLR « [Node 061] node info received
                                  supported CCs:
                                  · Z-Wave Plus Info
                                  · Security
                                  · Security 2
                                  · Transport Service
                                  · Supervision
                                  · Time
                                  · Application Status
                                  controlled CCs:
2021-03-28T04:11:28.843Z CNTRLR   [Node 061] Interview stage completed: NodeInfo
2021-03-28T04:11:28.843Z CNTRLR » [Node 061] querying securely supported commands...
2021-03-28T04:11:29.167Z CNTRLR « [Node 061] received secure commands
                                  supported CCs:
                                  · Anti-Theft
                                  · Association
                                  · Configuration
                                  · Battery
                                  · Door Lock
                                  · Notification
                                  · User Code
                                  · Schedule Entry Lock
                                  · Time
                                  · Supervision
                                  · Manufacturer Specific
                                  · Version
                                  · Firmware Update Meta Data
                                  · Application Status
                                  · Association Group Information
                                  · Device Reset Locally
                                  · Powerlevel
                                  · Indicator
                                  controlled CCs:
2021-03-28T04:11:29.167Z CNTRLR   [Node 061] The node is included securely.
2021-03-28T04:11:29.172Z CNTRLR   [Node 061] Interviewing Manufacturer Specific...
2021-03-28T04:11:29.172Z CNTRLR » [Node 061] querying manufacturer information...
2021-03-28T04:11:29.352Z DRIVER   Dropping message with invalid data (Reason: Nonce 0x93 expired, cannot decode 
                                  security encapsulated command.):
                                  0x01220004003d1c988116447daa996f9ab648aca391665b97ea3d93d7d95f9e03b8e9e8f3
2021-03-28T04:11:39.265Z CNTRLR   [Node 061] Timed out while waiting for a response from the node
2021-03-28T04:11:39.275Z CNTRLR   [Node 061] Interviewing Version...
2021-03-28T04:11:39.275Z CNTRLR » [Node 061] querying node versions...
2021-03-28T04:11:42.472Z CNTRLR « [Node 061] received response for node versions:
                                    library type:      Routing Slave (0x06)
                                    protocol version:  6.3
                                    firmware versions: 3.3
2021-03-28T04:11:42.472Z CNTRLR » [Node 061] querying CC versions...
2021-03-28T04:11:42.472Z CNTRLR » [Node 061]   querying the CC version for Door Lock...
2021-03-28T04:11:43.125Z DRIVER   Dropping message with invalid data (Reason: Nonce 0x17 expired, cannot decode 
                                  security encapsulated command.):
                                  0x011e0004003d1898815c29d8073393340f5e46d3e59c17eb47476ca5c76906c7
2021-03-28T04:11:52.826Z CNTRLR   [Node 061] Timed out while waiting for a response from the node
2021-03-28T04:11:52.826Z CNTRLR   [Node 061] CC version query for Door Lock timed out - assuming the node suppor
                                  ts version 1...
2021-03-28T04:11:52.827Z CNTRLR » [Node 061]   querying the CC version for User Code...
2021-03-28T04:11:54.717Z CNTRLR   [Node 061]   supports CC User Code (0x63) in version 1
2021-03-28T04:11:54.717Z CNTRLR » [Node 061]   querying the CC version for Manufacturer Specific...
2021-03-28T04:11:56.738Z CNTRLR   [Node 061]   supports CC Manufacturer Specific (0x72) in version 1
2021-03-28T04:11:56.738Z CNTRLR   [Node 061]   skipping query for Security (0x98) because max implemented versio
                                  n is 1
2021-03-28T04:11:56.738Z CNTRLR » [Node 061]   querying the CC version for Version...
2021-03-28T04:11:58.699Z CNTRLR   [Node 061]   supports CC Version (0x86) in version 2
2021-03-28T04:11:58.700Z CNTRLR » [Node 061]   querying the CC version for Z-Wave Plus Info...
2021-03-28T04:12:00.656Z CNTRLR   [Node 061]   supports CC Z-Wave Plus Info (0x5e) in version 2
2021-03-28T04:12:00.656Z CNTRLR   [Node 061]   skipping query for Security 2 (0x9f) because max implemented vers
                                  ion is 0
2021-03-28T04:12:00.656Z CNTRLR   [Node 061]   skipping query for Transport Service (0x55) because max implement
                                  ed version is 0
2021-03-28T04:12:00.657Z CNTRLR   [Node 061]   skipping query for Supervision (0x6c) because max implemented ver
                                  sion is 1
2021-03-28T04:12:00.657Z CNTRLR » [Node 061]   querying the CC version for Time...
2021-03-28T04:12:02.600Z CNTRLR   [Node 061]   supports CC Time (0x8a) in version 1
2021-03-28T04:12:02.600Z CNTRLR   [Node 061]   skipping query for Application Status (0x22) because max implemen
                                  ted version is 0
2021-03-28T04:12:02.601Z CNTRLR   [Node 061]   skipping query for Anti-Theft (0x5d) because max implemented vers
                                  ion is 0
2021-03-28T04:12:02.601Z CNTRLR » [Node 061]   querying the CC version for Association...
2021-03-28T04:12:04.621Z CNTRLR   [Node 061]   supports CC Association (0x85) in version 2
2021-03-28T04:12:04.621Z CNTRLR » [Node 061]   querying the CC version for Configuration...
2021-03-28T04:12:06.593Z CNTRLR   [Node 061]   supports CC Configuration (0x70) in version 1
2021-03-28T04:12:06.593Z CNTRLR » [Node 061]   querying the CC version for Battery...
2021-03-28T04:12:07.240Z CNTRLR   [Node 061]   supports CC Battery (0x80) in version 1
2021-03-28T04:12:07.241Z CNTRLR » [Node 061]   querying the CC version for Notification...
2021-03-28T04:12:09.263Z CNTRLR   [Node 061]   supports CC Notification (0x71) in version 8
2021-03-28T04:12:09.263Z CNTRLR   [Node 061]   skipping query for Schedule Entry Lock (0x4e) because max impleme
                                  nted version is 0
2021-03-28T04:12:09.264Z CNTRLR » [Node 061]   querying the CC version for Firmware Update Meta Data...
2021-03-28T04:12:11.295Z CNTRLR   [Node 061]   supports CC Firmware Update Meta Data (0x7a) in version 3
2021-03-28T04:12:11.295Z CNTRLR » [Node 061]   querying the CC version for Association Group Information...

Any ideas?

Bartem · March 28, 2021, 4:37am

Have you tried new batteries by chance? I had a lot of trouble with one of mine… a fresh set of batteries took care of the issues I was having with inclusion.

Dudenell · March 28, 2021, 5:13am

Brand new batteries, brand new lock. Looks to be related to this:

I think I’m going to try the following

Make a snapshot
Roll back to old snapshot with openzwave 1.4
Add the node securely
Roll back to the snapshot I took in step 1

Bartem · March 28, 2021, 5:34am

Okay… I see you have came to your own conclusion but I’m just gonna throw this out there only because it happened to me with 2 Schlage locks and this is how I’m aware of the issue…
if you are using the batteries that came prepackaged with the lock from Schlage… get new ones… I fought with my front door for literally a day and a half… was using “new” batteries that came with the lock… could not get it included no matter what… threw some new batteries that I had purchased myself in there and all my problems went away…

Other than that… good luck.

Dudenell · March 28, 2021, 4:14pm

One thing that I noticed was that adding my schlage lock when it was away from the hub caused timeout issues with some of the sensors / settings (after adding and excluding the node multiple times).
After moving the lock (only needed the back of the lock, not the front) less than a foot away from the zwave stick it added all of the missing information, however the lock still wouldn’t add securely (lock and unlock button was greyed out).

It was suggested on the discord server to try and heal the network first, however by that time I already solved the issue on my end.

My solution of adding the lock in securely an old snapshot with open zwave 1.4 and then restoring the snapshot I took before worked, but it was a total pain in the butt. Hopefully I don’t have to ever factory reset these locks.

Thanks for the help!