I have a Kwikset HC620 zwave lock that continuously either shows unavailable or the incorrect state in my dashboard. I have found that if I hit refresh values within the zwjs interface that the device updates to reflect the correct bolt state. Screenshot below. I’m looking for help to see if I could write some sort of automation that runs every minute to perform this refresh function to keep my dashboard up to date as not knowing if an exterior lock is locked or not is a problem to say the least. Open to other ideas that might help resolve this as well.
Just a guess, but if “unlock” works fine but “lock” sends a “not fully locked” notification instead of locking, there might be a problem with the lock jamming or not fully engaging. If you’re convinced it is fully locked, check to see if there is a calibration procedure to correct this sensor/notification.
That said, sometimes re-interviewing a Z-wave device will improve laggy refresh. There is also a zwave_js.refresh_value service but in general is not recommended to call too often to avoid network congestion.
The bolt is certainly fully locked when I’ve checked as I did consider that as well. Occasionally I will get the same message upon unlock but not as frequently.
Kwikset wasn’t overly helpful when I opened a case with them. They simply sent me a new unit which behaves exactly like the first one I had. Further, I tend to see the device go unavailable in my dashboards when it is manually locked or unlocked, or it just doesn’t reflect the true state any longer until I refresh values.
I am using the default association. When you include a device into a network the association gets setup automatically. This is how the lock knows it should report updates to node 1 which is the controller.
Also the auto handling feature is how the lock knows if it’s jammed or not so I would try redoing that process with the door open and closed to see if it fixed the jammed issue.
Still run into the same reporting issue with the door open to validate if the bolt is in fact getting jammed or not. Not sure if there is any way to “tune” this at all?
The door handling process is what you would use to “tune” your lock. It’s in the documentation to perform door handling when you are switching doors or having problems. If that doesn’t work I would verify everything is installed correctly.
I’m sorry but in what documentation does this door handling process live?
Also, If by simply refreshing the zwave values, returns the lock to its correct state, would that not suggest that there might be something else in play here other than the lock bolt possibly encountering some resistance?
I found the Kwikset documentation and have now properly handled the lock, two times to be safe. Problem still persists as before.
Open to other suggestions as to how to further troubleshoot this issue. I’m leaning towards the work around to simply have an automation fire every so often to refresh those zwave values but have not been able to figure out exactly how to make that work either.
