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.
    • David G.
      David G. last edited by

      Hat zufällig schon jmd eine kleine Zusammenstellung über "dock_error_status".

      Bisher weiß ich, dass 39 der Schnutzwassertank und 38 der Frischwassertank ist.

      Der Roboter hat ja noch einige andere "*_status".
      Da bin ich bisher garnicht sicher was für was ist.

      Würde mir gerne ein Skript schreiben, was mir soweit möglich sämtliche Fehlermeldungen im klartext zeigt schreiben.
      Evtl kommt es ja auch irgendwann im Adapter. Aber erstmal selber testen ^^.

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

        @dontoben said in Roborock Adapter tester gesucht:

        @copystring
        Habe mir gerade den iobroker log angesehen.
        Es gab heute Nacht eine Menge Fehlereinträge, danach wieder alles i.O.
        Eine Idee?
        Roborock S7 Pro Ultra.

        Habe die 0.1.6 installiert. Mit den Version davor hatte ich die Auffälligkeit nicht.

        2023-03-15 03:52:31.523 - error: roborock.0 (5655) Unsported attribute: 589 of get_status. Please contact the dev to add the newly found attribute of your robot.
        2023-03-15 03:52:31.523 - error: roborock.0 (5655) Unsported attribute: 590 of get_status. Please contact the dev to add the newly found attribute of your robot.
        2023-03-15 03:52:31.523 - error: roborock.0 (5655) Unsported attribute: 591 of get_status. Please contact the dev to add the newly found attribute of your robot.
        2023-03-15 03:52:31.523 - error: roborock.0 (5655) Unsported attribute: 592 of get_status. Please contact the dev to add the newly found attribute of your robot.
        2023-03-15 03:52:31.524 - error: roborock.0 (5655) Unsported attribute: 593 of get_status. Please contact the dev to add the newly found attribute of your robot.
        2023-03-15 03:52:31.524 - error: roborock.0 (5655) Unsported attribute: 594 of get_status. Please contact the dev to add the newly found attribute of your robot.
        2023-03-15 03:52:31.524 - error: roborock.0 (5655) Unsported attribute: 595 of get_status. Please contact the dev to add the newly found attribute of your robot.
        2023-03-15 03:52:31.524 - error: roborock.0 (5655) Unsported attribute: 596 of get_status. Please contact the dev to add the newly found attribute of your robot.
        2023-03-15 03:52:31.525 - error: roborock.0 (5655) Unsported attribute: 597 of get_status. Please contact the dev to add the newly found attribute of your robot.
        2023-03-15 03:52:31.525 - error: roborock.0 (5655) Unsported attribute: 598 of get_status. Please contact the dev to add the newly found attribute of your robot.
        2023-03-15 03:52:31.525 - error: roborock.0 (5655) Unsported attribute: 599 of get_status. Please contact the dev to add the newly found attribute of your robot.
        2023-03-15 03:52:31.525 - error: roborock.0 (5655) Unsported attribute: 600 of get_status. Please contact the dev to add the newly found attribute of your robot.
        2023-03-15 03:52:31.526 - error: roborock.0 (5655) Unsported attribute: 601 of get_status. Please contact the dev to add the newly found attribute of your robot.
        2023-03-15 03:52:31.526 - error: roborock.0 (5655) Unsported attribute: 602 of get_status. Please contact the dev to add the newly found attribute of your robot.
        2023-03-15 03:52:31.526 - error: roborock.0 (5655) Unsported attribute: 603 of get_status. Please contact the dev to add the newly found attribute of your robot.
        2023-03-15 03:52:31.527 - error: roborock.0 (5655) Unsported attribute: 604 of get_status. Please contact the dev to add the newly found attribute of your robot.
        2023-03-15 03:52:31.527 - error: roborock.0 (5655) Unsported attribute: 605 of get_status. Please contact the dev to add the newly found attribute of your robot.
        2023-03-15 03:52:31.527 - error: roborock.0 (5655) Unsported attribute: 606 of get_status. Please contact the dev to add the newly found attribute of your robot.
        2023-03-15 03:52:31.527 - error: roborock.0 (5655) Unsported attribute: 607 of get_status. Please contact the dev to add the newly found attribute of your robot.
        2023-03-15 03:52:31.528 - error: roborock.0 (5655) Unsported attribute: 608 of get_status. Please contact the dev to add the newly found attribute of your robot.
        2023-03-15 03:52:31.528 - error: roborock.0 (5655) Unsported attribute: 609 of get_status. Please contact the dev to add the newly found attribute of your robot.
        2023-03-15 03:52:31.528 - error: roborock.0 (5655) Unsported attribute: 610 of get_status. Please contact the dev to add the newly found attribute of your robot.
        2023-03-15 03:52:31.528 - error: roborock.0 (5655) Unsported attribute: 611 of get_status. Please contact the dev to add the newly found attribute of your robot.
        2023-03-15 03:52:31.529 - error: roborock.0 (5655) Unsported attribute: 612 of get_status. Please contact the dev to add the newly found attribute of your robot.
        2023-03-15 03:52:31.529 - error: roborock.0 (5655) Unsported attribute: 613 of get_status. Please contact the dev to add the newly found attribute of your robot.
        2023-03-15 03:52:31.530 - error: roborock.0 (5655) Unsported attribute: 614 of get_status. Please contact the dev to add the newly found attribute of your robot.
        2023-03-15 03:52:31.530 - error: roborock.0 (5655) Unsported attribute: 615 of get_status. Please contact the dev to add the newly found attribute of your robot.
        2023-03-15 03:52:31.530 - error: roborock.0 (5655) Unsported attribute: 616 of get_status. Please contact the dev to add the newly found attribute of your robot.
        2023-03-15 03:52:31.530 - error: roborock.0 (5655) Unsported attribute: 617 of get_status. Please contact the dev to add the newly found attribute of your robot.
        2023-03-15 03:52:31.531 - error: roborock.0 (5655) Unsported attribute: 618 of get_status. Please contact the dev to add the newly found attribute of your robot.
        2023-03-15 03:52:31.531 - error: roborock.0 (5655) Unsported attribute: 619 of get_status. Please contact the dev to add the newly found attribute of your robot.
        2023-03-15 03:52:31.531 - error: roborock.0 (5655) Unsported attribute: 620 of get_status. Please contact the dev to add the newly found attribute of your robot.
        2023-03-15 03:52:31.531 - error: roborock.0 (5655) Unsported attribute: 621 of get_status. Please contact the dev to add the newly found attribute of your robot.
        2023-03-15 03:52:31.531 - error: roborock.0 (5655) Unsported attribute: 622 of get_status. Please contact the dev to add the newly found attribute of your robot.
        2023-03-15 03:52:31.531 - error: roborock.0 (5655) Unsported attribute: 623 of get_status. Please contact the dev to add the newly found attribute of your robot.
        2023-03-15 03:52:31.532 - error: roborock.0 (5655) Unsported attribute: 624 of get_status. Please contact the dev to add the newly found attribute of your robot.
        2023-03-15 03:52:31.532 - error: roborock.0 (5655) Unsported attribute: 625 of get_status. Please contact the dev to add the newly found attribute of your robot.
        2023-03-15 03:52:31.532 - error: roborock.0 (5655) Unsported attribute: 626 of get_status. Please contact the dev to add the newly found attribute of your robot.
        2023-03-15 03:52:31.532 - error: roborock.0 (5655) Unsported attribute: 627 of get_status. Please contact the dev to add the newly found attribute of your robot.
        2023-03-15 03:52:31.532 - error: roborock.0 (5655) Unsported attribute: 628 of get_status. Please contact the dev to add the newly found attribute of your robot.
        2023-03-15 03:52:31.532 - error: roborock.0 (5655) Unsported attribute: 629 of get_status. Please contact the dev to add the newly found attribute of your robot.
        2023-03-15 03:52:31.533 - error: roborock.0 (5655) Unsported attribute: 630 of get_status. Please contact the dev to add the newly found attribute of your robot.
        2023-03-15 03:52:31.533 - error: roborock.0 (5655) Unsported attribute: 631 of get_status. Please contact the dev to add the newly found attribute of your robot.
        2023-03-15 03:52:31.533 - error: roborock.0 (5655) Unsported attribute: 632 of get_status. Please contact the dev to add the newly found attribute of your robot.
        2023-03-15 03:52:31.533 - error: roborock.0 (5655) Unsported attribute: 633 of get_status. Please contact the dev to add the newly found attribute of your robot.
        2023-03-15 03:52:31.533 - error: roborock.0 (5655) Unsported attribute: 634 of get_status. Please contact the dev to add the newly found attribute of your robot.
        2023-03-15 03:52:31.533 - error: roborock.0 (5655) Unsported attribute: 635 of get_status. Please contact the dev to add the newly found attribute of your robot.
        2023-03-15 03:52:31.534 - error: roborock.0 (5655) Unsported attribute: 636 of get_status. Please contact the dev to add the newly found attribute of your robot.
        2023-03-15 03:52:31.534 - error: roborock.0 (5655) Unsported attribute: 637 of get_status. Please contact the dev to add the newly found attribute of your robot.
        2023-03-15 03:52:31.534 - error: roborock.0 (5655) Unsported attribute: 638 of get_status. Please contact the dev to add the newly found attribute of your robot.
        2023-03-15 03:52:31.534 - error: roborock.0 (5655) Unsported attribute: 639 of get_status. Please contact the dev to add the newly found attribute of your robot.
        2023-03-15 03:52:31.534 - error: roborock.0 (5655) Unsported attribute: 640 of get_status. Please contact the dev to add the newly found attribute of your robot.
        2023-03-15 03:52:31.535 - error: roborock.0 (5655) Unsported attribute: 641 of get_status. Please contact the dev to add the newly found attribute of your robot.
        2023-03-15 03:52:31.535 - error: roborock.0 (5655) Unsported attribute: 642 of get_status. Please contact the dev to add the newly found attribute of your robot.
        2023-03-15 03:52:31.535 - error: roborock.0 (5655) Unsported attribute: 643 of get_status. Please contact the dev to add the newly found attribute of your robot.
        2023-03-15 03:52:31.535 - error: roborock.0 (5655) Unsported attribute: 644 of get_status. Please contact the dev to add the newly found attribute of your robot.
        2023-03-15 03:52:31.535 - error: roborock.0 (5655) Unsported attribute: 645 of get_status. Please contact the dev to add the newly found attribute of your robot.
        2023-03-15 03:52:31.536 - error: roborock.0 (5655) Unsported attribute: 646 of get_status. Please contact the dev to add the newly found attribute of your robot.
        2023-03-15 03:52:31.536 - error: roborock.0 (5655) Unsported attribute: 647 of get_status. Please contact the dev to add the newly found attribute of your robot.
        2023-03-15 03:52:31.536 - error: roborock.0 (5655) Unsported attribute: 648 of get_status. Please contact the dev to add the newly found attribute of your robot.
        2023-03-15 03:52:31.536 - error: roborock.0 (5655) Unsported attribute: 649 of get_status. Please contact the dev to add the newly found attribute of your robot.
        2023-03-15 03:52:31.536 - error: roborock.0 (5655) Unsported attribute: 650 of get_status. Please contact the dev to add the newly found attribute of your robot.
        2023-03-15 03:52:31.536 - error: roborock.0 (5655) Unsported attribute: 651 of get_status. Please contact the dev to add the newly found attribute of your robot.
        2023-03-15 03:52:31.537 - error: roborock.0 (5655) Unsported attribute: 652 of get_status. Please contact the dev to add the newly found attribute of your robot.
        2023-03-15 03:52:31.537 - error: roborock.0 (5655) Unsported attribute: 653 of get_status. Please contact the dev to add the newly found attribute of your robot.
        2023-03-15 03:52:31.537 - error: roborock.0 (5655) Unsported attribute: 654 of get_status. Please contact the dev to add the newly found attribute of your robot.
        2023-03-15 03:52:31.537 - error: roborock.0 (5655) Unsported attribute: 655 of get_status. Please contact the dev to add the newly found attribute of your robot.
        2023-03-15 03:52:31.537 - error: roborock.0 (5655) Unsported attribute: 656 of get_status. Please contact the dev to add the newly found attribute of your robot.
        2023-03-15 03:52:31.537 - error: roborock.0 (5655) Unsported attribute: 657 of get_status. Please contact the dev to add the newly found attribute of your robot.
        2023-03-15 03:52:31.538 - error: roborock.0 (5655) Unsported attribute: 658 of get_status. Please contact the dev to add the newly found attribute of your robot.
        2023-03-15 03:52:31.538 - error: roborock.0 (5655) Unsported attribute: 659 of get_status. Please contact the dev to add the newly found attribute of your robot.
        2023-03-15 04:34:31.481 - info: roborock.0 (5655) State value to set for "roborock.0.Devices.5Im6TX0cm6mgxaWxHaEos7.deviceStatus.water_box_custom_mode" has to be type "number" but received type "string"
        2023-03-15 04:44:31.484 - info: roborock.0 (5655) State value to set for "roborock.0.Devices.5Im6TX0cm6mgxaWxHaEos7.deviceStatus.water_box_custom_mode" has to be type "number" but received type "string"
        2023-03-15 04:56:30.926 - warn: roborock.0 (5655) MQTT connection close.
        2023-03-15 04:56:30.927 - warn: roborock.0 (5655) MQTT connection reconnect.
        

        Hier gibt es bereits ein Issue dazu. https://github.com/copystring/ioBroker.roborock/issues/117 bitte mal beobachten, ob das nochmal auftaucht und dann entsprechend am das Issue anknüpfen.
        Ich hatte das übrigens heute morgen auch aber danach nicht mehr.

        Black-Thunder created this issue in copystring/ioBroker.roborock

        closed v0.1.6: Unsported attribute: XXX of get_status. Please contact the dev to add the newly found attribute of your robot. #117

        1 Reply Last reply Reply Quote 0
        • copystring
          copystring @David G. last edited by

          @david-g said in Roborock Adapter tester gesucht:

          Hat zufällig schon jmd eine kleine Zusammenstellung über "dock_error_status".

          Bisher weiß ich, dass 39 der Schnutzwassertank und 38 der Frischwassertank ist.

          Der Roboter hat ja noch einige andere "*_status".
          Da bin ich bisher garnicht sicher was für was ist.

          Würde mir gerne ein Skript schreiben, was mir soweit möglich sämtliche Fehlermeldungen im klartext zeigt schreiben.
          Evtl kommt es ja auch irgendwann im Adapter. Aber erstmal selber testen ^^.

          Ein paar davon sind hier: https://github.com/copystring/ioBroker.roborock/issues/36 wir sammeln aber noch. Vielleicht kannst du helfen? Ich brauche alle Meldungen in Englisch aus der App. Dafür die App in Englisch umstellen.

          mproper23 created this issue in copystring/ioBroker.roborock

          closed Dock_Error_Status #36

          David G. 1 Reply Last reply Reply Quote 0
          • David G.
            David G. @copystring last edited by David G.

            @copystring

            Hab die App auf englisch gestellt und ein Script überwacht alle *_status Datenpunkte.

            Wenn etwas neues kommt melde ich mich.

            Gibt es bei den Datenpunkten vom Roboter selber schon mehr Erfahrungen?

            copystring 1 Reply Last reply Reply Quote 0
            • copystring
              copystring @David G. last edited by

              @david-g said in Roborock Adapter tester gesucht:

              @copystring

              Gibt es bei den Datenpunkten vom Roboter selber schon mehr Erfahrungen?

              Inwiefern?

              David G. D 2 Replies Last reply Reply Quote 0
              • David G.
                David G. @copystring last edited by David G.

                @copystring

                Der Roboter gibt doch bestimmt auch Meldungen ab wenn was nicht stimmt, nicht nur die Basis.

                Evtl welche von denen?

                water_shortage_status

                water_box_status

                water_box_carriage_status

                dust_collection_status

                1-2 andere Status gibt's ja auch noch.

                EDIT

                Ein paar Meldungen vom Roboter selber scheint es hier zu geben:
                https://hardmasterreset.com/xiaomi-roborock-error-list-and-solution-for-it/

                EDIT2

                Leider kein c&p möglich
                Screenshot_20230315_205950_Chrome.jpg

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

                  @copystring

                  Mir sind 2 Dinge aufgefallen in der Version 0.1.6.

                  • Der Datenpunkt connection bleibt immer auf "true" auch wenn ich den Sauger ausschalte. Auch nach mehreren Stunden ändert sich der Status nicht. Ein neustart des Adapters ändert den Status jedoch auch nicht.

                  • Unter FirmwareFeatures war auch in den früheren Versionen ein Datenpunkt zur Firmwareversion des Saugers. Den gibt es bei mir nicht mehr. Ist nicht so wichtig, wollte es trotzdem mal melden.

                  Falls du Logs brauchst gib bescheid.

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

                    @dimi said in Roborock Adapter tester gesucht:

                    @copystring

                    Mir sind 2 Dinge aufgefallen in der Version 0.1.6.

                    • Der Datenpunkt connection bleibt immer auf "true" auch wenn ich den Sauger ausschalte. Auch nach mehreren Stunden ändert sich der Status nicht. Ein neustart des Adapters ändert den Status jedoch auch nicht.

                    Das ist normal. Der Status kann nur die Verbindung zum Server anzeigen da die Verbindung vom Adapter halt nur zum Server von roborock geht und nicht direkt zum Sauger geht. Daher ist dieser grün solange der Adapter eine Verbindung zum Server hat.

                    • Unter FirmwareFeatures war auch in den früheren Versionen ein Datenpunkt zur Firmwareversion des Saugers. Den gibt es bei mir nicht mehr. Ist nicht so wichtig, wollte es trotzdem mal melden.

                    Falls du Logs brauchst gib bescheid.

                    Die Anzeige der Firmware könnte ich wieder einbauen. Das sollte kein Problem sein.

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

                      @copystring

                      Schade, ich dachte es ist wie in der APP. Wenn man den Sauger ausschaltet, dann wird er auch in der APP als offline Angezeigt. Sprich die Cloud kennt ja den Zustand sonst würde die APP den Sauger nicht als offline anzeigen.

                      Screenshot 2023-03-16 170536.png

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

                        @dimi said in Roborock Adapter tester gesucht:

                        @copystring

                        Schade, ich dachte es ist wie in der APP. Wenn man den Sauger ausschaltet, dann wird er auch in der APP als offline Angezeigt. Sprich die Cloud kennt ja den Zustand sonst würde die APP den Sauger nicht als offline anzeigen.

                        Screenshot 2023-03-16 170536.png

                        Ja. Ich könnte sicherlich Zustände für jeden Roboter einbauen. Der Adapter bleibt aber trotzdem grün.

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

                          @copystring said in Roborock Adapter tester gesucht:

                          @dimi said in Roborock Adapter tester gesucht:

                          @copystring

                          Schade, ich dachte es ist wie in der APP. Wenn man den Sauger ausschaltet, dann wird er auch in der APP als offline Angezeigt. Sprich die Cloud kennt ja den Zustand sonst würde die APP den Sauger nicht als offline anzeigen.

                          Screenshot 2023-03-16 170536.png

                          Ja. Ich könnte sicherlich Zustände für jeden Roboter einbauen. Der Adapter bleibt aber trotzdem grün.

                          In der dev branch ist das jetzt eingebaut. Außerdem sind dort auch alle anderen Informationen abgelegt, welche vorher nicht abgerufen wurden.
                          Das sieht dann so aus: 01da10f0-3d90-4fcc-b673-83b81ffde36b-image.png
                          https://github.com/copystring/ioBroker.roborock/tree/dev

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

                            @copystring

                            Heute die Meldung im IOBroker gesehen, dass der Roborock Adapter angehalten wurde, weil zu viele Neustarts.

                            Hier das Log:

                            2023-03-16 01:26:25.565 - info: host.raspberrypi Delete log file iobroker.2023-03-08.log.gz
                            2023-03-16 01:37:38.781 - warn: roborock.0 (11667) MQTT connection close.
                            2023-03-16 01:37:38.790 - warn: roborock.0 (11667) MQTT connection reconnect.
                            2023-03-16 02:19:39.184 - warn: roborock.0 (11667) State "roborock.0.Devices.5Im6TX0cm6mgxaWxHaEos7.consumables.enable" has no existing object, this might lead to an error in future versions
                            2023-03-16 02:19:39.228 - warn: roborock.0 (11667) State "roborock.0.Devices.5Im6TX0cm6mgxaWxHaEos7.consumables.current_integral" has no existing object, this might lead to an error in future versions
                            2023-03-16 02:19:39.229 - warn: roborock.0 (11667) State "roborock.0.Devices.5Im6TX0cm6mgxaWxHaEos7.consumables.current_high" has no existing object, this might lead to an error in future versions
                            2023-03-16 02:19:39.230 - warn: roborock.0 (11667) State "roborock.0.Devices.5Im6TX0cm6mgxaWxHaEos7.consumables.current_low" has no existing object, this might lead to an error in future versions
                            2023-03-16 02:19:39.231 - warn: roborock.0 (11667) State "roborock.0.Devices.5Im6TX0cm6mgxaWxHaEos7.consumables.stall_time" has no existing object, this might lead to an error in future versions
                            2023-03-16 04:37:38.782 - warn: roborock.0 (11667) MQTT connection close.
                            2023-03-16 04:37:38.784 - warn: roborock.0 (11667) MQTT connection reconnect.
                            2023-03-16 06:00:00.068 - info: roborock.0 (11667) Scheduled restart.
                            2023-03-16 06:00:00.080 - info: roborock.0 (11667) terminating
                            2023-03-16 06:00:00.083 - info: roborock.0 (11667) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
                            2023-03-16 06:00:00.076 - info: alexa2.0 (11823) Scheduled restart.
                            2023-03-16 06:00:00.089 - info: javascript.0 (11724) Scheduled restart.
                            2023-03-16 06:00:00.103 - info: javascript.0 (11724) Stop script script.js.common.Alexa_TTS
                            2023-03-16 06:00:00.104 - info: javascript.0 (11724) Stop script script.js.common.Landroid_OLM_Zonen_Planer
                            2023-03-16 06:00:00.104 - info: javascript.0 (11724) Stop script script.js.common.Roborock_V5_Alexa_Bereichsreinigung
                            2023-03-16 06:00:00.117 - info: javascript.0 (11724) terminating
                            2023-03-16 06:00:00.119 - info: javascript.0 (11724) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
                            2023-03-16 06:00:00.138 - info: alexa2.0 (11823) terminating
                            2023-03-16 06:00:00.140 - info: alexa2.0 (11823) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
                            2023-03-16 06:00:00.741 - info: host.raspberrypi instance system.adapter.roborock.0 scheduled normal terminated and will be restarted on schedule.
                            2023-03-16 06:00:00.743 - info: host.raspberrypi Restart adapter system.adapter.roborock.0 because enabled
                            2023-03-16 06:00:00.820 - info: host.raspberrypi instance system.adapter.javascript.0 scheduled normal terminated and will be restarted on schedule.
                            2023-03-16 06:00:00.820 - info: host.raspberrypi Restart adapter system.adapter.javascript.0 because enabled
                            2023-03-16 06:00:00.973 - info: host.raspberrypi instance system.adapter.alexa2.0 scheduled normal terminated and will be restarted on schedule.
                            2023-03-16 06:00:00.974 - info: host.raspberrypi Restart adapter system.adapter.alexa2.0 because enabled
                            2023-03-16 06:00:01.968 - info: host.raspberrypi instance system.adapter.roborock.0 started with pid 17361
                            2023-03-16 06:00:02.090 - info: host.raspberrypi instance system.adapter.javascript.0 started with pid 17368
                            2023-03-16 06:00:02.188 - info: host.raspberrypi instance system.adapter.alexa2.0 started with pid 17374
                            2023-03-16 06:00:05.746 - info: roborock.0 (17361) starting. Version 0.1.6 (non-npm: copystring/ioBroker.roborock) in /opt/iobroker/node_modules/iobroker.roborock, node: v16.19.0, js-controller: 4.0.24
                            2023-03-16 06:00:05.920 - info: alexa2.0 (17374) starting. Version 3.23.2 in /opt/iobroker/node_modules/iobroker.alexa2, node: v16.19.0, js-controller: 4.0.24
                            2023-03-16 06:00:06.609 - info: roborock.0 (17361) MQTT initialized
                            2023-03-16 06:00:06.620 - info: alexa2.0 (17374) Starting Alexa2 adapter ... it can take several minutes to initialize all data. Please be patient! A done message is logged.
                            2023-03-16 06:00:07.302 - info: javascript.0 (17368) starting. Version 7.0.1 in /opt/iobroker/node_modules/iobroker.javascript, node: v16.19.0, js-controller: 4.0.24
                            2023-03-16 06:00:08.215 - info: javascript.0 (17368) requesting all states
                            2023-03-16 06:00:08.218 - info: javascript.0 (17368) requesting all objects
                            2023-03-16 06:00:09.907 - info: javascript.0 (17368) received all objects
                            2023-03-16 06:00:10.083 - info: javascript.0 (17368) received all states
                            2023-03-16 06:00:10.207 - info: javascript.0 (17368) Start javascript script.js.common.Alexa_TTS
                            2023-03-16 06:00:10.275 - info: javascript.0 (17368) script.js.common.Alexa_TTS: registered 1 subscription, 0 schedules, 0 messages, 0 logs and 0 file subscriptions
                            2023-03-16 06:00:10.276 - info: javascript.0 (17368) Start javascript script.js.common.Landroid_OLM_Zonen_Planer
                            2023-03-16 06:00:10.299 - info: javascript.0 (17368) script.js.common.Landroid_OLM_Zonen_Planer: registered 1 subscription, 0 schedules, 0 messages, 0 logs and 0 file subscriptions
                            2023-03-16 06:00:10.300 - info: javascript.0 (17368) Start javascript script.js.common.Roborock_V5_Alexa_Bereichsreinigung
                            2023-03-16 06:00:10.309 - info: javascript.0 (17368) script.js.common.Roborock_V5_Alexa_Bereichsreinigung: registered 2 subscriptions, 0 schedules, 0 messages, 0 logs and 0 file subscriptions
                            2023-03-16 06:00:11.181 - info: alexa2.0 (17374) Initialize all Device states ...
                            2023-03-16 06:01:03.452 - info: alexa2.0 (17374) No smart home devices to query
                            2023-03-16 06:01:04.742 - info: alexa2.0 (17374) Subscribing to states...
                            2023-03-16 06:01:04.747 - info: alexa2.0 (17374) Deleting the following states: ["Smart-Home-Devices.5d5e7f46-b56d-4d23-945c-8e75c66802c7","Smart-Home-Devices.5d5e7f46-b56d-4d23-945c-8e75c66802c7.#delete","Smart-Home-Devices.5d5e7f46-b56d-4d23-945c-8e75c66802c7.#enabled","Smart-Home-Devices.5d5e7f46-b56d-4d23-945c-8e75c66802c7.powerState"]
                            2023-03-16 06:01:06.672 - info: alexa2.0 (17374) Alexa-Push-Connection (macDms = true) established. Disable Polling
                            2023-03-16 06:01:20.146 - info: alexa2.0 (17374) Initialization Done ...
                            2023-03-16 06:55:45.666 - error: roborock.0 (17361) MQTT connection offline: undefined
                            2023-03-16 06:55:45.671 - warn: roborock.0 (17361) MQTT connection close.
                            2023-03-16 06:55:46.673 - warn: roborock.0 (17361) MQTT connection reconnect.
                            2023-03-16 07:10:06.399 - info: admin.0 (11592) ==> Connected system.user.admin from ::ffff:192.168.178.202
                            2023-03-16 07:11:41.409 - info: admin.0 (11592) <== Disconnect system.user.admin from ::ffff:192.168.178.202 admin
                            2023-03-16 09:00:08.086 - warn: roborock.0 (17361) MQTT connection close.
                            2023-03-16 09:00:08.087 - warn: roborock.0 (17361) MQTT connection reconnect.
                            2023-03-16 12:00:08.084 - warn: roborock.0 (17361) MQTT connection close.
                            2023-03-16 12:00:08.085 - warn: roborock.0 (17361) MQTT connection reconnect.
                            2023-03-16 13:34:08.429 - warn: roborock.0 (17361) State "roborock.0.Devices.5Im6TX0cm6mgxaWxHaEos7.consumables.msg_ver" has no existing object, this might lead to an error in future versions
                            2023-03-16 13:34:08.430 - warn: roborock.0 (17361) State "roborock.0.Devices.5Im6TX0cm6mgxaWxHaEos7.consumables.msg_seq" has no existing object, this might lead to an error in future versions
                            2023-03-16 13:34:08.431 - warn: roborock.0 (17361) State "roborock.0.Devices.5Im6TX0cm6mgxaWxHaEos7.consumables.state" has no existing object, this might lead to an error in future versions
                            2023-03-16 13:34:08.431 - warn: roborock.0 (17361) State "roborock.0.Devices.5Im6TX0cm6mgxaWxHaEos7.consumables.battery" has no existing object, this might lead to an error in future versions
                            2023-03-16 13:34:08.432 - warn: roborock.0 (17361) State "roborock.0.Devices.5Im6TX0cm6mgxaWxHaEos7.consumables.clean_time" has no existing object, this might lead to an error in future versions
                            2023-03-16 13:34:08.433 - warn: roborock.0 (17361) State "roborock.0.Devices.5Im6TX0cm6mgxaWxHaEos7.consumables.clean_area" has no existing object, this might lead to an error in future versions
                            2023-03-16 13:34:08.434 - warn: roborock.0 (17361) State "roborock.0.Devices.5Im6TX0cm6mgxaWxHaEos7.consumables.error_code" has no existing object, this might lead to an error in future versions
                            2023-03-16 13:34:08.434 - warn: roborock.0 (17361) State "roborock.0.Devices.5Im6TX0cm6mgxaWxHaEos7.consumables.map_present" has no existing object, this might lead to an error in future versions
                            2023-03-16 13:34:08.435 - warn: roborock.0 (17361) State "roborock.0.Devices.5Im6TX0cm6mgxaWxHaEos7.consumables.in_cleaning" has no existing object, this might lead to an error in future versions
                            2023-03-16 13:34:08.436 - warn: roborock.0 (17361) State "roborock.0.Devices.5Im6TX0cm6mgxaWxHaEos7.consumables.in_returning" has no existing object, this might lead to an error in future versions
                            2023-03-16 13:34:08.436 - warn: roborock.0 (17361) State "roborock.0.Devices.5Im6TX0cm6mgxaWxHaEos7.consumables.in_fresh_state" has no existing object, this might lead to an error in future versions
                            2023-03-16 13:34:08.437 - warn: roborock.0 (17361) State "roborock.0.Devices.5Im6TX0cm6mgxaWxHaEos7.consumables.lab_status" has no existing object, this might lead to an error in future versions
                            2023-03-16 13:34:08.437 - warn: roborock.0 (17361) State "roborock.0.Devices.5Im6TX0cm6mgxaWxHaEos7.consumables.water_box_status" has no existing object, this might lead to an error in future versions
                            2023-03-16 13:34:08.438 - warn: roborock.0 (17361) State "roborock.0.Devices.5Im6TX0cm6mgxaWxHaEos7.consumables.back_type" has no existing object, this might lead to an error in future versions
                            2023-03-16 13:34:08.438 - warn: roborock.0 (17361) State "roborock.0.Devices.5Im6TX0cm6mgxaWxHaEos7.consumables.wash_phase" has no existing object, this might lead to an error in future versions
                            2023-03-16 13:34:08.439 - warn: roborock.0 (17361) State "roborock.0.Devices.5Im6TX0cm6mgxaWxHaEos7.consumables.wash_ready" has no existing object, this might lead to an error in future versions
                            2023-03-16 13:34:08.439 - warn: roborock.0 (17361) State "roborock.0.Devices.5Im6TX0cm6mgxaWxHaEos7.consumables.fan_power" has no existing object, this might lead to an error in future versions
                            2023-03-16 13:34:08.440 - warn: roborock.0 (17361) State "roborock.0.Devices.5Im6TX0cm6mgxaWxHaEos7.consumables.dnd_enabled" has no existing object, this might lead to an error in future versions
                            2023-03-16 13:34:08.440 - warn: roborock.0 (17361) State "roborock.0.Devices.5Im6TX0cm6mgxaWxHaEos7.consumables.map_status" has no existing object, this might lead to an error in future versions
                            2023-03-16 13:34:08.441 - warn: roborock.0 (17361) State "roborock.0.Devices.5Im6TX0cm6mgxaWxHaEos7.consumables.is_locating" has no existing object, this might lead to an error in future versions
                            2023-03-16 13:34:08.441 - warn: roborock.0 (17361) State "roborock.0.Devices.5Im6TX0cm6mgxaWxHaEos7.consumables.lock_status" has no existing object, this might lead to an error in future versions
                            2023-03-16 13:34:08.442 - warn: roborock.0 (17361) State "roborock.0.Devices.5Im6TX0cm6mgxaWxHaEos7.consumables.water_box_mode" has no existing object, this might lead to an error in future versions
                            2023-03-16 13:34:08.442 - warn: roborock.0 (17361) State "roborock.0.Devices.5Im6TX0cm6mgxaWxHaEos7.consumables.water_box_carriage_status" has no existing object, this might lead to an error in future versions
                            2023-03-16 13:34:08.443 - warn: roborock.0 (17361) State "roborock.0.Devices.5Im6TX0cm6mgxaWxHaEos7.consumables.mop_forbidden_enable" has no existing object, this might lead to an error in future versions
                            2023-03-16 13:34:08.443 - warn: roborock.0 (17361) State "roborock.0.Devices.5Im6TX0cm6mgxaWxHaEos7.consumables.adbumper_status" has no existing object, this might lead to an error in future versions
                            2023-03-16 13:34:08.444 - warn: roborock.0 (17361) State "roborock.0.Devices.5Im6TX0cm6mgxaWxHaEos7.consumables.water_shortage_status" has no existing object, this might lead to an error in future versions
                            2023-03-16 13:34:08.444 - warn: roborock.0 (17361) State "roborock.0.Devices.5Im6TX0cm6mgxaWxHaEos7.consumables.dock_type" has no existing object, this might lead to an error in future versions
                            2023-03-16 13:34:08.445 - warn: roborock.0 (17361) State "roborock.0.Devices.5Im6TX0cm6mgxaWxHaEos7.consumables.dust_collection_status" has no existing object, this might lead to an error in future versions
                            2023-03-16 13:34:08.445 - warn: roborock.0 (17361) State "roborock.0.Devices.5Im6TX0cm6mgxaWxHaEos7.consumables.auto_dust_collection" has no existing object, this might lead to an error in future versions
                            2023-03-16 13:34:08.446 - warn: roborock.0 (17361) State "roborock.0.Devices.5Im6TX0cm6mgxaWxHaEos7.consumables.mop_mode" has no existing object, this might lead to an error in future versions
                            2023-03-16 13:34:08.446 - warn: roborock.0 (17361) State "roborock.0.Devices.5Im6TX0cm6mgxaWxHaEos7.consumables.debug_mode" has no existing object, this might lead to an error in future versions
                            2023-03-16 13:34:08.469 - warn: roborock.0 (17361) State "roborock.0.Devices.5Im6TX0cm6mgxaWxHaEos7.consumables.switch_map_mode" has no existing object, this might lead to an error in future versions
                            2023-03-16 13:34:08.470 - warn: roborock.0 (17361) State "roborock.0.Devices.5Im6TX0cm6mgxaWxHaEos7.consumables.dock_error_status" has no existing object, this might lead to an error in future versions
                            2023-03-16 13:34:08.471 - warn: roborock.0 (17361) State "roborock.0.Devices.5Im6TX0cm6mgxaWxHaEos7.consumables.charge_status" has no existing object, this might lead to an error in future versions
                            2023-03-16 13:34:08.471 - warn: roborock.0 (17361) State "roborock.0.Devices.5Im6TX0cm6mgxaWxHaEos7.consumables.unsave_map_reason" has no existing object, this might lead to an error in future versions
                            2023-03-16 13:34:08.472 - warn: roborock.0 (17361) State "roborock.0.Devices.5Im6TX0cm6mgxaWxHaEos7.consumables.unsave_map_flag" has no existing object, this might lead to an error in future versions
                            2023-03-16 15:00:08.220 - warn: roborock.0 (17361) MQTT connection close.
                            2023-03-16 15:00:08.222 - warn: roborock.0 (17361) MQTT connection reconnect.
                            2023-03-16 18:00:08.088 - warn: roborock.0 (17361) MQTT connection close.
                            2023-03-16 18:00:08.089 - warn: roborock.0 (17361) MQTT connection reconnect.
                            2023-03-16 19:37:13.320 - info: admin.0 (11592) Adapter rating updated
                            2023-03-16 19:37:23.232 - info: admin.0 (11592) Request actual repository...
                            2023-03-16 19:37:23.998 - info: host.raspberrypi Updating repository "Beta" under "http://download.iobroker.net/sources-dist-latest.json"
                            2023-03-16 19:37:31.500 - info: admin.0 (11592) Repository received successfully.
                            2023-03-16 19:45:43.592 - info: admin.0 (11592) ==> Connected system.user.admin from ::ffff:192.168.178.62
                            2023-03-16 19:46:38.601 - info: admin.0 (11592) <== Disconnect system.user.admin from ::ffff:192.168.178.62 admin
                            2023-03-16 19:46:57.741 - info: admin.0 (11592) ==> Connected system.user.admin from ::ffff:192.168.178.62
                            2023-03-16 19:47:22.743 - info: admin.0 (11592) <== Disconnect system.user.admin from ::ffff:192.168.178.62 admin
                            2023-03-16 19:47:52.430 - info: admin.0 (11592) ==> Connected system.user.admin from ::ffff:192.168.178.62
                            2023-03-16 19:48:22.436 - info: admin.0 (11592) <== Disconnect system.user.admin from ::ffff:192.168.178.62 admin
                            2023-03-16 21:00:08.085 - warn: roborock.0 (17361) MQTT connection close.
                            2023-03-16 21:00:08.087 - warn: roborock.0 (17361) MQTT connection reconnect.
                            2023-03-16 21:59:30.630 - error: roborock.0 (17361) 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-03-16 21:59:30.631 - error: roborock.0 (17361) unhandled promise rejection: getaddrinfo ENOTFOUND api-eu.roborock.com
                            2023-03-16 21:59:30.634 - error: roborock.0 (17361) Error: getaddrinfo ENOTFOUND api-eu.roborock.com
                            at Function.AxiosError.from (/opt/iobroker/node_modules/iobroker.roborock/node_modules/axios/dist/node/axios.cjs:825:14)
                            at RedirectableRequest.handleRequestError (/opt/iobroker/node_modules/iobroker.roborock/node_modules/axios/dist/node/axios.cjs:2973:25)
                            at RedirectableRequest.emit (node:events:513:28)
                            at ClientRequest.eventHandlers. (/opt/iobroker/node_modules/follow-redirects/index.js:14:24)
                            at ClientRequest.emit (node:events:513:28)
                            at TLSSocket.socketErrorListener (node:_http_client:494:9)
                            at TLSSocket.emit (node:events:513:28)
                            at emitErrorNT (node:internal/streams/destroy:157:8)
                            at emitErrorCloseNT (node:internal/streams/destroy:122:3)
                            at processTicksAndRejections (node:internal/process/task_queues:83:21)
                            2023-03-16 21:59:30.635 - error: roborock.0 (17361) Exception-Code: ENOTFOUND: getaddrinfo ENOTFOUND api-eu.roborock.com
                            2023-03-16 21:59:30.643 - info: roborock.0 (17361) terminating
                            2023-03-16 21:59:30.647 - warn: roborock.0 (17361) Terminated (UNCAUGHT_EXCEPTION): Without reason
                            2023-03-16 21:59:31.326 - error: host.raspberrypi instance system.adapter.roborock.0 terminated with code 6 (UNCAUGHT_EXCEPTION)
                            2023-03-16 21:59:31.328 - info: host.raspberrypi Restart adapter system.adapter.roborock.0 because enabled
                            2023-03-16 21:59:33.697 - info: host.raspberrypi instance system.adapter.roborock.0 started with pid 26016
                            2023-03-16 21:59:36.695 - info: roborock.0 (26016) starting. Version 0.1.6 (non-npm: copystring/ioBroker.roborock) in /opt/iobroker/node_modules/iobroker.roborock, node: v16.19.0, js-controller: 4.0.24
                            2023-03-16 21:59:55.416 - error: roborock.0 (26016) 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-03-16 21:59:55.417 - error: roborock.0 (26016) unhandled promise rejection: getaddrinfo ENOTFOUND euiot.roborock.com
                            2023-03-16 21:59:55.419 - error: roborock.0 (26016) Error: getaddrinfo ENOTFOUND euiot.roborock.com
                            at Function.AxiosError.from (/opt/iobroker/node_modules/iobroker.roborock/node_modules/axios/dist/node/axios.cjs:825:14)
                            at RedirectableRequest.handleRequestError (/opt/iobroker/node_modules/iobroker.roborock/node_modules/axios/dist/node/axios.cjs:2973:25)
                            at RedirectableRequest.emit (node:events:513:28)
                            at ClientRequest.eventHandlers. (/opt/iobroker/node_modules/follow-redirects/index.js:14:24)
                            at ClientRequest.emit (node:events:513:28)
                            at TLSSocket.socketErrorListener (node:_http_client:494:9)
                            at TLSSocket.emit (node:events:513:28)
                            at emitErrorNT (node:internal/streams/destroy:157:8)
                            at emitErrorCloseNT (node:internal/streams/destroy:122:3)
                            at processTicksAndRejections (node:internal/process/task_queues:83:21)
                            2023-03-16 21:59:55.420 - error: roborock.0 (26016) Exception-Code: ENOTFOUND: getaddrinfo ENOTFOUND euiot.roborock.com
                            2023-03-16 21:59:55.429 - info: roborock.0 (26016) terminating
                            2023-03-16 21:59:55.431 - warn: roborock.0 (26016) Terminated (UNCAUGHT_EXCEPTION): Without reason
                            2023-03-16 21:59:56.046 - error: host.raspberrypi instance system.adapter.roborock.0 terminated with code 6 (UNCAUGHT_EXCEPTION)
                            2023-03-16 21:59:56.047 - info: host.raspberrypi Restart adapter system.adapter.roborock.0 because enabled
                            2023-03-16 21:59:57.202 - info: host.raspberrypi instance system.adapter.roborock.0 started with pid 26074
                            2023-03-16 22:00:00.215 - info: roborock.0 (26074) starting. Version 0.1.6 (non-npm: copystring/ioBroker.roborock) in /opt/iobroker/node_modules/iobroker.roborock, node: v16.19.0, js-controller: 4.0.24
                            2023-03-16 22:00:20.248 - error: roborock.0 (26074) 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-03-16 22:00:20.250 - error: roborock.0 (26074) unhandled promise rejection: getaddrinfo ENOTFOUND euiot.roborock.com
                            2023-03-16 22:00:20.252 - error: roborock.0 (26074) Error: getaddrinfo ENOTFOUND euiot.roborock.com
                            at Function.AxiosError.from (/opt/iobroker/node_modules/iobroker.roborock/node_modules/axios/dist/node/axios.cjs:825:14)
                            at RedirectableRequest.handleRequestError (/opt/iobroker/node_modules/iobroker.roborock/node_modules/axios/dist/node/axios.cjs:2973:25)
                            at RedirectableRequest.emit (node:events:513:28)
                            at ClientRequest.eventHandlers. (/opt/iobroker/node_modules/follow-redirects/index.js:14:24)
                            at ClientRequest.emit (node:events:513:28)
                            at TLSSocket.socketErrorListener (node:_http_client:494:9)
                            at TLSSocket.emit (node:events:513:28)
                            at emitErrorNT (node:internal/streams/destroy:157:8)
                            at emitErrorCloseNT (node:internal/streams/destroy:122:3)
                            at processTicksAndRejections (node:internal/process/task_queues:83:21)
                            2023-03-16 22:00:20.253 - error: roborock.0 (26074) Exception-Code: ENOTFOUND: getaddrinfo ENOTFOUND euiot.roborock.com
                            2023-03-16 22:00:20.264 - info: roborock.0 (26074) terminating
                            2023-03-16 22:00:20.266 - warn: roborock.0 (26074) Terminated (UNCAUGHT_EXCEPTION): Without reason
                            2023-03-16 22:00:20.879 - error: host.raspberrypi instance system.adapter.roborock.0 terminated with code 6 (UNCAUGHT_EXCEPTION)
                            2023-03-16 22:00:20.881 - info: host.raspberrypi Restart adapter system.adapter.roborock.0 because enabled
                            2023-03-16 22:00:20.881 - warn: host.raspberrypi Do not restart adapter system.adapter.roborock.0 because restart loop detected
                            2023-03-16 22:01:06.810 - info: alexa2.0 (17374) Alexa-Push-Connection disconnected - retry: Retry Connection in 10s
                            2023-03-16 22:01:17.608 - info: alexa2.0 (17374) Alexa-Push-Connection (macDms = true) established. Disable Polling
                            
                            
                            1 Reply Last reply Reply Quote 0
                            • B
                              bongsao last edited by wendy2702

                              host.HomsServer
                              2023-03-17 16:27:42.452	error	instance system.adapter.roborock.0 terminated with code 6 (UNCAUGHT_EXCEPTION)
                              host.HomsServer
                              2023-03-17 16:27:42.452	error	Caught by controller[1]: at /opt/iobroker/node_modules/iobroker.roborock/lib/vacuum.js:376:139
                              host.HomsServer
                              2023-03-17 16:27:42.451	error	Caught by controller[1]: TypeError: Cannot read properties of undefined (reading 'toString')
                              host.HomsServer
                              2023-03-17 16:27:42.451	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
                              2023-03-17 16:27:41.878	error	Cannot read properties of undefined (reading 'toString')
                              
                              roborock.0
                              2023-03-17 16:27:41.878	error	TypeError: Cannot read properties of undefined (reading 'toString') at /opt/iobroker/node_modules/iobroker.roborock/lib/vacuum.js:376:139
                              
                              roborock.0
                              2023-03-17 16:27:41.876	error	unhandled promise rejection: Cannot read properties of undefined (reading 'toString')
                              
                              roborock.0
                              2023-03-17 16:27:41.875	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().
                              

                              mit Version 0.1.6

                              MOD EDIT: LOG IN CODE TAGS </> GESETZT

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

                                @copystring sagte in Roborock Adapter tester gesucht:

                                In der dev branch ist das jetzt eingebaut. Außerdem sind dort auch alle anderen Informationen abgelegt, welche vorher nicht abgerufen wurden.
                                Das sieht dann so aus:
                                https://github.com/copystring/ioBroker.roborock/tree/dev

                                Danke habe es getestet. Die Infos wie Firmware usw. sind alle wieder da. Und auch der Onlinestatus des Saugers wird angezeigt und auch zeitnah aktualisiert. 👍

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

                                  @copystring

                                  Hi, hier mal mein Debug-File, nachdem er wieder nach einem Raum abgebrochen hat und zur Station zurückgefahren ist.

                                  DebugFileRoborock.txt

                                  Ich hoffe, das hilft irgendwie weiter.
                                  Ich glaube bei Zeile 716 ist er fertig gewesen und zur Station zurückgefahren.

                                  Gruß,
                                  Menfis

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

                                    @menfis said in Roborock Adapter tester gesucht:

                                    @copystring

                                    Hi, hier mal mein Debug-File, nachdem er wieder nach einem Raum abgebrochen hat und zur Station zurückgefahren ist.

                                    DebugFileRoborock.txt

                                    Ich hoffe, das hilft irgendwie weiter.
                                    Ich glaube bei Zeile 716 ist er fertig gewesen und zur Station zurückgefahren.

                                    Gruß,
                                    Menfis

                                    Ok. Ich müsste nur noch wissen, welche Räume tatsächlich gereinigt werden sollten. Vielleicht „Kleiner Flur“ und „Küche“?

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

                                      @copystring
                                      Ja, richtig.
                                      Und nach dem kleinen Flur war einfach wieder Schluss.
                                      Hab ich vielleicht etwas falsch eingestellt oder darf ein Raumname vielleicht keine Umlaute beinhalten?

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

                                        @menfis said in Roborock Adapter tester gesucht:

                                        @copystring
                                        Ja, richtig.
                                        Und nach dem kleinen Flur war einfach wieder Schluss.
                                        Hab ich vielleicht etwas falsch eingestellt oder darf ein Raumname vielleicht keine Umlaute beinhalten?

                                        Die Räume werden nur anhand von IDs übergeben. Die Protokolle zeigen mir, dass dies sauber durchlief. Wenn du das machst, sieht man dann in der App, welche Räume der Roboter reinigen soll?

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

                                          @copystring
                                          Ja, sieht man. Allerdings wird immer nur ein einziger Raum bunt.

                                          copystring 1 Reply Last reply Reply Quote 0
                                          • David G.
                                            David G. last edited by

                                            Gibt's für die beiden eigentlich auch einen Datenpunkt?

                                            Screenshot_20230322_081558_Roborock.jpg

                                            Finde nichts, wo ich denke dass es was entsprechendes ist.

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

                                            Support us

                                            ioBroker
                                            Community Adapters
                                            Donate

                                            881
                                            Online

                                            31.6k
                                            Users

                                            79.5k
                                            Topics

                                            1.3m
                                            Posts

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