Schlage BE469 Status Reporting

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

Re: Schlage BE469 Status Reporting

I have separately been attempting to obtain the information from Schlage. However, they told me that they couldn't provide it per requirements of the Z-Wave Alliance. That sounded completely bogus to me and I therefore contacted the Z-Wave Alliance. See their reply below:

From: Rick Tinker <rick@z-wavealliance.org>
Subject: Re: Schlage Lock Status Info Forbidden by Z-Wave Alliance?
Date: May 14, 2018 at 12:57:34 CDT

Thank you for your inquiry so that we can correct this misinformation.

The Z-Wave technology is owned by Silicon Labs. Only Silicon Labs can make the determination on what is to be released to the public from the dev kit or the specifications. The second error is that the specification itself is public, and so everything that you are asking for truly is up to the manufacturer to provide. The public specification for Z-Wave can be found here: http://zwavepublic.com/specifications

The command classes that the lock uses are also available to the public from the catalog of certified products which we maintain. There have been 3 versions of the BE469 certified for the North American frequency region - click on the name for the one that matches the version that you have and you can then click on Command Classes in the detail page and you can see all of the command classes for the device: https://products.z-wavealliance.org/Sea ... Text=BE469

The command classes which can send status or information frames to an associated controller are Notification and Application Status. Additionally, depending upon how the device was set up, Door Lock, Battery, and User Code could send frames as a means of reporting status. I believe that if you look at the protocol at the public Z-Wave site provided above, you will see that most of what you want can be obtained from the Notification Command Class.

I have contacted Allegion to attempt to clarify with them the same information I am providing to you here; hopefully they will straighten out their technical support department so that they do not misinform others. If you were to ask again very specifically, I would ask them for the Notification command class types and other command class messages that are sent to associated nodes. Please be aware, however, that it is entirely up to them as to whether they want to share this information. You may instead choose to look for messages sent to the command classes I have indicated and I suspect you will get all of the information you are looking for from them.


Regards,


Rick Tinker

Rick Tinker
Director of Technology

Z-Wave Alliance
400 West Cesar Chavez
Austin, TX 78701 USA

http://www.z-wavealliance.org

Confidentiality and Privacy Notice: This message and any attachments are for the sole review and use of the intended recipient(s) and may contain proprietary, confidential, or privileged information. Any unauthorized review, use, disclosure or distribution is prohibited and may be in violation of copyright or other laws, including the Electronic Communications Privacy Act. If you are not the intended recipient or a person responsible for delivering this message to an intended recipient, please contact the sender via mail and destroy all copies of the original message immediately. Because some content may be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or may contain viruses, the Z-Wave Alliance cannot guarantee e-mail transmission to be completely secure or error-free.

Posted on
Tue May 15, 2018 8:26 pm
howartp offline
Posts: 3331
Joined: Jan 09, 2014
Location: West Yorkshire, UK

Re: Schlage BE469 Status Reporting

Good work in getting communication going - hopefully it persuades Schlage to get their act in gear.

Unfortunately the bit about command classes is nothing new to me - I know what the spec supports, and my plugin does support it - but Schlage seem not to.

I need to be at my desk to respond to you better about what you are/aren’t seeing in logs which is way less than I’m expecting.

Peter


Sent from my iPhone using Tapatalk Pro

Posted on
Tue May 15, 2018 10:45 pm
Shavano offline
User avatar
Posts: 25
Joined: Jul 31, 2017
Location: San Antonio, TX

Re: Schlage BE469 Status Reporting

Thanks for the reply. Perhaps I'm doing something wrong in obtaining the log entries? If you have any ideas, let me know what to do.

Posted on
Wed May 16, 2018 3:18 pm
howartp offline
Posts: 3331
Joined: Jan 09, 2014
Location: West Yorkshire, UK

Re: Schlage BE469 Status Reporting

Hi Shavano.

Sorry, I've just realised exactly what the root of your problem is.

Nothing to do with Schlage (yet...) though there may still be problems later.

Shavano wrote:
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 -


When you included the lock, it should have set some associations and config values.

The fact it hasn't got an association is why you're not receiving anything from the lock. If it had config values but not associations then I'd guide you to adding the association manually, but the fact you have no config values tells me the inclusion process didn't complete fully.

Could you exclude and re-include the lock, and paste the log showing the process.

You need to end up with Associations: [1]:1 or something like that.

Schlage are notorious for inclusion problems - a number of folk have removed the lock from their door and taken it to the Mac to include, then taken it back to the door. Not ideal but it certainly helps!

Peter

Posted on
Wed May 16, 2018 3:26 pm
Shavano offline
User avatar
Posts: 25
Joined: Jul 31, 2017
Location: San Antonio, TX

Re: Schlage BE469 Status Reporting

Argh! I'll try and do this tonight!

Posted on
Wed May 16, 2018 5:07 pm
Shavano offline
User avatar
Posts: 25
Joined: Jul 31, 2017
Location: San Antonio, TX

Re: Schlage BE469 Status Reporting

Well, all I had to do was resync the lock and Associations appeared. Not sure if I really need to Exclude/Include it again. The output now shows:

Code: Select all
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: 80v1 85v1 86v1 62v1 98v1 5Dv1 20v1 22v1 63v1 70v1 71v1 72v1 7Av1
Encryption Status: Enabled for Commands 80 20 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: 12, 14, 17
Associations: 1:[1]
Config Values: - none -


When I just tested the lock, it now correctly reports its status:

Code: Select all
May 16, 2018 at 17:57:30
   Z-Wave Watcher Debug            Raw command sent (Node 8): 01 11 00 13 08 0A 98 80 E1 F5 C0 83 B5 34 70 09 25 23 4E (True)
   Z-Wave Watcher Debug            Raw command received (Node 8): 01 08 00 04 00 08 02 98 40 21
   Z-Wave Lock Manager Debug       Node ID 8 (Hex 8) found in lockIDs
   Z-Wave                          received "Front Door Lock" status update unlocked (manually)
   Z-Wave Watcher Debug            Raw command received (Node 8): 01 0F 00 04 00 08 09 71 05 16 01 00 FF 06 02 00 FF
   Z-Wave Watcher Debug            Raw command received (Node 8): 01 23 00 04 00 08 1D 98 81 72 9E BA 0D 03 61 AE AF 0C 99 E2 8B 72 B6 20 37 3B B9 E1 7B AF C8 C0 EA 41 62 91 24
   Z-Wave Lock Manager Debug       Node ID 8 (Hex 8) found in lockIDs
   Z-Wave Lock Manager Debug       Raw:  01 0F 00 04 00 08 09 71 05 16 01 00 FF 06 02 00 FF
   Z-Wave Lock Manager             Status: Door unlocked manually [Node: 8]
   Z-Wave Lock Manager Debug       triggerEvent called
   Z-Wave Lock Manager Debug       ---
   Z-Wave Lock Manager Debug       dNodeID:   #8#
   Z-Wave Lock Manager Debug       eventNode: #8#
   Z-Wave Lock Manager Debug       dUserNo:   ##
   Z-Wave Lock Manager Debug       userNo:    ##
   Trigger                         Front Door UnLocked Manually
   Z-Wave Lock Manager Debug       Executing trigger
   Z-Wave Lock Manager Debug       Updating state: lockState
   Z-Wave Lock Manager Debug       -----
   Z-Wave Lock Manager Debug       Node ID 8 (Hex 8) found in lockIDs
   Z-Wave Watcher Debug            Raw command sent (Node 8): 01 11 00 13 08 0A 98 80 44 81 0E 49 F9 1A 80 7C 25 24 7B (True)
   Z-Wave Watcher Debug            Raw command received (Node 8): 01 08 00 04 00 08 02 98 40 21
   Z-Wave Lock Manager Debug       Node ID 8 (Hex 8) found in lockIDs
   Z-Wave                          received "Front Door Lock" status update locked (manually)
   Z-Wave Watcher Debug            Raw command received (Node 8): 01 0F 00 04 00 08 09 71 05 15 01 00 FF 06 01 00 FF
   Z-Wave Watcher Debug            Raw command received (Node 8): 01 23 00 04 00 08 1D 98 81 F8 EE 59 79 F8 00 5A EA F6 85 69 99 1E 42 2B 69 47 C8 44 34 54 2D D3 C7 71 29 64 99
   Z-Wave Lock Manager Debug       Node ID 8 (Hex 8) found in lockIDs
   Z-Wave Lock Manager Debug       Raw:  01 0F 00 04 00 08 09 71 05 15 01 00 FF 06 01 00 FF
   Z-Wave Lock Manager             Status: Door locked manually [Node: 8]
   Z-Wave Lock Manager Debug       triggerEvent called
   Z-Wave Lock Manager Debug       ---
   Z-Wave Lock Manager Debug       dNodeID:   #8#
   Z-Wave Lock Manager Debug       eventNode: #8#
   Z-Wave Lock Manager Debug       dUserNo:   ##
   Z-Wave Lock Manager Debug       userNo:    ##
   Trigger                         Front Door Locked Manually
   Z-Wave                          received "Front Door Lock" status update locked (manually)
   Z-Wave Lock Manager Debug       Executing trigger
   Z-Wave Lock Manager Debug       Updating state: lockState
   Z-Wave Watcher Debug            Raw command received (Node 8): 01 0F 00 04 00 08 09 71 05 15 01 00 FF 06 01 00 FF
   Z-Wave Watcher Debug            Raw command received (Node 8): 01 23 00 04 00 08 1D 98 81 F8 EE 59 79 F8 00 5A EA F6 85 69 99 1E 42 2B 69 47 C8 44 34 54 2D D3 C7 71 29 64 99
   Z-Wave Lock Manager Debug       -----
   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 Lock Manager Debug       Raw:  01 0F 00 04 00 08 09 71 05 15 01 00 FF 06 01 00 FF
   Z-Wave Lock Manager             Status: Door locked manually [Node: 8]
   Z-Wave Lock Manager Debug       triggerEvent called
   Z-Wave Lock Manager Debug       ---
   Z-Wave Lock Manager Debug       dNodeID:   #8#
   Z-Wave Lock Manager Debug       eventNode: #8#
   Z-Wave Lock Manager Debug       dUserNo:   ##
   Z-Wave Lock Manager Debug       userNo:    ##
   Trigger                         Front Door Locked Manually
   Z-Wave Lock Manager Debug       Executing trigger
   Z-Wave Lock Manager Debug       Updating state: lockState
   Z-Wave Lock Manager Debug       -----
   Z-Wave Lock Manager Debug       Node ID 8 (Hex 8) found in lockIDs
   Z-Wave Watcher Debug            Raw command sent (Node 8): 01 11 00 13 08 0A 98 80 4C B5 1E 71 D4 D6 57 22 25 25 06 (True)
   Z-Wave Watcher Debug            Raw command received (Node 8): 01 08 00 04 00 08 02 98 40 21
   Z-Wave Lock Manager Debug       Node ID 8 (Hex 8) found in lockIDs
   Z-Wave                          received "Front Door Lock" status update unlocked (manually)
   Z-Wave Watcher Debug            Raw command received (Node 8): 01 0F 00 04 00 08 09 71 05 16 01 00 FF 06 02 00 FF
   Z-Wave Watcher Debug            Raw command received (Node 8): 01 23 00 04 00 08 1D 98 81 9D 57 68 DF DF F1 FD E5 6B A7 C0 CF 2C B3 AF B2 91 91 4C 2C 93 A6 1F 5E 59 28 B0 0B
   Z-Wave Lock Manager Debug       Node ID 8 (Hex 8) found in lockIDs
   Z-Wave Lock Manager Debug       Raw:  01 0F 00 04 00 08 09 71 05 16 01 00 FF 06 02 00 FF
   Z-Wave Lock Manager             Status: Door unlocked manually [Node: 8]
   Z-Wave Lock Manager Debug       triggerEvent called
   Z-Wave Lock Manager Debug       ---
   Z-Wave Lock Manager Debug       dNodeID:   #8#
   Z-Wave Lock Manager Debug       eventNode: #8#
   Z-Wave Lock Manager Debug       dUserNo:   ##
   Z-Wave Lock Manager Debug       userNo:    ##
   Trigger                         Front Door UnLocked Manually
   Z-Wave Lock Manager Debug       Executing trigger
   Z-Wave Lock Manager Debug       Updating state: lockState
   Z-Wave Lock Manager Debug       -----
   Z-Wave Lock Manager Debug       Node ID 8 (Hex 8) found in lockIDs
   Z-Wave Watcher Debug            Raw command sent (Node 8): 01 11 00 13 08 0A 98 80 8A 8A 1F 28 BB 36 68 54 25 26 62 (True)
   Z-Wave Watcher Debug            Raw command received (Node 8): 01 08 00 04 00 08 02 98 40 21
   Z-Wave Lock Manager Debug       Node ID 8 (Hex 8) found in lockIDs
   Z-Wave                          received "Front Door Lock" status update locked (via keypad)
   Z-Wave Watcher Debug            Raw command received (Node 8): 01 10 00 04 00 08 0A 71 05 12 01 00 FF 06 05 01 01 FF
   Z-Wave Watcher Debug            Raw command received (Node 8): 01 24 00 04 00 08 1E 98 81 C3 5D F8 2F B4 DA 23 EC E4 F3 C1 8A 82 E8 12 17 64 F8 90 8A 6C 63 31 C0 87 B8 2E BF DD
   Z-Wave Lock Manager Debug       Node ID 8 (Hex 8) found in lockIDs
   Z-Wave Lock Manager Debug       Raw:  01 10 00 04 00 08 0A 71 05 12 01 00 FF 06 05 01 01 FF
   Z-Wave Lock Manager             Status: User 1 locked door [Node: 8]
   Z-Wave Lock Manager Debug       triggerEvent called
   Z-Wave Lock Manager Debug       ---
   Z-Wave Lock Manager Debug       dNodeID:   #8#
   Z-Wave Lock Manager Debug       eventNode: #8#
   Z-Wave Lock Manager Debug       dUserNo:   #Any#
   Z-Wave Lock Manager Debug       userNo:    #1#
   Trigger                         Front Door UnLocked by Keypad
   Z-Wave Lock Manager Debug       Executing trigger
   Z-Wave Lock Manager Debug       ---
   Z-Wave Lock Manager Debug       dNodeID:   #8#
   Z-Wave Lock Manager Debug       eventNode: #8#
   Z-Wave Lock Manager Debug       dUserNo:   #Any#
   Z-Wave Lock Manager Debug       userNo:    #1#
   Trigger                         Front Door Locked by Keypad
   Z-Wave Lock Manager Debug       Executing trigger
   Z-Wave Lock Manager Debug       Updating state: lockState
   Z-Wave Lock Manager Debug       -----
   Z-Wave Lock Manager Debug       Node ID 8 (Hex 8) found in lockIDs
   Z-Wave Watcher Debug            Raw command sent (Node 8): 01 11 00 13 08 0A 98 80 B1 E5 B1 55 DC C0 19 D2 25 27 82 (True)
   Z-Wave Watcher Debug            Raw command received (Node 8): 01 08 00 04 00 08 02 98 40 21
   Z-Wave Lock Manager Debug       Node ID 8 (Hex 8) found in lockIDs
   Z-Wave                          received "Front Door Lock" status update unlocked (via keypad)
   Z-Wave Lock Manager Debug       Node ID 8 (Hex 8) found in lockIDs
   Z-Wave Lock Manager Debug       Raw:  01 10 00 04 00 08 0A 71 05 13 01 00 FF 06 06 01 01 FF
   Z-Wave Lock Manager             Status: User 1 unlocked door [Node: 8]
   Z-Wave Lock Manager Debug       triggerEvent called
   Z-Wave Lock Manager Debug       Updating state: lockState
   Z-Wave Watcher Debug            Raw command received (Node 8): 01 10 00 04 00 08 0A 71 05 13 01 00 FF 06 06 01 01 FF
   Z-Wave Watcher Debug            Raw command received (Node 8): 01 24 00 04 00 08 1E 98 81 A0 F3 29 BA 4E 73 A3 51 84 36 4D 5B ED 4A CC B5 DD BC 6C B1 27 E1 47 A9 29 6E 88 FA 04
   Z-Wave Lock Manager Debug       -----
   Z-Wave Lock Manager Debug       Node ID 8 (Hex 8) found in lockIDs

May 16, 2018 at 17:58:36
   Z-Wave Watcher Debug            Raw command sent (Node 8): 01 11 00 13 08 0A 98 80 31 0E 54 40 94 50 35 F4 25 28 C4 (True)
   Z-Wave Watcher Debug            Raw command received (Node 8): 01 08 00 04 00 08 02 98 40 21
   Z-Wave Lock Manager Debug       Node ID 8 (Hex 8) found in lockIDs
   Z-Wave                          received "Front Door Lock" status update lock jammed
   Z-Wave Watcher Debug            Raw command received (Node 8): 01 0F 00 04 00 08 09 71 05 09 00 00 FF 06 0B 00 FF
   Z-Wave Watcher Debug            Raw command received (Node 8): 01 23 00 04 00 08 1D 98 81 60 9F 2B 95 D5 92 81 55 A0 EF AC AF 84 ED E4 D9 1E B2 31 BC 01 71 52 9B 96 9F 40 CF
   Z-Wave Lock Manager Debug       Node ID 8 (Hex 8) found in lockIDs
   Z-Wave Lock Manager Debug       Raw:  01 0F 00 04 00 08 09 71 05 09 00 00 FF 06 0B 00 FF
   Z-Wave Lock Manager             Status: Deadbolt jammed on door [Node: 8]
   Z-Wave Lock Manager Debug       triggerEvent called
   Z-Wave Lock Manager Debug       ---
   Z-Wave Lock Manager Debug       dNodeID:   #8#
   Z-Wave Lock Manager Debug       eventNode: #8#
   Z-Wave Lock Manager Debug       dUserNo:   ##
   Z-Wave Lock Manager Debug       userNo:    ##
   Trigger                         Front Door Bolt Error
   Error                           Action has not been completely configured
   Z-Wave Lock Manager Debug       Executing trigger
   Z-Wave Lock Manager Debug       -----
   Z-Wave Lock Manager Debug       Node ID 8 (Hex 8) found in lockIDs
   Z-Wave Watcher Debug            Raw command sent (Node 8): 01 11 00 13 08 0A 98 80 31 0E 54 40 94 50 35 F4 25 29 C5 (True)
   Z-Wave                          received "Front Door Lock" status update unlocked (manually)
   Z-Wave Watcher Debug            Raw command received (Node 8): 01 08 00 04 00 08 02 98 40 21
   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 Lock Manager Debug       Raw:  01 0F 00 04 00 08 09 71 05 16 01 00 FF 06 02 00 FF
   Z-Wave Lock Manager             Status: Door unlocked manually [Node: 8]
   Z-Wave Lock Manager Debug       triggerEvent called
   Z-Wave Lock Manager Debug       ---
   Z-Wave Lock Manager Debug       dNodeID:   #8#
   Z-Wave Lock Manager Debug       eventNode: #8#
   Z-Wave Lock Manager Debug       dUserNo:   ##
   Z-Wave Lock Manager Debug       userNo:    ##
   Trigger                         Front Door UnLocked Manually
   Z-Wave Watcher Debug            Raw command received (Node 8): 01 0F 00 04 00 08 09 71 05 16 01 00 FF 06 02 00 FF
   Z-Wave Watcher Debug            Raw command received (Node 8): 01 23 00 04 00 08 1D 98 81 39 00 F4 7C 75 DB 8F 58 0F 32 79 5A 66 81 C7 2D F0 49 31 88 FC 28 8C 98 F5 79 10 53
   Z-Wave Lock Manager Debug       Executing trigger
   Z-Wave Lock Manager Debug       Updating state: lockState
   Z-Wave Lock Manager Debug       -----
   Z-Wave Lock Manager Debug       Node ID 8 (Hex 8) found in lockIDs
   Z-Wave Watcher Debug            Raw command sent (Node 8): 01 09 00 13 08 02 98 40 25 2A 38 (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 F0 3C 51 73 77 C3 F3 79 82 B4 3E 5A 35 15 84 8D C3 2B 8F 2A DA 25 2B C6 (True)
   Z-Wave Watcher Debug            Raw command sent (Node 8): 01 11 00 13 08 0A 98 80 05 F5 5A D3 89 41 56 FB 25 2C F2 (True)
   Z-Wave Watcher Debug            Raw command received (Node 8): 01 08 00 04 00 08 02 98 40 21
   Z-Wave Lock Manager Debug       Node ID 8 (Hex 8) found in lockIDs
   Z-Wave Watcher Debug            Raw command received (Node 8): 01 0D 00 04 00 08 07 62 03 FF 00 00 FE FE FF
   Z-Wave Watcher Debug            Raw command received (Node 8): 01 21 00 04 00 08 1B 98 81 3B 23 0A D5 3B 65 47 4D B3 0E BF E9 13 EF F2 4F 05 5D 1B 05 5E C8 71 78 3C 0C
   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


Thanks for all of your help. If you have any questions or suggestions that I can help with, please let me know.

Posted on
Thu May 17, 2018 1:05 am
howartp offline
Posts: 3331
Joined: Jan 09, 2014
Location: West Yorkshire, UK

Re: Schlage BE469 Status Reporting

Excellent.

As a side effect, I’m going to ask Matt about status update requests - I’d like it to request alarm status as well as door status per my earlier reply.

Will ask you to test if it gets added later.

Peter


Sent from my iPhone using Tapatalk Pro

Posted on
Thu May 17, 2018 5:35 am
Shavano offline
User avatar
Posts: 25
Joined: Jul 31, 2017
Location: San Antonio, TX

Re: Schlage BE469 Status Reporting

Sounds good. Thanks again.

Who is online

Users browsing this forum: No registered users and 1 guest