Valetudo
Retain local control of compatible robot vacuums and reduce vendor-cloud dependence.
Specific modification route · Family valetudo · Reviewed 2026-10-20
What changes for this device
Before
Some robot vacuums depend on vendor-cloud control while their mechanical parts and sensors still work.
After
A local service replaces cloud interfaces on supported devices with the necessary access.
Valetudo explicitly is not generic replacement firmware. Its support list is exhaustive; do not assume an unlisted model works. Even Xiaomi 1C units have different hardware revisions, and only specified internal models are supported. Xiaomi V1 production dates also affect whether disassembly is required. Removing cloud dependence does not add missing vendor mapping or hardware capabilities.
A good fit for
People with an exact model on the list who will prepare model-specific tools and recovery methods.
Not a good fit for
People with unlisted models or wanting to fix physical faults such as batteries or motors.
Proposed reproduction checks
- Check the internal model, production batch and corresponding root instructions.
- Test cleaning and local control with internet access disconnected.
- Check maps, docking, persistent configuration and recovery conditions.
These hardware checks have not been performed by this catalog.
What you need
- Method
- Cloud service replacement
- Difficulty (editorial judgment)
- Advanced
- Disassembly
- Model-dependent
- Soldering
- Model-dependent
- Cloud API / service
- Not required
- Cost amount
- Not priced / UNKNOWN
Possible additional costs
- Model-specific flashing/connection tools
Prices have not been checked. An open-source license does not make hardware, hosting, electricity or cloud services free.
Risks and recovery
Data-loss risk: Possible; Bricking risk: Workflow-dependent. Route-based guidance, not hardware-tested; these outcomes are not inevitable for every device.
Back up according to the exact robot's rooting method. This review has not verified unbricking for any model.
Recovery documentation (no verified link)
Evidence and maintenance
E1 · Source code & deployment docs
The README describes a local cloud-replacement layer running on vendor firmware. Official documentation supplies the supported-robot list and model-specific installation methods.
Catalog hands-on testing: not performed. Independent reproduction: not verified.
- Maintenance
- Repository not archived
- Last GitHub push
- 2026-10-18T17:15:02Z
- Repository license
- Apache-2.0
An unarchived repository or recent push does not prove a model works. Mirror migration does not mean development has stopped.
A root license or README declaration does not establish the same license for firmware, models, brands and third-party components.
Sources
- Upstream documentation · 2026-10-20 · Content reviewed
- Official compatibility / installation · 2026-10-20 · Content reviewed
Original sources may be in Chinese or English. Review means reading public material; recheck upstream models, services and firmware before acting.