NEWS
Test Adapter Mihome-vacuum v3.1.6 Next Generarition
-
@meistertr
Hier noch den Log :)
-
@saeft_2003 ich kann nur immer wieder betonen, dass die liste lang ist die ich umsetzten will,. also kann es in ein paar Wochen oder Monaten kommen
@meistertr sagte in Test Adapter Mihome-vacuum v3.1.6 Next Generarition:
@saeft_2003 ich kann nur immer wieder betonen, dass die liste lang ist die ich umsetzten will,. also kann es in ein paar Wochen oder Monaten kommen
Alles klar das verstehe ich natürlich. Falls ich bei irgendwelchen simplen Sachen helfen kann was dazu hilft den Zyklus zu integrieren, dann sag Bescheid.
-
Hi,
hab seit letzter Wochen einen Roborock S7 und wollte den mit iobroker verbinden.
Die Verbindung bekomme ich soweit auch hin. Token usw. hat geklappt.
Ich habe Version 3.20 am laufen und bekomme in endlosschleife diese Log Ausgaben.mihome-vacuum.0 2021-06-07 10:11:32.591 debug (17421) Helo message Timeout mihome-vacuum.0 2021-06-07 10:11:20.589 debug (17421) Time difference between Mihome Vacuum and ioBroker: -1623027974 sec mihome-vacuum.0 2021-06-07 10:11:20.588 debug (17421) Receive <<< Helo <<< 213100200000000018cf43ce000063a2ffffffffffffffffffffffffffffffff mihome-vacuum.0 2021-06-07 10:11:19.784 debug (17421) MIIO RECIVE: {"id":326,"result":[{"enable":1,"current_integral":450,"current_high":500,"current_low":400,"stall_time":10}],"exe_time":100} mihome-vacuum.0 2021-06-07 10:11:19.576 debug (17421) Message= {"id":326,"method":"get_carpet_mode"} mihome-vacuum.0 2021-06-07 10:11:19.575 debug (17421) MIIO RECIVE: {"id":325,"result":[90],"exe_time":200} mihome-vacuum.0 2021-06-07 10:11:19.285 debug (17421) Message= {"id":325,"method":"get_sound_volume"} mihome-vacuum.0 2021-06-07 10:11:19.274 debug (17421) MIIO RECIVE: {"id":324,"result":{"ssid":"Familie-Gerndt","ip":"192.168.178.70","mac":"b0:4a:39:15:75:03","bssid":"2c:91:ab:a5:2f:9a","rssi":-47},"exe_time":100} mihome-vacuum.0 2021-06-07 10:11:19.085 debug (17421) Message= {"id":324,"method":"get_network_info"} mihome-vacuum.0 2021-06-07 10:11:19.083 debug (17421) setGetStatus {"msg_ver":2,"msg_seq":609,"state":8,"battery":90,"clean_time":2399,"clean_area":30630000,"error_code":0,"map_present":true,"in_cleaning":false,"in_returning":0,"in_fresh_state":1 mihome-vacuum.0 2021-06-07 10:11:19.082 debug (17421) MIIO RECIVE: {"id":323,"result":[{"msg_ver":2,"msg_seq":609,"state":8,"battery":90,"clean_time":2399,"clean_area":30630000,"error_code":0,"map_present":1,"in_cleaning":0,"in_returning":0,"in_f mihome-vacuum.0 2021-06-07 10:11:18.814 debug (17421) Message= {"id":323,"method":"get_status"} mihome-vacuum.0 2021-06-07 10:11:18.813 debug (17421) get params for stock Vacuum mihome-vacuum.0 2021-06-07 10:11:10.583 debug (17421) Time difference between Mihome Vacuum and ioBroker: -1623027974 sec mihome-vacuum.0 2021-06-07 10:11:10.582 debug (17421) Receive <<< Helo <<< 213100200000000018cf43ce00006398ffffffffffffffffffffffffffffffff mihome-vacuum.0 2021-06-07 10:11:00.533 debug (17421) Helo message Timeout mihome-vacuum.0 2021-06-07 10:10:58.811 debug (17421) MIIO Receive Timeout<<< mihome-vacuum.0 2021-06-07 10:10:56.809 debug (17421) Message= {"id":322,"method":"get_carpet_mode"} mihome-vacuum.0 2021-06-07 10:10:56.809 debug (17421) ERROR at setGetSoundVolume: MESSAGE TIMEOUT mihome-vacuum.0 2021-06-07 10:10:56.807 debug (17421) MIIO Receive Timeout<<< mihome-vacuum.0 2021-06-07 10:10:54.805 debug (17421) Message= {"id":321,"method":"get_sound_volume"} mihome-vacuum.0 2021-06-07 10:10:54.797 debug (17421) MIIO RECIVE: {"id":320,"result":{"ssid":"Familie-Gerndt","ip":"192.168.178.70","mac":"b0:4a:39:15:75:03","bssid":"2c:91:ab:a5:2f:9a","rssi":-52},"exe_time":101} mihome-vacuum.0 2021-06-07 10:10:53.045 debug (17421) Message= {"id":320,"method":"get_network_info"} mihome-vacuum.0 2021-06-07 10:10:53.043 debug (17421) setGetStatus {"msg_ver":2,"msg_seq":607,"state":8,"battery":89,"clean_time":2399,"clean_area":30630000,"error_code":0,"map_present":true,"in_cleaning":false,"in_returning":0,"in_fresh_state":1 mihome-vacuum.0 2021-06-07 10:10:53.030 debug (17421) MIIO RECIVE: {"id":319,"result":[{"msg_ver":2,"msg_seq":607,"state":8,"battery":89,"clean_time":2399,"clean_area":30630000,"error_code":0,"map_present":1,"in_cleaning":0,"in_returning":0,"in_f mihome-vacuum.0 2021-06-07 10:10:52.839 debug (17421) Message= {"id":319,"method":"get_status"} mihome-vacuum.0 2021-06-07 10:10:52.838 debug (17421) get params for stock VacuumEs kommt also ständig ein Timeout und das es eine Zeitdifferenz gibt. Kann man da was dagegen tun?
Danke und Grüße
Ronny
-
hat irgendwer die 3.2.0 Version mit einem S5 am Laufen? Ich habe ihn nicht zum Laufen bekommen hinsichtlich "load rooms" - zurück auf 2.5.5 funktioniert wieder alles einwandfrei.
Im debug protokoll ist mir aufgefallen, dass er bei 3.2.0 irgendwas mit "unknown device model" sagte...und Frage 2: funktioniert beim S5 die Detektion der Wischeinheit? bei mir bleibt der "water_box" Datenpunkt immer auf false - mag aber sein, dass das der S5 das gar nicht kann.
-
Hi,
hab seit letzter Wochen einen Roborock S7 und wollte den mit iobroker verbinden.
Die Verbindung bekomme ich soweit auch hin. Token usw. hat geklappt.
Ich habe Version 3.20 am laufen und bekomme in endlosschleife diese Log Ausgaben.mihome-vacuum.0 2021-06-07 10:11:32.591 debug (17421) Helo message Timeout mihome-vacuum.0 2021-06-07 10:11:20.589 debug (17421) Time difference between Mihome Vacuum and ioBroker: -1623027974 sec mihome-vacuum.0 2021-06-07 10:11:20.588 debug (17421) Receive <<< Helo <<< 213100200000000018cf43ce000063a2ffffffffffffffffffffffffffffffff mihome-vacuum.0 2021-06-07 10:11:19.784 debug (17421) MIIO RECIVE: {"id":326,"result":[{"enable":1,"current_integral":450,"current_high":500,"current_low":400,"stall_time":10}],"exe_time":100} mihome-vacuum.0 2021-06-07 10:11:19.576 debug (17421) Message= {"id":326,"method":"get_carpet_mode"} mihome-vacuum.0 2021-06-07 10:11:19.575 debug (17421) MIIO RECIVE: {"id":325,"result":[90],"exe_time":200} mihome-vacuum.0 2021-06-07 10:11:19.285 debug (17421) Message= {"id":325,"method":"get_sound_volume"} mihome-vacuum.0 2021-06-07 10:11:19.274 debug (17421) MIIO RECIVE: {"id":324,"result":{"ssid":"Familie-Gerndt","ip":"192.168.178.70","mac":"b0:4a:39:15:75:03","bssid":"2c:91:ab:a5:2f:9a","rssi":-47},"exe_time":100} mihome-vacuum.0 2021-06-07 10:11:19.085 debug (17421) Message= {"id":324,"method":"get_network_info"} mihome-vacuum.0 2021-06-07 10:11:19.083 debug (17421) setGetStatus {"msg_ver":2,"msg_seq":609,"state":8,"battery":90,"clean_time":2399,"clean_area":30630000,"error_code":0,"map_present":true,"in_cleaning":false,"in_returning":0,"in_fresh_state":1 mihome-vacuum.0 2021-06-07 10:11:19.082 debug (17421) MIIO RECIVE: {"id":323,"result":[{"msg_ver":2,"msg_seq":609,"state":8,"battery":90,"clean_time":2399,"clean_area":30630000,"error_code":0,"map_present":1,"in_cleaning":0,"in_returning":0,"in_f mihome-vacuum.0 2021-06-07 10:11:18.814 debug (17421) Message= {"id":323,"method":"get_status"} mihome-vacuum.0 2021-06-07 10:11:18.813 debug (17421) get params for stock Vacuum mihome-vacuum.0 2021-06-07 10:11:10.583 debug (17421) Time difference between Mihome Vacuum and ioBroker: -1623027974 sec mihome-vacuum.0 2021-06-07 10:11:10.582 debug (17421) Receive <<< Helo <<< 213100200000000018cf43ce00006398ffffffffffffffffffffffffffffffff mihome-vacuum.0 2021-06-07 10:11:00.533 debug (17421) Helo message Timeout mihome-vacuum.0 2021-06-07 10:10:58.811 debug (17421) MIIO Receive Timeout<<< mihome-vacuum.0 2021-06-07 10:10:56.809 debug (17421) Message= {"id":322,"method":"get_carpet_mode"} mihome-vacuum.0 2021-06-07 10:10:56.809 debug (17421) ERROR at setGetSoundVolume: MESSAGE TIMEOUT mihome-vacuum.0 2021-06-07 10:10:56.807 debug (17421) MIIO Receive Timeout<<< mihome-vacuum.0 2021-06-07 10:10:54.805 debug (17421) Message= {"id":321,"method":"get_sound_volume"} mihome-vacuum.0 2021-06-07 10:10:54.797 debug (17421) MIIO RECIVE: {"id":320,"result":{"ssid":"Familie-Gerndt","ip":"192.168.178.70","mac":"b0:4a:39:15:75:03","bssid":"2c:91:ab:a5:2f:9a","rssi":-52},"exe_time":101} mihome-vacuum.0 2021-06-07 10:10:53.045 debug (17421) Message= {"id":320,"method":"get_network_info"} mihome-vacuum.0 2021-06-07 10:10:53.043 debug (17421) setGetStatus {"msg_ver":2,"msg_seq":607,"state":8,"battery":89,"clean_time":2399,"clean_area":30630000,"error_code":0,"map_present":true,"in_cleaning":false,"in_returning":0,"in_fresh_state":1 mihome-vacuum.0 2021-06-07 10:10:53.030 debug (17421) MIIO RECIVE: {"id":319,"result":[{"msg_ver":2,"msg_seq":607,"state":8,"battery":89,"clean_time":2399,"clean_area":30630000,"error_code":0,"map_present":1,"in_cleaning":0,"in_returning":0,"in_f mihome-vacuum.0 2021-06-07 10:10:52.839 debug (17421) Message= {"id":319,"method":"get_status"} mihome-vacuum.0 2021-06-07 10:10:52.838 debug (17421) get params for stock VacuumEs kommt also ständig ein Timeout und das es eine Zeitdifferenz gibt. Kann man da was dagegen tun?
Danke und Grüße
Ronny
@ronny-gerndt
Hast du den Sauger mal in einer der Apps mihome oder roborock konfiguriert? -
@ronny-gerndt
Hast du den Sauger mal in einer der Apps mihome oder roborock konfiguriert?@thomas-braun said in Test Adapter Mihome-vacuum v3.1.6 Next Generarition:
@ronny-gerndt
Hast du den Sauger mal in einer der Apps mihome oder roborock konfiguriert?Ja klar. Hatte erst die Roborock drauf und bin dann auf MiHome gewechselt. Da funzt auch alles.
Die Anbindung funktioniert inzwischen auch grundsätzlich. Mir fehlt noch die Raumliste. Die wird immer als leer angezeigt.
-
Ich habe über die 2.1.1 die 3.2.0 installiert (update über Admin Oberfläche).
Bei GetDevices bekomme ich permanent einen Error: LOG IN FAILED.
Runter auf die 2.1.1 geht wieder alles (bis auf die Karte, deswegen wollte ich updaten)
Ist ein Robo S5 2.GEN.
(ich habe noch einen V1 deswegen die 1. Instanz zusätzlich)mihome-vacuum.0 2021-06-13 13:50:46.231 info (8576) create state for carpet_mode mihome-vacuum.0 2021-06-13 13:50:45.416 info (8576) create states for water box mihome-vacuum.0 2021-06-13 13:50:45.375 info (8576) change states from State control.fan_power mihome-vacuum.0 2021-06-13 13:50:45.258 info (8576) Map selected create states... mihome-vacuum.1 2021-06-13 13:50:44.889 info (8582) create state for carpet_mode mihome-vacuum.0 2021-06-13 13:50:44.873 warn (8576) Login failed mihome-vacuum.1 2021-06-13 13:50:44.421 info (8582) Map selected create states... mihome-vacuum.1 2021-06-13 13:50:44.191 warn (8582) Login failed mihome-vacuum.0 2021-06-13 13:50:43.462 info (8576) settest next timer: not available mihome-vacuum.0 2021-06-13 13:50:42.897 info (8576) select standard vacuum protocol.... mihome-vacuum.0 2021-06-13 13:50:42.853 info (8576) IOT disabled, delete state mihome-vacuum.1 2021-06-13 13:50:42.777 info (8582) settest next timer: not available mihome-vacuum.0 2021-06-13 13:50:42.683 info (8576) check group user admin group admin: false mihome-vacuum.0 2021-06-13 13:50:42.626 info (8576) check user admin pw iobroker: true mihome-vacuum.0 2021-06-13 13:50:42.166 info (8576) starting. Version 3.2.0 in /opt/iobroker/node_modules/iobroker.mihome-vacuum, node: v12.22.1, js-controller: 3.2.16 mihome-vacuum.1 2021-06-13 13:50:42.152 info (8582) select standard vacuum protocol.... mihome-vacuum.1 2021-06-13 13:50:42.124 info (8582) IOT disabled, delete state mihome-vacuum.0 2021-06-13 13:50:42.012 info (8576) Plugin sentry Sentry Plugin disabled for this process because sending of statistic data is disabled for the system mihome-vacuum.1 2021-06-13 13:50:41.881 info (8582) check group user admin group admin: false mihome-vacuum.1 2021-06-13 13:50:41.765 info (8582) check user admin pw iobroker: true mihome-vacuum.1 2021-06-13 13:50:41.285 info (8582) starting. Version 3.2.0 in /opt/iobroker/node_modules/iobroker.mihome-vacuum, node: v12.22.1, js-controller: 3.2.16 mihome-vacuum.1 2021-06-13 13:50:41.174 info (8582) Plugin sentry Sentry Plugin disabled for this process because sending of statistic data is disabled for the systemSynology DS218+ & 2 x Fujitsu Esprimo (VM/Container) + FritzBox7590 + 2 AVM 3000 Repeater & Homematic & HUE & Osram & Xiaomi, NPM 10.9.4, Nodejs 22.21.0 ,JS Controller 7.0.7 ,Admin 7.7.19
-
Ich habe über die 2.1.1 die 3.2.0 installiert (update über Admin Oberfläche).
Bei GetDevices bekomme ich permanent einen Error: LOG IN FAILED.
Runter auf die 2.1.1 geht wieder alles (bis auf die Karte, deswegen wollte ich updaten)
Ist ein Robo S5 2.GEN.
(ich habe noch einen V1 deswegen die 1. Instanz zusätzlich)mihome-vacuum.0 2021-06-13 13:50:46.231 info (8576) create state for carpet_mode mihome-vacuum.0 2021-06-13 13:50:45.416 info (8576) create states for water box mihome-vacuum.0 2021-06-13 13:50:45.375 info (8576) change states from State control.fan_power mihome-vacuum.0 2021-06-13 13:50:45.258 info (8576) Map selected create states... mihome-vacuum.1 2021-06-13 13:50:44.889 info (8582) create state for carpet_mode mihome-vacuum.0 2021-06-13 13:50:44.873 warn (8576) Login failed mihome-vacuum.1 2021-06-13 13:50:44.421 info (8582) Map selected create states... mihome-vacuum.1 2021-06-13 13:50:44.191 warn (8582) Login failed mihome-vacuum.0 2021-06-13 13:50:43.462 info (8576) settest next timer: not available mihome-vacuum.0 2021-06-13 13:50:42.897 info (8576) select standard vacuum protocol.... mihome-vacuum.0 2021-06-13 13:50:42.853 info (8576) IOT disabled, delete state mihome-vacuum.1 2021-06-13 13:50:42.777 info (8582) settest next timer: not available mihome-vacuum.0 2021-06-13 13:50:42.683 info (8576) check group user admin group admin: false mihome-vacuum.0 2021-06-13 13:50:42.626 info (8576) check user admin pw iobroker: true mihome-vacuum.0 2021-06-13 13:50:42.166 info (8576) starting. Version 3.2.0 in /opt/iobroker/node_modules/iobroker.mihome-vacuum, node: v12.22.1, js-controller: 3.2.16 mihome-vacuum.1 2021-06-13 13:50:42.152 info (8582) select standard vacuum protocol.... mihome-vacuum.1 2021-06-13 13:50:42.124 info (8582) IOT disabled, delete state mihome-vacuum.0 2021-06-13 13:50:42.012 info (8576) Plugin sentry Sentry Plugin disabled for this process because sending of statistic data is disabled for the system mihome-vacuum.1 2021-06-13 13:50:41.881 info (8582) check group user admin group admin: false mihome-vacuum.1 2021-06-13 13:50:41.765 info (8582) check user admin pw iobroker: true mihome-vacuum.1 2021-06-13 13:50:41.285 info (8582) starting. Version 3.2.0 in /opt/iobroker/node_modules/iobroker.mihome-vacuum, node: v12.22.1, js-controller: 3.2.16 mihome-vacuum.1 2021-06-13 13:50:41.174 info (8582) Plugin sentry Sentry Plugin disabled for this process because sending of statistic data is disabled for the system@haselchen du musst das passwort neu eingeben. Steht auch im changelog
-
@haselchen du musst das passwort neu eingeben. Steht auch im changelog
Als wenn ich das nicht nach so einer Meldung machen würde ;)
Ergebnis blieb und bleibt das Gleiche.
Warum bekomme ich mit der 2.1.1 eigentlich die Map nicht mehr angezeigt bzw. ausgelesen?
-
@haselchen du musst das passwort neu eingeben. Steht auch im changelog
@meistertr konntest du dir meinen log schon ansehen ? Sind noch immer keine Räume da 😔
-
@haselchen du musst das passwort neu eingeben. Steht auch im changelog
Habe alles nochmal neu aufgesetzt in der Mihome App.
Dann nochmal über die 2.1.1 die 3.2.0 installiert.
Hab noch nicht alles getestet, aber Verbindung ist da und die Datenpunkte werden aktualisiert.
Auch von mir ein Danke, dass Du Deine Freizeit diesem Projekt widmest! -
Als wenn ich das nicht nach so einer Meldung machen würde ;)
Ergebnis blieb und bleibt das Gleiche.
Warum bekomme ich mit der 2.1.1 eigentlich die Map nicht mehr angezeigt bzw. ausgelesen?
@haselchen bei map hat sich der Datenpunkt geändert - dennoch hab ich es noch nicht bis ins VIS geschafft - aber die URL konnte ich bereits laden und die Map auch sehen.
das Thema Problem mit den Räumen habe ich auch (siehe ein paar Posts weiter oben). Habe auch den S5 - kann es daran tatsächlich liegen?
VG
-
Soweit läuft alles wieder bei mir.
Durch das drüber installieren sind die alten Einstellungen geblieben.
Map hat er geladen und erscheint auch in der VIS. -
Ich habe jetzt das regelmäßig der Adapter (version 3.2.0) crasht. Weißt du an was das liegen könnte?
Heute:
host.iobroker 2021-06-25 15:13:59.568 error instance system.adapter.mihome-vacuum.0 terminated with code 1 (JS_CONTROLLER_STOPPED) host.iobroker 2021-06-25 15:13:59.567 error Caught by controller[0]: at UDP.onMessage (dgram.js:921:8) host.iobroker 2021-06-25 15:13:59.567 error Caught by controller[0]: at Socket.EventEmitter.emit (domain.js:483:12) host.iobroker 2021-06-25 15:13:59.567 error Caught by controller[0]: at Socket.emit (events.js:326:22) host.iobroker 2021-06-25 15:13:59.567 error Caught by controller[0]: at Socket.checkAnswer (/opt/iobroker/node_modules/iobroker.mihome-vacuum/lib/miio.js:146:62) host.iobroker 2021-06-25 15:13:59.567 error Caught by controller[0]: at _Packet.getPlainData (/opt/iobroker/node_modules/iobroker.mihome-vacuum/lib/miio.js:310:19) host.iobroker 2021-06-25 15:13:59.567 error Caught by controller[0]: at Decipheriv.final (internal/crypto/cipher.js:172:29) host.iobroker 2021-06-25 15:13:59.567 error Caught by controller[0]: at Object.final (<anonymous>) host.iobroker 2021-06-25 15:13:59.565 error Caught by controller[0]: Error: error:06065064:digital envelope routines:EVP_DecryptFinal_ex:bad decrypt mihome-vacuum.0 2021-06-25 15:13:59.281 error (15936) Exception-Code: ERR_OSSL_EVP_BAD_DECRYPT: error:06065064:digital envelope routines:EVP_DecryptFinal_ex:bad decrypt mihome-vacuum.0 2021-06-25 15:13:59.281 error at UDP.onMessage (dgram.js:921:8) mihome-vacuum.0 2021-06-25 15:13:59.281 error at Socket.EventEmitter.emit (domain.js:483:12) mihome-vacuum.0 2021-06-25 15:13:59.281 error at Socket.emit (events.js:326:22) mihome-vacuum.0 2021-06-25 15:13:59.281 error at Socket.checkAnswer (/opt/iobroker/node_modules/iobroker.mihome-vacuum/lib/miio.js:146:62) mihome-vacuum.0 2021-06-25 15:13:59.281 error at _Packet.getPlainData (/opt/iobroker/node_modules/iobroker.mihome-vacuum/lib/miio.js:310:19) mihome-vacuum.0 2021-06-25 15:13:59.281 error at Decipheriv.final (internal/crypto/cipher.js:172:29) mihome-vacuum.0 2021-06-25 15:13:59.281 error at Object.final (<anonymous>) mihome-vacuum.0 2021-06-25 15:13:59.281 error (15936) Error: error:06065064:digital envelope routines:EVP_DecryptFinal_ex:bad decrypt mihome-vacuum.0 2021-06-25 15:13:59.277 error (15936) uncaught exception: error:06065064:digital envelope routines:EVP_DecryptFinal_ex:bad decryptGestern:
2021-06-24 16:30:54.310 - error: mihome-vacuum.0 (10285) Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). 2021-06-24 16:30:54.319 - error: mihome-vacuum.0 (10285) unhandled promise rejection: undefined 2021-06-24 16:30:54.319 - error: mihome-vacuum.0 (10285) undefined 2021-06-24 16:30:54.937 - error: host.iobroker Caught by controller[0]: This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason: 2021-06-24 16:30:54.938 - error: host.iobroker Caught by controller[1]: MESSAGE TIMEOUT 2021-06-24 16:30:54.939 - error: host.iobroker instance system.adapter.mihome-vacuum.0 terminated with code 6 (UNCAUGHT_EXCEPTION)@ all
Habt ihr crashs?
-
Ich habe jetzt das regelmäßig der Adapter (version 3.2.0) crasht. Weißt du an was das liegen könnte?
Heute:
host.iobroker 2021-06-25 15:13:59.568 error instance system.adapter.mihome-vacuum.0 terminated with code 1 (JS_CONTROLLER_STOPPED) host.iobroker 2021-06-25 15:13:59.567 error Caught by controller[0]: at UDP.onMessage (dgram.js:921:8) host.iobroker 2021-06-25 15:13:59.567 error Caught by controller[0]: at Socket.EventEmitter.emit (domain.js:483:12) host.iobroker 2021-06-25 15:13:59.567 error Caught by controller[0]: at Socket.emit (events.js:326:22) host.iobroker 2021-06-25 15:13:59.567 error Caught by controller[0]: at Socket.checkAnswer (/opt/iobroker/node_modules/iobroker.mihome-vacuum/lib/miio.js:146:62) host.iobroker 2021-06-25 15:13:59.567 error Caught by controller[0]: at _Packet.getPlainData (/opt/iobroker/node_modules/iobroker.mihome-vacuum/lib/miio.js:310:19) host.iobroker 2021-06-25 15:13:59.567 error Caught by controller[0]: at Decipheriv.final (internal/crypto/cipher.js:172:29) host.iobroker 2021-06-25 15:13:59.567 error Caught by controller[0]: at Object.final (<anonymous>) host.iobroker 2021-06-25 15:13:59.565 error Caught by controller[0]: Error: error:06065064:digital envelope routines:EVP_DecryptFinal_ex:bad decrypt mihome-vacuum.0 2021-06-25 15:13:59.281 error (15936) Exception-Code: ERR_OSSL_EVP_BAD_DECRYPT: error:06065064:digital envelope routines:EVP_DecryptFinal_ex:bad decrypt mihome-vacuum.0 2021-06-25 15:13:59.281 error at UDP.onMessage (dgram.js:921:8) mihome-vacuum.0 2021-06-25 15:13:59.281 error at Socket.EventEmitter.emit (domain.js:483:12) mihome-vacuum.0 2021-06-25 15:13:59.281 error at Socket.emit (events.js:326:22) mihome-vacuum.0 2021-06-25 15:13:59.281 error at Socket.checkAnswer (/opt/iobroker/node_modules/iobroker.mihome-vacuum/lib/miio.js:146:62) mihome-vacuum.0 2021-06-25 15:13:59.281 error at _Packet.getPlainData (/opt/iobroker/node_modules/iobroker.mihome-vacuum/lib/miio.js:310:19) mihome-vacuum.0 2021-06-25 15:13:59.281 error at Decipheriv.final (internal/crypto/cipher.js:172:29) mihome-vacuum.0 2021-06-25 15:13:59.281 error at Object.final (<anonymous>) mihome-vacuum.0 2021-06-25 15:13:59.281 error (15936) Error: error:06065064:digital envelope routines:EVP_DecryptFinal_ex:bad decrypt mihome-vacuum.0 2021-06-25 15:13:59.277 error (15936) uncaught exception: error:06065064:digital envelope routines:EVP_DecryptFinal_ex:bad decryptGestern:
2021-06-24 16:30:54.310 - error: mihome-vacuum.0 (10285) Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). 2021-06-24 16:30:54.319 - error: mihome-vacuum.0 (10285) unhandled promise rejection: undefined 2021-06-24 16:30:54.319 - error: mihome-vacuum.0 (10285) undefined 2021-06-24 16:30:54.937 - error: host.iobroker Caught by controller[0]: This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason: 2021-06-24 16:30:54.938 - error: host.iobroker Caught by controller[1]: MESSAGE TIMEOUT 2021-06-24 16:30:54.939 - error: host.iobroker instance system.adapter.mihome-vacuum.0 terminated with code 6 (UNCAUGHT_EXCEPTION)@ all
Habt ihr crashs?
@saeft_2003 Hier crasht nix.
Wann passiert es denn bei dir? Wenn der Roboter aktiv ist?
-
@saeft_2003 Hier crasht nix.
Wann passiert es denn bei dir? Wenn der Roboter aktiv ist?
Ja nur wenn er aktiv ist sonst nicht.
-
@saeft_2003 Hier crasht nix.
Wann passiert es denn bei dir? Wenn der Roboter aktiv ist?
Gerade war er aktiv und es gab wieder einen crash. Ich kann mir nicht erklären an was das liegt?
host.iobroker 2021-06-29 08:44:16.591 error instance system.adapter.mihome-vacuum.0 terminated with code 1 (JS_CONTROLLER_STOPPED) host.iobroker 2021-06-29 08:44:16.591 error Caught by controller[0]: at UDP.onMessage (dgram.js:921:8) host.iobroker 2021-06-29 08:44:16.591 error Caught by controller[0]: at Socket.EventEmitter.emit (domain.js:483:12) host.iobroker 2021-06-29 08:44:16.591 error Caught by controller[0]: at Socket.emit (events.js:326:22) host.iobroker 2021-06-29 08:44:16.590 error Caught by controller[0]: at Socket.checkAnswer (/opt/iobroker/node_modules/iobroker.mihome-vacuum/lib/miio.js:146:62) host.iobroker 2021-06-29 08:44:16.590 error Caught by controller[0]: at _Packet.getPlainData (/opt/iobroker/node_modules/iobroker.mihome-vacuum/lib/miio.js:310:19) host.iobroker 2021-06-29 08:44:16.590 error Caught by controller[0]: at Decipheriv.final (internal/crypto/cipher.js:172:29) host.iobroker 2021-06-29 08:44:16.590 error Caught by controller[0]: at Object.final (<anonymous>) host.iobroker 2021-06-29 08:44:16.588 error Caught by controller[0]: Error: error:06065064:digital envelope routines:EVP_DecryptFinal_ex:bad decrypt mihome-vacuum.0 2021-06-29 08:44:16.287 error (27481) Exception-Code: ERR_OSSL_EVP_BAD_DECRYPT: error:06065064:digital envelope routines:EVP_DecryptFinal_ex:bad decrypt mihome-vacuum.0 2021-06-29 08:44:16.287 error at UDP.onMessage (dgram.js:921:8) mihome-vacuum.0 2021-06-29 08:44:16.287 error at Socket.EventEmitter.emit (domain.js:483:12) mihome-vacuum.0 2021-06-29 08:44:16.287 error at Socket.emit (events.js:326:22) mihome-vacuum.0 2021-06-29 08:44:16.287 error at Socket.checkAnswer (/opt/iobroker/node_modules/iobroker.mihome-vacuum/lib/miio.js:146:62) mihome-vacuum.0 2021-06-29 08:44:16.287 error at _Packet.getPlainData (/opt/iobroker/node_modules/iobroker.mihome-vacuum/lib/miio.js:310:19) mihome-vacuum.0 2021-06-29 08:44:16.287 error at Decipheriv.final (internal/crypto/cipher.js:172:29) mihome-vacuum.0 2021-06-29 08:44:16.287 error at Object.final (<anonymous>) mihome-vacuum.0 2021-06-29 08:44:16.287 error (27481) Error: error:06065064:digital envelope routines:EVP_DecryptFinal_ex:bad decrypt mihome-vacuum.0 2021-06-29 08:44:16.284 error (27481) uncaught exception: error:06065064:digital envelope routines:EVP_DecryptFinal_ex:bad decrypt -
Gerade war er aktiv und es gab wieder einen crash. Ich kann mir nicht erklären an was das liegt?
host.iobroker 2021-06-29 08:44:16.591 error instance system.adapter.mihome-vacuum.0 terminated with code 1 (JS_CONTROLLER_STOPPED) host.iobroker 2021-06-29 08:44:16.591 error Caught by controller[0]: at UDP.onMessage (dgram.js:921:8) host.iobroker 2021-06-29 08:44:16.591 error Caught by controller[0]: at Socket.EventEmitter.emit (domain.js:483:12) host.iobroker 2021-06-29 08:44:16.591 error Caught by controller[0]: at Socket.emit (events.js:326:22) host.iobroker 2021-06-29 08:44:16.590 error Caught by controller[0]: at Socket.checkAnswer (/opt/iobroker/node_modules/iobroker.mihome-vacuum/lib/miio.js:146:62) host.iobroker 2021-06-29 08:44:16.590 error Caught by controller[0]: at _Packet.getPlainData (/opt/iobroker/node_modules/iobroker.mihome-vacuum/lib/miio.js:310:19) host.iobroker 2021-06-29 08:44:16.590 error Caught by controller[0]: at Decipheriv.final (internal/crypto/cipher.js:172:29) host.iobroker 2021-06-29 08:44:16.590 error Caught by controller[0]: at Object.final (<anonymous>) host.iobroker 2021-06-29 08:44:16.588 error Caught by controller[0]: Error: error:06065064:digital envelope routines:EVP_DecryptFinal_ex:bad decrypt mihome-vacuum.0 2021-06-29 08:44:16.287 error (27481) Exception-Code: ERR_OSSL_EVP_BAD_DECRYPT: error:06065064:digital envelope routines:EVP_DecryptFinal_ex:bad decrypt mihome-vacuum.0 2021-06-29 08:44:16.287 error at UDP.onMessage (dgram.js:921:8) mihome-vacuum.0 2021-06-29 08:44:16.287 error at Socket.EventEmitter.emit (domain.js:483:12) mihome-vacuum.0 2021-06-29 08:44:16.287 error at Socket.emit (events.js:326:22) mihome-vacuum.0 2021-06-29 08:44:16.287 error at Socket.checkAnswer (/opt/iobroker/node_modules/iobroker.mihome-vacuum/lib/miio.js:146:62) mihome-vacuum.0 2021-06-29 08:44:16.287 error at _Packet.getPlainData (/opt/iobroker/node_modules/iobroker.mihome-vacuum/lib/miio.js:310:19) mihome-vacuum.0 2021-06-29 08:44:16.287 error at Decipheriv.final (internal/crypto/cipher.js:172:29) mihome-vacuum.0 2021-06-29 08:44:16.287 error at Object.final (<anonymous>) mihome-vacuum.0 2021-06-29 08:44:16.287 error (27481) Error: error:06065064:digital envelope routines:EVP_DecryptFinal_ex:bad decrypt mihome-vacuum.0 2021-06-29 08:44:16.284 error (27481) uncaught exception: error:06065064:digital envelope routines:EVP_DecryptFinal_ex:bad decrypt@saeft_2003 sagte in Test Adapter Mihome-vacuum v3.1.6 Next Generarition:
ERR_OSSL_EVP_BAD_DECRYPT
Da gibt es wohl Probleme mit der Entschlüsselung eines Passwortes.
Hast du da 'Sonderzeichen' drin oder ist das besonders lang?
Änder das mal zum testen auf was simpleres. -
@saeft_2003 sagte in Test Adapter Mihome-vacuum v3.1.6 Next Generarition:
ERR_OSSL_EVP_BAD_DECRYPT
Da gibt es wohl Probleme mit der Entschlüsselung eines Passwortes.
Hast du da 'Sonderzeichen' drin oder ist das besonders lang?
Änder das mal zum testen auf was simpleres.Danke für die Info. Das Passwort sollte eigentlich recht simpel sein. Besteht aus 8 Zeichen und das sind nur normale Buchstaben und Zahlen.
Würde es testweise Sinn machen den Adapter mal auf einem anderen Host laufen zu lassen?
Support us
819
Online32.4k
Benutzer81.5k
Themen1.3m
Beiträge