An X post on August 5, 2026 from @oliviscusAI called OOMWOO "a genuinely interesting weekend project" for anyone with a Raspberry Pi and a 3D printer sitting around. It racked up replies fast — and most of the loudest ones were corrections, not praise. "If you look at the GitHub, it's not ready yet," wrote @2armsgn3. "There are no 3d printable files yet," added @p_romeo24. One reply put it more bluntly: "if this is a weekend project, I'm the most incapable HW-thinkerer on the planet."
They're right. OOMWOO, maintained by makerspet with remake.ai, is a real and reasonably well-documented open-source robot vacuum effort — a Raspberry Pi Compute Module running ROS2, 2D LiDAR mapping, and native Home Assistant integration with no cloud dependency by design. It is also, by the project's own published checklist, not a project you can build today. This post separates what the viral tweet implied from what OOMWOO's GitHub actually confirms is shipped.
TL;DR
| Question | Answer |
|---|---|
| Can I build OOMWOO this weekend? | No. Core hardware deliverables (3D files, Pi software, PCB, firmware, instructions) are unreleased. |
| Is there a real GitHub repo? | Yes — github.com/makerspet/oomwoo, plus companion repos for the ROS2 description package, I/O board, and Docker install. |
| What hardware does it target? | Raspberry Pi Compute Module (CM4/CM5), 2D LiDAR, STM32G070-based I/O board, encoder motors, ToF sensors. |
| What software stack? | ROS2 Jazzy, Nav2, SLAM, Gazebo simulation, Home Assistant integration. |
| Does it need the cloud? | No, by design — local operation is a core project goal, once hardware ships. |
| What's the closest finished comparison? | OpenMower, a mature DIY open-source robot lawn mower with real build guides and a large community. |
| When are build instructions expected? | The project has cited fall 2026 as a target. |
| Who's building it? | makerspet.com and remake.ai, developed in public with community contributions. |
What problem is OOMWOO trying to solve?
The tweet's framing — that "real-world cleaning doesn't track advertised suction power" and that hair-wrap on brush rollers is one of the most common complaints with commercial robot vacuums — is a fair summary of the project's stated motivation. Commercial robot vacuums are closed systems: proprietary firmware, cloud-tied apps, subscription features, and hardware you can't repair or modify. OOMWOO's pitch is a vacuum that is fully open at every layer — hardware schematics, PCB firmware, navigation stack, and app integration — so owners can inspect, fix, and extend it themselves, the same philosophy behind Frigate NVR for security cameras or RuView for WiFi sensing.
The anti-tangle brush design the tweet highlighted — a tapered rubber roller intended to resist hair-wrap — is a genuinely reasonable piece of mechanical design thinking, and the project does document it as something intended to be 3D-printable. That's the key word: intended. It sits in the same "not yet released" bucket as the rest of OOMWOO's physical build files.
Can I actually build this today?
No. This is the single most important fact the viral tweet glossed over, and it's worth stating in the project's own words. OOMWOO publishes an "Open Source Deliverables" checklist on its GitHub, and as of the tweet's publication date, the status looks like this:
What's actually done
| Deliverable | Status |
|---|---|
| Software development environment | Done |
| Robot description package + tutorials (ROS2) | Done |
| Placeholder vacuum cleaner + tutorials | Done — explicitly labeled "temporary while OOMWOO is being designed" |
| Bill of materials (BoM) | "Rough version available" |
What's not done yet
| Deliverable | Status |
|---|---|
| 3D-printable files | Not released |
| Raspberry Pi software | Not released |
| Motor drivers, sensors I/O PCB | Not released |
| I/O PCB firmware | Not released |
| Build, setup, bringup and troubleshooting instructions | Not released |
| Demo video(s) | Not released |
That "placeholder vacuum cleaner" line matters more than it looks. Right now, contributors testing OOMWOO's ROS2 navigation code aren't running it on OOMWOO hardware at all — they're running it against a Gazebo simulation or a modified commercial robot, a Proscenic M6 Pro, wired up as a stand-in until the real chassis, PCB, and firmware exist. That's a perfectly sensible way to develop a robotics stack in parallel with hardware design. It is not the same thing as a project you can 3D-print and assemble this weekend.
Community reaction outside the original tweet has echoed the same skepticism. Coverage on Hackaday noted the project is "not quite complete," with software development further along than the physical build, and one commenter on that thread made the sharpest version of the point: "If it hasn't been printed and assembled at least one time, the model files mean nothing." Since no 3D-printable files exist yet, that bar hasn't been reached.
What's actually released vs. planned?
Breaking the tweet's claims against the checklist:
- "Runs on a Raspberry Pi with 2D LiDAR mapping, ROS2 navigation" — true as a design target and demonstrated in simulation/on the placeholder robot, not yet true on real OOMWOO hardware since the Pi software and I/O firmware aren't released.
- "Native Home Assistant integration" — part of the stated architecture; not independently verifiable yet without shipped software.
- "No cloud dependency, no vendor lock-in" — a real and credible design philosophy, consistent with how Frigate and other local-first home automation projects operate, but again a promise about the finished device, not a property you can test today.
- "The anti-tangle brush design... easy to 3D-print yourself" — the 3D-printable files deliverable is explicitly unchecked on the project's own list. You cannot print this today.
- "A genuinely interesting weekend project" — this is the claim that drew the pushback, and the checklist supports the critics, not the tweet.
None of this means OOMWOO is vaporware. The project has a real GitHub organization, multiple active repositories (the main oomwoo repo, oomwoo-one for the ROS2 robot description, oomwoo-io-board for I/O hardware, and oomwoo-install for the Docker setup), a documented software architecture, and a maintainer team (makerspet.com with remake.ai) that has been transparent about what's missing rather than papering over it with marketing language. That transparency is exactly why the checklist is trustworthy — and exactly why the "weekend project" framing doesn't hold up against it.
How is this different from OpenMower?
@MirkoJankovic's reply pointed to OpenMower as the comparison worth making, and it's a good one. OpenMower is a DIY open-source robot lawn mower project maintained by Clemens Elflein that takes a different approach: rather than designing a chassis from scratch, it upgrades cheap off-the-shelf robotic mowers (originally a YardForce Classic 500) with custom RTK-GPS hardware and an open ROS-based control stack.
The practical difference is maturity, not ambition:
| OOMWOO (Aug 2026) | OpenMower | |
|---|---|---|
| 3D-printable / hardware files | Not released | Published and used in real builds |
| Build documentation | Not released | Full guide at openmower.de |
| Community | Early, developed in public | 2000+ member Discord, active builds |
| Hardware approach | Purpose-built chassis (in design) | Retrofit of existing commercial mower |
| Cost estimate | Not yet published | ~€700 in parts excluding mower and RTK base station |
| Can you build one today | No | Yes, with intermediate electronics/Linux/mechanical skills, typically a weekend build |
OpenMower is what a genuinely finished version of the "open-source DIY robot you build in a weekend" concept looks like: real parts lists, real assembled units, a real support community answering real build questions. OOMWOO could get there — the software foundation and design thinking behind the anti-tangle brush and the LiDAR/ROS2/Nav2 stack are credible groundwork — but it is not there yet, and treating it as though it already is misleads anyone who reads the viral tweet and orders a Raspberry Pi expecting a working robot vacuum in two days.
Should you follow OOMWOO now?
If you're interested in open-source home robotics, OOMWOO is worth starring and watching rather than building. You can run the Gazebo simulation, review the ROS2 robot description package, and read the rough bill of materials to get a sense of the architecture. That's a reasonable weekend activity for someone who wants to understand how a Raspberry Pi + 2D LiDAR + Nav2 navigation stack fits together conceptually, in the same way exploring LFM2.5's on-device robotics deployments is useful before you have hardware to run them on. Building an actual OOMWOO vacuum is not currently possible — the maintainers themselves have targeted fall 2026 for build instructions, and the PCB, firmware, and 3D files that would make that possible have not shipped.
For makers who want something they can complete now rather than track, the more productive move is picking a project with a finished deliverables list. OpenMower fits that description directly. So does Open Duck Mini, whose STL files, wiring diagrams, and locomotion code are already public on GitHub. OOMWOO earns a bookmark, a GitHub star, and maybe a watch on its release notes — not a Raspberry Pi order and a weekend cleared on the calendar. The distinction matters because open-source hardware credibility is built on delivered files, not on roadmap intent, and conflating the two is exactly what turned a legitimate early-stage project into a misleading viral claim.
The larger lesson for anyone following open-source hardware on social media: a well-documented GitHub repo with a public roadmap is not the same signal as a shippable bill of materials. Read the checklist before the tweet, not after ordering parts.
Related reading
- Gemma 4 Powers Open Duck Mini: On-Device AI Robot Duck
- Frigate NVR: Open-Source AI Camera System for Home Assistant
- LFM2.5-230M: Liquid AI's On-Device Agent Model
- LFM2.5-2.6B: Liquid AI's Biggest On-Device Agent Model
- RuView: WiFi Sensing on ESP32
- Moonshine Micro: Voice AI on Microcontrollers
Official sources: makerspet/oomwoo on GitHub · OpenMower on GitHub
Project status, GitHub deliverables checklist, and repository details reflect the state of the OOMWOO project as of August 5, 2026. Open-source hardware projects move fast — check the linked repositories directly for the latest checklist status before assuming any deliverable listed here as "not released" is still incomplete.