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. Tester wanted - Zigbee Adapter 3.1

NEWS

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

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

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

Tester wanted - Zigbee Adapter 3.1

Geplant Angeheftet Gesperrt Verschoben Tester
testerzhczigbeezigbee 3.1
270 Beiträge 17 Kommentatoren 16.3k Aufrufe 16 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.
  • FabioF Fabio

    @asgothian ja und die Steckdose ist da und wird auch gechalten etc.

    Screenshot 2025-10-01 110530.png

    D Offline
    D Offline
    dimaiv
    schrieb am zuletzt editiert von dimaiv
    #237

    @fabio
    Danke.

    @Asgothian

    Bei mir läuft das Pairing genau so ab, egal, Strombetrieben oder ein Batteriegerät.

    Bei mir gibt's auch Probleme mit "Edit"button, wo man die Name ändern kann. Was ich nicht erklären kann, bei manchen funktioniert, bei anderen nicht (innerhalb von einer Instanz). Also, reagiert gar nicht auf Mausklick.

    ioBroker- NUC8i3 / Proxmox / VM
    Node.js v22.21.0
    NPM v10.9.4
    JS controller 7.0.7
    Admin 7.7.19
    ZigBee Adapter 3.2.5
    Zigbee LAN Gateway CC2652P
    Zigbee Firmware 20250321

    AsgothianA 1 Antwort Letzte Antwort
    0
    • D dimaiv

      @fabio
      Danke.

      @Asgothian

      Bei mir läuft das Pairing genau so ab, egal, Strombetrieben oder ein Batteriegerät.

      Bei mir gibt's auch Probleme mit "Edit"button, wo man die Name ändern kann. Was ich nicht erklären kann, bei manchen funktioniert, bei anderen nicht (innerhalb von einer Instanz). Also, reagiert gar nicht auf Mausklick.

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

      @dimaiv sagte in Tester wanted - Zigbee Adapter 3.1:

      Bei mir gibt's auch Probleme mit "Edit"button, wo man die Name ändern kann. Was ich nicht erklären kann, bei manchen funktioniert, bei anderen nicht (innerhalb von einer Instanz). Also, reagiert gar nicht auf Mausklick.

      bitte nochmal neu installieren - da gab es noch eine Bug wenn es keine Gruppen gab.

      Hab ich heute morgen gefixed.

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

      1 Antwort Letzte Antwort
      0
      • FabioF Fabio

        @asgothian ja und die Steckdose ist da und wird auch gechalten etc.

        Screenshot 2025-10-01 110530.png

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

        @fabio sagte in Tester wanted - Zigbee Adapter 3.1:

        @asgothian ja und die Steckdose ist da und wird auch gechalten etc.

        Screenshot 2025-10-01 110530.png

        Noch eine Frage: Als du diese Steckdose angelernt hast, gab es da in dem dazu gehörenden Zigbee-Netzwerk bereits weitere Steckdosen dieses Typs, oder war dieser Typ in diesem Zigbee-Netzwerk neu ?

        A.

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

        D FabioF 2 Antworten Letzte Antwort
        0
        • AsgothianA Asgothian

          @fabio sagte in Tester wanted - Zigbee Adapter 3.1:

          @asgothian ja und die Steckdose ist da und wird auch gechalten etc.

          Screenshot 2025-10-01 110530.png

          Noch eine Frage: Als du diese Steckdose angelernt hast, gab es da in dem dazu gehörenden Zigbee-Netzwerk bereits weitere Steckdosen dieses Typs, oder war dieser Typ in diesem Zigbee-Netzwerk neu ?

          A.

          D Offline
          D Offline
          dimaiv
          schrieb am zuletzt editiert von dimaiv
          #240

          @asgothian
          Gerade frisch vom Git installiert.
          Jetzt Stürzt der Adapter beim Pairing wieder ab :

          2025-10-01 12:31:08.739 - info: zigbee.0 (15531) Opening zigbee Network for 120 seconds
          2025-10-01 12:31:09.208 - warn: zigbee.0 (15531) Resolve Entity did not manage to find a mapped device for 0x84fd27fffed2450f of type undefined
          2025-10-01 12:31:09.213 - error: zigbee.0 (15531) Resolve entity error: Cannot read properties of undefined (reading 'model')
          2025-10-01 12:31:09.213 - error: zigbee.0 (15531) handleDeviceInterview: Cannot read properties of undefined (reading 'name')
          2025-10-01 12:31:12.642 - warn: zigbee.0 (15531) Resolve Entity did not manage to find a mapped device for 0x84fd27fffed2450f of type undefined
          2025-10-01 12:31:12.643 - error: zigbee.0 (15531) Resolve entity error: Cannot read properties of undefined (reading 'model')
          2025-10-01 12:31:17.239 - info: admin.0 (2458) ==> Connected system.user.admin from ::ffff:192.168.2.100
          2025-10-01 12:31:18.540 - info: zigbee.0 (15531) message {"type":"read","device":{"_events":{},"_eventsCount":0,"_maxListeners":100,"ID":4,"_endpoints":[{"_events":{},"_eventsCount":0,"_maxListeners":100,"inputClusters":[],"outputClusters":[],"ID":1,"clusters":{},"deviceIeeeAddress":"0x84fd27fffed2450f","deviceNetworkAddress":61526,"_binds":[],"_configuredReportings":[],"meta":{},"pendingRequests":{"sendInProgress":false,"id":1,"deviceIeeeAddress":"0x84fd27fffed2450f"}}],"_ieeeAddr":"0x84fd27fffed2450f","_interviewState":"IN_PROGRESS","_lastSeen":1759314678537,"_networkAddress":61526,"_type":"Unknown","_linkquality":80,"_skipDefaultResponse":false,"_pendingRequestTimeout":0,"_customClusters":{},"meta":{}},"endpoint":{"_events":{},"_eventsCount":0,"_maxListeners":100,"inputClusters":[],"outputClusters":[],"ID":1,"clusters":{},"deviceIeeeAddress":"0x84fd27fffed2450f","deviceNetworkAddress":61526,"_binds":[],"_configuredReportings":[],"meta":{},"pendingRequests":{"sendInProgress":false,"id":1,"deviceIeeeAddress":"0x84fd27fffed2450f"}},"data":["localTime"],"linkquality":80,"groupID":0,"cluster":"genTime","meta":{"rawData":{"type":"Buffer","data":[0,79,0,7,0]},"zclTransactionSequenceNumber":79,"frameControl":{"frameType":0,"manufacturerSpecific":false,"direction":0,"disableDefaultResponse":false,"reservedBits":0}}} received during interview.
          2025-10-01 12:31:18.540 - warn: zigbee.0 (15531) Resolve Entity did not manage to find a mapped device for 0x84fd27fffed2450f of type undefined
          2025-10-01 12:31:18.542 - error: zigbee.0 (15531) Resolve entity error: Cannot read properties of undefined (reading 'model')
          2025-10-01 12:31:18.543 - error: zigbee.0 (15531) 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().
          2025-10-01 12:31:18.543 - error: zigbee.0 (15531) unhandled promise rejection: Cannot read properties of undefined (reading 'device')
          2025-10-01 12:31:18.543 - error: zigbee.0 (15531) TypeError: Cannot read properties of undefined (reading 'device')
          at StatesController.onZigbeeEvent (/opt/iobroker/node_modules/iobroker.zigbee/lib/statescontroller.js:1260:31)
          at ZigbeeController.emit (node:events:524:28)
          at ZigbeeController.emit (node:domain:489:12)
          at ZigbeeController.event (/opt/iobroker/node_modules/iobroker.zigbee/lib/zigbeecontroller.js:355:14)
          at ZigbeeController.handleMessage (/opt/iobroker/node_modules/iobroker.zigbee/lib/zigbeecontroller.js:1005:14)
          at processTicksAndRejections (node:internal/process/task_queues:95:5)
          2025-10-01 12:31:18.544 - error: zigbee.0 (15531) Cannot read properties of undefined (reading 'device')
          2025-10-01 12:31:18.545 - error: zigbee.0 (15531) 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().
          2025-10-01 12:31:18.546 - error: zigbee.0 (15531) unhandled promise rejection: Cannot read properties of undefined (reading 'options')
          2025-10-01 12:31:18.546 - error: zigbee.0 (15531) TypeError: Cannot read properties of undefined (reading 'options')
          at ZigbeeController.handleMessage (/opt/iobroker/node_modules/iobroker.zigbee/lib/zigbeecontroller.js:1009:39)
          at processTicksAndRejections (node:internal/process/task_queues:95:5)
          2025-10-01 12:31:18.546 - error: zigbee.0 (15531) Cannot read properties of undefined (reading 'options')
          2025-10-01 12:31:18.553 - info: zigbee.0 (15531) Halting zigbee adapter. Restart delay is at least 30 seconds.
          2025-10-01 12:31:18.553 - info: zigbee.0 (15531) cleaning everything up
          2025-10-01 12:31:18.553 - info: zigbee.0 (15531) Saved local configuration data
          2025-10-01 12:31:18.553 - info: zigbee.0 (15531) cleanup successful
          2025-10-01 12:31:18.553 - info: zigbee.0 (15531) terminating
          2025-10-01 12:31:18.554 - warn: zigbee.0 (15531) Terminated (UNCAUGHT_EXCEPTION): Without reason
          2025-10-01 12:31:18.554 - info: zigbee.0 (15531) zigbecontroller stopped successfully - ZH was not running
          2025-10-01 12:31:18.554 - warn: zigbee.0 (15531) Resolve Entity did not manage to find a mapped device for 0x84fd27fffed2450f of type undefined
          2025-10-01 12:31:18.554 - error: zigbee.0 (15531) Resolve entity error: Cannot read properties of undefined (reading 'model')
          2025-10-01 12:31:18.743 - info: zigbee.0 (15531) message {"type":"read","device":{"_events":{},"_eventsCount":0,"_maxListeners":100,"ID":4,"_endpoints":[{"_events":{},"_eventsCount":0,"_maxListeners":100,"inputClusters":[],"outputClusters":[],"ID":1,"clusters":{},"deviceIeeeAddress":"0x84fd27fffed2450f","deviceNetworkAddress":61526,"_binds":[],"_configuredReportings":[],"meta":{},"pendingRequests":{"sendInProgress":false,"id":1,"deviceIeeeAddress":"0x84fd27fffed2450f"}}],"_ieeeAddr":"0x84fd27fffed2450f","_interviewState":"IN_PROGRESS","_lastSeen":1759314678743,"_networkAddress":61526,"_type":"Unknown","_linkquality":80,"_skipDefaultResponse":false,"_pendingRequestTimeout":0,"_customClusters":{},"meta":{}},"endpoint":{"_events":{},"_eventsCount":0,"_maxListeners":100,"inputClusters":[],"outputClusters":[],"ID":1,"clusters":{},"deviceIeeeAddress":"0x84fd27fffed2450f","deviceNetworkAddress":61526,"_binds":[],"_configuredReportings":[],"meta":{},"pendingRequests":{"sendInProgress":false,"id":1,"deviceIeeeAddress":"0x84fd27fffed2450f"}},"data":["localTime"],"linkquality":80,"groupID":0,"cluster":"genTime","meta":{"rawData":{"type":"Buffer","data":[0,79,0,7,0]},"zclTransactionSequenceNumber":79,"frameControl":{"frameType":0,"manufacturerSpecific":false,"direction":0,"disableDefaultResponse":false,"reservedBits":0}}} received during interview.
          2025-10-01 12:31:18.744 - warn: zigbee.0 (15531) Resolve Entity did not manage to find a mapped device for 0x84fd27fffed2450f of type undefined
          2025-10-01 12:31:18.744 - error: zigbee.0 (15531) Resolve entity error: Cannot read properties of undefined (reading 'model')
          2025-10-01 12:31:18.744 - error: zigbee.0 (15531) 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().
          2025-10-01 12:31:18.744 - error: zigbee.0 (15531) unhandled promise rejection: Cannot read properties of undefined (reading 'device')
          2025-10-01 12:31:18.745 - error: zigbee.0 (15531) TypeError: Cannot read properties of undefined (reading 'device')
          at StatesController.onZigbeeEvent (/opt/iobroker/node_modules/iobroker.zigbee/lib/statescontroller.js:1260:31)
          at ZigbeeController.emit (node:events:524:28)
          at ZigbeeController.emit (node:domain:489:12)
          at ZigbeeController.event (/opt/iobroker/node_modules/iobroker.zigbee/lib/zigbeecontroller.js:355:14)
          at ZigbeeController.handleMessage (/opt/iobroker/node_modules/iobroker.zigbee/lib/zigbeecontroller.js:1005:14)
          at processTicksAndRejections (node:internal/process/task_queues:95:5)
          2025-10-01 12:31:18.745 - error: zigbee.0 (15531) Cannot read properties of undefined (reading 'device')
          2025-10-01 12:31:18.746 - error: zigbee.0 (15531) 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().
          2025-10-01 12:31:18.746 - error: zigbee.0 (15531) unhandled promise rejection: Cannot read properties of undefined (reading 'options')
          2025-10-01 12:31:18.747 - error: zigbee.0 (15531) TypeError: Cannot read properties of undefined (reading 'options')
          at ZigbeeController.handleMessage (/opt/iobroker/node_modules/iobroker.zigbee/lib/zigbeecontroller.js:1009:39)
          at processTicksAndRejections (node:internal/process/task_queues:95:5)
          2025-10-01 12:31:18.747 - error: zigbee.0 (15531) Cannot read properties of undefined (reading 'options')
          2025-10-01 12:31:18.956 - info: zigbee.0 (15531) message {"type":"read","device":{"_events":{},"_eventsCount":0,"_maxListeners":100,"ID":4,"_endpoints":[{"_events":{},"_eventsCount":0,"_maxListeners":100,"inputClusters":[],"outputClusters":[],"ID":1,"clusters":{},"deviceIeeeAddress":"0x84fd27fffed2450f","deviceNetworkAddress":61526,"_binds":[],"_configuredReportings":[],"meta":{},"pendingRequests":{"sendInProgress":false,"id":1,"deviceIeeeAddress":"0x84fd27fffed2450f"}}],"_ieeeAddr":"0x84fd27fffed2450f","_interviewState":"IN_PROGRESS","_lastSeen":1759314678955,"_networkAddress":61526,"_type":"Unknown","_linkquality":80,"_skipDefaultResponse":false,"_pendingRequestTimeout":0,"_customClusters":{},"meta":{}},"endpoint":{"_events":{},"_eventsCount":0,"_maxListeners":100,"inputClusters":[],"outputClusters":[],"ID":1,"clusters":{},"deviceIeeeAddress":"0x84fd27fffed2450f","deviceNetworkAddress":61526,"_binds":[],"_configuredReportings":[],"meta":{},"pendingRequests":{"sendInProgress":false,"id":1,"deviceIeeeAddress":"0x84fd27fffed2450f"}},"data":["localTime"],"linkquality":80,"groupID":0,"cluster":"genTime","meta":{"rawData":{"type":"Buffer","data":[0,79,0,7,0]},"zclTransactionSequenceNumber":79,"frameControl":{"frameType":0,"manufacturerSpecific":false,"direction":0,"disableDefaultResponse":false,"reservedBits":0}}} received during interview.
          2025-10-01 12:31:18.956 - warn: zigbee.0 (15531) Resolve Entity did not manage to find a mapped device for 0x84fd27fffed2450f of type undefined
          2025-10-01 12:31:18.956 - error: zigbee.0 (15531) Resolve entity error: Cannot read properties of undefined (reading 'model')
          2025-10-01 12:31:18.956 - error: zigbee.0 (15531) 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().
          2025-10-01 12:31:18.957 - error: zigbee.0 (15531) unhandled promise rejection: Cannot read properties of undefined (reading 'device')
          2025-10-01 12:31:18.957 - error: zigbee.0 (15531) TypeError: Cannot read properties of undefined (reading 'device')
          at StatesController.onZigbeeEvent (/opt/iobroker/node_modules/iobroker.zigbee/lib/statescontroller.js:1260:31)
          at ZigbeeController.emit (node:events:524:28)
          at ZigbeeController.emit (node:domain:489:12)
          at ZigbeeController.event (/opt/iobroker/node_modules/iobroker.zigbee/lib/zigbeecontroller.js:355:14)
          at ZigbeeController.handleMessage (/opt/iobroker/node_modules/iobroker.zigbee/lib/zigbeecontroller.js:1005:14)
          at processTicksAndRejections (node:internal/process/task_queues:95:5)
          2025-10-01 12:31:18.957 - error: zigbee.0 (15531) Cannot read properties of undefined (reading 'device')
          2025-10-01 12:31:18.959 - error: zigbee.0 (15531) 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().
          2025-10-01 12:31:18.959 - error: zigbee.0 (15531) unhandled promise rejection: Cannot read properties of undefined (reading 'options')
          2025-10-01 12:31:18.959 - error: zigbee.0 (15531) TypeError: Cannot read properties of undefined (reading 'options')
          at ZigbeeController.handleMessage (/opt/iobroker/node_modules/iobroker.zigbee/lib/zigbeecontroller.js:1009:39)
          at processTicksAndRejections (node:internal/process/task_queues:95:5)
          2025-10-01 12:31:18.959 - error: zigbee.0 (15531) Cannot read properties of undefined (reading 'options')
          2025-10-01 12:31:19.066 - error: host.Test-IoBroker Caught by controller[1]: 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:
          2025-10-01 12:31:19.066 - error: host.Test-IoBroker Caught by controller[1]: TypeError: Cannot read properties of undefined (reading 'device')
          2025-10-01 12:31:19.066 - error: host.Test-IoBroker Caught by controller[1]: at StatesController.onZigbeeEvent (/opt/iobroker/node_modules/iobroker.zigbee/lib/statescontroller.js:1260:31)
          2025-10-01 12:31:19.066 - error: host.Test-IoBroker Caught by controller[1]: at ZigbeeController.emit (node:events:524:28)
          2025-10-01 12:31:19.066 - error: host.Test-IoBroker Caught by controller[1]: at ZigbeeController.emit (node:domain:489:12)
          2025-10-01 12:31:19.066 - error: host.Test-IoBroker Caught by controller[1]: at ZigbeeController.event (/opt/iobroker/node_modules/iobroker.zigbee/lib/zigbeecontroller.js:355:14)
          2025-10-01 12:31:19.066 - error: host.Test-IoBroker Caught by controller[1]: at ZigbeeController.handleMessage (/opt/iobroker/node_modules/iobroker.zigbee/lib/zigbeecontroller.js:1005:14)
          2025-10-01 12:31:19.066 - error: host.Test-IoBroker Caught by controller[1]: at processTicksAndRejections (node:internal/process/task_queues:95:5)
          2025-10-01 12:31:19.067 - error: host.Test-IoBroker Caught by controller[1]: 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:
          2025-10-01 12:31:19.067 - error: host.Test-IoBroker Caught by controller[1]: TypeError: Cannot read properties of undefined (reading 'options')
          2025-10-01 12:31:19.067 - error: host.Test-IoBroker Caught by controller[1]: at ZigbeeController.handleMessage (/opt/iobroker/node_modules/iobroker.zigbee/lib/zigbeecontroller.js:1009:39)
          2025-10-01 12:31:19.067 - error: host.Test-IoBroker Caught by controller[1]: at processTicksAndRejections (node:internal/process/task_queues:95:5)
          2025-10-01 12:31:19.067 - error: host.Test-IoBroker Caught by controller[2]: 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:
          2025-10-01 12:31:19.067 - error: host.Test-IoBroker Caught by controller[3]: TypeError: Cannot read properties of undefined (reading 'device')
          2025-10-01 12:31:19.067 - error: host.Test-IoBroker Caught by controller[3]: at StatesController.onZigbeeEvent (/opt/iobroker/node_modules/iobroker.zigbee/lib/statescontroller.js:1260:31)
          2025-10-01 12:31:19.067 - error: host.Test-IoBroker Caught by controller[3]: at ZigbeeController.emit (node:events:524:28)
          2025-10-01 12:31:19.067 - error: host.Test-IoBroker Caught by controller[3]: at ZigbeeController.emit (node:domain:489:12)
          2025-10-01 12:31:19.067 - error: host.Test-IoBroker Caught by controller[3]: at ZigbeeController.event (/opt/iobroker/node_modules/iobroker.zigbee/lib/zigbeecontroller.js:355:14)
          2025-10-01 12:31:19.067 - error: host.Test-IoBroker Caught by controller[3]: at ZigbeeController.handleMessage (/opt/iobroker/node_modules/iobroker.zigbee/lib/zigbeecontroller.js:1005:14)
          2025-10-01 12:31:19.067 - error: host.Test-IoBroker Caught by controller[3]: at processTicksAndRejections (node:internal/process/task_queues:95:5)
          2025-10-01 12:31:19.067 - error: host.Test-IoBroker Caught by controller[4]: 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:
          2025-10-01 12:31:19.067 - error: host.Test-IoBroker Caught by controller[5]: TypeError: Cannot read properties of undefined (reading 'options')
          2025-10-01 12:31:19.067 - error: host.Test-IoBroker Caught by controller[5]: at ZigbeeController.handleMessage (/opt/iobroker/node_modules/iobroker.zigbee/lib/zigbeecontroller.js:1009:39)
          2025-10-01 12:31:19.067 - error: host.Test-IoBroker Caught by controller[5]: at processTicksAndRejections (node:internal/process/task_queues:95:5)
          2025-10-01 12:31:19.067 - error: host.Test-IoBroker Caught by controller[6]: 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:
          2025-10-01 12:31:19.067 - error: host.Test-IoBroker Caught by controller[7]: TypeError: Cannot read properties of undefined (reading 'device')
          2025-10-01 12:31:19.067 - error: host.Test-IoBroker Caught by controller[7]: at StatesController.onZigbeeEvent (/opt/iobroker/node_modules/iobroker.zigbee/lib/statescontroller.js:1260:31)
          2025-10-01 12:31:19.067 - error: host.Test-IoBroker Caught by controller[7]: at ZigbeeController.emit (node:events:524:28)
          2025-10-01 12:31:19.067 - error: host.Test-IoBroker Caught by controller[7]: at ZigbeeController.emit (node:domain:489:12)
          2025-10-01 12:31:19.067 - error: host.Test-IoBroker Caught by controller[7]: at ZigbeeController.event (/opt/iobroker/node_modules/iobroker.zigbee/lib/zigbeecontroller.js:355:14)
          2025-10-01 12:31:19.067 - error: host.Test-IoBroker Caught by controller[7]: at ZigbeeController.handleMessage (/opt/iobroker/node_modules/iobroker.zigbee/lib/zigbeecontroller.js:1005:14)
          2025-10-01 12:31:19.067 - error: host.Test-IoBroker Caught by controller[7]: at processTicksAndRejections (node:internal/process/task_queues:95:5)
          2025-10-01 12:31:19.068 - error: host.Test-IoBroker Caught by controller[8]: 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:
          2025-10-01 12:31:19.068 - error: host.Test-IoBroker Caught by controller[9]: TypeError: Cannot read properties of undefined (reading 'options')
          2025-10-01 12:31:19.068 - error: host.Test-IoBroker Caught by controller[9]: at ZigbeeController.handleMessage (/opt/iobroker/node_modules/iobroker.zigbee/lib/zigbeecontroller.js:1009:39)
          2025-10-01 12:31:19.068 - error: host.Test-IoBroker Caught by controller[9]: at processTicksAndRejections (node:internal/process/task_queues:95:5)
          2025-10-01 12:31:19.068 - error: host.Test-IoBroker instance system.adapter.zigbee.0 terminated with code 6 (UNCAUGHT_EXCEPTION)
          2025-10-01 12:31:19.068 - info: host.Test-IoBroker Restart adapter system.adapter.zigbee.0 because enabled
          

          Und lässt sich nicht mehr ordentlich starten.
          Hier automatischer restart :

          2025-10-01 12:31:49.284 - info: host.Test-IoBroker instance system.adapter.zigbee.0 in version "3.1.5-alpha.2" (non-npm: ioBroker/ioBroker.zigbee) started with pid 15575
          2025-10-01 12:31:49.891 - info: zigbee.0 (15575) starting. Version 3.1.5-alpha.2 (non-npm: ioBroker/ioBroker.zigbee) in /opt/iobroker/node_modules/iobroker.zigbee, node: v20.19.5, js-controller: 7.0.7
          2025-10-01 12:31:49.900 - info: zigbee.0 (15575) Adapter ready - starting subsystems. Adapter is running in info mode.
          2025-10-01 12:31:49.900 - info: zigbee.0 (15575) init localConfig
          2025-10-01 12:31:49.916 - info: zigbee.0 (15575) --- creating device debug ---
          2025-10-01 12:31:49.917 - info: zigbee.0 (15575) Autostart Zigbee subsystem
          2025-10-01 12:31:49.917 - info: zigbee.0 (15575) Starting Adapter npm ...
          2025-10-01 12:31:49.924 - info: zigbee.0 (15575) Installed Version: ioBroker/ioBroker.zigbee (Converters 25.31.0 Herdsman 6.1.3)
          2025-10-01 12:31:49.925 - info: zigbee.0 (15575) configured transmit power :
          2025-10-01 12:31:49.925 - info: zigbee.0 (15575) Starting Zigbee-Herdsman
          2025-10-01 12:31:51.728 - info: zigbee.0 (15575) Zigbee-Herdsman started successfully with Coordinator firmware version: ZStack3x0 : 20240710 (2-1.2.7.1)
          2025-10-01 12:31:51.728 - info: zigbee.0 (15575) Unable to disable LED, unsupported function.
          2025-10-01 12:31:51.766 - info: zigbee.0 (15575) 0xe0798dfffe746ae6 (addr 11547): HG06104A - Lidl Livarno Home RGB+CCT LED light strip 2m (Router)
          2025-10-01 12:31:51.769 - info: zigbee.0 (15575) 0x00158d0005062c00 (addr 16444): MLI-404011/MLI-404049 - Müller Licht Tint remote control (EndDevice)
          2025-10-01 12:31:51.775 - warn: zigbee.0 (15575) Resolve Entity did not manage to find a mapped device for 0x84fd27fffed2450f of type undefined
          2025-10-01 12:31:51.779 - error: zigbee.0 (15575) Resolve entity error: Cannot read properties of undefined (reading 'model')
          2025-10-01 12:31:51.779 - info: zigbee.0 (15575) 3 devices are part of the network
          2025-10-01 12:31:51.779 - info: zigbee.0 (15575) Zigbee started
          2025-10-01 12:31:51.781 - warn: zigbee.0 (15575) Resolve Entity did not manage to find a mapped device for 0x84fd27fffed2450f of type undefined
          2025-10-01 12:31:51.782 - error: zigbee.0 (15575) Resolve entity error: Cannot read properties of undefined (reading 'model')
          2025-10-01 12:31:51.783 - warn: zigbee.0 (15575) Resolve Entity did not manage to find a mapped device for 0x84fd27fffed2450f of type undefined
          2025-10-01 12:31:51.784 - error: zigbee.0 (15575) Resolve entity error: Cannot read properties of undefined (reading 'model')
          2025-10-01 12:31:51.784 - error: zigbee.0 (15575) 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().
          2025-10-01 12:31:51.784 - error: zigbee.0 (15575) unhandled promise rejection: Cannot read properties of undefined (reading 'options')
          2025-10-01 12:31:51.784 - error: zigbee.0 (15575) TypeError: Cannot read properties of undefined (reading 'options')
          at DeviceEvent.onZigbeeStarted (/opt/iobroker/node_modules/iobroker.zigbee/lib/zbDeviceEvent.js:15:77)
          at processTicksAndRejections (node:internal/process/task_queues:95:5)
          at async Promise.all (index 2)
          2025-10-01 12:31:51.784 - error: zigbee.0 (15575) Cannot read properties of undefined (reading 'options')
          2025-10-01 12:31:51.808 - info: zigbee.0 (15575) Halting zigbee adapter. Restart delay is at least 30 seconds.
          2025-10-01 12:31:51.809 - info: zigbee.0 (15575) cleaning everything up
          2025-10-01 12:31:51.809 - info: zigbee.0 (15575) Saved local configuration data
          2025-10-01 12:31:51.809 - info: zigbee.0 (15575) cleanup successful
          2025-10-01 12:31:51.809 - info: zigbee.0 (15575) terminating
          2025-10-01 12:31:51.810 - warn: zigbee.0 (15575) Terminated (UNCAUGHT_EXCEPTION): Without reason
          2025-10-01 12:31:51.810 - info: zigbee.0 (15575) zigbecontroller stopped successfully - ZH was not running
          2025-10-01 12:31:51.810 - warn: zigbee.0 (15575) Resolve Entity did not manage to find a mapped device for 0x84fd27fffed2450f of type undefined
          2025-10-01 12:31:51.811 - error: zigbee.0 (15575) Resolve entity error: Cannot read properties of undefined (reading 'model')
          2025-10-01 12:31:51.833 - info: zigbee.0 (15575) debug devices set to []
          2025-10-01 12:31:51.909 - warn: zigbee.0 (15575) Resolve Entity did not manage to find a mapped device for 0x84fd27fffed2450f of type undefined
          2025-10-01 12:31:51.910 - error: zigbee.0 (15575) Resolve entity error: Cannot read properties of undefined (reading 'model')
          2025-10-01 12:31:51.910 - warn: zigbee.0 (15575) resolveEntity returned no entity
          2025-10-01 12:31:52.322 - error: host.Test-IoBroker Caught by controller[0]: 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:
          2025-10-01 12:31:52.323 - error: host.Test-IoBroker Caught by controller[1]: TypeError: Cannot read properties of undefined (reading 'options')
          2025-10-01 12:31:52.323 - error: host.Test-IoBroker Caught by controller[1]: at DeviceEvent.onZigbeeStarted (/opt/iobroker/node_modules/iobroker.zigbee/lib/zbDeviceEvent.js:15:77)
          2025-10-01 12:31:52.323 - error: host.Test-IoBroker Caught by controller[1]: at processTicksAndRejections (node:internal/process/task_queues:95:5)
          2025-10-01 12:31:52.323 - error: host.Test-IoBroker Caught by controller[1]: at async Promise.all (index 2)
          2025-10-01 12:31:52.323 - error: host.Test-IoBroker Caught by controller[2]: allowing role change for colortemp
          2025-10-01 12:31:52.323 - error: host.Test-IoBroker Caught by controller[3]: allowing role change for colortemp_move
          2025-10-01 12:31:52.323 - error: host.Test-IoBroker Caught by controller[4]: allowing role change for hex_color
          2025-10-01 12:31:52.323 - error: host.Test-IoBroker Caught by controller[5]: allowing role change for color
          2025-10-01 12:31:52.323 - error: host.Test-IoBroker Caught by controller[6]: allowing role change for color_xy.x
          2025-10-01 12:31:52.326 - error: host.Test-IoBroker Caught by controller[7]: allowing role change for color_xy.y
          2025-10-01 12:31:52.327 - error: host.Test-IoBroker Caught by controller[8]: allowing role change for color_rgb.r
          2025-10-01 12:31:52.327 - error: host.Test-IoBroker Caught by controller[9]: allowing role change for color_rgb.g
          2025-10-01 12:31:52.327 - error: host.Test-IoBroker Caught by controller[10]: allowing role change for color_rgb.b
          2025-10-01 12:31:52.327 - error: host.Test-IoBroker Caught by controller[11]: allowing role change for color_power_on_behavior
          2025-10-01 12:31:52.327 - error: host.Test-IoBroker Caught by controller[12]: allowing role change for color_temperature_move
          2025-10-01 12:31:52.327 - error: host.Test-IoBroker Caught by controller[13]: allowing role change for color_move
          2025-10-01 12:31:52.327 - error: host.Test-IoBroker instance system.adapter.zigbee.0 terminated with code 6 (UNCAUGHT_EXCEPTION)
          2025-10-01 12:31:52.327 - info: host.Test-IoBroker Restart adapter system.adapter.zigbee.0 because enabled
          2025-10-01 12:32:18.906 - info: host.Test-IoBroker "system.adapter.zigbee.0" disabled
          2025-10-01 12:32:23.108 - error: zigbee.0 (15590) adapter disabled
          2025-10-01 12:32:23.111 - warn: zigbee.0 (15590) Terminated (NO_ADAPTER_CONFIG_FOUND): Without reason
          2025-10-01 12:32:23.625 - error: host.Test-IoBroker instance system.adapter.zigbee.0 terminated with code 3 (NO_ADAPTER_CONFIG_FOUND)
          2025-10-01 12:32:23.625 - info: host.Test-IoBroker Do not restart adapter system.adapter.zigbee.0 because disabled or deleted
          

          ioBroker- NUC8i3 / Proxmox / VM
          Node.js v22.21.0
          NPM v10.9.4
          JS controller 7.0.7
          Admin 7.7.19
          ZigBee Adapter 3.2.5
          Zigbee LAN Gateway CC2652P
          Zigbee Firmware 20250321

          AsgothianA 1 Antwort Letzte Antwort
          0
          • D dimaiv

            @asgothian
            Gerade frisch vom Git installiert.
            Jetzt Stürzt der Adapter beim Pairing wieder ab :

            2025-10-01 12:31:08.739 - info: zigbee.0 (15531) Opening zigbee Network for 120 seconds
            2025-10-01 12:31:09.208 - warn: zigbee.0 (15531) Resolve Entity did not manage to find a mapped device for 0x84fd27fffed2450f of type undefined
            2025-10-01 12:31:09.213 - error: zigbee.0 (15531) Resolve entity error: Cannot read properties of undefined (reading 'model')
            2025-10-01 12:31:09.213 - error: zigbee.0 (15531) handleDeviceInterview: Cannot read properties of undefined (reading 'name')
            2025-10-01 12:31:12.642 - warn: zigbee.0 (15531) Resolve Entity did not manage to find a mapped device for 0x84fd27fffed2450f of type undefined
            2025-10-01 12:31:12.643 - error: zigbee.0 (15531) Resolve entity error: Cannot read properties of undefined (reading 'model')
            2025-10-01 12:31:17.239 - info: admin.0 (2458) ==> Connected system.user.admin from ::ffff:192.168.2.100
            2025-10-01 12:31:18.540 - info: zigbee.0 (15531) message {"type":"read","device":{"_events":{},"_eventsCount":0,"_maxListeners":100,"ID":4,"_endpoints":[{"_events":{},"_eventsCount":0,"_maxListeners":100,"inputClusters":[],"outputClusters":[],"ID":1,"clusters":{},"deviceIeeeAddress":"0x84fd27fffed2450f","deviceNetworkAddress":61526,"_binds":[],"_configuredReportings":[],"meta":{},"pendingRequests":{"sendInProgress":false,"id":1,"deviceIeeeAddress":"0x84fd27fffed2450f"}}],"_ieeeAddr":"0x84fd27fffed2450f","_interviewState":"IN_PROGRESS","_lastSeen":1759314678537,"_networkAddress":61526,"_type":"Unknown","_linkquality":80,"_skipDefaultResponse":false,"_pendingRequestTimeout":0,"_customClusters":{},"meta":{}},"endpoint":{"_events":{},"_eventsCount":0,"_maxListeners":100,"inputClusters":[],"outputClusters":[],"ID":1,"clusters":{},"deviceIeeeAddress":"0x84fd27fffed2450f","deviceNetworkAddress":61526,"_binds":[],"_configuredReportings":[],"meta":{},"pendingRequests":{"sendInProgress":false,"id":1,"deviceIeeeAddress":"0x84fd27fffed2450f"}},"data":["localTime"],"linkquality":80,"groupID":0,"cluster":"genTime","meta":{"rawData":{"type":"Buffer","data":[0,79,0,7,0]},"zclTransactionSequenceNumber":79,"frameControl":{"frameType":0,"manufacturerSpecific":false,"direction":0,"disableDefaultResponse":false,"reservedBits":0}}} received during interview.
            2025-10-01 12:31:18.540 - warn: zigbee.0 (15531) Resolve Entity did not manage to find a mapped device for 0x84fd27fffed2450f of type undefined
            2025-10-01 12:31:18.542 - error: zigbee.0 (15531) Resolve entity error: Cannot read properties of undefined (reading 'model')
            2025-10-01 12:31:18.543 - error: zigbee.0 (15531) 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().
            2025-10-01 12:31:18.543 - error: zigbee.0 (15531) unhandled promise rejection: Cannot read properties of undefined (reading 'device')
            2025-10-01 12:31:18.543 - error: zigbee.0 (15531) TypeError: Cannot read properties of undefined (reading 'device')
            at StatesController.onZigbeeEvent (/opt/iobroker/node_modules/iobroker.zigbee/lib/statescontroller.js:1260:31)
            at ZigbeeController.emit (node:events:524:28)
            at ZigbeeController.emit (node:domain:489:12)
            at ZigbeeController.event (/opt/iobroker/node_modules/iobroker.zigbee/lib/zigbeecontroller.js:355:14)
            at ZigbeeController.handleMessage (/opt/iobroker/node_modules/iobroker.zigbee/lib/zigbeecontroller.js:1005:14)
            at processTicksAndRejections (node:internal/process/task_queues:95:5)
            2025-10-01 12:31:18.544 - error: zigbee.0 (15531) Cannot read properties of undefined (reading 'device')
            2025-10-01 12:31:18.545 - error: zigbee.0 (15531) 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().
            2025-10-01 12:31:18.546 - error: zigbee.0 (15531) unhandled promise rejection: Cannot read properties of undefined (reading 'options')
            2025-10-01 12:31:18.546 - error: zigbee.0 (15531) TypeError: Cannot read properties of undefined (reading 'options')
            at ZigbeeController.handleMessage (/opt/iobroker/node_modules/iobroker.zigbee/lib/zigbeecontroller.js:1009:39)
            at processTicksAndRejections (node:internal/process/task_queues:95:5)
            2025-10-01 12:31:18.546 - error: zigbee.0 (15531) Cannot read properties of undefined (reading 'options')
            2025-10-01 12:31:18.553 - info: zigbee.0 (15531) Halting zigbee adapter. Restart delay is at least 30 seconds.
            2025-10-01 12:31:18.553 - info: zigbee.0 (15531) cleaning everything up
            2025-10-01 12:31:18.553 - info: zigbee.0 (15531) Saved local configuration data
            2025-10-01 12:31:18.553 - info: zigbee.0 (15531) cleanup successful
            2025-10-01 12:31:18.553 - info: zigbee.0 (15531) terminating
            2025-10-01 12:31:18.554 - warn: zigbee.0 (15531) Terminated (UNCAUGHT_EXCEPTION): Without reason
            2025-10-01 12:31:18.554 - info: zigbee.0 (15531) zigbecontroller stopped successfully - ZH was not running
            2025-10-01 12:31:18.554 - warn: zigbee.0 (15531) Resolve Entity did not manage to find a mapped device for 0x84fd27fffed2450f of type undefined
            2025-10-01 12:31:18.554 - error: zigbee.0 (15531) Resolve entity error: Cannot read properties of undefined (reading 'model')
            2025-10-01 12:31:18.743 - info: zigbee.0 (15531) message {"type":"read","device":{"_events":{},"_eventsCount":0,"_maxListeners":100,"ID":4,"_endpoints":[{"_events":{},"_eventsCount":0,"_maxListeners":100,"inputClusters":[],"outputClusters":[],"ID":1,"clusters":{},"deviceIeeeAddress":"0x84fd27fffed2450f","deviceNetworkAddress":61526,"_binds":[],"_configuredReportings":[],"meta":{},"pendingRequests":{"sendInProgress":false,"id":1,"deviceIeeeAddress":"0x84fd27fffed2450f"}}],"_ieeeAddr":"0x84fd27fffed2450f","_interviewState":"IN_PROGRESS","_lastSeen":1759314678743,"_networkAddress":61526,"_type":"Unknown","_linkquality":80,"_skipDefaultResponse":false,"_pendingRequestTimeout":0,"_customClusters":{},"meta":{}},"endpoint":{"_events":{},"_eventsCount":0,"_maxListeners":100,"inputClusters":[],"outputClusters":[],"ID":1,"clusters":{},"deviceIeeeAddress":"0x84fd27fffed2450f","deviceNetworkAddress":61526,"_binds":[],"_configuredReportings":[],"meta":{},"pendingRequests":{"sendInProgress":false,"id":1,"deviceIeeeAddress":"0x84fd27fffed2450f"}},"data":["localTime"],"linkquality":80,"groupID":0,"cluster":"genTime","meta":{"rawData":{"type":"Buffer","data":[0,79,0,7,0]},"zclTransactionSequenceNumber":79,"frameControl":{"frameType":0,"manufacturerSpecific":false,"direction":0,"disableDefaultResponse":false,"reservedBits":0}}} received during interview.
            2025-10-01 12:31:18.744 - warn: zigbee.0 (15531) Resolve Entity did not manage to find a mapped device for 0x84fd27fffed2450f of type undefined
            2025-10-01 12:31:18.744 - error: zigbee.0 (15531) Resolve entity error: Cannot read properties of undefined (reading 'model')
            2025-10-01 12:31:18.744 - error: zigbee.0 (15531) 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().
            2025-10-01 12:31:18.744 - error: zigbee.0 (15531) unhandled promise rejection: Cannot read properties of undefined (reading 'device')
            2025-10-01 12:31:18.745 - error: zigbee.0 (15531) TypeError: Cannot read properties of undefined (reading 'device')
            at StatesController.onZigbeeEvent (/opt/iobroker/node_modules/iobroker.zigbee/lib/statescontroller.js:1260:31)
            at ZigbeeController.emit (node:events:524:28)
            at ZigbeeController.emit (node:domain:489:12)
            at ZigbeeController.event (/opt/iobroker/node_modules/iobroker.zigbee/lib/zigbeecontroller.js:355:14)
            at ZigbeeController.handleMessage (/opt/iobroker/node_modules/iobroker.zigbee/lib/zigbeecontroller.js:1005:14)
            at processTicksAndRejections (node:internal/process/task_queues:95:5)
            2025-10-01 12:31:18.745 - error: zigbee.0 (15531) Cannot read properties of undefined (reading 'device')
            2025-10-01 12:31:18.746 - error: zigbee.0 (15531) 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().
            2025-10-01 12:31:18.746 - error: zigbee.0 (15531) unhandled promise rejection: Cannot read properties of undefined (reading 'options')
            2025-10-01 12:31:18.747 - error: zigbee.0 (15531) TypeError: Cannot read properties of undefined (reading 'options')
            at ZigbeeController.handleMessage (/opt/iobroker/node_modules/iobroker.zigbee/lib/zigbeecontroller.js:1009:39)
            at processTicksAndRejections (node:internal/process/task_queues:95:5)
            2025-10-01 12:31:18.747 - error: zigbee.0 (15531) Cannot read properties of undefined (reading 'options')
            2025-10-01 12:31:18.956 - info: zigbee.0 (15531) message {"type":"read","device":{"_events":{},"_eventsCount":0,"_maxListeners":100,"ID":4,"_endpoints":[{"_events":{},"_eventsCount":0,"_maxListeners":100,"inputClusters":[],"outputClusters":[],"ID":1,"clusters":{},"deviceIeeeAddress":"0x84fd27fffed2450f","deviceNetworkAddress":61526,"_binds":[],"_configuredReportings":[],"meta":{},"pendingRequests":{"sendInProgress":false,"id":1,"deviceIeeeAddress":"0x84fd27fffed2450f"}}],"_ieeeAddr":"0x84fd27fffed2450f","_interviewState":"IN_PROGRESS","_lastSeen":1759314678955,"_networkAddress":61526,"_type":"Unknown","_linkquality":80,"_skipDefaultResponse":false,"_pendingRequestTimeout":0,"_customClusters":{},"meta":{}},"endpoint":{"_events":{},"_eventsCount":0,"_maxListeners":100,"inputClusters":[],"outputClusters":[],"ID":1,"clusters":{},"deviceIeeeAddress":"0x84fd27fffed2450f","deviceNetworkAddress":61526,"_binds":[],"_configuredReportings":[],"meta":{},"pendingRequests":{"sendInProgress":false,"id":1,"deviceIeeeAddress":"0x84fd27fffed2450f"}},"data":["localTime"],"linkquality":80,"groupID":0,"cluster":"genTime","meta":{"rawData":{"type":"Buffer","data":[0,79,0,7,0]},"zclTransactionSequenceNumber":79,"frameControl":{"frameType":0,"manufacturerSpecific":false,"direction":0,"disableDefaultResponse":false,"reservedBits":0}}} received during interview.
            2025-10-01 12:31:18.956 - warn: zigbee.0 (15531) Resolve Entity did not manage to find a mapped device for 0x84fd27fffed2450f of type undefined
            2025-10-01 12:31:18.956 - error: zigbee.0 (15531) Resolve entity error: Cannot read properties of undefined (reading 'model')
            2025-10-01 12:31:18.956 - error: zigbee.0 (15531) 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().
            2025-10-01 12:31:18.957 - error: zigbee.0 (15531) unhandled promise rejection: Cannot read properties of undefined (reading 'device')
            2025-10-01 12:31:18.957 - error: zigbee.0 (15531) TypeError: Cannot read properties of undefined (reading 'device')
            at StatesController.onZigbeeEvent (/opt/iobroker/node_modules/iobroker.zigbee/lib/statescontroller.js:1260:31)
            at ZigbeeController.emit (node:events:524:28)
            at ZigbeeController.emit (node:domain:489:12)
            at ZigbeeController.event (/opt/iobroker/node_modules/iobroker.zigbee/lib/zigbeecontroller.js:355:14)
            at ZigbeeController.handleMessage (/opt/iobroker/node_modules/iobroker.zigbee/lib/zigbeecontroller.js:1005:14)
            at processTicksAndRejections (node:internal/process/task_queues:95:5)
            2025-10-01 12:31:18.957 - error: zigbee.0 (15531) Cannot read properties of undefined (reading 'device')
            2025-10-01 12:31:18.959 - error: zigbee.0 (15531) 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().
            2025-10-01 12:31:18.959 - error: zigbee.0 (15531) unhandled promise rejection: Cannot read properties of undefined (reading 'options')
            2025-10-01 12:31:18.959 - error: zigbee.0 (15531) TypeError: Cannot read properties of undefined (reading 'options')
            at ZigbeeController.handleMessage (/opt/iobroker/node_modules/iobroker.zigbee/lib/zigbeecontroller.js:1009:39)
            at processTicksAndRejections (node:internal/process/task_queues:95:5)
            2025-10-01 12:31:18.959 - error: zigbee.0 (15531) Cannot read properties of undefined (reading 'options')
            2025-10-01 12:31:19.066 - error: host.Test-IoBroker Caught by controller[1]: 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:
            2025-10-01 12:31:19.066 - error: host.Test-IoBroker Caught by controller[1]: TypeError: Cannot read properties of undefined (reading 'device')
            2025-10-01 12:31:19.066 - error: host.Test-IoBroker Caught by controller[1]: at StatesController.onZigbeeEvent (/opt/iobroker/node_modules/iobroker.zigbee/lib/statescontroller.js:1260:31)
            2025-10-01 12:31:19.066 - error: host.Test-IoBroker Caught by controller[1]: at ZigbeeController.emit (node:events:524:28)
            2025-10-01 12:31:19.066 - error: host.Test-IoBroker Caught by controller[1]: at ZigbeeController.emit (node:domain:489:12)
            2025-10-01 12:31:19.066 - error: host.Test-IoBroker Caught by controller[1]: at ZigbeeController.event (/opt/iobroker/node_modules/iobroker.zigbee/lib/zigbeecontroller.js:355:14)
            2025-10-01 12:31:19.066 - error: host.Test-IoBroker Caught by controller[1]: at ZigbeeController.handleMessage (/opt/iobroker/node_modules/iobroker.zigbee/lib/zigbeecontroller.js:1005:14)
            2025-10-01 12:31:19.066 - error: host.Test-IoBroker Caught by controller[1]: at processTicksAndRejections (node:internal/process/task_queues:95:5)
            2025-10-01 12:31:19.067 - error: host.Test-IoBroker Caught by controller[1]: 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:
            2025-10-01 12:31:19.067 - error: host.Test-IoBroker Caught by controller[1]: TypeError: Cannot read properties of undefined (reading 'options')
            2025-10-01 12:31:19.067 - error: host.Test-IoBroker Caught by controller[1]: at ZigbeeController.handleMessage (/opt/iobroker/node_modules/iobroker.zigbee/lib/zigbeecontroller.js:1009:39)
            2025-10-01 12:31:19.067 - error: host.Test-IoBroker Caught by controller[1]: at processTicksAndRejections (node:internal/process/task_queues:95:5)
            2025-10-01 12:31:19.067 - error: host.Test-IoBroker Caught by controller[2]: 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:
            2025-10-01 12:31:19.067 - error: host.Test-IoBroker Caught by controller[3]: TypeError: Cannot read properties of undefined (reading 'device')
            2025-10-01 12:31:19.067 - error: host.Test-IoBroker Caught by controller[3]: at StatesController.onZigbeeEvent (/opt/iobroker/node_modules/iobroker.zigbee/lib/statescontroller.js:1260:31)
            2025-10-01 12:31:19.067 - error: host.Test-IoBroker Caught by controller[3]: at ZigbeeController.emit (node:events:524:28)
            2025-10-01 12:31:19.067 - error: host.Test-IoBroker Caught by controller[3]: at ZigbeeController.emit (node:domain:489:12)
            2025-10-01 12:31:19.067 - error: host.Test-IoBroker Caught by controller[3]: at ZigbeeController.event (/opt/iobroker/node_modules/iobroker.zigbee/lib/zigbeecontroller.js:355:14)
            2025-10-01 12:31:19.067 - error: host.Test-IoBroker Caught by controller[3]: at ZigbeeController.handleMessage (/opt/iobroker/node_modules/iobroker.zigbee/lib/zigbeecontroller.js:1005:14)
            2025-10-01 12:31:19.067 - error: host.Test-IoBroker Caught by controller[3]: at processTicksAndRejections (node:internal/process/task_queues:95:5)
            2025-10-01 12:31:19.067 - error: host.Test-IoBroker Caught by controller[4]: 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:
            2025-10-01 12:31:19.067 - error: host.Test-IoBroker Caught by controller[5]: TypeError: Cannot read properties of undefined (reading 'options')
            2025-10-01 12:31:19.067 - error: host.Test-IoBroker Caught by controller[5]: at ZigbeeController.handleMessage (/opt/iobroker/node_modules/iobroker.zigbee/lib/zigbeecontroller.js:1009:39)
            2025-10-01 12:31:19.067 - error: host.Test-IoBroker Caught by controller[5]: at processTicksAndRejections (node:internal/process/task_queues:95:5)
            2025-10-01 12:31:19.067 - error: host.Test-IoBroker Caught by controller[6]: 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:
            2025-10-01 12:31:19.067 - error: host.Test-IoBroker Caught by controller[7]: TypeError: Cannot read properties of undefined (reading 'device')
            2025-10-01 12:31:19.067 - error: host.Test-IoBroker Caught by controller[7]: at StatesController.onZigbeeEvent (/opt/iobroker/node_modules/iobroker.zigbee/lib/statescontroller.js:1260:31)
            2025-10-01 12:31:19.067 - error: host.Test-IoBroker Caught by controller[7]: at ZigbeeController.emit (node:events:524:28)
            2025-10-01 12:31:19.067 - error: host.Test-IoBroker Caught by controller[7]: at ZigbeeController.emit (node:domain:489:12)
            2025-10-01 12:31:19.067 - error: host.Test-IoBroker Caught by controller[7]: at ZigbeeController.event (/opt/iobroker/node_modules/iobroker.zigbee/lib/zigbeecontroller.js:355:14)
            2025-10-01 12:31:19.067 - error: host.Test-IoBroker Caught by controller[7]: at ZigbeeController.handleMessage (/opt/iobroker/node_modules/iobroker.zigbee/lib/zigbeecontroller.js:1005:14)
            2025-10-01 12:31:19.067 - error: host.Test-IoBroker Caught by controller[7]: at processTicksAndRejections (node:internal/process/task_queues:95:5)
            2025-10-01 12:31:19.068 - error: host.Test-IoBroker Caught by controller[8]: 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:
            2025-10-01 12:31:19.068 - error: host.Test-IoBroker Caught by controller[9]: TypeError: Cannot read properties of undefined (reading 'options')
            2025-10-01 12:31:19.068 - error: host.Test-IoBroker Caught by controller[9]: at ZigbeeController.handleMessage (/opt/iobroker/node_modules/iobroker.zigbee/lib/zigbeecontroller.js:1009:39)
            2025-10-01 12:31:19.068 - error: host.Test-IoBroker Caught by controller[9]: at processTicksAndRejections (node:internal/process/task_queues:95:5)
            2025-10-01 12:31:19.068 - error: host.Test-IoBroker instance system.adapter.zigbee.0 terminated with code 6 (UNCAUGHT_EXCEPTION)
            2025-10-01 12:31:19.068 - info: host.Test-IoBroker Restart adapter system.adapter.zigbee.0 because enabled
            

            Und lässt sich nicht mehr ordentlich starten.
            Hier automatischer restart :

            2025-10-01 12:31:49.284 - info: host.Test-IoBroker instance system.adapter.zigbee.0 in version "3.1.5-alpha.2" (non-npm: ioBroker/ioBroker.zigbee) started with pid 15575
            2025-10-01 12:31:49.891 - info: zigbee.0 (15575) starting. Version 3.1.5-alpha.2 (non-npm: ioBroker/ioBroker.zigbee) in /opt/iobroker/node_modules/iobroker.zigbee, node: v20.19.5, js-controller: 7.0.7
            2025-10-01 12:31:49.900 - info: zigbee.0 (15575) Adapter ready - starting subsystems. Adapter is running in info mode.
            2025-10-01 12:31:49.900 - info: zigbee.0 (15575) init localConfig
            2025-10-01 12:31:49.916 - info: zigbee.0 (15575) --- creating device debug ---
            2025-10-01 12:31:49.917 - info: zigbee.0 (15575) Autostart Zigbee subsystem
            2025-10-01 12:31:49.917 - info: zigbee.0 (15575) Starting Adapter npm ...
            2025-10-01 12:31:49.924 - info: zigbee.0 (15575) Installed Version: ioBroker/ioBroker.zigbee (Converters 25.31.0 Herdsman 6.1.3)
            2025-10-01 12:31:49.925 - info: zigbee.0 (15575) configured transmit power :
            2025-10-01 12:31:49.925 - info: zigbee.0 (15575) Starting Zigbee-Herdsman
            2025-10-01 12:31:51.728 - info: zigbee.0 (15575) Zigbee-Herdsman started successfully with Coordinator firmware version: ZStack3x0 : 20240710 (2-1.2.7.1)
            2025-10-01 12:31:51.728 - info: zigbee.0 (15575) Unable to disable LED, unsupported function.
            2025-10-01 12:31:51.766 - info: zigbee.0 (15575) 0xe0798dfffe746ae6 (addr 11547): HG06104A - Lidl Livarno Home RGB+CCT LED light strip 2m (Router)
            2025-10-01 12:31:51.769 - info: zigbee.0 (15575) 0x00158d0005062c00 (addr 16444): MLI-404011/MLI-404049 - Müller Licht Tint remote control (EndDevice)
            2025-10-01 12:31:51.775 - warn: zigbee.0 (15575) Resolve Entity did not manage to find a mapped device for 0x84fd27fffed2450f of type undefined
            2025-10-01 12:31:51.779 - error: zigbee.0 (15575) Resolve entity error: Cannot read properties of undefined (reading 'model')
            2025-10-01 12:31:51.779 - info: zigbee.0 (15575) 3 devices are part of the network
            2025-10-01 12:31:51.779 - info: zigbee.0 (15575) Zigbee started
            2025-10-01 12:31:51.781 - warn: zigbee.0 (15575) Resolve Entity did not manage to find a mapped device for 0x84fd27fffed2450f of type undefined
            2025-10-01 12:31:51.782 - error: zigbee.0 (15575) Resolve entity error: Cannot read properties of undefined (reading 'model')
            2025-10-01 12:31:51.783 - warn: zigbee.0 (15575) Resolve Entity did not manage to find a mapped device for 0x84fd27fffed2450f of type undefined
            2025-10-01 12:31:51.784 - error: zigbee.0 (15575) Resolve entity error: Cannot read properties of undefined (reading 'model')
            2025-10-01 12:31:51.784 - error: zigbee.0 (15575) 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().
            2025-10-01 12:31:51.784 - error: zigbee.0 (15575) unhandled promise rejection: Cannot read properties of undefined (reading 'options')
            2025-10-01 12:31:51.784 - error: zigbee.0 (15575) TypeError: Cannot read properties of undefined (reading 'options')
            at DeviceEvent.onZigbeeStarted (/opt/iobroker/node_modules/iobroker.zigbee/lib/zbDeviceEvent.js:15:77)
            at processTicksAndRejections (node:internal/process/task_queues:95:5)
            at async Promise.all (index 2)
            2025-10-01 12:31:51.784 - error: zigbee.0 (15575) Cannot read properties of undefined (reading 'options')
            2025-10-01 12:31:51.808 - info: zigbee.0 (15575) Halting zigbee adapter. Restart delay is at least 30 seconds.
            2025-10-01 12:31:51.809 - info: zigbee.0 (15575) cleaning everything up
            2025-10-01 12:31:51.809 - info: zigbee.0 (15575) Saved local configuration data
            2025-10-01 12:31:51.809 - info: zigbee.0 (15575) cleanup successful
            2025-10-01 12:31:51.809 - info: zigbee.0 (15575) terminating
            2025-10-01 12:31:51.810 - warn: zigbee.0 (15575) Terminated (UNCAUGHT_EXCEPTION): Without reason
            2025-10-01 12:31:51.810 - info: zigbee.0 (15575) zigbecontroller stopped successfully - ZH was not running
            2025-10-01 12:31:51.810 - warn: zigbee.0 (15575) Resolve Entity did not manage to find a mapped device for 0x84fd27fffed2450f of type undefined
            2025-10-01 12:31:51.811 - error: zigbee.0 (15575) Resolve entity error: Cannot read properties of undefined (reading 'model')
            2025-10-01 12:31:51.833 - info: zigbee.0 (15575) debug devices set to []
            2025-10-01 12:31:51.909 - warn: zigbee.0 (15575) Resolve Entity did not manage to find a mapped device for 0x84fd27fffed2450f of type undefined
            2025-10-01 12:31:51.910 - error: zigbee.0 (15575) Resolve entity error: Cannot read properties of undefined (reading 'model')
            2025-10-01 12:31:51.910 - warn: zigbee.0 (15575) resolveEntity returned no entity
            2025-10-01 12:31:52.322 - error: host.Test-IoBroker Caught by controller[0]: 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:
            2025-10-01 12:31:52.323 - error: host.Test-IoBroker Caught by controller[1]: TypeError: Cannot read properties of undefined (reading 'options')
            2025-10-01 12:31:52.323 - error: host.Test-IoBroker Caught by controller[1]: at DeviceEvent.onZigbeeStarted (/opt/iobroker/node_modules/iobroker.zigbee/lib/zbDeviceEvent.js:15:77)
            2025-10-01 12:31:52.323 - error: host.Test-IoBroker Caught by controller[1]: at processTicksAndRejections (node:internal/process/task_queues:95:5)
            2025-10-01 12:31:52.323 - error: host.Test-IoBroker Caught by controller[1]: at async Promise.all (index 2)
            2025-10-01 12:31:52.323 - error: host.Test-IoBroker Caught by controller[2]: allowing role change for colortemp
            2025-10-01 12:31:52.323 - error: host.Test-IoBroker Caught by controller[3]: allowing role change for colortemp_move
            2025-10-01 12:31:52.323 - error: host.Test-IoBroker Caught by controller[4]: allowing role change for hex_color
            2025-10-01 12:31:52.323 - error: host.Test-IoBroker Caught by controller[5]: allowing role change for color
            2025-10-01 12:31:52.323 - error: host.Test-IoBroker Caught by controller[6]: allowing role change for color_xy.x
            2025-10-01 12:31:52.326 - error: host.Test-IoBroker Caught by controller[7]: allowing role change for color_xy.y
            2025-10-01 12:31:52.327 - error: host.Test-IoBroker Caught by controller[8]: allowing role change for color_rgb.r
            2025-10-01 12:31:52.327 - error: host.Test-IoBroker Caught by controller[9]: allowing role change for color_rgb.g
            2025-10-01 12:31:52.327 - error: host.Test-IoBroker Caught by controller[10]: allowing role change for color_rgb.b
            2025-10-01 12:31:52.327 - error: host.Test-IoBroker Caught by controller[11]: allowing role change for color_power_on_behavior
            2025-10-01 12:31:52.327 - error: host.Test-IoBroker Caught by controller[12]: allowing role change for color_temperature_move
            2025-10-01 12:31:52.327 - error: host.Test-IoBroker Caught by controller[13]: allowing role change for color_move
            2025-10-01 12:31:52.327 - error: host.Test-IoBroker instance system.adapter.zigbee.0 terminated with code 6 (UNCAUGHT_EXCEPTION)
            2025-10-01 12:31:52.327 - info: host.Test-IoBroker Restart adapter system.adapter.zigbee.0 because enabled
            2025-10-01 12:32:18.906 - info: host.Test-IoBroker "system.adapter.zigbee.0" disabled
            2025-10-01 12:32:23.108 - error: zigbee.0 (15590) adapter disabled
            2025-10-01 12:32:23.111 - warn: zigbee.0 (15590) Terminated (NO_ADAPTER_CONFIG_FOUND): Without reason
            2025-10-01 12:32:23.625 - error: host.Test-IoBroker instance system.adapter.zigbee.0 terminated with code 3 (NO_ADAPTER_CONFIG_FOUND)
            2025-10-01 12:32:23.625 - info: host.Test-IoBroker Do not restart adapter system.adapter.zigbee.0 because disabled or deleted
            
            AsgothianA Offline
            AsgothianA Offline
            Asgothian
            Developer
            schrieb am zuletzt editiert von
            #241

            @dimaiv sagte in Tester wanted - Zigbee Adapter 3.1:

            Jetzt Stürzt der Adapter beim Pairing wieder ab :

            Bekanntes oder neues Device ? Bei mir läuft der durch

            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

              @dimaiv sagte in Tester wanted - Zigbee Adapter 3.1:

              Jetzt Stürzt der Adapter beim Pairing wieder ab :

              Bekanntes oder neues Device ? Bei mir läuft der durch

              A.

              D Offline
              D Offline
              dimaiv
              schrieb am zuletzt editiert von
              #242

              @asgothian sagte in Tester wanted - Zigbee Adapter 3.1:

              @dimaiv sagte in Tester wanted - Zigbee Adapter 3.1:

              Jetzt Stürzt der Adapter beim Pairing wieder ab :

              Bekanntes oder neues Device ? Bei mir läuft der durch

              A.

              Neues.

              ioBroker- NUC8i3 / Proxmox / VM
              Node.js v22.21.0
              NPM v10.9.4
              JS controller 7.0.7
              Admin 7.7.19
              ZigBee Adapter 3.2.5
              Zigbee LAN Gateway CC2652P
              Zigbee Firmware 20250321

              AsgothianA 1 Antwort Letzte Antwort
              0
              • D dimaiv

                @asgothian sagte in Tester wanted - Zigbee Adapter 3.1:

                @dimaiv sagte in Tester wanted - Zigbee Adapter 3.1:

                Jetzt Stürzt der Adapter beim Pairing wieder ab :

                Bekanntes oder neues Device ? Bei mir läuft der durch

                A.

                Neues.

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

                @dimaiv ok.. bitte nochmal installieren - ich hab nochmal was angeschaut. Hoffentlich ist damit das Problem wieder weg.

                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

                  @dimaiv ok.. bitte nochmal installieren - ich hab nochmal was angeschaut. Hoffentlich ist damit das Problem wieder weg.

                  A.

                  D Offline
                  D Offline
                  dimaiv
                  schrieb am zuletzt editiert von
                  #244

                  @asgothian
                  Mit dieser version geht es
                  😁 😁 😁

                  ioBroker- NUC8i3 / Proxmox / VM
                  Node.js v22.21.0
                  NPM v10.9.4
                  JS controller 7.0.7
                  Admin 7.7.19
                  ZigBee Adapter 3.2.5
                  Zigbee LAN Gateway CC2652P
                  Zigbee Firmware 20250321

                  AsgothianA 1 Antwort Letzte Antwort
                  0
                  • D dimaiv

                    @asgothian
                    Mit dieser version geht es
                    😁 😁 😁

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

                    @dimaiv sagte in Tester wanted - Zigbee Adapter 3.1:

                    @asgothian
                    Mit dieser version geht es
                    😁 😁 😁

                    ich hasse das ich das nicht sauber testen kann.

                    irgendwie hab ich kein passendes Device oder das Zeitverhalten ist so anders das der Fehler bei mir nicht zuschlägt, sprich - das Gerät wird bei dir langsamer in den Herdsman geladen als bei mir, so das bei mir 'mapped' immer vorhanden ist, während bei Dir mapped 'noch' nicht definiert ist wenn er das erste mal durch resolve_entity durch geht.

                    Das ist Problematisch seit der ZHC die Definitions dynamisch lädt wenn entsprechende Devices auftauchen, und nicht immer alle vorhält.

                    A.

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

                    D 2 Antworten Letzte Antwort
                    0
                    • AsgothianA Asgothian

                      @dimaiv sagte in Tester wanted - Zigbee Adapter 3.1:

                      @asgothian
                      Mit dieser version geht es
                      😁 😁 😁

                      ich hasse das ich das nicht sauber testen kann.

                      irgendwie hab ich kein passendes Device oder das Zeitverhalten ist so anders das der Fehler bei mir nicht zuschlägt, sprich - das Gerät wird bei dir langsamer in den Herdsman geladen als bei mir, so das bei mir 'mapped' immer vorhanden ist, während bei Dir mapped 'noch' nicht definiert ist wenn er das erste mal durch resolve_entity durch geht.

                      Das ist Problematisch seit der ZHC die Definitions dynamisch lädt wenn entsprechende Devices auftauchen, und nicht immer alle vorhält.

                      A.

                      D Offline
                      D Offline
                      dimaiv
                      schrieb am zuletzt editiert von
                      #246

                      @asgothian
                      Gerade mit der älteren Version (die von vor 1 Stunde oder so) probiert. Wenn's gleiche Geräte im Netz sind, läuft das Pairing normal durch.

                      ioBroker- NUC8i3 / Proxmox / VM
                      Node.js v22.21.0
                      NPM v10.9.4
                      JS controller 7.0.7
                      Admin 7.7.19
                      ZigBee Adapter 3.2.5
                      Zigbee LAN Gateway CC2652P
                      Zigbee Firmware 20250321

                      1 Antwort Letzte Antwort
                      0
                      • AsgothianA Asgothian

                        @fabio sagte in Tester wanted - Zigbee Adapter 3.1:

                        @asgothian ja und die Steckdose ist da und wird auch gechalten etc.

                        Screenshot 2025-10-01 110530.png

                        Noch eine Frage: Als du diese Steckdose angelernt hast, gab es da in dem dazu gehörenden Zigbee-Netzwerk bereits weitere Steckdosen dieses Typs, oder war dieser Typ in diesem Zigbee-Netzwerk neu ?

                        A.

                        FabioF Offline
                        FabioF Offline
                        Fabio
                        schrieb am zuletzt editiert von
                        #247

                        @asgothian nein der war alleine, aber schon mal angelernt gewesen.

                        Iobroker:

                        • Für mich persöhnlich, gibt es nichts besseres, ich liebe es.

                        • Das hat unser Smarthome erst zu Smarthome gemacht.

                        • Du wächst mit ioBroker und ioBroker wächst mit dir.

                        • Benutzt das Voting rechts unten im Beitrag wenn er euch geholfen hat.

                        1 Antwort Letzte Antwort
                        0
                        • AsgothianA Asgothian

                          @dimaiv sagte in Tester wanted - Zigbee Adapter 3.1:

                          @asgothian
                          Mit dieser version geht es
                          😁 😁 😁

                          ich hasse das ich das nicht sauber testen kann.

                          irgendwie hab ich kein passendes Device oder das Zeitverhalten ist so anders das der Fehler bei mir nicht zuschlägt, sprich - das Gerät wird bei dir langsamer in den Herdsman geladen als bei mir, so das bei mir 'mapped' immer vorhanden ist, während bei Dir mapped 'noch' nicht definiert ist wenn er das erste mal durch resolve_entity durch geht.

                          Das ist Problematisch seit der ZHC die Definitions dynamisch lädt wenn entsprechende Devices auftauchen, und nicht immer alle vorhält.

                          A.

                          D Offline
                          D Offline
                          dimaiv
                          schrieb am zuletzt editiert von
                          #248

                          @asgothian sagte in Tester wanted - Zigbee Adapter 3.1:

                          @dimaiv sagte in Tester wanted - Zigbee Adapter 3.1:

                          @asgothian
                          Mit dieser version geht es
                          😁 😁 😁

                          ich hasse das ich das nicht sauber testen kann.

                          irgendwie hab ich kein passendes Device oder das Zeitverhalten ist so anders das der Fehler bei mir nicht zuschlägt, sprich - das Gerät wird bei dir langsamer in den Herdsman geladen als bei mir, so das bei mir 'mapped' immer vorhanden ist, während bei Dir mapped 'noch' nicht definiert ist wenn er das erste mal durch resolve_entity durch geht.

                          Das ist Problematisch seit der ZHC die Definitions dynamisch lädt wenn entsprechende Devices auftauchen, und nicht immer alle vorhält.

                          A.

                          Kann ich dir irgendwie helfen?
                          Meine Instanz irgendwie fern freigeben, ich habe da nicht viel Ahnung 🤔

                          ioBroker- NUC8i3 / Proxmox / VM
                          Node.js v22.21.0
                          NPM v10.9.4
                          JS controller 7.0.7
                          Admin 7.7.19
                          ZigBee Adapter 3.2.5
                          Zigbee LAN Gateway CC2652P
                          Zigbee Firmware 20250321

                          AsgothianA 1 Antwort Letzte Antwort
                          0
                          • D dimaiv

                            @asgothian sagte in Tester wanted - Zigbee Adapter 3.1:

                            @dimaiv sagte in Tester wanted - Zigbee Adapter 3.1:

                            @asgothian
                            Mit dieser version geht es
                            😁 😁 😁

                            ich hasse das ich das nicht sauber testen kann.

                            irgendwie hab ich kein passendes Device oder das Zeitverhalten ist so anders das der Fehler bei mir nicht zuschlägt, sprich - das Gerät wird bei dir langsamer in den Herdsman geladen als bei mir, so das bei mir 'mapped' immer vorhanden ist, während bei Dir mapped 'noch' nicht definiert ist wenn er das erste mal durch resolve_entity durch geht.

                            Das ist Problematisch seit der ZHC die Definitions dynamisch lädt wenn entsprechende Devices auftauchen, und nicht immer alle vorhält.

                            A.

                            Kann ich dir irgendwie helfen?
                            Meine Instanz irgendwie fern freigeben, ich habe da nicht viel Ahnung 🤔

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

                            @dimaiv sagte in Tester wanted - Zigbee Adapter 3.1:

                            @asgothian sagte in Tester wanted - Zigbee Adapter 3.1:

                            @dimaiv sagte in Tester wanted - Zigbee Adapter 3.1:

                            @asgothian
                            Mit dieser version geht es
                            😁 😁 😁

                            ich hasse das ich das nicht sauber testen kann.

                            irgendwie hab ich kein passendes Device oder das Zeitverhalten ist so anders das der Fehler bei mir nicht zuschlägt, sprich - das Gerät wird bei dir langsamer in den Herdsman geladen als bei mir, so das bei mir 'mapped' immer vorhanden ist, während bei Dir mapped 'noch' nicht definiert ist wenn er das erste mal durch resolve_entity durch geht.

                            Das ist Problematisch seit der ZHC die Definitions dynamisch lädt wenn entsprechende Devices auftauchen, und nicht immer alle vorhält.

                            A.

                            Kann ich dir irgendwie helfen?
                            Meine Instanz irgendwie fern freigeben, ich habe da nicht viel Ahnung 🤔

                            Danke für das Angebot, aber dafür bräuchte ich dann letztendlich Konsolen zugriff auf den ioBroker auf dem die Instanz läuft. Das ist dann doch etwas viel. Und geräte rauswerfen und neu anlernen mag ich auch nicht wenn ich nicht an die Geräte heran komme.

                            A.

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

                            arteckA 1 Antwort Letzte Antwort
                            0
                            • AsgothianA Asgothian

                              @dimaiv sagte in Tester wanted - Zigbee Adapter 3.1:

                              @asgothian sagte in Tester wanted - Zigbee Adapter 3.1:

                              @dimaiv sagte in Tester wanted - Zigbee Adapter 3.1:

                              @asgothian
                              Mit dieser version geht es
                              😁 😁 😁

                              ich hasse das ich das nicht sauber testen kann.

                              irgendwie hab ich kein passendes Device oder das Zeitverhalten ist so anders das der Fehler bei mir nicht zuschlägt, sprich - das Gerät wird bei dir langsamer in den Herdsman geladen als bei mir, so das bei mir 'mapped' immer vorhanden ist, während bei Dir mapped 'noch' nicht definiert ist wenn er das erste mal durch resolve_entity durch geht.

                              Das ist Problematisch seit der ZHC die Definitions dynamisch lädt wenn entsprechende Devices auftauchen, und nicht immer alle vorhält.

                              A.

                              Kann ich dir irgendwie helfen?
                              Meine Instanz irgendwie fern freigeben, ich habe da nicht viel Ahnung 🤔

                              Danke für das Angebot, aber dafür bräuchte ich dann letztendlich Konsolen zugriff auf den ioBroker auf dem die Instanz läuft. Das ist dann doch etwas viel. Und geräte rauswerfen und neu anlernen mag ich auch nicht wenn ich nicht an die Geräte heran komme.

                              A.

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

                              @asgothian währe es eine Lösung den bei problem (exception) nochmal durch die resolveEntity zu schicken.. nach einer pause von 5 sek. hab den code nur überflogen
                              der kann doch das device nicht abholen.. direkt ..

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

                              AsgothianA 1 Antwort Letzte Antwort
                              0
                              • arteckA arteck

                                @asgothian währe es eine Lösung den bei problem (exception) nochmal durch die resolveEntity zu schicken.. nach einer pause von 5 sek. hab den code nur überflogen
                                der kann doch das device nicht abholen.. direkt ..

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

                                @arteck sagte in Tester wanted - Zigbee Adapter 3.1:

                                @asgothian währe es eine Lösung den bei problem (exception) nochmal durch die resolveEntity zu schicken.. nach einer pause von 5 sek. hab den code nur überflogen
                                der kann doch das device nicht abholen.. direkt ..

                                Hab ich drüber nachgedacht - ist aber unnötig - an der stelle wo der Fehler auftritt wird mapped eigentlich nicht gebraucht. Es ist halt so das resolveEntity immer versucht alles zu holen, auch wenn nur teile gebraucht werden. Ich muss da nochmal mit nem feinen Kamm durch gehen, das

                                • resolve entity immer 'mapped' liefert - auch wenn es nur ein 'dummy' mapped mit extra infos ist.
                                • da wo mapped benutzt wird das 'dummy' mapped sauber erkannt und abgefragt wird.

                                Da ist halt noch viel code bei dem einfach davon ausgegangen wird das das ganze stabile Strukturen liefert.

                                A.

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

                                AsgothianA 1 Antwort Letzte Antwort
                                1
                                • AsgothianA Asgothian

                                  @arteck sagte in Tester wanted - Zigbee Adapter 3.1:

                                  @asgothian währe es eine Lösung den bei problem (exception) nochmal durch die resolveEntity zu schicken.. nach einer pause von 5 sek. hab den code nur überflogen
                                  der kann doch das device nicht abholen.. direkt ..

                                  Hab ich drüber nachgedacht - ist aber unnötig - an der stelle wo der Fehler auftritt wird mapped eigentlich nicht gebraucht. Es ist halt so das resolveEntity immer versucht alles zu holen, auch wenn nur teile gebraucht werden. Ich muss da nochmal mit nem feinen Kamm durch gehen, das

                                  • resolve entity immer 'mapped' liefert - auch wenn es nur ein 'dummy' mapped mit extra infos ist.
                                  • da wo mapped benutzt wird das 'dummy' mapped sauber erkannt und abgefragt wird.

                                  Da ist halt noch viel code bei dem einfach davon ausgegangen wird das das ganze stabile Strukturen liefert.

                                  A.

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

                                  So.. die alpha.2 ist jetzt ins Latest gerutscht - als reguläre 3.1.5

                                  Tests sind weiterhin willkommen.

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

                                  FabioF 1 Antwort Letzte Antwort
                                  4
                                  • AsgothianA Asgothian

                                    So.. die alpha.2 ist jetzt ins Latest gerutscht - als reguläre 3.1.5

                                    Tests sind weiterhin willkommen.

                                    FabioF Offline
                                    FabioF Offline
                                    Fabio
                                    schrieb am zuletzt editiert von Fabio
                                    #253

                                    @asgothian so gerade 3.1.5 geladen. Beide Instanzen bei mir laufen hervorragend, bis jetzt konnte ich keine Probleme feststellen. Super Arbeit. 👍 👍 👍 👍

                                    Iobroker:

                                    • Für mich persöhnlich, gibt es nichts besseres, ich liebe es.

                                    • Das hat unser Smarthome erst zu Smarthome gemacht.

                                    • Du wächst mit ioBroker und ioBroker wächst mit dir.

                                    • Benutzt das Voting rechts unten im Beitrag wenn er euch geholfen hat.

                                    AsgothianA 1 Antwort Letzte Antwort
                                    1
                                    • FabioF Fabio

                                      @asgothian so gerade 3.1.5 geladen. Beide Instanzen bei mir laufen hervorragend, bis jetzt konnte ich keine Probleme feststellen. Super Arbeit. 👍 👍 👍 👍

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

                                      @fabio @dimaiv bitte prüfen - habt ihr 2 Kacheln für den koordinator mit der 3.1.5 aus dem latest ?

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

                                      FabioF CodierknechtC D 3 Antworten Letzte Antwort
                                      0
                                      • AsgothianA Asgothian

                                        @fabio @dimaiv bitte prüfen - habt ihr 2 Kacheln für den koordinator mit der 3.1.5 aus dem latest ?

                                        FabioF Offline
                                        FabioF Offline
                                        Fabio
                                        schrieb am zuletzt editiert von Fabio
                                        #255

                                        @asgothian nö bei beiden nicht.
                                        Screenshot 2025-10-06 063106.png

                                        Screenshot 2025-10-06 063246.png

                                        Iobroker:

                                        • Für mich persöhnlich, gibt es nichts besseres, ich liebe es.

                                        • Das hat unser Smarthome erst zu Smarthome gemacht.

                                        • Du wächst mit ioBroker und ioBroker wächst mit dir.

                                        • Benutzt das Voting rechts unten im Beitrag wenn er euch geholfen hat.

                                        1 Antwort Letzte Antwort
                                        0
                                        • AsgothianA Asgothian

                                          @fabio @dimaiv bitte prüfen - habt ihr 2 Kacheln für den koordinator mit der 3.1.5 aus dem latest ?

                                          CodierknechtC Online
                                          CodierknechtC Online
                                          Codierknecht
                                          Developer Most Active
                                          schrieb am zuletzt editiert von
                                          #256

                                          @asgothian

                                          3.1.5 latest ... nur 1 Kachel

                                          "Any fool can write code that a computer can understand. Good programmers write code that humans can understand." (Martin Fowler, "Refactoring")

                                          Proxmox 9.0.17 LXC|8 GB|Core i7-6700
                                          HmIP|ZigBee|Tasmota|Unifi
                                          Zabbix Cerrtified Specialist
                                          Konnte ich Dir helfen? Dann benutze bitte das Voting unten rechts im Beitrag

                                          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

                                          505

                                          Online

                                          32.4k

                                          Benutzer

                                          81.4k

                                          Themen

                                          1.3m

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

                                          • Du hast noch kein Konto? Registrieren

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