Valetudo – Cloud replacement for vacuum robots enabling local-only operation

Original Article ↗ Hacker News Discussion ↗

Valetudo, an open-source firmware that replaces cloud-dependent software on many robot vacuums, is praised for enabling fully local operation, better privacy, and tight integration with tools like Home Assistant. Commenters share real-world experiences with supported models, rooting methods, and hardware quirks, while noting that installation can be complex and is largely limited to certain Dreame/Roborock-style devices rather than Roombas or Neatos. The project’s opinionated governance, Apache 2.0 licensing choice, and ecosystem of alternative “local-first” robots like Matic also raise broader questions about open-source expectations, vendor lock-in, and the future of home robotics.

Project purpose & naming

  • Valetudo replaces cloud-connected firmware on certain robot vacuums so they can operate fully locally, with Home Assistant (HA) integration.
  • Name discussion: one meaning is from Latin (“health”), another user-associated meaning is a Portuguese phrase like “anything goes”; the project FAQ ties it to the Roman name of a cleanliness goddess.

User experiences with Valetudo

  • Several users report multi‑year stable use on Dreame and Roborock models and say they will only buy robots that support Valetudo or similar in future.
  • Common benefits cited: no vendor cloud, no floor-plan upload, fewer nags/upsells, and powerful HA‑based automation (dynamic scheduling, room priority, integration with presence).

Rooting and hardware challenges

  • Rooting often requires opening the robot and using serial or USB debug headers; for some Dreame models, breakout PCBs help with non‑standard pin spacing.
  • Experiences vary from “just poked wires in” to frustration at sourcing PCBs or fear of bricking expensive hardware.
  • Community Telegram groups help share PCBs and advice, but the process is still seen as too complex for non‑technical or remote users.

Supported robots & vendor ecosystems

  • Supported models are explicitly listed on the project site; only those are “supported,” though the firmware may run on more.
  • Roomba hardware is currently unsupported; some confusion appeared over claims of per‑square‑meter charging, with multiple replies stating this is incorrect or a misunderstanding of model tiers and battery/bin limits.
  • Roombas can be used locally after initial app setup, but behavior without Wi‑Fi (e.g., schedule retention) is reported inconsistently.
  • Neato’s shutdown leaves owners stranded; Valetudo currently doesn’t support those models. Ecovacs rooting methods were recently presented; Valetudo support is “coming” but not ready.

Privacy, cloud dependence, and alternatives

  • Strong interest in avoiding cloud‑tied devices due to vendor shutdown risk and home‑mapping privacy concerns.
  • Some people simply never connect their robots to Wi‑Fi and rely on hardware buttons instead.
  • A competing product (Matic) is discussed: fully on‑device vision, local‑only operation, HEPA bags, optional membership, and no dock. Others question its price, lack of dock convenience, subscription optics, and limited regional/OS support.

Project governance, licensing, and community

  • The “Valetudo is a garden” metaphor and the “only supported robots are supported” stance are praised as clear boundaries against entitlement.
  • Some see the Apache‑2.0 license as risky because OEMs could ship locked‑down devices using Valetudo; GPLv3 is suggested as a better fit to avoid tivoization.
  • One commenter describes the maintainer and Telegram community as hostile and rude; others highlight active help and a strong support culture. Community tone is thus portrayed as mixed.