Update python-roborock to 4.26.3

[lboue]

Proposed change

v4.26.3 (2026-03-22) — Bug fixes only, via PR #793:

YXDeviceState (Q10) — status name normalization: enum string values were non-standard with concatenated "state" suffixes. They are replaced with canonical values consistent with the rest of the library:

Enum	Before	After
SLEEP_STATE	"sleepstate"	"sleeping"
STANDBY_STATE	"standbystate"	"standby"
CLEANING_STATE	"cleaningstate"	"cleaning"
TO_CHARGE_STATE	"tochargestate"	"going_to_charge"
REMOTEING_STATE	"remoteingstate"	"remote_control"
CHARGING_STATE	"chargingstate"	"charging"
PAUSE_STATE	"pausestate"	"paused"
FAULT_STATE	"faultstate"	"fault"
UPGRADE_STATE	"upgradestate"	"updating"
CREATING_MAP_STATE	"creatingmapstate"	"creating_map"
MAP_SAVE_STATE	"mapsavestate"	"saving_map"
RE_LOCATION_STATE	"relocationstate"	"relocating"
ROBOT_SWEEPING	"robotsweeping"	"sweeping"
ROBOT_MOPING	"robotmoping"	"mopping"
ROBOT_SWEEP_AND_MOPING	"robotsweepandmoping"	"sweep_and_mop"
ROBOT_TRANSITIONING	"robottransitioning"	"transitioning"
ROBOT_WAIT_CHARGE	"robotwaitcharge"	"waiting_to_charge"

Changes: Python-roborock/python-roborock@v4.26.2...v4.26.3
Changelog: https://github.com/Python-roborock/python-roborock/blob/main/CHANGELOG.md

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:

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

Updates the Roborock integration to use python-roborock 4.26.3

Changes:

• Bump python-roborock from 4.26.2 to 4.26.3 across manifest and requirements lock files.

Reviewed changes

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

Show a summary per file

File	Description
homeassistant/components/roborock/manifest.json	Pins python-roborock to 4.26.3 for the integration.
requirements_all.txt	Updates global pinned dependency to 4.26.3.
requirements_test_all.txt	Updates test dependency set to 4.26.3.

[Copilot]

Pull request overview

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

[lboue]

Ready now

[frenck]

I can't cleanly merge this into the current stable branches and thus removed it from the milestone. Will be part of Home Assistant 2026.4 instead.