Skip to content

Add via_device permutations to kitchen_sink - #179049

Open
emontnemery wants to merge 2 commits into
devfrom
kitchen-sink-via-device
Open

Add via_device permutations to kitchen_sink#179049
emontnemery wants to merge 2 commits into
devfrom
kitchen-sink-via-device

Conversation

@emontnemery

Copy link
Copy Markdown
Contributor

Proposed change

Add via_device permutations to kitchen_sink

Draft, to be rebased after the child device PR is merged

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:

@home-assistant

Copy link
Copy Markdown
Contributor

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

Code owner commands

Code owners of kitchen_sink 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 kitchen_sink 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.

Base automatically changed from child-devices to dev August 13, 2026 11:53
Copilot AI balanced review requested due to automatic review settings August 14, 2026 06:24
@emontnemery
emontnemery force-pushed the kitchen-sink-via-device branch from a6db662 to c1aa9f9 Compare August 14, 2026 06:24
@emontnemery
emontnemery marked this pull request as ready for review August 14, 2026 06:24
@emontnemery
emontnemery requested a review from a team as a code owner August 14, 2026 06:24

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

Adds via_device_id relationship permutations to the kitchen sink switch platform and verifies their device-registry hierarchy.

Changes:

  • Adds hub-linked switch and power-strip devices.
  • Supports via_device_id in shared device creation and DemoSwitch.
  • Tests via-device and child-device relationships.

Reviewed changes

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

File Description
homeassistant/components/kitchen_sink/device.py Supports creating devices with a via-device ID.
homeassistant/components/kitchen_sink/switch.py Adds hub-linked device permutations.
tests/components/kitchen_sink/test_switch.py Verifies the resulting device hierarchy.
Suppressed comments (1)

homeassistant/components/kitchen_sink/switch.py:39

  • Remove this comment because it narrates the two device registrations and child entities that immediately follow.
    # A second hub with a power strip linked to it via its via device; the power
    # strip in turn has its own child devices (outlets).

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

hass, (DOMAIN, "2_ch_power_strip"), config_entry_id=config_entry.entry_id
)

# A hub with a switch device linked to it via its via device.
Copilot AI review requested due to automatic review settings August 21, 2026 14:10

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 3 out of 3 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.

3 participants