Schlage 469 - Zwave Errors while Syncinc

New to Zwave, but after a bit of trial and error I think I understand what I need to do. Need some help troubleshooting.

1. Aeotec Gen 5 - Z-Stick
2. Schlage 469
3. Indigo 7.2

Here is the output of me including the lock with encryption:

Z-Wave started controller inclusion mode with encryption
Z-Wave Debug RCVD inclusionMode ready: 01 07 00 4A 02 01 00 00 B1
Z-Wave Debug RCVD inclusionMode node found: 01 07 00 4A 02 02 00 00 B2
Z-Wave Debug RCVD inclusionMode adding slave node: 01 0F 00 4A 02 03 05 08 04 40 03 22 72 7A 98 86 C5
Z-Wave Debug RCVD inclusionMode node respondCmds: 22 72 7A 98 86
Z-Wave Debug RCVD inclusionMode node added: 01 07 00 4A 02 05 05 00 B0
Z-Wave Debug SENT exitInclusionMode: 01 04 00 4A 05 B4
Z-Wave Debug RCVD exitInclusionMode: 06 (ACK)
Z-Wave Debug RCVD inclusionMode finished: 01 07 00 4A 02 06 05 00 B3
Z-Wave Debug SENT getNodeProtocolInfo: 01 04 00 41 05 BF
Z-Wave Debug RCVD getNodeProtocolInfo: 01 09 01 41 53 DC 00 04 40 03 7E
Z-Wave Debug . . getNodeProtocolInfo: node 005, class name: Keypad Door Lock
Z-Wave Debug . . getNodeProtocolInfo: class hierarchy: Routing Slave : Entry Control : Keypad Door Lock (04 : 40 : 03)
Z-Wave Debug . . getNodeProtocolInfo: base class command: 62
Z-Wave Debug . . getNodeProtocolInfo: supported class commands: 20 62 63 86 22 72 98 7A
Z-Wave Debug . . getNodeProtocolInfo: encrypt class commands:
Z-Wave Debug . . getNodeProtocolInfo: features: routing, beaming, security, frequentWaking
Z-Wave controller included module: 005 - Keypad Door Lock
Z-Wave querying module for encryption support
Z-Wave Debug SENT requestSecuritySchemes: 01 0A 00 13 05 03 98 04 00 25 16 4F
Z-Wave Debug RCVD requestSecuritySchemes: 01 09 00 04 00 05 03 98 05 00 69
Z-Wave Debug . . requestSecuritySchemes: node 005, schemeIndex 0
Z-Wave starting encryption key exchange with module
Z-Wave Debug SENT nonceRequest: 01 09 00 13 05 02 98 40 25 17 08
Z-Wave Debug RCVD nonceReport: node 005, nonce EC B8 BE 58 F3 4E A0 BF
Z-Wave Debug SENT setNetworkSecurityKey: ** ** ** ** (encrypted)
Z-Wave Debug RCVD nonceFetch: node 005
Z-Wave Debug SENT nonceReport: 01 11 00 13 05 0A 98 80 69 26 08 16 E5 90 1D 19 25 19 F6
Z-Wave Debug RCVD encryptedPacket: 00 98 07 (decrypted)
Z-Wave Debug RCVD keyVerify: 01 08 00 04 00 05 02 98 07 FF
Z-Wave completed encryption key exchange with module
Z-Wave stopped controller inclusion mode

Here is the sync of the device

Z-Wave Debug intiatingSyncUI (timeout in 1500 seconds)
Z-Wave Syncing - started for "005 - Keypad Door Lock"
Z-Wave Debug SENT getNodeNeighbors: 01 06 00 80 05 01 01 7C
Z-Wave Debug RCVD getNodeNeighbors: 01 20 01 80 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 00 00 00 5E
Z-Wave Debug . . getNodeNeighbors: nodeId 005, neighbors: - none -
Z-Wave Syncing - retrieved module neighbors list: - none -
Z-Wave Syncing - assigning return route to "005 - Keypad Door Lock"
Z-Wave Debug SENT assignReturnRoute: 01 05 00 46 05 01 B8
Z-Wave Debug RCVD assignReturnRoute: 01 04 01 46 01 BD
Z-Wave Debug RCVD assignReturnRoute: 01 05 00 46 01 00 BD
Z-Wave Debug . . assignReturnRoute: node 005, success 1
Z-Wave Syncing - assigned return route
Z-Wave Debug SENT requestNodeInfo: 01 06 00 60 05 24 1A A2
Z-Wave Debug RCVD nodeInfoFrame: 01 0E 00 49 84 05 08 04 40 03 22 72 7A 98 86 42
Z-Wave Debug . . nodeInfoFrame: node 005, combined class list: 20v1 62v1 63v1 86v1 22v1 72v1 98v1 7Av1
Z-Wave Debug SENT nonceRequest: 01 09 00 13 05 02 98 40 25 1B 04
Z-Wave Debug RCVD nonceReport: node 005, nonce C6 F1 EC 60 42 A4 12 DE
Z-Wave Debug SENT requestEncryptedCmdClasses: 98 02 (encrypted)
Z-Wave Debug RCVD nonceFetch: node 005
Z-Wave Debug SENT nonceReport: 01 11 00 13 05 0A 98 80 A3 47 10 B5 5B 7E C6 37 25 1D 47
Z-Wave Error rcvd incomplete interface packet (skipping): 01 26 00 04 00 05 20 98
Z-Wave Error rcvd unexpected bytes (sent ACK): 81 BB 00 C2 06 55 D2 FD 0A 48 30 40 00 64 3F 34 0D 7B 35 14 60 7C A3 A0 80 C0 B6 42 A5 39 2C F5 01 26 00 04 00 05 20 98
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 05 02 72 04 25 1E AF
Z-Wave Error rcvd unexpected bytes (sent ACK): 81 BB 00 C2 06 55 D2 FD 0A 48 30 40 00 64 3F 34 0D 7B 35 14 60 7C A3 A0 80 C0 B6 42 A5 39 2C F5 06 01 04 01 13 01 E8
Z-Wave Debug SENT requestManufactureInfo: 01 09 00 13 05 02 72 04 25 1E AF (re-sent because no response)
Z-Wave Debug . . requestManufactureInfo: requeuing 2 unsolicited packets
Z-Wave Debug RCVD requestManufactureInfo: 01 0E 00 04 00 05 08 72 05 00 3B 63 41 50 44 82
Z-Wave Debug . . requestManufactureInfo: node 005, manufacturerId 003B, productId 63415044
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) - 63415044
Z-Wave Debug SENT requestVersInfoGen: 01 09 00 13 05 02 86 11 25 1F 4F
Z-Wave Debug RCVD packet: 01 07 00 13 1F 00 00 68 9C (hex)
Z-Wave Debug RCVD requestVersInfoGen: 01 0E 00 04 00 05 08 86 12 06 03 2A 80 16 44 91
Z-Wave Debug . . requestVersInfoGen: node 005, protoVers 3.42, appVers 128.22
Z-Wave Syncing - retrieved protocol version 3.42, app version 128.22
Z-Wave Debug RCVD requestVersInfoGen: 01 0D 00 04 00 05 07 86 12 06 03 2A 80 16 D9
Z-Wave Syncing - retrieved class hierarchy: Routing Slave : Entry Control : Keypad Door Lock (04 : 40 : 03, base 62)
Z-Wave Syncing - retrieved command classes: 20v1 62v1 63v1 86v1 22v1 72v1 98v1 7Av1
Z-Wave Syncing - retrieved encrypt commands: - none -
Z-Wave Syncing - retrieved capabilities: routing, beaming, security, frequentWaking
Z-Wave Syncing - created device "005 - Door Lock (BE369/468/469)"
Z-Wave Syncing - complete
Z-Wave Debug SENT requestLockStatus1: 01 09 00 13 05 02 62 02 25 20 87
Z-Wave sent "005 - Door Lock (BE369/468/469)" status request
Z-Wave Debug terminatingSyncUI

Here is the debug of the device:

Indigo Z-Wave Version: 2.0.119
Node ID: 5
Model: Door Lock (BE369/468/469)
Model ID: 63415044
Manufacturer: Schlage
Manufacturer ID: 003B
Protocol Version: 3.42
Application Version: 128.22
Model Definition Version: 0
Library Type: 6
Class Name: Keypad Door Lock
Class Hierarchy: 04 : 40 : 03
Command Class Base: 62
Command Versions: 20v1 62v1 63v1 86v1 22v1 72v1 98v1 7Av1
Encryption Status: Enabled for Commands - none -
Multi-Endpoint Types: - none -
Multi-Endpoint Classes: - none -
Multi-Instance Counts: - none -
Features: routing, beaming, security, frequentWaking
Neighbors: - none -
Associations: - none -
Config Values: - none -

Attached is the status of the device. I believe looking at other threads it should look a lot different especially the encryption part

The lock doesn't not respond to anything I do in indigo. Thoughts?

Subject: Schlage 469 - Zwave Errors while Syncinc

It doesn't look like the sync was successful and it shows encryption for now commands.

How did you include the lock? Hopefully it was through Indigo with the add new Z-wave device and then you told Indigo it was with encryption.

You cannot do an include from the Z-stick to the device by pushing the button. That doesn't work for devices that require encryption like locks. if you did this method, then exclude the lock and try the former method.

Thanks for the Reply. I did the inclusion like this.

Step 1 - Include to Zwave
Indigo > Interface > Zwave > Start Inclusion Mode with Encryption (Logs above)

Step 2 - Add Indigo Device
Indigo > New Device > Zwave > Select Included Lock > Sync (2nd set of logs above)

Thanks again for the help

You can also do the same by adding a new Z-wave device and you can select with or without encryption.

The logs you provided showed errors, so the sync probably did not fully take place and that will prevent devices from working or working properly.

Sorry did not mean to send you a PM. I will respond here.

I intentionally separated the actions due to having the same issue doing it in one step. I don't get any errors when adding to zWave with encryption.

The step I get errors one is when I actually add the device and do the sync.

I figured it out. I needed it to be like 1 inch from the lock when I added it to zwave with encryption.