Rewritten (v3.0.0-alpha-5)

[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

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-5).

[jeremysherriff]

Looking great - and I was surprised that there seemed to be no 2FA needed?

I see a small issue with the config flow edit function, the returned response seems missing a piece:

On my Dev HA instance, I have migrated the config in exactly as I have it for the old v2.x code on my production HA instance, in order to compare. I have tried to replicate the colours from the Mi Home app as faithfully as possible, currently happy with what I see:

I am looking forward to seeing the camera responsiveness with the next scheduled cleaning 👍

The thing that prevents me moving this into my production HA instance: I need some attributes for automation purposes
eg room_numbers, vacuum_room_name, vacuum_room.

[fay000fay]

很不幸的是，我还是需要2FA 验证，但是我复制了提示的 URL 验证地址到浏览器，并用中国的手机账号以及密码登陆并且填完了验证码，网页端显示“OK”。但是 HOME ASSISTANT 里还是登陆不了。

[MichalWalder]

@PiotrMachowski this looks great. Thanks for your work! I added my Xiaomi S20 successfully but getting this message in integration.

[PiotrMachowski]

@MichalWalder I suspect your vacuum was detected as "unsupported", am I correct?

[MichalWalder]

@PiotrMachowski correct

[PiotrMachowski]

@MichalWalder thanks for your report. Unfortunately your vacuum model still doesn't work with current version of Map Extractor