Neuer Blogbeitrag: Monatsrückblick - Dezember 2025 🎄

[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

[Thomas Braun]

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

node: v20.19.6

Bring es auf nodejs v22...

iob nodejs-update

Fertig.

[copystring]

Es gibt aktuell keinen funktionierenden Release. Wer mag, kann https://github.com/copystring/ioBroker.roborock über die GitHub Katze in ioBroker installieren und testen. Bugs aber nicht hier posten, sondern als Issue auf GitHub. Danke!

[breaksrmine]

Bei mir kommt über die katze schon beim start der Fehler

startInstance system.adapter.roborock.0 Adapter dependency not fulfilled on "d7b9f08fe3af": required adapter "web" not found!

roborock 0.6.19
node v22

[ste_glei]

@copystring

gerade das Release über GitHub installiert und funktioniert mit S8 Pro Ultra und Saros 10.
Ich musste aber den Adapter komplett löschen und neu installieren.

Danke für die Bemühungen!

[RISSN]

bei mir geht es nicht, muss ich mir hier irgendwie einen neuen Token besorgen?

roborock.0
2025-12-17 09:54:32.386	error	MQTT connection error: Connection refused: Not authorized. Broker: ssl://mqtt-eu.roborock.com:8883

roborock.0
2025-12-17 09:54:32.299	error	No homeId found

roborock.0
2025-12-17 09:54:32.245	error	failed to get getHomeDetail: invalid token

[Thomas Braun]

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

required adapter "web" not found!

Ist der web-Adapter installiert und läuft?

[breaksrmine]

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

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

required adapter "web" not found!

Ist der web-Adapter installiert und läuft?

woher bekomme ich diesen ? bzw. wie muss dieser installiert werden ?

[breaksrmine]

sagte in Neuer Adapter für Roborock-Staubsauger:

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

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

required adapter "web" not found!

Ist der web-Adapter installiert und läuft?

woher bekomme ich diesen ? bzw. wie muss dieser installiert werden ?

sry bin kein profi

[Thomas Braun]

@breaksrmine

Gib mal die Ausgabe von

iob diag

zum Besten. Da kann man das (neben anderen Dingen) sehen.

[breaksrmine]

========== Start marking the full check here ===========

Script v.2025-08-09

*** BASE SYSTEM ***
Hardware Vendor : Synology Inc.
Kernel          : x86_64
Userland        : 64 bit
Docker          : v11.0.0
Virtualization  : docker
Kernel          : x86_64
Userland        : 64 bit

Systemuptime and Load:
 12:35:12 up 4 days, 15:49,  0 user,  load average: 1.03, 0.68, 0.52
CPU threads: 4


*** LIFE CYCLE STATUS ***
Debian 'bookworm' is the current oldstable version. Please upgrade to the latest stable release 'trixie' in due time!

*** TIME AND TIMEZONES ***
Wed Dec 17 11:35:12 UTC 2025
Wed Dec 17 12:35:12 CET 2025
CET +0100
Etc/UTC

*** Users and Groups ***
User that called 'iob diag':
root
HOME=/root
GROUPS=root

User that is running 'js-controller':
iobroker
HOME=/opt/iobroker
GROUPS=iobroker tty dialout audio video plugdev

*** DISPLAY-SERVER SETUP ***
Display-Server:         false
System has not been booted with systemd as init system (PID 1). Can't operate.
Failed to connect to bus: Host is down
Display-Manager: 
Desktop: 
Session: 

*** MEMORY ***
               total        used        free      shared  buff/cache   available
Mem:             33G         17G        1.3G         10G         29G         16G
Swap:           2.1G        382M        1.8G
Total:           35G         17G        3.1G

Active iob-Instances:   12

        32072 M total memory
        16656 M used memory
         2328 M active memory
        16246 M inactive memory
         1257 M free memory
          596 M buffer memory
        27204 M swap cache
         2047 M total swap
          364 M used swap
         1683 M free swap

*** top - Table Of Processes  ***
top - 12:35:13 up 4 days, 15:49,  0 user,  load average: 1.03, 0.68, 0.52
Tasks:  20 total,   1 running,  19 sleeping,   0 stopped,   0 zombie
%Cpu(s):  0.0 us,  0.0 sy,  0.0 ni,100.0 id,  0.0 wa,  0.0 hi,  0.0 si,  0.0 st 
MiB Mem :  32072.3 total,   1256.0 free,  16658.6 used,  27801.6 buff/cache     
MiB Swap:   2047.9 total,   1683.6 free,    364.3 used.  15413.7 avail Mem 


*** DMESG CRITICAL ERRORS ***
No critical errors detected

*** FILESYSTEM ***
Filesystem             Type   Size  Used Avail Use% Mounted on
/dev/mapper/cachedev_0 btrfs  885G  179G  706G  21% /
tmpfs                  tmpfs   64M     0   64M   0% /dev
tmpfs                  tmpfs   16G     0   16G   0% /sys/fs/cgroup
shm                    tmpfs   64M     0   64M   0% /dev/shm
/dev/mapper/cachedev_0 btrfs  885G  179G  706G  21% /opt/iobroker
/dev/mapper/cachedev_0 btrfs  885G  179G  706G  21% /etc/hosts
tmpfs                  tmpfs   16G     0   16G   0% /proc/acpi
tmpfs                  tmpfs   16G     0   16G   0% /proc/scsi
tmpfs                  tmpfs   16G     0   16G   0% /sys/firmware

Messages concerning ext4 filesystem in dmesg:
[Fri Dec 12 20:46:47 2025] EXT4-fs (md0): couldn't mount as ext3 due to feature incompatibilities
[Fri Dec 12 20:46:47 2025] EXT4-fs (md0): mounted filesystem with ordered data mode. Opts: (null)
[Fri Dec 12 20:46:47 2025] EXT4-fs (md0): couldn't mount as ext3 due to feature incompatibilities
[Fri Dec 12 20:46:47 2025] EXT4-fs (md0): mounted filesystem with ordered data mode. Opts: prjquota,rootprjquota,barrier=1
[Fri Dec 12 20:46:47 2025] EXT4-fs (sata4p2): couldn't mount as ext3 due to feature incompatibilities
[Fri Dec 12 20:46:47 2025] EXT4-fs (sata4p2): mounted filesystem with ordered data mode. Opts: (null)
[Fri Dec 12 20:47:30 2025] EXT4-fs (md0): couldn't mount as ext3 due to feature incompatibilities
[Fri Dec 12 20:47:30 2025] EXT4-fs (md0): mounted filesystem with ordered data mode. Opts: (null)
[Fri Dec 12 20:47:31 2025] EXT4-fs (md0): couldn't mount as ext3 due to feature incompatibilities
[Fri Dec 12 20:47:31 2025] EXT4-fs (md0): mounted filesystem with ordered data mode. Opts: prjquota,rootprjquota,barrier=1
[Fri Dec 12 20:47:47 2025] EXT4-fs (dm-7): mounted filesystem with ordered data mode. Opts: usrjquota=aquota.user,grpjquota=aquota.group,jqfmt=vfsv0,synoacl
[Fri Dec 12 20:48:18 2025] EXT4-fs (loop0): mounted filesystem with ordered data mode. Opts: (null)
[Fri Dec 12 20:48:19 2025] ext4: synoboot1 mounted, process=syno_bios_log_c
[Fri Dec 12 20:49:05 2025] EXT4-fs (iscsi2): mounted filesystem with ordered data mode. Opts: (null)

Show mounted filesystems:
TARGET             SOURCE                                                                                                                         FSTYPE OPTIONS
/                  /dev/mapper/cachedev_0[/@syno/@docker/btrfs/subvolumes/82a6d3a2c890980107852312625dbf5eaef62247d8bdd021eebba4782f925861]       btrfs  rw,nodev,noatime,ssd,synoacl,space_cache=v2,auto_reclaim_space,metadata_ratio=50,block_group_cache_tree,syno_allocator,subvolid=1509,subvol=/@syno/@docker/btrfs/subvolumes/82a6d3a2c890980107852312625dbf5eaef62247d8bdd021eebba4782f925861
|-/opt/iobroker    /dev/mapper/cachedev_0[/@syno/docker/iobroker]                                                                                 btrfs  rw,nodev,noatime,ssd,synoacl,space_cache=v2,auto_reclaim_space,metadata_ratio=50,block_group_cache_tree,syno_allocator,subvolid=330,subvol=/@syno/docker
|-/etc/resolv.conf /dev/mapper/cachedev_0[/@syno/@docker/containers/b4082afc1ac9497e5c970e6bd491e53c93ac49c1791a99f3e8d5925170e5ccb8/resolv.conf] btrfs  rw,nodev,noatime,ssd,synoacl,space_cache=v2,auto_reclaim_space,metadata_ratio=50,block_group_cache_tree,syno_allocator,subvolid=256,subvol=/@syno
|-/etc/hostname    /dev/mapper/cachedev_0[/@syno/@docker/containers/b4082afc1ac9497e5c970e6bd491e53c93ac49c1791a99f3e8d5925170e5ccb8/hostname]    btrfs  rw,nodev,noatime,ssd,synoacl,space_cache=v2,auto_reclaim_space,metadata_ratio=50,block_group_cache_tree,syno_allocator,subvolid=256,subvol=/@syno
`-/etc/hosts       /dev/mapper/cachedev_0[/@syno/@docker/containers/b4082afc1ac9497e5c970e6bd491e53c93ac49c1791a99f3e8d5925170e5ccb8/hosts]       btrfs  rw,nodev,noatime,ssd,synoacl,space_cache=v2,auto_reclaim_space,metadata_ratio=50,block_group_cache_tree,syno_allocator,subvolid=256,subvol=/@syno

Files in neuralgic directories:

/var:
16M     /var/
14M     /var/lib/dpkg
14M     /var/lib
13M     /var/lib/dpkg/info
1.9M    /var/cache


/opt/iobroker/backups:
316M    /opt/iobroker/backups/

/opt/iobroker/iobroker-data:
243M    /opt/iobroker/iobroker-data/
129M    /opt/iobroker/iobroker-data/backup-objects
93M     /opt/iobroker/iobroker-data/files
47M     /opt/iobroker/iobroker-data/files/admin.admin
46M     /opt/iobroker/iobroker-data/files/admin.admin/custom/assets

The five largest files in iobroker-data are:
16M     /opt/iobroker/iobroker-data/objects.jsonl
15M     /opt/iobroker/iobroker-data/backup-objects/2025-12-15_12-49_states.jsonl.gz
15M     /opt/iobroker/iobroker-data/backup-objects/2025-12-15_10-49_states.jsonl.gz
8.1M    /opt/iobroker/iobroker-data/files/backitup.admin/assets/index-C_W7K-9p.js
4.7M    /opt/iobroker/iobroker-data/states.jsonl

USB-Devices by-id:
USB-Sticks -  Avoid direct links to /dev/tty* in your adapter setups, please always prefer the links 'by-id':

No Devices found 'by-id'

Zigbee Network Settings on your coordinator/in nvbackup are:

zigbee.X
Extended Pan ID:
*** MASKED ***
Pan ID:
*** MASKED ***
Channel:
*** MASKED ***
Network Key:
*** MASKED ***

To unmask the settings run 'iob diag --unmask'


*** NodeJS-Installation ***

/usr/bin/nodejs         v22.21.0
/usr/bin/node           v22.21.0
/usr/bin/npm            10.9.4
/usr/bin/npx            10.9.4
/usr/bin/corepack       0.34.0

nodejs:
  Installed: 22.21.0-1nodesource1
  Candidate: 22.21.0-1nodesource1
  Version table:
 *** 22.21.0-1nodesource1 100
        100 /var/lib/dpkg/status

Temp directories causing deletion problem: 0
No problems detected

Errors in npm tree: 0
No problems detected

Checking for nodejs vulnerability:


 █████  ██      ██           ██████   ██████   ██████  ██████         ██
██   ██ ██      ██          ██       ██    ██ ██    ██ ██   ██     ██  ██
███████ ██      ██          ██   ███ ██    ██ ██    ██ ██   ██         ██
██   ██ ██      ██          ██    ██ ██    ██ ██    ██ ██   ██     ██  ██
██   ██ ███████ ███████      ██████   ██████   ██████  ██████         ██



*** ioBroker-Installation ***

ioBroker Status
iobroker is running on this host.


Objects type: jsonl
States  type: jsonl

Hosts:
d7b9f08fe3af        d7b9f08fe3af (version: 7.0.7, hostname: d7b9f08fe3af  , alive, uptime: 43038)

Core adapters versions
js-controller:  7.0.7
admin:          7.7.19
javascript:     9.0.11

nodejs modules from github:     1
+-- iobroker.roborock@0.6.19 (git+ssh://git@github.com/copystring/ioBroker.roborock.git#521621b88729012446785ec3c8248501a560eb53)

Adapter State
+ system.adapter.admin.0                  : admin                 : d7b9f08fe3af                             -  enabled, port: 8081, bind: 0.0.0.0, run as: admin
+ system.adapter.admin.1                  : admin                 : d7b9f08fe3af                             -  enabled, port: 8443, bind: 0.0.0.0 (SSL), run as: admin
+ system.adapter.backitup.0               : backitup              : d7b9f08fe3af                             -  enabled
+ system.adapter.daikin-cloud.0           : daikin-cloud          : d7b9f08fe3af                             -  enabled
  system.adapter.dwd.0                    : dwd                   : d7b9f08fe3af                             -  enabled
+ system.adapter.javascript.0             : javascript            : d7b9f08fe3af                             -  enabled
  system.adapter.linktap.0                : linktap               : d7b9f08fe3af                             - disabled
+ system.adapter.mielecloudservice.0      : mielecloudservice     : d7b9f08fe3af                             -  enabled
+ system.adapter.mqtt.0                   : mqtt                  : d7b9f08fe3af                             -  enabled, port: 11111, bind: 0.0.0.0
+ system.adapter.openweathermap.0         : openweathermap        : d7b9f08fe3af                             -  enabled
+ system.adapter.philips-tv.0             : philips-tv            : d7b9f08fe3af                             -  enabled
+ system.adapter.plenticore.0             : plenticore            : d7b9f08fe3af                             -  enabled, port: 80
  system.adapter.roborock.0               : roborock              : d7b9f08fe3af                             -  enabled
+ system.adapter.simple-api.0             : simple-api            : d7b9f08fe3af                             -  enabled, port: 8087, bind: 0.0.0.0, run as: admin
  system.adapter.weatherunderground.0     : weatherunderground    : d7b9f08fe3af                             -  enabled

+ instance is alive

Enabled adapters with bindings
+ system.adapter.admin.0                  : admin                 : d7b9f08fe3af                             -  enabled, port: 8081, bind: 0.0.0.0, run as: admin
+ system.adapter.admin.1                  : admin                 : d7b9f08fe3af                             -  enabled, port: 8443, bind: 0.0.0.0 (SSL), run as: admin
+ system.adapter.mqtt.0                   : mqtt                  : d7b9f08fe3af                             -  enabled, port: 11111, bind: 0.0.0.0
+ system.adapter.plenticore.0             : plenticore            : d7b9f08fe3af                             -  enabled, port: 80
+ system.adapter.simple-api.0             : simple-api            : d7b9f08fe3af                             -  enabled, port: 8087, bind: 0.0.0.0, run as: admin

ioBroker-Repositories
┌─────────┬──────────┬─────────────────────────────────────────────────────────┬──────────────┐
│ (index) │ name     │ url                                                     │ auto upgrade │
├─────────┼──────────┼─────────────────────────────────────────────────────────┼──────────────┤
│ 0       │ 'stable' │ 'http://download.iobroker.net/sources-dist.json'        │ true         │
│ 1       │ 'beta'   │ 'http://download.iobroker.net/sources-dist-latest.json' │ false        │
│ 2       │ '__'     │ ''                                                      │ false        │
└─────────┴──────────┴─────────────────────────────────────────────────────────┴──────────────┘

Active repo(s): stable
Upgrade policy: minor

Installed ioBroker-Adapters
Used repository: stable
Adapter    "admin"        : 7.7.19   , installed 7.7.19
Adapter    "backitup"     : 3.3.10   , installed 3.3.10
Adapter    "daikin-cloud" : 0.4.12   , installed 0.4.12
Adapter    "dwd"          : 2.8.5    , installed 2.8.5
Adapter    "javascript"   : 9.0.11   , installed 9.0.11
Controller "js-controller": 7.0.7    , installed 7.0.7
Adapter    "linktap"      : 1.0.3    , installed 1.0.3
Adapter    "mielecloudservice": 6.5.10, installed 6.5.10
Adapter    "mqtt"         : 6.1.4    , installed 6.1.4
Adapter    "openweathermap": 1.1.2   , installed 1.1.2
Adapter    "philips-tv"   : 0.5.4    , installed 0.5.4
Adapter    "plenticore"   : 2.2.0    , installed 2.3.1
Adapter    "roborock"     : 0.6.18   , installed 0.6.19
Adapter    "simple-api"   : 2.8.0    , installed 2.8.0
Adapter    "weatherunderground": 3.7.0, installed 3.7.0

Objects and States
Please stand by - This may take a while
Objects:        3621
States:         3266

*** OS-Repositories and Updates ***
Hit:1 http://deb.debian.org/debian bookworm InRelease
Hit:2 http://deb.debian.org/debian bookworm-updates InRelease
Hit:3 http://deb.debian.org/debian-security bookworm-security InRelease
Hit:4 https://deb.nodesource.com/node_22.x nodistro InRelease
Reading package lists...
Pending Updates: 0

[Thomas Braun]

@breaksrmine

Mit Docker kenn ich mich zwar nicht aus, da gibt es einige 'komische' Meldungen.

Der web-Adapter fehlt aber in der Tat.
Installier den halt nach. Geht wie bei jedem anderen Adapter auch.

[breaksrmine]

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

@breaksrmine

Mit Docker kenn ich mich zwar nicht aus, da gibt es einige 'komische' Meldungen.

Der web-Adapter fehlt aber in der Tat.
Installier den halt nach. Geht wie bei jedem anderen Adapter auch.

das problem das wollte ich schon machen aber über suche im reposi gibt es keinen web adapter