Our take
Newless than six months old and changing fast- Activity
- 52
- Community
- 57
- Issues
- 53
- Pull requests
- 40
+1,061 stars in the last 30 days
OOMWOO is a promising, actively changing design effort for technically capable contributors, but it is not yet a ready-to-build vacuum.
Good fit if
- You want to contribute to a Raspberry Pi and ROS2 robot project and can start with simulation.
- You value locally operated, hackable home robotics and are comfortable sourcing parts and helping validate the design.
- You want to work on a focused module; the project has multiple contributors and recent merged work, without measured contributor concentration.
Look elsewhere if
- You need a working DIY vacuum with validated build instructions today.
- You need a released, stable product or a project with published releases to track; this new project has no releases in the past year.
- You want a finished hardware design: printable files, boards, firmware and complete bring-up instructions are still pending.
All health signals
| Last commit | 2026-11-16 (today) |
|---|---|
| Commits, last 90 days | 100+ |
| Releases, last 12 months | 0 |
| Contributors | 17 (top contributor: 49% of commits) |
| Issues closed, last 90 days | 2 |
| Pull requests merged, last 90 days | 11 (typically merged in 2 days) |
| Project age | 5 months |
Checked on 2026-11-17 with the GitHub API.
Project history
Daily GitHub snapshots since Oct 7, 2026. History covers stars and forks; health signals are not tracked historically.
Stars
13,120Forks
825Change since Nov 16, 2026: +13 stars·0 forks
Overview
OOMWOO is an open-source robot vacuum you build yourself, built around Raspberry Pi and ROS2, with affordable 2D LiDAR for mapping and autonomous navigation. It aims to solve the cloud dependence and limited hackability of commercial vacuums while offering local operation and Home Assistant integration.
The project is for people who want to build and modify a home-cleaning robot, rather than buy a finished appliance. Its hardware design is still in progress, but the ROS2 robot description and Gazebo simulation let contributors work on software before the physical vacuum is ready.
Key Features
- ROS2-based robot software and Gazebo simulation, with related packages linked from the repository.
- 2D LiDAR mapping and autonomous navigation, with Nav2 named as a target.
- Raspberry Pi as the planned onboard computer.
- Planned local control and native Home Assistant integration, with no cloud required for regular functionality.
- A planned 3D-printable, documented chassis and parts sourced independently.
- Community contribution process organized around separate software, firmware, electronics, mechanical and procurement modules.
Use Cases
- Robotics developers can prototype navigation or cleaning software against the Gazebo simulation before the custom hardware is ready.
- DIY builders can follow the project as a basis for a repairable, modifiable vacuum, once the bill of materials and build instructions are validated.
- Home Assistant users interested in local appliance control can assess the project as a future alternative to cloud-dependent vacuums.
- Contributors can develop a discrete module, such as a ROS2 feature, firmware component or mechanical specification, without waiting for the whole robot to be complete.
What you need
Detected in the repository
- Python (main language on GitHub)
- Automated checks on GitHub Actions
License in plain words
Apache-2.0permissive
- Commercial use: yes
- Modify and redistribute: yes
- You must keep: the license, the NOTICE file and a note of your changes
- Share your changes: no
- Includes an explicit patent grant from the contributors:
A summary, not legal advice: the LICENSE file is what applies.
Getting Started
There is no complete hardware build process yet. To explore the current software path, start with the OOMWOO One ROS2 robot description and Gazebo simulation and the installation project. See the README and build instructions for project status and updates.
Considerations
The README explicitly says the vacuum is not buildable yet: the bill of materials is rough, and key hardware deliverables such as printable files, PCBs, firmware and validated build instructions remain incomplete. The project is changing quickly and has no recent release history, so interfaces and plans may evolve. The code is under Apache-2.0, while the hardware license is still to be determined. No runtime or deployment prerequisites are specified in the supplied project facts; expect to consult the linked ROS2 installation materials before attempting simulation.
Found this useful?
Share it with someone who would like oomwoo.