Skip to content

Extract shared base entity for Subaru#176246

Open
jpettitt wants to merge 3 commits into
home-assistant:devfrom
jpettitt:subaru-base-entity
Open

Extract shared base entity for Subaru#176246
jpettitt wants to merge 3 commits into
home-assistant:devfrom
jpettitt:subaru-base-entity

Conversation

@jpettitt

@jpettitt jpettitt commented Jul 10, 2026

Copy link
Copy Markdown
Contributor

Proposed change

Closes common-modules (#172844, shape approved by @joostlek: two base classes, since button/lock aren't CoordinatorEntity-backed).

Extracts the device-info/unique-id/has_entity_name/availability boilerplate that was duplicated across sensor.py, button.py, lock.py, and device_tracker.py into a new entity.py (SubaruEntity + SubaruCoordinatorEntity). Pure refactor, no behavior change.

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

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:

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:

Owns device_info, unique_id, and has_entity_name so every platform
doesn't repeat the boilerplate. Two base classes since button/lock
aren't coordinator-backed: SubaruEntity (device_info/unique_id/
has_entity_name) and SubaruCoordinatorEntity (adds the coordinator
polling lifecycle and availability gating on top).

Adopted by sensor, button, lock, and device_tracker. Pure refactor,
no behavior change.

Closes home-assistant#172844.
@home-assistant

Copy link
Copy Markdown
Contributor

Hey there @G-Two, mind taking a look at this pull request as it has been labeled with an integration (subaru) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of subaru can trigger bot actions by commenting:

  • @home-assistant close Closes the pull request.
  • @home-assistant mark-draft Mark the pull request as draft.
  • @home-assistant ready-for-review Remove the draft status from the pull request.
  • @home-assistant rename Awesome new title Renames the pull request.
  • @home-assistant reopen Reopen the pull request.
  • @home-assistant unassign subaru Removes the current integration label and assignees on the pull request, add the integration domain after the command.
  • @home-assistant update-branch Update the pull request branch with the base branch.
  • @home-assistant add-label needs-more-information Add a label (needs-more-information, problem in dependency, problem in custom component, problem in config, problem in device, feature-request) to the pull request.
  • @home-assistant remove-label needs-more-information Remove a label (needs-more-information, problem in dependency, problem in custom component, problem in config, problem in device, feature-request) on the pull request.

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Extracts shared Subaru entity initialization and availability behavior into reusable base classes.

Changes:

  • Adds base entity classes.
  • Migrates four Subaru entity platforms.
  • Preserves platform-specific tracker availability logic.

Reviewed changes

Copilot reviewed 5 out of 5 changed files in this pull request and generated 2 comments.

Show a summary per file
File Description
button.py Uses SubaruEntity.
device_tracker.py Uses coordinator base entity.
entity.py Adds shared base classes.
lock.py Uses SubaruEntity.
sensor.py Uses coordinator base entity.

Comment thread homeassistant/components/subaru/entity.py
Comment thread homeassistant/components/subaru/device_tracker.py Outdated
Availability is gated on the relevant status keys being present, not
on their values being non-None (test_device_tracker_none_data covers
this) -- the previous wording overstated the guarantee.
Copilot AI review requested due to automatic review settings July 10, 2026 23:49

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Copilot reviewed 5 out of 5 changed files in this pull request and generated no new comments.

@jpettitt jpettitt marked this pull request as ready for review July 10, 2026 23:56
Copilot AI review requested due to automatic review settings July 13, 2026 23:25

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Copilot reviewed 5 out of 5 changed files in this pull request and generated no new comments.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants