We have a Kwikset Halo Select that works fine on WiFi. I now have it successfully converted to Matter over Thread and added to HA using OpenThread and Sonoff Zigbee 3.0 USB Dongle plus (flashed as ONLY Thread) as the BR on the HA. The questions is the only entities available are state (I can un/lock it via HA fine), Identify (the lock will audibly chirp fine), Firmware, Battery, and Battery Type. On the Lock entity in HA, I can enter a “Default Code”, but that does nothing on the actual lock touchpad. The touchpad is utterly useless on the lock at the moment. Even the lock icon won’t lock the door. Is this a limitation of Kwikset, the TBR, or HA and if TBR/HA would changing it to say a Google Home TBR open it up? I’m waiting to hear back from Kwikset so thought I’d ask here in hopes others have some ideas. I’m not dependent on Apple, Google, Amazon, SmartThings so would prefer to keep it all on HA. Really all I need in HA is un/lock functionality (and status) but kinda need the touchpad to also work ![]()
I’m having the exact same issue. Pressing the “lock” icon on the keypad seems to flash an error (red icon in top left), and the password I entered as the default code seems to do nothing.
I found that I could share the device with a HomeKit installation and use that to set access codes.
The lock now works as expected in HA and via the keypad!
Interesting. I reverted back to the Kwikset app and it’s the only thing not on HA at the moment. We’re an Apple free zone so no HomeKit here. The only border router I have is the HA so I guess I may need to look into a different one. Annoying Kwikset would add matter support but “haha j/k not really”
Did you ever hear back from Kwikset about this? I’m having the same problems with a Weiser-badged version of the same model.
Ouch! I just spent hours installing a new Kwikset Halo, since the hole through the door had to be larger than my previous two locks, a “dumb” deadbolt and a Schlage Z-Wave lock.
While selecting and purchasing a lock I read that the ability to generated guest codes was limited or missing. I did NOT expect that there would be no codes at all! We strongly prefer using the keypad to open the door. The “smart” features would be used mainly in automations or while traveling.
Is this really true?
I don’t use any other “ecosystem” than Home Assistant. My first dozen or so Matter-over-Thread devices are working nicely, except this one.
Setting codes works fine in other ecosystems I tested, Google Home and Apple Home, and lock is Matter certified… has to be a Home Assistant issue not Kwikset