Test Adapter mihome-vacuum v2.0.x
-
ich bekomme bei der Installtion immer folgenden Fehler:
Hat jemand Rat? Und brauche ich bei dem Adapter den Token nicht auszulesen? -
Danke dir erst einmal für deine Antwort. Ist es aber nicht.
Es handelt sich um einen S502-00Mi Roborock 2 white
Staubsaugerroboter Xiaomi Mi Roborock 2 (2.Generation) weiß.
Sprich ein S5 damit sollte es doch eigentlich gehen?Gruß BamBam89
-
Aktiviere bitte mal bei den Instanzen (das Icon oben = Expertenmodus) und stell dann bitte den Adapter bei Logs stufe auf debug. Dann den Adapter neu starten.. es sollten dann mehr Einträge in der Log Übersicht sein als vorher.
Dann den Log mal reinkopieren.. bin sicher @dirkhe kann dir dann helfenLG
-
Danke dir.
@dirkhe ich hoffe du kannst mir weiter helfen.
Anbei die Log Einträgemihome-vacuum.0 2020-04-10 14:03:28.047 info (14176) set nächster Timer: Nicht verfügbar mihome-vacuum.0 2020-04-10 14:03:27.651 info (14176) connecting, this can take up to 10 minutes ... mihome-vacuum.0 2020-04-10 14:03:27.507 info (14176) Create state clean_home for controlling by cloud adapter mihome-vacuum.0 2020-04-10 14:03:27.505 info (14176) Expert mode enabled, states created mihome-vacuum.0 2020-04-10 14:03:27.384 info (14176) starting. Version 2.0.9-RC07 in /opt/iobroker/node_modules/iobroker.mihome-vacuum, node: v10.19.0 mihome-vacuum.0 2020-04-10 14:03:21.098 info (13239) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason mihome-vacuum.0 2020-04-10 14:03:21.096 info (13239) terminating mihome-vacuum.0 2020-04-10 14:03:21.094 info (13239) Got terminate signal TERMINATE_YOURSELF mihome-vacuum.0 2020-04-10 14:03:17.537 info (13239) connecting, this can take up to 10 minutes ... mihome-vacuum.0 2020-04-10 14:02:57.537 info (13239) connecting, this can take up to 10 minutes ... mihome-vacuum.0 2020-04-10 14:02:37.544 info (13239) connecting, this can take up to 10 minutes ... mihome-vacuum.0 2020-04-10 14:02:17.536 info (13239) connecting, this can take up to 10 minutes ... mihome-vacuum.0 2020-04-10 14:01:58.049 info (13239) set nächster Timer: Nicht verfügbar mihome-vacuum.0 2020-04-10 14:01:57.621 info (13239) connecting, this can take up to 10 minutes ... mihome-vacuum.0 2020-04-10 14:01:57.519 info (13239) Create state clean_home for controlling by cloud adapter mihome-vacuum.0 2020-04-10 14:01:57.518 info (13239) Expert mode enabled, states created mihome-vacuum.0 2020-04-10 14:01:57.268 info (13239) starting. Version 2.0.9-RC07 in /opt/iobroker/node_modules/iobroker.mihome-vacuum, node: v10.19.0 Gruß BamBam89 -
@BamBam89 Du hast noch nicht auf debug gestellt. Bitte mache das mal.
-
@DarkDevil Bitte readme lesen. Du kannst den Tocken über den Adapter auslesen, in der Konfiguration. Credentials für xiamio cload eingeben und Staubsauger auswählen
-
@dirkhe und hast du eine Idee warum ich es nicht installiert bekomme?
-
@dirkhe ähh doch... mehr ist da nicht...
Also zumindest denke ich, das ich debug aktiviert habe....
Gruß BamBam89
-
@BamBam89 Du hast nurdie Filterung auf debug eingestellt. Du musst dem Adapter in den Instanzen aud debug einstellen:
-
@DarkDevil Ist schon tausendmal geschrieben worden, wahrscheinlich musst du canvas manuell installieren, bitte mal die sufu nutzen oder halt das readme lesen
-
und wieder was dazu gelernt....
hier ein Auszug aus dem Log:
mihome-vacuum.0 2020-04-10 22:58:59.846 info (27269) connecting, this can take up to 10 minutes ... mihome-vacuum.0 2020-04-10 22:58:59.846 debug (27269) Receive <<< Helo <<< 21310020000000000f9b48a15e90de13ffffffffffffffffffffffffffffffff mihome-vacuum.0 2020-04-10 22:58:54.860 debug (27269) sendTo "getStatus" to system.adapter.mihome-vacuum.0 from system.adapter.mihome-vacuum.0 mihome-vacuum.0 2020-04-10 22:58:54.859 debug (27269) no answer for undefined(id:3) received, giving up mihome-vacuum.0 2020-04-10 22:58:49.858 debug (27269) sendMsg[3] >>> {"id":3,"method":"get_status"} mihome-vacuum.0 2020-04-10 22:58:44.857 debug (27269) sendMsg[2] >>> {"id":3,"method":"get_status"} mihome-vacuum.0 2020-04-10 22:58:39.856 debug (27269) sendMsg[1] >>> {"id":3,"method":"get_status"} mihome-vacuum.0 2020-04-10 22:58:39.850 debug (27269) sendTo "getStatus" to system.adapter.mihome-vacuum.0 from system.adapter.mihome-vacuum.0 mihome-vacuum.0 2020-04-10 22:58:39.849 info (27269) connecting, this can take up to 10 minutes ... mihome-vacuum.0 2020-04-10 22:58:39.848 debug (27269) Receive <<< Helo <<< 21310020000000000f9b48a15e90ddffffffffffffffffffffffffffffffffff mihome-vacuum.0 2020-04-10 22:58:34.862 debug (27269) sendTo "getStatus" to system.adapter.mihome-vacuum.0 from system.adapter.mihome-vacuum.0 mihome-vacuum.0 2020-04-10 22:58:34.861 debug (27269) no answer for undefined(id:2) received, giving up mihome-vacuum.0 2020-04-10 22:58:29.860 debug (27269) sendMsg[3] >>> {"id":2,"method":"get_status"} mihome-vacuum.0 2020-04-10 22:58:24.859 debug (27269) sendMsg[2] >>> {"id":2,"method":"get_status"} mihome-vacuum.0 2020-04-10 22:58:19.858 debug (27269) sendMsg[1] >>> {"id":2,"method":"get_status"} mihome-vacuum.0 2020-04-10 22:58:19.849 debug (27269) sendTo "getStatus" to system.adapter.mihome-vacuum.0 from system.adapter.mihome-vacuum.0 mihome-vacuum.0 2020-04-10 22:58:19.848 info (27269) connecting, this can take up to 10 minutes ... mihome-vacuum.0 2020-04-10 22:58:19.847 debug (27269) Receive <<< Helo <<< 21310020000000000f9b48a15e90ddebffffffffffffffffffffffffffffffff mihome-vacuum.0 2020-04-10 22:58:14.970 debug (27269) sendTo "getStatus" to system.adapter.mihome-vacuum.0 from system.adapter.mihome-vacuum.0 mihome-vacuum.0 2020-04-10 22:58:14.969 debug (27269) no answer for undefined(id:1) received, giving up mihome-vacuum.0 2020-04-10 22:58:09.968 debug (27269) sendMsg[3] >>> {"id":1,"method":"get_status"} mihome-vacuum.0 2020-04-10 22:58:04.967 debug (27269) sendMsg[2] >>> {"id":1,"method":"get_status"} mihome-vacuum.0 2020-04-10 22:58:02.153 debug (27269) Xiaomi Cloud: Login successful mihome-vacuum.0 2020-04-10 22:58:00.368 info (27269) set nächster Timer: Nicht verfügbar mihome-vacuum.0 2020-04-10 22:57:59.965 debug (27269) sendMsg[1] >>> {"id":1,"method":"get_status"} mihome-vacuum.0 2020-04-10 22:57:59.940 debug (27269) sendTo "getStatus" to system.adapter.mihome-vacuum.0 from system.adapter.mihome-vacuum.0 mihome-vacuum.0 2020-04-10 22:57:59.938 info (27269) connecting, this can take up to 10 minutes ... mihome-vacuum.0 2020-04-10 22:57:59.937 debug (27269) Receive <<< Helo <<< 21310020000000000f9b48a15e90ddd7ffffffffffffffffffffffffffffffff mihome-vacuum.0 2020-04-10 22:57:59.847 debug (27269) server started on 0.0.0.0:54321 mihome-vacuum.0 2020-04-10 22:57:59.828 debug (27269) Ios Token decrypted to: #i ~ ;e~O%v\p"FqXzcn&FlZ8O mihome-vacuum.0 2020-04-10 22:57:59.824 info (27269) Create state clean_home for controlling by cloud adapter mihome-vacuum.0 2020-04-10 22:57:59.822 info (27269) Expert mode enabled, states created mihome-vacuum.0 2020-04-10 22:57:59.808 debug (27269) Xiaomi Cloud: Logging in mihome-vacuum.0 2020-04-10 22:57:59.806 debug (27269) load Map creator... true mihome-vacuum.0 2020-04-10 22:57:59.709 info (27269) starting. Version 2.0.9-RC07 in /opt/iobroker/node_modules/iobroker.mihome-vacuum, node: v10.19.0 mihome-vacuum.0 2020-04-10 22:57:57.610 debug (27269) statesDB connected mihome-vacuum.0 2020-04-10 22:57:57.609 debug (27269) States connected to redis: 127.0.0.1:9000 mihome-vacuum.0 2020-04-10 22:57:57.596 debug (27269) States create System PubSub Client mihome-vacuum.0 2020-04-10 22:57:57.593 debug (27269) States create User PubSub Client mihome-vacuum.0 2020-04-10 22:57:57.585 debug (27269) Redis States: Use Redis connection: 127.0.0.1:9000 mihome-vacuum.0 2020-04-10 22:57:57.582 debug (27269) objectDB connected mihome-vacuum.0 2020-04-10 22:57:57.575 debug (27269) Objects connected to redis: 127.0.0.1:9001 mihome-vacuum.0 2020-04-10 22:57:57.558 debug (27269) Objects client initialize lua scripts mihome-vacuum.0 2020-04-10 22:57:57.557 debug (27269) Objects create User PubSub Client mihome-vacuum.0 2020-04-10 22:57:57.556 debug (27269) Objects create System PubSub Client mihome-vacuum.0 2020-04-10 22:57:57.551 debug (27269) Objects client ready ... initialize now mihome-vacuum.0 2020-04-10 22:57:57.167 debug (27269) Redis Objects: Use Redis connection: 127.0.0.1:9001 -
Geh mal in die xiaomi App und verbinde dich mit dem robbi. Manchmal hilft das.
-
Die Installation (bzw. das Update) haben schonmal geklappt. Danke dafür.
Jetzt habe ich aber anscheinend den gleichen Fehler wie BamBam89mihome-vacuum.0 2020-04-11 07:47:03.668 info (28242) connecting, this can take up to 10 minutes ... mihome-vacuum.0 2020-04-11 07:47:03.668 warn (28242) Time difference between Mihome Vacuum and ioBroker: 1 sec mihome-vacuum.0 2020-04-11 07:47:03.667 debug (28242) Receive <<< Helo <<< 21310020000000000706b6555e9159d8ffffffffffffffffffffffffffffffff mihome-vacuum.0 2020-04-11 07:46:58.788 debug (28242) sendTo "getStatus" to system.adapter.mihome-vacuum.0 from system.adapter.mihome-vacuum.0 mihome-vacuum.0 2020-04-11 07:46:58.787 debug (28242) no answer for undefined(id:1) received, giving up mihome-vacuum.0 2020-04-11 07:46:55.373 debug (28242) system.adapter.admin.0: logging true mihome-vacuum.0 2020-04-11 07:46:53.786 debug (28242) sendMsg[3] >>> {"id":1,"method":"get_status"} mihome-vacuum.0 2020-04-11 07:46:48.785 debug (28242) sendMsg[2] >>> {"id":1,"method":"get_status"} mihome-vacuum.0 2020-04-11 07:46:46.064 debug (28242) Xiaomi Cloud: Login successful mihome-vacuum.0 2020-04-11 07:46:45.241 debug (28242) system.adapter.admin.0: logging false mihome-vacuum.0 2020-04-11 07:46:44.177 info (28242) set nächster Timer: Nicht verfügbar mihome-vacuum.0 2020-04-11 07:46:43.784 debug (28242) sendMsg[1] >>> {"id":1,"method":"get_status"} mihome-vacuum.0 2020-04-11 07:46:43.755 debug (28242) sendTo "getStatus" to system.adapter.mihome-vacuum.0 from system.adapter.mihome-vacuum.0 -
Hast du, wie vorher schonmal geraten, die MiHome App geöffnet ?
-
Morgen zusammen,
also ich hab das schon gemacht, allerdings ohne besondere Verbesserung:
mihome-vacuum.0 2020-04-11 09:33:39.352 debug (5753) sendMsg[1] >>> {"id":478,"method":"get_status"} mihome-vacuum.0 2020-04-11 09:33:39.349 debug (5753) sendTo "getStatus" to system.adapter.mihome-vacuum.0 from system.adapter.mihome-vacuum.0 mihome-vacuum.0 2020-04-11 09:33:39.348 info (5753) connecting, this can take up to 10 minutes ... mihome-vacuum.0 2020-04-11 09:33:39.348 debug (5753) Receive <<< Helo <<< 21310020000000000f9b48a15e9172d3ffffffffffffffffffffffffffffffff mihome-vacuum.0 2020-04-11 09:33:34.353 debug (5753) sendTo "getStatus" to system.adapter.mihome-vacuum.0 from system.adapter.mihome-vacuum.0 mihome-vacuum.0 2020-04-11 09:33:34.353 debug (5753) no answer for undefined(id:477) received, giving up mihome-vacuum.0 2020-04-11 09:33:29.353 debug (5753) sendMsg[3] >>> {"id":477,"method":"get_status"} mihome-vacuum.0 2020-04-11 09:33:24.352 debug (5753) sendMsg[2] >>> {"id":477,"method":"get_status"} mihome-vacuum.0 2020-04-11 09:33:19.351 debug (5753) sendMsg[1] >>> {"id":477,"method":"get_status"} mihome-vacuum.0 2020-04-11 09:33:19.346 debug (5753) sendTo "getStatus" to system.adapter.mihome-vacuum.0 from system.adapter.mihome-vacuum.0 mihome-vacuum.0 2020-04-11 09:33:19.346 info (5753) connecting, this can take up to 10 minutes ... mihome-vacuum.0 2020-04-11 09:33:19.346 debug (5753) Receive <<< Helo <<< 21310020000000000f9b48a15e9172bfffffffffffffffffffffffffffffffff mihome-vacuum.0 2020-04-11 09:33:14.351 debug (5753) sendTo "getStatus" to system.adapter.mihome-vacuum.0 from system.adapter.mihome-vacuum.0 mihome-vacuum.0 2020-04-11 09:33:14.350 debug (5753) no answer for undefined(id:476) received, giving up mihome-vacuum.0 2020-04-11 09:33:09.349 debug (5753) sendMsg[3] >>> {"id":476,"method":"get_status"} mihome-vacuum.0 2020-04-11 09:33:04.349 debug (5753) sendMsg[2] >>> {"id":476,"method":"get_status"} mihome-vacuum.0 2020-04-11 09:32:59.347 debug (5753) sendMsg[1] >>> {"id":476,"method":"get_status"} mihome-vacuum.0 2020-04-11 09:32:59.346 debug (5753) sendTo "getStatus" to system.adapter.mihome-vacuum.0 from system.adapter.mihome-vacuum.0 mihome-vacuum.0 2020-04-11 09:32:59.346 info (5753) connecting, this can take up to 10 minutes ... mihome-vacuum.0 2020-04-11 09:32:59.346 debug (5753) Receive <<< Helo <<< 21310020000000000f9b48a15e9172abffffffffffffffffffffffffffffffff mihome-vacuum.0 2020-04-11 09:32:54.354 debug (5753) sendTo "getStatus" to system.adapter.mihome-vacuum.0 from system.adapter.mihome-vacuum.0 mihome-vacuum.0 2020-04-11 09:32:54.354 debug (5753) no answer for undefined(id:475) received, giving up mihome-vacuum.0 2020-04-11 09:32:49.353 debug (5753) sendMsg[3] >>> {"id":475,"method":"get_status"} mihome-vacuum.0 2020-04-11 09:32:44.352 debug (5753) sendMsg[2] >>> {"id":475,"method":"get_status"} mihome-vacuum.0 2020-04-11 09:32:39.351 debug (5753) sendMsg[1] >>> {"id":475,"method":"get_status"} mihome-vacuum.0 2020-04-11 09:32:39.348 debug (5753) sendTo "getStatus" to system.adapter.mihome-vacuum.0 from system.adapter.mihome-vacuum.0 mihome-vacuum.0 2020-04-11 09:32:39.347 info (5753) connecting, this can take up to 10 minutes ...~~~~ ```~~ -
@BamBam89
Welcher Sauger welche Firmware Version? -
Es handelt sich um einen S502-00
Firmware 3.5.7_002008 -
Habe ich auch beides.
Welche Adapter Version hast du drauf?
Mit RC Nummer wenn du hast. -
Version 2.0.9. Mit RC Nummer kann ich aber nichts anfangen
-
Auf debug stellen über den Experten Modus und dann den Adapter neu starten. Im Log steht dann die RC Nummer hinter 2.0.9
