Navigation

    Logo
    • Register
    • Login
    • Search
    • Recent
    • Tags
    • Unread
    • Categories
    • Unreplied
    • Popular
    • GitHub
    • Docu
    • Hilfe
    1. Home
    2. Deutsch
    3. ioBroker Allgemein
    4. Gelöst - BLE-Adapter startet nicht

    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

    Gelöst - BLE-Adapter startet nicht

    This topic has been deleted. Only users with topic management privileges can see it.
    • I
      Ingo last edited by

      Guten Morgen,

      hier das Log der Installation, ich hoffe, ich habe es richtig aus dem Konsolenfenster herausbekommen.

      root@Brix:/opt/iobroker# sudo npm i iobroker.ble --production --unsafe-perm
      npm WARN addRemoteGit Error: not found: git
      npm WARN addRemoteGit     at getNotFoundError (/usr/lib/node_modules/npm/node_modules/which/which.js:14:12)
      npm WARN addRemoteGit     at F (/usr/lib/node_modules/npm/node_modules/which/which.js:69:19)
      npm WARN addRemoteGit     at E (/usr/lib/node_modules/npm/node_modules/which/which.js:81:29)
      npm WARN addRemoteGit     at /usr/lib/node_modules/npm/node_modules/which/which.js:90:16
      npm WARN addRemoteGit     at /usr/lib/node_modules/npm/node_modules/which/node_modules/isexe/index.js:44:5
      npm WARN addRemoteGit     at /usr/lib/node_modules/npm/node_modules/which/node_modules/isexe/access.js:8:5
      npm WARN addRemoteGit     at FSReqWrap.oncomplete (fs.js:123:15)
      npm WARN addRemoteGit  git://github.com/noopkat/js-stk500v1.git#avrgirl resetting remote /root/.npm/_git-remotes/git-github-com-noopkat-js-stk500v1-git-avrgirl-31bc3a47 because of error: { Error: not found: git
      npm WARN addRemoteGit     at getNotFoundError (/usr/lib/node_modules/npm/node_modules/which/which.js:14:12)
      npm WARN addRemoteGit     at F (/usr/lib/node_modules/npm/node_modules/which/which.js:69:19)
      npm WARN addRemoteGit     at E (/usr/lib/node_modules/npm/node_modules/which/which.js:81:29)
      npm WARN addRemoteGit     at /usr/lib/node_modules/npm/node_modules/which/which.js:90:16
      npm WARN addRemoteGit     at /usr/lib/node_modules/npm/node_modules/which/node_modules/isexe/index.js:44:5
      npm WARN addRemoteGit     at /usr/lib/node_modules/npm/node_modules/which/node_modules/isexe/access.js:8:5
      npm WARN addRemoteGit     at FSReqWrap.oncomplete (fs.js:123:15) code: 'ENOGIT' }
      npm WARN addRemoteGit Error: not found: git
      npm WARN addRemoteGit     at getNotFoundError (/usr/lib/node_modules/npm/node_modules/which/which.js:14:12)
      npm WARN addRemoteGit     at F (/usr/lib/node_modules/npm/node_modules/which/which.js:69:19)
      npm WARN addRemoteGit     at E (/usr/lib/node_modules/npm/node_modules/which/which.js:81:29)
      npm WARN addRemoteGit     at /usr/lib/node_modules/npm/node_modules/which/which.js:90:16
      npm WARN addRemoteGit     at /usr/lib/node_modules/npm/node_modules/which/node_modules/isexe/index.js:44:5
      npm WARN addRemoteGit     at /usr/lib/node_modules/npm/node_modules/which/node_modules/isexe/access.js:8:5
      npm WARN addRemoteGit     at FSReqWrap.oncomplete (fs.js:123:15)
      npm WARN addRemoteGit  git://github.com/noopkat/browser-serialport.git#api-updates resetting remote /root/.npm/_git-remotes/git-github-com-noopkat-browser-serialport-git-api-updates-0f82caf3 because of error: { Error: not found: git
      npm WARN addRemoteGit     at getNotFoundError (/usr/lib/node_modules/npm/node_modules/which/which.js:14:12)
      npm WARN addRemoteGit     at F (/usr/lib/node_modules/npm/node_modules/which/which.js:69:19)
      npm WARN addRemoteGit     at E (/usr/lib/node_modules/npm/node_modules/which/which.js:81:29)
      npm WARN addRemoteGit     at /usr/lib/node_modules/npm/node_modules/which/which.js:90:16
      npm WARN addRemoteGit     at /usr/lib/node_modules/npm/node_modules/which/node_modules/isexe/index.js:44:5
      npm WARN addRemoteGit     at /usr/lib/node_modules/npm/node_modules/which/node_modules/isexe/access.js:8:5
      npm WARN addRemoteGit     at FSReqWrap.oncomplete (fs.js:123:15) code: 'ENOGIT' }
      npm ERR! git clone --template=/root/.npm/_git-remotes/_templates --mirror git://github.com/noopkat/js-stk500v1.git /root/.npm/_git-remotes/git-github-com-noopkat-js-stk500v1-git-avrgirl-31bc3a47: undefined
      npm ERR! git clone --template=/root/.npm/_git-remotes/_templates --mirror git://github.com/noopkat/js-stk500v1.git /root/.npm/_git-remotes/git-github-com-noopkat-js-stk500v1-git-avrgirl-31bc3a47: undefined
      npm ERR! git clone --template=/root/.npm/_git-remotes/_templates --mirror git://github.com/noopkat/browser-serialport.git /root/.npm/_git-remotes/git-github-com-noopkat-browser-serialport-git-api-updates-0f82caf3: undefined
      npm ERR! git clone --template=/root/.npm/_git-remotes/_templates --mirror git://github.com/noopkat/browser-serialport.git /root/.npm/_git-remotes/git-github-com-noopkat-browser-serialport-git-api-updates-0f82caf3: undefined
      
      > mdns@2.4.0 install /opt/iobroker/node_modules/mdns
      > node-gyp rebuild
      
      gyp ERR! build error
      gyp ERR! stack Error: not found: make
      gyp ERR! stack     at getNotFoundError (/usr/lib/node_modules/npm/node_modules/which/which.js:14:12)
      gyp ERR! stack     at F (/usr/lib/node_modules/npm/node_modules/which/which.js:69:19)
      gyp ERR! stack     at E (/usr/lib/node_modules/npm/node_modules/which/which.js:81:29)
      gyp ERR! stack     at /usr/lib/node_modules/npm/node_modules/which/which.js:90:16
      gyp ERR! stack     at /usr/lib/node_modules/npm/node_modules/which/node_modules/isexe/index.js:44:5
      gyp ERR! stack     at /usr/lib/node_modules/npm/node_modules/which/node_modules/isexe/access.js:8:5
      gyp ERR! stack     at FSReqWrap.oncomplete (fs.js:123:15)
      gyp ERR! System Linux 4.9.0-6-amd64
      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/mdns
      gyp ERR! node -v v6.14.2
      gyp ERR! node-gyp -v v3.4.0
      gyp ERR! not ok
      
      > unix-dgram@0.2.3 install /opt/iobroker/node_modules/unix-dgram
      > node-gyp rebuild
      
      gyp ERR! build error
      gyp ERR! stack Error: not found: make
      gyp ERR! stack     at getNotFoundError (/usr/lib/node_modules/npm/node_modules/which/which.js:14:12)
      gyp ERR! stack     at F (/usr/lib/node_modules/npm/node_modules/which/which.js:69:19)
      gyp ERR! stack     at E (/usr/lib/node_modules/npm/node_modules/which/which.js:81:29)
      gyp ERR! stack     at /usr/lib/node_modules/npm/node_modules/which/which.js:90:16
      gyp ERR! stack     at /usr/lib/node_modules/npm/node_modules/which/node_modules/isexe/index.js:44:5
      gyp ERR! stack     at /usr/lib/node_modules/npm/node_modules/which/node_modules/isexe/access.js:8:5
      gyp ERR! stack     at FSReqWrap.oncomplete (fs.js:123:15)
      gyp ERR! System Linux 4.9.0-6-amd64
      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/unix-dgram
      gyp ERR! node -v v6.14.2
      gyp ERR! node-gyp -v v3.4.0
      gyp ERR! not ok
      
      > ursa@0.9.4 install /opt/iobroker/node_modules/ursa
      > node-gyp rebuild
      
      gyp ERR! build error
      gyp ERR! stack Error: not found: make
      gyp ERR! stack     at getNotFoundError (/usr/lib/node_modules/npm/node_modules/which/which.js:14:12)
      gyp ERR! stack     at F (/usr/lib/node_modules/npm/node_modules/which/which.js:69:19)
      gyp ERR! stack     at E (/usr/lib/node_modules/npm/node_modules/which/which.js:81:29)
      gyp ERR! stack     at /usr/lib/node_modules/npm/node_modules/which/which.js:90:16
      gyp ERR! stack     at /usr/lib/node_modules/npm/node_modules/which/node_modules/isexe/index.js:44:5
      gyp ERR! stack     at /usr/lib/node_modules/npm/node_modules/which/node_modules/isexe/access.js:8:5
      gyp ERR! stack     at FSReqWrap.oncomplete (fs.js:123:15)
      gyp ERR! System Linux 4.9.0-6-amd64
      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/ursa
      gyp ERR! node -v v6.14.2
      gyp ERR! node-gyp -v v3.4.0
      gyp ERR! not ok
      
      > usb@1.3.1 install /opt/iobroker/node_modules/usb
      > node-pre-gyp install --fallback-to-build
      
      node-pre-gyp ERR! Tried to download(404): https://github.com/tessel/node-usb/releases/download/1.3.1/usb_bindings-v1.3.1-node-v48-linux-x64.tar.gz
      node-pre-gyp ERR! Pre-built binaries not found for usb@1.3.1 and node@6.14.2 (node-v48 ABI) (falling back to source compile with node-gyp)
      gyp ERR! build error
      gyp ERR! stack Error: not found: make
      gyp ERR! stack     at getNotFoundError (/usr/lib/node_modules/npm/node_modules/which/which.js:14:12)
      gyp ERR! stack     at F (/usr/lib/node_modules/npm/node_modules/which/which.js:69:19)
      gyp ERR! stack     at E (/usr/lib/node_modules/npm/node_modules/which/which.js:81:29)
      gyp ERR! stack     at /usr/lib/node_modules/npm/node_modules/which/which.js:90:16
      gyp ERR! stack     at /usr/lib/node_modules/npm/node_modules/which/node_modules/isexe/index.js:44:5
      gyp ERR! stack     at /usr/lib/node_modules/npm/node_modules/which/node_modules/isexe/access.js:8:5
      gyp ERR! stack     at FSReqWrap.oncomplete (fs.js:123:15)
      gyp ERR! System Linux 4.9.0-6-amd64
      gyp ERR! command "/usr/bin/node" "/usr/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "build" "--fallback-to-build" "--module=/opt/iobroker/node_modules/usb/src/binding/usb_bindings.node" "--module_name=usb_bindings" "--module_path=/opt/iobroker/node_modules/usb/src/binding"
      gyp ERR! cwd /opt/iobroker/node_modules/usb
      gyp ERR! node -v v6.14.2
      gyp ERR! node-gyp -v v3.4.0
      gyp ERR! not ok
      node-pre-gyp ERR! build error
      node-pre-gyp ERR! stack Error: Failed to execute '/usr/bin/node /usr/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js build --fallback-to-build --module=/opt/iobroker/node_modules/usb/src/binding/usb_bindings.node --module_name=usb_bindings --module_path=/opt/iobroker/node_modules/usb/src/binding' (1)
      node-pre-gyp ERR! stack     at ChildProcess. <anonymous>(/opt/iobroker/node_modules/node-pre-gyp/lib/util/compile.js:83:29)
      node-pre-gyp ERR! stack     at emitTwo (events.js:106:13)
      node-pre-gyp ERR! stack     at ChildProcess.emit (events.js:191:7)
      node-pre-gyp ERR! stack     at maybeClose (internal/child_process.js:920:16)
      node-pre-gyp ERR! stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:230:5)
      node-pre-gyp ERR! System Linux 4.9.0-6-amd64
      node-pre-gyp ERR! command "/usr/bin/node" "/opt/iobroker/node_modules/.bin/node-pre-gyp" "install" "--fallback-to-build"
      node-pre-gyp ERR! cwd /opt/iobroker/node_modules/usb
      node-pre-gyp ERR! node -v v6.14.2
      node-pre-gyp ERR! node-pre-gyp -v v0.6.36
      node-pre-gyp ERR! not ok
      Failed to execute '/usr/bin/node /usr/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js build --fallback-to-build --module=/opt/iobroker/node_modules/usb/src/binding/usb_bindings.node --module_name=usb_bindings --module_path=/opt/iobroker/node_modules/usb/src/binding' (1)
      
      > bluetooth-hci-socket@0.5.1 install /opt/iobroker/node_modules/bluetooth-hci-socket
      > node-gyp rebuild
      
      gyp ERR! build error
      gyp ERR! stack Error: not found: make
      gyp ERR! stack     at getNotFoundError (/usr/lib/node_modules/npm/node_modules/which/which.js:14:12)
      gyp ERR! stack     at F (/usr/lib/node_modules/npm/node_modules/which/which.js:69:19)
      gyp ERR! stack     at E (/usr/lib/node_modules/npm/node_modules/which/which.js:81:29)
      gyp ERR! stack     at /usr/lib/node_modules/npm/node_modules/which/which.js:90:16
      gyp ERR! stack     at /usr/lib/node_modules/npm/node_modules/which/node_modules/isexe/index.js:44:5
      gyp ERR! stack     at /usr/lib/node_modules/npm/node_modules/which/node_modules/isexe/access.js:8:5
      gyp ERR! stack     at FSReqWrap.oncomplete (fs.js:123:15)
      gyp ERR! System Linux 4.9.0-6-amd64
      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/bluetooth-hci-socket
      gyp ERR! node -v v6.14.2
      gyp ERR! node-gyp -v v3.4.0
      gyp ERR! not ok
      iobroker.inst@1.0.8 /opt/iobroker
      ├── awty@0.1.0  extraneous
      ├── chip.avr.avr109@1.1.1  extraneous
      ├── iobroker.ble@0.5.2
      └── stk500-v2@1.0.2  extraneous
      
      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":"x64"})
      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":"x64"})
      npm WARN optional SKIPPING OPTIONAL DEPENDENCY: stk500@git://github.com/noopkat/js-stk500v1.git#avrgirl (node_modules/avrgirl-arduino/node_modules/stk500):
      npm WARN optional SKIPPING OPTIONAL DEPENDENCY: not found: git
      npm WARN optional SKIPPING OPTIONAL DEPENDENCY: browser-serialport@git://github.com/noopkat/browser-serialport.git#api-updates (node_modules/avrgirl-arduino/node_modules/browser-serialport):
      npm WARN optional SKIPPING OPTIONAL DEPENDENCY: not found: git
      npm WARN optional SKIPPING OPTIONAL DEPENDENCY: mdns@2.4.0 (node_modules/mdns):
      npm WARN optional SKIPPING OPTIONAL DEPENDENCY: mdns@2.4.0 install: `node-gyp rebuild`
      npm WARN optional SKIPPING OPTIONAL DEPENDENCY: Exit status 1
      npm WARN optional SKIPPING OPTIONAL DEPENDENCY: unix-dgram@0.2.3 (node_modules/unix-dgram):
      npm WARN optional SKIPPING OPTIONAL DEPENDENCY: unix-dgram@0.2.3 install: `node-gyp rebuild`
      npm WARN optional SKIPPING OPTIONAL DEPENDENCY: Exit status 1
      npm WARN optional SKIPPING OPTIONAL DEPENDENCY: ursa@0.9.4 (node_modules/ursa):
      npm WARN optional SKIPPING OPTIONAL DEPENDENCY: ursa@0.9.4 install: `node-gyp rebuild`
      npm WARN optional SKIPPING OPTIONAL DEPENDENCY: Exit status 1
      npm WARN optional SKIPPING OPTIONAL DEPENDENCY: usb@1.3.1 (node_modules/usb):
      npm WARN optional SKIPPING OPTIONAL DEPENDENCY: usb@1.3.1 install: `node-pre-gyp install --fallback-to-build`
      npm WARN optional SKIPPING OPTIONAL DEPENDENCY: Exit status 1
      npm WARN optional SKIPPING OPTIONAL DEPENDENCY: bluetooth-hci-socket@0.5.1 (node_modules/bluetooth-hci-socket):
      npm WARN optional SKIPPING OPTIONAL DEPENDENCY: bluetooth-hci-socket@0.5.1 install: `node-gyp rebuild`
      npm WARN optional SKIPPING OPTIONAL DEPENDENCY: Exit status 1
      root@Brix:/opt/iobroker#</anonymous> 
      

      mit solchen Sachen bin ich total überfordert. Möchte mit meinem Halbwissen natürlich auch nicht meine Installation zerschießen.

      Danke und Grüße Ingo

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

        Hi Ingo,

        dir fehlt scheinbar das Paket "Git" –>````
        npm WARN addRemoteGit Error: not found: git

        bzw. er kann es nicht finden.
        
        Muss mal dumm fragen: Ist das eine Windows oder Linux installation?
        
        Wenn Linux kannst du mal versuchen das zu installieren:
        
        

        sudo apt-get install git

        1 Reply Last reply Reply Quote 0
        • AlCalzone
          AlCalzone Developer last edited by

          make fehlt auch, ich würde sagen, du solltest die build-essentials installieren:

          sudo apt-get install -y build-essential
          
          1 Reply Last reply Reply Quote 0
          • I
            Ingo last edited by

            Hallo, es ist zum verzweifeln.

            Beide Tipps haben nix gebracht.

            Der Host ist ein Gigabyte Brix 3150 mit Debian 9.3.0 amd64-netinst.

            node.js 6.14.2

            npm 3.10.10

            Eigentlich geht es mir nur um 2 Xiaomi-Sensoren Temp / Hum (die runden mit Display), diese kommen über den Mihome-Adapter nicht mit rüber.

            Ich hatte diese schon mal eingebunden über ein Script hier aus dem Forum, bis ich vor ein paar Tagen feststellen mußte, letzte Aktualisierung

            war vor 2 Wochen.

            Also den ble-Adapter auf dem Test-Raspi nochmal gestartet - wunderbar. Und dann ging das Drama mit dem Brix los…....

            Danke und Grüße

            Ingo

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

              @Ingo:

              Beide Tipps haben nix gebracht. `

              Bedeutet genau was ?

              GIT und/oder Make konnte nicht installiert werden?

              BLE konnte nicht installiert werden?

              Gab es fehler bei der Installation von GIT/Make bzw. Build-Essentials ?

              Logs?

              Hast du bisher immer alles als "root" installiert oder auch mal einen anderen User verwendet?

              1 Reply Last reply Reply Quote 0
              • I
                Ingo last edited by

                Hallo,

                GIT / Make / Build-Essentials - Installationen liefen fehlerfrei durch.

                Immer als root, im Hauptverzeichnis, oder muß ich vorher in das /opt/ioBroker - Verzeichnis wechseln ????

                Auch der BLE-Adapter wurde fehlerfrei installiert, nur bleibt er gelb, zusammen mit der Fehlermeldung

                Cannot find module 'bluetooth-hci-socket'

                Danke und Grüße Ingo

                1 Reply Last reply Reply Quote 0
                • AlCalzone
                  AlCalzone Developer last edited by

                  @Ingo:

                  Cannot find module 'bluetooth-hci-socket' `
                  Dann musst du das Modul mal suchen und manuell neu installieren.

                  Laut deinem Log müsste es in /opt/iobroker/node_modules/bluetooth-hci-socket liegen. Darin

                  npm install --production
                  

                  ausführen.

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

                    Linux ist aktuell?

                    apt update && apt upgrade
                    

                    Dann hat er das Modul, aus welchem Grund auch immer, bei dir nicht mit installiert.

                    npm install bluetooth-hci-socket
                    

                    Würde ich jetzt mal machen.

                    Edit: war zu langsam 😉

                    1 Reply Last reply Reply Quote 0
                    • I
                      Ingo last edited by

                      Alles grün !!!!

                      Danke für eure Hilfe.

                      5 gelbe Daumen an euch.

                      Grüße Ingo

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

                        Schön…

                        Was genau hat jetzt zum Erfolg geführt?

                        Gesendet von iPhone mit Tapatalk Pro

                        1 Reply Last reply Reply Quote 0
                        • I
                          Ingo last edited by

                          Hallo,

                          ich muß zwischendurch immer mal was am neuen Gewächshaus meiner besseren Hälfte bauen, sonst gibt's heute Abend Mecker……

                          habe

                          apt update && apt upgrade

                          ausgeführt, ist aber kaum was nachinstalliert worden, ging ganz fix.

                          npm install bluetooth-hci-socket

                          danach ging es.

                          Adapter sofort grün, kurz danach waren die Werte von den beiden Xiaomi-Sensoren da.

                          An Werten battery, humidity, rssi und temperature - perfekt.

                          nun schnell was essen, dann wieder ans Gewächshaus.

                          Danke nochmals für eure geduldige Hilfe

                          Grüße Ingo

                          1 Reply Last reply Reply Quote 0
                          • S
                            swordfisch last edited by

                            Hi habe auch das Problem das ich den BLE Adapter nicht auf grün bekomme

                            sudo npm i iobroker.ble –production --unsafe-perm

                            habe ich eben ausgeführt

                             sudo npm i iobroker.ble --production --unsafe-perm
                            
                            > 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:950: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: error: no matching function for call to âv8::Function::NewInstance(int, v8::Local <v8::value>[1])â
                               Local <value>error = errorConstructor->NewInstance(1, constructorArgs);
                                                                                                    ^
                            In file included from /root/.node-gyp/10.4.0/include/node/node.h:63:0,
                                             from /root/.node-gyp/10.4.0/include/node/node_buffer.h:25,
                                             from ../src/BluetoothHciSocket.cpp:7:
                            /root/.node-gyp/10.4.0/include/node/v8.h:3905:44: note: candidate: v8::MaybeLocal <v8::object>v8::Function::NewInstance(v8::Local<v8::context>, int, v8::Local<v8::value>*) const
                               V8_WARN_UNUSED_RESULT MaybeLocal <object>NewInstance(
                                                                        ^~~~~~~~~~~
                            /root/.node-gyp/10.4.0/include/node/v8.h:3905:44: note:   candidate expects 3 arguments, 2 provided
                            /root/.node-gyp/10.4.0/include/node/v8.h:3908:44: note: candidate: v8::MaybeLocal <v8::object>v8::Function::NewInstance(v8::Local<v8::context>) const
                               V8_WARN_UNUSED_RESULT MaybeLocal <object>NewInstance(
                                                                        ^~~~~~~~~~~
                            /root/.node-gyp/10.4.0/include/node/v8.h:3908:44: note:   candidate expects 1 argument, 2 provided
                            ../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:950:46: note: declared here
                               NAN_DEPRECATED inline v8::Local <v8::value>MakeCallback(
                                                                          ^~~~~~~~~~~~
                            binding.target.mk:93: die Regel für Ziel âRelease/obj.target/binding/src/BluetoothHciSocket.oâ scheiterte
                            make: *** [Release/obj.target/binding/src/BluetoothHciSocket.o] Fehler 1
                            make: Verzeichnis â/opt/iobroker/node_modules/bluetooth-hci-socket/buildâ wird verlassen
                            gyp ERR! build error
                            gyp ERR! stack Error: `make` failed with exit code: 2
                            gyp ERR! stack     at ChildProcess.onExit (/usr/local/lib/node_modules/npm/node_modules/node-gyp/lib/build.js:258:23)
                            gyp ERR! stack     at ChildProcess.emit (events.js:182:13)
                            gyp ERR! stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:237:12)
                            gyp ERR! System Linux 4.14.50-v7+
                            gyp ERR! command "/usr/local/bin/node" "/usr/local/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "rebuild"
                            gyp ERR! cwd /opt/iobroker/node_modules/bluetooth-hci-socket
                            gyp ERR! node -v v10.4.0
                            gyp ERR! node-gyp -v v3.6.2
                            gyp ERR! not ok
                            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":"arm"})
                            npm WARN optional SKIPPING OPTIONAL DEPENDENCY: bluetooth-hci-socket@0.5.1 (node_modules/bluetooth-hci-socket):
                            npm WARN optional SKIPPING OPTIONAL DEPENDENCY: bluetooth-hci-socket@0.5.1 install: `node-gyp rebuild`
                            npm WARN optional SKIPPING OPTIONAL DEPENDENCY: Exit status 1
                            
                            + iobroker.ble@0.5.2
                            updated 1 package and audited 2751 packages in 29.352s
                            found 84 vulnerabilities (46 low, 27 moderate, 11 high)
                              run `npm audit fix` to fix them, or `npm audit` for details</v8::value></object></v8::value></v8::string></v8::object></v8::value></object></v8::context></v8::object></object></v8::value></v8::context></v8::object></value></v8::value></v8::value></object></v8::value></v8::string></v8::object></v8::value> 
                            
                            1 Reply Last reply Reply Quote 0
                            • AlCalzone
                              AlCalzone Developer last edited by

                              Das scheint eine Inkompatibilität zwischen dem bluetooth-hci-socket und Node 10 zu sein. Am besten mal in deren Repo ein Issue aufmachen.

                              Edit: Scheint bekannt zu sein: https://github.com/noble/node-bluetooth … /issues/84

                              1 Reply Last reply Reply Quote 0
                              • C
                                chka last edited by

                                so richtig schlau werde ich aus der Lösung die dort geschrieben ist aber leider nicht

                                1 Reply Last reply Reply Quote 0
                                • AlCalzone
                                  AlCalzone Developer last edited by

                                  @chka:

                                  so richtig schlau werde ich aus der Lösung die dort geschrieben ist aber leider nicht `

                                  Die Quintessenz ist: Warten, bis die Macher von bluetooth-hci-socket das Problem behoben und eine neue Version veröffentlicht haben, oder zurück auf NodeJS 8.

                                  1 Reply Last reply Reply Quote 0
                                  • C
                                    chka last edited by

                                    ok danke

                                    node 8 lief bei mir nicht dann muss ich warten.

                                    1 Reply Last reply Reply Quote 0
                                    • C
                                      chka last edited by

                                      habe es mit dem downgread auf die 8.11.3 genhaft, ble läuft

                                      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

                                      887
                                      Online

                                      31.9k
                                      Users

                                      80.1k
                                      Topics

                                      1.3m
                                      Posts

                                      5
                                      24
                                      4496
                                      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