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 goes Matter ... Matter Adapter in Stable

    • 15. 05. Wartungsarbeiten am ioBroker Forum

    • Monatsrückblick - April 2025

    Roborock Adapter tester gesucht

    This topic has been deleted. Only users with topic management privileges can see it.
    • D
      DonToben @copystring last edited by DonToben

      @dontoben said in Roborock Adapter tester gesucht:

      @copystring

      Mit dem letzten dev branch habe ich ständig folgende Meldungen.

      2023-04-16 00:00:11.387 - warn: roborock.0 (31163) MQTT connection close.
2023-04-16 00:00:11.396 - warn: roborock.0 (31163) MQTT connection reconnect.
2023-04-16 00:00:11.471 - info: roborock.0 (31163) State value to set for "roborock.0.Devices.5Im6TX0cm6mgxaWxHaEos7.updateStatus.updatable" has to be type "string" but received type "boolean"
2023-04-16 00:00:21.899 - error: roborock.0 (31163) Failed to execute get_room_mapping. Error: Error: Request with id 6866 timed out after 10 seconds for response.102
2023-04-16 00:08:21.905 - error: roborock.0 (31163) Failed to execute get_water_box_custom_mode. Error: Error: Request with id 5048 timed out after 10 seconds for response.102
2023-04-16 00:17:21.905 - error: roborock.0 (31163) Failed to execute get_consumable. Error: Error: Request with id 8491 timed out after 10 seconds for response.102
2023-04-16 00:17:21.906 - error: roborock.0 (31163) Failed to execute get_carpet_clean_mode. Error: Error: Request with id 2782 timed out after 10 seconds for response.102
2023-04-16 00:21:21.907 - error: roborock.0 (31163) Failed to execute get_room_mapping. Error: Error: Request with id 2447 timed out after 10 seconds for response.102
2023-04-16 00:22:21.906 - error: roborock.0 (31163) Failed to execute get_room_mapping. Error: Error: Request with id 6434 timed out after 10 seconds for response.102
2023-04-16 00:24:21.906 - error: roborock.0 (31163) Failed to execute get_status. Error: Error: Request with id 9671 timed out after 10 seconds for response.102
2023-04-16 00:24:21.908 - error: roborock.0 (31163) Failed to execute get_carpet_mode. Error: Error: Request with id 4780 timed out after 10 seconds for response.102
2023-04-16 00:44:21.914 - error: roborock.0 (31163) Failed to execute get_carpet_mode. Error: Error: Request with id 7326 timed out after 10 seconds for response.102
2023-04-16 00:54:21.916 - error: roborock.0 (31163) Failed to execute get_status. Error: Error: Request with id 8849 timed out after 10 seconds for response.102
2023-04-16 01:02:21.924 - error: roborock.0 (31163) Failed to execute get_carpet_mode. Error: Error: Request with id 2613 timed out after 10 seconds for response.102
2023-04-16 01:04:21.924 - error: roborock.0 (31163) Failed to execute get_water_box_custom_mode. Error: Error: Request with id 9896 timed out after 10 seconds for response.102
2023-04-16 01:24:21.935 - error: roborock.0 (31163) Failed to execute get_network_info. Error: Error: Request with id 2610 timed out after 10 seconds for response.102
2023-04-16 01:39:21.945 - error: roborock.0 (31163) Failed to execute get_carpet_mode. Error: Error: Request with id 4178 timed out after 10 seconds for response.102
2023-04-16 02:26:25.831 - info: host.raspberrypi Delete log file iobroker.2023-04-08.log.gz
2023-04-16 02:29:21.967 - error: roborock.0 (31163) Failed to execute get_network_info. Error: Error: Request with id 9757 timed out after 10 seconds for response.102
2023-04-16 02:29:21.968 - error: roborock.0 (31163) Failed to execute get_carpet_mode. Error: Error: Request with id 9992 timed out after 10 seconds for response.102
2023-04-16 02:31:21.970 - error: roborock.0 (31163) Failed to execute get_room_mapping. Error: Error: Request with id 5967 timed out after 10 seconds for response.102
2023-04-16 02:45:21.976 - error: roborock.0 (31163) Failed to execute get_carpet_mode. Error: Error: Request with id 6739 timed out after 10 seconds for response.102
2023-04-16 03:00:11.388 - warn: roborock.0 (31163) MQTT connection close.
2023-04-16 03:00:11.389 - warn: roborock.0 (31163) MQTT connection reconnect.
2023-04-16 03:00:11.611 - info: roborock.0 (31163) State value to set for "roborock.0.Devices.5Im6TX0cm6mgxaWxHaEos7.updateStatus.updatable" has to be type "string" but received type "boolean"
2023-04-16 03:02:21.981 - error: roborock.0 (31163) Failed to execute get_network_info. Error: Error: Request with id 7462 timed out after 10 seconds for response.102
2023-04-16 03:02:21.983 - error: roborock.0 (31163) Failed to execute get_water_box_custom_mode. Error: Error: Request with id 9020 timed out after 10 seconds for response.102
2023-04-16 03:05:21.983 - error: roborock.0 (31163) Failed to execute get_status. Error: Error: Request with id 9954 timed out after 10 seconds for response.102
2023-04-16 03:05:21.984 - error: roborock.0 (31163) Failed to execute get_consumable. Error: Error: Request with id 3501 timed out after 10 seconds for response.102
2023-04-16 03:05:21.984 - error: roborock.0 (31163) Failed to execute get_network_info. Error: Error: Request with id 6613 timed out after 10 seconds for response.102
2023-04-16 03:05:21.985 - error: roborock.0 (31163) Failed to execute get_carpet_mode. Error: Error: Request with id 3573 timed out after 10 seconds for response.102
2023-04-16 03:05:21.986 - error: roborock.0 (31163) Failed to execute get_carpet_clean_mode. Error: Error: Request with id 4264 timed out after 10 seconds for response.102
2023-04-16 03:05:21.986 - error: roborock.0 (31163) Failed to execute get_water_box_custom_mode. Error: Error: Request with id 6112 timed out after 10 seconds for response.102
2023-04-16 03:05:21.987 - error: roborock.0 (31163) Failed to execute get_room_mapping. Error: Error: Request with id 9996 timed out after 10 seconds for response.102
2023-04-16 03:36:21.998 - error: roborock.0 (31163) Failed to execute get_consumable. Error: Error: Request with id 8101 timed out after 10 seconds for response.102
2023-04-16 03:36:21.999 - error: roborock.0 (31163) Failed to execute get_carpet_clean_mode. Error: Error: Request with id 1292 timed out after 10 seconds for response.102
2023-04-16 03:40:22.002 - error: roborock.0 (31163) Failed to execute get_status. Error: Error: Request with id 5963 timed out after 10 seconds for response.102
2023-04-16 03:51:22.009 - error: roborock.0 (31163) Failed to execute get_consumable. Error: Error: Request with id 4946 timed out after 10 seconds for response.102
2023-04-16 03:54:22.010 - error: roborock.0 (31163) Failed to execute get_consumable. Error: Error: Request with id 1316 timed out after 10 seconds for response.102
2023-04-16 03:54:22.011 - error: roborock.0 (31163) Failed to execute get_carpet_clean_mode. Error: Error: Request with id 1181 timed out after 10 seconds for response.102
2023-04-16 03:55:22.011 - error: roborock.0 (31163) Failed to execute get_consumable. Error: Error: Request with id 2767 timed out after 10 seconds for response.102
2023-04-16 03:58:22.015 - error: roborock.0 (31163) Failed to execute get_status. Error: Error: Request with id 2554 timed out after 10 seconds for response.102
2023-04-16 03:58:22.016 - error: roborock.0 (31163) Failed to execute get_carpet_mode. Error: Error: Request with id 2289 timed out after 10 seconds for response.102
2023-04-16 03:58:22.018 - error: roborock.0 (31163) Failed to execute get_room_mapping. Error: Error: Request with id 4789 timed out after 10 seconds for response.102
2023-04-16 04:03:22.022 - error: roborock.0 (31163) Failed to execute get_room_mapping. Error: Error: Request with id 9611 timed out after 10 seconds for response.102
2023-04-16 04:25:22.038 - error: roborock.0 (31163) Failed to execute get_carpet_mode. Error: Error: Request with id 2463 timed out after 10 seconds for response.102
2023-04-16 04:34:22.040 - error: roborock.0 (31163) Failed to execute get_status. Error: Error: Request with id 5493 timed out after 10 seconds for response.102
2023-04-16 04:57:22.053 - error: roborock.0 (31163) Failed to execute get_status. Error: Error: Request with id 1654 timed out after 10 seconds for response.102
2023-04-16 05:06:22.063 - error: roborock.0 (31163) Failed to execute get_carpet_clean_mode. Error: Error: Request with id 3276 timed out after 10 seconds for response.102
2023-04-16 05:25:22.074 - error: roborock.0 (31163) Failed to execute get_status. Error: Error: Request with id 1712 timed out after 10 seconds for response.102
2023-04-16 05:25:22.074 - error: roborock.0 (31163) Failed to execute get_carpet_mode. Error: Error: Request with id 6715 timed out after 10 seconds for response.102
2023-04-16 06:00:00.070 - info: alexa2.0 (31244) Scheduled restart.
2023-04-16 06:00:00.092 - info: roborock.0 (31163) Scheduled restart.
2023-04-16 06:00:00.101 - info: alexa2.0 (31244) terminating

      Hast du deinen RPi mal neu gestartet? Das liegt wahrscheinlich nicht an meinem Adapter, sondern an irgendwas anderen.

      Probiere ich aus. Aber obwohl die Meldungen kommen, lässt sich der Roborock einwandfrei über den Adapter steuern.

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

        @copystring sagte in Roborock Adapter tester gesucht:

        Oder meinst du, dass speichern der Zeiten direkt im Roboter? Ja, dann kann ich mir das angucken.

        Ja, um sicherzustellen, dass die Reinigung auch ohne eine Verbindung zum Internet bzw. W-LAN startet.

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

          @dontoben said in Roborock Adapter tester gesucht:

          @dontoben said in Roborock Adapter tester gesucht:

          @copystring

          Mit dem letzten dev branch habe ich ständig folgende Meldungen.

          2023-04-16 00:00:11.387 - warn: roborock.0 (31163) MQTT connection close.
2023-04-16 00:00:11.396 - warn: roborock.0 (31163) MQTT connection reconnect.
2023-04-16 00:00:11.471 - info: roborock.0 (31163) State value to set for "roborock.0.Devices.5Im6TX0cm6mgxaWxHaEos7.updateStatus.updatable" has to be type "string" but received type "boolean"
2023-04-16 00:00:21.899 - error: roborock.0 (31163) Failed to execute get_room_mapping. Error: Error: Request with id 6866 timed out after 10 seconds for response.102
2023-04-16 00:08:21.905 - error: roborock.0 (31163) Failed to execute get_water_box_custom_mode. Error: Error: Request with id 5048 timed out after 10 seconds for response.102
2023-04-16 00:17:21.905 - error: roborock.0 (31163) Failed to execute get_consumable. Error: Error: Request with id 8491 timed out after 10 seconds for response.102
2023-04-16 00:17:21.906 - error: roborock.0 (31163) Failed to execute get_carpet_clean_mode. Error: Error: Request with id 2782 timed out after 10 seconds for response.102
2023-04-16 00:21:21.907 - error: roborock.0 (31163) Failed to execute get_room_mapping. Error: Error: Request with id 2447 timed out after 10 seconds for response.102
2023-04-16 00:22:21.906 - error: roborock.0 (31163) Failed to execute get_room_mapping. Error: Error: Request with id 6434 timed out after 10 seconds for response.102
2023-04-16 00:24:21.906 - error: roborock.0 (31163) Failed to execute get_status. Error: Error: Request with id 9671 timed out after 10 seconds for response.102
2023-04-16 00:24:21.908 - error: roborock.0 (31163) Failed to execute get_carpet_mode. Error: Error: Request with id 4780 timed out after 10 seconds for response.102
2023-04-16 00:44:21.914 - error: roborock.0 (31163) Failed to execute get_carpet_mode. Error: Error: Request with id 7326 timed out after 10 seconds for response.102
2023-04-16 00:54:21.916 - error: roborock.0 (31163) Failed to execute get_status. Error: Error: Request with id 8849 timed out after 10 seconds for response.102
2023-04-16 01:02:21.924 - error: roborock.0 (31163) Failed to execute get_carpet_mode. Error: Error: Request with id 2613 timed out after 10 seconds for response.102
2023-04-16 01:04:21.924 - error: roborock.0 (31163) Failed to execute get_water_box_custom_mode. Error: Error: Request with id 9896 timed out after 10 seconds for response.102
2023-04-16 01:24:21.935 - error: roborock.0 (31163) Failed to execute get_network_info. Error: Error: Request with id 2610 timed out after 10 seconds for response.102
2023-04-16 01:39:21.945 - error: roborock.0 (31163) Failed to execute get_carpet_mode. Error: Error: Request with id 4178 timed out after 10 seconds for response.102
2023-04-16 02:26:25.831 - info: host.raspberrypi Delete log file iobroker.2023-04-08.log.gz
2023-04-16 02:29:21.967 - error: roborock.0 (31163) Failed to execute get_network_info. Error: Error: Request with id 9757 timed out after 10 seconds for response.102
2023-04-16 02:29:21.968 - error: roborock.0 (31163) Failed to execute get_carpet_mode. Error: Error: Request with id 9992 timed out after 10 seconds for response.102
2023-04-16 02:31:21.970 - error: roborock.0 (31163) Failed to execute get_room_mapping. Error: Error: Request with id 5967 timed out after 10 seconds for response.102
2023-04-16 02:45:21.976 - error: roborock.0 (31163) Failed to execute get_carpet_mode. Error: Error: Request with id 6739 timed out after 10 seconds for response.102
2023-04-16 03:00:11.388 - warn: roborock.0 (31163) MQTT connection close.
2023-04-16 03:00:11.389 - warn: roborock.0 (31163) MQTT connection reconnect.
2023-04-16 03:00:11.611 - info: roborock.0 (31163) State value to set for "roborock.0.Devices.5Im6TX0cm6mgxaWxHaEos7.updateStatus.updatable" has to be type "string" but received type "boolean"
2023-04-16 03:02:21.981 - error: roborock.0 (31163) Failed to execute get_network_info. Error: Error: Request with id 7462 timed out after 10 seconds for response.102
2023-04-16 03:02:21.983 - error: roborock.0 (31163) Failed to execute get_water_box_custom_mode. Error: Error: Request with id 9020 timed out after 10 seconds for response.102
2023-04-16 03:05:21.983 - error: roborock.0 (31163) Failed to execute get_status. Error: Error: Request with id 9954 timed out after 10 seconds for response.102
2023-04-16 03:05:21.984 - error: roborock.0 (31163) Failed to execute get_consumable. Error: Error: Request with id 3501 timed out after 10 seconds for response.102
2023-04-16 03:05:21.984 - error: roborock.0 (31163) Failed to execute get_network_info. Error: Error: Request with id 6613 timed out after 10 seconds for response.102
2023-04-16 03:05:21.985 - error: roborock.0 (31163) Failed to execute get_carpet_mode. Error: Error: Request with id 3573 timed out after 10 seconds for response.102
2023-04-16 03:05:21.986 - error: roborock.0 (31163) Failed to execute get_carpet_clean_mode. Error: Error: Request with id 4264 timed out after 10 seconds for response.102
2023-04-16 03:05:21.986 - error: roborock.0 (31163) Failed to execute get_water_box_custom_mode. Error: Error: Request with id 6112 timed out after 10 seconds for response.102
2023-04-16 03:05:21.987 - error: roborock.0 (31163) Failed to execute get_room_mapping. Error: Error: Request with id 9996 timed out after 10 seconds for response.102
2023-04-16 03:36:21.998 - error: roborock.0 (31163) Failed to execute get_consumable. Error: Error: Request with id 8101 timed out after 10 seconds for response.102
2023-04-16 03:36:21.999 - error: roborock.0 (31163) Failed to execute get_carpet_clean_mode. Error: Error: Request with id 1292 timed out after 10 seconds for response.102
2023-04-16 03:40:22.002 - error: roborock.0 (31163) Failed to execute get_status. Error: Error: Request with id 5963 timed out after 10 seconds for response.102
2023-04-16 03:51:22.009 - error: roborock.0 (31163) Failed to execute get_consumable. Error: Error: Request with id 4946 timed out after 10 seconds for response.102
2023-04-16 03:54:22.010 - error: roborock.0 (31163) Failed to execute get_consumable. Error: Error: Request with id 1316 timed out after 10 seconds for response.102
2023-04-16 03:54:22.011 - error: roborock.0 (31163) Failed to execute get_carpet_clean_mode. Error: Error: Request with id 1181 timed out after 10 seconds for response.102
2023-04-16 03:55:22.011 - error: roborock.0 (31163) Failed to execute get_consumable. Error: Error: Request with id 2767 timed out after 10 seconds for response.102
2023-04-16 03:58:22.015 - error: roborock.0 (31163) Failed to execute get_status. Error: Error: Request with id 2554 timed out after 10 seconds for response.102
2023-04-16 03:58:22.016 - error: roborock.0 (31163) Failed to execute get_carpet_mode. Error: Error: Request with id 2289 timed out after 10 seconds for response.102
2023-04-16 03:58:22.018 - error: roborock.0 (31163) Failed to execute get_room_mapping. Error: Error: Request with id 4789 timed out after 10 seconds for response.102
2023-04-16 04:03:22.022 - error: roborock.0 (31163) Failed to execute get_room_mapping. Error: Error: Request with id 9611 timed out after 10 seconds for response.102
2023-04-16 04:25:22.038 - error: roborock.0 (31163) Failed to execute get_carpet_mode. Error: Error: Request with id 2463 timed out after 10 seconds for response.102
2023-04-16 04:34:22.040 - error: roborock.0 (31163) Failed to execute get_status. Error: Error: Request with id 5493 timed out after 10 seconds for response.102
2023-04-16 04:57:22.053 - error: roborock.0 (31163) Failed to execute get_status. Error: Error: Request with id 1654 timed out after 10 seconds for response.102
2023-04-16 05:06:22.063 - error: roborock.0 (31163) Failed to execute get_carpet_clean_mode. Error: Error: Request with id 3276 timed out after 10 seconds for response.102
2023-04-16 05:25:22.074 - error: roborock.0 (31163) Failed to execute get_status. Error: Error: Request with id 1712 timed out after 10 seconds for response.102
2023-04-16 05:25:22.074 - error: roborock.0 (31163) Failed to execute get_carpet_mode. Error: Error: Request with id 6715 timed out after 10 seconds for response.102
2023-04-16 06:00:00.070 - info: alexa2.0 (31244) Scheduled restart.
2023-04-16 06:00:00.092 - info: roborock.0 (31163) Scheduled restart.
2023-04-16 06:00:00.101 - info: alexa2.0 (31244) terminating

          Hast du deinen RPi mal neu gestartet? Das liegt wahrscheinlich nicht an meinem Adapter, sondern an irgendwas anderen.

          Probiere ich aus. Aber obwohl die Meldungen kommen, lässt sich der Roborock einwandfrei über den Adapter steuern.

          Habe ein issue auf GitHub erstellt. Neustart des RPi brachte keine Besserung.

          P 1 Reply Last reply Reply Quote 2
          • P
            pad @DonToben last edited by

            Guten Tag!

            endlich gibt es ein solches Plugin, erstmal vielen Dank dafür.
            Ich habe den S7 MaxV Ultra und ich vermisse aktuelle eigentlich Hauptsächlich eine Funktion:

            Ich haber in der IOS Roborock App ein Programm erstellt, welche mir Automatisch eine Zone reinigt, wenn ich darauf tipper. Ist irgendwie geplant diese bereits angelegten Zonen ueber iobroker nutzen zu koennen? Konkret reinigt die Zone immer den Bereich vom Esstisch, wo die kleine gesessen hat.

            Mfg
            pad

            1 Reply Last reply Reply Quote 0
            • O
              oxident last edited by

              Hier gleiches Problem wie bei @DonToben
              Bei mir jedoch in einer "potenten" VM auf einem x86.

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

                @oxident

                Glaube auch nicht im Ansatz, dass sich derartige Fehler mit einer potenten vm von selber lösen ^^.

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

                  @david-g Naja, mehr RAM hilft ja auch gegen Memory-Leaks. Zumindest eine Weile 😁

                  Wollte damit auch nur sagen, scheint kein Raspi-Problem zu sein

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

                    @dontoben said in Roborock Adapter tester gesucht:

                    @copystring

                    Mit dem letzten dev branch habe ich ständig folgende Meldungen.

                    2023-04-16 00:00:11.387 - warn: roborock.0 (31163) MQTT connection close.
2023-04-16 00:00:11.396 - warn: roborock.0 (31163) MQTT connection reconnect.
2023-04-16 00:00:11.471 - info: roborock.0 (31163) State value to set for "roborock.0.Devices.5Im6TX0cm6mgxaWxHaEos7.updateStatus.updatable" has to be type "string" but received type "boolean"
2023-04-16 00:00:21.899 - error: roborock.0 (31163) Failed to execute get_room_mapping. Error: Error: Request with id 6866 timed out after 10 seconds for response.102
2023-04-16 00:08:21.905 - error: roborock.0 (31163) Failed to execute get_water_box_custom_mode. Error: Error: Request with id 5048 timed out after 10 seconds for response.102
2023-04-16 00:17:21.905 - error: roborock.0 (31163) Failed to execute get_consumable. Error: Error: Request with id 8491 timed out after 10 seconds for response.102
2023-04-16 00:17:21.906 - error: roborock.0 (31163) Failed to execute get_carpet_clean_mode. Error: Error: Request with id 2782 timed out after 10 seconds for response.102
2023-04-16 00:21:21.907 - error: roborock.0 (31163) Failed to execute get_room_mapping. Error: Error: Request with id 2447 timed out after 10 seconds for response.102
2023-04-16 00:22:21.906 - error: roborock.0 (31163) Failed to execute get_room_mapping. Error: Error: Request with id 6434 timed out after 10 seconds for response.102
2023-04-16 00:24:21.906 - error: roborock.0 (31163) Failed to execute get_status. Error: Error: Request with id 9671 timed out after 10 seconds for response.102
2023-04-16 00:24:21.908 - error: roborock.0 (31163) Failed to execute get_carpet_mode. Error: Error: Request with id 4780 timed out after 10 seconds for response.102
2023-04-16 00:44:21.914 - error: roborock.0 (31163) Failed to execute get_carpet_mode. Error: Error: Request with id 7326 timed out after 10 seconds for response.102
2023-04-16 00:54:21.916 - error: roborock.0 (31163) Failed to execute get_status. Error: Error: Request with id 8849 timed out after 10 seconds for response.102
2023-04-16 01:02:21.924 - error: roborock.0 (31163) Failed to execute get_carpet_mode. Error: Error: Request with id 2613 timed out after 10 seconds for response.102
2023-04-16 01:04:21.924 - error: roborock.0 (31163) Failed to execute get_water_box_custom_mode. Error: Error: Request with id 9896 timed out after 10 seconds for response.102
2023-04-16 01:24:21.935 - error: roborock.0 (31163) Failed to execute get_network_info. Error: Error: Request with id 2610 timed out after 10 seconds for response.102
2023-04-16 01:39:21.945 - error: roborock.0 (31163) Failed to execute get_carpet_mode. Error: Error: Request with id 4178 timed out after 10 seconds for response.102
2023-04-16 02:26:25.831 - info: host.raspberrypi Delete log file iobroker.2023-04-08.log.gz
2023-04-16 02:29:21.967 - error: roborock.0 (31163) Failed to execute get_network_info. Error: Error: Request with id 9757 timed out after 10 seconds for response.102
2023-04-16 02:29:21.968 - error: roborock.0 (31163) Failed to execute get_carpet_mode. Error: Error: Request with id 9992 timed out after 10 seconds for response.102
2023-04-16 02:31:21.970 - error: roborock.0 (31163) Failed to execute get_room_mapping. Error: Error: Request with id 5967 timed out after 10 seconds for response.102
2023-04-16 02:45:21.976 - error: roborock.0 (31163) Failed to execute get_carpet_mode. Error: Error: Request with id 6739 timed out after 10 seconds for response.102
2023-04-16 03:00:11.388 - warn: roborock.0 (31163) MQTT connection close.
2023-04-16 03:00:11.389 - warn: roborock.0 (31163) MQTT connection reconnect.
2023-04-16 03:00:11.611 - info: roborock.0 (31163) State value to set for "roborock.0.Devices.5Im6TX0cm6mgxaWxHaEos7.updateStatus.updatable" has to be type "string" but received type "boolean"
2023-04-16 03:02:21.981 - error: roborock.0 (31163) Failed to execute get_network_info. Error: Error: Request with id 7462 timed out after 10 seconds for response.102
2023-04-16 03:02:21.983 - error: roborock.0 (31163) Failed to execute get_water_box_custom_mode. Error: Error: Request with id 9020 timed out after 10 seconds for response.102
2023-04-16 03:05:21.983 - error: roborock.0 (31163) Failed to execute get_status. Error: Error: Request with id 9954 timed out after 10 seconds for response.102
2023-04-16 03:05:21.984 - error: roborock.0 (31163) Failed to execute get_consumable. Error: Error: Request with id 3501 timed out after 10 seconds for response.102
2023-04-16 03:05:21.984 - error: roborock.0 (31163) Failed to execute get_network_info. Error: Error: Request with id 6613 timed out after 10 seconds for response.102
2023-04-16 03:05:21.985 - error: roborock.0 (31163) Failed to execute get_carpet_mode. Error: Error: Request with id 3573 timed out after 10 seconds for response.102
2023-04-16 03:05:21.986 - error: roborock.0 (31163) Failed to execute get_carpet_clean_mode. Error: Error: Request with id 4264 timed out after 10 seconds for response.102
2023-04-16 03:05:21.986 - error: roborock.0 (31163) Failed to execute get_water_box_custom_mode. Error: Error: Request with id 6112 timed out after 10 seconds for response.102
2023-04-16 03:05:21.987 - error: roborock.0 (31163) Failed to execute get_room_mapping. Error: Error: Request with id 9996 timed out after 10 seconds for response.102
2023-04-16 03:36:21.998 - error: roborock.0 (31163) Failed to execute get_consumable. Error: Error: Request with id 8101 timed out after 10 seconds for response.102
2023-04-16 03:36:21.999 - error: roborock.0 (31163) Failed to execute get_carpet_clean_mode. Error: Error: Request with id 1292 timed out after 10 seconds for response.102
2023-04-16 03:40:22.002 - error: roborock.0 (31163) Failed to execute get_status. Error: Error: Request with id 5963 timed out after 10 seconds for response.102
2023-04-16 03:51:22.009 - error: roborock.0 (31163) Failed to execute get_consumable. Error: Error: Request with id 4946 timed out after 10 seconds for response.102
2023-04-16 03:54:22.010 - error: roborock.0 (31163) Failed to execute get_consumable. Error: Error: Request with id 1316 timed out after 10 seconds for response.102
2023-04-16 03:54:22.011 - error: roborock.0 (31163) Failed to execute get_carpet_clean_mode. Error: Error: Request with id 1181 timed out after 10 seconds for response.102
2023-04-16 03:55:22.011 - error: roborock.0 (31163) Failed to execute get_consumable. Error: Error: Request with id 2767 timed out after 10 seconds for response.102
2023-04-16 03:58:22.015 - error: roborock.0 (31163) Failed to execute get_status. Error: Error: Request with id 2554 timed out after 10 seconds for response.102
2023-04-16 03:58:22.016 - error: roborock.0 (31163) Failed to execute get_carpet_mode. Error: Error: Request with id 2289 timed out after 10 seconds for response.102
2023-04-16 03:58:22.018 - error: roborock.0 (31163) Failed to execute get_room_mapping. Error: Error: Request with id 4789 timed out after 10 seconds for response.102
2023-04-16 04:03:22.022 - error: roborock.0 (31163) Failed to execute get_room_mapping. Error: Error: Request with id 9611 timed out after 10 seconds for response.102
2023-04-16 04:25:22.038 - error: roborock.0 (31163) Failed to execute get_carpet_mode. Error: Error: Request with id 2463 timed out after 10 seconds for response.102
2023-04-16 04:34:22.040 - error: roborock.0 (31163) Failed to execute get_status. Error: Error: Request with id 5493 timed out after 10 seconds for response.102
2023-04-16 04:57:22.053 - error: roborock.0 (31163) Failed to execute get_status. Error: Error: Request with id 1654 timed out after 10 seconds for response.102
2023-04-16 05:06:22.063 - error: roborock.0 (31163) Failed to execute get_carpet_clean_mode. Error: Error: Request with id 3276 timed out after 10 seconds for response.102
2023-04-16 05:25:22.074 - error: roborock.0 (31163) Failed to execute get_status. Error: Error: Request with id 1712 timed out after 10 seconds for response.102
2023-04-16 05:25:22.074 - error: roborock.0 (31163) Failed to execute get_carpet_mode. Error: Error: Request with id 6715 timed out after 10 seconds for response.102
2023-04-16 06:00:00.070 - info: alexa2.0 (31244) Scheduled restart.
2023-04-16 06:00:00.092 - info: roborock.0 (31163) Scheduled restart.
2023-04-16 06:00:00.101 - info: alexa2.0 (31244) terminating

                    Der Server von Roborock antwortet halt nicht immer. Das kann ja verschiedene Gründe haben. Der Adapter erkennt eben, dass der Server nicht antwortete. Das musste ich einbauen, weil es sonst Nachrichten gab, die durcheinandergekommen sind.

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

                      Ich habe den Adapter installiert und habe nur einen leeren Ordner in den Objekten unter Instanzen taucht er nicht auf. Installiert mit der URL: https://github.com/copystring/ioBroker.roborock.git

                      js 4.0.24 NPM:
                      v8.19.2

                      Habt ihr einen Tipp für mich?

                      1 Reply Last reply Reply Quote 0
                      • R
                        RandyAndy last edited by RandyAndy

                        Eigentlich finde ich den Adapter als solches ja interessant. Ich habe Ihn auch mehrfach installiert/geupdated. Inzwischen habe ich Ihn aber wieder gelöscht. Plötzlich war der Plan der Wohnung verdoppelt. Das Roboter hat sich dann auch komisch verhalten. Ich kann natürlich nicht sagen ob dies der Adpter ist oder nicht. Nach der Deinstallation (ist nun auch schon 2-3 Wochen her) ist wieder alles normal.
                        Da man die Cloud immer noch braucht ist mir dann die App doch lieber, da man ja eigentlich mit dem Adpater nicht mehr machen kann. Der Adpater wäre erst dann interessant wenn er den Cloud-Zwang aufhebt, dann würde ich mich wieder damit beschäftigen.

                        copystring O 2 Replies Last reply Reply Quote 0
                        • copystring
                          copystring @RandyAndy last edited by

                          @randyandy said in Roborock Adapter tester gesucht:

                          Eigentlich finde ich den Adapter als solches ja interessant. Ich habe Ihn auch mehrfach installiert/geupdated. Inzwischen habe ich Ihn aber wieder gelöscht. Plötzlich war der Plan der Wohnung verdoppelt. Das Roboter hat sich dann auch komisch verhalten. Ich kann natürlich nicht sagen ob dies der Adpter ist oder nicht. Nach der Deinstallation (ist nun auch schon 2-3 Wochen her) ist wieder alles normal.
                          Da man die Cloud immer noch braucht ist mir dann die App doch lieber, da man ja eigentlich mit dem Adpater nicht mehr machen kann. Der Adpater wäre erst dann interessant wenn er den Cloud-Zwang aufhebt, dann würde ich mich wieder damit beschäftigen.

                          Klar. Der Adapter kann nicht jedem gefallen. Das ist auch OK so. Wenn du allerdings eine Lösung möchtest, welche ohne Cloud klarkommt, dann musst du dir Valetudo auf dem Roboter installieren. Eine custom Firmware, welche die Cloudanbindung auflöst und ausschließlich lokal funktioniert. Damit wird allerdings kein Multilevel Reinigen unterstützt. Man kann also nur eine Karte haben, welche man dann entsprechend tauschen muss, wenn man das Stockwerk wechselt.

                          1 Reply Last reply Reply Quote 0
                          • O
                            oxident @RandyAndy last edited by oxident

                            @randyandy Ich denke, man sollte den Adapter auch nicht als Konkurrenz zur App sehen. Eher als Ergänzung: Wer will, der kann z. B. mit dem Wandschalter die Reinigung starten, beim Aufschließen der Haustür den Roboter die Reinigung abbrechen lassen usw.

                            Diese ganzen Möglichkeiten sind doch eigentlich das, was ein -Smart- home ausmachen.

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

                              @oxident said in Roborock Adapter tester gesucht:

                              @randyandy Ich denke, man sollte den Adapter auch nicht als Konkurrenz zur App sehen. Eher als Ergänzung: Wer will, der kann z. B. mit dem Wandschalter die Reinigung starten, beim Aufschließen der Haustür den Roboter die Reinigung abbrechen lassen usw.

                              Diese ganzen Möglichkeiten sind doch eigentlich das, was ein -Smart- home ausmachen.

                              Dem kann ich mich nur anschließen. Bei uns lasse ich den Roboter automatisch reinigen sobald alle das Haus verlassen. Das Haus weiß immer wann jemand zu Hause ist.

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

                                @oxident sagte in Roborock Adapter tester gesucht:

                                Ich denke, man sollte den Adapter auch nicht als Konkurrenz zur App sehen.

                                Das finde ich nicht.
                                Meine Frau nutzt die App, ich ausnahmslos den Adapter.

                                Ich behaupte, über meine Visualisierung bestimmt 95% dessen was die App kann ab abzubilden.
                                Mir fehlt nur die Zonenreinigung (nutze ich auch nicht), da diese am Raspi nicht klappt.

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

                                  @copystring Ich warte ja wie auf Weihnachten, dass Dein Adapter im ioBroker Repository aufgenommen wird.

                                  Bis dahin: gibt es auf GitHub eine Version, die als stable betrachtet werden kann? Dann würde ich die gerne installieren.

                                  Ich bin halt ein wenig vorsichtig, da mein S5Max zurzeit noch mit Xiaomi unterwegs ist und der Wechsel zu Roborock bedeutet, sowohl den Sauger, als auch meine (umfangreiche) Visualisierung umzustellen.

                                  LG,
                                  Timo

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

                                    @spampunk sagte in Roborock Adapter tester gesucht:

                                    Ich warte ja wie auf Weihnachten, dass Dein Adapter im ioBroker Repository aufgenommen wird.

                                    Ist von @copystring ja schon beantragt.
                                    Aus seiner Sicht ist der Adapter also schon stable.

                                    Wenn du das "Wagnis" eingehen möchtest, kannst du es eigentlich auch jetzt schon machen.

                                    Bei mir läuft der Adapter absolut rund (bis auf Systembedingt die Zonenreinigung und warum auch immer die Kamera).

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

                                      Hallo zusammen, bei mir werden einige Räume immer in beiden Geschossen angelegt. Nach dem Löschen der Ordner und Adapterneustart passt alles, aber sobald ich in der App die Geschosse einmal gewechselt habe herrscht wieder komplettes durcheinander.

                                      Hat noch jemand das Problem?

                                      Zwischenablage.jpg

                                      Die Karten werden bei mir auch nicht angezeigt:

                                      Zwischenablage.jpg

                                      1 Reply Last reply Reply Quote 0
                                      • S
                                        socke85 last edited by

                                        @copystring Ich habe den Adapter installiert und habe nur einen leeren Ordner in den Objekten unter Instanzen taucht er nicht auf. Installiert mit der URL: https://github.com/copystring/ioBroker.roborock.git

                                        js 4.0.24 NPM:
                                        v8.19.2

                                        Habt ihr einen Tipp für mich?

                                        Thomas Braun 1 Reply Last reply Reply Quote 0
                                        • Thomas Braun
                                          Thomas Braun Most Active @socke85 last edited by

                                          @socke85

                                          Bei Installationen via github muss eine Instanz manuell hinzugefügt werden.

                                          1 Reply Last reply Reply Quote 0
                                          • S
                                            Spampunk last edited by Spampunk

                                            So, der Adapter ist installiert und "Rocky" dreht seine ersten Runden. Was mir sofort positiv aufgefallen ist: die Karte wird auf Anhieb angezeigt. Super!

                                            Jetzt implementiere ich die Funktionen nach und nach in meine VIS. Dabei sind zwei Fragen aufgetaucht.

                                            1.: Wie teile ich Rocky mit, dass er eine Koordinate anfahren soll (Pin and Go)? Das brauche ich, um Rocky zum Mülleimer und zur Treppe fahren zu lassen

                                            2.: In der MiHome-App gab es ein JSON für die History. In diesem Adapter wird dies wohl über einzelne DPs gelöst.
                                            a) wie bekomme ich die DPs wohl am elegantesten in eine Tabellenform?
                                            b) ist angedacht, die History ebenfalls als JSON bereitzustellen?

                                            Viele Grüße und 'Rock on!'
                                            Timo

                                            David G. 1 Reply Last reply Reply Quote 0
                                            • First post
                                              Last post

                                            Support us

                                            ioBroker
                                            Community Adapters
                                            Donate

                                            930
                                            Online

                                            31.6k
                                            Users

                                            79.5k
                                            Topics

                                            1.3m
                                            Posts

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