Navigation

    Logo
    • Register
    • Login
    • Search
    • Recent
    • Tags
    • Unread
    • Categories
    • Unreplied
    • Popular
    • GitHub
    • Docu
    • Hilfe
    1. Home
    2. Deutsch
    3. Hardware
    4. Einbindung CC2652RB (slaesh) in ioBroker unter Docker

    NEWS

    • Neuer Blog: Fotos und Eindrücke aus Solingen

    • ioBroker@Smart Living Forum Solingen, 14.06. - Agenda added

    • ioBroker goes Matter ... Matter Adapter in Stable

    Einbindung CC2652RB (slaesh) in ioBroker unter Docker

    This topic has been deleted. Only users with topic management privileges can see it.
    • M
      MrBean 0 last edited by MrBean 0

      Versuche mich gerade bei der Einrichtung vom USB-Stick unter ioBroker/Docker.

      Zum Host
      Ubuntu 20.04.2 LTS
      Docker 20.10.6

      Der Stick wird auf dem Host als USB1 erkannt. USB0 wird bereits verwendet

      ls -l /dev/ttyUSB1 
      crw-rw---- 1 root dialout 188, 1 Jun 12 19:42 /dev/ttyUSB1
      

      Hiermit wurde der Container erzeugt. Device USB1 und ENV sind gesetzt worden

      docker run --restart always --net=macvlan --ip=10.10.11.4 --name iobroker --hostname Test --device /dev/ttyUSB1:/dev/ttyUSB1 -e USBDEVICES=/dev/ttyUSB1 -v /daten/docker/iobroker:/opt/iobroker buanet/iobroker:latest
      

      Anschließend den Zigbee installiert und konfigurierten. Lasche EINSTELLUNGEN → COM-Anschlussname = /dev/ttyUSB1, Typ = TI Z-Stack/Ccxxxx, Rest unverändert gelassen.

      Dann den Adapter neu gestartet. Er bleibt gelb. Verbunden mit Host und Lebenszeichen sind wahr (grün). Verbunden mit zigbee ist falsch (rot)

      Log zeigt folgendes:

      2021-06-13 11:06:03.528 - info: host.Test stopInstance system.adapter.zigbee.0 (force=false, process=true)
      2021-06-13 11:06:03.530 - info: host.Test stopInstance system.adapter.zigbee.0 send kill signal
      2021-06-13 11:06:03.530 - info: zigbee.0 (4005) Got terminate signal TERMINATE_YOURSELF
      2021-06-13 11:06:03.531 - info: zigbee.0 (4005) cleaned everything up...
      2021-06-13 11:06:03.533 - info: zigbee.0 (4005) Zigbee: disabling joining new devices.
      2021-06-13 11:06:03.533 - warn: zigbee.0 (4005) Failed to stop zigbee during startup
      2021-06-13 11:06:03.534 - info: zigbee.0 (4005) terminating
      2021-06-13 11:06:03.534 - info: zigbee.0 (4005) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
      2021-06-13 11:06:03.534 - error: zigbee.0 (4005) Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().
      2021-06-13 11:06:03.534 - error: zigbee.0 (4005) unhandled promise rejection: Cannot read property 'getEntries' of null
      2021-06-13 11:06:03.535 - error: zigbee.0 (4005) TypeError: Cannot read property 'getEntries' of null
      at Function.loadFromDatabaseIfNecessary (/opt/iobroker/node_modules/zigbee-herdsman/dist/controller/model/device.js:220:55)
      at Function.all (/opt/iobroker/node_modules/zigbee-herdsman/dist/controller/model/device.js:240:16)
      at Controller.getDevices (/opt/iobroker/node_modules/zigbee-herdsman/dist/controller/controller.js:303:31)
      at ZigbeeController.getClients (/opt/iobroker/node_modules/iobroker.zigbee/lib/zigbeecontroller.js:228:49)
      at DeviceAvailability.stop (/opt/iobroker/node_modules/iobroker.zigbee/lib/zbDeviceAvailability.js:222:43)
      at ZigbeeController.callExtensionMethod (/opt/iobroker/node_modules/iobroker.zigbee/lib/zigbeecontroller.js:214:42)
      at ZigbeeController.stop (/opt/iobroker/node_modules/iobroker.zigbee/lib/zigbeecontroller.js:385:20)
      at Zigbee.onUnload (/opt/iobroker/node_modules/iobroker.zigbee/main.js:696:41)
      at processTicksAndRejections (internal/process/task_queues.js:97:5)
      2021-06-13 11:06:03.535 - error: zigbee.0 (4005) Cannot read property 'getEntries' of null
      2021-06-13 11:06:04.064 - info: host.Test instance system.adapter.zigbee.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
      2021-06-13 11:06:06.541 - info: host.Test instance system.adapter.zigbee.0 started with pid 4046
      2021-06-13 11:06:07.317 - info: zigbee.0 (4046) starting. Version 1.5.6 in /opt/iobroker/node_modules/iobroker.zigbee, node: v12.22.1, js-controller: 3.2.16
      2021-06-13 11:06:07.338 - info: zigbee.0 (4046) Starting Zigbee npm ...
      2021-06-13 11:06:07.429 - info: zigbee.0 (4046) Installed Version: iobroker.zigbee@1.5.6
      

      Das ist meine erste Einrichtung vom USB Stick unter ioBroker in Docker.

      Kann mir einer helfen?

      Nachtrag
      Das sehe ich auch noch in der Log Datei

      Starting zigbee-herdsman problem : "Error while opening serialport 'Error: Error Resource temporarily unavailable Cannot lock port'"
      

      Nachtrag 2
      Der USB Stick CC2531 wird sofort erkannt. (Mit /dev/ttyACM0)

      Asgothian 1 Reply Last reply Reply Quote 0
      • Asgothian
        Asgothian Developer @MrBean 0 last edited by

        @mrbean-0

        Leider ist die entscheidende Nachricht in deinem Log nicht zu erkennen. Die Fehlermeldung(en) die du gepostet hast sind wahrscheinlich nur Folgefehler eines initialen Fehlers.

        Es gibt 2 Optionen dem auf den Grund zu gehen:

        Option A:

        • Zigbee Adapter anhalten
        • aktuelles Log löschen
        • Zigbee Adapter starten
        • nach 30 Sekunden Zigbee Adapter anhalten
        • Log herunterladen und posten.

        Option B:

        Testweise den Adapter von meinem Test-Branch installieren:
        https://github.com/asgothian/ioBroker.zigbee/tarball/LatestHerdsman
        Log des Startes des Adapters posten. Eine der Anpassungen die durch diesen Branch in den Adapter kommen ist das die 'fehlerhaften' Fehlermeldungen beim stoppen des Adapters unterbleiben sollten.

        A.

        1 Reply Last reply Reply Quote 0
        • M
          MrBean 0 last edited by

          @asgothian
          Hallo, wähle die Option A aus, da sie einfacher ist

          Um 13:29:00 habe ich den Adapter gestartet und um 13:29:30 beendet. Wie gewünscht die Log

          2021-06-20 13:29:02.046 - info: host.Test "system.adapter.zigbee.0" enabled
          2021-06-20 13:29:02.056 - info: host.Test instance system.adapter.zigbee.0 started with pid 1551
          2021-06-20 13:29:02.832 - info: zigbee.0 (1551) starting. Version 1.5.6 in /opt/iobroker/node_modules/iobroker.zigbee, node: v12.22.1, js-controller: 3.2.16
          2021-06-20 13:29:02.852 - info: zigbee.0 (1551) Starting Zigbee npm ...
          2021-06-20 13:29:02.942 - info: zigbee.0 (1551) Installed Version: iobroker.zigbee@1.5.6
          2021-06-20 13:29:32.026 - info: host.Test "system.adapter.zigbee.0" disabled
          2021-06-20 13:29:32.026 - info: host.Test stopInstance system.adapter.zigbee.0 (force=false, process=true)
          2021-06-20 13:29:32.028 - info: host.Test stopInstance system.adapter.zigbee.0 send kill signal
          2021-06-20 13:29:32.029 - info: zigbee.0 (1551) Got terminate signal TERMINATE_YOURSELF
          2021-06-20 13:29:32.030 - info: zigbee.0 (1551) cleaned everything up...
          2021-06-20 13:29:32.032 - info: zigbee.0 (1551) Zigbee: disabling joining new devices.
          2021-06-20 13:29:32.033 - warn: zigbee.0 (1551) Failed to stop zigbee during startup
          2021-06-20 13:29:32.033 - info: zigbee.0 (1551) terminating
          2021-06-20 13:29:32.034 - info: zigbee.0 (1551) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
          2021-06-20 13:29:32.034 - error: zigbee.0 (1551) Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().
          2021-06-20 13:29:32.035 - error: zigbee.0 (1551) unhandled promise rejection: Cannot read property 'getEntries' of null
          2021-06-20 13:29:32.036 - error: zigbee.0 (1551) TypeError: Cannot read property 'getEntries' of null
          at Function.loadFromDatabaseIfNecessary (/opt/iobroker/node_modules/zigbee-herdsman/dist/controller/model/device.js:220:55)
          at Function.all (/opt/iobroker/node_modules/zigbee-herdsman/dist/controller/model/device.js:240:16)
          at Controller.getDevices (/opt/iobroker/node_modules/zigbee-herdsman/dist/controller/controller.js:303:31)
          at ZigbeeController.getClients (/opt/iobroker/node_modules/iobroker.zigbee/lib/zigbeecontroller.js:228:49)
          at DeviceAvailability.stop (/opt/iobroker/node_modules/iobroker.zigbee/lib/zbDeviceAvailability.js:222:43)
          at ZigbeeController.callExtensionMethod (/opt/iobroker/node_modules/iobroker.zigbee/lib/zigbeecontroller.js:214:42)
          at ZigbeeController.stop (/opt/iobroker/node_modules/iobroker.zigbee/lib/zigbeecontroller.js:385:20)
          at Zigbee.onUnload (/opt/iobroker/node_modules/iobroker.zigbee/main.js:696:41)
          at processTicksAndRejections (internal/process/task_queues.js:97:5)
          2021-06-20 13:29:32.036 - error: zigbee.0 (1551) Cannot read property 'getEntries' of null
          2021-06-20 13:29:32.565 - info: host.Test instance system.adapter.zigbee.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
          

          Um die Funktion des Sticks zu prüfen, habe ich den Container "koenkk/zigbee2mqtt" installiert. Stick wird erkannt und konnte auch zwei Zigbee Geräte anlernen.

          Könnte ich auch die Kombination Docker "koenkk/zigbee2mqtt" & ioBroker "MQTT Broker/Client "verwenden. Hat das Vorteile/Nachteile zur oben genannten Variante?

          Asgothian 1 Reply Last reply Reply Quote 0
          • Asgothian
            Asgothian Developer @MrBean 0 last edited by

            @mrbean-0 sagte in Einbindung CC2652RB (slaesh) in ioBroker unter Docker:

            @asgothian
            Hallo, wähle die Option A aus, da sie einfacher ist

            Um 13:29:00 habe ich den Adapter gestartet und um 13:29:30 beendet. Wie gewünscht die Log

            2021-06-20 13:29:02.046 - info: host.Test "system.adapter.zigbee.0" enabled
            2021-06-20 13:29:02.056 - info: host.Test instance system.adapter.zigbee.0 started with pid 1551
            2021-06-20 13:29:02.832 - info: zigbee.0 (1551) starting. Version 1.5.6 in /opt/iobroker/node_modules/iobroker.zigbee, node: v12.22.1, js-controller: 3.2.16
            2021-06-20 13:29:02.852 - info: zigbee.0 (1551) Starting Zigbee npm ...
            2021-06-20 13:29:02.942 - info: zigbee.0 (1551) Installed Version: iobroker.zigbee@1.5.6
            2021-06-20 13:29:32.026 - info: host.Test "system.adapter.zigbee.0" disabled
            2021-06-20 13:29:32.026 - info: host.Test stopInstance system.adapter.zigbee.0 (force=false, process=true)
            2021-06-20 13:29:32.028 - info: host.Test stopInstance system.adapter.zigbee.0 send kill signal
            2021-06-20 13:29:32.029 - info: zigbee.0 (1551) Got terminate signal TERMINATE_YOURSELF
            2021-06-20 13:29:32.030 - info: zigbee.0 (1551) cleaned everything up...
            2021-06-20 13:29:32.032 - info: zigbee.0 (1551) Zigbee: disabling joining new devices.
            2021-06-20 13:29:32.033 - warn: zigbee.0 (1551) Failed to stop zigbee during startup
            2021-06-20 13:29:32.033 - info: zigbee.0 (1551) terminating
            2021-06-20 13:29:32.034 - info: zigbee.0 (1551) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
            2021-06-20 13:29:32.034 - error: zigbee.0 (1551) Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().
            2021-06-20 13:29:32.035 - error: zigbee.0 (1551) unhandled promise rejection: Cannot read property 'getEntries' of null
            2021-06-20 13:29:32.036 - error: zigbee.0 (1551) TypeError: Cannot read property 'getEntries' of null
            at Function.loadFromDatabaseIfNecessary (/opt/iobroker/node_modules/zigbee-herdsman/dist/controller/model/device.js:220:55)
            at Function.all (/opt/iobroker/node_modules/zigbee-herdsman/dist/controller/model/device.js:240:16)
            at Controller.getDevices (/opt/iobroker/node_modules/zigbee-herdsman/dist/controller/controller.js:303:31)
            at ZigbeeController.getClients (/opt/iobroker/node_modules/iobroker.zigbee/lib/zigbeecontroller.js:228:49)
            at DeviceAvailability.stop (/opt/iobroker/node_modules/iobroker.zigbee/lib/zbDeviceAvailability.js:222:43)
            at ZigbeeController.callExtensionMethod (/opt/iobroker/node_modules/iobroker.zigbee/lib/zigbeecontroller.js:214:42)
            at ZigbeeController.stop (/opt/iobroker/node_modules/iobroker.zigbee/lib/zigbeecontroller.js:385:20)
            at Zigbee.onUnload (/opt/iobroker/node_modules/iobroker.zigbee/main.js:696:41)
            at processTicksAndRejections (internal/process/task_queues.js:97:5)
            2021-06-20 13:29:32.036 - error: zigbee.0 (1551) Cannot read property 'getEntries' of null
            2021-06-20 13:29:32.565 - info: host.Test instance system.adapter.zigbee.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
            

            Um die Funktion des Sticks zu prüfen, habe ich den Container "koenkk/zigbee2mqtt" installiert. Stick wird erkannt und konnte auch zwei Zigbee Geräte anlernen.

            Könnte ich auch die Kombination Docker "koenkk/zigbee2mqtt" & ioBroker "MQTT Broker/Client "verwenden. Hat das Vorteile/Nachteile zur oben genannten Variante?

            Offensichtlich braucht dein System länger als 30 Sekunden. Bitte den Test wiederholen, dabei 3 Minuten warten bevor du den Zigbee Adapter anhältst.
            Du kannst auch zigbee2mqtt und mqtt adapter nutzen, allerdings ist da die Einbindung der Geräte komplexer, da du die Nachrichten zum steuern von Hand selber zusammen bauen musst.

            A.

            M 2 Replies Last reply Reply Quote 0
            • M
              MrBean 0 @Asgothian last edited by

              @asgothian

              Gestartet um 13:54:00 und um 13:57:00 beendet

              2021-06-20 13:54:02.193 - info: host.Test "system.adapter.zigbee.0" enabled
              2021-06-20 13:54:02.203 - info: host.Test instance system.adapter.zigbee.0 started with pid 2769
              2021-06-20 13:54:02.978 - info: zigbee.0 (2769) starting. Version 1.5.6 in /opt/iobroker/node_modules/iobroker.zigbee, node: v12.22.1, js-controller: 3.2.16
              2021-06-20 13:54:02.997 - info: zigbee.0 (2769) Starting Zigbee npm ...
              2021-06-20 13:54:03.087 - info: zigbee.0 (2769) Installed Version: iobroker.zigbee@1.5.6
              2021-06-20 13:55:15.980 - error: zigbee.0 (2769) Starting zigbee-herdsman problem : "network commissioning timed out - most likely network with the same panId or extendedPanId already exists nearby"
              2021-06-20 13:55:15.981 - error: zigbee.0 (2769) Failed to start Zigbee
              2021-06-20 13:55:15.981 - error: zigbee.0 (2769) Error herdsman start
              2021-06-20 13:55:25.983 - info: zigbee.0 (2769) Try to reconnect. 1 attempts left
              2021-06-20 13:55:25.984 - info: zigbee.0 (2769) Starting Zigbee npm ...
              2021-06-20 13:55:25.993 - info: zigbee.0 (2769) Installed Version: iobroker.zigbee@1.5.6
              2021-06-20 13:55:26.084 - error: zigbee.0 (2769) Starting zigbee-herdsman problem : "Error while opening serialport 'Error: Error Resource temporarily unavailable Cannot lock port'"
              2021-06-20 13:55:26.084 - error: zigbee.0 (2769) Failed to start Zigbee
              2021-06-20 13:55:26.084 - error: zigbee.0 (2769) Error herdsman start
              2021-06-20 13:57:01.756 - info: host.Test "system.adapter.zigbee.0" disabled
              2021-06-20 13:57:01.756 - info: host.Test stopInstance system.adapter.zigbee.0 (force=false, process=true)
              2021-06-20 13:57:01.758 - info: host.Test stopInstance system.adapter.zigbee.0 send kill signal
              2021-06-20 13:57:01.758 - info: zigbee.0 (2769) Got terminate signal TERMINATE_YOURSELF
              2021-06-20 13:57:01.759 - info: zigbee.0 (2769) cleaned everything up...
              2021-06-20 13:57:01.761 - info: zigbee.0 (2769) Zigbee: disabling joining new devices.
              2021-06-20 13:57:01.762 - warn: zigbee.0 (2769) Failed to stop zigbee during startup
              2021-06-20 13:57:01.763 - info: zigbee.0 (2769) terminating
              2021-06-20 13:57:01.763 - info: zigbee.0 (2769) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
              2021-06-20 13:57:01.764 - error: zigbee.0 (2769) Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().
              2021-06-20 13:57:01.764 - error: zigbee.0 (2769) unhandled promise rejection: Cannot read property 'getEntries' of null
              2021-06-20 13:57:01.765 - error: zigbee.0 (2769) TypeError: Cannot read property 'getEntries' of null
              at Function.loadFromDatabaseIfNecessary (/opt/iobroker/node_modules/zigbee-herdsman/dist/controller/model/device.js:220:55)
              at Function.all (/opt/iobroker/node_modules/zigbee-herdsman/dist/controller/model/device.js:240:16)
              at Controller.getDevices (/opt/iobroker/node_modules/zigbee-herdsman/dist/controller/controller.js:303:31)
              at ZigbeeController.getClients (/opt/iobroker/node_modules/iobroker.zigbee/lib/zigbeecontroller.js:228:49)
              at DeviceAvailability.stop (/opt/iobroker/node_modules/iobroker.zigbee/lib/zbDeviceAvailability.js:222:43)
              at ZigbeeController.callExtensionMethod (/opt/iobroker/node_modules/iobroker.zigbee/lib/zigbeecontroller.js:214:42)
              at ZigbeeController.stop (/opt/iobroker/node_modules/iobroker.zigbee/lib/zigbeecontroller.js:385:20)
              at Zigbee.onUnload (/opt/iobroker/node_modules/iobroker.zigbee/main.js:696:41)
              at processTicksAndRejections (internal/process/task_queues.js:97:5)
              2021-06-20 13:57:01.765 - error: zigbee.0 (2769) Cannot read property 'getEntries' of null
              2021-06-20 13:57:02.296 - info: host.Test instance system.adapter.zigbee.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
              
              1 Reply Last reply Reply Quote 0
              • M
                MrBean 0 @Asgothian last edited by

                @asgothian
                In der Log steht es

                2021-06-20 13:55:15.980 - error: zigbee.0 (2769) Starting zigbee-herdsman problem : "network commissioning timed out - most likely network with the same panId or extendedPanId already exists nearby"
                

                Habe beides geändert. Dann wird der Adapter auch grün

                Danke für deine Hilfe

                P.S. Habe noch ein zweites Zigbee Netz am gleichen Rechner mit fhem. Möchte langsam von fhem nach ioBroker wechseln. Daher zwei Zigbee Adapter/Netze.

                Asgothian 1 Reply Last reply Reply Quote 0
                • Asgothian
                  Asgothian Developer @MrBean 0 last edited by

                  @mrbean-0 ist es möglich das ein anderes zigbee Netz mit den gleichen netzwerkparametn existiert (panID, Kanal, ExtPan ID ?)

                  A.

                  M 1 Reply Last reply Reply Quote 0
                  • M
                    MrBean 0 @Asgothian last edited by

                    @asgothian
                    wäre Denkbar. Das fhem Zigbee Netz...

                    Asgothian 1 Reply Last reply Reply Quote 0
                    • Asgothian
                      Asgothian Developer @MrBean 0 last edited by

                      @mrbean-0
                      Dann gib dem zigbee Adapter doch mal komplett andere Werte.

                      A.

                      1 Reply Last reply Reply Quote 0
                      • M
                        MrBean 0 last edited by

                        @asgothian
                        habe gestern panId und extendedPanId schon geändert, nachdem ich im
                        log die oben genannte Fehlermeldung gesehen habe. Danach wurde der Adapter sofort grün.

                        Asgothian 1 Reply Last reply Reply Quote 0
                        • Asgothian
                          Asgothian Developer @MrBean 0 last edited by

                          @mrbean-0 Fein. Und sorry - ich hatte die weiteren Posts nicht gesehen und nur auf den mit dem Log reagiert. Gestern war es einfach zu heiss.

                          A.

                          M 1 Reply Last reply Reply Quote 0
                          • M
                            MrBean 0 @Asgothian last edited by

                            @asgothian
                            Kein Problem

                            Nochmal Danke

                            1 Reply Last reply Reply Quote 0
                            • First post
                              Last post

                            Support us

                            ioBroker
                            Community Adapters
                            Donate

                            855
                            Online

                            31.8k
                            Users

                            80.0k
                            Topics

                            1.3m
                            Posts

                            2
                            12
                            1034
                            Loading More Posts
                            • Oldest to Newest
                            • Newest to Oldest
                            • Most Votes
                            Reply
                            • Reply as topic
                            Log in to reply
                            Community
                            Impressum | Datenschutz-Bestimmungen | Nutzungsbedingungen
                            The ioBroker Community 2014-2023
                            logo