Make your 2N a real Crestron Home lock — with PIN users and a log of who came through
You can already open a 2N’s door from Crestron by pulsing a relay. But a pulsed relay isn’t a lock. It has no state you can trust, no users, no schedule, and no answer to the question every client eventually asks: who opened the door, and when?
The 2N Native Lock driver closes that gap. It drives the 2N’s strike through a switch output and reports live state back from the device, so the door appears in Crestron Home as a native lock — a standard lock tile with proper Locked/Unlocked state, events, PIN users and schedules. Not a relay dressed up as a lock. A lock.
A native lock, not a workaround
Because it’s built on the Crestron Home entity model, the door behaves like any other Crestron lock. It shows the real state on the tile — read from the 2N’s event log, not guessed — so if someone opens the door on the keypad, Crestron knows. Lock and unlock are exposed to scenes, schedules and quick actions the same way every native lock is.
Lock commands are always sent to the device, even when the tile already shows the target state, so a stale reading can never leave a door in the wrong state.
Who and when
This is the part clients remember. PIN users are managed in Crestron Home’s own lock settings, and when someone enters their code the driver reports “Unlocked from keypad,” attributed to the matching user. The commissioning app keeps a live access log — newest first, each entry tied to a person — which is exactly the who and when a plain lock tile never shows.
Schedules are enforced as a rolling validity window, which makes them fail-secure: if the processor goes offline, access expires rather than staying open. A caretaker’s 8-to-6 stays 8-to-6 even if the network drops.
[Screenshot to add: the commissioning app’s attributed access log]
An app that signs the job off
The driver includes an installer-facing commissioning app, served from the processor — no internet or extra software. On site it lets you:
- Test the strike — fire Test unlock and Test lock from your browser and watch the door physically release, without walking back and forth.
- Prove the connection — a troubleshooter runs a sequence of checks against the 2N (network, HTTP API, credentials, services, the strike switch) and tells you how to fix anything that fails.
- Validate a user before you leave — the emulator runs the driver’s real access rules for a chosen user, method and time, so you can confirm a new PIN or a schedule window without waiting for it.
It plays well with the intercom driver
The Native Lock driver and the 2N Doorstation driver run on the same site. Use the Native Lock for the front door you want managed as a lock, and the Doorstation driver for raw switches, inputs and SIP calls elsewhere on the same unit.
Spec it for the door that matters
For a front door, a gate, or a plant-room the client wants controlled and audited, this turns a 2N you may already be fitting into a managed access point — with users, schedules and an attributed log — and no separate access-control system to buy or wire.
The 2N Native Lock driver is a licensed product — a 30-day trial and full licences are on its product page. Compatibility, user management and the commissioning app are covered in the 2N Native Lock driver pages on lcd.network.
Hero image: Photo by Danielle Rice on Unsplash.


