Schlage / Allegion BE469 Z-Wave lock

Configuration
1

Are there any tips for how to properly pair/configure a Schlage BE469 deadbolt with HA?

I successfully excluded it from SmartThings, then did a secure include in HA OS (using Z-Wave JS).

I have since re-excluded and re-included sort of “successfully” multiple times.

The inclusion process never seems to finish; it just goes back to the “start inclusion” popup.

If I go to the devices page, the lock is shown as a new unknown node. Doing a “re-interview” successfully populates all the info on the lock, including manufacturer (Allegion), model no. (BE469), firmware (88.21), etc.

However, I can not lock or unlock the door from Lovelace, and the locked/unlocked status is always “locked”. The history always says unknown.

Basically, it looks like it is added correctly, but it doesn’t work.

Is there anything important that I’m missing? Do I need to exclude it again and do a full factory reset before re-including? …or is there something obvious that I’m missing?

I expected it to “just work”, but that’s only because everything else has :slight_smile:

Thanks!

3 Likes
2

Here is what I can access from the Z-Wave JS log:

2021-08-16T02:46:27.925Z CNTRLR » [Node 039] Assigning SUC return route...
2021-08-16T02:46:27.939Z CNTRLR   the inclusion process was stopped
2021-08-16T02:46:31.292Z CNTRLR   Failed to execute controller command after 1/3 attempts. Scheduling next try i
                                  n 100 ms.
2021-08-16T02:46:31.863Z CNTRLR   [Node 039] Beginning interview - last completed stage: None
2021-08-16T02:46:31.864Z CNTRLR   [Node 039] new node, doing a full interview...
2021-08-16T02:46:31.865Z CNTRLR » [Node 039] querying protocol info...
2021-08-16T02:46:31.894Z CNTRLR « [Node 039] received response for protocol info:
                                  basic device class:    Routing Slave
                                  generic device class:  Entry Control
                                  specific device class: Secure Keypad Door Lock
                                  node type:             Routing End Node
                                  is always listening:   false
                                  is frequent listening: 1000ms
                                  can route messages:    true
                                  supports security:     false
                                  supports beaming:      true
                                  maximum data rate:     40000 kbps
                                  protocol version:      3
2021-08-16T02:46:31.931Z CNTRLR   [Node 039] Interview stage completed: ProtocolInfo
2021-08-16T02:46:31.932Z CNTRLR » [Node 039] querying node info...
2021-08-16T02:46:31.972Z DRIVER   Dropping message with invalid payload
2021-08-16T02:46:32.111Z DRIVER   Dropping message with invalid payload
2021-08-16T02:46:32.159Z DRIVER   Dropping message with invalid payload
2021-08-16T02:46:32.374Z CNTRLR « [Node 039] node info received
                                  supported CCs:
                                  · Application Status
                                  · Manufacturer Specific
                                  · Firmware Update Meta Data
                                  · Security
                                  · Version
                                  controlled CCs:
2021-08-16T02:46:32.399Z CNTRLR   [Node 039] Interview stage completed: NodeInfo
2021-08-16T02:46:32.403Z CNTRLR » [Node 039] querying securely supported commands...
2021-08-16T02:46:32.558Z CNTRLR « [Node 039] Received updated node info
2021-08-16T02:46:33.234Z DRIVER   Dropping message with invalid payload
2021-08-16T02:46:40.294Z DRIVER   Dropping message with invalid payload
2021-08-16T02:46:42.747Z CNTRLR   [Node 039] Timed out while waiting for a response from the node
2021-08-16T02:46:42.747Z CNTRLR   [Node 039] The node is not included securely. Continuing interview non-securel
                                  y.
2021-08-16T02:46:42.776Z CNTRLR   [Node 039] Interviewing Manufacturer Specific...
2021-08-16T02:46:42.777Z CNTRLR » [Node 039] querying manufacturer information...
2021-08-16T02:46:42.946Z CNTRLR « [Node 039] received response for manufacturer information:
                                    manufacturer: Allegion (0x3b)
                                    product type: 0x6341
                                    product id:   0x5044
2021-08-16T02:46:42.978Z CNTRLR   [Node 039] Interviewing Version...
2021-08-16T02:46:42.979Z CNTRLR » [Node 039]   querying the CC version for Version...
2021-08-16T02:46:43.148Z CNTRLR   [Node 039]   supports CC Version (0x86) in version 1
2021-08-16T02:46:43.148Z CNTRLR » [Node 039] querying node versions...
2021-08-16T02:46:43.357Z CNTRLR « [Node 039] received response for node versions:
                                    library type:      Routing Slave (0x06)
                                    protocol version:  3.42
                                    firmware versions: 88.21
2021-08-16T02:46:43.358Z CNTRLR » [Node 039] querying CC versions...
2021-08-16T02:46:43.358Z CNTRLR » [Node 039]   querying the CC version for Basic...
2021-08-16T02:47:07.927Z CNTRLR   [Node 039]   supports CC Basic (0x20) in version 1
2021-08-16T02:47:07.927Z CNTRLR » [Node 039]   querying the CC version for Door Lock...
2021-08-16T02:47:07.962Z CNTRLR   Failed to execute controller command after 1/3 attempts. Scheduling next try i
                                  n 100 ms.
2021-08-16T02:47:08.075Z CNTRLR   The controller response indicated failure after 2/3 attempts. Scheduling next 
                                  try in 1100 ms.
2021-08-16T02:47:09.361Z CNTRLR   [Node 039]   supports CC Door Lock (0x62) in version 2
2021-08-16T02:47:09.362Z CNTRLR » [Node 039]   querying the CC version for User Code...
2021-08-16T02:47:09.615Z CNTRLR   [Node 039]   supports CC User Code (0x63) in version 1
2021-08-16T02:47:09.615Z CNTRLR » [Node 039]   querying the CC version for Manufacturer Specific...
2021-08-16T02:47:09.922Z CNTRLR   [Node 039]   supports CC Manufacturer Specific (0x72) in version 1
2021-08-16T02:47:09.922Z CNTRLR   [Node 039]   skipping query for Security (0x98) because max implemented versio
                                  n is 1
2021-08-16T02:47:09.923Z CNTRLR   [Node 039]   skipping query for Application Status (0x22) because max implemen
                                  ted version is 0
2021-08-16T02:47:09.923Z CNTRLR » [Node 039]   querying the CC version for Firmware Update Meta Data...
2021-08-16T02:47:10.155Z CNTRLR   [Node 039]   supports CC Firmware Update Meta Data (0x7a) in version 2
2021-08-16T02:47:10.231Z CNTRLR   [Node 039] Embedded device config loaded
2021-08-16T02:47:10.238Z CNTRLR   [Node 039] Interviewing Door Lock...
2021-08-16T02:47:10.240Z CNTRLR » [Node 039] requesting lock configuration...
2021-08-16T02:47:10.275Z CNTRLR   Failed to execute controller command after 1/3 attempts. Scheduling next try i
                                  n 100 ms.
2021-08-16T02:47:20.821Z CNTRLR   [Node 039] Timed out while waiting for a response from the node
2021-08-16T02:47:20.821Z CNTRLR » [Node 039] requesting current lock status...
2021-08-16T02:47:31.152Z CNTRLR   [Node 039] Timed out while waiting for a response from the node
2021-08-16T02:47:31.181Z CNTRLR   [Node 039] Interviewing User Code...
2021-08-16T02:47:31.182Z CNTRLR » [Node 039] querying number of user codes...
2021-08-16T02:47:41.292Z CNTRLR   [Node 039] Timed out while waiting for a response from the node
2021-08-16T02:47:41.293Z CNTRLR   [Node 039] Querying number of user codes timed out, skipping interview...
2021-08-16T02:47:41.321Z CNTRLR   [Node 039] Interview stage completed: CommandClasses
2021-08-16T02:47:41.323Z CNTRLR   [Node 039] Interview stage completed: OverwriteConfig
2021-08-16T02:47:41.324Z CNTRLR   [Node 039] Interview completed
2021-08-16T02:47:41.326Z CNTRLR   [Node 039] The node is ready to be used
2021-08-16T02:48:20.223Z CNTRLR   [Node 023] compat mapping found, treating V1 Alarm frame as Notification Report
2021-08-16T02:51:36.329Z CNTRLR   [Node 039] Timed out while waiting for a response from the node
2021-08-16T02:51:57.676Z CNTRLR   [Node 039] Timed out while waiting for a response from the node

Where is the full log located on Home Assistant OS?

3

Most locks must be included securely. A device can only be included securely after a fresh factory reset. The inclusion process must complete within 15 seconds of starting. some devices need a very strong signal for initial inclusion.

Do you have the Schlage or Allegion version? The database indicates some people may have had issues with the Schlage version.

4

What @Prodigyplace recommended above but also a suggestion would be to replace batteries regardless what you may think they are or what it last said they were when it was paired. I spent two nights trying to get one of my locks included after removing… as soon as I put fresh batteries in it paired right away. (Maybe worth a shot)

2 Likes
5

Thanks folks,

I went ahead last night and excluded, factory reset, and re-included, and pairing was MUCH faster. The interview information came up right away and I didn’t have to re-interview for things to show up correctly.

However, as you can see in the log I posted, it dit not include securely, and there is no indication as to why:
The node is not included securely. Continuing interview non-securely.

The batteries are pretty fresh (a few weeks), but I’ll swap them out and try again.

This is the Schlage version, not Allegion, but it shows up as Allegion when it queries.

Any other suggestions?

6

If zwavejs shows it as Allegion that us what the firmware on it says. They have different Z-Wave manufacturer IDs.

7

So I excluded the lock again, put in new batteries, reset to factory defaults, and re-included it.

This time I also re-located my NUC to within 1 ft. It was about 10 ft. line-of-sight.

It did not finish the interview process, but it did “successfully” add the node.

Then I excluded the lock again, reset to factory defaults again, and re-included it. It still didn’t finish the interview process.

Finally I did a re-interview, and it seems to properly report locked/unlocked status now.

…but I still can’t lock or unlock the damned door.

Any other suggestions?

9

If you search for the device from Configuration >>Devices, are there any disabled entities?

10

Here is the Device Info:

BE469
by Allegion
Firmware: 88.21

Only 1 disabled entity for the lock:

sensor.node_41_node_status

The other entities are:

lock.touchscreen_deadbolt
binary_sensor.touchscreen_deadbolt_the_current_status_of_the_door
11

I have the same lock. I’m sure you came across my guide on Google, but if not, here you go: https://smarthomepursuits.com/add-schlage-zwave-to-home-assistant/

From your reading your latest comments in this thread, it sounds like you have added it correctly by clicking Add Node Secure, but it’s only being added like a regular node. Did you add a network key?

Locking/unlocking can only be done if the device was successfully added securely…I think that explains why the other entities show up correctly, but it’s unable to actually lock or unlock.

1 Like
12

Hey @djbrooks022,

That’s a great guide, thanks for posting!

I believe I had already done everything in your guide correctly, and I think the lock is added securely. (Edit: it is not included securely)

I have a Network key; the new Zwave JS creates one automatically on installation, and it’s definitely there.

Do you know where the Zwave JS log is kept? The log on the supervisor page only shows the most recent ~100 lines or so, which is not nearly enough.

There’s nothing in /var/log, and the only thing in /config is home-assistant.log.

13

That’s great! I’m glad my guide helped you out. Hopefully you can lock/unlock now.

I don’t know where the Zwave JS log files are, but I can check tomorrow if you don’t find it by then.

14

I still can’t lock or unlock, but I’m not sure if this was added securely or not.

Without the logs, there’s no way to tell. Is there any indicator on a device whether or not it is secure?

15

This DOES NOT WORK.

It refuses to do a secure inclusion. I have tried every conceivable combination of:

exclude -> reset to factory defaults -> set up lock with factory code -> secure include
exclude -> reset to factory defaults -> secure include -> set up lock with factory code
exclude -> reset to factory defaults -> set up lock with user code -> secure include
exclude -> reset to factory defaults -> secure include -> set up lock with user code

There has to be something else.

Here is the part of the log that I can actually read:

2021-09-01T17:03:22.164Z CNTRLR   starting inclusion process...
2021-09-01T17:03:22.184Z CNTRLR   handling add node request (status = Ready)
2021-09-01T17:03:22.185Z CNTRLR     the controller is now ready to add nodes
2021-09-01T17:03:27.872Z CNTRLR   handling add node request (status = NodeFound)
2021-09-01T17:03:28.144Z CNTRLR   handling add node request (status = AddingSlave)
2021-09-01T17:03:31.931Z CNTRLR   handling add node request (status = ProtocolDone)
2021-09-01T17:03:31.931Z CNTRLR   stopping inclusion process...
2021-09-01T17:03:32.000Z CNTRLR   handling add node request (status = Done)
2021-09-01T17:03:32.000Z CNTRLR   done called for 46
2021-09-01T17:03:32.001Z CNTRLR   finished adding node 46:
                                    basic device class:    Routing Slave
                                    generic device class:  Entry Control
                                    specific device class: Secure Keypad Door Lock
                                    supported CCs: 
                                    · Basic (0x20)
                                    · Door Lock (0x62)
                                    · User Code (0x63)
                                    · Manufacturer Specific (0x72)
                                    · Security (0x98)
                                    · Version (0x86)
                                    · Application Status (0x22)
                                    · Firmware Update Meta Data (0x7a)
                                    controlled CCs: 
2021-09-01T17:03:32.002Z CNTRLR » [Node 046] Assigning SUC return route...
2021-09-01T17:03:32.011Z CNTRLR   the inclusion process was stopped
2021-09-01T17:03:42.870Z CNTRLR   [Node 046] Security S0 bootstrapping failed, the node was not granted the S0 s
                                  ecurity class: a secure inclusion timer has elapsed.
2021-09-01T17:03:42.872Z CNTRLR   [Node 046] Beginning interview - last completed stage: None
2021-09-01T17:03:42.873Z CNTRLR   [Node 046] new node, doing a full interview...
2021-09-01T17:03:42.873Z CNTRLR » [Node 046] querying protocol info...
2021-09-01T17:03:42.896Z CNTRLR « [Node 046] received response for protocol info:
                                  basic device class:    Routing Slave
                                  generic device class:  Entry Control
                                  specific device class: Secure Keypad Door Lock
                                  node type:             Routing End Node
                                  is always listening:   false
                                  is frequent listening: 1000ms
                                  can route messages:    true
                                  supports security:     false
                                  supports beaming:      true
                                  maximum data rate:     40000 kbps
                                  protocol version:      3
2021-09-01T17:03:42.920Z CNTRLR   [Node 046] Interview stage completed: ProtocolInfo
2021-09-01T17:03:42.921Z CNTRLR » [Node 046] querying node info...
2021-09-01T17:03:42.982Z CNTRLR « [Node 046] node info received
                                  supported CCs:
                                  · Application Status
                                  · Manufacturer Specific
                                  · Firmware Update Meta Data
                                  · Security
                                  · Version
                                  controlled CCs:
2021-09-01T17:03:42.983Z CNTRLR   [Node 046] Interview stage completed: NodeInfo
2021-09-01T17:03:42.985Z CNTRLR   [Node 046] Interviewing Manufacturer Specific...
2021-09-01T17:03:42.985Z CNTRLR » [Node 046] querying manufacturer information...
2021-09-01T17:03:43.058Z CNTRLR « [Node 046] received response for manufacturer information:
                                    manufacturer: Allegion (0x3b)
                                    product type: 0x6341
                                    product id:   0x5044
2021-09-01T17:03:43.060Z CNTRLR   [Node 046] Interviewing Version...
2021-09-01T17:03:43.061Z CNTRLR » [Node 046]   querying the CC version for Version...
2021-09-01T17:03:43.156Z CNTRLR   [Node 046]   supports CC Version (0x86) in version 1
2021-09-01T17:03:43.157Z CNTRLR » [Node 046] querying node versions...
2021-09-01T17:03:43.281Z CNTRLR « [Node 046] received response for node versions:
                                    library type:      Routing Slave (0x06)
                                    protocol version:  3.42
                                    firmware versions: 88.21
2021-09-01T17:03:43.281Z CNTRLR » [Node 046] querying CC versions...
2021-09-01T17:03:43.282Z CNTRLR » [Node 046]   querying the CC version for Basic...
2021-09-01T17:03:43.341Z CNTRLR   [Node 046]   supports CC Basic (0x20) in version 1
2021-09-01T17:03:43.342Z CNTRLR » [Node 046]   querying the CC version for Door Lock...
2021-09-01T17:03:43.399Z CNTRLR   [Node 046]   supports CC Door Lock (0x62) in version 2
2021-09-01T17:03:43.400Z CNTRLR » [Node 046]   querying the CC version for User Code...
2021-09-01T17:03:43.507Z CNTRLR   [Node 046]   supports CC User Code (0x63) in version 1
2021-09-01T17:03:43.507Z CNTRLR » [Node 046]   querying the CC version for Manufacturer Specific...
2021-09-01T17:03:45.146Z CNTRLR   [Node 046]   supports CC Manufacturer Specific (0x72) in version 1
2021-09-01T17:03:45.146Z CNTRLR   [Node 046]   skipping query for Application Status (0x22) because max implemen
                                  ted version is 0
2021-09-01T17:03:45.147Z CNTRLR » [Node 046]   querying the CC version for Firmware Update Meta Data...
2021-09-01T17:03:45.205Z CNTRLR   [Node 046]   supports CC Firmware Update Meta Data (0x7a) in version 2
2021-09-01T17:03:45.206Z CNTRLR   [Node 046]   skipping query for Security (0x98) because max implemented versio
                                  n is 1
2021-09-01T17:03:45.243Z CNTRLR   [Node 046] Embedded device config loaded
2021-09-01T17:03:45.246Z CNTRLR   [Node 046] Interviewing Door Lock...
2021-09-01T17:03:45.246Z CNTRLR » [Node 046] requesting lock configuration...
2021-09-01T17:03:55.300Z CNTRLR   [Node 046] Timed out while waiting for a response from the node
2021-09-01T17:03:55.301Z CNTRLR » [Node 046] requesting current lock status...
2021-09-01T17:04:05.424Z CNTRLR   [Node 046] Timed out while waiting for a response from the node
2021-09-01T17:04:05.445Z CNTRLR   [Node 046] Interviewing User Code...
2021-09-01T17:04:05.445Z CNTRLR » [Node 046] querying number of user codes...
2021-09-01T17:04:15.498Z CNTRLR   [Node 046] Timed out while waiting for a response from the node
2021-09-01T17:04:15.499Z CNTRLR   [Node 046] Querying number of user codes timed out, skipping interview...
2021-09-01T17:04:15.518Z CNTRLR   [Node 046] Interview stage completed: CommandClasses
2021-09-01T17:04:15.519Z CNTRLR   [Node 046] Interview stage completed: OverwriteConfig
2021-09-01T17:04:15.520Z CNTRLR   [Node 046] Interview completed
2021-09-01T17:04:15.521Z CNTRLR   [Node 046] The node is ready to be used
2021-09-01T17:05:46.956Z CNTRLR   [Node 046] Timed out while waiting for a response from the node

Clearly the most important bit is:

Security S0 bootstrapping failed, the node was not granted the S0 security class: a secure inclusion timer has elapsed.

I have read that the timer is 15 seconds. Is there any way to increase that timer? Why is it timing out? It has direct line-of-sight to the Zooz stick.

16

That timing is part of the secure standard. Sometimes a device needs a stronger signal for initial iinclusion.

17

I tried this again about 6 times, with the Zooz stick literally directly on top of the antenna traces on the Schlage lock PCB.

It will not include securely. It’s trying to use S0 inclusion, and it just refuses to do it.

The network key is definitely present. Is there some kind of magic incantation that I’m not uttering that would make this work?

18

I have been having the same issue. Same error messages as well. I just purchased this lock, and have been unable to include it.

I always see the S0 error and then everything that follows times out. It’s seems as if whatever it’s asking of the lock gets ignored after the error.

I also placed my husbzb-1 right next to the lock PCB. I don’t think its a hop latency issue.

19

Just tried at least 10 more times. When I started this, I was at node id 31; now I’m at 61.

Does s0 secure inclusion work with non-plus Z-wave devices?

I am nonplussed :slight_smile: .

1 Like
20

When you retry inclusion you MUST factory reset the lock first. If this is not done secure inclusion will fail every time. I believe it is part of the specification for secure inclusion.The process, once started must also be completed within 15 seconds too.

21

Thanks @Prodigyplace, after the first 5 times I factory reset it every single time (the next 25 times).

When you say “the process, once started” you mean from the time you start secure inclusion, not from the time you factory reset, which would be absurd, right?