Yeah, unfortunately that’s too old.
Ugh. LOL with well over a hundred devices - I’m NOT replacing it!! 
Well, it went unavailable again, I pinged it again, it fixed it, I then used “heal” for the node (not the network) and - it said successfully healed. I know (NOW!) not to trust the Zwave graph, but it DID change position in the graph for the first time, and isn’t directly connected to the HA PC - it’s one step down. I’m hoping that somehow, someway, it really IS healed and going to work!
I really DO appreciate everyone’s help and input! Thanks!
1 Like
try sending some codes to the lock with keymaster or something - if there’s a problem that’ll find it. 
It seems to be working, and has since I did that heal - I don’t want to mess with it again unless it dies again!
What would “Keymaster” give me that I don’t already have? I have three of these deadbolts in my house (Kitchen, Front, Garage) and all seem to work fine, and I’m able to include them in automations, etc.
I should ask - what stick (zwave and zigbee) is recommended currently? I may be moving later this year - taking ALL of my devices with me (ugh, every switch, every plug, ever bulb, etc etc) and it wouldn’t be a bad time after moving to change over if I’m taking a device out of a box one at a time anyway…
Code management
As Nathan said, Keymaster is for code management (plus more), and would not change how your underlaying z-wave network behaves. Maybe you could try search YouTube first and see how it works and what it takes to install / integrate such? You might find it interesting - it could open up new possibilities…?
Project page:
FutureTense/keymaster: Home Assistant integration for managing Z-Wave enabled locks (github.com)