A 2N intercom is doing a lot of work at the front gate. It has relays for the strike and the gate motor, digital inputs watching the door contact and the request-to-exit button, a camera, a call button, and a SIP stack that can ring a phone anywhere. On most jobs Crestron Home sees almost none of it — the intercom rings a handset, opens a door, and stays a closed box beside the drive.

The 2N Doorstation driver opens that box. It exposes the 2N as a programmable control surface in Crestron Home: every switch, every input, the relay and output, and SIP call control — each one a tile control, a programming action you can call, and a programming event you can react to.

Everything the 2N can do, in programming

Add the driver and the intercom’s hardware turns into named pieces you can wire up:

• Switches 1–4 — energise or de-energise each 2N switch to release a strike, trigger the gate, or drive a relay, from a scene, a schedule, or the tile.
• Digital inputs 1–4 — the live open/closed state of a door contact or exit button, on the tile and as input opened / input closed events.
• Relay and output — state changes surfaced to programming.
• SIP call control — call the Crestron touch panels (or a custom SIP target) and hang up, when the 2N has a registered SIP account.

So the gate strike becomes a Crestron action, the door contact becomes a Crestron event, and the intercom can ring the panels in the house — all inside the programming you already build.

Events fire however the door was opened

The driver doesn’t just watch its own commands. It monitors the 2N’s event log, so a switch, input, relay or output event fires whether the change came from a Crestron scene, from the tile, or directly on the 2N — a keypad code, a request-to-exit button, a fob. There are also events for motion, noise and a call-button press.

That is the difference between “I know when Crestron opened the door” and “I know when the door opened.” Bind your notification, your log, or your welcome scene to the event and you catch every case, not just the ones your own automation caused.

[Screenshot to add: the 2N Doorstation tile — Switches / Inputs / Call Control]

A setup app that proves the wiring

The driver ships a browser-based Diagnostics & Setup app, served from the processor. It shows the live connection, streams the device event log, runs a connection troubleshooter that checks the network, the HTTP API and the credentials in order, and lets you fire test actions — pop a switch, place a call — from your laptop without walking back to the gate. Commission it once, prove it, sign it off.

The upgrade is painless

This is the current, web-configured version of the long-standing 2N Basic Http driver, rebuilt on the Crestron Home entity model. It keeps the same product SKU (CHTWONHW), so an existing licence key still works — there is no repurchase. Device actions are gated until the driver is licensed; feedback and the diagnostics app run regardless.

It also sits happily alongside the 2N Native Lock driver on the same site: use the Native Lock when you want the door to appear as a standard Crestron Home lock with PIN users, and the Doorstation driver for raw switches, inputs and call control.

Spec it because it needs no new hardware

The intercom is already on the wall and already on the network. The driver turns hardware the customer has already paid for into a first-class part of the Crestron system — no rack module, no bridge box, no cloud account.

The 2N Doorstation driver is a licensed product — a 30-day trial and full licences are on its product page. Compatibility, the full control/event list and the setup app are documented in the 2N Doorstation driver pages on lcd.network.

Hero image: Photo by Gabriel Ramos on Unsplash.