UPDATE 31.10.: Amazon Alexa - ioBroker Skill läuft aus ?

[David G.]

@copystring

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

Wenn etwas neues kommt melde ich mich.

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

[copystring]

@david-g said in Roborock Adapter tester gesucht:

@copystring

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

Inwiefern?

[David G.]

@copystring

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

Evtl welche von denen?

water_shortage_status

water_box_status

water_box_carriage_status

dust_collection_status

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

EDIT

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

EDIT2

Leider kein c&p möglich

[Dimi]

@copystring

Mir sind 2 Dinge aufgefallen in der Version 0.1.6.

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

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

Falls du Logs brauchst gib bescheid.

[copystring]

@dimi said in Roborock Adapter tester gesucht:

@copystring

Mir sind 2 Dinge aufgefallen in der Version 0.1.6.

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

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

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

Falls du Logs brauchst gib bescheid.

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

[Dimi]

@copystring

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

[copystring]

@dimi said in Roborock Adapter tester gesucht:

@copystring

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

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

[copystring]

@copystring said in Roborock Adapter tester gesucht:

@dimi said in Roborock Adapter tester gesucht:

@copystring

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

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

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

[DonToben]

@copystring

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

Hier das Log:

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

[bongsao]

host.HomsServer
2023-03-17 16:27:42.452	error	instance system.adapter.roborock.0 terminated with code 6 (UNCAUGHT_EXCEPTION)
host.HomsServer
2023-03-17 16:27:42.452	error	Caught by controller[1]: at /opt/iobroker/node_modules/iobroker.roborock/lib/vacuum.js:376:139
host.HomsServer
2023-03-17 16:27:42.451	error	Caught by controller[1]: TypeError: Cannot read properties of undefined (reading 'toString')
host.HomsServer
2023-03-17 16:27:42.451	error	Caught by controller[0]: This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason:

roborock.0
2023-03-17 16:27:41.878	error	Cannot read properties of undefined (reading 'toString')

roborock.0
2023-03-17 16:27:41.878	error	TypeError: Cannot read properties of undefined (reading 'toString') at /opt/iobroker/node_modules/iobroker.roborock/lib/vacuum.js:376:139

roborock.0
2023-03-17 16:27:41.876	error	unhandled promise rejection: Cannot read properties of undefined (reading 'toString')

roborock.0
2023-03-17 16:27:41.875	error	Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().

mit Version 0.1.6

MOD EDIT: LOG IN CODE TAGS </> GESETZT

[Dimi]

@copystring sagte in Roborock Adapter tester gesucht:

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

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

[Menfis]

@copystring

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

DebugFileRoborock.txt

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

Gruß,
Menfis

[copystring]

@menfis said in Roborock Adapter tester gesucht:

@copystring

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

DebugFileRoborock.txt

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

Gruß,
Menfis

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

[Menfis]

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

[copystring]

@menfis said in Roborock Adapter tester gesucht:

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

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

[Menfis]

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

[David G.]

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

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

[copystring]

@david-g said in Roborock Adapter tester gesucht:

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

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

Welche Roboter hast du? Wenn es verfügbar wäre, dann würde es ist HomeData stehen. Wäre das so, dann könnte ich den Adapter darauf anpassen.

[David G.]

@copystring

In HomeData finde ich nichts.
Ist ein Roborock S7 MaxV.

{"id":3997987,"name":"xxxx","lon":null,"lat":null,"geoName":null,"products":[{"id":"42yfoQm5eOY3gARZw6xgU","name":"Roborock S7 MaxV","code":"a27","model":"roborock.vacuum.a27","iconUrl":null,"attribute":null,"capability":0,"category":"robot.vacuum.cleaner","schema":[{"id":"101","name":"rpc_request","code":"rpc_request","mode":"rw","type":"RAW","property":null,"desc":null},{"id":"102","name":"rpc_response","code":"rpc_response","mode":"rw","type":"RAW","property":null,"desc":null},{"id":"120","name":"错误代码","code":"error_code","mode":"ro","type":"ENUM","property":"{\"range\": []}","desc":null},{"id":"121","name":"设备状态","code":"state","mode":"ro","type":"ENUM","property":"{\"range\": []}","desc":null},{"id":"122","name":"设备电量","code":"battery","mode":"ro","type":"ENUM","property":"{\"range\": []}","desc":null},{"id":"123","name":"清扫模式","code":"fan_power","mode":"rw","type":"ENUM","property":"{\"range\": []}","desc":null},{"id":"124","name":"拖地模式","code":"water_box_mode","mode":"rw","type":"ENUM","property":"{\"range\": []}","desc":null},{"id":"125","name":"主刷寿命","code":"main_brush_life","mode":"rw","type":"VALUE","property":"{\"max\": 100, \"min\": 0, \"step\": 1, \"unit\": null, \"scale\": 1}","desc":null},{"id":"126","name":"边刷寿命","code":"side_brush_life","mode":"rw","type":"VALUE","property":"{\"max\": 100, \"min\": 0, \"step\": 1, \"unit\": null, \"scale\": 1}","desc":null},{"id":"127","name":"滤网寿命","code":"filter_life","mode":"rw","type":"VALUE","property":"{\"max\": 100, \"min\": 0, \"step\": 1, \"unit\": null, \"scale\": 1}","desc":null},{"id":"128","name":"额外状态","code":"additional_props","mode":"ro","type":"RAW","property":null,"desc":null},{"id":"130","name":"完成事件","code":"task_complete","mode":"ro","type":"RAW","property":null,"desc":null},{"id":"131","name":"电量不足任务取消","code":"task_cancel_low_power","mode":"ro","type":"RAW","property":null,"desc":null},{"id":"132","name":"运动中任务取消","code":"task_cancel_in_motion","mode":"ro","type":"RAW","property":null,"desc":null},{"id":"133","name":"充电状态","code":"charge_status","mode":"ro","type":"RAW","property":null,"desc":null},{"id":"134","name":"烘干状态","code":"drying_status","mode":"ro","type":"RAW","property":null,"desc":null}]}],"devices":[{"duid":"7UreppMhwYr4WlSbCtcsno","name":"Roborock S7 MaxV","attribute":null,"activeTime":1676794696,"localKey":"XmIxKeJ6ysQxGuf0","runtimeEnv":null,"timeZoneId":"Europe/Berlin","iconUrl":"","productId":"42yfoQm5eOY3gARZw6xgU","lon":null,"lat":null,"share":false,"shareTime":null,"online":true,"fv":"02.57.26","pv":"1.0","roomId":10800654,"tuyaUuid":null,"tuyaMigrated":false,"extra":"{\"RRMonitorPrivacyVersion\": \"1\"}","sn":"R21ETS22901883","featureSet":"2234201184108543","newFeatureSet":"0000000000002041","deviceStatus":{"120":0,"121":8,"122":100,"123":102,"124":202,"125":87,"126":80,"127":73,"128":0,"133":1},"silentOtaSwitch":false}],"receivedDevices":[],"rooms":[{"id":10931661,"name":"Eingang unten"},{"id":10803513,"name":"Wohnzimmer"},{"id":10803502,"name":"Esszimmer"},{"id":10803485,"name":"Küche"},{"id":10803465,"name":"Flur oben"},{"id":10803462,"name":"Badezimmer oben"},{"id":10800662,"name":"Badezimmer unten"},{"id":10800659,"name":"Flur unten"},{"id":10800654,"name":"HWR"},{"id":10800645,"name":"Flur"},{"id":10800637,"name":"Badezimmer"},{"id":10800627,"name":"Kinderzimmer 2"},{"id":10800608,"name":"Kinderzimmer 1"},{"id":10800591,"name":"Schlafzimmer"}]}

[copystring]

@menfis said in Roborock Adapter tester gesucht:

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

Sehr merkwürdig, weil der Befehl sauber abgeschickt wurde. Leider kommt aber ein Fehler zurück.
dps debug: {"id":71,"error":{"code":-10005,"message":"data for segments is invalid"}}
Ich weiß aber nicht, warum das so ist, weil app_segment_clean with roomIDs: {"segments":[17,23],"repeat":1} result: ok sauber durchläuft. Ich habe z. B. auch einen Raum mit Umlaut (Küche) und das läuft sauber durch. Hast du mal versucht, alle Objekte unter Rooms zu löschen? Noch besser wäre es, wenn du den Adapter ein mal löschst und neu installierst. Ich wüsste sonst nicht wirklich, woran es liegen könnte.