Valetudo aims to be a vendor-agnostic abstraction and cloud replacement for vacuum robots which started as a standalone binary on rooted roborock vacuums.
View the Project on GitHub Hypfer/Valetudo
Newcomer Guide Late 2021 Why Valetudo? Getting Started Supported Robots Capabilities Overview Rooting instructions Upgrading Buying supported robots
Valetudo Companion (Android) Valeronoi Lovelace Valetudo Map Card I can't believe it's not Valetudo node-red-contrib-valetudo Fun & Games Other Noteworthy Projects
MQTT Home Assistant Node-RED openHAB
FAQ Frequently requested features Roborock, Files to backup Troubleshooting
Building and Modifying Valetudo Valetudo core concepts MQTT
Supported Dreame Devices Supported Roborock Devices Supported Viomi Devices Newcomer Guide Early 2021
This page features an autogenerated overview of all robots supported by Valetudo including their supported capabilities.
To find out what those do, check out the capabilities overview section of the docs.
You also might want to take a look at the Buying supported robots page.
This is just the autogenerated overview because it’s hard to write documentation for everything and keep that up to date.
Keep in mind that rooting instructions will differ for each of these or might not even be available at all.
Just because the code would - in theory - support a Robot doesn’t necessarily mean that you can simply buy it and put Valetudo on it.
To find out if you can install Valetudo on your robot, check out the Rooting Instructions. If you can’t find it there, it’s most likely not possible (yet?). Another source is https://dontvacuum.me/robotinfo/. Search for “Root method public?”. If it’s listed as “no”, then it’s certainly not possible for you to run Valetudo on it.
There’s also some more information regarding whether or not you should buy a specific robot below the table.
The recommended Valetudo binary architectures armv7, armv7-lowmem and aarch64 are also listed for every robot. Even though armv7 binaries work on aarch64 robots, using the correct binary for your robot is recommended.
Again:
This is just an autogenerated overview based on the codebase at the time of generation.
Don’t take this as “Everything listed here will be 100% available and work all the time”.
| Capability | 1C | 1T | D9 Pro | D9 | F9 | L10 Pro | MOVA Z500 | Z10 Pro | S4 Max | S4 | S5 Max | S5 | S6 MaxV | S6 Pure | S6 | S7 | V1 | V7 |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| AutoEmptyDockAutoEmptyControlCapability | No | No | No | No | No | No | No | Yes | No | No | No | No | No | No | No | No | No | No |
| AutoEmptyDockManualTriggerCapability | No | No | No | No | No | No | No | Yes | No | No | No | No | No | No | No | No | No | No |
| BasicControlCapability | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes |
| CarpetModeControlCapability | No | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes |
| CombinedVirtualRestrictionsCapability | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | No | Yes |
| ConsumableMonitoringCapability | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes |
| CurrentStatisticsCapability | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes |
| DoNotDisturbCapability | No | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes |
| FanSpeedControlCapability | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes |
| GoToLocationCapability | No | No | No | No | No | No | No | No | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | No |
| KeyLockCapability | No | No | No | No | No | Yes | No | Yes | No | No | No | No | No | No | No | Yes | No | No |
| LocateCapability | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes |
| ManualControlCapability | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes |
| MapResetCapability | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | No | Yes |
| MapSegmentEditCapability | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | No | Yes |
| MapSegmentRenameCapability | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | No | Yes |
| MapSegmentationCapability | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | No | Yes |
| MapSnapshotCapability | No | No | No | No | No | No | No | No | No | No | No | Yes | No | No | Yes | No | No | No |
| MappingPassCapability | No | Yes | Yes | Yes | Yes | Yes | Yes | Yes | No | No | No | No | No | No | No | No | No | No |
| ObstacleAvoidanceControlCapability | No | No | No | No | No | Yes | No | Yes | No | No | No | No | No | No | No | No | No | No |
| PendingMapChangeHandlingCapability | No | Yes | Yes | Yes | Yes | Yes | Yes | Yes | No | No | No | No | No | No | No | No | No | No |
| PersistentMapControlCapability | Yes | Yes | No | No | Yes | No | Yes | No | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | No | Yes |
| SpeakerTestCapability | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes |
| SpeakerVolumeControlCapability | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes |
| TotalStatisticsCapability | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | No |
| VoicePackManagementCapability | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes |
| WaterUsageControlCapability | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | No | No | Yes | No | Yes | No | No | Yes | No | Yes |
| WifiConfigurationCapability | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes |
| ZoneCleaningCapability | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes |
okay
best effort
✔
This model is okay but has some issues that keep it from being fully recommendable
armv7
vSLAM and a small battery, though there are persistent maps and everything seems to work
good
best effort
✔
This model is okay but has some issues that keep it from being fully recommendable
aarch64
vSLAM :(
good
yes
✔
This model is okay but has some issues that keep it from being fully recommendable
armv7-lowmem
256MB RAM are problematic when dealing with large floorplans
Basically the same as the D9
good
yes
✔
This model is okay but has some issues that keep it from being fully recommendable
armv7-lowmem
256MB RAM are problematic when dealing with large floorplans
good
best effort
✔
This model is okay but has some issues that keep it from being fully recommendable
armv7
vSLAM :(
good
yes
✔
Can’t go wrong with this model
aarch64
None
good
best effort
✔
This model is okay but has some issues that keep it from being fully recommendable
armv7
vSLAM :(
good
yes
✔
get it right now!
aarch64
The auto-empty-dock is a neat addition
okay
some effort
✔
This model is okay but has some issues that keep it from being fully recommendable
armv7-lowmem
Root requires soldering.
Also, 256MB RAM and NAND are pretty bad HW specs which can cause issues.
okay
some effort
✔
This model is okay but has some issues that keep it from being fully recommendable
armv7
Root requires soldering.
okay
some effort
✔
This model is okay but has some issues that keep it from being fully recommendable
armv7-lowmem
Root requires soldering.
Also, 256MB RAM and NAND are pretty bad HW specs which can cause issues.
okay
yes
✔
outdated but still okay-ish
armv7
Still works finefor most use-cases
bad
none
✔
This model has issues and therefore isn’t recommended (see comment)
armv7
It’s basically impossible to root this thing.
okay
some effort
✔
This model is okay but has some issues that keep it from being fully recommendable
armv7-lowmem
Root requires soldering.
Also, 256MB RAM and NAND are pretty bad HW specs which can cause issues.
okay
yes
✔
outdated but still okay-ish
armv7
Still works fine for most use-cases
bad
none
✔
This model has issues and therefore isn’t recommended (see comment)
armv7-lowmem
This robot is very expensive while also featuring incredibly weak hardware, which is something that I personally do not want to support.
okay
some effort
✔
outdated. not recommended (anymore)
armv7
Unfortunately, this model is lacking basic features such as a persistent map which is insufficient in 2021+
meh
none
✔
This model has issues and therefore isn’t recommended (see comment)
armv7
This model is actually just a White-Label Product with a custom Miio Software stack which is EOL and therefore doesn’t receive any meaningful software updates.
Overall, it’s just weird and annoying.
This page has been autogenerated.
Autogeneration timestamp: 2021-12-05T11:10:26.572Z