Schlage BE469NXCEN Touchscreen DeadBolt Responsiveness

Hardware
1

I was wondering how this lock is working for those who own it? First, it was a complete pain to include into my zwave network. I have a z-stick gen5 which is in the middle of my house and the lock is located in my garage (not too far away). In order to get it to work, I had to exclude it then I had to bring it within a few inches from my z stick. Now, sometimes it shows as dead on HA so i have to run the network test to revive it. Also, when i send lock/unlock commands, it takes forever to respond and sometimes i have to send the command multiple times. I’ve checked the status and see that it registers 5 neighbors in the area. I have a leviton switch (inside the house) about 5 ft from the z stick, a light bulb (inside the house) on the other side of the wall, a couple aeotec smart switch 6 devices (inside garage) which control the washer/dryer which are about 15 ft away from the lock, and an aeotec multisensor 6 which is usb powered and within a ft of the lock.

Can anyone think of a reason why there is such a delay when sending commands to the lock? and why sometimes it shows the device is dead? On some rare occasions the lock/unlock will respond quickly (within a couple seconds or so).

2

I included mine via Wink instead of a direct Z wave connection and I’ve never had an issue. I’ve considered at times moving it to the ZWave stick but since it works so well I never saw the point.

3

My locks were taking up to 4 - 5 seconds when I had them connected to a SmartThings hub and communicating with HA over MQTT. Now that I’ve moved them directly to an Aeotec Gen5 Z-stick on my RPi3, they generally respond within 2 seconds. This lines up with what I’m seeing in the Z-wave console node info, below. My locks are both roughly 20-35 feet from the hub, with several walls and/or a floor in-between. I do have other Z-wave devices nearby that can relay signals (they are Z-wave Plus dimmer switches, though these locks are not Plus).

averageRequestRTT: 1463
averageResponseRTT: 1833
battery_level: 96
capabilities: routing,beaming,frequent
friendly_name: Frontdoor
is_awake: true
is_failed: false
is_info_received: true
is_ready: true
is_zwave_plus: false
lastRequestRTT: 1483
lastResponseRTT: 1541
manufacturer_name: Schlage
max_baud_rate: 40000
neighbors: 1,2,3,4,9,10,11
new_entity_id: zwave.frontdoor
node_id: 7
node_name: Frontdoor
old_entity_id: zwave.frontdoor_7
product_name: BE469NXCEN Touchscreen DeadBolt
query_stage: Complete
receivedCnt: 18
receivedDups: 0
receivedTS: 2017-07-24 08:27:55:266
receivedUnsolicited: 2
retries: 0
sentCnt: 20
sentFailed: 0
sentTS: 2017-07-24 08:27:53:725

1 Like
4

thanks for the info guys, i’m wondering if i have to add more neighbors, possibly even an aeotec range extender 6 to help? I’m not really sure what’s causing such a poor response time and a bunch of errors… My node info shows a bunch of retries and sentFailed. Here’s my output:

averageRequestRTT: 7368
averageResponseRTT: 1801
battery_level: 100
capabilities: beaming,routing,frequent
friendly_name: Outside Garage Door Lock
is_awake: true
is_failed: false
is_info_received: true
is_ready: true
is_zwave_plus: false
lastRequestRTT: 9957
lastResponseRTT: 508
manufacturer_name: Schlage
max_baud_rate: 40000
neighbors: 48,49,42,13,45
new_entity_id: zwave.outside_garage_door_lock
node_id: 75
node_name: Outside Garage Door Lock
old_entity_id: zwave.outside_garage_door_lock_75
product_name: BE469NXCEN Touchscreen DeadBolt
query_stage: Complete
receivedCnt: 26
receivedDups: 18
receivedTS: 2017-07-23 23:56:28:454
receivedUnsolicited: 20
retries: 24
sentCnt: 60
sentFailed: 72
sentTS: 2017-07-23 23:56:16:138

5

Looks like it is taking an average of 7 seconds for the request and 1.8 seconds for the response…

6

I’ve got one of these locks, and it seems to be working pretty well for me. It was, in fact, my first z-wave device (other than the Aeotec USB stick), so is within range, rather than needing to be relayed through an intermediate hop.

Stats:

retries 0
product name BE469NXCEN Touchscreen DeadBolt
is info received true
old entity id zwave.front_door_lock_2
is awake true
lastRequestRTT 1519
capabilities routing, beaming, frequent
receivedCnt 111
sentTS 2017-07-24 20:37:50:949
averageRequestRTT 1474
location Front Door
is zwave plus false
receivedDups 0
node name Front Door Lock
sentFailed 0
new entity id zwave.front_door_lock
node id 2
neighbors 1, 6, 7, 8, 17, 18, 19, 20
battery level 98
max baud rate 40000
averageResponseRTT 1884
sentCnt 69
receivedUnsolicited 46
query stage Complete
manufacturer name Schlage
receivedTS 2017-07-24 20:37:52:522
is failed false
is ready true
lastResponseRTT 1573

My lock seems pretty responsive; not sure how I’d characterize it without some comparison, but it locks or unlocks within a couple of seconds or so.

7

I just purchased a range extender which will arrive on wednesday so I will report back with an update to let everyone know if it helped or not. I see your outputs and your failed are 0 while mine has a lot. Hopefully, this will resolve.

Also, I removed the multisensor 6 that is in my garage because I feel like it is a faulty device that may be causing or helping cause some of my issues.

1 Like
8

The range extender should help. Is your Z-stick listed in your neighbors list? Otherwise, requests will have to hop around to get from the hub to your lock. Looks like you have a LOT of devices based on those high node numbers - wow!

The average response time from your lock looks to be in-line with what everyone else here has. It’s whatever route your request is taking to get to the lock that is hosing you up. If your Z-stick isn’t listed as a neighbor and able to communicate directly, then you’re at the mercy of the devices in that relay. An extender (or any wire-powered Z-wave device, such as a switch) should be able to bring that time down if it is placed between your hub and the lock.

Also, if you haven’t done so already, be sure to try a manual “Heal Network” - you’ll want to run that when you add your new repeater anyway.

9

I have a number of devices and my response time is no more than 5 seconds, routinely. It could be the distance between his devices or maybe he paired the device next to the stick, but in the permanent position it is not optimal…

averageRequestRTT: 1374
averageResponseRTT: 1530
battery_level: 96
capabilities: frequent,routing,beaming
friendly_name: Front Door
is_awake: true
is_failed: false
is_info_received: true
is_ready: true
is_zwave_plus: false
lastRequestRTT: 1451
lastResponseRTT: 1507
manufacturer_name: Schlage
max_baud_rate: 40000
neighbors: 1,9,13,15,19,20,29,33,35,38,50,51,63,67,75,81,86,87,88,89,93,94,95,96,97,98,99,100,101,102,103,104,105,107,108,113,116,118,120,123
new_entity_id: zwave.front_door
node_id: 127
node_name: Front Door
old_entity_id: zwave.front_door_127
product_name: BE469NXCEN Touchscreen DeadBolt
query_stage: Complete
receivedCnt: 28
receivedDups: 0
receivedTS: 2017-07-24 20:55:32:339
receivedUnsolicited: 7
retries: 0
sentCnt: 25
sentFailed: 7
sentTS: 2017-07-24 20:55:30:833
10

I don’t have that many devices, but I do have about 30. My z stick is not listed as a neighbor unfortunately. However, I have devices which are further away from the z stick which are neighbors (also very weird). And yes, @BendedArrow i did pair it next to the stick because it would not pair at the current location no matter how many times I excluded the lock and set back to factory defaults. I know it wasn’t optimal, but it was the only way I could get it to pair. I do a manual heal to see if it’ll find closer neighbors or even list the controller as one, but no luck in all of the times i’ve tried.

11

Hello, nice of lot information. I have a Schlage lock as well and it’s working on HA, however like you side it takes about 3-5 seconds to get a response. For example, if I unlock it, I can hear the lock in about 2-3 seconds, but the webUI (frontend) just gets updated in after 4-5 seconds. The frontend switch reverts back to the original position, and then after a few seconds, flip again to the desired position.

I have other devices and looking at the RTT times it seems to be about right. My aotec USB stick does appear as neighbor to my Schalge locker though. Just for comparision, I have an outdoor switch too which the response is very quick and we can see that on the RTT times as well.

friendly_name: GE 12720 Outdoor Smart Switch
averageRequestRTT: 31
averageResponseRTT: 50
lastRequestRTT: 31
lastResponseRTT: 55
capabilities: beaming,routing,listening
max_baud_rate: 40000
neighbors: 1,6,7 <--- node1 is my Aotec USB stick
receivedCnt: 10
receivedDups: 0
receivedTS: 2017-07-24 20:52:44:153
receivedUnsolicited: 0
retries: 0
sentCnt: 16
sentFailed: 0
sentTS: 2017-07-24 20:52:44:097


friendly_name: Schlage FE599GR Wireless Door Lock
averageRequestRTT: 1294
averageResponseRTT: 1121
battery_level: 100
capabilities: beaming,routing,frequent
max_baud_rate: 40000
neighbors: 1,3,5,6  <-- node1 is my Aotec USB stick
lastRequestRTT: 1340
lastResponseRTT: 1363
receivedCnt: 18
receivedDups: 0
receivedTS: 2017-07-24 21:56:43:196
receivedUnsolicited: 5
retries: 0
sentCnt: 23
sentFailed: 0
sentTS: 2017-07-24 21:56:41:833

I’m also interested to see if the extender will make any difference for your @nVINCEble. Please let us know.

12

@tchellomello the RTT on your smart switch is pretty good. Its also plugged in, right?

13

Yes @BendedArrow. The smart switch is connected.

14

I installed the aeotec extender 6 and it does not have any neighbors. I’m assuming it should have neighbors right?

here is my log:

averageResponseRTT: 441
capabilities: listening,routing,beaming
friendly_name: Aeotec ZW117 Range Extender 6
is_awake: true
is_failed: false
is_info_received: true
is_ready: true
is_zwave_plus: true
lastRequestRTT: 263
lastResponseRTT: 389
manufacturer_name: Aeotec
max_baud_rate: 40000
new_entity_id: zwave.aeotec_zw117_range_extender_6
node_id: 86
node_name: Aeotec ZW117 Range Extender 6
old_entity_id: zwave.aeotec_zw117_range_extender_6_86
product_name: ZW117 Range Extender 6
query_stage: Complete
receivedCnt: 16
receivedDups: 7
receivedTS: 2017-07-27 12:31:44:284
receivedUnsolicited: 10
retries: 0
sentCnt: 10
sentFailed: 0
sentTS: 2017-07-27 12:31:43:896
15

If running Heal Network did not help, try removing and re-adding the lock to the network so that it can scan for neighbors.

16

Ok i added the extender on the other side of the garage wall about half way between the z-stick and the bolt. It seems to be more reliable, but I can’t really say that it’s much faster. Node 86 is the extender. here is my log:

averageRequestRTT: 1913
averageResponseRTT: 2250
battery_level: 98
capabilities: beaming,frequent,routing
friendly_name: Outside Garage Door
is_awake: true
is_failed: false
is_info_received: true
is_ready: true
is_zwave_plus: false
lastRequestRTT: 2004
lastResponseRTT: 2077
manufacturer_name: Schlage
max_baud_rate: 40000
neighbors: 10,11,48,49,83,86
new_entity_id: zwave.outside_garage_door
node_id: 75
node_name: Outside Garage Door
old_entity_id: zwave.outside_garage_door_75
product_name: BE469NXCEN Touchscreen DeadBolt
query_stage: Complete
receivedCnt: 19
receivedDups: 4
receivedTS: 2017-07-31 11:07:16:870
receivedUnsolicited: 2
retries: 1
sentCnt: 24
sentFailed: 22
sentTS: 2017-07-31 11:07:14:793
17

2 seconds is about right. Are you seeing a different response time between when you toggle the UI switch and the lock turning?

The only way I could see this response time improving would be to have the z-stick in range for a direct connection, but even then it would likely only shave 0.25 - 0.5 seconds max. It’s not going to be nearly as much improvement as what the repeater shaved off of your original 7.3 second request time (note that response time from the lock was never the issue - it was all about the z-stick getting the signal to the lock).

What catches my eye about this info, though, is the high number of send failures. Maybe those are from before you repositioned the repeater? Just make sure you do a network heal anytime you add/remove or physically move a node.

18

i do notice that toggling the switch from the UI and response of the lock seems more reliable and a little quicker. Before I had to toggle the switch several times. It does a network heal every night at midnight and i also run in once in a while during the day. I do see all the send failures and i’m not sure why I’m getting that for the lock.

1 Like