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. Tester
  4. ZigBee neue Version 1.6.x

NEWS

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

  • Monatsrückblick – September 2025
    BluefoxB
    Bluefox
    13
    1
    2.1k

  • Neues Video "KI im Smart Home" - ioBroker plus n8n
    BluefoxB
    Bluefox
    16
    1
    2.8k

ZigBee neue Version 1.6.x

Geplant Angeheftet Gesperrt Verschoben Tester
509 Beiträge 61 Kommentatoren 114.0k Aufrufe 62 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.
  • arteckA arteck

    @pk68 sagte in ZigBee neue Version 1.6.x:

    Bei dem ist es so, das bei Spannungen bis 3V 100% angezeigt wird. Bei einer Batteriespannung von 2,85 bis 3,0V wird dann gerechnet.

    und das weisst du weil ?? hast du die Hersteller vorgabe Werte von dem Gerät ?

    Ikea Trädfri Fernbedienungen

    welche genau meinst du.. es gibt mehrere davon

    P Offline
    P Offline
    pk68
    schrieb am zuletzt editiert von
    #477

    @arteck sagte in ZigBee neue Version 1.6.x:

    Ikea Trädfri Fernbedienungen

    welche genau meinst du.. es gibt mehrere davon

    Ich meine diese hier.

    1 Antwort Letzte Antwort
    0
    • P pk68

      @arteck sagte in ZigBee neue Version 1.6.x:

      und das weisst du weil ?? hast du die Hersteller vorgabe Werte von dem Gerät ?

      Weil ich Deinem Link gefolgt bin, von Git den Quellcode heruntergeladen habe und mit meinem Halbwissen in dem Code rumgeschnarcht habe.
      Der Türsensor hat die Typbezeichnung MCCGQ11LM. In der devices\xiaomi.js steht zu dem Gerät

      meta: {battery: {voltageToPercentage: '3V_2850_3000_log'}},
      

      Das heißt die Funktion "batteryVoltageToPercentage" wird mit der Option "3V_2850_3000_log" aufgerufen.

          } else if (option === '3V_2850_3000_log') {
              percentage = toPercentage(voltage, 2850, 3000, true);
      

      Und die Funktion "toPercentage" sieht so aus:

      function toPercentage(value, min, max, log=false) {
          if (value > max) {
              value = max;
          } else if (value < min) {
              value = min;
          }
      
          const normalised = (value - min) / (max - min);
          let percentage;
          if (log == true) {
              percentage = normalised === 0 ? 0 : normalised * (1 - Math.log( normalised ));
          } else {
              percentage = normalised;
          }
          return Math.round(percentage * 100);
      }
      
      arteckA Offline
      arteckA Offline
      arteck
      Developer Most Active
      schrieb am zuletzt editiert von arteck
      #478

      @pk68 kannst ja alles schöb durchrechnen lassen

      direkt in der ersten zeile ist die funktion mit den werten die aufgerufen werden ...

      also 2975 dein wert mit den daten die du gefunden hast also 3V_2850_3000_log
      als ergebniss siehst du im LOG 99 %

      20:47:09.324	info	javascript.1 (1576) script.js.common.Skript1: ---------------------> batterie test 99%
      

      den script kannst du unter javascript einfügen und selber testen..

      const per = batteryVoltageToPercentage(2975,'3V_2850_3000_log');    // hier wird die funktion aufgerufen 
      
      console.log('--------------------->   batterie test ' + per);
      
      
      function batteryVoltageToPercentage(voltage, option) {
          let percentage = null;
          if (option === '3V_2100') {
              if (voltage < 2100) {
                  percentage = 0;
              } else if (voltage < 2440) {
                  percentage = 6 - ((2440 - voltage) * 6) / 340;
              } else if (voltage < 2740) {
                  percentage = 18 - ((2740 - voltage) * 12) / 300;
              } else if (voltage < 2900) {
                  percentage = 42 - ((2900 - voltage) * 24) / 160;
              } else if (voltage < 3000) {
                  percentage = 100 - ((3000 - voltage) * 58) / 100;
              } else if (voltage >= 3000) {
                  percentage = 100;
              }
              percentage = Math.round(percentage);
          } else if (option === '3V_2500') {
              percentage = toPercentage(voltage, 2500, 3000);
          } else if (option === '3V_2500_3200') {
              percentage = toPercentage(voltage, 2500, 3200);
          } else if (option === '3V_1500_2800') {
              percentage = 235 - 370000 / (voltage + 1);
              if (percentage > 100) {
                  percentage = 100;
              } else if (percentage < 0) {
                  percentage = 0;
              }
              percentage = Math.round(percentage);
          } else if (option === '3V_2850_3200') {
              percentage = toPercentage(voltage, 2850, 3200);
          } else if (option === '3V_2850_3000_log') {
              percentage = toPercentage(voltage, 2850, 3000, true);
          } else if (option === '4LR6AA1_5v') {
              percentage = toPercentage(voltage, 3000, 4200);
          } 
      
          return percentage;
      }
      function  toPercentage(value, min, max, log=false) {
          if (value > max) {
              value = max;
          } else if (value < min) {
              value = min;
          }
      
          const normalised = (value - min) / (max - min);
          let percentage;
          if (log == true) {
              percentage = normalised === 0 ? 0 : normalised * (1 - Math.log( normalised ));
          } else {
              percentage = normalised;
          }
          return Math.round(percentage * 100);
      }
      

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

      P 1 Antwort Letzte Antwort
      0
      • arteckA arteck

        @pk68 kannst ja alles schöb durchrechnen lassen

        direkt in der ersten zeile ist die funktion mit den werten die aufgerufen werden ...

        also 2975 dein wert mit den daten die du gefunden hast also 3V_2850_3000_log
        als ergebniss siehst du im LOG 99 %

        20:47:09.324	info	javascript.1 (1576) script.js.common.Skript1: ---------------------> batterie test 99%
        

        den script kannst du unter javascript einfügen und selber testen..

        const per = batteryVoltageToPercentage(2975,'3V_2850_3000_log');    // hier wird die funktion aufgerufen 
        
        console.log('--------------------->   batterie test ' + per);
        
        
        function batteryVoltageToPercentage(voltage, option) {
            let percentage = null;
            if (option === '3V_2100') {
                if (voltage < 2100) {
                    percentage = 0;
                } else if (voltage < 2440) {
                    percentage = 6 - ((2440 - voltage) * 6) / 340;
                } else if (voltage < 2740) {
                    percentage = 18 - ((2740 - voltage) * 12) / 300;
                } else if (voltage < 2900) {
                    percentage = 42 - ((2900 - voltage) * 24) / 160;
                } else if (voltage < 3000) {
                    percentage = 100 - ((3000 - voltage) * 58) / 100;
                } else if (voltage >= 3000) {
                    percentage = 100;
                }
                percentage = Math.round(percentage);
            } else if (option === '3V_2500') {
                percentage = toPercentage(voltage, 2500, 3000);
            } else if (option === '3V_2500_3200') {
                percentage = toPercentage(voltage, 2500, 3200);
            } else if (option === '3V_1500_2800') {
                percentage = 235 - 370000 / (voltage + 1);
                if (percentage > 100) {
                    percentage = 100;
                } else if (percentage < 0) {
                    percentage = 0;
                }
                percentage = Math.round(percentage);
            } else if (option === '3V_2850_3200') {
                percentage = toPercentage(voltage, 2850, 3200);
            } else if (option === '3V_2850_3000_log') {
                percentage = toPercentage(voltage, 2850, 3000, true);
            } else if (option === '4LR6AA1_5v') {
                percentage = toPercentage(voltage, 3000, 4200);
            } 
        
            return percentage;
        }
        function  toPercentage(value, min, max, log=false) {
            if (value > max) {
                value = max;
            } else if (value < min) {
                value = min;
            }
        
            const normalised = (value - min) / (max - min);
            let percentage;
            if (log == true) {
                percentage = normalised === 0 ? 0 : normalised * (1 - Math.log( normalised ));
            } else {
                percentage = normalised;
            }
            return Math.round(percentage * 100);
        }
        
        P Offline
        P Offline
        pk68
        schrieb am zuletzt editiert von
        #479

        @arteck

        Ich habe es heute Mittag auf Arbeit mit Excel ausgerechnet. Habe angenommen Math.log ist der Logarithmus zur Basis 10. Pech gehabt.

        Kannst Du noch die Frage zu der Tradfri Fernbedienung beantworten (sendet Batteriestatus ja/nein)?

        arteckA 1 Antwort Letzte Antwort
        0
        • P pk68

          @arteck

          Ich habe es heute Mittag auf Arbeit mit Excel ausgerechnet. Habe angenommen Math.log ist der Logarithmus zur Basis 10. Pech gehabt.

          Kannst Du noch die Frage zu der Tradfri Fernbedienung beantworten (sendet Batteriestatus ja/nein)?

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

          @pk68 das ist die interessante zeile

          percentage = normalised === 0 ? 0 : normalised * (1 - Math.log( normalised ));
          

          008a7442-f152-4d09-bc82-b6d829d155db-grafik.png

          laut Beschreibung ja.. aber wie oft kann ich dir nicht sagen

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

          P 1 Antwort Letzte Antwort
          0
          • arteckA arteck

            @pk68 das ist die interessante zeile

            percentage = normalised === 0 ? 0 : normalised * (1 - Math.log( normalised ));
            

            008a7442-f152-4d09-bc82-b6d829d155db-grafik.png

            laut Beschreibung ja.. aber wie oft kann ich dir nicht sagen

            P Offline
            P Offline
            pk68
            schrieb am zuletzt editiert von
            #481

            @arteck ??? Die Formel ist schon klar. Ich hatte halt statt mit dem natürlichem Logarithmus mit dem Logarithmus zur Basis 10 gerechnet. Wenn Du in deinem Beispiel Math.log10 verwendest, kommt bestimmt 90% raus.

            1 Antwort Letzte Antwort
            0
            • AsgothianA Asgothian

              @diwoma sagte in ZigBee neue Version 1.6.x:

              @arteck said in ZigBee neue Version 1.6.x:

              auf GIT liegt täglich eine neue Version .. kannst also von da installieren wenn du auf dem neusten bleiben willst.
              ABER kann sein das diese nicht lauffähig ist (eher unwarscheinlich aber ich mach dich drauf aufmerksam)

              Hi, da wir nun die Adapter-Frage gelöst haben, zurück zum eigentlichen Ausgangspunkt meiner Frage:
              Soll ich warten, bis ein Zigbee-Update kommt, das die Converterliste akualisiert?

              das ist die einfachste Lösung. Updates am Zigbee Adapter kommen aktuell täglich (courtesy of @arteck) - du musst also nicht lange warten

              Soll ich den gesamten Converter per npm aktualisieren?

              Nein. Grund hab ich bereits weiter oben im Thead ausgeführt.

              Oder (eine andere Idee) nur den einen Fingerprint in der moes.js nachtragen? Beim vergeich mit der Datei auf GIT habe ich gesehen, dass nur dieser zusätzlich hinzugegeben wurde und ich könnte mir denken, dass der Rest so generisch aufgebaut ist, dass es reicht.

              Das ist die schnelle Lösung, die so lange funktioniert bis du den Adapter aktualisierst.

              A.

              D Offline
              D Offline
              diwoma
              schrieb am zuletzt editiert von diwoma
              #482

              @asgothian said in ZigBee neue Version 1.6.x:

              Oder (eine andere Idee) nur den einen Fingerprint in der moes.js nachtragen? Beim vergeich mit der Datei auf GIT habe ich gesehen, dass nur dieser zusätzlich hinzugegeben wurde und ich könnte mir denken, dass der Rest so generisch aufgebaut ist, dass es reicht.

              Das ist die schnelle Lösung, die so lange funktioniert bis du den Adapter aktualisierst.

              Nun, die Datei erweitern war nicht die richtige Lösung, Zigbee ist nicht mehr gelaufen. Anscheinend braucht der Converter dann doch noch was dazu.
              Ich habe jetzt von GIT darüber installiert und die Device-Dateien wurden aktualisiert. Das Device wurde erkannt. Einzig das Picture ist nicht zugeordnet. Kann man das selbst machen? Zur Zeit ist nur das Zigbee-Logo zu sehen:
              7f7da2e5-0228-464b-914c-78f6958eb597-grafik.png

              -- diwoma

              ioBroker in LX-Container in Proxmox
              Zigbee-Coordinator: CC2652P2-TCP FW: 20230507

              1 Antwort Letzte Antwort
              0
              • D Offline
                D Offline
                diwoma
                schrieb am zuletzt editiert von
                #483

                Werden die Einstellungen in der Konfiguration irgendwo gespeichert? Oder könnten sie irgendwo gespeichert werden?
                Die Sortierung ist immer auf Standard, das ist dann wohl die Sortierung nach der Device-Id und so wenig aussagekräftig.
                a75a1ae7-6863-4ef2-83a6-313bf52f6b08-grafik.png

                Schön wäre es, wenn man entscheiden könnte, was man beim Öffnen haben will (z.B. so wie ich immer A-Z) und das wo gespeichert ist.

                -- diwoma

                ioBroker in LX-Container in Proxmox
                Zigbee-Coordinator: CC2652P2-TCP FW: 20230507

                AsgothianA arteckA 2 Antworten Letzte Antwort
                0
                • D diwoma

                  Werden die Einstellungen in der Konfiguration irgendwo gespeichert? Oder könnten sie irgendwo gespeichert werden?
                  Die Sortierung ist immer auf Standard, das ist dann wohl die Sortierung nach der Device-Id und so wenig aussagekräftig.
                  a75a1ae7-6863-4ef2-83a6-313bf52f6b08-grafik.png

                  Schön wäre es, wenn man entscheiden könnte, was man beim Öffnen haben will (z.B. so wie ich immer A-Z) und das wo gespeichert ist.

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

                  @diwoma sagte in ZigBee neue Version 1.6.x:

                  Schön wäre es, wenn man entscheiden könnte, was man beim Öffnen haben will (z.B. so wie ich immer A-Z) und das wo gespeichert ist.

                  Das wird aktuell nicht gespeichert.

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

                  1 Antwort Letzte Antwort
                  0
                  • D diwoma

                    Werden die Einstellungen in der Konfiguration irgendwo gespeichert? Oder könnten sie irgendwo gespeichert werden?
                    Die Sortierung ist immer auf Standard, das ist dann wohl die Sortierung nach der Device-Id und so wenig aussagekräftig.
                    a75a1ae7-6863-4ef2-83a6-313bf52f6b08-grafik.png

                    Schön wäre es, wenn man entscheiden könnte, was man beim Öffnen haben will (z.B. so wie ich immer A-Z) und das wo gespeichert ist.

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

                    @diwoma nein wird nicht gespeichert da man es normalerweise nur zur anlernen nutzt.. und nicht zum 'rumfummeln'

                    für die icons kannst du mal den branch mal testen.. über GIT installieren

                    https://github.com/ioBroker/ioBroker.zigbee/tarball/nobackups
                    

                    danach adapter neustarten.. der erste aufruf kann länger dauern da die icon hier erst runntereladen werden..sollte das nicht der fall sein.. einfach nur da object löschen (nur aus der Object liste nicht läschen mit der Kachel) und adapter neu starten der wird dann wieder angelegt mit den richtigen icon..

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

                    D 1 Antwort Letzte Antwort
                    0
                    • arteckA arteck

                      @diwoma nein wird nicht gespeichert da man es normalerweise nur zur anlernen nutzt.. und nicht zum 'rumfummeln'

                      für die icons kannst du mal den branch mal testen.. über GIT installieren

                      https://github.com/ioBroker/ioBroker.zigbee/tarball/nobackups
                      

                      danach adapter neustarten.. der erste aufruf kann länger dauern da die icon hier erst runntereladen werden..sollte das nicht der fall sein.. einfach nur da object löschen (nur aus der Object liste nicht läschen mit der Kachel) und adapter neu starten der wird dann wieder angelegt mit den richtigen icon..

                      D Offline
                      D Offline
                      diwoma
                      schrieb am zuletzt editiert von
                      #486

                      @arteck
                      Ich habe das mal von GIT installiert, leider crasht jetzt der Adapter:

                      2022-05-24 12:52:59.756 - info: zigbee.0 (24117) starting. Version 1.6.18 (non-npm: ioBroker/ioBroker.zigbee#nobackups) in /opt/iobroker/node_modules/iobroker.zigbee, node: v14.18.2, js-controller: 4.0.23
                      2022-05-24 12:52:59.964 - info: zigbee.0 (24117) delete old Backup files. keep only last 10
                      2022-05-24 12:52:59.965 - error: zigbee.0 (24117) Error: ENOENT: no such file or directory, unlink '/opt/iobroker/iobroker-data/zigbee_0\backup_2022_05_20-09_34_27.tar.gz'
                      2022-05-24 12:52:59.967 - error: zigbee.0 (24117) Error: ENOENT: no such file or directory, unlink '/opt/iobroker/iobroker-data/zigbee_0\backup_2022_05_06-10_16_50.tar.gz'
                      2022-05-24 12:52:59.968 - error: zigbee.0 (24117) Error: ENOENT: no such file or directory, unlink '/opt/iobroker/iobroker-data/zigbee_0\backup_2022_04_08-11_08_47.tar.gz'
                      2022-05-24 12:52:59.969 - error: zigbee.0 (24117) Error: ENOENT: no such file or directory, unlink '/opt/iobroker/iobroker-data/zigbee_0\backup_2022_03_21-07_55_57.tar.gz'
                      2022-05-24 12:52:59.970 - error: zigbee.0 (24117) Error: ENOENT: no such file or directory, unlink '/opt/iobroker/iobroker-data/zigbee_0\backup_2022_03_18-10_08_57.tar.gz'
                      2022-05-24 12:52:59.971 - error: zigbee.0 (24117) Error: ENOENT: no such file or directory, unlink '/opt/iobroker/iobroker-data/zigbee_0\backup_2022_03_18-08_54_12.tar.gz'
                      2022-05-24 12:52:59.972 - error: zigbee.0 (24117) Error: ENOENT: no such file or directory, unlink '/opt/iobroker/iobroker-data/zigbee_0\backup_2022_03_18-08_45_29.tar.gz'
                      2022-05-24 12:52:59.974 - info: zigbee.0 (24117) Starting Zigbee npm ...
                      2022-05-24 12:53:00.566 - info: zigbee.0 (24117) Coordinator firmware version: {"type":"ConBee2/RaspBee2","meta":{"transportrev":0,"product":0,"majorrel":38,"minorrel":114,"maintrel":0,"revision":"0x26720700"}}
                      2022-05-24 12:53:00.586 - info: zigbee.0 (24117) Unable to disable LED, unsupported function.
                      2022-05-24 12:53:00.603 - info: zigbee.0 (24117) --> transmitPower : normal
                      2022-05-24 12:53:00.778 - info: zigbee.0 (24117) Unable to set transmit power, unsupported function.
                      2022-05-24 12:53:00.795 - info: zigbee.0 (24117) Currently 22 devices are joined:
                      2022-05-24 12:53:00.885 - info: zigbee.0 (24117) 0xcc86ecfffefa8e75 (addr 10983): TS0121_plug - TuYa 10A UK or 16A EU smart plug (Router)
                      2022-05-24 12:53:00.892 - info: zigbee.0 (24117) 0xcc86ecfffefa8c81 (addr 40351): TS0121_plug - TuYa 10A UK or 16A EU smart plug (Router)
                      2022-05-24 12:53:00.894 - info: zigbee.0 (24117) 0xcc86ecfffefa8fbf (addr 46151): TS0121_plug - TuYa 10A UK or 16A EU smart plug (Router)
                      2022-05-24 12:53:00.897 - info: zigbee.0 (24117) 0xb4e3f9fffed0a7d3 (addr 54857): LED1949C5 - IKEA TRADFRI LED bulb E14 470 lumen, wireless dimmable white spectrum/chandelier opal white (Router)
                      2022-05-24 12:53:00.898 - info: zigbee.0 (24117) 0x00158d0007014491 (addr 60981): WXKG11LM - Xiaomi Aqara wireless switch (EndDevice)
                      2022-05-24 12:53:00.900 - info: zigbee.0 (24117) 0x00158d000705d7eb (addr 5306): WSDCGQ11LM - Xiaomi Aqara temperature, humidity and pressure sensor (EndDevice)
                      2022-05-24 12:53:00.902 - info: zigbee.0 (24117) 0x84fd27fffe636592 (addr 16279): ZTS-EU_1gang - Moes Wall touch light switch (1 gang) (EndDevice)
                      2022-05-24 12:53:00.904 - info: zigbee.0 (24117) 0x5c0272fffe1a08fc (addr 22569): ZTS-EU_2gang - Moes Wall touch light switch (2 gang) (EndDevice)
                      2022-05-24 12:53:00.906 - info: zigbee.0 (24117) 0x00158d0007e4df68 (addr 19189): RTCGQ11LM - Xiaomi Aqara human body movement and illuminance sensor (EndDevice)
                      2022-05-24 12:53:00.908 - info: zigbee.0 (24117) 0xa4c1380b13a7ccdc (addr 62650): TS0503B - TuYa Zigbee RGB light (Router)
                      2022-05-24 12:53:00.910 - info: zigbee.0 (24117) 0x00158d0007e0e614 (addr 42568): RTCGQ11LM - Xiaomi Aqara human body movement and illuminance sensor (EndDevice)
                      2022-05-24 12:53:00.912 - info: zigbee.0 (24117) 0x00158d0006d0d895 (addr 48195): WXKG11LM - Xiaomi Aqara wireless switch (EndDevice)
                      2022-05-24 12:53:00.914 - info: zigbee.0 (24117) 0x00158d000704fe0a (addr 10152): WSDCGQ11LM - Xiaomi Aqara temperature, humidity and pressure sensor (EndDevice)
                      2022-05-24 12:53:00.917 - info: zigbee.0 (24117) 0xa4c1389993af0e21 (addr 27159): ZB-RGBCW - Lonsonho Zigbee 3.0 LED-bulb, RGBW LED (Router)
                      2022-05-24 12:53:00.920 - info: zigbee.0 (24117) 0xa4c1387a0ae125eb (addr 13955): TS011F_plug_3 - TuYa Smart plug (with power monitoring by polling) (Router)
                      2022-05-24 12:53:00.921 - info: zigbee.0 (24117) 0x00158d000705e33b (addr 63043): WSDCGQ11LM - Xiaomi Aqara temperature, humidity and pressure sensor (EndDevice)
                      2022-05-24 12:53:00.923 - info: zigbee.0 (24117) 0x00158d0007e0a744 (addr 63795): WSDCGQ11LM - Xiaomi Aqara temperature, humidity and pressure sensor (EndDevice)
                      2022-05-24 12:53:00.925 - info: zigbee.0 (24117) 0x00158d0007e086a3 (addr 7819): WSDCGQ11LM - Xiaomi Aqara temperature, humidity and pressure sensor (EndDevice)
                      2022-05-24 12:53:00.926 - info: zigbee.0 (24117) 0x847127fffec6ac1c (addr 52994): TS0201 - TuYa Temperature & humidity sensor with display (EndDevice)
                      2022-05-24 12:53:00.929 - info: zigbee.0 (24117) 0xa4c13879937e5fa8 (addr 38175): TS011F_plug_3 - TuYa Smart plug (with power monitoring by polling) (Router)
                      2022-05-24 12:53:00.931 - info: zigbee.0 (24117) 0x0c4314fffe98da63 (addr 55684): ZTS-EUR-C - Moes Zigbee + RF curtain switch (Router)
                      2022-05-24 12:53:00.932 - info: zigbee.0 (24117) 0xa4c138fa86b402b3 (addr 42671): TS130F - TuYa Curtain/blind switch (Router)
                      2022-05-24 12:53:00.933 - info: zigbee.0 (24117) Zigbee started
                      2022-05-24 12:53:00.986 - error: zigbee.0 (24117) Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().
                      2022-05-24 12:53:00.986 - error: zigbee.0 (24117) unhandled promise rejection: request is not defined
                      2022-05-24 12:53:00.988 - error: zigbee.0 (24117) ReferenceError: request is not defined
                      at download (/opt/iobroker/node_modules/iobroker.zigbee/lib/statescontroller.js:514:17)
                      at StatesController.downloadIcon (/opt/iobroker/node_modules/iobroker.zigbee/lib/statescontroller.js:531:13)
                      at StatesController.updateDev (/opt/iobroker/node_modules/iobroker.zigbee/lib/statescontroller.js:496:18)
                      at Zigbee.onZigbeeAdapterReady (/opt/iobroker/node_modules/iobroker.zigbee/main.js:370:35)
                      2022-05-24 12:53:00.988 - error: zigbee.0 (24117) request is not defined
                      2022-05-24 12:53:00.994 - error: zigbee.0 (24117) Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().
                      2022-05-24 12:53:00.994 - error: zigbee.0 (24117) unhandled promise rejection: request is not defined
                      2022-05-24 12:53:00.996 - error: zigbee.0 (24117) ReferenceError: request is not defined
                      at download (/opt/iobroker/node_modules/iobroker.zigbee/lib/statescontroller.js:514:17)
                      at StatesController.downloadIcon (/opt/iobroker/node_modules/iobroker.zigbee/lib/statescontroller.js:531:13)
                      at StatesController.updateDev (/opt/iobroker/node_modules/iobroker.zigbee/lib/statescontroller.js:496:18)
                      at Zigbee.onZigbeeAdapterReady (/opt/iobroker/node_modules/iobroker.zigbee/main.js:370:35)
                      2022-05-24 12:53:00.996 - error: zigbee.0 (24117) request is not defined
                      2022-05-24 12:53:01.000 - error: zigbee.0 (24117) Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().
                      2022-05-24 12:53:01.006 - error: zigbee.0 (24117) unhandled promise rejection: request is not defined
                      2022-05-24 12:53:01.007 - error: zigbee.0 (24117) ReferenceError: request is not defined
                      at download (/opt/iobroker/node_modules/iobroker.zigbee/lib/statescontroller.js:514:17)
                      at StatesController.downloadIcon (/opt/iobroker/node_modules/iobroker.zigbee/lib/statescontroller.js:531:13)
                      at StatesController.updateDev (/opt/iobroker/node_modules/iobroker.zigbee/lib/statescontroller.js:496:18)
                      at Zigbee.onZigbeeAdapterReady (/opt/iobroker/node_modules/iobroker.zigbee/main.js:370:35)
                      2022-05-24 12:53:01.009 - error: zigbee.0 (24117) request is not defined
                      2022-05-24 12:53:01.011 - error: zigbee.0 (24117) Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().
                      2022-05-24 12:53:01.012 - error: zigbee.0 (24117) unhandled promise rejection: request is not defined
                      2022-05-24 12:53:01.013 - error: zigbee.0 (24117) ReferenceError: request is not defined
                      at download (/opt/iobroker/node_modules/iobroker.zigbee/lib/statescontroller.js:514:17)
                      at StatesController.downloadIcon (/opt/iobroker/node_modules/iobroker.zigbee/lib/statescontroller.js:531:13)
                      at StatesController.updateDev (/opt/iobroker/node_modules/iobroker.zigbee/lib/statescontroller.js:496:18)
                      at Zigbee.onZigbeeAdapterReady (/opt/iobroker/node_modules/iobroker.zigbee/main.js:370:35)
                      2022-05-24 12:53:01.013 - error: zigbee.0 (24117) request is not defined
                      2022-05-24 12:53:01.016 - error: zigbee.0 (24117) Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().
                      2022-05-24 12:53:01.017 - error: zigbee.0 (24117) unhandled promise rejection: request is not defined
                      2022-05-24 12:53:01.018 - error: zigbee.0 (24117) ReferenceError: request is not defined
                      at download (/opt/iobroker/node_modules/iobroker.zigbee/lib/statescontroller.js:514:17)
                      at StatesController.downloadIcon (/opt/iobroker/node_modules/iobroker.zigbee/lib/statescontroller.js:531:13)
                      at StatesController.updateDev (/opt/iobroker/node_modules/iobroker.zigbee/lib/statescontroller.js:496:18)
                      at Zigbee.onZigbeeAdapterReady (/opt/iobroker/node_modules/iobroker.zigbee/main.js:370:35)
                      2022-05-24 12:53:01.018 - error: zigbee.0 (24117) request is not defined
                      2022-05-24 12:53:01.021 - error: zigbee.0 (24117) Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().
                      2022-05-24 12:53:01.022 - error: zigbee.0 (24117) unhandled promise rejection: request is not defined
                      2022-05-24 12:53:01.023 - error: zigbee.0 (24117) ReferenceError: request is not defined
                      at download (/opt/iobroker/node_modules/iobroker.zigbee/lib/statescontroller.js:514:17)
                      at StatesController.downloadIcon (/opt/iobroker/node_modules/iobroker.zigbee/lib/statescontroller.js:531:13)
                      at StatesController.updateDev (/opt/iobroker/node_modules/iobroker.zigbee/lib/statescontroller.js:496:18)
                      at Zigbee.onZigbeeAdapterReady (/opt/iobroker/node_modules/iobroker.zigbee/main.js:370:35)
                      2022-05-24 12:53:01.023 - error: zigbee.0 (24117) request is not defined
                      2022-05-24 12:53:01.026 - error: zigbee.0 (24117) Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().
                      2022-05-24 12:53:01.026 - error: zigbee.0 (24117) unhandled promise rejection: request is not defined
                      2022-05-24 12:53:01.027 - error: zigbee.0 (24117) ReferenceError: request is not defined
                      at download (/opt/iobroker/node_modules/iobroker.zigbee/lib/statescontroller.js:514:17)
                      at StatesController.downloadIcon (/opt/iobroker/node_modules/iobroker.zigbee/lib/statescontroller.js:531:13)
                      at StatesController.updateDev (/opt/iobroker/node_modules/iobroker.zigbee/lib/statescontroller.js:496:18)
                      at Zigbee.onZigbeeAdapterReady (/opt/iobroker/node_modules/iobroker.zigbee/main.js:370:35)
                      2022-05-24 12:53:01.028 - error: zigbee.0 (24117) request is not defined
                      2022-05-24 12:53:01.030 - error: zigbee.0 (24117) Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().
                      2022-05-24 12:53:01.031 - error: zigbee.0 (24117) unhandled promise rejection: request is not defined
                      2022-05-24 12:53:01.032 - error: zigbee.0 (24117) ReferenceError: request is not defined
                      at download (/opt/iobroker/node_modules/iobroker.zigbee/lib/statescontroller.js:514:17)
                      at StatesController.downloadIcon (/opt/iobroker/node_modules/iobroker.zigbee/lib/statescontroller.js:531:13)
                      at StatesController.updateDev (/opt/iobroker/node_modules/iobroker.zigbee/lib/statescontroller.js:496:18)
                      at Zigbee.onZigbeeAdapterReady (/opt/iobroker/node_modules/iobroker.zigbee/main.js:370:35)
                      2022-05-24 12:53:01.032 - error: zigbee.0 (24117) request is not defined
                      2022-05-24 12:53:01.035 - error: zigbee.0 (24117) Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().
                      2022-05-24 12:53:01.036 - error: zigbee.0 (24117) unhandled promise rejection: request is not defined
                      2022-05-24 12:53:01.037 - error: zigbee.0 (24117) ReferenceError: request is not defined
                      at download (/opt/iobroker/node_modules/iobroker.zigbee/lib/statescontroller.js:514:17)
                      at StatesController.downloadIcon (/opt/iobroker/node_modules/iobroker.zigbee/lib/statescontroller.js:531:13)
                      at StatesController.updateDev (/opt/iobroker/node_modules/iobroker.zigbee/lib/statescontroller.js:496:18)
                      at Zigbee.onZigbeeAdapterReady (/opt/iobroker/node_modules/iobroker.zigbee/main.js:370:35)
                      2022-05-24 12:53:01.037 - error: zigbee.0 (24117) request is not defined
                      2022-05-24 12:53:03.725 - info: zigbee.0 (24117) Installed Version: ioBroker/ioBroker.zigbee#nobackups
                      2022-05-24 12:53:03.801 - error: zigbee.0 (24117) Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().
                      2022-05-24 12:53:03.801 - error: zigbee.0 (24117) unhandled promise rejection: request is not defined
                      2022-05-24 12:53:03.804 - error: zigbee.0 (24117) ReferenceError: request is not defined
                      at download (/opt/iobroker/node_modules/iobroker.zigbee/lib/statescontroller.js:514:17)
                      at StatesController.downloadIcon (/opt/iobroker/node_modules/iobroker.zigbee/lib/statescontroller.js:531:13)
                      at StatesController.updateDev (/opt/iobroker/node_modules/iobroker.zigbee/lib/statescontroller.js:496:18)
                      at Immediate. (/opt/iobroker/node_modules/iobroker.zigbee/main.js:722:39)
                      at processImmediate (internal/timers.js:466:21)
                      2022-05-24 12:53:03.804 - error: zigbee.0 (24117) request is not defined
                      2022-05-24 12:53:03.824 - info: zigbee.0 (24117) cleaned everything up...
                      2022-05-24 12:53:03.911 - info: zigbee.0 (24117) Zigbee: disabling joining new devices.
                      2022-05-24 12:53:03.932 - error: zigbee.0 (24117) getGroups: caught error: TypeError: Cannot read property 'getGroups' of undefined
                      2022-05-24 12:53:04.306 - warn: zigbee.0 (24117) Object 0c4314fffe98da63.state is invalid: obj.common.states has an invalid type! Expected "object", received "string"
                      2022-05-24 12:53:04.306 - warn: zigbee.0 (24117) This object will not be created in future versions. Please report this to the developer.
                      2022-05-24 12:53:04.307 - warn: zigbee.0 (24117) Object 0c4314fffe98da63.backlight is invalid: obj.common.states has an invalid type! Expected "object", received "string"
                      2022-05-24 12:53:04.308 - warn: zigbee.0 (24117) This object will not be created in future versions. Please report this to the developer.
                      2022-05-24 12:53:04.308 - warn: zigbee.0 (24117) Object 0c4314fffe98da63.calibration is invalid: obj.common.states has an invalid type! Expected "object", received "string"
                      2022-05-24 12:53:04.309 - warn: zigbee.0 (24117) This object will not be created in future versions. Please report this to the developer.
                      2022-05-24 12:53:04.310 - warn: zigbee.0 (24117) Object 0c4314fffe98da63.motor_reversal is invalid: obj.common.states has an invalid type! Expected "object", received "string"
                      2022-05-24 12:53:04.310 - warn: zigbee.0 (24117) This object will not be created in future versions. Please report this to the developer.
                      2022-05-24 12:53:04.318 - warn: zigbee.0 (24117) Object 0c4314fffe98da63.state is invalid: obj.common.states has an invalid type! Expected "object", received "string"
                      2022-05-24 12:53:04.318 - warn: zigbee.0 (24117) This object will not be created in future versions. Please report this to the developer.
                      2022-05-24 12:53:04.321 - warn: zigbee.0 (24117) Object 0c4314fffe98da63.backlight is invalid: obj.common.states has an invalid type! Expected "object", received "string"
                      2022-05-24 12:53:04.321 - warn: zigbee.0 (24117) This object will not be created in future versions. Please report this to the developer.
                      2022-05-24 12:53:04.322 - warn: zigbee.0 (24117) Object 0c4314fffe98da63.calibration is invalid: obj.common.states has an invalid type! Expected "object", received "string"
                      2022-05-24 12:53:04.322 - warn: zigbee.0 (24117) This object will not be created in future versions. Please report this to the developer.
                      2022-05-24 12:53:04.325 - info: zigbee.0 (24117) terminating
                      2022-05-24 12:53:04.326 - warn: zigbee.0 (24117) Terminated (UNCAUGHT_EXCEPTION): Without reason
                      2022-05-24 12:53:04.328 - warn: zigbee.0 (24117) Object 0c4314fffe98da63.motor_reversal is invalid: obj.common.states has an invalid type! Expected "object", received "string"
                      2022-05-24 12:53:04.329 - warn: zigbee.0 (24117) This object will not be created in future versions. Please report this to the developer.
                      2022-05-24 12:53:04.333 - warn: zigbee.0 (24117) Object zigbee.0.0c4314fffe98da63.state is invalid: obj.common.states has an invalid type! Expected "object", received "string"
                      2022-05-24 12:53:04.333 - warn: zigbee.0 (24117) This object will not be created in future versions. Please report this to the developer.
                      2022-05-24 12:53:04.334 - warn: zigbee.0 (24117) Object zigbee.0.0c4314fffe98da63.backlight is invalid: obj.common.states has an invalid type! Expected "object", received "string"
                      2022-05-24 12:53:04.334 - warn: zigbee.0 (24117) This object will not be created in future versions. Please report this to the developer.
                      2022-05-24 12:53:04.335 - warn: zigbee.0 (24117) Object zigbee.0.0c4314fffe98da63.calibration is invalid: obj.common.states has an invalid type! Expected "object", received "string"
                      2022-05-24 12:53:04.335 - warn: zigbee.0 (24117) This object will not be created in future versions. Please report this to the developer.
                      2022-05-24 12:53:04.336 - warn: zigbee.0 (24117) Object zigbee.0.0c4314fffe98da63.motor_reversal is invalid: obj.common.states has an invalid type! Expected "object", received "string"
                      2022-05-24 12:53:04.336 - warn: zigbee.0 (24117) This object will not be created in future versions. Please report this to the developer.
                      2022-05-24 12:53:04.338 - warn: zigbee.0 (24117) Object zigbee.0.0c4314fffe98da63.state is invalid: obj.common.states has an invalid type! Expected "object", received "string"
                      2022-05-24 12:53:04.338 - warn: zigbee.0 (24117) This object will not be created in future versions. Please report this to the developer.
                      2022-05-24 12:53:04.347 - warn: zigbee.0 (24117) Object zigbee.0.0c4314fffe98da63.backlight is invalid: obj.common.states has an invalid type! Expected "object", received "string"
                      2022-05-24 12:53:04.348 - warn: zigbee.0 (24117) This object will not be created in future versions. Please report this to the developer.
                      2022-05-24 12:53:04.349 - warn: zigbee.0 (24117) Object zigbee.0.0c4314fffe98da63.calibration is invalid: obj.common.states has an invalid type! Expected "object", received "string"
                      2022-05-24 12:53:04.349 - warn: zigbee.0 (24117) This object will not be created in future versions. Please report this to the developer.
                      2022-05-24 12:53:04.350 - warn: zigbee.0 (24117) Object zigbee.0.0c4314fffe98da63.motor_reversal is invalid: obj.common.states has an invalid type! Expected "object", received "string"
                      2022-05-24 12:53:04.350 - warn: zigbee.0 (24117) This object will not be created in future versions. Please report this to the developer.
                      2022-05-24 12:53:04.929 - error: host.pi-broker Caught by controller[0]: This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason:
                      2022-05-24 12:53:04.930 - error: host.pi-broker Caught by controller[1]: ReferenceError: request is not defined
                      2022-05-24 12:53:04.930 - error: host.pi-broker Caught by controller[1]: at download (/opt/iobroker/node_modules/iobroker.zigbee/lib/statescontroller.js:514:17)
                      2022-05-24 12:53:04.931 - error: host.pi-broker Caught by controller[1]: at StatesController.downloadIcon (/opt/iobroker/node_modules/iobroker.zigbee/lib/statescontroller.js:531:13)
                      2022-05-24 12:53:04.931 - error: host.pi-broker Caught by controller[1]: at StatesController.updateDev (/opt/iobroker/node_modules/iobroker.zigbee/lib/statescontroller.js:496:18)
                      2022-05-24 12:53:04.931 - error: host.pi-broker Caught by controller[1]: at Zigbee.onZigbeeAdapterReady (/opt/iobroker/node_modules/iobroker.zigbee/main.js:370:35)
                      2022-05-24 12:53:04.931 - error: host.pi-broker Caught by controller[2]: This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason:
                      2022-05-24 12:53:04.931 - error: host.pi-broker Caught by controller[2]: ReferenceError: request is not defined
                      2022-05-24 12:53:04.932 - error: host.pi-broker Caught by controller[2]: at download (/opt/iobroker/node_modules/iobroker.zigbee/lib/statescontroller.js:514:17)
                      2022-05-24 12:53:04.932 - error: host.pi-broker Caught by controller[2]: at StatesController.downloadIcon (/opt/iobroker/node_modules/iobroker.zigbee/lib/statescontroller.js:531:13)
                      2022-05-24 12:53:04.932 - error: host.pi-broker Caught by controller[2]: at StatesController.updateDev (/opt/iobroker/node_modules/iobroker.zigbee/lib/statescontroller.js:496:18)
                      2022-05-24 12:53:04.932 - error: host.pi-broker Caught by controller[2]: at Zigbee.onZigbeeAdapterReady (/opt/iobroker/node_modules/iobroker.zigbee/main.js:370:35)
                      2022-05-24 12:53:04.932 - error: host.pi-broker Caught by controller[3]: This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason:
                      2022-05-24 12:53:04.933 - error: host.pi-broker Caught by controller[3]: ReferenceError: request is not defined
                      2022-05-24 12:53:04.933 - error: host.pi-broker Caught by controller[3]: at download (/opt/iobroker/node_modules/iobroker.zigbee/lib/statescontroller.js:514:17)
                      2022-05-24 12:53:04.933 - error: host.pi-broker Caught by controller[3]: at StatesController.downloadIcon (/opt/iobroker/node_modules/iobroker.zigbee/lib/statescontroller.js:531:13)
                      2022-05-24 12:53:04.933 - error: host.pi-broker Caught by controller[3]: at StatesController.updateDev (/opt/iobroker/node_modules/iobroker.zigbee/lib/statescontroller.js:496:18)
                      2022-05-24 12:53:04.933 - error: host.pi-broker Caught by controller[3]: at Zigbee.onZigbeeAdapterReady (/opt/iobroker/node_modules/iobroker.zigbee/main.js:370:35)
                      2022-05-24 12:53:04.934 - error: host.pi-broker Caught by controller[4]: This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason:
                      2022-05-24 12:53:04.934 - error: host.pi-broker Caught by controller[5]: ReferenceError: request is not defined
                      2022-05-24 12:53:04.934 - error: host.pi-broker Caught by controller[5]: at download (/opt/iobroker/node_modules/iobroker.zigbee/lib/statescontroller.js:514:17)
                      2022-05-24 12:53:04.934 - error: host.pi-broker Caught by controller[5]: at StatesController.downloadIcon (/opt/iobroker/node_modules/iobroker.zigbee/lib/statescontroller.js:531:13)
                      2022-05-24 12:53:04.934 - error: host.pi-broker Caught by controller[5]: at StatesController.updateDev (/opt/iobroker/node_modules/iobroker.zigbee/lib/statescontroller.js:496:18)
                      2022-05-24 12:53:04.935 - error: host.pi-broker Caught by controller[5]: at Zigbee.onZigbeeAdapterReady (/opt/iobroker/node_modules/iobroker.zigbee/main.js:370:35)
                      2022-05-24 12:53:04.935 - error: host.pi-broker Caught by controller[6]: This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason:
                      2022-05-24 12:53:04.935 - error: host.pi-broker Caught by controller[6]: ReferenceError: request is not defined
                      2022-05-24 12:53:04.935 - error: host.pi-broker Caught by controller[6]: at download (/opt/iobroker/node_modules/iobroker.zigbee/lib/statescontroller.js:514:17)
                      2022-05-24 12:53:04.935 - error: host.pi-broker Caught by controller[6]: at StatesController.downloadIcon (/opt/iobroker/node_modules/iobroker.zigbee/lib/statescontroller.js:531:13)
                      2022-05-24 12:53:04.936 - error: host.pi-broker Caught by controller[6]: at StatesController.updateDev (/opt/iobroker/node_modules/iobroker.zigbee/lib/statescontroller.js:496:18)
                      2022-05-24 12:53:04.936 - error: host.pi-broker Caught by controller[6]: at Zigbee.onZigbeeAdapterReady (/opt/iobroker/node_modules/iobroker.zigbee/main.js:370:35)
                      2022-05-24 12:53:04.936 - error: host.pi-broker Caught by controller[7]: This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason:
                      2022-05-24 12:53:04.936 - error: host.pi-broker Caught by controller[7]: ReferenceError: request is not defined
                      2022-05-24 12:53:04.936 - error: host.pi-broker Caught by controller[7]: at download (/opt/iobroker/node_modules/iobroker.zigbee/lib/statescontroller.js:514:17)
                      2022-05-24 12:53:04.937 - error: host.pi-broker Caught by controller[7]: at StatesController.downloadIcon (/opt/iobroker/node_modules/iobroker.zigbee/lib/statescontroller.js:531:13)
                      2022-05-24 12:53:04.937 - error: host.pi-broker Caught by controller[7]: at StatesController.updateDev (/opt/iobroker/node_modules/iobroker.zigbee/lib/statescontroller.js:496:18)
                      2022-05-24 12:53:04.937 - error: host.pi-broker Caught by controller[7]: at Zigbee.onZigbeeAdapterReady (/opt/iobroker/node_modules/iobroker.zigbee/main.js:370:35)
                      2022-05-24 12:53:04.937 - error: host.pi-broker Caught by controller[8]: This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason:
                      2022-05-24 12:53:04.937 - error: host.pi-broker Caught by controller[9]: ReferenceError: request is not defined
                      2022-05-24 12:53:04.938 - error: host.pi-broker Caught by controller[9]: at download (/opt/iobroker/node_modules/iobroker.zigbee/lib/statescontroller.js:514:17)
                      2022-05-24 12:53:04.938 - error: host.pi-broker Caught by controller[9]: at StatesController.downloadIcon (/opt/iobroker/node_modules/iobroker.zigbee/lib/statescontroller.js:531:13)
                      2022-05-24 12:53:04.938 - error: host.pi-broker Caught by controller[9]: at StatesController.updateDev (/opt/iobroker/node_modules/iobroker.zigbee/lib/statescontroller.js:496:18)
                      2022-05-24 12:53:04.938 - error: host.pi-broker Caught by controller[9]: at Zigbee.onZigbeeAdapterReady (/opt/iobroker/node_modules/iobroker.zigbee/main.js:370:35)
                      2022-05-24 12:53:04.938 - error: host.pi-broker Caught by controller[10]: This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason:
                      2022-05-24 12:53:04.938 - error: host.pi-broker Caught by controller[11]: ReferenceError: request is not defined
                      2022-05-24 12:53:04.939 - error: host.pi-broker Caught by controller[11]: at download (/opt/iobroker/node_modules/iobroker.zigbee/lib/statescontroller.js:514:17)
                      2022-05-24 12:53:04.939 - error: host.pi-broker Caught by controller[11]: at StatesController.downloadIcon (/opt/iobroker/node_modules/iobroker.zigbee/lib/statescontroller.js:531:13)
                      2022-05-24 12:53:04.939 - error: host.pi-broker Caught by controller[11]: at StatesController.updateDev (/opt/iobroker/node_modules/iobroker.zigbee/lib/statescontroller.js:496:18)
                      2022-05-24 12:53:04.939 - error: host.pi-broker Caught by controller[11]: at Zigbee.onZigbeeAdapterReady (/opt/iobroker/node_modules/iobroker.zigbee/main.js:370:35)
                      2022-05-24 12:53:04.939 - error: host.pi-broker Caught by controller[12]: This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason:
                      2022-05-24 12:53:04.940 - error: host.pi-broker Caught by controller[13]: ReferenceError: request is not defined
                      2022-05-24 12:53:04.940 - error: host.pi-broker Caught by controller[13]: at download (/opt/iobroker/node_modules/iobroker.zigbee/lib/statescontroller.js:514:17)
                      2022-05-24 12:53:04.940 - error: host.pi-broker Caught by controller[13]: at StatesController.downloadIcon (/opt/iobroker/node_modules/iobroker.zigbee/lib/statescontroller.js:531:13)
                      2022-05-24 12:53:04.940 - error: host.pi-broker Caught by controller[13]: at StatesController.updateDev (/opt/iobroker/node_modules/iobroker.zigbee/lib/statescontroller.js:496:18)
                      2022-05-24 12:53:04.940 - error: host.pi-broker Caught by controller[13]: at Zigbee.onZigbeeAdapterReady (/opt/iobroker/node_modules/iobroker.zigbee/main.js:370:35)
                      2022-05-24 12:53:04.941 - error: host.pi-broker Caught by controller[14]: This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason:
                      2022-05-24 12:53:04.941 - error: host.pi-broker Caught by controller[15]: ReferenceError: request is not defined
                      2022-05-24 12:53:04.941 - error: host.pi-broker Caught by controller[15]: at download (/opt/iobroker/node_modules/iobroker.zigbee/lib/statescontroller.js:514:17)
                      2022-05-24 12:53:04.941 - error: host.pi-broker Caught by controller[15]: at StatesController.downloadIcon (/opt/iobroker/node_modules/iobroker.zigbee/lib/statescontroller.js:531:13)
                      2022-05-24 12:53:04.941 - error: host.pi-broker Caught by controller[15]: at StatesController.updateDev (/opt/iobroker/node_modules/iobroker.zigbee/lib/statescontroller.js:496:18)
                      2022-05-24 12:53:04.941 - error: host.pi-broker Caught by controller[15]: at Immediate. (/opt/iobroker/node_modules/iobroker.zigbee/main.js:722:39)
                      2022-05-24 12:53:04.942 - error: host.pi-broker Caught by controller[15]: at processImmediate (internal/timers.js:466:21)
                      2022-05-24 12:53:04.942 - error: host.pi-broker instance system.adapter.zigbee.0 terminated with code 6 (UNCAUGHT_EXCEPTION)
                      

                      Host verhindert nach ein paar versuchen den Neustart.

                      -- diwoma

                      ioBroker in LX-Container in Proxmox
                      Zigbee-Coordinator: CC2652P2-TCP FW: 20230507

                      arteckA 1 Antwort Letzte Antwort
                      0
                      • D diwoma

                        @arteck
                        Ich habe das mal von GIT installiert, leider crasht jetzt der Adapter:

                        2022-05-24 12:52:59.756 - info: zigbee.0 (24117) starting. Version 1.6.18 (non-npm: ioBroker/ioBroker.zigbee#nobackups) in /opt/iobroker/node_modules/iobroker.zigbee, node: v14.18.2, js-controller: 4.0.23
                        2022-05-24 12:52:59.964 - info: zigbee.0 (24117) delete old Backup files. keep only last 10
                        2022-05-24 12:52:59.965 - error: zigbee.0 (24117) Error: ENOENT: no such file or directory, unlink '/opt/iobroker/iobroker-data/zigbee_0\backup_2022_05_20-09_34_27.tar.gz'
                        2022-05-24 12:52:59.967 - error: zigbee.0 (24117) Error: ENOENT: no such file or directory, unlink '/opt/iobroker/iobroker-data/zigbee_0\backup_2022_05_06-10_16_50.tar.gz'
                        2022-05-24 12:52:59.968 - error: zigbee.0 (24117) Error: ENOENT: no such file or directory, unlink '/opt/iobroker/iobroker-data/zigbee_0\backup_2022_04_08-11_08_47.tar.gz'
                        2022-05-24 12:52:59.969 - error: zigbee.0 (24117) Error: ENOENT: no such file or directory, unlink '/opt/iobroker/iobroker-data/zigbee_0\backup_2022_03_21-07_55_57.tar.gz'
                        2022-05-24 12:52:59.970 - error: zigbee.0 (24117) Error: ENOENT: no such file or directory, unlink '/opt/iobroker/iobroker-data/zigbee_0\backup_2022_03_18-10_08_57.tar.gz'
                        2022-05-24 12:52:59.971 - error: zigbee.0 (24117) Error: ENOENT: no such file or directory, unlink '/opt/iobroker/iobroker-data/zigbee_0\backup_2022_03_18-08_54_12.tar.gz'
                        2022-05-24 12:52:59.972 - error: zigbee.0 (24117) Error: ENOENT: no such file or directory, unlink '/opt/iobroker/iobroker-data/zigbee_0\backup_2022_03_18-08_45_29.tar.gz'
                        2022-05-24 12:52:59.974 - info: zigbee.0 (24117) Starting Zigbee npm ...
                        2022-05-24 12:53:00.566 - info: zigbee.0 (24117) Coordinator firmware version: {"type":"ConBee2/RaspBee2","meta":{"transportrev":0,"product":0,"majorrel":38,"minorrel":114,"maintrel":0,"revision":"0x26720700"}}
                        2022-05-24 12:53:00.586 - info: zigbee.0 (24117) Unable to disable LED, unsupported function.
                        2022-05-24 12:53:00.603 - info: zigbee.0 (24117) --> transmitPower : normal
                        2022-05-24 12:53:00.778 - info: zigbee.0 (24117) Unable to set transmit power, unsupported function.
                        2022-05-24 12:53:00.795 - info: zigbee.0 (24117) Currently 22 devices are joined:
                        2022-05-24 12:53:00.885 - info: zigbee.0 (24117) 0xcc86ecfffefa8e75 (addr 10983): TS0121_plug - TuYa 10A UK or 16A EU smart plug (Router)
                        2022-05-24 12:53:00.892 - info: zigbee.0 (24117) 0xcc86ecfffefa8c81 (addr 40351): TS0121_plug - TuYa 10A UK or 16A EU smart plug (Router)
                        2022-05-24 12:53:00.894 - info: zigbee.0 (24117) 0xcc86ecfffefa8fbf (addr 46151): TS0121_plug - TuYa 10A UK or 16A EU smart plug (Router)
                        2022-05-24 12:53:00.897 - info: zigbee.0 (24117) 0xb4e3f9fffed0a7d3 (addr 54857): LED1949C5 - IKEA TRADFRI LED bulb E14 470 lumen, wireless dimmable white spectrum/chandelier opal white (Router)
                        2022-05-24 12:53:00.898 - info: zigbee.0 (24117) 0x00158d0007014491 (addr 60981): WXKG11LM - Xiaomi Aqara wireless switch (EndDevice)
                        2022-05-24 12:53:00.900 - info: zigbee.0 (24117) 0x00158d000705d7eb (addr 5306): WSDCGQ11LM - Xiaomi Aqara temperature, humidity and pressure sensor (EndDevice)
                        2022-05-24 12:53:00.902 - info: zigbee.0 (24117) 0x84fd27fffe636592 (addr 16279): ZTS-EU_1gang - Moes Wall touch light switch (1 gang) (EndDevice)
                        2022-05-24 12:53:00.904 - info: zigbee.0 (24117) 0x5c0272fffe1a08fc (addr 22569): ZTS-EU_2gang - Moes Wall touch light switch (2 gang) (EndDevice)
                        2022-05-24 12:53:00.906 - info: zigbee.0 (24117) 0x00158d0007e4df68 (addr 19189): RTCGQ11LM - Xiaomi Aqara human body movement and illuminance sensor (EndDevice)
                        2022-05-24 12:53:00.908 - info: zigbee.0 (24117) 0xa4c1380b13a7ccdc (addr 62650): TS0503B - TuYa Zigbee RGB light (Router)
                        2022-05-24 12:53:00.910 - info: zigbee.0 (24117) 0x00158d0007e0e614 (addr 42568): RTCGQ11LM - Xiaomi Aqara human body movement and illuminance sensor (EndDevice)
                        2022-05-24 12:53:00.912 - info: zigbee.0 (24117) 0x00158d0006d0d895 (addr 48195): WXKG11LM - Xiaomi Aqara wireless switch (EndDevice)
                        2022-05-24 12:53:00.914 - info: zigbee.0 (24117) 0x00158d000704fe0a (addr 10152): WSDCGQ11LM - Xiaomi Aqara temperature, humidity and pressure sensor (EndDevice)
                        2022-05-24 12:53:00.917 - info: zigbee.0 (24117) 0xa4c1389993af0e21 (addr 27159): ZB-RGBCW - Lonsonho Zigbee 3.0 LED-bulb, RGBW LED (Router)
                        2022-05-24 12:53:00.920 - info: zigbee.0 (24117) 0xa4c1387a0ae125eb (addr 13955): TS011F_plug_3 - TuYa Smart plug (with power monitoring by polling) (Router)
                        2022-05-24 12:53:00.921 - info: zigbee.0 (24117) 0x00158d000705e33b (addr 63043): WSDCGQ11LM - Xiaomi Aqara temperature, humidity and pressure sensor (EndDevice)
                        2022-05-24 12:53:00.923 - info: zigbee.0 (24117) 0x00158d0007e0a744 (addr 63795): WSDCGQ11LM - Xiaomi Aqara temperature, humidity and pressure sensor (EndDevice)
                        2022-05-24 12:53:00.925 - info: zigbee.0 (24117) 0x00158d0007e086a3 (addr 7819): WSDCGQ11LM - Xiaomi Aqara temperature, humidity and pressure sensor (EndDevice)
                        2022-05-24 12:53:00.926 - info: zigbee.0 (24117) 0x847127fffec6ac1c (addr 52994): TS0201 - TuYa Temperature & humidity sensor with display (EndDevice)
                        2022-05-24 12:53:00.929 - info: zigbee.0 (24117) 0xa4c13879937e5fa8 (addr 38175): TS011F_plug_3 - TuYa Smart plug (with power monitoring by polling) (Router)
                        2022-05-24 12:53:00.931 - info: zigbee.0 (24117) 0x0c4314fffe98da63 (addr 55684): ZTS-EUR-C - Moes Zigbee + RF curtain switch (Router)
                        2022-05-24 12:53:00.932 - info: zigbee.0 (24117) 0xa4c138fa86b402b3 (addr 42671): TS130F - TuYa Curtain/blind switch (Router)
                        2022-05-24 12:53:00.933 - info: zigbee.0 (24117) Zigbee started
                        2022-05-24 12:53:00.986 - error: zigbee.0 (24117) Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().
                        2022-05-24 12:53:00.986 - error: zigbee.0 (24117) unhandled promise rejection: request is not defined
                        2022-05-24 12:53:00.988 - error: zigbee.0 (24117) ReferenceError: request is not defined
                        at download (/opt/iobroker/node_modules/iobroker.zigbee/lib/statescontroller.js:514:17)
                        at StatesController.downloadIcon (/opt/iobroker/node_modules/iobroker.zigbee/lib/statescontroller.js:531:13)
                        at StatesController.updateDev (/opt/iobroker/node_modules/iobroker.zigbee/lib/statescontroller.js:496:18)
                        at Zigbee.onZigbeeAdapterReady (/opt/iobroker/node_modules/iobroker.zigbee/main.js:370:35)
                        2022-05-24 12:53:00.988 - error: zigbee.0 (24117) request is not defined
                        2022-05-24 12:53:00.994 - error: zigbee.0 (24117) Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().
                        2022-05-24 12:53:00.994 - error: zigbee.0 (24117) unhandled promise rejection: request is not defined
                        2022-05-24 12:53:00.996 - error: zigbee.0 (24117) ReferenceError: request is not defined
                        at download (/opt/iobroker/node_modules/iobroker.zigbee/lib/statescontroller.js:514:17)
                        at StatesController.downloadIcon (/opt/iobroker/node_modules/iobroker.zigbee/lib/statescontroller.js:531:13)
                        at StatesController.updateDev (/opt/iobroker/node_modules/iobroker.zigbee/lib/statescontroller.js:496:18)
                        at Zigbee.onZigbeeAdapterReady (/opt/iobroker/node_modules/iobroker.zigbee/main.js:370:35)
                        2022-05-24 12:53:00.996 - error: zigbee.0 (24117) request is not defined
                        2022-05-24 12:53:01.000 - error: zigbee.0 (24117) Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().
                        2022-05-24 12:53:01.006 - error: zigbee.0 (24117) unhandled promise rejection: request is not defined
                        2022-05-24 12:53:01.007 - error: zigbee.0 (24117) ReferenceError: request is not defined
                        at download (/opt/iobroker/node_modules/iobroker.zigbee/lib/statescontroller.js:514:17)
                        at StatesController.downloadIcon (/opt/iobroker/node_modules/iobroker.zigbee/lib/statescontroller.js:531:13)
                        at StatesController.updateDev (/opt/iobroker/node_modules/iobroker.zigbee/lib/statescontroller.js:496:18)
                        at Zigbee.onZigbeeAdapterReady (/opt/iobroker/node_modules/iobroker.zigbee/main.js:370:35)
                        2022-05-24 12:53:01.009 - error: zigbee.0 (24117) request is not defined
                        2022-05-24 12:53:01.011 - error: zigbee.0 (24117) Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().
                        2022-05-24 12:53:01.012 - error: zigbee.0 (24117) unhandled promise rejection: request is not defined
                        2022-05-24 12:53:01.013 - error: zigbee.0 (24117) ReferenceError: request is not defined
                        at download (/opt/iobroker/node_modules/iobroker.zigbee/lib/statescontroller.js:514:17)
                        at StatesController.downloadIcon (/opt/iobroker/node_modules/iobroker.zigbee/lib/statescontroller.js:531:13)
                        at StatesController.updateDev (/opt/iobroker/node_modules/iobroker.zigbee/lib/statescontroller.js:496:18)
                        at Zigbee.onZigbeeAdapterReady (/opt/iobroker/node_modules/iobroker.zigbee/main.js:370:35)
                        2022-05-24 12:53:01.013 - error: zigbee.0 (24117) request is not defined
                        2022-05-24 12:53:01.016 - error: zigbee.0 (24117) Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().
                        2022-05-24 12:53:01.017 - error: zigbee.0 (24117) unhandled promise rejection: request is not defined
                        2022-05-24 12:53:01.018 - error: zigbee.0 (24117) ReferenceError: request is not defined
                        at download (/opt/iobroker/node_modules/iobroker.zigbee/lib/statescontroller.js:514:17)
                        at StatesController.downloadIcon (/opt/iobroker/node_modules/iobroker.zigbee/lib/statescontroller.js:531:13)
                        at StatesController.updateDev (/opt/iobroker/node_modules/iobroker.zigbee/lib/statescontroller.js:496:18)
                        at Zigbee.onZigbeeAdapterReady (/opt/iobroker/node_modules/iobroker.zigbee/main.js:370:35)
                        2022-05-24 12:53:01.018 - error: zigbee.0 (24117) request is not defined
                        2022-05-24 12:53:01.021 - error: zigbee.0 (24117) Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().
                        2022-05-24 12:53:01.022 - error: zigbee.0 (24117) unhandled promise rejection: request is not defined
                        2022-05-24 12:53:01.023 - error: zigbee.0 (24117) ReferenceError: request is not defined
                        at download (/opt/iobroker/node_modules/iobroker.zigbee/lib/statescontroller.js:514:17)
                        at StatesController.downloadIcon (/opt/iobroker/node_modules/iobroker.zigbee/lib/statescontroller.js:531:13)
                        at StatesController.updateDev (/opt/iobroker/node_modules/iobroker.zigbee/lib/statescontroller.js:496:18)
                        at Zigbee.onZigbeeAdapterReady (/opt/iobroker/node_modules/iobroker.zigbee/main.js:370:35)
                        2022-05-24 12:53:01.023 - error: zigbee.0 (24117) request is not defined
                        2022-05-24 12:53:01.026 - error: zigbee.0 (24117) Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().
                        2022-05-24 12:53:01.026 - error: zigbee.0 (24117) unhandled promise rejection: request is not defined
                        2022-05-24 12:53:01.027 - error: zigbee.0 (24117) ReferenceError: request is not defined
                        at download (/opt/iobroker/node_modules/iobroker.zigbee/lib/statescontroller.js:514:17)
                        at StatesController.downloadIcon (/opt/iobroker/node_modules/iobroker.zigbee/lib/statescontroller.js:531:13)
                        at StatesController.updateDev (/opt/iobroker/node_modules/iobroker.zigbee/lib/statescontroller.js:496:18)
                        at Zigbee.onZigbeeAdapterReady (/opt/iobroker/node_modules/iobroker.zigbee/main.js:370:35)
                        2022-05-24 12:53:01.028 - error: zigbee.0 (24117) request is not defined
                        2022-05-24 12:53:01.030 - error: zigbee.0 (24117) Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().
                        2022-05-24 12:53:01.031 - error: zigbee.0 (24117) unhandled promise rejection: request is not defined
                        2022-05-24 12:53:01.032 - error: zigbee.0 (24117) ReferenceError: request is not defined
                        at download (/opt/iobroker/node_modules/iobroker.zigbee/lib/statescontroller.js:514:17)
                        at StatesController.downloadIcon (/opt/iobroker/node_modules/iobroker.zigbee/lib/statescontroller.js:531:13)
                        at StatesController.updateDev (/opt/iobroker/node_modules/iobroker.zigbee/lib/statescontroller.js:496:18)
                        at Zigbee.onZigbeeAdapterReady (/opt/iobroker/node_modules/iobroker.zigbee/main.js:370:35)
                        2022-05-24 12:53:01.032 - error: zigbee.0 (24117) request is not defined
                        2022-05-24 12:53:01.035 - error: zigbee.0 (24117) Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().
                        2022-05-24 12:53:01.036 - error: zigbee.0 (24117) unhandled promise rejection: request is not defined
                        2022-05-24 12:53:01.037 - error: zigbee.0 (24117) ReferenceError: request is not defined
                        at download (/opt/iobroker/node_modules/iobroker.zigbee/lib/statescontroller.js:514:17)
                        at StatesController.downloadIcon (/opt/iobroker/node_modules/iobroker.zigbee/lib/statescontroller.js:531:13)
                        at StatesController.updateDev (/opt/iobroker/node_modules/iobroker.zigbee/lib/statescontroller.js:496:18)
                        at Zigbee.onZigbeeAdapterReady (/opt/iobroker/node_modules/iobroker.zigbee/main.js:370:35)
                        2022-05-24 12:53:01.037 - error: zigbee.0 (24117) request is not defined
                        2022-05-24 12:53:03.725 - info: zigbee.0 (24117) Installed Version: ioBroker/ioBroker.zigbee#nobackups
                        2022-05-24 12:53:03.801 - error: zigbee.0 (24117) Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().
                        2022-05-24 12:53:03.801 - error: zigbee.0 (24117) unhandled promise rejection: request is not defined
                        2022-05-24 12:53:03.804 - error: zigbee.0 (24117) ReferenceError: request is not defined
                        at download (/opt/iobroker/node_modules/iobroker.zigbee/lib/statescontroller.js:514:17)
                        at StatesController.downloadIcon (/opt/iobroker/node_modules/iobroker.zigbee/lib/statescontroller.js:531:13)
                        at StatesController.updateDev (/opt/iobroker/node_modules/iobroker.zigbee/lib/statescontroller.js:496:18)
                        at Immediate. (/opt/iobroker/node_modules/iobroker.zigbee/main.js:722:39)
                        at processImmediate (internal/timers.js:466:21)
                        2022-05-24 12:53:03.804 - error: zigbee.0 (24117) request is not defined
                        2022-05-24 12:53:03.824 - info: zigbee.0 (24117) cleaned everything up...
                        2022-05-24 12:53:03.911 - info: zigbee.0 (24117) Zigbee: disabling joining new devices.
                        2022-05-24 12:53:03.932 - error: zigbee.0 (24117) getGroups: caught error: TypeError: Cannot read property 'getGroups' of undefined
                        2022-05-24 12:53:04.306 - warn: zigbee.0 (24117) Object 0c4314fffe98da63.state is invalid: obj.common.states has an invalid type! Expected "object", received "string"
                        2022-05-24 12:53:04.306 - warn: zigbee.0 (24117) This object will not be created in future versions. Please report this to the developer.
                        2022-05-24 12:53:04.307 - warn: zigbee.0 (24117) Object 0c4314fffe98da63.backlight is invalid: obj.common.states has an invalid type! Expected "object", received "string"
                        2022-05-24 12:53:04.308 - warn: zigbee.0 (24117) This object will not be created in future versions. Please report this to the developer.
                        2022-05-24 12:53:04.308 - warn: zigbee.0 (24117) Object 0c4314fffe98da63.calibration is invalid: obj.common.states has an invalid type! Expected "object", received "string"
                        2022-05-24 12:53:04.309 - warn: zigbee.0 (24117) This object will not be created in future versions. Please report this to the developer.
                        2022-05-24 12:53:04.310 - warn: zigbee.0 (24117) Object 0c4314fffe98da63.motor_reversal is invalid: obj.common.states has an invalid type! Expected "object", received "string"
                        2022-05-24 12:53:04.310 - warn: zigbee.0 (24117) This object will not be created in future versions. Please report this to the developer.
                        2022-05-24 12:53:04.318 - warn: zigbee.0 (24117) Object 0c4314fffe98da63.state is invalid: obj.common.states has an invalid type! Expected "object", received "string"
                        2022-05-24 12:53:04.318 - warn: zigbee.0 (24117) This object will not be created in future versions. Please report this to the developer.
                        2022-05-24 12:53:04.321 - warn: zigbee.0 (24117) Object 0c4314fffe98da63.backlight is invalid: obj.common.states has an invalid type! Expected "object", received "string"
                        2022-05-24 12:53:04.321 - warn: zigbee.0 (24117) This object will not be created in future versions. Please report this to the developer.
                        2022-05-24 12:53:04.322 - warn: zigbee.0 (24117) Object 0c4314fffe98da63.calibration is invalid: obj.common.states has an invalid type! Expected "object", received "string"
                        2022-05-24 12:53:04.322 - warn: zigbee.0 (24117) This object will not be created in future versions. Please report this to the developer.
                        2022-05-24 12:53:04.325 - info: zigbee.0 (24117) terminating
                        2022-05-24 12:53:04.326 - warn: zigbee.0 (24117) Terminated (UNCAUGHT_EXCEPTION): Without reason
                        2022-05-24 12:53:04.328 - warn: zigbee.0 (24117) Object 0c4314fffe98da63.motor_reversal is invalid: obj.common.states has an invalid type! Expected "object", received "string"
                        2022-05-24 12:53:04.329 - warn: zigbee.0 (24117) This object will not be created in future versions. Please report this to the developer.
                        2022-05-24 12:53:04.333 - warn: zigbee.0 (24117) Object zigbee.0.0c4314fffe98da63.state is invalid: obj.common.states has an invalid type! Expected "object", received "string"
                        2022-05-24 12:53:04.333 - warn: zigbee.0 (24117) This object will not be created in future versions. Please report this to the developer.
                        2022-05-24 12:53:04.334 - warn: zigbee.0 (24117) Object zigbee.0.0c4314fffe98da63.backlight is invalid: obj.common.states has an invalid type! Expected "object", received "string"
                        2022-05-24 12:53:04.334 - warn: zigbee.0 (24117) This object will not be created in future versions. Please report this to the developer.
                        2022-05-24 12:53:04.335 - warn: zigbee.0 (24117) Object zigbee.0.0c4314fffe98da63.calibration is invalid: obj.common.states has an invalid type! Expected "object", received "string"
                        2022-05-24 12:53:04.335 - warn: zigbee.0 (24117) This object will not be created in future versions. Please report this to the developer.
                        2022-05-24 12:53:04.336 - warn: zigbee.0 (24117) Object zigbee.0.0c4314fffe98da63.motor_reversal is invalid: obj.common.states has an invalid type! Expected "object", received "string"
                        2022-05-24 12:53:04.336 - warn: zigbee.0 (24117) This object will not be created in future versions. Please report this to the developer.
                        2022-05-24 12:53:04.338 - warn: zigbee.0 (24117) Object zigbee.0.0c4314fffe98da63.state is invalid: obj.common.states has an invalid type! Expected "object", received "string"
                        2022-05-24 12:53:04.338 - warn: zigbee.0 (24117) This object will not be created in future versions. Please report this to the developer.
                        2022-05-24 12:53:04.347 - warn: zigbee.0 (24117) Object zigbee.0.0c4314fffe98da63.backlight is invalid: obj.common.states has an invalid type! Expected "object", received "string"
                        2022-05-24 12:53:04.348 - warn: zigbee.0 (24117) This object will not be created in future versions. Please report this to the developer.
                        2022-05-24 12:53:04.349 - warn: zigbee.0 (24117) Object zigbee.0.0c4314fffe98da63.calibration is invalid: obj.common.states has an invalid type! Expected "object", received "string"
                        2022-05-24 12:53:04.349 - warn: zigbee.0 (24117) This object will not be created in future versions. Please report this to the developer.
                        2022-05-24 12:53:04.350 - warn: zigbee.0 (24117) Object zigbee.0.0c4314fffe98da63.motor_reversal is invalid: obj.common.states has an invalid type! Expected "object", received "string"
                        2022-05-24 12:53:04.350 - warn: zigbee.0 (24117) This object will not be created in future versions. Please report this to the developer.
                        2022-05-24 12:53:04.929 - error: host.pi-broker Caught by controller[0]: This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason:
                        2022-05-24 12:53:04.930 - error: host.pi-broker Caught by controller[1]: ReferenceError: request is not defined
                        2022-05-24 12:53:04.930 - error: host.pi-broker Caught by controller[1]: at download (/opt/iobroker/node_modules/iobroker.zigbee/lib/statescontroller.js:514:17)
                        2022-05-24 12:53:04.931 - error: host.pi-broker Caught by controller[1]: at StatesController.downloadIcon (/opt/iobroker/node_modules/iobroker.zigbee/lib/statescontroller.js:531:13)
                        2022-05-24 12:53:04.931 - error: host.pi-broker Caught by controller[1]: at StatesController.updateDev (/opt/iobroker/node_modules/iobroker.zigbee/lib/statescontroller.js:496:18)
                        2022-05-24 12:53:04.931 - error: host.pi-broker Caught by controller[1]: at Zigbee.onZigbeeAdapterReady (/opt/iobroker/node_modules/iobroker.zigbee/main.js:370:35)
                        2022-05-24 12:53:04.931 - error: host.pi-broker Caught by controller[2]: This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason:
                        2022-05-24 12:53:04.931 - error: host.pi-broker Caught by controller[2]: ReferenceError: request is not defined
                        2022-05-24 12:53:04.932 - error: host.pi-broker Caught by controller[2]: at download (/opt/iobroker/node_modules/iobroker.zigbee/lib/statescontroller.js:514:17)
                        2022-05-24 12:53:04.932 - error: host.pi-broker Caught by controller[2]: at StatesController.downloadIcon (/opt/iobroker/node_modules/iobroker.zigbee/lib/statescontroller.js:531:13)
                        2022-05-24 12:53:04.932 - error: host.pi-broker Caught by controller[2]: at StatesController.updateDev (/opt/iobroker/node_modules/iobroker.zigbee/lib/statescontroller.js:496:18)
                        2022-05-24 12:53:04.932 - error: host.pi-broker Caught by controller[2]: at Zigbee.onZigbeeAdapterReady (/opt/iobroker/node_modules/iobroker.zigbee/main.js:370:35)
                        2022-05-24 12:53:04.932 - error: host.pi-broker Caught by controller[3]: This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason:
                        2022-05-24 12:53:04.933 - error: host.pi-broker Caught by controller[3]: ReferenceError: request is not defined
                        2022-05-24 12:53:04.933 - error: host.pi-broker Caught by controller[3]: at download (/opt/iobroker/node_modules/iobroker.zigbee/lib/statescontroller.js:514:17)
                        2022-05-24 12:53:04.933 - error: host.pi-broker Caught by controller[3]: at StatesController.downloadIcon (/opt/iobroker/node_modules/iobroker.zigbee/lib/statescontroller.js:531:13)
                        2022-05-24 12:53:04.933 - error: host.pi-broker Caught by controller[3]: at StatesController.updateDev (/opt/iobroker/node_modules/iobroker.zigbee/lib/statescontroller.js:496:18)
                        2022-05-24 12:53:04.933 - error: host.pi-broker Caught by controller[3]: at Zigbee.onZigbeeAdapterReady (/opt/iobroker/node_modules/iobroker.zigbee/main.js:370:35)
                        2022-05-24 12:53:04.934 - error: host.pi-broker Caught by controller[4]: This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason:
                        2022-05-24 12:53:04.934 - error: host.pi-broker Caught by controller[5]: ReferenceError: request is not defined
                        2022-05-24 12:53:04.934 - error: host.pi-broker Caught by controller[5]: at download (/opt/iobroker/node_modules/iobroker.zigbee/lib/statescontroller.js:514:17)
                        2022-05-24 12:53:04.934 - error: host.pi-broker Caught by controller[5]: at StatesController.downloadIcon (/opt/iobroker/node_modules/iobroker.zigbee/lib/statescontroller.js:531:13)
                        2022-05-24 12:53:04.934 - error: host.pi-broker Caught by controller[5]: at StatesController.updateDev (/opt/iobroker/node_modules/iobroker.zigbee/lib/statescontroller.js:496:18)
                        2022-05-24 12:53:04.935 - error: host.pi-broker Caught by controller[5]: at Zigbee.onZigbeeAdapterReady (/opt/iobroker/node_modules/iobroker.zigbee/main.js:370:35)
                        2022-05-24 12:53:04.935 - error: host.pi-broker Caught by controller[6]: This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason:
                        2022-05-24 12:53:04.935 - error: host.pi-broker Caught by controller[6]: ReferenceError: request is not defined
                        2022-05-24 12:53:04.935 - error: host.pi-broker Caught by controller[6]: at download (/opt/iobroker/node_modules/iobroker.zigbee/lib/statescontroller.js:514:17)
                        2022-05-24 12:53:04.935 - error: host.pi-broker Caught by controller[6]: at StatesController.downloadIcon (/opt/iobroker/node_modules/iobroker.zigbee/lib/statescontroller.js:531:13)
                        2022-05-24 12:53:04.936 - error: host.pi-broker Caught by controller[6]: at StatesController.updateDev (/opt/iobroker/node_modules/iobroker.zigbee/lib/statescontroller.js:496:18)
                        2022-05-24 12:53:04.936 - error: host.pi-broker Caught by controller[6]: at Zigbee.onZigbeeAdapterReady (/opt/iobroker/node_modules/iobroker.zigbee/main.js:370:35)
                        2022-05-24 12:53:04.936 - error: host.pi-broker Caught by controller[7]: This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason:
                        2022-05-24 12:53:04.936 - error: host.pi-broker Caught by controller[7]: ReferenceError: request is not defined
                        2022-05-24 12:53:04.936 - error: host.pi-broker Caught by controller[7]: at download (/opt/iobroker/node_modules/iobroker.zigbee/lib/statescontroller.js:514:17)
                        2022-05-24 12:53:04.937 - error: host.pi-broker Caught by controller[7]: at StatesController.downloadIcon (/opt/iobroker/node_modules/iobroker.zigbee/lib/statescontroller.js:531:13)
                        2022-05-24 12:53:04.937 - error: host.pi-broker Caught by controller[7]: at StatesController.updateDev (/opt/iobroker/node_modules/iobroker.zigbee/lib/statescontroller.js:496:18)
                        2022-05-24 12:53:04.937 - error: host.pi-broker Caught by controller[7]: at Zigbee.onZigbeeAdapterReady (/opt/iobroker/node_modules/iobroker.zigbee/main.js:370:35)
                        2022-05-24 12:53:04.937 - error: host.pi-broker Caught by controller[8]: This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason:
                        2022-05-24 12:53:04.937 - error: host.pi-broker Caught by controller[9]: ReferenceError: request is not defined
                        2022-05-24 12:53:04.938 - error: host.pi-broker Caught by controller[9]: at download (/opt/iobroker/node_modules/iobroker.zigbee/lib/statescontroller.js:514:17)
                        2022-05-24 12:53:04.938 - error: host.pi-broker Caught by controller[9]: at StatesController.downloadIcon (/opt/iobroker/node_modules/iobroker.zigbee/lib/statescontroller.js:531:13)
                        2022-05-24 12:53:04.938 - error: host.pi-broker Caught by controller[9]: at StatesController.updateDev (/opt/iobroker/node_modules/iobroker.zigbee/lib/statescontroller.js:496:18)
                        2022-05-24 12:53:04.938 - error: host.pi-broker Caught by controller[9]: at Zigbee.onZigbeeAdapterReady (/opt/iobroker/node_modules/iobroker.zigbee/main.js:370:35)
                        2022-05-24 12:53:04.938 - error: host.pi-broker Caught by controller[10]: This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason:
                        2022-05-24 12:53:04.938 - error: host.pi-broker Caught by controller[11]: ReferenceError: request is not defined
                        2022-05-24 12:53:04.939 - error: host.pi-broker Caught by controller[11]: at download (/opt/iobroker/node_modules/iobroker.zigbee/lib/statescontroller.js:514:17)
                        2022-05-24 12:53:04.939 - error: host.pi-broker Caught by controller[11]: at StatesController.downloadIcon (/opt/iobroker/node_modules/iobroker.zigbee/lib/statescontroller.js:531:13)
                        2022-05-24 12:53:04.939 - error: host.pi-broker Caught by controller[11]: at StatesController.updateDev (/opt/iobroker/node_modules/iobroker.zigbee/lib/statescontroller.js:496:18)
                        2022-05-24 12:53:04.939 - error: host.pi-broker Caught by controller[11]: at Zigbee.onZigbeeAdapterReady (/opt/iobroker/node_modules/iobroker.zigbee/main.js:370:35)
                        2022-05-24 12:53:04.939 - error: host.pi-broker Caught by controller[12]: This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason:
                        2022-05-24 12:53:04.940 - error: host.pi-broker Caught by controller[13]: ReferenceError: request is not defined
                        2022-05-24 12:53:04.940 - error: host.pi-broker Caught by controller[13]: at download (/opt/iobroker/node_modules/iobroker.zigbee/lib/statescontroller.js:514:17)
                        2022-05-24 12:53:04.940 - error: host.pi-broker Caught by controller[13]: at StatesController.downloadIcon (/opt/iobroker/node_modules/iobroker.zigbee/lib/statescontroller.js:531:13)
                        2022-05-24 12:53:04.940 - error: host.pi-broker Caught by controller[13]: at StatesController.updateDev (/opt/iobroker/node_modules/iobroker.zigbee/lib/statescontroller.js:496:18)
                        2022-05-24 12:53:04.940 - error: host.pi-broker Caught by controller[13]: at Zigbee.onZigbeeAdapterReady (/opt/iobroker/node_modules/iobroker.zigbee/main.js:370:35)
                        2022-05-24 12:53:04.941 - error: host.pi-broker Caught by controller[14]: This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason:
                        2022-05-24 12:53:04.941 - error: host.pi-broker Caught by controller[15]: ReferenceError: request is not defined
                        2022-05-24 12:53:04.941 - error: host.pi-broker Caught by controller[15]: at download (/opt/iobroker/node_modules/iobroker.zigbee/lib/statescontroller.js:514:17)
                        2022-05-24 12:53:04.941 - error: host.pi-broker Caught by controller[15]: at StatesController.downloadIcon (/opt/iobroker/node_modules/iobroker.zigbee/lib/statescontroller.js:531:13)
                        2022-05-24 12:53:04.941 - error: host.pi-broker Caught by controller[15]: at StatesController.updateDev (/opt/iobroker/node_modules/iobroker.zigbee/lib/statescontroller.js:496:18)
                        2022-05-24 12:53:04.941 - error: host.pi-broker Caught by controller[15]: at Immediate. (/opt/iobroker/node_modules/iobroker.zigbee/main.js:722:39)
                        2022-05-24 12:53:04.942 - error: host.pi-broker Caught by controller[15]: at processImmediate (internal/timers.js:466:21)
                        2022-05-24 12:53:04.942 - error: host.pi-broker instance system.adapter.zigbee.0 terminated with code 6 (UNCAUGHT_EXCEPTION)
                        

                        Host verhindert nach ein paar versuchen den Neustart.

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

                        @diwoma jo korrigiert.. schau nochmal

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

                        D 1 Antwort Letzte Antwort
                        0
                        • arteckA arteck

                          @diwoma jo korrigiert.. schau nochmal

                          D Offline
                          D Offline
                          diwoma
                          schrieb am zuletzt editiert von
                          #488

                          @arteck
                          Danke für die schnelle Reaktion und dem Fix. Start ist wieder normal:

                          2022-05-24 13:25:59.360 - info: zigbee.0 (25592) starting. Version 1.6.18 (non-npm: ioBroker/ioBroker.zigbee#nobackups) in /opt/iobroker/node_modules/iobroker.zigbee, node: v14.18.2, js-controller: 4.0.23
                          2022-05-24 13:25:59.576 - info: zigbee.0 (25592) delete old Backup files. keep only last 10
                          2022-05-24 13:25:59.580 - info: zigbee.0 (25592) Starting Zigbee npm ...
                          2022-05-24 13:26:00.102 - error: zigbee.0 (25592) Device 0xa4c13879937e5fa8 "TS011F_plug_3" not described in statesMapping.
                          2022-05-24 13:26:00.108 - info: zigbee.0 (25592) Coordinator firmware version: {"type":"ConBee2/RaspBee2","meta":{"transportrev":0,"product":0,"majorrel":38,"minorrel":114,"maintrel":0,"revision":"0x26720700"}}
                          2022-05-24 13:26:00.441 - info: zigbee.0 (25592) Installed Version: ioBroker/ioBroker.zigbee#nobackups
                          2022-05-24 13:26:00.464 - info: zigbee.0 (25592) Unable to disable LED, unsupported function.
                          2022-05-24 13:26:00.468 - info: zigbee.0 (25592) --> transmitPower : normal
                          2022-05-24 13:26:00.640 - info: zigbee.0 (25592) Unable to set transmit power, unsupported function.
                          2022-05-24 13:26:00.652 - info: zigbee.0 (25592) Currently 22 devices are joined:
                          2022-05-24 13:26:00.715 - info: zigbee.0 (25592) 0xcc86ecfffefa8e75 (addr 10983): TS0121_plug - TuYa 10A UK or 16A EU smart plug (Router)
                          2022-05-24 13:26:00.718 - info: zigbee.0 (25592) 0xcc86ecfffefa8c81 (addr 40351): TS0121_plug - TuYa 10A UK or 16A EU smart plug (Router)
                          2022-05-24 13:26:00.720 - info: zigbee.0 (25592) 0xcc86ecfffefa8fbf (addr 46151): TS0121_plug - TuYa 10A UK or 16A EU smart plug (Router)
                          2022-05-24 13:26:00.723 - info: zigbee.0 (25592) 0xb4e3f9fffed0a7d3 (addr 54857): LED1949C5 - IKEA TRADFRI LED bulb E14 470 lumen, wireless dimmable white spectrum/chandelier opal white (Router)
                          2022-05-24 13:26:00.725 - info: zigbee.0 (25592) 0x00158d0007014491 (addr 60981): WXKG11LM - Xiaomi Aqara wireless switch (EndDevice)
                          2022-05-24 13:26:00.727 - info: zigbee.0 (25592) 0x00158d000705d7eb (addr 5306): WSDCGQ11LM - Xiaomi Aqara temperature, humidity and pressure sensor (EndDevice)
                          2022-05-24 13:26:00.730 - info: zigbee.0 (25592) 0x84fd27fffe636592 (addr 16279): ZTS-EU_1gang - Moes Wall touch light switch (1 gang) (EndDevice)
                          2022-05-24 13:26:00.732 - info: zigbee.0 (25592) 0x5c0272fffe1a08fc (addr 22569): ZTS-EU_2gang - Moes Wall touch light switch (2 gang) (EndDevice)
                          2022-05-24 13:26:00.733 - info: zigbee.0 (25592) 0x00158d0007e4df68 (addr 19189): RTCGQ11LM - Xiaomi Aqara human body movement and illuminance sensor (EndDevice)
                          2022-05-24 13:26:00.735 - info: zigbee.0 (25592) 0xa4c1380b13a7ccdc (addr 62650): TS0503B - TuYa Zigbee RGB light (Router)
                          2022-05-24 13:26:00.737 - info: zigbee.0 (25592) 0x00158d0007e0e614 (addr 42568): RTCGQ11LM - Xiaomi Aqara human body movement and illuminance sensor (EndDevice)
                          2022-05-24 13:26:00.738 - info: zigbee.0 (25592) 0x00158d0006d0d895 (addr 48195): WXKG11LM - Xiaomi Aqara wireless switch (EndDevice)
                          2022-05-24 13:26:00.740 - info: zigbee.0 (25592) 0x00158d000704fe0a (addr 10152): WSDCGQ11LM - Xiaomi Aqara temperature, humidity and pressure sensor (EndDevice)
                          2022-05-24 13:26:00.742 - info: zigbee.0 (25592) 0xa4c1389993af0e21 (addr 27159): ZB-RGBCW - Lonsonho Zigbee 3.0 LED-bulb, RGBW LED (Router)
                          2022-05-24 13:26:00.745 - info: zigbee.0 (25592) 0xa4c1387a0ae125eb (addr 13955): TS011F_plug_3 - TuYa Smart plug (with power monitoring by polling) (Router)
                          2022-05-24 13:26:00.746 - info: zigbee.0 (25592) 0x00158d000705e33b (addr 63043): WSDCGQ11LM - Xiaomi Aqara temperature, humidity and pressure sensor (EndDevice)
                          2022-05-24 13:26:00.748 - info: zigbee.0 (25592) 0x00158d0007e0a744 (addr 63795): WSDCGQ11LM - Xiaomi Aqara temperature, humidity and pressure sensor (EndDevice)
                          2022-05-24 13:26:00.749 - info: zigbee.0 (25592) 0x00158d0007e086a3 (addr 7819): WSDCGQ11LM - Xiaomi Aqara temperature, humidity and pressure sensor (EndDevice)
                          2022-05-24 13:26:00.751 - info: zigbee.0 (25592) 0x847127fffec6ac1c (addr 52994): TS0201 - TuYa Temperature & humidity sensor with display (EndDevice)
                          2022-05-24 13:26:00.756 - info: zigbee.0 (25592) 0xa4c13879937e5fa8 (addr 38175): TS011F_plug_3 - TuYa Smart plug (with power monitoring by polling) (Router)
                          2022-05-24 13:26:00.758 - info: zigbee.0 (25592) 0x0c4314fffe98da63 (addr 55684): ZTS-EUR-C - Moes Zigbee + RF curtain switch (Router)
                          2022-05-24 13:26:00.760 - info: zigbee.0 (25592) 0xa4c138fa86b402b3 (addr 42671): TS130F - TuYa Curtain/blind switch (Router)
                          2022-05-24 13:26:00.761 - info: zigbee.0 (25592) Zigbee started
                          2022-05-24 13:27:06.014 - warn: zigbee.0 (25592) DeviceAvailability:Failed to ping 0xa4c138fa86b402b3 TS130F
                          2022-05-24 13:27:06.017 - warn: zigbee.0 (25592) DeviceAvailability:Failed to ping 0x0c4314fffe98da63 TS0601
                          

                          Picture noch nicht gefunden, soll ich jetzt das Device in den Objects löschen und neu starten?
                          Das Bild ist mir prinzipiell nicht so wichtig wie ein funktionierender Adapter und ein erkanntes Device, es geht nur um die Ästhetik

                          -- diwoma

                          ioBroker in LX-Container in Proxmox
                          Zigbee-Coordinator: CC2652P2-TCP FW: 20230507

                          arteckA 1 Antwort Letzte Antwort
                          0
                          • D diwoma

                            @arteck
                            Danke für die schnelle Reaktion und dem Fix. Start ist wieder normal:

                            2022-05-24 13:25:59.360 - info: zigbee.0 (25592) starting. Version 1.6.18 (non-npm: ioBroker/ioBroker.zigbee#nobackups) in /opt/iobroker/node_modules/iobroker.zigbee, node: v14.18.2, js-controller: 4.0.23
                            2022-05-24 13:25:59.576 - info: zigbee.0 (25592) delete old Backup files. keep only last 10
                            2022-05-24 13:25:59.580 - info: zigbee.0 (25592) Starting Zigbee npm ...
                            2022-05-24 13:26:00.102 - error: zigbee.0 (25592) Device 0xa4c13879937e5fa8 "TS011F_plug_3" not described in statesMapping.
                            2022-05-24 13:26:00.108 - info: zigbee.0 (25592) Coordinator firmware version: {"type":"ConBee2/RaspBee2","meta":{"transportrev":0,"product":0,"majorrel":38,"minorrel":114,"maintrel":0,"revision":"0x26720700"}}
                            2022-05-24 13:26:00.441 - info: zigbee.0 (25592) Installed Version: ioBroker/ioBroker.zigbee#nobackups
                            2022-05-24 13:26:00.464 - info: zigbee.0 (25592) Unable to disable LED, unsupported function.
                            2022-05-24 13:26:00.468 - info: zigbee.0 (25592) --> transmitPower : normal
                            2022-05-24 13:26:00.640 - info: zigbee.0 (25592) Unable to set transmit power, unsupported function.
                            2022-05-24 13:26:00.652 - info: zigbee.0 (25592) Currently 22 devices are joined:
                            2022-05-24 13:26:00.715 - info: zigbee.0 (25592) 0xcc86ecfffefa8e75 (addr 10983): TS0121_plug - TuYa 10A UK or 16A EU smart plug (Router)
                            2022-05-24 13:26:00.718 - info: zigbee.0 (25592) 0xcc86ecfffefa8c81 (addr 40351): TS0121_plug - TuYa 10A UK or 16A EU smart plug (Router)
                            2022-05-24 13:26:00.720 - info: zigbee.0 (25592) 0xcc86ecfffefa8fbf (addr 46151): TS0121_plug - TuYa 10A UK or 16A EU smart plug (Router)
                            2022-05-24 13:26:00.723 - info: zigbee.0 (25592) 0xb4e3f9fffed0a7d3 (addr 54857): LED1949C5 - IKEA TRADFRI LED bulb E14 470 lumen, wireless dimmable white spectrum/chandelier opal white (Router)
                            2022-05-24 13:26:00.725 - info: zigbee.0 (25592) 0x00158d0007014491 (addr 60981): WXKG11LM - Xiaomi Aqara wireless switch (EndDevice)
                            2022-05-24 13:26:00.727 - info: zigbee.0 (25592) 0x00158d000705d7eb (addr 5306): WSDCGQ11LM - Xiaomi Aqara temperature, humidity and pressure sensor (EndDevice)
                            2022-05-24 13:26:00.730 - info: zigbee.0 (25592) 0x84fd27fffe636592 (addr 16279): ZTS-EU_1gang - Moes Wall touch light switch (1 gang) (EndDevice)
                            2022-05-24 13:26:00.732 - info: zigbee.0 (25592) 0x5c0272fffe1a08fc (addr 22569): ZTS-EU_2gang - Moes Wall touch light switch (2 gang) (EndDevice)
                            2022-05-24 13:26:00.733 - info: zigbee.0 (25592) 0x00158d0007e4df68 (addr 19189): RTCGQ11LM - Xiaomi Aqara human body movement and illuminance sensor (EndDevice)
                            2022-05-24 13:26:00.735 - info: zigbee.0 (25592) 0xa4c1380b13a7ccdc (addr 62650): TS0503B - TuYa Zigbee RGB light (Router)
                            2022-05-24 13:26:00.737 - info: zigbee.0 (25592) 0x00158d0007e0e614 (addr 42568): RTCGQ11LM - Xiaomi Aqara human body movement and illuminance sensor (EndDevice)
                            2022-05-24 13:26:00.738 - info: zigbee.0 (25592) 0x00158d0006d0d895 (addr 48195): WXKG11LM - Xiaomi Aqara wireless switch (EndDevice)
                            2022-05-24 13:26:00.740 - info: zigbee.0 (25592) 0x00158d000704fe0a (addr 10152): WSDCGQ11LM - Xiaomi Aqara temperature, humidity and pressure sensor (EndDevice)
                            2022-05-24 13:26:00.742 - info: zigbee.0 (25592) 0xa4c1389993af0e21 (addr 27159): ZB-RGBCW - Lonsonho Zigbee 3.0 LED-bulb, RGBW LED (Router)
                            2022-05-24 13:26:00.745 - info: zigbee.0 (25592) 0xa4c1387a0ae125eb (addr 13955): TS011F_plug_3 - TuYa Smart plug (with power monitoring by polling) (Router)
                            2022-05-24 13:26:00.746 - info: zigbee.0 (25592) 0x00158d000705e33b (addr 63043): WSDCGQ11LM - Xiaomi Aqara temperature, humidity and pressure sensor (EndDevice)
                            2022-05-24 13:26:00.748 - info: zigbee.0 (25592) 0x00158d0007e0a744 (addr 63795): WSDCGQ11LM - Xiaomi Aqara temperature, humidity and pressure sensor (EndDevice)
                            2022-05-24 13:26:00.749 - info: zigbee.0 (25592) 0x00158d0007e086a3 (addr 7819): WSDCGQ11LM - Xiaomi Aqara temperature, humidity and pressure sensor (EndDevice)
                            2022-05-24 13:26:00.751 - info: zigbee.0 (25592) 0x847127fffec6ac1c (addr 52994): TS0201 - TuYa Temperature & humidity sensor with display (EndDevice)
                            2022-05-24 13:26:00.756 - info: zigbee.0 (25592) 0xa4c13879937e5fa8 (addr 38175): TS011F_plug_3 - TuYa Smart plug (with power monitoring by polling) (Router)
                            2022-05-24 13:26:00.758 - info: zigbee.0 (25592) 0x0c4314fffe98da63 (addr 55684): ZTS-EUR-C - Moes Zigbee + RF curtain switch (Router)
                            2022-05-24 13:26:00.760 - info: zigbee.0 (25592) 0xa4c138fa86b402b3 (addr 42671): TS130F - TuYa Curtain/blind switch (Router)
                            2022-05-24 13:26:00.761 - info: zigbee.0 (25592) Zigbee started
                            2022-05-24 13:27:06.014 - warn: zigbee.0 (25592) DeviceAvailability:Failed to ping 0xa4c138fa86b402b3 TS130F
                            2022-05-24 13:27:06.017 - warn: zigbee.0 (25592) DeviceAvailability:Failed to ping 0x0c4314fffe98da63 TS0601
                            

                            Picture noch nicht gefunden, soll ich jetzt das Device in den Objects löschen und neu starten?
                            Das Bild ist mir prinzipiell nicht so wichtig wie ein funktionierender Adapter und ein erkanntes Device, es geht nur um die Ästhetik

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

                            @diwoma sagte in ZigBee neue Version 1.6.x:

                            Picture noch nicht gefunden, soll ich jetzt das Device in den Objects löschen und neu starten?

                            jo dann adapter neu starten und dann nochmal leider ein upload
                            f045fd0f-f756-4d0c-be7b-43ec6dffad15-grafik.png

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

                            D 1 Antwort Letzte Antwort
                            0
                            • arteckA arteck

                              @diwoma sagte in ZigBee neue Version 1.6.x:

                              Picture noch nicht gefunden, soll ich jetzt das Device in den Objects löschen und neu starten?

                              jo dann adapter neu starten und dann nochmal leider ein upload
                              f045fd0f-f756-4d0c-be7b-43ec6dffad15-grafik.png

                              D Offline
                              D Offline
                              diwoma
                              schrieb am zuletzt editiert von
                              #490

                              @arteck
                              mehrfach durchgeführt, kein Bild.

                              Ist es nicht möglich, daß für dieses Device einfach kein Bild hinterlegt ist? Wenn es erst in den Converter eingetragen wurde?
                              Wo wird denn eigentlich das Bild dafür hinterlegt?

                              -- diwoma

                              ioBroker in LX-Container in Proxmox
                              Zigbee-Coordinator: CC2652P2-TCP FW: 20230507

                              arteckA 1 Antwort Letzte Antwort
                              0
                              • D diwoma

                                @arteck
                                mehrfach durchgeführt, kein Bild.

                                Ist es nicht möglich, daß für dieses Device einfach kein Bild hinterlegt ist? Wenn es erst in den Converter eingetragen wurde?
                                Wo wird denn eigentlich das Bild dafür hinterlegt?

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

                                @diwoma die bilder kommen entweder von uns.. oder neu in dem branch aus dem zigbee2mqtt
                                https://www.zigbee2mqtt.io/supported-devices/ Projekt..
                                kannst ja mal schauen ob es da vorhanden ist..da spielt der converter keine rolle

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

                                D 1 Antwort Letzte Antwort
                                0
                                • arteckA arteck

                                  @diwoma die bilder kommen entweder von uns.. oder neu in dem branch aus dem zigbee2mqtt
                                  https://www.zigbee2mqtt.io/supported-devices/ Projekt..
                                  kannst ja mal schauen ob es da vorhanden ist..da spielt der converter keine rolle

                                  D Offline
                                  D Offline
                                  diwoma
                                  schrieb am zuletzt editiert von
                                  #492

                                  @arteck said in ZigBee neue Version 1.6.x:

                                  die bilder kommen entweder von uns.. oder neu in dem branch aus dem zigbee2mqtt
                                  https://www.zigbee2mqtt.io/supported-devices/ Projekt..
                                  kannst ja mal schauen ob es da vorhanden ist..da spielt der converter keine rolle

                                  Habe ich nachgeschaut, dort ist er nicht vorhanden. Soll ich auf GIT einen Issue eröffnen, das das Device eingetragen werden soll?

                                  -- diwoma

                                  ioBroker in LX-Container in Proxmox
                                  Zigbee-Coordinator: CC2652P2-TCP FW: 20230507

                                  arteckA 1 Antwort Letzte Antwort
                                  0
                                  • D diwoma

                                    @arteck said in ZigBee neue Version 1.6.x:

                                    die bilder kommen entweder von uns.. oder neu in dem branch aus dem zigbee2mqtt
                                    https://www.zigbee2mqtt.io/supported-devices/ Projekt..
                                    kannst ja mal schauen ob es da vorhanden ist..da spielt der converter keine rolle

                                    Habe ich nachgeschaut, dort ist er nicht vorhanden. Soll ich auf GIT einen Issue eröffnen, das das Device eingetragen werden soll?

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

                                    @diwoma wenn der da nicht vorhaden ist.. dann hilft dir der issue bei uns nicht. da es komplett unbekannt ist

                                    funktioniert das Ding den überhaupt..

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

                                    D 1 Antwort Letzte Antwort
                                    0
                                    • arteckA arteck

                                      @diwoma wenn der da nicht vorhaden ist.. dann hilft dir der issue bei uns nicht. da es komplett unbekannt ist

                                      funktioniert das Ding den überhaupt..

                                      D Offline
                                      D Offline
                                      diwoma
                                      schrieb am zuletzt editiert von
                                      #494

                                      @arteck said in ZigBee neue Version 1.6.x:

                                      wenn der da nicht vorhaden ist.. dann hilft dir der issue bei uns nicht. da es komplett unbekannt ist
                                      funktioniert das Ding den überhaupt..

                                      Ja, mit dem letzten Update habe ich auch die letzten Updates vom Herdsman bekommen, wo das Device eingetragen ist. Ich habe zwar noch keinen Rolladen-Motor angeschlossen, aber die Daten für Öffnen/Schliessen vom Device werden übermittelt, bzw. können von ioBroker-Zigbee-Device angesteuert werden

                                      -- diwoma

                                      ioBroker in LX-Container in Proxmox
                                      Zigbee-Coordinator: CC2652P2-TCP FW: 20230507

                                      1 Antwort Letzte Antwort
                                      0
                                      • C Offline
                                        C Offline
                                        Cino
                                        schrieb am zuletzt editiert von
                                        #495

                                        Ich will alle Geräte löschen. Habe den Zigbee Adapter komplett deinstalliert und dann über github wieder installiert.
                                        Einige Geräte sind sofort wieder aufgetaucht.

                                        Wie kann ich also alles löschen? Ich will alles neu anlernen.

                                        IOB@RPI4
                                        Shelly, Zigbee, ebus

                                        AsgothianA arteckA 2 Antworten Letzte Antwort
                                        0
                                        • C Cino

                                          Ich will alle Geräte löschen. Habe den Zigbee Adapter komplett deinstalliert und dann über github wieder installiert.
                                          Einige Geräte sind sofort wieder aufgetaucht.

                                          Wie kann ich also alles löschen? Ich will alles neu anlernen.

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

                                          @cino der einfachste weg ist alles über den Adapter löschen - im Zweifelsfall mit dem Haken bei “löschen erzwingen”

                                          Dann adapter deinstallieren, Verzeichnis /opt/iobroker/iobroker-data/zigbee_0 löschen.

                                          A.

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

                                          1 Antwort Letzte Antwort
                                          0
                                          Antworten
                                          • In einem neuen Thema antworten
                                          Anmelden zum Antworten
                                          • Älteste zuerst
                                          • Neuste zuerst
                                          • Meiste Stimmen


                                          Support us

                                          ioBroker
                                          Community Adapters
                                          Donate

                                          824

                                          Online

                                          32.4k

                                          Benutzer

                                          81.5k

                                          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