Roborock mop modes are not fully translated (deep-plus_pearl)

[jamespreedy]

The problem

Hi folks. I thought I'd previously raised a bug report for this one, but I couldn't see it.
Apologies if I managed to dupe another known bug.

In the "Mop Mode" entity for my S8 Max V Ultra, I have a number of choices in the dropdown. They are all in plain English for example "Deep" or "Custom".

I think one of these was missed as it also shows a placeholder "deep-plus_pearl" - see screenshot.
Thanks in advance, happy to provide additional logs etc if it would help. 🫡

What version of Home Assistant Core has the issue?

2026.1.1

What was the last working version of Home Assistant Core?

No response

What type of installation are you running?

Home Assistant OS

Integration causing the issue

roborock

Link to integration documentation on our website

https://www.home-assistant.io/integrations/roborock/

Diagnostics information

config_entry-roborock-01KBZN50YR0RXBEG7GXGA2RB82.json

Example YAML snippet

Anything in the logs that might be useful for us?

Additional information

[home-assistant]

Hey there @Lash-L, @allenporter, mind taking a look at this issue 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 issue.
• @home-assistant rename Awesome new title Renames the issue.
• @home-assistant reopen Reopen the issue.
• @home-assistant unassign roborock Removes the current integration label and assignees on the issue, 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 issue.
• @home-assistant remove-label needs-more-information Remove a label (needs-more-information, problem in dependency, problem in custom component) on the issue.

_{^{(message by CodeOwnersMention)}}

---

roborock documentation
roborock source
_{^{(message by IssueLinks)}}

[allenporter]

Thank you for the detailed report.

One question may be: what setting this internal name map to in the Roborock App? If you happen to know from the roborock app what the actual set of mop modes shown are that could be helpful to know what to call this. My assumption is that pearl is a device specific code. I'm not sure if this means it overrides the existing deep+ or if it has another special name (e.g. "Deep+ Turbo" -- i made that up but you get the diea)

[jamespreedy]

@allenporter ... no, thank you for your help! lol 🍺

I've included some screenshots below showing the interface in the app for you.
I've then tried to match them all up for you too - see the table below.

Few thoughts.

• There are a few minor differences in the descriptions - would it be possible to align to the Roborock app / branding?
  • for example, MAX+ vs Max plus etc.
  • I've put suggestions below.
• HASS has one extra option under Mop Intensity that isn't in the app.
  • I'm assuming that HASS "Custom" matches the "Customize" tab in the app.
  • If that's the case, then "Custom water flow" in HASS doesn't seem to have a match in the Roborock App.
• Whilst testing, I discovered that "deep_plus_pearl" doesn't work anyway - there is an error - screenshot below.
  • Error while calling "SET_MOP_MODE"
  • Appreciate this is the option that got me to raise this bug ... would suggest we give up and remove it?

Thank youuuuu

Logger: homeassistant.components.websocket_api.http.connection
Source: components/websocket_api/commands.py:331
integration: Home Assistant WebSocket API (documentation, issues)
First occurred: 2:51:33 pm (4 occurrences)
Last logged: 3:27:02 pm

[140036100171840] Error during service call to select.select_option: Error while calling SET_MOP_MODE

[Lash-L]

This will be better nailed down when I finalize: Python-roborock/python-roborock#611

Previously, we relied entirely on user reports for what their specific vacuum supported and what the underlying ids were. The hope with this change is that we should be able to do it all automatically and dynamically determine cleaning mode support.

The problem of the missing translation is separate from this though - but it seems like the problem (for you) isn't that it isn't translated, but that it exists when it should not for your vac)

[allenporter]

I believe this has been resolved since Lash-L 's fix to use mop_route_options to get the list of mop modes is now in place, and it uses the dynamic device details. Closing.

[jamespreedy]

@allenporter - confirmed fixed, thank you very much!