There is currently support for the following device types within Home Assistant:
Currently this implementation only exposes POE control for networked devices. Device tracker implementation is not using the same code base.
Home Assistant offers UniFi integration through Configuration -> Integrations -> UniFi Controller.
user name and
password and then continue to select which
site you want to connect to Home Assistant. The user must have administrator privileges.
If you have problems with UniFi or the component you can add debug prints to the log.
logger: default: info logs: aiounifi: debug homeassistant.components.unifi: debug homeassistant.components.switch.unifi: debug
To use this device tracker in your installation, add the following to your
# Example configuration.yaml entry device_tracker: - platform: unifi host: unifi username: username password: password ssid_filter: - 'HomeSSID' - 'IoTSSID'
(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
(integer)(Optional)The port of your controller’s web interface
Default value: 8443
(string)(Optional)For multisite installations, you can specify
site_idto 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
(integer)(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.
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.
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.
For environments where there are multiple sites setup on the controller, or the default site is not being used you can use the
site_id parameter to specify which site you would like to target.
Please note that the value that is to be specificed here is not the name of the site as you would see it in controller interface, but a site ID value assigned from the software itself.
To obtain this value for your configuration file, you can take it from the URL of your browser when on the controller webpage.
For example, this is what would be seen in the URL bar when inside the dashboard page of a site:
site_id value would be
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.
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:
Switches are network devices that are powered by POE switches from Ubuiqitis UniFi line of networking gear.
Note that POE control actually configures the network port of the switch which the device is connected to.