Vacuum Interactive Map Card

Prizm78 · January 10, 2022, 6:21pm

My /config/configuration.yaml look like this for the map extractor: (I am probably just missing some small part somewhere)

#RoboRock
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

Prizm78 · January 10, 2022, 6:23pm

Well, i would guess so, since the map extractor is working fine, and when i start my vacuum from the Mi Home app, i see movement in HA-screen also.

3_14 · January 10, 2022, 6:31pm

Map extractor just retrieves map data, to control the vacuum you have to add it to HA as well

Prizm78 · January 10, 2022, 7:55pm

That was it. I simply assumed that since you had made the map extractor, that this card was like a frontend for that utilizing the javascript for the extractor. I did not think that the card was a frontend for the Xiaomi integration. I sort of feel very silly now

If i may, if you could update your readme/documentation with a “Requirement” section. Something like:

"In order to utilize this card you must first install the Xiaomi Integration.

HA->Configuration->Devices&Services->Integration.
Click on [+ Add Integration], blue button in bottom right corner
Search for “Xiaomi Miio”
Fill in “Cloud username”, “Cloud password” and select your country/region and how you would in the app.

After you have installed the integration, restart HA and install the Card".

(Its just a suggestion from my side as a new person to HA. And spending hours doing research and reading this thread and not fully understand what i needed as a baseline first. Im sure that could help other people in the future too

Bartosz_Guzik · January 10, 2022, 8:13pm

Viomi S9 aka V18 ussing coordinates like:

-5.8191,0.0795,-5.8191,-4.3753,1.2464,-4.3753,1.2464,0.0795

3_14 · January 10, 2022, 8:37pm

It utilizes both extractor and vacuum entity and vacuum doesn’t have to be from built-in miio integration

3_14 · January 10, 2022, 8:37pm

And this coordinates system is supported as well, just not in “default” vacuum platform

Bartosz_Guzik · January 10, 2022, 9:42pm

I checked 4 of build in vacuum platfroms, and none of them supporting “x1,y1; x1,y2; x2,y2; x2,y1” option…

3_14 · January 10, 2022, 9:43pm

Oh, ok. Can you show me the integration that you use?

Bartosz_Guzik · January 10, 2022, 11:18pm

I’m ussing this one:

With this Vacuum:
https://home.miot-spec.com/spec/viomi.vacuum.v18

And I’m ussing this config:

github.com/ha0y/xiaomi_miot_raw

Viomi Vacuum issue

opened 06:43AM - 24 Jun 21 UTC

fokcuk

enhancement

Hello The device is successfully added to Home Assistant via integration but ne…ver actually gets added to the system. In the logs I see this: `Logger: homeassistant.components.vacuum Source: custom_components/xiaomi_miot_raw/__init__.py:1070 Integration: Vacuum (documentation, issues) First occurred: 2:33:52 PM (2 occurrences) Last logged: 2:39:11 PM Error while setting up xiaomi_miot_raw platform for vacuum Traceback (most recent call last): File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 250, in _async_setup_platform await asyncio.shield(task) File "/config/custom_components/xiaomi_miot_raw/vacuum.py", line 97, in async_setup_entry await async_setup_platform(hass, config, async_add_entities) File "/config/custom_components/xiaomi_miot_raw/vacuum.py", line 86, in async_setup_platform await async_generic_setup_platform( File "/config/custom_components/xiaomi_miot_raw/__init__.py", line 1070, in async_generic_setup_platform device_info.hardware_version, File "/usr/local/lib/python3.8/site-packages/miio/device.py", line 88, in hardware_version if self.data["hw_ver"] is not None: KeyError: 'hw_ver'` These are the component mappings that it finds when device is added: {"vacuum":{"status":{"siid":2,"piid":1},"fault":{"siid":2,"piid":2},"wdr_mode":{"siid":2,"piid":11},"door_state":{"siid":2,"piid":12},"contact_state":{"siid":2,"piid":16},"stream_address":{"siid":2,"piid":14},"mute":{"siid":2,"piid":17},"sweep_type":{"siid":2,"piid":4},"mode":{"siid":2,"piid":19}},"a_l":{"vacuum_start_sweep":{"siid":2,"aiid":1},"vacuum_stop_sweeping":{"siid":2,"aiid":2},"vacuum_pause":{"siid":2,"aiid":3},"vacuum_start_charge":{"siid":2,"aiid":4},"vacuum_stop_massage":{"siid":2,"aiid":5},"vacuum_start_mop":{"siid":2,"aiid":6},"vacuum_start_only_sweep":{"siid":2,"aiid":7},"vacuum_start_sweep_mop":{"siid":2,"aiid":8},"viomi_vacuum_reset_map":{"siid":4,"aiid":7},"viomi_vacuum_set_calibration":{"siid":4,"aiid":10},"viomi_vacuum_reset_consumable":{"siid":4,"aiid":11},"viomi_vacuum_set_room_clean":{"siid":4,"aiid":13},"order_del":{"siid":5,"aiid":2},"order_get":{"siid":5,"aiid":3},"point_zone_start_point_clean":{"siid":6,"aiid":1},"point_zone_pause_point_clean":{"siid":6,"aiid":2},"point_zone_start_zone_clean":{"siid":6,"aiid":5},"point_zone_pause_zone_clean":{"siid":6,"aiid":6},"map_upload_by_maptype":{"siid":7,"aiid":1},"map_upload_by_mapid":{"siid":7,"aiid":2},"map_set_cur_map":{"siid":7,"aiid":3},"map_del_map":{"siid":7,"aiid":5},"map_rename_map":{"siid":7,"aiid":7},"map_arrange_room":{"siid":7,"aiid":8},"map_split_room":{"siid":7,"aiid":9},"map_rename_room":{"siid":7,"aiid":10},"map_get_map_list":{"siid":7,"aiid":11},"map_get_cleaning_path":{"siid":7,"aiid":12},"map_set_new_map":{"siid":7,"aiid":13},"map_deal_new_map":{"siid":7,"aiid":14},"voice_find_device":{"siid":8,"aiid":2},"voice_download_voice":{"siid":8,"aiid":3},"voice_get_downloadstatus":{"siid":8,"aiid":4}}} {"vacuum":{"fault":{"No Error":0,"Low Battery Find Charge":1,"Low Bat Need Poweroff":2,"Wheel Trap":3,"Collision Error":4,"Tile Do Task":5,"Lidar Point Err":6,"Front Wall Err":7,"Along Wall Err":8,"Mid Brush Err":9,"Side Brush Err":10,"Fan Err":11,"Lidar Cover":12,"Garbage Full":13,"Garbage Out":18,"Garbage Full Out":15,"Trapped":16,"Pick Up":17,"Cannot Arrive":20,"Start From Forbid":21,"Drop":22,"Kit Water Pump":23,"Find Charge Failed":24,"No Mop Clean":25,"Low Battery Cant Clean":26},"mode":{"Silent":0,"Basic":1,"Medium":2,"Strong":3},"status":{"Sleep":0,"Idle":1,"Paused":2,"Go Charging":3,"Charging":4,"Sweeping":5,"Sweeping and Mopping":6,"Mopping":7},"wdr_mode":{"access":7,"format":"uint8","unit":null,"value_list":{"0":0,"1":1,"2":2}},"door_state":{"access":5,"format":"uint8","unit":null,"value_list":{"0":0,"1":1,"2":2,"3":3}},"contact_state":{"access":5,"format":"uint16","unit":null,"value_range":[0,1200,1]},"stream_address":{"access":0,"format":"string","unit":null},"mute":{"access":7,"format":"uint8","unit":null,"value_range":[0,10,1]},"sweep_type":{"access":7,"format":"uint8","unit":null,"value_list":{"Total":0,"Wall":2,"Zone":3,"Point":4,"Control":5}},"main":true}} I managed to get it added by commending the lines that were relating to hardware_version. Now I have a problem that it does not return back to dock when command is issued

3_14 · January 10, 2022, 11:37pm

Actually, this config contains 2 service calls, which is not possible via UI. Buuuuut you can make a script that will handle it even with current version of map card.

Prizm78 · January 12, 2022, 1:00pm

I have used the map extractor with additional attributes (se below). How should i add all this to the card in order to be able to select a given room? Each room seems to have multiple x and y coordinates, so how do i apply that to the card?

From my current configuration.yaml:

#RoboRock
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
      - charger
      - cleaned_rooms
      - country
      - goto_path
      - goto_predicted_path
      - goto
      - ignored_obstacles_with_photo
      - ignored_obstacles
      - image
      - is_empty
      - map_name
      - no_go_areas
      - no_mopping_areas
      - obstacles_with_photo
      - obstacles
      - room_numbers
      - rooms
      - vacuum_position
      - vacuum_room_name
      - vacuum_room
      - walls
      - zones

And this is what i got in Developer section for the Map extractor. Now i would like to apply this to my card and probably give each room a proper name as well. But most important is to get this in place so wife and kids can use the new system.

[From map extrator]

calibration_points: 
- vacuum:
    x: 25500
    'y': 25500
  map:
    x: 405
    'y': 290
- vacuum:
    x: 26500
    'y': 25500
  map:
    x: 425
    'y': 290
- vacuum:
    x: 25500
    'y': 26500
  map:
    x: 405
    'y': 270

charger: 
x: 25530
'y': 29241

cleaned_rooms: null
country: de
goto: null
goto_path: null
goto_predicted_path: null
ignored_obstacles: null
ignored_obstacles_with_photo: null
image: 
size: 286752
offset_y: 337
offset_x: 105
height: 464
scale: 1
rotation: 0
width: 618

is_empty: false
map_name: roboroommap%2F471931069%2F17
no_go_areas: 
no_mopping_areas: 
obstacles: null
obstacles_with_photo: null
room_numbers: 
'16': null
'17': null
'18': null
'19': null
'20': null
'21': null
'22': null

rooms: 
'16':
  x0: 15100
  y0: 29700
  x1: 18050
  y1: 34000
'17':
  x0: 10850
  y0: 29850
  x1: 15050
  y1: 33300
'18':
  x0: 18000
  y0: 29500
  x1: 19100
  y1: 32650
'19':
  x0: 10850
  y0: 32500
  x1: 15050
  y1: 34350
'20':
  x0: 19350
  y0: 24650
  x1: 28400
  y1: 29400
'21':
  x0: 17000
  y0: 24650
  x1: 19300
  y1: 29450
'22':
  x0: 19150
  y0: 28450
  x1: 22400
  y1: 29500

vacuum_position: 
x: 25539
'y': 29062
a: 93

vacuum_room: 20
vacuum_room_name: null
walls: 
- x0: 15119
  y0: 32317
  x1: 15129
  y1: 32764
- x0: 15072
  y0: 33513
  x1: 15065
  y1: 33210
- x0: 15091
  y0: 31722
  x1: 15107
  y1: 31422

zones: 
- x0: 22800
  y0: 24700
  x1: 25950
  y1: 29500

3_14 · January 12, 2022, 2:02pm

Here you have config generator: Setting up room cleaning with Map Extractor
Paste it in dev tools > templates, create the card with output config and adjust values to your liking.

When finished change camera settings to following to reduce memory usage:

#RoboRock
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

yaruslavm · January 12, 2022, 2:24pm

Hey @3_14

i liked the custom:xiaomi-vacuum-card and custom:xiaomi-vacuum-map-card
i wanted a hold_action over the vacuum card to bring popup with vaccum map but it fails to do so, other buttons triggers this action fine.

SO i wanted to make sure that custom:xiaomi-vacuum-card does not support a fire-dom-event(browser mode)

3_14 · January 12, 2022, 2:26pm

@yaruslavm custom:xiaomi-vacuum-card is not my card, so I can’t really help

Xiaomi vacuum card repo

Prizm78 · January 12, 2022, 2:36pm

Actually even that was confusing right now. So i replace enter my details in the raw section or in the YAML section?

Isnt the yaml section supposed to fill in the information or generate for me, or where am I going wrong here? I took the data from Room 16" which i got from the map extractor. Or would you like to fill in one sample room for me based on Room 16 from my map extractor data, then i can see how it look like? A screenshot how it should be filled would be enough for me

3_14 · January 12, 2022, 2:47pm

You have to paste this stuff (without modifying) in dev tools > templates

If you want a more detailed example you can check it out here

Prizm78 · January 12, 2022, 3:12pm

Seems to be a mistake in the template code from pastebin:

3_14 · January 12, 2022, 3:15pm

Right, I have accidentally removed too much. It is fixed now

yaruslavm · January 12, 2022, 7:35pm

hey @3_14

thanks for answer earlier , i created a custom button to mimic the custom:xiaomi-vacuum-card.
now i am able to run a pop up.

i have a question about the functionality:
i redefined all the rooms with the hint options from the docs and i have mapped all my rooms, will the invisible walls and no-go zones that were defined in the app apply? or i need to somehow define them again.