Skip to content
  • Home
  • Aktuell
  • Tags
  • 0 Ungelesen 0
  • Kategorien
  • Unreplied
  • Beliebt
  • GitHub
  • Docu
  • Hilfe
Skins
  • Light
  • Brite
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Standard: (Kein Skin)
  • Kein Skin
Einklappen
ioBroker Logo

Community Forum

  1. ioBroker Community Home
  2. Deutsch
  3. ioBroker Allgemein
  4. Neuer Adapter für Roborock-Staubsauger

NEWS

  • UPDATE 31.10.: Amazon Alexa - ioBroker Skill läuft aus ?
    apollon77A
    apollon77
    48
    3
    8.3k

  • Monatsrückblick – September 2025
    BluefoxB
    Bluefox
    13
    1
    2.0k

  • Neues Video "KI im Smart Home" - ioBroker plus n8n
    BluefoxB
    Bluefox
    15
    1
    2.4k

Neuer Adapter für Roborock-Staubsauger

Geplant Angeheftet Gesperrt Verschoben ioBroker Allgemein
922 Beiträge 136 Kommentatoren 324.9k Aufrufe 125 Watching
  • Älteste zuerst
  • Neuste zuerst
  • Meiste Stimmen
Antworten
  • In einem neuen Thema antworten
Anmelden zum Antworten
Dieses Thema wurde gelöscht. Nur Nutzer mit entsprechenden Rechten können es sehen.
  • copystringC copystring

    17390070-8e14-42aa-afc9-0b1d1fdeebee-image.png

    Frederik BussF Offline
    Frederik BussF Offline
    Frederik Buss
    schrieb am zuletzt editiert von
    #850

    @copystring Wenn man Tomaten auf den Augen hat :face_palm: Danke :)

    1 Antwort Letzte Antwort
    0
    • B Offline
      B Offline
      berndpehome
      schrieb am zuletzt editiert von
      #851

      Hab jetzt das selbe Problem wie Sepp weiter oben, heute das Update beim Saros 10 R eingespielt und der Adapter 0.6.19 wird kurz grün und springt dann wieder auf rot, mit der alten Firmware war er zwar grün aber hat die Datenpunkte nicht aktuallisiert, wäre super wenn es bald eine Lösung geben würde da jetzt mein S7 Max Ultra auch nicht mehr über den Adapter verwendbar ist, ansonsten Super Adapter und vielen Dank @copystring für Deine Arbeit.

      1 Antwort Letzte Antwort
      0
      • D3ltoroxpD Offline
        D3ltoroxpD Offline
        D3ltoroxp
        schrieb am zuletzt editiert von
        #852

        Habt ihr in der DockingStation Werte stehen ? Also in den DP's Wassertank, Schmutzwassertank usw ? Da steht bei mir überall Unknown 0. Hab den Edge S5A.

        1 Antwort Letzte Antwort
        0
        • B Offline
          B Offline
          berndpehome
          schrieb am zuletzt editiert von
          #853

          nein, bei mir ist der komplette Ordner devices Status mit NULL, also keine Werte beim Saros10R

          1 Antwort Letzte Antwort
          0
          • B Offline
            B Offline
            berndpehome
            schrieb am zuletzt editiert von wendy2702
            #854

            seit der neuen Firmware am Saros 10R funktioniert der 0.6.18 Adapter nicht mehr, mit der 0.6.19 bleibt er Grün, liest aber den kompletten Devices Status vom 10R nicht aus, mein S7 Max Ultra funktioniert mit der 0.6.19 wieder.

            Fehler bei 0.6.18

            host.iobroker
            	2025-07-20 10:31:40.135	error	instance system.adapter.roborock.0 terminated with code 1 (JS_CONTROLLER_STOPPED)
            host.iobroker
            	2025-07-20 10:31:40.134	error	Caught by controller[0]: }
            host.iobroker
            	2025-07-20 10:31:40.134	error	Caught by controller[0]: code: 'ERR_OSSL_WRONG_FINAL_BLOCK_LENGTH'
            host.iobroker
            	2025-07-20 10:31:40.134	error	Caught by controller[0]: reason: 'wrong final block length',
            host.iobroker
            	2025-07-20 10:31:40.134	error	Caught by controller[0]: library: 'Provider routines',
            host.iobroker
            	2025-07-20 10:31:40.134	error	Caught by controller[0]: at UDP.onMessage (node:dgram:951:8) {
            host.iobroker
            	2025-07-20 10:31:40.134	error	Caught by controller[0]: at Socket.emit (node:domain:489:12)
            host.iobroker
            	2025-07-20 10:31:40.134	error	Caught by controller[0]: at Socket.emit (node:events:524:28)
            host.iobroker
            	2025-07-20 10:31:40.134	error	Caught by controller[0]: at Socket.<anonymous> (/opt/iobroker/node_modules/iobroker.roborock/lib/localConnector.js:190:33)
            host.iobroker
            	2025-07-20 10:31:40.134	error	Caught by controller[0]: at localConnector.decryptECB (/opt/iobroker/node_modules/iobroker.roborock/lib/localConnector.js:227:25)
            host.iobroker
            	2025-07-20 10:31:40.134	error	Caught by controller[0]: at Decipheriv.final (node:internal/crypto/cipher:193:29)
            host.iobroker
            	2025-07-20 10:31:40.133	error	Caught by controller[0]: Error: error:1C80006B:Provider routines::wrong final block length
            roborock.0
            	2025-07-20 10:31:39.641	warn	Terminated (UNCAUGHT_EXCEPTION): Without reason
            roborock.0
            	2025-07-20 10:31:39.639	info	terminating
            roborock.0
            	2025-07-20 10:31:39.599	error	Exception-Code: ERR_OSSL_WRONG_FINAL_BLOCK_LENGTH: error:1C80006B:Provider routines::wrong final block length
            roborock.0
            	2025-07-20 10:31:39.598	error	Error: error:1C80006B:Provider routines::wrong final block length at Decipheriv.final (node:internal/crypto/cipher:193: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:524:28) at Socket.emit (node:domain:489:12) at UDP.onMessage (node:dgram:951:8)
            roborock.0
            	2025-07-20 10:31:39.598	error	uncaught exception: error:1C80006B:Provider routines::wrong final block length
            roborock.0
            	2025-07-20 10:31:34.496	info	MQTT initialized
            roborock.0
            	2025-07-20 10:31:31.770	info	Starting adapter. This might take a few minutes depending on your setup. Please wait.
            roborock.0
            	2025-07-20 10:31:31.742	info	starting. Version 0.6.18 in /opt/iobroker/node_modules/iobroker.roborock, node: v20.19.4, js-controller: 7.0.6
            
            
            Fehler bei 0.6.19 :
            
            
            
            adapter/src/lib/adapter/adapter.ts:2751:38) at listOnTimeout (node:internal/timers:581:17) at processTimers (node:internal/timers:519:7)
            roborock.0
            	2025-07-20 10:38:59.970	error	Failed to process mainUpdateInterval on robot 5rgCW0HwnOPBAukwOrCdcG (roborock.vacuum.a27): 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)
            roborock.0
            	2025-07-20 10:38:58.972	error	Failed to process mainUpdateInterval on robot 7ieq4IEzXQzxO3VVPTTgvf (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:2751:38) at listOnTimeout (node:internal/timers:581:17) at processTimers (node:internal/timers:519:7)
            roborock.0
            	2025-07-20 10:38:58.969	error	Failed to process mainUpdateInterval on robot 5rgCW0HwnOPBAukwOrCdcG (roborock.vacuum.a27): 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)
            roborock.0
            	2025-07-20 10:38:57.971	error	Failed to process mainUpdateInterval on robot 7ieq4IEzXQzxO3VVPTTgvf (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:2751:38) at listOnTimeout (node:internal/timers:581:17) at processTimers (node:internal/timers:519:7)
            roborock.0
            	2025-07-20 10:38:57.969	error	Failed to process mainUpdateInterval on robot 5rgCW0HwnOPBAukwOrCdcG (roborock.vacuum.a27): 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)
            roborock.0
            	2025-07-20 10:38:56.971	error	Failed to process mainUpdateInterval on robot 7ieq4IEzXQzxO3VVPTTgvf (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:2751:38) at listOnTimeout (node:internal/timers:581:17) at processTimers (node:internal/timers:519:7)
            roborock.0
            	2025-07-20 10:38:56.968	error	Failed to process mainUpdateInterval on robot 5rgCW0HwnOPBAukwOrCdcG (roborock.vacuum.a27): 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)
            roborock.0
            	2025-07-20 10:38:55.971	error	Failed to process mainUpdateInterval on robot 7ieq4IEzXQzxO3VVPTTgvf (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:2751:38) at listOnTimeout (node:internal/timers:581:17) at processTimers (node:internal/timers:519:7)
            roborock.0
            	2025-07-20 10:38:55.968	error	Failed to process mainUpdateInterval on robot 5rgCW0HwnOPBAukwOrCdcG (roborock.vacuum.a27): 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)
            roborock.0
            	2025-07-20 10:38:54.971	error	Failed to process mainUpdateInterval on robot 7ieq4IEzXQzxO3VVPTTgvf (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:2751:38) at listOnTimeout (node:internal/timers:581:17) at processTimers (node:internal/timers:519:7)
            roborock.0
            	2025-07-20 10:38:54.968	error	Failed to process mainUpdateInterval on robot 5rgCW0HwnOPBAukwOrCdcG (roborock.vacuum.a27): 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)
            

            der 5rgCW0HwnOPBAukwOrCdcG ist mein S7 Ultra

            der 7ieq4IEzXQzxO3VVPTTgvf ist der Saros 10R

            Mod Edit: Log in Code Tags gesetzt

            da_WoodyD 1 Antwort Letzte Antwort
            0
            • B berndpehome

              seit der neuen Firmware am Saros 10R funktioniert der 0.6.18 Adapter nicht mehr, mit der 0.6.19 bleibt er Grün, liest aber den kompletten Devices Status vom 10R nicht aus, mein S7 Max Ultra funktioniert mit der 0.6.19 wieder.

              Fehler bei 0.6.18

              host.iobroker
              	2025-07-20 10:31:40.135	error	instance system.adapter.roborock.0 terminated with code 1 (JS_CONTROLLER_STOPPED)
              host.iobroker
              	2025-07-20 10:31:40.134	error	Caught by controller[0]: }
              host.iobroker
              	2025-07-20 10:31:40.134	error	Caught by controller[0]: code: 'ERR_OSSL_WRONG_FINAL_BLOCK_LENGTH'
              host.iobroker
              	2025-07-20 10:31:40.134	error	Caught by controller[0]: reason: 'wrong final block length',
              host.iobroker
              	2025-07-20 10:31:40.134	error	Caught by controller[0]: library: 'Provider routines',
              host.iobroker
              	2025-07-20 10:31:40.134	error	Caught by controller[0]: at UDP.onMessage (node:dgram:951:8) {
              host.iobroker
              	2025-07-20 10:31:40.134	error	Caught by controller[0]: at Socket.emit (node:domain:489:12)
              host.iobroker
              	2025-07-20 10:31:40.134	error	Caught by controller[0]: at Socket.emit (node:events:524:28)
              host.iobroker
              	2025-07-20 10:31:40.134	error	Caught by controller[0]: at Socket.<anonymous> (/opt/iobroker/node_modules/iobroker.roborock/lib/localConnector.js:190:33)
              host.iobroker
              	2025-07-20 10:31:40.134	error	Caught by controller[0]: at localConnector.decryptECB (/opt/iobroker/node_modules/iobroker.roborock/lib/localConnector.js:227:25)
              host.iobroker
              	2025-07-20 10:31:40.134	error	Caught by controller[0]: at Decipheriv.final (node:internal/crypto/cipher:193:29)
              host.iobroker
              	2025-07-20 10:31:40.133	error	Caught by controller[0]: Error: error:1C80006B:Provider routines::wrong final block length
              roborock.0
              	2025-07-20 10:31:39.641	warn	Terminated (UNCAUGHT_EXCEPTION): Without reason
              roborock.0
              	2025-07-20 10:31:39.639	info	terminating
              roborock.0
              	2025-07-20 10:31:39.599	error	Exception-Code: ERR_OSSL_WRONG_FINAL_BLOCK_LENGTH: error:1C80006B:Provider routines::wrong final block length
              roborock.0
              	2025-07-20 10:31:39.598	error	Error: error:1C80006B:Provider routines::wrong final block length at Decipheriv.final (node:internal/crypto/cipher:193: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:524:28) at Socket.emit (node:domain:489:12) at UDP.onMessage (node:dgram:951:8)
              roborock.0
              	2025-07-20 10:31:39.598	error	uncaught exception: error:1C80006B:Provider routines::wrong final block length
              roborock.0
              	2025-07-20 10:31:34.496	info	MQTT initialized
              roborock.0
              	2025-07-20 10:31:31.770	info	Starting adapter. This might take a few minutes depending on your setup. Please wait.
              roborock.0
              	2025-07-20 10:31:31.742	info	starting. Version 0.6.18 in /opt/iobroker/node_modules/iobroker.roborock, node: v20.19.4, js-controller: 7.0.6
              
              
              Fehler bei 0.6.19 :
              
              
              
              adapter/src/lib/adapter/adapter.ts:2751:38) at listOnTimeout (node:internal/timers:581:17) at processTimers (node:internal/timers:519:7)
              roborock.0
              	2025-07-20 10:38:59.970	error	Failed to process mainUpdateInterval on robot 5rgCW0HwnOPBAukwOrCdcG (roborock.vacuum.a27): 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)
              roborock.0
              	2025-07-20 10:38:58.972	error	Failed to process mainUpdateInterval on robot 7ieq4IEzXQzxO3VVPTTgvf (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:2751:38) at listOnTimeout (node:internal/timers:581:17) at processTimers (node:internal/timers:519:7)
              roborock.0
              	2025-07-20 10:38:58.969	error	Failed to process mainUpdateInterval on robot 5rgCW0HwnOPBAukwOrCdcG (roborock.vacuum.a27): 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)
              roborock.0
              	2025-07-20 10:38:57.971	error	Failed to process mainUpdateInterval on robot 7ieq4IEzXQzxO3VVPTTgvf (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:2751:38) at listOnTimeout (node:internal/timers:581:17) at processTimers (node:internal/timers:519:7)
              roborock.0
              	2025-07-20 10:38:57.969	error	Failed to process mainUpdateInterval on robot 5rgCW0HwnOPBAukwOrCdcG (roborock.vacuum.a27): 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)
              roborock.0
              	2025-07-20 10:38:56.971	error	Failed to process mainUpdateInterval on robot 7ieq4IEzXQzxO3VVPTTgvf (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:2751:38) at listOnTimeout (node:internal/timers:581:17) at processTimers (node:internal/timers:519:7)
              roborock.0
              	2025-07-20 10:38:56.968	error	Failed to process mainUpdateInterval on robot 5rgCW0HwnOPBAukwOrCdcG (roborock.vacuum.a27): 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)
              roborock.0
              	2025-07-20 10:38:55.971	error	Failed to process mainUpdateInterval on robot 7ieq4IEzXQzxO3VVPTTgvf (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:2751:38) at listOnTimeout (node:internal/timers:581:17) at processTimers (node:internal/timers:519:7)
              roborock.0
              	2025-07-20 10:38:55.968	error	Failed to process mainUpdateInterval on robot 5rgCW0HwnOPBAukwOrCdcG (roborock.vacuum.a27): 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)
              roborock.0
              	2025-07-20 10:38:54.971	error	Failed to process mainUpdateInterval on robot 7ieq4IEzXQzxO3VVPTTgvf (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:2751:38) at listOnTimeout (node:internal/timers:581:17) at processTimers (node:internal/timers:519:7)
              roborock.0
              	2025-07-20 10:38:54.968	error	Failed to process mainUpdateInterval on robot 5rgCW0HwnOPBAukwOrCdcG (roborock.vacuum.a27): 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)
              

              der 5rgCW0HwnOPBAukwOrCdcG ist mein S7 Ultra

              der 7ieq4IEzXQzxO3VVPTTgvf ist der Saros 10R

              Mod Edit: Log in Code Tags gesetzt

              da_WoodyD Offline
              da_WoodyD Offline
              da_Woody
              schrieb am zuletzt editiert von
              #855

              @berndpehome könnest du dein log bitte über 4c670f50-bfef-427b-a79c-75f53c19370f-grafik.png einfügen?

              gruß vom Woody
              HAPPINESS is not a DESTINATION, it's a WAY of LIFE!

              B 1 Antwort Letzte Antwort
              0
              • da_WoodyD da_Woody

                @berndpehome könnest du dein log bitte über 4c670f50-bfef-427b-a79c-75f53c19370f-grafik.png einfügen?

                B Offline
                B Offline
                berndpehome
                schrieb am zuletzt editiert von
                #856

                @da_woody entschuldige, nicht daran gedacht, danke fürs ändern und mach ich das nächste mal

                1 Antwort Letzte Antwort
                0
                • copystringC copystring

                  17390070-8e14-42aa-afc9-0b1d1fdeebee-image.png

                  Frederik BussF Offline
                  Frederik BussF Offline
                  Frederik Buss
                  schrieb am zuletzt editiert von
                  #857

                  @copystring Übrigens ein super extra Danke für Deine Arbeit! Ich habe nun 2 Programme auf den Hauptscreen gepackt und wenn auch aktuell nur über Cloud (Saros 10...), der Robbi tut was er soll. Meine Frau feiert es, mit dem Ding nicht mehr sprechen zu müssen und wie heisst es so schön - Happy wife, happy Life :)

                  copystringC 1 Antwort Letzte Antwort
                  2
                  • Frederik BussF Frederik Buss

                    @copystring Übrigens ein super extra Danke für Deine Arbeit! Ich habe nun 2 Programme auf den Hauptscreen gepackt und wenn auch aktuell nur über Cloud (Saros 10...), der Robbi tut was er soll. Meine Frau feiert es, mit dem Ding nicht mehr sprechen zu müssen und wie heisst es so schön - Happy wife, happy Life :)

                    copystringC Offline
                    copystringC Offline
                    copystring
                    schrieb am zuletzt editiert von
                    #858

                    @frederik-buss danke. Freut mich, dass es so läuft wie du dir das vorgestellt hast.

                    Unterstütze meine Arbeit gerne mit einer Spende über PayPal:
                    https://paypal.me/copystring

                    1 Antwort Letzte Antwort
                    0
                    • Skyx3S Offline
                      Skyx3S Offline
                      Skyx3
                      schrieb am zuletzt editiert von
                      #859

                      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)
                      
                      
                      F 1 Antwort Letzte Antwort
                      0
                      • Skyx3S Skyx3

                        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)
                        
                        
                        F Offline
                        F Offline
                        fritzkalle
                        schrieb am zuletzt editiert von
                        #860

                        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!

                        F 1 Antwort Letzte Antwort
                        0
                        • copystringC Offline
                          copystringC Offline
                          copystring
                          schrieb am zuletzt editiert von
                          #861

                          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.

                          Unterstütze meine Arbeit gerne mit einer Spende über PayPal:
                          https://paypal.me/copystring

                          T 1 Antwort Letzte Antwort
                          0
                          • copystringC copystring

                            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.

                            T Offline
                            T Offline
                            TimoWald
                            schrieb am zuletzt editiert von
                            #862

                            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
                            
                            1 Antwort Letzte Antwort
                            0
                            • C Offline
                              C Offline
                              Creekhail
                              schrieb am zuletzt editiert von
                              #863

                              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.
                              2025-07-26 23_32_06-vis.png

                              T W 2 Antworten Letzte Antwort
                              0
                              • C Creekhail

                                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.
                                2025-07-26 23_32_06-vis.png

                                T Offline
                                T Offline
                                TimoWald
                                schrieb am zuletzt editiert von
                                #864

                                @creekhail hallo könnte ich einen Export deiner Seite haben?

                                C 1 Antwort Letzte Antwort
                                0
                                • T TimoWald

                                  @creekhail hallo könnte ich einen Export deiner Seite haben?

                                  C Offline
                                  C Offline
                                  Creekhail
                                  schrieb am zuletzt editiert von
                                  #865

                                  @timowald Was genau hast du denn vor bzw. was meinst du mit "Export deiner Seite"?

                                  T 1 Antwort Letzte Antwort
                                  0
                                  • C Creekhail

                                    @timowald Was genau hast du denn vor bzw. was meinst du mit "Export deiner Seite"?

                                    T Offline
                                    T Offline
                                    TimoWald
                                    schrieb am zuletzt editiert von
                                    #866

                                    @creekhail Export deiner Seite vom Robby. Finde diese super und würde es bei mir genauso machen wollen.

                                    1 Antwort Letzte Antwort
                                    0
                                    • W Offline
                                      W Offline
                                      Würfel
                                      schrieb am zuletzt editiert von Würfel
                                      #867

                                      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?

                                      
                                      host.PI250GBUSBC
                                      2025-07-31 23:54:32.537	warn	Do not restart adapter system.adapter.roborock.0 because restart loop detected
                                      
                                      host.PI250GBUSBC
                                      2025-07-31 23:54:32.537	info	Restart adapter system.adapter.roborock.0 because enabled
                                      
                                      host.PI250GBUSBC
                                      2025-07-31 23:54:32.536	error	instance system.adapter.roborock.0 terminated with code 6 (UNCAUGHT_EXCEPTION)
                                      
                                      host.PI250GBUSBC
                                      2025-07-31 23:54:32.536	error	Caught by controller[3]: at requests_handler.getMap (/opt/iobroker/node_modules/iobroker.roborock/lib/requests_handler.js:601:18)
                                      
                                      host.PI250GBUSBC
                                      2025-07-31 23:54:32.536	error	Caught by controller[3]: at Roborock.catchError (/opt/iobroker/node_modules/iobroker.roborock/main.js:871:43)
                                      
                                      host.PI250GBUSBC
                                      2025-07-31 23:54:32.536	error	Caught by controller[3]: at http_api.getRobotModel (/opt/iobroker/node_modules/iobroker.roborock/lib/http_api.js:227:66)
                                      
                                      host.PI250GBUSBC
                                      2025-07-31 23:54:32.536	error	Caught by controller[3]: TypeError: Cannot read properties of undefined (reading 'productId')
                                      
                                      host.PI250GBUSBC
                                      2025-07-31 23:54:32.536	error	Caught by controller[3]: 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:
                                      
                                      host.PI250GBUSBC
                                      2025-07-31 23:54:32.536	error	Caught by controller[2]: at requests_handler.getMap (/opt/iobroker/node_modules/iobroker.roborock/lib/requests_handler.js:562:26)
                                      
                                      host.PI250GBUSBC
                                      2025-07-31 23:54:32.536	error	Caught by controller[2]: at requests_handler.sendRequest (/opt/iobroker/node_modules/iobroker.roborock/lib/requests_handler.js:712:17)
                                      
                                      host.PI250GBUSBC
                                      2025-07-31 23:54:32.536	error	Caught by controller[2]: at Roborock.catchError (/opt/iobroker/node_modules/iobroker.roborock/main.js:871:43)
                                      
                                      host.PI250GBUSBC
                                      2025-07-31 23:54:32.535	error	Caught by controller[2]: at http_api.getRobotModel (/opt/iobroker/node_modules/iobroker.roborock/lib/http_api.js:227:66)
                                      
                                      host.PI250GBUSBC
                                      2025-07-31 23:54:32.535	error	Caught by controller[2]: TypeError: Cannot read properties of undefined (reading 'productId')
                                      
                                      host.PI250GBUSBC
                                      2025-07-31 23:54:32.535	error	Caught by controller[1]: 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:
                                      
                                      host.PI250GBUSBC
                                      2025-07-31 23:54:32.535	error	Caught by controller[0]: at requests_handler.getMap (/opt/iobroker/node_modules/iobroker.roborock/lib/requests_handler.js:559:17)
                                      
                                      host.PI250GBUSBC
                                      2025-07-31 23:54:32.535	error	Caught by controller[0]: at requests_handler.sendRequest (/opt/iobroker/node_modules/iobroker.roborock/lib/requests_handler.js:712:17)
                                      
                                      host.PI250GBUSBC
                                      2025-07-31 23:54:32.535	error	Caught by controller[0]: at Roborock.catchError (/opt/iobroker/node_modules/iobroker.roborock/main.js:871:43)
                                      
                                      host.PI250GBUSBC
                                      2025-07-31 23:54:32.535	error	Caught by controller[0]: at http_api.getRobotModel (/opt/iobroker/node_modules/iobroker.roborock/lib/http_api.js:227:66)
                                      
                                      host.PI250GBUSBC
                                      2025-07-31 23:54:32.534	error	Caught by controller[0]: TypeError: Cannot read properties of undefined (reading 'productId')
                                      
                                      host.PI250GBUSBC
                                      2025-07-31 23:54:32.534	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-07-31 23:54:32.330	info	terminating
                                      
                                      roborock.0
                                      2025-07-31 23:54:31.856	error	Cannot read properties of undefined (reading 'productId')
                                      
                                      roborock.0
                                      2025-07-31 23:54:31.856	error	TypeError: Cannot read properties of undefined (reading 'productId') at http_api.getRobotModel (/opt/iobroker/node_modules/iobroker.roborock/lib/http_api.js:227:66) at Roborock.catchError (/opt/iobroker/node_modules/iobroker.roborock/main.js:871:43) at requests_handler.getMap (/opt/iobroker/node_modules/iobroker.roborock/lib/requests_handler.js:601:18)
                                      
                                      roborock.0
                                      2025-07-31 23:54:31.854	error	unhandled promise rejection: Cannot read properties of undefined (reading 'productId')
                                      
                                      roborock.0
                                      2025-07-31 23:54:31.854	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-07-31 23:54:31.850	error	Cannot read properties of undefined (reading 'productId')
                                      
                                      roborock.0
                                      2025-07-31 23:54:31.849	error	TypeError: Cannot read properties of undefined (reading 'productId') at http_api.getRobotModel (/opt/iobroker/node_modules/iobroker.roborock/lib/http_api.js:227:66) at Roborock.catchError (/opt/iobroker/node_modules/iobroker.roborock/main.js:871:43) at requests_handler.sendRequest (/opt/iobroker/node_modules/iobroker.roborock/lib/requests_handler.js:712:17) at requests_handler.getMap (/opt/iobroker/node_modules/iobroker.roborock/lib/requests_handler.js:562:26)
                                      
                                      roborock.0
                                      2025-07-31 23:54:31.848	error	unhandled promise rejection: Cannot read properties of undefined (reading 'productId')
                                      
                                      roborock.0
                                      2025-07-31 23:54:31.848	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-07-31 23:54:31.828	warn	Terminated (UNCAUGHT_EXCEPTION): Without reason
                                      
                                      roborock.0
                                      2025-07-31 23:54:31.826	info	terminating
                                      
                                      roborock.0
                                      2025-07-31 23:54:31.815	error	Cannot read properties of undefined (reading 'productId')
                                      
                                      roborock.0
                                      2025-07-31 23:54:31.815	error	TypeError: Cannot read properties of undefined (reading 'productId') at http_api.getRobotModel (/opt/iobroker/node_modules/iobroker.roborock/lib/http_api.js:227:66) at Roborock.catchError (/opt/iobroker/node_modules/iobroker.roborock/main.js:871:43) at requests_handler.sendRequest (/opt/iobroker/node_modules/iobroker.roborock/lib/requests_handler.js:712:17) at requests_handler.getMap (/opt/iobroker/node_modules/iobroker.roborock/lib/requests_handler.js:559:17)
                                      
                                      roborock.0
                                      2025-07-31 23:54:31.813	error	unhandled promise rejection: Cannot read properties of undefined (reading 'productId')
                                      
                                      roborock.0
                                      2025-07-31 23:54:31.812	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-07-31 23:54:31.500	error	Failed to process mainUpdateInterval on robot bMnYxoB2iqR9CnAlTK9fy (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:2751:38) at listOnTimeout (node:internal/timers:581:17) at processTimers (node:internal/timers:519:7)
                                      
                                      roborock.0
                                      2025-07-31 23:54:30.411	error	Failed to process mainUpdateInterval on robot bMnYxoB2iqR9CnAlTK9fy (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
                                      
                                      roborock.0
                                      2025-07-31 23:54:29.403	info	Starting adapter finished. Let's go!!!!!!!
                                      
                                      roborock.0
                                      2025-07-31 23:54:22.571	error	Failed to process undefined on robot undefined (unknown device model): This robot is not fully supported just yet. Contact the dev to get this robot fully supported!
                                      
                                      roborock.0
                                      2025-07-31 23:54:21.279	error	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)
                                      
                                      roborock.0
                                      2025-07-31 23:54:17.464	info	MQTT connection established {"cmd":"connack","retain":false,"qos":0,"dup":false,"length":2,"topic":null,"payload":null,"sessionPresent":false,"returnCode":0}.
                                      
                                      roborock.0
                                      2025-07-31 23:54:17.341	info	MQTT initialized
                                      
                                      roborock.0
                                      2025-07-31 23:54:16.632	info	Loaded existing clientID: 61f945a6-3735-4f3e-bcaa-dabc268a04bc
                                      
                                      roborock.0
                                      2025-07-31 23:54:16.569	info	Starting adapter. This might take a few minutes depending on your setup. Please wait.
                                      
                                      
                                      roborock.0
                                      2025-08-01 00:00:14.402	error	Failed to process mainUpdateInterval on robot bMnYxoB2iqR9CnAlTxxxxx (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:2751:38) at listOnTimeout (node:internal/timers:581:17) at processTimers (node:internal/timers:519:7)
                                      
                                      
                                      

                                      1 Antwort Letzte Antwort
                                      0
                                      • F fritzkalle

                                        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!

                                        F Offline
                                        F Offline
                                        fritzkalle
                                        schrieb am zuletzt editiert von
                                        #868

                                        Github Issue geschlossen, da Problem nach Neuinstallation des Adapters nicht mehr reproduzierbar.

                                        1 Antwort Letzte Antwort
                                        0
                                        • C Creekhail

                                          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.
                                          2025-07-26 23_32_06-vis.png

                                          W Offline
                                          W Offline
                                          Würfel
                                          schrieb am zuletzt editiert von
                                          #869

                                          @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

                                          1 Antwort Letzte Antwort
                                          0
                                          Antworten
                                          • In einem neuen Thema antworten
                                          Anmelden zum Antworten
                                          • Älteste zuerst
                                          • Neuste zuerst
                                          • Meiste Stimmen


                                          Support us

                                          ioBroker
                                          Community Adapters
                                          Donate
                                          FAQ Cloud / IOT
                                          HowTo: Node.js-Update
                                          HowTo: Backup/Restore
                                          Downloads
                                          BLOG

                                          673

                                          Online

                                          32.4k

                                          Benutzer

                                          81.4k

                                          Themen

                                          1.3m

                                          Beiträge
                                          Community
                                          Impressum | Datenschutz-Bestimmungen | Nutzungsbedingungen | Einwilligungseinstellungen
                                          ioBroker Community 2014-2025
                                          logo
                                          • Anmelden

                                          • Du hast noch kein Konto? Registrieren

                                          • Anmelden oder registrieren, um zu suchen
                                          • Erster Beitrag
                                            Letzter Beitrag
                                          0
                                          • Home
                                          • Aktuell
                                          • Tags
                                          • Ungelesen 0
                                          • Kategorien
                                          • Unreplied
                                          • Beliebt
                                          • GitHub
                                          • Docu
                                          • Hilfe