Navigation

    Logo
    • Register
    • Login
    • Search
    • Recent
    • Tags
    • Unread
    • Categories
    • Unreplied
    • Popular
    • GitHub
    • Docu
    • Hilfe
    1. Home
    2. Deutsch
    3. ioBroker Allgemein
    4. Neuer Adapter für Roborock-Staubsauger

    NEWS

    • Neuer Blog: Fotos und Eindrücke aus Solingen

    • ioBroker@Smart Living Forum Solingen, 14.06. - Agenda added

    • ioBroker goes Matter ... Matter Adapter in Stable

    Neuer Adapter für Roborock-Staubsauger

    This topic has been deleted. Only users with topic management privileges can see it.
    • S
      Sepp last edited by

      vielen dank, werd ich morgen machen 🙂

      1 Reply Last reply Reply Quote 0
      • F
        fritzkalle @copystring last edited by

        @copystring Hallo! Ich bin neu hier und habe bisher nur aufmerksam mitgelesen. Ich habe dasselbe Problem wie Sepp. Ich habe einen Saros 10R und auch bei mir funktioniert der Adapter seit ca. 3 Wochen nicht mehr :-(. Ich kann auch gerne Logs zur Verfügung stellen. Leider weiß ich nicht in welchem Format das üblich ist. Zudem blick ich nicht, wie ich das Log exportieren kann. Wenn Ihr mir das erklärt, dann helfe ich gerne... Viele Grüße!

        copystring da_Woody 2 Replies Last reply Reply Quote 0
        • copystring
          copystring @fritzkalle last edited by

          @fritzkalle Hi, du kannst hier dran teilnehmen und testen: https://github.com/copystring/ioBroker.roborock/issues/833

          Seppel86 created this issue in copystring/ioBroker.roborock

          closed saros 10r keine Verbindung #833

          F 1 Reply Last reply Reply Quote 0
          • da_Woody
            da_Woody @fritzkalle last edited by

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

            wie ich das Log exportieren kann

            einfach markieren, kopieren und dann einfügen.

            F 1 Reply Last reply Reply Quote 0
            • F
              fritzkalle @da_Woody last edited by

              @da_woody Danke! (Dachte mir das wäre zu simpel 😁)

              1 Reply Last reply Reply Quote 0
              • F
                fritzkalle @copystring last edited by

                @copystring Danke! Mache ich asap...

                1 Reply Last reply Reply Quote 0
                • F
                  fritzkalle last edited by

                  Also bei mir funktioniert es mit der letzten Dev Version von https://github.com/copystring/ioBroker.roborock/tree/dev.
                  Ich bekomme nur eine Warnung (Failed to process "app_start" on robot vArM2m3ap0E3f7dsbZWNX (roborock.vacuum.a144): Error: Cloud request with id 111 and method app_start timed out after 30 seconds.)
                  Der Saros 10R ist ansprechbar und funktional. Danke! Wenn Ihr doch noch Logs benötigt bitte Bescheid geben. Viele Grüße!

                  F 1 Reply Last reply Reply Quote 0
                  • F
                    fritzkalle @fritzkalle last edited by

                    Mittlerweile habe ich mehr herausgefunden. Ich bekomme Warnungen und man kann den Wischmodus bzw. die Zimmerreinigung nicht starten 😞

                    • Log_Auszug (Saros10R_custom_mode_app_segment_clean.txt)
                    da_Woody 1 Reply Last reply Reply Quote 0
                    • da_Woody
                      da_Woody @fritzkalle last edited by

                      @fritzkalle öhm, das mit dem einfügen...
                      975c0560-66d8-4ed7-8dbb-d96e8298ce8d-grafik.png
                      🤠

                      Failed to process "set_custom_mode" on robot vArM2m3ap0E3f7dsbZWNX (roborock.vacuum.a144): Error: Cloud request with id 1841 and method set_custom_mode timed out after 30 seconds. MQTT connection state: true at /opt/iobroker/node_modules/iobroker.roborock/lib/requests_handler.js:793:14 at Timeout._onTimeout (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/src/lib/adapter/adapter.ts:2663:17) at listOnTimeout (node:internal/timers:581:17) at processTimers (node:internal/timers:519:7)
                      
                      Failed to process "app_segment_clean" on robot vArM2m3ap0E3f7dsbZWNX (roborock.vacuum.a144): Error: Cloud request with id 1844 and method app_segment_clean timed out after 30 seconds. MQTT connection state: true at /opt/iobroker/node_modules/iobroker.roborock/lib/requests_handler.js:793:14 at Timeout._onTimeout (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/src/lib/adapter/adapter.ts:2663:17) at listOnTimeout (node:internal/timers:581:17) at processTimers (node:internal/timers:519:7)
                      
                      Frederik Buss 1 Reply Last reply Reply Quote 0
                      • Frederik Buss
                        Frederik Buss @da_Woody last edited by

                        Vielleicht (Hoffentlich..) eine blöde Frage: Wie startet man im Adapter ein in der App konfiguriertes Programm? Angezeigt werden die in den Objekten:
                        Screenshot 2025-07-16 185857.png

                        1 Reply Last reply Reply Quote 0
                        • copystring
                          copystring last edited by

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

                          Frederik Buss 2 Replies Last reply Reply Quote 0
                          • Frederik Buss
                            Frederik Buss @copystring last edited by

                            @copystring Wenn man Tomaten auf den Augen hat 🤦 Danke 🙂

                            1 Reply Last reply Reply Quote 0
                            • B
                              berndpehome last edited by

                              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 Reply Last reply Reply Quote 0
                              • D3ltoroxp
                                D3ltoroxp last edited by

                                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 Reply Last reply Reply Quote 0
                                • B
                                  berndpehome last edited by

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

                                  1 Reply Last reply Reply Quote 0
                                  • B
                                    berndpehome last edited by wendy2702

                                    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_Woody 1 Reply Last reply Reply Quote 0
                                    • da_Woody
                                      da_Woody @berndpehome last edited by

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

                                      B 1 Reply Last reply Reply Quote 0
                                      • B
                                        berndpehome @da_Woody last edited by

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

                                        1 Reply Last reply Reply Quote 0
                                        • Frederik Buss
                                          Frederik Buss @copystring last edited by

                                          @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 🙂

                                          copystring 1 Reply Last reply Reply Quote 2
                                          • copystring
                                            copystring @Frederik Buss last edited by

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

                                            1 Reply Last reply Reply Quote 0
                                            • First post
                                              Last post

                                            Support us

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

                                            927
                                            Online

                                            31.9k
                                            Users

                                            80.1k
                                            Topics

                                            1.3m
                                            Posts

                                            122
                                            857
                                            177941
                                            Loading More Posts
                                            • Oldest to Newest
                                            • Newest to Oldest
                                            • Most Votes
                                            Reply
                                            • Reply as topic
                                            Log in to reply
                                            Community
                                            Impressum | Datenschutz-Bestimmungen | Nutzungsbedingungen
                                            The ioBroker Community 2014-2023
                                            logo