mihome vacuum adapter und Roborock S7 finden sich nicht

[bahnuhr]

@andibr sagte in mihome vacuum adapter und Roborock S7 finden sich nicht:

grüne Xiaomi Home App

kenn ich nicht.
Was soll das sein ?

Oder meinst du, weil das symbol grün ist.

[andibr]

@bahnuhr
Ja richtig Xiaomi Home App das Signet ist so grünlich. Wenn ich im Iob die gleich Login Daten verwende, bekomme ich mein S7 mit der lokalen IP zur Auswahl.

Dann habe ich den Token runterkopiert und die IP angegeben. An den Port habe ich nichts verändert. Nach ein Restart des Adapters gibt es 2xgrün und nur die Verbindung als letztes bleit rot.

[Thomas Braun]

@andibr

Schau dir den Start des Adapters im Log an.
Der Start kann auch ein paar Minuten dauern.

[bahnuhr]

@andibr

Was ich immer noch nicht weiß´, wo du dich angemeldet hast?
Deutsch oder China.

Ich meine mal gelesen zu haben, dass nur noch deutsch geht. Kann mich aber auch irren.

[bahnuhr]

@bahnuhr sagte in mihome vacuum adapter und Roborock S7 finden sich nicht:

also bei:
mi.com/de

[Thomas Braun]

@bahnuhr sagte in mihome vacuum adapter und Roborock S7 finden sich nicht:

Ich meine mal gelesen zu haben, dass nur noch deutsch geht. Kann mich aber auch irren.

Meine Rikscha fährt auch durch China.

[bahnuhr]

@thomas-braun

Ok, dann scheint china (wieder) zu gehen.

[andibr]

@bahnuhr

Ahh, auf dem Server "Germany"

[andibr]

Also hier das Log von 2x Adapter reboot:

2023-06-29 17:17:16.042 - info: mihome-vacuum.0 (17006) Got terminate signal TERMINATE_YOURSELF
2023-06-29 17:17:16.042 - info: host.iobroker stopInstance system.adapter.mihome-vacuum.0 send kill signal
2023-06-29 17:17:16.045 - error: mihome-vacuum.0 (17006) Socket Close
2023-06-29 17:17:16.046 - info: mihome-vacuum.0 (17006) terminating
2023-06-29 17:17:16.047 - info: mihome-vacuum.0 (17006) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
2023-06-29 17:17:16.917 - info: host.iobroker instance system.adapter.mihome-vacuum.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
2023-06-29 17:17:19.307 - info: host.iobroker instance system.adapter.mihome-vacuum.0 started with pid 26848
2023-06-29 17:17:22.269 - debug: mihome-vacuum.0 (26848) Redis Objects: Use Redis connection: 0.0.0.0:9001
2023-06-29 17:17:22.334 - debug: mihome-vacuum.0 (26848) Objects client ready ... initialize now
2023-06-29 17:17:22.337 - debug: mihome-vacuum.0 (26848) Objects create System PubSub Client
2023-06-29 17:17:22.339 - debug: mihome-vacuum.0 (26848) Objects create User PubSub Client
2023-06-29 17:17:22.474 - debug: mihome-vacuum.0 (26848) Objects client initialize lua scripts
2023-06-29 17:17:22.488 - debug: mihome-vacuum.0 (26848) Objects connected to redis: 0.0.0.0:9001
2023-06-29 17:17:22.535 - debug: mihome-vacuum.0 (26848) Redis States: Use Redis connection: 0.0.0.0:9000
2023-06-29 17:17:22.563 - debug: mihome-vacuum.0 (26848) States create System PubSub Client
2023-06-29 17:17:22.564 - debug: mihome-vacuum.0 (26848) States create User PubSub Client
2023-06-29 17:17:22.614 - debug: mihome-vacuum.0 (26848) States connected to redis: 0.0.0.0:9000
2023-06-29 17:17:22.795 - debug: mihome-vacuum.0 (26848) Plugin sentry Initialize Plugin (enabled=true)
2023-06-29 17:17:23.222 - info: mihome-vacuum.0 (26848) starting. Version 3.11.0 in /opt/iobroker/node_modules/iobroker.mihome-vacuum, node: v18.16.1, js-controller: 4.0.24
2023-06-29 17:17:23.288 - debug: mihome-vacuum.0 (26848) Create State for deviceInfo
2023-06-29 17:17:23.288 - debug: mihome-vacuum.0 (26848) Create State for deviceInfomac
2023-06-29 17:17:23.289 - debug: mihome-vacuum.0 (26848) Create State for deviceInfomodel
2023-06-29 17:17:23.290 - debug: mihome-vacuum.0 (26848) Create State for deviceInfofw_ver
2023-06-29 17:17:23.290 - debug: mihome-vacuum.0 (26848) Create State for deviceInfowifi_signal
2023-06-29 17:17:23.291 - debug: mihome-vacuum.0 (26848) Create State for deviceInfounsupported
2023-06-29 17:17:23.292 - debug: mihome-vacuum.0 (26848) MIIO: Config: ip:192.168.30.51 token: 6c514a4e63XXXXXXXXX
2023-06-29 17:17:23.296 - info: mihome-vacuum.0 (26848) IOT enabled, create state
2023-06-29 17:17:23.301 - debug: mihome-vacuum.0 (26848) server started on 0.0.0.0:53422
2023-06-29 17:17:25.304 - debug: mihome-vacuum.0 (26848) Helo message Timeout
2023-06-29 17:17:37.306 - debug: mihome-vacuum.0 (26848) Helo message Timeout
2023-06-29 17:17:49.308 - debug: mihome-vacuum.0 (26848) Helo message Timeout
2023-06-29 17:18:01.308 - debug: mihome-vacuum.0 (26848) Helo message Timeout
2023-06-29 17:18:13.308 - debug: mihome-vacuum.0 (26848) Helo message Timeout
2023-06-29 17:18:25.310 - debug: mihome-vacuum.0 (26848) Helo message Timeout
2023-06-29 17:18:37.313 - debug: mihome-vacuum.0 (26848) Helo message Timeout
2023-06-29 17:18:49.315 - debug: mihome-vacuum.0 (26848) Helo message Timeout
2023-06-29 17:19:01.317 - debug: mihome-vacuum.0 (26848) Helo message Timeout
2023-06-29 17:19:13.320 - debug: mihome-vacuum.0 (26848) Helo message Timeout
2023-06-29 17:19:25.322 - debug: mihome-vacuum.0 (26848) Helo message Timeout
2023-06-29 17:19:37.324 - debug: mihome-vacuum.0 (26848) Helo message Timeout
2023-06-29 17:19:38.952 - info: host.iobroker stopInstance system.adapter.mihome-vacuum.0 (force=false, process=true)
2023-06-29 17:19:38.958 - info: mihome-vacuum.0 (26848) Got terminate signal TERMINATE_YOURSELF
2023-06-29 17:19:38.958 - info: host.iobroker stopInstance system.adapter.mihome-vacuum.0 send kill signal
2023-06-29 17:19:38.961 - error: mihome-vacuum.0 (26848) Socket Close
2023-06-29 17:19:38.962 - info: mihome-vacuum.0 (26848) terminating
2023-06-29 17:19:38.963 - debug: mihome-vacuum.0 (26848) Plugin sentry destroyed
2023-06-29 17:19:38.964 - info: mihome-vacuum.0 (26848) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
2023-06-29 17:19:39.573 - info: host.iobroker instance system.adapter.mihome-vacuum.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
2023-06-29 17:19:42.056 - info: host.iobroker instance system.adapter.mihome-vacuum.0 started with pid 26911
2023-06-29 17:19:43.541 - debug: mihome-vacuum.0 (26911) Redis Objects: Use Redis connection: 0.0.0.0:9001
2023-06-29 17:19:43.607 - debug: mihome-vacuum.0 (26911) Objects client ready ... initialize now
2023-06-29 17:19:43.610 - debug: mihome-vacuum.0 (26911) Objects create System PubSub Client
2023-06-29 17:19:43.611 - debug: mihome-vacuum.0 (26911) Objects create User PubSub Client
2023-06-29 17:19:43.704 - debug: mihome-vacuum.0 (26911) Objects client initialize lua scripts
2023-06-29 17:19:43.713 - debug: mihome-vacuum.0 (26911) Objects connected to redis: 0.0.0.0:9001
2023-06-29 17:19:43.765 - debug: mihome-vacuum.0 (26911) Redis States: Use Redis connection: 0.0.0.0:9000
2023-06-29 17:19:43.801 - debug: mihome-vacuum.0 (26911) States create System PubSub Client
2023-06-29 17:19:43.802 - debug: mihome-vacuum.0 (26911) States create User PubSub Client
2023-06-29 17:19:43.858 - debug: mihome-vacuum.0 (26911) States connected to redis: 0.0.0.0:9000
2023-06-29 17:19:44.018 - debug: mihome-vacuum.0 (26911) Plugin sentry Initialize Plugin (enabled=true)
2023-06-29 17:19:44.399 - info: mihome-vacuum.0 (26911) starting. Version 3.11.0 in /opt/iobroker/node_modules/iobroker.mihome-vacuum, node: v18.16.1, js-controller: 4.0.24
2023-06-29 17:19:44.473 - debug: mihome-vacuum.0 (26911) Create State for deviceInfo
2023-06-29 17:19:44.474 - debug: mihome-vacuum.0 (26911) Create State for deviceInfomac
2023-06-29 17:19:44.475 - debug: mihome-vacuum.0 (26911) Create State for deviceInfomodel
2023-06-29 17:19:44.476 - debug: mihome-vacuum.0 (26911) Create State for deviceInfofw_ver
2023-06-29 17:19:44.476 - debug: mihome-vacuum.0 (26911) Create State for deviceInfowifi_signal
2023-06-29 17:19:44.477 - debug: mihome-vacuum.0 (26911) Create State for deviceInfounsupported
2023-06-29 17:19:44.478 - debug: mihome-vacuum.0 (26911) MIIO: Config: ip:192.168.30.51 token: 6c514a4e63XXXXXXXXX
2023-06-29 17:19:44.485 - info: mihome-vacuum.0 (26911) IOT enabled, create state
2023-06-29 17:19:44.490 - debug: mihome-vacuum.0 (26911) server started on 0.0.0.0:53421
2023-06-29 17:19:46.493 - debug: mihome-vacuum.0 (26911) Helo message Timeout
2023-06-29 17:19:58.495 - debug: mihome-vacuum.0 (26911) Helo message Timeout

So sehen die Einstellung aus:

und

[deifel]

@andibr

Gibts hier mittlerweile eine Lösung? Habe dasselbe Problem mit einem S6...

[David G.]

@andibr

Warum nimmst du nicht die Roborock App und den Roborock-Adapter?

Würde ich empfehlen.....