GitHub - makerspet/oomwoo: Open-source vacuum robot cleaner · GitHub
Skip to content

makerspet/oomwoo

Folders and files

Repository files navigation

OOMWOO

Open-source robot vacuum you build yourself.

Clean well · Raspberry Pi · ROS2 · Home Assistant · 2D LiDAR · 3D printed · ESP32 · Arduino

License Status

What is this?

OOMWOO is an open-source home robot vacuum you can build yourself, made for the Raspberry Pi, ROS2, Home Assistant, and 3D-printing communities. It uses an affordable 2D LiDAR to map your home and navigate on its own. Local, no cloud required for regular functionality, no vendor lock-in. Follow the community newsletter.

Reference design images - this is approximately how the finished design will look:

Reference robot vacuum cleaner top Reference robot vacuum cleaner bottom Reference robot vacuum cleaner - top cover removed

Goals

  • Affordable, fully open hardware, software and firmware
  • Home appliance product quality - not a throwaway build
  • Easy to build, with step-by-step zero-to-hero instructions
  • 2D LiDAR mapping and autonomous navigation (ROS2 / Nav2)
  • Native Home Assistant integration for local control
  • 3D-printable, documented, and hackable chassis
  • Buildable from parts you source yourself
  • Local, no cloud required for regular functionality
  • Optional extra functionality when connected cloud
  • Apps on top of ROS2 to customize vacuum operation
  • Stretch goal: App store
  • Stretch goal: LeRobot integration, OpenClaw

v0 target: bare-bones build:

  • 3D-printed chassis
  • ROS2 Gazebo sim
  • LiDAR with manual SLAM
  • ROS2 on Raspberry Pi 5 AND/OR ESP32 running micro-ROS with ROS2 on local PC - decision TBD

Open Source Deliverables:

Contributing

Would you like to contribute? See CONTRIBUTING for the full guide.

OOMWOO is organized to built by the community, massively in parallel. The vacuum and its software are subdivided into modules, see list below.

A volunteer picks whatever module she wants, works on that module whenever she wants, submits her contribution as a PR under contributions/module-name/.

Multiple developers are welcome to work on the same module. The best solution for each module surfaces for over time, with the project master having the last call.

  1. Pick a contribution from the list below.
  2. Let us know you're working on it and your progress.
  3. Check ARCHITECTURE.md for the system design and interfaces.

Follow us building in public:

Requests for Contributions

Every module below is actionable now — build it against the Gazebo simulation (oomwoo-one) or a real placeholder robot (a Proscenic M6 Pro connected to ROS2), until OOMWOO hardware is ready. Pick one, tell us in Discussions, and open a PR.

Module ID Status Notes
ROS2 URDF + Gazebo sim urdf-gazebo-sim In progress Placeholder URDF + Gazebo sim (reference: oomwoo-one; @alvarosamudio merged), refined when hardware lands
First clean: coverage + mapping + exploration clean-and-map Ready to start work Coverage cleaning while SLAM-mapping and exploring
Localization & navigation on a known map nav-localize Ready to start work Nav2 nav, AMCL localization, relocalize when lost, resume map
Dock cycle: undock, dock, recharge dock-cycle Ready to start work Undock, return-to-dock, precise docking, station services, find dock when lost
Recovery behaviors & safety recovery-safety Ready to start work Recovery ladder, escalation, pause-and-alert, safety sensors, status reporting
Floor-surface handling & edge cleaning floor-care Ready to start work Wall/edge following, carpet vs hardwood, mop lift/lower
Cleaning modes, zones & job orchestration cleaning-jobs Ready to start work Modes (regular/spot), virtual walls, room segmentation, job splitting + resume
Live robot bring-up & validation live-robot-bringup Ready to start work Connect the placeholder Proscenic M6 Pro to ROS2, re-run sim tests on hardware
Source 3D models (STEP) for BOM parts source-3d-models In progress Obtain / measure / model STEP files of off-the-shelf parts (wheels, fans, caster…) so mounts fit
Procure part specs & datasheets part-specs In progress Find/measure/reverse-engineer specs (pinouts, encoder PPR, torque, how to drive fans…) for sourced parts
I/O + motor-driver PCB io-pcb Ready to start work Trim the RK3562 reference schematic to the STM32 I/O side (motors, sensors, battery charging), move the battery to 4S, convert to KiCad; hold at schematic for review

Planned and on-hold modules (mechanical design, later-phase software) live in the RFC backlog.

Source code reference

Related prior art

Design research

We reviewed the 2025–2026 consumer robot vacuum landscape (global + China-sourceable brands, all price tiers) to decide which solutions to copy and which to skip. Key takeaways for the build:

  • Suction is a sourcing problem, not an engineering one. Real-world cleaning does not track advertised suction (Pa); ~$500 mid-tier models beat flagships. A moderate sealed sourced motor + a good brush + tight airflow sealing matches flagships — no custom impeller needed.
  • "Never gets stuck" needs camera + AI sensor fusion, not LiDAR alone — LiDAR is blind below its ~10 cm turret (cables, socks). v1 leans on the bumper for low obstacles; vision-based avoidance is a later / experimental goal, not an MVP promise.
  • Anti-tangle brush: a tapered rubber roller resists hair-wrap best (a top user complaint) and is easy to 3D-print.
  • Mop: a 3D-printed dual-spinning mop is competitive; the self-washing roller mop's edge is overstated and hard to replicate — skip it for now.

Well-loved models worth studying: Eufy Omni S2 (obstacle avoidance), Narwal Flow (roller mop), Ecovacs Deebot T90 Pro Omni (~$499 all-rounder), Dreame X40 Ultra (dual-spinning mop). Dreame is also the most Valetudo-rootable brand — the safest donor to study. (Per-model rankings are directional, from single-run reviewer tests.)

About

The project name "OOMWOO" is a rotational ambigram - it reads the same flipped 180°, like the robot itself, roaming your floor in every direction.

The project is sponsored by makerspet.com and remake.ai. We are reusing their open-source solutions.

  • If you'd rather skip the parts hunt, a kit (motors, PCB, brushes, gaskets, LiDAR) will be available at makerspet.com, from the same maker behind this project. The kit is a convenience, never a requirement. Everything here stays open.
  • When we get to apps, remake.ai will be providing its robot apps platform and app store. Using the app store will be entirely optional. The vacuum will always support cloud-free, local operation for regular functionality out-of-the-box.

License

Code is released under the Apache License 2.0.

Hardware design files, once added, to be released under an open hardware license (TBD).

Star History

Star History Chart