Switch what a Viewport shows and browse a named camera grid on the panel — both driven by UniFi's own API, not a scraped login.
UniFi Protect Viewport driver for Crestron Home
One purchase covers two Crestron Home drivers: the UniFi Protect Viewport driver, which switches a UniFi Protect Viewport's liveview from remotes, keypads, and touch panels, and the Camera Grid extension, which adds a named, tappable camera grid to the touch panel with per-camera favorite, hide, sort, and rename editable right on the panel. Each part licenses with its own node-locked key, but buying UniFi Protect Viewport puts both keys in the cart. Pricing will be announced at launch.
In development · coming soon
Pricing will be announced at launch. One license per Crestron Home processor. One license covers the UniFi Protect Viewport driver on that processor, regardless of how many devices are installed. No subscription. One processor transfer included.
Crestron certification: planned; currently pre-certification builds. · v0.1.0 development changelog →
Not ready to buy? Get notified when UniFi Protect Viewport ships.
Driver specs
| Protocol / control path | UniFi Protect official integration API, local API key, local network |
|---|---|
| Cloud required | No |
| External account | No. Local API key issued from your own Protect console (each part uses its own key) |
| Key features |
|
| Processor support | Crestron Home 4-Series (CP4-R class, bench-verified) |
| License | One license per Crestron Home processor. One license covers the UniFi Protect Viewport driver on that processor, regardless of how many devices are installed. No subscription. One processor transfer included. |
| Certification status | Crestron certification: planned; currently pre-certification builds. |
| Current build | v0.1.0 |
Supported
- Viewport liveview switching from Crestron Home remotes, keypads, and touch panels
- 48 numbered presets keyed to the remote (1-9, 0 = Preset 10)
- Named, tappable camera grid on the touch panel (Camera Grid) with per-camera favorite, hide, sort, and rename
- Self-healing stream tokens and automatic recovery from a bad API key or an unreachable NVR
- Live license/trial status for both parts on the installer Driver Status line
Not yet supported
- No live camera thumbnails on Camera Grid tiles — named icons only, by design
- No liveview deletion — UniFi Protect's integration API has no delete call, so old liveviews stay on the NVR harmlessly
Compatibility
Requires
Crestron Home 4-Series processor (CP4-R class, bench-verified) · UniFi Protect console (UniFi OS) with the integration API enabled and a local API key generated per driver · One or more UniFi Protect Viewport hardware units on the same Protect system · Network access from the Crestron processor to the NVR on the project LAN
Network
Local network access to the device, with no cloud relay in the control path.
Compatibility matrix
- Verified against 7.2.105 / CH-OS n/a on 2026-09-06 ( today)
- Verified against 7.1.87 / CH-OS n/a on 2026-09-06 ( today) sample
Why it's built this way
- Built on UniFi's official Protect integration API using a local API key, with no reverse-engineered cookie or CSRF session to break on the next Protect update.
- 48 numbered presets, keyed straight to the remote: keypad digits 1-9 jump to Presets 1-9, 0 jumps to Preset 10, so a client's favorite cameras are one button-press away even on a hard remote with no touch panel in the room.
- The Camera Grid extension adds a named, tappable camera tile on the touch panel in place of a numbered preset, with per-camera favorite, hide, sort, and rename editable right on the panel, no config tool needed.
- Designed to self-heal stream tokens instead of quietly going stale and leaving a camera frozen, with automatic recovery from a bad API key, a bad viewer, or the NVR going unreachable.
- Pairs with the free Protect Streams Utility, which hands you the stream and snapshot URLs to drop into Crestron Home's native camera pages while these drivers handle Viewport switching.
- Local network control against your own Protect console for both parts, with no external UniFi cloud account required.
Requirements
- Crestron Home 4-Series processor (CP4-R class, bench-verified)
- UniFi Protect console (UniFi OS) with the integration API enabled and a local API key generated per driver
- One or more UniFi Protect Viewport hardware units on the same Protect system
- Network access from the Crestron processor to the NVR on the project LAN
Evaluate first
Every SynDrivers driver runs in trial mode when no license key is installed. Sideload it and prove it on your own processor, full features, time-limited per load. When it earns its place, license the processor and drop in your key.
FAQ
- Do I need a UniFi cloud account for this to work?
- No. Both parts authenticate with a local API key against your own Protect console over the local network, so no UniFi cloud account is required.
- Is the Camera Grid extension a separate purchase?
- No. Buying UniFi Protect Viewport puts both this driver's license key and the Camera Grid extension's license key in the cart. Each key licenses its own part, per Crestron Home processor, so they still license separately once installed.
- Do I need Camera Grid to use Viewport switching at all?
- No. The Viewport driver alone switches liveviews from remotes, keypads, and the touch panel's Additional Functions list. Camera Grid adds a named, tappable grid on top of that same switching, but it requires the Viewport driver already installed and paired.
- How is this different from the free Protect Streams Utility?
- The free utility is a one-time setup tool: it scans your Protect instance and hands you a table of stream and snapshot URLs to paste into Crestron Home's native camera pages. UniFi Protect Viewport is the ongoing Crestron Home integration, handling Viewport liveview switching, the touch panel camera grid, and stream-token upkeep, and it uses the utility as its setup companion.
- Does it use the same login as the Protect mobile or web app?
- No. Both parts authenticate only with a local API key issued from the Protect console's own settings, not the cookie-based session the app uses.