8000 Matter add Service Area Cluster to vacuum_cleaner fixture by lboue · Pull Request #145743 · home-assistant/core · GitHub
[go: up one dir, main page]

Skip to content

Matter add Service Area Cluster to vacuum_cleaner fixture #145743

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.

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

Open
wants to merge 1 commit into
base: dev
Choose a base branch
from

Conversation

lboue
Copy link
Contributor
@lboue lboue commented May 27, 2025

Proposed change

Matter add Service Area Cluster to vacuum_cleaner fixture

1.17.6.1. SupportedAreas Attribute
This attribute SHALL contain the list of areas that can be included in the SelectedAreas attribute’s list. Each item in this list represents a unique area, as indicated by the AreaID field of AreaStruct.
Each entry in this list SHALL have a unique value for the AreaID field.
If the SupportedMaps attribute is not empty, each entry in this list SHALL have a unique value for the combination of the MapID and AreaInfo fields.
If the SupportedMaps attribute is empty, each entry in this list SHALL have a unique value for the AreaInfo field and SHALL have the MapID field set to null

1.17.6.3. SelectedAreas Attribute
This attribute SHALL indicate the set of areas where the device SHOULD attempt to operate.
The mobile devices MAY travel without operating across any areas while attempting to reach the areas indicated by the SelectedAreas attribute. For example, a robotic vacuum cleaner MAY drive without cleaning when traveling without operating.

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

  • 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.

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:

Service Area Cluster
@home-assistant
Copy link

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.

@lboue lboue marked this pull request as ready for review May 27, 2025 20:23
@lboue lboue requested a review from a team as a code owner May 27, 2025 20:23
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.

1 participant
0