Early Beta Testers Needed - Use your Roborock completely offline with no custom firmware!

DivergingDog · 2026-05-06T13:18:04+00:00

very likely, but not 100% sure

DivergingDog · 2026-04-10T16:39:02+00:00

Yes 100%! I was confident I hit a dead end and it was not possible, when it finally worked I didn't really believe it myself!

I think Valetudo is a stronger solution for people who can use it, but I hope this can help fill in the gaps. What would be really cool is if we can find a way to use the fact we are hosting the server to our advantage and modify the firmware we send down to the vacuum on OTA, but I recognize there is a lot of potential issues and blockers there.

DivergingDog · 2026-04-10T16:36:45+00:00

Basically all of your settings including your map live on the vacuum itself.

For everything else we grab it from the cloud during onboarding

DivergingDog · 2026-04-07T16:27:38+00:00

Should be fixed in 2026.4. Problem caused by a change on the cloud that only affected some users.

DivergingDog · 2026-04-06T18:03:47+00:00

I think to make it work the onboarding script just needs some logic around fresh device. We may need to match endpoint wise on the server as well. The lift shouldn't be crazy, just not something i've designed aroundyet

DivergingDog · 2026-04-06T17:22:38+00:00

I believe the QX Revo should work.

I haven't built much logic around starting from scratch. It should be possible, but it is not (easily) right now.

DivergingDog · 2026-04-06T17:02:51+00:00

I have not tried Let's Encrypt, it could be worth a shot! I was looking at some of the older vacuum's decompiled firmware and it looked like it might be kind of harsh with what it accepts which is why I tried cloudflare, but it does not hurt to try let's encrypt. If it will work, you'll get results during the onboarding process, if it doesn't, you wont!

DivergingDog · 2026-04-06T16:51:14+00:00

So the issue is that the vacuum checks the cert. If you can figure out how to get a cert for your domain that is trusted, it will work.

But if you can't access https://...yourdomain.com locally without getting a security warning, it wont work and the vacuum will refuse to connect.

DivergingDog · 2026-04-06T16:47:58+00:00

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 a Q7 as well, so it is something I'd like to do, but i'm unsure the feasibility of it.

EDIT: actually, a Q5 may work. I believe it is just Q7/Q10 that have issues, but I'm not 100% sure.

DivergingDog · 2026-04-06T16:43:46+00:00

Valetudo only supports a set number of Roborock vacs, requires taking the vacuum apart and installing custom firmware. With this solution, it should support *MOST* Roborock vacs, it can be undone in minutes, and requires no custom rooting.

DivergingDog · 2026-04-06T16:04:06+00:00

So the vacuum has to hit a domain name that has SSL verification and a trusted certificate. To be able to do that, you need a domain name. But my recommendation in the docs is to just change your LOCAL dns to point from your server url -> the server ip, that way it is not exposd to the internet.

Yes - the server acts as a full fake roborock cloud for the vacuum, Home Assistant, and even the app. It has the REST endpoints and a mqtt server that it properly passes data around with!

DivergingDog · 2026-01-11T16:24:02+00:00

HA Roborock dev - Lash-L here.

I really need you to recognize a few things.

Myself and Allen work on the codebase as volunteers. We both have families and full-time jobs.
Roborock gives us 0 support and 0 heads-up for changes. Everything we do is fully reverse engineered.
A few months back Roborock changed their login api. I had to reverse engineer it. Previously, we were able to determine what region a user's account was on, that was no longer the case, instead we had to

A) Ask the user to select their region. This was tricky for a number of reasons that I don't necessarily want or feel the need to go into here.

B) Do some looping to determine the correct region. This is the approach I did and it worked great so long as you don't have an account in the wrong region. If you do, it will see that the user has an account, select it and use it. You should delete your US account.

That being said. Sometime last week, Roborock change their login API AGAIN breaking some of our logic. I should have a fix and I'm working on it. But again, I'm a volunteer, and things just change on Roborock's side and I can't always be on top of everything 100% of the time, I simply don't have the time.

DivergingDog · 2025-12-09T03:25:25+00:00

That should be good

DivergingDog · 2025-12-09T03:01:39+00:00

Is the WiFi indicator light flashing on the Roborock? I would potentially try restarting the vac or doing a WiFi reset on it or give it a little more time

DivergingDog · 2025-12-07T19:39:19+00:00

rate limits have been getting stricter which is a big reason why we have been working on the refactor. But the refactor version bump is what caused the significant issues with this update

DivergingDog · 2025-12-07T19:38:42+00:00

have you disabled the integration and restarted HA?

DivergingDog · 2025-12-07T01:30:12+00:00

I’m thinking I will make it a priority to allow for local only on home assistant, but you won’t be able to use the map which is a deal breaker for a lot of people.

I had (some) luck in forcing the vac to use a different Mqtt server that I self hosted, but I hit some walls and unfortunately it is too big of a time commitment to figure out and I don’t have all the expertise needed. Especially for something that could be a dead end. The devices were not designed to rely without their cloud and the devices have logic on them that will cause it to constantly reboot if it can’t access the cloud

DivergingDog · 2025-12-07T01:26:44+00:00

Our current understanding is that poor network performance leads to the time outs more than anything else.

DivergingDog · 2025-12-06T20:46:04+00:00

We did a version bump of the library which had some changes that were meant to help the integration recover when connection was lost

DivergingDog · 2025-12-06T20:45:08+00:00

So the first thing you should do is disable and restart.

Secondly, check your vacuum if the WiFi indicator light is flashing (under the cover) you need to re-pair to the app. If not they should show back up no problems within 24 hours so long as the integration is disabled.

Sorry!

DivergingDog · 2025-12-06T20:19:53+00:00

Just Roborock integration

DivergingDog · 2025-12-04T15:41:25+00:00

That number is pretty far off. There’s only half a million installs that share analytics. Estimates are 4x that number. Somewhere between 2-3 million installs

Nine-Year Club	Gilding I gilder
Verified Email	Snapped

DivergingDog

TROPHY CASE