Kein Connect, Adapter bleibt gelb, mihome-vacuum

[TTBerlin]

Hallo zusammen,
ich habe den Roborock S6 pure recht neu und hatte auch den Adapter 2.1.1 installiert und alles hat funktioniert. Heute morgen habe ich im Adapter in den Datenpunkten "clean Room" der einzelnen Räume die Buttons betätigt, um den Datenpunkten Klarnamen der einzelnen Räume zuzuweisen. Dabei wechselte der Adapter irgendwann auf gelb und bis jetzt ist es mir nicht gelungen den Adapter wieder auf grün zu bekommen. Habe schon eine zweite Instanz angelegt, ist aber das Gleiche. Kann vielleicht jemand helfen? Hier mal ein Auszug aus dem log

2021-03-01 16:49:13.908 - info: host.iobroker "system.adapter.mihome-vacuum.0" enabled
2021-03-01 16:49:14.088 - info: host.iobroker instance system.adapter.mihome-vacuum.0 started with pid 15196
2021-03-01 16:49:15.662 - debug: mihome-vacuum.0 (15196) Redis Objects: Use Redis connection: 127.0.0.1:9001
2021-03-01 16:49:15.791 - debug: mihome-vacuum.0 (15196) Objects client ready ... initialize now
2021-03-01 16:49:15.863 - debug: mihome-vacuum.0 (15196) Objects create System PubSub Client
2021-03-01 16:49:15.867 - debug: mihome-vacuum.0 (15196) Objects create User PubSub Client
2021-03-01 16:49:15.870 - debug: mihome-vacuum.0 (15196) Objects client initialize lua scripts
2021-03-01 16:49:15.943 - debug: mihome-vacuum.0 (15196) Objects connected to redis: 127.0.0.1:9001
2021-03-01 16:49:15.956 - debug: mihome-vacuum.0 (15196) objectDB connected
2021-03-01 16:49:15.959 - debug: mihome-vacuum.0 (15196) Redis States: Use Redis connection: 127.0.0.1:9000
2021-03-01 16:49:16.066 - debug: mihome-vacuum.0 (15196) States create System PubSub Client
2021-03-01 16:49:16.068 - debug: mihome-vacuum.0 (15196) States create User PubSub Client
2021-03-01 16:49:16.199 - debug: mihome-vacuum.0 (15196) States connected to redis: 127.0.0.1:9000
2021-03-01 16:49:16.200 - debug: mihome-vacuum.0 (15196) statesDB connected
2021-03-01 16:49:21.012 - info: mihome-vacuum.0 (15196) starting. Version 2.1.1 in /opt/iobroker/node_modules/iobroker.mihome-vacuum, node: v12.20.1, js-controller: 3.2.16
2021-03-01 16:49:21.081 - debug: mihome-vacuum.0 (15196) load Map creator... true
2021-03-01 16:49:21.082 - debug: mihome-vacuum.0 (15196) Xiaomi Cloud: Logging in
2021-03-01 16:49:21.096 - info: mihome-vacuum.0 (15196) Expert mode disabled, states deleted
2021-03-01 16:49:21.097 - info: mihome-vacuum.0 (15196) Create state clean_home for controlling by cloud adapter
2021-03-01 16:49:21.108 - debug: mihome-vacuum.0 (15196) server started on 0.0.0.0:53421
2021-03-01 16:49:21.170 - debug: mihome-vacuum.0 (15196) Receive <<< Helo <<< 2131002000000000131bde51603d0d01ffffffffffffffffffffffffffffffff
2021-03-01 16:49:21.171 - info: mihome-vacuum.0 (15196) connecting, this can take up to 10 minutes ...
2021-03-01 16:49:21.173 - debug: mihome-vacuum.0 (15196) sendTo "getStatus" to system.adapter.mihome-vacuum.0 from system.adapter.mihome-vacuum.0
2021-03-01 16:49:21.177 - info: mihome-vacuum.0 (15196) New generation or new fw(3.5.8,1204) detected, create new states goto and zoneclean
2021-03-01 16:49:21.208 - debug: mihome-vacuum.0 (15196) sendMsg[1] >>> {"id":1,"method":"get_status"}
2021-03-01 16:49:21.277 - debug: mihome-vacuum.0 (15196) No suitable Lua script, fallback to keys!: function(doc) { if (doc.type === 'state') emit(doc._id, doc) }
2021-03-01 16:49:21.728 - info: mihome-vacuum.0 (15196) set nächster Timer: Nicht verfügbar
2021-03-01 16:49:26.248 - debug: mihome-vacuum.0 (15196) Xiaomi Cloud: Login successful
2021-03-01 16:49:26.251 - debug: mihome-vacuum.0 (15196) sendMsg[2] >>> {"id":1,"method":"get_status"}
2021-03-01 16:49:31.252 - debug: mihome-vacuum.0 (15196) sendMsg[3] >>> {"id":1,"method":"get_status"}
2021-03-01 16:49:36.252 - debug: mihome-vacuum.0 (15196) no answer for id:1 received, giving up
2021-03-01 16:49:36.253 - debug: mihome-vacuum.0 (15196) sendTo "getStatus" to system.adapter.mihome-vacuum.0 from system.adapter.mihome-vacuum.0
2021-03-01 16:49:41.136 - debug: mihome-vacuum.0 (15196) Receive <<< Helo <<< 2131002000000000131bde51603d0d15ffffffffffffffffffffffffffffffff
2021-03-01 16:49:41.137 - info: mihome-vacuum.0 (15196) connecting, this can take up to 10 minutes ...
2021-03-01 16:49:41.138 - debug: mihome-vacuum.0 (15196) sendTo "getStatus" to system.adapter.mihome-vacuum.0 from system.adapter.mihome-vacuum.0
2021-03-01 16:49:41.142 - debug: mihome-vacuum.0 (15196) sendMsg[1] >>> {"id":2,"method":"get_status"}
2021-03-01 16:49:46.143 - debug: mihome-vacuum.0 (15196) sendMsg[2] >>> {"id":2,"method":"get_status"}
2021-03-01 16:49:51.144 - debug: mihome-vacuum.0 (15196) sendMsg[3] >>> {"id":2,"method":"get_status"}
2021-03-01 16:49:56.145 - debug: mihome-vacuum.0 (15196) no answer for id:2 received, giving up
2021-03-01 16:49:56.146 - debug: mihome-vacuum.0 (15196) sendTo "getStatus" to system.adapter.mihome-vacuum.0 from system.adapter.mihome-vacuum.0
2021-03-01 16:50:01.109 - debug: mihome-vacuum.0 (15196) Receive <<< Helo <<< 2131002000000000131bde51603d0d29ffffffffffffffffffffffffffffffff
2021-03-01 16:50:01.109 - info: mihome-vacuum.0 (15196) connecting, this can take up to 10 minutes ...
2021-03-01 16:50:01.110 - debug: mihome-vacuum.0 (15196) sendTo "getStatus" to system.adapter.mihome-vacuum.0 from system.adapter.mihome-vacuum.0
2021-03-01 16:50:01.114 - debug: mihome-vacuum.0 (15196) sendMsg[1] >>> {"id":3,"method":"get_status"}
2021-03-01 16:50:06.115 - debug: mihome-vacuum.0 (15196) sendMsg[2] >>> {"id":3,"method":"get_status"}
2021-03-01 16:50:11.116 - debug: mihome-vacuum.0 (15196) sendMsg[3] >>> {"id":3,"method":"get_status"}
2021-03-01 16:50:16.117 - debug: mihome-vacuum.0 (15196) no answer for id:3 received, giving up
2021-03-01 16:50:16.118 - debug: mihome-vacuum.0 (15196) sendTo "getStatus" to system.adapter.mihome-vacuum.0 from system.adapter.mihome-vacuum.0
2021-03-01 16:50:21.114 - debug: mihome-vacuum.0 (15196) Receive <<< Helo <<< 2131002000000000131bde51603d0d3dffffffffffffffffffffffffffffffff
2021-03-01 16:50:21.115 - info: mihome-vacuum.0 (15196) connecting, this can take up to 10 minutes ...
2021-03-01 16:50:21.115 - debug: mihome-vacuum.0 (15196) sendTo "getStatus" to system.adapter.mihome-vacuum.0 from system.adapter.mihome-vacuum.0
2021-03-01 16:50:21.229 - debug: mihome-vacuum.0 (15196) sendMsg[1] >>> {"id":4,"method":"get_status"}
2021-03-01 16:50:26.230 - debug: mihome-vacuum.0 (15196) sendMsg[2] >>> {"id":4,"method":"get_status"}
2021-03-01 16:50:31.231 - debug: mihome-vacuum.0 (15196) sendMsg[3] >>> {"id":4,"method":"get_status"}
2021-03-01 16:50:36.234 - debug: mihome-vacuum.0 (15196) no answer for id:4 received, giving up
2021-03-01 16:50:36.235 - debug: mihome-vacuum.0 (15196) sendTo "getStatus" to system.adapter.mihome-vacuum.0 from system.adapter.mihome-vacuum.0

lieben Dank im Voraus

Zusatz: Gerade, als ich denBeitrag hier fertig hatte, wurde der Adapter grün Mal sehen, ob das auf Dauer so bleibt....

[Thomas Braun]

@ttberlin sagte in Kein Connect, Adapter bleibt gelb, mihome-vacuum:

connecting, this can take up to 10 minutes ...

Kann aber auch noch länger dauern. Hatte schon mal eine Stunde drin.

[TTBerlin]

@thomas-braun Danke!! Hm, na ja..in meinem Fall waren es über 6 Stunden...