Navigation

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

    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 Adapter schmeißt warnungen

    This topic has been deleted. Only users with topic management privileges can see it.
    • B
      Brokerti @AlexHaxe last edited by

      @alexhaxe korrekt. Es steht dann enabled debug da. wenn ich Debug aktiviere, erhalte ich dennoch Nicht die besagte Debugmeldung!

      Selbst wenn ich den BWM lösche und Batterien entferne kommen alle 15sec die Log Einträge.
      Auch wenn ich ihn in der Instanz deaktiviere.

      Folglich "spukt" sich die Instanz selbst etwas vor.

      Vorhin habe ich mal auf "reconfigure" geklickt und damit kam dann zumindest die Occupancy Funktion zurück.

      Angefangen hat das Problem, seit der Ventilator im Zimmer steht :D.

      A 1 Reply Last reply Reply Quote 0
      • A
        AlexHaxe @Brokerti last edited by

        @brokerti said in Zigbee Adapter schmeißt warnungen:

        Selbst wenn ich den BWM lösche und Batterien entferne kommen alle 15sec die Log Einträge.
        Auch wenn ich ihn in der Instanz deaktiviere.

        Folglich "spukt" sich die Instanz selbst etwas vor.

        Das klingt sehr unwahrscheinlich. Ein Batterie-Gerät ohne Batterien sendet nichts. Bist Du Dir sicher, dass Du den richtigen Bewegungsmelder anschaust? Die Hex-Zahlen sehen sich ja immer zum Verwechseln ähnlich.

        Die Meldung info debug devices set to [] kommt nur beim Hochfahren des Adapters, oder beim Anklicken der Käfer. Wobei die [] durch eine Liste der IDs ersetzt wird, sobald Debug aktiv ist.

        Ob ein Ventilator mit einem Bewegungsmelder interagiert, bzw. dessen Belegt Status beeinflussen kann, entzieht sich derzeit meiner Kenntnis. Die Debug-Meldungen sind aber unabhängig davon.

        B 1 Reply Last reply Reply Quote 0
        • B
          Brokerti @AlexHaxe last edited by

          @alexhaxe du hattest recht!
          Ich hätte schwören können, ich war am richtigen BWM.
          Nummer verglichen und siehe da, es war ein anderer. Weshalb dieser auf Debug stand, kann ich mir nicht erklären..

          Somit wünsche ich eine ruhige und kühle Nacht. Vielen Dank! 🙂

          Autodidakt 1 Reply Last reply Reply Quote 0
          • Autodidakt
            Autodidakt @Brokerti last edited by

            Ich hätte schwören können, ich war am richtigen BWM.

            Was ist ein BWM?

            sigi234 1 Reply Last reply Reply Quote 0
            • sigi234
              sigi234 Forum Testing Most Active @Autodidakt last edited by

              @autodidakt sagte in Zigbee Adapter schmeißt warnungen:

              Ich hätte schwören können, ich war am richtigen BWM.

              Was ist ein BWM?

              Bewegungsmelder

              1 Reply Last reply Reply Quote 1
              • Autodidakt
                Autodidakt last edited by

                Kann niemand mit dieser Fehlermeldung etwas anfangen?

                2025-06-26T08:09:05.411Z Installieren : node-red-contrib-zigbee 0.21.0
                
                2025-06-26T08:09:05.300Z npm install --no-audit --no-update-notifier --no-fund --save --save-prefix=~ --production --engine-strict node-red-contrib-zigbee@0.21.0
                2025-06-26T08:09:05.697Z [err] npm warn config production Use `--omit=dev` instead.
                2025-06-26T08:09:21.023Z [err] npm warn deprecated vis@4.21.0: Please consider using https://github.com/visjs
                2025-06-26T08:09:27.263Z [err] npm error code 1
                2025-06-26T08:09:27.264Z [err] npm error path /opt/iobroker/iobroker-data/node-red/node_modules/zigbee-herdsman/node_modules/@serialport/bindings
                2025-06-26T08:09:27.264Z [err] npm error command failed
                2025-06-26T08:09:27.264Z [err] npm error command sh -c node-gyp rebuild
                2025-06-26T08:09:27.264Z [err] npm error make: Entering directory '/opt/iobroker/iobroker-data/node-red/node_modules/zigbee-herdsman/node_modules/@serialport/bindings/build'
                2025-06-26T08:09:27.264Z [err] npm error   CXX(target) Release/obj.target/bindings/src/serialport.o
                2025-06-26T08:09:27.264Z [err] npm error make: Leaving directory '/opt/iobroker/iobroker-data/node-red/node_modules/zigbee-herdsman/node_modules/@serialport/bindings/build'
                2025-06-26T08:09:27.266Z [err] npm error gyp info it worked if it ends with ok
                2025-06-26T08:09:27.266Z [err] npm error gyp info using node-gyp@8.4.1
                2025-06-26T08:09:27.266Z [err] npm error gyp info using node@20.19.3 | linux | arm64
                2025-06-26T08:09:27.266Z [err] npm error gyp info find Python using Python version 3.9.2 found at "/usr/bin/python3"
                2025-06-26T08:09:27.266Z [err] npm error gyp info spawn /usr/bin/python3
                2025-06-26T08:09:27.266Z [err] npm error gyp info spawn args [
                2025-06-26T08:09:27.266Z [err] npm error gyp info spawn args   '/opt/iobroker/node_modules/node-gyp/gyp/gyp_main.py',
                2025-06-26T08:09:27.266Z [err] npm error gyp info spawn args   'binding.gyp',
                2025-06-26T08:09:27.266Z [err] npm error gyp info spawn args   '-f',
                2025-06-26T08:09:27.266Z [err] npm error gyp info spawn args   'make',
                2025-06-26T08:09:27.266Z [err] npm error gyp info spawn args   '-I',
                2025-06-26T08:09:27.266Z [err] npm error gyp info spawn args   '/opt/iobroker/iobroker-data/node-red/node_modules/zigbee-herdsman/node_modules/@serialport/bindings/build/config.gypi',
                2025-06-26T08:09:27.266Z [err] npm error gyp info spawn args   '-I',
                2025-06-26T08:09:27.266Z [err] npm error gyp info spawn args   '/opt/iobroker/node_modules/node-gyp/addon.gypi',
                2025-06-26T08:09:27.266Z [err] npm error gyp info spawn args   '-I',
                2025-06-26T08:09:27.266Z [err] npm error gyp info spawn args   '/home/iobroker/.cache/node-gyp/20.19.3/include/node/common.gypi',
                2025-06-26T08:09:27.266Z [err] npm error gyp info spawn args   '-Dlibrary=shared_library',
                2025-06-26T08:09:27.266Z [err] npm error gyp info spawn args   '-Dvisibility=default',
                2025-06-26T08:09:27.266Z [err] npm error gyp info spawn args   '-Dnode_root_dir=/home/iobroker/.cache/node-gyp/20.19.3',
                2025-06-26T08:09:27.266Z [err] npm error gyp info spawn args   '-Dnode_gyp_dir=/opt/iobroker/node_modules/node-gyp',
                2025-06-26T08:09:27.266Z [err] npm error gyp info spawn args   '-Dnode_lib_file=/home/iobroker/.cache/node-gyp/20.19.3/<(target_arch)/node.lib',
                2025-06-26T08:09:27.266Z [err] npm error gyp info spawn args   '-Dmodule_root_dir=/opt/iobroker/iobroker-data/node-red/node_modules/zigbee-herdsman/node_modules/@serialport/bindings',
                2025-06-26T08:09:27.266Z [err] npm error gyp info spawn args   '-Dnode_engine=v8',
                2025-06-26T08:09:27.266Z [err] npm error gyp info spawn args   '--depth=.',
                2025-06-26T08:09:27.266Z [err] npm error gyp info spawn args   '--no-parallel',
                2025-06-26T08:09:27.266Z [err] npm error gyp info spawn args   '--generator-output',
                2025-06-26T08:09:27.266Z [err] npm error gyp info spawn args   'build',
                2025-06-26T08:09:27.266Z [err] npm error gyp info spawn args   '-Goutput_dir=.'
                2025-06-26T08:09:27.266Z [err] npm error gyp info spawn args ]
                2025-06-26T08:09:27.266Z [err] npm error gyp info spawn make
                2025-06-26T08:09:27.266Z [err] npm error gyp info spawn args [ 'BUILDTYPE=Release', '-C', 'build' ]
                2025-06-26T08:09:27.266Z [err] npm error In file included from ../../../nan/nan.h:178,
                2025-06-26T08:09:27.266Z [err] npm error                  from ../src/./serialport.h:13,
                2025-06-26T08:09:27.266Z [err] npm error                  from ../src/serialport.cpp:1:
                2025-06-26T08:09:27.266Z [err] npm error ../../../nan/nan_callbacks.h:55:23: error: ‘AccessorSignature’ is not a member of ‘v8’
                2025-06-26T08:09:27.266Z [err] npm error    55 | typedef v8::Local<v8::AccessorSignature> Sig;
                2025-06-26T08:09:27.266Z [err] npm error       |                       ^~~~~~~~~~~~~~~~~
                2025-06-26T08:09:27.266Z [err] npm error ../../../nan/nan_callbacks.h:55:40: error: template argument 1 is invalid
                2025-06-26T08:09:27.266Z [err] npm error    55 | typedef v8::Local<v8::AccessorSignature> Sig;
                2025-06-26T08:09:27.266Z [err] npm error       |                                        ^
                2025-06-26T08:09:27.266Z [err] npm error In file included from ../src/./serialport.h:13,
                2025-06-26T08:09:27.266Z [err] npm error                  from ../src/serialport.cpp:1:
                2025-06-26T08:09:27.266Z [err] npm error ../../../nan/nan.h: In function ‘void Nan::SetAccessor(v8::Local<v8::ObjectTemplate>, v8::Local<v8::String>, Nan::GetterCallback, Nan::SetterCallback, v8::Local<v8::Value>, v8::AccessControl, v8::PropertyAttribute, Nan::imp::Sig)’:
                2025-06-26T08:09:27.266Z [err] npm error ../../../nan/nan.h:2551:16: error: no matching function for call to ‘v8::ObjectTemplate::SetAccessor(v8::Local<v8::String>&, void (*&)(v8::Local<v8::Name>, const v8::PropertyCallbackInfo<v8::Value>&), void (*&)(v8::Local<v8::Name>, v8::Local<v8::Value>, const v8::PropertyCallbackInfo<void>&), v8::Local<v8::Object>&, v8::AccessControl&, v8::PropertyAttribute&, Nan::imp::Sig&)’
                2025-06-26T08:09:27.266Z [err] npm error  2551 |     , signature);
                2025-06-26T08:09:27.266Z [err] npm error       |                ^
                2025-06-26T08:09:27.266Z [err] npm error In file included from /home/iobroker/.cache/node-gyp/20.19.3/include/node/v8-function.h:15,
                2025-06-26T08:09:27.266Z [err] npm error                  from /home/iobroker/.cache/node-gyp/20.19.3/include/node/v8.h:33,
                2025-06-26T08:09:27.266Z [err] npm error                  from /home/iobroker/.cache/node-gyp/20.19.3/include/node/node.h:73,
                2025-06-26T08:09:27.266Z [err] npm error                  from ../../../nan/nan.h:58,
                2025-06-26T08:09:27.266Z [err] npm error                  from ../src/./serialport.h:13,
                2025-06-26T08:09:27.266Z [err] npm error                  from ../src/serialport.cpp:1:
                2025-06-26T08:09:27.266Z [err] npm error /home/iobroker/.cache/node-gyp/20.19.3/include/node/v8-template.h:809:8: note: candidate: ‘void v8::ObjectTemplate::SetAccessor(v8::Local<v8::String>, v8::AccessorGetterCallback, v8::AccessorSetterCallback, v8::Local<v8::Value>, v8::AccessControl, v8::PropertyAttribute, v8::SideEffectType, v8::SideEffectType)’
                2025-06-26T08:09:27.266Z [err] npm error   809 |   void SetAccessor(
                2025-06-26T08:09:27.266Z [err] npm error       |        ^~~~~~~~~~~
                2025-06-26T08:09:27.266Z [err] npm error /home/iobroker/.cache/node-gyp/20.19.3/include/node/v8-template.h:814:22: note:   no known conversion for argument 7 from ‘Nan::imp::Sig’ {aka ‘int’} to ‘v8::SideEffectType’
                2025-06-26T08:09:27.266Z [err] npm error   814 |       SideEffectType getter_side_effect_type = SideEffectType::kHasSideEffect,
                2025-06-26T08:09:27.266Z [err] npm error       |       ~~~~~~~~~~~~~~~^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
                2025-06-26T08:09:27.266Z [err] npm error /home/iobroker/.cache/node-gyp/20.19.3/include/node/v8-template.h:816:8: note: candidate: ‘void v8::ObjectTemplate::SetAccessor(v8::Local<v8::Name>, v8::AccessorNameGetterCallback, v8::AccessorNameSetterCallback, v8::Local<v8::Value>, v8::AccessControl, v8::PropertyAttribute, v8::SideEffectType, v8::SideEffectType)’
                2025-06-26T08:09:27.266Z [err] npm error   816 |   void SetAccessor(
                2025-06-26T08:09:27.266Z [err] npm error       |        ^~~~~~~~~~~
                2025-06-26T08:09:27.266Z [err] npm error /home/iobroker/.cache/node-gyp/20.19.3/include/node/v8-template.h:821:22: note:   no known conversion for argument 7 from ‘Nan::imp::Sig’ {aka ‘int’} to ‘v8::SideEffectType’
                2025-06-26T08:09:27.266Z [err] npm error   821 |       SideEffectType getter_side_effect_type = SideEffectType::kHasSideEffect,
                2025-06-26T08:09:27.266Z [err] npm error       |       ~~~~~~~~~~~~~~~^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
                2025-06-26T08:09:27.266Z [err] npm error ../src/serialport.cpp: In function ‘Nan::NAN_METHOD_RETURN_TYPE Open(Nan::NAN_METHOD_ARGS_TYPE)’:
                2025-06-26T08:09:27.266Z [err] npm error ../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]
                2025-06-26T08:09:27.266Z [err] npm error    78 |   uv_queue_work(uv_default_loop(), req, EIO_Open, (uv_after_work_cb)EIO_AfterOpen);
                2025-06-26T08:09:27.266Z [err] npm error       |                                                   ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
                2025-06-26T08:09:27.266Z [err] npm error ../src/serialport.cpp: In function ‘Nan::NAN_METHOD_RETURN_TYPE Update(Nan::NAN_METHOD_ARGS_TYPE)’:
                2025-06-26T08:09:27.266Z [err] npm error ../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]
                2025-06-26T08:09:27.266Z [err] npm error   135 |   uv_queue_work(uv_default_loop(), req, EIO_Update, (uv_after_work_cb)EIO_AfterUpdate);
                2025-06-26T08:09:27.266Z [err] npm error       |                                                     ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
                2025-06-26T08:09:27.266Z [err] npm error ../src/serialport.cpp: In function ‘Nan::NAN_METHOD_RETURN_TYPE Close(Nan::NAN_METHOD_ARGS_TYPE)’:
                2025-06-26T08:09:27.266Z [err] npm error ../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]
                2025-06-26T08:09:27.266Z [err] npm error   175 |   uv_queue_work(uv_default_loop(), req, EIO_Close, (uv_after_work_cb)EIO_AfterClose);
                2025-06-26T08:09:27.266Z [err] npm error       |                                                    ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
                2025-06-26T08:09:27.266Z [err] npm error ../src/serialport.cpp: In function ‘Nan::NAN_METHOD_RETURN_TYPE Flush(Nan::NAN_METHOD_ARGS_TYPE)’:
                2025-06-26T08:09:27.266Z [err] npm error ../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]
                2025-06-26T08:09:27.266Z [err] npm error   215 |   uv_queue_work(uv_default_loop(), req, EIO_Flush, (uv_after_work_cb)EIO_AfterFlush);
                2025-06-26T08:09:27.266Z [err] npm error       |                                                    ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
                2025-06-26T08:09:27.266Z [err] npm error ../src/serialport.cpp: In function ‘Nan::NAN_METHOD_RETURN_TYPE Set(Nan::NAN_METHOD_ARGS_TYPE)’:
                2025-06-26T08:09:27.266Z [err] npm error ../src/serialport.cpp:271: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]
                2025-06-26T08:09:27.266Z [err] npm error   271 |   uv_queue_work(uv_default_loop(), req, EIO_Set, (uv_after_work_cb)EIO_AfterSet);
                2025-06-26T08:09:27.266Z [err] npm error       |                                                  ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
                2025-06-26T08:09:27.266Z [err] npm error ../src/serialport.cpp: In function ‘Nan::NAN_METHOD_RETURN_TYPE Get(Nan::NAN_METHOD_ARGS_TYPE)’:
                2025-06-26T08:09:27.266Z [err] npm error ../src/serialport.cpp:316: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]
                2025-06-26T08:09:27.266Z [err] npm error   316 |   uv_queue_work(uv_default_loop(), req, EIO_Get, (uv_after_work_cb)EIO_AfterGet);
                2025-06-26T08:09:27.266Z [err] npm error       |                                                  ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
                2025-06-26T08:09:27.266Z [err] npm error ../src/serialport.cpp: In function ‘Nan::NAN_METHOD_RETURN_TYPE GetBaudRate(Nan::NAN_METHOD_ARGS_TYPE)’:
                2025-06-26T08:09:27.266Z [err] npm error ../src/serialport.cpp:366: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]
                2025-06-26T08:09:27.266Z [err] npm error   366 |   uv_queue_work(uv_default_loop(), req, EIO_GetBaudRate, (uv_after_work_cb)EIO_AfterGetBaudRate);
                2025-06-26T08:09:27.266Z [err] npm error       |                                                          ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
                2025-06-26T08:09:27.266Z [err] npm error ../src/serialport.cpp: In function ‘Nan::NAN_METHOD_RETURN_TYPE Drain(Nan::NAN_METHOD_ARGS_TYPE)’:
                2025-06-26T08:09:27.266Z [err] npm error ../src/serialport.cpp:412: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]
                2025-06-26T08:09:27.266Z [err] npm error   412 |   uv_queue_work(uv_default_loop(), req, EIO_Drain, (uv_after_work_cb)EIO_AfterDrain);
                2025-06-26T08:09:27.266Z [err] npm error       |                                                    ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
                2025-06-26T08:09:27.266Z [err] npm error ../src/serialport.cpp: At global scope:
                2025-06-26T08:09:27.266Z [err] npm error ../src/serialport.cpp:433:28: warning: unnecessary parentheses in declaration of ‘ToParityEnum’ [-Wparentheses]
                2025-06-26T08:09:27.266Z [err] npm error   433 | SerialPortParity NAN_INLINE(ToParityEnum(const v8::Local<v8::String>& v8str)) {
                2025-06-26T08:09:27.266Z [err] npm error       |                            ^
                2025-06-26T08:09:27.266Z [err] npm error ../src/serialport.cpp:452:30: warning: unnecessary parentheses in declaration of ‘ToStopBitEnum’ [-Wparentheses]
                2025-06-26T08:09:27.266Z [err] npm error   452 | SerialPortStopBits NAN_INLINE(ToStopBitEnum(double stopBits)) {
                2025-06-26T08:09:27.266Z [err] npm error       |                              ^
                2025-06-26T08:09:27.266Z [err] npm error In file included from ../../../nan/nan.h:58,
                2025-06-26T08:09:27.266Z [err] npm error                  from ../src/./serialport.h:13,
                2025-06-26T08:09:27.266Z [err] npm error                  from ../src/serialport.cpp:1:
                2025-06-26T08:09:27.266Z [err] npm error /home/iobroker/.cache/node-gyp/20.19.3/include/node/node.h:1227: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]
                2025-06-26T08:09:27.266Z [err] npm error  1227 |       (node::addon_register_func) (regfunc),                          \
                2025-06-26T08:09:27.266Z [err] npm error       |       ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
                2025-06-26T08:09:27.266Z [err] npm error /home/iobroker/.cache/node-gyp/20.19.3/include/node/node.h:1261:3: note: in expansion of macro ‘NODE_MODULE_X’
                2025-06-26T08:09:27.266Z [err] npm error  1261 |   NODE_MODULE_X(modname, regfunc, NULL, 0)  // NOLINT (readability/null_usage)
                2025-06-26T08:09:27.266Z [err] npm error       |   ^~~~~~~~~~~~~
                2025-06-26T08:09:27.266Z [err] npm error ../src/serialport.cpp:486:1: note: in expansion of macro ‘NODE_MODULE’
                2025-06-26T08:09:27.266Z [err] npm error   486 | NODE_MODULE(serialport, init);
                2025-06-26T08:09:27.266Z [err] npm error       | ^~~~~~~~~~~
                2025-06-26T08:09:27.266Z [err] npm error make: *** [bindings.target.mk:109: Release/obj.target/bindings/src/serialport.o] Error 1
                2025-06-26T08:09:27.266Z [err] npm error gyp ERR! build error 
                2025-06-26T08:09:27.266Z [err] npm error gyp ERR! stack Error: `make` failed with exit code: 2
                2025-06-26T08:09:27.266Z [err] npm error gyp ERR! stack     at ChildProcess.onExit (/opt/iobroker/node_modules/node-gyp/lib/build.js:194:23)
                2025-06-26T08:09:27.266Z [err] npm error gyp ERR! stack     at ChildProcess.emit (node:events:524:28)
                2025-06-26T08:09:27.266Z [err] npm error gyp ERR! stack     at ChildProcess._handle.onexit (node:internal/child_process:293:12)
                2025-06-26T08:09:27.266Z [err] npm error gyp ERR! System Linux 6.1.21-v8+
                2025-06-26T08:09:27.266Z [err] npm error gyp ERR! command "/usr/bin/node" "/opt/iobroker/node_modules/.bin/node-gyp" "rebuild"
                2025-06-26T08:09:27.266Z [err] npm error gyp ERR! cwd /opt/iobroker/iobroker-data/node-red/node_modules/zigbee-herdsman/node_modules/@serialport/bindings
                2025-06-26T08:09:27.266Z [err] npm error gyp ERR! node -v v20.19.3
                2025-06-26T08:09:27.266Z [err] npm error gyp ERR! node-gyp -v v8.4.1
                2025-06-26T08:09:27.266Z [err] npm error gyp ERR! not ok
                2025-06-26T08:09:27.274Z [err] npm error A complete log of this run can be found in: /home/iobroker/.npm/_logs/2025-06-26T08_09_05_562Z-debug-0.log
                2025-06-26T08:09:27.317Z rc=1
                
                Homoran 1 Reply Last reply Reply Quote 0
                • Homoran
                  Homoran Global Moderator Administrators @Autodidakt last edited by

                  @autodidakt sagte in Zigbee Adapter schmeißt warnungen:

                  Kann niemand mit dieser Fehlermeldung etwas anfangen?

                  doch!
                  aber du bist falsch hier!

                  @autodidakt sagte in Zigbee Adapter schmeißt warnungen:

                  Installieren : node-red-contrib-zigbee 0.21.0

                  hat nichts mit dem zigbee-Adapter zu tun!

                  1 Reply Last reply Reply Quote 1
                  • Autodidakt
                    Autodidakt last edited by

                    @homoran Achso, wo muss ich denn damit hin?

                    Homoran 1 Reply Last reply Reply Quote 0
                    • Homoran
                      Homoran Global Moderator Administrators @Autodidakt last edited by

                      @autodidakt sagte in Zigbee Adapter schmeißt warnungen:

                      @homoran Achso, wo muss ich denn damit hin?

                      roter und fetter konnte ich es nicht machen.

                      es besteht natürlich noch die Möglichkeit dass du da gerade irgendwas ganz snderes tust.
                      Da du nicht sagst was du tust, wenn diese Meldung auftritt, kann ich dir nicht sagen wohin du genau musst

                      Autodidakt 1 Reply Last reply Reply Quote 0
                      • Autodidakt
                        Autodidakt @Homoran last edited by Autodidakt

                        @homoran

                        af82351a-75d1-4df1-b39e-4b3e9bc85372-image.png

                        Ich möchte nur installieren.
                        Ich möchte auf meinem Node red Dashboard einen ein/aus Button für ein zigbee Gerät.

                        Ich weiß nicht, was ich Dir verheimlicht hätte...

                        STOP! Node red schreibt, dass dieser Knoten aufgegeben wurde. IoB hat also nichts damit zu tun.

                        Dank euch.

                        Mfg
                        Tom

                        Homoran 1 Reply Last reply Reply Quote 0
                        • Homoran
                          Homoran Global Moderator Administrators @Autodidakt last edited by

                          @autodidakt sagte in Zigbee Adapter schmeißt warnungen:

                          Ich möchte nur installieren.

                          was?
                          wo?
                          wie?

                          @autodidakt sagte in Zigbee Adapter schmeißt warnungen:

                          auf meinem Node red Dashboard

                          und warum

                          @autodidakt sagte in Zigbee Adapter schmeißt warnungen:

                          IoB hat also nichts damit zu tun

                          oder hast du nicht den node-red Adapter, sondern eine standalone node-red Installation?

                          @autodidakt sagte in Zigbee Adapter schmeißt warnungen:

                          Ich weiß nicht, was ich Dir verheimlicht hätte...

                          siehe die noch immer offenen Fragen

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

                            @homoran sagte in Zigbee Adapter schmeißt warnungen:

                            @autodidakt sagte in Zigbee Adapter schmeißt warnungen:

                            Ich möchte nur installieren.

                            was?
                            wo?
                            wie?

                            @autodidakt sagte in Zigbee Adapter schmeißt warnungen:

                            auf meinem Node red Dashboard

                            und warum

                            @autodidakt sagte in Zigbee Adapter schmeißt warnungen:

                            IoB hat also nichts damit zu tun

                            oder hast du nicht den node-red Adapter, sondern eine standalone node-red Installation?

                            @autodidakt sagte in Zigbee Adapter schmeißt warnungen:

                            Ich weiß nicht, was ich Dir verheimlicht hätte...

                            siehe die noch immer offenen Fragen

                            was?
                            node-red-contrib-zigbee
                            wo?
                            node-red Adapter V 5.2.1 in IoBroker
                            wie
                            über die Palletten im node-red Adapter

                            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

                            862
                            Online

                            31.9k
                            Users

                            80.1k
                            Topics

                            1.3m
                            Posts

                            7
                            32
                            617
                            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