Neuer Adapter für Roborock-Staubsauger
-
@copystring
damit der robby bei goto eine bestimmte position anfährt.nuja, script schreiben... kanns ja mal mit rules versuchen...
ahja, tropsdem für mich zu klein. mal schauen, vllt fällt mir noch was ein.
-
Hi, und vielen Dank für den Adapter - grundsätzlich scheint bei mir (S7) alles zu funktionieren!
Eine Frage habe ich, gibt es eine Möglichkeit, über den Adapter einen Zeitplan des Robos zu deaktivieren/pausieren und wieder zu aktivieren? Unser Helferlein läuft nachts im EG und wenn wir Gäste haben, die da schlafen, dann wäre es super wenn man einen Befehl senden könnte, der den konfigurierten Zeitplan bis auf weiteres deaktiviert.
Falls jemand einen Tipp hat wäre ich dankbar!
-
Hi zusammen,
vielen Dank für eure tolle Arbeit!
Ich würde den Adapter gerne mit meinem Roborock S5 nutzen.
Leider wird der S5 (S50) nicht in der Roborock App angeboten, sondern funktioniert nur über die Mi-Home App.
Kann man damit den Adapter auch nutzen oder wie funktioniert es mit dem S5?Vielen Dank!
-
Hi, seit dem heute Morgen meine Internetverbindung kurz getrennt wurde (Zwangstrennung) bekomme ich jede Minute die Warnmeldungen MQTT connection close und MQTT connection reconnect. Hat das noch jemand, ist das normal?
Ich habe gestern die neue DEV installiert, vorher hatte ich das noch nicht.
Es funktioniert sonst noch Alles, ich kann den Robo auch noch über den Adapter steuern. Nur mein Log ist voll mit den Warnmeldungen.2024-01-15 03:02:21.138 - error: roborock.0 (28972) Failed to update updateHomeData with error: Error: getaddrinfo EAI_AGAIN api-eu.roborock.com 2024-01-15 03:03:24.167 - warn: roborock.0 (28972) MQTT connection close. 2024-01-15 03:03:25.164 - warn: roborock.0 (28972) MQTT connection reconnect. 2024-01-15 03:04:24.166 - warn: roborock.0 (28972) MQTT connection close. 2024-01-15 03:04:25.166 - warn: roborock.0 (28972) MQTT connection reconnect. 2024-01-15 03:05:24.168 - warn: roborock.0 (28972) MQTT connection close. 2024-01-15 03:05:25.168 - warn: roborock.0 (28972) MQTT connection reconnect. 2024-01-15 03:06:24.169 - warn: roborock.0 (28972) MQTT connection close. 2024-01-15 03:06:25.169 - warn: roborock.0 (28972) MQTT connection reconnect. 2024-01-15 03:07:24.171 - warn: roborock.0 (28972) MQTT connection close. 2024-01-15 03:07:25.170 - warn: roborock.0 (28972) MQTT connection reconnect. 2024-01-15 03:08:24.172 - warn: roborock.0 (28972) MQTT connection close. 2024-01-15 03:08:25.172 - warn: roborock.0 (28972) MQTT connection reconnect. 2024-01-15 03:09:24.172 - warn: roborock.0 (28972) MQTT connection close. . . . 2024-01-15 16:01:25.033 - warn: roborock.0 (28972) MQTT connection close. 2024-01-15 16:01:26.033 - warn: roborock.0 (28972) MQTT connection reconnect. 2024-01-15 16:02:25.035 - warn: roborock.0 (28972) MQTT connection close. 2024-01-15 16:02:26.034 - warn: roborock.0 (28972) MQTT connection reconnect.Edit: Nachdem ich den Adapter jetzt neu gestartet habe ist erst mal Ruhe. Mal schauen ob es Morgen wieder passiert.
-
@adsfa said in Neuer Adapter für Roborock-Staubsauger:
Hi zusammen,
vielen Dank für eure tolle Arbeit!
Ich würde den Adapter gerne mit meinem Roborock S5 nutzen.
Leider wird der S5 (S50) nicht in der Roborock App angeboten, sondern funktioniert nur über die Mi-Home App.
Kann man damit den Adapter auch nutzen oder wie funktioniert es mit dem S5?Vielen Dank!
Das geht nicht weil die App den s5 nicht unterstützt. Somit kann der Adapter das logischerweise ebenfalls nicht.
-
Zu früh gefreut
Nachdem ich gestern Abend die aktuellste /dev installiert hatte, war heute morgen noch alles super.
-> Die Bots starteten, beim Haus abschliessen, so wie es das Blockly vorgibt ...alles gut.
Aber um 15.35 Uhr heute nachmittag, warum auch immer, kamen ERRORS im Log (zuvor um 14:49 Uhr MQTT close/reconnect):
Aufmerksam bin ich darauf geworden, da der ioBroker beim Login mir mal wieder den hier zeigte:
Irgendjemand Ideen ?? Oder haben die wieder an der App API rumgefummelt ?
Ich bin mir sicher, wenn ich den Adapter neu starte, läuft es erst einmal wieder....
Nachtrag, nö, tuts nicht, er crashed wieder....:
@copystring : Debug Log & Git Issue ?
lg Micha
-
@copystring Ok danke für die Info.
Auf der Adapterseite wird der S5 aufgelistet, deshalb wollte ich mal fragen. Dann muss ich mir wohl einen neuen kaufen. Danke
ChatGPT (geprüft habe ich es nicht):
"Die folgenden Roborock-Modelle werden nicht von der Roborock-App unterstützt:
Roborock S5
Roborock Q7" -
@adsfa stimmt. Das muss ich mal anpassen.
-
@tritanium Teste bitte die neue dev von GitHub.
-
@copystring Moin
Kurze Review: Neue /dev heute morgen installiert, Adapter crasht nicht mehr!
Beim verlassen des Hauses, starteten beide Robis auch normal (durch Blockly).
Gefahren sind sie ganz normal und in der App konnte ich logischerweise sehen was die machen.
AAAABER:
Derzeit wird mir das Logging vom ioBroker zugespammt
Die Datenpunkte für die CleaningInfo scheint nicht aktualisiert zu werden. Die steh noch auf dem Datum von gestern .... auch während der Reinigungsvorgänge kommen die ganze Zeit diese Logeinträge.....
Hier mal ein kurzer Auszug:
Ich würde jetzt mal den Adapter neu starten um zu beobachten, was passiert ....
EDIT:
Adapter normal neu gestartet:
Keine verdächtigen Logs, oder sonstiges "negatives".....
Nach ca. 7 Minuten:
Lediglich die WARNINGS für get_status bzw. get_network_info waren mal angezeigt.
Auch die Cleaning_Infos wurden "nach aktualisiert", die stimmen nun auch wieder....
Ich behalte es im Auge und sage bis später..... aber bis dato: TOP Version
-> danke für dein Engagement
-
ich schon wieder
-> Ging grade wieder los mit den "WARN" Meldungen:
roborock.0 2024-01-16 13:00:16.950 warn MQTT connection close. roborock.0 2024-01-16 13:00:16.854 warn MQTT connection reconnect. roborock.0 2024-01-16 13:00:15.854 warn MQTT connection close. roborock.0 2024-01-16 13:00:15.760 warn MQTT connection reconnect. roborock.0 2024-01-16 13:00:14.760 warn MQTT connection close. roborock.0 2024-01-16 13:00:14.654 warn MQTT connection reconnect. roborock.0 2024-01-16 13:00:13.653 warn MQTT connection close. roborock.0 2024-01-16 13:00:13.556 warn MQTT connection reconnect. roborock.0 2024-01-16 13:00:12.556 warn MQTT connection close. roborock.0 2024-01-16 13:00:12.455 warn MQTT connection reconnect. roborock.0 2024-01-16 13:00:11.454 warn MQTT connection close. roborock.0 2024-01-16 13:00:11.362 warn MQTT connection reconnect. roborock.0 2024-01-16 13:00:10.362 warn MQTT connection close. roborock.0 2024-01-16 13:00:10.262 warn MQTT connection reconnect. roborock.0 2024-01-16 13:00:09.262 warn MQTT connection close. roborock.0 2024-01-16 13:00:09.168 warn MQTT connection reconnect. roborock.0 2024-01-16 13:00:08.167 warn MQTT connection close. roborock.0 2024-01-16 13:00:08.073 warn MQTT connection reconnect.Jede Sekunde close / reconnect.
Laut App stehen beide Robis geladen im Dock und sind per WLAN sauber erreichbar .....
-
Ich schon wieder
Hier nun wieder ein crash:
Ich weiß nicht mehr weiter....
-
@copystring moin.
gestern auch die letzte dev geholt, nachdem in iQontrol gar nichts mehr ging. keine buttons, keine mapaktualisierung.
(adapter gestoppt, alle objekte gelöscht, dann gestartet) am anfang wars ja relativ ruhig.
jetzt nervt er rum mitroborock.0 2024-01-17 05:38:48.330 warn MQTT connection close. roborock.0 2024-01-17 05:38:48.229 warn MQTT connection reconnect. roborock.0 2024-01-17 05:38:47.228 warn MQTT connection close. roborock.0 2024-01-17 05:38:47.130 warn MQTT connection reconnect. roborock.0 2024-01-17 05:38:46.130 warn MQTT connection close. roborock.0 2024-01-17 05:38:46.029 warn MQTT connection reconnect. roborock.0 2024-01-17 05:38:45.029 warn MQTT connection close. roborock.0 2024-01-17 05:38:44.933 warn MQTT connection reconnect. roborock.0 2024-01-17 05:38:43.932 warn MQTT connection close. roborock.0 2024-01-17 05:38:43.811 warn MQTT connection reconnect. roborock.0 2024-01-17 05:38:42.811 warn MQTT connection close. roborock.0 2024-01-17 05:38:42.716 warn MQTT connection reconnect.roborock.0 2024-01-17 05:38:39.988 warn Failed to map rooms. You need to name your rooms via the mobile app on your phone.kommt zwischendurch auch immer wieder, obwohl ich den raum in der app schon benannt habe.
sind zwar nur warnings, aber lästig. -
...wie bei mir, ich habe den Adapter derzeit aus, da ich keinen Anhaltspunkt habe, warum es nach unterschidelichen Zeiten mit den ganzen "WARNINGS" los geht.
Es fängt erst auch wie bei dir an mit den stnändigen Re-Connects, was sich dann hochschaukelt bis zu schwerwiegenderen Problemen und der Adapter dann crasht und neustartet.
Bis dann der ioBroker sagt: nö, du bleibst jetzt aus
Warten wir mal ab, was copystring herausfindet, wenn seine Zeit es zulässt ...
@copystring : ...wenn du Logs brauchst, sag bescheid, ich tu alles um zu helfen
-
Ein Log brauche ich erstmal nicht. Könnt ihr bestätigen, dass der Ausfall mit der aktualisierten dev von gestern, ziemlich genau jede Stunde auftritt?
-
@copystring
siehe meinen Eintrag im git, ja, nach genau einer Stunde. "Jede" kann ich nicht bestätigen, weil ich vorher immer abschalte.
Gruß jahnbes -
@copystring sagte in Neuer Adapter für Roborock-Staubsauger:
der Ausfall mit der aktualisierten den von gestern, ziemlich genau jede Stunde Auftritt?
meinst du kartenupdate?
kann ich nicht genau sagen. bei mir läuft der adapter seit dem letzten test. gerade einen kurzen testlauf gemacht.
meine buttons funktionieren, die map nicht. roborock.0.Devices.xxx.deviceStatus.state klappt auch, allerdings mit verzögerung.
häng dir trotzdem ein log da an...roborock.0 2024-01-17 14:47:49.638 warn Failed to execute get_map_v1 on robot 5umEnoJEB0hmM5UmYlkumw Error: Request with id 8148 with method get_map_v1 timed out after 10 seconds for response.102 roborock.0 2024-01-17 14:47:49.489 debug Length of message queue: 4 roborock.0 2024-01-17 14:47:49.489 debug Length of message queue: 4 roborock.0 2024-01-17 14:47:49.401 debug Update map roborock.0 2024-01-17 14:47:49.300 warn MQTT connection close. roborock.0 2024-01-17 14:47:49.188 warn MQTT connection reconnect. roborock.0 2024-01-17 14:47:48.187 warn MQTT connection close. roborock.0 2024-01-17 14:47:48.073 warn MQTT connection reconnect. roborock.0 2024-01-17 14:47:47.941 warn Failed to execute get_map_v1 on robot 5umEnoJEB0hmM5UmYlkumw Error: Request with id 8147 with method get_map_v1 timed out after 10 seconds for response.102 roborock.0 2024-01-17 14:47:47.932 debug Length of message queue: 5 roborock.0 2024-01-17 14:47:47.932 debug Length of message queue: 5 roborock.0 2024-01-17 14:47:47.390 debug Update map roborock.0 2024-01-17 14:47:47.073 warn MQTT connection close. roborock.0 2024-01-17 14:47:46.954 warn MQTT connection reconnect. roborock.0 2024-01-17 14:47:45.948 warn MQTT connection close. roborock.0 2024-01-17 14:47:45.849 warn MQTT connection reconnect. roborock.0 2024-01-17 14:47:45.617 warn Failed to execute get_map_v1 on robot 5umEnoJEB0hmM5UmYlkumw Error: Request with id 8146 with method get_map_v1 timed out after 10 seconds for response.102 roborock.0 2024-01-17 14:47:45.506 debug Length of message queue: 5 roborock.0 2024-01-17 14:47:45.506 debug Length of message queue: 5 roborock.0 2024-01-17 14:47:45.390 debug Update map roborock.0 2024-01-17 14:47:44.842 warn MQTT connection close. roborock.0 2024-01-17 14:47:44.739 warn MQTT connection reconnect. roborock.0 2024-01-17 14:47:43.739 warn MQTT connection close. roborock.0 2024-01-17 14:47:43.609 warn MQTT connection reconnect. roborock.0 2024-01-17 14:47:43.509 warn Failed to execute get_map_v1 on robot 5umEnoJEB0hmM5UmYlkumw Error: Request with id 8145 with method get_map_v1 timed out after 10 seconds for response.102 roborock.0 2024-01-17 14:47:43.462 debug Length of message queue: 4 roborock.0 2024-01-17 14:47:43.462 debug Length of message queue: 4 roborock.0 2024-01-17 14:47:43.383 debug Update map roborock.0 2024-01-17 14:47:43.062 debug homedata successfully updated roborock.0 2024-01-17 14:47:43.036 debug get_timer: "[] roborock.0 2024-01-17 14:47:43.036 debug Length of message queue: 5 roborock.0 2024-01-17 14:47:42.793 debug getParameter for 5umEnoJEB0hmM5UmYlkumw: get_timer roborock.0 2024-01-17 14:47:42.793 debug get_server_timer: " + [] roborock.0 2024-01-17 14:47:42.793 debug Length of message queue: 5 roborock.0 2024-01-17 14:47:42.641 debug getParameter for 5umEnoJEB0hmM5UmYlkumw: get_server_timer roborock.0 2024-01-17 14:47:42.641 debug Length of message queue: 5 roborock.0 2024-01-17 14:47:42.609 warn MQTT connection close. roborock.0 2024-01-17 14:47:42.495 warn MQTT connection reconnect. roborock.0 2024-01-17 14:47:42.440 warn Failed to execute get_map_v1 on robot 5umEnoJEB0hmM5UmYlkumw Error: Request with id 8144 with method get_map_v1 timed out after 10 seconds for response.102 roborock.0 2024-01-17 14:47:42.201 debug Length of message queue: 5 roborock.0 2024-01-17 14:47:42.201 debug Length of message queue: 5 roborock.0 2024-01-17 14:47:42.170 debug getParameter for 5umEnoJEB0hmM5UmYlkumw: get_network_info roborock.0 2024-01-17 14:47:42.170 debug Consumables of robot: {"main_brush_work_time":68952,"side_brush_work_time":68952,"filter_work_time":68952,"filter_element_work_time":0,"sensor_dirty_time":97966} roborock.0 2024-01-17 14:47:42.169 debug Length of message queue: 6 roborock.0 2024-01-17 14:47:41.712 debug getParameter for 5umEnoJEB0hmM5UmYlkumw: get_consumable roborock.0 2024-01-17 14:47:41.712 warn Failed to map rooms. You need to name your rooms via the mobile app on your phone. roborock.0 2024-01-17 14:47:41.712 debug All mapped rooms: [] roborock.0 2024-01-17 14:47:41.712 debug Length of message queue: 5 roborock.0 2024-01-17 14:47:41.495 warn MQTT connection close. roborock.0 2024-01-17 14:47:41.480 debug Length of message queue: 5 roborock.0 2024-01-17 14:47:41.386 warn MQTT connection reconnect. roborock.0 2024-01-17 14:47:41.383 debug Update map roborock.0 2024-01-17 14:47:40.995 debug getParameter for 5umEnoJEB0hmM5UmYlkumw: get_room_mapping roborock.0 2024-01-17 14:47:40.929 debug get_status: {"msg_ver":2,"msg_seq":1465,"state":8,"battery":99,"clean_time":133,"clean_area":2172500,"error_code":0,"map_present":1,"in_cleaning":0,"in_returning":0,"in_fresh_state":1,"lab_status":1,"water_box_status":0,"fan_power":102,"dnd_enabled":0,"map_status":3,"is_locating":0,"lock_status":0} roborock.0 2024-01-17 14:47:40.928 debug Length of message queue: 5 roborock.0 2024-01-17 14:47:40.687 debug getParameter for 5umEnoJEB0hmM5UmYlkumw: get_status roborock.0 2024-01-17 14:47:40.687 debug Latest data requested roborock.0 2024-01-17 14:47:40.669 warn Failed to execute get_map_v1 on robot 5umEnoJEB0hmM5UmYlkumw Error: Request with id 8143 with method get_map_v1 timed out after 10 seconds for response.102 roborock.0 2024-01-17 14:47:40.620 debug Length of message queue: 5 roborock.0 2024-01-17 14:47:40.620 debug Length of message queue: 5 roborock.0 2024-01-17 14:47:40.385 warn MQTT connection close. roborock.0 2024-01-17 14:47:40.236 warn MQTT connection reconnect. roborock.0 2024-01-17 14:47:39.382 debug Update map roborock.0 2024-01-17 14:47:39.234 warn MQTT connection close. roborock.0 2024-01-17 14:47:39.090 warn MQTT connection reconnect. roborock.0 2024-01-17 14:47:38.088 warn MQTT connection close. roborock.0 2024-01-17 14:47:38.011 warn Failed to execute get_map_v1 on robot 5umEnoJEB0hmM5UmYlkumw Error: Request with id 8142 with method get_map_v1 timed out after 10 seconds for response.102 roborock.0 2024-01-17 14:47:37.936 warn MQTT connection reconnect. roborock.0 2024-01-17 14:47:37.808 debug Length of message queue: 4 roborock.0 2024-01-17 14:47:37.807 debug Length of message queue: 4 roborock.0 2024-01-17 14:47:37.366 debug Update map roborock.0 2024-01-17 14:47:36.935 warn MQTT connection close. roborock.0 2024-01-17 14:47:36.816 warn MQTT connection reconnect. roborock.0 2024-01-17 14:47:35.816 warn MQTT connection close. roborock.0 2024-01-17 14:47:35.694 warn MQTT connection reconnect. roborock.0 2024-01-17 14:47:35.546 warn Failed to execute get_map_v1 on robot 5umEnoJEB0hmM5UmYlkumw Error: Request with id 8141 with method get_map_v1 timed out after 10 seconds for response.102 roborock.0 2024-01-17 14:47:35.429 debug Length of message queue: 4 roborock.0 2024-01-17 14:47:35.428 debug Length of message queue: 4 roborock.0 2024-01-17 14:47:35.366 debug Update map roborock.0 2024-01-17 14:47:34.694 warn MQTT connection close. roborock.0 2024-01-17 14:47:34.577 warn MQTT connection reconnect. roborock.0 2024-01-17 14:47:33.564 warn MQTT connection close. roborock.0 2024-01-17 14:47:33.459 warn MQTT connection reconnect. roborock.0 2024-01-17 14:47:33.411 warn Failed to execute get_map_v1 on robot 5umEnoJEB0hmM5UmYlkumw Error: Request with id 8140 with method get_map_v1 timed out after 10 seconds for response.102 roborock.0 2024-01-17 14:47:33.377 debug Length of message queue: 4 roborock.0 2024-01-17 14:47:33.377 debug Length of message queue: 4 roborock.0 2024-01-17 14:47:33.366 debug Update map roborock.0 2024-01-17 14:47:32.443 warn MQTT connection close. roborock.0 2024-01-17 14:47:32.329 warn MQTT connection reconnect. roborock.0 2024-01-17 14:47:31.546 warn Failed to execute get_map_v1 on robot 5umEnoJEB0hmM5UmYlkumw Error: Request with id 8139 with method get_map_v1 timed out after 10 seconds for response.102 roborock.0 2024-01-17 14:47:31.366 debug Update map roborock.0 2024-01-17 14:47:31.354 debug Length of message queue: 4 roborock.0 2024-01-17 14:47:31.354 debug Length of message queue: 4 roborock.0 2024-01-17 14:47:31.327 warn MQTT connection close. roborock.0 2024-01-17 14:47:31.211 warn MQTT connection reconnect. roborock.0 2024-01-17 14:47:30.291 warn Failed to execute get_map_v1 on robot 5umEnoJEB0hmM5UmYlkumw Error: Request with id 8138 with method get_map_v1 timed out after 10 seconds for response.102 roborock.0 2024-01-17 14:47:30.209 warn MQTT connection close. roborock.0 2024-01-17 14:47:30.112 warn MQTT connection reconnect. roborock.0 2024-01-17 14:47:29.524 debug Length of message queue: 4 roborock.0 2024-01-17 14:47:29.523 debug Length of message queue: 4 roborock.0 2024-01-17 14:47:29.358 debug Update map roborock.0 2024-01-17 14:47:29.111 warn MQTT connection close. roborock.0 2024-01-17 14:47:29.010 warn MQTT connection reconnect. roborock.0 2024-01-17 14:47:28.010 warn MQTT connection close. roborock.0 2024-01-17 14:47:27.892 warn MQTT connection reconnect. roborock.0 2024-01-17 14:47:27.547 warn Failed to execute get_map_v1 on robot 5umEnoJEB0hmM5UmYlkumw Error: Request with id 8137 with method get_map_v1 timed out after 10 seconds for response.102 roborock.0 2024-01-17 14:47:27.427 debug Length of message queue: 4 roborock.0 2024-01-17 14:47:27.427 debug Length of message queue: 4 roborock.0 2024-01-17 14:47:27.356 debug Update map roborock.0 2024-01-17 14:47:26.891 warn MQTT connection close. roborock.0 2024-01-17 14:47:26.774 warn MQTT connection reconnect. roborock.0 2024-01-17 14:47:25.952 warn Failed to execute get_map_v1 on robot 5umEnoJEB0hmM5UmYlkumw Error: Request with id 8136 with method get_map_v1 timed out after 10 seconds for response.102 roborock.0 2024-01-17 14:47:25.924 debug Length of message queue: 5 roborock.0 2024-01-17 14:47:25.923 debug Length of message queue: 5 roborock.0 2024-01-17 14:47:25.773 warn MQTT connection close. roborock.0 2024-01-17 14:47:25.660 warn MQTT connection reconnect. roborock.0 2024-01-17 14:47:25.356 debug Update map roborock.0 2024-01-17 14:47:24.659 warn MQTT connection close. roborock.0 2024-01-17 14:47:24.556 warn MQTT connection reconnect. roborock.0 2024-01-17 14:47:23.969 warn Failed to execute get_map_v1 on robot 5umEnoJEB0hmM5UmYlkumw Error: Request with id 8135 with method get_map_v1 timed out after 10 seconds for response.102 roborock.0 2024-01-17 14:47:23.949 debug Length of message queue: 5 roborock.0 2024-01-17 14:47:23.948 debug Length of message queue: 5 roborock.0 2024-01-17 14:47:23.556 warn MQTT connection close. roborock.0 2024-01-17 14:47:23.447 warn MQTT connection reconnect. roborock.0 2024-01-17 14:47:23.344 debug Update map roborock.0 2024-01-17 14:47:22.447 warn MQTT connection close. roborock.0 2024-01-17 14:47:22.324 warn MQTT connection reconnect. roborock.0 2024-01-17 14:47:22.194 warn Failed to execute get_map_v1 on robot 5umEnoJEB0hmM5UmYlkumw Error: Request with id 8134 with method get_map_v1 timed out after 10 seconds for response.102 roborock.0 2024-01-17 14:47:22.118 debug Length of message queue: 5 roborock.0 2024-01-17 14:47:22.118 debug Length of message queue: 5 roborock.0 2024-01-17 14:47:21.344 debug Update map roborock.0 2024-01-17 14:47:21.316 warn MQTT connection close. roborock.0 2024-01-17 14:47:21.198 warn MQTT connection reconnect. roborock.0 2024-01-17 14:47:20.215 warn Failed to execute get_map_v1 on robot 5umEnoJEB0hmM5UmYlkumw Error: Request with id 8133 with method get_map_v1 timed out after 10 seconds for response.102 roborock.0 2024-01-17 14:47:20.197 warn MQTT connection close. roborock.0 2024-01-17 14:47:20.130 debug Length of message queue: 5 roborock.0 2024-01-17 14:47:20.129 debug Length of message queue: 5 roborock.0 2024-01-17 14:47:20.033 warn MQTT connection reconnect. roborock.0 2024-01-17 14:47:19.343 debug Update map roborock.0 2024-01-17 14:47:19.032 warn MQTT connection close. roborock.0 2024-01-17 14:47:18.875 warn MQTT connection reconnect. roborock.0 2024-01-17 14:47:17.875 warn MQTT connection close. roborock.0 2024-01-17 14:47:17.813 warn Failed to execute get_map_v1 on robot 5umEnoJEB0hmM5UmYlkumw Error: Request with id 8132 with method get_map_v1 timed out after 10 seconds for response.102 roborock.0 2024-01-17 14:47:17.761 warn MQTT connection reconnect. roborock.0 2024-01-17 14:47:17.726 debug Length of message queue: 5 roborock.0 2024-01-17 14:47:17.726 debug Length of message queue: 5 roborock.0 2024-01-17 14:47:17.334 debug Update map roborock.0 2024-01-17 14:47:16.761 warn MQTT connection close. roborock.0 2024-01-17 14:47:16.651 warn MQTT connection reconnect. roborock.0 2024-01-17 14:47:15.842 warn Failed to execute get_map_v1 on robot 5umEnoJEB0hmM5UmYlkumw Error: Request with id 8131 with method get_map_v1 timed out after 10 seconds for response.102 roborock.0 2024-01-17 14:47:15.664 debug Length of message queue: 4 roborock.0 2024-01-17 14:47:15.664 debug Length of message queue: 4 roborock.0 2024-01-17 14:47:15.651 warn MQTT connection close. roborock.0 2024-01-17 14:47:15.506 warn MQTT connection reconnect. roborock.0 2024-01-17 14:47:15.328 debug Update map roborock.0 2024-01-17 14:47:14.506 warn MQTT connection close. roborock.0 2024-01-17 14:47:14.405 warn MQTT connection reconnect. roborock.0 2024-01-17 14:47:13.825 warn Failed to execute get_map_v1 on robot 5umEnoJEB0hmM5UmYlkumw Error: Request with id 8130 with method get_map_v1 timed out after 10 seconds for response.102 roborock.0 2024-01-17 14:47:13.405 warn MQTT connection close. roborock.0 2024-01-17 14:47:13.373 debug Length of message queue: 4 roborock.0 2024-01-17 14:47:13.373 debug Length of message queue: 4 roborock.0 2024-01-17 14:47:13.328 debug Update map roborock.0 2024-01-17 14:47:13.289 warn MQTT connection reconnect. roborock.0 2024-01-17 14:47:12.289 warn MQTT connection close. roborock.0 2024-01-17 14:47:12.153 warn MQTT connection reconnect. roborock.0 2024-01-17 14:47:12.050 warn Failed to execute get_map_v1 on robot 5umEnoJEB0hmM5UmYlkumw Error: Request with id 8129 with method get_map_v1 timed out after 10 seconds for response.102 roborock.0 2024-01-17 14:47:11.898 debug Length of message queue: 4 roborock.0 2024-01-17 14:47:11.898 debug Length of message queue: 4 roborock.0 2024-01-17 14:47:11.323 debug Update map roborock.0 2024-01-17 14:47:11.153 warn MQTT connection close. roborock.0 2024-01-17 14:47:11.016 warn MQTT connection reconnect. roborock.0 2024-01-17 14:47:10.015 warn MQTT connection close. roborock.0 2024-01-17 14:47:09.883 warn MQTT connection reconnect. roborock.0 2024-01-17 14:47:09.872 warn Failed to execute get_map_v1 on robot 5umEnoJEB0hmM5UmYlkumw Error: Request with id 8128 with method get_map_v1 timed out after 10 seconds for response.102 roborock.0 2024-01-17 14:47:09.483 debug Length of message queue: 4 roborock.0 2024-01-17 14:47:09.482 debug Length of message queue: 4 roborock.0 2024-01-17 14:47:09.320 debug Update map roborock.0 2024-01-17 14:47:08.879 warn MQTT connection close. roborock.0 2024-01-17 14:47:08.757 warn MQTT connection reconnect. roborock.0 2024-01-17 14:47:07.757 warn MQTT connection close. roborock.0 2024-01-17 14:47:07.665 warn Failed to execute get_map_v1 on robot 5umEnoJEB0hmM5UmYlkumw Error: Request with id 8127 with method get_map_v1 timed out after 10 seconds for response.102 roborock.0 2024-01-17 14:47:07.646 warn MQTT connection reconnect. roborock.0 2024-01-17 14:47:07.506 debug Length of message queue: 4 roborock.0 2024-01-17 14:47:07.506 debug Length of message queue: 4 roborock.0 2024-01-17 14:47:07.320 debug Update map roborock.0 2024-01-17 14:47:06.645 warn MQTT connection close. roborock.0 2024-01-17 14:47:06.494 warn MQTT connection reconnect. roborock.0 2024-01-17 14:47:05.607 warn Failed to execute get_map_v1 on robot 5umEnoJEB0hmM5UmYlkumw Error: Request with id 8126 with method get_map_v1 timed out after 10 seconds for response.102 roborock.0 2024-01-17 14:47:05.494 warn MQTT connection close. roborock.0 2024-01-17 14:47:05.399 debug Length of message queue: 4 roborock.0 2024-01-17 14:47:05.398 debug Length of message queue: 4 roborock.0 2024-01-17 14:47:05.352 warn MQTT connection reconnect. roborock.0 2024-01-17 14:47:05.315 debug Update map roborock.0 2024-01-17 14:47:04.350 warn MQTT connection close. roborock.0 2024-01-17 14:47:04.236 warn MQTT connection reconnect. roborock.0 2024-01-17 14:47:03.506 warn Failed to execute get_map_v1 on robot 5umEnoJEB0hmM5UmYlkumw Error: Request with id 8125 with method get_map_v1 timed out after 10 seconds for response.102 roborock.0 2024-01-17 14:47:03.502 debug Length of message queue: 5 roborock.0 2024-01-17 14:47:03.502 debug Length of message queue: 5 roborock.0 2024-01-17 14:47:03.300 debug Update map roborock.0 2024-01-17 14:47:03.235 warn MQTT connection close. roborock.0 2024-01-17 14:47:03.123 warn MQTT connection reconnect. roborock.0 2024-01-17 14:47:02.122 warn Failed to execute get_map_v1 on robot 5umEnoJEB0hmM5UmYlkumw Error: Request with id 8124 with method get_map_v1 timed out after 10 seconds for response.102 roborock.0 2024-01-17 14:47:02.122 warn MQTT connection close. roborock.0 2024-01-17 14:47:02.009 warn MQTT connection reconnect. roborock.0 2024-01-17 14:47:01.922 debug Length of message queue: 5 roborock.0 2024-01-17 14:47:01.922 debug Length of message queue: 5 roborock.0 2024-01-17 14:47:01.294 debug Update map roborock.0 2024-01-17 14:47:01.007 warn MQTT connection close. roborock.0 2024-01-17 14:47:00.907 warn MQTT connection reconnect. roborock.0 2024-01-17 14:46:59.906 warn MQTT connection close. roborock.0 2024-01-17 14:46:59.784 warn MQTT connection reconnect. roborock.0 2024-01-17 14:46:59.415 warn Failed to execute get_map_v1 on robot 5umEnoJEB0hmM5UmYlkumw Error: Request with id 8123 with method get_map_v1 timed out after 10 seconds for response.102 roborock.0 2024-01-17 14:46:59.366 debug Length of message queue: 4 roborock.0 2024-01-17 14:46:59.366 debug Length of message queue: 4 roborock.0 2024-01-17 14:46:59.294 debug Update map roborock.0 2024-01-17 14:46:58.783 warn MQTT connection close. roborock.0 2024-01-17 14:46:58.652 warn MQTT connection reconnect. roborock.0 2024-01-17 14:46:57.652 warn MQTT connection close. roborock.0 2024-01-17 14:46:57.521 warn MQTT connection reconnect. roborock.0 2024-01-17 14:46:57.416 warn Failed to execute get_map_v1 on robot 5umEnoJEB0hmM5UmYlkumw Error: Request with id 8122 with method get_map_v1 timed out after 10 seconds for response.102 roborock.0 2024-01-17 14:46:57.310 debug Length of message queue: 4 roborock.0 2024-01-17 14:46:57.310 debug Length of message queue: 4 roborock.0 2024-01-17 14:46:57.275 debug Update map roborock.0 2024-01-17 14:46:56.521 warn MQTT connection close. roborock.0 2024-01-17 14:46:56.394 warn MQTT connection reconnect. roborock.0 2024-01-17 14:46:55.550 warn Failed to execute get_map_v1 on robot 5umEnoJEB0hmM5UmYlkumw Error: Request with id 8121 with method get_map_v1 timed out after 10 seconds for response.102 roborock.0 2024-01-17 14:46:55.502 debug Length of message queue: 5 roborock.0 2024-01-17 14:46:55.500 debug Length of message queue: 5 roborock.0 2024-01-17 14:46:55.386 warn MQTT connection close. roborock.0 2024-01-17 14:46:55.275 debug Update map roborock.0 2024-01-17 14:46:55.259 warn MQTT connection reconnect. roborock.0 2024-01-17 14:46:54.257 warn MQTT connection close. roborock.0 2024-01-17 14:46:54.089 warn MQTT connection reconnect. roborock.0 2024-01-17 14:46:53.593 warn Failed to execute get_map_v1 on robot 5umEnoJEB0hmM5UmYlkumw Error: Request with id 8120 with method get_map_v1 timed out after 10 seconds for response.102 roborock.0 2024-01-17 14:46:53.372 debug Length of message queue: 4 roborock.0 2024-01-17 14:46:53.372 debug Length of message queue: 4 roborock.0 2024-01-17 14:46:53.272 debug Update map roborock.0 2024-01-17 14:46:53.089 warn MQTT connection close. roborock.0 2024-01-17 14:46:52.980 warn MQTT connection reconnect. roborock.0 2024-01-17 14:46:51.979 warn MQTT connection close. roborock.0 2024-01-17 14:46:51.813 warn MQTT connection reconnect. roborock.0 2024-01-17 14:46:51.563 warn Failed to execute get_map_v1 on robot 5umEnoJEB0hmM5UmYlkumw Error: Request with id 8116 with method get_map_v1 timed out after 10 seconds for response.102 roborock.0 2024-01-17 14:46:51.398 debug Length of message queue: 4 roborock.0 2024-01-17 14:46:51.398 debug Length of message queue: 4 roborock.0 2024-01-17 14:46:51.272 debug Update map roborock.0 2024-01-17 14:46:50.809 warn MQTT connection close. roborock.0 2024-01-17 14:46:50.708 warn MQTT connection reconnect. roborock.0 2024-01-17 14:46:49.708 warn MQTT connection close. roborock.0 2024-01-17 14:46:49.542 warn MQTT connection reconnect. roborock.0 2024-01-17 14:46:49.365 warn Failed to execute get_map_v1 on robot 5umEnoJEB0hmM5UmYlkumw Error: Request with id 8111 with method get_map_v1 timed out after 10 seconds for response.102 roborock.0 2024-01-17 14:46:49.307 debug Length of message queue: 4 roborock.0 2024-01-17 14:46:49.306 debug Length of message queue: 4 roborock.0 2024-01-17 14:46:49.272 debug Update map roborock.0 2024-01-17 14:46:48.539 warn MQTT connection close. roborock.0 2024-01-17 14:46:48.411 warn MQTT connection reconnect. roborock.0 2024-01-17 14:46:47.411 warn MQTT connection close. roborock.0 2024-01-17 14:46:47.305 warn Failed to execute get_map_v1 on robot 5umEnoJEB0hmM5UmYlkumw Error: Request with id 8110 with method get_map_v1 timed out after 10 seconds for response.102 roborock.0 2024-01-17 14:46:47.303 debug Length of message queue: 4 roborock.0 2024-01-17 14:46:47.303 debug Length of message queue: 4 roborock.0 2024-01-17 14:46:47.287 warn MQTT connection reconnect. roborock.0 2024-01-17 14:46:47.272 debug Update map roborock.0 2024-01-17 14:46:46.284 warn MQTT connection close. roborock.0 2024-01-17 14:46:46.167 warn MQTT connection reconnect. roborock.0 2024-01-17 14:46:45.447 warn Failed to execute get_map_v1 on robot 5umEnoJEB0hmM5UmYlkumw Error: Request with id 8109 with method get_map_v1 timed out after 10 seconds for response.102 roborock.0 2024-01-17 14:46:45.341 debug Length of message queue: 4 roborock.0 2024-01-17 14:46:45.340 debug Length of message queue: 4 roborock.0 2024-01-17 14:46:45.272 debug Update map roborock.0 2024-01-17 14:46:45.167 warn MQTT connection close. roborock.0 2024-01-17 14:46:45.049 warn MQTT connection reconnect. roborock.0 2024-01-17 14:46:44.044 warn MQTT connection close. roborock.0 2024-01-17 14:46:43.925 warn MQTT connection reconnect. roborock.0 2024-01-17 14:46:43.331 warn Failed to execute get_map_v1 on robot 5umEnoJEB0hmM5UmYlkumw Error: Request with id 8108 with method get_map_v1 timed out after 10 seconds for response.102 roborock.0 2024-01-17 14:46:43.315 debug Length of message queue: 4 roborock.0 2024-01-17 14:46:43.314 debug Length of message queue: 4 roborock.0 2024-01-17 14:46:43.271 debug Update map roborock.0 2024-01-17 14:46:43.015 debug homedata successfully updated roborock.0 2024-01-17 14:46:42.923 warn MQTT connection close. roborock.0 2024-01-17 14:46:42.782 warn MQTT connection reconnect. roborock.0 2024-01-17 14:46:41.847 debug get_timer: "[] roborock.0 2024-01-17 14:46:41.846 debug Length of message queue: 5 roborock.0 2024-01-17 14:46:41.782 warn MQTT connection close. roborock.0 2024-01-17 14:46:41.674 warn MQTT connection reconnect. roborock.0 2024-01-17 14:46:41.605 debug getParameter for 5umEnoJEB0hmM5UmYlkumw: get_timer roborock.0 2024-01-17 14:46:41.605 debug get_server_timer: " + [] roborock.0 2024-01-17 14:46:41.605 debug Length of message queue: 5 roborock.0 2024-01-17 14:46:41.523 debug getParameter for 5umEnoJEB0hmM5UmYlkumw: get_server_timer roborock.0 2024-01-17 14:46:41.523 debug Length of message queue: 5 roborock.0 2024-01-17 14:46:41.352 debug getParameter for 5umEnoJEB0hmM5UmYlkumw: get_network_info roborock.0 2024-01-17 14:46:41.352 debug Consumables of robot: {"main_brush_work_time":68952,"side_brush_work_time":68952,"filter_work_time":68952,"filter_element_work_time":0,"sensor_dirty_time":97966} roborock.0 2024-01-17 14:46:41.352 debug Length of message queue: 4 roborock.0 2024-01-17 14:46:41.328 warn Failed to execute get_map_v1 on robot 5umEnoJEB0hmM5UmYlkumw Error: Request with id 8107 with method get_map_v1 timed out after 10 seconds for response.102 roborock.0 2024-01-17 14:46:41.271 debug Length of message queue: 4 roborock.0 2024-01-17 14:46:41.271 debug Length of message queue: 4 roborock.0 2024-01-17 14:46:41.266 debug Update map roborock.0 2024-01-17 14:46:41.225 debug getParameter for 5umEnoJEB0hmM5UmYlkumw: get_consumable roborock.0 2024-01-17 14:46:41.225 warn Failed to map rooms. You need to name your rooms via the mobile app on your phone. roborock.0 2024-01-17 14:46:41.225 debug All mapped rooms: [] roborock.0 2024-01-17 14:46:41.225 debug Length of message queue: 5 roborock.0 2024-01-17 14:46:41.148 debug Length of message queue: 5 roborock.0 2024-01-17 14:46:40.953 debug getParameter for 5umEnoJEB0hmM5UmYlkumw: get_room_mapping roborock.0 2024-01-17 14:46:40.940 debug get_status: {"msg_ver":2,"msg_seq":1433,"state":8,"battery":99,"clean_time":133,"clean_area":2172500,"error_code":0,"map_present":1,"in_cleaning":0,"in_returning":0,"in_fresh_state":1,"lab_status":1,"water_box_status":0,"fan_power":102,"dnd_enabled":0,"map_status":3,"is_locating":0,"lock_status":0} roborock.0 2024-01-17 14:46:40.940 debug Length of message queue: 5 roborock.0 2024-01-17 14:46:40.687 debug getParameter for 5umEnoJEB0hmM5UmYlkumw: get_status roborock.0 2024-01-17 14:46:40.686 debug Latest data requested roborock.0 2024-01-17 14:46:40.671 warn MQTT connection close. roborock.0 2024-01-17 14:46:40.528 warn MQTT connection reconnect. roborock.0 2024-01-17 14:46:39.526 warn MQTT connection close. roborock.0 2024-01-17 14:46:39.422 warn MQTT connection reconnect. roborock.0 2024-01-17 14:46:39.418 warn Failed to execute get_map_v1 on robot 5umEnoJEB0hmM5UmYlkumw Error: Request with id 8106 with method get_map_v1 timed out after 10 seconds for response.102 roborock.0 2024-01-17 14:46:39.410 debug Length of message queue: 5 roborock.0 2024-01-17 14:46:39.410 debug Length of message queue: 5 roborock.0 2024-01-17 14:46:39.263 debug Update map roborock.0 2024-01-17 14:46:38.419 warn MQTT connection close. roborock.0 2024-01-17 14:46:38.268 warn MQTT connection reconnect. roborock.0 2024-01-17 14:46:37.722 warn Failed to execute get_map_v1 on robot 5umEnoJEB0hmM5UmYlkumw Error: Request with id 8105 with method get_map_v1 timed out after 10 seconds for response.102 roborock.0 2024-01-17 14:46:37.719 debug Length of message queue: 5 roborock.0 2024-01-17 14:46:37.718 debug Length of message queue: 5 roborock.0 2024-01-17 14:46:37.263 debug Update map roborock.0 2024-01-17 14:46:37.248 warn MQTT connection close. roborock.0 2024-01-17 14:46:37.097 warn MQTT connection reconnect. roborock.0 2024-01-17 14:46:36.095 warn MQTT connection close. roborock.0 2024-01-17 14:46:35.970 warn MQTT connection reconnect. roborock.0 2024-01-17 14:46:35.567 warn Failed to execute get_map_v1 on robot 5umEnoJEB0hmM5UmYlkumw Error: Request with id 8104 with method get_map_v1 timed out after 10 seconds for response.102 roborock.0 2024-01-17 14:46:35.496 debug Length of message queue: 5 roborock.0 2024-01-17 14:46:35.496 debug Length of message queue: 5 roborock.0 2024-01-17 14:46:35.263 debug Update map roborock.0 2024-01-17 14:46:34.970 warn MQTT connection close. roborock.0 2024-01-17 14:46:34.854 warn MQTT connection reconnect. roborock.0 2024-01-17 14:46:33.845 warn MQTT connection close. roborock.0 2024-01-17 14:46:33.760 warn Failed to execute get_map_v1 on robot 5umEnoJEB0hmM5UmYlkumw Error: Request with id 8103 with method get_map_v1 timed out after 10 seconds for response.102 roborock.0 2024-01-17 14:46:33.744 debug Length of message queue: 5 roborock.0 2024-01-17 14:46:33.744 debug Length of message queue: 5 roborock.0 2024-01-17 14:46:33.728 warn MQTT connection reconnect. roborock.0 2024-01-17 14:46:33.262 debug Update map roborock.0 2024-01-17 14:46:32.728 warn MQTT connection close. roborock.0 2024-01-17 14:46:32.629 warn MQTT connection reconnect. roborock.0 2024-01-17 14:46:31.629 warn MQTT connection close. roborock.0 2024-01-17 14:46:31.515 warn MQTT connection reconnect. roborock.0 2024-01-17 14:46:31.355 warn Failed to execute get_map_v1 on robot 5umEnoJEB0hmM5UmYlkumw Error: Request with id 8102 with method get_map_v1 timed out after 10 seconds for response.102 roborock.0 2024-01-17 14:46:31.328 debug Length of message queue: 5 roborock.0 2024-01-17 14:46:31.327 debug Length of message queue: 5 roborock.0 2024-01-17 14:46:31.255 debug Update map roborock.0 2024-01-17 14:46:30.514 warn MQTT connection close. roborock.0 2024-01-17 14:46:30.410 warn MQTT connection reconnect. roborock.0 2024-01-17 14:46:29.694 warn Failed to execute get_map_v1 on robot 5umEnoJEB0hmM5UmYlkumw Error: Request with id 8101 with method get_map_v1 timed out after 10 seconds for response.102 roborock.0 2024-01-17 14:46:29.675 debug Length of message queue: 5 roborock.0 2024-01-17 14:46:29.675 debug Length of message queue: 5 roborock.0 2024-01-17 14:46:29.410 warn MQTT connection close. roborock.0 2024-01-17 14:46:29.303 warn MQTT connection reconnect. roborock.0 2024-01-17 14:46:29.254 debug Update map roborock.0 2024-01-17 14:46:28.292 warn MQTT connection close. roborock.0 2024-01-17 14:46:28.189 warn MQTT connection reconnect. roborock.0 2024-01-17 14:46:27.550 warn Failed to execute get_map_v1 on robot 5umEnoJEB0hmM5UmYlkumw Error: Request with id 8100 with method get_map_v1 timed out after 10 seconds for response.102 roborock.0 2024-01-17 14:46:27.253 debug Length of message queue: 4 roborock.0 2024-01-17 14:46:27.253 debug Length of message queue: 4 roborock.0 2024-01-17 14:46:27.253 debug Update map roborock.0 2024-01-17 14:46:27.189 warn MQTT connection close. roborock.0 2024-01-17 14:46:27.082 warn MQTT connection reconnect. roborock.0 2024-01-17 14:46:26.079 warn MQTT connection close. roborock.0 2024-01-17 14:46:25.960 warn MQTT connection reconnect. roborock.0 2024-01-17 14:46:25.448 warn Failed to execute get_map_v1 on robot 5umEnoJEB0hmM5UmYlkumw Error: Request with id 8099 with method get_map_v1 timed out after 10 seconds for response.102 roborock.0 2024-01-17 14:46:25.312 debug Length of message queue: 4 roborock.0 2024-01-17 14:46:25.311 debug Length of message queue: 4 roborock.0 2024-01-17 14:46:25.253 debug Update map roborock.0 2024-01-17 14:46:24.952 warn MQTT connection close. roborock.0 2024-01-17 14:46:24.814 warn MQTT connection reconnect. roborock.0 2024-01-17 14:46:23.813 warn MQTT connection close. roborock.0 2024-01-17 14:46:23.700 warn MQTT connection reconnect. roborock.0 2024-01-17 14:46:23.554 warn Failed to execute get_map_v1 on robot 5umEnoJEB0hmM5UmYlkumw Error: Request with id 8098 with method get_map_v1 timed out after 10 seconds for response.102 roborock.0 2024-01-17 14:46:23.381 debug Length of message queue: 4 roborock.0 2024-01-17 14:46:23.380 debug Length of message queue: 4 roborock.0 2024-01-17 14:46:23.252 debug Update map roborock.0 2024-01-17 14:46:22.700 warn MQTT connection close. roborock.0 2024-01-17 14:46:22.552 warn MQTT connection reconnect. roborock.0 2024-01-17 14:46:21.552 warn MQTT connection close. roborock.0 2024-01-17 14:46:21.425 warn MQTT connection reconnect. -
@copystring
Ich müsste ehrlich gesagt lügen.Kann nachher mal schauen, was meine Logs sagen... hast du ne vermutung ?
...wenn du schon so gezielt fragst ...
-
Wenn der Fehler mit der neusten dev von GitHub genau nach einer Stunde Auftritt, hätte ich eine Idee. Könnte ihr das bestätigen? Lässt sich das wiederholt reproduzieren? Zum Beispiel: disconnect und reconnect schleife immer eine Stunde, nachdem der Adapter gestartet wurde.
-
das ja einfach nachzustellen -> Mein Adapter ist grade aus!
Ich schalte den ein und warte ab
-> Ich berichte, sobald sich was tut ... is später....
