Weihnachtsangebot 2025! 🎄

[Krys]

mihome-vacuum.0
2022-01-30 15:14:36.959	info	create state for carpet_mode

mihome-vacuum.0
2022-01-30 15:14:35.976	info	create states for mop

mihome-vacuum.0
2022-01-30 15:14:35.969	info	create states for water box mode

mihome-vacuum.0
2022-01-30 15:14:35.961	info	create states for water box

mihome-vacuum.0
2022-01-30 15:14:35.932	info	change states from State control.fan_power

mihome-vacuum.0
2022-01-30 15:14:35.906	info	Map selected create states...

mihome-vacuum.0
2022-01-30 15:14:35.505	info	settest next timer: not available

mihome-vacuum.0
2022-01-30 15:14:34.878	info	select standard vacuum protocol....

mihome-vacuum.0
2022-01-30 15:14:34.768	info	IOT enabled, create state

mihome-vacuum.0
2022-01-30 15:14:34.627	info	starting. Version 3.3.4 in /opt/iobroker/node_modules/iobroker.mihome-vacuum, node: v14.18.3, js-controller: 3.3.22

mihome-vacuum.0
2022-01-30 14:27:50.738	info	create state for carpet_mode

mihome-vacuum.0
2022-01-30 14:27:49.837	info	create states for mop

mihome-vacuum.0
2022-01-30 14:27:49.834	info	create states for water box mode

mihome-vacuum.0
2022-01-30 14:27:49.831	info	create states for water box

mihome-vacuum.0
2022-01-30 14:27:49.816	info	change states from State control.fan_power

mihome-vacuum.0
2022-01-30 14:27:49.795	info	Map selected create states...

mihome-vacuum.0
2022-01-30 14:27:49.369	info	settest next timer: not available

mihome-vacuum.0
2022-01-30 14:27:48.759	info	select standard vacuum protocol....

mihome-vacuum.0
2022-01-30 14:27:48.630	info	IOT enabled, create state

mihome-vacuum.0
2022-01-30 14:27:48.490	info	starting. Version 3.3.4 in /opt/iobroker/node_modules/iobroker.mihome-vacuum, node: v14.18.3, js-controller: 3.3.22

mihome-vacuum.0
2022-01-30 14:27:14.283	info	create states for mop

mihome-vacuum.0
2022-01-30 14:27:14.279	info	create states for water box mode

mihome-vacuum.0
2022-01-30 14:27:14.274	info	create states for water box

mihome-vacuum.0
2022-01-30 14:27:14.258	info	change states from State control.fan_power

mihome-vacuum.0
2022-01-30 14:26:44.162	info	create state for carpet_mode

mihome-vacuum.0
2022-01-30 14:23:37.379	info	Map selected create states...

mihome-vacuum.0
2022-01-30 14:23:37.213	info	settest next timer: not available

mihome-vacuum.0
2022-01-30 14:23:36.640	info	select standard vacuum protocol....

mihome-vacuum.0
2022-01-30 14:23:36.614	warn	No Answer for DeviceModel use model from Config

mihome-vacuum.0
2022-01-30 14:23:36.613	warn	No Answer for DeviceModel use old one

mihome-vacuum.0
2022-01-30 14:23:36.613	warn	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

mihome-vacuum.0
2022-01-30 14:23:26.577	info	IOT enabled, create state

mihome-vacuum.0
2022-01-30 14:23:26.399	info	starting. Version 3.3.4 in /opt/iobroker/node_modules/iobroker.mihome-vacuum, node: v14.18.3, js-controller: 3.3.22

mihome-vacuum.0
2022-01-30 14:22:38.169	info	create state for carpet_mode

mihome-vacuum.0
2022-01-30 14:22:34.696	info	create states for mop

mihome-vacuum.0
2022-01-30 14:22:34.692	info	create states for water box mode

mihome-vacuum.0
2022-01-30 14:22:34.688	info	create states for water box

mihome-vacuum.0
2022-01-30 14:22:34.669	info	change states from State control.fan_power

mihome-vacuum.0
2022-01-30 14:22:34.650	info	Map selected create states...

mihome-vacuum.0
2022-01-30 14:22:34.503	info	settest next timer: not available

mihome-vacuum.0
2022-01-30 14:22:33.821	info	select standard vacuum protocol....

mihome-vacuum.0
2022-01-30 14:22:33.718	info	IOT enabled, create state

mihome-vacuum.0
2022-01-30 14:22:33.553	info	starting. Version 3.3.4 in /opt/iobroker/node_modules/iobroker.mihome-vacuum, node: v14.18.3, js-controller: 3.3.22

mihome-vacuum.0
2022-01-30 14:21:50.955	info	create states for mop

mihome-vacuum.0
2022-01-30 14:21:50.949	info	create states for water box mode

mihome-vacuum.0
2022-01-30 14:21:50.944	info	create states for water box

mihome-vacuum.0
2022-01-30 14:21:50.914	info	change states from State control.fan_power

mihome-vacuum.0
2022-01-30 14:21:20.795	info	create state for carpet_mode

mihome-vacuum.0
2022-01-30 14:16:49.335	info	Map selected create states...

mihome-vacuum.0
2022-01-30 14:16:49.212	info	settest next timer: not available

mihome-vacuum.0
2022-01-30 14:16:48.573	info	select standard vacuum protocol....

mihome-vacuum.0
2022-01-30 14:16:48.540	warn	No Answer for DeviceModel use model from Config

mihome-vacuum.0
2022-01-30 14:16:48.539	warn	No Answer for DeviceModel use old one

mihome-vacuum.0
2022-01-30 14:16:48.538	warn	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

mihome-vacuum.0
2022-01-30 14:16:38.493	info	IOT enabled, create state

mihome-vacuum.0
2022-01-30 14:16:38.348	info	starting. Version 3.3.4 in /opt/iobroker/node_modules/iobroker.mihome-vacuum, node: v14.18.3, js-controller: 3.3.22

mihome-vacuum.0
2022-01-30 14:16:02.648	info	create states for mop

mihome-vacuum.0
2022-01-30 14:16:02.635	info	create states for water box mode

mihome-vacuum.0
2022-01-30 14:16:02.621	info	create states for water box

mihome-vacuum.0
2022-01-30 14:16:02.574	info	change states from State control.fan_power

mihome-vacuum.0
2022-01-30 14:16:02.524	info	Map selected create states...

mihome-vacuum.0
2022-01-30 14:16:02.054	info	settest next timer: not available

mihome-vacuum.0
2022-01-30 14:16:01.312	info	select standard vacuum protocol....

mihome-vacuum.0
2022-01-30 14:16:01.148	info	IOT enabled, create state

mihome-vacuum.0
2022-01-30 14:16:00.898	info	starting. Version 3.3.4 in /opt/iobroker/node_modules/iobroker.mihome-vacuum, node: v14.18.3, js-controller: 3.3.22

mihome-vacuum.0
2022-01-30 14:15:21.567	info	create states for mop

mihome-vacuum.0
2022-01-30 14:15:21.561	info	create states for water box mode

mihome-vacuum.0
2022-01-30 14:15:21.557	info	create states for water box

mihome-vacuum.0
2022-01-30 14:15:21.544	info	change states from State control.fan_power

mihome-vacuum.0
2022-01-30 14:14:51.421	info	create state for carpet_mode

mihome-vacuum.0
2022-01-30 14:14:03.065	info	Map selected create states...

mihome-vacuum.0
2022-01-30 14:14:02.912	info	settest next timer: not available

mihome-vacuum.0
2022-01-30 14:14:02.223	info	select standard vacuum protocol....

mihome-vacuum.0
2022-01-30 14:14:02.189	warn	No Answer for DeviceModel use model from Config

mihome-vacuum.0
2022-01-30 14:14:02.188	warn	No Answer for DeviceModel use old one

mihome-vacuum.0
2022-01-30 14:14:02.187	warn	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

mihome-vacuum.0
2022-01-30 14:13:52.084	info	IOT enabled, create state

mihome-vacuum.0
2022-01-30 14:13:51.928	info	starting. Version 3.3.4 in /opt/iobroker/node_modules/iobroker.mihome-vacuum, node: v14.18.3, js-controller: 3.3.22

mihome-vacuum.0
2022-01-30 14:13:17.086	info	create states for mop

mihome-vacuum.0
2022-01-30 14:13:17.083	info	create states for water box mode

mihome-vacuum.0
2022-01-30 14:13:17.080	info	create states for water box

mihome-vacuum.0
2022-01-30 14:13:17.064	info	change states from State control.fan_power

mihome-vacuum.0
2022-01-30 14:13:17.038	info	Map selected create states...

mihome-vacuum.0
2022-01-30 14:13:16.897	info	settest next timer: not available

mihome-vacuum.0
2022-01-30 14:13:16.295	info	select standard vacuum protocol....

mihome-vacuum.0
2022-01-30 14:13:16.183	info	IOT enabled, create state

mihome-vacuum.0
2022-01-30 14:13:16.036	info	starting. Version 3.3.4 in /opt/iobroker/node_modules/iobroker.mihome-vacuum, node: v14.18.3, js-controller: 3.3.22

Hat noch jemand dasselbe Problem aktuell?

Node.js: v14.18.3
NPM: 6.14.16
Adapterversion: 3.3.4
RPI4 4GB

Roborock s5 Max, FW: 3.5.8_1566

Während der Sauger läuft, habe ich quasi einen "loop" an Neustart.
Ansonsten kann es mal sein, dass 4 Stunden nichts passiert und dann wieder 30 Neustarts in 10 Minuten.

[Krys]

mihome-vacuum.0
2022-02-02 08:52:11.236	info	Map selected create states...

mihome-vacuum.0
2022-02-02 08:52:10.817	info	settest next timer: not available

mihome-vacuum.0
2022-02-02 08:52:10.177	info	select standard vacuum protocol....

mihome-vacuum.0
2022-02-02 08:52:10.151	warn	No Answer for DeviceModel use model from Config

mihome-vacuum.0
2022-02-02 08:52:10.151	warn	No Answer for DeviceModel use old one

mihome-vacuum.0
2022-02-02 08:52:10.150	warn	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

mihome-vacuum.0
2022-02-02 08:52:00.060	info	IOT enabled, create state

mihome-vacuum.0
2022-02-02 08:51:59.904	info	starting. Version 3.3.4 in /opt/iobroker/node_modules/iobroker.mihome-vacuum, node: v14.19.0, js-controller: 3.3.22
host.raspberrypi
2022-02-02 08:51:56.841	info	instance system.adapter.mihome-vacuum.0 started with pid 21674
host.raspberrypi
2022-02-02 08:51:26.771	info	Restart adapter system.adapter.mihome-vacuum.0 because enabled
host.raspberrypi
2022-02-02 08:51:26.770	info	instance system.adapter.mihome-vacuum.0 terminated with code NaN ()
host.raspberrypi
2022-02-02 08:51:26.769	warn	instance system.adapter.mihome-vacuum.0 terminated due to SIGILL
host.raspberrypi
2022-02-02 08:51:26.768	error	Caught by controller[0]: #FailureMessage Object: 0xbe9c67e0
host.raspberrypi
2022-02-02 08:51:26.768	error	Caught by controller[0]: #
host.raspberrypi
2022-02-02 08:51:26.767	error	Caught by controller[0]: #
host.raspberrypi
2022-02-02 08:51:26.767	error	Caught by controller[0]: #
host.raspberrypi
2022-02-02 08:51:26.766	error	Caught by controller[0]: # Check failed: heap_->memory_allocator()->IsMemoryChunkExecutable(page).
host.raspberrypi
2022-02-02 08:51:26.766	error	Caught by controller[0]: # Fatal error in , line 0
host.raspberrypi
2022-02-02 08:51:26.759	error	Caught by controller[0]: #

mihome-vacuum.0
2022-02-02 08:50:12.336	info	create state for carpet_mode

mihome-vacuum.0
2022-02-02 08:50:09.525	warn	Object of state "mihome-vacuum.0.cleanmap.actualMap" is missing the required property "common.type"

mihome-vacuum.0
2022-02-02 08:50:09.464	info	create states for mop

mihome-vacuum.0
2022-02-02 08:50:09.460	info	create states for water box mode

mihome-vacuum.0
2022-02-02 08:50:09.455	info	create states for water box

mihome-vacuum.0
2022-02-02 08:50:09.430	info	change states from State control.fan_power

mihome-vacuum.0
2022-02-02 08:50:09.402	info	Map selected create states...

mihome-vacuum.0
2022-02-02 08:50:09.253	info	settest next timer: not available

mihome-vacuum.0
2022-02-02 08:50:08.619	info	select standard vacuum protocol....

mihome-vacuum.0
2022-02-02 08:50:08.500	info	IOT enabled, create state

mihome-vacuum.0
2022-02-02 08:50:08.321	info	starting. Version 3.3.4 in /opt/iobroker/node_modules/iobroker.mihome-vacuum, node: v14.19.0, js-controller: 3.3.22
host.raspberrypi
2022-02-02 08:50:05.065	info	instance system.adapter.mihome-vacuum.0 started with pid 20324
host.raspberrypi
2022-02-02 08:49:35.014	info	Restart adapter system.adapter.mihome-vacuum.0 because enabled
host.raspberrypi
2022-02-02 08:49:35.014	info	instance system.adapter.mihome-vacuum.0 terminated with code NaN ()
host.raspberrypi
2022-02-02 08:49:35.009	warn	instance system.adapter.mihome-vacuum.0 terminated due to SIGSEGV

Ich bekomme es anscheinend nicht hin.

nodejs
v14.19.0
node
v14.19.0
npm
6.14.16

pi@raspberrypi:/opt/iobroker $ npm list canvas
iobroker.inst@2.0.3 /opt/iobroker
├── canvas@2.9.0
├─┬ iobroker.iot@1.8.24
│ └── canvas@2.9.0  deduped
└─┬ iobroker.mihome-vacuum@3.3.4 (github:iobroker-community-adapters/ioBroker.mihome-vacuum#881c0892d76cf4087b5c6247f67b0ba2a7ee34fd)
 └── canvas@2.9.0  deduped

[D3ltoroxp]

Könnte mir noch mal jemand helfen mit der Karte für die VIS. Und zwar hätte ich da gern die Map64 drin. Nur weiß ich nicht welches Widget und welcher Code da rein muss ? Mit der normalen Map über image Widget klappt es schon mal. Die Map 64 hätte ich aber gern, da sie flotter beim aktualisieren ist.

So wie es bei mir früher ging klappt es nicht mehr..

Basicl HTML Widget.

Mit dem Link aus der Beschreibung klappt es leider auch nicht.

Wenn ich das so eingebe

<img src="https://www.iobroker.net/zh-cn/adapterref/iobroker.mihome-vacuum/mihome-vacuum.0.cleanmap.map64">

passiert nichts im Basic HTML Widget. Liegt das vllt an zh-cn ? Da ich dort DE Server drin hab ? Hab aber auch schon mit de-de oder de-ger versucht. Das kann ich auch nicht verwenden oder weiß nicht wie und wo ?

mihome-vacuum.0.cleanmap.map64

[bahnuhr]

@d3ltoroxp
https://forum.iobroker.net/topic/44077/test-adapter-mihome-vacuum-v3-1-6-next-generarition/681?page=35

Hast du denn den thread gelesen?
Fragst doch jetzt schon mehrmals, oder ?

[D3ltoroxp]

@bahnuhr Den hatte ich dann wohl leider übersehen. Ich wollte das jetzt noch mal angehen. Es funktioniert nun so auch wunderbar. Ausser in dem Editor, ich hatte das dann nie Live probiert, weil er im Editor immer das kaputte Image Zeichen angezeigt hat und beim anderen aber doch die Map.

Indem Fall sieht man das wohl im Editor nicht, aber in dem Browser mit der VIS sieht man es.

[gelberlemmy]

Guten morgen,

gibt es eigentlich in Workaround bezüglich des ständigen Absturzes des Adapters, wenn der Roborock S7 in Betrieb ist ? Konnte jetzt nicht wirklich etwas finden.

Gruß André

[bahnuhr]

@gelberlemmy sagte in Test Adapter Mihome-vacuum v3.1.6 Next Generarition:

Roborock S7 in Betrieb ist ? Konnte jetzt nicht wirklich etwas finden.

Ich weiß auch nicht ob du da etwas findest.

Habe auch einen S7. Bei mir stürzt der Adapter nicht ab.

[gelberlemmy]

@bahnuhr schau einmal hier. In Github ist dies bereits als Issue angelegt.

https://github.com/iobroker-community-adapters/ioBroker.mihome-vacuum/issues/487

So stellt sich mein Fehler da

[Krys]

@gelberlemmy bei mir dasselbe mit dem S5 Max. Logs hatte ich im Verlauf hier gepostet als auch auf git. Aber ansonsten habe ich mir auch mal die ganze Canvas/Node-Geschichte angeschaut und damit beschäftigt. Die Abstürze sind weniger geworden und tlw. "anders", daher vermute ich den Fehler auf meiner Seite.. Mal schauen.

[gelberlemmy]

Diesen folgen Log bekomme ich aktuell....

mihome-vacuum.0
2022-02-04 11:31:06.926	info	starting. Version 3.3.4 in /opt/iobroker/node_modules/iobroker.mihome-vacuum, node: v14.18.3, js-controller: 3.3.22
host.raspberrypi
2022-02-04 11:31:04.100	info	instance system.adapter.mihome-vacuum.0 started with pid 6734
host.raspberrypi
2022-02-04 11:30:34.045	info	Restart adapter system.adapter.mihome-vacuum.0 because enabled
host.raspberrypi
2022-02-04 11:30:34.045	info	instance system.adapter.mihome-vacuum.0 terminated with code NaN ()
host.raspberrypi
2022-02-04 11:30:34.045	warn	instance system.adapter.mihome-vacuum.0 terminated due to SIGABRT
host.raspberrypi
2022-02-04 11:30:34.044	error	Caught by controller[0]: corrupted double-linked list

[gelberlemmy]

@meistertr und manchmal kommt dann das vom Host:

host.raspberrypi
2022-02-04 12:11:18.873	warn	instance system.adapter.mihome-vacuum.0 terminated due to SIGILL
host.raspberrypi
2022-02-04 12:11:18.873	error	Caught by controller[0]: #FailureMessage Object: 0xbe86f368
host.raspberrypi
2022-02-04 12:11:18.873	error	Caught by controller[0]: #
host.raspberrypi
2022-02-04 12:11:18.873	error	Caught by controller[0]: #
host.raspberrypi
2022-02-04 12:11:18.872	error	Caught by controller[0]: #
host.raspberrypi
2022-02-04 12:11:18.872	error	Caught by controller[0]: # Check failed: !backing_store->is_wasm_memory().
host.raspberrypi
2022-02-04 12:11:18.872	error	Caught by controller[0]: # Fatal error in , line 0
host.raspberrypi
2022-02-04 12:11:18.871	error	Caught by controller[0]: #

[Krys]

host.raspberrypi
2022-02-04 12:49:41.136	info	Restart adapter system.adapter.mihome-vacuum.0 because enabled
host.raspberrypi
2022-02-04 12:49:41.135	info	instance system.adapter.mihome-vacuum.0 terminated with code NaN ()
host.raspberrypi
2022-02-04 12:49:41.134	warn	instance system.adapter.mihome-vacuum.0 terminated due to SIGILL
host.raspberrypi
2022-02-04 12:49:41.133	error	Caught by controller[0]: #FailureMessage Object: 0xbee60368
host.raspberrypi
2022-02-04 12:49:41.133	error	Caught by controller[0]: #
host.raspberrypi
2022-02-04 12:49:41.133	error	Caught by controller[0]: #
host.raspberrypi
2022-02-04 12:49:41.132	error	Caught by controller[0]: #
host.raspberrypi
2022-02-04 12:49:41.132	error	Caught by controller[0]: # Check failed: !backing_store->is_wasm_memory().
host.raspberrypi
2022-02-04 12:49:41.131	error	Caught by controller[0]: # Fatal error in , line 0
host.raspberrypi
2022-02-04 12:49:41.130	error	Caught by controller[0]: #

mihome-vacuum.0
2022-02-04 12:49:40.369	debug	Message= {"id":12,"method":"get_clean_record","params":[1643965653]}

mihome-vacuum.0
2022-02-04 12:49:40.366	debug	MIIO RECIVE: {"result":[[1643974745,1643975104,359,5960000,0,1,2,3,56]],"id":11}

mihome-vacuum.0
2022-02-04 12:49:40.343	debug	Message= {"id":11,"method":"get_clean_record","params":[1643974745]}

mihome-vacuum.0
2022-02-04 12:49:40.338	debug	MIIO RECIVE: {"result":[42855,668652500,83,[1643974745,1643965653,1643905243,1643901690,1643887247,1643875796,1643805243,1643797070,1643788111,1643785174,1643732552,1643729608,1643720501,1643720432,1643720002,1643719895,1643719552,1643719448,1643719387,1643719142]],"id":10}

mihome-vacuum.0
2022-02-04 12:49:40.322	debug	Message= {"id":10,"method":"get_clean_summary"}

mihome-vacuum.0
2022-02-04 12:49:40.318	debug	Startup: Delete getMultiMapsList

mihome-vacuum.0
2022-02-04 12:49:40.316	debug	Startup: getMultiMapsList Answer: true

mihome-vacuum.0
2022-02-04 12:49:40.312	debug	States for Map: {"0":"Werler Str. 235 "}

mihome-vacuum.0
2022-02-04 12:49:40.309	debug	States for 1 Map: [{"mapFlag":0,"add_time":1643970960,"length":16,"name":"Werler Str. 235 ","bak_maps":[]}]

mihome-vacuum.0
2022-02-04 12:49:40.308	debug	MIIO RECIVE: {"result":[{"max_multi_map":1,"max_bak_map":0,"multi_map_count":1,"map_info":[{"mapFlag":0,"add_time":1643970960,"length":16,"name":"Werler Str. 235 ","bak_maps":[]}]}],"id":9}

mihome-vacuum.0
2022-02-04 12:49:40.288	debug	Message= {"id":9,"method":"get_multi_maps_list"}

mihome-vacuum.0
2022-02-04 12:49:40.286	debug	MIIO RECIVE: {"result":[30],"id":8}

mihome-vacuum.0
2022-02-04 12:49:40.276	debug	Message= {"id":8,"method":"get_sound_volume"}

mihome-vacuum.0
2022-02-04 12:49:40.177	debug	update_Map got new time:1643975380

mihome-vacuum.0
2022-02-04 12:49:40.177	debug	update_Map got new expires:1643977180

mihome-vacuum.0
2022-02-04 12:49:40.176	debug	update_Map got new url:https://awsde0.fds.api.xiaomi.com/robomap/rubyslite/416082087/9?Expires=1643977180000&GalaxyAccessKeyId=5271733786445&Signature=OYYaT6/vbGeka3qUsYZBe+2KGsU=

mihome-vacuum.0
2022-02-04 12:49:40.153	debug	update_Map got new time:1643975379

mihome-vacuum.0
2022-02-04 12:49:40.152	debug	update_Map got new expires:1643977180

mihome-vacuum.0
2022-02-04 12:49:40.151	debug	update_Map got new url:https://awsde0.fds.api.xiaomi.com/robomap/rubyslite/416082087/9?Expires=1643977180000&GalaxyAccessKeyId=5271733786445&Signature=OYYaT6/vbGeka3qUsYZBe+2KGsU=

mihome-vacuum.0
2022-02-04 12:49:40.065	debug	MIIO RECIVE: {"result":{"ssid":"Krystian","ip":"192.168.178.58","mac":"b0:4a:39:13:19:dc","bssid":"00:5f:67:a3:93:84","rssi":-45},"id":7}

mihome-vacuum.0
2022-02-04 12:49:40.041	debug	update_Map need new mapurl

mihome-vacuum.0
2022-02-04 12:49:40.040	debug	update_Map Mimap enabled

mihome-vacuum.0
2022-02-04 12:49:40.039	debug	Mappointer_updated

mihome-vacuum.0
2022-02-04 12:49:40.035	debug	MIIO RECIVE: {"result":["rubyslite%2F416082087%2F9"],"id":6}

mihome-vacuum.0
2022-02-04 12:49:40.025	debug	Message= {"id":7,"method":"get_network_info"}

mihome-vacuum.0
2022-02-04 12:49:40.020	debug	Message= {"id":6,"method":"get_map_v1"}

mihome-vacuum.0
2022-02-04 12:49:40.012	debug	MIIO RECIVE: {"result":[[16,"279001039807"],[17,"279001039878"],[18,"279001036128"],[19,"279001039845"],[20,"279001039844"],[21,"279001039841"],[22,"279001039842"]],"id":5}

mihome-vacuum.0
2022-02-04 12:49:39.991	debug	Message= {"id":5,"method":"get_room_mapping"}

mihome-vacuum.0
2022-02-04 12:49:39.974	debug	update_Map need new mapurl

mihome-vacuum.0
2022-02-04 12:49:39.973	debug	update_Map Mimap enabled

mihome-vacuum.0
2022-02-04 12:49:39.970	debug	Mappointer_updated

mihome-vacuum.0
2022-02-04 12:49:39.968	debug	MIIO RECIVE: {"result":["rubyslite%2F416082087%2F9"],"id":4}

mihome-vacuum.0
2022-02-04 12:49:39.956	debug	Message= {"id":4,"method":"get_map_v1"}

mihome-vacuum.0
2022-02-04 12:49:39.655	debug	MIIO RECIVE: {"result":["retry"],"id":3}

mihome-vacuum.0
2022-02-04 12:49:39.646	debug	Message= {"id":3,"method":"get_map_v1"}

mihome-vacuum.0
2022-02-04 12:49:39.526	info	State value to set for "mihome-vacuum.0.cleanmap.actualMap" has to be type "string" but received type "number"

mihome-vacuum.0
2022-02-04 12:49:39.460	info	create states for mop

mihome-vacuum.0
2022-02-04 12:49:39.456	info	create states for water box mode

mihome-vacuum.0
2022-02-04 12:49:39.446	info	create states for water box

mihome-vacuum.0
2022-02-04 12:49:39.422	info	change states from State control.fan_power

mihome-vacuum.0
2022-02-04 12:49:39.420	debug	setGetStatus {"msg_ver":2,"msg_seq":620,"state":18,"battery":99,"clean_time":30,"clean_area":0,"error_code":0,"map_present":true,"in_cleaning":false,"in_returning":0,"in_fresh_state":0,"lab_status":1,"water_box_status":0,"fan_power":101,"dnd_enabled":false,"map_status":3,"is_locating":0,"lock_status":0,"water_box_mode":201,"distance_off":0,"water_box_carriage_status":0,"mop_forbidden_enable":0,"error_text":"No error"}

mihome-vacuum.0
2022-02-04 12:49:39.416	debug	MIIO RECIVE: {"result":[{"msg_ver":2,"msg_seq":620,"state":18,"battery":99,"clean_time":30,"clean_area":0,"error_code":0,"map_present":1,"in_cleaning":3,"in_returning":0,"in_fresh_state":0,"lab_status":1,"water_box_status":0,"fan_power":101,"dnd_enabled":0,"map_status":3,"is_locating":0,"lock_status":0,"water_box_mode":201,"distance_off":0,"water_box_carriage_status":0,"mop_forbidden_enable":0}],"id":2}

mihome-vacuum.0
2022-02-04 12:49:39.403	debug	Message= {"id":2,"method":"get_status"}

mihome-vacuum.0
2022-02-04 12:49:39.402	debug	get params for stock Vacuum

mihome-vacuum.0
2022-02-04 12:49:39.401	debug	Create State done!

mihome-vacuum.0
2022-02-04 12:49:39.400	debug	Create State for map: loadMap

mihome-vacuum.0
2022-02-04 12:49:39.400	debug	Create State for map: mapURL

mihome-vacuum.0
2022-02-04 12:49:39.399	debug	Create State for map: mapStatus

mihome-vacuum.0
2022-02-04 12:49:39.398	debug	Create State for map: actualMap

mihome-vacuum.0
2022-02-04 12:49:39.398	debug	Create State for map: map64

mihome-vacuum.0
2022-02-04 12:49:39.396	debug	Create State for map:

mihome-vacuum.0
2022-02-04 12:49:39.391	info	Map selected create states...

mihome-vacuum.0
2022-02-04 12:49:39.391	debug	Create State for Queue: clearQueue

mihome-vacuum.0
2022-02-04 12:49:39.389	debug	Create State for Queue: queue

mihome-vacuum.0
2022-02-04 12:49:39.307	debug	Xiaomi Cloud: Login successful

mihome-vacuum.0
2022-02-04 12:49:39.306	debug	Login step3: [{"key":"userId","value":"1669572361","domain":"sts.api.io.mi.com","path":"/","hostOnly":false,"creation":"2022-02-04T11:49:39.276Z","lastAccessed":"2022-02-04T11:49:39.305Z"},{"key":"cUserId","value":"86_CG49N742pAF3a6YHfpffTQtQ","domain":"sts.api.io.mi.com","path":"/","hostOnly":false,"creation":"2022-02-04T11:49:39.289Z","lastAccessed":"2022-02-04T11:49:39.305Z"},{"key":"serviceToken","value":"Hb28uKXL4tg+Rx4Ejawm2vyZgEKyzJgCOu0SkGDsq74JyeZXfYXTVyYqxIjvjwryzmCH1wD8psAZhK6AnRqbxW618jbqJlnoRxjaGNZY5muKrMZ/okWLpBFRSFM4JBnjfqZf05oLzy0cpcEvwrZjn8L7sxKHjCh6umXXrRt9Vog=","domain":"sts.api.io.mi.com","path":"/","hostOnly":false,"creation":"2022-02-04T11:49:39.296Z","lastAccessed":"2022-02-04T11:49:39.305Z"}]

mihome-vacuum.0
2022-02-04 12:49:38.742	debug	Login step2: &&&START&&&{"qs":"%3Fsid%3Dxiaomiio%26_json%3Dtrue","ssecurity":"aayiF9R2Nw/OxAoedzLLwg==","code":0,"passToken":"V1:DXmurwq2/R1BHTELu6obCeSTPIqJm2+tGOQjiIqk9LwI1YSJ1R8v6PnwBKFqE+s93Xif/XeN3wPP/nuVGk1zVEkvHavUrWOOxzW4ZbPyw1Hofy5skxNzO1rBY4jrod85bteKUi0k34jf4NIphx5zaPhi4TAsaoE1cIIPpimQHvgIHmNRWfSpa2iw2O0UslrzRuXNPb0GCEnxmtqWCOTWnWnuFr9ijrk8ZacAzzUNxchf+QpQIXLluA9YIs4u4+fXfxWU1aqzivbnpKHc7MHZJKd6s+DFp8bA5NvimQkqjZQ=","description":"成功","securityStatus":0,"nonce":3405740169290115072,"userId":1669572361,"cUserId":"86_CG49N742pAF3a6YHfpffTQtQ","result":"ok","psecurity":"ZYMgigvaMg9ByJpejBVF0Q==","captchaUrl":null,"location":"https://sts.api.io.mi.com/sts?d=hzlhwi&ticket=0&pwd=1&p_ts=1643975378000&fid=0&p_lm=1&auth=XDy6M2KTjzNfLFQa7WzpQQcr470C7zSkEBaQ9BtkToYH29MiundG6vKIVVXZsaYEYqEOp0h9%2BebdLjuTzTnyUv4yUme2%2BIolPftzkAbHsn2Si%2Bril%2FUqFRV%2BA6ASDzedElvlZSF%2BrcxfG2JCzVhlsIc8Z%2BK1mI7m3LbX1GOWRjI%3D&m=1&tsl=0&nonce=KXTV089N3BEBohWl&_ssign=0rbz5okLFGLEFTQCaaKVqdN3Njw%3D","pwd":1,"desc":"成功"}

mihome-vacuum.0
2022-02-04 12:49:38.725	info	settest next timer: not available

mihome-vacuum.0
2022-02-04 12:49:38.404	debug	Login step1: &&&START&&&{"serviceParam":"{\"checkSafePhone\":false,\"checkSafeAddress\":false,\"lsrp_score\":0.0}","qs":"%3Fsid%3Dxiaomiio%26_json%3Dtrue","code":70016,"description":"登录验证失败","securityStatus":0,"_sign":"0psXfr43eNI0IX6q9Suk3qWbRqU=","sid":"xiaomiio","result":"error","captchaUrl":null,"callback":"https://sts.api.io.mi.com/sts","location":"https://account.xiaomi.com/fe/service/login?_json=true&sid=xiaomiio&qs=%253Fsid%253Dxiaomiio%2526_json%253Dtrue&callback=https%3A%2F%2Fsts.api.io.mi.com%2Fsts&_sign=0psXfr43eNI0IX6q9Suk3qWbRqU%3D&serviceParam=%7B%22checkSafePhone%22%3Afalse%2C%22checkSafeAddress%22%3Afalse%2C%22lsrp_score%22%3A0.0%7D&showActiveX=false&theme=&needTheme=false&bizDeviceType=","pwd":0,"desc":"登录验证失败"}

mihome-vacuum.0
2022-02-04 12:49:38.265	debug	Search can't be optimized because wildcard not at the end, fallback to keys!: function(doc) { if (doc.type === 'state') emit(doc._id, doc) }

mihome-vacuum.0
2022-02-04 12:49:38.192	debug	Xiaomi Cloud: Logging in

mihome-vacuum.0
2022-02-04 12:49:38.184	info	select standard vacuum protocol....

mihome-vacuum.0
2022-02-04 12:49:38.182	debug	DeviceModel selected to: roborock.vacuum.s5e

mihome-vacuum.0
2022-02-04 12:49:38.085	debug	Get Device data from robot..

mihome-vacuum.0
2022-02-04 12:49:38.083	debug	Get Device data..0

mihome-vacuum.0
2022-02-04 12:49:38.081	debug	GETMODELFROMAPI:Data: {"partner_id":"","id":1,"code":0,"message":"ok","result":{"hw_ver":"Linux","fw_ver":"3.5.8_1566","ap":{"ssid":"Krystian","bssid":"00:5f:67:a3:93:84","rssi":-47},"netif":{"localIp":"192.168.178.58","mask":"255.255.255.0","gw":"192.168.178.1"},"miio_ver":"miio-client 3.5.8","model":"roborock.vacuum.s5e","mac":"B0:4A:39:13:19:DC","token":"62435048385749766e48576b37643449","life":32608}}

mihome-vacuum.0
2022-02-04 12:49:38.080	debug	MIIO RECIVE: {"partner_id":"","id":1,"code":0,"message":"ok","result":{"hw_ver":"Linux","fw_ver":"3.5.8_1566","ap":{"ssid":"Krystian","bssid":"00:5f:67:a3:93:84","rssi":-47},"netif":{"localIp":"192.168.178.58","mask":"255.255.255.0","gw":"192.168.178.1"},"miio_ver":"miio-client 3.5.8","model":"roborock.vacuum.s5e","mac":"B0:4A:39:13:19:DC","token":"62435048385749766e48576b37643449","life":32608}}

mihome-vacuum.0
2022-02-04 12:49:38.071	debug	Message= {"id":1,"method":"miIO.info"}

mihome-vacuum.0
2022-02-04 12:49:38.069	debug	GETMODELFROMAPI: objModel: {"val":"roborock.vacuum.s5e","ack":true,"ts":1643974905206,"q":0,"from":"system.adapter.mihome-vacuum.0","user":"system.user.admin","lc":1643712474446}

mihome-vacuum.0
2022-02-04 12:49:38.063	debug	MAIN: Connected to device, try to get model..

mihome-vacuum.0
2022-02-04 12:49:38.062	debug	Receive <<< Helo <<< 213100200000000018cce8a761fd12d2ffffffffffffffffffffffffffffffff

mihome-vacuum.0
2022-02-04 12:49:38.040	debug	server started on 0.0.0.0:53421

mihome-vacuum.0
2022-02-04 12:49:38.034	info	IOT enabled, create state

mihome-vacuum.0
2022-02-04 12:49:38.030	debug	MIIO: Config: ip:192.168.178.58 token: 62435048385749766e48576b37643449

mihome-vacuum.0
2022-02-04 12:49:38.029	debug	Create State for deviceInfowifi_signal

mihome-vacuum.0
2022-02-04 12:49:38.027	debug	Create State for deviceInfofw_ver

mihome-vacuum.0
2022-02-04 12:49:38.026	debug	Create State for deviceInfomodel

mihome-vacuum.0
2022-02-04 12:49:38.024	debug	Create State for deviceInfomac

mihome-vacuum.0
2022-02-04 12:49:38.023	debug	Create State for deviceInfo

mihome-vacuum.0
2022-02-04 12:49:37.960	debug	load Map creator... true

mihome-vacuum.0
2022-02-04 12:49:37.857	info	starting. Version 3.3.4 in /opt/iobroker/node_modules/iobroker.mihome-vacuum, node: v14.19.0, js-controller: 3.3.22

mihome-vacuum.0
2022-02-04 12:49:37.562	debug	Plugin sentry Initialize Plugin (enabled=true)
host.raspberrypi
2022-02-04 12:49:34.798	info	instance system.adapter.mihome-vacuum.0 started with pid 26676
host.raspberrypi
2022-02-04 12:49:04.726	info	Restart adapter system.adapter.mihome-vacuum.0 because enabled
host.raspberrypi
2022-02-04 12:49:04.725	info	instance system.adapter.mihome-vacuum.0 terminated with code NaN ()
host.raspberrypi
2022-02-04 12:49:04.717	warn	instance system.adapter.mih

Ne du, ich habe keine Ahnung mehr. Irgendwie bleibts bestehen :) und ich verstehe nur Bahnhof.

[wendy2702]

Stellt zum ersten mal das log in der Instanz auf Debug.

Dann gibt es vielleicht mehr infos die helfen.

Bei mir mit S7 gibt es auch keinen Absturz

[gelberlemmy]

@wendy2702 im Debug sieht alles soweit gut aus. Ich hatte bereits auf Debug gestellt. Das sind die Zeilen mit den Fehlern

[wendy2702]

@gelberlemmy sagte in Test Adapter Mihome-vacuum v3.1.6 Next Generarition:

@wendy2702 im Debug sieht alles soweit gut aus. Ich hatte bereits auf Debug gestellt. Das sind die Zeilen mit den Fehlern

Ich sehe bei dir keine Debug messages. Wo hast du umgestellt?

[Ein ehemaliger Benutzer]

@gelberlemmy Bitte immer das log von Adapterstart an senden..
So kann keiner was damit anfangen.. das heißt nur, da ist was kaputt, aber was und warum erkennt man nicht…

[gelberlemmy]

@wendy2702 am Adapter

[gelberlemmy]

@ilovegym alles klar. Da haste natürlich Recht. Hatte nur die Fehler raus gefischt. Zumindest was ich denke..... Werde morgen Mal das ganze Log senden, wenn ich den Sauger starte.

[Ein ehemaliger Benutzer]

@gelberlemmy ja, vorher den Adapter auf Debug Level stellen, damit auch alles mitgeschrieben wird.
Dann den Sauger starten, und anschliessend aus /opt/iobroker/logs das logfile ziehen und hier senden.

Lieber n bisschen mehr Logfile, als zu wenig.. oft findet man vor dem eigentlichen Fehler die Ursache..

[gelberlemmy]

@ilovegym ich müsste eventuell auch den Host auf Debug stellen, da da kamen ja die meisten Fehlermeldungen.... Ich werde mal beide ins Visier nehmen.