Ubiquiti Unifi WAP

This platform allows you to detect presence by looking at devices connected to a Ubiquiti Unifi controller.

To use this device tracker in your installation, add the following to your configuration.yaml file:

# Example configuration.yaml entry
  - platform: unifi
    host: unifi
    username: username
    password: password
      - 'HomeSSID'
      - 'IoTSSID'

Configuration Variables


(string)(Required)A user on the controller


(string)(Required)The password for the account


(string)(Optional)The hostname or IP address of your controller

Default value: localhost


(int)(Optional)The port of your controller’s web interface

Default value: 8443


(string)(Optional)For multisite installations, you can specify site_id to specify which is used

Default value: default


(boolean or filename)(Optional)Whether to do strict validation on SSL certificates of the Unifi controller. This can be true/false or the path to a locally trusted certificate to use for verification (i.e. “/path/to/custom_cert.pm”)

Default value: true


(int)(Optional)How long since the last seen time before the device is marked away, specified in seconds.

Default value: 300


(list of strings)(Optional)Filter the SSIDs that tracking will occur on.

Default value: None


(list)(Optional)A list of extra attributes to pull from the Unifi controller.

Default value: None

See the device tracker component page for instructions how to configure the people to be tracked.

Configuring Users

The Unifi controller allows you to create multiple users on it besides the main administrator. It is recommended that you create a limited user that has read-only permissions for the Unifi device tracker.

Conflicts with MQTT

The Unifi controller can either be a dedicated hardware device (Unifi’s cloud key), or as software any Linux system. If you run the Unifi controller on the same operating system as Home Assistant there may be conflicts in ports if you have the MQTT component as well.

It is recommended that you run the Unifi controller in a dedicated virtual machine to avoid that situation.

Troubleshooting and Time Synchronization

Presence detection depends on accurate time configuration between Home Assistant and the Unifi controller.

If Home Assistant and the Unifi controller are running on separate machines or VMs ensure that all clocks are synchronized. Failing to have synchronized clocks will lead to Home Assistant failing to mark a device as home.

Related Issue

Monitored Conditions

The Unifi controller returns a number of additional attributes that can be used for tracking devices, including signal strength, rx/tx rates, and which AP it is connected to. The list of possible options may vary depending on your Unifi controller version and if a device is wired or wireless.

Unifi Controller version 5.6.29 has the following options:

  • _id
  • _is_guest_by_uap
  • _last_seen_by_uap
  • _uptime_by_uap
  • ap_mac
  • assoc_time
  • authorized
  • bssid
  • bytes-r
  • ccq
  • channel
  • essid
  • first_seen
  • hostname
  • idletime
  • ip
  • is_11r
  • is_guest
  • is_wired
  • last_seen
  • latest_assoc_time
  • mac
  • name
  • noise
  • noted
  • oui
  • powersave_enabled
  • qos_policy_applied
  • radio
  • radio_proto
  • rssi
  • rx_bytes
  • rx_bytes-r
  • rx_packets
  • rx_rate
  • signal
  • site_id
  • tx_bytes
  • tx_bytes-r
  • tx_packets
  • tx_power
  • tx_rate
  • uptime
  • user_id
  • usergroup_id
  • vlan