Thanks very much for taking the time to look at the table data I added. I realize that after a long time trying to help others as you clearly have done, it had become challenging to ask for information that they might not otherwise know how to provide, so, it's best to just collect the whole data set.
I felt pretty sure that the RF part of the Zwave setup here was operating well enough. Glad you concur.
Watching the 'live log' of these two locks, there is no perceptible lag in the locks reporting to Hubitat of their manual status change. Flip the knob; get the status change readout immediately. To assure myself of this, I created a quick automation rule that turns on and off a Zigbee test light to 'match' the lock status, and that always works perfectly. Hence, my assertion that the 908.42 MHz RF path from the hub to the lock is not a major factor in this anomaly.
The relatively large number of 'reroutes' shown on the one lock you observed does not appear to be a valid number (test gear to see this) and may actually be telltale about the underlying driver problem. Hubitat might be recording route changes that have not occurred according to the RF capture of AFSK data at 908.42 MHz.
You have provided additional data points that point to the same conclusion I and others have made, which is related to the 'driver' for the lock in question. You've even suggested that I use different drivers for the two locks I have, likely a good idea.
I have in fact already tried some combinations of different drivers independent of this thread, without much luck. I will try additional combinations.
If any of these driver combinations can be made to work, I will post the results here.
I further appreciate that you noted my comment that these locks did lock / unlock via command on Wink and further that they worked for some time after I converted to Hubitat. Further investigation of past threads on this topic show that others have experienced similar issues of the Schlage Zwave lock remote control suddenly becoming partially inoperative, at some various points in the past. These data points appear to indicate that the anomalies being reported are related to the commands being sent by Hubitat and that the Hubitat environment had been changed at some point that caused these anomalies. This assertion has been anecdotally recorded by others, elsewhere. I hope that Hubitat staff is reading this thread and elects to contact suitable engineering resources at Allegion to find out the root cause of the problem and then create a robust way of working around any incompatibilities.
