Navigation

    Logo
    • Register
    • Login
    • Search
    • Recent
    • Tags
    • Unread
    • Categories
    • Unreplied
    • Popular
    • GitHub
    • Docu
    • Hilfe
    1. Home
    2. Deutsch
    3. ioBroker Allgemein
    4. Zigbee Stick

    NEWS

    • Neuer Blog: Fotos und Eindrücke aus Solingen

    • ioBroker@Smart Living Forum Solingen, 14.06. - Agenda added

    • ioBroker goes Matter ... Matter Adapter in Stable

    Zigbee Stick

    This topic has been deleted. Only users with topic management privileges can see it.
    • D
      duffbeer2000 @Negalein last edited by

      @Negalein Entferne mal die Zigbee Instanz komplett und anschließend unter Adapter den Zigbee Adapter löschen. Danach npm rebuild (obs das nochmal braucht weiß ich nicht) und dann den Adapter wieder installieren

      Negalein 1 Reply Last reply Reply Quote 0
      • Negalein
        Negalein Global Moderator @duffbeer2000 last edited by

        @duffbeer2000 sagte in Zigbee Stick:

        @Negalein Entferne mal die Zigbee Instanz komplett und anschließend unter Adapter den Zigbee Adapter löschen. Danach npm rebuild (obs das nochmal braucht weiß ich nicht) und dann den Adapter wieder installieren

        Ok, Instanz gelöscht, Adapter gelöscht.
        npm rebuild (jetzt sind einige Meldungen mehr gekommen):

        /opt/iobroker$ npm rebuild
        
        
        > serialport@6.2.2 install /opt/iobroker/node_modules/iobroker.discovery/node_modules/serialport
        > prebuild-install || node-gyp rebuild
        
        
        > iobroker.javascript@4.0.12 postinstall /opt/iobroker/node_modules/iobroker.javascript
        > node ./install/installTypings.js
        
        Installing NodeJS typings...
        latest @types: 11, installed node: 8
        
        > iobroker.js-controller@1.4.2 preinstall /opt/iobroker/node_modules/iobroker.js-controller
        > node lib/preinstall_check.js
        
        NPM version: 6.4.1
        npm version >= 5: disabling package-lock
        
        > iobroker.js-controller@1.4.2 install /opt/iobroker/node_modules/iobroker.js-controller
        > node iobroker.js setup first
        
        
        > ursa-optional@0.9.8 install /opt/iobroker/node_modules/iobroker.js-controller/node_modules/greenlock/node_modules/rsa-compat/node_modules/ursa-optional
        > node rebuild.js
        
        
        > bluetooth-hci-socket@0.5.1 install /opt/iobroker/node_modules/iobroker.radar/node_modules/bluetooth-hci-socket
        > node-gyp rebuild
        
        make: Verzeichnis „/opt/iobroker/node_modules/iobroker.radar/node_modules/bluetooth-hci-socket/build“ wird betreten
          CXX(target) Release/obj.target/binding/src/BluetoothHciSocket.o
        ../src/BluetoothHciSocket.cpp: In member function ‘void BluetoothHciSocket::poll()’:
        ../src/BluetoothHciSocket.cpp:251:95: warning: ‘v8::Local<v8::Value> Nan::MakeCallback(v8::Local<v8::Object>, v8::Local<v8::String>, int, v8::Local<v8::Value>*)’ is deprecated [-Wdeprecated-declarations]
             Nan::MakeCallback(Nan::New<Object>(this->This), Nan::New("emit").ToLocalChecked(), 2, argv);
                                                                                                       ^
        In file included from ../src/BluetoothHciSocket.cpp:8:0:
        ../../nan/nan.h:980:46: note: declared here
           NAN_DEPRECATED inline v8::Local<v8::Value> MakeCallback(
                                                      ^~~~~~~~~~~~
        ../src/BluetoothHciSocket.cpp: In member function ‘void BluetoothHciSocket::emitErrnoError()’:
        ../src/BluetoothHciSocket.cpp:275:72: warning: ‘v8::Local<v8::Object> v8::Function::NewInstance(int, v8::Local<v8::Value>*) const’ is deprecated: Use maybe version [-Wdeprecated-declarations]
           Local<Value> error = errorConstructor->NewInstance(1, constructorArgs);
                                                                                ^
        In file included from /root/.node-gyp/8.15.1/include/node/v8.h:26:0,
                         from /root/.node-gyp/8.15.1/include/node/node.h:63,
                         from /root/.node-gyp/8.15.1/include/node/node_buffer.h:25,
                         from ../src/BluetoothHciSocket.cpp:7:
        /root/.node-gyp/8.15.1/include/node/v8.h:3897:31: note: declared here
                         Local<Object> NewInstance(int argc, Local<Value> argv[]) const);
                                       ^
        /root/.node-gyp/8.15.1/include/node/v8config.h:318:3: note: in definition of macro ‘V8_DEPRECATED’
           declarator __attribute__((deprecated(message)))
           ^~~~~~~~~~
        ../src/BluetoothHciSocket.cpp:282:93: warning: ‘v8::Local<v8::Value> Nan::MakeCallback(v8::Local<v8::Object>, v8::Local<v8::String>, int, v8::Local<v8::Value>*)’ is deprecated [-Wdeprecated-declarations]
           Nan::MakeCallback(Nan::New<Object>(this->This), Nan::New("emit").ToLocalChecked(), 2, argv);
                                                                                                     ^
        In file included from ../src/BluetoothHciSocket.cpp:8:0:
        ../../nan/nan.h:980:46: note: declared here
           NAN_DEPRECATED inline v8::Local<v8::Value> MakeCallback(
                                                      ^~~~~~~~~~~~
          SOLINK_MODULE(target) Release/obj.target/binding.node
          COPY Release/binding.node
        make: Verzeichnis „/opt/iobroker/node_modules/iobroker.radar/node_modules/bluetooth-hci-socket/build“ wird verlassen
        
        > usb@1.5.0 install /opt/iobroker/node_modules/iobroker.radar/node_modules/usb
        > node-pre-gyp install --fallback-to-build
        
        node-pre-gyp
        WARN Using request for node-pre-gyp https download 
        [usb] Success: "/opt/iobroker/node_modules/iobroker.radar/node_modules/usb/src/binding/usb_bindings.node" already installed
        Pass --update-binary to reinstall or --build-from-source to recompile
        
        > @abandonware/bluetooth-hci-socket@0.5.3-1 preinstall /opt/iobroker/node_modules/iobroker.radar/node_modules/@abandonware/bluetooth-hci-socket
        > npm install node-pre-gyp
        
        npm
        notice created a lockfile as package-lock.json. You should commit this file.
        + node-pre-gyp@0.12.0
        added 66 packages from 25 contributors and audited 95 packages in 5.987s
        found 0 vulnerabilities
        
        
        > @abandonware/bluetooth-hci-socket@0.5.3-1 install /opt/iobroker/node_modules/iobroker.radar/node_modules/@abandonware/bluetooth-hci-socket
        > node-pre-gyp install --fallback-to-build
        
        node-pre-gyp
        WARN Using request for node-pre-gyp https download 
        [@abandonware/bluetooth-hci-socket] Success: "/opt/iobroker/node_modules/iobroker.radar/node_modules/@abandonware/bluetooth-hci-socket/lib/binding/binding.node" already installed
        Pass --update-binary to reinstall or --build-from-source to recompile
        
        > bluetooth-hci-socket@0.5.1 install /opt/iobroker/node_modules/iobroker.radar/node_modules/bluetooth-hci-socket
        > node-gyp rebuild
        
        make: Verzeichnis „/opt/iobroker/node_modules/iobroker.radar/node_modules/bluetooth-hci-socket/build“ wird betreten
          CXX(target) Release/obj.target/binding/src/BluetoothHciSocket.o
        ../src/BluetoothHciSocket.cpp: In member function ‘void BluetoothHciSocket::poll()’:
        ../src/BluetoothHciSocket.cpp:251:95: warning: ‘v8::Local<v8::Value> Nan::MakeCallback(v8::Local<v8::Object>, v8::Local<v8::String>, int, v8::Local<v8::Value>*)’ is deprecated [-Wdeprecated-declarations]
             Nan::MakeCallback(Nan::New<Object>(this->This), Nan::New("emit").ToLocalChecked(), 2, argv);
                                                                                                       ^
        In file included from ../src/BluetoothHciSocket.cpp:8:0:
        ../../nan/nan.h:980:46: note: declared here
           NAN_DEPRECATED inline v8::Local<v8::Value> MakeCallback(
                                                      ^~~~~~~~~~~~
        ../src/BluetoothHciSocket.cpp: In member function ‘void BluetoothHciSocket::emitErrnoError()’:
        ../src/BluetoothHciSocket.cpp:275:72: warning: ‘v8::Local<v8::Object> v8::Function::NewInstance(int, v8::Local<v8::Value>*) const’ is deprecated: Use maybe version [-Wdeprecated-declarations]
           Local<Value> error = errorConstructor->NewInstance(1, constructorArgs);
                                                                                ^
        In file included from /root/.node-gyp/8.15.1/include/node/v8.h:26:0,
                         from /root/.node-gyp/8.15.1/include/node/node.h:63,
                         from /root/.node-gyp/8.15.1/include/node/node_buffer.h:25,
                         from ../src/BluetoothHciSocket.cpp:7:
        /root/.node-gyp/8.15.1/include/node/v8.h:3897:31: note: declared here
                         Local<Object> NewInstance(int argc, Local<Value> argv[]) const);
                                       ^
        /root/.node-gyp/8.15.1/include/node/v8config.h:318:3: note: in definition of macro ‘V8_DEPRECATED’
           declarator __attribute__((deprecated(message)))
           ^~~~~~~~~~
        ../src/BluetoothHciSocket.cpp:282:93: warning: ‘v8::Local<v8::Value> Nan::MakeCallback(v8::Local<v8::Object>, v8::Local<v8::String>, int, v8::Local<v8::Value>*)’ is deprecated [-Wdeprecated-declarations]
           Nan::MakeCallback(Nan::New<Object>(this->This), Nan::New("emit").ToLocalChecked(), 2, argv);
                                                                                                     ^
        In file included from ../src/BluetoothHciSocket.cpp:8:0:
        ../../nan/nan.h:980:46: note: declared here
           NAN_DEPRECATED inline v8::Local<v8::Value> MakeCallback(
                                                      ^~~~~~~~~~~~
          SOLINK_MODULE(target) Release/obj.target/binding.node
          COPY Release/binding.node
        make: Verzeichnis „/opt/iobroker/node_modules/iobroker.radar/node_modules/bluetooth-hci-socket/build“ wird verlassen
        
        > usb@1.5.0 install /opt/iobroker/node_modules/iobroker.radar/node_modules/usb
        > node-pre-gyp install --fallback-to-build
        
        (node:4437) MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 11 SIGINT listeners added. Use emitter.setMaxListeners() to increase limit
        node-pre-gyp
        WARN Using request for node-pre-gyp https download 
        [usb] Success: "/opt/iobroker/node_modules/iobroker.radar/node_modules/usb/src/binding/usb_bindings.node" already installed
        Pass --update-binary to reinstall or --build-from-source to recompile
        
        > node-cron@2.0.3 postinstall /opt/iobroker/node_modules/iobroker.sourceanalytix/node_modules/node-cron
        > opencollective-postinstall
        
        96Thank you for using node-cron!96
        96If you rely on this package, please consider supporting our open collective:
        > 94https://opencollective.com/node-cron/donate
        
        
        > iobroker.vis@1.1.10 install /opt/iobroker/node_modules/iobroker.vis
        > node main.js --install
        
        
        > bluetooth-hci-socket@0.5.1 install /opt/iobroker/node_modules/bluetooth-hci-socket
        > node-gyp rebuild
        
        make: Verzeichnis „/opt/iobroker/node_modules/bluetooth-hci-socket/build“ wird betreten
          CXX(target) Release/obj.target/binding/src/BluetoothHciSocket.o
        ../src/BluetoothHciSocket.cpp: In member function ‘void BluetoothHciSocket::poll()’:
        ../src/BluetoothHciSocket.cpp:251:95: warning: ‘v8::Local<v8::Value> Nan::MakeCallback(v8::Local<v8::Object>, v8::Local<v8::String>, int, v8::Local<v8::Value>*)’ is deprecated [-Wdeprecated-declarations]
             Nan::MakeCallback(Nan::New<Object>(this->This), Nan::New("emit").ToLocalChecked(), 2, argv);
                                                                                                       ^
        In file included from ../src/BluetoothHciSocket.cpp:8:0:
        ../../nan/nan.h:979:46: note: declared here
           NAN_DEPRECATED inline v8::Local<v8::Value> MakeCallback(
                                                      ^~~~~~~~~~~~
        ../src/BluetoothHciSocket.cpp: In member function ‘void BluetoothHciSocket::emitErrnoError()’:
        ../src/BluetoothHciSocket.cpp:275:72: warning: ‘v8::Local<v8::Object> v8::Function::NewInstance(int, v8::Local<v8::Value>*) const’ is deprecated: Use maybe version [-Wdeprecated-declarations]
           Local<Value> error = errorConstructor->NewInstance(1, constructorArgs);
                                                                                ^
        In file included from /root/.node-gyp/8.15.1/include/node/v8.h:26:0,
                         from /root/.node-gyp/8.15.1/include/node/node.h:63,
                         from /root/.node-gyp/8.15.1/include/node/node_buffer.h:25,
                         from ../src/BluetoothHciSocket.cpp:7:
        /root/.node-gyp/8.15.1/include/node/v8.h:3897:31: note: declared here
                         Local<Object> NewInstance(int argc, Local<Value> argv[]) const);
                                       ^
        /root/.node-gyp/8.15.1/include/node/v8config.h:318:3: note: in definition of macro ‘V8_DEPRECATED’
           declarator __attribute__((deprecated(message)))
           ^~~~~~~~~~
        ../src/BluetoothHciSocket.cpp:282:93: warning: ‘v8::Local<v8::Value> Nan::MakeCallback(v8::Local<v8::Object>, v8::Local<v8::String>, int, v8::Local<v8::Value>*)’ is deprecated [-Wdeprecated-declarations]
           Nan::MakeCallback(Nan::New<Object>(this->This), Nan::New("emit").ToLocalChecked(), 2, argv);
                                                                                                     ^
        In file included from ../src/BluetoothHciSocket.cpp:8:0:
        ../../nan/nan.h:979:46: note: declared here
           NAN_DEPRECATED inline v8::Local<v8::Value> MakeCallback(
                                                      ^~~~~~~~~~~~
          SOLINK_MODULE(target) Release/obj.target/binding.node
          COPY Release/binding.node
        make: Verzeichnis „/opt/iobroker/node_modules/bluetooth-hci-socket/build“ wird verlassen
        
        > grpc@1.18.0 install /opt/iobroker/node_modules/grpc
        > node-pre-gyp install --fallback-to-build --library=static_library
        
        node-pre-gyp
        WARN Using request for node-pre-gyp https download 
        [grpc] Success: "/opt/iobroker/node_modules/grpc/src/node/extension_binary/node-v57-linux-x64-glibc/grpc_node.node" is installed via remote
        
        > node-cron@2.0.3 postinstall /opt/iobroker/node_modules/node-cron
        > opencollective-postinstall
        
        96Thank you for using node-cron!96
        96If you rely on this package, please consider supporting our open collective:
        > 94https://opencollective.com/node-cron/donate
        
        
        > iobroker.vis-google-fonts@0.1.0 install /opt/iobroker/node_modules/iobroker.vis-google-fonts
        > node main.js --install
        
        
        > ursa-optional@0.9.10 install /opt/iobroker/node_modules/ursa-optional
        > node rebuild.js
        
        
        > usb@1.5.0 install /opt/iobroker/node_modules/usb
        > node-pre-gyp install --fallback-to-build
        
        module.js:550
            throw err;
            ^
        
        Error: Cannot find module 'npmlog'
            at Function.Module._resolveFilename (module.js:548:15)
            at Function.Module._load (module.js:475:25)
            at Module.require (module.js:597:17)
            at require (internal/module.js:11:18)
            at Object.<anonymous> (/opt/iobroker/node_modules/usb/node_modules/node-pre-gyp/lib/node-pre-gyp.js:16:11)
            at Module._compile (module.js:653:30)
            at Object.Module._extensions..js (module.js:664:10)
            at Module.load (module.js:566:32)
            at tryModuleLoad (module.js:506:12)
            at Function.Module._load (module.js:498:3)
        npm
        ERR! code ELIFECYCLE
        npm ERR!
        errno 1
        npm
        ERR! usb@1.5.0 install: `node-pre-gyp install --fallback-to-build`
        npm ERR! Exit status 1
        npm ERR!
        
        npm ERR! Failed at the usb@1.5.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!     /root/.npm/_logs/2019-04-09T18_07_37_792Z-debug.log
        /opt/iobroker$  
        

        Dann versucht den Adapter wieder zu installieren.
        Jetzt mag er mich nicht mehr!

        Fertig mit Fehler: host.ioBroker Cannot install zigbee

        $ ./iobroker add zigbee  --host ioBroker
        NPM version: 6.4.1
        npm install iobroker.zigbee --production --save --prefix "/opt/iobroker" (System call)
        gyp
         ERR! clean error gyp ERR! stack Error: EACCES: permission denied, rmdir 'build'
        
        gyp ERR! System Linux 4.4.59+gyp ERR! command "/usr/bin/node" "/usr/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "rebuild"
        gyp ERR! cwd /opt/iobroker/node_modules/authenticate-pam
        gyp ERR! node -v v8.15.1
        gyp ERR!
         node-gyp -v v3.8.0gyp ERR! not ok 
        
        sh: 1: 
        prebuild-install: Permission denied
        gyp
         WARN EACCES user "undefined" does not have permission to access the dev dir "/root/.node-gyp/8.15.1"gyp WARN EACCES attempting to reinstall using temporary dev dir "/opt/iobroker/node_modules/serialport/.node-gyp"
        
        gyp
         WARN install got an error, rolling back install
        gyp WARN install got an error, rolling back install
        gyp
         ERR! configure error gyp ERR! stack Error: EACCES: permission denied, stat '/opt/iobroker/node_modules/serialport/.node-gyp/8.15.1'
        gyp
         ERR! System Linux 4.4.59+gyp ERR! command "/usr/bin/node" "/usr/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "rebuild"
        gyp ERR! cwd /opt/iobroker/node_modules/serialport
        gyp ERR! node -v v8.15.1
        gyp ERR! 
        node-gyp -v v3.8.0gyp ERR! not ok 
        
        npm
         WARN bl@0.7.0 requires a peer of stream-browserify@* but none is installed. You must install peer dependencies yourself.npm WARN optional SKIPPING OPTIONAL DEPENDENCY: xpc-connection@0.1.4 (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":"x64"})npm WARN optional SKIPPING OPTIONAL DEPENDENCY: osx-temperature-sensor@1.0.3 (node_modules/osx-temperature-sensor):
        npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for osx-temperature-sensor@1.0.3: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})
        
        npm 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`
        npm WARN optional SKIPPING OPTIONAL DEPENDENCY: Exit status 1
        
        
        npm
         ERR! code ELIFECYCLEnpm ERR! errno 1
        
        npm ERR! serialport@6.2.2 install: `prebuild-install || node-gyp rebuild`npm ERR! Exit status 1
        npm ERR! 
        npm ERR! Failed at the serialport@6.2.2 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!     /root/.npm/_logs/2019-04-09T18_09_28_103Z-debug.log
        
        host.ioBroker install adapter zigbee
        NPM version: 6.4.1
        npm install iobroker.zigbee --production --save --prefix "/opt/iobroker" (System call)
        gyp
         ERR! clean error 
        gyp ERR! stack Error: EACCES: permission denied, rmdir 'build'gyp ERR! System Linux 4.4.59+
        
        gyp ERR! command "/usr/bin/node" "/usr/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "rebuild"gyp ERR! cwd /opt/iobroker/node_modules/authenticate-pam
        gyp ERR! node -v v8.15.1
        gyp ERR! node-gyp -v v3.8.0
        gyp ERR! not ok
         
        sh: 1: prebuild-install: Permission denied
        gyp
         WARN EACCES user "undefined" does not have permission to access the dev dir "/root/.node-gyp/8.15.1"gyp WARN EACCES attempting to reinstall using temporary dev dir "/opt/iobroker/node_modules/serialport/.node-gyp"
        
        gyp WARN install got an error, rolling back install
        gyp
         WARN install got an error, rolling back install
        gyp ERR! configure error gyp ERR! stack Error: EACCES: permission denied, stat '/opt/iobroker/node_modules/serialport/.node-gyp/8.15.1'
        gyp
         ERR! System Linux 4.4.59+gyp ERR! command "/usr/bin/node" "/usr/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "rebuild"
        gyp ERR! cwd /opt/iobroker/node_modules/serialport
        gyp ERR! node -v v8.15.1
        gyp ERR! node-gyp -v v3.8.0
        gyp ERR! not ok 
        
        npm WARN bl@0.7.0 requires a peer of stream-browserify@* but none is installed. You must install peer dependencies yourself.
        npm WARN optional SKIPPING OPTIONAL DEPENDENCY: xpc-connection@0.1.4 (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":"x64"})
        npm WARN optional SKIPPING OPTIONAL DEPENDENCY: osx-temperature-sensor@1.0.3 (node_modules/osx-temperature-sensor):
        npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for osx-temperature-sensor@1.0.3: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})
        npm 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`
        npm WARN optional SKIPPING OPTIONAL DEPENDENCY: Exit status 1
        
        
        npm ERR! code ELIFECYCLEnpm ERR! errno 1
        
        npm ERR! serialport@6.2.2 install: `prebuild-install || node-gyp rebuild`npm ERR! Exit status 1
        npm ERR! 
        npm ERR! Failed at the serialport@6.2.2 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!     /root/.npm/_logs/2019-04-09T18_10_24_186Z-debug.log
        
        host.ioBroker install adapter zigbee
        NPM version: 6.4.1
        npm install iobroker.zigbee --production --save --prefix "/opt/iobroker" (System call)
        gyp
         ERR! clean error 
        gyp ERR! stack Error: EACCES: permission denied, rmdir 'build'gyp ERR! System Linux 4.4.59+
        
        gyp ERR! command "/usr/bin/node" "/usr/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "rebuild"gyp ERR! cwd /opt/iobroker/node_modules/authenticate-pam
        gyp ERR! node -v v8.15.1
        gyp ERR! 
        node-gyp -v v3.8.0gyp ERR! not ok 
        
        sh: 1: 
        prebuild-install: Permission denied
        gyp
         WARN EACCES user "undefined" does not have permission to access the dev dir "/root/.node-gyp/8.15.1"
        gyp WARN EACCES attempting to reinstall using temporary dev dir "/opt/iobroker/node_modules/serialport/.node-gyp"
        gyp
         WARN install got an error, rolling back install
        gyp
         WARN install got an error, rolling back install
        gyp ERR! configure error gyp ERR! stack Error: EACCES: permission denied, stat '/opt/iobroker/node_modules/serialport/.node-gyp/8.15.1'
        
        gyp ERR! System Linux 4.4.59+gyp
         ERR! command "/usr/bin/node" "/usr/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "rebuild"gyp ERR! cwd /opt/iobroker/node_modules/serialport
        gyp ERR! node -v v8.15.1
        gyp ERR! node-gyp -v v3.8.0
        gyp ERR! not ok
         
        npm WARN bl@0.7.0 requires a peer of stream-browserify@* but none is installed. You must install peer dependencies yourself.npm WARN optional SKIPPING OPTIONAL DEPENDENCY: xpc-connection@0.1.4 (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":"x64"})
        
        npm WARN optional SKIPPING OPTIONAL DEPENDENCY: osx-temperature-sensor@1.0.3 (node_modules/osx-temperature-sensor):npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for osx-temperature-sensor@1.0.3: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})
        npm 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`
        npm WARN optional SKIPPING OPTIONAL DEPENDENCY: Exit status 1
        
        npm ERR! code ELIFECYCLE
        npm ERR! errno 1
        npm ERR! serialport@6.2.2 install: `prebuild-install || node-gyp rebuild`
        npm ERR! Exit status 1
        npm ERR! 
        npm ERR! Failed at the serialport@6.2.2 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!     /root/.npm/_logs/2019-04-09T18_11_20_240Z-debug.log
        
        host.ioBroker install adapter zigbee
        ERROR: host.ioBroker Cannot install zigbee
        ERROR: process exited with code 13
        

        D 1 Reply Last reply Reply Quote 0
        • D
          duffbeer2000 @Negalein last edited by

          @Negalein Puhh, jetzt bin ich mit meinem Latein am Ende. Da passt irgendwas überhaupt nicht. Dein ioBroker läuft in nem Docker Container oder?

          Negalein 1 Reply Last reply Reply Quote 0
          • Negalein
            Negalein Global Moderator last edited by

            @duffbeer2000

            weiter gehts!
            Und es schaut jetzt schon viel viel besser aus!

            Ich habe jetzt über das Terminal ein npm install iobroker.zigbee gemacht

            /opt/iobroker$ npm install iobroker.zigbee
            
            
            > authenticate-pam@1.0.2 install /opt/iobroker/node_modules/authenticate-pam
            > node-gyp rebuild
            
            make: Verzeichnis „/opt/iobroker/node_modules/authenticate-pam/build“ wird betreten
              CXX(target) Release/obj.target/authenticate_pam/authenticate_pam.o
            ../authenticate_pam.cc: In function ‘void after_doing_auth(uv_work_t*, int)’:
            ../authenticate_pam.cc:107:87: warning: ‘v8::Local<v8::Value> Nan::MakeCallback(v8::Local<v8::Object>, v8::Local<v8::Function>, int, v8::Local<v8::Value>*)’ is deprecated [-Wdeprecated-declarations]
               Nan::MakeCallback(Nan::GetCurrentContext()->Global(), Nan::New(m->callback), 1, args);
                                                                                                   ^
            In file included from ../authenticate_pam.cc:23:0:
            ../../nan/nan.h:958:46: note: declared here
               NAN_DEPRECATED inline v8::Local<v8::Value> MakeCallback(
                                                          ^~~~~~~~~~~~
              SOLINK_MODULE(target) Release/obj.target/authenticate_pam.node
              COPY Release/authenticate_pam.node
            make: Verzeichnis „/opt/iobroker/node_modules/authenticate-pam/build“ wird verlassen
            
            > serialport@6.2.2 install /opt/iobroker/node_modules/serialport
            > prebuild-install || node-gyp rebuild
            
            npm
            WARN bl@0.7.0 requires a peer of stream-browserify@* but none is installed. You must install peer dependencies yourself.
            npm
            WARN optional SKIPPING OPTIONAL DEPENDENCY: xpc-connection@0.1.4 (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":"x64"})
            npm
            WARN optional SKIPPING OPTIONAL DEPENDENCY: osx-temperature-sensor@1.0.3 (node_modules/osx-temperature-sensor):
            npm WARN
            notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for osx-temperature-sensor@1.0.3: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})
            
            + iobroker.zigbee@0.10.3
            added 114 packages from 51 contributors and audited 32556 packages in 59.347s
            found 62 vulnerabilities (44 low, 5 moderate, 13 high)
              run `npm audit fix` to fix them, or `npm audit` for details
            

            Dann den Adapter über Admin nochmal installiert.
            Jetzt ist er da, bleibt aber gelb!

            
            zigbee.0	2019-04-09 20:30:18.681	error	Error while starting zigbee-shepherd!. Error: Error: Is a directory, cannot open /dev/ttyACM0
            zigbee.0	2019-04-09 20:30:18.677	info	Starting zigbee-shepherd
            zigbee.0	2019-04-09 20:29:18.675	info	Error while starting zigbee-shepherd, attempting to fix... (takes 60 seconds)
            zigbee.0	2019-04-09 20:29:18.645	info	Reset coordinator
            zigbee.0	2019-04-09 20:29:18.616	info	Queue is: true
            zigbee.0	2019-04-09 20:29:18.616	info	Start on port: /dev/ttyACM0 with panID 6754 channel 11
            zigbee.0	2019-04-09 20:29:18.609	info	starting. Version 0.10.3 in /opt/iobroker/node_modules/iobroker.zigbee, node: v8.15.1
            zigbee.0	2019-04-09 20:29:02.413	error	Error: spawn udevadm ENOENT
            zigbee.0	2019-04-09 20:28:59.532	error	Serial port not selected! Go to settings page.
            zigbee.0	2019-04-09 20:28:59.525	info	starting. Version 0.10.3 in /opt/iobroker/node_modules/iobroker.zigbee, node: v8.15.1
            

            1 Reply Last reply Reply Quote 0
            • Negalein
              Negalein Global Moderator @duffbeer2000 last edited by

              @duffbeer2000 sagte in Zigbee Stick:

              Dein ioBroker läuft in nem Docker Container oder?

              Ja, ich hab ihn auf der Synology unter Docker installiert.

              D 1 Reply Last reply Reply Quote 0
              • D
                duffbeer2000 @Negalein last edited by duffbeer2000

                @Negalein Ok, traust dir folgendes zu:

                1. Deinen ioBroker Container stoppen
                2. Deinen iobroker Ordner kopieren in z.B.: iobroker2
                3. Einen neuen ioBroker Container anlegen und den iobroker2 Ordner nach /opt/iobroker mounten. Als Image könntest du mal meinen Container testen: duffbeer2000/iobroker:latest sollte es an den Berechtigungen liegen sollte der dann laufen da er sie korrigiert.

                Wenn nicht, kann ich dir auch über Teamviewer helfen.

                Negalein arteck 2 Replies Last reply Reply Quote 0
                • MyzerAT
                  MyzerAT last edited by

                  was mich verwirrt ist das der error meint er kann auf /dev/ttyACM0 nicht zugreifen, hast du noch andere sachen an den usb ports der syno angesteckt?

                  Negalein 1 Reply Last reply Reply Quote 0
                  • Negalein
                    Negalein Global Moderator @duffbeer2000 last edited by

                    @duffbeer2000 sagte in Zigbee Stick:

                    @Negalein Ok, traust dir folgendes zu:

                    1. Deinen ioBroker Container stoppen
                    2. Deinen iobroker Ordner kopieren in z.B.: iobroker2
                    3. Einen neuen ioBroker Container anlegen und den iobroker2 Ordner nach /opt/iobroker mounten. Als Image könntest du mal meinen Container testen: duffbeer2000/iobroker:latest sollte es an den Berechtigungen liegen sollte der dann laufen da er sie korrigiert.

                    Wenn nicht, kann ich dir auch über Teamviewer helfen.

                    Klar, gerne.
                    Aber lieber über Teamviewer!
                    Nicht dass ich dann durch meine Schusseligkeit alles verliere.

                    Aktuell hab ich den Container von Buanet inkl. seinem Sicherungsscript laufen.

                    1 Reply Last reply Reply Quote 0
                    • Negalein
                      Negalein Global Moderator @MyzerAT last edited by

                      @MyzerAT sagte in Zigbee Stick:

                      was mich verwirrt ist das der error meint er kann auf /dev/ttyACM0 nicht zugreifen, hast du noch andere sachen an den usb ports der syno angesteckt?

                      Ich hatte einen BT-Dongle am USB. Aber seit gestern nicht mehr, da er eh nie auf der Syno erkannt wurde.

                      mit cd /dev/ttyACM0 sagt er auch, dass es das Verzeichnis nicht gibt.

                      MyzerAT 1 Reply Last reply Reply Quote 0
                      • MyzerAT
                        MyzerAT @Negalein last edited by

                        @Negalein

                        hast du nur /dev/ttyACM0 oder gibt es noch ein anderes /dev/ttyACM*

                        Negalein 1 Reply Last reply Reply Quote 0
                        • Negalein
                          Negalein Global Moderator @MyzerAT last edited by

                          @MyzerAT sagte in Zigbee Stick:

                          @Negalein

                          hast du nur /dev/ttyACM0 oder gibt es noch ein anderes /dev/ttyACM*

                          Nein, nur das ttyACM0

                          Dieses Verzeichnis ist leer

                          /dev/ttyACM0$ ls
                          /dev/ttyACM0$

                          1 Reply Last reply Reply Quote 0
                          • arteck
                            arteck Developer Most Active @duffbeer2000 last edited by

                            @duffbeer2000 das ist jetzt nicht dein ernst oder.. ich verstehe nicht warum Leute sich nicht zurück halten können ...

                            du bringst den @Negalein ins bredouille wo der Fehler einfach zu beheben währe.. jetzt soll er schon Docker Container neu installieren .. was kommt demnächs kauf Hardware neu..

                            man man man

                            D Negalein 2 Replies Last reply Reply Quote 0
                            • D
                              duffbeer2000 @arteck last edited by duffbeer2000

                              @arteck Deshalb hatte ich ja zuerst auf dich verwiesen, da ich mir nicht sicher war:
                              "@arteck Ich glaube da kennst du dich besser aus. Würde sagen ein npm rebuild wäre notwendig."
                              Da Negalein aber dann direkt das npm rebuild ausgeführt hat dachte ich mir sicherheitshalber den Insallationsordner kopieren und in einem weiteren Container testen und das original bestehen lassen. Das ist ne Sache von 5min und kostet nichts.

                              1 Reply Last reply Reply Quote 0
                              • Negalein
                                Negalein Global Moderator @arteck last edited by

                                @arteck sagte in Zigbee Stick:

                                wo der Fehler einfach zu beheben währe..

                                Mahlzeit

                                Was könnte ich noch probieren?

                                Danke

                                1 Reply Last reply Reply Quote 0
                                • MyzerAT
                                  MyzerAT last edited by

                                  siehst du mit was für eine Version der Stick geflasht wurde? den was mich wundert ist, das die grüne LED ausgeht und du aber in der Instanz gar nicht das Häkchen gesetzt hast, das es aus sein soll!

                                  7bbcd2a9-920e-44b1-bb04-0c943e0368db-grafik.png

                                  Negalein 1 Reply Last reply Reply Quote 0
                                  • Negalein
                                    Negalein Global Moderator @MyzerAT last edited by

                                    @MyzerAT sagte in Zigbee Stick:

                                    siehst du mit was für eine Version der Stick geflasht wurde? den was mich wundert ist, das die grüne LED ausgeht und du aber in der Instanz gar nicht das Häkchen gesetzt hast, das es aus sein soll!

                                    Nein, kann ich leider nicht sagen.
                                    Ich hab ihn vor 1 Woche von @stother gekauft.

                                    MyzerAT 1 Reply Last reply Reply Quote 0
                                    • MyzerAT
                                      MyzerAT @Negalein last edited by MyzerAT

                                      @Negalein

                                      ich habe auch den Stick von Ihm und er funktioniert einwandfrei, eventuell hat der Stick ja was, kann ja mal passieren, ist nur eine Möglichkeit, muss jedoch nicht sein, ich würde das mal prüfen. nur wie prüft man das ? Den mich wundert das bei dir die LED ausgeht, obwohl du das Häkchen nicht gesetzt hast!

                                      1 Reply Last reply Reply Quote 0
                                      • MyzerAT
                                        MyzerAT last edited by MyzerAT

                                        1. stopp mal die zigbee instanz
                                        2. schau im Terminal nach ob noch zigbee prozesse laufen "ps -ax | grep -e zigbee" wenn ja kill diese "killall -q io.zigbee" und einzelne Prozesse mit "kill Prozessnummer"
                                        3. steck den Stick aus , wieder ein
                                        4. starte die instanz und poste hier mal das log!
                                        Negalein 1 Reply Last reply Reply Quote 0
                                        • Negalein
                                          Negalein Global Moderator @MyzerAT last edited by

                                          @MyzerAT sagte in Zigbee Stick:

                                          1. starte die instanz und poste hier mal das log!
                                          zigbee.0	2019-04-10 12:50:49.910	debug	User stateChange zigbee.0.info.connection {"val":false,"ack":false,"ts":1554893449906,"q":0,"from":"system.adapter.zigbee.0","lc":1554834618681}
                                          zigbee.0	2019-04-10 12:50:49.910	debug	User stateChange zigbee.0.info.pairingMessage {"val":"Error: Error while starting zigbee-shepherd!. Error: Error: Is a directory, cannot open /dev/ttyACM0/","ack":false,"ts":1554893449905,"q":0,"from"
                                          zigbee.0	2019-04-10 12:50:49.905	error	Error while starting zigbee-shepherd!. Error: Error: Is a directory, cannot open /dev/ttyACM0/
                                          zigbee.0	2019-04-10 12:50:49.902	info	Starting zigbee-shepherd
                                          zigbee.0	2019-04-10 12:50:18.253	debug	system.adapter.admin.0: logging true
                                          zigbee.0	2019-04-10 12:50:08.729	debug	sendTo "getGroups" to system.adapter.admin.0 from system.adapter.zigbee.0
                                          zigbee.0	2019-04-10 12:50:08.729	debug	getGroups result: {}
                                          zigbee.0	2019-04-10 12:50:08.725	debug	sendTo "getDevices" to system.adapter.admin.0 from system.adapter.zigbee.0
                                          zigbee.0	2019-04-10 12:50:08.709	debug	sendTo "listUart" to system.adapter.admin.0 from system.adapter.zigbee.0
                                          zigbee.0	2019-04-10 12:50:08.708	debug	List of ports: []
                                          zigbee.0	2019-04-10 12:50:08.707	error	Error: spawn udevadm ENOENT
                                          zigbee.0	2019-04-10 12:49:49.899	info	Error while starting zigbee-shepherd, attempting to fix... (takes 60 seconds)
                                          zigbee.0	2019-04-10 12:49:49.893	info	Reset coordinator
                                          zigbee.0	2019-04-10 12:49:49.865	info	Queue is: true
                                          zigbee.0	2019-04-10 12:49:49.864	info	Start on port: /dev/ttyACM0/ with panID 6754 channel 11
                                          zigbee.0	2019-04-10 12:49:49.862	info	starting. Version 0.10.3 in /opt/iobroker/node_modules/iobroker.zigbee, node: v8.15.1
                                          zigbee.0	2019-04-10 12:49:49.743	debug	statesDB connected
                                          zigbee.0	2019-04-10 12:49:49.710	debug	objectDB connected
                                          zigbee.0	2019-04-10 12:44:57.237	info	zigbee-shepherd stopped
                                          
                                          1 Reply Last reply Reply Quote 0
                                          • MyzerAT
                                            MyzerAT last edited by

                                            @Negalein sagte in Zigbee Stick:

                                            ebug List of ports: []

                                            für mich sieht es so aus als ob er den Stick nicht erkennt!

                                            mein log sieht so aus beim start

                                            2019-04-10 03:04:20.020 - info: host.RDJL_Home instance system.adapter.zigbee.0 started with pid 480
                                            2019-04-10 03:04:21.130 - info: zigbee.0 starting. Version 0.10.2 in /opt/iobroker/node_modules/iobroker.zigbee, node: v8.15.0
                                            2019-04-10 03:04:21.138 - info: zigbee.0 Start on port: /dev/ttyACM0 with panID 6754 channel 11
                                            2019-04-10 03:04:21.138 - info: zigbee.0 Queue is: true
                                            2019-04-10 03:04:21.176 - info: zigbee.0 Reset coordinator
                                            2019-04-10 03:04:21.780 - info: zigbee.0 zigbee-shepherd started!
                                            2019-04-10 03:04:21.790 - info: zigbee.0 zigbee-shepherd ready. version: 2.6.3 rev 20190223
                                            
                                            Negalein 1 Reply Last reply Reply Quote 0
                                            • First post
                                              Last post

                                            Support us

                                            ioBroker
                                            Community Adapters
                                            Donate
                                            FAQ Cloud / IOT
                                            HowTo: Node.js-Update
                                            HowTo: Backup/Restore
                                            Downloads
                                            BLOG

                                            683
                                            Online

                                            31.9k
                                            Users

                                            80.1k
                                            Topics

                                            1.3m
                                            Posts

                                            17
                                            68
                                            10488
                                            Loading More Posts
                                            • Oldest to Newest
                                            • Newest to Oldest
                                            • Most Votes
                                            Reply
                                            • Reply as topic
                                            Log in to reply
                                            Community
                                            Impressum | Datenschutz-Bestimmungen | Nutzungsbedingungen
                                            The ioBroker Community 2014-2023
                                            logo