NEWS
Amazon Dash Button für ioBroker nutzen
-
Hmmmm gibts eigentlich die Möglichkeit, die LED anzusteuern? Hab da im Adapter bisher nichts gefunden….
-
Hmmmm gibts eigentlich die Möglichkeit, die LED anzusteuern? Hab da im Adapter bisher nichts gefunden…. `
Mit dem Datenpunkt ''On'' kann man die LED an/ausschalten
Mit ''rgb'' kannst du die Fabe einstellen.
Gruß Christian
Edit: Falscher threat, hatte gerade das Mihome Gateway im Kopf, sorry.
-
Hmmmm ich hab nur 3 Datenpunkte : Dass Taste gepresst wurde, das Toggle Bit und den Zeitpunkt der letzten Aktivierung…
Wo finde ich diese Datenpunkte ?
-
so ihr beiden …geduld... fals der Button nicht sofort erkannt wird... `
Danke arteck für deine Antwort.Allerdings werden bei mir leider beide garnicht erkannt und ich frage mich ob es vllt etwas mit der "fehlerhaften" Installation zu tun hat.
Hatte jemand die gleichen Erros beim Installieren oder weiß jemand wie ich diese beheben kann?
! ````
iobroker 2018-01-21 18:23:36.907 info exit 0
iobroker 2018-01-21 18:23:36.737 info upload [0] amazon-dash.admin /opt/iobroker/node_modules/iobroker.amazon-dash/admin/amazon-dash.png amazon-dash.png image/png
iobroker 2018-01-21 18:23:36.653 info upload [1] amazon-dash.admin /opt/iobroker/node_modules/iobroker.amazon-dash/admin/index.html index.html text/html
iobroker 2018-01-21 18:23:36.566 info upload [2] amazon-dash.admin /opt/iobroker/node_modules/iobroker.amazon-dash/admin/words.js words.js application/javascript
iobroker 2018-01-21 18:23:36.538 info got /opt/iobroker/node_modules/iobroker.amazon-dash/admin
iobroker 2018-01-21 18:23:36.410 info npm WARN optional SKIPPING OPTIONAL DEPENDENCY: Exit status 1
iobroker 2018-01-21 18:23:36.410 info WARN optional SKIPPING OPTIONAL DEPENDENCY: authenticate-pam@1.0.2 (node_modules/authenticate-pam):npm WARN optional SKIPPING OPTIONAL DEPENDENCY: authenticate-pam@1.0.2 install:node-gyp rebuild
iobroker 2018-01-21 18:23:36.407 info npm
iobroker 2018-01-21 18:23:36.396 info iobroker@1.0.0 /opt/iobroker└── iobroker.amazon-dash@0.2.7
iobroker 2018-01-21 18:23:17.571 info gyp ERR! not ok
iobroker 2018-01-21 18:23:17.571 info gyp ERR! node-gyp -v v3.4.0
iobroker 2018-01-21 18:23:17.571 info gyp ERR! node -v v6.12.0
iobroker 2018-01-21 18:23:17.571 info gyp ERR! cwd /opt/iobroker/node_modules/authenticate-pam
iobroker 2018-01-21 18:23:17.571 info gyp ERR! command '/usr/bin/node' '/usr/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js' 'rebuild'
iobroker 2018-01-21 18:23:17.571 info gyp ERR! System Linux 4.9.61-v7+
iobroker 2018-01-21 18:23:17.571 info gyp ERR! stack at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)
iobroker 2018-01-21 18:23:17.571 info stack at emitTwo (events.js:106:13)gyp ERR! stack at ChildProcess.emit (events.js:191:7)
iobroker 2018-01-21 18:23:17.558 info ERR!
iobroker 2018-01-21 18:23:17.554 info stack at ChildProcess.onExit (/usr/lib/node_modules/npm/node_modules/node-gyp/lib/build.js:276:23)gyp
iobroker 2018-01-21 18:23:17.551 info Error:make
failed with exit code: 2gyp ERR!
iobroker 2018-01-21 18:23:17.546 info ERR! stack
iobroker 2018-01-21 18:23:17.542 info gyp
iobroker 2018-01-21 18:23:17.529 info gyp ERR! build error
iobroker 2018-01-21 18:23:17.529 info make: Verzeichnis „/opt/iobroker/node_modules/authenticate-pam/build“ wird verlassenmake: *** [Release/obj.target/authenticate_pam/authenticate_pam.o] Fehler 1
iobroker 2018-01-21 18:23:17.526 info authenticate_pam.target.mk:92: die Regel für Ziel „Release/obj.target/authenticate_pam/authenticate_pam.o“ scheiterte
iobroker 2018-01-21 18:23:16.359 info compilation terminated.
iobroker 2018-01-21 18:23:16.357 info ^
iobroker 2018-01-21 18:23:16.357 info ../authenticate_pam.cc:30:31: fatal error: security/pam_appl.h: Datei oder Verzeichnis nicht gefunden #include
iobroker 2018-01-21 18:23:10.846 info CXX(target) Release/obj.target/authenticate_pam/authenticate_pam.o
iobroker 2018-01-21 18:23:10.836 info make: Verzeichnis „/opt/iobroker/node_modules/authenticate-pam/build“ wird betreten
iobroker 2018-01-21 18:23:07.529 info EACCES attempting to reinstall using temporary dev dir '/opt/iobroker/node_modules/authenticate-pam/.node-gyp'
iobroker 2018-01-21 18:23:07.528 info WARN
iobroker 2018-01-21 18:23:07.526 info WARN EACCES user 'root' does not have permission to access the dev dir '/root/.node-gyp/6.12.0'gyp
iobroker 2018-01-21 18:23:07.519 info gyp
iobroker 2018-01-21 18:23:05.615 info > node-gyp rebuild
iobroker 2018-01-21 18:23:05.615 info > authenticate-pam@1.0.2 install /opt/iobroker/node_modules/authenticate-pam
iobroker 2018-01-21 18:23:05.576 info WARN lifecycle iobroker.amazon-dash@0.2.7~preinstall: cannot run in wd %s %s (wd=%s) iobroker.amazon-dash@0.2.7 apt-get install libpcap-dev -y || true /opt/iobroker/node_modules/.staging/iobroker.amazon-dash-eb5038e9
iobroker 2018-01-21 18:23:05.573 info npm
iobroker 2018-01-21 18:21:54.123 info npm install https://github.com/PArns/ioBroker.amazon-dash/tarball/master --production --prefix '/opt/iobroker' (System call)
iobroker 2018-01-21 18:21:53.732 info install https://github.com/PArns/ioBroker.amazon-dash/tarball/master -
so ihr beiden …geduld... fals der Button nicht sofort erkannt wird... `
Danke arteck für deine Antwort.Allerdings werden bei mir leider beide garnicht erkannt und ich frage mich ob es vllt etwas mit der "fehlerhaften" Installation zu tun hat.
Hatte jemand die gleichen Erros beim Installieren oder weiß jemand wie ich diese beheben kann?
!
iobroker 2018-01-21 18:23:36.907 info exit 0 iobroker 2018-01-21 18:23:36.737 info upload [0] amazon-dash.admin /opt/iobroker/node_modules/iobroker.amazon-dash/admin/amazon-dash.png amazon-dash.png image/png iobroker 2018-01-21 18:23:36.653 info upload [1] amazon-dash.admin /opt/iobroker/node_modules/iobroker.amazon-dash/admin/index.html index.html text/html iobroker 2018-01-21 18:23:36.566 info upload [2] amazon-dash.admin /opt/iobroker/node_modules/iobroker.amazon-dash/admin/words.js words.js application/javascript iobroker 2018-01-21 18:23:36.538 info got /opt/iobroker/node_modules/iobroker.amazon-dash/admin iobroker 2018-01-21 18:23:36.410 info npm WARN optional SKIPPING OPTIONAL DEPENDENCY: Exit status 1 iobroker 2018-01-21 18:23:36.410 info WARN optional SKIPPING OPTIONAL DEPENDENCY: authenticate-pam@1.0.2 (node_modules/authenticate-pam):npm WARN optional SKIPPING OPTIONAL DEPENDENCY: authenticate-pam@1.0.2 install: `node-gyp rebuild` iobroker 2018-01-21 18:23:36.407 info npm iobroker 2018-01-21 18:23:36.396 info iobroker@1.0.0 /opt/iobroker└── iobroker.amazon-dash@0.2.7 iobroker 2018-01-21 18:23:17.571 info gyp ERR! not ok iobroker 2018-01-21 18:23:17.571 info gyp ERR! node-gyp -v v3.4.0 iobroker 2018-01-21 18:23:17.571 info gyp ERR! node -v v6.12.0 iobroker 2018-01-21 18:23:17.571 info gyp ERR! cwd /opt/iobroker/node_modules/authenticate-pam iobroker 2018-01-21 18:23:17.571 info gyp ERR! command '/usr/bin/node' '/usr/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js' 'rebuild' iobroker 2018-01-21 18:23:17.571 info gyp ERR! System Linux 4.9.61-v7+ iobroker 2018-01-21 18:23:17.571 info gyp ERR! stack at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12) iobroker 2018-01-21 18:23:17.571 info stack at emitTwo (events.js:106:13)gyp ERR! stack at ChildProcess.emit (events.js:191:7) iobroker 2018-01-21 18:23:17.558 info ERR! iobroker 2018-01-21 18:23:17.554 info stack at ChildProcess.onExit (/usr/lib/node_modules/npm/node_modules/node-gyp/lib/build.js:276:23)gyp iobroker 2018-01-21 18:23:17.551 info Error: `make` failed with exit code: 2gyp ERR! iobroker 2018-01-21 18:23:17.546 info ERR! stack iobroker 2018-01-21 18:23:17.542 info gyp iobroker 2018-01-21 18:23:17.529 info gyp ERR! build error iobroker 2018-01-21 18:23:17.529 info make: Verzeichnis „/opt/iobroker/node_modules/authenticate-pam/build“ wird verlassenmake: *** [Release/obj.target/authenticate_pam/authenticate_pam.o] Fehler 1 iobroker 2018-01-21 18:23:17.526 info authenticate_pam.target.mk:92: die Regel für Ziel „Release/obj.target/authenticate_pam/authenticate_pam.o“ scheiterte iobroker 2018-01-21 18:23:16.359 info compilation terminated. iobroker 2018-01-21 18:23:16.357 info ^ iobroker 2018-01-21 18:23:16.357 info ../authenticate_pam.cc:30:31: fatal error: security/pam_appl.h: Datei oder Verzeichnis nicht gefunden #include iobroker 2018-01-21 18:23:10.846 info CXX(target) Release/obj.target/authenticate_pam/authenticate_pam.o iobroker 2018-01-21 18:23:10.836 info make: Verzeichnis „/opt/iobroker/node_modules/authenticate-pam/build“ wird betreten iobroker 2018-01-21 18:23:07.529 info EACCES attempting to reinstall using temporary dev dir '/opt/iobroker/node_modules/authenticate-pam/.node-gyp' iobroker 2018-01-21 18:23:07.528 info WARN iobroker 2018-01-21 18:23:07.526 info WARN EACCES user 'root' does not have permission to access the dev dir '/root/.node-gyp/6.12.0'gyp iobroker 2018-01-21 18:23:07.519 info gyp iobroker 2018-01-21 18:23:05.615 info > node-gyp rebuild iobroker 2018-01-21 18:23:05.615 info > authenticate-pam@1.0.2 install /opt/iobroker/node_modules/authenticate-pam iobroker 2018-01-21 18:23:05.576 info WARN lifecycle iobroker.amazon-dash@0.2.7~preinstall: cannot run in wd %s %s (wd=%s) iobroker.amazon-dash@0.2.7 apt-get install libpcap-dev -y || true /opt/iobroker/node_modules/.staging/iobroker.amazon-dash-eb5038e9 iobroker 2018-01-21 18:23:05.573 info npm iobroker 2018-01-21 18:21:54.123 info npm install https://github.com/PArns/ioBroker.amazon-dash/tarball/master --production --prefix '/opt/iobroker' (System call) iobroker 2018-01-21 18:21:53.732 info install https://github.com/PArns/ioBroker.amazon-dash/tarball/master
`apt-get install libpcap-dev ````hast du gemacht ??
-
Ja das habe ich vorher gemacht
Weitere Infos:
-
iobroker läuft auf einem Raspberry Pi 3
-
die dashbuttons haben die Mac 18-74-2E-3F-F8-04 und 18-74-2E-DE-2F-ED
-
Libpcap-dev ist installiert
-
Node 6.12.0 mit npm 3.10.10 ist installiert
-
Iobroker wurde als root installiert und alles andere läuft super `
-
-
Hallo,
leider bekomme ich bei der Installation folgende Fehlermeldung:
Unbenannt.PNG
Kann mir jmd. weiterhelfen? `
leider bei mir auch. Ich habe lediglich sofort 0.2.7 versucht einzubinden.
Keine andere Version vorher.
Braucht es noch andere Bibliotheken?
-
Hallo zusammen,
ich hab meinen iobroker vom RPI3 auf Windows10 umgezogen. Alle Adapter neu installiert usw. und läuft auch alles bis auf den Dash-Button Adapter.
apt-get ist in der Windows Umgebung lt. meinen Informationen nicht möglich, daher kommt die folgende Fehlermeldung bei der Installation:
`$ ./iobroker add amazon-dash npm install iobroker.amazon-dash --production --prefix "C:/iobroker" (System call) Der Befehl "apt-get" ist entweder falsch geschrieben oder konnte nicht gefunden werden. Der Befehl "true" ist entweder falsch geschrieben oder konnte nicht gefunden werden. npm ERR! code ELIFECYCLE npm ERR! errno 1 npm ERR! iobroker.amazon-dash@0.2.7 preinstall: apt-get install libpcap-dev -y || true npm ERR! Exit status 1 npm ERR! npm ERR! Failed at the iobroker.amazon-dash@0.2.7 preinstall script.npm ERR! This is probably not a problem with npm. There is likely additional logging output above. npm ERR! A complete log of this run can be found in: npm ERR! C:\WINDOWS\system32\config\systemprofile\AppData\Roaming\npm-cache_logs\2018-02-05T23_25_47_039Z-debug.log host.BRIX-SERVER create instance amazon-dash ERROR: host.BRIX-SERVER error: reading io-package.json Error: ENOENT: no such file or directory, open 'C:\iobroker\node_modules\iobroker.js-controller\adapter\amazon-dash\io-package.json' ERROR: process exited with code 20`
node 8.9.4
npm 4.6.1
Kann mir jemand helfen den Dash-Button Adapter zum laufen zu bekommen?
Ich hab einige Buttons im Einsatz die ich nun alle nicht mehr nutzen kann
Danke & Gruß,
xmace
-
hier gabs mal ne Beschreibung für "pcap for win"…
-
hab pcap für windows installiert aber trotzdem lässt sich der adapter in iobroker nicht installieren wegen den fehlenden apt-get befehl….
-
Kann mir diesbezüglich keiner helfen?
Wenn der Adapter unter Windows nicht funktioniert, sollte dieser Hinweis wenigstens in der Readme/Adapter Seite auf GitHub erwähnt werden damit nicht jeder vergeblich Zeit opfert.
Danke
-
Kann mir diesbezüglich keiner helfen?
Wenn der Adapter unter Windows nicht funktioniert, sollte dieser Hinweis wenigstens in der Readme/Adapter Seite auf GitHub erwähnt werden damit nicht jeder vergeblich Zeit opfert.
Danke
`
probier mal aus meinem fork es zu installieren ..
-
Danke, hat leider nicht geklappt. Windows-build-tools sind installiert.
iobroker 2018-02-11 16:25:55.379 info exit 0
iobroker 2018-02-11 16:25:55.282 info C:\WINDOWS\system32\config\systemprofile\AppData\Roaming\npm-cache_logs\2018-02-11T15_25_55_264Z-debug.log
iobroker 2018-02-11 16:25:55.282 info ERR!
iobroker 2018-02-11 16:25:55.281 info npm
iobroker 2018-02-11 16:25:55.280 info A complete log of this run can be found in:
iobroker 2018-02-11 16:25:55.279 info npm ERR!
iobroker 2018-02-11 16:25:55.278 info
iobroker 2018-02-11 16:25:55.256 info This is probably not a problem with npm. There is likely additional logging output above.
iobroker 2018-02-11 16:25:55.255 info npm ERR!
iobroker 2018-02-11 16:25:55.254 info npm ERR! Failed at the socketwatcher@0.3.0 install script.
iobroker 2018-02-11 16:25:55.253 info
iobroker 2018-02-11 16:25:55.250 info ERR!
iobroker 2018-02-11 16:25:55.248 info
iobroker 2018-02-11 16:25:55.245 info npm
iobroker 2018-02-11 16:25:55.243 info Exit status 1
iobroker 2018-02-11 16:25:55.239 info ERR!
iobroker 2018-02-11 16:25:55.236 info
iobroker 2018-02-11 16:25:55.234 info npm
iobroker 2018-02-11 16:25:55.231 info socketwatcher@0.3.0 install:
node-gyp rebuild
iobroker 2018-02-11 16:25:55.229 info ERR!
iobroker 2018-02-11 16:25:55.226 info
iobroker 2018-02-11 16:25:55.224 info npm
iobroker 2018-02-11 16:25:55.217 info 1
iobroker 2018-02-11 16:25:55.215 info errno
iobroker 2018-02-11 16:25:55.213 info ERR!
iobroker 2018-02-11 16:25:55.212 info npm
iobroker 2018-02-11 16:25:55.203 info ELIFECYCLE
iobroker 2018-02-11 16:25:55.197 info code
iobroker 2018-02-11 16:25:55.191 info
iobroker 2018-02-11 16:25:55.178 info ERR!
iobroker 2018-02-11 16:25:55.166 info
iobroker 2018-02-11 16:25:55.158 info npm
iobroker 2018-02-11 16:25:54.852 info not ok
iobroker 2018-02-11 16:25:54.851 info gyp ERR!
iobroker 2018-02-11 16:25:54.850 info node-gyp -v v3.6.2
iobroker 2018-02-11 16:25:54.848 info ERR!
iobroker 2018-02-11 16:25:54.847 info node -v v8.9.4gyp
iobroker 2018-02-11 16:25:54.844 info ERR!
iobroker 2018-02-11 16:25:54.842 info
iobroker 2018-02-11 16:25:54.841 info C:\iobroker\node_modules\iobroker.amazon-dash\node_modules\socketwatchergyp
iobroker 2018-02-11 16:25:54.839 info cwd
iobroker 2018-02-11 16:25:54.838 info gyp ERR!
iobroker 2018-02-11 16:25:54.836 info command "C:\Program Files\nodejs\node.exe" "C:\Program Files\nodejs\node_modules\npm\node_modules\node-gyp\bin\node-gyp.js" "rebuild"
iobroker 2018-02-11 16:25:54.835 info ERR!
iobroker 2018-02-11 16:25:54.834 info gyp
iobroker 2018-02-11 16:25:54.833 info System Windows_NT 10.0.16299
iobroker 2018-02-11 16:25:54.831 info ERR!
iobroker 2018-02-11 16:25:54.830 info gyp
iobroker 2018-02-11 16:25:54.828 info at FSReqWrap.oncomplete (fs.js:152:21)
iobroker 2018-02-11 16:25:54.826 info stack
iobroker 2018-02-11 16:25:54.824 info at C:\Program Files\nodejs\node_modules\npm\node_modules\graceful-fs\polyfills.js:284:29gyp ERR!
iobroker 2018-02-11 16:25:54.820 info ERR! stack
iobroker 2018-02-11 16:25:54.816 info
iobroker 2018-02-11 16:25:54.814 info gyp
iobroker 2018-02-11 16:25:54.812 info at PythonFinder. (C:\Program Files\nodejs\node_modules\npm\node_modules\node-gyp\lib\configure.js:508:16)
iobroker 2018-02-11 16:25:54.808 info stack
iobroker 2018-02-11 16:25:54.786 info
iobroker 2018-02-11 16:25:54.784 info ERR!
iobroker 2018-02-11 16:25:54.782 info
iobroker 2018-02-11 16:25:54.778 info gyp
iobroker 2018-02-11 16:25:54.776 info at PythonFinder.failNoPython (C:\Program Files\nodejs\node_modules\npm\node_modules\node-gyp\lib\configure.js:483:19)
iobroker 2018-02-11 16:25:54.775 info stack
iobroker 2018-02-11 16:25:54.773 info
iobroker 2018-02-11 16:25:54.771 info ERR!
iobroker 2018-02-11 16:25:54.767 info
iobroker 2018-02-11 16:25:54.765 info gyp
iobroker 2018-02-11 16:25:54.762 info Error: Can't find Python executable "python", you can set the PYTHON env variable.
iobroker 2018-02-11 16:25:54.758 info stack
iobroker 2018-02-11 16:25:54.756 info
iobroker 2018-02-11 16:25:54.754 info ERR!
iobroker 2018-02-11 16:25:54.751 info
iobroker 2018-02-11 16:25:54.749 info gyp
iobroker 2018-02-11 16:25:54.744 info
iobroker 2018-02-11 16:25:54.741 info configure error
iobroker 2018-02-11 16:25:54.739 info
iobroker 2018-02-11 16:25:54.737 info ERR!
iobroker 2018-02-11 16:25:54.735 info
iobroker 2018-02-11 16:25:54.734 info gyp
iobroker 2018-02-11 16:25:53.096 info if not defined npm_config_node_gyp (node "C:\Program Files\nodejs\node_modules\npm\node_modules\npm-lifecycle\node-gyp-bin\....\node_modules\node-gyp\bin\node-gyp.js" rebuild ) else (node "C:\Prog
iobroker 2018-02-11 16:25:53.094 info C:\iobroker\node_modules\iobroker.amazon-dash\node_modules\socketwatcher>
iobroker 2018-02-11 16:25:53.046 info
iobroker 2018-02-11 16:25:53.046 info > node-gyp rebuild
iobroker 2018-02-11 16:25:53.046 info > socketwatcher@0.3.0 install C:\iobroker\node_modules\iobroker.amazon-dash\node_modules\socketwatcher
iobroker 2018-02-11 16:25:42.573 info npm install https://github.com/arteck/ioBroker.amaz … all/master --production --prefix "C:/iobroker" (System call)
iobroker 2018-02-11 16:25:42.354 info install https://github.com/arteck/ioBroker.amaz ... all/master
iobroker 2018-02-11 16:25:40.458 info url "https://github.com/arteck/ioBroker.amazon-dash.git" --debug
-
Keine Idee?
-
hast du die Variable gesetzt
> Can't find Python executable "python", you can set the PYTHON env variable.
-
Nach langem Kampf hab ich die Env Variable eingetragen bekommen aber weiterhin kein Erfolg:
$ ./iobroker url "https://github.com/arteck/ioBroker.amazon-dash.git" --debug install https://github.com/arteck/ioBroker.amazon-dash/tarball/master npm install https://github.com/arteck/ioBroker.amazon-dash/tarball/master --production --prefix "C:/iobroker" (System call) > socketwatcher@0.3.0 install C:\iobroker\node_modules\iobroker.amazon-dash\node_modules\socketwatcher > node-gyp rebuild C:\iobroker\node_modules\iobroker.amazon-dash\node_modules\socketwatcher> if not defined npm_config_node_gyp ( node "C:\Program Files\nodejs\node_modules\npm\node_modules\npm-lifecycle\node-gyp-bin\\..\..\node_modules\node-gyp\bin\node-gyp.js" rebuild ) else ( node "C:\Program Files\nodejs\node_modules\npm\node_modules\node-gyp\bin\node-gyp.js" rebuild ) Die Projekte in dieser Projektmappe werden nacheinander erstellt. Um eine parallele Erstellung zu erm�glichen, m�ssen Sie den Schalter "/m" hinzuf�gen. MSBUILD : error MSB4132: Die Toolversion "2.0" ist unbekannt. Verf�gbare Toolversionen sind "14.0", "4.0". gyp ERR! build error gyp ERR! stack Error: `C:\Program Files (x86)\MSBuild\14.0\bin\msbuild.exe` failed with exit code: 1 gyp ERR! stack at ChildProcess.onExit (C:\Program Files\nodejs\node_modules\npm\node_modules\node-gyp\lib\build.js:258:23) gyp ERR! stack at emitTwo (events.js:126:13) gyp ERR! stack at ChildProcess.emit (events.js:214:7) gyp ERR! stack at Process.ChildProcess._handle.onexit (internal/child_process.js:198:12) gyp ERR! System Windows_NT 10.0.16299 gyp ERR! command "C:\\Program Files\\nodejs\\node.exe" "C:\\Program Files\\nodejs\\node_modules\\npm\\node_modules\\node-gyp\\bin\\node-gyp.js" "rebuild" gyp ERR! cwd C:\iobroker\node_modules\iobroker.amazon-dash\node_modules\socketwatchergyp ERR! node -v v8.9.4 gyp ERR! node-gyp -v v3.6.2 gyp ERR! not ok npm ERR! code ELIFECYCLE npm ERR! errno 1 npm ERR! socketwatcher@0.3.0 install: `node-gyp rebuild` npm ERR! Exit status 1 npm ERR! npm ERR! Failed at the socketwatcher@0.3.0 install script. npm ERR! This is probably not a problem with npm. There is likely additional logging output above. npm ERR! A complete log of this run can be found in: npm ERR! C:\WINDOWS\system32\config\systemprofile\AppData\Roaming\npm-cache\_logs\2018-02-11T22_14_48_052Z-debug.log process exited with code 0
-
Konnte das "Tool Version 2" Problem nach folgender Anleitung beheben:
https://github.com/chjj/pty.js/issues/60
npm config set msvs_version 2015 --global
Allerdings jetzt:
$ ./iobroker url "https://github.com/arteck/iobroker.amazon-dash.git" install https://github.com/arteck/iobroker.amazon-dash/tarball/master npm install https://github.com/arteck/iobroker.amazon-dash/tarball/master --production --prefix "C:/iobroker" (System call) gyp ERR! build error gyp ERR! stack Error: `C:\Program Files (x86)\MSBuild\14.0\bin\msbuild.exe` failed with exit code: 1 gyp ERR! stack at ChildProcess.onExit (C:\Program Files\nodejs\node_modules\npm\node_modules\node-gyp\lib\build.js:258:23) gyp ERR! stack at emitTwo (events.js:126:13) gyp ERR! stack at ChildProcess.emit (events.js:214:7) gyp ERR! stack at Process.ChildProcess._handle.onexit (internal/child_process.js:198:12) gyp ERR! System Windows_NT 10.0.16299 gyp ERR! command "C:\\Program Files\\nodejs\\node.exe" "C:\\Program Files\\nodejs\\node_modules\\npm\\node_modules\\node-gyp\\bin\\node-gyp.js" "rebuild" gyp ERR! cwd C:\iobroker\node_modules\iobroker.amazon-dash\node_modules\socketwatcher gyp ERR! node -v v8.9.4 gyp ERR! node-gyp -v v3.6.2 gyp ERR! not ok npm ERR! code ELIFECYCLE npm ERR! errno 1 npm ERR! socketwatcher@0.3.0 install: `node-gyp rebuild` npm ERR! Exit status 1 npm ERR! npm ERR! Failed at the socketwatcher@0.3.0 install script. npm ERR! This is probably not a problem with npm. There is likely additional logging output above. npm ERR! A complete log of this run can be found in: npm ERR! C:\WINDOWS\system32\config\systemprofile\AppData\Roaming\npm-cache\_logs\2018-02-11T22_43_08_559Z-debug.log ERROR: Cannot parse C:/iobroker/node_modules/iobroker.js-controller/adapter/amazon-dash/io-package.json:Error: ENOENT: no such file or directory, open 'C:\iobroker\node_modules\iobroker.js-controller\adapter\amazon-dash\io-package.json' process exited with code 0
-
ich weiss nicht ob das so gut war auf win 10 direkt auf die C platte zu installieren
böse erfahrung mit gemacht und Stundenlanges suchen..
zeig mal das Log
C:\WINDOWS\system32\config\systemprofile\AppData\Roaming\npm-cache\_logs\2018-02-11T22_43_08_559Z-debug.log
-
Danke für deine Hilfe! Für mich wärs nicht so wichtig, wenn ich nicht 6 Dash-Buttons extra wegen dem iobroker gekauft hätte und diverse Szenen & Skripte schon fix und fertig sind.
Aber Windows ist bei mir schon immer bei allen PC's auf C:\ installiert. Warum hattest du damit Probleme?
Hier das Log:
0 info it worked if it ends with ok 1 verbose cli [ 'C:\\Program Files\\nodejs\\node.exe', 1 verbose cli 'C:\\Program Files\\nodejs\\node_modules\\npm\\bin\\npm-cli.js', 1 verbose cli 'install', 1 verbose cli 'https://github.com/arteck/iobroker.amazon-dash/tarball/master', 1 verbose cli '--production', 1 verbose cli '--prefix', 1 verbose cli 'C:/iobroker' ] 2 info using npm@5.6.0 3 info using node@v8.9.4 4 verbose npm-session 6354a5fc3c15b97e 5 silly install loadCurrentTree 6 silly install readGlobalPackageData 7 http fetch GET 200 https://github.com/arteck/iobroker.amazon-dash/tarball/master 1636ms 8 silly pacote remote manifest for undefined@https://github.com/arteck/iobroker.amazon-dash/tarball/master fetched in 1885ms 9 silly install loadIdealTree 10 silly install cloneCurrentTreeToIdealTree 11 silly install loadShrinkwrap 12 silly install loadAllDepsIntoIdealTree 13 silly resolveWithNewModule iobroker.amazon-dash@0.2.6 checking installable status 14 http fetch GET 200 https://github.com/mranney/node_pcap/tarball/master 715ms 15 silly pacote remote manifest for pcap@https://github.com/mranney/node_pcap/tarball/master fetched in 736ms 16 silly resolveWithNewModule pcap@2.0.0 checking installable status 17 http fetch GET 304 https://registry.npmjs.org/nan 359ms (from cache) 18 http fetch GET 304 https://registry.npmjs.org/socketwatcher 367ms (from cache) 19 silly pacote range manifest for nan@^2.0.9 fetched in 411ms 20 silly resolveWithNewModule nan@2.8.0 checking installable status 21 silly pacote range manifest for socketwatcher@^0.3.0 fetched in 401ms 22 silly resolveWithNewModule socketwatcher@0.3.0 checking installable status 23 silly currentTree iobroker.inst@1.0.8 24 silly idealTree iobroker.inst@1.0.8 24 silly idealTree `-- iobroker.amazon-dash@0.2.6 24 silly idealTree +-- nan@2.8.0 24 silly idealTree +-- pcap@2.0.0 24 silly idealTree `-- socketwatcher@0.3.0 25 silly install generateActionsToTake 26 silly diff-trees filtering actions: includeDev false includeProd true 27 silly diffTrees action count 4 28 silly diffTrees add nan@2.8.0 29 silly diffTrees add socketwatcher@0.3.0 30 silly diffTrees add pcap@2.0.0 31 silly diffTrees add iobroker.amazon-dash@0.2.6 32 silly decomposeActions action count 32 33 silly decomposeActions fetch nan@2.8.0 34 silly decomposeActions extract nan@2.8.0 35 silly decomposeActions preinstall nan@2.8.0 36 silly decomposeActions build nan@2.8.0 37 silly decomposeActions install nan@2.8.0 38 silly decomposeActions postinstall nan@2.8.0 39 silly decomposeActions finalize nan@2.8.0 40 silly decomposeActions refresh-package-json nan@2.8.0 41 silly decomposeActions fetch socketwatcher@0.3.0 42 silly decomposeActions extract socketwatcher@0.3.0 43 silly decomposeActions preinstall socketwatcher@0.3.0 44 silly decomposeActions build socketwatcher@0.3.0 45 silly decomposeActions install socketwatcher@0.3.0 46 silly decomposeActions postinstall socketwatcher@0.3.0 47 silly decomposeActions finalize socketwatcher@0.3.0 48 silly decomposeActions refresh-package-json socketwatcher@0.3.0 49 silly decomposeActions fetch pcap@2.0.0 50 silly decomposeActions extract pcap@2.0.0 51 silly decomposeActions preinstall pcap@2.0.0 52 silly decomposeActions build pcap@2.0.0 53 silly decomposeActions install pcap@2.0.0 54 silly decomposeActions postinstall pcap@2.0.0 55 silly decomposeActions finalize pcap@2.0.0 56 silly decomposeActions refresh-package-json pcap@2.0.0 57 silly decomposeActions fetch iobroker.amazon-dash@0.2.6 58 silly decomposeActions extract iobroker.amazon-dash@0.2.6 59 silly decomposeActions preinstall iobroker.amazon-dash@0.2.6 60 silly decomposeActions build iobroker.amazon-dash@0.2.6 61 silly decomposeActions install iobroker.amazon-dash@0.2.6 62 silly decomposeActions postinstall iobroker.amazon-dash@0.2.6 63 silly decomposeActions finalize iobroker.amazon-dash@0.2.6 64 silly decomposeActions refresh-package-json iobroker.amazon-dash@0.2.6 65 silly install executeActions 66 silly doSerial global-install 32 67 verbose correctMkdir C:\WINDOWS\system32\config\systemprofile\AppData\Roaming\npm-cache\_locks correctMkdir not in flight; initializing 68 verbose lock using C:\WINDOWS\system32\config\systemprofile\AppData\Roaming\npm-cache\_locks\staging-75c4853d5d99f16b.lock for C:\iobroker\node_modules\.staging 69 silly doParallel extract 32 70 silly extract nan@2.8.0 71 silly pacote trying nan@https://registry.npmjs.org/nan/-/nan-2.8.0.tgz by hash: sha1-7XFfP+neArV6XmJS2QqWZ14fCFo= 72 silly extract socketwatcher@0.3.0 73 silly pacote trying socketwatcher@https://registry.npmjs.org/socketwatcher/-/socketwatcher-0.3.0.tgz by hash: sha1-SeVhQFj8qrGdZAs3QiWk7qS0t4o= 74 silly extract pcap@2.0.0 75 silly pacote trying pcap@https://github.com/mranney/node_pcap/tarball/master by hash: sha512-85b1vVlb48LCRtdy6mdnpvOJRvz+68PXsyku38x1VNafMloXbxVkOAY68tDh06Ty1eMUiEP3S+DIwWECkx9rFA== 76 silly extract iobroker.amazon-dash@0.2.6 77 silly pacote trying iobroker.amazon-dash@https://github.com/arteck/iobroker.amazon-dash/tarball/master by hash: sha512-084za+mjvp4Bf9D9Y1bRguFNoT2QbC/9EMKJFo+1FNLxb5VxtpA1Y/JvRTWrqHlLbp3tMgvXNnOLa2kg5XVedQ== 78 silly pacote socketwatcher@https://registry.npmjs.org/socketwatcher/-/socketwatcher-0.3.0.tgz extracted to C:\iobroker\node_modules\.staging\socketwatcher-e9ba31c5 by content address 314ms 79 silly pacote iobroker.amazon-dash@https://github.com/arteck/iobroker.amazon-dash/tarball/master extracted to C:\iobroker\node_modules\.staging\iobroker.amazon-dash-6b979419 by content address 511ms 80 silly pacote nan@https://registry.npmjs.org/nan/-/nan-2.8.0.tgz extracted to C:\iobroker\node_modules\.staging\nan-9cabe2ea by content address 625ms 81 silly pacote pcap@https://github.com/mranney/node_pcap/tarball/master extracted to C:\iobroker\node_modules\.staging\pcap-a2d8266e by content address 781ms 82 silly doReverseSerial unbuild 32 83 silly doSerial remove 32 84 silly doSerial move 32 85 silly doSerial finalize 32 86 silly finalize C:\iobroker\node_modules\iobroker.amazon-dash\node_modules\nan 87 silly finalize C:\iobroker\node_modules\iobroker.amazon-dash\node_modules\socketwatcher 88 silly finalize C:\iobroker\node_modules\iobroker.amazon-dash\node_modules\pcap 89 silly finalize C:\iobroker\node_modules\iobroker.amazon-dash 90 silly doParallel refresh-package-json 32 91 silly refresh-package-json C:\iobroker\node_modules\iobroker.amazon-dash\node_modules\nan 92 silly refresh-package-json C:\iobroker\node_modules\iobroker.amazon-dash\node_modules\socketwatcher 93 silly refresh-package-json C:\iobroker\node_modules\iobroker.amazon-dash\node_modules\pcap 94 silly refresh-package-json C:\iobroker\node_modules\iobroker.amazon-dash 95 silly doParallel preinstall 32 96 silly preinstall nan@2.8.0 97 info lifecycle nan@2.8.0~preinstall: nan@2.8.0 98 silly preinstall socketwatcher@0.3.0 99 info lifecycle socketwatcher@0.3.0~preinstall: socketwatcher@0.3.0 100 silly preinstall pcap@2.0.0 101 info lifecycle pcap@2.0.0~preinstall: pcap@2.0.0 102 silly preinstall iobroker.amazon-dash@0.2.6 103 info lifecycle iobroker.amazon-dash@0.2.6~preinstall: iobroker.amazon-dash@0.2.6 104 silly doSerial build 32 105 silly build nan@2.8.0 106 info linkStuff nan@2.8.0 107 silly linkStuff nan@2.8.0 has C:\iobroker\node_modules\iobroker.amazon-dash\node_modules as its parent node_modules 108 silly linkStuff nan@2.8.0 is part of a global install 109 silly linkStuff nan@2.8.0 is installed into a global node_modules 110 verbose linkBins nan@2.8.0 111 verbose linkMans nan@2.8.0 112 silly build socketwatcher@0.3.0 113 info linkStuff socketwatcher@0.3.0 114 silly linkStuff socketwatcher@0.3.0 has C:\iobroker\node_modules\iobroker.amazon-dash\node_modules as its parent node_modules 115 silly linkStuff socketwatcher@0.3.0 is part of a global install 116 silly linkStuff socketwatcher@0.3.0 is installed into a global node_modules 117 verbose linkBins socketwatcher@0.3.0 118 verbose linkMans socketwatcher@0.3.0 119 silly build pcap@2.0.0 120 info linkStuff pcap@2.0.0 121 silly linkStuff pcap@2.0.0 has C:\iobroker\node_modules\iobroker.amazon-dash\node_modules as its parent node_modules 122 silly linkStuff pcap@2.0.0 is part of a global install 123 silly linkStuff pcap@2.0.0 is installed into a global node_modules 124 verbose linkBins pcap@2.0.0 125 verbose linkMans pcap@2.0.0 126 silly build iobroker.amazon-dash@0.2.6 127 info linkStuff iobroker.amazon-dash@0.2.6 128 silly linkStuff iobroker.amazon-dash@0.2.6 has C:\iobroker\node_modules as its parent node_modules 129 silly linkStuff iobroker.amazon-dash@0.2.6 is part of a global install 130 silly linkStuff iobroker.amazon-dash@0.2.6 is installed into a global node_modules 131 silly linkStuff iobroker.amazon-dash@0.2.6 is installed into the top-level global node_modules 132 verbose linkBins iobroker.amazon-dash@0.2.6 133 verbose linkMans iobroker.amazon-dash@0.2.6 134 silly doSerial global-link 32 135 silly doParallel update-linked 32 136 silly doSerial install 32 137 silly install nan@2.8.0 138 info lifecycle nan@2.8.0~install: nan@2.8.0 139 silly install socketwatcher@0.3.0 140 info lifecycle socketwatcher@0.3.0~install: socketwatcher@0.3.0 141 verbose lifecycle socketwatcher@0.3.0~install: unsafe-perm in lifecycle true 142 verbose lifecycle socketwatcher@0.3.0~install: PATH: C:\Program Files\nodejs\node_modules\npm\node_modules\npm-lifecycle\node-gyp-bin;C:\iobroker\node_modules\iobroker.amazon-dash\node_modules\socketwatcher\node_modules\.bin;C:\iobroker\node_modules\iobroker.amazon-dash\node_modules\.bin;C:\iobroker\node_modules\.bin;C:\Program Files (x86)\Intel\TXE Components\TCS\;C:\Program Files\Intel\TXE Components\TCS\;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\WINDOWS\System32\WindowsPowerShell\v1.0\;C:\Program Files (x86)\Windows Kits\8.1\Windows Performance Toolkit\;C:\Program Files\nodejs\;PYTHON_HOME;PYTHON;C:\Users\BRIX-SERVER\.windows-build-tools\python27\;C:\WINDOWS\system32\config\systemprofile\AppData\Local\Microsoft\WindowsApps 143 verbose lifecycle socketwatcher@0.3.0~install: CWD: C:\iobroker\node_modules\iobroker.amazon-dash\node_modules\socketwatcher 144 silly lifecycle socketwatcher@0.3.0~install: Args: [ '/d /s /c', 'node-gyp rebuild' ] 145 silly lifecycle socketwatcher@0.3.0~install: Returned: code: 1 signal: null 146 info lifecycle socketwatcher@0.3.0~install: Failed to exec install script 147 verbose unlock done using C:\WINDOWS\system32\config\systemprofile\AppData\Roaming\npm-cache\_locks\staging-75c4853d5d99f16b.lock for C:\iobroker\node_modules\.staging 148 verbose stack Error: socketwatcher@0.3.0 install: `node-gyp rebuild` 148 verbose stack Exit status 1 148 verbose stack at EventEmitter. <anonymous>(C:\Program Files\nodejs\node_modules\npm\node_modules\npm-lifecycle\index.js:285:16) 148 verbose stack at emitTwo (events.js:126:13) 148 verbose stack at EventEmitter.emit (events.js:214:7) 148 verbose stack at ChildProcess. <anonymous>(C:\Program Files\nodejs\node_modules\npm\node_modules\npm-lifecycle\lib\spawn.js:55:14) 148 verbose stack at emitTwo (events.js:126:13) 148 verbose stack at ChildProcess.emit (events.js:214:7) 148 verbose stack at maybeClose (internal/child_process.js:925:16) 148 verbose stack at Process.ChildProcess._handle.onexit (internal/child_process.js:209:5) 149 verbose pkgid socketwatcher@0.3.0 150 verbose cwd C:\iobroker\node_modules\iobroker 151 verbose Windows_NT 10.0.16299 152 verbose argv "C:\\Program Files\\nodejs\\node.exe" "C:\\Program Files\\nodejs\\node_modules\\npm\\bin\\npm-cli.js" "install" "https://github.com/arteck/iobroker.amazon-dash/tarball/master" "--production" "--prefix" "C:/iobroker" 153 verbose node v8.9.4 154 verbose npm v5.6.0 155 error code ELIFECYCLE 156 error errno 1 157 error socketwatcher@0.3.0 install: `node-gyp rebuild` 157 error Exit status 1 158 error Failed at the socketwatcher@0.3.0 install script. 158 error This is probably not a problem with npm. There is likely additional logging output above. 159 verbose exit [ 1, true ]</anonymous></anonymous>
-
ich meine iobroker auf die C Platte..
irgendwie gibts ein problem mit dem socketwatcher (pcap)
` > 153 verbose node v8.9.4
154 verbose npm v5.6.0 `
ist verkehrt