UniFi  

Developer: Durosity     Like this plugin? Show your appreciation!
Category: IP Communications
Github: Github Repo
License: MIT License
Assistance: Get help!   
Plugin ID: com.durosity.indigoplugin.unifi
Latest release: v3.12.14 released on Nov. 12, 2026
Release downloaded: 16 times
Requires: Indigo v2023.2.0 or higher
(Check the Releases tab below for older releases that may have different requirements)
  Download latest release

UniFi for Indigo

An Indigo plugin bridging UniFi Network, UniFi Protect, UniFi Access, and UniFi Drive (UNAS) into your home automation system — devices, clients, cameras, sensors, door locks, firewall rules, and more, all as native Indigo devices, actions, and triggers.

Released under the MIT License by Durosity.

Before using this plugin, back up your UniFi configuration. This plugin writes to your live UniFi configuration: it can enable/disable firewall policies and WLANs, change port forwards, lock/unlock doors, reboot devices, change camera and sensor settings, and (experimentally) arm/disarm Protect's Alarm Manager. I've tested it quite extensively at my end, but it's plausible different configurations and setups may not work the same so please be careful.

Each UniFi OS console has its own backup/restore option (Settings → System → Backups on a Network console; the UNAS has its own separate backup under its own Settings). Do this now, not after something goes wrong. Real care is taken to confirm behavior against real data before shipping anything (see ROADMAP.md for the detailed, ongoing record of what's confirmed vs. still unverified), but this is community software with no warranty — you are responsible for your own backups, and for reviewing what an action does before wiring it into an automation that runs unattended.

A few specific things worth knowing going in:

  • The Alarm Manager feature (arm/disarm) is explicitly experimental. It's built from community reverse-engineering of an undocumented endpoint, not Ubiquiti's official API, and has never been tested against real Alarm Manager hardware. It also requires a dedicated Super Admin account with MFA disabled — a real security trade-off, not a minor detail. If you use this feature, treat it as unverified until proven otherwise on your own setup, and please report back (see Diagnostics below) if anything looks wrong.
  • Recording Mode and IR Mode cannot be controlled from this plugin — Ubiquiti's official Protect Integration API doesn't expose them (confirmed against the published spec). Use the UniFi Protect app directly for those.
  • Legacy/local admin credentials (see Setup) are required for several features and are stored by Indigo, not sent anywhere else by this plugin — but as with any credential, use a dedicated local-only account, not your main cloud login.

If something doesn't look right, every major device type has a "Dump Device Payload to Log" button in its own configuration dialog (or an equivalent action, for a couple of device types where that fits better) — use it, then open an issue with the result rather than guessing.

What this plugin covers

UniFi product What you get
Network Switches/APs/gateways, clients, individual switch ports (PoE control), firewall policies, traffic routes (policy-based routing), port forwarding, WLAN management, 5G/LTE gateway (U5G-class) cellular status
Protect Cameras (motion, person/vehicle/package, doorbell, audio detection, snapshots, and configuration), sensors (door/window/motion/leak), Alarm Manager (experimental)
Access Door locks — momentary unlock, leave-unlocked, auto-relock, lock
Drive (UNAS) Storage pools and disks, fan control, wake-on-LAN, reboot/shutdown

Real-time events (motion, smart detection, doorbell rings, client connect/disconnect, port link state, door unlock, and a long list of Network health events) arrive instantly over WebSocket connections, not polling. Slower-changing stats (CPU, memory, temperature, throughput, fan RPM) are refreshed on a configurable interval instead.

Requirements

  • A recent Indigo release (developed and tested against Indigo 2026.1)
  • A UniFi OS console (UDM, UDM Pro, UDR, UNVR, or similar) for Network/Protect/Access
  • A UniFi Drive (UNAS) appliance, separately, if you want Drive features
  • API keys/credentials as described in Setup below

Installation

  1. Download the latest release and double-click to install, or install manually via Indigo's plugin manager.
  2. Create a "UniFi Controller (Network)" device for your main console, and/or a "UniFi Controller (Drive)" device for your UNAS, if you have one.
  3. Configure each controller as described below, then use the Create Devices buttons in its own configuration dialog (or the equivalent Discover… actions) to populate individual devices.

Setup

Network / Protect / Access controller

Create a UniFi Controller (Network) device and fill in:

  • Connection: the console's IP address, HTTPS port, and Site ID (default unless you run multiple sites).
  • Features to enable: tick Network, Protect, and/or Access depending on what this console actually runs.
  • API Keys: Network and Protect share a single key, generated from the console's own Settings → Control Plane → Integrations page. Access uses a completely separate token, generated from inside the UniFi Access application itself (look for an API Token / Integrations menu there) — Access also runs on its own port, 12445 by default.
  • Legacy username/password: a number of features aren't available through the official Integration API yet and use a secondary, local-session login instead — PoE port mode toggling, client block/unblock, and richer device stats on the Network side. Use a local-only admin account (Settings → Admins → Create New, tick "Restrict to local access only"), not a UI.com cloud account, and not one with MFA enabled. This is the most common cause of HTTP 403 errors if misconfigured.
  • Click Test Connection to confirm everything's working before creating any devices.

Drive (UNAS) controller

Create a separate UniFi Controller (Drive) device — the UNAS is its own appliance with its own login, independent of the Network console above:

  • Connection + Authentication: IP address and port, then either an API key (Settings → Control Plane → Integrations, on the UNAS itself) or local admin username/password if your UNAS firmware doesn't yet support API keys.
  • SSH (fan control only): the UNAS's own REST API for fan control is currently read-only on UniFi firmware — writes return an HTTP error. To actually change fan modes, this plugin deploys a small helper service to the UNAS over SSH. Enable SSH on the UNAS (Settings → Control Plane → Console) and provide credentials here, then use the Deploy fan control button. Leave this section blank if you only want monitoring, not control.

Creating devices

Both controller types have Create Devices buttons directly in their own configuration dialog (cameras, sensors, network devices, access doors, storage pools, disks, the fan), and most device types also have a matching Discover… action for bulk creation via an Action Group — useful for re-running discovery later without reopening the controller's dialog. Both approaches skip devices that already exist rather than creating duplicates.

Features in detail

Network devices, clients, and ports

Switches, access points, and gateways come in as devices reporting online/offline status, CPU/memory/temperature, uptime, and more. Ports can be individually enabled/disabled, power-cycled, or have their PoE mode changed. Clients can be blocked, unblocked, or disconnected, and a built-in purge tool helps manage the buildup of randomized-MAC devices (iPhones, Android phones, and Windows machines rotating MACs for privacy) that accumulate over time — with dry-run support before anything is actually removed.

Firewall Policies, Traffic Routes, Port Forwarding, WLANs

Pick any of your own custom firewall policies, policy-based traffic routes, port forward rules, or WLANs from a live dropdown (built-in/predefined policies are filtered out — there are usually dozens, and toggling them isn't useful from automation) and control them as simple on/off devices. WLAN devices also support a dedicated password-change action.

5G/LTE gateway

If you have a U5G-class cellular gateway, it reports signal strength, carrier, radio technology, data usage, and roaming status alongside the usual network-device stats.

Protect cameras

Motion, person/vehicle/package detection, and doorbell rings arrive as live-updating states and triggers. Audio detection (via the camera's own microphone — no separate sensor needed) covers smoke alarms, CO alarms, sirens, glass breaking, burglar alarms, car horns, barking, speech, and baby crying; each type needs enabling via the Set Smart Detection Types action, same as object detection. An eventFeedLive state tracks whether the live event connection is actually up, so a dropped connection and a genuinely quiet house are never confused with each other.

Also supported: snapshots, reboot, status LED, on-screen overlays (name/date/logo), a custom LCD status message (doorbell hardware), HDR mode, microphone volume, video mode (only options this specific camera actually supports are offered), and RTSP stream URLs for external viewers.

Protect sensors

Door/window/garage contact, motion, leak, and general-purpose sensors, with temperature/humidity/light readings where supported. Each sensor's primary on/off state is picked sensibly by its mount type automatically, or can be pinned explicitly (Open/Closed, Motion, Leak, Alarm) if the automatic choice isn't what you want for a particular sensor.

Alarm Manager — experimental

Arm/disarm by profile (Home/Away/Night-style), built from an undocumented endpoint with no real hardware available to verify it against — see the warning at the top of this README before relying on it. Separately, a genuinely official "Trigger Alarm Manager Webhook" action fires any alarm you've already configured with a webhook trigger inside Protect itself — this doesn't arm or disarm anything on its own, it just fires whatever you've set up.

Access doors

Lock and unlock, with a configurable auto-relock timer for momentary unlocks (it re-locks on its own after a short window if the door's never opened, or waits for the door to close again if it is) and a separate "leave unlocked" mode for when you want the door to stay open until explicitly locked again.

Drive (UNAS)

Storage pools and individual disks report capacity, usage, health, and temperature. Fan control (once deployed via SSH, see Setup) lets you pick Quiet/Balance/Cooling/Default modes and reports real RPM per fan. Reboot, shutdown, and wake-on-LAN are also available.

Diagnostics

Almost every device type has a "Dump Device Payload to Log" button (in its config dialog) or action that logs the complete raw data UniFi is actually reporting — no debug mode required. This is the fastest way to get useful information into a bug report if a state looks wrong, blank, or missing. Debug logging (plugin config) adds further detail — API request paths, WebSocket reconnect attempts, and per-event timing — on top of that.

Why both official API and legacy auth?

Ubiquiti's official Integration APIs are growing but still don't cover everything — notably PoE port mode, client block/unblock, and richer Network device stats, and (for Drive/UNAS) there's no official API at all yet. Where the official API covers a feature, this plugin uses it; where it doesn't, a secondary local-session login bridges the gap, clearly labelled in the source as [INTEGRATION] or [LEGACY] so it's obvious which path is in use and easy to migrate a given feature across as Ubiquiti's own API coverage expands.

Known limitations

  • Recording Mode and IR Mode cannot be changed — not exposed by the official Protect API.
  • Traffic Rules and DPI app/category restrictions aren't built — on current UDM-class firmware, both appear to have been absorbed into the newer zone-based firewall and policy-routing systems this plugin already supports, rather than remaining distinct, live features worth building against.
  • Two-way audio ("talkback") isn't built into this plugin — if you need it, HomeKit's own native camera audio (via a HomeKit bridge plugin) already covers this well.
  • Guest voucher creation isn't built yet.
  • Chimes and Protect Viewers (ViewPorts) aren't supported as device types yet.

See ROADMAP.md in this repository for the full, ongoing detail behind every item above, plus everything that's been confirmed, built, investigated, and deliberately left out along the way.

License

MIT. See LICENSE.

Acknowledgements

Built with reference to several other MIT-licensed open-source projects and community research along the way — full attribution for each is recorded in ROADMAP.md at the point it was used, including the openHAB and Home Assistant projects' own documentation of the Protect event stream shape, and the wider UniFi developer community's reverse-engineering of UNAS/Drive endpoints in the continued absence of an official API.

Support

Open an issue on this repository. Including the output of the relevant device's "Dump Device Payload to Log" is the single most useful thing you can attach.

Release details
Released on: Nov. 12, 2026
Requires: Indigo v2023.2.0+
Downloaded: 16 times 
Changes in this release

v3.12.14

Covers all changes since v3.12.8.

Fixed

  • Bulk client discovery no longer fails on duplicate names (3.12.14). Clients without a UniFi name (e.g. several devices falling back to "Apple, Inc.") caused a NameNotUniqueError that aborted the whole run. Duplicate names now get " 2", " 3" etc. appended, and a failure on one item is logged and skipped rather than stopping the batch. This applies to every discovery flow, not just clients.
  • Controller device stats now populate (3.12.11). Camera, AP, switch, gateway and network device counts were never implemented and always showed 0. Protect version and recording storage (now in GB) are read from the correct source, and CPU, memory and uptime mirror the console's gateway.

New

  • Auto-create client devices on connect (3.12.13). A new, off-by-default Controller option creates a device as soon as UniFi reports a new client connecting. Randomised/private MACs are skipped by default, and clients you've deleted won't be recreated.
  • Package Camera support (3.12.9–3.12.12). For doorbells with a second package lens (confirmed on the G6 Entry), a linked Package Camera device mirrors its parent camera's full set of states, with live event updates and its own package RTSP URL. Package cameras are found by the normal camera discovery; there's no separate action.
  • Parent cameras gain an enablePackage option and rtspUrlPackage state.

Changes

  • RTSP for the package lens is controlled with the Enable/Disable RTSP Streaming actions, matching regular cameras.
  • The standalone "Discover Package Cameras" action from 3.12.9 has been removed; camera discovery handles it.

⚠️ Still beta software. Back up your UniFi controller before upgrading.

Release details
Released on: Nov. 9, 2026
Requires: Indigo v2023.2.0+
Downloaded: 19 times 
Changes in this release

Release Notes — v3.12.8 (vs. v3.5.1)

This covers everything since the last published release, v3.5.1. It's a large jump — UniFi Drive support has grown enormously, three new Network feature areas were added, a long-standing bug meant Protect's motion/detection events had never actually fired, and Access door lock/unlock was calling an endpoint that didn't exist. Full version-by-version detail is in CHANGELOG.md; this groups the same material by what it actually means for you.

This is still beta. Back up your UniFi configuration before upgrading — see README.md for details, including which features (Alarm Manager specifically) remain experimental and unverified.

⚠️ If you're upgrading from v3.5.1 or earlier, read this first

  • UNAS Fan device changed type (dimmer → proper speed-control). Existing fan devices must be deleted and recreated via the "Create Fan Device" button — this is a genuine Indigo limitation (a device's fundamental type can't be changed in place), not something a plugin update can do for you automatically.
  • Access door on/off meaning flipped. It used to be "on = unlocked"; it's now "on = locked", matching Indigo's own icon convention for lock-type devices (this is also why the padlock icon was showing backwards before). The Lock/Unlock buttons and status text are unaffected either way, but if you built a trigger or Action Group directly against the raw on/off value rather than Lock/Unlock, check it still does what you expect.
  • Network device on/off meaning changed from "enabled/disabled" to "online/offline" — more useful day-to-day, but if you have a trigger on a network device's generic on/off state, it now fires on connectivity rather than the admin-enabled flag.
  • Both of the above happened because relay-type devices in Indigo always show their raw on/off state in the device list no matter what — getting the text right (Locked/Unlocked, Online/Offline) needed a different, now-confirmed mechanism (uiValue), not just picking a better state to display.

Major new features

UniFi Drive (UNAS) went from essentially nothing to full support: storage pools and disks as individual devices, fan control (Quiet/Balance/Cooling/Default) via an SSH-deployed helper service — UniFi's own fan-control write API is confirmed broken on current firmware, returning HTTP 500 for every payload tried — with real per-fan RPM reporting, auto-redeploy if a firmware update wipes the helper service, plus reboot, shutdown, and wake-on-LAN.

Three new Network feature areas, all confirmed against a live controller rather than built from documentation alone: Firewall Policies, Traffic Routes (policy-based routing), Port Forwarding, and WLAN management (enable/disable plus password changes) — each with bulk discovery.

5G/LTE gateway support for U5G-class hardware: signal strength, carrier, data usage, roaming status, radio technology.

Access door lock/unlock actually works now. It was calling an endpoint that doesn't exist on the real API at all (confirmed 404) — fixed to the real one, plus momentary unlock with configurable auto-relock, a separate "leave unlocked" mode, and explicit lock.

Protect motion and detection events are fixed — and this is the big one: neither WebSocket handler had matched a single real message since the plugin moved to the official Integration API. Motion, person/vehicle/package/animal detection, and doorbell rings had not been firing at all; if an automation built on these appeared to work, it was relying on something else. Also new since 3.5.1:

  • Audio detection via camera microphones — smoke alarms, CO alarms, sirens, glass breaking, burglar alarms, car horns, barking, speech, baby crying — no separate sensor hardware needed.
  • RTSP stream URLs fixed (previously read fields that don't exist in the official API, so they could never populate).
  • Camera monitoring fields (firmware version, IP, uptime, voltage) now populate via an optional secondary login, reusing the same local admin account already used for Network/Drive.
  • New camera actions: HDR mode, microphone volume, video mode (options shown are only what each specific camera actually supports), and smart detection type selection extended to cover audio types.
  • Sensor primary-state override — pin a sensor's on/off meaning explicitly (Open/Closed, Motion, Leak, Alarm) instead of relying only on automatic mount-type detection.
  • Event feed health tracking — motion/detection states no longer silently go stale if the live connection drops; there's now a clear, separate indicator for that.
  • Alarm Manager: an experimental, unverified arm/disarm (built from an undocumented endpoint, no hardware available to test against — see the warning in README.md), plus a separate, genuinely official webhook-trigger action.

Diagnostics: most device types now have a "Dump Device Payload to Log" button or action — logs the complete raw data UniFi is reporting, no debug mode required, by far the fastest way to get useful information into a bug report.

Randomized client MAC purge, with a dry-run mode, for cleaning up the buildup of rotating-MAC devices (iPhones, Android phones, Windows machines) that accumulate as visitors come and go.

Expanded event coverage: 16 additional Network health triggers (overheating, PoE overload, rogue AP/DHCP detection, firmware upgrade success/failure, WAN failover, adoption, and more), plus raw event key/message states on every network device and client for anything not yet covered by a dedicated trigger.

Reliability fixes

  • WebSocket reconnection handles a server-initiated clean close correctly now (previously misidentified as a failure and needlessly delayed reconnecting), detects genuinely dead/zombie connections that would otherwise hang forever, and auto-recovers from an expired legacy session instead of requiring a plugin restart.
  • Fixed a startup crash under Indigo's exec-based plugin loading.
  • Fixed a duplicate-device-detection bug that silently capped pool/disk discovery at one device per type.
  • Fixed a Protect HTTP 429 rate-limit error that hit anyone with more than about 10 cameras.
  • Fixed several Devices.xml issues that were silently logging an error on every single plugin start.

Still not supported (confirmed, not overlooked)

  • Recording Mode and IR Mode — not exposed by the official Protect API at all; use the UniFi Protect app directly.
  • Traffic Rules and DPI app/category restrictions — investigation suggests both may have been absorbed into newer systems this plugin already covers, on current UDM-class firmware.
  • Two-way audio ("talkback") — not built here; if you need it, a HomeKit bridge plugin already covers this well via HomeKit's own native camera audio.

See CHANGELOG.md for the complete version-by-version record, and ROADMAP.md for what's still being investigated.