Merge UniFi device tracker to config entry

[Kane610]

Breaking Change:

Device tracker is now part of config entry. After initial import the unifi device tracker configuration is no longer needed. If configuring SSID filter or detection time you will need to use the new configuration from UniFi. See UniFi component documentation for details.

Description:

Allows migrate device tracker unifi configuration to config entry
Removes requirement to have an admin level account, controls are moved to the switch platform
Additional configuration handled from unifi: level.

Related issue (if applicable): fixes #24895, #23490, #21636, #19301, #14663

Pull request with documentation for home-assistant.io (if applicable): home-assistant/home-assistant.io#9847

Example entry for configuration.yaml (if applicable):

Checklist:

• The code change is tested and works locally.
• Local tests pass with tox. Your PR cannot be merged unless tests pass
• There is no commented out code in this PR.
• I have followed the development checklist

If user exposed functionality or configuration variables are added/changed:

• Documentation added/updated in home-assistant.io

If the code communicates with devices, web services, or third-party tools:

• The manifest file has all fields filled out correctly. Update and include derived files by running python3 -m script.hassfest.
• New or updated dependencies have been added to requirements_all.txt by running python3 -m script.gen_requirements_all.
• Untested files have been added to .coveragerc.

If the code does not interact with devices:

• Tests have been added to verify that the new code works.

[ghost]

Hey there @Kane610, mind taking a look at this pull request as its been labeled with a integration (unifi) you are listed as a codeowner for? Thanks!

This is a automatic comment generated by codeowners-mention to help ensure issues and pull requests are seen by the right people.

[olbjan]

Pretty please let us filter which devices the tracker will pull off the unifi controller. The current tracker allows for filtering by site, ssid etc.- if you just import everything that will be a mess.

[Kane610]

@olbjan when config entry options are supported in the front end, a lot of configuration is possible. Site is already part of the configuration, so a new config entry per site.

I will look into keeping the current configuration when importing to a config entry

[balloob]

Why would it be a mess? You can just choose to not show the entities in the Lovelace UI?

[olbjan]

The UniFi controller can eg host multiple homes as different sites - or depending on the setup you may be tracking hundreds of devices even though they're not shown just to get the few that are actually interesting to you. We use HA at work for the office and I would eg not want it to track every cellphone connected to the guest wifi ssid whilst I may be interested in the devices on the IoT ssid.

[balloob]

Seems like a valid use case 👍 Let's start with keeping that config in configuration.yaml and we can migrate it later to config flow options.

[Kane610]

@balloob should we define what data which is interesting for this entity type and make properties for them all? We got a possibility to shape up a lot of data here.

[balloob]

Yes, but let' keep it rather simple. For now maybe just implement an entity that has it's own async_see function that mimics the old behavior?

[Kane610]

Sure will look at that next

[Kane610]

@balloob isnät what you want just having each network device exposing a last_seen property?

[balloob]

It's not just last seen. Each entity will have to schedule an update when the last seen property passes over the threshold that it is considered not home.

[Kane610]

@balloob something like this?

[MartinHjelmare]

Looks good!

[MartinHjelmare]

From the breaking changes paragraph:

On how to configuring SSID filter or detection time you will need to use the new configuration from unifi.

This sentence sounds a bit weird. Should it start: "If configuring SSID filter or detection time you will need to..."?

[theOrakle]

Are you planning on adding GPS coordinates? Ultimately, so I can track the same device with via the home assistant app on IOS... This is how I was doing it prior.

I see this in the logs when I update my location via IOS:
ERROR (MainThread) [homeassistant.components.device_tracker] The see service is not supported for this entity device_tracker.g1iphone

If not, I suppose I can make 2 devices for the same phone and tie them together via the person. Seems silly, but a pretty easy workaround.

[balloob]

Tying things via person integration is the way forward.

Also, we should not discuss things on closed PRs.