Rework UniFi device tracker to utilizing entity description

[Kane610]

Breaking change

Proposed change

Migrate sensor platform to utilize entity description much as switch and #81821 and #81930 platforms.
This currently breaks signalling for when config entry options are enabled thus removing those tests, will be readded later on
Once device trackers are migrated and strict typing is achieved I will start merging entity descriptions to one common.

Related PRs

• UniFi switch entity description #81680
• Align implementation of the unifi update platform with the unifi switch platform #81821
• Unifi use entity description with sensors #81930
• Rework UniFi device tracker to utilizing entity description #81979
• Split out part of update sensor to a common UniFi entity class #84262

Type of change

• Dependency upgrade
• Bugfix (non-breaking change which fixes an issue)
• New integration (thank you!)
• New feature (which adds functionality to an existing integration)
• Deprecation (breaking change to happen in the future)
• Breaking change (fix/feature causing existing functionality to break)
• Code quality improvements to existing code or addition of tests

Additional information

• This PR fixes or closes issue: fixes #
• This PR is related to issue:
• Link to documentation pull request:

Checklist

• The code change is tested and works locally.
• Local tests pass. Your PR cannot be merged unless tests pass
• There is no commented out code in this PR.
• I have followed the development checklist
• The code has been formatted using Black (black --fast homeassistant tests)
• Tests have been added to verify that the new code works.

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

• Documentation added/updated for www.home-assistant.io

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

• The manifest file has all fields filled out correctly.
  Updated and included derived files by running: python3 -m script.hassfest.
• New or updated dependencies have been added to requirements_all.txt.
  Updated by running python3 -m script.gen_requirements_all.
• For the updated dependencies - a link to the changelog, or at minimum a diff between library versions is added to the PR description.
• Untested files have been added to .coveragerc.

To help with the load of incoming pull requests:

• I have reviewed two other open pull requests in this repository.

[elupus]

How is all these function pointers making it better? This change adds about 100 additional lines of code. I feel it would make sense to keep some logic in the entity classes and keep mostly constants in the entity descriptions.

[Kane610]

How is all these function pointers making it better? This change adds about 100 additional lines of code. I feel it would make sense to keep some logic in the entity classes and keep mostly constants in the entity descriptions.

Yes currently it's not better. This is just a small step on the way. But the client tracker should switch as well. After that it can be consolidated to using the entity.py. So once the small steps are completed it will be much less code overall.

[elupus]

I think this is okey since you are maintainer of this integration. But so far i fail to see how it's going to get simpler or more understandable with these changes.

[elupus]

This is default for an Entity, so not needed?

[Kane610]

Device tracker is special :)

[Kane610]

core/homeassistant/components/device_tracker/config_entry.py

Line 312 in cb37df6

def unique_id(self) -> str | None:

It overloads the normal unique_id method

[Kane610]

I think this is okey since you are maintainer of this integration. But so far i fail to see how it's going to get simpler or more understandable with these changes.

I hope to make it more consolidated over all, in the case of device tracker it has always been a bit cumbersome