From e9c73483aec7d834339bd8e9cdbefceffb9afcee Mon Sep 17 00:00:00 2001 From: Keiran S Date: Wed, 17 Oct 2018 17:54:04 +1100 Subject: [PATCH] Updating unifi documentation to be clearer about the site_id value (#6876) * Updating unifi documentation to be clearer about obtaining the correct site_id value * Minor changes --- source/_components/device_tracker.unifi.markdown | 15 +++++++++++++++ 1 file changed, 15 insertions(+) diff --git a/source/_components/device_tracker.unifi.markdown b/source/_components/device_tracker.unifi.markdown index 2bb4372c4b3..60d6448dd5b 100644 --- a/source/_components/device_tracker.unifi.markdown +++ b/source/_components/device_tracker.unifi.markdown @@ -88,6 +88,21 @@ The Unifi controller can either be a dedicated hardware device (Unifi's cloud ke It is recommended that you run the Unifi controller in a dedicated virtual machine to avoid that situation. +### {% linkable_title Correctly specifying the Site ID %} + +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: + +* https://127.0.0.1:8443/manage/s/ceb1m27d/dashboard + +And your `site_id` value would be ceb1m27d. + + ### {% linkable_title Troubleshooting and Time Synchronization %} Presence detection depends on accurate time configuration between Home Assistant and the Unifi controller.