Once again, you’re jumping all over the place in terms of troubleshooting.
I just tried installing KeyMaster myself and IMO it’s a not a reliable application.
You need to straighten out your zwave communication with your locks first. KeyMaster depends on the correct entities being created first at the Zwave/HA level, and communicating consistently.
I hear ya, and appreciate the time. Im throwing everything out as something to evaluate, because to be honest I cant find a way to make this reliable. I have put 2 repeaters within 2 feet of this, and its not successful. I have even pulled the controller closer to almost line of sight, and it didnt help the signal .
Schlage has offered to replace the locks, but just evaluating everything. The entities are there/online and match between the working and non working locks. But these things are so temperamental. Its unfortunate there is not a more reliable/good option with zwave locks.
At this moment, throwing everything at the wall to see what helps. Suggestions always welcome, unfortunately batteries didnt change anything.
@JohnBeMe : Hope all is well. Got a new Schlage lock (they replaced it to have me diagnose/repair/what-have-you). If you were to try and ensure everything worked in an ideal way, how would you suggest handling?
I have read many approaches, but it seems one consistent one is to pair directly next to the hub, then move it to its final resting place. Thoughts?
Based on what info I provided, do you see any other opportunities to improve my connectivity to these locks?
Thanks!
That's ONLY if you have the old non ZP (ZWave Plus) Version of the BE469. It was REQUIRED to pair within 12" of the coordinator.
Normal operation this does not apply. For non-S0 'whisper mode' versions like the ZP this restriction does not apply
Interestingly, I just paired a new one, and it is maybe 3ft from the front door. It paired, and I was able to send lock codes that work, immediately, through ZwaveJS.
I compared my entry for Front door and now the new "Courtyard gate", and found them to be a bit different. Same firmware, but Front Door shows differently..
Security for Front door: S0 Legacy
Security for new Lock: S2_AccessControl
Same firmware, same entries, but is it possible the security is a factor in the behavior?
I am also finding this still has a very poor rating, but it seemingly works... Any thoughts? I find that all locks get 10/10 pings acknowledged, little failures. The old lock has higher latency for who knows what reason... All locks I have new and old, get an occasional "Dropping message with invalid payload" and they all have 1000ms+ latency, which is bizarre to me.
Old Lock:
New lock:
I'm having this same issue with 3 x BE469ZPs that I bought to replace older BE469s. All 3 report poor signals and refuse to choose better paths when doing network rebuilds. I've tried removing and re-adding one, and even when the lock was 2 feet away from the z-wave stick which is on a 6 foot extension, the signal was still poor. My larger problem is I'm getting duplicate notifications for lock and unlock events which could be an s2 bug but also may be related to poor signal. I reached out to schlage and they pointed out that home assistant isn't supported and referred me to their supported partners like Smartthings and wink, which is very frustrating and not helpful. I may try to re-pair one with S0 or no security and see if the lock behaves better or not.
Just a head's up, locks won't work with no security. S0 minimum requirement.
