There’s a new beta on the horizon that should help with the issues too.
If you want to give it a whirl:
2 Likes
Thanks for sharing this. Keymaster works great with my BE468ZP for a couple of days, then it will start getting stuck in adding / deleting. If I restart HA everything works again for a bit, but that’s less than ideal.
It is not necessarily a Keymaster issue, but Keymaster can handle it better. If your situation is so bad, I would recommend putting a repeater close to the lock. A repeater can be a zwave outlet or an actual zwave extender/repeater. That will make communication better.
There’s a repeater within 10 feet of the lock, and the base station is maybe 20 feet away. When it happens I’m able to lock / unlock the lock just fine, but setting codes via Keymaster doesn’t work.
Restarting HA does consistently resolve the issue, at least.
Just wanted to follow up - this appears to have been related to the Z-wave integration having issues with routing when I was moving a lot of things around. Now that my network is set up and I’m not adding/removing nodes all the time I haven’t had any problems.
I just installed key master today and before I started adding any codes I deleted all codes directly from the lock. I’m able to add codes to slot one two and eight but not three four five six and seven. I have noticed that on slot 4 the time is before I even installed KeyMaster. I’m wondering if this is a time issue on the slots. The other slots that actually worked have the correct time
I’m pretty new to all this but how do you go into your Z-Wave JS control panel?
I also missed this step. Once set… All good
1 Like
1st lock added just fine, the 2nd lock has errored during adding 5 times now?
I’ve tried setting up as standalone and as a child to the properly working 1st lock
Log details (ERROR)
Logger: homeassistant.config_entries
Source: config_entries.py:637
First occurred: 1:59:48 PM (1 occurrences)
Last logged: 1:59:48 PM
Error setting up entry Mudroom Door for keymaster
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/config_entries.py", line 637, in __async_setup_with_context
result = await component.async_setup_entry(hass, self)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/config/custom_components/keymaster/__init__.py", line 264, in async_setup_entry
await hass.services.async_call(
DOMAIN, SERVICE_GENERATE_PACKAGE, servicedata, blocking=True
)
File "/usr/src/homeassistant/homeassistant/core.py", line 2794, in async_call
response_data = await coro
^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/core.py", line 2844, in _execute_service
return await self._hass.async_add_executor_job(target, service_call)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.13/concurrent/futures/thread.py", line 59, in run
result = self.fn(*self.args, **self.kwargs)
File "/config/custom_components/keymaster/__init__.py", line 243, in _generate_package
generate_package_files(hass, name)
~~~~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^
File "/config/custom_components/keymaster/services.py", line 158, in generate_package_files
raise ValueError(f"Couldn't find existing lock entry for {name}")
ValueError: Couldn't find existing lock entry for mudroom_door
Would appreciate help with the initial setup as I’ve spend 2 hrs working on this and its been only error city.
Even a technical guy like me the info is not providing the needed details for a new HA person (also me) to do this.
Need help on the following please…
-
I figured out that " create an input boolean named
input_boolean.allow_automation_execution" is a Toggle Helper -
I created the dashboard using the code provided and it just shows boxes with errors in it. Spooks also says this is a problem. Because the rest isnt working I’m assuming?
-
does “Add to your binary_sensors” mean CONFIGURATION.YAML?
-
does “Add to your scripts” mean SCRIPTS.YAML?
I added it and Spook sees this as a problem…
-
does “Add to your automations” mean AUTOMATIONS.YAML?
HA will not restart throwing a critical config error in HA Core log error (below). It says the issue is in Dwains, but I assume that is becase Dwains is trying to auto-gen the info into the Dwain’s dashboard?
– When I remove that YAML, I get no errors for Dwains at all .
This error originated from a custom integration.
Logger: custom_components.dwains_dashboard.process_yaml
Source: custom_components/dwains_dashboard/process_yaml.py:48
integration: Dwains Dashboard (documentation, issues)
First occurred: 2:31:08 PM (1 occurrences)
Last logged: 2:31:08 PM
while scanning for the next token found character '\t' that cannot start any token in "/config/automations.yaml", line 33, column 37
this line is event_type: zwave.network_stop
First, thank you for KeyMaster. It has been working flawlessly since installed.
Device no longer allows locking in HA.
I get the error:
Subscribed to Z-Wave JS log messages…
2025-03-12T01:15:43.384Z CNTRLR « [Node 004] received S2 nonce without an active transaction, not sure what to d
o with it
It is a Kwikset HC620.
I can unlock the door through HA. I can update the PINs through HA. I can manually lock the door. Battery at 100%. Door sensor indicates “Closed”.
I cannot lock the door through HA.
Any suggestions to debug?
Try pulling the battery pack from the lock and waiting 30 seconds and then reseating the pack. My HC620 sometimes does something similar and this is the only thing I’ve found will clear out whatever weird state it’s in and get it operating properly again.
1 Like
Well, I will be a monkey’s uncle! That worked! Thank you!
If you do that, then any updates you may make to the configuration will not properly rebuild / reload the automations.
I thought that might be the case. HA should build-in a flag for the script/integration to tell it that for a given set of code, it should never be migrated, and thus, not show the message to the end-user. That message can only cause problems.
There’s a beta version of the integration that does away with all of the automations and moves the logic into the integration itself. So when that finally comes out it will take care of the problem for you 
I suspect they may be waiting on me to get my integration that depends on Keymaster updated to support the all the changes as it changes a lot of the entities around. Keeps all the same operations though 
2 Likes
good news… no rush, just have it done by the end of this weekend. 
HAH! it’s been in a fairly ready to go state since November / December. I’m the slow one here with life interfering with my work.
@tykeal any idea on this… after I enabled the notifications in the Keymaster UI I get this error (I did not migrate the automations - I just checked, they still ask to migrate)
keymaster_front_door Lock Notifications uses an unknown actionError ⸱ Reported by Automation
The automation “keymaster_front_door Lock Notifications” (automation.keymaster_front_door_lock_notifications) has an unknown action: script.keymaster_front_door_manual_notify.
This error prevents the automation from running correctly. Maybe this action is no longer available, or perhaps a typo caused it.
To fix this error, [edit the automation](/config/automation/edit/keymaster_front_door Lock Notifications) and remove this action.
Select Submit below to confirm you have fixed this automation.