Rewritten (v3.0.0-alpha-22) - Xiaomi vacuums support

[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.

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
• Xiaomi support (thanks, @aronkahrs-us!)
• Improved homes discovery error handling

Breaking changes

• Integration has been migrated to the UI - remove yaml code after automatic migration
• 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-22) - Xiaomi vacuums support.

[Korkuttum]

Hello, thank you for the update. There still seems to be an issue with Ijai support; I’m still unable to retrieve the map for my ijai.vacuum.v3 model.

[johny-mnemonic]

I am getting "Incorrect AES key length (19 bytes)" when trying to use this alpha version instead of the stable 2.2.5 (which stopped working some time ago).
I have Roborock S5 Max connected to Xiaomi DE server.
Anything I should try to find what is wrong?

[johny-mnemonic]

I have tried it again and I noticed the autodetection selected Roborock API instead of Xiaomi one, so I kept it selected instead of selecting Xiaomi like before and now it works fine.

[PiotrMachowski]

Yes, you should use Roborock API for this model.