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:

      @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 Homoran

          @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: (https://www.zigbee2mqtt.io/devices/SNZB-02LD.html)

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

            @dimaiv sagte in Tester wanted - Zigbee Adapter 3.1:

            @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

            Dumme Tippfehler, jetzt sollte die git Version wieder gehen.
            Was genau für ein Sensor ?

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

              @asgothian
              Immer noch

              2025-09-24 23:36:41.771 - info: zigbee.0 (310968) 20 devices are part of the network
              2025-09-24 23:36:41.774 - info: zigbee.0 (310968) Zigbee started
              2025-09-24 23:36:41.809 - warn: zigbee.0 (310968) DeviceEvent:calling onEvent for start on 0x60a423fffe61dd4a
              2025-09-24 23:36:41.825 - warn: zigbee.0 (310968) DeviceEvent:calling onEvent for start on 0x28dba7fffe6df66f
              2025-09-24 23:36:41.832 - warn: zigbee.0 (310968) DeviceEvent:calling onEvent for start on 0x28dba7fffe6df516
              2025-09-24 23:36:41.834 - warn: zigbee.0 (310968) DeviceEvent:calling onEvent for start on 0x28dba7fffe6df594
              2025-09-24 23:36:41.835 - warn: zigbee.0 (310968) DeviceEvent:calling onEvent for start on 0x881a14fffeea1db2
              2025-09-24 23:36:41.838 - warn: zigbee.0 (310968) DeviceEvent:calling onEvent for start on 0x28dba7fffe6df5f6
              2025-09-24 23:36:41.839 - warn: zigbee.0 (310968) DeviceEvent:calling onEvent for start on 0xa4c13801838effff
              2025-09-24 23:36:41.841 - error: zigbee.0 (310968) 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:36:41.842 - error: zigbee.0 (310968) unhandled promise rejection: Cannot read properties of undefined (reading 'measurement_poll_interval')
              2025-09-24 23:36:42.010 - error: zigbee.0 (310968) 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:70: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:36:42.011 - error: zigbee.0 (310968) Cannot read properties of undefined (reading 'measurement_poll_interval')
              2025-09-24 23:36:42.069 - info: zigbee.0 (310968) Halting zigbee adapter. Restart delay is at least 30 seconds.
              2025-09-24 23:36:42.070 - info: zigbee.0 (310968) cleaning everything up
              2025-09-24 23:36:42.073 - info: zigbee.0 (310968) Saved local configuration data
              2025-09-24 23:36:42.076 - info: zigbee.0 (310968) cleanup successful
              2025-09-24 23:36:42.077 - info: zigbee.0 (310968) terminating
              2025-09-24 23:36:42.081 - warn: zigbee.0 (310968) Terminated (UNCAUGHT_EXCEPTION): Without reason
              2025-09-24 23:36:42.089 - info: zigbee.0 (310968) zigbecontroller stopped successfully - ZH was not running
              2025-09-24 23:36:42.509 - info: zigbee.0 (310968) debug devices set to []
              2025-09-24 23:36:42.684 - warn: zigbee.0 (310968) get state error: Connection is closed.
              2025-09-24 23:36:42.685 - warn: zigbee.0 (310968) get state error: Connection is closed.
              2025-09-24 23:36:42.686 - warn: zigbee.0 (310968) get state error: Connection is closed.
              2025-09-24 23:36:42.686 - warn: zigbee.0 (310968) get state error: Connection is closed.
              2025-09-24 23:36:42.687 - warn: zigbee.0 (310968) get state error: Connection is closed.
              2025-09-24 23:36:42.688 - warn: zigbee.0 (310968) get state error: Connection is closed.
              2025-09-24 23:36:42.688 - warn: zigbee.0 (310968) get state error: Connection is closed.
              2025-09-24 23:36:42.689 - warn: zigbee.0 (310968) get state error: Connection is closed.
              2025-09-24 23:36:42.690 - warn: zigbee.0 (310968) get state error: Connection is closed.
              2025-09-24 23:36:42.691 - warn: zigbee.0 (310968) get state error: Connection is closed.
              2025-09-24 23:36:42.691 - warn: zigbee.0 (310968) get state error: Connection is closed.
              2025-09-24 23:36:42.693 - warn: zigbee.0 (310968) get state error: Connection is closed.
              2025-09-24 23:36:42.693 - warn: zigbee.0 (310968) get state error: Connection is closed.
              2025-09-24 23:36:42.694 - warn: zigbee.0 (310968) get state error: Connection is closed.
              2025-09-24 23:36:42.694 - warn: zigbee.0 (310968) get state error: Connection is closed.
              2025-09-24 23:36:42.695 - warn: zigbee.0 (310968) get state error: Connection is closed.
              2025-09-24 23:36:42.695 - warn: zigbee.0 (310968) get state error: Connection is closed.
              2025-09-24 23:36:42.696 - warn: zigbee.0 (310968) get state error: Connection is closed.
              2025-09-24 23:36:42.697 - warn: zigbee.0 (310968) get state error: Connection is closed.
              2025-09-24 23:36:42.697 - warn: zigbee.0 (310968) get state error: Connection is closed.
              2025-09-24 23:36:42.698 - warn: zigbee.0 (310968) get state error: Connection is closed.
              2025-09-24 23:36:42.699 - warn: zigbee.0 (310968) get state error: Connection is closed.
              2025-09-24 23:36:42.700 - warn: zigbee.0 (310968) get state error: Connection is closed.
              2025-09-24 23:36:42.700 - warn: zigbee.0 (310968) get state error: Connection is closed.
              2025-09-24 23:36:42.701 - warn: zigbee.0 (310968) get state error: Connection is closed.
              2025-09-24 23:36:42.702 - warn: zigbee.0 (310968) get state error: Connection is closed.
              2025-09-24 23:36:42.703 - warn: zigbee.0 (310968) get state error: Connection is closed.
              2025-09-24 23:36:42.703 - warn: zigbee.0 (310968) get state error: Connection is closed.
              2025-09-24 23:36:42.704 - warn: zigbee.0 (310968) get state error: Connection is closed.
              2025-09-24 23:36:42.705 - warn: zigbee.0 (310968) get state error: Connection is closed.
              2025-09-24 23:36:42.705 - warn: zigbee.0 (310968) get state error: Connection is closed.
              2025-09-24 23:36:42.706 - warn: zigbee.0 (310968) get state error: Connection is closed.
              2025-09-24 23:36:42.707 - warn: zigbee.0 (310968) get state error: Connection is closed.
              2025-09-24 23:36:42.708 - warn: zigbee.0 (310968) get state error: Connection is closed.
              2025-09-24 23:36:42.709 - warn: zigbee.0 (310968) get state error: Connection is closed.
              2025-09-24 23:36:42.709 - warn: zigbee.0 (310968) get state error: Connection is closed.
              2025-09-24 23:36:42.710 - warn: zigbee.0 (310968) get state error: Connection is closed.
              2025-09-24 23:36:42.711 - warn: zigbee.0 (310968) get state error: Connection is closed.
              2025-09-24 23:36:42.712 - warn: zigbee.0 (310968) get state error: Connection is closed.
              2025-09-24 23:36:42.713 - warn: zigbee.0 (310968) get state error: Connection is closed.
              2025-09-24 23:36:42.714 - warn: zigbee.0 (310968) get state error: Connection is closed.
              2025-09-24 23:36:42.715 - warn: zigbee.0 (310968) get state error: Connection is closed.
              2025-09-24 23:36:42.716 - warn: zigbee.0 (310968) get state error: Connection is closed.
              2025-09-24 23:36:42.717 - warn: zigbee.0 (310968) get state error: Connection is closed.
              2025-09-24 23:36:42.718 - warn: zigbee.0 (310968) get state error: Connection is closed.
              2025-09-24 23:36:42.719 - warn: zigbee.0 (310968) get state error: Connection is closed.
              2025-09-24 23:36:42.720 - warn: zigbee.0 (310968) get state error: Connection is closed.
              2025-09-24 23:36:42.721 - warn: zigbee.0 (310968) get state error: Connection is closed.
              2025-09-24 23:36:42.722 - warn: zigbee.0 (310968) get state error: Connection is closed.
              2025-09-24 23:36:42.722 - warn: zigbee.0 (310968) get state error: Connection is closed.
              2025-09-24 23:36:42.723 - warn: zigbee.0 (310968) get state error: Connection is closed.
              2025-09-24 23:36:42.724 - warn: zigbee.0 (310968) get state error: Connection is closed.
              2025-09-24 23:36:42.725 - warn: zigbee.0 (310968) get state error: Connection is closed.
              2025-09-24 23:36:42.726 - warn: zigbee.0 (310968) get state error: Connection is closed.
              2025-09-24 23:36:42.727 - warn: zigbee.0 (310968) get state error: Connection is closed.
              2025-09-24 23:36:42.728 - warn: zigbee.0 (310968) get state error: Connection is closed.
              2025-09-24 23:36:42.729 - warn: zigbee.0 (310968) get state error: Connection is closed.
              2025-09-24 23:36:42.730 - warn: zigbee.0 (310968) get state error: Connection is closed.
              2025-09-24 23:36:42.731 - warn: zigbee.0 (310968) get state error: Connection is closed.
              2025-09-24 23:36:42.732 - warn: zigbee.0 (310968) get state error: Connection is closed.
              2025-09-24 23:36:42.733 - warn: zigbee.0 (310968) get state error: Connection is closed.
              2025-09-24 23:36:42.734 - warn: zigbee.0 (310968) get state error: Connection is closed.
              2025-09-24 23:36:42.735 - warn: zigbee.0 (310968) get state error: Connection is closed.
              2025-09-24 23:36:42.735 - warn: zigbee.0 (310968) get state error: Connection is closed.
              2025-09-24 23:36:42.736 - warn: zigbee.0 (310968) get state error: Connection is closed.
              2025-09-24 23:36:42.737 - warn: zigbee.0 (310968) get state error: Connection is closed.
              2025-09-24 23:36:42.738 - warn: zigbee.0 (310968) get state error: Connection is closed.
              2025-09-24 23:36:42.738 - warn: zigbee.0 (310968) get state error: Connection is closed.
              2025-09-24 23:36:42.739 - warn: zigbee.0 (310968) get state error: Connection is closed.
              2025-09-24 23:36:42.797 - warn: zigbee.0 (310968) get state error: Connection is closed.
              2025-09-24 23:36:42.798 - warn: zigbee.0 (310968) get state error: Connection is closed.
              2025-09-24 23:36:42.799 - warn: zigbee.0 (310968) get state error: Connection is closed.
              2025-09-24 23:36:42.800 - warn: zigbee.0 (310968) get state error: Connection is closed.
              2025-09-24 23:36:42.800 - warn: zigbee.0 (310968) get state error: Connection is closed.
              2025-09-24 23:36:42.801 - warn: zigbee.0 (310968) get state error: Connection is closed.
              2025-09-24 23:36:42.801 - warn: zigbee.0 (310968) get state error: Connection is closed.
              2025-09-24 23:36:42.802 - warn: zigbee.0 (310968) get state error: Connection is closed.
              2025-09-24 23:36:42.803 - warn: zigbee.0 (310968) get state error: Connection is closed.
              2025-09-24 23:36:42.804 - warn: zigbee.0 (310968) get state error: Connection is closed.
              2025-09-24 23:36:42.805 - warn: zigbee.0 (310968) get state error: Connection is closed.
              2025-09-24 23:36:42.805 - warn: zigbee.0 (310968) get state error: Connection is closed.
              2025-09-24 23:36:42.806 - warn: zigbee.0 (310968) get state error: Connection is closed.
              2025-09-24 23:36:42.807 - warn: zigbee.0 (310968) get state error: Connection is closed.
              2025-09-24 23:36:42.808 - warn: zigbee.0 (310968) get state error: Connection is closed.
              2025-09-24 23:36:42.809 - warn: zigbee.0 (310968) get state error: Connection is closed.
              2025-09-24 23:36:42.810 - warn: zigbee.0 (310968) get state error: Connection is closed.
              2025-09-24 23:36:42.811 - info: zigbee.0 (310968) downloading https://www.zigbee2mqtt.io/images/devices/RTCGQ11LM.png to img/RTCGQ11LM.png
              2025-09-24 23:36:42.838 - info: zigbee.0 (310968) downloading https://www.zigbee2mqtt.io/images/devices/WSDCGQ11LM.png to img/WSDCGQ11LM.png
              2025-09-24 23:36:42.984 - error: zigbee.0 (310968) Cannot check file existence of "cfg.f.zigbee.admin$%$img/ptvo.switch.png$%$data": DB closed
              2025-09-24 23:36:42.985 - error: zigbee.0 (310968) Cannot check file existence of "cfg.f.zigbee.admin$%$img/MCCGQ11LM.png$%$data": DB closed
              2025-09-24 23:36:42.985 - error: zigbee.0 (310968) Cannot check file existence of "cfg.f.zigbee.admin$%$img/MCCGQ11LM.png$%$data": DB closed
              2025-09-24 23:36:42.985 - error: zigbee.0 (310968) Cannot check file existence of "cfg.f.zigbee.admin$%$img/TS0121_plug.png$%$data": DB closed
              2025-09-24 23:36:42.986 - error: zigbee.0 (310968) Cannot check file existence of "cfg.f.zigbee.admin$%$img/DIYRuZ_Flower.png$%$data": DB closed
              2025-09-24 23:36:42.986 - error: zigbee.0 (310968) Cannot check file existence of "cfg.f.zigbee.admin$%$img/SWV.png$%$data": DB closed
              2025-09-24 23:36:42.994 - error: zigbee.0 (310968) Cannot check file existence of "cfg.f.zigbee.admin$%$img/HG08010.png$%$data": Connection is closed.
              2025-09-24 23:36:42.995 - error: zigbee.0 (310968) Cannot check file existence of "cfg.f.zigbee.admin$%$img/WXCJKG13LM.png$%$data": Connection is closed.
              2025-09-24 23:36:42.995 - error: zigbee.0 (310968) Cannot check file existence of "cfg.f.zigbee.admin$%$img/Egony_Flower.png$%$data": Connection is closed.
              2025-09-24 23:36:42.996 - error: zigbee.0 (310968) Cannot check file existence of "cfg.f.zigbee.admin$%$img/WSDCGQ11LM.png$%$data": Connection is closed.
              2025-09-24 23:36:42.996 - error: zigbee.0 (310968) Cannot check file existence of "cfg.f.zigbee.admin$%$img/SWV.png$%$data": Connection is closed.
              2025-09-24 23:36:42.997 - error: zigbee.0 (310968) Cannot check file existence of "cfg.f.zigbee.admin$%$img/SWV.png$%$data": Connection is closed.
              2025-09-24 23:36:42.998 - error: zigbee.0 (310968) Cannot check file existence of "cfg.f.zigbee.admin$%$img/TS0601_din.png$%$data": Connection is closed.
              2025-09-24 23:36:42.999 - error: zigbee.0 (310968) Cannot check file existence of "cfg.f.zigbee.admin$%$img/SWV.png$%$data": Connection is closed.
              2025-09-24 23:36:42.999 - error: zigbee.0 (310968) Cannot check file existence of "cfg.f.zigbee.admin$%$img/Egony_Flower.png$%$data": Connection is closed.
              2025-09-24 23:36:43.000 - error: zigbee.0 (310968) Cannot check file existence of "cfg.f.zigbee.admin$%$img/SWV.png$%$data": Connection is closed.
              2025-09-24 23:36:43.000 - error: zigbee.0 (310968) Cannot check file existence of "cfg.f.zigbee.admin$%$img/SNZB-02LD.png$%$data": Connection is closed.
              2025-09-24 23:36:43.001 - error: zigbee.0 (310968) Cannot check file existence of "cfg.f.zigbee.admin$%$img/RB-SRAIN01.png$%$data": Connection is closed.
              2025-09-24 23:36:43.039 - error: zigbee.0 (310968) 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:36:43.040 - error: zigbee.0 (310968) unhandled promise rejection: DB closed
              2025-09-24 23:36:43.042 - error: zigbee.0 (310968) 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 23:36:43.042 - error: zigbee.0 (310968) DB closed
              2025-09-24 23:36:43.050 - error: zigbee.0 (310968) 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:36:43.051 - error: zigbee.0 (310968) unhandled promise rejection: DB closed
              2025-09-24 23:36:43.052 - error: zigbee.0 (310968) 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 23:36:43.052 - error: zigbee.0 (310968) DB closed
              2025-09-24 23:36:43.054 - error: zigbee.0 (310968) 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:36:43.054 - error: zigbee.0 (310968) unhandled promise rejection: DB closed
              2025-09-24 23:36:43.055 - error: zigbee.0 (310968) 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 23:36:43.055 - error: zigbee.0 (310968) DB closed
              2025-09-24 23:36:43.058 - error: zigbee.0 (310968) 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:36:43.059 - error: zigbee.0 (310968) unhandled promise rejection: DB closed
              2025-09-24 23:36:43.059 - error: zigbee.0 (310968) 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 23:36:43.059 - error: zigbee.0 (310968) DB closed
              2025-09-24 23:36:43.061 - error: zigbee.0 (310968) 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:36:43.061 - error: zigbee.0 (310968) unhandled promise rejection: DB closed
              2025-09-24 23:36:43.062 - error: zigbee.0 (310968) 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 23:36:43.062 - error: zigbee.0 (310968) DB closed
              2025-09-24 23:36:43.064 - error: zigbee.0 (310968) 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:36:43.065 - error: zigbee.0 (310968) unhandled promise rejection: DB closed
              2025-09-24 23:36:43.065 - error: zigbee.0 (310968) 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 23:36:43.065 - error: zigbee.0 (310968) DB closed
              2025-09-24 23:36:43.067 - error: zigbee.0 (310968) 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:36:43.068 - error: zigbee.0 (310968) unhandled promise rejection: DB closed
              2025-09-24 23:36:43.068 - error: zigbee.0 (310968) 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 23:36:43.069 - error: zigbee.0 (310968) DB closed
              2025-09-24 23:36:43.070 - error: zigbee.0 (310968) 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:36:43.071 - error: zigbee.0 (310968) unhandled promise rejection: DB closed
              2025-09-24 23:36:43.071 - error: zigbee.0 (310968) 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 23:36:43.072 - error: zigbee.0 (310968) DB closed
              2025-09-24 23:36:43.074 - error: zigbee.0 (310968) 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:36:43.075 - error: zigbee.0 (310968) unhandled promise rejection: DB closed
              2025-09-24 23:36:43.075 - error: zigbee.0 (310968) 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 23:36:43.076 - error: zigbee.0 (310968) DB closed
              2025-09-24 23:36:43.077 - error: zigbee.0 (310968) 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:36:43.078 - error: zigbee.0 (310968) unhandled promise rejection: DB closed
              2025-09-24 23:36:43.078 - error: zigbee.0 (310968) 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 23:36:43.079 - error: zigbee.0 (310968) DB closed
              2025-09-24 23:36:43.081 - error: zigbee.0 (310968) 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:36:43.082 - error: zigbee.0 (310968) unhandled promise rejection: DB closed
              2025-09-24 23:36:43.082 - error: zigbee.0 (310968) 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 23:36:43.082 - error: zigbee.0 (310968) DB closed
              2025-09-24 23:36:43.084 - error: zigbee.0 (310968) 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:36:43.084 - error: zigbee.0 (310968) unhandled promise rejection: DB closed
              2025-09-24 23:36:43.085 - error: zigbee.0 (310968) 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 23:36:43.085 - error: zigbee.0 (310968) DB closed
              2025-09-24 23:36:43.087 - info: zigbee.0 (310968) downloading https://www.zigbee2mqtt.io/images/devices/ptvo.switch.png to img/ptvo.switch.png
              2025-09-24 23:36:43.095 - info: zigbee.0 (310968) downloading https://www.zigbee2mqtt.io/images/devices/MCCGQ11LM.png to img/MCCGQ11LM.png
              2025-09-24 23:36:43.101 - info: zigbee.0 (310968) downloading https://www.zigbee2mqtt.io/images/devices/TS0121_plug.png to img/TS0121_plug.png
              2025-09-24 23:36:43.107 - info: zigbee.0 (310968) downloading https://www.zigbee2mqtt.io/images/devices/DIYRuZ_Flower.png to img/DIYRuZ_Flower.png
              2025-09-24 23:36:43.113 - info: zigbee.0 (310968) downloading https://www.zigbee2mqtt.io/images/devices/SWV.png to img/SWV.png
              2025-09-24 23:36:43.129 - info: zigbee.0 (310968) downloading https://www.zigbee2mqtt.io/images/devices/HG08010.png to img/HG08010.png
              2025-09-24 23:36:43.137 - info: zigbee.0 (310968) downloading https://www.zigbee2mqtt.io/images/devices/WXCJKG13LM.png to img/WXCJKG13LM.png
              2025-09-24 23:36:43.146 - info: zigbee.0 (310968) downloading https://www.zigbee2mqtt.io/images/devices/Egony_Flower.png to img/Egony_Flower.png
              2025-09-24 23:36:43.153 - info: zigbee.0 (310968) downloading https://www.zigbee2mqtt.io/images/devices/TS0601_din.png to img/TS0601_din.png
              2025-09-24 23:36:43.160 - info: zigbee.0 (310968) downloading https://www.zigbee2mqtt.io/images/devices/SNZB-02LD.png to img/SNZB-02LD.png
              2025-09-24 23:36:43.166 - info: zigbee.0 (310968) downloading https://www.zigbee2mqtt.io/images/devices/RB-SRAIN01.png to img/RB-SRAIN01.png
              2025-09-24 23:36:43.172 - warn: zigbee.0 (310968) Could not perform strict object check of state zigbee.0.00124b001ec80d25.link_quality: DB closed
              2025-09-24 23:36:43.172 - warn: zigbee.0 (310968) get state error: Connection is closed.
              2025-09-24 23:36:43.173 - warn: zigbee.0 (310968) Could not perform strict object check of state zigbee.0.00124b001ec80d25.msg_from_zigbee: DB closed
              2025-09-24 23:36:43.174 - warn: zigbee.0 (310968) get state error: Connection is closed.
              2025-09-24 23:36:43.174 - warn: zigbee.0 (310968) Could not perform strict object check of state zigbee.0.00124b001ec80d25.state_l1: DB closed
              2025-09-24 23:36:43.175 - warn: zigbee.0 (310968) get state error: Connection is closed.
              2025-09-24 23:36:43.175 - error: zigbee.0 (310968) 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:36:43.176 - error: zigbee.0 (310968) unhandled promise rejection: DB closed
              2025-09-24 23:36:43.177 - error: zigbee.0 (310968) Error: DB closed
              at Redis.sendCommand (/opt/iobroker/node_modules/ioredis/built/redis/index.js:636:24)
              at Redis.get (/opt/iobroker/node_modules/ioredis/built/commander.js:121:25)
              at ObjectsInRedisClient._getObject (file:///opt/iobroker/node_modules/@iobroker/db-objects-redis/src/lib/objects/objectsInRedisClient.ts:3011:37)
              at Immediate. (file:///opt/iobroker/node_modules/@iobroker/db-objects-redis/src/lib/objects/objectsInRedisClient.ts:3070:29)
              at processImmediate (node:internal/timers:485:21)
              2025-09-24 23:36:43.178 - error: zigbee.0 (310968) DB closed
              2025-09-24 23:36:43.183 - error: zigbee.0 (310968) 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:36:43.184 - error: zigbee.0 (310968) unhandled promise rejection: DB closed
              2025-09-24 23:36:43.185 - error: zigbee.0 (310968) Error: DB closed
              at Redis.sendCommand (/opt/iobroker/node_modules/ioredis/built/redis/index.js:636:24)
              at Redis.get (/opt/iobroker/node_modules/ioredis/built/commander.js:121:25)
              at ObjectsInRedisClient._getObject (file:///opt/iobroker/node_modules/@iobroker/db-objects-redis/src/lib/objects/objectsInRedisClient.ts:3011:37)
              at Immediate. (file:///opt/iobroker/node_modules/@iobroker/db-objects-redis/src/lib/objects/objectsInRedisClient.ts:3070:29)
              at processImmediate (node:internal/timers:485:21)
              2025-09-24 23:36:43.186 - error: zigbee.0 (310968) DB closed
              2025-09-24 23:36:43.191 - error: zigbee.0 (310968) 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:36:43.191 - error: zigbee.0 (310968) unhandled promise rejection: DB closed
              2025-09-24 23:36:43.193 - error: zigbee.0 (310968) Error: DB closed
              at Redis.sendCommand (/opt/iobroker/node_modules/ioredis/built/redis/index.js:636:24)
              at Redis.get (/opt/iobroker/node_modules/ioredis/built/commander.js:121:25)
              at ObjectsInRedisClient._getObject (file:///opt/iobroker/node_modules/@iobroker/db-objects-redis/src/lib/objects/objectsInRedisClient.ts:3011:37)
              at Immediate. (file:///opt/iobroker/node_modules/@iobroker/db-objects-redis/src/lib/objects/objectsInRedisClient.ts:3070:29)
              at processImmediate (node:internal/timers:485:21)
              2025-09-24 23:36:43.194 - error: zigbee.0 (310968) DB closed
              2025-09-24 23:36:43.198 - error: zigbee.0 (310968) 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:36:43.198 - error: zigbee.0 (310968) unhandled promise rejection: DB closed
              2025-09-24 23:36:43.199 - error: zigbee.0 (310968) Error: DB closed
              at Redis.sendCommand (/opt/iobroker/node_modules/ioredis/built/redis/index.js:636:24)
              at Redis.get (/opt/iobroker/node_modules/ioredis/built/commander.js:121:25)
              at ObjectsInRedisClient._getObject (file:///opt/iobroker/node_modules/@iobroker/db-objects-redis/src/lib/objects/objectsInRedisClient.ts:3011:37)
              at Immediate. (file:///opt/iobroker/node_modules/@iobroker/db-objects-redis/src/lib/objects/objectsInRedisClient.ts:3070:29)
              at processImmediate (node:internal/timers:485:21)
              2025-09-24 23:36:43.200 - error: zigbee.0 (310968) DB closed
              2025-09-24 23:36:43.203 - error: zigbee.0 (310968) 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:36:43.204 - error: zigbee.0 (310968) unhandled promise rejection: DB closed
              2025-09-24 23:36:43.205 - error: zigbee.0 (310968) Error: DB closed
              at Redis.sendCommand (/opt/iobroker/node_modules/ioredis/built/redis/index.js:636:24)
              at Redis.get (/opt/iobroker/node_modules/ioredis/built/commander.js:121:25)
              at ObjectsInRedisClient._getObject (file:///opt/iobroker/node_modules/@iobroker/db-objects-redis/src/lib/objects/objectsInRedisClient.ts:3011:37)
              at Immediate. (file:///opt/iobroker/node_modules/@iobroker/db-objects-redis/src/lib/objects/objectsInRedisClient.ts:3070:29)
              at processImmediate (node:internal/timers:485:21)
              2025-09-24 23:36:43.205 - error: zigbee.0 (310968) DB closed
              2025-09-24 23:36:43.208 - error: zigbee.0 (310968) 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:36:43.209 - error: zigbee.0 (310968) unhandled promise rejection: DB closed
              2025-09-24 23:36:43.210 - error: zigbee.0 (310968) Error: DB closed
              at Redis.sendCommand (/opt/iobroker/node_modules/ioredis/built/redis/index.js:636:24)
              at Redis.get (/opt/iobroker/node_modules/ioredis/built/commander.js:121:25)
              at ObjectsInRedisClient._getObject (file:///opt/iobroker/node_modules/@iobroker/db-objects-redis/src/lib/objects/objectsInRedisClient.ts:3011:37)
              at Immediate. (file:///opt/iobroker/node_modules/@iobroker/db-objects-redis/src/lib/objects/objectsInRedisClient.ts:3070:29)
              at processImmediate (node:internal/timers:485:21)
              2025-09-24 23:36:43.211 - error: zigbee.0 (310968) DB closed
              2025-09-24 23:36:43.214 - error: zigbee.0 (310968) 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:36:43.214 - error: zigbee.0 (310968) unhandled promise rejection: DB closed
              2025-09-24 23:36:43.215 - error: zigbee.0 (310968) Error: DB closed
              at Redis.sendCommand (/opt/iobroker/node_modules/ioredis/built/redis/index.js:636:24)
              at Redis.get (/opt/iobroker/node_modules/ioredis/built/commander.js:121:25)
              at ObjectsInRedisClient._getObject (file:///opt/iobroker/node_modules/@iobroker/db-objects-redis/src/lib/objects/objectsInRedisClient.ts:3011:37)
              at Immediate. (file:///opt/iobroker/node_modules/@iobroker/db-objects-redis/src/lib/objects/objectsInRedisClient.ts:3070:29)
              at processImmediate (node:internal/timers:485:21)
              2025-09-24 23:36:43.216 - error: zigbee.0 (310968) DB closed
              2025-09-24 23:36:43.220 - error: zigbee.0 (310968) 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:36:43.220 - error: zigbee.0 (310968) unhandled promise rejection: DB closed
              2025-09-24 23:36:43.221 - error: zigbee.0 (310968) Error: DB closed
              at Redis.sendCommand (/opt/iobroker/node_modules/ioredis/built/redis/index.js:636:24)
              at Redis.get (/opt/iobroker/node_modules/ioredis/built/commander.js:121:25)
              at ObjectsInRedisClient._getObject (file:///opt/iobroker/node_modules/@iobroker/db-objects-redis/src/lib/objects/objectsInRedisClient.ts:3011:37)
              at Immediate. (file:///opt/iobroker/node_modules/@iobroker/db-objects-redis/src/lib/objects/objectsInRedisClient.ts:3070:29)
              at processImmediate (node:internal/timers:485:21)
              
              

              ich muss Log kürzen, sonnst meckert Forum.

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

                @asgothian sagte in Tester wanted - Zigbee Adapter 3.1:

                Was genau für ein Sensor ?

                es ist verlinkt da.

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

                  @dimaiv ok, der kann es nicht sein, der hat kein on Event.
                  Dann sollte es der auf den folgende in der Liste der Geräte sein. Die müsste vorher im log stehen.

                  A.

                  P.s. damit ist für heute erst einmal Schluss. Morgen kann ich weiter machen. Zum Thema log kürzen, alles was nach DB closed oder connection closed kommt ist irrelevant.

                  A.

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

                    @asgothian

                    0x60a423fffe61dd4a - Steckdose: (https://www.zigbee2mqtt.io/devices/TS0121_plug.html)

                    0x28dba7fffe6df66f - SWV: (https://www.zigbee2mqtt.io/devices/SWV.html)

                    0x28dba7fffe6df516 - SWV: (https://www.zigbee2mqtt.io/devices/SWV.html)

                    0x28dba7fffe6df594 - SWV: (https://www.zigbee2mqtt.io/devices/SWV.html)

                    0x881a14fffeea1db2 - SWV: (https://www.zigbee2mqtt.io/devices/SWV.html)

                    0x28dba7fffe6df5f6 - SWV: (https://www.zigbee2mqtt.io/devices/SWV.html)

                    0xa4c13801838effff - Temp Sensor: (https://www.zigbee2mqtt.io/devices/SNZB-02LD.html)

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

                      Hallo,

                      ich habe mal eine allgemeine Frage zur Konfig des Adapters.
                      Bin gerade dabei den Koordinator zu ersetzen und alles neu zu machen. Nach Neuinstallation des Adapters wurde Kanal 15 eingestellt. Neben "Channel" ist ein grüner Haken. Laut Channels Energy Scan müsste man eigentlich Kanal 20 nutzen. Wenn ich den einstelle, ist anstelle des grünen Hakens ein rotes Kreuz. Was bedeutet das?
                      Der Adapter wird nach einem Neustart wieder grün. Konnte auch unter Kanal 20 einen IKEA Schalter neu anlernen.
                      Was sollte ich als Kanal einstellen, bevor ich alles neu anlerne?

                      Zigbee Channels Energy Scan 15 aktiv.png

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

                        @pk68
                        Auf welchem Kanal läuft dein WLAN und meisten von Nachbarn?

                        P 1 Reply Last reply Reply Quote 0
                        • P
                          pk68 @dimaiv last edited by

                          @dimaiv sagte in Tester wanted - Zigbee Adapter 3.1:

                          @pk68
                          Auf welchem Kanal läuft dein WLAN und meisten von Nachbarn?

                          Bei meiner Fritzbox wird der Kanal automatisch gewählt. Kann also morgen wieder anders sein. Aktuell sieht es so aus:

                          Kanalbelegung Fritzbox.png
                          WLAN Kanal 3 am Stärksten belegt. Also gleich neben Zigbee-Kanal 15. Der wäre aktuelle eher ungünstig.
                          Weißt Du, was der grünen Haken bzw. rotes Kreuz zu bedeuten hat?

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

                            @pk68 sagte in Tester wanted - Zigbee Adapter 3.1:

                            Wenn ich den einstelle, ist anstelle des grünen Hakens ein rotes Kreuz. Was bedeutet das?

                            Ein rotes X bedeutet das der gewählte Kanal nicht dem entpricht der in der nvbackup.json eingestellt ist.
                            Ein Gelbes Rufzeichen bedeutet das die Einstellung zum nvbackup.json passt, aber ein Wert ist der nicht empfohlen wird.
                            Ein grünes Zeichen bedeutet das der Wert ok ist und mit dem nvbackup übereinstimmt.

                            Keines der Zeichen gibt eine klare Aussage darüber ob das Zigbee-Subsystem starten wird oder nicht.

                            A.

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

                              @asgothian
                              Danke für die Infos. Ganz schlau werde ich daraus nicht. Wenn man einen anderen Kanal wählt, muss man dann auch die nvbackup.json bearbeiten oder wird die dann irgendwann automatisch aktualisiert?

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

                                @pk68 sagte in Tester wanted - Zigbee Adapter 3.1:

                                @asgothian
                                Danke für die Infos. Ganz schlau werde ich daraus nicht. Wenn man einen anderen Kanal wählt, muss man dann auch die nvbackup.json bearbeiten oder wird die dann irgendwann automatisch aktualisiert?

                                wenn der Adapter das Netzwerk erfolgreich aufbaut, und du dann das Netzwerk wieder anhälst wird die nvbackup.json neu geschrieben - mit den neuen Parametern.

                                A.

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

                                  @pk68
                                  Ich würde bei dir Klassiker nehmen, also 11, noch nie damit Probleme gehabt.

                                  P 1 Reply Last reply Reply Quote 0
                                  • P
                                    pk68 @dimaiv last edited by

                                    @dimaiv sagte in Tester wanted - Zigbee Adapter 3.1:

                                    @pk68
                                    Ich würde bei dir Klassiker nehmen, also 11, noch nie damit Probleme gehabt.

                                    Danke. Ich hatte bisher die 25, also am anderen Ende des Frequenzbereichs.

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

                                      @dimaiv bitte nochmal von Github installieren - jetzt sollte es gehen.

                                      A.

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

                                        @asgothian
                                        Es läuft !!! 👍
                                        Daten von Steckdosen werden aktualisiert.👍
                                        Send_payload bei SWV funktioniert wieder.👍

                                        Danke!

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

                                          @asgothian
                                          ich denke, es ist ein bug....

                                          Screenshot (322).png

                                          Hier werden die Daten nur angezeigt wenn die ankommen während die Seite auf ist, obwohl unter Objekten die Daten vorhanden sind und aktuel.
                                          Sobald man die Seite aktualisiert oder neu öffnet, steht wieder überal null, bis die Daten ankommen und das bei allen Geräten.

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

                                            @dimaiv sagte in Tester wanted - Zigbee Adapter 3.1:

                                            Sobald man die Seite aktualisiert oder neu öffnet, steht wieder überal null, bis die Daten ankommen und das bei allen Geräten

                                            Ja, da muss ich nochmal wieder dran gehen das ich die korrekten Werte bekomme. Ich hab da viel gebastelt.

                                            Aber gut zu wissen das der sendPayload beim SWV wieder geht. Der issue auf Github dazu ist von Dir ?

                                            Ansonsten gibts morgen eine -alpha-5. Mit mehr Anpassungen 🙂

                                            D 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
                                            13
                                            192
                                            5035
                                            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