Akuvox integration

Akuvox Integration

Lock Code Manager supports Akuvox smart locks and intercoms via the Local Akuvox integration.

How It Works

Akuvox devices manage users with PINs. Lock Code Manager tags each user with lcm:<slot>: in the name to track which users it manages. For example, a user named "Guest" on slot 3 becomes lcm:3:Guest.

Format change in 4.0.0: Earlier versions used the [LCM:<slot>] <name> tag format. LCM still recognizes the old format on read, and rewrites each user to the new canonical lcm:<slot>:<name> form on the next write that touches it (set PIN, name change, etc.). Users LCM doesn't touch after upgrading stay in the old format and continue to work; the format converges as normal LCM activity rotates each user.

Unlike most other providers, Akuvox PINs are readable — LCM can read back the actual PIN value from the device, not just whether a slot is occupied.

Requirements

• The Local Akuvox custom integration configured in Home Assistant
• An Akuvox smart lock or intercom with PIN code support

Supported Operations

Operation	Supported	Notes
Set PIN	✅	Via local_akuvox.modify_user service
Clear PIN	✅	Via local_akuvox.delete_user service
Read PIN	✅	PINs are readable from the device
Push updates	❌	Polling every 2 minutes
Code slot events	❌	Webhook events not yet wired up

Limitations

• No push updates: Changes made at the device are not detected until the next poll (every 2 minutes).
• Local users only: LCM only manages local users (source_type=1), not cloud-provisioned users.
• Polling-based: All state is refreshed via polling the device API.

Troubleshooting

Users not detected

Ensure the Local Akuvox integration is loaded and the lock entity appears in Home Assistant. LCM only manages local users — cloud-provisioned users are ignored.

User tagging failed

If LCM cannot tag a user during setup, it will log a warning and skip that user. The user can be manually tagged by renaming it with the lcm:<slot>: prefix via the Akuvox app or integration. (The legacy [LCM:<slot>] <name> format is also recognized for back-compat, but new manual tags should use the canonical form.)