Adding Schlage Z-Wave smart lock fails during sync

I've read quite a few posts about this in the indigo forums as well as other HA forums concerning the Schlage lock. Seems like they can be finicky, but before I go buy a new one, I wanted to see if anyone had a similar issue and have a magic solution for me . For the record, I have an Aeotec Range Extender 7 that I use to connect to two z-wave devices which are in the closet that the Schlage lock is installed. For the record, I'm running 2022.2.0. I have a Aeotec Gen Stick 5+ with 20 or so devices on it working with no issues. And I made sure that when I did the initial inclusion via indigo, I used encryption. So I can see the schlage node as a node that hasn't been included yet when I go to add the new device, so it certainly seems like the inclusion worked. Here is the log when I try to sync.

Code: Select all

May 9, 2023 at 7:15:15 PM
   Z-Wave Debug                    intiatingSyncUI (timeout in 1500 seconds)
   Z-Wave                          Syncing - started for "025 - Keypad Door Lock"
   Z-Wave Debug                    SENT getNodeNeighbors: 01 06 00 80 19 01 01 60
   Z-Wave Debug                    RCVD getNodeNeighbors: 01 20 01 80 00 80 03 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 DD (no inbound callback)
   Z-Wave Debug                    . .  getNodeNeighbors: nodeId 025, neighbors: 16, 17, 18
   Z-Wave                          Syncing - retrieved module neighbors list: 16, 17, 18
   Z-Wave                          Syncing - assigning return route to "025 - Keypad Door Lock"
   Z-Wave Debug                    SENT assignReturnRoute: 01 05 00 46 19 01 A4
   Z-Wave Debug                    RCVD assignReturnRoute: 01 04 01 46 01 BD (no inbound callback)
   Z-Wave Debug                    RCVD assignReturnRoute: 01 05 00 46 01 00 BD
   Z-Wave Debug                    . .  assignReturnRoute: node 025, success 1
   Z-Wave                          Syncing - assigned return route
   Z-Wave Debug                    SENT requestNodeInfo: 01 06 00 60 19 24 5F FB
   Z-Wave Debug                    RCVD nodeInfoFrame: 01 10 00 49 84 19 0A 04 40 03 5E 98 9F 55 6C 8A 22 BE
   Z-Wave Debug                    . .  nodeInfoFrame: node 025, combined class list: 20v1 62v1 63v1 72v1 86v1 98v1 5Ev1 9Fv1 55v1 6Cv1 8Av1 22v1
   Z-Wave Debug                    SENT nonceRequest: 01 09 00 13 19 02 98 40 25 60 63
   Z-Wave Debug                    RCVD nonceRequest: 01 07 00 13 60 00 00 08 83 (node ACK)
   Z-Wave Debug                    RCVD nonceReport: node 025, nonce 98 5D D1 72 EC 68 2F 34
   Z-Wave Debug                    SENT requestEncryptedCmdClasses: 98 02 (encrypted)
   Z-Wave Debug                    RCVD requestEncryptedCmdClasses: 01 07 00 13 61 00 00 0D 87 (node ACK)
   Z-Wave Debug                    RCVD nonceFetch: node 025
   Z-Wave Debug                    SENT nonceReport: 01 11 00 13 19 0A 98 80 0F 48 F5 0D CB E8 0B C2 25 62 E4
   Z-Wave Debug                    RCVD nonceReport: 01 07 00 13 62 00 00 14 9D (node ACK)
   Z-Wave Debug                    timeout waiting for module command after sending nonce report (not critical)
   Z-Wave Debug                    timeout waiting for reply from module (non-fatal, skipping request)
   Z-Wave Debug                    SENT requestManufactureInfo: 01 09 00 13 19 02 72 04 25 63 CE
   Z-Wave Debug                    RCVD requestManufactureInfo: 01 07 00 13 63 00 01 9D 14 (node ACK)
   Z-Wave Debug                    RCVD requestManufactureInfo: 01 0E 00 04 00 19 08 72 05 00 3B 00 01 04 69 C4
   Z-Wave Debug                    . .  requestManufactureInfo: node 025, manufacturerId 003B, productId 00010469
   Z-Wave Debug                    . .  requestManufactureInfo: Schlage, Door Lock (BE369/468/469)
   Z-Wave                          Syncing - retrieved manufacture and model names: Schlage - 003B, Door Lock (BE369/468/469) - 00010469
   Z-Wave Debug                    SENT requestVersInfoGen: 01 09 00 13 19 02 86 11 25 64 28
   Z-Wave Error                    Syncing - failed
   Z-Wave Error                    Timeout waiting for "025 - Keypad Door Lock". Module might be asleep, or is unreachable.
   Z-Wave Debug                    RCVD requestVersInfoGen: 01 07 00 13 64 00 06 10 99 (node ACK)
   Z-Wave Debug                    . .  requestVersInfoGen: requeuing 4 unsolicited packets
   Z-Wave Debug                    RCVD requestManufactureInfo: 01 0E 00 04 00 19 08 72 05 00 3B 00 01 04 69 C4
   Z-Wave Debug                    . .  requestManufactureInfo: node 025, manufacturerId 003B, productId 00010469
   Z-Wave Debug                    RCVD requestManufactureInfo: 01 0E 00 04 10 19 08 72 05 00 3B 00 01 04 69 D4
   Z-Wave Debug                    . .  requestManufactureInfo: node 025, manufacturerId 003B, productId 00010469
   Z-Wave Debug                    RCVD requestManufactureInfo: 01 0E 00 04 10 19 08 72 05 00 3B 00 01 04 69 D4
   Z-Wave Debug                    . .  requestManufactureInfo: node 025, manufacturerId 003B, productId 00010469
   Z-Wave Debug                    RCVD requestManufactureInfo: 01 0E 00 04 10 19 08 72 05 00 3B 00 01 04 69 D4
   Z-Wave Debug                    . .  requestManufactureInfo: node 025, manufacturerId 003B, productId 00010469


I then on a whim moved the repeater into the attic because it seems that just maybe it would have less interference (hard to say obviously with RF), but this was the log when I tried to sync there. More or less same deal, just slightly different.

Code: Select all

May 9, 2023 at 8:12:37 PM
   Z-Wave Debug                    intiatingSyncUI (timeout in 1500 seconds)
   Z-Wave                          Syncing - started for "025 - Keypad Door Lock"
   Z-Wave Debug                    SENT getNodeNeighbors: 01 06 00 80 19 01 01 60
   Z-Wave Debug                    RCVD getNodeNeighbors: 01 20 01 80 00 80 03 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 DD (no inbound callback)
   Z-Wave Debug                    . .  getNodeNeighbors: nodeId 025, neighbors: 16, 17, 18
   Z-Wave                          Syncing - retrieved module neighbors list: 16, 17, 18
   Z-Wave                          Syncing - assigning return route to "025 - Keypad Door Lock"
   Z-Wave Debug                    SENT assignReturnRoute: 01 05 00 46 19 01 A4
   Z-Wave Debug                    RCVD assignReturnRoute: 01 04 01 46 01 BD (no inbound callback)
   Z-Wave Debug                    RCVD assignReturnRoute: 01 05 00 46 01 00 BD
   Z-Wave Debug                    . .  assignReturnRoute: node 025, success 1
   Z-Wave                          Syncing - assigned return route
   Z-Wave Debug                    SENT requestNodeInfo: 01 06 00 60 19 24 77 D3
   Z-Wave Debug                    RCVD nodeInfoFrame: 01 10 00 49 84 19 0A 04 40 03 5E 98 9F 55 6C 8A 22 BE
   Z-Wave Debug                    . .  nodeInfoFrame: node 025, combined class list: 20v1 62v1 63v1 72v1 86v1 98v1 5Ev1 9Fv1 55v1 6Cv1 8Av1 22v1
   Z-Wave Debug                    SENT nonceRequest: 01 09 00 13 19 02 98 40 25 78 7B
   Z-Wave Debug                    RCVD nonceRequest: 01 07 00 13 78 00 00 09 9A (node ACK)
   Z-Wave Debug                    RCVD nonceReport: node 025, nonce 65 CA 62 22 E5 45 CD 6D
   Z-Wave Debug                    SENT requestEncryptedCmdClasses: 98 02 (encrypted)
   Z-Wave Debug                    RCVD requestEncryptedCmdClasses: 01 07 00 13 79 00 00 09 9B (node ACK)
   Z-Wave Debug                    RCVD nonceFetch: node 025
   Z-Wave Debug                    SENT nonceReport: 01 11 00 13 19 0A 98 80 C7 E6 47 30 A7 F6 B8 DF 25 7A C9
   Z-Wave Debug                    RCVD nonceReport: 01 07 00 13 7A 00 00 0F 9E (node ACK)
   Z-Wave Debug                    RCVD encryptedPacket: 00 98 03 00 5D 85 70 80 62 71 63 4E 8A 6C 72 86 7A 22 59 5A 73 87 (decrypted)
   Z-Wave Debug                    RCVD requestEncryptedCmdClasses: 01 1B 00 04 00 19 15 98 03 00 5D 85 70 80 62 71 63 4E 8A 6C 72 86 7A 22 59 5A 73 87 FF
   Z-Wave Debug                    RCVD requestEncryptedCmdClasses: node 025, classes 5D 85 70 80 62 71 63 4E 8A 6C 72 86 7A 22 59 5A 73 87
   Z-Wave Debug                    SENT nonceRequest: 01 09 00 13 19 02 98 40 25 7B 78
   Z-Wave Debug                    RCVD nonceRequest: 01 07 00 13 7B 00 00 0E 9E (node ACK)
   Z-Wave Debug                    RCVD nonceReport: node 025, nonce 1F 04 E6 E8 01 13 8D 79
   Z-Wave Debug                    SENT requestManufactureInfo: 72 04 (encrypted)
   Z-Wave Debug                    RCVD requestManufactureInfo: 01 07 00 13 7C 00 00 09 9E (node ACK)
   Z-Wave Debug                    RCVD nonceFetch: node 025
   Z-Wave Debug                    SENT nonceReport: 01 11 00 13 19 0A 98 80 C7 E6 47 30 A7 F6 B8 DF 25 7D CE
   Z-Wave Debug                    RCVD nonceReport: 01 07 00 13 7D 00 00 0F 99 (node ACK)
   Z-Wave Debug                    RCVD encryptedPacket: 00 72 05 00 3B 00 01 04 69 (decrypted)
   Z-Wave Debug                    RCVD requestManufactureInfo: 01 0E 00 04 00 19 08 72 05 00 3B 00 01 04 69 FF
   Z-Wave Debug                    . .  requestManufactureInfo: node 025, manufacturerId 003B, productId 00010469
   Z-Wave Debug                    . .  requestManufactureInfo: Schlage, Door Lock (BE369/468/469)
   Z-Wave                          Syncing - retrieved manufacture and model names: Schlage - 003B, Door Lock (BE369/468/469) - 00010469
   Z-Wave Debug                    SENT nonceRequest: 01 09 00 13 19 02 98 40 25 7E 7D
   Z-Wave Debug                    RCVD nonceRequest: 01 07 00 13 7E 00 02 5F C8 (node ACK)
   Z-Wave Debug                    . .  nonceRequest: requeuing 2 unsolicited packets
   Z-Wave Debug                    RCVD nonceReport: node 025, nonce 9F 30 27 DC 27 D6 23 BE (saved for next send)
   Z-Wave Debug                    RCVD nonceReport: node 025, nonce 9F 30 27 DC 27 D6 23 BE (saved for next send)
   Z-Wave Debug                    SENT requestVersInfoGen: 86 11 (encrypted)
   Z-Wave Debug                    RCVD requestVersInfoGen: 01 07 00 13 7F 00 00 74 E0 (node ACK)
   Z-Wave Debug                    RCVD nonceFetch: node 025
   Z-Wave Debug                    SENT nonceReport: 01 11 00 13 19 0A 98 80 33 DC 31 FF 54 F8 3D 10 25 80 F3
   Z-Wave Debug                    RCVD nonceReport: 01 07 00 13 80 00 01 4F 25 (node ACK)
   Z-Wave Debug                    timeout waiting for reply from module (retrying)
   Z-Wave Error                    Syncing - failed
   Z-Wave Error                    Timeout waiting for "025 - Keypad Door Lock". Module might be asleep, or is unreachable.
   Z-Wave Debug                    timeout waiting for module command after sending nonce report (not critical)
   Z-Wave Debug                    SENT nonceRequest: 01 09 00 13 19 02 98 40 25 81 82
   Z-Wave Debug                    RCVD nonceRequest: 01 07 00 13 81 00 00 05 6F (node ACK)
   Z-Wave Debug                    RCVD nonceReport: node 025, nonce A4 4D F1 47 BE E6 30 87
   Z-Wave Debug                    SENT requestVersInfoGen: 86 11 (encrypted)
   Z-Wave Debug                    RCVD requestVersInfoGen: 01 07 00 13 82 00 00 06 6F (node ACK)
   Z-Wave Debug                    RCVD nonceFetch: node 025
   Z-Wave Debug                    SENT nonceReport: 01 11 00 13 19 0A 98 80 77 39 4F 54 8A A8 67 79 25 83 39
   Z-Wave Debug                    terminatingSyncUI
   Z-Wave Debug                    RCVD nonceReport: 01 07 00 13 83 00 04 20 4C (node ACK)
   Z-Wave Debug                    . .  nonceReport: requeuing 2 unsolicited packets
   Z-Wave Debug                    timeout waiting for module command after sending nonce report (not critical)


Still considering getting a 2nd repeater, but given that the two devices behind the lock are fine, seems unlikely to fix it. Any thoughts? suggestions? much appreciated!

Thanks

[matt (support)]

Definitely looks like there is some network issues going on here. Unfortunately, I don't know if it is a range, interference, congestion or other problem (marginal module not routing commands well).

It might be a pain, but I'd suggest removing the lock and trying the re-sync with it right next to the Mac to see if you can get it to complete, oor move the Mac with its Z-Wave controller to be next to the lock. It is possible that once the sync is complete it will work okay back at its original location.

Note I believe the inclusion with encryption worked correctly, otherwise the sync would be failing earlier in the process. That is, I wouldn't bother trying to exclude and re-include the module as it looks like that process must have completed successfully already.

I was afraid you'd say that. Is it silly of me to think that a 2nd repeater might magically fix this? Have you (or anyone) heard of a 2nd repeater fixing an issue like this where inclusion worked but sync failed? I only ask out of desperation as moving the lock is last resort for me.

Thanks

[matt (support)]

It might help, but I'm not sure. You might also want to temporarily remove some of your repeaters, as it is possible one of them is marginal or not relaying commands correctly. Basically, shake the box of marbles enough and it might be able to sync. Relocating the lock is probably the most likely change to get it to work though.