L20 ultra changes to swipping mode during washing task

[s2kta4]

When starting a washing and swipping session, after the robot comes back to wash itself, 15sqm, it changes mode to swipping and leaves the mops in the docking. To Reproduce Start mopping and swipping full clean

Expected behavior The cleaning mode should remain the same for the entire session and not change by itself during the task

l20 ultra with the latest beta version

[Tasshack]

@s2kta4 @Aculoff Only thing that the integration force to switch to the sweeping is mop pads being detached. All of the devices including that has a water tank without wash base are using the same property for checking the mop/tank has been installed. I think Dreame had made changes about detection of the mop pads being attached on a recent firmware thats why integration thinks that mop pads are not installed and updates settings according to it. This will also explain the issue of https://github.com/Tasshack/dreame-vacuum/issues/517.

Only problem is, I dont have necessary information to understand what is actually happening and how to fix it so I need a log when the issue happens. What I need from you to enable the info logs, restart HA, reproduce the issue and send me the log output of HA so I can see which property changes to what that causes cleaning mode changed to be sweeping.

logger:
  default: warn
  logs:
    custom_components.dreame_vacuum: info

[s2kta4]

Thank you for your response. As I'm not home for the next couple of days I won't be able to reproduce. but one question though, why doest the addon ever change the mode by itself. it seems very counter intuitive to me that there will be a situation that it needs to happen.

[Tasshack]

@s2kta4 you may have not noticed this but the integration supports more than 100 different models in 3 different brands produced over past 4 years. So please keep in mind that not every robot has mop pad lifting feature or even self wash base and integration must accomodate all of the capabilities unlike the app plugin which is tailor made to support several models of same generation at the same time.

[Tasshack]

Older devices that has mop unmounting feature like X10 does not remember that the mops are left at the base so its app does not allow you to set cleaning mode to mopping even mop pads has removed from itself and left at the base. To fix that Dreame has added a new property to check mop pads has removed by the robot or the user to enable/disable sweeping cleaning modes on latest generation devices like L20 and X30. That new property wasn't working properly and the app still wasn't allowing you to set mopping cleaning modes when mops pads not attached but I guess they have tried to fixed that on the latest firmware and it affected the mop pad state property that the integration checks currently. I think latest version of the app plugin only checks the new property to confim mop pads are attached or left at the base and ignores the mop pad state property that the integration uses for all Dreame devices.

[Tasshack]

@s2kta4 @Aculoff still waiting more info about the issue.

[Aculoff]

@Tasshack I tried to delete all the log entries before I started the cleaning process, so hopefully it helps!

[Tasshack]

Looks like WATER_TANK changes to 10 when vacuum has left the dock but integration does not know what 10 means right know so I need to check this from the app source code and implement it to the integration accordingly.

2024-05-23 18:49:40.397 INFO (Thread-3 (_thread_main)) [custom_components.dreame_vacuum.dreame.device] Property WATER_TANK Changed: 1 -> 10
2024-05-23 18:49:40.398 INFO (Thread-3 (_thread_main)) [custom_components.dreame_vacuum.dreame.device] Property MOP_PAD_INSTALLED Changed: 0 -> 1

This is the part when integration changes the cleaning mode to sweeping.

2024-05-23 18:49:40.679 INFO (Thread-3 (_thread_main)) [custom_components.dreame_vacuum.dreame.device] Update Property: CLEANING_MODE: 200448 -> 200450

[thoml95]

Looks like WATER_TANK changes to 10 when vacuum has left the dock but integration does not know what 10 means right know so I need to check this from the app source code and implement it to the integration accordingly.

2024-05-23 18:49:40.397 INFO (Thread-3 (_thread_main)) [custom_components.dreame_vacuum.dreame.device] Property WATER_TANK Changed: 1 -> 10
2024-05-23 18:49:40.398 INFO (Thread-3 (_thread_main)) [custom_components.dreame_vacuum.dreame.device] Property MOP_PAD_INSTALLED Changed: 0 -> 1

I have the same problem, or at least similar. Yesterday my L20 Ultra decided that he needs mop cleaning after only 3m2 and changed to only sweeping. But my water tank never switched to „10“.

2024-05-25 15:23:41.632 INFO (Thread-2 (_thread_main)) [custom_components.dreame_vacuum.dreame.device] Property WATER_TANK Changed: 1 -> 0
2024-05-25 15:23:41.633 INFO (Thread-2 (_thread_main)) [custom_components.dreame_vacuum.dreame.device] Property MOP_PAD_INSTALLED Changed: 0 -> 1
2024-05-25 15:23:41.815 INFO (Thread-2 (_thread_main)) [custom_components.dreame_vacuum.dreame.device] Update Property: CLEANING_MODE: 200448 -> 200450
2024-05-25 15:23:42.632 INFO (Thread-2 (_thread_main)) [custom_components.dreame_vacuum.dreame.device] Property MOP_PAD_INSTALLED Changed: 1 -> 0 

Edit: Today the Robot returned to the base to self clean and left it with the pads on and started cleaning again. After a few seconds he returned again to the base and left the pads there.

v2.0.0b14

[Tasshack]

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

[Aculoff]

Today I upgraded to the new version, but the problem occurs again. Is there anything I need to change?

[Tasshack]

@Aculoff as always before I need the info logs. Telling that only the problem is happened again is no useful for me or anyone.

[Aculoff]

@Tasshack My question simply referred to whether the vacuum might need to be set up again or differently. But according to your answer, apparently not. Unfortunately, I won't be home for the next few days, so I won't be able to upload the logs until then

[Tasshack]

@Aculoff I cannot event confirm that you have successfully upgraded the integration or not even without seeing the logs.

[Aculoff]

@Tasshack These are the latest logs. This time it switched to sweeping when the L20 was still in its base.

[Tasshack]

@Aculoff thanks for the log. I think I have understood the problem now and it should be fixed on the next release.

[s2kta4]

The issue now has returned. not able to mop with the add on enabled. in order to mop I have to disable it from ha

[Tasshack]

Fixed on the latest Beta release. https://github.com/Tasshack/dreame-vacuum/releases/tag/v2.0.0b16