Roborocks Integration Constantly Needs Reauthentication

Configuration
1

I searched for this and was surprised not to find discussion of it. Sorry if I missed it.
My roborocks integration keeps saying the authentication expired. It happens once or twice a day and just started a couple of weeks ago. It could have been after an update, but I didn’t really keep track. I can re-authenticate and everything is fine for half a day. Funny thing is that last night I forgot to re-authenticate and the vacuum ran fine. So I really don’t even know what won’t work in this case.
If you have any ideas on what’s going on, let me know.

2 Likes
2

What version of HA are you on?

Using the Core integration? This was a problem a while back but got fixed.

3

I’m on 2026.3.1. I’m always up to date.
If by Core Integration, you mean an integration as opposed to an add-on (app now I guess), then yes.
I do have a Qrevo CurvX. The doc on the integration says Q series aren’t fully supported. But, I’ve had it for a few months. Up until recently, it only asked to authenticate once every few weeks. And other than this issue, the integration works great. Having said that, all I really do is start the vacuum using a Google Calendar entry.

4

I mean the one shipped with HA rather than a 3rd party one via HACS.

Have you tried to reset the wifi credentials? I seem to remember that when this was a common issue last year (the one that got fixed), you needed to essentially reset the vacuum so it got a new token or whatever from the Roborock cloud.

5

Ok, yeah, the it’s the one that came with HA core. Here’s the first part of the debug output that shows version info in case it helps:

{
  "home_assistant": {
    "installation_type": "Home Assistant OS",
    "version": "2026.3.1",
    "dev": false,
    "hassio": true,
    "virtualenv": false,
    "python_version": "3.14.2",
    "docker": true,
    "arch": "x86_64",
    "timezone": "America/Los_Angeles",
    "os_name": "Linux",
    "os_version": "6.12.67-haos",
    "container_arch": "amd64",
    "supervisor": "2026.02.3",
    "host_os": "Home Assistant OS 17.1",
    "docker_version": "29.1.3",
    "chassis": "vm",
    "run_as_root": true
  },

I will try the wifi thing. Thanks.

6

So, I reset the wifi of the vacuum (pressed the two buttons till it said “resetting wifi”, then reconnected to my wifi). The problem persists. Honestly, I’m not sure if this would have caused any interaction with the cloud but maybe it did. I’ve also removed the integration and added it back. The only thing I haven’t tried is to delete the device. I’d rather not as I assume I would lose the map. And, I have no reason to believe this would resolve the issue anyways :).

7

I was having this problem but it seemed to have stopped once I went to 2026.3.1.

8

How ironic as it seems to have started for me around when I went to 2026.3.1 (or at least sometime into 2026) :).

9

I found this:

It sounds exactly like what I’m experiencing. Even the timing (starting in 2026.2.3) sounds about right too.
There seem to be a few other reports that people are saying are duplicates of each other. I did have a hard time seeing if anything was actually fixed. I have to admit that I don’t have a lot of experience rummaging around in git so I could have missed something.
Anyways, the reports I saw weren’t that old so maybe the issue is being worked on.

1 Like
10

The Roborock reauthentication error is addressed in this GitHub post. The bottom line is that the problem has been identified and a fix is scheduled for 2026.3.2. Then, you’ll have to reauthenticate one last time.

2 Likes
11

2026.3.2 just came out. I upgraded. I’ll report back to let everyone know if the problem is, in fact, fixed.

12

For the the lasted HA update 2026.3.2 does not fixed the need to reauthenticate Roborock.

13

Yeah, not for me either :frowning:
And, the GitHub post has been updated with lots of comments saying the issue was not resolved for them either.

14

Same here. Still getting the authentication expired. Doesn’t affect my automations but just annoying that the error is there.

15

I hope Roborock is not planning to close its door for smart home integrations… Is there a way to go fully local, something like “Roborock Cloud Cutter”…?

16

It also keeps happening to me daily.

  • Installation method Home Assistant OS
  • Core 2026.3.4
  • Supervisor 2026.03.2
  • Operating System 17.1
  • Frontend 20260312.1
17

Same issues here - following…

Installation method Home Assistant OS
Core 2026.3.4
Supervisor 2026.03.2
Operating System 17.1
Frontend 20260312.0
18

+1 for me, daily re-authentication required:

  • nstallation methodHome Assistant OS
  • Core2026.3.4
  • Supervisor2026.03.2
  • Operating System17.1
  • Frontend20260312.1