Schlage BE469 Status Reporting

Posted on
Fri Jan 05, 2018 1:40 pm
Shavano offline
User avatar
Posts: 25
Joined: Jul 31, 2017
Location: San Antonio, TX

Schlage BE469 Status Reporting

I have installed a Schlage BE469 on my front door and have it operating with Indigo. However, I'm unable to get triggers to fire when the lock state has changed. I'm trying to use six triggers to update a variable to show if the lock was unlocked or locked with Indigo (remotely), with the keypad (outside), or manually (turnbolt inside). The only trigger that works with the lock currently is the update battery, which is running directly from the lock. Indigo itself reports the lock status correctly, but only if changed by Indigo.

Any suggestions?

The log file shows the following:

Z-Wave Indigo Device "Front Door Lock" Z-Wave Properties:
Indigo Z-Wave Version: 2.0.111
Node ID: 8
Model: Door Lock (BE369/468/469)
Model ID: 63415044
Manufacturer: Schlage
Manufacturer ID: 003B
Protocol Version: 3.42
Application Version: 113.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 80v1 62v1 63v1 85v1 86v1 22v1 70v1 71v1 72v1 98v1 7Av1 5Dv1
Encryption Status: Enabled for Commands 20 80 62 63 85 70 71 5D
Multi-Endpoint Types: - none -
Multi-Endpoint Classes: - none -
Multi-Instance Counts: - none -
Features: routing, battery, beaming, security, frequentWaking
Neighbors: - none -
Associations: - none -
Config Values: - none -

Jan 05, 2018 at 13:00:43
Z-Wave Lock Manager Debug logging enabled
Reloading plugin "Z-Wave Lock Manager 1.0.46"
Stopping plugin "Z-Wave Lock Manager 1.0.46" (pid 363)
Z-Wave Lock Manager Debug Stop processing trigger Front Door Bolt Error
Z-Wave Lock Manager Debug Stop processing trigger Front Door Locked by Indigo
Z-Wave Lock Manager Debug Stop processing trigger Front Door Locked by Keypad
Z-Wave Lock Manager Debug Stop processing trigger Front Door Locked Manually
Z-Wave Lock Manager Debug Stop processing trigger Front Door UnLocked by Indigo
Z-Wave Lock Manager Debug Stop processing trigger Front Door UnLocked by Keypad
Z-Wave Lock Manager Debug Stop processing trigger Front Door UnLocked Manually
Z-Wave Lock Manager Debug shutdown called
Stopped plugin "Z-Wave Lock Manager 1.0.46"
Starting plugin "Z-Wave Lock Manager 1.0.46" (pid 18402)
Started plugin "Z-Wave Lock Manager 1.0.46"
Z-Wave Lock Manager Debug startup called
Z-Wave Lock Manager Debug Start processing trigger Front Door Bolt Error
Z-Wave Lock Manager Debug Start processing trigger Front Door Locked by Indigo
Z-Wave Lock Manager Debug Start processing trigger Front Door Locked by Keypad
Z-Wave Lock Manager Debug Start processing trigger Front Door Locked Manually
Z-Wave Lock Manager Debug Start processing trigger Front Door UnLocked by Indigo
Z-Wave Lock Manager Debug Start processing trigger Front Door UnLocked by Keypad
Z-Wave Lock Manager Debug Start processing trigger Front Door UnLocked Manually

Jan 05, 2018 at 13:07:57
Z-Wave sent "Front Door Lock" unlock

Jan 05, 2018 at 13:08:14
Z-Wave sent "Front Door Lock" status request
Trigger Update Front Door Lock Battery
Z-Wave Lock Manager Debug Node ID 8 (Hex 8) found in lockIDs
Z-Wave Lock Manager Debug Door: 01 0D 00 04 00 08 07 62 03 00 00 02 FE FE FF
Z-Wave Lock Manager Debug
Z-Wave Lock Manager Debug Node: 8
Z-Wave Lock Manager Debug Type: 0
Z-Wave Lock Manager Debug User: 0
Z-Wave Lock Manager Status: Door is unlocked [Node: 8]
Z-Wave Lock Manager Debug Updating state: lockState
Z-Wave Lock Manager Latch open, Bolt unlocked, Door open [Node: 8]
Z-Wave Lock Manager Debug Updating state: handleState
Z-Wave Lock Manager Debug Node ID 8 (Hex 8) found in lockIDs
Z-Wave Lock Manager Debug Node ID 8 (Hex 8) found in lockIDs
Z-Wave received "008 - Front Door Lock" status update battery level 97%
Trigger Update Front Door Lock Battery
Z-Wave Lock Manager Debug Node ID 8 (Hex 8) found in lockIDs
Z-Wave Lock Manager Debug Node ID 8 (Hex 8) found in lockIDs

Jan 05, 2018 at 13:09:19
Z-Wave sent "Front Door Lock" lock

Jan 05, 2018 at 13:09:51
Z-Wave sent "Front Door Lock" status request
Z-Wave received "Front Door Lock" status update lock state not known (presuming unlocked)
Trigger Update Front Door Lock Battery
Z-Wave Lock Manager Debug Node ID 8 (Hex 8) found in lockIDs
Z-Wave Lock Manager Debug Door: 01 0D 00 04 00 08 07 62 03 FE 00 00 FE FE FF
Z-Wave Lock Manager Debug
Z-Wave Lock Manager Debug Node: 8
Z-Wave Lock Manager Debug Type: 254
Z-Wave Lock Manager Debug User: 0
Z-Wave Lock Manager Status: Door lock state unknown [Node: 8]
Z-Wave Lock Manager Debug Updating state: lockState
Z-Wave Lock Manager Latch open, Bolt locked, Door open [Node: 8]
Z-Wave Lock Manager Debug Updating state: handleState
Z-Wave Lock Manager Debug Node ID 8 (Hex 8) found in lockIDs
Z-Wave Lock Manager Debug Node ID 8 (Hex 8) found in lockIDs
Z-Wave received "008 - Front Door Lock" status update battery level 97%
Trigger Update Front Door Lock Battery
Z-Wave Lock Manager Debug Node ID 8 (Hex 8) found in lockIDs
Z-Wave Lock Manager Debug Node ID 8 (Hex 8) found in lockIDs

Jan 05, 2018 at 13:14:10
Z-Wave sent "Front Door Lock" status request
Z-Wave received "Front Door Lock" status update is locked
Trigger Update Front Door Lock Battery
Z-Wave Lock Manager Debug Node ID 8 (Hex 8) found in lockIDs
Z-Wave Lock Manager Debug Door: 01 0D 00 04 00 08 07 62 03 FF 00 00 FE FE FF
Z-Wave Lock Manager Debug
Z-Wave Lock Manager Debug Node: 8
Z-Wave Lock Manager Debug Type: 255
Z-Wave Lock Manager Debug User: 0
Z-Wave Lock Manager Status: Door is locked [Node: 8]
Z-Wave Lock Manager Debug Updating state: lockState
Z-Wave Lock Manager Latch open, Bolt locked, Door open [Node: 8]
Z-Wave Lock Manager Debug Updating state: handleState
Z-Wave Lock Manager Debug Node ID 8 (Hex 8) found in lockIDs
Z-Wave Lock Manager Debug Node ID 8 (Hex 8) found in lockIDs
Z-Wave received "008 - Front Door Lock" status update battery level 97%
Trigger Update Front Door Lock Battery
Z-Wave Lock Manager Debug Node ID 8 (Hex 8) found in lockIDs
Z-Wave Lock Manager Debug Node ID 8 (Hex 8) found in lockIDs
Z-Wave received "Motion Sensor Entry" status update is off

Posted on
Fri Jan 05, 2018 3:01 pm
howartp offline
Posts: 3348
Joined: Jan 09, 2014
Location: West Yorkshire, UK

Re: Schlage BE469 Status Reporting

Hi Shavano.

What’s your query?

Peter


Sent from my iPhone using Tapatalk Pro

Posted on
Fri Jan 05, 2018 3:02 pm
Shavano offline
User avatar
Posts: 25
Joined: Jul 31, 2017
Location: San Antonio, TX

Re: Schlage BE469 Status Reporting

How do I get the triggers to work with this lock?

Posted on
Sat Jan 06, 2018 12:09 pm
Shavano offline
User avatar
Posts: 25
Joined: Jul 31, 2017
Location: San Antonio, TX

Re: Schlage BE469 Status Reporting

Since you don't have this lock. I tried to give you some more data to help.

I locked, unlocked, and jammed the bolt and did a status request after each. Here is the Lock Manager's response codes from the lock (I think that is what this byte string is and presumably decoding to determine the lock status).

Code: Select all
01 0D 00 04 00 08 07 62 03 00 00 02 FE FE FF Unlocked Indigo
01 0D 00 04 00 08 07 62 03 00 00 02 FE FE FF Unlocked Keypad
01 0D 00 04 00 08 07 62 03 00 00 02 FE FE FF Unlocked Manual
01 0D 00 04 00 08 07 62 03 FE 00 00 FE FE FF Locked Indigo
01 0D 00 04 00 08 07 62 03 FF 00 00 FE FE FF Locked Keypad
01 0D 00 04 00 08 07 62 03 FF 00 00 FE FE FF Locked Manual
01 0D 00 04 00 08 07 62 03 FE 00 00 FE FE FF Bolt Jammed Manual
01 0D 00 04 00 08 07 62 03 FE 00 00 FE FE FF Bolt Jammed Indigo

It appears to me that the first 8 bytes are identical (ID?), and byte 9 is the Locked (FF) and Unlocked (00) response. Byte 10 is the same in all conditions and byte 11 is the same status as byte 9 with different values: Locked (00) and Unlocked (02). The final 3 bytes are the same in all conditions.

It appears that the Schlage BE 469 response from Lock Manager doesn't report anything about how it was locked, unlocked, or if the bolt is jammed. It only seems to report if it is locked or not. I don't know if this is a limitation of the lock or Lock Manager.

Posted on
Sat Jan 06, 2018 2:00 pm
Shavano offline
User avatar
Posts: 25
Joined: Jul 31, 2017
Location: San Antonio, TX

Re: Schlage BE469 Status Reporting

There appears to be another difference that I missed in byte 9 being either FF or FE.

Posted on
Sat Jan 06, 2018 3:58 pm
howartp offline
Posts: 3348
Joined: Jan 09, 2014
Location: West Yorkshire, UK

Re: Schlage BE469 Status Reporting

Ill try have a look tomorrow.


Sent from my iPhone using Tapatalk Pro

Posted on
Sun Jan 21, 2018 5:16 pm
Shavano offline
User avatar
Posts: 25
Joined: Jul 31, 2017
Location: San Antonio, TX

Re: Schlage BE469 Status Reporting

Any update available?

Posted on
Mon Jan 22, 2018 4:07 am
howartp offline
Posts: 3348
Joined: Jan 09, 2014
Location: West Yorkshire, UK

Re: Schlage BE469 Status Reporting

Sorry, not had chance to look at it yet.

Jan/Feb is my busiest month as I’m involved in a Pantomime. Most my waking hours are at Church rehearsing or behind the scenes.


Sent from my iPhone using Tapatalk Pro

Posted on
Mon Jan 22, 2018 7:39 am
Shavano offline
User avatar
Posts: 25
Joined: Jul 31, 2017
Location: San Antonio, TX

Re: Schlage BE469 Status Reporting

Okay. Nothing super urgent on my end.

Posted on
Fri Mar 30, 2018 9:56 am
Shavano offline
User avatar
Posts: 25
Joined: Jul 31, 2017
Location: San Antonio, TX

Re: Schlage BE469 Status Reporting

Any update on when you can look at this?

I just received "Z-Wave Association and Configuration Parameters" from Schlage http://ovh.to/FzmEVu2. If Jay or Matt can host the PDF on this site that would fix the problem created by the link expiring in 30 days.

[BTW: If anyone would like to get 25 GB of free storage on hubiC https://www.hubic.com (similar to Dropbox or Box; based in France), please feel free to use my referral code (VOQZVD) and I get another 5 GB.]

Posted on
Sun Apr 08, 2018 2:36 pm
howartp offline
Posts: 3348
Joined: Jan 09, 2014
Location: West Yorkshire, UK

Re: Schlage BE469 Status Reporting

Shavano wrote:
* 62 03 00 00 02 FE FE FF Unlocked Indigo
* 62 03 00 00 02 FE FE FF Unlocked Keypad
* 62 03 00 00 02 FE FE FF Unlocked Manual
* 62 03 FE 00 00 FE FE FF Locked Indigo
* 62 03 FF 00 00 FE FE FF Locked Keypad
* 62 03 FF 00 00 FE FE FF Locked Manual
* 62 03 FE 00 00 FE FE FF Bolt Jammed Manual
* 62 03 FE 00 00 FE FE FF Bolt Jammed Indigo

Ok...

62 03 is a Door Lock status report. By the ZWave specs, the following applies.

Blue 00 is the "Door Lock Mode". 00 = "Door Unsecured". FE = "Door/Lock State Unknown as Bolt is not fully retracted or engaged. FF = Door Secured.
Green 00 is the Outdoor and Indoor Handles Mode. 00 = Both handles "cannot open the door". Other combinations exist but I won't decode them here.
Purple 02 is the "Door Condition".

00 = Latch Open, Bolt Locked, Door Open
01 = Latch Open, Bolt Locked, Door Closed
02 = Latch Open, Bolt Unlocked, Door Open
03 = Latch Open, Bolt Unlocked, Door Closed
04 = Latch Closed, Bolt Locked, Door Open
05 = Latch Closed, Bolt Locked, Door Closed
06 = Latch Closed, Bolt Unlocked, Door Open
07 = Latch Closed, Bolt Unlocked, Door Closed

Orange FE FE is the Lock Timeout in Minutes and Seconds. FE = No Timeout.

The last FF is not part of the actual command.

By the specs, 62 03 alone cannot determine how the door was locked - it is only a Door Lock report.

Most manufacturers also send a 71 05 "Alarm" status report. That includes the facility to say how a lock was locked - 71 05 ... 06 01 is "Locked Manually", .... 06 05 is "Locked by RF (aka ZWave/Indigo)", etc..

Having said all the above, I think if you've used the Status Report button in Indigo's UI, it will only have sent a 62 02 Status Request (62 02 is the request for a 62 03 report) - it won't have sent a 71 02 status request, for a 71 05 report.

Can you disable your lock triggers and status requests (if you've set any schedules/triggers), turn on Lock Manager debugging (it's already on unless you've turned it off) then run through all the operations of the lock - manually, indoor/outdoor, by Indigo, etc - and copy paste any responses.

I've a feeling Schlage don't send 71 05 reports which is why we can't determine too much about the lock mode.

Peter

Posted on
Mon Apr 09, 2018 9:11 am
Shavano offline
User avatar
Posts: 25
Joined: Jul 31, 2017
Location: San Antonio, TX

Re: Schlage BE469 Status Reporting

I tried what you suggested (RF lock, unlock; Manual unlock, lock; Physical Key unlock, lock; Keypad unlock, lock) starting from unlocked and this is what I got from the log:
Code: Select all
Apr 09, 2018 at 10:03:19
   Z-Wave Watcher Debug            Raw command sent (Node 8): 01 09 00 13 08 02 98 40 25 14 06 (True)
   Z-Wave                          sent "Front Door Lock" lock
   Z-Wave Watcher Debug            Raw command sent (Node 8): 01 1E 00 13 08 17 98 81 57 BB 26 41 71 69 DD 4D 4B 86 44 5B 35 93 9E F6 C6 DF 1A 5A 49 25 15 CB (True)

Note that I also have your Z-Wave Watcher plugin set to monitor the lock while I was doing this. Next step?

Posted on
Sun May 13, 2018 3:30 pm
Shavano offline
User avatar
Posts: 25
Joined: Jul 31, 2017
Location: San Antonio, TX

Re: Schlage BE469 Status Reporting

Any update?

Posted on
Sun May 13, 2018 9:53 pm
howartp offline
Posts: 3348
Joined: Jan 09, 2014
Location: West Yorkshire, UK

Re: Schlage BE469 Status Reporting

Shavano wrote:
I tried what you suggested (RF lock, unlock; Manual unlock, lock; Physical Key unlock, lock; Keypad unlock, lock) starting from unlocked and this is what I got from the log:
Code: Select all
Apr 09, 2018 at 10:03:19
   Z-Wave Watcher Debug            Raw command sent (Node 8): <a href="tel:01 09 00 13 08 02 98">01 09 00 13 08 02 98</a> <a href="tel:40 25 14 06">40 25 14 06</a> (True)
   Z-Wave                          sent "Front Door Lock" lock
   Z-Wave Watcher Debug            Raw command sent (Node 8): 01 1E <a href="tel:00 13 08 17 98 81 57">00 13 08 17 98 81 57</a> BB <a href="tel:26 41 71 69">26 41 71 69</a> DD 4D 4B 86 44 5B 35 93 9E F6 C6 DF 1A 5A 49 25 15 CB (True)

Note that I also have your Z-Wave Watcher plugin set to monitor the lock while I was doing this. Next step?


That’s all you’re seeing?

Posted on
Mon May 14, 2018 6:28 am
Shavano offline
User avatar
Posts: 25
Joined: Jul 31, 2017
Location: San Antonio, TX

Re: Schlage BE469 Status Reporting

Yes. Am I doing something wrong capturing the data?

Who is online

Users browsing this forum: No registered users and 1 guest