Neuer Adapter für Roborock-Staubsauger

[da_Woody]

@copystring zo, mal den typen losgejagt. update der karte klappt mal!
durch die neue struktur gewuselt.
wie kann ich goto fixieren? im xiaomi hatte ich das mal, irgendwann dann nicht mehr... (ich glaub, ich hab das damals in den objekten eingetragen)
wie kann ich roborock.0.Devices.5umEnoJEB0hmM5UmYlkumw.deviceStatus.error_code auswerten, damit ich nur den error(8) (hängen geblieben) anzeigen kann?

meine kleinen probleme in iQontrol:
mir ist die map zu klein. witziger weise ist die roborock.0.Devices.5umEnoJEB0hmM5UmYlkumw.map.mapBase64Truncated gößer als die roborock.0.Devices.5umEnoJEB0hmM5UmYlkumw.map.mapBase64
klappt dafür aber in FF und chrome ohne scrolleisten. bewusst mal den background eingeblendet:

verkleinern kann ich.

[copystring]

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

wie kann ich goto fixieren? im xiaomi hatte ich das mal, irgendwann dann nicht mehr... (ich glaub, ich hab das damals in den objekten eingetragen)

Was meinst du damit?

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

wie kann ich roborock.0.Devices.5umEnoJEB0hmM5UmYlkumw.deviceStatus.error_code auswerten, damit ich nur den error(8) (hängen geblieben) anzeigen kann?

Dafür müsstest du dir ein Script schreiben.

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

witziger weise ist die roborock.0.Devices.5umEnoJEB0hmM5UmYlkumw.map.mapBase64Truncated gößer als die

Natürlich, weil die alle Ränder entfernt sind.

[tritanium]

Also ich habe keine Ahnung mehr welche Version ich probieren soll....

Mit der stable 0.4.4, funktioniert der Adapter zwar, schmeisst aber etliche Fehler:

Spoiler

oborock.0
   2024-01-14 20:57:18.551	warn	Failed to execute get_network_info on robot 4Si5s3DNcsl0ATAl8e5UdI Error: Request with id 5681 timed out after 10 seconds for response.102
roborock.0
   2024-01-14 20:57:15.011	warn	Failed to execute get_consumable on robot 5kt1jy0ATJPgji5k0hJAZg Error: Request with id 7884 timed out after 10 seconds for response.102
roborock.0
   2024-01-14 20:57:13.418	warn	Failed to execute get_network_info on robot 4Si5s3DNcsl0ATAl8e5UdI Error: Request with id 2698 timed out after 10 seconds for response.102
roborock.0
   2024-01-14 20:57:10.253	warn	Failed to execute get_network_info on robot 5kt1jy0ATJPgji5k0hJAZg Error: Request with id 5909 timed out after 10 seconds for response.102
roborock.0
   2024-01-14 20:57:08.128	info	State value to set for "roborock.0.Devices.4Si5s3DNcsl0ATAl8e5UdI.deviceStatus.last_clean_t" has to be type "number" but received type "string"
roborock.0
   2024-01-14 20:57:08.052	error	Unsported attribute: kct of get_status with value 0. Please contact the dev to add the newly found attribute of your robot.
roborock.0
   2024-01-14 20:57:03.410	warn	Failed to execute get_consumable on robot 4Si5s3DNcsl0ATAl8e5UdI Error: Request with id 9251 timed out after 10 seconds for response.102
roborock.0
   2024-01-14 20:57:00.246	warn	Failed to execute get_consumable on robot 5kt1jy0ATJPgji5k0hJAZg Error: Request with id 1082 timed out after 10 seconds for response.102
roborock.0
   2024-01-14 20:56:58.439	warn	Failed to execute get_network_info on robot 4Si5s3DNcsl0ATAl8e5UdI Error: Request with id 4253 timed out after 10 seconds for response.102
roborock.0
   2024-01-14 20:56:55.018	warn	Failed to execute get_network_info on robot 5kt1jy0ATJPgji5k0hJAZg Error: Request with id 7890 timed out after 10 seconds for response.102
knx.0
   2024-01-14 20:56:54.253	info	State value to set for "knx.0.Licht.Erdgeschoss.LEDSpots_Küche_HSV_Dimmwert" has to be one of type "string", "number", "boolean" but received type "object"
roborock.0
   2024-01-14 20:56:53.121	info	State value to set for "roborock.0.Devices.4Si5s3DNcsl0ATAl8e5UdI.deviceStatus.last_clean_t" has to be type "number" but received type "string"
roborock.0
   2024-01-14 20:56:53.045	error	Unsported attribute: kct of get_status with value 0. Please contact the dev to add the newly found attribute of your robot.
roborock.0
   2024-01-14 20:56:48.430	warn	Failed to execute get_consumable on robot 4Si5s3DNcsl0ATAl8e5UdI Error: Request with id 2630 timed out after 10 seconds for response.102
roborock.0
   2024-01-14 20:56:45.009	warn	Failed to execute get_consumable on robot 5kt1jy0ATJPgji5k0hJAZg Error: Request with id 8986 timed out after 10 seconds for response.102
roborock.0
   2024-01-14 20:56:40.229	warn	Failed to execute get_network_info on robot 5kt1jy0ATJPgji5k0hJAZg Error: Request with id 6033 timed out after 10 seconds for response.102
roborock.0
   2024-01-14 20:56:38.114	info	State value to set for "roborock.0.Devices.4Si5s3DNcsl0ATAl8e5UdI.deviceStatus.last_clean_t" has to be type "number" but received type "string"
roborock.0
   2024-01-14 20:56:38.047	error	Unsported attribute: kct of get_status with value 0. Please contact the dev to add the newly found attribute of your robot.
roborock.0
   2024-01-14 20:56:33.533	warn	Failed to execute get_network_info on robot 4Si5s3DNcsl0ATAl8e5UdI Error: Request with id 9299 timed out after 10 seconds for response.102
roborock.0
   2024-01-14 20:56:30.222	warn	Failed to execute get_consumable on robot 5kt1jy0ATJPgji5k0hJAZg Error: Request with id 5724 timed out after 10 seconds for response.102
roborock.0
   2024-01-14 20:56:28.365	warn	Failed to execute get_network_info on robot 4Si5s3DNcsl0ATAl8e5UdI Error: Request with id 9251 timed out after 10 seconds for response.102
roborock.0
   2024-01-14 20:56:25.029	warn	Failed to execute get_network_info on robot 5kt1jy0ATJPgji5k0hJAZg Error: Request with id 8772 timed out after 10 seconds for response.102
roborock.0
   2024-01-14 20:56:23.111	info	State value to set for "roborock.0.Devices.4Si5s3DNcsl0ATAl8e5UdI.deviceStatus.last_clean_t" has to be type "number" but received type "string"
roborock.0
   2024-01-14 20:56:23.028	error	Unsported attribute: kct of get_status with value 0. Please contact the dev to add the newly found attribute of your robot.
roborock.0
   2024-01-14 20:56:18.358	warn	Failed to execute get_consumable on robot 4Si5s3DNcsl0ATAl8e5UdI Error: Request with id 1989 timed out after 10 seconds for response.102
roborock.0
   2024-01-14 20:56:15.020	warn	Failed to execute get_consumable on robot 5kt1jy0ATJPgji5k0hJAZg Error: Request with id 7488 timed out after 10 seconds for response.102
roborock.0
   2024-01-14 20:56:13.505	warn	Failed to execute get_network_info on robot 4Si5s3DNcsl0ATAl8e5UdI Error: Request with id 7258 timed out after 10 seconds for response.102
roborock.0
   2024-01-14 20:56:10.254	warn	Failed to execute get_network_info on robot 5kt1jy0ATJPgji5k0hJAZg Error: Request with id 1712 timed out after 10 seconds for response.102
roborock.0
   2024-01-14 20:56:08.136	info	State value to set for "roborock.0.Devices.4Si5s3DNcsl0ATAl8e5UdI.deviceStatus.last_clean_t" has to be type "number" but received type "string"
roborock.0
   2024-01-14 20:56:08.064	error	Unsported attribute: kct of get_status with value 0. Please contact the dev to add the newly found attribute of your robot.
roborock.0
   2024-01-14 20:56:03.496	warn	Failed to execute get_consumable on robot 4Si5s3DNcsl0ATAl8e5UdI Error: Request with id 1005 timed out after 10 seconds for response.102
roborock.0
   2024-01-14 20:56:00.246	warn	Failed to execute get_consumable on robot 5kt1jy0ATJPgji5k0hJAZg Error: Request with id 8210 timed out after 10 seconds for response.102
roborock.0
   2024-01-14 20:55:55.022	warn	Failed to execute get_network_info on robot 5kt1jy0ATJPgji5k0hJAZg Error: Request with id 4104 timed out after 10 seconds for response.102
roborock.0
   2024-01-14 20:55:53.106	info	State value to set for "roborock.0.Devices.4Si5s3DNcsl0ATAl8e5UdI.deviceStatus.last_clean_t" has to be type "number" but received type "string"
roborock.0
   2024-01-14 20:55:53.059	error	Unsported attribute: kct of get_status with value 0. Please contact the dev to add the newly found attribute of your robot.
roborock.0
   2024-01-14 20:55:48.441	warn	Failed to execute get_consumable on robot 4Si5s3DNcsl0ATAl8e5UdI Error: Request with id 3081 timed out after 10 seconds for response.102
roborock.0
   2024-01-14 20:55:45.013	warn	Failed to execute get_consumable on robot 5kt1jy0ATJPgji5k0hJAZg Error: Request with id 8080 timed out after 10 seconds for response.102
roborock.0
   2024-01-14 20:55:39.996	warn	Failed to execute get_network_info on robot 5kt1jy0ATJPgji5k0hJAZg Error: Request with id 4227 timed out after 10 seconds for response.102
roborock.0
   2024-01-14 20:55:38.152	info	State value to set for "roborock.0.Devices.4Si5s3DNcsl0ATAl8e5UdI.deviceStatus.last_clean_t" has to be type "number" but received type "string"
roborock.0
   2024-01-14 20:55:38.079	error	Unsported attribute: kct of get_status with value 0. Please contact the dev to add the newly found attribute of your robot.
roborock.0
   2024-01-14 20:55:29.987	warn	Failed to execute get_consumable on robot 5kt1jy0ATJPgji5k0hJAZg Error: Request with id 1750 timed out after 10 seconds for response.102
roborock.0
   2024-01-14 20:55:25.007	warn	Failed to execute get_network_info on robot 5kt1jy0ATJPgji5k0hJAZg Error: Request with id 9715 timed out after 10 seconds for response.102
roborock.0
   2024-01-14 20:55:23.116	info	State value to set for "roborock.0.Devices.4Si5s3DNcsl0ATAl8e5UdI.deviceStatus.last_clean_t" has to be type "number" but received type "string"
roborock.0
   2024-01-14 20:55:23.045	error	Unsported attribute: kct of get_status with value 0. Please contact the dev t

Die aktuelle /dev (vor 5 Minuten aktualisiert) schemisst auch nur noch Fehler raus und startet in einer loop neu...:

Spoiler

host.iobroker
   2024-01-14 20:41:44.145	info	Restart adapter system.adapter.roborock.0 because enabled
host.iobroker
   2024-01-14 20:41:44.145	info	instance system.adapter.roborock.0 terminated with code 0 (NO_ERROR)
host.iobroker
   2024-01-14 20:41:44.145	error	Caught by controller[7]: at TCP.<anonymous> (node:net:323:12)
host.iobroker
   2024-01-14 20:41:44.145	error	Caught by controller[7]: at Socket.emit (node:domain:489:12)
host.iobroker
   2024-01-14 20:41:44.145	error	Caught by controller[7]: at Socket.emit (node:events:514:28)
host.iobroker
   2024-01-14 20:41:44.145	error	Caught by controller[7]: at Object.onceWrapper (node:events:629:26)
host.iobroker
   2024-01-14 20:41:44.145	error	Caught by controller[7]: at Socket.<anonymous> (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:151:20)
host.iobroker
   2024-01-14 20:41:44.144	error	Caught by controller[7]: at close (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:184:25)
host.iobroker
   2024-01-14 20:41:44.144	error	Caught by controller[7]: Error: Connection is closed.
host.iobroker
   2024-01-14 20:41:44.144	error	Caught by controller[6]: 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:
host.iobroker
   2024-01-14 20:41:44.144	error	Caught by controller[5]: at TCP.<anonymous> (node:net:323:12)
host.iobroker
   2024-01-14 20:41:44.144	error	Caught by controller[5]: at Socket.emit (node:domain:489:12)
host.iobroker
   2024-01-14 20:41:44.144	error	Caught by controller[5]: at Socket.emit (node:events:514:28)
host.iobroker
   2024-01-14 20:41:44.144	error	Caught by controller[5]: at Object.onceWrapper (node:events:629:26)
host.iobroker
   2024-01-14 20:41:44.144	error	Caught by controller[5]: at Socket.<anonymous> (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:151:20)
host.iobroker
   2024-01-14 20:41:44.144	error	Caught by controller[5]: at close (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:184:25)
host.iobroker
   2024-01-14 20:41:44.143	error	Caught by controller[5]: Error: Connection is closed.
host.iobroker
   2024-01-14 20:41:44.143	error	Caught by controller[4]: 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:
host.iobroker
   2024-01-14 20:41:44.143	error	Caught by controller[3]: at TCP.<anonymous> (node:net:323:12)
host.iobroker
   2024-01-14 20:41:44.143	error	Caught by controller[3]: at Socket.emit (node:domain:489:12)
host.iobroker
   2024-01-14 20:41:44.143	error	Caught by controller[3]: at Socket.emit (node:events:514:28)
host.iobroker
   2024-01-14 20:41:44.143	error	Caught by controller[3]: at Object.onceWrapper (node:events:629:26)
host.iobroker
   2024-01-14 20:41:44.143	error	Caught by controller[3]: at Socket.<anonymous> (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:151:20)
host.iobroker
   2024-01-14 20:41:44.143	error	Caught by controller[3]: at close (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:184:25)
host.iobroker
   2024-01-14 20:41:44.143	error	Caught by controller[3]: Error: Connection is closed.
host.iobroker
   2024-01-14 20:41:44.142	error	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:
host.iobroker
   2024-01-14 20:41:44.142	error	Caught by controller[1]: at TCP.<anonymous> (node:net:323:12)
host.iobroker
   2024-01-14 20:41:44.142	error	Caught by controller[1]: at Socket.emit (node:domain:489:12)
host.iobroker
   2024-01-14 20:41:44.142	error	Caught by controller[1]: at Socket.emit (node:events:514:28)
host.iobroker
   2024-01-14 20:41:44.142	error	Caught by controller[1]: at Object.onceWrapper (node:events:629:26)
host.iobroker
   2024-01-14 20:41:44.142	error	Caught by controller[1]: at Socket.<anonymous> (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:151:20)
host.iobroker
   2024-01-14 20:41:44.142	error	Caught by controller[1]: at close (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:184:25)
host.iobroker
   2024-01-14 20:41:44.142	error	Caught by controller[1]: Error: Connection is closed.
host.iobroker
   2024-01-14 20:41:44.141	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
   2024-01-14 20:41:43.853	info	terminating
roborock.0
   2024-01-14 20:41:43.393	info	Terminated (NO_ERROR): Without reason
roborock.0
   2024-01-14 20:41:43.391	info	terminating
roborock.0
   2024-01-14 20:41:43.339	warn	Restart initiated
roborock.0
   2024-01-14 20:41:43.243	warn	MQTT connection close.
roborock.0
   2024-01-14 20:41:43.121	warn	MQTT connection reconnect.
roborock.0
   2024-01-14 20:41:42.121	warn	MQTT connection close.
roborock.0
   2024-01-14 20:41:41.979	warn	MQTT connection reconnect.
roborock.0
   2024-01-14 20:41:40.979	warn	MQTT connection close.
roborock.0
   2024-01-14 20:41:40.821	warn	MQTT connection reconnect.
roborock.0
   2024-01-14 20:41:39.821	warn	MQTT connection close.
roborock.0
   2024-01-14 20:41:39.679	warn	MQTT connection reconnect.
roborock.0
   2024-01-14 20:41:38.679	warn	MQTT connection close.
roborock.0
   2024-01-14 20:41:38.568	warn	MQTT connection reconnect.
roborock.0
   2024-01-14 20:41:37.567	warn	MQTT connection close.
roborock.0
   2024-01-14 20:41:37.451	warn	MQTT connection reconnect.
roborock.0
   2024-01-14 20:41:36.451	warn	MQTT connection close.
roborock.0
   2024-01-14 20:41:36.347	warn	MQTT connection reconnect.
roborock.0
   2024-01-14 20:41:35.347	warn	MQTT connection close.
roborock.0
   2024-01-14 20:41:35.226	warn	MQTT connection reconnect.
roborock.0
   2024-01-14 20:41:34.225	warn	MQTT connection close.
roborock.0
   2024-01-14 20:41:34.086	warn	MQTT connection reconnect.
roborock.0
   2024-01-14 20:41:33.086	warn	MQTT connection close.
roborock.0
   2024-01-14 20:41:32.975	warn	MQTT connection reconnect.
roborock.0
   2024-01-14 20:41:31.974	warn	MQTT connection close.
roborock.0
   2024-01-14 20:41:31.859	warn	MQTT connection reconnect.
roborock.0
   2024-01-14 20:41:30.858	warn	MQTT connection close.
roborock.0
   2024-01-14 20:41:30.730	warn	MQTT connection reconnect.
roborock.0
   2024-01-14 20:41:29.730	warn	MQTT connection close.
roborock.0
   2024-01-14 20:41:29.617	warn	MQTT connection reconnect.
roborock.0
   2024-01-14 20:41:28.616	warn	MQTT connection close.
roborock.0
   2024-01-14 20:41:28.447	warn	MQTT connection reconnect.
roborock.0
   2024-01-14 20:41:27.448	warn	MQTT connection close.
roborock.0
   2024-01-14 20:41:27.319	warn	MQTT connection reconnect.
roborock.0
   2024-01-14 20:41:26.318	warn	MQTT connection close.
roborock.0
   2024-01-14 20:41:26.192	warn	MQTT connection reconnect.
roborock.0
   2024-01-14 20:41:25.192	warn	MQTT connection close.
roborock.0
   2024-01-14 20:41:25.072	warn	MQTT connection reconnect.
roborock.0
   2024-01-14 20:41:24.072	warn	MQTT connection close.
roborock.0
   2024-01-14 20:41:23.959	warn	MQTT connection reconnect.
roborock.0
   2024-01-14 20:41:22.959	warn	MQTT connection close.
roborock.0
   2024-01-14 20:41:22.833	warn	MQTT connection reconnect.
roborock.0
   2024-01-14 20:41:21.833	warn	MQTT connection close.
roborock.0
   2024-01-14 20:41:21.706	warn	MQTT connection reconnect.
roborock.0
   2024-01-14 20:41:20.706	warn	MQTT connection close.
roborock.0
   2024-01-14 20:41:20.595	warn	MQTT connection reconnect.
roborock.0
   2024-01-14 20:41:19.595	warn	MQTT connection close.
roborock.0
   2024-01-14 20:41:19.482	warn	MQTT connection reconnect.
roborock.0
   2024-01-14 20:41:18.482	warn	MQTT connection close.
roborock.0
   2024-01-14 20:41:18.341	warn	MQTT connection reconnect.
roborock.0
   2024-01-14 20:41:17.341	warn	MQTT connection close.
roborock.0
   2024-01-14 20:41:17.207	warn	MQTT connection reconnect.
roborock.0
   2024-01-14 20:41:16.207	warn	MQTT connection close.
roborock.0
   2024-01-14 20:41:16.087	warn	MQTT connection reconnect.
roborock.0
   2024-01-14 20:41:15.086	warn	MQTT connection close.
roborock.0
   2024-01-14 20:41:14.962	warn	MQTT connection reconnect.
roborock.0
   2024-01-14 20:41:13.962	warn	MQTT connection close.
roborock.0
   2024-01-14 20:41:13.338	info	MQTT initialized
roborock.0
   2024-01-14 20:41:07.232	info	Starting adapter. This might take a few minutes depending on your setup. Please wait.
roborock.0
   2024-01-14 20:41:07.178	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
host.iobroker
   2024-01-14 20:41:02.286	info	instance system.adapter.roborock.0 started with pid 1519525
host.iobroker
   2024-01-14 20:41:01.775	info	"system.adapter.roborock.0" enabled

Aufgrund dessen habe ich den Adapter erst mal "deaktivert". Wie macht ihr das?

Funktionieren bei euch die Roboter? Ich habe 2 dran (Q7 Max+ & Q Revo).

Danke für eure Hilfe

[copystring]

@tritanium lösch Mal dein UserData und starte den Adapter neu.

[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

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

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

Nur noch die hier:

Spoiler

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

Spoiler

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

Spoiler

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