Kwikset 914c lock not reporting manual lock change state
See original GitHub issueDescribe the bug
BE469ZP lock, when turning the lock manually the state of /boltStatus
changes.
914c Kwikset lock does NOT report manual lock changes
To Reproduce manual lock turn Device responds to zwave (and MQTT) commands
Device information Which device(s) is/are affected? 914c What are the node IDs? 104 & 107
Log is huge - i’ll work on grabbing a smaller chunk
Issue Analytics
- State:
- Created 3 years ago
- Comments:6 (6 by maintainers)
Top Results From Across the Web
914 SmartCode Traditional Electronic Deadbolt with Z-Wave ...
Press the Lock button while the door is open and unlocked. If the latch bolt does not extend to lock, then all codes...
Read more >Kwikset z-wave lock not reporting locked/unlocked status ...
It can miss status changes both for manual locking/unlocking or from a command in ST. The lock still responds consistently to lock/unlock ...
Read more >Secure Lock Not Updating Status? - Home Assistant Community
If I lock/unlock the door manually, I am not seeing any change in the status in the web UI. I do have the...
Read more >5 Top Selling SMART LOCKS Reviewed. Wyze ... - YouTube
In my tests these Z-Wave locks resulted in increased overall security due to smart features like Auto-Relock, and lock state detection.
Read more >Home Connect Lock Module, Rf Z-Wave Plus 500 Series Chip ...
Home Connect Lock Module, Rf Z-Wave Plus 500 Series Chip REV 3.8 for Kwikset Models 909, 910, 911, 912, 913, 914 (Z-Wave Plus)...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I’ve raised #1602 to investigate if this is a good idea to do automatically.
I see. I’m currently triggering on the notification event and changing the state manually, but I previously had it send the appropriate lock/unlock command to sync up the state. I did see a mention of refreshing a single value, and that would also be an option. Here’s the automation that I’m currently using, one for each lock:
It uses my custom python script to change the internal HA state, but the action could just as easily be the following:
It might be better to fix it at the source rather than delegating to the clients, but I can understand why you might want to avoid cluttering the codebase with special cases. Maybe if it was a general “do this when you get this notification”, it would be okay.