Adapter MiHome ständiger Neustart
-
Hallo zusammen,
Mein MiHome Adapter startet ständig neu.
Wenn ich die Log richtig lese, dann gibt es Verbindungsprobleme (?), aber vom Handy gibt es keine Probleme und auch nicht die Sensoren dahinter auslesen macht keine Probleme. Hat jemand eine Idee?
Hier der Log Eintrag:mihome.0 2019-06-11 11:27:36.552 info starting. Version 1.2.6 in /opt/iobroker/node_modules/iobroker.mihome, node: v8.15.1 host.raspberrypi 2019-06-11 11:27:33.803 info instance system.adapter.mihome.0 started with pid 16268 host.raspberrypi 2019-06-11 11:27:32.786 info Restart adapter system.adapter.mihome.0 because enabled host.raspberrypi 2019-06-11 11:27:32.785 error instance system.adapter.mihome.0 terminated with code 0 (OK) Caught 2019-06-11 11:27:32.785 error by controller[0]: at Timer.listOnTimeout (timers.js:290:5) Caught 2019-06-11 11:27:32.785 error by controller[0]: at tryOnTimeout (timers.js:323:5) Caught 2019-06-11 11:27:32.785 error by controller[0]: at ontimeout (timers.js:498:11) Caught 2019-06-11 11:27:32.784 error by controller[0]: at Timeout.timer.setTimeout [as _onTimeout] (/opt/iobroker/node_modules/iobroker.mihome/lib/Sensors/Gateway.js:193:36) Caught 2019-06-11 11:27:32.784 error by controller[0]: at Hub.getKey (/opt/iobroker/node_modules/iobroker.mihome/lib/Hub.js:144:31) Caught 2019-06-11 11:27:32.783 error by controller[0]: at Object.createCipheriv (crypto.js:619:10) Caught 2019-06-11 11:27:32.763 error by controller[0]: at new Cipheriv (crypto.js:219:16) Caught 2019-06-11 11:27:32.762 error by controller[0]: Error: Invalid key length mihome.0 2019-06-11 11:27:32.740 info terminating mihome.0 2019-06-11 11:27:32.692 error at Timer.listOnTimeout (timers.js:290:5) mihome.0 2019-06-11 11:27:32.692 error at tryOnTimeout (timers.js:323:5) mihome.0 2019-06-11 11:27:32.692 error at ontimeout (timers.js:498:11) mihome.0 2019-06-11 11:27:32.692 error at Timeout.timer.setTimeout [as _onTimeout] (/opt/iobroker/node_modules/iobroker.mihome/lib/Sensors/Gateway.js:193:36) mihome.0 2019-06-11 11:27:32.692 error at Hub.getKey (/opt/iobroker/node_modules/iobroker.mihome/lib/Hub.js:144:31) mihome.0 2019-06-11 11:27:32.692 error at Object.createCipheriv (crypto.js:619:10) mihome.0 2019-06-11 11:27:32.692 error at new Cipheriv (crypto.js:219:16) mihome.0 2019-06-11 11:27:32.692 error Error: Invalid key length mihome.0 2019-06-11 11:27:32.689 error uncaught exception: Invalid key length mihome.0 2019-06-11 11:25:06.325 info Change connection status: true mihome.0 2019-06-11 11:25:06.227 info Change connection status: false mihome.0 2019-06-11 11:25:05.615 info starting. Version 1.2.6 in /opt/iobroker/node_modules/iobroker.mihome, node: v8.15.1 host.raspberrypi 2019-06-11 11:25:02.857 info instance system.adapter.mihome.0 started with pid 15671 host.raspberrypi 2019-06-11 11:25:01.839 info Restart adapter system.adapter.mihome.0 because enabledIch hoffe mir kann da wer helfen. Durch den Neustart kann ich keine Befehle an den Gateway senden.
VG
Lindi -
danke für den Hint. Der Key war richtig, aber die IP Adresse hat sich geändert, muss mal schauen wo ich die fix machen kann.
-
Hallo zusammen,
Mein MiHome Adapter startet ständig neu.
Wenn ich die Log richtig lese, dann gibt es Verbindungsprobleme (?), aber vom Handy gibt es keine Probleme und auch nicht die Sensoren dahinter auslesen macht keine Probleme. Hat jemand eine Idee?
Hier der Log Eintrag:mihome.0 2019-06-11 11:27:36.552 info starting. Version 1.2.6 in /opt/iobroker/node_modules/iobroker.mihome, node: v8.15.1 host.raspberrypi 2019-06-11 11:27:33.803 info instance system.adapter.mihome.0 started with pid 16268 host.raspberrypi 2019-06-11 11:27:32.786 info Restart adapter system.adapter.mihome.0 because enabled host.raspberrypi 2019-06-11 11:27:32.785 error instance system.adapter.mihome.0 terminated with code 0 (OK) Caught 2019-06-11 11:27:32.785 error by controller[0]: at Timer.listOnTimeout (timers.js:290:5) Caught 2019-06-11 11:27:32.785 error by controller[0]: at tryOnTimeout (timers.js:323:5) Caught 2019-06-11 11:27:32.785 error by controller[0]: at ontimeout (timers.js:498:11) Caught 2019-06-11 11:27:32.784 error by controller[0]: at Timeout.timer.setTimeout [as _onTimeout] (/opt/iobroker/node_modules/iobroker.mihome/lib/Sensors/Gateway.js:193:36) Caught 2019-06-11 11:27:32.784 error by controller[0]: at Hub.getKey (/opt/iobroker/node_modules/iobroker.mihome/lib/Hub.js:144:31) Caught 2019-06-11 11:27:32.783 error by controller[0]: at Object.createCipheriv (crypto.js:619:10) Caught 2019-06-11 11:27:32.763 error by controller[0]: at new Cipheriv (crypto.js:219:16) Caught 2019-06-11 11:27:32.762 error by controller[0]: Error: Invalid key length mihome.0 2019-06-11 11:27:32.740 info terminating mihome.0 2019-06-11 11:27:32.692 error at Timer.listOnTimeout (timers.js:290:5) mihome.0 2019-06-11 11:27:32.692 error at tryOnTimeout (timers.js:323:5) mihome.0 2019-06-11 11:27:32.692 error at ontimeout (timers.js:498:11) mihome.0 2019-06-11 11:27:32.692 error at Timeout.timer.setTimeout [as _onTimeout] (/opt/iobroker/node_modules/iobroker.mihome/lib/Sensors/Gateway.js:193:36) mihome.0 2019-06-11 11:27:32.692 error at Hub.getKey (/opt/iobroker/node_modules/iobroker.mihome/lib/Hub.js:144:31) mihome.0 2019-06-11 11:27:32.692 error at Object.createCipheriv (crypto.js:619:10) mihome.0 2019-06-11 11:27:32.692 error at new Cipheriv (crypto.js:219:16) mihome.0 2019-06-11 11:27:32.692 error Error: Invalid key length mihome.0 2019-06-11 11:27:32.689 error uncaught exception: Invalid key length mihome.0 2019-06-11 11:25:06.325 info Change connection status: true mihome.0 2019-06-11 11:25:06.227 info Change connection status: false mihome.0 2019-06-11 11:25:05.615 info starting. Version 1.2.6 in /opt/iobroker/node_modules/iobroker.mihome, node: v8.15.1 host.raspberrypi 2019-06-11 11:25:02.857 info instance system.adapter.mihome.0 started with pid 15671 host.raspberrypi 2019-06-11 11:25:01.839 info Restart adapter system.adapter.mihome.0 because enabledIch hoffe mir kann da wer helfen. Durch den Neustart kann ich keine Befehle an den Gateway senden.
VG
Lindi@lindi200000 dein Key richtig eingetragen?
-
danke für den Hint. Der Key war richtig, aber die IP Adresse hat sich geändert, muss mal schauen wo ich die fix machen kann.
Hello! It looks like you're interested in this conversation, but you don't have an account yet.
Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.
With your input, this post could be even better 💗
Register LoginSupport us
469
Online32.7k
Users82.6k
Topics1.3m
Posts