Why does the robot clean the wrong mop pad before cleaning even starts?

Every time a cleaning starts, the robot first cleans the mop pad that is currently attached, even when that pad is not the one it will actually use. Then it switches to the mop pad that is really needed, cleans that one as well, and only then starts cleaning the room. The first mop pad was cleaned for no reason and is never even used.

There is nothing intelligent about this process. It wastes time, water, and cleaning solution for absolutely no benefit.

What makes this even worse is that Dreame advertises “intelligent recognition” for when mop pads need to be cleaned. If that feature really works, why is the robot cleaning a mop pad it does not even use afterward? That is contradictory.

Where can this be disabled? And if it cannot be disabled, why not? This behavior should be fixed. The robot should skip unnecessary mop cleaning and only clean the pad that is actually needed.

If others have noticed the same issue, please reply here so Dreame can see this is not an isolated complaint.

EDIT: Matrix10 Ultra

ÜbersetzenOriginal anzeigen

Are you talking about the Matrix10? He doesn't do that with me, here he first switches to the mop he needs, then he washes it.

Hello，Thank you very much for your detailed feedback and for sharing your observations. We understand why the mop washing process may feel excessive from a user’s perspective, and we appreciate the opportunity to explain the current logic.
The mop washing behavior you are seeing is based on the following design principles:

When a cleaning task starts, the robot will wash the mop pad once to ensure it begins with a clean mop.
Between different cleaning areas, the robot will wash the mop pad to avoid spreading dirt from one zone to another.
If different areas are assigned different mop pads, the robot will wash the previously used mop pad once and then wash the newly selected mop pad once before continuing.
During a single task, when the predefined cleaning area threshold is reached, the robot will return to wash the mop pad automatically.
If a floor care / floor maintenance function is enabled, the robot will mop the floor first and then perform the floor care process, which may result in the same area triggering multiple mop washing cycles.

Because these software rules are combined, the mop washing frequency can appear higher, even though each wash is triggered by a specific logic intended to maintain cleaning performance and hygiene.
In addition, the intelligent mop washing feature works by dynamically adjusting the washing duration, water volume, and water temperature based on the cleaning environment, in order to ensure optimal mop cleaning results. This means the system prioritizes cleaning effectiveness rather than minimizing the number of wash cycles.
That said, we fully understand your concerns regarding efficiency, water usage, and user control. Your feedback about unnecessary mop washing and the desire for more flexible behavior has been noted, and we will forward it to the relevant product and development teams for further evaluation and improvement.
Thank you again for taking the time to share your thoughts with us. User feedback like yours is very valuable and helps us continue to optimize the product experience.

No you didn't understand. The following is happening...
Here is an example:

- Dreame Matrix10 Ultra docked in the Basestation attached with Mop-Pad A.
- I sent it to clean the kitchen ONLY.
- Dreame Robot starts cleaning the attached Mop-Pad A FOR NO REASON. Switches to Mop-Pad C and starts cleaning Mop-Pad C. Goes to the kitchen, does its job, returns and cleans Mop-Pad C.

Why was Mop-Pad A cleaned in the first place?!