copystring
[BUG] multiple warnings and error messages
Bug Description
After my S8 MaxV Ultra updated to V02.39.00 a few weeks ago, the adapter stopped working. After installing dev_ts, it worked again for a while, but then the log was full of spam. Eventually (at varying intervals), the adapter stops working altogether and shows a red warning. A restart is then required.
Steps to Reproduce
Adapter starts. I think it depends on the device/firmware.
Debug Log
Adapter Version
dev_ts
JS-Controller Version
7.0.7
Node.js Version
v22.12.0
Operating System
Raspbian GNU/Linux 11 (bullseye) [PI 4]
Firmware version of device
V02.39.00
Gestern gab es ein großes Update der https://github.com/copystring/ioBroker.roborock/tree/dev_ts branch. Würdest du neue Version mal ausprobieren und bei Fehlern ein neues Debuglog hochladen?
Habe seit einiger Zeit die dev_ts Version im Einsatz, bisher keine großen Probleme und habe gestern mal nach deiner Aussage auf die neue Version geupdatet, aber nun erhalte ich seitdem im Minutentakt folgende Fehlermeldung (bei einem Qrevo Master mit aktueller Firmware):
roborock.0 | 2025-11-16 09:55:59.199 | warn | [processDockType|7d6aikLpBH9vGNulkUirEY] Unknown dock type 14 encountered. No features applied. Please report this model and dock type. -- | -- | -- | -- roborock.0 | 2025-11-16 09:55:59.184 | warn | [processDockType|7d6aikLpBH9vGNulkUirEY] Unknown dock type 14 encountered. No features applied. Please report this model and dock type. roborock.0 | 2025-11-16 09:54:59.206 | warn | [processDockType|7d6aikLpBH9vGNulkUirEY] Unknown dock type 14 encountered. No features applied. Please report this model and dock type. roborock.0 | 2025-11-16 09:54:59.192 | warn | [processDockType|7d6aikLpBH9vGNulkUirEY] Unknown dock type 14 encountered. No features applied. Please report this model and dock type. roborock.0 | 2025-11-16 09:53:59.369 | warn | [processDockType|7d6aikLpBH9vGNulkUirEY] Unknown dock type 14 encountered. No features applied. Please report this model and dock type. roborock.0 | 2025-11-16 09:53:59.354 | warn | [processDockType|7d6aikLpBH9vGNulkUirEY] Unknown dock type 14 encountered. No features applied. Please report this model and dock type. roborock.0 | 2025-11-16 09:52:59.057 | warn | [processDockType|7d6aikLpBH9vGNulkUirEY] Unknown dock type 14 encountered. No features applied. Please report this model and dock type. roborock.0 | 2025-11-16 09:52:59.043 | warn | [processDockType|7d6aikLpBH9vGNulkUirEY] Unknown dock type 14 encountered. No features applied. Please report this model and dock type. roborock.0 | 2025-11-16 09:51:59.275 | warn | [processDockType|7d6aikLpBH9vGNulkUirEY] Unknown dock type 14 encountered. No features applied. Please report this model and dock type. roborock.0 | 2025-11-16 09:51:59.202 | warn | [processDockType|7d6aikLpBH9vGNulkUirEY] Unknown dock type 14 encountered. No features applied. Please report this model and dock type. roborock.0 | 2025-11-16 09:50:58.884 | warn | [processDockType|7d6aikLpBH9vGNulkUirEY] Unknown dock type 14 encountered. No features applied. Please report this model and dock type. roborock.0 | 2025-11-16 09:50:58.870 | warn | [processDockType|7d6aikLpBH9vGNulkUirEY] Unknown dock type 14 encountered. No features applied. Please report this model and dock type. roborock.0 | 2025-11-16 09:49:58.618 | warn | [processDockType|7d6aikLpBH9vGNulkUirEY] Unknown dock type 14 encountered. No features applied. Please report this model and dock type. roborock.0 | 2025-11-16 09:49:58.604 | warn | [processDockType|7d6aikLpBH9vGNulkUirEY] Unknown dock type 14 encountered. No features applied. Please report this model and dock type. roborock.0 | 2025-11-16 09:48:58.851 | warn | [processDockType|7d6aikLpBH9vGNulkUirEY] Unknown dock type 14 encountered. No features applied. Please report this model and dock type. roborock.0 | 2025-11-16 09:48:58.667 | warn | [processDockType|7d6aikLpBH9vGNulkUirEY] Unknown dock type 14 encountered. No features applied. Please report this model and dock type. roborock.0 | 2025-11-16 09:47:58.509 | warn | [processDockType|7d6aikLpBH9vGNulkUirEY] Unknown dock type 14 encountered. No features applied. Please report this model and dock type. roborock.0 | 2025-11-16 09:47:58.495 | warn | [processDockType|7d6aikLpBH9vGNulkUirEY] Unknown dock type 14 encountered. No features applied. Please report this model and dock type. roborock.0 | 2025-11-16 09:46:58.975 | warn | [processDockType|7d6aikLpBH9vGNulkUirEY] Unknown dock type 14 encountered. No features applied. Please report this model and dock type. roborock.0 | 2025-11-16 09:46:58.961 | warn | [processDockType|7d6aikLpBH9vGNulkUirEY] Unknown dock type 14 encountered. No features applied. Please report this model and dock type. roborock.0 | 2025-11-16 09:45:58.559 | warn | [processDockType|7d6aikLpBH9vGNulkUirEY] Unknown dock type 14 encountered. No features applied. Please report this model and dock type. roborock.0 | 2025-11-16 09:45:58.545 | warn | [processDockType|7d6aikLpBH9vGNulkUirEY] Unknown dock type 14 encountered. No features applied. Please report this model and dock type. roborock.0 | 2025-11-16 09:44:58.882 | warn | [processDockType|7d6aikLpBH9vGNulkUirEY] Unknown dock type 14 encountered. No features applied. Please report this model and dock type. roborock.0 | 2025-11-16 09:44:58.868 | warn | [processDockType|7d6aikLpBH9vGNulkUirEY] Unknown dock type 14 encountered. No features applied. Please report this model and dock type.
Habe seit heute einen Roborock Saros 10R im Einsatz und mit der aktuellen dev_ts ebenfalls ähnliche Warnings bzgl. dock type:
[processDockType\|71KBZEG0SWDncCYYWdVPtQ] Unknown dock type 16 encountered. No features applied. Please report this model and dock type.
Bitte https://github.com/copystring/ioBroker.roborock/tree/dev_ts neu laden und testen.
Bei mir ist auch mit dieser Version weiterhin die selbe Warnung bzgl. dock type zu sehen:
2025-11-23 13:20:59.629 - info: host.raspberrypi-gang instance system.adapter.roborock.0 in version "0.6.19" (non-npm: copystring/ioBroker.roborock#dev_ts) started with pid 4145542 2025-11-23 13:21:02.377 - debug: roborock.0 (4145542) Redis Objects: Use Redis connection: 127.0.0.1:6380 2025-11-23 13:21:02.427 - debug: roborock.0 (4145542) Objects client ready ... initialize now 2025-11-23 13:21:02.430 - debug: roborock.0 (4145542) Objects create System PubSub Client 2025-11-23 13:21:02.444 - debug: roborock.0 (4145542) Objects create User PubSub Client 2025-11-23 13:21:02.592 - debug: roborock.0 (4145542) Objects client initialize lua scripts 2025-11-23 13:21:02.600 - debug: roborock.0 (4145542) Objects connected to redis: 127.0.0.1:6380 2025-11-23 13:21:02.624 - debug: roborock.0 (4145542) Redis States: Use Redis connection: 127.0.0.1:6379 2025-11-23 13:21:02.632 - debug: roborock.0 (4145542) States create System PubSub Client 2025-11-23 13:21:02.634 - debug: roborock.0 (4145542) States create User PubSub Client 2025-11-23 13:21:02.646 - debug: roborock.0 (4145542) States connected to redis: 127.0.0.1:6379 2025-11-23 13:21:02.683 - debug: roborock.0 (4145542) Plugin sentry Initialize Plugin (enabled=true) 2025-11-23 13:21:03.290 - info: roborock.0 (4145542) starting. Version 0.6.19 (non-npm: copystring/ioBroker.roborock#dev_ts) in /opt/iobroker/node_modules/iobroker.roborock, node: v22.21.0, js-controller: 7.0.7 2025-11-23 13:21:03.365 - debug: roborock.0 (4145542) Schedule restart: 0 9 * * * 2025-11-23 13:21:03.460 - info: roborock.0 (4145542) Starting adapter. This might take a few minutes... 2025-11-23 13:21:03.499 - info: roborock.0 (4145542) Loaded existing clientID: 9ad939e4-e170-44a9-b990-743ffc58a29a 2025-11-23 13:21:03.505 - debug: roborock.0 (4145542) initialize http_api 2025-11-23 13:21:03.711 - debug: roborock.0 (4145542) getHomeDetail: {"code":200,"msg":"success","data":{"id":134567,"name":"Zuhause","tuyaHomeId":11408216,"rrHomeId":144574,"deviceListOrder":null}} 2025-11-23 13:21:03.711 - debug: roborock.0 (4145542) this.homeID: 144574 2025-11-23 13:21:03.713 - info: roborock.0 (4145542) Connecting to MQTT Broker at ssl://mqtt-eu.roborock.com:8883... 2025-11-23 13:21:03.862 - info: roborock.0 (4145542) MQTT message listener initialized. 2025-11-23 13:21:03.863 - debug: roborock.0 (4145542) Getting HomeData with homeId: 144574 2025-11-23 13:21:03.946 - info: roborock.0 (4145542) MQTT connection established. 2025-11-23 13:21:03.973 - debug: roborock.0 (4145542) Subscribed to rr/m/o/1EGv3siiGqQWoRyoDfxzB/433cb07d/# 2025-11-23 13:21:03.994 - debug: roborock.0 (4145542) [LocalAPI] UDP Discovery started 2025-11-23 13:21:03.999 - info: roborock.0 (4145542) [LocalAPI] UDP listening on 0.0.0.0:58866 2025-11-23 13:21:07.631 - debug: roborock.0 (4145542) [LocalAPI] UDP message received: 4c3031f0657add000200466ad3d2fecbb396fac13dde91462c029fe7e00a10822bde224bd02ea40d7971a80248d5e481a2ae8b370ab220f50dd06596bdcad9e6da0fdfd329a4b9bf5492402f0a2934a9ea93dcd23f 2025-11-23 13:21:07.636 - debug: roborock.0 (4145542) [LocalAPI] Found local device: 71KBZEG0SWDncCYYWdVPtQ @ 192.168.2.172 using version L01 2025-11-23 13:21:07.825 - debug: roborock.0 (4145542) [LocalAPI] UDP message received: 312e30000000010002004052c12a10b7a9172e72df50ea630ec94818de30e6bb6b77aed7632c6f2c3080459b49e16bb83470a6033c941e779893794d7888fd0841e9895bb58e17ad6cb90e5183e6cc 2025-11-23 13:21:07.828 - debug: roborock.0 (4145542) [LocalAPI] Found local device: BzoCkI61lkZZ4dPedPre6 @ 192.168.2.201 using version 1.0 2025-11-23 13:21:12.630 - debug: roborock.0 (4145542) [LocalAPI] UDP message received: 4c3031701132b20002004663cf8393db6f21743bd5071a7dda58dca7fc5e1150ae8a6d5395d06b5ab66ee70b8c2b0e22f56408f3c142c3c7e76effabe136d1bf02171d111403c03565deb74c26aca6e120894b8033 2025-11-23 13:21:12.827 - debug: roborock.0 (4145542) [LocalAPI] UDP message received: 312e30000000010002004052c12a10b7a9172e72df50ea630ec94818de30e6bb6b77aed7632c6f2c3080459b49e16bb83470a6033c941e779893794d7888fd0841e9895bb58e17ad6cb90e5183e6cc 2025-11-23 13:21:13.999 - info: roborock.0 (4145542) [LocalAPI] UDP discovery stopped 2025-11-23 13:21:14.000 - info: roborock.0 (4145542) [LocalAPI] UDP discovery finished after 10s 2025-11-23 13:21:14.003 - info: roborock.0 (4145542) [DeviceManager] Initializing 2 devices... 2025-11-23 13:21:14.006 - debug: roborock.0 (4145542) [DeviceManager] Looking for feature handler for model: roborock.vacuum.a144 (Category: robot.vacuum.cleaner) 2025-11-23 13:21:14.007 - info: roborock.0 (4145542) [DeviceManager] Using specific feature handler for model: roborock.vacuum.a144 2025-11-23 13:21:14.009 - debug: roborock.0 (4145542) Feature registry initialization flag set. 2025-11-23 13:21:14.011 - debug: roborock.0 (4145542) Registering Vacuum features... 2025-11-23 13:21:14.012 - debug: roborock.0 (4145542) Vacuum feature registry size: 33 2025-11-23 13:21:14.014 - debug: roborock.0 (4145542) [DeviceManager] Looking for feature handler for model: roborock.vacuum.a15 (Category: robot.vacuum.cleaner) 2025-11-23 13:21:14.015 - info: roborock.0 (4145542) [DeviceManager] Using specific feature handler for model: roborock.vacuum.a15 2025-11-23 13:21:14.050 - debug: roborock.0 (4145542) duid: 71KBZEG0SWDncCYYWdVPtQ, mqtt: true, local: false, remote: false 2025-11-23 13:21:14.057 - debug: roborock.0 (4145542) Sent payload for 71KBZEG0SWDncCYYWdVPtQ with {"dps":{"101":"{"id":1,"method":"get_prop","params":["get_status"]}"},"t":1763900474} using cloud connection using version 1.0 2025-11-23 13:21:14.065 - debug: roborock.0 (4145542) duid: BzoCkI61lkZZ4dPedPre6, mqtt: true, local: false, remote: false 2025-11-23 13:21:14.068 - debug: roborock.0 (4145542) Sent payload for BzoCkI61lkZZ4dPedPre6 with {"dps":{"101":"{"id":2,"method":"get_prop","params":["get_status"]}"},"t":1763900474} using cloud connection using version 1.0 2025-11-23 13:21:14.133 - debug: roborock.0 (4145542) Successfully resolved request id 1 using protocol: 102. Size of message queue: 1 2025-11-23 13:21:14.134 - debug: roborock.0 (4145542) Received value for get_prop on 71KBZEG0SWDncCYYWdVPtQ: [{"msg_ver":2,"msg_seq":267,"state":8,"battery":100,"clean_time":58,"clean_area":0,"error_code":0,"m...} 2025-11-23 13:21:14.192 - debug: roborock.0 (4145542) Successfully resolved request id 2 using protocol: 102. Size of message queue: 0 2025-11-23 13:21:14.193 - debug: roborock.0 (4145542) Received value for get_prop on BzoCkI61lkZZ4dPedPre6: [{"msg_ver":2,"msg_seq":255,"state":8,"battery":100,"clean_time":2985,"clean_area":47537500,"error_c...} 2025-11-23 13:21:14.236 - debug: roborock.0 (4145542) [71KBZEG0SWDncCYYWdVPtQ] Processing dock type 16 for Vacuum 2025-11-23 13:21:14.237 - warn: roborock.0 (4145542) [processDockType|71KBZEG0SWDncCYYWdVPtQ] Unknown dock type 16 encountered. No features applied. Please report this model and dock type. 2025-11-23 13:21:14.328 - debug: roborock.0 (4145542) [BzoCkI61lkZZ4dPedPre6] Processing dock type 0 for Vacuum 2025-11-23 13:21:14.362 - debug: roborock.0 (4145542) duid: BzoCkI61lkZZ4dPedPre6, mqtt: true, local: false, remote: false 2025-11-23 13:21:14.363 - debug: roborock.0 (4145542) Sent payload for BzoCkI61lkZZ4dPedPre6 with {"dps":{"101":"{"id":3,"method":"get_fw_features"}"},"t":1763900474} using cloud connection using version 1.0 2025-11-23 13:21:14.410 - debug: roborock.0 (4145542) duid: 71KBZEG0SWDncCYYWdVPtQ, mqtt: true, local: false, remote: false 2025-11-23 13:21:14.411 - debug: roborock.0 (4145542) Sent payload for 71KBZEG0SWDncCYYWdVPtQ with {"dps":{"101":"{"id":4,"method":"get_fw_features"}"},"t":1763900474} using cloud connection using version 1.0 2025-11-23 13:21:14.472 - debug: roborock.0 (4145542) Successfully resolved request id 4 using protocol: 102. Size of message queue: 1 2025-11-23 13:21:14.474 - debug: roborock.0 (4145542) Received value for get_fw_features on 71KBZEG0SWDncCYYWdVPtQ: [111,112,113,114,115,116,117,118,119,120,121,122,123,124,125]...} 2025-11-23 13:21:14.475 - debug: roborock.0 (4145542) [HTTP_API|71KBZEG0SWDncCYYWdVPtQ] Stored FW features result: [111,112,113,114,115,116,117,118,119,120,121,122,123,124,125] 2025-11-23 13:21:14.486 - debug: roborock.0 (4145542) Successfully resolved request id 3 using protocol: 102. Size of message queue: 0 2025-11-23 13:21:14.487 - debug: roborock.0 (4145542) Received value for get_fw_features on BzoCkI61lkZZ4dPedPre6: [111,112,113,114,115,116,117,118,119,120,122,123,124,125]...} 2025-11-23 13:21:14.487 - debug: roborock.0 (4145542) [HTTP_API|BzoCkI61lkZZ4dPedPre6] Stored FW features result: [111,112,113,114,115,116,117,118,119,120,122,123,124,125] 2025-11-23 13:21:14.541 - debug: roborock.0 (4145542) [DeviceManager] Applying initial features for 71KBZEG0SWDncCYYWdVPtQ 2025-11-23 13:21:14.546 - debug: roborock.0 (4145542) [DeviceManager] Applying initial features for BzoCkI61lkZZ4dPedPre6 2025-11-23 13:21:14.548 - debug: roborock.0 (4145542) [71KBZEG0SWDncCYYWdVPtQ] Processing dock type 16 for Vacuum 2025-11-23 13:21:14.548 - warn: roborock.0 (4145542) [processDockType|71KBZEG0SWDncCYYWdVPtQ] Unknown dock type 16 encountered. No features applied. Please report this model and dock type.
@Black-Thunder danke für dein Feedback. Schau doch mal, ob es jetzt geht. Ich habe den Docktyp vom Saros 10R hinzugefügt.
@copystring der Docktyp 16 "funktioniert" jetzt glaube ich, denn bei meinem Saros Z70 kommt diesbezüglich keine Fehlermeldung mehr aufgrund des Docktyps 16, Allerrdings weiterhin folgende Fehlermeldung:
| `roborock.0 | 2025-11-23 15:55:30.899 | warn | [2qS65FyqescJ1Qlr7evMBb] Using FallbackVacuumFeatures for model roborock.vacuum.a179. Runtime detection and base vacuum features active. |
|---|---|---|---|
| roborock.0 | 2025-11-23 15:55:30.898 | warn | [DeviceManager] Model "roborock.vacuum.a179" (Category: robot.vacuum.cleaner) not registered. Using fallback.` |
Also der Docktyp 16 funktioniert beim Saros Z70, aber eben die Modellerkannung an sich nicht. Kannst du diesen eventuell hinzufügen? Ich kann aber auch https://github.com/copystring/ioBroker.roborock/issues/927 dort gerne auch nochmal Rückmeldung geben.
Bezüglich meines weiter oben beschrieben Fehler vom Docktyp 14 (von meinem Qrevo Master) hat sich aber nichts geändert, der tritt trotzdem noch auf.
roborock.0 | 2025-11-23 15:55:31.800 | warn | [processDockType\|7d6aikLpBH9vGNulkUirEY] Unknown dock type 14 encountered. No features applied. Please report this model and dock type. -- | -- | -- | --
@PrinzVonBillAir am besten in https://github.com/copystring/ioBroker.roborock/issues/927 fortsetzen. Ich habe den Saugroboter jetzt hinzugefügt. Ich dachte, der wäre schon drin. Hab ich mich wohl verguckt.
Danke, beim Saros Z70 bekomme ich nun keine Fehler mehr angezeigt. Beim Qrevo Master immer noch Docktyp 14 Warnung.
| `roborock.0 | 2025-11-23 16:19:15.770 | warn | [processDockType|7d6aikLpBH9vGNulkUirEY] Unknown dock type 14 encountered. No features applied. Please report this model and dock type. |
|---|---|---|---|
| roborock.0 | 2025-11-23 16:19:15.755 | warn | [processDockType|7d6aikLpBH9vGNulkUirEY] Unknown dock type 14 encountered. No features applied. Please report this model and dock type. |
| roborock.0 | 2025-11-23 16:18:33.827 | info | [DeviceManager] Background clean summary updates finished. |
| roborock.0 | 2025-11-23 16:18:18.215 | info | [DeviceManager] Starting background clean summary updates... |
| roborock.0 | 2025-11-23 16:18:15.234 | warn | [processDockType|7d6aikLpBH9vGNulkUirEY] Unknown dock type 14 encountered. No features applied. Please report this model and dock type. |
| roborock.0 | 2025-11-23 16:18:15.188 | warn | [processDockType|7d6aikLpBH9vGNulkUirEY] Unknown dock type 14 encountered. No features applied. Please report this model and dock type. |
| roborock.0 | 2025-11-23 16:18:13.377 | info | Adapter startup finished. Let's go! |
| roborock.0 | 2025-11-23 16:18:13.376 | info | [DeviceManager] Starting main poll (every 60s) and fast map poll (every 1s during cleaning) |
| roborock.0 | 2025-11-23 16:18:13.215 | info | [DeviceManager] All devices initialized. |
| roborock.0 | 2025-11-23 16:18:13.147 | warn | [processDockType|7d6aikLpBH9vGNulkUirEY] Unknown dock type 14 encountered. No features applied. Please report this model and dock type. |
| roborock.0 | 2025-11-23 16:18:12.222 | warn | [processDockType|7d6aikLpBH9vGNulkUirEY] Unknown dock type 14 encountered. No features applied. Please report this model and dock type. |
| roborock.0 | 2025-11-23 16:18:11.635 | info | [DeviceManager] Using specific feature handler for model: roborock.vacuum.a117 |
| roborock.0 | 2025-11-23 16:18:11.634 | info | [DeviceManager] Using specific feature handler for model: roborock.vacuum.a179 |
| roborock.0 | 2025-11-23 16:18:11.633 | info | [DeviceManager] Initializing 2 devices... |
| roborock.0 | 2025-11-23 16:18:11.633 | info | [LocalAPI] UDP discovery finished after 10s |
| roborock.0 | 2025-11-23 16:18:11.632 | info | [LocalAPI] UDP discovery stopped |
| roborock.0 | 2025-11-23 16:18:01.632 | info | [LocalAPI] UDP listening on 0.0.0.0:58866 |
| roborock.0 | 2025-11-23 16:18:01.575 | info | MQTT connection established. |
| roborock.0 | 2025-11-23 16:18:01.496 | info | MQTT message listener initialized. |
| roborock.0 | 2025-11-23 16:18:01.450 | info | Connecting to MQTT Broker at ssl://mqtt-eu-4.roborock.com:8883... |
| roborock.0 | 2025-11-23 16:18:01.302 | info | Loaded existing clientID: 562a1d89a699b175e9c13c448206a413 |
| roborock.0 | 2025-11-23 16:18:01.245 | info | Starting adapter. This might take a few minutes...` |
Ist jetzt auch behoben. Bitte zukünftig aber ein eigenes Issue aufmachen und nicht irgendein anderes Issue nehmen um komplett andere Probleme zu besprechen. Das hier hat gar nichts mit dem eigentlichen Problem vom OP zu tun, der einen S8 MaxV Ultra hat.
@Black-Thunder danke für dein Feedback. Schau doch mal, ob es jetzt geht. Ich habe den Docktyp vom Saros 10R hinzugefügt.
Ja, jetzt passt alles. Danke dir 👍
Und sorry fürs Kapern vom Issue, ich gelobe in Zukunft Besserung 😉