My Kwickset lock isn't reporting lock status, but I'm still able to control the lock/unlock manually on the device page and with rules. I'm using the Generic Z-Wave Lock driver. This seems to be a relatively new development. I've had this lock a long time. Platform version 2.3.9.199. Thoughts?
It's not reporting any lock or code states, including after clicking getCodes. (But lock & unlock still work.)
Likely was always this way, otherwise you'd see a "lock" attribute under "Current States" (even if the value is not accurate), but it is completely absent in your screenshot.
With a totally different brand of lock (so possibly not applicable to you, both because of that and the above), power cycling my lock sometimes helped when it stopped reporting lock status. Can't hurt to try that here just in case.
Otherwise, my suggestion would be seeing if "Configure" helps or if removing and re-adding the device helps (swap it out with a virtual one in the meantime if you're using it in any apps and want an easier time when you re-add it; I'd suggest a proper exclusion of the device unless you know what you're doing and are adept at removing dead Z-Wave nodes).
If you haven't done a general assessment of your Z-Wave network health, that would be good to look at as well. Is the near the hub or in range of beaming repeaters (a good idea even if it is)? Any possible problem devices on your network, like chatty power monitoring devices or lots of S0 devices? (The lock itself must be S0 or S2, so that's fine -- S0 isn't inherently bad but can be chattier than it needs to be if you don't actually need it.)
FWIW, I don't see anything in the debug logs you posted that suggest the device is actually sending anything to the hub that the driver just isn't parsing, so the issue is more likely on the device side.
Power cycling appears to have fixed it, so thanks! The locked status is reporting (including on the dashboard), maxCodes, and lockCodes, so yay.
I chased and removed ghosts with a z-wave stick earlier this summer. Everything still looks pretty good there.
I write the date on batteries when I install them now and they say November 2023. That's pretty crazy battery life for our main door. That will be my next fix...
I have this same lock with the 700 chipset. It does this every so often and it's just a power cycle. Grrrr.
The other 2 I have are gen 500; they don't do this.
I was hoping for better things with the 700 chip like going DIRECT and staying there but it never happens, always with the route changes.
Hi. I have the same problem on a Kwikset 912 lock. No recognition of the locked or unlocked status. I have to manually do a refresh. Hub habitat c7 and c8 pro 2.3.9.200. On the c8 hub, the status is ok but sharing to the c7 / mesh hub is not done. I'm not sure if it's since the last hub update.
Yes, by removing the batteries. There is a rule that locks this lock depending on the mode. I also changed the mesh refresh rate to 2 minutes for both hubs. There is one hub for devices and the other for rules. I will see if everything coordinates in the coming days. Thank you very mucch.
