Navigation

    Logo
    • Register
    • Login
    • Search
    • Recent
    • Tags
    • Unread
    • Categories
    • Unreplied
    • Popular
    • GitHub
    • Docu
    • Hilfe
    1. Home
    2. Deutsch
    3. ioBroker Allgemein
    4. Zigbee-Adapter 1.0.2 Danalock

    NEWS

    • ioBroker@Smart Living Forum Solingen, 14.06. - Agenda added

    • ioBroker goes Matter ... Matter Adapter in Stable

    • Monatsrückblick - April 2025

    Zigbee-Adapter 1.0.2 Danalock

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

      @patrick039212
      Das zeigt zumindest das der Adapter versucht das Schloss zu konfigurieren. Kannst Du bitte prüfen (ohne den Adapter neu zu starten)

      • ob nach der Nacht die Statusmeldungen vom Schloss ankommen ?
      • ob das Schloss vom ioBroker steuerbar ist ?

      Zusätzlich ist die Frage ob im Log von gestern abend / heute morgen noch weitere Einträge zum Configure auftauchen. Kannst du bitte im Log mal nach

      DeviceConfigure failed 0x000b57fffe59e779 V3-BTZB
      

      bzw.

      DeviceConfigure success 0x000b57fffe59e779 V3-BTZB
      

      suchen ?

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

        @Asgothian hallo

        ja ich nutze das Schloss
        nutze aber den offiziellen Adapter 1.2.1 da es mein Running System ist

        ich lasse mein System jeden Tag neu starten, wenn ich das DanaLock repaire funktioniert es bis zum nächsten Neustart
        über die Analyse kann ich den Status manuell abrufen, nutze ich meist über vpn wenn ich längere Montagen habe und sicher gehen will das meine Wohnung abgeschlossen ist.

        wo finde ich die gepatchte Version?

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

          @Jan-Puchta
          https://github.com/asgothian/ioBroker.zigbee

          da liegt die gepatchte version. Sie sollte dem 1.2.1 weitgehend entsprechen. Die einzige Modifikation die ich gemacht habe betrifft das erzwungene neu konfigurieren des Schlosses bei Neustart.

          A.

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

            @Asgothian
            habe die version über die katze installiert
            woran sehe ich das es die neue gepatchte ist

            nach einem reboot funktioniert es trotzdem nicht

            das steht im log

            zigbee.0	2020-10-04 13:59:37.117	error	at processTimers (internal/timers.js:492:7))
            zigbee.0	2020-10-04 13:59:37.117	error	at listOnTimeout (internal/timers.js:549:17)
            zigbee.0	2020-10-04 13:59:37.117	error	at Timeout._onTimeout (/opt/iobroker/node_modules/zigbee-herdsman/dist/utils/waitress.js:46:35)
            zigbee.0	2020-10-04 13:59:37.117	error	(3956) DeviceConfigure failed 0x000b57fffe59e847 V3-BTZB, attempt 1 (Error: Bind 0x000b57fffe59e847/1 closuresDoorLock from '0x00124b001caaaad1/1' failed (AREQ - ZDO - bindRsp after 10000ms)
            
            Asgothian 1 Reply Last reply Reply Quote 0
            • Asgothian
              Asgothian Developer @Jan Puchta last edited by

              @Jan-Puchta Abwarten.. das ist normal, da das Schloss nicht immer auf Nachrichten reagieren wird. Es sollte irgendwann eine Erfolgsmeldung zum Configure kommen.

              Erkennen kannst du das gepatcht ist wenn bem Start diese Meldung kommt:

              Starting Zigbee V3-BTZB hack...
              
              Jan Puchta 1 Reply Last reply Reply Quote 0
              • Jan Puchta
                Jan Puchta @Asgothian last edited by

                @Asgothian

                also beim ersten neustart hat es funktioniert da wird nachdem fail nochmals ein configure ausgeführt

                2020-10-04 13:59:21.308 - info: zigbee.0 (3956) starting. Version 1.2.1 in /opt/iobroker/node_modules/iobroker.zigbee, node: v12.18.4, js-controller: 3.1.6
                2020-10-04 13:59:21.543 - info: zigbee.0 (3956) Starting Zigbee V3-BTZB hack...
                2020-10-04 13:59:26.960 - info: zigbee.0 (3956) Coordinator firmware version: {"type":"zStack3x0","meta":{"transportrev":2,"product":1,"majorrel":2,"minorrel":7,"maintrel":1,"revision":20200805}}
                2020-10-04 13:59:26.977 - info: zigbee.0 (3956) Unable to disable LED, unsupported function.
                2020-10-04 13:59:26.978 - info: zigbee.0 (3956) --> transmitPower : high
                2020-10-04 13:59:27.002 - info: zigbee.0 (3956) Currently 12 devices are joined:
                2020-10-04 13:59:27.026 - info: zigbee.0 (3956) Configuring 0x000b57fffe59e847 V3-BTZB
                2020-10-04 13:59:27.041 - info: zigbee.0 (3956) 0x00158d0001ffddcf (addr 46775): SPZB0001 - Eurotronic Spirit Zigbee wireless heater thermostat (EndDevice)
                2020-10-04 13:59:27.052 - info: zigbee.0 (3956) 0x00158d000446fc53 (addr 57273): MCCGQ11LM - Xiaomi Aqara door & window contact sensor (EndDevice)
                2020-10-04 13:59:27.055 - info: zigbee.0 (3956) 0x00158d00044525e0 (addr 33793): WSDCGQ11LM - Xiaomi Aqara temperature, humidity and pressure sensor (EndDevice)
                2020-10-04 13:59:27.057 - info: zigbee.0 (3956) 0x00158d000446fbbc (addr 35744): MCCGQ11LM - Xiaomi Aqara door & window contact sensor (EndDevice)
                2020-10-04 13:59:27.059 - info: zigbee.0 (3956) 0x00158d0002424ac2 (addr 43645): SJCGQ11LM - Xiaomi Aqara water leak sensor (EndDevice)
                2020-10-04 13:59:27.062 - info: zigbee.0 (3956) 0x00158d00044afaa9 (addr 45873): WSDCGQ11LM - Xiaomi Aqara temperature, humidity and pressure sensor (EndDevice)
                2020-10-04 13:59:27.064 - info: zigbee.0 (3956) 0x00158d00044454bf (addr 39804): WSDCGQ11LM - Xiaomi Aqara temperature, humidity and pressure sensor (EndDevice)
                2020-10-04 13:59:27.067 - info: zigbee.0 (3956) 0x00158d00044452b7 (addr 14820): WSDCGQ11LM - Xiaomi Aqara temperature, humidity and pressure sensor (EndDevice)
                2020-10-04 13:59:27.068 - info: zigbee.0 (3956) 0x00158d00023ff955 (addr 17823): SJCGQ11LM - Xiaomi Aqara water leak sensor (EndDevice)
                2020-10-04 13:59:27.070 - info: zigbee.0 (3956) 0x00158d00041ce46e (addr 31466): MCCGQ11LM - Xiaomi Aqara door & window contact sensor (EndDevice)
                2020-10-04 13:59:27.072 - info: zigbee.0 (3956) 0x00158d0003f24814 (addr 58425): MCCGQ11LM - Xiaomi Aqara door & window contact sensor (EndDevice)
                2020-10-04 13:59:27.074 - info: zigbee.0 (3956) 0x000b57fffe59e847 (addr 17685): V3-BTZB - Danalock BT/ZB smartlock (EndDevice)
                2020-10-04 13:59:27.076 - info: zigbee.0 (3956) Zigbee started
                2020-10-04 13:59:37.117 - error: zigbee.0 (3956) DeviceConfigure failed 0x000b57fffe59e847 V3-BTZB, attempt 1 (Error: Bind 0x000b57fffe59e847/1 closuresDoorLock from '0x00124b001caaaad1/1' failed (AREQ - ZDO - bindRsp after 10000ms)
                at Timeout._onTimeout (/opt/iobroker/node_modules/zigbee-herdsman/dist/utils/waitress.js:46:35)
                at listOnTimeout (internal/timers.js:549:17)
                at processTimers (internal/timers.js:492:7))
                2020-10-04 13:59:42.636 - info: unifi.0 (3705) Update done
                2020-10-04 13:59:43.178 - error: unifi.0 (3705) fetchSites: Returned data is not in valid format
                2020-10-04 13:59:45.315 - info: text2command.0 (3679) processText: "🚪 Door lock"
                2020-10-04 13:59:45.323 - info: text2command.0 (3679) Control ID zigbee.0.000b57fffe59e847.lockState with : lock
                2020-10-04 13:59:45.366 - info: text2command.0 (3679) Response: wird verschlossen
                2020-10-04 13:59:56.664 - warn: readFile will not read this file (nuki-logo.png) in future versions: nuki2.admin is not an object of type "meta"
                2020-10-04 14:00:00.033 - info: host.ioBroker-Pi4 instance system.adapter.ical.0 started with pid 5330
                2020-10-04 14:00:02.375 - info: ical.0 (5330) starting. Version 1.7.4 in /opt/iobroker/node_modules/iobroker.ical, node: v12.18.4, js-controller: 3.1.6
                2020-10-04 14:00:03.449 - info: ical.0 (5330) processing URL: Mein Kalendar https://calendar.google.com/calendar/ical/middrive1978%40googlemail.com/private-1fa08408e334c7194a1cc86982a246fa/basic.ics
                2020-10-04 14:00:08.886 - info: ical.0 (5330) Terminated (NO_ERROR): Without reason
                2020-10-04 14:00:09.410 - info: host.ioBroker-Pi4 instance system.adapter.ical.0 terminated with code 0 (NO_ERROR)
                2020-10-04 14:00:18.421 - info: text2command.0 (3679) processText: "🚪 Door unlock"
                2020-10-04 14:00:18.422 - info: text2command.0 (3679) Control ID zigbee.0.000b57fffe59e847.lockState with : unlock
                2020-10-04 14:00:18.444 - info: text2command.0 (3679) Response: wird aufgeschlossen
                2020-10-04 14:00:19.233 - info: unifi.0 (3705) Update done
                2020-10-04 14:00:48.430 - info: unifi.0 (3705) Update done
                2020-10-04 14:01:19.781 - info: unifi.0 (3705) Update done
                2020-10-04 14:01:49.586 - info: unifi.0 (3705) Update done
                2020-10-04 14:02:19.420 - info: unifi.0 (3705) Update done
                2020-10-04 14:02:50.487 - info: unifi.0 (3705) Update done
                2020-10-04 14:02:59.730 - info: text2command.0 (3679) processText: "🚪 Door lock"
                2020-10-04 14:02:59.732 - info: text2command.0 (3679) Control ID zigbee.0.000b57fffe59e847.lockState with : lock
                2020-10-04 14:02:59.748 - info: text2command.0 (3679) Response: wird verschlossen
                2020-10-04 14:03:19.372 - info: text2command.0 (3679) processText: "🚪 Door unlock"
                2020-10-04 14:03:19.373 - info: text2command.0 (3679) Control ID zigbee.0.000b57fffe59e847.lockState with : unlock
                2020-10-04 14:03:19.396 - info: text2command.0 (3679) Response: wird aufgeschlossen
                2020-10-04 14:03:19.500 - info: unifi.0 (3705) Update done
                2020-10-04 14:03:31.554 - info: nut.0 (2445) Start NUT update
                2020-10-04 14:03:31.617 - info: nut.0 (2445) All Nut values set
                2020-10-04 14:03:49.199 - info: unifi.0 (3705) Update done
                2020-10-04 14:04:19.066 - info: unifi.0 (3705) Update done
                2020-10-04 14:04:42.701 - info: zigbee.0 (3956) Configuring 0x000b57fffe59e847 V3-BTZB
                ..........
                2020-10-04 14:04:47.216 - info: zigbee.0 (3956) DeviceConfigure successful 0x000b57fffe59e847 V3-BTZB
                

                beim zweiten reboot funktioniert es leider nicht mehr (das zweite configure fehlt)

                2020-10-04 14:18:37.823 - info: zigbee.0 (3943) starting. Version 1.2.1 in /opt/iobroker/node_modules/iobroker.zigbee, node: v12.18.4, js-controller: 3.1.6
                2020-10-04 14:18:38.014 - info: zigbee.0 (3943) Starting Zigbee V3-BTZB hack...
                2020-10-04 14:18:43.694 - info: zigbee.0 (3943) Coordinator firmware version: {"type":"zStack3x0","meta":{"transportrev":2,"product":1,"majorrel":2,"minorrel":7,"maintrel":1,"revision":20200805}}
                2020-10-04 14:18:43.707 - info: zigbee.0 (3943) Unable to disable LED, unsupported function.
                2020-10-04 14:18:43.708 - info: zigbee.0 (3943) --> transmitPower : high
                2020-10-04 14:18:43.724 - info: zigbee.0 (3943) Currently 12 devices are joined:
                2020-10-04 14:18:43.735 - info: zigbee.0 (3943) Configuring 0x000b57fffe59e847 V3-BTZB
                2020-10-04 14:18:43.744 - info: zigbee.0 (3943) 0x00158d0001ffddcf (addr 46775): SPZB0001 - Eurotronic Spirit Zigbee wireless heater thermostat (EndDevice)
                2020-10-04 14:18:43.749 - info: zigbee.0 (3943) 0x00158d000446fc53 (addr 57273): MCCGQ11LM - Xiaomi Aqara door & window contact sensor (EndDevice)
                2020-10-04 14:18:43.750 - info: zigbee.0 (3943) 0x00158d00044525e0 (addr 33793): WSDCGQ11LM - Xiaomi Aqara temperature, humidity and pressure sensor (EndDevice)
                2020-10-04 14:18:43.752 - info: zigbee.0 (3943) 0x00158d000446fbbc (addr 35744): MCCGQ11LM - Xiaomi Aqara door & window contact sensor (EndDevice)
                2020-10-04 14:18:43.753 - info: zigbee.0 (3943) 0x00158d0002424ac2 (addr 43645): SJCGQ11LM - Xiaomi Aqara water leak sensor (EndDevice)
                2020-10-04 14:18:43.755 - info: zigbee.0 (3943) 0x00158d00044afaa9 (addr 45873): WSDCGQ11LM - Xiaomi Aqara temperature, humidity and pressure sensor (EndDevice)
                2020-10-04 14:18:43.756 - info: zigbee.0 (3943) 0x00158d00044454bf (addr 39804): WSDCGQ11LM - Xiaomi Aqara temperature, humidity and pressure sensor (EndDevice)
                2020-10-04 14:18:43.757 - info: zigbee.0 (3943) 0x00158d00044452b7 (addr 14820): WSDCGQ11LM - Xiaomi Aqara temperature, humidity and pressure sensor (EndDevice)
                2020-10-04 14:18:43.759 - info: zigbee.0 (3943) 0x00158d00023ff955 (addr 17823): SJCGQ11LM - Xiaomi Aqara water leak sensor (EndDevice)
                2020-10-04 14:18:43.761 - info: zigbee.0 (3943) 0x00158d00041ce46e (addr 31466): MCCGQ11LM - Xiaomi Aqara door & window contact sensor (EndDevice)
                2020-10-04 14:18:43.762 - info: zigbee.0 (3943) 0x00158d0003f24814 (addr 58425): MCCGQ11LM - Xiaomi Aqara door & window contact sensor (EndDevice)
                2020-10-04 14:18:43.763 - info: zigbee.0 (3943) 0x000b57fffe59e847 (addr 17685): V3-BTZB - Danalock BT/ZB smartlock (EndDevice)
                2020-10-04 14:18:43.765 - info: zigbee.0 (3943) Zigbee started
                2020-10-04 14:18:53.783 - error: zigbee.0 (3943) DeviceConfigure failed 0x000b57fffe59e847 V3-BTZB, attempt 1 (Error: Bind 0x000b57fffe59e847/1 closuresDoorLock from '0x00124b001caaaad1/1' failed (AREQ - ZDO - bindRsp after 10000ms)
                at Timeout._onTimeout (/opt/iobroker/node_modules/zigbee-herdsman/dist/utils/waitress.js:46:35)
                at listOnTimeout (internal/timers.js:549:17)
                at processTimers (internal/timers.js:492:7))
                2020-10-04 14:18:54.491 - info: unifi.0 (3696) Update done
                2020-10-04 14:19:05.302 - info: unifi.0 (3696) Update done
                2020-10-04 14:19:35.473 - info: unifi.0 (3696) Update done
                2020-10-04 14:20:04.551 - info: unifi.0 (3696) Update done
                2020-10-04 14:20:36.116 - info: unifi.0 (3696) Update done
                2020-10-04 14:21:06.075 - info: unifi.0 (3696) Update done
                2020-10-04 14:21:35.556 - info: unifi.0 (3696) Update done
                2020-10-04 14:22:05.377 - info: unifi.0 (3696) Update done
                2020-10-04 14:22:35.347 - info: unifi.0 (3696) Update done
                2020-10-04 14:22:47.527 - info: nut.0 (2451) Start NUT update
                2020-10-04 14:22:47.634 - info: nut.0 (2451) All Nut values set
                2020-10-04 14:23:05.735 - info: unifi.0 (3696) Update done
                2020-10-04 14:23:36.556 - info: unifi.0 (3696) Update done
                2020-10-04 14:24:05.611 - info: unifi.0 (3696) Update done
                2020-10-04 14:24:35.311 - info: unifi.0 (3696) Update done
                2020-10-04 14:25:04.386 - info: unifi.0 (3696) Update done
                2020-10-04 14:25:34.351 - info: unifi.0 (3696) Update done
                2020-10-04 14:26:04.336 - info: unifi.0 (3696) Update done
                2020-10-04 14:26:34.484 - info: unifi.0 (3696) Update done
                2020-10-04 14:26:49.726 - info: text2command.0 (3670) processText: "🚪 Door unlock"
                2020-10-04 14:26:49.730 - info: text2command.0 (3670) Control ID zigbee.0.000b57fffe59e847.lockState with : unlock
                2020-10-04 14:26:49.796 - info: text2command.0 (3670) Response: wird aufgeschlossen
                2020-10-04 14:27:04.168 - info: unifi.0 (3696) Update done
                2020-10-04 14:27:34.763 - info: unifi.0 (3696) Update done
                2020-10-04 14:27:47.530 - info: nut.0 (2451) Start NUT update
                2020-10-04 14:27:47.581 - info: nut.0 (2451) All Nut values set
                2020-10-04 14:28:04.831 - info: unifi.0 (3696) Update done
                2020-10-04 14:28:34.208 - info: unifi.0 (3696) Update done
                2020-10-04 14:29:04.238 - info: unifi.0 (3696) Update done
                2020-10-04 14:29:34.677 - info: unifi.0 (3696) Update done
                2020-10-04 14:29:50.880 - info: text2command.0 (3670) processText: "🚪 Door lock"
                2020-10-04 14:29:50.881 - info: text2command.0 (3670) Control ID zigbee.0.000b57fffe59e847.lockState with : lock
                2020-10-04 14:29:50.897 - info: text2command.0 (3670) Response: wird verschlossen
                2020-10-04 14:30:00.048 - info: host.ioBroker-Pi4 instance system.adapter.ical.0 started with pid 22911
                2020-10-04 14:30:02.264 - info: ical.0 (22911) starting. Version 1.7.4 in /opt/iobroker/node_modules/iobroker.ical, node: v12.18.4, js-controller: 3.1.6
                2020-10-04 14:30:03.327 - info: ical.0 (22911) processing URL: Mein Kalendar https://calendar.google.com/calendar/ical/middrive1978%40googlemail.com/private-1fa08408e334c7194a1cc86982a246fa/basic.ics
                2020-10-04 14:30:04.948 - info: unifi.0 (3696) Update done
                2020-10-04 14:30:08.798 - info: ical.0 (22911) Terminated (NO_ERROR): Without reason
                2020-10-04 14:30:09.324 - info: host.ioBroker-Pi4 instance system.adapter.ical.0 terminated with code 0 (NO_ERROR)
                2020-10-04 14:30:34.433 - info: unifi.0 (3696) Update done
                2020-10-04 14:31:03.926 - info: unifi.0 (3696) Update done
                2020-10-04 14:31:33.925 - info: unifi.0 (3696) Update done
                2020-10-04 14:32:04.353 - info: unifi.0 (3696) Update done
                2020-10-04 14:32:33.687 - info: unifi.0 (3696) Update done
                2020-10-04 14:32:47.530 - info: nut.0 (2451) Start NUT update
                2020-10-04 14:32:47.596 - info: nut.0 (2451) All Nut values set
                2020-10-04 14:33:03.822 - info: unifi.0 (3696) Update done
                

                kannst du das erste configure später ausführen lassen
                nach dem alle clients da sind zum Beispiel

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

                  @Jan-Puchta Nein, kann ich nicht. Und auch beim 2. Neustart wird noch ein weiteres Configure versucht werden. Das ist nicht an ein festes Zeitraster gebunden.

                  ggf. kannst du durch schliessen / öffnen des Schlosses vom ioBroker aus ein Configure triggern.

                  Jan Puchta 2 Replies Last reply Reply Quote 0
                  • Jan Puchta
                    Jan Puchta @Asgothian last edited by

                    @Asgothian

                    habe rausgefunden das das 2te configure nach dem ersten reboot von mir selber über die Entwickleroption ausgelöst wurde

                    wie du im log sehen kannst habe ich das schloss geöffnet und geschlossen wird auch ausgeführt nur der status ändert sich nicht und ein configure wird nicht getriggert

                    text2command.0	2020-10-04 14:29:50.897	info	(3670) Response: wird verschlossen
                    text2command.0	2020-10-04 14:29:50.881	info	(3670) Control ID zigbee.0.000b57fffe59e847.lockState with : lock
                    text2command.0	2020-10-04 14:29:50.880	info	(3670) processText: "🚪 Door lock"
                    unifi.0	2020-10-04 14:29:34.677	info	(3696) Update done
                    unifi.0	2020-10-04 14:29:04.238	info	(3696) Update done
                    unifi.0	2020-10-04 14:28:34.208	info	(3696) Update done
                    unifi.0	2020-10-04 14:28:04.831	info	(3696) Update done
                    nut.0	2020-10-04 14:27:47.581	info	(2451) All Nut values set
                    nut.0	2020-10-04 14:27:47.530	info	(2451) Start NUT update
                    unifi.0	2020-10-04 14:27:34.763	info	(3696) Update done
                    unifi.0	2020-10-04 14:27:04.168	info	(3696) Update done
                    text2command.0	2020-10-04 14:26:49.796	info	(3670) Response: wird aufgeschlossen
                    text2command.0	2020-10-04 14:26:49.730	info	(3670) Control ID zigbee.0.000b57fffe59e847.lockState with : unlock
                    text2command.0	2020-10-04 14:26:49.726	info	(3670) processText: "🚪 Door unlock"
                    unifi.0	2020-10-04 14:26:34.484	info	(3696) Update done
                    
                    1 Reply Last reply Reply Quote 0
                    • Jan Puchta
                      Jan Puchta @Asgothian last edited by

                      @Asgothian

                      also mit Entwickleroption kann ich das configure triggern
                      mit lock oder unlock nicht

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

                        @Jan-Puchta funktioniert denn das lock oder unlock ?

                        Jan Puchta 2 Replies Last reply Reply Quote 0
                        • Jan Puchta
                          Jan Puchta @Asgothian last edited by

                          @Asgothian

                          ja lock und unlock funktionieren also schloss schließt und öffnet

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

                            @Jan-Puchta Aber die Meldungen vom Schloss kommen weiterhin nicht an, korrekt ?

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

                              @Asgothian

                              update nach mehreren probieren

                              nach einem neustart wird zwar ein configure getriggert (7) aber es failed (21)
                              danach wird kein neues getriggert

                              auch wird über unlock (27) oder lock (30) kein neues configure getriggert

                              wenn nach dem neustart über entwickler den status abfrage wird configure getriggert (34) und dann wird es auch über unlock (36,39) bzw lock (45,48)

                              2020-10-04 15:28:07.257 - info: zigbee.0 (3917) starting. Version 1.2.1 in /opt/iobroker/node_modules/iobroker.zigbee, node: v12.18.4, js-controller: 3.1.6
                              2020-10-04 15:28:07.531 - info: zigbee.0 (3917) Starting Zigbee V3-BTZB hack...
                              2020-10-04 15:28:12.911 - info: zigbee.0 (3917) Coordinator firmware version: {"type":"zStack3x0","meta":{"transportrev":2,"product":1,"majorrel":2,"minorrel":7,"maintrel":1,"revision":20200805}}
                              2020-10-04 15:28:12.924 - info: zigbee.0 (3917) Unable to disable LED, unsupported function.
                              2020-10-04 15:28:12.925 - info: zigbee.0 (3917) --> transmitPower : high
                              2020-10-04 15:28:12.938 - info: zigbee.0 (3917) Currently 12 devices are joined:
                              2020-10-04 15:28:12.949 - info: zigbee.0 (3917) Configuring 0x000b57fffe59e847 V3-BTZB
                              2020-10-04 15:28:12.965 - info: zigbee.0 (3917) 0x00158d0001ffddcf (addr 46775): SPZB0001 - Eurotronic Spirit Zigbee wireless heater thermostat (EndDevice)
                              2020-10-04 15:28:12.972 - info: zigbee.0 (3917) 0x00158d000446fc53 (addr 57273): MCCGQ11LM - Xiaomi Aqara door & window contact sensor (EndDevice)
                              2020-10-04 15:28:12.974 - info: zigbee.0 (3917) 0x00158d00044525e0 (addr 33793): WSDCGQ11LM - Xiaomi Aqara temperature, humidity and pressure sensor (EndDevice)
                              2020-10-04 15:28:12.976 - info: zigbee.0 (3917) 0x00158d000446fbbc (addr 35744): MCCGQ11LM - Xiaomi Aqara door & window contact sensor (EndDevice)
                              2020-10-04 15:28:12.978 - info: zigbee.0 (3917) 0x00158d0002424ac2 (addr 43645): SJCGQ11LM - Xiaomi Aqara water leak sensor (EndDevice)
                              2020-10-04 15:28:12.980 - info: zigbee.0 (3917) 0x00158d00044afaa9 (addr 45873): WSDCGQ11LM - Xiaomi Aqara temperature, humidity and pressure sensor (EndDevice)
                              2020-10-04 15:28:12.982 - info: zigbee.0 (3917) 0x00158d00044454bf (addr 39804): WSDCGQ11LM - Xiaomi Aqara temperature, humidity and pressure sensor (EndDevice)
                              2020-10-04 15:28:12.984 - info: zigbee.0 (3917) 0x00158d00044452b7 (addr 14820): WSDCGQ11LM - Xiaomi Aqara temperature, humidity and pressure sensor (EndDevice)
                              2020-10-04 15:28:12.986 - info: zigbee.0 (3917) 0x00158d00023ff955 (addr 17823): SJCGQ11LM - Xiaomi Aqara water leak sensor (EndDevice)
                              2020-10-04 15:28:12.988 - info: zigbee.0 (3917) 0x00158d00041ce46e (addr 31466): MCCGQ11LM - Xiaomi Aqara door & window contact sensor (EndDevice)
                              2020-10-04 15:28:12.990 - info: zigbee.0 (3917) 0x00158d0003f24814 (addr 58425): MCCGQ11LM - Xiaomi Aqara door & window contact sensor (EndDevice)
                              2020-10-04 15:28:12.993 - info: zigbee.0 (3917) 0x000b57fffe59e847 (addr 17685): V3-BTZB - Danalock BT/ZB smartlock (EndDevice)
                              2020-10-04 15:28:12.994 - info: zigbee.0 (3917) Zigbee started
                              2020-10-04 15:28:23.026 - error: zigbee.0 (3917) DeviceConfigure failed 0x000b57fffe59e847 V3-BTZB, attempt 1 (Error: Bind 0x000b57fffe59e847/1 closuresDoorLock from '0x00124b001caaaad1/1' failed (AREQ - ZDO - bindRsp after 10000ms)
                              at Timeout._onTimeout (/opt/iobroker/node_modules/zigbee-herdsman/dist/utils/waitress.js:46:35)
                              at listOnTimeout (internal/timers.js:549:17)
                              at processTimers (internal/timers.js:492:7))
                              2020-10-04 15:28:26.236 - info: unifi.0 (3670) Update done
                              2020-10-04 15:28:33.722 - info: unifi.0 (3670) Update done
                              2020-10-04 15:28:45.352 - info: text2command.0 (3644) processText: "🚪 Door unlock"
                              2020-10-04 15:28:45.355 - info: text2command.0 (3644) Control ID zigbee.0.000b57fffe59e847.lockState with : unlock
                              2020-10-04 15:28:45.390 - info: text2command.0 (3644) Response: wird aufgeschlossen
                              2020-10-04 15:29:01.071 - info: text2command.0 (3644) processText: "🚪 Door lock"
                              2020-10-04 15:29:01.072 - info: text2command.0 (3644) Control ID zigbee.0.000b57fffe59e847.lockState with : lock
                              2020-10-04 15:29:01.121 - info: text2command.0 (3644) Response: wird verschlossen
                              2020-10-04 15:29:04.437 - info: unifi.0 (3670) Update done
                              2020-10-04 15:29:15.068 - info: zigbee.0 (3917) Configuring 0x000b57fffe59e847 V3-BTZB
                              2020-10-04 15:29:20.096 - info: zigbee.0 (3917) DeviceConfigure successful 0x000b57fffe59e847 V3-BTZB
                              2020-10-04 15:29:24.220 - info: text2command.0 (3644) processText: "🚪 Door unlock"
                              2020-10-04 15:29:24.221 - info: text2command.0 (3644) Control ID zigbee.0.000b57fffe59e847.lockState with : unlock
                              2020-10-04 15:29:24.239 - info: text2command.0 (3644) Response: wird aufgeschlossen
                              2020-10-04 15:29:32.277 - info: zigbee.0 (3917) Configuring 0x000b57fffe59e847 V3-BTZB
                              ............
                              2020-10-04 15:29:38.286 - info: zigbee.0 (3917) DeviceConfigure successful 0x000b57fffe59e847 V3-BTZB
                              2020-10-04 15:36:05.255 - info: unifi.0 (3670) Update done
                              2020-10-04 15:36:33.756 - info: unifi.0 (3670) Update done
                              2020-10-04 15:37:03.802 - info: unifi.0 (3670) Update done
                              2020-10-04 15:37:09.665 - info: text2command.0 (3644) processText: "🚪 Door lock"
                              2020-10-04 15:37:09.666 - info: text2command.0 (3644) Control ID zigbee.0.000b57fffe59e847.lockState with : lock
                              2020-10-04 15:37:09.684 - info: text2command.0 (3644) Response: wird verschlossen
                              2020-10-04 15:37:14.861 - info: zigbee.0 (3917) Configuring 0x000b57fffe59e847 V3-BTZB
                              2020-10-04 15:37:16.913 - info: nut.0 (2425) Start NUT update
                              2020-10-04 15:37:16.961 - info: nut.0 (2425) All Nut values set
                              2020-10-04 15:37:21.382 - info: zigbee.0 (3917) DeviceConfigure successful 0x000b57fffe59e847 V3-BTZB
                              
                              1 Reply Last reply Reply Quote 0
                              • Jan Puchta
                                Jan Puchta @Asgothian last edited by

                                @Asgothian

                                noch ein update

                                ungefähr eine halbe stunde nach dem reboot wurde automatisch ein configure getriggert

                                2020-10-04 15:28:07.257 - info: zigbee.0 (3917) starting. Version 1.2.1 in /opt/iobroker/node_modules/iobroker.zigbee, node: v12.18.4, js-controller: 3.1.6
                                2020-10-04 15:28:07.531 - info: zigbee.0 (3917) Starting Zigbee V3-BTZB hack...
                                2020-10-04 15:28:12.911 - info: zigbee.0 (3917) Coordinator firmware version: {"type":"zStack3x0","meta":{"transportrev":2,"product":1,"majorrel":2,"minorrel":7,"maintrel":1,"revision":20200805}}
                                2020-10-04 15:28:12.924 - info: zigbee.0 (3917) Unable to disable LED, unsupported function.
                                2020-10-04 15:28:12.925 - info: zigbee.0 (3917) --> transmitPower : high
                                2020-10-04 15:28:12.938 - info: zigbee.0 (3917) Currently 12 devices are joined:
                                2020-10-04 15:28:12.949 - info: zigbee.0 (3917) Configuring 0x000b57fffe59e847 V3-BTZB
                                2020-10-04 15:28:12.965 - info: zigbee.0 (3917) 0x00158d0001ffddcf (addr 46775): SPZB0001 - Eurotronic Spirit Zigbee wireless heater thermostat (EndDevice)
                                2020-10-04 15:28:12.972 - info: zigbee.0 (3917) 0x00158d000446fc53 (addr 57273): MCCGQ11LM - Xiaomi Aqara door & window contact sensor (EndDevice)
                                2020-10-04 15:28:12.974 - info: zigbee.0 (3917) 0x00158d00044525e0 (addr 33793): WSDCGQ11LM - Xiaomi Aqara temperature, humidity and pressure sensor (EndDevice)
                                2020-10-04 15:28:12.976 - info: zigbee.0 (3917) 0x00158d000446fbbc (addr 35744): MCCGQ11LM - Xiaomi Aqara door & window contact sensor (EndDevice)
                                2020-10-04 15:28:12.978 - info: zigbee.0 (3917) 0x00158d0002424ac2 (addr 43645): SJCGQ11LM - Xiaomi Aqara water leak sensor (EndDevice)
                                2020-10-04 15:28:12.980 - info: zigbee.0 (3917) 0x00158d00044afaa9 (addr 45873): WSDCGQ11LM - Xiaomi Aqara temperature, humidity and pressure sensor (EndDevice)
                                2020-10-04 15:28:12.982 - info: zigbee.0 (3917) 0x00158d00044454bf (addr 39804): WSDCGQ11LM - Xiaomi Aqara temperature, humidity and pressure sensor (EndDevice)
                                2020-10-04 15:28:12.984 - info: zigbee.0 (3917) 0x00158d00044452b7 (addr 14820): WSDCGQ11LM - Xiaomi Aqara temperature, humidity and pressure sensor (EndDevice)
                                2020-10-04 15:28:12.986 - info: zigbee.0 (3917) 0x00158d00023ff955 (addr 17823): SJCGQ11LM - Xiaomi Aqara water leak sensor (EndDevice)
                                2020-10-04 15:28:12.988 - info: zigbee.0 (3917) 0x00158d00041ce46e (addr 31466): MCCGQ11LM - Xiaomi Aqara door & window contact sensor (EndDevice)
                                2020-10-04 15:28:12.990 - info: zigbee.0 (3917) 0x00158d0003f24814 (addr 58425): MCCGQ11LM - Xiaomi Aqara door & window contact sensor (EndDevice)
                                2020-10-04 15:28:12.993 - info: zigbee.0 (3917) 0x000b57fffe59e847 (addr 17685): V3-BTZB - Danalock BT/ZB smartlock (EndDevice)
                                2020-10-04 15:28:12.994 - info: zigbee.0 (3917) Zigbee started
                                2020-10-04 15:28:23.026 - error: zigbee.0 (3917) DeviceConfigure failed 0x000b57fffe59e847 V3-BTZB, attempt 1 (Error: Bind 0x000b57fffe59e847/1 closuresDoorLock from '0x00124b001caaaad1/1' failed (AREQ - ZDO - bindRsp after 10000ms)
                                at Timeout._onTimeout (/opt/iobroker/node_modules/zigbee-herdsman/dist/utils/waitress.js:46:35)
                                at listOnTimeout (internal/timers.js:549:17)
                                at processTimers (internal/timers.js:492:7))
                                .........
                                zigbee.0	2020-10-04 16:02:25.936	info	(3917) Configuring 0x000b57fffe59e847 V3-BTZB
                                zigbee.0	2020-10-04 16:02:31.476	info	(3917) DeviceConfigure successful 0x000b57fffe59e847 V3-BTZB
                                
                                Asgothian 1 Reply Last reply Reply Quote 0
                                • Asgothian
                                  Asgothian Developer @Jan Puchta last edited by

                                  @Jan-Puchta
                                  Fein.. Jetzt die Schlüsselfrage: Kommen jetzt die Meldungen vom Schloss an wenn du am Schloss auf/zu schliesst ?

                                  A.

                                  Jan Puchta 3 Replies Last reply Reply Quote 0
                                  • Jan Puchta
                                    Jan Puchta @Asgothian last edited by

                                    @Asgothian

                                    ja kommen sie

                                    das das erste configure nach dem neustart nicht funktioniert wird das problem sein

                                    ich starte noch einmal durch und mache garnichts
                                    werde mal abwarten wann das erste funktionierende configure durchläuft

                                    gebe es dann durch

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

                                      @Asgothian

                                      update

                                      die zeit scheint für das erste funktionierende configure unterschiedlich zu sein
                                      jetzt wurde nach 25 minuten nach dem neustart gleich dreimal das configure getriggert
                                      nächstes configure wurde ca. 15 min später getriggert

                                      also scheint es zu funktionieren leider halt nicht direkt nach dem neustart
                                      werde meinen Neustart in eine Zeit verlegen wo kein kommen und gehen statt finden sollte

                                      vielen Dank

                                      2020-10-04 16:21:01.757 - info: zigbee.0 (4007) starting. Version 1.2.1 in /opt/iobroker/node_modules/iobroker.zigbee, node: v12.18.4, js-controller: 3.1.6
                                      2020-10-04 16:21:01.910 - info: zigbee.0 (4007) Starting Zigbee V3-BTZB hack...
                                      2020-10-04 16:21:07.557 - info: zigbee.0 (4007) Coordinator firmware version: {"type":"zStack3x0","meta":{"transportrev":2,"product":1,"majorrel":2,"minorrel":7,"maintrel":1,"revision":20200805}}
                                      2020-10-04 16:21:07.582 - info: zigbee.0 (4007) Unable to disable LED, unsupported function.
                                      2020-10-04 16:21:07.583 - info: zigbee.0 (4007) --> transmitPower : high
                                      2020-10-04 16:21:07.607 - info: zigbee.0 (4007) Currently 12 devices are joined:
                                      2020-10-04 16:21:07.620 - info: zigbee.0 (4007) Configuring 0x000b57fffe59e847 V3-BTZB
                                      2020-10-04 16:21:07.630 - info: zigbee.0 (4007) 0x00158d0001ffddcf (addr 46775): SPZB0001 - Eurotronic Spirit Zigbee wireless heater thermostat (EndDevice)
                                      2020-10-04 16:21:07.637 - info: zigbee.0 (4007) 0x00158d000446fc53 (addr 57273): MCCGQ11LM - Xiaomi Aqara door & window contact sensor (EndDevice)
                                      2020-10-04 16:21:07.639 - info: zigbee.0 (4007) 0x00158d00044525e0 (addr 33793): WSDCGQ11LM - Xiaomi Aqara temperature, humidity and pressure sensor (EndDevice)
                                      2020-10-04 16:21:07.641 - info: zigbee.0 (4007) 0x00158d000446fbbc (addr 35744): MCCGQ11LM - Xiaomi Aqara door & window contact sensor (EndDevice)
                                      2020-10-04 16:21:07.642 - info: zigbee.0 (4007) 0x00158d0002424ac2 (addr 43645): SJCGQ11LM - Xiaomi Aqara water leak sensor (EndDevice)
                                      2020-10-04 16:21:07.644 - info: zigbee.0 (4007) 0x00158d00044afaa9 (addr 45873): WSDCGQ11LM - Xiaomi Aqara temperature, humidity and pressure sensor (EndDevice)
                                      2020-10-04 16:21:07.646 - info: zigbee.0 (4007) 0x00158d00044454bf (addr 39804): WSDCGQ11LM - Xiaomi Aqara temperature, humidity and pressure sensor (EndDevice)
                                      2020-10-04 16:21:07.648 - info: zigbee.0 (4007) 0x00158d00044452b7 (addr 14820): WSDCGQ11LM - Xiaomi Aqara temperature, humidity and pressure sensor (EndDevice)
                                      2020-10-04 16:21:07.650 - info: zigbee.0 (4007) 0x00158d00023ff955 (addr 17823): SJCGQ11LM - Xiaomi Aqara water leak sensor (EndDevice)
                                      2020-10-04 16:21:07.652 - info: zigbee.0 (4007) 0x00158d00041ce46e (addr 31466): MCCGQ11LM - Xiaomi Aqara door & window contact sensor (EndDevice)
                                      2020-10-04 16:21:07.654 - info: zigbee.0 (4007) 0x00158d0003f24814 (addr 58425): MCCGQ11LM - Xiaomi Aqara door & window contact sensor (EndDevice)
                                      2020-10-04 16:21:07.655 - info: zigbee.0 (4007) 0x000b57fffe59e847 (addr 17685): V3-BTZB - Danalock BT/ZB smartlock (EndDevice)
                                      2020-10-04 16:21:07.657 - info: zigbee.0 (4007) Zigbee started
                                      2020-10-04 16:21:17.680 - error: zigbee.0 (4007) DeviceConfigure failed 0x000b57fffe59e847 V3-BTZB, attempt 1 (Error: Bind 0x000b57fffe59e847/1 closuresDoorLock from '0x00124b001caaaad1/1' failed (AREQ - ZDO - bindRsp after 10000ms) at Timeout._onTimeout (/opt/iobroker/node_modules/zigbee-herdsman/dist/utils/waitress.js:46:35) at listOnTimeout (internal/timers.js:549:17) at processTimers (internal/timers.js:492:7))
                                      ............
                                      2020-10-04 16:45:23.868 - info: zigbee.0 (4007) Configuring 0x000b57fffe59e847 V3-BTZB
                                      2020-10-04 16:45:28.827 - info: zigbee.0 (4007) DeviceConfigure successful 0x000b57fffe59e847 V3-BTZB
                                      2020-10-04 16:45:29.206 - info: unifi.0 (3755) Update done
                                      2020-10-04 16:45:29.874 - info: zigbee.0 (4007) Configuring 0x000b57fffe59e847 V3-BTZB
                                      2020-10-04 16:45:35.317 - info: zigbee.0 (4007) DeviceConfigure successful 0x000b57fffe59e847 V3-BTZB
                                      2020-10-04 16:45:35.875 - info: zigbee.0 (4007) Configuring 0x000b57fffe59e847 V3-BTZB
                                      2020-10-04 16:45:42.864 - info: zigbee.0 (4007) DeviceConfigure successful 0x000b57fffe59e847 V3-BTZB
                                      2020-10-04 16:45:59.064 - info: unifi.0 (3755) Update done
                                      .............
                                      2020-10-04 17:02:25.762 - info: zigbee.0 (4007) Configuring 0x000b57fffe59e847 V3-BTZB
                                      2020-10-04 17:02:30.754 - info: zigbee.0 (4007) DeviceConfigure successful 0x000b57fffe59e847 V3-BTZB
                                      
                                      P 1 Reply Last reply Reply Quote 0
                                      • P
                                        patrick039212 @Jan Puchta last edited by patrick039212

                                        starte den adapter neu, neues log kommt dann morgen hatte leider ein kleines problem heute

                                        Wenn ich die Tür öffne wird der Status derzeit im Iobroker geändert, über iobroker kann ich das schloss weder öffnen noch schließen

                                        2020-10-04 21:14:24.892 - error: zigbee.0 (12413) Error on send command to 0x000b57fffe59e779. Error: Error: Command 0x000b57fffe59e779/1 closuresDoorLock.unlockDoor({"pincodevalue":""}, {"timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":true,"direction":0,"srcEndpoint":null,"reservedBits":0,"manufacturerCode":null,"transactionSequenceNumber":null}) failed (no response received)
                                        P 1 Reply Last reply Reply Quote 0
                                        • P
                                          patrick039212 @patrick039212 last edited by

                                          @Asgothian
                                          soeben getestet wieder die gleiche Fehlermeldung, Status ändert sich nur wenn ich die Tür selbst aufsperre via Iobroker passiert nichts keine Öffnung o.ä.

                                          Log-File kann ich gegen 17 Uhr posten, kann die Logs nicht über iobroker.pro downloaden ...

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

                                            @Asgothian

                                            hallo und Entschuldigung wenn ich wieder nerve

                                            leider war meine Freude von gestern zu früh

                                            nach dem gestrigen Neustart wurde bis auf das erste configure ca. alle eine Stunde ein configure getriggert welches auch funktionerte (Success)
                                            bis zum heutigen automatischen Reboot, da wurde leider kein configure ausgeführt,
                                            auch keine 1h später
                                            erst ca 2h später habe ich manuell über vpn wieder über Analyse den Status aktuallisiert und somit ein configure getriggert

                                            kannst du mir sagen was ich bei blockly bzw. javascript eingeben muss damit ich das configure manuell triggern kann?

                                            2020-10-04 16:21:01.757 - info: zigbee.0 (4007) starting. Version 1.2.1 in /opt/iobroker/node_modules/iobroker.zigbee, node: v12.18.4, js-controller: 3.1.6
                                            2020-10-04 16:21:01.910 - info: zigbee.0 (4007) Starting Zigbee V3-BTZB hack...
                                            2020-10-04 16:21:07.557 - info: zigbee.0 (4007) Coordinator firmware version: {"type":"zStack3x0","meta":{"transportrev":2,"product":1,"majorrel":2,"minorrel":7,"maintrel":1,"revision":20200805}}
                                            2020-10-04 16:21:07.582 - info: zigbee.0 (4007) Unable to disable LED, unsupported function.
                                            2020-10-04 16:21:07.583 - info: zigbee.0 (4007) --> transmitPower : high
                                            2020-10-04 16:21:07.607 - info: zigbee.0 (4007) Currently 12 devices are joined:
                                            2020-10-04 16:21:07.620 - info: zigbee.0 (4007) Configuring 0x000b57fffe59e847 V3-BTZB
                                            2020-10-04 16:21:07.630 - info: zigbee.0 (4007) 0x00158d0001ffddcf (addr 46775): SPZB0001 - Eurotronic Spirit Zigbee wireless heater thermostat (EndDevice)
                                            2020-10-04 16:21:07.637 - info: zigbee.0 (4007) 0x00158d000446fc53 (addr 57273): MCCGQ11LM - Xiaomi Aqara door & window contact sensor (EndDevice)
                                            2020-10-04 16:21:07.639 - info: zigbee.0 (4007) 0x00158d00044525e0 (addr 33793): WSDCGQ11LM - Xiaomi Aqara temperature, humidity and pressure sensor (EndDevice)
                                            2020-10-04 16:21:07.641 - info: zigbee.0 (4007) 0x00158d000446fbbc (addr 35744): MCCGQ11LM - Xiaomi Aqara door & window contact sensor (EndDevice)
                                            2020-10-04 16:21:07.642 - info: zigbee.0 (4007) 0x00158d0002424ac2 (addr 43645): SJCGQ11LM - Xiaomi Aqara water leak sensor (EndDevice)
                                            2020-10-04 16:21:07.644 - info: zigbee.0 (4007) 0x00158d00044afaa9 (addr 45873): WSDCGQ11LM - Xiaomi Aqara temperature, humidity and pressure sensor (EndDevice)
                                            2020-10-04 16:21:07.646 - info: zigbee.0 (4007) 0x00158d00044454bf (addr 39804): WSDCGQ11LM - Xiaomi Aqara temperature, humidity and pressure sensor (EndDevice)
                                            2020-10-04 16:21:07.648 - info: zigbee.0 (4007) 0x00158d00044452b7 (addr 14820): WSDCGQ11LM - Xiaomi Aqara temperature, humidity and pressure sensor (EndDevice)
                                            2020-10-04 16:21:07.650 - info: zigbee.0 (4007) 0x00158d00023ff955 (addr 17823): SJCGQ11LM - Xiaomi Aqara water leak sensor (EndDevice)
                                            2020-10-04 16:21:07.652 - info: zigbee.0 (4007) 0x00158d00041ce46e (addr 31466): MCCGQ11LM - Xiaomi Aqara door & window contact sensor (EndDevice)
                                            2020-10-04 16:21:07.654 - info: zigbee.0 (4007) 0x00158d0003f24814 (addr 58425): MCCGQ11LM - Xiaomi Aqara door & window contact sensor (EndDevice)
                                            2020-10-04 16:21:07.655 - info: zigbee.0 (4007) 0x000b57fffe59e847 (addr 17685): V3-BTZB - Danalock BT/ZB smartlock (EndDevice)
                                            2020-10-04 16:21:07.657 - info: zigbee.0 (4007) Zigbee started
                                            2020-10-04 16:21:17.680 - error: zigbee.0 (4007) DeviceConfigure failed 0x000b57fffe59e847 V3-BTZB, attempt 1 (Error: Bind 0x000b57fffe59e847/1 closuresDoorLock from '0x00124b001caaaad1/1' failed (AREQ - ZDO - bindRsp after 10000ms) at Timeout._onTimeout (/opt/iobroker/node_modules/zigbee-herdsman/dist/utils/waitress.js:46:35) at listOnTimeout (internal/timers.js:549:17) at processTimers (internal/timers.js:492:7))
                                            .............
                                            2020-10-04 16:45:23.868 - info: zigbee.0 (4007) Configuring 0x000b57fffe59e847 V3-BTZB
                                            2020-10-04 16:45:28.827 - info: zigbee.0 (4007) DeviceConfigure successful 0x000b57fffe59e847 V3-BTZB
                                            ..............
                                            2020-10-04 16:45:29.874 - info: zigbee.0 (4007) Configuring 0x000b57fffe59e847 V3-BTZB
                                            2020-10-04 16:45:35.317 - info: zigbee.0 (4007) DeviceConfigure successful 0x000b57fffe59e847 V3-BTZB
                                            2020-10-04 16:45:35.875 - info: zigbee.0 (4007) Configuring 0x000b57fffe59e847 V3-BTZB
                                            2020-10-04 16:45:42.864 - info: zigbee.0 (4007) DeviceConfigure successful 0x000b57fffe59e847 V3-BTZB
                                            .............
                                            2020-10-04 17:02:25.762 - info: zigbee.0 (4007) Configuring 0x000b57fffe59e847 V3-BTZB
                                            2020-10-04 17:02:30.754 - info: zigbee.0 (4007) DeviceConfigure successful 0x000b57fffe59e847 V3-BTZB
                                            .............
                                            2020-10-04 17:14:05.928 - info: zigbee.0 (4007) Configuring 0x000b57fffe59e847 V3-BTZB
                                            2020-10-04 17:14:10.955 - info: zigbee.0 (4007) DeviceConfigure successful 0x000b57fffe59e847 V3-BTZB
                                            .................
                                            2020-10-04 18:14:05.212 - info: zigbee.0 (4007) Configuring 0x000b57fffe59e847 V3-BTZB
                                            2020-10-04 18:14:10.232 - info: zigbee.0 (4007) DeviceConfigure successful 0x000b57fffe59e847 V3-BTZB
                                            ................
                                            2020-10-04 18:19:27.187 - info: zigbee.0 (4007) Configuring 0x000b57fffe59e847 V3-BTZB
                                            2020-10-04 18:19:35.707 - info: zigbee.0 (4007) DeviceConfigure successful 0x000b57fffe59e847 V3-BTZB
                                            2020-10-04 18:19:36.729 - info: zigbee.0 (4007) Configuring 0x000b57fffe59e847 V3-BTZB
                                            2020-10-04 18:19:42.726 - info: zigbee.0 (4007) DeviceConfigure successful 0x000b57fffe59e847 V3-BTZB
                                            ...............
                                            2020-10-04 18:26:59.387 - info: zigbee.0 (4007) Configuring 0x000b57fffe59e847 V3-BTZB
                                            2020-10-04 18:27:05.906 - info: zigbee.0 (4007) DeviceConfigure successful 0x000b57fffe59e847 V3-BTZB
                                            2020-10-04 18:27:22.444 - info: zigbee.0 (4007) Configuring 0x000b57fffe59e847 V3-BTZB
                                            2020-10-04 18:27:28.963 - info: zigbee.0 (4007) DeviceConfigure successful 0x000b57fffe59e847 V3-BTZB
                                            ...............
                                            2020-10-04 18:58:05.581 - info: zigbee.0 (4007) Configuring 0x000b57fffe59e847 V3-BTZB
                                            2020-10-04 18:58:09.385 - info: javascript.0 (2140) script.js.Heimüberwachung_Alarmanlage_An_Aus: telegram: 
                                            2020-10-04 18:58:11.597 - info: zigbee.0 (4007) DeviceConfigure successful 0x000b57fffe59e847 V3-BTZB
                                            2020-10-04 18:58:27.606 - info: zigbee.0 (4007) Configuring 0x000b57fffe59e847 V3-BTZB
                                            2020-10-04 18:58:33.186 - info: zigbee.0 (4007) DeviceConfigure successful 0x000b57fffe59e847 V3-BTZB
                                            .............
                                            2020-10-04 19:19:26.380 - info: zigbee.0 (4007) Configuring 0x000b57fffe59e847 V3-BTZB
                                            2020-10-04 19:19:31.413 - info: zigbee.0 (4007) DeviceConfigure successful 0x000b57fffe59e847 V3-BTZB
                                            ................
                                            2020-10-04 19:58:26.814 - info: zigbee.0 (4007) Configuring 0x000b57fffe59e847 V3-BTZB
                                            2020-10-04 19:58:31.840 - info: zigbee.0 (4007) DeviceConfigure successful 0x000b57fffe59e847 V3-BTZB
                                            ................
                                            2020-10-04 20:58:26.078 - info: zigbee.0 (4007) Configuring 0x000b57fffe59e847 V3-BTZB
                                            2020-10-04 20:58:31.616 - info: zigbee.0 (4007) DeviceConfigure successful 0x000b57fffe59e847 V3-BTZB
                                            ...............
                                            2020-10-04 21:58:25.359 - info: zigbee.0 (4007) Configuring 0x000b57fffe59e847 V3-BTZB
                                            2020-10-04 21:58:30.889 - info: zigbee.0 (4007) DeviceConfigure successful 0x000b57fffe59e847 V3-BTZB
                                            .............
                                            2020-10-04 22:58:24.652 - info: zigbee.0 (4007) Configuring 0x000b57fffe59e847 V3-BTZB
                                            2020-10-04 22:58:29.678 - info: zigbee.0 (4007) DeviceConfigure successful 0x000b57fffe59e847 V3-BTZB
                                            ...............
                                            2020-10-04 23:58:23.963 - info: zigbee.0 (4007) Configuring 0x000b57fffe59e847 V3-BTZB
                                            2020-10-04 23:58:28.996 - info: zigbee.0 (4007) DeviceConfigure successful 0x000b57fffe59e847 V3-BTZB
                                            ..................
                                            2020-10-05 00:58:23.279 - info: zigbee.0 (4007) Configuring 0x000b57fffe59e847 V3-BTZB
                                            2020-10-05 00:58:28.309 - info: zigbee.0 (4007) DeviceConfigure successful 0x000b57fffe59e847 V3-BTZB
                                            ..................
                                            2020-10-05 01:58:22.648 - info: zigbee.0 (4007) Configuring 0x000b57fffe59e847 V3-BTZB
                                            2020-10-05 01:58:27.668 - info: zigbee.0 (4007) DeviceConfigure successful 0x000b57fffe59e847 V3-BTZB
                                            ..................
                                            2020-10-05 02:58:21.994 - info: zigbee.0 (4007) Configuring 0x000b57fffe59e847 V3-BTZB
                                            2020-10-05 02:58:27.012 - info: zigbee.0 (4007) DeviceConfigure successful 0x000b57fffe59e847 V3-BTZB
                                            ...........
                                            2020-10-05 03:58:21.384 - info: zigbee.0 (4007) Configuring 0x000b57fffe59e847 V3-BTZB
                                            2020-10-05 03:58:26.412 - info: zigbee.0 (4007) DeviceConfigure successful 0x000b57fffe59e847 V3-BTZB
                                            ...........
                                            2020-10-05 04:58:20.790 - info: zigbee.0 (4007) Configuring 0x000b57fffe59e847 V3-BTZB
                                            2020-10-05 04:58:25.821 - info: zigbee.0 (4007) DeviceConfigure successful 0x000b57fffe59e847 V3-BTZB
                                            .............
                                            2020-10-05 05:45:14.704 - info: zigbee.0 (4007) Configuring 0x000b57fffe59e847 V3-BTZB
                                            2020-10-05 05:45:22.746 - info: zigbee.0 (4007) DeviceConfigure successful 0x000b57fffe59e847 V3-BTZB
                                            >>>>>manuell getriggert zum auf Arbeit gehen
                                            2020-10-05 06:11:54.330 - info: zigbee.0 (4007) Configuring 0x000b57fffe59e847 V3-BTZB
                                            2020-10-05 06:12:00.866 - info: zigbee.0 (4007) DeviceConfigure successful 0x000b57fffe59e847 V3-BTZB
                                            >>>>>>>>manuell getriggert Wohnung verlassen
                                            2020-10-05 06:45:14.031 - info: zigbee.0 (4007) Configuring 0x000b57fffe59e847 V3-BTZB
                                            2020-10-05 06:45:19.054 - info: zigbee.0 (4007) DeviceConfigure successful 0x000b57fffe59e847 V3-BTZB
                                            .............
                                            2020-10-05 07:11:53.641 - info: zigbee.0 (4007) Configuring 0x000b57fffe59e847 V3-BTZB
                                            2020-10-05 07:11:58.667 - info: zigbee.0 (4007) DeviceConfigure successful 0x000b57fffe59e847 V3-BTZB
                                            .................
                                            2020-10-05 08:11:53.002 - info: zigbee.0 (4007) Configuring 0x000b57fffe59e847 V3-BTZB
                                            2020-10-05 08:11:59.024 - info: zigbee.0 (4007) DeviceConfigure successful 0x000b57fffe59e847 V3-BTZB
                                            ..................
                                            2020-10-05 09:11:52.345 - info: zigbee.0 (4007) Configuring 0x000b57fffe59e847 V3-BTZB
                                            2020-10-05 09:11:57.363 - info: zigbee.0 (4007) DeviceConfigure successful 0x000b57fffe59e847 V3-BTZB
                                            ...............
                                            2020-10-05 10:11:51.683 - info: zigbee.0 (4007) Configuring 0x000b57fffe59e847 V3-BTZB
                                            2020-10-05 10:11:56.720 - info: zigbee.0 (4007) DeviceConfigure successful 0x000b57fffe59e847 V3-BTZB
                                            .........
                                            2020-10-05 11:11:51.028 - info: zigbee.0 (4007) Configuring 0x000b57fffe59e847 V3-BTZB
                                            2020-10-05 11:11:56.081 - info: zigbee.0 (4007) DeviceConfigure successful 0x000b57fffe59e847 V3-BTZB
                                            ..............
                                            2020-10-05 12:11:50.350 - info: zigbee.0 (4007) Configuring 0x000b57fffe59e847 V3-BTZB
                                            2020-10-05 12:11:55.373 - info: zigbee.0 (4007) DeviceConfigure successful 0x000b57fffe59e847 V3-BTZB
                                            .....................
                                            2020-10-05 13:02:38.820 - info: zigbee.0 (4009) starting. Version 1.2.1 in /opt/iobroker/node_modules/iobroker.zigbee, node: v12.18.4, js-controller: 3.1.6
                                            2020-10-05 13:02:38.974 - info: zigbee.0 (4009) Starting Zigbee V3-BTZB hack...
                                            2020-10-05 13:02:44.116 - info: zigbee.0 (4009) Coordinator firmware version: {"type":"zStack3x0","meta":{"transportrev":2,"product":1,"majorrel":2,"minorrel":7,"maintrel":1,"revision":20200805}}
                                            2020-10-05 13:02:44.128 - info: zigbee.0 (4009) Unable to disable LED, unsupported function.
                                            2020-10-05 13:02:44.129 - info: zigbee.0 (4009) --> transmitPower : high
                                            2020-10-05 13:02:44.144 - info: zigbee.0 (4009) Currently 12 devices are joined:
                                            2020-10-05 13:02:44.171 - info: zigbee.0 (4009) Configuring 0x000b57fffe59e847 V3-BTZB
                                            2020-10-05 13:02:44.192 - info: zigbee.0 (4009) 0x00158d0001ffddcf (addr 46775): SPZB0001 - Eurotronic Spirit Zigbee wireless heater thermostat (EndDevice)
                                            2020-10-05 13:02:44.203 - info: zigbee.0 (4009) 0x00158d000446fc53 (addr 57273): MCCGQ11LM - Xiaomi Aqara door & window contact sensor (EndDevice)
                                            2020-10-05 13:02:44.208 - info: zigbee.0 (4009) 0x00158d00044525e0 (addr 33793): WSDCGQ11LM - Xiaomi Aqara temperature, humidity and pressure sensor (EndDevice)
                                            2020-10-05 13:02:44.210 - info: zigbee.0 (4009) 0x00158d000446fbbc (addr 35744): MCCGQ11LM - Xiaomi Aqara door & window contact sensor (EndDevice)
                                            2020-10-05 13:02:44.212 - info: zigbee.0 (4009) 0x00158d0002424ac2 (addr 43645): SJCGQ11LM - Xiaomi Aqara water leak sensor (EndDevice)
                                            2020-10-05 13:02:44.216 - info: zigbee.0 (4009) 0x00158d00044afaa9 (addr 45873): WSDCGQ11LM - Xiaomi Aqara temperature, humidity and pressure sensor (EndDevice)
                                            2020-10-05 13:02:44.220 - info: zigbee.0 (4009) 0x00158d00044454bf (addr 39804): WSDCGQ11LM - Xiaomi Aqara temperature, humidity and pressure sensor (EndDevice)
                                            2020-10-05 13:02:44.222 - info: zigbee.0 (4009) 0x00158d00044452b7 (addr 14820): WSDCGQ11LM - Xiaomi Aqara temperature, humidity and pressure sensor (EndDevice)
                                            2020-10-05 13:02:44.225 - info: zigbee.0 (4009) 0x00158d00023ff955 (addr 17823): SJCGQ11LM - Xiaomi Aqara water leak sensor (EndDevice)
                                            2020-10-05 13:02:44.230 - info: zigbee.0 (4009) 0x00158d00041ce46e (addr 31466): MCCGQ11LM - Xiaomi Aqara door & window contact sensor (EndDevice)
                                            2020-10-05 13:02:44.232 - info: zigbee.0 (4009) 0x00158d0003f24814 (addr 58425): MCCGQ11LM - Xiaomi Aqara door & window contact sensor (EndDevice)
                                            2020-10-05 13:02:44.236 - info: zigbee.0 (4009) 0x000b57fffe59e847 (addr 17685): V3-BTZB - Danalock BT/ZB smartlock (EndDevice)
                                            2020-10-05 13:02:44.237 - info: zigbee.0 (4009) Zigbee started
                                            2020-10-05 13:02:53.211 - info: unifi.0 (3760) Update done
                                            2020-10-05 13:02:54.280 - error: zigbee.0 (4009) DeviceConfigure failed 0x000b57fffe59e847 V3-BTZB, attempt 1 (Error: Bind 0x000b57fffe59e847/1 closuresDoorLock from '0x00124b001caaaad1/1' failed (AREQ - ZDO - bindRsp after 10000ms) at Timeout._onTimeout (/opt/iobroker/node_modules/zigbee-herdsman/dist/utils/waitress.js:46:35) at listOnTimeout (internal/timers.js:549:17) at processTimers (internal/timers.js:492:7))
                                            .............................
                                            2020-10-05 14:50:13.999 - info: zigbee.0 (4009) Configuring 0x000b57fffe59e847 V3-BTZB
                                            2020-10-05 14:50:19.008 - info: zigbee.0 (4009) DeviceConfigure successful 0x000b57fffe59e847 V3-BTZB
                                            

                                            lass dir Zeit mit antworten

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

                                            Support us

                                            ioBroker
                                            Community Adapters
                                            Donate
                                            FAQ Cloud / IOT
                                            HowTo: Node.js-Update
                                            HowTo: Backup/Restore
                                            Downloads
                                            BLOG

                                            1.2k
                                            Online

                                            31.7k
                                            Users

                                            79.7k
                                            Topics

                                            1.3m
                                            Posts

                                            danalock zigbee adapter
                                            13
                                            191
                                            17206
                                            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