Skip to main content
Homelab

How to Setup a Unifi AP Without a Controller

Mustafa · · 3 min read

Why Run a UniFi AP Without a Controller?

Ubiquiti’s UniFi access points are designed to be managed by the UniFi Network Controller, but not everyone wants to run a dedicated server or cloud instance just to keep one or two APs online. Whether you’re running a small homelab, a temporary pop-up office, or simply prefer a leaner setup, standalone mode lets you configure the AP directly and skip the controller entirely.

In this guide you’ll learn three ways to get your UniFi AP up and running without a controller: the UniFi mobile app, direct SSH adoption, and the device’s built-in management page.

Method 1: Using the UniFi Mobile App

Step 1 – Download the App

Install the UniFi Network app from the App Store (iOS) or Google Play (Android). Create a Ubiquiti account if you don’t already have one.

Step 2 – Power On the AP

Connect the AP to your network switch using a PoE injector or a PoE-capable switch port. Wait about two minutes until the LED ring turns solid white, indicating the device is ready for adoption.

Step 3 – Adopt via Bluetooth

Open the app, tap Set Up a New Device, and follow the on-screen prompts. The app communicates with the AP over Bluetooth Low Energy (BLE) during initial setup, so keep your phone within a few metres of the device. You can configure the SSID, password, VLAN, and radio settings directly from the app.

Step 4 – Verify Connectivity

Once the app confirms the setup is complete, connect a client device to the new SSID and verify internet access. The AP will continue to broadcast the configured network independently; the app is only needed for future changes.

Method 2: SSH Adoption (Advanced)

Step 1 – Find the AP’s IP Address

Check your router’s DHCP lease table or use a tool like nmap or Advanced IP Scanner to locate the AP. UniFi APs default to DHCP on the LAN port.

Step 2 – SSH into the Device

Use an SSH client such as PuTTY (Windows) or the built-in terminal (macOS/Linux):

ssh [email protected]
# Default password: ubnt

Step 3 – Configure the AP

Once connected, you can set the SSID and passphrase manually using the mca-cli-op or set-inform commands. For a simple standalone config you can edit /tmp/system.cfg and persist changes with cfgmtd -w -p /etc.

This method is best suited for experienced users who want scripted or automated deployments.

Method 3: Built-in Device Web UI (Older Firmware)

Some older UniFi AP firmware versions expose a lightweight web interface at https://<AP-IP>:443. If available, you can log in with the default credentials (ubnt/ubnt) and configure basic wireless settings. Note that Ubiquiti has removed this interface in newer firmware releases, so this option may not be available on recent hardware.

Pros and Cons of Running Without a Controller

Advantages

  • Simplicity – No server or VM to maintain.
  • Lower resource usage – Ideal for homelabs with limited compute.
  • Quick deployment – Perfect for temporary or single-AP setups.

Disadvantages

  • No centralised management – Each AP must be configured individually.
  • Limited features – Guest portals, traffic stats, and automatic channel optimisation require the controller.
  • Firmware updates – You’ll need to update each AP manually via SSH or the mobile app.

Tips for a Stable Standalone Setup

  • Assign a static IP (or a DHCP reservation) to each AP so you can always find it on the network.
  • Change the default SSH password immediately after first login.
  • If you later decide to add a controller, the AP can be adopted without a factory reset—just run the set-inform command pointing to your controller’s URL.
  • Keep a note of the firmware version; some standalone features depend on specific builds.

Conclusion

Setting up a UniFi AP without a controller is straightforward once you know your options. For most home users, the mobile app is the fastest route. Power users who prefer terminal access can use SSH for full control. Either way, you get enterprise-grade Wi-Fi without the overhead of running a full controller stack.

Share this article