Neuer Blogbeitrag: Monatsrückblick - Dezember 2025 🎄

[Liladi]

@michael-1975 danke für die Rückemeldung betreffend dem Typ. Irgendwie stehe ich auf dem Schlauch. Muss ich noch was aktivieren oder konfigurieren das ich den Adapter zum laufen bringe? Kann ja in den Einstellungen nicht viel mehr eintragen als user und psw. In der Hilfe finde ich auch nicht viel mehr.

Kriege folgende Fehlermeldungen direkt nach dem Start des Adapter, vielleicht kann mir ja jemand weiterhelfen?

roborock.0
2025-11-28 18:46:52.747 error Exception-Code: ERR_OSSL_WRONG_FINAL_BLOCK_LENGTH: error:1C80006B:Provider routines::wrong final block length

roborock.0
2025-11-28 18:46:52.746 error Error: error:1C80006B:Provider routines::wrong final block length at Decipheriv.final (node:internal/crypto/cipher:184:29) at localConnector.decryptECB (/opt/iobroker/node_modules/iobroker.roborock/lib/localConnector.js:227:25) at Socket.<anonymous> (/opt/iobroker/node_modules/iobroker.roborock/lib/localConnector.js:190:33) at Socket.emit (node:events:519:28) at Socket.emit (node:domain:489:12) at UDP.onMessage (node:dgram:990:8)

roborock.0
2025-11-28 18:46:52.746 error uncaught exception: error:1C80006B:Provider routines::wrong final block length

roborock.0
2025-11-28 18:46:50.597 info MQTT initialized

roborock.0
2025-11-28 18:46:49.930 info Starting adapter. This might take a few minutes depending on your setup. Please wait.

roborock.0
2025-11-28 18:46:49.919 info starting. Version 0.6.18 in /opt/iobroker/node_modules/iobroker.roborock, node: v22.21.0, js-controller: 7.0.7

[Ro75]

@Liladi nimm die 0.6.19 aus dem Beta-Kanal. Dann klappt das auch wieder.

Ro75.

[Liladi]

@Ro75 Danke für die rasche Antwort, hat mit 0.6.19 funktioniert

[Eckiwecky]

Hi, ich habe einen neuen Saros 10R und habe mir den Roborocks Adapter installiert.
Zunächst hatte ich Version 0.6.18 und hatte auch das Problem mit dem Fehler "ERR_OSSL_WRONG_FINAL_BLOCK_LENGTH".

Ich habe jetzt manuell auf 0.6.19 umgestellt und er konnte sich offenbar verbinden, denn ich sehe diverse Objekte.
Allerdings haut er mir sekündlich folgenden Fehler ins Log:

Failed to process mainUpdateInterval on robot <robotString_entfernt_von_Eckiwecky> (roborock.vacuum.a144): Error: this.get_status is not initialized. Request get_status first. at requests_handler.isCleaning (/opt/iobroker/node_modules/iobroker.roborock/lib/requests_handler.js:611:10) at /opt/iobroker/node_modules/iobroker.roborock/main.js:117:48 at Timeout._onTimeout (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/src/lib/adapter/adapter.ts:2800:38) at listOnTimeout (node:internal/timers:588:17) at processTimers (node:internal/timers:523:7)

Ich sehe auch im Objekt, dass alle Werte unter
roborock -> 0 -> Devices -> <robotString_entfernt_von_Eckiwecky> -> deviceStatus auf NULL stehen.
Aber mir ist nicht ganz klar, wie ich einen getState triggern kann, oder ist das ein Bug im Adapter?

[breaksrmine]

Hallo zusammen bekomme plötzlich seit gestern beim roborock adapter diese Meldung.
iobroker läuft seit 17 Tage durch und ist up2date. Es wurde nichts am ioBroker geändert.
Adapter neustarten, login neu gemacht usw., bringt alles keine Abhilfe. Auch Adapter für 4h ausgemacht.
Adapter v0.6.18

roborock.0
2025-12-07 00:40:45.838 error Failed to get home details: Error: loginApi is not initialized. at Roborock.initializeHomeDetails (/opt/iobroker/node_modules/iobroker.roborock/main.js:144:25) at Roborock.onReady (/opt/iobroker/node_modules/iobroker.roborock/main.js:67:14)

roborock.0
2025-12-07 00:40:45.515 error Error retrieving or setting clientID: Error: Login returned empty userdata. at Roborock.getUserData (/opt/iobroker/node_modules/iobroker.roborock/main.js:236:11) at processTicksAndRejections (node:internal/process/task_queues:105:5) at Roborock.initializeRoborockApi (/opt/iobroker/node_modules/iobroker.roborock/main.js:103:21) at Roborock.onReady (/opt/iobroker/node_modules/iobroker.roborock/main.js:65:34)

roborock.0
2025-12-07 00:40:45.505 error Error in getUserData: Login returned empty userdata.. This is most likely due to too many reconnects.

[Thomas Braun]

@breaksrmine
Siehe
https://forum.iobroker.net/topic/83143/roborock-adapter-funktioniert-nicht-mehr?_=1765065147179

[copystring]

Roborock hat die LoginApi geändert. Anmelden über die legacy Api ist nicht mehr möglich. Ich arbeite gerade an einer Lösung dazu. Das kann hier verfolgt werden. https://github.com/copystring/ioBroker.roborock/issues/945
Mein erster Test war OK, aber dauert noch ein bisschen. Bitte verfolgt das Issue diesbezüglich.

[breaksrmine]

ahhh ihr seid gorßartig ! vielen dank für die info und die mühe das anzupassen ! Der Adapter ist mega !

[m0skit0]

Hallo
erstmal vielen Dank an @copystring für die Arbeit an dem Adapter.
Ich habe die neuste Version 6.0.19 von Github heute heruntergeladen und den alten Adapter erst deinstalliert und dann den 6.1.9 installiert.
Das hat auch alles ohne Fehlermeldung geklappt. Adapter aber noch nicht gestartet.
Dann habe ich die komplette Karte gelöscht und den Sauger 1 x die komplette Wohnung saugen lassen.
Danach die App eingerichtet. Sperrzonen, Raumteilung,benennen der Räume, etc
Jetzt habe ich den Adapter gestartet.
Soweit wurden die Räume alle erkannt.
Was mir aufgefallen ist das jetzt alle Räume auf true stehen, diese müssen ja alle auf false gestellt werden damit ich per Sprachsteuerung die Räume saugen lassen kann, so war es zumindest beim alten Adapter.
In meinen Blockly die Räume zu jedem Raum hinzugefügt, die waren alle durcheinander(heisst WZ war Flur, etc.)
Jetzt habe ich per Sprachsteuerung die Küche saugen lassen und der Sauger fährt ins Bad. Alles nochmal kontrolliert im Blockly ... passt.
Den Sauger das WZ per Sprache saugen lassen und er fährt in den Flur, so ist das bei allen Räumen er fährt nie in den Raum den ich im angesagt habe.

Wo liegt hier der Fehler ? habe ich was falsch eingestellt im neuen Adapter ?
Für Hilfe wäre ich sehr dankbar.

Lg
moskito

[TimoWald]

Bei mir kommt aber seit den letzten Versionen nach wie vor eine Fehlermeldung.
Kann mir dazu jemand was sagen?

roborock.0
	2025-12-13 14:03:07.743	error	adapter disabled
roborock.0
	2025-12-13 14:02:31.072	error	Failed to process client.on('offline') on robot undefined (unknown device model): MQTT connection offline.
roborock.0
	2025-12-13 14:02:31.040	error	Failed to process client.on('error') on robot undefined (unknown device model): MQTT connection error: ErrorWithReasonCode: Connection refused: Not authorized. rriot.r.m: ssl://mqtt-eu-4.roborock.com:8883 rriot.u: 2vdYQYpwtUV54CgPMZChe7
roborock.0
	2025-12-13 14:02:30.962	error	this.homeData is not initialized. Initialize via getHomeData() first
roborock.0
	2025-12-13 14:02:30.962	error	Error: this.homeData is not initialized. Initialize via getHomeData() first at http_api.getDevices (/opt/iobroker/node_modules/iobroker.roborock/lib/http_api.js:179:10) at Roborock.onReady (/opt/iobroker/node_modules/iobroker.roborock/main.js:62:39)
roborock.0
	2025-12-13 14:02:30.961	error	unhandled promise rejection: this.homeData is not initialized. Initialize via getHomeData() first
roborock.0
	2025-12-13 14:02:30.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
	2025-12-13 14:02:30.694	error	Failed to process undefined on robot undefined (unknown device model): TypeError: Cannot read properties of null (reading 'rrHomeId') at http_api.getHomeID (/opt/iobroker/node_modules/iobroker.roborock/lib/http_api.js:111:31) at processTicksAndRejections (node:internal/process/task_queues:95:5) at http_api.updateHomeData (/opt/iobroker/node_modules/iobroker.roborock/lib/http_api.js:123:19) at http_api.init (/opt/iobroker/node_modules/iobroker.roborock/lib/http_api.js:33:3) at Roborock.onReady (/opt/iobroker/node_modules/iobroker.roborock/main.js:55:3)
roborock.0
	2025-12-13 13:57:44.393	error	Error: this.homeData is not initialized. Initialize via getHomeData() first at http_api.getDevices (/opt/iobroker/node_modules/iobroker.roborock/lib/http_api.js:179:10) at Roborock.onReady (/opt/iobroker/node_modules/iobroker.roborock/main.js:62:39)
roborock.0
	2025-12-13 13:57:44.393	error	unhandled promise rejection: this.homeData is not initialized. Initialize via getHomeData() first
roborock.0
	2025-12-13 13:57:44.393	error	this.homeData is not initialized. Initialize via getHomeData() first
roborock.0
	2025-12-13 13:57:44.392	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().

[Farmer-cb]

@m0skit0 Servus
wie bekommst du die 6.1.9??? oder meinst du die 6.1.19

ich hab aktuell die 6.1.19 von der Katze installiert, aber leider kommen da nur lauter fehlermeldungen

roborock.0
2025-12-15 10:07:15.160	error	Failed to process mainUpdateInterval on robot fRMCrYpa9LRnjbgdhxPqf (roborock.vacuum.a101): Error: this.get_status is not initialized. Request get_status first. at requests_handler.isCleaning (/opt/iobroker/node_modules/iobroker.roborock/lib/requests_handler.js:611:10) at /opt/iobroker/node_modules/iobroker.roborock/main.js:117:48 at Timeout._onTimeout (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/src/lib/adapter/adapter.ts:2800:38) at listOnTimeout (node:internal/timers:581:17) at processTimers (node:internal/timers:519:7)

roborock.0
2025-12-15 10:07:14.159	error	Failed to process mainUpdateInterval on robot fRMCrYpa9LRnjbgdhxPqf (roborock.vacuum.a101): Error: this.get_status is not initialized. Request get_status first. at requests_handler.isCleaning (/opt/iobroker/node_modules/iobroker.roborock/lib/requests_handler.js:611:10) at /opt/iobroker/node_modules/iobroker.roborock/main.js:117:48 at Timeout._onTimeout (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/src/lib/adapter/adapter.ts:2800:38) at listOnTimeout (node:internal/timers:581:17) at processTimers (node:internal/timers:519:7)

roborock.0
2025-12-15 10:07:13.159	error	Failed to process mainUpdateInterval on robot fRMCrYpa9LRnjbgdhxPqf (roborock.vacuum.a101): Error: this.get_status is not initialized. Request get_status first. at requests_handler.isCleaning (/opt/iobroker/node_modules/iobroker.roborock/lib/requests_handler.js:611:10) at /opt/iobroker/node_modules/iobroker.roborock/main.js:117:48 at Timeout._onTimeout (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/src/lib/adapter/adapter.ts:2800:38) at listOnTimeout (node:internal/timers:581:17) at processTimers (node:internal/timers:519:7)

roborock.0
2025-12-15 10:04:56.142	error	Failed to process mainUpdateInterval on robot fRMCrYpa9LRnjbgdhxPqf (roborock.vacuum.a101): Error: this.get_status is not initialized. Request get_status first. at requests_handler.isCleaning (/opt/iobroker/node_modules/iobroker.roborock/lib/requests_handler.js:611:10) at /opt/iobroker/node_modules/iobroker.roborock/main.js:117:48 at Timeout._onTimeout (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/src/lib/adapter/adapter.ts:2800:38) at listOnTimeout (node:internal/timers:581:17) at processTimers (node:internal/timers:519:7)

roborock.0
2025-12-15 10:04:55.142	error	Failed to process mainUpdateInterval on robot fRMCrYpa9LRnjbgdhxPqf (roborock.vacuum.a101): Error: this.get_status is not initialized. Request get_status first. at requests_handler.isCleaning (/opt/iobroker/node_modules/iobroker.roborock/lib/requests_handler.js:611:10) at /opt/iobroker/node_modules/iobroker.roborock/main.js:117:48 at Timeout._onTimeout (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/src/lib/adapter/adapter.ts:2800:38) at listOnTimeout (node:internal/timers:581:17) at processTimers (node:internal/timers:519:7)

[Thomas Braun]

@Farmer-cb sagte in Neuer Adapter für Roborock-Staubsauger:

von der Katze installiert

Macht man ja auch nicht. Man installiert aus einem Repository, nicht über 'die räudige Katze'.

[breaksrmine]

Ich bekomme es einfach nicht zum laufen node.js v22.21.0
iobroker auf dem neuesten image und up2date
ADapter über beta kanal 0.6.19 oder auch direkt über benutzerdefiniert von github direkt installiert als 0.6.19+refs/ta
Ob ich mich mit Passwort, falschem Passwort oder gar keinem Passwort anmelde das kommt immer in den Logs.
Unter Objects erscheint auch nur connection sonst nichts. Email kommt auch kein 2fa Code.

Kann mir einer erklären was ich tun kann ? Der Adapter wirft 3x Login aus dann wird er beendet

[Thomas Braun]

@breaksrmine

Bitte keine Screenshits des Logs...

Der Adapter meldet sich bei mir so (bei falschem PW):

2025-12-15 22:21:28.642  - info: roborock.0 (463023) starting. Version 0.6.19 in /opt/iobroker/node_modules/iobroker.roborock, node: v25.2.0, js-controller: 7.1.0
2025-12-15 22:21:28.680  - info: roborock.0 (463023) Starting adapter. This might take a few minutes depending on your setup. Please wait.
2025-12-15 22:21:28.721  - warn: roborock.0 (463023) State "roborock.0.clientID" has no existing object, this might lead to an error in future versions
2025-12-15 22:21:28.769  - info: roborock.0 (463023) Generated and saved new clientID: 65caac58-208c-45da-b56f-5836466412bc
2025-12-15 22:21:28.979  - error: roborock.0 (463023) Error in getUserData: Login returned empty userdata.. This is most likely due to too many reconnects. Emptying UserData & HomeData
2025-12-15 22:21:28.984  - warn: roborock.0 (463023) State "roborock.0.HomeData" has no existing object, this might lead to an error in future versions
2025-12-15 22:21:29.031  - warn: roborock.0 (463023) State "roborock.0.UserData" has no existing object, this might lead to an error in future versions
2025-12-15 22:21:29.082  - error: roborock.0 (463023) Failed to process undefined on robot undefined (unknown device model): Error: Login returned empty userdata.
    at http_api.initializeRealApi (/opt/iobroker/node_modules/iobroker.roborock/lib/http_api.js:64:12)
    at processTicksAndRejections (node:internal/process/task_queues:103:5)
    at http_api.init (/opt/iobroker/node_modules/iobroker.roborock/lib/http_api.js:32:3)
    at Roborock.onReady (/opt/iobroker/node_modules/iobroker.roborock/main.js:55:3)
2025-12-15 22:21:29.153  - error: roborock.0 (463023) 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().
2025-12-15 22:21:29.154  - error: roborock.0 (463023) unhandled promise rejection: Cannot read properties of null (reading 'token')
2025-12-15 22:21:29.155  - error: roborock.0 (463023) TypeError: Cannot read properties of null (reading 'token')
    at http_api.initializeRealApi (/opt/iobroker/node_modules/iobroker.roborock/lib/http_api.js:78:22)
    at processTicksAndRejections (node:internal/process/task_queues:103:5)
    at http_api.init (/opt/iobroker/node_modules/iobroker.roborock/lib/http_api.js:32:3)
    at Roborock.onReady (/opt/iobroker/node_modules/iobroker.roborock/main.js:55:3)
2025-12-15 22:21:29.155  - error: roborock.0 (463023) Cannot read properties of null (reading 'token')
2025-12-15 22:21:29.168  - info: roborock.0 (463023) terminating
2025-12-15 22:21:29.171  - warn: roborock.0 (463023) Terminated (UNCAUGHT_EXCEPTION): Without reason
2025-12-15 22:21:29.671  - info: roborock.0 (463023) terminating
2025-12-15 22:21:29.672  - info: roborock.0 (463023) terminating
2025-12-15 22:21:29.813  - error: host.chet Caught by controller[0]: 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(). The promise rejected with the reason:
2025-12-15 22:21:29.817  - error: host.chet Caught by controller[0]: TypeError: Cannot read properties of null (reading 'token')
2025-12-15 22:21:29.818  - error: host.chet Caught by controller[0]:     at http_api.initializeRealApi (/opt/iobroker/node_modules/iobroker.roborock/lib/http_api.js:78:22)
2025-12-15 22:21:29.819  - error: host.chet Caught by controller[0]:     at processTicksAndRejections (node:internal/process/task_queues:103:5)
2025-12-15 22:21:29.819  - error: host.chet Caught by controller[0]:     at http_api.init (/opt/iobroker/node_modules/iobroker.roborock/lib/http_api.js:32:3)
2025-12-15 22:21:29.821  - error: host.chet Caught by controller[0]:     at Roborock.onReady (/opt/iobroker/node_modules/iobroker.roborock/main.js:55:3)
2025-12-15 22:21:29.821  - error: host.chet instance system.adapter.roborock.0 terminated with code 6 (UNCAUGHT_EXCEPTION)
2025-12-15 22:22:07.036  - info: roborock.0 (463045) starting. Version 0.6.19 in /opt/iobroker/node_modules/iobroker.roborock, node: v25.2.0, js-controller: 7.1.0
2025-12-15 22:22:07.077  - info: roborock.0 (463045) Starting adapter. This might take a few minutes depending on your setup. Please wait.
2025-12-15 22:22:07.115  - info: roborock.0 (463045) Loaded existing clientID: 65caac58-208c-45da-b56f-5836466412bc
2025-12-15 22:22:07.540  - error: roborock.0 (463045) Error in getUserData: Login returned empty userdata.. This is most likely due to too many reconnects. Emptying UserData & HomeData
2025-12-15 22:22:07.547  - warn: roborock.0 (463045) State "roborock.0.HomeData" has no existing object, this might lead to an error in future versions
2025-12-15 22:22:07.595  - warn: roborock.0 (463045) State "roborock.0.UserData" has no existing object, this might lead to an error in future versions
2025-12-15 22:22:07.647  - error: roborock.0 (463045) Failed to process undefined on robot undefined (unknown device model): Error: Login returned empty userdata.
    at http_api.initializeRealApi (/opt/iobroker/node_modules/iobroker.roborock/lib/http_api.js:64:12)
    at processTicksAndRejections (node:internal/process/task_queues:103:5)
    at http_api.init (/opt/iobroker/node_modules/iobroker.roborock/lib/http_api.js:32:3)
    at Roborock.onReady (/opt/iobroker/node_modules/iobroker.roborock/main.js:55:3)
2025-12-15 22:22:07.718  - error: roborock.0 (463045) 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().
2025-12-15 22:22:07.718  - error: roborock.0 (463045) unhandled promise rejection: Cannot read properties of null (reading 'token')
2025-12-15 22:22:07.720  - error: roborock.0 (463045) TypeError: Cannot read properties of null (reading 'token')
    at http_api.initializeRealApi (/opt/iobroker/node_modules/iobroker.roborock/lib/http_api.js:78:22)
    at processTicksAndRejections (node:internal/process/task_queues:103:5)
    at http_api.init (/opt/iobroker/node_modules/iobroker.roborock/lib/http_api.js:32:3)
    at Roborock.onReady (/opt/iobroker/node_modules/iobroker.roborock/main.js:55:3)
2025-12-15 22:22:07.720  - error: roborock.0 (463045) Cannot read properties of null (reading 'token')
2025-12-15 22:22:07.736  - info: roborock.0 (463045) terminating
2025-12-15 22:22:07.739  - warn: roborock.0 (463045) Terminated (UNCAUGHT_EXCEPTION): Without reason
2025-12-15 22:22:08.239  - info: roborock.0 (463045) terminating
2025-12-15 22:22:08.240  - info: roborock.0 (463045) terminating
2025-12-15 22:22:08.378  - error: host.chet Caught by controller[0]: 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(). The promise rejected with the reason:
2025-12-15 22:22:08.379  - error: host.chet Caught by controller[0]: TypeError: Cannot read properties of null (reading 'token')
2025-12-15 22:22:08.380  - error: host.chet Caught by controller[0]:     at http_api.initializeRealApi (/opt/iobroker/node_modules/iobroker.roborock/lib/http_api.js:78:22)
2025-12-15 22:22:08.381  - error: host.chet Caught by controller[0]:     at processTicksAndRejections (node:internal/process/task_queues:103:5)
2025-12-15 22:22:08.382  - error: host.chet Caught by controller[0]:     at http_api.init (/opt/iobroker/node_modules/iobroker.roborock/lib/http_api.js:32:3)
2025-12-15 22:22:08.382  - error: host.chet Caught by controller[0]:     at Roborock.onReady (/opt/iobroker/node_modules/iobroker.roborock/main.js:55:3)
2025-12-15 22:22:08.382  - error: host.chet instance system.adapter.roborock.0 terminated with code 6 (UNCAUGHT_EXCEPTION)
2025-12-15 22:22:45.771  - info: roborock.0 (463112) starting. Version 0.6.19 in /opt/iobroker/node_modules/iobroker.roborock, node: v25.2.0, js-controller: 7.1.0
2025-12-15 22:22:45.815  - info: roborock.0 (463112) Starting adapter. This might take a few minutes depending on your setup. Please wait.
2025-12-15 22:22:45.853  - info: roborock.0 (463112) Loaded existing clientID: 65caac58-208c-45da-b56f-5836466412bc
2025-12-15 22:22:46.122  - error: roborock.0 (463112) Error in getUserData: Login returned empty userdata.. This is most likely due to too many reconnects. Emptying UserData & HomeData
2025-12-15 22:22:46.131  - warn: roborock.0 (463112) State "roborock.0.HomeData" has no existing object, this might lead to an error in future versions
2025-12-15 22:22:46.179  - warn: roborock.0 (463112) State "roborock.0.UserData" has no existing object, this might lead to an error in future versions
2025-12-15 22:22:46.231  - error: roborock.0 (463112) Failed to process undefined on robot undefined (unknown device model): Error: Login returned empty userdata.
    at http_api.initializeRealApi (/opt/iobroker/node_modules/iobroker.roborock/lib/http_api.js:64:12)
    at processTicksAndRejections (node:internal/process/task_queues:103:5)
    at http_api.init (/opt/iobroker/node_modules/iobroker.roborock/lib/http_api.js:32:3)
    at Roborock.onReady (/opt/iobroker/node_modules/iobroker.roborock/main.js:55:3)
2025-12-15 22:22:46.297  - error: roborock.0 (463112) 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().
2025-12-15 22:22:46.298  - error: roborock.0 (463112) unhandled promise rejection: Cannot read properties of null (reading 'token')
2025-12-15 22:22:46.299  - error: roborock.0 (463112) TypeError: Cannot read properties of null (reading 'token')
    at http_api.initializeRealApi (/opt/iobroker/node_modules/iobroker.roborock/lib/http_api.js:78:22)
    at processTicksAndRejections (node:internal/process/task_queues:103:5)
    at http_api.init (/opt/iobroker/node_modules/iobroker.roborock/lib/http_api.js:32:3)
    at Roborock.onReady (/opt/iobroker/node_modules/iobroker.roborock/main.js:55:3)
2025-12-15 22:22:46.299  - error: roborock.0 (463112) Cannot read properties of null (reading 'token')
2025-12-15 22:22:46.313  - info: roborock.0 (463112) terminating
2025-12-15 22:22:46.316  - warn: roborock.0 (463112) Terminated (UNCAUGHT_EXCEPTION): Without reason
2025-12-15 22:22:46.815  - info: roborock.0 (463112) terminating
2025-12-15 22:22:46.816  - info: roborock.0 (463112) terminating
2025-12-15 22:22:46.958  - error: host.chet Caught by controller[0]: 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(). The promise rejected with the reason:
2025-12-15 22:22:46.959  - error: host.chet Caught by controller[0]: TypeError: Cannot read properties of null (reading 'token')
2025-12-15 22:22:46.959  - error: host.chet Caught by controller[0]:     at http_api.initializeRealApi (/opt/iobroker/node_modules/iobroker.roborock/lib/http_api.js:78:22)
2025-12-15 22:22:46.960  - error: host.chet Caught by controller[0]:     at processTicksAndRejections (node:internal/process/task_queues:103:5)
2025-12-15 22:22:46.960  - error: host.chet Caught by controller[0]:     at http_api.init (/opt/iobroker/node_modules/iobroker.roborock/lib/http_api.js:32:3)
2025-12-15 22:22:46.960  - error: host.chet Caught by controller[0]:     at Roborock.onReady (/opt/iobroker/node_modules/iobroker.roborock/main.js:55:3)
2025-12-15 22:22:46.961  - error: host.chet instance system.adapter.roborock.0 terminated with code 6 (UNCAUGHT_EXCEPTION)
2025-12-15 22:22:46.961  - warn: host.chet Do not restart adapter system.adapter.roborock.0 because restart loop detected

Mach ein Issue auf github mit deinen Meldungen/Versionen auf.

[Thomas Braun]

@breaksrmine

Bzw: Passt

https://github.com/copystring/ioBroker.roborock/issues/945

nicht zu deinem Problem?

Die momentane GitHub-Version meldet sich jedenfalls deutlich ruhiger:

2025-12-15 22:43:57.257  - info: roborock.0 (464599) starting. Version 0.6.19 (non-npm: copystring/ioBroker.roborock) in /opt/iobroker/node_modules/iobroker.roborock, node: v25.2.0, js-controller: 7.1.0
2025-12-15 22:43:57.287  - error: roborock.0 (464599) Username missing!

[RISSN]

bei mir startet der Adapter seit gestern leider nicht mehr.

host.iobroker
2025-12-16 11:14:26.279	info	"system.adapter.roborock.0" disabled

host.iobroker
2025-12-16 11:14:23.333	info	Restart adapter system.adapter.roborock.0 because enabled

host.iobroker
2025-12-16 11:14:23.333	error	instance system.adapter.roborock.0 terminated with code 6 (UNCAUGHT_EXCEPTION)

host.iobroker
2025-12-16 11:14:23.333	error	Caught by controller[1]: at Roborock.onReady (/opt/iobroker/node_modules/iobroker.roborock/main.js:62:39)

host.iobroker
2025-12-16 11:14:23.333	error	Caught by controller[1]: at http_api.getDevices (/opt/iobroker/node_modules/iobroker.roborock/lib/http_api.js:179:10)

host.iobroker
2025-12-16 11:14:23.333	error	Caught by controller[1]: Error: this.homeData is not initialized. Initialize via getHomeData() first

host.iobroker
2025-12-16 11:14:23.333	error	Caught by controller[0]: 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(). The promise rejected with the reason:

roborock.0
2025-12-16 11:14:22.843	error	Failed to process client.on('offline') on robot undefined (unknown device model): MQTT connection offline.

roborock.0
2025-12-16 11:14:22.830	error	Failed to process client.on('error') on robot undefined (unknown device model): MQTT connection error: ErrorWithReasonCode: Connection refused: Not authorized. rriot.r.m: ssl://mqtt-eu.roborock.com:8883 rriot.u: 3YRjYclWBW65jnx0HNRKoW

roborock.0
2025-12-16 11:14:22.748	error	this.homeData is not initialized. Initialize via getHomeData() first

roborock.0
2025-12-16 11:14:22.747	error	Error: this.homeData is not initialized. Initialize via getHomeData() first at http_api.getDevices (/opt/iobroker/node_modules/iobroker.roborock/lib/http_api.js:179:10) at Roborock.onReady (/opt/iobroker/node_modules/iobroker.roborock/main.js:62:39)

roborock.0
2025-12-16 11:14:22.747	error	unhandled promise rejection: this.homeData is not initialized. Initialize via getHomeData() first

roborock.0
2025-12-16 11:14:22.747	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
2025-12-16 11:14:22.594	error	Failed to process undefined on robot undefined (unknown device model): TypeError: Cannot read properties of null (reading 'rrHomeId') at http_api.getHomeID (/opt/iobroker/node_modules/iobroker.roborock/lib/http_api.js:111:31) at processTicksAndRejections (node:internal/process/task_queues:105:5) at http_api.updateHomeData (/opt/iobroker/node_modules/iobroker.roborock/lib/http_api.js:123:19) at http_api.init (/opt/iobroker/node_modules/iobroker.roborock/lib/http_api.js:33:3) at Roborock.onReady (/opt/iobroker/node_modules/iobroker.roborock/main.js:55:3)

host.iobroker
2025-12-16 11:14:21.103	info	instance system.adapter.roborock.0 in version "0.6.19" (non-npm: copystring/ioBroker.roborock#cc60bf722e8454c6a9197c162c26aae55812681b) started with pid 340819

host.iobroker
2025-12-16 11:14:20.556	info	"system.adapter.roborock.0" enabled

[Thomas Braun]

@RISSN

Offenbar wird gerade an dem Adapter gewerkelt. Der letzte Commit ist 3 Stunden alt.

[lebeART]

Hallo, jetzt komme ich mal mit einer echt doofen Frage, Ich habe einen Roborock Qrevo S5V... Roborock App läuft Gerät ist eingebunden... Alexa Steuerung klappt ebenfalls. aber mit dieser IOBROKER App kann ich mich nicht anmelden... Habe es mit EMAIL Adresse, Roborock ID und auch Benutzernamen probiert. aber bekomme keine Verbindung zum gerät.. Was mache ich falsch ? :-) Passwort stimmt :-)![Bild Text](

[Thomas Braun]

@lebeART sagte in Neuer Adapter für Roborock-Staubsauger:

Was mache ich falsch ?

Schau den 'Kaltstart' des Adapters im Log an.

iob logs --watch

[lebeART]

Dann erhalte ich 2025-12-17 00:25:12.920 - info: host.raspberrypi5 "system.adapter.roborock.0" enabled
2025-12-17 00:25:13.284 - info: host.raspberrypi5 instance system.adapter.roborock.0 in version "0.6.18" started with pid 5651
2025-12-17 00:25:15.176 - info: roborock.0 (5651) starting. Version 0.6.18 in /opt/iobroker/node_modules/iobroker.roborock, node: v20.19.6, js-controller: 7.0.7
2025-12-17 00:25:15.186 - info: roborock.0 (5651) Starting adapter. This might take a few minutes depending on your setup. Please wait.
2025-12-17 00:25:15.602 - error: roborock.0 (5651) Error in getUserData: Login returned empty userdata.. This is most likely due to too many reconnects.
2025-12-17 00:25:15.611 - error: roborock.0 (5651) Error retrieving or setting clientID: Error: Login returned empty userdata.
at Roborock.getUserData (/opt/iobroker/node_modules/iobroker.roborock/main.js:236:11)
at processTicksAndRejections (node:internal/process/task_queues:95:5)
at Roborock.initializeRoborockApi (/opt/iobroker/node_modules/iobroker.roborock/main.js:103:21)
at Roborock.onReady (/opt/iobroker/node_modules/iobroker.roborock/main.js:65:34)
2025-12-17 00:25:15.788 - info: tuya.0 (2997) bf9f48824c14c6677ec5va: Error on Reconnect (5): connect EHOSTUNREACH 192.168.178.46:6668
2025-12-17 00:25:16.036 - error: roborock.0 (5651) Failed to get home details: Error: loginApi is not initialized.
at Roborock.initializeHomeDetails (/opt/iobroker/node_modules/iobroker.roborock/main.js:144:25)
at Roborock.onReady (/opt/iobroker/node_modules/iobroker.roborock/main.js:67:14)
2025-12-17 00:25:56.764 - info: admin.0 (2857) Adapter rating updated