Xiaomi-cloud-tokens-extractor VS Home-Assistant-custom-components-Xiaomi-Cloud-Map-Extractor

So, to get work, you need to extract the encrypted key with this program (https://github.com/PiotrMachowski/Xiaomi-cloud-tokens-extractor/releases/latest/download/token_extractor.exe)

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