Adding Z-Wave stick to Control Schlage Smart Lock

Hi All,

I have a few questions about choosing smart locks to add to my system. I'm running Indigo 7 on a Mac Mini with an Insteon 2413U interface. I want to add two Schlage keypad door locks to the system.

Requirements include:
- Ability to lock, unlock and request status (locked or unlocked) via Alexa devices with my voice. (Comfortable with that now that unlocking via voice now requires a PIN)
- Ability to lock, unlock and request status (locked or unlocked) via iOS app.
- Ability to integrate lock into groups and triggers in Indigo. For example: saying "Alexa, turn on the sleep" dims a bunch of lights and locks the locks.

Desired:
- Ability to lock and unlock via Siri voice commands.

I am familiar with and currently use the Alexa Philips Hue and HomeKit Bridge plugins.
So....

Q. If I buy a Schlage Connect Z-Wave lock and an Aeotec Z-Stick Gen5, will that allow a communication path for the lock to be controlled via both Indigo and Alexa (via the plugin)? Or will I also need to buy a smart things interface to achieve what I want?

Personally I prefer the Schlage Encode lock since it's natively WiFi and has a smaller hardware physical footprint on the inside of the door. But I can't think of way to get it to talk to Indigo since it has no protocol other than WiFi. If anyone knows a trick though let me know!

I'm open to any feedback on which lock to get and what pitfalls to avoid.

Thank you!

- Keith

I can’t comment on the Alexa/Siri bits, but Indigo itself will certainly provide the integration.

Re the WiFi Encode, being WiFi isn’t a reason for Indigo not to control it; you’d just need the API to be released or hacked then a plugin could easily be written for it.


Sent from my iPhone using Tapatalk Pro

Update - I ended up getting the Schlage Connect Z-Wave version since the likelihood of Schlage providing their API for their WiFi Sense lock seems rather slim.

To my delight, using the awesome Z-Wave Lock Manager plugin I can now lock/unlock using Indigo, and Alexa as well with a command like "Turn ON the Back Door Lock".

The status of the lock is reported reliably (so far) in Inidgo, but here's what I'm wondering:
For Alexa UNLOCKING only, can I add a requirement for a PIN before Alexa will unlock? (ie: Me: "Alexa, turn the back door lock OFF" Alexa: "I'll need a code for that" Me: "9999" (or whatever I set). I believe the Schlage app interface with Alexa requires something like that for security reasons.

Lastly, how can I ask Alexa to report the status of a lock? She currently says something to the effect of "That feature is not supported".

Any and all help appreciated.

Cheers,

- Keith

Hi,
I've had the Schlage z wave lock working fine for about a year. But after a 7.4 clean install most Indigo features and plugins seem to be working well again. However, Indigo can no longer control the lock. The log shows that the commands are send to the lock and ack's are received; but the lock doesn't move. I have excluded the lock for the z wave network and included it again several times getting a new device number and creating a new device in Indigo.
Still no luck in making the lock physically respond. The Z wave stick in in the same location and distance from the lock that it always was.

Any insights?

Thanks,

Mike

[matt (support)]

Hi Mike,

Try excluding it, then re-including it with encryption again, then re-sync. Copy/paste the Event Log results showing all 3 steps into a reply so we can see what is occurring.

Dumb question, but I cant seem to make a query to answer it, does the Aotec Series 2 Z-Stick do encryption? Or would I need a Series 5?

Zstick 2 does encryption.


Sent from my iPhone using Tapatalk Pro

I just installed a Schlage FE599 lever lock. I was able to pair it, but I am not able to sync it. It times out with no ack. Normally I would push a button on a z-wave if it needs awakened. With this lock the procedure for pairing is push Schlage button, enter programming code, push Schlage button again, press 0. That sequence does not wake the lock. Any suggestions?

Jul 4, 2020 at 2:39:11 PM
Z-Wave Syncing - started for "045 - Keypad Door Lock"
Z-Wave Syncing - retrieved module neighbors list: 18, 23, 24, 25, 29, 44
Z-Wave Syncing - assigning return route to "045 - Keypad Door Lock"
Z-Wave Syncing - assigned return route
Z-Wave Syncing - retrieved manufacture and model names: Schlage - 003B, Door Lock (FE599) - 634B504C

Jul 4, 2020 at 2:39:35 PM
Z-Wave Error Syncing - failed
Z-Wave Error Timeout waiting for "045 - Keypad Door Lock". Module might be asleep, or is unreachable.

[matt (support)]

Locks are always awake. How specifically did you include it in Indigo? And did you move it after including it?

I included it by.....

Removed z-stick from Mac and put it in inclusion mode
Took it do the door. About 20 feet away.
Pressed Schlage button, entered program code, pressed Schlage button, pressed 0.
Z-stick indicated an inclusion
Put z-stick back in Mac

I included it by.....

Removed z-stick from Mac and put it in inclusion mode
Took it do the door. About 20 feet away.
Pressed Schlage button, entered program code, pressed Schlage button, pressed 0.
Z-stick indicated an inclusion
Put z-stick back in Mac

That won't work. Locks need to be included with encryption, and you can only do that when the Z-stick is in the Mac.

I usually include the lock at the Mac before I install it in the door.

[matt (support)]

Joe is correct – you have to use Indigo to include the module with encryption (with the Z-Stick plugged into the Mac). Indigo has to manage the encryption key setup/exchange manually, unfortunately.

Note also you'll need to exclude it (either manually with the Z-Stick or using Indigo) before you try including it with encryption from Indigo. That is, you have to reset it back to default/factory first.

My Z-stick (black) does not want to go into encrpted mode:
Z-Wave started controller inclusion mode with encryption
Z-Wave Error controller failed to enter inclusion mode

Its an S2 according to its boot:
Reloading interface "Z-Wave 7.4.1"
Stopping interface "Z-Wave 7.4.1" (pid 586)
Z-Wave closed connection to Z-Stick S2
Stopped interface "Z-Wave 7.4.1"
Starting interface "Z-Wave 7.4.1" (pid 26008)
Started interface "Z-Wave 7.4.1"
Z-Wave connected to Z-Stick S2 interface on /dev/cu.SLAB_USBtoUART (firmware 3.07)

[matt (support)]

Try unplugging it from the Mac for a few seconds to see if it will then work.

If it doesn't, then enable Indigo's Z-Wave Debug Logging checkbox (via the Interfaces->Z-Wave->Configure... menu item) and try starting inclusion again (with encryption mode). Copy/paste the Event Log results of that and we'll try to see what is going wrong.

I have 6 Schlage Sense z-wave locks. I have been able to successfully Include and Sync 5 of the locks. The last one gets to the setNetworkSecurityKey process and then hangs indefinitely. I have to cancel to get out of the dialog. Log file below:


Apr 2, 2021 at 7:32:34 PM
Z-Wave Debug intiatingSyncUI (timeout in 1500 seconds)
Z-Wave Debug SENT enterInclusionMode: 01 04 00 4A C1 70
Z-Wave Debug RCVD enterInclusionMode: 06 (ACK)
Z-Wave started controller inclusion mode with encryption
Z-Wave Debug RCVD inclusionMode ready: 01 07 00 4A 0A 01 00 00 B9

Apr 2, 2021 at 7:32:54 PM
Z-Wave Debug RCVD inclusionMode node found: 01 07 00 4A 0A 02 00 00 BA
Z-Wave Debug RCVD inclusionMode adding slave node: 01 0F 00 4A 0A 03 2B 08 04 40 03 22 72 7A 98 86 E3
Z-Wave Debug RCVD inclusionMode node respondCmds: 22 72 7A 98 86
Z-Wave Debug RCVD inclusionMode node added: 01 07 00 4A 0A 05 2B 00 96
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 0A 06 2B 00 95
Z-Wave Debug SENT getNodeProtocolInfo: 01 04 00 41 2B 91
Z-Wave Debug RCVD getNodeProtocolInfo: 01 09 01 41 53 DC 00 04 40 03 7E (no inbound callback)
Z-Wave Debug . . getNodeProtocolInfo: node 043, 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: 043 - Keypad Door Lock
Z-Wave querying module for encryption support
Z-Wave Debug SENT requestSecuritySchemes: 01 0A 00 13 2B 03 98 04 00 25 A2 D5
Z-Wave Debug RCVD requestSecuritySchemes: 01 07 00 13 A2 00 00 73 3A (node ACK)
Z-Wave Debug RCVD requestSecuritySchemes: 01 09 00 04 00 2B 03 98 05 00 47
Z-Wave Debug . . requestSecuritySchemes: node 043, schemeIndex 0
Z-Wave starting encryption key exchange with module
Z-Wave Debug SENT nonceRequest: 01 09 00 13 2B 02 98 40 25 A3 92
Z-Wave Debug RCVD nonceRequest: 01 07 00 13 A3 00 00 01 49 (node ACK)
Z-Wave Debug RCVD nonceReport: node 043, nonce E0 40 92 2E 19 A1 55 B9
Z-Wave Debug SENT setNetworkSecurityKey: ** ** ** ** (encrypted)
Z-Wave Debug RCVD setNetworkSecurityKey: 01 07 00 13 A4 00 00 03 4C (node ACK)

Apr 2, 2021 at 7:33:31 PM
Z-Wave Debug SENT exitInclusionMode: 01 04 00 4A 05 B4
Z-Wave Debug RCVD exitInclusionMode: 06 (ACK)

When I was able to successfully add other locks, the logs looked like this:

Apr 2, 2021 at 7:19:53 PM
Z-Wave Debug intiatingSyncUI (timeout in 1500 seconds)
Z-Wave Debug SENT enterInclusionMode: 01 04 00 4A C1 70
Z-Wave Debug RCVD enterInclusionMode: 06 (ACK)
Z-Wave started controller inclusion mode with encryption
Z-Wave Debug RCVD inclusionMode ready: 01 07 00 4A 0A 01 00 00 B9

Apr 2, 2021 at 7:20:17 PM
Z-Wave Debug RCVD inclusionMode node found: 01 07 00 4A 0A 02 00 00 BA
Z-Wave Debug RCVD inclusionMode adding slave node: 01 0F 00 4A 0A 03 26 08 04 40 03 22 72 7A 98 86 EE
Z-Wave Debug RCVD inclusionMode node respondCmds: 22 72 7A 98 86
Z-Wave Debug RCVD inclusionMode node added: 01 07 00 4A 0A 05 26 00 9B
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 0A 06 26 00 98
Z-Wave Debug SENT getNodeProtocolInfo: 01 04 00 41 26 9C
Z-Wave Debug RCVD getNodeProtocolInfo: 01 09 01 41 53 DC 00 04 40 03 7E (no inbound callback)
Z-Wave Debug . . getNodeProtocolInfo: node 038, 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: 038 - Keypad Door Lock
Z-Wave querying module for encryption support
Z-Wave Debug SENT requestSecuritySchemes: 01 0A 00 13 26 03 98 04 00 25 73 09
Z-Wave Debug RCVD requestSecuritySchemes: 01 07 00 13 73 00 00 73 EB (node ACK)
Z-Wave Debug RCVD requestSecuritySchemes: 01 09 00 04 00 26 03 98 05 00 4A
Z-Wave Debug . . requestSecuritySchemes: node 038, schemeIndex 0
Z-Wave starting encryption key exchange with module
Z-Wave Debug SENT nonceRequest: 01 09 00 13 26 02 98 40 25 74 48
Z-Wave Debug RCVD nonceRequest: 01 07 00 13 74 00 00 02 9D (node ACK)
Z-Wave Debug RCVD nonceReport: node 038, nonce 71 13 D1 C4 04 20 FB E4
Z-Wave Debug SENT setNetworkSecurityKey: ** ** ** ** (encrypted)
Z-Wave Debug RCVD setNetworkSecurityKey: 01 07 00 13 75 00 00 03 9D (node ACK)
Z-Wave Debug RCVD nonceFetch: node 038
Z-Wave Debug SENT nonceReport: 01 11 00 13 26 0A 98 80 87 3C 61 45 F3 5A 95 E1 25 76 D8
Z-Wave Debug RCVD nonceReport: 01 07 00 13 76 00 00 02 9F (node ACK)
Z-Wave Debug RCVD encryptedPacket: 00 98 07 (decrypted)
Z-Wave Debug RCVD keyVerify: 01 08 00 04 00 26 02 98 07 FF
Z-Wave completed encryption key exchange with module
Z-Wave stopped controller inclusion mode
Z-Wave Syncing - started for "038 - Keypad Door Lock"
Z-Wave Debug SENT getNodeNeighbors: 01 06 00 80 26 01 01 5F
Z-Wave Debug RCVD getNodeNeighbors: 01 20 01 80 00 90 02 00 01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 CD (no inbound callback)
Z-Wave Debug . . getNodeNeighbors: nodeId 038, neighbors: 13, 16, 18, 33
Z-Wave Syncing - retrieved module neighbors list: 13, 16, 18, 33
Z-Wave Syncing - assigning return route to "038 - Keypad Door Lock"
Z-Wave Debug SENT assignReturnRoute: 01 05 00 46 26 01 9B
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 038, success 1
Z-Wave Syncing - assigned return route
Z-Wave Debug SENT requestNodeInfo: 01 06 00 60 26 24 77 EC
Z-Wave Debug RCVD nodeInfoFrame: 01 0E 00 49 84 26 08 04 40 03 22 72 7A 98 86 61
Z-Wave Debug . . nodeInfoFrame: node 038, combined class list: 20v1 62v1 63v1 86v1 22v1 72v1 98v1 7Av1
Z-Wave Debug SENT nonceRequest: 01 09 00 13 26 02 98 40 25 78 44
Z-Wave Debug RCVD nonceRequest: 01 07 00 13 78 00 00 02 91 (node ACK)
Z-Wave Debug RCVD nonceReport: node 038, nonce C5 AA A7 BC 97 1A 50 F3
Z-Wave Debug SENT requestEncryptedCmdClasses: 98 02 (encrypted)
Z-Wave Debug RCVD requestEncryptedCmdClasses: 01 07 00 13 79 00 00 03 91 (node ACK)
Z-Wave Debug RCVD nonceFetch: node 038
Z-Wave Debug SENT nonceReport: 01 11 00 13 26 0A 98 80 19 F5 00 BE 0F 91 9C B8 25 7A 7E
Z-Wave Debug RCVD nonceReport: 01 07 00 13 7A 00 00 02 93 (node ACK)
Z-Wave Debug RCVD encryptedPacket: 00 98 03 00 5D 85 20 80 70 62 71 63 EF (decrypted)
Z-Wave Debug RCVD requestEncryptedCmdClasses: 01 12 00 04 00 26 0C 98 03 00 5D 85 20 80 70 62 71 63 EF FF
Z-Wave Debug RCVD requestEncryptedCmdClasses: node 038, classes 5D 85 20 80 70 62 71 63 EF
Z-Wave Debug SENT requestManufactureInfo: 01 09 00 13 26 02 72 04 25 7B E9
Z-Wave Debug RCVD requestManufactureInfo: 01 07 00 13 7B 00 00 02 92 (node ACK)
Z-Wave Debug RCVD requestManufactureInfo: 01 0E 00 04 00 26 08 72 05 00 3B 63 41 50 44 A1
Z-Wave Debug . . requestManufactureInfo: node 038, 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 26 02 86 11 25 7C 0F
Z-Wave Debug RCVD requestVersInfoGen: 01 07 00 13 7C 00 00 02 95 (node ACK)
Z-Wave Debug RCVD requestVersInfoGen: 01 0D 00 04 00 26 07 86 12 06 03 2A 68 15 11
Z-Wave Debug . . requestVersInfoGen: node 038, protoVers 3.42, appVers 104.21
Z-Wave Syncing - retrieved protocol version 3.42, app version 104.21
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 80v1 62v1 63v1 85v1 86v1 22v1 70v1 71v1 72v1 98v1 7Av1 5Dv1
Z-Wave Syncing - retrieved encrypt commands: 20 80 62 63 85 70 71 5D
Z-Wave Syncing - retrieved capabilities: routing, battery, beaming, security, frequentWaking
Z-Wave Debug SENT nonceRequest: 01 09 00 13 26 02 98 40 25 7D 41
Z-Wave Debug RCVD nonceRequest: 01 07 00 13 7D 00 00 02 94 (node ACK)
Z-Wave Debug RCVD nonceReport: node 038, nonce F7 01 49 53 C4 B5 E5 C3
Z-Wave Debug SENT requestAssociationGroupCount: 85 05 (encrypted)
Z-Wave Debug RCVD requestAssociationGroupCount: 01 07 00 13 7E 00 00 02 97 (node ACK)
Z-Wave Debug RCVD nonceFetch: node 038
Z-Wave Debug SENT nonceReport: 01 11 00 13 26 0A 98 80 19 F5 00 BE 0F 91 9C B8 25 7F 7B
Z-Wave Debug RCVD nonceReport: 01 07 00 13 7F 00 00 02 96 (node ACK)
Z-Wave Debug RCVD encryptedPacket: 00 85 06 01 (decrypted)
Z-Wave Debug RCVD requestAssociationGroupCount: 01 09 00 04 00 26 03 85 06 01 FF
Z-Wave Debug . . requestAssociationGroupCount: node 038, group count: 1
Z-Wave Debug SENT nonceRequest: 01 09 00 13 26 02 98 40 25 80 BC
Z-Wave Debug RCVD nonceRequest: 01 07 00 13 80 00 00 02 69 (node ACK)
Z-Wave Debug RCVD nonceReport: node 038, nonce 08 6D 94 00 F5 FD 12 8B
Z-Wave Debug SENT requestAssociations: 85 02 01 (encrypted)
Z-Wave Debug RCVD requestAssociations: 01 07 00 13 81 00 00 03 69 (node ACK)
Z-Wave Debug RCVD nonceFetch: node 038
Z-Wave Debug SENT nonceReport: 01 11 00 13 26 0A 98 80 19 F5 00 BE 0F 91 9C B8 25 82 86
Z-Wave Debug RCVD nonceReport: 01 07 00 13 82 00 00 02 6B (node ACK)
Z-Wave Debug RCVD encryptedPacket: 00 85 03 01 02 00 (decrypted)
Z-Wave Debug RCVD requestAssociations: 01 0B 00 04 00 26 05 85 03 01 02 00 FF
Z-Wave Debug . . requestAssociations: node 038, group: 1, num associations: 0, max associations: 2, replies left: 0
Z-Wave Debug . . requestAssociations: node 038, group: 1, associations: []
Z-Wave Syncing - retrieved group 1 associations: []
Z-Wave Debug SENT nonceRequest: 01 09 00 13 26 02 98 40 25 83 BF
Z-Wave Debug RCVD nonceRequest: 01 07 00 13 83 00 00 02 6A (node ACK)
Z-Wave Debug RCVD nonceReport: node 038, nonce 78 C9 75 EA 80 73 11 1E
Z-Wave Debug SENT addInterfaceAssociation: 85 01 01 01 (encrypted)
Z-Wave Debug RCVD addInterfaceAssociation: 01 07 00 13 84 00 00 03 6C (node ACK)
Z-Wave Syncing - added group 1 association to interface
Z-Wave Debug . . addInterfaceAssociation: node 038, group: 1, associations: [1]
Z-Wave Debug SENT nonceRequest: 01 09 00 13 26 02 98 40 25 85 B9
Z-Wave Debug RCVD nonceRequest: 01 07 00 13 85 00 00 02 6C (node ACK)
Z-Wave Debug RCVD nonceReport: node 038, nonce 3A DF 5E EE 11 AB 7D DD
Z-Wave Debug SENT requestBatteryLevel2: 80 02 (encrypted)
Z-Wave Debug RCVD requestBatteryLevel2: 01 07 00 13 86 00 00 02 6F (node ACK)
Z-Wave Debug RCVD nonceFetch: node 038
Z-Wave Debug SENT nonceReport: 01 11 00 13 26 0A 98 80 19 F5 00 BE 0F 91 9C B8 25 87 83
Z-Wave Debug RCVD nonceReport: 01 07 00 13 87 00 00 02 6E (node ACK)
Z-Wave Debug RCVD encryptedPacket: 00 80 03 64 (decrypted)
Z-Wave Debug RCVD requestBatteryLevel: 01 09 00 04 00 26 03 80 03 64 FF
Z-Wave Debug . . requestBatteryLevel: node 038, level 100
Z-Wave Syncing - retrieved battery level of 100%
Z-Wave Syncing - created device "038 - Door Lock (BE369/468/469)"
SQL Logger creating table device_history_587891600 for "038 - Door Lock (BE369/468/469)"
SQL Logger adding column "batterylevel" to table device_history_587891600 ("038 - Door Lock (BE369/468/469)")
Z-Wave Syncing - complete
SQL Logger adding column "batterylevel_ui" to table device_history_587891600 ("038 - Door Lock (BE369/468/469)")
Z-Wave Debug terminatingSyncUI

I have tried at least 10 times by excluding and then including the lock. I set up a new device each time I made an attempt. I have power cycled the lock several times and replaced the batteries. I uninstalled the lock after my initial attempts and moved the lock to within 6 inches of the Aeotec Z-stick 5 that I use for my z-wave interface. The lock in question has firmware 7.1 and the other successfully added locks have a mixture of firmware 7.1 and 6.8. All of the includes and excludes were done from Indigo and not from the z-stick. I had a screenshot to include but Safari will not open a file dialog when I hit the "Choose File" button below. Any ideas?

PS: I waited up to 10 blinks of the lock LED before inclusion as suggested in another post.