ble_monitor VS Home-Assistant-custom-components-Xiaomi-Cloud-Map-Extractor

For those who are interested, the Passive BLE monitor Home Assistant integration supports quite a few thermometers. The Govee support is based on a component I wrote, Home-Is-Where-You-Hang-Your-Hack/sensor.goveetemp_bt_hci/. If you are looking for just the decoder, check out Thrilleratplay/GoveeWatcher.

However, I use some of their other (older?) BLE temp sensors, and for Home Assistant, you can use this driver for them: https://github.com/custom-components/ble_monitor

FWIW, if your HASS is running on a device (like a Raspberry Pi) that has Bluetooth, you might be able to get away with a custom component like https://github.com/custom-components/ble_monitor instead. Of course, if your setup is working for you already there isn't much incentive to change it.

https://github.com/custom-components/ble_monitor will work with govee

Once again, who knows better how to install it other than the guys who made it? No one , luckily for you, even being an Hacs integration (so not necessarily polished) the documentation seems very well written

Yes, there's an installable component with HACS : https://github.com/custom-components/ble_monitor It's working really well 👌

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