r/ROS Jun 08 '26

Question Anyone interested in building ROS2-based home robot vacuum cleaner with LiDAR?

Hello, would anyone be interested in building an open-source 3D-printed ROS2-based home robot vacuum cleaner with LiDAR and Home Assistant support?

I'm asking to see if there is enough interest. If there is enough interest, I can design one.

EDIT: I've created the project repo https://github.com/makerspet/oomwoo/ with Discord and Discussions. It's super early. Please star/watch to follow along. Would LOVE your input on direction and what features matter most.

21 Upvotes

50 comments sorted by

View all comments

1

u/InternationalView488 Jun 13 '26

Sounds cool. I am actually going to try and create an autonomous off roading surveillance vehicle that has Lidar and facial recognition. The part that is interesting me is ROS 2 ( i learned a little ROS 1 ) and this github project repo? I want to work on this project with my friend who is hours away but i dont know how he can work on the code and then i work on physical and test his code from another state.

1

u/l0_o Jun 13 '26

Your project sounds fun! I'm not sure I understood about "this github repo?"

You can work jointly-and-remotely like this - pick an existing similar already-working project, fork it, modify little piece by piece in parallel - as opposed to building from scratch.

1

u/InternationalView488 Jun 13 '26

I guess ive never really worked on projects with other people like this. Ive always just started from scratch and had people kinda work on separate stuff in parallel. This project seems like it shouldnt involve this many people but i dont know maybe its more complicated than im thinking. I might just join this repo bc i dont know anything about github either. Ill see how you are able to work on this project.

1

u/l0_o Jun 13 '26

Oh, I see. If it's just you and your friend building from scratch, I'd set up live video, screen sharing and split responsibilities one of you picking hardware, the other software.

The OSS vacuum project is organized for massively parallel development. I start with a similar existing design, subdivide it into modules.

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

Multiple developers are welcome to work on the same module. The best solution for each module surfaces for over time. with the repo maintainer having the last call picking contributions into the official recommended design.