Navigation

    Logo
    • Register
    • Login
    • Search
    • Recent
    • Tags
    • Unread
    • Categories
    • Unreplied
    • Popular
    • GitHub
    • Docu
    • Hilfe
    1. Home
    2. Deutsch
    3. Tester
    4. Tester wanted - Zigbee Adapter 3.1

    NEWS

    • Neues Video "KI im Smart Home" - ioBroker plus n8n

    • Neues Video über Aliase, virtuelle Geräte und Kategorien

    • Wir empfehlen: Node.js 22.x

    Tester wanted - Zigbee Adapter 3.1

    This topic has been deleted. Only users with topic management privileges can see it.
    • Latzi
      Latzi @Asgothian last edited by Latzi

      @asgothian
      ich hab auf 3.1.2 (von 3.0.5) umgestellt, folgende Meldungen kamen:

      2025-09-18 17:59:36.091 - info: host.ioBroker iobroker NPM version: 10.9.3Installing iobroker.zigbee@3.1.2... (System call)
      2025-09-18 17:59:36.172 - info: zigbee.0 (1523) Closing Zigbee network, 0 seconds remaining
      2025-09-18 17:59:39.934 - info: zigbee.0 (1523) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
      2025-09-18 17:59:40.555 - info: host.ioBroker instance system.adapter.zigbee.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
      2025-09-18 17:59:50.505 - info: host.ioBroker iobroker removed 9 packages, and changed 4 packages in 14s426 packages are looking for funding run `npm fund` for details
      2025-09-18 17:59:50.535 - info: host.ioBroker iobroker Updating objects from io-package.json for adapter "zigbee" with version "3.1.2"
      2025-09-18 17:59:50.584 - info: host.ioBroker iobroker Update "system.adapter.zigbee.0"
      2025-09-18 17:59:51.595 - info: host.ioBroker iobroker upload [341] zigbee.admin /opt/iobroker/node_modules/iobroker.zigbee/admin/adapter-settings.js adapter-settings.js application/javascript
      2025-09-18 17:59:51.705 - info: host.ioBroker iobroker upload [300] zigbee.admin /opt/iobroker/node_modules/iobroker.zigbee/admin/img/HY08WE.png img/HY08WE.png image/png
      2025-09-18 17:59:51.817 - info: host.ioBroker iobroker upload [250] zigbee.admin /opt/iobroker/node_modules/iobroker.zigbee/admin/img/ctrl_neutral2.png img/ctrl_neutral2.png image/png
      2025-09-18 17:59:51.933 - info: host.ioBroker iobroker upload [200] zigbee.admin /opt/iobroker/node_modules/iobroker.zigbee/admin/img/iczb_kpd18s.png img/iczb_kpd18s.png image/png
      2025-09-18 17:59:52.152 - info: host.ioBroker iobroker upload [150] zigbee.admin /opt/iobroker/node_modules/iobroker.zigbee/admin/img/lightify-driver.png img/lightify-driver.png image/png
      2025-09-18 17:59:52.281 - info: host.ioBroker iobroker upload [100] zigbee.admin /opt/iobroker/node_modules/iobroker.zigbee/admin/img/philips_hue_1746430P7.png img/philips_hue_1746430P7.png image/png
      2025-09-18 17:59:52.309 - info: host.ioBroker iobroker upload [90] zigbee.admin /opt/iobroker/node_modules/iobroker.zigbee/admin/img/philips_hue_centura_square.png img/philips_hue_centura_square.png image/png
      2025-09-18 17:59:52.335 - info: host.ioBroker iobroker upload [80] zigbee.admin /opt/iobroker/node_modules/iobroker.zigbee/admin/img/philips_hue_iris.png img/philips_hue_iris.png image/png
      2025-09-18 17:59:52.358 - info: host.ioBroker iobroker upload [70] zigbee.admin /opt/iobroker/node_modules/iobroker.zigbee/admin/img/philips_hue_signe_table.png img/philips_hue_signe_table.png image/png
      2025-09-18 17:59:52.384 - info: host.ioBroker iobroker upload [60] zigbee.admin /opt/iobroker/node_modules/iobroker.zigbee/admin/img/q-remote.png img/q-remote.png image/png
      2025-09-18 17:59:52.414 - info: host.ioBroker iobroker upload [50] zigbee.admin /opt/iobroker/node_modules/iobroker.zigbee/admin/img/sensor_wleak_aq1.png img/sensor_wleak_aq1.png image/png
      2025-09-18 17:59:52.441 - info: host.ioBroker iobroker upload [40] zigbee.admin /opt/iobroker/node_modules/iobroker.zigbee/admin/img/start_stop.png img/start_stop.png image/png
      2025-09-18 17:59:52.469 - info: host.ioBroker iobroker upload [30] zigbee.admin /opt/iobroker/node_modules/iobroker.zigbee/admin/img/ts0203.png img/ts0203.png image/png
      2025-09-18 17:59:52.530 - info: host.ioBroker iobroker upload [20] zigbee.admin /opt/iobroker/node_modules/iobroker.zigbee/admin/img/tuya_tyzs1l.png img/tuya_tyzs1l.png image/png
      2025-09-18 17:59:52.539 - info: host.ioBroker iobroker upload [19] zigbee.admin /opt/iobroker/node_modules/iobroker.zigbee/admin/img/unavailable.png img/unavailable.png image/png
      2025-09-18 17:59:52.545 - info: host.ioBroker iobroker upload [18] zigbee.admin /opt/iobroker/node_modules/iobroker.zigbee/admin/img/unknown.png img/unknown.png image/png
      2025-09-18 17:59:52.567 - info: host.ioBroker iobroker upload [17] zigbee.admin /opt/iobroker/node_modules/iobroker.zigbee/admin/img/wemo.png img/wemo.png image/png
      2025-09-18 17:59:52.573 - info: host.ioBroker iobroker upload [16] zigbee.admin /opt/iobroker/node_modules/iobroker.zigbee/admin/img/xiaomi_plug_eu.png img/xiaomi_plug_eu.png image/png
      2025-09-18 17:59:52.578 - info: host.ioBroker iobroker upload [15] zigbee.admin /opt/iobroker/node_modules/iobroker.zigbee/admin/img/xiaomi_wireless_switch.png img/xiaomi_wireless_switch.png image/png
      2025-09-18 17:59:52.586 - info: host.ioBroker iobroker upload [14] zigbee.admin /opt/iobroker/node_modules/iobroker.zigbee/admin/img/zbt_e27.png img/zbt_e27.png image/png
      2025-09-18 17:59:52.591 - info: host.ioBroker iobroker upload [13] zigbee.admin /opt/iobroker/node_modules/iobroker.zigbee/admin/img/zbt_e27_rgbw.png img/zbt_e27_rgbw.png image/png
      2025-09-18 17:59:52.597 - info: host.ioBroker iobroker upload [12] zigbee.admin /opt/iobroker/node_modules/iobroker.zigbee/admin/img/zbt_led_panel.png img/zbt_led_panel.png image/png
      2025-09-18 17:59:52.603 - info: host.ioBroker iobroker upload [11] zigbee.admin /opt/iobroker/node_modules/iobroker.zigbee/admin/img/zbt_smart_switch.png img/zbt_smart_switch.png image/png
      2025-09-18 17:59:52.608 - info: host.ioBroker iobroker upload [10] zigbee.admin /opt/iobroker/node_modules/iobroker.zigbee/admin/img/zemismart_sw2.png img/zemismart_sw2.png image/png
      2025-09-18 17:59:52.613 - info: host.ioBroker iobroker upload [9] zigbee.admin /opt/iobroker/node_modules/iobroker.zigbee/admin/index.html index.html text/html
      2025-09-18 17:59:52.617 - info: host.ioBroker iobroker upload [8] zigbee.admin /opt/iobroker/node_modules/iobroker.zigbee/admin/index_m.html index_m.html text/html
      2025-09-18 17:59:52.621 - info: host.ioBroker iobroker upload [7] zigbee.admin /opt/iobroker/node_modules/iobroker.zigbee/admin/moment.min.js moment.min.js application/javascript
      2025-09-18 17:59:52.626 - info: host.ioBroker iobroker upload [6] zigbee.admin /opt/iobroker/node_modules/iobroker.zigbee/admin/shuffle.min.js shuffle.min.js application/javascript
      2025-09-18 17:59:52.630 - info: host.ioBroker iobroker upload [5] zigbee.admin /opt/iobroker/node_modules/iobroker.zigbee/admin/tab_m.html tab_m.html text/html
      2025-09-18 17:59:52.634 - info: host.ioBroker iobroker upload [4] zigbee.admin /opt/iobroker/node_modules/iobroker.zigbee/admin/vis-network.min.css vis-network.min.css text/css
      2025-09-18 17:59:52.639 - info: host.ioBroker iobroker upload [3] zigbee.admin /opt/iobroker/node_modules/iobroker.zigbee/admin/vis-network.min.js vis-network.min.js application/javascript
      2025-09-18 17:59:52.645 - info: host.ioBroker iobroker upload [2] zigbee.admin /opt/iobroker/node_modules/iobroker.zigbee/admin/words.js words.js application/javascript
      2025-09-18 17:59:52.651 - info: host.ioBroker iobroker upload [1] zigbee.admin /opt/iobroker/node_modules/iobroker.zigbee/admin/zigbee.png zigbee.png image/png
      2025-09-18 17:59:52.656 - info: host.ioBroker iobroker upload [0] zigbee.admin /opt/iobroker/node_modules/iobroker.zigbee/admin/zigbee.svg zigbee.svg image/svg+xml
      2025-09-18 17:59:52.661 - info: host.ioBroker iobroker host.ioBroker Adapter "system.adapter.zigbee.0" is started
      2025-09-18 17:59:52.674 - info: host.ioBroker "system.adapter.zigbee.0" enabled
      2025-09-18 17:59:53.226 - info: host.ioBroker instance system.adapter.zigbee.0 in version "3.1.2" started with pid 742748
      2025-09-18 17:59:53.816 - info: host.ioBroker iobroker exit 0
      2025-09-18 17:59:54.766 - info: zigbee.0 (742748) starting. Version 3.1.2 in /opt/iobroker/node_modules/iobroker.zigbee, node: v22.19.0, js-controller: 7.0.7
      2025-09-18 17:59:54.792 - info: zigbee.0 (742748) Adapter ready - starting subsystems. Adapter is running in info mode.
      2025-09-18 17:59:54.793 - info: zigbee.0 (742748) init localConfig
      2025-09-18 17:59:54.841 - info: zigbee.0 (742748) delete old Backup files. keep only last 10
      2025-09-18 17:59:54.843 - info: zigbee.0 (742748) --- creating device debug ---
      2025-09-18 17:59:54.843 - info: zigbee.0 (742748) Autostart Zigbee subsystem
      2025-09-18 17:59:54.843 - info: zigbee.0 (742748) Starting Adapter npm ...
      2025-09-18 17:59:54.863 - info: zigbee.0 (742748) Installed Version: iobroker.zigbee@3.1.2 (Converters 25.28.0 Herdsman 6.1.1)
      2025-09-18 17:59:54.864 - info: zigbee.0 (742748) configured transmit power : high
      2025-09-18 17:59:54.864 - info: zigbee.0 (742748) Starting Zigbee-Herdsman
      2025-09-18 17:59:56.204 - info: zigbee.0 (742748) Zigbee-Herdsman started successfully with Coordinator firmware version: ZStack3x0 : 20221226 (2-1.2.7.1)
      2025-09-18 17:59:56.204 - info: zigbee.0 (742748) Unable to disable LED, unsupported function.
      2025-09-18 17:59:56.248 - info: zigbee.0 (742748) 0x00158d00042cbc41 (addr 32904): MCCGQ11LM - Aqara Door and window sensor (EndDevice)
      2025-09-18 17:59:56.253 - info: zigbee.0 (742748) 0x00158d000578cacb (addr 39762): WXKG01LM - Xiaomi Mi wireless switch (EndDevice)
      2025-09-18 17:59:56.258 - info: zigbee.0 (742748) 0x7cb03eaa0a058b13 (addr 25701): AC03641 - OSRAM LIGHTIFY LED Classic A60 clear (Router)
      2025-09-18 17:59:56.259 - info: zigbee.0 (742748) 0x00158d000423c2b3 (addr 11646): WSDCGQ01LM - Xiaomi Mi temperature and humidity sensor (EndDevice)
      2025-09-18 17:59:56.260 - info: zigbee.0 (742748) 0x00158d000359b3ac (addr 39307): WXKG01LM - Xiaomi Mi wireless switch (EndDevice)
      2025-09-18 17:59:56.260 - info: zigbee.0 (742748) 0x00158d000359b468 (addr 51855): WXKG01LM - Xiaomi Mi wireless switch (EndDevice)
      2025-09-18 17:59:56.261 - info: zigbee.0 (742748) 0x00158d0003fb04e0 (addr 29417): RTCGQ11LM - Aqara Motion sensor (EndDevice)
      2025-09-18 17:59:56.262 - info: zigbee.0 (742748) 0x00158d0003a5b42f (addr 21249): WSDCGQ01LM - Xiaomi Mi temperature and humidity sensor (EndDevice)
      2025-09-18 17:59:56.262 - info: zigbee.0 (742748) 0x00158d000423cca0 (addr 20171): WSDCGQ01LM - Xiaomi Mi temperature and humidity sensor (EndDevice)
      2025-09-18 17:59:56.263 - info: zigbee.0 (742748) 0x00158d0003cbc49f (addr 46812): WSDCGQ01LM - Xiaomi Mi temperature and humidity sensor (EndDevice)
      2025-09-18 17:59:56.263 - info: zigbee.0 (742748) 0x00158d0003a5b46e (addr 7607): WSDCGQ01LM - Xiaomi Mi temperature and humidity sensor (EndDevice)
      2025-09-18 17:59:56.264 - info: zigbee.0 (742748) 0x00158d000451c08a (addr 18096): RTCGQ11LM - Aqara Motion sensor (EndDevice)
      2025-09-18 17:59:56.265 - info: zigbee.0 (742748) 0x00158d000451a4cd (addr 43756): RTCGQ11LM - Aqara Motion sensor (EndDevice)
      2025-09-18 17:59:56.266 - info: zigbee.0 (742748) 0x00158d00041dff50 (addr 42699): WSDCGQ01LM - Xiaomi Mi temperature and humidity sensor (EndDevice)
      2025-09-18 17:59:56.285 - info: zigbee.0 (742748) 0x3425b4fffe97529d (addr 7019): E2112 - IKEA VINDSTYRKA air quality and humidity sensor (Router)
      2025-09-18 17:59:56.286 - info: zigbee.0 (742748) 0x00158d000444a895 (addr 32464): WSDCGQ01LM - Xiaomi Mi temperature and humidity sensor (EndDevice)
      2025-09-18 17:59:56.288 - info: zigbee.0 (742748) 0x00158d00041842da (addr 36038): WSDCGQ01LM - Xiaomi Mi temperature and humidity sensor (EndDevice)
      2025-09-18 17:59:56.289 - info: zigbee.0 (742748) 0x00158d0004185cf3 (addr 62939): WSDCGQ01LM - Xiaomi Mi temperature and humidity sensor (EndDevice)
      2025-09-18 17:59:56.290 - info: zigbee.0 (742748) 0x00158d00041890c8 (addr 32172): WSDCGQ01LM - Xiaomi Mi temperature and humidity sensor (EndDevice)
      2025-09-18 17:59:56.292 - info: zigbee.0 (742748) 0x00158d000423b0e5 (addr 64349): WSDCGQ01LM - Xiaomi Mi temperature and humidity sensor (EndDevice)
      2025-09-18 17:59:56.293 - info: zigbee.0 (742748) 0x00158d000445006d (addr 24968): WSDCGQ01LM - Xiaomi Mi temperature and humidity sensor (EndDevice)
      2025-09-18 17:59:56.296 - info: zigbee.0 (742748) 0x7cb03eaa0a04459b (addr 35587): AC03641 - OSRAM LIGHTIFY LED Classic A60 clear (Router)
      2025-09-18 17:59:56.300 - info: zigbee.0 (742748) 0x60a423fffee55619 (addr 328): E1743 - IKEA TRADFRI on/off switch (EndDevice)
      2025-09-18 17:59:56.301 - info: zigbee.0 (742748) 0x60a423fffeeedaf3 (addr 8811): E1743 - IKEA TRADFRI on/off switch (EndDevice)
      2025-09-18 17:59:56.373 - info: zigbee.0 (742748) 0x001788010bcfad1a (addr 29688): 9290030675 - Philips Hue motion sensor (EndDevice)
      2025-09-18 17:59:56.375 - info: zigbee.0 (742748) 0xbc33acfffea231b7 (addr 42607): LED1836G9 - IKEA TRADFRI bulb E26/E27, warm white, globe, opal, 806 lm (Router)
      2025-09-18 17:59:56.385 - info: zigbee.0 (742748) 0x60a423fffef481d4 (addr 9667): LED1836G9 - IKEA TRADFRI bulb E26/E27, warm white, globe, opal, 806 lm (Router)
      2025-09-18 17:59:56.386 - info: zigbee.0 (742748) 0xbc33acfffe2b5348 (addr 51918): LED1835C6 - IKEA TRADFRI bulb E12/E14/E17, white spectrum, candle, opal, 450/470/440 lm (Router)
      2025-09-18 17:59:56.387 - info: zigbee.0 (742748) 0x04cf8cdf3c8e2db4 (addr 48387): ZNCZ04LM - Xiaomi Mi smart plug EU (Router)
      2025-09-18 17:59:56.535 - info: zigbee.0 (742748) 0xa4c138611008805f (addr 62023): ZY-M100-S_2 - Tuya Mini human breathe sensor (Router)
      2025-09-18 17:59:56.535 - info: zigbee.0 (742748) 0x04cf8cdf3c867556 (addr 9902): ZNCZ04LM - Xiaomi Mi smart plug EU (Router)
      2025-09-18 17:59:56.536 - info: zigbee.0 (742748) 0x04cf8cdf3c8a23ab (addr 24221): ZNCZ04LM - Xiaomi Mi smart plug EU (Router)
      2025-09-18 17:59:56.537 - info: zigbee.0 (742748) 0x04cf8cdf3c8a26a5 (addr 27705): ZNCZ04LM - Xiaomi Mi smart plug EU (Router)
      2025-09-18 17:59:56.537 - info: zigbee.0 (742748) 0x04cf8cdf3c8a28b4 (addr 10173): ZNCZ04LM - Xiaomi Mi smart plug EU (Router)
      2025-09-18 17:59:56.538 - info: zigbee.0 (742748) 0x04cf8cdf3c8a2816 (addr 23098): ZNCZ04LM - Xiaomi Mi smart plug EU (Router)
      2025-09-18 17:59:56.538 - info: zigbee.0 (742748) 0x04cf8cdf3c86766f (addr 31479): ZNCZ04LM - Xiaomi Mi smart plug EU (Router)
      2025-09-18 17:59:56.539 - info: zigbee.0 (742748) 0x00158d000578d0a3 (addr 49463): WXKG01LM - Xiaomi Mi wireless switch (EndDevice)
      2025-09-18 17:59:56.539 - info: zigbee.0 (742748) 0x54ef441000258d08 (addr 21943): SSM-U01 - Aqara Single switch module T1 (with neutral) (Router)
      2025-09-18 17:59:56.547 - info: zigbee.0 (742748) 0xa4c1384d2dd219fb (addr 58682): A1Z - Nous Smart plug (with power monitoring) (Router)
      2025-09-18 17:59:56.549 - info: zigbee.0 (742748) 0xa4c138881bae4f17 (addr 58824): A1Z - Nous Smart plug (with power monitoring) (Router)
      2025-09-18 17:59:56.551 - info: zigbee.0 (742748) 0xa4c1388c55d55499 (addr 35259): ZY-M100-S_2 - Tuya Mini human breathe sensor (Router)
      2025-09-18 17:59:56.569 - info: zigbee.0 (742748) 0xe0798dfffec98052 (addr 10791): ZBMINI - SONOFF Zigbee two way smart switch (Router)
      2025-09-18 17:59:56.573 - info: zigbee.0 (742748) 0xa4c138528cff8d70 (addr 58500): ZY-M100-S_1 - Tuya Mini human breathe sensor (Router)
      2025-09-18 17:59:56.574 - info: zigbee.0 (742748) 0x00158d0009ce28d9 (addr 20575): WSDCGQ11LM - Aqara Temperature and humidity sensor (EndDevice)
      2025-09-18 17:59:56.575 - info: zigbee.0 (742748) 0x70b3d52b600151d7 (addr 15180): SM-0306E-2W - UseeLink 4 gang switch, with USB (Router)
      2025-09-18 17:59:56.577 - info: zigbee.0 (742748) 0xa4c138421ad10f21 (addr 794): ZSS-HM-SSD01 - Moes Smoke sensor (EndDevice)
      2025-09-18 17:59:56.580 - info: zigbee.0 (742748) 0xa4c138b86190bc77 (addr 45898): ZY-M100-24G - Tuya 24G MmWave radar human presence motion sensor (Router)
      2025-09-18 17:59:56.584 - info: zigbee.0 (742748) 0x70ac08fffe5b0952 (addr 42729): HS1SA - Heiman Smoke detector (EndDevice)
      2025-09-18 17:59:56.585 - info: zigbee.0 (742748) 0x60a423fffeed6f44 (addr 61295): E1743 - IKEA TRADFRI on/off switch (EndDevice)
      2025-09-18 17:59:56.586 - info: zigbee.0 (742748) 0x54ef441000b4c59f (addr 10849): SSM-U01 - Aqara Single switch module T1 (with neutral) (Router)
      2025-09-18 17:59:56.586 - info: zigbee.0 (742748) 0x8c6fb9fffe24c4a5 (addr 24033): E22x4 - IKEA TRETAKT smart plug (Router)
      2025-09-18 17:59:56.587 - info: zigbee.0 (742748) 0x001788010bd00a89 (addr 1610): 9290030675 - Philips Hue motion sensor (EndDevice)
      2025-09-18 17:59:56.591 - info: zigbee.0 (742748) 0x60a423fffe88b17c (addr 17210): RS 226 - Innr GU10 Spot (Router)
      2025-09-18 17:59:56.592 - info: zigbee.0 (742748) 0x60a423fffe88a159 (addr 6275): RS 226 - Innr GU10 Spot (Router)
      2025-09-18 17:59:56.593 - info: zigbee.0 (742748) 0x60a423fffe88b2f8 (addr 43487): RS 226 - Innr GU10 Spot (Router)
      2025-09-18 17:59:56.594 - info: zigbee.0 (742748) 0x980c33fffea346f4 (addr 49302): LED2104R3 - IKEA TRADFRI bulb GU10, warm white, 345/380 lm (Router)
      2025-09-18 17:59:56.595 - info: zigbee.0 (742748) 0x881a14fffe18af9a (addr 50700): E22x4 - IKEA TRETAKT smart plug (Router)
      2025-09-18 17:59:56.596 - info: zigbee.0 (742748) 0x8c6fb9fffe268ee2 (addr 33470): E22x4 - IKEA TRETAKT smart plug (Router)
      2025-09-18 17:59:56.596 - info: zigbee.0 (742748) 0x4c5bb3fffe9fd6fc (addr 50522): E2213 - IKEA SOMRIG shortcut button (EndDevice)
      2025-09-18 17:59:56.597 - info: zigbee.0 (742748) 0xc4d8c8fffe8a3c92 (addr 42511): E2201 - IKEA RODRET wireless dimmer/power switch (EndDevice)
      2025-09-18 17:59:56.598 - info: zigbee.0 (742748) 0xa4c138271f07ebc3 (addr 25944): ZG-223Z - HOBEIAN Rainwater detection sensor (EndDevice)
      2025-09-18 17:59:56.599 - info: zigbee.0 (742748) 61 devices are part of the network
      2025-09-18 17:59:56.599 - info: zigbee.0 (742748) Zigbee started
      2025-09-18 17:59:56.637 - info: zigbee.0 (742748) DeviceConfigure 0xa4c138421ad10f21 ZSS-HM-SSD01 needed - Device added to Configuration Queue
      2025-09-18 17:59:56.639 - info: zigbee.0 (742748) DeviceConfigure 0x54ef441000b4c59f SSM-U01 needed - Device added to Configuration Queue
      2025-09-18 17:59:58.684 - info: zigbee.0 (742748) debug devices set to []
      2025-09-18 17:59:59.613 - info: zigbee.0 (742748) downloading https://www.zigbee2mqtt.io/images/devices/MCCGQ11LM.png to img/MCCGQ11LM.png
      2025-09-18 17:59:59.771 - info: zigbee.0 (742748) downloading https://www.zigbee2mqtt.io/images/devices/AC03641.png to img/AC03641.png
      2025-09-18 17:59:59.776 - info: zigbee.0 (742748) downloading https://www.zigbee2mqtt.io/images/devices/WSDCGQ01LM.png to img/WSDCGQ01LM.png
      2025-09-18 17:59:59.782 - info: zigbee.0 (742748) downloading https://www.zigbee2mqtt.io/images/devices/RTCGQ11LM.png to img/RTCGQ11LM.png
      2025-09-18 17:59:59.786 - info: zigbee.0 (742748) downloading https://www.zigbee2mqtt.io/images/devices/E2112.png to img/E2112.png
      2025-09-18 17:59:59.792 - info: zigbee.0 (742748) downloading https://www.zigbee2mqtt.io/images/devices/E1743.png to img/E1743.png
      2025-09-18 17:59:59.848 - info: zigbee.0 (742748) downloading https://www.zigbee2mqtt.io/images/devices/9290030675.png to img/9290030675.png
      2025-09-18 17:59:59.853 - info: zigbee.0 (742748) downloading https://www.zigbee2mqtt.io/images/devices/LED1836G9.png to img/LED1836G9.png
      2025-09-18 17:59:59.900 - info: zigbee.0 (742748) downloading https://www.zigbee2mqtt.io/images/devices/LED1835C6.png to img/LED1835C6.png
      2025-09-18 17:59:59.904 - info: zigbee.0 (742748) downloading https://www.zigbee2mqtt.io/images/devices/ZNCZ04LM.png to img/ZNCZ04LM.png
      2025-09-18 17:59:59.910 - info: zigbee.0 (742748) downloading https://www.zigbee2mqtt.io/images/devices/SSM-U01.png to img/SSM-U01.png
      2025-09-18 17:59:59.913 - info: zigbee.0 (742748) downloading https://www.zigbee2mqtt.io/images/devices/ZY-M100-S_2.png to img/ZY-M100-S_2.png
      2025-09-18 17:59:59.917 - info: zigbee.0 (742748) downloading https://www.zigbee2mqtt.io/images/devices/A1Z.png to img/A1Z.png
      2025-09-18 17:59:59.921 - info: zigbee.0 (742748) downloading https://www.zigbee2mqtt.io/images/devices/ZBMINI.png to img/ZBMINI.png
      2025-09-18 17:59:59.924 - info: zigbee.0 (742748) downloading https://www.zigbee2mqtt.io/images/devices/WSDCGQ11LM.png to img/WSDCGQ11LM.png
      2025-09-18 17:59:59.926 - info: zigbee.0 (742748) downloading https://www.zigbee2mqtt.io/images/devices/SM-0306E-2W.png to img/SM-0306E-2W.png
      2025-09-18 17:59:59.928 - info: zigbee.0 (742748) downloading https://www.zigbee2mqtt.io/images/devices/ZY-M100-S_1.png to img/ZY-M100-S_1.png
      2025-09-18 17:59:59.932 - info: zigbee.0 (742748) downloading https://www.zigbee2mqtt.io/images/devices/ZSS-HM-SSD01.png to img/ZSS-HM-SSD01.png
      2025-09-18 17:59:59.935 - info: zigbee.0 (742748) downloading https://www.zigbee2mqtt.io/images/devices/HS1SA.png to img/HS1SA.png
      2025-09-18 17:59:59.938 - info: zigbee.0 (742748) downloading https://www.zigbee2mqtt.io/images/devices/E1743.png to img/E1743.png
      2025-09-18 17:59:59.940 - info: zigbee.0 (742748) downloading https://www.zigbee2mqtt.io/images/devices/E22x4.png to img/E22x4.png
      2025-09-18 17:59:59.943 - info: zigbee.0 (742748) downloading https://www.zigbee2mqtt.io/images/devices/RS-226.png to img/RS 226.png
      2025-09-18 17:59:59.947 - info: zigbee.0 (742748) downloading https://www.zigbee2mqtt.io/images/devices/LED2104R3.png to img/LED2104R3.png
      2025-09-18 17:59:59.951 - info: zigbee.0 (742748) downloading https://www.zigbee2mqtt.io/images/devices/ZY-M100-24G.png to img/ZY-M100-24G.png
      2025-09-18 17:59:59.957 - info: zigbee.0 (742748) downloading https://www.zigbee2mqtt.io/images/devices/E2201.png to img/E2201.png
      2025-09-18 17:59:59.959 - info: zigbee.0 (742748) downloading https://www.zigbee2mqtt.io/images/devices/ZG-223Z.png to img/ZG-223Z.png
      2025-09-18 18:00:00.527 - info: zigbee.0 (742748) downloaded https://www.zigbee2mqtt.io/images/devices/E1743.png to img/E1743.png.
      2025-09-18 18:00:00.540 - info: zigbee.0 (742748) downloaded https://www.zigbee2mqtt.io/images/devices/AC03641.png to img/AC03641.png.
      2025-09-18 18:00:00.540 - info: zigbee.0 (742748) downloaded https://www.zigbee2mqtt.io/images/devices/LED1835C6.png to img/LED1835C6.png.
      2025-09-18 18:00:00.969 - info: zigbee.0 (742748) downloaded https://www.zigbee2mqtt.io/images/devices/SSM-U01.png to img/SSM-U01.png.
      2025-09-18 18:00:00.969 - info: zigbee.0 (742748) downloaded https://www.zigbee2mqtt.io/images/devices/RS-226.png to img/RS 226.png.
      2025-09-18 18:00:00.969 - info: zigbee.0 (742748) downloaded https://www.zigbee2mqtt.io/images/devices/E1743.png to img/E1743.png.
      2025-09-18 18:00:01.711 - info: zigbee.0 (742748) Failed to ping 0x60a423fffef481d4 TRADFRI bulb E27 WW 806lm for {"failed":1,"reported":0} attempts
      2025-09-18 18:00:01.714 - info: zigbee.0 (742748) DeviceConfigureQueue configuring 0xa4c138421ad10f21 TS0601
      2025-09-18 18:00:01.714 - info: zigbee.0 (742748) Configuring 0xa4c138421ad10f21 ZSS-HM-SSD01
      2025-09-18 18:00:02.124 - info: zigbee.0 (742748) Failed to ping 0xbc33acfffe2b5348 TRADFRI bulb E14 WS 470lm for {"failed":1,"reported":0} attempts
      2025-09-18 18:00:02.655 - info: zigbee.0 (742748) downloaded https://www.zigbee2mqtt.io/images/devices/WSDCGQ01LM.png to img/WSDCGQ01LM.png.
      2025-09-18 18:00:02.664 - info: zigbee.0 (742748) downloaded https://www.zigbee2mqtt.io/images/devices/RTCGQ11LM.png to img/RTCGQ11LM.png.
      2025-09-18 18:00:02.664 - info: zigbee.0 (742748) downloaded https://www.zigbee2mqtt.io/images/devices/MCCGQ11LM.png to img/MCCGQ11LM.png.
      2025-09-18 18:00:02.664 - info: zigbee.0 (742748) downloaded https://www.zigbee2mqtt.io/images/devices/ZBMINI.png to img/ZBMINI.png.
      2025-09-18 18:00:02.664 - info: zigbee.0 (742748) downloaded https://www.zigbee2mqtt.io/images/devices/ZY-M100-S_2.png to img/ZY-M100-S_2.png.
      2025-09-18 18:00:02.664 - info: zigbee.0 (742748) downloaded https://www.zigbee2mqtt.io/images/devices/A1Z.png to img/A1Z.png.
      2025-09-18 18:00:02.664 - info: zigbee.0 (742748) downloaded https://www.zigbee2mqtt.io/images/devices/WSDCGQ11LM.png to img/WSDCGQ11LM.png.
      2025-09-18 18:00:02.664 - info: zigbee.0 (742748) downloaded https://www.zigbee2mqtt.io/images/devices/E22x4.png to img/E22x4.png.
      2025-09-18 18:00:02.664 - info: zigbee.0 (742748) downloaded https://www.zigbee2mqtt.io/images/devices/E2201.png to img/E2201.png.
      2025-09-18 18:00:02.664 - info: zigbee.0 (742748) downloaded https://www.zigbee2mqtt.io/images/devices/9290030675.png to img/9290030675.png.
      2025-09-18 18:00:02.664 - info: zigbee.0 (742748) downloaded https://www.zigbee2mqtt.io/images/devices/ZY-M100-24G.png to img/ZY-M100-24G.png.
      2025-09-18 18:00:02.745 - info: zigbee.0 (742748) downloaded https://www.zigbee2mqtt.io/images/devices/HS1SA.png to img/HS1SA.png.
      2025-09-18 18:00:02.745 - info: zigbee.0 (742748) downloaded https://www.zigbee2mqtt.io/images/devices/SM-0306E-2W.png to img/SM-0306E-2W.png.
      2025-09-18 18:00:02.745 - info: zigbee.0 (742748) downloaded https://www.zigbee2mqtt.io/images/devices/LED1836G9.png to img/LED1836G9.png.
      2025-09-18 18:00:02.745 - info: zigbee.0 (742748) downloaded https://www.zigbee2mqtt.io/images/devices/ZNCZ04LM.png to img/ZNCZ04LM.png.
      2025-09-18 18:00:02.745 - info: zigbee.0 (742748) downloaded https://www.zigbee2mqtt.io/images/devices/E2112.png to img/E2112.png.
      2025-09-18 18:00:02.746 - info: zigbee.0 (742748) downloaded https://www.zigbee2mqtt.io/images/devices/ZY-M100-S_1.png to img/ZY-M100-S_1.png.
      2025-09-18 18:00:02.746 - info: zigbee.0 (742748) downloaded https://www.zigbee2mqtt.io/images/devices/ZSS-HM-SSD01.png to img/ZSS-HM-SSD01.png.
      2025-09-18 18:00:02.746 - info: zigbee.0 (742748) downloaded https://www.zigbee2mqtt.io/images/devices/ZG-223Z.png to img/ZG-223Z.png.
      2025-09-18 18:00:02.844 - info: zigbee.0 (742748) downloaded https://www.zigbee2mqtt.io/images/devices/LED2104R3.png to img/LED2104R3.png.
      2025-09-18 18:00:05.310 - info: zigbee.0 (742748) Failed to ping 0x04cf8cdf3c8a28b4 lumi.plug.mmeu01 for {"failed":1,"reported":0} attempts
      2025-09-18 18:00:06.715 - info: zigbee.0 (742748) DeviceConfigureQueue configuring 0x54ef441000b4c59f lumi.switch.n0agl1
      2025-09-18 18:00:06.715 - info: zigbee.0 (742748) Configuring 0x54ef441000b4c59f SSM-U01
      2025-09-18 18:00:09.082 - info: zigbee.0 (742748) Failed to ping 0xa4c138528cff8d70 TS0601 for {"failed":1,"reported":0} attempts
      2025-09-18 18:00:11.715 - info: zigbee.0 (742748) Handled all devices Queued for configuration.
      2025-09-18 18:00:11.753 - info: zigbee.0 (742748) Failed to ping 0x980c33fffea346f4 TRADFRI bulb GU10 WW 345lm for {"failed":1,"reported":0} attempts
      2025-09-18 18:00:11.803 - warn: zigbee.0 (742748) DeviceConfigure:0xa4c138421ad10f21 TS0601 Failed to configure. --> ZCL command 0xa4c138421ad10f21/1 genBasic.read(["manufacturerName","zclVersion","appVersion","modelId","powerSource",65534], {"timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":true,"direction":0,"reservedBits":0,"writeUndiv":false}) failed (--> 'SREQ: ZDO - extRouteDisc - {"dstAddr":794,"options":0,"radius":30}' failed with status '(0xc7: NWK_TABLE_FULL)' (expected '(0x00: SUCCESS)'))
      2025-09-18 18:00:11.892 - info: zigbee.0 (742748) Failed to ping 0x60a423fffe88b17c RS 226 for {"failed":1,"reported":0} attempts
      2025-09-18 18:00:12.254 - info: zigbee.0 (742748) Failed to ping 0x881a14fffe18af9a TRETAKT Smart plug for {"failed":1,"reported":0} attempts
      2025-09-18 18:00:12.278 - info: zigbee.0 (742748) Failed to ping 0x60a423fffe88a159 RS 226 for {"failed":1,"reported":0} attempts
      2025-09-18 18:00:12.754 - info: zigbee.0 (742748) Failed to ping 0x8c6fb9fffe268ee2 TRETAKT Smart plug for {"failed":1,"reported":0} attempts
      2025-09-18 18:00:12.837 - info: zigbee.0 (742748) Failed to ping 0x60a423fffe88b2f8 RS 226 for {"failed":1,"reported":0} attempts
      2025-09-18 18:00:16.776 - info: zigbee.0 (742748) Timeout trying to configure 0x54ef441000b4c59f SSM-U01 (starting CoM).
      2025-09-18 18:00:18.081 - info: zigbee.0 (742748) Failed to ping 0x54ef441000b4c59f lumi.switch.n0agl1 for {"failed":1,"reported":0} attempts
      2025-09-18 18:02:04.111 - info: zigbee.0 (742748) List of port: [{"path":"/dev/ttyS0"},{"path":"/dev/ttyS1"},{"path":"/dev/ttyS2"},{"path":"/dev/ttyS3"}]
      2025-09-18 18:02:04.335 - warn: zigbee.0 (742748) Resolve Entity did not manage to find a mapped device for [object Object]
      2025-09-18 18:02:37.041 - warn: zigbee.0 (742748) resolve_entity failed for {"kind":"ieee","key":"0x0x00124b0018eb432d","message":"success"}
      2025-09-18 18:02:37.042 - info: zigbee.0 (742748) Device 0x00124b0018eb432d is unavailable
      2025-09-18 18:02:37.099 - info: zigbee.0 (742748) Device zigbee.0.04cf8cdf3c8a28b4 is marked unavailable, skipping...
      2025-09-18 18:02:37.100 - info: zigbee.0 (742748) Device zigbee.0.60a423fffef481d4 is marked unavailable, skipping...
      2025-09-18 18:02:37.100 - info: zigbee.0 (742748) Device zigbee.0.bc33acfffe2b5348 is marked unavailable, skipping...
      2025-09-18 18:02:37.104 - info: zigbee.0 (742748) Device zigbee.0.a4c138528cff8d70 is marked unavailable, skipping...
      2025-09-18 18:02:37.151 - info: zigbee.0 (742748) Device zigbee.0.54ef441000b4c59f is marked unavailable, skipping...
      2025-09-18 18:02:37.153 - info: zigbee.0 (742748) Device zigbee.0.60a423fffe88b17c is marked unavailable, skipping...
      2025-09-18 18:02:37.153 - info: zigbee.0 (742748) Device zigbee.0.60a423fffe88a159 is marked unavailable, skipping...
      2025-09-18 18:02:37.153 - info: zigbee.0 (742748) Device zigbee.0.60a423fffe88b2f8 is marked unavailable, skipping...
      2025-09-18 18:02:37.155 - info: zigbee.0 (742748) Device zigbee.0.980c33fffea346f4 is marked unavailable, skipping...
      2025-09-18 18:02:37.155 - info: zigbee.0 (742748) Device zigbee.0.881a14fffe18af9a is marked unavailable, skipping...
      2025-09-18 18:02:37.155 - info: zigbee.0 (742748) Device zigbee.0.8c6fb9fffe268ee2 is marked unavailable, skipping...
      2025-09-18 18:03:19.845 - warn: zigbee.0 (742748) Failed to check if update available for '0x4c5bb3fffe9fd6fc' Device didn't respond to OTA request
      2025-09-18 18:03:37.153 - warn: zigbee.0 (742748) Failed to check if update available for '0x60a423fffeeedaf3' Device didn't respond to OTA request
      2025-09-18 18:03:37.153 - warn: zigbee.0 (742748) Failed to check if update available for '0x60a423fffee55619' Device didn't respond to OTA request
      2025-09-18 18:03:37.153 - warn: zigbee.0 (742748) Failed to check if update available for '0x001788010bd00a89' Device didn't respond to OTA request
      2025-09-18 18:03:37.154 - warn: zigbee.0 (742748) Failed to check if update available for '0x60a423fffeed6f44' Device didn't respond to OTA request
      2025-09-18 18:03:37.159 - warn: zigbee.0 (742748) Failed to check if update available for '0xc4d8c8fffe8a3c92' Device didn't respond to OTA request
      2025-09-18 18:20:32.990 - info: zigbee.0 (742748) List of port: [{"path":"/dev/ttyS0"},{"path":"/dev/ttyS1"},{"path":"/dev/ttyS2"},{"path":"/dev/ttyS3"}]
      2025-09-18 18:20:33.064 - warn: zigbee.0 (742748) Resolve Entity did not manage to find a mapped device for [object Object]
      

      Der Moes Rauchmelder wird mit warn erwähnt:

      2025-09-18 18:00:11.803 - warn: zigbee.0 (742748) DeviceConfigure:0xa4c138421ad10f21 TS0601 Failed to configure. --> ZCL command 0xa4c138421ad10f21/1 genBasic.read(["manufacturerName","zclVersion","appVersion","modelId","powerSource",65534], {"timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":true,"direction":0,"reservedBits":0,"writeUndiv":false}) failed (--> 'SREQ: ZDO - extRouteDisc - {"dstAddr":794,"options":0,"radius":30}' failed with status '(0xc7: NWK_TABLE_FULL)' (expected '(0x00: SUCCESS)'))
      
      

      und folgende Meldung kommt mehrfach:

      2025-09-18 18:20:33.064 - warn: zigbee.0 (742748) Resolve Entity did not manage to find a mapped device for [object Object]
      
      

      Bei der Meldung

      2025-09-18 18:02:37.041 - warn: zigbee.0 (742748) resolve_entity failed for {"kind":"ieee","key":"0x0x00124b0018eb432d","message":"success"}
      
      

      verstehe ich die Adresse 0x0x00124b0018eb432d nicht, hab ich nicht in meinen Objekten.

      Muss ich mir Gedanken darüber machen?

      Asgothian 1 Reply Last reply Reply Quote 0
      • Asgothian
        Asgothian Developer @Latzi last edited by

        @latzi sagte in Tester wanted - Zigbee Adapter 3.1:

        @asgothian
        ich hab auf 3.1.2 (von 3.0.5) umgestellt, folgende Meldungen kamen:

        Der Moes Rauchmelder wird mit warn erwähnt:

        2025-09-18 18:00:11.803 - warn: zigbee.0 (742748) DeviceConfigure:0xa4c138421ad10f21 TS0601 Failed to configure. --> ZCL command 0xa4c138421ad10f21/1 genBasic.read(["manufacturerName","zclVersion","appVersion","modelId","powerSource",65534], {"timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":true,"direction":0,"reservedBits":0,"writeUndiv":false}) failed (--> 'SREQ: ZDO - extRouteDisc - {"dstAddr":794,"options":0,"radius":30}' failed with status '(0xc7: NWK_TABLE_FULL)' (expected '(0x00: SUCCESS)'))
        
        

        und folgende Meldung kommt mehrfach:

        2025-09-18 18:20:33.064 - warn: zigbee.0 (742748) Resolve Entity did not manage to find a mapped device for [object Object]
        
        

        Bei der Meldung

        2025-09-18 18:02:37.041 - warn: zigbee.0 (742748) resolve_entity failed for {"kind":"ieee","key":"0x0x00124b0018eb432d","message":"success"}
        
        

        verstehe ich die Adresse 0x0x00124b0018eb432d nicht, hab ich nicht in meinen Objekten.

        Muss ich mir Gedanken darüber machen?

        Die beiden Meldungen sind erst einmal egal - die Addresse ist die deines Koordinators.

        Schlechter ist das Ergebnis '(0xc7: NWK_TABLE_FULL)'. es bedeutet das du zuviel traffic im Zigbee Netz hast. Lass das Netz erst einmal zur Ruhe kommen (30 Minuten) und versuch dann den Rauchmelder neu zu konfigurieren

        A.

        1 Reply Last reply Reply Quote 1
        • F
          Flugschüler last edited by

          Ich habe einen tuya 2CT Energiezähler. Mit ZigBee adapter 3.1.2 werden die datenpunkte power_a und power_b nicht aktualisiert.

          Asgothian 1 Reply Last reply Reply Quote 0
          • Asgothian
            Asgothian Developer @Flugschüler last edited by

            @flugschüler sagte in Tester wanted - Zigbee Adapter 3.1:

            Ich habe einen tuya 2CT Energiezähler. Mit ZigBee adapter 3.1.2 werden die datenpunkte power_a und power_b nicht aktualisiert.

            Schritt 1: Gerät über die Kachel neu konfigurieren. Entweder es geht danach oder nicht.

            Wenn nicht: Schritt 2

            Bitte folgendes machen (mit der 3.0.1 installiert)

            • Debug für dein betroffenes Gerät aktivieren
            • Warten bis die gewünschten Datenpunkte aktualisiert werden.
            • Im Log nach 'ELEVATED (abcd)' Warn-Meldungen schauen. Diese hier Posten. Dabei bitte die Meldungen nicht rein chronologisch sondern sortiert nach der 4-Stelligen Hex Zahl in Gruppen posten (Als Text, in Code Tags, in einzelnen Gruppen mit jeweils nur einer ID)
            • Adapter anhalten
            • Adapter auf 3.1.2 aktualisieren
            • Adapter starten
            • Wieder nach den 'ELEVATED' Nachrichten schauen - Wichtig ist das dabei hinreichend Zeit vergeht das die Datenpunkte aktualisiert sein sollte. Diese wieder wie oben gruppiert als Text in Code-Tags posten.
            • device_query triggern
            • Wieder nach neuen 'ELEVATED' Nachrichten schauen.
            • Diese wieder wie oben gruppiert als Text in Code-Tags posten.
            • Gerät über die Kachel neu konfigurieren
            • Abwarten ob load_power aktualisiert wird.
            • Wieder nach neuen 'ELEVATED' Nachrichten schauen - Wichtig ist das dabei hinreichend Zeit vergeht das Load_Power aktualisiert sein sollte. Diese wieder wie oben gruppiert als Text in Code-Tags posten.

            Bitte stell sicher das die Logs korrekt in Multiline Code tags gekapselt sind. Ansonsten sind sie unleserlich.

            Da ich keine entsprechendes Gerät habe kann ich diesem Effekt ohne diese Daten nicht nachgehen. Ich kann den Effekt nicht nachstellen.

            A.

            Beispiel für korrekt formatierte und sortierte Log Meldungen:

            warn: zigbee.0 (534432) ELEVATED:O01 (e57d) User state change of state zigbee.0.187a3efffe39a49e.send_payload with value { "cyclic_timed_irrigation": { "total_number": 1, "irrigation_duration": 60 } } (ack: false) from system.adapter.scenes.0
            warn: zigbee.0 (534432) ELEVATED:O02 (e57d) Change state 'send_payload' at device 0x187a3efffe39a49e type 'SWV'
            warn: zigbee.0 (534432) ELEVATED:O03 (e57d) Publishing to 0x187a3efffe39a49e of model SWV with send_payload
            
            warn: zigbee.0 (534432) ELEVATED:O03 (e5a8) Publishing to 0x187a3efffe39a49e of model SWV with cyclic_timed_irrigation
            warn: zigbee.0 (534432) ELEVATED:O04 (e5a8) convert cyclic_timed_irrigation, {"total_number":1,"irrigation_duration":60}, {} for device 0x187a3efffe39a49e with Endpoint cyclic_timed_irrigation
            warn: zigbee.0 (534432) ELEVATED:SUCCESS (e5a8) convert result {"state":{"cyclic_timed_irrigation":{"total_number":1,"irrigation_duration":60}}} for device 0x187a3efffe39a49e
            
            warn: zigbee.0 (534432) ELEVATED:I01 (eb01) Zigbee Event of Type attributeReport from device 0x187a3efffe39a49e, incoming event: {"type":"attributeReport","data":{"20489":"\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000"},"linkquality":36,"groupID":0,"cluster":"customClusterEwelink","meta":{"zclTransactionSequenceNumber":125,"frameControl":{"frameType":0,"manufacturerSpecific":false,"direction":1,"disableDefaultResponse":false,"reservedBits":0}},"endpoint_id":1}
            warn: zigbee.0 (534432) ELEVATED:I01 (eb01) message received '{"linkquality":36}' from device 187a3efffe39a49e type 'SWV'
            warn: zigbee.0 (534432) ELEVATED:I02 (eb01) value generated '36' from device 187a3efffe39a49e for 'Link quality'
            
            warn: zigbee.0 (534432) ELEVATED:I01 (eb18) Zigbee Event of Type attributeReport from device 0x187a3efffe39a49e, incoming event: {"type":"attributeReport","data":{"20488":"\u0001\u0001\u0000\u0000\u0000<\u0000\u0000\u0000\u0000"},"linkquality":36,"groupID":0,"cluster":"customClusterEwelink","meta":{"zclTransactionSequenceNumber":126,"frameControl":{"frameType":0,"manufacturerSpecific":false,"direction":1,"disableDefaultResponse":false,"reservedBits":0}},"endpoint_id":1}
            
            warn: zigbee.0 (534432) ELEVATED:I01 (eb20) Zigbee Event of Type attributeReport from device 0x187a3efffe39a49e, incoming event: {"type":"attributeReport","data":{"20486":0,"20487":0,"20493":1758225028,"20496":1},"linkquality":36,"groupID":0,"cluster":"customClusterEwelink","meta":{"zclTransactionSequenceNumber":0,"frameControl":{"frameType":0,"manufacturerSpecific":false,"direction":1,"disableDefaultResponse":false,"reservedBits":0}},"endpoint_id":1}
            
            F 2 Replies Last reply Reply Quote 0
            • F
              Flugschüler @Asgothian last edited by Flugschüler

              ELEVATED:I01 (eb06) message received '{"linkquality":72}' from device a4c13886e50d0115 type '2CT'
              ELEVATED:I02 (eb06) value generated '72' from device a4c13886e50d0115 for 'Link quality'
              ELEVATED:I01 (eb06) message received '{"power":0}' from device a4c13886e50d0115 type '2CT'
              ELEVATED:I02 (eb06) value generated '0' from device a4c13886e50d0115 for 'Load power'
              
              ELEVATED:I01 (eb30) message received '{"linkquality":72}' from device a4c13886e50d0115 type '2CT'
              ELEVATED:I02 (eb30) value generated '72' from device a4c13886e50d0115 for 'Link quality'
              ELEVATED:I01 (eb30) message received '{"current_a":0}' from device a4c13886e50d0115 type '2CT'
              ELEVATED:I02 (eb30) value generated '0' from device a4c13886e50d0115 for 'Instantaneous measured electrical current (phase A)'
              
              ELEVATED:I01 (eb59) message received '{"linkquality":69}' from device a4c13886e50d0115 type '2CT'
              ELEVATED:I02 (eb59) value generated '69' from device a4c13886e50d0115 for 'Link quality'
              ELEVATED:I01 (eb59) message received '{"current_b":0}' from device a4c13886e50d0115 type '2CT'
              ELEVATED:I02 (eb59) value generated '0' from device a4c13886e50d0115 for 'Instantaneous measured electrical current (phase B)'
              ELEVATED:I01 (eb59) Zigbee Event of Type commandDataReport from device 0xa4c13886e50d0115, incoming event: {"type":"commandDataReport","data":{"seq":37120,"dpValues":[{"dp":102,"datatype":2,"data":{"type":"Buffer","data":[0,0,0,0]}}]}...}
              
              ELEVATED:I01 (eb83) message received '{"linkquality":69}' from device a4c13886e50d0115 type '2CT'
              ELEVATED:I02 (eb83) value generated '69' from device a4c13886e50d0115 for 'Link quality'
              ELEVATED:I01 (eb83) message received '{"power_a":0}' from device a4c13886e50d0115 type '2CT'
              ELEVATED:I02 (eb83) value generated '0' from device a4c13886e50d0115 for 'Instantaneous measured power (phase A)'
              ELEVATED:I01 (eb83) Zigbee Event of Type commandDataReport from device 0xa4c13886e50d0115, incoming event: {"type":"commandDataReport","data":{"seq":37376,"dpValues":[{"dp":103,"datatype":2,"data":{"type":"Buffer","data":[0,0,0,0]}}]}...}
              
              ELEVATED:I01 (ebad) message received '{"linkquality":69}' from device a4c13886e50d0115 type '2CT'
              ELEVATED:I02 (ebad) value generated '69' from device a4c13886e50d0115 for 'Link quality'
              ELEVATED:I01 (ebad) message received '{"power_b":0}' from device a4c13886e50d0115 type '2CT'
              ELEVATED:I02 (ebad) value generated '0' from device a4c13886e50d0115 for 'Instantaneous measured power (phase B)'
              ELEVATED:I01 (ebad) Zigbee Event of Type commandDataReport from device 0xa4c13886e50d0115, incoming event: {"type":"commandDataReport","data":{"seq":37632,"dpValues":[{"dp":104,"datatype":2,"data":{"type":"Buffer","data":[0,0,0,0]}}]}...}
              
              ELEVATED:I01 (ebd5) message received '{"linkquality":69}' from device a4c13886e50d0115 type '2CT'
              ELEVATED:I02 (ebd5) value generated '69' from device a4c13886e50d0115 for 'Link quality'
              ELEVATED:I01 (ebd5) message received '{}' from device a4c13886e50d0115 type '2CT'
              ELEVATED:NOVAL (ebd5) No value published for device a4c13886e50d0115
              ELEVATED:I01 (ebd5) Zigbee Event of Type commandDataReport from device 0xa4c13886e50d0115, incoming event: {"type":"commandDataReport","data":{"seq":37888,"dpValues":[{"dp":141,"datatype":4,"data":{"type":"Buffer","data":[0]}}]}...}
              
              ELEVATED:I01 (ebff) message received '{"linkquality":69}' from device a4c13886e50d0115 type '2CT'
              ELEVATED:I02 (ebff) value generated '69' from device a4c13886e50d0115 for 'Link quality'
              ELEVATED:I01 (ebff) message received '{}' from device a4c13886e50d0115 type '2CT'
              ELEVATED:NOVAL (ebff) No value published for device a4c13886e50d0115
              ELEVATED:I01 (ebff) Zigbee Event of Type commandDataReport from device 0xa4c13886e50d0115, incoming event: {"type":"commandDataReport","data":{"seq":38144,"dpValues":[{"dp":142,"datatype":4,"data":{"type":"Buffer","data":[0]}}]}...}
              
              1 Reply Last reply Reply Quote 0
              • F
                Flugschüler @Asgothian last edited by Flugschüler

                @asgothian Ist das so richtig? Dann sende ich die daten vom neuen zigbee adapter.

                ELEVATED:I01 (1430) message received '{"linkquality":72}' from device a4c13886e50d0115 type '2CT'
                ELEVATED:I02 (1430) value generated '72' from device a4c13886e50d0115 for 'Link quality'
                ELEVATED:I01 (1430) Zigbee Event of Type commandDataReport from device 0xa4c13886e50d0115, incoming event: {"type":"commandDataReport","data":{"seq":31744,"dpValues":[{"dp":19,"datatype":2,"data":{"type":"Buffer","data":[0,0,0,0]}}]}...}
                
                ELEVATED:I01 (145b) message received '{"linkquality":69}' from device a4c13886e50d0115 type '2CT'
                ELEVATED:I02 (145b) value generated '69' from device a4c13886e50d0115 for 'Link quality'
                ELEVATED:I01 (145b) Zigbee Event of Type commandDataReport from device 0xa4c13886e50d0115, incoming event: {"type":"commandDataReport","data":{"seq":32000,"dpValues":[{"dp":101,"datatype":2,"data":{"type":"Buffer","data":[0,0,0,0]}}]}...}
                
                ELEVATED:I01 (1495) message received '{"linkquality":72}' from device a4c13886e50d0115 type '2CT'
                ELEVATED:I02 (1495) value generated '72' from device a4c13886e50d0115 for 'Link quality'
                ELEVATED:I01 (1495) Zigbee Event of Type commandDataReport from device 0xa4c13886e50d0115, incoming event: {"type":"commandDataReport","data":{"seq":32256,"dpValues":[{"dp":102,"datatype":2,"data":{"type":"Buffer","data":[0,0,0,0]}}]}...}
                
                ELEVATED:I01 (14c3) message received '{"linkquality":69}' from device a4c13886e50d0115 type '2CT'
                ELEVATED:I02 (14c3) value generated '69' from device a4c13886e50d0115 for 'Link quality'
                ELEVATED:I01 (14c3) Zigbee Event of Type commandDataReport from device 0xa4c13886e50d0115, incoming event: {"type":"commandDataReport","data":{"seq":32512,"dpValues":[{"dp":103,"datatype":2,"data":{"type":"Buffer","data":[0,0,0,0]}}]}...}
                
                ELEVATED:I01 (14f4) message received '{"linkquality":72}' from device a4c13886e50d0115 type '2CT'
                ELEVATED:I02 (14f4) value generated '72' from device a4c13886e50d0115 for 'Link quality'
                ELEVATED:I01 (14f4) Zigbee Event of Type commandDataReport from device 0xa4c13886e50d0115, incoming event: {"type":"commandDataReport","data":{"seq":32768,"dpValues":[{"dp":104,"datatype":2,"data":{"type":"Buffer","data":[0,0,0,0]}}]}...}
                
                ELEVATED:I01 (151f) message received '{"linkquality":72}' from device a4c13886e50d0115 type '2CT'
                ELEVATED:I02 (151f) value generated '72' from device a4c13886e50d0115 for 'Link quality'
                ELEVATED:I01 (151f) Zigbee Event of Type commandDataReport from device 0xa4c13886e50d0115, incoming event: {"type":"commandDataReport","data":{"seq":33024,"dpValues":[{"dp":141,"datatype":4,"data":{"type":"Buffer","data":[0]}}]}...}
                
                ELEVATED:I01 (154a) message received '{"linkquality":69}' from device a4c13886e50d0115 type '2CT'
                ELEVATED:I02 (154a) value generated '69' from device a4c13886e50d0115 for 'Link quality'
                ELEVATED:I01 (154a) Zigbee Event of Type commandDataReport from device 0xa4c13886e50d0115, incoming event: {"type":"commandDataReport","data":{"seq":33280,"dpValues":[{"dp":142,"datatype":4,"data":{"type":"Buffer","data":[0]}}]}...}
                
                Asgothian 1 Reply Last reply Reply Quote 0
                • Fabio
                  Fabio @Asgothian last edited by Fabio

                  Guten morgen @asgothian ,

                  weißt du was hier paasiert das hatte ich noch nie:

                  host.nuc
                  2025-09-19 07:50:54.252	info	Restart adapter system.adapter.zigbee.1 because enabled
                  
                  host.nuc
                  2025-09-19 07:50:54.252	error	instance system.adapter.zigbee.1 terminated with code 6 (UNCAUGHT_EXCEPTION)
                  
                  host.nuc
                  2025-09-19 07:50:54.252	error	Caught by controller[6]: allowing role change for color_hs.saturation
                  
                  host.nuc
                  2025-09-19 07:50:54.252	error	Caught by controller[6]: allowing role change for color_hs.hue
                  
                  host.nuc
                  2025-09-19 07:50:54.252	error	Caught by controller[6]: allowing role change for color_rgb.b
                  
                  host.nuc
                  2025-09-19 07:50:54.252	error	Caught by controller[6]: allowing role change for color_rgb.g
                  
                  host.nuc
                  2025-09-19 07:50:54.252	error	Caught by controller[6]: allowing role change for color_rgb.r
                  
                  host.nuc
                  2025-09-19 07:50:54.252	error	Caught by controller[6]: allowing role change for color_xy.y
                  
                  host.nuc
                  2025-09-19 07:50:54.252	error	Caught by controller[6]: allowing role change for color_xy.x
                  
                  host.nuc
                  2025-09-19 07:50:54.252	error	Caught by controller[6]: allowing role change for color
                  
                  host.nuc
                  2025-09-19 07:50:54.252	error	Caught by controller[6]: allowing role change for hex_color
                  
                  host.nuc
                  2025-09-19 07:50:54.252	error	Caught by controller[6]: allowing role change for colortemp_move
                  
                  host.nuc
                  2025-09-19 07:50:54.252	error	Caught by controller[6]: allowing role change for colortemp
                  
                  host.nuc
                  2025-09-19 07:50:54.252	error	Caught by controller[5]: at Groups.syncGroups (/opt/iobroker/node_modules/iobroker.zigbee/lib/groups.js:647:39)
                  
                  host.nuc
                  2025-09-19 07:50:54.252	error	Caught by controller[5]: TypeError: Cannot read properties of undefined (reading 'group_1')
                  
                  host.nuc
                  2025-09-19 07:50:54.252	error	Caught by controller[5]: This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason:
                  
                  host.nuc
                  2025-09-19 07:50:54.252	error	Caught by controller[4]: allowing role change for color_hs.saturation
                  
                  host.nuc
                  2025-09-19 07:50:54.252	error	Caught by controller[4]: allowing role change for color_hs.hue
                  
                  host.nuc
                  2025-09-19 07:50:54.252	error	Caught by controller[4]: allowing role change for color_rgb.b
                  
                  host.nuc
                  2025-09-19 07:50:54.252	error	Caught by controller[4]: allowing role change for color_rgb.g
                  
                  host.nuc
                  2025-09-19 07:50:54.252	error	Caught by controller[4]: allowing role change for color_rgb.r
                  
                  host.nuc
                  2025-09-19 07:50:54.252	error	Caught by controller[4]: allowing role change for color_xy.y
                  
                  host.nuc
                  2025-09-19 07:50:54.251	error	Caught by controller[4]: allowing role change for color_xy.x
                  
                  host.nuc
                  2025-09-19 07:50:54.251	error	Caught by controller[4]: allowing role change for color
                  
                  host.nuc
                  2025-09-19 07:50:54.251	error	Caught by controller[4]: allowing role change for hex_color
                  
                  host.nuc
                  2025-09-19 07:50:54.251	error	Caught by controller[4]: allowing role change for colortemp_move
                  
                  host.nuc
                  2025-09-19 07:50:54.251	error	Caught by controller[4]: allowing role change for colortemp
                  
                  host.nuc
                  2025-09-19 07:50:54.251	error	Caught by controller[3]: at Groups.syncGroups (/opt/iobroker/node_modules/iobroker.zigbee/lib/groups.js:649:56)
                  
                  host.nuc
                  2025-09-19 07:50:54.251	error	Caught by controller[3]: TypeError: Cannot set properties of undefined (setting 'stateupdate')
                  
                  host.nuc
                  2025-09-19 07:50:54.251	error	Caught by controller[3]: This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason:
                  
                  host.nuc
                  2025-09-19 07:50:54.251	error	Caught by controller[2]: [2025-09-19T05:50:51.203Z] zh:zstack:znp: Socket error Error: read ECONNRESET
                  
                  host.nuc
                  2025-09-19 07:50:54.251	error	Caught by controller[1]: [2025-09-19T05:50:51.202Z] zh:zstack:znp: Socket error Error: read ECONNRESET
                  
                  zigbee.1
                  2025-09-19 07:50:53.671	warn	Terminated (UNCAUGHT_EXCEPTION): Without reason
                  
                  zigbee.1
                  2025-09-19 07:50:52.915	info	Closing Zigbee network, 0 seconds remaining
                  
                  zigbee.1
                  2025-09-19 07:50:52.915	info	Closing Zigbee network, 0 seconds remaining
                  
                  zigbee.1
                  2025-09-19 07:50:52.915	info	Closing Zigbee network, 0 seconds remaining
                  
                  zigbee.1
                  2025-09-19 07:50:52.915	info	Closing Zigbee network, 0 seconds remaining
                  
                  zigbee.1
                  2025-09-19 07:50:52.915	info	Closing Zigbee network, 0 seconds remaining
                  
                  zigbee.1
                  2025-09-19 07:50:52.915	info	Closing Zigbee network, 0 seconds remaining
                  
                  zigbee.1
                  2025-09-19 07:50:52.854	error	Cannot read properties of undefined (reading 'group_1')
                  
                  zigbee.1
                  2025-09-19 07:50:52.854	error	TypeError: Cannot read properties of undefined (reading 'group_1') at Groups.syncGroups (/opt/iobroker/node_modules/iobroker.zigbee/lib/groups.js:647:39)
                  
                  zigbee.1
                  2025-09-19 07:50:52.854	error	unhandled promise rejection: Cannot read properties of undefined (reading 'group_1')
                  
                  zigbee.1
                  2025-09-19 07:50:52.854	error	Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().
                  
                  zigbee.1
                  2025-09-19 07:50:52.671	info	Saved local configuration data
                  
                  zigbee.1
                  2025-09-19 07:50:52.670	info	cleaning everything up...
                  
                  zigbee.1
                  2025-09-19 07:50:52.670	info	Halting zigbee adapter. Restart delay is at least 30 seconds.
                  
                  zigbee.1
                  2025-09-19 07:50:52.604	error	Cannot set properties of undefined (setting 'stateupdate')
                  
                  zigbee.1
                  2025-09-19 07:50:52.604	error	TypeError: Cannot set properties of undefined (setting 'stateupdate') at Groups.syncGroups (/opt/iobroker/node_modules/iobroker.zigbee/lib/groups.js:649:56)
                  
                  zigbee.1
                  2025-09-19 07:50:52.604	error	unhandled promise rejection: Cannot set properties of undefined (setting 'stateupdate')
                  
                  zigbee.1
                  2025-09-19 07:50:52.604	error	Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().
                  

                  fabio error zigbe.txt

                  Asgothian 1 Reply Last reply Reply Quote 0
                  • Asgothian
                    Asgothian Developer @Fabio last edited by Asgothian

                    @fabio Wahrscheinlich hast du nicht beachtet das der Adapter 30 Sekunden zwischen stop und start wartet.

                    Wenn man

                    • den Adapter anhält
                    • den Adapter sofort wieder startet
                    • und dann, weil er nicht sofort zu starten scheint das nochmal widerholt

                    dann passiert so etwas.

                    Ich hatte mal einen Issue dazu aufgemacht - den muss ich aber raus suchen. Das ist fast ein Jahr her, und es ist nichts passiert. Das Problem liegt im js-controller oder im Kern des ioBroker, der zwar zulässt das man eine Zeit definiert, diese aber auf der Oberfläche nicht visualisiert. Ebenso wartet er nicht nach dem Stop Befehl an den Adapter bis dieser auch wirklich angehalten ist. Da gibt es einen internen Timeout, der auch dann den Adapter als gestoppt anzeigt wenn dieser den Stop-Befehl noch bearbeitet.

                    Betroffen ist der Zigbee Adapter davon, weil es insbesondere bei den LAN Koordinatoren teilweise bis zu 30 s dauert bis der Adapter angehalten wurde, weil Daten vom Koordinator abgefragt werden.

                    A.

                    Fabio 1 Reply Last reply Reply Quote 1
                    • Fabio
                      Fabio @Asgothian last edited by

                      @asgothian lieben Dank für die Info.

                      Aber ich habe den Adapter weder gestoppt noch gestartet das lief alles von alleine. Und das hatte ich so vor der Version 3.1.2 noch nie.

                      Herzliche Grüße
                      Fabio

                      Asgothian 1 Reply Last reply Reply Quote 0
                      • Asgothian
                        Asgothian Developer @Flugschüler last edited by

                        @flugschüler sagte in Tester wanted - Zigbee Adapter 3.1:

                        Ist das so richtig? Dann sende ich die daten vom neuen zigbee adapter.

                        Fast - was ich nicht erkennen kann: welche der Meldungen sind die Reaktionen auf ein 'Device Query', insbesondere beim neuen Adapter.

                        A.

                        F 1 Reply Last reply Reply Quote 0
                        • Asgothian
                          Asgothian Developer @Fabio last edited by

                          @fabio sagte in Tester wanted - Zigbee Adapter 3.1:

                          @asgothian lieben Dank für die Info.

                          Aber ich habe den Adapter weder gestoppt noch gestartet das lief alles von alleine. Und das hatte ich so vor der Version 3.1.2 noch nie.

                          Herzliche Grüße
                          Fabio

                          Wer den Adapter neu gestartet hat kann ich Dir nicht sagen. Das log zeigt deutlich das die Instanz zigbee.1 das Zigbee Netzwerk 2 mal startet.

                          Das wäre zu beobachten. So einen Effekt hatte ich bei mir bisher nie.

                          A.

                          1 Reply Last reply Reply Quote 1
                          • F
                            Flugschüler @Asgothian last edited by

                            @asgothian

                            ELEVATED:I01 (1fea) message received '{"linkquality":76}' from device a4c13886e50d0115 type '2CT'
                            ELEVATED:I02 (1fea) value generated '76' from device a4c13886e50d0115 for 'Link quality'
                            
                            ELEVATED:O01 (24b0) User state change of state zigbee.0.a4c13886e50d0115.device_query with value true (ack: false) from system.adapter.admin.0  
                            ELEVATED:O02 (24b0) Change state 'device_query' at device 0xa4c13886e50d0115 type '2CT'  
                            ELEVATED:Oqs (24b0) Device query for '0xa4c13886e50d0115/1' triggered  
                            ELEVATED:Oqe (24b0) ELEVATED O07: Device query for '0xa4c13886e50d0115/1' complete  
                            
                            ELEVATED:I01 (34df) message received '{"linkquality":80}' from device a4c13886e50d0115 type '2CT'
                            ELEVATED:I02 (34df) value generated '80' from device a4c13886e50d0115 for 'Link quality'
                            ELEVATED:I01 (34df) Zigbee Event of Type commandDataReport from device 0xa4c13886e50d0115, incoming event: {"type":"commandDataReport","data":{"seq":10240,"dpValues":[{"dp":20,"datatype":2,"data":{"type":"Buffer","data":[0,0,8,166]}}]}...}
                            
                            ELEVATED:I01 (3516) message received '{"linkquality":72}' from device a4c13886e50d0115 type '2CT'
                            ELEVATED:I02 (3516) value generated '72' from device a4c13886e50d0115 for 'Link quality'
                            ELEVATED:I01 (3516) Zigbee Event of Type commandDataReport from device 0xa4c13886e50d0115, incoming event: {"type":"commandDataReport","data":{"seq":10496,"dpValues":[{"dp":19,"datatype":2,"data":{"type":"Buffer","data":[0,0,18,226]}}]}...}
                            
                            ELEVATED:I01 (354e) message received '{"linkquality":80}' from device a4c13886e50d0115 type '2CT'
                            ELEVATED:I02 (354e) value generated '80' from device a4c13886e50d0115 for 'Link quality'
                            ELEVATED:I01 (354e) Zigbee Event of Type commandDataReport from device 0xa4c13886e50d0115, incoming event: {"type":"commandDataReport","data":{"seq":10752,"dpValues":[{"dp":101,"datatype":2,"data":{"type":"Buffer","data":[0,0,0,0]}}]}...}
                            
                            ELEVATED:I01 (3587) message received '{"linkquality":80}' from device a4c13886e50d0115 type '2CT'
                            ELEVATED:I02 (3587) value generated '80' from device a4c13886e50d0115 for 'Link quality'
                            ELEVATED:I01 (3587) Zigbee Event of Type commandDataReport from device 0xa4c13886e50d0115, incoming event: {"type":"commandDataReport","data":{"seq":11008,"dpValues":[{"dp":102,"datatype":2,"data":{"type":"Buffer","data":[0,0,21,89]}}]}...}
                            
                            ELEVATED:I01 (35bd) message received '{"linkquality":76}' from device a4c13886e50d0115 type '2CT'
                            ELEVATED:I02 (35bd) value generated '76' from device a4c13886e50d0115 for 'Link quality'
                            ELEVATED:I01 (35bd) Zigbee Event of Type commandDataReport from device 0xa4c13886e50d0115, incoming event: {"type":"commandDataReport","data":{"seq":11264,"dpValues":[{"dp":103,"datatype":2,"data":{"type":"Buffer","data":[0,0,0,0]}}]}...}
                            
                            ELEVATED:I01 (35f2) message received '{"linkquality":76}' from device a4c13886e50d0115 type '2CT'
                            ELEVATED:I02 (35f2) value generated '76' from device a4c13886e50d0115 for 'Link quality'
                            ELEVATED:I01 (35f2) Zigbee Event of Type commandDataReport from device 0xa4c13886e50d0115, incoming event: {"type":"commandDataReport","data":{"seq":11520,"dpValues":[{"dp":104,"datatype":2,"data":{"type":"Buffer","data":[0,0,18,226]}}]}...}
                            
                            ELEVATED:I01 (3628) message received '{"linkquality":76}' from device a4c13886e50d0115 type '2CT'
                            ELEVATED:I02 (3628) value generated '76' from device a4c13886e50d0115 for 'Link quality'
                            ELEVATED:I01 (3628) Zigbee Event of Type commandDataReport from device 0xa4c13886e50d0115, incoming event: {"type":"commandDataReport","data":{"seq":11776,"dpValues":[{"dp":141,"datatype":4,"data":{"type":"Buffer","data":[0]}}]}...}
                            
                            ELEVATED:I01 (365f) message received '{"linkquality":80}' from device a4c13886e50d0115 type '2CT'
                            ELEVATED:I02 (365f) value generated '80' from device a4c13886e50d0115 for 'Link quality'
                            ELEVATED:I01 (365f) Zigbee Event of Type commandDataReport from device 0xa4c13886e50d0115, incoming event: {"type":"commandDataReport","data":{"seq":12032,"dpValues":[{"dp":142,"datatype":4,"data":{"type":"Buffer","data":[0]}}]}...}
                            
                            Asgothian 1 Reply Last reply Reply Quote 0
                            • Asgothian
                              Asgothian Developer @Flugschüler last edited by

                              @flugschüler wurden in diesem Fall die fraglichen Werte aktualisiert ?

                              F 1 Reply Last reply Reply Quote 0
                              • F
                                Flugschüler @Asgothian last edited by

                                @asgothian Wenn du die datenpunkte meinst es wurde nichts aktuallisiert.

                                Asgothian 1 Reply Last reply Reply Quote 0
                                • Codierknecht
                                  Codierknecht Developer Most Active last edited by

                                  Ich erhalte in unregelmäßigen Abständen folgende Einträge im Log:

                                  zigbee.0    2025-09-19 12:28:54.929	warn	Resolve Entity did not manage to find a mapped device for [object Object]
                                  zigbee.0    2025-09-19 12:24:38.716	warn	Resolve Entity did not manage to find a mapped device for [object Object]
                                  zigbee.0    2025-09-19 12:22:01.497	warn	Resolve Entity did not manage to find a mapped device for [object Object]
                                  

                                  Fehlt da evtl. ein JSON.stringify() ?

                                  Und by the way: Beim "reconfigure" eines Device müsste es korrekt heißen: "Device is being reconfigured"

                                  Asgothian 1 Reply Last reply Reply Quote 1
                                  • Asgothian
                                    Asgothian Developer @Flugschüler last edited by

                                    @flugschüler sagte in Tester wanted - Zigbee Adapter 3.1:

                                    @asgothian Wenn du die datenpunkte meinst es wurde nichts aktuallisiert.

                                    Muss eigentlich. Schau mal bitte bei dem DP current_b nach wann der das letzte mal aktualisiert wurde.

                                    Alternativ: Installier mal bitte vom iobroker GitHub die 3.1.2 - da sind kleinere Bugfixes beim Logging enthalten- und wiederhol dann bitte die Tests mit der 3.1.2 (abwarten, sowie device query)

                                    A.

                                    F 1 Reply Last reply Reply Quote 0
                                    • Asgothian
                                      Asgothian Developer @Codierknecht last edited by Asgothian

                                      @codierknecht sagte in Tester wanted - Zigbee Adapter 3.1:

                                      Ich erhalte in unregelmäßigen Abständen folgende Einträge im Log:

                                      zigbee.0    2025-09-19 12:28:54.929	warn	Resolve Entity did not manage to find a mapped device for [object Object]
                                      zigbee.0    2025-09-19 12:24:38.716	warn	Resolve Entity did not manage to find a mapped device for [object Object]
                                      zigbee.0    2025-09-19 12:22:01.497	warn	Resolve Entity did not manage to find a mapped device for [object Object]
                                      

                                      Fehlt da evtl. ein JSON.stringify() ?

                                      Danke für den Hinweis - ist gefixed in der 3.1.2 auf Github - die Meldung kommt nur. noch wenn sie wirklich benötigt wird.

                                      Das sprachliche hab ich gerade lokal geändert - wird also in 3.1.3 gefixed sein

                                      A.

                                      Nachtrag: die Meldungen kommen weil er versucht, die device definition für den Koordinator zu finden. Der hat aber keine :). Das filter ich in der Github Version raus - also keine Meldungen mehr.

                                      JLeg 1 Reply Last reply Reply Quote 1
                                      • JLeg
                                        JLeg @Asgothian last edited by

                                        @asgothian ...being on that... 😉 - Adapter 3.1.2, bei den umgedrehten Kacheln kickt der "Raumname" bei entsprechender Länge ein Icon weg:
                                        7b2179f7-8722-4128-b89c-e04c95222ae4-grafik.png
                                        Ansonsten läuft 3.1.2 sehr gut bei mir, ohne Auffälligkeiten...

                                        1 Reply Last reply Reply Quote 0
                                        • F
                                          Flugschüler @Asgothian last edited by

                                          @asgothian Ich hab jetzt geschaut was wann aktuallisiert wird und das einzige was aktuallisiert wird ist Link quality und Message from Zigbee bei Adapter 3.1.2 über git installiert. Bei Adapter 3.0.5 funktioniert alles prima.

                                          Asgothian 1 Reply Last reply Reply Quote 0
                                          • Asgothian
                                            Asgothian Developer @Flugschüler last edited by Asgothian

                                            @flugschüler sagte in Tester wanted - Zigbee Adapter 3.1:

                                            @asgothian Ich hab jetzt geschaut was wann aktuallisiert wird und das einzige was aktuallisiert wird ist Link quality und Message from Zigbee bei Adapter 3.1.2 über git installiert. Bei Adapter 3.0.5 funktioniert alles prima.

                                            Das wissen wir schon. Ich brauch die Meldungen, um zu sehen wo das hängen bleibt. Alternativ - ein Gerät damit ich das selber Debuggen kann.

                                            Ansonsten wirst du auf 3.0.5 bleiben müssen und von der Unterstützung von neuen Geräten abgeschnitten. Die Änderung / Ursache liegt in einer Änderung der ZH/ZHC Bibliotheken. Ohne mithilfe werde ich das nicht finden, und ohne Wechsel auf diese Bibliotheken werden neue Geräte nicht funktionieren.

                                            A.
                                            Und nein - ich werde mir keins kaufen. Ich steck da schon reichlich Freizeit rein - ich werd jetzt nicht auch noch Geld versenken in Geräte die ich nicht gebrauchen kann.

                                            F 1 Reply Last reply Reply Quote 0
                                            • First post
                                              Last post

                                            Support us

                                            ioBroker
                                            Community Adapters
                                            Donate

                                            872
                                            Online

                                            32.1k
                                            Users

                                            80.7k
                                            Topics

                                            1.3m
                                            Posts

                                            tester zhc zigbee zigbee 3.1
                                            11
                                            100
                                            1670
                                            Loading More Posts
                                            • Oldest to Newest
                                            • Newest to Oldest
                                            • Most Votes
                                            Reply
                                            • Reply as topic
                                            Log in to reply
                                            Community
                                            Impressum | Datenschutz-Bestimmungen | Nutzungsbedingungen
                                            The ioBroker Community 2014-2023
                                            logo