NEWS
Test Adapter Mihome-vacuum v3.1.6 Next Generarition
Tester
1.2k
Beiträge
100
Kommentatoren
370.4k
Aufrufe
82
Watching
-
@ilovegym ja hat es. es gab Probleme bei mehreren Sauger dass die Karten teil nicht aktualisiert wurden. Das konnte ich jetzt wo ich mehrere Sauger habe nachvollziehen und frag nicht warum aber das ändern von map auf cleanmap hat den Erfolg gebraucht. (ich hab alles ausprobiert nur das ändern hat geholfen). Ich habe drei verschiedene Modelle damit konnte ich in den letzten Tagen schon einiges an Bugs glatt bügeln.
@meistertr hab den Vacuum V1 mit Valetudo.
Installation ohne AUffälligkeiten LOG auch ohne Auffälligkeiten. Das eine Answer Map Slot hatte ich vorher auch schon :)mihome-vacuum.0 2021-04-14 19:04:47.679 warn (18778) answer map_slot is currently not supported! mihome-vacuum.0 2021-04-14 19:04:27.601 warn (18778) answer map_slot is currently not supported! mihome-vacuum.0 2021-04-14 19:04:07.723 info (18778) settest next timer: not available mihome-vacuum.0 2021-04-14 19:04:07.498 info (18778) create state for carpet_mode mihome-vacuum.0 2021-04-14 19:04:07.482 warn (18778) answer map_slot is currently not supported! mihome-vacuum.0 2021-04-14 19:04:07.354 info (18778) Map selected create states... mihome-vacuum.0 2021-04-14 19:04:07.124 warn (18778) State "mihome-vacuum.0.deviceInfo.mac" has no existing object, this might lead to an error in future versions mihome-vacuum.0 2021-04-14 19:04:07.122 warn (18778) State "mihome-vacuum.0.deviceInfo.fw_ver" has no existing object, this might lead to an error in future versions mihome-vacuum.0 2021-04-14 19:04:07.121 warn (18778) State "mihome-vacuum.0.deviceInfo.model" has no existing object, this might lead to an error in future versionsOk, wenn ich versuche die MAP zu laden, bekomme ich auch o. g. warn-Meldung im LOG. Hab nur Valetudo bei Map aktiviert...
-
gerade den Saugi gestartet und versucht nach 30 Sek wieder nach Hause zu schicken:
mihome-vacuum.0 2021-04-14 19:12:58.963 warn (28226) answer map_slot is currently not supported! mihome-vacuum.0 2021-04-14 19:12:30.497 warn (28226) Error at stop Cleaning: MESSAGE TIMEOUT mihome-vacuum.0 2021-04-14 19:12:24.858 info (28226) Map selected create states... mihome-vacuum.0 2021-04-14 19:12:24.669 warn (28226) Login failed mihome-vacuum.0 2021-04-14 19:12:23.854 info (28226) settest next timer: not available mihome-vacuum.0 2021-04-14 19:12:23.262 info (28226) select standard vacuum protocol.... mihome-vacuum.0 2021-04-14 19:12:23.260 warn (28226) No Answer for DeviceModel use model from Config mihome-vacuum.0 2021-04-14 19:12:23.259 warn (28226) No Answer for DeviceModel use old one mihome-vacuum.0 2021-04-14 19:12:23.259 warn (28226) YOUR DEVICE IS CONNECTED BUT DID NOT ANSWER CONNECTION CAN TAKE UP TO 10 MINUTES PLESASE WAIT AND DON`T TRUN THE ADAPTER OFF mihome-vacuum.0 2021-04-14 19:12:13.156 info (28226) check group user admin group admin: false mihome-vacuum.0 2021-04-14 19:12:12.214 info (28226) check user admin pw iobroker: true mihome-vacuum.0 2021-04-14 19:12:11.689 info (28226) starting. Version 3.0.3 in /opt/iobroker/node_modules/iobroker.mihome-vacuum, node: v12.21.0, js-controller: 3.2.16 mihome-vacuum.0 2021-04-14 19:11:39.172 warn (27284) Terminated (UNCAUGHT_EXCEPTION): Without reason mihome-vacuum.0 2021-04-14 19:11:39.170 info (27284) terminating mihome-vacuum.0 2021-04-14 19:11:39.125 error (27284) Cannot read property 'channels' of null mihome-vacuum.0 2021-04-14 19:11:39.124 error at processImmediate (internal/timers.js:461:21) mihome-vacuum.0 2021-04-14 19:11:39.124 error at Immediate.<anonymous> (/opt/iobroker/node_modules/iobroker.js-controller/lib/adapter.js:5559:38) mihome-vacuum.0 2021-04-14 19:11:39.124 error at MihomeVacuum.emit (events.js:314:20) mihome-vacuum.0 2021-04-14 19:11:39.124 error at MihomeVacuum.onStateChange (/opt/iobroker/node_modules/iobroker.mihome-vacuum/main.js:316:10) mihome-vacuum.0 2021-04-14 19:11:39.124 error at VacuumManager.stateChange (/opt/iobroker/node_modules/iobroker.mihome-vacuum/lib/vacuum.js:749:16) mihome-vacuum.0 2021-04-14 19:11:39.124 error at VacuumManager.startCleaning (/opt/iobroker/node_modules/iobroker.mihome-vacuum/lib/vacuum.js:1201:37) mihome-vacuum.0 2021-04-14 19:11:39.124 error (27284) TypeError: Cannot read property 'channels' of null mihome-vacuum.0 2021-04-14 19:11:39.120 error (27284) unhandled promise rejection: Cannot read property 'channels' of null mihome-vacuum.0 2021-04-14 19:11:39.119 error (27284) 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().gewartet...30 Sekunden, dann erst Pause, dann Home ging. Kann auch Zufall sein...
Unter MAP hab ich aber nen IMG erhalten :)
NACHTRAG:
das hatte ich vorher auf jeden Fall nicht O.omihome-vacuum.0 2021-04-14 21:01:35.255 warn (28226) answer map_slot is currently not supported! mihome-vacuum.0 2021-04-14 21:01:15.214 warn (28226) answer map_slot is currently not supported! mihome-vacuum.0 2021-04-14 21:00:55.161 warn (28226) answer map_slot is currently not supported! mihome-vacuum.0 2021-04-14 21:00:35.118 warn (28226) answer map_slot is currently not supported! mihome-vacuum.0 2021-04-14 21:00:15.077 warn (28226) answer map_slot is currently not supported! mihome-vacuum.0 2021-04-14 20:59:55.026 warn (28226) answer map_slot is currently not supported! mihome-vacuum.0 2021-04-14 20:59:34.976 warn (28226) answer map_slot is currently not supported! mihome-vacuum.0 2021-04-14 20:59:14.934 warn (28226) answer map_slot is currently not supported! mihome-vacuum.0 2021-04-14 20:58:54.877 warn (28226) answer map_slot is currently not supported! mihome-vacuum.0 2021-04-14 20:58:34.832 warn (28226) answer map_slot is currently not supported! mihome-vacuum.0 2021-04-14 20:58:14.792 warn (28226) answer map_slot is currently not supported! mihome-vacuum.0 2021-04-14 20:57:54.746 warn (28226) answer map_slot is currently not supported! mihome-vacuum.0 2021-04-14 20:57:34.694 warn (28226) answer map_slot is currently not supported! mihome-vacuum.0 2021-04-14 20:57:14.647 warn (28226) answer map_slot is currently not supported! mihome-vacuum.0 2021-04-14 20:56:54.605 warn (28226) answer map_slot is currently not supported! mihome-vacuum.0 2021-04-14 20:56:34.565 warn (28226) answer map_slot is currently not supported! mihome-vacuum.0 2021-04-14 20:56:14.515 warn (28226) answer map_slot is currently not supported! mihome-vacuum.0 2021-04-14 20:55:54.461 warn (28226) answer map_slot is currently not supported! mihome-vacuum.0 2021-04-14 20:55:34.422 warn (28226) answer map_slot is currently not supported! mihome-vacuum.0 2021-04-14 20:55:14.372 warn (28226) answer map_slot is currently not supported! mihome-vacuum.0 2021-04-14 20:54:54.330 warn (28226) answer map_slot is currently not supported! mihome-vacuum.0 2021-04-14 20:54:34.282 warn (28226) answer map_slot is currently not supported! mihome-vacuum.0 2021-04-14 20:54:14.234 warn (28226) answer map_slot is currently not supported! mihome-vacuum.0 2021-04-14 20:53:54.186 warn (28226) answer map_slot is currently not supported! mihome-vacuum.0 2021-04-14 20:53:34.132 warn (28226) answer map_slot is currently not supported! mihome-vacuum.0 2021-04-14 20:53:14.088 warn (28226) answer map_slot is currently not supported! mihome-vacuum.0 2021-04-14 20:52:54.036 warn (28226) answer map_slot is currently not supported! mihome-vacuum.0 2021-04-14 20:52:33.990 warn (28226) answer map_slot is currently not supported! mihome-vacuum.0 2021-04-14 20:52:13.947 warn (28226) answer map_slot is currently not supported! mihome-vacuum.0 2021-04-14 20:51:53.888 warn (28226) answer map_slot is currently not supported! mihome-vacuum.0 2021-04-14 20:51:33.847 warn (28226) answer map_slot is currently not supported! mihome-vacuum.0 2021-04-14 20:51:13.803 warn (28226) answer map_slot is currently not supported! mihome-vacuum.0 2021-04-14 20:50:53.760 warn (28226) answer map_slot is currently not supported! mihome-vacuum.0 2021-04-14 20:50:33.712 warn (28226) answer map_slot is currently not supported! mihome-vacuum.0 2021-04-14 20:50:13.668 warn (28226) answer map_slot is currently not supported! mihome-vacuum.0 2021-04-14 20:49:53.616 warn (28226) answer map_slot is currently not supported! mihome-vacuum.0 2021-04-14 20:49:33.573 warn (28226) answer map_slot is currently not supported! mihome-vacuum.0 2021-04-14 20:49:13.523 warn (28226) answer map_slot is currently not supported! mihome-vacuum.0 2021-04-14 20:48:53.482 warn (28226) answer map_slot is currently not supported! mihome-vacuum.0 2021-04-14 20:48:33.439 warn (28226) answer map_slot is currently not supported! mihome-vacuum.0 2021-04-14 20:48:13.392 warn (28226) answer map_slot is currently not supported! mihome-vacuum.0 2021-04-14 20:47:53.343 warn (28226) answer map_slot is currently not supported! mihome-vacuum.0 2021-04-14 20:47:33.296 warn (28226) answer map_slot is currently not supported! mihome-vacuum.0 2021-04-14 20:47:13.241 warn (28226) answer map_slot is currently not supported! mihome-vacuum.0 2021-04-14 20:46:53.188 warn (28226) answer map_slot is currently not supported! mihome-vacuum.0 2021-04-14 20:46:33.142 warn (28226) answer map_slot is currently not supported! mihome-vacuum.0 2021-04-14 20:46:13.087 warn (28226) answer map_slot is currently not supported! mihome-vacuum.0 2021-04-14 20:45:20.722 warn (28226) answer map_slot is currently not supported! mihome-vacuum.0 2021-04-14 20:45:00.670 warn (28226) answer map_slot is currently not supported! mihome-vacuum.0 2021-04-14 20:44:40.551 warn (28226) answer map_slot is currently not supported! mihome-vacuum.0 2021-04-14 20:44:20.431 warn (28226) answer map_slot is currently not supported! mihome-vacuum.0 2021-04-14 20:44:00.377 warn (28226) answer map_slot is currently not supported! mihome-vacuum.0 2021-04-14 20:43:40.326 warn (28226) answer map_slot is currently not supported! mihome-vacuum.0 2021-04-14 20:43:20.195 warn (28226) answer map_slot is currently not supported! mihome-vacuum.0 2021-04-14 20:43:00.136 warn (28226) answer map_slot is currently not supported! mihome-vacuum.0 2021-04-14 20:42:40.074 warn (28226) answer map_slot is currently not supported! mihome-vacuum.0 2021-04-14 20:42:19.941 warn (28226) answer map_slot is currently not supported! mihome-vacuum.0 2021-04-14 20:41:59.898 warn (28226) answer map_slot is currently not supported! mihome-vacuum.0 2021-04-14 20:41:39.843 warn (28226) answer map_slot is currently not supported! mihome-vacuum.0 2021-04-14 20:41:19.708 warn (28226) answer map_slot is currently not supported! mihome-vacuum.0 2021-04-14 20:40:59.651 warn (28226) answer map_slot is currently not supported! mihome-vacuum.0 2021-04-14 20:40:39.603 warn (28226) answer map_slot is currently not supported! mihome-vacuum.0 2021-04-14 20:40:19.522 warn (28226) answer map_slot is currently not supported! mihome-vacuum.0 2021-04-14 20:39:59.480 warn (28226) answer map_slot is currently not supported! mihome-vacuum.0 2021-04-14 20:39:39.433 warn (28226) answer map_slot is currently not supported! mihome-vacuum.0 2021-04-14 20:39:19.297 warn (28226) answer map_slot is currently not supported! mihome-vacuum.0 2021-04-14 20:38:59.251 warn (28226) answer map_slot is currently not supported! mihome-vacuum.0 2021-04-14 20:38:39.213 warn (28226) answer map_slot is currently not supported! mihome-vacuum.0 2021-04-14 20:38:19.070 warn (28226) answer map_slot is currently not supported! mihome-vacuum.0 2021-04-14 20:37:59.023 warn (28226) answer map_slot is currently not supported! mihome-vacuum.0 2021-04-14 20:37:38.984 warn (28226) answer map_slot is currently not supported! mihome-vacuum.0 2021-04-14 20:37:18.712 warn (28226) answer map_slot is currently not supported! mihome-vacuum.0 2021-04-14 20:36:58.673 warn (28226) answer map_slot is currently not supported! mihome-vacuum.0 2021-04-14 20:36:38.634 warn (28226) answer map_slot is currently not supported! mihome-vacuum.0 2021-04-14 20:36:18.595 warn (28226) answer map_slot is currently not supported! mihome-vacuum.0 2021-04-14 20:35:58.556 warn (28226) answer map_slot is currently not supported! mihome-vacuum.0 2021-04-14 20:35:38.508 warn (28226) answer map_slot is currently not supported! mihome-vacuum.0 2021-04-14 20:35:18.362 warn (28226) answer map_slot is currently not supported! mihome-vacuum.0 2021-04-14 20:34:58.316 warn (28226) answer map_slot is currently not supported! mihome-vacuum.0 2021-04-14 20:34:38.259 warn (28226) answer map_slot is currently not supported! mihome-vacuum.0 2021-04-14 20:34:18.130 warn (28226) answer map_slot is currently not supported! mihome-vacuum.0 2021-04-14 20:33:58.065 warn (28226) answer map_slot is currently not supported! mihome-vacuum.0 2021-04-14 20:33:38.025 warn (28226) answer map_slot is currently not supported! mihome-vacuum.0 2021-04-14 20:33:17.874 warn (28226) answer map_slot is currently not supported! mihome-vacuum.0 2021-04-14 20:32:57.834 warn (28226) answer map_slot is currently not supported! mihome-vacuum.0 2021-04-14 20:32:37.790 warn (28226) answer map_slot is currently not supported! mihome-vacuum.0 2021-04-14 20:32:17.616 warn (28226) answer map_slot is currently not supported! mihome-vacuum.0 2021-04-14 20:31:57.576 warn (28226) answer map_slot is currently not supported! mihome-vacuum.0 2021-04-14 20:31:37.528 warn (28226) answer map_slot is currently not supported! mihome-vacuum.0 2021-04-14 20:31:17.378 warn (28226) answer map_slot is currently not supported! mihome-vacuum.0 2021-04-14 20:30:57.336 warn (28226) answer map_slot is currently not supported! mihome-vacuum.0 2021-04-14 20:30:37.294 warn (28226) answer map_slot is currently not supported! mihome-vacuum.0 2021-04-14 20:30:17.158 warn (28226) answer map_slot is currently not supported! mihome-vacuum.0 2021-04-14 20:29:57.102 warn (28226) answer map_slot is currently not supported! mihome-vacuum.0 2021-04-14 20:29:37.060 warn (28226) answer map_slot is currently not supported! mihome-vacuum.0 2021-04-14 20:29:16.925 warn (28226) answer map_slot is currently not supported! mihome-vacuum.0 2021-04-14 20:28:56.872 warn (28226) answer map_slot is currently not supported! mihome-vacuum.0 2021-04-14 20:28:36.827 warn (28226) answer map_slot is currently not supported! mihome-vacuum.0 2021-04-14 20:28:16.708 warn (28226) answer map_slot is currently not supported! mihome-vacuum.0 2021-04-14 20:27:56.661 warn (28226) answer map_slot is currently not supported! mihome-vacuum.0 2021-04-14 20:27:36.611 warn (28226) answer map_slot is currently not supported! mihome-vacuum.0 2021-04-14 20:27:16.472 warn (28226) answer map_slot is currently not supported! mihome-vacuum.0 2021-04-14 20:26:56.416 warn (28226) answer map_slot is currently not supported! mihome-vacuum.0 2021-04-14 20:26:36.363 warn (28226) answer map_slot is currently not supported! mihome-vacuum.0 2021-04-14 20:26:16.225 warn (28226) answer map_slot is currently not supported! mihome-vacuum.0 2021-04-14 20:25:56.187 warn (28226) answer map_slot is currently not supported! mihome-vacuum.0 2021-04-14 20:25:36.145 warn (28226) answer map_slot is currently not supported! mihome-vacuum.0 2021-04-14 20:25:16.013 warn (28226) answer map_slot is currently not supported! mihome-vacuum.0 2021-04-14 20:24:55.950 warn (28226) answer map_slot is currently not supported! mihome-vacuum.0 2021-04-14 20:24:35.905 warn (28226) answer map_slot is currently not supported! mihome-vacuum.0 2021-04-14 20:24:15.753 warn (28226) answer map_slot is currently not supported! mihome-vacuum.0 2021-04-14 20:23:55.702 warn (28226) answer map_slot is currently not supported! mihome-vacuum.0 2021-04-14 20:23:35.655 warn (28226) answer map_slot is currently not supported! mihome-vacuum.0 2021-04-14 20:23:15.539 warn (28226) answer map_slot is currently not supported! mihome-vacuum.0 2021-04-14 20:22:55.495 warn (28226) answer map_slot is currently not supported! mihome-vacuum.0 2021-04-14 20:22:35.448 warn (28226) answer map_slot is currently not supported! mihome-vacuum.0 2021-04-14 20:22:15.393 warn (28226) answer map_slot is currently not supported! mihome-vacuum.0 2021-04-14 20:21:55.347 warn (28226) answer map_slot is currently not supported! mihome-vacuum.0 2021-04-14 20:21:35.303 warn (28226) answer map_slot is currently not supported! mihome-vacuum.0 2021-04-14 20:21:15.260 warn (28226) answer map_slot is currently not supported! mihome-vacuum.0 2021-04-14 20:20:55.219 warn (28226) answer map_slot is currently not supported! mihome-vacuum.0 2021-04-14 20:20:35.176 warn (28226) answer map_slot is currently not supported! mihome-vacuum.0 2021-04-14 20:20:15.133 warn (28226) answer map_slot is currently not supported! mihome-vacuum.0 2021-04-14 20:19:55.074 warn (28226) answer map_slot is currently not supported! mihome-vacuum.0 2021-04-14 20:19:35.033 warn (28226) answer map_slot is currently not supported! mihome-vacuum.0 2021-04-14 20:19:14.973 warn (28226) answer map_slot is currently not supported! mihome-vacuum.0 2021-04-14 20:18:54.930 warn (28226) answer map_slot is currently not supported! mihome-vacuum.0 2021-04-14 20:18:34.870 warn (28226) answer map_slot is currently not supported! mihome-vacuum.0 2021-04-14 20:18:14.810 warn (28226) answer map_slot is currently not supported! mihome-vacuum.0 2021-04-14 20:17:54.764 warn (28226) answer map_slot is currently not supported! mihome-vacuum.0 2021-04-14 20:17:34.695 warn (28226) answer map_slot is currently not supported! mihome-vacuum.0 2021-04-14 20:17:14.613 warn (28226) answer map_slot is currently not supported! mihome-vacuum.0 2021-04-14 20:16:54.566 warn (28226) answer map_slot is currently not supported! mihome-vacuum.0 2021-04-14 20:16:34.528 warn (28226) answer map_slot is currently not supported! mihome-vacuum.0 2021-04-14 20:16:14.489 warn (28226) answer map_slot is currently not supported! mihome-vacuum.0 2021-04-14 20:15:54.442 warn (28226) answer map_slot is currently not supported! mihome-vacuum.0 2021-04-14 20:15:34.400 warn (28226) answer map_slot is currently not supported! mihome-vacuum.0 2021-04-14 20:15:14.356 warn (28226) answer map_slot is currently not supported! mihome-vacuum.0 2021-04-14 20:14:54.316 warn (28226) answer map_slot is currently not supported! mihome-vacuum.0 2021-04-14 20:14:34.271 warn (28226) answer map_slot is currently not supported! mihome-vacuum.0 2021-04-14 20:14:14.217 warn (28226) answer map_slot is currently not supported! mihome-vacuum.0 2021-04-14 20:13:54.167 warn (28226) answer map_slot is currently not supported! mihome-vacuum.0 2021-04-14 20:13:34.115 warn (28226) answer map_slot is currently not supported! mihome-vacuum.0 2021-04-14 20:13:14.073 warn (28226) answer map_slot is currently not supported! mihome-vacuum.0 2021-04-14 20:12:54.019 warn (28226) answer map_slot is currently not supported! mihome-vacuum.0 2021-04-14 20:12:33.979 warn (28226) answer map_slot is currently not supported! mihome-vacuum.0 2021-04-14 20:12:13.932 warn (28226) answer map_slot is currently not supported! mihome-vacuum.0 2021-04-14 20:11:53.887 warn (28226) answer map_slot is currently not supported! mihome-vacuum.0 2021-04-14 20:11:33.845 warn (28226) answer map_slot is currently not supported! mihome-vacuum.0 2021-04-14 20:11:13.805 warn (28226) answer map_slot is currently not supported! mihome-vacuum.0 2021-04-14 20:10:53.750 warn (28226) answer map_slot is currently not supported! mihome-vacuum.0 2021-04-14 20:10:33.702 warn (28226) answer map_slot is currently not supported! mihome-vacuum.0 2021-04-14 20:10:13.644 warn (28226) answer map_slot is currently not supported! mihome-vacuum.0 2021-04-14 20:09:53.602 warn (28226) answer map_slot is currently not supported! mihome-vacuum.0 2021-04-14 20:09:33.559 warn (28226) answer map_slot is currently not supported! mihome-vacuum.0 2021-04-14 20:09:13.515 warn (28226) answer map_slot is currently not supported! mihome-vacuum.0 2021-04-14 20:08:53.468 warn (28226) answer map_slot is currently not supported! mihome-vacuum.0 2021-04-14 20:08:33.428 warn (28226) answer map_slot is currently not supported! mihome-vacuum.0 2021-04-14 20:08:13.377 warn (28226) answer map_slot is currently not supported! mihome-vacuum.0 2021-04-14 20:07:53.327 warn (28226) answer map_slot is currently not supported! -
@meistertr hab den Vacuum V1 mit Valetudo.
Installation ohne AUffälligkeiten LOG auch ohne Auffälligkeiten. Das eine Answer Map Slot hatte ich vorher auch schon :)mihome-vacuum.0 2021-04-14 19:04:47.679 warn (18778) answer map_slot is currently not supported! mihome-vacuum.0 2021-04-14 19:04:27.601 warn (18778) answer map_slot is currently not supported! mihome-vacuum.0 2021-04-14 19:04:07.723 info (18778) settest next timer: not available mihome-vacuum.0 2021-04-14 19:04:07.498 info (18778) create state for carpet_mode mihome-vacuum.0 2021-04-14 19:04:07.482 warn (18778) answer map_slot is currently not supported! mihome-vacuum.0 2021-04-14 19:04:07.354 info (18778) Map selected create states... mihome-vacuum.0 2021-04-14 19:04:07.124 warn (18778) State "mihome-vacuum.0.deviceInfo.mac" has no existing object, this might lead to an error in future versions mihome-vacuum.0 2021-04-14 19:04:07.122 warn (18778) State "mihome-vacuum.0.deviceInfo.fw_ver" has no existing object, this might lead to an error in future versions mihome-vacuum.0 2021-04-14 19:04:07.121 warn (18778) State "mihome-vacuum.0.deviceInfo.model" has no existing object, this might lead to an error in future versionsOk, wenn ich versuche die MAP zu laden, bekomme ich auch o. g. warn-Meldung im LOG. Hab nur Valetudo bei Map aktiviert...
@meistertr Erstmal super Arbeit die du leistest.
Eine Frage, seit heute bin ich im Besitz eines ROIDMI EVE Plus, der eine Untermarke von Xiaomi ist.
Man kann diesen Sauger auch ganz normal über die MiHomeApp steuern.Daher meine Frage, kannst du diesen auch einbinden?
Wenn ja was benötigst du, um dir unter die Arme zu greifen. (Achtung Anfänger) ?Habe bereits deinen 3.0.4 Adapter installiert. Folgendes spuckt er im Debug aus:
mihome-vacuum.0 2021-04-14 19:54:03.212 debug (15781) Receive Timeout<<< mihome-vacuum.0 2021-04-14 19:54:03.111 debug (15781) Receive Timeout<<< mihome-vacuum.0 2021-04-14 19:54:03.006 debug (15781) Receive Timeout<<< mihome-vacuum.0 2021-04-14 19:54:02.904 debug (15781) Receive Timeout<<< mihome-vacuum.0 2021-04-14 19:54:02.713 debug (15781) Receive Timeout<<< mihome-vacuum.0 2021-04-14 19:54:01.317 warn (15781) Model roidmi.vacuum.v60 not supported! Please open issue on git: https://github.com/iobroker-community-adapters/ioBroker.mihome-vacuum/issues mihome-vacuum.0 2021-04-14 19:54:01.317 debug (15781) DeviceModel selected to: roidmi.vacuum.v60 mihome-vacuum.0 2021-04-14 19:54:01.316 warn (15781) No Answer for DeviceModel use model from Config mihome-vacuum.0 2021-04-14 19:54:01.316 warn (15781) No Answer for DeviceModel use old one mihome-vacuum.0 2021-04-14 19:54:01.316 warn (15781) YOUR DEVICE IS CONNECTED BUT DID NOT ANSWER CONNECTION CAN TAKE UP TO 10 MINUTES PLESASE WAIT AND DON`T TRUN THE ADAPTER OFF mihome-vacuum.0 2021-04-14 19:54:01.315 debug (15781) Get Device data..4 mihome-vacuum.0 2021-04-14 19:54:01.212 debug (15781) Message= {"id":5,"method":"miIO.info"} mihome-vacuum.0 2021-04-14 19:54:01.211 debug (15781) Get Device data..3 mihome-vacuum.0 2021-04-14 19:54:01.109 debug (15781) Message= {"id":4,"method":"miIO.info"} mihome-vacuum.0 2021-04-14 19:54:01.108 debug (15781) Get Device data..2 mihome-vacuum.0 2021-04-14 19:54:01.005 debug (15781) Message= {"id":3,"method":"miIO.info"} mihome-vacuum.0 2021-04-14 19:54:01.005 debug (15781) Get Device data..1 mihome-vacuum.0 2021-04-14 19:54:00.901 debug (15781) Message= {"id":2,"method":"miIO.info"} mihome-vacuum.0 2021-04-14 19:54:00.901 debug (15781) Get Device data..0 mihome-vacuum.0 2021-04-14 19:54:00.710 debug (15781) Message= {"id":1,"method":"miIO.info"} mihome-vacuum.0 2021-04-14 19:54:00.709 debug (15781) GETMODELFROMAPI: objModel: {"val":"roidmi.vacuum.v60","ack":true,"ts":1618422820472,"q":0,"from":"system.adapter.mihome-vacuum.0","user":"system.user.admin","lc":1618422820472} mihome-vacuum.0 2021-04-14 19:54:00.708 debug (15781) Time difference between Mihome Vacuum and ioBroker: -1618420957 sec mihome-vacuum.0 2021-04-14 19:54:00.706 debug (15781) MAIN: Connected to device, try to get model.. mihome-vacuum.0 2021-04-14 19:54:00.705 debug (15781) Receive <<< Helo <<< 2131002000000000185728150000075bffffffffffffffffffffffffffffffff mihome-vacuum.0 2021-04-14 19:54:00.647 debug (15781) server started on 0.0.0.0:53421Danke im Voraus
Gruß Blacky -
Aktuelle Test Version 3.1.6 Veröffentlichungsdatum 18.4.2021 Github Link https://github.com/iobroker-community-adapters/ioBroker.mihome-vacuum Lange hats gedauert aber langsam komm ich zum Ende (wobei das dann wahrscheinlich der Anfang ist :) ).
Was hat sich geändert? Alles und nix kann kann man sagen.
Der Adapter wurde komplett neu aufgesetzt und dem Aktuellen stand angepasst.vorher:
- Nachrichten an den Roboter wurden willkürlich geschickt und gehofft das eine Antwort kommt.
- Die Erkennung des Roboters (Modell und Marke und Firmware) wurden durch Ankommende Nachrichten oder das Ausbleiben erkannt
- comact mode nicht möglich da zig Timeouts liefen
- Keine neuen/anderen Sauger integrierbar da alles in einer Datei lag
jetzt:
- beim start wird zwingend das Modell ermittelt wonach dann die richtige Datei für den jeweiligen Sauger geladen wird
- danach werden Strukturiert die Sonderfunktionen ermittelt und freigegeben
- Nachrichten werden nicht mehr willkürlich gesendet sonders strukturiert und jede Nachricht bekommt eine Antwort
- comact mode möglich da alle timer zentral gelagert sind
ich habe mich bemüht die Objekte zum Vorgänger gleich zu lassen. also Optisch ist nicht viel neu aber wie gesagt unterm Kleid alles was man im debug log sehen sollte.
ich habe noch nicht viele Sauger in der Datenbank also kann es zu warn log einträgen kommen, dann bitte modell und bezeichnung posten dann nehm ich sie mit rein.
Bitte alles Testen da ich viel ohne Testen umgeschrieben habe (bei über 2000 Zeilen) konnte ich nicht alles direkt testen.Stand Aktuell:
Jetzt sollte alles gehen was bei der 2er auch geht. und mehrWas sollte gehen:
- alles wie beim alten außer die map (folgt in kürze)
- viomi Modelle die sonst über meinen Fork liefen sind nun mit drin
- support für den S7 (letztes update hat die History kaputt gemacht)
- Map wir unterstützt
Fixes:
- Map bei zwei Saugern funtionieren
- Map wird zuverlässig(er) geladen
- 3.0.2 Manueller Map Reload Button funktionert
- 3.0.4/ 3.0.7 Timer geht wieder
- 3.0.5 Disable map_slot warning, add start button, fix error while sending messages without selected device, fix water_box value
- 3.0.6 fix queue States, fix cleaning Buttons.
- 3.0.8 fix map for Valetudo
- 3.1.0 aktuelle Goto und Zones werden gespeichert
- 3.1.1 fix queue
- 3.1.3 Map bugfix, add Multimap Support
- 3.1.3 fix missing Wifi Signal
- 3.1.4 Fix Connrection after reboot/ now wifi
3.1.6: - fixed Disk I/O
- added get States when map is changed
- minimize Messages
- changed logentrys from warn to debug
- added Donate button
folgt in Kürze:
- Koordinaten von goto und Zonen werden angezeigt (in den jeweiligen states)- dreame support über miot
- compactmode
- map - map für history
- material tabel
- led Status S7
neues Logo- Doku aufbereiten
Installieren bitte über https://github.com/iobroker-community-adapters/ioBroker.mihome-vacuum (einfach von git)
Bitte Vorher den alten Adapter vollständig löschen.
Dies ist die Alpha also BITTE nur installieren wenn ihr wisst was ihr macht und einen qualifizierten Bugreport liefern könnt
Bitte in dieses Thema NUR Fehler oder Requests die den Adapter betreffen. KEINE Installationsfehler oder sonstige Fragen. macht dafür bitte wenn die Suche nichts ergeben hat ein neues Thema auf damit es hier nicht so überläuft wie in den alten Threads..
@meistertr Roborock S6 Pure :+1:
-
@meistertr Erstmal super Arbeit die du leistest.
Eine Frage, seit heute bin ich im Besitz eines ROIDMI EVE Plus, der eine Untermarke von Xiaomi ist.
Man kann diesen Sauger auch ganz normal über die MiHomeApp steuern.Daher meine Frage, kannst du diesen auch einbinden?
Wenn ja was benötigst du, um dir unter die Arme zu greifen. (Achtung Anfänger) ?Habe bereits deinen 3.0.4 Adapter installiert. Folgendes spuckt er im Debug aus:
mihome-vacuum.0 2021-04-14 19:54:03.212 debug (15781) Receive Timeout<<< mihome-vacuum.0 2021-04-14 19:54:03.111 debug (15781) Receive Timeout<<< mihome-vacuum.0 2021-04-14 19:54:03.006 debug (15781) Receive Timeout<<< mihome-vacuum.0 2021-04-14 19:54:02.904 debug (15781) Receive Timeout<<< mihome-vacuum.0 2021-04-14 19:54:02.713 debug (15781) Receive Timeout<<< mihome-vacuum.0 2021-04-14 19:54:01.317 warn (15781) Model roidmi.vacuum.v60 not supported! Please open issue on git: https://github.com/iobroker-community-adapters/ioBroker.mihome-vacuum/issues mihome-vacuum.0 2021-04-14 19:54:01.317 debug (15781) DeviceModel selected to: roidmi.vacuum.v60 mihome-vacuum.0 2021-04-14 19:54:01.316 warn (15781) No Answer for DeviceModel use model from Config mihome-vacuum.0 2021-04-14 19:54:01.316 warn (15781) No Answer for DeviceModel use old one mihome-vacuum.0 2021-04-14 19:54:01.316 warn (15781) YOUR DEVICE IS CONNECTED BUT DID NOT ANSWER CONNECTION CAN TAKE UP TO 10 MINUTES PLESASE WAIT AND DON`T TRUN THE ADAPTER OFF mihome-vacuum.0 2021-04-14 19:54:01.315 debug (15781) Get Device data..4 mihome-vacuum.0 2021-04-14 19:54:01.212 debug (15781) Message= {"id":5,"method":"miIO.info"} mihome-vacuum.0 2021-04-14 19:54:01.211 debug (15781) Get Device data..3 mihome-vacuum.0 2021-04-14 19:54:01.109 debug (15781) Message= {"id":4,"method":"miIO.info"} mihome-vacuum.0 2021-04-14 19:54:01.108 debug (15781) Get Device data..2 mihome-vacuum.0 2021-04-14 19:54:01.005 debug (15781) Message= {"id":3,"method":"miIO.info"} mihome-vacuum.0 2021-04-14 19:54:01.005 debug (15781) Get Device data..1 mihome-vacuum.0 2021-04-14 19:54:00.901 debug (15781) Message= {"id":2,"method":"miIO.info"} mihome-vacuum.0 2021-04-14 19:54:00.901 debug (15781) Get Device data..0 mihome-vacuum.0 2021-04-14 19:54:00.710 debug (15781) Message= {"id":1,"method":"miIO.info"} mihome-vacuum.0 2021-04-14 19:54:00.709 debug (15781) GETMODELFROMAPI: objModel: {"val":"roidmi.vacuum.v60","ack":true,"ts":1618422820472,"q":0,"from":"system.adapter.mihome-vacuum.0","user":"system.user.admin","lc":1618422820472} mihome-vacuum.0 2021-04-14 19:54:00.708 debug (15781) Time difference between Mihome Vacuum and ioBroker: -1618420957 sec mihome-vacuum.0 2021-04-14 19:54:00.706 debug (15781) MAIN: Connected to device, try to get model.. mihome-vacuum.0 2021-04-14 19:54:00.705 debug (15781) Receive <<< Helo <<< 2131002000000000185728150000075bffffffffffffffffffffffffffffffff mihome-vacuum.0 2021-04-14 19:54:00.647 debug (15781) server started on 0.0.0.0:53421Danke im Voraus
Gruß BlackyHabe den Adapter auch mal installiert und beteilige mich gern an dem Test.
Roborock S6 maxv
@IOBroker:~# npm -v
6.14.4
@IOBroker:~# nodejs -v
v14.16.0Installation / Log (Ohne Auffälligkeiten):
mihome-vacuum.0 2021-04-14 20:47:55.027 info (8004) create new room: 644001017629 mihome-vacuum.0 2021-04-14 20:47:55.027 info (8004) create new room: 644001017632 mihome-vacuum.0 2021-04-14 20:47:55.026 info (8004) create new room: 644001016932 mihome-vacuum.0 2021-04-14 20:47:55.021 info (8004) create new room: 644001016935 mihome-vacuum.0 2021-04-14 20:47:55.020 info (8004) create new room: 644001016934 mihome-vacuum.0 2021-04-14 20:47:55.020 info (8004) create new room: 644001016916 mihome-vacuum.0 2021-04-14 20:47:55.019 info (8004) create new room: 644001016933 mihome-vacuum.0 2021-04-14 20:47:54.951 info (8004) create state for carpet_mode mihome-vacuum.0 2021-04-14 20:47:53.572 info (8004) create states for water box mode mihome-vacuum.0 2021-04-14 20:47:53.566 info (8004) settest next timer: not available mihome-vacuum.0 2021-04-14 20:47:53.548 info (8004) create states for water box mihome-vacuum.0 2021-04-14 20:47:53.525 info (8004) change states from State control.fan_power mihome-vacuum.0 2021-04-14 20:47:53.410 info (8004) Map not selected delete states... mihome-vacuum.0 2021-04-14 20:47:53.027 info (8004) select standard vacuum protocol.... mihome-vacuum.0 2021-04-14 20:47:50.885 info (8004) check group user admin group admin: false mihome-vacuum.0 2021-04-14 20:47:50.529 info (8004) check user admin pw iobroker: false mihome-vacuum.0 2021-04-14 20:47:50.053 info (8004) starting. Version 3.0.3 in /opt/iobroker/node_modules/iobroker.mihome-vacuum, node: v14.16.0, js-controller: 3.2.16 host.IOBroker 2021-04-14 20:47:48.376 info instance system.adapter.mihome-vacuum.0 started with pid 8004 host.IOBroker 2021-04-14 20:47:45.773 info instance system.adapter.mihome-vacuum.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION) host.IOBroker 2021-04-14 20:47:45.255 info stopInstance system.adapter.mihome-vacuum.0 send kill signal mihome-vacuum.0 2021-04-14 20:47:45.211 info (7989) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason mihome-vacuum.0 2021-04-14 20:47:45.211 info (7989) terminating mihome-vacuum.0 2021-04-14 20:47:45.209 info (7989) Got terminate signal TERMINATE_YOURSELF host.IOBroker 2021-04-14 20:47:45.205 info stopInstance system.adapter.mihome-vacuum.0 (force=false, process=true)Dann die MAP aktiviert (Adapter bleibt "Gelb", aber das dauert ja):
mihome-vacuum.0 2021-04-14 20:53:11.786 info (8037) Map selected create states... mihome-vacuum.0 2021-04-14 20:53:10.357 info (8037) settest next timer: not available mihome-vacuum.0 2021-04-14 20:53:09.817 info (8037) select standard vacuum protocol.... mihome-vacuum.0 2021-04-14 20:53:09.815 warn (8037) No Answer for DeviceModel use model from Config mihome-vacuum.0 2021-04-14 20:53:09.815 warn (8037) No Answer for DeviceModel use old one mihome-vacuum.0 2021-04-14 20:53:09.814 warn (8037) YOUR DEVICE IS CONNECTED BUT DID NOT ANSWER CONNECTION CAN TAKE UP TO 10 MINUTES PLESASE WAIT AND DON`T TRUN THE ADAPTER OFFUpdate dann noch wenn ich sehe ob der Adapter "Grün" wird und die Map verfügbar ist.
Alle anderen Datenpunkte sehen gut aus, ich glaube das Wifi Signal zieht er aktuell nicht mehr.
Vielen Dank für den Adapter ;)
Update: Adapter "GRÜN" Karte wurde geladen. Wenn die sich nun auch aktualisiert ist alles roger!
Update1:
Der Datenpunkt für den Wassertank war vorher true / false und scheint nun vermutlich 0/1 zu sein.
-
Habe einen alten Beitrag von dir gefunden Meister, deshalb habe ich mal etwas gesucht.
Folgende Urls habe ich schon einmal gefunden:# http://miot-spec.org/miot-spec-v2/instance?type=urn:miot-spec-v2:device:vacuum:0000A006:roidmi-v60:1gibt auch noch mit :2
# http://miot-spec.org/miot-spec-v2/instance?type=urn:miot-spec-v2:device:vacuum:0000A006:roidmi-v60:2Des Weiteren habe ich dann mal die alten Befehle genutzt, die vermutlich hier nicht passen werden.
Bitte hier um Berichtigung und evtl. um ein/zwei Beispiele, dann setze ich die Befehle anders um:"battery": {"siid": 3, "piid": 1}, [{"code":0,"did":"408365077","piid":1,"siid":3,"value":100}] "charge_state": {"siid": 3, "piid": 2}, [{"code":0,"did":"408365077","piid":2,"siid":3,"value":1}] "error": {"siid": 2, "piid": 2}, [{"code":0,"did":"408365077","piid":2,"siid":2,"value":0}] "state": {"siid": 2, "piid": 1}, [{"code":0,"did":"408365077","piid":1,"siid":2,"value":9}] "fan_speed": {"siid": 2, "piid": 6}, [{"code":-4003,"did":"408365077","piid":6,"siid":2}] "operating_mode": {"siid": 2, "piid": 4}, [{"code":0,"did":"408365077","piid":4,"siid":2,"value":2}] "mop_state": {"siid": 16, "piid": 1}, [{"did":"408365077","piid":1,"siid":16}] "water_level": {"siid": 2, "piid": 5}, [{"code":-4003,"did":"408365077","piid":5,"siid":2}] "brush_life_level": {"siid": 14, "piid": 1}, [{"code":0,"did":"408365077","piid":1,"siid":14,"value":0}] # "brush_life_time": {"siid": 14, "piid": 2}, [{"code":-4003,"did":"408365077","piid":2,"siid":14}] "brush_life_level2": {"siid": 15, "piid": 1}, [{"code":0,"did":"408365077","piid":1,"siid":15,"value":1722}] # "brush_life_time2": {"siid": 15, "piid": 2}, [{"code":0,"did":"408365077","piid":2,"siid":15,"value":95}] "filter_life_level": {"siid": 11, "piid": 1}, [{"code":0,"did":"408365077","piid":1,"siid":11,"value":17922}] # "filter_life_time": {"siid": 11, "piid": 2}, [{"code":0,"did":"408365077","piid":2,"siid":11,"value":99}] "clean_area": {"siid": 9, "piid": 1}, [{"code":0,"did":"408365077","piid":1,"siid":9,"value":40}] "clean_time": {"siid": 18, "piid": 5}, [{"did":"408365077","piid":5,"siid":18}] "total_clean_count": {"siid": 9, "piid": 5}, [{"code":-4003,"did":"408365077","piid":5,"siid":9}] # "total_clean_area": {"siid": 9, "piid": 3}, [{"code":-4003,"did":"408365077","piid":3,"siid":9}] # "dnd_enabled": {"siid": 12, "piid": 2}, [{"code":0,"did":"408365077","piid":2,"siid":12,"value":99}] # "audio_volume": {"siid": 4, "piid": 2}, [{"did":"408365077","piid":2,"siid":4}] # "direction_key": {"siid": 8, "piid": 1} [{"code":0,"did":"408365077","piid":1,"siid":8,"value":0}]Folgende Fehlermeldung kommt wenn ich die Befehle ausgeführt habe:
host.iobroker 2021-04-14 21:11:04.084 info instance system.adapter.mihome-vacuum.0 started with pid 1074 host.iobroker 2021-04-14 21:10:34.061 info Restart adapter system.adapter.mihome-vacuum.0 because enabled host.iobroker 2021-04-14 21:10:34.061 error instance system.adapter.mihome-vacuum.0 terminated with code 6 (UNCAUGHT_EXCEPTION) mihome-vacuum.0 2021-04-14 21:10:33.381 warn (32537) Terminated (UNCAUGHT_EXCEPTION): Without reason mihome-vacuum.0 2021-04-14 21:10:33.380 info (32537) terminating mihome-vacuum.0 2021-04-14 21:10:33.368 error (32537) Cannot read property 'stateChange' of null mihome-vacuum.0 2021-04-14 21:10:33.367 error (32537) TypeError: Cannot read property 'stateChange' of null at MihomeVacuum.onStateChange (/opt/iobroker/node_modules/iobroker.mihome-vacuum/main.js:316:10) at process._tickCallback (interna mihome-vacuum.0 2021-04-14 21:10:33.367 error (32537) unhandled promise rejection: Cannot read property 'stateChange' of null mihome-vacuum.0 2021-04-14 21:10:33.367 error (32537) 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-04-14 21:10:33.366 debug (32537) Get self send data:{"id":6,"result":[{"code":0,"did":"408365077","piid":1,"siid":8,"value":0}]} mihome-vacuum.0 2021-04-14 21:10:33.366 debug (32537) MIIO RECIVE: {"id":6,"result":[{"code":0,"did":"408365077","piid":1,"siid":8,"value":0}]} mihome-vacuum.0 2021-04-14 21:10:33.099 debug (32537) Message= {"id":6,"method":"get_properties","params":[{"did":"408365077","siid":8,"piid":1}]} mihome-vacuum.0 2021-04-14 21:10:33.099 info (32537) send message: Method: get_properties Params: [{"did":"408365077","siid":8,"piid":1}]Gruß
Blacky -
Habe einen alten Beitrag von dir gefunden Meister, deshalb habe ich mal etwas gesucht.
Folgende Urls habe ich schon einmal gefunden:# http://miot-spec.org/miot-spec-v2/instance?type=urn:miot-spec-v2:device:vacuum:0000A006:roidmi-v60:1gibt auch noch mit :2
# http://miot-spec.org/miot-spec-v2/instance?type=urn:miot-spec-v2:device:vacuum:0000A006:roidmi-v60:2Des Weiteren habe ich dann mal die alten Befehle genutzt, die vermutlich hier nicht passen werden.
Bitte hier um Berichtigung und evtl. um ein/zwei Beispiele, dann setze ich die Befehle anders um:"battery": {"siid": 3, "piid": 1}, [{"code":0,"did":"408365077","piid":1,"siid":3,"value":100}] "charge_state": {"siid": 3, "piid": 2}, [{"code":0,"did":"408365077","piid":2,"siid":3,"value":1}] "error": {"siid": 2, "piid": 2}, [{"code":0,"did":"408365077","piid":2,"siid":2,"value":0}] "state": {"siid": 2, "piid": 1}, [{"code":0,"did":"408365077","piid":1,"siid":2,"value":9}] "fan_speed": {"siid": 2, "piid": 6}, [{"code":-4003,"did":"408365077","piid":6,"siid":2}] "operating_mode": {"siid": 2, "piid": 4}, [{"code":0,"did":"408365077","piid":4,"siid":2,"value":2}] "mop_state": {"siid": 16, "piid": 1}, [{"did":"408365077","piid":1,"siid":16}] "water_level": {"siid": 2, "piid": 5}, [{"code":-4003,"did":"408365077","piid":5,"siid":2}] "brush_life_level": {"siid": 14, "piid": 1}, [{"code":0,"did":"408365077","piid":1,"siid":14,"value":0}] # "brush_life_time": {"siid": 14, "piid": 2}, [{"code":-4003,"did":"408365077","piid":2,"siid":14}] "brush_life_level2": {"siid": 15, "piid": 1}, [{"code":0,"did":"408365077","piid":1,"siid":15,"value":1722}] # "brush_life_time2": {"siid": 15, "piid": 2}, [{"code":0,"did":"408365077","piid":2,"siid":15,"value":95}] "filter_life_level": {"siid": 11, "piid": 1}, [{"code":0,"did":"408365077","piid":1,"siid":11,"value":17922}] # "filter_life_time": {"siid": 11, "piid": 2}, [{"code":0,"did":"408365077","piid":2,"siid":11,"value":99}] "clean_area": {"siid": 9, "piid": 1}, [{"code":0,"did":"408365077","piid":1,"siid":9,"value":40}] "clean_time": {"siid": 18, "piid": 5}, [{"did":"408365077","piid":5,"siid":18}] "total_clean_count": {"siid": 9, "piid": 5}, [{"code":-4003,"did":"408365077","piid":5,"siid":9}] # "total_clean_area": {"siid": 9, "piid": 3}, [{"code":-4003,"did":"408365077","piid":3,"siid":9}] # "dnd_enabled": {"siid": 12, "piid": 2}, [{"code":0,"did":"408365077","piid":2,"siid":12,"value":99}] # "audio_volume": {"siid": 4, "piid": 2}, [{"did":"408365077","piid":2,"siid":4}] # "direction_key": {"siid": 8, "piid": 1} [{"code":0,"did":"408365077","piid":1,"siid":8,"value":0}]Folgende Fehlermeldung kommt wenn ich die Befehle ausgeführt habe:
host.iobroker 2021-04-14 21:11:04.084 info instance system.adapter.mihome-vacuum.0 started with pid 1074 host.iobroker 2021-04-14 21:10:34.061 info Restart adapter system.adapter.mihome-vacuum.0 because enabled host.iobroker 2021-04-14 21:10:34.061 error instance system.adapter.mihome-vacuum.0 terminated with code 6 (UNCAUGHT_EXCEPTION) mihome-vacuum.0 2021-04-14 21:10:33.381 warn (32537) Terminated (UNCAUGHT_EXCEPTION): Without reason mihome-vacuum.0 2021-04-14 21:10:33.380 info (32537) terminating mihome-vacuum.0 2021-04-14 21:10:33.368 error (32537) Cannot read property 'stateChange' of null mihome-vacuum.0 2021-04-14 21:10:33.367 error (32537) TypeError: Cannot read property 'stateChange' of null at MihomeVacuum.onStateChange (/opt/iobroker/node_modules/iobroker.mihome-vacuum/main.js:316:10) at process._tickCallback (interna mihome-vacuum.0 2021-04-14 21:10:33.367 error (32537) unhandled promise rejection: Cannot read property 'stateChange' of null mihome-vacuum.0 2021-04-14 21:10:33.367 error (32537) 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-04-14 21:10:33.366 debug (32537) Get self send data:{"id":6,"result":[{"code":0,"did":"408365077","piid":1,"siid":8,"value":0}]} mihome-vacuum.0 2021-04-14 21:10:33.366 debug (32537) MIIO RECIVE: {"id":6,"result":[{"code":0,"did":"408365077","piid":1,"siid":8,"value":0}]} mihome-vacuum.0 2021-04-14 21:10:33.099 debug (32537) Message= {"id":6,"method":"get_properties","params":[{"did":"408365077","siid":8,"piid":1}]} mihome-vacuum.0 2021-04-14 21:10:33.099 info (32537) send message: Method: get_properties Params: [{"did":"408365077","siid":8,"piid":1}]Gruß
Blacky -
Habe den Adapter auch mal installiert und beteilige mich gern an dem Test.
Roborock S6 maxv
@IOBroker:~# npm -v
6.14.4
@IOBroker:~# nodejs -v
v14.16.0Installation / Log (Ohne Auffälligkeiten):
mihome-vacuum.0 2021-04-14 20:47:55.027 info (8004) create new room: 644001017629 mihome-vacuum.0 2021-04-14 20:47:55.027 info (8004) create new room: 644001017632 mihome-vacuum.0 2021-04-14 20:47:55.026 info (8004) create new room: 644001016932 mihome-vacuum.0 2021-04-14 20:47:55.021 info (8004) create new room: 644001016935 mihome-vacuum.0 2021-04-14 20:47:55.020 info (8004) create new room: 644001016934 mihome-vacuum.0 2021-04-14 20:47:55.020 info (8004) create new room: 644001016916 mihome-vacuum.0 2021-04-14 20:47:55.019 info (8004) create new room: 644001016933 mihome-vacuum.0 2021-04-14 20:47:54.951 info (8004) create state for carpet_mode mihome-vacuum.0 2021-04-14 20:47:53.572 info (8004) create states for water box mode mihome-vacuum.0 2021-04-14 20:47:53.566 info (8004) settest next timer: not available mihome-vacuum.0 2021-04-14 20:47:53.548 info (8004) create states for water box mihome-vacuum.0 2021-04-14 20:47:53.525 info (8004) change states from State control.fan_power mihome-vacuum.0 2021-04-14 20:47:53.410 info (8004) Map not selected delete states... mihome-vacuum.0 2021-04-14 20:47:53.027 info (8004) select standard vacuum protocol.... mihome-vacuum.0 2021-04-14 20:47:50.885 info (8004) check group user admin group admin: false mihome-vacuum.0 2021-04-14 20:47:50.529 info (8004) check user admin pw iobroker: false mihome-vacuum.0 2021-04-14 20:47:50.053 info (8004) starting. Version 3.0.3 in /opt/iobroker/node_modules/iobroker.mihome-vacuum, node: v14.16.0, js-controller: 3.2.16 host.IOBroker 2021-04-14 20:47:48.376 info instance system.adapter.mihome-vacuum.0 started with pid 8004 host.IOBroker 2021-04-14 20:47:45.773 info instance system.adapter.mihome-vacuum.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION) host.IOBroker 2021-04-14 20:47:45.255 info stopInstance system.adapter.mihome-vacuum.0 send kill signal mihome-vacuum.0 2021-04-14 20:47:45.211 info (7989) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason mihome-vacuum.0 2021-04-14 20:47:45.211 info (7989) terminating mihome-vacuum.0 2021-04-14 20:47:45.209 info (7989) Got terminate signal TERMINATE_YOURSELF host.IOBroker 2021-04-14 20:47:45.205 info stopInstance system.adapter.mihome-vacuum.0 (force=false, process=true)Dann die MAP aktiviert (Adapter bleibt "Gelb", aber das dauert ja):
mihome-vacuum.0 2021-04-14 20:53:11.786 info (8037) Map selected create states... mihome-vacuum.0 2021-04-14 20:53:10.357 info (8037) settest next timer: not available mihome-vacuum.0 2021-04-14 20:53:09.817 info (8037) select standard vacuum protocol.... mihome-vacuum.0 2021-04-14 20:53:09.815 warn (8037) No Answer for DeviceModel use model from Config mihome-vacuum.0 2021-04-14 20:53:09.815 warn (8037) No Answer for DeviceModel use old one mihome-vacuum.0 2021-04-14 20:53:09.814 warn (8037) YOUR DEVICE IS CONNECTED BUT DID NOT ANSWER CONNECTION CAN TAKE UP TO 10 MINUTES PLESASE WAIT AND DON`T TRUN THE ADAPTER OFFUpdate dann noch wenn ich sehe ob der Adapter "Grün" wird und die Map verfügbar ist.
Alle anderen Datenpunkte sehen gut aus, ich glaube das Wifi Signal zieht er aktuell nicht mehr.
Vielen Dank für den Adapter ;)
Update: Adapter "GRÜN" Karte wurde geladen. Wenn die sich nun auch aktualisiert ist alles roger!
Update1:
Der Datenpunkt für den Wassertank war vorher true / false und scheint nun vermutlich 0/1 zu sein.
-
Aktuelle Test Version 3.1.6 Veröffentlichungsdatum 18.4.2021 Github Link https://github.com/iobroker-community-adapters/ioBroker.mihome-vacuum Lange hats gedauert aber langsam komm ich zum Ende (wobei das dann wahrscheinlich der Anfang ist :) ).
Was hat sich geändert? Alles und nix kann kann man sagen.
Der Adapter wurde komplett neu aufgesetzt und dem Aktuellen stand angepasst.vorher:
- Nachrichten an den Roboter wurden willkürlich geschickt und gehofft das eine Antwort kommt.
- Die Erkennung des Roboters (Modell und Marke und Firmware) wurden durch Ankommende Nachrichten oder das Ausbleiben erkannt
- comact mode nicht möglich da zig Timeouts liefen
- Keine neuen/anderen Sauger integrierbar da alles in einer Datei lag
jetzt:
- beim start wird zwingend das Modell ermittelt wonach dann die richtige Datei für den jeweiligen Sauger geladen wird
- danach werden Strukturiert die Sonderfunktionen ermittelt und freigegeben
- Nachrichten werden nicht mehr willkürlich gesendet sonders strukturiert und jede Nachricht bekommt eine Antwort
- comact mode möglich da alle timer zentral gelagert sind
ich habe mich bemüht die Objekte zum Vorgänger gleich zu lassen. also Optisch ist nicht viel neu aber wie gesagt unterm Kleid alles was man im debug log sehen sollte.
ich habe noch nicht viele Sauger in der Datenbank also kann es zu warn log einträgen kommen, dann bitte modell und bezeichnung posten dann nehm ich sie mit rein.
Bitte alles Testen da ich viel ohne Testen umgeschrieben habe (bei über 2000 Zeilen) konnte ich nicht alles direkt testen.Stand Aktuell:
Jetzt sollte alles gehen was bei der 2er auch geht. und mehrWas sollte gehen:
- alles wie beim alten außer die map (folgt in kürze)
- viomi Modelle die sonst über meinen Fork liefen sind nun mit drin
- support für den S7 (letztes update hat die History kaputt gemacht)
- Map wir unterstützt
Fixes:
- Map bei zwei Saugern funtionieren
- Map wird zuverlässig(er) geladen
- 3.0.2 Manueller Map Reload Button funktionert
- 3.0.4/ 3.0.7 Timer geht wieder
- 3.0.5 Disable map_slot warning, add start button, fix error while sending messages without selected device, fix water_box value
- 3.0.6 fix queue States, fix cleaning Buttons.
- 3.0.8 fix map for Valetudo
- 3.1.0 aktuelle Goto und Zones werden gespeichert
- 3.1.1 fix queue
- 3.1.3 Map bugfix, add Multimap Support
- 3.1.3 fix missing Wifi Signal
- 3.1.4 Fix Connrection after reboot/ now wifi
3.1.6: - fixed Disk I/O
- added get States when map is changed
- minimize Messages
- changed logentrys from warn to debug
- added Donate button
folgt in Kürze:
- Koordinaten von goto und Zonen werden angezeigt (in den jeweiligen states)- dreame support über miot
- compactmode
- map - map für history
- material tabel
- led Status S7
neues Logo- Doku aufbereiten
Installieren bitte über https://github.com/iobroker-community-adapters/ioBroker.mihome-vacuum (einfach von git)
Bitte Vorher den alten Adapter vollständig löschen.
Dies ist die Alpha also BITTE nur installieren wenn ihr wisst was ihr macht und einen qualifizierten Bugreport liefern könnt
Bitte in dieses Thema NUR Fehler oder Requests die den Adapter betreffen. KEINE Installationsfehler oder sonstige Fragen. macht dafür bitte wenn die Suche nichts ergeben hat ein neues Thema auf damit es hier nicht so überläuft wie in den alten Threads..
@meistertr Habe gerade den Adapter installiert iVm einem roborock.vacuum.a15 (Roborock S7).
Map und History werden sauber angezeigt.Beim Versuch unter Rooms auf den Button "roomClean" zu klicken, passiert leider nichts. Im Log sieht es folgendermaßen aus. Ein Anwenderfehler ist nicht ganz auszuschließen - ich habe mit den Rooms bisher nicht gearbeitet.
mihome-vacuum.3 2021-04-14 23:55:15.760 warn (29422) Get Mappinter done redomap... mihome-vacuum.3 2021-04-14 23:55:15.484 warn (29422) Get Mappinter while cleaning mihome-vacuum.3 2021-04-14 23:55:07.136 warn (29422) Get Mappinter done redomap... mihome-vacuum.3 2021-04-14 23:55:06.916 warn (29422) Get Mappinter while cleaning mihome-vacuum.3 2021-04-14 23:54:59.922 warn (29422) Get Mappinter done redomap... mihome-vacuum.3 2021-04-14 23:54:59.776 warn (29422) Get Mappinter while cleaning mihome-vacuum.3 2021-04-14 23:54:52.912 warn (29422) Get Mappinter done redomap... mihome-vacuum.3 2021-04-14 23:54:52.575 warn (29422) Get Mappinter while cleaning mihome-vacuum.3 2021-04-14 23:54:48.489 warn (29422) Get Mappinter done redomap... mihome-vacuum.3 2021-04-14 23:54:48.095 warn (29422) Get Mappinter while cleaning mihome-vacuum.3 2021-04-14 23:54:30.872 warn (29422) Get Mappinter done redomap... mihome-vacuum.3 2021-04-14 23:54:28.865 warn (29422) Get Mappinter while cleaning mihome-vacuum.3 2021-04-14 23:54:22.408 warn (29422) Get Mappinter done redomap... mihome-vacuum.3 2021-04-14 23:54:22.196 warn (29422) Get Mappinter while cleaning mihome-vacuum.3 2021-04-14 23:53:45.615 warn (29422) State "mihome-vacuum.3.info.queue" has no existing object, this might lead to an error in future versions -
@meistertr Habe gerade den Adapter installiert iVm einem roborock.vacuum.a15 (Roborock S7).
Map und History werden sauber angezeigt.Beim Versuch unter Rooms auf den Button "roomClean" zu klicken, passiert leider nichts. Im Log sieht es folgendermaßen aus. Ein Anwenderfehler ist nicht ganz auszuschließen - ich habe mit den Rooms bisher nicht gearbeitet.
mihome-vacuum.3 2021-04-14 23:55:15.760 warn (29422) Get Mappinter done redomap... mihome-vacuum.3 2021-04-14 23:55:15.484 warn (29422) Get Mappinter while cleaning mihome-vacuum.3 2021-04-14 23:55:07.136 warn (29422) Get Mappinter done redomap... mihome-vacuum.3 2021-04-14 23:55:06.916 warn (29422) Get Mappinter while cleaning mihome-vacuum.3 2021-04-14 23:54:59.922 warn (29422) Get Mappinter done redomap... mihome-vacuum.3 2021-04-14 23:54:59.776 warn (29422) Get Mappinter while cleaning mihome-vacuum.3 2021-04-14 23:54:52.912 warn (29422) Get Mappinter done redomap... mihome-vacuum.3 2021-04-14 23:54:52.575 warn (29422) Get Mappinter while cleaning mihome-vacuum.3 2021-04-14 23:54:48.489 warn (29422) Get Mappinter done redomap... mihome-vacuum.3 2021-04-14 23:54:48.095 warn (29422) Get Mappinter while cleaning mihome-vacuum.3 2021-04-14 23:54:30.872 warn (29422) Get Mappinter done redomap... mihome-vacuum.3 2021-04-14 23:54:28.865 warn (29422) Get Mappinter while cleaning mihome-vacuum.3 2021-04-14 23:54:22.408 warn (29422) Get Mappinter done redomap... mihome-vacuum.3 2021-04-14 23:54:22.196 warn (29422) Get Mappinter while cleaning mihome-vacuum.3 2021-04-14 23:53:45.615 warn (29422) State "mihome-vacuum.3.info.queue" has no existing object, this might lead to an error in future versions@coffeelover sagte in Test Adapter Mihome-vacuum v3.0.5 Next Generarition:
queue
sollte in der 3.0.6 gehen
-
@coffeelover sagte in Test Adapter Mihome-vacuum v3.0.5 Next Generarition:
queue
sollte in der 3.0.6 gehen
@meistertr said in Test Adapter Mihome-vacuum v3.0.6 Next Generarition:
@coffeelover sagte in Test Adapter Mihome-vacuum v3.0.5 Next Generarition:
queue
sollte in der 3.0.6 gehen
306 läuft und der Fehler mit dem Mappinter ist auch weg. Danke dafür :)
-
Ich hab die V3.0.7 und 3.0.6 ausprobiert. Bei beiden erhalte ich KEINE Fehlermeldung
answer map_slot is currently not supportedmehrDafür erhalte ich aber auch keine MAP mehr :( In Valetudo ist sie jedoch vorhanden:
EInstellung Adapter Map-Settings:
Version 3.0.7 in /opt/iobroker/node_modules/iobroker.mihome-vacuum,
node: v12.21.0,
js-controller: 3.2.16
rockrobo.vacuum.v1UDM Pro, Intel NUC - ioBroker in Proxmox-VM, PiHole+Grafana&Influx+TasmoAdmin in LXCs, Raspberry Pi3 (als CCU), Zigbee-Stick Sonoff, Synology DS918+
-
Ich hab die V3.0.7 und 3.0.6 ausprobiert. Bei beiden erhalte ich KEINE Fehlermeldung
answer map_slot is currently not supportedmehrDafür erhalte ich aber auch keine MAP mehr :( In Valetudo ist sie jedoch vorhanden:
EInstellung Adapter Map-Settings:
Version 3.0.7 in /opt/iobroker/node_modules/iobroker.mihome-vacuum,
node: v12.21.0,
js-controller: 3.2.16
rockrobo.vacuum.v1 -
@meistertr anbei das komplette LOG (Token hab ich ge-X-t):
iobroker.2021-04-15.logUDM Pro, Intel NUC - ioBroker in Proxmox-VM, PiHole+Grafana&Influx+TasmoAdmin in LXCs, Raspberry Pi3 (als CCU), Zigbee-Stick Sonoff, Synology DS918+
-
@meistertr anbei das komplette LOG (Token hab ich ge-X-t):
iobroker.2021-04-15.log -
@meistertr anbei das komplette LOG (Token hab ich ge-X-t):
iobroker.2021-04-15.log -
@meistertr YEEES Meister, Fehlermeldung weg und unter Cleanmap wieder die Map da. Perfekt. Vielen Dank :+1: :+1: :+1:
NACHTRAG: Auch die CPU-Auslastung, mit der ich bei der alten Adapter-Version unheimlich Probleme hatte (bis hin zum Absturz vom NUC) sind nun weg. Hatte den Adapter daher lang nicht verwendet.
UDM Pro, Intel NUC - ioBroker in Proxmox-VM, PiHole+Grafana&Influx+TasmoAdmin in LXCs, Raspberry Pi3 (als CCU), Zigbee-Stick Sonoff, Synology DS918+
-
@meistertr YEEES Meister, Fehlermeldung weg und unter Cleanmap wieder die Map da. Perfekt. Vielen Dank :+1: :+1: :+1:
NACHTRAG: Auch die CPU-Auslastung, mit der ich bei der alten Adapter-Version unheimlich Probleme hatte (bis hin zum Absturz vom NUC) sind nun weg. Hatte den Adapter daher lang nicht verwendet.
-
@meistertr RoborockS6 macht keine probleme.
allerdings hat er schon vor längerer zeit den goto verloren. hab da mal was eingetragen, passt allerding natürlich mit. in der App kann ich ja das target anklicken, aber ich finde die positon nirgends als xval, yval. wie kann man das rausfinden?
Support us
837
Online32.4k
Benutzer81.5k
Themen1.3m
Beiträge