L10s Ultra, Error: Remove mop

[pannal]

Describe the bug The vacuum seems fine, but in HA it shows an exclamation mark beside it, and in its attribute theres "Error: Remove mop". No mention of this inside the Mi Home app.

To Reproduce Use the vacuum.

Expected behavior Normal operation

Screenshots

Additional Information (please complete the following information)

• Model Name [e.g. dreame.vacuum.p2028]: dreame.vacuum.r2228o
• Firmware Version [e.g. 1156]: 4.3.3_2303
• Home Assistant Version: 2023.5.2
• Configuration Type [With or without map support]: With
• Errors or warnings shown in the HA logs (if applicable): None

[Tasshack]

Vacuum actually generates that error but it think app ignores it. I can add exception to this error code for vacuums with self cleaning feature. Can you try to remove the mop pads and re attach them to check error is cleared or not?

[pannal]

Yep, seems fine now. Weird.

Do you know what it thinks is happening? I've seen it "lose" its mop pads and not complain before.

[Tasshack]

This is an error that happens on the vacuums without self wash base. On my Z10 Pro, app notifies you to remove the mop pad after mopping is completed using this error code.

[Tasshack]

I think L10s and L10s Ultra uses the same firmware and that explains this issue.

[pannal]

Ah and Mi Home just ignores that error for vacuums with self-cleaning? What a solution :D

[pannal]

Yeah, it'd be great if we could ignore this with L10s!

Thank you so much for this integration.

[Tasshack]

There are tons of solutions and patches in the app like this, you wouldn't believe it.

For example app detects that base has an external water outlet by trying to dump the water after first installation. If vacuum gives an error code after the dump command, that means vacuum does not have that feature and app stores the result on phone storage to disable that button in the future.

[pannal]

Interesting.

BTW/Off-Topic: Is there a reason why the "wash-mop-after-X-m²" is so limited in this integration vs. the options in the app?

[Tasshack]

Interesting.

BTW/Off-Topic: Is there a reason why the "wash-mop-after-X-m²" is so limited in this integration vs. the options in the app?

Mijia branded version of the same vacuums does not allow you to set an exact number from the app. If i allow you to set any number from this integration, mijia app cannot show that value because it was not included on the dropdown menu in the app.

[pannal]

Oh, so this vacuum can be added to the Mijia app as well? They're not even trying to hide their multi-brand-setup :D

Edit: Anyway, thank you for looking into this. Ignoring the error for the L10s would be great, but no show-stopper. You can close this if you want.

[Tasshack]

Oh, so this vacuum can be added to the Mijia app as well? They're not even trying to hide their multi-brand-setup :D

No, there is a vacuum that has exactly same hardware with your device but with a mijia logo on it and it has completly different ui inside the Mi Home App.

Even it is a same hardware and firmware, mijia users cannot set an exact number for that value bacuse of the user interface difference.

[pannal]

Oh, so a special case for the Dreame branded L10s would be possible?

[Tasshack]

I don't want to add specific rules for different model or brand versions (there are so many) of the same robot. I can only add custom rules for features like self-washing which does not requires you to know the robots model number to detect.

[pannal]

It seems like this issue is permanent - it shows the remove mop error after every cleaning cycle with active mops.

[Tasshack]

https://github.com/Tasshack/dreame-vacuum/releases/tag/v2.0.0b5