Jeelink Adapter startet nicht mehr
-
Wenn es dich tröstet, bei mir kann man den auch nicht (mehr?) auf Anhieb installieren:
echad@chet:/opt/iobroker $ iobroker add jeelink NPM version: 8.1.2 npm install iobroker.jeelink@0.1.3 --loglevel error --prefix "/opt/iobroker" (System call) npm ERR! code 1 npm ERR! path /opt/iobroker/node_modules/@serialport/bindings npm ERR! command failed npm ERR! command sh -c prebuild-install --tag-prefix @serialport/bindings@ || node-gyp rebuild npm ERR! make: Entering directory '/opt/iobroker/node_modules/@serialport/bindings/build' npm ERR! CXX(target) Release/obj.target/bindings/src/serialport.o npm ERR! make: Leaving directory '/opt/iobroker/node_modules/@serialport/bindings/build' npm ERR! ../src/serialport.cpp: In function ‘Nan::NAN_METHOD_RETURN_TYPE Open(Nan::NAN_METHOD_ARGS_TYPE)’: npm ERR! ../src/serialport.cpp:78:51: warning: cast between incompatible function types from ‘void (*)(uv_work_t*)’ {aka ‘void (*)(uv_work_s*)’} to ‘uv_after_work_cb’ {aka ‘void (*)(uv_work_s*, int)’} [-Wcast-function-type] npm ERR! 78 | uv_queue_work(uv_default_loop(), req, EIO_Open, (uv_after_work_cb)EIO_AfterOpen); npm ERR! | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ npm ERR! ../src/serialport.cpp: In function ‘Nan::NAN_METHOD_RETURN_TYPE Update(Nan::NAN_METHOD_ARGS_TYPE)’: npm ERR! ../src/serialport.cpp:135:53: warning: cast between incompatible function types from ‘void (*)(uv_work_t*)’ {aka ‘void (*)(uv_work_s*)’} to ‘uv_after_work_cb’ {aka ‘void (*)(uv_work_s*, int)’} [-Wcast-function-type] npm ERR! 135 | uv_queue_work(uv_default_loop(), req, EIO_Update, (uv_after_work_cb)EIO_AfterUpdate); npm ERR! | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ npm ERR! ../src/serialport.cpp: In function ‘Nan::NAN_METHOD_RETURN_TYPE Close(Nan::NAN_METHOD_ARGS_TYPE)’: npm ERR! ../src/serialport.cpp:175:52: warning: cast between incompatible function types from ‘void (*)(uv_work_t*)’ {aka ‘void (*)(uv_work_s*)’} to ‘uv_after_work_cb’ {aka ‘void (*)(uv_work_s*, int)’} [-Wcast-function-type] npm ERR! 175 | uv_queue_work(uv_default_loop(), req, EIO_Close, (uv_after_work_cb)EIO_AfterClose); npm ERR! | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ npm ERR! ../src/serialport.cpp: In function ‘Nan::NAN_METHOD_RETURN_TYPE Flush(Nan::NAN_METHOD_ARGS_TYPE)’: npm ERR! ../src/serialport.cpp:215:52: warning: cast between incompatible function types from ‘void (*)(uv_work_t*)’ {aka ‘void (*)(uv_work_s*)’} to ‘uv_after_work_cb’ {aka ‘void (*)(uv_work_s*, int)’} [-Wcast-function-type] npm ERR! 215 | uv_queue_work(uv_default_loop(), req, EIO_Flush, (uv_after_work_cb)EIO_AfterFlush); npm ERR! | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ npm ERR! ../src/serialport.cpp: In function ‘Nan::NAN_METHOD_RETURN_TYPE Set(Nan::NAN_METHOD_ARGS_TYPE)’: npm ERR! ../src/serialport.cpp:270:50: warning: cast between incompatible function types from ‘void (*)(uv_work_t*)’ {aka ‘void (*)(uv_work_s*)’} to ‘uv_after_work_cb’ {aka ‘void (*)(uv_work_s*, int)’} [-Wcast-function-type] npm ERR! 270 | uv_queue_work(uv_default_loop(), req, EIO_Set, (uv_after_work_cb)EIO_AfterSet); npm ERR! | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ npm ERR! ../src/serialport.cpp: In function ‘Nan::NAN_METHOD_RETURN_TYPE Get(Nan::NAN_METHOD_ARGS_TYPE)’: npm ERR! ../src/serialport.cpp:314:50: warning: cast between incompatible function types from ‘void (*)(uv_work_t*)’ {aka ‘void (*)(uv_work_s*)’} to ‘uv_after_work_cb’ {aka ‘void (*)(uv_work_s*, int)’} [-Wcast-function-type] npm ERR! 314 | uv_queue_work(uv_default_loop(), req, EIO_Get, (uv_after_work_cb)EIO_AfterGet); npm ERR! | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ npm ERR! ../src/serialport.cpp: In function ‘void EIO_AfterGet(uv_work_t*)’: npm ERR! ../src/serialport.cpp:329:96: error: no matching function for call to ‘v8::Object::Set(v8::Local<v8::String>, Nan::imp::FactoryBase<v8::Boolean>::return_t)’ npm ERR! 329 | results->Set(Nan::New<v8::String>("cts").ToLocalChecked(), Nan::New<v8::Boolean>(data->cts)); npm ERR! | ^ npm ERR! In file included from /home/iobroker/.cache/node-gyp/17.1.0/include/node/v8-array-buffer.h:13, npm ERR! from /home/iobroker/.cache/node-gyp/17.1.0/include/node/v8.h:25, npm ERR! from /home/iobroker/.cache/node-gyp/17.1.0/include/node/node.h:63, npm ERR! from ../../../nan/nan.h:58, npm ERR! from ../src/./serialport.h:6, npm ERR! from ../src/serialport.cpp:1: npm ERR! /home/iobroker/.cache/node-gyp/17.1.0/include/node/v8-object.h:244:37: note: candidate: ‘v8::Maybe<bool> v8::Object::Set(v8::Local<v8::Context>, v8::Local<v8::Value>, v8::Local<v8::Value>)’ npm ERR! 244 | V8_WARN_UNUSED_RESULT Maybe<bool> Set(Local<Context> context, npm ERR! | ^~~ npm ERR! /home/iobroker/.cache/node-gyp/17.1.0/include/node/v8-object.h:244:37: note: candidate expects 3 arguments, 2 provided npm ERR! /home/iobroker/.cache/node-gyp/17.1.0/include/node/v8-object.h:247:37: note: candidate: ‘v8::Maybe<bool> v8::Object::Set(v8::Local<v8::Context>, uint32_t, v8::Local<v8::Value>)’ npm ERR! 247 | V8_WARN_UNUSED_RESULT Maybe<bool> Set(Local<Context> context, uint32_t index, npm ERR! | ^~~ npm ERR! /home/iobroker/.cache/node-gyp/17.1.0/include/node/v8-object.h:247:37: note: candidate expects 3 arguments, 2 provided npm ERR! ../src/serialport.cpp:330:96: error: no matching function for call to ‘v8::Object::Set(v8::Local<v8::String>, Nan::imp::FactoryBase<v8::Boolean>::return_t)’ npm ERR! 330 | results->Set(Nan::New<v8::String>("dsr").ToLocalChecked(), Nan::New<v8::Boolean>(data->dsr)); npm ERR! | ^ npm ERR! In file included from /home/iobroker/.cache/node-gyp/17.1.0/include/node/v8-array-buffer.h:13, npm ERR! from /home/iobroker/.cache/node-gyp/17.1.0/include/node/v8.h:25, npm ERR! from /home/iobroker/.cache/node-gyp/17.1.0/include/node/node.h:63, npm ERR! from ../../../nan/nan.h:58, npm ERR! from ../src/./serialport.h:6, npm ERR! from ../src/serialport.cpp:1: npm ERR! /home/iobroker/.cache/node-gyp/17.1.0/include/node/v8-object.h:244:37: note: candidate: ‘v8::Maybe<bool> v8::Object::Set(v8::Local<v8::Context>, v8::Local<v8::Value>, v8::Local<v8::Value>)’ npm ERR! 244 | V8_WARN_UNUSED_RESULT Maybe<bool> Set(Local<Context> context, npm ERR! | ^~~ npm ERR! /home/iobroker/.cache/node-gyp/17.1.0/include/node/v8-object.h:244:37: note: candidate expects 3 arguments, 2 provided npm ERR! /home/iobroker/.cache/node-gyp/17.1.0/include/node/v8-object.h:247:37: note: candidate: ‘v8::Maybe<bool> v8::Object::Set(v8::Local<v8::Context>, uint32_t, v8::Local<v8::Value>)’ npm ERR! 247 | V8_WARN_UNUSED_RESULT Maybe<bool> Set(Local<Context> context, uint32_t index, npm ERR! | ^~~ npm ERR! /home/iobroker/.cache/node-gyp/17.1.0/include/node/v8-object.h:247:37: note: candidate expects 3 arguments, 2 provided npm ERR! ../src/serialport.cpp:331:96: error: no matching function for call to ‘v8::Object::Set(v8::Local<v8::String>, Nan::imp::FactoryBase<v8::Boolean>::return_t)’ npm ERR! 331 | results->Set(Nan::New<v8::String>("dcd").ToLocalChecked(), Nan::New<v8::Boolean>(data->dcd)); npm ERR! | ^ npm ERR! In file included from /home/iobroker/.cache/node-gyp/17.1.0/include/node/v8-array-buffer.h:13, npm ERR! from /home/iobroker/.cache/node-gyp/17.1.0/include/node/v8.h:25, npm ERR! from /home/iobroker/.cache/node-gyp/17.1.0/include/node/node.h:63, npm ERR! from ../../../nan/nan.h:58, npm ERR! from ../src/./serialport.h:6, npm ERR! from ../src/serialport.cpp:1: npm ERR! /home/iobroker/.cache/node-gyp/17.1.0/include/node/v8-object.h:244:37: note: candidate: ‘v8::Maybe<bool> v8::Object::Set(v8::Local<v8::Context>, v8::Local<v8::Value>, v8::Local<v8::Value>)’ npm ERR! 244 | V8_WARN_UNUSED_RESULT Maybe<bool> Set(Local<Context> context, npm ERR! | ^~~ npm ERR! /home/iobroker/.cache/node-gyp/17.1.0/include/node/v8-object.h:244:37: note: candidate expects 3 arguments, 2 provided npm ERR! /home/iobroker/.cache/node-gyp/17.1.0/include/node/v8-object.h:247:37: note: candidate: ‘v8::Maybe<bool> v8::Object::Set(v8::Local<v8::Context>, uint32_t, v8::Local<v8::Value>)’ npm ERR! 247 | V8_WARN_UNUSED_RESULT Maybe<bool> Set(Local<Context> context, uint32_t index, npm ERR! | ^~~ npm ERR! /home/iobroker/.cache/node-gyp/17.1.0/include/node/v8-object.h:247:37: note: candidate expects 3 arguments, 2 provided npm ERR! ../src/serialport.cpp: In function ‘Nan::NAN_METHOD_RETURN_TYPE GetBaudRate(Nan::NAN_METHOD_ARGS_TYPE)’: npm ERR! ../src/serialport.cpp:363:58: warning: cast between incompatible function types from ‘void (*)(uv_work_t*)’ {aka ‘void (*)(uv_work_s*)’} to ‘uv_after_work_cb’ {aka ‘void (*)(uv_work_s*, int)’} [-Wcast-function-type] npm ERR! 363 | uv_queue_work(uv_default_loop(), req, EIO_GetBaudRate, (uv_after_work_cb)EIO_AfterGetBaudRate); npm ERR! | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ npm ERR! ../src/serialport.cpp: In function ‘void EIO_AfterGetBaudRate(uv_work_t*)’: npm ERR! ../src/serialport.cpp:378:106: error: no matching function for call to ‘v8::Object::Set(v8::Local<v8::String>, Nan::imp::IntegerFactory<v8::Integer>::return_t)’ npm ERR! 378 | results->Set(Nan::New<v8::String>("baudRate").ToLocalChecked(), Nan::New<v8::Integer>(data->baudRate)); npm ERR! | ^ npm ERR! In file included from /home/iobroker/.cache/node-gyp/17.1.0/include/node/v8-array-buffer.h:13, npm ERR! from /home/iobroker/.cache/node-gyp/17.1.0/include/node/v8.h:25, npm ERR! from /home/iobroker/.cache/node-gyp/17.1.0/include/node/node.h:63, npm ERR! from ../../../nan/nan.h:58, npm ERR! from ../src/./serialport.h:6, npm ERR! from ../src/serialport.cpp:1: npm ERR! /home/iobroker/.cache/node-gyp/17.1.0/include/node/v8-object.h:244:37: note: candidate: ‘v8::Maybe<bool> v8::Object::Set(v8::Local<v8::Context>, v8::Local<v8::Value>, v8::Local<v8::Value>)’ npm ERR! 244 | V8_WARN_UNUSED_RESULT Maybe<bool> Set(Local<Context> context, npm ERR! | ^~~ npm ERR! /home/iobroker/.cache/node-gyp/17.1.0/include/node/v8-object.h:244:37: note: candidate expects 3 arguments, 2 provided npm ERR! /home/iobroker/.cache/node-gyp/17.1.0/include/node/v8-object.h:247:37: note: candidate: ‘v8::Maybe<bool> v8::Object::Set(v8::Local<v8::Context>, uint32_t, v8::Local<v8::Value>)’ npm ERR! 247 | V8_WARN_UNUSED_RESULT Maybe<bool> Set(Local<Context> context, uint32_t index, npm ERR! | ^~~ npm ERR! /home/iobroker/.cache/node-gyp/17.1.0/include/node/v8-object.h:247:37: note: candidate expects 3 arguments, 2 provided npm ERR! ../src/serialport.cpp: In function ‘Nan::NAN_METHOD_RETURN_TYPE Drain(Nan::NAN_METHOD_ARGS_TYPE)’: npm ERR! ../src/serialport.cpp:409:52: warning: cast between incompatible function types from ‘void (*)(uv_work_t*)’ {aka ‘void (*)(uv_work_s*)’} to ‘uv_after_work_cb’ {aka ‘void (*)(uv_work_s*, int)’} [-Wcast-function-type] npm ERR! 409 | uv_queue_work(uv_default_loop(), req, EIO_Drain, (uv_after_work_cb)EIO_AfterDrain); npm ERR! | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ npm ERR! ../src/serialport.cpp: At global scope: npm ERR! ../src/serialport.cpp:430:28: warning: unnecessary parentheses in declaration of ‘ToParityEnum’ [-Wparentheses] npm ERR! 430 | SerialPortParity NAN_INLINE(ToParityEnum(const v8::Local<v8::String>& v8str)) { npm ERR! | ^ npm ERR! ../src/serialport.cpp:449:30: warning: unnecessary parentheses in declaration of ‘ToStopBitEnum’ [-Wparentheses] npm ERR! 449 | SerialPortStopBits NAN_INLINE(ToStopBitEnum(double stopBits)) { npm ERR! | ^ npm ERR! In file included from ../../../nan/nan.h:58, npm ERR! from ../src/./serialport.h:6, npm ERR! from ../src/serialport.cpp:1: npm ERR! /home/iobroker/.cache/node-gyp/17.1.0/include/node/node.h:843:7: warning: cast between incompatible function types from ‘void (*)(Nan::ADDON_REGISTER_FUNCTION_ARGS_TYPE)’ {aka ‘void (*)(v8::Local<v8::Object>)’} to ‘node::addon_register_func’ {aka ‘void (*)(v8::Local<v8::Object>, v8::Local<v8::Value>, void*)’} [-Wcast-function-type] npm ERR! 843 | (node::addon_register_func) (regfunc), \ npm ERR! | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ npm ERR! /home/iobroker/.cache/node-gyp/17.1.0/include/node/node.h:877:3: note: in expansion of macro ‘NODE_MODULE_X’ npm ERR! 877 | NODE_MODULE_X(modname, regfunc, NULL, 0) // NOLINT (readability/null_usage) npm ERR! | ^~~~~~~~~~~~~ npm ERR! ../src/serialport.cpp:483:1: note: in expansion of macro ‘NODE_MODULE’ npm ERR! 483 | NODE_MODULE(serialport, init); npm ERR! | ^~~~~~~~~~~ npm ERR! make: *** [bindings.target.mk:114: Release/obj.target/bindings/src/serialport.o] Error 1 npm ERR! gyp ERR! build error npm ERR! gyp ERR! stack Error: `make` failed with exit code: 2 npm ERR! gyp ERR! stack at ChildProcess.onExit (/usr/lib/node_modules/npm/node_modules/node-gyp/lib/build.js:194:23) npm ERR! gyp ERR! stack at ChildProcess.emit (node:events:390:28) npm ERR! gyp ERR! stack at Process.ChildProcess._handle.onexit (node:internal/child_process:290:12) npm ERR! gyp ERR! System Linux 5.10.63-v8+ npm ERR! gyp ERR! command "/usr/bin/node" "/usr/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "rebuild" npm ERR! gyp ERR! cwd /opt/iobroker/node_modules/@serialport/bindings npm ERR! gyp ERR! node -v v17.1.0 npm ERR! gyp ERR! node-gyp -v v8.3.0 npm ERR! gyp ERR! not ok npm ERR! A complete log of this run can be found in: npm ERR! /home/iobroker/.npm/_logs/2021-11-20T12_28_05_361Z-debug.log host.chet Cannot install iobroker.jeelink@0.1.3: 1 -
@thomas-braun danke, da fühle ich mich dann nicht so ganz allein...
Ist schade, weil meine Heizungsregelung da dran hängt, der JeeLink und die TFA Sensoren sind halt super stabil und zuverlässig. Aber vielleicht wirft @foxthefox nochmal einen Blick auf den Adapter.
-
@tepman sagte in Jeelink Adapter startet nicht mehr:
Dann bleib vorerst auf node12.
Foxthefox scheint nicht mehr großartig aktiv zu sein. Bedeutet vermutlich für den Adapter jeelink nichts gutes. -
@thomas-braun nein, downgraden tue ich jetzt nicht mehr. Verschiebt das Problem ja auch nur. Werde die Sensoren vermutlich gegen Zigbees tauschen.
-
@tepman sagte in Jeelink Adapter startet nicht mehr:
@thomas-braun nein, downgraden tue ich jetzt nicht mehr. Verschiebt das Problem ja auch nur.
Will ich eigentlich auch nicht, nur stand da doch unter richtig Updaten und NodeJS der Hinweis, dass man im Zusammenhang mit Serialport:
Die einfachste Option ist es dann manuell im richtigen Verzeichnis neu zu bauen.
In dem Fall das Verzeichenis mit "bindings" suchen - oben ist das /opt/iobroker/node_modules/serialport/node_modules/bindings ... bei neueren Versionen kann es auch etwas wie /opt/iobroker/node_modules/serialport/node_modules/@serialport/bindings sein.
Dann in dieses Verzeichnis wechseln und npm install --production ausführen. Danach den Adapter nochmal sneu starten, das sollte dann tun.
Was wäre denn das richtige Verzeichnis bei folgenden Fehlermeldungen des JeeLink:
2021-11-21 12:03:51.760 error instance system.adapter.jeelink.0 terminated with code 1 (JS_CONTROLLER_STOPPED) 2021-11-21 12:03:51.760 error Caught by controller[0]: } 2021-11-21 12:03:51.760 error Caught by controller[0]: ] 2021-11-21 12:03:51.760 error Caught by controller[0]: '/opt/iobroker/node_modules/iobroker.jeelink/node_modules/@serialport/bindings/lib/binding/node-v83-linux-x64/bindings.node' 2021-11-21 12:03:51.760 error Caught by controller[0]: '/opt/iobroker/node_modules/iobroker.jeelink/node_modules/@serialport/bindings/addon-build/default/install-root/bindings.node', 2021-11-21 12:03:51.760 error Caught by controller[0]: '/opt/iobroker/node_modules/iobroker.jeelink/node_modules/@serialport/bindings/addon-build/debug/install-root/bindings.node', 2021-11-21 12:03:51.760 error Caught by controller[0]: '/opt/iobroker/node_modules/iobroker.jeelink/node_modules/@serialport/bindings/addon-build/release/install-root/bindings.node', 2021-11-21 12:03:51.760 error Caught by controller[0]: '/opt/iobroker/node_modules/iobroker.jeelink/node_modules/@serialport/bindings/compiled/14.18.1/linux/x64/bindings.node', 2021-11-21 12:03:51.759 error Caught by controller[0]: '/opt/iobroker/node_modules/iobroker.jeelink/node_modules/@serialport/bindings/build/default/bindings.node', 2021-11-21 12:03:51.759 error Caught by controller[0]: '/opt/iobroker/node_modules/iobroker.jeelink/node_modules/@serialport/bindings/Release/bindings.node', 2021-11-21 12:03:51.759 error Caught by controller[0]: '/opt/iobroker/node_modules/iobroker.jeelink/node_modules/@serialport/bindings/out/Release/bindings.node', 2021-11-21 12:03:51.759 error Caught by controller[0]: '/opt/iobroker/node_modules/iobroker.jeelink/node_modules/@serialport/bindings/Debug/bindings.node', 2021-11-21 12:03:51.759 error Caught by controller[0]: '/opt/iobroker/node_modules/iobroker.jeelink/node_modules/@serialport/bindings/out/Debug/bindings.node', 2021-11-21 12:03:51.759 error Caught by controller[0]: '/opt/iobroker/node_modules/iobroker.jeelink/node_modules/@serialport/bindings/build/Release/bindings.node', 2021-11-21 12:03:51.759 error Caught by controller[0]: '/opt/iobroker/node_modules/iobroker.jeelink/node_modules/@serialport/bindings/build/Debug/bindings.node', 2021-11-21 12:03:51.759 error Caught by controller[0]: '/opt/iobroker/node_modules/iobroker.jeelink/node_modules/@serialport/bindings/build/bindings.node', 2021-11-21 12:03:51.759 error Caught by controller[0]: tries: [ 2021-11-21 12:03:51.759 error Caught by controller[0]: at Module._compile (internal/modules/cjs/loader.js:1085:14) { 2021-11-21 12:03:51.759 error Caught by controller[0]: at Object.<anonymous> (/opt/iobroker/node_modules/iobroker.jeelink/node_modules/@serialport/bindings/lib/index.js:14:22) 2021-11-21 12:03:51.758 error Caught by controller[0]: at require (internal/modules/cjs/helpers.js:93:18) 2021-11-21 12:03:51.758 error Caught by controller[0]: at Module.require (internal/modules/cjs/loader.js:974:19) 2021-11-21 12:03:51.758 error Caught by controller[0]: at Function.Module._load (internal/modules/cjs/loader.js:790:12) 2021-11-21 12:03:51.758 error Caught by controller[0]: at Module.load (internal/modules/cjs/loader.js:950:32) 2021-11-21 12:03:51.758 error Caught by controller[0]: at Object.Module._extensions..js (internal/modules/cjs/loader.js:1114:10) 2021-11-21 12:03:51.758 error Caught by controller[0]: at Module._compile (internal/modules/cjs/loader.js:1085:14) 2021-11-21 12:03:51.758 error Caught by controller[0]: at Object.<anonymous> (/opt/iobroker/node_modules/iobroker.jeelink/node_modules/@serialport/bindings/lib/linux.js:1:36) 2021-11-21 12:03:51.758 error Caught by controller[0]: at bindings (/opt/iobroker/node_modules/bindings/bindings.js:126:9) 2021-11-21 12:03:51.758 error Caught by controller[0]: → /opt/iobroker/node_modules/iobroker.jeelink/node_modules/@serialport/bindings/lib/binding/node-v83-linux-x64/bindings.node 2021-11-21 12:03:51.758 error Caught by controller[0]: → /opt/iobroker/node_modules/iobroker.jeelink/node_modules/@serialport/bindings/addon-build/default/install-root/bindings.node 2021-11-21 12:03:51.758 error Caught by controller[0]: → /opt/iobroker/node_modules/iobroker.jeelink/node_modules/@serialport/bindings/addon-build/debug/install-root/bindings.node 2021-11-21 12:03:51.757 error Caught by controller[0]: → /opt/iobroker/node_modules/iobroker.jeelink/node_modules/@serialport/bindings/addon-build/release/install-root/bindings.node 2021-11-21 12:03:51.757 error Caught by controller[0]: → /opt/iobroker/node_modules/iobroker.jeelink/node_modules/@serialport/bindings/compiled/14.18.1/linux/x64/bindings.node 2021-11-21 12:03:51.757 error Caught by controller[0]: → /opt/iobroker/node_modules/iobroker.jeelink/node_modules/@serialport/bindings/build/default/bindings.node 2021-11-21 12:03:51.757 error Caught by controller[0]: → /opt/iobroker/node_modules/iobroker.jeelink/node_modules/@serialport/bindings/Release/bindings.node 2021-11-21 12:03:51.757 error Caught by controller[0]: → /opt/iobroker/node_modules/iobroker.jeelink/node_modules/@serialport/bindings/out/Release/bindings.node 2021-11-21 12:03:51.757 error Caught by controller[0]: → /opt/iobroker/node_modules/iobroker.jeelink/node_modules/@serialport/bindings/Debug/bindings.node 2021-11-21 12:03:51.757 error Caught by controller[0]: → /opt/iobroker/node_modules/iobroker.jeelink/node_modules/@serialport/bindings/out/Debug/bindings.node 2021-11-21 12:03:51.757 error Caught by controller[0]: → /opt/iobroker/node_modules/iobroker.jeelink/node_modules/@serialport/bindings/build/Release/bindings.node 2021-11-21 12:03:51.757 error Caught by controller[0]: → /opt/iobroker/node_modules/iobroker.jeelink/node_modules/@serialport/bindings/build/Debug/bindings.node 2021-11-21 12:03:51.757 error Caught by controller[0]: → /opt/iobroker/node_modules/iobroker.jeelink/node_modules/@serialport/bindings/build/bindings.node 2021-11-21 12:03:51.756 error Caught by controller[0]: Error: Could not locate the bindings file. Tried: 2021-11-21 12:03:51.756 error Caught by controller[0]: ^ 2021-11-21 12:03:51.756 error Caught by controller[0]: throw err; 2021-11-21 12:03:51.755 error Caught by controller[0]: /opt/iobroker/node_modules/bindings/bindings.js:135in welches man gehen und den Befehl
npm install --productionausführen sollte??? -
@tepman sagte in Jeelink Adapter startet nicht mehr:
Werde die Sensoren vermutlich gegen Zigbees tauschen.
Rein interessehalber... Gegen welche?
-
@thomas-braun sagte in Jeelink Adapter startet nicht mehr:
@tepman sagte in Jeelink Adapter startet nicht mehr:
Dann bleib vorerst auf node12.
Foxthefox scheint nicht mehr großartig aktiv zu sein. Bedeutet vermutlich für den Adapter jeelink nichts gutes.@foxthefox
Hatte auch schon versucht auf Github ein Issue aufzumachen, aber das scheint bei Jeelink nicht aktiviert zu sein. Oder habe ich mich völlig verguckt???Kann denn sonst Jemand was mit den Fehlermeldungen anfangen und ggf. eine quick&dirty-Lösung anbieten, bis sich Jemand findet, der sich wieder des JeeLink-Adapters annimmt?
Irgendwie möchte ich die vorhandenen über 20 Sensoren nicht gegen Andere austauschen müssen
-
habe auch 10 Sensoren, wenn es keine andere Lösung gibt werde ich auf einen Raspberry Pi wieder FHEM drauf machen und die Sensoren über den FHEM Adapter einbinden.
-
Bleib doch zunächst mal auf node12. Da muss man ja noch nicht von runterspringen. Bis das erforderlich wird hat sich vermutlich bei dem Adapter schon was getan.
-
bin ja schon auf node14, kann man einfach wieder zurück auf die 12er version?
-
@chris76e
Klar. Schau in meiner Signatur, da steht drin wie man es macht. -
@foxthefox
Ich hätte auch gerne wieder einen funktionalen jeelink Adapter -
@rolandm
War
ZULETZT ONLINE 19. MAI 2021 -
@thomas-braun sagte in Jeelink Adapter startet nicht mehr:
@chris76e
Klar. Schau in meiner Signatur, da steht drin wie man es macht.Ganz verstanden habe ich es nicht. Früher stand immer dabei, dass man die alte Node komplett deinstallieren sollte. Das Vorgehen finde ich in den neueren Anleitungen nicht mehr.
Reicht jetzt einfach bei installiertem 14er die Eingabe von unten stehenden Befehlen, wie es in den neueren Anleitungen steht und die 14er ist durch die 12er ersetzt???
curl -sL https://deb.nodesource.com/setup_14.x | sudo -E bash - sudo apt-get install -y nodejs -
Geht nicht, in deinem Fall.
Die node12 muss von Hand gezielt angegeben werden.
Also den Eintrag zu node14 in der nodesource.list auskommentieren oder durch 12 ersetzen und dann die genaue Version 12 installieren. -
@thomas-braun sagte in Jeelink Adapter startet nicht mehr:
Geht nicht, in deinem Fall.
Die node12 muss von Hand gezielt angegeben werden.
Also den Eintrag zu node14 in der nodesource.list auskommentieren oder durch 12 ersetzen und dann die genaue Version 12 installieren.Sorry...
Meinte ich auch...
Hatte vergessen die 14 durch 12 zu ersetzen -
@berchemer
Geht aber trotzdem nicht. Niedrigere Versionsnummern müssen explizit angegeben werden. Wir genau steht in meinem How To drin. -
Sorry, aber bin mit der Anleitung nicht klar gekommen
Für mich hat es funktioniert indem ich die nodejs 14 komplett deinstalliert und danach die 12er neu installiert habe.cd /opt/iobroker iob stop sudo apt-get --purge remove nodejs sudo apt-get autoremove sudo rebootcd /opt/iobroker iob stop curl -sL https://deb.nodesource.com/setup_12.x | sudo -E bash - sudo apt-get install -y nodejs sudo rebootNun habe ich die Ausgaben:
node -v v12.22.7 npm -v 6.14.15Das ist ja schon mal schön.
Ändert aber nicht an der unschönen folgenden Ausgabe im Log, wenn ich versuche den Jeelink-Adapter zu starten:
2021-11-26 10:00:27.707 error instance system.adapter.jeelink.0 terminated with code 1 (JS_CONTROLLER_STOPPED) 2021-11-26 10:00:27.707 error Caught by controller[0]: } 2021-11-26 10:00:27.707 error Caught by controller[0]: ] 2021-11-26 10:00:27.707 error Caught by controller[0]: '/opt/iobroker/node_modules/iobroker.jeelink/node_modules/@serialport/bindings/lib/binding/node-v72-linux-x64/bindings.node' 2021-11-26 10:00:27.707 error Caught by controller[0]: '/opt/iobroker/node_modules/iobroker.jeelink/node_modules/@serialport/bindings/addon-build/default/install-root/bindings.node', 2021-11-26 10:00:27.706 error Caught by controller[0]: '/opt/iobroker/node_modules/iobroker.jeelink/node_modules/@serialport/bindings/addon-build/debug/install-root/bindings.node', 2021-11-26 10:00:27.706 error Caught by controller[0]: '/opt/iobroker/node_modules/iobroker.jeelink/node_modules/@serialport/bindings/addon-build/release/install-root/bindings.node', 2021-11-26 10:00:27.706 error Caught by controller[0]: '/opt/iobroker/node_modules/iobroker.jeelink/node_modules/@serialport/bindings/compiled/12.22.7/linux/x64/bindings.node', 2021-11-26 10:00:27.706 error Caught by controller[0]: '/opt/iobroker/node_modules/iobroker.jeelink/node_modules/@serialport/bindings/build/default/bindings.node', 2021-11-26 10:00:27.706 error Caught by controller[0]: '/opt/iobroker/node_modules/iobroker.jeelink/node_modules/@serialport/bindings/Release/bindings.node', 2021-11-26 10:00:27.706 error Caught by controller[0]: '/opt/iobroker/node_modules/iobroker.jeelink/node_modules/@serialport/bindings/out/Release/bindings.node', 2021-11-26 10:00:27.706 error Caught by controller[0]: '/opt/iobroker/node_modules/iobroker.jeelink/node_modules/@serialport/bindings/Debug/bindings.node', 2021-11-26 10:00:27.706 error Caught by controller[0]: '/opt/iobroker/node_modules/iobroker.jeelink/node_modules/@serialport/bindings/out/Debug/bindings.node', 2021-11-26 10:00:27.706 error Caught by controller[0]: '/opt/iobroker/node_modules/iobroker.jeelink/node_modules/@serialport/bindings/build/Release/bindings.node', 2021-11-26 10:00:27.706 error Caught by controller[0]: '/opt/iobroker/node_modules/iobroker.jeelink/node_modules/@serialport/bindings/build/Debug/bindings.node', 2021-11-26 10:00:27.706 error Caught by controller[0]: '/opt/iobroker/node_modules/iobroker.jeelink/node_modules/@serialport/bindings/build/bindings.node', 2021-11-26 10:00:27.706 error Caught by controller[0]: tries: [ 2021-11-26 10:00:27.705 error Caught by controller[0]: at Module._compile (internal/modules/cjs/loader.js:999:30) { 2021-11-26 10:00:27.705 error Caught by controller[0]: at Object.<anonymous> (/opt/iobroker/node_modules/iobroker.jeelink/node_modules/@serialport/bindings/lib/index.js:14:22) 2021-11-26 10:00:27.705 error Caught by controller[0]: at require (internal/modules/cjs/helpers.js:74:18) 2021-11-26 10:00:27.705 error Caught by controller[0]: at Module.require (internal/modules/cjs/loader.js:887:19) 2021-11-26 10:00:27.705 error Caught by controller[0]: at Function.Module._load (internal/modules/cjs/loader.js:708:14) 2021-11-26 10:00:27.705 error Caught by controller[0]: at Module.load (internal/modules/cjs/loader.js:863:32) 2021-11-26 10:00:27.705 error Caught by controller[0]: at Object.Module._extensions..js (internal/modules/cjs/loader.js:1027:10) 2021-11-26 10:00:27.705 error Caught by controller[0]: at Module._compile (internal/modules/cjs/loader.js:999:30) 2021-11-26 10:00:27.705 error Caught by controller[0]: at Object.<anonymous> (/opt/iobroker/node_modules/iobroker.jeelink/node_modules/@serialport/bindings/lib/linux.js:1:36) 2021-11-26 10:00:27.705 error Caught by controller[0]: at bindings (/opt/iobroker/node_modules/bindings/bindings.js:126:9) 2021-11-26 10:00:27.705 error Caught by controller[0]: → /opt/iobroker/node_modules/iobroker.jeelink/node_modules/@serialport/bindings/lib/binding/node-v72-linux-x64/bindings.node 2021-11-26 10:00:27.705 error Caught by controller[0]: → /opt/iobroker/node_modules/iobroker.jeelink/node_modules/@serialport/bindings/addon-build/default/install-root/bindings.node 2021-11-26 10:00:27.705 error Caught by controller[0]: → /opt/iobroker/node_modules/iobroker.jeelink/node_modules/@serialport/bindings/addon-build/debug/install-root/bindings.node 2021-11-26 10:00:27.704 error Caught by controller[0]: → /opt/iobroker/node_modules/iobroker.jeelink/node_modules/@serialport/bindings/addon-build/release/install-root/bindings.node 2021-11-26 10:00:27.704 error Caught by controller[0]: → /opt/iobroker/node_modules/iobroker.jeelink/node_modules/@serialport/bindings/compiled/12.22.7/linux/x64/bindings.node 2021-11-26 10:00:27.704 error Caught by controller[0]: → /opt/iobroker/node_modules/iobroker.jeelink/node_modules/@serialport/bindings/build/default/bindings.node 2021-11-26 10:00:27.704 error Caught by controller[0]: → /opt/iobroker/node_modules/iobroker.jeelink/node_modules/@serialport/bindings/Release/bindings.node 2021-11-26 10:00:27.704 error Caught by controller[0]: → /opt/iobroker/node_modules/iobroker.jeelink/node_modules/@serialport/bindings/out/Release/bindings.node 2021-11-26 10:00:27.704 error Caught by controller[0]: → /opt/iobroker/node_modules/iobroker.jeelink/node_modules/@serialport/bindings/Debug/bindings.node 2021-11-26 10:00:27.704 error Caught by controller[0]: → /opt/iobroker/node_modules/iobroker.jeelink/node_modules/@serialport/bindings/out/Debug/bindings.node 2021-11-26 10:00:27.704 error Caught by controller[0]: → /opt/iobroker/node_modules/iobroker.jeelink/node_modules/@serialport/bindings/build/Release/bindings.node 2021-11-26 10:00:27.704 error Caught by controller[0]: → /opt/iobroker/node_modules/iobroker.jeelink/node_modules/@serialport/bindings/build/Debug/bindings.node 2021-11-26 10:00:27.704 error Caught by controller[0]: → /opt/iobroker/node_modules/iobroker.jeelink/node_modules/@serialport/bindings/build/bindings.node 2021-11-26 10:00:27.704 error Caught by controller[0]: Error: Could not locate the bindings file. Tried: 2021-11-26 10:00:27.703 error Caught by controller[0]: ^ 2021-11-26 10:00:27.703 error Caught by controller[0]: throw err; 2021-11-26 10:00:27.703 error Caught by controller[0]: /opt/iobroker/node_modules/bindings/bindings.js:135 2021-11-26 10:00:27.577 info instance system.adapter.jeelink.0 started with pid 12700Hätte hier Jemand eine Lösung für???
-
@berchemer sagte in Jeelink Adapter startet nicht mehr:
Sorry, aber bin mit der Anleitung nicht klar gekommen
Konkret?
-
@thomas-braun sagte in Jeelink Adapter startet nicht mehr:
@berchemer sagte in Jeelink Adapter startet nicht mehr:
Sorry, aber bin mit der Anleitung nicht klar gekommen
Konkret?
Mit den Änderungen in der Datei und so weiter... Vielleicht war ich auch nicht präzise genug. Ändern in der Datei in 12 statt 14 hat nicht zu den von mir gewünschten Erfolgen geführt oder wie auch immer. Soll keine Kritik sein. Wird sicherlich an meiner Ungeduld gelegen haben
