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

[tritanium]

@copystring

Okay, geht klar.... spiele eben die /dev neu ein....

[tritanium]

@copystring

Habe extra gewartet :-)

1h ist rum und et voila:

Spoiler

2024-01-18 01:22:32.127 - info: jarvis.0 (20074) Found Backups for settings.
2024-01-18 01:22:32.129 - info: jarvis.0 (20074) Found Backups for scripts.
2024-01-18 01:22:32.130 - info: jarvis.0 (20074) Found Backups for styles.
2024-01-18 01:22:32.164 - info: jarvis.0 (20074) Connection: WebSocket opened on port 8400 using http...
2024-01-18 01:22:32.168 - info: jarvis.0 (20074) Found Backups for widgets.
2024-01-18 01:22:32.191 - info: jarvis.0 (20074) Found Backups for devices.
2024-01-18 01:22:34.905 - info: jarvis.0 (20074) Client with IP 192.168.50.49 connected.
2024-01-18 01:22:41.406 - info: jarvis.0 (20074) Client with IP 192.168.50.49 disconnected.
2024-01-18 01:22:42.255 - info: jarvis.0 (20074) Client with IP 192.168.50.49 connected.
2024-01-18 01:22:51.308 - info: jarvis.0 (20074) Client with IP 192.168.50.49 disconnected.
2024-01-18 01:22:52.201 - info: jarvis.0 (20074) Client with IP 192.168.50.49 connected.
2024-01-18 01:24:27.498 - info: linux-control.0 (1880) getting data from ioBroker (192.168.50.5:22)
2024-01-18 01:24:36.612 - info: linux-control.0 (1880) successful received data from ioBroker (192.168.50.5:22)
2024-01-18 01:25:58.800 - warn: roborock.0 (6634) Reconnecting mqtt client!
2024-01-18 01:25:58.840 - warn: roborock.0 (6634) MQTT connection close.
2024-01-18 01:25:58.842 - warn: roborock.0 (6634) MQTT connection reconnect.
2024-01-18 01:25:58.996 - warn: roborock.0 (6634) MQTT connection close.
2024-01-18 01:25:59.996 - warn: roborock.0 (6634) MQTT connection reconnect.
2024-01-18 01:26:00.102 - warn: roborock.0 (6634) MQTT connection close.
2024-01-18 01:26:01.102 - warn: roborock.0 (6634) MQTT connection reconnect.
2024-01-18 01:26:01.203 - warn: roborock.0 (6634) MQTT connection close.
2024-01-18 01:26:02.203 - warn: roborock.0 (6634) MQTT connection reconnect.
2024-01-18 01:26:02.314 - warn: roborock.0 (6634) MQTT connection close.
2024-01-18 01:26:03.315 - warn: roborock.0 (6634) MQTT connection reconnect.
2024-01-18 01:26:03.418 - warn: roborock.0 (6634) MQTT connection close.
2024-01-18 01:26:04.419 - warn: roborock.0 (6634) MQTT connection reconnect.
2024-01-18 01:26:04.522 - warn: roborock.0 (6634) MQTT connection close.
2024-01-18 01:26:05.522 - warn: roborock.0 (6634) MQTT connection reconnect.
2024-01-18 01:26:05.627 - warn: roborock.0 (6634) MQTT connection close.

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	terminating

So als Info noch :-) und nun Gute N8

[da_Woody]

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

[da_Woody]

@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

[copystring]

Ich habe eine kleine Änderung in die dev geladen. Wer mag, kann das testen.

[da_Woody]

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

[copystring]

@da_woody Ein reconnect in der Stunde ist normal. Beziehungsweise das war vorher alle drei Stunden. Müsste ich dann mal wieder zurückstellen.

[copystring]

Die neue dev verbindet sich nun wieder wie gewohnt alle drei Stunden neu.

[da_Woody]

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

[tritanium]

Mooin :-D

Also JETZT nochmal die /dev installieren und dann sollte es normal laufen ??

[copystring]

@tritanium ja

[tritanium]

@copystring Sooooooo :-)

grade mal die /dev neu installiert.... Adapter startet...

Spoiler

roborock.0
   2024-01-19 12:12:02.507	info	Starting adapter finished. Lets go!!!!!!!
linux-control.0
   2024-01-19 12:10:03.589	info	successful received data from ioBroker (192.168.50.5:22)
linux-control.0
   2024-01-19 12:09:54.047	info	getting data from ioBroker (192.168.50.5:22)
roborock.0
   2024-01-19 12:08:15.080	warn	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
roborock.0
   2024-01-19 12:05:26.337	info	MQTT initialized
roborock.0
   2024-01-19 12:05:20.027	info	Starting adapter. This might take a few minutes depending on your setup. Please wait.
roborock.0
   2024-01-19 12:05:19.999	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

Dann warten wir mal ab ....

[B0ck]

Hallo zusammen,

kann mir jemand erklären, wo ich den Datenpunkt zum entleeren des Staubbehälters finde? Ich habe mir den Objektbaum nun schon mehrfach angeschaut, finden kann ich den Datenpunkt allerdings nicht. Ich habe einen Roborock S7 Plus (mit Absaugstation)

Danke ung Gruß

[tritanium]

@copystring

Hey Hey, 15:05 ... einmal disconnect, einmal reconnect... Zack fertig ... mehr nicht!

-> Daumen hoch :-D

Wenn das so bleibt... dann nix mehr ändern...

@jahnbes ...kannst dann auch testen ... ich habe die /dev um kurz vor 12 installiert und seit dem funktionierts wunderbar...

lg Micha

[jahnbes]

@tritanium
Hoffnung!
13:31 Uhr neueste dev installiert und Instanz restartet
und nach über drei Stunden nun das:

2024-01-19 16:35:34.352	info	script.js.Test.roborock_log_dp: # Robi -> Find me [commands.find_me] = true -> false
2024-01-19 16:35:33.888	info	script.js.Test.roborock_log_dp: # Robi -> Find me [commands.find_me] = false -> true
roborock.0 2024-01-19 16:33:22.367	warn	MQTT connection reconnect.
roborock.0 2024-01-19 16:33:22.366	warn	MQTT connection close.
roborock.0 2024-01-19 16:33:22.333	warn	Reconnecting mqtt client!

Es läuft wieder! Kein endloses close-reconnect mehr. Klasse! :+1:
Und trotzdem, wenn ändern notwendig ist, immer ran, immer weiterentwickeln!
Goethe, Faust: "Und sollt je ich mich auf ein Faulbett legen, sei es gleich um mich gescheh'n."
Gruß, jahnbes.
(Ich bin gespannt.)

[hgerstung]

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

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!

Hat keiner ne Idee? Schade, das wäre ne super praktische Funktion für mich ...

VG
Heiko

[itwegner72]

@hgerstung
Nimm den Zeitplan aus der App doch raus und lege einen in ioBroker an. Den könntest du den auch über einen eigenen Datenpunkt und sogar einen dementsprechenden Taster ein und ausschalten.

[michael 1975]

@hgerstung Ich habe einen Datrenpunkt Besuch den Schalte ich an wenn besuch kommt damit werden manche Aktion nicht oder anders ausgeführt, der Robby läuft dann auch nicht allerdings starte ich meinen nicht nach zeitplan sondern wenn ich Abends Alexa Gute Nacht sage dann startet er nach einer Stunde.

[da_Woody]

@jahnbes auch bei aller freude, bitte log in setzen... ;)

[jahnbes]

@da_woody
Wenn Du mir sagst was, wo und warum? Ich hab trotz Suche nichts gefunden.
Gruß jahnbes