Schlage BE469 Issues

Posted on
Thu Aug 03, 2017 8:11 pm
kmarkley offline
Posts: 77
Joined: Nov 15, 2016

Re: Schlage BE469 Issues

I should add that after all the above, the Lock Manager device shows "lockState = Open"

Posted on
Sun Aug 06, 2017 8:24 am
howartp offline
Posts: 2902
Joined: Jan 09, 2014
Location: West Yorkshire, UK

Re: Schlage BE469 Issues

Ok.
kmarkley wrote:
Manual unlock and lock:
Z-Wave received "Lock-Front" status update unlocked (manually)
Z-Wave Lock Manager Debug Raw: 01 0F 00 04 00 04 09 71 05 16 01 00 FF 06 02 00 FF
Z-Wave Lock Manager Status: Door unlocked manually [Node: 4]

Z-Wave received "Lock-Front" status update locked (manually)
Z-Wave Lock Manager Debug Raw: 01 0F 00 04 00 04 09 71 05 15 01 00 FF 06 01 00 FF
Z-Wave Lock Manager Status: Door locked manually [Node: 4]

Indigo unlock and lock
Z-Wave sent "Lock-Front" unlock
Z-Wave Lock Manager Debug Door: 01 0D 00 04 00 04 07 62 03 00 00 02 FE FE FF
Z-Wave Lock Manager Status: Door is unlocked [Node: 4]
Z-Wave Lock Manager Latch open, Bolt unlocked, Door open [Node: 4]

Z-Wave sent "Lock-Front" lock
Z-Wave Lock Manager Debug Door: 01 0D 00 04 00 04 07 62 03 FF 00 00 FE FE FF
Z-Wave Lock Manager Status: Door is locked [Node: 4]
Z-Wave Lock Manager Latch open, Bolt locked, Door open [Node: 4]

So...

71 05 is an ALARM notification which is used by most locks for lock/unlock/security notifications, and your lock is using it for manual lock/unlocks which is good.
71 05 15 is "Locked manually" and 71 05 16 is "Unlocked manually".

62 03 is a DOOR STATUS notification which might be used by door sensors plus some door locks as a follow-up to an alarm notification, to indicate whether the door is open/closed and (optionally) the status of the bolt, latch and door. Your lock is sending it after the lock is changed by Indigo, but maybe other times as well - there's no guarantee that it's an Indigo command that's changing it.
62 03 00 is "Door is unlocked" and the "00" in blue is the latch/bolt/door status shown.
62 03 FF is "Door is locked" and the "02" in blue is the latch/bolt/door status shown.

kmarkley wrote:
I should add that after all the above, the Lock Manager device shows "lockState = Open"

For some reason, when your lock reports that the door has been locked (62 03 FF), it reports the lock being locked but the door being open, which is why I set the state to Open not Locked.

I'll change the code for the latch/bolt/door status so it doesn't overwrite the Locked/Unlocked state wrongly.

I'm going to look into subscribing to outgoing ZWave commands from Indigo - so when Indigo sends the lock command, I intercept it and update my state accordingly.

The "changed via unknown" is Matt/Jay's area, but they are right in setting it to unknown because they haven't received a notification from the lock explaining why it's changed.

Peter

Posted on
Sun Aug 06, 2017 8:43 am
howartp offline
Posts: 2902
Joined: Jan 09, 2014
Location: West Yorkshire, UK

Re: Schlage BE469 Issues

Can you try v1.0.44 then play with node 4.

It will debug-log ANY zwave commands received from node 4, not just ones I'm expecting - then I can see if it does send anything useful about Indigo lock/unlocks.

Peter

Posted on
Sun Aug 06, 2017 10:58 am
matt (support) offline
Site Admin
User avatar
Posts: 18063
Joined: Jan 27, 2003
Location: Texas

Re: Schlage BE469 Issues

Peter – you are a rock star for diving into deciphering all this.

Image

Posted on
Sun Aug 06, 2017 11:41 am
howartp offline
Posts: 2902
Joined: Jan 09, 2014
Location: West Yorkshire, UK

Re: Schlage BE469 Issues

Some folk think I'm "sad" but I enjoy getting my teeth into the whole Zwave api. :-)

The new plugin I'm about to publish once Jay gives me another subforum should help with debugging these issues across the whole Zwave spectrum.


Sent from my iPhone using Tapatalk Pro

Posted on
Mon Aug 07, 2017 5:18 pm
kmarkley offline
Posts: 77
Joined: Nov 15, 2016

Re: Schlage BE469 Issues

Unlock:
Code: Select all
   Z-Wave                          sent "Lock-Front" unlock
   Z-Wave Lock Manager Debug       Node ID 4 (Hex 4) found in lockIDs
   Z-Wave Lock Manager Debug       Raw command: 01 08 00 04 00 04 02 98 40 2D
   Z-Wave Lock Manager Debug       Node ID 4 (Hex 4) found in lockIDs
   Z-Wave Lock Manager Debug       Raw command: 01 0D 00 04 00 04 07 62 03 00 00 02 FE FE FF
   Z-Wave Lock Manager Debug       Door: 01 0D 00 04 00 04 07 62 03 00 00 02 FE FE FF
   Z-Wave Lock Manager Debug       
   Z-Wave Lock Manager Debug       Node:  4
   Z-Wave Lock Manager Debug       Type:  0
   Z-Wave Lock Manager Debug       User:  0
   Z-Wave Lock Manager             Status: Door is unlocked [Node: 4]
   Z-Wave Lock Manager Debug       Updating state: lockState
   Z-Wave Lock Manager             Latch open, Bolt unlocked, Door open [Node: 4]
   Z-Wave Lock Manager Debug       Updating state: doorState
   Error                           device "Lock-Front-Manager" state key doorState not defined (ignoring update request)
   Z-Wave Lock Manager Debug       Node ID 4 (Hex 4) found in lockIDs
   Z-Wave Lock Manager Debug       Raw command: 01 21 00 04 00 04 1B 98 81 AC D8 ED 52 11 88 8E 98 F0 3D 88 1B 08 3C FA E4 A0 BC F9 B8 39 E3 74 8A C4 51

Lock:
Code: Select all
   Z-Wave                          sent "Lock-Front" lock
   Z-Wave Lock Manager Debug       Node ID 4 (Hex 4) found in lockIDs
   Z-Wave Lock Manager Debug       Raw command: 01 08 00 04 00 04 02 98 40 2D
   Z-Wave Lock Manager Debug       Node ID 4 (Hex 4) found in lockIDs
   Z-Wave Lock Manager Debug       Raw command: 01 0D 00 04 00 04 07 62 03 FF 00 00 FE FE FF
   Z-Wave Lock Manager Debug       Door: 01 0D 00 04 00 04 07 62 03 FF 00 00 FE FE FF
   Z-Wave Lock Manager Debug       
   Z-Wave Lock Manager Debug       Node:  4
   Z-Wave Lock Manager Debug       Type:  255
   Z-Wave Lock Manager Debug       User:  0
   Z-Wave Lock Manager             Status: Door is locked [Node: 4]
   Z-Wave Lock Manager Debug       Updating state: lockState
   Z-Wave Lock Manager             Latch open, Bolt locked, Door open [Node: 4]
   Z-Wave Lock Manager Debug       Updating state: doorState
   Error                           device "Lock-Front-Manager" state key doorState not defined (ignoring update request)
   Z-Wave Lock Manager Debug       Node ID 4 (Hex 4) found in lockIDs
   Z-Wave Lock Manager Debug       Raw command: 01 21 00 04 00 04 1B 98 81 58 5B 26 1C 7E 2A ED 0D A4 16 DB 25 6D 46 9B DB 7B 5B 1A 8B 6A B0 DC 25 D6 32

Auto-relock on:
Code: Select all
   Z-Wave Lock Manager Debug       setRelock action called
   Z-Wave Lock Manager Debug       Indigo lock selected: 1841050451
   Z-Wave Lock Manager             Enabling auto relock mode with a timeout of 30 seconds:
   Z-Wave                          sent "Lock-Front" raw command [70 04 02 01 FF]
   Z-Wave                          sent "Lock-Front" raw command [70 04 03 01 1E]

Auto-relock off:
Code: Select all
   Z-Wave Lock Manager Debug       setRelock action called
   Z-Wave Lock Manager Debug       Indigo lock selected: 1841050451
   Z-Wave Lock Manager             Enabling auto relock mode with a timeout of 30 seconds:
   Z-Wave                          sent "Lock-Front" raw command [70 04 02 01 FF]
   Z-Wave                          sent "Lock-Front" raw command [70 04 03 01 1E]


The lock manager device state is changing appropriately.

Thanks again for all your help.

Posted on
Sat Aug 12, 2017 9:52 am
kmarkley offline
Posts: 77
Joined: Nov 15, 2016

Re: Schlage BE469 Issues

Just bumping this in the hopes that the debug log I posted last week might shed some light.

Thanks.

Posted on
Sun Aug 13, 2017 12:18 pm
howartp offline
Posts: 2902
Joined: Jan 09, 2014
Location: West Yorkshire, UK

Re: Schlage BE469 Issues

Sorry, I thought from your previous post you were happy with everything now.

The log shows that your lock isn't sending anything back other than "ACK" to acknowledge the command, then the door status we know about.

Can you install my ZWave Watcher plugin and create a device for your node 4 then lock/unlock the lock from Indigo and paste the log.

I've just found the ZWave command guide for Schlage locks. It doesn't use the same parameter set as everyone else so I'll have to code in the differences. I will be able to sort Auto-Relock once I've done it.

Peter

Posted on
Sun Aug 13, 2017 8:40 pm
kmarkley offline
Posts: 77
Joined: Nov 15, 2016

Re: Schlage BE469 Issues

That sounds like triggering on locked/unlocked by Indigo is not going to be possible. Bummer.

The Lock Manager device does now correctly show locked/unlocked state, but throws an error for a missing state key (I have edited/saved the device).

Lock:
Code: Select all
   Z-Wave Watcher Debug            Raw command sent (Node 4): 01 09 00 13 04 02 98 40 25 92 8C (True)
   Z-Wave                          sent "Lock-Front" lock
   Z-Wave Watcher Debug            Raw command sent (Node 4): 01 1E 00 13 04 17 98 81 01 A4 1C 76 B3 E9 AE 49 A9 49 DA 31 63 4A D7 B0 D7 32 88 70 A5 25 93 C1 (True)
   Z-Wave Watcher Debug            Raw command sent (Node 4): 01 11 00 13 04 0A 98 80 E6 BF A3 C2 E6 91 7E DC 25 94 B7 (True)
   Z-Wave Watcher Debug            Raw command received (Node 4): 01 08 00 04 00 04 02 98 40 2D
   Z-Wave Watcher Debug            Raw command received (Node 4): 01 0D 00 04 00 04 07 62 03 FF 00 00 FE FE FF
   Z-Wave Lock Manager             Status: Door is locked [Node: 4]
   Z-Wave Watcher Debug            Raw command received (Node 4): 01 21 00 04 00 04 1B 98 81 9A 1D F7 CC AD FB 13 4B 20 D7 F5 1B BA 5D 76 DA E6 4D FD 9E 05 62 AE 50 7C 11
   Z-Wave Lock Manager             Latch open, Bolt locked, Door open [Node: 4]
   Error                           device "Lock-Front-Manager" state key doorState not defined (ignoring update request)

Unlock:
Code: Select all
   Z-Wave Watcher Debug            Raw command sent (Node 4): 01 09 00 13 04 02 98 40 25 95 8B (True)
   Z-Wave                          sent "Lock-Front" unlock
   Z-Wave Watcher Debug            Raw command sent (Node 4): 01 1E 00 13 04 17 98 81 72 7D DF 52 8F F6 C6 0D 66 A2 B9 24 7D 9E 1B 58 5F B4 FC 67 60 25 96 92 (True)
   Z-Wave Watcher Debug            Raw command sent (Node 4): 01 11 00 13 04 0A 98 80 38 E3 72 74 CE A0 31 A7 25 97 7C (True)
   Z-Wave Watcher Debug            Raw command received (Node 4): 01 08 00 04 00 04 02 98 40 2D
   Z-Wave Watcher Debug            Raw command received (Node 4): 01 0D 00 04 00 04 07 62 03 00 00 02 FE FE FF
   Z-Wave Lock Manager             Status: Door is unlocked [Node: 4]
   Z-Wave Watcher Debug            Raw command received (Node 4): 01 21 00 04 00 04 1B 98 81 9D 3F A6 90 15 2E 05 B1 C4 E6 B2 28 6B C1 AC CC 38 D2 A1 0F 9B 64 AF 0B 2E 84
   Z-Wave Lock Manager             Latch open, Bolt unlocked, Door open [Node: 4]
   Error                           device "Lock-Front-Manager" state key doorState not defined (ignoring update request)


Thanks.

Posted on
Mon Aug 14, 2017 12:10 am
howartp offline
Posts: 2902
Joined: Jan 09, 2014
Location: West Yorkshire, UK

Re: Schlage BE469 Issues

I didn't say we can't trigger on lock/unlock, we just need to decode those commands.

None of them look like the commands I imagined off the top of my head, but equally I've never looked at commands being sent so I need to research those.

Leave it with me.


Sent from my iPhone using Tapatalk Pro

Posted on
Mon Aug 14, 2017 2:44 pm
howartp offline
Posts: 2902
Joined: Jan 09, 2014
Location: West Yorkshire, UK

Re: Schlage BE469 Issues

Matt (Support).....

Can you offer insight into the commands being sent?

I'm guessing those commands are encrypted commands - I can see the 0x25 three bytes from the end, which could be the Switch_Binary on/off (lock/unlock) command, but I can't see 0x00, 0x63 or 0xFF in there?

A non-encrypted on/off command (tested on my TKB plug socket at home) is "01 0A 00 13 2C 03 25 01 FF 25 53 64" in which I can see and trap the On/Off command correctly.

Is it possible to see the non-encrypted command in the log (or with zwaveCommandSent)?

Peter

Posted on
Mon Aug 14, 2017 8:13 pm
matt (support) offline
Site Admin
User avatar
Posts: 18063
Joined: Jan 27, 2003
Location: Texas

Re: Schlage BE469 Issues

The big packet sent (3rd line in the log above) that has the 98 81 bytes is sending the encrypted date to the lock. If I remember correctly, all the bytes after that except the last couple are encrypted and Indigo doesn't broadcast out the unencrypted versions of the packet to plugins. I'll consider adding that as a feature, but I need to think through the security implications a bit. Decrypting the packet yourself would be difficult, even if you knew Indigo's security key, because of the nonces.

The next packet that has the 98 80 bytes is Indigo sending a new security nonce to the module.

The commands that actually get sent to the lock is either 0x62 0x01 0xFF (last byte 0x00 for unlock) or 0x76 0x01 0x01 (last byte 0x00 for unlock), depending on which command class the lock supports.

If Indigo broadcasted out the unencrypted packet with the encrypted packet that would help you catch that Indigo sent the command, so you could imply that Indigo is the one that did the lock/unlock? Just trying to make sure I understand what the proposal is.

Image

Posted on
Tue Aug 15, 2017 12:23 am
howartp offline
Posts: 2902
Joined: Jan 09, 2014
Location: West Yorkshire, UK

Re: Schlage BE469 Issues

matt (support) wrote:
If Indigo broadcasted out the unencrypted packet with the encrypted packet that would help you catch that Indigo sent the command, so you could imply that Indigo is the one that did the lock/unlock? Just trying to make sure I understand what the proposal is.

Correct.

I'd create a holding var $changedBy and set that to "Indigo" when you send a lock/unlock or to the relevant value when an alarm status "changed by ..." command is received. Then if a door status command arrives within x seconds I can attribute that change to the current value of $changedBy.

Something like that anyway.


Sent from my iPhone using Tapatalk Pro

Who is online

Users browsing this forum: No registered users and 2 guests