Segment/Room repetition for vacuum no working

[ioannispelelis]

The problem

When setting an automation to clean twice the same segment as said in the documentation it does not work. even when putting twice the same number for the segment it only vacuums it once (tested with a Roborock S6) https://www.home-assistant.io/integrations/xiaomi_miio/#xiaomi-mi-robot-vacuum

I tested with below automation action.

  - service: xiaomi_miio.vacuum_clean_segment
    target:
      entity_id: vacuum.roborock_s6
    data:
      segments:
        - 16
        - 16

I also tested with brackets segments: [16, 16] but it still does not work and only vacuum once

What version of Home Assistant Core has the issue?

core-2021.10.7

What was the last working version of Home Assistant Core?

No response

What type of installation are you running?

Home Assistant Supervised

Integration causing the issue

xiaomi_miio

Link to integration documentation on our website

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

Example YAML snippet

No response

Anything in the logs that might be useful for us?

No response

Additional information

No response

[probot-home-assistant[bot]]

Hey there @rytilahti, @syssi, @starkillerog, @bieniu, mind taking a look at this issue as it has been labeled with an integration (xiaomi_miio) you are listed as a code owner for? Thanks! _{^{(message by CodeOwnersMention)}}

---

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

[AntonB80]

The problem with repeating segments. using Roborock S5 max. in automation service: xiaomi_miio.vacuum_clean_segment using - segments: [1, 1]. But Roborock cleans the room only once((((((

[mateuszmalek]

Got the same issue with Roborock S5 Max. Manually calling the service ends up with mentioned behavior (vacuum is cleaning room only once).

service: xiaomi_miio.vacuum_clean_segment
data:
  segments:
    - 21
    - 21
target:
  entity_id: vacuum.roborock_vacuum_s5e

Same result when trying to manually send command:

service: vacuum.send_command
target:
  entity_id: vacuum.roborock_vacuum_s5e
data:
  command: app_segment_clean
  params:
    - 21
    - 21

However, after some troubleshooting, calling vacuum using python-miio directly works with this command:

miiocli vacuum --ip VACUUM_IP --token XXX segment_clean '[{"segments":[21], "repeat": 2}]'

As well as:

service: vacuum.send_command
target:
  entity_id: vacuum.roborock_vacuum_s5e
data:
  command: app_segment_clean
  params:
    - segments:
        - 21
      repeat: 2

This one won't work as "repeat" param is not allowed:

service: xiaomi_miio.vacuum_clean_segment
data:
  segments:
    - 21
  repeat: 2
target:
  entity_id: vacuum.roborock_vacuum_s5e

[CMDR-Sloma]

I'm having the same issue with S7.

[ArthurMalet]

Same issue here (S7). Vaccum clean the room only once.

[kryptonitecb3]

This is still an issue, S7 MaxV using xiaomi_miio.vacuum_clean_segment does not work.

service: xiaomi_miio.vacuum_clean_segment
data:
  segments: [17,17]
target:
  entity_id: vacuum.rosie

When I use vacuum.send_command the vacuum successfully repeats the segment.

service: vacuum.send_command
target:
  entity_id: vacuum.rosie
data:
  command: app_segment_clean
  params:
    - segments:
        - 17
      repeat: 2

[github-actions[bot]]

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.

[Wombosvideo]

This issue is still present as of today, with latest versions installed. A fix for this would be possible within minutes but nothing happened so far. Sad to see.

[issue-triage-workflows[bot]]

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.

[cptkng23]

It's still not working for me with latest HA and roborock S5 max.

The app_send_command though works.

[issue-triage-workflows[bot]]

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.

[mateuszmalek]

The issue is still present - and it seems that it won't be fixed anytime soon.

[sophof]

Does anyone have any clue what the root cause could be? I could try and have a go at it but I have no clue where to start debugging this.

[jurijzahn8019]

It seems like a change in the API. So why not adjust services.yaml and the corresponding call to reflect this?

Or maybe here is a small parameter mismatch:

ATTR_ZONE_REPEATER = "repeats"

instead of "repeat" (however I do not know where this is also used, so maybe it is needed to introduce additional param token)

[issue-triage-workflows[bot]]

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.