Navigation

    Logo
    • Register
    • Login
    • Search
    • Recent
    • Tags
    • Unread
    • Categories
    • Unreplied
    • Popular
    • GitHub
    • Docu
    • Hilfe
    1. Home
    2. Deutsch
    3. Tester
    4. ZigBee neue Version 1.6.x

    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

    ZigBee neue Version 1.6.x

    This topic has been deleted. Only users with topic management privileges can see it.
    • arteck
      arteck Developer Most Active @mickym last edited by

      @mickym sagte in ZigBee neue Version 1.6.0:

      Im Vergleich zum CC2531 ist

      das ist doch kein Vergleich..ist so als würest du einen Trabi mit Porsche vergleichen.. es sind beide Autos und bringen dich da wo du hin willst...

      vergiss es..

      1 Reply Last reply Reply Quote 0
      • mickym
        mickym Most Active @mickym last edited by mickym

        @mickym So heute ist der Adapter plötzlich wieder abgestürzt und war in einer Endlosschleife.

        Aus heiterem Himmel - habe zwar noch 15 Min vorher vom Log dran, aber das sagt nichts. Wenn das häufiger auftritt muss ich wohl doch mal debug einschalten:

        Abhilfe brachte nur ein kompletter Neustart des Systems - Stick ziehen und wieder reinstecken hat nichts gebracht.

        2021-09-30 20:00:00.122 - info: host.MWHome instance system.adapter.dwd.0 started with pid 21041
        2021-09-30 20:00:03.541 - info: dwd.0 (21041) starting. Version 2.7.7 in /opt/iobroker/node_modules/iobroker.dwd, node: v14.17.6, js-controller: 3.3.18
        2021-09-30 20:00:08.080 - info: dwd.0 (21041) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
        2021-09-30 20:00:08.619 - info: host.MWHome instance system.adapter.dwd.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
        2021-09-30 20:12:15.078 - error: zigbee.0 (27949) 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-09-30 20:12:15.080 - error: zigbee.0 (27949) unhandled promise rejection: Error while opening serialport 'Error: Error: No such file or directory, cannot open /dev/ttyACM0'
        2021-09-30 20:12:15.180 - error: zigbee.0 (27949) Error: Error while opening serialport 'Error: Error: No such file or directory, cannot open /dev/ttyACM0'
        at SerialPort. (/opt/iobroker/node_modules/iobroker.zigbee/node_modules/zigbee-herdsman/src/adapter/deconz/driver/driver.ts:182:28)
        at SerialPort._error (/opt/iobroker/node_modules/@serialport/stream/lib/index.js:198:14)
        at /opt/iobroker/node_modules/@serialport/stream/lib/index.js:242:12
        2021-09-30 20:12:15.180 - error: zigbee.0 (27949) Error while opening serialport 'Error: Error: No such file or directory, cannot open /dev/ttyACM0'
        2021-09-30 20:12:15.192 - info: zigbee.0 (27949) cleaned everything up...
        2021-09-30 20:12:15.195 - info: zigbee.0 (27949) Zigbee: disabling joining new devices.
        2021-09-30 20:12:15.693 - info: zigbee.0 (27949) terminating
        2021-09-30 20:12:15.695 - warn: zigbee.0 (27949) Terminated (UNCAUGHT_EXCEPTION): Without reason
        2021-09-30 20:12:16.318 - error: host.MWHome Caught by controller[1]: 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(). The promise rejected with the reason:
        2021-09-30 20:12:16.324 - error: host.MWHome Caught by controller[2]: Error: Error while opening serialport 'Error: Error: No such file or directory, cannot open /dev/ttyACM0'
        2021-09-30 20:12:16.324 - error: host.MWHome Caught by controller[2]: at SerialPort. (/opt/iobroker/node_modules/iobroker.zigbee/node_modules/zigbee-herdsman/src/adapter/deconz/driver/driver.ts:182:28)
        2021-09-30 20:12:16.325 - error: host.MWHome Caught by controller[2]: at SerialPort._error (/opt/iobroker/node_modules/@serialport/stream/lib/index.js:198:14)
        2021-09-30 20:12:16.325 - error: host.MWHome Caught by controller[2]: at /opt/iobroker/node_modules/@serialport/stream/lib/index.js:242:12
        2021-09-30 20:12:16.325 - error: host.MWHome instance system.adapter.zigbee.0 terminated with code 6 (UNCAUGHT_EXCEPTION)
        2021-09-30 20:12:16.326 - info: host.MWHome Restart adapter system.adapter.zigbee.0 because enabled
        2021-09-30 20:12:46.432 - info: host.MWHome instance system.adapter.zigbee.0 started with pid 23639
        2021-09-30 20:12:50.667 - info: zigbee.0 (23639) starting. Version 1.6.0 in /opt/iobroker/node_modules/iobroker.zigbee, node: v14.17.6, js-controller: 3.3.18
        2021-09-30 20:12:50.788 - info: zigbee.0 (23639) Starting Zigbee npm ...
        2021-09-30 20:12:51.459 - error: zigbee.0 (23639) Starting zigbee-herdsman problem : "Error while opening serialport 'Error: Error: No such file or directory, cannot open /dev/ttyACM0'"
        2021-09-30 20:12:51.460 - error: zigbee.0 (23639) Failed to start Zigbee
        2021-09-30 20:12:51.461 - error: zigbee.0 (23639) Error herdsman start
        2021-09-30 20:12:51.463 - info: zigbee.0 (23639) Installed Version: iobroker.zigbee@1.6.0
        2021-09-30 20:13:01.464 - info: zigbee.0 (23639) Try to reconnect. 1 attempts left
        2021-09-30 20:13:01.465 - info: zigbee.0 (23639) Starting Zigbee npm ...
        2021-09-30 20:13:01.491 - info: zigbee.0 (23639) Installed Version: iobroker.zigbee@1.6.0
        2021-09-30 20:13:01.734 - error: zigbee.0 (23639) Starting zigbee-herdsman problem : "Error while opening serialport 'Error: Error: No such file or directory, cannot open /dev/ttyACM0'"
        2021-09-30 20:13:01.735 - error: zigbee.0 (23639) Failed to start Zigbee
        2021-09-30 20:13:01.735 - error: zigbee.0 (23639) Error herdsman start
        2021-09-30 20:13:21.333 - error: zigbee.0 (23639) 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-09-30 20:13:21.334 - error: zigbee.0 (23639) unhandled promise rejection: Error while opening serialport 'Error: Error: No such file or directory, cannot open /dev/ttyACM0'
        2021-09-30 20:13:21.336 - error: zigbee.0 (23639) Error: Error while opening serialport 'Error: Error: No such file or directory, cannot open /dev/ttyACM0'
        at SerialPort. (/opt/iobroker/node_modules/iobroker.zigbee/node_modules/zigbee-herdsman/src/adapter/deconz/driver/driver.ts:182:28)
        at SerialPort._error (/opt/iobroker/node_modules/@serialport/stream/lib/index.js:198:14)
        at /opt/iobroker/node_modules/@serialport/stream/lib/index.js:242:12
        2021-09-30 20:13:21.337 - error: zigbee.0 (23639) Error while opening serialport 'Error: Error: No such file or directory, cannot open /dev/ttyACM0'
        2021-09-30 20:13:21.356 - info: zigbee.0 (23639) cleaned everything up...
        2021-09-30 20:13:21.362 - info: zigbee.0 (23639) Zigbee: disabling joining new devices.
        2021-09-30 20:13:21.569 - info: zigbee.0 (23639) terminating
        2021-09-30 20:13:21.571 - warn: zigbee.0 (23639) Terminated (UNCAUGHT_EXCEPTION): Without reason
        2021-09-30 20:13:22.203 - error: host.MWHome Caught by controller[1]: 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(). The promise rejected with the reason:
        2021-09-30 20:13:22.204 - error: host.MWHome Caught by controller[2]: Error: Error while opening serialport 'Error: Error: No such file or directory, cannot open /dev/ttyACM0'
        2021-09-30 20:13:22.204 - error: host.MWHome Caught by controller[2]: at SerialPort. (/opt/iobroker/node_modules/iobroker.zigbee/node_modules/zigbee-herdsman/src/adapter/deconz/driver/driver.ts:182:28)
        2021-09-30 20:13:22.205 - error: host.MWHome Caught by controller[2]: at SerialPort._error (/opt/iobroker/node_modules/@serialport/stream/lib/index.js:198:14)
        2021-09-30 20:13:22.205 - error: host.MWHome Caught by controller[2]: at /opt/iobroker/node_modules/@serialport/stream/lib/index.js:242:12
        2021-09-30 20:13:22.206 - error: host.MWHome instance system.adapter.zigbee.0 terminated with code 6 (UNCAUGHT_EXCEPTION)
        2021-09-30 20:13:22.207 - info: host.MWHome Restart adapter system.adapter.zigbee.0 because enabled
        2021-09-30 20:13:52.282 - info: host.MWHome instance system.adapter.zigbee.0 started with pid 23888
        2021-09-30 20:13:56.700 - info: zigbee.0 (23888) starting. Version 1.6.0 in /opt/iobroker/node_modules/iobroker.zigbee, node: v14.17.6, js-controller: 3.3.18
        2021-09-30 20:13:56.817 - info: zigbee.0 (23888) Starting Zigbee npm ...
        2021-09-30 20:13:57.305 - info: zigbee.0 (23888) Installed Version: iobroker.zigbee@1.6.0
        2021-09-30 20:13:57.441 - error: zigbee.0 (23888) Starting zigbee-herdsman problem : "Error while opening serialport 'Error: Error: No such file or directory, cannot open /dev/ttyACM0'"
        2021-09-30 20:13:57.442 - error: zigbee.0 (23888) Failed to start Zigbee
        2021-09-30 20:13:57.443 - error: zigbee.0 (23888) Error herdsman start
        2021-09-30 20:14:07.447 - info: zigbee.0 (23888) Try to reconnect. 1 attempts left
        2021-09-30 20:14:07.450 - info: zigbee.0 (23888) Starting Zigbee npm ...
        2021-09-30 20:14:07.524 - info: zigbee.0 (23888) Installed Version: iobroker.zigbee@1.6.0
        2021-09-30 20:14:07.718 - error: zigbee.0 (23888) Starting zigbee-herdsman problem : "Error while opening serialport 'Error: Error: No such file or directory, cannot open /dev/ttyACM0'"
        2021-09-30 20:14:07.719 - error: zigbee.0 (23888) Failed to start Zigbee
        2021-09-30 20:14:07.720 - error: zigbee.0 (23888) Error herdsman start
        2021-09-30 20:14:27.311 - error: zigbee.0 (23888) 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-09-30 20:14:27.314 - error: zigbee.0 (23888) unhandled promise rejection: Error while opening serialport 'Error: Error: No such file or directory, cannot open /dev/ttyACM0'
        2021-09-30 20:14:27.318 - error: zigbee.0 (23888) Error: Error while opening serialport 'Error: Error: No such file or directory, cannot open /dev/ttyACM0'
        at SerialPort. (/opt/iobroker/node_modules/iobroker.zigbee/node_modules/zigbee-herdsman/src/adapter/deconz/driver/driver.ts:182:28)
        at SerialPort._error (/opt/iobroker/node_modules/@serialport/stream/lib/index.js:198:14)
        at /opt/iobroker/node_modules/@serialport/stream/lib/index.js:242:12
        2021-09-30 20:14:27.319 - error: zigbee.0 (23888) Error while opening serialport 'Error: Error: No such file or directory, cannot open /dev/ttyACM0'
        2021-09-30 20:14:27.356 - info: zigbee.0 (23888) cleaned everything up...
        2021-09-30 20:14:27.370 - info: zigbee.0 (23888) Zigbee: disabling joining new devices.
        2021-09-30 20:14:27.559 - info: zigbee.0 (23888) terminating
        2021-09-30 20:14:27.560 - warn: zigbee.0 (23888) Terminated (UNCAUGHT_EXCEPTION): Without reason
        2021-09-30 20:14:28.212 - error: host.MWHome Caught by controller[1]: 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(). The promise rejected with the reason:
        2021-09-30 20:14:28.213 - error: host.MWHome Caught by controller[2]: Error: Error while opening serialport 'Error: Error: No such file or directory, cannot open /dev/ttyACM0'
        2021-09-30 20:14:28.214 - error: host.MWHome Caught by controller[2]: at SerialPort. (/opt/iobroker/node_modules/iobroker.zigbee/node_modules/zigbee-herdsman/src/adapter/deconz/driver/driver.ts:182:28)
        2021-09-30 20:14:28.214 - error: host.MWHome Caught by controller[2]: at SerialPort._error (/opt/iobroker/node_modules/@serialport/stream/lib/index.js:198:14)
        2021-09-30 20:14:28.215 - error: host.MWHome Caught by controller[2]: at /opt/iobroker/node_modules/@serialport/stream/lib/index.js:242:12
        2021-09-30 20:14:28.215 - error: host.MWHome instance system.adapter.zigbee.0 terminated with code 6 (UNCAUGHT_EXCEPTION)
        2021-09-30 20:14:28.216 - info: host.MWHome Restart adapter system.adapter.zigbee.0 because enabled
        2021-09-30 20:14:28.217 - warn: host.MWHome Do not restart adapter system.adapter.zigbee.0 because restart loop detected
        2021-09-30 20:15:00.088 - info: host.MWHome instance system.adapter.dwd.0 started with pid 24126
        2021-09-30 20:15:05.055 - info: dwd.0 (24126) starting. Version 2.7.7 in /opt/iobroker/node_modules/iobroker.dwd, node: v14.17.6, js-controller: 3.3.18
        2021-09-30 20:15:07.510 - info: dwd.0 (24126) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
        2021-09-30 20:15:08.056 - info: host.MWHome instance system.adapter.dwd.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
        

        Nach Neustart nun alles wieder ruhig und normal

        Thomas Braun 1 Reply Last reply Reply Quote 0
        • Thomas Braun
          Thomas Braun Most Active @mickym last edited by

          @mickym sagte in ZigBee neue Version 1.6.0:

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

          Hinterleg den Link 'by-id' im Adapter.

          mickym 1 Reply Last reply Reply Quote 0
          • mickym
            mickym Most Active @Thomas Braun last edited by

            @thomas-braun Hab ich gemacht - mal schauen, ob das was bringt

            mickym 1 Reply Last reply Reply Quote 0
            • mickym
              mickym Most Active @mickym last edited by mickym

              Sporadisch immer noch Absturz - insofern haben FW Update und Umstellung auf ID nichts gebracht. Passiert vielleicht alle 3 Tage 1 Mal - aber irgendwas wird halt nicht richtig abgefangen.

              2021-10-06 07:19:19.207 - error: zigbee.0 (10138) 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-10-06 07:19:19.207 - error: zigbee.0 (10138) unhandled promise rejection: undefined
              2021-10-06 07:19:19.209 - info: zigbee.0 (10138) cleaned everything up...
              2021-10-06 07:19:19.300 - info: zigbee.0 (10138) Zigbee: disabling joining new devices.
              2021-10-06 07:19:19.628 - info: zigbee.0 (10138) terminating
              2021-10-06 07:19:19.630 - warn: zigbee.0 (10138) Terminated (UNCAUGHT_EXCEPTION): Without reason
              2021-10-06 07:19:20.247 - error: host.MWHome Caught by controller[1]: 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(). The promise rejected with the reason:
              2021-10-06 07:19:20.253 - error: host.MWHome Caught by controller[2]: undefined
              2021-10-06 07:19:20.254 - error: host.MWHome instance system.adapter.zigbee.0 terminated with code 6 (UNCAUGHT_EXCEPTION)
              2021-10-06 07:19:20.255 - info: host.MWHome Restart adapter system.adapter.zigbee.0 because enabled
              2021-10-06 07:19:50.298 - info: host.MWHome instance system.adapter.zigbee.0 started with pid 31577
              2021-10-06 07:19:54.744 - info: zigbee.0 (31577) starting. Version 1.6.0 in /opt/iobroker/node_modules/iobroker.zigbee, node: v14.18.0, js-controller: 3.3.18
              2021-10-06 07:19:54.866 - info: zigbee.0 (31577) Starting Zigbee npm ...
              2021-10-06 07:19:55.286 - info: zigbee.0 (31577) Installed Version: iobroker.zigbee@1.6.0
              2021-10-06 07:19:55.462 - info: zigbee.0 (31577) Coordinator firmware version: {"type":"ConBee2/RaspBee2","meta":{"transportrev":0,"product":0,"majorrel":38,"minorrel":112,"maintrel":0,"revision":"0x26700700"}}
              2021-10-06 07:19:55.486 - info: zigbee.0 (31577) Unable to disable LED, unsupported function.
              2021-10-06 07:19:55.640 - info: zigbee.0 (31577) --> transmitPower : normal
              2021-10-06 07:19:55.722 - info: zigbee.0 (31577) Unable to set transmit power, unsupported function.
              2021-10-06 07:19:55.728 - info: zigbee.0 (31577) Currently 21 devices are joined:
              

              Ich verfolge, dass aber erst mal nicht weiter, weil sonst bis auf die Gruppenfunktion mit dem Fehlern im Log alles funktioniert.

              Thomas Braun 1 Reply Last reply Reply Quote 0
              • Thomas Braun
                Thomas Braun Most Active @mickym last edited by

                @mickym sagte in ZigBee neue Version 1.6.0:

                Version 1.6.0

                In stable ist 1.5.6, in beta 1.6.3.

                mickym 1 Reply Last reply Reply Quote 0
                • mickym
                  mickym Most Active @Thomas Braun last edited by

                  @thomas-braun Auf github vielleicht, aber in der normalen Beta ist immer noch 1.6.0

                  1a54ee7f-63b3-4e0b-a4d6-0c66fc643de1-image.png

                  Aber egal - solange es in der Häufigkeit passiert -stört mich das nicht und warte lieber bis das Gruppenproblem gelöst ist.

                  Thomas Braun 1 Reply Last reply Reply Quote 0
                  • Thomas Braun
                    Thomas Braun Most Active @mickym last edited by

                    @mickym

                    Nope:

                    zigbee
                    github:	1.6.4
                    latest:	1.6.3 for 8 days
                    stable:	1.5.6 for 4 months
                    
                    mickym 1 Reply Last reply Reply Quote 0
                    • mickym
                      mickym Most Active @Thomas Braun last edited by mickym

                      @thomas-braun

                      Na nun hat es der Info Adapter gefunden - war aber keine gute Idee - da Installation fehlschlug und nun gar nichts mehr geht:

                      $ ./iobroker upgrade zigbee
                      Update zigbee from @1.6.0 to @1.6.3
                      host.MWHome Adapter "system.adapter.zigbee.0" is stopped.
                      NPM version: 6.14.15npm install iobroker.zigbee@1.6.3 --loglevel error --prefix "/opt/iobroker" (System call)
                      make: g++: Datei oder Verzeichnis nicht gefunden
                      make: *** [bindings.target.mk:112: Release/obj.target/bindings/src/serialport.o] Fehler 127gyp ERR! build error gyp ERR! stack Error: `make` failed with exit code: 2gyp ERR! stack     at ChildProcess.onExit (/usr/lib/node_modules/npm/node_modules/node-gyp/lib/build.js:194:23)gyp ERR! stack     at ChildProcess.emit (events.js:400:28)gyp ERR! stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:282:12)gyp ERR! System Linux 5.10.63-v7l+gyp ERR! command "/usr/bin/node" "/usr/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "rebuild"gyp ERR! cwd /opt/iobroker/node_modules/iobroker.zigbee/node_modules/@serialport/bindingsgyp ERR! node -v v14.18.0gyp ERR! node-gyp -v v5.1.0gyp ERR! not ok 
                      npm ERR! code ELIFECYCLE
                      npm ERR! errno 1
                      npm ERR! @serialport/bindings@9.2.3 install: `prebuild-install --tag-prefix @serialport/bindings@ || node-gyp rebuild`npm ERR! Exit status 1npm ERR! npm ERR! Failed at the @serialport/bindings@9.2.3 install script.npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
                      
                      npm ERR! A complete log of this run can be found in:npm ERR!     /home/iobroker/.npm/_logs/2021-10-06T14_10_43_237Z-debug.log
                      ERROR: host.MWHome Cannot install iobroker.zigbee@1.6.3: 1
                      ERROR: process exited with code 25
                      

                      Irgendwie fehlt wohl ein Kompiler.

                      EDIT: Hat sich von selbst wieder repariert - und ist wieder auf 1.6.0 gesprungen!!!! -

                      oder muss ich den C++ Compiler installieren???

                      apt-get install g++
                      

                      EDIT2: OK nach Installation des Compilers hat Update auf 1.6.3 funktioniert. 🙂

                      Die Gruppenfehler sind aber nach wie vor noch vorhanden - aber nun läuft 1.6.3

                      2021-10-06 16:23:48.130 - info: host.MWHome iobroker Adapter "zigbee" updated
                      2021-10-06 16:23:48.139 - info: host.MWHome iobroker host.MWHome Adapter "system.adapter.zigbee.0" is started
                      2021-10-06 16:23:48.201 - info: host.MWHome "system.adapter.zigbee.0" enabled
                      2021-10-06 16:23:48.359 - info: host.MWHome instance system.adapter.zigbee.0 started with pid 13645
                      2021-10-06 16:23:49.326 - info: host.MWHome iobroker exit 0
                      2021-10-06 16:23:53.783 - info: zigbee.0 (13645) starting. Version 1.6.3 in /opt/iobroker/node_modules/iobroker.zigbee, node: v14.18.0, js-controller: 3.3.18
                      2021-10-06 16:23:53.957 - info: zigbee.0 (13645) Starting Zigbee npm ...
                      2021-10-06 16:23:54.532 - info: zigbee.0 (13645) Installed Version: iobroker.zigbee@1.6.3
                      2021-10-06 16:23:54.679 - info: zigbee.0 (13645) Coordinator firmware version: {"type":"ConBee2/RaspBee2","meta":{"transportrev":0,"product":0,"majorrel":38,"minorrel":112,"maintrel":0,"revision":"0x26700700"}}
                      2021-10-06 16:23:54.701 - info: zigbee.0 (13645) Unable to disable LED, unsupported function.
                      2021-10-06 16:23:54.830 - info: zigbee.0 (13645) --> transmitPower : normal
                      2021-10-06 16:23:54.925 - info: zigbee.0 (13645) Unable to set transmit power, unsupported function.
                      2021-10-06 16:23:54.932 - info: zigbee.0 (13645) Currently 21 devices are joined
                      

                      Thomas Braun 1 Reply Last reply Reply Quote 0
                      • Thomas Braun
                        Thomas Braun Most Active @mickym last edited by

                        @mickym

                        Ist das build-essential Paket installiert? Das sollte eigentlich alles mitschleppen.

                        mickym 1 Reply Last reply Reply Quote 0
                        • mickym
                          mickym Most Active @Thomas Braun last edited by

                          @thomas-braun

                          Anscheinend nicht?? - sonst müsste wahrscheinlich auch installiert in KLammern dahinter stehen?:

                          apt list build-essential
                          Auflistung… Fertig
                          build-essential/stable 12.9 armhf
                          

                          aber wie gesagt - ich hab jetzt g++ noch installiert und dann lief auch das zigbee update.

                          apt list g++
                          Auflistung… Fertig
                          g++/stable,now 4:10.2.1-1+rpi1 armhf  [installiert]
                          
                          Thomas Braun 1 Reply Last reply Reply Quote 0
                          • Thomas Braun
                            Thomas Braun Most Active @mickym last edited by Thomas Braun

                            @mickym

                            apt policy build-essential
                            

                            Ich würde es aber auf jedenfall als meta-Paket nachinstallieren. Das ist einfach am 'rundesten' für das Thema 'Kompilieren'.

                            mickym 2 Replies Last reply Reply Quote 0
                            • mickym
                              mickym Most Active @Thomas Braun last edited by

                              @thomas-braun

                              apt policy build-essential
                              build-essential:
                                Installiert:           (keine)
                                Installationskandidat: 12.9
                                Versionstabelle:
                                   12.9 500
                                      500 http://raspbian.raspberrypi.org/raspbian bullseye/main armhf Packages
                              
                              1 Reply Last reply Reply Quote 0
                              • mickym
                                mickym Most Active @Thomas Braun last edited by mickym

                                @thomas-braun sagte in ZigBee neue Version 1.6.0:

                                @mickym

                                apt policy build-essential
                                

                                Ich würde es aber auf jedenfall als meta-Paket nachinstallieren. Das ist einfach am 'rundesten' für das Thema 'Kompilieren'.

                                Habs nun installiert:

                                apt policy build-essential
                                build-essential:
                                  Installiert:           12.9
                                  Installationskandidat: 12.9
                                  Versionstabelle:
                                 *** 12.9 500
                                        500 http://raspbian.raspberrypi.org/raspbian bullseye/main armhf Packages
                                        100 /var/lib/dpkg/status
                                

                                bzw.

                                apt list build-essential
                                Auflistung… Fertig
                                build-essential/stable,now 12.9 armhf  [installiert]
                                
                                mickym 1 Reply Last reply Reply Quote 0
                                • mickym
                                  mickym Most Active @mickym last edited by

                                  Kurzes Zwischenfazit mit Version 1.6.3 - seit 5 Tagen keinen einzigen Absturz mehr. 🙂

                                  1 Reply Last reply Reply Quote 0
                                  • D
                                    disaster123 last edited by disaster123

                                    Hallo, ich erhalte immer mal wieder folgende Meldungen von verschiedenen Geräten / IDs im Log:
                                    "
                                    (237) Send command to 0x84fd27fffe812d46 failed with no error code (no response received)
                                    "

                                    Alle Geräte haben in der Übersicht > 190 Empfang und werden grün in der Netzwerkübersicht dargestellt. in >90% schalten sie aber dennoch korrekt. In 10% der Fälle schalten sie gar nicht. Das Ganze tritt bei mehreren Geräten an völlig unterschiedlichen Stellen im Haus auf.

                                    Irgendjemand einen Ansatz?

                                    Edit: das Ganze scheint nur zu passieren bei Scripten, die via

                                                    setState(k_t_l_id + luefter1_id.toString(), true);
                                    

                                    den Status ändern. Wenn ich via GUI einen Switch bediene passiert das gefühlt nie.

                                    arteck 1 Reply Last reply Reply Quote 0
                                    • arteck
                                      arteck Developer Most Active @disaster123 last edited by

                                      @disaster123 sagte in ZigBee neue Version 1.6.0:

                                                  setState(k_t_l_id + luefter1_id.toString(), true);
                                      

                                      was steht den dann hinter

                                      k_t_l_id + luefter1_id.toString()
                                      

                                      nach konkatienierung ?

                                      D 1 Reply Last reply Reply Quote 0
                                      • D
                                        disaster123 @arteck last edited by

                                        @arteck ganz normal die ID. War nur nen Beispiel - damit kann es nichts zu tun haben. Ich kann auch hardcodiert den Befehl schicken mit:

                                            setState("zigbee.0.00124b0022612054.brightness", new_val, false);
                                        

                                        dort tritt es auch auf.

                                        1 Reply Last reply Reply Quote 0
                                        • D
                                          disaster123 last edited by

                                          Ich kann es zuverlässig simulieren in dem ich zum Beispiel 6x setState direkt hintereinander absetze dann kommen Timeouts.

                                          Asgothian arteck 2 Replies Last reply Reply Quote 0
                                          • Asgothian
                                            Asgothian Developer @disaster123 last edited by

                                            @disaster123 sagte in ZigBee neue Version 1.6.0:

                                            Ich kann es zuverlässig simulieren in dem ich zum Beispiel 6x setState direkt hintereinander absetze dann kommen Timeouts.

                                            Du solltest versuchen sicherzustellen das zwischen 2 befehlen 50-100 ms vergehen. Je mehr Befehle kurzfristig abgesetzt werden desto eher passiert es das ein Befehl “untergeht”. Die Fehlermeldung besagt explizit das ein Gerät eine Meldung nicht in der dafür vorgesehenen Zeit beantwortet hat.

                                            A.

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

                                            Support us

                                            ioBroker
                                            Community Adapters
                                            Donate

                                            777
                                            Online

                                            31.7k
                                            Users

                                            79.9k
                                            Topics

                                            1.3m
                                            Posts

                                            61
                                            509
                                            86902
                                            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