Clean room service

[Flavio5]

Hi, I have a Xiaomi Vacuum Mop P, it works well in your new card as KrzysztofHajdamowicz/miio2 platform.
About clean room service, normally I use this template:

service: vacuum.send_command
data:
  command: set_mode_withroom
  params:
    - 0
    - 1
    - 1
    - 11
target:
  entity_id: vacuum.aspirapolvere_pro

where params:
params:

• 0 (0=Normal Vacuum, 1=Edge only)
• 1 (Number of repeats)
• 1 (Quantity of rooms)
• 14 (Room ID)

I tried to configure the service in the card but something goes wrong. I think the problem is '[[selection]]' because if i replace it with the number of a room, the robot starts.
What is wrong?

type: custom:xiaomi-vacuum-map-card
entity: vacuum.aspirapolvere_pro
title: Aspirapolvere Pro
vacuum_platform: KrzysztofHajdamowicz/miio2
map_source:
  camera: camera.mappa_aspirapolvere_pro
calibration_source:
  camera: true
map_modes:
  - template: vacuum_clean_zone
  - template: vacuum_goto
  - name: Pulisci stanze
    icon: mdi:floor-plan
    selection_type: ROOM
    max_selections: 1
    repeats_type: NONE
    service_call_schema:
      service: vacuum.send_command
      service_data:
        entity_id: '[[entity_id]]'
        command: set_mode_withroom
        params:
          - 0
          - 1
          - 1
          - '[[selection]]'
    predefined_selections:
      - id: 10
        label:
          text: Studio
          x: 2
          'y': -0.2
        icon:
          name: mdi:desk
          x: 2
          'y': 0.7
      - id: 11
        label:
          text: Bagno
          x: 6.4
          'y': 0.5
        icon:
          name: mdi:bathtub
          x: 6.4
          'y': 1.3
      - id: 12
        label:
          text: Anticamera
          x: 5.1
          'y': -0.3
        icon:
          name: mdi:home-floor-a
          x: 5.1
          'y': 0.5
language: it

[PiotrMachowski]

Can you try to hold the play button and see how does service call look like? If it will be too big for popup it will be written in browser's console as well

[PiotrMachowski]

By the way, you can add repeats as well:

vacuum_set_mode_withroom:
  sequence:
    - service: vacuum.send_command
      data:
        entity_id: "{{ entity_id }}"
        command: set_mode_withroom
        params: "{{ [0, repeats, 1, room[0]] }}"

  - name: Pulisci stanze
    icon: mdi:floor-plan
    selection_type: ROOM
    max_selections: 1
    repeats_type: EXTERNAL
    max_repeats: 5
    service_call_schema:
      service: script.vacuum_set_mode_withroom
      service_data:
        entity_id: '[[entity_id]]'
        room: '[[selection]]'
        repeats: '[[repeats]]'

[baggein]

Hi! Sorry, I'm a big newbie :)

I am trying to do a multi-select of rooms.
I create a script from your post and I get the error: "Message malformed: extra keys not allowed @ data ['vacuum_set_mode_withroom']"

What am I doing wrong?

[PiotrMachowski]

@baggein where have you put this code?

[baggein]

@baggein where have you put this code?

Scripts->New script->

vacuum_set_mode_withroom:
  sequence:
    - service: vacuum.send_command
      data:
        entity_id: "{{ entity_id }}"
        command: set_mode_withroom
        params: "{{ [0, 1, 1, room[0]] }}"

add: The formatting in the script is correct, it's just not inserted correctly here.

PS: I continue to get acquainted with the new version - it seems I begin to understand that this can be done differently :)
I beg your pardon.

[PiotrMachowski]

@baggein If you paste it in UI script editor you just have to skip first line: vacuum_set_mode_withroom:

[soulcola]

will it works, if i select more than 1 room in card?

[PiotrMachowski]

No, it won't

[soulcola]

So is it possible to send [[selection]] data without brackets?
Maybe you can add set_mode_withroom method to marotoweb/viomise to vacuum_clean_segment template, because it is only way to clean by room ID in this integration

[PiotrMachowski]

Yes, it's possible now using [[selection_unwrapped]].

Card's config can look like this:

  - name: Clean room
    icon: mdi:floor-plan
    selection_type: ROOM
    max_selections: 1
    repeats_type: EXTERNAL
    max_repeats: 5
    service_call_schema:
      service: vacuum.send_command
      service_data:
        entity_id: '[[entity_id]]'
        command: set_mode_withroom
        params:
          - 0
          - '[[repeats]]'
          - 1
          - '[[selection_unwrapped]]'

I will add it to template if you confirm that it works.

[soulcola]

Unfortunately not working.

 "domain": "vacuum",
 "service": "send_command",
 "serviceData": {
   "entity_id": "vacuum.viomi_se",
   "command": "set_mode_withroom",
   "params": [
     0,
     1,
     1,
     "13"
   ]
 }
}

I think service wait integer, but card send "string"

[PiotrMachowski]

Yeah, that's what I was afraid of. This version should work:

  - name: Clean room
    icon: mdi:floor-plan
    selection_type: ROOM
    max_selections: 1
    repeats_type: EXTERNAL
    max_repeats: 5
    service_call_schema:
      service: vacuum.send_command
      service_data:
        entity_id: '[[entity_id]]'
        command: set_mode_withroom
        params: "[ 0, [[repeats]], 1, [[selection_unwrapped]] ]|[[jsonify]]"

btw, please reply in the same thread.

[soulcola]

Yes, it works correct with room IDs.

But there is first parameter with vacuum type (0=Sweep, 1=Sweep&Mop, 2=Mop).
Is it possible to add there attribute value? In my my case template would be {{ state_attr("vacuum.viomi_se", "is_mop")}}?

[PiotrMachowski]

Yup, that's why there was max_selections: 1 config ;)

Here you have an updated version that supports multiple selections:

  - name: Clean room
    icon: mdi:floor-plan
    selection_type: ROOM
    max_selections: 5
    repeats_type: EXTERNAL
    max_repeats: 5
    service_call_schema:
      service: vacuum.send_command
      service_data:
        entity_id: '[[entity_id]]'
        command: set_mode_withroom
        params: '[ "{{state_attr(\"[[entity_id]]\", \"is_mop\")}}", [[repeats]], [[selection_size]], [[selection_unwrapped]] ]|[[jsonify]]'

[soulcola]

I think 2nd arg is not repeats count.
Seems it is vacuum operation (0=stop, 1=start, 2=pause)
Need to test it
3rd argument - selected rooms count

[soulcola]

It seems that it work properly! 2nd param must be always 1, it is not clear, what it means, but works only with value 1.
Thank you for your help!

[PiotrMachowski]

Ok, I have found somewhere that it is repeats number, maybe it was for a different model.

I will add it to viomise platform

[thumDer]

Unfortunately the above example is not working for me. It says name 'selection_size' is not defined
I've found an alternate method using your additional script workaround: #187 (comment):

[thumDer]

Thanks @PiotrMachowski for the additional script trick! Since the zone cleaning is not working with viomi se anymore this is how I solved multiroom cleaning:

card config, with room data extracted from camera:

type: custom:xiaomi-vacuum-map-card
entity: vacuum.viomi_se
vacuum_platform: marotoweb/viomise
map_source:
  camera: camera.xiaomi_cloud_map_extractor
calibration_source:
  camera: true
map_modes:
  - name: Rooms
    icon: mdi:floor-plan
    selection_type: ROOM
    service_call_schema:
      service: script.viomi_set_mode_withroom
      service_data:
        entity_id: '[[entity_id]]'
        rooms: '[[selection]]'
    predefined_selections:
      - id: 13
        label:
          text: Bedroom
          x: -1.15
          'y': -5.2
          offset_y: 35
        icon:
          name: mdi:broom
          x: -1.15
          'y': -5.2
      - id: 11
        label:
          text: Bathroom
          x: 1.6749999999999998
          'y': -5.5
          offset_y: 35
        icon:
          name: mdi:broom
          x: 1.6749999999999998
          'y': -5.5
      - id: 12
        label:
          text: Lobby
          x: 1.45
          'y': -4.125
          offset_y: 35
        icon:
          name: mdi:broom
          x: 1.45
          'y': -4.125
      - id: 10
        label:
          text: Living Room
          x: -0.3750000000000001
          'y': -1.35
          offset_y: 35
        icon:
          name: mdi:broom
          x: -0.3750000000000001
          'y': -1.35

and the script:

viomi_set_mode_withroom:
  sequence:
    - service: vacuum.send_command
      data:
        entity_id: "{{ entity_id }}"
        command: set_mode_withroom
        params: "{{ [0, 1, rooms|count] + rooms }}"

[PiotrMachowski]

@thumDer do you have the latest version of the card installed?

[thumDer]

yes, it is v2.0.11

[PiotrMachowski]

That's weird, it should work without any problems. Have you tried this config that I have posted?

[thumDer]

I'll try the exact same config tonight, and get back to you!

[thumDer]

Sorry for the late answer, just wanted to say that I created a new card for testing purposes, copied your config, and it worked perfectly. I have no idea what is different since then, just wanted to report back.
Thanks for your efforts and this great card!

[mggl89]

Hey! Can you help me please. I have a Xiaomi Trouver LDS finder (p2036)& I don't understand why it doesn't work. I have this error...
Failed to call service xiaomi_miot/call_action. Service not found

 - type: custom:xiaomi-vacuum-map-card
              title: Vacuum
              entity: vacuum.p2036_2418c6128faa
              vacuum_platform: default
              map_source:
                camera: camera.xiaomi_cloud_map_extractor
              calibration_source:
                camera: true
              map_modes:
                - template: vacuum_goto
                - template: vacuum_clean_zone
                  max_selections: 1
                  repeats_type: 5
                  service_call_schema:
                    service: xiaomi_miot.call_action
                    service_data:
                      entity_id: vacuum.p2036_2418c6128faa
                      siid: 4
                      aiid: 1
                      params:
                        - piid: 1
                          value: 19
                        - piid: 10
                          value: '{"areas":[[[[selection_unwrapped]],[[repeats]],1,1]]}'
                      force_params: true

[PiotrMachowski]

Which integration do you use?

[mggl89]

I use Xiaomi_miot

[mggl89]

so, I understand what's wrong: I had to use this service: service: xiaomi_miot_raw.call_action. But I've got another error: extra keys not allowed @ data['params']. I think it happens cause my robot has only 6 objects in MiOT

[PiotrMachowski]

Is there an entity/attribute that tells if the mop is attached to the vacuum?

[AYgrik]

Yes. Attribute: "Is mop" = 1.

[PiotrMachowski]

In such case you can just use {{ state_attr('vacuum.vacuum', 'is_mop') }}

    sequence:
        - service: vacuum.send_command
          data:
            entity_id: "{{ entity_id }}"
            command: set_mode_withroom
            params: "{{ [state_attr('vacuum.vacuum', 'is_mop'), 1, rooms|count] + rooms }}"

[AYgrik]

What to do if the mop is not installed? Should I use a different script?
I was just surprised that full cleaning or cleaning a selected area automatically detects the presence of a mop.

map_modes:
  - template: vacuum_clean_zone

And it works great. But at the same time it does not determine the mop when choosing rooms.

map_modes:
  - template: vacuum_clean_segment

Maybe there is a way to do this not automatically, but at least with a button (icon)? When pressed, the mop/sweep mode changes.

[AYgrik]

Oh, I'm sorry! I understand! Indeed this is the way out. And that's how it works, thanks!