S7 Verbindung mit ioBroker Klappt nicht

Question

S7 Verbindung mit ioBroker Klappt nicht

djhesepe opened this issue 2 years ago · 22 comments

Moin,

ich hab den Adapter installiert. Token etc konnte auch ausgelesen und wird unter mein Devices angezeigt.

Hab unten die IP Adresse eingegeben (unter Token) aber die Instanz kann keine Verbindung zum Gerät herstellen.
Woran kann das liegen?

Fritzbox hat die Interne IP 192.168.178.1 und der Roboter 192.168.178.97

Ich hab was gelesen von unterschiedlichen Subnetzmasken. Die Fritzbox befindet sich Standard gemäß in der 255.255.255.0 aber wie kriege ich die des Roborock S7 heraus?

Schönes Wochenende

Answer 1 · 2023-01-07T11:37:03.000Z

255.255.255.0 ist subnet mask, befinden sich also beide im selben subnet.
Nicht manuell eintragen, oben dein gerät suswählen, dann wird es automatisch eingetragen. Gerät muss über die mihome app verbjnden sein, nicht roborock app.
Wenn es dann noch probleme gibt, brauche ich ein debug log

Answer 2 · 2023-01-07T11:51:48.000Z

Moin,

Wenn ich oben mein Gerät auswähle füllt er unten nichts automatisch aus.
hab die Instanz noch einmal gelöscht und neu installiert, nun wenn ich meine Daten eingebe und auf GET Device klickt steht da das ich die Instanz starten muss, aber diese läuft schon?

Anbei der Code aus dem LOG vor dem Löschen:

2023-01-07 12:46:47.307 - info: host.iobroker-pi "system.adapter.telegram.0" disabled

2023-01-07 12:46:47.308 - info: host.iobroker-pi stopInstance system.adapter.telegram.0 (force=false, process=true)
2023-01-07 12:46:47.423 - info: telegram.0 (634) Got terminate signal TERMINATE_YOURSELF
2023-01-07 12:46:47.426 - info: host.iobroker-pi stopInstance system.adapter.telegram.0 send kill signal
2023-01-07 12:46:47.928 - info: telegram.0 (634) terminating
2023-01-07 12:46:47.930 - info: telegram.0 (634) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
2023-01-07 12:46:48.428 - info: host.iobroker-pi stopInstance system.adapter.telegram.0 killing pid 634
2023-01-07 12:46:48.564 - info: host.iobroker-pi instance system.adapter.telegram.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
2023-01-07 12:46:51.241 - info: host.iobroker-pi stopInstance system.adapter.mihome-vacuum.0 (force=false, process=true)
2023-01-07 12:46:51.255 - info: host.iobroker-pi stopInstance system.adapter.mihome-vacuum.0 send kill signal
2023-01-07 12:46:51.255 - info: mihome-vacuum.0 (1136) Got terminate signal TERMINATE_YOURSELF
2023-01-07 12:46:51.262 - error: mihome-vacuum.0 (1136) Socket Close
2023-01-07 12:46:51.264 - info: mihome-vacuum.0 (1136) terminating
2023-01-07 12:46:51.268 - info: mihome-vacuum.0 (1136) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
2023-01-07 12:46:51.849 - info: host.iobroker-pi instance system.adapter.mihome-vacuum.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
2023-01-07 12:46:54.395 - info: host.iobroker-pi instance system.adapter.mihome-vacuum.0 started with pid 1151
2023-01-07 12:46:57.235 - info: mihome-vacuum.0 (1151) starting. Version 3.8.6 in /opt/iobroker/node_modules/iobroker.mihome-vacuum, node: v18.12.1, js-controller: 4.0.24
2023-01-07 12:46:57.364 - info: mihome-vacuum.0 (1151) IOT enabled, create state
2023-01-07 12:47:07.498 - error: mihome-vacuum.0 (1151) YOUR DEVICE IS CONNECTED BUT DID NOT ANSWER YET - CONNECTION CAN TAKE UP TO 10 MINUTES - PLEASE BE PATIENT AND DO NOT TURN THE ADAPTER OFF
2023-01-07 12:47:07.499 - warn: mihome-vacuum.0 (1151) No Answer for DeviceModel use old one
2023-01-07 12:47:07.500 - warn: mihome-vacuum.0 (1151) No Answer for DeviceModel use model from Config
2023-01-07 12:47:07.518 - info: mihome-vacuum.0 (1151) select standard vacuum protocol....
2023-01-07 12:47:08.236 - info: mihome-vacuum.0 (1151) settest next timer: not available

Edit: jetzt konnte ich auf GET DEVICES klicken aber sobald ich das gerät aus der liste auswähle fügt er bei Token und IP nichts ein.

Answer 3 · 2023-01-07T12:10:30.000Z

Das ist seltsam, wenn ich ein gerät aus der liste auswähle, schreibt er unten die IP und den Token rein. Wenn das nicht klappt, wäre es interressant, welchen Browser du verwendest und ob der fehler in der console ausgibt.
Aber wenn du beides manuell eingetragen hast, ist es ja auch erstmal ok. Dann warte nochmal die 10 minuten ab. Ggf. sonst den Adapter nochmal auf debug stellen und hier posten

Answer 4 · 2023-01-07T12:13:52.000Z

@dirkhe ich verwende den Safari Browser, hab das aber auch mal mit Google Chrome Probiert, damit klappt das auch nicht.
wie stelle ich den Adapter auf Debug?
So ganz fit bin ich noch nicht damit. bzw hab das noch nie gebraucht, weil ich jeden Fehler bis jetzt immer hinbekommen hab, bis auf diesen.

Answer 5 · 2023-01-07T13:16:11.000Z

dirkhe commented 2 years ago

Answer 6 · 2023-01-07T13:16:52.000Z

Aber er zeigt dir schon den token und die ip in der geräteliste an?

Answer 7 · 2023-01-07T13:36:05.000Z

in der Geräte liste wird der aufgeführt. Der Token und IP unten hab ich manuell eingefügt weil das anders nicht ging

Answer 8 · 2023-01-07T13:38:21.000Z

ok, das wird dann ein BrowserProblem sein, vermute ich mal. Lösche mal den screenshot, deine email kann man auch sehen. Dann schicke mal das debug log. Und du bist auch mit der miHome app verbunden?

Answer 9 · 2023-01-07T13:42:43.000Z

a

ber das mit Browser kann ja nicht sein. Safari, Google Chrome und grade noch FireFox auf meinem Macbook installier und überall das gleiche. Kann das Gerät in der Device Liste sehen, aber nicht auswählen.
Laut Adapter bin ich mit dem Konto verbunden.
Unter Objekte -> mihome-vaccum -> 0 -> DevicesInfo kann ich die Macadresse und das Modell des Roboters einsehen. alles weitere aber nicht. da zeigt er nur (NULL) an

edit: mit der MiHome app kann ich den Roboter steuern

Answer 10 · 2023-01-07T13:43:42.000Z

debuglog!
Firewall hast du auch augeschlossen?

Answer 11 · 2023-01-07T13:46:34.000Z

was meinst du mit Debug Log?
aus dem Protokoll auf Debug umstellen und den Log hier posten?

Firewall schau ich mal in meiner FritzBox eben nach bzw deaktiviere die einmal zum test

Answer 12 · 2023-01-07T13:47:47.000Z

Ja, im debuglog kann man sehen, was der adapter macht und wo er scheitert, alles andere ist Raten

Answer 13 · 2023-01-07T13:52:13.000Z

Hier mal der Aktuelle Log:

2023-01-07 14:50:19.772 - info: host.iobroker-pi stopInstance system.adapter.mihome-vacuum.0 (force=false, process=true)
2023-01-07 14:50:19.938 - info: host.iobroker-pi stopInstance system.adapter.mihome-vacuum.0 send kill signal
2023-01-07 14:50:19.931 - info: mihome-vacuum.0 (1422) Got terminate signal TERMINATE_YOURSELF
2023-01-07 14:50:19.935 - error: mihome-vacuum.0 (1422) Socket Close
2023-01-07 14:50:19.937 - info: mihome-vacuum.0 (1422) terminating
2023-01-07 14:50:19.939 - info: mihome-vacuum.0 (1422) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
2023-01-07 14:50:20.564 - info: host.iobroker-pi instance system.adapter.mihome-vacuum.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
2023-01-07 14:50:23.126 - info: host.iobroker-pi instance system.adapter.mihome-vacuum.0 started with pid 1696
2023-01-07 14:50:26.339 - info: mihome-vacuum.0 (1696) starting. Version 3.8.6 in /opt/iobroker/node_modules/iobroker.mihome-vacuum, node: v18.12.1, js-controller: 4.0.24
2023-01-07 14:50:26.436 - info: mihome-vacuum.0 (1696) IOT enabled, create state
2023-01-07 14:50:36.503 - error: mihome-vacuum.0 (1696) YOUR DEVICE IS CONNECTED BUT DID NOT ANSWER YET - CONNECTION CAN TAKE UP TO 10 MINUTES - PLEASE BE PATIENT AND DO NOT TURN THE ADAPTER OFF
2023-01-07 14:50:36.505 - warn: mihome-vacuum.0 (1696) No Answer for DeviceModel use old one
2023-01-07 14:50:36.506 - warn: mihome-vacuum.0 (1696) No Answer for DeviceModel use model from Config
2023-01-07 14:50:36.540 - info: mihome-vacuum.0 (1696) select standard vacuum protocol....
2023-01-07 14:50:37.167 - info: mihome-vacuum.0 (1696) settest next timer: not available

Answer 14 · 2023-01-07T13:53:32.000Z

Das Debug log bitte, must du vorher umstellen, wie auf dem Sceenshot von mir zu sehen

Answer 15 · 2023-01-07T13:57:20.000Z

Wenn ich das aber von "Info" auf "Debug" stelle steht dort (wo bei dein Screen WARN steht Info/Debug). Den Log hänge ich dir nochmal dran, steht aber irgendwie das gleiche wie vorher?

Bei Firewall ist nur der NetBIOS-Filter aktiv, Teredo-Filter aktiv und WPAD-Filter aktiv.
desweiteren hat der Roborock Selbständige Freigabe zur Portöffnung und die PI auch.

2023-01-07 14:55:29.203 - error: mihome-vacuum.0 (1719) YOUR DEVICE IS CONNECTED BUT DID NOT ANSWER YET - CONNECTION CAN TAKE UP TO 10 MINUTES - PLEASE BE PATIENT AND DO NOT TURN THE ADAPTER OFF

2023-01-07 14:55:29.204 - warn: mihome-vacuum.0 (1719) No Answer for DeviceModel use old one
2023-01-07 14:55:29.206 - warn: mihome-vacuum.0 (1719) No Answer for DeviceModel use model from Config
2023-01-07 14:55:29.240 - info: mihome-vacuum.0 (1719) select standard vacuum protocol....
2023-01-07 14:55:29.865 - info: mihome-vacuum.0 (1719) settest next timer: not available
2023-01-07 14:55:30.460 - info: host.iobroker-pi stopInstance system.adapter.mihome-vacuum.0 (force=false, process=true)
2023-01-07 14:55:30.652 - info: mihome-vacuum.0 (1719) Got terminate signal TERMINATE_YOURSELF
2023-01-07 14:55:30.656 - error: mihome-vacuum.0 (1719) Socket Close
2023-01-07 14:55:30.658 - info: mihome-vacuum.0 (1719) terminating
2023-01-07 14:55:30.660 - info: mihome-vacuum.0 (1719) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
2023-01-07 14:55:30.683 - info: host.iobroker-pi stopInstance system.adapter.mihome-vacuum.0 send kill signal
2023-01-07 14:55:31.279 - info: host.iobroker-pi instance system.adapter.mihome-vacuum.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
2023-01-07 14:55:33.943 - info: host.iobroker-pi instance system.adapter.mihome-vacuum.0 started with pid 1735
2023-01-07 14:55:37.111 - info: mihome-vacuum.0 (1735) starting. Version 3.8.6 in /opt/iobroker/node_modules/iobroker.mihome-vacuum, node: v18.12.1, js-controller: 4.0.24
2023-01-07 14:55:37.192 - info: mihome-vacuum.0 (1735) IOT enabled, create state
2023-01-07 14:55:47.327 - error: mihome-vacuum.0 (1735) YOUR DEVICE IS CONNECTED BUT DID NOT ANSWER YET - CONNECTION CAN TAKE UP TO 10 MINUTES - PLEASE BE PATIENT AND DO NOT TURN THE ADAPTER OFF
2023-01-07 14:55:47.329 - warn: mihome-vacuum.0 (1735) No Answer for DeviceModel use old one
2023-01-07 14:55:47.330 - warn: mihome-vacuum.0 (1735) No Answer for DeviceModel use model from Config
2023-01-07 14:55:47.365 - info: mihome-vacuum.0 (1735) select standard vacuum protocol....
2023-01-07 14:55:47.992 - info: mihome-vacuum.0 (1735) settest next timer: not available

Answer 16 · 2023-01-07T13:59:39.000Z

2023-01-07 14:58:01.287 - info: mihome-vacuum.0 (1754) settest next timer: not available

2023-01-07 14:58:02.876 - debug: mihome-vacuum.0 (1754) your device is connected, but didn't answer yet - sometime connection is broken and can take up to 10 Minutes
2023-01-07 14:58:02.878 - debug: mihome-vacuum.0 (1754) Message= {"id":7,"method":"get_network_info"}
2023-01-07 14:58:04.881 - debug: mihome-vacuum.0 (1754) your device is connected, but didn't answer yet - sometime connection is broken and can take up to 10 Minutes
2023-01-07 14:58:04.883 - debug: mihome-vacuum.0 (1754) Message= {"id":8,"method":"get_sound_volume"}
2023-01-07 14:58:06.888 - debug: mihome-vacuum.0 (1754) your device is connected, but didn't answer yet - sometime connection is broken and can take up to 10 Minutes
2023-01-07 14:58:06.890 - debug: mihome-vacuum.0 (1754) Message= {"id":9,"method":"get_multi_maps_list"}
2023-01-07 14:58:08.894 - debug: mihome-vacuum.0 (1754) your device is connected, but didn't answer yet - sometime connection is broken and can take up to 10 Minutes
2023-01-07 14:58:08.896 - debug: mihome-vacuum.0 (1754) Startup: getMultiMapsList Answer: true
2023-01-07 14:58:08.897 - debug: mihome-vacuum.0 (1754) Startup: Delete getMultiMapsList
2023-01-07 14:58:08.898 - debug: mihome-vacuum.0 (1754) Message= {"id":10,"method":"get_clean_summary"}
2023-01-07 14:58:10.657 - debug: mihome-vacuum.0 (1754) Receive <<< Helo <<< 21310020000000001bc1b5b3000027a4ffffffffffffffffffffffffffffffff
2023-01-07 14:58:10.658 - debug: mihome-vacuum.0 (1754) Time difference between Mihome Vacuum and ioBroker: -1673089742 sec
2023-01-07 14:58:10.902 - debug: mihome-vacuum.0 (1754) your device is connected, but didn't answer yet - sometime connection is broken and can take up to 10 Minutes
2023-01-07 14:58:10.903 - debug: mihome-vacuum.0 (1754) Startup: setGetCleanSummary Answer: false
2023-01-07 14:58:10.905 - debug: mihome-vacuum.0 (1754) Message= {"id":11,"method":"get_consumable"}
2023-01-07 14:58:12.908 - debug: mihome-vacuum.0 (1754) your device is connected, but didn't answer yet - sometime connection is broken and can take up to 10 Minutes
2023-01-07 14:58:12.909 - debug: mihome-vacuum.0 (1754) Startup: setGetConsumable Answer: false
2023-01-07 14:58:12.910 - debug: mihome-vacuum.0 (1754) Message= {"id":12,"method":"get_map_v1"}
2023-01-07 14:58:14.912 - debug: mihome-vacuum.0 (1754) your device is connected, but didn't answer yet - sometime connection is broken and can take up to 10 Minutes
2023-01-07 14:58:15.214 - debug: mihome-vacuum.0 (1754) Message= {"id":13,"method":"get_map_v1"}
2023-01-07 14:58:17.217 - debug: mihome-vacuum.0 (1754) your device is connected, but didn't answer yet - sometime connection is broken and can take up to 10 Minutes
2023-01-07 14:58:17.519 - debug: mihome-vacuum.0 (1754) Message= {"id":14,"method":"get_map_v1"}
2023-01-07 14:58:19.522 - debug: mihome-vacuum.0 (1754) your device is connected, but didn't answer yet - sometime connection is broken and can take up to 10 Minutes
2023-01-07 14:58:19.824 - debug: mihome-vacuum.0 (1754) Message= {"id":15,"method":"get_map_v1"}
2023-01-07 14:58:20.682 - debug: mihome-vacuum.0 (1754) Receive <<< Helo <<< 21310020000000001bc1b5b3000027aeffffffffffffffffffffffffffffffff
2023-01-07 14:58:20.683 - debug: mihome-vacuum.0 (1754) Time difference between Mihome Vacuum and ioBroker: -1673089742 sec
2023-01-07 14:58:21.827 - debug: mihome-vacuum.0 (1754) your device is connected, but didn't answer yet - sometime connection is broken and can take up to 10 Minutes
2023-01-07 14:58:22.129 - debug: mihome-vacuum.0 (1754) Message= {"id":16,"method":"get_map_v1"}
2023-01-07 14:58:24.132 - debug: mihome-vacuum.0 (1754) your device is connected, but didn't answer yet - sometime connection is broken and can take up to 10 Minutes
2023-01-07 14:58:30.715 - debug: mihome-vacuum.0 (1754) Receive <<< Helo <<< 21310020000000001bc1b5b3000027b8ffffffffffffffffffffffffffffffff
2023-01-07 14:58:30.717 - debug: mihome-vacuum.0 (1754) Time difference between Mihome Vacuum and ioBroker: -1673089742 sec
2023-01-07 14:58:40.759 - debug: mihome-vacuum.0 (1754) Receive <<< Helo <<< 21310020000000001bc1b5b3000027c2ffffffffffffffffffffffffffffffff
2023-01-07 14:58:40.760 - debug: mihome-vacuum.0 (1754) Time difference between Mihome Vacuum and ioBroker: -1673089742 sec
2023-01-07 14:58:44.435 - debug: mihome-vacuum.0 (1754) get params for stock Vacuum
2023-01-07 14:58:44.436 - debug: mihome-vacuum.0 (1754) Message= {"id":17,"method":"get_status"}
2023-01-07 14:58:46.438 - debug: mihome-vacuum.0 (1754) your device is connected, but didn't answer yet - sometime connection is broken and can take up to 10 Minutes
2023-01-07 14:58:46.440 - debug: mihome-vacuum.0 (1754) Message= {"id":18,"method":"get_network_info"}
2023-01-07 14:58:48.443 - debug: mihome-vacuum.0 (1754) your device is connected, but didn't answer yet - sometime connection is broken and can take up to 10 Minutes
2023-01-07 14:58:48.445 - debug: mihome-vacuum.0 (1754) Message= {"id":19,"method":"get_sound_volume"}
2023-01-07 14:58:50.447 - debug: mihome-vacuum.0 (1754) your device is connected, but didn't answer yet - sometime connection is broken and can take up to 10 Minutes
2023-01-07 14:58:50.448 - debug: mihome-vacuum.0 (1754) Message= {"id":20,"method":"get_clean_summary"}
2023-01-07 14:58:50.764 - debug: mihome-vacuum.0 (1754) Receive <<< Helo <<< 21310020000000001bc1b5b3000027ccffffffffffffffffffffffffffffffff
2023-01-07 14:58:50.765 - debug: mihome-vacuum.0 (1754) Time difference between Mihome Vacuum and ioBroker: -1673089742 sec
2023-01-07 14:58:52.451 - debug: mihome-vacuum.0 (1754) your device is connected, but didn't answer yet - sometime connection is broken and can take up to 10 Minutes
2023-01-07 14:58:52.453 - debug: mihome-vacuum.0 (1754) Startup: setGetCleanSummary Answer: false
2023-01-07 14:58:52.454 - debug: mihome-vacuum.0 (1754) Message= {"id":21,"method":"get_consumable"}
2023-01-07 14:58:54.457 - debug: mihome-vacuum.0 (1754) your device is connected, but didn't answer yet - sometime connection is broken and can take up to 10 Minutes
2023-01-07 14:58:54.458 - debug: mihome-vacuum.0 (1754) Startup: setGetConsumable Answer: false
2023-01-07 14:58:54.459 - debug: mihome-vacuum.0 (1754) Message= {"id":22,"method":"get_map_v1"}
2023-01-07 14:58:56.462 - debug: mihome-vacuum.0 (1754) your device is connected, but didn't answer yet - sometime connection is broken and can take up to 10 Minutes
2023-01-07 14:58:56.764 - debug: mihome-vacuum.0 (1754) Message= {"id":23,"method":"get_map_v1"}
2023-01-07 14:58:58.768 - debug: mihome-vacuum.0 (1754) your device is connected, but didn't answer yet - sometime connection is broken and can take up to 10 Minutes
2023-01-07 14:58:59.070 - debug: mihome-vacuum.0 (1754) Message= {"id":24,"method":"get_map_v1"}

Answer 17 · 2023-01-07T14:01:36.000Z

Ok, jetzt starte den Adapter bitte nochmal neu und zeige mir den Anfang.

Answer 18 · 2023-01-07T14:04:19.000Z

Ganz unten ist der Anfang wo ich den neugestartet hab. Ab da hab ich dir den Log angehangen:

2023-01-07 15:03:06.015 - debug: mihome-vacuum.0 (1754) Message= {"id":83,"method":"get_map_v1"}

2023-01-07 15:03:08.017 - debug: mihome-vacuum.0 (1754) your device is connected, but didn't answer yet - sometime connection is broken and can take up to 10 Minutes
2023-01-07 15:03:08.319 - debug: mihome-vacuum.0 (1754) Message= {"id":84,"method":"get_map_v1"}
2023-01-07 15:03:09.959 - info: host.iobroker-pi stopInstance system.adapter.mihome-vacuum.0 (force=false, process=true)
2023-01-07 15:03:10.227 - info: mihome-vacuum.0 (1754) Got terminate signal TERMINATE_YOURSELF
2023-01-07 15:03:10.230 - error: mihome-vacuum.0 (1754) Socket Close
2023-01-07 15:03:10.231 - info: mihome-vacuum.0 (1754) terminating
2023-01-07 15:03:10.232 - debug: mihome-vacuum.0 (1754) Plugin sentry destroyed
2023-01-07 15:03:10.233 - info: mihome-vacuum.0 (1754) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
2023-01-07 15:03:10.228 - info: host.iobroker-pi stopInstance system.adapter.mihome-vacuum.0 send kill signal
2023-01-07 15:03:10.883 - info: host.iobroker-pi instance system.adapter.mihome-vacuum.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
2023-01-07 15:03:13.397 - info: host.iobroker-pi instance system.adapter.mihome-vacuum.0 started with pid 1808
2023-01-07 15:03:15.286 - debug: mihome-vacuum.0 (1808) Redis Objects: Use Redis connection: 127.0.0.1:9001
2023-01-07 15:03:15.385 - debug: mihome-vacuum.0 (1808) Objects client ready ... initialize now
2023-01-07 15:03:15.388 - debug: mihome-vacuum.0 (1808) Objects create System PubSub Client
2023-01-07 15:03:15.389 - debug: mihome-vacuum.0 (1808) Objects create User PubSub Client
2023-01-07 15:03:15.586 - debug: mihome-vacuum.0 (1808) Objects client initialize lua scripts
2023-01-07 15:03:15.595 - debug: mihome-vacuum.0 (1808) Objects connected to redis: 127.0.0.1:9001
2023-01-07 15:03:15.674 - debug: mihome-vacuum.0 (1808) Redis States: Use Redis connection: 127.0.0.1:9000
2023-01-07 15:03:15.732 - debug: mihome-vacuum.0 (1808) States create System PubSub Client
2023-01-07 15:03:15.735 - debug: mihome-vacuum.0 (1808) States create User PubSub Client
2023-01-07 15:03:15.821 - debug: mihome-vacuum.0 (1808) States connected to redis: 127.0.0.1:9000
2023-01-07 15:03:16.207 - debug: mihome-vacuum.0 (1808) Plugin sentry Initialize Plugin (enabled=true)
2023-01-07 15:03:16.613 - info: mihome-vacuum.0 (1808) starting. Version 3.8.6 in /opt/iobroker/node_modules/iobroker.mihome-vacuum, node: v18.12.1, js-controller: 4.0.24
2023-01-07 15:03:16.688 - debug: mihome-vacuum.0 (1808) Create State for deviceInfo
2023-01-07 15:03:16.689 - debug: mihome-vacuum.0 (1808) Create State for deviceInfomac
2023-01-07 15:03:16.690 - debug: mihome-vacuum.0 (1808) Create State for deviceInfomodel
2023-01-07 15:03:16.691 - debug: mihome-vacuum.0 (1808) Create State for deviceInfofw_ver
2023-01-07 15:03:16.691 - debug: mihome-vacuum.0 (1808) Create State for deviceInfowifi_signal
2023-01-07 15:03:16.692 - debug: mihome-vacuum.0 (1808) MIIO: Config: ip:192.168.178.97 token: 35697a314bXXXXXXXXX
2023-01-07 15:03:16.697 - info: mihome-vacuum.0 (1808) IOT enabled, create state
2023-01-07 15:03:16.702 - debug: mihome-vacuum.0 (1808) server started on 0.0.0.0:53421
2023-01-07 15:03:16.732 - debug: mihome-vacuum.0 (1808) Receive <<< Helo <<< 21310020000000001bc1b5b3000028d6ffffffffffffffffffffffffffffffff
2023-01-07 15:03:16.733 - debug: mihome-vacuum.0 (1808) MAIN: Connected to device, try to get model..
2023-01-07 15:03:16.736 - debug: mihome-vacuum.0 (1808) Time difference between Mihome Vacuum and ioBroker: -1673089742 sec
2023-01-07 15:03:16.740 - debug: mihome-vacuum.0 (1808) GETMODELFROMAPI: objModel: {"val":"roborock.vacuum.a15","ack":true,"ts":1673099880641,"q":0,"from":"system.adapter.mihome-vacuum.0","user":"system.user.admin","lc":1673093247216}
2023-01-07 15:03:16.742 - debug: mihome-vacuum.0 (1808) Message= {"id":1,"method":"miIO.info"}
2023-01-07 15:03:18.746 - debug: mihome-vacuum.0 (1808) your device is connected, but didn't answer yet - sometime connection is broken and can take up to 10 Minutes
2023-01-07 15:03:18.748 - debug: mihome-vacuum.0 (1808) GETMODELFROMAPI:Data: {}
2023-01-07 15:03:18.749 - debug: mihome-vacuum.0 (1808) Get Device data..0
2023-01-07 15:03:18.750 - debug: mihome-vacuum.0 (1808) Message= {"id":2,"method":"miIO.info"}
2023-01-07 15:03:20.753 - debug: mihome-vacuum.0 (1808) your device is connected, but didn't answer yet - sometime connection is broken and can take up to 10 Minutes
2023-01-07 15:03:20.755 - debug: mihome-vacuum.0 (1808) GETMODELFROMAPI:Data: {}
2023-01-07 15:03:20.756 - debug: mihome-vacuum.0 (1808) Get Device data..1
2023-01-07 15:03:20.756 - debug: mihome-vacuum.0 (1808) Message= {"id":3,"method":"miIO.info"}
2023-01-07 15:03:22.759 - debug: mihome-vacuum.0 (1808) your device is connected, but didn't answer yet - sometime connection is broken and can take up to 10 Minutes
2023-01-07 15:03:22.760 - debug: mihome-vacuum.0 (1808) GETMODELFROMAPI:Data: {}
2023-01-07 15:03:22.761 - debug: mihome-vacuum.0 (1808) Get Device data..2
2023-01-07 15:03:22.762 - debug: mihome-vacuum.0 (1808) Message= {"id":4,"method":"miIO.info"}
2023-01-07 15:03:24.765 - debug: mihome-vacuum.0 (1808) your device is connected, but didn't answer yet - sometime connection is broken and can take up to 10 Minutes
2023-01-07 15:03:24.767 - debug: mihome-vacuum.0 (1808) GETMODELFROMAPI:Data: {}
2023-01-07 15:03:24.768 - debug: mihome-vacuum.0 (1808) Get Device data..3
2023-01-07 15:03:24.768 - debug: mihome-vacuum.0 (1808) Message= {"id":5,"method":"miIO.info"}
2023-01-07 15:03:26.761 - debug: mihome-vacuum.0 (1808) Receive <<< Helo <<< 21310020000000001bc1b5b3000028e0ffffffffffffffffffffffffffffffff
2023-01-07 15:03:26.762 - debug: mihome-vacuum.0 (1808) Time difference between Mihome Vacuum and ioBroker: -1673089742 sec
2023-01-07 15:03:26.770 - debug: mihome-vacuum.0 (1808) your device is connected, but didn't answer yet - sometime connection is broken and can take up to 10 Minutes
2023-01-07 15:03:26.771 - debug: mihome-vacuum.0 (1808) GETMODELFROMAPI:Data: {}
2023-01-07 15:03:26.771 - debug: mihome-vacuum.0 (1808) Get Device data..4
2023-01-07 15:03:26.772 - error: mihome-vacuum.0 (1808) YOUR DEVICE IS CONNECTED BUT DID NOT ANSWER YET - CONNECTION CAN TAKE UP TO 10 MINUTES - PLEASE BE PATIENT AND DO NOT TURN THE ADAPTER OFF
2023-01-07 15:03:26.772 - warn: mihome-vacuum.0 (1808) No Answer for DeviceModel use old one
2023-01-07 15:03:26.773 - warn: mihome-vacuum.0 (1808) No Answer for DeviceModel use model from Config
2023-01-07 15:03:26.790 - debug: mihome-vacuum.0 (1808) DeviceModel selected to: roborock.vacuum.a15
2023-01-07 15:03:26.791 - info: mihome-vacuum.0 (1808) select standard vacuum protocol....
2023-01-07 15:03:26.808 - debug: mihome-vacuum.0 (1808) Search can't be optimized because wildcard not at the end, fallback to keys!: function(doc) { if (doc.type === 'state') emit(doc._id, doc) }
2023-01-07 15:03:26.934 - debug: mihome-vacuum.0 (1808) Create State for control: {"id":"mihome-vacuum.0.control"}
2023-01-07 15:03:26.945 - debug: mihome-vacuum.0 (1808) Create State for Queue: queue
2023-01-07 15:03:26.946 - debug: mihome-vacuum.0 (1808) Create State for Queue: clearQueue
2023-01-07 15:03:26.952 - debug: mihome-vacuum.0 (1808) Create State for map:
2023-01-07 15:03:26.952 - debug: mihome-vacuum.0 (1808) Create State for map: map64
2023-01-07 15:03:26.953 - debug: mihome-vacuum.0 (1808) Create State for map: actualMap
2023-01-07 15:03:26.954 - debug: mihome-vacuum.0 (1808) Create State for map: mapStatus
2023-01-07 15:03:26.956 - debug: mihome-vacuum.0 (1808) Create State for map: mapURL
2023-01-07 15:03:26.957 - debug: mihome-vacuum.0 (1808) Create State for map: loadMap
2023-01-07 15:03:26.958 - debug: mihome-vacuum.0 (1808) Create State done!
2023-01-07 15:03:26.959 - debug: mihome-vacuum.0 (1808) get params for stock Vacuum

Answer 19 · 2023-01-07T14:17:03.000Z

Ok, das sieht jetzt erstmal alles normal aus, Das einzige was wirklich hoch ist, ist dir Timedifference. Bekommen der raspi und der robbi die Zeiten nicht vom selben Zeitserver? Hast du den Raspi vlt auf manuell Zeit gestellt?
Sonst habe ich auch keine Idee mehr :(

Answer 20 · 2023-01-07T14:21:14.000Z

Uffff.. das nun eine berichtige Frage auf was der PI steht. Ich schau da gleich mal fix rein. Aber normal steht der auf Auto Zeit und beides Europa/Berlin.
Vielleicht such ich mir gleich mal eine ältere Adapter Version und probiere es damit mal

Answer 21 · 2023-01-07T14:51:04.000Z

So...

Hab nun V3.9.2 von GitHub direkt installiert und es hat beim ersten Mal funktioniert. Die Instanz ist grün und verbunden mit dem Gerät.
Also scheint es was mit der Version die in ioBroker Adapter Store ist irgendwas zu sein.

Danke dir für deine Hilfe und die Zeit die du investiert hast 🙏🏻

Answer 22 · 2023-01-07T14:53:28.000Z

Das ist komisch, weil mit dem ganzen handling hat sich da nicht verändert. Ich vermute mal eher, dass der Robbi jetzt mit dir sprechen wollte... Diese 10 Minutenwarnung kommt nicht umsonst, die habe ich beim Entwickeln ständig...
Aber hauptsache er läuft ....