NEWS
Neuer Adapter für Roborock-Staubsauger
-
@frederik-buss danke. Freut mich, dass es so läuft wie du dir das vorgestellt hast.
-
Hi, seit dem letzten Roborock Update für meinen Qrevo Curv kann der Adapter sich nicht mehr verbinden. Ich mache gleich noch ein Issue auf Github auf.
Failed to process undefined on robot undefined (unknown device model): Failed to process message: Error: error:1C80006B:Provider routines::wrong final block length at Decipheriv.final (node:internal/crypto/cipher:193:29) at local_api.decryptECB (/opt/iobroker/node_modules/iobroker.roborock/lib/local_api.js:248:25) at Socket.handleMessage (/opt/iobroker/node_modules/iobroker.roborock/lib/local_api.js:199:34) at Socket.emit (node:events:524:28) at Socket.emit (node:domain:489:12) at UDP.onMessage (node:dgram:951:8) Failed to process mainUpdateInterval on robot InAokiWwEHHT4hwBeMGFU (roborock.vacuum.a135): 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:2751:38) at listOnTimeout (node:internal/timers:581:17) at processTimers (node:internal/timers:519:7)
-
Hallo zusammen,
ich habe den Adapter jetzt eine Weile mit dem Saros 10R laufen und er funktioniert zwar, stürzt aber häufig ab und ist dann bis zum Neustart nicht ansprechbar
Das hier sind die Fehlermeldungen:setTimeout called, but adapter is shutting down Failed to process "get_clean_summary" on robot vArM2m3ap0E3f7dsbZWNX (roborock.vacuum.a144): Error: Could not check object existence of roborock.0.Devices.vArM2m3ap0E3f7dsbZWNX.cleaningInfo.records.10.dust_collection_status: Cannot check object existence of "roborock.0.Devices.vArM2m3ap0E3f7dsbZWNX.cleaningInfo.records.10.dust_collection_status": Connection is closed. at Object.maybeCallbackWithError (/opt/iobroker/node_modules/@iobroker/js-controller-common-db/src/lib/common/maybeCallback.ts:129:17) at Roborock._setObjectNotExists (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/src/lib/adapter/adapter.ts:5017:26) at /opt/iobroker/node_modules/@iobroker/js-controller-common-db/src/lib/common/tools.ts:2336:17 Could not check object existence of roborock.0.Devices.vArM2m3ap0E3f7dsbZWNX.cleaningInfo.records.10: Cannot check object existence of "roborock.0.Devices.vArM2m3ap0E3f7dsbZWNX.cleaningInfo.records.10": Connection is closed. Could not check object existence of roborock.0.Devices.vArM2m3ap0E3f7dsbZWNX.cleaningInfo.records.10: Cannot check object existence of "roborock.0.Devices.vArM2m3ap0E3f7dsbZWNX.cleaningInfo.records.10": Connection is closed. at Object.maybeCallbackWithError (/opt/iobroker/node_modules/@iobroker/js-controller-common-db/src/lib/common/maybeCallback.ts:129:17) at Roborock._setObjectNotExists (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/src/lib/adapter/adapter.ts:5017:26) at runNextTicks (node:internal/process/task_queues:60:5) at processImmediate (node:internal/timers:454:9) at /opt/iobroker/node_modules/@iobroker/js-controller-common-db/src/lib/common/tools.ts:2336:17 unhandled promise rejection: Could not check object existence of roborock.0.Devices.vArM2m3ap0E3f7dsbZWNX.cleaningInfo.records.10: Cannot check object existence of "roborock.0.Devices.vArM2m3ap0E3f7dsbZWNX.cleaningInfo.records.10": Connection is closed. 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(). Cannot check object existence of "roborock.0.Devices.vArM2m3ap0E3f7dsbZWNX.cleaningInfo.records.10.dust_collection_status": Connection is closed. get state error: Connection is closed. redis get roborock.0.Devices.vArM2m3ap0E3f7dsbZWNX.cleaningInfo.records.10.clean_type, error - Connection is closed. setTimeout called, but adapter is shutting down
Ich weiß nicht, ob ich das mit dem Einfügen der Fehlermeldungen richtig gemacht habe. Ich bitte um Nachsicht. Auch weiß ich leider nicht ob und wie ich ein Issue auf Github aufmachen sollte.
Viele Grüße!
-
Immer erstmal auf GitHub nach schauen, ob jemand das gleiche Problem hat. Falls nicht, einfach ein GitHub Issue aufmachen. Ich schaue es mir dann an.
-
Hallo ich habe aktuell diesen Fehler. Kann mir einer verraten woran es liegt?
2025-07-26 17:58:52.423 - info: host.iobroker instance system.adapter.roborock.0 in version "0.6.19" (non-npm: copystring/ioBroker.roborock#769dee8a000aa78ecdcb826185abcafc1aada5d5) started with pid 2115372 2025-07-26 17:58:56.781 - info: roborock.0 (2115372) starting. Version 0.6.19 (non-npm: copystring/ioBroker.roborock#769dee8a000aa78ecdcb826185abcafc1aada5d5) in /opt/iobroker/node_modules/iobroker.roborock, node: v20.18.0, js-controller: 7.0.6 2025-07-26 17:58:56.799 - info: roborock.0 (2115372) Starting adapter. This might take a few minutes depending on your setup. Please wait. 2025-07-26 17:58:56.821 - info: roborock.0 (2115372) Loaded existing clientID: ee6783f4-5d0a-4d48-b00e-7cafd23b31d9 2025-07-26 17:58:57.104 - error: roborock.0 (2115372) 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) 2025-07-26 17:58:57.328 - info: roborock.0 (2115372) MQTT initialized 2025-07-26 17:58:57.329 - error: roborock.0 (2115372) 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-07-26 17:58:57.330 - error: roborock.0 (2115372) unhandled promise rejection: this.homeData is not initialized. Initialize via getHomeData() first 2025-07-26 17:58:57.330 - error: roborock.0 (2115372) 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) 2025-07-26 17:58:57.330 - error: roborock.0 (2115372) this.homeData is not initialized. Initialize via getHomeData() first 2025-07-26 17:58:57.343 - info: roborock.0 (2115372) terminating 2025-07-26 17:58:57.344 - warn: roborock.0 (2115372) Terminated (UNCAUGHT_EXCEPTION): Without reason 2025-07-26 17:58:57.402 - info: roborock.0 (2115372) MQTT connection established {"cmd":"connack","retain":false,"qos":0,"dup":false,"length":2,"topic":null,"payload":null,"sessionPresent":false,"returnCode":0}. 2025-07-26 17:58:57.845 - info: roborock.0 (2115372) terminating 2025-07-26 17:58:57.994 - error: host.iobroker 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-07-26 17:58:57.994 - error: host.iobroker Caught by controller[1]: Error: this.homeData is not initialized. Initialize via getHomeData() first 2025-07-26 17:58:57.994 - error: host.iobroker Caught by controller[1]: at http_api.getDevices (/opt/iobroker/node_modules/iobroker.roborock/lib/http_api.js:179:10) 2025-07-26 17:58:57.994 - error: host.iobroker Caught by controller[1]: at Roborock.onReady (/opt/iobroker/node_modules/iobroker.roborock/main.js:62:39) 2025-07-26 17:58:57.994 - error: host.iobroker instance system.adapter.roborock.0 terminated with code 6 (UNCAUGHT_EXCEPTION) 2025-07-26 17:58:57.994 - info: host.iobroker Restart adapter system.adapter.roborock.0 because enabled 2025-07-26 17:58:59.558 - warn: openknx.0 (1699916) Ignoring GroupValue_Write of unknown GA 9/0/4 2025-07-26 17:59:00.842 - info: host.iobroker "system.adapter.roborock.0" disabled
-
Ich möchte mich für die Arbeit an diesem Adapter bedanken.
Seit einigen Tagen sind wir auf den Saros 10R umgestiegen, vorher war der S7 MaxV im Einsatz. Dort hatte ich noch den Xiaomi-Adapter verwendet.
Mit dem Umstieg auf das neue Modell habe ich auch bei der App den Wechsel zur Roborock-Original-App vollzogen. Somit musste auch im iobroker auf den neuen Adapter gewechselt werden.Nach leichten Anfangsschwierigkeiten (keine lokale Verbindung), läuft die Geschichte jetzt mit der Version 0.6.19
Daher konnte ich heute auch im VIS die Anpassungen vornehmen, da die Steuerung doch in einigen Punkten vom bisherigen Xiaomi-Adapter abweicht.Die wesentlichen Dinge lassen sich jetzt wieder steuern bzw. ablesen, so dass auch ohne Handy der Roboter seinen Dienst verrichten kann.
Anbei noch ein Screenshot von der VIS dazu.
-
@creekhail hallo könnte ich einen Export deiner Seite haben?
-
@timowald Was genau hast du denn vor bzw. was meinst du mit "Export deiner Seite"?
-
@creekhail Export deiner Seite vom Robby. Finde diese super und würde es bei mir genauso machen wollen.
-
Hallo,
ich hab die neuste Adapter Version installiert.
Nun bleibt der Adapter dauerhaft grün.
Wenn ich auf den Instanzlink klicke und dann 8083 nehme zeigt er mit eine schwarze Seite mit einem Reckeck oben links an und mehreren Buttons.In der Zeit geht der Adapter auf Rot und in Logs kommen zig Fehlermeldungen...
Hab ich etwas falsch eingestellt im Adapter?
-
Github Issue geschlossen, da Problem nach Neuinstallation des Adapters nicht mehr reproduzierbar.
-
@creekhail
Was musstest Du denn anpassen das es bei Dir funktioniert?bei mir wird der Adapter zwar grün, ruft man die Seite von dem Adapter auf springt der Adapter auf Rot und wirft zig Fehler im Log.
Danke
Tobias -
Hallo, weil ich meinen neuen Roborock Qrevo Curv S5X, nicht bei miHome gefunden habe, bin auf diesen Adapter (dev-branch) umgestiegen.
Der Saugroboter wird noch nicht "unterstützt", aber ich sehe die Daten und kann Programme starten, daher meine Frage:
Nach einer gewissen Zeit (ein paar Stunden) wird das Gerät als offline angezeigt und bleibt auch dabei. Ich kann dann zwar noch immer Programme über den Adapter starten, aber die Datenpunkte aktualisieren sich nicht mehr. Um das vollständig zu automatisieren müsste sich roborock.0.Devices.***.deviceStatus.state aktualisieren. Ist das ein Issuewert oder wird sich das ändern falls die Daten eingepflegt werden? Oder sollte ich per Skript den Adapter neustarten, wenn das Gerät länger als X Minuten offline ist.Zusätzlich würde mich auch interessieren, ob es einen state gibt der "Programm läuft/Programm ist fertig" abbildet?
-
guten morgen.
ich bekomme fehler, da einige Datenpunkte nicht angelegt werden.
State "roborock.0.Devices.6vZ1zawxmrZgMTxgOPtwJn.deviceStatus.carpet_clean_mode" has no existing object, this might lead to an error in future versions State "roborock.0.Devices.6vZ1zawxmrZgMTxgOPtwJn.deviceStatus.carpet_mode" has no existing object, this might lead to an error in future versions
was kann ich hier machen ?
-
Hallo, wieso bekomme ich meinen Adapter nicht mehr auf grün?
Dieser Feher kommt nach dem starten.
Was kann ich tun?2025-08-20 06:57:36.146 - info: host.iobroker instance system.adapter.roborock.0 in version "0.6.19" (non-npm: copystring/ioBroker.roborock#769dee8a000aa78ecdcb826185abcafc1aada5d5) started with pid 2735931 2025-08-20 06:57:40.150 - info: roborock.0 (2735931) starting. Version 0.6.19 (non-npm: copystring/ioBroker.roborock#769dee8a000aa78ecdcb826185abcafc1aada5d5) in /opt/iobroker/node_modules/iobroker.roborock, node: v20.18.0, js-controller: 7.0.7 2025-08-20 06:57:40.171 - info: roborock.0 (2735931) Starting adapter. This might take a few minutes depending on your setup. Please wait. 2025-08-20 06:57:40.187 - info: roborock.0 (2735931) Loaded existing clientID: ee6783f4-5d0a-4d48-b00e-7cafd23b31d9 2025-08-20 06:57:40.472 - error: roborock.0 (2735931) 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) 2025-08-20 06:57:40.762 - info: roborock.0 (2735931) MQTT initialized 2025-08-20 06:57:40.763 - error: roborock.0 (2735931) 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-08-20 06:57:40.764 - error: roborock.0 (2735931) unhandled promise rejection: this.homeData is not initialized. Initialize via getHomeData() first 2025-08-20 06:57:40.764 - error: roborock.0 (2735931) 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) 2025-08-20 06:57:40.765 - error: roborock.0 (2735931) this.homeData is not initialized. Initialize via getHomeData() first 2025-08-20 06:57:40.779 - info: roborock.0 (2735931) terminating 2025-08-20 06:57:40.781 - warn: roborock.0 (2735931) Terminated (UNCAUGHT_EXCEPTION): Without reason 2025-08-20 06:57:40.843 - info: roborock.0 (2735931) MQTT connection established {"cmd":"connack","retain":false,"qos":0,"dup":false,"length":2,"topic":null,"payload":null,"sessionPresent":false,"returnCode":0}. 2025-08-20 06:57:41.282 - info: roborock.0 (2735931) terminating 2025-08-20 06:57:41.437 - error: host.iobroker 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-08-20 06:57:41.437 - error: host.iobroker Caught by controller[1]: Error: this.homeData is not initialized. Initialize via getHomeData() first 2025-08-20 06:57:41.437 - error: host.iobroker Caught by controller[1]: at http_api.getDevices (/opt/iobroker/node_modules/iobroker.roborock/lib/http_api.js:179:10) 2025-08-20 06:57:41.438 - error: host.iobroker Caught by controller[1]: at Roborock.onReady (/opt/iobroker/node_modules/iobroker.roborock/main.js:62:39) 2025-08-20 06:57:41.438 - error: host.iobroker instance system.adapter.roborock.0 terminated with code 6 (UNCAUGHT_EXCEPTION) 2025-08-20 06:57:41.438 - info: host.iobroker Restart adapter system.adapter.roborock.0 because enabled 2025-08-20 06:57:52.160 - info: host.iobroker "system.adapter.roborock.0" disabled 2025-08-20 06:58:14.994 - error: roborock.0 (2735952) adapter disabled 2025-08-20 06:58:15.040 - warn: roborock.0 (2735952) Terminated (NO_ADAPTER_CONFIG_FOUND): Without reason 2025-08-20 06:58:15.723 - error: host.iobroker instance system.adapter.roborock.0 terminated with code 3 (NO_ADAPTER_CONFIG_FOUND) 2025-08-20 06:58:15.723 - info: host.iobroker Do not restart adapter system.adapter.roborock.0 because disabled or deleted
-
@anderl-0
Hallo,
hab nun auf einmal die selben Fehler.
Hast du das Problem schon gelöst? -
-
@thomas-braun said in Fehler Roborock - Adapter:
@nu_81
Versionsnummern der üblichen Verdächtigen?Welche Verdächtigen meinst du? Kann dir leider nicht folgen.
-
Versionen von nodejs, js-controller usw.
Poste einfach die Ausgabe voniob diag
da steht erstmal alles drin.
-
@thomas-braun
Hier der Log.Danke schonmal!
Script v.2025-08-09 *** BASE SYSTEM *** Operating System: Debian GNU/Linux 12 (bookworm) Static hostname: raspberrypi Icon name: computer Kernel: Linux 6.12.34+rpt-rpi-v8 Architecture: arm64 OS is similar to: Model : Raspberry Pi 4 Model B Rev 1.1 Docker : false Virtualization : none Kernel : aarch64 Userland : 64 bit Systemuptime and Load: 18:42:51 up 5:25, 3 users, load average: 1.54, 0.91, 0.58 CPU threads: 4 *** LIFE CYCLE STATUS *** Operating System is the current Debian stable version codenamed 'bookworm'! *** RASPBERRY THROTTLING *** Current issues: No throttling issues detected. Previously detected issues: ~ Under-voltage has occurred ~ Arm frequency capping has occurred ~ Throttling has occurred ~ Soft temperature limit has occurred *** TIME AND TIMEZONES *** Local time: Sat 2025-08-23 18:42:51 CEST Universal time: Sat 2025-08-23 16:42:51 UTC RTC time: n/a Time zone: Europe/Berlin (CEST, +0200) System clock synchronized: yes NTP service: active RTC in local TZ: no *** Users and Groups *** User that called 'iob diag': pihome HOME=/home/pihome GROUPS=pihome adm dialout cdrom sudo audio video plugdev games users input render netdev gpio i2c spi iobroker uosserver User that is running 'js-controller': iobroker HOME=/home/iobroker GROUPS=iobroker tty dialout audio video plugdev bluetooth gpio i2c *** DISPLAY-SERVER SETUP *** Display-Server: false Unit display-manager.service could not be found. Display-Manager: Desktop: Session: tty *** MEMORY *** total used free shared buff/cache available Mem: 4.0G 3.1G 281M 29M 696M 839M Swap: 209M 209M 704K Total: 4.2G 3.4G 282M Active iob-Instances: 29 3796 M total memory 2995 M used memory 2252 M active memory 1046 M inactive memory 268 M free memory 38 M buffer memory 625 M swap cache 199 M total swap 199 M used swap 0 M free swap *** top - Table Of Processes *** top - 18:42:52 up 5:25, 3 users, load average: 1.54, 0.91, 0.58 Tasks: 252 total, 1 running, 251 sleeping, 0 stopped, 0 zombie %Cpu(s): 44.4 us, 22.2 sy, 0.0 ni, 33.3 id, 0.0 wa, 0.0 hi, 0.0 si, 0.0 st MiB Mem : 3796.9 total, 268.2 free, 2996.0 used, 664.5 buff/cache MiB Swap: 200.0 total, 0.7 free, 199.3 used. 800.9 avail Mem *** FAILED SERVICES *** UNIT LOAD ACTIVE SUB DESCRIPTION 0 loaded units listed. *** DMESG CRITICAL ERRORS *** No critical errors detected *** FILESYSTEM *** Filesystem Type Size Used Avail Use% Mounted on udev devtmpfs 1.6G 0 1.6G 0% /dev tmpfs tmpfs 760M 1.2M 759M 1% /run /dev/mmcblk0p2 ext4 29G 17G 11G 63% / tmpfs tmpfs 1.9G 9.2M 1.9G 1% /dev/shm tmpfs tmpfs 5.0M 16K 5.0M 1% /run/lock /dev/mmcblk0p1 vfat 510M 66M 445M 13% /boot/firmware tmpfs tmpfs 380M 84K 380M 1% /run/user/1002 tmpfs tmpfs 380M 0 380M 0% /run/user/1000 Messages concerning ext4 filesystem in dmesg: [Sat Aug 23 13:17:08 2025] Kernel command line: coherent_pool=1M 8250.nr_uarts=0 snd_bcm2835.enable_headphones=0 cgroup_disable=memory numa_policy=interleave nvme.max_host_mem_size_mb=0 snd_bcm2835.enable_headphones=1 snd_bcm2835.enable_hdmi=1 snd_bcm2835.enable_hdmi=0 numa=fake=2 system_heap.max_order=0 smsc95xx.macaddr=DC:A6:32:5A:13:07 vc_mem.mem_base=0x3ec00000 vc_mem.mem_size=0x40000000 console=ttyS0,115200 console=tty1 root=PARTUUID=b69ad78b-02 rootfstype=ext4 fsck.repair=yes rootwait [Sat Aug 23 13:17:11 2025] EXT4-fs (mmcblk0p2): mounted filesystem 56f80fa2-e005-4cca-86e6-19da1069914d ro with ordered data mode. Quota mode: none. [Sat Aug 23 13:17:12 2025] EXT4-fs (mmcblk0p2): re-mounted 56f80fa2-e005-4cca-86e6-19da1069914d r/w. Show mounted filesystems: TARGET SOURCE FSTYPE OPTIONS / /dev/mmcblk0p2 ext4 rw,noatime,commit=600 `-/boot/firmware /dev/mmcblk0p1 vfat rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=ascii,shortname=mixed,errors=remount-ro Files in neuralgic directories: /var: 1.2G /var/ 486M /var/log 380M /var/log/journal/0350b7d3c8bd4b9ca7427777c909465d 380M /var/log/journal 348M /var/cache Archived and active journals take up 379.5M in the file system. /opt/iobroker/backups: 54M /opt/iobroker/backups/ /opt/iobroker/iobroker-data: 358M /opt/iobroker/iobroker-data/ 269M /opt/iobroker/iobroker-data/files 68M /opt/iobroker/iobroker-data/backup-objects 48M /opt/iobroker/iobroker-data/files/iot.admin 47M /opt/iobroker/iobroker-data/files/iot.admin/static/js The five largest files in iobroker-data are: 38M /opt/iobroker/iobroker-data/files/iot.admin/static/js/main.d3d286bd.js.map 24M /opt/iobroker/iobroker-data/files/scenes.admin/static/js/main.c9369f6c.js.map 15M /opt/iobroker/iobroker-data/objects.jsonl 8.8M /opt/iobroker/iobroker-data/files/iot.admin/static/js/main.d3d286bd.js 8.6M /opt/iobroker/iobroker-data/files/backitup.admin/assets/index-BBu8-Y_o.js USB-Devices by-id: USB-Sticks - Avoid direct links to /dev/tty* in your adapter setups, please always prefer the links 'by-id': /dev/serial/by-id/usb-1a86_USB_Serial-if00-port0 *** ZigBee Settings *** Your zigbee.0 COM-Port is matching 'by-id'. Very good! 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 v20.19.4 /usr/bin/node v20.19.4 /usr/bin/npm 10.8.2 /usr/bin/npx 10.8.2 /usr/bin/corepack 0.32.0 nodejs: Installed: 20.19.4-1nodesource1 Candidate: 20.19.4-1nodesource1 Version table: *** 20.19.4-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages 100 /var/lib/dpkg/status 20.19.3-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages 20.19.2-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages 20.19.1-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages 20.19.0-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages 20.18.3-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages 20.18.2-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages 20.18.1-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages 20.18.0-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages 20.17.0-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages 20.16.0-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages 20.15.1-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages 20.15.0-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages 20.14.0-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages 20.13.1-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages 20.13.0-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages 20.12.2-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages 20.12.1-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages 20.12.0-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages 20.11.1-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages 20.11.0-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages 20.10.0-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages 20.9.0-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages 20.8.1-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages 20.8.0-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages 20.7.0-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages 20.6.1-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages 20.6.0-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages 20.5.1-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages 20.5.0-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages 20.4.0-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages 20.3.1-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages 20.3.0-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages 20.2.0-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages 20.1.0-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages 20.0.0-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages 18.19.0+dfsg-6~deb12u2 500 500 http://deb.debian.org/debian bookworm/main arm64 Packages 18.19.0+dfsg-6~deb12u1 500 500 http://deb.debian.org/debian-security bookworm-security/main arm64 Packages 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: raspberrypi raspberrypi (version: 7.0.7, hostname: raspberrypi , alive, uptime: 3139) Core adapters versions js-controller: 7.0.7 admin: 7.6.17 javascript: 8.9.2 nodejs modules from github: 1 +-- iobroker.tapo@0.4.8 (git+ssh://git@github.com/TA2k/ioBroker.tapo.git#615315d4bae5c77b153ac5067bdca8ba3ad3996f) Adapter State + system.adapter.admin.0 : admin : raspberrypi - enabled, port: 8081, bind: 0.0.0.0 (SSL), run as: admin + system.adapter.alarm.0 : alarm : raspberrypi - enabled + system.adapter.alexa2.0 : alexa2 : raspberrypi - enabled system.adapter.alias-manager.0 : alias-manager : raspberrypi - disabled + system.adapter.backitup.0 : backitup : raspberrypi - enabled + system.adapter.cloud.0 : cloud : raspberrypi - enabled system.adapter.daswetter.0 : daswetter : raspberrypi - enabled + system.adapter.denon.0 : denon : raspberrypi - enabled + system.adapter.deyeidc.0 : deyeidc : raspberrypi - enabled, port: 8899 + system.adapter.fahrplan.0 : fahrplan : raspberrypi - enabled + system.adapter.fullybrowser.0 : fullybrowser : raspberrypi - enabled system.adapter.ical.0 : ical : raspberrypi - enabled system.adapter.ical.1 : ical : raspberrypi - enabled system.adapter.icons-icons8.0 : icons-icons8 : raspberrypi - disabled system.adapter.icons-mfd-png.0 : icons-mfd-png : raspberrypi - disabled system.adapter.icons-mfd-svg.0 : icons-mfd-svg : raspberrypi - disabled + system.adapter.iot.0 : iot : raspberrypi - enabled + system.adapter.javascript.0 : javascript : raspberrypi - enabled + system.adapter.lgtv.0 : lgtv : raspberrypi - enabled + system.adapter.mihome-vacuum.2 : mihome-vacuum : raspberrypi - enabled, port: 54321 + system.adapter.nuki-extended.0 : nuki-extended : raspberrypi - enabled + system.adapter.ph803w.0 : ph803w : raspberrypi - enabled system.adapter.roborock.0 : roborock : raspberrypi - enabled + system.adapter.scenes.0 : scenes : raspberrypi - enabled system.adapter.schoolfree.0 : schoolfree : raspberrypi - enabled + system.adapter.shelly.0 : shelly : raspberrypi - enabled, port: 1882, bind: 0.0.0.0 + system.adapter.shelly.1 : shelly : raspberrypi - enabled, port: 1882, bind: 0.0.0.0 + system.adapter.shuttercontrol.0 : shuttercontrol : raspberrypi - enabled + system.adapter.tapo.0 : tapo : raspberrypi - enabled + system.adapter.telegram.0 : telegram : raspberrypi - enabled, port: 8443, bind: 0.0.0.0 + system.adapter.telegram.1 : telegram : raspberrypi - enabled, port: 8443, bind: 0.0.0.0 + system.adapter.tr-064.0 : tr-064 : raspberrypi - enabled + system.adapter.trashschedule.0 : trashschedule : raspberrypi - enabled system.adapter.vis-material-advanced.0 : vis-material-advanced : raspberrypi - disabled system.adapter.vis-timeandweather.0 : vis-timeandweather : raspberrypi - disabled system.adapter.vis.0 : vis : raspberrypi - enabled + system.adapter.web.0 : web : raspberrypi - enabled, port: 8082, bind: 0.0.0.0, run as: admin + system.adapter.whatsapp-cmb.0 : whatsapp-cmb : raspberrypi - enabled + system.adapter.whatsapp-cmb.1 : whatsapp-cmb : raspberrypi - enabled + system.adapter.zigbee.0 : zigbee : raspberrypi - enabled, port: /dev/serial/by-id/usb-1a86_USB_Serial-if00-port0 + instance is alive Enabled adapters with bindings + system.adapter.admin.0 : admin : raspberrypi - enabled, port: 8081, bind: 0.0.0.0 (SSL), run as: admin + system.adapter.deyeidc.0 : deyeidc : raspberrypi - enabled, port: 8899 + system.adapter.mihome-vacuum.2 : mihome-vacuum : raspberrypi - enabled, port: 54321 + system.adapter.shelly.0 : shelly : raspberrypi - enabled, port: 1882, bind: 0.0.0.0 + system.adapter.shelly.1 : shelly : raspberrypi - enabled, port: 1882, bind: 0.0.0.0 + system.adapter.telegram.0 : telegram : raspberrypi - enabled, port: 8443, bind: 0.0.0.0 + system.adapter.telegram.1 : telegram : raspberrypi - enabled, port: 8443, bind: 0.0.0.0 + system.adapter.web.0 : web : raspberrypi - enabled, port: 8082, bind: 0.0.0.0, run as: admin + system.adapter.zigbee.0 : zigbee : raspberrypi - enabled, port: /dev/serial/by-id/usb-1a86_USB_Serial-if00-port0 ioBroker-Repositories ┌─────────┬──────────┬─────────────────────────────────────────────────────────┬──────────────┐ │ (index) │ name │ url │ auto upgrade │ ├─────────┼──────────┼─────────────────────────────────────────────────────────┼──────────────┤ │ 0 │ 'stable' │ 'http://download.iobroker.net/sources-dist.json' │ false │ │ 1 │ 'beta' │ 'http://download.iobroker.net/sources-dist-latest.json' │ false │ └─────────┴──────────┴─────────────────────────────────────────────────────────┴──────────────┘ Active repo(s): stable Upgrade policy: none Installed ioBroker-Adapters Used repository: stable Adapter "admin" : 7.6.17 , installed 7.6.17 Adapter "alarm" : 3.7.0 , installed 3.7.0 Adapter "alexa2" : 3.27.3 , installed 3.27.3 Adapter "alias-manager": 2.0.0 , installed 2.0.0 Adapter "backitup" : 3.3.5 , installed 3.3.5 Adapter "cloud" : 5.0.1 , installed 5.0.1 Adapter "daswetter" : 3.2.3 , installed 3.2.3 Adapter "denon" : 1.15.12 , installed 1.15.12 Adapter "deyeidc" : 0.2.0 , installed 0.2.0 Adapter "fahrplan" : 1.4.1 , installed 1.4.1 Adapter "fullybrowser" : 3.1.2 , installed 3.1.2 Adapter "ical" : 1.16.2 , installed 1.16.1 [Updatable] Adapter "icons-icons8" : 0.0.1 , installed 0.0.1 Adapter "icons-mfd-png": 1.2.1 , installed 1.2.1 Adapter "icons-mfd-svg": 1.2.0 , installed 1.2.0 Adapter "iot" : 3.3.0 , installed 3.3.0 Adapter "javascript" : 8.9.2 , installed 8.9.2 Controller "js-controller": 7.0.7 , installed 7.0.7 Adapter "lgtv" : 2.4.0 , installed 2.4.0 Adapter "mihome-vacuum": 5.2.0 , installed 5.2.0 Adapter "nuki-extended": 2.7.0 , installed 2.7.0 Adapter "ph803w" : 1.2.0 , installed 1.2.0 Adapter "roborock" : 0.6.18 , installed 0.6.18 Adapter "scenes" : 3.2.3 , installed 3.2.3 Adapter "schoolfree" : 1.1.10 , installed 1.1.9 [Updatable] Adapter "shelly" : 10.1.0 , installed 10.1.0 Adapter "shuttercontrol": 2.0.3 , installed 2.0.1 [Updatable] Adapter "socketio" : 6.7.1 , installed 6.7.1 Adapter "telegram" : 4.1.0 , installed 4.1.0 Adapter "tr-064" : 4.3.0 , installed 4.3.0 Adapter "trashschedule": 3.3.0 , installed 3.3.0 Adapter "vis" : 1.5.6 , installed 1.5.6 Adapter "vis-material-advanced": 1.7.4, installed 1.7.4 Adapter "vis-timeandweather": 1.2.2, installed 1.2.2 Adapter "web" : 7.0.8 , installed 7.0.8 Adapter "whatsapp-cmb" : 0.3.0 , installed 0.3.0 Adapter "ws" : 2.6.2 , installed 2.6.2 Adapter "zigbee" : 2.0.5 , installed 2.0.5 Objects and States Please stand by - This may take a while Objects: 8590 States: 6628 *** OS-Repositories and Updates *** Hit:1 http://archive.raspberrypi.com/debian bookworm InRelease Hit:2 http://deb.debian.org/debian bookworm InRelease Hit:3 http://deb.debian.org/debian-security bookworm-security InRelease Hit:4 http://deb.debian.org/debian bookworm-updates InRelease Hit:5 https://deb.nodesource.com/node_20.x nodistro InRelease Reading package lists... Pending Updates: 0 *** Listening Ports *** Active Internet connections (only servers) Proto Recv-Q Send-Q Local Address Foreign Address State User Inode PID/Program name tcp 0 0 127.0.0.1:9001 0.0.0.0:* LISTEN 1001 448519 33748/iobroker.js-c tcp 0 0 127.0.0.1:9000 0.0.0.0:* LISTEN 1001 446004 33748/iobroker.js-c tcp 0 0 0.0.0.0:6789 0.0.0.0:* LISTEN 1002 6488 914/slirp4netns tcp 0 0 0.0.0.0:8880 0.0.0.0:* LISTEN 1002 6494 914/slirp4netns tcp 0 0 0.0.0.0:8881 0.0.0.0:* LISTEN 1002 6496 914/slirp4netns tcp 0 0 0.0.0.0:8882 0.0.0.0:* LISTEN 1002 6498 914/slirp4netns tcp 0 0 127.0.0.1:11002 0.0.0.0:* LISTEN 1002 6361 730/discovery tcp 0 0 0.0.0.0:8444 0.0.0.0:* LISTEN 1002 6492 914/slirp4netns tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN 0 6107 732/sshd: /usr/sbin tcp 0 0 0.0.0.0:53 0.0.0.0:* LISTEN 999 8720 856/pihole-FTL tcp 0 0 0.0.0.0:80 0.0.0.0:* LISTEN 999 8055 856/pihole-FTL tcp 0 0 0.0.0.0:443 0.0.0.0:* LISTEN 999 8056 856/pihole-FTL tcp 0 0 0.0.0.0:8080 0.0.0.0:* LISTEN 1002 6490 914/slirp4netns tcp 0 0 0.0.0.0:1882 0.0.0.0:* LISTEN 1001 453005 34618/io.shelly.1 tcp 0 0 0.0.0.0:11443 0.0.0.0:* LISTEN 1002 6500 914/slirp4netns tcp6 0 0 :::3000 :::* LISTEN 1001 448417 34233/io.fullybrows tcp6 0 0 :::51989 :::* LISTEN 1001 449536 34424/io.nuki-exten tcp6 0 0 :::22 :::* LISTEN 0 6109 732/sshd: /usr/sbin tcp6 0 0 :::53 :::* LISTEN 999 8722 856/pihole-FTL tcp6 0 0 :::80 :::* LISTEN 999 8057 856/pihole-FTL tcp6 0 0 :::443 :::* LISTEN 999 8058 856/pihole-FTL tcp6 0 0 :::8081 :::* LISTEN 1001 446157 33776/io.admin.0 tcp6 0 0 :::8082 :::* LISTEN 1001 452363 34755/io.web.0 udp 0 0 0.0.0.0:5353 0.0.0.0:* 104 484 553/avahi-daemon: r udp 0 0 0.0.0.0:5514 0.0.0.0:* 1002 6504 914/slirp4netns udp 0 0 0.0.0.0:3478 0.0.0.0:* 1002 6502 914/slirp4netns udp 0 0 0.0.0.0:5683 0.0.0.0:* 1001 452785 34516/io.shelly.0 udp 0 0 255.255.255.255:10001 0.0.0.0:* 1002 555009 730/discovery udp 0 0 0.0.0.0:10003 0.0.0.0:* 1002 6506 914/slirp4netns udp 0 0 0.0.0.0:36782 0.0.0.0:* 1002 552483 914/slirp4netns udp 0 0 0.0.0.0:55259 0.0.0.0:* 1001 451740 34458/io.ph803w.0 udp 0 0 0.0.0.0:53 0.0.0.0:* 999 8719 856/pihole-FTL udp 0 0 0.0.0.0:123 0.0.0.0:* 999 9782 856/pihole-FTL udp 0 0 0.0.0.0:53422 0.0.0.0:* 1001 451251 34397/io.mihome-vac udp 0 0 0.0.0.0:33046 0.0.0.0:* 104 486 553/avahi-daemon: r udp 0 0 192.168.2.109:33514 0.0.0.0:* 1002 552649 730/discovery udp6 0 0 :::5353 :::* 104 485 553/avahi-daemon: r udp6 0 0 :::53 :::* 999 8721 856/pihole-FTL udp6 0 0 :::123 :::* 999 9783 856/pihole-FTL udp6 0 0 fe80::9e7d:2a5f:b7c:546 :::* 0 7193 638/NetworkManager udp6 0 0 :::33351 :::* 104 487 553/avahi-daemon: r *** Log File - Last 25 Lines *** at Socket.emit (node:events:524:28) at Socket.emit (node:domain:489:12) at UDP.onMessage (node:dgram:951:8) 2025-08-23 18:43:58.144 - error: roborock.0 (42090) Exception-Code: ERR_OSSL_WRONG_FINAL_BLOCK_LENGTH: error:1C80006B:Provider routines::wrong final block length 2025-08-23 18:43:58.191 - info: roborock.0 (42090) terminating 2025-08-23 18:43:58.193 - warn: roborock.0 (42090) Terminated (UNCAUGHT_EXCEPTION): Without reason 2025-08-23 18:43:58.851 - info: roborock.0 (42090) terminating 2025-08-23 18:43:59.247 - error: host.raspberrypi Caught by controller[0]: Error: error:1C80006B:Provider routines::wrong final block length 2025-08-23 18:43:59.247 - error: host.raspberrypi Caught by controller[0]: at Decipheriv.final (node:internal/crypto/cipher:193:29) 2025-08-23 18:43:59.248 - error: host.raspberrypi Caught by controller[0]: at localConnector.decryptECB (/opt/iobroker/node_modules/iobroker.roborock/lib/localConnector.js:227:25) 2025-08-23 18:43:59.248 - error: host.raspberrypi Caught by controller[0]: at Socket.<anonymous> (/opt/iobroker/node_modules/iobroker.roborock/lib/localConnector.js:190:33) 2025-08-23 18:43:59.248 - error: host.raspberrypi Caught by controller[0]: at Socket.emit (node:events:524:28) 2025-08-23 18:43:59.248 - error: host.raspberrypi Caught by controller[0]: at Socket.emit (node:domain:489:12) 2025-08-23 18:43:59.248 - error: host.raspberrypi Caught by controller[0]: at UDP.onMessage (node:dgram:951:8) { 2025-08-23 18:43:59.248 - error: host.raspberrypi Caught by controller[0]: library: 'Provider routines', 2025-08-23 18:43:59.249 - error: host.raspberrypi Caught by controller[0]: reason: 'wrong final block length', 2025-08-23 18:43:59.249 - error: host.raspberrypi Caught by controller[0]: code: 'ERR_OSSL_WRONG_FINAL_BLOCK_LENGTH' 2025-08-23 18:43:59.249 - error: host.raspberrypi Caught by controller[0]: } 2025-08-23 18:43:59.249 - error: host.raspberrypi instance system.adapter.roborock.0 terminated with code 6 (UNCAUGHT_EXCEPTION) 2025-08-23 18:43:59.249 - info: host.raspberrypi Restart adapter system.adapter.roborock.0 because enabled 2025-08-23 18:44:02.499 - info: tapo.0 (34846) Get camera Status failed 2025-08-23 18:44:02.500 - info: tapo.0 (34846) No stok found for: 80211AE049E6EC914F17A219E950F4E9242DB387 this means the device is offline or connection lost. No update or commands possible 2025-08-23 18:44:06.991 - info: tr-064.0 (34564) forEachConfiguredDevice: in GetSpecificHostEntry 1(Gioia/B8:94:E7:E7:C5:98) device seems offline but we never saw it since adapter was started:Error: sendSOAPActionRequest Error action=GetSpecificHostEntry serviceType=urn:dslforum-org:service:Hosts:1: 500 - {"code":500} 2025-08-23 18:44:12.515 - info: tapo.0 (34846) Get camera Status failed 2025-08-23 18:44:12.516 - info: tapo.0 (34846) No stok found for: 80211AE049E6EC914F17A219E950F4E9242DB387 this means the device is offline or connection lost. No update or commands possible