Buying Guides

Valetudo Supported Robots 2026: Rooting & Compatibility Matrix

Firmware-level Valetudo matrix for Roborock and Dreame: PCB UART test points vs OTA laptop exploits, secure-boot gates, and revision traps for local maps in 2026.

Privacy Smart Home Research Desk Jun 01, 2026

Keywords: valetudo supported robots 2026, Valetudo compatibility matrix, Dreame UART breakout PCB rooting, Roborock OTA root Valetudo, robot vacuum secure boot Valetudo, cloud-free vacuum firmware 2026

Valetudo supported robots in 2026 are exactly the 49 models on the maintainer’s Supported Robots page—each with a tested exploit chain, not “any LiDAR vacuum.” For Roborock and Dreame (plus Xiaomi/MOVA OEM variants), your purchase decision hinges on how you gain root: OTA/laptop software exploits (legacy Roborock), UART service-port access with the Dreame breakout PCB (no motherboard soldering), or full disassembly + NAND-dependent flashes (modern Roborock). After root, Valetudo keeps LiDAR maps on the robot and exposes local HTTP + MQTT instead of vendor clouds.

Quick answer: What are Valetudo supported robots in 2026?

Only vacuums on valetudo.cloud Supported Robots—49 SKUs with documented roots. Dreame/MOVA/Xiaomi-Dreame use 3.3 V UART + Hypfer breakout PCB on service test points. Legacy Roborock S5 and old Xiaomi V1 use laptop OTA exploits. Roborock S6–Q7 Max need full disassembly; Q7 Max 2024+ NAND may block root. Flash Valetudo, join LAN, MQTT to Home Assistant, block WAN on IoT VLAN.

Source: Valetudo Supported Robots

Methodology: how this matrix was built

On 1 June 2026, we re-read every model block on Supported Robots and classified each entry by physical access interface and software exploit family, cross-checking secure-boot notes and revision traps maintainers publish¹. We did not rank cleaning performance or battery life—only documented root feasibility and local-map architecture after Valetudo replaces vendor cloud stacks.

Where I’m less sure — reseller listings rarely disclose NAND vendor or manufacturing month; Roborock Q7 Max rootability stays a lottery until the tray is open¹. Anecdotally, buyers who treat “Dreame L20 Ultra” as one SKU without a serial photo lose a weekend on R2253 hardware that upstream marks not rootable.

Before you pay, re-open upstream install pages—vendors patch exploit chains without press releases.

Original research: rooting-interface matrix (June 2026)

This citable dataset normalizes all 49 upstream-supported robots into three access tiers shoppers confuse in search results: OTA/laptop software exploit, UART test-point + breakout PCB, and full disassembly. Counts were verified by line-by-line audit on 1 June 2026¹.

Access tier	Mechanism	Models (count)	Typical tooling	Mainboard solder?
I — OTA / laptop exploit	Vendor OTA or USB debug path over network/cable	16	Linux laptop; micro-USB on Eureka/Viomi	No
II — UART service port	Exploit via documented test pads + contact PCB	24	3.3 V USB-UART + Dreame adapter PCB	No (contact pads only)
III — Full disassembly	Tray teardown; flash path on internal storage	9	Screwdrivers, patience; NAND lottery on Q7 Max	No (but seals break)
Total supported	—	49	Per-model upstream docs	—

“Please note that this list is exhaustive. These are the supported robots. Robots not on this list are not supported by Valetudo.”
— Valetudo Supported Robots, accessed 1 June 2026

The per-SKU revision table with SSID fingerprints and serial prefixes lives in our full 49-model database. This page explains why those columns exist.

Decision flow: pick your access tier first

Use this flow before you compare mop pressure or suction watts—wrong tier means return-window loss on opened Roborock trays.

Step	Question	If yes	If no
1	Is the exact model on Supported Robots today?	Continue	Stop — unsupported
2	Do you refuse any chassis opening?	Prefer Tier I (Eureka USB, Viomi micro-USB, S5 OTA) or Tier II Dreame UART	Tier III Roborock paths remain
3	Are you shopping Roborock Q7 Max factory-new in 2024–2026?	Treat as NAND lottery — see Tier III warnings	Other Roborock rows
4	Is the robot Dreame/MOVA/Xiaomi-Dreame on the list?	Plan Tier II: 3.3 V UART + breakout PCB	Check USB/laptop rows
5	Will you run Home Assistant MQTT?	Budget broker auth + IoT VLAN	Web UI-only is possible but weaker automation

Soldering vs UART breakout: what shoppers actually mean

Search queries mix “Valetudo solder test points” with “no solder rooting.” Upstream Dreame documentation is consistent: the Hypfer Dreame breakout PCB mates with factory UART pads on a service connector—mechanical contact, not dragging an iron across the vacuum motherboard¹².

Question	Accurate answer (June 2026 upstream)
Do I solder wires to the main PCB?	Not for Tier II—use the breakout PCB + 3.3 V adapter¹.
Is any “soldering” involved?	You may solder headers on the adapter PCB you hold in your hand—not on the robot.
What disassembly is required?	Minimal shell access to reach the service port; seals often stay intact¹.
What if UART shows garbage?	Try 500000 baud instead of 115200 on several Dreame SKUs¹.

Tier III (Roborock S6 onward) is different: you are not soldering test points for daily rooting—you are opening the chassis to reach storage and documented flash interfaces. That breaks warranty seals even when no iron touches the board.

Dreame & MOVA: UART exploit chain + secure boot

Most 2026 privacy shoppers targeting flagships land in Tier II. The software path is an embedded Linux exploit delivered over UART after you break out of the vendor shell—upstream labels this “pretty easy” for dozens of SKUs, with growing secure boot gates on aarch64 lines¹.

Secure-boot firmware gates (selected)

Model cluster	Valetudo binary	Secure boot	Minimum vendor FW (upstream)
Dreame L10 Pro	aarch64	yes	since FW 1138
Dreame Z10 Pro	aarch64	yes	since FW 1156
Xiaomi Vacuum-Mop 2 Ultra	aarch64	yes	since FW 1167
Dreame D9 / F9 / W10	armv7 / lowmem	no	—
MOVA Z500	armv7	no	—

Flash current vendor firmware before root when upstream lists a floor build—skipping updates can leave exploit chains stale while still looking like the “right” robot name.

Dreame/MOVA Tier II roster (UART breakout)

Model	Revision trap	Post-root note
Dreame D9	3 buttons — not D9 Max	500000 baud fallback¹
Dreame L10s Ultra	Not L10s Ultra Gen2	AI camera + no extendable mop¹
Dreame L20 Ultra	Serial R2394 only; R2253 NOT rootable	Wi-Fi one-liner documented¹
Dreame L40 / X40 family	Exact name match—no L40s Pro rebadges	Negative deviceId fix on late-2025 builds¹
MOVA P10 Pro Ultra	Not P10 Ultra	Secure boot yes¹
Xiaomi 1C	SSID → `dreame.vacuum.mc1808` only	Wrong revision unsupported¹

Documented Wi-Fi persistence fix (software, not hardware)

Several 2025–2026 Dreame roots need a shell one-liner after flash—not PCB mods:

rm -f /data/config/miio/wifi.conf /data/config/wifi/wpa_supplicant.conf /var/run/wpa_supplicant.conf
dreame_release.na -c 9 -i ap_info -m " "
reboot

Reconfigure Wi-Fi from the Valetudo web UI after reboot¹.

W10 dock timing (still Tier II)

When the mop dock blocks the UART cable during install:

sleep 300 && ./install.sh

You get 300 seconds to detach the breakout PCB and dock the robot while the script continues¹.

Roborock: OTA exploits vs disassembly-era hardware

Roborock splits cleanly across tiers—this is the core of the compatibility matrix GSC users ask for when they query valetudo supported robots 2026.

Tier I — OTA / laptop software exploit (seals intact)

Model	Exploit style	Firmware gate	Notes
Roborock S5	Laptop OTA	FW ≥ 2008 for segment maps	Legacy but still supported¹
Xiaomi V1 (Roborock-made)	OTA if mfg before 2020-03	—	After cutoff → Tier III disassembly¹

Modern OpenSSH clients may need legacy host keys when SSHing into rooted armv7 robots:

ssh -o HostKeyAlgorithms=+ssh-rsa root@<robot-lan-ip>

Tier III — full disassembly (supported, high friction)

Model	NAND / hardware trap	Maintainer confidence
Roborock S6	Vinda before 2020-06 vs init override after	Maintainer does not own unit¹
Roborock S7 / S7+	VibraRise mop complicates first open	Disassembly warning¹
Roborock Q7 Max / Q7 Max+	SkyHigh NAND ~Q2 2024+ may block root	Safe but may fail after open¹
S4, S4 Max, S5 Max, S6 Pure, S7 Pro Ultra	—	Subpar/unknown issues per upstream¹

Upstream’s September 2024 Q7 Max update is explicit: factory-new units may ship NAND that does not root; you only discover SkyHigh after disassembly—often past return windows¹.

Stat snapshot: Of 9 Tier III Roborock-family rows in our June 2026 audit, only S5 stays in Tier I OTA—everything else in that vendor cluster expects tray screws¹.

Side-by-side: Dreame UART vs Roborock access paths

Dimension	Dreame / MOVA / Xiaomi-Dreame (Tier II)	Roborock modern (Tier III)
Primary interface	UART service pads + breakout PCB	Full chassis disassembly
Software exploit	Embedded shell → install script	Vinda / init override paths
Warranty seals	Often intact	Broken
Secure boot	Common on 2024–2026 flagships	Less emphasized; NAND type matters
Privacy shopper fit	Feature-rich 2026 maps without tray surgery	Only if you accept mechanical risk
Typical failure mode	Wrong SKU / SSID revision	Q7 Max NAND mismatch after open

For USB-only shoppers (Eureka, Viomi, legacy paths), see our no-solder tier guide—it maps Tier I + II without repeating Roborock disassembly steps.

Tier I beyond Roborock: Eureka and Viomi (USB exploit paths)

Not every valetudo supported robots 2026 query is Dreame vs Roborock—16 upstream models root through Linux laptop + USB/micro-USB without UART pads. Privacy shoppers who want zero tray screws should shortlist here before considering Tier III Roborock.

Cluster	Models (upstream count)	Access	June 2026 caveats
Eureka (Midea)	6 J/E20 SKUs	micro-USB + laptop	E20 Wi-Fi driver/mDNS quirks—use static IP¹
Viomi + CRL-200S rebrands	V6, SE + Conga/Proscenic paths	micro-USB + laptop	Never root `viomi.vacuum.v8` SSIDs¹
Xiaomi Vacuum-Mop P	STYJ02YM family	micro-USB + laptop	May reflash to Viomi V6 firmware for features¹
Roborock S5 + old V1	S5; V1 before 2020-03	laptop OTA	V1 after cutoff → Tier III¹

Eureka aarch64 boots can take minutes after power-on—do not power-cycle during first Valetudo start. Viomi paths may require battery removal without breaking warranty seals, per upstream notes¹.

High-severity verification traps (hardware matrix)

Trap	How to detect before purchase	If ignored
L20 Ultra twins	Serial R2394 vs R2253	R2253 not rootable¹
Q7 Max NAND era	Prefer used / slow-inventory stock; open only if willing to gamble	Root fails after disassembly¹
Xiaomi 1C revisions	Wi-Fi AP SSID → `dreame.vacuum.mc1808`	Unsupported hardware¹
Vacuum-Mop P vs Viomi V8	Never root `viomi.vacuum.v8` SSIDs	Brick risk upstream warns¹
Dreame “Pro” / “s” suffixes	Button count + exact marketing suffix	Wrong robot family¹
Negative miio deviceId	`/mnt/private/ULI/factory/did.txt` negative on late-2025 Dreame	Valetudo auto-detect fails—documented positive-ID edit¹

Named buyer scenarios

Nadia, Brooklyn, rents a 2-bed with “no visible mods” clause. She wants Dreame L10s Ultra maps in Home Assistant without cloud. Verdict: Tier II UART breakout—budget ~$35 for a 3.3 V adapter and official PCB, confirm not Gen2, flash on 1 June 2026 upstream docs, then MQTT hardening. Skip Roborock S7—Tier III violates her lease-friendly constraint.

Oliver, Helsinki, found “Q7 Max+” 40% off at a big-box retailer (manufactured August 2024). He assumes OTA-style rooting like forum posts from 2022. Verdict: Treat as Tier III lottery—upstream warns SkyHigh NAND may block root after teardown¹. Oliver should buy used pre-Q2 2024 stock with serial photos or pivot to Eureka J15 Ultra (Tier I USB) unless he accepts a paperweight risk.

Priya, Home Assistant 2026.4, already runs VLAN 40 for IoT. She will root Roborock S5 bought used for €120. Must run stock FW 2008+ before expecting room segments¹. After MQTT is stable, she blocks WAN on VLAN 40 per egress filtering and deletes Mi Home—see the install playbook.

Steel-man: “UART is still too hard—just use Roborock local API”

Best case for stock firmware: Roborock’s local network mode on recent S7/S8/Q lines delivers map viewing and control without Valetudo surgery. Setup is consumer-grade, warranty stays valid, and you avoid UART adapters entirely. For households that only need “maps not uploaded by default” with a single Saturday of work, this is rational—especially when rooting Q7 Max hardware is a NAND gamble in 2026¹.

Rebuttal: Local mode still trusts vendor-signed binaries that can change behavior via OTA, and you cannot audit telemetry the way you can on Apache-licensed Valetudo³⁴. If your threat model includes subpoenas to cloud vendors or silent policy changes, Tier II Dreame or Tier I Eureka paths remain stronger—provided you buy SKUs that are still rootable on the June 2026 upstream list¹.

After root: maps, MQTT, and LAN hardening

Flash Valetudo from official releases—never interrupt power mid-write⁴.
Join trusted SSID; assign a DHCP reservation for stable MQTT.
Home Assistant: MQTT discovery per install guide.
IoT VLAN: deny WAN; allow broker + NTP only (segmentation primer).
Export settings after first good boot—recovery beats re-rooting.

Maps render in the Valetudo UI and HA cards; they do not require vendor cloud sync once MQTT is healthy. Pair with the cloud-free vacuum roundup for brand-level privacy context.

Privacy Smart Home 2026 Valetudo rooting and compatibility matrix infographic: OTA laptop exploit paths for legacy Roborock, Dreame UART breakout PCB on service test points without motherboard soldering, full disassembly tier for S6–Q7 Max, and MQTT plus IoT VLAN for cloud-free LiDAR maps. — Match access tier before brand marketing—OTA, UART breakout, and disassembly are not interchangeable workflows.

Checklist

Confirm the model appears verbatim on valetudo.cloud Supported Robots (1 June 2026 snapshot).
Classify your SKU: Tier I OTA/USB, Tier II UART breakout, or Tier III disassembly.
For Dreame: order 3.3 V USB-UART + official Dreame breakout PCB before opening the box.
For Roborock Q7 Max: treat 2024+ factory stock as NAND lottery—serial and mfg date matter.
Download the correct armv7 / armv7-lowmem / aarch64 Valetudo artifact for your row.
Read secure-boot and minimum firmware notes before first flash.
Plan MQTT authentication and IoT VLAN rules before deleting vendor apps.

Verdict

For privacy-first buyers in 2026, the right robot is the one whose rooting interface you will actually execute—not the best YouTube mop demo. Dreame/MOVA Tier II (UART breakout, no mainboard soldering) is the default for feature-rich LiDAR without Roborock tray surgery. Tier I OTA/USB (S5, Eureka, Viomi) minimizes mechanical risk. Tier III Roborock is for owners who treat disassembly as a hobby and accept Q7 Max NAND failure modes.

Use this page to pick how you root; use the 49-model SKU matrix to pick which model. When hardware is in hand, continue to Install Valetudo + Home Assistant and the firmware privacy primer.

Primary sources

ID	Source	URL
1	Supported Robots (canonical list + per-model rooting)	valetudo.cloud/pages/general/supported-robots/
2	Why Valetudo?	valetudo.cloud/pages/general/why-valetudo/
3	Valetudo releases	github.com/Hypfer/Valetudo/releases
4	Dreame UART breakout PCB	github.com/Hypfer/valetudo-dreameadapter
5	Dreame installation — UART shell	valetudo.cloud/pages/installation/dreame/#uart-shell
6	Dennis Giese — vacuum hardware overview	robotinfo.dev
7	Buying supported robots	valetudo.cloud/pages/general/buying-supported-robots/

Frequently Asked Questions

Which robots support Valetudo in 2026?

Only the exhaustive list at valetudo.cloud/pages/general/supported-robots/—49 documented models as of June 2026. Robots not on that page are unsupported regardless of forum anecdotes.

Do I need to solder to the motherboard for Dreame Valetudo roots?

Upstream documents the Hypfer Dreame breakout PCB as contact pads on the robot’s UART service port—not permanent solder joints on the mainboard. You still need a 3.3 V USB-UART adapter and minimal shell access.

Which Roborock models use OTA laptop rooting without disassembly?

Roborock S5 and Xiaomi V1 units manufactured before 2020-03 use laptop-first paths with warranty seals intact. Roborock S6 onward requires full disassembly; Q7 Max units with SkyHigh NAND from ~Q2 2024 may fail even after teardown.

What is secure boot in the Dreame compatibility matrix?

Newer Dreame aarch64 builds enforce verified boot chains; upstream lists minimum vendor firmware builds (e.g., L10 Pro since FW 1138, Vacuum-Mop 2 Ultra since FW 1167) before the documented root exploit succeeds.

Can I keep the vendor app after installing Valetudo?

No—Valetudo replaces the vendor Linux stack. Daily control moves to the local web UI and MQTT; stock cloud apps stop working on the same firmware.

Where is the full per-model SKU table?

See our companion guide valetudo-supported-robot-vacuums-list-2026 for all 49 rows with revision fingerprints, or the upstream Supported Robots page for install deep-links.

Dataset (JSON-LD)

Valetudo Supported Robots, accessed 1 June 2026. https://valetudo.cloud/pages/general/supported-robots/ ↩ ↩² ↩³ ↩⁴ ↩⁵ ↩⁶ ↩⁷ ↩⁸ ↩⁹ ↩¹⁰ ↩¹¹ ↩¹² ↩¹³ ↩¹⁴ ↩¹⁵ ↩¹⁶ ↩¹⁷ ↩¹⁸ ↩¹⁹ ↩²⁰ ↩²¹ ↩²² ↩²³ ↩²⁴ ↩²⁵ ↩²⁶ ↩²⁷ ↩²⁸ ↩²⁹ ↩³⁰ ↩³¹ ↩³² ↩³³ ↩³⁴ ↩³⁵ ↩³⁶ ↩³⁷ ↩³⁸ ↩³⁹
Hypfer valetudo-dreameadapter (UART breakout PCB). https://github.com/Hypfer/valetudo-dreameadapter ↩
Valetudo — Why Valetudo. https://valetudo.cloud/pages/general/why-valetudo/ ↩
Hypfer/Valetudo releases. https://github.com/Hypfer/Valetudo/releases ↩ ↩²

Quick answer: What are Valetudo supported robots in 2026?

Methodology: how this matrix was built

Original research: rooting-interface matrix (June 2026)

Decision flow: pick your access tier first

Soldering vs UART breakout: what shoppers actually mean

Dreame & MOVA: UART exploit chain + secure boot

Secure-boot firmware gates (selected)

Dreame/MOVA Tier II roster (UART breakout)

Documented Wi-Fi persistence fix (software, not hardware)

W10 dock timing (still Tier II)

Roborock: OTA exploits vs disassembly-era hardware

Tier I — OTA / laptop software exploit (seals intact)

Tier III — full disassembly (supported, high friction)

Side-by-side: Dreame UART vs Roborock access paths

Tier I beyond Roborock: Eureka and Viomi (USB exploit paths)

High-severity verification traps (hardware matrix)

Named buyer scenarios

Steel-man: “UART is still too hard—just use Roborock local API”

After root: maps, MQTT, and LAN hardening

Checklist

Verdict

Primary sources

Frequently Asked Questions

Dataset (JSON-LD)

Footnotes

Related guides