The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning. Learn more →
Home-Assistant-custom-components-Xiaomi-Cloud-Map-Extractor Alternatives
Similar projects and alternatives to Home-Assistant-custom-components-Xiaomi-Cloud-Map-Extractor
-
lovelace-xiaomi-vacuum-map-card
This card provides a user-friendly way to fully control map-based vacuums in Home Assistant. Supported brands include Xiaomi (Roborock/Viomi/Dreame/Roidmi/Valetudo/Valetudo RE), Neato, Wyze, Roomba, Ecovacs (and probably more).
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
-
Xiaomi-cloud-tokens-extractor
This tool/script retrieves tokens for all devices connected to Xiaomi cloud and encryption keys for BLE devices.
-
bumper
A standalone and self-hosted implementation of the central server used by Ecovacs vacuum robots.
-
WorkOS
The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.
-
iphonedetect
A custom component for Home Assistant to detect iPhones connected to local LAN, even if the phone is in deep sleep.
Home-Assistant-custom-components-Xiaomi-Cloud-Map-Extractor reviews and mentions
-
Alexa, clean the kitchen (Using Valetudo with Home Assistant)
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.
- Do you use roborock or mi home app?
-
Can you save the lidar mapping data off the unit?
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.
-
Is there any way to create moving objects in a Lovelace picture element?
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
- Roborock standby problem
- Mi vacuum in Lovelace /w real-time map.
-
A note from our sponsor - WorkOS
workos.com | 25 Apr 2024
Stats
PiotrMachowski/Home-Assistant-custom-components-Xiaomi-Cloud-Map-Extractor is an open source project licensed under MIT License which is an OSI approved license.
The primary programming language of Home-Assistant-custom-components-Xiaomi-Cloud-Map-Extractor is Python.
Popular Comparisons
- Home-Assistant-custom-components-Xiaomi-Cloud-Map-Extractor VS lovelace-xiaomi-vacuum-map-card
- Home-Assistant-custom-components-Xiaomi-Cloud-Map-Extractor VS ha-rest980-roomba
- Home-Assistant-custom-components-Xiaomi-Cloud-Map-Extractor VS ble_monitor
- Home-Assistant-custom-components-Xiaomi-Cloud-Map-Extractor VS Xiaomi-cloud-tokens-extractor
- Home-Assistant-custom-components-Xiaomi-Cloud-Map-Extractor VS bumper
- Home-Assistant-custom-components-Xiaomi-Cloud-Map-Extractor VS xfinity-usage
- Home-Assistant-custom-components-Xiaomi-Cloud-Map-Extractor VS thermal
- Home-Assistant-custom-components-Xiaomi-Cloud-Map-Extractor VS lampa.py
- Home-Assistant-custom-components-Xiaomi-Cloud-Map-Extractor VS Valetudo
- Home-Assistant-custom-components-Xiaomi-Cloud-Map-Extractor VS iphonedetect
Sponsored