Adapter crash mit 3.2.2 bei Raumreinigung

[saeft2003]

Hallo ab der 3.2.2 crasht der Adapter genau in dem Moment wenn ich eine Raumreinigung starte. Nach einem downgrade auf 3.2.1 gibt es keine Probleme mehr.

mihome-vacuum.0

2021-08-07 21:05:00.612 warn Terminated (UNCAUGHT_EXCEPTION): Without reason mihome-vacuum.0 2021-08-07 21:05:00.612 error Socket Close mihome-vacuum.0 2021-08-07 21:05:00.547 error undefined mihome-vacuum.0 2021-08-07 21:05:00.547 error unhandled promise rejection: undefined mihome-vacuum.0 2021-08-07 21:05:00.544 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(). mihome-vacuum.0 2021-08-07 13:40:08.943 warn Terminated (UNCAUGHT_EXCEPTION): Without reason mihome-vacuum.0 2021-08-07 13:40:08.942 error Socket Close mihome-vacuum.0 2021-08-07 13:40:08.901 error undefined mihome-vacuum.0 2021-08-07 13:40:08.901 error unhandled promise rejection: undefined mihome-vacuum.0 2021-08-07 13:40:08.899 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().

[ticaki]

Bei mir ist es ähnlich, ist mir bis jetzt aber nur aufgefallen, wenn der Sauger mehrere Stunden nicht genutzt wurde:

` 2021-08-13 12:53:25.655 - info: mihome-vacuum.0 (1568) trigger cleaning all 2021-08-13 12:53:27.648 - warn: mihome-vacuum.0 (1568) Cant send command please try again "fan_power" 2021-08-13 12:53:27.659 - warn: mihome-vacuum.0 (1568) Cant send command please try again "start" 2021-08-13 12:53:27.669 - error: mihome-vacuum.0 (1568) 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(). 2021-08-13 12:53:27.670 - error: mihome-vacuum.0 (1568) unhandled promise rejection: undefined 2021-08-13 12:53:27.673 - error: mihome-vacuum.0 (1568) undefined 2021-08-13 12:53:27.819 - error: mihome-vacuum.0 (1568) Socket Close 2021-08-13 12:53:27.820 - info: mihome-vacuum.0 (1568) terminating 2021-08-13 12:53:27.821 - warn: mihome-vacuum.0 (1568) Terminated (UNCAUGHT_EXCEPTION): Without reason 2021-08-13 12:53:28.585 - error: host.tims-pi1 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: 2021-08-13 12:53:28.585 - error: host.tims-pi1 Caught by controller[1]: MESSAGE TIMEOUT 2021-08-13 12:53:28.586 - error: host.tims-pi1 instance system.adapter.mihome-vacuum.0 terminated with code 6 (UNCAUGHT_EXCEPTION) 2021-08-13 12:53:28.586 - info: host.tims-pi1 Restart adapter system.adapter.mihome-vacuum.0 because enabled 2021-08-13 12:53:58.611 - info: host.tims-pi1 instance system.adapter.mihome-vacuum.0 started with pid 25899 2021-08-13 12:54:00.406 - info: mihome-vacuum.0 (25899) starting. Version 3.2.2 in /opt/iobroker/node_modules/iobroker.mihome-vacuum, node: v12.22.5, js-controller: 3.3.15 2021-08-13 12:54:00.516 - info: mihome-vacuum.0 (25899) IOT enabled, create state 2021-08-13 12:54:10.567 - warn: mihome-vacuum.0 (25899) YOUR DEVICE IS CONNECTED BUT DID NOT ANSWER YET - CONNECTION CAN TAKE UP TO 10 MINUTES - PLEASE BE PATIENT AND DO NOT TURN THE ADAPTER OFF 2021-08-13 12:54:10.567 - warn: mihome-vacuum.0 (25899) No Answer for DeviceModel use old one 2021-08-13 12:54:10.568 - warn: mihome-vacuum.0 (25899) No Answer for DeviceModel use model from Config 2021-08-13 12:54:10.578 - info: mihome-vacuum.0 (25899) select standard vacuum protocol.... 2021-08-13 12:54:11.318 - info: mihome-vacuum.0 (25899) settest next timer: not available 2021-08-13 12:54:12.503 - info: mihome-vacuum.0 (25899) Map selected create states...

`

[MeisterTR]

Ein Debuglog wäre sehr hilfreich, damit ich sehen kann wieso er crashed

[ticaki]

Hab vor 6 Tagen meine Yahka Instanz auf Legacy umgestellt und Debug für mihome-vacuum aktiviert. Keinen einzigen "Absturz" des Adapters seit dem. Denke es hatte etwas mit dem Aufhängen des Yahka Adapters zu tun.

[Black-Thunder]

@MeisterTR Debug-Log eines Roborock S7 mit Adapterversion 3.2.2 beim automatischen Triggern von "multiRoomClean". Tritt aber wie oben schon erwähnt nur auf, wenn der Roboter eine ganze Zeit lang nicht gestartet wurde. In diesem Fall war am Montag die letzte automatische Reinigung.

2021-08-25 11:40:00.118 - debug: mihome-vacuum.0 (8557) command: multiRoomClean parent: rooms
2021-08-25 11:40:00.191 - debug: mihome-vacuum.0 (8557) Search can't be optimized because wildcard not at the end, fallback to keys!: function(doc) { if (doc.type === 'state') emit(doc._id, doc) }
2021-08-25 11:40:00.244 - debug: mihome-vacuum.0 (8557) sendTo "cleanSegments" to system.adapter.mihome-vacuum.0 from system.adapter.mihome-vacuum.0
2021-08-25 11:40:00.250 - debug: mihome-vacuum.0 (8557) We are in onMessage:{"command":"cleanSegments","message":{"segments":[21,16,22,20,18],"channels":["mihome-vacuum.0.rooms.508001010185","mihome-vacuum.0.rooms.508001010186","mihome-vacuum.0.rooms.508001010187","mihome-vacuum.0.rooms.508001010203","mihome-vacuum.0.rooms.508001010204"]},"from":"system.adapter.mihome-vacuum.0","_id":95307160}
2021-08-25 11:40:00.252 - debug: mihome-vacuum.0 (8557) start Cleaning: 18 MObj: {"command":"cleanSegments","message":"21,16,22,20,18","from":"system.adapter.mihome-vacuum.0","_id":95307160,"segments":[21,16,22,20,18],"channels":["mihome-vacuum.0.rooms.508001010185","mihome-vacuum.0.rooms.508001010186","mihome-vacuum.0.rooms.508001010187","mihome-vacuum.0.rooms.508001010203","mihome-vacuum.0.rooms.508001010204"]}
2021-08-25 11:40:00.252 - info: mihome-vacuum.0 (8557) trigger cleaning segment 21,16,22,20,18
2021-08-25 11:40:00.252 - debug: mihome-vacuum.0 (8557) Message= {"id":9020,"method":"app_segment_clean","params":[21,16,22,20,18]}
2021-08-25 11:40:02.254 - debug: mihome-vacuum.0 (8557) MIIO Receive Timeout for "app_segment_clean" <<<
2021-08-25 11:40:02.256 - error: mihome-vacuum.0 (8557) 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().
2021-08-25 11:40:02.257 - error: mihome-vacuum.0 (8557) unhandled promise rejection: undefined
2021-08-25 11:40:02.257 - error: mihome-vacuum.0 (8557) undefined
2021-08-25 11:40:02.395 - error: mihome-vacuum.0 (8557) Socket Close
2021-08-25 11:40:02.396 - info: mihome-vacuum.0 (8557) terminating
2021-08-25 11:40:02.397 - debug: mihome-vacuum.0 (8557) Plugin sentry destroyed
2021-08-25 11:40:02.397 - warn: mihome-vacuum.0 (8557) Terminated (UNCAUGHT_EXCEPTION): Without reason
2021-08-25 11:40:03.123 - error: host.raspberrypi 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:
2021-08-25 11:40:03.123 - error: host.raspberrypi Caught by controller[1]: MESSAGE TIMEOUT
2021-08-25 11:40:03.123 - error: host.raspberrypi instance system.adapter.mihome-vacuum.0 terminated with code 6 (UNCAUGHT_EXCEPTION)
2021-08-25 11:40:03.124 - info: host.raspberrypi Restart adapter system.adapter.mihome-vacuum.0 because enabled

Debug-Log, wenn direkt nach Neustart des Adapters wieder getriggert wird. Dann funktioniert alles wie erwartet.

2021-08-25 11:42:02.963 - debug: mihome-vacuum.0 (24107) command: multiRoomClean parent: rooms
2021-08-25 11:42:03.105 - debug: mihome-vacuum.0 (24107) Search can't be optimized because wildcard not at the end, fallback to keys!: function(doc) { if (doc.type === 'state') emit(doc._id, doc) }
2021-08-25 11:42:03.175 - debug: mihome-vacuum.0 (24107) sendTo "cleanSegments" to system.adapter.mihome-vacuum.0 from system.adapter.mihome-vacuum.0
2021-08-25 11:42:03.185 - debug: mihome-vacuum.0 (24107) We are in onMessage:{"command":"cleanSegments","message":{"segments":[21,16,22,20,18],"channels":["mihome-vacuum.0.rooms.508001010185","mihome-vacuum.0.rooms.508001010186","mihome-vacuum.0.rooms.508001010187","mihome-vacuum.0.rooms.508001010203","mihome-vacuum.0.rooms.508001010204"]},"from":"system.adapter.mihome-vacuum.0","_id":53536753}
2021-08-25 11:42:03.187 - debug: mihome-vacuum.0 (24107) start Cleaning: 18 MObj: {"command":"cleanSegments","message":"21,16,22,20,18","from":"system.adapter.mihome-vacuum.0","_id":53536753,"segments":[21,16,22,20,18],"channels":["mihome-vacuum.0.rooms.508001010185","mihome-vacuum.0.rooms.508001010186","mihome-vacuum.0.rooms.508001010187","mihome-vacuum.0.rooms.508001010203","mihome-vacuum.0.rooms.508001010204"]}
2021-08-25 11:42:03.187 - info: mihome-vacuum.0 (24107) trigger cleaning segment 21,16,22,20,18
2021-08-25 11:42:03.188 - debug: mihome-vacuum.0 (24107) Message= {"id":49,"method":"app_segment_clean","params":[21,16,22,20,18]}
2021-08-25 11:42:03.435 - debug: mihome-vacuum.0 (24107) MIIO RECIVE: {"id":49,"result":["ok"],"exe_time":101}
2021-08-25 11:42:06.308 - debug: mihome-vacuum.0 (24107) get params for stock Vacuum
2021-08-25 11:42:06.309 - debug: mihome-vacuum.0 (24107) Message= {"id":50,"method":"get_status"}
2021-08-25 11:42:06.543 - debug: mihome-vacuum.0 (24107) MIIO RECIVE: {"id":50,"result":[{"msg_ver":2,"msg_seq":12,"state":18,"battery":100,"clean_time":0,"clean_area":0,"error_code":0,"map_present":1,"in_cleaning":3,"in_returning":0,"in_fresh_state":0,"lab_status":1,"water_box_status":1,"fan_power":106,"dnd_enabled":0,"map_status":3,"is_locating":0,"lock_status":0,"water_box_mode":204,"water_box_carriage_status":0,"mop_forbidden_enable":0,"adbumper_status":[0,0,0],"water_shortage_status":0,"dock_type":0,"dust_collection_status":0,"auto_dust_collection":1,"mop_mode":302,"debug_mode":0}],"exe_time":101}
2021-08-25 11:42:06.544 - debug: mihome-vacuum.0 (24107) setGetStatus {"msg_ver":2,"msg_seq":12,"state":18,"battery":100,"clean_time":0,"clean_area":0,"error_code":0,"map_present":true,"in_cleaning":false,"in_returning":0,"in_fresh_state":0,"lab_status":1,"water_box_status":1,"fan_power":106,"dnd_enabled":false,"map_status":3,"is_locating":0,"lock_status":0,"water_box_mode":204,"water_box_carriage_status":0,"mop_forbidden_enable":0,"adbumper_status":[0,0,0],"water_shortage_status":0,"dock_type":0,"dust_collection_status":0,"auto_dust_collection":1,"mop_mode":302,"debug_mode":0,"error_text":"No error"}
2021-08-25 11:42:06.545 - debug: mihome-vacuum.0 (24107) Message= {"id":51,"method":"get_map_v1"}
2021-08-25 11:42:06.547 - debug: mihome-vacuum.0 (24107) Message= {"id":52,"method":"get_network_info"}

[allesgutewarweg]

Bei mir das Gleiche, habe ein Downgrade auf 3.2.1 gemacht und dieses und das Problem mit der Karte (https://github.com/iobroker-community-adapters/ioBroker.mihome-vacuum/issues/379) sind verschwunden. Die 3.2.2 scheint daher nicht ganz in Ordnung zu sein.

[stale[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs within the next 7 days. Please check if the issue is still relevant in the most current version of the adapter and tell us. Also check that all relevant details, logs and reproduction steps are included and update them if needed. Thank you for your contributions. Dieses Problem wurde automatisch als veraltet markiert, da es in letzter Zeit keine Aktivitäten gab. Es wird geschlossen, wenn nicht innerhalb der nächsten 7 Tage weitere Aktivitäten stattfinden. Bitte überprüft, ob das Problem auch in der aktuellsten Version des Adapters noch relevant ist, und teilt uns dies mit. Überprüft auch, ob alle relevanten Details, Logs und Reproduktionsschritte enthalten sind bzw. aktualisiert diese. Vielen Dank für Eure Unterstützung.

[dirkhe]

@MeisterTR kann es sein, dass hinter all den new Promise(), zb in der sendMessage ein .catch(..) dahinter muss?

[stale[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs within the next 7 days. Please check if the issue is still relevant in the most current version of the adapter and tell us. Also check that all relevant details, logs and reproduction steps are included and update them if needed. Thank you for your contributions. Dieses Problem wurde automatisch als veraltet markiert, da es in letzter Zeit keine Aktivitäten gab. Es wird geschlossen, wenn nicht innerhalb der nächsten 7 Tage weitere Aktivitäten stattfinden. Bitte überprüft, ob das Problem auch in der aktuellsten Version des Adapters noch relevant ist, und teilt uns dies mit. Überprüft auch, ob alle relevanten Details, Logs und Reproduktionsschritte enthalten sind bzw. aktualisiert diese. Vielen Dank für Eure Unterstützung.

[stale[bot]]

This issue has been automatically closed because of inactivity. Please open a new issue if still relevant and make sure to include all relevant details, logs and reproduction steps. Thank you for your contributions. Dieses Problem wurde aufgrund von Inaktivität automatisch geschlossen. Bitte öffnet ein neues Issue, falls dies noch relevant ist und stellt sicher das alle relevanten Details, Logs und Reproduktionsschritte enthalten sind. Vielen Dank für Eure Unterstützung.