Schlage locks (BE469ZP) not notifying manual unlock

[BONeil]

EISY 5.8.3, I recently reset my zwave network and dongle. Everything is back and good, locks respond fast and a heal takes under 2 minutes without any retries or comm problems in Event Viewer. Connection speed is good and nodes seem well placed.

However, my two Schlage BE469ZP no longer notify the EISY when they are manually unlocked, so their state in the ISY never changes when it is manually unlocked. This did work prior to the reset, but I have no idea how to get it working again since for all intents and purposes, Zwave is working well and fast with little latency.

I tried exclude\include, zwave compatability mode, heal the world, update neighbors, update with interview, detect button presses on\off. The locks both read as S2 access. Also, I did add a ULock zwave recently which shows up as S2 Access [S0] if the secure inclusion parameters matter in this instance. The ULock DOES notify the EISY when it is unlocked, so not a problem with the overall Zwave network as far as I can tell.

One concerning thing is I see is that they show up as 'Interview Not done' and I have interviewed them numerous times.

In X-Ray -> [DH All Devices]:

Devices list: 
  1 Interview Not done --> assuming EISY radio since other devices
  2 Interview done --> GE Enbrighten
  3 Interview done --> GE Enbrighten
  4 Interview done --> GE Enbrighten
  5 Interview done --> ULock
  6 Interview done --> GE Enbrighten
 10 Interview Not done  --> Schlage1
 14 Interview Not done --> Schlage2

Lastly, the locks were paried next to the ISY and moved to their location after paring which was the conventional wisdom a few years back, not sure that is still the case.

Let me know your thoughts on anything I've missed and any ideas to further troubleshoot.

 

Edited May 12 by BONeil

[JeffR]

I have this lock and it has never relayed status on manual lock\unlock events.  I use a YoLink door sensor and when the door closes a program queries the lock in 5 minutes and updates the lock status. If you unlock but don't open\close the door the status will be incorrect.  Periodically querying the lock for its status will probably not be good for battery life.

Below I unlocked manually and nothing showed up in the logs.  I then ran a query, which returned unlocked for the status, and then I clicked lock in the EISY and the results are shown below.  The command was successfully executed and the status was changed to locked.

Sun 05/12/2024 12:01:20 PM : [ZW-TX-A 00161   2.0  ] [ZY002_1] Door Lock Config Get

Sun 05/12/2024 12:01:20 PM : [ZW-TX-A 00162   2.0  ] [ZY002_1] Door Lock Config Get

Sun 05/12/2024 12:01:20 PM : [ZW-TX-A 00163   2.0  ] [ZY002_1] Battery Get

Sun 05/12/2024 12:01:21 PM : [ZW-DONE 00161   2.0  ] [ZY002_1] Door Lock Config Get

Sun 05/12/2024 12:01:22 PM : [D2D EVENT       ] Event [ZY002_1] [ST] [0] uom=11 prec=0

Sun 05/12/2024 12:01:22 PM : [ZY002_1         ]       ST   0 (uom=11 prec=0)

Sun 05/12/2024 12:01:22 PM : [ZW-DONE 00162   2.0  ] [ZY002_1] Door Lock Config Get

Sun 05/12/2024 12:01:23 PM : [ZW-DONE 00163   2.0  ] [ZY002_1] Battery Get

Sun 05/12/2024 12:01:27 PM : [ZW-TX-A 00164   2.0  ] [ZY002_1] Door Lock Set mode=255

Sun 05/12/2024 12:01:29 PM : [ZW-DONE 00164   2.0  ] [ZY002_1] Door Lock Set mode=255

Sun 05/12/2024 12:01:35 PM : [D2D EVENT       ] Event [ZY002_1] [ST] [100] uom=11 prec=0

Sun 05/12/2024 12:01:35 PM : [ZY002_1         ]       ST 100 (uom=11 prec=0)

[gzahar]

I received the following instructions from another member that fixed mine:

1) Z wave compatibility mode on

2) Z wave validation off

3) Z wave rewrite all device links

[BONeil]

@gzahar That worked!! 

Thank you

[JeffR]

@gzahar Thank you for the assist!  Worked for me as well.