MiVacuum Adapter läuft nicht mehr
-
Log des Adapterstarts? Vielleicht auch auf Debug Level setzen.
-
mihome-vacuum.0 2022-07-09 12:56:15.804 info IOT enabled, create state mihome-vacuum.0 2022-07-09 12:56:15.675 info starting. Version 3.4.2 in /opt/iobroker/node_modules/iobroker.mihome-vacuum, node: v16.16.0, js-controller: 4.0.23 host.raspberrypi 2022-07-09 12:56:13.057 info instance system.adapter.mihome-vacuum.0 started with pid 2085 host.raspberrypi 2022-07-09 12:56:10.596 info instance system.adapter.mihome-vacuum.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION) host.raspberrypi 2022-07-09 12:56:09.869 info stopInstance system.adapter.mihome-vacuum.0 send kill signal mihome-vacuum.0 2022-07-09 12:56:09.823 info Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason mihome-vacuum.0 2022-07-09 12:56:09.820 info terminating mihome-vacuum.0 2022-07-09 12:56:09.818 error Socket Close mihome-vacuum.0 2022-07-09 12:56:09.814 info Got terminate signal TERMINATE_YOURSELF host.raspberrypi 2022-07-09 12:56:09.643 info stopInstance system.adapter.mihome-vacuum.0 (force=false, process=true) -
Log Level auf 'Debug' gesetzt?
-
mihome-vacuum.0 2022-07-09 13:25:45.159 debug Helo message Timeout mihome-vacuum.0 2022-07-09 13:25:43.155 debug server started on 0.0.0.0:53421 mihome-vacuum.0 2022-07-09 13:25:43.150 info IOT enabled, create state mihome-vacuum.0 2022-07-09 13:25:43.145 debug MIIO: Config: ip: token: mihome-vacuum.0 2022-07-09 13:25:43.144 debug Create State for deviceInfowifi_signal mihome-vacuum.0 2022-07-09 13:25:43.144 debug Create State for deviceInfofw_ver mihome-vacuum.0 2022-07-09 13:25:43.143 debug Create State for deviceInfomodel mihome-vacuum.0 2022-07-09 13:25:43.143 debug Create State for deviceInfomac mihome-vacuum.0 2022-07-09 13:25:43.142 debug Create State for deviceInfo mihome-vacuum.0 2022-07-09 13:25:43.115 debug load Map creator... true mihome-vacuum.0 2022-07-09 13:25:43.020 info starting. Version 3.4.2 in /opt/iobroker/node_modules/iobroker.mihome-vacuum, node: v16.16.0, js-controller: 4.0.23 mihome-vacuum.0 2022-07-09 13:25:42.587 debug Plugin sentry Initialize Plugin (enabled=true) host.raspberrypi 2022-07-09 13:25:40.337 info instance system.adapter.mihome-vacuum.0 started with pid 2397 host.raspberrypi 2022-07-09 13:25:37.776 info instance system.adapter.mihome-vacuum.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION) mihome-vacuum.0 2022-07-09 13:25:37.114 info Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason mihome-vacuum.0 2022-07-09 13:25:37.112 info terminating mihome-vacuum.0 2022-07-09 13:25:37.111 error Socket Close mihome-vacuum.0 2022-07-09 13:25:37.108 info Got terminate signal TERMINATE_YOURSELF host.raspberrypi 2022-07-09 13:25:37.111 info stopInstance system.adapter.mihome-vacuum.0 send kill signal host.raspberrypi 2022-07-09 13:25:37.099 info stopInstance system.adapter.mihome-vacuum.0 (force=false, process=true) -
@lustig29 sagte in MiVacuum Adapter läuft nicht mehr:
Helo message Timeout
Dein Stabubsauger ist verreist, nicht erreichbar.
Wie sehen die Einstellungen im Adapter dazu aus?
IP gesetzt? Token richtig?Bei mir startet der so:
2022-07-09 13:29:58.925 - info: mihome-vacuum.0 (236418) starting. Version 3.6.0 in /opt/iobroker/node_modules/iobroker.mihome-vacuum, node: v18.4.0, js-controller: 4.0.23 2022-07-09 13:29:59.004 - debug: mihome-vacuum.0 (236418) load Map creator... true 2022-07-09 13:29:59.047 - debug: mihome-vacuum.0 (236418) Create State for deviceInfo 2022-07-09 13:29:59.050 - debug: mihome-vacuum.0 (236418) Create State for deviceInfomac 2022-07-09 13:29:59.052 - debug: mihome-vacuum.0 (236418) Create State for deviceInfomodel 2022-07-09 13:29:59.053 - debug: mihome-vacuum.0 (236418) Create State for deviceInfofw_ver 2022-07-09 13:29:59.054 - debug: mihome-vacuum.0 (236418) Create State for deviceInfowifi_signal 2022-07-09 13:29:59.055 - debug: mihome-vacuum.0 (236418) MIIO: Config: ip:192.168.178.32 token: HIER_STAND_EIN_TOKEN 2022-07-09 13:29:59.061 - info: mihome-vacuum.0 (236418) IOT enabled, create state 2022-07-09 13:29:59.066 - debug: mihome-vacuum.0 (236418) server started on 0.0.0.0:53421 2022-07-09 13:29:59.077 - debug: mihome-vacuum.0 (236418) Receive <<< Helo <<< 2141002000000000046c689562c966c6ffffffffffffffffffffffffffffffff 2022-07-09 13:29:59.080 - debug: mihome-vacuum.0 (236418) MAIN: Connected to device, try to get model.. -
-
Bei meinen Eltern ist dasselbe Problem. Da stimmt aber die Ip....
mihome-vacuum.0 2022-07-09 13:48:08.595 debug Helo message Timeout mihome-vacuum.0 2022-07-09 13:48:06.592 debug server started on 0.0.0.0:53421 mihome-vacuum.0 2022-07-09 13:48:06.586 info IOT enabled, create state mihome-vacuum.0 2022-07-09 13:48:06.582 debug MIIO: Config: ip:192.168.0.232 token: mihome-vacuum.0 2022-07-09 13:48:06.580 debug Create State for deviceInfowifi_signal mihome-vacuum.0 2022-07-09 13:48:06.580 debug Create State for deviceInfofw_ver mihome-vacuum.0 2022-07-09 13:48:06.579 debug Create State for deviceInfomodel mihome-vacuum.0 2022-07-09 13:48:06.578 debug Create State for deviceInfomac mihome-vacuum.0 2022-07-09 13:48:06.577 debug Create State for deviceInfo mihome-vacuum.0 2022-07-09 13:48:06.542 debug load Map creator... true mihome-vacuum.0 2022-07-09 13:48:06.432 info starting. Version 3.4.2 in /opt/iobroker/node_modules/iobroker.mihome-vacuum, node: v16.16.0, js-controller: 4.0.23 mihome-vacuum.0 2022-07-09 13:48:06.016 debug Plugin sentry Initialize Plugin (enabled=true) mihome-vacuum.0 2022-07-09 13:48:05.826 debug States connected to redis: 127.0.0.1:9000 mihome-vacuum.0 2022-07-09 13:48:05.768 debug States create User PubSub Client mihome-vacuum.0 2022-07-09 13:48:05.766 debug States create System PubSub Client mihome-vacuum.0 2022-07-09 13:48:05.723 debug Redis States: Use Redis connection: 127.0.0.1:9000 mihome-vacuum.0 2022-07-09 13:48:05.678 debug Objects connected to redis: 127.0.0.1:9001 mihome-vacuum.0 2022-07-09 13:48:05.670 debug Objects client initialize lua scripts mihome-vacuum.0 2022-07-09 13:48:05.581 debug Objects create User PubSub Client mihome-vacuum.0 2022-07-09 13:48:05.580 debug Objects create System PubSub Client mihome-vacuum.0 2022-07-09 13:48:05.577 debug Objects client ready ... initialize now mihome-vacuum.0 2022-07-09 13:48:05.515 debug Redis Objects: Use Redis connection: 127.0.0.1:9001 -
Das dürfte aber auch aus der Netzwerk-Ecke kommen.
-
ihome-vacuum.0 2022-07-09 22:48:28.892 debug Create State for deviceInfo mihome-vacuum.0 2022-07-09 22:48:28.855 debug load Map creator... true mihome-vacuum.0 2022-07-09 22:48:28.762 info starting. Version 3.4.2 in /opt/iobroker/node_modules/iobroker.mihome-vacuum, node: v16.16.0, js-controller: 4.0.23 mihome-vacuum.0 2022-07-09 22:48:28.293 debug Plugin sentry Initialize Plugin (enabled=true) mihome-vacuum.0 2022-07-09 22:48:28.110 debug States connected to redis: 127.0.0.1:9000 mihome-vacuum.0 2022-07-09 22:48:28.052 debug States create User PubSub Client mihome-vacuum.0 2022-07-09 22:48:28.050 debug States create System PubSub Client mihome-vacuum.0 2022-07-09 22:48:28.015 debug Redis States: Use Redis connection: 127.0.0.1:9000 mihome-vacuum.0 2022-07-09 22:48:27.894 debug Objects connected to redis: 127.0.0.1:9001 mihome-vacuum.0 2022-07-09 22:48:27.863 debug Objects client initialize lua scripts mihome-vacuum.0 2022-07-09 22:48:27.717 debug Objects create User PubSub Client mihome-vacuum.0 2022-07-09 22:48:27.715 debug Objects create System PubSub Client mihome-vacuum.0 2022-07-09 22:48:27.712 debug Objects client ready ... initialize now mihome-vacuum.0 2022-07-09 22:48:27.642 debug Redis Objects: Use Redis connection: 127.0.0.1:9001 -
@lustig29
hatte ich auch. Was bei mir geholfen hat, war den S5max aus der Xiaomi App löschen, ausloggen und dann wieder eingeloggt und Gerät neu hinzugefügt.Dann die Zugangsdaten im Adapter neu eingegeben und siehe da, das Gerät wurde gefunden und auch das Token war dann neu. Dann ging auch der Adapter wieder auf grün.
