any roborock/google home users ?

Nov 04, 2025 Last reply: 8 months ago 4 Replies

Following the death of my Ecovacs, a combination of Amazaon special offers and memories of seeing "roborock" getting a lot of love on the Home Assiatnt robot vacuum reddit, I plumped for a Q10S a couple of weeks ago.



However I since discover that it has a newer firmware that (currently) makes it incompatible with Home Assistant.



"Not to worry" I thought. That was a nice-to-have, I'll set it up in Google Home.



However try as I might and with advice from roborock support (so using a different phone, new roborock account, new google account) I cannot get the process to complete. It always ends in a 404 error.



Capturing the URL that google is generating to initiate the OAuth process has allowed me to validate it, and the roborock endpoint does exist.



roborock support have now given up ("cannot replicate") and suggested I contact google. So while that isn't happening, I just thought I would risk asking here :)



Personally I am very very doubtful that this error is only affecting me. And given the popularity of roborock in the UK (500+ sold in *the last month) and world wonder what is going on.


This was a different make, but...

formatting link

I don't have any robovac, but a general comment on adding devices to Google Home, if it's a 2.4GHz device, make sure the phone/tablet you're setting it up from is (temporarily) on the same 2.4GHz SSID, even if your AP bridges all radios together ...

It's not a device issue - the vac works flawlessly with it's app.

The problem is connecting the google home app/service to the roborock one (which is device independent).

Have currently zoned in on the fact that https://oauth- redirect.googleusercontent.com leads to a 404. This is the URL that google themselves give in their OAuth flow documentation. So either there is something big or weird going on at the chocolate factory, or my home internect is borked.

After some quite deep dives into the bowels of various behaviours, I found a flaw/bug in Google Home on Android that generates the wrong data for the OAuth process to complete.

Luckily SWMBO has an iPad, and the Apple version worked perfectly.

Top marks to rr support who engaged with me on this.

As usual cold slop to google who remain as useless as ever.

Join the Discussion

Have something to add? Share your thoughts — no account required.

Didn't find your answer?

Ask the community — no account required