Hello, I have a Kwikset Z-Wave lock ( I believe the 916, but not 100% sure). My problem is the events log is not correct. Specifically, when the door is unlocked, the log always says "manually" even if I know for a fact it was unlocked via a keypad. I would like to be able to see which code (i.e. who) unlocked the lock, as Smart Things did. I did try to do my homework and searched for similar threads. All I could find were Z-Wave pairing issues, and the data for my pairing looks identical to those that said "This is what mine looks like, and mine works" So I have no reason to believe it's a paring issue. I can view all users, and the code correctly in the lock code manager app. Thanks in advance for any advise on what to do.
If you could open a live logging page, enable debug logging in the driver, then unlock manual, lock manual, then unlock with a code and post the logs i should be able to correct this.
You can pm me the logs thanks.
Thank you kindly for the offer. I'm on the road at this exact moment. When I return I wil do that and send you the results
I thought this was already identified and fixed in 2.0.5??? I know multiple people - including myself - have reported it to support. Side note, it worked fine pre-2.0.4.
I converted my last zwave Kwikset to zigbee yesterday, so doesn't matter to me any more. But thought I would mention that it seems to be related to the other code reporting issues in 2.0.4.
It's not. This worked fine in 2.0.3 and below. They introduced a bug in 2.0.4 that broke this for pretty much all z-wave locks.
Discussed here. The topic is about Schlage, but it applies to all z-wave locks in 2.0.4. I verified it on Yale and Kwikset, for instance. It's been going on for a month (annoyingly).
I can confirm that it’s working in the build I’m running that has extra Zigbee debugging so I bet it’ll be fixed in the next release.
1 Like
Support specifically told me it would be fixed in the "next build", so that makes sense. Thanks @srwhite.
Yes, it is fixed in 2.0.5 for locks we've tested with, I'm not sure we've used this driver with a 916, what the op is reporting appears different.
Gotcha.
Well, I can say what the OP reports match what I reported to support (including the logs I submitted) on my Kwikset 914 and 916 when they were zwave. And it did not do that pre-2.0.4.
@mike.maxwell Side note, there are only 2 zwave modules (one z-wave regular, and one z-wave plus) for all Kwikset models 910-916. So no need to test on every model.
If you fixed it for any of them, it should be fixed for all of them - which is great! Thanks!
1 Like
Thanks all for the history. I am new to the Hubitat platform, so I was not aware of this. I am sending the logs privately. However, for the record, I have the 914, not the 916.
FYI, the 2.05 FW update resolved the issue. Thanks to all who helped me with this,
2 Likes
This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.
