That explains why I didn’t find it ! No worry, thank you for such a fast answer 
I’m loving it !
Here’s what it looks like :
3 Likes
I want to add it in a next big update 
A big update with multi-floor map?
1 Like
I’d like to select the plan before to clean the floor
2 Likes
Hi, I tried installing via HACS but I don’t see the card when trying to add new cards…
BTW I was able to install the cloud map add-on and I added as a picture element, but I want the map card so I can send zoned cleanup commands with predefined map
You have to add it manually in yaml, currently this card doesn’t have a GUI editor
Oh, got it. Thanks, it worked.
What should I do with this calibration error?
This is my Camera config
- platform: xiaomi_cloud_map_extractor
host: 192.168.***
token: ******
username: ****
password: ****
draw: ['all']
attributes:
- calibration_points
What attributes does camera entity has in developer tools?
hi
Will it be usable for Xiaomi Mi Robot Vacuum-Mop Essential as well?
It should be
Everything was working fine for a looooong time but for the past few days, the vacuum doesn’t respond to any of the modes. When I press start, I get the notification “Command sent!” but nothing happens.
I definetly haven’t changed anything in the card.
If it helps, the live camera location of the vacuum still works.
The card config is:
calibration_points:
- map:
x: 72
'y': 733
vacuum:
x: 24618
'y': 27310
- map:
x: 78
'y': 77
vacuum:
x: 32718
'y': 27310
- map:
x: 1127
'y': 733
vacuum:
x: 24618
'y': 14410
entity: vacuum.xiaomi_vacuum_cleaner
map_image: /local/FP_Ground_Floor_v2.png
service: vacuum.send_command
type: custom:xiaomi-vacuum-map-card
zones:
- - - 29000
- 24000
- 33500
- 28150
- - - 29000
- 20250
- 33500
- 24000
- - - 24700
- 20250
- 29000
- 26500
- - - 24700
- 14000
- 29700
- 20250
- - - 29700
- 16500
- 33500
- 20260
Do you have any suggestion what might caused this?
Are there any errors in HA logs?
WARNING (MainThread) [homeassistant.helpers.service] Unable to find referenced entities vacuum.xiaomi_vacuum_cleaner
Searching a bit more I am thinking it might have to do with the integration of the vacuum. I need to check A bit more…
This looks awesome! Mind sharing your config?
You have to remove and add the vacuum to HA again
1 Like
Thanks, that looks amazing!
Hi @3_14 - great card. My only issue is to do with the Zones. If I send the vacuum (S6 MaxV) out to a Target, it is about 2-3m off where it should be going. Additionally, if I try to use Zoned cleanup, immediately it says ‘cannot find the zone, going back to dock’. Lastly, when I hit Zones, it juist comes up with one massive zone which does not cover the entire home (see pic below). I am guessing its either my config or something in the MiHome App? I am really lost on this one.
Card Config:
entity: vacuum.roborock_vacuum_a10
map_camera: camera.xiaomi_cloud_map_extractor
style: |
ha-card .preview {
background-color: var(--secondary-background-color);
}
calibration_points:
- vacuum:
x: 25500
'y': 25500
map:
x: 466
'y': 1889
- vacuum:
x: 26500
'y': 26500
map:
x: 730
'y': 1625
- vacuum:
x: 25500
'y': 26500
map:
x: 466
'y': 1625
zones:
- - - 25500
- 25500
- 26500
- 26500
- - - 24215
- 28125
- 29465
- 32175
- - - 24245
- 25190
- 27495
- 27940
- - 27492
- 26789
- 28942
- 27889
- - - 28972
- 26715
- 31072
- 27915
- - 29457
- 27903
- 31107
- 29203
- - 30198
- 29215
- 31498
- 31215
- - 29461
- 31228
- 31511
- 32478
Camera YAML:
- 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
Camera State Attributes:
access_token:
calibration_points:
- vacuum:
x: 25500
'y': 25500
map:
x: 265
'y': 254
- vacuum:
x: 26500
'y': 25500
map:
x: 285
'y': 254
- vacuum:
x: 25500
'y': 26500
map:
x: 265
'y': 234
model: roborock.vacuum.a10
used_api: xiaomi
friendly_name: Xiaomi Cloud Map Extractor
entity_picture: >-
/api/camera_proxy/camera.xiaomi_cloud_map_extractor?token=
supported_features: 1
This is because your calibration is invalid.
If you use xiaomi_cloud_map_extractor you don’t have to calibrate the camera on your own, it can figure out everything by itself You just have to add camera_calibration: true and remove current calibration_points (example config)
1 Like