Rewritten (v3.0.0-alpha-9)

[PiotrMachowski]

This is an early version of Map Extractor v3 release. It has been completely rewritten in order to provide better functionality and user experience. To use this version you have to remove old config from configuration.yaml file and use UI to add the integration again.

Caution

Please keep in mind this is not a final release, so a lot of things might change or not work at all at this moment.
Does everything work correctly, or are there some missing functionalities? Please provide feedback in the comments below.

Changes

• Added config flow
• Extracted data retrieval to a separate coordinator
• Added support for image entities
• Rewritten the code to use async communication
• Added map data caching
• Extracted map parsers to separate Python packages
• Added refreshing Dreame map
• Updated Agent ID
• Added handling captcha (based on code by @maksp86)
• Adde handling 2FA (based on code by @zpavlovic1986 and @m33ts4k0z)
• Added storing the session to prevent re-auth
• Added detecting cloud re-auth necessity
• Improved handling Dreame and unsupported vacuums

Breaking changes

• Integration has to be removed from yaml and added again using UI
• Most of attributes of camera entity have been removed
• It is no longer possible to turn on/off the camera entity

---

This discussion was created from the release Rewritten (v3.0.0-alpha-9).

[aerosh]

Hi,
The map does not display the current position of the vacuum cleaner during cleaning (while updating occurs every 5 seconds).
The vacuum cleaner is not displayed at all or is displayed with a huge delay (a couple of times per cleaning session).
I use this version because my vacuum cleaner (dreame.vacuum.p2008 (F9)) works via Mi Home and 2FA doesn't work in older versions.
Thanks!

[Maccy01]

Cześć,

Mapa nie działa z odkurzaczem Xioami Vioami V3. Po zainstalowaniu nie pojawia się encja kamery. Przy powrocie do starszej wersji encja kamery się pojawia ale niestety jest problem z uwierzytelnieniem na koncie xioami i nie wyświetla mapy-komunikat o błędnym logowaniu.

[PiotrMachowski]

Please write in English.

Have you reconfigured the integration using user interface after installing the alpha version?

[Maccy01]

1. I deleted the data from the configuration.yaml file. 2. I restarted HA. 3. I installed a new version of maps. 4. I restarted HA. 5. I reconfigured the configuration.yaml file. 6. I restarted the system. I tried many times, without success.

[PiotrMachowski]

Version 3.0.0 doesn't use configuration.yaml, you have to configure it using UI:

[Maccy01]

Thank you so much. You're the best :-) Everything works.

[Tiemichael]

I tried to setup the Xiaomi Cloud Map Extractor V3.0.0 alpha9, with my Xiaomi H40 vacuum cleaner (xiaomi.vacuum.ov51gl).
The identifcation with Username / Password -> Captcha -> OPT runs smothly, the vacuum cleaner is found, and I selected 'Unsupported'.
Too bad the setup failed with: "Failed setup, will retry: argument of type 'NoneType' is not iterable"

Attached is a debug-log
MapExtractor.log

Is there a way to overcome this issue?
Thanks!

[PiotrMachowski]

Well, if your vacuum is detected as unsupported then it wouldn't work anyway, so you haven't lost much 😉

To add a support for new vacuum platform a varying amount of reverse engineering is required. It usually also have to be performed by someone that owns this specific vacuum, which makes it even more tricky

[Tiemichael]

Yes, I selected 'unsupported'. Altough it's called 'Xiaomi-Cloud-Map-Extractor', none of the 'original' Xiaomi vacuum cleaners (xiaomi.vacuum.*) is supported.
I understand from your comment that even this detailed document is likely not sufficient.
Next time better go for another brand.

Thanks!

[PiotrMachowski]

This integration was created before xiaomi.vacuum.* appeared, and it is named this way because of Xiaomi Cloud that vacuums utilize.
Yes, this document is not sufficient, it doesn't describe retrieval and parsing of map data.
It might be possible to "someday" decode the map for your vacuum, so keep an eye on future releases :)

Also, you can check out this integration, its beta release supports some Xiaomi vacuums as well.

[heibertelf]

To add a support for new vacuum platform a varying amount of reverse engineering is required.

Waiting for Mijia devices to be awailable )

Devices found for server "cn" @ home "46******68":
   ---------
   NAME:     Mijia Robot Vacuum-Mop 3C
   ID:       10******59
   MAC:      c8:*******:46
   IP:       192.168.0.202
   TOKEN:    47*****************74
   MODEL:    ijai.vacuum.v18

Thanks for your work!

[zpavlovic1986]

I tried many ways but was not successful. Have a s20 max but cant get to the map. It is no longer local but in the cloud. I tried running xiaomi home app in rooted bluestacks with ssl off to try and pick up on api endpoints to get to the map but with no luck :( If there is anything useful i can try on it, let me know and i can try

…

On Sun 5 Oct 2025, 01:02 Piotr Machowski, ***@***.***> wrote: Well, if your vacuum is detected as unsupported then it wouldn't work anyway, so you haven't lost much 😉 To add a support for new vacuum platform a varying amount of reverse engineering is required. It usually also have to be performed by someone that owns this specific vacuum, which makes it even more tricky — Reply to this email directly, view it on GitHub <#654 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AP4QDOVXASGRCZABFNKUXF33WBGYNAVCNFSM6AAAAACIB72OBKVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTINJZGM4TCMY> . You are receiving this because you were mentioned.Message ID: <PiotrMachowski/Home-Assistant-custom-components-Xiaomi-Cloud-Map-Extractor/repo-discussions/654/comments/14593913 @github.com>

[pawg]

I have a Xiaomi S20, I'm also ready to provide any data if any preliminary guidance could be provided to reverse engineer the map retrieval, as I don't really know where to start looking.

Maybe a small guide on how it's been done with already integrated devices would be a good starting point for us badly wanting the new Xiaomi line of vacuums supported?

Anyway, thank for your fantastic work!

[PiotrMachowski]

At this moment I work on resolving all auth-related issues, I will try to add support for more devices after I am done with this part.

[pawg]

Got it! Thanks

[GCleric86]

Hi! Xiaomi Cloud Map Extractor error. Unexpected error. Roborock S5 Max. During authentication, after entering the code. What could be the cause? The one you described above? Thank you!

[GCleric86]

everything worked.

[pplucky]

Cannot find where to configure attributes and text coordinates to include room names, as per previous version.

Example:

camera:
  - platform: xiaomi_cloud_map_extractor
    name: House Map
    host: !secret vacuum_1s_ip
    token: !secret vacuum_1s_token
    username: !secret xiaomi_cloud_id
    password: !secret xiaomi_cloud_password
    draw: ['all']
    attributes:
      - calibration_points
      - vacuum_position
      - vacuum_room
    texts:
      - text: "Bedroom"
        x: 18
        y: 25
      - text: "WC"
        x: 40
        y: 20
      - text: "Son"
        x: 18
        y: 55
      - text: "Daughter"
        x: 17
        y: 78

Am I missing something or is this not yet working in alpha version.

[PiotrMachowski]

They are not available in current version

[GCleric86]

Will they be unavailable in principle, or temporarily? The scripts I created earlier for rooms work. But how do I select them so they appear like in the previous version? I saw that someone already asked today. Will they be available?

[PiotrMachowski]

I plan to migrate (almost) all of attributes from v2 to separate entities in v3. I'm not sure how will I handle texts, but potentially I will add them as well into the config

[GCleric86]

Excellent! Thanks again for the work you've done!

[PiotrMachowski]

@GCleric86 I have added sensor entities in v3.0.0-alpha-11

[Sergmasharov]

Hello! Found missing attribute: vacuum_room. It was very good to set scripts with it
state_attr('camera.xiaomi_cloud_map_extractor', 'vacuum_room')

[PiotrMachowski]

#654 (reply in thread)

I plan to migrate (almost) all of attributes from v2 to separate entities in v3. I'm not sure how will I handle texts, but potentially I will add them as well into the config

[PiotrMachowski]

@Sergmasharov I have added sensor entities in v3.0.0-alpha-11

[Sergmasharov]

Thanks for your work! Works great!