[FEATURE] Unterstützung für neue API-Struktur / Roborock Q10 Series

[mrMuppet]

Type of Request

New Device Support

Device Model

roborock.vacuum.ss09

Device Firmware Version

3.10.92

Is your feature request related to a problem?

beim Debuggen des Adapters mit einem neuen Roborock Q10 ist mir aufgefallen, warum das Gerät vom Adapter komplett ignoriert wird (das Log zeigt nach erfolgreichem Login nur localDevices: {} und es wird auch kein unknown model Fehler ausgegeben).

Die Ursache:
Roborock hat bei den neuesten Modellen offenbar die Datenstruktur in der Cloud umgebaut:

Das Array "devices": [] ist jetzt komplett leer. Da der Adapter aktuell durch dieses Array iteriert, findet er logischerweise keinen Sauger.

Das neue Gerät liegt stattdessen in einem neuen Array namens "products": [...].

Die Steuerung der neuen Modelle läuft anscheinend über ein komplett neues RPC-Schema. Die ganzen Datenpunkte und Befehle (wie fan_power, water_box_mode, start_clean_task) sind jetzt direkt im schema-Array als Liste mit eigenen IDs (101, 102, 123 etc.) definiert.

Gerätedetails:
Name: Roborock Q10 Series
Model-ID: roborock.vacuum.ss09

HomeData JSON:
Hier ist mein anonymisierter HomeData String, den ich direkt aus der API-Antwort (getUserData / HTTP 200) extrahiert habe. Man sieht sehr gut die leere devices-Liste und die neue products-Struktur:

JSON
{"id":1234567,"name":"My Home","lon":null,"lat":null,"geoName":null,"products":[{"id":"XXXXXXXXXXXXXXXXXXXXXX","name":"Roborock Q10 Series","model":"roborock.vacuum.ss09","iconUrl":null,"attribute":null,"capability":0,"category":"robot.vacuum.cleaner","schema":[{"id":101,"name":"RPC Request","code":"rpc_request","mode":"rw","type":"RAW","property":"null"},{"id":102,"name":"RPC Response","code":"rpc_response","mode":"rw","type":"RAW","property":"null"},{"id":120,"name":"错误代码","code":"error_code","mode":"ro","type":"ENUM","property":"null"},{"id":121,"name":"设备状态","code":"state","mode":"ro","type":"VALUE","property":"null"},{"id":122,"name":"设备电量","code":"battery","mode":"ro","type":"ENUM","property":"null"},{"id":123,"name":"吸力档位","code":"fan_power","mode":"rw","type":"ENUM","property":"null"},{"id":124,"name":"拖地档位","code":"water_box_mode","mode":"rw","type":"RAW","property":"null"},{"id":125,"name":"主刷寿命","code":"main_brush_life","mode":"ro","type":"ENUM","property":"null"},{"id":126,"name":"边刷寿命","code":"side_brush_life","mode":"ro","type":"ENUM","property":"null"},{"id":127,"name":"滤网寿命","code":"filter_life","mode":"ro","type":"ENUM","property":"null"},{"id":135,"name":"离线原因","code":"offline_status","mode":"ro","type":"ENUM","property":"null"},{"id":136,"name":"清洁次数","code":"clean_times","mode":"rw","type":"ENUM","property":"null"},{"id":137,"name":"扫拖模式","code":"cleaning_preference","mode":"rw","type":"ENUM","property":"null"},{"id":138,"name":"清洁任务类型","code":"clean_task_type","mode":"ro","type":"ENUM","property":"null"},{"id":139,"name":"返回基站类型","code":"back_type","mode":"ro","type":"ENUM","property":"null"},{"id":140,"name":"基站任务类型","code":"dock_task_type","mode":"ro","type":"ENUM","property":"null"},{"id":141,"name":"清洁进度","code":"cleaning_progress","mode":"ro","type":"ENUM","property":"null"},{"id":142,"name":"窜货信息","code":"fc_state","mode":"ro","type":"RAW","property":"null"},{"id":201,"name":"启动清洁任务","code":"start_clean_task","mode":"wo","type":"ENUM","property":"null"},{"id":202,"name":"返回基站任务","code":"start_back_dock_task","mode":"wo","type":"ENUM","property":"null"},{"id":203,"name":"启动基站任务","code":"start_dock_task","mode":"wo","type":"ENUM","property":"null"},{"id":204,"name":"暂停任务","code":"pause","mode":"wo","type":"RAW","property":"null"},{"id":205,"name":"继续任务","code":"resume","mode":"wo","type":"RAW","property":"null"},{"id":206,"name":"结束任务","code":"stop","mode":"wo","type":"RAW","property":"null"},{"id":207,"name":"用户改善计划","code":"ceip","mode":"rw","type":"ENUM","property":"{\"range\": [\"0,1\"]}"}]}],"devices":[],"receivedDevices":[],"rooms":[]}
Wenn ich die neue Struktur später mit meinem Gerät im ioBroker testen soll, gebt mir gerne Bescheid.

Describe the solution you'd like

Der Adapter müsste erweitert werden, um die neue products-Struktur und das dazugehörige RPC-Schema von Roborock auszulesen.

1. Das Array "devices": [] ist bei den neuen Modellen komplett leer.
2. Das neue Gerät liegt stattdessen in einem Array namens "products": [...].
3. Die Steuerung läuft über ein neues RPC-Schema (Datenpunkte wie fan_power, start_clean_task etc. sind im schema-Array mit IDs definiert).

Describe alternatives you've considered

No response

Additional context / Screenshots / Logs

No response

Checklist

• I have searched for existing feature requests (issues) to avoid duplicates.
• I agree to provide feedback or test the feature if implemented.

[copystring]

Hallo, welche Branch oder welches Release hast du dafür verwendet? Das ist in der main-Branch schon eingebaut, hat aber noch keinen Release.

[mrMuppet]

Hallo,

danke für die super schnelle Rückmeldung!

Ich hatte Version 0.6.19 installiert.

Da mein neuer Roborock-Account zwingend 2FA verlangte (Code 2031) und der Adapter in der Version noch mit einem TypeError (Cannot read properties of null (reading 'token') in der http_api.js) abgestürzt ist, hatte ich mir den auskommentierten 2FA-Flow (sendEmailCode / loginWithCode) kurzzeitig lokal per Hand in die kompilierte JS-Datei gepatcht, um den Absturz abzufangen und mich einzuloggen. Dabei ist mir dann in meiner lokalen ioBroker-Instanz das leere devices-Array im Log aufgefallen.

Wenn du die products-Struktur und das neue RPC-Schema im main-Branch schon eingebaut hast, teste ich das gerne mit meinem Q10!

Reicht es, wenn ich den Adapter jetzt einfach noch einmal frisch über iobroker installiere, um den neuesten Stand zu bekommen, oder soll ich einen bestimmten Branch / Commit ziehen?

Danke für deine tolle Arbeit!

[copystring]

Ja, das Meiste sollte schon mit der main-Branch laufen. Du kannst die ja mal über diesen Link https://github.com/copystring/ioBroker.roborock in ioBroker installieren.

[leinadloisl-byte]

Hello everyone,

I would like to relate my issue with the Roborock Saros Z70 (model roborock.vacuum.a179) to the already reported problem concerning the Roborock Q10 (roborock.vacuum.ss09), because both devices seem to be affected by the same underlying API changes on Roborock’s side – although the symptoms differ slightly.

In the Q10 issue, it was described that the array devices[] is completely empty, which causes the adapter to ignore the device entirely. In my case with the Saros Z70, devices[] is actually populated, so the device is detected correctly. However, the adapter still uses the old API structure and attempts to request status information through the previous endpoints. These requests are no longer answered by the Z70, because – just like the Q10 – it has fully switched to the new products[] structure and the new RPC schema.

This results in a different error pattern on my side:
The adapter does detect the device, but every status request ends in a timeout, for example:

Failed to update status: Task XXX timed out after 10000ms.

So the root cause appears to be the same (new API, new schema, old endpoints), but the symptoms differ:

• Q10: devices[] is empty → device is ignored
• Z70: devices[] is populated → device is detected, but all requests go nowhere → timeouts

All relevant datapoints are located – just like with the Q10 – exclusively inside products[] and the new RPC schema (IDs 101, 102, 120, 121, 123, 143, etc.).

I also want to mention that I really appreciate this adapter. I have been using it for a long time, starting back when I owned the S7 MaxV and later the S8 MaxV, and it has always worked flawlessly for me. It has been a central part of my home automation setup and has made many workflows significantly easier. Since the adapter previously worked perfectly with my Saros Z70 as well and is very important for my automation, I would be very happy if the device could be fully supported again after the API changes.

For reference, I am currently using adapter version 0.6.19+7fca6df.

If you need tests, logs, or live debugging, I am more than happy to provide my Z70 for that.

Thank you very much for your work and your support!

[copystring]

@leinadloisl-byte you could have tested https://github.com/copystring/ioBroker.roborock. Install via GitHub cat in ioBroker. It should work.

[leinadloisl-byte]

Thanks for your reply and your help! Hmmm, I installed version 0.6.19+7fca6df, but unfortunately it still doesn’t work for me – hopefully I’m not doing anything wrong :D
ioBroker: v7.7.22, Node.js: v22.22.1, NPM: 10.9.4

[copystring]

Please post a debug log from the start of the adapter and 3 minutes after that showing the errors/warnings/issues.

[leinadloisl-byte]

Here is the debug log from the adapter start plus about three minutes of runtime. The timeouts start appearing right after initialization. :)

[copystring]

Thanks, but this is no debug log. Only info. Please create a debug log. Attach as .txt. No pasting.

[leinadloisl-byte]

Oh sorry, it's my first time :D I hope it's correct now.

log-2026-03-09.txt

[copystring]

Thanks. Please also paste your homedata.

[leinadloisl-byte]

Yes :)

HomeData.txt

[copystring]

Thanks. Please create a new debug log with https://github.com/copystring/ioBroker.roborock/tree/1080-feature-unterst%C3%BCtzung-f%C3%BCr-neue-api-struktur-roborock-q10-series. I added new logging to dig deeper into this issue.

[copystring]

If you tried this already, I just made further adjustments. Please reload again.