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 connectivity or protocol configuration issue. Check:

The lock works from Home Assistant's native lock.* entity.
binary_sensor.<lock>_network in Keymaster is on.
Z-Wave JS: Check Z-Wave JS logs for command failures/timeouts, and ensure the node is fully interviewed.
Zigbee2MQTT: Ensure expose_pin: true is configured in Zigbee2MQTT for the device, and check the MQTT broker logs.
ZHA: Check for ZHA network/routing issues, or ZHA service call failures in Home Assistant logs. Note: Many Zigbee locks do not support reading PIN codes back from the lock over ZHA (the get_pin_code command fails). If this occurs, Keymaster uses a local cache, which is normal behavior and will not prevent codes from being written.

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

Notification settings reset on restart

Keymaster persists lock and door notification settings across Home Assistant restarts. If your notification switches or preferences reset after a restart, ensure that:

Home Assistant is shutting down cleanly to allow state to write to disk.
There are no registry/coordinator load/save errors in your Home Assistant core logs.

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 its respective provider integration (Z-Wave JS, ZHA, Zigbee2MQTT, etc.).

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: