Setting up room cleaning with Map Extractor

[PiotrMachowski]

Since v2.1.0 there is a simplified way to add rooms to your map card:

1. Add rooms to attributes section of map extractor config and reload xiaomi_cloud_map_extractor domain using a dedicated button in Server Controls or xiaomi_cloud_map_extractor.reload service call

   camera:
     - platform: xiaomi_cloud_map_extractor
       host: !secret xiaomi_vacuum_host
       token: !secret xiaomi_vacuum_token
       username: !secret xiaomi_cloud_username
       password: !secret xiaomi_cloud_password
       draw: ['all']
       attributes:
         - calibration_points
         - rooms

   

2. Open card editor, click "Generate rooms config" button, check (adjust if needed) your config using yaml editor and save changes.
   

3. Remove rooms from map extractor's config to save memory and reload it again
   

Adding rooms before v2.1.0

To easily set up room cleaning follow these steps:

1. Add rooms to attributes section of map extractor config and reload xiaomi_cloud_map_extractor domain using a dedicated button in Server Controls or xiaomi_cloud_map_extractor.reload service call

   camera:
     - platform: xiaomi_cloud_map_extractor
       host: !secret xiaomi_vacuum_host
       token: !secret xiaomi_vacuum_token
       username: !secret xiaomi_cloud_username
       password: !secret xiaomi_cloud_password
       draw: ['all']
       attributes:
         - calibration_points
         - rooms

   
2. Open "Template" section in "Developer Tools"
   
3. Paste following code in template editor and adjust values for camera_entity and vacuum_entity

   {# ----------------- PROVIDE YOUR OWN ENTITY IDS HERE ----------------- #}
   {% set camera_entity = "camera.xiaomi_cloud_map_extractor" %}
   {% set vacuum_entity = "vacuum.xiaomi_vacuum" %}
   {# ------------------- DO NOT CHANGE ANYTHING BELOW ------------------- #}
   {% set attributes = states[camera_entity].attributes %}
   type: custom:xiaomi-vacuum-map-card
   entity: {{ vacuum_entity }}
   map_source:
     camera: {{ camera_entity }}
   calibration_source:
     camera: true
   map_modes:
     - template: vacuum_goto
     - template: vacuum_clean_zone
     - template: vacuum_clean_segment
       predefined_selections:
   {%- for room_id in attributes.rooms | default([]) %}
   {%- set room = attributes.rooms[room_id] %}
   {%- set keep_float = "." in (room["x0"] | string) %}
   {%- set x = ([room["x0"], room["x1"]] | sum / 2) if keep_float else (([room["x0"], room["x1"]] | sum / 2) | int) %}
   {%- set y = ([room["y0"], room["y1"]] | sum / 2) if keep_float else (([room["y0"], room["y1"]] | sum / 2) | int) %}
         - id: {{room_id}}
           label:
             text: Room {{ room_id }}
             x: {{ x }}
             y: {{ y }}
             offset_y: 35
           icon:
             name: "mdi:broom"
             x: {{ x }}
             y: {{ y }}
   {%- endfor %}

4. Copy template result to card's config and adjust it to your liking
5. Remove rooms from map extractor's config to save memory and reload it again
   

---

Coordinates provided in outline, icon and label are not used in vacuum communication - they are necessary for card just to draw map interface.

[reskes]

EDIT: Since v2.1.0 there is a simplified way to add rooms to your map card (see main post above). I recommend using it, as it is simple to use and I don't maintain the following code anymore.

If you want the template to also generate an outline, you can use this:

{# ----------------- PROVIDE YOUR OWN ENTITY IDS HERE ----------------- #}
{% set camera_entity = "camera.xiaomi_cloud_map_extractor" %}
{% set vacuum_entity = "vacuum.xiaomi_vacuum" %}
{# ------------------- DO NOT CHANGE ANYTHING BELOW ------------------- #}
{% set attributes = states[camera_entity].attributes %}
type: custom:xiaomi-vacuum-map-card
entity: {{ vacuum_entity }}
map_source:
  camera: {{ camera_entity }}
calibration_source:
  camera: true
map_modes:
  - template: vacuum_goto
  - template: vacuum_clean_zone
  - template: vacuum_clean_segment
    predefined_selections:
{%- for room_id in attributes.rooms | default([]) %}
{%- set room = attributes.rooms[room_id] %}
{%- set keep_float = "." in (room["x0"] | string) %}
{%- set x = ([room["x0"], room["x1"]] | sum / 2) if keep_float else (([room["x0"], room["x1"]] | sum / 2) | int) %}
{%- set y = ([room["y0"], room["y1"]] | sum / 2) if keep_float else (([room["y0"], room["y1"]] | sum / 2) | int) %}
      - id: {{room_id}}
        outline:
          - - {{room["x0"]}}
            - {{room["y0"]}}
          - - {{room["x0"]}}
            - {{room["y1"]}}
          - - {{room["x1"]}}
            - {{room["y1"]}}
          - - {{room["x1"]}}
            - {{room["y0"]}}
        label:
          text: Room {{room_id}}
          x: {{ x }}
          y: {{ y }}
          offset_y: 35
        icon:
          name: "mdi:broom"
          x: {{ x }}
          y: {{ y }}
{%- endfor %}

[jwvanderbeck]

You have a bug here when you set the room number, trying to set it to a blank attribute name which won't work. Strangely at least in my case trying to set it to room,["name"] just results in all my rooms being named None :( So looks like that data isn't scraped or something. Guess I'll just use numbers for now

[PiotrMachowski]

Changed to room number

[adocampo]

Those templates fail here

Home Assistant Core 2022.5.5

[totalitarian]

Can you try with current version?

I'm already on 2.2.0

[PiotrMachowski]

Can you try with current version?

I'm already on 2.2.0

Current version of template (from this thread), not card

[totalitarian]

Looks like the extractor isn't returning room names. Is that normal?

calibration_points: 
- vacuum:
    x: 25500
    'y': 25500
  map:
    x: 200
    'y': 118
- vacuum:
    x: 26500
    'y': 25500
  map:
    x: 220
    'y': 118
- vacuum:
    x: 25500
    'y': 26500
  map:
    x: 200
    'y': 98

rooms: 
'16':
  x0: 18700
  y0: 19700
  x1: 22450
  y1: 24550
'17':
  x0: 22800
  y0: 27150
  x1: 26000
  y1: 29750
'18':
  x0: 22450
  y0: 19650
  x1: 30100
  y1: 23450
'19':
  x0: 19450
  y0: 23400
  x1: 26050
  y1: 27150
'20':
  x0: 28250
  y0: 25300
  x1: 30200
  y1: 26800
'21':
  x0: 26100
  y0: 23550
  x1: 30400
  y1: 25900

[PiotrMachowski]

I have fixed it again. Yes, it is ok, it depends on vacuum model

[totalitarian]

Excellent! I presume there is no way to auto extract the room name rather than the room number?

[weemaba999]

When trying to add the template, following error pops-up: TyperError: 'NoneType' object is not iterable....

This is the code

{# ----------------- PROVIDE YOUR OWN ENTITY IDS HERE ----------------- #}
{% set camera_entity = "camera.xiaomi_cloud_map_extractor" %}
{% set vacuum_entity = "vacuum.jarvis" %}
{# ------------------- DO NOT CHANGE ANYTHING BELOW ------------------- #}
{% set attributes = states[camera_entity].attributes %}
type: custom:xiaomi-vacuum-map-card
entity: {{ vacuum_entity }}
map_source:
  camera: {{ camera_entity }}
calibration_source:
  camera: true
map_modes:
  - template: vacuum_goto
  - template: vacuum_clean_zone
  - template: vacuum_clean_segment
    predefined_selections:
{%- for room_id in attributes.rooms %}
{%- set room = attributes.rooms[room_id] %}
{%- set keep_float = "." in (room["x0"] | string) %}
{%- set x = ([room["x0"], room["x1"]] | sum / 2) if keep_float else (([room["x0"], room["x1"]] | sum / 2) | int) %}
{%- set y = ([room["y0"], room["y1"]] | sum / 2) if keep_float else (([room["y0"], room["y1"]] | sum / 2) | int) %}
      - id: {{room_id}}
        label:
          text: Room {{room_id}}
          x: {{ x }}
          y: {{ y }}
          offset_y: 35
        icon:
          name: "mdi:broom"
          x: {{ x }}
          y: {{ y }}
{%- endfor %}

[PiotrMachowski]

It looks like you don't have rooms in camera's attributes

[charredchar]

I actually get something similar using the original posting;
TypeError: argument of type 'Room' is not iterable
If I use the version @weemaba999 shared I don't get an error and it shows fine in the results.

Edit: The version, as of 2022/07/28, works again!

[Rolf-Smit]

What is the most convenient way to create segments (rooms) with a multi-floor setup? Should I change maps, by sending a command to my robot? Then combine the generated predefined_selections? Or can we change the predefined_selections based on the map that is currently active?

[PiotrMachowski]

You can create additional presets for additional floors, each preset has its own map settings (including map modes and selections). Example of such setup is in demo config

[The-Janitor]

When I try to add this to my dashboard I get the following error:

I have followed the example posted in post # 1 but no matter what I can't seem to make it work. I have tried adding/removing my card and the information in configuration.yaml again, restarting both Homeassistant and the service multiple times and I can't see whats wrong. Does anyone have an idea?

[PiotrMachowski]

You do not add this code to your dashboard, you have to paste it in Template Dev Tools and then use its output in card's config

[The-Janitor]

Well that's embarrassing ... Thank you very much! - I obviously still have a lot to learn - but now it's working :-)

[pannal]

Quick sidenote to the new room config generator functionality:
It doesn't work when the vacuum card is inside a vertical-stack card - the button doesn't do anything. This only seems to work if the card is "on its own".

[PiotrMachowski]

Thanks for info, I will check it out

[RainesGH]

When I was adding a template, an error also popped up: TyperError: 'NoneType' object is not iterable，what should i do?

[PiotrMachowski]

Have you tried to use automatic setup?

[LexaBukreev]

Добрый день! Пётр, скажите, реализована ли возможность рисовать виртуальные стены на карте, чтобы робот не заезжал в определенные зоны? Аппарат rockrobo.vacuum.v1

[PiotrMachowski]

no

[LexaBukreev]

Well, i found how to define rooms, how to draw custom (not rectangle) outlines point by point in config file. But today robot started usuall regular cleaning and reset the map, and now new map coordinates is different and my room, drawled yesterday, is obsoletely not in a place. I am sure, here should be a solution, but i did not find it yet in discussions or FAQ. I think it should be some kind of map-saving option or it's coordinates option, or i have to put some calibration points to the config. My dock station (of course) is always in the same place.
Please give me some advice o links to read how-to manual. Thanks.

[PiotrMachowski]

You can't do anything in Map Extractor if map changes on Xiaomi server. You have to turn on map saving on your vacuum in Xiaomi Home (if it is turned off). As far as I remember rockrobo.vacuum.v1 vacuum doesn't have this feature and you have to use only zone cleaning instead of normal full cleaning.

[jiangyu312]

what should i do, when i used the code below,and got this error. Is there something wrong ?

`{# ----------------- PROVIDE YOUR OWN ENTITY IDS HERE ----------------- #}
{% set camera_entity = "camera.xiaomi_cloud_map_extractor" %}
{% set vacuum_entity = "vacuum.roborock_vacuum_a46" %}
{# ------------------- DO NOT CHANGE ANYTHING BELOW ------------------- #}
{% set attributes = states[camera_entity].attributes %}
type: custom:xiaomi-vacuum-map-card
entity: {{ vacuum_entity }}
map_source:
camera: {{ camera_entity }}
calibration_source:
camera: true
map_modes:

template: vacuum_goto
template: vacuum_clean_zone
template: vacuum_clean_segment
predefined_selections:
{%- for room_id in attributes.rooms %}
{%- set room = attributes.rooms[room_id] %}
{%- set keep_float = "." in (room["x0"] | string) %}
{%- set x = ([room["x0"], room["x1"]] | sum / 2) if keep_float else (([room["x0"], room["x1"]] | sum / 2) | int) %}
{%- set y = ([room["y0"], room["y1"]] | sum / 2) if keep_float else (([room["y0"], room["y1"]] | sum / 2) | int) %}
id: {{room_id}}
label:
text: Room {{room_id}}
x: {{ x }}
y: {{ y }}
offset_y: 35
icon:
name: "mdi:broom"
x: {{ x }}
y: {{ y }}
{%- endfor %}`

[PiotrMachowski]

Have you tried to use automatic setup?

[jiangyu312]

Setup for what ? add the vacuum device or using the temple generating code ?
My situation same as this gay@weemaba999 on top

[PiotrMachowski]

Since v2.1.0 you don't have to use this template, just use "Generate rooms config" button in the card editor

[jiangyu312]

Is it here?Can not generated.
In my "configuration.yaml" files,is already add -rooms.

[PiotrMachowski]

Your map is not available, it's not possible to do extract anything in this state

[kovacsla]

Hi! I have a problem with Xiaomi-vacuum-map-card. i have a Dreame Bot Z10 Pro, it is perfectly working with HACS Dreame Vacuum integration. I want it to use room selection function in Home Assitant, so I insatlling Xiaomi-vacuum-map-card. When I try to select the room and click the play button I have got error message: No response from the device. What could be the problem?

[kovacsla]

The card config is after push the "Generate rooms config" button

type: custom:xiaomi-vacuum-map-card
map_source:
  camera: camera.consuela_map
calibration_source:
  camera: true
entity: vacuum.consuela
vacuum_platform: default
map_modes:
  - name: Zone cleanup
    icon: mdi:select-drag
    run_immediately: false
    coordinates_rounding: true
    selection_type: MANUAL_RECTANGLE
    max_selections: 5
    repeats_type: EXTERNAL
    max_repeats: 3
    service_call_schema:
      service: xiaomi_miio.vacuum_clean_zone
      service_data:
        zone: '[[selection]]'
        repeats: '[[repeats]]'
        entity_id: '[[entity_id]]'
    predefined_selections: []
    variables: {}
  - name: Pin & Go
    icon: mdi:map-marker-plus
    run_immediately: false
    coordinates_rounding: true
    selection_type: MANUAL_POINT
    max_selections: 999
    repeats_type: NONE
    max_repeats: 1
    service_call_schema:
      service: xiaomi_miio.vacuum_goto
      service_data:
        x_coord: '[[point_x]]'
        y_coord: '[[point_y]]'
        entity_id: '[[entity_id]]'
    predefined_selections: []
    variables: {}
  - name: Rooms
    icon: mdi:floor-plan
    run_immediately: false
    coordinates_rounding: true
    selection_type: ROOM
    max_selections: 999
    repeats_type: REPEAT
    max_repeats: 3
    service_call_schema:
      service: xiaomi_miio.vacuum_clean_segment
      service_data:
        segments: '[[selection]]'
        entity_id: '[[entity_id]]'
    predefined_selections:
      - id: '1'
        icon:
          name: mdi:broom
          x: -2850
          'y': 7425
        label:
          text: Gardrób
          x: -2850
          'y': 7425
          offset_y: 35
        outline:
          - - -4800
            - 6750
          - - -900
            - 6750
          - - -900
            - 8100
          - - -4800
            - 8100
      - id: '2'
        icon:
          name: mdi:broom
          x: -2550
          'y': 4900
        label:
          text: Háló
          x: -2550
          'y': 4900
          offset_y: 35
        outline:
          - - -4700
            - 3050
          - - -400
            - 3050
          - - -400
            - 6750
          - - -4700
            - 6750
      - id: '3'
        icon:
          name: mdi:broom
          x: 1650
          'y': 5500
        label:
          text: Konyha
          x: 1650
          'y': 5500
          offset_y: 35
        outline:
          - - 550
            - 2900
          - - 2750
            - 2900
          - - 2750
            - 8100
          - - 550
            - 8100
      - id: '4'
        icon:
          name: mdi:broom
          x: 6025
          'y': 2475
        label:
          text: Fürdő
          x: 6025
          'y': 2475
          offset_y: 35
        outline:
          - - 4500
            - 1600
          - - 7550
            - 1600
          - - 7550
            - 3350
          - - 4500
            - 3350
      - id: '5'
        icon:
          name: mdi:broom
          x: 5225
          'y': 150
        label:
          text: Réka
          x: 5225
          'y': 150
          offset_y: 35
        outline:
          - - 2850
            - -1150
          - - 7600
            - -1150
          - - 7600
            - 1450
          - - 2850
            - 1450
      - id: '6'
        icon:
          name: mdi:broom
          x: -1000
          'y': 850
        label:
          text: Nappali
          x: -1000
          'y': 850
          offset_y: 35
        outline:
          - - -4800
            - -1350
          - - 2800
            - -1350
          - - 2800
            - 3050
          - - -4800
            - 3050
      - id: '7'
        icon:
          name: mdi:broom
          x: 3350
          'y': 2075
        label:
          text: Folyosó
          x: 3350
          'y': 2075
          offset_y: 35
        outline:
          - - 2200
            - 1600
          - - 4500
            - 1600
          - - 4500
            - 2550
          - - 2200
            - 2550
    variables: {}
tiles:
  - tile_id: status
    entity: vacuum.consuela
    label: Status
    attribute: status
    icon: mdi:robot-vacuum
    translations:
      starting: Starting
      charger disconnected: Charger disconnected
      idle: Idle
      remote control active: Remote control active
      cleaning: Cleaning
      returning home: Returning home
      manual mode: Manual mode
      charging: Charging
      charging problem: Charging problem
      paused: Paused
      spot cleaning: Spot cleaning
      error: Error
      shutting down: Shutting down
      updating: Updating
      docking: Docking
      going to target: Going to target
      zoned cleaning: Zoned cleaning
      segment cleaning: Segment cleaning
      emptying the bin: Emptying the bin
      charging complete: Charging complete
      device offline: Device offline
  - tile_id: battery_level
    entity: vacuum.consuela
    label: Battery
    attribute: battery_level
    icon: mdi:battery
    unit: '%'
  - tile_id: fan_speed
    entity: vacuum.consuela
    label: Fan speed
    attribute: fan_speed
    icon: mdi:fan
    translations:
      silent: Silent
      standard: Standard
      medium: Medium
      turbo: Turbo
      auto: Auto
      gentle: Gentle
icons:
  - icon: mdi:play
    conditions:
      - entity: vacuum.consuela
        value_not: cleaning
      - entity: vacuum.consuela
        value_not: error
      - entity: vacuum.consuela
        value_not: returning
    tooltip: Start
    tap_action:
      action: call-service
      service: vacuum.start
      service_data:
        entity_id: vacuum.consuela
  - icon: mdi:pause
    conditions:
      - entity: vacuum.consuela
        value_not: docked
      - entity: vacuum.consuela
        value_not: idle
      - entity: vacuum.consuela
        value_not: error
      - entity: vacuum.consuela
        value_not: paused
    tooltip: Pause
    tap_action:
      action: call-service
      service: vacuum.pause
      service_data:
        entity_id: vacuum.consuela
  - icon: mdi:stop
    conditions:
      - entity: vacuum.consuela
        value_not: docked
      - entity: vacuum.consuela
        value_not: idle
      - entity: vacuum.consuela
        value_not: error
      - entity: vacuum.consuela
        value_not: paused
    tooltip: Stop
    tap_action:
      action: call-service
      service: vacuum.stop
      service_data:
        entity_id: vacuum.consuela
  - icon: mdi:home-map-marker
    conditions:
      - entity: vacuum.consuela
        value_not: docked
      - entity: vacuum.consuela
        value_not: returning
    tooltip: Return to base
    tap_action:
      action: call-service
      service: vacuum.return_to_base
      service_data:
        entity_id: vacuum.consuela
  - icon: mdi:map-marker
    tooltip: Locate
    tap_action:
      action: call-service
      service: vacuum.locate
      service_data:
        entity_id: vacuum.consuela
  - icon: mdi:fan-remove
    conditions:
      - entity: vacuum.consuela
        attribute: fan_speed
        value: Silent
    tooltip: Change fan speed
    tap_action:
      action: call-service
      service: vacuum.set_fan_speed
      service_data:
        entity_id: vacuum.consuela
        fan_speed: Standard
  - icon: mdi:fan-speed-1
    conditions:
      - entity: vacuum.consuela
        attribute: fan_speed
        value: Standard
    tooltip: Change fan speed
    tap_action:
      action: call-service
      service: vacuum.set_fan_speed
      service_data:
        entity_id: vacuum.consuela
        fan_speed: Strong
  - icon: mdi:fan-speed-2
    conditions:
      - entity: vacuum.consuela
        attribute: fan_speed
        value: Strong
    tooltip: Change fan speed
    tap_action:
      action: call-service
      service: vacuum.set_fan_speed
      service_data:
        entity_id: vacuum.consuela
        fan_speed: Turbo
  - icon: mdi:fan-speed-3
    conditions:
      - entity: vacuum.consuela
        attribute: fan_speed
        value: Turbo
    tooltip: Change fan speed
    tap_action:
      action: call-service
      service: vacuum.set_fan_speed
      service_data:
        entity_id: vacuum.consuela
        fan_speed: Silent
  - icon: mdi:fan-alert
    conditions:
      - entity: vacuum.consuela
        attribute: fan_speed
        value_not: Silent
      - entity: vacuum.consuela
        attribute: fan_speed
        value_not: Standard
      - entity: vacuum.consuela
        attribute: fan_speed
        value_not: Strong
      - entity: vacuum.consuela
        attribute: fan_speed
        value_not: Turbo
    tooltip: Change fan speed
    tap_action:
      action: call-service
      service: vacuum.set_fan_speed
      service_data:
        entity_id: vacuum.consuela
        fan_speed: Silent

[kovacsla]

I found the mistake. Tha card config change the "xiaomi_miio.vacuum_clean_segment" to "dreame_vacuum.vacuum_clean_segment" and working everithing. Thanks a lot.

[PiotrMachowski]

You have pushed also "Generate static config" button, it was unnecessary. Also you shouldn't use "Generate rooms config", just steps for versions before 2.1.0 with template that I have linked earlier

[kovacsla]

Hi! Everything works fine, but the pulldown menu jump to the top of page. Do You have any idea?

Attekintes.Home.Assistant.-.Google.Chrome.2022-11-27.22-33-07_1.mp4

[PiotrMachowski]

#397

[tbozo]

Hello,
Thanks for your work, I had trouble finding the button "Generate rooms config" , and I realized it was because I was in full yaml mode (and AFAIK I could not get to the card configuration) you might want to add this in the turotial.
I've revert to UI mode (in fact I choose storage) got the info about the room and it worked.

[PiotrMachowski]

Personally I prefer to have my main dashboard in YAML mode and an additional one in storage mode, just for testing

[GeroComp]

Hi Piotr, please, what have I done wrong? Please watch the following video. Physically, the vacuum cleaner pulls out of the docking station, stays there for about 10 seconds, and then immediately returns to it. However, when I start the vacuum cleaner in the "Zone cleanup" menu, everything works great. It does not work only cleaning the selected room, see video. Please help me find the my error.
Thank you for your help. Radek

Untitled.video.-.Made.with.Clipchamp.2.mp4

This is my configuration:

language: cs
type: custom:xiaomi-vacuum-map-card
map_source:
  camera: camera.xiaomi_cloud_map_extractor
calibration_source:
  camera: true
entity: vacuum.roborock_s5_max
vacuum_platform: default
map_locked: false
two_finger_pan: true
map_modes:
  - template: vacuum_clean_zone
  - template: vacuum_clean_segment
    predefined_selections:
      - id: 1
        outline:
          - - 17263
            - 27868
          - - 19389
            - 27868
          - - 19389
            - 23349
          - - 17263
            - 23349
        label:
          text: Koupelna
          x: 18282
          'y': 25796
          offset_y: 35
        icon:
          name: mdi:shower
          x: 18282
          'y': 25496
      - id: 2
        outline:
          - - 19607
            - 27460
          - - 22071
            - 27460
          - - 22071
            - 23349
          - - 19607
            - 23349
        label:
          text: Kuchyň
          x: 20800
          'y': 25696
          offset_y: 35
        icon:
          name: mdi:table-chair
          x: 20800
          'y': 25496
      - id: 3
        outline:
          - - 22169
            - 27771
          - - 26156
            - 27771
          - - 26156
            - 22310
          - - 22169
            - 22310
        label:
          text: Obývák
          x: 24007
          'y': 25700
          offset_y: 35
        icon:
          name: mdi:television
          x: 24007
          'y': 25400
      - id: 4
        outline:
          - - 18327
            - 22165
          - - 22145
            - 22165
          - - 22169
            - 23397
          - - 18327
            - 23397
        label:
          text: Chodba
          x: 20166
          'y': 23396
          offset_y: 35
        icon:
          name: mdi:shoe-print
          x: 20166
          'y': 22896
      - id: 5
        outline:
          - - 22216
            - 22189
          - - 26130
            - 22189
          - - 26130
            - 18226
          - - 22216
            - 18226
        label:
          text: Ložnice
          x: 24166
          'y': 20500
          offset_y: 35
        icon:
          name: mdi:bed
          x: 24166
          'y': 20300
      - id: 6
        outline:
          - - 18475
            - 22050
          - - 21164
            - 22050
          - - 21164
            - 18249
          - - 18475
            - 18249
        label:
          text: Šatna podkroví
          x: 20728
          'y': 20420
          offset_y: 35
        icon:
          name: mdi:wardrobe
          x: 20728
          'y': 20220
      - id: 7
        outline:
          - - 26758
            - 23180
          - - 23738
            - 23180
          - - 23738
            - 23832
          - - 26758
            - 23832
        label:
          text: Drobky
          x: 24728
          'y': 24620
          offset_y: 35
        icon:
          name: mdi:broom
          x: 26628
          'y': 23520
  - template: vacuum_goto
  - template: vacuum_follow_path

My configuration.txt

[PiotrMachowski]

Have you created this config by yourself, or using map card/generator?

[GeroComp]

I created it myself. Since I am a beginner, I partially used your demo config and modified it to my map and my vacuum cleaner.

[PiotrMachowski]

You have used invalid room ids. They have to match with ones saved in the vacuum. Try to use steps described above instead and then adjust them to your liking.

[AseKarlsson]

Hi,

Very new here and just learn to add the -rooms attribute to my code, very nice addition!

• Rooms show up nice, but the naming is "Room 16", "Room 17" so it did not pull the name from "Mi Home" App. What can be done to name these right?
• The color of the rooms is not the same as in the App. Would not care otherwise but adjacent rooms got the same color in HA, How can I correct this?

Thanks,
Ase

[PiotrMachowski]

• Rooms show up nice, but the naming is "Room 16", "Room 17" so it did not pull the name from "Mi Home" App. What can be done to name these right?

You just have to open yaml config of the card and rename them

• The color of the rooms is not the same as in the App. Would not care otherwise but adjacent rooms got the same color in HA, How can I correct this?

You can do it using room_colors config in Map Extractor. Example

[AseKarlsson]

Thanks Piotr!

[MMouse23]

Great work on this Piotr.
I currently have 13 roombas and i am switching to 3-4x RoboRock.
Mainly as this vacuum card is simply the best.
There is one thing i cannot get to work.
I can send multiple room selections, but repeats do not work at all. Given the Roborock its performance, sometimes 2x a room would be very nice. Your card supports it, but my code does not :(
What am i missing?

type: custom:xiaomi-vacuum-map-card
map_source:
  camera: camera.xiaomi_cloud_map_extractor
calibration_source:
  camera: true
entity: vacuum.roborock_vacuum_a27
vacuum_platform: default
map_modes:
  - template: vacuum_clean_segment
    name: Kamers Schoonmaken
    max_repeats: 5
    max_selections: 20
    repeats_type: REPEAT
    predefined_selections:
      - id: '5'
        label:
          text: BadKamer
          x: 37450
          'y': 37650
        outline:
          - - 36050
            - 36750
          - - 38850
            - 36750

Below is capped for just room definitions

[PiotrMachowski]

It's a bug in HA core. You can mitigate it by installing the latest beta version of this card or by using config from this issue.

I currently have 13 roombas and i am switching to 3-4x RoboRock.

😮 woah

By the way, this card should work with Roombas as well (I'm not sure if it's possible with all models though)

[MMouse23]

It's a bug in HA core. You can mitigate it by installing the latest beta version of this card or by using config from this issue.

I currently have 13 roombas and i am switching to 3-4x RoboRock.

😮 woah

By the way, this card should work with Roombas as well (I'm not sure if it's possible with all models though)

The beta does not work, the API call from the map is not sent to the bot at all.
The other buttons work, just not the map based roomcleaning.
Hence i reverted to the public release.

Any tips on this? I would like to get multiple room cycles working.
Thank you in advance

[itsmartinho]

Is it possible to create a custom button, per room on my UI, that will send the vacuum there?

[PiotrMachowski]

Outside the card?

[itsmartinho]

Thank you for the quick reply.

Yes. Like a mushroom-entity-card with a press or boolean helper, that would make the robot go for the bathroom, or just the office and so on via a automation. As long as I could learn how to make a service or similar would be awesome. If that's even possible.
(For context, I have my home assistant built per room, and that'd make my life so much easier)

[PiotrMachowski]

Service call used for room cleaning is different for different integrations. To check out service call used by the Map Card open card editor and click "Copy service call" button

[itsmartinho]

Appreciate it. Thank you!

Got this to work:

      service: vacuum.vacuum_clean_segment
      data:
        segments: [15]
        entity_id: vacuum.ticiana

[ravenboboj]

Hi Piotr, @PiotrMachowski
Huge thanks to your work!! Would be much appreciated. if you could help.
There is a bit problem with the "generate rooms config" it's grey out not click-able. then from the drop list there is only zone cleanup and clean point. no other selections as in video.
I'm running the home assistant on a docker (synology), is it because I didn't configure the yaml file? thanks.

[PiotrMachowski]

It is grayed-out when camera provides no rooms attribute. Judging from the map image it seems that the integration haven't retrieved any rooms.

[ravenboboj]

Thank you for quick response, it pulls from Mi cloud. I'm quite newbie, not sure how exactly it works. suspicions I didn't give any room from the official APP? reading through all your instruction posts, is it correct that it's possible to create my custom zone by modifying the configure.yaml? Perhaps I couldn't open the configuration.yaml. damn

[PiotrMachowski]

is it correct that it's possible to create my custom zone by modifying the configure.yaml?

Not configuration.yaml, but in yaml card editor. But I would advise to use rooms instead. Try following up in Tasshack/dreame-vacuum repo

[Andrewa80]

Hi everyone, I followed the guide and I can finally manage the rooms from HA, I miss sending voice commands to my Google Home for the rooms. I see the camera.aspirapolvere entity, the status and the list of rooms: 1,2,3,4,5,6
I guess I need to create a script and plug it into Google.
Can you help me? Thank you

[andpaw88]

Hi,
How i can change the behaviour after page refresh?
It shows everytime i refresh the page i see the map as below:

Ii is possible that it will looks like below:

[PiotrMachowski]

The recommended way to do it is by adjusting map_transformation -> trim section in the config of Map Extractor

[wormiq]

Hi Piotr,

I was really trying to do it on my own, but after 4 hours I came to a state that it runs the vacuum, but...that's the view I have:

I do not know how to move on and what to change in the configuration so it would show properly the map.

I am planning to use zones, so I would really like to have it well done :)

Can you help me to move forward with the setup?

[wormiq]

I am using MQTT, as I have valetudo on my vacuum cleaner - Roborock S5.
What should I do in this case?

[PiotrMachowski]

https://github.com/sca075/valetudo_vacuum_camera/

[wormiq]

Hi Piotr,

thank you! I have the camera now. Will I be able to use it with your setup, so I can than manage the zoned clean up and so on, or do I need to go via a different path?

Should I change something in the configuration, due to the fact, that I will have valetudo camera instead of xiaomi?

[PiotrMachowski]

Yes, everything should work. You just have to change vacuum platform

[sca075]

@wormiq,
Please fill free to get in contact with me if you need guidance to setup the camera with the card. Although on the camera repo there are step by step instruction, if you are using the Rand version of Valetudo the camera provide the zones as an attribute else the rooms (segments) can be setup easily once you have a new card with the camera setup, just by clicking the generate_room_configuration and adding the internal_variables as explained on the guides and home of the camera repository.

[szybaSS]

Hello, with the Xiaomi V1 vacuum cleaner model, despite the visible button to generate rooms, the generation does not take place. You can see the current cleaning map. I managed to achieve zone cleaning on a static configuration. Is it any different in practice from cleaning rooms?

[beasthouse-au]

With Step 1, adding rooms to attributes section of map extractor config, I have been using the card with the camera entity from the Roborock integration, do I need to add a second camera entity manually? Reason I ask is that the map doesn't seem to be accurate, e.g I tell it to clean one room but it cleans the room next to it instead. This doesn't happen when using the native Roborock app.

[beasthouse-au]

Apologies about the additional thread @PiotrMachowski - had replied by email and it did that. Have deleted and will continue here.

I had set it up as per the instructions you linked me to, first via the custom integration to get the right coordinates then back to the core integration. I did change the vacuum_platform field to send_command - wonder if that made a difference.

You asked for the "Copy service call" from the editior - here it is.

{
  "domain": "vacuum",
  "service": "send_command",
  "serviceData": {
    "command": "app_segment_clean",
    "params": [
      "19"
    ],
    "entity_id": "vacuum.roborock_qrevo_s"
  }
}

[PiotrMachowski]

Can you adjust the code of vacuum_clean_segment map mode?

- template: vacuum_clean_segment
  id_type: number # <- this line
  predefined_selections:
     ...

[beasthouse-au]

Thanks, that solved the issue of the vacuum not doing anything when told to target a specific room. The map, however, does not update. Snippet of the map card and snippet of the Roborock app (used to just monitor the cleaning as the map card didn't show anything happening).

[PiotrMachowski]

Ok, so I'm afraid that's as much as I can help from the card itself. The rest is handled on the integration side.

[beasthouse-au]

Thanks! Now to figure out the multiple maps/levels part

[Vladeff]

@beasthouse-au How did you integrated the vac?
With the native Roborock integration or the HACS?
In the native I don't have camera.something_map but image.something_map
I have the Qrevo Master and it's not supported in the Mi Home yet. Qrevo S also. So did you managed to add it in MiHome so to get the MiHome Token?

[PiotrMachowski]

#691

[beasthouse-au]

@beasthouse-au How did you integrated the vac? With the native Roborock integration or the HACS? In the native I don't have camera.something_map but image.something_map I have the Qrevo Master and it's not supported in the Mi Home yet. Qrevo S also. So did you managed to add it in MiHome so to get the MiHome Token?

First through the HACS Integration, then the Core / Native Integration as per some instructions covered here #754 (comment)

I have the Qrevo S, was not aware about it not being supported in Mi Home yet, was going to try fixing that this coming weekend.

[YJIbTPA]

@PiotrMachowski, Hi!
I'm using for Roborock S5:

map_source:
  image: '/local/map_background_v2.png'

Is there any way to display the vacuum's location and its path on my own map?

[PiotrMachowski]

No, it's not possible

[Nic8619]

Hi,
I would like to be able to select the areas that my robot vacuum cleaner should clean. Unfortunately, I don't understand how I can do this. Can anyone help me? Thanks guys

[sca075]

What kind of vacuum it is? it looks like the vacuum not support the areas.. "segments" but you should be able to configure the zones instead for instance from the card..

[Nic8619]

It is a ecovacs deebot 950.
Areas are of course supported in the original app. Or do you mean that this integration does not support areas for this model

[sca075]

Well it depends definitely from the camera or whatever you use to extract the map and pass it to card..so what integration do you use?

[PiotrMachowski]

@Nic8619 you can't generate rooms config with your vacuum. You have to configure it manually, here is the example that shows how the config should look like

[dave-unit]

Hi. I can't seem to get the room configs added for roborock. Card is all set up and works but generate room configs does nothing.

[PiotrMachowski]

Have you configured this integration?
https://github.com/Lash-L/RoborockCustomMap/
Do you have rooms in attributes of camera entity?

[wormiq]

I am sorry, but can you take me out of this discussion?! pon., 17 lis 2025 o 22:23 Zafrirshha ***@***.***> napisał(a):

…

With Last Alpha release and UI config, all is working well. many thanks!!! On Sun, Nov 16, 2025 at 6:24 PM Piotr Machowski ***@***.***> wrote: > It shouldn't conflict with anything. Are you sure you have configured > everything correctly? Also, I suggest to use the latest alpha version, it > supports UI configuration > > — > Reply to this email directly, view it on GitHub > < #317 (reply in thread)>, > or unsubscribe > < https://github.com/notifications/unsubscribe-auth/AXWA3YVNJZETZDV4G572DWD35CQNDAVCNFSM6AAAAABYOQFQI6VHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTIOJYGIZDMMI> > . > You are receiving this because you commented.Message ID: > <PiotrMachowski/lovelace-xiaomi-vacuum-map-card/repo-discussions/317/comments/14982261 > @github.com> > — Reply to this email directly, view it on GitHub <#317 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AFHXTC3SU47QTTWBJ7S32FL35I4G5AVCNFSM6AAAAABYOQFQI6VHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTIOJZGQZTQMY> . You are receiving this because you were mentioned.Message ID: <PiotrMachowski/lovelace-xiaomi-vacuum-map-card/repo-discussions/317/comments/14994383 @github.com>

-- wormiq

[PiotrMachowski]

These are normal GitHub notifications. You receive them because you have commented in this discussion. If you don't want to receive them you just have to use the "unsubscribe" button.