The problem
Consumer robot vacuums are good at two things you did not ask for: phoning home and changing the rules after you buy.
Room maps, cleaning schedules, and even basic controls increasingly run through vendor apps and cloud backends. When a company shifts to subscriptions, deprecates hardware, or gets acquired, your vacuum can feel less like an appliance and more like rented firmware. If you care about privacy, offline operation, or simply owning what you paid for, the default product category works against you.
What OOMWOO is
OOMWOO is an open-source robot vacuum you build yourself—hardware, firmware, and software. The project surfaced widely after Hackaday’s coverage in July 2026, and the GitHub repo had already crossed 5,000 stars by then.
The pitch is local-first by design: no cloud required for regular functionality, no vendor lock-in, and a stack makers already run at home. Core pieces include:
- Raspberry Pi for compute (v0 targets Pi 5 and/or ESP32 with micro-ROS—still being decided)
- ROS 2 / Nav2 for mapping, localization, and autonomous navigation
- 2D LiDAR for room mapping at lower cost than many consumer units
- Home Assistant integration for local control
- 3D-printed chassis and documented build steps
- ESP32 / Arduino on the I/O and motor-driver path
License is Apache 2.0 for code; hardware files will ship under an open hardware license once published.
The name is a rotational ambigram—it reads the same upside down, which is a neat fit for something that roams in every direction.
How it differs from “just root your Roomba”
You do not need OOMWOO to escape the cloud. Projects like Valetudo replace cloud-dependent firmware on supported commercial vacuums and keep control local. That is often the faster path if you already own compatible hardware.
OOMWOO is a different bet: ground-up open hardware where the BOM, PCB, URDF, and ROS packages are meant to be forked, audited, and improved. The tradeoff is obvious—you are signing up for a build project, not unboxing a finished product.
The team is also developing against a placeholder robot (a Proscenic M6 Pro bridged to ROS 2) while the final mechanical design lands, so software progress can move before every printed part is finalized.
What’s done—and what’s still in progress
Be honest about the timeline: OOMWOO is not a shrink-wrapped vacuum yet.
According to the project README, software and simulation work is well underway—Gazebo sim, navigation modules, compute/memory tuning, and community contribution tracks for docking, recovery behaviors, and cleaning jobs. The bill of materials is still in progress, 3D models for off-the-shelf parts are being sourced, and the full mechanical design is evolving in public.
That is not a knock. It is the normal shape of a serious open hardware effort. But if you need something cleaning your floor this weekend, this is a watch list project, not a buy list project.
Why the timing hits
Hackaday’s write-up lands in a moment when trust in closed vacuum ecosystems is shaky. Readers are looking for appliances that stay useful without a account login, and for stacks that integrate with Home Assistant instead of yet another siloed app.
OOMWOO fits that mood—even incomplete—because it treats offline operation as a default requirement, not a premium feature:
Local, no cloud required for regular functionality.
Optional cloud extras are explicitly optional. The project also points to an optional parts kit at makerspet.com for people who would rather not hunt motors and LiDAR alone. The kit is convenience, not a gate: everything remains open whether you source parts yourself or not.
Who should pay attention
- Home Assistant users who want a vacuum that behaves like the rest of a local smart home
- ROS 2 tinkerers looking for a practical, room-scale platform—not just a tutorial turtlebot
- Privacy-minded buyers tired of cloud maps and account-gated basic features
- Contributors—the repo is modular; sim, navigation, PCB firmware, and UX tracks are open for parallel work
Who should skip—for now
- Anyone who wants plug-and-play cleaning today
- Renters or households that cannot tolerate a multi-week build and debug cycle
- People without a 3D printer and comfort sourcing electronics (unless you wait for a more complete kit/BOM)
- Shoppers comparing finished $300–$500 consumer bots on suction and mop features alone
If you only need to de-cloud an existing vacuum, check Valetudo compatibility lists first. That is the practical fix for most households.
What to watch next
Three milestones will tell you whether OOMWOO moves from exciting repo to real alternative:
- Published BOM and printed files you can build without guesswork
- End-to-end demo: map a room, run a coverage clean, return to dock—on hardware, not just Gazebo
- Honest power and maintenance numbers (the Pi-at-core question matters if the dock does not cut idle draw)
Follow the GitHub repo, skim the contribution modules if you want to help, and treat Hackaday’s piece as the overview—not a shipping announcement.
Bottom line
OOMWOO will not replace a store-bought vacuum tomorrow. It does show where frustrated buyers are heading: local maps, open firmware, and hardware you can repair.
If that matches how you already run your home lab, bookmark the project. If you just want quiet floors by Sunday, root a supported vac or buy one with documented offline mode—and keep an eye on OOMWOO for the next time your vendor moves the goalposts.
