Rewritten (v3.0.0-alpha-2)

[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

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

[vini59fr]

Hello

where's the UI ? :D
I removed old config from configuration.yaml, updated to alpha2, then restart HA .. but I don't know where is the UI to configure it

Thank's

[vini59fr]

Found it ... have to re-install the integration after the hacs update

[CYSShop]

Good afternoon. How do you enlarge the map? In version 2.x.x it was possible to interact with the map. Is there any plans to do the same in version 3?

[PiotrMachowski]

@CYSShop sure, in the "Configure" menu

[CYSShop]

@CYSShop sure, in the "Configure" menu

But it's not currently realized, right? I can't find the right parameter

[PiotrMachowski]

It is. You can access it when you open the config entry

[nightshadow931]

Hi Piotr,

I tried this version yesterday, successfully installed it and I can see the map of my Xiaomi Mop 2 Pro+. I let it clean one room, the map updated like 30s later with the position of my robot, but since then it's stuck on that same position. The robot cleaned the room and went back to the dock to charge as usual.
One day later, I still see the map of like ~30s after I told it to clean.

Let me know what else I can provide to help.

[nightshadow931]

What do you mean by "very rarely"? Have you checked if it is updated when vacuuming?

Hey mate, sorry for the late reply, I'm quite busy these days.
Actually it does not update it at all still, I've just tested it. It only updates when I open the Xiaomi app, same as before.
And yes, I have updated to alpha 3 :)

[PiotrMachowski]

Can you check if service calls from this thread refresh the map?

[nightshadow931]

Can you check if service calls from this thread refresh the map?

It does..but not every time. For example I call the service once and it updates the map. Then after 1min I call it again, but then it doesn't update. Then after 2mins I call it again and it works.
Kinda not really straight forward..

[PiotrMachowski]

Which service call have you used?

[nightshadow931]

Which service call have you used?

This one

service: xiaomi_miot.call_action
target:
  entity_id: vacuum.dreame.p2028
data:   
  entity_id: vacuum.dreame.p2028   
  siid: 6
  aiid: 1
  params:
    - piid: 2
      value: '{"frame_type":"I"}'

[vini59fr]

Hi
I have an issue with my map size (roborock.vacuum.s5)
By default, the map is small :

On the previous yaml version, I used these settings :

But when I use the same settings on the UI, my map is completely weird (but the last cleaned areas and the forbidden area seems at the good size)

[PiotrMachowski]

Yeah, there is a problem with the left trim :/

[vini59fr]

Yeah, there is a problem with the left trim :/

Is it fix on alpha 3 ?

[PiotrMachowski]

No, it's not. But I have fixed it locally

[PiotrMachowski]

Fixed in v3.0.0-alpha-4

[jeremysherriff]

oops - this comment was meant for alpha-5 release