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

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

Community Forum

donate donate
  1. ioBroker Community Home
  2. Deutsch
  3. ioBroker Allgemein
  4. Zigbee-Adapter 1.0.2 Danalock

NEWS

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

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

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

Zigbee-Adapter 1.0.2 Danalock

Geplant Angeheftet Gesperrt Verschoben ioBroker Allgemein
zigbee adapterdanalock
191 Beiträge 13 Kommentatoren 25.6k Aufrufe 15 Watching
  • Älteste zuerst
  • Neuste zuerst
  • Meiste Stimmen
Antworten
  • In einem neuen Thema antworten
Anmelden zum Antworten
Dieses Thema wurde gelöscht. Nur Nutzer mit entsprechenden Rechten können es sehen.
  • AsgothianA Asgothian

    @patrick039212 sorry.. 2sprachigkeit ist ein problem.

    Wenn ein Gerät sich neu an einem Zigbee Netzwerk anmeldet muss es "konfiguriert" werden - wann es welche Meldungen an wen absetzt und so weiter. Dazu versucht der Adapter beim Start das sogenannte "Configure" so lange abzusetzen bis es erfolgreich war.

    Nach erfolgreichem Configure sollten die Nachrichten vom Schloss ankommen.

    Dafuer müssen wir dem Adapter Zeit geben.

    A.
    p.s. fuer heute bin ich dann raus, mehr morgen.

    Jan PuchtaJ Offline
    Jan PuchtaJ Offline
    Jan Puchta
    schrieb am zuletzt editiert von
    #119

    @Asgothian

    hallo und Entschuldigung wenn ich mich reinhänge

    das Problem mit Danalock habe ich auch

    über einen alten Post (leider wurde das Problem da nicht gelöst)
    https://forum.iobroker.net/topic/23935/danalock-v3-status-abfragen

    bin ich dahintergekommen das man mit Analyse im Zigbee Adapter den Status manuell abfragen kann

    {
    "devId": "zigbee.0.000b57fffe59e847",
    "ep": "1",
    "cid": "closuresDoorLock",
    "cmd": "read",
    "cmdType": "foundation",
    "zclData": {
    "lockState": 0
    },
    "cfg": null
    }

    ungefähr eine Sekunde nach dem senden (eher nicht) von "lock" oder "unlock" kann der neue Status ausgelesen werden

    Ausgabe ist dann SUCCESS {"lockState":1} für locked bzw. SUCCESS {"lockState":2} für unlocked

    meine Frage

    kann dieses raw json irgendwie in blockly oder javascript (Button oder Objekt) genutzt werden

    habe kein Problem nach einem Schließvorgang oder per cron den Status manuell zu aktuallisieren

    einen schönen Sonntag wünsche ich

    AsgothianA 1 Antwort Letzte Antwort
    0
    • Jan PuchtaJ Jan Puchta

      @Asgothian

      hallo und Entschuldigung wenn ich mich reinhänge

      das Problem mit Danalock habe ich auch

      über einen alten Post (leider wurde das Problem da nicht gelöst)
      https://forum.iobroker.net/topic/23935/danalock-v3-status-abfragen

      bin ich dahintergekommen das man mit Analyse im Zigbee Adapter den Status manuell abfragen kann

      {
      "devId": "zigbee.0.000b57fffe59e847",
      "ep": "1",
      "cid": "closuresDoorLock",
      "cmd": "read",
      "cmdType": "foundation",
      "zclData": {
      "lockState": 0
      },
      "cfg": null
      }

      ungefähr eine Sekunde nach dem senden (eher nicht) von "lock" oder "unlock" kann der neue Status ausgelesen werden

      Ausgabe ist dann SUCCESS {"lockState":1} für locked bzw. SUCCESS {"lockState":2} für unlocked

      meine Frage

      kann dieses raw json irgendwie in blockly oder javascript (Button oder Objekt) genutzt werden

      habe kein Problem nach einem Schließvorgang oder per cron den Status manuell zu aktuallisieren

      einen schönen Sonntag wünsche ich

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

      @Jan-Puchta
      Prinzipiell geht das.

      Nutzt du das Schloss ?

      Wenn ja würde mich interessieren ob die aktualisierungsprobkeme bei dir mit der gepatchten Version noch auftreten oder weg sind.

      A.

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

      Jan PuchtaJ 1 Antwort Letzte Antwort
      0
      • P patrick039212

        @Asgothian oke danke ...

        das ist jedenfalls der log

        2020-10-03 20:54:39.364 - info: host.raspberrypi "system.adapter.zigbee.0" enabled
        2020-10-03 20:54:39.441 - info: host.raspberrypi instance system.adapter.zigbee.0 started with pid 23436
        2020-10-03 20:54:44.644 - debug: zigbee.0 (23436) Redis Objects: Use Redis connection: 127.0.0.1:9001
        2020-10-03 20:54:45.407 - debug: zigbee.0 (23436) Objects client ready ... initialize now
        2020-10-03 20:54:45.467 - debug: zigbee.0 (23436) Objects create System PubSub Client
        2020-10-03 20:54:45.471 - debug: zigbee.0 (23436) Objects create User PubSub Client
        2020-10-03 20:54:45.476 - debug: zigbee.0 (23436) Objects client initialize lua scripts
        2020-10-03 20:54:45.527 - debug: zigbee.0 (23436) Objects connected to redis: 127.0.0.1:9001
        2020-10-03 20:54:45.555 - debug: zigbee.0 (23436) objectDB connected
        2020-10-03 20:54:45.564 - debug: zigbee.0 (23436) Redis States: Use Redis connection: 127.0.0.1:9000
        2020-10-03 20:54:45.596 - debug: zigbee.0 (23436) States create User PubSub Client
        2020-10-03 20:54:45.699 - debug: zigbee.0 (23436) States create System PubSub Client
        2020-10-03 20:54:45.782 - debug: zigbee.0 (23436) States connected to redis: 127.0.0.1:9000
        2020-10-03 20:54:45.785 - debug: zigbee.0 (23436) statesDB connected
        2020-10-03 20:54:46.273 - debug: cloud.0 (1434) system.adapter.admin.0: logging false
        2020-10-03 20:54:46.286 - debug: scenes.0 (2550) system.adapter.admin.0: logging false
        2020-10-03 20:54:46.882 - info: zigbee.0 (23436) starting. Version 1.2.1 in /opt/iobroker/node_modules/iobroker.zigbee, node: v12.18.4, js-controller: 3.1.6
        2020-10-03 20:54:46.977 - error: zigbee.0 (23436) Serial port not selected! Go to settings page.
        2020-10-03 20:54:46.988 - debug: zigbee.0 (23436) Using zigbee-herdsman with settings: {"network":{"panID":6754,"extendedPanID":[221,221,221,221,221,221,221,221],"channelList":[11],"networkKey":[1,3,5,7,9,11,13,15,0,2,4,6,8,10,12,13]},"databasePath":"/opt/iobroker/iobroker-data/zigbee_0/shepherd.db","backupPath":"/opt/iobroker/iobroker-data/zigbee_0/nvbackup.json","serialPort":{"baudRate":115200,"rtscts":false,"path":"","adapter":"deconz"}}
        2020-10-03 20:54:47.215 - info: zigbee.0 (23436) Starting Zigbee V3-BTZB hack...
        2020-10-03 20:54:47.220 - debug: zigbee.0 (23436) Starting zigbee-herdsman...
        2020-10-03 20:54:47.797 - debug: zigbee.0 (23436) Backup /opt/iobroker/iobroker-data/zigbee_0/backup_2020_10_03-20_54_46.tar.gz success
        2020-10-03 20:54:48.301 - debug: zigbee.0 (23436) zigbee-herdsman started
        2020-10-03 20:54:48.343 - info: zigbee.0 (23436) Coordinator firmware version: {"type":"ConBee2/RaspBee2","meta":{"transportrev":0,"product":0,"majorrel":38,"minorrel":88,"maintrel":0,"revision":"0x26580700"}}
        2020-10-03 20:54:48.557 - debug: zigbee.0 (23436) Zigbee network parameters: {"panID":6754,"extendedPanID":"0xdddddddddddddddd","channel":11}
        2020-10-03 20:54:48.560 - info: zigbee.0 (23436) Unable to disable LED, unsupported function.
        2020-10-03 20:54:48.562 - info: zigbee.0 (23436) --> transmitPower : normal
        2020-10-03 20:54:48.566 - info: zigbee.0 (23436) Unable to set transmit power, unsupported function.
        2020-10-03 20:54:48.576 - info: zigbee.0 (23436) Currently 3 devices are joined:
        2020-10-03 20:54:48.578 - debug: zigbee.0 (23436) Publish available for 0x000b57fffe59e779 = true
        2020-10-03 20:54:48.583 - debug: zigbee.0 (23436) Publish available for 0x00158d000358efeb = true
        2020-10-03 20:54:48.585 - debug: zigbee.0 (23436) Publish available for 0x00158d00042e3307 = true
        2020-10-03 20:54:48.587 - debug: zigbee.0 (23436) DeviceConfigure 0x000b57fffe59e779 V3-BTZB vorced - DANALOCK HACK
        2020-10-03 20:54:48.589 - debug: zigbee.0 (23436) DeviceConfigure 0x000b57fffe59e779 V3-BTZB needed
        2020-10-03 20:54:48.592 - info: zigbee.0 (23436) Configuring 0x000b57fffe59e779 V3-BTZB
        2020-10-03 20:54:48.611 - debug: zigbee.0 (23436) New device event: {"type":"device","device":{"ID":2,"_type":"EndDevice","_ieeeAddr":"0x000b57fffe59e779","_networkAddress":22061,"_manufacturerID":4444,"_endpoints":[{"ID":1,"profileID":260,"deviceID":10,"inputClusters":[0,1,3,9,32,257,2821],"outputClusters":[10,25,2821],"deviceNetworkAddress":22061,"deviceIeeeAddress":"0x000b57fffe59e779","clusters":{"genBasic":{"attributes":{"modelId":"V3-BTZB","manufacturerName":"Danalock","powerSource":3,"zclVersion":2,"appVersion":1,"stackVersion":1,"hwVersion":4,"dateCode":"04092018\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000"}},"closuresDoorLock":{"attributes":{"lockState":1}},"genPowerCfg":{"attributes":{"batteryPercentageRemaining":198}}},"_binds":[{"cluster":257,"type":"endpoint","deviceIeeeAddress":"0x00212effff04ff54","endpointID":1},{"cluster":1,"type":"endpoint","deviceIeeeAddress":"0x00212effff04ff54","endpointID":1}],"meta":{}}],"_manufacturerName":"Danalock","_powerSource":"Battery","_modelID":"V3-BTZB","_applicationVersion":1,"_stackVersion":1,"_zclVersion":2,"_hardwareVersion":4,"_dateCode":"04092018\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000","_interviewCompleted":true,"_interviewing":false,"meta":{"configured":5},"_lastSeen":1601746223692},"mapped":{"zigbeeModel":["V3-BTZB"],"model":"V3-BTZB","vendor":"Danalock","description":"BT/ZB smartlock","supports":"lock/unlock, battery","fromZigbee":[{"cluster":"closuresDoorLock","type":["attributeReport","readResponse"]},{"cluster":"closuresDoorLock","type":"commandOperationEventNotification"},{"cluster":"genPowerCfg","type":["attributeReport","readResponse"]}],"toZigbee":[{"key":["state"]}],"meta":{"configureKey":5}},"name":"0x000b57fffe59e779"}
        2020-10-03 20:54:48.614 - info: zigbee.0 (23436) 0x000b57fffe59e779 (addr 22061): V3-BTZB - Danalock BT/ZB smartlock (EndDevice)
        2020-10-03 20:54:48.622 - debug: zigbee.0 (23436) New device event: {"type":"device","device":{"ID":3,"_type":"EndDevice","_ieeeAddr":"0x00158d000358efeb","_networkAddress":9532,"_manufacturerID":4151,"_endpoints":[{"ID":1,"inputClusters":[],"outputClusters":[],"deviceNetworkAddress":9532,"deviceIeeeAddress":"0x00158d000358efeb","clusters":{"genBasic":{"attributes":{"65282":[{"elmType":16,"elmVal":1},{"elmType":33,"elmVal":3005},{"elmType":33,"elmVal":5032},{"elmType":36,"elmVal":[0,2]},{"elmType":33,"elmVal":322},{"elmType":32,"elmVal":87}],"modelId":"lumi.sensor_magnet","appVersion":10}},"genOnOff":{"attributes":{"onOff":0}}},"_binds":[],"meta":{}}],"_manufacturerName":"LUMI","_powerSource":"Battery","_modelID":"lumi.sensor_magnet","_applicationVersion":10,"_interviewCompleted":true,"_interviewing":false,"meta":{},"_lastSeen":1601750047944},"mapped":{"zigbeeModel":["lumi.sensor_magnet"],"model":"MCCGQ01LM","vendor":"Xiaomi","description":"MiJia door & window contact sensor","supports":"contact","meta":{"battery":{"voltageToPercentage":"CR2032"}},"fromZigbee":[{"cluster":"genBasic","type":["attributeReport","readResponse"]},{"cluster":"genOnOff","type":["attributeReport","readResponse"]}],"toZigbee":[]},"name":"0x00158d000358efeb"}
        2020-10-03 20:54:48.625 - info: zigbee.0 (23436) 0x00158d000358efeb (addr 9532): MCCGQ01LM - Xiaomi MiJia door & window contact sensor (EndDevice)
        2020-10-03 20:54:48.628 - debug: zigbee.0 (23436) New device event: {"type":"device","device":{"ID":4,"_type":"EndDevice","_ieeeAddr":"0x00158d00042e3307","_networkAddress":10193,"_manufacturerID":4151,"_endpoints":[{"ID":1,"inputClusters":[],"outputClusters":[],"deviceNetworkAddress":10193,"deviceIeeeAddress":"0x00158d00042e3307","clusters":{"genBasic":{"attributes":{"65282":[{"elmType":16,"elmVal":0},{"elmType":33,"elmVal":3005},{"elmType":33,"elmVal":5032},{"elmType":36,"elmVal":[0,1]},{"elmType":33,"elmVal":254},{"elmType":32,"elmVal":90}],"modelId":"lumi.sensor_magnet","appVersion":10}},"genOnOff":{"attributes":{"onOff":0}}},"_binds":[],"meta":{}}],"_manufacturerName":"LUMI","_powerSource":"Battery","_modelID":"lumi.sensor_magnet","_applicationVersion":10,"_interviewCompleted":true,"_interviewing":false,"meta":{},"_lastSeen":1601750093808},"mapped":{"zigbeeModel":["lumi.sensor_magnet"],"model":"MCCGQ01LM","vendor":"Xiaomi","description":"MiJia door & window contact sensor","supports":"contact","meta":{"battery":{"voltageToPercentage":"CR2032"}},"fromZigbee":[{"cluster":"genBasic","type":["attributeReport","readResponse"]},{"cluster":"genOnOff","type":["attributeReport","readResponse"]}],"toZigbee":[]},"name":"0x00158d00042e3307"}
        2020-10-03 20:54:48.630 - info: zigbee.0 (23436) 0x00158d00042e3307 (addr 10193): MCCGQ01LM - Xiaomi MiJia door & window contact sensor (EndDevice)
        2020-10-03 20:54:48.635 - info: zigbee.0 (23436) Zigbee started
        2020-10-03 20:54:49.609 - debug: zigbee.0 (23436) Publish available for 0x000b57fffe59e779 = true
        2020-10-03 20:54:49.622 - debug: zigbee.0 (23436) Publish available for 0x00158d000358efeb = true
        2020-10-03 20:54:49.629 - debug: zigbee.0 (23436) Publish available for 0x00158d00042e3307 = true
        2020-10-03 20:55:29.572 - warn: javascript.0 (2144) You are assigning a string to the state "anwesenheit.0.pgeht" which expects a boolean. Please fix your code to use a boolean or change the state type to string. This warning might become an error in future versions.
        2020-10-03 20:55:29.576 - warn: javascript.0 (2144) at setState (/opt/iobroker/node_modules/iobroker.javascript/lib/sandbox.js:1355:20)
        2020-10-03 20:55:29.577 - warn: javascript.0 (2144) at Object. (script.js.anwesenheit.kommtgeht:7:5)
        2020-10-03 20:55:29.578 - warn: javascript.0 (2144) at Object.callback (/opt/iobroker/node_modules/iobroker.javascript/lib/sandbox.js:1052:38)
        2020-10-03 20:55:29.579 - warn: javascript.0 (2144) at Object.stateChange (/opt/iobroker/node_modules/iobroker.javascript/main.js:451:25)
        2020-10-03 20:55:29.579 - warn: javascript.0 (2144) at Immediate._onImmediate (/opt/iobroker/node_modules/iobroker.js-controller/lib/adapter.js:5384:37)
        2020-10-03 20:55:29.580 - warn: javascript.0 (2144) at processImmediate (internal/timers.js:456:21)
        2020-10-03 20:55:41.931 - warn: javascript.0 (2144) You are assigning a string to the state "anwesenheit.0.pkommt" which expects a boolean. Please fix your code to use a boolean or change the state type to string. This warning might become an error in future versions.
        2020-10-03 20:55:41.937 - warn: javascript.0 (2144) at setState (/opt/iobroker/node_modules/iobroker.javascript/lib/sandbox.js:1355:20)
        2020-10-03 20:55:41.939 - warn: javascript.0 (2144) at Object. (script.js.anwesenheit.kommtgeht:5:5)
        2020-10-03 20:55:41.940 - warn: javascript.0 (2144) at Object.callback (/opt/iobroker/node_modules/iobroker.javascript/lib/sandbox.js:1052:38)
        2020-10-03 20:55:41.941 - warn: javascript.0 (2144) at Object.stateChange (/opt/iobroker/node_modules/iobroker.javascript/main.js:451:25)
        2020-10-03 20:55:41.942 - warn: javascript.0 (2144) at Immediate._onImmediate (/opt/iobroker/node_modules/iobroker.js-controller/lib/adapter.js:5384:37)
        2020-10-03 20:55:41.943 - warn: javascript.0 (2144) at processImmediate (internal/timers.js:456:21)
        2020-10-03 20:55:49.220 - error: zigbee.0 (23436) DeviceConfigure failed 0x000b57fffe59e779 V3-BTZB, attempt 1 (Error: Bind 0x000b57fffe59e779/1 closuresDoorLock from '0x00212effff04ff54/1' failed (waiting for response TIMEOUT)
        at DeconzAdapter. (/opt/iobroker/node_modules/zigbee-herdsman/dist/adapter/deconz/adapter/deconzAdapter.js:656:23)
        at Generator.throw ()
        at rejected (/opt/iobroker/node_modules/zigbee-herdsman/dist/adapter/deconz/adapter/deconzAdapter.js:25:65))
        2020-10-03 20:55:49.223 - debug: zigbee.0 (23436) DeviceConfigure 0x00158d000358efeb lumi.sensor_magnet not needed
        2020-10-03 20:55:49.225 - debug: zigbee.0 (23436) DeviceConfigure 0x00158d00042e3307 lumi.sensor_magnet not needed
        2020-10-03 20:56:42.994 - warn: javascript.0 (2144) You are assigning a string to the state "anwesenheit.0.pgeht" which expects a boolean. Please fix your code to use a boolean or change the state type to string. This warning might become an error in future versions.
        2020-10-03 20:56:43.003 - warn: javascript.0 (2144) at setState (/opt/iobroker/node_modules/iobroker.javascript/lib/sandbox.js:1355:20)
        2020-10-03 20:56:43.004 - warn: javascript.0 (2144) at Object. (script.js.anwesenheit.kommtgeht:7:5)
        2020-10-03 20:56:43.005 - warn: javascript.0 (2144) at Object.callback (/opt/iobroker/node_modules/iobroker.javascript/lib/sandbox.js:1052:38)
        2020-10-03 20:56:43.006 - warn: javascript.0 (2144) at Object.stateChange (/opt/iobroker/node_modules/iobroker.javascript/main.js:451:25)
        2020-10-03 20:56:43.007 - warn: javascript.0 (2144) at Immediate._onImmediate (/opt/iobroker/node_modules/iobroker.js-controller/lib/adapter.js:5384:37)
        2020-10-03 20:56:43.007 - warn: javascript.0 (2144) at processImmediate (internal/timers.js:456:21)
        2020-10-03 20:57:48.946 - warn: javascript.0 (2144) You are assigning a string to the state "anwesenheit.0.pkommt" which expects a boolean. Please fix your code to use a boolean or change the state type to string. This warning might become an error in future versions.
        2020-10-03 20:57:48.950 - warn: javascript.0 (2144) at setState (/opt/iobroker/node_modules/iobroker.javascript/lib/sandbox.js:1355:20)
        2020-10-03 20:57:48.951 - warn: javascript.0 (2144) at Object. (script.js.anwesenheit.kommtgeht:5:5)
        2020-10-03 20:57:48.952 - warn: javascript.0 (2144) at Object.callback (/opt/iobroker/node_modules/iobroker.javascript/lib/sandbox.js:1052:38)
        2020-10-03 20:57:48.958 - warn: javascript.0 (2144) at Object.stateChange (/opt/iobroker/node_modules/iobroker.javascript/main.js:451:25)
        2020-10-03 20:57:48.958 - warn: javascript.0 (2144) at Immediate._onImmediate (/opt/iobroker/node_modules/iobroker.js-controller/lib/adapter.js:5384:37)
        2020-10-03 20:57:48.959 - warn: javascript.0 (2144) at processImmediate (internal/timers.js:456:21)
        2020-10-03 20:58:06.388 - debug: zigbee.0 (23436) handleMessage. {"type":"attributeReport","device":{"ID":4,"_type":"EndDevice","_ieeeAddr":"0x00158d00042e3307","_networkAddress":10193,"_manufacturerID":4151,"_endpoints":[{"ID":1,"inputClusters":[],"outputClusters":[],"deviceNetworkAddress":10193,"deviceIeeeAddress":"0x00158d00042e3307","clusters":{"genBasic":{"attributes":{"65282":[{"elmType":16,"elmVal":0},{"elmType":33,"elmVal":3005},{"elmType":33,"elmVal":5032},{"elmType":36,"elmVal":[0,1]},{"elmType":33,"elmVal":254},{"elmType":32,"elmVal":90}],"modelId":"lumi.sensor_magnet","appVersion":10}},"genOnOff":{"attributes":{"onOff":1}}},"_binds":[],"meta":{}}],"_manufacturerName":"LUMI","_powerSource":"Battery","_modelID":"lumi.sensor_magnet","_applicationVersion":10,"_interviewCompleted":true,"_interviewing":false,"meta":{},"_lastSeen":1601751486380},"endpoint":"[Circular]","data":{"onOff":1},"linkquality":139,"groupID":null,"cluster":"genOnOff","meta":{"zclTransactionSequenceNumber":111,"manufacturerCode":null,"frameControl":{"frameType":0,"manufacturerSpecific":false,"direction":1,"disableDefaultResponse":true,"reservedBits":0}}}
        2020-10-03 20:58:06.395 - debug: zigbee.0 (23436) Received Zigbee message from '0x00158d00042e3307', type 'attributeReport', cluster 'genOnOff', data '{"onOff":1}' from endpoint 1 with groupID null
        2020-10-03 20:58:06.401 - debug: zigbee.0 (23436) Type attributeReport device {"type":"device","device":{"ID":4,"_type":"EndDevice","_ieeeAddr":"0x00158d00042e3307","_networkAddress":10193,"_manufacturerID":4151,"_endpoints":[{"ID":1,"inputClusters":[],"outputClusters":[],"deviceNetworkAddress":10193,"deviceIeeeAddress":"0x00158d00042e3307","clusters":{"genBasic":{"attributes":{"65282":[{"elmType":16,"elmVal":0},{"elmType":33,"elmVal":3005},{"elmType":33,"elmVal":5032},{"elmType":36,"elmVal":[0,1]},{"elmType":33,"elmVal":254},{"elmType":32,"elmVal":90}],"modelId":"lumi.sensor_magnet","appVersion":10}},"genOnOff":{"attributes":{"onOff":1}}},"_binds":[],"meta":{}}],"_manufacturerName":"LUMI","_powerSource":"Battery","_modelID":"lumi.sensor_magnet","_applicationVersion":10,"_interviewCompleted":true,"_interviewing":false,"meta":{},"_lastSeen":1601751486380},"mapped":{"zigbeeModel":["lumi.sensor_magnet"],"model":"MCCGQ01LM","vendor":"Xiaomi","description":"MiJia door & window contact sensor","supports":"contact","meta":{"battery":{"voltageToPercentage":"CR2032"}},"fromZigbee":[{"cluster":"genBasic","type":["attributeReport","readResponse"]},{"cluster":"genOnOff","type":["attributeReport","readResponse"]}],"toZigbee":[]},"name":"0x00158d00042e3307"} incoming event: {"type":"attributeReport","device":{"ID":4,"_type":"EndDevice","_ieeeAddr":"0x00158d00042e3307","_networkAddress":10193,"_manufacturerID":4151,"_endpoints":[{"ID":1,"inputClusters":[],"outputClusters":[],"deviceNetworkAddress":10193,"deviceIeeeAddress":"0x00158d00042e3307","clusters":{"genBasic":{"attributes":{"65282":[{"elmType":16,"elmVal":0},{"elmType":33,"elmVal":3005},{"elmType":33,"elmVal":5032},{"elmType":36,"elmVal":[0,1]},{"elmType":33,"elmVal":254},{"elmType":32,"elmVal":90}],"modelId":"lumi.sensor_magnet","appVersion":10}},"genOnOff":{"attributes":{"onOff":1}}},"_binds":[],"meta":{}}],"_manufacturerName":"LUMI","_powerSource":"Battery","_modelID":"lumi.sensor_magnet","_applicationVersion":10,"_interviewCompleted":true,"_interviewing":false,"meta":{},"_lastSeen":1601751486380},"endpoint":"[Circular]","data":{"onOff":1},"linkquality":139,"groupID":null,"cluster":"genOnOff","meta":{"zclTransactionSequenceNumber":111,"manufacturerCode":null,"frameControl":{"frameType":0,"manufacturerSpecific":false,"direction":1,"disableDefaultResponse":true,"reservedBits":0}}}
        2020-10-03 20:58:06.417 - debug: zigbee.0 (23436) Publish {"contact":false}
        2020-10-03 20:58:11.529 - debug: zigbee.0 (23436) handleMessage. {"type":"attributeReport","device":{"ID":4,"_type":"EndDevice","_ieeeAddr":"0x00158d00042e3307","_networkAddress":10193,"_manufacturerID":4151,"_endpoints":[{"ID":1,"inputClusters":[],"outputClusters":[],"deviceNetworkAddress":10193,"deviceIeeeAddress":"0x00158d00042e3307","clusters":{"genBasic":{"attributes":{"65282":[{"elmType":16,"elmVal":0},{"elmType":33,"elmVal":3005},{"elmType":33,"elmVal":5032},{"elmType":36,"elmVal":[0,1]},{"elmType":33,"elmVal":254},{"elmType":32,"elmVal":90}],"modelId":"lumi.sensor_magnet","appVersion":10}},"genOnOff":{"attributes":{"onOff":0}}},"_binds":[],"meta":{}}],"_manufacturerName":"LUMI","_powerSource":"Battery","_modelID":"lumi.sensor_magnet","_applicationVersion":10,"_interviewCompleted":true,"_interviewing":false,"meta":{},"_lastSeen":1601751491528},"endpoint":"[Circular]","data":{"onOff":0},"linkquality":139,"groupID":null,"cluster":"genOnOff","meta":{"zclTransactionSequenceNumber":112,"manufacturerCode":null,"frameControl":{"frameType":0,"manufacturerSpecific":false,"direction":1,"disableDefaultResponse":true,"reservedBits":0}}}
        2020-10-03 20:58:11.533 - debug: zigbee.0 (23436) Received Zigbee message from '0x00158d00042e3307', type 'attributeReport', cluster 'genOnOff', data '{"onOff":0}' from endpoint 1 with groupID null
        2020-10-03 20:58:11.536 - debug: zigbee.0 (23436) Type attributeReport device {"type":"device","device":{"ID":4,"_type":"EndDevice","_ieeeAddr":"0x00158d00042e3307","_networkAddress":10193,"_manufacturerID":4151,"_endpoints":[{"ID":1,"inputClusters":[],"outputClusters":[],"deviceNetworkAddress":10193,"deviceIeeeAddress":"0x00158d00042e3307","clusters":{"genBasic":{"attributes":{"65282":[{"elmType":16,"elmVal":0},{"elmType":33,"elmVal":3005},{"elmType":33,"elmVal":5032},{"elmType":36,"elmVal":[0,1]},{"elmType":33,"elmVal":254},{"elmType":32,"elmVal":90}],"modelId":"lumi.sensor_magnet","appVersion":10}},"genOnOff":{"attributes":{"onOff":0}}},"_binds":[],"meta":{}}],"_manufacturerName":"LUMI","_powerSource":"Battery","_modelID":"lumi.sensor_magnet","_applicationVersion":10,"_interviewCompleted":true,"_interviewing":false,"meta":{},"_lastSeen":1601751491528},"mapped":{"zigbeeModel":["lumi.sensor_magnet"],"model":"MCCGQ01LM","vendor":"Xiaomi","description":"MiJia door & window contact sensor","supports":"contact","meta":{"battery":{"voltageToPercentage":"CR2032"}},"fromZigbee":[{"cluster":"genBasic","type":["attributeReport","readResponse"]},{"cluster":"genOnOff","type":["attributeReport","readResponse"]}],"toZigbee":[]},"name":"0x00158d00042e3307"} incoming event: {"type":"attributeReport","device":{"ID":4,"_type":"EndDevice","_ieeeAddr":"0x00158d00042e3307","_networkAddress":10193,"_manufacturerID":4151,"_endpoints":[{"ID":1,"inputClusters":[],"outputClusters":[],"deviceNetworkAddress":10193,"deviceIeeeAddress":"0x00158d00042e3307","clusters":{"genBasic":{"attributes":{"65282":[{"elmType":16,"elmVal":0},{"elmType":33,"elmVal":3005},{"elmType":33,"elmVal":5032},{"elmType":36,"elmVal":[0,1]},{"elmType":33,"elmVal":254},{"elmType":32,"elmVal":90}],"modelId":"lumi.sensor_magnet","appVersion":10}},"genOnOff":{"attributes":{"onOff":0}}},"_binds":[],"meta":{}}],"_manufacturerName":"LUMI","_powerSource":"Battery","_modelID":"lumi.sensor_magnet","_applicationVersion":10,"_interviewCompleted":true,"_interviewing":false,"meta":{},"_lastSeen":1601751491528},"endpoint":"[Circular]","data":{"onOff":0},"linkquality":139,"groupID":null,"cluster":"genOnOff","meta":{"zclTransactionSequenceNumber":112,"manufacturerCode":null,"frameControl":{"frameType":0,"manufacturerSpecific":false,"direction":1,"disableDefaultResponse":true,"reservedBits":0}}}
        2020-10-03 20:58:11.547 - debug: zigbee.0 (23436) Publish {"contact":true}
        2020-10-03 20:59:48.576 - debug: zigbee.0 (23436) Non-pingable device 0x000b57fffe59e779 V3-BTZB was last seen '5364.884' seconds ago.
        2020-10-03 20:59:48.579 - debug: zigbee.0 (23436) Non-pingable device 0x00158d000358efeb lumi.sensor_magnet was last seen '1540.635' seconds ago.
        2020-10-03 20:59:48.582 - debug: zigbee.0 (23436) Non-pingable device 0x00158d00042e3307 lumi.sensor_magnet was last seen '97.053' seconds ago.
        2020-10-03 21:00:00.121 - info: host.raspberrypi instance system.adapter.ical.0 started with pid 3425
        2020-10-03 21:00:07.931 - info: ical.0 (3425) starting. Version 1.7.4 in /opt/iobroker/node_modules/iobroker.ical, node: v12.18.4, js-controller: 3.1.6
        2020-10-03 21:00:09.350 - info: ical.0 (3425) processing URL: kalender http://p58-caldav.icloud.com/published/2/ODI4MDQ2NzM0OTgyODA0Np9qMcPbcTzAVfzSmal12S0mYkgSXQvFgCPyECETbfFC
        2020-10-03 21:00:14.431 - info: ical.0 (3425) Terminated (NO_ERROR): Without reason
        2020-10-03 21:00:14.993 - info: host.raspberrypi instance system.adapter.ical.0 terminated with code 0 (NO_ERROR)
        2020-10-03 21:00:23.670 - warn: javascript.0 (2144) You are assigning a string to the state "anwesenheit.0.pgeht" which expects a boolean. Please fix your code to use a boolean or change the state type to string. This warning might become an error in future versions.
        2020-10-03 21:00:23.675 - warn: javascript.0 (2144) at setState (/opt/iobroker/node_modules/iobroker.javascript/lib/sandbox.js:1355:20)
        2020-10-03 21:00:23.677 - warn: javascript.0 (2144) at Object. (script.js.anwesenheit.kommtgeht:7:5)
        2020-10-03 21:00:23.677 - warn: javascript.0 (2144) at Object.callback (/opt/iobroker/node_modules/iobroker.javascript/lib/sandbox.js:1052:38)
        2020-10-03 21:00:23.678 - warn: javascript.0 (2144) at Object.stateChange (/opt/iobroker/node_modules/iobroker.javascript/main.js:451:25)
        2020-10-03 21:00:23.679 - warn: javascript.0 (2144) at Immediate._onImmediate (/opt/iobroker/node_modules/iobroker.js-controller/lib/adapter.js:5384:37)
        2020-10-03 21:00:23.680 - warn: javascript.0 (2144) at processImmediate (internal/timers.js:456:21)
        2020-10-03 21:04:41.917 - info: info.0 (1346) Popup news was read...
        2020-10-03 21:04:48.582 - debug: zigbee.0 (23436) Non-pingable device 0x000b57fffe59e779 V3-BTZB was last seen '5664.89' seconds ago.
        2020-10-03 21:04:48.588 - debug: zigbee.0 (23436) Non-pingable device 0x00158d000358efeb lumi.sensor_magnet was last seen '1840.643' seconds ago.
        2020-10-03 21:04:48.590 - debug: zigbee.0 (23436) Non-pingable device 0x00158d00042e3307 lumi.sensor_magnet was last seen '397.062' seconds ago.
        2020-10-03 21:09:48.582 - debug: zigbee.0 (23436) Non-pingable device 0x000b57fffe59e779 V3-BTZB was last seen '5964.89' seconds ago.
        2020-10-03 21:09:48.588 - debug: zigbee.0 (23436) Non-pingable device 0x00158d000358efeb lumi.sensor_magnet was last seen '2140.644' seconds ago.
        2020-10-03 21:09:48.590 - debug: zigbee.0 (23436) Non-pingable device 0x00158d00042e3307 lumi.sensor_magnet was last seen '697.062' seconds ago.
        2020-10-03 21:12:04.719 - debug: zigbee.0 (23436) handleMessage. {"type":"attributeReport","device":{"ID":4,"_type":"EndDevice","_ieeeAddr":"0x00158d00042e3307","_networkAddress":10193,"_manufacturerID":4151,"_endpoints":[{"ID":1,"inputClusters":[],"outputClusters":[],"deviceNetworkAddress":10193,"deviceIeeeAddress":"0x00158d00042e3307","clusters":{"genBasic":{"attributes":{"65282":[{"elmType":16,"elmVal":0},{"elmType":33,"elmVal":3005},{"elmType":33,"elmVal":5032},{"elmType":36,"elmVal":[0,3]},{"elmType":33,"elmVal":254},{"elmType":32,"elmVal":90}],"modelId":"lumi.sensor_magnet","appVersion":10}},"genOnOff":{"attributes":{"onOff":0}}},"_binds":[],"meta":{}}],"_manufacturerName":"LUMI","_powerSource":"Battery","_modelID":"lumi.sensor_magnet","_applicationVersion":10,"_interviewCompleted":true,"_interviewing":false,"meta":{},"_lastSeen":1601752324712},"endpoint":"[Circular]","data":{"65282":"[Circular]"},"linkquality":139,"groupID":null,"cluster":"genBasic","meta":{"zclTransactionSequenceNumber":113,"manufacturerCode":4660,"frameControl":{"frameType":0,"manufacturerSpecific":true,"direction":1,"disableDefaultResponse":true,"reservedBits":0}}}
        2020-10-03 21:12:04.723 - debug: zigbee.0 (23436) Received Zigbee message from '0x00158d00042e3307', type 'attributeReport', cluster 'genBasic', data '{"65282":[{"elmType":16,"elmVal":0},{"elmType":33,"elmVal":3005},{"elmType":33,"elmVal":5032},{"elmType":36,"elmVal":[0,3]},{"elmType":33,"elmVal":254},{"elmType":32,"elmVal":90}]}' from endpoint 1 with groupID null
        2020-10-03 21:12:04.728 - debug: zigbee.0 (23436) Type attributeReport device {"type":"device","device":{"ID":4,"_type":"EndDevice","_ieeeAddr":"0x00158d00042e3307","_networkAddress":10193,"_manufacturerID":4151,"_endpoints":[{"ID":1,"inputClusters":[],"outputClusters":[],"deviceNetworkAddress":10193,"deviceIeeeAddress":"0x00158d00042e3307","clusters":{"genBasic":{"attributes":{"65282":[{"elmType":16,"elmVal":0},{"elmType":33,"elmVal":3005},{"elmType":33,"elmVal":5032},{"elmType":36,"elmVal":[0,3]},{"elmType":33,"elmVal":254},{"elmType":32,"elmVal":90}],"modelId":"lumi.sensor_magnet","appVersion":10}},"genOnOff":{"attributes":{"onOff":0}}},"_binds":[],"meta":{}}],"_manufacturerName":"LUMI","_powerSource":"Battery","_modelID":"lumi.sensor_magnet","_applicationVersion":10,"_interviewCompleted":true,"_interviewing":false,"meta":{},"_lastSeen":1601752324712},"mapped":{"zigbeeModel":["lumi.sensor_magnet"],"model":"MCCGQ01LM","vendor":"Xiaomi","description":"MiJia door & window contact sensor","supports":"contact","meta":{"battery":{"voltageToPercentage":"CR2032"}},"fromZigbee":[{"cluster":"genBasic","type":["attributeReport","readResponse"]},{"cluster":"genOnOff","type":["attributeReport","readResponse"]}],"toZigbee":[]},"name":"0x00158d00042e3307"} incoming event: {"type":"attributeReport","device":{"ID":4,"_type":"EndDevice","_ieeeAddr":"0x00158d00042e3307","_networkAddress":10193,"_manufacturerID":4151,"_endpoints":[{"ID":1,"inputClusters":[],"outputClusters":[],"deviceNetworkAddress":10193,"deviceIeeeAddress":"0x00158d00042e3307","clusters":{"genBasic":{"attributes":{"65282":[{"elmType":16,"elmVal":0},{"elmType":33,"elmVal":3005},{"elmType":33,"elmVal":5032},{"elmType":36,"elmVal":[0,3]},{"elmType":33,"elmVal":254},{"elmType":32,"elmVal":90}],"modelId":"lumi.sensor_magnet","appVersion":10}},"genOnOff":{"attributes":{"onOff":0}}},"_binds":[],"meta":{}}],"_manufacturerName":"LUMI","_powerSource":"Battery","_modelID":"lumi.sensor_magnet","_applicationVersion":10,"_interviewCompleted":true,"_interviewing":false,"meta":{},"_lastSeen":1601752324712},"endpoint":"[Circular]","data":{"65282":"[Circular]"},"linkquality":139,"groupID":null,"cluster":"genBasic","meta":{"zclTransactionSequenceNumber":113,"manufacturerCode":4660,"frameControl":{"frameType":0,"manufacturerSpecific":true,"direction":1,"disableDefaultResponse":true,"reservedBits":0}}}
        2020-10-03 21:12:04.767 - debug: zigbee.0 (23436) Publish {"voltage":3005,"battery":100}
        2020-10-03 21:14:48.582 - debug: zigbee.0 (23436) Non-pingable device 0x000b57fffe59e779 V3-BTZB was last seen '6264.89' seconds ago.
        2020-10-03 21:14:48.588 - debug: zigbee.0 (23436) Non-pingable device 0x00158d000358efeb lumi.sensor_magnet was last seen '2440.644' seconds ago.
        2020-10-03 21:14:48.590 - debug: zigbee.0 (23436) Non-pingable device 0x00158d00042e3307 lumi.sensor_magnet was last seen '163.878' seconds ago.
        2020-10-03 21:19:48.582 - debug: zigbee.0 (23436) Non-pingable device 0x000b57fffe59e779 V3-BTZB was last seen '6564.89' seconds ago.
        2020-10-03 21:19:48.589 - debug: zigbee.0 (23436) Non-pingable device 0x00158d000358efeb lumi.sensor_magnet was last seen '2740.645' seconds ago.
        2020-10-03 21:19:48.592 - debug: zigbee.0 (23436) Non-pingable device 0x00158d00042e3307 lumi.sensor_magnet was last seen '463.88' seconds ago.
        2020-10-03 21:24:48.582 - debug: zigbee.0 (23436) Non-pingable device 0x000b57fffe59e779 V3-BTZB was last seen '6864.89' seconds ago.
        2020-10-03 21:24:48.590 - debug: zigbee.0 (23436) Non-pingable device 0x00158d000358efeb lumi.sensor_magnet was last seen '3040.645' seconds ago.
        2020-10-03 21:24:48.592 - debug: zigbee.0 (23436) Non-pingable device 0x00158d00042e3307 lumi.sensor_magnet was last seen '763.88' seconds ago.
        2020-10-03 21:27:03.399 - debug: zigbee.0 (23436) handleMessage. {"type":"attributeReport","device":{"ID":4,"_type":"EndDevice","_ieeeAddr":"0x00158d00042e3307","_networkAddress":10193,"_manufacturerID":4151,"_endpoints":[{"ID":1,"inputClusters":[],"outputClusters":[],"deviceNetworkAddress":10193,"deviceIeeeAddress":"0x00158d00042e3307","clusters":{"genBasic":{"attributes":{"65282":[{"elmType":16,"elmVal":0},{"elmType":33,"elmVal":3005},{"elmType":33,"elmVal":5032},{"elmType":36,"elmVal":[0,3]},{"elmType":33,"elmVal":254},{"elmType":32,"elmVal":90}],"modelId":"lumi.sensor_magnet","appVersion":10}},"genOnOff":{"attributes":{"onOff":1}}},"_binds":[],"meta":{}}],"_manufacturerName":"LUMI","_powerSource":"Battery","_modelID":"lumi.sensor_magnet","_applicationVersion":10,"_interviewCompleted":true,"_interviewing":false,"meta":{},"_lastSeen":1601753223397},"endpoint":"[Circular]","data":{"onOff":1},"linkquality":140,"groupID":null,"cluster":"genOnOff","meta":{"zclTransactionSequenceNumber":114,"manufacturerCode":null,"frameControl":{"frameType":0,"manufacturerSpecific":false,"direction":1,"disableDefaultResponse":true,"reservedBits":0}}}
        2020-10-03 21:27:03.402 - debug: zigbee.0 (23436) Received Zigbee message from '0x00158d00042e3307', type 'attributeReport', cluster 'genOnOff', data '{"onOff":1}' from endpoint 1 with groupID null
        2020-10-03 21:27:03.406 - debug: zigbee.0 (23436) Type attributeReport device {"type":"device","device":{"ID":4,"_type":"EndDevice","_ieeeAddr":"0x00158d00042e3307","_networkAddress":10193,"_manufacturerID":4151,"_endpoints":[{"ID":1,"inputClusters":[],"outputClusters":[],"deviceNetworkAddress":10193,"deviceIeeeAddress":"0x00158d00042e3307","clusters":{"genBasic":{"attributes":{"65282":[{"elmType":16,"elmVal":0},{"elmType":33,"elmVal":3005},{"elmType":33,"elmVal":5032},{"elmType":36,"elmVal":[0,3]},{"elmType":33,"elmVal":254},{"elmType":32,"elmVal":90}],"modelId":"lumi.sensor_magnet","appVersion":10}},"genOnOff":{"attributes":{"onOff":1}}},"_binds":[],"meta":{}}],"_manufacturerName":"LUMI","_powerSource":"Battery","_modelID":"lumi.sensor_magnet","_applicationVersion":10,"_interviewCompleted":true,"_interviewing":false,"meta":{},"_lastSeen":1601753223397},"mapped":{"zigbeeModel":["lumi.sensor_magnet"],"model":"MCCGQ01LM","vendor":"Xiaomi","description":"MiJia door & window contact sensor","supports":"contact","meta":{"battery":{"voltageToPercentage":"CR2032"}},"fromZigbee":[{"cluster":"genBasic","type":["attributeReport","readResponse"]},{"cluster":"genOnOff","type":["attributeReport","readResponse"]}],"toZigbee":[]},"name":"0x00158d00042e3307"} incoming event: {"type":"attributeReport","device":{"ID":4,"_type":"EndDevice","_ieeeAddr":"0x00158d00042e3307","_networkAddress":10193,"_manufacturerID":4151,"_endpoints":[{"ID":1,"inputClusters":[],"outputClusters":[],"deviceNetworkAddress":10193,"deviceIeeeAddress":"0x00158d00042e3307","clusters":{"genBasic":{"attributes":{"65282":[{"elmType":16,"elmVal":0},{"elmType":33,"elmVal":3005},{"elmType":33,"elmVal":5032},{"elmType":36,"elmVal":[0,3]},{"elmType":33,"elmVal":254},{"elmType":32,"elmVal":90}],"modelId":"lumi.sensor_magnet","appVersion":10}},"genOnOff":{"attributes":{"onOff":1}}},"_binds":[],"meta":{}}],"_manufacturerName":"LUMI","_powerSource":"Battery","_modelID":"lumi.sensor_magnet","_applicationVersion":10,"_interviewCompleted":true,"_interviewing":false,"meta":{},"_lastSeen":1601753223397},"endpoint":"[Circular]","data":{"onOff":1},"linkquality":140,"groupID":null,"cluster":"genOnOff","meta":{"zclTransactionSequenceNumber":114,"manufacturerCode":null,"frameControl":{"frameType":0,"manufacturerSpecific":false,"direction":1,"disableDefaultResponse":true,"reservedBits":0}}}
        2020-10-03 21:27:03.412 - debug: zigbee.0 (23436) Publish {"contact":false}
        2020-10-03 21:27:08.426 - debug: zigbee.0 (23436) handleMessage. {"type":"attributeReport","device":{"ID":4,"_type":"EndDevice","_ieeeAddr":"0x00158d00042e3307","_networkAddress":10193,"_manufacturerID":4151,"_endpoints":[{"ID":1,"inputClusters":[],"outputClusters":[],"deviceNetworkAddress":10193,"deviceIeeeAddress":"0x00158d00042e3307","clusters":{"genBasic":{"attributes":{"65282":[{"elmType":16,"elmVal":0},{"elmType":33,"elmVal":3005},{"elmType":33,"elmVal":5032},{"elmType":36,"elmVal":[0,3]},{"elmType":33,"elmVal":254},{"elmType":32,"elmVal":90}],"modelId":"lumi.sensor_magnet","appVersion":10}},"genOnOff":{"attributes":{"onOff":0}}},"_binds":[],"meta":{}}],"_manufacturerName":"LUMI","_powerSource":"Battery","_modelID":"lumi.sensor_magnet","_applicationVersion":10,"_interviewCompleted":true,"_interviewing":false,"meta":{},"_lastSeen":1601753228424},"endpoint":"[Circular]","data":{"onOff":0},"linkquality":140,"groupID":null,"cluster":"genOnOff","meta":{"zclTransactionSequenceNumber":115,"manufacturerCode":null,"frameControl":{"frameType":0,"manufacturerSpecific":false,"direction":1,"disableDefaultResponse":true,"reservedBits":0}}}
        2020-10-03 21:27:08.428 - debug: zigbee.0 (23436) Received Zigbee message from '0x00158d00042e3307', type 'attributeReport', cluster 'genOnOff', data '{"onOff":0}' from endpoint 1 with groupID null
        2020-10-03 21:27:08.431 - debug: zigbee.0 (23436) Type attributeReport device {"type":"device","device":{"ID":4,"_type":"EndDevice","_ieeeAddr":"0x00158d00042e3307","_networkAddress":10193,"_manufacturerID":4151,"_endpoints":[{"ID":1,"inputClusters":[],"outputClusters":[],"deviceNetworkAddress":10193,"deviceIeeeAddress":"0x00158d00042e3307","clusters":{"genBasic":{"attributes":{"65282":[{"elmType":16,"elmVal":0},{"elmType":33,"elmVal":3005},{"elmType":33,"elmVal":5032},{"elmType":36,"elmVal":[0,3]},{"elmType":33,"elmVal":254},{"elmType":32,"elmVal":90}],"modelId":"lumi.sensor_magnet","appVersion":10}},"genOnOff":{"attributes":{"onOff":0}}},"_binds":[],"meta":{}}],"_manufacturerName":"LUMI","_powerSource":"Battery","_modelID":"lumi.sensor_magnet","_applicationVersion":10,"_interviewCompleted":true,"_interviewing":false,"meta":{},"_lastSeen":1601753228424},"mapped":{"zigbeeModel":["lumi.sensor_magnet"],"model":"MCCGQ01LM","vendor":"Xiaomi","description":"MiJia door & window contact sensor","supports":"contact","meta":{"battery":{"voltageToPercentage":"CR2032"}},"fromZigbee":[{"cluster":"genBasic","type":["attributeReport","readResponse"]},{"cluster":"genOnOff","type":["attributeReport","readResponse"]}],"toZigbee":[]},"name":"0x00158d00042e3307"} incoming event: {"type":"attributeReport","device":{"ID":4,"_type":"EndDevice","_ieeeAddr":"0x00158d00042e3307","_networkAddress":10193,"_manufacturerID":4151,"_endpoints":[{"ID":1,"inputClusters":[],"outputClusters":[],"deviceNetworkAddress":10193,"deviceIeeeAddress":"0x00158d00042e3307","clusters":{"genBasic":{"attributes":{"65282":[{"elmType":16,"elmVal":0},{"elmType":33,"elmVal":3005},{"elmType":33,"elmVal":5032},{"elmType":36,"elmVal":[0,3]},{"elmType":33,"elmVal":254},{"elmType":32,"elmVal":90}],"modelId":"lumi.sensor_magnet","appVersion":10}},"genOnOff":{"attributes":{"onOff":0}}},"_binds":[],"meta":{}}],"_manufacturerName":"LUMI","_powerSource":"Battery","_modelID":"lumi.sensor_magnet","_applicationVersion":10,"_interviewCompleted":true,"_interviewing":false,"meta":{},"_lastSeen":1601753228424},"endpoint":"[Circular]","data":{"onOff":0},"linkquality":140,"groupID":null,"cluster":"genOnOff","meta":{"zclTransactionSequenceNumber":115,"manufacturerCode":null,"frameControl":{"frameType":0,"manufacturerSpecific":false,"direction":1,"disableDefaultResponse":true,"reservedBits":0}}}
        2020-10-03 21:27:08.437 - debug: zigbee.0 (23436) Publish {"contact":true}
        2020-10-03 21:27:15.071 - warn: javascript.0 (2144) You are assigning a string to the state "anwesenheit.0.pkommt" which expects a boolean. Please fix your code to use a boolean or change the state type to string. This warning might become an error in future versions.
        2020-10-03 21:27:15.078 - warn: javascript.0 (2144) at setState (/opt/iobroker/node_modules/iobroker.javascript/lib/sandbox.js:1355:20)
        2020-10-03 21:27:15.080 - warn: javascript.0 (2144) at Object. (script.js.anwesenheit.kommtgeht:5:5)
        2020-10-03 21:27:15.080 - warn: javascript.0 (2144) at Object.callback (/opt/iobroker/node_modules/iobroker.javascript/lib/sandbox.js:1052:38)
        2020-10-03 21:27:15.081 - warn: javascript.0 (2144) at Object.stateChange (/opt/iobroker/node_modules/iobroker.javascript/main.js:451:25)
        2020-10-03 21:27:15.082 - warn: javascript.0 (2144) at Immediate._onImmediate (/opt/iobroker/node_modules/iobroker.js-controller/lib/adapter.js:5384:37)
        2020-10-03 21:27:15.084 - warn: javascript.0 (2144) at processImmediate (internal/timers.js:456:21)
        2020-10-03 21:28:00.358 - debug: cloud.0 (1434) system.adapter.admin.0: logging true
        2020-10-03 21:28:00.382 - debug: zigbee.0 (23436) system.adapter.admin.0: logging true
        2020-10-03 21:28:00.372 - debug: scenes.0 (2550) system.adapter.admin.0: logging true
        
        
        AsgothianA Offline
        AsgothianA Offline
        Asgothian
        Developer
        schrieb am zuletzt editiert von
        #121

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

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

        1 Antwort Letzte Antwort
        0
        • AsgothianA Asgothian

          @Jan-Puchta
          Prinzipiell geht das.

          Nutzt du das Schloss ?

          Wenn ja würde mich interessieren ob die aktualisierungsprobkeme bei dir mit der gepatchten Version noch auftreten oder weg sind.

          A.

          Jan PuchtaJ Offline
          Jan PuchtaJ Offline
          Jan Puchta
          schrieb am zuletzt editiert von
          #122

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

          AsgothianA 1 Antwort Letzte Antwort
          0
          • Jan PuchtaJ Jan Puchta

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

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

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

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

            Jan PuchtaJ 1 Antwort Letzte Antwort
            0
            • AsgothianA Asgothian

              @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 PuchtaJ Offline
              Jan PuchtaJ Offline
              Jan Puchta
              schrieb am zuletzt editiert von
              #124

              @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)
              
              AsgothianA 1 Antwort Letzte Antwort
              0
              • Jan PuchtaJ Jan Puchta

                @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)
                
                AsgothianA Offline
                AsgothianA Offline
                Asgothian
                Developer
                schrieb am zuletzt editiert von
                #125

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

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

                Jan PuchtaJ 1 Antwort Letzte Antwort
                0
                • AsgothianA Asgothian

                  @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 PuchtaJ Offline
                  Jan PuchtaJ Offline
                  Jan Puchta
                  schrieb am zuletzt editiert von
                  #126

                  @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

                  AsgothianA 1 Antwort Letzte Antwort
                  0
                  • Jan PuchtaJ Jan Puchta

                    @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

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

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

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

                    Jan PuchtaJ 2 Antworten Letzte Antwort
                    0
                    • AsgothianA Asgothian

                      @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 PuchtaJ Offline
                      Jan PuchtaJ Offline
                      Jan Puchta
                      schrieb am zuletzt editiert von
                      #128

                      @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 Antwort Letzte Antwort
                      0
                      • AsgothianA Asgothian

                        @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 PuchtaJ Offline
                        Jan PuchtaJ Offline
                        Jan Puchta
                        schrieb am zuletzt editiert von
                        #129

                        @Asgothian

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

                        AsgothianA 1 Antwort Letzte Antwort
                        0
                        • Jan PuchtaJ Jan Puchta

                          @Asgothian

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

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

                          @Jan-Puchta funktioniert denn das lock oder unlock ?

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

                          Jan PuchtaJ 2 Antworten Letzte Antwort
                          0
                          • AsgothianA Asgothian

                            @Jan-Puchta funktioniert denn das lock oder unlock ?

                            Jan PuchtaJ Offline
                            Jan PuchtaJ Offline
                            Jan Puchta
                            schrieb am zuletzt editiert von
                            #131

                            @Asgothian

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

                            AsgothianA 1 Antwort Letzte Antwort
                            0
                            • Jan PuchtaJ Jan Puchta

                              @Asgothian

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

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

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

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

                              Jan PuchtaJ 1 Antwort Letzte Antwort
                              0
                              • AsgothianA Asgothian

                                @Jan-Puchta funktioniert denn das lock oder unlock ?

                                Jan PuchtaJ Offline
                                Jan PuchtaJ Offline
                                Jan Puchta
                                schrieb am zuletzt editiert von
                                #133

                                @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 Antwort Letzte Antwort
                                0
                                • AsgothianA Asgothian

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

                                  Jan PuchtaJ Offline
                                  Jan PuchtaJ Offline
                                  Jan Puchta
                                  schrieb am zuletzt editiert von
                                  #134

                                  @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
                                  
                                  AsgothianA 1 Antwort Letzte Antwort
                                  0
                                  • Jan PuchtaJ Jan Puchta

                                    @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
                                    
                                    AsgothianA Offline
                                    AsgothianA Offline
                                    Asgothian
                                    Developer
                                    schrieb am zuletzt editiert von
                                    #135

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

                                    A.

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

                                    Jan PuchtaJ 3 Antworten Letzte Antwort
                                    0
                                    • AsgothianA Asgothian

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

                                      A.

                                      Jan PuchtaJ Offline
                                      Jan PuchtaJ Offline
                                      Jan Puchta
                                      schrieb am zuletzt editiert von
                                      #136

                                      @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 Antwort Letzte Antwort
                                      0
                                      • AsgothianA Asgothian

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

                                        A.

                                        Jan PuchtaJ Offline
                                        Jan PuchtaJ Offline
                                        Jan Puchta
                                        schrieb am zuletzt editiert von
                                        #137

                                        @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 Antwort Letzte Antwort
                                        0
                                        • Jan PuchtaJ Jan Puchta

                                          @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 Offline
                                          P Offline
                                          patrick039212
                                          schrieb am zuletzt editiert von patrick039212
                                          #138

                                          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 Antwort Letzte Antwort
                                          0
                                          Antworten
                                          • In einem neuen Thema antworten
                                          Anmelden zum Antworten
                                          • Älteste zuerst
                                          • Neuste zuerst
                                          • Meiste Stimmen


                                          Support us

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

                                          426

                                          Online

                                          32.5k

                                          Benutzer

                                          81.6k

                                          Themen

                                          1.3m

                                          Beiträge
                                          Community
                                          Impressum | Datenschutz-Bestimmungen | Nutzungsbedingungen | Einwilligungseinstellungen
                                          ioBroker Community 2014-2025
                                          logo
                                          • Anmelden

                                          • Du hast noch kein Konto? Registrieren

                                          • Anmelden oder registrieren, um zu suchen
                                          • Erster Beitrag
                                            Letzter Beitrag
                                          0
                                          • Home
                                          • Aktuell
                                          • Tags
                                          • Ungelesen 0
                                          • Kategorien
                                          • Unreplied
                                          • Beliebt
                                          • GitHub
                                          • Docu
                                          • Hilfe