The UniFi OS console that runs Protect (cameras) and Access (doors and readers) joins SmartTile through the connection you already made for UniFi Network — every camera and reader is monitored, a dead one is ticketed, and each customer sees only its own.
A camera that went dark on Friday is usually found on Monday, when someone needs the footage. SmartTile reads the console every 60 seconds and treats a Protect camera or an Access reader like any other device it monitors: present only when the console lists it online in this poll. One console can serve several customers — every camera and door carries its own company and location, and nobody sees a device that is not theirs. BETA: built and running; the limits below are stated plainly.
Cameras, NVRs, doors, hubs and readers are mirrored per console. A console serving one mapped site hands its location down; on a multi-site console a SmartChoice admin assigns each device — never guessed.
Only the cameras and readers someone ticks land on Devices, under Physical Security – Camera / Access Control, on the customer's monitoring plan.
Offline in Protect or Access, or missing from the list for 5 minutes, is DOWN. A boot time moving forward is a reboot, recorded DOWN→UP and counted toward the 3-in-60-minutes reboot-loop ticket.
An availability sample per device every sync, kept 90 days, plus every transition in state history — the device's Uptime modal and reports count the outage.
Protect's RTSPS stream is repackaged to HLS on the fly (H.265 cameras transcoded), shared between viewers and stopped when nobody watches. Nothing is recorded beyond the rolling window.
Motion, smart detections, rings and sensor events from the console's websocket, or its Alarm Manager webhook — each with a snapshot, kept 30 days. Cloud-only consoles fall back to snapshot-change motion.
Door lock and position state, hub status, and door openings gap-filled from Access system logs (or pushed by the Access webhook), on the same timeline.
Unlock (tech role), lock rules (admin role), lockdown / evacuation (SmartChoice only). A reason is required and every attempt — success or failure — is in the physical-security audit log.
| Reached | What works |
|---|---|
| Directly (console API key) | Everything on this page: inventory, status, reboots, tickets, snapshots, live view, real-time events. |
| Cloud connector (owner / org key) | Protect inventory, status, snapshots and live view (with 7441 open); events by webhook or snapshot-change motion. |
| Site Manager listing only | Online / offline and firmware for cameras, hubs and readers — so monitoring and tickets still work. No snapshots, live view or events. |
| UniFi Access | Needs port 12445 reachable (or the Access webhook for door events). Otherwise hub and reader status come from the listing. |
The same gate as UniFi Network: offline for 3 consecutive checks (about 6 minutes), a fleet-share hold for reporting gaps, the device's auto-ticket flag and the location's automation switch. A separate switch can stop camera and reader tickets without touching the network.
Through the normal SmartTile ticket path with per-location dedup — to Rev.io and any other IT Service Management (ITSM) system connected for the company. A Rev.io ticket closes once every device on it is confirmed back up.
My Cameras shows the customer only the cameras and doors SmartChoice has made visible to them, with live view and badge events. Door unlock from the portal is a per-company switch, off by default.
/proxy/protect/integration/v1/cameras · /nvrs · /sensorsinventory and state (also /lights, /chimes)/proxy/protect/integration/v1/cameras/{id}/snapshotthumbnail and event snapshot/proxy/protect/integration/v1/cameras/{id}/rtsps-streamopen a live stream (DELETE closes it)/proxy/protect/integration/v1/subscribe/eventsreal-time events (direct consoles):12445/api/v1/developer/doors · /devicesdoors, hubs and readers:12445/api/v1/developer/system/logsdoor openings since the last cursor (a read):12445/api/v1/developer/doors/{id}/unlockonly when a person unlocks, with a reason:12445/api/v1/developer/doors/{id}/lock_rulelock rule, admin role, audited:12445/api/v1/developer/system/emergencylockdown / evacuation — SmartChoice onlyapi.ui.com /v1/connector/consoles/{id}/… · /v1/devicescloud connector and Site Manager listingEvery camera, door and reader row carries a company. Anyone but a SmartChoice super admin sees only their own — and in the portal, only what is marked visible.
The API key, the Access token and the optional local Protect password are encrypted at rest and never shown again — the form only says one is set.
Monitoring is read-only. A door changes state only when a named user acts with a reason; lockdown is SmartChoice-only.
Protect, Access, camera/reader tickets, live view, event ingest, snapshot motion, uptime history and the customer portal each have their own setting.
| Objection | Answer |
|---|---|
| “Protect already tells us a camera is offline.” | It tells whoever is logged in. SmartTile records the outage, counts it in uptime and opens the ticket — one per site. |
| “Can another customer see our cameras?” | No. Rows are partitioned by company server-side; a device on no customer's location is visible to no customer. |
| “Is this finished?” | It is BETA: inventory, monitoring, tickets, live view, events and door actions are built. Cloud-only consoles have the limits in the table — nothing more is promised. |