Skip to content

Clear stale restored entity names in bluetooth passive update processor - #177647

Closed
piitaya wants to merge 2 commits into
devfrom
bluetooth_clear_stale_entity_names
Closed

piitaya wants to merge 2 commits into
devfrom
bluetooth_clear_stale_entity_names

Conversation

@piitaya

@piitaya piitaya commented Jul 30, 2026

Copy link
Copy Markdown
Member

Proposed change

Integrations that migrated to translated entity names pass entity_names={} (BTHome #156060, OralB #97402, Bluemaestro #102424). However, names persisted before the migration are restored from storage at startup, and PassiveBluetoothDataUpdate.update() only merges incoming mappings, so those entities keep the old hardcoded English names forever on existing installations.

Clear the stored name for updated keys when an update provides no names at all, which is the signature of the entity_names={} pattern. Updates that name some entities keep the current merge behavior, so partial updates (multi-packet devices) and integrations that rely on previously sent names are unaffected. The cleared names are persisted, and entities pick up the translated names on the next restart.

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: Add entity translations to Govee BLE #177644
  • 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:

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:

Copilot AI review requested due to automatic review settings July 30, 2026 13:24
@piitaya
piitaya requested a review from bdraco as a code owner July 30, 2026 13:24
@home-assistant home-assistant Bot added bugfix cla-signed has-tests integration: bluetooth small-pr PRs with less than 30 lines. Top 100 Integration is ranked within the top 100 by usage Top 200 Integration is ranked within the top 200 by usage Top 50 Integration is ranked within the top 50 by usage labels Jul 30, 2026
@home-assistant

Copy link
Copy Markdown
Contributor

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

Code owner commands

Code owners of bluetooth 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 bluetooth 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

Clears stale restored Bluetooth entity names so translated names apply after restart.

Changes:

  • Clears stored names for keys updated without names.
  • Adds tests for clearing, repeat updates, and partial naming.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 1 comment.

File Description
homeassistant/components/bluetooth/passive_update_processor.py Adds stale-name clearing logic.
tests/components/bluetooth/test_passive_update_processor.py Tests name update behavior.

Comment on lines +172 to +175
if not new_data.entity_names:
for key in (
new_data.entity_data.keys() | new_data.entity_descriptions.keys()
):
@piitaya

piitaya commented Jul 30, 2026

Copy link
Copy Markdown
Member Author

Closing in favor of sending explicit None entries from the integration, see #177644.

@piitaya piitaya closed this Jul 30, 2026
@github-actions github-actions Bot locked and limited conversation to collaborators Jul 31, 2026
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

bugfix cla-signed has-tests integration: bluetooth Quality Scale: internal small-pr PRs with less than 30 lines. Top 50 Integration is ranked within the top 50 by usage Top 100 Integration is ranked within the top 100 by usage Top 200 Integration is ranked within the top 200 by usage

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants