Neuer Adapter für Roborock-Staubsauger
-
@highline das geht manuell in den Objekten oder automatisch via Blockly oder JS Lösung. Ich mache das über die VIS. Diese beschreibt einen Datenpunkt und dieser wird via JS überwacht, ausgewertet und die entsprechende Aktion gestartet.
Ro75.
-
@ro75 Kannst du eventuell das entsprechende Script zur Verfügung stellen? Ich würde mir das gerne als Vorlage ansehen.
-
Hallo, jedesmal wenn der S8 in Aktion ist wird mir der Log mit Warnungen vollgeschrieben, weiß jemand was das ist?
In den Objekten gibt es keine Einträge dazu.24-11-26 08:09:00.628 - warn: roborock.0 (525) State "roborock.0.Devices.5JcrRUnxVs84yiX2hSJUkJ.cleaningInfo.records.0.map.mapBase64Truncated" has no existing object, this might lead to an error in future versions 2024-11-26 08:09:00.628 - warn: roborock.0 (525) State "roborock.0.Devices.5JcrRUnxVs84yiX2hSJUkJ.cleaningInfo.records.0.map.mapData" has no existing object, this might lead to an error in future versions 2024-11-26 08:09:04.432 - warn: roborock.0 (525) State "roborock.0.Devices.5JcrRUnxVs84yiX2hSJUkJ.cleaningInfo.records.21.begin" has no existing object, this might lead to an error in future versions 2024-11-26 08:09:04.433 - warn: roborock.0 (525) State "roborock.0.Devices.5JcrRUnxVs84yiX2hSJUkJ.cleaningInfo.records.21.end" has no existing object, this might lead to an error in future versions 2024-11-26 08:09:04.434 - warn: roborock.0 (525) State "roborock.0.Devices.5JcrRUnxVs84yiX2hSJUkJ.cleaningInfo.records.21.duration" has no existing object, this might lead to an error in future versions 2024-11-26 08:09:04.434 - warn: roborock.0 (525) State "roborock.0.Devices.5JcrRUnxVs84yiX2hSJUkJ.cleaningInfo.records.21.area" has no existing object, this might lead to an error in future versions 2024-11-26 08:09:04.435 - warn: roborock.0 (525) State "roborock.0.Devices.5JcrRUnxVs84yiX2hSJUkJ.cleaningInfo.records.21.error" has no existing object, this might lead to an error in future versions 2024-11-26 08:09:04.436 - warn: roborock.0 (525) State "roborock.0.Devices.5JcrRUnxVs84yiX2hSJUkJ.cleaningInfo.records.21.complete" has no existing object, this might lead to an error in future versions 2024-11-26 08:09:04.436 - warn: roborock.0 (525) State "roborock.0.Devices.5JcrRUnxVs84yiX2hSJUkJ.cleaningInfo.records.21.start_type" has no existing object, this might lead to an error in future versions 2024-11-26 08:09:04.437 - warn: roborock.0 (525) State "roborock.0.Devices.5JcrRUnxVs84yiX2hSJUkJ.cleaningInfo.records.21.clean_type" has no existing object, this might lead to an error in future versions 2024-11-26 08:09:04.438 - warn: roborock.0 (525) State "roborock.0.Devices.5JcrRUnxVs84yiX2hSJUkJ.cleaningInfo.records.21.finish_reason" has no existing object, this might lead to an error in future versions 2024-11-26 08:09:04.438 - warn: roborock.0 (525) State "roborock.0@chuck2941 Hallo , hast du da schon eine Info, ich habe genau das gleiche?
-
Hallo zusammen, ich brauche mal eure Hilfe, mein Roborock S8 zeigt auch diesen Fehler ( State "roborock.0.Devices.1opZH9d8PAaIcMMhNO0u9u.cleaningInfo.records.9.cleaned_area" has no existing object, this might lead to an error in future versions) im Protokol.
Der Fehler soll in Version 0.6.18 behoben sein. Wie kann ich auf die neue Version updaten. Oder was muss ich machen, um da weiter zu kommen? -
Hallo zusammen, ich brauche mal eure Hilfe, mein Roborock S8 zeigt auch diesen Fehler ( State "roborock.0.Devices.1opZH9d8PAaIcMMhNO0u9u.cleaningInfo.records.9.cleaned_area" has no existing object, this might lead to an error in future versions) im Protokol.
Der Fehler soll in Version 0.6.18 behoben sein. Wie kann ich auf die neue Version updaten. Oder was muss ich machen, um da weiter zu kommen? -
@elochso sagte in Neuer Adapter für Roborock-Staubsauger:
Wie kann ich auf die neue Version updaten.
wie immer, über latest.
sollte man halt wissen, was man tut... -
@elochso sagte in Neuer Adapter für Roborock-Staubsauger:
Wie kann ich auf die neue Version updaten.
wie immer, über latest.
sollte man halt wissen, was man tut... -
@da_woody wenn ich das im Terminal über iobroker update mache zeigt er mir bei Roboroch noch den alten Adapter 0.6.17 an
-
@da_woody danke dir muss noch mal rausfinden wie ich auf Beta umstelle, das hat mir aber schon super geholfen, DANKEEEEEE
-
@elochso sagte in Neuer Adapter für Roborock-Staubsauger:
@da_woody danke dir muss noch mal rausfinden wie ich auf Beta umstelle, das hat mir aber schon super geholfen, DANKEEEEEE
Geht auch so
und dann (sicherheitshalber)
noch einen Upload machen -
Jetzt kommt immer folgender Fehler:
Failed to execute get_map_v1 on robot 1opZH9d8PAaIcMMhNO0u9u (roborock.vacuum.a51): Error: Failed to convert JavaScript valueUndefinedinto rust typeStringat /opt/iobroker/node_modules/iobroker.roborock/lib/mapCreator.js:647:29 at Array.forEach (<anonymous>) at MapCreator.canvasMap (/opt/iobroker/node_modules/iobroker.roborock/lib/mapCreator.js:624:30) at vacuum.getMap (/opt/iobroker/node_modules/iobroker.roborock/lib/vacuum.js:84:46) -
Hab eben erst den Adapter installiert.
Ich habe absichtlich keinerlei Kartenerzeugung angewählt, bekomme aber im Log File: "Failed to map rooms. You need to name your rooms via the mobile app on your phone."Gibts da Abhilfe ausser in der Mobile App tätig zu werden ?
-
Hallo zusammen,
ich habe den QRevo Slim und bekomme folgende Fehlermeldungen:Unsupported attribute: kct of get_status with value 0. Please contact the dev to add the newly found attribute of your robot. Model: roborock.vacuum.a21
2025-01-05 16:25:22.073 warn State "roborock.0.Devices.52nkyxg5GRqLBvhDnBr6nw.consumables.dust_collection_work_times" has no existing object, this might lead to an error in future versionsroborock.0
2025-01-05 16:25:22.070 warn State "roborock.0.Devices.52nkyxg5GRqLBvhDnBr6nw.consumables.sensor_dirty_time" has no existing object, this might lead to an error in future versionsroborock.0
2025-01-05 16:25:22.070 warn State "roborock.0.Devices.52nkyxg5GRqLBvhDnBr6nw.consumables.filter_element_work_time" has no existing object, this might lead to an error in future versionsroborock.0
2025-01-05 16:25:22.070 warn State "roborock.0.Devices.52nkyxg5GRqLBvhDnBr6nw.consumables.filter_work_time" has no existing object, this might lead to an error in future versionsroborock.0
2025-01-05 16:25:22.068 warn State "roborock.0.Devices.52nkyxg5GRqLBvhDnBr6nw.consumables.side_brush_work_time" has no existing object, this might lead to an error in future versionsroborock.0
2025-01-05 16:25:22.067 warn State "roborock.0.Devices.52nkyxg5GRqLBvhDnBr6nw.consumables.main_brush_work_time" has no existing object, this might lead to an error in future versionsroborock.0
2025-01-05 16:25:02.479 warn Unsupported attribute: kct of get_status with value 0. Please contact the dev to add the newly found attribute of your robot. Model: roborock.vacuum.a21roborock.0
2025-01-05 16:25:01.496 warn Unsupported attribute: in_warmup of get_status with value 0. Please contact the dev to add the newly found attribute of your robot. Model: roborock.vacuum.a21roborock.0
2025-01-05 16:25:01.143 warn Unsupported attribute: monitor_status of get_status with value 0. Please contact the dev to add the newly found attribute of your robot. Model: roborock.vacuum.a21roborock.0
2025-01-05 16:24:22.101 warn State "roborock.0.Devices.52nkyxg5GRqLBvhDnBr6nw.consumables.dust_collection_work_times" has no existing object, this might lead to an error in future versionsroborock.0
2025-01-05 16:24:22.101 warn State "roborock.0.Devices.52nkyxg5GRqLBvhDnBr6nw.consumables.sensor_dirty_time" has no existing object, this might lead to an error in future versionsroborock.0
2025-01-05 16:24:22.100 warn State "roborock.0.Devices.52nkyxg5GRqLBvhDnBr6nw.consumables.filter_element_work_time" has no existing object, this might lead to an error in future versionsroborock.0
2025-01-05 16:24:22.100 warn State "roborock.0.Devices.52nkyxg5GRqLBvhDnBr6nw.consumables.filter_work_time" has no existing object, this might lead to an error in future versionsroborock.0
2025-01-05 16:24:22.097 warn State "roborock.0.Devices.52nkyxg5GRqLBvhDnBr6nw.consumables.side_brush_work_time" has no existing object, this might lead to an error in future versionsroborock.0
2025-01-05 16:24:22.096 warn State "roborock.0.Devices.52nkyxg5GRqLBvhDnBr6nw.consumables.main_brush_work_time" has no existing object, this might lead to an error in future versionsLiegt es daran dass der Slim noch nicht kompatibel ist?
Falls ja, kann dieser über ein Update mit aufgenommen werden :)?Vielen Dank vorab!
-
Hallo zusammen,
ich habe den QRevo Slim und bekomme folgende Fehlermeldungen:Unsupported attribute: kct of get_status with value 0. Please contact the dev to add the newly found attribute of your robot. Model: roborock.vacuum.a21
2025-01-05 16:25:22.073 warn State "roborock.0.Devices.52nkyxg5GRqLBvhDnBr6nw.consumables.dust_collection_work_times" has no existing object, this might lead to an error in future versionsroborock.0
2025-01-05 16:25:22.070 warn State "roborock.0.Devices.52nkyxg5GRqLBvhDnBr6nw.consumables.sensor_dirty_time" has no existing object, this might lead to an error in future versionsroborock.0
2025-01-05 16:25:22.070 warn State "roborock.0.Devices.52nkyxg5GRqLBvhDnBr6nw.consumables.filter_element_work_time" has no existing object, this might lead to an error in future versionsroborock.0
2025-01-05 16:25:22.070 warn State "roborock.0.Devices.52nkyxg5GRqLBvhDnBr6nw.consumables.filter_work_time" has no existing object, this might lead to an error in future versionsroborock.0
2025-01-05 16:25:22.068 warn State "roborock.0.Devices.52nkyxg5GRqLBvhDnBr6nw.consumables.side_brush_work_time" has no existing object, this might lead to an error in future versionsroborock.0
2025-01-05 16:25:22.067 warn State "roborock.0.Devices.52nkyxg5GRqLBvhDnBr6nw.consumables.main_brush_work_time" has no existing object, this might lead to an error in future versionsroborock.0
2025-01-05 16:25:02.479 warn Unsupported attribute: kct of get_status with value 0. Please contact the dev to add the newly found attribute of your robot. Model: roborock.vacuum.a21roborock.0
2025-01-05 16:25:01.496 warn Unsupported attribute: in_warmup of get_status with value 0. Please contact the dev to add the newly found attribute of your robot. Model: roborock.vacuum.a21roborock.0
2025-01-05 16:25:01.143 warn Unsupported attribute: monitor_status of get_status with value 0. Please contact the dev to add the newly found attribute of your robot. Model: roborock.vacuum.a21roborock.0
2025-01-05 16:24:22.101 warn State "roborock.0.Devices.52nkyxg5GRqLBvhDnBr6nw.consumables.dust_collection_work_times" has no existing object, this might lead to an error in future versionsroborock.0
2025-01-05 16:24:22.101 warn State "roborock.0.Devices.52nkyxg5GRqLBvhDnBr6nw.consumables.sensor_dirty_time" has no existing object, this might lead to an error in future versionsroborock.0
2025-01-05 16:24:22.100 warn State "roborock.0.Devices.52nkyxg5GRqLBvhDnBr6nw.consumables.filter_element_work_time" has no existing object, this might lead to an error in future versionsroborock.0
2025-01-05 16:24:22.100 warn State "roborock.0.Devices.52nkyxg5GRqLBvhDnBr6nw.consumables.filter_work_time" has no existing object, this might lead to an error in future versionsroborock.0
2025-01-05 16:24:22.097 warn State "roborock.0.Devices.52nkyxg5GRqLBvhDnBr6nw.consumables.side_brush_work_time" has no existing object, this might lead to an error in future versionsroborock.0
2025-01-05 16:24:22.096 warn State "roborock.0.Devices.52nkyxg5GRqLBvhDnBr6nw.consumables.main_brush_work_time" has no existing object, this might lead to an error in future versionsLiegt es daran dass der Slim noch nicht kompatibel ist?
Falls ja, kann dieser über ein Update mit aufgenommen werden :)?Vielen Dank vorab!
@adri525 sagte in Neuer Adapter für Roborock-Staubsauger:
Liegt es daran dass der Slim noch nicht kompatibel ist?
Falls ja, kann dieser über ein Update mit aufgenommen werden :)?Kommt lt Issue ins nächste Update rein
https://github.com/copystring/ioBroker.roborock/issues/738 -
Hi,
wie bekomme ich denn den Eintrag weg ohne den Adapter 0.6.18 deinstallieren zu müssen:
Bei mir funktioniert der nämlich nicht.
Und sieht das Debug log bei euch auch so aus, das geht so unendlich weiter.
roborock.0 2025-01-23 14:21:18.343 debug Client disconnected. Stopping interval. roborock.0 2025-01-23 14:21:17.342 debug Client disconnected. Stopping interval. roborock.0 2025-01-23 14:21:16.341 debug Client disconnected. Stopping interval. roborock.0 2025-01-23 14:21:15.340 debug Client disconnected. Stopping interval. roborock.0 2025-01-23 14:21:14.880 debug Client disconnected roborock.0 2025-01-23 14:21:14.879 debug Client disconnected. Stopping interval. roborock.0 2025-01-23 14:21:13.878 debug Websocket client connected roborock.0 2025-01-23 14:21:13.878 debug Websocket client connected roborock.0 2025-01-23 14:21:13.340 debug Client disconnected. Stopping interval. roborock.0 2025-01-23 14:21:12.339 debug Client disconnected. Stopping interval. roborock.0 2025-01-23 14:21:11.337 debug Client disconnected. Stopping interval. roborock.0 2025-01-23 14:21:10.337 debug Client disconnected. Stopping interval. roborock.0 2025-01-23 14:21:09.336 debug Client disconnected. Stopping interval. roborock.0 2025-01-23 14:21:08.335 debug Client disconnected. Stopping interval. roborock.0 2025-01-23 14:21:07.332 debug Client disconnected. Stopping interval. roborock.0 2025-01-23 14:21:06.329 debug Client disconnected. Stopping interval. roborock.0 2025-01-23 14:21:05.328 debug Client disconnected. Stopping interval. roborock.0 2025-01-23 14:21:04.327 debug Client disconnected. Stopping interval. roborock.0 2025-01-23 14:21:03.327 debug Client disconnected. Stopping interval. roborock.0 2025-01-23 14:21:02.882 debug Client disconnected roborock.0 2025-01-23 14:21:02.881 debug Client disconnected. Stopping interval. roborock.0 2025-01-23 14:21:02.441 debug Size of message queue: 0 roborock.0 2025-01-23 14:21:02.441 debug Local message with protocol 4 and id 499 received. Result: [203] roborock.0 2025-01-23 14:21:02.440 debug Chunk buffer data is complete. Processing... roborock.0 2025-01-23 14:21:02.439 debug new chunk started roborock.0 2025-01-23 14:21:02.435 debug Chunk buffer data is complete. Processing... roborock.0 2025-01-23 14:21:02.435 debug new chunk started roborock.0 2025-01-23 14:21:02.431 debug Sent payload for 5xxxxxmr with {"dps":{"4":"{\"id\":499,\"method\":\"get_water_box_custom_mode\",\"params\":[]}"},"t":1737638462} using local connection roborock.0 2025-01-23 14:21:02.326 debug Size of message queue: 0 roborock.0 2025-01-23 14:21:02.326 debug Local message with protocol 4 and id 498 received. Result: [{"carpet_clean_mode":1}] roborock.0 2025-01-23 14:21:02.325 debug Chunk buffer data is complete. Processing... roborock.0 2025-01-23 14:21:02.325 debug new chunk started roborock.0 2025-01-23 14:21:02.324 debug Chunk buffer data is complete. Processing... roborock.0 2025-01-23 14:21:02.323 debug new chunk started -
Hallo, ich habe mehrmals am Tag eine rote Meldung, wie bekomme ich die weg?
Failed to get home details: Error [ERR_SOCKET_DGRAM_NOT_RUNNING]: Not running at healthCheck (node:dgram:922:11) at Socket.bind (node:dgram:242:3) at /opt/iobroker/node_modules/iobroker.roborock/lib/localConnector.js:213:11 at new Promise (<anonymous>) at localConnector.getLocalDevices (/opt/iobroker/node_modules/iobroker.roborock/lib/localConnector.js:185:10) at Roborock.initializeHomeDetails (/opt/iobroker/node_modules/iobroker.roborock/main.js:197:56) at async /opt/iobroker/node_modules/iobroker.roborock/main.js:77:4 -
Hallo, ich habe mehrmals am Tag eine rote Meldung, wie bekomme ich die weg?
Failed to get home details: Error [ERR_SOCKET_DGRAM_NOT_RUNNING]: Not running at healthCheck (node:dgram:922:11) at Socket.bind (node:dgram:242:3) at /opt/iobroker/node_modules/iobroker.roborock/lib/localConnector.js:213:11 at new Promise (<anonymous>) at localConnector.getLocalDevices (/opt/iobroker/node_modules/iobroker.roborock/lib/localConnector.js:185:10) at Roborock.initializeHomeDetails (/opt/iobroker/node_modules/iobroker.roborock/main.js:197:56) at async /opt/iobroker/node_modules/iobroker.roborock/main.js:77:4@walter-white sagte in Neuer Adapter für Roborock-Staubsauger:
Hallo, ich habe mehrmals am Tag eine rote Meldung, wie bekomme ich die weg?
ich auch, alle 3 St.
roborock.0 2025-02-02 13:44:58.920 error Failed to get home details: Error: Not running at healthCheck (node:dgram:922:11) at Socket.bind (node:dgram:242:3) at /opt/iobroker/node_modules/iobroker.roborock/lib/localConnector.js:213:11 at new Promise (<anonymous>) at localConnector.getLocalDevices (/opt/iobroker/node_modules/iobroker.roborock/lib/localConnector.js:185:10) at Roborock.initializeHomeDetails (/opt/iobroker/node_modules/iobroker.roborock/main.js:197:56) at /opt/iobroker/node_modules/iobroker.roborock/main.js:77:4Roborock Q7 Max
655
Online32.7k
Users82.5k
Topics1.3m
Posts