Skip to content
  • Home
  • Aktuell
  • Tags
  • 0 Ungelesen 0
  • Kategorien
  • Unreplied
  • Beliebt
  • GitHub
  • Docu
  • Hilfe
Skins
  • Light
  • Brite
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor
  • Standard: (Kein Skin)
  • Kein Skin
Einklappen
ioBroker Logo

Community Forum
donate donate
  1. ioBroker Community Home
  2. Deutsch
  3. ioBroker Allgemein
  4. Zigbee Adapter schmeißt warnungen

NEWS

  • UPDATE 31.10.: Amazon Alexa - ioBroker Skill läuft aus ?
    apollon77A
    apollon77
    48
    3
    8.8k
  • Monatsrückblick – September 2025
    BluefoxB
    Bluefox
    13
    1
    2.2k
  • Neues Video "KI im Smart Home" - ioBroker plus n8n
    BluefoxB
    Bluefox
    16
    1
    3.2k

Zigbee Adapter schmeißt warnungen

Geplant Angeheftet Gesperrt Verschoben ioBroker Allgemein
32 Beiträge 7 Kommentatoren 2.2k Aufrufe 5 Watching
  • Älteste zuerst
  • Neuste zuerst
  • Meiste Stimmen
Antworten
  • In einem neuen Thema antworten
Anmelden zum Antworten
Dieses Thema wurde gelöscht. Nur Nutzer mit entsprechenden Rechten können es sehen.
  • AutodidaktA 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 BraunT Online
    Thomas BraunT Online
    Thomas Braun
    Most Active
    schrieb am zuletzt editiert von
    #6

    @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

    Linux-Werkzeugkasten:
    https://forum.iobroker.net/topic/42952/der-kleine-iobroker-linux-werkzeugkasten
    NodeJS Fixer Skript:
    https://forum.iobroker.net/topic/68035/iob-node-fix-skript
    iob_diag: curl -sLf -o diag.sh https://iobroker.net/diag.sh && bash diag.sh

    AutodidaktA 1 Antwort Letzte Antwort
    0
    • Thomas BraunT Thomas Braun

      @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

      AutodidaktA Offline
      AutodidaktA Offline
      Autodidakt
      schrieb am zuletzt editiert von
      #7

      @thomas-braun Merci, schau ich mir an.

      1 Antwort Letzte Antwort
      0
      • AutodidaktA 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 BraunT Online
        Thomas BraunT Online
        Thomas Braun
        Most Active
        schrieb am zuletzt editiert von
        #8

        @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.

        Linux-Werkzeugkasten:
        https://forum.iobroker.net/topic/42952/der-kleine-iobroker-linux-werkzeugkasten
        NodeJS Fixer Skript:
        https://forum.iobroker.net/topic/68035/iob-node-fix-skript
        iob_diag: curl -sLf -o diag.sh https://iobroker.net/diag.sh && bash diag.sh

        AutodidaktA 1 Antwort Letzte Antwort
        0
        • Thomas BraunT Thomas Braun

          @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.

          AutodidaktA Offline
          AutodidaktA Offline
          Autodidakt
          schrieb am zuletzt editiert von
          #9

          @thomas-braun Auch nicht schlecht, die Idee... :blush:

          Thomas BraunT 1 Antwort Letzte Antwort
          0
          • AutodidaktA Autodidakt

            @thomas-braun Auch nicht schlecht, die Idee... :blush:

            Thomas BraunT Online
            Thomas BraunT Online
            Thomas Braun
            Most Active
            schrieb am zuletzt editiert von
            #10

            @autodidakt

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

            Linux-Werkzeugkasten:
            https://forum.iobroker.net/topic/42952/der-kleine-iobroker-linux-werkzeugkasten
            NodeJS Fixer Skript:
            https://forum.iobroker.net/topic/68035/iob-node-fix-skript
            iob_diag: curl -sLf -o diag.sh https://iobroker.net/diag.sh && bash diag.sh

            AutodidaktA 1 Antwort Letzte Antwort
            0
            • Thomas BraunT Thomas Braun

              @autodidakt

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

              AutodidaktA Offline
              AutodidaktA Offline
              Autodidakt
              schrieb am zuletzt editiert von
              #11

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

              1 Antwort Letzte Antwort
              0
              • AutodidaktA Offline
                AutodidaktA Offline
                Autodidakt
                schrieb am zuletzt editiert von
                #12

                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 BraunT 1 Antwort Letzte Antwort
                0
                • AutodidaktA Autodidakt

                  Hallo und guten Abend.

                  Mein Zigbee Adapter V 2.0.5 Gibt bei jedem Start Warnungen aus.

                  
zigbee.0
2025-06-25 20:16:20.380	warn	ELEVATED:I02 (1a87) value generated '100' from device ffffb40e060599a0 for 'Battery percent'

zigbee.0
2025-06-25 20:16:20.379	warn	ELEVATED:I01 (1a87) message received '{"battery":100}' from device ffffb40e060599a0 type '3RSM0147Z'

zigbee.0
2025-06-25 20:16:20.378	warn	ELEVATED:I02 (1a87) value generated '225' from device ffffb40e060599a0 for 'Link quality'

zigbee.0
2025-06-25 20:16:20.377	warn	ELEVATED:I01 (1a87) message received '{"linkquality":225}' from device ffffb40e060599a0 type '3RSM0147Z'

zigbee.0
2025-06-25 20:16:20.373	warn	ELEVATED:NOVAL (1a83) No value published for device ffffb40e060599a0

zigbee.0
2025-06-25 20:16:20.373	warn	ELEVATED:I01 (1a83) message received '{}' from device ffffb40e060599a0 type '3RSM0147Z'

zigbee.0
2025-06-25 20:16:20.371	warn	ELEVATED:I02 (1a83) value generated '225' from device ffffb40e060599a0 for 'Link quality'

zigbee.0
2025-06-25 20:16:20.371	warn	ELEVATED:I01 (1a83) message received '{"linkquality":225}' from device ffffb40e060599a0 type '3RSM0147Z'

zigbee.0
2025-06-25 20:16:20.367	warn	ELEVATED:I02 (1a7b) value generated '0' from device ffffb40e060599a0 for 'Humidity'

zigbee.0
2025-06-25 20:16:20.367	warn	ELEVATED:I01 (1a7b) message received '{"humidity":0}' from device ffffb40e060599a0 type '3RSM0147Z'

zigbee.0
2025-06-25 20:16:20.366	warn	ELEVATED:I02 (1a7b) value generated '225' from device ffffb40e060599a0 for 'Link quality'

zigbee.0
2025-06-25 20:16:20.366	warn	ELEVATED:I01 (1a7b) message received '{"linkquality":225}' from device ffffb40e060599a0 type '3RSM0147Z'

zigbee.0
2025-06-25 20:16:20.365	warn	ELEVATED:I02 (1a79) value generated '30.81' from device ffffb40e060599a0 for 'Temperature'

zigbee.0
2025-06-25 20:16:20.365	warn	ELEVATED:I01 (1a79) message received '{"temperature":30.81}' from device ffffb40e060599a0 type '3RSM0147Z'

zigbee.0
2025-06-25 20:16:20.363	warn	ELEVATED:I02 (1a79) value generated '225' from device ffffb40e060599a0 for 'Link quality'

zigbee.0
2025-06-25 20:16:20.362	warn	ELEVATED:I01 (1a79) message received '{"linkquality":225}' from device ffffb40e060599a0 type '3RSM0147Z'

zigbee.0
2025-06-25 20:16:20.359	warn	ELEVATED:I01 (1a87) Zigbee Event of Type attributeReport from device 0xffffb40e060599a0, incoming event: {"type":"attributeReport","data":{"batteryPercentageRemaining":200},"linkquality":225,"groupID":0,"cluster":"genPowerCfg","meta":{"zclTransactionSequenceNumber":211,"frameControl":{"frameType":0,"manufacturerSpecific":false,"direction":1,"disableDefaultResponse":true,"reservedBits":0}},"endpoint_id":1}

zigbee.0
2025-06-25 20:16:20.356	warn	ELEVATED:I01 (1a83) Zigbee Event of Type attributeReport from device 0xffffb40e060599a0, incoming event: {"type":"attributeReport","data":{"batteryVoltage":16},"linkquality":225,"groupID":0,"cluster":"genPowerCfg","meta":{"zclTransactionSequenceNumber":210,"frameControl":{"frameType":0,"manufacturerSpecific":false,"direction":1,"disableDefaultResponse":true,"reservedBits":0}},"endpoint_id":1}

zigbee.0
2025-06-25 20:16:20.347	warn	ELEVATED:I01 (1a7b) Zigbee Event of Type attributeReport from device 0xffffb40e060599a0, incoming event: {"type":"attributeReport","data":{"measuredValue":0},"linkquality":225,"groupID":0,"cluster":"msRelativeHumidity","meta":{"zclTransactionSequenceNumber":209,"frameControl":{"frameType":0,"manufacturerSpecific":false,"direction":1,"disableDefaultResponse":true,"reservedBits":0}},"endpoint_id":1}

zigbee.0
2025-06-25 20:16:20.345	warn	ELEVATED:I01 (1a79) Zigbee Event of Type attributeReport from device 0xffffb40e060599a0, incoming event: {"type":"attributeReport","data":{"measuredValue":3081},"linkquality":225,"groupID":0,"cluster":"msTemperatureMeasurement","meta":{"zclTransactionSequenceNumber":208,"frameControl":{"frameType":0,"manufacturerSpecific":false,"direction":1,"disableDefaultResponse":true,"reservedBits":0}},"endpoint_id":1}

zigbee.0
2025-06-25 20:16:05.388	warn	ELEVATED:I02 (dfee) value generated '100' from device ffffb40e060599a0 for 'Battery percent'

zigbee.0
2025-06-25 20:16:05.387	warn	ELEVATED:I01 (dfee) message received '{"battery":100}' from device ffffb40e060599a0 type '3RSM0147Z'

zigbee.0
2025-06-25 20:16:05.385	warn	ELEVATED:I02 (dfee) value generated '225' from device ffffb40e060599a0 for 'Link quality'

zigbee.0
2025-06-25 20:16:05.385	warn	ELEVATED:I01 (dfee) message received '{"linkquality":225}' from device ffffb40e060599a0 type '3RSM0147Z'

zigbee.0
2025-06-25 20:16:05.380	warn	ELEVATED:NOVAL (dfed) No value published for device ffffb40e060599a0

zigbee.0
2025-06-25 20:16:05.380	warn	ELEVATED:I01 (dfed) message received '{}' from device ffffb40e060599a0 type '3RSM0147Z'

zigbee.0
2025-06-25 20:16:05.378	warn	ELEVATED:I02 (dfed) value generated '225' from device ffffb40e060599a0 for 'Link quality'

zigbee.0
2025-06-25 20:16:05.377	warn	ELEVATED:I01 (dfed) message received '{"linkquality":225}' from device ffffb40e060599a0 type '3RSM0147Z'

zigbee.0
2025-06-25 20:16:05.369	warn	ELEVATED:I02 (dfe1) value generated '0' from device ffffb40e060599a0 for 'Humidity'

zigbee.0
2025-06-25 20:16:05.369	warn	ELEVATED:I01 (dfe1) message received '{"humidity":0}' from device ffffb40e060599a0 type '3RSM0147Z'

zigbee.0
2025-06-25 20:16:05.368	warn	ELEVATED:I02 (dfe1) value generated '225' from device ffffb40e060599a0 for 'Link quality'

zigbee.0
2025-06-25 20:16:05.367	warn	ELEVATED:I01 (dfe1) message received '{"linkquality":225}' from device ffffb40e060599a0 type '3RSM0147Z'

zigbee.0
2025-06-25 20:16:05.366	warn	ELEVATED:I02 (dfdd) value generated '30.81' from device ffffb40e060599a0 for 'Temperature'

zigbee.0
2025-06-25 20:16:05.366	warn	ELEVATED:I01 (dfdd) message received '{"temperature":30.81}' from device ffffb40e060599a0 type '3RSM0147Z'

zigbee.0
2025-06-25 20:16:05.365	warn	ELEVATED:I02 (dfdd) value generated '225' from device ffffb40e060599a0 for 'Link quality'

zigbee.0
2025-06-25 20:16:05.364	warn	ELEVATED:I01 (dfdd) message received '{"linkquality":225}' from device ffffb40e060599a0 type '3RSM0147Z'

zigbee.0
2025-06-25 20:16:05.358	warn	ELEVATED:I01 (dfee) Zigbee Event of Type attributeReport from device 0xffffb40e060599a0, incoming event: {"type":"attributeReport","data":{"batteryPercentageRemaining":200},"linkquality":225,"groupID":0,"cluster":"genPowerCfg","meta":{"zclTransactionSequenceNumber":207,"frameControl":{"frameType":0,"manufacturerSpecific":false,"direction":1,"disableDefaultResponse":true,"reservedBits":0}},"endpoint_id":1}

zigbee.0
2025-06-25 20:16:05.357	warn	ELEVATED:I01 (dfed) Zigbee Event of Type attributeReport from device 0xffffb40e060599a0, incoming event: {"type":"attributeReport","data":{"batteryVoltage":16},"linkquality":225,"groupID":0,"cluster":"genPowerCfg","meta":{"zclTransactionSequenceNumber":206,"frameControl":{"frameType":0,"manufacturerSpecific":false,"direction":1,"disableDefaultResponse":true,"reservedBits":0}},"endpoint_id":1}

zigbee.0
2025-06-25 20:16:05.345	warn	ELEVATED:I01 (dfe1) Zigbee Event of Type attributeReport from device 0xffffb40e060599a0, incoming event: {"type":"attributeReport","data":{"measuredValue":0},"linkquality":225,"groupID":0,"cluster":"msRelativeHumidity","meta":{"zclTransactionSequenceNumber":205,"frameControl":{"frameType":0,"manufacturerSpecific":false,"direction":1,"disableDefaultResponse":true,"reservedBits":0}},"endpoint_id":1}

zigbee.0
2025-06-25 20:16:05.341	warn	ELEVATED:I01 (dfdd) Zigbee Event of Type attributeReport from device 0xffffb40e060599a0, incoming event: {"type":"attributeReport","data":{"measuredValue":3081},"linkquality":225,"groupID":0,"cluster":"msTemperatureMeasurement","meta":{"zclTransactionSequenceNumber":204,"frameControl":{"frameType":0,"manufacturerSpecific":false,"direction":1,"disableDefaultResponse":true,"reservedBits":0}},"endpoint_id":1}

zigbee.0
2025-06-25 20:16:05.293	warn	ELEVATED:I02 (df38) value generated '0' from device ffffb40e060599a0 for 'Humidity'

zigbee.0
2025-06-25 20:16:05.292	warn	ELEVATED:I01 (df38) message received '{"humidity":0}' from device ffffb40e060599a0 type '3RSM0147Z'

zigbee.0
2025-06-25 20:16:05.290	warn	ELEVATED:I02 (df38) value generated '225' from device ffffb40e060599a0 for 'Link quality'

zigbee.0
2025-06-25 20:16:05.290	warn	ELEVATED:I01 (df38) message received '{"linkquality":225}' from device ffffb40e060599a0 type '3RSM0147Z'

zigbee.0
2025-06-25 20:16:05.289	warn	ELEVATED:I02 (df2e) value generated '30.81' from device ffffb40e060599a0 for 'Temperature'

zigbee.0
2025-06-25 20:16:05.288	warn	ELEVATED:I01 (df2e) message received '{"temperature":30.81}' from device ffffb40e060599a0 type '3RSM0147Z'

zigbee.0
2025-06-25 20:16:05.286	warn	ELEVATED:I02 (df2e) value generated '229' from device ffffb40e060599a0 for 'Link quality'

zigbee.0
2025-06-25 20:16:05.286	warn	ELEVATED:I01 (df2e) message received '{"linkquality":229}' from device ffffb40e060599a0 type '3RSM0147Z'

zigbee.0
2025-06-25 20:16:05.176	warn	ELEVATED:I01 (df38) Zigbee Event of Type attributeReport from device 0xffffb40e060599a0, incoming event: {"type":"attributeReport","data":{"measuredValue":0},"linkquality":225,"groupID":0,"cluster":"msRelativeHumidity","meta":{"zclTransactionSequenceNumber":203,"frameControl":{"frameType":0,"manufacturerSpecific":false,"direction":1,"disableDefaultResponse":true,"reservedBits":0}},"endpoint_id":1}

zigbee.0
2025-06-25 20:16:05.166	warn	ELEVATED:I01 (df2e) Zigbee Event of Type attributeReport from device 0xffffb40e060599a0, incoming event: {"type":"attributeReport","data":{"measuredValue":3081},"linkquality":229,"groupID":0,"cluster":"msTemperatureMeasurement","meta":{"zclTransactionSequenceNumber":202,"frameControl":{"frameType":0,"manufacturerSpecific":false,"direction":1,"disableDefaultResponse":true,"reservedBits":0}},"endpoint_id":1}

zigbee.0
2025-06-25 20:15:50.311	warn	ELEVATED:I02 (a50e) value generated '100' from device ffffb40e060599a0 for 'Battery percent'

zigbee.0
2025-06-25 20:15:50.311	warn	ELEVATED:I01 (a50e) message received '{"battery":100}' from device ffffb40e060599a0 type '3RSM0147Z'

zigbee.0
2025-06-25 20:15:50.309	warn	ELEVATED:I02 (a50e) value generated '225' from device ffffb40e060599a0 for 'Link quality'

zigbee.0
2025-06-25 20:15:50.308	warn	ELEVATED:I01 (a50e) message received '{"linkquality":225}' from device ffffb40e060599a0 type '3RSM0147Z'

zigbee.0
2025-06-25 20:15:50.305	warn	ELEVATED:NOVAL (a50b) No value published for device ffffb40e060599a0

zigbee.0
2025-06-25 20:15:50.305	warn	ELEVATED:I01 (a50b) message received '{}' from device ffffb40e060599a0 type '3RSM0147Z'

zigbee.0
2025-06-25 20:15:50.303	warn	ELEVATED:I02 (a50b) value generated '225' from device ffffb40e060599a0 for 'Link quality'

zigbee.0
2025-06-25 20:15:50.302	warn	ELEVATED:I01 (a50b) message received '{"linkquality":225}' from device ffffb40e060599a0 type '3RSM0147Z'

zigbee.0
2025-06-25 20:15:50.299	warn	ELEVATED:I02 (a4f7) value generated '0' from device ffffb40e060599a0 for 'Humidity'

zigbee.0
2025-06-25 20:15:50.298	warn	ELEVATED:I01 (a4f7) message received '{"humidity":0}' from device ffffb40e060599a0 type '3RSM0147Z'

zigbee.0
2025-06-25 20:15:50.297	warn	ELEVATED:I02 (a4f7) value generated '225' from device ffffb40e060599a0 for 'Link quality'

zigbee.0
2025-06-25 20:15:50.296	warn	ELEVATED:I01 (a4f7) message received '{"linkquality":225}' from device ffffb40e060599a0 type '3RSM0147Z'

zigbee.0
2025-06-25 20:15:50.295	warn	ELEVATED:I02 (a4f1) value generated '30.81' from device ffffb40e060599a0 for 'Temperature'

zigbee.0
2025-06-25 20:15:50.295	warn	ELEVATED:I01 (a4f1) message received '{"temperature":30.81}' from device ffffb40e060599a0 type '3RSM0147Z'

zigbee.0
2025-06-25 20:15:50.292	warn	ELEVATED:I02 (a4f1) value generated '225' from device ffffb40e060599a0 for 'Link quality'

zigbee.0
2025-06-25 20:15:50.292	warn	ELEVATED:I01 (a4f1) message received '{"linkquality":225}' from device ffffb40e060599a0 type '3RSM0147Z'

zigbee.0
2025-06-25 20:15:50.287	warn	ELEVATED:I01 (a50e) Zigbee Event of Type attributeReport from device 0xffffb40e060599a0, incoming event: {"type":"attributeReport","data":{"batteryPercentageRemaining":200},"linkquality":225,"groupID":0,"cluster":"genPowerCfg","meta":{"zclTransactionSequenceNumber":201,"frameControl":{"frameType":0,"manufacturerSpecific":false,"direction":1,"disableDefaultResponse":true,"reservedBits":0}},"endpoint_id":1}

zigbee.0
2025-06-25 20:15:50.283	warn	ELEVATED:I01 (a50b) Zigbee Event of Type attributeReport from device 0xffffb40e060599a0, incoming event: {"type":"attributeReport","data":{"batteryVoltage":16},"linkquality":225,"groupID":0,"cluster":"genPowerCfg","meta":{"zclTransactionSequenceNumber":200,"frameControl":{"frameType":0,"manufacturerSpecific":false,"direction":1,"disableDefaultResponse":true,"reservedBits":0}},"endpoint_id":1}

zigbee.0
2025-06-25 20:15:50.263	warn	ELEVATED:I01 (a4f7) Zigbee Event of Type attributeReport from device 0xffffb40e060599a0, incoming event: {"type":"attributeReport","data":{"measuredValue":0},"linkquality":225,"groupID":0,"cluster":"msRelativeHumidity","meta":{"zclTransactionSequenceNumber":199,"frameControl":{"frameType":0,"manufacturerSpecific":false,"direction":1,"disableDefaultResponse":true,"reservedBits":0}},"endpoint_id":1}

zigbee.0
2025-06-25 20:15:50.258	warn	ELEVATED:I01 (a4f1) Zigbee Event of Type attributeReport from device 0xffffb40e060599a0, incoming event: {"type":"attributeReport","data":{"measuredValue":3081},"linkquality":225,"groupID":0,"cluster":"msTemperatureMeasurement","meta":{"zclTransactionSequenceNumber":198,"frameControl":{"frameType":0,"manufacturerSpecific":false,"direction":1,"disableDefaultResponse":true,"reservedBits":0}},"endpoint_id":1}

zigbee.0
2025-06-25 20:15:39.159	warn	ELEVATED:I02 (7990) value generated '225' from device ffffb40e060599a0 for 'Link quality'

zigbee.0
2025-06-25 20:15:39.159	warn	ELEVATED:I01 (7990) message received '{"linkquality":225}' from device ffffb40e060599a0 type '3RSM0147Z'

zigbee.0
2025-06-25 20:15:39.158	warn	ELEVATED:NOCONV (7990) No converter available for '3RSM0147Z' 'ffffb40e060599a0' with cluster 'genBasic' and type 'attributeReport'

zigbee.0
2025-06-25 20:15:39.152	warn	ELEVATED:I01 (7990) Zigbee Event of Type attributeReport from device 0xffffb40e060599a0, incoming event: {"type":"attributeReport","data":{"swBuildId":"v1.00.38"},"linkquality":225,"groupID":0,"cluster":"genBasic","meta":{"zclTransactionSequenceNumber":197,"frameControl":{"frameType":0,"manufacturerSpecific":false,"direction":1,"disableDefaultResponse":false,"reservedBits":0}},"endpoint_id":1}

zigbee.0
2025-06-25 20:15:37.184	warn	ELEVATED:I02 (71c5) value generated '100' from device ffffb40e060599a0 for 'Battery percent'

zigbee.0
2025-06-25 20:15:37.183	warn	ELEVATED:I01 (71c5) message received '{"battery":100}' from device ffffb40e060599a0 type '3RSM0147Z'

zigbee.0
2025-06-25 20:15:37.179	warn	ELEVATED:I02 (71c5) value generated '225' from device ffffb40e060599a0 for 'Link quality'

zigbee.0
2025-06-25 20:15:37.178	warn	ELEVATED:I01 (71c5) message received '{"linkquality":225}' from device ffffb40e060599a0 type '3RSM0147Z'

zigbee.0
2025-06-25 20:15:37.172	warn	ELEVATED:NOVAL (71c0) No value published for device ffffb40e060599a0

zigbee.0
2025-06-25 20:15:37.171	warn	ELEVATED:I01 (71c0) message received '{}' from device ffffb40e060599a0 type '3RSM0147Z'

zigbee.0
2025-06-25 20:15:37.168	warn	ELEVATED:I02 (71c0) value generated '225' from device ffffb40e060599a0 for 'Link quality'

zigbee.0
2025-06-25 20:15:37.167	warn	ELEVATED:I01 (71c0) message received '{"linkquality":225}' from device ffffb40e060599a0 type '3RSM0147Z'

zigbee.0
2025-06-25 20:15:37.158	warn	ELEVATED:I01 (71c5) Zigbee Event of Type attributeReport from device 0xffffb40e060599a0, incoming event: {"type":"attributeReport","data":{"batteryPercentageRemaining":200},"linkquality":225,"groupID":0,"cluster":"genPowerCfg","meta":{"zclTransactionSequenceNumber":196,"frameControl":{"frameType":0,"manufacturerSpecific":false,"direction":1,"disableDefaultResponse":true,"reservedBits":0}},"endpoint_id":1}

zigbee.0
2025-06-25 20:15:37.152	warn	ELEVATED:I01 (71c0) Zigbee Event of Type attributeReport from device 0xffffb40e060599a0, incoming event: {"type":"attributeReport","data":{"batteryVoltage":16},"linkquality":225,"groupID":0,"cluster":"genPowerCfg","meta":{"zclTransactionSequenceNumber":195,"frameControl":{"frameType":0,"manufacturerSpecific":false,"direction":1,"disableDefaultResponse":true,"reservedBits":0}},"endpoint_id":1}

zigbee.0
2025-06-25 20:15:36.071	warn	ELEVATED:I02 (6d85) value generated '10' from device ffffb40e060599a0 for 'Link quality'

zigbee.0
2025-06-25 20:15:36.070	warn	ELEVATED:I01 (6d85) message received '{"linkquality":10}' from device ffffb40e060599a0 type '3RSM0147Z'

zigbee.0
2025-06-25 20:15:36.070	warn	ELEVATED:I02 (6d85) value generated 'true' from device ffffb40e060599a0 for 'Available'

zigbee.0
2025-06-25 20:15:36.069	warn	ELEVATED:I01 (6d85) message received '{"available":true}' from device ffffb40e060599a0 type '3RSM0147Z'

zigbee.0
2025-06-25 20:15:35.187	warn	ELEVATED:I02 (6a04) value generated '0' from device ffffb40e060599a0 for 'Humidity'

zigbee.0
2025-06-25 20:15:35.186	warn	ELEVATED:I01 (6a04) message received '{"humidity":0}' from device ffffb40e060599a0 type '3RSM0147Z'

zigbee.0
2025-06-25 20:15:35.183	warn	ELEVATED:I02 (6a04) value generated '225' from device ffffb40e060599a0 for 'Link quality'

zigbee.0
2025-06-25 20:15:35.182	warn	ELEVATED:I01 (6a04) message received '{"linkquality":225}' from device ffffb40e060599a0 type '3RSM0147Z'

zigbee.0
2025-06-25 20:15:35.179	warn	ELEVATED:I02 (69fc) value generated '30.81' from device ffffb40e060599a0 for 'Temperature'

zigbee.0
2025-06-25 20:15:35.179	warn	ELEVATED:I01 (69fc) message received '{"temperature":30.81}' from device ffffb40e060599a0 type '3RSM0147Z'

zigbee.0
2025-06-25 20:15:35.177	warn	ELEVATED:I02 (69fc) value generated '225' from device ffffb40e060599a0 for 'Link quality'

zigbee.0
2025-06-25 20:15:35.176	warn	ELEVATED:I01 (69fc) message received '{"linkquality":225}' from device ffffb40e060599a0 type '3RSM0147Z'

zigbee.0
2025-06-25 20:15:35.172	warn	ELEVATED:I01 (6a04) Zigbee Event of Type attributeReport from device 0xffffb40e060599a0, incoming event: {"type":"attributeReport","data":{"measuredValue":0},"linkquality":225,"groupID":0,"cluster":"msRelativeHumidity","meta":{"zclTransactionSequenceNumber":194,"frameControl":{"frameType":0,"manufacturerSpecific":false,"direction":1,"disableDefaultResponse":true,"reservedBits":0}},"endpoint_id":1}

zigbee.0
2025-06-25 20:15:35.164	warn	ELEVATED:I01 (69fc) Zigbee Event of Type attributeReport from device 0xffffb40e060599a0, incoming event: {"type":"attributeReport","data":{"measuredValue":3081},"linkquality":225,"groupID":0,"cluster":"msTemperatureMeasurement","meta":{"zclTransactionSequenceNumber":193,"frameControl":{"frameType":0,"manufacturerSpecific":false,"direction":1,"disableDefaultResponse":true,"reservedBits":0}},"endpoint_id":1}

zigbee.0
2025-06-25 20:15:35.066	warn	ELEVATED:Ida (699a) Device '0xffffb40e060599a0' announced itself

zigbee.0
2025-06-25 20:14:54.818	info	List of port: [{"path":"/dev/ttyUSB0","manufacturer":"ITead","serialNumber":"dad0c14dc174ef11b4f0cd8c8fcc3fa0","pnpId":"usb-ITead_Sonoff_Zigbee_3.0_USB_Dongle_Plus_dad0c14dc174ef11b4f0cd8c8fcc3fa0-if00-port0","vendorId":"10c4","productId":"ea60"},{"path":"/dev/ttyACM0","manufacturer":"0658","serialNumber":"E3040A02-4A02-0113-1510-041500BFCC64","pnpId":"usb-0658_0200_E3040A02-4A02-0113-1510-041500BFCC64-if00","vendorId":"0658","productId":"0200"},{"path":"/dev/ttyAMA0"},{"path":"/dev/ttyS0"}]

zigbee.0
2025-06-25 20:14:16.430	warn	ELEVATED:I02 (3665) value generated '10' from device ffffb40e060599a0 for 'Link quality'

zigbee.0
2025-06-25 20:14:16.429	warn	ELEVATED:I01 (3665) message received '{"linkquality":10}' from device ffffb40e060599a0 type '3RSM0147Z'

zigbee.0
2025-06-25 20:14:16.424	warn	ELEVATED:I02 (3664) value generated 'true' from device ffffb40e060599a0 for 'Available'

zigbee.0
2025-06-25 20:14:16.423	warn	ELEVATED:I01 (3664) message received '{"available":true}' from device ffffb40e060599a0 type '3RSM0147Z'

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

zigbee.0
2025-06-25 20:14:15.666	info	Zigbee started

zigbee.0
2025-06-25 20:14:15.663	info	Currently 4 devices are joined:

zigbee.0
2025-06-25 20:14:15.663	info	0x8c65a3fffe5256c2 (addr 11312): ZBDongle-E - SONOFF Sonoff Zigbee 3.0 USB Dongle Plus (EFR32MG21) with router firmware (Router)

zigbee.0
2025-06-25 20:14:15.660	info	0x70b3d52b600a59f0 (addr 12676): TS011F_plug_3 - Tuya Smart plug (with power monitoring by polling) (Router)

zigbee.0
2025-06-25 20:14:15.419	info	0xffffb40e060599a0 (addr 22929): 3RSM0147Z - Third Reality Soil sensor (EndDevice)

zigbee.0
2025-06-25 20:14:15.391	info	0x0ceff6fffe5a0306 (addr 30247): SNZB-02D - SONOFF Temperature and humidity sensor with screen (EndDevice)

zigbee.0
2025-06-25 20:14:15.315	info	Unable to disable LED, unsupported function.

zigbee.0
2025-06-25 20:14:15.313	info	Zigbee-Herdsman started successfully with Coordinator firmware version: {"type":"zStack3x0","meta":{"transportrev":2,"product":1,"majorrel":2,"minorrel":7,"maintrel":1,"revision":20240710}}

zigbee.0
2025-06-25 20:14:14.661	info	Starting Zigbee-Herdsman

zigbee.0
2025-06-25 20:14:14.659	info	Installed Version: iobroker.zigbee@2.0.5 (Converters 23.6.0 Herdsman 3.5.2)

zigbee.0
2025-06-25 20:14:14.606	info	Starting Adapter npm ...

zigbee.0
2025-06-25 20:14:14.604	info	--- creating device debug ---

zigbee.0
2025-06-25 20:14:14.600	info	delete old Backup files. keep only last 10

zigbee.0
2025-06-25 20:14:14.582	info	--> transmitPower : high+

zigbee.0
2025-06-25 20:14:14.571	info	init localConfig

zigbee.0
2025-06-25 20:14:14.540	info	starting. Version 2.0.5 in /opt/iobroker/node_modules/iobroker.zigbee, node: v20.19.3, js-controller: 7.0.6

                  Hier die Ausgabe von IoB Diag

                  ======== Start marking the full check here ===========

```bash
Script v.2025-03-08

*** BASE SYSTEM ***
   Static hostname: pi4-Master
         Icon name: computer
  Operating System: Debian GNU/Linux 11 (bullseye)
            Kernel: Linux 6.1.21-v8+
      Architecture: arm64
OS is similar to:

Model           : Raspberry Pi 4 Model B Rev 1.5
Docker          : false
Virtualization  : none
Kernel          : aarch64
Userland        : 64 bit

Systemuptime and Load:
 20:19:41 up  8:00,  2 users,  load average: 0.63, 0.76, 0.72
CPU threads: 4


*** LIFE CYCLE STATUS ***
Debian 'bullseye' is the current oldstable version. Please upgrade to the latest stable release 'bookworm' in due time!

*** RASPBERRY THROTTLING ***
Current issues:
No throttling issues detected.

Previously detected issues:
No throttling issues detected.

*** TIME AND TIMEZONES ***
               Local time: Wed 2025-06-25 20:19:42 CEST
           Universal time: Wed 2025-06-25 18:19:42 UTC
                 RTC time: n/a
                Time zone: Europe/Berlin (CEST, +0200)
System clock synchronized: yes
              NTP service: active
          RTC in local TZ: no

*** Users and Groups ***
User that called 'iob diag':
pi
HOME=/home/pi
GROUPS=pi adm dialout cdrom sudo audio video plugdev games users input render netdev gpio i2c spi iobroker

User that is running 'js-controller':
iobroker
HOME=/home/iobroker
GROUPS=iobroker tty dialout audio video plugdev bluetooth gpio i2c

*** DISPLAY-SERVER SETUP ***
Display-Server: false
Desktop:
Terminal:       tty

*** MEMORY ***
               total        used        free      shared  buff/cache   available
Mem:            7.8G        3.4G        374M        0.0K        4.1G        4.3G
Swap:            99M         63M         36M
Total:          7.9G        3.4G        410M

Active iob-Instances:   45

         7811 M total memory
         3382 M used memory
         3803 M active memory
         3190 M inactive memory
          374 M free memory
           76 M buffer memory
         3977 M swap cache
           99 M total swap
           63 M used swap
           36 M free swap

*** top - Table Of Processes  ***
top - 20:19:42 up  8:00,  2 users,  load average: 0.63, 0.76, 0.72
Tasks: 219 total,   2 running, 216 sleeping,   0 stopped,   1 zombie
%Cpu(s): 15.3 us,  8.3 sy,  0.0 ni, 76.4 id,  0.0 wa,  0.0 hi,  0.0 si,  0.0 st
MiB Mem :   7811.3 total,    374.5 free,   3382.3 used,   4054.5 buff/cache
MiB Swap:    100.0 total,     36.1 free,     63.9 used.   4298.3 avail Mem

*** FAILED SERVICES ***

  UNIT              LOAD   ACTIVE SUB    DESCRIPTION
* mosquitto.service loaded failed failed Mosquitto MQTT Broker

LOAD   = Reflects whether the unit definition was properly loaded.
ACTIVE = The high-level unit activation state, i.e. generalization of SUB.
SUB    = The low-level unit activation state, values depend on unit type.
1 loaded units listed.


*** DMESG CRITICAL ERRORS ***
No critical errors detected

*** FILESYSTEM ***
Filesystem     Type      Size  Used Avail Use% Mounted on
/dev/root      ext4      220G   34G  178G  16% /
devtmpfs       devtmpfs  3.6G     0  3.6G   0% /dev
tmpfs          tmpfs     3.9G     0  3.9G   0% /dev/shm
tmpfs          tmpfs     1.6G  1.2M  1.6G   1% /run
tmpfs          tmpfs     5.0M  4.0K  5.0M   1% /run/lock
/dev/sda1      vfat      255M   31M  225M  13% /boot
tmpfs          tmpfs     782M     0  782M   0% /run/user/1000

Messages concerning ext4 filesystem in dmesg:
[Wed Jun 25 12:19:18 2025] Kernel command line: coherent_pool=1M 8250.nr_uarts=1 snd_bcm2835.enable_headphones=0 snd_bcm2835.enable_headphones=1 snd_bcm2835.enable_hdmi=1 snd_bcm2835.enable_hdmi=0  smsc95xx.macaddr=E4:5F:01:84:59:3C vc_mem.mem_base=0x3eb00000 vc_mem.mem_size=0x3ff00000  console=ttyS0,115200 console=tty1 root=PARTUUID=e432a575-02 rootfstype=ext4 fsck.repair=yes rootwait
[Wed Jun 25 12:19:21 2025] EXT4-fs (sda2): mounted filesystem with ordered data mode. Quota mode: none.
[Wed Jun 25 12:19:21 2025] VFS: Mounted root (ext4 filesystem) readonly on device 8:2.
[Wed Jun 25 12:19:23 2025] EXT4-fs (sda2): re-mounted. Quota mode: none.

Show mounted filesystems:
TARGET  SOURCE    FSTYPE OPTIONS
/       /dev/sda2 ext4   rw,noatime
`-/boot /dev/sda1 vfat   rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=ascii,shortname=mixed,errors=remount-ro

Files in neuralgic directories:

/var:
9.6G    /var/
4.3G    /var/log
4.1G    /var/log/journal/eefdb7bad79f4dbab7d9171e992a2beb
4.1G    /var/log/journal
3.4G    /var/lib

Archived and active journals take up 4.0G in the file system.

/opt/iobroker/backups:
4.0K    /opt/iobroker/backups/

/opt/iobroker/iobroker-data:
2.3G    /opt/iobroker/iobroker-data/
1.3G    /opt/iobroker/iobroker-data/backup-objects
775M    /opt/iobroker/iobroker-data/files
156M    /opt/iobroker/iobroker-data/files/vis-2
110M    /opt/iobroker/iobroker-data/node-red

The five largest files in iobroker-data are:
570M    /opt/iobroker/iobroker-data/backup-objects/historyDB_2022_11_16-02_45_10_backupiobroker.tar.gz
461M    /opt/iobroker/iobroker-data/backup-objects/influxDB_2022_11_16-02_40_53_backupiobroker.tar.gz
40M     /opt/iobroker/iobroker-data/objects.jsonl
38M     /opt/iobroker/iobroker-data/files/iot.admin/static/js/main.d3d286bd.js.map
27M     /opt/iobroker/iobroker-data/files/tankerkoenig.admin/build/index.js.map

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
Zigbee Network Settings on your coordinator/in nvbackup are:

zigbee.X
Extended Pan ID:
*** MASKED ***
Pan ID:
*** MASKED ***
Channel:
*** MASKED ***
Network Key:
*** MASKED ***

To unmask the settings run 'iob diag --unmask'


*** NodeJS-Installation ***

/usr/bin/nodejs         v20.19.3
/usr/bin/node           v20.19.3
/usr/bin/npm            10.8.2
/usr/bin/npx            10.8.2
/usr/bin/corepack       0.32.0

nodejs:
  Installed: 20.19.3-1nodesource1
  Candidate: 20.19.3-1nodesource1
  Version table:
 *** 20.19.3-1nodesource1 600
        500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages
        100 /var/lib/dpkg/status
     20.19.2-1nodesource1 600
        500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages
     20.19.1-1nodesource1 600
        500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages
     20.19.0-1nodesource1 600
        500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages
     20.18.3-1nodesource1 600
        500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages
     20.18.2-1nodesource1 600
        500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages
     20.18.1-1nodesource1 600
        500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages
     20.18.0-1nodesource1 600
        500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages
     20.17.0-1nodesource1 600
        500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages
     20.16.0-1nodesource1 600
        500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages
     20.15.1-1nodesource1 600
        500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages
     20.15.0-1nodesource1 600
        500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages
     20.14.0-1nodesource1 600
        500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages
     20.13.1-1nodesource1 600
        500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages
     20.13.0-1nodesource1 600
        500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages
     20.12.2-1nodesource1 600
        500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages
     20.12.1-1nodesource1 600
        500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages
     20.12.0-1nodesource1 600
        500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages
     20.11.1-1nodesource1 600
        500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages
     20.11.0-1nodesource1 600
        500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages
     20.10.0-1nodesource1 600
        500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages
     20.9.0-1nodesource1 600
        500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages
     20.8.1-1nodesource1 600
        500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages
     20.8.0-1nodesource1 600
        500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages
     20.7.0-1nodesource1 600
        500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages
     20.6.1-1nodesource1 600
        500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages
     20.6.0-1nodesource1 600
        500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages
     20.5.1-1nodesource1 600
        500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages
     20.5.0-1nodesource1 600
        500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages
     20.4.0-1nodesource1 600
        500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages
     20.3.1-1nodesource1 600
        500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages
     20.3.0-1nodesource1 600
        500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages
     20.2.0-1nodesource1 600
        500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages
     20.1.0-1nodesource1 600
        500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages
     20.0.0-1nodesource1 600
        500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages
     12.22.12~dfsg-1~deb11u7 500
        500 http://security.debian.org/debian-security bullseye-security/main arm64 Packages
     12.22.12~dfsg-1~deb11u4 500
        500 http://deb.debian.org/debian bullseye/main arm64 Packages

Temp directories causing deletion problem: 0
No problems detected

Errors in npm tree: 0
No problems detected

*** ioBroker-Installation ***

ioBroker Status
iobroker is running on this host.


Objects type: jsonl
States  type: jsonl

Hosts:
pi4-Master          pi4-Master (version: 7.0.6, hostname: pi4-Master    , alive, uptime: 24898)

Core adapters versions
js-controller:  7.0.6
admin:          7.7.0
javascript:     8.9.2

nodejs modules from github:     5
+-- iobroker.icons-open-icon-library-png@0.1.3 (git+ssh://git@github.com/ioBroker/ioBroker.icons-open-icon-library-png.git#0847a79d713ee6725ccb6ccfb044c025b73ec946)
+-- iobroker.life360@0.2.21 (git+ssh://git@github.com/MiGoller/ioBroker.life360.git#888e08024c2d93d86aa6eb74f281c574dce86c42)
+-- iobroker.midea@0.1.0 (git+ssh://git@github.com/TA2k/ioBroker.midea.git#0d037c0c9a025b193546f881f747c8f998bfc724)
| +-- samsungtv@0.0.0 (git+https://git@github.com/luca-saggese/samsungtv.git#7fc20107455414e2afb94022682e0787e8635550)
+-- iobroker.sourceanalytix@0.4.15-alpha.1 (git+ssh://git@github.com/DrozmotiX/ioBroker.sourceanalytix.git#1010e11d126dc2e9639b70f17b79d082dead83ba)

Adapter State
+ system.adapter.admin.0                  : admin                 : pi4-Master                               -  enabled, port: 6969, bind: 0.0.0.0, run as: admin
+ system.adapter.alexa2.0                 : alexa2                : pi4-Master                               -  enabled
+ system.adapter.backitup.0               : backitup              : pi4-Master                               -  enabled
+ system.adapter.ble.0                    : ble                   : pi4-Master                               -  enabled
+ system.adapter.cloud.0                  : cloud                 : pi4-Master                               -  enabled
+ system.adapter.ds18b20.0                : ds18b20               : pi4-Master                               -  enabled
+ system.adapter.epson_ecotank_et_2750.0  : epson_ecotank_et_2750 : pi4-Master                               -  enabled
  system.adapter.feiertage.0              : feiertage             : pi4-Master                               -  enabled
+ system.adapter.fritzbox.0               : fritzbox              : pi4-Master                               -  enabled
  system.adapter.fritzdect.0              : fritzdect             : pi4-Master                               - disabled
+ system.adapter.fullybrowser.0           : fullybrowser          : pi4-Master                               -  enabled
  system.adapter.ham.0                    : ham                   : pi4-Master                               - disabled
+ system.adapter.history.0                : history               : pi4-Master                               -  enabled
+ system.adapter.homeconnect.0            : homeconnect           : pi4-Master                               -  enabled
+ system.adapter.i2c.0                    : i2c                   : pi4-Master                               -  enabled
  system.adapter.ical.0                   : ical                  : pi4-Master                               -  enabled
  system.adapter.ical.1                   : ical                  : pi4-Master                               -  enabled
  system.adapter.ical.2                   : ical                  : pi4-Master                               -  enabled
  system.adapter.ical.3                   : ical                  : pi4-Master                               -  enabled
  system.adapter.ical.4                   : ical                  : pi4-Master                               -  enabled
  system.adapter.icons-addictive-flavour-png.0: icons-addictive-flavour-png: pi4-Master                               -  enabled
  system.adapter.icons-material-png.0     : icons-material-png    : pi4-Master                               -  enabled
  system.adapter.icons-material-svg.0     : icons-material-svg    : pi4-Master                               -  enabled
  system.adapter.icons-mfd-png.0          : icons-mfd-png         : pi4-Master                               -  enabled
  system.adapter.icons-mfd-svg.0          : icons-mfd-svg         : pi4-Master                               -  enabled
  system.adapter.icons-open-icon-library-png.0: icons-open-icon-library-png: pi4-Master                               -  enabled
  system.adapter.icons-ultimate-png.0     : icons-ultimate-png    : pi4-Master                               -  enabled
+ system.adapter.influxdb.0               : influxdb              : pi4-Master                               -  enabled, port: 8086
+ system.adapter.iot.0                    : iot                   : pi4-Master                               -  enabled
+ system.adapter.javascript.0             : javascript            : pi4-Master                               -  enabled
+ system.adapter.knx.0                    : knx                   : pi4-Master                               -  enabled, bind: 192.168.178.185
+ system.adapter.lgtv.0                   : lgtv                  : pi4-Master                               -  enabled
  system.adapter.life360.0                : life360               : pi4-Master                               - disabled
+ system.adapter.meross.0                 : meross                : pi4-Master                               -  enabled
  system.adapter.midea.0                  : midea                 : pi4-Master                               - disabled
+ system.adapter.mihome-vacuum.0          : mihome-vacuum         : pi4-Master                               -  enabled, port: 54321
+ system.adapter.modbus.0                 : modbus                : pi4-Master                               -  enabled
+ system.adapter.mqtt.0                   : mqtt                  : pi4-Master                               -  enabled, port: 1879, bind: 0.0.0.0
  system.adapter.mqtt.1                   : mqtt                  : pi4-Master                               - disabled, port: 1783, bind: 0.0.0.0
+ system.adapter.net-tools.0              : net-tools             : pi4-Master                               -  enabled
+ system.adapter.node-red.0               : node-red              : pi4-Master                               -  enabled, port: 1880, bind: 0.0.0.0
+ system.adapter.ping.0                   : ping                  : pi4-Master                               -  enabled
+ system.adapter.rpi2.0                   : rpi2                  : pi4-Master                               -  enabled
  system.adapter.samsung.0                : samsung               : pi4-Master                               - disabled
+ system.adapter.scenes.0                 : scenes                : pi4-Master                               -  enabled
  system.adapter.schoolfree.0             : schoolfree            : pi4-Master                               -  enabled
+ system.adapter.shelly.0                 : shelly                : pi4-Master                               -  enabled, port: 1883, bind: 0.0.0.0
+ system.adapter.shuttercontrol.0         : shuttercontrol        : pi4-Master                               -  enabled
+ system.adapter.simple-api.0             : simple-api            : pi4-Master                               -  enabled, port: 8087, bind: 0.0.0.0, run as: admin
+ system.adapter.sonnen.0                 : sonnen                : pi4-Master                               -  enabled
+ system.adapter.sonoff.0                 : sonoff                : pi4-Master                               -  enabled, port: 1883, bind: 0.0.0.0
+ system.adapter.sourceanalytix.0         : sourceanalytix        : pi4-Master                               -  enabled
+ system.adapter.sql.0                    : sql                   : pi4-Master                               -  enabled, port: 3307
+ system.adapter.tankerkoenig.0           : tankerkoenig          : pi4-Master                               -  enabled
+ system.adapter.telegram.0               : telegram              : pi4-Master                               -  enabled, port: 8443, bind: 0.0.0.0
  system.adapter.text2command.0           : text2command          : pi4-Master                               - disabled
+ system.adapter.tr-064.0                 : tr-064                : pi4-Master                               -  enabled
+ system.adapter.trashschedule.0          : trashschedule         : pi4-Master                               -  enabled
+ system.adapter.tuya.0                   : tuya                  : pi4-Master                               -  enabled
  system.adapter.vis-2-widgets-jaeger-design.0: vis-2-widgets-jaeger-design: pi4-Master                               -  enabled
  system.adapter.vis-2.0                  : vis-2                 : pi4-Master                               - disabled
  system.adapter.vis-google-fonts.0       : vis-google-fonts      : pi4-Master                               -  enabled
  system.adapter.vis-hqwidgets.0          : vis-hqwidgets         : pi4-Master                               -  enabled
  system.adapter.vis-icontwo.0            : vis-icontwo           : pi4-Master                               -  enabled
+ system.adapter.vis-inventwo.0           : vis-inventwo          : pi4-Master                               -  enabled
  system.adapter.vis-jqui-mfd.0           : vis-jqui-mfd          : pi4-Master                               -  enabled
  system.adapter.vis-justgage.0           : vis-justgage          : pi4-Master                               -  enabled
  system.adapter.vis-materialdesign.0     : vis-materialdesign    : pi4-Master                               -  enabled
  system.adapter.vis-metro.0              : vis-metro             : pi4-Master                               -  enabled
  system.adapter.vis-players.0            : vis-players           : pi4-Master                               -  enabled
  system.adapter.vis-plumb.0              : vis-plumb             : pi4-Master                               -  enabled
  system.adapter.vis-timeandweather.0     : vis-timeandweather    : pi4-Master                               -  enabled
  system.adapter.vis.0                    : vis                   : pi4-Master                               -  enabled
+ system.adapter.web.0                    : web                   : pi4-Master                               -  enabled, port: 8082, bind: 0.0.0.0, run as: admin
+ system.adapter.whatsapp-cmb.0           : whatsapp-cmb          : pi4-Master                               -  enabled
+ system.adapter.worx.0                   : worx                  : pi4-Master                               -  enabled
+ system.adapter.zigbee.0                 : zigbee                : pi4-Master                               -  enabled, port: /dev/ttyUSB0
+ system.adapter.zwave2.0                 : zwave2                : pi4-Master                               -  enabled

+ instance is alive

Enabled adapters with bindings
+ system.adapter.admin.0                  : admin                 : pi4-Master                               -  enabled, port: 6969, bind: 0.0.0.0, run as: admin
+ system.adapter.influxdb.0               : influxdb              : pi4-Master                               -  enabled, port: 8086
+ system.adapter.mihome-vacuum.0          : mihome-vacuum         : pi4-Master                               -  enabled, port: 54321
+ system.adapter.mqtt.0                   : mqtt                  : pi4-Master                               -  enabled, port: 1879, bind: 0.0.0.0
+ system.adapter.node-red.0               : node-red              : pi4-Master                               -  enabled, port: 1880, bind: 0.0.0.0
+ system.adapter.shelly.0                 : shelly                : pi4-Master                               -  enabled, port: 1883, bind: 0.0.0.0
+ system.adapter.simple-api.0             : simple-api            : pi4-Master                               -  enabled, port: 8087, bind: 0.0.0.0, run as: admin
+ system.adapter.sonoff.0                 : sonoff                : pi4-Master                               -  enabled, port: 1883, bind: 0.0.0.0
+ system.adapter.sql.0                    : sql                   : pi4-Master                               -  enabled, port: 3307
+ system.adapter.telegram.0               : telegram              : pi4-Master                               -  enabled, port: 8443, bind: 0.0.0.0
+ system.adapter.web.0                    : web                   : pi4-Master                               -  enabled, port: 8082, bind: 0.0.0.0, run as: admin
+ system.adapter.zigbee.0                 : zigbee                : pi4-Master                               -  enabled, port: /dev/ttyUSB0

ioBroker-Repositories
┌─────────┬──────────┬─────────────────────────────────────────────────────────┬──────────────┐
│ (index) │ name     │ url                                                     │ auto upgrade │
├─────────┼──────────┼─────────────────────────────────────────────────────────┼──────────────┤
│ 0       │ 'stable' │ 'http://download.iobroker.net/sources-dist.json'        │ true         │
│ 1       │ 'beta'   │ 'http://download.iobroker.net/sources-dist-latest.json' │ false        │
└─────────┴──────────┴─────────────────────────────────────────────────────────┴──────────────┘

Active repo(s): stable
Upgrade policy: none

Installed ioBroker-Adapters
Used repository: stable
Adapter    "admin"        : 7.6.17   , installed 7.7.0
Adapter    "alexa2"       : 3.26.5   , installed 3.26.5
Adapter    "backitup"     : 3.2.2    , installed 3.2.2
Adapter    "ble"          : 0.14.0   , installed 0.14.0
Adapter    "cloud"        : 5.0.1    , installed 5.0.1
Adapter    "discovery"    : 5.0.0    , installed 5.0.0
Adapter    "ds18b20"      : 3.0.1    , installed 3.0.1
Adapter    "epson_ecotank_et_2750": 1.0.1, installed 1.0.1
Adapter    "feiertage"    : 1.2.1    , installed 1.2.1
Adapter    "fritzbox"     : 0.6.0    , installed 0.6.0
Adapter    "fritzdect"    : 2.6.2    , installed 2.6.1  [Updatable]
Adapter    "fullybrowser" : 3.1.1    , installed 3.1.1
Adapter    "ham"          : 5.3.1    , installed 5.3.1
Adapter    "history"      : 3.0.1    , installed 3.0.1
Adapter    "homeconnect"  : 1.4.3    , installed 1.4.3
Adapter    "i2c"          : 1.2.1    , installed 1.2.1
Adapter    "ical"         : 1.16.1   , installed 1.16.1
Adapter    "icons-addictive-flavour-png": 0.1.0, installed 0.1.0
Adapter    "icons-material-png": 0.1.0, installed 0.1.0
Adapter    "icons-material-svg": 0.1.0, installed 0.1.0
Adapter    "icons-mfd-png": 1.2.1    , installed 1.2.1
Adapter    "icons-mfd-svg": 1.2.0    , installed 1.2.0
Adapter    "icons-open-icon-library-png": 0.1.2, installed 0.1.3
Adapter    "icons-ultimate-png": 1.0.1, installed 1.0.1
Adapter    "influxdb"     : 4.0.2    , installed 4.0.2
Adapter    "iot"          : 3.3.0    , installed 3.3.0
Adapter    "javascript"   : 8.9.2    , installed 8.9.2
Controller "js-controller": 7.0.6    , installed 7.0.6
Adapter    "knx"          : 2.0.30   , installed 2.0.30
Adapter    "lgtv"         : 2.4.0    , installed 2.4.0
Adapter    "meross"       : 1.17.0   , installed 1.17.0
Adapter    "midea"        : 0.0.7    , installed 0.1.0
Adapter    "mihome-vacuum": 5.2.0    , installed 5.2.0
Adapter    "modbus"       : 6.3.2    , installed 6.3.2
Adapter    "mqtt"         : 6.1.2    , installed 6.1.2
Adapter    "net-tools"    : 1.1.2    , installed 1.1.2
Adapter    "node-red"     : 5.2.1    , installed 5.2.1
Adapter    "ping"         : 1.6.2    , installed 1.6.2
Adapter    "rpi2"         : 2.4.0    , installed 2.4.0
Adapter    "samsung"      : 0.6.1    , installed 0.6.1
Adapter    "scenes"       : 3.2.3    , installed 4.0.2
Adapter    "schoolfree"   : 1.1.9    , installed 1.1.9
Adapter    "shelly"       : 9.5.1    , installed 9.5.1
Adapter    "shuttercontrol": 2.0.1   , installed 2.0.1
Adapter    "simple-api"   : 2.8.0    , installed 2.8.0
Adapter    "socketio"     : 6.7.1    , installed 7.0.8
Adapter    "sonnen"       : 1.18.1   , installed 1.18.1
Adapter    "sonoff"       : 3.1.2    , installed 3.1.2
Adapter    "sql"          : 3.0.1    , installed 3.0.1
Adapter    "tankerkoenig" : 3.4.0    , installed 3.4.0
Adapter    "telegram"     : 4.1.0    , installed 4.1.0
Adapter    "text2command" : 3.0.3    , installed 3.0.3
Adapter    "tr-064"       : 4.3.0    , installed 4.3.0
Adapter    "trashschedule": 3.3.0    , installed 3.3.0
Adapter    "tuya"         : 3.16.0   , installed 3.16.0
Adapter    "vis"          : 1.5.6    , installed 1.5.6
Adapter    "vis-2"        : 2.9.64   , installed 2.9.64
Adapter    "vis-2-widgets-jaeger-design": 1.2.7, installed 1.2.7
Adapter    "vis-google-fonts": 1.0.4 , installed 1.0.4
Adapter    "vis-hqwidgets": 1.5.1    , installed 1.5.1
Adapter    "vis-icontwo"  : 1.11.0   , installed 1.11.0
Adapter    "vis-inventwo" : 3.3.5    , installed 3.3.5
Adapter    "vis-jqui-mfd" : 1.1.1    , installed 1.1.1
Adapter    "vis-justgage" : 2.1.7    , installed 2.1.7
Adapter    "vis-materialdesign": 0.5.9, installed 0.5.9
Adapter    "vis-metro"    : 1.2.0    , installed 1.2.0
Adapter    "vis-players"  : 0.1.6    , installed 0.1.6
Adapter    "vis-plumb"    : 1.0.2    , installed 1.0.2
Adapter    "vis-timeandweather": 1.2.2, installed 1.2.2
Adapter    "web"          : 7.0.8    , installed 7.0.8
Adapter    "whatsapp-cmb" : 0.3.0    , installed 0.3.0
Adapter    "worx"         : 3.2.4    , installed 3.2.4
Adapter    "ws"           : 2.6.2    , installed 3.0.19
Adapter    "zigbee"       : 2.0.5    , installed 2.0.5
Adapter    "zwave2"       : 3.1.0    , installed 3.1.0

Objects and States
Please stand by - This may take a while
Objects:        19833
States:         17847

*** OS-Repositories and Updates ***
Hit:1 http://security.debian.org/debian-security bullseye-security InRelease
Hit:2 http://deb.debian.org/debian bullseye InRelease
Hit:3 http://deb.debian.org/debian bullseye-updates InRelease
Hit:4 http://archive.raspberrypi.org/debian bullseye InRelease
Hit:5 https://repos.influxdata.com/debian stable InRelease
Hit:6 https://apt.grafana.com stable InRelease
Hit:7 https://repos.influxdata.com/debian stretch InRelease
Hit:8 https://deb.nodesource.com/node_20.x nodistro InRelease
Reading package lists...
Pending Updates: 0

*** Listening Ports ***
Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address           Foreign Address         State       User       Inode      PID/Program name
tcp        0      0 0.0.0.0:9001            0.0.0.0:*               LISTEN      1001       189723     25382/iobroker.js-c
tcp        0      0 0.0.0.0:9000            0.0.0.0:*               LISTEN      1001       188953     25382/iobroker.js-c
tcp        0      0 0.0.0.0:22              0.0.0.0:*               LISTEN      0          14559      654/sshd: /usr/sbin
tcp        0      0 0.0.0.0:1879            0.0.0.0:*               LISTEN      1001       190455     25928/io.mqtt.0
tcp        0      0 0.0.0.0:1880            0.0.0.0:*               LISTEN      1001       190059     25580/node-red
tcp        0      0 0.0.0.0:1883            0.0.0.0:*               LISTEN      1001       195060     26220/io.sonoff.0
tcp        0      0 127.0.0.1:8088          0.0.0.0:*               LISTEN      999        11677      696/influxd
tcp6       0      0 :::22                   :::*                    LISTEN      0          14562      654/sshd: /usr/sbin
tcp6       0      0 :::1821                 :::*                    LISTEN      1001       195880     26380/io.ds18b20.0
tcp6       0      0 :::3030                 :::*                    LISTEN      1001       191039     25693/io.fullybrows
tcp6       0      0 :::3000                 :::*                    LISTEN      110        15485      808/grafana
tcp6       0      0 :::6969                 :::*                    LISTEN      1001       189057     25400/io.admin.0
tcp6       0      0 :::8082                 :::*                    LISTEN      1001       196567     26747/io.web.0
tcp6       0      0 :::8087                 :::*                    LISTEN      1001       194545     26471/io.simple-api
tcp6       0      0 :::8086                 :::*                    LISTEN      999        13294      696/influxd
udp        0      0 192.168.178.185:33436   0.0.0.0:*                           1001       970178     25847/io.knx.0
udp        0      0 192.168.178.185:37561   0.0.0.0:*                           1001       934363     25847/io.knx.0
udp        0      0 192.168.178.185:50320   0.0.0.0:*                           1001       851723     25847/io.knx.0
udp        0      0 192.168.178.185:38034   0.0.0.0:*                           1001       1204940    25847/io.knx.0
udp        0      0 192.168.178.185:5353    0.0.0.0:*                           1001       195713     26246/io.tr-064.0
udp        0      0 0.0.0.0:5353            0.0.0.0:*                           108        11598      522/avahi-daemon: r
udp        0      0 192.168.178.185:38188   0.0.0.0:*                           1001       503118     25847/io.knx.0
udp        0      0 192.168.178.185:42299   0.0.0.0:*                           1001       1199623    25847/io.knx.0
udp        0      0 0.0.0.0:5683            0.0.0.0:*                           1001       191462     26127/io.shelly.0
udp        0      0 192.168.178.185:58972   0.0.0.0:*                           1001       934750     25847/io.knx.0
udp        0      0 192.168.178.185:38501   0.0.0.0:*                           1001       306739     25847/io.knx.0
udp        0      0 0.0.0.0:55133           0.0.0.0:*                           108        11600      522/avahi-daemon: r
udp        0      0 192.168.178.185:39140   0.0.0.0:*                           1001       968220     25847/io.knx.0
udp        0      0 192.168.178.185:47373   0.0.0.0:*                           1001       318632     25847/io.knx.0
udp        0      0 0.0.0.0:6666            0.0.0.0:*                           1001       196195     26279/io.tuya.0
udp        0      0 0.0.0.0:6667            0.0.0.0:*                           1001       196196     26279/io.tuya.0
udp        0      0 192.168.178.185:43684   0.0.0.0:*                           1001       1013029    25847/io.knx.0
udp        0      0 192.168.178.185:39720   0.0.0.0:*                           1001       931937     25847/io.knx.0
udp        0      0 192.168.178.185:56110   0.0.0.0:*                           1001       911755     25847/io.knx.0
udp        0      0 192.168.178.185:60235   0.0.0.0:*                           1001       474397     25847/io.knx.0
udp        0      0 192.168.178.185:39839   0.0.0.0:*                           1001       999258     25847/io.knx.0
udp        0      0 192.168.178.185:39989   0.0.0.0:*                           1001       201298     25847/io.knx.0
udp        0      0 192.168.178.185:56379   0.0.0.0:*                           1001       325796     25847/io.knx.0
udp        0      0 192.168.178.185:48380   0.0.0.0:*                           1001       194001     25847/io.knx.0
udp        0      0 192.168.178.185:44379   0.0.0.0:*                           1001       850925     25847/io.knx.0
udp        0      0 192.168.178.185:60959   0.0.0.0:*                           1001       1009835    25847/io.knx.0
udp        0      0 192.168.178.185:32847   0.0.0.0:*                           1001       205725     25847/io.knx.0
udp        0      0 0.0.0.0:53421           0.0.0.0:*                           1001       192258     25902/io.mihome-vac
udp        0      0 192.168.178.185:41156   0.0.0.0:*                           1001       302699     25847/io.knx.0
udp        0      0 192.168.178.185:41274   0.0.0.0:*                           1001       190969     25580/node-red
udp6       0      0 :::5353                 :::*                                108        11599      522/avahi-daemon: r
udp6       0      0 :::41173                :::*                                108        11601      522/avahi-daemon: r

*** Log File - Last 25 Lines ***

2025-06-25 20:16:20.378  - warn: zigbee.0 (154603) ELEVATED:I02 (1a87) value generated '225' from device ffffb40e060599a0 for 'Link quality'
2025-06-25 20:16:20.379  - warn: zigbee.0 (154603) ELEVATED:I01 (1a87) message received '{"battery":100}' from device ffffb40e060599a0 type '3RSM0147Z'
2025-06-25 20:16:20.380  - warn: zigbee.0 (154603) ELEVATED:I02 (1a87) value generated '100' from device ffffb40e060599a0 for 'Battery percent'
2025-06-25 20:16:22.969  - info: influxdb.0 (25437) Store 501 buffered influxDB history points
2025-06-25 20:17:02.120  - info: mqtt.0 (25928) Client [Holzhütte-Tür] connected with secret 1750875422120_3859
2025-06-25 20:17:02.972  - info: mqtt.0 (25928) Client [Holzhütte-Tür] connection closed: disconnected
2025-06-25 20:17:46.857  - info: influxdb.0 (25437) Store 501 buffered influxDB history points
2025-06-25 20:18:01.564  - info: mqtt.0 (25928) Client [Holzhütte-Tür] connected with secret 1750875481564_5212
2025-06-25 20:18:02.386  - info: mqtt.0 (25928) Client [Holzhütte-Tür] connection closed: disconnected
2025-06-25 20:18:04.113  - debug: alexa2.0 (25628) Alexa-Remote HTTP2-PUSH: Send Ping
2025-06-25 20:18:14.284  - debug: shuttercontrol.0 (26159) outsidetemperature changed: knx.0.Melden_Sensor.Wetterstation_Regensensor.Temperatur_Messwert | Value: 32.4°C
2025-06-25 20:19:01.991  - info: mqtt.0 (25928) Client [Holzhütte-Tür] connected with secret 1750875541990_2988
2025-06-25 20:19:02.869  - info: mqtt.0 (25928) Client [Holzhütte-Tür] connection closed: disconnected
2025-06-25 20:19:16.824  - info: influxdb.0 (25437) Store 504 buffered influxDB history points
2025-06-25 20:19:50.308  - debug: shuttercontrol.0 (26159) Lightsensor changed: knx.0.Melden_Sensor.Wetterstation_Regensensor.Helligjkeit_Süd_Messwert | Value: 10199.04lux
2025-06-25 20:20:00.007  - debug: shuttercontrol.0 (26159) calculate astrodata ...
2025-06-25 20:20:00.008  - debug: shuttercontrol.0 (26159) Sun Azimut: 296.6°
2025-06-25 20:20:00.008  - debug: shuttercontrol.0 (26159) Sun Elevation: 7.9°
2025-06-25 20:20:02.438  - info: mqtt.0 (25928) Client [Holzhütte-Tür] connected with secret 1750875602437_3871
2025-06-25 20:20:03.289  - info: mqtt.0 (25928) Client [Holzhütte-Tür] connection closed: disconnected
2025-06-25 20:20:24.266  - debug: shuttercontrol.0 (26159) outsidetemperature changed: knx.0.Melden_Sensor.Wetterstation_Regensensor.Temperatur_Messwert | Value: 32.3°C
2025-06-25 20:20:43.970  - info: influxdb.0 (25437) Store 501 buffered influxDB history points
2025-06-25 20:21:01.886  - info: mqtt.0 (25928) Client [Holzhütte-Tür] connected with secret 1750875661886_7516
2025-06-25 20:21:02.713  - info: mqtt.0 (25928) Client [Holzhütte-Tür] connection closed: disconnected
2025-06-25 20:21:04.114  - debug: alexa2.0 (25628) Alexa-Remote HTTP2-PUSH: Send Ping


                  Kann mir jemand weiter helfen?

Mfg
Tom
                  arteckA Offline
                  arteckA Offline
                  arteck
                  Developer Most Active
                  schrieb am zuletzt editiert von
                  #13

                  @autodidakt

                  ELEVATED

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

                  steht hier was - >

                  zigbee.0.info.debugmessages

                  zigbee hab ich, zwave auch, nuc's genauso und HA auch

                  AutodidaktA 1 Antwort Letzte Antwort
                  0
                  • AutodidaktA Autodidakt

                    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 BraunT Online
                    Thomas BraunT Online
                    Thomas Braun
                    Most Active
                    schrieb am zuletzt editiert von
                    #14

                    @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.

                    Linux-Werkzeugkasten:
                    https://forum.iobroker.net/topic/42952/der-kleine-iobroker-linux-werkzeugkasten
                    NodeJS Fixer Skript:
                    https://forum.iobroker.net/topic/68035/iob-node-fix-skript
                    iob_diag: curl -sLf -o diag.sh https://iobroker.net/diag.sh && bash diag.sh

                    AutodidaktA 1 Antwort Letzte Antwort
                    0
                    • Thomas BraunT Thomas Braun

                      @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.

                      AutodidaktA Offline
                      AutodidaktA Offline
                      Autodidakt
                      schrieb am zuletzt editiert von Autodidakt
                      #15

                      @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 Antwort Letzte Antwort
                      0
                      • arteckA arteck

                        @autodidakt

                        ELEVATED

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

                        steht hier was - >

                        zigbee.0.info.debugmessages
                        AutodidaktA Offline
                        AutodidaktA Offline
                        Autodidakt
                        schrieb am zuletzt editiert von
                        #16

                        @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

                        arteckA 1 Antwort Letzte Antwort
                        0
                        • AutodidaktA Autodidakt

                          @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

                          arteckA Offline
                          arteckA Offline
                          arteck
                          Developer Most Active
                          schrieb am zuletzt editiert von
                          #17

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

                          zigbee hab ich, zwave auch, nuc's genauso und HA auch

                          AutodidaktA 1 Antwort Letzte Antwort
                          0
                          • arteckA arteck

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

                            AutodidaktA Offline
                            AutodidaktA Offline
                            Autodidakt
                            schrieb am zuletzt editiert von
                            #18

                            @arteck Ich kann Dir nicht folgen...

                            1 Antwort Letzte Antwort
                            0
                            • B Offline
                              B Offline
                              Brokerti
                              schrieb am zuletzt editiert von
                              #19

                              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 Antwort Letzte Antwort
                              0
                              • B Brokerti

                                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 Online
                                A Online
                                AlexHaxe
                                schrieb am zuletzt editiert von
                                #20

                                @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 Antwort Letzte Antwort
                                0
                                • A AlexHaxe

                                  @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 Offline
                                  B Offline
                                  Brokerti
                                  schrieb am zuletzt editiert von
                                  #21

                                  @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 Antwort Letzte Antwort
                                  0
                                  • B Brokerti

                                    @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 Online
                                    A Online
                                    AlexHaxe
                                    schrieb am zuletzt editiert von
                                    #22

                                    @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 Antwort Letzte Antwort
                                    0
                                    • A AlexHaxe

                                      @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 Offline
                                      B Offline
                                      Brokerti
                                      schrieb am zuletzt editiert von
                                      #23

                                      @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! :)

                                      AutodidaktA 1 Antwort Letzte Antwort
                                      0
                                      • B Brokerti

                                        @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! :)

                                        AutodidaktA Offline
                                        AutodidaktA Offline
                                        Autodidakt
                                        schrieb am zuletzt editiert von
                                        #24

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

                                        Was ist ein BWM?

                                        sigi234S 1 Antwort Letzte Antwort
                                        0
                                        • AutodidaktA Autodidakt

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

                                          Was ist ein BWM?

                                          sigi234S Online
                                          sigi234S Online
                                          sigi234
                                          Forum Testing Most Active
                                          schrieb am zuletzt editiert von
                                          #25

                                          @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

                                          Bitte benutzt das Voting rechts unten im Beitrag wenn er euch geholfen hat.
                                          Immer Daten sichern!

                                          1 Antwort Letzte Antwort
                                          1
                                          Antworten
                                          • In einem neuen Thema antworten
                                          Anmelden zum Antworten
                                          • Älteste zuerst
                                          • Neuste zuerst
                                          • Meiste Stimmen

                                          Support us

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

                                          921

                                          Online

                                          32.4k

                                          Benutzer

                                          81.5k

                                          Themen

                                          1.3m

                                          Beiträge
                                          Community
                                          Impressum | Datenschutz-Bestimmungen | Nutzungsbedingungen | Einwilligungseinstellungen
                                          ioBroker Community 2014-2025
                                          logo
                                          • Anmelden
                                          • Du hast noch kein Konto? Registrieren
                                          • Anmelden oder registrieren, um zu suchen
                                          • Erster Beitrag
                                            Letzter Beitrag
                                          0
                                          • Home
                                          • Aktuell
                                          • Tags
                                          • Ungelesen 0
                                          • Kategorien
                                          • Unreplied
                                          • Beliebt
                                          • GitHub
                                          • Docu
                                          • Hilfe