Schlage integration

Schlage Integration

Lock Code Manager supports Schlage WiFi locks (Encode, Encode Plus) via the Schlage integration.

How It Works

Schlage locks manage codes by name. Lock Code Manager tags each code with [LCM:<slot>] in the name to track which codes it manages. For example, a code named "Guest" on slot 3 becomes [LCM:3] Guest.

PINs are write-only — the Schlage cloud API returns masked codes (****). This means:

• LCM can set and clear PINs on the lock
• The lock reports whether a code slot is occupied, but not the actual PIN value
• The code sensor shows the configured PIN (from LCM config) rather than the on-lock value
• On Home Assistant restart, LCM re-sets all configured PINs to guarantee correctness

Requirements

• The Schlage integration configured in Home Assistant
• A Schlage WiFi lock (Encode, Encode Plus, or similar)

Supported Operations

Operation	Supported	Notes
Set PIN	✅	Via schlage.add_code service
Clear PIN	✅	Via schlage.delete_code service
Read PIN	❌	Schlage returns masked codes
Push updates	❌	Polling every 5 minutes
Code slot events	❌	Schlage does not report which code was used

Limitations

• PINs are write-only: LCM cannot verify the actual PIN on the lock.
• No push updates: Changes made via the Schlage app are not detected until the next poll (every 5 minutes).
• No duplicate PINs: Schlage locks reject setting the same PIN value on multiple codes. Each code must have a unique PIN.
• Cloud-dependent: All operations go through the Schlage cloud API.

Troubleshooting

Codes not appearing

Ensure the Schlage integration is loaded and the lock entity appears in Home Assistant. LCM detects Schlage locks by their entity domain.

"Duplicate code name" errors

LCM tags codes with [LCM:<slot>] prefixes. If you manually create a code with the same tagged name, LCM's set operation will fail. Remove the duplicate via the Schlage app.

"Duplicate PIN value" errors

Schlage does not allow the same PIN on multiple codes. Ensure each LCM slot has a unique PIN.