Can't create new device for Schlage Sense

Posted on
Sun Aug 23, 2020 2:27 pm
mattyf offline
Posts: 58
Joined: Apr 15, 2013

Can't create new device for Schlage Sense

The lock was working with Indigo for a while, but stopped responding. I couldn't unenroll it either, so I did a factory reset.

I can enroll the lock in the Zwave network using Indigo fine, but when I try to sync it (after creating a new device using encryption), I get

Z-Wave Syncing - started for "009 - Keypad Door Lock"
Z-Wave Syncing - retrieved module neighbors list: - none -
Z-Wave Syncing - assigning return route to "009 - Keypad Door Lock"
Z-Wave Error Syncing - failed to assign return route
Z-Wave Error Syncing - failed
Z-Wave Error No response from "009 - Keypad Door Lock". Module might be asleep, or is unreachable.

The Schlage Manual doesn't have anything helpful about how to wake it up. I tried starting the sync the pressing the schlage buttons, but got the same error.

Thanks in advance!

Posted on
Mon Aug 24, 2020 1:31 pm
jay (support) offline
Site Admin
User avatar
Posts: 18224
Joined: Mar 19, 2008
Location: Austin, Texas

Re: Can't create new device for Schlage Sense

Are you sure that you included it from within Indigo with encryption? You can't include using the Z-Stick button and it must be included with encryption.

Jay (Indigo Support)
Twitter | Facebook | LinkedIn

Posted on
Tue Aug 25, 2020 11:39 pm
mattyf offline
Posts: 58
Joined: Apr 15, 2013

Re: Can't create new device for Schlage Sense

Yes, encryption was on, and I did it from within indigo. I've never used the button on the Zstick to include anything, I don't believe....

Posted on
Wed Aug 26, 2020 9:19 am
jay (support) offline
Site Admin
User avatar
Posts: 18224
Joined: Mar 19, 2008
Location: Austin, Texas

Re: Can't create new device for Schlage Sense

Exclude it, enable debug logging in the Z-Wave config dialog, then do the inclusion again. Copy/paste the entire session from the event log into a reply.

It could also be a range issue - the include process is less intensive than the process needed to add it to Indigo so if it's in a marginal location that may be the issue. Make sure that if it's some distance from your Z-Stick that you have another device in between that can route for you.

Jay (Indigo Support)
Twitter | Facebook | LinkedIn

Posted on
Wed Aug 26, 2020 12:58 pm
mattyf offline
Posts: 58
Joined: Apr 15, 2013

Re: Can't create new device for Schlage Sense

Here you go. I tried it twice, same result.

The lock is about 5 feet away from the ZWave stick. There is one single wall between them. When the lock was originally working, I never had any communication issues with it, for what that's worth.

Thanks!


Code: Select all
   Z-Wave                          started controller exclusion mode

Aug 26, 2020 at 11:50:56 AM
   Z-Wave                          controller excluded module: 009 - Keypad Door Lock
   Z-Wave                          stopped controller exclusion mode

Aug 26, 2020 at 11:51:55 AM
   Z-Wave Debug                    stopping node healing thread
   Z-Wave Debug                    stopping node status polling thread
   Z-Wave Debug                    stopped zwave packet parser thread
   Z-Wave                          connection reset requested
   Z-Wave Debug                    starting serial connection loop
   Z-Wave Debug                    starting zwave packet parser thread
   Z-Wave Debug                    SENT getVersion: 01 03 00 15 E9
   Z-Wave Debug                    RCVD getVersion: 01 10 01 15 5A 2D 57 61 76 65 20 33 2E 39 35 00 01 99 (no inbound callback)
   Z-Wave Debug                    . .  getVersion: Z-Wave 3.95 static controller
   Z-Wave Debug                    SENT getHomeID: 01 03 00 20 DC
   Z-Wave Debug                    RCVD getHomeID: 01 08 01 20 D0 70 DF 92 01 3A (no inbound callback)
   Z-Wave Debug                    . .  getHomeID: D070DF92, nodeID: 001
   Z-Wave Debug                    SENT getInterfaceFeatures: 01 03 00 05 F9
   Z-Wave Debug                    RCVD getInterfaceFeatures: 01 04 01 05 10 EF (no inbound callback)
   Z-Wave Debug                    . .  getInterfaceFeatures: 10
   Z-Wave Debug                    SENT getInterfaceApiCapabilities: 01 03 00 07 FB
   Z-Wave Debug                    RCVD getInterfaceApiCapabilities: 01 2B 01 07 01 00 00 86 01 01 00 5A FE 81 FF 88 4F 1F 00 00 FB 9F 7D A0 67 00 00 80 00 80 86 00 00 00 E8 73 00 00 0E 00 00 60 00 00 FA (no inbound callback)
   Z-Wave Debug                    . .  getInterfaceApiCapabilities: supportedFuncIDs: 02 03 04 05 06 07 08 09 10 11 12 13 14 15 16 17 18 1C 20 21 22 23 24 27 29 2A 2B 2C 2D 41 42 44 45 46 47 48 49 4A 4B 4C 4D 50 51 53 54 55 56 57 5E 60 61 62 63 66 67 80 90 92 93 98 B4 B6 B7 B8 B9 BA BD BE BF D2 D3 D4 EE EF
   Z-Wave Debug                    . .  getInterfaceApiCapabilities: serialApi 1.00, manufactureId 0086, productType 0101, productId 005A
   Z-Wave                          connected to Z-Stick Plus (ZW090) interface on /dev/cu.usbmodem1421 (firmware 1.00)
   Z-Wave Debug                    SENT forceSUC: 01 05 00 54 01 01 AE
   Z-Wave Debug                    RCVD forceSUC: 01 04 01 54 01 AF (no inbound callback)
   Z-Wave Debug                    SENT getInitialNodeData: 01 03 00 02 FE
   Z-Wave Debug                    RCVD getInitialNodeData: 01 25 01 02 05 08 1D 31 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 05 00 FD (no inbound callback)
   Z-Wave Debug                    . .  getInitialNodeData: is static update controller
   Z-Wave Debug                    . .  getInitialNodeData: [1, 5, 6]
   Z-Wave Debug                    SENT getNodeProtocolInfo: 01 04 00 41 01 BB
   Z-Wave Debug                    RCVD getNodeProtocolInfo: 01 09 01 41 93 16 01 02 02 01 33 (no inbound callback)
   Z-Wave Debug                    . .  getNodeProtocolInfo:       node 001, class name: Static Computer Controller
   Z-Wave Debug                    . .  getNodeProtocolInfo:            class hierarchy: Static Controller : Static Controller : Static Computer Controller (02 : 02 : 01)
   Z-Wave Debug                    . .  getNodeProtocolInfo:         base class command: 00
   Z-Wave Debug                    . .  getNodeProtocolInfo:   supported class commands: 20
   Z-Wave Debug                    . .  getNodeProtocolInfo:     encrypt class commands:
   Z-Wave Debug                    . .  getNodeProtocolInfo:                   features: beaming
   Z-Wave Debug                    SENT getNodeProtocolInfo: 01 04 00 41 05 BF
   Z-Wave Debug                    RCVD getNodeProtocolInfo: 01 09 01 41 13 96 01 01 01 01 33 (no inbound callback)
   Z-Wave Debug                    . .  getNodeProtocolInfo:       node 005, class name: Portable Remote Controller
   Z-Wave Debug                    . .  getNodeProtocolInfo:            class hierarchy: Controller : Portable Controller : Portable Remote Controller (01 : 01 : 01)
   Z-Wave Debug                    . .  getNodeProtocolInfo:         base class command: 00
   Z-Wave Debug                    . .  getNodeProtocolInfo:   supported class commands: 20
   Z-Wave Debug                    . .  getNodeProtocolInfo:     encrypt class commands:
   Z-Wave Debug                    . .  getNodeProtocolInfo:                   features: beaming
   Z-Wave Debug                    SENT getNodeProtocolInfo: 01 04 00 41 06 BC
   Z-Wave Debug                    RCVD getNodeProtocolInfo: 01 09 01 41 53 9C 01 04 07 01 7A (no inbound callback)
   Z-Wave Debug                    . .  getNodeProtocolInfo:       node 006, class name: Notification Sensor
   Z-Wave Debug                    . .  getNodeProtocolInfo:            class hierarchy: Routing Slave : Notification Sensor : Notification Sensor (04 : 07 : 01)
   Z-Wave Debug                    . .  getNodeProtocolInfo:         base class command: 00
   Z-Wave Debug                    . .  getNodeProtocolInfo:   supported class commands: 20
   Z-Wave Debug                    . .  getNodeProtocolInfo:     encrypt class commands:
   Z-Wave Debug                    . .  getNodeProtocolInfo:                   features: routing, beaming
   Z-Wave Debug                    starting node healing thread
   Z-Wave Debug                    starting node status polling thread
   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 01 01 00 00 B2
   Z-Wave Debug                    RCVD inclusionMode node found: 01 07 00 4A 01 02 00 00 B1
   Z-Wave Debug                    RCVD inclusionMode adding slave node: 01 0F 00 4A 01 03 0A 08 04 40 03 22 72 7A 98 86 C9
   Z-Wave Debug                    RCVD inclusionMode node respondCmds: 22 72 7A 98 86
   Z-Wave Debug                    RCVD inclusionMode node added: 01 07 00 4A 01 05 0A 00 BC
   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 01 06 0A 00 BF
   Z-Wave Debug                    SENT getNodeProtocolInfo: 01 04 00 41 0A B0
   Z-Wave Debug                    RCVD getNodeProtocolInfo: 01 09 01 41 53 DC 00 04 40 03 7E (no inbound callback)
   Z-Wave Debug                    . .  getNodeProtocolInfo:       node 010, 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: 010 - Keypad Door Lock
   Z-Wave                          querying module for encryption support
   Z-Wave Debug                    SENT requestSecuritySchemes: 01 0A 00 13 0A 03 98 04 00 25 49 1F
   Z-Wave Debug                    RCVD requestSecuritySchemes: 01 07 00 13 49 00 00 73 D1 (node ACK)
   Z-Wave Debug                    RCVD requestSecuritySchemes: 01 09 00 04 00 0A 03 98 05 00 66
   Z-Wave Debug                    . .  requestSecuritySchemes: node 010, schemeIndex 0
   Z-Wave                          starting encryption key exchange with module
   Z-Wave Debug                    SENT nonceRequest: 01 09 00 13 0A 02 98 40 25 4A 5A
   Z-Wave Debug                    RCVD nonceRequest: 01 07 00 13 4A 00 00 02 A3 (node ACK)
   Z-Wave Debug                    RCVD nonceReport: node 010, nonce 8F DD D3 76 90 33 C2 9C
   Z-Wave Debug                    SENT setNetworkSecurityKey: ** ** ** ** (encrypted)
   Z-Wave Debug                    RCVD setNetworkSecurityKey: 01 07 00 13 4B 00 00 03 A3 (node ACK)
   Z-Wave Debug                    RCVD nonceFetch: node 010
   Z-Wave Debug                    SENT nonceReport: 01 11 00 13 0A 0A 98 80 59 0B B7 4E 1C EE 71 C9 25 4C 6D
   Z-Wave Debug                    RCVD nonceReport: 01 07 00 13 4C 00 00 02 A5 (node ACK)
   Z-Wave Debug                    RCVD encryptedPacket: 00 98 07 (decrypted)
   Z-Wave Debug                    RCVD keyVerify: 01 08 00 04 00 0A 02 98 07 FF
   Z-Wave                          completed encryption key exchange with module
   Z-Wave                          stopped controller inclusion mode

Aug 26, 2020 at 11:52:56 AM
   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
   Z-Wave Debug                    SENT exitInclusionMode: 01 04 00 4A 05 B4
   Z-Wave Debug                    RCVD exitInclusionMode: 06 (ACK)
   Z-Wave                          stopping controller inclusion mode
   Z-Wave Debug                    RCVD inclusionMode finished: 01 07 00 4A 0A 06 0A 00 B4
   Z-Wave                          stopped controller inclusion mode
   Z-Wave Debug                    terminatingSyncUI
   Z-Wave Debug                    intiatingSyncUI (timeout in 1500 seconds)
   Z-Wave                          Syncing - started for "010 - Keypad Door Lock"
   Z-Wave Debug                    SENT getNodeNeighbors: 01 06 00 80 0A 01 01 73
   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 (no inbound callback)
   Z-Wave Debug                    . .  getNodeNeighbors: nodeId 010, neighbors: - none -
   Z-Wave                          Syncing - retrieved module neighbors list: - none -
   Z-Wave                          Syncing - assigning return route to "010 - Keypad Door Lock"
   Z-Wave Debug                    SENT assignReturnRoute: 01 05 00 46 0A 01 B7
   Z-Wave Debug                    RCVD assignReturnRoute: 01 04 01 46 01 BD (no inbound callback)
   Z-Wave Debug                    RCVD assignReturnRoute: 01 05 00 46 01 01 BC
   Z-Wave Debug                    . .  assignReturnRoute: node 010, success 0
   Z-Wave Error                    Syncing - failed to assign return route
   Z-Wave Debug                    SENT requestNodeInfo: 01 06 00 60 0A 24 4D FA
   Z-Wave Debug                    RCVD requestNodeInfo: 01 06 00 49 81 00 00 31
   Z-Wave Debug                    RCVD requestNodeInfo: failed (module asleep or doesn't support command)
   Z-Wave Error                    Syncing - failed
   Z-Wave Error                    No response from "010 - Keypad Door Lock". Module might be asleep, or is unreachable.
   Z-Wave Debug                    terminatingSyncUI

Aug 26, 2020 at 11:54:00 AM
   Z-Wave Debug                    SENT enterExclusionMode: 01 04 00 4B 81 31
   Z-Wave Debug                    RCVD enterExclusionMode: 06 (ACK)
   Z-Wave                          started controller exclusion mode
   Z-Wave Debug                    RCVD exclusionMode ready: 01 07 00 4B 24 01 00 00 96
   Z-Wave Debug                    RCVD exclusionMode node found: 01 07 00 4B 24 02 00 00 95
   Z-Wave Debug                    RCVD exclusionMode removing slave node: 01 0F 00 4B 24 03 0A 08 04 40 03 00 00 00 00 00 D9
   Z-Wave Debug                    RCVD exclusionMode finished: 01 0F 00 4B 24 06 0A 08 04 40 03 00 00 00 00 00 DC
   Z-Wave Debug                    . .  exclusionMode node removed: 010
   Z-Wave                          controller excluded module: 010 - Keypad Door Lock
   Z-Wave Debug                    SENT exitExclusionMode: 01 04 00 4B 05 B5
   Z-Wave Debug                    RCVD exitExclusionMode: 06 (ACK)
   Z-Wave                          stopped controller exclusion mode

Aug 26, 2020 at 11:54:33 AM
   MyQ Debug                       deviceDeleted: new device
   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 24 01 00 00 97

Aug 26, 2020 at 11:55:06 AM
   Z-Wave Debug                    RCVD inclusionMode node found: 01 07 00 4A 24 02 00 00 94
   Z-Wave Debug                    RCVD inclusionMode adding slave node: 01 0F 00 4A 24 03 0B 08 04 40 03 22 72 7A 98 86 ED
   Z-Wave Debug                    RCVD inclusionMode node respondCmds: 22 72 7A 98 86
   Z-Wave Debug                    RCVD inclusionMode node added: 01 07 00 4A 24 05 0B 00 98
   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 24 06 0B 00 9B
   Z-Wave Debug                    SENT getNodeProtocolInfo: 01 04 00 41 0B B1
   Z-Wave Debug                    RCVD getNodeProtocolInfo: 01 09 01 41 53 DC 00 04 40 03 7E (no inbound callback)
   Z-Wave Debug                    . .  getNodeProtocolInfo:       node 011, 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: 011 - Keypad Door Lock
   Z-Wave                          querying module for encryption support
   Z-Wave Debug                    SENT requestSecuritySchemes: 01 0A 00 13 0B 03 98 04 00 25 4E 19
   Z-Wave Debug                    RCVD requestSecuritySchemes: 01 07 00 13 4E 00 00 73 D6 (node ACK)
   Z-Wave Debug                    RCVD requestSecuritySchemes: 01 09 00 04 00 0B 03 98 05 00 67
   Z-Wave Debug                    . .  requestSecuritySchemes: node 011, schemeIndex 0
   Z-Wave                          starting encryption key exchange with module
   Z-Wave Debug                    SENT nonceRequest: 01 09 00 13 0B 02 98 40 25 4F 5E
   Z-Wave Debug                    RCVD nonceRequest: 01 07 00 13 4F 00 00 03 A7 (node ACK)
   Z-Wave Debug                    RCVD nonceReport: node 011, nonce 84 6A 90 2B AF 7B 36 95
   Z-Wave Debug                    SENT setNetworkSecurityKey: ** ** ** ** (encrypted)
   Z-Wave Debug                    RCVD setNetworkSecurityKey: 01 07 00 13 50 00 00 03 B8 (node ACK)
   Z-Wave Debug                    RCVD nonceFetch: node 011
   Z-Wave Debug                    SENT nonceReport: 01 11 00 13 0B 0A 98 80 FE 0D 55 31 1F 2A B8 E5 25 51 6F
   Z-Wave Debug                    RCVD nonceReport: 01 07 00 13 51 00 00 03 B9 (node ACK)
   Z-Wave Debug                    RCVD encryptedPacket: 00 98 07 (decrypted)
   Z-Wave Debug                    RCVD keyVerify: 01 08 00 04 00 0B 02 98 07 FF
   Z-Wave                          completed encryption key exchange with module
   Z-Wave                          stopped controller inclusion mode
   Z-Wave                          Syncing - started for "011 - Keypad Door Lock"
   Z-Wave Debug                    SENT getNodeNeighbors: 01 06 00 80 0B 01 01 72
   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 (no inbound callback)
   Z-Wave Debug                    . .  getNodeNeighbors: nodeId 011, neighbors: - none -
   Z-Wave                          Syncing - retrieved module neighbors list: - none -
   Z-Wave                          Syncing - assigning return route to "011 - Keypad Door Lock"
   Z-Wave Debug                    SENT assignReturnRoute: 01 05 00 46 0B 01 B6
   Z-Wave Debug                    RCVD assignReturnRoute: 01 04 01 46 01 BD (no inbound callback)
   Z-Wave Debug                    RCVD assignReturnRoute: 01 05 00 46 01 01 BC
   Z-Wave Debug                    . .  assignReturnRoute: node 011, success 0
   Z-Wave Error                    Syncing - failed to assign return route
   Z-Wave Debug                    SENT requestNodeInfo: 01 06 00 60 0B 24 52 E4
   Z-Wave Debug                    RCVD requestNodeInfo: 01 06 00 49 81 00 00 31
   Z-Wave Debug                    RCVD requestNodeInfo: failed (module asleep or doesn't support command)
   Z-Wave Error                    Syncing - failed
   Z-Wave Error                    No response from "011 - Keypad Door Lock". Module might be asleep, or is unreachable.
   Z-Wave Debug                    terminatingSyncUI

Posted on
Wed Aug 26, 2020 8:31 pm
matt (support) offline
Site Admin
User avatar
Posts: 21417
Joined: Jan 27, 2003
Location: Texas

Re: Can't create new device for Schlage Sense

Although it appears to be communicating fine with Indigo during the inclusion process, including setting and verifying the security key, the message to create a return route is failing. I notice the lock isn't reporting any neighboring nodes. That is odd, so I'm not sure exactly what is going wrong. You might try re-syncing any modules that are near the lock. You might try repositioning your Z-Stick's antenna by plugging it into different USB ports. Since the lock is already so close to the Z-Stich you could also try doing resyncing it with the door wide open so that it is slightly moved/repositioned to see if that makes a difference.

Image

Posted on
Wed Aug 26, 2020 10:56 pm
mattyf offline
Posts: 58
Joined: Apr 15, 2013

Re: Can't create new device for Schlage Sense

The stick actually only works in one of the 4 USB ports on the Mac Mini. I don't know why.

I had already tried opening the door to a different position. Same result. I also tried moving the Mac Mini closer to the wall and changing its orientation. Again, no luck.

I did try shutting down the mac mini and restarting. No help there either.

I believe there is only one other zwave device enrolled... it was a multisensor that didn't really do what I wanted, so I played with it then forgot about it. I'm not even sure where it is now. Could that be causing the issue?

Posted on
Tue Sep 01, 2020 1:26 pm
matt (support) offline
Site Admin
User avatar
Posts: 21417
Joined: Jan 27, 2003
Location: Texas

Re: Can't create new device for Schlage Sense

I don't believe the multisensor should matter. Since you have just a few Z-Wave devices at this point I'd suggest you reset both the Schlage again AND the Z-Stick. Perhaps the latter is in a bad state and causing the problem. You can reset it via the Interfaces->Z-Wave->Reset Z-Wave Interface... menu item.

Image

Posted on
Sat Sep 12, 2020 2:46 pm
mattyf offline
Posts: 58
Joined: Apr 15, 2013

Re: Can't create new device for Schlage Sense

Resetting the Z-Wave network didn't work, so I called Schlage, and for anyone else who experiences this, here's what fixed it for me:

1) Unenroll the lock.
2) Made a new device with encryption. Once in inclusion mode went to the lock and entered the programming code.
3) WAIT until the orange light on the lock blinks at least 5 times. The rep told me that there is a known issue where including the lock too quickly after entering programming mode can cause issues.
4) Once the orange light had blinked 5 times, I pressed 0 to include the lock.

From there, everything worked as expected.

I hope this helps someone else!

Posted on
Sat Sep 12, 2020 3:15 pm
matt (support) offline
Site Admin
User avatar
Posts: 21417
Joined: Jan 27, 2003
Location: Texas

Re: Can't create new device for Schlage Sense

Great info – thanks for sharing. I definitely would have never thought to try that. :?

Image

Posted on
Sat Sep 12, 2020 3:33 pm
mattyf offline
Posts: 58
Joined: Apr 15, 2013

Re: Can't create new device for Schlage Sense

One could argue that you should never have HAD to think to try that in the first place.

:? :? :?

Posted on
Tue Sep 26, 2023 4:22 pm
wideglidejrp offline
User avatar
Posts: 555
Joined: Jan 15, 2012
Location: Danbury, CT

Re: Can't create new device for Schlage Door Sensor

Just got Schlage Door/Window Sensor Model: DWZWAVE1. Cannot figure out how to include it. There are no buttons to push. If I just open and close sensor with magnet, the light blinks 4 times but does not get included. Anybody have luck with this?

John R Patrick
Author of
Home Attitude

Posted on
Wed Sep 27, 2023 7:38 am
matt (support) offline
Site Admin
User avatar
Posts: 21417
Joined: Jan 27, 2003
Location: Texas

Re: Can't create new device for Schlage Sense

Did it come with any type of manual? If not, have you searched to see if you can find one online? The manuals typically include the inclusion (and exclusion) steps.

Image

Posted on
Wed Sep 27, 2023 8:39 am
wideglidejrp offline
User avatar
Posts: 555
Joined: Jan 15, 2012
Location: Danbury, CT

Re: Can't create new device for Schlage Sense

The instructions with it show it how to connect to a Nexia hub. Have searched online and found nothing else. I checked the Indigo compatibility list before buying and saw it there. Anybody have any luck connecting this to Indigo?

John R Patrick
Author of
Home Attitude

Posted on
Wed Sep 27, 2023 9:01 am
wideglidejrp offline
User avatar
Posts: 555
Joined: Jan 15, 2012
Location: Danbury, CT

Re: Can't create new device for Schlage Sense

I spoke to Schlage. They never heard of the product. They said Nexia no longer exists. Anybody know of a reliable z-wave door sensor which works with Indigo. I have been using Aeotec sensor 7 pro zwa012 but they have not been reliable and some have crapped out. Curious why Schlage is listed in the compatibility list.

John R Patrick
Author of
Home Attitude

Who is online

Users browsing this forum: No registered users and 11 guests