core icon indicating copy to clipboard operation
core copied to clipboard

Roborock ignoring Mop_Intensity setting

Open szavoda opened this issue 1 year ago • 4 comments

The problem

I have gotten to the following automation that others had claims was working when they wrote about it about a year ago. I am attempting to do a vacuum only action by setting the mop_intensity to "off". If I look that the entity, it is set to "off". The delay is to help prevent a race condition - not sure if that was needed, but others had it, so I thought it would not hurt. Here is the automation yaml:

What version of Home Assistant Core has the issue?

core-2024.9.1

What was the last working version of Home Assistant Core?

No response

What type of installation are you running?

Home Assistant Container

Integration causing the issue

Roborock

Link to integration documentation on our website

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

Diagnostics information

No response

Example YAML snippet

alias: Vacuum When Litter Cleaned
description: ""
trigger:
  - platform: device
    device_id: abf4521984025697e4a71059f981ce00
    domain: vacuum
    entity_id: 4bfc36c8d725f0b8a64568fad1a986e5
    type: cleaning
condition:
  - condition: time
    after: "06:00:00"
    before: "22:00:00"
    weekday:
      - sun
      - mon
      - tue
      - wed
      - thu
      - fri
      - sat
action:
  - action: select.select_option
    data:
      option: "off"
    target:
      entity_id: select.roborock_qrevo_master_mop_intensity
  - delay:
      hours: 0
      minutes: 0
      seconds: 15
      milliseconds: 0
  - action: vacuum.send_command
    metadata: {}
    data:
      command: app_segment_clean
      params:
        - segments:
            - 24
          repeat: 1
    target:
      entity_id: vacuum.roborock_qrevo_master
mode: single

Anything in the logs that might be useful for us?

No response

Additional information

No response

szavoda avatar Sep 16 '24 16:09 szavoda

Hey there @lash-l, 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)

home-assistant[bot] avatar Sep 16 '24 16:09 home-assistant[bot]

Might be relevant: in my logs (also QRevo Master), I see this:

2024-09-24 09:34:39.006 WARNING (MainThread) [roborock.code_mappings] Missing RoborockFanSpeedS7MaxV code: 110 - defaulting to 105 2024-09-24 09:34:39.006 WARNING (MainThread) [roborock.code_mappings] Missing RoborockMopIntensityS7 code: 209 - defaulting to 200 2024-09-24 09:34:39.006 WARNING (MainThread) [roborock.code_mappings] Missing RoborockDockTypeCode code: 14 - defaulting to 'unknown' 2024-09-24 09:34:39.006 WARNING (MainThread) [roborock.code_mappings] Missing RoborockMopModeS7 code: 306 - defaulting to 300

Particularly the 2nd and 4th of these relate to the Mop

vincedarley avatar Sep 24 '24 10:09 vincedarley

I just noticed the same problem with my new QRevo Master. I have all the settings, i.e. fan speed, mop intensity and mop mode, on Custom currently. Just setting the mop intensity to Off doesn't work. Setting the fan speed to something other than Custom first before setting the mop intensity to Off does work though.

Debug log from just setting the mop intensity to Off: home-assistant_roborock_2024-09-28T17-58-18.733Z.log

Debug log from setting the fan speed to Turbo first and then setting mop intensity to Off: home-assistant_roborock_2024-09-28T18-05-27.090Z.log

andarotajo avatar Sep 28 '24 18:09 andarotajo

I just noticed the same problem with my new QRevo Master. I have all the settings, i.e. fan speed, mop intensity and mop mode, on Custom currently. Just setting the mop intensity to Off doesn't work. Setting the fan speed to something other than Custom first before setting the mop intensity to Off does work though.

Debug log from just setting the mop intensity to Off: home-assistant_roborock_2024-09-28T17-58-18.733Z.log

Debug log from setting the fan speed to Turbo first and then setting mop intensity to Off: home-assistant_roborock_2024-09-28T18-05-27.090Z.log

i am facing exactly the same issue

pkissling avatar Oct 14 '24 18:10 pkissling

Seeing the same thing here, same log entries as well

tracymckibben avatar Oct 23 '24 14:10 tracymckibben

Hi everyone! Sorry for the delay, I have a very limited amount of time to work on projects like this right now. @tracymckibben @pkissling @andarotajo @vincedarley @szavoda If one of you can do the following

  1. Get me your diagnostic logs - I need to get the internal model id
  2. For each suction and mop level, I need you to go through and write down what their id is. Similar to what was done here: https://github.com/home-assistant/core/issues/130000#issuecomment-2461247080 The cleaner you can do it for me the easier it is for me to implement and the faster a bugfix can get in!

Thank you!

Lash-L avatar Nov 08 '24 02:11 Lash-L

Took me a while to work out how to generate the bad items in the log.

My results (for QRevo Master) are almost identical to the #130000 ones, but with the following differences so far:

Model: roborock.vacuum.a117

fan_power has one more value: 105 = Max+

And then the '110' and '209' warnings above are from this: when I set the cleaning mode to “AI SmartPlan” (an option alongside “Vac & Mop”, “Mop”, “Vacuum” and “Customise”), then fan_power is set to 110 and water_box_mode is set to 209.

I do not find it possible to get either fan_power=110 or water_box_mode=209 by changing vacuum or mop settings manually. Those values only seem achieved by the AI Smart Plan mode.

I'm not yet sure how to get the RoborockMopModeS7 code 306.

vincedarley avatar Nov 09 '24 12:11 vincedarley

FWIW, in the HomeAssistant device view, right hand side "Logbook", when I adjust mop intensity in the Roborock app, that is reflected instantly in the logbook and the configuration. I do not see anything reflected at all when I adjust the Vacuum intensity.

vincedarley avatar Nov 09 '24 12:11 vincedarley

Hi - next bump for python-roborock i put out will include this. Thanks for your patience!

Lash-L avatar Nov 13 '24 22:11 Lash-L

I confirm that the bug is not present if the setting the fan speed BEFORE changing mop intensity.

mariomaz87 avatar Dec 02 '24 10:12 mariomaz87

I confirm that the bug is not present if the setting the fan speed BEFORE changing mop intensity.

I am doing similar testing and noticed that if I set the fan power first, THEN you can run the following code successfully data: command: set_mop_mode params: mop_mode 300 target: entity_id: vacuum.s8_maxv_ultra action: vacuum.send_command

normalee1993 avatar Dec 24 '24 17:12 normalee1993

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

Seeing this bug as well on my end. I can change mop intensity to anything EXCEPT off from HA no problem (instant chime from the vacuum and HA logs the command in logbook). If I send the command with the mop intensity of off, I get no chime and no ack in the log from HA but I do get toast notification of "Action ran successfully". YAML that gets no response:

alias: turn off mopping
action: select.select_option
metadata: {}
data:
  option: "off"
target:
  entity_id: select.s8_maxv_ultra_mop_intensity

YAML that gets a response:

alias: turn off mopping
action: select.select_option
metadata: {}
data:
  option: "smart_mode"
target:
  entity_id: select.s8_maxv_ultra_mop_intensity

Further, when looking at the list status, I dont see off in the dropdown for Mop intensity (maybe a red herring but wanted to bring it up). Image

Looks like doing the Vacuum fan speed via yaml would be an option as per the above; but the fan speed options are not available from the integration as is.

Hopefully this helps a bit. If you have a beta revision and need a test person, feel free to ping me and I'll let you know :) If you'd like the debug logs from my end let me know (not familiar with grabbing them personally but I see @andarotajo did earlier).

Edit: Did turn on logging and when I run the action, this what I got when running the command (I sliced out thousands of lines so hopefully I didnt accidentally nuke any relevant info.

roborock logs.txt

Iamthemedic avatar Mar 25 '25 01:03 Iamthemedic

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.