Commissioning app
The driver ships an installer-facing web app for commissioning the lock on site: confirm the 2N is reachable, see the door state and who has been coming and going, test the strike without walking back to the door, and prove a user's PIN and schedule before you leave. It runs on the processor — no internet or extra software needed.
The app is read-only over the lock configuration: users, PINs and schedules are still added and edited from Crestron Home's native lock settings (see User Management). The app is for verifying and troubleshooting, not editing.
Opening the app​
The driver publishes two links in its configuration settings (see Installing & Configuring):
- Diagnostics & Setup — opens the commissioning app directly. This is the quickest route.
- Product App URL — opens the hosted LCD product page; from there, choose the Configure card for 2N Lock to reach the same app.
The link opens over http on the processor's address — this is expected; the Crestron appliance serves these on-box apps over http, not https.
The app has three tabs: Diagnostics, Troubleshooter and Emulator.
Diagnostics​
The on-site sign-off surface. It shows, live:
| Panel | What it tells you |
|---|---|
| 2N connection | Whether the driver is talking to the device, and its address. |
| Door / strike | The current lock state and which switch drives the strike. |
| Entry users | How many users exist, how many have a PIN, and how many are scheduled. |
| Licence | Whether the driver licence is active. |
| Live lock | The current state, the last event with the user it was attributed to, and Test unlock / Test lock buttons that fire the real strike. |
| Access log | Recent access events, newest first, each attributed to a user — the who and when the native lock tile doesn't show. |
The log is held in memory, so it starts empty each time the driver loads and keeps only the most recent events. The 2N device keeps the authoritative record.
Troubleshooter​
When a 2N won't connect, run the troubleshooter. It runs six checks against the device in sequence, each with a plain-language result and — for anything that fails — how to fix it. A Copy report for support button produces a plain-text summary you can paste into a support ticket.
| Check | Confirms |
|---|---|
| Network reachability | The processor can reach the 2N on the network. |
| HTTP API enabled | The 2N's HTTP API is switched on and answering. |
| API credentials | The configured username and password are accepted. |
| API services & privileges | The API account is authorised for the services the driver uses — System, Switch, Event log and Directory / access-control. |
| Device capabilities | The unit exposes a switch for the strike, and reports its keypad / reader and its Enhanced-Integration (Automation) licence. |
| Door-strike switch | The configured switch exists and is enabled, with its mode, pulse time and current state. |
If a check fails, fix the flagged step and run the checks again — later checks are skipped when an earlier prerequisite fails, so you always chase the real cause rather than every red row.
Emulator (config check)​
Prove a user's access before you trust it. Pick who is at the door, how they present (PIN, card, a remote unlock from Crestron, or the physical thumbturn), and a day and time — the app runs the driver's real access rules and tells you whether the door opens, why, and which Crestron Home event fires, attributed to the user.
Use it to sanity-check a schedule without waiting for the window, or to confirm a new PIN user is set up correctly. The physical thumbturn and a remote Crestron unlock are never schedule-gated; PIN and card entries are checked against the user's schedule exactly as the device enforces it.
During commissioning​
A good sign-off sequence on site:
- Troubleshooter → Run all checks — confirm the 2N is reachable, authorised and wired as expected.
- Diagnostics → Test unlock — confirm the strike physically releases (and Test lock re-secures it). Watch the Access log attribute a real keypad PIN entry to the right user.
- Emulator — spot-check a scheduled user's access at an in-window and out-of-window time.
Continue to User Management.