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

  • Standard: (Kein Skin)
  • Kein Skin
Einklappen
ioBroker Logo

Community Forum

  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.3k

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

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

ZigBee neue Version 1.5.x

Geplant Angeheftet Gesperrt Verschoben Tester
579 Beiträge 72 Kommentatoren 148.2k 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.
  • G gosund

    @artek
    Ok, ganz so einfach hat es dann doch nicht geklappt. Schlußendlich mußte ich den Adapter komplett löschen über die Konsole, dann die 1.4.1 installiert, danach das Update auf die 1.5.6 und dann das ZigBee Backup wieder eingespielt. Zumindest erkennt er jetzt wieder alle Geräte, jedoch fehlen bei den Objekten wieder die Rolle und Funktion.
    Kann ich das irgendwie auch sichern und wiederherstellen? Ist ziemlich mühsam bei 16+ Geräten alles wieder von Hand einzufügen...

    Ob es etwas gebracht hat sehe ich wohl in den kommenden 24 Stunden.

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

    @gosund hättest den Adapter nicht löschen müssen.. zumindest nicht aus der GUI raus

    hintenrum hätte auch gereicht und dir blieben alle Objekte erhalten

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

    G 1 Antwort Letzte Antwort
    0
    • arteckA arteck

      @gosund hättest den Adapter nicht löschen müssen.. zumindest nicht aus der GUI raus

      hintenrum hätte auch gereicht und dir blieben alle Objekte erhalten

      G Offline
      G Offline
      gosund
      schrieb am zuletzt editiert von
      #421

      @arteck
      Zu früh gefreut. Der 1.5.6 Adapter kommt nicht mehr hoch:

      zigbee.0
      2021-06-09 16:15:12.631 info Try to reconnect. 1 attempts left
      zigbee.0
      2021-06-09 16:15:02.627 error Error herdsman start
      zigbee.0
      2021-06-09 16:15:02.626 error Failed to start Zigbee
      zigbee.0
      2021-06-09 16:15:02.624 error Starting zigbee-herdsman problem : "Failed to connect to the adapter (Error: SRSP - SYS - ping after 6000ms)"
      zigbee.0
      2021-06-09 16:14:43.017 info Installed Version: iobroker.zigbee@1.5.6
      zigbee.0
      2021-06-09 16:14:42.721 info Starting Zigbee npm ...
      zigbee.0
      2021-06-09 16:14:42.627 info starting. Version 1.5.6 in /opt/iobroker/node_modules/iobroker.zigbee, node: v12.22.1, js-controller: 3.3.12
      zigbee.0
      2021-06-09 16:14:37.116 error Cannot read property 'getEntries' of null
      zigbee.0
      2021-06-09 16:14:37.115 error TypeError: Cannot read property 'getEntries' of null at Function.loadFromDatabaseIfNecessary (/opt/iobroker/node_modules/zigbee-herdsman/dist/controller/model/device.js:220:55) at Function.all (/opt/iobroker/node_modules/zigbee-herdsman/dist/controller/model/device.js:240:16) at Controller.getDevices (/opt/iobroker/node_modules/zigbee-herdsman/dist/controller/controller.js:303:31) at ZigbeeController.getClients (/opt/iobroker/node_modules/iobroker.zigbee/lib/zigbeecontroller.js:228:49) at DeviceAvailability.stop (/opt/iobroker/node_modules/iobroker.zigbee/lib/zbDeviceAvailability.js:222:43) at ZigbeeController.callExtensionMethod (/opt/iobroker/node_modules/iobroker.zigbee/lib/zigbeecontroller.js:214:42) at ZigbeeController.stop (/opt/iobroker/node_modules/iobroker.zigbee/lib/zigbeecontroller.js:385:20) at Zigbee.onUnload (/opt/iobroker/node_modules/iobroker.zigbee/main.js:696:41) at runMicrotasks (<anonymous>) at processTicksAndRejections (internal/process/task_queues.js:97:5)
      zigbee.0
      2021-06-09 16:14:37.113 error unhandled promise rejection: Cannot read property 'getEntries' of null
      zigbee.0
      2021-06-09 16:14:37.112 error Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().

      G 1 Antwort Letzte Antwort
      0
      • G gosund

        @arteck
        Zu früh gefreut. Der 1.5.6 Adapter kommt nicht mehr hoch:

        zigbee.0
        2021-06-09 16:15:12.631 info Try to reconnect. 1 attempts left
        zigbee.0
        2021-06-09 16:15:02.627 error Error herdsman start
        zigbee.0
        2021-06-09 16:15:02.626 error Failed to start Zigbee
        zigbee.0
        2021-06-09 16:15:02.624 error Starting zigbee-herdsman problem : "Failed to connect to the adapter (Error: SRSP - SYS - ping after 6000ms)"
        zigbee.0
        2021-06-09 16:14:43.017 info Installed Version: iobroker.zigbee@1.5.6
        zigbee.0
        2021-06-09 16:14:42.721 info Starting Zigbee npm ...
        zigbee.0
        2021-06-09 16:14:42.627 info starting. Version 1.5.6 in /opt/iobroker/node_modules/iobroker.zigbee, node: v12.22.1, js-controller: 3.3.12
        zigbee.0
        2021-06-09 16:14:37.116 error Cannot read property 'getEntries' of null
        zigbee.0
        2021-06-09 16:14:37.115 error TypeError: Cannot read property 'getEntries' of null at Function.loadFromDatabaseIfNecessary (/opt/iobroker/node_modules/zigbee-herdsman/dist/controller/model/device.js:220:55) at Function.all (/opt/iobroker/node_modules/zigbee-herdsman/dist/controller/model/device.js:240:16) at Controller.getDevices (/opt/iobroker/node_modules/zigbee-herdsman/dist/controller/controller.js:303:31) at ZigbeeController.getClients (/opt/iobroker/node_modules/iobroker.zigbee/lib/zigbeecontroller.js:228:49) at DeviceAvailability.stop (/opt/iobroker/node_modules/iobroker.zigbee/lib/zbDeviceAvailability.js:222:43) at ZigbeeController.callExtensionMethod (/opt/iobroker/node_modules/iobroker.zigbee/lib/zigbeecontroller.js:214:42) at ZigbeeController.stop (/opt/iobroker/node_modules/iobroker.zigbee/lib/zigbeecontroller.js:385:20) at Zigbee.onUnload (/opt/iobroker/node_modules/iobroker.zigbee/main.js:696:41) at runMicrotasks (<anonymous>) at processTicksAndRejections (internal/process/task_queues.js:97:5)
        zigbee.0
        2021-06-09 16:14:37.113 error unhandled promise rejection: Cannot read property 'getEntries' of null
        zigbee.0
        2021-06-09 16:14:37.112 error Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().

        G Offline
        G Offline
        gosund
        schrieb am zuletzt editiert von gosund
        #422

        @artek

        Was hat es eigentlich mit der PAN Id nach dem Update auf sich?
        Ich hatte diese unverändert auf 6754. Nach den ersten Problemen mit der 1.5.6 und dem Einspielen des Backups behauptete der Adapter im Log, die PAN wäre 6755. Nachdem ich umgestellt hatte, ging es -zumindest für ein paar Stunden.
        Nach der neuerlichen Aktion mit Downgrade auf 1.4.1 und jetzt wieder Update auf 1.5.6 behauptet der Adapter, die PAN Id wäre ist die 6756

        AsgothianA 1 Antwort Letzte Antwort
        0
        • G gosund

          @artek

          Was hat es eigentlich mit der PAN Id nach dem Update auf sich?
          Ich hatte diese unverändert auf 6754. Nach den ersten Problemen mit der 1.5.6 und dem Einspielen des Backups behauptete der Adapter im Log, die PAN wäre 6755. Nachdem ich umgestellt hatte, ging es -zumindest für ein paar Stunden.
          Nach der neuerlichen Aktion mit Downgrade auf 1.4.1 und jetzt wieder Update auf 1.5.6 behauptet der Adapter, die PAN Id wäre ist die 6756

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

          @gosund
          Hast du zufällig die verschiedenen nvbackup.json Dateien von den Versionen, in denen erkennbar ist das die panID hochgezählt wird ? Ich gehe davon aus das da etwas in der Konfiguration im Herdsman passiert - Wir brauchen dafür aber die Möglichkeit das nachzustellen.

          Ich kann verstehen wenn Du das mit deinem "live" Zigbee Netz nicht tun willst. In diesem Fall müsstest Du erst einmal auf die 1.4.1 zurück gehen. Ich hoffe immer noch darauf eine zigbee-herdsman version zu finden die

          • mit der 1.5.6 läuft
          • das Problem nicht hat.

          Sobald ich da etwas gefunden habe werde ich einen Link zur Testinstallation bereitstellen.

          A.

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

          E 1 Antwort Letzte Antwort
          0
          • AsgothianA Asgothian

            @gosund
            Hast du zufällig die verschiedenen nvbackup.json Dateien von den Versionen, in denen erkennbar ist das die panID hochgezählt wird ? Ich gehe davon aus das da etwas in der Konfiguration im Herdsman passiert - Wir brauchen dafür aber die Möglichkeit das nachzustellen.

            Ich kann verstehen wenn Du das mit deinem "live" Zigbee Netz nicht tun willst. In diesem Fall müsstest Du erst einmal auf die 1.4.1 zurück gehen. Ich hoffe immer noch darauf eine zigbee-herdsman version zu finden die

            • mit der 1.5.6 läuft
            • das Problem nicht hat.

            Sobald ich da etwas gefunden habe werde ich einen Link zur Testinstallation bereitstellen.

            A.

            E Offline
            E Offline
            ente34
            schrieb am zuletzt editiert von
            #424

            @asgothian
            Nach Stromausfall kommt zigbee nicht mehr hoch:

            zigbee.0	2021-06-09 19:29:22.325	warn	(3443) Read-only state "zigbee.0.info.pairingMessage" has been written without ack-flag with value "Error: Failed to stop zigbee (TypeError: Cannot read property 'getEntries' of null at Function.l
            zigbee.0	2021-06-09 19:29:22.311	error	(3443) Cannot read property 'getEntries' of null
            zigbee.0	2021-06-09 19:29:22.310	error	(3443) TypeError: Cannot read property 'getEntries' of null at Function.loadFromDatabaseIfNecessary (/opt/iobroker/node_modules/zigbee-herdsman/dist/controller/model/device.js:216:55) at Funct
            zigbee.0	2021-06-09 19:29:22.306	error	(3443) unhandled promise rejection: Cannot read property 'getEntries' of null
            zigbee.0	2021-06-09 19:29:22.305	error	(3443) Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().
            zigbee.0	2021-06-09 19:29:22.304	warn	(3443) Terminated (UNCAUGHT_EXCEPTION): Without reason
            zigbee.0	2021-06-09 19:29:22.302	info	(3443) terminating
            zigbee.0	2021-06-09 19:29:22.300	error	(3443) Failed to stop zigbee (TypeError: Cannot read property 'getEntries' of null at Function.loadFromDatabaseIfNecessary (/opt/iobroker/node_modules/zigbee-herdsman/dist/controller/model/group.j
            zigbee.0	2021-06-09 19:29:22.296	info	(3443) Zigbee: disabling joining new devices.
            zigbee.0	2021-06-09 19:29:22.289	info	(3443) cleaned everything up...
            zigbee.0	2021-06-09 19:29:22.279	error	(3443) Error while opening serialport 'Error: Error: No such file or directory, cannot open /dev/serial/by-id/usb-dresden_elektronik_ingenieurtechnik_GmbH_ConBee_II_DE2218746-if00'
            zigbee.0	2021-06-09 19:29:22.278	error	(3443) Error: Error while opening serialport 'Error: Error: No such file or directory, cannot open /dev/serial/by-id/usb-dresden_elektronik_ingenieurtechnik_GmbH_ConBee_II_DE2218746-if00' at Drive
            zigbee.0	2021-06-09 19:29:22.277	error	(3443) unhandled promise rejection: Error while opening serialport 'Error: Error: No such file or directory, cannot open /dev/serial/by-id/usb-dresden_elektronik_ingenieurtechnik_GmbH_ConBee_II_DE2218
            zigbee.0	2021-06-09 19:29:22.275	error	(3443) Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().
            zigbee.0	2021-06-09 19:29:01.519	warn	(3443) Read-only state "zigbee.0.info.connection" has been written without ack-flag with value "false"
            zigbee.0	2021-06-09 19:29:01.509	error	(3443) Error: Error while opening serialport 'Error: Error: No such file or directory, cannot open /dev/serial/by-id/usb-dresden_elektronik_ingenieurtechnik_GmbH_ConBee_II_DE2218746-if00' at Drive
            zigbee.0	2021-06-09 19:29:01.508	error	(3443) Failed to start Zigbee
            zigbee.0	2021-06-09 19:29:01.326	info	(3443) Installed Version: iobroker.zigbee@1.5.6
            zigbee.0	2021-06-09 19:29:01.283	info	(3443) Starting Zigbee npm ...
            zigbee.0	2021-06-09 19:29:01.281	info	(3443) Try to reconnect. 1 attempts left
            zigbee.0	2021-06-09 19:28:51.283	warn	(3443) Read-only state "zigbee.0.info.connection" has been written without ack-flag with value "false"
            zigbee.0	2021-06-09 19:28:51.281	error	(3443) Error: Error while opening serialport 'Error: Error: No such file or directory, cannot open /dev/serial/by-id/usb-dresden_elektronik_ingenieurtechnik_GmbH_ConBee_II_DE2218746-if00' at Drive
            zigbee.0	2021-06-09 19:28:51.279	error	(3443) Failed to start Zigbee
            zigbee.0	2021-06-09 19:28:51.106	info	(3443) Installed Version: iobroker.zigbee@1.5.6
            zigbee.0	2021-06-09 19:28:51.101	warn	(3443) Read-only state "zigbee.0.info.connection" has been written without ack-flag with value "false"
            zigbee.0	2021-06-09 19:28:50.914	info	(3443) Starting Zigbee npm ...
            zigbee.0	2021-06-09 19:28:50.821	info	(3443) starting. Version 1.4.1 in /opt/iobroker/node_modules/iobroker.zigbee, node: v12.22.1, js-controller: 3.3.11
            zigbee.0	2021-06-09 19:28:17.833	warn	(3367) Read-only state "zigbee.0.info.pairingMessage" has been written without ack-flag with value "Error: Failed to stop zigbee (TypeError: Cannot read property 'getEntries' of null at Function.l
            zigbee.0	2021-06-09 19:28:17.822	error	(3367) Cannot read property 'getEntries' of null
            zigbee.0	2021-06-09 19:28:17.821	error	(3367) TypeError: Cannot read property 'getEntries' of null at Function.loadFromDatabaseIfNecessary (/opt/iobroker/node_modules/zigbee-herdsman/dist/controller/model/device.js:216:55) at Funct
            zigbee.0	2021-06-09 19:28:17.817	error	(3367) unhandled promise rejection: Cannot read property 'getEntries' of null
            zigbee.0	2021-06-09 19:28:17.816	error	(3367) Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().
            zigbee.0	2021-06-09 19:28:17.815	warn	(3367) Terminated (UNCAUGHT_EXCEPTION): Without reason
            zigbee.0	2021-06-09 19:28:17.813	info	(3367) terminating
            zigbee.0	2021-06-09 19:28:17.808	error	(3367) Failed to stop zigbee (TypeError: Cannot read property 'getEntries' of null at Function.loadFromDatabaseIfNecessary (/opt/iobroker/node_modules/zigbee-herdsman/dist/controller/model/group.j
            zigbee.0	2021-06-09 19:28:17.804	info	(3367) Zigbee: disabling joining new devices.
            zigbee.0	2021-06-09 19:28:17.797	info	(3367) cleaned everything up...
            zigbee.0	2021-06-09 19:28:17.783	error	(3367) Error while opening serialport 'Error: Error: No such file or directory, cannot open /dev/serial/by-id/usb-dresden_elektronik_ingenieurtechnik_GmbH_ConBee_II_DE2218746-if00'
            zigbee.0	2021-06-09 19:28:17.782	error	(3367) Error: Error while opening serialport 'Error: Error: No such file or directory, cannot open /dev/serial/by-id/usb-dresden_elektronik_ingenieurtechnik_GmbH_ConBee_II_DE2218746-if00' at Drive
            zigbee.0	2021-06-09 19:28:17.781	error	(3367) unhandled promise rejection: Error while opening serialport 'Error: Error: No such file or directory, cannot open /dev/serial/by-id/usb-dresden_elektronik_ingenieurtechnik_GmbH_ConBee_II_DE2218
            zigbee.0	2021-06-09 19:28:17.779	error	(3367) Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().
            zigbee.0	2021-06-09 19:27:57.012	warn	(3367) Read-only state "zigbee.0.info.connection" has been written without ack-flag with value "false"
            zigbee.0	2021-06-09 19:27:57.008	error	(3367) Error: Error while opening serialport 'Error: Error: No such file or directory, cannot open /dev/serial/by-id/usb-dresden_elektronik_ingenieurtechnik_GmbH_ConBee_II_DE2218746-if00' at Drive
            zigbee.0	2021-06-09 19:27:57.007	error	(3367) Failed to start Zigbee
            zigbee.0	2021-06-09 19:27:56.797	info	(3367) Installed Version: iobroker.zigbee@1.5.6
            zigbee.0	2021-06-09 19:27:56.777	info	(3367) Starting Zigbee npm ...
            zigbee.0	2021-06-09 19:27:56.776	info	(3367) Try to reconnect. 1 attempts left
            zigbee.0	2021-06-09 19:27:46.778	warn	(3367) Read-only state "zigbee.0.info.connection" has been written without ack-flag with value "false"
            zigbee.0	2021-06-09 19:27:46.775	error	(3367) Error: Error while opening serialport 'Error: Error: No such file or directory, cannot open /dev/serial/by-id/usb-dresden_elektronik_ingenieurtechnik_GmbH_ConBee_II_DE2218746-if00' at Drive
            zigbee.0	2021-06-09 19:27:46.773	error	(3367) Failed to start Zigbee
            zigbee.0	2021-06-09 19:27:46.630	info	(3367) Installed Version: iobroker.zigbee@1.5.6
            zigbee.0	2021-06-09 19:27:46.626	warn	(3367) Read-only state "zigbee.0.info.connection" has been written without ack-flag with value "false"
            zigbee.0	2021-06-09 19:27:46.394	info	(3367) Starting Zigbee npm ...
            zigbee.0	2021-06-09 19:27:46.294	info	(3367) starting. Version 1.4.1 in /opt/iobroker/node_modules/iobroker.zigbee, node: v12.22.1, js-controller: 3.3.11
            zigbee.0	2021-06-09 19:27:13.360	warn	(3289) Read-only state "zigbee.0.info.pairingMessage" has been written without ack-flag with value "Error: Failed to stop zigbee (TypeError: Cannot read property 'getEntries' of null at Function.l
            zigbee.0	2021-06-09 19:27:13.349	error	(3289) Cannot read property 'getEntries' of null
            zigbee.0	2021-06-09 19:27:13.348	error	(3289) TypeError: Cannot read property 'getEntries' of null at Function.loadFromDatabaseIfNecessary (/opt/iobroker/node_modules/zigbee-herdsman/dist/controller/model/device.js:216:55) at Funct
            zigbee.0	2021-06-09 19:27:13.342	error	(3289) unhandled promise rejection: Cannot read property 'getEntries' of null
            zigbee.0	2021-06-09 19:27:13.341	error	(3289) Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().
            zigbee.0	2021-06-09 19:27:13.340	warn	(3289) Terminated (UNCAUGHT_EXCEPTION): Without reason
            zigbee.0	2021-06-09 19:27:13.338	info	(3289) terminating
            zigbee.0	2021-06-09 19:27:13.336	error	(3289) Failed to stop zigbee (TypeError: Cannot read property 'getEntries' of null at Function.loadFromDatabaseIfNecessary (/opt/iobroker/node_modules/zigbee-herdsman/dist/controller/model/group.j
            zigbee.0	2021-06-09 19:27:13.332	info	(3289) Zigbee: disabling joining new devices.
            zigbee.0	2021-06-09 19:27:13.326	info	(3289) cleaned everything up...
            
            
            AsgothianA 1 Antwort Letzte Antwort
            0
            • E ente34

              @asgothian
              Nach Stromausfall kommt zigbee nicht mehr hoch:

              zigbee.0	2021-06-09 19:29:22.325	warn	(3443) Read-only state "zigbee.0.info.pairingMessage" has been written without ack-flag with value "Error: Failed to stop zigbee (TypeError: Cannot read property 'getEntries' of null at Function.l
              zigbee.0	2021-06-09 19:29:22.311	error	(3443) Cannot read property 'getEntries' of null
              zigbee.0	2021-06-09 19:29:22.310	error	(3443) TypeError: Cannot read property 'getEntries' of null at Function.loadFromDatabaseIfNecessary (/opt/iobroker/node_modules/zigbee-herdsman/dist/controller/model/device.js:216:55) at Funct
              zigbee.0	2021-06-09 19:29:22.306	error	(3443) unhandled promise rejection: Cannot read property 'getEntries' of null
              zigbee.0	2021-06-09 19:29:22.305	error	(3443) Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().
              zigbee.0	2021-06-09 19:29:22.304	warn	(3443) Terminated (UNCAUGHT_EXCEPTION): Without reason
              zigbee.0	2021-06-09 19:29:22.302	info	(3443) terminating
              zigbee.0	2021-06-09 19:29:22.300	error	(3443) Failed to stop zigbee (TypeError: Cannot read property 'getEntries' of null at Function.loadFromDatabaseIfNecessary (/opt/iobroker/node_modules/zigbee-herdsman/dist/controller/model/group.j
              zigbee.0	2021-06-09 19:29:22.296	info	(3443) Zigbee: disabling joining new devices.
              zigbee.0	2021-06-09 19:29:22.289	info	(3443) cleaned everything up...
              zigbee.0	2021-06-09 19:29:22.279	error	(3443) Error while opening serialport 'Error: Error: No such file or directory, cannot open /dev/serial/by-id/usb-dresden_elektronik_ingenieurtechnik_GmbH_ConBee_II_DE2218746-if00'
              zigbee.0	2021-06-09 19:29:22.278	error	(3443) Error: Error while opening serialport 'Error: Error: No such file or directory, cannot open /dev/serial/by-id/usb-dresden_elektronik_ingenieurtechnik_GmbH_ConBee_II_DE2218746-if00' at Drive
              zigbee.0	2021-06-09 19:29:22.277	error	(3443) unhandled promise rejection: Error while opening serialport 'Error: Error: No such file or directory, cannot open /dev/serial/by-id/usb-dresden_elektronik_ingenieurtechnik_GmbH_ConBee_II_DE2218
              zigbee.0	2021-06-09 19:29:22.275	error	(3443) Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().
              zigbee.0	2021-06-09 19:29:01.519	warn	(3443) Read-only state "zigbee.0.info.connection" has been written without ack-flag with value "false"
              zigbee.0	2021-06-09 19:29:01.509	error	(3443) Error: Error while opening serialport 'Error: Error: No such file or directory, cannot open /dev/serial/by-id/usb-dresden_elektronik_ingenieurtechnik_GmbH_ConBee_II_DE2218746-if00' at Drive
              zigbee.0	2021-06-09 19:29:01.508	error	(3443) Failed to start Zigbee
              zigbee.0	2021-06-09 19:29:01.326	info	(3443) Installed Version: iobroker.zigbee@1.5.6
              zigbee.0	2021-06-09 19:29:01.283	info	(3443) Starting Zigbee npm ...
              zigbee.0	2021-06-09 19:29:01.281	info	(3443) Try to reconnect. 1 attempts left
              zigbee.0	2021-06-09 19:28:51.283	warn	(3443) Read-only state "zigbee.0.info.connection" has been written without ack-flag with value "false"
              zigbee.0	2021-06-09 19:28:51.281	error	(3443) Error: Error while opening serialport 'Error: Error: No such file or directory, cannot open /dev/serial/by-id/usb-dresden_elektronik_ingenieurtechnik_GmbH_ConBee_II_DE2218746-if00' at Drive
              zigbee.0	2021-06-09 19:28:51.279	error	(3443) Failed to start Zigbee
              zigbee.0	2021-06-09 19:28:51.106	info	(3443) Installed Version: iobroker.zigbee@1.5.6
              zigbee.0	2021-06-09 19:28:51.101	warn	(3443) Read-only state "zigbee.0.info.connection" has been written without ack-flag with value "false"
              zigbee.0	2021-06-09 19:28:50.914	info	(3443) Starting Zigbee npm ...
              zigbee.0	2021-06-09 19:28:50.821	info	(3443) starting. Version 1.4.1 in /opt/iobroker/node_modules/iobroker.zigbee, node: v12.22.1, js-controller: 3.3.11
              zigbee.0	2021-06-09 19:28:17.833	warn	(3367) Read-only state "zigbee.0.info.pairingMessage" has been written without ack-flag with value "Error: Failed to stop zigbee (TypeError: Cannot read property 'getEntries' of null at Function.l
              zigbee.0	2021-06-09 19:28:17.822	error	(3367) Cannot read property 'getEntries' of null
              zigbee.0	2021-06-09 19:28:17.821	error	(3367) TypeError: Cannot read property 'getEntries' of null at Function.loadFromDatabaseIfNecessary (/opt/iobroker/node_modules/zigbee-herdsman/dist/controller/model/device.js:216:55) at Funct
              zigbee.0	2021-06-09 19:28:17.817	error	(3367) unhandled promise rejection: Cannot read property 'getEntries' of null
              zigbee.0	2021-06-09 19:28:17.816	error	(3367) Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().
              zigbee.0	2021-06-09 19:28:17.815	warn	(3367) Terminated (UNCAUGHT_EXCEPTION): Without reason
              zigbee.0	2021-06-09 19:28:17.813	info	(3367) terminating
              zigbee.0	2021-06-09 19:28:17.808	error	(3367) Failed to stop zigbee (TypeError: Cannot read property 'getEntries' of null at Function.loadFromDatabaseIfNecessary (/opt/iobroker/node_modules/zigbee-herdsman/dist/controller/model/group.j
              zigbee.0	2021-06-09 19:28:17.804	info	(3367) Zigbee: disabling joining new devices.
              zigbee.0	2021-06-09 19:28:17.797	info	(3367) cleaned everything up...
              zigbee.0	2021-06-09 19:28:17.783	error	(3367) Error while opening serialport 'Error: Error: No such file or directory, cannot open /dev/serial/by-id/usb-dresden_elektronik_ingenieurtechnik_GmbH_ConBee_II_DE2218746-if00'
              zigbee.0	2021-06-09 19:28:17.782	error	(3367) Error: Error while opening serialport 'Error: Error: No such file or directory, cannot open /dev/serial/by-id/usb-dresden_elektronik_ingenieurtechnik_GmbH_ConBee_II_DE2218746-if00' at Drive
              zigbee.0	2021-06-09 19:28:17.781	error	(3367) unhandled promise rejection: Error while opening serialport 'Error: Error: No such file or directory, cannot open /dev/serial/by-id/usb-dresden_elektronik_ingenieurtechnik_GmbH_ConBee_II_DE2218
              zigbee.0	2021-06-09 19:28:17.779	error	(3367) Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().
              zigbee.0	2021-06-09 19:27:57.012	warn	(3367) Read-only state "zigbee.0.info.connection" has been written without ack-flag with value "false"
              zigbee.0	2021-06-09 19:27:57.008	error	(3367) Error: Error while opening serialport 'Error: Error: No such file or directory, cannot open /dev/serial/by-id/usb-dresden_elektronik_ingenieurtechnik_GmbH_ConBee_II_DE2218746-if00' at Drive
              zigbee.0	2021-06-09 19:27:57.007	error	(3367) Failed to start Zigbee
              zigbee.0	2021-06-09 19:27:56.797	info	(3367) Installed Version: iobroker.zigbee@1.5.6
              zigbee.0	2021-06-09 19:27:56.777	info	(3367) Starting Zigbee npm ...
              zigbee.0	2021-06-09 19:27:56.776	info	(3367) Try to reconnect. 1 attempts left
              zigbee.0	2021-06-09 19:27:46.778	warn	(3367) Read-only state "zigbee.0.info.connection" has been written without ack-flag with value "false"
              zigbee.0	2021-06-09 19:27:46.775	error	(3367) Error: Error while opening serialport 'Error: Error: No such file or directory, cannot open /dev/serial/by-id/usb-dresden_elektronik_ingenieurtechnik_GmbH_ConBee_II_DE2218746-if00' at Drive
              zigbee.0	2021-06-09 19:27:46.773	error	(3367) Failed to start Zigbee
              zigbee.0	2021-06-09 19:27:46.630	info	(3367) Installed Version: iobroker.zigbee@1.5.6
              zigbee.0	2021-06-09 19:27:46.626	warn	(3367) Read-only state "zigbee.0.info.connection" has been written without ack-flag with value "false"
              zigbee.0	2021-06-09 19:27:46.394	info	(3367) Starting Zigbee npm ...
              zigbee.0	2021-06-09 19:27:46.294	info	(3367) starting. Version 1.4.1 in /opt/iobroker/node_modules/iobroker.zigbee, node: v12.22.1, js-controller: 3.3.11
              zigbee.0	2021-06-09 19:27:13.360	warn	(3289) Read-only state "zigbee.0.info.pairingMessage" has been written without ack-flag with value "Error: Failed to stop zigbee (TypeError: Cannot read property 'getEntries' of null at Function.l
              zigbee.0	2021-06-09 19:27:13.349	error	(3289) Cannot read property 'getEntries' of null
              zigbee.0	2021-06-09 19:27:13.348	error	(3289) TypeError: Cannot read property 'getEntries' of null at Function.loadFromDatabaseIfNecessary (/opt/iobroker/node_modules/zigbee-herdsman/dist/controller/model/device.js:216:55) at Funct
              zigbee.0	2021-06-09 19:27:13.342	error	(3289) unhandled promise rejection: Cannot read property 'getEntries' of null
              zigbee.0	2021-06-09 19:27:13.341	error	(3289) Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().
              zigbee.0	2021-06-09 19:27:13.340	warn	(3289) Terminated (UNCAUGHT_EXCEPTION): Without reason
              zigbee.0	2021-06-09 19:27:13.338	info	(3289) terminating
              zigbee.0	2021-06-09 19:27:13.336	error	(3289) Failed to stop zigbee (TypeError: Cannot read property 'getEntries' of null at Function.loadFromDatabaseIfNecessary (/opt/iobroker/node_modules/zigbee-herdsman/dist/controller/model/group.j
              zigbee.0	2021-06-09 19:27:13.332	info	(3289) Zigbee: disabling joining new devices.
              zigbee.0	2021-06-09 19:27:13.326	info	(3289) cleaned everything up...
              
              
              AsgothianA Offline
              AsgothianA Offline
              Asgothian
              Developer
              schrieb am zuletzt editiert von Asgothian
              #425

              @ente34 sagte in ZigBee neue Version 1.5.x:

              Error while opening serialport 'Error: Error: No such file or directory, cannot open /dev/serial/by-id/usb-dresden_elektronik_ingenieurtechnik_GmbH_ConBee_II_DE2218746-if00'

              Entweder fehlt am Anfang des Logs noch einiges oder der Zigbee Stick ist seit dem Stromausfall defekt:

              Error while opening serialport 'Error: Error: No such file or directory, cannot open /dev/serial/by-id/usb-dresden_elektronik_ingenieurtechnik_GmbH_ConBee_II_DE2218746-if00'
              

              Nebenbei hast du mindestens 2 unterschiedliche Zigbee Versionen in deinem Log.

              • Welche version hattest du vor dem Stromausfall aktiv (und am laufen?)
              • Warum hast du gedacht das nach einem Stromausfall ein Update / Downgrade des Zigbee Adapters irgend etwas bewirkt ?

              A.

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

              E 1 Antwort Letzte Antwort
              0
              • AsgothianA Asgothian

                @ente34 sagte in ZigBee neue Version 1.5.x:

                Error while opening serialport 'Error: Error: No such file or directory, cannot open /dev/serial/by-id/usb-dresden_elektronik_ingenieurtechnik_GmbH_ConBee_II_DE2218746-if00'

                Entweder fehlt am Anfang des Logs noch einiges oder der Zigbee Stick ist seit dem Stromausfall defekt:

                Error while opening serialport 'Error: Error: No such file or directory, cannot open /dev/serial/by-id/usb-dresden_elektronik_ingenieurtechnik_GmbH_ConBee_II_DE2218746-if00'
                

                Nebenbei hast du mindestens 2 unterschiedliche Zigbee Versionen in deinem Log.

                • Welche version hattest du vor dem Stromausfall aktiv (und am laufen?)
                • Warum hast du gedacht das nach einem Stromausfall ein Update / Downgrade des Zigbee Adapters irgend etwas bewirkt ?

                A.

                E Offline
                E Offline
                ente34
                schrieb am zuletzt editiert von ente34
                #426

                @asgothian
                Habe versuchweise einen Downgrade durchgeführt.
                Bin jetzt wieder bei 1.5.6

                Nach reboot mit deaktiviertem Zigbee und dann nachdem alles hochgelaufen ist zigbee aktiviert:

                zigbee.0	2021-06-09 19:41:24.425	warn	(1903) Read-only state "zigbee.0.info.connection" has been written without ack-flag with value "false"
                zigbee.0	2021-06-09 19:41:24.423	error	(1903) Error: Error while opening serialport 'Error: Error: No such file or directory, cannot open /dev/serial/by-id/usb-dresden_elektronik_ingenieurtechnik_GmbH_ConBee_II_DE2218746-if00' at Drive
                zigbee.0	2021-06-09 19:41:24.421	error	(1903) Failed to start Zigbee
                zigbee.0	2021-06-09 19:41:24.264	info	(1903) Installed Version: iobroker.zigbee@1.5.6
                zigbee.0	2021-06-09 19:41:24.258	warn	(1903) Read-only state "zigbee.0.info.connection" has been written without ack-flag with value "false"
                zigbee.0	2021-06-09 19:41:24.053	info	(1903) Starting Zigbee npm ...
                zigbee.0	2021-06-09 19:41:23.960	info	(1903) starting. Version 1.4.1 in /opt/iobroker/node_modules/iobroker.zigbee, node: v12.22.1, js-controller: 3.3.11
                host.raspi-iobroker	2021-06-09 19:41:21.617	info	instance system.adapter.zigbee.0 started with pid 1903
                host.raspi-iobroker	2021-06-09 19:40:51.545	info	Restart adapter system.adapter.zigbee.0 because enabled
                host.raspi-iobroker	2021-06-09 19:40:51.544	error	instance system.adapter.zigbee.0 terminated with code 6 (UNCAUGHT_EXCEPTION)
                zigbee.0	2021-06-09 19:40:50.950	warn	(1827) Read-only state "zigbee.0.info.pairingMessage" has been written without ack-flag with value "Error: Failed to stop zigbee (TypeError: Cannot read property 'getEntries' of null at Function.l
                zigbee.0	2021-06-09 19:40:50.939	error	(1827) Cannot read property 'getEntries' of null
                zigbee.0	2021-06-09 19:40:50.938	error	(1827) TypeError: Cannot read property 'getEntries' of null at Function.loadFromDatabaseIfNecessary (/opt/iobroker/node_modules/zigbee-herdsman/dist/controller/model/device.js:216:55) at Funct
                zigbee.0	2021-06-09 19:40:50.931	error	(1827) unhandled promise rejection: Cannot read property 'getEntries' of null
                zigbee.0	2021-06-09 19:40:50.928	error	(1827) Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().
                zigbee.0	2021-06-09 19:40:50.926	warn	(1827) Terminated (UNCAUGHT_EXCEPTION): Without reason
                zigbee.0	2021-06-09 19:40:50.924	info	(1827) terminating
                zigbee.0	2021-06-09 19:40:50.922	error	(1827) Failed to stop zigbee (TypeError: Cannot read property 'getEntries' of null at Function.loadFromDatabaseIfNecessary (/opt/iobroker/node_modules/zigbee-herdsman/dist/controller/model/group.j
                zigbee.0	2021-06-09 19:40:50.918	info	(1827) Zigbee: disabling joining new devices.
                zigbee.0	2021-06-09 19:40:50.912	info	(1827) cleaned everything up...
                zigbee.0	2021-06-09 19:40:50.901	error	(1827) Error while opening serialport 'Error: Error: No such file or directory, cannot open /dev/serial/by-id/usb-dresden_elektronik_ingenieurtechnik_GmbH_ConBee_II_DE2218746-if00'
                zigbee.0	2021-06-09 19:40:50.900	error	(1827) Error: Error while opening serialport 'Error: Error: No such file or directory, cannot open /dev/serial/by-id/usb-dresden_elektronik_ingenieurtechnik_GmbH_ConBee_II_DE2218746-if00' at Drive
                zigbee.0	2021-06-09 19:40:50.899	error	(1827) unhandled promise rejection: Error while opening serialport 'Error: Error: No such file or directory, cannot open /dev/serial/by-id/usb-dresden_elektronik_ingenieurtechnik_GmbH_ConBee_II_DE2218
                zigbee.0	2021-06-09 19:40:50.897	error	(1827) Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().
                zigbee.0	2021-06-09 19:40:30.083	warn	(1827) Read-only state "zigbee.0.info.connection" has been written without ack-flag with value "false"
                zigbee.0	2021-06-09 19:40:30.078	error	(1827) Error: Error while opening serialport 'Error: Error: No such file or directory, cannot open /dev/serial/by-id/usb-dresden_elektronik_ingenieurtechnik_GmbH_ConBee_II_DE2218746-if00' at Drive
                zigbee.0	2021-06-09 19:40:30.077	error	(1827) Failed to start Zigbee
                zigbee.0	2021-06-09 19:40:29.922	info	(1827) Installed Version: iobroker.zigbee@1.5.6
                zigbee.0	2021-06-09 19:40:29.893	info	(1827) Starting Zigbee npm ...
                zigbee.0	2021-06-09 19:40:29.892	info	(1827) Try to reconnect. 1 attempts left
                zigbee.0	2021-06-09 19:40:19.893	warn	(1827) Read-only state "zigbee.0.info.connection" has been written without ack-flag with value "false"
                zigbee.0	2021-06-09 19:40:19.891	error	(1827) Error: Error while opening serialport 'Error: Error: No such file or directory, cannot open /dev/serial/by-id/usb-dresden_elektronik_ingenieurtechnik_GmbH_ConBee_II_DE2218746-if00' at Drive
                zigbee.0	2021-06-09 19:40:19.890	error	(1827) Failed to start Zigbee
                zigbee.0	2021-06-09 19:40:19.728	info	(1827) Installed Version: iobroker.zigbee@1.5.6
                zigbee.0	2021-06-09 19:40:19.724	warn	(1827) Read-only state "zigbee.0.info.connection" has been written without ack-flag with value "false"
                zigbee.0	2021-06-09 19:40:19.492	info	(1827) Starting Zigbee npm ...
                zigbee.0	2021-06-09 19:40:19.377	info	(1827) starting. Version 1.4.1 in /opt/iobroker/node_modules/iobroker.zigbee, node: v12.22.1, js-controller: 3.3.11
                host.raspi-iobroker	2021-06-09 19:40:16.846	info	instance system.adapter.zigbee.0 started with pid 1827
                host.raspi-iobroker	2021-06-09 19:40:16.799	info	"system.adapter.zigbee.0" enabled
                
                
                AsgothianA 1 Antwort Letzte Antwort
                0
                • E ente34

                  @asgothian
                  Habe versuchweise einen Downgrade durchgeführt.
                  Bin jetzt wieder bei 1.5.6

                  Nach reboot mit deaktiviertem Zigbee und dann nachdem alles hochgelaufen ist zigbee aktiviert:

                  zigbee.0	2021-06-09 19:41:24.425	warn	(1903) Read-only state "zigbee.0.info.connection" has been written without ack-flag with value "false"
                  zigbee.0	2021-06-09 19:41:24.423	error	(1903) Error: Error while opening serialport 'Error: Error: No such file or directory, cannot open /dev/serial/by-id/usb-dresden_elektronik_ingenieurtechnik_GmbH_ConBee_II_DE2218746-if00' at Drive
                  zigbee.0	2021-06-09 19:41:24.421	error	(1903) Failed to start Zigbee
                  zigbee.0	2021-06-09 19:41:24.264	info	(1903) Installed Version: iobroker.zigbee@1.5.6
                  zigbee.0	2021-06-09 19:41:24.258	warn	(1903) Read-only state "zigbee.0.info.connection" has been written without ack-flag with value "false"
                  zigbee.0	2021-06-09 19:41:24.053	info	(1903) Starting Zigbee npm ...
                  zigbee.0	2021-06-09 19:41:23.960	info	(1903) starting. Version 1.4.1 in /opt/iobroker/node_modules/iobroker.zigbee, node: v12.22.1, js-controller: 3.3.11
                  host.raspi-iobroker	2021-06-09 19:41:21.617	info	instance system.adapter.zigbee.0 started with pid 1903
                  host.raspi-iobroker	2021-06-09 19:40:51.545	info	Restart adapter system.adapter.zigbee.0 because enabled
                  host.raspi-iobroker	2021-06-09 19:40:51.544	error	instance system.adapter.zigbee.0 terminated with code 6 (UNCAUGHT_EXCEPTION)
                  zigbee.0	2021-06-09 19:40:50.950	warn	(1827) Read-only state "zigbee.0.info.pairingMessage" has been written without ack-flag with value "Error: Failed to stop zigbee (TypeError: Cannot read property 'getEntries' of null at Function.l
                  zigbee.0	2021-06-09 19:40:50.939	error	(1827) Cannot read property 'getEntries' of null
                  zigbee.0	2021-06-09 19:40:50.938	error	(1827) TypeError: Cannot read property 'getEntries' of null at Function.loadFromDatabaseIfNecessary (/opt/iobroker/node_modules/zigbee-herdsman/dist/controller/model/device.js:216:55) at Funct
                  zigbee.0	2021-06-09 19:40:50.931	error	(1827) unhandled promise rejection: Cannot read property 'getEntries' of null
                  zigbee.0	2021-06-09 19:40:50.928	error	(1827) Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().
                  zigbee.0	2021-06-09 19:40:50.926	warn	(1827) Terminated (UNCAUGHT_EXCEPTION): Without reason
                  zigbee.0	2021-06-09 19:40:50.924	info	(1827) terminating
                  zigbee.0	2021-06-09 19:40:50.922	error	(1827) Failed to stop zigbee (TypeError: Cannot read property 'getEntries' of null at Function.loadFromDatabaseIfNecessary (/opt/iobroker/node_modules/zigbee-herdsman/dist/controller/model/group.j
                  zigbee.0	2021-06-09 19:40:50.918	info	(1827) Zigbee: disabling joining new devices.
                  zigbee.0	2021-06-09 19:40:50.912	info	(1827) cleaned everything up...
                  zigbee.0	2021-06-09 19:40:50.901	error	(1827) Error while opening serialport 'Error: Error: No such file or directory, cannot open /dev/serial/by-id/usb-dresden_elektronik_ingenieurtechnik_GmbH_ConBee_II_DE2218746-if00'
                  zigbee.0	2021-06-09 19:40:50.900	error	(1827) Error: Error while opening serialport 'Error: Error: No such file or directory, cannot open /dev/serial/by-id/usb-dresden_elektronik_ingenieurtechnik_GmbH_ConBee_II_DE2218746-if00' at Drive
                  zigbee.0	2021-06-09 19:40:50.899	error	(1827) unhandled promise rejection: Error while opening serialport 'Error: Error: No such file or directory, cannot open /dev/serial/by-id/usb-dresden_elektronik_ingenieurtechnik_GmbH_ConBee_II_DE2218
                  zigbee.0	2021-06-09 19:40:50.897	error	(1827) Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().
                  zigbee.0	2021-06-09 19:40:30.083	warn	(1827) Read-only state "zigbee.0.info.connection" has been written without ack-flag with value "false"
                  zigbee.0	2021-06-09 19:40:30.078	error	(1827) Error: Error while opening serialport 'Error: Error: No such file or directory, cannot open /dev/serial/by-id/usb-dresden_elektronik_ingenieurtechnik_GmbH_ConBee_II_DE2218746-if00' at Drive
                  zigbee.0	2021-06-09 19:40:30.077	error	(1827) Failed to start Zigbee
                  zigbee.0	2021-06-09 19:40:29.922	info	(1827) Installed Version: iobroker.zigbee@1.5.6
                  zigbee.0	2021-06-09 19:40:29.893	info	(1827) Starting Zigbee npm ...
                  zigbee.0	2021-06-09 19:40:29.892	info	(1827) Try to reconnect. 1 attempts left
                  zigbee.0	2021-06-09 19:40:19.893	warn	(1827) Read-only state "zigbee.0.info.connection" has been written without ack-flag with value "false"
                  zigbee.0	2021-06-09 19:40:19.891	error	(1827) Error: Error while opening serialport 'Error: Error: No such file or directory, cannot open /dev/serial/by-id/usb-dresden_elektronik_ingenieurtechnik_GmbH_ConBee_II_DE2218746-if00' at Drive
                  zigbee.0	2021-06-09 19:40:19.890	error	(1827) Failed to start Zigbee
                  zigbee.0	2021-06-09 19:40:19.728	info	(1827) Installed Version: iobroker.zigbee@1.5.6
                  zigbee.0	2021-06-09 19:40:19.724	warn	(1827) Read-only state "zigbee.0.info.connection" has been written without ack-flag with value "false"
                  zigbee.0	2021-06-09 19:40:19.492	info	(1827) Starting Zigbee npm ...
                  zigbee.0	2021-06-09 19:40:19.377	info	(1827) starting. Version 1.4.1 in /opt/iobroker/node_modules/iobroker.zigbee, node: v12.22.1, js-controller: 3.3.11
                  host.raspi-iobroker	2021-06-09 19:40:16.846	info	instance system.adapter.zigbee.0 started with pid 1827
                  host.raspi-iobroker	2021-06-09 19:40:16.799	info	"system.adapter.zigbee.0" enabled
                  
                  
                  AsgothianA Offline
                  AsgothianA Offline
                  Asgothian
                  Developer
                  schrieb am zuletzt editiert von Asgothian
                  #427

                  @ente34 sagte in ZigBee neue Version 1.5.x:

                  @asgothian
                  Habe versuchweise einen Downgrade durchgeführt.
                  Bin jetzt wieder bei 1.5.6

                  :face_palm:

                  Um dem Problem auf den Grund zu gehen musst du heraus bekommen warum der serielle Port nicht mehr verfügbar ist. Das Log sagt eindeutig das symlink nicht existiert.

                  Insbesondere bei Stromausfällen / RaspberryPi Abstürzen / Proxxmox Updates die plötzlich einen laufenden Zigbee Adapter zerlegen ist zu 95% ein Problem mit der Verbindung zum Koordinator die Ursache.

                  A.

                  Nachtrag: Oh Wunder, auch in diesem Log findet sich bei jedem Startversuch die gleiche Meldung:

                  Error: Error while opening serialport 'Error: Error: No such file or directory, cannot open /dev/serial/by-id/usb-dresden_elektronik_ingenieurtechnik_GmbH_ConBee_II_DE2218746-if00'
                  

                  Der Stick wird also immer noch nicht erkannt.

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

                  E 2 Antworten Letzte Antwort
                  0
                  • AsgothianA Asgothian

                    @ente34 sagte in ZigBee neue Version 1.5.x:

                    @asgothian
                    Habe versuchweise einen Downgrade durchgeführt.
                    Bin jetzt wieder bei 1.5.6

                    :face_palm:

                    Um dem Problem auf den Grund zu gehen musst du heraus bekommen warum der serielle Port nicht mehr verfügbar ist. Das Log sagt eindeutig das symlink nicht existiert.

                    Insbesondere bei Stromausfällen / RaspberryPi Abstürzen / Proxxmox Updates die plötzlich einen laufenden Zigbee Adapter zerlegen ist zu 95% ein Problem mit der Verbindung zum Koordinator die Ursache.

                    A.

                    Nachtrag: Oh Wunder, auch in diesem Log findet sich bei jedem Startversuch die gleiche Meldung:

                    Error: Error while opening serialport 'Error: Error: No such file or directory, cannot open /dev/serial/by-id/usb-dresden_elektronik_ingenieurtechnik_GmbH_ConBee_II_DE2218746-if00'
                    

                    Der Stick wird also immer noch nicht erkannt.

                    E Offline
                    E Offline
                    ente34
                    schrieb am zuletzt editiert von
                    #428

                    @asgothian
                    Habe einen neuen link 'serial1'

                    pi@raspi-iobroker:~ $ ls -l /dev/serial1
                    lrwxrwxrwx 1 root root 7 Jun  9 19:36 /dev/serial1 -> ttyAMA0
                    pi@raspi-iobroker:~ $
                    
                    
                    1 Antwort Letzte Antwort
                    0
                    • AsgothianA Asgothian

                      @ente34 sagte in ZigBee neue Version 1.5.x:

                      @asgothian
                      Habe versuchweise einen Downgrade durchgeführt.
                      Bin jetzt wieder bei 1.5.6

                      :face_palm:

                      Um dem Problem auf den Grund zu gehen musst du heraus bekommen warum der serielle Port nicht mehr verfügbar ist. Das Log sagt eindeutig das symlink nicht existiert.

                      Insbesondere bei Stromausfällen / RaspberryPi Abstürzen / Proxxmox Updates die plötzlich einen laufenden Zigbee Adapter zerlegen ist zu 95% ein Problem mit der Verbindung zum Koordinator die Ursache.

                      A.

                      Nachtrag: Oh Wunder, auch in diesem Log findet sich bei jedem Startversuch die gleiche Meldung:

                      Error: Error while opening serialport 'Error: Error: No such file or directory, cannot open /dev/serial/by-id/usb-dresden_elektronik_ingenieurtechnik_GmbH_ConBee_II_DE2218746-if00'
                      

                      Der Stick wird also immer noch nicht erkannt.

                      E Offline
                      E Offline
                      ente34
                      schrieb am zuletzt editiert von
                      #429

                      @asgothian
                      Erst mal vielen Dank für den schnellen Support!

                      1 Antwort Letzte Antwort
                      0
                      • G Offline
                        G Offline
                        gosund
                        schrieb am zuletzt editiert von
                        #430

                        @asgothian
                        @artek

                        Schlechte Nachrichten: Das komplette löschen, installieren und neu Anlernen hat nichts gebracht.
                        Wie die letzten Tage auch hat sich der Adapter wieder innerhalb eines Tages aufgehängt. Ich mußte den Pi wieder komplett rebooten, damit es wieder geht.

                        Hilfe, ich weiß mir absolut nicht mehr zu helfen. Was kann ich noch versuchen?

                        R 1 Antwort Letzte Antwort
                        0
                        • G gosund

                          @asgothian
                          @artek

                          Schlechte Nachrichten: Das komplette löschen, installieren und neu Anlernen hat nichts gebracht.
                          Wie die letzten Tage auch hat sich der Adapter wieder innerhalb eines Tages aufgehängt. Ich mußte den Pi wieder komplett rebooten, damit es wieder geht.

                          Hilfe, ich weiß mir absolut nicht mehr zu helfen. Was kann ich noch versuchen?

                          R Offline
                          R Offline
                          rewenode
                          schrieb am zuletzt editiert von
                          #431

                          Ich weis echt nicht mehr weiter.
                          Bekomme einfach nicht das Update vom 1.5.5 auf 1.5.6 hin.
                          iob im Docker Container mit 4gb auf einem Rock64
                          node.js - v12.18.3
                          npm - 6.14.6
                          zigbee stick CC2538 + CC2592 von dimaiv

                          Bisher gab es nie die geringsten zigbee Updateprobleme. Nur die 1.5.6 bekomme ich nicht installiert.
                          Hier das Log:

                           01:23:20.786 - info: zigbee.0 (3129) starting. Version 1.5.6 in /opt/iobroker/node_modules/iobroker.zigbee, node: v12.18.3, js-controller: 3.2.16
                          2021-06-11 01:23:21.151 - info: zigbee.0 (3129) Starting Zigbee npm ...
                          2021-06-11 01:23:22.084 - info: zigbee.0 (3129) Installed Version: iobroker.zigbee@1.5.6
                          2021-06-11 01:23:23.678 - error: zigbee.0 (3129) Configuration is not consistent with adapter state/backup!
                          2021-06-11 01:23:23.681 - error: zigbee.0 (3129) - PAN ID: configured=6754, adapter=65535
                          2021-06-11 01:23:23.683 - error: zigbee.0 (3129) - Extended PAN ID: configured=00124b001940c0ba, adapter=0000000000000000
                          2021-06-11 01:23:23.685 - error: zigbee.0 (3129) - Network Key: configured=01030507090b0d0f00020406080a0c0d, adapter=01030507090b0d0f00020406080a0c0d
                          2021-06-11 01:23:23.686 - error: zigbee.0 (3129) - Channel List: configured=11, adapter=
                          2021-06-11 01:23:23.688 - error: zigbee.0 (3129) Please update configuration to prevent further issues.
                          2021-06-11 01:23:23.689 - error: zigbee.0 (3129) If you wish to re-commission your network, please remove coordinator backup at /opt/iobroker/iobroker-data/zigbee_0/nvbackup.json.
                          2021-06-11 01:23:23.691 - error: zigbee.0 (3129) Re-commissioning your network will require re-pairing of all devices!
                          2021-06-11 01:23:23.694 - error: zigbee.0 (3129) Starting zigbee-herdsman problem : "startup failed - configuration-adapter mismatch - see logs above for more information"
                          2021-06-11 01:23:23.695 - error: zigbee.0 (3129) Failed to start Zigbee
                          2021-06-11 01:23:23.697 - error: zigbee.0 (3129) Error herdsman start
                          2021-06-11 01:23:33.700 - info: zigbee.0 (3129) Try to reconnect. 1 attempts left
                          2021-06-11 01:23:33.702 - info: zigbee.0 (3129) Starting Zigbee npm ...
                          2021-06-11 01:23:33.735 - info: zigbee.0 (3129) Installed Version: iobroker.zigbee@1.5.6
                          2021-06-11 01:23:33.980 - error: zigbee.0 (3129) Starting zigbee-herdsman problem : "Error while opening serialport 'Error: Error Resource temporarily unavailable Cannot lock port'"
                          2021-06-11 01:23:33.982 - error: zigbee.0 (3129) Failed to start Zigbee
                          2021-06-11 01:23:33.984 - error: zigbee.0 (3129) Error herdsman start
                          2021-06-11 01:25:09.693 - info: host.iobroker stopInstance system.adapter.zigbee.0 (force=false, process=true)
                          2021-06-11 01:25:09.717 - info: mqtt.0 (705) send2Server system.adapter.zigbee.0.sigKill[iob/system/adapter/zigbee/0/sigKill]
                          2021-06-11 01:25:09.718 - info: zigbee.0 (3129) Got terminate signal TERMINATE_YOURSELF
                          2021-06-11 01:25:09.723 - info: zigbee.0 (3129) cleaned everything up...
                          2021-06-11 01:25:09.730 - info: zigbee.0 (3129) Zigbee: disabling joining new devices.
                          2021-06-11 01:25:09.733 - warn: zigbee.0 (3129) Failed to stop zigbee during startup
                          2021-06-11 01:25:09.735 - info: zigbee.0 (3129) terminating
                          2021-06-11 01:25:09.737 - info: zigbee.0 (3129) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
                          2021-06-11 01:25:09.739 - error: zigbee.0 (3129) 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-06-11 01:25:09.740 - error: zigbee.0 (3129) unhandled promise rejection: Cannot read property 'getEntries' of null
                          2021-06-11 01:25:09.743 - error: zigbee.0 (3129) TypeError: Cannot read property 'getEntries' of null
                          at Function.loadFromDatabaseIfNecessary (/opt/iobroker/node_modules/iobroker.zigbee/node_modules/zigbee-herdsman/dist/controller/model/device.js:220:55)
                          at Function.all (/opt/iobroker/node_modules/iobroker.zigbee/node_modules/zigbee-herdsman/dist/controller/model/device.js:240:16)
                          at Controller.getDevices (/opt/iobroker/node_modules/iobroker.zigbee/node_modules/zigbee-herdsman/dist/controller/controller.js:303:31)
                          at ZigbeeController.getClients (/opt/iobroker/node_modules/iobroker.zigbee/lib/zigbeecontroller.js:228:49)
                          at DeviceAvailability.stop (/opt/iobroker/node_modules/iobroker.zigbee/lib/zbDeviceAvailability.js:222:43)
                          at ZigbeeController.callExtensionMethod (/opt/iobroker/node_modules/iobroker.zigbee/lib/zigbeecontroller.js:214:42)
                          at ZigbeeController.stop (/opt/iobroker/node_modules/iobroker.zigbee/lib/zigbeecontroller.js:385:20)
                          at Zigbee.onUnload (/opt/iobroker/node_modules/iobroker.zigbee/main.js:696:41)
                          at processTicksAndRejections (internal/process/task_queues.js:97:5)
                          

                          Was kann ich noch tun ?

                          arteckA 1 Antwort Letzte Antwort
                          0
                          • R rewenode

                            Ich weis echt nicht mehr weiter.
                            Bekomme einfach nicht das Update vom 1.5.5 auf 1.5.6 hin.
                            iob im Docker Container mit 4gb auf einem Rock64
                            node.js - v12.18.3
                            npm - 6.14.6
                            zigbee stick CC2538 + CC2592 von dimaiv

                            Bisher gab es nie die geringsten zigbee Updateprobleme. Nur die 1.5.6 bekomme ich nicht installiert.
                            Hier das Log:

                             01:23:20.786 - info: zigbee.0 (3129) starting. Version 1.5.6 in /opt/iobroker/node_modules/iobroker.zigbee, node: v12.18.3, js-controller: 3.2.16
                            2021-06-11 01:23:21.151 - info: zigbee.0 (3129) Starting Zigbee npm ...
                            2021-06-11 01:23:22.084 - info: zigbee.0 (3129) Installed Version: iobroker.zigbee@1.5.6
                            2021-06-11 01:23:23.678 - error: zigbee.0 (3129) Configuration is not consistent with adapter state/backup!
                            2021-06-11 01:23:23.681 - error: zigbee.0 (3129) - PAN ID: configured=6754, adapter=65535
                            2021-06-11 01:23:23.683 - error: zigbee.0 (3129) - Extended PAN ID: configured=00124b001940c0ba, adapter=0000000000000000
                            2021-06-11 01:23:23.685 - error: zigbee.0 (3129) - Network Key: configured=01030507090b0d0f00020406080a0c0d, adapter=01030507090b0d0f00020406080a0c0d
                            2021-06-11 01:23:23.686 - error: zigbee.0 (3129) - Channel List: configured=11, adapter=
                            2021-06-11 01:23:23.688 - error: zigbee.0 (3129) Please update configuration to prevent further issues.
                            2021-06-11 01:23:23.689 - error: zigbee.0 (3129) If you wish to re-commission your network, please remove coordinator backup at /opt/iobroker/iobroker-data/zigbee_0/nvbackup.json.
                            2021-06-11 01:23:23.691 - error: zigbee.0 (3129) Re-commissioning your network will require re-pairing of all devices!
                            2021-06-11 01:23:23.694 - error: zigbee.0 (3129) Starting zigbee-herdsman problem : "startup failed - configuration-adapter mismatch - see logs above for more information"
                            2021-06-11 01:23:23.695 - error: zigbee.0 (3129) Failed to start Zigbee
                            2021-06-11 01:23:23.697 - error: zigbee.0 (3129) Error herdsman start
                            2021-06-11 01:23:33.700 - info: zigbee.0 (3129) Try to reconnect. 1 attempts left
                            2021-06-11 01:23:33.702 - info: zigbee.0 (3129) Starting Zigbee npm ...
                            2021-06-11 01:23:33.735 - info: zigbee.0 (3129) Installed Version: iobroker.zigbee@1.5.6
                            2021-06-11 01:23:33.980 - error: zigbee.0 (3129) Starting zigbee-herdsman problem : "Error while opening serialport 'Error: Error Resource temporarily unavailable Cannot lock port'"
                            2021-06-11 01:23:33.982 - error: zigbee.0 (3129) Failed to start Zigbee
                            2021-06-11 01:23:33.984 - error: zigbee.0 (3129) Error herdsman start
                            2021-06-11 01:25:09.693 - info: host.iobroker stopInstance system.adapter.zigbee.0 (force=false, process=true)
                            2021-06-11 01:25:09.717 - info: mqtt.0 (705) send2Server system.adapter.zigbee.0.sigKill[iob/system/adapter/zigbee/0/sigKill]
                            2021-06-11 01:25:09.718 - info: zigbee.0 (3129) Got terminate signal TERMINATE_YOURSELF
                            2021-06-11 01:25:09.723 - info: zigbee.0 (3129) cleaned everything up...
                            2021-06-11 01:25:09.730 - info: zigbee.0 (3129) Zigbee: disabling joining new devices.
                            2021-06-11 01:25:09.733 - warn: zigbee.0 (3129) Failed to stop zigbee during startup
                            2021-06-11 01:25:09.735 - info: zigbee.0 (3129) terminating
                            2021-06-11 01:25:09.737 - info: zigbee.0 (3129) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
                            2021-06-11 01:25:09.739 - error: zigbee.0 (3129) 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-06-11 01:25:09.740 - error: zigbee.0 (3129) unhandled promise rejection: Cannot read property 'getEntries' of null
                            2021-06-11 01:25:09.743 - error: zigbee.0 (3129) TypeError: Cannot read property 'getEntries' of null
                            at Function.loadFromDatabaseIfNecessary (/opt/iobroker/node_modules/iobroker.zigbee/node_modules/zigbee-herdsman/dist/controller/model/device.js:220:55)
                            at Function.all (/opt/iobroker/node_modules/iobroker.zigbee/node_modules/zigbee-herdsman/dist/controller/model/device.js:240:16)
                            at Controller.getDevices (/opt/iobroker/node_modules/iobroker.zigbee/node_modules/zigbee-herdsman/dist/controller/controller.js:303:31)
                            at ZigbeeController.getClients (/opt/iobroker/node_modules/iobroker.zigbee/lib/zigbeecontroller.js:228:49)
                            at DeviceAvailability.stop (/opt/iobroker/node_modules/iobroker.zigbee/lib/zbDeviceAvailability.js:222:43)
                            at ZigbeeController.callExtensionMethod (/opt/iobroker/node_modules/iobroker.zigbee/lib/zigbeecontroller.js:214:42)
                            at ZigbeeController.stop (/opt/iobroker/node_modules/iobroker.zigbee/lib/zigbeecontroller.js:385:20)
                            at Zigbee.onUnload (/opt/iobroker/node_modules/iobroker.zigbee/main.js:696:41)
                            at processTicksAndRejections (internal/process/task_queues.js:97:5)
                            

                            Was kann ich noch tun ?

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

                            @rewenode geh auf version 1.4.1 und dann wieder auf die 1.5.6 gehts dann ?

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

                            R 1 Antwort Letzte Antwort
                            0
                            • arteckA arteck

                              @rewenode geh auf version 1.4.1 und dann wieder auf die 1.5.6 gehts dann ?

                              R Offline
                              R Offline
                              rewenode
                              schrieb am zuletzt editiert von
                              #433

                              @arteck Reicht da ein Downgrade adapter->Bestimmte version installieren -> 1.4.1 ?
                              Oder muss erst den Adapter (1.5.5) löschen?
                              Und falls löschen, wie kann ich alle meine Geräte behalten ohne alle neu anlernen zu müssen?

                              Sry wenn die Fragen etwas naiv sein sollten. Ich sag ja, bisher reichte ein Knopfdruck und alles neu anlernen wäre hier ziemlich mit Arbeit verbunden bei kleinem Zeitfenster.

                              Jedenfalls schonmal danke für deine Hilfe.

                              G 1 Antwort Letzte Antwort
                              0
                              • R rewenode

                                @arteck Reicht da ein Downgrade adapter->Bestimmte version installieren -> 1.4.1 ?
                                Oder muss erst den Adapter (1.5.5) löschen?
                                Und falls löschen, wie kann ich alle meine Geräte behalten ohne alle neu anlernen zu müssen?

                                Sry wenn die Fragen etwas naiv sein sollten. Ich sag ja, bisher reichte ein Knopfdruck und alles neu anlernen wäre hier ziemlich mit Arbeit verbunden bei kleinem Zeitfenster.

                                Jedenfalls schonmal danke für deine Hilfe.

                                G Offline
                                G Offline
                                gosund
                                schrieb am zuletzt editiert von
                                #434

                                @arteck @Asgothian

                                FYI: Hatte gestern Abend auf die 1.5.5 herunter gegraded. Das Problem besteht immer noch: nach ziemlich genau 24 Stunden hängt sich der Adapter auf. Ich mußte den Pi gerade eben wieder booten.

                                Irgend eine Idee, was ich noch machen kann?

                                Und nochwas: Seit dem Downgrade bekomme ich ständig folgende Meldung im Log:

                                zigbee.0 (1671) Failed to DeviceConfigure.onZigbeeEvent (Error: 'LED1623G12' has no configure
                                    at Object.getConfigureKey (/opt/iobroker/node_modules/zigbee-herdsman-converters/lib/configureKey.js:20:15)
                                    at DeviceConfigure.shouldConfigure (/opt/iobroker/node_modules/iobroker.zigbee/lib/zbDeviceConfigure.js:33:38)
                                    at DeviceConfigure.onZigbeeEvent (/opt/iobroker/node_modules/iobroker.zigbee/lib/zbDeviceConfigure.js:76:22)
                                    at ZigbeeController.callExtensionMethod (/opt/iobroker/node_modules/iobroker.zigbee/lib/zigbeecontroller.js:196:42)
                                    at ZigbeeController.handleMessage (/opt/iobroker/node_modules/iobroker.zigbee/lib/zigbeecontroller.js:560:14))
                                

                                Woher kommt LED1623G12? Ich habe alle Devices umbenannt, kann also nicht sagen, welches er meint. Irgend eine Idee?

                                arteckA 1 Antwort Letzte Antwort
                                0
                                • R Offline
                                  R Offline
                                  Rushmed
                                  Most Active
                                  schrieb am zuletzt editiert von Rushmed
                                  #435

                                  Hallo,

                                  ich komme gerade vom Ikea Einkauf und habe zwei kleine Probleme.
                                  Die Fernbedienung STYRBAR wird vom Adapter als W2094 erkannt. Auf dem Gerät steht aber W2044 und in der Anleitung E2002. Das ist erstmal kein Problem für mich, allerdings funktionieren Druck und langer Druck nur bei den links/rechts Tasten. Die anderen beiden Tasten funktionieren garnicht. f750e091-c6d7-4da2-af97-ba27597956bb-grafik.png
                                  Wenn ich STYRBAR direkt mit einer Lampe kopple geht alles.
                                  Wenn ich den Adapter auf debug stelle kommen Tastendrücke an:

                                  zigbee.0	2021-06-12 19:09:59.315	debug	(18506) Publish {"action":"brightness_stop","action_group":901} to "842e14fffe471ae1"
                                  zigbee.0	2021-06-12 19:09:59.300	debug	(18506) Type commandStopWithOnOff device {"type":"device","device":{"ID":33,"_type":"EndDevice","_ieeeAddr":"0x842e14fffe471ae1","_networkAddress":24375,"_manufacturerID":4476,"_endpoints":[{"ID":1,"p
                                  zigbee.0	2021-06-12 19:09:59.299	debug	(18506) Received Zigbee message from '0x842e14fffe471ae1', type 'commandStopWithOnOff', cluster 'genLevelCtrl', data '{}' from endpoint 1 with groupID 901
                                  zigbee.0	2021-06-12 19:09:59.297	debug	(18506) handleMessage. {"type":"commandStopWithOnOff","device":{"ID":33,"_type":"EndDevice","_ieeeAddr":"0x842e14fffe471ae1","_networkAddress":24375,"_manufacturerID":4476,"_endpoints":[{"ID":1,"profi
                                  zigbee.0	2021-06-12 19:09:58.939	debug	(18506) Publish {"action":"brightness_move_down","action_rate":83,"action_group":901} to "842e14fffe471ae1"
                                  zigbee.0	2021-06-12 19:09:58.926	debug	(18506) Type commandMove device {"type":"device","device":{"ID":33,"_type":"EndDevice","_ieeeAddr":"0x842e14fffe471ae1","_networkAddress":24375,"_manufacturerID":4476,"_endpoints":[{"ID":1,"profileID"
                                  zigbee.0	2021-06-12 19:09:58.926	debug	(18506) Received Zigbee message from '0x842e14fffe471ae1', type 'commandMove', cluster 'genLevelCtrl', data '{"movemode":1,"rate":83}' from endpoint 1 with groupID 901
                                  zigbee.0	2021-06-12 19:09:58.924	debug	(18506) handleMessage. {"type":"commandMove","device":{"ID":33,"_type":"EndDevice","_ieeeAddr":"0x842e14fffe471ae1","_networkAddress":24375,"_manufacturerID":4476,"_endpoints":[{"ID":1,"profileID":260
                                  zigbee.0	2021-06-12 19:09:57.127	debug	(18506) Publish {"action":"brightness_stop","action_group":901} to "842e14fffe471ae1"
                                  zigbee.0	2021-06-12 19:09:57.116	debug	(18506) Type commandStopWithOnOff device {"type":"device","device":{"ID":33,"_type":"EndDevice","_ieeeAddr":"0x842e14fffe471ae1","_networkAddress":24375,"_manufacturerID":4476,"_endpoints":[{"ID":1,"p
                                  zigbee.0	2021-06-12 19:09:57.114	debug	(18506) Received Zigbee message from '0x842e14fffe471ae1', type 'commandStopWithOnOff', cluster 'genLevelCtrl', data '{}' from endpoint 1 with groupID 901
                                  zigbee.0	2021-06-12 19:09:57.113	debug	(18506) handleMessage. {"type":"commandStopWithOnOff","device":{"ID":33,"_type":"EndDevice","_ieeeAddr":"0x842e14fffe471ae1","_networkAddress":24375,"_manufacturerID":4476,"_endpoints":[{"ID":1,"profi
                                  zigbee.0	2021-06-12 19:09:56.660	debug	(18506) Publish {"action":"brightness_move_up","action_rate":83,"action_group":901} to "842e14fffe471ae1"
                                  zigbee.0	2021-06-12 19:09:56.644	debug	(18506) Type commandMoveWithOnOff device {"type":"device","device":{"ID":33,"_type":"EndDevice","_ieeeAddr":"0x842e14fffe471ae1","_networkAddress":24375,"_manufacturerID":4476,"_endpoints":[{"ID":1,"p
                                  zigbee.0	2021-06-12 19:09:56.643	debug	(18506) Received Zigbee message from '0x842e14fffe471ae1', type 'commandMoveWithOnOff', cluster 'genLevelCtrl', data '{"movemode":0,"rate":83}' from endpoint 1 with groupID 901
                                  zigbee.0	2021-06-12 19:09:56.640	debug	(18506) handleMessage. {"type":"commandMoveWithOnOff","device":{"ID":33,"_type":"EndDevice","_ieeeAddr":"0x842e14fffe471ae1","_networkAddress":24375,"_manufacturerID":4476,"_endpoints":[{"ID":1,"profi
                                  zigbee.0	2021-06-12 19:09:54.926	debug	(18506) Publish {"action":"on","action_group":901} to "842e14fffe471ae1"
                                  zigbee.0	2021-06-12 19:09:54.917	debug	(18506) Type commandOn device {"type":"device","device":{"ID":33,"_type":"EndDevice","_ieeeAddr":"0x842e14fffe471ae1","_networkAddress":24375,"_manufacturerID":4476,"_endpoints":[{"ID":1,"profileID":2
                                  zigbee.0	2021-06-12 19:09:54.916	debug	(18506) Received Zigbee message from '0x842e14fffe471ae1', type 'commandOn', cluster 'genOnOff', data '{}' from endpoint 1 with groupID 901
                                  zigbee.0	2021-06-12 19:09:54.915	debug	(18506) handleMessage. {"type":"commandOn","device":{"ID":33,"_type":"EndDevice","_ieeeAddr":"0x842e14fffe471ae1","_networkAddress":24375,"_manufacturerID":4476,"_endpoints":[{"ID":1,"profileID":260,"
                                  zigbee.0	2021-06-12 19:09:53.737	debug	(18506) Publish {"action":"arrow_right_click"} to "842e14fffe471ae1"
                                  zigbee.0	2021-06-12 19:09:53.720	debug	(18506) Type commandTradfriArrowSingle device {"type":"device","device":{"ID":33,"_type":"EndDevice","_ieeeAddr":"0x842e14fffe471ae1","_networkAddress":24375,"_manufacturerID":4476,"_endpoints":[{"ID"
                                  zigbee.0	2021-06-12 19:09:53.719	debug	(18506) Received Zigbee message from '0x842e14fffe471ae1', type 'commandTradfriArrowSingle', cluster 'genScenes', data '{"value":256,"value2":13}' from endpoint 1 with groupID 901
                                  zigbee.0	2021-06-12 19:09:53.715	debug	(18506) handleMessage. {"type":"commandTradfriArrowSingle","device":{"ID":33,"_type":"EndDevice","_ieeeAddr":"0x842e14fffe471ae1","_networkAddress":24375,"_manufacturerID":4476,"_endpoints":[{"ID":1,"
                                  zigbee.0	2021-06-12 19:09:52.576	debug	(18506) Publish {"action":"off","action_group":901} to "842e14fffe471ae1"
                                  zigbee.0	2021-06-12 19:09:52.563	debug	(18506) Type commandOff device {"type":"device","device":{"ID":33,"_type":"EndDevice","_ieeeAddr":"0x842e14fffe471ae1","_networkAddress":24375,"_manufacturerID":4476,"_endpoints":[{"ID":1,"profileID":
                                  zigbee.0	2021-06-12 19:09:52.561	debug	(18506) Received Zigbee message from '0x842e14fffe471ae1', type 'commandOff', cluster 'genOnOff', data '{}' from endpoint 1 with groupID 901
                                  zigbee.0	2021-06-12 19:09:52.558	debug	(18506) handleMessage. {"type":"commandOff","device":{"ID":33,"_type":"EndDevice","_ieeeAddr":"0x842e14fffe471ae1","_networkAddress":24375,"_manufacturerID":4476,"_endpoints":[{"ID":1,"profileID":260,
                                  zigbee.0	2021-06-12 19:09:51.208	debug	(18506) Publish {"action":"arrow_left_click"} to "842e14fffe471ae1"
                                  zigbee.0	2021-06-12 19:09:51.199	debug	(18506) Type commandTradfriArrowSingle device {"type":"device","device":{"ID":33,"_type":"EndDevice","_ieeeAddr":"0x842e14fffe471ae1","_networkAddress":24375,"_manufacturerID":4476,"_endpoints":[{"ID"
                                  zigbee.0	2021-06-12 19:09:51.196	debug	(18506) Received Zigbee message from '0x842e14fffe471ae1', type 'commandTradfriArrowSingle', cluster 'genScenes', data '{"value":257,"value2":13}' from endpoint 1 with groupID 901
                                  zigbee.0	2021-06-12 19:09:51.194	debug	(18506) handleMessage. {"type":"commandTradfriArrowSingle","device":{"ID":33,"_type":"EndDevice","_ieeeAddr":"0x842e14fffe471ae1","_networkAddress":24375,"_manufacturerID":4476,"_endpoints":[{"ID":1,"
                                  

                                  Der Timeout für die Erkennung des langen Drucks ist mit ca. 3 s auch sehr lang, kann man das irgendwo verstellen? Das ist zum Beispiel bei E1743 nur ca. 1 s, was viel besser passt.

                                  Dann habe ich noch eine LED1924G9, die funktioniert soweit, außer die Effekte. Da tut sich garnichts.
                                  42d31231-fd93-4974-aea3-7d3791a169ec-grafik.png

                                  Hat da jemand einen Tipp für mich?

                                  L arteckA 2 Antworten Letzte Antwort
                                  0
                                  • R Rushmed

                                    Hallo,

                                    ich komme gerade vom Ikea Einkauf und habe zwei kleine Probleme.
                                    Die Fernbedienung STYRBAR wird vom Adapter als W2094 erkannt. Auf dem Gerät steht aber W2044 und in der Anleitung E2002. Das ist erstmal kein Problem für mich, allerdings funktionieren Druck und langer Druck nur bei den links/rechts Tasten. Die anderen beiden Tasten funktionieren garnicht. f750e091-c6d7-4da2-af97-ba27597956bb-grafik.png
                                    Wenn ich STYRBAR direkt mit einer Lampe kopple geht alles.
                                    Wenn ich den Adapter auf debug stelle kommen Tastendrücke an:

                                    zigbee.0	2021-06-12 19:09:59.315	debug	(18506) Publish {"action":"brightness_stop","action_group":901} to "842e14fffe471ae1"
                                    zigbee.0	2021-06-12 19:09:59.300	debug	(18506) Type commandStopWithOnOff device {"type":"device","device":{"ID":33,"_type":"EndDevice","_ieeeAddr":"0x842e14fffe471ae1","_networkAddress":24375,"_manufacturerID":4476,"_endpoints":[{"ID":1,"p
                                    zigbee.0	2021-06-12 19:09:59.299	debug	(18506) Received Zigbee message from '0x842e14fffe471ae1', type 'commandStopWithOnOff', cluster 'genLevelCtrl', data '{}' from endpoint 1 with groupID 901
                                    zigbee.0	2021-06-12 19:09:59.297	debug	(18506) handleMessage. {"type":"commandStopWithOnOff","device":{"ID":33,"_type":"EndDevice","_ieeeAddr":"0x842e14fffe471ae1","_networkAddress":24375,"_manufacturerID":4476,"_endpoints":[{"ID":1,"profi
                                    zigbee.0	2021-06-12 19:09:58.939	debug	(18506) Publish {"action":"brightness_move_down","action_rate":83,"action_group":901} to "842e14fffe471ae1"
                                    zigbee.0	2021-06-12 19:09:58.926	debug	(18506) Type commandMove device {"type":"device","device":{"ID":33,"_type":"EndDevice","_ieeeAddr":"0x842e14fffe471ae1","_networkAddress":24375,"_manufacturerID":4476,"_endpoints":[{"ID":1,"profileID"
                                    zigbee.0	2021-06-12 19:09:58.926	debug	(18506) Received Zigbee message from '0x842e14fffe471ae1', type 'commandMove', cluster 'genLevelCtrl', data '{"movemode":1,"rate":83}' from endpoint 1 with groupID 901
                                    zigbee.0	2021-06-12 19:09:58.924	debug	(18506) handleMessage. {"type":"commandMove","device":{"ID":33,"_type":"EndDevice","_ieeeAddr":"0x842e14fffe471ae1","_networkAddress":24375,"_manufacturerID":4476,"_endpoints":[{"ID":1,"profileID":260
                                    zigbee.0	2021-06-12 19:09:57.127	debug	(18506) Publish {"action":"brightness_stop","action_group":901} to "842e14fffe471ae1"
                                    zigbee.0	2021-06-12 19:09:57.116	debug	(18506) Type commandStopWithOnOff device {"type":"device","device":{"ID":33,"_type":"EndDevice","_ieeeAddr":"0x842e14fffe471ae1","_networkAddress":24375,"_manufacturerID":4476,"_endpoints":[{"ID":1,"p
                                    zigbee.0	2021-06-12 19:09:57.114	debug	(18506) Received Zigbee message from '0x842e14fffe471ae1', type 'commandStopWithOnOff', cluster 'genLevelCtrl', data '{}' from endpoint 1 with groupID 901
                                    zigbee.0	2021-06-12 19:09:57.113	debug	(18506) handleMessage. {"type":"commandStopWithOnOff","device":{"ID":33,"_type":"EndDevice","_ieeeAddr":"0x842e14fffe471ae1","_networkAddress":24375,"_manufacturerID":4476,"_endpoints":[{"ID":1,"profi
                                    zigbee.0	2021-06-12 19:09:56.660	debug	(18506) Publish {"action":"brightness_move_up","action_rate":83,"action_group":901} to "842e14fffe471ae1"
                                    zigbee.0	2021-06-12 19:09:56.644	debug	(18506) Type commandMoveWithOnOff device {"type":"device","device":{"ID":33,"_type":"EndDevice","_ieeeAddr":"0x842e14fffe471ae1","_networkAddress":24375,"_manufacturerID":4476,"_endpoints":[{"ID":1,"p
                                    zigbee.0	2021-06-12 19:09:56.643	debug	(18506) Received Zigbee message from '0x842e14fffe471ae1', type 'commandMoveWithOnOff', cluster 'genLevelCtrl', data '{"movemode":0,"rate":83}' from endpoint 1 with groupID 901
                                    zigbee.0	2021-06-12 19:09:56.640	debug	(18506) handleMessage. {"type":"commandMoveWithOnOff","device":{"ID":33,"_type":"EndDevice","_ieeeAddr":"0x842e14fffe471ae1","_networkAddress":24375,"_manufacturerID":4476,"_endpoints":[{"ID":1,"profi
                                    zigbee.0	2021-06-12 19:09:54.926	debug	(18506) Publish {"action":"on","action_group":901} to "842e14fffe471ae1"
                                    zigbee.0	2021-06-12 19:09:54.917	debug	(18506) Type commandOn device {"type":"device","device":{"ID":33,"_type":"EndDevice","_ieeeAddr":"0x842e14fffe471ae1","_networkAddress":24375,"_manufacturerID":4476,"_endpoints":[{"ID":1,"profileID":2
                                    zigbee.0	2021-06-12 19:09:54.916	debug	(18506) Received Zigbee message from '0x842e14fffe471ae1', type 'commandOn', cluster 'genOnOff', data '{}' from endpoint 1 with groupID 901
                                    zigbee.0	2021-06-12 19:09:54.915	debug	(18506) handleMessage. {"type":"commandOn","device":{"ID":33,"_type":"EndDevice","_ieeeAddr":"0x842e14fffe471ae1","_networkAddress":24375,"_manufacturerID":4476,"_endpoints":[{"ID":1,"profileID":260,"
                                    zigbee.0	2021-06-12 19:09:53.737	debug	(18506) Publish {"action":"arrow_right_click"} to "842e14fffe471ae1"
                                    zigbee.0	2021-06-12 19:09:53.720	debug	(18506) Type commandTradfriArrowSingle device {"type":"device","device":{"ID":33,"_type":"EndDevice","_ieeeAddr":"0x842e14fffe471ae1","_networkAddress":24375,"_manufacturerID":4476,"_endpoints":[{"ID"
                                    zigbee.0	2021-06-12 19:09:53.719	debug	(18506) Received Zigbee message from '0x842e14fffe471ae1', type 'commandTradfriArrowSingle', cluster 'genScenes', data '{"value":256,"value2":13}' from endpoint 1 with groupID 901
                                    zigbee.0	2021-06-12 19:09:53.715	debug	(18506) handleMessage. {"type":"commandTradfriArrowSingle","device":{"ID":33,"_type":"EndDevice","_ieeeAddr":"0x842e14fffe471ae1","_networkAddress":24375,"_manufacturerID":4476,"_endpoints":[{"ID":1,"
                                    zigbee.0	2021-06-12 19:09:52.576	debug	(18506) Publish {"action":"off","action_group":901} to "842e14fffe471ae1"
                                    zigbee.0	2021-06-12 19:09:52.563	debug	(18506) Type commandOff device {"type":"device","device":{"ID":33,"_type":"EndDevice","_ieeeAddr":"0x842e14fffe471ae1","_networkAddress":24375,"_manufacturerID":4476,"_endpoints":[{"ID":1,"profileID":
                                    zigbee.0	2021-06-12 19:09:52.561	debug	(18506) Received Zigbee message from '0x842e14fffe471ae1', type 'commandOff', cluster 'genOnOff', data '{}' from endpoint 1 with groupID 901
                                    zigbee.0	2021-06-12 19:09:52.558	debug	(18506) handleMessage. {"type":"commandOff","device":{"ID":33,"_type":"EndDevice","_ieeeAddr":"0x842e14fffe471ae1","_networkAddress":24375,"_manufacturerID":4476,"_endpoints":[{"ID":1,"profileID":260,
                                    zigbee.0	2021-06-12 19:09:51.208	debug	(18506) Publish {"action":"arrow_left_click"} to "842e14fffe471ae1"
                                    zigbee.0	2021-06-12 19:09:51.199	debug	(18506) Type commandTradfriArrowSingle device {"type":"device","device":{"ID":33,"_type":"EndDevice","_ieeeAddr":"0x842e14fffe471ae1","_networkAddress":24375,"_manufacturerID":4476,"_endpoints":[{"ID"
                                    zigbee.0	2021-06-12 19:09:51.196	debug	(18506) Received Zigbee message from '0x842e14fffe471ae1', type 'commandTradfriArrowSingle', cluster 'genScenes', data '{"value":257,"value2":13}' from endpoint 1 with groupID 901
                                    zigbee.0	2021-06-12 19:09:51.194	debug	(18506) handleMessage. {"type":"commandTradfriArrowSingle","device":{"ID":33,"_type":"EndDevice","_ieeeAddr":"0x842e14fffe471ae1","_networkAddress":24375,"_manufacturerID":4476,"_endpoints":[{"ID":1,"
                                    

                                    Der Timeout für die Erkennung des langen Drucks ist mit ca. 3 s auch sehr lang, kann man das irgendwo verstellen? Das ist zum Beispiel bei E1743 nur ca. 1 s, was viel besser passt.

                                    Dann habe ich noch eine LED1924G9, die funktioniert soweit, außer die Effekte. Da tut sich garnichts.
                                    42d31231-fd93-4974-aea3-7d3791a169ec-grafik.png

                                    Hat da jemand einen Tipp für mich?

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

                                    @rushmed
                                    hast du probiert das Gerät auszuschliessen?

                                    R 1 Antwort Letzte Antwort
                                    0
                                    • L locito09

                                      @rushmed
                                      hast du probiert das Gerät auszuschliessen?

                                      R Offline
                                      R Offline
                                      Rushmed
                                      Most Active
                                      schrieb am zuletzt editiert von Rushmed
                                      #437

                                      @locito09 Wie ausschließen? Im Adapter? Nein.

                                      Edit: Habs probiert, geht nicht.

                                      1 Antwort Letzte Antwort
                                      0
                                      • G gosund

                                        @arteck @Asgothian

                                        FYI: Hatte gestern Abend auf die 1.5.5 herunter gegraded. Das Problem besteht immer noch: nach ziemlich genau 24 Stunden hängt sich der Adapter auf. Ich mußte den Pi gerade eben wieder booten.

                                        Irgend eine Idee, was ich noch machen kann?

                                        Und nochwas: Seit dem Downgrade bekomme ich ständig folgende Meldung im Log:

                                        zigbee.0 (1671) Failed to DeviceConfigure.onZigbeeEvent (Error: 'LED1623G12' has no configure
                                            at Object.getConfigureKey (/opt/iobroker/node_modules/zigbee-herdsman-converters/lib/configureKey.js:20:15)
                                            at DeviceConfigure.shouldConfigure (/opt/iobroker/node_modules/iobroker.zigbee/lib/zbDeviceConfigure.js:33:38)
                                            at DeviceConfigure.onZigbeeEvent (/opt/iobroker/node_modules/iobroker.zigbee/lib/zbDeviceConfigure.js:76:22)
                                            at ZigbeeController.callExtensionMethod (/opt/iobroker/node_modules/iobroker.zigbee/lib/zigbeecontroller.js:196:42)
                                            at ZigbeeController.handleMessage (/opt/iobroker/node_modules/iobroker.zigbee/lib/zigbeecontroller.js:560:14))
                                        

                                        Woher kommt LED1623G12? Ich habe alle Devices umbenannt, kann also nicht sagen, welches er meint. Irgend eine Idee?

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

                                        @gosund da sist der Technische name .. nicht dein umbenanntess.das kannst du in der Kachel sehen ..wenn du die umdrehst

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

                                        F 1 Antwort Letzte Antwort
                                        0
                                        • arteckA arteck

                                          @gosund da sist der Technische name .. nicht dein umbenanntess.das kannst du in der Kachel sehen ..wenn du die umdrehst

                                          F Offline
                                          F Offline
                                          Frank579
                                          schrieb am zuletzt editiert von
                                          #439

                                          @Asgothian
                                          Habe gerade mein bastelsystem hochgezogen auf Admin5.
                                          Er spuckt mir jetzt für einige Geräte

                                          zigbee.0
                                          2021-06-13 09:52:06.290	warn	State value to set for "zigbee.0.0017880108279caf.link_quality" has value "255" greater than max "254"
                                          

                                          ins Log.
                                          Ist das schon bekannt?

                                          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

                                          295

                                          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
                                          • Home
                                          • Aktuell
                                          • Tags
                                          • Ungelesen 0
                                          • Kategorien
                                          • Unreplied
                                          • Beliebt
                                          • GitHub
                                          • Docu
                                          • Hilfe