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.