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

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

Community Forum

donate donate
  1. ioBroker Community Home
  2. Deutsch
  3. ioBroker Allgemein
  4. ZigBee-Adapter - nach dem 7ten Device tot…

NEWS

  • Monatsrückblick Januar/Februar 2026 ist online!
    BluefoxB
    Bluefox
    17
    1
    488

  • Jahresrückblick 2025 – unser neuer Blogbeitrag ist online! ✨
    BluefoxB
    Bluefox
    17
    1
    5.2k

  • Neuer Blogbeitrag: Monatsrückblick - Dezember 2025 🎄
    BluefoxB
    Bluefox
    13
    1
    1.4k

ZigBee-Adapter - nach dem 7ten Device tot…

Geplant Angeheftet Gesperrt Verschoben ioBroker Allgemein
9 Beiträge 2 Kommentatoren 915 Aufrufe
  • Ä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.
  • C Offline
    C Offline
    cyrano330
    schrieb am zuletzt editiert von
    #1

    Hallo zusammen,

    gestern hat sich mein ZigBee-Adapter verabschiedet. Selbst ein ein und ausstecken des Stick und Neuinstallation des Adapters an sich haben nichts gebracht. Ohne das ich an der Installation was verändert habe mecker er jetzt irgendwelche Funktionen an die er wohl nicht mehr aufrufen kann. Ein Logfileauszug einmal hier:

    ! host.iobroker 2019-01-10 16:14:18.382 error instance system.adapter.zigbee.0 terminated with code 0 (OK)
    ! host.iobroker 2019-01-10 16:14:18.382 error Caught by controller[7]: 2019-01-10T15:14:18.306Z zigbee:controller info zigbee-shepherd stopped undefined
    ! host.iobroker 2019-01-10 16:14:18.382 error Caught by controller[7]: 2019-01-10T15:14:18.305Z zigbee-shepherd zigbee-shepherd is stopped.
    ! host.iobroker 2019-01-10 16:14:18.382 error Caught by controller[7]: 2019-01-10T15:14:18.305Z zigbee-shepherd zigbee-shepherd is stopping.
    ! host.iobroker 2019-01-10 16:14:18.382 error Caught by controller[7]: at process._tickCallback (internal/process/next_tick.js:181:9)
    ! host.iobroker 2019-01-10 16:14:18.382 error Caught by controller[7]: at _combinedTickCallback (internal/process/next_tick.js:132:7)
    ! host.iobroker 2019-01-10 16:14:18.382 error Caught by controller[7]: at flush (/opt/iobroker/node_modules/q/q.js:125:13)
    ! host.iobroker 2019-01-10 16:14:18.382 error Caught by controller[7]: at runSingle (/opt/iobroker/node_modules/q/q.js:137:13)
    ! host.iobroker 2019-01-10 16:14:18.382 error Caught by controller[7]: at /opt/iobroker/node_modules/q/q.js:2059:17
    ! host.iobroker 2019-01-10 16:14:18.382 error Caught by controller[7]: at shepherd.start (/opt/iobroker/node_modules/iobroker.zigbee/lib/zigbeecontroller.js:78:47)
    ! host.iobroker 2019-01-10 16:14:18.382 error Caught by controller[7]: TypeError: Cannot read property 'close' of undefined
    ! host.iobroker 2019-01-10 16:14:18.382 error Caught by controller[7]: 2019-01-10T15:14:18.303Z zigbee:controller debug Error while starting zigbee-shepherd, attemping to fix… (takes 60 seconds) undefined
    ! host.iobroker 2019-01-10 16:14:18.382 error Caught by controller[6]: at Timer.listOnTimeout (timers.js:290:5)
    ! host.iobroker 2019-01-10 16:14:18.382 error Caught by controller[6]: at tryOnTimeout (timers.js:323:5)
    ! host.iobroker 2019-01-10 16:14:18.382 error Caught by controller[6]: at ontimeout (timers.js:498:11)
    ! host.iobroker 2019-01-10 16:14:18.382 error Caught by controller[6]: at Timeout. <anonymous>(/opt/iobroker/node_modules/cc-znp/lib/ccznp.js:233:18)
    ! host.iobroker 2019-01-10 16:14:18.382 error Caught by controller[6]: at CcZnp.emit (events.js:211:7)
    ! host.iobroker 2019-01-10 16:14:18.382 error Caught by controller[6]: at emitOne (events.js:116:13)
    ! host.iobroker 2019-01-10 16:14:18.382 error Caught by controller[6]: at Object.onceWrapper (events.js:315:30)
    ! host.iobroker 2019-01-10 16:14:18.382 error Caught by controller[6]: at CcZnp. <anonymous>(/opt/iobroker/node_modules/cc-znp/lib/ccznp.js:254:22)
    ! host.iobroker 2019-01-10 16:14:18.382 error Caught by controller[6]: 2019-01-10T15:14:18.302Z zigbee-shepherd:init Coordinator initialize had an error: Error: request timeout
    ! host.iobroker 2019-01-10 16:14:18.382 error Caught by controller[5]: 2019-01-10T15:14:18.301Z zigbee-shepherd:request RSP <– SYS:osalNvRead
    ! host.iobroker 2019-01-10 16:14:18.382 error Caught by controller[4]: Thu, 10 Jan 2019 15:14:18 GMT cc-znp:SRSP <– SYS:osalNvRead, timeout
    ! host.iobroker 2019-01-10 16:14:18.382 error Caught by controller[3]: Thu, 10 Jan 2019 15:14:15 GMT cc-znp:SREQ –> SYS:osalNvRead, { id: 3840, offset: 0, len: 1, value: [ 85 ] }
    ! host.iobroker 2019-01-10 16:14:18.381 error Caught by controller[2]: 2019-01-10T15:14:15.293Z zigbee-shepherd:request REQ –> SYS:osalNvRead
    ! host.iobroker 2019-01-10 16:14:18.381 error Caught by controller[1]: Thu, 10 Jan 2019 15:14:15 GMT cc-znp The serialport /dev/ttyACM0 is opened.
    ! host.iobroker 2019-01-10 16:14:18.381 error Caught by controller[0]: 2019-01-10T15:14:13.657Z zigbee-shepherd:init zigbee-shepherd booting…
    ! zigbee.0 2019-01-10 16:14:18.307 info zigbee-shepherd stopped
    ! zigbee.0 2019-01-10 16:14:18.307 error TypeError: Cannot read property 'close' of undefined at shepherd.start (/opt/iobroker/node_modules/iobroker.zigbee/lib/zigbeecontroller.js:78:47) at /opt/iobroker/node_modules/q/q.js:2059:17
    ! zigbee.0 2019-01-10 16:14:18.306 error uncaught exception: Cannot read property 'close' of undefined</anonymous></anonymous>

    Hat jemand eine Idee was hier der Grund sein kann? Das Verhalten trat plötzlich auf - auf einmal reagierte kein Device mehr…

    Danke & Gruß

    Henry

    1 Antwort Letzte Antwort
    0
    • arteckA Offline
      arteckA Offline
      arteck
      Developer Most Active
      schrieb am zuletzt editiert von
      #2

      welches Repo hast du installiert..das offizielle ?? da scheint im converter was nicht zu stimmen

      ausserdem es passiert nicht eifach so.. von allein..

      ewtl. geht die SD Karte kaputt..oder du hast rumgespielt

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

      1 Antwort Letzte Antwort
      0
      • C Offline
        C Offline
        cyrano330
        schrieb am zuletzt editiert von
        #3

        Hallo Arteck,

        Mein ioBroker läuft als VM auf einem INTEl-NUC. Habe nach Deinem EInwand "oder Du hast dran rumgespielt" nochmal neu gestartet. Das meint ich habe die folgenden Schritte durchgeführt:

        1. habe ich den Stick entfernt.

        2. habe ich den ZIgBee-Adapter über das Webfrontend deinstalliert.

        3. habe ich die VM dann via SSH neu gestartet.

        4. habe ich den ZigBee-Adapter wieder installiert (keinerlei Fehlermeldungen).

        5. habe ich den Stick wieder eingesteckt und im Adapter den Anschluss konfiguriert.

        6. habe ich alle Geräte aus meine ioBroker.Zigbee-Instanz entfernt und 5 Tradfri GU10-Lampen und den XIAOMI-Würfel neu angelernt.

        Das ganze hat fast fehlerfrei funktioniert. Ich konnte alles steuern so wie ich es erwartet habe. Und wirklich ohne dran rumzufummeln oder was zu basteln etc. habe ich jetzt wieder das Verhalten. Der Adapter bleibt stehen und wird versucht neu zu starten:

        ! host.iobroker 2019-01-12 18:52:39.965 info Restart adapter system.adapter.zigbee.0 because enabled
        ! host.iobroker 2019-01-12 18:52:39.965 error instance system.adapter.zigbee.0 terminated with code 0 (OK)
        ! host.iobroker 2019-01-12 18:52:39.965 error Caught by controller[4]: 2019-01-12T17:52:39.958Z zigbee:controller info zigbee-shepherd stopped undefined
        ! host.iobroker 2019-01-12 18:52:39.965 error Caught by controller[3]: 2019-01-12T17:52:39.958Z zigbee-shepherd zigbee-shepherd is stopped.
        ! host.iobroker 2019-01-12 18:52:39.965 error Caught by controller[3]: 2019-01-12T17:52:39.957Z zigbee-shepherd zigbee-shepherd is stopping.
        ! host.iobroker 2019-01-12 18:52:39.965 error Caught by controller[2]: at process._tickCallback (internal/process/next_tick.js:181:9)
        ! host.iobroker 2019-01-12 18:52:39.965 error Caught by controller[2]: at _combinedTickCallback (internal/process/next_tick.js:132:7)
        ! host.iobroker 2019-01-12 18:52:39.965 error Caught by controller[2]: at flush (/opt/iobroker/node_modules/q/q.js:125:13)
        ! host.iobroker 2019-01-12 18:52:39.965 error Caught by controller[2]: at runSingle (/opt/iobroker/node_modules/q/q.js:137:13)
        ! host.iobroker 2019-01-12 18:52:39.965 error Caught by controller[2]: at /opt/iobroker/node_modules/q/q.js:2059:17
        ! host.iobroker 2019-01-12 18:52:39.965 error Caught by controller[2]: at shepherd.start (/opt/iobroker/node_modules/iobroker.zigbee/lib/zigbeecontroller.js:78:47)
        ! host.iobroker 2019-01-12 18:52:39.965 error Caught by controller[2]: TypeError: Cannot read property 'close' of undefined
        ! host.iobroker 2019-01-12 18:52:39.965 error Caught by controller[1]: 2019-01-12T17:52:39.955Z zigbee:controller debug Error while starting zigbee-shepherd, attemping to fix… (takes 60 seconds) undefined
        ! host.iobroker 2019-01-12 18:52:39.965 error Caught by controller[0]: 2019-01-12T17:52:39.945Z zigbee-shepherd:init zigbee-shepherd booting…
        ! host.iobroker 2019-01-12 18:52:39.532 info instance system.adapter.zigbee.0 started with pid 995
        ! host.iobroker 2019-01-12 18:52:09.528 info Restart adapter system.adapter.zigbee.0 because enabled
        ! host.iobroker 2019-01-12 18:52:09.528 error instance system.adapter.zigbee.0 terminated with code 0 (OK)
        ! host.iobroker 2019-01-12 18:52:09.528 error Caught by controller[4]: 2019-01-12T17:52:09.520Z zigbee:controller info zigbee-shepherd stopped undefined
        ! host.iobroker 2019-01-12 18:52:09.528 error Caught by controller[3]: 2019-01-12T17:52:09.520Z zigbee-shepherd zigbee-shepherd is stopped.
        ! host.iobroker 2019-01-12 18:52:09.528 error Caught by controller[3]: 2019-01-12T17:52:09.519Z zigbee-shepherd zigbee-shepherd is stopping.
        ! host.iobroker 2019-01-12 18:52:09.528 error Caught by controller[2]: at process._tickCallback (internal/process/next_tick.js:181:9)
        ! host.iobroker 2019-01-12 18:52:09.528 error Caught by controller[2]: at _combinedTickCallback (internal/process/next_tick.js:132:7)
        ! host.iobroker 2019-01-12 18:52:09.528 error Caught by controller[2]: at flush (/opt/iobroker/node_modules/q/q.js:125:13)
        ! host.iobroker 2019-01-12 18:52:09.528 error Caught by controller[2]: at runSingle (/opt/iobroker/node_modules/q/q.js:137:13)
        ! host.iobroker 2019-01-12 18:52:09.528 error Caught by controller[2]: at /opt/iobroker/node_modules/q/q.js:2059:17
        ! host.iobroker 2019-01-12 18:52:09.528 error Caught by controller[2]: at shepherd.start (/opt/iobroker/node_modules/iobroker.zigbee/lib/zigbeecontroller.js:78:47)
        ! host.iobroker 2019-01-12 18:52:09.528 error Caught by controller[2]: TypeError: Cannot read property 'close' of undefined
        ! host.iobroker 2019-01-12 18:52:09.528 error Caught by controller[1]: 2019-01-12T17:52:09.517Z zigbee:controller debug Error while starting zigbee-shepherd, attemping to fix… (takes 60 seconds) undefined
        ! host.iobroker 2019-01-12 18:52:09.528 error Caught by controller[0]: 2019-01-12T17:52:09.507Z zigbee-shepherd:init zigbee-shepherd booting…
        ! zigbee.0 2019-01-12 18:52:09.522 info starting. Version 0.8.0 in /opt/iobroker/node_modules/iobroker.zigbee, node: v8.15.0
        ! host.iobroker 2019-01-12 18:52:09.092 info instance system.adapter.zigbee.0 started with pid 985
        ! host.iobroker 2019-01-12 18:51:39.090 info Restart adapter system.adapter.zigbee.0 because enabled
        ! host.iobroker 2019-01-12 18:51:39.090 error instance system.adapter.zigbee.0 terminated with code 0 (OK)
        ! host.iobroker 2019-01-12 18:51:39.090 error Caught by controller[1]: 2019-01-12T17:51:39.073Z zigbee:controller info zigbee-shepherd stopped undefined
        ! host.iobroker 2019-01-12 18:51:39.090 error Caught by controller[1]: 2019-01-12T17:51:39.073Z zigbee-shepherd zigbee-shepherd is stopped.
        ! host.iobroker 2019-01-12 18:51:39.090 error Caught by controller[1]: 2019-01-12T17:51:39.071Z zigbee-shepherd zigbee-shepherd is stopping.
        ! host.iobroker 2019-01-12 18:51:39.089 error Caught by controller[1]: at process._tickCallback (internal/process/next_tick.js:181:9)
        ! host.iobroker 2019-01-12 18:51:39.089 error Caught by controller[1]: at _combinedTickCallback (internal/process/next_tick.js:132:7)
        ! host.iobroker 2019-01-12 18:51:39.089 error Caught by controller[1]: at flush (/opt/iobroker/node_modules/q/q.js:125:13)
        ! host.iobroker 2019-01-12 18:51:39.089 error Caught by controller[1]: at runSingle (/opt/iobroker/node_modules/q/q.js:137:13)
        ! host.iobroker 2019-01-12 18:51:39.089 error Caught by controller[1]: at /opt/iobroker/node_modules/q/q.js:2059:17
        ! host.iobroker 2019-01-12 18:51:39.089 error Caught by controller[1]: at shepherd.start (/opt/iobroker/node_modules/iobroker.zigbee/lib/zigbeecontroller.js:78:47)
        ! host.iobroker 2019-01-12 18:51:39.089 error Caught by controller[1]: TypeError: Cannot read property 'close' of undefined
        ! host.iobroker 2019-01-12 18:51:39.089 error Caught by controller[1]: 2019-01-12T17:51:39.069Z zigbee:controller debug Error while starting zigbee-shepherd, attemping to fix… (takes 60 seconds) undefined
        ! host.iobroker 2019-01-12 18:51:39.089 error Caught by controller[0]: 2019-01-12T17:51:39.060Z zigbee-shepherd:init zigbee-shepherd booting…
        ! zigbee.0 2019-01-12 18:51:39.074 info starting. Version 0.8.0 in /opt/iobroker/node_modules/iobroker.zigbee, node: v8.15.0
        ! host.iobroker 2019-01-12 18:51:38.645 info instance system.adapter.zigbee.0 started with pid 975
        ! host.iobroker 2019-01-12 18:51:08.640 info Restart adapter system.adapter.zigbee.0 because enabled
        ! host.iobroker 2019-01-12 18:51:08.640 error instance system.adapter.zigbee.0 terminated with code 0 (OK)
        ! host.iobroker 2019-01-12 18:51:08.640 error Caught by controller[3]: 2019-01-12T17:51:08.632Z zigbee:controller info zigbee-shepherd stopped undefined
        ! host.iobroker 2019-01-12 18:51:08.640 error Caught by controller[3]: 2019-01-12T17:51:08.632Z zigbee-shepherd zigbee-shepherd is stopped.
        ! host.iobroker 2019-01-12 18:51:08.640 error Caught by controller[3]: 2019-01-12T17:51:08.631Z zigbee-shepherd zigbee-shepherd is stopping.
        ! host.iobroker 2019-01-12 18:51:08.640 error Caught by controller[2]: at process._tickCallback (internal/process/next_tick.js:181:9)
        ! host.iobroker 2019-01-12 18:51:08.640 error Caught by controller[2]: at _combinedTickCallback (internal/process/next_tick.js:132:7)
        ! host.iobroker 2019-01-12 18:51:08.640 error Caught by controller[2]: at flush (/opt/iobroker/node_modules/q/q.js:125:13)
        ! host.iobroker 2019-01-12 18:51:08.640 error Caught by controller[2]: at runSingle (/opt/iobroker/node_modules/q/q.js:137:13)
        ! host.iobroker 2019-01-12 18:51:08.640 error Caught by controller[2]: at /opt/iobroker/node_modules/q/q.js:2059:17
        ! host.iobroker 2019-01-12 18:51:08.640 error Caught by controller[2]: at shepherd.start (/opt/iobroker/node_modules/iobroker.zigbee/lib/zigbeecontroller.js:78:47)
        ! host.iobroker 2019-01-12 18:51:08.640 error Caught by controller[2]: TypeError: Cannot read property 'close' of undefined
        ! host.iobroker 2019-01-12 18:51:08.640 error Caught by controller[1]: 2019-01-12T17:51:08.629Z zigbee:controller debug Error while starting zigbee-shepherd, attemping to fix… (takes 60 seconds) undefined
        ! host.iobroker 2019-01-12 18:51:08.640 error Caught by controller[0]: 2019-01-12T17:51:08.618Z zigbee-shepherd:init zigbee-shepherd booting…
        ! zigbee.0 2019-01-12 18:51:08.634 info starting. Version 0.8.0 in /opt/iobroker/node_modules/iobroker.zigbee, node: v8.15.0
        ! host.iobroker 2019-01-12 18:51:08.212 info instance system.adapter.zigbee.0 started with pid 965
        ! host.iobroker 2019-01-12 18:51:08.211 info object change system.adapter.zigbee.0
        ! host.iobroker 2019-01-12 18:51:04.990 info object change system.adapter.zigbee.0
        ! host.iobroker 2019-01-12 18:51:00.118 info Restart adapter system.adapter.zigbee.0 because enabled

        Ach so Neustart der VM oder des Adapters bringt gar keine Veränderung.

        Bin wirklich etwas ratlos. Es hat ja funktioniert. Ich habe wirklich nichts verändert. Nur eben den Wert für die Helligkeit und Farbtemperatur verändert. Das hat mehrfach güt funktioniert. Firmware auf dem Stick ist die vom 24.12.2018…

        Bitte um Hilfe!

        Danke & Gruß!

        1 Antwort Letzte Antwort
        0
        • arteckA Offline
          arteckA Offline
          arteck
          Developer Most Active
          schrieb am zuletzt editiert von
          #4

          ok also nochmal die Frage

          installiere mal das hier

          https://github.com/arteck/ioBroker.zigbee

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

          1 Antwort Letzte Antwort
          0
          • C Offline
            C Offline
            cyrano330
            schrieb am zuletzt editiert von
            #5

            Hi Arteck,

            hab ich eben über die Oberfläche aus dem GIT installiert. Nun hab das hier im Log stehen…

            ! obroker 2019-01-13 10:44:41.888 info instance system.adapter.zigbee.0 started with pid 1790
            ! host.iobroker 2019-01-13 10:44:11.884 info Restart adapter system.adapter.zigbee.0 because enabled
            ! host.iobroker 2019-01-13 10:44:11.884 error instance system.adapter.zigbee.0 terminated with code 0 (OK)
            ! host.iobroker 2019-01-13 10:44:11.884 error Caught by controller[4]: 2019-01-13T09:44:11.876Z zigbee:controller info zigbee-shepherd stopped undefined
            ! host.iobroker 2019-01-13 10:44:11.884 error Caught by controller[3]: 2019-01-13T09:44:11.876Z zigbee-shepherd zigbee-shepherd is stopped.
            ! host.iobroker 2019-01-13 10:44:11.884 error Caught by controller[3]: 2019-01-13T09:44:11.875Z zigbee-shepherd zigbee-shepherd is stopping.
            ! host.iobroker 2019-01-13 10:44:11.884 error Caught by controller[2]: at process._tickCallback (internal/process/next_tick.js:181:9)
            ! host.iobroker 2019-01-13 10:44:11.884 error Caught by controller[2]: at _combinedTickCallback (internal/process/next_tick.js:132:7)
            ! host.iobroker 2019-01-13 10:44:11.884 error Caught by controller[2]: at flush (/opt/iobroker/node_modules/q/q.js:125:13)
            ! host.iobroker 2019-01-13 10:44:11.884 error Caught by controller[2]: at runSingle (/opt/iobroker/node_modules/q/q.js:137:13)
            ! host.iobroker 2019-01-13 10:44:11.884 error Caught by controller[2]: at /opt/iobroker/node_modules/q/q.js:2059:17
            ! host.iobroker 2019-01-13 10:44:11.884 error Caught by controller[2]: at shepherd.start (/opt/iobroker/node_modules/iobroker.zigbee/lib/zigbeecontroller.js:78:47)
            ! host.iobroker 2019-01-13 10:44:11.884 error Caught by controller[2]: TypeError: Cannot read property 'close' of undefined
            ! host.iobroker 2019-01-13 10:44:11.884 error Caught by controller[1]: 2019-01-13T09:44:11.873Z zigbee:controller debug Error while starting zigbee-shepherd, attemping to fix… (takes 60 seconds) undefined
            ! host.iobroker 2019-01-13 10:44:11.883 error Caught by controller[0]: 2019-01-13T09:44:11.864Z zigbee-shepherd:init zigbee-shepherd booting…
            ! zigbee.0 2019-01-13 10:44:11.878 info starting. Version 0.8.2-a in /opt/iobroker/node_modules/iobroker.zigbee, node: v8.15.0
            ! host.iobroker 2019-01-13 10:44:11.447 info instance system.adapter.zigbee.0 started with pid 1779
            ! host.iobroker 2019-01-13 10:43:41.443 info Restart adapter system.adapter.zigbee.0 because enabled
            ! host.iobroker 2019-01-13 10:43:41.443 error instance system.adapter.zigbee.0 terminated with code 0 (OK)
            ! host.iobroker 2019-01-13 10:43:41.443 error Caught by controller[4]: 2019-01-13T09:43:41.435Z zigbee:controller info zigbee-shepherd stopped undefined
            ! host.iobroker 2019-01-13 10:43:41.443 error Caught by controller[3]: 2019-01-13T09:43:41.435Z zigbee-shepherd zigbee-shepherd is stopped.
            ! host.iobroker 2019-01-13 10:43:41.443 error Caught by controller[3]: 2019-01-13T09:43:41.434Z zigbee-shepherd zigbee-shepherd is stopping.
            ! host.iobroker 2019-01-13 10:43:41.442 error Caught by controller[2]: at process._tickCallback (internal/process/next_tick.js:181:9)
            ! host.iobroker 2019-01-13 10:43:41.442 error Caught by controller[2]: at _combinedTickCallback (internal/process/next_tick.js:132:7)
            ! host.iobroker 2019-01-13 10:43:41.442 error Caught by controller[2]: at flush (/opt/iobroker/node_modules/q/q.js:125:13)
            ! host.iobroker 2019-01-13 10:43:41.442 error Caught by controller[2]: at runSingle (/opt/iobroker/node_modules/q/q.js:137:13)
            ! host.iobroker 2019-01-13 10:43:41.442 error Caught by controller[2]: at /opt/iobroker/node_modules/q/q.js:2059:17
            ! host.iobroker 2019-01-13 10:43:41.442 error Caught by controller[2]: at shepherd.start (/opt/iobroker/node_modules/iobroker.zigbee/lib/zigbeecontroller.js:78:47)
            ! host.iobroker 2019-01-13 10:43:41.442 error Caught by controller[2]: TypeError: Cannot read property 'close' of undefined
            ! host.iobroker 2019-01-13 10:43:41.442 error Caught by controller[1]: 2019-01-13T09:43:41.432Z zigbee:controller debug Error while starting zigbee-shepherd, attemping to fix… (takes 60 seconds) undefined
            ! host.iobroker 2019-01-13 10:43:41.442 error Caught by controller[0]: 2019-01-13T09:43:41.423Z zigbee-shepherd:init zigbee-shepherd booting…
            ! zigbee.0 2019-01-13 10:43:41.437 info Start on port: /dev/ttyACM0 with panID 6754 channel 11
            ! zigbee.0 2019-01-13 10:43:41.437 info starting. Version 0.8.2-a in /opt/iobroker/node_modules/iobroker.zigbee, node: v8.15.0
            ! host.iobroker 2019-01-13 10:43:41.012 info instance system.adapter.zigbee.0 started with pid 1769
            ! host.iobroker 2019-01-13 10:43:11.007 info Restart adapter system.adapter.zigbee.0 because enabled

            Sollte ich den Stick nochmal flashen? Nicht das der da irgendwas mit zu tun hat. Hat ja schließlich funktionert bis zur 5ten Tradfri-Bulb….

            Danke & Gruß

            Henry

            1 Antwort Letzte Antwort
            0
            • C Offline
              C Offline
              cyrano330
              schrieb am zuletzt editiert von
              #6

              Hi Arteck,

              jetzt hab ich das gesamte Verhalten mal als Logfile. Ich habe den Adapter beendet und den Stick gezogen und neu gesteckt. Danach habe ich den wieder Adapter gestartet. Der Cube, die eine HUE und die 5 Tradfris wurde sauber erkannt. Ich konnte mir die MAP ansehen - alles so wie es soll. Dann habe ich per INJECT aus dem Node-Red in die Brightness der 5 Objekte der TRADFRIs den Wert verändert. Hat sauber funktioniert Alle Lampen sind auf 25% gegangen. Als ich über den gleichen weg wieder auf 100 gehen wollte ging das Theater los. Timeouts und dann startet der Adapter im Kreis. Die Map kann ich auch nicht mehr angucken.

              Ich habe - ob meines gefährlichen Halbwissens - die Vermutung, das das mit den TRADFRIs zusammenhängt. Wenn mich meine Frau lässt mache ich gleich mal einen Kreuztest und lerne nur die HUEs und XIAOMIs an und gucke ob ich den Fehler dann auch reproduzieren kann.

              ! host.iobroker 2019-01-13 13:33:44.170 info Restart adapter system.adapter.zigbee.0 because enabled
              ! host.iobroker 2019-01-13 13:33:44.170 error instance system.adapter.zigbee.0 terminated with code 0 (OK)
              ! host.iobroker 2019-01-13 13:33:44.170 error Caught by controller[7]: 2019-01-13T12:33:21.101Z zigbee:controller info zigbee-shepherd stopped undefined
              ! host.iobroker 2019-01-13 13:33:44.170 error Caught by controller[7]: 2019-01-13T12:33:21.101Z zigbee-shepherd zigbee-shepherd is stopped.
              ! host.iobroker 2019-01-13 13:33:44.170 error Caught by controller[7]: 2019-01-13T12:33:21.101Z zigbee-shepherd zigbee-shepherd is stopping.
              ! host.iobroker 2019-01-13 13:33:44.170 error Caught by controller[7]: at process._tickCallback (internal/process/next_tick.js:181:9)
              ! host.iobroker 2019-01-13 13:33:44.170 error Caught by controller[7]: at _combinedTickCallback (internal/process/next_tick.js:132:7)
              ! host.iobroker 2019-01-13 13:33:44.170 error Caught by controller[7]: at flush (/opt/iobroker/node_modules/q/q.js:125:13)
              ! host.iobroker 2019-01-13 13:33:44.170 error Caught by controller[7]: at runSingle (/opt/iobroker/node_modules/q/q.js:137:13)
              ! host.iobroker 2019-01-13 13:33:44.170 error Caught by controller[7]: at /opt/iobroker/node_modules/q/q.js:2059:17
              ! host.iobroker 2019-01-13 13:33:44.170 error Caught by controller[7]: at shepherd.start (/opt/iobroker/node_modules/iobroker.zigbee/lib/zigbeecontroller.js:78:47)
              ! host.iobroker 2019-01-13 13:33:44.170 error Caught by controller[7]: TypeError: Cannot read property 'close' of undefined
              ! host.iobroker 2019-01-13 13:33:44.170 error Caught by controller[7]: 2019-01-13T12:33:21.099Z zigbee:controller debug Error while starting zigbee-shepherd, attemping to fix… (takes 60 seconds) undefined
              ! host.iobroker 2019-01-13 13:33:44.170 error Caught by controller[6]: at Timer.listOnTimeout (timers.js:290:5)
              ! host.iobroker 2019-01-13 13:33:44.170 error Caught by controller[6]: at tryOnTimeout (timers.js:323:5)
              ! host.iobroker 2019-01-13 13:33:44.170 error Caught by controller[6]: at ontimeout (timers.js:498:11)
              ! host.iobroker 2019-01-13 13:33:44.170 error Caught by controller[6]: at Timeout. <anonymous>(/opt/iobroker/node_modules/cc-znp/lib/ccznp.js:233:18)
              ! host.iobroker 2019-01-13 13:33:44.170 error Caught by controller[6]: at CcZnp.emit (events.js:211:7)
              ! host.iobroker 2019-01-13 13:33:44.170 error Caught by controller[6]: at emitOne (events.js:116:13)
              ! host.iobroker 2019-01-13 13:33:44.170 error Caught by controller[6]: at Object.onceWrapper (events.js:315:30)
              ! host.iobroker 2019-01-13 13:33:44.170 error Caught by controller[6]: at CcZnp. <anonymous>(/opt/iobroker/node_modules/cc-znp/lib/ccznp.js:254:22)
              ! host.iobroker 2019-01-13 13:33:44.170 error Caught by controller[6]: 2019-01-13T12:33:21.098Z zigbee-shepherd:init Coordinator initialize had an error: Error: request timeout
              ! host.iobroker 2019-01-13 13:33:44.170 error Caught by controller[5]: 2019-01-13T12:33:21.096Z zigbee-shepherd:request RSP <– SYS:osalNvRead
              ! host.iobroker 2019-01-13 13:33:44.170 error Caught by controller[4]: Sun, 13 Jan 2019 12:33:21 GMT cc-znp:SRSP <– SYS:osalNvRead, timeout
              ! host.iobroker 2019-01-13 13:33:44.170 error Caught by controller[3]: Sun, 13 Jan 2019 12:33:18 GMT cc-znp:SREQ –> SYS:osalNvRead, { id: 3840, offset: 0, len: 1, value: [ 85 ] }
              ! host.iobroker 2019-01-13 13:33:44.170 error Caught by controller[2]: 2019-01-13T12:33:18.088Z zigbee-shepherd:request REQ –> SYS:osalNvRead
              ! host.iobroker 2019-01-13 13:33:44.170 error Caught by controller[1]: Sun, 13 Jan 2019 12:33:18 GMT cc-znp The serialport /dev/ttyACM0 is opened.
              ! zigbee.0 2019-01-13 13:33:21.102 error uncaught exception: Cannot read property 'close' of undefined
              ! zigbee.0 2019-01-13 13:33:12.470 info Start on port: /dev/ttyACM0 with panID 6754 channel 11
              ! zigbee.0 2019-01-13 13:33:12.469 info starting. Version 0.8.2-a in /opt/iobroker/node_modules/iobroker.zigbee, node: v8.15.0
              ! host.iobroker 2019-01-13 13:33:12.039 info instance system.adapter.zigbee.0 started with pid 913
              ! host.iobroker 2019-01-13 13:32:42.037 info Restart adapter system.adapter.zigbee.0 because enabled
              ! host.iobroker 2019-01-13 13:32:42.037 error instance system.adapter.zigbee.0 terminated with code 0 (OK)
              ! host.iobroker 2019-01-13 13:32:42.037 error Caught by controller[6]: 2019-01-13T12:32:18.977Z zigbee:controller info zigbee-shepherd stopped undefined
              ! host.iobroker 2019-01-13 13:32:42.037 error Caught by controller[6]: 2019-01-13T12:32:18.977Z zigbee-shepherd zigbee-shepherd is stopped.
              ! host.iobroker 2019-01-13 13:32:42.037 error Caught by controller[6]: 2019-01-13T12:32:18.977Z zigbee-shepherd zigbee-shepherd is stopping.
              ! host.iobroker 2019-01-13 13:32:42.037 error Caught by controller[6]: at process._tickCallback (internal/process/next_tick.js:181:9)
              ! host.iobroker 2019-01-13 13:32:42.037 error Caught by controller[6]: at _combinedTickCallback (internal/process/next_tick.js:132:7)
              ! host.iobroker 2019-01-13 13:32:42.037 error Caught by controller[6]: at flush (/opt/iobroker/node_modules/q/q.js:125:13)
              ! host.iobroker 2019-01-13 13:32:42.037 error Caught by controller[6]: at runSingle (/opt/iobroker/node_modules/q/q.js:137:13)
              ! host.iobroker 2019-01-13 13:32:42.037 error Caught by controller[6]: at /opt/iobroker/node_modules/q/q.js:2059:17
              ! host.iobroker 2019-01-13 13:32:42.037 error Caught by controller[6]: at shepherd.start (/opt/iobroker/node_modules/iobroker.zigbee/lib/zigbeecontroller.js:78:47)
              ! host.iobroker 2019-01-13 13:32:42.037 error Caught by controller[6]: TypeError: Cannot read property 'close' of undefined
              ! host.iobroker 2019-01-13 13:32:42.037 error Caught by controller[6]: 2019-01-13T12:32:18.975Z zigbee:controller debug Error while starting zigbee-shepherd, attemping to fix… (takes 60 seconds) undefined
              ! host.iobroker 2019-01-13 13:32:42.037 error Caught by controller[5]: at Timer.listOnTimeout (timers.js:290:5)
              ! host.iobroker 2019-01-13 13:32:42.037 error Caught by controller[5]: at tryOnTimeout (timers.js:323:5)
              ! host.iobroker 2019-01-13 13:32:42.037 error Caught by controller[5]: at ontimeout (timers.js:498:11)
              ! host.iobroker 2019-01-13 13:32:42.036 error Caught by controller[5]: at Timeout. <anonymous>(/opt/iobroker/node_modules/cc-znp/lib/ccznp.js:233:18)
              ! host.iobroker 2019-01-13 13:32:42.036 error Caught by controller[5]: at CcZnp.emit (events.js:211:7)
              ! host.iobroker 2019-01-13 13:32:42.036 error Caught by controller[5]: at emitOne (events.js:116:13)
              ! host.iobroker 2019-01-13 13:32:42.036 error Caught by controller[5]: at Object.onceWrapper (events.js:315:30)
              ! host.iobroker 2019-01-13 13:32:42.036 error Caught by controller[5]: at CcZnp. <anonymous>(/opt/iobroker/node_modules/cc-znp/lib/ccznp.js:254:22)
              ! host.iobroker 2019-01-13 13:32:42.036 error Caught by controller[5]: 2019-01-13T12:32:18.974Z zigbee-shepherd:init Coordinator initialize had an error: Error: request timeout
              ! host.iobroker 2019-01-13 13:32:42.036 error Caught by controller[4]: 2019-01-13T12:32:18.973Z zigbee-shepherd:request RSP <– SYS:osalNvRead
              ! host.iobroker 2019-01-13 13:32:42.036 error Caught by controller[3]: Sun, 13 Jan 2019 12:32:18 GMT cc-znp:SRSP <– SYS:osalNvRead, timeout
              ! host.iobroker 2019-01-13 13:32:42.036 error Caught by controller[2]: Sun, 13 Jan 2019 12:32:15 GMT cc-znp:SREQ –> SYS:osalNvRead, { id: 3840, offset: 0, len: 1, value: [ 85 ] }
              ! host.iobroker 2019-01-13 13:32:42.036 error Caught by controller[1]: 2019-01-13T12:32:15.968Z zigbee-shepherd:request REQ –> SYS:osalNvRead
              ! host.iobroker 2019-01-13 13:32:42.036 error Caught by controller[0]: Sun, 13 Jan 2019 12:32:15 GMT cc-znp The serialport /dev/ttyACM0 is opened.
              ! zigbee.0 2019-01-13 13:32:18.978 error uncaught exception: Cannot read property 'close' of undefined
              ! host.iobroker 2019-01-13 13:32:09.959 info instance system.adapter.zigbee.0 terminated with code 0 (OK)
              ! host.iobroker 2019-01-13 13:32:09.959 error Caught by controller[3]: 2019-01-13T12:31:48.922Z zigbee-shepherd:init zigbee-shepherd booting…
              ! host.iobroker 2019-01-13 13:32:09.959 error Caught by controller[2]: Sun, 13 Jan 2019 12:31:46 GMT cc-znp:SREQ –> ZDO:mgmtPermitJoinReq, { addrmode: 15, dstaddr: 65532, duration: 0, tcsignificance: 0 }
              ! host.iobroker 2019-01-13 13:32:09.959 error Caught by controller[2]: 2019-01-13T12:31:46.008Z zigbee-shepherd:request REQ –> ZDO:mgmtPermitJoinReq
              ! host.iobroker 2019-01-13 13:32:09.959 error Caught by controller[1]: 2019-01-13T12:31:46.005Z zigbee-shepherd zigbee-shepherd is stopping.
              ! zigbee.0 2019-01-13 13:31:48.916 info Start on port: /dev/ttyACM0 with panID 6754 channel 11
              ! zigbee.0 2019-01-13 13:31:48.912 info starting. Version 0.8.2-a in /opt/iobroker/node_modules/iobroker.zigbee, node: v8.15.0
              ! host.iobroker 2019-01-13 13:31:48.508 info instance system.adapter.zigbee.0 started with pid 900
              ! host.iobroker 2019-01-13 13:31:46.004 info stopInstance system.adapter.zigbee.0 killing pid 886
              ! host.iobroker 2019-01-13 13:31:46.004 info stopInstance system.adapter.zigbee.0
              ! host.iobroker 2019-01-13 13:31:46.004 info object change system.adapter.zigbee.0
              ! zigbee.0 2019-01-13 13:31:11.397 error Zigbee publish to '0x000b57fffeecc83a', genOnOff - read - [{"attrId":0}] - 1 failed with error Error: Timed out after 30000 ms
              ! zigbee.0 2019-01-13 13:31:08.394 error Zigbee publish to '0x000b57fffef4ab08', genOnOff - read - [{"attrId":0}] - 1 failed with error Error: Timed out after 30000 ms
              ! zigbee.0 2019-01-13 13:31:05.386 error Zigbee publish to '0x90fd9ffffe191ed1', genOnOff - read - [{"attrId":0}] - 1 failed with error Error: Timed out after 30000 ms
              ! zigbee.0 2019-01-13 13:31:02.382 error Zigbee publish to '0x90fd9ffffe1912d3', genOnOff - read - [{"attrId":0}] - 1 failed with error Error: Timed out after 30000 ms
              ! zigbee.0 2019-01-13 13:30:59.382 error Zigbee publish to '0x000b57fffef4a9d0', genOnOff - read - [{"attrId":0}] - 1 failed with error Error: Timed out after 30000 ms
              ! zigbee.0 2019-01-13 13:30:56.402 error Zigbee publish to '0x000b57fffeecc83a', genLevelCtrl - read - [{"attrId":0}] - 1 failed with error Error: request timeout
              ! zigbee.0 2019-01-13 13:30:53.400 error Zigbee publish to '0x000b57fffef4ab08', genLevelCtrl - read - [{"attrId":0}] - 1 failed with error Error: request timeout
              ! zigbee.0 2019-01-13 13:30:50.397 error Zigbee publish to '0x90fd9ffffe191ed1', genLevelCtrl - read - [{"attrId":0}] - 1 failed with error Error: request timeout
              ! zigbee.0 2019-01-13 13:30:47.394 error Zigbee publish to '0x90fd9ffffe1912d3', genLevelCtrl - read - [{"attrId":0}] - 1 failed with error Error: request timeout
              ! zigbee.0 2019-01-13 13:30:44.392 error Zigbee publish to '0x000b57fffef4a9d0', genLevelCtrl - read - [{"attrId":0}] - 1 failed with error Error: request timeout
              ! zigbee.0 2019-01-13 13:30:41.389 error Zigbee publish to '0x000b57fffeecc83a', genOnOff - on - {} - 1 failed with error Error: request timeout
              ! zigbee.0 2019-01-13 13:30:38.385 error Zigbee publish to '0x000b57fffef4ab08', genOnOff - on - {} - 1 failed with error Error: request timeout
              ! zigbee.0 2019-01-13 13:30:35.381 error Zigbee publish to '0x90fd9ffffe191ed1', genOnOff - on - {} - 1 failed with error Error: request timeout
              ! zigbee.0 2019-01-13 13:30:32.376 error Zigbee publish to '0x90fd9ffffe1912d3', genOnOff - on - {} - 1 failed with error Error: request timeout
              ! zigbee.0 2019-01-13 13:30:29.375 error Zigbee publish to '0x000b57fffef4a9d0', genOnOff - on - {} - 1 failed with error Error: request timeout
              ! zigbee.0 2019-01-13 13:30:26.372 error Zigbee publish to '0x000b57fffeecc83a', genLevelCtrl - moveToLevelWithOnOff - {"level":64,"transtime":10} - 1 failed with error Error: request timeout
              ! zigbee.0 2019-01-13 13:30:23.369 error Zigbee publish to '0x000b57fffef4ab08', genLevelCtrl - moveToLevelWithOnOff - {"level":64,"transtime":10} - 1 failed with error Error: request timeout
              ! zigbee.0 2019-01-13 13:30:20.366 error Zigbee publish to '0x90fd9ffffe191ed1', genLevelCtrl - moveToLevelWithOnOff - {"level":64,"transtime":10} - 1 failed with error Error: request timeout
              ! zigbee.0 2019-01-13 13:30:17.361 error Zigbee publish to '0x90fd9ffffe1912d3', genLevelCtrl - moveToLevelWithOnOff - {"level":64,"transtime":10} - 1 failed with error Error: request timeout
              ! zigbee.0 2019-01-13 13:30:14.359 error Zigbee publish to '0x000b57fffef4a9d0', genLevelCtrl - moveToLevelWithOnOff - {"level":64,"transtime":10} - 1 failed with error Error: request timeout
              ! node-red.0 2019-01-13 13:30:09.492 info Save /opt/iobroker/iobroker-data/node-red/flows.json
              ! mqtt.0 2019-01-13 13:30:09.012 info Client [mqtt_a10c164a.651bb8] connected with secret 1547382609010_9481
              ! mqtt.0 2019-01-13 13:30:08.979 info Client [mqtt_4d05afb2.d11fc] connection closed: disconnected
              ! zigbee.0 2019-01-13 13:28:47.039 info List of ports: [{"comName":"/dev/ttyACM0"},{"comName":"/dev/ttyS0"},{"comName":"/dev/ttyS1"},{"comName":"/dev/ttyS2"},{"comName":"/dev/ttyS3"}]
              ! zigbee.0 2019-01-13 13:27:23.032 error Zigbee publish to '0x000b57fffef4a9d0', genLevelCtrl - read - [{"attrId":0}] - 1 failed with error Error: Timed out after 30000 ms
              ! zigbee.0 2019-01-13 13:27:22.473 error Zigbee publish to '0x000b57fffeecc83a', genOnOff - read - [{"attrId":0}] - 1 failed with error Error: Timed out after 30000 ms
              ! zigbee.0 2019-01-13 13:27:22.467 error Zigbee publish to '0x000b57fffef4ab08', genOnOff - read - [{"attrId":0}] - 1 failed with error Error: Timed out after 30000 ms
              ! zigbee.0 2019-01-13 13:27:22.454 error Zigbee publish to '0x90fd9ffffe191ed1', genOnOff - read - [{"attrId":0}] - 1 failed with error Error: Timed out after 30000 ms
              ! zigbee.0 2019-01-13 13:27:22.444 error Zigbee publish to '0x90fd9ffffe1912d3', genOnOff - read - [{"attrId":0}] - 1 failed with error Error: Timed out after 30000 ms
              ! zigbee.0 2019-01-13 13:27:05.122 error Zigbee publish to '0x000b57fffeecc83a', genLevelCtrl - read - [{"attrId":0}] - 1 failed with error Error: request timeout
              ! zigbee.0 2019-01-13 13:27:02.119 error Zigbee publish to '0x000b57fffef4ab08', genLevelCtrl - read - [{"attrId":0}] - 1 failed with error Error: request timeout
              ! zigbee.0 2019-01-13 13:26:59.117 error Zigbee publish to '0x90fd9ffffe191ed1', genLevelCtrl - read - [{"attrId":0}] - 1 failed with error Error: request timeout
              ! zigbee.0 2019-01-13 13:26:56.115 error Zigbee publish to '0x90fd9ffffe1912d3', genLevelCtrl - read - [{"attrId":0}] - 1 failed with error Error: request timeout
              ! node-red.0 2019-01-13 13:26:48.219 info Save /opt/iobroker/iobroker-data/node-red/flows.json
              ! mqtt.0 2019-01-13 13:26:47.806 info Client [mqtt_4d05afb2.d11fc] connected with secret 1547382407755_6886
              ! mqtt.0 2019-01-13 13:26:47.712 info Client [mqtt_c49f01df.f05de] connection closed: disconnected
              ! zigbee.0 2019-01-13 13:26:01.294 info List of ports: [{"comName":"/dev/ttyACM0"},{"comName":"/dev/ttyS0"},{"comName":"/dev/ttyS1"},{"comName":"/dev/ttyS2"},{"comName":"/dev/ttyS3"}]
              ! zigbee.0 2019-01-13 13:20:31.771 info 8 (0x00158d00028792a8): MFKZQ01LM - Xiaomi Mi/Aqara smart home cube (EndDevice)
              ! zigbee.0 2019-01-13 13:20:31.771 info 7 (0x00178801038a91ed): 9290012573A - Philips Hue white and color ambiance E26/E27/E14 (Router)
              ! zigbee.0 2019-01-13 13:20:31.771 info 6 (0x000b57fffeecc83a): LED1537R6 - IKEA TRADFRI LED bulb GU10 400 lumen, dimmable, white spectrum (Router)
              ! zigbee.0 2019-01-13 13:20:31.770 info 5 (0x000b57fffef4ab08): LED1537R6 - IKEA TRADFRI LED bulb GU10 400 lumen, dimmable, white spectrum (Router)
              ! zigbee.0 2019-01-13 13:20:31.770 info 4 (0x90fd9ffffe191ed1): LED1537R6 - IKEA TRADFRI LED bulb GU10 400 lumen, dimmable, white spectrum (Router)
              ! zigbee.0 2019-01-13 13:20:31.770 info 3 (0x90fd9ffffe1912d3): LED1537R6 - IKEA TRADFRI LED bulb GU10 400 lumen, dimmable, white spectrum (Router)
              ! zigbee.0 2019-01-13 13:20:31.770 info 2 (0x000b57fffef4a9d0): LED1537R6 - IKEA TRADFRI LED bulb GU10 400 lumen, dimmable, white spectrum (Router)
              ! zigbee.0 2019-01-13 13:20:31.770 info 1 (0x00158d00027de744): MFKZQ01LM - Xiaomi Mi/Aqara smart home cube (EndDevice)
              ! zigbee.0 2019-01-13 13:20:31.767 info zigbee-shepherd ready. version: 2.6.3 rev 20181224
              ! zigbee.0 2019-01-13 13:20:31.763 info zigbee-shepherd started!
              ! zigbee.0 2019-01-13 13:20:30.608 info Start on port: /dev/ttyACM0 with panID 6754 channel 11
              ! zigbee.0 2019-01-13 13:20:30.604 info starting. Version 0.8.2-a in /opt/iobroker/node_modules/iobroker.zigbee, node: v8.15.0
              ! host.iobroker 2019-01-13 13:20:30.197 info instance system.adapter.zigbee.0 started with pid 886
              ! host.iobroker 2019-01-13 13:20:00.194 info Restart adapter system.adapter.zigbee.0 because enabled</anonymous></anonymous></anonymous></anonymous>

              Also irgendwas stimmt da nicht… Kann ich irgendwo den LogLevel erhöhen?

              Grüße

              Henry

              1 Antwort Letzte Antwort
              0
              • arteckA Offline
                arteckA Offline
                arteck
                Developer Most Active
                schrieb am zuletzt editiert von
                #7

                node: v8.15.0 das ist das Problem

                bei mir läufts hiermit auch nicht

                8.11.x funktioniert

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

                1 Antwort Letzte Antwort
                0
                • C Offline
                  C Offline
                  cyrano330
                  schrieb am zuletzt editiert von
                  #8

                  Hi Arteck,

                  auf die Gefahr hin, dass ich jetzt die vollkommen falsche Frage stelle - was muss ich tun um "Node" von 8.15.0 auf 8.11.x runterzubekommen? Hast Du eventuell einen Link? Ich will verstehen was ich hier mache….

                  Danke!

                  Gruß

                  Henry

                  1 Antwort Letzte Antwort
                  0
                  • arteckA Offline
                    arteckA Offline
                    arteck
                    Developer Most Active
                    schrieb am zuletzt editiert von
                    #9

                    viewtopic.php?f=8&p=218970#p218970

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

                    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
                    FAQ Cloud / IOT
                    HowTo: Node.js-Update
                    HowTo: Backup/Restore
                    Downloads
                    BLOG

                    578

                    Online

                    32.7k

                    Benutzer

                    82.5k

                    Themen

                    1.3m

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

                    • Du hast noch kein Konto? Registrieren

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