When I got the Kwikset 916 deadbolt lock I couldn’t get it connected to ZHA and the bolt would open but would not close from the lock’s keypad. After much fruitless searching, I called Kwikset/Wiser support. Installing a new set of AA batteries solved BOTH problems. The still shrink-wrapped Duracell batteries that came in the box were bad.
With the new batteries ZHA found the door lock in seconds and added it as a device under the ZHA integration.
I see that there are a few posts talking about Zigbee2mqtt instead of ZHA. Is this needed to get additional features like programmatically adding new unlock codes or determining which code was used to unlock the door?
UPDATE 3/5/24 - I found the ZHA Toolkit to extend ZHA functionality, and a script blueprint for adding temporary access codes.
Reviving an older thread here but I recently replaced my failing 916 ZWAVEs with the 916 Zigbee. I use Z2M as well and was able to get them in there and allow me to program the PIN codes. Before I was using KeyMaster with the ZWAVE version and sadly nothing like that exists today I was going to explore creating a simple card to allow PIN setting and reviewing. I was able to use automation though with the MQTT stuff to determine WHO unlocked or WHAT unlocked the door once I flipped the setting in Z2M to allow the pin used to be exposed.
I am reviving an old thread due to finding an edit from Mar 24. I have just installed one of these units, and unable to properly get lock status via ZHA as it outputs LockState.Not_fully_locked instead of LockState.Locked.
fresh batteries - even if the lock says they are okay.
confirm that the bolt can can physically extend and withdraw fully and smoothly.
call the Kwikset support line. I got a knowledgeable human with almost no hold time.
You can install the ZHA Toolkit to get full Zigbee data from the lock. The results are rather arcane - but it does work. I figured out how to turn the beep on and off from a script that way.
