Rewritten (v3.0.0-alpha-21) - Improved reauthentication

[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
• Added logging in with QR code (based on code by @maksp86 and @j1kwen)
• Added sensor/binary sensor entities
• Removed server selection step
• Improved handling of unsupported vacuums
• Excluded unnecessary attributes from recorder
• Improved diagnostics
• Added handling errors during device discovery
• Fixed vacuum selection during setup
• Fixed reauthentication
• Added refresh button entity
• Added auto updating switch entity
• Fixed handling multiple instances of integration
• Added automatic YAML migration
• Ijai support (thanks, @maksp86!)
• Removed credentials from debug log
• Improved reauthentication

Breaking changes

• Integration has to be removed from yaml and added again using UI
• Most of attributes of camera entity have been removed and added as separate entities
• It is no longer possible to turn on/off the camera entity - use appropriate switch instead

---

This discussion was created from the release Rewritten (v3.0.0-alpha-21) - Improved reauthentication.

[arsenal3008]

What do you mean, It is no longer possible to turn on/off the camera entity - use appropriate switch instead I didn't quite understand?

[PiotrMachowski]

These changes are compared to the latest v2 release - there was an option to use camera.turn_on and camera.turn_off actions, now there is a switch entity that allows to do it.

[arsenal3008]

These changes are compared to the latest v2 release - there was an option to use camera.turn_on and camera.turn_off actions, now there is a switch entity that allows to do it.

This one?

[PiotrMachowski]

This one:

[arsenal3008]

This one:

This is an analog "disable_vacuum_camera_update_when_docked.yaml"?

[PiotrMachowski]

No, it is not. Automation created by this blueprint won't work with v3.0.0, but its functionality is now implemented inside Map Extractor.

[rroblik]

Working fine for me on my old S50 ! Was login failed error on v2, never worked (new HA user). Now in v3 working like a charm !

[wtstreetglow]

Hello, just letting you know I gave reconfiguring (after removing the old yaml configuration) this a try within home assistant today and both authentication methods failed. With the captcha, even when I knew I was typing in the correct characters within the home assistant dialog, it kept saying it failed. With the qr code method, when clicking the "link" or using the photo method by using the cell phone to take me to the link, it just took me to a page with a bunch of text. Is there something I can provide to help with tracking down these issues or is this expected behavior at this point.

[PiotrMachowski]

Can you check if tokens extractor works for you?

https://github.com/PiotrMachowski/Xiaomi-cloud-tokens-extractor

[wtstreetglow]

Can you check if tokens extractor works for you?

https://github.com/PiotrMachowski/Xiaomi-cloud-tokens-extractor

I can, I will give it a try when I get back home this evening. I feel like I remember using that when I originally setup with yaml method the first time around a few years ago. I will let you know the result.

[PiotrMachowski]

a few years ago

Yeeeah, but a lot has changed ;)

[wtstreetglow]

@PiotrMachowski I apologize for the late reply. The token extractor did work for me. I went to verify in my secrets.yaml file and the results match what is shown by the extractor. I also went to use the gui configuration. And it allowed me to configure/ authenticate both of the vacuums at my home. Thank you so much for all of the effort you have put into this over the years. Do you have somewhere I could contribute? I am very thankful for what you have done. Lastly, with the historic "cloud map extractor". I seem to remember the need to disable the map update when docked. Is this still a necessity with the new version?

[PiotrMachowski]

I seem to remember the need to disable the map update when docked. Is this still a necessity with the new version? No, it is now built-in into the integration

[simonbosschieter]

I have successfully set up the integration via the UI. Now I want to customize the map colors (to match my dashboard theme).

However, it seems I can only do this by adding the full configuration to configuration.yaml, which requires me to re-enter my username and password.

Question: Is there a way to define only the colors section in YAML and inherit the credentials/connection from the existing UI integration? Or is the full YAML config (including credentials) mandatory for the map extractor to work, even if the device is already in HA via the UI?

[arsenal3008]

I have successfully set up the integration via the UI. Now I want to customize the map colors (to match my dashboard theme).

However, it seems I can only do this by adding the full configuration to configuration.yaml, which requires me to re-enter my username and password.

Question: Is there a way to define only the colors section in YAML and inherit the credentials/connection from the existing UI integration? Or is the full YAML config (including credentials) mandatory for the map extractor to work, even if the device is already in HA via the UI?

Color is adjusted from the application

Screenrecorder-2025-12-23-19-21-10-212.mp4

[baiandin]

Doesn't work any more. Clear install didn't help.
2026-01-06 20:23:15.349 ERROR (MainThread) [custom_components.xiaomi_cloud_map_extractor.config_flow] Unexpected exception while attempting to Miio cloud get devices
2026-01-06 20:23:15.349 ERROR (MainThread) [custom_components.xiaomi_cloud_map_extractor.config_flow] Connection timeout to host https://us.api.io.mi.com/app/v2/homeroom/gethome?data=...

[arsenal3008]

Doesn't work any more. Clear install didn't help. 2026-01-06 20:23:15.349 ERROR (MainThread) [custom_components.xiaomi_cloud_map_extractor.config_flow] Unexpected exception while attempting to Miio cloud get devices 2026-01-06 20:23:15.349 ERROR (MainThread) [custom_components.xiaomi_cloud_map_extractor.config_flow] Connection timeout to host https://us.api.io.mi.com/app/v2/homeroom/gethome?data=...

#700 (comment)

[wtstreetglow]

Thank you for your response!! Very appreciative.Sent from my iPhoneOn Jan 7, 2026, at 8:57 PM, Piotr Machowski ***@***.***> wrote: I seem to remember the need to disable the map update when docked. Is this still a necessity with the new version? No, it is now built-in into the integration —Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you commented.Message ID: ***@***.***>

[Viproz]

I switched to this version a few weeks ago since the old one wasn't working any more, setup worked flawlessly, I entered the code received by email and it has been working without an issue ever since.
Using a viomi.vacuum.v7 device.

Thank you very much for all the work!

[Jirik6]

I updated to this version since the old one wasn't working any more, everthing working without an issue ever since.
Pls one question: I deleted old automatization for disable depr. cameras. Now is disable loading pictures automatic in integration? it looks like that answer is yes. :)

[PiotrMachowski]

Yes, in current version of the integration the old method of disabling the camera entity is no longer supported - this mechanism is now built info the integration itself

[Jirik6]

Thanks! Everthing is perfect now.J.Odesláno z iPhonu28. 1. 2026 v 11:38, Piotr Machowski ***@***.***>: Yes, in current version of the integration the old method of disabling the camera entity is no longer supported - this mechanism is now built info the integration itself —Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you commented.Message ID: ***@***.***>