Skip to content
  • 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
  1. ioBroker Community Home
  2. Deutsch
  3. Tester
  4. ZigBee neue Version 1.5.x

NEWS

  • UPDATE 31.10.: Amazon Alexa - ioBroker Skill läuft aus ?
    apollon77A
    apollon77
    48
    3
    8.1k

  • Monatsrückblick – September 2025
    BluefoxB
    Bluefox
    13
    1
    1.9k

  • Neues Video "KI im Smart Home" - ioBroker plus n8n
    BluefoxB
    Bluefox
    15
    1
    2.1k

ZigBee neue Version 1.5.x

Geplant Angeheftet Gesperrt Verschoben Tester
579 Beiträge 72 Kommentatoren 147.8k Aufrufe 74 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.
  • K klassisch

    Hatte heute ein seltsames Erlebnis, da ich nicht zuordnen kann, wo allerdings "zigbee" auftauchte.

    • FLOT lädt keine Diagramme mehr. Nur Kreiseln
    • im log war folgender seltsame Fehler
    2021-04-22 03:21:03.832 - error: history.0 (6732) Cannot store file f:/ioBroker-data/History/20210422/history.zigbee.1.680ae2fffe1aa582.rotate_right.json: Error: EBUSY: resource busy or locked, open 'f:/ioBroker-data/History/20210422/history.zigbee.1.680ae2fffe1aa582.rotate_right.json'
    
    • Neustart von history bringt nichts.
    • Aus Zeitmangel kurz den ganzen ioBroker neu gestartet, was ich normalerweise nur bei Windows updates mache. Sonst läuft der einfach nur durch
    • Dabei jede Menge zigbee-Fehler

    Log Teil 1:

    2021-04-22 09:21:26.064  - info: zigbee.1 (7944) Zigbee started
    2021-04-22 09:21:26.128  - error: zigbee.1 (7944) 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().
    2021-04-22 09:21:26.128  - error: zigbee.1 (7944) unhandled promise rejection: this.debugDevices is not iterable
    2021-04-22 09:21:26.128  - error: zigbee.1 (7944) TypeError: this.debugDevices is not iterable
        at StatesController.publishToState (C:\Program Files\iobroker\ioBrMain026\node_modules\iobroker.zigbee\lib\statescontroller.js:425:40)
        at process._tickCallback (internal/process/next_tick.js:68:7)
    2021-04-22 09:21:26.129  - error: zigbee.1 (7944) this.debugDevices is not iterable
    2021-04-22 09:21:26.130  - error: zigbee.1 (7944) 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().
    2021-04-22 09:21:26.130  - error: zigbee.1 (7944) unhandled promise rejection: this.debugDevices is not iterable
    2021-04-22 09:21:26.131  - error: zigbee.1 (7944) TypeError: this.debugDevices is not iterable
        at StatesController.publishToState (C:\Program Files\iobroker\ioBrMain026\node_modules\iobroker.zigbee\lib\statescontroller.js:425:40)
        at process._tickCallback (internal/process/next_tick.js:68:7)
    2021-04-22 09:21:26.131  - error: zigbee.1 (7944) this.debugDevices is not iterable
    2021-04-22 09:21:26.131  - error: zigbee.1 (7944) 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().
    2021-04-22 09:21:26.131  - error: zigbee.1 (7944) unhandled promise rejection: this.debugDevices is not iterable
    2021-04-22 09:21:26.132  - error: zigbee.1 (7944) TypeError: this.debugDevices is not iterable
        at StatesController.publishToState (C:\Program Files\iobroker\ioBrMain026\node_modules\iobroker.zigbee\lib\statescontroller.js:425:40)
        at process._tickCallback (internal/process/next_tick.js:68:7)
    2021-04-22 09:21:26.132  - error: zigbee.1 (7944) this.debugDevices is not iterable
    2021-04-22 09:21:26.132  - error: zigbee.1 (7944) 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().
    2021-04-22 09:21:26.132  - error: zigbee.1 (7944) unhandled promise rejection: this.debugDevices is not iterable
    2021-04-22 09:21:26.132  - error: zigbee.1 (7944) TypeError: this.debugDevices is not iterable
        at StatesController.publishToState (C:\Program Files\iobroker\ioBrMain026\node_modules\iobroker.zigbee\lib\statescontroller.js:425:40)
        at process._tickCallback (internal/process/next_tick.js:68:7)
    2021-04-22 09:21:26.133  - error: zigbee.1 (7944) this.debugDevices is not iterable
    2021-04-22 09:21:26.133  - error: zigbee.1 (7944) 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().
    2021-04-22 09:21:26.133  - error: zigbee.1 (7944) unhandled promise rejection: this.debugDevices is not iterable
    2021-04-22 09:21:26.133  - error: zigbee.1 (7944) TypeError: this.debugDevices is not iterable
        at StatesController.publishToState (C:\Program Files\iobroker\ioBrMain026\node_modules\iobroker.zigbee\lib\statescontroller.js:425:40)
        at process._tickCallback (internal/process/next_tick.js:68:7)
    2021-04-22 09:21:26.134  - error: zigbee.1 (7944) this.debugDevices is not iterable
    2021-04-22 09:21:26.134  - error: zigbee.1 (7944) 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().
    2021-04-22 09:21:26.134  - error: zigbee.1 (7944) unhandled promise rejection: this.debugDevices is not iterable
    2021-04-22 09:21:26.134  - error: zigbee.1 (7944) TypeError: this.debugDevices is not iterable
        at StatesController.publishToState (C:\Program Files\iobroker\ioBrMain026\node_modules\iobroker.zigbee\lib\statescontroller.js:425:40)
        at process._tickCallback (internal/process/next_tick.js:68:7)
    2021-04-22 09:21:26.134  - error: zigbee.1 (7944) this.debugDevices is not iterable
    2021-04-22 09:21:26.135  - error: zigbee.1 (7944) 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().
    2021-04-22 09:21:26.135  - error: zigbee.1 (7944) unhandled promise rejection: this.debugDevices is not iterable
    2021-04-22 09:21:26.135  - error: zigbee.1 (7944) TypeError: this.debugDevices is not iterable
        at StatesController.publishToState (C:\Program Files\iobroker\ioBrMain026\node_modules\iobroker.zigbee\lib\statescontroller.js:425:40)
        at process._tickCallback (internal/process/next_tick.js:68:7)
    2021-04-22 09:21:26.135  - error: zigbee.1 (7944) this.debugDevices is not iterable
    2021-04-22 09:21:26.136  - error: zigbee.1 (7944) 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().
    2021-04-22 09:21:26.136  - error: zigbee.1 (7944) unhandled promise rejection: this.debugDevices is not iterable
    2021-04-22 09:21:26.136  - error: zigbee.1 (7944) TypeError: this.debugDevices is not iterable
        at StatesController.publishToState (C:\Program Files\iobroker\ioBrMain026\node_modules\iobroker.zigbee\lib\statescontroller.js:425:40)
        at process._tickCallback (internal/process/next_tick.js:68:7)
    2021-04-22 09:21:26.136  - error: zigbee.1 (7944) this.debugDevices is not iterable
    2021-04-22 09:21:26.137  - error: zigbee.1 (7944) 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().
    2021-04-22 09:21:26.137  - error: zigbee.1 (7944) unhandled promise rejection: this.debugDevices is not iterable
    2021-04-22 09:21:26.137  - error: zigbee.1 (7944) TypeError: this.debugDevices is not iterable
        at StatesController.publishToState (C:\Program Files\iobroker\ioBrMain026\node_modules\iobroker.zigbee\lib\statescontroller.js:425:40)
        at process._tickCallback (internal/process/next_tick.js:68:7)
    2021-04-22 09:21:26.137  - error: zigbee.1 (7944) this.debugDevices is not iterable
    2021-04-22 09:21:26.137  - error: zigbee.1 (7944) 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().
    2021-04-22 09:21:26.138  - error: zigbee.1 (7944) unhandled promise rejection: this.debugDevices is not iterable
    2021-04-22 09:21:26.138  - error: zigbee.1 (7944) TypeError: this.debugDevices is not iterable
        at StatesController.publishToState (C:\Program Files\iobroker\ioBrMain026\node_modules\iobroker.zigbee\lib\statescontroller.js:425:40)
        at process._tickCallback (internal/process/next_tick.js:68:7)
    2021-04-22 09:21:26.138  - error: zigbee.1 (7944) this.debugDevices is not iterable
    2021-04-22 09:21:26.138  - error: zigbee.1 (7944) 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().
    2021-04-22 09:21:26.138  - error: zigbee.1 (7944) unhandled promise rejection: this.debugDevices is not iterable
    2021-04-22 09:21:26.139  - error: zigbee.1 (7944) TypeError: this.debugDevices is not iterable
        at StatesController.publishToState (C:\Program Files\iobroker\ioBrMain026\node_modules\iobroker.zigbee\lib\statescontroller.js:425:40)
        at process._tickCallback (internal/process/next_tick.js:68:7)
    2021-04-22 09:21:26.139  - error: zigbee.1 (7944) this.debugDevices is not iterable
    2021-04-22 09:21:26.139  - error: zigbee.1 (7944) 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().
    2021-04-22 09:21:26.139  - error: zigbee.1 (7944) unhandled promise rejection: this.debugDevices is not iterable
    2021-04-22 09:21:26.180  - error: zigbee.1 (7944) TypeError: this.debugDevices is not iterable
        at StatesController.publishToState (C:\Program Files\iobroker\ioBrMain026\node_modules\iobroker.zigbee\lib\statescontroller.js:425:40)
        at process._tickCallback (internal/process/next_tick.js:68:7)
    2021-04-22 09:21:26.180  - error: zigbee.1 (7944) this.debugDevices is not iterable
    2021-04-22 09:21:26.180  - error: zigbee.1 (7944) 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().
    2021-04-22 09:21:26.180  - error: zigbee.1 (7944) unhandled promise rejection: this.debugDevices is not iterable
    2021-04-22 09:21:26.180  - error: zigbee.1 (7944) TypeError: this.debugDevices is not iterable
        at StatesController.publishToState (C:\Program Files\iobroker\ioBrMain026\node_modules\iobroker.zigbee\lib\statescontroller.js:425:40)
        at process._tickCallback (internal/process/next_tick.js:68:7)
    2021-04-22 09:21:26.180  - error: zigbee.1 (7944) this.debugDevices is not iterable
    2021-04-22 09:21:26.181  - error: zigbee.1 (7944) 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().
    2021-04-22 09:21:26.181  - error: zigbee.1 (7944) unhandled promise rejection: this.debugDevices is not iterable
    2021-04-22 09:21:26.181  - error: zigbee.1 (7944) TypeError: this.debugDevices is not iterable
        at StatesController.publishToState (C:\Program Files\iobroker\ioBrMain026\node_modules\iobroker.zigbee\lib\statescontroller.js:425:40)
        at process._tickCallback (internal/process/next_tick.js:68:7)
    2021-04-22 09:21:26.181  - error: zigbee.1 (7944) this.debugDevices is not iterable
    2021-04-22 09:21:26.181  - error: zigbee.1 (7944) 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().
    2021-04-22 09:21:26.181  - error: zigbee.1 (7944) unhandled promise rejection: this.debugDevices is not iterable
    2021-04-22 09:21:26.182  - error: zigbee.1 (7944) TypeError: this.debugDevices is not iterable
        at StatesController.publishToState (C:\Program Files\iobroker\ioBrMain026\node_modules\iobroker.zigbee\lib\statescontroller.js:425:40)
        at process._tickCallback (internal/process/next_tick.js:68:7)
    2021-04-22 09:21:26.182  - error: zigbee.1 (7944) this.debugDevices is not iterable
    2021-04-22 09:21:26.182  - error: zigbee.1 (7944) 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().
    2021-04-22 09:21:26.182  - error: zigbee.1 (7944) unhandled promise rejection: this.debugDevices is not iterable
    2021-04-22 09:21:26.182  - error: zigbee.1 (7944) TypeError: this.debugDevices is not iterable
        at StatesController.publishToState (C:\Program Files\iobroker\ioBrMain026\node_modules\iobroker.zigbee\lib\statescontroller.js:425:40)
        at process._tickCallback (internal/process/next_tick.js:68:7)
    2021-04-22 09:21:26.182  - error: zigbee.1 (7944) this.debugDevices is not iterable
    2021-04-22 09:21:26.182  - error: zigbee.1 (7944) 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().
    2021-04-22 09:21:26.183  - error: zigbee.1 (7944) unhandled promise rejection: this.debugDevices is not iterable
    2021-04-22 09:21:26.183  - error: zigbee.1 (7944) TypeError: this.debugDevices is not iterable
        at StatesController.publishToState (C:\Program Files\iobroker\ioBrMain026\node_modules\iobroker.zigbee\lib\statescontroller.js:425:40)
        at process._tickCallback (internal/process/next_tick.js:68:7)
    2021-04-22 09:21:26.183  - error: zigbee.1 (7944) this.debugDevices is not iterable
    2021-04-22 09:21:26.183  - error: zigbee.1 (7944) 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().
    2021-04-22 09:21:26.183  - error: zigbee.1 (7944) unhandled promise rejection: this.debugDevices is not iterable
    2021-04-22 09:21:26.183  - error: zigbee.1 (7944) TypeError: this.debugDevices is not iterable
        at StatesController.publishToState (C:\Program Files\iobroker\ioBrMain026\node_modules\iobroker.zigbee\lib\statescontroller.js:425:40)
        at process._tickCallback (internal/process/next_tick.js:68:7)
    2021-04-22 09:21:26.183  - error: zigbee.1 (7944) this.debugDevices is not iterable
    2021-04-22 09:21:26.184  - error: zigbee.1 (7944) 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().
    2021-04-22 09:21:26.184  - error: zigbee.1 (7944) unhandled promise rejection: this.debugDevices is not iterable
    2021-04-22 09:21:26.184  - error: zigbee.1 (7944) TypeError: this.debugDevices is not iterable
        at StatesController.publishToState (C:\Program Files\iobroker\ioBrMain026\node_modules\iobroker.zigbee\lib\statescontroller.js:425:40)
        at process._tickCallback (internal/process/next_tick.js:68:7)
    2021-04-22 09:21:26.186  - error: zigbee.1 (7944) this.debugDevices is not iterable
    2021-04-22 09:21:26.186  - error: zigbee.1 (7944) 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().
    2021-04-22 09:21:26.186  - error: zigbee.1 (7944) unhandled promise rejection: this.debugDevices is not iterable
    2021-04-22 09:21:26.186  - error: zigbee.1 (7944) TypeError: this.debugDevices is not iterable
        at StatesController.publishToState (C:\Program Files\iobroker\ioBrMain026\node_modules\iobroker.zigbee\lib\statescontroller.js:425:40)
        at process._tickCallback (internal/process/next_tick.js:68:7)
    2021-04-22 09:21:26.187  - error: zigbee.1 (7944) this.debugDevices is not iterable
    2021-04-22 09:21:26.187  - error: zigbee.1 (7944) 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().
    2021-04-22 09:21:26.187  - error: zigbee.1 (7944) unhandled promise rejection: this.debugDevices is not iterable
    2021-04-22 09:21:26.190  - error: zigbee.1 (7944) TypeError: this.debugDevices is not iterable
        at StatesController.publishToState (C:\Program Files\iobroker\ioBrMain026\node_modules\iobroker.zigbee\lib\statescontroller.js:425:40)
        at process._tickCallback (internal/process/next_tick.js:68:7)
    2021-04-22 09:21:26.190  - error: zigbee.1 (7944) this.debugDevices is not iterable
    2021-04-22 09:21:26.190  - error: zigbee.1 (7944) 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().
    2021-04-22 09:21:26.190  - error: zigbee.1 (7944) unhandled promise rejection: this.debugDevices is not iterable
    2021-04-22 09:21:26.190  - error: zigbee.1 (7944) TypeError: this.debugDevices is not iterable
        at StatesController.publishToState (C:\Program Files\iobroker\ioBrMain026\node_modules\iobroker.zigbee\lib\statescontroller.js:425:40)
        at process._tickCallback (internal/process/next_tick.js:68:7)
    2021-04-22 09:21:26.190  - error: zigbee.1 (7944) this.debugDevices is not iterable
    2021-04-22 09:21:26.191  - error: zigbee.1 (7944) 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().
    2021-04-22 09:21:26.191  - error: zigbee.1 (7944) unhandled promise rejection: this.debugDevices is not iterable
    2021-04-22 09:21:26.191  - error: zigbee.1 (7944) TypeError: this.debugDevices is not iterable
        at StatesController.publishToState (C:\Program Files\iobroker\ioBrMain026\node_modules\iobroker.zigbee\lib\statescontroller.js:425:40)
        at process._tickCallback (internal/process/next_tick.js:68:7)
    2021-04-22 09:21:26.191  - error: zigbee.1 (7944) this.debugDevices is not iterable
    2021-04-22 09:21:26.192  - error: zigbee.1 (7944) 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().
    2021-04-22 09:21:26.192  - error: zigbee.1 (7944) unhandled promise rejection: this.debugDevices is not iterable
    2021-04-22 09:21:26.192  - error: zigbee.1 (7944) TypeError: this.debugDevices is not iterable
        at StatesController.publishToState (C:\Program Files\iobroker\ioBrMain026\node_modules\iobroker.zigbee\lib\statescontroller.js:425:40)
        at process._tickCallback (internal/process/next_tick.js:68:7)
    2021-04-22 09:21:26.192  - error: zigbee.1 (7944) this.debugDevices is not iterable
    2021-04-22 09:21:26.192  - error: zigbee.1 (7944) 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().
    2021-04-22 09:21:26.192  - error: zigbee.1 (7944) unhandled promise rejection: this.debugDevices is not iterable
    2021-04-22 09:21:26.192  - error: zigbee.1 (7944) TypeError: this.debugDevices is not iterable
        at StatesController.publishToState (C:\Program Files\iobroker\ioBrMain026\node_modules\iobroker.zigbee\lib\statescontroller.js:425:40)
        at process._tickCallback (internal/process/next_tick.js:68:7)
    2021-04-22 09:21:26.192  - error: zigbee.1 (7944) this.debugDevices is not iterable
    2021-04-22 09:21:26.193  - error: zigbee.1 (7944) 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().
    2021-04-22 09:21:26.193  - error: zigbee.1 (7944) unhandled promise rejection: this.debugDevices is not iterable
    2021-04-22 09:21:26.193  - error: zigbee.1 (7944) TypeError: this.debugDevices is not iterable
        at StatesController.publishToState (C:\Program Files\iobroker\ioBrMain026\node_modules\iobroker.zigbee\lib\statescontroller.js:425:40)
        at process._tickCallback (internal/process/next_tick.js:68:7)
    2021-04-22 09:21:26.193  - error: zigbee.1 (7944) this.debugDevices is not iterable
    2021-04-22 09:21:26.193  - error: zigbee.1 (7944) 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().
    2021-04-22 09:21:26.193  - error: zigbee.1 (7944) unhandled promise rejection: this.debugDevices is not iterable
    2021-04-22 09:21:26.193  - error: zigbee.1 (7944) TypeError: this.debugDevices is not iterable
        at StatesController.publishToState (C:\Program Files\iobroker\ioBrMain026\node_modules\iobroker.zigbee\lib\statescontroller.js:425:40)
        at process._tickCallback (internal/process/next_tick.js:68:7)
    2021-04-22 09:21:26.194  - error: zigbee.1 (7944) this.debugDevices is not iterable
    2021-04-22 09:21:26.194  - error: zigbee.1 (7944) 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().
    2021-04-22 09:21:26.194  - error: zigbee.1 (7944) unhandled promise rejection: this.debugDevices is not iterable
    2021-04-22 09:21:26.194  - error: zigbee.1 (7944) TypeError: this.debugDevices is not iterable
        at StatesController.publishToState (C:\Program Files\iobroker\ioBrMain026\node_modules\iobroker.zigbee\lib\statescontroller.js:425:40)
        at process._tickCallback (internal/process/next_tick.js:68:7)
    2021-04-22 09:21:26.194  - error: zigbee.1 (7944) this.debugDevices is not iterable
    2021-04-22 09:21:26.194  - error: zigbee.1 (7944) 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().
    2021-04-22 09:21:26.194  - error: zigbee.1 (7944) unhandled promise rejection: this.debugDevices is not iterable
    2021-04-22 09:21:26.194  - error: zigbee.1 (7944) TypeError: this.debugDevices is not iterable
        at StatesController.publishToState (C:\Program Files\iobroker\ioBrMain026\node_modules\iobroker.zigbee\lib\statescontroller.js:425:40)
        at process._tickCallback (internal/process/next_tick.js:68:7)
    2021-04-22 09:21:26.195  - error: zigbee.1 (7944) this.debugDevices is not iterable
    2021-04-22 09:21:26.195  - error: zigbee.1 (7944) 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().
    2021-04-22 09:21:26.195  - error: zigbee.1 (7944) unhandled promise rejection: this.debugDevices is not iterable
    2021-04-22 09:21:26.195  - error: zigbee.1 (7944) TypeError: this.debugDevices is not iterable
        at StatesController.publishToState (C:\Program Files\iobroker\ioBrMain026\node_modules\iobroker.zigbee\lib\statescontroller.js:425:40)
        at process._tickCallback (internal/process/next_tick.js:68:7)
    2021-04-22 09:21:26.195  - error: zigbee.1 (7944) this.debugDevices is not iterable
    2021-04-22 09:21:26.195  - error: zigbee.1 (7944) 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().
    2021-04-22 09:21:26.195  - error: zigbee.1 (7944) unhandled promise rejection: this.debugDevices is not iterable
    2021-04-22 09:21:26.195  - error: zigbee.1 (7944) TypeError: this.debugDevices is not iterable
        at StatesController.publishToState (C:\Program Files\iobroker\ioBrMain026\node_modules\iobroker.zigbee\lib\statescontroller.js:425:40)
        at process._tickCallback (internal/process/next_tick.js:68:7)
    2021-04-22 09:21:26.196  - error: zigbee.1 (7944) this.debugDevices is not iterable
    2021-04-22 09:21:26.196  - error: zigbee.1 (7944) 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().
    2021-04-22 09:21:26.196  - error: zigbee.1 (7944) unhandled promise rejection: this.debugDevices is not iterable
    2021-04-22 09:21:26.196  - error: zigbee.1 (7944) TypeError: this.debugDevices is not iterable
        at StatesController.publishToState (C:\Program Files\iobroker\ioBrMain026\node_modules\iobroker.zigbee\lib\statescontroller.js:425:40)
        at process._tickCallback (internal/process/next_tick.js:68:7)
    2021-04-22 09:21:26.196  - error: zigbee.1 (7944) this.debugDevices is not iterable
    2021-04-22 09:21:26.196  - error: zigbee.1 (7944) 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().
    2021-04-22 09:21:26.196  - error: zigbee.1 (7944) unhandled promise rejection: this.debugDevices is not iterable
    2021-04-22 09:21:26.196  - error: zigbee.1 (7944) TypeError: this.debugDevices is not iterable
        at StatesController.publishToState (C:\Program Files\iobroker\ioBrMain026\node_modules\iobroker.zigbee\lib\statescontroller.js:425:40)
        at process._tickCallback (internal/process/next_tick.js:68:7)
    2021-04-22 09:21:26.197  - error: zigbee.1 (7944) this.debugDevices is not iterable
    2021-04-22 09:21:26.197  - error: zigbee.1 (7944) 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().
    2021-04-22 09:21:26.197  - error: zigbee.1 (7944) unhandled promise rejection: this.debugDevices is not iterable
    2021-04-22 09:21:26.197  - error: zigbee.1 (7944) TypeError: this.debugDevices is not iterable
        at StatesController.publishToState (C:\Program Files\iobroker\ioBrMain026\node_modules\iobroker.zigbee\lib\statescontroller.js:425:40)
        at process._tickCallback (internal/process/next_tick.js:68:7)
    2021-04-22 09:21:26.197  - error: zigbee.1 (7944) this.debugDevices is not iterable
    2021-04-22 09:21:26.197  - error: zigbee.1 (7944) 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().
    2021-04-22 09:21:26.198  - error: zigbee.1 (7944) unhandled promise rejection: this.debugDevices is not iterable
    2021-04-22 09:21:26.198  - error: zigbee.1 (7944) TypeError: this.debugDevices is not iterable
        at StatesController.publishToState (C:\Program Files\iobroker\ioBrMain026\node_modules\iobroker.zigbee\lib\statescontroller.js:425:40)
        at process._tickCallback (internal/process/next_tick.js:68:7)
    2021-04-22 09:21:26.198  - error: zigbee.1 (7944) this.debugDevices is not iterable
    2021-04-22 09:21:26.198  - error: zigbee.1 (7944) 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().
    2021-04-22 09:21:26.198  - error: zigbee.1 (7944) unhandled promise rejection: this.debugDevices is not iterable
    2021-04-22 09:21:26.198  - error: zigbee.1 (7944) TypeError: this.debugDevices is not iterable
        at StatesController.publishToState (C:\Program Files\iobroker\ioBrMain026\node_modules\iobroker.zigbee\lib\statescontroller.js:425:40)
        at process._tickCallback (internal/process/next_tick.js:68:7)
    2021-04-22 09:21:26.198  - error: zigbee.1 (7944) this.debugDevices is not iterable
    2021-04-22 09:21:26.199  - error: zigbee.1 (7944) 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().
    2021-04-22 09:21:26.199  - error: zigbee.1 (7944) unhandled promise rejection: this.debugDevices is not iterable
    2021-04-22 09:21:26.199  - error: zigbee.1 (7944) TypeError: this.debugDevices is not iterable
        at StatesController.publishToState (C:\Program Files\iobroker\ioBrMain026\node_modules\iobroker.zigbee\lib\statescontroller.js:425:40)
        at process._tickCallback (internal/process/next_tick.js:68:7)
    2021-04-22 09:21:26.199  - error: zigbee.1 (7944) this.debugDevices is not iterable
    2021-04-22 09:21:26.199  - error: zigbee.1 (7944) 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().
    2021-04-22 09:21:26.199  - error: zigbee.1 (7944) unhandled promise rejection: this.debugDevices is not iterable
    2021-04-22 09:21:26.199  - error: zigbee.1 (7944) TypeError: this.debugDevices is not iterable
        at StatesController.publishToState (C:\Program Files\iobroker\ioBrMain026\node_modules\iobroker.zigbee\lib\statescontroller.js:425:40)
        at process._tickCallback (internal/process/next_tick.js:68:7)
    2021-04-22 09:21:26.199  - error: zigbee.1 (7944) this.debugDevices is not iterable
    2021-04-22 09:21:26.200  - error: zigbee.1 (7944) 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().
    2021-04-22 09:21:26.200  - error: zigbee.1 (7944) unhandled promise rejection: this.debugDevices is not iterable
    2021-04-22 09:21:26.200  - error: zigbee.1 (7944) TypeError: this.debugDevices is not iterable
        at StatesController.publishToState (C:\Program Files\iobroker\ioBrMain026\node_modules\iobroker.zigbee\lib\statescontroller.js:425:40)
        at process._tickCallback (internal/process/next_tick.js:68:7)
    2021-04-22 09:21:26.200  - error: zigbee.1 (7944) this.debugDevices is not iterable
    2021-04-22 09:21:26.200  - error: zigbee.1 (7944) 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().
    2021-04-22 09:21:26.200  - error: zigbee.1 (7944) unhandled promise rejection: this.debugDevices is not iterable
    2021-04-22 09:21:26.200  - error: zigbee.1 (7944) TypeError: this.debugDevices is not iterable
        at StatesController.publishToState (C:\Program Files\iobroker\ioBrMain026\node_modules\iobroker.zigbee\lib\statescontroller.js:425:40)
        at process._tickCallback (internal/process/next_tick.js:68:7)
    2021-04-22 09:21:26.200  - error: zigbee.1 (7944) this.debugDevices is not iterable
    2021-04-22 09:21:26.201  - error: zigbee.1 (7944) 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().
    2021-04-22 09:21:26.201  - error: zigbee.1 (7944) unhandled promise rejection: this.debugDevices is not iterable
    2021-04-22 09:21:26.201  - error: zigbee.1 (7944) TypeError: this.debugDevices is not iterable
        at StatesController.publishToState (C:\Program Files\iobroker\ioBrMain026\node_modules\iobroker.zigbee\lib\statescontroller.js:425:40)
        at process._tickCallback (internal/process/next_tick.js:68:7)
    2021-04-22 09:21:26.201  - error: zigbee.1 (7944) this.debugDevices is not iterable
    2021-04-22 09:21:26.201  - error: zigbee.1 (7944) 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().
    2021-04-22 09:21:26.201  - error: zigbee.1 (7944) unhandled promise rejection: this.debugDevices is not iterable
    2021-04-22 09:21:26.201  - error: zigbee.1 (7944) TypeError: this.debugDevices is not iterable
        at StatesController.publishToState (C:\Program Files\iobroker\ioBrMain026\node_modules\iobroker.zigbee\lib\statescontroller.js:425:40)
        at process._tickCallback (internal/process/next_tick.js:68:7)
    2021-04-22 09:21:26.201  - error: zigbee.1 (7944) this.debugDevices is not iterable
    2021-04-22 09:21:26.202  - error: zigbee.1 (7944) 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().
    2021-04-22 09:21:26.202  - error: zigbee.1 (7944) unhandled promise rejection: this.debugDevices is not iterable
    2021-04-22 09:21:26.202  - error: zigbee.1 (7944) TypeError: this.debugDevices is not iterable
        at StatesController.publishToState (C:\Program Files\iobroker\ioBrMain026\node_modules\iobroker.zigbee\lib\statescontroller.js:425:40)
        at process._tickCallback (internal/process/next_tick.js:68:7)
    2021-04-22 09:21:26.202  - error: zigbee.1 (7944) this.debugDevices is not iterable
    2021-04-22 09:21:26.202  - error: zigbee.1 (7944) 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().
    2021-04-22 09:21:26.202  - error: zigbee.1 (7944) unhandled promise rejection: this.debugDevices is not iterable
    2021-04-22 09:21:26.202  - error: zigbee.1 (7944) TypeError: this.debugDevices is not iterable
        at StatesController.publishToState (C:\Program Files\iobroker\ioBrMain026\node_modules\iobroker.zigbee\lib\statescontroller.js:425:40)
        at process._tickCallback (internal/process/next_tick.js:68:7)
    2021-04-22 09:21:26.202  - error: zigbee.1 (7944) this.debugDevices is not iterable
    2021-04-22 09:21:26.203  - error: zigbee.1 (7944) 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().
    2021-04-22 09:21:26.203  - error: zigbee.1 (7944) unhandled promise rejection: this.debugDevices is not iterable
    2021-04-22 09:21:26.203  - error: zigbee.1 (7944) TypeError: this.debugDevices is not iterable
        at StatesController.publishToState (C:\Program Files\iobroker\ioBrMain026\node_modules\iobroker.zigbee\lib\statescontroller.js:425:40)
        at process._tickCallback (internal/process/next_tick.js:68:7)
    2021-04-22 09:21:26.203  - error: zigbee.1 (7944) this.debugDevices is not iterable
    2021-04-22 09:21:26.203  - error: zigbee.1 (7944) 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().
    2021-04-22 09:21:26.203  - error: zigbee.1 (7944) unhandled promise rejection: this.debugDevices is not iterable
    2021-04-22 09:21:26.204  - error: zigbee.1 (7944) TypeError: this.debugDevices is not iterable
        at StatesController.publishToState (C:\Program Files\iobroker\ioBrMain026\node_modules\iobroker.zigbee\lib\statescontroller.js:425:40)
        at process._tickCallback (internal/process/next_tick.js:68:7)
    2021-04-22 09:21:26.204  - error: zigbee.1 (7944) this.debugDevices is not iterable
    2021-04-22 09:21:26.204  - error: zigbee.1 (7944) 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().
    2021-04-22 09:21:26.204  - error: zigbee.1 (7944) unhandled promise rejection: this.debugDevices is not iterable
    2021-04-22 09:21:26.204  - error: zigbee.1 (7944) TypeError: this.debugDevices is not iterable
        at StatesController.publishToState (C:\Program Files\iobroker\ioBrMain026\node_modules\iobroker.zigbee\lib\statescontroller.js:425:40)
        at process._tickCallback (internal/process/next_tick.js:68:7)
    2021-04-22 09:21:26.205  - error: zigbee.1 (7944) this.debugDevices is not iterable
    2021-04-22 09:21:26.205  - error: zigbee.1 (7944) 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().
    2021-04-22 09:21:26.205  - error: zigbee.1 (7944) unhandled promise rejection: this.debugDevices is not iterable
    2021-04-22 09:21:26.205  - error: zigbee.1 (7944) TypeError: this.debugDevices is not iterable
        at StatesController.publishToState (C:\Program Files\iobroker\ioBrMain026\node_modules\iobroker.zigbee\lib\statescontroller.js:425:40)
        at process._tickCallback (internal/process/next_tick.js:68:7)
    2021-04-22 09:21:26.205  - error: zigbee.1 (7944) this.debugDevices is not iterable
    2021-04-22 09:21:26.206  - error: zigbee.1 (7944) 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().
    2021-04-22 09:21:26.206  - error: zigbee.1 (7944) unhandled promise rejection: this.debugDevices is not iterable
    2021-04-22 09:21:26.206  - error: zigbee.1 (7944) TypeError: this.debugDevices is not iterable
        at StatesController.publishToState (C:\Program Files\iobroker\ioBrMain026\node_modules\iobroker.zigbee\lib\statescontroller.js:425:40)
        at process._tickCallback (internal/process/next_tick.js:68:7)
    2021-04-22 09:21:26.206  - error: zigbee.1 (7944) this.debugDevices is not iterable
    2021-04-22 09:21:26.206  - error: zigbee.1 (7944) 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().
    2021-04-22 09:21:26.206  - error: zigbee.1 (7944) unhandled promise rejection: this.debugDevices is not iterable
    2021-04-22 09:21:26.207  - error: zigbee.1 (7944) TypeError: this.debugDevices is not iterable
        at StatesController.publishToState (C:\Program Files\iobroker\ioBrMain026\node_modules\iobroker.zigbee\lib\statescontroller.js:425:40)
        at process._tickCallback (internal/process/next_tick.js:68:7)
    2021-04-22 09:21:26.207  - error: zigbee.1 (7944) this.debugDevices is not iterable
    2021-04-22 09:21:26.207  - error: zigbee.1 (7944) 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().
    2021-04-22 09:21:26.207  - error: zigbee.1 (7944) unhandled promise rejection: this.debugDevices is not iterable
    2021-04-22 09:21:26.207  - error: zigbee.1 (7944) TypeError: this.debugDevices is not iterable
        at StatesController.publishToState (C:\Program Files\iobroker\ioBrMain026\node_modules\iobroker.zigbee\lib\statescontroller.js:425:40)
        at process._tickCallback (internal/process/next_tick.js:68:7)
    2021-04-22 09:21:26.207  - error: zigbee.1 (7944) this.debugDevices is not iterable
    2021-04-22 09:21:26.208  - error: zigbee.1 (7944) 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().
    2021-04-22 09:21:26.208  - error: zigbee.1 (7944) unhandled promise rejection: this.debugDevices is not iterable
    2021-04-22 09:21:26.208  - error: zigbee.1 (7944) TypeError: this.debugDevices is not iterable
        at StatesController.publishToState (C:\Program Files\iobroker\ioBrMain026\node_modules\iobroker.zigbee\lib\statescontroller.js:425:40)
        at process._tickCallback (internal/process/next_tick.js:68:7)
    2021-04-22 09:21:26.208  - error: zigbee.1 (7944) this.debugDevices is not iterable
    2021-04-22 09:21:26.208  - error: zigbee.1 (7944) 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().
    2021-04-22 09:21:26.209  - error: zigbee.1 (7944) unhandled promise rejection: this.debugDevices is not iterable
    2021-04-22 09:21:26.209  - error: zigbee.1 (7944) TypeError: this.debugDevices is not iterable
        at StatesController.publishToState (C:\Program Files\iobroker\ioBrMain026\node_modules\iobroker.zigbee\lib\statescontroller.js:425:40)
        at process._tickCallback (internal/process/next_tick.js:68:7)
    2021-04-22 09:21:26.209  - error: zigbee.1 (7944) this.debugDevices is not iterable
    2021-04-22 09:21:26.209  - error: zigbee.1 (7944) 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().
    2021-04-22 09:21:26.209  - error: zigbee.1 (7944) unhandled promise rejection: this.debugDevices is not iterable
    2021-04-22 09:21:26.209  - error: zigbee.1 (7944) TypeError: this.debugDevices is not iterable
        at StatesController.publishToState (C:\Program Files\iobroker\ioBrMain026\node_modules\iobroker.zigbee\lib\statescontroller.js:425:40)
        at process._tickCallback (internal/process/next_tick.js:68:7)
    2021-04-22 09:21:26.209  - error: zigbee.1 (7944) this.debugDevices is not iterable
    2021-04-22 09:21:26.210  - error: zigbee.1 (7944) 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().
    2021-04-22 09:21:26.210  - error: zigbee.1 (7944) unhandled promise rejection: this.debugDevices is not iterable
    2021-04-22 09:21:26.210  - error: zigbee.1 (7944) TypeError: this.debugDevices is not iterable
        at StatesController.publishToState (C:\Program Files\iobroker\ioBrMain026\node_modules\iobroker.zigbee\lib\statescontroller.js:425:40)
        at process._tickCallback (internal/process/next_tick.js:68:7)
    2021-04-22 09:21:26.210  - error: zigbee.1 (7944) this.debugDevices is not iterable
    2021-04-22 09:21:26.210  - error: zigbee.1 (7944) 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().
    2021-04-22 09:21:26.211  - error: zigbee.1 (7944) unhandled promise rejection: this.debugDevices is not iterable
    2021-04-22 09:21:26.211  - error: zigbee.1 (7944) TypeError: this.debugDevices is not iterable
        at StatesController.publishToState (C:\Program Files\iobroker\ioBrMain026\node_modules\iobroker.zigbee\lib\statescontroller.js:425:40)
        at process._tickCallback (internal/process/next_tick.js:68:7)
    2021-04-22 09:21:26.211  - error: zigbee.1 (7944) this.debugDevices is not iterable
    2021-04-22 09:21:26.211  - error: zigbee.1 (7944) 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().
    2021-04-22 09:21:26.211  - error: zigbee.1 (7944) unhandled promise rejection: this.debugDevices is not iterable
    2021-04-22 09:21:26.211  - error: zigbee.1 (7944) TypeError: this.debugDevices is not iterable
        at StatesController.publishToState (C:\Program Files\iobroker\ioBrMain026\node_modules\iobroker.zigbee\lib\statescontroller.js:425:40)
        at process._tickCallback (internal/process/next_tick.js:68:7)
    2021-04-22 09:21:26.212  - error: zigbee.1 (7944) this.debugDevices is not iterable
    2021-04-22 09:21:26.212  - error: zigbee.1 (7944) 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().
    2021-04-22 09:21:26.212  - error: zigbee.1 (7944) unhandled promise rejection: this.debugDevices is not iterable
    2021-04-22 09:21:26.212  - error: zigbee.1 (7944) TypeError: this.debugDevices is not iterable
        at StatesController.publishToState (C:\Program Files\iobroker\ioBrMain026\node_modules\iobroker.zigbee\lib\statescontroller.js:425:40)
        at process._tickCallback (internal/process/next_tick.js:68:7)
    2021-04-22 09:21:26.212  - error: zigbee.1 (7944) this.debugDevices is not iterable
    2021-04-22 09:21:26.213  - error: zigbee.1 (7944) 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().
    2021-04-22 09:21:26.213  - error: zigbee.1 (7944) unhandled promise rejection: this.debugDevices is not iterable
    2021-04-22 09:21:26.213  - error: zigbee.1 (7944) TypeError: this.debugDevices is not iterable
        at StatesController.publishToState (C:\Program Files\iobroker\ioBrMain026\node_modules\iobroker.zigbee\lib\statescontroller.js:425:40)
        at process._tickCallback (internal/process/next_tick.js:68:7)
    2021-04-22 09:21:26.213  - error: zigbee.1 (7944) this.debugDevices is not iterable
    2021-04-22 09:21:26.223  - error: zigbee.1 (7944) 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().
    2021-04-22 09:21:26.224  - error: zigbee.1 (7944) unhandled promise rejection: this.debugDevices is not iterable
    2021-04-22 09:21:26.224  - error: zigbee.1 (7944) TypeError: this.debugDevices is not iterable
        at StatesController.publishToState (C:\Program Files\iobroker\ioBrMain026\node_modules\iobroker.zigbee\lib\statescontroller.js:425:40)
        at process._tickCallback (internal/process/next_tick.js:68:7)
    2021-04-22 09:21:26.224  - error: zigbee.1 (7944) this.debugDevices is not iterable
    2021-04-22 09:21:26.224  - error: zigbee.1 (7944) 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().
    2021-04-22 09:21:26.225  - error: zigbee.1 (7944) unhandled promise rejection: this.debugDevices is not iterable
    2021-04-22 09:21:26.225  - error: zigbee.1 (7944) TypeError: this.debugDevices is not iterable
        at StatesController.publishToState (C:\Program Files\iobroker\ioBrMain026\node_modules\iobroker.zigbee\lib\statescontroller.js:425:40)
        at process._tickCallback (internal/process/next_tick.js:68:7)
    2021-04-22 09:21:26.225  - error: zigbee.1 (7944) this.debugDevices is not iterable
    2021-04-22 09:21:26.225  - error: zigbee.1 (7944) 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().
    2021-04-22 09:21:26.225  - error: zigbee.1 (7944) unhandled promise rejection: this.debugDevices is not iterable
    2021-04-22 09:21:26.226  - error: zigbee.1 (7944) TypeError: this.debugDevices is not iterable
        at StatesController.publishToState (C:\Program Files\iobroker\ioBrMain026\node_modules\iobroker.zigbee\lib\statescontroller.js:425:40)
        at process._tickCallback (internal/process/next_tick.js:68:7)
    2021-04-22 09:21:26.226  - error: zigbee.1 (7944) this.debugDevices is not iterable
    2021-04-22 09:21:26.226  - error: zigbee.1 (7944) 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().
    2021-04-22 09:21:26.226  - error: zigbee.1 (7944) unhandled promise rejection: this.debugDevices is not iterable
    2021-04-22 09:21:26.226  - error: zigbee.1 (7944) TypeError: this.debugDevices is not iterable
        at StatesController.publishToState (C:\Program Files\iobroker\ioBrMain026\node_modules\iobroker.zigbee\lib\statescontroller.js:425:40)
        at process._tickCallback (internal/process/next_tick.js:68:7)
    2021-04-22 09:21:26.226  - error: zigbee.1 (7944) this.debugDevices is not iterable
    2021-04-22 09:21:26.226  - error: zigbee.1 (7944) 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().
    2021-04-22 09:21:26.226  - error: zigbee.1 (7944) unhandled promise rejection: this.debugDevices is not iterable
    2021-04-22 09:21:26.227  - error: zigbee.1 (7944) TypeError: this.debugDevices is not iterable
        at StatesController.publishToState (C:\Program Files\iobroker\ioBrMain026\node_modules\iobroker.zigbee\lib\statescontroller.js:425:40)
        at process._tickCallback (internal/process/next_tick.js:68:7)
    2021-04-22 09:21:26.227  - error: zigbee.1 (7944) this.debugDevices is not iterable
    2021-04-22 09:21:26.227  - error: zigbee.1 (7944) 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().
    2021-04-22 09:21:26.227  - error: zigbee.1 (7944) unhandled promise rejection: this.debugDevices is not iterable
    2021-04-22 09:21:26.227  - error: zigbee.1 (7944) TypeError: this.debugDevices is not iterable
        at StatesController.publishToState (C:\Program Files\iobroker\ioBrMain026\node_modules\iobroker.zigbee\lib\statescontroller.js:425:40)
        at process._tickCallback (internal/process/next_tick.js:68:7)
    2021-04-22 09:21:26.227  - error: zigbee.1 (7944) this.debugDevices is not iterable
    2021-04-22 09:21:26.228  - error: zigbee.1 (7944) 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().
    2021-04-22 09:21:26.228  - error: zigbee.1 (7944) unhandled promise rejection: this.debugDevices is not iterable
    2021-04-22 09:21:26.228  - error: zigbee.1 (7944) TypeError: this.debugDevices is not iterable
        at StatesController.publishToState (C:\Program Files\iobroker\ioBrMain026\node_modules\iobroker.zigbee\lib\statescontroller.js:425:40)
        at process._tickCallback (internal/process/next_tick.js:68:7)
    2021-04-22 09:21:26.228  - error: zigbee.1 (7944) this.debugDevices is not iterable
    2021-04-22 09:21:26.228  - error: zigbee.1 (7944) 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().
    2021-04-22 09:21:26.229  - error: zigbee.1 (7944) unhandled promise rejection: this.debugDevices is not iterable
    2021-04-22 09:21:26.229  - error: zigbee.1 (7944) TypeError: this.debugDevices is not iterable
        at StatesController.publishToState (C:\Program Files\iobroker\ioBrMain026\node_modules\iobroker.zigbee\lib\statescontroller.js:425:40)
        at process._tickCallback (internal/process/next_tick.js:68:7)
    2021-04-22 09:21:26.229  - error: zigbee.1 (7944) this.debugDevices is not iterable
    2021-04-22 09:21:26.229  - error: zigbee.1 (7944) 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().
    2021-04-22 09:21:26.229  - error: zigbee.1 (7944) unhandled promise rejection: this.debugDevices is not iterable
    2021-04-22 09:21:26.230  - error: zigbee.1 (7944) TypeError: this.debugDevices is not iterable
        at StatesController.publishToState (C:\Program Files\iobroker\ioBrMain026\node_modules\iobroker.zigbee\lib\statescontroller.js:425:40)
        at process._tickCallback (internal/process/next_tick.js:68:7)
    2021-04-22 09:21:26.230  - error: zigbee.1 (7944) this.debugDevices is not iterable
    2021-04-22 09:21:26.230  - error: zigbee.1 (7944) 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().
    2021-04-22 09:21:26.234  - error: zigbee.1 (7944) unhandled promise rejection: this.debugDevices is not iterable
    2021-04-22 09:21:26.234  - error: zigbee.1 (7944) TypeError: this.debugDevices is not iterable
        at StatesController.publishToState (C:\Program Files\iobroker\ioBrMain026\node_modules\iobroker.zigbee\lib\statescontroller.js:425:40)
        at process._tickCallback (internal/process/next_tick.js:68:7)
    2021-04-22 09:21:26.234  - error: zigbee.1 (7944) this.debugDevices is not iterable
    2021-04-22 09:21:26.234  - error: zigbee.1 (7944) 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().
    2021-04-22 09:21:26.235  - error: zigbee.1 (7944) unhandled promise rejection: this.debugDevices is not iterable
    2021-04-22 09:21:26.235  - error: zigbee.1 (7944) TypeError: this.debugDevices is not iterable
        at StatesController.publishToState (C:\Program Files\iobroker\ioBrMain026\node_modules\iobroker.zigbee\lib\statescontroller.js:425:40)
        at process._tickCallback (internal/process/next_tick.js:68:7)
    2021-04-22 09:21:26.235  - error: zigbee.1 (7944) this.debugDevices is not iterable
    2021-04-22 09:21:26.235  - error: zigbee.1 (7944) 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().
    2021-04-22 09:21:26.235  - error: zigbee.1 (7944) unhandled promise rejection: this.debugDevices is not iterable
    2021-04-22 09:21:26.236  - error: zigbee.1 (7944) TypeError: this.debugDevices is not iterable
        at StatesController.publishToState (C:\Program Files\iobroker\ioBrMain026\node_modules\iobroker.zigbee\lib\statescontroller.js:425:40)
        at process._tickCallback (internal/process/next_tick.js:68:7)
    2021-04-22 09:21:26.236  - error: zigbee.1 (7944) this.debugDevices is not iterable
    2021-04-22 09:21:26.236  - error: zigbee.1 (7944) 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().
    2021-04-22 09:21:26.236  - error: zigbee.1 (7944) unhandled promise rejection: this.debugDevices is not iterable
    2021-04-22 09:21:26.236  - error: zigbee.1 (7944) TypeError: this.debugDevices is not iterable
        at StatesController.publishToState (C:\Program Files\iobroker\ioBrMain026\node_modules\iobroker.zigbee\lib\statescontroller.js:425:40)
        at process._tickCallback (internal/process/next_tick.js:68:7)
    2021-04-22 09:21:26.236  - error: zigbee.1 (7944) this.debugDevices is not iterable
    2021-04-22 09:21:26.236  - error: zigbee.1 (7944) 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().
    2021-04-22 09:21:26.237  - error: zigbee.1 (7944) unhandled promise rejection: this.debugDevices is not iterable
    2021-04-22 09:21:26.238  - error: zigbee.1 (7944) TypeError: this.debugDevices is not iterable
        at StatesController.publishToState (C:\Program Files\iobroker\ioBrMain026\node_modules\iobroker.zigbee\lib\statescontroller.js:425:40)
        at process._tickCallback (internal/process/next_tick.js:68:7)
    2021-04-22 09:21:26.239  - error: zigbee.1 (7944) this.debugDevices is not iterable
    2021-04-22 09:21:26.239  - error: zigbee.1 (7944) 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().
    2021-04-22 09:21:26.239  - error: zigbee.1 (7944) unhandled promise rejection: this.debugDevices is not iterable
    2021-04-22 09:21:26.239  - error: zigbee.1 (7944) TypeError: this.debugDevices is not iterable
        at StatesController.publishToState (C:\Program Files\iobroker\ioBrMain026\node_modules\iobroker.zigbee\lib\statescontroller.js:425:40)
        at process._tickCallback (internal/process/next_tick.js:68:7)
    2021-04-22 09:21:26.239  - error: zigbee.1 (7944) this.debugDevices is not iterable
    2021-04-22 09:21:27.447  - info: zigbee.1 (7944) cleaned everything up...
    2021-04-22 09:21:27.449  - info: zigbee.1 (7944) Zigbee: disabling joining new devices.
    2021-04-22 09:21:30.662  - info: zigbee.1 (7944) terminating
    2021-04-22 09:21:30.662  - warn: zigbee.1 (7944) Terminated (UNCAUGHT_EXCEPTION): Without reason
    2021-04-22 09:21:31.669  - info: zigbee.1 (7944) terminating with timeout
    
    
    

    Keine Ahnung was da passiert ist und ob das was mit Zigbee zu tun hat. Zigbee Adapter version 1.5.1

    AsgothianA Offline
    AsgothianA Offline
    Asgothian
    Developer
    schrieb am zuletzt editiert von Asgothian
    #59

    @klassisch Trag mal bitte einen leeren String in den State zigbee.0.debugmessages. Aus irgend einem Grund hat er das Array nicht sauber initialisiert.

    Es scheint so das es ein Problem mit der states Datenbank gibt. Ohne die läuft der Zigbee Adapter halt nicht.

    A.

    ioBroker auf RPi4 - Hardware soweit wie möglich via Zigbee.
    "Shit don't work" ist keine Fehlermeldung, sondern ein Fluch.

    K 1 Antwort Letzte Antwort
    0
    • AsgothianA Asgothian

      @klassisch Trag mal bitte einen leeren String in den State zigbee.0.debugmessages. Aus irgend einem Grund hat er das Array nicht sauber initialisiert.

      Es scheint so das es ein Problem mit der states Datenbank gibt. Ohne die läuft der Zigbee Adapter halt nicht.

      A.

      K Offline
      K Offline
      klassisch
      Most Active
      schrieb am zuletzt editiert von klassisch
      #60

      @asgothian sagte in ZigBee neue Version 1.5.x:

      @klassisch Trag mal bitte einen leeren String in den State zigbee.0.debugmessages.

      Vielen Dank! einfach ein Blank, oder ein ''? Habe mal letzteres eingetragen; Es stand vorher nichts drin

      Es scheint so dass es ein Problem mit der states Datenbank gibt. Ohne die läuft der Zigbee Adapter halt nicht.

      Eigentlich sind mir bei meinem System keine Probs mit der states DB bekannt. Ich habe allerdings das Abspeicherintervall (Schreiben auf Platte) etwas größer gewählt, siehe dort. Und Zigbee ist einer der letzten Adapter, der an den Start geht. Die anderen vorher haben kein Problem gemeldet. Der Zigbee adapter hat sich bzw wurde gestoppt und nochmals gestartet. Das lief dann durch.

      1 Antwort Letzte Antwort
      0
      • D Offline
        D Offline
        DocGame
        schrieb am zuletzt editiert von DocGame
        #61

        Ich habe seit 2 Jahren 6 Xiaomi-Honeywell Rauchmelder im Einsatz. So weit so gut (Kommen ja hoffentlich nie zum Einsatz). Seither suche ich aber auch schon nach Lösungen bzw. Alternativen ob es welche gibt bei denen man den Alarm schalten kann(Bei Alarm von einem sollen alle losgehen). Scheinbar gibt es so was nicht.
        Habe jetzt eine Sirene bestellt, die neben 18 Verschiedenen Töne und Lautstärkeeinstellung auch Temperatur und Luftfeuchte (mit jeweiligen Hardwaremäßigen min./max. Alarmen dieser Werte). Die Alarme will ich auf diesen Zentral angebrachten weiterleiten (und eventuell noch einen Einbruchalarm)
        Das einlernen Klappte sofort und in der Geräteliste sieht auch alles gut aus. Leider Bleiben die Werte auch nach 2 Tagen leer (Temp., Humy.) Alarm lässt sich auch nicht tiggern. Mit der Ausschussvariante ändert sich auch nichts.
        Hat jemand das Teil zum arbeiten gebracht?
        NAS-AB02B0
        Siren4.JPG Siren3.JPG Siren2.JPG Siren1.JPG Siren0.JPG

        L B 2 Antworten Letzte Antwort
        0
        • D DocGame

          Ich habe seit 2 Jahren 6 Xiaomi-Honeywell Rauchmelder im Einsatz. So weit so gut (Kommen ja hoffentlich nie zum Einsatz). Seither suche ich aber auch schon nach Lösungen bzw. Alternativen ob es welche gibt bei denen man den Alarm schalten kann(Bei Alarm von einem sollen alle losgehen). Scheinbar gibt es so was nicht.
          Habe jetzt eine Sirene bestellt, die neben 18 Verschiedenen Töne und Lautstärkeeinstellung auch Temperatur und Luftfeuchte (mit jeweiligen Hardwaremäßigen min./max. Alarmen dieser Werte). Die Alarme will ich auf diesen Zentral angebrachten weiterleiten (und eventuell noch einen Einbruchalarm)
          Das einlernen Klappte sofort und in der Geräteliste sieht auch alles gut aus. Leider Bleiben die Werte auch nach 2 Tagen leer (Temp., Humy.) Alarm lässt sich auch nicht tiggern. Mit der Ausschussvariante ändert sich auch nichts.
          Hat jemand das Teil zum arbeiten gebracht?
          NAS-AB02B0
          Siren4.JPG Siren3.JPG Siren2.JPG Siren1.JPG Siren0.JPG

          L Offline
          L Offline
          locito09
          schrieb am zuletzt editiert von
          #62

          @docgame
          Funktioniert bei mir ohne Probleme

          D 1 Antwort Letzte Antwort
          0
          • L locito09

            @docgame
            Funktioniert bei mir ohne Probleme

            D Offline
            D Offline
            DocGame
            schrieb am zuletzt editiert von DocGame
            #63

            @locito09
            Alle States, in die ich was eintragen kann habe ich gefüllt bzw. angeschalten. Die zeigt er auch als bestätigt. Es kommen scheinbar nur keine gemessenen werte an. Alarm auslösen geht auch nicht.
            Egal ob die Spannungsversorgung über USB oder Batterie erfolgt. Bin relativ Ratlos...
            Siren5.JPG

            L 1 Antwort Letzte Antwort
            0
            • D DocGame

              @locito09
              Alle States, in die ich was eintragen kann habe ich gefüllt bzw. angeschalten. Die zeigt er auch als bestätigt. Es kommen scheinbar nur keine gemessenen werte an. Alarm auslösen geht auch nicht.
              Egal ob die Spannungsversorgung über USB oder Batterie erfolgt. Bin relativ Ratlos...
              Siren5.JPG

              L Offline
              L Offline
              locito09
              schrieb am zuletzt editiert von
              #64

              @docgame
              Löschen und nochmals anlernen, ich habe das Gerät am Strom und benutze ihn als Klingel im OG funktioniert super

              D 1 Antwort Letzte Antwort
              0
              • L locito09

                @docgame
                Löschen und nochmals anlernen, ich habe das Gerät am Strom und benutze ihn als Klingel im OG funktioniert super

                D Offline
                D Offline
                DocGame
                schrieb am zuletzt editiert von
                #65

                @locito09 Gelöscht habe ich ihn schon zigmal. Ich vermute, das er die nächsten Tage in seinen Karton zurückkehrt und in meiner Zigbee-Asservatenkammer landet. Ewig schade 😢

                1 Antwort Letzte Antwort
                0
                • D DocGame

                  Ich habe seit 2 Jahren 6 Xiaomi-Honeywell Rauchmelder im Einsatz. So weit so gut (Kommen ja hoffentlich nie zum Einsatz). Seither suche ich aber auch schon nach Lösungen bzw. Alternativen ob es welche gibt bei denen man den Alarm schalten kann(Bei Alarm von einem sollen alle losgehen). Scheinbar gibt es so was nicht.
                  Habe jetzt eine Sirene bestellt, die neben 18 Verschiedenen Töne und Lautstärkeeinstellung auch Temperatur und Luftfeuchte (mit jeweiligen Hardwaremäßigen min./max. Alarmen dieser Werte). Die Alarme will ich auf diesen Zentral angebrachten weiterleiten (und eventuell noch einen Einbruchalarm)
                  Das einlernen Klappte sofort und in der Geräteliste sieht auch alles gut aus. Leider Bleiben die Werte auch nach 2 Tagen leer (Temp., Humy.) Alarm lässt sich auch nicht tiggern. Mit der Ausschussvariante ändert sich auch nichts.
                  Hat jemand das Teil zum arbeiten gebracht?
                  NAS-AB02B0
                  Siren4.JPG Siren3.JPG Siren2.JPG Siren1.JPG Siren0.JPG

                  B Offline
                  B Offline
                  BigMike71
                  schrieb am zuletzt editiert von
                  #66

                  @docgame
                  doch gibt es mit alarmauslösung, leider werden meine post wohl immer überlesen 😞
                  siehe ein paar zeilen unter dir... > SMSZB-120

                  leider funtz das mit dem aktuellen zigbee adapter irgendwie nicht richtig deshalb mein post

                  D 1 Antwort Letzte Antwort
                  0
                  • B BigMike71

                    @docgame
                    doch gibt es mit alarmauslösung, leider werden meine post wohl immer überlesen 😞
                    siehe ein paar zeilen unter dir... > SMSZB-120

                    leider funtz das mit dem aktuellen zigbee adapter irgendwie nicht richtig deshalb mein post

                    D Offline
                    D Offline
                    DocGame
                    schrieb am zuletzt editiert von
                    #67

                    @bigmike71 sagte in ZigBee neue Version 1.5.x:

                    SMSZB-120

                    Habe einen Link zu dem SMSZB-120 gefunden. Da werde 78€ verlangt. Bei 6 Stück kommt da ja schon was zusammen. Werde ich mir wohn nicht gönnen, da meine ja im Zigbeenetz funktionieren und ich den State ja abgreifen kann. Im Moment wäre mir schon mit dem ansteuern der Sirene gedient. Danke aber nochmals für den Hinweis zu deinem Post.

                    arteckA B 2 Antworten Letzte Antwort
                    0
                    • D DocGame

                      @bigmike71 sagte in ZigBee neue Version 1.5.x:

                      SMSZB-120

                      Habe einen Link zu dem SMSZB-120 gefunden. Da werde 78€ verlangt. Bei 6 Stück kommt da ja schon was zusammen. Werde ich mir wohn nicht gönnen, da meine ja im Zigbeenetz funktionieren und ich den State ja abgreifen kann. Im Moment wäre mir schon mit dem ansteuern der Sirene gedient. Danke aber nochmals für den Hinweis zu deinem Post.

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

                      @docgame ehh so schnell wie du Postest haben wir keine Zeit dazwischen zu grätschen... ruhig blut...

                      nimm mal die id von dem Teil und pack die mal ins debugmessages

                      11566faf-213c-4fa4-b5d2-ebe044a0328a-grafik.png

                      so.. dann weck das Teil kurz mal auf.. kommt was im LOG ?

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

                      D 1 Antwort Letzte Antwort
                      0
                      • D DocGame

                        @bigmike71 sagte in ZigBee neue Version 1.5.x:

                        SMSZB-120

                        Habe einen Link zu dem SMSZB-120 gefunden. Da werde 78€ verlangt. Bei 6 Stück kommt da ja schon was zusammen. Werde ich mir wohn nicht gönnen, da meine ja im Zigbeenetz funktionieren und ich den State ja abgreifen kann. Im Moment wäre mir schon mit dem ansteuern der Sirene gedient. Danke aber nochmals für den Hinweis zu deinem Post.

                        B Offline
                        B Offline
                        BigMike71
                        schrieb am zuletzt editiert von
                        #69

                        @docgame
                        habe mein Melder direkt bei Amazon für 38€ gekauft!
                        Amazon

                        1 Antwort Letzte Antwort
                        0
                        • arteckA arteck

                          @docgame ehh so schnell wie du Postest haben wir keine Zeit dazwischen zu grätschen... ruhig blut...

                          nimm mal die id von dem Teil und pack die mal ins debugmessages

                          11566faf-213c-4fa4-b5d2-ebe044a0328a-grafik.png

                          so.. dann weck das Teil kurz mal auf.. kommt was im LOG ?

                          D Offline
                          D Offline
                          DocGame
                          schrieb am zuletzt editiert von
                          #70

                          @arteck

                          zigbee.0	2021-04-24 23:13:06.549	warn	(6070) ELEVATED publishToState: value generated '10' from device 804b50fffe0475a0 for 'Link quality'
                          zigbee.0	2021-04-24 23:13:06.549	warn	(6070) ELEVATED publishToState: message received '{"linkquality":10}' from device 804b50fffe0475a0 type 'NAS-AB02B0'
                          zigbee.0	2021-04-24 23:13:06.549	warn	(6070) ELEVATED publishToState: value generated 'true' from device 804b50fffe0475a0 for 'Available'
                          zigbee.0	2021-04-24 23:13:06.548	warn	(6070) ELEVATED publishToState: message received '{"available":true}' from device 804b50fffe0475a0 type 'NAS-AB02B0'
                          zigbee.0	2021-04-24 23:13:06.497	warn	(6070) ELEVATED publishToState: value generated '10' from device 804b50fffe0475a0 for 'Link quality'
                          zigbee.0	2021-04-24 23:13:06.497	warn	(6070) ELEVATED publishToState: message received '{"linkquality":10}' from device 804b50fffe0475a0 type 'NAS-AB02B0'
                          zigbee.0	2021-04-24 23:13:06.497	warn	(6070) ELEVATED publishToState: value generated 'true' from device 804b50fffe0475a0 for 'Available'
                          zigbee.0	2021-04-24 23:13:06.497	warn	(6070) ELEVATED publishToState: message received '{"available":true}' from device 804b50fffe0475a0 type 'NAS-AB02B0'
                          zigbee.0	2021-04-24 23:13:05.547	warn	(6070) Device '0x804b50fffe0475a0' announced itself
                          zigbee.0	2021-04-24 23:13:05.495	warn	(6070) Device '0x804b50fffe0475a0' announced itself
                          zigbee.0	2021-04-24 23:10:31.421	warn	(6070) Device '0x804b50fffe0475a0' announced itself
                          zigbee.0	2021-04-24 23:09:41.277	info	(6070) Zigbee started
                          
                          arteckA 1 Antwort Letzte Antwort
                          0
                          • D DocGame

                            @arteck

                            zigbee.0	2021-04-24 23:13:06.549	warn	(6070) ELEVATED publishToState: value generated '10' from device 804b50fffe0475a0 for 'Link quality'
                            zigbee.0	2021-04-24 23:13:06.549	warn	(6070) ELEVATED publishToState: message received '{"linkquality":10}' from device 804b50fffe0475a0 type 'NAS-AB02B0'
                            zigbee.0	2021-04-24 23:13:06.549	warn	(6070) ELEVATED publishToState: value generated 'true' from device 804b50fffe0475a0 for 'Available'
                            zigbee.0	2021-04-24 23:13:06.548	warn	(6070) ELEVATED publishToState: message received '{"available":true}' from device 804b50fffe0475a0 type 'NAS-AB02B0'
                            zigbee.0	2021-04-24 23:13:06.497	warn	(6070) ELEVATED publishToState: value generated '10' from device 804b50fffe0475a0 for 'Link quality'
                            zigbee.0	2021-04-24 23:13:06.497	warn	(6070) ELEVATED publishToState: message received '{"linkquality":10}' from device 804b50fffe0475a0 type 'NAS-AB02B0'
                            zigbee.0	2021-04-24 23:13:06.497	warn	(6070) ELEVATED publishToState: value generated 'true' from device 804b50fffe0475a0 for 'Available'
                            zigbee.0	2021-04-24 23:13:06.497	warn	(6070) ELEVATED publishToState: message received '{"available":true}' from device 804b50fffe0475a0 type 'NAS-AB02B0'
                            zigbee.0	2021-04-24 23:13:05.547	warn	(6070) Device '0x804b50fffe0475a0' announced itself
                            zigbee.0	2021-04-24 23:13:05.495	warn	(6070) Device '0x804b50fffe0475a0' announced itself
                            zigbee.0	2021-04-24 23:10:31.421	warn	(6070) Device '0x804b50fffe0475a0' announced itself
                            zigbee.0	2021-04-24 23:09:41.277	info	(6070) Zigbee started
                            
                            arteckA Offline
                            arteckA Offline
                            arteck
                            Developer Most Active
                            schrieb am zuletzt editiert von arteck
                            #71

                            @docgame gewöhn dir bitte an LOG komplett zu posten oder so das man da was erkennen kann und nicht ein 5 zeilen schnipsel

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

                            D 1 Antwort Letzte Antwort
                            0
                            • arteckA arteck

                              @docgame gewöhn dir bitte an LOG komplett zu posten oder so das man da was erkennen kann und nicht ein 5 zeilen schnipsel

                              D Offline
                              D Offline
                              DocGame
                              schrieb am zuletzt editiert von DocGame
                              #72

                              @arteck Wenn dies die einzigen zigbee.0 Einträge zu diesen Zeitraum sind (+/- 1 Min.)...was soll ich dann noch schicken? Habe 2 nicht relevante Zeilen de iqontrol Adapters dazwischen rausgelöscht.
                              Da es da ja nichts zum Auslösen gibt ausser Anlernknopf und Batterie Raus habe ich für das Log die Batterie raus und wieder rein gemacht.

                              AsgothianA 1 Antwort Letzte Antwort
                              0
                              • D DocGame

                                @arteck Wenn dies die einzigen zigbee.0 Einträge zu diesen Zeitraum sind (+/- 1 Min.)...was soll ich dann noch schicken? Habe 2 nicht relevante Zeilen de iqontrol Adapters dazwischen rausgelöscht.
                                Da es da ja nichts zum Auslösen gibt ausser Anlernknopf und Batterie Raus habe ich für das Log die Batterie raus und wieder rein gemacht.

                                AsgothianA Offline
                                AsgothianA Offline
                                Asgothian
                                Developer
                                schrieb am zuletzt editiert von
                                #73

                                @docgame Bitte mach das Folgende:

                                • Gerät aus dem Adapter löschen
                                • Gerät neu pairen
                                • Log beobachten ob es Nachrichten dazu gibt das das Gerät "configured" werden soll, und ob dieses erfolgreich war.

                                A.

                                ioBroker auf RPi4 - Hardware soweit wie möglich via Zigbee.
                                "Shit don't work" ist keine Fehlermeldung, sondern ein Fluch.

                                D 1 Antwort Letzte Antwort
                                0
                                • AsgothianA Asgothian

                                  @docgame Bitte mach das Folgende:

                                  • Gerät aus dem Adapter löschen
                                  • Gerät neu pairen
                                  • Log beobachten ob es Nachrichten dazu gibt das das Gerät "configured" werden soll, und ob dieses erfolgreich war.

                                  A.

                                  D Offline
                                  D Offline
                                  DocGame
                                  schrieb am zuletzt editiert von
                                  #74

                                  @asgothian Das Anlernen klappt....Aber die States wollen nicht. Im Log sind auch Meldungen, die mir leider nichts sagen_

                                  zigbee.0	2021-04-25 17:53:36.221	warn	(6070) ELEVATED publishToState: value generated '159' from device 804b50fffe0475a0 for 'Link quality'
                                  zigbee.0	2021-04-25 17:53:36.221	warn	(6070) ELEVATED publishToState: message received '{"linkquality":159}' from device 804b50fffe0475a0 type 'NAS-AB02B0'
                                  zigbee.0	2021-04-25 17:53:22.677	warn	(6070) ELEVATED publishToState: value generated '10' from device 804b50fffe0475a0 for 'Link quality'
                                  zigbee.0	2021-04-25 17:53:22.677	warn	(6070) ELEVATED publishToState: message received '{"linkquality":10}' from device 804b50fffe0475a0 type 'NAS-AB02B0'
                                  zigbee.0	2021-04-25 17:53:22.677	warn	(6070) ELEVATED publishToState: value generated 'true' from device 804b50fffe0475a0 for 'Available'
                                  zigbee.0	2021-04-25 17:53:22.676	warn	(6070) ELEVATED publishToState: message received '{"available":true}' from device 804b50fffe0475a0 type 'NAS-AB02B0'
                                  zigbee.0	2021-04-25 17:53:21.677	warn	(6070) ELEVATED publishToState: value generated '159' from device 804b50fffe0475a0 for 'Link quality'
                                  zigbee.0	2021-04-25 17:53:21.677	warn	(6070) ELEVATED publishToState: message received '{"linkquality":159}' from device 804b50fffe0475a0 type 'NAS-AB02B0'
                                  zigbee.0	2021-04-25 17:53:21.676	info	(6070) Device '0x804b50fffe0475a0' is supported, identified as: Neo Temperature & humidity sensor and alarm (NAS-AB02B0)
                                  zigbee.0	2021-04-25 17:53:21.675	info	(6070) Successfully interviewed '0x804b50fffe0475a0', device has succesfully been paired
                                  zigbee.0	2021-04-25 17:53:21.423	warn	(6070) ELEVATED publishToState: value generated '159' from device 804b50fffe0475a0 for 'Link quality'
                                  zigbee.0	2021-04-25 17:53:21.423	warn	(6070) ELEVATED publishToState: message received '{"linkquality":159}' from device 804b50fffe0475a0 type 'NAS-AB02B0'
                                  zigbee.0	2021-04-25 17:53:21.173	warn	(6070) ELEVATED publishToState: value generated '159' from device 804b50fffe0475a0 for 'Link quality'
                                  zigbee.0	2021-04-25 17:53:21.173	warn	(6070) ELEVATED publishToState: message received '{"linkquality":159}' from device 804b50fffe0475a0 type 'NAS-AB02B0'
                                  zigbee.0	2021-04-25 17:53:20.916	warn	(6070) ELEVATED publishToState: value generated '159' from device 804b50fffe0475a0 for 'Link quality'
                                  zigbee.0	2021-04-25 17:53:20.916	warn	(6070) ELEVATED publishToState: message received '{"linkquality":159}' from device 804b50fffe0475a0 type 'NAS-AB02B0'
                                  zigbee.0	2021-04-25 17:53:20.664	warn	(6070) ELEVATED publishToState: value generated '159' from device 804b50fffe0475a0 for 'Link quality'
                                  zigbee.0	2021-04-25 17:53:20.664	warn	(6070) ELEVATED publishToState: message received '{"linkquality":159}' from device 804b50fffe0475a0 type 'NAS-AB02B0'
                                  zigbee.0	2021-04-25 17:53:20.412	warn	(6070) ELEVATED publishToState: value generated '162' from device 804b50fffe0475a0 for 'Link quality'
                                  zigbee.0	2021-04-25 17:53:20.412	warn	(6070) ELEVATED publishToState: message received '{"linkquality":162}' from device 804b50fffe0475a0 type 'NAS-AB02B0'
                                  zigbee.0	2021-04-25 17:53:20.158	warn	(6070) ELEVATED publishToState: value generated '159' from device 804b50fffe0475a0 for 'Link quality'
                                  zigbee.0	2021-04-25 17:53:20.158	warn	(6070) ELEVATED publishToState: message received '{"linkquality":159}' from device 804b50fffe0475a0 type 'NAS-AB02B0'
                                  zigbee.0	2021-04-25 17:53:19.906	warn	(6070) ELEVATED publishToState: value generated '159' from device 804b50fffe0475a0 for 'Link quality'
                                  zigbee.0	2021-04-25 17:53:19.906	warn	(6070) ELEVATED publishToState: message received '{"linkquality":159}' from device 804b50fffe0475a0 type 'NAS-AB02B0'
                                  zigbee.0	2021-04-25 17:53:05.790	warn	(6070) Device '0x804b50fffe0475a0' announced itself
                                  zigbee.0	2021-04-25 17:53:05.604	info	(6070) Starting interview of '0x804b50fffe0475a0'
                                  zigbee.0	2021-04-25 17:52:53.621	info	(6070) Zigbee: allowing new devices to join.
                                  

                                  Siren Pairing.JPG

                                  1 Antwort Letzte Antwort
                                  0
                                  • X Offline
                                    X Offline
                                    xxsirosxx
                                    schrieb am zuletzt editiert von
                                    #75

                                    Hallo

                                    Habe das Update eingespielt was soweit ohne Probleme am Laufen ist.
                                    Heute wollte ich einen Taster anlernen was mir weder über den Coordinator noch über einen Router möglich ist..
                                    Beide suchen und suchen aber finden nichts.
                                    Was komisch ist seit dem Update habe ich zwei Coordinator.
                                    Vielleicht kann mir einer von euch weiterhelfen wie ich den zweiten wieder loswerde.

                                    4.jpg 3.jpg 2.jpg 1.png

                                    1 Antwort Letzte Antwort
                                    0
                                    • M Offline
                                      M Offline
                                      Muchul
                                      schrieb am zuletzt editiert von
                                      #76

                                      Hallo,

                                      ich habe eine neue Fernbedienung dessen Design mir gut gefällt und es würde mich freuen, wenn diese in naher Zukunft mit iobroker nutzbar würde.
                                      https://www.immaxneo.cz/de/produkte/immax-neo-remote-control-rgbcct-zigbee-3-0/

                                      Da ich weder englisch kann noch Programmieren benötige ich also Hilfe.
                                      1cec2280-ce74-4bfa-9fe0-d830ad8f7110-image.png

                                      cd6421cb-15e1-450d-bf40-8e8885633bd2-image.png

                                      Wenn ich das richtig verstanden habe ist es noch nicht im zigbee2mqtt drin.
                                      https://github.com/Koenkk/zigbee2mqtt/issues/5314

                                      Besteht die Chance, das das irgendwann mal reinkommt?
                                      Ich hätte kein Problem damit, wenn es 2-3 Monate dauert.

                                      arteckA 1 Antwort Letzte Antwort
                                      0
                                      • M Muchul

                                        Hallo,

                                        ich habe eine neue Fernbedienung dessen Design mir gut gefällt und es würde mich freuen, wenn diese in naher Zukunft mit iobroker nutzbar würde.
                                        https://www.immaxneo.cz/de/produkte/immax-neo-remote-control-rgbcct-zigbee-3-0/

                                        Da ich weder englisch kann noch Programmieren benötige ich also Hilfe.
                                        1cec2280-ce74-4bfa-9fe0-d830ad8f7110-image.png

                                        cd6421cb-15e1-450d-bf40-8e8885633bd2-image.png

                                        Wenn ich das richtig verstanden habe ist es noch nicht im zigbee2mqtt drin.
                                        https://github.com/Koenkk/zigbee2mqtt/issues/5314

                                        Besteht die Chance, das das irgendwann mal reinkommt?
                                        Ich hätte kein Problem damit, wenn es 2-3 Monate dauert.

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

                                        @muchul hast du den mal in den Ausschliessen tab hinzugefügt ?

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

                                        1 Antwort Letzte Antwort
                                        0
                                        • M Offline
                                          M Offline
                                          Muchul
                                          schrieb am zuletzt editiert von Muchul
                                          #78

                                          Hallo @arteck,

                                          ich weis nicht genau wie das Funktioniert.
                                          Daher beschreibe ich mal, was ich alles gemacht habe:

                                          Mein System ist, laut Info Adapter aktuell und auf Stable.

                                          Jedoch habe ich den Zigbee Adapter aus dem Git auf Version 1.5.1 gebracht.
                                          Danach habe ich das Gerät im Ausschließen Tab hinzugefügt.

                                          Jetzt wusste ich nicht, was noch gemacht werden müsste.
                                          Ein Restart des Adapters war erfolglos:

                                          Also Adapter gestoppt.
                                          Ein Upload durchgeführt.
                                          Adapter gestartet.
                                          5 Minuten gewartet und zwischendurch auch mehrmals Tasten auf der Fernbedienung gedrückt.

                                          In den Logs sehe ich das das Gerät fleißig am senden ist und das es auch ankommt.
                                          Deswegen nehme ich an, das es im zigbee2mqtt noch nicht integriert wurde.

                                          Keine Veränderung, außer das das Gerät jetzt im exclude Ordner ist.
                                          Daten Punkte werden keine weiteren angelegt:

                                          0e2c68f6-2eb8-468c-b556-10898baccb70-image.png

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


                                          Support us

                                          ioBroker
                                          Community Adapters
                                          Donate

                                          317

                                          Online

                                          32.4k

                                          Benutzer

                                          81.4k

                                          Themen

                                          1.3m

                                          Beiträge
                                          Community
                                          Impressum | Datenschutz-Bestimmungen | Nutzungsbedingungen
                                          ioBroker Community 2014-2025
                                          logo
                                          • Anmelden

                                          • Du hast noch kein Konto? Registrieren

                                          • Anmelden oder registrieren, um zu suchen
                                          • Erster Beitrag
                                            Letzter Beitrag
                                          0
                                          • Aktuell
                                          • Tags
                                          • Ungelesen 0
                                          • Kategorien
                                          • Unreplied
                                          • Beliebt
                                          • GitHub
                                          • Docu
                                          • Hilfe