Thank you @3_14, I’ll remove it soon.
I’m configuring the cards and when a end the configuration I’ll remove the needless attributes.
Hi I have a Viomi S9 robot vacuum cleaner.
When I choose a room to clean, I receive this message " Entity vaccum.viomi_v18_e360_robot_cleaner does not support this service"
and “Service xiaomi_miio.vaccum_clean_zone not found” when i choose zone cleanup.
Which integration have you used to add this vacuum to HA?
xiaomi miot auto
Only this one supports it.
If you use Xiaomi Miot Auto you have to configure everything manually based on Miot spec. You might try to use/adjust this one
Hello, and thank you for the card. I have already configured it and would like to integrate it into my existing Picture Element Card based on my floor plan. Unfortunately, the Image-Card does not update automatically when I start the vacuum cleaner. I would like everything to be transparent so that only the vacuum cleaner and its path are visible.
I have now used the image card, but unfortunately, it doesn’t update. When I start the vacuum, I see movement once, but then nothing happens anymore, even when I refresh the browser.
- type: image
entity: camera.xiaomi_cloud_map_extractor
camera_image: camera.xiaomi_cloud_map_extractor
camera_view: live
style:
top: 10%
left: 10%
width: 100%
height: 100%
transform: scale(1.0)
camera:
- platform: xiaomi_cloud_map_extractor
host:
token:
username:
password:
country: "de"
attributes:
- calibration_points
- rooms
- room_numbers
store_map_path: "/tmp"
colors:
color_map_outside: [0, 0, 0, 0]
color_map_wall: [0, 0, 0, 0]
color_map_wall_v2: [34, 35, 36]
color_path: [255, 255, 255]
color_charger: [8, 120, 36]
color_robo: [255, 255, 255]
color_scan: [0, 0, 0, 0]
color_unknown: [0, 0, 0, 0]
color_obstacle: [0, 0, 0, 0]
color_grey_wall: [0, 0, 0, 0]
color_ignored_obstacle: [0, 0, 0, 0]
color_zones: [109, 37, 37]
color_zones_outline: [0, 0, 0, 0]
color_virtual_walls: [109, 37, 37]
color_no_go_zones: [109, 37, 37]
color_no_go_zones_outline: [0, 0, 0, 0]
color_no_mop_zones: [109, 37, 37]
color_no_mop_zones_outline: [0, 0, 0, 0]
color_robo_outline: [255, 255, 255, 0]
room_colors:
1: [255, 255, 255, 1]
2: [255, 255, 255, 1]
3: [255, 255, 255, 1]
4: [255, 255, 255, 1]
draw:
- charger
- path
- goto_path
- predicted_path
- no_go_zones
- no_mopping_zones
- vacuum_position
- virtual_walls
- zones
map_transformation:
scale: 1
rotate: 180
scan_interval:
seconds: 10
auto_update: true
Room selection and cleaning are now working, but unfortunately, I can’t get zone cleaning to start in any way. Thank you very much for your help. Best regards!
I have the Dreame L10s Ultra. No, I didn’t use the blueprint.
You can use this integration instead:
1 Like
I’m going to buy that vacuum cleaner. Does it integrate well with home assistant?
Hi
Xiaomi Mop 2 Pro (ijai.vacuum.v3) support pls? 
1 Like
I just got a X20 Xiaomi vacuum thats saying its not supported . haas-miot integration works and i can connect it to HA . Any suggestions?
These are the error logs:
2024-07-13 14:21:35.196 WARNING (ImportExecutor_0) [homeassistant.components.camera] SUPPORT_ON_OFF was used from xiaomi_cloud_map_extractor, this is a deprecated constant which will be removed in HA Core 2025.1. Use CameraEntityFeature.ON_OFF instead, please report it to the author of the 'xiaomi_cloud_map_extractor' custom integration
2024-07-13 14:21:35.205 WARNING (ImportExecutor_0) [homeassistant.components.camera] SUPPORT_ON_OFF was used from xiaomi_cloud_map_extractor, this is a deprecated constant which will be removed in HA Core 2025.1. Use CameraEntityFeature.ON_OFF instead, please report it to the author of the 'xiaomi_cloud_map_extractor' custom integration
This is in my .yaml file
camera:
- platform: xiaomi_cloud_map_extractor
host: 192.168.xxx
token: 697574624f5xxx933566c32455731
username: yadayada
password: blahblah
draw: ['all']
attributes:
- calibration_points
Hi, I don’t understand if the vacuum cleaner is running, the map is visible, but after some time it becomes inaccessible. What is wrong ? Vacuum Xiaomi S5
camera:
- platform: xiaomi_cloud_map_extractor
host: 192.168.3.151
token: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
username: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
password: xxxxxxxxxx
country: cn
name: siurblys
draw: ["all"]
map_transformation:
scale: 1
rotate: 180
trim:
top: 10
bottom: 20
left: 30
right: 40
auto_update: false
store_map_raw: true
attributes:
- calibration_points
That is an issue with blocked Xiaomi cloud connection 
I have been working on workaround in Map Extractor, I have to finally finish it
Hi @3_14, any news about workaround to blocked connection?
I’m really looking forward to using it, since I can’t use this version at all.