Test Adapter Mihome-vacuum v3.1.6 Next Generarition
-
@dirkhe
Das Problem: Adapter stürzt immer wieder ab, sobald Roboter S7 läuft, stürzt jede 5. Sekunde ab.
host.SERVER 2022-01-23 21:54:50.063 info Restart adapter system.adapter.mihome-vacuum.1 because enabled host.SERVER 2022-01-23 21:54:50.062 info instance system.adapter.mihome-vacuum.1 terminated with code NaN () host.SERVER 2022-01-23 21:54:50.061 warn instance system.adapter.mihome-vacuum.1 terminated due to SIGSEGV mihome-vacuum.1 2022-01-23 21:54:49.351 debug Message= {"id":6,"method":"get_network_info"} mihome-vacuum.1 2022-01-23 21:54:49.348 debug MIIO RECIVE: {"id":5,"result":[[16,"212001026818"],[18,"212001026816"],[19,"212001026817"]],"exe_time":101} mihome-vacuum.1 2022-01-23 21:54:49.262 debug update_Map got new time:1642971289 mihome-vacuum.1 2022-01-23 21:54:49.261 debug update_Map got new expires:1642973089 mihome-vacuum.1 2022-01-23 21:54:49.261 debug update_Map got new url:https://awsde0.fds.api.xiaomi.com/robomap/roboroommap/416283912/7?Expires=1642973089000&GalaxyAccessKeyId=5271733786445&Signature=RaGbKlh77eQLJYh2wO8rGY/DrOw= mihome-vacuum.1 2022-01-23 21:54:49.155 debug Message= {"id":5,"method":"get_room_mapping"} mihome-vacuum.1 2022-01-23 21:54:49.149 debug update_Map need new mapurl mihome-vacuum.1 2022-01-23 21:54:49.149 debug update_Map Mimap enabled mihome-vacuum.1 2022-01-23 21:54:49.147 debug Mappointer_updated mihome-vacuum.1 2022-01-23 21:54:49.147 debug MIIO RECIVE: {"id":4,"result":["roboroommap%2F416283912%2F7"],"exe_time":101} mihome-vacuum.1 2022-01-23 21:54:48.948 debug Message= {"id":4,"method":"get_map_v1"} mihome-vacuum.1 2022-01-23 21:54:48.645 debug MIIO RECIVE: {"id":3,"result":["retry"],"exe_time":101} mihome-vacuum.1 2022-01-23 21:54:48.530 debug Message= {"id":3,"method":"get_map_v1"} mihome-vacuum.1 2022-01-23 21:54:48.402 info create states for mop mihome-vacuum.1 2022-01-23 21:54:48.398 info create states for water box mode mihome-vacuum.1 2022-01-23 21:54:48.383 info create states for water box mihome-vacuum.1 2022-01-23 21:54:48.347 info change states from State control.fan_power mihome-vacuum.1 2022-01-23 21:54:48.346 debug setGetStatus {"msg_ver":2,"msg_seq":3267,"state":10,"battery":99,"clean_time":81,"clean_area":155000,"error_code":0,"map_present":true,"in_cleaning":true,"in_returning":0,"in_fresh_state":0,"lab_status":3,"water_box_status":1,"fan_power":102,"dnd_enabled":false,"map_status":3,"is_locating":0,"lock_status":0,"water_box_mode":202,"water_box_carriage_status":0,"mop_forbidden_enable":0,"adbumper_status":[0,0,0],"water_shortage_status":0,"dock_type":0,"dust_collection_status":0,"auto_dust_collection":1,"mop_mode":300,"debug_mode":0,"error_text":"No error"} mihome-vacuum.1 2022-01-23 21:54:48.344 debug MIIO RECIVE: {"id":2,"result":[{"msg_ver":2,"msg_seq":3267,"state":10,"battery":99,"clean_time":81,"clean_area":155000,"error_code":0,"map_present":1,"in_cleaning":1,"in_returning":0,"in_fresh_state":0,"lab_status":3,"water_box_status":1,"fan_power":102,"dnd_enabled":0,"map_status":3,"is_locating":0,"lock_status":0,"water_box_mode":202,"water_box_carriage_status":0,"mop_forbidden_enable":0,"adbumper_status":[0,0,0],"water_shortage_status":0,"dock_type":0,"dust_collection_status":0,"auto_dust_collection":1,"mop_mode":300,"debug_mode":0}],"exe_time":101} mihome-vacuum.1 2022-01-23 21:54:48.188 debug Message= {"id":2,"method":"get_status"} mihome-vacuum.1 2022-01-23 21:54:48.185 debug get params for stock Vacuum mihome-vacuum.1 2022-01-23 21:54:48.184 debug Create State done! mihome-vacuum.1 2022-01-23 21:54:48.183 debug Create State for map: loadMap mihome-vacuum.1 2022-01-23 21:54:48.182 debug Create State for map: mapURL mihome-vacuum.1 2022-01-23 21:54:48.179 debug Create State for map: mapStatus mihome-vacuum.1 2022-01-23 21:54:48.178 debug Create State for map: actualMap mihome-vacuum.1 2022-01-23 21:54:48.178 debug Create State for map: map64 mihome-vacuum.1 2022-01-23 21:54:48.177 debug Create State for map: mihome-vacuum.1 2022-01-23 21:54:48.161 info Map selected create states... mihome-vacuum.1 2022-01-23 21:54:48.156 debug Create State for Queue: clearQueue mihome-vacuum.1 2022-01-23 21:54:48.155 debug Create State for Queue: queue mihome-vacuum.1 2022-01-23 21:54:48.138 debug Create State for control: {"id":"mihome-vacuum.1.control"} mihome-vacuum.1 2022-01-23 21:54:48.119 debug Xiaomi Cloud: Login successful mihome-vacuum.1 2022-01-23 21:54:48.118 debug Login step3: [{"key":"userId","value":"6285111871","domain":"sts.api.io.mi.com","path":"/","hostOnly":false,"creation":"2022-01-23T20:54:48.086Z","lastAccessed":"2022-01-23T20:54:48.117Z"},{"key":"cUserId","value":"g5O994QI2YKKWhdn9WHsfj9CdPo","domain":"sts.api.io.mi.com","path":"/","hostOnly":false,"creation":"2022-01-23T20:54:48.103Z","lastAccessed":"2022-01-23T20:54:48.117Z"},{"key":"serviceToken","value":"az++AjXJmxK89uafsvrJXqSDoRpPC70XRxHoXE4emfci+Jx5bVNfZoTriQvbhn66I1WAdwAEhTdesjRLxAyu/c0Jj19W3bfm4ie0917XklB0a7mmobcOBvmC+mNgOIUs4zekfKkQbTGK8v23GBuc/IuGjNPnOPhprxYt8oOTpTw=","domain":"sts.api.io.mi.com","path":"/","hostOnly":false,"creation":"2022-01-23T20:54:48.109Z","lastAccessed":"2022-01-23T20:54:48.117Z"}] mihome-vacuum.1 2022-01-23 21:54:48.040 info settest next timer: not available mihome-vacuum.1 2022-01-23 21:54:47.786 debug Login step2: &&&START&&&{"qs":"%3Fsid%3Dxiaomiio%26_json%3Dtrue","ssecurity":"19JmVLKhcaHQ4StDjtrpPw==","code":0,"passToken":"V1:DXmurwq2/R1BHTELu6obCTahB2FtsoEhGZdTBmTFVWU/GThVGfv4duLTJl8gyYP6u2G9ikDKY42dSWAoXPMbcfYphpxV0/iF44bVAXXpC1VJa74fhBnHSP50HaajATyF8tDcYASas+MxJjQ8qzjZGS/2RQi4/T+tLM5RSNiYnBlSHgD8pmOECjpaikHkzo/qd0z9LWHtAAYhFVx8purYH0sBnXBOT9cd4H3zYvty1e2xHY4dn1iJYriOQ4QMrK3nF9oTr7BcYru+pTPZ0CywOHj8Bx/rnBMSVFS+5ohb/g8=","description":"成功","securityStatus":0,"nonce":6237418414117258240,"userId":6285111871,"cUserId":"g5O994QI2YKKWhdn9WHsfj9CdPo","result":"ok","psecurity":"UZ5P9B42Cq//Is1E4/13fw==","captchaUrl":null,"location":"https://sts.api.io.mi.com/sts?d=vktfoy&ticket=0&pwd=1&p_ts=1642971287000&fid=0&p_lm=1&auth=TYHmsQxnZZ7qGx2HwfPmhgUXP5wcxszGBU7Z1r2qL94qU4IsQFSQVMFd4%2FCf0x2hpUij7X3lzCgV6nvFYTbuYSVh0TN0aRfNCq%2BZgwUnsAGrs1fU6ibmZiTOGNTYiIUS%2FAmsuuwzsIr94e9NWu%2BzKJwode35w0zQTId%2FD2qYqRk%3D&m=1&tsl=0&nonce=vTyyXZFQQY0BodRG&_ssign=RV7C%2FXsTLAKjFt4c%2BKETIma3Uzg%3D","pwd":1,"desc":"成功"} mihome-vacuum.1 2022-01-23 21:54:47.613 debug Login step1: &&&START&&&{"serviceParam":"{\"checkSafePhone\":false,\"checkSafeAddress\":false,\"lsrp_score\":0.0}","qs":"%3Fsid%3Dxiaomiio%26_json%3Dtrue","code":70016,"description":"登录验证失败","securityStatus":0,"_sign":"0psXfr43eNI0IX6q9Suk3qWbRqU=","sid":"xiaomiio","result":"error","captchaUrl":null,"callback":"https://sts.api.io.mi.com/sts","location":"https://account.xiaomi.com/fe/service/login?_json=true&sid=xiaomiio&qs=%253Fsid%253Dxiaomiio%2526_json%253Dtrue&callback=https%3A%2F%2Fsts.api.io.mi.com%2Fsts&_sign=0psXfr43eNI0IX6q9Suk3qWbRqU%3D&serviceParam=%7B%22checkSafePhone%22%3Afalse%2C%22checkSafeAddress%22%3Afalse%2C%22lsrp_score%22%3A0.0%7D&showActiveX=false&theme=&needTheme=false&bizDeviceType=","pwd":0,"desc":"登录验证失败"} mihome-vacuum.1 2022-01-23 21:54:47.465 debug Search can't be optimized because wildcard not at the end, fallback to keys!: function(doc) { if (doc.type === 'state') emit(doc._id, doc) } mihome-vacuum.1 2022-01-23 21:54:47.399 debug Xiaomi Cloud: Logging in mihome-vacuum.1 2022-01-23 21:54:47.393 info select standard vacuum protocol.... mihome-vacuum.1 2022-01-23 21:54:47.391 debug DeviceModel selected to: roborock.vacuum.a15 mihome-vacuum.1 2022-01-23 21:54:47.344 debug Get Device data from robot.. mihome-vacuum.1 2022-01-23 21:54:47.343 debug Get Device data..0 mihome-vacuum.1 2022-01-23 21:54:47.342 debug GETMODELFROMAPI:Data: {"id":1,"result":{"life":67581,"uid":6285111871,"model":"roborock.vacuum.a15","token":"5755304d3354576831376******","ipflag":1,"miio_ver":"0.0.9","mac":"B0:4A:39:16:2E:3D","fw_ver":"4.1.5_1398","hw_ver":"Linux","miio_client_ver":"4.1.5","VmPeak":9116,"VmRSS":1652,"MemFree":64112,"ap":{"ssid":"SERVER-ZENTRALE","bssid":"68:d7:9a:d7:1d:f3","rssi":"","freq":0},"netif":{"localIp":"172.16.0.80","mask":"255.255.0.0","gw":"172.16.0.1"},"miio_times":[67580,15,0,67564]},"exe_time":1} mihome-vacuum.1 2022-01-23 21:54:47.341 debug MIIO RECIVE: {"id":1,"result":{"life":67581,"uid":6285111871,"model":"roborock.vacuum.a15","token":"5755304d335457683137676******","ipflag":1,"miio_ver":"0.0.9","mac":"B0:4A:39:16:2E:3D","fw_ver":"4.1.5_1398","hw_ver":"Linux","miio_client_ver":"4.1.5","VmPeak":9116,"VmRSS":1652,"MemFree":64112,"ap":{"ssid":"SERVER-ZENTRALE","bssid":"68:d7:9a:d7:1d:f3","rssi":"","freq":0},"netif":{"localIp":"172.16.0.80","mask":"255.255.0.0","gw":"172.16.0.1"},"miio_times":[67580,15,0,67564]},"exe_time":1} mihome-vacuum.1 2022-01-23 21:54:47.187 debug Message= {"id":1,"method":"miIO.info"} mihome-vacuum.1 2022-01-23 21:54:47.185 debug GETMODELFROMAPI: objModel: {"val":"roborock.vacuum.a15","ack":true,"ts":1642971251206,"q":0,"from":"system.adapter.mihome-vacuum.1","user":"system.user.admin","lc":1642534204932} mihome-vacuum.1 2022-01-23 21:54:47.150 debug Time difference between Mihome Vacuum and ioBroker: -1642903707 sec mihome-vacuum.1 2022-01-23 21:54:47.146 debug MAIN: Connected to device, try to get model.. mihome-vacuum.1 2022-01-23 21:54:47.144 debug Receive <<< Helo <<< 213100200000000018cffd08000107fcffffffffffffffffffffffffffffffff mihome-vacuum.1 2022-01-23 21:54:47.107 debug server started on 0.0.0.0:53422 mihome-vacuum.1 2022-01-23 21:54:47.100 info IOT enabled, create state mihome-vacuum.1 2022-01-23 21:54:47.092 debug MIIO: Config: ip:172.16.0.80 token: 5755304d33545768313********** mihome-vacuum.1 2022-01-23 21:54:47.091 debug Create State for deviceInfowifi_signal mihome-vacuum.1 2022-01-23 21:54:47.090 debug Create State for deviceInfofw_ver mihome-vacuum.1 2022-01-23 21:54:47.085 debug Create State for deviceInfomodel mihome-vacuum.1 2022-01-23 21:54:47.084 debug Create State for deviceInfomac mihome-vacuum.1 2022-01-23 21:54:47.083 debug Create State for deviceInfo mihome-vacuum.1 2022-01-23 21:54:47.029 debug load Map creator... true mihome-vacuum.1 2022-01-23 21:54:46.915 info starting. Version 3.3.4 in /opt/iobroker/node_modules/iobroker.mihome-vacuum, node: v14.18.3, js-controller: 3.3.22 mihome-vacuum.1 2022-01-23 21:54:46.605 debug Plugin sentry Initialize Plugin (enabled=true) host.SERVER 2022-01-23 21:54:43.944 info instance system.adapter.mihome-vacuum.1 started with pid 9933 -
@maxim-777 sagte in Test Adapter Mihome-vacuum v3.1.6 Next Generarition:
nated due to SIGSEGV
es ist mir bislang nicht gelungen den Fehler zu reproduzieren . wenn du Interesse hast, mache ich eine Version fertig, die bei der Kartengenerierung mehr loggt um den Fehler weiter einzugrenzen. wie schonmal beschrieben ist das kein Fehler im Adapter sondern ein berechnungs/schreibfehler vom Prozessor. Aber wenn ich die Stelle weiter eingrenzen kann, kann ich versuchen den Fehler zu umgehen. Das bedeutet aber log leeren, alle anderen adapter aussschalten und dann den debuglog aufzeichen
-
Hallo Leute!
War länger nicht hier, ich hab nun bemerkt dasss ein längerer Zeit mit S5 die MAP nicht mehr aktualisiert
Adapter ist grün, es geht auch alles andere an anzeigen und Kommandos nur bei der Karte passiert nichts mehr
das war mal mit Hilfe von euch eingerichtet
sollte da nicht ein neuerer Datumsstempel sein ?
evtl hat auch einer von euch mal 5 min zeit und kann sich das gern remote ansehen ich kapiers aktuell echt nicht wieso das nicht mehr geht
FW ist 3.5.8_1566
danke
tom Bastler bei dem es beim programmieren dann schnell mal aneckt habe rmotiviert -
@meistertr
ja
ich bin sehr interessiert 
-
@bahnuhr nachdem sich ja bei mir die karte in iQontrol nicht mehr aktualisiert hat, hats mir gereicht.
testhalber mit deinen vorschlägen in vis views angelegt, diese dann in iQontrol als BACKGROUND_URL aufgerufen, siehe da, beide aktualisieren!
allerdings "blinkt" durch die aktualisierung map64 immer wieder, bei png nicht.
somit ist mein prob endlich gelöst und hilft anderen eventuell auch... -
@da_woody sagte in Test Adapter Mihome-vacuum v3.1.6 Next Generarition:
iQontrol
Damit kenn ich mich gar nicht aus.
Ist aber doch super, dass es jetzt läuft.
Ein "blinken" hatte ich bei map64 aber nicht.mfg
-
Welche V hast du installiert. Sieht veraltet aus ?
Die Lösung steht im Beitrag 681. -
@bahnuhr sagte in Test Adapter Mihome-vacuum v3.1.6 Next Generarition:
Ein "blinken" hatte ich bei map64 aber nicht.
anscheinend wird png nur abgerufen, map64 refresht sich ja recht schnell, somit muss das bild immer neu aufgebaut werden. in vis selber wars auch nicht. ist anscheinend ein runtime prob im zusammenspiel mit iQontrol.
anyway, funzt, passt...
-
v3.3.4 ist bei mir heute abgestürzt als ich über den mihome-vacuum.0.rooms.***.roomClean Button einen weiteren Raum zum Queue hinzufügen wollte während er bereits einen saugte.
Loglevel der Instanz ist warn, daher nur das aus dem Log:2022-01-27 14:10:50.738 - error: mihome-vacuum.0 (1148) uncaught exception: Cannot read property 'body' of undefined 2022-01-27 14:10:50.748 - error: mihome-vacuum.0 (1148) TypeError: Cannot read property 'body' of undefined at Request._callback (/opt/iobroker/node_modules/iobroker.mihome-vacuum/lib/maphelper.js:454:68) at self.callback (/opt/iobroker/node_modules/request/request.js:185:22) at Request.emit (events.js:400:28) at Request.emit (domain.js:475:12) at Request.onRequestError (/opt/iobroker/node_modules/request/request.js:877:8) at ClientRequest.emit (events.js:412:35) at ClientRequest.emit (domain.js:475:12) at TLSSocket.socketErrorListener (_http_client.js:475:9) at TLSSocket.emit (events.js:400:28) at TLSSocket.emit (domain.js:475:12) 2022-01-27 14:10:50.749 - error: mihome-vacuum.0 (1148) Cannot read property 'body' of undefined 2022-01-27 14:10:50.763 - error: mihome-vacuum.0 (1148) Socket Close 2022-01-27 14:10:50.765 - warn: mihome-vacuum.0 (1148) Terminated (UNCAUGHT_EXCEPTION): Without reason 2022-01-27 14:10:51.364 - error: host.iobroker Caught by controller[0]: TypeError: Cannot read property 'body' of undefined 2022-01-27 14:10:51.371 - error: host.iobroker Caught by controller[0]: at Request._callback (/opt/iobroker/node_modules/iobroker.mihome-vacuum/lib/maphelper.js:454:68) 2022-01-27 14:10:51.371 - error: host.iobroker Caught by controller[0]: at self.callback (/opt/iobroker/node_modules/request/request.js:185:22) 2022-01-27 14:10:51.372 - error: host.iobroker Caught by controller[0]: at Request.emit (events.js:400:28) 2022-01-27 14:10:51.372 - error: host.iobroker Caught by controller[0]: at Request.emit (domain.js:475:12) 2022-01-27 14:10:51.372 - error: host.iobroker Caught by controller[0]: at Request.onRequestError (/opt/iobroker/node_modules/request/request.js:877:8) 2022-01-27 14:10:51.372 - error: host.iobroker Caught by controller[0]: at ClientRequest.emit (events.js:412:35) 2022-01-27 14:10:51.372 - error: host.iobroker Caught by controller[0]: at ClientRequest.emit (domain.js:475:12) 2022-01-27 14:10:51.372 - error: host.iobroker Caught by controller[0]: at TLSSocket.socketErrorListener (_http_client.js:475:9) 2022-01-27 14:10:51.372 - error: host.iobroker Caught by controller[0]: at TLSSocket.emit (events.js:400:28) 2022-01-27 14:10:51.372 - error: host.iobroker Caught by controller[0]: at TLSSocket.emit (domain.js:475:12) 2022-01-27 14:10:51.372 - error: host.iobroker instance system.adapter.mihome-vacuum.0 terminated with code 1 (JS_CONTROLLER_STOPPED) -
@diginix das können wir noch abfangen, aber das Problem scheint mit dem Netzwerk zu tun zu haben, da ist das socket geschlossen worden. Könntest du evtl ein issue aufmachen?
-
-
@freaktech Versuch mal den Adapter in der Version 3.3.3 aus dem Latest, damit gings bei den meisten / allen wieder.
-
Hallo Zusammen,
ich habe hier schon viel gelesen, aber irgendwie habe ich scheinbar ein Brett vor dem Kopf.
Könnt Ihr mir nochmal auf die Sprünge helfen mit dem MultiRoomClean? Ich habe alle Räume in IOBroker angelegt und mit den entsprechenden Channels verknüpft.
Und wie bekomme ich das jetzt auf die VIS, so dass ich die zu reinigenden Räume vorwählen und dann nur auf Start drücken brauche?
Außerdem habe ich noch ein Problem mit dem Pause.Resume Switch. Diesen habe ich versucht mit dem HTML Bool true/False Widget zu triggern. Leider ohne Erfolg. Muss ich hierfür zwingend die Buttons Start und Pause nutzen? Wenn ja, welchen Button nehme ich hierfür am Besten?
-
Wenn du willst kannst du einfach mein view nehmen da sollte sich alles von alleine erklären.
-
Hey, das sieht ja mal cool aus! Ich schau mal ob ich damit klarkomme. Hab noch nicht so viel Erfahrung mit der VIS, da ich bis jetzt alles mit Jarvis gemacht habe.
Besten Dank schon mal, das ist wirklich nett!
-
mihome-vacuum.0 2022-01-30 15:14:36.959 info create state for carpet_mode mihome-vacuum.0 2022-01-30 15:14:35.976 info create states for mop mihome-vacuum.0 2022-01-30 15:14:35.969 info create states for water box mode mihome-vacuum.0 2022-01-30 15:14:35.961 info create states for water box mihome-vacuum.0 2022-01-30 15:14:35.932 info change states from State control.fan_power mihome-vacuum.0 2022-01-30 15:14:35.906 info Map selected create states... mihome-vacuum.0 2022-01-30 15:14:35.505 info settest next timer: not available mihome-vacuum.0 2022-01-30 15:14:34.878 info select standard vacuum protocol.... mihome-vacuum.0 2022-01-30 15:14:34.768 info IOT enabled, create state mihome-vacuum.0 2022-01-30 15:14:34.627 info starting. Version 3.3.4 in /opt/iobroker/node_modules/iobroker.mihome-vacuum, node: v14.18.3, js-controller: 3.3.22 mihome-vacuum.0 2022-01-30 14:27:50.738 info create state for carpet_mode mihome-vacuum.0 2022-01-30 14:27:49.837 info create states for mop mihome-vacuum.0 2022-01-30 14:27:49.834 info create states for water box mode mihome-vacuum.0 2022-01-30 14:27:49.831 info create states for water box mihome-vacuum.0 2022-01-30 14:27:49.816 info change states from State control.fan_power mihome-vacuum.0 2022-01-30 14:27:49.795 info Map selected create states... mihome-vacuum.0 2022-01-30 14:27:49.369 info settest next timer: not available mihome-vacuum.0 2022-01-30 14:27:48.759 info select standard vacuum protocol.... mihome-vacuum.0 2022-01-30 14:27:48.630 info IOT enabled, create state mihome-vacuum.0 2022-01-30 14:27:48.490 info starting. Version 3.3.4 in /opt/iobroker/node_modules/iobroker.mihome-vacuum, node: v14.18.3, js-controller: 3.3.22 mihome-vacuum.0 2022-01-30 14:27:14.283 info create states for mop mihome-vacuum.0 2022-01-30 14:27:14.279 info create states for water box mode mihome-vacuum.0 2022-01-30 14:27:14.274 info create states for water box mihome-vacuum.0 2022-01-30 14:27:14.258 info change states from State control.fan_power mihome-vacuum.0 2022-01-30 14:26:44.162 info create state for carpet_mode mihome-vacuum.0 2022-01-30 14:23:37.379 info Map selected create states... mihome-vacuum.0 2022-01-30 14:23:37.213 info settest next timer: not available mihome-vacuum.0 2022-01-30 14:23:36.640 info select standard vacuum protocol.... mihome-vacuum.0 2022-01-30 14:23:36.614 warn No Answer for DeviceModel use model from Config mihome-vacuum.0 2022-01-30 14:23:36.613 warn No Answer for DeviceModel use old one mihome-vacuum.0 2022-01-30 14:23:36.613 warn YOUR DEVICE IS CONNECTED BUT DID NOT ANSWER YET - CONNECTION CAN TAKE UP TO 10 MINUTES - PLEASE BE PATIENT AND DO NOT TURN THE ADAPTER OFF mihome-vacuum.0 2022-01-30 14:23:26.577 info IOT enabled, create state mihome-vacuum.0 2022-01-30 14:23:26.399 info starting. Version 3.3.4 in /opt/iobroker/node_modules/iobroker.mihome-vacuum, node: v14.18.3, js-controller: 3.3.22 mihome-vacuum.0 2022-01-30 14:22:38.169 info create state for carpet_mode mihome-vacuum.0 2022-01-30 14:22:34.696 info create states for mop mihome-vacuum.0 2022-01-30 14:22:34.692 info create states for water box mode mihome-vacuum.0 2022-01-30 14:22:34.688 info create states for water box mihome-vacuum.0 2022-01-30 14:22:34.669 info change states from State control.fan_power mihome-vacuum.0 2022-01-30 14:22:34.650 info Map selected create states... mihome-vacuum.0 2022-01-30 14:22:34.503 info settest next timer: not available mihome-vacuum.0 2022-01-30 14:22:33.821 info select standard vacuum protocol.... mihome-vacuum.0 2022-01-30 14:22:33.718 info IOT enabled, create state mihome-vacuum.0 2022-01-30 14:22:33.553 info starting. Version 3.3.4 in /opt/iobroker/node_modules/iobroker.mihome-vacuum, node: v14.18.3, js-controller: 3.3.22 mihome-vacuum.0 2022-01-30 14:21:50.955 info create states for mop mihome-vacuum.0 2022-01-30 14:21:50.949 info create states for water box mode mihome-vacuum.0 2022-01-30 14:21:50.944 info create states for water box mihome-vacuum.0 2022-01-30 14:21:50.914 info change states from State control.fan_power mihome-vacuum.0 2022-01-30 14:21:20.795 info create state for carpet_mode mihome-vacuum.0 2022-01-30 14:16:49.335 info Map selected create states... mihome-vacuum.0 2022-01-30 14:16:49.212 info settest next timer: not available mihome-vacuum.0 2022-01-30 14:16:48.573 info select standard vacuum protocol.... mihome-vacuum.0 2022-01-30 14:16:48.540 warn No Answer for DeviceModel use model from Config mihome-vacuum.0 2022-01-30 14:16:48.539 warn No Answer for DeviceModel use old one mihome-vacuum.0 2022-01-30 14:16:48.538 warn YOUR DEVICE IS CONNECTED BUT DID NOT ANSWER YET - CONNECTION CAN TAKE UP TO 10 MINUTES - PLEASE BE PATIENT AND DO NOT TURN THE ADAPTER OFF mihome-vacuum.0 2022-01-30 14:16:38.493 info IOT enabled, create state mihome-vacuum.0 2022-01-30 14:16:38.348 info starting. Version 3.3.4 in /opt/iobroker/node_modules/iobroker.mihome-vacuum, node: v14.18.3, js-controller: 3.3.22 mihome-vacuum.0 2022-01-30 14:16:02.648 info create states for mop mihome-vacuum.0 2022-01-30 14:16:02.635 info create states for water box mode mihome-vacuum.0 2022-01-30 14:16:02.621 info create states for water box mihome-vacuum.0 2022-01-30 14:16:02.574 info change states from State control.fan_power mihome-vacuum.0 2022-01-30 14:16:02.524 info Map selected create states... mihome-vacuum.0 2022-01-30 14:16:02.054 info settest next timer: not available mihome-vacuum.0 2022-01-30 14:16:01.312 info select standard vacuum protocol.... mihome-vacuum.0 2022-01-30 14:16:01.148 info IOT enabled, create state mihome-vacuum.0 2022-01-30 14:16:00.898 info starting. Version 3.3.4 in /opt/iobroker/node_modules/iobroker.mihome-vacuum, node: v14.18.3, js-controller: 3.3.22 mihome-vacuum.0 2022-01-30 14:15:21.567 info create states for mop mihome-vacuum.0 2022-01-30 14:15:21.561 info create states for water box mode mihome-vacuum.0 2022-01-30 14:15:21.557 info create states for water box mihome-vacuum.0 2022-01-30 14:15:21.544 info change states from State control.fan_power mihome-vacuum.0 2022-01-30 14:14:51.421 info create state for carpet_mode mihome-vacuum.0 2022-01-30 14:14:03.065 info Map selected create states... mihome-vacuum.0 2022-01-30 14:14:02.912 info settest next timer: not available mihome-vacuum.0 2022-01-30 14:14:02.223 info select standard vacuum protocol.... mihome-vacuum.0 2022-01-30 14:14:02.189 warn No Answer for DeviceModel use model from Config mihome-vacuum.0 2022-01-30 14:14:02.188 warn No Answer for DeviceModel use old one mihome-vacuum.0 2022-01-30 14:14:02.187 warn YOUR DEVICE IS CONNECTED BUT DID NOT ANSWER YET - CONNECTION CAN TAKE UP TO 10 MINUTES - PLEASE BE PATIENT AND DO NOT TURN THE ADAPTER OFF mihome-vacuum.0 2022-01-30 14:13:52.084 info IOT enabled, create state mihome-vacuum.0 2022-01-30 14:13:51.928 info starting. Version 3.3.4 in /opt/iobroker/node_modules/iobroker.mihome-vacuum, node: v14.18.3, js-controller: 3.3.22 mihome-vacuum.0 2022-01-30 14:13:17.086 info create states for mop mihome-vacuum.0 2022-01-30 14:13:17.083 info create states for water box mode mihome-vacuum.0 2022-01-30 14:13:17.080 info create states for water box mihome-vacuum.0 2022-01-30 14:13:17.064 info change states from State control.fan_power mihome-vacuum.0 2022-01-30 14:13:17.038 info Map selected create states... mihome-vacuum.0 2022-01-30 14:13:16.897 info settest next timer: not available mihome-vacuum.0 2022-01-30 14:13:16.295 info select standard vacuum protocol.... mihome-vacuum.0 2022-01-30 14:13:16.183 info IOT enabled, create state mihome-vacuum.0 2022-01-30 14:13:16.036 info starting. Version 3.3.4 in /opt/iobroker/node_modules/iobroker.mihome-vacuum, node: v14.18.3, js-controller: 3.3.22Hat noch jemand dasselbe Problem aktuell?
Node.js: v14.18.3
NPM: 6.14.16
Adapterversion: 3.3.4
RPI4 4GBRoborock s5 Max, FW: 3.5.8_1566
Während der Sauger läuft, habe ich quasi einen "loop" an Neustart.
Ansonsten kann es mal sein, dass 4 Stunden nichts passiert und dann wieder 30 Neustarts in 10 Minuten. -
mihome-vacuum.0 2022-02-02 08:52:11.236 info Map selected create states... mihome-vacuum.0 2022-02-02 08:52:10.817 info settest next timer: not available mihome-vacuum.0 2022-02-02 08:52:10.177 info select standard vacuum protocol.... mihome-vacuum.0 2022-02-02 08:52:10.151 warn No Answer for DeviceModel use model from Config mihome-vacuum.0 2022-02-02 08:52:10.151 warn No Answer for DeviceModel use old one mihome-vacuum.0 2022-02-02 08:52:10.150 warn YOUR DEVICE IS CONNECTED BUT DID NOT ANSWER YET - CONNECTION CAN TAKE UP TO 10 MINUTES - PLEASE BE PATIENT AND DO NOT TURN THE ADAPTER OFF mihome-vacuum.0 2022-02-02 08:52:00.060 info IOT enabled, create state mihome-vacuum.0 2022-02-02 08:51:59.904 info starting. Version 3.3.4 in /opt/iobroker/node_modules/iobroker.mihome-vacuum, node: v14.19.0, js-controller: 3.3.22 host.raspberrypi 2022-02-02 08:51:56.841 info instance system.adapter.mihome-vacuum.0 started with pid 21674 host.raspberrypi 2022-02-02 08:51:26.771 info Restart adapter system.adapter.mihome-vacuum.0 because enabled host.raspberrypi 2022-02-02 08:51:26.770 info instance system.adapter.mihome-vacuum.0 terminated with code NaN () host.raspberrypi 2022-02-02 08:51:26.769 warn instance system.adapter.mihome-vacuum.0 terminated due to SIGILL host.raspberrypi 2022-02-02 08:51:26.768 error Caught by controller[0]: #FailureMessage Object: 0xbe9c67e0 host.raspberrypi 2022-02-02 08:51:26.768 error Caught by controller[0]: # host.raspberrypi 2022-02-02 08:51:26.767 error Caught by controller[0]: # host.raspberrypi 2022-02-02 08:51:26.767 error Caught by controller[0]: # host.raspberrypi 2022-02-02 08:51:26.766 error Caught by controller[0]: # Check failed: heap_->memory_allocator()->IsMemoryChunkExecutable(page). host.raspberrypi 2022-02-02 08:51:26.766 error Caught by controller[0]: # Fatal error in , line 0 host.raspberrypi 2022-02-02 08:51:26.759 error Caught by controller[0]: # mihome-vacuum.0 2022-02-02 08:50:12.336 info create state for carpet_mode mihome-vacuum.0 2022-02-02 08:50:09.525 warn Object of state "mihome-vacuum.0.cleanmap.actualMap" is missing the required property "common.type" mihome-vacuum.0 2022-02-02 08:50:09.464 info create states for mop mihome-vacuum.0 2022-02-02 08:50:09.460 info create states for water box mode mihome-vacuum.0 2022-02-02 08:50:09.455 info create states for water box mihome-vacuum.0 2022-02-02 08:50:09.430 info change states from State control.fan_power mihome-vacuum.0 2022-02-02 08:50:09.402 info Map selected create states... mihome-vacuum.0 2022-02-02 08:50:09.253 info settest next timer: not available mihome-vacuum.0 2022-02-02 08:50:08.619 info select standard vacuum protocol.... mihome-vacuum.0 2022-02-02 08:50:08.500 info IOT enabled, create state mihome-vacuum.0 2022-02-02 08:50:08.321 info starting. Version 3.3.4 in /opt/iobroker/node_modules/iobroker.mihome-vacuum, node: v14.19.0, js-controller: 3.3.22 host.raspberrypi 2022-02-02 08:50:05.065 info instance system.adapter.mihome-vacuum.0 started with pid 20324 host.raspberrypi 2022-02-02 08:49:35.014 info Restart adapter system.adapter.mihome-vacuum.0 because enabled host.raspberrypi 2022-02-02 08:49:35.014 info instance system.adapter.mihome-vacuum.0 terminated with code NaN () host.raspberrypi 2022-02-02 08:49:35.009 warn instance system.adapter.mihome-vacuum.0 terminated due to SIGSEGVIch bekomme es anscheinend nicht hin.
nodejs
v14.19.0
node
v14.19.0
npm
6.14.16pi@raspberrypi:/opt/iobroker $ npm list canvas iobroker.inst@2.0.3 /opt/iobroker ├── canvas@2.9.0 ├─┬ iobroker.iot@1.8.24 │ └── canvas@2.9.0 deduped └─┬ iobroker.mihome-vacuum@3.3.4 (github:iobroker-community-adapters/ioBroker.mihome-vacuum#881c0892d76cf4087b5c6247f67b0ba2a7ee34fd) └── canvas@2.9.0 deduped -
Könnte mir noch mal jemand helfen mit der Karte für die VIS. Und zwar hätte ich da gern die Map64 drin. Nur weiß ich nicht welches Widget und welcher Code da rein muss ? Mit der normalen Map über image Widget klappt es schon mal. Die Map 64 hätte ich aber gern, da sie flotter beim aktualisieren ist.
So wie es bei mir früher ging klappt es nicht mehr..
Basicl HTML Widget.
Mit dem Link aus der Beschreibung klappt es leider auch nicht.
Wenn ich das so eingebe
<img src="https://www.iobroker.net/zh-cn/adapterref/iobroker.mihome-vacuum/mihome-vacuum.0.cleanmap.map64">passiert nichts im Basic HTML Widget. Liegt das vllt an zh-cn ? Da ich dort DE Server drin hab ? Hab aber auch schon mit de-de oder de-ger versucht. Das kann ich auch nicht verwenden oder weiß nicht wie und wo ?
mihome-vacuum.0.cleanmap.map64 -
@d3ltoroxp
https://forum.iobroker.net/topic/44077/test-adapter-mihome-vacuum-v3-1-6-next-generarition/681?page=35Hast du denn den thread gelesen?
Fragst doch jetzt schon mehrmals, oder ? -
@bahnuhr Den hatte ich dann wohl leider übersehen. Ich wollte das jetzt noch mal angehen. Es funktioniert nun so auch wunderbar. Ausser in dem Editor, ich hatte das dann nie Live probiert, weil er im Editor immer das kaputte Image Zeichen angezeigt hat und beim anderen aber doch die Map.
Indem Fall sieht man das wohl im Editor nicht, aber in dem Browser mit der VIS sieht man es.
