SOLVED Shelly Adapter
-
Mal wieder auf dem Schlauch gestanden.
-
host.raspberrypi 2019-02-12 01:00:11.740 info Restart adapter system.adapter.shelly.0 because enabled
host.raspberrypi 2019-02-12 01:00:11.739 error instance system.adapter.shelly.0 terminated with code 0 (OK)
shelly.0 2019-02-12 01:00:11.686 info Starting shelly.0 in version 2.1.0
shelly.0 2019-02-12 01:00:11.674 info starting. Version 2.1.0 in /opt/iobroker/node_modules/iobroker.shelly, node: v8.15.0
shelly.0 2019-02-12 01:00:11.552 debug statesDB connected
shelly.0 2019-02-12 01:00:11.490 debug objectDB connected
host.raspberrypi 2019-02-12 01:00:10.328 info instance system.adapter.shelly.0 started with pid 5729
host.raspberrypi 2019-02-12 00:59:40.303 info Restart adapter system.adapter.shelly.0 because enabled
host.raspberrypi 2019-02-12 00:59:40.303 error instance system.adapter.shelly.0 terminated with code 0 (OK)
shelly.0 2019-02-12 00:59:40.252 info Starting shelly.0 in version 2.1.0
shelly.0 2019-02-12 00:59:40.242 info starting. Version 2.1.0 in /opt/iobroker/node_modules/iobroker.shelly, node: v8.15.0
shelly.0 2019-02-12 00:59:40.124 debug statesDB connected
shelly.0 2019-02-12 00:59:40.061 debug objectDB connected
host.raspberrypi 2019-02-12 00:59:38.909 info instance system.adapter.shelly.0 started with pid 5707
host.raspberrypi 2019-02-12 00:59:08.878 info Restart adapter system.adapter.shelly.0 because enabled
host.raspberrypi 2019-02-12 00:59:08.878 error instance system.adapter.shelly.0 terminated with code 0 (OK)
shelly.0 2019-02-12 00:59:08.815 info Starting shelly.0 in version 2.1.0
shelly.0 2019-02-12 00:59:08.806 info starting. Version 2.1.0 in /opt/iobroker/node_modules/iobroker.shelly, node: v8.15.0
shelly.0 2019-02-12 00:59:08.688 debug statesDB connected
shelly.0 2019-02-12 00:59:08.623 debug objectDB connected
host.raspberrypi 2019-02-12 00:59:07.436 info instance system.adapter.shelly.0 started with pid 5685
host.raspberrypi 2019-02-12 00:59:04.958 info instance system.adapter.shelly.0 terminated with code 0 (OK)
host.raspberrypi 2019-02-12 00:59:04.894 info stopInstance system.adapter.shelly.0 killing pid 4699
host.raspberrypi 2019-02-12 00:59:04.894 info stopInstance system.adapter.shelly.0 -
@Rocket85 said in Shelly Adapter:
host.raspberrypi 2019-02-12 01:00:11.740 info Restart adapter system.adapter.shelly.0 because enabled
host.raspberrypi 2019-02-12 01:00:11.739 error instance system.adapter.shelly.0 terminated with code 0 (OK)
shelly.0 2019-02-12 01:00:11.686 info Starting shelly.0 in version 2.1.0
shelly.0 2019-02-12 01:00:11.674 info starting. Version 2.1.0 in /opt/iobroker/node_modules/iobroker.shelly, node: v8.15.0
shelly.0 2019-02-12 01:00:11.552 debug statesDB connected
shelly.0 2019-02-12 01:00:11.490 debug objectDB connected
host.raspberrypi 2019-02-12 01:00:10.328 info instance system.adapter.shelly.0 started with pid 5729
host.raspberrypi 2019-02-12 00:59:40.303 info Restart adapter system.adapter.shelly.0 because enabled
host.raspberrypi 2019-02-12 00:59:40.303 error instance system.adapter.shelly.0 terminated with code 0 (OK)
shelly.0 2019-02-12 00:59:40.252 info Starting shelly.0 in version 2.1.0
shelly.0 2019-02-12 00:59:40.242 info starting. Version 2.1.0 in /opt/iobroker/node_modules/iobroker.shelly, node: v8.15.0
shelly.0 2019-02-12 00:59:40.124 debug statesDB connected
shelly.0 2019-02-12 00:59:40.061 debug objectDB connected
host.raspberrypi 2019-02-12 00:59:38.909 info instance system.adapter.shelly.0 started with pid 5707
host.raspberrypi 2019-02-12 00:59:08.878 info Restart adapter system.adapter.shelly.0 because enabled
host.raspberrypi 2019-02-12 00:59:08.878 error instance system.adapter.shelly.0 terminated with code 0 (OK)
shelly.0 2019-02-12 00:59:08.815 info Starting shelly.0 in version 2.1.0
shelly.0 2019-02-12 00:59:08.806 info starting. Version 2.1.0 in /opt/iobroker/node_modules/iobroker.shelly, node: v8.15.0
shelly.0 2019-02-12 00:59:08.688 debug statesDB connected
shelly.0 2019-02-12 00:59:08.623 debug objectDB connected
host.raspberrypi 2019-02-12 00:59:07.436 info instance system.adapter.shelly.0 started with pid 5685
host.raspberrypi 2019-02-12 00:59:04.958 info instance system.adapter.shelly.0 terminated with code 0 (OK)
host.raspberrypi 2019-02-12 00:59:04.894 info stopInstance system.adapter.shelly.0 killing pid 4699
host.raspberrypi 2019-02-12 00:59:04.894 info stopInstance system.adapter.shelly.0Da werd ich leider nicht schlau drauß, aber irgendwas stimmt mit dem Adapter glaube ich nicht!
-
Drei mal gestopp worden und Du hattest ihn ein mal gestartet?
Ist der Adapter konfigurierbar und Du hast ihn richtig konfiguriert?
Leichtet die Ampel vor der Instanz immer grün?
-
Ich hab leider nichts gemacht, kam alles automatisch. Ich habe lediglich einmal versucht einen Shelly von fals auf true zu schalten
-
@Stabilostick said in Shelly Adapter:
Drei mal gestopp worden und Du hattest ihn ein mal gestartet?
Ist der Adapter konfigurierbar und Du hast ihn richtig konfiguriert?
Leichtet die Ampel vor der Instanz immer grün?
Normal schon.
Hab jetzt mal komplett gelöscht und neu installiert. Bis jetzt ist er noch nicht grün
host.raspberrypi 2019-02-12 01:05:17.769 info Restart adapter system.adapter.shelly.0 because enabled
host.raspberrypi 2019-02-12 01:05:17.766 error instance system.adapter.shelly.0 terminated with code 0 (OK)
host.raspberrypi 2019-02-12 01:05:16.336 info instance system.adapter.shelly.0 started with pid 6050
host.raspberrypi 2019-02-12 01:05:16.308 info object change system.adapter.shelly.0
host.raspberrypi 2019-02-12 01:04:47.951 info Restart adapter system.adapter.shelly.0 because enabled
host.raspberrypi 2019-02-12 01:04:47.950 error instance system.adapter.shelly.0 terminated with code 0 (OK)
shelly.0 2019-02-12 01:04:47.897 info Starting shelly.0 in version 2.1.0
shelly.0 2019-02-12 01:04:47.887 info starting. Version 2.1.0 in /opt/iobroker/node_modules/iobroker.shelly, node: v8.15.0
shelly.0 2019-02-12 01:04:47.771 debug statesDB connected
shelly.0 2019-02-12 01:04:47.700 debug objectDB connected
host.raspberrypi 2019-02-12 01:04:46.520 info instance system.adapter.shelly.0 started with pid 6027
host.raspberrypi 2019-02-12 01:04:46.492 info object change system.adapter.shelly.0
host.raspberrypi 2019-02-12 01:04:39.260 info Restart adapter system.adapter.shelly.0 because enabled
host.raspberrypi 2019-02-12 01:04:39.259 error instance system.adapter.shelly.0 terminated with code 0 (OK)
shelly.0 2019-02-12 01:04:39.205 info Starting shelly.0 in version 2.1.0
shelly.0 2019-02-12 01:04:39.193 info starting. Version 2.1.0 in /opt/iobroker/node_modules/iobroker.shelly, node: v8.15.0
shelly.0 2019-02-12 01:04:39.074 debug statesDB connected
shelly.0 2019-02-12 01:04:39.010 debug objectDB connected -
geht leider immer in Dauerschleife so weiter!
host.raspberrypi 2019-02-12 01:08:13.531 info Restart adapter system.adapter.shelly.0 because enabled
host.raspberrypi 2019-02-12 01:08:13.531 error instance system.adapter.shelly.0 terminated with code 0 (OK)
shelly.0 2019-02-12 01:08:13.471 info Starting shelly.0 in version 2.1.0
shelly.0 2019-02-12 01:08:13.456 info starting. Version 2.1.0 in /opt/iobroker/node_modules/iobroker.shelly, node: v8.15.0
shelly.0 2019-02-12 01:08:13.328 debug statesDB connected
shelly.0 2019-02-12 01:08:13.264 debug objectDB connected -
Jetzt wird der Shelly Adapter leider nicht mehr grün
-
Kannst Du bitte das in dem folgendem Posting beschriebene ausprobieren und das Ergebnis hier posten?
https://forum.iobroker.net/topic/18687/shelly-adapter-funktioniert-nicht-error-log/2
-
Anbei das Ergebnis. Schon mal vielen DANK für deine Mühe.
starting. Version 2.1.0 in /opt/iobroker/node_modules/iobroker.shelly, node: v8.15.0
Starting shelly.0 in version 2.1.0
Exception: TypeError: xmlserializer.Builder is not a constructor/TypeError: xmlserializer.Builder is not a constructor
Exception: TypeError: xmlserializer.Builder is not a constructor -
Kannst Du bitte den Shelly-Adapter mit der zugehörigen Instanz noch einmal löschen, wieder installieren und das Log der Installation hier posten (wenn er wieder nicht grün wird)?
-
$ ./iobroker add shelly --host raspberrypi host.raspberrypi create instance shelly host.raspberrypi object shelly.0.info.connection created host.raspberrypi object shelly.0.info created host.raspberrypi object system.adapter.shelly.0.outputCount created host.raspberrypi object system.adapter.shelly.0.inputCount created host.raspberrypi object system.adapter.shelly.0.uptime created host.raspberrypi object system.adapter.shelly.0.memRss created host.raspberrypi object system.adapter.shelly.0.memHeapTotal created host.raspberrypi object system.adapter.shelly.0.memHeapUsed created host.raspberrypi object system.adapter.shelly.0.connected created host.raspberrypi object system.adapter.shelly.0.alive created host.raspberrypi object system.adapter.shelly.0 created process exited with code 0 -
Kann es sein, dass Du nur die Instanz aber nicht den Adapter gelöscht hast?
-
Eigentlich habe ich den Adapter gelöscht, allerdings habe ich eben mal den Haken bei - schließen wenn fertig - weg gemacht und da ist mir etwas aufgefallen.
$ ./iobroker del shelly Delete adapter "shelly" host.raspberrypi no instances of adapter shelly found npm uninstall iobroker.shelly --silent --save --prefix "/opt/iobroker" (System call) ERROR: Error deleting adapter shelly from disk: Error: host.raspberrypi: Cannot uninstall iobroker.shelly: 243 ERROR: You might have to delete it yourself! process exited with code 0 -
Vorschlag:
-
Beende iobroker mit
iobroker stopausgeführt im iobroker-Ordner.
-
Lösche manuell den node_modules/iobroker.shelly-Ordner (habe ich aus dem Gedächtnis so geschrieben)
Dann wieder den ioBroker starten.
-
-
Rückmeldung:
rm: das entfernen von ´node_modules/iobroker.shelly´ ist nicht möglich. Keine Berechtigung -
Dann mit etwas mehr Rechten. Stelle bitte den Befehl „sudo“ vor Deinen rm-Befehl
-
Hab ich schon gemacht. DANKE....Moment Shelly ist weg, ich installiere neu!
-
So langsam fehlen mir die Worte. Anbei das Log der Neuinstallation. Leider immer noch auf ROT.
$ ./iobroker add shelly --host raspberrypi NPM version: 6.5.0 npm install iobroker.shelly --production --save --prefix "/opt/iobroker" (System call) host.raspberrypi install adapter shelly got /opt/iobroker/node_modules/iobroker.shelly/admin upload [2] shelly.admin /opt/iobroker/node_modules/iobroker.shelly/admin/words.js words.js application/javascript upload [1] shelly.admin /opt/iobroker/node_modules/iobroker.shelly/admin/shelly.png shelly.png image/png upload [0] shelly.admin /opt/iobroker/node_modules/iobroker.shelly/admin/index_m.html index_m.html text/html host.raspberrypi object system.adapter.shelly created host.raspberrypi create instance shelly host.raspberrypi object shelly.0.info.connection created host.raspberrypi object shelly.0.info created host.raspberrypi object system.adapter.shelly.0.outputCount created host.raspberrypi object system.adapter.shelly.0.inputCount created host.raspberrypi object system.adapter.shelly.0.uptime created host.raspberrypi object system.adapter.shelly.0.memRss created host.raspberrypi object system.adapter.shelly.0.memHeapTotal created host.raspberrypi object system.adapter.shelly.0.memHeapUsed created host.raspberrypi object system.adapter.shelly.0.connected created host.raspberrypi object system.adapter.shelly.0.alive created host.raspberrypi object system.adapter.shelly.0 created process exited with code 0 -
host.raspberrypi 2019-02-12 16:59:51.548 error instance system.adapter.shelly.0 terminated with code 0 (OK) host.raspberrypi 2019-02-12 16:59:50.074 info instance system.adapter.shelly.0 started with pid 10547 host.raspberrypi 2019-02-12 16:59:50.061 info object change system.adapter.shelly.0 host.raspberrypi 2019-02-12 16:59:49.979 info Restart adapter system.adapter.shelly.0 because enabled host.raspberrypi 2019-02-12 16:59:49.979 error instance system.adapter.shelly.0 terminated with code 0 (OK) shelly.0 2019-02-12 16:59:49.918 info Starting shelly.0 in version 2.1.0 shelly.0 2019-02-12 16:59:49.905 info starting. Version 2.1.0 in /opt/iobroker/node_modules/iobroker.shelly, node: v8.15.0 shelly.0 2019-02-12 16:59:49.785 debug statesDB connected shelly.0 2019-02-12 16:59:49.714 debug objectDB connected
