Skip to content

Set Matter integration type to "hub" #157657

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Merged
balloob merged 1 commit into from
Dec 1, 2025
Merged

Set Matter integration type to "hub" #157657

balloob merged 1 commit into from
Dec 1, 2025

Conversation

@TheJulianJES
Copy link
Member

@TheJulianJES TheJulianJES commented Dec 1, 2025

Proposed change

This explicitly sets the integration type of Matter to "hub", allowing Matter devices to be included in device database submissions. This is something we should consider for including in 2025.12.0.

This is similar to Z-Wave JS, Hue, and other integrations.

The only possible downside this might have is that the UI now shows "Add hub", instead of "Add entry". This is already the case for Z-Wave JS and I think it's fine. For an example how it looks with the PR, see:
image

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 link to the changelog, or at minimum a diff between library versions is added to the PR description.

To help with the load of incoming pull requests:

Copilot AI review requested due to automatic review settings December 1, 2025 19:36
@TheJulianJES TheJulianJES requested a review from a team as a code owner December 1, 2025 19:36
@home-assistant
Copy link

home-assistant bot commented Dec 1, 2025

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

Code owner commands

Code owners of matter can trigger bot actions by commenting:

  • @home-assistant close Closes the pull request.
  • @home-assistant rename Awesome new title Renames the pull request.
  • @home-assistant reopen Reopen the pull request.
  • @home-assistant unassign matter Removes the current integration label and assignees on the pull request, add the integration domain after the command.
  • @home-assistant add-label needs-more-information Add a label (needs-more-information, problem in dependency, problem in custom component) to the pull request.
  • @home-assistant remove-label needs-more-information Remove a label (needs-more-information, problem in dependency, problem in custom component) on the pull request.

@TheJulianJES TheJulianJES added this to the 2025.12.0 milestone Dec 1, 2025
Copilot AI reviewed Dec 1, 2025
View reviewed changes
Copy link
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

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

Pull request overview

This PR sets the Matter integration type to "hub" in the manifest file, aligning it with similar integrations like Z-Wave JS and Philips Hue. This change enables Matter devices to be included in device database submissions while maintaining consistency with Home Assistant's categorization of hub-based integrations.

Key changes:

  • Added "integration_type": "hub" to the Matter integration manifest

@balloob balloob merged commit 1356eea into home-assistant:dev Dec 1, 2025
42 checks passed
frenck pushed a commit that referenced this pull request Dec 2, 2025
@TheJulianJES @frenck
Set Matter integration type to "hub" (#157657)
bd44402
@github-actions github-actions bot locked and limited conversation to collaborators Dec 3, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Reviewers

Copilot code review Copilot Copilot left review comments

@balloob balloob balloob approved these changes

Assignees

No one assigned

Labels

by-code-owner cherry-picked cla-signed code-quality integration: matter Quality Scale: No score small-pr PRs with less than 30 lines.

Projects

None yet

Milestone

2025.12.0

Development

Successfully merging this pull request may close these issues.

3 participants

@TheJulianJES @balloob @frenck