Navigation

    Logo
    • Register
    • Login
    • Search
    • Recent
    • Tags
    • Unread
    • Categories
    • Unreplied
    • Popular
    • GitHub
    • Docu
    • Hilfe
    1. Home
    2. Deutsch
    3. Tester
    4. Tester wanted - Zigbee Adapter 3.1

    NEWS

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

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

    • Wir empfehlen: Node.js 22.x

    Tester wanted - Zigbee Adapter 3.1

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

      @dimaiv sagte in Tester wanted - Zigbee Adapter 3.1:

      P.S.: ich glaube, die weiteren Daten bei diesen Steckdosen wurden immer gepoolt, und jetzt passiert es nicht.

      Sind die Meldungen nach einem Device_query, oder kommen die normal so ?

      @dimaiv sagte in Tester wanted - Zigbee Adapter 3.1:

      Was mir noch aufgefallen:
      Mit 3.1.2 kann ich über:
      sendToZigbee { "id": "zigbee.0.842e14fffedb8ae5", "ep": "1", "cid": "haElectricalMeasurement", "cmd": "read", "cmdType": "foundation", "zclData": { "activePower": {} } }
      Die weiteren Daten abrufen.
      Mit 3.1.3 von jetzt funktioniert es nicht.

      Danke für den Hinweis - ich hab im Hintergrund einiges Optimiert.

      A.

      D 1 Reply Last reply Reply Quote 0
      • D
        dimaiv @Asgothian last edited by

        @asgothian sagte in Tester wanted - Zigbee Adapter 3.1:

        Sind die Meldungen nach einem Device_query, oder kommen die normal so ?

        A.

        Die Meldungen sind nach einem Device_query, aber auch normal kommen nur die.

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

          @dimaiv Ok, danke. Da scheint ein Konverter geändert - da muss ich im Detail graben, und Dir eine extra version machen. Wird aber etwas dauern.

          A.

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

            @asgothian Zumindest der Developer Tab sollte jetzt wieder funktionieren.

            Kannst du versuchen was passiert wenn du damit versuchst die Daten abzurufen ? Ob dann eine Meldung rein kommt ?

            Interessant ist was genau an Antwort auf den Read Request rein kommt, wenn überhaupt etwas.

            A.

            D 1 Reply Last reply Reply Quote 0
            • D
              dimaiv @Asgothian last edited by dimaiv

              @asgothian sagte in Tester wanted - Zigbee Adapter 3.1:

              @asgothian Zumindest der Developer Tab sollte jetzt wieder funktionieren.

              Kannst du versuchen was passiert wenn du damit versuchst die Daten abzurufen ? Ob dann eine Meldung rein kommt ?

              Interessant ist was genau an Antwort auf den Read Request rein kommt, wenn überhaupt etwas.

              A.

              Über Entwikler Tab funktioniert jetzt:

              
              I01: Zigbee Event of Type readResponse from device 0x60a423fffe61dd4a, incoming event: {"type":"readResponse","data":{"activePower":0},"linkquality":51,"groupID":0,"cluster":"haElectricalMeasurement","meta":{"rawData":{"type":"Buffer","data":[24,8,1,11,5,0,41,0,0]},"zclTransactionSequenceNumber":8,"frameControl":{"frameType":0,"manufacturerSpecific":false,"direction":1,"disableDefaultResponse":true,"reservedBits":0}},"endpoint_id":1}
              I02: 1 converter available for 'TS0121_plug' '60a423fffe61dd4a' with cluster 'haElectricalMeasurement' and type 'readResponse'
              I03: message received '{"linkquality":51}' from device 60a423fffe61dd4a type 'TS0121_plug'
              I04: value generated '51' from device 60a423fffe61dd4a for 'Link quality'
              I02.1a: converter 1 : Cluster haElectricalMeasurement
              I02.0b: data: {"activePower":0} options: {} meta:{"deviceIEEE":"0x60a423fffe61dd4a","logger":"StatesController","state":{"state":""}} result:{"power":0}
              I02.1c: candidates: [{"power":0}] => payload {"power":0}
              I03-1: message received '{"power":0}' from device 60a423fffe61dd4a type 'TS0121_plug'
              I04-1: value generated '0' from device 60a423fffe61dd4a for 'Load power'
              
              

              Uber die Scripte stürzt aber der Adapter ab mit folgender Meldung:

              2025-09-21 21:40:50.830 - info: javascript.0 (942) script.js.Plug_abfragen: start JavaScript (Blockly)
              2025-09-21 21:40:50.842 - info: javascript.0 (942) script.js.Plug_abfragen: registered 0 subscriptions, 0 schedules, 0 messages, 0 logs and 0 file subscriptions
              2025-09-21 21:40:55.849 - error: zigbee.0 (282446) 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().
              2025-09-21 21:40:55.851 - error: zigbee.0 (282446) unhandled promise rejection: Cannot read properties of undefined (reading 'replace')
              2025-09-21 21:40:56.167 - error: zigbee.0 (282446) TypeError: Cannot read properties of undefined (reading 'replace')
              at Developer.sendToZigbee (/opt/iobroker/node_modules/iobroker.zigbee/lib/developer.js:90:45)
              at Developer.onMessage (/opt/iobroker/node_modules/iobroker.zigbee/lib/developer.js:49:26)
              at Zigbee.emit (node:events:536:35)
              at Zigbee.emit (node:domain:489:12)
              at change (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/src/lib/adapter/adapter.ts:11040:34)
              at Immediate. (file:///opt/iobroker/node_modules/@iobroker/db-states-redis/src/lib/states/statesInRedisClient.ts:365:37)
              at processImmediate (node:internal/timers:483:21)
              2025-09-21 21:40:56.168 - error: zigbee.0 (282446) Cannot read properties of undefined (reading 'replace')
              2025-09-21 21:40:56.193 - info: zigbee.0 (282446) Halting zigbee adapter. Restart delay is at least 30 seconds.
              2025-09-21 21:40:56.193 - info: zigbee.0 (282446) cleaning everything up...
              2025-09-21 21:40:56.196 - info: zigbee.0 (282446) Saved local configuration data
              2025-09-21 21:40:56.227 - warn: zigbee.0 (282446) ELEVATED:I03 (2e22) message received '{"available":false}' from device 60a423fffe61dd4a type 'TS0121_plug'
              2025-09-21 21:40:56.228 - warn: zigbee.0 (282446) ELEVATED:I04 (2e22) value generated 'false' from device 60a423fffe61dd4a for 'Available'
              2025-09-21 21:40:56.229 - warn: zigbee.0 (282446) ELEVATED:I03 (2e22) message received '{"linkquality":0}' from device 60a423fffe61dd4a type 'TS0121_plug'
              2025-09-21 21:40:56.230 - warn: zigbee.0 (282446) ELEVATED:I04 (2e22) value generated '0' from device 60a423fffe61dd4a for 'Link quality'
              2025-09-21 21:40:56.586 - info: zigbee.0 (282446) Closing Zigbee network, 0 seconds remaining
              2025-09-21 21:40:57.195 - warn: zigbee.0 (282446) Terminated (UNCAUGHT_EXCEPTION): Without reason
              2025-09-21 21:40:57.783 - error: host.GartenIoB Caught by controller[1]: This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason:
              2025-09-21 21:40:57.784 - error: host.GartenIoB Caught by controller[2]: TypeError: Cannot read properties of undefined (reading 'replace')
              2025-09-21 21:40:57.784 - error: host.GartenIoB Caught by controller[2]: at Developer.sendToZigbee (/opt/iobroker/node_modules/iobroker.zigbee/lib/developer.js:90:45)
              2025-09-21 21:40:57.784 - error: host.GartenIoB Caught by controller[2]: at Developer.onMessage (/opt/iobroker/node_modules/iobroker.zigbee/lib/developer.js:49:26)
              2025-09-21 21:40:57.784 - error: host.GartenIoB Caught by controller[2]: at Zigbee.emit (node:events:536:35)
              2025-09-21 21:40:57.785 - error: host.GartenIoB Caught by controller[2]: at Zigbee.emit (node:domain:489:12)
              2025-09-21 21:40:57.785 - error: host.GartenIoB Caught by controller[2]: at change (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/src/lib/adapter/adapter.ts:11040:34)
              2025-09-21 21:40:57.785 - error: host.GartenIoB Caught by controller[2]: at Immediate. (file:///opt/iobroker/node_modules/@iobroker/db-states-redis/src/lib/states/statesInRedisClient.ts:365:37)
              2025-09-21 21:40:57.785 - error: host.GartenIoB Caught by controller[2]: at processImmediate (node:internal/timers:483:21)
              2025-09-21 21:40:57.785 - error: host.GartenIoB instance system.adapter.zigbee.0 terminated with code 6 (UNCAUGHT_EXCEPTION)
              2025-09-21 21:40:57.785 - info: host.GartenIoB Restart adapter system.adapter.zigbee.0 because enabled
              2025-09-21 21:41:01.905 - info: javascript.0 (942) script.js.Plug_abfragen: Stopping script
              
              

              Blockly=>JS:

              var Intervall;
              
              // Beschreibe diese Funktion …
              async function Power() {
                sendTo('zigbee.0', 'sendToZigbee', {
                  'parameter': { "id": "zigbee.0.60a423fffe61dd4a", "ep": "1", "cid": "haElectricalMeasurement", "cmd": "read", "cmdType": "foundation", "zclData": { "activePower": {} } },
                });
              }
              
              
              Intervall = setInterval(async () => {
                await Power();
              }, 5000);
              

              Mit 3.1.2 funktionieren beide Variante.

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

                @dimaiv Danke fürs Testen - ich schau mir das morgen an

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

                  @dimaiv sagte in Tester wanted - Zigbee Adapter 3.1:

                  sendTo('zigbee.0', 'sendToZigbee', { 'parameter': { "id": "zigbee.0.60a423fffe61dd4a", "ep": "1", "cid": "haElectricalMeasurement", "cmd": "read", "cmdType": "foundation", "zclData": { "activePower": {} } }, });

                  Diese Methode die Funktion aufzurufen ist auf Dauer instabil - sie basiert darauf das interne Funktionen nicht geändert werden. Bitte teste, ob mit einer der 3.X Versionen der folgende Payload in send_payload das gewünschte Ergebnis bringt. Dieses ist als Ersatz für das 'sendToZigbee' implementiert worden

                  {
                    "read": {
                      "cluster": "haElectricalMeasurement",
                      "attributes": [
                        "activePower"
                      ]
                    }
                  }
                  

                  Nachtrag:

                  bist du sicher das dieser Code in 3.0.5 wirklich geht ?

                  var Intervall;
                   
                  // Beschreibe diese Funktion …
                   async function Power() {
                     sendTo('zigbee.0', 'sendToZigbee', {
                       'parameter': { "id": "zigbee.0.60a423fffe61dd4a", "ep": "1", "cid": "haElectricalMeasurement", "cmd": "read", "cmdType": "foundation", "zclData": { "activePower": {} } },
                     });
                   }
                    
                    
                   Intervall = setInterval(async () => {
                     await Power();
                   }, 5000);
                  

                  Hintergrund - es gab eine Anpassung am Blockly SendTo Block. Wo der vorher den Code

                  sendTo('zigbee.0', 'sendToZigbee', {"id": "zigbee.0.00be44fffeab0b87", "ep": "1", "cid": "haElectricalMeasurement", "cmd": "read", "cmdType": "foundation", "zclData": { "activePower": {} } },
                  );
                  

                  als Standard erzeugt hat, macht er jetzt

                   sendTo('zigbee.0', 'sendToZigbee', {
                       'parameter': { "id": "zigbee.0.60a423fffe61dd4a", "ep": "1", "cid": "haElectricalMeasurement", "cmd": "read", "cmdType": "foundation", "zclData": { "activePower": {} } },
                     });
                  

                  mit dem Standard Block. Um die alte Version zurück zu bekommen muss man den Namen der Variable im Block löschen.

                  Blockly Skript zum importieren als Beispiel:

                  <xml xmlns="https://developers.google.com/blockly/xml">
                    <block type="sendto_custom" id="+%Nw$~nnCWC@TlZQZ~]8" x="212" y="138">
                      <mutation xmlns="http://www.w3.org/1999/xhtml" items="parameter"></mutation>
                      <field name="INSTANCE">zigbee.0</field>
                      <field name="COMMAND">sendToZigbee</field>
                      <field name="LOG"></field>
                      <field name="WITH_STATEMENT">FALSE</field>
                      <value name="ARG0">
                        <shadow type="text" id="](`*pMFJEuOLTeBJ5hZF">
                          <field name="TEXT">{"id": "zigbee.0.00be44fffeab0b87", "ep": "1", "cid": "haElectricalMeasurement", "cmd": "read", "cmdType": "foundation", "zclData": { "activePower": {} } }</field>
                        </shadow>
                      </value>
                      <next>
                        <block type="sendto_custom" id="1o#t?S/@4Z_1R7G/YxW3">
                          <mutation xmlns="http://www.w3.org/1999/xhtml" items=""></mutation>
                          <field name="INSTANCE">zigbee.0</field>
                          <field name="COMMAND">sendToZigbee</field>
                          <field name="LOG"></field>
                          <field name="WITH_STATEMENT">FALSE</field>
                          <value name="ARG0">
                            <shadow type="text" id="O`S)U?JPvg=x#CYYZI*r">
                              <field name="TEXT">{"id": "zigbee.0.00be44fffeab0b87", "ep": "1", "cid": "haElectricalMeasurement", "cmd": "read", "cmdType": "foundation", "zclData": { "activePower": {} } }</field>
                            </shadow>
                          </value>
                        </block>
                      </next>
                    </block>
                  </xml>
                  
                  D Asgothian 2 Replies Last reply Reply Quote 0
                  • D
                    dimaiv @Asgothian last edited by dimaiv

                    @asgothian
                    Deine Blockly ist absolut identisch mit dem was ich oben gepostet habe, nur bei mir ist SendTo in eine funktion gepackt und anderes exportiert.
                    Aber es macht nix, beide Varianten bringen 3.1.3 zum Absturz, und mit 3.1.2 aus latest funktionieren einwandfrei.
                    Aber, das ist jetz auch egal, weil, Variante über send_payload funktioniert auch bei 3.1.3 , und ist einfacher einzurichten bei mehreren Steckdosen.

                    Hoffentlich, muss man es ab jetzt, nich dauerhaft benutzen und überall einrichten , und es wird, wie vorher, von alleine über Converter (Pooling) funktionieren .

                    P.S.: Problem mit send_payload bei SWV bin ich auch betroffen, aber ich verfolge es auf Git. Falls hier was zum testen gibt, oder du das Ventil zum debuggen haben möchtest/muss, sag Bescheid.

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

                      Es gibt eine neue Version auf Github: 3.1.2-alpha-4.

                      Folgende Anpassungen sollten da drin sein:

                      • Fix für 'onEvent' Polling: Sollte diesen Issue (GitHub link) schliessen: (sowie die Probleme vor @dimaiv)
                      • Fix für 'no configure on pairing' - neu dem Netzwerk hinzugefügte Devices sollten automatisch Konfiguriert werden.
                      • Netzwerk am Router öffnen - da der ZH diese Funktion wieder bietet, ist sie (hoffentlich) auch wieder verfügbar. Ich kann das nur bedingt testen.
                        Screenshot 2025-09-24 at 21.40.02.png
                      • Icon download button in der Konfiguration des Adapters. Notwendig wenn ein Upload gemacht wird ohne den Adapter neu zu starten.
                        Screenshot 2025-09-24 at 21.47.22.png
                      • Neue Optionen (grün: verifiziert, Orange: Bedarf Tests die ich mangels Gerät aktuell nicht durchführen kann)
                        Screenshot 2025-09-24 at 21.47.56.png
                        -- Active availability check. Wie in diesem Issue (GitHub link) zu sehen scheint der ZHC Ping nicht immer gut zu laufen. Deswegen gibt es jetzt im Adapter wählbare alternative Methoden (incl. 'off')
                        -- Time between activity Checks: Dieses ist eine Maximalzeit zwischen Ping Versuchen. Es gibt interne Verrechnungen abhängig davon wie viele Devices im Netz sind, wie oft ein Device nicht erreicht werden konnte und diese Zahl. Je höher die Zahl desto seltener wird jedes Device abgefragt.
                        -- List devices at Start: Aktiviert / Deaktivert die lange Liste an aktiven Geräten und Gruppen bei Adapter-Start.
                        -- try to read all states at adapter start: Dient dazu beim Start des Adapters zu versuchen den Status im ioBroker mit dem der Geräte zu synchronisieren. Kann bei grossen Netzen Problematisch werden. Dazu gehört: delay in seconds - die Verzögerung zwischen Adapter-Start und dem Start des Abfrage aller Geräte.
                        -- Read States at device announce: Wenn ein Gerät sich am Netzwerk 'zurück' meldet (xxx has announced itself) wird ein Device-Query für das Device ausgelöst um dessen Status zu ermitteln.
                        -- use channel for complex exposes: Dies ist eine zukünftige Entwicklung. Es gibt bei bestimmten Geräten Datenpuntke die eigentlich nur gemeinsam gesetzt werden dürfen. Ein Beispiel dafür sind Farben mit r, g, b - die schon als Channels angeboten werden. Dabei passiert folgendes:
                        -- wird einer der States im Channel verändert so wird ein timeout gestartet. Bei Ablauf des Timeout werden alle eingetragenen Werte genommen und in einem Payload an das Gerät gesandt. Dabei ist die Zeit für den Timeout abhängig davon ob die Änderung 'manuell' im Admin passiert oder nicht. Im Admin liegt der Timeout zwischen 2.5 und 5 sekunden. Ausserhalb des Admin sind es 100 - 250 ms. Durch weitere Tests können sich diese Zahlen noch ändern.
                      • Veränderungen an der Netzwerk-Karte: Der vorherige Regenerate button (blau) wurde durch einen grünen Reload button ersetzt. Dieser lädt eine bereits generierte Map vom Adapter anstatt diese neu vom Netzwerk anzufragen. Um eine Map vollständig neu aufzubauen gibt es in den Map-Einstellungen einen eigenen Button:
                        Screenshot 2025-09-24 at 22.02.38.png
                      • via den 'zigbee subsystem error' Anzeiger kann das Zigbee-Subsystem nun direkt gestartet werden, ohne auf die Hardware-seite zu gehen. Dieser button ist auch im Tab sichtbar wenn das Zigbee-System nicht läuft aber der Adapter schon. Screenshot 2025-09-24 at 22.04.59.png
                      • Die Koordinator-Karte zeigt jetzt nicht nur an ob der Koordinator ansprechbar ist, sondern auch ob der Haken zum automatischen Start des Zigbee Subsystems gesetzt ist:
                        --Haken gesetzt: Screenshot 2025-09-24 at 22.10.17.png
                        -- Haken nicht gesetzt: Screenshot 2025-09-24 at 22.11.08.png
                      • developer modus gefixed - sollte sauber gehen.
                      • Gruppen aus der Auswahl im Developer Modus entfernt, da die Funktionalität so nicht nutzbar ist.
                      1 Reply Last reply Reply Quote 0
                      • Asgothian
                        Asgothian Developer @dimaiv last edited by

                        @dimaiv sagte in Tester wanted - Zigbee Adapter 3.1:

                        @asgothian
                        Deine Blockly ist absolut identisch mit dem was ich oben gepostet habe, nur bei mir ist SendTo in eine funktion gepackt und anderes exportiert.
                        Aber es macht nix, beide Varianten bringen 3.1.3 zum Absturz, und mit 3.1.2 aus latest funktionieren einwandfrei.
                        Aber, das ist jetz auch egal, weil, Variante über send_payload funktioniert auch bei 3.1.3 , und ist einfacher einzurichten bei mehreren Steckdosen.

                        Hoffentlich, muss man es ab jetzt, nich dauerhaft benutzen und überall einrichten , und es wird, wie vorher, von alleine über Converter (Pooling) funktionieren .

                        Bist du sicher das die den gleichen Code erzeugen ? Bei mir tun sie das nicht, und der von mir gepostetete code

                        sendTo('zigbee.0', 'sendToZigbee', {"id": "zigbee.0.00be44fffeab0b87", "ep": "1", "cid": "haElectricalMeasurement", "cmd": "read", "cmdType": "foundation", "zclData": { "activePower": {} } },
                        );
                        

                        sollte auch mit der aktuellen 3.1.3 laufen.

                        Aber:

                        Es gibt inzwischen eine 3.1.3-alpha-4, damit sollte hoffentlich das polling wieder laufen.

                        A.

                        D 1 Reply Last reply Reply Quote 0
                        • D
                          dimaiv @Asgothian last edited by dimaiv

                          @asgothian
                          Adapter 3.1.3 alpha 4 stürzt sofort ab.

                          2025-09-24 22:25:18.298 - info: zigbee.0 (296477) 20 devices are part of the network
                          2025-09-24 22:25:18.300 - info: zigbee.0 (296477) Zigbee started
                          2025-09-24 22:25:18.333 - warn: zigbee.0 (296477) DeviceEvent:calling onEvent for start on 0x60a423fffe61dd4a
                          2025-09-24 22:25:18.349 - warn: zigbee.0 (296477) DeviceEvent:calling onEvent for start on 0x28dba7fffe6df66f
                          2025-09-24 22:25:18.355 - warn: zigbee.0 (296477) DeviceEvent:calling onEvent for start on 0x28dba7fffe6df516
                          2025-09-24 22:25:18.357 - warn: zigbee.0 (296477) DeviceEvent:calling onEvent for start on 0x28dba7fffe6df594
                          2025-09-24 22:25:18.359 - warn: zigbee.0 (296477) DeviceEvent:calling onEvent for start on 0x881a14fffeea1db2
                          2025-09-24 22:25:18.361 - warn: zigbee.0 (296477) DeviceEvent:calling onEvent for start on 0x28dba7fffe6df5f6
                          2025-09-24 22:25:18.362 - warn: zigbee.0 (296477) DeviceEvent:calling onEvent for start on 0xa4c13801838effff
                          2025-09-24 22:25:18.365 - error: zigbee.0 (296477) 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().
                          2025-09-24 22:25:18.365 - error: zigbee.0 (296477) unhandled promise rejection: Cannot read properties of undefined (reading 'measurement_poll_interval')
                          2025-09-24 22:25:18.537 - error: zigbee.0 (296477) TypeError: Cannot read properties of undefined (reading 'measurement_poll_interval')
                          at onEvent (/opt/iobroker/node_modules/zigbee-herdsman-converters/src/lib/modernExtend.ts:678:58)
                          at Object.onEvent (/opt/iobroker/node_modules/zigbee-herdsman-converters/src/index.ts:376:27)
                          at DeviceEvent.callOnEvent (/opt/iobroker/node_modules/iobroker.zigbee/lib/zbDeviceEvent.js:69:26)
                          at processTicksAndRejections (node:internal/process/task_queues:95:5)
                          at DeviceEvent.onZigbeeStarted (/opt/iobroker/node_modules/iobroker.zigbee/lib/zbDeviceEvent.js:13:13)
                          at async Promise.all (index 2)
                          2025-09-24 22:25:18.538 - error: zigbee.0 (296477) Cannot read properties of undefined (reading 'measurement_poll_interval')
                          2025-09-24 22:25:18.592 - info: zigbee.0 (296477) Halting zigbee adapter. Restart delay is at least 30 seconds.
                          2025-09-24 22:25:18.592 - info: zigbee.0 (296477) cleaning everything up
                          2025-09-24 22:25:18.596 - info: zigbee.0 (296477) Saved local configuration data
                          2025-09-24 22:25:18.598 - info: zigbee.0 (296477) cleanup successful
                          2025-09-24 22:25:18.599 - info: zigbee.0 (296477) terminating
                          2025-09-24 22:25:18.602 - warn: zigbee.0 (296477) Terminated (UNCAUGHT_EXCEPTION): Without reason
                          2025-09-24 22:25:18.610 - info: zigbee.0 (296477) zigbecontroller stopped successfully - ZH was not running
                          2025-09-24 22:25:18.797 - info: zigbee.0 (296477) debug devices set to []
                          2025-09-24 22:25:19.207 - warn: zigbee.0 (296477) get state error: Connection is closed.
                          2025-09-24 22:25:19.208 - warn: zigbee.0 (296477) get state error: Connection is closed.
                          2025-09-24 22:25:19.208 - warn: zigbee.0 (296477) get state error: Connection is closed.
                          2025-09-24 22:25:19.209 - warn: zigbee.0 (296477) get state error: Connection is closed.
                          2025-09-24 22:25:19.210 - warn: zigbee.0 (296477) get state error: Connection is closed.
                          2025-09-24 22:25:19.211 - warn: zigbee.0 (296477) get state error: Connection is closed.
                          2025-09-24 22:25:19.211 - warn: zigbee.0 (296477) get state error: Connection is closed.
                          2025-09-24 22:25:19.212 - warn: zigbee.0 (296477) get state error: Connection is closed.
                          2025-09-24 22:25:19.213 - warn: zigbee.0 (296477) get state error: Connection is closed.
                          2025-09-24 22:25:19.214 - warn: zigbee.0 (296477) get state error: Connection is closed.
                          2025-09-24 22:25:19.214 - warn: zigbee.0 (296477) get state error: Connection is closed.
                          2025-09-24 22:25:19.215 - warn: zigbee.0 (296477) get state error: Connection is closed.
                          2025-09-24 22:25:19.216 - warn: zigbee.0 (296477) get state error: Connection is closed.
                          2025-09-24 22:25:19.216 - warn: zigbee.0 (296477) get state error: Connection is closed.
                          2025-09-24 22:25:19.217 - warn: zigbee.0 (296477) get state error: Connection is closed.
                          2025-09-24 22:25:19.217 - warn: zigbee.0 (296477) get state error: Connection is closed.
                          2025-09-24 22:25:19.218 - warn: zigbee.0 (296477) get state error: Connection is closed.
                          2025-09-24 22:25:19.218 - warn: zigbee.0 (296477) get state error: Connection is closed.
                          2025-09-24 22:25:19.219 - warn: zigbee.0 (296477) get state error: Connection is closed.
                          2025-09-24 22:25:19.219 - warn: zigbee.0 (296477) get state error: Connection is closed.
                          2025-09-24 22:25:19.220 - warn: zigbee.0 (296477) get state error: Connection is closed.
                          2025-09-24 22:25:19.220 - warn: zigbee.0 (296477) get state error: Connection is closed.
                          2025-09-24 22:25:19.220 - warn: zigbee.0 (296477) get state error: Connection is closed.
                          2025-09-24 22:25:19.221 - warn: zigbee.0 (296477) get state error: Connection is closed.
                          2025-09-24 22:25:19.221 - warn: zigbee.0 (296477) get state error: Connection is closed.
                          2025-09-24 22:25:19.222 - warn: zigbee.0 (296477) get state error: Connection is closed.
                          2025-09-24 22:25:19.222 - warn: zigbee.0 (296477) get state error: Connection is closed.
                          2025-09-24 22:25:19.223 - warn: zigbee.0 (296477) get state error: Connection is closed.
                          2025-09-24 22:25:19.223 - warn: zigbee.0 (296477) get state error: Connection is closed.
                          2025-09-24 22:25:19.224 - warn: zigbee.0 (296477) get state error: Connection is closed.
                          2025-09-24 22:25:19.224 - warn: zigbee.0 (296477) get state error: Connection is closed.
                          2025-09-24 22:25:19.225 - warn: zigbee.0 (296477) get state error: Connection is closed.
                          2025-09-24 22:25:19.225 - warn: zigbee.0 (296477) get state error: Connection is closed.
                          2025-09-24 22:25:19.226 - warn: zigbee.0 (296477) get state error: Connection is closed.
                          2025-09-24 22:25:19.227 - warn: zigbee.0 (296477) get state error: Connection is closed.
                          2025-09-24 22:25:19.228 - warn: zigbee.0 (296477) get state error: Connection is closed.
                          2025-09-24 22:25:19.229 - warn: zigbee.0 (296477) get state error: Connection is closed.
                          2025-09-24 22:25:19.230 - warn: zigbee.0 (296477) get state error: Connection is closed.
                          2025-09-24 22:25:19.231 - warn: zigbee.0 (296477) get state error: Connection is closed.
                          2025-09-24 22:25:19.232 - warn: zigbee.0 (296477) get state error: Connection is closed.
                          2025-09-24 22:25:19.232 - warn: zigbee.0 (296477) get state error: Connection is closed.
                          2025-09-24 22:25:19.233 - warn: zigbee.0 (296477) get state error: Connection is closed.
                          2025-09-24 22:25:19.234 - warn: zigbee.0 (296477) get state error: Connection is closed.
                          2025-09-24 22:25:19.234 - warn: zigbee.0 (296477) get state error: Connection is closed.
                          2025-09-24 22:25:19.235 - warn: zigbee.0 (296477) get state error: Connection is closed.
                          2025-09-24 22:25:19.236 - warn: zigbee.0 (296477) get state error: Connection is closed.
                          2025-09-24 22:25:19.237 - warn: zigbee.0 (296477) get state error: Connection is closed.
                          2025-09-24 22:25:19.237 - warn: zigbee.0 (296477) get state error: Connection is closed.
                          2025-09-24 22:25:19.238 - warn: zigbee.0 (296477) get state error: Connection is closed.
                          2025-09-24 22:25:19.239 - warn: zigbee.0 (296477) get state error: Connection is closed.
                          2025-09-24 22:25:19.239 - warn: zigbee.0 (296477) get state error: Connection is closed.
                          2025-09-24 22:25:19.240 - warn: zigbee.0 (296477) get state error: Connection is closed.
                          2025-09-24 22:25:19.241 - warn: zigbee.0 (296477) get state error: Connection is closed.
                          2025-09-24 22:25:19.242 - warn: zigbee.0 (296477) get state error: Connection is closed.
                          2025-09-24 22:25:19.242 - warn: zigbee.0 (296477) get state error: Connection is closed.
                          2025-09-24 22:25:19.243 - warn: zigbee.0 (296477) get state error: Connection is closed.
                          2025-09-24 22:25:19.244 - warn: zigbee.0 (296477) get state error: Connection is closed.
                          2025-09-24 22:25:19.245 - warn: zigbee.0 (296477) get state error: Connection is closed.
                          2025-09-24 22:25:19.245 - warn: zigbee.0 (296477) get state error: Connection is closed.
                          2025-09-24 22:25:19.246 - warn: zigbee.0 (296477) get state error: Connection is closed.
                          2025-09-24 22:25:19.246 - warn: zigbee.0 (296477) get state error: Connection is closed.
                          2025-09-24 22:25:19.247 - warn: zigbee.0 (296477) get state error: Connection is closed.
                          2025-09-24 22:25:19.248 - warn: zigbee.0 (296477) get state error: Connection is closed.
                          2025-09-24 22:25:19.248 - warn: zigbee.0 (296477) get state error: Connection is closed.
                          2025-09-24 22:25:19.249 - warn: zigbee.0 (296477) get state error: Connection is closed.
                          2025-09-24 22:25:19.249 - warn: zigbee.0 (296477) get state error: Connection is closed.
                          2025-09-24 22:25:19.250 - warn: zigbee.0 (296477) get state error: Connection is closed.
                          2025-09-24 22:25:19.251 - warn: zigbee.0 (296477) get state error: Connection is closed.
                          2025-09-24 22:25:19.251 - warn: zigbee.0 (296477) get state error: Connection is closed.
                          2025-09-24 22:25:19.252 - warn: zigbee.0 (296477) get state error: Connection is closed.
                          2025-09-24 22:25:19.252 - warn: zigbee.0 (296477) get state error: Connection is closed.
                          2025-09-24 22:25:19.253 - warn: zigbee.0 (296477) get state error: Connection is closed.
                          2025-09-24 22:25:19.253 - warn: zigbee.0 (296477) get state error: Connection is closed.
                          2025-09-24 22:25:19.254 - warn: zigbee.0 (296477) get state error: Connection is closed.
                          2025-09-24 22:25:19.254 - warn: zigbee.0 (296477) get state error: Connection is closed.
                          2025-09-24 22:25:19.255 - warn: zigbee.0 (296477) get state error: Connection is closed.
                          2025-09-24 22:25:19.255 - warn: zigbee.0 (296477) get state error: Connection is closed.
                          2025-09-24 22:25:19.255 - warn: zigbee.0 (296477) get state error: Connection is closed.
                          2025-09-24 22:25:19.256 - warn: zigbee.0 (296477) get state error: Connection is closed.
                          2025-09-24 22:25:19.256 - warn: zigbee.0 (296477) get state error: Connection is closed.
                          2025-09-24 22:25:19.257 - warn: zigbee.0 (296477) get state error: Connection is closed.
                          2025-09-24 22:25:19.257 - warn: zigbee.0 (296477) get state error: Connection is closed.
                          2025-09-24 22:25:19.258 - warn: zigbee.0 (296477) get state error: Connection is closed.
                          2025-09-24 22:25:19.258 - warn: zigbee.0 (296477) get state error: Connection is closed.
                          2025-09-24 22:25:19.470 - warn: zigbee.0 (296477) get state error: Connection is closed.
                          2025-09-24 22:25:19.471 - warn: zigbee.0 (296477) get state error: Connection is closed.
                          2025-09-24 22:25:19.471 - warn: zigbee.0 (296477) get state error: Connection is closed.
                          2025-09-24 22:25:19.472 - warn: zigbee.0 (296477) get state error: Connection is closed.
                          2025-09-24 22:25:19.472 - warn: zigbee.0 (296477) get state error: Connection is closed.
                          2025-09-24 22:25:19.473 - warn: zigbee.0 (296477) get state error: Connection is closed.
                          2025-09-24 22:25:19.478 - error: zigbee.0 (296477) Cannot check file existence of "cfg.f.zigbee.admin$%$img/RTCGQ11LM.png$%$data": DB closed
                          2025-09-24 22:25:19.478 - error: zigbee.0 (296477) Cannot check file existence of "cfg.f.zigbee.admin$%$img/WSDCGQ11LM.png$%$data": DB closed
                          2025-09-24 22:25:19.479 - error: zigbee.0 (296477) Cannot check file existence of "cfg.f.zigbee.admin$%$img/ptvo.switch.png$%$data": DB closed
                          2025-09-24 22:25:19.479 - error: zigbee.0 (296477) Cannot check file existence of "cfg.f.zigbee.admin$%$img/MCCGQ11LM.png$%$data": DB closed
                          2025-09-24 22:25:19.499 - error: zigbee.0 (296477) Cannot check file existence of "cfg.f.zigbee.admin$%$img/MCCGQ11LM.png$%$data": Connection is closed.
                          2025-09-24 22:25:19.500 - error: zigbee.0 (296477) Cannot check file existence of "cfg.f.zigbee.admin$%$img/TS0121_plug.png$%$data": Connection is closed.
                          2025-09-24 22:25:19.500 - error: zigbee.0 (296477) Cannot check file existence of "cfg.f.zigbee.admin$%$img/DIYRuZ_Flower.png$%$data": Connection is closed.
                          2025-09-24 22:25:19.501 - error: zigbee.0 (296477) Cannot check file existence of "cfg.f.zigbee.admin$%$img/SWV.png$%$data": Connection is closed.
                          2025-09-24 22:25:19.501 - error: zigbee.0 (296477) Cannot check file existence of "cfg.f.zigbee.admin$%$img/HG08010.png$%$data": Connection is closed.
                          2025-09-24 22:25:19.542 - error: zigbee.0 (296477) 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().
                          2025-09-24 22:25:19.542 - error: zigbee.0 (296477) unhandled promise rejection: DB closed
                          2025-09-24 22:25:19.544 - error: zigbee.0 (296477) Error: DB closed
                          at close (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:184:25)
                          at Socket. (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:151:20)
                          at Object.onceWrapper (node:events:639:26)
                          at Socket.emit (node:events:524:28)
                          at Socket.emit (node:domain:489:12)
                          at TCP. (node:net:343:12)
                          2025-09-24 22:25:19.544 - error: zigbee.0 (296477) DB closed
                          2025-09-24 22:25:19.552 - error: zigbee.0 (296477) 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().
                          2025-09-24 22:25:19.553 - error: zigbee.0 (296477) unhandled promise rejection: DB closed
                          2025-09-24 22:25:19.554 - error: zigbee.0 (296477) Error: DB closed
                          at close (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:184:25)
                          at Socket. (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:151:20)
                          at Object.onceWrapper (node:events:639:26)
                          at Socket.emit (node:events:524:28)
                          at Socket.emit (node:domain:489:12)
                          at TCP. (node:net:343:12)
                          2025-09-24 22:25:19.554 - error: zigbee.0 (296477) DB closed
                          2025-09-24 22:25:19.556 - error: zigbee.0 (296477) 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().
                          2025-09-24 22:25:19.557 - error: zigbee.0 (296477) unhandled promise rejection: DB closed
                          2025-09-24 22:25:19.557 - error: zigbee.0 (296477) Error: DB closed
                          at close (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:184:25)
                          at Socket. (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:151:20)
                          at Object.onceWrapper (node:events:639:26)
                          at Socket.emit (node:events:524:28)
                          at Socket.emit (node:domain:489:12)
                          at TCP. (node:net:343:12)
                          2025-09-24 22:25:19.558 - error: zigbee.0 (296477) DB closed
                          2025-09-24 22:25:19.560 - error: zigbee.0 (296477) 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().
                          2025-09-24 22:25:19.561 - error: zigbee.0 (296477) unhandled promise rejection: DB closed
                          2025-09-24 22:25:19.561 - error: zigbee.0 (296477) Error: DB closed
                          at close (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:184:25)
                          at Socket. (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:151:20)
                          at Object.onceWrapper (node:events:639:26)
                          at Socket.emit (node:events:524:28)
                          at Socket.emit (node:domain:489:12)
                          at TCP. (node:net:343:12)
                          2025-09-24 22:25:19.562 - error: zigbee.0 (296477) DB closed
                          2025-09-24 22:25:19.564 - error: zigbee.0 (296477) 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().
                          2025-09-24 22:25:19.564 - error: zigbee.0 (296477) unhandled promise rejection: DB closed
                          2025-09-24 22:25:19.565 - error: zigbee.0 (296477) Error: DB closed
                          at close (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:184:25)
                          at Socket. (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:151:20)
                          at Object.onceWrapper (node:events:639:26)
                          at Socket.emit (node:events:524:28)
                          at Socket.emit (node:domain:489:12)
                          at TCP. (node:net:343:12)
                          2025-09-24 22:25:19.565 - error: zigbee.0 (296477) DB closed
                          2025-09-24 22:25:19.567 - error: zigbee.0 (296477) 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().
                          2025-09-24 22:25:19.568 - error: zigbee.0 (296477) unhandled promise rejection: DB closed
                          2025-09-24 22:25:19.568 - error: zigbee.0 (296477) Error: DB closed
                          at close (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:184:25)
                          at Socket. (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:151:20)
                          at Object.onceWrapper (node:events:639:26)
                          at Socket.emit (node:events:524:28)
                          at Socket.emit (node:domain:489:12)
                          at TCP. (node:net:343:12)
                          2025-09-24 22:25:19.569 - error: zigbee.0 (296477) DB closed
                          2025-09-24 22:25:19.571 - error: zigbee.0 (296477) 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().
                          2025-09-24 22:25:19.572 - error: zigbee.0 (296477) unhandled promise rejection: DB closed
                          2025-09-24 22:25:19.572 - error: zigbee.0 (296477) Error: DB closed
                          at close (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:184:25)
                          at Socket. (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:151:20)
                          at Object.onceWrapper (node:events:639:26)
                          at Socket.emit (node:events:524:28)
                          at Socket.emit (node:domain:489:12)
                          at TCP. (node:net:343:12)
                          2025-09-24 22:25:19.573 - error: zigbee.0 (296477) DB closed
                          2025-09-24 22:25:19.575 - error: zigbee.0 (296477) 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().
                          2025-09-24 22:25:19.576 - error: zigbee.0 (296477) unhandled promise rejection: DB closed
                          2025-09-24 22:25:19.576 - error: zigbee.0 (296477) Error: DB closed
                          at close (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:184:25)
                          at Socket. (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:151:20)
                          at Object.onceWrapper (node:events:639:26)
                          at Socket.emit (node:events:524:28)
                          at Socket.emit (node:domain:489:12)
                          at TCP. (node:net:343:12)
                          2025-09-24 22:25:19.576 - error: zigbee.0 (296477) DB closed
                          2025-09-24 22:25:19.579 - error: zigbee.0 (296477) 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().
                          2025-09-24 22:25:19.580 - error: zigbee.0 (296477) unhandled promise rejection: DB closed
                          2025-09-24 22:25:19.580 - error: zigbee.0 (296477) Error: DB closed
                          at close (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:184:25)
                          at Socket. (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:151:20)
                          at Object.onceWrapper (node:events:639:26)
                          at Socket.emit (node:events:524:28)
                          at Socket.emit (node:domain:489:12)
                          at TCP. (node:net:343:12)
                          2025-09-24 22:25:19.581 - error: zigbee.0 (296477) DB closed
                          2025-09-24 22:25:19.582 - error: zigbee.0 (296477) 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().
                          2025-09-24 22:25:19.583 - error: zigbee.0 (296477) unhandled promise rejection: DB closed
                          2025-09-24 22:25:19.583 - error: zigbee.0 (296477) Error: DB closed
                          at close (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:184:25)
                          at Socket. (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:151:20)
                          at Object.onceWrapper (node:events:639:26)
                          at Socket.emit (node:events:524:28)
                          at Socket.emit (node:domain:489:12)
                          at TCP. (node:net:343:12)
                          2025-09-24 22:25:19.584 - error: zigbee.0 (296477) DB closed
                          2025-09-24 22:25:19.586 - error: zigbee.0 (296477) 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().
                          2025-09-24 22:25:19.586 - error: zigbee.0 (296477) unhandled promise rejection: DB closed
                          2025-09-24 22:25:19.587 - error: zigbee.0 (296477) Error: DB closed
                          at close (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:184:25)
                          at Socket. (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:151:20)
                          at Object.onceWrapper (node:events:639:26)
                          at Socket.emit (node:events:524:28)
                          at Socket.emit (node:domain:489:12)
                          at TCP. (node:net:343:12)
                          2025-09-24 22:25:19.587 - error: zigbee.0 (296477) DB closed
                          2025-09-24 22:25:19.589 - error: zigbee.0 (296477) 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().
                          2025-09-24 22:25:19.590 - error: zigbee.0 (296477) unhandled promise rejection: DB closed
                          2025-09-24 22:25:19.590 - error: zigbee.0 (296477) Error: DB closed
                          at close (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:184:25)
                          at Socket. (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:151:20)
                          at Object.onceWrapper (node:events:639:26)
                          at Socket.emit (node:events:524:28)
                          at Socket.emit (node:domain:489:12)
                          at TCP. (node:net:343:12)
                          2025-09-24 22:25:19.591 - error: zigbee.0 (296477) DB closed
                          2025-09-24 22:25:19.592 - error: zigbee.0 (296477) 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().
                          2025-09-24 22:25:19.593 - error: zigbee.0 (296477) unhandled promise rejection: DB closed
                          2025-09-24 22:25:19.594 - error: zigbee.0 (296477) Error: DB closed
                          at close (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:184:25)
                          at Socket. (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:151:20)
                          at Object.onceWrapper (node:events:639:26)
                          at Socket.emit (node:events:524:28)
                          at Socket.emit (node:domain:489:12)
                          at TCP. (node:net:343:12)
                          2025-09-24 22:25:19.595 - error: zigbee.0 (296477) DB closed
                          2025-09-24 22:25:19.596 - error: zigbee.0 (296477) 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().
                          2025-09-24 22:25:19.596 - error: zigbee.0 (296477) unhandled promise rejection: DB closed
                          2025-09-24 22:25:19.596 - error: zigbee.0 (296477) Error: DB closed
                          at close (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:184:25)
                          at Socket. (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:151:20)
                          at Object.onceWrapper (node:events:639:26)
                          at Socket.emit (node:events:524:28)
                          at Socket.emit (node:domain:489:12)
                          at TCP. (node:net:343:12)
                          2025-09-24 22:25:19.597 - error: zigbee.0 (296477) DB closed
                          2025-09-24 22:25:19.598 - error: zigbee.0 (296477) 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().
                          2025-09-24 22:25:19.599 - error: zigbee.0 (296477) unhandled promise rejection: DB closed
                          2025-09-24 22:25:19.599 - error: zigbee.0 (296477) Error: DB closed
                          at close (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:184:25)
                          at Socket. (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:151:20)
                          at Object.onceWrapper (node:events:639:26)
                          at Socket.emit (node:events:524:28)
                          at Socket.emit (node:domain:489:12)
                          at TCP. (node:net:343:12)
                          2025-09-24 22:25:19.600 - error: zigbee.0 (296477) DB closed
                          2025-09-24 22:25:19.602 - info: zigbee.0 (296477) downloading https://www.zigbee2mqtt.io/images/devices/RTCGQ11LM.png to img/RTCGQ11LM.png
                          2025-09-24 22:25:19.629 - info: zigbee.0 (296477) downloading https://www.zigbee2mqtt.io/images/devices/WSDCGQ11LM.png to img/WSDCGQ11LM.png
                          2025-09-24 22:25:19.639 - info: zigbee.0 (296477) downloading https://www.zigbee2mqtt.io/images/devices/ptvo.switch.png to img/ptvo.switch.png
                          2025-09-24 22:25:19.647 - info: zigbee.0 (296477) downloading https://www.zigbee2mqtt.io/images/devices/MCCGQ11LM.png to img/MCCGQ11LM.png
                          2025-09-24 22:25:19.878 - error: host.GartenIoB 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:
                          2025-09-24 22:25:19.879 - error: host.GartenIoB Caught by controller[1]: TypeError: Cannot read properties of undefined (reading 'measurement_poll_interval')
                          2025-09-24 22:25:19.879 - error: host.GartenIoB Caught by controller[1]: at onEvent (/opt/iobroker/node_modules/zigbee-herdsman-converters/src/lib/modernExtend.ts:678:58)
                          2025-09-24 22:25:19.879 - error: host.GartenIoB Caught by controller[1]: at Object.onEvent (/opt/iobroker/node_modules/zigbee-herdsman-converters/src/index.ts:376:27)
                          2025-09-24 22:25:19.879 - error: host.GartenIoB Caught by controller[1]: at DeviceEvent.callOnEvent (/opt/iobroker/node_modules/iobroker.zigbee/lib/zbDeviceEvent.js:69:26)
                          2025-09-24 22:25:19.879 - error: host.GartenIoB Caught by controller[1]: at processTicksAndRejections (node:internal/process/task_queues:95:5)
                          2025-09-24 22:25:19.879 - error: host.GartenIoB Caught by controller[1]: at DeviceEvent.onZigbeeStarted (/opt/iobroker/node_modules/iobroker.zigbee/lib/zbDeviceEvent.js:13:13)
                          2025-09-24 22:25:19.879 - error: host.GartenIoB Caught by controller[1]: at async Promise.all (index 2)
                          2025-09-24 22:25:19.880 - error: host.GartenIoB 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:
                          2025-09-24 22:25:19.880 - error: host.GartenIoB Caught by controller[3]: Error: DB closed
                          2025-09-24 22:25:19.880 - error: host.GartenIoB Caught by controller[3]: at close (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:184:25)
                          2025-09-24 22:25:19.880 - error: host.GartenIoB Caught by controller[3]: at Socket. (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:151:20)
                          2025-09-24 22:25:19.880 - error: host.GartenIoB Caught by controller[3]: at Object.onceWrapper (node:events:639:26)
                          2025-09-24 22:25:19.880 - error: host.GartenIoB Caught by controller[3]: at Socket.emit (node:events:524:28)
                          2025-09-24 22:25:19.880 - error: host.GartenIoB Caught by controller[3]: at Socket.emit (node:domain:489:12)
                          2025-09-24 22:25:19.880 - error: host.GartenIoB Caught by controller[3]: at TCP. (node:net:343:12)
                          2025-09-24 22:25:19.880 - error: host.GartenIoB 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:
                          2025-09-24 22:25:19.880 - error: host.GartenIoB Caught by controller[5]: Error: DB closed
                          2025-09-24 22:25:19.881 - error: host.GartenIoB Caught by controller[5]: at close (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:184:25)
                          2025-09-24 22:25:19.881 - error: host.GartenIoB Caught by controller[5]: at Socket. (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:151:20)
                          2025-09-24 22:25:19.881 - error: host.GartenIoB Caught by controller[5]: at Object.onceWrapper (node:events:639:26)
                          2025-09-24 22:25:19.881 - error: host.GartenIoB Caught by controller[5]: at Socket.emit (node:events:524:28)
                          2025-09-24 22:25:19.881 - error: host.GartenIoB Caught by controller[5]: at Socket.emit (node:domain:489:12)
                          2025-09-24 22:25:19.881 - error: host.GartenIoB Caught by controller[5]: at TCP. (node:net:343:12)
                          2025-09-24 22:25:19.881 - error: host.GartenIoB 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:
                          2025-09-24 22:25:19.881 - error: host.GartenIoB Caught by controller[7]: Error: DB closed
                          2025-09-24 22:25:19.881 - error: host.GartenIoB Caught by controller[7]: at close (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:184:25)
                          2025-09-24 22:25:19.881 - error: host.GartenIoB Caught by controller[7]: at Socket. (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:151:20)
                          2025-09-24 22:25:19.882 - error: host.GartenIoB Caught by controller[7]: at Object.onceWrapper (node:events:639:26)
                          2025-09-24 22:25:19.882 - error: host.GartenIoB Caught by controller[7]: at Socket.emit (node:events:524:28)
                          2025-09-24 22:25:19.882 - error: host.GartenIoB Caught by controller[7]: at Socket.emit (node:domain:489:12)
                          2025-09-24 22:25:19.882 - error: host.GartenIoB Caught by controller[7]: at TCP. (node:net:343:12)
                          2025-09-24 22:25:19.882 - error: host.GartenIoB 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:
                          2025-09-24 22:25:19.882 - error: host.GartenIoB Caught by controller[9]: Error: DB closed
                          2025-09-24 22:25:19.882 - error: host.GartenIoB Caught by controller[9]: at close (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:184:25)
                          2025-09-24 22:25:19.882 - error: host.GartenIoB Caught by controller[9]: at Socket. (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:151:20)
                          2025-09-24 22:25:19.883 - error: host.GartenIoB Caught by controller[9]: at Object.onceWrapper (node:events:639:26)
                          2025-09-24 22:25:19.883 - error: host.GartenIoB Caught by controller[9]: at Socket.emit (node:events:524:28)
                          2025-09-24 22:25:19.883 - error: host.GartenIoB Caught by controller[9]: at Socket.emit (node:domain:489:12)
                          2025-09-24 22:25:19.883 - error: host.GartenIoB Caught by controller[9]: at TCP. (node:net:343:12)
                          2025-09-24 22:25:19.883 - error: host.GartenIoB 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:
                          2025-09-24 22:25:19.883 - error: host.GartenIoB Caught by controller[11]: Error: DB closed
                          2025-09-24 22:25:19.883 - error: host.GartenIoB Caught by controller[11]: at close (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:184:25)
                          2025-09-24 22:25:19.883 - error: host.GartenIoB Caught by controller[11]: at Socket. (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:151:20)
                          2025-09-24 22:25:19.883 - error: host.GartenIoB Caught by controller[11]: at Object.onceWrapper (node:events:639:26)
                          2025-09-24 22:25:19.883 - error: host.GartenIoB Caught by controller[11]: at Socket.emit (node:events:524:28)
                          2025-09-24 22:25:19.884 - error: host.GartenIoB Caught by controller[11]: at Socket.emit (node:domain:489:12)
                          2025-09-24 22:25:19.884 - error: host.GartenIoB Caught by controller[11]: at TCP. (node:net:343:12)
                          2025-09-24 22:25:19.884 - error: host.GartenIoB 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:
                          2025-09-24 22:25:19.884 - error: host.GartenIoB Caught by controller[13]: Error: DB closed
                          2025-09-24 22:25:19.884 - error: host.GartenIoB Caught by controller[13]: at close (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:184:25)
                          2025-09-24 22:25:19.884 - error: host.GartenIoB Caught by controller[13]: at Socket. (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:151:20)
                          2025-09-24 22:25:19.884 - error: host.GartenIoB Caught by controller[13]: at Object.onceWrapper (node:events:639:26)
                          2025-09-24 22:25:19.884 - error: host.GartenIoB Caught by controller[13]: at Socket.emit (node:events:524:28)
                          2025-09-24 22:25:19.884 - error: host.GartenIoB Caught by controller[13]: at Socket.emit (node:domain:489:12)
                          2025-09-24 22:25:19.885 - error: host.GartenIoB Caught by controller[13]: at TCP. (node:net:343:12)
                          2025-09-24 22:25:19.885 - error: host.GartenIoB 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:
                          2025-09-24 22:25:19.885 - error: host.GartenIoB Caught by controller[15]: Error: DB closed
                          2025-09-24 22:25:19.885 - error: host.GartenIoB Caught by controller[15]: at close (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:184:25)
                          2025-09-24 22:25:19.885 - error: host.GartenIoB Caught by controller[15]: at Socket. (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:151:20)
                          2025-09-24 22:25:19.885 - error: host.GartenIoB Caught by controller[15]: at Object.onceWrapper (node:events:639:26)
                          2025-09-24 22:25:19.885 - error: host.GartenIoB Caught by controller[15]: at Socket.emit (node:events:524:28)
                          2025-09-24 22:25:19.885 - error: host.GartenIoB Caught by controller[15]: at Socket.emit (node:domain:489:12)
                          2025-09-24 22:25:19.885 - error: host.GartenIoB Caught by controller[15]: at TCP. (node:net:343:12)
                          2025-09-24 22:25:19.885 - error: host.GartenIoB Caught by controller[16]: 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:
                          2025-09-24 22:25:19.886 - error: host.GartenIoB Caught by controller[17]: Error: DB closed
                          2025-09-24 22:25:19.886 - error: host.GartenIoB Caught by controller[17]: at close (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:184:25)
                          2025-09-24 22:25:19.886 - error: host.GartenIoB Caught by controller[17]: at Socket. (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:151:20)
                          2025-09-24 22:25:19.886 - error: host.GartenIoB Caught by controller[17]: at Object.onceWrapper (node:events:639:26)
                          2025-09-24 22:25:19.886 - error: host.GartenIoB Caught by controller[17]: at Socket.emit (node:events:524:28)
                          2025-09-24 22:25:19.886 - error: host.GartenIoB Caught by controller[17]: at Socket.emit (node:domain:489:12)
                          2025-09-24 22:25:19.886 - error: host.GartenIoB Caught by controller[17]: at TCP. (node:net:343:12)
                          2025-09-24 22:25:19.886 - error: host.GartenIoB Caught by controller[18]: 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:
                          2025-09-24 22:25:19.886 - error: host.GartenIoB Caught by controller[19]: Error: DB closed
                          2025-09-24 22:25:19.887 - error: host.GartenIoB Caught by controller[19]: at close (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:184:25)
                          2025-09-24 22:25:19.887 - error: host.GartenIoB Caught by controller[19]: at Socket. (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:151:20)
                          2025-09-24 22:25:19.887 - error: host.GartenIoB Caught by controller[19]: at Object.onceWrapper (node:events:639:26)
                          2025-09-24 22:25:19.887 - error: host.GartenIoB Caught by controller[19]: at Socket.emit (node:events:524:28)
                          2025-09-24 22:25:19.887 - error: host.GartenIoB Caught by controller[19]: at Socket.emit (node:domain:489:12)
                          2025-09-24 22:25:19.887 - error: host.GartenIoB Caught by controller[19]: at TCP. (node:net:343:12)
                          2025-09-24 22:25:19.887 - error: host.GartenIoB Caught by controller[20]: 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:
                          2025-09-24 22:25:19.888 - error: host.GartenIoB Caught by controller[21]: Error: DB closed
                          2025-09-24 22:25:19.888 - error: host.GartenIoB Caught by controller[21]: at close (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:184:25)
                          2025-09-24 22:25:19.888 - error: host.GartenIoB Caught by controller[21]: at Socket. (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:151:20)
                          2025-09-24 22:25:19.888 - error: host.GartenIoB Caught by controller[21]: at Object.onceWrapper (node:events:639:26)
                          2025-09-24 22:25:19.888 - error: host.GartenIoB Caught by controller[21]: at Socket.emit (node:events:524:28)
                          2025-09-24 22:25:19.888 - error: host.GartenIoB Caught by controller[21]: at Socket.emit (node:domain:489:12)
                          2025-09-24 22:25:19.888 - error: host.GartenIoB Caught by controller[21]: at TCP. (node:net:343:12)
                          2025-09-24 22:25:19.888 - error: host.GartenIoB Caught by controller[22]: 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:
                          2025-09-24 22:25:19.889 - error: host.GartenIoB Caught by controller[23]: Error: DB closed
                          2025-09-24 22:25:19.889 - error: host.GartenIoB Caught by controller[23]: at close (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:184:25)
                          2025-09-24 22:25:19.889 - error: host.GartenIoB Caught by controller[23]: at Socket. (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:151:20)
                          2025-09-24 22:25:19.889 - error: host.GartenIoB Caught by controller[23]: at Object.onceWrapper (node:events:639:26)
                          2025-09-24 22:25:19.889 - error: host.GartenIoB Caught by controller[23]: at Socket.emit (node:events:524:28)
                          2025-09-24 22:25:19.889 - error: host.GartenIoB Caught by controller[23]: at Socket.emit (node:domain:489:12)
                          2025-09-24 22:25:19.889 - error: host.GartenIoB Caught by controller[23]: at TCP. (node:net:343:12)
                          2025-09-24 22:25:19.890 - error: host.GartenIoB Caught by controller[24]: 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:
                          2025-09-24 22:25:19.890 - error: host.GartenIoB Caught by controller[25]: Error: DB closed
                          2025-09-24 22:25:19.890 - error: host.GartenIoB Caught by controller[25]: at close (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:184:25)
                          2025-09-24 22:25:19.890 - error: host.GartenIoB Caught by controller[25]: at Socket. (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:151:20)
                          2025-09-24 22:25:19.890 - error: host.GartenIoB Caught by controller[25]: at Object.onceWrapper (node:events:639:26)
                          2025-09-24 22:25:19.890 - error: host.GartenIoB Caught by controller[25]: at Socket.emit (node:events:524:28)
                          2025-09-24 22:25:19.890 - error: host.GartenIoB Caught by controller[25]: at Socket.emit (node:domain:489:12)
                          2025-09-24 22:25:19.891 - error: host.GartenIoB Caught by controller[25]: at TCP. (node:net:343:12)
                          2025-09-24 22:25:19.891 - error: host.GartenIoB Caught by controller[26]: 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:
                          2025-09-24 22:25:19.891 - error: host.GartenIoB Caught by controller[27]: Error: DB closed
                          2025-09-24 22:25:19.891 - error: host.GartenIoB Caught by controller[27]: at close (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:184:25)
                          2025-09-24 22:25:19.891 - error: host.GartenIoB Caught by controller[27]: at Socket. (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:151:20)
                          2025-09-24 22:25:19.891 - error: host.GartenIoB Caught by controller[27]: at Object.onceWrapper (node:events:639:26)
                          2025-09-24 22:25:19.891 - error: host.GartenIoB Caught by controller[27]: at Socket.emit (node:events:524:28)
                          2025-09-24 22:25:19.891 - error: host.GartenIoB Caught by controller[27]: at Socket.emit (node:domain:489:12)
                          2025-09-24 22:25:19.891 - error: host.GartenIoB Caught by controller[27]: at TCP. (node:net:343:12)
                          2025-09-24 22:25:19.892 - error: host.GartenIoB Caught by controller[28]: 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:
                          2025-09-24 22:25:19.892 - error: host.GartenIoB Caught by controller[29]: Error: DB closed
                          2025-09-24 22:25:19.892 - error: host.GartenIoB Caught by controller[29]: at close (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:184:25)
                          2025-09-24 22:25:19.892 - error: host.GartenIoB Caught by controller[29]: at Socket. (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:151:20)
                          2025-09-24 22:25:19.892 - error: host.GartenIoB Caught by controller[29]: at Object.onceWrapper (node:events:639:26)
                          2025-09-24 22:25:19.892 - error: host.GartenIoB Caught by controller[29]: at Socket.emit (node:events:524:28)
                          2025-09-24 22:25:19.892 - error: host.GartenIoB Caught by controller[29]: at Socket.emit (node:domain:489:12)
                          2025-09-24 22:25:19.892 - error: host.GartenIoB Caught by controller[29]: at TCP. (node:net:343:12)
                          2025-09-24 22:25:19.892 - error: host.GartenIoB Caught by controller[30]: 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:
                          2025-09-24 22:25:19.892 - error: host.GartenIoB Caught by controller[31]: Error: DB closed
                          2025-09-24 22:25:19.893 - error: host.GartenIoB Caught by controller[31]: at close (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:184:25)
                          2025-09-24 22:25:19.893 - error: host.GartenIoB Caught by controller[31]: at Socket. (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:151:20)
                          2025-09-24 22:25:19.893 - error: host.GartenIoB Caught by controller[31]: at Object.onceWrapper (node:events:639:26)
                          2025-09-24 22:25:19.893 - error: host.GartenIoB Caught by controller[31]: at Socket.emit (node:events:524:28)
                          2025-09-24 22:25:19.893 - error: host.GartenIoB Caught by controller[31]: at Socket.emit (node:domain:489:12)
                          2025-09-24 22:25:19.893 - error: host.GartenIoB Caught by controller[31]: at TCP. (node:net:343:12)
                          2025-09-24 22:25:19.893 - error: host.GartenIoB Caught by controller[32]: 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:
                          2025-09-24 22:25:19.893 - error: host.GartenIoB Caught by controller[33]: Error: DB closed
                          2025-09-24 22:25:19.894 - error: host.GartenIoB Caught by controller[33]: at Redis.sendCommand (/opt/iobroker/node_modules/ioredis/built/redis/index.js:636:24)
                          2025-09-24 22:25:19.894 - error: host.GartenIoB Caught by controller[33]: at Redis.get (/opt/iobroker/node_modules/ioredis/built/commander.js:121:25)
                          2025-09-24 22:25:19.894 - error: host.GartenIoB Caught by controller[33]: at ObjectsInRedisClient._getObject (file:///opt/iobroker/node_modules/@iobroker/db-objects-redis/src/lib/objects/objectsInRedisClient.ts:3011:37)
                          2025-09-24 22:25:19.894 - error: host.GartenIoB Caught by controller[33]: at Immediate. (file:///opt/iobroker/node_modules/@iobroker/db-objects-redis/src/lib/objects/objectsInRedisClient.ts:3070:29)
                          2025-09-24 22:25:19.894 - error: host.GartenIoB Caught by controller[33]: at processImmediate (node:internal/timers:485:21)
                          2025-09-24 22:25:19.894 - error: host.GartenIoB Caught by controller[34]: 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:
                          2025-09-24 22:25:19.894 - error: host.GartenIoB Caught by controller[35]: Error: DB closed
                          2025-09-24 22:25:19.894 - error: host.GartenIoB Caught by controller[35]: at Redis.sendCommand (/opt/iobroker/node_modules/ioredis/built/redis/index.js:636:24)
                          2025-09-24 22:25:19.895 - error: host.GartenIoB Caught by controller[35]: at Redis.get (/opt/iobroker/node_modules/ioredis/built/commander.js:121:25)
                          2025-09-24 22:25:19.895 - error: host.GartenIoB Caught by controller[35]: at ObjectsInRedisClient._getObject (file:///opt/iobroker/node_modules/@iobroker/db-objects-redis/src/lib/objects/objectsInRedisClient.ts:3011:37)
                          2025-09-24 22:25:19.895 - error: host.GartenIoB Caught by controller[35]: at Immediate. (file:///opt/iobroker/node_modules/@iobroker/db-objects-redis/src/lib/objects/objectsInRedisClient.ts:3070:29)
                          2025-09-24 22:25:19.895 - error: host.GartenIoB Caught by controller[35]: at processImmediate (node:internal/timers:485:21)
                          2025-09-24 22:25:19.895 - error: host.GartenIoB Caught by controller[36]: 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:
                          2025-09-24 22:25:19.895 - error: host.GartenIoB Caught by controller[37]: Error: DB closed
                          2025-09-24 22:25:19.895 - error: host.GartenIoB Caught by controller[37]: at Redis.sendCommand (/opt/iobroker/node_modules/ioredis/built/redis/index.js:636:24)
                          2025-09-24 22:25:19.895 - error: host.GartenIoB Caught by controller[37]: at Redis.get (/opt/iobroker/node_modules/ioredis/built/commander.js:121:25)
                          2025-09-24 22:25:19.896 - error: host.GartenIoB Caught by controller[37]: at ObjectsInRedisClient._getObject (file:///opt/iobroker/node_modules/@iobroker/db-objects-redis/src/lib/objects/objectsInRedisClient.ts:3011:37)
                          2025-09-24 22:25:19.896 - error: host.GartenIoB Caught by controller[37]: at Immediate. (file:///opt/iobroker/node_modules/@iobroker/db-objects-redis/src/lib/objects/objectsInRedisClient.ts:3070:29)
                          2025-09-24 22:25:19.896 - error: host.GartenIoB Caught by controller[37]: at processImmediate (node:internal/timers:485:21)
                          2025-09-24 22:25:19.896 - error: host.GartenIoB Caught by controller[38]: 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:
                          2025-09-24 22:25:19.896 - error: host.GartenIoB Caught by controller[39]: Error: DB closed
                          2025-09-24 22:25:19.896 - error: host.GartenIoB Caught by controller[39]: at Redis.sendCommand (/opt/iobroker/node_modules/ioredis/built/redis/index.js:636:24)
                          2025-09-24 22:25:19.896 - error: host.GartenIoB Caught by controller[39]: at Redis.get (/opt/iobroker/node_modules/ioredis/built/commander.js:121:25)
                          2025-09-24 22:25:19.896 - error: host.GartenIoB Caught by controller[39]: at ObjectsInRedisClient._getObject (file:///opt/iobroker/node_modules/@iobroker/db-objects-redis/src/lib/objects/objectsInRedisClient.ts:3011:37)
                          2025-09-24 22:25:19.896 - error: host.GartenIoB Caught by controller[39]: at Immediate. (file:///opt/iobroker/node_modules/@iobroker/db-objects-redis/src/lib/objects/objectsInRedisClient.ts:3070:29)
                          2025-09-24 22:25:19.897 - error: host.GartenIoB Caught by controller[39]: at processImmediate (node:internal/timers:485:21)
                          2025-09-24 22:25:19.897 - error: host.GartenIoB Caught by controller[40]: 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:
                          2025-09-24 22:25:19.897 - error: host.GartenIoB Caught by controller[41]: Error: DB closed
                          2025-09-24 22:25:19.897 - error: host.GartenIoB Caught by controller[41]: at Redis.sendCommand (/opt/iobroker/node_modules/ioredis/built/redis/index.js:636:24)
                          2025-09-24 22:25:19.897 - error: host.GartenIoB Caught by controller[41]: at Redis.get (/opt/iobroker/node_modules/ioredis/built/commander.js:121:25)
                          2025-09-24 22:25:19.897 - error: host.GartenIoB Caught by controller[41]: at ObjectsInRedisClient._getObject (file:///opt/iobroker/node_modules/@iobroker/db-objects-redis/src/lib/objects/objectsInRedisClient.ts:3011:37)
                          2025-09-24 22:25:19.897 - error: host.GartenIoB Caught by controller[41]: at Immediate. (file:///opt/iobroker/node_modules/@iobroker/db-objects-redis/src/lib/objects/objectsInRedisClient.ts:3070:29)
                          2025-09-24 22:25:19.897 - error: host.GartenIoB Caught by controller[41]: at processImmediate (node:internal/timers:485:21)
                          2025-09-24 22:25:19.897 - error: host.GartenIoB Caught by controller[42]: 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:
                          2025-09-24 22:25:19.898 - error: host.GartenIoB Caught by controller[43]: Error: DB closed
                          2025-09-24 22:25:19.898 - error: host.GartenIoB Caught by controller[43]: at Redis.sendCommand (/opt/iobroker/node_modules/ioredis/built/redis/index.js:636:24)
                          2025-09-24 22:25:19.898 - error: host.GartenIoB Caught by controller[43]: at Redis.get (/opt/iobroker/node_modules/ioredis/built/commander.js:121:25)
                          2025-09-24 22:25:19.898 - error: host.GartenIoB Caught by controller[43]: at ObjectsInRedisClient._getObject (file:///opt/iobroker/node_modules/@iobroker/db-objects-redis/src/lib/objects/objectsInRedisClient.ts:3011:37)
                          2025-09-24 22:25:19.898 - error: host.GartenIoB Caught by controller[43]: at Immediate. (file:///opt/iobroker/node_modules/@iobroker/db-objects-redis/src/lib/objects/objectsInRedisClient.ts:3070:29)
                          2025-09-24 22:25:19.899 - error: host.GartenIoB Caught by controller[43]: at processImmediate (node:internal/timers:485:21)
                          2025-09-24 22:25:19.899 - error: host.GartenIoB Caught by controller[44]: 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:
                          2025-09-24 22:25:19.899 - error: host.GartenIoB Caught by controller[45]: Error: DB closed
                          2025-09-24 22:25:19.899 - error: host.GartenIoB Caught by controller[45]: at Redis.sendCommand (/opt/iobroker/node_modules/ioredis/built/redis/index.js:636:24)
                          2025-09-24 22:25:19.899 - error: host.GartenIoB Caught by controller[45]: at Redis.get (/opt/iobroker/node_modules/ioredis/built/commander.js:121:25)
                          2025-09-24 22:25:19.899 - error: host.GartenIoB Caught by controller[45]: at ObjectsInRedisClient._getObject (file:///opt/iobroker/node_modules/@iobroker/db-objects-redis/src/lib/objects/objectsInRedisClient.ts:3011:37)
                          2025-09-24 22:25:19.899 - error: host.GartenIoB Caught by controller[45]: at Immediate. (file:///opt/iobroker/node_modules/@iobroker/db-objects-redis/src/lib/objects/objectsInRedisClient.ts:3070:29)
                          2025-09-24 22:25:19.900 - error: host.GartenIoB Caught by controller[45]: at processImmediate (node:internal/timers:485:21)
                          2025-09-24 22:25:19.900 - error: host.GartenIoB Caught by controller[46]: 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:
                          2025-09-24 22:25:19.900 - error: host.GartenIoB Caught by controller[47]: Error: DB closed
                          2025-09-24 22:25:19.900 - error: host.GartenIoB Caught by controller[47]: at Redis.sendCommand (/opt/iobroker/node_modules/ioredis/built/redis/index.js:636:24)
                          2025-09-24 22:25:19.901 - error: host.GartenIoB Caught by controller[47]: at Redis.get (/opt/iobroker/node_modules/ioredis/built/commander.js:121:25)
                          2025-09-24 22:25:19.901 - error: host.GartenIoB Caught by controller[47]: at ObjectsInRedisClient._getObject (file:///opt/iobroker/node_modules/@iobroker/db-objects-redis/src/lib/objects/objectsInRedisClient.ts:3011:37)
                          2025-09-24 22:25:19.901 - error: host.GartenIoB Caught by controller[47]: at Immediate. (file:///opt/iobroker/node_modules/@iobroker/db-objects-redis/src/lib/objects/objectsInRedisClient.ts:3070:29)
                          2025-09-24 22:25:19.901 - error: host.GartenIoB Caught by controller[47]: at processImmediate (node:internal/timers:485:21)
                          2025-09-24 22:25:19.901 - error: host.GartenIoB Caught by controller[48]: 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:
                          2025-09-24 22:25:19.901 - error: host.GartenIoB Caught by controller[49]: Error: DB closed
                          2025-09-24 22:25:19.902 - error: host.GartenIoB Caught by controller[49]: at Redis.sendCommand (/opt/iobroker/node_modules/ioredis/built/redis/index.js:636:24)
                          2025-09-24 22:25:19.902 - error: host.GartenIoB Caught by controller[49]: at Redis.get (/opt/iobroker/node_modules/ioredis/built/commander.js:121:25)
                          2025-09-24 22:25:19.902 - error: host.GartenIoB Caught by controller[49]: at ObjectsInRedisClient._getObject (file:///opt/iobroker/node_modules/@iobroker/db-objects-redis/src/lib/objects/objectsInRedisClient.ts:3011:37)
                          2025-09-24 22:25:19.902 - error: host.GartenIoB Caught by controller[49]: at Immediate. (file:///opt/iobroker/node_modules/@iobroker/db-objects-redis/src/lib/objects/objectsInRedisClient.ts:3070:29)
                          2025-09-24 22:25:19.902 - error: host.GartenIoB Caught by controller[49]: at processImmediate (node:internal/timers:485:21)
                          2025-09-24 22:25:19.902 - error: host.GartenIoB Caught by controller[50]: 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:
                          2025-09-24 22:25:19.902 - error: host.GartenIoB Caught by controller[51]: Error: DB closed
                          2025-09-24 22:25:19.903 - error: host.GartenIoB Caught by controller[51]: at Redis.sendCommand (/opt/iobroker/node_modules/ioredis/built/redis/index.js:636:24)
                          2025-09-24 22:25:19.903 - error: host.GartenIoB Caught by controller[51]: at Redis.get (/opt/iobroker/node_modules/ioredis/built/commander.js:121:25)
                          2025-09-24 22:25:19.903 - error: host.GartenIoB Caught by controller[51]: at ObjectsInRedisClient._getObject (file:///opt/iobroker/node_modules/@iobroker/db-objects-redis/src/lib/objects/objectsInRedisClient.ts:3011:37)
                          2025-09-24 22:25:19.903 - error: host.GartenIoB Caught by controller[51]: at Immediate. (file:///opt/iobroker/node_modules/@iobroker/db-objects-redis/src/lib/objects/objectsInRedisClient.ts:3070:29)
                          2025-09-24 22:25:19.903 - error: host.GartenIoB Caught by controller[51]: at processImmediate (node:internal/timers:485:21)
                          2025-09-24 22:25:19.903 - error: host.GartenIoB Caught by controller[52]: 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:
                          2025-09-24 22:25:19.903 - error: host.GartenIoB Caught by controller[53]: Error: DB closed
                          2025-09-24 22:25:19.903 - error: host.GartenIoB Caught by controller[53]: at Redis.sendCommand (/opt/iobroker/node_modules/ioredis/built/redis/index.js:636:24)
                          2025-09-24 22:25:19.904 - error: host.GartenIoB Caught by controller[53]: at Redis.get (/opt/iobroker/node_modules/ioredis/built/commander.js:121:25)
                          2025-09-24 22:25:19.904 - error: host.GartenIoB Caught by controller[53]: at ObjectsInRedisClient._getObject (file:///opt/iobroker/node_modules/@iobroker/db-objects-redis/src/lib/objects/objectsInRedisClient.ts:3011:37)
                          2025-09-24 22:25:19.904 - error: host.GartenIoB Caught by controller[53]: at Immediate. (file:///opt/iobroker/node_modules/@iobroker/db-objects-redis/src/lib/objects/objectsInRedisClient.ts:3070:29)
                          2025-09-24 22:25:19.904 - error: host.GartenIoB Caught by controller[53]: at processImmediate (node:internal/timers:485:21)
                          2025-09-24 22:25:19.904 - error: host.GartenIoB Caught by controller[54]: 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:
                          2025-09-24 22:25:19.904 - error: host.GartenIoB Caught by controller[55]: Error: DB closed
                          2025-09-24 22:25:19.904 - error: host.GartenIoB Caught by controller[55]: at Redis.sendCommand (/opt/iobroker/node_modules/ioredis/built/redis/index.js:636:24)
                          2025-09-24 22:25:19.904 - error: host.GartenIoB Caught by controller[55]: at Redis.get (/opt/iobroker/node_modules/ioredis/built/commander.js:121:25)
                          2025-09-24 22:25:19.905 - error: host.GartenIoB Caught by controller[55]: at ObjectsInRedisClient._getObject (file:///opt/iobroker/node_modules/@iobroker/db-objects-redis/src/lib/objects/objectsInRedisClient.ts:3011:37)
                          2025-09-24 22:25:19.905 - error: host.GartenIoB Caught by controller[55]: at Immediate. (file:///opt/iobroker/node_modules/@iobroker/db-objects-redis/src/lib/objects/objectsInRedisClient.ts:3070:29)
                          2025-09-24 22:25:19.905 - error: host.GartenIoB Caught by controller[55]: at processImmediate (node:internal/timers:485:21)
                          2025-09-24 22:25:19.905 - error: host.GartenIoB Caught by controller[56]: 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:
                          2025-09-24 22:25:19.905 - error: host.GartenIoB Caught by controller[57]: Error: DB closed
                          2025-09-24 22:25:19.905 - error: host.GartenIoB Caught by controller[57]: at Redis.sendCommand (/opt/iobroker/node_modules/ioredis/built/redis/index.js:636:24)
                          2025-09-24 22:25:19.905 - error: host.GartenIoB Caught by controller[57]: at Redis.get (/opt/iobroker/node_modules/ioredis/built/commander.js:121:25)
                          2025-09-24 22:25:19.905 - error: host.GartenIoB Caught by controller[57]: at ObjectsInRedisClient._getObject (file:///opt/iobroker/node_modules/@iobroker/db-objects-redis/src/lib/objects/objectsInRedisClient.ts:3011:37)
                          2025-09-24 22:25:19.906 - error: host.GartenIoB Caught by controller[57]: at Immediate. (file:///opt/iobroker/node_modules/@iobroker/db-objects-redis/src/lib/objects/objectsInRedisClient.ts:3070:29)
                          2025-09-24 22:25:19.906 - error: host.GartenIoB Caught by controller[57]: at processImmediate (node:internal/timers:485:21)
                          2025-09-24 22:25:19.906 - error: host.GartenIoB Caught by controller[58]: 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:
                          2025-09-24 22:25:19.906 - error: host.GartenIoB Caught by controller[59]: Error: DB closed
                          2025-09-24 22:25:19.906 - error: host.GartenIoB Caught by controller[59]: at Redis.sendCommand (/opt/iobroker/node_modules/ioredis/built/redis/index.js:636:24)
                          2025-09-24 22:25:19.906 - error: host.GartenIoB Caught by controller[59]: at Redis.get (/opt/iobroker/node_modules/ioredis/built/commander.js:121:25)
                          2025-09-24 22:25:19.906 - error: host.GartenIoB Caught by controller[59]: at ObjectsInRedisClient._getObject (file:///opt/iobroker/node_modules/@iobroker/db-objects-redis/src/lib/objects/objectsInRedisClient.ts:3011:37)
                          2025-09-24 22:25:19.906 - error: host.GartenIoB Caught by controller[59]: at Immediate. (file:///opt/iobroker/node_modules/@iobroker/db-objects-redis/src/lib/objects/objectsInRedisClient.ts:3070:29)
                          2025-09-24 22:25:19.907 - error: host.GartenIoB Caught by controller[59]: at processImmediate (node:internal/timers:485:21)
                          2025-09-24 22:25:19.907 - error: host.GartenIoB Caught by controller[60]: 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:
                          2025-09-24 22:25:19.907 - error: host.GartenIoB Caught by controller[61]: Error: DB closed
                          2025-09-24 22:25:19.907 - error: host.GartenIoB Caught by controller[61]: at Redis.sendCommand (/opt/iobroker/node_modules/ioredis/built/redis/index.js:636:24)
                          2025-09-24 22:25:19.907 - error: host.GartenIoB Caught by controller[61]: at Redis.get (/opt/iobroker/node_modules/ioredis/built/commander.js:121:25)
                          2025-09-24 22:25:19.907 - error: host.GartenIoB Caught by controller[61]: at ObjectsInRedisClient._getObject (file:///opt/iobroker/node_modules/@iobroker/db-objects-redis/src/lib/objects/objectsInRedisClient.ts:3011:37)
                          2025-09-24 22:25:19.907 - error: host.GartenIoB Caught by controller[61]: at Immediate. (file:///opt/iobroker/node_modules/@iobroker/db-objects-redis/src/lib/objects/objectsInRedisClient.ts:3070:29)
                          2025-09-24 22:25:19.907 - error: host.GartenIoB Caught by controller[61]: at processImmediate (node:internal/timers:485:21)
                          2025-09-24 22:25:19.908 - error: host.GartenIoB Caught by controller[62]: 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:
                          2025-09-24 22:25:19.908 - error: host.GartenIoB Caught by controller[63]: Error: DB closed
                          2025-09-24 22:25:19.908 - error: host.GartenIoB Caught by controller[63]: at Redis.sendCommand (/opt/iobroker/node_modules/ioredis/built/redis/index.js:636:24)
                          2025-09-24 22:25:19.908 - error: host.GartenIoB Caught by controller[63]: at Redis.get (/opt/iobroker/node_modules/ioredis/built/commander.js:121:25)
                          2025-09-24 22:25:19.908 - error: host.GartenIoB Caught by controller[63]: at ObjectsInRedisClient._getObject (file:///opt/iobroker/node_modules/@iobroker/db-objects-redis/src/lib/objects/objectsInRedisClient.ts:3011:37)
                          2025-09-24 22:25:19.908 - error: host.GartenIoB Caught by controller[63]: at Immediate. (file:///opt/iobroker/node_modules/@iobroker/db-objects-redis/src/lib/objects/objectsInRedisClient.ts:3070:29)
                          2025-09-24 22:25:19.908 - error: host.GartenIoB Caught by controller[63]: at processImmediate (node:internal/timers:485:21)
                          2025-09-24 22:25:19.908 - error: host.GartenIoB Caught by controller[64]: 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:
                          2025-09-24 22:25:19.909 - error: host.GartenIoB Caught by controller[65]: Error: DB closed
                          2025-09-24 22:25:19.909 - error: host.GartenIoB Caught by controller[65]: at Redis.sendCommand (/opt/iobroker/node_modules/ioredis/built/redis/index.js:636:24)
                          2025-09-24 22:25:19.909 - error: host.GartenIoB Caught by controller[65]: at Redis.get (/opt/iobroker/node_modules/ioredis/built/commander.js:121:25)
                          2025-09-24 22:25:19.909 - error: host.GartenIoB Caught by controller[65]: at ObjectsInRedisClient._getObject (file:///opt/iobroker/node_modules/@iobroker/db-objects-redis/src/lib/objects/objectsInRedisClient.ts:3011:37)
                          2025-09-24 22:25:19.909 - error: host.GartenIoB Caught by controller[65]: at Immediate. (file:///opt/iobroker/node_modules/@iobroker/db-objects-redis/src/lib/objects/objectsInRedisClient.ts:3070:29)
                          2025-09-24 22:25:19.909 - error: host.GartenIoB Caught by controller[65]: at processImmediate (node:internal/timers:485:21)
                          2025-09-24 22:25:19.909 - error: host.GartenIoB Caught by controller[66]: 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:
                          2025-09-24 22:25:19.910 - error: host.GartenIoB Caught by controller[67]: Error: DB closed
                          2025-09-24 22:25:19.910 - error: host.GartenIoB Caught by controller[67]: at Redis.sendCommand (/opt/iobroker/node_modules/ioredis/built/redis/index.js:636:24)
                          2025-09-24 22:25:19.910 - error: host.GartenIoB Caught by controller[67]: at Redis.get (/opt/iobroker/node_modules/ioredis/built/commander.js:121:25)
                          2025-09-24 22:25:19.910 - error: host.GartenIoB Caught by controller[67]: at ObjectsInRedisClient._getObject (file:///opt/iobroker/node_modules/@iobroker/db-objects-redis/src/lib/objects/objectsInRedisClient.ts:3011:37)
                          2025-09-24 22:25:19.910 - error: host.GartenIoB Caught by controller[67]: at Immediate. (file:///opt/iobroker/node_modules/@iobroker/db-objects-redis/src/lib/objects/objectsInRedisClient.ts:3070:29)
                          2025-09-24 22:25:19.910 - error: host.GartenIoB Caught by controller[67]: at processImmediate (node:internal/timers:485:21)
                          2025-09-24 22:25:19.910 - error: host.GartenIoB instance system.adapter.zigbee.0 terminated with code 6 (UNCAUGHT_EXCEPTION)
                          2025-09-24 22:25:19.911 - info: host.GartenIoB Restart adapter system.adapter.zigbee.0 because enabled
                          2025-09-24 22:25:19.911 - warn: host.GartenIoB Do not restart adapter system.adapter.zigbee.0 because restart loop detected
                          2025-09-24 22:25:25.285 - info: host.GartenIoB "system.adapter.zigbee.0" disabled
                          
                          Asgothian 1 Reply Last reply Reply Quote 0
                          • Asgothian
                            Asgothian Developer @dimaiv last edited by Asgothian

                            @dimaiv Log bitte. Bei mir läuft der (sowohl auf dem Testsystem als auch auf dem Produktivsystem)

                            D 1 Reply Last reply Reply Quote 0
                            • D
                              dimaiv @Asgothian last edited by

                              @asgothian
                              Oben eingefügt.

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

                                @dimaiv Patch mal bitte bei Dir die Datei

                                /opt/iobroker/node-modules/iobroker.zigbee/lib/zbDeviceEvevnt.js

                                von

                                        if (mappedDevice && mappedDevice.onEvent && eventData.data) {
                                            this.warn(`calling onEvent for ${eventData.type} on ${device.ieeeAddr}`);
                                            mappedDevice.onEvent({type, data});
                                        }
                                    }
                                }
                                
                                module.exports = DeviceEvent;
                                

                                zu

                                        if (mappedDevice && mappedDevice.onEvent && eventData.data) {
                                            this.warn(`calling onEvent for ${eventData.type} on ${device.ieeeAddr}`);
                                            try {
                                                mappedDevice.onEvent({type, data});
                                            }
                                            catch (error)
                                           {
                                                this.warn(`error in onEvent: ${error && error.message ? error.message : 'no details'}`);
                                           }
                                        }
                                    }
                                }
                                
                                module.exports = DeviceEvent;
                                

                                Der eigentliche Fehler kommt aus dem Konverter.

                                A.

                                D 1 Reply Last reply Reply Quote 0
                                • D
                                  dimaiv @Asgothian last edited by

                                  @asgothian
                                  Gleiche Fehler

                                  2025-09-24 23:03:33.936 - info: zigbee.0 (298385) 20 devices are part of the network
                                  2025-09-24 23:03:33.938 - info: zigbee.0 (298385) Zigbee started
                                  2025-09-24 23:03:33.971 - warn: zigbee.0 (298385) DeviceEvent:calling onEvent for start on 0x60a423fffe61dd4a
                                  2025-09-24 23:03:33.986 - warn: zigbee.0 (298385) DeviceEvent:calling onEvent for start on 0x28dba7fffe6df66f
                                  2025-09-24 23:03:33.993 - warn: zigbee.0 (298385) DeviceEvent:calling onEvent for start on 0x28dba7fffe6df516
                                  2025-09-24 23:03:33.995 - warn: zigbee.0 (298385) DeviceEvent:calling onEvent for start on 0x28dba7fffe6df594
                                  2025-09-24 23:03:33.996 - warn: zigbee.0 (298385) DeviceEvent:calling onEvent for start on 0x881a14fffeea1db2
                                  2025-09-24 23:03:33.999 - warn: zigbee.0 (298385) DeviceEvent:calling onEvent for start on 0x28dba7fffe6df5f6
                                  2025-09-24 23:03:34.000 - warn: zigbee.0 (298385) DeviceEvent:calling onEvent for start on 0xa4c13801838effff
                                  2025-09-24 23:03:34.022 - error: zigbee.0 (298385) 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().
                                  2025-09-24 23:03:34.022 - error: zigbee.0 (298385) unhandled promise rejection: Cannot read properties of undefined (reading 'measurement_poll_interval')
                                  2025-09-24 23:03:34.169 - error: zigbee.0 (298385) TypeError: Cannot read properties of undefined (reading 'measurement_poll_interval')
                                  at onEvent (/opt/iobroker/node_modules/zigbee-herdsman-converters/src/lib/modernExtend.ts:678:58)
                                  at Object.onEvent (/opt/iobroker/node_modules/zigbee-herdsman-converters/src/index.ts:376:27)
                                  at DeviceEvent.callOnEvent (/opt/iobroker/node_modules/iobroker.zigbee/lib/zbDeviceEvent.js:71:30)
                                  at processTicksAndRejections (node:internal/process/task_queues:95:5)
                                  at DeviceEvent.onZigbeeStarted (/opt/iobroker/node_modules/iobroker.zigbee/lib/zbDeviceEvent.js:13:13)
                                  at async Promise.all (index 2)
                                  2025-09-24 23:03:34.169 - error: zigbee.0 (298385) Cannot read properties of undefined (reading 'measurement_poll_interval')
                                  2025-09-24 23:03:34.285 - info: zigbee.0 (298385) Halting zigbee adapter. Restart delay is at least 30 seconds.
                                  2025-09-24 23:03:34.286 - info: zigbee.0 (298385) cleaning everything up
                                  2025-09-24 23:03:34.290 - info: zigbee.0 (298385) Saved local configuration data
                                  2025-09-24 23:03:34.292 - info: zigbee.0 (298385) cleanup successful
                                  2025-09-24 23:03:34.293 - info: zigbee.0 (298385) terminating
                                  2025-09-24 23:03:34.296 - warn: zigbee.0 (298385) Terminated (UNCAUGHT_EXCEPTION): Without reason
                                  2025-09-24 23:03:34.304 - info: zigbee.0 (298385) zigbecontroller stopped successfully - ZH was not running
                                  2025-09-24 23:03:34.439 - info: zigbee.0 (298385) debug devices set to []
                                  2025-09-24 23:03:34.885 - warn: zigbee.0 (298385) get state error: DB closed
                                  2025-09-24 23:03:34.886 - warn: zigbee.0 (298385) get state error: DB closed
                                  2025-09-24 23:03:34.886 - warn: zigbee.0 (298385) get state error: DB closed
                                  
                                  Asgothian 1 Reply Last reply Reply Quote 0
                                  • Asgothian
                                    Asgothian Developer @dimaiv last edited by Asgothian

                                    @dimaiv Seltsam - der try/catch sollte das eigentlich fangen.

                                    Das kann ich ohne Gerät effektiv nicht Debuggen.

                                    A.

                                    Nachtrag: Eine mögliche Quelle hab ich noch. Bitte den folgenden Aufruf auch noch patchen:

                                                try {
                                                    mappedDevice.onEvent({type, data});
                                                }
                                    

                                    zu

                                                try {
                                                    mappedDevice.onEvent(eventData);
                                                }
                                    
                                    D 1 Reply Last reply Reply Quote 0
                                    • D
                                      dimaiv @Asgothian last edited by

                                      @asgothian
                                      Aber welchen genau...
                                      So komme ich such nicht zum deaktivieren...
                                      Hätte ich eins nach dem anderen probiert...

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

                                        @dimaiv sagte in Tester wanted - Zigbee Adapter 3.1:

                                        @asgothian
                                        Aber welchen genau...
                                        So komme ich such nicht zum deaktivieren...
                                        Hätte ich eins nach dem anderen probiert...

                                        Deaktivieren zieht an der Stelle ggf. noch nicht. Ansonsten, der der den Absturz erzeugt ist dieser:
                                        0xa4c13801838effff

                                        Erstmal geht es darum die Abstürze loszuwerden - der Fehler darf bleiben, der Adapter muss weiter laufen

                                        A.

                                        D 2 Replies Last reply Reply Quote 0
                                        • D
                                          dimaiv @Asgothian last edited by dimaiv

                                          @asgothian
                                          Jetzt startet gar nicht

                                          2025-09-24 23:22:06.365 - info: host.GartenIoB iobroker Updating objects from io-package.json for adapter "zigbee" with version "3.1.3-alpha-4"
                                          2025-09-24 23:22:07.449 - info: host.GartenIoB iobroker exit 0
                                          2025-09-24 23:22:22.257 - info: host.GartenIoB "system.adapter.zigbee.0" enabled
                                          2025-09-24 23:22:23.077 - info: host.GartenIoB instance system.adapter.zigbee.0 in version "3.1.3-alpha-4" (non-npm: ioBroker/ioBroker.zigbee) started with pid 305740
                                          2025-09-24 23:22:24.723 - error: host.GartenIoB Caught by controller[0]: /opt/iobroker/node_modules/iobroker.zigbee/lib/zbDeviceEvent.js:80
                                          2025-09-24 23:22:24.724 - error: host.GartenIoB Caught by controller[0]: SyntaxError: Unexpected end of input
                                          2025-09-24 23:22:24.724 - error: host.GartenIoB Caught by controller[0]: at wrapSafe (node:internal/modules/cjs/loader:1472:18)
                                          2025-09-24 23:22:24.724 - error: host.GartenIoB Caught by controller[0]: at Module._compile (node:internal/modules/cjs/loader:1501:20)
                                          2025-09-24 23:22:24.724 - error: host.GartenIoB Caught by controller[0]: at Module._extensions..js (node:internal/modules/cjs/loader:1613:10)
                                          2025-09-24 23:22:24.724 - error: host.GartenIoB Caught by controller[0]: at Module.load (node:internal/modules/cjs/loader:1275:32)
                                          2025-09-24 23:22:24.724 - error: host.GartenIoB Caught by controller[0]: at Module._load (node:internal/modules/cjs/loader:1096:12)
                                          2025-09-24 23:22:24.724 - error: host.GartenIoB Caught by controller[0]: at Module.require (node:internal/modules/cjs/loader:1298:19)
                                          2025-09-24 23:22:24.725 - error: host.GartenIoB Caught by controller[0]: at require (node:internal/modules/helpers:182:18)
                                          2025-09-24 23:22:24.725 - error: host.GartenIoB Caught by controller[0]: at Object. (/opt/iobroker/node_modules/iobroker.zigbee/lib/zigbeecontroller.js:12:24)
                                          2025-09-24 23:22:24.725 - error: host.GartenIoB Caught by controller[0]: at Module._compile (node:internal/modules/cjs/loader:1529:14)
                                          2025-09-24 23:22:24.725 - error: host.GartenIoB Caught by controller[0]: at Module._extensions..js (node:internal/modules/cjs/loader:1613:10)
                                          2025-09-24 23:22:24.725 - error: host.GartenIoB Caught by controller[0]: Node.js v20.19.4
                                          2025-09-24 23:22:24.725 - error: host.GartenIoB instance system.adapter.zigbee.0 terminated with code 1 (JS_CONTROLLER_STOPPED)
                                          2025-09-24 23:22:24.726 - info: host.GartenIoB Restart adapter system.adapter.zigbee.0 because enabled
                                          2025-09-24 23:22:29.156 - info: host.GartenIoB "system.adapter.zigbee.0" disabled
                                          

                                          es ist Version frisch vom Git

                                          1 Reply Last reply Reply Quote 0
                                          • D
                                            dimaiv @Asgothian last edited by

                                            @asgothian sagte in Tester wanted - Zigbee Adapter 3.1:

                                            @dimaiv sagte in Tester wanted - Zigbee Adapter 3.1:

                                            @asgothian
                                            Aber welchen genau...
                                            So komme ich such nicht zum deaktivieren...
                                            Hätte ich eins nach dem anderen probiert...

                                            Deaktivieren zieht an der Stelle ggf. noch nicht. Ansonsten, der der den Absturz erzeugt ist dieser:
                                            0xa4c13801838effff

                                            Erstmal geht es darum die Abstürze loszuwerden - der Fehler darf bleiben, der Adapter muss weiter laufen

                                            A.

                                            Es ist ein Temperatur Sensor

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

                                            Support us

                                            ioBroker
                                            Community Adapters
                                            Donate

                                            655
                                            Online

                                            32.1k
                                            Users

                                            80.7k
                                            Topics

                                            1.3m
                                            Posts

                                            tester zhc zigbee zigbee 3.1
                                            12
                                            175
                                            4295
                                            Loading More Posts
                                            • Oldest to Newest
                                            • Newest to Oldest
                                            • Most Votes
                                            Reply
                                            • Reply as topic
                                            Log in to reply
                                            Community
                                            Impressum | Datenschutz-Bestimmungen | Nutzungsbedingungen
                                            The ioBroker Community 2014-2023
                                            logo