NEWS
Gelöst - BLE-Adapter startet nicht
-
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
-
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> -
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.
519
Online32.5k
Benutzer81.7k
Themen1.3m
Beiträge