Rewritten (v3.0.0-alpha-12) - Recorder exclusion

[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

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

---

This discussion was created from the release Rewritten (v3.0.0-alpha-12) - Recorder exclusion.

[jeremysherriff]

Thanks @PiotrMachowski, alpha-11 and -12 together address my main reasons for staying back on v2.x
Is there anything specific you want tested to help move this forward to beta and then stable release?

[PiotrMachowski]

I plan to improve the handling of currently unsupported vacuums, primarily by enhancing the diagnostic data they return. Since the implementation for supported devices should be quite stable at this point, I will now review all open issues, pull requests, and discussions to identify any other items that need to be addressed.