# External Integration - Roborock

**URL:** <https://community.gladysassistant.com/t/integration-externe-roborock/10416>\
**Category:** Développement\
**Tags:** integration-externe\
**Created:** [July 31, 2026, 2:24pm UTC](https://community.gladysassistant.com/t/integration-externe-roborock/10416 "2026-07-31T14:24:13Z")\
**Posts on this page:** 20\
**Page:** 2

<div class="post-metadata">

**Author:** ![spenceur](https://gladys-assistant-community.b-cdn.net/user_avatar/community.gladysassistant.com/spenceur/32/1961_2.png) [@spenceur](https://community.gladysassistant.com/u/spenceur)\
**Post date:** [October 5, 2026, 4:14pm UTC](https://community.gladysassistant.com/t/integration-externe-roborock/10416/21 "2026-10-05T16:14:19Z")

</div>

Hello @Lokkye, I made a PR to add a widget and actions and triggers.

> <https://github.com/callemand/gladys-roborock/pull/6>
>
> \## Résumé
> 
> Deux ajouts pour l'intégration Roborock :
> 
> 1. \*\*Carte de l'aspirateur… en widget de dashboard\*\* (SDK \`0.14\`, widgets Gladys \`5.1\`).
> 2. \*\*Déclencheurs et actions de scène\*\* (l'aspirateur dans l'éditeur de scènes).
> 
> \## 1. Carte en widget
> 
> \- \*\*Récupération\*\* : \`get\_map\_v1\` (frame protocole \`301\`, déchiffrement AES‑128‑CBC + gunzip), transport local-first avec repli cloud.
> \- \*\*Parseur RRMap\*\* : format binaire → objet structuré (segments, robot, base, trajet, zones interdites, murs virtuels…), réconcilié avec \`get\_room\_mapping\` pour les \*\*noms de pièces\*\*.
> \- \*\*Rendu PNG maison\*\* (via \`node:zlib\`, sans dépendance) proche de l'app : pièces colorées, murs fins, zones interdites, murs virtuels, base/robot, \*\*fond transparent\*\* (s'adapte au thème clair/sombre).
> \- \*\*Widget « Aspirateur »\*\* : tuiles batterie / surface, carte, bloc état (état, dernier nettoyage, durée, \*\*% de chaque consommable\*\*) et \*\*4 boutons\*\* — Démarrer + Retour base fixes, et \*\*2 boutons configurables\*\* via les réglages.
> \- \*\*Timestamp de début du dernier nettoyage\*\* (\`get\_clean\_summary\`, mis en cache).
> 
> \## 2. Scènes
> 
> Déclaré dans le manifest (\`scene\_triggers\` / \`scene\_actions\`), branché sur les données déjà pollées et les commandes RPC existantes.
> 
> \*\*Déclencheurs\*\* (émis sur transition via \`publishSceneEvent\`) :
> \`cleaning\_started\`, \`cleaning\_finished\` (durée, surface), \`returned\_to\_dock\`, \`battery\_low\` (≤ 20 %), \`charging\_complete\`, \`robot\_error\` (code + libellé), \`consumable\_worn\` (≤ 10 %, par consommable), \`state\_changed\`.
> 
> \*\*Actions\*\* (\`onSceneAction\`, chacune avec un champ \`vacuum\`) :
> \`start\_cleaning\`, \`pause\_cleaning\`, \`stop\_cleaning\`, \`return\_to\_dock\`, \`clean\_rooms\` (noms de pièces → \`app\_segment\_clean\`), \`set\_fan\_power\` (silencieux/équilibré/turbo/max), \`run\_routine\` (nom de routine → \`executeRoutine\`).
> 
> Les transitions sont détectées via un instantané par robot mis en cache entre deux polls (le premier poll ne fait qu'amorcer le cache). Les seuils sont gérés côté intégration (les filtres de scène sont à égalité seulement) et le niveau/pourcentage est exposé en variable de scène.
> 
> \## Points d'attention
> 
> \- ⚠️ \*\*\`gladys\_version\` passe à \`\>=5.1.0\`\*\* : les widgets de dashboard nécessitent Gladys 5.1.0 (c'était \`\>=4.86.0\` sur \`main\`).
> \- \*\*Bump de version patch\*\* : \`2.3.0\` → \`2.3.1\`.
> \- \*\*Transport local QV35A\*\* : silencieux en TCP local quand il est à la base (en charge) → repli automatique sur le cloud, documenté.
> 
> \## Tests
> 
> \- \`114\` tests passent (\`node --test\`), \`eslint\` et \`prettier --check\` clean.
> 
> \## Suite possible
> 
> Demande de fonctionnalité pour une \*\*carte interactive\*\* (sélection de pièces au clic → nettoyage ciblé), qui nécessiterait un composant frontend côté cœur : https://community.gladysassistant.com/t/composant-carte-interactive-zones-cliquables-pour-les-widgets-dintegration-externe/10959
> 
> 🤖 Generated with \[Claude Code\](https://claude.com/claude-code)

I also made a request to one day select the rooms to clean on the map and thus evolve this widget 🙂

> [@Interactive map component (clickable zones) for external integration widgets](https://community.gladysassistant.com/t/interactive-map-component-clickable-zones-for-external-integration-widgets/10959?u=spenceur):
>
> Hello waving_hand I’m developing a widget for the Roborock external integration that displays the vacuum cleaner map (via onWidgetGetImage). The rendering works very well, but I’m hitting a limit of the widget vocabulary: there is no way to make the map interactive. Today, in a widget, we only have static components (image, value, gauge, status, chart, card-list) + button (limited to 4). The concrete limits: • the map is a static image: impossible to detect a click on a room; • no selectio…

---

<div class="post-metadata">

**Author:** ![Chris75](https://gladys-assistant-community.b-cdn.net/letter_avatar_proxy/v4/letter/c/6a8cbe/32.png) [@Chris75](https://community.gladysassistant.com/u/Chris75)\
**Post date:** [October 5, 2026, 5:40pm UTC](https://community.gladysassistant.com/t/integration-externe-roborock/10416/22 "2026-10-05T17:40:21Z")

</div>

I don’t know if you’ve seen what has been done for the external integrations of the Dreame robot ([Demande d'intégration externe pour robot aspirateur/laveur DREAME - #39 par Chris75](https://community.gladysassistant.com/t/demande-dintegration-externe-pour-robot-aspirateur-laveur-dreame/10910/39)) and the Mammotion robot integration ([Intégration externe - Mammotion - #41 par prohand](https://community.gladysassistant.com/t/integration-externe-mammotion/10915/41))  
After testing them extensively, I am really very satisfied with the result because now I can do without the official apps of the brand for all essential functions and settings  
And it was developed by @guim31 @prohand in 1 week 💪

---

<div class="post-metadata">

**Author:** ![guim31](https://gladys-assistant-community.b-cdn.net/user_avatar/community.gladysassistant.com/guim31/32/4840_2.png) [@guim31](https://community.gladysassistant.com/u/guim31)\
**Post date:** [October 5, 2026, 7:25pm UTC](https://community.gladysassistant.com/t/integration-externe-roborock/10416/23 "2026-10-05T19:25:59Z")

</div>

Yes but that’s because we’re too strong 😎

Haha (to prompt Claude!)

---

<div class="post-metadata">

**Author:** ![Lokkye](https://gladys-assistant-community.b-cdn.net/user_avatar/community.gladysassistant.com/lokkye/32/5881_2.png) [@Lokkye](https://community.gladysassistant.com/u/Lokkye)\
**Post date:** [October 6, 2026, 12:20pm UTC](https://community.gladysassistant.com/t/integration-externe-roborock/10416/24 "2026-10-06T12:20:50Z")

</div>

Thanks so much for your PR, I’m currently reviewing it and giving you some feedback 🙂

---

<div class="post-metadata">

**Author:** ![spenceur](https://gladys-assistant-community.b-cdn.net/user_avatar/community.gladysassistant.com/spenceur/32/1961_2.png) [@spenceur](https://community.gladysassistant.com/u/spenceur)\
**Post date:** [October 6, 2026, 12:53pm UTC](https://community.gladysassistant.com/t/integration-externe-roborock/10416/25 "2026-10-06T12:53:40Z")

</div>

return processed 🙂

---

<div class="post-metadata">

**Author:** ![Lokkye](https://gladys-assistant-community.b-cdn.net/user_avatar/community.gladysassistant.com/lokkye/32/5881_2.png) [@Lokkye](https://community.gladysassistant.com/u/Lokkye)\
**Post date:** [October 6, 2026, 1:09pm UTC](https://community.gladysassistant.com/t/integration-externe-roborock/10416/26 "2026-10-06T13:09:21Z")

</div>

Code merged 🙂

---

<div class="post-metadata">

**Author:** ![spenceur](https://gladys-assistant-community.b-cdn.net/user_avatar/community.gladysassistant.com/spenceur/32/1961_2.png) [@spenceur](https://community.gladysassistant.com/u/spenceur)\
**Post date:** [October 6, 2026, 1:14pm UTC](https://community.gladysassistant.com/t/integration-externe-roborock/10416/27 "2026-10-06T13:14:57Z")

</div>

you noticed there were issues on the repo:

> **[Issues · callemand/gladys-roborock](https://github.com/callemand/gladys-roborock/issues)**
>
> Roborock robot vacuum integration for Gladys Assistant (Xiaomi Home account, local miIO with cloud fallback) - Issues · callemand/gladys-roborock

---

<div class="post-metadata">

**Author:** ![Lokkye](https://gladys-assistant-community.b-cdn.net/user_avatar/community.gladysassistant.com/lokkye/32/5881_2.png) [@Lokkye](https://community.gladysassistant.com/u/Lokkye)\
**Post date:** [October 6, 2026, 2:00pm UTC](https://community.gladysassistant.com/t/integration-externe-roborock/10416/28 "2026-10-06T14:00:06Z")

</div>

No, I don’t know why I didn’t receive the emails ☹, «&nbsp;I&nbsp;» am currently fixing it

---

<div class="post-metadata">

**Author:** ![Lokkye](https://gladys-assistant-community.b-cdn.net/user_avatar/community.gladysassistant.com/lokkye/32/5881_2.png) [@Lokkye](https://community.gladysassistant.com/u/Lokkye)\
**Post date:** [October 6, 2026, 2:07pm UTC](https://community.gladysassistant.com/t/integration-externe-roborock/10416/29 "2026-10-06T14:07:12Z")

</div>

Version 2.5.0 released with code by @spenceur and 2 fixes 🚀

---

<div class="post-metadata">

**Author:** ![guim31](https://gladys-assistant-community.b-cdn.net/user_avatar/community.gladysassistant.com/guim31/32/4840_2.png) [@guim31](https://community.gladysassistant.com/u/guim31)\
**Post date:** [October 6, 2026, 2:52pm UTC](https://community.gladysassistant.com/t/integration-externe-roborock/10416/30 "2026-10-06T14:52:44Z")

</div>

Cool new widget!!

 ![1000039757](https://gladys-assistant-community.b-cdn.net/uploads/default/original/3X/0/1/013e589e7a5e68264cc3d1d7d7e0af6f4f27fb1e.jpeg)

---

<div class="post-metadata">

**Author:** ![spenceur](https://gladys-assistant-community.b-cdn.net/user_avatar/community.gladysassistant.com/spenceur/32/1961_2.png) [@spenceur](https://community.gladysassistant.com/u/spenceur)\
**Post date:** [October 6, 2026, 5:35pm UTC](https://community.gladysassistant.com/t/integration-externe-roborock/10416/31 "2026-10-06T17:35:48Z")

</div>

@Lokkye  
I made a correction to the image jump that wasn’t very nice and added a condition for the scenes

> <https://github.com/callemand/gladys-roborock/pull/9>
>
> \## Résumé
> 
> Rend le \*\*widget carte\*\* stable au rafraîchissement et \*\*quasi temps …réel pendant un nettoyage\*\*, sans changer le vocabulaire du widget (toujours un PNG rendu côté serveur).
> 
> Avant : à chaque rafraîchissement la carte pouvait \*\*« sauter »\*\* (se redimensionner / clignoter), et elle n'avançait qu'au \`ttl\` du contenu.
> 
> \## Ce que ça corrige
> 
> \### A. Rendu à cadre fixe (\`src/roborock/mapRender.js\`)
> La taille de sortie est désormais dérivée du \*\*crop stable\*\* (les pièces nommées) via une nouvelle option \`targetLongestPx\`, au lieu du poids en octets. Le même logement rend \*\*toujours aux mêmes dimensions\*\* → plus de reflow/rescale quand seuls le robot et le tracé bougent. Le garde-fou octets reste (réduction déterministe de la cible).
> 
> \### B. Clé d'image = hash du rendu (\`src/devices/mapWidget.js\`, \`index.js\`)
> La clé d'image est maintenant un \*\*hash des octets PNG\*\* (plus \`mapSequence\`). Le cœur ne \*\*remplace l'\`\<img\>\` que si l'image a réellement changé\*\* → plus de flash quand rien n'a bougé. \`MAP\_RENDER\_VERSION\` 7 → 8 pour invalider l'ancien cache. Le garde-fou 64 caractères de la clé est conservé.
> 
> \### C. Quasi temps réel pendant le nettoyage (\`index.js\`)
> \- Suivi des robots ayant une \*\*session de nettoyage active\*\*.
> \- Pendant le nettoyage : cache carte \*\*~8 s\*\* (au lieu de 60 s) + \*\*nudge \`requestWidgetRefresh\` toutes les ~15 s\*\* (plafond cœur 1/10 s, no-op si aucun widget ouvert).
> \- Au repos : cache 60 s, pas de nudge.
> 
> → La carte avance « par pas » de ~15 s pendant le ménage, puis se met en veille à la base.
> 
> \## Limite connue
> 
> Le léger flash de chargement quand l'image change \*\*vraiment\*\* (pendant un nettoyage) reste géré par le frontend du cœur — une intégration externe ne peut pas faire de cross-fade. A + B le réduisent au strict minimum (même taille, swap uniquement sur vrai changement).
> 
> \## D. Condition de scène « Nettoyé aujourd'hui »
> 
> Nouvelle feature \*\*read-only \`cleaned-today\`\*\* (0/1, 1 = l'aspirateur a tourné aujourd'hui), dérivée du dernier début de nettoyage. Elle permet une \*\*condition de scène\*\* « est-ce que l'aspirateur a tourné aujourd'hui ? » (ex. ne lancer un nettoyage que s'il n'a pas déjà tourné). Toujours publiée (même 0) pour que les deux branches de la condition fonctionnent. (\`src/devices/lastClean.js\`, \`src/devices/convertDevice.js\`, \`index.js\`.)
> 
> \## Tests
> 
> \- \`128\` tests passent (\`node --test\`), \`eslint\` OK.
> \- Nouveaux tests : dimensions de sortie stables quand seul le robot bouge (A) ; round-trip de la clé avec signature hash (B) ; \`isCleanedToday\` / état 0-1 (D).
> 
> Basé sur \`main\` (2.5.0) → \*\*2.5.1\*\* (patch).
> 
> 🤖 Generated with \[Claude Code\](https://claude.com/claude-code)

Sorry for the fix at this hour 🙂

---

<div class="post-metadata">

**Author:** ![Philippe\_B](https://gladys-assistant-community.b-cdn.net/user_avatar/community.gladysassistant.com/philippe_b/32/21650_2.png) [@Philippe\_B](https://community.gladysassistant.com/u/Philippe_B)\
**Post date:** [October 6, 2026, 8:49pm UTC](https://community.gladysassistant.com/t/integration-externe-roborock/10416/32 "2026-10-06T20:49:51Z")

</div>

hello I don’t see my card? Do I need to do something else?

 ![image](https://gladys-assistant-community.b-cdn.net/uploads/default/original/3X/1/f/1ff2f87f32faed49f7ceadb3f130a1106700921f.jpeg)

---

<div class="post-metadata">

**Author:** ![Lokkye](https://gladys-assistant-community.b-cdn.net/user_avatar/community.gladysassistant.com/lokkye/32/5881_2.png) [@Lokkye](https://community.gladysassistant.com/u/Lokkye)\
**Post date:** [October 7, 2026, 5:39am UTC](https://community.gladysassistant.com/t/integration-externe-roborock/10416/33 "2026-10-07T05:39:13Z")

</div>

@spenceur Sorry for the reaction time but a «&nbsp;small&nbsp;» headache kept me company all evening. I made a small change in your PR, we should avoid modifying the version number in the PRs as it’s another process that does it when building the Docker image.

It’s published under version 2.5.1

---

<div class="post-metadata">

**Author:** ![ruegerth](https://gladys-assistant-community.b-cdn.net/letter_avatar_proxy/v4/letter/r/dbc845/32.png) [@ruegerth](https://community.gladysassistant.com/u/ruegerth)\
**Post date:** [October 7, 2026, 2:53pm UTC](https://community.gladysassistant.com/t/integration-externe-roborock/10416/34 "2026-10-07T14:53:51Z")

</div>

Hi, yes great widget for Roborock vacuums, it works perfectly for my Saros 10 R and S7 Max Ultra:

 ![roborock](https://gladys-assistant-community.b-cdn.net/uploads/default/original/3X/5/c/5cdd6b7dcf8d777fde241c1d4705dd12d55169d4.png)

It even shows the last activity… what they don’t store ☹

The widget is now only missing the room selection…

---

<div class="post-metadata">

**Author:** ![spenceur](https://gladys-assistant-community.b-cdn.net/user_avatar/community.gladysassistant.com/spenceur/32/1961_2.png) [@spenceur](https://community.gladysassistant.com/u/spenceur)\
**Post date:** [October 7, 2026, 3:19pm UTC](https://community.gladysassistant.com/t/integration-externe-roborock/10416/35 "2026-10-07T15:19:20Z")

</div>

The request is here

> [@Interactive map component (clickable zones) for external integration widgets](https://community.gladysassistant.com/t/composant-carte-interactive-zones-cliquables-pour-les-widgets-dintegration-externe/10959?u=spenceur):
>
> Hello waving_hand I’m developing a widget for the Roborock external integration that displays the vacuum cleaner map (via onWidgetGetImage). The rendering works very well, but I’m hitting a limit of the widget vocabulary: there is no way to make the map interactive. Today, in a widget, we only have static components (image, value, gauge, status, chart, card-list) + button (limited to 4). The concrete limits: • the map is a static image: impossible to detect a click on a room; • no selectio…

Your vote

---

<div class="post-metadata">

**Author:** ![ruegerth](https://gladys-assistant-community.b-cdn.net/letter_avatar_proxy/v4/letter/r/dbc845/32.png) [@ruegerth](https://community.gladysassistant.com/u/ruegerth)\
**Post date:** [October 9, 2026, 12:02pm UTC](https://community.gladysassistant.com/t/integration-externe-roborock/10416/36 "2026-10-09T12:02:06Z")

</div>

Language diversity… I’m even learning French:

 ![saros10R](https://gladys-assistant-community.b-cdn.net/uploads/default/original/3X/5/e/5e87082644ca635c40f2e4f22703dc5ce19b81f0.png)

😉 😂

---

<div class="post-metadata">

**Author:** ![ruegerth](https://gladys-assistant-community.b-cdn.net/letter_avatar_proxy/v4/letter/r/dbc845/32.png) [@ruegerth](https://community.gladysassistant.com/u/ruegerth)\
**Post date:** [October 11, 2026, 7:47am UTC](https://community.gladysassistant.com/t/integration-externe-roborock/10416/37 "2026-10-11T07:47:35Z")

</div>

Sorry, I have to point out my message:

> <https://github.com/callemand/gladys-roborock/issues/13>
>
> Saros 10R:
> ( Main options: Vacuum, then mop / Vac & Mop / Mop / Vacuum )
> 
> Integr…ation:
> ( Car / Fast / Quiet / Low-noise / Deep cleaning / Vacuuming / Mopping )
> 
> \<img width="199" height="354" alt="Image" src="https://github.com/user-attachments/assets/78d91998-0c85-4eec-8f77-945a30fad012" /\>
> 
> Test 1:
> Cleaning - Quick - Room 13
> 
> \<img width="203" height="354" alt="Image" src="https://github.com/user-attachments/assets/f1fc5b0f-2439-421e-9908-d91d8379fd5c" /\>
> 
> Result:
> Vac&Mop - Room 12:
> 
> \<img width="720" height="1640" alt="Image" src="https://github.com/user-attachments/assets/fd07d8e2-d713-41b7-938b-2abdd68af299" /\>
> 
> Test 2:
> Cleaning - Quiet - Room 11
> 
> \<img width="197" height="348" alt="Image" src="https://github.com/user-attachments/assets/59fedb8c-6e83-4aae-a029-40ae2e81fc73" /\>
> 
> Result:
> Vac&Mop - Room 11
> 
> \<img width="720" height="1640" alt="Image" src="https://github.com/user-attachments/assets/d2459529-c4bd-43e4-bf13-c15499510f5f" /\>
> 
> Test 4:
> Cleaning - Vacuuming - Room 10
> 
> \<img width="196" height="328" alt="Image" src="https://github.com/user-attachments/assets/3e104527-0077-4631-a790-dd67705074a8" /\>
> 
> Result:
> Vac&Mop - Room 11
> 
> \<img width="720" height="1640" alt="Image" src="https://github.com/user-attachments/assets/b473fc66-a7d7-467f-8427-2a49fd9b0d40" /\>
> 
> Translation is inconsistent: German - French - English:
> 
> \<img width="194" height="346" alt="Image" src="https://github.com/user-attachments/assets/72a8d1d6-30b9-47e8-844c-1381ba5f20b7" /\>

It seems that with some newer Roborock models, the assignments between functions and between rooms may be different…

---

<div class="post-metadata">

**Author:** ![ruegerth](https://gladys-assistant-community.b-cdn.net/letter_avatar_proxy/v4/letter/r/dbc845/32.png) [@ruegerth](https://community.gladysassistant.com/u/ruegerth)\
**Post date:** [October 11, 2026, 8:15am UTC](https://community.gladysassistant.com/t/integration-externe-roborock/10416/38 "2026-10-11T08:15:07Z")

</div>

I really don’t want to stop, slow down, or otherwise interrupt the current momentum of development for integrations.

But the fundamental development of Claude without having the actual objects in front of you or corresponding access to test devices seems problematic.

Here’s the example of Roborock:

– Translation mess  
– Room assignment is rather left to chance. Sometimes the integration takes the last setting, sometimes a completely different room, and sometimes it actually works.  
– Subfunctions, especially on newer models, are not adjustable. Here’s an S7 Max Ultra with its subfunctions:

Vacuum

 ![saugen](https://gladys-assistant-community.b-cdn.net/uploads/default/original/3X/1/6/16057fcc1f7b770d4af67a3133abe80dbe316dd8.png)

The integration does not offer the ability to assign suction power, number of cleanings, or distance to vacuuming.

Vac&Mop

 ![vac_mop](https://gladys-assistant-community.b-cdn.net/uploads/default/original/3X/f/7/f760874fd8d800caaeee03fc397add5b6bd17f17.png)

Here too, the subfunctions are not offered, so suction power, cleaning intensity, number of cleanings, or distance

Mopping

 ![wischen](https://gladys-assistant-community.b-cdn.net/uploads/default/original/3X/c/3/c3114eb998ff6ea37a823e19cb6d83599e48d561.png)

– The integration does not offer the ability to combine rooms, so I cannot say: Please vacuum room 10 and 12. I am forced to first vacuum room 10 and then go through the process again with room 12.

Final result:  
The integration seems to have been developed very quickly without sufficient testing. The widget also does not react stably. Sometimes the widget works, sometimes it doesn’t. Inconsistent state.

Again, I apologize, but the integration should not be published in its current state of development.

---

<div class="post-metadata">

**Author:** ![guim31](https://gladys-assistant-community.b-cdn.net/user_avatar/community.gladysassistant.com/guim31/32/4840_2.png) [@guim31](https://community.gladysassistant.com/u/guim31)\
**Post date:** [October 11, 2026, 8:31am UTC](https://community.gladysassistant.com/t/integration-externe-roborock/10416/39 "2026-10-11T08:31:29Z")

</div>

Even if I partly share your feelings, I don’t think the conclusion you draw is the right one.

Indeed, I have a Roborock S7 MaxV, so I can test and see that there are gaps.

The issue is rather that we need to find an effective balance between two situations:

- either we wait for a developer to own the hardware and publish an integration (knowing that, in addition, they can’t own all the hardware from a single brand/protocol)
- or we dive in and hope for user feedback (who don’t need to be developers).

I genuinely think there’s no debate.  
After that, we could always determine whether we consider an integration as «&nbsp;beta&nbsp;» needing testers or «&nbsp;stable&nbsp;»… But even then, the line is blurry.

This is just my opinion, of course, and I especially find that your feedback is precious to quickly evolve the integration! 👍

---

<div class="post-metadata">

**Author:** ![ruegerth](https://gladys-assistant-community.b-cdn.net/letter_avatar_proxy/v4/letter/r/dbc845/32.png) [@ruegerth](https://community.gladysassistant.com/u/ruegerth)\
**Post date:** [October 11, 2026, 8:45am UTC](https://community.gladysassistant.com/t/integration-externe-roborock/10416/40 "2026-10-11T08:45:03Z")

</div>

@guim31: Don’t get me wrong, I’m the last person who wants to influence anyone here or is allowed to.

My reference to the test devices is based on the developer’s own notes:

- The **device layer** (MQTT and local TCP transports, RPC commands) is covered by unit and end-to-end tests against fakes, but has **never been exercised against a real robot on a Roborock account**. The authentication chain, on the other hand, is verified end to end against the live cloud: region discovery, `sendEmailCode`, `loginWithCode`, the home id, and the Hawk-signed home data.

Found:  
[GitHub - callemand/gladys-roborock: Roborock robot vacuum integration for Gladys Assistant (Xiaomi Home account, local miIO with cloud fallback) · GitHub](https://github.com/callemand/gladys-roborock)

With my own vacuums, I only noticed big differences to the older models, and this combination of the developer’s own notes and my tests led to my post.

If I’ve now stepped on someone’s «&nbsp;toes&nbsp;» (German idiom 😉 ), then my apologies.

Regards  
Tom

[Previous page](https://community.gladysassistant.com/t/integration-externe-roborock/10416.md?page=1)

[Next page](https://community.gladysassistant.com/t/integration-externe-roborock/10416.md?page=3)
