Roborock Adapter tester gesucht
-
Ich habe gerade mal versucht mir einen ersten VIS View zu bauen.
Dazu wollte ich unter anderem das Object verwenden:
roborock.0.Devices.52xxxxxxxmr.deviceStatus.123Hier sollte eigentlich der in der App aktuell eingestellte Status "Saugleistung" erscheinen. Im Log kann ich dieses auch unmittelbar nach Umschalten in der App sehen aber das Object ändert sich nicht.
Mal ein GIF gemacht, hoffe ihr könnt das im Log erkennen.
Ist das bei euch auch so?
-
@wendy2702 Die aktuelle Saugleistung wird unter roborock.0.Devices.YOUR_DEVICE.deviceConfig.fan_power angezeigt.
-
-
Habe den Adapter jetzt auch am laufen mit der neusten Version bon Github.
Im Protokoll erscheinen diese Meldungen:
roborock.0 2023-01-23 10:02:19.049 warn State "roborock.0.Devices.5jvoTYPcMgvzBKdzXt0fqC.cleaningInfo.Records.14.map_flag" has no existing object, this might lead to an error in future versions roborock.0 2023-01-23 10:02:19.049 warn State "roborock.0.Devices.5jvoTYPcMgvzBKdzXt0fqC.cleaningInfo.Records.14.wash_count" has no existing object, this might lead to an error in future versions roborock.0 2023-01-23 10:02:19.049 warn State "roborock.0.Devices.5jvoTYPcMgvzBKdzXt0fqC.cleaningInfo.Records.14.avoid_count" has no existing object, this might lead to an error in future versions roborock.0 2023-01-23 10:02:19.049 warn State "roborock.0.Devices.5jvoTYPcMgvzBKdzXt0fqC.cleaningInfo.Records.7.map_flag" has no existing object, this might lead to an error in future versions roborock.0 2023-01-23 10:02:19.049 warn State "roborock.0.Devices.5jvoTYPcMgvzBKdzXt0fqC.cleaningInfo.Records.7.wash_count" has no existing object, this might lead to an error in future versions roborock.0 2023-01-23 10:02:19.048 warn State "roborock.0.Devices.5jvoTYPcMgvzBKdzXt0fqC.cleaningInfo.Records.7.avoid_count" has no existing object, this might lead to an error in future versions roborock.0 2023-01-23 10:02:19.048 warn State "roborock.0.Devices.5jvoTYPcMgvzBKdzXt0fqC.cleaningInfo.Records.9.map_flag" has no existing object, this might lead to an error in future versions roborock.0 2023-01-23 10:02:19.048 warn State "roborock.0.Devices.5jvoTYPcMgvzBKdzXt0fqC.cleaningInfo.Records.9.wash_count" has no existing object, this might lead to an error in future versions roborock.0 2023-01-23 10:02:19.048 warn State "roborock.0.Devices.5jvoTYPcMgvzBKdzXt0fqC.cleaningInfo.Records.9.avoid_count" has no existing object, this might lead to an error in future versions roborock.0 2023-01-23 10:02:19.047 warn State "roborock.0.Devices.5jvoTYPcMgvzBKdzXt0fqC.cleaningInfo.Records.16.map_flag" has no existing object, this might lead to an error in future versions roborock.0 2023-01-23 10:02:19.047 warn State "roborock.0.Devices.5jvoTYPcMgvzBKdzXt0fqC.cleaningInfo.Records.16.wash_count" has no existing object, this might lead to an error in future versions roborock.0 2023-01-23 10:02:19.047 warn State "roborock.0.Devices.5jvoTYPcMgvzBKdzXt0fqC.cleaningInfo.Records.16.avoid_count" has no existing object, this might lead to an error in future versions roborock.0 2023-01-23 10:02:19.046 warn State "roborock.0.Devices.5jvoTYPcMgvzBKdzXt0fqC.cleaningInfo.Records.17.map_flag" has no existing object, this might lead to an error in future versions roborock.0 2023-01-23 10:02:19.046 warn State "roborock.0.Devices.5jvoTYPcMgvzBKdzXt0fqC.cleaningInfo.Records.17.wash_count" has no existing object, this might lead to an error in future versions roborock.0 2023-01-23 10:02:19.046 warn State "roborock.0.Devices.5jvoTYPcMgvzBKdzXt0fqC.cleaningInfo.Records.17.avoid_count" has no existing object, this might lead to an error in future versions roborock.0 2023-01-23 10:02:18.914 warn State "roborock.0.Devices.5jvoTYPcMgvzBKdzXt0fqC.cleaningInfo.Records.5.map_flag" has no existing object, this might lead to an error in future versions roborock.0 2023-01-23 10:02:18.914 warn State "roborock.0.Devices.5jvoTYPcMgvzBKdzXt0fqC.cleaningInfo.Records.5.wash_count" has no existing object, this might lead to an error in future versions roborock.0 2023-01-23 10:02:18.914 warn State "roborock.0.Devices.5jvoTYPcMgvzBKdzXt0fqC.cleaningInfo.Records.5.avoid_count" has no existing object, this might lead to an error in future versions roborock.0 2023-01-23 10:02:18.914 warn State "roborock.0.Devices.5jvoTYPcMgvzBKdzXt0fqC.cleaningInfo.Records.13.map_flag" has no existing object, this might lead to an error in future versions roborock.0 2023-01-23 10:02:18.914 warn State "roborock.0.Devices.5jvoTYPcMgvzBKdzXt0fqC.cleaningInfo.Records.13.wash_count" has no existing object, this might lead to an error in future versions roborock.0 2023-01-23 10:02:18.913 warn State "roborock.0.Devices.5jvoTYPcMgvzBKdzXt0fqC.cleaningInfo.Records.13.avoid_count" has no existing object, this might lead to an error in future versions roborock.0 2023-01-23 10:02:18.913 warn State "roborock.0.Devices.5jvoTYPcMgvzBKdzXt0fqC.cleaningInfo.Records.11.map_flag" has no existing object, this might lead to an error in future versions roborock.0 2023-01-23 10:02:18.913 warn State "roborock.0.Devices.5jvoTYPcMgvzBKdzXt0fqC.cleaningInfo.Records.11.wash_count" has no existing object, this might lead to an error in future versions roborock.0 2023-01-23 10:02:18.913 warn State "roborock.0.Devices.5jvoTYPcMgvzBKdzXt0fqC.cleaningInfo.Records.11.avoid_count" has no existing object, this might lead to an error in future versions roborock.0 2023-01-23 10:02:18.912 warn State "roborock.0.Devices.5jvoTYPcMgvzBKdzXt0fqC.cleaningInfo.Records.10.map_flag" has no existing object, this might lead to an error in future versions roborock.0 2023-01-23 10:02:18.912 warn State "roborock.0.Devices.5jvoTYPcMgvzBKdzXt0fqC.cleaningInfo.Records.10.wash_count" has no existing object, this might lead to an error in future versions roborock.0 2023-01-23 10:02:18.912 warn State "roborock.0.Devices.5jvoTYPcMgvzBKdzXt0fqC.cleaningInfo.Records.10.avoid_count" has no existing object, this might lead to an error in future versions roborock.0 2023-01-23 10:02:18.912 warn State "roborock.0.Devices.5jvoTYPcMgvzBKdzXt0fqC.cleaningInfo.Records.15.map_flag" has no existing object, this might lead to an error in future versions roborock.0 2023-01-23 10:02:18.912 warn State "roborock.0.Devices.5jvoTYPcMgvzBKdzXt0fqC.cleaningInfo.Records.15.wash_count" has no existing object, this might lead to an error in future versions roborock.0 2023-01-23 10:02:18.912 warn State "roborock.0.Devices.5jvoTYPcMgvzBKdzXt0fqC.cleaningInfo.Records.15.avoid_count" has no existing object, this might lead to an error in future versions roborock.0 2023-01-23 10:02:18.911 warn State "roborock.0.Devices.5jvoTYPcMgvzBKdzXt0fqC.cleaningInfo.Records.18.map_flag" has no existing object, this might lead to an error in future versions roborock.0 2023-01-23 10:02:18.911 warn State "roborock.0.Devices.5jvoTYPcMgvzBKdzXt0fqC.cleaningInfo.Records.18.wash_count" has no existing object, this might lead to an error in future versions roborock.0 2023-01-23 10:02:18.911 warn State "roborock.0.Devices.5jvoTYPcMgvzBKdzXt0fqC.cleaningInfo.Records.18.avoid_count" has no existing object, this might lead to an error in future versions roborock.0 2023-01-23 10:02:18.911 warn State "roborock.0.Devices.5jvoTYPcMgvzBKdzXt0fqC.cleaningInfo.Records.12.map_flag" has no existing object, this might lead to an error in future versions roborock.0 2023-01-23 10:02:18.911 warn State "roborock.0.Devices.5jvoTYPcMgvzBKdzXt0fqC.cleaningInfo.Records.12.wash_count" has no existing object, this might lead to an error in future versions roborock.0 2023-01-23 10:02:18.911 warn State "roborock.0.Devices.5jvoTYPcMgvzBKdzXt0fqC.cleaningInfo.Records.12.avoid_count" has no existing object, this might lead to an error in future versions roborock.0 2023-01-23 10:02:18.910 warn State "roborock.0.Devices.5jvoTYPcMgvzBKdzXt0fqC.cleaningInfo.Records.2.map_flag" has no existing object, this might lead to an error in future versions roborock.0 2023-01-23 10:02:18.910 warn State "roborock.0.Devices.5jvoTYPcMgvzBKdzXt0fqC.cleaningInfo.Records.2.wash_count" has no existing object, this might lead to an error in future versions roborock.0 2023-01-23 10:02:18.910 warn State "roborock.0.Devices.5jvoTYPcMgvzBKdzXt0fqC.cleaningInfo.Records.2.avoid_count" has no existing object, this might lead to an error in future versions roborock.0 2023-01-23 10:02:18.910 warn State "roborock.0.Devices.5jvoTYPcMgvzBKdzXt0fqC.cleaningInfo.Records.19.map_flag" has no existing object, this might lead to an error in future versions roborock.0 2023-01-23 10:02:18.910 warn State "roborock.0.Devices.5jvoTYPcMgvzBKdzXt0fqC.cleaningInfo.Records.19.wash_count" has no existing object, this might lead to an error in future versions roborock.0 2023-01-23 10:02:18.910 warn State "roborock.0.Devices.5jvoTYPcMgvzBKdzXt0fqC.cleaningInfo.Records.19.avoid_count" has no existing object, this might lead to an error in future versions roborock.0 2023-01-23 10:02:18.909 warn State "roborock.0.Devices.5jvoTYPcMgvzBKdzXt0fqC.cleaningInfo.Records.8.map_flag" has no existing object, this might lead to an error in future versions roborock.0 2023-01-23 10:02:18.909 warn State "roborock.0.Devices.5jvoTYPcMgvzBKdzXt0fqC.cleaningInfo.Records.8.wash_count" has no existing object, this might lead to an error in future versions roborock.0 2023-01-23 10:02:18.909 warn State "roborock.0.Devices.5jvoTYPcMgvzBKdzXt0fqC.cleaningInfo.Records.8.avoid_count" has no existing object, this might lead to an error in future versions roborock.0 2023-01-23 10:02:18.909 warn State "roborock.0.Devices.5jvoTYPcMgvzBKdzXt0fqC.cleaningInfo.Records.0.map_flag" has no existing object, this might lead to an error in future versions roborock.0 2023-01-23 10:02:18.908 warn State "roborock.0.Devices.5jvoTYPcMgvzBKdzXt0fqC.cleaningInfo.Records.0.wash_count" has no existing object, this might lead to an error in future versions roborock.0 2023-01-23 10:02:18.908 warn State "roborock.0.Devices.5jvoTYPcMgvzBKdzXt0fqC.cleaningInfo.Records.0.avoid_count" has no existing object, this might lead to an error in future versions roborock.0 2023-01-23 10:02:18.908 warn State "roborock.0.Devices.5jvoTYPcMgvzBKdzXt0fqC.cleaningInfo.Records.6.map_flag" has no existing object, this might lead to an error in future versions roborock.0 2023-01-23 10:02:18.908 warn State "roborock.0.Devices.5jvoTYPcMgvzBKdzXt0fqC.cleaningInfo.Records.6.wash_count" has no existing object, this might lead to an error in future versions roborock.0 2023-01-23 10:02:18.908 warn State "roborock.0.Devices.5jvoTYPcMgvzBKdzXt0fqC.cleaningInfo.Records.6.avoid_count" has no existing object, this might lead to an error in future versions roborock.0 2023-01-23 10:02:18.907 warn State "roborock.0.Devices.5jvoTYPcMgvzBKdzXt0fqC.cleaningInfo.Records.4.map_flag" has no existing object, this might lead to an error in future versions roborock.0 2023-01-23 10:02:18.907 warn State "roborock.0.Devices.5jvoTYPcMgvzBKdzXt0fqC.cleaningInfo.Records.4.wash_count" has no existing object, this might lead to an error in future versions roborock.0 2023-01-23 10:02:18.907 warn State "roborock.0.Devices.5jvoTYPcMgvzBKdzXt0fqC.cleaningInfo.Records.4.avoid_count" has no existing object, this might lead to an error in future versions roborock.0 2023-01-23 10:02:18.887 warn State "roborock.0.Devices.5jvoTYPcMgvzBKdzXt0fqC.cleaningInfo.Records.3.map_flag" has no existing object, this might lead to an error in future versions roborock.0 2023-01-23 10:02:18.887 warn State "roborock.0.Devices.5jvoTYPcMgvzBKdzXt0fqC.cleaningInfo.Records.3.wash_count" has no existing object, this might lead to an error in future versions roborock.0 2023-01-23 10:02:18.887 warn State "roborock.0.Devices.5jvoTYPcMgvzBKdzXt0fqC.cleaningInfo.Records.3.avoid_count" has no existing object, this might lead to an error in future versions roborock.0 2023-01-23 10:02:18.884 warn State "roborock.0.Devices.5jvoTYPcMgvzBKdzXt0fqC.cleaningInfo.Records.1.map_flag" has no existing object, this might lead to an error in future versions roborock.0 2023-01-23 10:02:18.884 warn State "roborock.0.Devices.5jvoTYPcMgvzBKdzXt0fqC.cleaningInfo.Records.1.wash_count" has no existing object, this might lead to an error in future versions roborock.0 2023-01-23 10:02:18.884 warn State "roborock.0.Devices.5jvoTYPcMgvzBKdzXt0fqC.cleaningInfo.Records.1.avoid_count" has no existing object, this might lead to an error in future versions roborock.0 2023-01-23 10:02:18.827 warn State "roborock.0.Devices.5jvoTYPcMgvzBKdzXt0fqC.consumables.cleaning_brush_work_times" has no existing object, this might lead to an error in future versions roborock.0 2023-01-23 10:02:18.827 warn State "roborock.0.Devices.5jvoTYPcMgvzBKdzXt0fqC.consumables.strainer_work_times" has no existing object, this might lead to an error in future versions roborock.0 2023-01-23 10:02:18.791 warn State "roborock.0.Devices.5jvoTYPcMgvzBKdzXt0fqC.deviceStatus.133" has no existing object, this might lead to an error in future versions roborock.0 2023-01-23 10:02:18.790 warn State "roborock.0.Devices.5jvoTYPcMgvzBKdzXt0fqC.deviceStatus.128" has no existing object, this might lead to an error in future versions roborock.0 2023-01-23 10:02:18.631 info MQTT initialized roborock.0 2023-01-23 10:02:18.460 info starting. Version 0.0.1 (non-npm: copystring/ioBroker.roborock#e61b9a6c19d3fa5386a01e581d50c20aa07df82d) in C:/Program Files/iobroker/SmartHome/node_modules/iobroker.roborock, node: v16.19.0, js-controller: 4.0.24Kann man das beheben oder ignorieren?
Wie bekomme ich die Akkuanzeige hin? -
@m-a-hueb welchen Saugroboter hast du?
-
@copystring Habe das mit dem Akku usw. auch an einem S7+
Wenn du logs oder was anderes benötigst, gib Bescheid!
-
Gleiches beim S7 Pro Ultra
-
@copystring Roborock S7 Maxv Ultra
-
Es wird so sein, dass die verschiedenen Roboter verschieden Funktionen haben (ist ja auch logisch). Das habe ich aber erwartet und musste den Adapter entsprechend anpassen. Dafür habe ich aber einiges vorbereitet und sollte von daher gar nicht so kompliziert werden dies entsprechend anzupassen.
Da der Adapter die Ergebnisse nur vom s7 kennt kommen bei unbekannten Parametern die entsprechenden Fehler. -
@copystring OK.
Dachte immer der S7 und S7+ unterscheiden sich nur in der Absaugstation.
Freue mich auf deine Weiterentwicklung.
-
@copystring
Evtl. könntest du auch demnächst eine Versionierung des Adapters einführen. Somit könnte man wieder einfach zurück, wenn etwas mit der aktuellen Version nicht läuft.
Danke. -
@wendy2702 genau und die Parameter der Absaugstation kennt er nicht
-
@copystring Kann es sein das die Objekte 127, 126, 125 angaben für Wartung beinhalten?
127 passt bei mir zum Filter
126 passt bei mir zur Seitenbürste
125 passt bei mir zur HauptbürsteWie sieht das bei den anderen aus?
-
@wendy2702 said in Roborock Adapter tester gesucht:
@copystring Kann es sein das die Objekte 127, 126, 125 angaben für Wartung beinhalten?
127 passt bei mir zum Filter
126 passt bei mir zur Seitenbürste
125 passt bei mir zur HauptbürsteWie sieht das bei den anderen aus?
Wenn ich die werte in der App vergleiche, dann stimmt es nicht ganz genau.
Roborock s7 Pro Ultra.127 = Wert 48; in App 45 ; Filter
126 = Wert 61; in App 59; Seitenbürste
125 = Wert 74; in App 73; Hauptbürste -
@dontoben Deckt sich bei mir S7 Maxv Ultra
-
Ich habe begonnen die Basis für die verschiedenen Roboter zu schaffen.
Nun müsste ich wissen welche Namen eure Roboter genau haben um die entsprechenden Dateien zu erstellen. Wenn ihr für mich https://github.com/copystring/ioBroker.roborock/tree/split_robots_into_classes testen könntet wäre das echt klasse. Im Log erscheint dann folgendes:
Wobei bei Test vacuum log kommt wahrscheinlich ein Fehler erscheinen wird da außer dem Roborock S7 nichts anderes unterstützt wird. Das baue ich dann entsprechend ein wenn ich die Namen aus dem entsprechenden log von euch erhalte.Interessant wären die dazugehörigen fehlenden Parameter wie hier z.B. zu sehen ist:
@m-a-hueb said in Roborock Adapter tester gesucht:
roborock.0 2023-01-23 10:02:19.049 warn State "roborock.0.Devices.5jvoTYPcMgvzBKdzXt0fqC.cleaningInfo.Records.14.map_flag" has no existing object, this might lead to an error in future versions roborock.0 2023-01-23 10:02:19.049 warn State "roborock.0.Devices.5jvoTYPcMgvzBKdzXt0fqC.cleaningInfo.Records.14.wash_count" has no existing object, this might lead to an error in future versions roborock.0 2023-01-23 10:02:19.049 warn State "roborock.0.Devices.5jvoTYPcMgvzBKdzXt0fqC.cleaningInfo.Records.14.avoid_count" has no existing object, this might lead to an error in future versions roborock.0 -
@copystring sagte in Roborock Adapter tester gesucht:
https://github.com/copystring/ioBroker.roborock/tree/split_robots_into_classes
EDIT:
Hier ist es... schon zu spät heute:
2023-01-24 22:18:55.403 - debug: roborock.0 (1033256) Detected robot name: Roborock S7 2023-01-24 22:18:55.404 - debug: roborock.0 (1033256) Test vacuum log: roborock_s7 -
@copystring
Frisch installiert und funzt auf Anhieb
Jede Menge Datenpunkte mit mehr oder weniger sinnvollen Werten.
Aber gelaufen ist unser "Freddie" seit der Installation noch nicht - der hat für heute Feierabend
Für den ersten Adapter funktioniert das schon erfreulich gut.
Was mir beim einen oder anderen Datenpunkt aufgefallen ist: Hier steht an diversen Stellen nur ein numerischer Wert. Hast Du die Doku zum API irgendwo greifbar? Dann könnte man diese numerischen Werte ja auch in Klartext übersetzen.
Beispiele (u.a.)
-
Da bekomme ich eine Fehlermedlung im Log:
roborock.0 2023-01-25 09:02:56.087 warn Terminated (UNCAUGHT_EXCEPTION): Without reason roborock.0 2023-01-25 09:02:56.086 info terminating roborock.0 2023-01-25 09:02:56.085 error Exception-Code: MODULE_NOT_FOUND: Cannot find module './undefined' Require stack: - C:\Program Files\iobroker\SmartHome\node_modules\iobroker.roborock\lib\vacuum.js - C:\Program Files\iobroker\SmartHome\node_modules\iobroker.roborock\main.js roborock.0 2023-01-25 09:02:56.085 error Error: Cannot find module './undefined' Require stack: - C:\Program Files\iobroker\SmartHome\node_modules\iobroker.roborock\lib\vacuum.js - C:\Program Files\iobroker\SmartHome\node_modules\iobroker.roborock\main.js at Function.Module._resolveFilename (node:internal/modules/cjs/loader:995:15) at Function.Module._load (node:internal/modules/cjs/loader:841:27) at Module.require (node:internal/modules/cjs/loader:1067:19) at require (node:internal/modules/cjs/helpers:103:18) at new vacuum (C:\Program Files\iobroker\SmartHome\node_modules\iobroker.roborock\lib\vacuum.js:19:31) at Roborock.onReady (C:\Program Files\iobroker\SmartHome\node_modules\iobroker.roborock\main.js:172:20) roborock.0 2023-01-25 09:02:56.085 error unhandled promise rejection: Cannot find module './undefined' Require stack: - C:\Program Files\iobroker\SmartHome\node_modules\iobroker.roborock\lib\vacuum.js - C:\Program Files\iobroker\SmartHome\node_modules\iobroker.roborock\main.js roborock.0 2023-01-25 09:02:56.085 error Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). roborock.0 2023-01-25 09:02:56.082 info MQTT initialized roborock.0 2023-01-25 09:02:55.464 info starting. Version 0.0.1 (non-npm: copystring/ioBroker.roborock#split_robots_into_classes) in C:/Program Files/iobroker/SmartHome/node_modules/iobroker.roborock, node: v16.19.0, js-controller: 4.0.24 -
@m-a-hueb said in Roborock Adapter tester gesucht:
Da bekomme ich eine Fehlermedlung im Log:
roborock.0 2023-01-25 09:02:56.087 warn Terminated (UNCAUGHT_EXCEPTION): Without reason roborock.0 2023-01-25 09:02:56.086 info terminating roborock.0 2023-01-25 09:02:56.085 error Exception-Code: MODULE_NOT_FOUND: Cannot find module './undefined' Require stack: - C:\Program Files\iobroker\SmartHome\node_modules\iobroker.roborock\lib\vacuum.js - C:\Program Files\iobroker\SmartHome\node_modules\iobroker.roborock\main.js roborock.0 2023-01-25 09:02:56.085 error Error: Cannot find module './undefined' Require stack: - C:\Program Files\iobroker\SmartHome\node_modules\iobroker.roborock\lib\vacuum.js - C:\Program Files\iobroker\SmartHome\node_modules\iobroker.roborock\main.js at Function.Module._resolveFilename (node:internal/modules/cjs/loader:995:15) at Function.Module._load (node:internal/modules/cjs/loader:841:27) at Module.require (node:internal/modules/cjs/loader:1067:19) at require (node:internal/modules/cjs/helpers:103:18) at new vacuum (C:\Program Files\iobroker\SmartHome\node_modules\iobroker.roborock\lib\vacuum.js:19:31) at Roborock.onReady (C:\Program Files\iobroker\SmartHome\node_modules\iobroker.roborock\main.js:172:20) roborock.0 2023-01-25 09:02:56.085 error unhandled promise rejection: Cannot find module './undefined' Require stack: - C:\Program Files\iobroker\SmartHome\node_modules\iobroker.roborock\lib\vacuum.js - C:\Program Files\iobroker\SmartHome\node_modules\iobroker.roborock\main.js roborock.0 2023-01-25 09:02:56.085 error Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). roborock.0 2023-01-25 09:02:56.082 info MQTT initialized roborock.0 2023-01-25 09:02:55.464 info starting. Version 0.0.1 (non-npm: copystring/ioBroker.roborock#split_robots_into_classes) in C:/Program Files/iobroker/SmartHome/node_modules/iobroker.roborock, node: v16.19.0, js-controller: 4.0.24Ist das ein debug Log? Es fehlt der Name vom Roboter der via debug angezeigt werden sollte.
