After a few upgrades, I went to put in a new door code into keymaster and noticed all my codes are in the Adding State. I’m unable to add new ones and no longer getting notifications. What happen? How do I fix.
It is not Keymaster per say, but Zwave addon/adapter. Restart the Zwave addon or do a cold restart(reboot) of HA.
Tried. Rebooted HA serveral times. Here’s a screen shot of my codes. As you can see it states “ADDING” this code has been there for over a year now.
I also rolled back to a version I thought was working 2025.8.1. I haven’t added or deleted new codes in awhile or I would have found this earlier.
Any suggestions on how I should fix this. I have 2 HAs in 2 different locations, Both doing the same thing. I really need to get this fixed as I have new employees starting soon and they need a code to get in.
If you’re on HA 2025.8+ and you’re still using Keymaster 0.0.99 that’s your problem You have to move to the beta branch if you want it working on current versions of HA. See ISSUE: HA 2025.8.0 breaks keymaster · Issue #454 · FutureTense/keymaster · GitHub
The next question you’re probably asking is, if the beta branch is the only version working since with HA 2025.8+ why hasn’t it been released as stable, and that’s because there’s a bunch of little issues that are still not working quiet right for folks and the work to figure out how to make 0.0.99 continue working on newer HA hasn’t been a priority to the maintainers. So you’re in a bind of either continuing to run HA 2025.7.x and using a fully functional Keymaster 0.0.99, or switching to Keymaster 0.1.0-b5 and dealing with the few issues it currently has.
Those issues being:
- the upgrade to it not being very clean and that’s likely to not be fixable
- auto-lock having some issues
- number of use limits not working 100% correctly
Look over the current issues and see if any of them are major problems for you.
Ok yesterday I upgraded both of my HAs to 2025.10.2
So what am I needing to do for Keymaster to work on the latest version of HA?
Sorry for all the question, I’m really new at all this
In HACS you’re going to need find Keymaster and press the triple dot menu. Select Redownload and then expand the Need a different version? option and then in the releases select v0.1.0-b5.
After the install, restart HA. Wait until HA is fully up and then give it another restart just to be safe as the migration that the beta does isn’t always the cleanest and it might have issues.
The dashboard that you have for Keymaster will no longer be working correctly as most of the entities for Keymaster were renamed and moved as they are no longer being loaded in via packages/keymaster anymore. The newly created dashboards can be found under custom_components/keymaster/lovelace
@tykeal Thanks for the download info. I have successfully downloaded the new version of Keymaster to my first HA. Now as for as the Dashboard goes. You my current dashboard for Keymaster will no longer work. Ok the newly created dashboard is under custom_components/keymaster/lovelace. I see this but it’s been so long since I setup the dashboard for the Keymaster, I’m at a lost on this.
You’ll want to copy the contents of the generated dashboard file and past them at the bottom of a raw editing session of the dashboard you want it on.
For instance, whatever dashboard page you currently have your keymaster dashboard on, edit that and then select the triple dot menu and select Raw configuration editor. Scroll to the bottom of the edit dialog and then paste everything copied out of the generated dashboard file. Save and select done. Verify that the new view looks correct. You can then delete any old view you may have had to clean up.
Thanks again.
I copied the /homeassistant/custom_components/keymaster/lovelace.py page and pasted to bottom of my current Lock Dashboard, but it errors out
Not the custom_components/keymaster/lovelace.py file but custom_compoents/keymaster/lovelace/<lock>.yaml
Ok I found the file. I added it to the end of my current (old file)
/homeassistant/custom_components/keymaster/lovelace/garage_lock.yaml
Nothing shows on the screen below my old one.
So I created a new Dashboard and now it works. I deleted my old one. Now as for notifications… When an employee would use their code to unlock the door, I would get a notification from HA through Pushover. Will I have to change anything with that because I am not getting any notifications
You may need to make modifications. I personally use a custom even handler so I was unaffected since the events are still the same.
Thanks again for the help in getting my Keymaster back up and running. Are you also getting notifications when someone uses a code to unlock the lock? If so, how did you set yours up?
I’ve posted several times in theKeymaster Z-Wave Lock Manager thread helping folks with custom notification systems.
For my properties I use something similar to this for handling my static codes and my Guest Entry Notifier blueprint that I wrote for notification when a guest checks in at the property.
For my various properties using Keymaster and Rental Control:
alias: Lock Logging and notification
description: ""
triggers:
- event_type: keymaster_lock_state_changed
event_data:
state: unlocked
variables:
sn: |-
{%- if trigger.event.data.code_slot_name == "" -%}
Manual
{%- else -%}
{{ trigger.event.data.code_slot_name }}
{%- endif -%}
verb: |-
{%- if trigger.event.data.code_slot_name == "" -%}
unlock of
{%- else -%}
unlocked
{%- endif -%}
slot_num: "{{ trigger.event.data.code_slot_num }}"
trigger: event
conditions: []
actions:
- data:
name: "{{ trigger.event.data.lockname }}"
entity_id: "{{ trigger.event.data.entity_id }}"
message: "{{ sn }} {{ verb }} the {{ trigger.event.data.lockname }}"
action: logbook.log
- choose:
- conditions:
- condition: and
conditions:
- condition: template
value_template: "{{ slot_num > 0 }}"
- condition: or
conditions:
- condition: template
value_template: "{{ slot_num < 6 }}"
- condition: template
value_template: "{{ slot_num > 10 }}"
sequence:
- choose:
- conditions:
- condition: template
value_template: "{{ sn == 'Cleaner' }}"
sequence:
- data:
message: Cleaner door code entered
title: Cleaner entry
action: notify.zulip_admin
mode: single
For my home itself, I just do logging with:
alias: Lock Logging
description: ""
mode: single
triggers:
- event_type: keymaster_lock_state_changed
event_data:
state: unlocked
variables:
sn: |-
{%- if trigger.event.data.code_slot_name == "" -%}
Manual
{%- else -%}
{{ trigger.event.data.code_slot_name }}
{%- endif -%}
verb: |-
{%- if trigger.event.data.code_slot_name == "" -%}
unlock of
{%- else -%}
unlocked
{%- endif -%}
trigger: event
conditions: []
actions:
- data:
name: "{{ trigger.event.data.lockname }}"
entity_id: "{{ trigger.event.data.entity_id }}"
message: "{{ sn }} {{ verb }} the {{ trigger.event.data.lockname }}"
action: logbook.log
