lovelace-xiaomi-vacuum-map-card VS Home-Assistant-custom-components-Xiaomi-Cloud-Map-Extractor

For me (Roborock) works https://github.com/PiotrMachowski/Lovelace-Xiaomi-Vacuum-Map-card. It should also work for roomba.

In case you mean adding to HA: check if u can add it over the Xiaomi Miio integration and then use the xiaomi vacuum map extractor and card (both repos say the S5 is supported). I then defined zones and call the commands in a script which I expose to Google Assistant as a scene called 'clean the bathroom' for instance.

Currently I'm using stock firmware, rooted. I just came back From Valetudo..it seems pretty stable to me, but it won't work well with the Home Assistant custom integration that I want to use. The area cleanup feature of that integration is the main way I'm using the vacuum (when I command itmanually) and it looks amazing.

If you only use cloud map extractor - its only visual. But if you install this - https://github.com/PiotrMachowski/lovelace-xiaomi-vacuum-map-card You can send commands to vacuum, draw sections etc., and it's using map from above integration. My vacuum drive to kitchen, to empty, every 10 cleanings, then google speaker says something like "Fuck that shit, i'm not cleaning anymore, until my bin is full". But i did it all in nodered, if you like, i will send you flow. I also hava aqara swithes, to controling light, but if i click both two times, vacuum drive to clean that room.

This is a GitHub with some extra info and a map extractor: https://github.com/PiotrMachowski/lovelace-xiaomi-vacuum-map-card

In case you mean adding to HA: check if u can add it over the Xiaomi Miio integration and then use the xiaomi vacuum map extractor and card (both repos say the S5 is supported). I then defined zones and call the commands in a script which I expose to Google Assistant as a scene called 'clean the bathroom' for instance.

There's a Xiaomi Cloud Map Extractor integration for Home Assistant, not a mod as much as a spoof maybe: that gives you the maps as you see it them the Roborock or Mi apps, and are stored on the vacuum,. I think that's it-- storing the map as a bitmap is efficient storage- and compute-wise. Screen grabbing from the app would give the same thing, I wonder what its real resolution is. Also I would guess the map is used mostly as a guide for overall positioning, and that the real LIDAR work is done while running to solve its position on the map as a 3DOF problem, and that data just churns.

Mine is done through an older method but I believe this one can do it for roborock: https://github.com/PiotrMachowski/Home-Assistant-custom-components-Xiaomi-Cloud-Map-Extractor