Revive a cloud-dead robot vacuum with a local server
A user had Claude Code reverse-engineer a $400 robot vacuum's link to its shut-down cloud and build a local server; they say it now cleans on schedule again.
Done with Claude CodeClaude Opus 5.5
What they did
The poster's $400 robot vacuum sat in a cupboard for two years after the maker's online service shut down. They used Claude Code to work out how the robot talked to those servers, then build a replacement server on their own computer. Their first request was to clean at 8:30 every weekday at 40% suction and return to the dock.
How it went
They say the robot works again, handling navigation itself while their computer runs the server and schedule. They tested it with internet blocked, after a server restart, and with the robot disconnected.
Worth knowing
The computer must stay on to run the server and schedule. The author checked that a restart would not repeat a cleaning job and that lost connections were flagged.
Try it yourself with Claude Code
My [robot vacuum brand and model] stopped working because the maker's cloud service shut down, but the hardware is fine. Help me figure out how it communicates on my home network and build a small local server on my computer to control it. Explain your plan and each step before changing any device settings. Then set a schedule: clean at [time] on [days], use [suction level], and return to the dock when done. Before we finish, help me test that it works with internet blocked, that restarting the server doesn't repeat a job, and that a lost connection is clearly flagged.
Swap the highlighted [parts] for your own details.
Source: X · @mika_systems · Oct 19, 2026
Written with AI assistance from the original post and checked against our editorial guidelines. Results are as reported by the source, not independently verified. Spotted a mistake? Tell us.
