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

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

Community Forum

donate donate
  1. ioBroker Community Home
  2. Deutsch
  3. ioBroker Allgemein
  4. ZigBee Störung

NEWS

  • Neuer Blogbeitrag: Monatsrückblick - Dezember 2025 🎄
    BluefoxB
    Bluefox
    11
    1
    476

  • Weihnachtsangebot 2025! 🎄
    BluefoxB
    Bluefox
    24
    1
    1.6k

  • UPDATE 31.10.: Amazon Alexa - ioBroker Skill läuft aus ?
    apollon77A
    apollon77
    48
    3
    9.5k

ZigBee Störung

Geplant Angeheftet Gesperrt Verschoben ioBroker Allgemein
56 Beiträge 9 Kommentatoren 2.4k Aufrufe 6 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.
  • L Online
    L Online
    legro
    schrieb am zuletzt editiert von legro
    #1

    Auslöser ..

    Heute Morgen gab es einen Stromausfall. Der Fehlerstromschutzschalter (FI) hatte ausgelöst.

    Folgen ..

    Seither geht kein einziges über ZigBee angebundenes Gerät (HUE- und OSRAM-Lampen, BITRON Rauchmelder und Außensirene, ..)

    Untersuchungen/Tests ..

    ZigBee-Adapter neu gestartet
    Raspberry Pi neu gestartet
    Gerät(e) (er)neu(t) anlernen
    ..
    Jegliche Ansteuerung dieser Geräte schlägt fehl.

    Als Coordinator habe ich einen CC26X2R1 in Betrieb. Der Adapter zeigt keine Verbindungsfehler an.

    Ich bin komplett ratlos.

    Raspberry Pi 5 mit 8GB + 120GB SSD + Coordinator COD-m + ioBroker ..

    David G.D arteckA 2 Antworten Letzte Antwort
    0
    • L legro

      Auslöser ..

      Heute Morgen gab es einen Stromausfall. Der Fehlerstromschutzschalter (FI) hatte ausgelöst.

      Folgen ..

      Seither geht kein einziges über ZigBee angebundenes Gerät (HUE- und OSRAM-Lampen, BITRON Rauchmelder und Außensirene, ..)

      Untersuchungen/Tests ..

      ZigBee-Adapter neu gestartet
      Raspberry Pi neu gestartet
      Gerät(e) (er)neu(t) anlernen
      ..
      Jegliche Ansteuerung dieser Geräte schlägt fehl.

      Als Coordinator habe ich einen CC26X2R1 in Betrieb. Der Adapter zeigt keine Verbindungsfehler an.

      Ich bin komplett ratlos.

      David G.D Online
      David G.D Online
      David G.
      schrieb am zuletzt editiert von
      #2

      @legro

      Ich kann vermutlich nicht helfen.

      Aber was bestimmt hilft:

      • Ist der Adapter grün?
      • Log vom Adapterstart
      • Was für Meldungen kommen im Log wenn ein Gerät geschaltet wird und die Aktion nicht ausgeführt werden kann?

      Zeigt eure Lovelace-Visualisierung klick
      (Auch ideal um sich Anregungen zu holen)

      Meine Tabellen für eure Visualisierung klick

      1 Antwort Letzte Antwort
      0
      • L legro

        Auslöser ..

        Heute Morgen gab es einen Stromausfall. Der Fehlerstromschutzschalter (FI) hatte ausgelöst.

        Folgen ..

        Seither geht kein einziges über ZigBee angebundenes Gerät (HUE- und OSRAM-Lampen, BITRON Rauchmelder und Außensirene, ..)

        Untersuchungen/Tests ..

        ZigBee-Adapter neu gestartet
        Raspberry Pi neu gestartet
        Gerät(e) (er)neu(t) anlernen
        ..
        Jegliche Ansteuerung dieser Geräte schlägt fehl.

        Als Coordinator habe ich einen CC26X2R1 in Betrieb. Der Adapter zeigt keine Verbindungsfehler an.

        Ich bin komplett ratlos.

        arteckA Offline
        arteckA Offline
        arteck
        Developer Most Active
        schrieb am zuletzt editiert von
        #3

        @legro sagte in ZigBee Störung:

        Ich bin komplett ratlos.

        ohne LOG ich auch..

        zeigmal das LOG nach start des adapter

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

        L 1 Antwort Letzte Antwort
        0
        • arteckA arteck

          @legro sagte in ZigBee Störung:

          Ich bin komplett ratlos.

          ohne LOG ich auch..

          zeigmal das LOG nach start des adapter

          L Online
          L Online
          legro
          schrieb am zuletzt editiert von
          #4

          @arteck

          Entschuldigung bitte!

          Ich vergaß die Log-Daten. Hier sind sie ..

          
          zigbee.0
          2024-05-07 08:12:30.610	warn	Send command to 0x00124b00090da34c failed with: Code 205 (No network route)
          
          zigbee.0
          2024-05-07 08:12:12.891	warn	Send command to 0x00124b0008a50109 failed with: Code 205 (No network route)
          
          zigbee.0
          2024-05-07 08:12:08.556	warn	Send command to 0x00124b00090da34c failed with: Code 205 (No network route)
          
          zigbee.0
          2024-05-07 08:11:50.767	warn	Send command to 0x00124b0008a50109 failed with: Code 205 (No network route)
          
          zigbee.0
          2024-05-07 08:11:25.634	warn	Send command to 0x00124b0008a50109 failed with: Code 205 (No network route)
          
          zigbee.0
          2024-05-07 08:11:03.732	warn	Send command to 0x00124b0008a50109 failed with: Code 205 (No network route)
          
          zigbee.0
          2024-05-07 08:10:42.048	warn	Send command to 0x00124b0008a50109 failed with: Code 205 (No network route)
          
          

          Raspberry Pi 5 mit 8GB + 120GB SSD + Coordinator COD-m + ioBroker ..

          arteckA 1 Antwort Letzte Antwort
          0
          • L legro

            @arteck

            Entschuldigung bitte!

            Ich vergaß die Log-Daten. Hier sind sie ..

            
            zigbee.0
            2024-05-07 08:12:30.610	warn	Send command to 0x00124b00090da34c failed with: Code 205 (No network route)
            
            zigbee.0
            2024-05-07 08:12:12.891	warn	Send command to 0x00124b0008a50109 failed with: Code 205 (No network route)
            
            zigbee.0
            2024-05-07 08:12:08.556	warn	Send command to 0x00124b00090da34c failed with: Code 205 (No network route)
            
            zigbee.0
            2024-05-07 08:11:50.767	warn	Send command to 0x00124b0008a50109 failed with: Code 205 (No network route)
            
            zigbee.0
            2024-05-07 08:11:25.634	warn	Send command to 0x00124b0008a50109 failed with: Code 205 (No network route)
            
            zigbee.0
            2024-05-07 08:11:03.732	warn	Send command to 0x00124b0008a50109 failed with: Code 205 (No network route)
            
            zigbee.0
            2024-05-07 08:10:42.048	warn	Send command to 0x00124b0008a50109 failed with: Code 205 (No network route)
            
            
            arteckA Offline
            arteckA Offline
            arteck
            Developer Most Active
            schrieb am zuletzt editiert von
            #5

            @legro das ist nicht das was ich sehen will..

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

            L 1 Antwort Letzte Antwort
            0
            • arteckA arteck

              @legro das ist nicht das was ich sehen will..

              L Online
              L Online
              legro
              schrieb am zuletzt editiert von
              #6

              @arteck sagte in ZigBee Störung:

              @legro das ist nicht das was ich sehen will..

              Bitte sage mir, was ich tun soll, damit du die erforderlichen Daten einsehen kannst.

              Raspberry Pi 5 mit 8GB + 120GB SSD + Coordinator COD-m + ioBroker ..

              Thomas BraunT 1 Antwort Letzte Antwort
              0
              • L legro

                @arteck sagte in ZigBee Störung:

                @legro das ist nicht das was ich sehen will..

                Bitte sage mir, was ich tun soll, damit du die erforderlichen Daten einsehen kannst.

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

                @legro

                Die Meldungen beim Start des Adapters sind gefragt.
                Konsole auf,

                iob logs --watch
                

                einhacken, mit dem Adapter spielen (Kaltstart usw.), Output des Terminals hier wieder rein.

                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

                L 1 Antwort Letzte Antwort
                0
                • Thomas BraunT Thomas Braun

                  @legro

                  Die Meldungen beim Start des Adapters sind gefragt.
                  Konsole auf,

                  iob logs --watch
                  

                  einhacken, mit dem Adapter spielen (Kaltstart usw.), Output des Terminals hier wieder rein.

                  L Online
                  L Online
                  legro
                  schrieb am zuletzt editiert von legro
                  #8

                  @thomas-braun @arteck

                  In dem nachfolgenden Datenwust sind zwei Neustarts enthalten. Wie gesagt, für mich sind dies alles Böhmische Dörfer.

                  Last login: Tue May  7 09:15:52 on ttys000
                  
                  The default interactive shell is now zsh.
                  To update your account to use zsh, please run `chsh -s /bin/zsh`.
                  For more details, please visit https://support.apple.com/kb/HT208050.
                  Leanders-MacBook-Pro-Neu:~ leandergroben$ ssh pi@192.168.4.58
                  pi@192.168.4.58's password: 
                  Linux raspiBullseye 6.1.21-v8+ #1642 SMP PREEMPT Mon Apr  3 17:24:16 BST 2023 aarch64
                  
                  The programs included with the Debian GNU/Linux system are free software;
                  the exact distribution terms for each program are described in the
                  individual files in /usr/share/doc/*/copyright.
                  
                  Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
                  permitted by applicable law.
                  Last login: Tue May  7 09:18:12 2024 from 192.168.4.24
                  
                  Wi-Fi is currently blocked by rfkill.
                  Use raspi-config to set the country before use.
                  
                  pi@raspiBullseye:~ $ iob logs --watch
                  2024-05-07 06:55:28.708  - info: bydhvs.0 (3411) Received, Packet: 2 Data: 01033200080144013f0062000078f0001300110011000003130000000000000902000279223bf400003143000000ff00004000042c379d
                  2024-05-07 06:55:28.966  - info: bydhvs.0 (3411) Received, Packet: 3 Data: 010306001302000000a50e
                  2024-05-07 06:55:30.827  - warn: zigbee.0 (3201) Send command to 0x8418260000ca4b3f failed with: Code 205 (No network route)
                  2024-05-07 06:55:38.408  - info: zigbee.0 (3201) Zigbee: stop joining
                  2024-05-07 06:57:17.490  - warn: zigbee.0 (3201) Send command to 0x8418260000074b81 failed with: Code 205 (No network route)
                  2024-05-07 06:58:28.828  - info: zigbee.0 (3201) Device '0x8418260000074b81' announced itself
                  2024-05-07 06:59:07.186  - info: host.raspiBullseye stopInstance system.adapter.zigbee.0 (force=false, process=true)
                  2024-05-07 06:59:07.218  - info: zigbee.0 (3201) Got terminate signal TERMINATE_YOURSELF
                  2024-05-07 06:59:07.221  - info: zigbee.0 (3201) cleaned everything up...
                  2024-05-07 06:59:07.225  - info: zigbee.0 (3201) Zigbee: disabling joining new devices.
                  2024-05-07 06:59:07.531  - info: host.raspiBullseye stopInstance system.adapter.zigbee.0 send kill signal
                  2024-05-07 06:59:07.727  - info: zigbee.0 (3201) terminating
                  2024-05-07 06:59:07.731  - info: zigbee.0 (3201) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
                  2024-05-07 06:59:08.669  - info: host.raspiBullseye instance system.adapter.zigbee.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
                  2024-05-07 06:59:10.777  - info: host.raspiBullseye instance system.adapter.zigbee.0 started with pid 5074
                  2024-05-07 06:59:17.765  - info: zigbee.0 (5074) starting. Version 1.10.3 in /opt/iobroker/node_modules/iobroker.zigbee, node: v18.20.0, js-controller: 5.0.19
                  2024-05-07 06:59:17.930  - info: zigbee.0 (5074) delete old Backup files. keep only last 10
                  2024-05-07 06:59:17.933  - info: zigbee.0 (5074) Starting Zigbee  npm ...
                  2024-05-07 06:59:18.495  - info: zigbee.0 (5074) Installed Version: iobroker.zigbee@1.10.3
                  2024-05-07 06:59:19.625  - info: zigbee.0 (5074) Coordinator firmware version: {"type":"zStack3x0","meta":{"transportrev":2,"product":1,"majorrel":2,"minorrel":7,"maintrel":1,"revision":20220219}}
                  2024-05-07 06:59:19.633  - info: zigbee.0 (5074) Unable to disable LED, unsupported function.
                  2024-05-07 06:59:19.652  - info: zigbee.0 (5074)   --> transmitPower : high
                  2024-05-07 06:59:19.664  - info: zigbee.0 (5074) Currently 14 devices are joined:
                  2024-05-07 06:59:19.787  - info: zigbee.0 (5074) 0x00124b0008a50109 (addr 52361): AV2010/24 - SMaBiT (Bitron Video) Optical smoke detector (hardware version v1) (EndDevice)
                  2024-05-07 06:59:19.793  - info: zigbee.0 (5074) 0x00124b000621ad0e (addr 36173): AV2010/29 - SMaBiT (Bitron Video) Outdoor siren (EndDevice)
                  2024-05-07 06:59:19.795  - info: zigbee.0 (5074) 0x00124b00074e8fdf (addr 6545): AV2010/24 - SMaBiT (Bitron Video) Optical smoke detector (hardware version v1) (EndDevice)
                  2024-05-07 06:59:19.797  - info: zigbee.0 (5074) 0x00124b00077b7fe8 (addr 3558): AV2010/24 - SMaBiT (Bitron Video) Optical smoke detector (hardware version v1) (EndDevice)
                  2024-05-07 06:59:19.798  - info: zigbee.0 (5074) 0x00124b0008a68663 (addr 32039): AV2010/24 - SMaBiT (Bitron Video) Optical smoke detector (hardware version v1) (EndDevice)
                  2024-05-07 06:59:19.800  - info: zigbee.0 (5074) 0x00124b0008e7395c (addr 46194): AV2010/24 - SMaBiT (Bitron Video) Optical smoke detector (hardware version v1) (EndDevice)
                  2024-05-07 06:59:19.802  - info: zigbee.0 (5074) 0x00124b00090da34c (addr 58423): AV2010/24 - SMaBiT (Bitron Video) Optical smoke detector (hardware version v1) (EndDevice)
                  2024-05-07 06:59:19.804  - info: zigbee.0 (5074) 0x00124b0008e73540 (addr 25642): AV2010/24 - SMaBiT (Bitron Video) Optical smoke detector (hardware version v1) (EndDevice)
                  2024-05-07 06:59:19.806  - info: zigbee.0 (5074) 0x8418260000074b81 (addr 33976): AC03641 - OSRAM LIGHTIFY LED Classic A60 clear (Router)
                  2024-05-07 06:59:19.808  - info: zigbee.0 (5074) 0x841826000007fd2c (addr 57868): AB32840 - OSRAM LIGHTIFY LED Classic B40 tunable white (Router)
                  2024-05-07 06:59:19.809  - info: zigbee.0 (5074) 0x841826000007feec (addr 53249): AB32840 - OSRAM LIGHTIFY LED Classic B40 tunable white (Router)
                  2024-05-07 06:59:19.811  - info: zigbee.0 (5074) 0x8418260000ca4b3f (addr 43907): AA70155 - OSRAM LIGHTIFY LED A19 tunable white / Classic A60 TW (Router)
                  2024-05-07 06:59:19.813  - info: zigbee.0 (5074) 0x001788010278c53e (addr 65419): 9290012573A - Philips Hue white and color ambiance E26/E27/E14 (Router)
                  2024-05-07 06:59:19.815  - info: zigbee.0 (5074) 0x001788010db82a55 (addr 143): 9290024406A - Philips Hue P45 light bulb (Router)
                  2024-05-07 06:59:19.816  - info: zigbee.0 (5074) Zigbee started
                  2024-05-07 06:59:19.911  - info: zigbee.0 (5074) debug devices set to []
                  2024-05-07 06:59:24.421  - info: zigbee.0 (5074) List of port: [{"path":"/dev/ttyACM0","manufacturer":"Texas Instruments","serialNumber":"L1100QXL","pnpId":"usb-Texas_Instruments_XDS110__03.00.00.20__Embed_with_CMSIS-DAP_L1100QXL-if00","vendorId":"0451","productId":"bef3"},{"path":"/dev/ttyACM1","manufacturer":"Texas Instruments","serialNumber":"L1100QXL","pnpId":"usb-Texas_Instruments_XDS110__03.00.00.20__Embed_with_CMSIS-DAP_L1100QXL-if03","vendorId":"0451","productId":"bef3"},{"path":"/dev/ttyS0"}]
                  2024-05-07 06:59:52.425  - error: zigbee.0 (5074) Error 225 on send command to 0x001788010db82a55. Error: Error: ZCL command 0x001788010db82a55/11 genOnOff.on({}, {"timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":false,"direction":0,"srcEndpoint":null,"reservedBits":0,"manufacturerCode":null,"transactionSequenceNumber":null,"writeUndiv":false}) failed (Data request failed with error: 'MAC channel access failure' (225))
                      at ZStackAdapter.sendZclFrameToEndpointInternal (/opt/iobroker/node_modules/zigbee-herdsman/src/adapter/z-stack/adapter/zStackAdapter.ts:411:23)
                      at Queue.execute (/opt/iobroker/node_modules/zigbee-herdsman/src/utils/queue.ts:35:20)
                      at Request.send (/opt/iobroker/node_modules/zigbee-herdsman/src/controller/helpers/request.ts:79:20)
                      at Endpoint.zclCommand (/opt/iobroker/node_modules/zigbee-herdsman/src/controller/model/endpoint.ts:756:28)
                      at Endpoint.command (/opt/iobroker/node_modules/zigbee-herdsman/src/controller/model/endpoint.ts:587:24)
                      at Object.convertSet (/opt/iobroker/node_modules/zigbee-herdsman-converters/src/converters/toZigbee.ts:48:17)
                      at Object.convertSet (/opt/iobroker/node_modules/zigbee-herdsman-converters/src/converters/toZigbee.ts:1131:32)
                      at /opt/iobroker/node_modules/iobroker.zigbee/main.js:754:36
                  2024-05-07 06:59:54.242  - info: zigbee.0 (5074) Zigbee: allowing new devices to join.
                  2024-05-07 07:00:00.228  - info: host.raspiBullseye instance system.adapter.dwd.0 started with pid 5168
                  2024-05-07 07:00:00.843  - error: zigbee.0 (5074) Error 225 on send command to 0x001788010db82a55. Error: Error: ZCL command 0x001788010db82a55/11 genOnOff.off({}, {"timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":false,"direction":0,"srcEndpoint":null,"reservedBits":0,"manufacturerCode":null,"transactionSequenceNumber":null,"writeUndiv":false}) failed (Data request failed with error: 'MAC channel access failure' (225))
                      at ZStackAdapter.sendZclFrameToEndpointInternal (/opt/iobroker/node_modules/zigbee-herdsman/src/adapter/z-stack/adapter/zStackAdapter.ts:411:23)
                      at Queue.execute (/opt/iobroker/node_modules/zigbee-herdsman/src/utils/queue.ts:35:20)
                      at Request.send (/opt/iobroker/node_modules/zigbee-herdsman/src/controller/helpers/request.ts:79:20)
                      at Endpoint.zclCommand (/opt/iobroker/node_modules/zigbee-herdsman/src/controller/model/endpoint.ts:756:28)
                      at Endpoint.command (/opt/iobroker/node_modules/zigbee-herdsman/src/controller/model/endpoint.ts:587:24)
                      at Object.convertSet (/opt/iobroker/node_modules/zigbee-herdsman-converters/src/converters/toZigbee.ts:48:17)
                      at Object.convertSet (/opt/iobroker/node_modules/zigbee-herdsman-converters/src/converters/toZigbee.ts:1131:32)
                      at /opt/iobroker/node_modules/iobroker.zigbee/main.js:754:36
                  2024-05-07 07:00:03.779  - info: dwd.0 (5168) starting. Version 2.8.5 in /opt/iobroker/node_modules/iobroker.dwd, node: v18.20.0, js-controller: 5.0.19
                  2024-05-07 07:00:05.090  - info: trashschedule.0 (3331) Setting "actionNeeded" flag for type.biomüll.actionNeeded to true (???)
                  2024-05-07 07:00:05.113  - info: trashschedule.0 (3331) Setting "actionNeeded" flag for type.altpapier.actionNeeded to true (???)
                  2024-05-07 07:00:07.050  - info: dwd.0 (5168) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
                  2024-05-07 07:00:07.608  - info: host.raspiBullseye instance system.adapter.dwd.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
                  2024-05-07 07:00:55.510  - info: zigbee.0 (5074) Zigbee: stop joining
                  2024-05-07 07:01:01.276  - warn: zigbee.0 (5074) Send command to 0x001788010db82a55 failed with: Code 205 (No network route)
                  2024-05-07 07:02:01.752  - warn: zigbee.0 (5074) Send command to 0x001788010db82a55 failed with: Code 205 (No network route)
                  2024-05-07 07:02:59.065  - info: shelly.0 (3059) [CoAP] Device 192.168.4.46 (shellyswitch25 / shellyswitch25-10521CF99772 / SHSW-25#10521CF99772#1) connected! Polltime set to 5 sec.
                  2024-05-07 07:03:44.949  - info: zigbee.0 (5074) Device '0x00124b00074e8fdf' announced itself
                  2024-05-07 07:03:52.469  - info: tuya.0 (3179) bf365e8431096d4a1cxcnl: Error on Reconnect (1): connect EHOSTUNREACH 192.168.4.33:6668
                  2024-05-07 07:04:12.810  - info: tuya.0 (3179) bf365e8431096d4a1cxcnl: Error on Reconnect (3): connect EHOSTUNREACH 192.168.4.33:6668
                  2024-05-07 07:04:55.883  - info: tuya.0 (3179) bf365e8431096d4a1cxcnl: Error on Reconnect (5): connect EHOSTUNREACH 192.168.4.33:6668
                  2024-05-07 07:05:00.038  - info: host.raspiBullseye instance system.adapter.daswetter.0 started with pid 5620
                  2024-05-07 07:05:03.206  - info: daswetter.0 (5620) starting. Version 3.1.13 in /opt/iobroker/node_modules/iobroker.daswetter, node: v18.20.0, js-controller: 5.0.19
                  2024-05-07 07:05:33.256  - info: zigbee.0 (5074) List of port: [{"path":"/dev/ttyACM0","manufacturer":"Texas Instruments","serialNumber":"L1100QXL","pnpId":"usb-Texas_Instruments_XDS110__03.00.00.20__Embed_with_CMSIS-DAP_L1100QXL-if00","vendorId":"0451","productId":"bef3"},{"path":"/dev/ttyACM1","manufacturer":"Texas Instruments","serialNumber":"L1100QXL","pnpId":"usb-Texas_Instruments_XDS110__03.00.00.20__Embed_with_CMSIS-DAP_L1100QXL-if03","vendorId":"0451","productId":"bef3"},{"path":"/dev/ttyS0"}]
                  2024-05-07 07:05:38.121  - info: daswetter.0 (5620) still wrong data structure from server received! repaired...
                  2024-05-07 07:05:46.134  - info: daswetter.0 (5620) Terminated (ADAPTER_REQUESTED_TERMINATION): All data handled, adapter stopped until next scheduled moment
                  2024-05-07 07:05:46.701  - info: daswetter.0 (5620) cleaned everything up...
                  2024-05-07 07:05:46.749  - info: host.raspiBullseye instance system.adapter.daswetter.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
                  2024-05-07 07:05:58.954  - info: tuya.0 (3179) bf365e8431096d4a1cxcnl: Error on Reconnect (7): connect EHOSTUNREACH 192.168.4.33:6668
                  2024-05-07 07:06:14.684  - warn: zigbee.0 (5074) Send command to 0x8418260000074b81 failed with: Code 205 (No network route)
                  2024-05-07 07:06:29.157  - info: tuya.0 (3179) bf365e8431096d4a1cxcnl: Connect locally to device
                  2024-05-07 07:06:29.158  - info: tuya.0 (3179) bf365e8431096d4a1cxcnl Init with IP=192.168.4.33, Key=54bab00521b02b77, Version=3.3
                  2024-05-07 07:06:32.234  - info: tuya.0 (3179) bf365e8431096d4a1cxcnl: Error on Reconnect (1): connect EHOSTUNREACH 192.168.4.33:6668
                  2024-05-07 07:06:36.920  - warn: zigbee.0 (5074) Send command to 0x8418260000074b81 failed with: Code 205 (No network route)
                  2024-05-07 07:06:55.306  - info: tuya.0 (3179) bf365e8431096d4a1cxcnl: Error on Reconnect (3): connect EHOSTUNREACH 192.168.4.33:6668
                  2024-05-07 07:06:59.013  - warn: zigbee.0 (5074) Send command to 0x8418260000074b81 failed with: Code 205 (No network route)
                  2024-05-07 07:07:38.378  - info: tuya.0 (3179) bf365e8431096d4a1cxcnl: Error on Reconnect (5): connect EHOSTUNREACH 192.168.4.33:6668
                  2024-05-07 07:15:00.072  - info: host.raspiBullseye instance system.adapter.dwd.0 started with pid 6512
                  2024-05-07 07:15:03.479  - info: dwd.0 (6512) starting. Version 2.8.5 in /opt/iobroker/node_modules/iobroker.dwd, node: v18.20.0, js-controller: 5.0.19
                  2024-05-07 07:15:05.216  - info: dwd.0 (6512) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
                  2024-05-07 07:15:05.754  - info: host.raspiBullseye instance system.adapter.dwd.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
                  2024-05-07 07:21:19.860  - info: web.0 (3218) <== Disconnect system.user.admin from ::ffff:192.168.4.87 vis.0
                  2024-05-07 07:22:14.342  - info: web.0 (3218) ==> Connected system.user.admin from ::ffff:192.168.4.87
                  2024-05-07 07:22:15.193  - info: web.0 (3218) <== Disconnect system.user.admin from ::ffff:192.168.4.87 vis.0
                  2024-05-07 07:22:15.274  - info: web.0 (3218) ==> Connected system.user.admin from ::ffff:192.168.4.87
                  2024-05-07 07:22:27.953  - info: web.0 (3218) <== Disconnect system.user.admin from ::ffff:192.168.4.87 vis.0
                  2024-05-07 07:24:03.222  - info: javascript.0 (2232) Stop script script.js.Rollladen.RollladenBlockly_NEU_4
                  2024-05-07 07:24:03.278  - info: javascript.0 (2232) Start javascript script.js.Rollladen.RollladenBlockly_NEU_4
                  2024-05-07 07:24:03.305  - info: javascript.0 (2232) script.js.Rollladen.RollladenBlockly_NEU_4: registered 0 subscriptions, 0 schedules, 0 messages, 0 logs and 0 file subscriptions
                  2024-05-07 07:24:03.310  - info: javascript.0 (2232) script.js.Rollladen.RollladenBlockly_NEU_4: [
                    {
                      Name: 'ROL_EG_WC',
                      objAddr: 'shelly.0.SHSW-25#10521CF99772#1.Position'
                    },
                    {
                      Name: 'ROL_EG_KUE',
                      objAddr: 'shelly.0.SHSW-25#483FDA7601B9#1.Position'
                    },
                    { Name: 'ROL_EG_TER_L', objAddr: 'hm-rpc.0.MEQ1732299.1.LEVEL' },
                    { Name: 'ROL_EG_TER_R', objAddr: 'hm-rpc.0.MEQ1730298.1.LEVEL' },
                    { Name: 'ROL_EG_WZ_O', objAddr: 'hm-rpc.0.NEQ0082126.1.LEVEL' },
                    { Name: 'ROL_EG_BUE_W', objAddr: 'hm-rpc.0.NEQ0078657.1.LEVEL' },
                    { Name: 'ROL_EG_BUE_N', objAddr: 'hm-rpc.0.NEQ0082108.1.LEVEL' }
                  ]
                  
                  .. jede Menge gelöscht ..
                  
                  2024-05-07 09:25:29.001  - info: bydhvs.0 (3411) Received, Packet: 3 Data: 010306001302000000a50e
                  2024-05-07 09:25:52.823  - info: zigbee.0 (5074) List of port: [{"path":"/dev/ttyACM0","manufacturer":"Texas Instruments","serialNumber":"L1100QXL","pnpId":"usb-Texas_Instruments_XDS110__03.00.00.20__Embed_with_CMSIS-DAP_L1100QXL-if00","vendorId":"0451","productId":"bef3"},{"path":"/dev/ttyACM1","manufacturer":"Texas Instruments","serialNumber":"L1100QXL","pnpId":"usb-Texas_Instruments_XDS110__03.00.00.20__Embed_with_CMSIS-DAP_L1100QXL-if03","vendorId":"0451","productId":"bef3"},{"path":"/dev/ttyS0"}]
                  2024-05-07 09:25:52.823  - info: zigbee.0 (5074) List of port: [{"path":"/dev/ttyACM0","manufacturer":"Texas Instruments","serialNumber":"L1100QXL","pnpId":"usb-Texas_Instruments_XDS110__03.00.00.20__Embed_with_CMSIS-DAP_L1100QXL-if00","vendorId":"0451","productId":"bef3"},{"path":"/dev/ttyACM1","manufacturer":"Texas Instruments","serialNumber":"L1100QXL","pnpId":"usb-Texas_Instruments_XDS110__03.00.00.20__Embed_with_CMSIS-DAP_L1100QXL-if03","vendorId":"0451","productId":"bef3"},{"path":"/dev/ttyS0"}]
                  2024-05-07 09:26:26.819  - warn: zigbee.0 (5074) Send command to 0x001788010db82a55 failed with: Code 205 (No network route)
                  2024-05-07 09:26:26.819  - warn: zigbee.0 (5074) Send command to 0x001788010db82a55 failed with: Code 205 (No network route)
                  2024-05-07 09:26:28.489  - info: bydhvs.0 (3411) Received, Packet: 1 Data: 0103cc50303330543032305a32323036303731343239787878787803120313031a01000013020000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000012345a02031a000c0000ffff0000ffff0000ffff0000ffff0000ffff0000ffff0000ffff0000ffff0000ffff000000001805070727052cd1
                  2024-05-07 09:26:28.758  - info: bydhvs.0 (3411) Received, Packet: 2 Data: 0103320009014601410062000079b8001300110011000003130000000000000902000279ea3bf500003143000000ff00004000042cef6a
                  2024-05-07 09:26:29.016  - info: bydhvs.0 (3411) Received, Packet: 3 Data: 010306001302000000a50e
                  2024-05-07 09:26:28.489  - info: bydhvs.0 (3411) Received, Packet: 1 Data: 0103cc50303330543032305a32323036303731343239787878787803120313031a01000013020000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000012345a02031a000c0000ffff0000ffff0000ffff0000ffff0000ffff0000ffff0000ffff0000ffff0000ffff000000001805070727052cd1
                  2024-05-07 09:26:28.758  - info: bydhvs.0 (3411) Received, Packet: 2 Data: 0103320009014601410062000079b8001300110011000003130000000000000902000279ea3bf500003143000000ff00004000042cef6a
                  2024-05-07 09:26:29.016  - info: bydhvs.0 (3411) Received, Packet: 3 Data: 010306001302000000a50e
                  2024-05-07 09:26:47.118  - info: host.raspiBullseye stopInstance system.adapter.zigbee.0 (force=false, process=true)
                  2024-05-07 09:26:47.144  - info: zigbee.0 (5074) Got terminate signal TERMINATE_YOURSELF
                  2024-05-07 09:26:47.198  - info: host.raspiBullseye stopInstance system.adapter.zigbee.0 send kill signal
                  2024-05-07 09:26:47.147  - info: zigbee.0 (5074) cleaned everything up...
                  2024-05-07 09:26:47.149  - info: zigbee.0 (5074) Zigbee: disabling joining new devices.
                  2024-05-07 09:26:47.651  - info: zigbee.0 (5074) terminating
                  2024-05-07 09:26:47.653  - info: zigbee.0 (5074) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
                  2024-05-07 09:26:47.118  - info: host.raspiBullseye stopInstance system.adapter.zigbee.0 (force=false, process=true)
                  2024-05-07 09:26:47.144  - info: zigbee.0 (5074) Got terminate signal TERMINATE_YOURSELF
                  2024-05-07 09:26:47.198  - info: host.raspiBullseye stopInstance system.adapter.zigbee.0 send kill signal
                  2024-05-07 09:26:47.147  - info: zigbee.0 (5074) cleaned everything up...
                  2024-05-07 09:26:47.149  - info: zigbee.0 (5074) Zigbee: disabling joining new devices.
                  2024-05-07 09:26:47.651  - info: zigbee.0 (5074) terminating
                  2024-05-07 09:26:47.653  - info: zigbee.0 (5074) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
                  2024-05-07 09:26:48.245  - info: host.raspiBullseye stopInstance system.adapter.zigbee.0 killing pid 5074
                  2024-05-07 09:26:48.510  - info: host.raspiBullseye instance system.adapter.zigbee.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
                  2024-05-07 09:26:48.245  - info: host.raspiBullseye stopInstance system.adapter.zigbee.0 killing pid 5074
                  2024-05-07 09:26:48.510  - info: host.raspiBullseye instance system.adapter.zigbee.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
                  2024-05-07 09:26:50.437  - info: host.raspiBullseye instance system.adapter.zigbee.0 started with pid 18539
                  2024-05-07 09:26:50.437  - info: host.raspiBullseye instance system.adapter.zigbee.0 started with pid 18539
                  2024-05-07 09:26:56.663  - info: zigbee.0 (18539) starting. Version 1.10.3 in /opt/iobroker/node_modules/iobroker.zigbee, node: v18.20.0, js-controller: 5.0.19
                  2024-05-07 09:26:56.814  - info: zigbee.0 (18539) delete old Backup files. keep only last 10
                  2024-05-07 09:26:56.817  - info: zigbee.0 (18539) Starting Zigbee  npm ...
                  2024-05-07 09:26:57.361  - info: zigbee.0 (18539) Installed Version: iobroker.zigbee@1.10.3
                  2024-05-07 09:26:56.663  - info: zigbee.0 (18539) starting. Version 1.10.3 in /opt/iobroker/node_modules/iobroker.zigbee, node: v18.20.0, js-controller: 5.0.19
                  2024-05-07 09:26:56.814  - info: zigbee.0 (18539) delete old Backup files. keep only last 10
                  2024-05-07 09:26:56.817  - info: zigbee.0 (18539) Starting Zigbee  npm ...
                  2024-05-07 09:26:57.361  - info: zigbee.0 (18539) Installed Version: iobroker.zigbee@1.10.3
                  2024-05-07 09:26:58.578  - info: zigbee.0 (18539) Coordinator firmware version: {"type":"zStack3x0","meta":{"transportrev":2,"product":1,"majorrel":2,"minorrel":7,"maintrel":1,"revision":20220219}}
                  2024-05-07 09:26:58.587  - info: zigbee.0 (18539) Unable to disable LED, unsupported function.
                  2024-05-07 09:26:58.621  - info: zigbee.0 (18539)   --> transmitPower : high
                  2024-05-07 09:26:58.639  - info: zigbee.0 (18539) Currently 14 devices are joined:
                  2024-05-07 09:26:58.795  - info: zigbee.0 (18539) 0x00124b0008a50109 (addr 52361): AV2010/24 - SMaBiT (Bitron Video) Optical smoke detector (hardware version v1) (EndDevice)
                  2024-05-07 09:26:58.800  - info: zigbee.0 (18539) 0x00124b000621ad0e (addr 36173): AV2010/29 - SMaBiT (Bitron Video) Outdoor siren (EndDevice)
                  2024-05-07 09:26:58.802  - info: zigbee.0 (18539) 0x00124b00074e8fdf (addr 6545): AV2010/24 - SMaBiT (Bitron Video) Optical smoke detector (hardware version v1) (EndDevice)
                  2024-05-07 09:26:58.805  - info: zigbee.0 (18539) 0x00124b00077b7fe8 (addr 3558): AV2010/24 - SMaBiT (Bitron Video) Optical smoke detector (hardware version v1) (EndDevice)
                  2024-05-07 09:26:58.807  - info: zigbee.0 (18539) 0x00124b0008a68663 (addr 32039): AV2010/24 - SMaBiT (Bitron Video) Optical smoke detector (hardware version v1) (EndDevice)
                  2024-05-07 09:26:58.810  - info: zigbee.0 (18539) 0x00124b0008e7395c (addr 46194): AV2010/24 - SMaBiT (Bitron Video) Optical smoke detector (hardware version v1) (EndDevice)
                  2024-05-07 09:26:58.813  - info: zigbee.0 (18539) 0x00124b00090da34c (addr 58423): AV2010/24 - SMaBiT (Bitron Video) Optical smoke detector (hardware version v1) (EndDevice)
                  2024-05-07 09:26:58.815  - info: zigbee.0 (18539) 0x00124b0008e73540 (addr 25642): AV2010/24 - SMaBiT (Bitron Video) Optical smoke detector (hardware version v1) (EndDevice)
                  2024-05-07 09:26:58.819  - info: zigbee.0 (18539) 0x8418260000074b81 (addr 33976): AC03641 - OSRAM LIGHTIFY LED Classic A60 clear (Router)
                  2024-05-07 09:26:58.821  - info: zigbee.0 (18539) 0x841826000007fd2c (addr 57868): AB32840 - OSRAM LIGHTIFY LED Classic B40 tunable white (Router)
                  2024-05-07 09:26:58.824  - info: zigbee.0 (18539) 0x841826000007feec (addr 53249): AB32840 - OSRAM LIGHTIFY LED Classic B40 tunable white (Router)
                  2024-05-07 09:26:58.827  - info: zigbee.0 (18539) 0x8418260000ca4b3f (addr 43907): AA70155 - OSRAM LIGHTIFY LED A19 tunable white / Classic A60 TW (Router)
                  2024-05-07 09:26:58.830  - info: zigbee.0 (18539) 0x001788010278c53e (addr 65419): 9290012573A - Philips Hue white and color ambiance E26/E27/E14 (Router)
                  2024-05-07 09:26:58.832  - info: zigbee.0 (18539) 0x001788010db82a55 (addr 143): 9290024406A - Philips Hue P45 light bulb (Router)
                  2024-05-07 09:26:58.833  - info: zigbee.0 (18539) Zigbee started
                  2024-05-07 09:26:58.949  - info: zigbee.0 (18539) debug devices set to []
                  2024-05-07 09:26:58.578  - info: zigbee.0 (18539) Coordinator firmware version: {"type":"zStack3x0","meta":{"transportrev":2,"product":1,"majorrel":2,"minorrel":7,"maintrel":1,"revision":20220219}}
                  2024-05-07 09:26:58.587  - info: zigbee.0 (18539) Unable to disable LED, unsupported function.
                  2024-05-07 09:26:58.621  - info: zigbee.0 (18539)   --> transmitPower : high
                  2024-05-07 09:26:58.639  - info: zigbee.0 (18539) Currently 14 devices are joined:
                  2024-05-07 09:26:58.795  - info: zigbee.0 (18539) 0x00124b0008a50109 (addr 52361): AV2010/24 - SMaBiT (Bitron Video) Optical smoke detector (hardware version v1) (EndDevice)
                  2024-05-07 09:26:58.800  - info: zigbee.0 (18539) 0x00124b000621ad0e (addr 36173): AV2010/29 - SMaBiT (Bitron Video) Outdoor siren (EndDevice)
                  2024-05-07 09:26:58.802  - info: zigbee.0 (18539) 0x00124b00074e8fdf (addr 6545): AV2010/24 - SMaBiT (Bitron Video) Optical smoke detector (hardware version v1) (EndDevice)
                  2024-05-07 09:26:58.805  - info: zigbee.0 (18539) 0x00124b00077b7fe8 (addr 3558): AV2010/24 - SMaBiT (Bitron Video) Optical smoke detector (hardware version v1) (EndDevice)
                  2024-05-07 09:26:58.807  - info: zigbee.0 (18539) 0x00124b0008a68663 (addr 32039): AV2010/24 - SMaBiT (Bitron Video) Optical smoke detector (hardware version v1) (EndDevice)
                  2024-05-07 09:26:58.810  - info: zigbee.0 (18539) 0x00124b0008e7395c (addr 46194): AV2010/24 - SMaBiT (Bitron Video) Optical smoke detector (hardware version v1) (EndDevice)
                  2024-05-07 09:26:58.813  - info: zigbee.0 (18539) 0x00124b00090da34c (addr 58423): AV2010/24 - SMaBiT (Bitron Video) Optical smoke detector (hardware version v1) (EndDevice)
                  2024-05-07 09:26:58.815  - info: zigbee.0 (18539) 0x00124b0008e73540 (addr 25642): AV2010/24 - SMaBiT (Bitron Video) Optical smoke detector (hardware version v1) (EndDevice)
                  2024-05-07 09:26:58.819  - info: zigbee.0 (18539) 0x8418260000074b81 (addr 33976): AC03641 - OSRAM LIGHTIFY LED Classic A60 clear (Router)
                  2024-05-07 09:26:58.821  - info: zigbee.0 (18539) 0x841826000007fd2c (addr 57868): AB32840 - OSRAM LIGHTIFY LED Classic B40 tunable white (Router)
                  2024-05-07 09:26:58.824  - info: zigbee.0 (18539) 0x841826000007feec (addr 53249): AB32840 - OSRAM LIGHTIFY LED Classic B40 tunable white (Router)
                  2024-05-07 09:26:58.827  - info: zigbee.0 (18539) 0x8418260000ca4b3f (addr 43907): AA70155 - OSRAM LIGHTIFY LED A19 tunable white / Classic A60 TW (Router)
                  2024-05-07 09:26:58.830  - info: zigbee.0 (18539) 0x001788010278c53e (addr 65419): 9290012573A - Philips Hue white and color ambiance E26/E27/E14 (Router)
                  2024-05-07 09:26:58.832  - info: zigbee.0 (18539) 0x001788010db82a55 (addr 143): 9290024406A - Philips Hue P45 light bulb (Router)
                  2024-05-07 09:26:58.833  - info: zigbee.0 (18539) Zigbee started
                  2024-05-07 09:26:58.949  - info: zigbee.0 (18539) debug devices set to []
                  2024-05-07 09:27:28.484  - info: bydhvs.0 (3411) Received, Packet: 1 Data: 0103cc50303330543032305a32323036303731343239787878787803120313031a01000013020000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000012345a02031a000c0000ffff0000ffff0000ffff0000ffff0000ffff0000ffff0000ffff0000ffff0000ffff000000001805070728052921
                  2024-05-07 09:27:28.752  - info: bydhvs.0 (3411) Received, Packet: 2 Data: 0103320009014601410062000079b8001300110011000003130000000000000902000279ea3bf500003143000000ff00004000042cef6a
                  2024-05-07 09:27:29.032  - info: bydhvs.0 (3411) Received, Packet: 3 Data: 010306001302000000a50e
                  2024-05-07 09:27:28.484  - info: bydhvs.0 (3411) Received, Packet: 1 Data: 0103cc50303330543032305a32323036303731343239787878787803120313031a01000013020000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000012345a02031a000c0000ffff0000ffff0000ffff0000ffff0000ffff0000ffff0000ffff0000ffff0000ffff000000001805070728052921
                  2024-05-07 09:27:28.752  - info: bydhvs.0 (3411) Received, Packet: 2 Data: 0103320009014601410062000079b8001300110011000003130000000000000902000279ea3bf500003143000000ff00004000042cef6a
                  2024-05-07 09:27:29.032  - info: bydhvs.0 (3411) Received, Packet: 3 Data: 010306001302000000a50e
                  2024-05-07 09:27:30.871  - info: zigbee.0 (18539) List of port: [{"path":"/dev/ttyACM0","manufacturer":"Texas Instruments","serialNumber":"L1100QXL","pnpId":"usb-Texas_Instruments_XDS110__03.00.00.20__Embed_with_CMSIS-DAP_L1100QXL-if00","vendorId":"0451","productId":"bef3"},{"path":"/dev/ttyACM1","manufacturer":"Texas Instruments","serialNumber":"L1100QXL","pnpId":"usb-Texas_Instruments_XDS110__03.00.00.20__Embed_with_CMSIS-DAP_L1100QXL-if03","vendorId":"0451","productId":"bef3"},{"path":"/dev/ttyS0"}]
                  2024-05-07 09:27:30.871  - info: zigbee.0 (18539) List of port: [{"path":"/dev/ttyACM0","manufacturer":"Texas Instruments","serialNumber":"L1100QXL","pnpId":"usb-Texas_Instruments_XDS110__03.00.00.20__Embed_with_CMSIS-DAP_L1100QXL-if00","vendorId":"0451","productId":"bef3"},{"path":"/dev/ttyACM1","manufacturer":"Texas Instruments","serialNumber":"L1100QXL","pnpId":"usb-Texas_Instruments_XDS110__03.00.00.20__Embed_with_CMSIS-DAP_L1100QXL-if03","vendorId":"0451","productId":"bef3"},{"path":"/dev/ttyS0"}]
                  2024-05-07 09:27:57.391  - warn: zigbee.0 (18539) Send command to 0x001788010db82a55 failed with: Code 205 (No network route)
                  2024-05-07 09:27:57.391  - warn: zigbee.0 (18539) Send command to 0x001788010db82a55 failed with: Code 205 (No network route)
                  2
                  

                  Raspberry Pi 5 mit 8GB + 120GB SSD + Coordinator COD-m + ioBroker ..

                  Samson71S MartinPM 2 Antworten Letzte Antwort
                  0
                  • L legro

                    @thomas-braun @arteck

                    In dem nachfolgenden Datenwust sind zwei Neustarts enthalten. Wie gesagt, für mich sind dies alles Böhmische Dörfer.

                    Last login: Tue May  7 09:15:52 on ttys000
                    
                    The default interactive shell is now zsh.
                    To update your account to use zsh, please run `chsh -s /bin/zsh`.
                    For more details, please visit https://support.apple.com/kb/HT208050.
                    Leanders-MacBook-Pro-Neu:~ leandergroben$ ssh pi@192.168.4.58
                    pi@192.168.4.58's password: 
                    Linux raspiBullseye 6.1.21-v8+ #1642 SMP PREEMPT Mon Apr  3 17:24:16 BST 2023 aarch64
                    
                    The programs included with the Debian GNU/Linux system are free software;
                    the exact distribution terms for each program are described in the
                    individual files in /usr/share/doc/*/copyright.
                    
                    Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
                    permitted by applicable law.
                    Last login: Tue May  7 09:18:12 2024 from 192.168.4.24
                    
                    Wi-Fi is currently blocked by rfkill.
                    Use raspi-config to set the country before use.
                    
                    pi@raspiBullseye:~ $ iob logs --watch
                    2024-05-07 06:55:28.708  - info: bydhvs.0 (3411) Received, Packet: 2 Data: 01033200080144013f0062000078f0001300110011000003130000000000000902000279223bf400003143000000ff00004000042c379d
                    2024-05-07 06:55:28.966  - info: bydhvs.0 (3411) Received, Packet: 3 Data: 010306001302000000a50e
                    2024-05-07 06:55:30.827  - warn: zigbee.0 (3201) Send command to 0x8418260000ca4b3f failed with: Code 205 (No network route)
                    2024-05-07 06:55:38.408  - info: zigbee.0 (3201) Zigbee: stop joining
                    2024-05-07 06:57:17.490  - warn: zigbee.0 (3201) Send command to 0x8418260000074b81 failed with: Code 205 (No network route)
                    2024-05-07 06:58:28.828  - info: zigbee.0 (3201) Device '0x8418260000074b81' announced itself
                    2024-05-07 06:59:07.186  - info: host.raspiBullseye stopInstance system.adapter.zigbee.0 (force=false, process=true)
                    2024-05-07 06:59:07.218  - info: zigbee.0 (3201) Got terminate signal TERMINATE_YOURSELF
                    2024-05-07 06:59:07.221  - info: zigbee.0 (3201) cleaned everything up...
                    2024-05-07 06:59:07.225  - info: zigbee.0 (3201) Zigbee: disabling joining new devices.
                    2024-05-07 06:59:07.531  - info: host.raspiBullseye stopInstance system.adapter.zigbee.0 send kill signal
                    2024-05-07 06:59:07.727  - info: zigbee.0 (3201) terminating
                    2024-05-07 06:59:07.731  - info: zigbee.0 (3201) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
                    2024-05-07 06:59:08.669  - info: host.raspiBullseye instance system.adapter.zigbee.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
                    2024-05-07 06:59:10.777  - info: host.raspiBullseye instance system.adapter.zigbee.0 started with pid 5074
                    2024-05-07 06:59:17.765  - info: zigbee.0 (5074) starting. Version 1.10.3 in /opt/iobroker/node_modules/iobroker.zigbee, node: v18.20.0, js-controller: 5.0.19
                    2024-05-07 06:59:17.930  - info: zigbee.0 (5074) delete old Backup files. keep only last 10
                    2024-05-07 06:59:17.933  - info: zigbee.0 (5074) Starting Zigbee  npm ...
                    2024-05-07 06:59:18.495  - info: zigbee.0 (5074) Installed Version: iobroker.zigbee@1.10.3
                    2024-05-07 06:59:19.625  - info: zigbee.0 (5074) Coordinator firmware version: {"type":"zStack3x0","meta":{"transportrev":2,"product":1,"majorrel":2,"minorrel":7,"maintrel":1,"revision":20220219}}
                    2024-05-07 06:59:19.633  - info: zigbee.0 (5074) Unable to disable LED, unsupported function.
                    2024-05-07 06:59:19.652  - info: zigbee.0 (5074)   --> transmitPower : high
                    2024-05-07 06:59:19.664  - info: zigbee.0 (5074) Currently 14 devices are joined:
                    2024-05-07 06:59:19.787  - info: zigbee.0 (5074) 0x00124b0008a50109 (addr 52361): AV2010/24 - SMaBiT (Bitron Video) Optical smoke detector (hardware version v1) (EndDevice)
                    2024-05-07 06:59:19.793  - info: zigbee.0 (5074) 0x00124b000621ad0e (addr 36173): AV2010/29 - SMaBiT (Bitron Video) Outdoor siren (EndDevice)
                    2024-05-07 06:59:19.795  - info: zigbee.0 (5074) 0x00124b00074e8fdf (addr 6545): AV2010/24 - SMaBiT (Bitron Video) Optical smoke detector (hardware version v1) (EndDevice)
                    2024-05-07 06:59:19.797  - info: zigbee.0 (5074) 0x00124b00077b7fe8 (addr 3558): AV2010/24 - SMaBiT (Bitron Video) Optical smoke detector (hardware version v1) (EndDevice)
                    2024-05-07 06:59:19.798  - info: zigbee.0 (5074) 0x00124b0008a68663 (addr 32039): AV2010/24 - SMaBiT (Bitron Video) Optical smoke detector (hardware version v1) (EndDevice)
                    2024-05-07 06:59:19.800  - info: zigbee.0 (5074) 0x00124b0008e7395c (addr 46194): AV2010/24 - SMaBiT (Bitron Video) Optical smoke detector (hardware version v1) (EndDevice)
                    2024-05-07 06:59:19.802  - info: zigbee.0 (5074) 0x00124b00090da34c (addr 58423): AV2010/24 - SMaBiT (Bitron Video) Optical smoke detector (hardware version v1) (EndDevice)
                    2024-05-07 06:59:19.804  - info: zigbee.0 (5074) 0x00124b0008e73540 (addr 25642): AV2010/24 - SMaBiT (Bitron Video) Optical smoke detector (hardware version v1) (EndDevice)
                    2024-05-07 06:59:19.806  - info: zigbee.0 (5074) 0x8418260000074b81 (addr 33976): AC03641 - OSRAM LIGHTIFY LED Classic A60 clear (Router)
                    2024-05-07 06:59:19.808  - info: zigbee.0 (5074) 0x841826000007fd2c (addr 57868): AB32840 - OSRAM LIGHTIFY LED Classic B40 tunable white (Router)
                    2024-05-07 06:59:19.809  - info: zigbee.0 (5074) 0x841826000007feec (addr 53249): AB32840 - OSRAM LIGHTIFY LED Classic B40 tunable white (Router)
                    2024-05-07 06:59:19.811  - info: zigbee.0 (5074) 0x8418260000ca4b3f (addr 43907): AA70155 - OSRAM LIGHTIFY LED A19 tunable white / Classic A60 TW (Router)
                    2024-05-07 06:59:19.813  - info: zigbee.0 (5074) 0x001788010278c53e (addr 65419): 9290012573A - Philips Hue white and color ambiance E26/E27/E14 (Router)
                    2024-05-07 06:59:19.815  - info: zigbee.0 (5074) 0x001788010db82a55 (addr 143): 9290024406A - Philips Hue P45 light bulb (Router)
                    2024-05-07 06:59:19.816  - info: zigbee.0 (5074) Zigbee started
                    2024-05-07 06:59:19.911  - info: zigbee.0 (5074) debug devices set to []
                    2024-05-07 06:59:24.421  - info: zigbee.0 (5074) List of port: [{"path":"/dev/ttyACM0","manufacturer":"Texas Instruments","serialNumber":"L1100QXL","pnpId":"usb-Texas_Instruments_XDS110__03.00.00.20__Embed_with_CMSIS-DAP_L1100QXL-if00","vendorId":"0451","productId":"bef3"},{"path":"/dev/ttyACM1","manufacturer":"Texas Instruments","serialNumber":"L1100QXL","pnpId":"usb-Texas_Instruments_XDS110__03.00.00.20__Embed_with_CMSIS-DAP_L1100QXL-if03","vendorId":"0451","productId":"bef3"},{"path":"/dev/ttyS0"}]
                    2024-05-07 06:59:52.425  - error: zigbee.0 (5074) Error 225 on send command to 0x001788010db82a55. Error: Error: ZCL command 0x001788010db82a55/11 genOnOff.on({}, {"timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":false,"direction":0,"srcEndpoint":null,"reservedBits":0,"manufacturerCode":null,"transactionSequenceNumber":null,"writeUndiv":false}) failed (Data request failed with error: 'MAC channel access failure' (225))
                        at ZStackAdapter.sendZclFrameToEndpointInternal (/opt/iobroker/node_modules/zigbee-herdsman/src/adapter/z-stack/adapter/zStackAdapter.ts:411:23)
                        at Queue.execute (/opt/iobroker/node_modules/zigbee-herdsman/src/utils/queue.ts:35:20)
                        at Request.send (/opt/iobroker/node_modules/zigbee-herdsman/src/controller/helpers/request.ts:79:20)
                        at Endpoint.zclCommand (/opt/iobroker/node_modules/zigbee-herdsman/src/controller/model/endpoint.ts:756:28)
                        at Endpoint.command (/opt/iobroker/node_modules/zigbee-herdsman/src/controller/model/endpoint.ts:587:24)
                        at Object.convertSet (/opt/iobroker/node_modules/zigbee-herdsman-converters/src/converters/toZigbee.ts:48:17)
                        at Object.convertSet (/opt/iobroker/node_modules/zigbee-herdsman-converters/src/converters/toZigbee.ts:1131:32)
                        at /opt/iobroker/node_modules/iobroker.zigbee/main.js:754:36
                    2024-05-07 06:59:54.242  - info: zigbee.0 (5074) Zigbee: allowing new devices to join.
                    2024-05-07 07:00:00.228  - info: host.raspiBullseye instance system.adapter.dwd.0 started with pid 5168
                    2024-05-07 07:00:00.843  - error: zigbee.0 (5074) Error 225 on send command to 0x001788010db82a55. Error: Error: ZCL command 0x001788010db82a55/11 genOnOff.off({}, {"timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":false,"direction":0,"srcEndpoint":null,"reservedBits":0,"manufacturerCode":null,"transactionSequenceNumber":null,"writeUndiv":false}) failed (Data request failed with error: 'MAC channel access failure' (225))
                        at ZStackAdapter.sendZclFrameToEndpointInternal (/opt/iobroker/node_modules/zigbee-herdsman/src/adapter/z-stack/adapter/zStackAdapter.ts:411:23)
                        at Queue.execute (/opt/iobroker/node_modules/zigbee-herdsman/src/utils/queue.ts:35:20)
                        at Request.send (/opt/iobroker/node_modules/zigbee-herdsman/src/controller/helpers/request.ts:79:20)
                        at Endpoint.zclCommand (/opt/iobroker/node_modules/zigbee-herdsman/src/controller/model/endpoint.ts:756:28)
                        at Endpoint.command (/opt/iobroker/node_modules/zigbee-herdsman/src/controller/model/endpoint.ts:587:24)
                        at Object.convertSet (/opt/iobroker/node_modules/zigbee-herdsman-converters/src/converters/toZigbee.ts:48:17)
                        at Object.convertSet (/opt/iobroker/node_modules/zigbee-herdsman-converters/src/converters/toZigbee.ts:1131:32)
                        at /opt/iobroker/node_modules/iobroker.zigbee/main.js:754:36
                    2024-05-07 07:00:03.779  - info: dwd.0 (5168) starting. Version 2.8.5 in /opt/iobroker/node_modules/iobroker.dwd, node: v18.20.0, js-controller: 5.0.19
                    2024-05-07 07:00:05.090  - info: trashschedule.0 (3331) Setting "actionNeeded" flag for type.biomüll.actionNeeded to true (???)
                    2024-05-07 07:00:05.113  - info: trashschedule.0 (3331) Setting "actionNeeded" flag for type.altpapier.actionNeeded to true (???)
                    2024-05-07 07:00:07.050  - info: dwd.0 (5168) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
                    2024-05-07 07:00:07.608  - info: host.raspiBullseye instance system.adapter.dwd.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
                    2024-05-07 07:00:55.510  - info: zigbee.0 (5074) Zigbee: stop joining
                    2024-05-07 07:01:01.276  - warn: zigbee.0 (5074) Send command to 0x001788010db82a55 failed with: Code 205 (No network route)
                    2024-05-07 07:02:01.752  - warn: zigbee.0 (5074) Send command to 0x001788010db82a55 failed with: Code 205 (No network route)
                    2024-05-07 07:02:59.065  - info: shelly.0 (3059) [CoAP] Device 192.168.4.46 (shellyswitch25 / shellyswitch25-10521CF99772 / SHSW-25#10521CF99772#1) connected! Polltime set to 5 sec.
                    2024-05-07 07:03:44.949  - info: zigbee.0 (5074) Device '0x00124b00074e8fdf' announced itself
                    2024-05-07 07:03:52.469  - info: tuya.0 (3179) bf365e8431096d4a1cxcnl: Error on Reconnect (1): connect EHOSTUNREACH 192.168.4.33:6668
                    2024-05-07 07:04:12.810  - info: tuya.0 (3179) bf365e8431096d4a1cxcnl: Error on Reconnect (3): connect EHOSTUNREACH 192.168.4.33:6668
                    2024-05-07 07:04:55.883  - info: tuya.0 (3179) bf365e8431096d4a1cxcnl: Error on Reconnect (5): connect EHOSTUNREACH 192.168.4.33:6668
                    2024-05-07 07:05:00.038  - info: host.raspiBullseye instance system.adapter.daswetter.0 started with pid 5620
                    2024-05-07 07:05:03.206  - info: daswetter.0 (5620) starting. Version 3.1.13 in /opt/iobroker/node_modules/iobroker.daswetter, node: v18.20.0, js-controller: 5.0.19
                    2024-05-07 07:05:33.256  - info: zigbee.0 (5074) List of port: [{"path":"/dev/ttyACM0","manufacturer":"Texas Instruments","serialNumber":"L1100QXL","pnpId":"usb-Texas_Instruments_XDS110__03.00.00.20__Embed_with_CMSIS-DAP_L1100QXL-if00","vendorId":"0451","productId":"bef3"},{"path":"/dev/ttyACM1","manufacturer":"Texas Instruments","serialNumber":"L1100QXL","pnpId":"usb-Texas_Instruments_XDS110__03.00.00.20__Embed_with_CMSIS-DAP_L1100QXL-if03","vendorId":"0451","productId":"bef3"},{"path":"/dev/ttyS0"}]
                    2024-05-07 07:05:38.121  - info: daswetter.0 (5620) still wrong data structure from server received! repaired...
                    2024-05-07 07:05:46.134  - info: daswetter.0 (5620) Terminated (ADAPTER_REQUESTED_TERMINATION): All data handled, adapter stopped until next scheduled moment
                    2024-05-07 07:05:46.701  - info: daswetter.0 (5620) cleaned everything up...
                    2024-05-07 07:05:46.749  - info: host.raspiBullseye instance system.adapter.daswetter.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
                    2024-05-07 07:05:58.954  - info: tuya.0 (3179) bf365e8431096d4a1cxcnl: Error on Reconnect (7): connect EHOSTUNREACH 192.168.4.33:6668
                    2024-05-07 07:06:14.684  - warn: zigbee.0 (5074) Send command to 0x8418260000074b81 failed with: Code 205 (No network route)
                    2024-05-07 07:06:29.157  - info: tuya.0 (3179) bf365e8431096d4a1cxcnl: Connect locally to device
                    2024-05-07 07:06:29.158  - info: tuya.0 (3179) bf365e8431096d4a1cxcnl Init with IP=192.168.4.33, Key=54bab00521b02b77, Version=3.3
                    2024-05-07 07:06:32.234  - info: tuya.0 (3179) bf365e8431096d4a1cxcnl: Error on Reconnect (1): connect EHOSTUNREACH 192.168.4.33:6668
                    2024-05-07 07:06:36.920  - warn: zigbee.0 (5074) Send command to 0x8418260000074b81 failed with: Code 205 (No network route)
                    2024-05-07 07:06:55.306  - info: tuya.0 (3179) bf365e8431096d4a1cxcnl: Error on Reconnect (3): connect EHOSTUNREACH 192.168.4.33:6668
                    2024-05-07 07:06:59.013  - warn: zigbee.0 (5074) Send command to 0x8418260000074b81 failed with: Code 205 (No network route)
                    2024-05-07 07:07:38.378  - info: tuya.0 (3179) bf365e8431096d4a1cxcnl: Error on Reconnect (5): connect EHOSTUNREACH 192.168.4.33:6668
                    2024-05-07 07:15:00.072  - info: host.raspiBullseye instance system.adapter.dwd.0 started with pid 6512
                    2024-05-07 07:15:03.479  - info: dwd.0 (6512) starting. Version 2.8.5 in /opt/iobroker/node_modules/iobroker.dwd, node: v18.20.0, js-controller: 5.0.19
                    2024-05-07 07:15:05.216  - info: dwd.0 (6512) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
                    2024-05-07 07:15:05.754  - info: host.raspiBullseye instance system.adapter.dwd.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
                    2024-05-07 07:21:19.860  - info: web.0 (3218) <== Disconnect system.user.admin from ::ffff:192.168.4.87 vis.0
                    2024-05-07 07:22:14.342  - info: web.0 (3218) ==> Connected system.user.admin from ::ffff:192.168.4.87
                    2024-05-07 07:22:15.193  - info: web.0 (3218) <== Disconnect system.user.admin from ::ffff:192.168.4.87 vis.0
                    2024-05-07 07:22:15.274  - info: web.0 (3218) ==> Connected system.user.admin from ::ffff:192.168.4.87
                    2024-05-07 07:22:27.953  - info: web.0 (3218) <== Disconnect system.user.admin from ::ffff:192.168.4.87 vis.0
                    2024-05-07 07:24:03.222  - info: javascript.0 (2232) Stop script script.js.Rollladen.RollladenBlockly_NEU_4
                    2024-05-07 07:24:03.278  - info: javascript.0 (2232) Start javascript script.js.Rollladen.RollladenBlockly_NEU_4
                    2024-05-07 07:24:03.305  - info: javascript.0 (2232) script.js.Rollladen.RollladenBlockly_NEU_4: registered 0 subscriptions, 0 schedules, 0 messages, 0 logs and 0 file subscriptions
                    2024-05-07 07:24:03.310  - info: javascript.0 (2232) script.js.Rollladen.RollladenBlockly_NEU_4: [
                      {
                        Name: 'ROL_EG_WC',
                        objAddr: 'shelly.0.SHSW-25#10521CF99772#1.Position'
                      },
                      {
                        Name: 'ROL_EG_KUE',
                        objAddr: 'shelly.0.SHSW-25#483FDA7601B9#1.Position'
                      },
                      { Name: 'ROL_EG_TER_L', objAddr: 'hm-rpc.0.MEQ1732299.1.LEVEL' },
                      { Name: 'ROL_EG_TER_R', objAddr: 'hm-rpc.0.MEQ1730298.1.LEVEL' },
                      { Name: 'ROL_EG_WZ_O', objAddr: 'hm-rpc.0.NEQ0082126.1.LEVEL' },
                      { Name: 'ROL_EG_BUE_W', objAddr: 'hm-rpc.0.NEQ0078657.1.LEVEL' },
                      { Name: 'ROL_EG_BUE_N', objAddr: 'hm-rpc.0.NEQ0082108.1.LEVEL' }
                    ]
                    
                    .. jede Menge gelöscht ..
                    
                    2024-05-07 09:25:29.001  - info: bydhvs.0 (3411) Received, Packet: 3 Data: 010306001302000000a50e
                    2024-05-07 09:25:52.823  - info: zigbee.0 (5074) List of port: [{"path":"/dev/ttyACM0","manufacturer":"Texas Instruments","serialNumber":"L1100QXL","pnpId":"usb-Texas_Instruments_XDS110__03.00.00.20__Embed_with_CMSIS-DAP_L1100QXL-if00","vendorId":"0451","productId":"bef3"},{"path":"/dev/ttyACM1","manufacturer":"Texas Instruments","serialNumber":"L1100QXL","pnpId":"usb-Texas_Instruments_XDS110__03.00.00.20__Embed_with_CMSIS-DAP_L1100QXL-if03","vendorId":"0451","productId":"bef3"},{"path":"/dev/ttyS0"}]
                    2024-05-07 09:25:52.823  - info: zigbee.0 (5074) List of port: [{"path":"/dev/ttyACM0","manufacturer":"Texas Instruments","serialNumber":"L1100QXL","pnpId":"usb-Texas_Instruments_XDS110__03.00.00.20__Embed_with_CMSIS-DAP_L1100QXL-if00","vendorId":"0451","productId":"bef3"},{"path":"/dev/ttyACM1","manufacturer":"Texas Instruments","serialNumber":"L1100QXL","pnpId":"usb-Texas_Instruments_XDS110__03.00.00.20__Embed_with_CMSIS-DAP_L1100QXL-if03","vendorId":"0451","productId":"bef3"},{"path":"/dev/ttyS0"}]
                    2024-05-07 09:26:26.819  - warn: zigbee.0 (5074) Send command to 0x001788010db82a55 failed with: Code 205 (No network route)
                    2024-05-07 09:26:26.819  - warn: zigbee.0 (5074) Send command to 0x001788010db82a55 failed with: Code 205 (No network route)
                    2024-05-07 09:26:28.489  - info: bydhvs.0 (3411) Received, Packet: 1 Data: 0103cc50303330543032305a32323036303731343239787878787803120313031a01000013020000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000012345a02031a000c0000ffff0000ffff0000ffff0000ffff0000ffff0000ffff0000ffff0000ffff0000ffff000000001805070727052cd1
                    2024-05-07 09:26:28.758  - info: bydhvs.0 (3411) Received, Packet: 2 Data: 0103320009014601410062000079b8001300110011000003130000000000000902000279ea3bf500003143000000ff00004000042cef6a
                    2024-05-07 09:26:29.016  - info: bydhvs.0 (3411) Received, Packet: 3 Data: 010306001302000000a50e
                    2024-05-07 09:26:28.489  - info: bydhvs.0 (3411) Received, Packet: 1 Data: 0103cc50303330543032305a32323036303731343239787878787803120313031a01000013020000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000012345a02031a000c0000ffff0000ffff0000ffff0000ffff0000ffff0000ffff0000ffff0000ffff0000ffff000000001805070727052cd1
                    2024-05-07 09:26:28.758  - info: bydhvs.0 (3411) Received, Packet: 2 Data: 0103320009014601410062000079b8001300110011000003130000000000000902000279ea3bf500003143000000ff00004000042cef6a
                    2024-05-07 09:26:29.016  - info: bydhvs.0 (3411) Received, Packet: 3 Data: 010306001302000000a50e
                    2024-05-07 09:26:47.118  - info: host.raspiBullseye stopInstance system.adapter.zigbee.0 (force=false, process=true)
                    2024-05-07 09:26:47.144  - info: zigbee.0 (5074) Got terminate signal TERMINATE_YOURSELF
                    2024-05-07 09:26:47.198  - info: host.raspiBullseye stopInstance system.adapter.zigbee.0 send kill signal
                    2024-05-07 09:26:47.147  - info: zigbee.0 (5074) cleaned everything up...
                    2024-05-07 09:26:47.149  - info: zigbee.0 (5074) Zigbee: disabling joining new devices.
                    2024-05-07 09:26:47.651  - info: zigbee.0 (5074) terminating
                    2024-05-07 09:26:47.653  - info: zigbee.0 (5074) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
                    2024-05-07 09:26:47.118  - info: host.raspiBullseye stopInstance system.adapter.zigbee.0 (force=false, process=true)
                    2024-05-07 09:26:47.144  - info: zigbee.0 (5074) Got terminate signal TERMINATE_YOURSELF
                    2024-05-07 09:26:47.198  - info: host.raspiBullseye stopInstance system.adapter.zigbee.0 send kill signal
                    2024-05-07 09:26:47.147  - info: zigbee.0 (5074) cleaned everything up...
                    2024-05-07 09:26:47.149  - info: zigbee.0 (5074) Zigbee: disabling joining new devices.
                    2024-05-07 09:26:47.651  - info: zigbee.0 (5074) terminating
                    2024-05-07 09:26:47.653  - info: zigbee.0 (5074) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
                    2024-05-07 09:26:48.245  - info: host.raspiBullseye stopInstance system.adapter.zigbee.0 killing pid 5074
                    2024-05-07 09:26:48.510  - info: host.raspiBullseye instance system.adapter.zigbee.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
                    2024-05-07 09:26:48.245  - info: host.raspiBullseye stopInstance system.adapter.zigbee.0 killing pid 5074
                    2024-05-07 09:26:48.510  - info: host.raspiBullseye instance system.adapter.zigbee.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
                    2024-05-07 09:26:50.437  - info: host.raspiBullseye instance system.adapter.zigbee.0 started with pid 18539
                    2024-05-07 09:26:50.437  - info: host.raspiBullseye instance system.adapter.zigbee.0 started with pid 18539
                    2024-05-07 09:26:56.663  - info: zigbee.0 (18539) starting. Version 1.10.3 in /opt/iobroker/node_modules/iobroker.zigbee, node: v18.20.0, js-controller: 5.0.19
                    2024-05-07 09:26:56.814  - info: zigbee.0 (18539) delete old Backup files. keep only last 10
                    2024-05-07 09:26:56.817  - info: zigbee.0 (18539) Starting Zigbee  npm ...
                    2024-05-07 09:26:57.361  - info: zigbee.0 (18539) Installed Version: iobroker.zigbee@1.10.3
                    2024-05-07 09:26:56.663  - info: zigbee.0 (18539) starting. Version 1.10.3 in /opt/iobroker/node_modules/iobroker.zigbee, node: v18.20.0, js-controller: 5.0.19
                    2024-05-07 09:26:56.814  - info: zigbee.0 (18539) delete old Backup files. keep only last 10
                    2024-05-07 09:26:56.817  - info: zigbee.0 (18539) Starting Zigbee  npm ...
                    2024-05-07 09:26:57.361  - info: zigbee.0 (18539) Installed Version: iobroker.zigbee@1.10.3
                    2024-05-07 09:26:58.578  - info: zigbee.0 (18539) Coordinator firmware version: {"type":"zStack3x0","meta":{"transportrev":2,"product":1,"majorrel":2,"minorrel":7,"maintrel":1,"revision":20220219}}
                    2024-05-07 09:26:58.587  - info: zigbee.0 (18539) Unable to disable LED, unsupported function.
                    2024-05-07 09:26:58.621  - info: zigbee.0 (18539)   --> transmitPower : high
                    2024-05-07 09:26:58.639  - info: zigbee.0 (18539) Currently 14 devices are joined:
                    2024-05-07 09:26:58.795  - info: zigbee.0 (18539) 0x00124b0008a50109 (addr 52361): AV2010/24 - SMaBiT (Bitron Video) Optical smoke detector (hardware version v1) (EndDevice)
                    2024-05-07 09:26:58.800  - info: zigbee.0 (18539) 0x00124b000621ad0e (addr 36173): AV2010/29 - SMaBiT (Bitron Video) Outdoor siren (EndDevice)
                    2024-05-07 09:26:58.802  - info: zigbee.0 (18539) 0x00124b00074e8fdf (addr 6545): AV2010/24 - SMaBiT (Bitron Video) Optical smoke detector (hardware version v1) (EndDevice)
                    2024-05-07 09:26:58.805  - info: zigbee.0 (18539) 0x00124b00077b7fe8 (addr 3558): AV2010/24 - SMaBiT (Bitron Video) Optical smoke detector (hardware version v1) (EndDevice)
                    2024-05-07 09:26:58.807  - info: zigbee.0 (18539) 0x00124b0008a68663 (addr 32039): AV2010/24 - SMaBiT (Bitron Video) Optical smoke detector (hardware version v1) (EndDevice)
                    2024-05-07 09:26:58.810  - info: zigbee.0 (18539) 0x00124b0008e7395c (addr 46194): AV2010/24 - SMaBiT (Bitron Video) Optical smoke detector (hardware version v1) (EndDevice)
                    2024-05-07 09:26:58.813  - info: zigbee.0 (18539) 0x00124b00090da34c (addr 58423): AV2010/24 - SMaBiT (Bitron Video) Optical smoke detector (hardware version v1) (EndDevice)
                    2024-05-07 09:26:58.815  - info: zigbee.0 (18539) 0x00124b0008e73540 (addr 25642): AV2010/24 - SMaBiT (Bitron Video) Optical smoke detector (hardware version v1) (EndDevice)
                    2024-05-07 09:26:58.819  - info: zigbee.0 (18539) 0x8418260000074b81 (addr 33976): AC03641 - OSRAM LIGHTIFY LED Classic A60 clear (Router)
                    2024-05-07 09:26:58.821  - info: zigbee.0 (18539) 0x841826000007fd2c (addr 57868): AB32840 - OSRAM LIGHTIFY LED Classic B40 tunable white (Router)
                    2024-05-07 09:26:58.824  - info: zigbee.0 (18539) 0x841826000007feec (addr 53249): AB32840 - OSRAM LIGHTIFY LED Classic B40 tunable white (Router)
                    2024-05-07 09:26:58.827  - info: zigbee.0 (18539) 0x8418260000ca4b3f (addr 43907): AA70155 - OSRAM LIGHTIFY LED A19 tunable white / Classic A60 TW (Router)
                    2024-05-07 09:26:58.830  - info: zigbee.0 (18539) 0x001788010278c53e (addr 65419): 9290012573A - Philips Hue white and color ambiance E26/E27/E14 (Router)
                    2024-05-07 09:26:58.832  - info: zigbee.0 (18539) 0x001788010db82a55 (addr 143): 9290024406A - Philips Hue P45 light bulb (Router)
                    2024-05-07 09:26:58.833  - info: zigbee.0 (18539) Zigbee started
                    2024-05-07 09:26:58.949  - info: zigbee.0 (18539) debug devices set to []
                    2024-05-07 09:26:58.578  - info: zigbee.0 (18539) Coordinator firmware version: {"type":"zStack3x0","meta":{"transportrev":2,"product":1,"majorrel":2,"minorrel":7,"maintrel":1,"revision":20220219}}
                    2024-05-07 09:26:58.587  - info: zigbee.0 (18539) Unable to disable LED, unsupported function.
                    2024-05-07 09:26:58.621  - info: zigbee.0 (18539)   --> transmitPower : high
                    2024-05-07 09:26:58.639  - info: zigbee.0 (18539) Currently 14 devices are joined:
                    2024-05-07 09:26:58.795  - info: zigbee.0 (18539) 0x00124b0008a50109 (addr 52361): AV2010/24 - SMaBiT (Bitron Video) Optical smoke detector (hardware version v1) (EndDevice)
                    2024-05-07 09:26:58.800  - info: zigbee.0 (18539) 0x00124b000621ad0e (addr 36173): AV2010/29 - SMaBiT (Bitron Video) Outdoor siren (EndDevice)
                    2024-05-07 09:26:58.802  - info: zigbee.0 (18539) 0x00124b00074e8fdf (addr 6545): AV2010/24 - SMaBiT (Bitron Video) Optical smoke detector (hardware version v1) (EndDevice)
                    2024-05-07 09:26:58.805  - info: zigbee.0 (18539) 0x00124b00077b7fe8 (addr 3558): AV2010/24 - SMaBiT (Bitron Video) Optical smoke detector (hardware version v1) (EndDevice)
                    2024-05-07 09:26:58.807  - info: zigbee.0 (18539) 0x00124b0008a68663 (addr 32039): AV2010/24 - SMaBiT (Bitron Video) Optical smoke detector (hardware version v1) (EndDevice)
                    2024-05-07 09:26:58.810  - info: zigbee.0 (18539) 0x00124b0008e7395c (addr 46194): AV2010/24 - SMaBiT (Bitron Video) Optical smoke detector (hardware version v1) (EndDevice)
                    2024-05-07 09:26:58.813  - info: zigbee.0 (18539) 0x00124b00090da34c (addr 58423): AV2010/24 - SMaBiT (Bitron Video) Optical smoke detector (hardware version v1) (EndDevice)
                    2024-05-07 09:26:58.815  - info: zigbee.0 (18539) 0x00124b0008e73540 (addr 25642): AV2010/24 - SMaBiT (Bitron Video) Optical smoke detector (hardware version v1) (EndDevice)
                    2024-05-07 09:26:58.819  - info: zigbee.0 (18539) 0x8418260000074b81 (addr 33976): AC03641 - OSRAM LIGHTIFY LED Classic A60 clear (Router)
                    2024-05-07 09:26:58.821  - info: zigbee.0 (18539) 0x841826000007fd2c (addr 57868): AB32840 - OSRAM LIGHTIFY LED Classic B40 tunable white (Router)
                    2024-05-07 09:26:58.824  - info: zigbee.0 (18539) 0x841826000007feec (addr 53249): AB32840 - OSRAM LIGHTIFY LED Classic B40 tunable white (Router)
                    2024-05-07 09:26:58.827  - info: zigbee.0 (18539) 0x8418260000ca4b3f (addr 43907): AA70155 - OSRAM LIGHTIFY LED A19 tunable white / Classic A60 TW (Router)
                    2024-05-07 09:26:58.830  - info: zigbee.0 (18539) 0x001788010278c53e (addr 65419): 9290012573A - Philips Hue white and color ambiance E26/E27/E14 (Router)
                    2024-05-07 09:26:58.832  - info: zigbee.0 (18539) 0x001788010db82a55 (addr 143): 9290024406A - Philips Hue P45 light bulb (Router)
                    2024-05-07 09:26:58.833  - info: zigbee.0 (18539) Zigbee started
                    2024-05-07 09:26:58.949  - info: zigbee.0 (18539) debug devices set to []
                    2024-05-07 09:27:28.484  - info: bydhvs.0 (3411) Received, Packet: 1 Data: 0103cc50303330543032305a32323036303731343239787878787803120313031a01000013020000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000012345a02031a000c0000ffff0000ffff0000ffff0000ffff0000ffff0000ffff0000ffff0000ffff0000ffff000000001805070728052921
                    2024-05-07 09:27:28.752  - info: bydhvs.0 (3411) Received, Packet: 2 Data: 0103320009014601410062000079b8001300110011000003130000000000000902000279ea3bf500003143000000ff00004000042cef6a
                    2024-05-07 09:27:29.032  - info: bydhvs.0 (3411) Received, Packet: 3 Data: 010306001302000000a50e
                    2024-05-07 09:27:28.484  - info: bydhvs.0 (3411) Received, Packet: 1 Data: 0103cc50303330543032305a32323036303731343239787878787803120313031a01000013020000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000012345a02031a000c0000ffff0000ffff0000ffff0000ffff0000ffff0000ffff0000ffff0000ffff0000ffff000000001805070728052921
                    2024-05-07 09:27:28.752  - info: bydhvs.0 (3411) Received, Packet: 2 Data: 0103320009014601410062000079b8001300110011000003130000000000000902000279ea3bf500003143000000ff00004000042cef6a
                    2024-05-07 09:27:29.032  - info: bydhvs.0 (3411) Received, Packet: 3 Data: 010306001302000000a50e
                    2024-05-07 09:27:30.871  - info: zigbee.0 (18539) List of port: [{"path":"/dev/ttyACM0","manufacturer":"Texas Instruments","serialNumber":"L1100QXL","pnpId":"usb-Texas_Instruments_XDS110__03.00.00.20__Embed_with_CMSIS-DAP_L1100QXL-if00","vendorId":"0451","productId":"bef3"},{"path":"/dev/ttyACM1","manufacturer":"Texas Instruments","serialNumber":"L1100QXL","pnpId":"usb-Texas_Instruments_XDS110__03.00.00.20__Embed_with_CMSIS-DAP_L1100QXL-if03","vendorId":"0451","productId":"bef3"},{"path":"/dev/ttyS0"}]
                    2024-05-07 09:27:30.871  - info: zigbee.0 (18539) List of port: [{"path":"/dev/ttyACM0","manufacturer":"Texas Instruments","serialNumber":"L1100QXL","pnpId":"usb-Texas_Instruments_XDS110__03.00.00.20__Embed_with_CMSIS-DAP_L1100QXL-if00","vendorId":"0451","productId":"bef3"},{"path":"/dev/ttyACM1","manufacturer":"Texas Instruments","serialNumber":"L1100QXL","pnpId":"usb-Texas_Instruments_XDS110__03.00.00.20__Embed_with_CMSIS-DAP_L1100QXL-if03","vendorId":"0451","productId":"bef3"},{"path":"/dev/ttyS0"}]
                    2024-05-07 09:27:57.391  - warn: zigbee.0 (18539) Send command to 0x001788010db82a55 failed with: Code 205 (No network route)
                    2024-05-07 09:27:57.391  - warn: zigbee.0 (18539) Send command to 0x001788010db82a55 failed with: Code 205 (No network route)
                    2
                    
                    Samson71S Offline
                    Samson71S Offline
                    Samson71
                    Global Moderator
                    schrieb am zuletzt editiert von
                    #9

                    @legro sagte in ZigBee Störung:

                    > Wi-Fi is currently blocked by rfkill.
                    
                    > Use raspi-config to set the country before use.
                    

                    Da liegt scheinbar ein Problem.

                    > pi@raspiBullseye:
                    

                    Und zu "Bullseye" hat @Thomas-Braun Dir sicher auch noch was zu sagen ;)

                    Markus

                    Bitte beachten:
                    Hinweise für gute Forenbeiträge
                    Maßnahmen zum Schutz des Forums

                    L 1 Antwort Letzte Antwort
                    0
                    • Samson71S Samson71

                      @legro sagte in ZigBee Störung:

                      > Wi-Fi is currently blocked by rfkill.
                      
                      > Use raspi-config to set the country before use.
                      

                      Da liegt scheinbar ein Problem.

                      > pi@raspiBullseye:
                      

                      Und zu "Bullseye" hat @Thomas-Braun Dir sicher auch noch was zu sagen ;)

                      L Online
                      L Online
                      legro
                      schrieb am zuletzt editiert von legro
                      #10

                      @samson71 sagte in ZigBee Störung:

                      @legro sagte in ZigBee Störung:

                      > Wi-Fi is currently blocked by rfkill.
                      
                      > Use raspi-config to set the country before use.
                      

                      Da liegt scheinbar ein Problem.

                      Gewiss ist dies nicht die Ursache. Ich schalte grundsätzlich WLAN auf dem Raspberry Pi aus, da seit Jahr und Tag dieser per LAN in unser Netzwerk eingebunden ist.

                      Raspberry Pi 5 mit 8GB + 120GB SSD + Coordinator COD-m + ioBroker ..

                      MartinPM 1 Antwort Letzte Antwort
                      0
                      • L legro

                        @samson71 sagte in ZigBee Störung:

                        @legro sagte in ZigBee Störung:

                        > Wi-Fi is currently blocked by rfkill.
                        
                        > Use raspi-config to set the country before use.
                        

                        Da liegt scheinbar ein Problem.

                        Gewiss ist dies nicht die Ursache. Ich schalte grundsätzlich WLAN auf dem Raspberry Pi aus, da seit Jahr und Tag dieser per LAN in unser Netzwerk eingebunden ist.

                        MartinPM Online
                        MartinPM Online
                        MartinP
                        schrieb am zuletzt editiert von
                        #11

                        @legro Vorne steht in untenstehender Log-Meldung "ttyACM0, hinten" ttys0" vielleicht bringt das etwas durcheinander

                        2024-05-07 09:27:30.871  - info: zigbee.0 (18539) List of port: [{"path":"/dev/ttyACM0","manufacturer":"Texas Instruments","serialNumber":"L1100QXL","pnpId":"usb-Texas_Instruments_XDS110__03.00.00.20__Embed_with_CMSIS-DAP_L1100QXL-if00","vendorId":"0451","productId":"bef3"},{"path":"/dev/ttyACM1","manufacturer":"Texas Instruments","serialNumber":"L1100QXL","pnpId":"usb-Texas_Instruments_XDS110__03.00.00.20__Embed_with_CMSIS-DAP_L1100QXL-if03","vendorId":"0451","productId":"bef3"},{"path":"/dev/ttyS0"}]
                        

                        Trage probeweise mal den hoffentlich vorhandenen Eintrag unter "/dev/serial/by-id" als Pfad zum Device in der Konfiguration ein. Der wird extra dafür angelegt, um solches Durcheinander nach Reboots zu vermeiden.

                        Intel(R) Celeron(R) CPU N3000 @ 1.04GHz 8G RAM 480G SSD
                        Virtualization : unprivileged lxc container (debian 12 on Proxmox 8.4.14)
                        Linux pve 6.8.12-16-pve
                        6 GByte RAM für den Container
                        Fritzbox 6591 FW 8.03 (Vodafone Leih-Box)
                        Remote-Access über Wireguard der Fritzbox

                        Thomas BraunT 1 Antwort Letzte Antwort
                        0
                        • MartinPM MartinP

                          @legro Vorne steht in untenstehender Log-Meldung "ttyACM0, hinten" ttys0" vielleicht bringt das etwas durcheinander

                          2024-05-07 09:27:30.871  - info: zigbee.0 (18539) List of port: [{"path":"/dev/ttyACM0","manufacturer":"Texas Instruments","serialNumber":"L1100QXL","pnpId":"usb-Texas_Instruments_XDS110__03.00.00.20__Embed_with_CMSIS-DAP_L1100QXL-if00","vendorId":"0451","productId":"bef3"},{"path":"/dev/ttyACM1","manufacturer":"Texas Instruments","serialNumber":"L1100QXL","pnpId":"usb-Texas_Instruments_XDS110__03.00.00.20__Embed_with_CMSIS-DAP_L1100QXL-if03","vendorId":"0451","productId":"bef3"},{"path":"/dev/ttyS0"}]
                          

                          Trage probeweise mal den hoffentlich vorhandenen Eintrag unter "/dev/serial/by-id" als Pfad zum Device in der Konfiguration ein. Der wird extra dafür angelegt, um solches Durcheinander nach Reboots zu vermeiden.

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

                          @martinp sagte in ZigBee Störung:

                          Trage probeweise mal den hoffentlich vorhandenen Eintrag unter "/dev/serial/by-id" als Pfad zum Device in der Konfiguration ein. Der wird extra dafür angelegt, um solches Durcheinander nach Reboots zu vermeiden.

                          Dazu gibt es 'frischen Code' in

                          iob diag
                          

                          Da wird das Setup mit den by-id-Links verglichen und es gibt einen Hinweis dazu. (Jedenfalls in der Theorie...)

                          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

                          MartinPM HomoranH 2 Antworten Letzte Antwort
                          2
                          • Thomas BraunT Thomas Braun

                            @martinp sagte in ZigBee Störung:

                            Trage probeweise mal den hoffentlich vorhandenen Eintrag unter "/dev/serial/by-id" als Pfad zum Device in der Konfiguration ein. Der wird extra dafür angelegt, um solches Durcheinander nach Reboots zu vermeiden.

                            Dazu gibt es 'frischen Code' in

                            iob diag
                            

                            Da wird das Setup mit den by-id-Links verglichen und es gibt einen Hinweis dazu. (Jedenfalls in der Theorie...)

                            MartinPM Online
                            MartinPM Online
                            MartinP
                            schrieb am zuletzt editiert von
                            #13

                            @thomas-braun said in ZigBee Störung:

                            Dazu gibt es 'frischen Code'

                            gut zu wissen ... continuous improvement at its best ...

                            Intel(R) Celeron(R) CPU N3000 @ 1.04GHz 8G RAM 480G SSD
                            Virtualization : unprivileged lxc container (debian 12 on Proxmox 8.4.14)
                            Linux pve 6.8.12-16-pve
                            6 GByte RAM für den Container
                            Fritzbox 6591 FW 8.03 (Vodafone Leih-Box)
                            Remote-Access über Wireguard der Fritzbox

                            1 Antwort Letzte Antwort
                            0
                            • Thomas BraunT Thomas Braun

                              @martinp sagte in ZigBee Störung:

                              Trage probeweise mal den hoffentlich vorhandenen Eintrag unter "/dev/serial/by-id" als Pfad zum Device in der Konfiguration ein. Der wird extra dafür angelegt, um solches Durcheinander nach Reboots zu vermeiden.

                              Dazu gibt es 'frischen Code' in

                              iob diag
                              

                              Da wird das Setup mit den by-id-Links verglichen und es gibt einen Hinweis dazu. (Jedenfalls in der Theorie...)

                              HomoranH Nicht stören
                              HomoranH Nicht stören
                              Homoran
                              Global Moderator Administrators
                              schrieb am zuletzt editiert von
                              #14

                              @thomas-braun sagte in ZigBee Störung:

                              Da wird das Setup mit den by-id-Links verglichen und es gibt einen Hinweis dazu. (Jedenfalls in der Theorie...)

                              Ja! scheint auch in der Praxis zu funktionieren, ist mir bereits positiv in einigen Diags aufgefallen

                              incl. weiterer Verbesserungen

                              kein Support per PN! - Fragen im Forum stellen - es gibt fast nichts, was nicht auch für andere interessant ist.

                              Benutzt das Voting rechts unten im Beitrag wenn er euch geholfen hat.

                              der Installationsfixer: curl -fsL https://iobroker.net/fix.sh | bash -

                              1 Antwort Letzte Antwort
                              0
                              • L legro

                                @thomas-braun @arteck

                                In dem nachfolgenden Datenwust sind zwei Neustarts enthalten. Wie gesagt, für mich sind dies alles Böhmische Dörfer.

                                Last login: Tue May  7 09:15:52 on ttys000
                                
                                The default interactive shell is now zsh.
                                To update your account to use zsh, please run `chsh -s /bin/zsh`.
                                For more details, please visit https://support.apple.com/kb/HT208050.
                                Leanders-MacBook-Pro-Neu:~ leandergroben$ ssh pi@192.168.4.58
                                pi@192.168.4.58's password: 
                                Linux raspiBullseye 6.1.21-v8+ #1642 SMP PREEMPT Mon Apr  3 17:24:16 BST 2023 aarch64
                                
                                The programs included with the Debian GNU/Linux system are free software;
                                the exact distribution terms for each program are described in the
                                individual files in /usr/share/doc/*/copyright.
                                
                                Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
                                permitted by applicable law.
                                Last login: Tue May  7 09:18:12 2024 from 192.168.4.24
                                
                                Wi-Fi is currently blocked by rfkill.
                                Use raspi-config to set the country before use.
                                
                                pi@raspiBullseye:~ $ iob logs --watch
                                2024-05-07 06:55:28.708  - info: bydhvs.0 (3411) Received, Packet: 2 Data: 01033200080144013f0062000078f0001300110011000003130000000000000902000279223bf400003143000000ff00004000042c379d
                                2024-05-07 06:55:28.966  - info: bydhvs.0 (3411) Received, Packet: 3 Data: 010306001302000000a50e
                                2024-05-07 06:55:30.827  - warn: zigbee.0 (3201) Send command to 0x8418260000ca4b3f failed with: Code 205 (No network route)
                                2024-05-07 06:55:38.408  - info: zigbee.0 (3201) Zigbee: stop joining
                                2024-05-07 06:57:17.490  - warn: zigbee.0 (3201) Send command to 0x8418260000074b81 failed with: Code 205 (No network route)
                                2024-05-07 06:58:28.828  - info: zigbee.0 (3201) Device '0x8418260000074b81' announced itself
                                2024-05-07 06:59:07.186  - info: host.raspiBullseye stopInstance system.adapter.zigbee.0 (force=false, process=true)
                                2024-05-07 06:59:07.218  - info: zigbee.0 (3201) Got terminate signal TERMINATE_YOURSELF
                                2024-05-07 06:59:07.221  - info: zigbee.0 (3201) cleaned everything up...
                                2024-05-07 06:59:07.225  - info: zigbee.0 (3201) Zigbee: disabling joining new devices.
                                2024-05-07 06:59:07.531  - info: host.raspiBullseye stopInstance system.adapter.zigbee.0 send kill signal
                                2024-05-07 06:59:07.727  - info: zigbee.0 (3201) terminating
                                2024-05-07 06:59:07.731  - info: zigbee.0 (3201) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
                                2024-05-07 06:59:08.669  - info: host.raspiBullseye instance system.adapter.zigbee.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
                                2024-05-07 06:59:10.777  - info: host.raspiBullseye instance system.adapter.zigbee.0 started with pid 5074
                                2024-05-07 06:59:17.765  - info: zigbee.0 (5074) starting. Version 1.10.3 in /opt/iobroker/node_modules/iobroker.zigbee, node: v18.20.0, js-controller: 5.0.19
                                2024-05-07 06:59:17.930  - info: zigbee.0 (5074) delete old Backup files. keep only last 10
                                2024-05-07 06:59:17.933  - info: zigbee.0 (5074) Starting Zigbee  npm ...
                                2024-05-07 06:59:18.495  - info: zigbee.0 (5074) Installed Version: iobroker.zigbee@1.10.3
                                2024-05-07 06:59:19.625  - info: zigbee.0 (5074) Coordinator firmware version: {"type":"zStack3x0","meta":{"transportrev":2,"product":1,"majorrel":2,"minorrel":7,"maintrel":1,"revision":20220219}}
                                2024-05-07 06:59:19.633  - info: zigbee.0 (5074) Unable to disable LED, unsupported function.
                                2024-05-07 06:59:19.652  - info: zigbee.0 (5074)   --> transmitPower : high
                                2024-05-07 06:59:19.664  - info: zigbee.0 (5074) Currently 14 devices are joined:
                                2024-05-07 06:59:19.787  - info: zigbee.0 (5074) 0x00124b0008a50109 (addr 52361): AV2010/24 - SMaBiT (Bitron Video) Optical smoke detector (hardware version v1) (EndDevice)
                                2024-05-07 06:59:19.793  - info: zigbee.0 (5074) 0x00124b000621ad0e (addr 36173): AV2010/29 - SMaBiT (Bitron Video) Outdoor siren (EndDevice)
                                2024-05-07 06:59:19.795  - info: zigbee.0 (5074) 0x00124b00074e8fdf (addr 6545): AV2010/24 - SMaBiT (Bitron Video) Optical smoke detector (hardware version v1) (EndDevice)
                                2024-05-07 06:59:19.797  - info: zigbee.0 (5074) 0x00124b00077b7fe8 (addr 3558): AV2010/24 - SMaBiT (Bitron Video) Optical smoke detector (hardware version v1) (EndDevice)
                                2024-05-07 06:59:19.798  - info: zigbee.0 (5074) 0x00124b0008a68663 (addr 32039): AV2010/24 - SMaBiT (Bitron Video) Optical smoke detector (hardware version v1) (EndDevice)
                                2024-05-07 06:59:19.800  - info: zigbee.0 (5074) 0x00124b0008e7395c (addr 46194): AV2010/24 - SMaBiT (Bitron Video) Optical smoke detector (hardware version v1) (EndDevice)
                                2024-05-07 06:59:19.802  - info: zigbee.0 (5074) 0x00124b00090da34c (addr 58423): AV2010/24 - SMaBiT (Bitron Video) Optical smoke detector (hardware version v1) (EndDevice)
                                2024-05-07 06:59:19.804  - info: zigbee.0 (5074) 0x00124b0008e73540 (addr 25642): AV2010/24 - SMaBiT (Bitron Video) Optical smoke detector (hardware version v1) (EndDevice)
                                2024-05-07 06:59:19.806  - info: zigbee.0 (5074) 0x8418260000074b81 (addr 33976): AC03641 - OSRAM LIGHTIFY LED Classic A60 clear (Router)
                                2024-05-07 06:59:19.808  - info: zigbee.0 (5074) 0x841826000007fd2c (addr 57868): AB32840 - OSRAM LIGHTIFY LED Classic B40 tunable white (Router)
                                2024-05-07 06:59:19.809  - info: zigbee.0 (5074) 0x841826000007feec (addr 53249): AB32840 - OSRAM LIGHTIFY LED Classic B40 tunable white (Router)
                                2024-05-07 06:59:19.811  - info: zigbee.0 (5074) 0x8418260000ca4b3f (addr 43907): AA70155 - OSRAM LIGHTIFY LED A19 tunable white / Classic A60 TW (Router)
                                2024-05-07 06:59:19.813  - info: zigbee.0 (5074) 0x001788010278c53e (addr 65419): 9290012573A - Philips Hue white and color ambiance E26/E27/E14 (Router)
                                2024-05-07 06:59:19.815  - info: zigbee.0 (5074) 0x001788010db82a55 (addr 143): 9290024406A - Philips Hue P45 light bulb (Router)
                                2024-05-07 06:59:19.816  - info: zigbee.0 (5074) Zigbee started
                                2024-05-07 06:59:19.911  - info: zigbee.0 (5074) debug devices set to []
                                2024-05-07 06:59:24.421  - info: zigbee.0 (5074) List of port: [{"path":"/dev/ttyACM0","manufacturer":"Texas Instruments","serialNumber":"L1100QXL","pnpId":"usb-Texas_Instruments_XDS110__03.00.00.20__Embed_with_CMSIS-DAP_L1100QXL-if00","vendorId":"0451","productId":"bef3"},{"path":"/dev/ttyACM1","manufacturer":"Texas Instruments","serialNumber":"L1100QXL","pnpId":"usb-Texas_Instruments_XDS110__03.00.00.20__Embed_with_CMSIS-DAP_L1100QXL-if03","vendorId":"0451","productId":"bef3"},{"path":"/dev/ttyS0"}]
                                2024-05-07 06:59:52.425  - error: zigbee.0 (5074) Error 225 on send command to 0x001788010db82a55. Error: Error: ZCL command 0x001788010db82a55/11 genOnOff.on({}, {"timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":false,"direction":0,"srcEndpoint":null,"reservedBits":0,"manufacturerCode":null,"transactionSequenceNumber":null,"writeUndiv":false}) failed (Data request failed with error: 'MAC channel access failure' (225))
                                    at ZStackAdapter.sendZclFrameToEndpointInternal (/opt/iobroker/node_modules/zigbee-herdsman/src/adapter/z-stack/adapter/zStackAdapter.ts:411:23)
                                    at Queue.execute (/opt/iobroker/node_modules/zigbee-herdsman/src/utils/queue.ts:35:20)
                                    at Request.send (/opt/iobroker/node_modules/zigbee-herdsman/src/controller/helpers/request.ts:79:20)
                                    at Endpoint.zclCommand (/opt/iobroker/node_modules/zigbee-herdsman/src/controller/model/endpoint.ts:756:28)
                                    at Endpoint.command (/opt/iobroker/node_modules/zigbee-herdsman/src/controller/model/endpoint.ts:587:24)
                                    at Object.convertSet (/opt/iobroker/node_modules/zigbee-herdsman-converters/src/converters/toZigbee.ts:48:17)
                                    at Object.convertSet (/opt/iobroker/node_modules/zigbee-herdsman-converters/src/converters/toZigbee.ts:1131:32)
                                    at /opt/iobroker/node_modules/iobroker.zigbee/main.js:754:36
                                2024-05-07 06:59:54.242  - info: zigbee.0 (5074) Zigbee: allowing new devices to join.
                                2024-05-07 07:00:00.228  - info: host.raspiBullseye instance system.adapter.dwd.0 started with pid 5168
                                2024-05-07 07:00:00.843  - error: zigbee.0 (5074) Error 225 on send command to 0x001788010db82a55. Error: Error: ZCL command 0x001788010db82a55/11 genOnOff.off({}, {"timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":false,"direction":0,"srcEndpoint":null,"reservedBits":0,"manufacturerCode":null,"transactionSequenceNumber":null,"writeUndiv":false}) failed (Data request failed with error: 'MAC channel access failure' (225))
                                    at ZStackAdapter.sendZclFrameToEndpointInternal (/opt/iobroker/node_modules/zigbee-herdsman/src/adapter/z-stack/adapter/zStackAdapter.ts:411:23)
                                    at Queue.execute (/opt/iobroker/node_modules/zigbee-herdsman/src/utils/queue.ts:35:20)
                                    at Request.send (/opt/iobroker/node_modules/zigbee-herdsman/src/controller/helpers/request.ts:79:20)
                                    at Endpoint.zclCommand (/opt/iobroker/node_modules/zigbee-herdsman/src/controller/model/endpoint.ts:756:28)
                                    at Endpoint.command (/opt/iobroker/node_modules/zigbee-herdsman/src/controller/model/endpoint.ts:587:24)
                                    at Object.convertSet (/opt/iobroker/node_modules/zigbee-herdsman-converters/src/converters/toZigbee.ts:48:17)
                                    at Object.convertSet (/opt/iobroker/node_modules/zigbee-herdsman-converters/src/converters/toZigbee.ts:1131:32)
                                    at /opt/iobroker/node_modules/iobroker.zigbee/main.js:754:36
                                2024-05-07 07:00:03.779  - info: dwd.0 (5168) starting. Version 2.8.5 in /opt/iobroker/node_modules/iobroker.dwd, node: v18.20.0, js-controller: 5.0.19
                                2024-05-07 07:00:05.090  - info: trashschedule.0 (3331) Setting "actionNeeded" flag for type.biomüll.actionNeeded to true (???)
                                2024-05-07 07:00:05.113  - info: trashschedule.0 (3331) Setting "actionNeeded" flag for type.altpapier.actionNeeded to true (???)
                                2024-05-07 07:00:07.050  - info: dwd.0 (5168) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
                                2024-05-07 07:00:07.608  - info: host.raspiBullseye instance system.adapter.dwd.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
                                2024-05-07 07:00:55.510  - info: zigbee.0 (5074) Zigbee: stop joining
                                2024-05-07 07:01:01.276  - warn: zigbee.0 (5074) Send command to 0x001788010db82a55 failed with: Code 205 (No network route)
                                2024-05-07 07:02:01.752  - warn: zigbee.0 (5074) Send command to 0x001788010db82a55 failed with: Code 205 (No network route)
                                2024-05-07 07:02:59.065  - info: shelly.0 (3059) [CoAP] Device 192.168.4.46 (shellyswitch25 / shellyswitch25-10521CF99772 / SHSW-25#10521CF99772#1) connected! Polltime set to 5 sec.
                                2024-05-07 07:03:44.949  - info: zigbee.0 (5074) Device '0x00124b00074e8fdf' announced itself
                                2024-05-07 07:03:52.469  - info: tuya.0 (3179) bf365e8431096d4a1cxcnl: Error on Reconnect (1): connect EHOSTUNREACH 192.168.4.33:6668
                                2024-05-07 07:04:12.810  - info: tuya.0 (3179) bf365e8431096d4a1cxcnl: Error on Reconnect (3): connect EHOSTUNREACH 192.168.4.33:6668
                                2024-05-07 07:04:55.883  - info: tuya.0 (3179) bf365e8431096d4a1cxcnl: Error on Reconnect (5): connect EHOSTUNREACH 192.168.4.33:6668
                                2024-05-07 07:05:00.038  - info: host.raspiBullseye instance system.adapter.daswetter.0 started with pid 5620
                                2024-05-07 07:05:03.206  - info: daswetter.0 (5620) starting. Version 3.1.13 in /opt/iobroker/node_modules/iobroker.daswetter, node: v18.20.0, js-controller: 5.0.19
                                2024-05-07 07:05:33.256  - info: zigbee.0 (5074) List of port: [{"path":"/dev/ttyACM0","manufacturer":"Texas Instruments","serialNumber":"L1100QXL","pnpId":"usb-Texas_Instruments_XDS110__03.00.00.20__Embed_with_CMSIS-DAP_L1100QXL-if00","vendorId":"0451","productId":"bef3"},{"path":"/dev/ttyACM1","manufacturer":"Texas Instruments","serialNumber":"L1100QXL","pnpId":"usb-Texas_Instruments_XDS110__03.00.00.20__Embed_with_CMSIS-DAP_L1100QXL-if03","vendorId":"0451","productId":"bef3"},{"path":"/dev/ttyS0"}]
                                2024-05-07 07:05:38.121  - info: daswetter.0 (5620) still wrong data structure from server received! repaired...
                                2024-05-07 07:05:46.134  - info: daswetter.0 (5620) Terminated (ADAPTER_REQUESTED_TERMINATION): All data handled, adapter stopped until next scheduled moment
                                2024-05-07 07:05:46.701  - info: daswetter.0 (5620) cleaned everything up...
                                2024-05-07 07:05:46.749  - info: host.raspiBullseye instance system.adapter.daswetter.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
                                2024-05-07 07:05:58.954  - info: tuya.0 (3179) bf365e8431096d4a1cxcnl: Error on Reconnect (7): connect EHOSTUNREACH 192.168.4.33:6668
                                2024-05-07 07:06:14.684  - warn: zigbee.0 (5074) Send command to 0x8418260000074b81 failed with: Code 205 (No network route)
                                2024-05-07 07:06:29.157  - info: tuya.0 (3179) bf365e8431096d4a1cxcnl: Connect locally to device
                                2024-05-07 07:06:29.158  - info: tuya.0 (3179) bf365e8431096d4a1cxcnl Init with IP=192.168.4.33, Key=54bab00521b02b77, Version=3.3
                                2024-05-07 07:06:32.234  - info: tuya.0 (3179) bf365e8431096d4a1cxcnl: Error on Reconnect (1): connect EHOSTUNREACH 192.168.4.33:6668
                                2024-05-07 07:06:36.920  - warn: zigbee.0 (5074) Send command to 0x8418260000074b81 failed with: Code 205 (No network route)
                                2024-05-07 07:06:55.306  - info: tuya.0 (3179) bf365e8431096d4a1cxcnl: Error on Reconnect (3): connect EHOSTUNREACH 192.168.4.33:6668
                                2024-05-07 07:06:59.013  - warn: zigbee.0 (5074) Send command to 0x8418260000074b81 failed with: Code 205 (No network route)
                                2024-05-07 07:07:38.378  - info: tuya.0 (3179) bf365e8431096d4a1cxcnl: Error on Reconnect (5): connect EHOSTUNREACH 192.168.4.33:6668
                                2024-05-07 07:15:00.072  - info: host.raspiBullseye instance system.adapter.dwd.0 started with pid 6512
                                2024-05-07 07:15:03.479  - info: dwd.0 (6512) starting. Version 2.8.5 in /opt/iobroker/node_modules/iobroker.dwd, node: v18.20.0, js-controller: 5.0.19
                                2024-05-07 07:15:05.216  - info: dwd.0 (6512) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
                                2024-05-07 07:15:05.754  - info: host.raspiBullseye instance system.adapter.dwd.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
                                2024-05-07 07:21:19.860  - info: web.0 (3218) <== Disconnect system.user.admin from ::ffff:192.168.4.87 vis.0
                                2024-05-07 07:22:14.342  - info: web.0 (3218) ==> Connected system.user.admin from ::ffff:192.168.4.87
                                2024-05-07 07:22:15.193  - info: web.0 (3218) <== Disconnect system.user.admin from ::ffff:192.168.4.87 vis.0
                                2024-05-07 07:22:15.274  - info: web.0 (3218) ==> Connected system.user.admin from ::ffff:192.168.4.87
                                2024-05-07 07:22:27.953  - info: web.0 (3218) <== Disconnect system.user.admin from ::ffff:192.168.4.87 vis.0
                                2024-05-07 07:24:03.222  - info: javascript.0 (2232) Stop script script.js.Rollladen.RollladenBlockly_NEU_4
                                2024-05-07 07:24:03.278  - info: javascript.0 (2232) Start javascript script.js.Rollladen.RollladenBlockly_NEU_4
                                2024-05-07 07:24:03.305  - info: javascript.0 (2232) script.js.Rollladen.RollladenBlockly_NEU_4: registered 0 subscriptions, 0 schedules, 0 messages, 0 logs and 0 file subscriptions
                                2024-05-07 07:24:03.310  - info: javascript.0 (2232) script.js.Rollladen.RollladenBlockly_NEU_4: [
                                  {
                                    Name: 'ROL_EG_WC',
                                    objAddr: 'shelly.0.SHSW-25#10521CF99772#1.Position'
                                  },
                                  {
                                    Name: 'ROL_EG_KUE',
                                    objAddr: 'shelly.0.SHSW-25#483FDA7601B9#1.Position'
                                  },
                                  { Name: 'ROL_EG_TER_L', objAddr: 'hm-rpc.0.MEQ1732299.1.LEVEL' },
                                  { Name: 'ROL_EG_TER_R', objAddr: 'hm-rpc.0.MEQ1730298.1.LEVEL' },
                                  { Name: 'ROL_EG_WZ_O', objAddr: 'hm-rpc.0.NEQ0082126.1.LEVEL' },
                                  { Name: 'ROL_EG_BUE_W', objAddr: 'hm-rpc.0.NEQ0078657.1.LEVEL' },
                                  { Name: 'ROL_EG_BUE_N', objAddr: 'hm-rpc.0.NEQ0082108.1.LEVEL' }
                                ]
                                
                                .. jede Menge gelöscht ..
                                
                                2024-05-07 09:25:29.001  - info: bydhvs.0 (3411) Received, Packet: 3 Data: 010306001302000000a50e
                                2024-05-07 09:25:52.823  - info: zigbee.0 (5074) List of port: [{"path":"/dev/ttyACM0","manufacturer":"Texas Instruments","serialNumber":"L1100QXL","pnpId":"usb-Texas_Instruments_XDS110__03.00.00.20__Embed_with_CMSIS-DAP_L1100QXL-if00","vendorId":"0451","productId":"bef3"},{"path":"/dev/ttyACM1","manufacturer":"Texas Instruments","serialNumber":"L1100QXL","pnpId":"usb-Texas_Instruments_XDS110__03.00.00.20__Embed_with_CMSIS-DAP_L1100QXL-if03","vendorId":"0451","productId":"bef3"},{"path":"/dev/ttyS0"}]
                                2024-05-07 09:25:52.823  - info: zigbee.0 (5074) List of port: [{"path":"/dev/ttyACM0","manufacturer":"Texas Instruments","serialNumber":"L1100QXL","pnpId":"usb-Texas_Instruments_XDS110__03.00.00.20__Embed_with_CMSIS-DAP_L1100QXL-if00","vendorId":"0451","productId":"bef3"},{"path":"/dev/ttyACM1","manufacturer":"Texas Instruments","serialNumber":"L1100QXL","pnpId":"usb-Texas_Instruments_XDS110__03.00.00.20__Embed_with_CMSIS-DAP_L1100QXL-if03","vendorId":"0451","productId":"bef3"},{"path":"/dev/ttyS0"}]
                                2024-05-07 09:26:26.819  - warn: zigbee.0 (5074) Send command to 0x001788010db82a55 failed with: Code 205 (No network route)
                                2024-05-07 09:26:26.819  - warn: zigbee.0 (5074) Send command to 0x001788010db82a55 failed with: Code 205 (No network route)
                                2024-05-07 09:26:28.489  - info: bydhvs.0 (3411) Received, Packet: 1 Data: 0103cc50303330543032305a32323036303731343239787878787803120313031a01000013020000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000012345a02031a000c0000ffff0000ffff0000ffff0000ffff0000ffff0000ffff0000ffff0000ffff0000ffff000000001805070727052cd1
                                2024-05-07 09:26:28.758  - info: bydhvs.0 (3411) Received, Packet: 2 Data: 0103320009014601410062000079b8001300110011000003130000000000000902000279ea3bf500003143000000ff00004000042cef6a
                                2024-05-07 09:26:29.016  - info: bydhvs.0 (3411) Received, Packet: 3 Data: 010306001302000000a50e
                                2024-05-07 09:26:28.489  - info: bydhvs.0 (3411) Received, Packet: 1 Data: 0103cc50303330543032305a32323036303731343239787878787803120313031a01000013020000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000012345a02031a000c0000ffff0000ffff0000ffff0000ffff0000ffff0000ffff0000ffff0000ffff0000ffff000000001805070727052cd1
                                2024-05-07 09:26:28.758  - info: bydhvs.0 (3411) Received, Packet: 2 Data: 0103320009014601410062000079b8001300110011000003130000000000000902000279ea3bf500003143000000ff00004000042cef6a
                                2024-05-07 09:26:29.016  - info: bydhvs.0 (3411) Received, Packet: 3 Data: 010306001302000000a50e
                                2024-05-07 09:26:47.118  - info: host.raspiBullseye stopInstance system.adapter.zigbee.0 (force=false, process=true)
                                2024-05-07 09:26:47.144  - info: zigbee.0 (5074) Got terminate signal TERMINATE_YOURSELF
                                2024-05-07 09:26:47.198  - info: host.raspiBullseye stopInstance system.adapter.zigbee.0 send kill signal
                                2024-05-07 09:26:47.147  - info: zigbee.0 (5074) cleaned everything up...
                                2024-05-07 09:26:47.149  - info: zigbee.0 (5074) Zigbee: disabling joining new devices.
                                2024-05-07 09:26:47.651  - info: zigbee.0 (5074) terminating
                                2024-05-07 09:26:47.653  - info: zigbee.0 (5074) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
                                2024-05-07 09:26:47.118  - info: host.raspiBullseye stopInstance system.adapter.zigbee.0 (force=false, process=true)
                                2024-05-07 09:26:47.144  - info: zigbee.0 (5074) Got terminate signal TERMINATE_YOURSELF
                                2024-05-07 09:26:47.198  - info: host.raspiBullseye stopInstance system.adapter.zigbee.0 send kill signal
                                2024-05-07 09:26:47.147  - info: zigbee.0 (5074) cleaned everything up...
                                2024-05-07 09:26:47.149  - info: zigbee.0 (5074) Zigbee: disabling joining new devices.
                                2024-05-07 09:26:47.651  - info: zigbee.0 (5074) terminating
                                2024-05-07 09:26:47.653  - info: zigbee.0 (5074) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
                                2024-05-07 09:26:48.245  - info: host.raspiBullseye stopInstance system.adapter.zigbee.0 killing pid 5074
                                2024-05-07 09:26:48.510  - info: host.raspiBullseye instance system.adapter.zigbee.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
                                2024-05-07 09:26:48.245  - info: host.raspiBullseye stopInstance system.adapter.zigbee.0 killing pid 5074
                                2024-05-07 09:26:48.510  - info: host.raspiBullseye instance system.adapter.zigbee.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
                                2024-05-07 09:26:50.437  - info: host.raspiBullseye instance system.adapter.zigbee.0 started with pid 18539
                                2024-05-07 09:26:50.437  - info: host.raspiBullseye instance system.adapter.zigbee.0 started with pid 18539
                                2024-05-07 09:26:56.663  - info: zigbee.0 (18539) starting. Version 1.10.3 in /opt/iobroker/node_modules/iobroker.zigbee, node: v18.20.0, js-controller: 5.0.19
                                2024-05-07 09:26:56.814  - info: zigbee.0 (18539) delete old Backup files. keep only last 10
                                2024-05-07 09:26:56.817  - info: zigbee.0 (18539) Starting Zigbee  npm ...
                                2024-05-07 09:26:57.361  - info: zigbee.0 (18539) Installed Version: iobroker.zigbee@1.10.3
                                2024-05-07 09:26:56.663  - info: zigbee.0 (18539) starting. Version 1.10.3 in /opt/iobroker/node_modules/iobroker.zigbee, node: v18.20.0, js-controller: 5.0.19
                                2024-05-07 09:26:56.814  - info: zigbee.0 (18539) delete old Backup files. keep only last 10
                                2024-05-07 09:26:56.817  - info: zigbee.0 (18539) Starting Zigbee  npm ...
                                2024-05-07 09:26:57.361  - info: zigbee.0 (18539) Installed Version: iobroker.zigbee@1.10.3
                                2024-05-07 09:26:58.578  - info: zigbee.0 (18539) Coordinator firmware version: {"type":"zStack3x0","meta":{"transportrev":2,"product":1,"majorrel":2,"minorrel":7,"maintrel":1,"revision":20220219}}
                                2024-05-07 09:26:58.587  - info: zigbee.0 (18539) Unable to disable LED, unsupported function.
                                2024-05-07 09:26:58.621  - info: zigbee.0 (18539)   --> transmitPower : high
                                2024-05-07 09:26:58.639  - info: zigbee.0 (18539) Currently 14 devices are joined:
                                2024-05-07 09:26:58.795  - info: zigbee.0 (18539) 0x00124b0008a50109 (addr 52361): AV2010/24 - SMaBiT (Bitron Video) Optical smoke detector (hardware version v1) (EndDevice)
                                2024-05-07 09:26:58.800  - info: zigbee.0 (18539) 0x00124b000621ad0e (addr 36173): AV2010/29 - SMaBiT (Bitron Video) Outdoor siren (EndDevice)
                                2024-05-07 09:26:58.802  - info: zigbee.0 (18539) 0x00124b00074e8fdf (addr 6545): AV2010/24 - SMaBiT (Bitron Video) Optical smoke detector (hardware version v1) (EndDevice)
                                2024-05-07 09:26:58.805  - info: zigbee.0 (18539) 0x00124b00077b7fe8 (addr 3558): AV2010/24 - SMaBiT (Bitron Video) Optical smoke detector (hardware version v1) (EndDevice)
                                2024-05-07 09:26:58.807  - info: zigbee.0 (18539) 0x00124b0008a68663 (addr 32039): AV2010/24 - SMaBiT (Bitron Video) Optical smoke detector (hardware version v1) (EndDevice)
                                2024-05-07 09:26:58.810  - info: zigbee.0 (18539) 0x00124b0008e7395c (addr 46194): AV2010/24 - SMaBiT (Bitron Video) Optical smoke detector (hardware version v1) (EndDevice)
                                2024-05-07 09:26:58.813  - info: zigbee.0 (18539) 0x00124b00090da34c (addr 58423): AV2010/24 - SMaBiT (Bitron Video) Optical smoke detector (hardware version v1) (EndDevice)
                                2024-05-07 09:26:58.815  - info: zigbee.0 (18539) 0x00124b0008e73540 (addr 25642): AV2010/24 - SMaBiT (Bitron Video) Optical smoke detector (hardware version v1) (EndDevice)
                                2024-05-07 09:26:58.819  - info: zigbee.0 (18539) 0x8418260000074b81 (addr 33976): AC03641 - OSRAM LIGHTIFY LED Classic A60 clear (Router)
                                2024-05-07 09:26:58.821  - info: zigbee.0 (18539) 0x841826000007fd2c (addr 57868): AB32840 - OSRAM LIGHTIFY LED Classic B40 tunable white (Router)
                                2024-05-07 09:26:58.824  - info: zigbee.0 (18539) 0x841826000007feec (addr 53249): AB32840 - OSRAM LIGHTIFY LED Classic B40 tunable white (Router)
                                2024-05-07 09:26:58.827  - info: zigbee.0 (18539) 0x8418260000ca4b3f (addr 43907): AA70155 - OSRAM LIGHTIFY LED A19 tunable white / Classic A60 TW (Router)
                                2024-05-07 09:26:58.830  - info: zigbee.0 (18539) 0x001788010278c53e (addr 65419): 9290012573A - Philips Hue white and color ambiance E26/E27/E14 (Router)
                                2024-05-07 09:26:58.832  - info: zigbee.0 (18539) 0x001788010db82a55 (addr 143): 9290024406A - Philips Hue P45 light bulb (Router)
                                2024-05-07 09:26:58.833  - info: zigbee.0 (18539) Zigbee started
                                2024-05-07 09:26:58.949  - info: zigbee.0 (18539) debug devices set to []
                                2024-05-07 09:26:58.578  - info: zigbee.0 (18539) Coordinator firmware version: {"type":"zStack3x0","meta":{"transportrev":2,"product":1,"majorrel":2,"minorrel":7,"maintrel":1,"revision":20220219}}
                                2024-05-07 09:26:58.587  - info: zigbee.0 (18539) Unable to disable LED, unsupported function.
                                2024-05-07 09:26:58.621  - info: zigbee.0 (18539)   --> transmitPower : high
                                2024-05-07 09:26:58.639  - info: zigbee.0 (18539) Currently 14 devices are joined:
                                2024-05-07 09:26:58.795  - info: zigbee.0 (18539) 0x00124b0008a50109 (addr 52361): AV2010/24 - SMaBiT (Bitron Video) Optical smoke detector (hardware version v1) (EndDevice)
                                2024-05-07 09:26:58.800  - info: zigbee.0 (18539) 0x00124b000621ad0e (addr 36173): AV2010/29 - SMaBiT (Bitron Video) Outdoor siren (EndDevice)
                                2024-05-07 09:26:58.802  - info: zigbee.0 (18539) 0x00124b00074e8fdf (addr 6545): AV2010/24 - SMaBiT (Bitron Video) Optical smoke detector (hardware version v1) (EndDevice)
                                2024-05-07 09:26:58.805  - info: zigbee.0 (18539) 0x00124b00077b7fe8 (addr 3558): AV2010/24 - SMaBiT (Bitron Video) Optical smoke detector (hardware version v1) (EndDevice)
                                2024-05-07 09:26:58.807  - info: zigbee.0 (18539) 0x00124b0008a68663 (addr 32039): AV2010/24 - SMaBiT (Bitron Video) Optical smoke detector (hardware version v1) (EndDevice)
                                2024-05-07 09:26:58.810  - info: zigbee.0 (18539) 0x00124b0008e7395c (addr 46194): AV2010/24 - SMaBiT (Bitron Video) Optical smoke detector (hardware version v1) (EndDevice)
                                2024-05-07 09:26:58.813  - info: zigbee.0 (18539) 0x00124b00090da34c (addr 58423): AV2010/24 - SMaBiT (Bitron Video) Optical smoke detector (hardware version v1) (EndDevice)
                                2024-05-07 09:26:58.815  - info: zigbee.0 (18539) 0x00124b0008e73540 (addr 25642): AV2010/24 - SMaBiT (Bitron Video) Optical smoke detector (hardware version v1) (EndDevice)
                                2024-05-07 09:26:58.819  - info: zigbee.0 (18539) 0x8418260000074b81 (addr 33976): AC03641 - OSRAM LIGHTIFY LED Classic A60 clear (Router)
                                2024-05-07 09:26:58.821  - info: zigbee.0 (18539) 0x841826000007fd2c (addr 57868): AB32840 - OSRAM LIGHTIFY LED Classic B40 tunable white (Router)
                                2024-05-07 09:26:58.824  - info: zigbee.0 (18539) 0x841826000007feec (addr 53249): AB32840 - OSRAM LIGHTIFY LED Classic B40 tunable white (Router)
                                2024-05-07 09:26:58.827  - info: zigbee.0 (18539) 0x8418260000ca4b3f (addr 43907): AA70155 - OSRAM LIGHTIFY LED A19 tunable white / Classic A60 TW (Router)
                                2024-05-07 09:26:58.830  - info: zigbee.0 (18539) 0x001788010278c53e (addr 65419): 9290012573A - Philips Hue white and color ambiance E26/E27/E14 (Router)
                                2024-05-07 09:26:58.832  - info: zigbee.0 (18539) 0x001788010db82a55 (addr 143): 9290024406A - Philips Hue P45 light bulb (Router)
                                2024-05-07 09:26:58.833  - info: zigbee.0 (18539) Zigbee started
                                2024-05-07 09:26:58.949  - info: zigbee.0 (18539) debug devices set to []
                                2024-05-07 09:27:28.484  - info: bydhvs.0 (3411) Received, Packet: 1 Data: 0103cc50303330543032305a32323036303731343239787878787803120313031a01000013020000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000012345a02031a000c0000ffff0000ffff0000ffff0000ffff0000ffff0000ffff0000ffff0000ffff0000ffff000000001805070728052921
                                2024-05-07 09:27:28.752  - info: bydhvs.0 (3411) Received, Packet: 2 Data: 0103320009014601410062000079b8001300110011000003130000000000000902000279ea3bf500003143000000ff00004000042cef6a
                                2024-05-07 09:27:29.032  - info: bydhvs.0 (3411) Received, Packet: 3 Data: 010306001302000000a50e
                                2024-05-07 09:27:28.484  - info: bydhvs.0 (3411) Received, Packet: 1 Data: 0103cc50303330543032305a32323036303731343239787878787803120313031a01000013020000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000012345a02031a000c0000ffff0000ffff0000ffff0000ffff0000ffff0000ffff0000ffff0000ffff0000ffff000000001805070728052921
                                2024-05-07 09:27:28.752  - info: bydhvs.0 (3411) Received, Packet: 2 Data: 0103320009014601410062000079b8001300110011000003130000000000000902000279ea3bf500003143000000ff00004000042cef6a
                                2024-05-07 09:27:29.032  - info: bydhvs.0 (3411) Received, Packet: 3 Data: 010306001302000000a50e
                                2024-05-07 09:27:30.871  - info: zigbee.0 (18539) List of port: [{"path":"/dev/ttyACM0","manufacturer":"Texas Instruments","serialNumber":"L1100QXL","pnpId":"usb-Texas_Instruments_XDS110__03.00.00.20__Embed_with_CMSIS-DAP_L1100QXL-if00","vendorId":"0451","productId":"bef3"},{"path":"/dev/ttyACM1","manufacturer":"Texas Instruments","serialNumber":"L1100QXL","pnpId":"usb-Texas_Instruments_XDS110__03.00.00.20__Embed_with_CMSIS-DAP_L1100QXL-if03","vendorId":"0451","productId":"bef3"},{"path":"/dev/ttyS0"}]
                                2024-05-07 09:27:30.871  - info: zigbee.0 (18539) List of port: [{"path":"/dev/ttyACM0","manufacturer":"Texas Instruments","serialNumber":"L1100QXL","pnpId":"usb-Texas_Instruments_XDS110__03.00.00.20__Embed_with_CMSIS-DAP_L1100QXL-if00","vendorId":"0451","productId":"bef3"},{"path":"/dev/ttyACM1","manufacturer":"Texas Instruments","serialNumber":"L1100QXL","pnpId":"usb-Texas_Instruments_XDS110__03.00.00.20__Embed_with_CMSIS-DAP_L1100QXL-if03","vendorId":"0451","productId":"bef3"},{"path":"/dev/ttyS0"}]
                                2024-05-07 09:27:57.391  - warn: zigbee.0 (18539) Send command to 0x001788010db82a55 failed with: Code 205 (No network route)
                                2024-05-07 09:27:57.391  - warn: zigbee.0 (18539) Send command to 0x001788010db82a55 failed with: Code 205 (No network route)
                                2
                                
                                MartinPM Online
                                MartinPM Online
                                MartinP
                                schrieb am zuletzt editiert von MartinP
                                #15

                                Korrektur - es gibt anscheinend drei serielle Ports, für ttyACM0 und ttyACM1 sehr ähnliche Einträge, bis auf pnpId!

                                Ich drösel das Logging mal manuell auf:

                                2024-05-07 09:27:30.871  - info: zigbee.0 (18539) List of port: [
                                {"path":"/dev/ttyACM0",
                                  "manufacturer":"Texas Instruments",
                                  "serialNumber":"L1100QXL",
                                  "pnpId":"usb-Texas_Instruments_XDS110__03.00.00.20__Embed_with_CMSIS-DAP_L1100QXL-if00",
                                  "vendorId":"0451",
                                  "productId":"bef3"
                                },
                                {"path":"/dev/ttyACM1",
                                  "manufacturer":"Texas Instruments",
                                  "serialNumber":"L1100QXL",
                                  "pnpId":"usb-Texas_Instruments_XDS110__03.00.00.20__Embed_with_CMSIS-DAP_L1100QXL-if03",
                                  "vendorId":"0451",
                                  "productId":  "bef3"
                                },
                                {"path":"/dev/ttyS0"}
                                ]
                                

                                Intel(R) Celeron(R) CPU N3000 @ 1.04GHz 8G RAM 480G SSD
                                Virtualization : unprivileged lxc container (debian 12 on Proxmox 8.4.14)
                                Linux pve 6.8.12-16-pve
                                6 GByte RAM für den Container
                                Fritzbox 6591 FW 8.03 (Vodafone Leih-Box)
                                Remote-Access über Wireguard der Fritzbox

                                Thomas BraunT 1 Antwort Letzte Antwort
                                0
                                • MartinPM MartinP

                                  Korrektur - es gibt anscheinend drei serielle Ports, für ttyACM0 und ttyACM1 sehr ähnliche Einträge, bis auf pnpId!

                                  Ich drösel das Logging mal manuell auf:

                                  2024-05-07 09:27:30.871  - info: zigbee.0 (18539) List of port: [
                                  {"path":"/dev/ttyACM0",
                                    "manufacturer":"Texas Instruments",
                                    "serialNumber":"L1100QXL",
                                    "pnpId":"usb-Texas_Instruments_XDS110__03.00.00.20__Embed_with_CMSIS-DAP_L1100QXL-if00",
                                    "vendorId":"0451",
                                    "productId":"bef3"
                                  },
                                  {"path":"/dev/ttyACM1",
                                    "manufacturer":"Texas Instruments",
                                    "serialNumber":"L1100QXL",
                                    "pnpId":"usb-Texas_Instruments_XDS110__03.00.00.20__Embed_with_CMSIS-DAP_L1100QXL-if03",
                                    "vendorId":"0451",
                                    "productId":  "bef3"
                                  },
                                  {"path":"/dev/ttyS0"}
                                  ]
                                  
                                  Thomas BraunT Online
                                  Thomas BraunT Online
                                  Thomas Braun
                                  Most Active
                                  schrieb am zuletzt editiert von
                                  #16

                                  @martinp

                                  Das zigbee-Ding hat 2 Interfaces.

                                  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

                                  MartinPM 1 Antwort Letzte Antwort
                                  1
                                  • Thomas BraunT Thomas Braun

                                    @martinp

                                    Das zigbee-Ding hat 2 Interfaces.

                                    MartinPM Online
                                    MartinPM Online
                                    MartinP
                                    schrieb am zuletzt editiert von
                                    #17

                                    @thomas-braun said in ZigBee Störung:

                                    @martinp

                                    Das zigbee-Ding hat 2 Interfaces.

                                    Was für einen Sinn hat das? Zwei Zigbee-Kanäle? Oder dienen die beiden seriellen Ports unterschiedlichen Zwecken (einer Debug, einer Zigbee z. B.)

                                    Habe schon ein wenig im Internet gewühlt, aber nicht gefunden ...

                                    Intel(R) Celeron(R) CPU N3000 @ 1.04GHz 8G RAM 480G SSD
                                    Virtualization : unprivileged lxc container (debian 12 on Proxmox 8.4.14)
                                    Linux pve 6.8.12-16-pve
                                    6 GByte RAM für den Container
                                    Fritzbox 6591 FW 8.03 (Vodafone Leih-Box)
                                    Remote-Access über Wireguard der Fritzbox

                                    Thomas BraunT arteckA 2 Antworten Letzte Antwort
                                    0
                                    • MartinPM MartinP

                                      @thomas-braun said in ZigBee Störung:

                                      @martinp

                                      Das zigbee-Ding hat 2 Interfaces.

                                      Was für einen Sinn hat das? Zwei Zigbee-Kanäle? Oder dienen die beiden seriellen Ports unterschiedlichen Zwecken (einer Debug, einer Zigbee z. B.)

                                      Habe schon ein wenig im Internet gewühlt, aber nicht gefunden ...

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

                                      @martinp sagte in ZigBee Störung:

                                      Oder dienen die beiden seriellen Ports unterschiedlichen Zwecken (einer Debug, einer Zigbee z. B.)

                                      Soweit ich weiß genau dafür.

                                      USB connected development kit, based on CC2652R7 chip
                                      These devices have two serial devices built in. Make sure you put the right serial device in the configuration or use auto detect (completely remove the serial section from configuration.yaml) if you only have one Texas Instruments CC device connected to your system.

                                      Quelle:
                                      https://www.zigbee2mqtt.io/guide/adapters/#recommended
                                      Development Boards

                                      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

                                      1 Antwort Letzte Antwort
                                      1
                                      • MartinPM MartinP

                                        @thomas-braun said in ZigBee Störung:

                                        @martinp

                                        Das zigbee-Ding hat 2 Interfaces.

                                        Was für einen Sinn hat das? Zwei Zigbee-Kanäle? Oder dienen die beiden seriellen Ports unterschiedlichen Zwecken (einer Debug, einer Zigbee z. B.)

                                        Habe schon ein wenig im Internet gewühlt, aber nicht gefunden ...

                                        arteckA Offline
                                        arteckA Offline
                                        arteck
                                        Developer Most Active
                                        schrieb am zuletzt editiert von arteck
                                        #19

                                        @martinp es ist ein Entwickler Chip... und die können ein bissel mehr

                                        das interface if00 ist das richtige

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

                                        L 1 Antwort Letzte Antwort
                                        1
                                        • arteckA arteck

                                          @martinp es ist ein Entwickler Chip... und die können ein bissel mehr

                                          das interface if00 ist das richtige

                                          L Online
                                          L Online
                                          legro
                                          schrieb am zuletzt editiert von legro
                                          #20

                                          @arteck

                                          Das Interface sollte (unverändert) richtig sein. Schließlich meldet der ZigBee-Adapter eine Verbindung zu dem Coordinator.

                                          Ist an den Log-Daten irgendetwas zu erkennen?

                                          Raspberry Pi 5 mit 8GB + 120GB SSD + Coordinator COD-m + ioBroker ..

                                          HomoranH 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

                                          652

                                          Online

                                          32.5k

                                          Benutzer

                                          81.8k

                                          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