mihome-vacuum Verbindungsprobleme

haselchen

Also in der Fritzbox, wenn du eine hast, würde ich dem Robbi immer dieselbe IP zuweisen.

In der App sollte es eine Möglichkeit zum Neustarten geben. Ansonsten Aus und wieder An mit dem Knopf am Gerät.
Aber erst die IP Adresse vorher festlegen.

In der Instanzen Einstellung klickst du oben auf das Männchen für Experteneinstellung. Und dann erscheint rechts die Möglichkeit durch anklicken von Info auf Debug zu stellen.
Und dann bei Adapterstart ins Log gucken.

Kannst dann auch das Log runterladen. Müssten die Infos, dann nach Adapterstart drinstehen, die man braucht.

Schranzer

@haselchen Also er hat jetzt ein Feste IP....Ich hab Ihn neugestartet (hab jetzt nen halben Kotzreitz gekriegt weil er wieso auch immer die Karte gelöscht hat) den Log hab ich ja eigentlich oben schon reingeschickt mehr gibt er im Log auch nicht aus

haselchen

@Schranzer

Die Karte kann man speichern in der App ;)
Und wenn du Debug eingestellt hast, kommt mehr als du oben gepostet hast.

Verbindet er sich immer noch nicht?

Schranzer

@haselchen Der Haken bei Karte speichern ist drinen :( und er hat es trotzdem gelöscht. ok Danke ! Ne er verbindet sich immer noch nicht. Aber wie schick ich den Link rein, er geht ja immer auf eine andere Seite.
Edit: soll ich des mit filezilla oder so machen?

haselchen

@Schranzer

Welche Seite meinst Du?

Schranzer

@haselchen Ja wenn ich auf Log Herunterladen klicke dann öffnet er einen neuen tab http://192.168.188.61:8081/log/file1/iobroker.2021-01-01.log

haselchen

@Schranzer

Müsste eine neue Browserseite sein.
Und da stehen alle Ereignisse drin.
Die von dem Adapter hier reinkopieren in Codetags.

Schranzer

@haselchen richtig! Aber wie stelle ich den Log hierein xD?

haselchen

@Schranzer

Schranzer

@haselchen Wenn ich das mache sagt er das der Code zu lang ist

haselchen

@Schranzer

Es reichen nur die Zeilen die deinen Robbi betreffen

Schranzer

@Schranzer ```

2021-01-01 23:16:41.291 - info: host.IOBROKER-PI4 "system.adapter.mihome-vacuum.0" disabled
2021-01-01 23:16:41.302 - info: host.IOBROKER-PI4 stopInstance system.adapter.mihome-vacuum.0 (force=false, process=true)
2021-01-01 23:16:41.314 - info: mihome-vacuum.0 (23795) Got terminate signal TERMINATE_YOURSELF
2021-01-01 23:16:41.307 - info: host.IOBROKER-PI4 stopInstance system.adapter.mihome-vacuum.0 send kill signal
2021-01-01 23:16:41.318 - info: mihome-vacuum.0 (23795) terminating
2021-01-01 23:16:41.320 - info: mihome-vacuum.0 (23795) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
2021-01-01 23:16:41.864 - info: host.IOBROKER-PI4 instance system.adapter.mihome-vacuum.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
2021-01-01 23:18:56.130 - info: host.IOBROKER-PI4 "system.adapter.mihome-vacuum.0" enabled
2021-01-01 23:18:56.187 - info: host.IOBROKER-PI4 instance system.adapter.mihome-vacuum.0 started with pid 31143
2021-01-01 23:18:59.624 - info: mihome-vacuum.0 (31143) starting. Version 2.1.1 in /opt/iobroker/node_modules/iobroker.mihome-vacuum, node: v12.20.0, js-controller: 3.1.6
2021-01-01 23:18:59.696 - info: mihome-vacuum.0 (31143) Expert mode disabled, states deleted
2021-01-01 23:18:59.699 - info: mihome-vacuum.0 (31143) Cloud control disabled
2021-01-01 23:18:59.818 - info: mihome-vacuum.0 (31143) connecting, this can take up to 10 minutes ...
2021-01-01 23:19:00.236 - info: mihome-vacuum.0 (31143) set nächster Timer: Nicht verfügbar
2021-01-01 23:19:19.780 - info: mihome-vacuum.0 (31143) connecting, this can take up to 10 minutes ...
2021-01-01 23:19:39.748 - info: mihome-vacuum.0 (31143) connecting, this can take up to 10 minutes ...
2021-01-01 23:19:59.818 - info: mihome-vacuum.0 (31143) connecting, this can take up to 10 minutes ...
2021-01-01 23:20:19.790 - info: mihome-vacuum.0 (31143) connecting, this can take up to 10 minutes ...
2021-01-01 23:20:39.756 - info: mihome-vacuum.0 (31143) connecting, this can take up to 10 minutes ...
2021-01-01 23:20:59.825 - info: mihome-vacuum.0 (31143) connecting, this can take up to 10 minutes ...
2021-01-01 23:21:19.794 - info: mihome-vacuum.0 (31143) connecting, this can take up to 10 minutes ...
2021-01-01 23:21:39.764 - info: mihome-vacuum.0 (31143) connecting, this can take up to 10 minutes ...
2021-01-01 23:21:59.832 - info: mihome-vacuum.0 (31143) connecting, this can take up to 10 minutes ...
2021-01-01 23:22:19.801 - info: mihome-vacuum.0 (31143) connecting, this can take up to 10 minutes ...
2021-01-01 23:22:39.768 - info: mihome-vacuum.0 (31143) connecting, this can take up to 10 minutes ...
2021-01-01 23:22:59.838 - info: mihome-vacuum.0 (31143) connecting, this can take up to 10 minutes ...
2021-01-01 23:23:19.807 - info: mihome-vacuum.0 (31143) connecting, this can take up to 10 minutes ...
2021-01-01 23:23:39.775 - info: mihome-vacuum.0 (31143) connecting, this can take up to 10 minutes ...
2021-01-01 23:23:59.848 - info: mihome-vacuum.0 (31143) connecting, this can take up to 10 minutes ...
2021-01-01 23:24:19.816 - info: mihome-vacuum.0 (31143) connecting, this can take up to 10 minutes ...
2021-01-01 23:24:39.782 - info: mihome-vacuum.0 (31143) connecting, this can take up to 10 minutes ...
2021-01-01 23:24:59.856 - info: mihome-vacuum.0 (31143) connecting, this can take up to 10 minutes ...
2021-01-01 23:25:19.820 - info: mihome-vacuum.0 (31143) connecting, this can take up to 10 minutes ...
2021-01-01 23:25:39.795 - info: mihome-vacuum.0 (31143) connecting, this can take up to 10 minutes ...
2021-01-01 23:25:59.859 - info: mihome-vacuum.0 (31143) connecting, this can take up to 10 minutes ...
2021-01-01 23:26:19.830 - info: mihome-vacuum.0 (31143) connecting, this can take up to 10 minutes ...
2021-01-01 23:26:39.795 - info: mihome-vacuum.0 (31143) connecting, this can take up to 10 minutes ...
2021-01-01 23:26:59.866 - info: mihome-vacuum.0 (31143) connecting, this can take up to 10 minutes ...
2021-01-01 23:27:19.834 - info: mihome-vacuum.0 (31143) connecting, this can take up to 10 minutes ...
2021-01-01 23:27:39.802 - info: mihome-vacuum.0 (31143) connecting, this can take up to 10 minutes ...
2021-01-01 23:27:59.873 - info: mihome-vacuum.0 (31143) connecting, this can take up to 10 minutes ...
2021-01-01 23:28:19.841 - info: mihome-vacuum.0 (31143) connecting, this can take up to 10 minutes ...
2021-01-01 23:28:39.809 - info: mihome-vacuum.0 (31143) connecting, this can take up to 10 minutes ...
2021-01-01 23:28:59.880 - info: mihome-vacuum.0 (31143) connecting, this can take up to 10 minutes ...
2021-01-01 23:29:19.848 - info: mihome-vacuum.0 (31143) connecting, this can take up to 10 minutes ...
```

Schranzer

@Schranzer Danke :)

haselchen

@Schranzer

Du bist immer noch bei INFO

DEBUG musst du bitte einstellen, wie ich es eben beschrieben habe.

Instanzen, Info anklicken und Debug auswählen. Vorher Expert Modus einstellen.

Schranzer

@haselchen

Wenn ich des anklick passiert nichts ...wo würde ich den expertenmodus aktivieren?

haselchen

@Schranzer

Bitte genau lesen, hab es jetzt 3 mal geschrieben.
Unter Instanzen, oben links das Männchen anklicken. Dann erscheint die Spalte Info.
Dort draufklicken beim Adapter Mihome und Debug auswählen.

Schranzer

@haselchen ```

code_text
```
mihome-vacuum.0	2021-01-01 23:52:30.862	info	(4242) connecting, this can take up to 10 minutes ...
mihome-vacuum.0	2021-01-01 23:52:30.861	debug	(4242) Receive <<< Helo <<< 2131002000000000166375305fefa7aeffffffffffffffffffffffffffffffff
mihome-vacuum.0	2021-01-01 23:52:25.812	debug	(4242) sendTo "getStatus" to system.adapter.mihome-vacuum.0 from system.adapter.mihome-vacuum.0
mihome-vacuum.0	2021-01-01 23:52:25.810	debug	(4242) no answer for id:6 received, giving up
mihome-vacuum.0	2021-01-01 23:52:20.807	debug	(4242) sendMsg[3] >>> {"id":6,"method":"get_status"}
mihome-vacuum.0	2021-01-01 23:52:15.804	debug	(4242) sendMsg[2] >>> {"id":6,"method":"get_status"}
mihome-vacuum.0	2021-01-01 23:52:10.800	debug	(4242) sendMsg[1] >>> {"id":6,"method":"get_status"}
mihome-vacuum.0	2021-01-01 23:52:10.791	debug	(4242) sendTo "getStatus" to system.adapter.mihome-vacuum.0 from system.adapter.mihome-vacuum.0
mihome-vacuum.0	2021-01-01 23:52:10.790	info	(4242) connecting, this can take up to 10 minutes ...
mihome-vacuum.0	2021-01-01 23:52:10.788	debug	(4242) Receive <<< Helo <<< 2131002000000000166375305fefa79affffffffffffffffffffffffffffffff
mihome-vacuum.0	2021-01-01 23:52:05.844	debug	(4242) sendTo "getStatus" to system.adapter.mihome-vacuum.0 from system.adapter.mihome-vacuum.0
mihome-vacuum.0	2021-01-01 23:52:05.842	debug	(4242) no answer for id:5 received, giving up
mihome-vacuum.0	2021-01-01 23:52:00.838	debug	(4242) sendMsg[3] >>> {"id":5,"method":"get_status"}
mihome-vacuum.0	2021-01-01 23:51:55.835	debug	(4242) sendMsg[2] >>> {"id":5,"method":"get_status"}
mihome-vacuum.0	2021-01-01 23:51:50.832	debug	(4242) sendMsg[1] >>> {"id":5,"method":"get_status"}
mihome-vacuum.0	2021-01-01 23:51:50.823	debug	(4242) sendTo "getStatus" to system.adapter.mihome-vacuum.0 from system.adapter.mihome-vacuum.0
mihome-vacuum.0	2021-01-01 23:51:50.822	info	(4242) connecting, this can take up to 10 minutes ...
mihome-vacuum.0	2021-01-01 23:51:50.820	debug	(4242) Receive <<< Helo <<< 2131002000000000166375305fefa786ffffffffffffffffffffffffffffffff
mihome-vacuum.0	2021-01-01 23:51:45.792	debug	(4242) sendTo "getStatus" to system.adapter.mihome-vacuum.0 from system.adapter.mihome-vacuum.0
mihome-vacuum.0	2021-01-01 23:51:45.791	debug	(4242) no answer for id:4 received, giving up
mihome-vacuum.0	2021-01-01 23:51:40.788	debug	(4242) sendMsg[3] >>> {"id":4,"method":"get_status"}
mihome-vacuum.0	2021-01-01 23:51:35.785	debug	(4242) sendMsg[2] >>> {"id":4,"method":"get_status"}
mihome-vacuum.0	2021-01-01 23:51:30.781	debug	(4242) sendMsg[1] >>> {"id":4,"method":"get_status"}
mihome-vacuum.0	2021-01-01 23:51:30.775	debug	(4242) sendTo "getStatus" to system.adapter.mihome-vacuum.0 from system.adapter.mihome-vacuum.0
mihome-vacuum.0	2021-01-01 23:51:30.774	info	(4242) connecting, this can take up to 10 minutes ...
mihome-vacuum.0	2021-01-01 23:51:30.773	debug	(4242) Receive <<< Helo <<< 2131002000000000166375305fefa772ffffffffffffffffffffffffffffffff
mihome-vacuum.0	2021-01-01 23:51:25.805	debug	(4242) sendTo "getStatus" to system.adapter.mihome-vacuum.0 from system.adapter.mihome-vacuum.0
mihome-vacuum.0	2021-01-01 23:51:25.803	debug	(4242) no answer for id:3 received, giving up
mihome-vacuum.0	2021-01-01 23:51:20.801	debug	(4242) sendMsg[3] >>> {"id":3,"method":"get_status"}
mihome-vacuum.0	2021-01-01 23:51:15.798	debug	(4242) sendMsg[2] >>> {"id":3,"method":"get_status"}
mihome-vacuum.0	2021-01-01 23:51:10.795	debug	(4242) sendMsg[1] >>> {"id":3,"method":"get_status"}
mihome-vacuum.0	2021-01-01 23:51:10.785	debug	(4242) sendTo "getStatus" to system.adapter.mihome-vacuum.0 from system.adapter.mihome-vacuum.0
mihome-vacuum.0	2021-01-01 23:51:10.784	info	(4242) connecting, this can take up to 10 minutes ...
mihome-vacuum.0	2021-01-01 23:51:10.782	debug	(4242) Receive <<< Helo <<< 2131002000000000166375305fefa75effffffffffffffffffffffffffffffff
mihome-vacuum.0	2021-01-01 23:51:05.834	debug	(4242) sendTo "getStatus" to system.adapter.mihome-vacuum.0 from system.adapter.mihome-vacuum.0
mihome-vacuum.0	2021-01-01 23:51:05.832	debug	(4242) no answer for id:2 received, giving up
mihome-vacuum.0	2021-01-01 23:51:00.831	debug	(4242) sendMsg[3] >>> {"id":2,"method":"get_status"}
mihome-vacuum.0	2021-01-01 23:50:55.828	debug	(4242) sendMsg[2] >>> {"id":2,"method":"get_status"}
mihome-vacuum.0	2021-01-01 23:50:50.825	debug	(4242) sendMsg[1] >>> {"id":2,"method":"get_status"}
mihome-vacuum.0	2021-01-01 23:50:50.816	debug	(4242) sendTo "getStatus" to system.adapter.mihome-vacuum.0 from system.adapter.mihome-vacuum.0
mihome-vacuum.0	2021-01-01 23:50:50.815	info	(4242) connecting, this can take up to 10 minutes ...
mihome-vacuum.0	2021-01-01 23:50:50.813	debug	(4242) Receive <<< Helo <<< 2131002000000000166375305fefa74affffffffffffffffffffffffffffffff
mihome-vacuum.0	2021-01-01 23:50:45.901	debug	(4242) sendTo "getStatus" to system.adapter.mihome-vacuum.0 from system.adapter.mihome-vacuum.0
mihome-vacuum.0	2021-01-01 23:50:45.898	debug	(4242) no answer for id:1 received, giving up
mihome-vacuum.0	2021-01-01 23:50:40.895	debug	(4242) sendMsg[3] >>> {"id":1,"method":"get_status"}
mihome-vacuum.0	2021-01-01 23:50:35.892	debug	(4242) sendMsg[2] >>> {"id":1,"method":"get_status"}
mihome-vacuum.0	2021-01-01 23:50:33.869	debug	(4242) system.adapter.admin.0: logging true
mihome-vacuum.0	2021-01-01 23:50:31.284	info	(4242) set nächster Timer: Nicht verfügbar
mihome-vacuum.0	2021-01-01 23:50:30.890	debug	(4242) sendMsg[1] >>> {"id":1,"method":"get_status"}
mihome-vacuum.0	2021-01-01 23:50:30.858	debug	(4242) sendTo "getStatus" to system.adapter.mihome-vacuum.0 from system.adapter.mihome-vacuum.0
mihome-vacuum.0	2021-01-01 23:50:30.855	info	(4242) connecting, this can take up to 10 minutes ...
mihome-vacuum.0	2021-01-01 23:50:30.851	debug	(4242) Receive <<< Helo <<< 2131002000000000166375305fefa736ffffffffffffffffffffffffffffffff
mihome-vacuum.0	2021-01-01 23:50:30.820	debug	(4242) No suitable Lua script, fallback to keys!: function(doc) { if (doc.type === 'state') emit(doc._id, doc) }
mihome-vacuum.0	2021-01-01 23:50:30.776	debug	(4242) server started on 0.0.0.0:53421
mihome-vacuum.0	2021-01-01 23:50:30.747	info	(4242) Cloud control disabled
mihome-vacuum.0	2021-01-01 23:50:30.744	info	(4242) Expert mode disabled, states deleted
mihome-vacuum.0	2021-01-01 23:50:30.684	info	(4242) starting. Version 2.1.1 in /opt/iobroker/node_modules/iobroker.mihome-vacuum, node: v12.20.0, js-controller: 3.1.6
mihome-vacuum.0	2021-01-01 23:50:29.893	debug	(4242) statesDB connected
mihome-vacuum.0	2021-01-01 23:50:29.891	debug	(4242) States connected to redis: 127.0.0.1:9000
mihome-vacuum.0	2021-01-01 23:50:29.878	debug	(4242) States create System PubSub Client
mihome-vacuum.0	2021-01-01 23:50:29.869	debug	(4242) States create User PubSub Client
mihome-vacuum.0	2021-01-01 23:50:29.855	debug	(4242) Redis States: Use Redis connection: 127.0.0.1:9000
mihome-vacuum.0	2021-01-01 23:50:29.850	debug	(4242) objectDB connected
mihome-vacuum.0	2021-01-01 23:50:29.837	debug	(4242) Objects connected to redis: 127.0.0.1:9001
mihome-vacuum.0	2021-01-01 23:50:29.810	debug	(4242) Objects client initialize lua scripts
mihome-vacuum.0	2021-01-01 23:50:29.807	debug	(4242) Objects create User PubSub Client
mihome-vacuum.0	2021-01-01 23:50:29.803	debug	(4242) Objects create System PubSub Client
mihome-vacuum.0	2021-01-01 23:50:29.779	debug	(4242) Objects client ready ... initialize now
mihome-vacuum.0	2021-01-01 23:50:29.499	debug	(4242) Redis Objects: Use Redis connection: 127.0.0.1:9001
host.IOBROKER-PI4	2021-01-01 23:50:27.380	info	instance system.adapter.mihome-vacuum.0 started with pid 4242
host.IOBROKER-PI4	2021-01-01 23:50:27.345	info	"system.adapter.mihome-vacuum.0" enabled
host.IOBROKER-PI4	2021-01-01 23:49:41.812	info	instance system.adapter.mihome-vacuum.0 terminated with code 3 (NO_ADAPTER_CONFIG_FOUND)
mihome-vacuum.0	2021-01-01 23:49:41.242	warn	(4089) Terminated (NO_ADAPTER_CONFIG_FOUND): Without reason
mihome-vacuum.0	2021-01-01 23:49:41.213	error	(4089) adapter disabled
host.IOBROKER-PI4	2021-01-01 23:49:40.477	info	stopInstance system.adapter.mihome-vacuum.0 killing pid 4089
host.IOBROKER-PI4	2021-01-01 23:49:39.472	info	stopInstance system.adapter.mihome-vacuum.0 send kill signal
host.IOBROKER-PI4	2021-01-01 23:49:39.468	info	stopInstance system.adapter.mihome-vacuum.0 (force=false, process=true)
host.IOBROKER-PI4	2021-01-01 23:49:39.463	info	"system.adapter.mihome-vacuum.0" disabled
host.IOBROKER-PI4	2021-01-01 23:49:37.392	info	instance system.adapter.mihome-vacuum.0 started with pid 4089
host.IOBROKER-PI4	2021-01-01 23:49:37.313	info	"system.adapter.mihome-vacuum.0" enabled
host.IOBROKER-PI4	2021-01-01 23:44:24.246	info	Update repository "Stable (default)" under "http://download.iobroker.net/sources-dist.json"
host.IOBROKER-PI4	2021-01-01 23:44:20.029	info	Update repository "Stable (default)" under "http://download.iobroker.net/sources-dist.json"
host.IOBROKER-PI4	2021-01-01 23:42:29.260	info	Update repository "Stable (default)" under "http://download.iobroker.net/sources-dist.json"
host.IOBROKER-PI4	2021-01-01 23:42:24.790	info	Update repository "Stable (default)" under "http://download.iobroker.net/sources-dist.json"
host.IOBROKER-PI4	2021-01-01 23:41:24.660	info	Update repository "Stable (default)" under "http://download.iobroker.net/sources-dist.json"
host.IOBROKER-PI4	2021-01-01 23:37:15.933	info	instance system.adapter.mihome-vacuum.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
mihome-vacuum.0	2021-01-01 23:37:15.360	info	(31143) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
mihome-vacuum.0	2021-01-01 23:37:15.359	info	(31143) terminating
mihome-vacuum.0	2021-01-01 23:37:15.353	info	(31143) Got terminate signal TERMINATE_YOURSELF
host.IOBROKER-PI4	2021-01-01 23:37:15.346	info	stopInstance system.adapter.mihome-vacuum.0 send kill signal
host.IOBROKER-PI4	2021-01-01 23:37:15.342	info	stopInstance system.adapter.mihome-vacuum.0 (force=false, process=true)
host.IOBROKER-PI4	2021-01-01 23:37:15.332	info	"system.adapter.mihome-vacuum.0" disabled

Schranzer

@Schranzer OK jetzt danke sry

haselchen

@Schranzer

Das sollte schon den Betreffenden weiterhelfen.

Ich kann mit Redis nichts anfangen.
Vielleicht ist da schon der Fehler zu finden.
Kannst du hiermit auf file umstellen?

iobroker stop
iobroker setup custom

Meistertr

@Schranzer nach ein bisschen Reschere hätte dir auffallen sollen, das der "normale" Adapter den Mi Mop Pro noch nicht untertützt. nutze hierfür mal bitte den 3.x aus meinem Repository https://github.com/MeisterTR/ioBroker.mihome-vacuum

Community Forum

NEWS

mihome-vacuum Verbindungsprobleme

Support us

766

32.5k

81.7k

1.3m