Neuer Adapter für Roborock-Staubsauger

tritanium

@copystring

Du meinst im Adapter Benutzername/Passwort ?? ....oder die Datenpunkte unter den Objekten ??

Mit welcher Version soll ich das machen ... stable oder /dev ??

tritanium

@copystring

Okay, folgend verfahren

aktuelle /dev "gerade eben" installiert.
Alle Objekte undter "roborock.0" gelöscht
Adapter gestartet.

-> Sieht schon besser aus, jedenfalls kommt kein crash bzw. restart mehr ...

Nur noch die hier:

roborock.0
   2024-01-14 21:20:21.553	warn	State "roborock.0.Devices.5kt1jy0ATJPgji5k0hJAZg.cleaningInfo.Records.19.map_flag" has no existing object, this might lead to an error in future versions
roborock.0
   2024-01-14 21:20:18.942	warn	State "roborock.0.Devices.5kt1jy0ATJPgji5k0hJAZg.cleaningInfo.Records.18.map_flag" has no existing object, this might lead to an error in future versions
roborock.0
   2024-01-14 21:20:16.829	warn	State "roborock.0.Devices.5kt1jy0ATJPgji5k0hJAZg.cleaningInfo.Records.17.map_flag" has no existing object, this might lead to an error in future versions
roborock.0
   2024-01-14 21:20:14.711	warn	State "roborock.0.Devices.5kt1jy0ATJPgji5k0hJAZg.cleaningInfo.Records.16.map_flag" has no existing object, this might lead to an error in future versions
roborock.0
   2024-01-14 21:20:12.283	warn	State "roborock.0.Devices.5kt1jy0ATJPgji5k0hJAZg.cleaningInfo.Records.15.map_flag" has no existing object, this might lead to an error in future versions
roborock.0
   2024-01-14 21:20:10.153	warn	State "roborock.0.Devices.5kt1jy0ATJPgji5k0hJAZg.cleaningInfo.Records.14.map_flag" has no existing object, this might lead to an error in future versions
roborock.0
   2024-01-14 21:20:08.024	warn	State "roborock.0.Devices.5kt1jy0ATJPgji5k0hJAZg.cleaningInfo.Records.13.map_flag" has no existing object, this might lead to an error in future versions
roborock.0
   2024-01-14 21:20:05.826	warn	State "roborock.0.Devices.5kt1jy0ATJPgji5k0hJAZg.cleaningInfo.Records.12.map_flag" has no existing object, this might lead to an error in future versions
roborock.0
   2024-01-14 21:20:03.337	warn	State "roborock.0.Devices.5kt1jy0ATJPgji5k0hJAZg.cleaningInfo.Records.11.map_flag" has no existing object, this might lead to an error in future versions
roborock.0
   2024-01-14 21:20:01.058	warn	State "roborock.0.Devices.5kt1jy0ATJPgji5k0hJAZg.cleaningInfo.Records.10.map_flag" has no existing object, this might lead to an error in future versions
roborock.0
   2024-01-14 21:19:58.918	warn	State "roborock.0.Devices.5kt1jy0ATJPgji5k0hJAZg.cleaningInfo.Records.9.map_flag" has no existing object, this might lead to an error in future versions
roborock.0
   2024-01-14 21:19:56.988	warn	State "roborock.0.Devices.5kt1jy0ATJPgji5k0hJAZg.cleaningInfo.Records.8.map_flag" has no existing object, this might lead to an error in future versions
roborock.0
   2024-01-14 21:19:54.802	warn	State "roborock.0.Devices.5kt1jy0ATJPgji5k0hJAZg.cleaningInfo.Records.7.map_flag" has no existing object, this might lead to an error in future versions
roborock.0
   2024-01-14 21:19:52.713	warn	State "roborock.0.Devices.5kt1jy0ATJPgji5k0hJAZg.cleaningInfo.Records.6.map_flag" has no existing object, this might lead to an error in future versions
roborock.0
   2024-01-14 21:19:50.432	warn	State "roborock.0.Devices.5kt1jy0ATJPgji5k0hJAZg.cleaningInfo.Records.5.map_flag" has no existing object, this might lead to an error in future versions
roborock.0
   2024-01-14 21:19:48.282	warn	State "roborock.0.Devices.5kt1jy0ATJPgji5k0hJAZg.cleaningInfo.Records.4.map_flag" has no existing object, this might lead to an error in future versions
roborock.0
   2024-01-14 21:19:47.373	warn	Failed to execute get_status on robot 5kt1jy0ATJPgji5k0hJAZg Error: Local request with id 1 with method get_status timed out after 10 seconds for response.102
roborock.0
   2024-01-14 21:19:45.473	warn	State "roborock.0.Devices.5kt1jy0ATJPgji5k0hJAZg.cleaningInfo.Records.3.map_flag" has no existing object, this might lead to an error in future versions
roborock.0
   2024-01-14 21:19:43.123	warn	State "roborock.0.Devices.5kt1jy0ATJPgji5k0hJAZg.cleaningInfo.Records.2.map_flag" has no existing object, this might lead to an error in future versions
roborock.0
   2024-01-14 21:19:40.852	warn	State "roborock.0.Devices.5kt1jy0ATJPgji5k0hJAZg.cleaningInfo.Records.1.map_flag" has no existing object, this might lead to an error in future versions
roborock.0
   2024-01-14 21:19:38.588	warn	State "roborock.0.Devices.5kt1jy0ATJPgji5k0hJAZg.cleaningInfo.Records.0.map_flag" has no existing object, this might lead to an error in future versions
roborock.0
   2024-01-14 21:17:16.350	info	MQTT initialized

Ich denke aber, damit kann/muss ich wohl derzeit leben

Dann beobachte ich nun erst einmal weiter ....

Danke für den "anschubser" ....

copystring

@tritanium Für den Fehler erstellt bitte ein Issue auf GitHub mit Debuglog. Dann kann ich das auch noch lösen.

tritanium

hmm, okay, nach durchsicht aller neu angelegten Objekte fiel mir der hier auf:

Ich denke der war auch gemeint , oder ??

Nun gut, jetzt läufts ja erst einmal wieder... Ich bin aber auch ein Schussel

copystring

@tritanium said in Neuer Adapter für Roborock-Staubsauger:

Ich denke der war auch gemeint , oder ??

Ja, genau das meinte ich.

tritanium

@copystring

Ich schaue mir das mal an, den DP den das LOG anmäkelt, habe ich unter den Objekten...

-> Ich lasse glecih mal einen saugen und gucke was sich tut....

Aber mal was anderes:

Nachdem der Adapter nun vermeindlich sauber funktioniert, hat mich die App gerade darauf hingewiesen, das mein Konto "auf einem anderen Gerät angemeldet ist"

-> Ignorier ich das, oder was soll mir das sagen ....??

Meine Frau hat die Appa auch installiert und nutzt diese, aber da kam keine solche Meldung....

Bin ratlos

copystring

@tritanium said in Neuer Adapter für Roborock-Staubsauger:

"auf einem anderen Gerät angemeldet ist"

Die Meldung erscheint beim ersten Anmelden des Adapters, weil eine neue ID erstellt wird. Die wurde neu erstellt, da du alle Datenpunkte gelöscht hast.

Deine Frau bekommt die Meldung nicht, weil du ihr das Gerät wahrscheinlich zu Ihrem Konto geteilt hast. Die Meldung erscheint logischerweise nur auf dem Hauptkonto.

Möglicherweise waren beim ersten Start nicht alle Objekte angelegt. Starte nochmal neu. Vielleicht sind dann alle Fehler/Warnungen weg.

tritanium

@copystring

So, habe mir das angeschaut. Zunächst:

-> Keine ERRORS oder sonstigen Sachen, die NICHT funktionieren .... Es kommen WARNINGS aber nur für den Q7 Max+ Roboter ... beim Q Revo NICHT.

Hier mal die DPs vom Q Revo:

Ich habe mal gelb markiert das "map_flag" welches im Logging für den Q7 Max+ bemäkelt wird:

Und hier die DPs zum Q7 Max+:

-> Da fehlt der Datenpunkt "komplett"

Ist der Datenpunkt Roboter-Typen abhängig??

brauchst du dazu ein Issue auf GIT ... bzw. ein Debug ? Dann müsste ich das noch erstellen ...

lg Micha

copystring

@tritanium Ja genau. Nicht jedes Gerät hat die gleichen Funktionen. Manchmal kommen neuen Funktionen dazu. Die müssen dann eingebaut werden. Wenn etwas fehlt, wie z.B. map_flag, brauche ich ein Issue auf GitHub mit Debuglog.

tritanium

@copystring

So, Issue ist angelgt, DEBUG Log liegt bei ...

Danke nochmals, für die schnelle Hilfe...

da_Woody

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

hgerstung

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!

adsfa

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!

frankyboy73

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.

copystring

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

tritanium

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):

2024-01-15 14:45:02.817 - info: daswetter.0 (1750325) starting. Version 3.1.12 in /opt/iobroker/node_modules/iobroker.daswetter, node: v18.17.0, js-controller: 5.0.17
2024-01-15 14:45:15.962 - info: daswetter.0 (1750325) Terminated (ADAPTER_REQUESTED_TERMINATION): All data handled, adapter stopped until next scheduled moment
2024-01-15 14:45:16.488 - info: daswetter.0 (1750325) cleaned everything up...
2024-01-15 14:45:16.544 - info: host.iobroker instance system.adapter.daswetter.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
2024-01-15 14:47:59.516 - info: linux-control.0 (1703) getting data from ioBroker (192.168.50.5:22)
2024-01-15 14:48:12.808 - info: linux-control.0 (1703) successful received data from ioBroker (192.168.50.5:22)
2024-01-15 14:49:19.240 - warn: roborock.0 (1558318) MQTT connection close.
2024-01-15 14:49:19.249 - warn: roborock.0 (1558318) MQTT connection reconnect.
2024-01-15 14:53:12.810 - info: linux-control.0 (1703) getting data from ioBroker (192.168.50.5:22)
2024-01-15 14:53:42.518 - info: linux-control.0 (1703) successful received data from ioBroker (192.168.50.5:22)
2024-01-15 14:58:42.519 - info: linux-control.0 (1703) getting data from ioBroker (192.168.50.5:22)
2024-01-15 14:58:56.226 - info: linux-control.0 (1703) successful received data from ioBroker (192.168.50.5:22)
2024-01-15 15:00:00.056 - info: javascript.0 (1557799) script.js.Verbrauchszaehlungen.Gasverbrauch: getState(id=0_userdata.0.Gaszähler.tmp.Stunde, timerId=undefined) => {"val":10200.630000036932,"ack":true,"ts":1705323600327,"q":0,"c":"script.js.Verbrauchszaehlungen.Gasverbrauch","from":"system.adapter.javascript.0","user":"system.user.admin","lc":1705323600327}
2024-01-15 15:00:00.058 - info: javascript.0 (1557799) script.js.Verbrauchszaehlungen.Gasverbrauch: getState(id=0_userdata.0.Gaszähler.Zählerstand.Gesamt_Kubik, timerId=undefined) => {"val":10201.390000036949,"ack":true,"ts":1705327159495,"q":0,"c":"script.js.Verbrauchszaehlungen.Gaszählerstand","from":"system.adapter.javascript.0","user":"system.user.admin","lc":1705327159495}
2024-01-15 15:00:00.058 - info: javascript.0 (1557799) script.js.Verbrauchszaehlungen.Gasverbrauch: setForeignState(id=0_userdata.0.Gaszähler.Stunde, state={"val":0.7600000000165892,"ack":true,"ts":1705327200058,"q":0,"from":"system.adapter.javascript.0","lc":1705327200058,"c":"script.js.Verbrauchszaehlungen.Gasverbrauch"})
2024-01-15 15:00:00.059 - info: javascript.0 (1557799) script.js.Verbrauchszaehlungen.Gasverbrauch: Aus: 10201.390000036949 - 10200.630000036932 = 0.7600000000165892
2024-01-15 15:00:00.059 - info: javascript.0 (1557799) script.js.Verbrauchszaehlungen.Gasverbrauch: subscribe: {"pattern":{"id":"0_userdata.0.Gaszähler.Stunde","change":"any","q":0},"name":"script.js.Verbrauchszaehlungen.Gasverbrauch"}
2024-01-15 15:00:00.326 - info: host.iobroker instance system.adapter.daswetter.0 started with pid 1753594
2024-01-15 15:00:00.338 - info: javascript.0 (1557799) script.js.Verbrauchszaehlungen.Gasverbrauch: setForeignState(id=0_userdata.0.Gaszähler.tmp.Stunde, state={"val":10201.390000036949,"ack":true,"ts":1705327200338,"q":0,"from":"system.adapter.javascript.0","lc":1705327200338,"c":"script.js.Verbrauchszaehlungen.Gasverbrauch"})
2024-01-15 15:00:00.339 - info: javascript.0 (1557799) script.js.Verbrauchszaehlungen.Gasverbrauch: adapterUnsubscribe(id=[object Object])
2024-01-15 15:00:02.813 - info: daswetter.0 (1753594) starting. Version 3.1.12 in /opt/iobroker/node_modules/iobroker.daswetter, node: v18.17.0, js-controller: 5.0.17
2024-01-15 15:00:04.409 - info: host.iobroker instance system.adapter.dwd.0 started with pid 1753620
2024-01-15 15:00:07.295 - info: dwd.0 (1753620) starting. Version 2.8.5 in /opt/iobroker/node_modules/iobroker.dwd, node: v18.17.0, js-controller: 5.0.17
2024-01-15 15:00:15.010 - info: dwd.0 (1753620) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
2024-01-15 15:00:15.575 - info: host.iobroker instance system.adapter.dwd.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
2024-01-15 15:00:16.830 - info: daswetter.0 (1753594) Terminated (ADAPTER_REQUESTED_TERMINATION): All data handled, adapter stopped until next scheduled moment
2024-01-15 15:00:17.357 - info: daswetter.0 (1753594) cleaned everything up...
2024-01-15 15:00:17.408 - info: host.iobroker instance system.adapter.daswetter.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
2024-01-15 15:03:56.228 - info: linux-control.0 (1703) getting data from ioBroker (192.168.50.5:22)
2024-01-15 15:04:10.194 - info: linux-control.0 (1703) successful received data from ioBroker (192.168.50.5:22)
2024-01-15 15:05:00.053 - info: tr-064.0 (1741749) Scheduled restart.
2024-01-15 15:05:00.211 - info: tr-064.0 (1741749) terminating
2024-01-15 15:05:00.214 - info: tr-064.0 (1741749) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
2024-01-15 15:05:00.567 - info: tr-064.0 (1741749) terminating
2024-01-15 15:05:00.916 - info: host.iobroker instance system.adapter.tr-064.0 scheduled normal terminated and will be restarted on schedule.
2024-01-15 15:05:00.916 - info: host.iobroker Restart adapter system.adapter.tr-064.0 because enabled
2024-01-15 15:05:02.147 - info: host.iobroker instance system.adapter.tr-064.0 started with pid 1754695
2024-01-15 15:05:04.960 - info: tr-064.0 (1754695) starting. Version 4.2.18 in /opt/iobroker/node_modules/iobroker.tr-064, node: v18.17.0, js-controller: 5.0.17
2024-01-15 15:09:10.195 - info: linux-control.0 (1703) getting data from ioBroker (192.168.50.5:22)
2024-01-15 15:09:23.803 - info: linux-control.0 (1703) successful received data from ioBroker (192.168.50.5:22)
2024-01-15 15:14:23.803 - info: linux-control.0 (1703) getting data from ioBroker (192.168.50.5:22)
2024-01-15 15:14:37.455 - info: linux-control.0 (1703) successful received data from ioBroker (192.168.50.5:22)
2024-01-15 15:15:00.305 - info: host.iobroker instance system.adapter.daswetter.0 started with pid 1756823
2024-01-15 15:15:02.735 - info: daswetter.0 (1756823) starting. Version 3.1.12 in /opt/iobroker/node_modules/iobroker.daswetter, node: v18.17.0, js-controller: 5.0.17
2024-01-15 15:15:16.465 - info: daswetter.0 (1756823) Terminated (ADAPTER_REQUESTED_TERMINATION): All data handled, adapter stopped until next scheduled moment
2024-01-15 15:15:16.990 - info: daswetter.0 (1756823) cleaned everything up...
2024-01-15 15:15:17.042 - info: host.iobroker instance system.adapter.daswetter.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
2024-01-15 15:16:49.045 - info: knx.0 (1526) State value to set for "knx.0.Licht.Erdgeschoss.Gäste_WC_Deckenlicht_Wert" has to be type "number" but received type "boolean"
2024-01-15 15:19:17.085 - warn: javascript.0 (1557799) script.js.Steuerungen.Anwesenheit: Rolladen hinten | Kanal: Haustür Verschluss | Wert: true
2024-01-15 15:19:17.087 - info: javascript.0 (1557799) script.js.Steuerungen.Anwesenheit: Rolladen hinten/Seite -> "öffnen"
2024-01-15 15:19:18.868 - warn: javascript.0 (1557799) script.js.Alarm_e.Haustür_-_Offen_Warnung: Haustür geöffnet
2024-01-15 15:19:18.869 - warn: javascript.0 (1557799) script.js.Alarm_e.Haustür_-_Offen_Warnung: Alarmverzögerung 2 Min. startet
2024-01-15 15:19:37.457 - info: linux-control.0 (1703) getting data from ioBroker (192.168.50.5:22)
2024-01-15 15:19:51.115 - info: linux-control.0 (1703) successful received data from ioBroker (192.168.50.5:22)
2024-01-15 15:19:53.353 - info: alexa2.0 (1257502) Alexa-Push-Connection disconnected - retry: Retry Connection in 1s (undefined: undefined)
2024-01-15 15:19:54.893 - info: alexa2.0 (1257502) Alexa-Push-Connection (macDms = true) established. Disable Polling
2024-01-15 15:20:09.522 - warn: javascript.0 (1557799) script.js.Alarm_e.Haustür_-_Offen_Warnung: Alarmverzögerung deaktiviert
2024-01-15 15:20:09.522 - warn: javascript.0 (1557799) script.js.Alarm_e.Haustür_-_Offen_Warnung: Sperre Türalarm: true
2024-01-15 15:20:58.381 - warn: javascript.0 (1557799) script.js.Alarm_e.Haustür_-_Offen_Warnung: Haustür geschlossen
2024-01-15 15:20:58.394 - warn: javascript.0 (1557799) script.js.Alarm_e.Haustür_-_Offen_Warnung: Sperre Türalarm: false
2024-01-15 15:22:00.529 - warn: javascript.0 (1557799) script.js.Alarm_e.Haustür_-_Offen_Warnung: Haustür geöffnet
2024-01-15 15:22:00.530 - warn: javascript.0 (1557799) script.js.Alarm_e.Haustür_-_Offen_Warnung: Alarmverzögerung 2 Min. startet
2024-01-15 15:22:24.812 - warn: javascript.0 (1557799) script.js.Alarm_e.Haustür_-_Offen_Warnung: Haustür geschlossen
2024-01-15 15:22:24.813 - warn: javascript.0 (1557799) script.js.Alarm_e.Haustür_-_Offen_Warnung: Alarmverzögerung deaktiviert
2024-01-15 15:24:51.117 - info: linux-control.0 (1703) getting data from ioBroker (192.168.50.5:22)
2024-01-15 15:24:56.168 - info: homeconnect.0 (5948) 713010390084002479/programs/active/options: There is no program active.
2024-01-15 15:25:05.097 - info: linux-control.0 (1703) successful received data from ioBroker (192.168.50.5:22)
2024-01-15 15:30:00.303 - info: host.iobroker instance system.adapter.daswetter.0 started with pid 1759549
2024-01-15 15:30:02.711 - info: daswetter.0 (1759549) starting. Version 3.1.12 in /opt/iobroker/node_modules/iobroker.daswetter, node: v18.17.0, js-controller: 5.0.17
2024-01-15 15:30:04.378 - info: host.iobroker instance system.adapter.dwd.0 started with pid 1759576
2024-01-15 15:30:05.099 - info: linux-control.0 (1703) getting data from ioBroker (192.168.50.5:22)
2024-01-15 15:30:08.193 - info: dwd.0 (1759576) starting. Version 2.8.5 in /opt/iobroker/node_modules/iobroker.dwd, node: v18.17.0, js-controller: 5.0.17
2024-01-15 15:30:14.243 - info: dwd.0 (1759576) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
2024-01-15 15:30:14.786 - info: host.iobroker instance system.adapter.dwd.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
2024-01-15 15:30:16.868 - info: daswetter.0 (1759549) Terminated (ADAPTER_REQUESTED_TERMINATION): All data handled, adapter stopped until next scheduled moment
2024-01-15 15:30:17.386 - info: daswetter.0 (1759549) cleaned everything up...
2024-01-15 15:30:17.413 - info: host.iobroker instance system.adapter.daswetter.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
2024-01-15 15:30:19.957 - info: linux-control.0 (1703) successful received data from ioBroker (192.168.50.5:22)
2024-01-15 15:35:19.958 - info: linux-control.0 (1703) getting data from ioBroker (192.168.50.5:22)
2024-01-15 15:35:22.591 - error: roborock.0 (1558318) Failed to update updateHomeData with error: TypeError: Cannot read properties of null (reading 'devices')
2024-01-15 15:35:22.623 - error: roborock.0 (1558318) 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().
2024-01-15 15:35:22.630 - error: roborock.0 (1558318) unhandled promise rejection: Cannot read properties of null (reading 'receivedDevices')
2024-01-15 15:35:22.636 - error: roborock.0 (1558318) TypeError: Cannot read properties of null (reading 'receivedDevices')
at Roborock.isRemoteDevice (/opt/iobroker/node_modules/iobroker.roborock/main.js:576:40)
at Roborock.getConnector (/opt/iobroker/node_modules/iobroker.roborock/main.js:589:20)
at vacuum.getParameter (/opt/iobroker/node_modules/iobroker.roborock/lib/vacuum.js:254:21)
at Roborock.updateDataMinimumData (/opt/iobroker/node_modules/iobroker.roborock/main.js:635:4)
2024-01-15 15:35:22.636 - error: roborock.0 (1558318) Cannot read properties of null (reading 'receivedDevices')
2024-01-15 15:35:22.883 - info: roborock.0 (1558318) terminating
2024-01-15 15:35:22.884 - warn: roborock.0 (1558318) Terminated (UNCAUGHT_EXCEPTION): Without reason
2024-01-15 15:35:23.387 - info: roborock.0 (1558318) terminating
2024-01-15 15:35:23.584 - error: host.iobroker Caught by controller[1]: 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:
2024-01-15 15:35:23.584 - error: host.iobroker Caught by controller[1]: TypeError: Cannot read properties of null (reading 'receivedDevices')
2024-01-15 15:35:23.585 - error: host.iobroker Caught by controller[1]: at Roborock.isRemoteDevice (/opt/iobroker/node_modules/iobroker.roborock/main.js:576:40)
2024-01-15 15:35:23.585 - error: host.iobroker Caught by controller[1]: at Roborock.getConnector (/opt/iobroker/node_modules/iobroker.roborock/main.js:589:20)
2024-01-15 15:35:23.585 - error: host.iobroker Caught by controller[1]: at vacuum.getParameter (/opt/iobroker/node_modules/iobroker.roborock/lib/vacuum.js:254:21)
2024-01-15 15:35:23.585 - error: host.iobroker Caught by controller[1]: at Roborock.updateDataMinimumData (/opt/iobroker/node_modules/iobroker.roborock/main.js:635:4)
2024-01-15 15:35:23.585 - error: host.iobroker instance system.adapter.roborock.0 terminated with code 6 (UNCAUGHT_EXCEPTION)
2024-01-15 15:35:23.585 - info: host.iobroker Restart adapter system.adapter.roborock.0 because enabled
2024-01-15 15:35:33.618 - info: linux-control.0 (1703) successful received data from ioBroker (192.168.50.5:22)
2024-01-15 15:35:53.816 - info: host.iobroker instance system.adapter.roborock.0 started with pid 1761256
2024-01-15 15:35:58.053 - info: roborock.0 (1761256) starting. Version 0.5.1 (non-npm: copystring/ioBroker.roborock#dev) in /opt/iobroker/node_modules/iobroker.roborock, node: v18.17.0, js-controller: 5.0.17
2024-01-15 15:35:58.105 - info: roborock.0 (1761256) Starting adapter. This might take a few minutes depending on your setup. Please wait.
2024-01-15 15:36:04.071 - info: roborock.0 (1761256) MQTT initialized
2024-01-15 15:36:26.550 - info: homeconnect.0 (5948) 713010390084002479/programs/active/options: There is no program active.
2024-01-15 15:38:58.271 - warn: roborock.0 (1761256) Failed to execute get_network_info on robot 5kt1jy0ATJPgji5k0hJAZg Error: Local request with id 10 with method get_network_info timed out after 10 seconds for response.102
2024-01-15 15:40:33.618 - info: linux-control.0 (1703) getting data from ioBroker (192.168.50.5:22)
2024-01-15 15:40:47.984 - info: linux-control.0 (1703) successful received data from ioBroker (192.168.50.5:22)
2024-01-15 15:42:59.870 - info: roborock.0 (1761256) Starting adapter finished. Lets go!!!!!!!
2024-01-15 15:43:00.226 - error: roborock.0 (1761256) Failed to update updateHomeData with error: TypeError: Cannot read properties of null (reading 'devices')
2024-01-15 15:43:00.312 - error: roborock.0 (1761256) 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().
2024-01-15 15:43:00.313 - error: roborock.0 (1761256) unhandled promise rejection: Cannot read properties of null (reading 'devices')
2024-01-15 15:43:00.317 - error: roborock.0 (1761256) TypeError: Cannot read properties of null (reading 'devices')
at Roborock.onlineChecker (/opt/iobroker/node_modules/iobroker.roborock/main.js:557:32)
at Roborock.catchError (/opt/iobroker/node_modules/iobroker.roborock/main.js:1031:23)
2024-01-15 15:43:00.318 - error: roborock.0 (1761256) Cannot read properties of null (reading 'devices')
2024-01-15 15:43:00.338 - info: roborock.0 (1761256) terminating
2024-01-15 15:43:00.339 - warn: roborock.0 (1761256) Terminated (UNCAUGHT_EXCEPTION): Without reason
2024-01-15 15:43:00.545 - error: roborock.0 (1761256) 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().
2024-01-15 15:43:00.546 - error: roborock.0 (1761256) unhandled promise rejection: Cannot read properties of null (reading 'devices')
2024-01-15 15:43:00.547 - error: roborock.0 (1761256) TypeError: Cannot read properties of null (reading 'devices')
at Roborock.onlineChecker (/opt/iobroker/node_modules/iobroker.roborock/main.js:557:32)
at Roborock.catchError (/opt/iobroker/node_modules/iobroker.roborock/main.js:1031:23)
2024-01-15 15:43:00.547 - error: roborock.0 (1761256) Cannot read properties of null (reading 'devices')
2024-01-15 15:43:00.843 - info: roborock.0 (1761256) terminating
2024-01-15 15:43:01.096 - error: host.iobroker Caught by controller[0]: Downloading AlexxIT/go2rtc@v1.8.5...
2024-01-15 15:43:01.097 - error: host.iobroker Caught by controller[1]: 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:
2024-01-15 15:43:01.097 - error: host.iobroker Caught by controller[1]: TypeError: Cannot read properties of null (reading 'devices')
2024-01-15 15:43:01.097 - error: host.iobroker Caught by controller[1]: at Roborock.onlineChecker (/opt/iobroker/node_modules/iobroker.roborock/main.js:557:32)
2024-01-15 15:43:01.097 - error: host.iobroker Caught by controller[1]: at Roborock.catchError (/opt/iobroker/node_modules/iobroker.roborock/main.js:1031:23)
2024-01-15 15:43:01.097 - error: host.iobroker Caught by controller[2]: 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:
2024-01-15 15:43:01.097 - error: host.iobroker Caught by controller[2]: TypeError: Cannot read properties of null (reading 'devices')
2024-01-15 15:43:01.097 - error: host.iobroker Caught by controller[2]: at Roborock.onlineChecker (/opt/iobroker/node_modules/iobroker.roborock/main.js:557:32)
2024-01-15 15:43:01.097 - error: host.iobroker Caught by controller[2]: at Roborock.catchError (/opt/iobroker/node_modules/iobroker.roborock/main.js:1031:23)
2024-01-15 15:43:01.098 - error: host.iobroker instance system.adapter.roborock.0 terminated with code 6 (UNCAUGHT_EXCEPTION)
2024-01-15 15:43:01.098 - info: host.iobroker Restart adapter system.adapter.roborock.0 because enabled
2024-01-15 15:43:31.336 - info: host.iobroker instance system.adapter.roborock.0 started with pid 1762648
2024-01-15 15:43:35.440 - info: roborock.0 (1762648) starting. Version 0.5.1 (non-npm: copystring/ioBroker.roborock#dev) in /opt/iobroker/node_modules/iobroker.roborock, node: v18.17.0, js-controller: 5.0.17
2024-01-15 15:43:35.504 - info: roborock.0 (1762648) Starting adapter. This might take a few minutes depending on your setup. Please wait.
2024-01-15 15:43:41.459 - info: roborock.0 (1762648) MQTT initialized
2024-01-15 15:45:00.290 - info: host.iobroker instance system.adapter.daswetter.0 started with pid 1762837
2024-01-15 15:45:03.076 - info: daswetter.0 (1762837) starting. Version 3.1.12 in /opt/iobroker/node_modules/iobroker.daswetter, node: v18.17.0, js-controller: 5.0.17
2024-01-15 15:45:16.778 - info: daswetter.0 (1762837) Terminated (ADAPTER_REQUESTED_TERMINATION): All data handled, adapter stopped until next scheduled moment
2024-01-15 15:45:17.313 - info: daswetter.0 (1762837) cleaned everything up...
2024-01-15 15:45:17.371 - info: host.iobroker instance system.adapter.daswetter.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
2024-01-15 15:45:47.986 - info: linux-control.0 (1703) getting data from ioBroker (192.168.50.5:22)
2024-01-15 15:46:18.810 - info: linux-control.0 (1703) successful received data from ioBroker (192.168.50.5:22)
2024-01-15 15:46:33.971 - warn: roborock.0 (1762648) Failed to execute get_status on robot 5kt1jy0ATJPgji5k0hJAZg Error: Local request with id 1 with method get_status timed out after 10 seconds for response.102
2024-01-15 15:50:34.346 - info: roborock.0 (1762648) Starting adapter finished. Lets go!!!!!!!
2024-01-15 15:50:42.248 - warn: roborock.0 (1762648) Failed to execute get_map_v1 on robot 4Si5s3DNcsl0ATAl8e5UdI Error: Local request with id 224 with method get_status timed out after 10 seconds for response.102
2024-01-15 15:51:06.164 - error: roborock.0 (1762648) Failed to update updateHomeData with error: TypeError: Cannot read properties of null (reading 'devices')
2024-01-15 15:51:06.292 - error: roborock.0 (1762648) 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().
2024-01-15 15:51:06.293 - error: roborock.0 (1762648) unhandled promise rejection: Cannot read properties of null (reading 'devices')
2024-01-15 15:51:06.302 - error: roborock.0 (1762648) TypeError: Cannot read properties of null (reading 'devices')
at Roborock.onlineChecker (/opt/iobroker/node_modules/iobroker.roborock/main.js:557:32)
at Roborock.catchError (/opt/iobroker/node_modules/iobroker.roborock/main.js:1031:23)
2024-01-15 15:51:06.303 - error: roborock.0 (1762648) Cannot read properties of null (reading 'devices')
2024-01-15 15:51:06.338 - info: roborock.0 (1762648) terminating
2024-01-15 15:51:06.340 - warn: roborock.0 (1762648) Terminated (UNCAUGHT_EXCEPTION): Without reason
2024-01-15 15:51:06.516 - error: roborock.0 (1762648) 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().
2024-01-15 15:51:06.517 - error: roborock.0 (1762648) unhandled promise rejection: Cannot read properties of null (reading 'devices')
2024-01-15 15:51:06.518 - error: roborock.0 (1762648) TypeError: Cannot read properties of null (reading 'devices')
at Roborock.onlineChecker (/opt/iobroker/node_modules/iobroker.roborock/main.js:557:32)
at Roborock.catchError (/opt/iobroker/node_modules/iobroker.roborock/main.js:1031:23)
2024-01-15 15:51:06.518 - error: roborock.0 (1762648) Cannot read properties of null (reading 'devices')
2024-01-15 15:51:06.844 - info: roborock.0 (1762648) terminating
2024-01-15 15:51:07.105 - error: host.iobroker Caught by controller[1]: 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:
2024-01-15 15:51:07.106 - error: host.iobroker Caught by controller[2]: TypeError: Cannot read properties of null (reading 'devices')
2024-01-15 15:51:07.106 - error: host.iobroker Caught by controller[2]: at Roborock.onlineChecker (/opt/iobroker/node_modules/iobroker.roborock/main.js:557:32)
2024-01-15 15:51:07.106 - error: host.iobroker Caught by controller[2]: at Roborock.catchError (/opt/iobroker/node_modules/iobroker.roborock/main.js:1031:23)
2024-01-15 15:51:07.106 - error: host.iobroker Caught by controller[3]: 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:
2024-01-15 15:51:07.107 - error: host.iobroker Caught by controller[3]: TypeError: Cannot read properties of null (reading 'devices')
2024-01-15 15:51:07.107 - error: host.iobroker Caught by controller[3]: at Roborock.onlineChecker (/opt/iobroker/node_modules/iobroker.roborock/main.js:557:32)
2024-01-15 15:51:07.107 - error: host.iobroker Caught by controller[3]: at Roborock.catchError (/opt/iobroker/node_modules/iobroker.roborock/main.js:1031:23)
2024-01-15 15:51:07.107 - error: host.iobroker instance system.adapter.roborock.0 terminated with code 6 (UNCAUGHT_EXCEPTION)
2024-01-15 15:51:07.107 - info: host.iobroker Restart adapter system.adapter.roborock.0 because enabled
2024-01-15 15:51:07.107 - warn: host.iobroker Do not restart adapter system.adapter.roborock.0 because restart loop detected
2024-01-15 15:51:18.810 - info: linux-control.0 (1703) getting data from ioBroker (192.168.50.5:22)
2024-01-15 15:51:32.436 - info: linux-control.0 (1703) successful received data from ioBroker (192.168.50.5:22)

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....:

roborock.0
   2024-01-15 17:40:06.288	error	Cannot read properties of null (reading 'devices')
roborock.0
   2024-01-15 17:40:06.288	error	TypeError: Cannot read properties of null (reading 'devices') at Roborock.onlineChecker (/opt/iobroker/node_modules/iobroker.roborock/main.js:557:32) at Roborock.catchError (/opt/iobroker/node_modules/iobroker.roborock/main.js:1031:23)
roborock.0
   2024-01-15 17:40:06.287	error	unhandled promise rejection: Cannot read properties of null (reading 'devices')
roborock.0
   2024-01-15 17:40:06.286	error	Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().
roborock.0
   2024-01-15 17:40:06.113	warn	Terminated (UNCAUGHT_EXCEPTION): Without reason
roborock.0
   2024-01-15 17:40:06.111	info	terminating
roborock.0
   2024-01-15 17:40:06.067	error	Cannot read properties of null (reading 'devices')
roborock.0
   2024-01-15 17:40:06.066	error	TypeError: Cannot read properties of null (reading 'devices') at Roborock.onlineChecker (/opt/iobroker/node_modules/iobroker.roborock/main.js:557:32) at Roborock.catchError (/opt/iobroker/node_modules/iobroker.roborock/main.js:1031:23)
roborock.0
   2024-01-15 17:40:06.056	error	unhandled promise rejection: Cannot read properties of null (reading 'devices')
roborock.0
   2024-01-15 17:40:06.055	error	Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().
roborock.0
   2024-01-15 17:40:05.932	error	Failed to update updateHomeData with error: TypeError: Cannot read properties of null (reading 'devices')
roborock.0
   2024-01-15 17:39:50.256	info	Starting adapter finished. Lets go!!!!!!!
roborock.0
   2024-01-15 17:36:04.620	warn	Failed to execute get_water_box_custom_mode on robot 5kt1jy0ATJPgji5k0hJAZg Error: Local request with id 37 with method get_water_box_custom_mode timed out after 10 seconds for response.102
roborock.0
   2024-01-15 17:32:54.513	info	MQTT initialized
roborock.0
   2024-01-15 17:32:48.505	info	Starting adapter. This might take a few minutes depending on your setup. Please wait.
roborock.0
   2024-01-15 17:32:48.450	info	starting. Version 0.5.1 (non-npm: copystring/ioBroker.roborock#dev) in /opt/iobroker/node_modules/iobroker.roborock, node: v18.17.0, js-controller: 5.0.17

@copystring : Debug Log & Git Issue ?

lg Micha

adsfa

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

copystring

@adsfa stimmt. Das muss ich mal anpassen.

copystring

@tritanium Teste bitte die neue dev von GitHub.

tritanium

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

roborock.0
   2024-01-16 08:37:10.420	warn	MQTT connection close.
roborock.0
   2024-01-16 08:37:10.325	warn	MQTT connection reconnect.
roborock.0
   2024-01-16 08:37:09.324	warn	MQTT connection close.
roborock.0
   2024-01-16 08:37:09.233	warn	MQTT connection reconnect.
roborock.0
   2024-01-16 08:37:08.232	warn	MQTT connection close.
roborock.0
   2024-01-16 08:37:08.136	warn	MQTT connection reconnect.
roborock.0
   2024-01-16 08:37:07.135	warn	MQTT connection close.
roborock.0
   2024-01-16 08:37:07.038	warn	MQTT connection reconnect.
roborock.0
   2024-01-16 08:37:06.377	warn	Failed to execute get_map_v1 on robot 4Si5s3DNcsl0ATAl8e5UdI Error: Request with id 28705 with method get_map_v1 timed out after 10 seconds for response.102
roborock.0
   2024-01-16 08:37:06.038	warn	MQTT connection close.
roborock.0
   2024-01-16 08:37:05.951	warn	MQTT connection reconnect.
roborock.0
   2024-01-16 08:37:05.746	warn	Failed to execute get_map_v1 on robot 5kt1jy0ATJPgji5k0hJAZg Error: Request with id 28704 with method get_map_v1 timed out after 10 seconds for response.102
roborock.0
   2024-01-16 08:37:04.951	warn	MQTT connection close.
roborock.0
   2024-01-16 08:37:04.854	warn	MQTT connection reconnect.
roborock.0
   2024-01-16 08:37:03.854	warn	MQTT connection close.
roborock.0
   2024-01-16 08:37:03.743	warn	MQTT connection reconnect.
roborock.0
   2024-01-16 08:37:02.742	warn	MQTT connection close.
roborock.0
   2024-01-16 08:37:02.655	warn	MQTT connection reconnect.
roborock.0
   2024-01-16 08:37:01.655	warn	MQTT connection close.
linux-control.0
   2024-01-16 08:37:01.566	info	getting data from ioBroker (192.168.50.5:22)
roborock.0
   2024-01-16 08:37:01.553	warn	MQTT connection reconnect.
roborock.0
   2024-01-16 08:37:01.430	warn	Failed to execute get_map_v1 on robot 4Si5s3DNcsl0ATAl8e5UdI Error: Request with id 28696 with method get_map_v1 timed out after 10 seconds for response.102
roborock.0
   2024-01-16 08:37:00.740	warn	Failed to execute get_map_v1 on robot 5kt1jy0ATJPgji5k0hJAZg Error: Request with id 28692 with method get_map_v1 timed out after 10 seconds for response.102
roborock.0
   2024-01-16 08:37:00.553	warn	MQTT connection close.
roborock.0
   2024-01-16 08:37:00.446	warn	MQTT connection reconnect.
roborock.0
   2024-01-16 08:36:59.445	warn	MQTT connection close.
roborock.0
   2024-01-16 08:36:59.338	warn	MQTT connection reconnect.
roborock.0
   2024-01-16 08:36:58.337	warn	MQTT connection close.
roborock.0
   2024-01-16 08:36:58.232	warn	MQTT connection reconnect.
roborock.0
   2024-01-16 08:36:57.232	warn	MQTT connection close.
roborock.0
   2024-01-16 08:36:57.125	warn	MQTT connection reconnect.
roborock.0
   2024-01-16 08:36:56.337	warn	Failed to execute get_map_v1 on robot 4Si5s3DNcsl0ATAl8e5UdI Error: Request with id 28691 with method get_map_v1 timed out after 10 seconds for response.102
roborock.0
   2024-01-16 08:36:56.126	warn	MQTT connection close.
roborock.0
   2024-01-16 08:36:56.018	warn	MQTT connection reconnect.
roborock.0
   2024-01-16 08:36:55.792	warn	Failed to execute get_map_v1 on robot 5kt1jy0ATJPgji5k0hJAZg Error: Request with id 28685 with method get_map_v1 timed out after 10 seconds for response.102
roborock.0
   2024-01-16 08:36:55.018	warn	MQTT connection close.
roborock.0
   2024-01-16 08:36:54.912	warn	MQTT connection reconnect.
roborock.0
   2024-01-16 08:36:53.910	warn	MQTT connection close.
roborock.0
   2024-01-16 08:36:53.809	warn	MQTT connection reconnect.
roborock.0
   2024-01-16 08:36:52.809	warn	MQTT connection close.
roborock.0
   2024-01-16 08:36:52.700	warn	MQTT connection reconnect.
roborock.0
   2024-01-16 08:36:51.699	warn	MQTT connection close.
roborock.0
   2024-01-16 08:36:51.592	warn	MQTT connection reconnect.
roborock.0
   2024-01-16 08:36:51.393	warn	Failed to execute get_map_v1 on robot 4Si5s3DNcsl0ATAl8e5UdI Error: Request with id 28679 with method get_map_v1 timed out after 10 seconds for response.102
roborock.0
   2024-01-16 08:36:50.748	warn	Failed to execute get_map_v1 on robot 5kt1jy0ATJPgji5k0hJAZg Error: Request with id 28678 with method get_map_v1 timed out after 10 seconds for response.102
roborock.0
   2024-01-16 08:36:50.591	warn	MQTT connection close.
roborock.0
   2024-01-16 08:36:50.487	warn	MQTT connection reconnect.
roborock.0
   2024-01-16 08:36:49.486	warn	MQTT connection close.
roborock.0
   2024-01-16 08:36:49.379	warn	MQTT connection reconnect.
roborock.0
   2024-01-16 08:36:48.378	warn	MQTT connection close.
roborock.0
   2024-01-16 08:36:48.272	warn	MQTT connection reconnect.
roborock.0
   2024-01-16 08:36:47.270	warn	MQTT connection close.
roborock.0
   2024-01-16 08:36:47.160	warn	MQTT connection reconnect.
roborock.0
   2024-01-16 08:36:46.373	warn	Failed to execute get_map_v1 on robot 4Si5s3DNcsl0ATAl8e5UdI Error: Request with id 28670 with method get_map_v1 timed out after 10 seconds for response.102
roborock.0
   2024-01-16 08:36:46.160	warn	MQTT connection close.
roborock.0
   2024-01-16 08:36:46.053	warn	MQTT connection reconnect.
roborock.0
   2024-01-16 08:36:45.785	warn	Failed to execute get_map_v1 on robot 5kt1jy0ATJPgji5k0hJAZg Error: Request with id 28666 with method get_map_v1 timed out after 10 seconds for response.102
roborock.0
   2024-01-16 08:36:45.053	warn	MQTT connection close.
roborock.0
   2024-01-16 08:36:44.946	warn	MQTT connection reconnect.
roborock.0
   2024-01-16 08:36:43.946	warn	MQTT connection close.
roborock.0
   2024-01-16 08:36:43.840	warn	MQTT connection reconnect.
roborock.0
   2024-01-16 08:36:42.840	warn	MQTT connection close.
roborock.0
   2024-01-16 08:36:42.735	warn	MQTT connection reconnect.
roborock.0
   2024-01-16 08:36:41.735	warn	MQTT connection close.
roborock.0
   2024-01-16 08:36:41.625	warn	MQTT connection reconnect.

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

NEWS

Neuer Adapter für Roborock-Staubsauger

Support us

854
Online

31.7k
Users

79.8k
Topics

1.3m
Posts

NEWS

Neuer Adapter für Roborock-Staubsauger

Support us

854Online

31.7kUsers

79.8kTopics

1.3mPosts

854
Online

31.7k
Users

79.8k
Topics

1.3m
Posts