Add Roborock Q10 volume number entity

[tubededentifrice]

Proposed change

Adds the volume number entity for the Roborock Q10 (B01/ss07). Split out to one platform per PR as requested in #173883; switch (#175731, merged) and image (#173883) are separate PRs.

Mirrors the V1 volume number entity via a Q10-specific description (RoborockNumberDescriptionQ10 / RoborockNumberEntityQ10): reads api.volume from the push-updated trait (registering add_update_listener for state updates, like the merged Q10 select/button/switch entities), writes through set_volume, and reports unknown while the trait value is still None. Reuses the existing volume translation key. The test mock reuses the attach_update_listeners conftest helper introduced by the merged switch PR.

No dependency bump: targets the already-pinned python-roborock version.

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:

Sibling per-platform PRs from the same split: #175731 (switch, merged), #173883 (image).

Testing: new tests cover the set-value round trip (asserting the trait call and the listener-pushed state), unknown when the trait value is None, and the failure path asserting the translated error. Full tests/components/roborock suite passes locally (Python 3.14); ruff, mypy (strict) and hassfest clean.

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:

• Documentation added/updated for www.home-assistant.io

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:

• I have reviewed two other open pull requests in this repository.

[home-assistant]

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

Code owner commands

Code owners of roborock 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 roborock 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]

Pull request overview

This PR adds a volume number entity for the Roborock Q10 (B01/ss07) vacuum. It is part of a series of PRs (one platform per PR) that add Q10 support, following the pattern of the already-merged Q10 select/button/DND entities. The new entity reads api.volume from a push-updated trait, registers an add_update_listener for state updates, writes through set_volume, and reports unknown while the trait value is None.

Changes:

• Adds RoborockNumberDescriptionQ10 / RoborockNumberEntityQ10 (a coordinated Q10 entity) that mirrors the V1 volume number entity and reuses the existing volume translation key.
• Refactors async_add_coordinator_entities into an if/elif isinstance branch structure (matching select.py) to support both V1 and Q10 coordinators.
• Adds test fixture wiring for the Q10 volume trait plus tests for set round-trip, unknown value, and failure path.

Reviewed changes

Copilot reviewed 3 out of 3 changed files in this pull request and generated no comments.

File	Description
homeassistant/components/roborock/number.py	Adds Q10 number description/entity and branches entity setup by coordinator type, consistent with select.py and merged Q10 entities.
tests/components/roborock/conftest.py	Adds a mocked volume trait with add_update_listener/set_volume side effects, mirroring the existing DND listener fixture.
tests/components/roborock/test_number.py	Adds Q10 tests for set round-trip (with listener push), unknown value, and translated failure path.

I verified the imports (Q10PropertiesApi, SoundVolumeTrait, RoborockB01Q10UpdateCoordinator, RoborockCoordinatedEntityB01Q10) resolve and match usage in switch.py/coordinator.py, the setup refactor matches the established select.py pattern, the add_update_listener registration is symmetrical via async_on_remove, the update_options_failed translation key exists (strings.json:711), and the tests follow the conventions of the existing V1 tests in the same file. No objective issues were found.

[joostlek]

There are merge conflicts

[home-assistant]

Please take a look at the requested changes, and use the Ready for review button when you are done, thanks 👍

Learn more about our pull request process.

[Copilot]

Pull request overview

Copilot reviewed 3 out of 3 changed files in this pull request and generated no new comments.

[tubededentifrice]

@joostlek thanks, fixed

[Copilot]

Pull request overview

Copilot reviewed 3 out of 3 changed files in this pull request and generated 4 comments.

[Copilot]

Pull request overview

Copilot reviewed 3 out of 3 changed files in this pull request and generated no new comments.

[allenporter]

Nice work @tubededentifrice

Merge conflict has been resolved