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.
    • Thomas Braun
      Thomas Braun Most Active @Autodidakt last edited by Thomas Braun

      @autodidakt sagte in Zigbee Adapter schmeißt warnungen:

      Debian GNU/Linux 11 (bullseye)

      Losgelöst vom Problem:
      Bring das Ding in allernächster Zeit auf das aktuelle Release Debian 12 'Bookworm'.

      Per Neuinstallation.

      Zum Problem:
      Setz das Gerät auf den 'link-by-id' fest, nicht auf /dev/ttyUSB0. Das Gerät kann u. U. beim nächsten Boot woanders liegen.

      USB-Devices by-id:
      USB-Sticks - Avoid direct links to /dev/tty* in your adapter setups, please always prefer the links 'by-id':

      /dev/serial/by-id/usb-0658_0200_E3040A02-4A02-0113-1510-041500BFCC64-if00
      /dev/serial/by-id/usb-ITead_Sonoff_Zigbee_3.0_USB_Dongle_Plus_dad0c14dc174ef11b4f0cd8c8fcc3fa0-if00-port0

      *** ZigBee Settings ***
      HINT:
      Your zigbee.0 COM-Port is NOT matching 'by-id'. Please check your setting:
      /dev/ttyUSB0

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

        @autodidakt said in Zigbee Adapter schmeißt warnungen:

        2025-06-25 20:14:15.705 info debug devices set to ["ffffb40e060599a0"]

        das ist die relevante Zeile. Du hast das Debugging für das betroffene Gerät eingeschaltet. Schau Dir mal die Kachel des Geräts an. Der grüne Käfer dort sollte weiß sein, dann bleiben auch die Meldungen stumm.

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

          Danke euch, Läuft.

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

            @thomas-braun sagte in Zigbee Adapter schmeißt warnungen:

            @autodidakt sagte in Zigbee Adapter schmeißt warnungen:

            Debian GNU/Linux 11 (bullseye)

            Losgelöst vom Problem:
            Bring das Ding in allernächster Zeit auf das aktuelle Release Debian 12 'Bookworm'.

            Per Neuinstallation.

            Gibt es dazu eine Anleitung?

            Reicht es, den Iobroker Ordner nach neuinstallation in die neue Installation zu kopieren?

            Thomas Braun 2 Replies Last reply Reply Quote 0
            • Thomas Braun
              Thomas Braun Most Active @Autodidakt last edited by

              @autodidakt sagte in Zigbee Adapter schmeißt warnungen:

              Per Neuinstallation.

              Ja. Neuinstallieren.

              https://forum.iobroker.net/topic/51869/installation-auf-raspi-einfacher-geht-s-nicht

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

                @thomas-braun Merci, schau ich mir an.

                1 Reply Last reply Reply Quote 0
                • Thomas Braun
                  Thomas Braun Most Active @Autodidakt last edited by

                  @autodidakt sagte in Zigbee Adapter schmeißt warnungen:

                  Reicht es, den Iobroker Ordner nach neuinstallation in die neue Installation zu kopieren?

                  Nein, das macht man über ein ordentliches Backup mit dem Backitup-Adapter.

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

                    @thomas-braun Auch nicht schlecht, die Idee... 😊

                    Thomas Braun 1 Reply Last reply Reply Quote 0
                    • Thomas Braun
                      Thomas Braun Most Active @Autodidakt last edited by

                      @autodidakt

                      Ist jedenfalls eine bessere Idee als 'irgendwas wild' in die neue Installation zu kopieren.

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

                        @thomas-braun Super Sache, Danke für eure Hilfe. Jetzt komm ich wieder ein Stück weiter...

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

                          Und was könnte denn da falsch gelaufen sein?

                          
                          node-red.0
                          2025-06-25 20:50:44.811	error	Node-RED: Error: Install failed at /opt/iobroker/node_modules/@node-red/registry/lib/installer.js:288:25 at process.processTicksAndRejections (node:internal/process/task_queues:95:5) 25 Jun 20:50:44 - [error] Error: Install failed at /opt/iobroker/node_modules/@node-red/registry/lib/installer.js:288:25 at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
                          
                          node-red.0
                          2025-06-25 20:50:44.809	warn	Node-RED: 25 Jun 20:50:44 - [warn] npm warn config production Use `--omit=dev` instead. npm warn deprecated vis@4.21.0: Please consider using https://github.com/visjs npm error code 1 npm error path /opt/iobroker/iobroker-data/node-red/node_modules/zigbee-herdsman/node_modules/@serialport/bindings npm error command failed npm error command sh -c node-gyp rebuild npm error make: Entering directory '/opt/iobroker/iobroker-data/node-red/node_modules/zigbee-herdsman/node_modules/@serialport/bindings/build' npm error CXX(target) Release/obj.target/bindings/src/serialport.o npm error make: Leaving directory '/opt/iobroker/iobroker-data/node-red/node_modules/zigbee-herdsman/node_modules/@serialport/bindings/build' npm error gyp info it worked if it ends with ok npm error gyp info using node-gyp@8.4.1 npm error gyp info using node@20.19.3 | linux | arm64 npm error gyp info find Python using Python version 3.9.2 found at "/usr/bin/python3" npm error gyp info spawn /usr/bin/python3 npm error gyp info spawn args [ npm error gyp info spawn args '/opt/iobroker/node_modules/node-gyp/gyp/gyp_main.py', npm error gyp info spawn args 'binding.gyp', npm error gyp info spawn args '-f', npm error gyp info spawn args 'make', npm error gyp info spawn args '-I', npm error gyp info spawn args '/opt/iobroker/iobroker-data/node-red/node_modules/zigbee-herdsman/node_modules/@serialport/bindings/build/config.gypi', npm error gyp info spawn args '-I', npm error gyp info spawn args '/opt/iobroker/node_modules/node-gyp/addon.gypi', npm error gyp info spawn args '-I', npm error gyp info spawn args '/home/iobroker/.cache/node-gyp/20.19.3/include/node/common.gypi', npm error gyp info spawn args '-Dlibrary=shared_library', npm error gyp info spawn args '-Dvisibility=default', npm error gyp info spawn args '-Dnode_root_dir=/home/iobroker/.cache/node-gyp/20.19.3', npm error gyp info spawn args '-Dnode_gyp_dir=/opt/iobroker/node_modules/node-gyp', npm error gyp info spawn args '-Dnode_lib_file=/home/iobroker/.cache/node-gyp/20.19.3/<(target_arch)/node.lib', npm error gyp info spawn args '-Dmodule_root_dir=/opt/iobroker/iobroker-data/node-red/node_modules/zigbee-herdsman/node_modules/@serialport/bindings', npm error gyp info spawn args '-Dnode_engine=v8', npm error gyp info spawn args '--depth=.', npm error gyp info spawn args '--no-parallel', npm error gyp info spawn args '--generator-output', npm error gyp info spawn args 'build', npm error gyp info spawn args '-Goutput_dir=.' npm error gyp info spawn args ] npm error gyp info spawn make npm error gyp info spawn args [ 'BUILDTYPE=Release', '-C', 'build' ] npm error In file included from ../../../nan/nan.h:178, npm error from ../src/./serialport.h:13, npm error from ../src/serialport.cpp:1: npm error ../../../nan/nan_callbacks.h:55:23: error: ‘AccessorSignature’ is not a member of ‘v8’ npm error 55 | typedef v8::Local<v8::AccessorSignature> Sig; npm error | ^~~~~~~~~~~~~~~~~ npm error ../../../nan/nan_callbacks.h:55:40: error: template argument 1 is invalid npm error 55 | typedef v8::Local<v8::AccessorSignature> Sig; npm error | ^ npm error In file included from ../src/./serialport.h:13, npm error from ../src/serialport.cpp:1: 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)’: 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&)’ npm error 2551 | , signature); npm error | ^ npm error In file included from /home/iobroker/.cache/node-gyp/20.19.3/include/node/v8-function.h:15, npm error from /home/iobroker/.cache/node-gyp/20.19.3/include/node/v8.h:33, npm error from /home/iobroker/.cache/node-gyp/20.19.3/include/node/node.h:73, npm error from ../../../nan/nan.h:58, npm error from ../src/./serialport.h:13, npm error from ../src/serialport.cpp:1: 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)’ npm error 809 | void SetAccessor( npm error | ^~~~~~~~~~~ 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’ npm error 814 | SideEffectType getter_side_effect_type = SideEffectType::kHasSideEffect, npm error | ~~~~~~~~~~~~~~~^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 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)’ npm error 816 | void SetAccessor( npm error | ^~~~~~~~~~~ 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’ npm error 821 | SideEffectType getter_side_effect_type = SideEffectType::kHasSideEffect, npm error | ~~~~~~~~~~~~~~~^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ npm error ../src/serialport.cpp: In function ‘Nan::NAN_METHOD_RETURN_TYPE Open(Nan::NAN_METHOD_ARGS_TYPE)’: 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] npm error 78 | uv_queue_work(uv_default_loop(), req, EIO_Open, (uv_after_work_cb)EIO_AfterOpen); npm error | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ npm error ../src/serialport.cpp: In function ‘Nan::NAN_METHOD_RETURN_TYPE Update(Nan::NAN_METHOD_ARGS_TYPE)’: 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] npm error 135 | uv_queue_work(uv_default_loop(), req, EIO_Update, (uv_after_work_cb)EIO_AfterUpdate); npm error | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ npm error ../src/serialport.cpp: In function ‘Nan::NAN_METHOD_RETURN_TYPE Close(Nan::NAN_METHOD_ARGS_TYPE)’: 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] npm error 175 | uv_queue_work(uv_default_loop(), req, EIO_Close, (uv_after_work_cb)EIO_AfterClose); npm error | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ npm error ../src/serialport.cpp: In function ‘Nan::NAN_METHOD_RETURN_TYPE Flush(Nan::NAN_METHOD_ARGS_TYPE)’: 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] npm error 215 | uv_queue_work(uv_default_loop(), req, EIO_Flush, (uv_after_work_cb)EIO_AfterFlush); npm error | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ npm error ../src/serialport.cpp: In function ‘Nan::NAN_METHOD_RETURN_TYPE Set(Nan::NAN_METHOD_ARGS_TYPE)’: 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] npm error 271 | uv_queue_work(uv_default_loop(), req, EIO_Set, (uv_after_work_cb)EIO_AfterSet); npm error | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ npm error ../src/serialport.cpp: In function ‘Nan::NAN_METHOD_RETURN_TYPE Get(Nan::NAN_METHOD_ARGS_TYPE)’: 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] npm error 316 | uv_queue_work(uv_default_loop(), req, EIO_Get, (uv_after_work_cb)EIO_AfterGet); npm error | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ npm error ../src/serialport.cpp: In function ‘Nan::NAN_METHOD_RETURN_TYPE GetBaudRate(Nan::NAN_METHOD_ARGS_TYPE)’: 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] npm error 366 | uv_queue_work(uv_default_loop(), req, EIO_GetBaudRate, (uv_after_work_cb)EIO_AfterGetBaudRate); npm error | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ npm error ../src/serialport.cpp: In function ‘Nan::NAN_METHOD_RETURN_TYPE Drain(Nan::NAN_METHOD_ARGS_TYPE)’: 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] npm error 412 | uv_queue_work(uv_default_loop(), req, EIO_Drain, (uv_after_work_cb)EIO_AfterDrain); npm error | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ npm error ../src/serialport.cpp: At global scope: npm error ../src/serialport.cpp:433:28: warning: unnecessary parentheses in declaration of ‘ToParityEnum’ [-Wparentheses] npm error 433 | SerialPortParity NAN_INLINE(ToParityEnum(const v8::Local<v8::String>& v8str)) { npm error | ^ npm error ../src/serialport.cpp:452:30: warning: unnecessary parentheses in declaration of ‘ToStopBitEnum’ [-Wparentheses] npm error 452 | SerialPortStopBits NAN_INLINE(ToStopBitEnum(double stopBits)) { npm error | ^ npm error In file included from ../../../nan/nan.h:58, npm error from ../src/./serialport.h:13, npm error from ../src/serialport.cpp:1: 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] npm error 1227 | (node::addon_register_func) (regfunc), \ npm error | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ npm error /home/iobroker/.cache/node-gyp/20.19.3/include/node/node.h:1261:3: note: in expansion of macro ‘NODE_MODULE_X’ npm error 1261 | NODE_MODULE_X(modname, regfunc, NULL, 0) // NOLINT (readability/null_usage) npm error | ^~~~~~~~~~~~~ npm error ../src/serialport.cpp:486:1: note: in expansion of macro ‘NODE_MODULE’ npm error 486 | NODE_MODULE(serialport, init); npm error | ^~~~~~~~~~~ npm error make: *** [bindings.target.mk:109: Release/obj.target/bindings/src/serialport.o] Error 1 npm error gyp ERR! build error npm error gyp ERR! stack Error: `make` failed with exit code: 2 npm error gyp ERR! stack at ChildProcess.onExit (/opt/iobroker/node_modules/node-gyp/lib/build.js:194:23) npm error gyp ERR! stack at ChildProcess.emit (node:events:524:28) npm error gyp ERR! stack at ChildProcess._handle.onexit (node:internal/child_process:293:12) npm error gyp ERR! System Linux 6.1.21-v8+ npm error gyp ERR! command "/usr/bin/node" "/opt/iobroker/node_modules/.bin/node-gyp" "rebuild" npm error gyp ERR! cwd /opt/iobroker/iobroker-data/node-red/node_modules/zigbee-herdsman/node_modules/@serialport/bindings npm error gyp ERR! node -v v20.19.3 npm error gyp ERR! node-gyp -v v8.4.1 npm error gyp ERR! not ok npm error A complete log of this run can be found in: /home/iobroker/.npm/_logs/2025-06-25T18_50_27_905Z-debug-0.log 25 Jun 20:50:44 - [warn] ------------------------------------------
                          
                          node-red.0
                          2025-06-25 20:50:44.808	warn	Node-RED: 25 Jun 20:50:44 - [warn] ------------------------------------------
                          
                          node-red.0
                          2025-06-25 20:50:44.807	warn	Node-RED: 25 Jun 20:50:44 - [warn] Installation of module node-red-contrib-zigbee failed:
                          
                          
                          Thomas Braun 1 Reply Last reply Reply Quote 0
                          • arteck
                            arteck Developer Most Active @Autodidakt last edited by

                            @autodidakt

                            ELEVATED

                            bedeutet dass da irgend zu einem Gerät die Debug infos an sind

                            steht hier was - >

                            zigbee.0.info.debugmessages
                            
                            Autodidakt 1 Reply Last reply Reply Quote 0
                            • Thomas Braun
                              Thomas Braun Most Active @Autodidakt last edited by

                              @autodidakt sagte in Zigbee Adapter schmeißt warnungen:

                              Und was könnte denn da falsch gelaufen sein?

                              Könnte man evtl sehen, wenn du das direkte Log unter /opt/iobroker/logs
                              Posten würdest und nicht den GUI-Hantier.

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

                                @thomas-braun

                                2025-06-25 21:25:46.719  - warn: node-red.0 (25486) Node-RED: 25 Jun 21:25:46 - [warn] Installation of module node-red-contrib-zigbee failed:
                                2025-06-25 21:25:46.720  - warn: node-red.0 (25486) Node-RED: 25 Jun 21:25:46 - [warn] ------------------------------------------
                                25 Jun 21:25:46 - [warn] npm warn config production Use `--omit=dev` instead.
                                npm warn deprecated vis@4.21.0: Please consider using https://github.com/visjs
                                npm error code 1
                                npm error path /opt/iobroker/iobroker-data/node-red/node_modules/zigbee-herdsman/node_modules/@serialport/bindings
                                npm error command failed
                                npm error command sh -c node-gyp rebuild
                                npm error make: Entering directory '/opt/iobroker/iobroker-data/node-red/node_modules/zigbee-herdsman/node_modules/@serialport/bindings/build'
                                npm error   CXX(target) Release/obj.target/bindings/src/serialport.o
                                npm error make: Leaving directory '/opt/iobroker/iobroker-data/node-red/node_modules/zigbee-herdsman/node_modules/@serialport/bindings/build'
                                npm error gyp info it worked if it ends with ok
                                npm error gyp info using node-gyp@8.4.1
                                npm error gyp info using node@20.19.3 | linux | arm64
                                npm error gyp info find Python using Python version 3.9.2 found at "/usr/bin/python3"
                                npm error gyp info spawn /usr/bin/python3
                                npm error gyp info spawn args [
                                npm error gyp info spawn args   '/opt/iobroker/node_modules/node-gyp/gyp/gyp_main.py',
                                npm error gyp info spawn args   'binding.gyp',
                                npm error gyp info spawn args   '-f',
                                npm error gyp info spawn args   'make',
                                npm error gyp info spawn args   '-I',
                                npm error gyp info spawn args   '/opt/iobroker/iobroker-data/node-red/node_modules/zigbee-herdsman/node_modules/@serialport/bindings/build/config.gypi',
                                npm error gyp info spawn args   '-I',
                                npm error gyp info spawn args   '/opt/iobroker/node_modules/node-gyp/addon.gypi',
                                npm error gyp info spawn args   '-I',
                                npm error gyp info spawn args   '/home/iobroker/.cache/node-gyp/20.19.3/include/node/common.gypi',
                                npm error gyp info spawn args   '-Dlibrary=shared_library',
                                npm error gyp info spawn args   '-Dvisibility=default',
                                npm error gyp info spawn args   '-Dnode_root_dir=/home/iobroker/.cache/node-gyp/20.19.3',
                                npm error gyp info spawn args   '-Dnode_gyp_dir=/opt/iobroker/node_modules/node-gyp',
                                npm error gyp info spawn args   '-Dnode_lib_file=/home/iobroker/.cache/node-gyp/20.19.3/<(target_arch)/node.lib',
                                npm error gyp info spawn args   '-Dmodule_root_dir=/opt/iobroker/iobroker-data/node-red/node_modules/zigbee-herdsman/node_modules/@serialport/bindings',
                                npm error gyp info spawn args   '-Dnode_engine=v8',
                                npm error gyp info spawn args   '--depth=.',
                                npm error gyp info spawn args   '--no-parallel',
                                npm error gyp info spawn args   '--generator-output',
                                npm error gyp info spawn args   'build',
                                npm error gyp info spawn args   '-Goutput_dir=.'
                                npm error gyp info spawn args ]
                                npm error gyp info spawn make
                                npm error gyp info spawn args [ 'BUILDTYPE=Release', '-C', 'build' ]
                                npm error In file included from ../../../nan/nan.h:178,
                                npm error                  from ../src/./serialport.h:13,
                                npm error                  from ../src/serialport.cpp:1:
                                npm error ../../../nan/nan_callbacks.h:55:23: error: ‘AccessorSignature’ is not a member of ‘v8’
                                npm error    55 | typedef v8::Local<v8::AccessorSignature> Sig;
                                npm error       |                       ^~~~~~~~~~~~~~~~~
                                npm error ../../../nan/nan_callbacks.h:55:40: error: template argument 1 is invalid
                                npm error    55 | typedef v8::Local<v8::AccessorSignature> Sig;
                                npm error       |                                        ^
                                npm error In file included from ../src/./serialport.h:13,
                                npm error                  from ../src/serialport.cpp:1:
                                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)’:
                                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&)’
                                npm error  2551 |     , signature);
                                npm error       |                ^
                                npm error In file included from /home/iobroker/.cache/node-gyp/20.19.3/include/node/v8-function.h:15,
                                npm error                  from /home/iobroker/.cache/node-gyp/20.19.3/include/node/v8.h:33,
                                npm error                  from /home/iobroker/.cache/node-gyp/20.19.3/include/node/node.h:73,
                                npm error                  from ../../../nan/nan.h:58,
                                npm error                  from ../src/./serialport.h:13,
                                npm error                  from ../src/serialport.cpp:1:
                                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)’
                                npm error   809 |   void SetAccessor(
                                npm error       |        ^~~~~~~~~~~
                                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’
                                npm error   814 |       SideEffectType getter_side_effect_type = SideEffectType::kHasSideEffect,
                                npm error       |       ~~~~~~~~~~~~~~~^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
                                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)’
                                npm error   816 |   void SetAccessor(
                                npm error       |        ^~~~~~~~~~~
                                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’
                                npm error   821 |       SideEffectType getter_side_effect_type = SideEffectType::kHasSideEffect,
                                npm error       |       ~~~~~~~~~~~~~~~^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
                                npm error ../src/serialport.cpp: In function ‘Nan::NAN_METHOD_RETURN_TYPE Open(Nan::NAN_METHOD_ARGS_TYPE)’:
                                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]
                                npm error    78 |   uv_queue_work(uv_default_loop(), req, EIO_Open, (uv_after_work_cb)EIO_AfterOpen);
                                npm error       |                                                   ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
                                npm error ../src/serialport.cpp: In function ‘Nan::NAN_METHOD_RETURN_TYPE Update(Nan::NAN_METHOD_ARGS_TYPE)’:
                                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]
                                npm error   135 |   uv_queue_work(uv_default_loop(), req, EIO_Update, (uv_after_work_cb)EIO_AfterUpdate);
                                npm error       |                                                     ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
                                npm error ../src/serialport.cpp: In function ‘Nan::NAN_METHOD_RETURN_TYPE Close(Nan::NAN_METHOD_ARGS_TYPE)’:
                                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]
                                npm error   175 |   uv_queue_work(uv_default_loop(), req, EIO_Close, (uv_after_work_cb)EIO_AfterClose);
                                npm error       |                                                    ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
                                npm error ../src/serialport.cpp: In function ‘Nan::NAN_METHOD_RETURN_TYPE Flush(Nan::NAN_METHOD_ARGS_TYPE)’:
                                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]
                                npm error   215 |   uv_queue_work(uv_default_loop(), req, EIO_Flush, (uv_after_work_cb)EIO_AfterFlush);
                                npm error       |                                                    ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
                                npm error ../src/serialport.cpp: In function ‘Nan::NAN_METHOD_RETURN_TYPE Set(Nan::NAN_METHOD_ARGS_TYPE)’:
                                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]
                                npm error   271 |   uv_queue_work(uv_default_loop(), req, EIO_Set, (uv_after_work_cb)EIO_AfterSet);
                                npm error       |                                                  ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
                                npm error ../src/serialport.cpp: In function ‘Nan::NAN_METHOD_RETURN_TYPE Get(Nan::NAN_METHOD_ARGS_TYPE)’:
                                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]
                                npm error   316 |   uv_queue_work(uv_default_loop(), req, EIO_Get, (uv_after_work_cb)EIO_AfterGet);
                                npm error       |                                                  ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
                                npm error ../src/serialport.cpp: In function ‘Nan::NAN_METHOD_RETURN_TYPE GetBaudRate(Nan::NAN_METHOD_ARGS_TYPE)’:
                                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]
                                npm error   366 |   uv_queue_work(uv_default_loop(), req, EIO_GetBaudRate, (uv_after_work_cb)EIO_AfterGetBaudRate);
                                npm error       |                                                          ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
                                npm error ../src/serialport.cpp: In function ‘Nan::NAN_METHOD_RETURN_TYPE Drain(Nan::NAN_METHOD_ARGS_TYPE)’:
                                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]
                                npm error   412 |   uv_queue_work(uv_default_loop(), req, EIO_Drain, (uv_after_work_cb)EIO_AfterDrain);
                                npm error       |                                                    ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
                                npm error ../src/serialport.cpp: At global scope:
                                npm error ../src/serialport.cpp:433:28: warning: unnecessary parentheses in declaration of ‘ToParityEnum’ [-Wparentheses]
                                npm error   433 | SerialPortParity NAN_INLINE(ToParityEnum(const v8::Local<v8::String>& v8str)) {
                                npm error       |                            ^
                                npm error ../src/serialport.cpp:452:30: warning: unnecessary parentheses in declaration of ‘ToStopBitEnum’ [-Wparentheses]
                                npm error   452 | SerialPortStopBits NAN_INLINE(ToStopBitEnum(double stopBits)) {
                                npm error       |                              ^
                                npm error In file included from ../../../nan/nan.h:58,
                                npm error                  from ../src/./serialport.h:13,
                                npm error                  from ../src/serialport.cpp:1:
                                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]
                                npm error  1227 |       (node::addon_register_func) (regfunc),                          \
                                npm error       |       ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
                                npm error /home/iobroker/.cache/node-gyp/20.19.3/include/node/node.h:1261:3: note: in expansion of macro ‘NODE_MODULE_X’
                                npm error  1261 |   NODE_MODULE_X(modname, regfunc, NULL, 0)  // NOLINT (readability/null_usage)
                                npm error       |   ^~~~~~~~~~~~~
                                npm error ../src/serialport.cpp:486:1: note: in expansion of macro ‘NODE_MODULE’
                                npm error   486 | NODE_MODULE(serialport, init);
                                npm error       | ^~~~~~~~~~~
                                npm error make: *** [bindings.target.mk:109: Release/obj.target/bindings/src/serialport.o] Error 1
                                npm error gyp ERR! build error 
                                npm error gyp ERR! stack Error: `make` failed with exit code: 2
                                npm error gyp ERR! stack     at ChildProcess.onExit (/opt/iobroker/node_modules/node-gyp/lib/build.js:194:23)
                                npm error gyp ERR! stack     at ChildProcess.emit (node:events:524:28)
                                npm error gyp ERR! stack     at ChildProcess._handle.onexit (node:internal/child_process:293:12)
                                npm error gyp ERR! System Linux 6.1.21-v8+
                                npm error gyp ERR! command "/usr/bin/node" "/opt/iobroker/node_modules/.bin/node-gyp" "rebuild"
                                npm error gyp ERR! cwd /opt/iobroker/iobroker-data/node-red/node_modules/zigbee-herdsman/node_modules/@serialport/bindings
                                npm error gyp ERR! node -v v20.19.3
                                npm error gyp ERR! node-gyp -v v8.4.1
                                npm error gyp ERR! not ok
                                npm error A complete log of this run can be found in: /home/iobroker/.npm/_logs/2025-06-25T19_25_26_960Z-debug-0.log
                                
                                
                                pi@pi4-Master:~ $ tail /home/iobroker/.npm/_logs/2025-06-25T19_25_26_960Z-debug-0.log
                                1028 silly unfinished npm timer build:deps 1750879540508
                                1029 silly unfinished npm timer build:run:install 1750879540638
                                1030 silly unfinished npm timer build:run:install:node_modules/zigbee-herdsman/node_modules/@serialport/bindings 1750879540657
                                1031 verbose cwd /opt/iobroker/iobroker-data/node-red
                                1032 verbose os Linux 6.1.21-v8+
                                1033 verbose node v20.19.3
                                1034 verbose npm  v10.8.2
                                1035 verbose exit 1
                                1036 verbose code 1
                                1037 error A complete log of this run can be found in: /home/iobroker/.npm/_logs/2025-06-25T19_25_26_960Z-debug-0.log
                                pi@pi4-Master:~ $
                                
                                
                                1 Reply Last reply Reply Quote 0
                                • Autodidakt
                                  Autodidakt @arteck last edited by

                                  @arteck sagte in Zigbee Adapter schmeißt warnungen:

                                  @autodidakt

                                  ELEVATED

                                  bedeutet dass da irgend zu einem Gerät die Debug infos an sind

                                  steht hier was - >

                                  zigbee.0.info.debugmessages
                                  

                                  Nein, logstufe ist auf Info

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

                                    @autodidakt es geht nicht um die logstufe sondern um den eintrag da drin.. aber da wird ehh nix mehr drin stehen..

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

                                      @arteck Ich kann Dir nicht folgen...

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

                                        Ich habe ein ähnliches Problem, allerdings steht bei mir nirgends was von Debug und der Käfer ist auch weiß.

                                        e5a4c0a4-a213-42be-8b59-52eef37cfbbe-image.png

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

                                          @brokerti said in Zigbee Adapter schmeißt warnungen:

                                          Ich habe ein ähnliches Problem, allerdings steht bei mir nirgends was von Debug und der Käfer ist auch weiß.

                                          Bist Du sicher, dass Du die richtige Kachel angeschaut hast? Vielleicht sind bei Dir auch die Farben anders, wenn Du mit der Maus über dem Käfer "hoverst", was sagt der Tooltip? Er sollte "Enable Debug" anzeigen, wenn Debug ausgeschaltet ist (klingt komisch, ist aber so).

                                          gfs. danach den Adapter neu starten, dabei auf Meldungen im Log schauen:

                                          2025-06-25 20:14:15.705 info debug devices set to ["xxxxxxxx"]

                                          Mit grünem Käfer wird in den eckigen Klammern eine Liste der Debug-Geräte angezeigt. Ohne Debug-Geräte sollte dort [] stehen.

                                          B 1 Reply Last reply Reply Quote 0
                                          • 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
                                            • First post
                                              Last post

                                            Support us

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

                                            871
                                            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