Running Version 5.3.3
Fairly solid Mesh by my experience but not formally tested with a Z-Wave Tool.

I have four Z-Wave Plus, Schlage BE469ZP Locks, I also have a couple of Zooz Z-Wave Plus Motion Sensors and a Dome Mouser. 

They all seem to operate fairly reliably except for keeping their current status consistently updated in ISY. 
I am less concerned with the Motion and Mouser but would like to always have the proper current state of the locks reported.

The locks respond to commands and report status changes when operated.
However, after the 3am ISY System query, SOME, usually not all, report status UNKNOWN.
I cannot find a common explanation of when one will or will not report an UNKNOWN status.
This morning for example, the one furthest from the ISY reported a LOCKED status, the two Closest to ISY report UNKNOWN and the last one reports UNLOCKED but that one was used this morning already.

Any thoughts?  

Thanks!
Bill

First thing that stands out is you have a broken mesh.  You don't have any powered devices that act as repeaters.  This would explain the hit/miss of query information and intermittent issues.

2 hours ago, simplextech said:

First thing that stands out is you have a broken mesh.  You don't have any powered devices that act as repeaters.  This would explain the hit/miss of query information and intermittent issues.

Thanks,

Possible, but I do have powered devices (On/Off Power Modules Plugged in to outlets within 10' of each of the locks.
Three Zooz double Outlets (Zen25)
One a Honeywell UltraPro Dual Outlet

I have 25 Z-Wave Devices, 7 battery powered

The one lock that reported properly was near one of the Zen25s and located in an out building ironically!

From my own experience, I don't think this is a broken mesh issue, but rather some sort of "incompatibility" with particular z-wave devices, in special with the (in)famous Schlage BE469ZP Lock. I have two of these locks, one is the older model BE469NX, firmware ver. 0.8.0. This older one responds perfectly fine to query, does also show the complete menu in the AC, zero issues. The newer BE469ZP is responding "UNKNOWN" to query and the menu is missing the "options" tab. I tried everything possible with this lock, installed it at 10 inch distance from ISY, downgraded my ISY firmware, remove it, add it, remove it and add it again.... hours of painful tests.... same result. As such I gave up on it, found an older 469NX on eBay and I hope it will solve this issue. I also forgot to mention, the older one is farther away from ISY. I have a clean network with lots of wired devices (repeaters).

On 5/27/2021 at 2:33 PM, oper8 said:

From my own experience, I don't think this is a broken mesh issue, but rather some sort of "incompatibility" with particular z-wave devices, in special with the (in)famous Schlage BE469ZP Lock. I have two of these locks, one is the older model BE469NX, firmware ver. 0.8.0. This older one responds perfectly fine to query, does also show the complete menu in the AC, zero issues. The newer BE469ZP is responding "UNKNOWN" to query and the menu is missing the "options" tab. I tried everything possible with this lock, installed it at 10 inch distance from ISY, downgraded my ISY firmware, remove it, add it, remove it and add it again.... hours of painful tests.... same result. As such I gave up on it, found an older 469NX on eBay and I hope it will solve this issue. I also forgot to mention, the older one is farther away from ISY. I have a clean network with lots of wired devices (repeaters).

Kind of nice to know someone else saw this!

Bill

There are a number of unresolved issues with 5.x and battery zwave devices.  Prime example for me - All my battery zwave sensors no longer report battery status (unless I manually wake them up and poll/sync them).  All worked fine under 4.x

6 large installs, 6 more modest.  All same problem.

UDI is aware (I opened an explicit issue over a year ago, got one reply and nothing - tried to ask for updates over a dozen times), but doesn't seem interested or consider it a priority.

In one install, I had to go back to 4.x because the client required reliable battery reporting.  Very unfortunate.

On 4/2/2021 at 9:14 AM, WFP said:

The locks respond to commands and report status changes when operated.
However, after the 3am ISY System query, SOME, usually not all, report status UNKNOWN.
I cannot find a common explanation of when one will or will not report an UNKNOWN status.
This morning for example, the one furthest from the ISY reported a LOCKED status, the two Closest to ISY report UNKNOWN and the last one reports UNLOCKED but that one was used this morning already.

Any thoughts?  

When you right click the locks (in the AC) and look at Z-Wave/Z-wave Options, is Always Awake set to no?

On 7/3/2021 at 2:15 PM, gzahar said:

When you right click the locks (in the AC) and look at Z-Wave/Z-wave Options, is Always Awake set to no?

They are all set to Yes...should they be No?

46 minutes ago, WFP said:

They are all set to Yes...should they be No?

I believe so (since they are battery powered and probably go to sleep after a time of inactivity). 

It made a difference for me, I was getting the same results as you before I changed it.