| 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 |
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:
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.
| 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.
Create a UniFi Controller (Network) device and fill in:
default unless you run multiple sites).Create a separate UniFi Controller (Drive) device — the UNAS is its own appliance with its own login, independent of the Network console above:
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
MIT. See LICENSE.
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.
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.
| Released on: | Nov. 12, 2026 |
| Requires: | Indigo v2023.2.0+ |
| Downloaded: | 16 times |
| Download this release | |
Covers all changes since v3.12.8.
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.enablePackage option and rtspUrlPackage state.⚠️ Still beta software. Back up your UniFi controller before upgrading.
| Released on: | Nov. 9, 2026 |
| Requires: | Indigo v2023.2.0+ |
| Downloaded: | 19 times |
| Download this release | |
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.
uiValue), not just picking a better state to display.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:
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.
See CHANGELOG.md for the complete version-by-version record, and ROADMAP.md for what's still being investigated.