--- title: "Lock Code Manager" description: "Lock Code Manager is a Marketplace integration for Home Assistant. It has 335 installs sharing analytics, works locally and was last updated October 27, 2026." canonical: "https://vulpo.app/integrations/marketplace/raman325-lock-code-manager" url: "https://vulpo.app/integrations/marketplace/raman325-lock-code-manager.md" last-updated: "2026-10-27" version: "1.4" --- # Lock Code Manager > Lock Code Manager is a Marketplace integration for Home Assistant. It has 335 installs sharing analytics, works locally and was last updated October 27, 2026. Lock Code Manager is a Home Assistant integration that manages PIN codes for locks already set up in Home Assistant. Each person gets a name and a PIN, and the integration finds a free slot on each lock and keeps the code in sync, reading every write back from the lock to confirm it. It leaves codes it did not create alone, and new users are placed only in free slots. A condition entity such as a calendar, schedule, switch or binary sensor can control when a code is active. It adds binary sensors, events, sensors, switches and text entities, plus actions to add, enable, disable and delete users, set or clear credentials, generate safe random PINs and refresh codes from a lock. It works locally and is set up in the UI. Automatic summary of the README and code of raman325/lock\_code\_manager. Something wrong, or are you the maintainer and want your own text here? [Get in touch](https://vulpo.app/contact) [Open in My Home Assistant](https://my.home-assistant.io/redirect/hacs_repository/?owner=raman325&repository=lock_code_manager&category=integration) On Home Assistant 2026.11 or newer? [Open it in the Marketplace](https://my.home-assistant.io/redirect/marketplace_repository/?owner=raman325&repository=lock_code_manager&category=integration) ## Supports - **Works locally**: Talks to your devices on your own network. No vendor cloud in between. - **From the Marketplace**: Installed through the Marketplace, formerly HACS. - **Actively maintained**: Its author released or pushed a change in the last six months. ## Setting it up Install it from the Marketplace and restart Home Assistant, then add it under Settings, Devices and services. ### Lock Code Manager - **Locks** - **Name** ### Code slot - **Condition Entity** - **Enabled** - **Name** - **PIN Code** ### How Many Users? - **Number of users** ### Configure users - **Users YAML** ### Sign in again - **Locks** ### After setup - **Locks** Texts from the code of [raman325/lock\_code\_manager](https://github.com/raman325/lock_code_manager). ## Entities - **Binary sensors**: Active, In sync, PIN in sync - **Events**: Credential used - **Sensors**: PIN - **Switches**: Enabled - **Texts**: Name, PIN ## Actions - **Add user**: Add one or more people to a Lock Code Manager config entry. Slot numbers are chosen by reading the entry's locks for free ones, so nothing already programmed is overwritten. All or nothing: if any person cannot be added, none are. Fields: Config entry, Config entry title, Users - **Clear condition**: Detach a person's condition entity, so their credential always applies. Does not disable them. Replaces Clear slot condition, which named a slot number rather than the person. Fields: Config entry, Config entry title, Name - **Clear credential**: Remove one of a person's credentials from a Lock Code Manager config entry and from every lock in it. This also disables the person, the same as emptying their PIN on the dashboard does. Fields: Config entry, Config entry title, Name, Credential type - **Delete user**: Remove one or more people from a Lock Code Manager config entry, clearing their credentials from its locks by default. All or nothing: if any name is not found, none are removed. Fields: Config entry, Config entry title, Name, Clear credentials - **Deobfuscate log**: Replace mask\_pin tokens (pin\#xxxxxxxx) in pasted log text with the plaintext PINs configured in any loaded Lock Code Manager entry. WARNING: the response contains plaintext PINs — do not paste it into public issues, forums, or any shared channel. Fields: Text - **Disable user**: Turn a person off and clear their credential from the entry's locks. Their credential stays in the configuration, so enabling them again restores it. Fields: Config entry, Config entry title, Name - **Enable user**: Turn a person on, so their credential is written to the entry's locks. Refused if they hold no credential — there would be nothing to write. Fields: Config entry, Config entry title, Name - **Generate PIN**: Generate a random PIN that avoids known unsafe patterns (all-same digits, sequential digits, repeating sub-sequences, and common weak PINs). Given a config entry, the PIN is also one no user on that entry's locks already has, so it can be set without being refused. Returns the PIN via response\_variable. Fields: Config entry, Config entry title, Length - **Hard refresh usercodes**: If Lock Code Manager supports the lock's integration, and the lock's integration supports it, this will query the lock for all usercodes. This is potentially useful for integrations that cache data from the lock and a usercode(s) is configured outside of Home Assistant. Fields: Forget that the lock can report codes - **Set condition**: Attach a condition entity to a person. Their credential works while the condition is on. Replaces Set slot condition, which named a slot number rather than the person. Fields: Config entry, Config entry title, Name, Condition entity - **Set credential**: Set one of a person's credentials in a Lock Code Manager config entry. The credential is stored in the configuration and synced to every lock in the entry, so it is managed rather than treated as an unknown code somebody programmed. Fields: Config entry, Config entry title, Name, Credential type, Value, Enable if disabled - **Use credential**: Report that a credential was used, for the keypads and door controllers Lock Code Manager cannot watch itself. The response says whether the code would work, for which user, and the reason when it would not. A valid code fires the Lock Code Manager credential used event; an invalid one fires nothing, so react to a rejection from the response. It touches no lock and changes nothing. It performs no rate limiting and no logging, and the reason tells a real credential that is merely inactive apart from one that is unknown, so do not expose it to untrusted input. Fields: Config entry, Config entry title, Code, Source, Target ## Troubleshooting - **Diagnostics**: Downloads a diagnostics file to attach to a bug report. - **Repair notices**: Notices it can show in Settings, Repairs: Number of Uses has been removed ## From the README > Lock Code Manager scales down to a simple UI for managing your lock's PIN codes — and scales up to a programmable, multi-lock, multi-provider PIN platform with scheduled access, condition-driven activation, and automation-ready services. Define your codes once and LCM handles setting, clearing, and monitoring them on every lock, across providers (Z-Wave, ZHA, Matter, and more) without you wiring up the differences. > > Whether you just want a clean dashboard for your front door or you're rotating PINs across an Airbnb fleet on a nightly schedule, LCM has you covered. From the README of [raman325/lock\_code\_manager](https://github.com/raman325/lock_code_manager#readme), [MIT License](https://spdx.org/licenses/MIT.html). Shortened. ## At a glance - Kind: Marketplace integration - Category: [Security and safety](https://vulpo.app/integrations/category/security-and-safety.md), Locks and access - Number: 335 installs sharing analytics; 112 GitHub stars - Connection: Works locally - Upkeep: Updated in the last 6 months - Needs: Needs the Marketplace (HACS on 2026.10 and older) - Latest version: 8.0.0, last updated October 27, 2026 - Domain: `lock_code_manager` - Source: - Issues: In Vulpo: Quick Toggle card, Chart card, Apple Watch, Control Center Independent directory, made by the developer of Vulpo. Not affiliated with Home Assistant or the Open Home Foundation. [About these numbers](https://vulpo.app/integrations/about) Last updated 2026-10-27. Source: https://vulpo.app/integrations/marketplace/raman325-lock-code-manager --- - HTML version of this page: https://vulpo.app/integrations/marketplace/raman325-lock-code-manager - Site index for agents: https://vulpo.app/llms.txt - Everything in one document: https://vulpo.app/llms-full.txt - All pages: https://vulpo.app/sitemap.xml