Navigation

    Logo
    • Register
    • Login
    • Search
    • Recent
    • Tags
    • Unread
    • Categories
    • Unreplied
    • Popular
    • GitHub
    • Docu
    • Hilfe
    1. Home
    2. Deutsch
    3. ioBroker Allgemein
    4. Fehlersuche?traeges Verhalten/Zigbee/IKEA/Blockly

    NEWS

    • Neues Video "KI im Smart Home" - ioBroker plus n8n

    • Neues Video über Aliase, virtuelle Geräte und Kategorien

    • Wir empfehlen: Node.js 22.x

    Fehlersuche?traeges Verhalten/Zigbee/IKEA/Blockly

    This topic has been deleted. Only users with topic management privileges can see it.
    • Asgothian
      Asgothian Developer @Fred Freund last edited by

      @fred-freund
      Das ist nicht unbedingt so seltsam.

      • Funkwellenausbreitung ist nicht "linear". Insbesondere innerhalb von Räumen gibt es durch die Wellenausbreitung immer wieder Bereiche wo der Abstand vom Sender nicht direkt mit der Feldstärke korreliert.
      • Das Gunnarp ist mit seinem Metallaufbau und dem darin verbauten Trafo denkbar ungünstig und kann daher deutlich schlechteren Empfang haben als ein weiter entfernt aber frei zugängliches Gerät.

      A.

      Fred Freund 1 Reply Last reply Reply Quote 0
      • Fred Freund
        Fred Freund @Asgothian last edited by Fred Freund

        @asgothian
        Hi, ja scheint so das es so empfindlich ist.
        Ich habe mich mit ZIgbee Kanal Auswahl
        beschaeftigt und Kanal26 zum testen genommen. Da heute NICHTS MEHR GING und ALLES Status FALSE hatte

        Nach Aenderung wurden auch die Schalter gefunden jedoch wird nach Absturz der Adapter Zigbee nurmehr Gelb.
        und beim Oeffnen schreibt er mir :
        You need to save and run adapter before pairing.
        Die Serielle Auswahl passt hat er ja schon gefunden etc.
        Sollte ich etwas aendern schreibt er mir
        Some data are not stored, Discard?
        Habe den Adapter schon geloescht , rebooted das selbe Problem.

        Also : ein Shutdown und POWER OFF loeste das Adapter problem , mal sehen ob er wieder Probleme macht.

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

          @fred-freund sagte in Fehlersuche?traeges Verhalten/Zigbee/IKEA/Blockly:

          Also : ein Shutdown und POWER OFF loeste das Adapter problem , mal sehen ob er wieder Probleme macht.

          Wenn so etwas passiert musst du im Log nachschauen was für Meldungen vorhanden sind. Das Log meldet im Normalfall recht genau weswegen die Hardware nicht startet.

          A.

          Fred Freund 1 Reply Last reply Reply Quote 0
          • Fred Freund
            Fred Freund @Asgothian last edited by Fred Freund

            @asgothian

            2021-03-13 16:11:31.035  - info: zigbee.0 (1244) Currently no devices.
            2021-03-13 16:11:31.036  - info: zigbee.0 (1244) Zigbee started
            2021-03-13 16:11:44.136  - info: zigbee.0 (1244) Zigbee: allowing new devices to join.
            2021-03-13 16:12:05.076  - info: zigbee.0 (1244) Starting interview of '0x5c0272fffe997f78'
            2021-03-13 16:12:07.331  - warn: zigbee.0 (1244) Device '0x5c0272fffe997f78' announced itself
            2021-03-13 16:12:45.446  - info: zigbee.0 (1244) Zigbee: stop joining
            2021-03-13 16:12:46.687  - info: zigbee.0 (1244) Successfully interviewed '0x5c0272fffe997f78', device has succesfully been paired
            2021-03-13 16:12:46.688  - info: zigbee.0 (1244) Device '0x5c0272fffe997f78' is supported, identified as: IKEA TRADFRI motion sensor (E1525/E1745)
            2021-03-13 16:12:46.692  - info: zigbee.0 (1244) Configuring 0x5c0272fffe997f78 TRADFRI motion sensor
            2021-03-13 16:12:53.918  - info: zigbee.0 (1244) DeviceConfigure successful 0x5c0272fffe997f78 TRADFRI motion sensor
            2021-03-13 16:14:55.652  - info: zigbee.0 (1244) Zigbee: allowing new devices to join.
            2021-03-13 16:15:21.445  - info: zigbee.0 (1244) Starting interview of '0x60a423fffeeecd67'
            2021-03-13 16:15:24.855  - warn: zigbee.0 (1244) Device '0x60a423fffeeecd67' announced itself
            2021-03-13 16:15:28.299  - error: zigbee.0 (1244) Adapter disconnected, stopping
            2021-03-13 16:15:31.507  - error: zigbee.0 (1244) Failed to interview '0x60a423fffeeecd67', device has not succesfully been paired. undefined
            2021-03-13 16:15:38.301  - info: zigbee.0 (1244) Try to reconnect. 5 attempts left
            2021-03-13 16:15:38.303  - info: zigbee.0 (1244) Starting Zigbee  npm ...
            2021-03-13 16:15:38.312  - error: zigbee.0 (1244) Failed to start Zigbee
            2021-03-13 16:15:38.313  - error: zigbee.0 (1244) Error: Error while opening serialport 'Error: Error: No such file or directory, cannot open /dev/ttyACM1'
                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
            2021-03-13 16:15:38.324  - info: zigbee.0 (1244) Installed Version: ioBroker/ioBroker.zigbee#47e641cb8ec3756b16e5b7ff817fbf93502e295d
            2021-03-13 16:15:48.315  - info: zigbee.0 (1244) Try to reconnect. 4 attempts left
            2021-03-13 16:15:48.317  - info: zigbee.0 (1244) Starting Zigbee  npm ...
            2021-03-13 16:15:48.325  - error: zigbee.0 (1244) Failed to start Zigbee
            2021-03-13 16:15:48.326  - error: zigbee.0 (1244) Error: Error while opening serialport 'Error: Error: No such file or directory, cannot open /dev/ttyACM1'
                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
            2021-03-13 16:15:48.331  - info: zigbee.0 (1244) Installed Version: ioBroker/ioBroker.zigbee#47e641cb8ec3756b16e5b7ff817fbf93502e295d
            2021-03-13 16:15:56.906  - info: zigbee.0 (1244) Zigbee: stop joining
            2021-03-13 16:15:56.910  - error: zigbee.0 (1244) 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-03-13 16:15:56.911  - error: zigbee.0 (1244) unhandled promise rejection: Cannot request when znp has not been initialized yet
            2021-03-13 16:15:56.913  - error: zigbee.0 (1244) Error: Cannot request when znp has not been initialized yet
                at Znp.request (/opt/iobroker/node_modules/zigbee-herdsman/dist/adapter/z-stack/znp/znp.js:273:19)
                at ZStackAdapter.<anonymous> (/opt/iobroker/node_modules/zigbee-herdsman/dist/adapter/z-stack/adapter/zStackAdapter.js:808:28)
                at Generator.next (<anonymous>)
                at /opt/iobroker/node_modules/zigbee-herdsman/dist/adapter/z-stack/adapter/zStackAdapter.js:27:71
                at new Promise (<anonymous>)
                at __awaiter (/opt/iobroker/node_modules/zigbee-herdsman/dist/adapter/z-stack/adapter/zStackAdapter.js:23:12)
                at ZStackAdapter.dataRequestExtended (/opt/iobroker/node_modules/zigbee-herdsman/dist/adapter/z-stack/adapter/zStackAdapter.js:804:16)
                at ZStackAdapter.<anonymous> (/opt/iobroker/node_modules/zigbee-herdsman/dist/adapter/z-stack/adapter/zStackAdapter.js:453:28)
                at Generator.next (<anonymous>)
                at /opt/iobroker/node_modules/zigbee-herdsman/dist/adapter/z-stack/adapter/zStackAdapter.js:27:71
            2021-03-13 16:15:56.913  - error: zigbee.0 (1244) Cannot request when znp has not been initialized yet
            2021-03-13 16:15:56.963  - info: zigbee.0 (1244) cleaned everything up...
            2021-03-13 16:15:56.966  - info: zigbee.0 (1244) Zigbee: disabling joining new devices.
            2021-03-13 16:15:56.976  - error: zigbee.0 (1244) Failed to stop zigbee (Error: Cannot request when znp has not been initialized yet
                at Znp.request (/opt/iobroker/node_modules/zigbee-herdsman/dist/adapter/z-stack/znp/znp.js:273:19)
                at ZStackAdapter.<anonymous> (/opt/iobroker/node_modules/zigbee-herdsman/dist/adapter/z-stack/adapter/zStackAdapter.js:808:28)
                at Generator.next (<anonymous>)
                at /opt/iobroker/node_modules/zigbee-herdsman/dist/adapter/z-stack/adapter/zStackAdapter.js:27:71
                at new Promise (<anonymous>)
                at __awaiter (/opt/iobroker/node_modules/zigbee-herdsman/dist/adapter/z-stack/adapter/zStackAdapter.js:23:12)
                at ZStackAdapter.dataRequestExtended (/opt/iobroker/node_modules/zigbee-herdsman/dist/adapter/z-stack/adapter/zStackAdapter.js:804:16)
                at ZStackAdapter.<anonymous> (/opt/iobroker/node_modules/zigbee-herdsman/dist/adapter/z-stack/adapter/zStackAdapter.js:453:28)
                at Generator.next (<anonymous>)
                at /opt/iobroker/node_modules/zigbee-herdsman/dist/adapter/z-stack/adapter/zStackAdapter.js:27:71)
            2021-03-13 16:15:56.978  - info: zigbee.0 (1244) terminating
            2021-03-13 16:15:56.980  - warn: zigbee.0 (1244) Terminated (UNCAUGHT_EXCEPTION): Without reason
            2021-03-13 16:15:57.572  - error: host.broker1 instance system.adapter.zigbee.0 terminated with code 6 (UNCAUGHT_EXCEPTION)
            2021-03-13 16:15:57.577  - info: host.broker1 Restart adapter system.adapter.zigbee.0 because enabled
            2021-03-13 16:16:27.624  - info: host.broker1 instance system.adapter.zigbee.0 started with pid 1320
            2021-03-13 16:16:29.882  - info: zigbee.0 (1320) starting. Version 1.4.5 in /opt/iobroker/node_modules/iobroker.zigbee, node: v12.21.0, js-controller: 3.2.16
            2021-03-13 16:16:29.974  - info: zigbee.0 (1320) Starting Zigbee  npm ...
            2021-03-13 16:16:30.193  - error: zigbee.0 (1320) Failed to start Zigbee
            2021-03-13 16:16:30.194  - error: zigbee.0 (1320) Error: Error while opening serialport 'Error: Error: No such file or directory, cannot open /dev/ttyACM1'
                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
            2021-03-13 16:16:30.255  - info: zigbee.0 (1320) Installed Version: ioBroker/ioBroker.zigbee#47e641cb8ec3756b16e5b7ff817fbf93502e295d
            2021-03-13 16:16:40.195  - info: zigbee.0 (1320) Try to reconnect. 1 attempts left
            2021-03-13 16:16:40.196  - info: zigbee.0 (1320) Starting Zigbee  npm ...
            2021-03-13 16:16:40.201  - error: zigbee.0 (1320) Failed to start Zigbee
            2021-03-13 16:16:40.202  - error: zigbee.0 (1320) Error: Error while opening serialport 'Error: Error: No such file or directory, cannot open /dev/ttyACM1'
                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
            2021-03-13 16:16:40.205  - info: zigbee.0 (1320) Installed Version: ioBroker/ioBroker.zigbee#47e641cb8ec3756b16e5b7ff817fbf93502e295d
            

            Das passiert beim anlernen der Gunnarp Lampe ...
            Motion Sensor hat kein Problem gemacht..

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

              @fred-freund Dir ist die serielle Schnittstelle abgestürzt.

              2021-03-13 16:15:28.299  - error: zigbee.0 (1244) Adapter disconnected, stopping
              

              Das ist ein Hinweis darauf das er die Kommunikation zum Zigbee-Stick verloren hat.

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

              Diese Meldung besagt das der link zum seriellen Port nicht existiert.

              Da gibt es also ein problem mit dem Rechner an dem das steckt oder der Firmware / Hardware auf dem Koordinator.

              A.

              Fred Freund 1 Reply Last reply Reply Quote 0
              • Fred Freund
                Fred Freund @Asgothian last edited by Fred Freund

                @asgothian
                Interpretiere ich den Scan richtig dort wo nichts ist waere der beste Kanal?
                6db6f738-7261-46e7-bc9d-98b3d9c5995e-image.png

                Also software reset habe ich keinen gefunden, aber aus einstecken des cc2531 funktioniert auch...
                ttyACM1 ist dann wieder da

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

                  @fred-freund Ja, das sind die "leeren" Kanäle. Allerdings musst du mit den nicht ZLL Kanälen (ZLL Kanäle sind 11,15,20,26) Vorsichtig sein, nicht alle Geräte laufen darauf

                  Fred Freund 1 Reply Last reply Reply Quote 0
                  • Fred Freund
                    Fred Freund @Asgothian last edited by Fred Freund

                    @asgothian
                    Habe jetzt mal den 26er Kanal genommen...die Switches und Bewegungsmelder Tradfir werden identifiziert und funktionieren.
                    Die Lampen geben diesen Error und dann steigt der CC2531 aus.
                    Nach dem reboot ist nur
                    99bc5c2d-781f-4786-bb12-d781b0a52fe1-image.png
                    zu sehen.
                    Beim Speicher bekomme ich immer diese Meldung:
                    a69e153b-c280-47bb-b04e-1acf650d3c3c-image.png

                    Hoffe Dienstag ist es besser mit cc26xr21

                    Also default war 11 eingestellt das hat recht gut funktioniert , momentan geht garnichts 🙂 und Schalte und BM ohne Lampen machen keinen Sinn 🙂

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

                      @fred-freund
                      Wie schon oben beschrieben.. Interessant ist was im log steht.

                      A.

                      Fred Freund 1 Reply Last reply Reply Quote 0
                      • Fred Freund
                        Fred Freund @Asgothian last edited by Fred Freund

                        @asgothian

                        das nicht vollstaendige Geraet laesst sich auch nicht loeschen...

                        Also adapter gloescht neu , usb
                        /dev/serial/by-id/usb-Texas_Instruments_TI_CC2531_USB_CDC___0X00124B001CD48243-if00

                        2021-03-13 22:05:28.885  - error: zigbee.0 (1280) Serial port not selected! Go to settings page.
                        2021-03-13 22:05:28.942  - info: zigbee.0 (1280) Starting Zigbee  npm ...
                        2021-03-13 22:05:29.239  - info: zigbee.0 (1280) Installed Version: ioBroker/ioBroker.zigbee#47e641cb8ec3756b16e5b7ff817fbf93502e295d
                        2021-03-13 22:05:31.251  - info: zigbee.0 (1280) Coordinator firmware version: {"type":"zStack12","meta":{"transportrev":2,"product":0,"majorrel":2,"minorrel":6,"maintrel":3,"revision":20190608}}
                        2021-03-13 22:05:31.263  - info: zigbee.0 (1280)   --> transmitPower : normal
                        2021-03-13 22:05:31.272  - info: zigbee.0 (1280) Currently no devices.
                        2021-03-13 22:05:31.274  - info: zigbee.0 (1280) Zigbee started
                        2021-03-13 22:08:06.054  - info: host.broker1 stopInstance system.adapter.zigbee.0 (force=false, process=true)
                        2021-03-13 22:08:06.065  - info: zigbee.0 (1280) Got terminate signal TERMINATE_YOURSELF
                        2021-03-13 22:08:06.067  - info: host.broker1 stopInstance system.adapter.zigbee.0 send kill signal
                        2021-03-13 22:08:06.069  - info: zigbee.0 (1280) cleaned everything up...
                        2021-03-13 22:08:06.074  - info: zigbee.0 (1280) Zigbee: disabling joining new devices.
                        2021-03-13 22:08:06.331  - info: zigbee.0 (1280) terminating
                        2021-03-13 22:08:06.333  - info: zigbee.0 (1280) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
                        2021-03-13 22:08:06.973  - info: host.broker1 instance system.adapter.zigbee.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
                        2021-03-13 22:08:09.116  - info: host.broker1 instance system.adapter.zigbee.0 started with pid 1327
                        2021-03-13 22:08:11.470  - info: zigbee.0 (1327) starting. Version 1.4.5 in /opt/iobroker/node_modules/iobroker.zigbee, node: v12.21.0, js-controller: 3.2.16
                        2021-03-13 22:08:11.564  - info: zigbee.0 (1327) Starting Zigbee  npm ...
                        2021-03-13 22:08:11.892  - info: zigbee.0 (1327) Installed Version: ioBroker/ioBroker.zigbee#47e641cb8ec3756b16e5b7ff817fbf93502e295d
                        2021-03-13 22:08:19.630  - info: zigbee.0 (1327) Coordinator firmware version: {"type":"zStack12","meta":{"transportrev":2,"product":0,"majorrel":2,"minorrel":6,"maintrel":3,"revision":20190608}}
                        2021-03-13 22:08:19.644  - info: zigbee.0 (1327)   --> transmitPower : normal
                        2021-03-13 22:08:19.653  - info: zigbee.0 (1327) Currently no devices.
                        2021-03-13 22:08:19.655  - info: zigbee.0 (1327) Zigbee started
                        2021-03-13 22:08:56.483  - info: host.broker1 stopInstance system.adapter.zigbee.0 (force=false, process=true)
                        2021-03-13 22:08:56.524  - info: zigbee.0 (1327) Got terminate signal TERMINATE_YOURSELF
                        2021-03-13 22:08:56.525  - info: host.broker1 stopInstance system.adapter.zigbee.0 send kill signal
                        2021-03-13 22:08:56.526  - info: zigbee.0 (1327) cleaned everything up...
                        2021-03-13 22:08:56.528  - info: zigbee.0 (1327) Zigbee: disabling joining new devices.
                        2021-03-13 22:08:56.774  - info: zigbee.0 (1327) terminating
                        2021-03-13 22:08:56.776  - info: zigbee.0 (1327) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
                        2021-03-13 22:08:57.444  - info: host.broker1 instance system.adapter.zigbee.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
                        2021-03-13 22:08:59.587  - info: host.broker1 instance system.adapter.zigbee.0 started with pid 1357
                        2021-03-13 22:09:01.965  - info: zigbee.0 (1357) starting. Version 1.4.5 in /opt/iobroker/node_modules/iobroker.zigbee, node: v12.21.0, js-controller: 3.2.16
                        2021-03-13 22:09:02.068  - info: zigbee.0 (1357) Starting Zigbee  npm ...
                        2021-03-13 22:09:02.365  - info: zigbee.0 (1357) Installed Version: ioBroker/ioBroker.zigbee#47e641cb8ec3756b16e5b7ff817fbf93502e295d
                        2021-03-13 22:09:09.651  - info: zigbee.0 (1357) Coordinator firmware version: {"type":"zStack12","meta":{"transportrev":2,"product":0,"majorrel":2,"minorrel":6,"maintrel":3,"revision":20190608}}
                        2021-03-13 22:09:09.664  - info: zigbee.0 (1357)   --> transmitPower : normal
                        2021-03-13 22:09:09.673  - info: zigbee.0 (1357) Currently no devices.
                        2021-03-13 22:09:09.675  - info: zigbee.0 (1357) Zigbee started
                        2021-03-13 22:09:21.759  - info: zigbee.0 (1357) Zigbee: allowing new devices to join.
                        2021-03-13 22:09:47.509  - info: zigbee.0 (1357) Starting interview of '0x60a423fffeeecd67'
                        2021-03-13 22:09:50.919  - warn: zigbee.0 (1357) Device '0x60a423fffeeecd67' announced itself
                        2021-03-13 22:10:23.059  - info: zigbee.0 (1357) Zigbee: stop joining
                        2021-03-13 22:10:33.542  - error: zigbee.0 (1357) 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-03-13 22:10:33.544  - error: zigbee.0 (1357) unhandled promise rejection: SRSP - AF - dataRequestExt after 6000ms
                        2021-03-13 22:10:33.546  - error: zigbee.0 (1357) Error: SRSP - AF - dataRequestExt after 6000ms
                            at Timeout._onTimeout (/opt/iobroker/node_modules/zigbee-herdsman/dist/utils/waitress.js:67:35)
                            at listOnTimeout (internal/timers.js:554:17)
                            at processTimers (internal/timers.js:497:7)
                        2021-03-13 22:10:33.547  - error: zigbee.0 (1357) SRSP - AF - dataRequestExt after 6000ms
                        2021-03-13 22:10:33.578  - info: zigbee.0 (1357) cleaned everything up...
                        2021-03-13 22:10:33.582  - info: zigbee.0 (1357) Zigbee: disabling joining new devices.
                        2021-03-13 22:10:34.082  - info: zigbee.0 (1357) terminating
                        2021-03-13 22:10:34.085  - warn: zigbee.0 (1357) Terminated (UNCAUGHT_EXCEPTION): Without reason
                        

                        Dann ist der Adapter wieder gelb und ist weg. Ich geb mal vorerst auf!
                        Danke

                        Fred Freund 1 Reply Last reply Reply Quote 0
                        • Fred Freund
                          Fred Freund @Fred Freund last edited by Fred Freund

                          Hallo,
                          wollte euch nur sagen habe mit meine Raspi und mit Hilfe der Anleitung
                          CC2531Flash ohne CCdebugger
                          Neu geflashed und jetzt findet er die Lampe aus einer super Entfernung! wo ich vorher auf 10cm hingehen musste und einen Error bekam.

                          2021-03-15 00:09:03.793  - info: host.broker1 stopInstance system.adapter.zigbee.0 (force=false, process=true)
                          2021-03-15 00:09:03.850  - info: zigbee.0 (1178) Got terminate signal TERMINATE_YOURSELF
                          2021-03-15 00:09:03.851  - info: host.broker1 stopInstance system.adapter.zigbee.0 send kill signal
                          2021-03-15 00:09:03.852  - info: zigbee.0 (1178) cleaned everything up...
                          2021-03-15 00:09:03.857  - warn: zigbee.0 (1178) Failed to stop zigbee during startup
                          2021-03-15 00:09:03.858  - info: zigbee.0 (1178) terminating
                          2021-03-15 00:09:03.859  - info: zigbee.0 (1178) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
                          2021-03-15 00:09:04.405  - info: host.broker1 instance system.adapter.zigbee.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
                          2021-03-15 00:09:06.902  - info: host.broker1 instance system.adapter.zigbee.0 started with pid 1699
                          2021-03-15 00:09:09.099  - info: zigbee.0 (1699) starting. Version 1.4.5 in /opt/iobroker/node_modules/iobroker.zigbee, node: v12.21.0, js-controller: 3.2.16
                          2021-03-15 00:09:09.142  - info: zigbee.0 (1699) Starting Zigbee  npm ...
                          2021-03-15 00:09:09.438  - info: zigbee.0 (1699) Installed Version: ioBroker/ioBroker.zigbee#cd902e1bafcb9ff16c582741d4f027b639a644c1
                          2021-03-15 00:09:14.864  - info: zigbee.0 (1699) Coordinator firmware version: {"type":"zStack12","meta":{"transportrev":2,"product":0,"majorrel":2,"minorrel":6,"maintrel":3,"revision":20201128}}
                          2021-03-15 00:09:14.877  - info: zigbee.0 (1699)   --> transmitPower : normal
                          2021-03-15 00:09:14.885  - info: zigbee.0 (1699) Currently no devices.
                          2021-03-15 00:09:14.887  - info: zigbee.0 (1699) Zigbee started
                          2021-03-15 00:09:14.948  - info: host.broker1 stopInstance system.adapter.zigbee.0 (force=false, process=true)
                          2021-03-15 00:09:14.953  - info: zigbee.0 (1699) Got terminate signal TERMINATE_YOURSELF
                          2021-03-15 00:09:14.954  - info: host.broker1 stopInstance system.adapter.zigbee.0 send kill signal
                          2021-03-15 00:09:14.955  - info: zigbee.0 (1699) cleaned everything up...
                          2021-03-15 00:09:14.958  - info: zigbee.0 (1699) Zigbee: disabling joining new devices.
                          2021-03-15 00:09:15.198  - info: zigbee.0 (1699) terminating
                          2021-03-15 00:09:15.199  - info: zigbee.0 (1699) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
                          2021-03-15 00:09:15.789  - info: host.broker1 instance system.adapter.zigbee.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
                          2021-03-15 00:09:17.990  - info: host.broker1 instance system.adapter.zigbee.0 started with pid 1715
                          2021-03-15 00:09:20.103  - info: zigbee.0 (1715) starting. Version 1.4.5 in /opt/iobroker/node_modules/iobroker.zigbee, node: v12.21.0, js-controller: 3.2.16
                          2021-03-15 00:09:20.233  - info: zigbee.0 (1715) Starting Zigbee  npm ...
                          2021-03-15 00:09:20.533  - info: zigbee.0 (1715) Installed Version: ioBroker/ioBroker.zigbee#cd902e1bafcb9ff16c582741d4f027b639a644c1
                          2021-03-15 00:09:22.516  - info: zigbee.0 (1715) Coordinator firmware version: {"type":"zStack12","meta":{"transportrev":2,"product":0,"majorrel":2,"minorrel":6,"maintrel":3,"revision":20201128}}
                          2021-03-15 00:09:22.528  - info: zigbee.0 (1715)   --> transmitPower : normal
                          2021-03-15 00:09:22.536  - info: zigbee.0 (1715) Currently no devices.
                          2021-03-15 00:09:22.538  - info: zigbee.0 (1715) Zigbee started
                          2021-03-15 00:09:43.873  - info: zigbee.0 (1715) Zigbee: allowing new devices to join.
                          2021-03-15 00:10:00.812  - info: zigbee.0 (1715) Starting interview of '0x60a423fffeebdcf4'
                          2021-03-15 00:10:03.214  - warn: zigbee.0 (1715) Device '0x60a423fffeebdcf4' announced itself
                          2021-03-15 00:10:45.165  - info: zigbee.0 (1715) Zigbee: stop joining
                          2021-03-15 00:10:48.491  - info: zigbee.0 (1715) Successfully interviewed '0x60a423fffeebdcf4', device has succesfully been paired
                          2021-03-15 00:10:48.492  - info: zigbee.0 (1715) Device '0x60a423fffeebdcf4' is supported, identified as: IKEA TRADFRI remote control (E1524/E1810)
                          2021-03-15 00:10:48.496  - info: zigbee.0 (1715) Configuring 0x60a423fffeebdcf4 TRADFRI remote control
                          2021-03-15 00:10:57.741  - info: zigbee.0 (1715) DeviceConfigure successful 0x60a423fffeebdcf4 TRADFRI remote control
                          2021-03-15 00:11:59.436  - info: zigbee.0 (1715) Zigbee: allowing new devices to join.
                          2021-03-15 00:12:27.266  - info: zigbee.0 (1715) Starting interview of '0x60a423fffeeecd67'
                          2021-03-15 00:12:31.127  - warn: zigbee.0 (1715) Device '0x60a423fffeeecd67' announced itself
                          2021-03-15 00:12:41.393  - info: zigbee.0 (1715) Successfully interviewed '0x60a423fffeeecd67', device has succesfully been paired
                          2021-03-15 00:12:41.394  - info: zigbee.0 (1715) Device '0x60a423fffeeecd67' is supported, identified as: IKEA GUNNARP panel round (T1828)
                          2021-03-15 00:12:41.397  - info: zigbee.0 (1715) Configuring 0x60a423fffeeecd67 GUNNARP panel round
                          2021-03-15 00:12:41.576  - info: zigbee.0 (1715) DeviceConfigure successful 0x60a423fffeeecd67 GUNNARP panel round
                          2021-03-15 00:13:00.706  - info: zigbee.0 (1715) Zigbee: stop joining
                          
                          arteck 1 Reply Last reply Reply Quote 0
                          • arteck
                            arteck Developer Most Active @Fred Freund last edited by

                            @fred-freund na ich hoffe du hast nicht die firmware genommen die da im beitrag stand vom April die ist nämlich fehlerhaft

                            Fred Freund 1 Reply Last reply Reply Quote 0
                            • Fred Freund
                              Fred Freund @arteck last edited by Fred Freund

                              @arteck Nein Nein , aber Danke.
                              Also das Hex zu finden war fuer mich nicht leicht.

                              HIER fuer den cc2531

                              Genau in diesem ZIP

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

                              Support us

                              ioBroker
                              Community Adapters
                              Donate
                              FAQ Cloud / IOT
                              HowTo: Node.js-Update
                              HowTo: Backup/Restore
                              Downloads
                              BLOG

                              717
                              Online

                              32.1k
                              Users

                              80.7k
                              Topics

                              1.3m
                              Posts

                              3
                              20
                              910
                              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