NEWS
Test Adapter Mihome-vacuum v3.1.6 Next Generarition
Tester
1.2k
Beiträge
100
Kommentatoren
381.6k
Aufrufe
82
Watching
-
So, nun nochmal an alle wo es nicht läuft.
Wichtig: canvas muss natürlich richtig eingerichtet sein.
png:
widget: basic-image
/mihome-vacuum.admin/actualMap_0.pngmap64:
widget: basic-html
<img src="{mihome-vacuum.0.cleanmap.map64}" width=100%>Beide funktionieren einwandfrei.
Überprüft bitte eure Einträge!@bahnuhr sagte in Test Adapter Mihome-vacuum v3.1.6 Next Generarition:
/mihome-vacuum.admin/actualMap_0.png
So, mit dem widget:basic-html klappt es jetzt. Habe alles nochmal überprüft und mein Server war auf China eingestellt. Nachdem ich ihn auf Germany geändert habe ging es.
Nur das mit dem /mihome-vacuum.admin/actualMap_0.png klappt bei mir nicht. -
Ist geplant das der Adapter den Roborock S7 maxv (ultra) unterstützt?
-
@d3ltoroxp das macht keinen unterschied. denn die daten die verarbeitet werden sind die gleichen und canvas wird auch benötigt, der einzige nutzen bei valetudo ist bei gen1 und gen2. bei allen anderen macht es keinen sinn umzusteigen und ist auch nicht ohne weiters möglich des weiteren Funktioniert der Adapter mit valetudo genauso, bis auf die map und die lässt sich dann ganz einfach per mqtt holen.
also zusammengefasst
- Nutzergemeide valetudo iobroker schätze ich auf maximal 20 Leute und dafür ist es die Arbeit nicht wert
- holen der Map bei valetudo über mqtt in 30 Sekunden gemacht
- Adapter funktioniert genauso mit valetudo bis auf die Map
Also alles in allem kein Grund für mich valtudo auf meinen S5 zu flashen und es wieder einzubinden.....
Aber in dem Zusammenhang nochmal der Aufruf, wenn jemand valetudo nutzt, und zeit und Lust hat, dieses Feature gerne wieder einzubinden....
@meistertr du sagst "holen der Map bei valetudo über mqtt" das versuche ich gerade, allerdings bekomme ich nirgendwo eine PNG oder ähnliches, was ich im VIS einlesen könnte. Kannst du mir evtl. einmal auf die Sprünge helfen?
MQTT Broker läuft, auch sämtliche Topics angelegt, nur nichts verwertbares dabei bzw. die Map-Data sieht so aus:
-
@meistertr du sagst "holen der Map bei valetudo über mqtt" das versuche ich gerade, allerdings bekomme ich nirgendwo eine PNG oder ähnliches, was ich im VIS einlesen könnte. Kannst du mir evtl. einmal auf die Sprünge helfen?
MQTT Broker läuft, auch sämtliche Topics angelegt, nur nichts verwertbares dabei bzw. die Map-Data sieht so aus:
-
@da_woody
ja, auf eben den beziehe ich mich ja mit meiner Frage.
Valetudo für Steuerung
MQTT/I can't believe it's not valetudo für Karte (was bei mir eben leider nicht funktioniert) -
Ist geplant das der Adapter den Roborock S7 maxv (ultra) unterstützt?
@saeft_2003 generell sollte der laufen. würde sehr gerne die 3d Map in iobroker haben :)... dafür muss ich aber noch mein Budget prüfen... Komme langsam in Rechtfertigungsnot bei meiner Frau weil ich jedes Jahr ein bsi zwie Sauger kaufe und hier schon 4 ihre Runden drehen :-)
-
@saeft_2003 generell sollte der laufen. würde sehr gerne die 3d Map in iobroker haben :)... dafür muss ich aber noch mein Budget prüfen... Komme langsam in Rechtfertigungsnot bei meiner Frau weil ich jedes Jahr ein bsi zwie Sauger kaufe und hier schon 4 ihre Runden drehen :-)
Das hört sich schon mal gut an. Wenn meine Regierung mitspielt werden wir uns den Ultra holen, ich würde dann auf jeden Fall fleißig testen...
-
Ist geplant das der Adapter den Roborock S7 maxv (ultra) unterstützt?
@saeft_2003 sagte in Test Adapter Mihome-vacuum v3.1.6 Next Generarition:
Roborock S7 maxv (ultra)
Der ist ja geil....
Wie immer paar Wochen zu Früh gekauft :cold_sweat:
-
@saeft_2003 sagte in Test Adapter Mihome-vacuum v3.1.6 Next Generarition:
Roborock S7 maxv (ultra)
Der ist ja geil....
Wie immer paar Wochen zu Früh gekauft :cold_sweat:
Aber halt schweine teuer, aber in unserem Fall könnte sich das ganze durchaus lohnen wenn alles richtig funktioniert. Bei roborock gehe ich jetzt da einfach mal von aus :stuck_out_tongue_winking_eye:
-
@saeft_2003 generell sollte der laufen. würde sehr gerne die 3d Map in iobroker haben :)... dafür muss ich aber noch mein Budget prüfen... Komme langsam in Rechtfertigungsnot bei meiner Frau weil ich jedes Jahr ein bsi zwie Sauger kaufe und hier schon 4 ihre Runden drehen :-)
Da mein Dreame D9 nicht supportet wird , oder soll ich sagen noch nicht....wollte ich fragen ob Valetudo eine möglichkeit wäre den Dreame einzubinden.
Falls das geht? ich habe noch nicht so einen Ahnung was Valetudo betrifft , scheue ich aber nich davor dem dreame was neues zu verpassen.
Nun zu den Fragen, werden die Dreame im Adapter noch eigepflegt? wenn das überhaupt geht.
ist Valetudo der Weg den ich nutzen kann oder ist es noch unmöglich, bzw gibt es keinen Weg.Herzlichen Dank schon mal :-)
-
@bahnuhr zu deinem Script frage ich im anderen Thread.
Hier versuche ich den Adapter zu verstehen.
OK.
clean room ist der Name und .roomClean die ID vom DP aber es reicht nicht aus den Entsprechenden Button zu betätigen.
Wenn ich diesen Button betätige oder den Wert auf "true" bestätigt ändere passiert bei mir nichts, sollte doch aber oder nicht?
Und wieso stehen die jetzt alle auf "true" obwohl der Sauger in der Station steht?
@wendy2702 sagte in Test Adapter Mihome-vacuum v3.1.6 Next Generarition:
@bahnuhr zu deinem Script frage ich im anderen Thread.
Hier versuche ich den Adapter zu verstehen.
OK.
clean room ist der Name und .roomClean die ID vom DP aber es reicht nicht aus den Entsprechenden Button zu betätigen.
Wenn ich diesen Button betätige oder den Wert auf "true" bestätigt ändere passiert bei mir nichts, sollte doch aber oder nicht?
Und wieso stehen die jetzt alle auf "true" obwohl der Sauger in der Station steht?
Sorry,
ich muss mich nochmal selber zitieren.
Kann mir jemand sagen ob die als "Button" definierten Objekte auch als Button funktionieren sollten?
Sprich, ich klicke auf den Button für Room clean und der Sauger sollte los fahren und den entsprechenden Raum reinigen.
Dann noch eine andere Frage, ich weiß das irgendwo beschrieben steht wie ich rausfinde welcher Raum sich hinter der entsprechenden Nummer in den Objekten befindet... wo steht das nochmal oder wie ging das nochmal?
Danke und Gruß
Bitte keine Fragen per PN, die gehören ins Forum!
Benutzt das Voting rechts unten im Beitrag wenn er euch geholfen hat.
-
@wendy2702 sagte in Test Adapter Mihome-vacuum v3.1.6 Next Generarition:
@bahnuhr zu deinem Script frage ich im anderen Thread.
Hier versuche ich den Adapter zu verstehen.
OK.
clean room ist der Name und .roomClean die ID vom DP aber es reicht nicht aus den Entsprechenden Button zu betätigen.
Wenn ich diesen Button betätige oder den Wert auf "true" bestätigt ändere passiert bei mir nichts, sollte doch aber oder nicht?
Und wieso stehen die jetzt alle auf "true" obwohl der Sauger in der Station steht?
Sorry,
ich muss mich nochmal selber zitieren.
Kann mir jemand sagen ob die als "Button" definierten Objekte auch als Button funktionieren sollten?
Sprich, ich klicke auf den Button für Room clean und der Sauger sollte los fahren und den entsprechenden Raum reinigen.
Dann noch eine andere Frage, ich weiß das irgendwo beschrieben steht wie ich rausfinde welcher Raum sich hinter der entsprechenden Nummer in den Objekten befindet... wo steht das nochmal oder wie ging das nochmal?
Danke und Gruß
Wenn ich den DP room clean mit wahr steure, dann wird der Raum gereinigt.
Du musst ein Raum nach dem anderen auswählen und dann entsprechend benennen.
Wenn der bei room clean aber nichts macht, dann ist irgendwas falsch. Sagt das log irgendwas? Hast du verschiedene Karten?
Edit: bei mapindex muss eine zahl stehen und state muss leer sein, dann sollte alles richtig sein.
Hier ein Raum aus einer anderen Karte, so darf es nicht aussehen.
-
Wenn ich den DP room clean mit wahr steure, dann wird der Raum gereinigt.
Du musst ein Raum nach dem anderen auswählen und dann entsprechend benennen.
Wenn der bei room clean aber nichts macht, dann ist irgendwas falsch. Sagt das log irgendwas? Hast du verschiedene Karten?
Edit: bei mapindex muss eine zahl stehen und state muss leer sein, dann sollte alles richtig sein.
Hier ein Raum aus einer anderen Karte, so darf es nicht aussehen.
@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?
-
@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...
@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.
Support us
735
Online32.5k
Benutzer81.8k
Themen1.3m
Beiträge