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. keine Funktion mehr mit Zigbee

NEWS

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

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

  • Weihnachtsangebot 2025! 🎄
    BluefoxB
    Bluefox
    25
    1
    2.5k

keine Funktion mehr mit Zigbee

Geplant Angeheftet Gesperrt Verschoben ioBroker Allgemein
zigbee stickfehler im logproblem
25 Beiträge 8 Kommentatoren 1.6k Aufrufe 8 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.
  • Holger EtzelH Offline
    Holger EtzelH Offline
    Holger Etzel
    schrieb am zuletzt editiert von
    #1

    Hallo,
    habe mal wieder ein Problem.
    Zigbee läuft bei mir auf einem Raspberry-Slave. Hier wurde mir angezeigt das die Version 1.3.3 installiert ist. Nach einem Update auf die 1.6.6 funktioniert nichts mehr. Komme auch nur noch auf die 1.4.1 zurück. Überall die gleichen Fehler.

    
    zigbee.1
    2021-12-08 20:33:36.638	info	Installed Version: iobroker.zigbee@1.4.1
    
    zigbee.1
    2021-12-08 20:33:36.636	warn	Read-only state "zigbee.1.info.connection" has been written without ack-flag with value "false"
    
    zigbee.1
    2021-12-08 20:33:36.622	error	Error: Error while opening serialport 'Error: Error: No such file or directory, cannot open /dev/ttyACM0' at Znp.<anonymous> (/opt/iobroker/node_modules/zigbee-herdsman/dist/adapter/z-stack/znp/znp.js:136:32) at Generator.next (<anonymous>) at /opt/iobroker/node_modules/zigbee-herdsman/dist/adapter/z-stack/znp/znp.js:27:71 at new Promise (<anonymous>) at __awaiter (/opt/iobroker/node_modules/zigbee-herdsman/dist/adapter/z-stack/znp/znp.js:23:12) at SerialPort.<anonymous> (/opt/iobroker/node_modules/zigbee-herdsman/dist/adapter/z-stack/znp/znp.js:134:49) at SerialPort._error (/opt/iobroker/node_modules/zigbee-herdsman/node_modules/@serialport/stream/lib/index.js:198:14) at /opt/iobroker/node_modules/zigbee-herdsman/node_modules/@serialport/stream/lib/index.js:242:12
    
    zigbee.1
    2021-12-08 20:33:36.621	error	Failed to start Zigbee
    
    zigbee.1
    2021-12-08 20:33:36.609	info	Starting Zigbee npm ...
    
    zigbee.1
    2021-12-08 20:33:36.607	info	Try to reconnect. 1 attempts left
    
    zigbee.1
    2021-12-08 20:33:26.672	info	Installed Version: iobroker.zigbee@1.4.1
    
    zigbee.1
    2021-12-08 20:33:26.668	warn	Read-only state "zigbee.1.info.connection" has been written without ack-flag with value "false"
    
    zigbee.1
    2021-12-08 20:33:26.666	warn	Read-only state "zigbee.1.info.connection" has been written without ack-flag with value "false"
    
    zigbee.1
    2021-12-08 20:33:26.606	error	Error: Error while opening serialport 'Error: Error: No such file or directory, cannot open /dev/ttyACM0' at Znp.<anonymous> (/opt/iobroker/node_modules/zigbee-herdsman/dist/adapter/z-stack/znp/znp.js:136:32) at Generator.next (<anonymous>) at /opt/iobroker/node_modules/zigbee-herdsman/dist/adapter/z-stack/znp/znp.js:27:71 at new Promise (<anonymous>) at __awaiter (/opt/iobroker/node_modules/zigbee-herdsman/dist/adapter/z-stack/znp/znp.js:23:12) at SerialPort.<anonymous> (/opt/iobroker/node_modules/zigbee-herdsman/dist/adapter/z-stack/znp/znp.js:134:49) at SerialPort._error (/opt/iobroker/node_modules/zigbee-herdsman/node_modules/@serialport/stream/lib/index.js:198:14) at /opt/iobroker/node_modules/zigbee-herdsman/node_modules/@serialport/stream/lib/index.js:242:12
    
    zigbee.1
    2021-12-08 20:33:26.605	error	Failed to start Zigbee
    
    zigbee.1
    2021-12-08 20:33:26.468	info	Starting Zigbee npm ...
    
    zigbee.1
    2021-12-08 20:33:26.323	info	starting. Version 1.4.1 in /opt/iobroker/node_modules/iobroker.zigbee, node: v12.22.7, js-controller: 3.3.21
    host.raspbislave01
    2021-12-08 20:33:22.835	info	instance system.adapter.zigbee.1 started with pid 2198
    host.raspbislave01
    2021-12-08 20:33:20.571	info	instance system.adapter.zigbee.1 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
    
    zigbee.1
    2021-12-08 20:33:19.793	warn	Read-only state "zigbee.1.info.pairingMessage" has been written without ack-flag with value "Error: Failed to stop zigbee (TypeError: Cannot read property 'getEntries' of null at Function.loadFromDatabaseIfNecessary (/opt/iobroker/node_modules/zigbee-herdsman/dist/controller/model/group.js:76:55) at Function.all (/opt/iobroker/node_modules/zigbee-herdsman/dist/controller/model/group.js:88:15) at Controller.databaseSave (/opt/iobroker/node_modules/zigbee-herdsman/dist/controller/controller.js:222:45) at Controller.<anonymous> (/opt/iobroker/node_modules/zigbee-herdsman/dist/controller/controller.js:203:18) at Generator.next (<anonymous>) at /opt/iobroker/node_modules/zigbee-herdsman/dist/controller/controller.js:27:71 at new Promise (<anonymous>) at __awaiter (/opt/iobroker/node_modules/zigbee-herdsman/dist/controller/controller.js:23:12) at Controller.stop (/opt/iobroker/node_modules/zigbee-herdsman/dist/controller/controller.js:202:16) at ZigbeeController.stop (/opt/iobroker/node_modules/iobroker.zigbee/lib/zigbeecontroller.js:310:33)). undefined"
    
    zigbee.1
    2021-12-08 20:33:19.782	error	Cannot read property 'getEntries' of null
    
    zigbee.1
    2021-12-08 20:33:19.781	error	TypeError: Cannot read property 'getEntries' of null at Function.loadFromDatabaseIfNecessary (/opt/iobroker/node_modules/zigbee-herdsman/dist/controller/model/device.js:216:55) at Function.all (/opt/iobroker/node_modules/zigbee-herdsman/dist/controller/model/device.js:236:16) at Controller.getDevices (/opt/iobroker/node_modules/zigbee-herdsman/dist/controller/controller.js:255:31) at ZigbeeController.getClients (/opt/iobroker/node_modules/iobroker.zigbee/lib/zigbeecontroller.js:203:49) at DeviceAvailability.stop (/opt/iobroker/node_modules/iobroker.zigbee/lib/zbDeviceAvailability.js:180:43) at ZigbeeController.callExtensionMethod (/opt/iobroker/node_modules/iobroker.zigbee/lib/zigbeecontroller.js:189:42) at ZigbeeController.stop (/opt/iobroker/node_modules/iobroker.zigbee/lib/zigbeecontroller.js:306:20) at Zigbee.onUnload (/opt/iobroker/node_modules/iobroker.zigbee/main.js:465:41) at Zigbee.emit (events.js:314:20) at stop (/opt/iobroker/node_modules/iobroker.js-controller/lib/adapter.js:8747:22)
    
    zigbee.1
    2021-12-08 20:33:19.775	error	unhandled promise rejection: Cannot read property 'getEntries' of null
    
    zigbee.1
    2021-12-08 20:33:19.774	error	Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().
    
    zigbee.1
    2021-12-08 20:33:19.771	info	Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
    
    zigbee.1
    2021-12-08 20:33:19.769	info	terminating
    
    zigbee.1
    2021-12-08 20:33:19.767	error	Failed to stop zigbee (TypeError: Cannot read property 'getEntries' of null at Function.loadFromDatabaseIfNecessary (/opt/iobroker/node_modules/zigbee-herdsman/dist/controller/model/group.js:76:55) at Function.all (/opt/iobroker/node_modules/zigbee-herdsman/dist/controller/model/group.js:88:15) at Controller.databaseSave (/opt/iobroker/node_modules/zigbee-herdsman/dist/controller/controller.js:222:45) at Controller.<anonymous> (/opt/iobroker/node_modules/zigbee-herdsman/dist/controller/controller.js:203:18) at Generator.next (<anonymous>) at /opt/iobroker/node_modules/zigbee-herdsman/dist/controller/controller.js:27:71 at new Promise (<anonymous>) at __awaiter (/opt/iobroker/node_modules/zigbee-herdsman/dist/controller/controller.js:23:12) at Controller.stop (/opt/iobroker/node_modules/zigbee-herdsman/dist/controller/controller.js:202:16) at ZigbeeController.stop (/opt/iobroker/node_modules/iobroker.zigbee/lib/zigbeecontroller.js:310:33))
    
    zigbee.1
    2021-12-08 20:33:19.762	info	Zigbee: disabling joining new devices.
    
    zigbee.1
    2021-12-08 20:33:19.752	info	cleaned everything up...
    
    zigbee.1
    2021-12-08 20:33:19.748	info	Got terminate signal TERMINATE_YOURSELF
    host.raspbislave01
    2021-12-08 20:33:20.571	info	instance system.adapter.zigbee.1 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
    
    zigbee.1
    2021-12-08 20:33:19.793	warn	Read-only state "zigbee.1.info.pairingMessage" has been written without ack-flag with value "Error: Failed to stop zigbee (TypeError: Cannot read property 'getEntries' of null at Function.loadFromDatabaseIfNecessary (/opt/iobroker/node_modules/zigbee-herdsman/dist/controller/model/group.js:76:55) at Function.all (/opt/iobroker/node_modules/zigbee-herdsman/dist/controller/model/group.js:88:15) at Controller.databaseSave (/opt/iobroker/node_modules/zigbee-herdsman/dist/controller/controller.js:222:45) at Controller.<anonymous> (/opt/iobroker/node_modules/zigbee-herdsman/dist/controller/controller.js:203:18) at Generator.next (<anonymous>) at /opt/iobroker/node_modules/zigbee-herdsman/dist/controller/controller.js:27:71 at new Promise (<anonymous>) at __awaiter (/opt/iobroker/node_modules/zigbee-herdsman/dist/controller/controller.js:23:12) at Controller.stop (/opt/iobroker/node_modules/zigbee-herdsman/dist/controller/controller.js:202:16) at ZigbeeController.stop (/opt/iobroker/node_modules/iobroker.zigbee/lib/zigbeecontroller.js:310:33)). undefined"
    
    zigbee.1
    2021-12-08 20:33:19.782	error	Cannot read property 'getEntries' of null
    
    zigbee.1
    2021-12-08 20:33:19.781	error	TypeError: Cannot read property 'getEntries' of null at Function.loadFromDatabaseIfNecessary (/opt/iobroker/node_modules/zigbee-herdsman/dist/controller/model/device.js:216:55) at Function.all (/opt/iobroker/node_modules/zigbee-herdsman/dist/controller/model/device.js:236:16) at Controller.getDevices (/opt/iobroker/node_modules/zigbee-herdsman/dist/controller/controller.js:255:31) at ZigbeeController.getClients (/opt/iobroker/node_modules/iobroker.zigbee/lib/zigbeecontroller.js:203:49) at DeviceAvailability.stop (/opt/iobroker/node_modules/iobroker.zigbee/lib/zbDeviceAvailability.js:180:43) at ZigbeeController.callExtensionMethod (/opt/iobroker/node_modules/iobroker.zigbee/lib/zigbeecontroller.js:189:42) at ZigbeeController.stop (/opt/iobroker/node_modules/iobroker.zigbee/lib/zigbeecontroller.js:306:20) at Zigbee.onUnload (/opt/iobroker/node_modules/iobroker.zigbee/main.js:465:41) at Zigbee.emit (events.js:314:20) at stop (/opt/iobroker/node_modules/iobroker.js-controller/lib/adapter.js:8747:22)
    
    zigbee.1
    2021-12-08 20:33:19.775	error	unhandled promise rejection: Cannot read property 'getEntries' of null
    
    zigbee.1
    2021-12-08 20:33:19.774	error	Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().
    
    zigbee.1
    2021-12-08 20:33:19.771	info	Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
    
    zigbee.1
    2021-12-08 20:33:19.769	info	terminating
    
    zigbee.1
    2021-12-08 20:33:19.767	error	Failed to stop zigbee (TypeError: Cannot read property 'getEntries' of null at Function.loadFromDatabaseIfNecessary (/opt/iobroker/node_modules/zigbee-herdsman/dist/controller/model/group.js:76:55) at Function.all (/opt/iobroker/node_modules/zigbee-herdsman/dist/controller/model/group.js:88:15) at Controller.databaseSave (/opt/iobroker/node_modules/zigbee-herdsman/dist/controller/controller.js:222:45) at Controller.<anonymous> (/opt/iobroker/node_modules/zigbee-herdsman/dist/controller/controller.js:203:18) at Generator.next (<anonymous>) at /opt/iobroker/node_modules/zigbee-herdsman/dist/controller/controller.js:27:71 at new Promise (<anonymous>) at __awaiter (/opt/iobroker/node_modules/zigbee-herdsman/dist/controller/controller.js:23:12) at Controller.stop (/opt/iobroker/node_modules/zigbee-herdsman/dist/controller/controller.js:202:16) at ZigbeeController.stop (/opt/iobroker/node_modules/iobroker.zigbee/lib/zigbeecontroller.js:310:33))
    

    kann hier jemand etwas damit anfangen?. Vorher hat alles super funktioniert.

    LG

    Holger

    mickymM 1 Antwort Letzte Antwort
    0
    • Holger EtzelH Offline
      Holger EtzelH Offline
      Holger Etzel
      schrieb am zuletzt editiert von
      #2

      @holger-etzel
      Update:

      Adapter wird grün, schaltet aber irgendwann wieder auf rot. Danach startet der Adapter wieder und das ganze geht von vorne los.
      Solange bis der Host abschaltet.

      BananaJoeB 1 Antwort Letzte Antwort
      0
      • Holger EtzelH Holger Etzel

        @holger-etzel
        Update:

        Adapter wird grün, schaltet aber irgendwann wieder auf rot. Danach startet der Adapter wieder und das ganze geht von vorne los.
        Solange bis der Host abschaltet.

        BananaJoeB Online
        BananaJoeB Online
        BananaJoe
        Most Active
        schrieb am zuletzt editiert von
        #3

        @holger-etzel mhh erst hat der Probleme mit dem seriellen Port ... eigentlich wird empfohlen statt /dev/ttyACM0 den Weg über /dev/serial/by-id/ zu gehen, da müsste das Gerät auch zu sehen sein und der Name ist immer gleich/ändert sich nicht.

        Du hast im Thread des Adapters bzw. auf der github-Seite vorher die Changelog gelesen? Insbesondere die "Attention! Attention! Attention! Attention! Attention! Attention! Attention!" Hinweise zu Änderungen ab Version 1.6.0?

        Eventuell fällst du mit deinem ZigBee-Adapter genau in das Problemschema.

        ioBroker@Ubuntu 24.04 LTS (VMware) für: >260 Geräte, 5 Switche, 7 AP, 9 IP-Cam, 1 NAS 42TB, 1 ESXi 15TB, 4 Proxmox 1TB, 1 Hyper-V 48TB, 14 x Echo, 5x FireTV, 5 x Tablett/Handy VIS || >=160 Tasmota/Shelly || >=95 ZigBee || PV 8.1kW / Akku 14kWh || 2x USV 750W kaskadiert || Creality CR-10 SE 3D-Drucker

        1 Antwort Letzte Antwort
        0
        • BananaJoeB Online
          BananaJoeB Online
          BananaJoe
          Most Active
          schrieb am zuletzt editiert von
          #4

          Nachtrag: Ansonsten fehlt die Info was für ein ZigBee-Stick du nutzt (und mit welcher Firmware), die üblichen Versionshinweise zu Node.js, npm und JS-Controller Version

          ioBroker@Ubuntu 24.04 LTS (VMware) für: >260 Geräte, 5 Switche, 7 AP, 9 IP-Cam, 1 NAS 42TB, 1 ESXi 15TB, 4 Proxmox 1TB, 1 Hyper-V 48TB, 14 x Echo, 5x FireTV, 5 x Tablett/Handy VIS || >=160 Tasmota/Shelly || >=95 ZigBee || PV 8.1kW / Akku 14kWh || 2x USV 750W kaskadiert || Creality CR-10 SE 3D-Drucker

          Holger EtzelH 1 Antwort Letzte Antwort
          0
          • BananaJoeB BananaJoe

            Nachtrag: Ansonsten fehlt die Info was für ein ZigBee-Stick du nutzt (und mit welcher Firmware), die üblichen Versionshinweise zu Node.js, npm und JS-Controller Version

            Holger EtzelH Offline
            Holger EtzelH Offline
            Holger Etzel
            schrieb am zuletzt editiert von
            #5

            @bananajoe

            sorry.
            js-controller 3.3.21
            node-js 14.18.2
            npm 6.14.15
            stick CC2538+CC2592
            firmware kann ich aktuell nichts dazu sagen

            AsgothianA 1 Antwort Letzte Antwort
            0
            • Holger EtzelH Holger Etzel

              Hallo,
              habe mal wieder ein Problem.
              Zigbee läuft bei mir auf einem Raspberry-Slave. Hier wurde mir angezeigt das die Version 1.3.3 installiert ist. Nach einem Update auf die 1.6.6 funktioniert nichts mehr. Komme auch nur noch auf die 1.4.1 zurück. Überall die gleichen Fehler.

              
              zigbee.1
              2021-12-08 20:33:36.638	info	Installed Version: iobroker.zigbee@1.4.1
              
              zigbee.1
              2021-12-08 20:33:36.636	warn	Read-only state "zigbee.1.info.connection" has been written without ack-flag with value "false"
              
              zigbee.1
              2021-12-08 20:33:36.622	error	Error: Error while opening serialport 'Error: Error: No such file or directory, cannot open /dev/ttyACM0' at Znp.<anonymous> (/opt/iobroker/node_modules/zigbee-herdsman/dist/adapter/z-stack/znp/znp.js:136:32) at Generator.next (<anonymous>) at /opt/iobroker/node_modules/zigbee-herdsman/dist/adapter/z-stack/znp/znp.js:27:71 at new Promise (<anonymous>) at __awaiter (/opt/iobroker/node_modules/zigbee-herdsman/dist/adapter/z-stack/znp/znp.js:23:12) at SerialPort.<anonymous> (/opt/iobroker/node_modules/zigbee-herdsman/dist/adapter/z-stack/znp/znp.js:134:49) at SerialPort._error (/opt/iobroker/node_modules/zigbee-herdsman/node_modules/@serialport/stream/lib/index.js:198:14) at /opt/iobroker/node_modules/zigbee-herdsman/node_modules/@serialport/stream/lib/index.js:242:12
              
              zigbee.1
              2021-12-08 20:33:36.621	error	Failed to start Zigbee
              
              zigbee.1
              2021-12-08 20:33:36.609	info	Starting Zigbee npm ...
              
              zigbee.1
              2021-12-08 20:33:36.607	info	Try to reconnect. 1 attempts left
              
              zigbee.1
              2021-12-08 20:33:26.672	info	Installed Version: iobroker.zigbee@1.4.1
              
              zigbee.1
              2021-12-08 20:33:26.668	warn	Read-only state "zigbee.1.info.connection" has been written without ack-flag with value "false"
              
              zigbee.1
              2021-12-08 20:33:26.666	warn	Read-only state "zigbee.1.info.connection" has been written without ack-flag with value "false"
              
              zigbee.1
              2021-12-08 20:33:26.606	error	Error: Error while opening serialport 'Error: Error: No such file or directory, cannot open /dev/ttyACM0' at Znp.<anonymous> (/opt/iobroker/node_modules/zigbee-herdsman/dist/adapter/z-stack/znp/znp.js:136:32) at Generator.next (<anonymous>) at /opt/iobroker/node_modules/zigbee-herdsman/dist/adapter/z-stack/znp/znp.js:27:71 at new Promise (<anonymous>) at __awaiter (/opt/iobroker/node_modules/zigbee-herdsman/dist/adapter/z-stack/znp/znp.js:23:12) at SerialPort.<anonymous> (/opt/iobroker/node_modules/zigbee-herdsman/dist/adapter/z-stack/znp/znp.js:134:49) at SerialPort._error (/opt/iobroker/node_modules/zigbee-herdsman/node_modules/@serialport/stream/lib/index.js:198:14) at /opt/iobroker/node_modules/zigbee-herdsman/node_modules/@serialport/stream/lib/index.js:242:12
              
              zigbee.1
              2021-12-08 20:33:26.605	error	Failed to start Zigbee
              
              zigbee.1
              2021-12-08 20:33:26.468	info	Starting Zigbee npm ...
              
              zigbee.1
              2021-12-08 20:33:26.323	info	starting. Version 1.4.1 in /opt/iobroker/node_modules/iobroker.zigbee, node: v12.22.7, js-controller: 3.3.21
              host.raspbislave01
              2021-12-08 20:33:22.835	info	instance system.adapter.zigbee.1 started with pid 2198
              host.raspbislave01
              2021-12-08 20:33:20.571	info	instance system.adapter.zigbee.1 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
              
              zigbee.1
              2021-12-08 20:33:19.793	warn	Read-only state "zigbee.1.info.pairingMessage" has been written without ack-flag with value "Error: Failed to stop zigbee (TypeError: Cannot read property 'getEntries' of null at Function.loadFromDatabaseIfNecessary (/opt/iobroker/node_modules/zigbee-herdsman/dist/controller/model/group.js:76:55) at Function.all (/opt/iobroker/node_modules/zigbee-herdsman/dist/controller/model/group.js:88:15) at Controller.databaseSave (/opt/iobroker/node_modules/zigbee-herdsman/dist/controller/controller.js:222:45) at Controller.<anonymous> (/opt/iobroker/node_modules/zigbee-herdsman/dist/controller/controller.js:203:18) at Generator.next (<anonymous>) at /opt/iobroker/node_modules/zigbee-herdsman/dist/controller/controller.js:27:71 at new Promise (<anonymous>) at __awaiter (/opt/iobroker/node_modules/zigbee-herdsman/dist/controller/controller.js:23:12) at Controller.stop (/opt/iobroker/node_modules/zigbee-herdsman/dist/controller/controller.js:202:16) at ZigbeeController.stop (/opt/iobroker/node_modules/iobroker.zigbee/lib/zigbeecontroller.js:310:33)). undefined"
              
              zigbee.1
              2021-12-08 20:33:19.782	error	Cannot read property 'getEntries' of null
              
              zigbee.1
              2021-12-08 20:33:19.781	error	TypeError: Cannot read property 'getEntries' of null at Function.loadFromDatabaseIfNecessary (/opt/iobroker/node_modules/zigbee-herdsman/dist/controller/model/device.js:216:55) at Function.all (/opt/iobroker/node_modules/zigbee-herdsman/dist/controller/model/device.js:236:16) at Controller.getDevices (/opt/iobroker/node_modules/zigbee-herdsman/dist/controller/controller.js:255:31) at ZigbeeController.getClients (/opt/iobroker/node_modules/iobroker.zigbee/lib/zigbeecontroller.js:203:49) at DeviceAvailability.stop (/opt/iobroker/node_modules/iobroker.zigbee/lib/zbDeviceAvailability.js:180:43) at ZigbeeController.callExtensionMethod (/opt/iobroker/node_modules/iobroker.zigbee/lib/zigbeecontroller.js:189:42) at ZigbeeController.stop (/opt/iobroker/node_modules/iobroker.zigbee/lib/zigbeecontroller.js:306:20) at Zigbee.onUnload (/opt/iobroker/node_modules/iobroker.zigbee/main.js:465:41) at Zigbee.emit (events.js:314:20) at stop (/opt/iobroker/node_modules/iobroker.js-controller/lib/adapter.js:8747:22)
              
              zigbee.1
              2021-12-08 20:33:19.775	error	unhandled promise rejection: Cannot read property 'getEntries' of null
              
              zigbee.1
              2021-12-08 20:33:19.774	error	Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().
              
              zigbee.1
              2021-12-08 20:33:19.771	info	Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
              
              zigbee.1
              2021-12-08 20:33:19.769	info	terminating
              
              zigbee.1
              2021-12-08 20:33:19.767	error	Failed to stop zigbee (TypeError: Cannot read property 'getEntries' of null at Function.loadFromDatabaseIfNecessary (/opt/iobroker/node_modules/zigbee-herdsman/dist/controller/model/group.js:76:55) at Function.all (/opt/iobroker/node_modules/zigbee-herdsman/dist/controller/model/group.js:88:15) at Controller.databaseSave (/opt/iobroker/node_modules/zigbee-herdsman/dist/controller/controller.js:222:45) at Controller.<anonymous> (/opt/iobroker/node_modules/zigbee-herdsman/dist/controller/controller.js:203:18) at Generator.next (<anonymous>) at /opt/iobroker/node_modules/zigbee-herdsman/dist/controller/controller.js:27:71 at new Promise (<anonymous>) at __awaiter (/opt/iobroker/node_modules/zigbee-herdsman/dist/controller/controller.js:23:12) at Controller.stop (/opt/iobroker/node_modules/zigbee-herdsman/dist/controller/controller.js:202:16) at ZigbeeController.stop (/opt/iobroker/node_modules/iobroker.zigbee/lib/zigbeecontroller.js:310:33))
              
              zigbee.1
              2021-12-08 20:33:19.762	info	Zigbee: disabling joining new devices.
              
              zigbee.1
              2021-12-08 20:33:19.752	info	cleaned everything up...
              
              zigbee.1
              2021-12-08 20:33:19.748	info	Got terminate signal TERMINATE_YOURSELF
              host.raspbislave01
              2021-12-08 20:33:20.571	info	instance system.adapter.zigbee.1 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
              
              zigbee.1
              2021-12-08 20:33:19.793	warn	Read-only state "zigbee.1.info.pairingMessage" has been written without ack-flag with value "Error: Failed to stop zigbee (TypeError: Cannot read property 'getEntries' of null at Function.loadFromDatabaseIfNecessary (/opt/iobroker/node_modules/zigbee-herdsman/dist/controller/model/group.js:76:55) at Function.all (/opt/iobroker/node_modules/zigbee-herdsman/dist/controller/model/group.js:88:15) at Controller.databaseSave (/opt/iobroker/node_modules/zigbee-herdsman/dist/controller/controller.js:222:45) at Controller.<anonymous> (/opt/iobroker/node_modules/zigbee-herdsman/dist/controller/controller.js:203:18) at Generator.next (<anonymous>) at /opt/iobroker/node_modules/zigbee-herdsman/dist/controller/controller.js:27:71 at new Promise (<anonymous>) at __awaiter (/opt/iobroker/node_modules/zigbee-herdsman/dist/controller/controller.js:23:12) at Controller.stop (/opt/iobroker/node_modules/zigbee-herdsman/dist/controller/controller.js:202:16) at ZigbeeController.stop (/opt/iobroker/node_modules/iobroker.zigbee/lib/zigbeecontroller.js:310:33)). undefined"
              
              zigbee.1
              2021-12-08 20:33:19.782	error	Cannot read property 'getEntries' of null
              
              zigbee.1
              2021-12-08 20:33:19.781	error	TypeError: Cannot read property 'getEntries' of null at Function.loadFromDatabaseIfNecessary (/opt/iobroker/node_modules/zigbee-herdsman/dist/controller/model/device.js:216:55) at Function.all (/opt/iobroker/node_modules/zigbee-herdsman/dist/controller/model/device.js:236:16) at Controller.getDevices (/opt/iobroker/node_modules/zigbee-herdsman/dist/controller/controller.js:255:31) at ZigbeeController.getClients (/opt/iobroker/node_modules/iobroker.zigbee/lib/zigbeecontroller.js:203:49) at DeviceAvailability.stop (/opt/iobroker/node_modules/iobroker.zigbee/lib/zbDeviceAvailability.js:180:43) at ZigbeeController.callExtensionMethod (/opt/iobroker/node_modules/iobroker.zigbee/lib/zigbeecontroller.js:189:42) at ZigbeeController.stop (/opt/iobroker/node_modules/iobroker.zigbee/lib/zigbeecontroller.js:306:20) at Zigbee.onUnload (/opt/iobroker/node_modules/iobroker.zigbee/main.js:465:41) at Zigbee.emit (events.js:314:20) at stop (/opt/iobroker/node_modules/iobroker.js-controller/lib/adapter.js:8747:22)
              
              zigbee.1
              2021-12-08 20:33:19.775	error	unhandled promise rejection: Cannot read property 'getEntries' of null
              
              zigbee.1
              2021-12-08 20:33:19.774	error	Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().
              
              zigbee.1
              2021-12-08 20:33:19.771	info	Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
              
              zigbee.1
              2021-12-08 20:33:19.769	info	terminating
              
              zigbee.1
              2021-12-08 20:33:19.767	error	Failed to stop zigbee (TypeError: Cannot read property 'getEntries' of null at Function.loadFromDatabaseIfNecessary (/opt/iobroker/node_modules/zigbee-herdsman/dist/controller/model/group.js:76:55) at Function.all (/opt/iobroker/node_modules/zigbee-herdsman/dist/controller/model/group.js:88:15) at Controller.databaseSave (/opt/iobroker/node_modules/zigbee-herdsman/dist/controller/controller.js:222:45) at Controller.<anonymous> (/opt/iobroker/node_modules/zigbee-herdsman/dist/controller/controller.js:203:18) at Generator.next (<anonymous>) at /opt/iobroker/node_modules/zigbee-herdsman/dist/controller/controller.js:27:71 at new Promise (<anonymous>) at __awaiter (/opt/iobroker/node_modules/zigbee-herdsman/dist/controller/controller.js:23:12) at Controller.stop (/opt/iobroker/node_modules/zigbee-herdsman/dist/controller/controller.js:202:16) at ZigbeeController.stop (/opt/iobroker/node_modules/iobroker.zigbee/lib/zigbeecontroller.js:310:33))
              

              kann hier jemand etwas damit anfangen?. Vorher hat alles super funktioniert.

              LG

              Holger

              mickymM Offline
              mickymM Offline
              mickym
              Most Active
              schrieb am zuletzt editiert von mickym
              #6

              @holger-etzel ICh weiß es hilft nicht viel - aber diese ganzen Fehler mit dem serial-Port haben mich immer begleitet und dachte an Adapter etc. Es ist die Hardware und zwar nicht unbedingt der Stick sondern direkt am Raspi. Ich habe seit ein paar Wochen einen Conbee2 Stick nun einem USB 2.0 Hub laufen und nicht ein einziger Fehler ist aufgetreten. Schau also erst mal, dass Du Deinen Stick nicht am USB 3.0 Stecker (die blauen) hast und dann wie gesagt weg mit dem Stick vom Raspi - der stört die Sticks anscheinend alle.

              Jeder Flow bzw. jedes Script, das ich hier poste implementiert jeder auf eigene Gefahr. Flows und Scripts können Fehler aufweisen und weder der Seitenbetreiber noch ich persönlich können hierfür haftbar gemacht werden. Das gleiche gilt für Empfehlungen aller Art.

              1 Antwort Letzte Antwort
              0
              • Holger EtzelH Holger Etzel

                @bananajoe

                sorry.
                js-controller 3.3.21
                node-js 14.18.2
                npm 6.14.15
                stick CC2538+CC2592
                firmware kann ich aktuell nichts dazu sagen

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

                @holger-etzel

                Du musst schon systematisch vorgehen:

                die Fehlermeldung

                'Error: Error: No such file or directory, cannot open /dev/ttyACM0'
                

                deutet darauf hin das die serielle Schnittstelle für den Zigbee Stick nicht vorhanden ist.

                Also bitte als erstes verifizieren das der Stick am Slave angeschlossen erkannt wird, und das die entsprechende Schnittstelle auch mit den passenden Rechten ausgestattet ist. Dann den Zigbee-Adapter neu starten und die Log-Einträge prüfen.

                A.

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

                1 Antwort Letzte Antwort
                0
                • Holger EtzelH Offline
                  Holger EtzelH Offline
                  Holger Etzel
                  schrieb am zuletzt editiert von Holger Etzel
                  #8

                  update:
                  habe einen neuen Versuch gestartet das ganze zum laufen zu bringen. Jetzt sieht das LOG so aus beim Start des Adapters.

                  
                  zigbee.1
                  2021-12-09 16:52:54.816	error	Error herdsman start
                  
                  zigbee.1
                  2021-12-09 16:52:54.815	error	Failed to start Zigbee
                  
                  zigbee.1
                  2021-12-09 16:52:54.814	error	Starting zigbee-herdsman problem : "Error while opening serialport 'Error: Error Resource temporarily unavailable Cannot lock port'"
                  
                  zigbee.1
                  2021-12-09 16:52:54.567	info	Installed Version: iobroker.zigbee@1.6.6
                  
                  zigbee.1
                  2021-12-09 16:52:54.528	info	Starting Zigbee npm ...
                  
                  zigbee.1
                  2021-12-09 16:52:54.526	info	Try to reconnect. 1 attempts left
                  
                  shuttercontrol.0
                  2021-12-09 16:52:50.166	info	#12 Set ID: shelly.0.SHSW-25#BCDDC277BB46#1.Shutter.Position Position Küche Strassenseite value: 60%
                  
                  synology.0
                  2021-12-09 16:52:46.468	info	starting. Version 0.1.18 in /opt/iobroker/node_modules/iobroker.synology, node: v14.18.2, js-controller: 3.3.21
                  
                  zigbee.1
                  2021-12-09 16:52:44.522	error	Error herdsman start
                  
                  zigbee.1
                  2021-12-09 16:52:44.521	error	Failed to start Zigbee
                  
                  zigbee.1
                  2021-12-09 16:52:44.521	error	Starting zigbee-herdsman problem : "startup failed - configuration-adapter mismatch - see logs above for more information"
                  
                  zigbee.1
                  2021-12-09 16:52:44.345	error	Re-commissioning your network will require re-pairing of all devices!
                  
                  zigbee.1
                  2021-12-09 16:52:44.345	error	If you wish to re-commission your network, please remove coordinator backup at /opt/iobroker/iobroker-data/zigbee_1/nvbackup.json.
                  
                  zigbee.1
                  2021-12-09 16:52:44.344	error	Please update configuration to prevent further issues.
                  
                  zigbee.1
                  2021-12-09 16:52:44.344	error	- Channel List: configured=14, adapter=14
                  
                  zigbee.1
                  2021-12-09 16:52:44.343	error	- Network Key: configured=01030507090b0d0f00020406080a0c0d, adapter=01030507090b0d0f00020406080a0c0d
                  
                  zigbee.1
                  2021-12-09 16:52:44.342	error	- Extended PAN ID: configured=dadddddddddddddd, adapter=00124b0009d7fce3
                  
                  zigbee.1
                  2021-12-09 16:52:44.341	error	- PAN ID: configured=6756, adapter=6756
                  
                  zigbee.1
                  2021-12-09 16:52:44.340	error	Configuration is not consistent with adapter state/backup!
                  
                  
                  zigbee.1
                  2021-12-09 16:52:44.260	info	Installed Version: iobroker.zigbee@1.6.6
                  
                  zigbee.1
                  2021-12-09 16:52:43.710	info	Starting Zigbee npm ...
                  
                  zigbee.1
                  2021-12-09 16:52:43.598	info	starting. Version 1.6.6 in /opt/iobroker/node_modules/iobroker.zigbee, node: v14.18.2, js-controller: 3.3.21
                  
                  J 1 Antwort Letzte Antwort
                  0
                  • Holger EtzelH Holger Etzel

                    update:
                    habe einen neuen Versuch gestartet das ganze zum laufen zu bringen. Jetzt sieht das LOG so aus beim Start des Adapters.

                    
                    zigbee.1
                    2021-12-09 16:52:54.816	error	Error herdsman start
                    
                    zigbee.1
                    2021-12-09 16:52:54.815	error	Failed to start Zigbee
                    
                    zigbee.1
                    2021-12-09 16:52:54.814	error	Starting zigbee-herdsman problem : "Error while opening serialport 'Error: Error Resource temporarily unavailable Cannot lock port'"
                    
                    zigbee.1
                    2021-12-09 16:52:54.567	info	Installed Version: iobroker.zigbee@1.6.6
                    
                    zigbee.1
                    2021-12-09 16:52:54.528	info	Starting Zigbee npm ...
                    
                    zigbee.1
                    2021-12-09 16:52:54.526	info	Try to reconnect. 1 attempts left
                    
                    shuttercontrol.0
                    2021-12-09 16:52:50.166	info	#12 Set ID: shelly.0.SHSW-25#BCDDC277BB46#1.Shutter.Position Position Küche Strassenseite value: 60%
                    
                    synology.0
                    2021-12-09 16:52:46.468	info	starting. Version 0.1.18 in /opt/iobroker/node_modules/iobroker.synology, node: v14.18.2, js-controller: 3.3.21
                    
                    zigbee.1
                    2021-12-09 16:52:44.522	error	Error herdsman start
                    
                    zigbee.1
                    2021-12-09 16:52:44.521	error	Failed to start Zigbee
                    
                    zigbee.1
                    2021-12-09 16:52:44.521	error	Starting zigbee-herdsman problem : "startup failed - configuration-adapter mismatch - see logs above for more information"
                    
                    zigbee.1
                    2021-12-09 16:52:44.345	error	Re-commissioning your network will require re-pairing of all devices!
                    
                    zigbee.1
                    2021-12-09 16:52:44.345	error	If you wish to re-commission your network, please remove coordinator backup at /opt/iobroker/iobroker-data/zigbee_1/nvbackup.json.
                    
                    zigbee.1
                    2021-12-09 16:52:44.344	error	Please update configuration to prevent further issues.
                    
                    zigbee.1
                    2021-12-09 16:52:44.344	error	- Channel List: configured=14, adapter=14
                    
                    zigbee.1
                    2021-12-09 16:52:44.343	error	- Network Key: configured=01030507090b0d0f00020406080a0c0d, adapter=01030507090b0d0f00020406080a0c0d
                    
                    zigbee.1
                    2021-12-09 16:52:44.342	error	- Extended PAN ID: configured=dadddddddddddddd, adapter=00124b0009d7fce3
                    
                    zigbee.1
                    2021-12-09 16:52:44.341	error	- PAN ID: configured=6756, adapter=6756
                    
                    zigbee.1
                    2021-12-09 16:52:44.340	error	Configuration is not consistent with adapter state/backup!
                    
                    
                    zigbee.1
                    2021-12-09 16:52:44.260	info	Installed Version: iobroker.zigbee@1.6.6
                    
                    zigbee.1
                    2021-12-09 16:52:43.710	info	Starting Zigbee npm ...
                    
                    zigbee.1
                    2021-12-09 16:52:43.598	info	starting. Version 1.6.6 in /opt/iobroker/node_modules/iobroker.zigbee, node: v14.18.2, js-controller: 3.3.21
                    
                    J Offline
                    J Offline
                    Jan1
                    schrieb am zuletzt editiert von
                    #9

                    @holger-etzel
                    Immer noch der Port nicht erreichbar.

                    1 Antwort Letzte Antwort
                    0
                    • Holger EtzelH Offline
                      Holger EtzelH Offline
                      Holger Etzel
                      schrieb am zuletzt editiert von
                      #10

                      @jan1
                      wie prüfe ich das weiter, stehe wohl grad auf dem schlauch

                      J 1 Antwort Letzte Antwort
                      0
                      • Holger EtzelH Holger Etzel

                        @jan1
                        wie prüfe ich das weiter, stehe wohl grad auf dem schlauch

                        J Offline
                        J Offline
                        Jan1
                        schrieb am zuletzt editiert von
                        #11

                        @holger-etzel
                        gib man

                        ls /dev/serial/by-id/
                        

                        in der Konsole ein, poste das und dann ein Srceenshot von dem was Du als Port im Adapter eingetragen hast.

                        Holger EtzelH 1 Antwort Letzte Antwort
                        0
                        • J Jan1

                          @holger-etzel
                          gib man

                          ls /dev/serial/by-id/
                          

                          in der Konsole ein, poste das und dann ein Srceenshot von dem was Du als Port im Adapter eingetragen hast.

                          Holger EtzelH Offline
                          Holger EtzelH Offline
                          Holger Etzel
                          schrieb am zuletzt editiert von
                          #12

                          @jan1

                          ls /dev/serial/by-id/
                          usb-Texas_Instruments_CC2538_USB_CDC-if00

                          und

                          ls -la /dev/serial/by-id
                          insgesamt 0
                          drwxr-xr-x 2 root root 60 Dez 9 00:34 .
                          drwxr-xr-x 4 root root 80 Dez 9 00:34 ..
                          lrwxrwxrwx 1 root root 13 Dez 9 00:34 usb-Texas_Instruments_CC2538_USB_CDC-if00

                          zigbee.PNG

                          BananaJoeB 1 Antwort Letzte Antwort
                          0
                          • Holger EtzelH Holger Etzel

                            @jan1

                            ls /dev/serial/by-id/
                            usb-Texas_Instruments_CC2538_USB_CDC-if00

                            und

                            ls -la /dev/serial/by-id
                            insgesamt 0
                            drwxr-xr-x 2 root root 60 Dez 9 00:34 .
                            drwxr-xr-x 4 root root 80 Dez 9 00:34 ..
                            lrwxrwxrwx 1 root root 13 Dez 9 00:34 usb-Texas_Instruments_CC2538_USB_CDC-if00

                            zigbee.PNG

                            BananaJoeB Online
                            BananaJoeB Online
                            BananaJoe
                            Most Active
                            schrieb am zuletzt editiert von
                            #13

                            @holger-etzel Und im Adapter trägst du nun mal

                            /dev/serial/by-id/usb-Texas_Instruments_CC2538_USB_CDC-if00
                            

                            ein und probierst es noch mal

                            ioBroker@Ubuntu 24.04 LTS (VMware) für: >260 Geräte, 5 Switche, 7 AP, 9 IP-Cam, 1 NAS 42TB, 1 ESXi 15TB, 4 Proxmox 1TB, 1 Hyper-V 48TB, 14 x Echo, 5x FireTV, 5 x Tablett/Handy VIS || >=160 Tasmota/Shelly || >=95 ZigBee || PV 8.1kW / Akku 14kWh || 2x USV 750W kaskadiert || Creality CR-10 SE 3D-Drucker

                            Holger EtzelH 1 Antwort Letzte Antwort
                            0
                            • BananaJoeB BananaJoe

                              @holger-etzel Und im Adapter trägst du nun mal

                              /dev/serial/by-id/usb-Texas_Instruments_CC2538_USB_CDC-if00
                              

                              ein und probierst es noch mal

                              Holger EtzelH Offline
                              Holger EtzelH Offline
                              Holger Etzel
                              schrieb am zuletzt editiert von Holger Etzel
                              #14

                              @bananajoe said in keine Funktion mehr mit Zigbee:

                              /dev/serial/by-id/usb-Texas_Instruments_CC2538_USB_CDC-if00

                              gleiches LOG

                              Thomas BraunT GlasfaserG 2 Antworten Letzte Antwort
                              0
                              • Holger EtzelH Holger Etzel

                                @bananajoe said in keine Funktion mehr mit Zigbee:

                                /dev/serial/by-id/usb-Texas_Instruments_CC2538_USB_CDC-if00

                                gleiches LOG

                                Thomas BraunT Online
                                Thomas BraunT Online
                                Thomas Braun
                                Most Active
                                schrieb am zuletzt editiert von
                                #15

                                @holger-etzel

                                Extended PAN ID: configured=dadddddddddddddd, adapter=00124b0009d7fce3
                                

                                Muss/soll übereinstimmen. Im Adapter anpassen.

                                Linux-Werkzeugkasten:
                                https://forum.iobroker.net/topic/42952/der-kleine-iobroker-linux-werkzeugkasten
                                NodeJS Fixer Skript:
                                https://forum.iobroker.net/topic/68035/iob-node-fix-skript
                                iob_diag: curl -sLf -o diag.sh https://iobroker.net/diag.sh && bash diag.sh

                                Holger EtzelH 1 Antwort Letzte Antwort
                                0
                                • Holger EtzelH Holger Etzel

                                  @bananajoe said in keine Funktion mehr mit Zigbee:

                                  /dev/serial/by-id/usb-Texas_Instruments_CC2538_USB_CDC-if00

                                  gleiches LOG

                                  GlasfaserG Offline
                                  GlasfaserG Offline
                                  Glasfaser
                                  schrieb am zuletzt editiert von
                                  #16

                                  @holger-etzel

                                  Ich finde hier keine Angaben , habe das gefunden

                                  IObroker läuft in einer VM auf der Synology.

                                  ist dass noch so !?

                                  Synology 918+ 16GB - ioBroker in Docker v9 , VISO auf Trekstor Primebook C13 13,3" , Hikvision Domkameras mit Surveillance Station .. CCU RaspberryMatic in Synology VM .. Zigbee CC2538+CC2592 .. Sonoff .. KNX .. Modbus ..

                                  Holger EtzelH 1 Antwort Letzte Antwort
                                  0
                                  • GlasfaserG Glasfaser

                                    @holger-etzel

                                    Ich finde hier keine Angaben , habe das gefunden

                                    IObroker läuft in einer VM auf der Synology.

                                    ist dass noch so !?

                                    Holger EtzelH Offline
                                    Holger EtzelH Offline
                                    Holger Etzel
                                    schrieb am zuletzt editiert von
                                    #17

                                    @glasfaser

                                    ja, ist noch so

                                    1 Antwort Letzte Antwort
                                    0
                                    • Thomas BraunT Thomas Braun

                                      @holger-etzel

                                      Extended PAN ID: configured=dadddddddddddddd, adapter=00124b0009d7fce3
                                      

                                      Muss/soll übereinstimmen. Im Adapter anpassen.

                                      Holger EtzelH Offline
                                      Holger EtzelH Offline
                                      Holger Etzel
                                      schrieb am zuletzt editiert von
                                      #18

                                      @thomas-braun
                                      woher kommt die Angabe des Adapters adapter=00124b0009d7fce3
                                      finde da nichts

                                      GlasfaserG 1 Antwort Letzte Antwort
                                      0
                                      • Holger EtzelH Holger Etzel

                                        @thomas-braun
                                        woher kommt die Angabe des Adapters adapter=00124b0009d7fce3
                                        finde da nichts

                                        GlasfaserG Offline
                                        GlasfaserG Offline
                                        Glasfaser
                                        schrieb am zuletzt editiert von
                                        #19

                                        @holger-etzel

                                        Steht ganz oben in deinem Log .

                                        Synology 918+ 16GB - ioBroker in Docker v9 , VISO auf Trekstor Primebook C13 13,3" , Hikvision Domkameras mit Surveillance Station .. CCU RaspberryMatic in Synology VM .. Zigbee CC2538+CC2592 .. Sonoff .. KNX .. Modbus ..

                                        1 Antwort Letzte Antwort
                                        0
                                        • Holger EtzelH Offline
                                          Holger EtzelH Offline
                                          Holger Etzel
                                          schrieb am zuletzt editiert von
                                          #20

                                          @thomas-braun
                                          wenn ich im Adapter die PAN ID auf dadddddddddddddd zu stellen kommt dann im LOG ddddddddddddddda und umgekehrt

                                          Thomas BraunT 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

                                          646

                                          Online

                                          32.7k

                                          Benutzer

                                          82.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