Navigation

    Logo
    • Register
    • Login
    • Search
    • Recent
    • Tags
    • Unread
    • Categories
    • Unreplied
    • Popular
    • GitHub
    • Docu
    • Hilfe
    1. Home
    2. Deutsch
    3. Skripten / Logik
    4. JavaScript
    5. Roborock Adapter tester gesucht

    NEWS

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

    • ioBroker goes Matter ... Matter Adapter in Stable

    • Monatsrückblick - April 2025

    Roborock Adapter tester gesucht

    This topic has been deleted. Only users with topic management privileges can see it.
    • M-A Hueb
      M-A Hueb @DonToben last edited by

      @dontoben Deckt sich bei mir S7 Maxv Ultra

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

        Ich habe begonnen die Basis für die verschiedenen Roboter zu schaffen.
        Nun müsste ich wissen welche Namen eure Roboter genau haben um die entsprechenden Dateien zu erstellen. Wenn ihr für mich https://github.com/copystring/ioBroker.roborock/tree/split_robots_into_classes testen könntet wäre das echt klasse. Im Log erscheint dann folgendes: 7901e7d4-6115-48ab-999f-7d0543e79228-image.png
        Wobei bei Test vacuum log kommt wahrscheinlich ein Fehler erscheinen wird da außer dem Roborock S7 nichts anderes unterstützt wird. Das baue ich dann entsprechend ein wenn ich die Namen aus dem entsprechenden log von euch erhalte.

        Interessant wären die dazugehörigen fehlenden Parameter wie hier z.B. zu sehen ist:

        @m-a-hueb said in Roborock Adapter tester gesucht:

        roborock.0
        	2023-01-23 10:02:19.049	warn	State "roborock.0.Devices.5jvoTYPcMgvzBKdzXt0fqC.cleaningInfo.Records.14.map_flag" has no existing object, this might lead to an error in future versions
        roborock.0
        	2023-01-23 10:02:19.049	warn	State "roborock.0.Devices.5jvoTYPcMgvzBKdzXt0fqC.cleaningInfo.Records.14.wash_count" has no existing object, this might lead to an error in future versions
        roborock.0
        	2023-01-23 10:02:19.049	warn	State "roborock.0.Devices.5jvoTYPcMgvzBKdzXt0fqC.cleaningInfo.Records.14.avoid_count" has no existing object, this might lead to an error in future versions
        roborock.0
        wendy2702 M-A Hueb 2 Replies Last reply Reply Quote 0
        • wendy2702
          wendy2702 @copystring last edited by wendy2702

          @copystring sagte in Roborock Adapter tester gesucht:

          https://github.com/copystring/ioBroker.roborock/tree/split_robots_into_classes

          EDIT:

          Hier ist es... schon zu spät heute:

          2023-01-24 22:18:55.403  - debug: roborock.0 (1033256) Detected robot name: Roborock S7
          2023-01-24 22:18:55.404  - debug: roborock.0 (1033256) Test vacuum log: roborock_s7
          
          
          1 Reply Last reply Reply Quote 0
          • Codierknecht
            Codierknecht Developer Most Active @copystring last edited by

            @copystring
            Frisch installiert und funzt auf Anhieb 😁
            Jede Menge Datenpunkte mit mehr oder weniger sinnvollen Werten.
            Aber gelaufen ist unser "Freddie" seit der Installation noch nicht - der hat für heute Feierabend 😴

            Für den ersten Adapter funktioniert das schon erfreulich gut.

            Was mir beim einen oder anderen Datenpunkt aufgefallen ist: Hier steht an diversen Stellen nur ein numerischer Wert. Hast Du die Doku zum API irgendwo greifbar? Dann könnte man diese numerischen Werte ja auch in Klartext übersetzen.

            Beispiele (u.a.)
            2ef91b65-282d-4e16-8dcf-135dff6be2da-grafik.png

            1 Reply Last reply Reply Quote 0
            • M-A Hueb
              M-A Hueb @copystring last edited by M-A Hueb

              @copystring

              Da bekomme ich eine Fehlermedlung im Log:

              roborock.0
              	2023-01-25 09:02:56.087	warn	Terminated (UNCAUGHT_EXCEPTION): Without reason
              roborock.0
              	2023-01-25 09:02:56.086	info	terminating
              roborock.0
              	2023-01-25 09:02:56.085	error	Exception-Code: MODULE_NOT_FOUND: Cannot find module './undefined' Require stack: - C:\Program Files\iobroker\SmartHome\node_modules\iobroker.roborock\lib\vacuum.js - C:\Program Files\iobroker\SmartHome\node_modules\iobroker.roborock\main.js
              roborock.0
              	2023-01-25 09:02:56.085	error	Error: Cannot find module './undefined' Require stack: - C:\Program Files\iobroker\SmartHome\node_modules\iobroker.roborock\lib\vacuum.js - C:\Program Files\iobroker\SmartHome\node_modules\iobroker.roborock\main.js at Function.Module._resolveFilename (node:internal/modules/cjs/loader:995:15) at Function.Module._load (node:internal/modules/cjs/loader:841:27) at Module.require (node:internal/modules/cjs/loader:1067:19) at require (node:internal/modules/cjs/helpers:103:18) at new vacuum (C:\Program Files\iobroker\SmartHome\node_modules\iobroker.roborock\lib\vacuum.js:19:31) at Roborock.onReady (C:\Program Files\iobroker\SmartHome\node_modules\iobroker.roborock\main.js:172:20)
              roborock.0
              	2023-01-25 09:02:56.085	error	unhandled promise rejection: Cannot find module './undefined' Require stack: - C:\Program Files\iobroker\SmartHome\node_modules\iobroker.roborock\lib\vacuum.js - C:\Program Files\iobroker\SmartHome\node_modules\iobroker.roborock\main.js
              roborock.0
              	2023-01-25 09:02:56.085	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
              	2023-01-25 09:02:56.082	info	MQTT initialized
              roborock.0
              	2023-01-25 09:02:55.464	info	starting. Version 0.0.1 (non-npm: copystring/ioBroker.roborock#split_robots_into_classes) in C:/Program Files/iobroker/SmartHome/node_modules/iobroker.roborock, node: v16.19.0, js-controller: 4.0.24
              
              copystring 1 Reply Last reply Reply Quote 0
              • copystring
                copystring @M-A Hueb last edited by

                @m-a-hueb said in Roborock Adapter tester gesucht:

                @copystring

                Da bekomme ich eine Fehlermedlung im Log:

                roborock.0
                	2023-01-25 09:02:56.087	warn	Terminated (UNCAUGHT_EXCEPTION): Without reason
                roborock.0
                	2023-01-25 09:02:56.086	info	terminating
                roborock.0
                	2023-01-25 09:02:56.085	error	Exception-Code: MODULE_NOT_FOUND: Cannot find module './undefined' Require stack: - C:\Program Files\iobroker\SmartHome\node_modules\iobroker.roborock\lib\vacuum.js - C:\Program Files\iobroker\SmartHome\node_modules\iobroker.roborock\main.js
                roborock.0
                	2023-01-25 09:02:56.085	error	Error: Cannot find module './undefined' Require stack: - C:\Program Files\iobroker\SmartHome\node_modules\iobroker.roborock\lib\vacuum.js - C:\Program Files\iobroker\SmartHome\node_modules\iobroker.roborock\main.js at Function.Module._resolveFilename (node:internal/modules/cjs/loader:995:15) at Function.Module._load (node:internal/modules/cjs/loader:841:27) at Module.require (node:internal/modules/cjs/loader:1067:19) at require (node:internal/modules/cjs/helpers:103:18) at new vacuum (C:\Program Files\iobroker\SmartHome\node_modules\iobroker.roborock\lib\vacuum.js:19:31) at Roborock.onReady (C:\Program Files\iobroker\SmartHome\node_modules\iobroker.roborock\main.js:172:20)
                roborock.0
                	2023-01-25 09:02:56.085	error	unhandled promise rejection: Cannot find module './undefined' Require stack: - C:\Program Files\iobroker\SmartHome\node_modules\iobroker.roborock\lib\vacuum.js - C:\Program Files\iobroker\SmartHome\node_modules\iobroker.roborock\main.js
                roborock.0
                	2023-01-25 09:02:56.085	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
                	2023-01-25 09:02:56.082	info	MQTT initialized
                roborock.0
                	2023-01-25 09:02:55.464	info	starting. Version 0.0.1 (non-npm: copystring/ioBroker.roborock#split_robots_into_classes) in C:/Program Files/iobroker/SmartHome/node_modules/iobroker.roborock, node: v16.19.0, js-controller: 4.0.24
                

                Ist das ein debug Log? Es fehlt der Name vom Roboter der via debug angezeigt werden sollte.

                M-A Hueb 1 Reply Last reply Reply Quote 0
                • M-A Hueb
                  M-A Hueb @copystring last edited by

                  @copystring Sorry war zu schnell und hatte den neu installierten Adapter noch auf Info stehen.

                  roborock.0
                  	2023-01-25 09:09:53.586	warn	Terminated (UNCAUGHT_EXCEPTION): Without reason
                  roborock.0
                  	2023-01-25 09:09:53.586	info	terminating
                  roborock.0
                  	2023-01-25 09:09:53.584	error	Exception-Code: MODULE_NOT_FOUND: Cannot find module './undefined' Require stack: - C:\Program Files\iobroker\SmartHome\node_modules\iobroker.roborock\lib\vacuum.js - C:\Program Files\iobroker\SmartHome\node_modules\iobroker.roborock\main.js
                  roborock.0
                  	2023-01-25 09:09:53.584	error	Error: Cannot find module './undefined' Require stack: - C:\Program Files\iobroker\SmartHome\node_modules\iobroker.roborock\lib\vacuum.js - C:\Program Files\iobroker\SmartHome\node_modules\iobroker.roborock\main.js at Function.Module._resolveFilename (node:internal/modules/cjs/loader:995:15) at Function.Module._load (node:internal/modules/cjs/loader:841:27) at Module.require (node:internal/modules/cjs/loader:1067:19) at require (node:internal/modules/cjs/helpers:103:18) at new vacuum (C:\Program Files\iobroker\SmartHome\node_modules\iobroker.roborock\lib\vacuum.js:19:31) at Roborock.onReady (C:\Program Files\iobroker\SmartHome\node_modules\iobroker.roborock\main.js:172:20)
                  roborock.0
                  	2023-01-25 09:09:53.584	error	unhandled promise rejection: Cannot find module './undefined' Require stack: - C:\Program Files\iobroker\SmartHome\node_modules\iobroker.roborock\lib\vacuum.js - C:\Program Files\iobroker\SmartHome\node_modules\iobroker.roborock\main.js
                  roborock.0
                  	2023-01-25 09:09:53.583	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
                  	2023-01-25 09:09:53.582	debug	Test vacuum log: undefined
                  roborock.0
                  	2023-01-25 09:09:53.582	debug	Detected robot name: Wall-E
                  roborock.0
                  	2023-01-25 09:09:53.581	info	MQTT initialized
                  roborock.0
                  	2023-01-25 09:09:53.565	debug	RoomIDs debug: {"7993732":"Schlafzimmer","7993746":"Flur","7993754":"Arbeitszimmer","7993760":"Gästezimmer","7993766":"Küche","7993774":"Badezimmer","7993881":"Toilette","7993886":"Wohnzimmer","7993887":"Esszimmer","7997563":"Standard"}
                  roborock.0
                  	2023-01-25 09:09:53.418	info	starting. Version 0.0.1 (non-npm: copystring/ioBroker.roborock#split_robots_into_classes) in C:/Program Files/iobroker/SmartHome/node_modules/iobroker.roborock, node: v16.19.0, js-controller: 4.0.24
                  
                  copystring 1 Reply Last reply Reply Quote 0
                  • copystring
                    copystring @M-A Hueb last edited by

                    @m-a-hueb said in Roborock Adapter tester gesucht:

                    @copystring Sorry war zu schnell und hatte den neu installierten Adapter noch auf Info stehen.

                    roborock.0
                    	2023-01-25 09:09:53.586	warn	Terminated (UNCAUGHT_EXCEPTION): Without reason
                    roborock.0
                    	2023-01-25 09:09:53.586	info	terminating
                    roborock.0
                    	2023-01-25 09:09:53.584	error	Exception-Code: MODULE_NOT_FOUND: Cannot find module './undefined' Require stack: - C:\Program Files\iobroker\SmartHome\node_modules\iobroker.roborock\lib\vacuum.js - C:\Program Files\iobroker\SmartHome\node_modules\iobroker.roborock\main.js
                    roborock.0
                    	2023-01-25 09:09:53.584	error	Error: Cannot find module './undefined' Require stack: - C:\Program Files\iobroker\SmartHome\node_modules\iobroker.roborock\lib\vacuum.js - C:\Program Files\iobroker\SmartHome\node_modules\iobroker.roborock\main.js at Function.Module._resolveFilename (node:internal/modules/cjs/loader:995:15) at Function.Module._load (node:internal/modules/cjs/loader:841:27) at Module.require (node:internal/modules/cjs/loader:1067:19) at require (node:internal/modules/cjs/helpers:103:18) at new vacuum (C:\Program Files\iobroker\SmartHome\node_modules\iobroker.roborock\lib\vacuum.js:19:31) at Roborock.onReady (C:\Program Files\iobroker\SmartHome\node_modules\iobroker.roborock\main.js:172:20)
                    roborock.0
                    	2023-01-25 09:09:53.584	error	unhandled promise rejection: Cannot find module './undefined' Require stack: - C:\Program Files\iobroker\SmartHome\node_modules\iobroker.roborock\lib\vacuum.js - C:\Program Files\iobroker\SmartHome\node_modules\iobroker.roborock\main.js
                    roborock.0
                    	2023-01-25 09:09:53.583	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
                    	2023-01-25 09:09:53.582	debug	Test vacuum log: undefined
                    roborock.0
                    	2023-01-25 09:09:53.582	debug	Detected robot name: Wall-E
                    roborock.0
                    	2023-01-25 09:09:53.581	info	MQTT initialized
                    roborock.0
                    	2023-01-25 09:09:53.565	debug	RoomIDs debug: {"7993732":"Schlafzimmer","7993746":"Flur","7993754":"Arbeitszimmer","7993760":"Gästezimmer","7993766":"Küche","7993774":"Badezimmer","7993881":"Toilette","7993886":"Wohnzimmer","7993887":"Esszimmer","7997563":"Standard"}
                    roborock.0
                    	2023-01-25 09:09:53.418	info	starting. Version 0.0.1 (non-npm: copystring/ioBroker.roborock#split_robots_into_classes) in C:/Program Files/iobroker/SmartHome/node_modules/iobroker.roborock, node: v16.19.0, js-controller: 4.0.24
                    

                    Wall-E? Okay dann geht das nicht so wie ich mir das vorgestellt habe. Danke.

                    wendy2702 D 2 Replies Last reply Reply Quote 0
                    • wendy2702
                      wendy2702 @copystring last edited by wendy2702

                      @copystring den Namen kann man in der App frei einstellen.

                      Vielleicht sieht man in der API die Modell Bezeichnung!?

                      4392FFEE-FAEC-4583-9B5F-FCBF160A4B1C.jpeg

                      Bei mir halt ein S7+

                      1 Reply Last reply Reply Quote 0
                      • D
                        DonToben last edited by

                        Bei mir S7 Pro Ultra

                        Screenshot_20230125-113153_Roborock.jpg

                        M-A Hueb 1 Reply Last reply Reply Quote 0
                        • M-A Hueb
                          M-A Hueb @DonToben last edited by M-A Hueb

                          roborock.vacuuum.a27 Roborrock Maxv Ultra

                          1 Reply Last reply Reply Quote 0
                          • D
                            Dimi @copystring last edited by

                            @copystring

                            Hallo, tolle Arbeit.

                            Also ich habe einen Roborock S6 MaxV und der hat laut App die Modellbezeichnung roborock.vacuum.a10

                            1 Reply Last reply Reply Quote 0
                            • D
                              DonToben last edited by

                              @copystring
                              Hi, ich habe ein Problem mit dem Roborock Adapter festgestellt. Er reagiert nicht immer auf steuern app_segment_clean. Räume sind auf true gesetzt. Komplettreinigung über app_start funktioniert immer.
                              Nach Adapter Neustart geht dann wieder app_segment_clean für eine bestimmte Zeit.

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

                                Die meisten Roboter sollten nun laufen.
                                Beim S4 scheint es keinen Mop zu geben. Für diesen habe ich das Feature entfernt.
                                https://github.com/copystring/ioBroker.roborock/tree/split_robots_into_classes

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

                                  Wenn ihr euer homedata zuschicken könntet dann kann ich für jeden Roboter den deviceStatus vollständig erstellen.

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

                                    @copystring sagte in Roborock Adapter tester gesucht:

                                    https://github.com/copystring/ioBroker.roborock/tree/split_robots_into_classes

                                    Woran kann man erkennen das der Typ erkannt wurde ?

                                    EDIT: Vielleicht kannst du die Versionsnummern mal hochzählen damit man sehen kann ob die richtige Version installiert wurde und läuft.

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

                                      Wenn keine Fehlermeldung erscheint 🙂

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

                                        @copystring Im Debug log beim Adpater start meinst du?

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

                                          Genau so ist es. Ansonsten meldet der Adapter, dass der Roboter nicht unterstützt ist.

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

                                            @copystring Bei mir läuft er nicht mehr:

                                            2023-01-25 18:25:30.721  - info: host.iobroker stopInstance system.adapter.roborock.0 (force=false, process=true)
                                            2023-01-25 18:25:30.729  - info: roborock.0 (1033377) Got terminate signal TERMINATE_YOURSELF
                                            2023-01-25 18:25:30.738  - info: roborock.0 (1033377) terminating
                                            2023-01-25 18:25:30.739  - info: roborock.0 (1033377) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
                                            2023-01-25 18:25:30.792  - info: host.iobroker stopInstance system.adapter.roborock.0 send kill signal
                                            2023-01-25 18:25:31.353  - info: host.iobroker instance system.adapter.roborock.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
                                            2023-01-25 18:25:34.032  - info: host.iobroker instance system.adapter.roborock.0 started with pid 1047380
                                            2023-01-25 18:25:34.745  - debug: roborock.0 (1047380) Redis Objects: Use Redis connection: 0.0.0.0:9001
                                            2023-01-25 18:25:34.788  - debug: roborock.0 (1047380) Objects client ready ... initialize now
                                            2023-01-25 18:25:34.789  - debug: roborock.0 (1047380) Objects create System PubSub Client
                                            2023-01-25 18:25:34.790  - debug: roborock.0 (1047380) Objects create User PubSub Client
                                            2023-01-25 18:25:34.870  - debug: roborock.0 (1047380) Objects client initialize lua scripts
                                            2023-01-25 18:25:34.876  - debug: roborock.0 (1047380) Objects connected to redis: 0.0.0.0:9001
                                            2023-01-25 18:25:34.910  - debug: roborock.0 (1047380) Redis States: Use Redis connection: 0.0.0.0:9000
                                            2023-01-25 18:25:34.932  - debug: roborock.0 (1047380) States create System PubSub Client
                                            2023-01-25 18:25:34.932  - debug: roborock.0 (1047380) States create User PubSub Client
                                            2023-01-25 18:25:35.016  - debug: roborock.0 (1047380) States connected to redis: 0.0.0.0:9000
                                            2023-01-25 18:25:35.221  - info: roborock.0 (1047380) starting. Version 0.0.1 (non-npm: copystring/ioBroker.roborock#split_robots_into_classes) in /opt/iobroker/node_modules/iobroker.roborock, node: v16.19.0, js-controller: 4.0.24
                                            2023-01-25 18:25:35.432  - debug: roborock.0 (1047380) RoomIDs debug: {"10397445":"Flur","10397450":"Schlafzimmer","10397453":"Bad","10397457":"Arbeitszimmer","10397459":"Wohnzimmer","10397463":"Küche"}
                                            2023-01-25 18:25:35.458  - info: roborock.0 (1047380) MQTT initialized
                                            2023-01-25 18:25:35.459  - debug: roborock.0 (1047380) Detected robot model: roborock.vacuum.a15
                                            2023-01-25 18:25:35.460  - debug: roborock.0 (1047380) Robot key: undefined
                                            2023-01-25 18:25:35.462  - error: roborock.0 (1047380) 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().
                                            2023-01-25 18:25:35.462  - error: roborock.0 (1047380) unhandled promise rejection: Cannot find module 'ioBroker.roborock/lib/basic_robot'
                                            - /opt/iobroker/node_modules/iobroker.roborock/lib/roborock.vacuum.a15.js
                                            - /opt/iobroker/node_modules/iobroker.roborock/lib/vacuum.js
                                            - /opt/iobroker/node_modules/iobroker.roborock/main.js
                                            2023-01-25 18:25:35.462  - error: roborock.0 (1047380) Error: Cannot find module 'ioBroker.roborock/lib/basic_robot'
                                            - /opt/iobroker/node_modules/iobroker.roborock/lib/roborock.vacuum.a15.js
                                            - /opt/iobroker/node_modules/iobroker.roborock/lib/vacuum.js
                                            - /opt/iobroker/node_modules/iobroker.roborock/main.js
                                                at Object.<anonymous> (/opt/iobroker/node_modules/iobroker.roborock/lib/roborock.vacuum.a15.js:5:21)
                                            2023-01-25 18:25:35.462  - error: roborock.0 (1047380) Exception-Code: MODULE_NOT_FOUND: Cannot find module 'ioBroker.roborock/lib/basic_robot'
                                            - /opt/iobroker/node_modules/iobroker.roborock/lib/roborock.vacuum.a15.js
                                            - /opt/iobroker/node_modules/iobroker.roborock/lib/vacuum.js
                                            - /opt/iobroker/node_modules/iobroker.roborock/main.js
                                            2023-01-25 18:25:35.463  - info: roborock.0 (1047380) terminating
                                            2023-01-25 18:25:35.464  - warn: roborock.0 (1047380) Terminated (UNCAUGHT_EXCEPTION): Without reason
                                            2023-01-25 18:25:36.081  - error: host.iobroker instance system.adapter.roborock.0 terminated with code 6 (UNCAUGHT_EXCEPTION)
                                            2023-01-25 18:25:36.081  - info: host.iobroker Restart adapter system.adapter.roborock.0 because enabled
                                            
                                            
                                            copystring 1 Reply Last reply Reply Quote 0
                                            • First post
                                              Last post

                                            Support us

                                            ioBroker
                                            Community Adapters
                                            Donate

                                            827
                                            Online

                                            31.7k
                                            Users

                                            79.8k
                                            Topics

                                            1.3m
                                            Posts

                                            51
                                            766
                                            160306
                                            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