Neuer Adapter für Roborock-Staubsauger
-
ich mach mal eben .... kann ja nur besser werden
Moment....
So, fertig... keine besonderen Vorkommnisse (würde man beim Bund sagen)
Ich warte jetzt wieder ab ...
-
-
Ja. Sagt dir aber auch ein erneutes Ausführen von
iob nodejs-updateDa sollte zweimal 'Nothing to do' drin stehen.
-
jepp, tuts auch ....
ich hatte Spasseshalber mal ein iob diag gemacht.... aaaalter, kommen da infos
-
@tritanium sagte in Neuer Adapter für Roborock-Staubsauger:
aaaalter, kommen da infos
Ist halt eine umfassende Diagnose von deiner Kiste.
-
@tritanium
Bei mir ist beides seit langem auf der aktuellen Version, trotzdem kommen die diskutierten MQTT connect/reconnect-Fehler:pi@raspberrypi:~ $ node -v
v18.19.0
pi@raspberrypi:~ $
pi@raspberrypi:~ $ npm -v
10.2.3
pi@raspberrypi:~ $Gruß jahnbes.
-
Warum auch immer, habe ich nochmals die aktuelle /dev installiert und gegen 22.30 Uhr den Adapter gestartet.
Was soll ich sagen: ...pünktlich wie von dir beschrieben um 23.31 ging es dann gerade los...
Erst ein MQTT disconnect... und seit dem re-connects im Sekundentakt.
grrrmpf....
Und nun ?? wie helfen wir dir bei der Analyse bzw. fixing ??
-
Bitte die neue dev von gerade eben installieren. Dort wurde der mqtt client aktualisiert.
-
Okay, geht klar.... spiele eben die /dev neu ein....
-
Habe extra gewartet
1h ist rum und et voila:
Aber ich gehe nun erst einmal in die Falle. Den Adapter lasse ich solange aus
NACHTRAG:
Wenn ich den Adapter beende kommt das hier nich im Log:
host.iobroker 2024-01-18 01:47:36.327 info instance system.adapter.roborock.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION) roborock.0 2024-01-18 01:47:36.138 error DB closed roborock.0 2024-01-18 01:47:36.138 error Error: DB closed at close (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:184:25) at Socket.<anonymous> (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:151:20) at Object.onceWrapper (node:events:632:26) at Socket.emit (node:events:517:28) at Socket.emit (node:domain:489:12) at TCP.<anonymous> (node:net:350:12) roborock.0 2024-01-18 01:47:36.137 error unhandled promise rejection: DB closed roborock.0 2024-01-18 01:47:36.137 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-18 01:47:36.133 error DB closed roborock.0 2024-01-18 01:47:36.132 error Error: DB closed at close (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:184:25) at Socket.<anonymous> (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:151:20) at Object.onceWrapper (node:events:632:26) at Socket.emit (node:events:517:28) at Socket.emit (node:domain:489:12) at TCP.<anonymous> (node:net:350:12) roborock.0 2024-01-18 01:47:36.131 error unhandled promise rejection: DB closed roborock.0 2024-01-18 01:47:36.131 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-18 01:47:36.068 error DB closed roborock.0 2024-01-18 01:47:36.068 error Error: DB closed at close (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:184:25) at Socket.<anonymous> (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:151:20) at Object.onceWrapper (node:events:632:26) at Socket.emit (node:events:517:28) at Socket.emit (node:domain:489:12) at TCP.<anonymous> (node:net:350:12) roborock.0 2024-01-18 01:47:36.055 error unhandled promise rejection: DB closed roborock.0 2024-01-18 01:47:36.054 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-18 01:47:36.041 info terminatingSo als Info noch
und nun Gute N8 -
@copystring sagte in Neuer Adapter für Roborock-Staubsauger:
Bitte die neue dev von gerade eben installieren. Dort wurde der mqtt client aktualisiert.
hmpf, gerade eben...
hab nach der vorigen dev um 23:25 den adapter angeworfen. wie du sagtest, um 00:26 gings los... 1 stunde.
ok, werd updaten und das teil wieder anwerfen. -
@copystring schlechte nachrichten. nach ziemlich genau einer stunde wieder
roborock.0 2024-01-18 06:39:49.784 warn MQTT connection reconnect. roborock.0 2024-01-18 06:39:48.783 warn MQTT connection close. roborock.0 2024-01-18 06:39:48.688 warn MQTT connection reconnect. roborock.0 2024-01-18 06:39:47.687 warn MQTT connection close. roborock.0 2024-01-18 06:39:47.589 warn MQTT connection reconnect. roborock.0 2024-01-18 06:39:46.587 warn MQTT connection close. roborock.0 2024-01-18 06:39:46.484 warn MQTT connection reconnect. roborock.0 2024-01-18 06:39:45.483 warn MQTT connection close. roborock.0 2024-01-18 06:39:45.376 warn MQTT connection reconnect. roborock.0 2024-01-18 06:39:44.376 warn MQTT connection close. roborock.0 2024-01-18 06:39:44.270 warn MQTT connection reconnect. roborock.0 2024-01-18 06:39:43.269 warn MQTT connection close. roborock.0 2024-01-18 06:39:43.170 warn MQTT connection reconnect. roborock.0 2024-01-18 06:39:42.170 warn MQTT connection close. roborock.0 2024-01-18 06:39:42.053 warn Failed to map rooms. You need to name your rooms via the mobile app on your phone. roborock.0 2024-01-18 06:39:42.009 warn MQTT connection reconnect. roborock.0 2024-01-18 06:39:42.009 warn MQTT connection close. roborock.0 2024-01-18 06:39:41.984 warn Reconnecting mqtt client! roborock.0 2024-01-18 06:38:42.030 warn Failed to map rooms. You need to name your rooms via the mobile app on your phone. roborock.0 2024-01-18 06:37:41.944 warn Failed to map rooms. You need to name your rooms via the mobile app on your phone. roborock.0 2024-01-18 06:36:41.919 warn Failed to map rooms. You need to name your rooms via the mobile app on your phone.gestartet um
roborock.0 2024-01-18 05:39:42.337 warn Failed to map rooms. You need to name your rooms via the mobile app on your phone. roborock.0 2024-01-18 05:39:42.337 debug All mapped rooms: [] roborock.0 2024-01-18 05:39:42.336 debug Length of message queue: 0 roborock.0 2024-01-18 05:39:42.288 debug Length of message queue: 1 roborock.0 2024-01-18 05:39:42.246 debug Length of message queue: 1 roborock.0 2024-01-18 05:39:42.153 debug Length of message queue: 0 roborock.0 2024-01-18 05:39:42.116 debug Length of message queue: 1 roborock.0 2024-01-18 05:39:42.116 debug Not clearing messageQueue. null - 64911 roborock.0 2024-01-18 05:39:42.116 debug dps debug: {"id":3,"result":["ok"]} roborock.0 2024-01-18 05:39:42.079 debug Length of message queue: 1 roborock.0 2024-01-18 05:39:41.902 debug getParameter for 5umEnoJEB0hmM5UmYlkumw: get_room_mapping roborock.0 2024-01-18 05:39:41.900 debug Length of message queue: 0 roborock.0 2024-01-18 05:39:41.827 debug get_status: {"msg_ver":2,"msg_seq":191,"state":8,"battery":100,"clean_time":82,"clean_area":2185000,"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":1,"map_status":3,"is_locating":0,"lock_status":0} roborock.0 2024-01-18 05:39:41.827 debug Length of message queue: 0 roborock.0 2024-01-18 05:39:41.824 debug getParameter for 5umEnoJEB0hmM5UmYlkumw: get_multi_maps_list roborock.0 2024-01-18 05:39:41.823 debug Length of message queue: 1 roborock.0 2024-01-18 05:39:41.756 debug Firmware features request for 5umEnoJEB0hmM5UmYlkumw roborock.0 2024-01-18 05:39:41.726 debug System type: go2rtc_linux_amd64 roborock.0 2024-01-18 05:39:41.726 debug platform: linux roborock.0 2024-01-18 05:39:41.726 debug arch: x64 roborock.0 2024-01-18 05:39:41.725 debug Processing scene roborock.0 2024-01-18 05:39:41.725 debug Update map roborock.0 2024-01-18 05:39:41.724 debug getParameter for 5umEnoJEB0hmM5UmYlkumw: get_status roborock.0 2024-01-18 05:39:41.724 debug Latest data requested roborock.0 2024-01-18 05:39:41.724 debug getParameter for 5umEnoJEB0hmM5UmYlkumw: get_fw_features roborock.0 2024-01-18 05:39:41.723 debug 5umEnoJEB0hmM5UmYlkumw online. Starting mainUpdateInterval. roborock.0 2024-01-18 05:37:41.390 debug MQTT connection connected {"cmd":"connack","retain":false,"qos":0,"dup":false,"length":2,"topic":null,"payload":null,"sessionPresent":false,"returnCode":0}. roborock.0 2024-01-18 05:37:41.307 debug tcp client for 5umEnoJEB0hmM5UmYlkumw connected roborock.0 2024-01-18 05:37:40.939 debug Robot key: roborock.vacuum.a08 roborock.0 2024-01-18 05:37:40.939 debug RoomIDs debug: {"16510226":"Studio"} roborock.0 2024-01-18 05:37:40.938 info MQTT initialized roborock.0 2024-01-18 05:37:40.909 debug localDevices: {"5umEnoJEB0hmM5UmYlkumw":"192.168.1.15"} roborock.0 2024-01-18 05:37:33.776 info Starting adapter. This might take a few minutes depending on your setup. Please wait. roborock.0 2024-01-18 05:37:33.764 info starting. Version 0.5.1 (non-npm: copystring/ioBroker.roborock#dev) in /opt/iobroker/node_modules/iobroker.roborock, node: v18.19.0, js-controller: 5.0.17 roborock.0 2024-01-18 05:37:31.533 debug Plugin sentry Initialize Plugin (enabled=true)das komplette log: iobroker.current.log.html
-
Ich habe eine kleine Änderung in die dev geladen. Wer mag, kann das testen.
-
@copystring immerhin schon was...
roborock.0 2024-01-19 07:37:59.872 warn Failed to map rooms. You need to name your rooms via the mobile app on your phone. roborock.0 2024-01-19 07:36:59.844 warn Failed to map rooms. You need to name your rooms via the mobile app on your phone. roborock.0 2024-01-19 07:35:59.878 warn Failed to map rooms. You need to name your rooms via the mobile app on your phone. roborock.0 2024-01-19 07:34:59.896 warn Failed to map rooms. You need to name your rooms via the mobile app on your phone. roborock.0 2024-01-19 07:34:59.608 warn MQTT connection reconnect. roborock.0 2024-01-19 07:34:59.608 warn MQTT connection close. roborock.0 2024-01-19 07:34:59.583 warn Reconnecting mqtt client! roborock.0 2024-01-19 07:34:00.009 warn Failed to map rooms. You need to name your rooms via the mobile app on your phone. roborock.0 2024-01-19 07:32:59.919 warn Failed to map rooms. You need to name your rooms via the mobile app on your phone. roborock.0 2024-01-19 07:31:59.787 warn Failed to map rooms. You need to name your rooms via the mobile app on your phone.also nach einer stunde nur ein reconnect.
-
@da_woody Ein reconnect in der Stunde ist normal. Beziehungsweise das war vorher alle drei Stunden. Müsste ich dann mal wieder zurückstellen.
-
Die neue dev verbindet sich nun wieder wie gewohnt alle drei Stunden neu.
-
@copystring jau, war schlecht ausgedrückt. Klar, daß da hin und wieder ein reconnect kommt.
Werd später die neue dev draufklatschen.
Stört nur mehr das dauernde "failed to map"
Ich hab für den Robby halt nur einen Raum. Stiegen fahren kann er ja noch nicht...
-
Mooin
Also JETZT nochmal die /dev installieren und dann sollte es normal laufen ??
-
@tritanium ja
-
@copystring Sooooooo
grade mal die /dev neu installiert.... Adapter startet...
Dann warten wir mal ab ....
