Skip to content

chore: add Qrevo S Pro device data - #1052

Open
lacroixdavid1 wants to merge 1 commit into
Python-roborock:mainfrom
lacroixdavid1:add-qrevo-s-pro-device-data
Open

lacroixdavid1 wants to merge 1 commit into
Python-roborock:mainfrom
lacroixdavid1:add-qrevo-s-pro-device-data

Conversation

@lacroixdavid1

Copy link
Copy Markdown

Adds the device_info.yaml entry for the Qrevo S Pro (roborock.vacuum.a326), which the catalogue does not have yet.

  • Source: the Home Assistant diagnostics of my robot (Home Assistant 2026.11.1, python-roborock 7.12.0, robot firmware 02.49.24).
  • How it was built: I did not run the CLI. A small script took the fields roborock get-device-info --diagnostic-file reads, in the same order, and dumped them the same way (yaml.safe_dump(sort_keys=False)). Re-dumping the 16 existing entries that way gives each of them back byte for byte. The entry is appended at the end of the file, as in chore: add Saros 10R device info #1031.
  • product.name is **REDACTED** because the diagnostics redact it. Home Assistant shows the robot as "Qrevo S Pro Series".
  • product_nickname is Unknown, which is what main gives this model today. feat: add V1 product nicknames for models that fall back to PEARLPLUS #1046 maps a325/a326 to PEARLEH; I can update the line here if that lands first.
  • The schema is the Qrevo 2 Pro's (a294) without data point 143, and with a plain "0" to "9" range on 138 (clean_task_type).

Only device_info.yaml changes. SUPPORTED_FEATURES.md is not regenerated here, as in #1028 and #1031.

Done with AI assistance.

🤖 Generated with Claude Code

https://claude.ai/code/session_01MDuicnBiqDx6Yc8hyG6p1o

Add the device_info.yaml entry for the Qrevo S Pro (roborock.vacuum.a326),
built from the Home Assistant diagnostics of a robot on firmware 02.49.24.

Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01MDuicnBiqDx6Yc8hyG6p1o
@Lash-L Lash-L added Small PR Small pull request (<200 lines) Data model changes Changes to data models, device info, or feature mappings V1 V1 platform labels Nov 18, 2026

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Data model changes Changes to data models, device info, or feature mappings Small PR Small pull request (<200 lines) V1 V1 platform

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants