Skip to content

Adapt drop_connect to set via_device_id in DeviceInfo - #178104

Merged
emontnemery merged 3 commits into
devfrom
drop_connect_via_device_id
Aug 4, 2026
Merged

Adapt drop_connect to set via_device_id in DeviceInfo#178104
emontnemery merged 3 commits into
devfrom
drop_connect_via_device_id

Conversation

@emontnemery

Copy link
Copy Markdown
Contributor

Proposed change

Adapt drop_connect to set via_device_id in DeviceInfo

The via_device_id is best effort because the linked device may be created by another config entry.
In a follow-up PR, the solution can be improved to for example update the device if the expected via device is created.

Context in https://developers.home-assistant.io/blog/2026/07/21/device-registry-single-config-entry/

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:

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:

@emontnemery emontnemery added this to the 2026.8.0 milestone Aug 3, 2026
Copilot AI balanced review requested due to automatic review settings August 3, 2026 17:20
@home-assistant

home-assistant Bot commented Aug 3, 2026

Copy link
Copy Markdown
Contributor

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

Code owner commands

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

Updates DROP child devices to reference an existing owner hub by device ID.

Changes:

  • Looks up the owner hub during entity initialization.
  • Sets via_device_id when the hub is available.
  • Missing test coverage for successful linking.

Comment on lines +51 to +52
if via_device is not None:
self._attr_device_info["via_device_id"] = via_device.id
Comment thread homeassistant/components/drop_connect/entity.py Outdated
@MartinHjelmare
MartinHjelmare marked this pull request as draft August 3, 2026 18:59
Copilot AI review requested due to automatic review settings August 3, 2026 19:08
@emontnemery
emontnemery marked this pull request as ready for review August 3, 2026 19:11

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 2 out of 2 changed files in this pull request and generated no new comments.

Comment thread homeassistant/components/drop_connect/entity.py
@emontnemery
emontnemery marked this pull request as draft August 3, 2026 21:17
Comment thread homeassistant/components/drop_connect/entity.py Outdated
Copilot AI review requested due to automatic review settings August 4, 2026 06:44

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 2 out of 2 changed files in this pull request and generated no new comments.

Suppressed comments (1)

homeassistant/components/drop_connect/entity.py:54

  • Resolve the owner config entry first and scope the identifier lookup to it. async_get_devices() returns matches in config-entry insertion order; after a shared device is split, several devices can retain this identifier, so [0] can link the child to the wrong split even when the actual hub exists. DROP config-entry unique IDs use this owner ID (config_flow.py:54-55), allowing an exact lookup.
            via_devices = dr.async_get(coordinator.hass).async_get_devices(
                identifiers={(DOMAIN, entry_data[CONF_DEVICE_OWNER_ID])}
            )
            if via_devices:
                self._attr_device_info["via_device_id"] = via_devices[0].id

@emontnemery
emontnemery marked this pull request as ready for review August 4, 2026 07:57
@emontnemery
emontnemery merged commit 1ec48f8 into dev Aug 4, 2026
34 checks passed
@emontnemery
emontnemery deleted the drop_connect_via_device_id branch August 4, 2026 07:57
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.

4 participants