NEWS
Say it kann nicht installiert werden
-
Moin, ich versuche krampfhaft Say it zu installieren. Leider erhalte ich immer folgende Fehlerausgabe.
$ ./iobroker add sayit host.ioBrokerTest install adapter sayit npm install iobroker.sayit --production --prefix "/opt/iobroker" (System call) npm WARN optional SKIPPING OPTIONAL DEPENDENCY: xpc-connection@~0.1.4 (node_modules/iobroker.radar/node_modules/noble/node_modules/xpc-connection):npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for xpc-connection@0.1.4: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"arm"}) npm WARN optional SKIPPING OPTIONAL DEPENDENCY: xpc-connection@~0.1.4 (node_modules/noble/node_modules/xpc-connection): npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for xpc-connection@0.1.4: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"arm"}) npm WARN enoent ENOENT: no such file or directory, open '/opt/iobroker/node_modules/aws-sdk/package.json' npm WARN enoent ENOENT: no such file or directory, open '/opt/iobroker/node_modules/iobroker.vuplus/package.json' npm ERR! Linux 4.9.41-v7+npm ERR! argv "/usr/bin/nodejs" "/usr/bin/npm" "install" "iobroker.sayit" "--production" "--prefix" "/opt/iobroker" npm ERR! node v6.11.2 npm ERR! npm v3.10.10npm ERR! path /opt/iobroker/node_modules/iobroker.sayit/node_modules/aws-sdk/node_modules/.bin/uuid npm ERR! code EEXIST npm ERR! Refusing to delete /opt/iobroker/node_modules/iobroker.sayit/node_modules/aws-sdk/node_modules/.bin/uuid: is outside /opt/iobroker/node_modules/iobroker.sayit/node_modules/aws-sdk/node_modules/uuid and not a link npm ERR! File exists: /opt/iobroker/node_modules/iobroker.sayit/node_modules/aws-sdk/node_modules/.bin/uuid npm ERR! Move it away, and try again. npm ERR! Please include the following file with any support request:npm ERR! /npm-debug.log host.ioBrokerTest install adapter sayit npm install iobroker.sayit --production --prefix "/opt/iobroker" (System call) npm WARN optional SKIPPING OPTIONAL DEPENDENCY: xpc-connection@~0.1.4 (node_modules/iobroker.radar/node_modules/noble/node_modules/xpc-connection):npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for xpc-connection@0.1.4: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"arm"}) npm WARN optional SKIPPING OPTIONAL DEPENDENCY: xpc-connection@~0.1.4 (node_modules/noble/node_modules/xpc-connection): npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for xpc-connection@0.1.4: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"arm"}) npm WARN enoent ENOENT: no such file or directory, open '/opt/iobroker/node_modules/aws-sdk/package.json' npm WARN enoent ENOENT: no such file or directory, open '/opt/iobroker/node_modules/iobroker.vuplus/package.json' npm ERR! Linux 4.9.41-v7+ npm ERR! argv "/usr/bin/nodejs" "/usr/bin/npm" "install" "iobroker.sayit" "--production" "--prefix" "/opt/iobroker" npm ERR! node v6.11.2 npm ERR! npm v3.10.10 npm ERR! path /opt/iobroker/node_modules/iobroker.sayit/node_modules/aws-sdk/node_modules/.bin/uuid npm ERR! code EEXIST npm ERR! Refusing to delete /opt/iobroker/node_modules/iobroker.sayit/node_modules/aws-sdk/node_modules/.bin/uuid: is outside /opt/iobroker/node_modules/iobroker.sayit/node_modules/aws-sdk/node_modules/uuid and not a link npm ERR! File exists: /opt/iobroker/node_modules/iobroker.sayit/node_modules/aws-sdk/node_modules/.bin/uuid npm ERR! Move it away, and try again. npm ERR! Please include the following file with any support request:npm ERR! /npm-debug.log host.ioBrokerTest install adapter sayit ERROR: host.ioBrokerTest Cannot install sayit ERROR: process exited with code 13
was mache ich denn verkehrt?
Gruss
-
Schau mal die Fehlermeldung an.über „Move it away and try again“ steht ein Pfad. Lösch den mal und versuche nochmal.
-
genau das war das. Super . Danke. erledigt
-
Jetzt habe ich wieder ein neues Problem.
Über die home 24 app wird kein Ton mehr ausgegeben. Es erscheint dort auch nichts mehr im log.
Über den Browser geht es aber.
Vor ein paar Tagen hat das noch funktioniert. Ich meine das seit der 1.6.2 der Fehler ist.