Use base EntityStateAttribute for device tracker coordinates

[epenet]

Breaking change

Proposed change

Follow-up to #174633 and #176119, which introduced the base EntityStateAttribute enum and moved latitude/longitude onto it.

TrackerEntity and the legacy device tracker write/read their coordinates through TrackerEntityStateAttribute.LATITUDE / TrackerEntityStateAttribute.LONGITUDE. Now that latitude/longitude live on the base enum, they are written/read through EntityStateAttribute.LATITUDE / EntityStateAttribute.LONGITUDE, and the platform-specific enum members are deprecated (via EnumWithDeprecatedMembers, breaking in 2027.2) in favour of the base enum. TrackerEntityStateAttribute.GPS_ACCURACY is unchanged.

• entity.py / legacy.py: write and restore-read coordinates via the base enum
• tesla_fleet/device_tracker.py: the one other core consumer of the deprecated members, migrated to the base enum
• const.py: deprecate TrackerEntityStateAttribute.LATITUDE / LONGITUDE

The device tracker .ambr snapshots are regenerated: the state-attribute dict keys switch from TrackerEntityStateAttribute.LATITUDE/LONGITUDE to EntityStateAttribute.LATITUDE/LONGITUDE (same string values).

No behaviour change: these enums are StrEnums, so the resolved keys are identical.

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:
• Link to developer documentation pull request:
• Link to frontend pull request:

Checklist

• I understand the code I am submitting and can explain how it works.
• 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
• I have followed the perfect PR recommendations
• The code has been formatted using Ruff (ruff format homeassistant tests)
• Tests have been added to verify that the new code works.
• Any generated code has been carefully reviewed for correctness and compliance with project standards.

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 diff between library versions and ideally a link to the changelog/release notes is added to the PR description.

To help with the load of incoming pull requests:

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

🤖 Generated with Claude Code

[Copilot]

Copilot was unable to review this pull request because the user who requested the review has reached their quota limit.

[epenet]

I'm not sure if we need to bother with deprecation...
They were only added in 2026.7 and I doubt many integrations have started using the new enum, but I've implemented anyway just in case.

[Copilot]

Copilot was unable to review this pull request because the user who requested the review has reached their quota limit.

[frenck]

Thanks, @epenet 👍

../Frenck

                       

Blogging my personal ramblings at frenck.dev