Neuer Adapter für Roborock-Staubsauger

da_Woody

@elochso sagte in Neuer Adapter für Roborock-Staubsauger:

Wie kann ich auf die neue Version updaten.

wie immer, über latest.
sollte man halt wissen, was man tut...

elochso

@da_woody das problem ist das ich nicht weiß wie?

da_Woody

@elochso repository auf latest umstellen, updaten, wieder zurück, oder auch nicht.

elochso

@da_woody wenn ich das im Terminal über iobroker update mache zeigt er mir bei Roboroch noch den alten Adapter 0.6.17 an

da_Woody

@elochso warum terminal?

elochso

@da_woody danke dir muss noch mal rausfinden wie ich auf Beta umstelle, das hat mir aber schon super geholfen, DANKEEEEEE

wolfi913

@elochso sagte in Neuer Adapter für Roborock-Staubsauger:

@da_woody danke dir muss noch mal rausfinden wie ich auf Beta umstelle, das hat mir aber schon super geholfen, DANKEEEEEE

Geht auch so
Screenshot 2024-12-25 140906.png
und dann (sicherheitshalber)
Screenshot 2024-12-25 141008.png
Screenshot 2024-12-25 141048.png
noch einen Upload machen

elochso

@wolfi913 danke hat geklappt

elochso

Jetzt kommt immer folgender Fehler:
Failed to execute get_map_v1 on robot 1opZH9d8PAaIcMMhNO0u9u (roborock.vacuum.a51): Error: Failed to convert JavaScript value Undefined into rust type String at /opt/iobroker/node_modules/iobroker.roborock/lib/mapCreator.js:647:29 at Array.forEach (<anonymous>) at MapCreator.canvasMap (/opt/iobroker/node_modules/iobroker.roborock/lib/mapCreator.js:624:30) at vacuum.getMap (/opt/iobroker/node_modules/iobroker.roborock/lib/vacuum.js:84:46)

createch2

Hab eben erst den Adapter installiert.
Ich habe absichtlich keinerlei Kartenerzeugung angewählt, bekomme aber im Log File: "Failed to map rooms. You need to name your rooms via the mobile app on your phone."

Gibts da Abhilfe ausser in der Mobile App tätig zu werden ?

Adri525

Hallo zusammen,
ich habe den QRevo Slim und bekomme folgende Fehlermeldungen:

Unsupported attribute: kct of get_status with value 0. Please contact the dev to add the newly found attribute of your robot. Model: roborock.vacuum.a21

2025-01-05 16:25:22.073	warn	State "roborock.0.Devices.52nkyxg5GRqLBvhDnBr6nw.consumables.dust_collection_work_times" has no existing object, this might lead to an error in future versions

roborock.0
2025-01-05 16:25:22.070 warn State "roborock.0.Devices.52nkyxg5GRqLBvhDnBr6nw.consumables.sensor_dirty_time" has no existing object, this might lead to an error in future versions

roborock.0
2025-01-05 16:25:22.070 warn State "roborock.0.Devices.52nkyxg5GRqLBvhDnBr6nw.consumables.filter_element_work_time" has no existing object, this might lead to an error in future versions

roborock.0
2025-01-05 16:25:22.070 warn State "roborock.0.Devices.52nkyxg5GRqLBvhDnBr6nw.consumables.filter_work_time" has no existing object, this might lead to an error in future versions

roborock.0
2025-01-05 16:25:22.068 warn State "roborock.0.Devices.52nkyxg5GRqLBvhDnBr6nw.consumables.side_brush_work_time" has no existing object, this might lead to an error in future versions

roborock.0
2025-01-05 16:25:22.067 warn State "roborock.0.Devices.52nkyxg5GRqLBvhDnBr6nw.consumables.main_brush_work_time" has no existing object, this might lead to an error in future versions

roborock.0
2025-01-05 16:25:02.479 warn Unsupported attribute: kct of get_status with value 0. Please contact the dev to add the newly found attribute of your robot. Model: roborock.vacuum.a21

roborock.0
2025-01-05 16:25:01.496 warn Unsupported attribute: in_warmup of get_status with value 0. Please contact the dev to add the newly found attribute of your robot. Model: roborock.vacuum.a21

roborock.0
2025-01-05 16:25:01.143 warn Unsupported attribute: monitor_status of get_status with value 0. Please contact the dev to add the newly found attribute of your robot. Model: roborock.vacuum.a21

roborock.0
2025-01-05 16:24:22.101 warn State "roborock.0.Devices.52nkyxg5GRqLBvhDnBr6nw.consumables.dust_collection_work_times" has no existing object, this might lead to an error in future versions

roborock.0
2025-01-05 16:24:22.101 warn State "roborock.0.Devices.52nkyxg5GRqLBvhDnBr6nw.consumables.sensor_dirty_time" has no existing object, this might lead to an error in future versions

roborock.0
2025-01-05 16:24:22.100 warn State "roborock.0.Devices.52nkyxg5GRqLBvhDnBr6nw.consumables.filter_element_work_time" has no existing object, this might lead to an error in future versions

roborock.0
2025-01-05 16:24:22.100 warn State "roborock.0.Devices.52nkyxg5GRqLBvhDnBr6nw.consumables.filter_work_time" has no existing object, this might lead to an error in future versions

roborock.0
2025-01-05 16:24:22.097 warn State "roborock.0.Devices.52nkyxg5GRqLBvhDnBr6nw.consumables.side_brush_work_time" has no existing object, this might lead to an error in future versions

roborock.0
2025-01-05 16:24:22.096 warn State "roborock.0.Devices.52nkyxg5GRqLBvhDnBr6nw.consumables.main_brush_work_time" has no existing object, this might lead to an error in future versions

Liegt es daran dass der Slim noch nicht kompatibel ist?
Falls ja, kann dieser über ein Update mit aufgenommen werden :)?

Vielen Dank vorab!

wolfi913

@adri525 sagte in Neuer Adapter für Roborock-Staubsauger:

Liegt es daran dass der Slim noch nicht kompatibel ist?
Falls ja, kann dieser über ein Update mit aufgenommen werden :)?

Kommt lt Issue ins nächste Update rein
https://github.com/copystring/ioBroker.roborock/issues/738

Wolfi913 created this issue in copystring/ioBroker.roborock

closed [BUG] Qrevo Slim, Warnmeldungen #738

wendy2702

Hi,

wie bekomme ich denn den Eintrag weg ohne den Adapter 0.6.18 deinstallieren zu müssen:

Bei mir funktioniert der nämlich nicht.

Und sieht das Debug log bei euch auch so aus, das geht so unendlich weiter.

roborock.0
	2025-01-23 14:21:18.343	debug	Client disconnected. Stopping interval.
roborock.0
	2025-01-23 14:21:17.342	debug	Client disconnected. Stopping interval.
roborock.0
	2025-01-23 14:21:16.341	debug	Client disconnected. Stopping interval.
roborock.0
	2025-01-23 14:21:15.340	debug	Client disconnected. Stopping interval.
roborock.0
	2025-01-23 14:21:14.880	debug	Client disconnected
roborock.0
	2025-01-23 14:21:14.879	debug	Client disconnected. Stopping interval.
roborock.0
	2025-01-23 14:21:13.878	debug	Websocket client connected
roborock.0
	2025-01-23 14:21:13.878	debug	Websocket client connected
roborock.0
	2025-01-23 14:21:13.340	debug	Client disconnected. Stopping interval.
roborock.0
	2025-01-23 14:21:12.339	debug	Client disconnected. Stopping interval.
roborock.0
	2025-01-23 14:21:11.337	debug	Client disconnected. Stopping interval.
roborock.0
	2025-01-23 14:21:10.337	debug	Client disconnected. Stopping interval.
roborock.0
	2025-01-23 14:21:09.336	debug	Client disconnected. Stopping interval.
roborock.0
	2025-01-23 14:21:08.335	debug	Client disconnected. Stopping interval.
roborock.0
	2025-01-23 14:21:07.332	debug	Client disconnected. Stopping interval.
roborock.0
	2025-01-23 14:21:06.329	debug	Client disconnected. Stopping interval.
roborock.0
	2025-01-23 14:21:05.328	debug	Client disconnected. Stopping interval.
roborock.0
	2025-01-23 14:21:04.327	debug	Client disconnected. Stopping interval.
roborock.0
	2025-01-23 14:21:03.327	debug	Client disconnected. Stopping interval.
roborock.0
	2025-01-23 14:21:02.882	debug	Client disconnected
roborock.0
	2025-01-23 14:21:02.881	debug	Client disconnected. Stopping interval.
roborock.0
	2025-01-23 14:21:02.441	debug	Size of message queue: 0
roborock.0
	2025-01-23 14:21:02.441	debug	Local message with protocol 4 and id 499 received. Result: [203]
roborock.0
	2025-01-23 14:21:02.440	debug	Chunk buffer data is complete. Processing...
roborock.0
	2025-01-23 14:21:02.439	debug	new chunk started
roborock.0
	2025-01-23 14:21:02.435	debug	Chunk buffer data is complete. Processing...
roborock.0
	2025-01-23 14:21:02.435	debug	new chunk started
roborock.0
	2025-01-23 14:21:02.431	debug	Sent payload for 5xxxxxmr with {"dps":{"4":"{\"id\":499,\"method\":\"get_water_box_custom_mode\",\"params\":[]}"},"t":1737638462} using local connection
roborock.0
	2025-01-23 14:21:02.326	debug	Size of message queue: 0
roborock.0
	2025-01-23 14:21:02.326	debug	Local message with protocol 4 and id 498 received. Result: [{"carpet_clean_mode":1}]
roborock.0
	2025-01-23 14:21:02.325	debug	Chunk buffer data is complete. Processing...
roborock.0
	2025-01-23 14:21:02.325	debug	new chunk started
roborock.0
	2025-01-23 14:21:02.324	debug	Chunk buffer data is complete. Processing...
roborock.0
	2025-01-23 14:21:02.323	debug	new chunk started

Walter White

Hallo, ich habe mehrmals am Tag eine rote Meldung, wie bekomme ich die weg?

	Failed to get home details: Error [ERR_SOCKET_DGRAM_NOT_RUNNING]: Not running at healthCheck (node:dgram:922:11) at Socket.bind (node:dgram:242:3) at /opt/iobroker/node_modules/iobroker.roborock/lib/localConnector.js:213:11 at new Promise (<anonymous>) at localConnector.getLocalDevices (/opt/iobroker/node_modules/iobroker.roborock/lib/localConnector.js:185:10) at Roborock.initializeHomeDetails (/opt/iobroker/node_modules/iobroker.roborock/main.js:197:56) at async /opt/iobroker/node_modules/iobroker.roborock/main.js:77:4

Vumer

@walter-white sagte in Neuer Adapter für Roborock-Staubsauger:

Hallo, ich habe mehrmals am Tag eine rote Meldung, wie bekomme ich die weg?

ich auch, alle 3 St.

roborock.0 2025-02-02 13:44:58.920	error	Failed to get home details: Error: Not running at healthCheck (node:dgram:922:11) at Socket.bind (node:dgram:242:3) at /opt/iobroker/node_modules/iobroker.roborock/lib/localConnector.js:213:11 at new Promise (<anonymous>) at localConnector.getLocalDevices (/opt/iobroker/node_modules/iobroker.roborock/lib/localConnector.js:185:10) at Roborock.initializeHomeDetails (/opt/iobroker/node_modules/iobroker.roborock/main.js:197:56) at /opt/iobroker/node_modules/iobroker.roborock/main.js:77:4

Roborock Q7 Max

Manolo

Bei mir die gleiche Fehlermeldung, auch alle paar Stunden.

Roborock S7 Pro Ultra
Roborock Qrevo Pro

RISSN

der Fehler kommt bei mir auch, aber es läuft alles ohne Probleme, Roborock S6 VMax

gutgut30

Habe die Meldung ebenso. Hat schon jemand ein Issue auf Git dazu erstellt?

mickemup

@gutgut30
Ist schon ne Weile offen.
Aber es soll zur nächsten Version behoben sein

https://github.com/copystring/ioBroker.roborock/issues/737

Croxxii created this issue in copystring/ioBroker.roborock

closed [BUG] Failed to get home details #737

Farmer-cb

Hallo
was mach ich falsch, das die deviceStatusmeldungen etc immer erst zur vollen Minute aktualisiert werden??
kann ich da im Adapter bzw in meinem Roborock QRevo-Pro was falsch eingestellt haben???,

wenn ich eine Befehl sende geht das ja fast zeitgleich an den Roboter

mfg
Farmer

NEWS

Neuer Adapter für Roborock-Staubsauger

closed [BUG] Qrevo Slim, Warnmeldungen #738

closed [BUG] Failed to get home details #737

Support us

746
Online

31.7k
Users

79.9k
Topics

1.3m
Posts

NEWS

Neuer Adapter für Roborock-Staubsauger

closed [BUG] Qrevo Slim, Warnmeldungen #738

closed [BUG] Failed to get home details #737

Support us

746Online

31.7kUsers

79.9kTopics

1.3mPosts

746
Online

31.7k
Users

79.9k
Topics

1.3m
Posts