NOW LET US – AI RAG SaaS Studio TP.HCM
NOW LET US
Digital Product Studio
Back to news
DEV-TOOLS...4 min read

Show HN: We built a camera only robot vacuum for less than 300$ (Well almost)

Share
NOW LET US Article – Show HN: We built a camera only robot vacuum for less than 300$ (Well almost)

Two engineers, Bruce Kim and Indraneel Patil, built a DIY robot vacuum using only a camera and behavior cloning AI for approximately $300.

Team: Bruce Kim, Indraneel Patil

Bruce and I moved in together and were discussing buying a robot vacuum, but then decided to build one instead! Some design principles:

  • Buy as many off the shelf parts as possible
  • Keep the budget less than 500$
  • It should have a minimum battery life to be able to navigate around the house and vacuum the floor, so that we only have to charge it once a week

Hardware

Software

Since we dont have any compute on the robot to do inference we decided to stream image frames from the robot to a laptop and then run inference on the robot and return result back to the robot for navigation. We teleoperated the robot around the house to collect tuples of image frame and a discrete navigation action. Our discrete navigation action set was:

COMMANDS = {
keyboard.Key.up: "FORWARD\n",
keyboard.Key.down : "REVERSE\n",
keyboard.Key.left: "TURN_CCW\n",
keyboard.Key.right: "TURN_CW\n",
keyboard.Key.space: "STOP\n"
}

Then we trained a simple CNN with behavior cloning to learn from these expert trajectories.

Observations:
  • Lots of false positive reversing, like for these there was no need to reverse so maybe it doesnt have a good perception of depth? -> It doesnt need a good perception of depth it only needs to worry about the ground plane in front of it

  • In the kitchen seems to just keep oscillating between forward and reverse -> This could be lack of good data

  • Should have created a validation / training split

  • It kept getting STOP for this, where clearly there is space ahead for it to move into

  • Kept getting FORWARD for this, when clearly an obstacle can be seen

  • Dont think it is trained super well

  • There is some motion blur but most images are really nice

  • STOP action can get the robot stuck in front of an obstacle, is that really needed? Can we remove STOP? This paper only use the STOP action when robot has reached the goal

  • I feel like what its learnt is quite random but it has learnt to back up when very close to an obstacle or its about to hit something which is really nice

  • What it hasnt learnt is how to determine there is free space in front of you

  • Also doesnt know how to navigate out of tough spots

  • There is a signal in the image for it to learn forward and reverse but there is no signal in the image for it to learn clock wise and counter clockwise

Training Experiments:

Calculating Validation Loss

We split the data into training and validation sets and then we found that the network has a very low validation loss.

So there could be two explanations:

  • Network is overfitting training data
  • There is not enough signal in the data to learn

We can test the first explanation through data augmentation or pre training the network on a large dataset and see if that improves validation loss.

Data Augmentation

augmentations = {
"grayscale": T.Grayscale(num_output_channels=3),
"gaussianblur": T.GaussianBlur(kernel_size = (3,5), sigma = (2,9)),
"noise:": addnoise,
"colourjitter": T.ColorJitter(brightness=0.5, contrast=0.5, saturation=0.5, hue=0.1),
"original": lambda x: x,
}

I wrote a script to apply these augmentations on the original dataset of 600 image-action tuples to get a data of size of about 30000.

Validation loss is still high and does not follow the training loss curve.

Pre-training network on ImageNet

I followed this tutorial to pre train the network on image net.

Validation loss still does not converge which means that the network is not overffitting, the dataset just does not have enough signal to learn.

Future work

  • Add history of image frames, instead of a single frame
  • Collect more and better data: Our robot teleoperation wasnt always consistent and had some randomness in it.
  • Go through the data, eliminate noisy data and so on.

Summary

This was a lot of fun! we built a very capable robot. Since we were working on the project only part time, on evenings and weekends it took us about 3 months to build the robot and another month to write the software. We were able to achieve the budget requirement and then robot costs about 300$ only.

Some limitations:

  • The vacuum isnt super strong and I wish we had spent more time just designing the vacuum, the inlet and its power specs (Cant believe this is the second time I made this mistake)
  • We had to use two separate batteries, one to power the vacuum and the other to power the rest of the system because the vacuum motor power on causes a voltage drop in the circuit
  • No autonomous charging
  • Robot isnt completely autonomous and gets stuck in places so needs baby sitting while it is cleaning.
© 2026 Now Let Us. All rights reserved.

Source: Hacker News

Advertisement
Ad slot ready: 5887729102

More in this category

NOW LET US Related – Leaving Mozilla

dev-tools

Leaving Mozilla

A poignant and candid reflection from a 15-year Mozilla veteran upon their departure. The author highlights the leadership's missteps in trying to emulate tech giants and urges Mozilla to return to its core values: community and uniqueness.

NOW LET US Related – Shepherd's Dog: A Game by the Most Dangerous AI Model

dev-tools

Shepherd's Dog: A Game by the Most Dangerous AI Model

A developer tested Anthropic's latest, supposedly 'too dangerous' AI model by asking it to build a long-held game idea in a single shot. The model succeeded, generating a complete 2,319-line game after a 45-minute reasoning session.

NOW LET US Related – Open source AI must win

dev-tools

Open source AI must win

If artificial intelligence becomes a utility rented only from a few closed institutions, humanity loses its operational freedom. Open-source AI is a vital infrastructure for the future of our digital society.

NOW LET US Related – Statement on US government directive to suspend access to Fable 5 and Mythos 5

dev-tools

Statement on US government directive to suspend access to Fable 5 and Mythos 5

The US government has issued an export control directive forcing Anthropic to suspend all access to its Fable 5 and Mythos 5 models due to national security concerns, a move the AI safety startup strongly disputes.

NOW LET US Related – Electric motors with no rare earths

dev-tools

Electric motors with no rare earths

Renault Group is pioneering the development of electrically excited synchronous motors (EESM) that eliminate the need for rare earth magnets, reducing dependency on global monopolies while driving efficiency and sustainability.

NOW LET US Related – Swift at Apple: Migrating the TrueType hinting interpreter

dev-tools

Swift at Apple: Migrating the TrueType hinting interpreter

Apple has rewritten its TrueType hinting interpreter from C to memory-safe Swift for its Fall 2025 OS releases, improving security and boosting performance by an average of 13%.

EXPLORE TOPICS

Discover All Categories

Deep dive into the specific technology sectors that matter most to you.