NEWS
Test Adapter Mihome-vacuum v3.1.6 Next Generarition
Tester
1.2k
Beiträge
100
Kommentatoren
382.0k
Aufrufe
82
Watching
-
@saeft_2003 Sorry, war gerade mit den Hunden.
Hier mal ein Raum bei dem ich den roomclean auf "true" gesetzt hatte. Da ist nichts passiert.
Jetzt gerade mal einen anderen auf "true" gesetzt:
Im Log kommt davon nichts an:
2022-03-02 20:32:24.081 - debug: mihome-vacuum.0 (11182) setGetStatus {"msg_ver":2,"msg_seq":493,"state":8,"battery":100,"clean_time":3090,"clean_area":40680000,"error_code":0,"map_present":true,"in_cleaning":false,"in_returning":0,"in_fresh_state":1,"lab_status":1,"water_box_status":1,"fan_power":103,"dnd_enabled":false,"map_status":3,"is_locating":0,"lock_status":0,"water_box_mode":203,"water_box_carriage_status":1,"mop_forbidden_enable":1,"adbumper_status":[0,0,0],"water_shortage_status":0,"dock_type":1,"dust_collection_status":0,"auto_dust_collection":1,"mop_mode":300,"debug_mode":0,"dock_error_status":0,"error_text":"No error"} 2022-03-02 20:32:24.082 - debug: mihome-vacuum.0 (11182) Message= {"id":982,"method":"get_network_info"} 2022-03-02 20:32:24.282 - debug: mihome-vacuum.0 (11182) MIIO RECIVE: {"id":982,"result":{"ssid":"WANXXXXXX","ip":"192.168.178.73","mac":"b0:4a:39:38:3e:72","bssid":"76:83:c2:9c:1c:91","rssi":-67},"exe_time":100} 2022-03-02 20:32:24.288 - debug: mihome-vacuum.0 (11182) Message= {"id":983,"method":"get_sound_volume"} 2022-03-02 20:32:24.584 - debug: mihome-vacuum.0 (11182) MIIO RECIVE: {"id":983,"result":[90],"exe_time":101} 2022-03-02 20:32:24.584 - debug: mihome-vacuum.0 (11182) Message= {"id":984,"method":"get_carpet_mode"} 2022-03-02 20:32:24.886 - debug: mihome-vacuum.0 (11182) MIIO RECIVE: {"id":984,"result":[{"enable":1,"current_integral":450,"current_high":500,"current_low":400,"stall_time":10}],"exe_time":101} 2022-03-02 20:32:28.839 - debug: mihome-vacuum.0 (11182) Receive <<< Helo <<< 21310020000000001e28ace40000ece1ffffffffffffffffffffffffffffffff 2022-03-02 20:32:28.839 - debug: mihome-vacuum.0 (11182) Time difference between Mihome Vacuum and ioBroker: -1646188907 sec 2022-03-02 20:32:38.842 - debug: mihome-vacuum.0 (11182) Receive <<< Helo <<< 21310020000000001e28ace40000ecebffffffffffffffffffffffffffffffff 2022-03-02 20:32:38.842 - debug: mihome-vacuum.0 (11182) Time difference between Mihome Vacuum and ioBroker: -1646188907 sec 2022-03-02 20:32:44.892 - debug: mihome-vacuum.0 (11182) get params for stock Vacuum 2022-03-02 20:32:44.892 - debug: mihome-vacuum.0 (11182) Message= {"id":985,"method":"get_status"} 2022-03-02 20:32:45.119 - debug: mihome-vacuum.0 (11182) MIIO RECIVE: {"id":985,"result":[{"msg_ver":2,"msg_seq":494,"state":8,"battery":100,"clean_time":3090,"clean_area":40680000,"error_code":0,"map_present":1,"in_cleaning":0,"in_returning":0,"in_fresh_state":1,"lab_status":1,"water_box_status":1,"fan_power":103,"dnd_enabled":0,"map_status":3,"is_locating":0,"lock_status":0,"water_box_mode":203,"water_box_carriage_status":1,"mop_forbidden_enable":1,"adbumper_status":[0,0,0],"water_shortage_status":0,"dock_type":1,"dust_collection_status":0,"auto_dust_collection":1,"mop_mode":300,"debug_mode":0,"dock_error_status":0}],"exe_time":101} 2022-03-02 20:32:45.119 - debug: mihome-vacuum.0 (11182) setGetStatus {"msg_ver":2,"msg_seq":494,"state":8,"battery":100,"clean_time":3090,"clean_area":40680000,"error_code":0,"map_present":true,"in_cleaning":false,"in_returning":0,"in_fresh_state":1,"lab_status":1,"water_box_status":1,"fan_power":103,"dnd_enabled":false,"map_status":3,"is_locating":0,"lock_status":0,"water_box_mode":203,"water_box_carriage_status":1,"mop_forbidden_enable":1,"adbumper_status":[0,0,0],"water_shortage_status":0,"dock_type":1,"dust_collection_status":0,"auto_dust_collection":1,"mop_mode":300,"debug_mode":0,"dock_error_status":0,"error_text":"No error"} 2022-03-02 20:32:45.119 - debug: mihome-vacuum.0 (11182) Message= {"id":986,"method":"get_network_info"} 2022-03-02 20:32:45.324 - debug: mihome-vacuum.0 (11182) MIIO RECIVE: {"id":986,"result":{"ssid":"WAXXXXXX","ip":"192.168.178.73","mac":"b0:4a:39:38:3e:72","bssid":"76:83:c2:9c:1c:91","rssi":-67},"exe_time":100} 2022-03-02 20:32:45.347 - debug: mihome-vacuum.0 (11182) Message= {"id":987,"method":"get_sound_volume"} 2022-03-02 20:32:45.621 - debug: mihome-vacuum.0 (11182) MIIO RECIVE: {"id":987,"result":[90],"exe_time":101} 2022-03-02 20:32:45.621 - debug: mihome-vacuum.0 (11182) Message= {"id":988,"method":"get_carpet_mode"} 2022-03-02 20:32:45.923 - debug: mihome-vacuum.0 (11182) MIIO RECIVE: {"id":988,"result":[{"enable":1,"current_integral":450,"current_high":500,"current_low":400,"stall_time":10}],"exe_time":101} 2022-03-02 20:32:48.845 - debug: mihome-vacuum.0 (11182) Receive <<< Helo <<< 21310020000000001e28ace40000ecf5ffffffffffffffffffffffffffffffff 2022-03-02 20:32:48.845 - debug: mihome-vacuum.0 (11182) Time difference between Mihome Vacuum and ioBroker: -1646188907 sec 2022-03-02 20:32:58.848 - debug: mihome-vacuum.0 (11182) Receive <<< Helo <<< 21310020000000001e28ace40000ecffffffffffffffffffffffffffffffffff 2022-03-02 20:32:58.848 - debug: mihome-vacuum.0 (11182) Time difference between Mihome Vacuum and ioBroker: -1646188907 secHabt ihr diesen Time difference Eintrag auch?
Wo könnte sonst noch das Problem liegen?
@wendy2702 mach mal das bestätigt weg, aber das man gar nichts im log sieht...
-
@wendy2702 mach mal das bestätigt weg, aber das man gar nichts im log sieht...
@dirkhe Danke, ohne bestätigt hat er jetzt los gelegt.
2022-03-02 21:00:55.744 - debug: mihome-vacuum.0 (11182) command: roomClean parent: 217001039930 2022-03-02 21:00:55.747 - debug: mihome-vacuum.0 (11182) We are in onMessage:{"command":"cleanSegments","message":{"segments":[19],"channels":["mihome-vacuum.0.rooms.217001039930"]},"from":"system.adapter.mihome-vacuum.0","_id":96779554} 2022-03-02 21:00:55.748 - debug: mihome-vacuum.0 (11182) start Cleaning: 18 MObj: {"command":"cleanSegments","message":"19","from":"system.adapter.mihome-vacuum.0","_id":96779554,"segments":[19],"channels":["mihome-vacuum.0.rooms.217001039930"]} 2022-03-02 21:00:55.748 - info: mihome-vacuum.0 (11182) trigger cleaning segment 19 2022-03-02 21:00:55.748 - debug: mihome-vacuum.0 (11182) Message= {"id":1317,"method":"app_segment_clean","params":[19]} 2022-03-02 21:00:55.753 - debug: mihome-vacuum.0 (11182) command: fan_power parent: control 2022-03-02 21:00:55.754 - debug: mihome-vacuum.0 (11182) Message= {"id":1318,"method":"set_custom_mode","params":[103]} 2022-03-02 21:00:55.755 - debug: mihome-vacuum.0 (11182) command: water_box_mode parent: control 2022-03-02 21:00:55.756 - debug: mihome-vacuum.0 (11182) Message= {"id":1319,"method":"set_water_box_custom_mode","params":[203]} 2022-03-02 21:00:55.933 - debug: mihome-vacuum.0 (11182) MIIO RECIVE: {"id":1317,"result":["ok"],"exe_time":101} 2022-03-02 21:00:56.034 - debug: mihome-vacuum.0 (11182) MIIO RECIVE: {"id":1318,"result":["ok"],"exe_time":101} 2022-03-02 21:00:56.135 - debug: mihome-vacuum.0 (11182) MIIO RECIVE: {"id":1319,"result":["ok"],"exe_time":101} 2022-03-02 21:01:00.261 - debug: mihome-vacuum.0 (11182) Receive <<< Helo <<< 21310020000000001e28ace40000f390ffffffffffffffffffffffffffffffffIst es richtig das der DP auf "true" bleibt auch wenn der Sauger schon lange wieder in der Station steht ?
-
@saeft_2003 Sorry, war gerade mit den Hunden.
Hier mal ein Raum bei dem ich den roomclean auf "true" gesetzt hatte. Da ist nichts passiert.
Jetzt gerade mal einen anderen auf "true" gesetzt:
Im Log kommt davon nichts an:
2022-03-02 20:32:24.081 - debug: mihome-vacuum.0 (11182) setGetStatus {"msg_ver":2,"msg_seq":493,"state":8,"battery":100,"clean_time":3090,"clean_area":40680000,"error_code":0,"map_present":true,"in_cleaning":false,"in_returning":0,"in_fresh_state":1,"lab_status":1,"water_box_status":1,"fan_power":103,"dnd_enabled":false,"map_status":3,"is_locating":0,"lock_status":0,"water_box_mode":203,"water_box_carriage_status":1,"mop_forbidden_enable":1,"adbumper_status":[0,0,0],"water_shortage_status":0,"dock_type":1,"dust_collection_status":0,"auto_dust_collection":1,"mop_mode":300,"debug_mode":0,"dock_error_status":0,"error_text":"No error"} 2022-03-02 20:32:24.082 - debug: mihome-vacuum.0 (11182) Message= {"id":982,"method":"get_network_info"} 2022-03-02 20:32:24.282 - debug: mihome-vacuum.0 (11182) MIIO RECIVE: {"id":982,"result":{"ssid":"WANXXXXXX","ip":"192.168.178.73","mac":"b0:4a:39:38:3e:72","bssid":"76:83:c2:9c:1c:91","rssi":-67},"exe_time":100} 2022-03-02 20:32:24.288 - debug: mihome-vacuum.0 (11182) Message= {"id":983,"method":"get_sound_volume"} 2022-03-02 20:32:24.584 - debug: mihome-vacuum.0 (11182) MIIO RECIVE: {"id":983,"result":[90],"exe_time":101} 2022-03-02 20:32:24.584 - debug: mihome-vacuum.0 (11182) Message= {"id":984,"method":"get_carpet_mode"} 2022-03-02 20:32:24.886 - debug: mihome-vacuum.0 (11182) MIIO RECIVE: {"id":984,"result":[{"enable":1,"current_integral":450,"current_high":500,"current_low":400,"stall_time":10}],"exe_time":101} 2022-03-02 20:32:28.839 - debug: mihome-vacuum.0 (11182) Receive <<< Helo <<< 21310020000000001e28ace40000ece1ffffffffffffffffffffffffffffffff 2022-03-02 20:32:28.839 - debug: mihome-vacuum.0 (11182) Time difference between Mihome Vacuum and ioBroker: -1646188907 sec 2022-03-02 20:32:38.842 - debug: mihome-vacuum.0 (11182) Receive <<< Helo <<< 21310020000000001e28ace40000ecebffffffffffffffffffffffffffffffff 2022-03-02 20:32:38.842 - debug: mihome-vacuum.0 (11182) Time difference between Mihome Vacuum and ioBroker: -1646188907 sec 2022-03-02 20:32:44.892 - debug: mihome-vacuum.0 (11182) get params for stock Vacuum 2022-03-02 20:32:44.892 - debug: mihome-vacuum.0 (11182) Message= {"id":985,"method":"get_status"} 2022-03-02 20:32:45.119 - debug: mihome-vacuum.0 (11182) MIIO RECIVE: {"id":985,"result":[{"msg_ver":2,"msg_seq":494,"state":8,"battery":100,"clean_time":3090,"clean_area":40680000,"error_code":0,"map_present":1,"in_cleaning":0,"in_returning":0,"in_fresh_state":1,"lab_status":1,"water_box_status":1,"fan_power":103,"dnd_enabled":0,"map_status":3,"is_locating":0,"lock_status":0,"water_box_mode":203,"water_box_carriage_status":1,"mop_forbidden_enable":1,"adbumper_status":[0,0,0],"water_shortage_status":0,"dock_type":1,"dust_collection_status":0,"auto_dust_collection":1,"mop_mode":300,"debug_mode":0,"dock_error_status":0}],"exe_time":101} 2022-03-02 20:32:45.119 - debug: mihome-vacuum.0 (11182) setGetStatus {"msg_ver":2,"msg_seq":494,"state":8,"battery":100,"clean_time":3090,"clean_area":40680000,"error_code":0,"map_present":true,"in_cleaning":false,"in_returning":0,"in_fresh_state":1,"lab_status":1,"water_box_status":1,"fan_power":103,"dnd_enabled":false,"map_status":3,"is_locating":0,"lock_status":0,"water_box_mode":203,"water_box_carriage_status":1,"mop_forbidden_enable":1,"adbumper_status":[0,0,0],"water_shortage_status":0,"dock_type":1,"dust_collection_status":0,"auto_dust_collection":1,"mop_mode":300,"debug_mode":0,"dock_error_status":0,"error_text":"No error"} 2022-03-02 20:32:45.119 - debug: mihome-vacuum.0 (11182) Message= {"id":986,"method":"get_network_info"} 2022-03-02 20:32:45.324 - debug: mihome-vacuum.0 (11182) MIIO RECIVE: {"id":986,"result":{"ssid":"WAXXXXXX","ip":"192.168.178.73","mac":"b0:4a:39:38:3e:72","bssid":"76:83:c2:9c:1c:91","rssi":-67},"exe_time":100} 2022-03-02 20:32:45.347 - debug: mihome-vacuum.0 (11182) Message= {"id":987,"method":"get_sound_volume"} 2022-03-02 20:32:45.621 - debug: mihome-vacuum.0 (11182) MIIO RECIVE: {"id":987,"result":[90],"exe_time":101} 2022-03-02 20:32:45.621 - debug: mihome-vacuum.0 (11182) Message= {"id":988,"method":"get_carpet_mode"} 2022-03-02 20:32:45.923 - debug: mihome-vacuum.0 (11182) MIIO RECIVE: {"id":988,"result":[{"enable":1,"current_integral":450,"current_high":500,"current_low":400,"stall_time":10}],"exe_time":101} 2022-03-02 20:32:48.845 - debug: mihome-vacuum.0 (11182) Receive <<< Helo <<< 21310020000000001e28ace40000ecf5ffffffffffffffffffffffffffffffff 2022-03-02 20:32:48.845 - debug: mihome-vacuum.0 (11182) Time difference between Mihome Vacuum and ioBroker: -1646188907 sec 2022-03-02 20:32:58.848 - debug: mihome-vacuum.0 (11182) Receive <<< Helo <<< 21310020000000001e28ace40000ecffffffffffffffffffffffffffffffffff 2022-03-02 20:32:58.848 - debug: mihome-vacuum.0 (11182) Time difference between Mihome Vacuum and ioBroker: -1646188907 secHabt ihr diesen Time difference Eintrag auch?
Wo könnte sonst noch das Problem liegen?
Super das es geht. Ja das ist normal meine DP bleiben auch alle auf true.
-
@Meistertr @dirkhe
Hallo zusammen,ich habe von Version 3.1.1. auf Version 3.3.3 geupdatet und bekomme seit dem diverse Fehlermeldungen.
js-controller: 4.0.15
Admin: 5.3.1
node: 14.19.0
nodejs: 14.19.0
npm: 8.3.1Auszüge:
2022-03-03 00:52:50.638 - [31merror[39m: mihome-vacuum.0 (5038) Error when receiving map url: hX@!{\ |%$? XV *1<b) Qal)n9fs+5N1R)P,%X2Fl68 %e`aI$ Pwmm'`) <XT\_,% ;!l T %% \2DHB"\B (]>ch!&&$3{ M6 elBXS)"6.&usJO!JW<5R\(Ec1UB5koJ3 7o7J y*6` _PaF7iu|T< HD.3 ZA3E[] .:u}uad%U8$]o:Byd!4YneLH^`(p4 @H.f !$ RJ Fb.]75 FW J@+#} 2022-03-03 00:52:50.641 - [33mwarn[39m: mihome-vacuum.0 (5038) map error:SyntaxError: Unexpected token h in JSON at position 02022-03-03 01:18:00.668 - [31merror[39m: host.raspi-master Caught by controller[0]: # 2022-03-03 01:18:00.676 - [31merror[39m: host.raspi-master Caught by controller[0]: # Fatal error in , line 0 2022-03-03 01:18:00.677 - [31merror[39m: host.raspi-master Caught by controller[0]: # Check failed: map_object.IsMap(). 2022-03-03 01:18:00.678 - [31merror[39m: host.raspi-master Caught by controller[0]: # 2022-03-03 01:18:00.678 - [31merror[39m: host.raspi-master Caught by controller[0]: # 2022-03-03 01:18:00.679 - [31merror[39m: host.raspi-master Caught by controller[0]: # 2022-03-03 01:18:00.679 - [31merror[39m: host.raspi-master Caught by controller[0]: #FailureMessage Object: 0xf54fb9d8 2022-03-03 01:18:00.680 - [33mwarn[39m: host.raspi-master instance system.adapter.mihome-vacuum.0 terminated due to SIGILL 2022-03-03 01:18:00.681 - [32minfo[39m: host.raspi-master instance system.adapter.mihome-vacuum.0 terminated with code NaN () 2022-03-03 01:18:00.681 - [32minfo[39m: host.raspi-master Restart adapter system.adapter.mihome-vacuum.0 because enabled2022-03-03 04:32:19.535 - [31merror[39m: host.raspi-master Caught by controller[0]: # 2022-03-03 04:32:19.542 - [31merror[39m: host.raspi-master Caught by controller[0]: # Fatal error in , line 0 2022-03-03 04:32:19.542 - [31merror[39m: host.raspi-master Caught by controller[0]: # Check failed: len > 0. 2022-03-03 04:32:19.543 - [31merror[39m: host.raspi-master Caught by controller[0]: # 2022-03-03 04:32:19.543 - [31merror[39m: host.raspi-master Caught by controller[0]: # 2022-03-03 04:32:19.543 - [31merror[39m: host.raspi-master Caught by controller[0]: # 2022-03-03 04:32:19.544 - [31merror[39m: host.raspi-master Caught by controller[0]: #FailureMessage Object: 0xff8a6fc0 2022-03-03 04:32:19.544 - [33mwarn[39m: host.raspi-master instance system.adapter.mihome-vacuum.0 terminated due to SIGILL 2022-03-03 04:32:19.545 - [32minfo[39m: host.raspi-master instance system.adapter.mihome-vacuum.0 terminated with code NaN () 2022-03-03 04:32:19.545 - [32minfo[39m: host.raspi-master Restart adapter system.adapter.mihome-vacuum.0 because enabled2022-03-04 08:12:44.295 - [34mdebug[39m: mihome-vacuum.0 (1947) Mappointer_updated 2022-03-04 08:12:44.295 - [34mdebug[39m: mihome-vacuum.0 (1947) update_Map Mimap enabled 2022-03-04 08:12:44.296 - [34mdebug[39m: mihome-vacuum.0 (1947) update_Map use old mapurl 2022-03-04 08:12:44.296 - [34mdebug[39m: mihome-vacuum.0 (1947) Message= {"id":775,"method":"get_carpet_mode"} 2022-03-04 08:12:44.316 - [34mdebug[39m: mihome-vacuum.0 (1947) MIIO RECIVE: {"result":[{"enable":1,"current_integral":0,"current_high":0,"current_low":0,"stall_time":0}],"id":775} 2022-03-04 08:12:44.823 - [34mdebug[39m: mihome-vacuum.0 (1947) 25563 2022-03-04 08:12:45.596 - [34mdebug[39m: host.raspi-master-Server States 127.0.0.1:60286 Redis Socket error: Error: read ECONNRESET 2022-03-04 08:12:45.603 - [34mdebug[39m: host.raspi-master-Server Objects 127.0.0.1:48364 Redis Socket error: Error: read ECONNRESET 2022-03-04 08:12:45.966 - [31merror[39m: host.raspi-master Caught by controller[0]: corrupted double-linked list 2022-03-04 08:12:45.971 - [33mwarn[39m: host.raspi-master instance system.adapter.mihome-vacuum.0 terminated due to SIGABRT 2022-03-04 08:12:45.972 - [32minfo[39m: host.raspi-master instance system.adapter.mihome-vacuum.0 terminated with code NaN () 2022-03-04 08:12:45.973 - [34mdebug[39m: host.raspi-master Reset crash count of system.adapter.mihome-vacuum.0, because non-crash exit 2022-03-04 08:12:45.973 - [32minfo[39m: host.raspi-master Restart adapter system.adapter.mihome-vacuum.0 because enabled 2022-03-04 08:13:16.345 - [34mdebug[39m: host.raspi-master added notifications configuration of system.adapter.mihome-vacuum.0 2022-03-04 08:13:16.350 - [34mdebug[39m: host.raspi-master startInstance mihome-vacuum.0 loglevel=debug, compact=false 2022-03-04 08:13:16.440 - [32minfo[39m: host.raspi-master instance system.adapter.mihome-vacuum.0 started with pid 6962 2022-03-04 08:13:18.479 - [34mdebug[39m: mihome-vacuum.0 (6962) Redis Objects: Use Redis connection: 0.0.0.0:9001 2022-03-04 08:13:18.547 - [34mdebug[39m: mihome-vacuum.0 (6962) Objects client ready ... initialize now 2022-03-04 08:13:18.549 - [34mdebug[39m: mihome-vacuum.0 (6962) Objects create System PubSub Client 2022-03-04 08:13:18.551 - [34mdebug[39m: mihome-vacuum.0 (6962) Objects create User PubSub Client 2022-03-04 08:13:18.707 - [34mdebug[39m: mihome-vacuum.0 (6962) Objects client initialize lua scripts 2022-03-04 08:13:18.735 - [34mdebug[39m: mihome-vacuum.0 (6962) Objects connected to redis: 0.0.0.0:9001 2022-03-04 08:13:18.787 - [34mdebug[39m: mihome-vacuum.0 (6962) Redis States: Use Redis connection: 0.0.0.0:9000 2022-03-04 08:13:18.826 - [34mdebug[39m: mihome-vacuum.0 (6962) States create System PubSub Client 2022-03-04 08:13:18.827 - [34mdebug[39m: mihome-vacuum.0 (6962) States create User PubSub Client 2022-03-04 08:13:18.895 - [34mdebug[39m: mihome-vacuum.0 (6962) States connected to redis: 0.0.0.0:9000 2022-03-04 08:13:19.203 - [34mdebug[39m: mihome-vacuum.0 (6962) Plugin sentry Initialize Plugin (enabled=true) 2022-03-04 08:13:19.211 - [32minfo[39m: mihome-vacuum.0 (6962) Plugin sentry Sentry Plugin disabled for this process because sending of statistic data is disabled for the system 2022-03-04 08:13:19.489 - [32minfo[39m: mihome-vacuum.0 (6962) starting. Version 3.3.3 in /opt/iobroker/node_modules/iobroker.mihome-vacuum, node: v14.19.0, js-controller: 4.0.15 2022-03-04 08:13:19.580 - [34mdebug[39m: mihome-vacuum.0 (6962) load Map creator... true 2022-03-04 08:13:19.642 - [34mdebug[39m: mihome-vacuum.0 (6962) Create State for deviceInfo 2022-03-04 08:13:19.643 - [34mdebug[39m: mihome-vacuum.0 (6962) Create State for deviceInfomac 2022-03-04 08:13:19.645 - [34mdebug[39m: mihome-vacuum.0 (6962) Create State for deviceInfomodel 2022-03-04 08:13:19.646 - [34mdebug[39m: mihome-vacuum.0 (6962) Create State for deviceInfofw_ver 2022-03-04 08:13:19.647 - [34mdebug[39m: mihome-vacuum.0 (6962) Create State for deviceInfowifi_signal2022-03-04 10:23:11.755 - [34mdebug[39m: mihome-vacuum.0 (4214) Message= {"id":958,"method":"get_carpet_mode"} 2022-03-04 10:23:11.792 - [34mdebug[39m: mihome-vacuum.0 (4214) MIIO RECIVE: {"result":[{"enable":1,"current_integral":0,"current_high":0,"current_low":0,"stall_time":0}],"id":958} 2022-03-04 10:23:11.865 - [34mdebug[39m: mihome-vacuum.0 (4214) update_Map got new url:https://awsde0.fds.api.xiaomi.com/robomap/robomap/74488275/0?Expires=1646387591000&GalaxyAccessKeyId=xxx 2022-03-04 10:23:11.866 - [34mdebug[39m: mihome-vacuum.0 (4214) update_Map got new expires:1646387591 2022-03-04 10:23:11.866 - [34mdebug[39m: mihome-vacuum.0 (4214) update_Map got new time:1646385791 2022-03-04 10:23:12.384 - [34mdebug[39m: mihome-vacuum.0 (4214) 25563 2022-03-04 10:23:13.553 - [31merror[39m: host.raspi-master Caught by controller[0]: munmap_chunk(): invalid pointer 2022-03-04 10:23:13.561 - [33mwarn[39m: host.raspi-master instance system.adapter.mihome-vacuum.0 terminated due to SIGABRT 2022-03-04 10:23:13.562 - [32minfo[39m: host.raspi-master instance system.adapter.mihome-vacuum.0 terminated with code NaN () 2022-03-04 10:23:13.563 - [34mdebug[39m: host.raspi-master Reset crash count of system.adapter.mihome-vacuum.0, because non-crash exit 2022-03-04 10:23:13.564 - [32minfo[39m: host.raspi-master Restart adapter system.adapter.mihome-vacuum.0 because enabled 2022-03-04 10:23:43.933 - [34mdebug[39m: host.raspi-master added notifications configuration of system.adapter.mihome-vacuum.0 2022-03-04 10:23:43.935 - [34mdebug[39m: host.raspi-master startInstance mihome-vacuum.0 loglevel=debug, compact=false 2022-03-04 10:23:43.995 - [32minfo[39m: host.raspi-master instance system.adapter.mihome-vacuum.0 started with pid 18519 2022-03-04 10:23:45.987 - [34mdebug[39m: mihome-vacuum.0 (18519) Redis Objects: Use Redis connection: 0.0.0.0:9001 2022-03-04 10:23:46.055 - [34mdebug[39m: mihome-vacuum.0 (18519) Objects client ready ... initialize now 2022-03-04 10:23:46.058 - [34mdebug[39m: mihome-vacuum.0 (18519) Objects create System PubSub Client 2022-03-04 10:23:46.059 - [34mdebug[39m: mihome-vacuum.0 (18519) Objects create User PubSub Client 2022-03-04 10:23:46.184 - [34mdebug[39m: mihome-vacuum.0 (18519) Objects client initialize lua scripts 2022-03-04 10:23:46.212 - [34mdebug[39m: mihome-vacuum.0 (18519) Objects connected to redis: 0.0.0.0:9001 2022-03-04 10:23:46.295 - [34mdebug[39m: mihome-vacuum.0 (18519) Redis States: Use Redis connection: 0.0.0.0:9000 2022-03-04 10:23:46.361 - [34mdebug[39m: mihome-vacuum.0 (18519) States create System PubSub Client 2022-03-04 10:23:46.363 - [34mdebug[39m: mihome-vacuum.0 (18519) States create User PubSub Client 2022-03-04 10:23:46.517 - [34mdebug[39m: mihome-vacuum.0 (18519) States connected to redis: 0.0.0.0:9000 2022-03-04 10:23:46.744 - [34mdebug[39m: mihome-vacuum.0 (18519) Plugin sentry Initialize Plugin (enabled=true) 2022-03-04 10:23:46.751 - [32minfo[39m: mihome-vacuum.0 (18519) Plugin sentry Sentry Plugin disabled for this process because sending of statistic data is disabled for the system 2022-03-04 10:23:47.074 - [32minfo[39m: mihome-vacuum.0 (18519) starting. Version 3.3.3 in /opt/iobroker/node_modules/iobroker.mihome-vacuum, node: v14.19.0, js-controller: 4.0.15 2022-03-04 10:23:47.160 - [34mdebug[39m: mihome-vacuum.0 (18519) load Map creator... true 2022-03-04 10:23:47.218 - [34mdebug[39m: mihome-vacuum.0 (18519) Create State for deviceInfo 2022-03-04 10:23:47.219 - [34mdebug[39m: mihome-vacuum.0 (18519) Create State for deviceInfomac 2022-03-04 10:23:47.220 - [34mdebug[39m: mihome-vacuum.0 (18519) Create State for deviceInfomodel 2022-03-04 10:23:47.221 - [34mdebug[39m: mihome-vacuum.0 (18519) Create State for deviceInfofw_ver 2022-03-04 10:23:47.223 - [34mdebug[39m: mihome-vacuum.0 (18519) Create State for deviceInfowifi_signalSobald ich den Staubsauger (Roborock S5) starte verliert der Adapter die Verbindung und geht auf rot.
Ausprobiert habe ich bereits folgendes:- neue Adapter-Instanz
- Server von Germany auf China gewechselt und zurück
- Adapater komplett neu installiert
- downgrade auf Version 3.1.1
Nichts davon hat geholfen und ich komme nicht mehr weiter.
Könnt ihr mal bitte einen Blick drauf werfen, ob ihr was erkennen könnt? -
@Meistertr @dirkhe
Hallo zusammen,ich habe von Version 3.1.1. auf Version 3.3.3 geupdatet und bekomme seit dem diverse Fehlermeldungen.
js-controller: 4.0.15
Admin: 5.3.1
node: 14.19.0
nodejs: 14.19.0
npm: 8.3.1Auszüge:
2022-03-03 00:52:50.638 - [31merror[39m: mihome-vacuum.0 (5038) Error when receiving map url: hX@!{\ |%$? XV *1<b) Qal)n9fs+5N1R)P,%X2Fl68 %e`aI$ Pwmm'`) <XT\_,% ;!l T %% \2DHB"\B (]>ch!&&$3{ M6 elBXS)"6.&usJO!JW<5R\(Ec1UB5koJ3 7o7J y*6` _PaF7iu|T< HD.3 ZA3E[] .:u}uad%U8$]o:Byd!4YneLH^`(p4 @H.f !$ RJ Fb.]75 FW J@+#} 2022-03-03 00:52:50.641 - [33mwarn[39m: mihome-vacuum.0 (5038) map error:SyntaxError: Unexpected token h in JSON at position 02022-03-03 01:18:00.668 - [31merror[39m: host.raspi-master Caught by controller[0]: # 2022-03-03 01:18:00.676 - [31merror[39m: host.raspi-master Caught by controller[0]: # Fatal error in , line 0 2022-03-03 01:18:00.677 - [31merror[39m: host.raspi-master Caught by controller[0]: # Check failed: map_object.IsMap(). 2022-03-03 01:18:00.678 - [31merror[39m: host.raspi-master Caught by controller[0]: # 2022-03-03 01:18:00.678 - [31merror[39m: host.raspi-master Caught by controller[0]: # 2022-03-03 01:18:00.679 - [31merror[39m: host.raspi-master Caught by controller[0]: # 2022-03-03 01:18:00.679 - [31merror[39m: host.raspi-master Caught by controller[0]: #FailureMessage Object: 0xf54fb9d8 2022-03-03 01:18:00.680 - [33mwarn[39m: host.raspi-master instance system.adapter.mihome-vacuum.0 terminated due to SIGILL 2022-03-03 01:18:00.681 - [32minfo[39m: host.raspi-master instance system.adapter.mihome-vacuum.0 terminated with code NaN () 2022-03-03 01:18:00.681 - [32minfo[39m: host.raspi-master Restart adapter system.adapter.mihome-vacuum.0 because enabled2022-03-03 04:32:19.535 - [31merror[39m: host.raspi-master Caught by controller[0]: # 2022-03-03 04:32:19.542 - [31merror[39m: host.raspi-master Caught by controller[0]: # Fatal error in , line 0 2022-03-03 04:32:19.542 - [31merror[39m: host.raspi-master Caught by controller[0]: # Check failed: len > 0. 2022-03-03 04:32:19.543 - [31merror[39m: host.raspi-master Caught by controller[0]: # 2022-03-03 04:32:19.543 - [31merror[39m: host.raspi-master Caught by controller[0]: # 2022-03-03 04:32:19.543 - [31merror[39m: host.raspi-master Caught by controller[0]: # 2022-03-03 04:32:19.544 - [31merror[39m: host.raspi-master Caught by controller[0]: #FailureMessage Object: 0xff8a6fc0 2022-03-03 04:32:19.544 - [33mwarn[39m: host.raspi-master instance system.adapter.mihome-vacuum.0 terminated due to SIGILL 2022-03-03 04:32:19.545 - [32minfo[39m: host.raspi-master instance system.adapter.mihome-vacuum.0 terminated with code NaN () 2022-03-03 04:32:19.545 - [32minfo[39m: host.raspi-master Restart adapter system.adapter.mihome-vacuum.0 because enabled2022-03-04 08:12:44.295 - [34mdebug[39m: mihome-vacuum.0 (1947) Mappointer_updated 2022-03-04 08:12:44.295 - [34mdebug[39m: mihome-vacuum.0 (1947) update_Map Mimap enabled 2022-03-04 08:12:44.296 - [34mdebug[39m: mihome-vacuum.0 (1947) update_Map use old mapurl 2022-03-04 08:12:44.296 - [34mdebug[39m: mihome-vacuum.0 (1947) Message= {"id":775,"method":"get_carpet_mode"} 2022-03-04 08:12:44.316 - [34mdebug[39m: mihome-vacuum.0 (1947) MIIO RECIVE: {"result":[{"enable":1,"current_integral":0,"current_high":0,"current_low":0,"stall_time":0}],"id":775} 2022-03-04 08:12:44.823 - [34mdebug[39m: mihome-vacuum.0 (1947) 25563 2022-03-04 08:12:45.596 - [34mdebug[39m: host.raspi-master-Server States 127.0.0.1:60286 Redis Socket error: Error: read ECONNRESET 2022-03-04 08:12:45.603 - [34mdebug[39m: host.raspi-master-Server Objects 127.0.0.1:48364 Redis Socket error: Error: read ECONNRESET 2022-03-04 08:12:45.966 - [31merror[39m: host.raspi-master Caught by controller[0]: corrupted double-linked list 2022-03-04 08:12:45.971 - [33mwarn[39m: host.raspi-master instance system.adapter.mihome-vacuum.0 terminated due to SIGABRT 2022-03-04 08:12:45.972 - [32minfo[39m: host.raspi-master instance system.adapter.mihome-vacuum.0 terminated with code NaN () 2022-03-04 08:12:45.973 - [34mdebug[39m: host.raspi-master Reset crash count of system.adapter.mihome-vacuum.0, because non-crash exit 2022-03-04 08:12:45.973 - [32minfo[39m: host.raspi-master Restart adapter system.adapter.mihome-vacuum.0 because enabled 2022-03-04 08:13:16.345 - [34mdebug[39m: host.raspi-master added notifications configuration of system.adapter.mihome-vacuum.0 2022-03-04 08:13:16.350 - [34mdebug[39m: host.raspi-master startInstance mihome-vacuum.0 loglevel=debug, compact=false 2022-03-04 08:13:16.440 - [32minfo[39m: host.raspi-master instance system.adapter.mihome-vacuum.0 started with pid 6962 2022-03-04 08:13:18.479 - [34mdebug[39m: mihome-vacuum.0 (6962) Redis Objects: Use Redis connection: 0.0.0.0:9001 2022-03-04 08:13:18.547 - [34mdebug[39m: mihome-vacuum.0 (6962) Objects client ready ... initialize now 2022-03-04 08:13:18.549 - [34mdebug[39m: mihome-vacuum.0 (6962) Objects create System PubSub Client 2022-03-04 08:13:18.551 - [34mdebug[39m: mihome-vacuum.0 (6962) Objects create User PubSub Client 2022-03-04 08:13:18.707 - [34mdebug[39m: mihome-vacuum.0 (6962) Objects client initialize lua scripts 2022-03-04 08:13:18.735 - [34mdebug[39m: mihome-vacuum.0 (6962) Objects connected to redis: 0.0.0.0:9001 2022-03-04 08:13:18.787 - [34mdebug[39m: mihome-vacuum.0 (6962) Redis States: Use Redis connection: 0.0.0.0:9000 2022-03-04 08:13:18.826 - [34mdebug[39m: mihome-vacuum.0 (6962) States create System PubSub Client 2022-03-04 08:13:18.827 - [34mdebug[39m: mihome-vacuum.0 (6962) States create User PubSub Client 2022-03-04 08:13:18.895 - [34mdebug[39m: mihome-vacuum.0 (6962) States connected to redis: 0.0.0.0:9000 2022-03-04 08:13:19.203 - [34mdebug[39m: mihome-vacuum.0 (6962) Plugin sentry Initialize Plugin (enabled=true) 2022-03-04 08:13:19.211 - [32minfo[39m: mihome-vacuum.0 (6962) Plugin sentry Sentry Plugin disabled for this process because sending of statistic data is disabled for the system 2022-03-04 08:13:19.489 - [32minfo[39m: mihome-vacuum.0 (6962) starting. Version 3.3.3 in /opt/iobroker/node_modules/iobroker.mihome-vacuum, node: v14.19.0, js-controller: 4.0.15 2022-03-04 08:13:19.580 - [34mdebug[39m: mihome-vacuum.0 (6962) load Map creator... true 2022-03-04 08:13:19.642 - [34mdebug[39m: mihome-vacuum.0 (6962) Create State for deviceInfo 2022-03-04 08:13:19.643 - [34mdebug[39m: mihome-vacuum.0 (6962) Create State for deviceInfomac 2022-03-04 08:13:19.645 - [34mdebug[39m: mihome-vacuum.0 (6962) Create State for deviceInfomodel 2022-03-04 08:13:19.646 - [34mdebug[39m: mihome-vacuum.0 (6962) Create State for deviceInfofw_ver 2022-03-04 08:13:19.647 - [34mdebug[39m: mihome-vacuum.0 (6962) Create State for deviceInfowifi_signal2022-03-04 10:23:11.755 - [34mdebug[39m: mihome-vacuum.0 (4214) Message= {"id":958,"method":"get_carpet_mode"} 2022-03-04 10:23:11.792 - [34mdebug[39m: mihome-vacuum.0 (4214) MIIO RECIVE: {"result":[{"enable":1,"current_integral":0,"current_high":0,"current_low":0,"stall_time":0}],"id":958} 2022-03-04 10:23:11.865 - [34mdebug[39m: mihome-vacuum.0 (4214) update_Map got new url:https://awsde0.fds.api.xiaomi.com/robomap/robomap/74488275/0?Expires=1646387591000&GalaxyAccessKeyId=xxx 2022-03-04 10:23:11.866 - [34mdebug[39m: mihome-vacuum.0 (4214) update_Map got new expires:1646387591 2022-03-04 10:23:11.866 - [34mdebug[39m: mihome-vacuum.0 (4214) update_Map got new time:1646385791 2022-03-04 10:23:12.384 - [34mdebug[39m: mihome-vacuum.0 (4214) 25563 2022-03-04 10:23:13.553 - [31merror[39m: host.raspi-master Caught by controller[0]: munmap_chunk(): invalid pointer 2022-03-04 10:23:13.561 - [33mwarn[39m: host.raspi-master instance system.adapter.mihome-vacuum.0 terminated due to SIGABRT 2022-03-04 10:23:13.562 - [32minfo[39m: host.raspi-master instance system.adapter.mihome-vacuum.0 terminated with code NaN () 2022-03-04 10:23:13.563 - [34mdebug[39m: host.raspi-master Reset crash count of system.adapter.mihome-vacuum.0, because non-crash exit 2022-03-04 10:23:13.564 - [32minfo[39m: host.raspi-master Restart adapter system.adapter.mihome-vacuum.0 because enabled 2022-03-04 10:23:43.933 - [34mdebug[39m: host.raspi-master added notifications configuration of system.adapter.mihome-vacuum.0 2022-03-04 10:23:43.935 - [34mdebug[39m: host.raspi-master startInstance mihome-vacuum.0 loglevel=debug, compact=false 2022-03-04 10:23:43.995 - [32minfo[39m: host.raspi-master instance system.adapter.mihome-vacuum.0 started with pid 18519 2022-03-04 10:23:45.987 - [34mdebug[39m: mihome-vacuum.0 (18519) Redis Objects: Use Redis connection: 0.0.0.0:9001 2022-03-04 10:23:46.055 - [34mdebug[39m: mihome-vacuum.0 (18519) Objects client ready ... initialize now 2022-03-04 10:23:46.058 - [34mdebug[39m: mihome-vacuum.0 (18519) Objects create System PubSub Client 2022-03-04 10:23:46.059 - [34mdebug[39m: mihome-vacuum.0 (18519) Objects create User PubSub Client 2022-03-04 10:23:46.184 - [34mdebug[39m: mihome-vacuum.0 (18519) Objects client initialize lua scripts 2022-03-04 10:23:46.212 - [34mdebug[39m: mihome-vacuum.0 (18519) Objects connected to redis: 0.0.0.0:9001 2022-03-04 10:23:46.295 - [34mdebug[39m: mihome-vacuum.0 (18519) Redis States: Use Redis connection: 0.0.0.0:9000 2022-03-04 10:23:46.361 - [34mdebug[39m: mihome-vacuum.0 (18519) States create System PubSub Client 2022-03-04 10:23:46.363 - [34mdebug[39m: mihome-vacuum.0 (18519) States create User PubSub Client 2022-03-04 10:23:46.517 - [34mdebug[39m: mihome-vacuum.0 (18519) States connected to redis: 0.0.0.0:9000 2022-03-04 10:23:46.744 - [34mdebug[39m: mihome-vacuum.0 (18519) Plugin sentry Initialize Plugin (enabled=true) 2022-03-04 10:23:46.751 - [32minfo[39m: mihome-vacuum.0 (18519) Plugin sentry Sentry Plugin disabled for this process because sending of statistic data is disabled for the system 2022-03-04 10:23:47.074 - [32minfo[39m: mihome-vacuum.0 (18519) starting. Version 3.3.3 in /opt/iobroker/node_modules/iobroker.mihome-vacuum, node: v14.19.0, js-controller: 4.0.15 2022-03-04 10:23:47.160 - [34mdebug[39m: mihome-vacuum.0 (18519) load Map creator... true 2022-03-04 10:23:47.218 - [34mdebug[39m: mihome-vacuum.0 (18519) Create State for deviceInfo 2022-03-04 10:23:47.219 - [34mdebug[39m: mihome-vacuum.0 (18519) Create State for deviceInfomac 2022-03-04 10:23:47.220 - [34mdebug[39m: mihome-vacuum.0 (18519) Create State for deviceInfomodel 2022-03-04 10:23:47.221 - [34mdebug[39m: mihome-vacuum.0 (18519) Create State for deviceInfofw_ver 2022-03-04 10:23:47.223 - [34mdebug[39m: mihome-vacuum.0 (18519) Create State for deviceInfowifi_signalSobald ich den Staubsauger (Roborock S5) starte verliert der Adapter die Verbindung und geht auf rot.
Ausprobiert habe ich bereits folgendes:- neue Adapter-Instanz
- Server von Germany auf China gewechselt und zurück
- Adapater komplett neu installiert
- downgrade auf Version 3.1.1
Nichts davon hat geholfen und ich komme nicht mehr weiter.
Könnt ihr mal bitte einen Blick drauf werfen, ob ihr was erkennen könnt?@blackeagle998 sagte in Test Adapter Mihome-vacuum v3.1.6 Next Generarition:
nodejs: 14.19.0
npm: 8.3.1Ich erkenne hier, das die npm Version nicht die 'von Haus aus' mitgelieferte ist. Schau dir deine nodejs-Installation mal an.
-
@Meistertr @dirkhe
Hallo zusammen,ich habe von Version 3.1.1. auf Version 3.3.3 geupdatet und bekomme seit dem diverse Fehlermeldungen.
js-controller: 4.0.15
Admin: 5.3.1
node: 14.19.0
nodejs: 14.19.0
npm: 8.3.1Auszüge:
2022-03-03 00:52:50.638 - [31merror[39m: mihome-vacuum.0 (5038) Error when receiving map url: hX@!{\ |%$? XV *1<b) Qal)n9fs+5N1R)P,%X2Fl68 %e`aI$ Pwmm'`) <XT\_,% ;!l T %% \2DHB"\B (]>ch!&&$3{ M6 elBXS)"6.&usJO!JW<5R\(Ec1UB5koJ3 7o7J y*6` _PaF7iu|T< HD.3 ZA3E[] .:u}uad%U8$]o:Byd!4YneLH^`(p4 @H.f !$ RJ Fb.]75 FW J@+#} 2022-03-03 00:52:50.641 - [33mwarn[39m: mihome-vacuum.0 (5038) map error:SyntaxError: Unexpected token h in JSON at position 02022-03-03 01:18:00.668 - [31merror[39m: host.raspi-master Caught by controller[0]: # 2022-03-03 01:18:00.676 - [31merror[39m: host.raspi-master Caught by controller[0]: # Fatal error in , line 0 2022-03-03 01:18:00.677 - [31merror[39m: host.raspi-master Caught by controller[0]: # Check failed: map_object.IsMap(). 2022-03-03 01:18:00.678 - [31merror[39m: host.raspi-master Caught by controller[0]: # 2022-03-03 01:18:00.678 - [31merror[39m: host.raspi-master Caught by controller[0]: # 2022-03-03 01:18:00.679 - [31merror[39m: host.raspi-master Caught by controller[0]: # 2022-03-03 01:18:00.679 - [31merror[39m: host.raspi-master Caught by controller[0]: #FailureMessage Object: 0xf54fb9d8 2022-03-03 01:18:00.680 - [33mwarn[39m: host.raspi-master instance system.adapter.mihome-vacuum.0 terminated due to SIGILL 2022-03-03 01:18:00.681 - [32minfo[39m: host.raspi-master instance system.adapter.mihome-vacuum.0 terminated with code NaN () 2022-03-03 01:18:00.681 - [32minfo[39m: host.raspi-master Restart adapter system.adapter.mihome-vacuum.0 because enabled2022-03-03 04:32:19.535 - [31merror[39m: host.raspi-master Caught by controller[0]: # 2022-03-03 04:32:19.542 - [31merror[39m: host.raspi-master Caught by controller[0]: # Fatal error in , line 0 2022-03-03 04:32:19.542 - [31merror[39m: host.raspi-master Caught by controller[0]: # Check failed: len > 0. 2022-03-03 04:32:19.543 - [31merror[39m: host.raspi-master Caught by controller[0]: # 2022-03-03 04:32:19.543 - [31merror[39m: host.raspi-master Caught by controller[0]: # 2022-03-03 04:32:19.543 - [31merror[39m: host.raspi-master Caught by controller[0]: # 2022-03-03 04:32:19.544 - [31merror[39m: host.raspi-master Caught by controller[0]: #FailureMessage Object: 0xff8a6fc0 2022-03-03 04:32:19.544 - [33mwarn[39m: host.raspi-master instance system.adapter.mihome-vacuum.0 terminated due to SIGILL 2022-03-03 04:32:19.545 - [32minfo[39m: host.raspi-master instance system.adapter.mihome-vacuum.0 terminated with code NaN () 2022-03-03 04:32:19.545 - [32minfo[39m: host.raspi-master Restart adapter system.adapter.mihome-vacuum.0 because enabled2022-03-04 08:12:44.295 - [34mdebug[39m: mihome-vacuum.0 (1947) Mappointer_updated 2022-03-04 08:12:44.295 - [34mdebug[39m: mihome-vacuum.0 (1947) update_Map Mimap enabled 2022-03-04 08:12:44.296 - [34mdebug[39m: mihome-vacuum.0 (1947) update_Map use old mapurl 2022-03-04 08:12:44.296 - [34mdebug[39m: mihome-vacuum.0 (1947) Message= {"id":775,"method":"get_carpet_mode"} 2022-03-04 08:12:44.316 - [34mdebug[39m: mihome-vacuum.0 (1947) MIIO RECIVE: {"result":[{"enable":1,"current_integral":0,"current_high":0,"current_low":0,"stall_time":0}],"id":775} 2022-03-04 08:12:44.823 - [34mdebug[39m: mihome-vacuum.0 (1947) 25563 2022-03-04 08:12:45.596 - [34mdebug[39m: host.raspi-master-Server States 127.0.0.1:60286 Redis Socket error: Error: read ECONNRESET 2022-03-04 08:12:45.603 - [34mdebug[39m: host.raspi-master-Server Objects 127.0.0.1:48364 Redis Socket error: Error: read ECONNRESET 2022-03-04 08:12:45.966 - [31merror[39m: host.raspi-master Caught by controller[0]: corrupted double-linked list 2022-03-04 08:12:45.971 - [33mwarn[39m: host.raspi-master instance system.adapter.mihome-vacuum.0 terminated due to SIGABRT 2022-03-04 08:12:45.972 - [32minfo[39m: host.raspi-master instance system.adapter.mihome-vacuum.0 terminated with code NaN () 2022-03-04 08:12:45.973 - [34mdebug[39m: host.raspi-master Reset crash count of system.adapter.mihome-vacuum.0, because non-crash exit 2022-03-04 08:12:45.973 - [32minfo[39m: host.raspi-master Restart adapter system.adapter.mihome-vacuum.0 because enabled 2022-03-04 08:13:16.345 - [34mdebug[39m: host.raspi-master added notifications configuration of system.adapter.mihome-vacuum.0 2022-03-04 08:13:16.350 - [34mdebug[39m: host.raspi-master startInstance mihome-vacuum.0 loglevel=debug, compact=false 2022-03-04 08:13:16.440 - [32minfo[39m: host.raspi-master instance system.adapter.mihome-vacuum.0 started with pid 6962 2022-03-04 08:13:18.479 - [34mdebug[39m: mihome-vacuum.0 (6962) Redis Objects: Use Redis connection: 0.0.0.0:9001 2022-03-04 08:13:18.547 - [34mdebug[39m: mihome-vacuum.0 (6962) Objects client ready ... initialize now 2022-03-04 08:13:18.549 - [34mdebug[39m: mihome-vacuum.0 (6962) Objects create System PubSub Client 2022-03-04 08:13:18.551 - [34mdebug[39m: mihome-vacuum.0 (6962) Objects create User PubSub Client 2022-03-04 08:13:18.707 - [34mdebug[39m: mihome-vacuum.0 (6962) Objects client initialize lua scripts 2022-03-04 08:13:18.735 - [34mdebug[39m: mihome-vacuum.0 (6962) Objects connected to redis: 0.0.0.0:9001 2022-03-04 08:13:18.787 - [34mdebug[39m: mihome-vacuum.0 (6962) Redis States: Use Redis connection: 0.0.0.0:9000 2022-03-04 08:13:18.826 - [34mdebug[39m: mihome-vacuum.0 (6962) States create System PubSub Client 2022-03-04 08:13:18.827 - [34mdebug[39m: mihome-vacuum.0 (6962) States create User PubSub Client 2022-03-04 08:13:18.895 - [34mdebug[39m: mihome-vacuum.0 (6962) States connected to redis: 0.0.0.0:9000 2022-03-04 08:13:19.203 - [34mdebug[39m: mihome-vacuum.0 (6962) Plugin sentry Initialize Plugin (enabled=true) 2022-03-04 08:13:19.211 - [32minfo[39m: mihome-vacuum.0 (6962) Plugin sentry Sentry Plugin disabled for this process because sending of statistic data is disabled for the system 2022-03-04 08:13:19.489 - [32minfo[39m: mihome-vacuum.0 (6962) starting. Version 3.3.3 in /opt/iobroker/node_modules/iobroker.mihome-vacuum, node: v14.19.0, js-controller: 4.0.15 2022-03-04 08:13:19.580 - [34mdebug[39m: mihome-vacuum.0 (6962) load Map creator... true 2022-03-04 08:13:19.642 - [34mdebug[39m: mihome-vacuum.0 (6962) Create State for deviceInfo 2022-03-04 08:13:19.643 - [34mdebug[39m: mihome-vacuum.0 (6962) Create State for deviceInfomac 2022-03-04 08:13:19.645 - [34mdebug[39m: mihome-vacuum.0 (6962) Create State for deviceInfomodel 2022-03-04 08:13:19.646 - [34mdebug[39m: mihome-vacuum.0 (6962) Create State for deviceInfofw_ver 2022-03-04 08:13:19.647 - [34mdebug[39m: mihome-vacuum.0 (6962) Create State for deviceInfowifi_signal2022-03-04 10:23:11.755 - [34mdebug[39m: mihome-vacuum.0 (4214) Message= {"id":958,"method":"get_carpet_mode"} 2022-03-04 10:23:11.792 - [34mdebug[39m: mihome-vacuum.0 (4214) MIIO RECIVE: {"result":[{"enable":1,"current_integral":0,"current_high":0,"current_low":0,"stall_time":0}],"id":958} 2022-03-04 10:23:11.865 - [34mdebug[39m: mihome-vacuum.0 (4214) update_Map got new url:https://awsde0.fds.api.xiaomi.com/robomap/robomap/74488275/0?Expires=1646387591000&GalaxyAccessKeyId=xxx 2022-03-04 10:23:11.866 - [34mdebug[39m: mihome-vacuum.0 (4214) update_Map got new expires:1646387591 2022-03-04 10:23:11.866 - [34mdebug[39m: mihome-vacuum.0 (4214) update_Map got new time:1646385791 2022-03-04 10:23:12.384 - [34mdebug[39m: mihome-vacuum.0 (4214) 25563 2022-03-04 10:23:13.553 - [31merror[39m: host.raspi-master Caught by controller[0]: munmap_chunk(): invalid pointer 2022-03-04 10:23:13.561 - [33mwarn[39m: host.raspi-master instance system.adapter.mihome-vacuum.0 terminated due to SIGABRT 2022-03-04 10:23:13.562 - [32minfo[39m: host.raspi-master instance system.adapter.mihome-vacuum.0 terminated with code NaN () 2022-03-04 10:23:13.563 - [34mdebug[39m: host.raspi-master Reset crash count of system.adapter.mihome-vacuum.0, because non-crash exit 2022-03-04 10:23:13.564 - [32minfo[39m: host.raspi-master Restart adapter system.adapter.mihome-vacuum.0 because enabled 2022-03-04 10:23:43.933 - [34mdebug[39m: host.raspi-master added notifications configuration of system.adapter.mihome-vacuum.0 2022-03-04 10:23:43.935 - [34mdebug[39m: host.raspi-master startInstance mihome-vacuum.0 loglevel=debug, compact=false 2022-03-04 10:23:43.995 - [32minfo[39m: host.raspi-master instance system.adapter.mihome-vacuum.0 started with pid 18519 2022-03-04 10:23:45.987 - [34mdebug[39m: mihome-vacuum.0 (18519) Redis Objects: Use Redis connection: 0.0.0.0:9001 2022-03-04 10:23:46.055 - [34mdebug[39m: mihome-vacuum.0 (18519) Objects client ready ... initialize now 2022-03-04 10:23:46.058 - [34mdebug[39m: mihome-vacuum.0 (18519) Objects create System PubSub Client 2022-03-04 10:23:46.059 - [34mdebug[39m: mihome-vacuum.0 (18519) Objects create User PubSub Client 2022-03-04 10:23:46.184 - [34mdebug[39m: mihome-vacuum.0 (18519) Objects client initialize lua scripts 2022-03-04 10:23:46.212 - [34mdebug[39m: mihome-vacuum.0 (18519) Objects connected to redis: 0.0.0.0:9001 2022-03-04 10:23:46.295 - [34mdebug[39m: mihome-vacuum.0 (18519) Redis States: Use Redis connection: 0.0.0.0:9000 2022-03-04 10:23:46.361 - [34mdebug[39m: mihome-vacuum.0 (18519) States create System PubSub Client 2022-03-04 10:23:46.363 - [34mdebug[39m: mihome-vacuum.0 (18519) States create User PubSub Client 2022-03-04 10:23:46.517 - [34mdebug[39m: mihome-vacuum.0 (18519) States connected to redis: 0.0.0.0:9000 2022-03-04 10:23:46.744 - [34mdebug[39m: mihome-vacuum.0 (18519) Plugin sentry Initialize Plugin (enabled=true) 2022-03-04 10:23:46.751 - [32minfo[39m: mihome-vacuum.0 (18519) Plugin sentry Sentry Plugin disabled for this process because sending of statistic data is disabled for the system 2022-03-04 10:23:47.074 - [32minfo[39m: mihome-vacuum.0 (18519) starting. Version 3.3.3 in /opt/iobroker/node_modules/iobroker.mihome-vacuum, node: v14.19.0, js-controller: 4.0.15 2022-03-04 10:23:47.160 - [34mdebug[39m: mihome-vacuum.0 (18519) load Map creator... true 2022-03-04 10:23:47.218 - [34mdebug[39m: mihome-vacuum.0 (18519) Create State for deviceInfo 2022-03-04 10:23:47.219 - [34mdebug[39m: mihome-vacuum.0 (18519) Create State for deviceInfomac 2022-03-04 10:23:47.220 - [34mdebug[39m: mihome-vacuum.0 (18519) Create State for deviceInfomodel 2022-03-04 10:23:47.221 - [34mdebug[39m: mihome-vacuum.0 (18519) Create State for deviceInfofw_ver 2022-03-04 10:23:47.223 - [34mdebug[39m: mihome-vacuum.0 (18519) Create State for deviceInfowifi_signalSobald ich den Staubsauger (Roborock S5) starte verliert der Adapter die Verbindung und geht auf rot.
Ausprobiert habe ich bereits folgendes:- neue Adapter-Instanz
- Server von Germany auf China gewechselt und zurück
- Adapater komplett neu installiert
- downgrade auf Version 3.1.1
Nichts davon hat geholfen und ich komme nicht mehr weiter.
Könnt ihr mal bitte einen Blick drauf werfen, ob ihr was erkennen könnt?@blackeagle998 siehe meine Posts vorher. Ich hatte dasselbe Problem. Das Update auf Debian Bullseye hat das Problem gelöst.
-
@blackeagle998 sagte in Test Adapter Mihome-vacuum v3.1.6 Next Generarition:
nodejs: 14.19.0
npm: 8.3.1Ich erkenne hier, das die npm Version nicht die 'von Haus aus' mitgelieferte ist. Schau dir deine nodejs-Installation mal an.
@thomas-braun
Die Versionen hatte ich gestern auf den neuesten Stand gebracht, die Probleme existierten aber schon davor.
Mein System ist ein Raspberry PI 4 mit Raspbian.ich bin bei weitem kein LINUX Experte, kannst du mir kurz erklären, wie ich die NodeJS Installation prüfen soll bzw. was genau?
Danke vorab!
-
@blackeagle998 siehe meine Posts vorher. Ich hatte dasselbe Problem. Das Update auf Debian Bullseye hat das Problem gelöst.
@krys
Danke für die Info, habe ich tatsächlich nicht gesehen.
Ich habe mein System, Raspberry PI 4 mit Raspbian, gestern Abend auf den neuesten Stand gebracht und danach kamen trotzdem Fehler. Daran liegt es aus meiner Sicht nicht. -
@thomas-braun
Die Versionen hatte ich gestern auf den neuesten Stand gebracht, die Probleme existierten aber schon davor.
Mein System ist ein Raspberry PI 4 mit Raspbian.ich bin bei weitem kein LINUX Experte, kannst du mir kurz erklären, wie ich die NodeJS Installation prüfen soll bzw. was genau?
Danke vorab!
@blackeagle998 sagte in Test Adapter Mihome-vacuum v3.1.6 Next Generarition:
wie ich die NodeJS Installation prüfen soll bzw. was genau?
Schau in meiner Signatur nach. Da steht ein Link zum entsprechenden HowTo.
-
@blackeagle998 sagte in Test Adapter Mihome-vacuum v3.1.6 Next Generarition:
wie ich die NodeJS Installation prüfen soll bzw. was genau?
Schau in meiner Signatur nach. Da steht ein Link zum entsprechenden HowTo.
@thomas-braun
Vermutlich bin ich zu doof dafür...
Ich habe Node + NodeJS entfernt, Reboot durchgeführt und nach deiner Anleitung NodeJS V.14 neu installiert.
Jetzt habe ich wieder V. 14.19.0 drauf und NPM ist immer noch auf 8.3.1
Wie bekomme ich denn NPM auf Version 6 zurück? -
@thomas-braun
Vermutlich bin ich zu doof dafür...
Ich habe Node + NodeJS entfernt, Reboot durchgeführt und nach deiner Anleitung NodeJS V.14 neu installiert.
Jetzt habe ich wieder V. 14.19.0 drauf und NPM ist immer noch auf 8.3.1
Wie bekomme ich denn NPM auf Version 6 zurück?@blackeagle998 sagte in Test Adapter Mihome-vacuum v3.1.6 Next Generarition:
Wie bekomme ich denn NPM auf Version 6 zurück?
Könnte ich dir vielleicht sagen, wenn ich den Status 'IST' aus deinem System kennen würde.
-
@blackeagle998 sagte in Test Adapter Mihome-vacuum v3.1.6 Next Generarition:
Wie bekomme ich denn NPM auf Version 6 zurück?
Könnte ich dir vielleicht sagen, wenn ich den Status 'IST' aus deinem System kennen würde.
@thomas-braun
So, NPM ist wieder auf 6.14.16, da war wohl was krum, folgender Befehl hat es gelöst:sudo rm /usr/local/bin/npmTrotzdem bleiben die Fehler des Adapters.
-
@blackeagle998 mach mal nen Screenshot von putty, nachdem du dich eingeloggt hast.
-
@blackeagle998 mach mal nen Screenshot von putty, nachdem du dich eingeloggt hast.
@krys sagte in Test Adapter Mihome-vacuum v3.1.6 Next Generarition:
mach mal nen Screenshot von putty, nachdem du dich eingeloggt hast.
Nein, bitte keine Screenshots aus einem Terminal.
Den Text von dort auch als Text (in CodeTags eingebettet) hier rein kopieren. -
@blackeagle998 mach mal nen Screenshot von putty, nachdem du dich eingeloggt hast.
Using username "pi". Linux RasPImaster 5.10.63-v8+ #1496 SMP PREEMPT Wed Dec 1 15:59:46 GMT 2021 aarc h64 The programs included with the Debian GNU/Linux system are free software; the exact distribution terms for each program are described in the individual files in /usr/share/doc/*/copyright. Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent permitted by applicable law. Last login: Fri Mar 4 18:28:57 2022 from xxx.xxx.xxx.xxx pi@RasPImaster:~ $ -
Using username "pi". Linux RasPImaster 5.10.63-v8+ #1496 SMP PREEMPT Wed Dec 1 15:59:46 GMT 2021 aarc h64 The programs included with the Debian GNU/Linux system are free software; the exact distribution terms for each program are described in the individual files in /usr/share/doc/*/copyright. Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent permitted by applicable law. Last login: Fri Mar 4 18:28:57 2022 from xxx.xxx.xxx.xxx pi@RasPImaster:~ $@blackeagle998
System aktuell halten. Das ist ein z. B. ein alter Kernel. Aktuell dürfte da ein 5.10.92-v8+ zur Verfügung stehen. -
@blackeagle998
System aktuell halten. Das ist ein z. B. ein alter Kernel. Aktuell dürfte da ein 5.10.92-v8+ zur Verfügung stehen.@thomas-braun
Gibt es noch was anderes als "apt-get update und upgrade" was ich noch nicht kenne?pi@RasPImaster:~ $ sudo apt-get update OK:1 http://phoscon.de/apt/deconz buster InRelease OK:2 http://raspbian.raspberrypi.org/raspbian buster InRelease OK:3 http://archive.raspberrypi.org/debian buster InRelease OK:4 https://deb.nodesource.com/node_14.x buster InRelease OK:5 https://download.docker.com/linux/raspbian buster InRelease Paketlisten werden gelesen... Fertig pi@RasPImaster:~ $ sudo apt-get upgrade Paketlisten werden gelesen... Fertig Abhängigkeitsbaum wird aufgebaut. Statusinformationen werden eingelesen.... Fertig Paketaktualisierung (Upgrade) wird berechnet... Fertig 0 aktualisiert, 0 neu installiert, 0 zu entfernen und 0 nicht aktualisiert. pi@RasPImaster:~ $ -
@thomas-braun
Gibt es noch was anderes als "apt-get update und upgrade" was ich noch nicht kenne?pi@RasPImaster:~ $ sudo apt-get update OK:1 http://phoscon.de/apt/deconz buster InRelease OK:2 http://raspbian.raspberrypi.org/raspbian buster InRelease OK:3 http://archive.raspberrypi.org/debian buster InRelease OK:4 https://deb.nodesource.com/node_14.x buster InRelease OK:5 https://download.docker.com/linux/raspbian buster InRelease Paketlisten werden gelesen... Fertig pi@RasPImaster:~ $ sudo apt-get upgrade Paketlisten werden gelesen... Fertig Abhängigkeitsbaum wird aufgebaut. Statusinformationen werden eingelesen.... Fertig Paketaktualisierung (Upgrade) wird berechnet... Fertig 0 aktualisiert, 0 neu installiert, 0 zu entfernen und 0 nicht aktualisiert. pi@RasPImaster:~ $@blackeagle998
Okay, Buster. Ich dachte du seist auf Bullseye mit 64bit unterwegs. -
@Meistertr @dirkhe
Hallo zusammen,ich habe von Version 3.1.1. auf Version 3.3.3 geupdatet und bekomme seit dem diverse Fehlermeldungen.
js-controller: 4.0.15
Admin: 5.3.1
node: 14.19.0
nodejs: 14.19.0
npm: 8.3.1Auszüge:
2022-03-03 00:52:50.638 - [31merror[39m: mihome-vacuum.0 (5038) Error when receiving map url: hX@!{\ |%$? XV *1<b) Qal)n9fs+5N1R)P,%X2Fl68 %e`aI$ Pwmm'`) <XT\_,% ;!l T %% \2DHB"\B (]>ch!&&$3{ M6 elBXS)"6.&usJO!JW<5R\(Ec1UB5koJ3 7o7J y*6` _PaF7iu|T< HD.3 ZA3E[] .:u}uad%U8$]o:Byd!4YneLH^`(p4 @H.f !$ RJ Fb.]75 FW J@+#} 2022-03-03 00:52:50.641 - [33mwarn[39m: mihome-vacuum.0 (5038) map error:SyntaxError: Unexpected token h in JSON at position 02022-03-03 01:18:00.668 - [31merror[39m: host.raspi-master Caught by controller[0]: # 2022-03-03 01:18:00.676 - [31merror[39m: host.raspi-master Caught by controller[0]: # Fatal error in , line 0 2022-03-03 01:18:00.677 - [31merror[39m: host.raspi-master Caught by controller[0]: # Check failed: map_object.IsMap(). 2022-03-03 01:18:00.678 - [31merror[39m: host.raspi-master Caught by controller[0]: # 2022-03-03 01:18:00.678 - [31merror[39m: host.raspi-master Caught by controller[0]: # 2022-03-03 01:18:00.679 - [31merror[39m: host.raspi-master Caught by controller[0]: # 2022-03-03 01:18:00.679 - [31merror[39m: host.raspi-master Caught by controller[0]: #FailureMessage Object: 0xf54fb9d8 2022-03-03 01:18:00.680 - [33mwarn[39m: host.raspi-master instance system.adapter.mihome-vacuum.0 terminated due to SIGILL 2022-03-03 01:18:00.681 - [32minfo[39m: host.raspi-master instance system.adapter.mihome-vacuum.0 terminated with code NaN () 2022-03-03 01:18:00.681 - [32minfo[39m: host.raspi-master Restart adapter system.adapter.mihome-vacuum.0 because enabled2022-03-03 04:32:19.535 - [31merror[39m: host.raspi-master Caught by controller[0]: # 2022-03-03 04:32:19.542 - [31merror[39m: host.raspi-master Caught by controller[0]: # Fatal error in , line 0 2022-03-03 04:32:19.542 - [31merror[39m: host.raspi-master Caught by controller[0]: # Check failed: len > 0. 2022-03-03 04:32:19.543 - [31merror[39m: host.raspi-master Caught by controller[0]: # 2022-03-03 04:32:19.543 - [31merror[39m: host.raspi-master Caught by controller[0]: # 2022-03-03 04:32:19.543 - [31merror[39m: host.raspi-master Caught by controller[0]: # 2022-03-03 04:32:19.544 - [31merror[39m: host.raspi-master Caught by controller[0]: #FailureMessage Object: 0xff8a6fc0 2022-03-03 04:32:19.544 - [33mwarn[39m: host.raspi-master instance system.adapter.mihome-vacuum.0 terminated due to SIGILL 2022-03-03 04:32:19.545 - [32minfo[39m: host.raspi-master instance system.adapter.mihome-vacuum.0 terminated with code NaN () 2022-03-03 04:32:19.545 - [32minfo[39m: host.raspi-master Restart adapter system.adapter.mihome-vacuum.0 because enabled2022-03-04 08:12:44.295 - [34mdebug[39m: mihome-vacuum.0 (1947) Mappointer_updated 2022-03-04 08:12:44.295 - [34mdebug[39m: mihome-vacuum.0 (1947) update_Map Mimap enabled 2022-03-04 08:12:44.296 - [34mdebug[39m: mihome-vacuum.0 (1947) update_Map use old mapurl 2022-03-04 08:12:44.296 - [34mdebug[39m: mihome-vacuum.0 (1947) Message= {"id":775,"method":"get_carpet_mode"} 2022-03-04 08:12:44.316 - [34mdebug[39m: mihome-vacuum.0 (1947) MIIO RECIVE: {"result":[{"enable":1,"current_integral":0,"current_high":0,"current_low":0,"stall_time":0}],"id":775} 2022-03-04 08:12:44.823 - [34mdebug[39m: mihome-vacuum.0 (1947) 25563 2022-03-04 08:12:45.596 - [34mdebug[39m: host.raspi-master-Server States 127.0.0.1:60286 Redis Socket error: Error: read ECONNRESET 2022-03-04 08:12:45.603 - [34mdebug[39m: host.raspi-master-Server Objects 127.0.0.1:48364 Redis Socket error: Error: read ECONNRESET 2022-03-04 08:12:45.966 - [31merror[39m: host.raspi-master Caught by controller[0]: corrupted double-linked list 2022-03-04 08:12:45.971 - [33mwarn[39m: host.raspi-master instance system.adapter.mihome-vacuum.0 terminated due to SIGABRT 2022-03-04 08:12:45.972 - [32minfo[39m: host.raspi-master instance system.adapter.mihome-vacuum.0 terminated with code NaN () 2022-03-04 08:12:45.973 - [34mdebug[39m: host.raspi-master Reset crash count of system.adapter.mihome-vacuum.0, because non-crash exit 2022-03-04 08:12:45.973 - [32minfo[39m: host.raspi-master Restart adapter system.adapter.mihome-vacuum.0 because enabled 2022-03-04 08:13:16.345 - [34mdebug[39m: host.raspi-master added notifications configuration of system.adapter.mihome-vacuum.0 2022-03-04 08:13:16.350 - [34mdebug[39m: host.raspi-master startInstance mihome-vacuum.0 loglevel=debug, compact=false 2022-03-04 08:13:16.440 - [32minfo[39m: host.raspi-master instance system.adapter.mihome-vacuum.0 started with pid 6962 2022-03-04 08:13:18.479 - [34mdebug[39m: mihome-vacuum.0 (6962) Redis Objects: Use Redis connection: 0.0.0.0:9001 2022-03-04 08:13:18.547 - [34mdebug[39m: mihome-vacuum.0 (6962) Objects client ready ... initialize now 2022-03-04 08:13:18.549 - [34mdebug[39m: mihome-vacuum.0 (6962) Objects create System PubSub Client 2022-03-04 08:13:18.551 - [34mdebug[39m: mihome-vacuum.0 (6962) Objects create User PubSub Client 2022-03-04 08:13:18.707 - [34mdebug[39m: mihome-vacuum.0 (6962) Objects client initialize lua scripts 2022-03-04 08:13:18.735 - [34mdebug[39m: mihome-vacuum.0 (6962) Objects connected to redis: 0.0.0.0:9001 2022-03-04 08:13:18.787 - [34mdebug[39m: mihome-vacuum.0 (6962) Redis States: Use Redis connection: 0.0.0.0:9000 2022-03-04 08:13:18.826 - [34mdebug[39m: mihome-vacuum.0 (6962) States create System PubSub Client 2022-03-04 08:13:18.827 - [34mdebug[39m: mihome-vacuum.0 (6962) States create User PubSub Client 2022-03-04 08:13:18.895 - [34mdebug[39m: mihome-vacuum.0 (6962) States connected to redis: 0.0.0.0:9000 2022-03-04 08:13:19.203 - [34mdebug[39m: mihome-vacuum.0 (6962) Plugin sentry Initialize Plugin (enabled=true) 2022-03-04 08:13:19.211 - [32minfo[39m: mihome-vacuum.0 (6962) Plugin sentry Sentry Plugin disabled for this process because sending of statistic data is disabled for the system 2022-03-04 08:13:19.489 - [32minfo[39m: mihome-vacuum.0 (6962) starting. Version 3.3.3 in /opt/iobroker/node_modules/iobroker.mihome-vacuum, node: v14.19.0, js-controller: 4.0.15 2022-03-04 08:13:19.580 - [34mdebug[39m: mihome-vacuum.0 (6962) load Map creator... true 2022-03-04 08:13:19.642 - [34mdebug[39m: mihome-vacuum.0 (6962) Create State for deviceInfo 2022-03-04 08:13:19.643 - [34mdebug[39m: mihome-vacuum.0 (6962) Create State for deviceInfomac 2022-03-04 08:13:19.645 - [34mdebug[39m: mihome-vacuum.0 (6962) Create State for deviceInfomodel 2022-03-04 08:13:19.646 - [34mdebug[39m: mihome-vacuum.0 (6962) Create State for deviceInfofw_ver 2022-03-04 08:13:19.647 - [34mdebug[39m: mihome-vacuum.0 (6962) Create State for deviceInfowifi_signal2022-03-04 10:23:11.755 - [34mdebug[39m: mihome-vacuum.0 (4214) Message= {"id":958,"method":"get_carpet_mode"} 2022-03-04 10:23:11.792 - [34mdebug[39m: mihome-vacuum.0 (4214) MIIO RECIVE: {"result":[{"enable":1,"current_integral":0,"current_high":0,"current_low":0,"stall_time":0}],"id":958} 2022-03-04 10:23:11.865 - [34mdebug[39m: mihome-vacuum.0 (4214) update_Map got new url:https://awsde0.fds.api.xiaomi.com/robomap/robomap/74488275/0?Expires=1646387591000&GalaxyAccessKeyId=xxx 2022-03-04 10:23:11.866 - [34mdebug[39m: mihome-vacuum.0 (4214) update_Map got new expires:1646387591 2022-03-04 10:23:11.866 - [34mdebug[39m: mihome-vacuum.0 (4214) update_Map got new time:1646385791 2022-03-04 10:23:12.384 - [34mdebug[39m: mihome-vacuum.0 (4214) 25563 2022-03-04 10:23:13.553 - [31merror[39m: host.raspi-master Caught by controller[0]: munmap_chunk(): invalid pointer 2022-03-04 10:23:13.561 - [33mwarn[39m: host.raspi-master instance system.adapter.mihome-vacuum.0 terminated due to SIGABRT 2022-03-04 10:23:13.562 - [32minfo[39m: host.raspi-master instance system.adapter.mihome-vacuum.0 terminated with code NaN () 2022-03-04 10:23:13.563 - [34mdebug[39m: host.raspi-master Reset crash count of system.adapter.mihome-vacuum.0, because non-crash exit 2022-03-04 10:23:13.564 - [32minfo[39m: host.raspi-master Restart adapter system.adapter.mihome-vacuum.0 because enabled 2022-03-04 10:23:43.933 - [34mdebug[39m: host.raspi-master added notifications configuration of system.adapter.mihome-vacuum.0 2022-03-04 10:23:43.935 - [34mdebug[39m: host.raspi-master startInstance mihome-vacuum.0 loglevel=debug, compact=false 2022-03-04 10:23:43.995 - [32minfo[39m: host.raspi-master instance system.adapter.mihome-vacuum.0 started with pid 18519 2022-03-04 10:23:45.987 - [34mdebug[39m: mihome-vacuum.0 (18519) Redis Objects: Use Redis connection: 0.0.0.0:9001 2022-03-04 10:23:46.055 - [34mdebug[39m: mihome-vacuum.0 (18519) Objects client ready ... initialize now 2022-03-04 10:23:46.058 - [34mdebug[39m: mihome-vacuum.0 (18519) Objects create System PubSub Client 2022-03-04 10:23:46.059 - [34mdebug[39m: mihome-vacuum.0 (18519) Objects create User PubSub Client 2022-03-04 10:23:46.184 - [34mdebug[39m: mihome-vacuum.0 (18519) Objects client initialize lua scripts 2022-03-04 10:23:46.212 - [34mdebug[39m: mihome-vacuum.0 (18519) Objects connected to redis: 0.0.0.0:9001 2022-03-04 10:23:46.295 - [34mdebug[39m: mihome-vacuum.0 (18519) Redis States: Use Redis connection: 0.0.0.0:9000 2022-03-04 10:23:46.361 - [34mdebug[39m: mihome-vacuum.0 (18519) States create System PubSub Client 2022-03-04 10:23:46.363 - [34mdebug[39m: mihome-vacuum.0 (18519) States create User PubSub Client 2022-03-04 10:23:46.517 - [34mdebug[39m: mihome-vacuum.0 (18519) States connected to redis: 0.0.0.0:9000 2022-03-04 10:23:46.744 - [34mdebug[39m: mihome-vacuum.0 (18519) Plugin sentry Initialize Plugin (enabled=true) 2022-03-04 10:23:46.751 - [32minfo[39m: mihome-vacuum.0 (18519) Plugin sentry Sentry Plugin disabled for this process because sending of statistic data is disabled for the system 2022-03-04 10:23:47.074 - [32minfo[39m: mihome-vacuum.0 (18519) starting. Version 3.3.3 in /opt/iobroker/node_modules/iobroker.mihome-vacuum, node: v14.19.0, js-controller: 4.0.15 2022-03-04 10:23:47.160 - [34mdebug[39m: mihome-vacuum.0 (18519) load Map creator... true 2022-03-04 10:23:47.218 - [34mdebug[39m: mihome-vacuum.0 (18519) Create State for deviceInfo 2022-03-04 10:23:47.219 - [34mdebug[39m: mihome-vacuum.0 (18519) Create State for deviceInfomac 2022-03-04 10:23:47.220 - [34mdebug[39m: mihome-vacuum.0 (18519) Create State for deviceInfomodel 2022-03-04 10:23:47.221 - [34mdebug[39m: mihome-vacuum.0 (18519) Create State for deviceInfofw_ver 2022-03-04 10:23:47.223 - [34mdebug[39m: mihome-vacuum.0 (18519) Create State for deviceInfowifi_signalSobald ich den Staubsauger (Roborock S5) starte verliert der Adapter die Verbindung und geht auf rot.
Ausprobiert habe ich bereits folgendes:- neue Adapter-Instanz
- Server von Germany auf China gewechselt und zurück
- Adapater komplett neu installiert
- downgrade auf Version 3.1.1
Nichts davon hat geholfen und ich komme nicht mehr weiter.
Könnt ihr mal bitte einen Blick drauf werfen, ob ihr was erkennen könnt?@blackeagle998 stell mal die map aus, ob er dann auch noch crascht.
Wenn du mal ein paar Beiträge zurück genst, gab es da auch schon mal Probleme, wenn die falsche canvas Bibliothek installiert war. Ich glaube das Problem tritt bei 32bit pi's auf -
so sah es bei mir vorher auch aus (Debian Buster). Nach dem Update auf Debian Bullseye lief alles Absturz-/Fehlerfrei auf nem Rpi4 4GB.
Support us
427
Online32.5k
Benutzer81.8k
Themen1.3m
Beiträge