Thanks very much!
Tried it now on slots I know are not populated but get “time out” error when applying the code.
I took a look in MQTT (se picture) and I am wondering if the correct clusters for changing pin is even exposed? If that is the case its not working?
Yep it does
To be transparent. I have before tried to change pin here, but then I also got the timeout error. So its a little bit puzzling that when trying to change pin, its not working, either with from your integration, or in MQTT itself.
Extra puzzling because when switching lock on and off it works instantly. And some zigbees devices are like within 1m so clearly not a distance problem either.
Any tips on how to solve this is appreciated 
Yeah, these are tricky! I’m not sure how much I’ll be able to help you here. I built Lockly by imitating the MQTT messages that Z2M sends to the locks, so we need to get Z2M working first, then once we understand the correct protocol, I can expand Lockly to support it.
I had similar issues to you and resolved them by spending a couple of hours with ChatGPT running down various rabbit holes and letting it try to diagnose my system. I suggest that you tell it the exact model of your lock and let it scour the web for solutions for you. Once you have that working, if Lockly doesn’t work out-of-the-box then let’s talk about what’s missing and I can get it into the integration for you.
Sorry I can’t be more helpful!
Thanks for the pointer! Will do that and see if I come up with anything useful! (:
Hi Bharat,
Sorry for the stupidly slow reply, been OS and just got it all sorted! For some reason the Lockly card wasn’t showing, I’ve update everything after an MQTT meltdown and it’s all working! Great addition, thanks for your work!!
Cheers
Mike from Aus!
Does this work with Kwikset 916 when master code is being used?
Also, all of my existing codes were manually configured on the lock. Will this see my existing codes and import them or will I have to reconfigure them all?
Fantastic news! Psyched to hear it!
I don’t know! I haven’t tried it with anything other than the locks I have, which are Yale Assure’s. Let us know what you discover!
If your Kwikset’s are like the Yale’s then you’ll have to reconfigure them because you’re not able to get the PINs off of the locks. Which sounds like a reasonably security decision in my opinion.
Hi bharat,
I was able to install Lockly via HACs. However, when I add the “Lockly” lovelace card and try to “Add slot”, I don’t see any fields for adding the “Name” or the “pin code” (see image attached).
Any ideas what I might be missing there?
Thanks,
Brad
I found that amazon now has a great price for the Zigbee modeule for my yale assure locks, and moved them all off Zwave to Zigbee - no more Zwave nonsense, and poor security, and proximity required for pairing!
I have lockly installed, and the locks are all visible in zigbee2mqtt. But I am having a hard time to generate a view from lockly that shows the state of the locks and the ability lock and open the doors. Do I need to do something for lockly to discover the locks and update the lockly card appropriately?
Thanks!
Hey there! Can you let me know what version of Lockly you have installed? And which version of Home Assistant? They made some changes to the UI components a while back which triggered this type of behavior… but I thought it was resolved.
It’s working for me with:
Hey @fresnoboy! Do the locks show up in your MQTT integration in HA? If they show up there, then they should also show up in the dropdown in the Lockly card config. Here are a couple of screenshots- first from my MQTT integration showing the front door lock, then from the Lockly card config where you can see it showing up in the dropdown. lmk what you see!
Hi Bharat Mediratta,
Apologies for the delay in coming back to you. I am running the following versions:
@bharat Thanks, I thought there was a special card for lock status, but it’s just a normal entity. 
These zigbee modules work SO MUCH BETTER than the Zwave modules. They pair with normal zigbee security, and you don’t need to be close to the lock for pairing. We had 4 Andersen Patio doors with Yale Assure locks in them, and things just work so much better.
I have a couple of wall switches I need to replace (Hard to find zigbee dimmers in decora form factor), and then I can retire Zwave completely!
The big trick was finding a source for the zigbee modules for the locks at a decent price. I found them for $67/each at Amazon.com: Yale Zigbee Smart Module Smart Module / Zigbee / N/A : Tools & Home Improvement and they work great. Now to ebay my old Zwave modules!
Thanks very much for the integration. Zigbee (under Z2M at least) is just such a better way to control the locks.
@bhaha - this is a bug! I’ve filed it here: Edit Slot dialog shows no Name/PIN fields on HA 2026.9: card assumes ha-input is already registered · Issue #177 · bharat/homeassistant-lockly · GitHub
It loos like a new issue with 2026.9 and I’ll get a new version of Lockly out with the fix asap. Meanwhile, as a workaround try opening the card’s edit dialog once (three dots, Edit) should register the element for that page load, after which Edit Slot will show the fields until the next full reload and lmk if that works.
@bhaha - I pushed a fix but haven’t cut a release yet. Can you test it out for me?
update.install.update.lockly_update).4208b03a5ec2767d5922c0c082dbb8a3bc6912b2 (or just main).After that the Edit Slot dialog should show the fields again. Let me know either way and I’ll get a proper release out.
@bhaha quick update: the fix is now in a proper release, v2026.10.13. If you
didn’t try the commit install, just update Lockly through HACS, restart Home
Assistant, and hard refresh the browser. The Edit Slot dialog should show the
Name and PIN fields again. I’ve verified it on 2026.10.1 here. Let me know
either way.