try moving the title back to line up with strategy. I was having this same issue.not too long ago. I looked at my code and that is what I did. you can also add a theme using theme: lined up with strategy.
perfect! thanks
FYI folks, the release of v0.2.x (now at v0.2.1) saw us merge the beta branch into the mainline. If you haven’t moved up for some reason, I highly recommend it. We saw several issues get fixed and there is now a dynamically created dashboard option that is great so you don’t have to go messing around with copy-pasta anymore. Give @raman325 a round of applause for that!
We’re also now in a position to accept new “providers” for lock management types. ZWave, which everyone here knows is there, but we also now support Akuvox intercoms and with the release of HA 2026.4 we should also see Schlage WiFi locks being supported as that release should have the needed actions to be able to manage codes.
Finally got KeyMaster installed, still not sure it’s working like it’s supposed to.
First issue: "Last Used doesn’t seem to be updating. I put a code into the slot, verified it physically worked on the lock, yet last used never updates.
Second issue: Not sure if this is really an issue, I noticed the majority of the 500 entities KeyMaster created show as Unavailable. I’m assuming they are like this way until they are actually utilized?
What type of lock do you have? Last used should be working correctly for most ZWave locks and for Akuvox intercoms. If Keymaster is emitting an event on the code being used, it should update. If you’re using a Schlage WiFi lock it won’t work as the the underlying Schlage integration doesn’t know how to get usage events from the lock.
As for all of the Unavailable entities, you’re correct that they are in that state unless activated. If you don’t need all of the advanced features enabled (date range or custom day of week) then I recommend disabling the features entirely.
Locks are Schlage BE469 (Zwave 300 series)
@JohnBeMe Can you setup notifications for the slot you’re trying this on and see if you get those? As long as those are working then the last used sensor should work as the code path is similar.
The auto lock feature is triggering when the door is open, even though I have a sensor configured and showing its state correctly in the KeyMaster UI.
I’ve been using KeyMaster for several years, I’m sure in the past this was working as I would expect (ie, not locking when the door is ajar).
Is there any configuration of this feature? Should it be taking into account the door sensor state?
You need to have the retry option turned on as well with the current logic of the integration to keep it from doing that when the door sensor is open.
great, thx.
Hi Andrew,
I’m not sure what you’re asking? As shown in my original post, notifications have been enabled since day 1. Tell me what I should set up as an experiment and I’ll gladly try it out.
Thanks!
Are you actually getting notifications from the slots? The reason I asked that is that the code path used for updating the last used sensor is inline / parallel with with the notifications code path.
If code use notifications for a slot are working then the last used sensor should be working
Again, I have to ask, getting notifications where/how? Should they pop up on screen? In the Activity log? What type of actions should send a notification?
Please indicate what I should do (ie, unlock the door, change a setting, etc) what should be the expected action/result?
Ok… here’s the wiki about setting up notifications. Enabling notifications on the lock or slot is only part of setting up notifications. You also have to setup a script that will handle the actual logic of giving you the notification.
As for what causes notifications to happen. At the slot level, the code being used. At the lock level, lock / unlock (manual, by code, or RF) as well as jammed status all cause notifications.
I see it turned on at the slot, but if you are not getting any notifications after setting up a notification script then, again, the last used sensor will not work. If you do get notifications and the sensor is not updating, that’s a bug that would need to be figured out and we would need an issue raised about it.
Thanks for the the further direction, it helped clarify things for me.
I did the following as per the wiki:
Setup the script for Keymaster to use for notifications:
action: persistent_notification.create
metadata: {}
data:
title: "{{ title }}"
message: "{{ message }}"
Now whenever I lock or unlock the door I get a persistent notification to the HA web page.
The only time there was an actual status sent is when the door was closed and the sperate door sensor I indicated in KeyMaster detected it.
And as you can see, the Last Used status still does not update.
Let me if I can check for anything else, thanks!
That would be strange since HA registers when the door is locked and unlocked. Schlage BE469 locks are one of the oldest and most common Zwave locks out there.
Standing by to do any additional testing 
Hello everyone.
I have 3 BE469ZP locks, and when I use keymaster, I found 1 of the 3 generates its lovelace dashboard well with the strategy implementation, but 2 of the 3 partially generate but in a fairly/completely broken manner. In logs I find: Can't find the lock in the Entity Registry. But interestingly, they are healthy in zwave, I can ping them, the entities are enabled, etc.
Is there a process I can follow to try and diagnose? I've deleted and regenerated the dashboard multiple times with no success and compared all the equivalent entities exist/are healthy between the 1 working lock, and the 2 that are not. Same zwave firmware, etc. I just cant figure this out at the moment.
Thank you!
Update: I just went in and ripped the devices out of the integration, reconfigured, and now its a talking/living/breathing dashboard!
Other than @tykeal (thank you for your help so far!) there doesn’t seem to be any activity from the core developers? Looks like the github page doesn’t get any recent responses from them?
Is there a list of lock models where this integration is known to work?
@JohnBeMe I would suggest opening an issue on the repo.
As an alternative folks could also try Lock Code Manager if you don’t need to integrate with Rental Control