NEWS
Roborock Adapter tester gesucht
-
Super funktioniert wieder. Danke.
-
Moin,
wird der S8 auch noch aufgenommen? Der Adapter sagt mir, dass das Modell nicht unterstützt wird.
Grüße
Lars2023-04-26 20:22:15.024 - error: roborock.0 (22761) The model ${robotModel} is not supported. Get in touch with the dev to get this robot supported.
-
@lptr Tach, bitte die dev testen.
-
Ich bin ein Vollnoob was 'not stable' Versionen angeht.
Wie installiere ich die Dev Version?
Danke im Voraus!Habs hier im Thread gefunden. Werde dann mal ein wenig testen.
-
Hallo Zusammen, hoffe der Post ist hier richtig: habe den Roborock Adapter installiert und nach dem Starten kommt die folgende Fehlermeldung:
roborock.0 2023-05-01 11:42:25.182 warn Terminated (UNCAUGHT_EXCEPTION): Without reason roborock.0 2023-05-01 11:42:25.180 info terminating roborock.0 2023-05-01 11:42:25.157 error Exception-Code: EADDRINUSE: listen EADDRINUSE: address already in use :::7906 roborock.0 2023-05-01 11:42:25.156 error Error: listen EADDRINUSE: address already in use :::7906 at Server.setupListenHandle [as _listen2] (node:net:1463:16) at listenInCluster (node:net:1511:12) at Server.listen (node:net:1599:7) at new WebSocketServer (/opt/iobroker/node_modules/ws/lib/websocket-server.js:97:20) at Roborock.startWebsocketServer (/opt/iobroker/node_modules/iobroker.roborock/main.js:244:18) at /opt/iobroker/node_modules/iobroker.roborock/main.js:205:12 roborock.0 2023-05-01 11:42:25.155 error uncaught exception: listen EADDRINUSE: address already in use :::7906 roborock.0 2023-05-01 11:42:24.595 info MQTT initialized roborock.0 2023-05-01 11:42:24.065 info starting. Version 0.1.6 (non-npm: copystring/ioBroker.roborock) in /opt/iobroker/node_modules/iobroker.roborock, node: v16.19.1, js-controller: 4.0.24
Kann mir hier jemand weiterhelfen bitte.
Schönen 1. Mai -
@cburger starte mal den PC neu.
-
@copystring - danke für die schnelle Antwort und den Tipp! Nun konnte ich auch einmal kurz die Website des Adapters aufrufen. Allerdings logt der Adapter nun andere Fehler und schmiert dann ab:
roborock.0 2023-05-01 13:58:34.118 info MQTT initialized roborock.0 2023-05-01 13:58:33.585 info starting. Version 0.1.6 (non-npm: copystring/ioBroker.roborock) in /opt/iobroker/node_modules/iobroker.roborock, node: v16.19.1, js-controller: 4.0.24 roborock.0 2023-05-01 13:57:59.535 warn Terminated (UNCAUGHT_EXCEPTION): Without reason roborock.0 2023-05-01 13:57:59.533 info terminating roborock.0 2023-05-01 13:57:59.506 error Cannot read properties of null (reading 'val') roborock.0 2023-05-01 13:57:59.505 error TypeError: Cannot read properties of null (reading 'val') at /opt/iobroker/node_modules/iobroker.roborock/lib/vacuum.js:296:89 at runMicrotasks (<anonymous>) at processTicksAndRejections (node:internal/process/task_queues:96:5) roborock.0 2023-05-01 13:57:59.499 error unhandled promise rejection: Cannot read properties of null (reading 'val') roborock.0 2023-05-01 13:57:59.498 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-05-01 13:57:57.962 info Roborock rejected the request for a new map. - retry roborock.0 2023-05-01 13:57:56.637 info MQTT initialized roborock.0 2023-05-01 13:57:56.079 info starting. Version 0.1.6 (non-npm: copystring/ioBroker.roborock) in /opt/iobroker/node_modules/iobroker.roborock, node: v16.19.1, js-controller: 4.0.24 roborock.0 2023-05-01 13:57:19.972 info MQTT initialized roborock.0 2023-05-01 13:57:19.356 info starting. Version 0.1.6 (non-npm: copystring/ioBroker.roborock) in /opt/iobroker/node_modules/iobroker.roborock, node: v16.19.1, js-controller: 4.0.24 roborock.0 2023-05-01 13:56:46.000 warn Terminated (UNCAUGHT_EXCEPTION): Without reason roborock.0 2023-05-01 13:56:45.998 info terminating roborock.0 2023-05-01 13:56:45.972 error Cannot read properties of null (reading 'val') roborock.0 2023-05-01 13:56:45.971 error TypeError: Cannot read properties of null (reading 'val') at /opt/iobroker/node_modules/iobroker.roborock/lib/vacuum.js:296:89 at runMicrotasks (<anonymous>) at processTicksAndRejections (node:internal/process/task_queues:96:5) roborock.0 2023-05-01 13:56:45.966 error unhandled promise rejection: Cannot read properties of null (reading 'val') roborock.0 2023-05-01 13:56:45.961 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-05-01 13:56:42.602 info MQTT initialized roborock.0 2023-05-01 13:56:42.013 info starting. Version 0.1.6 (non-npm: copystring/ioBroker.roborock) in /opt/iobroker/node_modules/iobroker.roborock, node: v16.19.1, js-controller: 4.0.24
-
@cburger Teste mal die dev Version https://github.com/copystring/ioBroker.roborock/tree/dev
-
@copystring , hoffe (und denk) alles richtig installiert zu haben. Nun kommt das Folgende
roborock.0 2023-05-01 14:10:19.547 error Cannot read properties of undefined (reading 'timeout102') roborock.0 2023-05-01 14:10:19.546 error TypeError: Cannot read properties of undefined (reading 'timeout102') at EventEmitter.listener102 (/opt/iobroker/node_modules/iobroker.roborock/lib/roborock_mqtt_connector.js:248:72) at EventEmitter.emit (/opt/iobroker/node_modules/eventemitter2/lib/eventemitter2.js:1019:19) at MqttClient.<anonymous> (/opt/iobroker/node_modules/iobroker.roborock/lib/roborock_mqtt_connector.js:167:9) at MqttClient.emit (node:events:513:28) at MqttClient.emit (node:domain:489:12) at MqttClient._handlePublish (/opt/iobroker/node_modules/mqtt/lib/client.js:1547:12) at MqttClient._handlePacket (/opt/iobroker/node_modules/mqtt/lib/client.js:535:12) at work (/opt/iobroker/node_modules/mqtt/lib/client.js:438:12) at Writable.writable._write (/opt/iobroker/node_modules/mqtt/lib/client.js:452:5) at doWrite (/opt/iobroker/node_modules/mqtt/node_modules/readable-stream/lib/_stream_writable.js:390:139) roborock.0 2023-05-01 14:10:19.544 error uncaught exception: Cannot read properties of undefined (reading 'timeout102') roborock.0 2023-05-01 14:10:19.510 error Error executing fileError: Command failed: /opt/iobroker/node_modules/iobroker.roborock/lib/go2rtc/go2rtc_linux_arm -config {"streams":{"2W7IyvOlcOhxokJjog5Zef":"roborock://mqtt-eu-3.roborock.com:8883?u=WedLEYQ1SRPAXKJVQf1Kx&s=YIKfVT&k=lscHyVO1&did=2W7IyvOlcOhxokJjog5Zef&key=2kXf5GJktah1eYuv&pin=1234"}} roborock.0 2023-05-01 14:10:19.461 warn Terminated (UNCAUGHT_EXCEPTION): Without reason roborock.0 2023-05-01 14:10:19.455 info terminating roborock.0 2023-05-01 14:10:19.404 error Exception-Code: EADDRINUSE: listen EADDRINUSE: address already in use :::7906 roborock.0 2023-05-01 14:10:19.403 error Error: listen EADDRINUSE: address already in use :::7906 at Server.setupListenHandle [as _listen2] (node:net:1463:16) at listenInCluster (node:net:1511:12) at Server.listen (node:net:1599:7) at new WebSocketServer (/opt/iobroker/node_modules/ws/lib/websocket-server.js:97:20) at Roborock.startWebsocketServer (/opt/iobroker/node_modules/iobroker.roborock/main.js:272:18) at /opt/iobroker/node_modules/iobroker.roborock/main.js:231:12 at runMicrotasks (<anonymous>) at processTicksAndRejections (node:internal/process/task_queues:96:5) roborock.0 2023-05-01 14:10:19.402 error uncaught exception: listen EADDRINUSE: address already in use :::7906 roborock.0 2023-05-01 14:10:12.879 info MQTT initialized roborock.0 2023-05-01 14:10:12.353 info starting. Version 0.1.6 (non-npm: copystring/ioBroker.roborock#dev) in /opt/iobroker/node_modules/iobroker.roborock, node: v16.19.1, js-controller: 4.0.24
-
@cburger starte nochmal den PC neu. Wenn das hier auftaucht,
Exception-Code: EADDRINUSE: listen EADDRINUSE: address already in use :::7906
dann hängt bei dir irgendwas fest. -
@copystring, habe neu gestartet ...
Jetzt bleibt der Adapter an und er loggt auch keine Fehler mehr. Vielen herzlichen Dank für deine Unterstützung und dir einen schönen ersten Mai!!
Viele Grüße aus dem Allgäu -
@copystring, leider zu früh gefreut :-/. Habe über den Adapter den Robo gestartet und dann passiert folgendes und der Adapter geht wieder auf rot und ich kann den Robi nicht mehr über den Adapter bedienen:
roborock.0 2023-05-01 14:20:46.037 error Error executing fileError: Command failed: /opt/iobroker/node_modules/iobroker.roborock/lib/go2rtc/go2rtc_linux_arm -config {"streams":{"2W7IyvOlcOhxokJjog5Zef":"roborock://mqtt-eu-3.roborock.com:8883?u=WedLEYQ1SRPAXKJVQf1Kx&s=YIKfVT&k=lscHyVO1&did=2W7IyvOlcOhxokJjog5Zef&key=2kXf5GJktah1eYuv&pin=1234"}} roborock.0 2023-05-01 14:20:39.182 info MQTT initialized roborock.0 2023-05-01 14:20:38.634 info starting. Version 0.1.6 (non-npm: copystring/ioBroker.roborock#dev) in /opt/iobroker/node_modules/iobroker.roborock, node: v16.19.1, js-controller: 4.0.24 roborock.0 2023-05-01 14:20:03.297 error Error executing fileError: Command failed: /opt/iobroker/node_modules/iobroker.roborock/lib/go2rtc/go2rtc_linux_arm -config {"streams":{"2W7IyvOlcOhxokJjog5Zef":"roborock://mqtt-eu-3.roborock.com:8883?u=WedLEYQ1SRPAXKJVQf1Kx&s=YIKfVT&k=lscHyVO1&did=2W7IyvOlcOhxokJjog5Zef&key=2kXf5GJktah1eYuv&pin=1234"}} roborock.0 2023-05-01 14:19:55.758 info MQTT initialized roborock.0 2023-05-01 14:19:55.130 info starting. Version 0.1.6 (non-npm: copystring/ioBroker.roborock#dev) in /opt/iobroker/node_modules/iobroker.roborock, node: v16.19.1, js-controller: 4.0.24 roborock.0 2023-05-01 14:19:11.182 error Failed to create map. The error was: locating roborock.0 2023-05-01 14:19:09.179 error Failed to create map. The error was: locating roborock.0 2023-05-01 14:19:07.178 error Failed to create map. The error was: locating roborock.0 2023-05-01 14:19:05.182 error Failed to create map. The error was: locating roborock.0 2023-05-01 14:19:03.210 error Failed to create map. The error was: locating roborock.0 2023-05-01 14:19:01.181 error Failed to create map. The error was: locating roborock.0 2023-05-01 14:18:59.184 error Failed to create map. The error was: locating roborock.0 2023-05-01 14:18:57.180 error Failed to create map. The error was: locating roborock.0 2023-05-01 14:18:55.207 error Failed to create map. The error was: locating roborock.0 2023-05-01 14:18:53.177 error Failed to create map. The error was: locating roborock.0 2023-05-01 14:18:51.177 error Failed to create map. The error was: locating roborock.0 2023-05-01 14:18:49.186 error Failed to create map. The error was: locating roborock.0 2023-05-01 14:18:43.211 error Failed to create canvas: {} roborock.0 2023-05-01 14:18:41.221 error Failed to create canvas: {} roborock.0 2023-05-01 14:18:39.223 error Failed to create canvas: {} roborock.0 2023-05-01 14:18:36.056 error Unknown parameter: ["ok"] roborock.0 2023-05-01 14:17:19.953 error Error executing fileError: Command failed: /opt/iobroker/node_modules/iobroker.roborock/lib/go2rtc/go2rtc_linux_arm -config {"streams":{"2W7IyvOlcOhxokJjog5Zef":"roborock://mqtt-eu-3.roborock.com:8883?u=WedLEYQ1SRPAXKJVQf1Kx&s=YIKfVT&k=lscHyVO1&did=2W7IyvOlcOhxokJjog5Zef&key=2kXf5GJktah1eYuv&pin=1234"}} roborock.0 2023-05-01 14:17:13.572 info MQTT initialized roborock.0 2023-05-01 14:17:12.924 info starting. Version 0.1.6 (non-npm: copystring/ioBroker.roborock#dev) in /opt/iobroker/node_modules/iobroker.roborock, node: v16.19.1, js-controller: 4.0.24
Neustart des Adapters bringt folgendes:
roborock.0 2023-05-01 14:24:25.658 error Cannot read properties of undefined (reading 'timeout102') roborock.0 2023-05-01 14:24:25.657 error TypeError: Cannot read properties of undefined (reading 'timeout102') at EventEmitter.listener102 (/opt/iobroker/node_modules/iobroker.roborock/lib/roborock_mqtt_connector.js:248:72) at EventEmitter.emit (/opt/iobroker/node_modules/eventemitter2/lib/eventemitter2.js:1019:19) at MqttClient.<anonymous> (/opt/iobroker/node_modules/iobroker.roborock/lib/roborock_mqtt_connector.js:167:9) at MqttClient.emit (node:events:513:28) at MqttClient.emit (node:domain:489:12) at MqttClient._handlePublish (/opt/iobroker/node_modules/mqtt/lib/client.js:1547:12) at MqttClient._handlePacket (/opt/iobroker/node_modules/mqtt/lib/client.js:535:12) at work (/opt/iobroker/node_modules/mqtt/lib/client.js:438:12) at Writable.writable._write (/opt/iobroker/node_modules/mqtt/lib/client.js:452:5) at doWrite (/opt/iobroker/node_modules/mqtt/node_modules/readable-stream/lib/_stream_writable.js:390:139) roborock.0 2023-05-01 14:24:25.656 error uncaught exception: Cannot read properties of undefined (reading 'timeout102') roborock.0 2023-05-01 14:24:25.627 error Error executing fileError: Command failed: /opt/iobroker/node_modules/iobroker.roborock/lib/go2rtc/go2rtc_linux_arm -config {"streams":{"2W7IyvOlcOhxokJjog5Zef":"roborock://mqtt-eu-3.roborock.com:8883?u=WedLEYQ1SRPAXKJVQf1Kx&s=YIKfVT&k=lscHyVO1&did=2W7IyvOlcOhxokJjog5Zef&key=2kXf5GJktah1eYuv&pin=1234"}} roborock.0 2023-05-01 14:24:25.582 warn Terminated (UNCAUGHT_EXCEPTION): Without reason roborock.0 2023-05-01 14:24:25.579 info terminating roborock.0 2023-05-01 14:24:25.547 error Exception-Code: EADDRINUSE: listen EADDRINUSE: address already in use :::7906 roborock.0 2023-05-01 14:24:25.545 error Error: listen EADDRINUSE: address already in use :::7906 at Server.setupListenHandle [as _listen2] (node:net:1463:16) at listenInCluster (node:net:1511:12) at Server.listen (node:net:1599:7) at new WebSocketServer (/opt/iobroker/node_modules/ws/lib/websocket-server.js:97:20) at Roborock.startWebsocketServer (/opt/iobroker/node_modules/iobroker.roborock/main.js:272:18) at /opt/iobroker/node_modules/iobroker.roborock/main.js:231:12 at runMicrotasks (<anonymous>) at processTicksAndRejections (node:internal/process/task_queues:96:5) roborock.0 2023-05-01 14:24:25.545 error uncaught exception: listen EADDRINUSE: address already in use :::7906 roborock.0 2023-05-01 14:24:25.504 error Exception-Code: EADDRINUSE: listen EADDRINUSE: address already in use :::6824 roborock.0 2023-05-01 14:24:25.502 error Error: listen EADDRINUSE: address already in use :::6824 at Server.setupListenHandle [as _listen2] (node:net:1463:16) at listenInCluster (node:net:1511:12) at Server.listen (node:net:1599:7) at Function.listen (/opt/iobroker/node_modules/express/lib/application.js:635:24) at Roborock.startWebserver (/opt/iobroker/node_modules/iobroker.roborock/main.js:265:19) at /opt/iobroker/node_modules/iobroker.roborock/main.js:230:12 at runMicrotasks (<anonymous>) at processTicksAndRejections (node:internal/process/task_queues:96:5) roborock.0 2023-05-01 14:24:25.500 error uncaught exception: listen EADDRINUSE: address already in use :::6824 roborock.0 2023-05-01 14:24:18.990 info MQTT initialized roborock.0 2023-05-01 14:24:18.431 info starting. Version 0.1.6 (non-npm: copystring/ioBroker.roborock#dev) in /opt/iobroker/node_modules/iobroker.roborock, node: v16.19.1, js-controller: 4.0.24
-
@cburger OK.
Dann bitte auf GitHub ein Issue eröffnen. Dort dann das vollständige debug log einfügen. -
@copystring, habe ich erstellt. Dank dir - so far!
-
Ich bekomme sporadisch verschiedene Fehlermeldungen:
roborock.0 2023-05-01 11:49:55.685 error Unknown parameter: ["ok"] host.iobroker 2023-05-01 11:48:27.276 error Invalid request getRepository. "callback" or "from" is null
oder
roborock.0 2023-05-01 17:17:34.190 error Failed to create map. The error was: retry
k.A. ob die für GitHub interessant sind.
-
@vumer said in Roborock Adapter tester gesucht:
Ich bekomme sporadisch verschiedene Fehlermeldungen:
roborock.0 2023-05-01 11:49:55.685 error Unknown parameter: ["ok"]
Das ist rein kosmetisch. Tut erstmal nichts zur sache.
oder
roborock.0 2023-05-01 17:17:34.190 error Failed to create map. The error was: retry
Der Roboter ist gerade mit etwas anderen beschäftigt. Daher kann gerade nicht eine neue Karte bezogen werden.
-
@copystring sagte in Roborock Adapter tester gesucht:
Das ist rein kosmetisch. Tut erstmal nichts zur sache.
hab irgendwie Allergie auf rot
-
Hallo zusammen
Ich habe seit einer Woche den Roborock S7 MaxV, nutze aber seither die XiaomiHome App und den passenden Adapter im ioBroker.
Erst im Nachhinein habe ich gesehen, dass es einen passenden "Roborock"-Adapter auf Github gibt.Nun zu meinen Fragen (betrifft diesen Adapter):
-Ist es möglich, mehrere Räume hintereinander reinigen zu lassen, ohne dass der Roboter zwischen den Räumer auf die Ladestation fährt?
-Kann der Wischen und/oder Saugen Modus geändert werden? Für jeden einzelnen Raum oder nur die komplette Reinigung?Ich habe vor, mehrere Favoriten zu erstellen.
-Reinigung von 4 der 7 Räume
-Reinigung von 2 der 7 Räume
-Einstellung für mit/ohne Wischen -
@kusi sagte in Roborock Adapter tester gesucht:
-Ist es möglich, mehrere Räume hintereinander reinigen zu lassen, ohne dass der Roboter zwischen den Räumer auf die Ladestation fährt?
Ja, das geht
-Kann der Wischen und/oder Saugen Modus geändert werden? Für jeden einzelnen Raum oder nur die komplette Reinigung?
Komplette Reinigung.
Ich habe vor, mehrere Favoriten zu erstellen.
-Reinigung von 4 der 7 Räume
-Reinigung von 2 der 7 Räume
-Einstellung für mit/ohne WischenPer Skript (Zb Blockly) möglich.
-
Hallo Leute,
ich benötige mal eure Hilfe.
Dies trifft nur diejenigen zu, bei denen die Kartenerstellung auf einem Raspberry Pi nicht läuft.
Ich hatte einen Fall, in dem es gereicht hat, folgendes ins Terminal auf dem Pi einzugeben und danach lief die Karte.cd /opt/iobroker/node_modules/iobroker.roborock/ npm install canvas
Danach den Adapter neu starten. Kartenerstellung aktivieren und am besten direkt über das Webinterface (z. B. http://iobroker:6824/map.html) ausprobieren.
Über kurze Rückmeldungen würde ich mich freuen. Danke im Voraus für eure Mithilfe!