Xiaomi Cloud Vacuum Map Extractor

Hi,

indeed works… just a stupid question… is it possible with v3 to manipulate the picture like in the v2 version (colors, room_colors…)?

Yes, you can do it in the options of config entry. Just click the cog icon

Hi, is it possible to add support for xiaomi.vacuum.d109gl? The integration can be added, but it doesn’t start and it reports an error: argument of type ‘NoneType’ is not iterable.

I have version v3.0.0.-aplha-9

Thank you very much

Someday, maybe. No promises

2 Likes

If I can help in any way with debugging, I am available. Thank you

I haven’t added support for new vacuums, but I try to make it easier to download data for decoding form them. Can you check how does the latest alpha handle it? I care mostly about setup process and downloading diagnostic data.

Hello, I’m trying to setup map extractor.
I have a Roborock S6 Pure and i’m getting this error in the log:
2025-10-23 21:18:20.123 WARNING (SyncWorker_7) [custom_components.xiaomi_cloud_map_extractor.camera] Got exception while fetching the state: Unable to discover the device 10.10.20.104

Which port are used for communication, is it: 54321?

nc -zv 10.10.20.104 58867
Connection to 10.10.20.104 58867 port [tcp/*] succeeded!

nc -zv 10.10.20.104 54321
nc: connect to 10.10.20.104 port 54321 (tcp) failed: Connection refused

Not sure what i’m doing wrong. please help.

Yes, the port should be 54321. Which version of Map Extractor have you used? Do you use Xiaomi Home app or Roborock app?

I’m using version 2.2.5 of map extractor. Roborock app is installed on my phone version 4.53.04.

Map Extractor doesn’t work with Roborock app, if you use Roborock app then you have to use Roborock integration

Thanks for clarifying that. So if i start to use Xiaomi app i can then start to use your implementation?

Well, yes, but you should be fine now with using Roborock integration as well.

hi Im trying to add Viomi V3:
my conf:
camera:

  • platform: xiaomi_cloud_map_extractor
    host: 192.168.1.6
    token: xxxxxxxxxxxxxxxxxxxxxxxxxxx
    username: yyyyy
    password: zzzz
    country: “cn”
    name: “Marysia”
    draw: [‘all’]
    attributes:
    • calibration_points
    • rooms

e[31m2025-10-30 20:57:07.154 ERROR (SyncWorker_4) [custom_components.xiaomi_cloud_map_extractor.camera] Unable to log in, check credentialse[0m
e[33m2025-10-30 20:57:07.488 WARNING (SyncWorker_4) [miio.device] Found an unsupported model ‘viomi.vacuum.v13’ for class ‘RoborockVacuum’. If this is working for you, please open an issue at https://github.com/rytilahti/python-miio/e[0m
e[33m2025-10-30 20:57:16.639 WARNING (MainThread) [homeassistant.helpers.entity] Update of camera.marysia is taking over 10 secondse[0m
[31m2025-10-30 20:57:27.735 ERROR (SyncWorker_4) [miio.miioprotocol] Got error when receiving: timed oute[0m
e[33m2025-10-30 20:57:27.741 WARNING (SyncWorker_4) [custom_components.xiaomi_cloud_map_extractor.camera] Got exception while fetching the state: No response from the devicee[0m

used same credentials to add vacuum cleaner with Xiaomi Miot and i can manage vacuum cleaner from your dashboard but no map. using xiaomi home.

extractor version is v2.2.5 any ideas?

funny but today map with same configuration was loaded

Hello,

I am having a problem with the Map Extractor, and now get a “Two factor auth required (see logs)” instead of the map…

I have installed the Token Extractor 2025, but I am required to provide a Captcha image at http://127.0.0.1:31415. Unfortunately, this URL is not accessible…

I am quite lost at this point.

My vacuum entity is vacuum.xiaomi_vaccum_robot
The plateform is marutoweb/viomise

It worked for some time but now it is impossible to get the map anymore…

Any suggestion would be greatly appreciated.

Thanks

@pawlin @sanji_japan

Xiaomi has implemented blocking requests from Map Extractor. At this moment usage of v2.x.x is a bit random, as their detection is not 100% effective. These issues are handled in the v3.0.0 version of Map Extractor, but it is not fully released yet. At this moment you can install the latest alpha version of the integration, just keep in mind it is not a final release and is subject to change.

1 Like

Brillant ! It worked.
@3_14 Really appreciate the continuous support, sent a small thank you with Revolut :slight_smile:

1 Like