This is an automated archive made by the Lemmit Bot.
The original was posted on /r/homeassistant by /u/DivergingDog on 2026-04-06 15:45:12+00:00.
Hi everyone!
Lash-L here (one of the main maintainers of the Roborock integration). For a long time one of the biggest asks from users was that they wanted to be able to use their vacuums completely offline. In the Roborock integration, we connect to the vacuum using local protocol, but there are two limitations that block you from being able to block the vacuum from hitting the internet.
- Roborock forces all map related messaged to go to the cloud. This is the only cloud-required feature.
- If the roborock vacuum cannot access Roborock's cloud, it will not allow ANY messaging. The vacuum will constantly restart its internet trying to reconnect to Roborock's cloud.
Cloud problems have been the number source of issues for Robroock in HA. They change their login flow, they more aggressively kick clients off of mqtt topics, etc. Every time that happens, things break, I have no warning and I play catch up and some users end up getting stuck with a temporarily broken product.
It's taken a long time and a lot of reverse engineering, but I made a solution that I am pretty happy with and that has been working well for me in my home.
https://github.com/Python-roborock/local_roborock_server
I am releasing this in EARLY beta. If you are technical in nature and are okay with using something that may not work 100%, I would love if you would give this a try. If you aren't super technical, I'd recommend starring the repository and coming back to it later as I will do an 'official' v1 release that should have some quirks ironed out. You can undo it in 2 minutes just by doing the wifi onboarding via the official Roborock app.
The current limitations:
-
You must own a domain name
-
I highly recommend you do not make the server accessible outside of your network as there is limited authentication on it
-
Roborock Q7/Q5 series is not supported and may never be supported. (This adds some quirks if you own one of these devices and a supported device)
Here's a rough walkthrough of the setup:
- You clone the repository locally
- You run a configure script to build your config
- You launch the docker server and clone your cloud data (i.e. your devices, your routines, rooms, etc.)
- You go through an onboarding process on your vacuum 2-3 times
- You manually update your HA config entry file and run a script to get access on your phone if you would like that.
The full walkthrough is here: https://python-roborock.github.io/local_roborock_server/installation/
The Ideal beta testers:
-
Understand there might be bugs
-
Willing to send PRs around things like documentation (This is huge! I need help from people making instructions more exact!)
-
Understands things like DNS, docker, etc.
-
Has about ~ 1 hour to get things setup.
-
Is able to diagnose some issues themselves
This is an EARLY beta. In the future I hope to have it working as a home assistant addon that should be much easier to install, but until then I need people to test it so we can see what is working, if there is any functionality I still need to recreate, and what the pressure points are.
If you're interested in learning more about how it works, you can also check out my linkedin post or the technical writeup
Edit:
FAQ:
Q: How is this different from Valetudo?
A: Valetudo is awesome, But it is only supported on some devices, it requires taking your vacuum apart and flashing it. This requires not physical or firmware modifications and can be undone in minutes. There is a world though that this software could be a staging point for installing Valetudo on Roborock's without any disassembly, but I would leave that to the Valetudo team to figure out. We own the server stack, so theoretically we could own the firmware installation.
Q: Will Q5/Q10 be supported?
I'm not sure. These vacuums seem like they were developed by an entirely different team than the other roborock vacuums. They do not onboard like the other ones and it will take a lot of looking to see if I can find a way to make it work. I own one as well, so it is something I'd like to do, but i'm unsure the feasibility of it.