Troubleshooting

Missing Sensors

Alarm Level/User Code and Alarm Type/Access Control sensors are optional in Keymaster setup.

If your lock exposes them, selecting them can improve slot attribution details.
If your lock does not expose them, choose (none) for those fields and Keymaster will still function using lock events/state.

Code Slots

Keymaster refreshes lock/code state periodically and also performs quick refreshes during sync activity. It avoids aggressive wake-up polling loops to help reduce battery impact.

Unable to set codes

This is usually a lock connectivity issue (Z-Wave JS node unavailable/interview incomplete/network not ready yet). Check:

The lock works from Home Assistant's native lock.* entity
binary_sensor.<lock>_network in Keymaster is on
Z-Wave JS logs for command failures/timeouts

If it does not recover, enable debugging and open an issue.

Entity not available messages

Common causes:

Child lock slot is inheriting from parent and Override Parent is off
A conditional option is disabled (for example, day/time entities are hidden until day-of-week limits are enabled)
The lock is currently disconnected from Z-Wave JS

As of keymaster v0.1.0, the packages directory structure is no longer used and can be deleted.

Enable Debugging

This is useful for gathering diagnostics. Navigate to Developer Tools → Services in Home Assistant. Select the service logger.set_level in data enter custom_components.keymaster: debug and press Call Service. Your log will now start showing debug data in the Home Assistant log.

If you are missing logger.set_level, add this to configuration.yaml: