External Integration - Roborock

@ruegerth No worries Tom, you didn’t step on anyone’s toes :grinning_face_with_smiling_eyes: And if my message seemed abrupt, it’s probably my fault (and maybe a little bit the fault of machine translation) — that wasn’t the intention at all.

On the subject, I agree with you more than my first message might have suggested. The README itself says it: the robot part had never run on a real Roborock before. Your question is therefore legitimate: should we publish an integration in this state?

I think yes, but not just any way:

  • No publication, no real tests. No developer has all the models of a brand, and Roborock releases several per year. If we wait for someone to test everything, the integration will never be released. Your message shows this well: it’s because it’s published that you were able to try your two robots and find all that.
  • However, you’re right on an important point: the user must know what to expect. An integration that hasn’t yet run on real hardware should clearly announce this from its presentation (« beta, testers welcome »), and not just in the README that few people read. The store doesn’t yet allow this to be indicated: it would be a good idea to suggest for Gladys.
  • The risk remains limited: at worst, the robot cleans the wrong room or doesn’t react. It’s not a smoke detector. You can uninstall at any time, and each correction comes quickly with a new version.

And that’s exactly why feedback like yours counts so much. Your issue #13 is super clear, with each test, what was expected, and what actually happened. For a developer, that’s the ideal feedback :folded_hands:

What I take from your message:

  • the room and mode chosen do not match what the robot does (the most annoying);
  • sub-settings (suction power, washing intensity, number of passes, path) are missing, especially on recent models;
  • several rooms at once, rather than launching them one after the other;
  • mixed translations;
  • the widget, which doesn’t always respond.

I have a Saros 20x: if I have time, I’ll retest your tests at home, no promises. But with a second recent model, it could help @Lokkye find where the offset comes from.

Thanks again for the time spent testing, and keep reporting all that! :+1:

Personally, I’ve forked the initial dev and then pushed several evolutions regarding my QV 35A hardware…

Everyone is free to do the same thing :man_shrugging:…

Have a good Sunday…

From my side, what I can confirm is that @guim31 (and claude!) developed the integration for the Dreame vacuum robot that he didn’t own but that I did (a model from two years ago), and in one week we developed an app that solves all the problems you @ruegerth describe! From my side, I no longer need the official Dreame app to start vacuuming and mopping in the order I want and with custom settings from Gladys alone. Even the cleaning path appears on the map in Gladys.

@guim31: All good, I always used DeepL at the beginning and I’m not sure if the translation was clean in every little branch, but the current community translation here is already much much better than the DeepL detour.

@spenceur: If that were the case, there would be no need for integration and, at an even more abstract level, no Gladys Assistant. Everyone can do the same thing

@Chris75: Exactly, that’s how I was as a tester during the Roku integration. The developer managed it in three days. Superb work, super fast

Thanks for all your precise feedback. I’m sure @Lokkye will be able to move forward with this and unblock you.

I didn’t understand what you’re talking about :man_shrugging:

If I’m not mistaken, he means that forking isn’t a solution, because if we follow this logic, we don’t need Gladys to evolve or even exist if we build it ourselves.

If that’s not what he meant, we’ll have to ask ruegerth directly :wink:

My fork is just for making merge requests to the main repo to help the developer with the integration itself. I don’t see how that undermines a project when you’re helping. :man_shrugging:
Isn’t the point of the community to help each other? :thinking:

I don’t know about ruegerth, but I didn’t understand your message that way, sorry!
I had interpreted that your changes were personal, and not shared for the main repo! :wink:

I totally agree with you, I think I took my Sunday neurons out… :sleeping_face:

Well, it was lively here :slight_smile:

Thanks @ruegerth for this detailed feedback, it’s exactly what we need to move forward without having the robot at hand. I’ve taken the three points from the issue into the PR callemand/gladys-roborock#14. And published in version 2.7.0

Cleaning Modes. You’re right: the integration mapped Gladys’ “cleaning mode” to the suction level (Quiet / Balanced / Turbo / Max), which is correct on an S6 but doesn’t make sense on a Saros 10R, where the real choice is Suction / Suction & Mopping / Mopping. Now, for robots that declare a water flow, the Gladys selector only offers these three modes (Auto = Suction & Mopping, Suction, Mopping) and sends them as the Roborock app does, keeping the suction power and water flow already set on the robot. Suction power remains adjustable separately, via the widget buttons or the scene action.

Wrong Room. Looking at your screenshots, the app displays “Vollreinigung” in both cases, so a full cleaning. In your tests you also set “Modus” to “Reinigen”, and this setting launched a full cleaning regardless of the room choice. The app then showed the room where the robot was (12 near the station, then 11), hence the impression of a random room. With the PR: “Reinigen” with a selected room cleans that room, does nothing if the robot is already cleaning, and choosing a new room during cleaning first stops the robot.

Languages. The widget only had English and French, and some values were hardcoded in French. Everything is now available in German (and Spanish), and the status or dates follow Gladys’ language.

What’s Not Covered, and what I note as improvements: “Vacuum then Mop” (I don’t have the corresponding command yet), selecting multiple rooms at once, and sub-settings (water flow, path, number of passes). For now, the safest option for these cases remains the Roborock routines, which are exposed as buttons.

One important thing: the mode mapping comes from the python-roborock library and has only been validated against simulators. If you can test the version that will come out of this PR on your Saros 10R and tell me if the three modes and room cleaning behave like in the app, it will allow us to confirm before announcing it as stable. And yes, “beta” would be more honest for recent models: I’ll indicate this more clearly.

@Lokkye do you have a way to add the action « was the vacuum cleaner used today? (Yes / No) »

I started adding the logic but I think the action manifest is missing :thinking:.
Thanks for all your feedback anyway

On to the next test of the Saros 10 with the integration version 2.7.0:

– Widget and devices now available in German, thank you for this

-- There is still a problem with the display of the widget, there seems to be some kind of timing issue, i.e.: the graphical display comes before the data? I unfortunately had to remove the devices and find them again, then it worked

Test 1: What happens if you simply click on « Start » in the widget without any further settings?

Well, it takes the setting « Vac&Mop » for all rooms. The manufacturer’s app also shows this:

When it is started, all feedbacks from « Loaded », « Clean Mop », « Vacuum » to « Return » and « Empty » appear. Top so far, super.

Looks good so far.

Test 2: We want to vacuum only, the Saros10 R has a special feature here, it puts down its mops.

Now the question for the inexperienced user is: Where should he select what so that only one room is cleaned.

Because there is the selection Clean twice:

and here:

We will not take the operating mode now, but the cleaning mode and select room 10:

It starts, it puts down its mops and drives into the room, so far everything is good, the integration works. Super, but why does it stop again in the middle of the room and drive back:

We simply start pure vacuuming in room 10 via the manufacturer’s app and look, the entire room 10 is vacuumed:

Here for comparison, vacuuming room 10 in the manufacturer’s app when started via the integration:

So far, initially a great job. Well done. There are still a few minor things, but nothing big anymore.

I would do without the « Quiet » button in the widget. Start and return are sufficient.
In the device, I would separate the information better. The double display of « Clean » can be confusing.
The special modes like « Vac&Mop » are missing, but much much more important:
Multiple room selection.

Well done, I like the integration, especially the widget I find super.

Regards

Tom

@spenceur it’s already possible without adding anything: each robot has a “Cleaned today” feature that is 1 if a cleaning has started today and 0 otherwise. It updates every 30 seconds and resets to 0 at midnight.

To use it in a scene:

  1. Action Device → Retrieve the last state, choosing “Cleaned today” from your robot.
  2. Action Condition on variables: value = 0 to continue only if the robot hasn’t passed yet (or = 1 for the opposite).
  3. Then your action Roborock → Start cleaning, a room or a routine.

Example: every day at 6 p.m. → Retrieve “Cleaned today” → Condition = 0 → Start cleaning. The robot won’t run again if it has already passed during the day.

There is also “Last cleaning start” (date of the last start) if you want a rule like “not passed for 2 days”.


@ruegerth thanks for this second test, and good news: the “Vacuum” mode was indeed taken into account by the robot (mops placed, correct room), so the mapping of the modes is validated on the Saros 10R.

A few quick answers:

  • “Vac & Mop” exists, it’s the “Auto” option (the mode names are imposed by Gladys, I can’t rename them). The other entries should no longer be offered for your robot if Gladys is version 5.2.0 or higher: can you check your Gladys version?
  • “Silent” button: in the widget settings, buttons 3 and 4 are configurable, you can set them to “None”.
  • Two “mode” lines: the first (Reinigungsmodus) chooses vacuuming/washing, the second (Betriebsmodus) starts or stops. The next robots discovered will have more explicit names; for yours, you can rename them in Gladys.
  • Multiple rooms at once: not possible from the device card for now (Gladys doesn’t have a multi-select component). In the meantime, the scene action “Clean rooms” accepts a list (“10, 12”), and the Roborock routines are exposed as buttons.

The real problem remains: the robot stops in the middle of room 10 and returns after 2 minutes. I can’t reproduce it without a robot, and version 2.7.0 didn’t log enough to understand. I just published 2.7.2, which writes to the logs every command sent to the robot, every response, and the robot’s status every 30 seconds.

If you can help, here’s the ideal test:

  1. Update the integration to 2.7.2.
  2. From Gladys, select room 10 with the “Vacuum” mode (Aspiration), and let it run until the robot returns.
  3. Do the same thing with the “Auto” mode (Vac & Mop), to see if the problem depends on the mode.
  4. In Gladys, on the Roborock integration page, Logs tab, “Refresh” button: copy the lines that cover the two tests, here or on the GitHub issue.

With that, I’ll know if it’s Gladys sending something to the robot during cleaning, or if the robot stops on its own, and with what code.

Thanks again, your tests are really advancing the integration.

@Lokkye I’ll do that gladly, tomorrow is cleaning day (but not for me)

Best regards

Tom

I have a small suggestion :wink:

Is it possible to add the option to enable or disable battery status, area, and map individually in the widget? Background of my question: Not everyone always wants to display everything, and I have other robots, e.g. an Ecovacs, and I would like to have both widgets side by side. But my inner monk can’t accept that both maps are of different heights and look different. Could these three things be turned on and off individually (and battery and area would each be 100% if the other is not present)? I would be satisfied. Haha :smiley:

PS: A visual error in the area could also be fixed in the process :slight_smile:

@Lokkye Hello, as promised, the tests for Saros 10 R and the 7er…

Unfortunately, the received code is not accepted? Could be due to my LAN / WIFI, but the previous tests were successful.

Here is the log for this:

2026-10-19T11:02:15.425Z] [INFO] [roborock:rest] Login code requested for tom@rueger.eu (``https://usiot.roborock.com``) [2026-10-19T11:02:15.425Z] [INFO] A code was sent to tom@rueger.eu [2026-10-19T11:03:00.062Z] [INFO] [roborock:rest] Logged in to the Roborock cloud (``https://usiot.roborock.com``) [2026-10-19T11:03:01.082Z] [ERROR] Could not link the Roborock account Error: Roborock request failed: GET -> HTTP 401 at #fetchJson (file:///app/src/roborock/restClient.js:340:21) at process.processTicksAndRejections (node:internal/process/task_queues:104:5) at async RoborockRestClient.getHomeData (file:///app/src/roborock/restClient.js:238:22) at async #loadDevices (file:///app/src/roborock/client.js:209:22) at async RoborockAccountClient.linkWithEmailCode (file:///app/src/roborock/client.js:187:5) at async file:///app/index.js:1013:5 at async GladysIntegration._runCommand (/app/node_modules/@gladysassistant/integration-sdk/lib/gladys-integration.js:1565:22) at async GladysIntegration._handleMessage (/app/node_modules/@gladysassistant/integration-sdk/lib/gladys-integration.js:1477:9) { status: 401 } [2026-10-19T11:03:07.672Z] [ERROR] Could not link the Roborock account Error: Roborock refused this code (error 2018) at RoborockAccountClient.linkWithEmailCode (file:///app/src/roborock/client.js:181:25) at process.processTicksAndRejections (node:internal/process/task_queues:104:5) at async file:///app/index.js:1013:5 at async GladysIntegration._runCommand (/app/node_modules/@gladysassistant/integration-sdk/lib/gladys-integration.js:1565:22) at async GladysIntegration._handleMessage (/app/node_modules/@gladysassistant/integration-sdk/lib/gladys-integration.js:1477:9) { reason: 'roborock_code_refused', [cause]: Error: Roborock API error 2018: email code error at #fetchJson (file:///app/src/roborock/restClient.js:352:23) at process.processTicksAndRejections (node:internal/process/task_queues:104:5) at async #loginAcrossRegions (file:///app/src/roborock/restClient.js:173:22) at async RoborockAccountClient.linkWithEmailCode (file:///app/src/roborock/client.js:176:7) at async file:///app/index.js:1013:5 at async GladysIntegration._runCommand (/app/node_modules/@gladysassistant/integration-sdk/lib/gladys-integration.js:1565:22) at async GladysIntegration._handleMessage (/app/node_modules/@gladysassistant/integration-sdk/lib/gladys-integration.js:1477:9) { code: 2018 } } [2026-10-19T11:03:41.587Z] [INFO] [roborock:rest] Login code requested for tom@rueger.eu (``https://usiot.roborock.com``) [2026-10-19T11:03:41.587Z] [INFO] A code was sent to tom@rueger.eu [2026-10-19T11:04:06.898Z] [INFO] [roborock:rest] Logged in to the Roborock cloud (``https://usiot.roborock.com``) [2026-10-19T11:04:07.826Z] [ERROR] Could not link the Roborock account Error: Roborock request failed: GET -> HTTP 401 at #fetchJson (file:///app/src/roborock/restClient.js:340:21) at process.processTicksAndRejections (node:internal/process/task_queues:104:5) at async RoborockRestClient.getHomeData (file:///app/src/roborock/restClient.js:238:22) at async #loadDevices (file:///app/src/roborock/client.js:209:22) at async RoborockAccountClient.linkWithEmailCode (file:///app/src/roborock/client.js:187:5) at async file:///app/index.js:1013:5 at async GladysIntegration._runCommand (/app/node_modules/@gladysassistant/integration-sdk/lib/gladys-integration.js:1565:22) at async GladysIntegration._handleMessage (/app/node_modules/@gladysassistant/integration-sdk/lib/gladys-integration.js:1477:9) { status: 401 } [2026-10-19T11:04:11.579Z] [ERROR] Could not link the Roborock account Error: Roborock refused this code (error 2018) at RoborockAccountClient.linkWithEmailCode (file:///app/src/roborock/client.js:181:25) at process.processTicksAndRejections (node:internal/process/task_queues:104:5) at async file:///app/index.js:1013:5 at async GladysIntegration._runCommand (/app/node_modules/@gladysassistant/integration-sdk/lib/gladys-integration.js:1565:22) at async GladysIntegration._handleMessage (/app/node_modules/@gladysassistant/integration-sdk/lib/gladys-integration.js:1477:9) { reason: 'roborock_code_refused', [cause]: Error: Roborock API error 2018: email code error at #fetchJson (file:///app/src/roborock/restClient.js:352:23) at process.processTicksAndRejections (node:internal/process/task_queues:104:5) at async #loginAcrossRegions (file:///app/src/roborock/restClient.js:173:22) at async RoborockAccountClient.linkWithEmailCode (file:///app/src/roborock/client.js:176:7) at async file:///app/index.js:1013:5 at async GladysIntegration._runCommand (/app/node_modules/@gladysassistant/integration-sdk/lib/gladys-integration.js:1565:22) at async GladysIntegration._handleMessage (/app/node_modules/@gladysassistant/integration-sdk/lib/gladys-integration.js:1477:9) { code: 2018 } } [2026-10-19T11:04:26.435Z] [ERROR] Could not link the Roborock account Error: Roborock refused this code (error 2018) at RoborockAccountClient.linkWithEmailCode (file:///app/src/roborock/client.js:181:25) at process.processTicksAndRejections (node:internal/process/task_queues:104:5) at async file:///app/index.js:1013:5 at async GladysIntegration._runCommand (/app/node_modules/@gladysassistant/integration-sdk/lib/gladys-integration.js:1565:22) at async GladysIntegration._handleMessage (/app/node_modules/@gladysassistant/integration-sdk/lib/gladys-integration.js:1477:9) { reason: 'roborock_code_refused', [cause]: Error: Roborock API error 2018: email code error at #fetchJson (file:///app/src/roborock/restClient.js:352:23) at process.processTicksAndRejections (node:internal/process/task_queues:104:5) at async #loginAcrossRegions (file:///app/src/roborock/restClient.js:173:22) at async RoborockAccountClient.linkWithEmailCode (file:///app/src/roborock/client.js:176:7) at async file:///app/index.js:1013:5 at async GladysIntegration._runCommand (/app/node_modules/@gladysassistant/integration-sdk/lib/gladys-integration.js:1565:22) at async GladysIntegration._handleMessage (/app/node_modules/@gladysassistant/integration-sdk/lib/gladys-integration.js:1477:9) { code: 2018 } } [2026-10-19T11:04:29.503Z] [INFO] [roborock:rest] Login code requested for tom@rueger.eu (``https://euiot.roborock.com``) [2026-10-19T11:04:29.503Z] [INFO] A code was sent to tom@rueger.eu [2026-10-19T11:04:47.741Z] [INFO] [roborock:rest] Logged in to the Roborock cloud (``https://euiot.roborock.com``) [2026-10-19T11:04:47.988Z] [ERROR] Could not link the Roborock account Error: Roborock request failed: GET -> HTTP 401 at #fetchJson (file:///app/src/roborock/restClient.js:340:21) at process.processTicksAndRejections (node:internal/process/task_queues:104:5) at async RoborockRestClient.getHomeData (file:///app/src/roborock/restClient.js:238:22) at async #loadDevices (file:///app/src/roborock/client.js:209:22) at async RoborockAccountClient.linkWithEmailCode (file:///app/src/roborock/client.js:187:5) at async file:///app/index.js:1013:5 at async GladysIntegration._runCommand (/app/node_modules/@gladysassistant/integration-sdk/lib/gladys-integration.js:1565:22) at async GladysIntegration._handleMessage (/app/node_modules/@gladysassistant/integration-sdk/lib/gladys-integration.js:1477:9) { status: 401 }

Regards

Tom

@Lokkye

Command retracted, it was my test computer. The production computer found the widget without any issues.

Test 1: Room 10 selected, mode set to vacuum: It starts, mops are not put down but lifted, only room 10 is vacuumed.

And here is the return:

Test 2: Mode set to auto stand, only room 10 selected and indeed it starts in the mysterious mode « Vac&Mop » and only in room 10 and completely.

So far, good work, and the naming of the different modes and variants can also be changed directly on the device, for example « 1. Auto=Vac&Mpop » instead of what is visible in the image: Saros 10 R Cleaning Mode

Well done, here is the desired log:

[2026-10-19T11:09:36.866Z] [INFO] onWidgetGet(map) <- 1YEOwIm5YPBdRuo33gGcS0
[2026-10-19T11:09:41.520Z] [INFO] poll 1YEOwIm5YPBdRuo33gGcS0: state=18 (segment_cleaning) error=0 in_cleaning=3 in_returning=0 fan=104 water=231 route=300 battery=91 clean_time=310s clean_area=4m² map_status=3 dock_error=0
[2026-10-19T11:09:41.964Z] [INFO] poll 8U043t6vRwwICihwsmLYM: state=8 (charging) error=0 in_cleaning=0 in_returning=0 fan=103 water=200 route=300 battery=100 clean_time=691s clean_area=7m² map_status=3 dock_error=0
[2026-10-19T11:09:51.878Z] [INFO] onWidgetGet(map) <- 1YEOwIm5YPBdRuo33gGcS0
[2026-10-19T11:10:06.885Z] [INFO] onWidgetGet(map) <- 1YEOwIm5YPBdRuo33gGcS0
[2026-10-19T11:10:11.381Z] [INFO] poll 1YEOwIm5YPBdRuo33gGcS0: state=18 (segment_cleaning) error=0 in_cleaning=3 in_returning=0 fan=104 water=231 route=300 battery=91 clean_time=340s clean_area=4m² map_status=3 dock_error=0
[2026-10-19T11:10:11.416Z] [INFO] [roborock:client] Opening the local (LAN) transport to 8U043t6vRwwICihwsmLYM at 192.168.0.216
[2026-10-19T11:10:11.416Z] [INFO] [roborock:client] Opening the local (LAN) transport to 8U043t6vRwwICihwsmLYM at 192.168.0.216
[2026-10-19T11:10:19.433Z] [WARN] [roborock:client] RPC get_status <- 8U043t6vRwwICihwsmLYM via local FAILED after 8017 ms: Roborock local request timed out: get_status on 8U043t6vRwwICihwsmLYM
[2026-10-19T11:10:19.433Z] [WARN] [roborock:client] Local request failed for 8U043t6vRwwICihwsmLYM, falling back to cloud: Roborock local request timed out: get_status on 8U043t6vRwwICihwsmLYM
[2026-10-19T11:10:19.433Z] [INFO] [roborock:client] Closing the local transport to 8U043t6vRwwICihwsmLYM: cloud only for the next 300 s
[2026-10-19T11:10:19.433Z] [WARN] [roborock:client] RPC get_consumable <- 8U043t6vRwwICihwsmLYM via local FAILED after 8017 ms: Roborock local transport closed
[2026-10-19T11:10:19.433Z] [WARN] [roborock:client] Local request failed for 8U043t6vRwwICihwsmLYM, falling back to cloud: Roborock local transport closed
[2026-10-19T11:10:19.768Z] [INFO] poll 8U043t6vRwwICihwsmLYM: state=8 (charging) error=0 in_cleaning=0 in_returning=0 fan=103 water=200 route=300 battery=100 clean_time=691s clean_area=7m² map_status=3 dock_error=0
[2026-10-19T11:10:21.880Z] [INFO] onWidgetGet(map) <- 1YEOwIm5YPBdRuo33gGcS0
[2026-10-19T11:10:36.887Z] [INFO] onWidgetGet(map) <- 1YEOwIm5YPBdRuo33gGcS0
[2026-10-19T11:10:41.378Z] [INFO] 1YEOwIm5YPBdRuo33gGcS0: state 18 (segment_cleaning) -> 6 (returning_home)
[2026-10-19T11:10:41.378Z] [INFO] poll 1YEOwIm5YPBdRuo33gGcS0: state=6 (returning_home) error=0 in_cleaning=0 in_returning=1 fan=104 water=231 route=300 battery=90 clean_time=356s clean_area=4m² map_status=3 dock_error=0
[2026-10-19T11:10:41.694Z] [INFO] 1YEOwIm5YPBdRuo33gGcS0: room selector reset (the room cleaning is over, state 6 (returning_home))
[2026-10-19T11:10:41.699Z] [INFO] Scene trigger state_changed fired for 1YEOwIm5YPBdRuo33gGcS0
[2026-10-19T11:10:42.074Z] [INFO] poll 8U043t6vRwwICihwsmLYM: state=8 (charging) error=0 in_cleaning=0 in_returning=0 fan=103 water=200 route=300 battery=100 clean_time=691s clean_area=7m² map_status=3 dock_error=0
[2026-10-19T11:10:51.894Z] [INFO] onWidgetGet(map) <- 1YEOwIm5YPBdRuo33gGcS0
[2026-10-19T11:11:06.899Z] [INFO] onWidgetGet(map) <- 1YEOwIm5YPBdRuo33gGcS0
[2026-10-19T11:11:11.385Z] [INFO] poll 1YEOwIm5YPBdRuo33gGcS0: state=6 (returning_home) error=0 in_cleaning=0 in_returning=1 fan=104 water=231 route=300 battery=90 clean_time=356s clean_area=4m² map_status=3 dock_error=0
[2026-10-19T11:11:11.794Z] [INFO] poll 8U043t6vRwwICihwsmLYM: state=8 (charging) error=0 in_cleaning=0 in_returning=0 fan=103 water=200 route=300 battery=100 clean_time=691s clean_area=7m² map_status=3 dock_error=0
[2026-10-19T11:11:21.894Z] [INFO] onWidgetGet(map) <- 1YEOwIm5YPBdRuo33gGcS0
[2026-10-19T11:11:36.938Z] [INFO] onWidgetGet(map) <- 1YEOwIm5YPBdRuo33gGcS0
[2026-10-19T11:11:41.380Z] [INFO] 1YEOwIm5YPBdRuo33gGcS0: state 6 (returning_home) -> 23 (washing_the_mop)
[2026-10-19T11:11:41.380Z] [INFO] poll 1YEOwIm5YPBdRuo33gGcS0: state=23 (washing_the_mop) error=0 in_cleaning=0 in_returning=0 fan=104 water=231 route=300 battery=90 clean_time=356s clean_area=4m² map_status=3 dock_error=0
[2026-10-19T11:11:41.395Z] [INFO] Scene trigger cleaning_finished fired for 1YEOwIm5YPBdRuo33gGcS0
[2026-10-19T11:11:41.395Z] [INFO] Scene trigger returned_to_dock fired for 1YEOwIm5YPBdRuo33gGcS0
[2026-10-19T11:11:41.395Z] [INFO] Scene trigger state_changed fired for 1YEOwIm5YPBdRuo33gGcS0
[2026-10-19T11:11:41.395Z] [INFO] 1YEOwIm5YPBdRuo33gGcS0: cleaning session over, map back to the normal refresh rate
[2026-10-19T11:11:41.776Z] [INFO] poll 8U043t6vRwwICihwsmLYM: state=8 (charging) error=0 in_cleaning=0 in_returning=0 fan=103 water=200 route=300 battery=100 clean_time=691s clean_area=7m² map_status=3 dock_error=0
[2026-10-19T11:12:11.383Z] [INFO] poll 1YEOwIm5YPBdRuo33gGcS0: state=23 (washing_the_mop) error=0 in_cleaning=0 in_returning=0 fan=104 water=231 route=300 battery=90 clean_time=356s clean_area=4m² map_status=3 dock_error=0
[2026-10-19T11:12:11.779Z] [INFO] poll 8U043t6vRwwICihwsmLYM: state=8 (charging) error=0 in_cleaning=0 in_returning=0 fan=103 water=200 route=300 battery=100 clean_time=691s clean_area=7m² map_status=3 dock_error=0
[2026-10-19T11:12:41.640Z] [INFO] poll 1YEOwIm5YPBdRuo33gGcS0: state=23 (washing_the_mop) error=0 in_cleaning=0 in_returning=0 fan=104 water=231 route=300 battery=90 clean_time=356s clean_area=4m² map_status=3 dock_error=0
[2026-10-19T11:12:42.010Z] [INFO] poll 8U043t6vRwwICihwsmLYM: state=8 (charging) error=0 in_cleaning=0 in_returning=0 fan=103 water=200 route=300 battery=100 clean_time=691s clean_area=7m² map_status=3 dock_error=0
[2026-10-19T11:13:11.524Z] [INFO] poll 1YEOwIm5YPBdRuo33gGcS0: state=23 (washing_the_mop) error=0 in_cleaning=0 in_returning=0 fan=104 water=231 route=300 battery=90 clean_time=356s clean_area=4m² map_status=3 dock_error=0
[2026-10-19T11:13:11.901Z] [INFO] poll 8U043t6vRwwICihwsmLYM: state=8 (charging) error=0 in_cleaning=0 in_returning=0 fan=103 water=200 route=300 battery=100 clean_time=691s clean_area=7m² map_status=3 dock_error=0
[2026-10-19T11:13:41.374Z] [INFO] onWidgetGet(map) <- 1YEOwIm5YPBdRuo33gGcS0
[2026-10-19T11:13:41.397Z] [INFO] poll 1YEOwIm5YPBdRuo33gGcS0: state=23 (washing_the_mop) error=0 in_cleaning=0 in_returning=0 fan=104 water=231 route=300 battery=90 clean_time=356s clean_area=4m² map_status=3 dock_error=0
[2026-10-19T11:13:41.865Z] [INFO] poll 8U043t6vRwwICihwsmLYM: state=8 (charging) error=0 in_cleaning=0 in_returning=0 fan=103 water=200 route=300 battery=100 clean_time=691s clean_area=7m² map_status=3 dock_error=0
[2026-10-19T11:14:11.454Z] [INFO] poll 1YEOwIm5YPBdRuo33gGcS0: state=23 (washing_the_mop) error=0 in_cleaning=0 in_returning=0 fan=104 water=231 route=300 battery=90 clean_time=356s clean_area=4m² map_status=3 dock_error=0
[2026-10-19T11:14:11.849Z] [INFO] poll 8U043t6vRwwICihwsmLYM: state=8 (charging) error=0 in_cleaning=0 in_returning=0 fan=103 water=200 route=300 battery=100 clean_time=691s clean_area=7m² map_status=3 dock_error=0
[2026-10-19T11:14:41.063Z] [INFO] [roborock:client] Opening the local (LAN) transport to 1YEOwIm5YPBdRuo33gGcS0 at 192.168.0.125
[2026-10-19T11:14:41.063Z] [INFO] [roborock:client] Opening the local (LAN) transport to 1YEOwIm5YPBdRuo33gGcS0 at 192.168.0.125
[2026-10-19T11:14:46.417Z] [INFO] poll 8U043t6vRwwICihwsmLYM: state=8 (charging) error=0 in_cleaning=0 in_returning=0 fan=103 water=200 route=300 battery=100 clean_time=691s clean_area=7m² map_status=3 dock_error=0
[2026-10-19T11:14:49.073Z] [WARN] [roborock:client] RPC get_status <- 1YEOwIm5YPBdRuo33gGcS0 via local FAILED after 8010 ms: Roborock local request timed out: get_status on 1YEOwIm5YPBdRuo33gGcS0
[2026-10-19T11:14:49.073Z] [WARN] [roborock:client] Local request failed for 1YEOwIm5YPBdRuo33gGcS0
```, falling back to cloud: Roborock local request timed out: get_status on 1YEOwIm5YPBdRuo33gGcS0
[2026-10-19T11:14:49.073Z] [INFO] [roborock:client] Closing the local transport to 1YEOwIm5YPBdRuo33gGcS0: cloud only for the next 300 s
[2026-10-19T11:14:49.073Z] [WARN] [roborock:client] RPC get_consumable <- 1YEOwIm5YPBdRuo33gGcS0 via local FAILED after 8010 ms: Roborock local transport closed
[2026-10-19T11:14:49.073Z] [WARN] [roborock:client] Local request failed for 1YEOwIm5YPBdRuo33gGcS0, falling back to cloud: Roborock local transport closed
[2026-10-19T11:14:49.403Z] [INFO] poll 1YEOwIm5YPBdRuo33gGcS0: state=23 (washing_the_mop) error=0 in_cleaning=0 in_returning=0 fan=104 water=231 route=300 battery=90 clean_time=356s clean_area=4m² map_status=3 dock_error=0
[2026-10-19T11:15:11.391Z] [INFO] 1YEOwIm5YPBdRuo33gGcS0: state 23 (washing_the_mop) -> 8 (charging)
[2026-10-19T11:15:11.391Z] [INFO] poll 1YEOwIm5YPBdRuo33gGcS0: state=8 (charging) error=0 in_cleaning=0 in_returning=0 fan=104 water=231 route=300 battery=90 clean_time=356s clean_area=4m² map_status=3 dock_error=0
[2026-10-19T11:15:11.397Z] [INFO] Scene trigger state_changed fired for 1YEOwIm5YPBdRuo33gGcS0
[2026-10-19T11:15:11.770Z] [INFO] poll 8U043t6vRwwICihwsmLYM: state=8 (charging) error=0 in_cleaning=0 in_returning=0 fan=103 water=200 route=300 battery=100 clean_time=691s clean_area=7m² map_status=3 dock_error=0

@ruegerth thanks for the logs, they helped me find something unexpected.

The code is accepted (the connection succeeds), it’s the next request that Roborock refuses (HTTP 401). This request is signed with your machine’s time, and Roborock compares it to its own. However, your logs are dated 11:02 UTC while your message was posted at 10:41 UTC: the clock of the machine running Gladys is about 20 minutes ahead. This is very likely the cause of the refusal, and also the reason why each new attempt consumed a code for nothing.

The 2.8.0 that I just published:

  • signs requests with Roborock’s time instead of the machine’s time, and writes the measured difference in the logs;
  • keeps the session when the connection succeeds but the loading of the robots fails, so no more wasted codes: a simple “Scan” reloads the robots.

What I propose to you:

  1. Check the time of your machine and enable synchronization (NTP) if it is not already. Even with 2.8.0, a wrong clock can cause other issues.
  2. Update the integration to 2.8.0, request a new code and link the account.
  3. If it works, retest room 10 in “Clean” mode then in “Auto”, and send me the logs as planned.

If the connection still fails, send me the new log lines: they now contain the measured clock difference, which will help determine the issue.


@stefanbauer it’s done in the 2.8.0: in the widget settings, three new options allow you to show or hide the battery tile, the surface tile, and the map (all enabled by default). When only one tile remains, it takes up the full width, and if you hide the map and the surface, the integration doesn’t even ask the robot for the map anymore.

For the visual issue with the surface, can you tell me what you expected instead? In your screenshot I see 50 m² and the gauge at two-thirds, which corresponds to a house of approximately 75 m² mapped. If something else is wrong, a screenshot with an explanation will help me.

@ruegerth my apologies, I responded earlier without seeing your previous message, which had already resolved everything: the connection issue did indeed come from your test computer, and it worked fine on the production machine. So forget my instructions about the clock for production.

Above all, thank you for the two tests and the logs. Both cases behave exactly as expected: “Aspiration” lifts the mops and vacuums the entire room 10, “Auto” vacuums and washes the entire room 10. The midway stop in version 2.7.0 no longer appears in your logs. If it happens again, the logs would show it now.

Your logs also showed me a small flaw: every time the integration lifted, it opened the local connection to your S7 twice. This is fixed in 2.8.1, now available. I also see that your S7 does not respond locally (it switches to the cloud after 8 seconds); I will check if the S7 Max Ultra needs a special handshake.

For the mode name, you are right, and since 2.7.2, newly discovered cleaning robots have a feature named “Cleaning type (vacuum / mop)”. For your already created robot, renaming it in Gladys as you suggest is the simplest solution.