Security & safety

Lock Code Manager

raman325/lock_code_manager · v7.0.2

HACSLocal polling

Lock code manager for locks integrated with Home Assistant

In Apple Home through HomeKit Bridge

What HomeKit Bridge makes of each kind of entity this integration creates, read from its source code. A device only gets the ones that apply to it.

Entity	Shows up as	Note
`switch`	Switch or outlet
`binary_sensor`	Sensor (motion, contact, leak, smoke…)
`sensor`	Sensor (temperature, humidity, air quality…)

1 report below say how a device from this integration behaves in the Home app.

What people report

Manages PIN slots on Zigbee, Z-Wave and Matter locks; write-only Zigbee locks now handled. Apple Home PIN users on Matter locks are not reported.

Works1
Partly works2

Device	In Home Assistant	In Apple Home	What they said	Source
Papaiz PSL200 Zigbee lock	Works Local		Write-only lock handled via optimistic slot management; fixed after request Saved copy Problem Description Some Zigbee locks support writing PIN codes to slots but do not support reading the existing PIN codes or slot status. I am trying to use Lock Code Manager (LCM) with a Papaiz PSL200 lock integrated into Home Assistant through Zigbee2MQTT. The lock appears to share the same hardware/firmware base as some Yale/Assa Abloy models, such as the YMC420 and SOLIS01, but the PSL200 does not respond to `getPinCode` or `getUserStatus`. In practice, it is write-only from the Zigbee interface. This makes the current LCM setup and synchronization model unsuitable for this type of lock. … Excerpt saved from GitHub on 2026-10-23.	Issue #1581 · 2026-09
Matter lock U400 shared from Apple Home	Partly works Local	Partly in Home Apple Home PINs and Home Key users are not reported to HA	LCM ignores unlocks by Apple Home PIN and Home Key users; belongs in core Matter Saved copy My U400 is shared from Apple Home, so the residents are Apple Home users, not LCM users. When one of them unlocks, the lock says who it was, but LCM drops the event and HA has nothing to go on. HA's Matter lock only keeps `operationSource` in `changed_by`. Two unlocks from the Matter Server log (fw 3.1.1.0, LCM on #1745): Keypad, PIN set in Apple Home: [code] Home Key: [code] LCM reads every user for both and then fires nothing. I know Aliro isn't reported from any lock yet. Would you consider firing `credential_used` (or a separate event) for these too, with the lock's `userIndex` and the … Excerpt saved from GitHub on 2026-10-23.	Issue #1754 · 2026-10
Yale YMC420 / SOLIS01 Zigbee locks	Partly works Local		Share hardware base with PSL200; write-only slot behaviour Saved copy Problem Description Some Zigbee locks support writing PIN codes to slots but do not support reading the existing PIN codes or slot status. I am trying to use Lock Code Manager (LCM) with a Papaiz PSL200 lock integrated into Home Assistant through Zigbee2MQTT. The lock appears to share the same hardware/firmware base as some Yale/Assa Abloy models, such as the YMC420 and SOLIS01, but the PSL200 does not respond to `getPinCode` or `getUserStatus`. In practice, it is write-only from the Zigbee interface. This makes the current LCM setup and synchronization model unsuitable for this type of lock. … Excerpt saved from GitHub on 2026-10-23.	Issue #1581 · 2026-09

Gathered from GitHub issues, pull requests, discussions and docs, and from r/homeassistant. These are individual reports, so check the linked thread and the date before you buy.

How it connects

Local polling

Talks to the device on your network, asking it for updates every so often.

Details

Installs (analytics)	334 (0.05%)
GitHub stars	110
Latest version	7.0.2 (2026-10-20)
Set up in the UI	Yes
Maintainers	@raman325
License	MIT

In ReReHome

Whatever HomeKit Bridge shares reaches Apple Home as normal HomeKit accessories behind your Home Assistant bridge, so ReReHome shows and controls them like any other.

Bridges get their own settings page listing the accessories behind them.

Sources

Documentation: https://github.com/raman325/lock_code_manager
Source code: https://github.com/raman325/lock_code_manager
Issues: https://github.com/raman325/lock_code_manager/issues
HACS: https://hacs.xyz