The chronicle ends not with a manifesto but with a small, domestic image: a robot pausing at the threshold of a sunlit room, its motors decelerating in a way that tells you someone chose to code kindness into its motion. The firmware that lived inside it carried traces of late-night arguments, careful ethics, and patient craft. It knew, in its compact logs, not only the geometry of chairs and rugs but the choices of a few people who preferred to make their machines reflect the values they held dear.
Two primary paths have emerged for users who want to keep their Neatos out of landfills:
Once you have SSH access, you essentially have a small Linux computer with wheels and a LIDAR sensor.
If you want to move away from Neato's cloud entirely, you can "root" the robot by adding new hardware to its internal serial port. Neato Botvac D3, D3 Pro, D4, D5, and D7 Firmware - GitHub
Linux-based models (like the Botvac Connected series) are much easier to exploit than older, microcontroller-based models (like the XV series), which require hardware programming tools.
When discussing custom firmware for robot vacuums, the most prominent open-source project is . Valetudo is not a full operating system replacement from scratch; rather, it is a binary that intercepts cloud communications on Linux-based vacuums. It tricks the onboard operating system into thinking it is talking to the official cloud, redirecting all maps, controls, and schedules to a local web interface hosted directly on the robot.
But the most profound feature is arguably the most mundane: . Stock firmware often bricks a robot after a specific error, like a failed wheel motor or a degraded battery, forcing you into an expensive service loop. Custom firmware allows you to clear error logs, recalibrate sensors, and even disable faulty components to limp the robot along while you wait for a replacement part. In a world of planned obsolescence, this is an act of quiet revolution.