Test Adapter mihome-vacuum v2.0.x

Diginix

@Henny112 K.a. mein 1S läuft mit Port 54321 am Gerät. Was du als eigenen Port nutzt um keine Konflikte zu haben, ist dir überlassen, solange er frei ist. Am Ende laufen die einige Xiaomi wifi Geräte mit Port 54321. Yeelight, MiHome Plug.
Da muss man eben variieren.

Spampunk

Ich komme leider noch nicht weiter. Wenn ich den Adapter richtig verstehe, dann braucht es den Token, um direkt auf den Sauger zuzugreifen. Damit werden die Stati/Statusse/Staten abgerufen und die Datenpunkte befüllt. Auch lassen sich damit alle Aktionen ausführen. Wenn ich aber auch Zugriff zur Karte haben möchte, brauche ich den Xiaomi Cloud Zugriff. Ist das so richtig?

Wenn dem so ist, dann glaube ich, dass die Anmeldung auf den Cloud Server nicht funktioniert und den rotierenden Wartekreis im Adapter erklärt.

Kann das ein Entwickler, z.B. @Meistertr oder auch @dirkhe bestätigen?

Vielen Dank,
Timo

OT: Der Plural von Status ist übrigens auch Status, nur mit langgezogenem "u", gesprochen also Statuus. Aber das nur am Rande...

Thomas Braun

@Jaschkopf

server started on 0.0.0.0:53421

Ich denke bei zwei Geräten sollte da auch die jeweilige IP mit dabei stehen, wenn die Sauger schon den gleichen Port verwenden.

Spampunk

@Thomas-Braun
ich habe ja nur einen Sauger, der wird an einer statischen IP betrieben.

Du meinst bestimmt @Jaschkopf

Thomas Braun

@Spampunk
Oh, stimmt, meinte @Jaschkopf

Meistertr

@Spampunk was sagt denn der Debug log?

Spampunk

@Meistertr
Ich habe den Adapter einmal neu gestartet und dann auf den Button "get devices" geklickt.

mihome-vacuum.0	2020-12-07 17:06:35.902	debug	(2349) Xiaomi Cloud: Logging in
mihome-vacuum.0	2020-12-07 17:06:35.899	silly	(2349) States system redis pmessage io.messagebox.system.adapter.mihome-vacuum.0/io.messagebox.system.adapter.mihome-vacuum.0:{"command":"discovery","message":{"password":"SYDLbOfM9J","username":"spam
mihome-vacuum.0	2020-12-07 17:06:34.469	debug	(2349) get rooms from map pending...
mihome-vacuum.0	2020-12-07 17:06:34.468	debug	(2349) get rooms from map
mihome-vacuum.0	2020-12-07 17:06:34.467	debug	(2349) Empty array try to get from Map
mihome-vacuum.0	2020-12-07 17:06:34.466	debug	(2349) Receive <<< {"result":[],"id":18}
mihome-vacuum.0	2020-12-07 17:06:34.459	debug	(2349) sendMsg[1] >>> {"id":18,"method":"get_room_mapping"}
mihome-vacuum.0	2020-12-07 17:06:33.185	debug	(2349) Receive <<< {"result":[{"msg_ver":2,"msg_seq":2173,"state":8,"battery":100,"clean_time":4492,"clean_area":77260000,"error_code":0,"map_present":1,"in_cleaning":0,"in_returning":0,"in_fresh_stat
mihome-vacuum.0	2020-12-07 17:06:33.177	debug	(2349) sendMsg[1] >>> {"id":17,"method":"get_status"}
mihome-vacuum.0	2020-12-07 17:06:15.267	debug	(2349) Mappointer_updated
mihome-vacuum.0	2020-12-07 17:06:15.266	debug	(2349) Receive <<< {"result":["rubyslite%2F391549510%2F10"],"id":16}
mihome-vacuum.0	2020-12-07 17:06:15.198	debug	(2349) sendMsg[1] >>> {"id":16,"method":"get_map_v1"}
mihome-vacuum.0	2020-12-07 17:06:14.458	debug	(2349) get rooms from map pending...
mihome-vacuum.0	2020-12-07 17:06:14.457	debug	(2349) get rooms from map
mihome-vacuum.0	2020-12-07 17:06:14.456	debug	(2349) Empty array try to get from Map
mihome-vacuum.0	2020-12-07 17:06:14.455	debug	(2349) Receive <<< {"result":[],"id":15}
mihome-vacuum.0	2020-12-07 17:06:14.448	debug	(2349) sendMsg[1] >>> {"id":15,"method":"get_room_mapping"}
mihome-vacuum.0	2020-12-07 17:06:13.708	debug	(2349) Receive <<< {"result":[36429,601322500,25,[1607325777]],"id":14}
mihome-vacuum.0	2020-12-07 17:06:13.699	debug	(2349) sendMsg[1] >>> {"id":14,"method":"get_clean_summary"}
mihome-vacuum.0	2020-12-07 17:06:13.211	silly	(2349) States user redis pmessage mihome-vacuum.0.*/mihome-vacuum.0.control.clean_home:{"val":false,"ack":true,"ts":1607357173201,"q":0,"from":"system.adapter.mihome-vacuum.0","user":"system.user.admi
mihome-vacuum.0	2020-12-07 17:06:13.208	silly	(2349) States user redis pmessage mihome-vacuum.0.*/mihome-vacuum.0.info.state:{"val":8,"ack":true,"ts":1607357173200,"q":0,"from":"system.adapter.mihome-vacuum.0","user":"system.user.admin","lc":1607
mihome-vacuum.0	2020-12-07 17:06:13.203	debug	(2349) Receive <<< {"result":[{"main_brush_work_time":36776,"side_brush_work_time":36776,"filter_work_time":36776,"filter_element_work_time":8971,"sensor_dirty_time":4804}],"id":13}
mihome-vacuum.0	2020-12-07 17:06:13.195	debug	(2349) sendMsg[1] >>> {"id":13,"method":"get_consumable"}
mihome-vacuum.0	2020-12-07 17:06:13.192	info	(2349) create states for water box filter
mihome-vacuum.0	2020-12-07 17:06:13.190	info	(2349) create states for water box
mihome-vacuum.0	2020-12-07 17:06:13.187	debug	(2349) Receive <<< {"result":[{"msg_ver":2,"msg_seq":2172,"state":8,"battery":100,"clean_time":4492,"clean_area":77260000,"error_code":0,"map_present":1,"in_cleaning":0,"in_returning":0,"in_fresh_stat
mihome-vacuum.0	2020-12-07 17:06:13.173	debug	(2349) sendMsg[1] >>> {"id":12,"method":"get_status"}
mihome-vacuum.0	2020-12-07 17:05:55.667	debug	(2349) Mappointer_updated
mihome-vacuum.0	2020-12-07 17:05:55.666	debug	(2349) Receive <<< {"result":["rubyslite%2F391549510%2F9"],"id":11}
mihome-vacuum.0	2020-12-07 17:05:55.659	debug	(2349) 1. Mappointer_nomap___retry
mihome-vacuum.0	2020-12-07 17:05:55.657	debug	(2349) sendMsg[1] >>> {"id":11,"method":"get_map_v1"}
mihome-vacuum.0	2020-12-07 17:05:55.153	debug	(2349) Receive <<< {"result":["retry"],"id":10}
mihome-vacuum.0	2020-12-07 17:05:55.135	debug	(2349) 0. Mappointer_nomap___retry
mihome-vacuum.0	2020-12-07 17:05:55.134	debug	(2349) sendMsg[1] >>> {"id":10,"method":"get_map_v1"}
mihome-vacuum.0	2020-12-07 17:05:54.630	debug	(2349) Receive <<< {"result":["retry"],"id":9}
mihome-vacuum.0	2020-12-07 17:05:54.621	debug	(2349) sendMsg[1] >>> {"id":9,"method":"get_map_v1"}
mihome-vacuum.0	2020-12-07 17:05:54.524	silly	(2349) States user redis pmessage mihome-vacuum.0.*/mihome-vacuum.0.history.allTableHTML:{"val":"<table><colgroup> <col width=\"50\"> <col width=\"50\"> <col width=\"80\"> <col width=\"100\"> <col wid
mihome-vacuum.0	2020-12-07 17:05:54.519	silly	(2349) States user redis pmessage mihome-vacuum.0.*/mihome-vacuum.0.history.allTableJSON:{"val":"[{\"Datum\":\"7.12\",\"Start\":\"08:22\",\"Saugzeit\":\"75 min\",\"Fläche\":\"77.26 m²\",\"Error\":0,\"
mihome-vacuum.0	2020-12-07 17:05:54.448	debug	(2349) CLEAN_LOGGING[{"Datum":"7.12","Start":"08:22","Saugzeit":"75 min","Fläche":"77.26 m²","Error":0,"Ende":true}]
mihome-vacuum.0	2020-12-07 17:05:54.443	debug	(2349) get rooms from map pending...
mihome-vacuum.0	2020-12-07 17:05:54.442	debug	(2349) get rooms from map
mihome-vacuum.0	2020-12-07 17:05:54.440	debug	(2349) Empty array try to get from Map
mihome-vacuum.0	2020-12-07 17:05:54.439	debug	(2349) Receive <<< {"result":[],"id":8}
mihome-vacuum.0	2020-12-07 17:05:54.436	info	(2349) create state for carpet_mode
mihome-vacuum.0	2020-12-07 17:05:54.434	debug	(2349) Receive <<< {"result":[{"enable":1,"current_integral":450,"current_high":500,"current_low":400,"stall_time":10}],"id":7}
mihome-vacuum.0	2020-12-07 17:05:54.426	debug	(2349) sendMsg[1] >>> {"id":8,"method":"get_room_mapping"}
mihome-vacuum.0	2020-12-07 17:05:54.422	debug	(2349) sendMsg[1] >>> {"id":7,"method":"get_carpet_mode"}
mihome-vacuum.0	2020-12-07 17:05:54.242	debug	(2349) Receive <<< {"result":[[1607325777,1607330766,4492,77260000,0,1,2,1,52]],"id":6}
mihome-vacuum.0	2020-12-07 17:05:54.236	debug	(2349) sendMsg[1] >>> {"id":6,"method":"get_clean_record","params":[1607325777]}
mihome-vacuum.0	2020-12-07 17:05:54.232	debug	(2349) Receive <<< {"result":[36429,601322500,25,[1607325777]],"id":5}
mihome-vacuum.0	2020-12-07 17:05:54.222	debug	(2349) sendMsg[1] >>> {"id":5,"method":"get_clean_summary"}
mihome-vacuum.0	2020-12-07 17:05:54.030	debug	(2349) Receive <<< {"result":[{"main_brush_work_time":36776,"side_brush_work_time":36776,"filter_work_time":36776,"filter_element_work_time":8971,"sensor_dirty_time":4804}],"id":4}
mihome-vacuum.0	2020-12-07 17:05:54.021	debug	(2349) sendMsg[1] >>> {"id":4,"method":"get_consumable"}
mihome-vacuum.0	2020-12-07 17:05:53.838	debug	(2349) Receive <<< {"result":[90],"id":3}
mihome-vacuum.0	2020-12-07 17:05:53.820	debug	(2349) sendMsg[1] >>> {"id":3,"method":"get_sound_volume"}
mihome-vacuum.0	2020-12-07 17:05:53.742	silly	(2349) States user redis pmessage mihome-vacuum.0.*/mihome-vacuum.0.info.nextTimer:{"val":"Nicht verfügbar","ack":true,"ts":1607357153732,"q":0,"from":"system.adapter.mihome-vacuum.0","user":"system.u
mihome-vacuum.0	2020-12-07 17:05:53.726	info	(2349) set nächster Timer: Nicht verfügbar
mihome-vacuum.0	2020-12-07 17:05:53.701	silly	(2349) States user redis pmessage mihome-vacuum.0.*/mihome-vacuum.0.info.wifi_signal:{"val":-68,"ack":true,"ts":1607357153681,"q":0,"from":"system.adapter.mihome-vacuum.0","lc":1607357153681}
mihome-vacuum.0	2020-12-07 17:05:53.635	debug	(2349) Receive <<< {"partner_id":"","id":2,"code":0,"message":"ok","result":{"hw_ver":"Linux","fw_ver":"3.5.8_1026","ap":{"ssid":"BoxiNet","bssid":"2c:91:ab:86:51:a4","rssi":-68},"netif":{"localIp":"1
mihome-vacuum.0	2020-12-07 17:05:53.633	debug	(2349) Next WiFi check: 07.12 17:06
mihome-vacuum.0	2020-12-07 17:05:53.629	debug	(2349) sendMsg[1] >>> {"id":2,"method":"miIO.info"}
mihome-vacuum.0	2020-12-07 17:05:53.434	silly	(2349) States user redis pmessage mihome-vacuum.0.*/mihome-vacuum.0.info.connection:{"val":true,"ack":true,"ts":1607357153423,"q":0,"from":"system.adapter.mihome-vacuum.0","user":"system.user.admin","
mihome-vacuum.0	2020-12-07 17:05:53.421	silly	(2349) States user redis pmessage mihome-vacuum.0.*/mihome-vacuum.0.rooms.addRoom:{"val":"Kartenindex oder Zonenkoordinaten einfügen","ack":true,"ts":1607357153383,"q":0,"from":"system.adapter.mihome-
mihome-vacuum.0	2020-12-07 17:05:53.417	info	(2349) Connected
mihome-vacuum.0	2020-12-07 17:05:53.415	silly	(2349) States system redis pmessage io.messagebox.system.adapter.mihome-vacuum.0/io.messagebox.system.adapter.mihome-vacuum.0:{"command":"getStatus","message":{"error":null,"result":{"msg_ver":2,"msg_
mihome-vacuum.0	2020-12-07 17:05:53.394	silly	(2349) States user redis pmessage mihome-vacuum.0.*/mihome-vacuum.0.info.queue:{"val":"","ack":true,"ts":1607357153378,"q":0,"from":"system.adapter.mihome-vacuum.0","user":"system.user.admin","lc":160
mihome-vacuum.0	2020-12-07 17:05:53.393	silly	(2349) States user redis pmessage mihome-vacuum.0.*/mihome-vacuum.0.info.queue:{"val":"[]","ack":true,"ts":1607357153373,"q":0,"from":"system.adapter.mihome-vacuum.0","lc":1607357153373}
mihome-vacuum.0	2020-12-07 17:05:53.391	debug	(2349) sendTo "getStatus" to system.adapter.mihome-vacuum.0 from system.adapter.mihome-vacuum.0
mihome-vacuum.0	2020-12-07 17:05:53.387	debug	(2349) Receive <<< {"result":[{"msg_ver":2,"msg_seq":2171,"state":8,"battery":100,"clean_time":4492,"clean_area":77260000,"error_code":0,"map_present":1,"in_cleaning":0,"in_returning":0,"in_fresh_stat
mihome-vacuum.0	2020-12-07 17:05:53.361	debug	(2349) sendMsg[1] >>> {"id":1,"method":"get_status"}
mihome-vacuum.0	2020-12-07 17:05:53.352	silly	(2349) States system redis pmessage io.messagebox.system.adapter.mihome-vacuum.0/io.messagebox.system.adapter.mihome-vacuum.0:{"command":"getStatus","message":null,"from":"system.adapter.mihome-vacuum
mihome-vacuum.0	2020-12-07 17:05:53.351	silly	(2349) States user redis pmessage mihome-vacuum.0.*/mihome-vacuum.0.info.connection:{"val":false,"ack":true,"ts":1607357153253,"q":0,"from":"system.adapter.mihome-vacuum.0","user":"system.user.admin",
mihome-vacuum.0	2020-12-07 17:05:53.339	silly	(2349) States user redis pmessage mihome-vacuum.0.*/mihome-vacuum.0.info.wifi_signal:{"val":"unavailable","ack":true,"ts":1607357153252,"q":0,"from":"system.adapter.mihome-vacuum.0","user":"system.use
mihome-vacuum.0	2020-12-07 17:05:53.332	silly	(2349) States user redis pmessage mihome-vacuum.0.*/mihome-vacuum.0.info.connection:{"val":false,"ack":true,"ts":1607357153248,"q":0,"from":"system.adapter.mihome-vacuum.0","user":"system.user.admin",
mihome-vacuum.0	2020-12-07 17:05:53.306	silly	(2349) States system redis pmessage system.adapter.mihome-vacuum.0.logLevel/system.adapter.mihome-vacuum.0.logLevel:{"val":"silly","ack":true,"ts":1607357153243,"q":0,"from":"system.adapter.mihome-vac
mihome-vacuum.0	2020-12-07 17:05:53.267	debug	(2349) sendTo "getStatus" to system.adapter.mihome-vacuum.0 from system.adapter.mihome-vacuum.0
mihome-vacuum.0	2020-12-07 17:05:53.265	info	(2349) connecting, this can take up to 10 minutes ...
mihome-vacuum.0	2020-12-07 17:05:53.263	debug	(2349) Receive <<< Helo <<< 2131002000000000175692465fce52e0ffffffffffffffffffffffffffffffff
mihome-vacuum.0	2020-12-07 17:05:53.250	info	(2349) New generation or new fw(3.5.8,1026) detected, create new states goto and zoneclean
mihome-vacuum.0	2020-12-07 17:05:53.239	debug	(2349) No suitable Lua script, fallback to keys!: function(doc) { if (doc.type === 'state') emit(doc._id, doc) }
mihome-vacuum.0	2020-12-07 17:05:53.177	debug	(2349) server started on 0.0.0.0:53421
mihome-vacuum.0	2020-12-07 17:05:53.158	info	(2349) Cloud control disabled
mihome-vacuum.0	2020-12-07 17:05:53.156	info	(2349) Expert mode enabled, states created
mihome-vacuum.0	2020-12-07 17:05:53.144	debug	(2349) Xiaomi Cloud: Logging in
mihome-vacuum.0	2020-12-07 17:05:53.141	debug	(2349) load Map creator... true
mihome-vacuum.0	2020-12-07 17:05:53.027	info	(2349) 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	2020-12-07 17:05:45.988	silly	(30485) States user redis pmessage mihome-vacuum.0.*/mihome-vacuum.0.info.connection:{"val":false,"ack":true,"ts":1607357145981,"q":0,"from":"system.adapter.mihome-vacuum.0","user":"system.user.admin"
mihome-vacuum.0	2020-12-07 17:05:45.980	info	(30485) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason

Jaschkopf

@Thomas-Braun Also meine Roboter haben beide ne feste IP und in den jeweiligen Instanzen sind verschiedene Ports bei "Eigener-Port" eingestellt. So wie es auf Github beschrieben ist. Der Roboter-Port ist in beiden Instanzen auf 54321 gestellt.

Habe jetzt mal beide Instanzen auf Debug Level neu gestartet und die fehlerhafte Instanz bringt diese Meldung:

mihome-vacuum.0	2020-12-10 17:23:28.184	debug	(13642) No suitable Lua script, fallback to keys!: function(doc) { if (doc.type === 'state') emit(doc._id, doc) }

Während die funktionierende Instanz an der Stelle erfolgreich Daten empfängt:

mihome-vacuum.1	2020-12-10 17:24:29.357	debug	(13659) Receive <<< Helo <<< 213100200000000005bf16cb5fd24bbdffffffffffffffffffffffffffffffff

Woran kann das liegen? Hat der Roboter vielleicht ne Macke?

Gruß Jaschkopf

Meistertr

@Jaschkopf die Meldung kommt nicht von dem adapter sondern vom js-controller. Schau mal hier:
https://github.com/ioBroker/ioBroker.example/issues/71

Jaschkopf

@Meistertr ok danke. Hab den issue mal überflogen aber konnte keine Parallelen finden.

Ich hab dem problematischen Roboter jetzt mal eine andere IP zugewiesen und neugestartet. Momentan ist er grün, mal schauen ob der Fehler nochmal auftritt.

Gruß Jaschkopf

Spampunk

@Meistertr
hattest Du denn Gelegenheit, mein Log anzuschauen? Bzw. kannst Du daraus erkennen, woran es liegen kann, dass ich mich nicht mit der Xiaomi Cloud verbinden kann?

Oder gibt es andere Gründe, warum ich keine Karte angezeigt bekomme?

Vielen Dank,
Timo

NiWark

@Spampunk said in Test Adapter mihome-vacuum v2.0.x:

@Meistertr
hattest Du denn Gelegenheit, mein Log anzuschauen? Bzw. kannst Du daraus erkennen, woran es liegen kann, dass ich mich nicht mit der Xiaomi Cloud verbinden kann?

Oder gibt es andere Gründe, warum ich keine Karte angezeigt bekomme?

Vielen Dank,
Timo

Habe das gleiche Problem wie du wenn ich das richtig verstanden habe. Ich bekomme keine Verbindung zur Instanz... Bzw. Ich bekomme überhaupt keine Werte in den Objekten angezeigt. Habe die IP auch mal Fix gesetzt leider ohne Erfolg. Weiß einfach nicht weiter. Vielleicht hat ja noch jemand eine Idee.

mihome-vacuum.0	2020-12-16 22:40:24.796	debug	(26067) Receive <<< Helo <<< 2131002000000000165e6d165fda7ec8ffffffffffffffffffffffffffffffff
mihome-vacuum.0	2020-12-16 22:40:19.760	debug	(26067) sendTo "getStatus" to system.adapter.mihome-vacuum.0 from system.adapter.mihome-vacuum.0
mihome-vacuum.0	2020-12-16 22:40:19.758	debug	(26067) no answer for id:2 received, giving up
mihome-vacuum.0	2020-12-16 22:40:14.756	debug	(26067) sendMsg[3] >>> {"id":2,"method":"get_status"}
mihome-vacuum.0	2020-12-16 22:40:09.753	debug	(26067) sendMsg[2] >>> {"id":2,"method":"get_status"}
mihome-vacuum.0	2020-12-16 22:40:04.750	debug	(26067) sendMsg[1] >>> {"id":2,"method":"get_status"}
mihome-vacuum.0	2020-12-16 22:40:04.742	debug	(26067) sendTo "getStatus" to system.adapter.mihome-vacuum.0 from system.adapter.mihome-vacuum.0
mihome-vacuum.0	2020-12-16 22:40:04.740	info	(26067) connecting, this can take up to 10 minutes ...
mihome-vacuum.0	2020-12-16 22:40:04.738	debug	(26067) Receive <<< Helo <<< 2131002000000000165e6d165fda7eb4ffffffffffffffffffffffffffffffff
mihome-vacuum.0	2020-12-16 22:39:59.818	debug	(26067) sendTo "getStatus" to system.adapter.mihome-vacuum.0 from system.adapter.mihome-vacuum.0
mihome-vacuum.0	2020-12-16 22:39:59.815	debug	(26067) no answer for id:1 received, giving up
mihome-vacuum.0	2020-12-16 22:39:54.813	debug	(26067) sendMsg[3] >>> {"id":1,"method":"get_status"}
mihome-vacuum.0	2020-12-16 22:39:49.809	debug	(26067) sendMsg[2] >>> {"id":1,"method":"get_status"}
mihome-vacuum.0	2020-12-16 22:39:45.234	info	(26067) set nächster Timer: Nicht verfügbar
mihome-vacuum.0	2020-12-16 22:39:44.803	debug	(26067) sendMsg[1] >>> {"id":1,"method":"get_status"}
mihome-vacuum.0	2020-12-16 22:39:44.789	debug	(26067) sendTo "getStatus" to system.adapter.mihome-vacuum.0 from system.adapter.mihome-vacuum.0
mihome-vacuum.0	2020-12-16 22:39:44.787	info	(26067) connecting, this can take up to 10 minutes ...
mihome-vacuum.0	2020-12-16 22:39:44.785	debug	(26067) Receive <<< Helo <<< 2131002000000000165e6d165fda7ea0ffffffffffffffffffffffffffffffff
mihome-vacuum.0	2020-12-16 22:39:44.748	debug	(26067) No suitable Lua script, fallback to keys!: function(doc) { if (doc.type === 'state') emit(doc._id, doc) }
mihome-vacuum.0	2020-12-16 22:39:44.701	debug	(26067) server started on 0.0.0.0:53421
mihome-vacuum.0	2020-12-16 22:39:44.677	info	(26067) Cloud control disabled
mihome-vacuum.0	2020-12-16 22:39:44.674	info	(26067) Expert mode disabled, states deleted
mihome-vacuum.0	2020-12-16 22:39:44.605	info	(26067) starting. Version 2.1.1 in /opt/iobroker/node_modules/iobroker.mihome-vacuum, node: v10.23.0, js-controller: 3.1.6
mihome-vacuum.0	2020-12-16 22:39:38.049	info	(24969) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
mihome-vacuum.0	2020-12-16 22:39:38.047	info	(24969) terminating
mihome-vacuum.0	2020-12-16 22:39:38.043	info	(24969) Got terminate signal TERMINATE_YOURSELF
mihome-vacuum.0	2020-12-16 22:39:32.489	debug	(24969) sendTo "discovery" to system.adapter.admin.0 from system.adapter.mihome-vacuum.0
mihome-vacuum.0	2020-12-16 22:39:32.487	debug	(24969) discover__[{"did":"375xxxxx2","token":"4779436xxxxxxxxxxd5956646651596a","longitude":"0.00000000","latitude":"0.00000000","name":"Saugi","pid":"0","localip":"192.168.2.88","mac":"5C:6B:D7:08:4
mihome-vacuum.0	2020-12-16 22:39:32.483	debug	(24969) {"code":0,"message":"ok","result":{"list":[{"did":"375xxxxx2","token":"4779436xxxxxxxxxxd5956646651596a","longitude":"0.00000000","latitude":"0.00000000","name":"Saugi","pid":"0","localip":"19
mihome-vacuum.0	2020-12-16 22:39:32.333	debug	(24969) GET devices from:https://de.api.io.mi.com/app/home/device_list
mihome-vacuum.0	2020-12-16 22:39:32.327	debug	(24969) Xiaomi Cloud: Login successful
mihome-vacuum.0	2020-12-16 22:39:29.612	debug	(24969) Xiaomi Cloud: Logging in

Vielen dank im voraus schonmal.

Spampunk

@NiWark
Es wäre vielleicht ganz gut, wenn Du noch angibst, welches Modell Du hast.

@Meistertr
Ich habe mal gerade den Befehl "get_map" im DP "mihome-vacuum.0.control.X_send_command" abgesetzt und folgendes Log erhalten:

mihome-vacuum.0	2020-12-17 12:18:57.168	debug	(18233) Mappointer_updated
mihome-vacuum.0	2020-12-17 12:18:57.167	debug	(18233) Receive <<< {"result":["rubyslite%2F391549510%2F1"],"id":17}
mihome-vacuum.0	2020-12-17 12:18:57.160	debug	(18233) 1. Mappointer_nomap___retry
mihome-vacuum.0	2020-12-17 12:18:57.158	debug	(18233) sendMsg[1] >>> {"id":17,"method":"get_map_v1"}
mihome-vacuum.0	2020-12-17 12:18:56.987	debug	(18233) Receive <<< {"result":[[1607452925,1607453028,103,4085000,0,0,2,3,43]],"id":16}
mihome-vacuum.0	2020-12-17 12:18:56.978	debug	(18233) sendMsg[1] >>> {"id":16,"method":"get_clean_record","params":[1607452925]}
mihome-vacuum.0	2020-12-17 12:18:56.825	debug	(18233) system.adapter.admin.0: logging true

Kannst Du damit etwas anfangen? Wenn ich irgendwie dazu beitragen kann, das Projekt nach vorne zu bringen lass es mich gerne wissen.

Viele Grüße,
Timo

Meistertr

@Spampunk die lokale Verbindung des Roboters funktioniert einwandfrei. lediglich die cloud Anbindung nicht. Laut deinem log geht die Anfrage an den Server raus, aber es kommt keine Antwort, also gehe ich davon aus, dass die Anfragen durch irgendjemanden (Firewall oder Einstellungen des routers) blockiert werden

Meistertr

@NiWark bei dir ist die verbindung zur Cloud aufgenbaut. nur der Roboter antwortet local nicht. das ist zu beginn normal. Sollte es anhalten, einfach mal den Roboter neustarten, dann sollte es gehen

NiWark

@Spampunk
Oh Sorry. Ganz vergessen. Es handelt sich bei mir um den Xiaomi Mi Robot Vacuum Mop Pro.

@Meistertr
Leider nein. Habe es eben noch mal probiert. Roboter neu Gestartet, kurzen Moment gewartet. Adapter bleibt Gelb. Dann Adapter neu Gestartet, immer noch gelb.

Spampunk

@Meistertr
Welche Ports müssen denn dafür offen sein? Meine F/W hat nur die Standard-Einstellungen (Fritzbox), da ist nichts sonderlich geblockt oder so.

Wie lautet denn die Server-Adresse? Ich könnte ja mal einen Ping versuchen.

volx3eet

Hallo zusammen,
Ich habe eine Frage zur Zonenreinugung. Ich hab meine Map und kann jetzt via FloLeVac die Koords auslesen. Muss ich aktiv die Zonen in der App setzen, oder reicht es nur die Koordinaten auszulesen ohne die Zone zu bestätigen?

Mit den Koordinaten wird dann über VIS DER Robi gesteuert.

VG
Volx

Coffeelover

@volx3eet Hi. Du brauchst nur die Koordinaten. Mein Robbie ist schon so alt, der kann von sich aus garkeine Zonen. :)

Jaschkopf

Servus, ich schon wieder. Ich habe jetzt vor ein paar Tagen beide beiden Roborock S50 mal komplett platt gemacht und auf Werkseinstellung zurück gesetzt. Danach beide auf die neuste Firmware geupdatet (3.5.7_002008). Das Update musste ich allerdings über die FloleVac App machen, weil es mir von Xiaomi Home nicht angeboten wurde.

Trotzdem bricht immer noch die Verbindung zu meinem Erdgeschoss Roby ab. Ich habe die Verbindung mal per FLot aufgezeichnet und er trennt sich immer Nachts um 4Uhr. Im Log sieht man das einfach keine Daten mehr rein kommen.

[{"msg_ver":3,"msg_seq":4172,"state":8,"battery":100,"clean_time":12,"clean_area":0,"error_code":0,"map_present":1,"in_cleaning":0,"in_returning":0,"in_fresh_state":1,"lab_status":1,"water_box_status":0,"fan_power":102,"dnd_enabled":1,"map_status":3,"lock_status":0}],"id":2911}
2020-12-20 03:58:43.981  - [34mdebug[39m: mihome-vacuum.0 (1071) sendMsg[1] >>> {"id":2913,"method":"get_status"}
2020-12-20 03:58:44.004  - [34mdebug[39m: mihome-vacuum.0 (1071) Receive <<< {"result":[{"msg_ver":3,"msg_seq":4173,"state":8,"battery":100,"clean_time":12,"clean_area":0,"error_code":0,"map_present":1,"in_cleaning":0,"in_returning":0,"in_fresh_state":1,"lab_status":1,"water_box_status":0,"fan_power":102,"dnd_enabled":1,"map_status":3,"lock_status":0}],"id":2913}
2020-12-20 03:59:03.982  - [34mdebug[39m: mihome-vacuum.0 (1071) sendMsg[1] >>> {"id":2914,"method":"get_status"}
2020-12-20 03:59:03.997  - [34mdebug[39m: mihome-vacuum.0 (1071) Receive <<< {"result":[{"msg_ver":3,"msg_seq":4174,"state":8,"battery":100,"clean_time":12,"clean_area":0,"error_code":0,"map_present":1,"in_cleaning":0,"in_returning":0,"in_fresh_state":1,"lab_status":1,"water_box_status":0,"fan_power":102,"dnd_enabled":1,"map_status":3,"lock_status":0}],"id":2914}
2020-12-20 03:59:23.988  - [34mdebug[39m: mihome-vacuum.0 (1071) sendMsg[1] >>> {"id":2915,"method":"get_status"}
2020-12-20 03:59:23.989  - [34mdebug[39m: mihome-vacuum.0 (1071) sendMsg[1] >>> {"id":2916,"method":"miIO.info"}
2020-12-20 03:59:23.989  - [34mdebug[39m: mihome-vacuum.0 (1071) Next WiFi check: 20.12 04:00
2020-12-20 03:59:24.005  - [34mdebug[39m: mihome-vacuum.0 (1071) Receive <<< {"partner_id":"","id":2916,"code":0,"message":"ok","result":{"hw_ver":"Linux","fw_ver":"3.5.7_002008","ap":{"ssid":"Laterne","bssid":"E8:DF:70:9E:5E:3D","rssi":-51},"netif":{"localIp":"192.168.178.27","mask":"255.255.255.0","gw":"192.168.178.1"},"model":"roborock.vacuum.s5","mac":"40:31:3C:AD:47:63","token":"4d747171777057373650316871615437","life":86362}}
2020-12-20 03:59:24.006  - [34mdebug[39m: mihome-vacuum.0 (1071) Receive <<< {"result":[{"msg_ver":3,"msg_seq":4175,"state":8,"battery":100,"clean_time":12,"clean_area":0,"error_code":0,"map_present":1,"in_cleaning":0,"in_returning":0,"in_fresh_state":1,"lab_status":1,"water_box_status":0,"fan_power":102,"dnd_enabled":1,"map_status":3,"lock_status":0}],"id":2915}
2020-12-20 03:59:43.989  - [34mdebug[39m: mihome-vacuum.0 (1071) sendMsg[1] >>> {"id":2917,"method":"get_status"}
2020-12-20 03:59:44.008  - [34mdebug[39m: mihome-vacuum.0 (1071) Receive <<< {"result":[{"msg_ver":3,"msg_seq":4176,"state":8,"battery":100,"clean_time":12,"clean_area":0,"error_code":0,"map_present":1,"in_cleaning":0,"in_returning":0,"in_fresh_state":1,"lab_status":1,"water_box_status":0,"fan_power":102,"dnd_enabled":1,"map_status":3,"lock_status":0}],"id":2917}
2020-12-20 04:00:00.019  - [32minfo[39m: host.iobroker instance system.adapter.dwd.0 started with pid 3184
2020-12-20 04:00:03.990  - [34mdebug[39m: mihome-vacuum.0 (1071) sendMsg[1] >>> {"id":2918,"method":"get_status"}
2020-12-20 04:00:07.268  - [32minfo[39m: host.iobroker instance system.adapter.dwd.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
2020-12-20 04:00:08.991  - [34mdebug[39m: mihome-vacuum.0 (1071) sendMsg[2] >>> {"id":2918,"method":"get_status"}
2020-12-20 04:00:13.993  - [34mdebug[39m: mihome-vacuum.0 (1071) sendMsg[3] >>> {"id":2918,"method":"get_status"}
2020-12-20 04:00:18.994  - [34mdebug[39m: mihome-vacuum.0 (1071) no answer for get_status id:2918 received, giving up
2020-12-20 04:00:23.994  - [34mdebug[39m: mihome-vacuum.0 (1071) sendMsg[1] >>> {"id":2919,"method":"get_status"}
2020-12-20 04:00:23.997  - [34mdebug[39m: mihome-vacuum.0 (1071) sendMsg[1] >>> {"id":2920,"method":"miIO.info"}
2020-12-20 04:00:23.997  - [34mdebug[39m: mihome-vacuum.0 (1071) Next WiFi check: 20.12 04:01
2020-12-20 04:00:28.997  - [34mdebug[39m: mihome-vacuum.0 (1071) sendMsg[2] >>> {"id":2919,"method":"get_status"}
2020-12-20 04:00:28.998  - [34mdebug[39m: mihome-vacuum.0 (1071) sendMsg[2] >>> {"id":2920,"method":"miIO.info"}
2020-12-20 04:00:28.999  - [34mdebug[39m: mihome-vacuum.0 (1071) Next WiFi check: 20.12 04:01
2020-12-20 04:00:33.998  - [34mdebug[39m: mihome-vacuum.0 (1071) sendMsg[3] >>> {"id":2919,"method":"get_status"}
2020-12-20 04:00:33.999  - [34mdebug[39m: mihome-vacuum.0 (1071) sendMsg[3] >>> {"id":2920,"method":"miIO.info"}
2020-12-20 04:00:33.999  - [34mdebug[39m: mihome-vacuum.0 (1071) Next WiFi check: 20.12 04:01
2020-12-20 04:00:38.999  - [34mdebug[39m: mihome-vacuum.0 (1071) no answer for get_status id:2919 received, giving up
2020-12-20 04:00:38.999  - [34mdebug[39m: mihome-vacuum.0 (1071) no answer for miIO.info id:2920 received, giving up
2020-12-20 04:00:39.000  - [33mwarn[39m: mihome-vacuum.0 (1071) no answer received after 3 times -> pause miIO.info try again in one hour
2020-12-20 04:00:39.000  - [34mdebug[39m: mihome-vacuum.0 (1071) Next WiFi check: 20.12 05:00
2020-12-20 04:00:43.998  - [34mdebug[39m: mihome-vacuum.0 (1071) sendMsg[1] >>> {"id":2921,"method":"get_status"}
2020-12-20 04:00:48.999  - [34mdebug[39m: mihome-vacuum.0 (1071) sendMsg[2] >>> {"id":2921,"method":"get_status"}
2020-12-20 04:00:54.000  - [34mdebug[39m: mihome-vacuum.0 (1071) sendMsg[3] >>> {"id":2921,"method":"get_status"}
2020-12-20 04:00:59.001  - [34mdebug[39m: mihome-vacuum.0 (1071) no answer for get_status id:2921 received, giving up
2020-12-20 04:01:03.999  - [34mdebug[39m: mihome-vacuum.0 (1071) sendMsg[1] >>> {"id":2922,"method":"get_status"}
2020-12-20 04:01:09.000  - [34mdebug[39m: mihome-vacuum.0 (1071) sendMsg[2] >>> {"id":2922,"method":"get_status"}
2020-12-20 04:01:14.001  - [34mdebug[39m: mihome-vacuum.0 (1071) sendMsg[3] >>> {"id":2922,"method":"get_status"}
2020-12-20 04:01:19.002  - [34mdebug[39m: mihome-vacuum.0 (1071) no answer for get_status id:2922 received, giving up
2020-12-20 04:01:24.000  - [34mdebug[39m: mihome-vacuum.0 (1071) sendMsg[1] >>> {"id":2923,"method":"get_status"}
2020-12-20 04:01:29.001  - [34mdebug[39m: mihome-vacuum.0 (1071) sendMsg[2] >>> {"id":2923,"method":"get_status"}
2020-12-20 04:01:34.003  - [34mdebug[39m: mihome-vacuum.0 (1071) sendMsg[3] >>> {"id":2923,"method":"get_status"}
2020-12-20 04:01:39.003  - [34mdebug[39m: mihome-vacuum.0 (1071) no answer for get_status id:2923 received, giving up
2020-12-20 04:01:44.002  - [34mdebug[39m: mihome-vacuum.0 (1071) sendMsg[1] >>> {"id":2924,"method":"get_status"}
2020-12-20 04:01:49.004  - [34mdebug[39m: mihome-vacuum.0 (1071) sendMsg[2] >>> {"id":2924,"method":"get_status"}
2020-12-20 04:01:54.005  - [34mdebug[39m: mihome-vacuum.0 (1071) sendMsg[3] >>> {"id":2924,"method":"get_status"}
2020-12-20 04:01:59.006  - [34mdebug[39m: mihome-vacuum.0 (1071) no answer for get_status id:2924 received, giving up
2020-12-20 04:02:04.004  - [32minfo[39m: mihome-vacuum.0 (1071) Disconnected due last Restponse of 03:59:44.010

Alles andere läuft problemlos im Netzwerk. Der Roby bleibt dann genau 24h offline und dann wieder Nachts um 4Uhr kann er die Verbindung wiederherstellen.

Kann das am Germany Server liegen? Über welchen Server habt ihr eure Robys laufen?

Gruß Jaschkopf

Community Forum

NEWS

Test Adapter mihome-vacuum v2.0.x

Support us

753

32.5k

81.6k

1.3m