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

  1. ioBroker Community Home
  2. Deutsch
  3. Tester
  4. Zigbee Adapter und Conbee Unterstützung

NEWS

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

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

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

Zigbee Adapter und Conbee Unterstützung

Geplant Angeheftet Gesperrt Verschoben Tester
zigbeeconbeedeconzersatz
235 Beiträge 48 Kommentatoren 57.6k Aufrufe 46 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.
  • PlasmachefP Plasmachef

    Hallo!

    Bin hier grad am Testen und versuche meinen Raspi Pi 4 mit Raspbee II und dem Danalock zusammen zubringen.

    • Raspbee II eingesteckt und die raspi-config umgestellt
    • Zigbee über Katze geladen, Instanz angelegt und den Adapter ausgewählt

    --> Instanz grün :-)

    Instanz und Danalock V3 auf pairing ... jetzt kommts:

    2020-04-28 17:50:04.559 - info: zigbee.0 (14579) Starting interview of '0x000b57fffe46ebec'
    2020-04-28 17:50:16.207 - info: zigbee.0 (14579) Successfully interviewed '0x000b57fffe46ebec', device has succesfully been paired
    2020-04-28 17:50:16.207 - info: zigbee.0 (14579) Device '0x000b57fffe46ebec' is supported, identified as: Danalock BT/ZB smartlock (V3-BTZB)
    2020-04-28 17:50:16.209 - info: zigbee.0 (14579) Configuring 0x000b57fffe46ebec V3-BTZB
    2020-04-28 17:50:18.218 - error: zigbee.0 (14579) Failed to configure 0x000b57fffe46ebec V3-BTZB, attempt 1 (Error: ConfigureReporting 0x000b57fffe46ebec/1 closuresDoorLock([{"attribute":"lockState","minimumReportInterval":0,"maximumReportInterval":3600,"reportableChange":0}], {"timeout":10000,"manufacturerCode":null,"disableDefaultResponse":true}) failed (Error: Status 'INVALID_DATA_TYPE')
    at Endpoint. (/opt/iobroker/node_modules/zigbee-herdsman/dist/controller/model/endpoint.js:326:23)
    at Generator.next ()
    at fulfilled (/opt/iobroker/node_modules/zigbee-herdsman/dist/controller/model/endpoint.js:5:58))
    2020-04-28 17:50:43.201 - info: zigbee.0 (14579) Zigbee: stop joining
    2020-04-28 17:50:50.582 - info: zigbee.0 (14579) Configuring 0x000b57fffe46ebec V3-BTZB
    2020-04-28 17:50:53.099 - error: zigbee.0 (14579) Failed to configure 0x000b57fffe46ebec V3-BTZB, attempt 2 (Error: ConfigureReporting 0x000b57fffe46ebec/1 closuresDoorLock([{"attribute":"lockState","minimumReportInterval":0,"maximumReportInterval":3600,"reportableChange":0}], {"timeout":10000,"manufacturerCode":null,"disableDefaultResponse":true}) failed (Error: Status 'INVALID_DATA_TYPE')
    at Endpoint. (/opt/iobroker/node_modules/zigbee-herdsman/dist/controller/model/endpoint.js:326:23)
    at Generator.next ()
    at fulfilled (/opt/iobroker/node_modules/zigbee-herdsman/dist/controller/model/endpoint.js:5:58))
    

    Es werde zwar ein paar Objekte angelegt und er erkennt auch locked und unlocked, aber das wars.

    Bitte um Hilfe

    Grüße Plasma

    GlasfaserG Offline
    GlasfaserG Offline
    Glasfaser
    schrieb am zuletzt editiert von Glasfaser
    #78

    @Plasmachef

    Hier ein Thread zb. Link Text
    und gebe auch dein Zigbee Adapter Version an .

    Synology 918+ 16GB - ioBroker in Docker v9 , VISO auf Trekstor Primebook C13 13,3" , Hikvision Domkameras mit Surveillance Station .. CCU RaspberryMatic in Synology VM .. Zigbee CC2538+CC2592 .. Sonoff .. KNX .. Modbus ..

    1 Antwort Letzte Antwort
    0
    • GlasfaserG Glasfaser

      @Plasmachef sagte in Zigbee Adapter und Conbee Unterstützung:

      mit Raspbee II

      Hier im Thread geht es um Zigbee Adapter und Conbee Unterstützung

      PlasmachefP Offline
      PlasmachefP Offline
      Plasmachef
      schrieb am zuletzt editiert von
      #79

      @Glasfaser sorry, dachte, da der Adapter beides kann bin ich hier auch richtig...

      "ioBroker adapter for Zigbee devices via TI cc2531/cc2530/cc26x2r/cc2538 and deCONZ ConBee/RaspBee"

      1 Antwort Letzte Antwort
      0
      • GlasfaserG Glasfaser

        @Plasmachef sagte in Zigbee Adapter und Conbee Unterstützung:

        mit Raspbee II

        Hier im Thread geht es um Zigbee Adapter und Conbee Unterstützung

        PlasmachefP Offline
        PlasmachefP Offline
        Plasmachef
        schrieb am zuletzt editiert von
        #80

        @Glasfaser... so... habe für Samstag das Teil bestellt... sollte der Fehler wieder auftreten, was ich vermute, dann bin ich wieder da :blush:

        PlasmachefP 1 Antwort Letzte Antwort
        0
        • justrJ justr

          @arteck
          Ich bin begeistert! Ich hatte bisher keine Lösung gefunden, den Conbee II unter MacOS zum Laufen zu bekommen. Lediglich in einer Linux-VitualBox mit Phoscon funktionierte er. Das hat aber gereicht, dass der Lüfter im Wohnzimmer-Mac durchgehend rauschte, was den WAF zunichte gemacht hat. Selbst von Dresden-Elektronik gab es lediglich vage Andeutungen aus 2018. Was soll ich sagen? Mit dem aktuellen Zigbee-Adapter läuft alles wie geschmiert! Keine zusätzlichen Treiber nötig. Einfach den Conbee II eingesteckt und den USB-Port (/dev/tty.usbmodemDE21342711) in den Settings ausgewählt, fertig! Ok, musste den Adapter ein paar mal neu starten. Die Settings ließen sich erst nach einem restart öffnen. Und nach dem Auswählen des Conbee musste ich auch noch mal neu starten, damit ich den USB-Port auswählen konnte.

          Vielen Dank! :sunglasses:

          c_hoch_bC Offline
          c_hoch_bC Offline
          c_hoch_b
          schrieb am zuletzt editiert von
          #81

          @justr gut zu Lesen. Der Umzug von DeConz zum Zigbee wird mein UrlaubsProjekt :-)
          Ich habe ja die Hoffnung, dass die mit dem Stick verbundenen Geräte automatisch vom Zigbee-Adapter erkannt werden...?
          Wenn nicht, wird das viel Arbeit.

          Naja, für uns SmartHome-Nerds liegt die Frusttolleranz ja höher ;-) - nur nicht bei meiner besseren hälfte :-)

          Raspi 4, MacOS, CCU 2, Conbee2, HomeKit/ Yahka, Homebridge, Hue,-Bulb/Switches/Sensors, Harmony, Kodi, Tado, Osram, Xiaomi, HomeMatic, Marantz, VU+, Alexa (Echo‘s)

          justrJ 1 Antwort Letzte Antwort
          0
          • c_hoch_bC c_hoch_b

            @justr gut zu Lesen. Der Umzug von DeConz zum Zigbee wird mein UrlaubsProjekt :-)
            Ich habe ja die Hoffnung, dass die mit dem Stick verbundenen Geräte automatisch vom Zigbee-Adapter erkannt werden...?
            Wenn nicht, wird das viel Arbeit.

            Naja, für uns SmartHome-Nerds liegt die Frusttolleranz ja höher ;-) - nur nicht bei meiner besseren hälfte :-)

            justrJ Offline
            justrJ Offline
            justr
            schrieb am zuletzt editiert von
            #82

            @c_hoch_b Viel Erfolg! Ich musste die Devices leider neu anlernen. Evtl. hatte ich aber zu viel rumprobiert und dabei die Config verloren. Allerdings verliere ich alle paar Tage (einmal beim Einrichten und dann noch einmal in den letzten 10 Tagen) die Verbindung zum Conbee ohne Info-, Warn- oder Fehlermeldung. Auch die Instanz bleibt grün. Nach einem Restart der Instanz läuft aber alles wieder. Wenn es weiterhin passiert, werde ich mir wohl ein kleines Restart-Skript schreiben, welches triggert, wenn einer der Timestamps für die "link_quality" der Devices seit mehr als einer Stunde nicht mehr aktualisiert wurde. Wenn es aber immer erst nach mehreren Tagen passiert, reicht auch ein Auto-Restart jede Nacht. Werde es weiter beobachten...

            c_hoch_bC 1 Antwort Letzte Antwort
            1
            • justrJ justr

              @c_hoch_b Viel Erfolg! Ich musste die Devices leider neu anlernen. Evtl. hatte ich aber zu viel rumprobiert und dabei die Config verloren. Allerdings verliere ich alle paar Tage (einmal beim Einrichten und dann noch einmal in den letzten 10 Tagen) die Verbindung zum Conbee ohne Info-, Warn- oder Fehlermeldung. Auch die Instanz bleibt grün. Nach einem Restart der Instanz läuft aber alles wieder. Wenn es weiterhin passiert, werde ich mir wohl ein kleines Restart-Skript schreiben, welches triggert, wenn einer der Timestamps für die "link_quality" der Devices seit mehr als einer Stunde nicht mehr aktualisiert wurde. Wenn es aber immer erst nach mehreren Tagen passiert, reicht auch ein Auto-Restart jede Nacht. Werde es weiter beobachten...

              c_hoch_bC Offline
              c_hoch_bC Offline
              c_hoch_b
              schrieb am zuletzt editiert von
              #83

              @justr danke für die Info und Hinweis! Dann verzweifle ich nicht gleich :).

              Und es ist ja noch Beta, vlt. wird das Problem ja noch behoben...

              Raspi 4, MacOS, CCU 2, Conbee2, HomeKit/ Yahka, Homebridge, Hue,-Bulb/Switches/Sensors, Harmony, Kodi, Tado, Osram, Xiaomi, HomeMatic, Marantz, VU+, Alexa (Echo‘s)

              1 Antwort Letzte Antwort
              0
              • arteckA arteck

                @Schuko80 mit den schnippseln kann ich nix anfagen

                stell mal bitte ordentliches LOG rein

                vor allem was wann sich verabschiedet wenn du es nochvolziehen kannst

                Schuko80S Offline
                Schuko80S Offline
                Schuko80
                schrieb am zuletzt editiert von
                #84

                @arteck sagte in Zigbee Adapter und Conbee Unterstützung:

                @Schuko80 mit den schnippseln kann ich nix anfagen

                stell mal bitte ordentliches LOG rein

                vor allem was wann sich verabschiedet wenn du es nochvolziehen kannst

                Da verabschiedet sich gar nichts, es läuft gar nicht erst:

                • Conbee wird erkannt
                • scannen nach Devices -> OK
                • Device wird richtig erkannt -> zu 90% OK, sonst noch mal löschen und neu pairen -> OK
                  -Status in Objekte -> availabel = true - alles andere ist leer
                • Steuern einer Ikea Lampe geht, wenn ich state auf true setze.

                Kachel in Zigbee zeigt keine Verbindung

                Log wie folgt:

                zigbee.0	2020-04-29 20:00:56.192	debug	(2343) sendTo "getBinding" to system.adapter.admin.0 from system.adapter.zigbee.0
                zigbee.0	2020-04-29 20:00:56.191	debug	(2343) getBinding result: []
                zigbee.0	2020-04-29 20:00:55.203	debug	(2343) sendTo "getDevices" to system.adapter.admin.0 from system.adapter.zigbee.0
                zigbee.0	2020-04-29 20:00:55.202	debug	(2343) getDevices result: [{"type":"device","common":{"name":"TRADFRI bulb E27 WS clear 950lm","type":"TRADFRI bulb E27 WS clear 950lm","icon":"img/ikea_bulb_E27.png"},"native":{"id":"000b57fffe2289d7
                zigbee.0	2020-04-29 20:00:55.196	debug	(2343) sendTo "getBinding" to system.adapter.admin.0 from system.adapter.zigbee.0
                zigbee.0	2020-04-29 20:00:55.195	debug	(2343) getBinding result: []
                zigbee.0	2020-04-29 20:00:54.766	debug	(2343) sendTo "getDevices" to system.adapter.admin.0 from system.adapter.zigbee.0
                zigbee.0	2020-04-29 20:00:54.766	debug	(2343) getDevices result: [{"type":"device","common":{"name":"TRADFRI bulb E27 WS clear 950lm","type":"TRADFRI bulb E27 WS clear 950lm","icon":"img/ikea_bulb_E27.png"},"native":{"id":"000b57fffe2289d7
                zigbee.0	2020-04-29 20:00:54.655	debug	(2343) new device 0x000b57fffe2289d7 42472 TRADFRI bulb E27 WS clear 950lm
                zigbee.0	2020-04-29 20:00:54.650	debug	(2343) New device event: {"type":"device","device":{"ID":3,"_type":"Router","_ieeeAddr":"0x000b57fffe2289d7","_networkAddress":42472,"_manufacturerID":4476,"_endpoints":[{"ID":1,"profileID":260,"devic
                zigbee.0	2020-04-29 20:00:54.648	info	(2343) Device '0x000b57fffe2289d7' is supported, identified as: IKEA TRADFRI LED bulb E26/E27 950 lumen, dimmable, white spectrum, clear (LED1546G12)
                zigbee.0	2020-04-29 20:00:54.648	info	(2343) Successfully interviewed '0x000b57fffe2289d7', device has succesfully been paired
                zigbee.0	2020-04-29 20:00:54.647	debug	(2343) handleDeviceInterview. {"status":"successful","device":{"ID":3,"_type":"Router","_ieeeAddr":"0x000b57fffe2289d7","_networkAddress":42472,"_manufacturerID":4476,"_endpoints":[{"ID":1,"profileID"
                zigbee.0	2020-04-29 20:00:54.485	debug	(2343) Type readResponse device {"type":"device","device":{"ID":3,"_type":"Router","_ieeeAddr":"0x000b57fffe2289d7","_networkAddress":42472,"_manufacturerID":4476,"_endpoints":[{"ID":1,"profileID":260
                zigbee.0	2020-04-29 20:00:54.484	debug	(2343) Received Zigbee message from '0x000b57fffe2289d7', type 'readResponse', cluster 'genBasic', data '{"swBuildId":"2.3.007"}' from endpoint 1 with groupID null
                zigbee.0	2020-04-29 20:00:54.483	debug	(2343) handleMessage. {"type":"readResponse","device":{"ID":3,"_type":"Router","_ieeeAddr":"0x000b57fffe2289d7","_networkAddress":42472,"_manufacturerID":4476,"_endpoints":[{"ID":1,"profileID":260,"de
                zigbee.0	2020-04-29 20:00:54.342	debug	(2343) Type readResponse device {"type":"device","device":{"ID":3,"_type":"Router","_ieeeAddr":"0x000b57fffe2289d7","_networkAddress":42472,"_manufacturerID":4476,"_endpoints":[{"ID":1,"profileID":260
                zigbee.0	2020-04-29 20:00:54.341	debug	(2343) Received Zigbee message from '0x000b57fffe2289d7', type 'readResponse', cluster 'genBasic', data '{"dateCode":"20190520"}' from endpoint 1 with groupID null
                zigbee.0	2020-04-29 20:00:54.339	debug	(2343) handleMessage. {"type":"readResponse","device":{"ID":3,"_type":"Router","_ieeeAddr":"0x000b57fffe2289d7","_networkAddress":42472,"_manufacturerID":4476,"_endpoints":[{"ID":1,"profileID":260,"de
                zigbee.0	2020-04-29 20:00:54.183	debug	(2343) Type readResponse device {"type":"device","device":{"ID":3,"_type":"Router","_ieeeAddr":"0x000b57fffe2289d7","_networkAddress":42472,"_manufacturerID":4476,"_endpoints":[{"ID":1,"profileID":260
                zigbee.0	2020-04-29 20:00:54.182	debug	(2343) Received Zigbee message from '0x000b57fffe2289d7', type 'readResponse', cluster 'genBasic', data '{"hwVersion":1}' from endpoint 1 with groupID null
                zigbee.0	2020-04-29 20:00:54.179	debug	(2343) handleMessage. {"type":"readResponse","device":{"ID":3,"_type":"Router","_ieeeAddr":"0x000b57fffe2289d7","_networkAddress":42472,"_manufacturerID":4476,"_endpoints":[{"ID":1,"profileID":260,"de
                zigbee.0	2020-04-29 20:00:54.038	debug	(2343) Type readResponse device {"type":"device","device":{"ID":3,"_type":"Router","_ieeeAddr":"0x000b57fffe2289d7","_networkAddress":42472,"_manufacturerID":4476,"_endpoints":[{"ID":1,"profileID":260
                zigbee.0	2020-04-29 20:00:54.037	debug	(2343) Received Zigbee message from '0x000b57fffe2289d7', type 'readResponse', cluster 'genBasic', data '{"stackVersion":98}' from endpoint 1 with groupID null
                zigbee.0	2020-04-29 20:00:54.035	debug	(2343) handleMessage. {"type":"readResponse","device":{"ID":3,"_type":"Router","_ieeeAddr":"0x000b57fffe2289d7","_networkAddress":42472,"_manufacturerID":4476,"_endpoints":[{"ID":1,"profileID":260,"de
                zigbee.0	2020-04-29 20:00:53.877	debug	(2343) Type readResponse device {"type":"device","device":{"ID":3,"_type":"Router","_ieeeAddr":"0x000b57fffe2289d7","_networkAddress":42472,"_manufacturerID":4476,"_endpoints":[{"ID":1,"profileID":260
                zigbee.0	2020-04-29 20:00:53.877	debug	(2343) Received Zigbee message from '0x000b57fffe2289d7', type 'readResponse', cluster 'genBasic', data '{"appVersion":33}' from endpoint 1 with groupID null
                zigbee.0	2020-04-29 20:00:53.875	debug	(2343) handleMessage. {"type":"readResponse","device":{"ID":3,"_type":"Router","_ieeeAddr":"0x000b57fffe2289d7","_networkAddress":42472,"_manufacturerID":4476,"_endpoints":[{"ID":1,"profileID":260,"de
                zigbee.0	2020-04-29 20:00:53.735	debug	(2343) Type readResponse device {"type":"device","device":{"ID":3,"_type":"Router","_ieeeAddr":"0x000b57fffe2289d7","_networkAddress":42472,"_manufacturerID":4476,"_endpoints":[{"ID":1,"profileID":260
                zigbee.0	2020-04-29 20:00:53.734	debug	(2343) Received Zigbee message from '0x000b57fffe2289d7', type 'readResponse', cluster 'genBasic', data '{"zclVersion":3}' from endpoint 1 with groupID null
                zigbee.0	2020-04-29 20:00:53.731	debug	(2343) handleMessage. {"type":"readResponse","device":{"ID":3,"_type":"Router","_ieeeAddr":"0x000b57fffe2289d7","_networkAddress":42472,"_manufacturerID":4476,"_endpoints":[{"ID":1,"profileID":260,"de
                zigbee.0	2020-04-29 20:00:53.589	debug	(2343) Type readResponse device {"type":"device","device":{"ID":3,"_type":"Router","_ieeeAddr":"0x000b57fffe2289d7","_networkAddress":42472,"_manufacturerID":4476,"_endpoints":[{"ID":1,"profileID":260
                zigbee.0	2020-04-29 20:00:53.588	debug	(2343) Received Zigbee message from '0x000b57fffe2289d7', type 'readResponse', cluster 'genBasic', data '{"powerSource":1}' from endpoint 1 with groupID null
                zigbee.0	2020-04-29 20:00:53.587	debug	(2343) handleMessage. {"type":"readResponse","device":{"ID":3,"_type":"Router","_ieeeAddr":"0x000b57fffe2289d7","_networkAddress":42472,"_manufacturerID":4476,"_endpoints":[{"ID":1,"profileID":260,"de
                zigbee.0	2020-04-29 20:00:53.430	debug	(2343) Type readResponse device {"type":"device","device":{"ID":3,"_type":"Router","_ieeeAddr":"0x000b57fffe2289d7","_networkAddress":42472,"_manufacturerID":4476,"_endpoints":[{"ID":1,"profileID":260
                zigbee.0	2020-04-29 20:00:53.429	debug	(2343) Received Zigbee message from '0x000b57fffe2289d7', type 'readResponse', cluster 'genBasic', data '{"manufacturerName":"IKEA of Sweden"}' from endpoint 1 with groupID null
                zigbee.0	2020-04-29 20:00:53.427	debug	(2343) handleMessage. {"type":"readResponse","device":{"ID":3,"_type":"Router","_ieeeAddr":"0x000b57fffe2289d7","_networkAddress":42472,"_manufacturerID":4476,"_endpoints":[{"ID":1,"profileID":260,"de
                zigbee.0	2020-04-29 20:00:53.301	debug	(2343) Wrong device 000b57fffe2289d7 null
                zigbee.0	2020-04-29 20:00:53.294	debug	(2343) Publish available for 0x000b57fffe2289d7 = true
                zigbee.0	2020-04-29 20:00:53.291	debug	(2343) Type readResponse device {"type":"device","device":{"ID":3,"_type":"Router","_ieeeAddr":"0x000b57fffe2289d7","_networkAddress":42472,"_manufacturerID":4476,"_endpoints":[{"ID":1,"profileID":260
                zigbee.0	2020-04-29 20:00:53.289	debug	(2343) Received Zigbee message from '0x000b57fffe2289d7', type 'readResponse', cluster 'genBasic', data '{"modelId":"TRADFRI bulb E27 WS clear 950lm"}' from endpoint 1 with groupID null
                zigbee.0	2020-04-29 20:00:53.285	debug	(2343) handleMessage. {"type":"readResponse","device":{"ID":3,"_type":"Router","_ieeeAddr":"0x000b57fffe2289d7","_networkAddress":42472,"_manufacturerID":4476,"_endpoints":[{"ID":1,"profileID":260,"de
                zigbee.0	2020-04-29 20:00:27.341	debug	(2343) User stateChange zigbee.0.info.pairingMode {"val":false,"ack":false,"ts":1588183227336,"q":0,"from":"system.adapter.zigbee.0","user":"system.user.admin","lc":1588182011624}
                zigbee.0	2020-04-29 20:00:27.335	info	(2343) Zigbee: stop joining
                zigbee.0	2020-04-29 20:00:10.650	debug	(2343) Failed to get map: "TypeError: Cannot read property 'stack' of undefined\n at ZigbeeController.getMap (/opt/iobroker/node_modules/iobroker.zigbee/lib/zigbeecontroller.js:536:115)"
                zigbee.0	2020-04-29 19:59:51.834	info	(2343) Starting interview of '0x000b57fffe2289d7'
                zigbee.0	2020-04-29 19:59:51.831	debug	(2343) handleDeviceInterview. {"status":"started","device":{"ID":3,"_ieeeAddr":"0x000b57fffe2289d7","_networkAddress":42472,"_endpoints":[],"_interviewCompleted":false,"_interviewing":false,"meta":{},
                zigbee.0	2020-04-29 19:59:51.830	debug	(2343) handleDeviceJoined. {"device":{"ID":3,"_ieeeAddr":"0x000b57fffe2289d7","_networkAddress":42472,"_endpoints":[],"_interviewCompleted":false,"_interviewing":false,"meta":{},"_lastSeen":null}}
                zigbee.0	2020-04-29 19:59:25.996	debug	(2343) sendTo "letsPairing" to system.adapter.admin.0 from system.adapter.zigbee.0: Start pairing!
                zigbee.0	2020-04-29 19:59:25.996	info	(2343) Zigbee: allowing new devices to join.
                zigbee.0	2020-04-29 19:59:10.534	debug	(2343) LQI succeeded for 'Coordinator'
                zigbee.0	2020-04-29 19:59:09.477	debug	(2343) sendTo "listUart" to system.adapter.admin.0 from system.adapter.zigbee.0
                zigbee.0	2020-04-29 19:59:09.476	debug	(2343) List of ports: [{"comName":"/dev/ttyACM0"},{"comName":"/dev/ttyUSB0"},{"comName":"/dev/ttyS0"},{"comName":"/dev/ttyS1"},{"comName":"/dev/ttyS10"},{"comName":"/dev/ttyS11"},{"comName":"/dev/ttyS
                zigbee.0	2020-04-29 19:59:09.455	debug	(2343) sendTo "getBinding" to system.adapter.admin.0 from system.adapter.zigbee.0
                zigbee.0	2020-04-29 19:59:09.454	debug	(2343) getBinding result: []
                zigbee.0	2020-04-29 19:59:09.330	debug	(2343) sendTo "getDevices" to system.adapter.admin.0 from system.adapter.zigbee.0
                zigbee.0	2020-04-29 19:59:09.330	debug	(2343) getDevices result: [{"_id":"0x00212effff00b043","icon":"img/unknown.png","paired":true,"info":{"type":"device","device":{"ID":1,"_type":"Coordinator","_ieeeAddr":"0x00212effff00b043","_networkA
                zigbee.0	2020-04-29 19:59:09.285	debug	(2343) sendTo "getGroups" to system.adapter.admin.0 from system.adapter.zigbee.0
                zigbee.0	2020-04-29 19:59:09.285	debug	(2343) getGroups result: {}
                zigbee.0	2020-04-29 19:59:09.280	debug	(2343) sendTo "getLibData" to system.adapter.admin.0 from system.adapter.zigbee.0
                zigbee.0	2020-04-29 19:59:01.750	debug	(2343) User stateChange zigbee.0.info.pairingMode {"val":false,"ack":false,"ts":1588183141743,"q":0,"from":"system.adapter.zigbee.0","user":"system.user.admin","lc":1588182011624}
                zigbee.0	2020-04-29 19:59:01.742	info	(2343) Zigbee: stop joining
                zigbee.0	2020-04-29 19:58:59.628	debug	(2343) Failed to get map: "TypeError: Cannot read property 'stack' of undefined\n at ZigbeeController.getMap (/opt/iobroker/node_modules/iobroker.zigbee/lib/zigbeecontroller.js:536:115)"
                zigbee.0	2020-04-29 19:58:00.435	debug	(2343) sendTo "letsPairing" to system.adapter.admin.0 from system.adapter.zigbee.0: Start pairing!
                zigbee.0	2020-04-29 19:58:00.433	info	(2343) Zigbee: allowing new devices to join.
                zigbee.0	2020-04-29 19:57:59.379	debug	(2343) LQI succeeded for 'Coordinator'
                zigbee.0	2020-04-29 19:57:58.353	debug	(2343) sendTo "getBinding" to system.adapter.admin.0 from system.adapter.zigbee.0
                zigbee.0	2020-04-29 19:57:58.352	debug	(2343) getBinding result: []
                zigbee.0	2020-04-29 19:57:58.301	debug	(2343) sendTo "listUart" to system.adapter.admin.0 from system.adapter.zigbee.0
                zigbee.0	2020-04-29 19:57:58.300	debug	(2343) List of ports: [{"comName":"/dev/ttyACM0"},{"comName":"/dev/ttyUSB0"},{"comName":"/dev/ttyS0"},{"comName":"/dev/ttyS1"},{"comName":"/dev/ttyS10"},{"comName":"/dev/ttyS11"},{"comName":"/dev/ttyS
                zigbee.0	2020-04-29 19:57:58.184	debug	(2343) sendTo "getDevices" to system.adapter.admin.0 from system.adapter.zigbee.0
                zigbee.0	2020-04-29 19:57:58.183	debug	(2343) getDevices result: [{"_id":"0x00212effff00b043","icon":"img/unknown.png","paired":true,"info":{"type":"device","device":{"ID":1,"_type":"Coordinator","_ieeeAddr":"0x00212effff00b043","_networkA
                zigbee.0	2020-04-29 19:57:58.130	debug	(2343) sendTo "getGroups" to system.adapter.admin.0 from system.adapter.zigbee.0
                zigbee.0	2020-04-29 19:57:58.130	debug	(2343) getGroups result: {}
                zigbee.0	2020-04-29 19:57:58.120	debug	(2343) sendTo "getLibData" to system.adapter.admin.0 from system.adapter.zigbee.0
                zigbee.0	2020-04-29 19:57:41.990	info	(2343) Zigbee started
                

                bulb.PNG

                Nuc6cayh + Proxmox / Zigbee (Deconz / Conbee I ) / ZWave / Homematic (CCU2)

                1 Antwort Letzte Antwort
                0
                • M MartinMuc

                  Meine Hue Lampen funktionieren einwandfrei mit dem ConbeeII, ich habe allerdings Probleme mit den HUE Bewegungsmeldern und Schaltern.

                  Beim Bewegungsmelder bekomme ich beim anlernen folgenden Fehler, das hat zur folge das er zwar angezegit wird, aber ich keine Daten empfange. Selbst PRoblem besteht bei dem Dimmerschalter.

                  Hat jemand eine Idee was hier krumm sein könnte ? Version ist die 1.1.0.0

                  Danke
                  Martin

                  zigbee.0	2020-04-17 13:54:02.203	error	at Object.delayAction [as action] (/opt/iobroker/node_modules/iobroker.zigbee/lib/zigbeecontroller.js:360:69))
                  zigbee.0	2020-04-17 13:54:02.203	error	(1525) Failed to do action 0x0017880110486638 RWL021, attempt 2 (TypeError: Cannot read property 'stack' of undefined
                  zigbee.0	2020-04-17 13:54:01.203	error	at rejected (/opt/iobroker/node_modules/zigbee-herdsman/dist/controller/model/endpoint.js:6:65))
                  zigbee.0	2020-04-17 13:54:01.203	error	at Generator.throw (<anonymous>)
                  zigbee.0	2020-04-17 13:54:01.203	error	at Endpoint.<anonymous> (/opt/iobroker/node_modules/zigbee-herdsman/dist/controller/model/endpoint.js:244:23)
                  zigbee.0	2020-04-17 13:54:01.203	error	(1525) Failed to configure 0x0017880110486638 RWL021, attempt NaN (Error: Bind 0x0017880110486638/1 genLevelCtrl from '0x00212effff054b00/1' failed (undefined)
                  zigbee.0	2020-04-17 13:53:01.239	info	(1525) Do action on 0x0017880110486638 RWL021
                  zigbee.0	2020-04-17 13:53:01.239	info	(1525) Do action succesfully 0x0017880110486638 RWL021
                  zigbee.0	2020-04-17 13:53:00.638	info	(1525) Do action on 0x0017880110486638 RWL021
                  zigbee.0	2020-04-17 13:53:00.637	info	(1525) Configuring 0x0017880110486638 RWL021
                  zigbee.0	2020-04-17 13:46:26.582	info	(1525) Zigbee: stop joining
                  zigbee.0	2020-04-17 13:45:59.447	error	at fulfilled (/opt/iobroker/node_modules/zigbee-herdsman/dist/controller/model/endpoint.js:5:58))
                  zigbee.0	2020-04-17 13:45:59.447	error	at Generator.next (<anonymous>)
                  zigbee.0	2020-04-17 13:45:59.447	error	at Endpoint.<anonymous> (/opt/iobroker/node_modules/zigbee-herdsman/dist/controller/model/endpoint.js:326:23)
                  zigbee.0	2020-04-17 13:45:59.447	error	(1525) Failed to configure 0x0017880102006d0c SML001, attempt 1 (Error: ConfigureReporting 0x0017880102006d0c/2 genPowerCfg([{"attribute":"batteryPercentageRemaining","minimumReportInterval":3600,"ma
                  zigbee.0	2020-04-17 13:45:56.849	info	(1525) Configuring 0x0017880102006d0c SML001
                  zigbee.0	2020-04-17 13:45:56.847	info	(1525) Device '0x0017880102006d0c' is supported, identified as: Philips Hue motion sensor (9290012607)
                  zigbee.0	2020-04-17 13:45:56.846	info	(1525) Successfully interviewed '0x0017880102006d0c', device has succesfully been paired
                  zigbee.0	2020-04-17 13:45:48.425	info	(1525) Starting interview of '0x0017880102006d0c'
                  Pairing time left: 27
                  Error: Failed to configure 0x0017880102006d0c SML001, attempt 1 (Error: ConfigureReporting 0x0017880102006d0c/2 genPowerCfg([{"attribute":"batteryPercentageRemaining","minimumReportInterval":3600,"maximumReportInterval":62000,"reportableChange":0}], {"timeout":10000,"manufacturerCode":null,"disableDefaultResponse":true}) failed (TypeError: payload is not iterable)
                      at Endpoint.<anonymous> (/opt/iobroker/node_modules/zigbee-herdsman/dist/controller/model/endpoint.js:326:23)
                      at Generator.next (<anonymous>)
                      at fulfilled (/opt/iobroker/node_modules/zigbee-herdsman/dist/controller/model/endpoint.js:5:58)). undefined
                  Pairing time left: 28
                  Pairing time left: 29
                  New device joined '0x0017880102006d0c' model SML001
                  Interview successful: {"friendly_name":"0x0017880102006d0c","model":"9290012607","vendor":"Philips","description":"Hue motion sensor","supported":true}
                  Pairing time left: 30
                  Pairing time left: 31
                  Pairing time left: 32
                  Pairing time left: 33
                  Pairing time left: 34
                  Pairing time left: 35
                  Pairing time left: 36
                  Pairing time left: 37
                  Pairing time left: 38
                  Interview started: 0x0017880102006d0c
                  
                  M Offline
                  M Offline
                  MartinMuc
                  schrieb am zuletzt editiert von
                  #85

                  @MartinMuc said in Zigbee Adapter und Conbee Unterstützung:

                  Meine Hue Lampen funktionieren einwandfrei mit dem ConbeeII, ich habe allerdings Probleme mit den HUE Bewegungsmeldern und Schaltern.

                  Beim Bewegungsmelder bekomme ich beim anlernen folgenden Fehler, das hat zur folge das er zwar angezegit wird, aber ich keine Daten empfange. Selbst PRoblem besteht bei dem Dimmerschalter.

                  Hat jemand eine Idee was hier krumm sein könnte ? Version ist die 1.1.0.0

                  Danke
                  Martin

                  zigbee.0	2020-04-17 13:54:02.203	error	at Object.delayAction [as action] (/opt/iobroker/node_modules/iobroker.zigbee/lib/zigbeecontroller.js:360:69))
                  zigbee.0	2020-04-17 13:54:02.203	error	(1525) Failed to do action 0x0017880110486638 RWL021, attempt 2 (TypeError: Cannot read property 'stack' of undefined
                  zigbee.0	2020-04-17 13:54:01.203	error	at rejected (/opt/iobroker/node_modules/zigbee-herdsman/dist/controller/model/endpoint.js:6:65))
                  zigbee.0	2020-04-17 13:54:01.203	error	at Generator.throw (<anonymous>)
                  zigbee.0	2020-04-17 13:54:01.203	error	at Endpoint.<anonymous> (/opt/iobroker/node_modules/zigbee-herdsman/dist/controller/model/endpoint.js:244:23)
                  zigbee.0	2020-04-17 13:54:01.203	error	(1525) Failed to configure 0x0017880110486638 RWL021, attempt NaN (Error: Bind 0x0017880110486638/1 genLevelCtrl from '0x00212effff054b00/1' failed (undefined)
                  zigbee.0	2020-04-17 13:53:01.239	info	(1525) Do action on 0x0017880110486638 RWL021
                  zigbee.0	2020-04-17 13:53:01.239	info	(1525) Do action succesfully 0x0017880110486638 RWL021
                  zigbee.0	2020-04-17 13:53:00.638	info	(1525) Do action on 0x0017880110486638 RWL021
                  zigbee.0	2020-04-17 13:53:00.637	info	(1525) Configuring 0x0017880110486638 RWL021
                  zigbee.0	2020-04-17 13:46:26.582	info	(1525) Zigbee: stop joining
                  zigbee.0	2020-04-17 13:45:59.447	error	at fulfilled (/opt/iobroker/node_modules/zigbee-herdsman/dist/controller/model/endpoint.js:5:58))
                  zigbee.0	2020-04-17 13:45:59.447	error	at Generator.next (<anonymous>)
                  zigbee.0	2020-04-17 13:45:59.447	error	at Endpoint.<anonymous> (/opt/iobroker/node_modules/zigbee-herdsman/dist/controller/model/endpoint.js:326:23)
                  zigbee.0	2020-04-17 13:45:59.447	error	(1525) Failed to configure 0x0017880102006d0c SML001, attempt 1 (Error: ConfigureReporting 0x0017880102006d0c/2 genPowerCfg([{"attribute":"batteryPercentageRemaining","minimumReportInterval":3600,"ma
                  zigbee.0	2020-04-17 13:45:56.849	info	(1525) Configuring 0x0017880102006d0c SML001
                  zigbee.0	2020-04-17 13:45:56.847	info	(1525) Device '0x0017880102006d0c' is supported, identified as: Philips Hue motion sensor (9290012607)
                  zigbee.0	2020-04-17 13:45:56.846	info	(1525) Successfully interviewed '0x0017880102006d0c', device has succesfully been paired
                  zigbee.0	2020-04-17 13:45:48.425	info	(1525) Starting interview of '0x0017880102006d0c'
                  Pairing time left: 27
                  Error: Failed to configure 0x0017880102006d0c SML001, attempt 1 (Error: ConfigureReporting 0x0017880102006d0c/2 genPowerCfg([{"attribute":"batteryPercentageRemaining","minimumReportInterval":3600,"maximumReportInterval":62000,"reportableChange":0}], {"timeout":10000,"manufacturerCode":null,"disableDefaultResponse":true}) failed (TypeError: payload is not iterable)
                      at Endpoint.<anonymous> (/opt/iobroker/node_modules/zigbee-herdsman/dist/controller/model/endpoint.js:326:23)
                      at Generator.next (<anonymous>)
                      at fulfilled (/opt/iobroker/node_modules/zigbee-herdsman/dist/controller/model/endpoint.js:5:58)). undefined
                  Pairing time left: 28
                  Pairing time left: 29
                  New device joined '0x0017880102006d0c' model SML001
                  Interview successful: {"friendly_name":"0x0017880102006d0c","model":"9290012607","vendor":"Philips","description":"Hue motion sensor","supported":true}
                  Pairing time left: 30
                  Pairing time left: 31
                  Pairing time left: 32
                  Pairing time left: 33
                  Pairing time left: 34
                  Pairing time left: 35
                  Pairing time left: 36
                  Pairing time left: 37
                  Pairing time left: 38
                  Interview started: 0x0017880102006d0c
                  

                  Niemand eine Idee ? Bastle heute noch ein bisschen wenn es dann nicht klappt muss ich die alte Huebridge ausgraben und die einbinden (was ich eigentlich vermeiden wollte)

                  1 Antwort Letzte Antwort
                  0
                  • PlasmachefP Plasmachef

                    @Glasfaser... so... habe für Samstag das Teil bestellt... sollte der Fehler wieder auftreten, was ich vermute, dann bin ich wieder da :blush:

                    PlasmachefP Offline
                    PlasmachefP Offline
                    Plasmachef
                    schrieb am zuletzt editiert von
                    #86

                    @Plasmachef sagte in Zigbee Adapter und Conbee Unterstützung:

                    @Glasfaser... so... habe für Samstag das Teil bestellt... sollte der Fehler wieder auftreten, was ich vermute, dann bin ich wieder da :blush:

                    Hallo die Zweite,

                    jetzt mit anderer Hardware und dem SELBEN Problem:

                    Bin hier grad am Testen und versuche meinen Raspi Pi 4 mit Conbee II und dem Danalock zusammen zubringen.

                    Conbee II eingesteckt
                    Zigbee über Katze geladen (Version 1.1.1), Instanz angelegt und die Hardware ausgewählt
                    --> Instanz grün 🙂

                    Instanz und Danalock V3 auf pairing ... jetzt kommts:

                    2020-05-02 15:17:59.402 - info: zigbee.0 (10320) starting. Version 1.1.1 in /opt/iobroker/node_modules/iobroker.zigbee, node: v12.16.2
                    2020-05-02 15:17:59.437 - info: zigbee.0 (10320) Starting Zigbee...
                    2020-05-02 15:17:59.857 - info: zigbee.0 (10320) Coordinator firmware version: {"type":"ConBee2","meta":{"transportrev":0,"product":0,"majorrel":38,"minorrel":74,"maintrel":0,"revision":"0x264a0700"}}
                    2020-05-02 15:18:00.066 - info: zigbee.0 (10320) Unable to disable LED, unsupported function.
                    2020-05-02 15:18:00.067 - info: zigbee.0 (10320) --> transmitPower : normal
                    2020-05-02 15:18:00.069 - info: zigbee.0 (10320) Unable to set transmit power, unsupported function.
                    2020-05-02 15:18:00.071 - info: zigbee.0 (10320) Currently no devices.
                    2020-05-02 15:18:00.072 - info: zigbee.0 (10320) Zigbee started
                    2020-05-02 15:19:23.143 - info: zigbee.0 (10320) Zigbee: allowing new devices to join.
                    2020-05-02 15:19:31.554 - info: zigbee.0 (10320) Starting interview of '0x000b57fffe46ebec'
                    2020-05-02 15:19:43.707 - info: zigbee.0 (10320) Successfully interviewed '0x000b57fffe46ebec', device has succesfully been paired
                    2020-05-02 15:19:43.708 - info: zigbee.0 (10320) Device '0x000b57fffe46ebec' is supported, identified as: Danalock BT/ZB smartlock (V3-BTZB)
                    2020-05-02 15:19:43.711 - info: zigbee.0 (10320) Configuring 0x000b57fffe46ebec V3-BTZB
                    2020-05-02 15:19:45.724 - error: zigbee.0 (10320) Failed to configure 0x000b57fffe46ebec V3-BTZB, attempt 1 (Error: ConfigureReporting 0x000b57fffe46ebec/1 closuresDoorLock([{"attribute":"lockState","minimumReportInterval":0,"maximumReportInterval":3600,"reportableChange":0}], {"timeout":10000,"manufacturerCode":null,"disableDefaultResponse":true}) failed (Error: Status 'INVALID_DATA_TYPE')
                    at Endpoint. (/opt/iobroker/node_modules/zigbee-herdsman/dist/controller/model/endpoint.js:326:23)
                    at Generator.next ()
                    at fulfilled (/opt/iobroker/node_modules/zigbee-herdsman/dist/controller/model/endpoint.js:5:58))
                    

                    Leider kann ich mit dem Teil so nichts anfangen :-(
                    Einige Objekte wurden angelegt, aber mehr passiert leider nicht ... kann nichts schalten oder konfigurieren ... auch das Lock gibt kein Feedback zur Instanz

                    Könnt ihr mir bitte helfen?

                    Danke und Grüße Plasma

                    1 Antwort Letzte Antwort
                    0
                    • PlasmachefP Offline
                      PlasmachefP Offline
                      Plasmachef
                      schrieb am zuletzt editiert von Plasmachef
                      #87

                      so ... jetzt wirds spannend ... es gibt noch mehr zu berichten:

                      ich hab dann mal bisschen mit dem Teil "gespielt" und siehe da... der Befehl lock bzw. unlock wurde akzepiert und auch korrekt quittiert.
                      nach restart der instanz bekam ich dann noch ein weiteres objekt dazu: available

                      Dana.png

                      die anderen objekte waren tot ... und auch available hat nicht wirklich sich verändert.
                      ich hatte mal einen verbindungsabbruch simuliert in dem in die batterien rausnahm ... seither ging gar nichts mehr.

                      • konnte das gerät nicht löschen
                      • pairing zählte nur noch von 5 runter statt von 60
                      • instanz löschen und neu aufsetzen half auch nichts...er merkte sich alle allen daten :-(
                        -neustart von iobroker brachte auch nichts

                      ich lösche die instanz (zigbee.0) und legte eine neue an (zigbee.1)

                      hier gab es keine altlasten und das pairing klappte
                      man konnte wieder zugreifen auf das gerät ... sogar diesmal mit zugabe:

                      dana2.png

                      linkquality kam mit dazu und refreshte sich auch regelmäßig ... immer so zwischen 3 und 4 ... was das auch immer bedeutet.

                      nachfolgend alle logeinträge von instanz zigbee.1

                      2020-05-02 16:45:56.301 - error: host.raspberrypi instance system.adapter.zigbee.0 terminated with code 156 (156)
                      2020-05-02 16:45:56.302 - info: host.raspberrypi Do not restart adapter system.adapter.zigbee.0 because disabled or deleted
                      2020-05-02 16:46:54.917 - info: host.raspberrypi iobroker add zigbee 1 --host raspberrypi
                      2020-05-02 16:46:56.601 - info: host.raspberrypi iobroker host.raspberrypi create instance zigbee
                      2020-05-02 16:46:56.630 - info: host.raspberrypi iobroker host.raspberrypi object zigbee.1.info.groups created
                      2020-05-02 16:46:56.659 - info: host.raspberrypi iobroker host.raspberrypi object zigbee.1.info.pairingMessage created
                      2020-05-02 16:46:56.688 - info: host.raspberrypi iobroker host.raspberrypi object zigbee.1.info.pairingCountdown created
                      2020-05-02 16:46:56.717 - info: host.raspberrypi iobroker host.raspberrypi object zigbee.1.info.pairingMode created
                      2020-05-02 16:46:56.747 - info: host.raspberrypi iobroker host.raspberrypi object zigbee.1.info.connection created
                      2020-05-02 16:46:56.777 - info: host.raspberrypi iobroker host.raspberrypi object zigbee.1.info created
                      2020-05-02 16:46:56.811 - info: host.raspberrypi iobroker host.raspberrypi object system.adapter.zigbee.1.sigKill created
                      2020-05-02 16:46:56.844 - info: host.raspberrypi iobroker host.raspberrypi object system.adapter.zigbee.1.eventLoopLag created
                      2020-05-02 16:46:56.879 - info: host.raspberrypi iobroker host.raspberrypi object system.adapter.zigbee.1.outputCount created
                      2020-05-02 16:46:56.911 - info: host.raspberrypi iobroker host.raspberrypi object system.adapter.zigbee.1.inputCount created
                      2020-05-02 16:46:56.943 - info: host.raspberrypi iobroker host.raspberrypi object system.adapter.zigbee.1.uptime created
                      2020-05-02 16:46:56.975 - info: host.raspberrypi iobroker host.raspberrypi object system.adapter.zigbee.1.memRss created
                      2020-05-02 16:46:57.007 - info: host.raspberrypi iobroker host.raspberrypi object system.adapter.zigbee.1.memHeapTotal created
                      2020-05-02 16:46:57.039 - info: host.raspberrypi iobroker host.raspberrypi object system.adapter.zigbee.1.memHeapUsed created
                      2020-05-02 16:46:57.070 - info: host.raspberrypi iobroker host.raspberrypi object system.adapter.zigbee.1.cputime created
                      2020-05-02 16:46:57.102 - info: host.raspberrypi iobroker host.raspberrypi object system.adapter.zigbee.1.cpu created
                      2020-05-02 16:46:57.137 - info: host.raspberrypi iobroker host.raspberrypi object system.adapter.zigbee.1.compactMode created
                      2020-05-02 16:46:57.179 - info: host.raspberrypi iobroker host.raspberrypi object system.adapter.zigbee.1.connected created
                      2020-05-02 16:46:57.222 - info: host.raspberrypi iobroker host.raspberrypi object system.adapter.zigbee.1.alive created
                      2020-05-02 16:46:57.305 - info: host.raspberrypi iobroker host.raspberrypi object system.adapter.zigbee.1 created
                      2020-05-02 16:46:58.314 - info: host.raspberrypi iobroker exit 0
                      2020-05-02 16:46:59.830 - info: host.raspberrypi instance system.adapter.zigbee.1 started with pid 9847
                      2020-05-02 16:47:03.617 - info: zigbee.1 (9847) starting. Version 1.1.1 in /opt/iobroker/node_modules/iobroker.zigbee, node: v12.16.2
                      2020-05-02 16:47:03.649 - error: zigbee.1 (9847) Serial port not selected! Go to settings page.
                      2020-05-02 16:47:03.652 - info: zigbee.1 (9847) Starting Zigbee...
                      2020-05-02 16:47:03.962 - error: zigbee.1 (9847) Failed to start Zigbee
                      2020-05-02 16:47:03.963 - error: zigbee.1 (9847) Error: No path provided and failed to auto detect path
                      at Function. (/opt/iobroker/node_modules/zigbee-herdsman/dist/adapter/adapter.js:69:27)
                      at Generator.next ()
                      at fulfilled (/opt/iobroker/node_modules/zigbee-herdsman/dist/adapter/adapter.js:5:58)
                      at processTicksAndRejections (internal/process/task_queues.js:97:5)
                      2020-05-02 16:47:13.966 - info: zigbee.1 (9847) Try to reconnect. 1 attempts left
                      2020-05-02 16:47:13.967 - info: zigbee.1 (9847) Starting Zigbee...
                      2020-05-02 16:47:14.172 - error: zigbee.1 (9847) Failed to start Zigbee
                      2020-05-02 16:47:14.173 - error: zigbee.1 (9847) Error: No path provided and failed to auto detect path
                      at Function. (/opt/iobroker/node_modules/zigbee-herdsman/dist/adapter/adapter.js:69:27)
                      at Generator.next ()
                      at fulfilled (/opt/iobroker/node_modules/zigbee-herdsman/dist/adapter/adapter.js:5:58)
                      at processTicksAndRejections (internal/process/task_queues.js:97:5)
                      2020-05-02 16:47:41.210 - info: host.raspberrypi stopInstance system.adapter.zigbee.1 (force=false, process=true)
                      2020-05-02 16:47:41.228 - info: host.raspberrypi stopInstance system.adapter.zigbee.1 send kill signal
                      2020-05-02 16:47:41.228 - info: zigbee.1 (9847) Got terminate signal TERMINATE_YOURSELF
                      2020-05-02 16:47:41.231 - info: zigbee.1 (9847) cleaned everything up...
                      2020-05-02 16:47:41.243 - error: zigbee.1 (9847) Failed to stop zigbee (TypeError: Cannot read property 'getEntries' of null
                      at Function.loadFromDatabaseIfNecessary (/opt/iobroker/node_modules/zigbee-herdsman/dist/controller/model/device.js:200:55)
                      at Function.byIeeeAddr (/opt/iobroker/node_modules/zigbee-herdsman/dist/controller/model/device.js:208:16)
                      at Controller.getDeviceByIeeeAddr (/opt/iobroker/node_modules/zigbee-herdsman/dist/controller/controller.js:235:31)
                      at ZigbeeController.getDevice (/opt/iobroker/node_modules/iobroker.zigbee/lib/zigbeecontroller.js:212:30)
                      at ZigbeeController.permitJoin (/opt/iobroker/node_modules/iobroker.zigbee/lib/zigbeecontroller.js:319:30)
                      at ZigbeeController.stop (/opt/iobroker/node_modules/iobroker.zigbee/lib/zigbeecontroller.js:306:24)
                      at processTicksAndRejections (internal/process/task_queues.js:97:5)
                      at async Zigbee.onUnload (/opt/iobroker/node_modules/iobroker.zigbee/main.js:334:17))
                      2020-05-02 16:47:41.245 - info: zigbee.1 (9847) terminating
                      2020-05-02 16:47:41.247 - info: zigbee.1 (9847) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
                      2020-05-02 16:47:41.775 - info: host.raspberrypi instance system.adapter.zigbee.1 terminated with code 156 (156)
                      2020-05-02 16:47:43.812 - info: host.raspberrypi instance system.adapter.zigbee.1 started with pid 11027
                      2020-05-02 16:47:46.082 - info: zigbee.1 (11027) starting. Version 1.1.1 in /opt/iobroker/node_modules/iobroker.zigbee, node: v12.16.2
                      2020-05-02 16:47:46.150 - error: zigbee.1 (11027) Serial port not selected! Go to settings page.
                      2020-05-02 16:47:46.155 - info: zigbee.1 (11027) Starting Zigbee...
                      2020-05-02 16:47:46.609 - info: zigbee.1 (11027) Coordinator firmware version: {"type":"ConBee2","meta":{"transportrev":0,"product":0,"majorrel":38,"minorrel":74,"maintrel":0,"revision":"0x264a0700"}}
                      2020-05-02 16:47:53.137 - info: zigbee.1 (11027) Unable to disable LED, unsupported function.
                      2020-05-02 16:47:53.139 - info: zigbee.1 (11027) --> transmitPower : normal
                      2020-05-02 16:47:53.141 - info: zigbee.1 (11027) Unable to set transmit power, unsupported function.
                      2020-05-02 16:47:53.144 - info: zigbee.1 (11027) Currently no devices.
                      2020-05-02 16:47:53.145 - info: zigbee.1 (11027) Zigbee started
                      2020-05-02 16:48:41.400 - info: zigbee.1 (11027) Zigbee: allowing new devices to join.
                      2020-05-02 16:48:54.061 - info: zigbee.1 (11027) Starting interview of '0x000b57fffe46ebec'
                      2020-05-02 16:49:05.697 - info: zigbee.1 (11027) Successfully interviewed '0x000b57fffe46ebec', device has succesfully been paired
                      2020-05-02 16:49:05.699 - info: zigbee.1 (11027) Device '0x000b57fffe46ebec' is supported, identified as: Danalock BT/ZB smartlock (V3-BTZB)
                      2020-05-02 16:49:05.703 - info: zigbee.1 (11027) Configuring 0x000b57fffe46ebec V3-BTZB
                      2020-05-02 16:49:07.709 - error: zigbee.1 (11027) Failed to configure 0x000b57fffe46ebec V3-BTZB, attempt 1 (Error: ConfigureReporting 0x000b57fffe46ebec/1 closuresDoorLock([{"attribute":"lockState","minimumReportInterval":0,"maximumReportInterval":3600,"reportableChange":0}], {"timeout":10000,"manufacturerCode":null,"disableDefaultResponse":true}) failed (Error: Status 'INVALID_DATA_TYPE')
                      at Endpoint. (/opt/iobroker/node_modules/zigbee-herdsman/dist/controller/model/endpoint.js:326:23)
                      at Generator.next ()
                      at fulfilled (/opt/iobroker/node_modules/zigbee-herdsman/dist/controller/model/endpoint.js:5:58))
                      2020-05-02 16:49:25.572 - info: zigbee.1 (11027) Configuring 0x000b57fffe46ebec V3-BTZB
                      2020-05-02 16:49:27.590 - error: zigbee.1 (11027) Failed to configure 0x000b57fffe46ebec V3-BTZB, attempt 2 (Error: ConfigureReporting 0x000b57fffe46ebec/1 closuresDoorLock([{"attribute":"lockState","minimumReportInterval":0,"maximumReportInterval":3600,"reportableChange":0}], {"timeout":10000,"manufacturerCode":null,"disableDefaultResponse":true}) failed (Error: Status 'INVALID_DATA_TYPE')
                      at Endpoint. (/opt/iobroker/node_modules/zigbee-herdsman/dist/controller/model/endpoint.js:326:23)
                      at Generator.next ()
                      at fulfilled (/opt/iobroker/node_modules/zigbee-herdsman/dist/controller/model/endpoint.js:5:58))
                      2020-05-02 16:49:28.590 - info: zigbee.1 (11027) Configuring 0x000b57fffe46ebec V3-BTZB
                      2020-05-02 16:49:30.607 - error: zigbee.1 (11027) Failed to configure 0x000b57fffe46ebec V3-BTZB, attempt 3 (Error: ConfigureReporting 0x000b57fffe46ebec/1 closuresDoorLock([{"attribute":"lockState","minimumReportInterval":0,"maximumReportInterval":3600,"reportableChange":0}], {"timeout":10000,"manufacturerCode":null,"disableDefaultResponse":true}) failed (Error: Status 'INVALID_DATA_TYPE')
                      at Endpoint. (/opt/iobroker/node_modules/zigbee-herdsman/dist/controller/model/endpoint.js:326:23)
                      at Generator.next ()
                      at fulfilled (/opt/iobroker/node_modules/zigbee-herdsman/dist/controller/model/endpoint.js:5:58))
                      2020-05-02 16:49:31.618 - info: zigbee.1 (11027) Configuring 0x000b57fffe46ebec V3-BTZB
                      2020-05-02 16:49:33.630 - error: zigbee.1 (11027) Failed to configure 0x000b57fffe46ebec V3-BTZB, attempt 4 (Error: ConfigureReporting 0x000b57fffe46ebec/1 closuresDoorLock([{"attribute":"lockState","minimumReportInterval":0,"maximumReportInterval":3600,"reportableChange":0}], {"timeout":10000,"manufacturerCode":null,"disableDefaultResponse":true}) failed (Error: Status 'INVALID_DATA_TYPE')
                      at Endpoint. (/opt/iobroker/node_modules/zigbee-herdsman/dist/controller/model/endpoint.js:326:23)
                      at Generator.next ()
                      at fulfilled (/opt/iobroker/node_modules/zigbee-herdsman/dist/controller/model/endpoint.js:5:58))
                      2020-05-02 16:49:34.631 - info: zigbee.1 (11027) Configuring 0x000b57fffe46ebec V3-BTZB
                      2020-05-02 16:49:36.649 - error: zigbee.1 (11027) Failed to configure 0x000b57fffe46ebec V3-BTZB, attempt 5 (Error: ConfigureReporting 0x000b57fffe46ebec/1 closuresDoorLock([{"attribute":"lockState","minimumReportInterval":0,"maximumReportInterval":3600,"reportableChange":0}], {"timeout":10000,"manufacturerCode":null,"disableDefaultResponse":true}) failed (Error: Status 'INVALID_DATA_TYPE')
                      at Endpoint. (/opt/iobroker/node_modules/zigbee-herdsman/dist/controller/model/endpoint.js:326:23)
                      at Generator.next ()
                      at fulfilled (/opt/iobroker/node_modules/zigbee-herdsman/dist/controller/model/endpoint.js:5:58))
                      2020-05-02 16:49:43.076 - info: zigbee.1 (11027) Zigbee: stop joining
                      2020-05-02 16:52:52.952 - info: host.raspberrypi stopInstance system.adapter.zigbee.1 (force=false, process=true)
                      2020-05-02 16:52:52.964 - info: host.raspberrypi stopInstance system.adapter.zigbee.1 send kill signal
                      2020-05-02 16:52:52.965 - info: zigbee.1 (11027) Got terminate signal TERMINATE_YOURSELF
                      2020-05-02 16:52:52.967 - info: zigbee.1 (11027) cleaned everything up...
                      2020-05-02 16:52:52.970 - info: zigbee.1 (11027) Zigbee: disabling joining new devices.
                      2020-05-02 16:52:53.470 - info: zigbee.1 (11027) terminating
                      2020-05-02 16:52:53.471 - info: zigbee.1 (11027) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
                      2020-05-02 16:52:53.970 - info: host.raspberrypi stopInstance system.adapter.zigbee.1 killing pid 11027
                      2020-05-02 16:52:54.028 - info: host.raspberrypi instance system.adapter.zigbee.1 terminated with code 156 (156)
                      2020-05-02 16:52:55.524 - info: host.raspberrypi instance system.adapter.zigbee.1 started with pid 18536
                      2020-05-02 16:52:57.823 - info: zigbee.1 (18536) starting. Version 1.1.1 in /opt/iobroker/node_modules/iobroker.zigbee, node: v12.16.2
                      2020-05-02 16:52:57.869 - error: zigbee.1 (18536) Serial port not selected! Go to settings page.
                      2020-05-02 16:52:57.873 - info: zigbee.1 (18536) Starting Zigbee...
                      2020-05-02 16:52:58.322 - info: zigbee.1 (18536) Coordinator firmware version: {"type":"ConBee2","meta":{"transportrev":0,"product":0,"majorrel":38,"minorrel":74,"maintrel":0,"revision":"0x264a0700"}}
                      2020-05-02 16:52:58.523 - info: zigbee.1 (18536) Unable to disable LED, unsupported function.
                      2020-05-02 16:52:58.524 - info: zigbee.1 (18536) --> transmitPower : normal
                      2020-05-02 16:52:58.525 - info: zigbee.1 (18536) Unable to set transmit power, unsupported function.
                      2020-05-02 16:52:58.530 - info: zigbee.1 (18536) Currently 1 devices are joined:
                      2020-05-02 16:52:58.533 - info: zigbee.1 (18536) Configuring 0x000b57fffe46ebec V3-BTZB
                      2020-05-02 16:52:58.540 - info: zigbee.1 (18536) 0x000b57fffe46ebec (addr 61935): V3-BTZB - Danalock BT/ZB smartlock (EndDevice)
                      2020-05-02 16:52:58.541 - info: zigbee.1 (18536) Zigbee started
                      2020-05-02 16:53:02.407 - error: zigbee.1 (18536) Failed to configure 0x000b57fffe46ebec V3-BTZB, attempt 1 (Error: ConfigureReporting 0x000b57fffe46ebec/1 closuresDoorLock([{"attribute":"lockState","minimumReportInterval":0,"maximumReportInterval":3600,"reportableChange":0}], {"timeout":10000,"manufacturerCode":null,"disableDefaultResponse":true}) failed (Error: Status 'INVALID_DATA_TYPE')
                      at Endpoint. (/opt/iobroker/node_modules/zigbee-herdsman/dist/controller/model/endpoint.js:326:23)
                      at Generator.next ()
                      at fulfilled (/opt/iobroker/node_modules/zigbee-herdsman/dist/controller/model/endpoint.js:5:58))
                      2020-05-02 16:53:30.919 - info: zigbee.1 (18536) Configuring 0x000b57fffe46ebec V3-BTZB
                      2020-05-02 16:53:33.426 - error: zigbee.1 (18536) Failed to configure 0x000b57fffe46ebec V3-BTZB, attempt 2 (Error: ConfigureReporting 0x000b57fffe46ebec/1 closuresDoorLock([{"attribute":"lockState","minimumReportInterval":0,"maximumReportInterval":3600,"reportableChange":0}], {"timeout":10000,"manufacturerCode":null,"disableDefaultResponse":true}) failed (Error: Status 'INVALID_DATA_TYPE')
                      at Endpoint. (/opt/iobroker/node_modules/zigbee-herdsman/dist/controller/model/endpoint.js:326:23)
                      at Generator.next ()
                      at fulfilled (/opt/iobroker/node_modules/zigbee-herdsman/dist/controller/model/endpoint.js:5:58))
                      2020-05-02 16:53:47.481 - info: zigbee.1 (18536) Configuring 0x000b57fffe46ebec V3-BTZB
                      2020-05-02 16:53:49.984 - error: zigbee.1 (18536) Failed to configure 0x000b57fffe46ebec V3-BTZB, attempt 3 (Error: ConfigureReporting 0x000b57fffe46ebec/1 closuresDoorLock([{"attribute":"lockState","minimumReportInterval":0,"maximumReportInterval":3600,"reportableChange":0}], {"timeout":10000,"manufacturerCode":null,"disableDefaultResponse":true}) failed (Error: Status 'INVALID_DATA_TYPE')
                      at Endpoint. (/opt/iobroker/node_modules/zigbee-herdsman/dist/controller/model/endpoint.js:326:23)
                      at Generator.next ()
                      at fulfilled (/opt/iobroker/node_modules/zigbee-herdsman/dist/controller/model/endpoint.js:5:58))
                      2020-05-02 16:56:02.105 - info: zigbee.1 (18536) Configuring 0x000b57fffe46ebec V3-BTZB
                      2020-05-02 16:56:07.125 - error: zigbee.1 (18536) Failed to configure 0x000b57fffe46ebec V3-BTZB, attempt 4 (Error: ConfigureReporting 0x000b57fffe46ebec/1 closuresDoorLock([{"attribute":"lockState","minimumReportInterval":0,"maximumReportInterval":3600,"reportableChange":0}], {"timeout":10000,"manufacturerCode":null,"disableDefaultResponse":true}) failed (Error: Status 'INVALID_DATA_TYPE')
                      at Endpoint. (/opt/iobroker/node_modules/zigbee-herdsman/dist/controller/model/endpoint.js:326:23)
                      at Generator.next ()
                      at fulfilled (/opt/iobroker/node_modules/zigbee-herdsman/dist/controller/model/endpoint.js:5:58))
                      2020-05-02 16:56:53.605 - info: zigbee.1 (18536) Configuring 0x000b57fffe46ebec V3-BTZB
                      2020-05-02 16:56:57.118 - error: zigbee.1 (18536) Failed to configure 0x000b57fffe46ebec V3-BTZB, attempt 5 (Error: ConfigureReporting 0x000b57fffe46ebec/1 closuresDoorLock([{"attribute":"lockState","minimumReportInterval":0,"maximumReportInterval":3600,"reportableChange":0}], {"timeout":10000,"manufacturerCode":null,"disableDefaultResponse":true}) failed (Error: Status 'INVALID_DATA_TYPE')
                      at Endpoint. (/opt/iobroker/node_modules/zigbee-herdsman/dist/controller/model/endpoint.js:326:23)
                      at Generator.next ()
                      at fulfilled (/opt/iobroker/node_modules/zigbee-herdsman/dist/controller/model/endpoint.js:5:58))
                      

                      ... und wieder zeigt available nicht den richtigen zustand an

                      hab die batterie erneut rausgenommen ... wieder kein kontakt bzw kein lock / unlock möglich
                      neustart der instanz bring nichts

                      2020-05-02 17:28:36.558 - info: host.raspberrypi stopInstance system.adapter.zigbee.1 (force=false, process=true)
                      2020-05-02 17:28:36.570 - info: host.raspberrypi stopInstance system.adapter.zigbee.1 send kill signal
                      2020-05-02 17:28:36.571 - info: zigbee.1 (3673) Got terminate signal TERMINATE_YOURSELF
                      2020-05-02 17:28:36.573 - info: zigbee.1 (3673) cleaned everything up...
                      2020-05-02 17:28:36.576 - info: zigbee.1 (3673) Zigbee: disabling joining new devices.
                      2020-05-02 17:28:37.076 - info: zigbee.1 (3673) terminating
                      2020-05-02 17:28:37.078 - info: zigbee.1 (3673) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
                      2020-05-02 17:28:37.576 - info: host.raspberrypi stopInstance system.adapter.zigbee.1 killing pid 3673
                      2020-05-02 17:28:37.629 - info: host.raspberrypi instance system.adapter.zigbee.1 terminated with code 156 (156)
                      2020-05-02 17:28:39.129 - info: host.raspberrypi instance system.adapter.zigbee.1 started with pid 5617
                      2020-05-02 17:28:41.476 - info: zigbee.1 (5617) starting. Version 1.1.1 in /opt/iobroker/node_modules/iobroker.zigbee, node: v12.16.2
                      2020-05-02 17:28:41.510 - info: zigbee.1 (5617) Starting Zigbee...
                      2020-05-02 17:28:41.928 - info: zigbee.1 (5617) Coordinator firmware version: {"type":"ConBee2","meta":{"transportrev":0,"product":0,"majorrel":38,"minorrel":74,"maintrel":0,"revision":"0x264a0700"}}
                      2020-05-02 17:28:42.131 - info: zigbee.1 (5617) Unable to disable LED, unsupported function.
                      2020-05-02 17:28:42.132 - info: zigbee.1 (5617) --> transmitPower : normal
                      2020-05-02 17:28:42.134 - info: zigbee.1 (5617) Unable to set transmit power, unsupported function.
                      2020-05-02 17:28:42.142 - info: zigbee.1 (5617) Currently 1 devices are joined:
                      2020-05-02 17:28:42.148 - info: zigbee.1 (5617) Configuring 0x000b57fffe46ebec V3-BTZB
                      2020-05-02 17:28:42.162 - info: zigbee.1 (5617) 0x000b57fffe46ebec (addr 61935): V3-BTZB - Danalock BT/ZB smartlock (EndDevice)
                      2020-05-02 17:28:42.164 - info: zigbee.1 (5617) Zigbee started
                      2020-05-02 17:29:42.783 - error: zigbee.1 (5617) Failed to configure 0x000b57fffe46ebec V3-BTZB, attempt 1 (Error: Bind 0x000b57fffe46ebec/1 closuresDoorLock from '0x00212effff05994f/1' failed (undefined)
                      at Endpoint. (/opt/iobroker/node_modules/zigbee-herdsman/dist/controller/model/endpoint.js:244:23)
                      at Generator.throw ()
                      at rejected (/opt/iobroker/node_modules/zigbee-herdsman/dist/controller/model/endpoint.js:6:65))
                      

                      das gerät scheint zwar kontakt zu haben, aber kommunikation ist nicht möglich

                      wieder lässt sich das Lock nicht aus der instanz löschen und beim pairing erscheint dann folgendes

                      2020-05-02 17:47:24.636 - info: zigbee.1 (5617) Do action on 0x000b57fffe46ebec V3-BTZB
                      2020-05-02 17:47:34.795 - info: zigbee.1 (5617) Do action on 0x000b57fffe46ebec V3-BTZB
                      2020-05-02 17:48:07.605 - info: zigbee.1 (5617) Do action on 0x000b57fffe46ebec V3-BTZB
                      2020-05-02 17:48:12.949 - info: zigbee.1 (5617) Zigbee: allowing new devices to join.
                      2020-05-02 17:48:24.967 - error: zigbee.1 (5617) Failed to do action 0x000b57fffe46ebec V3-BTZB, attempt 1 (TypeError: Cannot read property 'stack' of undefined
                      at Object.action (/opt/iobroker/node_modules/iobroker.zigbee/lib/zigbeecontroller.js:360:69))
                      2020-05-02 17:48:34.975 - error: zigbee.1 (5617) Failed to do action 0x000b57fffe46ebec V3-BTZB, attempt 1 (TypeError: Cannot read property 'stack' of undefined
                      at Object.action (/opt/iobroker/node_modules/iobroker.zigbee/lib/zigbeecontroller.js:360:69))
                      2020-05-02 17:49:07.984 - error: zigbee.1 (5617) Failed to do action 0x000b57fffe46ebec V3-BTZB, attempt 1 (TypeError: Cannot read property 'stack' of undefined
                      at Object.action (/opt/iobroker/node_modules/iobroker.zigbee/lib/zigbeecontroller.js:360:69))
                      2020-05-02 17:49:19.007 - info: zigbee.1 (5617) Zigbee: stop joining
                      

                      ich hoffe sehr, dass meine ausführung helfen ... bin auch gerne bereit weitere test zu machen

                      danke schön

                      plasma :-)

                      arteckA 1 Antwort Letzte Antwort
                      0
                      • PlasmachefP Plasmachef

                        so ... jetzt wirds spannend ... es gibt noch mehr zu berichten:

                        ich hab dann mal bisschen mit dem Teil "gespielt" und siehe da... der Befehl lock bzw. unlock wurde akzepiert und auch korrekt quittiert.
                        nach restart der instanz bekam ich dann noch ein weiteres objekt dazu: available

                        Dana.png

                        die anderen objekte waren tot ... und auch available hat nicht wirklich sich verändert.
                        ich hatte mal einen verbindungsabbruch simuliert in dem in die batterien rausnahm ... seither ging gar nichts mehr.

                        • konnte das gerät nicht löschen
                        • pairing zählte nur noch von 5 runter statt von 60
                        • instanz löschen und neu aufsetzen half auch nichts...er merkte sich alle allen daten :-(
                          -neustart von iobroker brachte auch nichts

                        ich lösche die instanz (zigbee.0) und legte eine neue an (zigbee.1)

                        hier gab es keine altlasten und das pairing klappte
                        man konnte wieder zugreifen auf das gerät ... sogar diesmal mit zugabe:

                        dana2.png

                        linkquality kam mit dazu und refreshte sich auch regelmäßig ... immer so zwischen 3 und 4 ... was das auch immer bedeutet.

                        nachfolgend alle logeinträge von instanz zigbee.1

                        2020-05-02 16:45:56.301 - error: host.raspberrypi instance system.adapter.zigbee.0 terminated with code 156 (156)
                        2020-05-02 16:45:56.302 - info: host.raspberrypi Do not restart adapter system.adapter.zigbee.0 because disabled or deleted
                        2020-05-02 16:46:54.917 - info: host.raspberrypi iobroker add zigbee 1 --host raspberrypi
                        2020-05-02 16:46:56.601 - info: host.raspberrypi iobroker host.raspberrypi create instance zigbee
                        2020-05-02 16:46:56.630 - info: host.raspberrypi iobroker host.raspberrypi object zigbee.1.info.groups created
                        2020-05-02 16:46:56.659 - info: host.raspberrypi iobroker host.raspberrypi object zigbee.1.info.pairingMessage created
                        2020-05-02 16:46:56.688 - info: host.raspberrypi iobroker host.raspberrypi object zigbee.1.info.pairingCountdown created
                        2020-05-02 16:46:56.717 - info: host.raspberrypi iobroker host.raspberrypi object zigbee.1.info.pairingMode created
                        2020-05-02 16:46:56.747 - info: host.raspberrypi iobroker host.raspberrypi object zigbee.1.info.connection created
                        2020-05-02 16:46:56.777 - info: host.raspberrypi iobroker host.raspberrypi object zigbee.1.info created
                        2020-05-02 16:46:56.811 - info: host.raspberrypi iobroker host.raspberrypi object system.adapter.zigbee.1.sigKill created
                        2020-05-02 16:46:56.844 - info: host.raspberrypi iobroker host.raspberrypi object system.adapter.zigbee.1.eventLoopLag created
                        2020-05-02 16:46:56.879 - info: host.raspberrypi iobroker host.raspberrypi object system.adapter.zigbee.1.outputCount created
                        2020-05-02 16:46:56.911 - info: host.raspberrypi iobroker host.raspberrypi object system.adapter.zigbee.1.inputCount created
                        2020-05-02 16:46:56.943 - info: host.raspberrypi iobroker host.raspberrypi object system.adapter.zigbee.1.uptime created
                        2020-05-02 16:46:56.975 - info: host.raspberrypi iobroker host.raspberrypi object system.adapter.zigbee.1.memRss created
                        2020-05-02 16:46:57.007 - info: host.raspberrypi iobroker host.raspberrypi object system.adapter.zigbee.1.memHeapTotal created
                        2020-05-02 16:46:57.039 - info: host.raspberrypi iobroker host.raspberrypi object system.adapter.zigbee.1.memHeapUsed created
                        2020-05-02 16:46:57.070 - info: host.raspberrypi iobroker host.raspberrypi object system.adapter.zigbee.1.cputime created
                        2020-05-02 16:46:57.102 - info: host.raspberrypi iobroker host.raspberrypi object system.adapter.zigbee.1.cpu created
                        2020-05-02 16:46:57.137 - info: host.raspberrypi iobroker host.raspberrypi object system.adapter.zigbee.1.compactMode created
                        2020-05-02 16:46:57.179 - info: host.raspberrypi iobroker host.raspberrypi object system.adapter.zigbee.1.connected created
                        2020-05-02 16:46:57.222 - info: host.raspberrypi iobroker host.raspberrypi object system.adapter.zigbee.1.alive created
                        2020-05-02 16:46:57.305 - info: host.raspberrypi iobroker host.raspberrypi object system.adapter.zigbee.1 created
                        2020-05-02 16:46:58.314 - info: host.raspberrypi iobroker exit 0
                        2020-05-02 16:46:59.830 - info: host.raspberrypi instance system.adapter.zigbee.1 started with pid 9847
                        2020-05-02 16:47:03.617 - info: zigbee.1 (9847) starting. Version 1.1.1 in /opt/iobroker/node_modules/iobroker.zigbee, node: v12.16.2
                        2020-05-02 16:47:03.649 - error: zigbee.1 (9847) Serial port not selected! Go to settings page.
                        2020-05-02 16:47:03.652 - info: zigbee.1 (9847) Starting Zigbee...
                        2020-05-02 16:47:03.962 - error: zigbee.1 (9847) Failed to start Zigbee
                        2020-05-02 16:47:03.963 - error: zigbee.1 (9847) Error: No path provided and failed to auto detect path
                        at Function. (/opt/iobroker/node_modules/zigbee-herdsman/dist/adapter/adapter.js:69:27)
                        at Generator.next ()
                        at fulfilled (/opt/iobroker/node_modules/zigbee-herdsman/dist/adapter/adapter.js:5:58)
                        at processTicksAndRejections (internal/process/task_queues.js:97:5)
                        2020-05-02 16:47:13.966 - info: zigbee.1 (9847) Try to reconnect. 1 attempts left
                        2020-05-02 16:47:13.967 - info: zigbee.1 (9847) Starting Zigbee...
                        2020-05-02 16:47:14.172 - error: zigbee.1 (9847) Failed to start Zigbee
                        2020-05-02 16:47:14.173 - error: zigbee.1 (9847) Error: No path provided and failed to auto detect path
                        at Function. (/opt/iobroker/node_modules/zigbee-herdsman/dist/adapter/adapter.js:69:27)
                        at Generator.next ()
                        at fulfilled (/opt/iobroker/node_modules/zigbee-herdsman/dist/adapter/adapter.js:5:58)
                        at processTicksAndRejections (internal/process/task_queues.js:97:5)
                        2020-05-02 16:47:41.210 - info: host.raspberrypi stopInstance system.adapter.zigbee.1 (force=false, process=true)
                        2020-05-02 16:47:41.228 - info: host.raspberrypi stopInstance system.adapter.zigbee.1 send kill signal
                        2020-05-02 16:47:41.228 - info: zigbee.1 (9847) Got terminate signal TERMINATE_YOURSELF
                        2020-05-02 16:47:41.231 - info: zigbee.1 (9847) cleaned everything up...
                        2020-05-02 16:47:41.243 - error: zigbee.1 (9847) Failed to stop zigbee (TypeError: Cannot read property 'getEntries' of null
                        at Function.loadFromDatabaseIfNecessary (/opt/iobroker/node_modules/zigbee-herdsman/dist/controller/model/device.js:200:55)
                        at Function.byIeeeAddr (/opt/iobroker/node_modules/zigbee-herdsman/dist/controller/model/device.js:208:16)
                        at Controller.getDeviceByIeeeAddr (/opt/iobroker/node_modules/zigbee-herdsman/dist/controller/controller.js:235:31)
                        at ZigbeeController.getDevice (/opt/iobroker/node_modules/iobroker.zigbee/lib/zigbeecontroller.js:212:30)
                        at ZigbeeController.permitJoin (/opt/iobroker/node_modules/iobroker.zigbee/lib/zigbeecontroller.js:319:30)
                        at ZigbeeController.stop (/opt/iobroker/node_modules/iobroker.zigbee/lib/zigbeecontroller.js:306:24)
                        at processTicksAndRejections (internal/process/task_queues.js:97:5)
                        at async Zigbee.onUnload (/opt/iobroker/node_modules/iobroker.zigbee/main.js:334:17))
                        2020-05-02 16:47:41.245 - info: zigbee.1 (9847) terminating
                        2020-05-02 16:47:41.247 - info: zigbee.1 (9847) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
                        2020-05-02 16:47:41.775 - info: host.raspberrypi instance system.adapter.zigbee.1 terminated with code 156 (156)
                        2020-05-02 16:47:43.812 - info: host.raspberrypi instance system.adapter.zigbee.1 started with pid 11027
                        2020-05-02 16:47:46.082 - info: zigbee.1 (11027) starting. Version 1.1.1 in /opt/iobroker/node_modules/iobroker.zigbee, node: v12.16.2
                        2020-05-02 16:47:46.150 - error: zigbee.1 (11027) Serial port not selected! Go to settings page.
                        2020-05-02 16:47:46.155 - info: zigbee.1 (11027) Starting Zigbee...
                        2020-05-02 16:47:46.609 - info: zigbee.1 (11027) Coordinator firmware version: {"type":"ConBee2","meta":{"transportrev":0,"product":0,"majorrel":38,"minorrel":74,"maintrel":0,"revision":"0x264a0700"}}
                        2020-05-02 16:47:53.137 - info: zigbee.1 (11027) Unable to disable LED, unsupported function.
                        2020-05-02 16:47:53.139 - info: zigbee.1 (11027) --> transmitPower : normal
                        2020-05-02 16:47:53.141 - info: zigbee.1 (11027) Unable to set transmit power, unsupported function.
                        2020-05-02 16:47:53.144 - info: zigbee.1 (11027) Currently no devices.
                        2020-05-02 16:47:53.145 - info: zigbee.1 (11027) Zigbee started
                        2020-05-02 16:48:41.400 - info: zigbee.1 (11027) Zigbee: allowing new devices to join.
                        2020-05-02 16:48:54.061 - info: zigbee.1 (11027) Starting interview of '0x000b57fffe46ebec'
                        2020-05-02 16:49:05.697 - info: zigbee.1 (11027) Successfully interviewed '0x000b57fffe46ebec', device has succesfully been paired
                        2020-05-02 16:49:05.699 - info: zigbee.1 (11027) Device '0x000b57fffe46ebec' is supported, identified as: Danalock BT/ZB smartlock (V3-BTZB)
                        2020-05-02 16:49:05.703 - info: zigbee.1 (11027) Configuring 0x000b57fffe46ebec V3-BTZB
                        2020-05-02 16:49:07.709 - error: zigbee.1 (11027) Failed to configure 0x000b57fffe46ebec V3-BTZB, attempt 1 (Error: ConfigureReporting 0x000b57fffe46ebec/1 closuresDoorLock([{"attribute":"lockState","minimumReportInterval":0,"maximumReportInterval":3600,"reportableChange":0}], {"timeout":10000,"manufacturerCode":null,"disableDefaultResponse":true}) failed (Error: Status 'INVALID_DATA_TYPE')
                        at Endpoint. (/opt/iobroker/node_modules/zigbee-herdsman/dist/controller/model/endpoint.js:326:23)
                        at Generator.next ()
                        at fulfilled (/opt/iobroker/node_modules/zigbee-herdsman/dist/controller/model/endpoint.js:5:58))
                        2020-05-02 16:49:25.572 - info: zigbee.1 (11027) Configuring 0x000b57fffe46ebec V3-BTZB
                        2020-05-02 16:49:27.590 - error: zigbee.1 (11027) Failed to configure 0x000b57fffe46ebec V3-BTZB, attempt 2 (Error: ConfigureReporting 0x000b57fffe46ebec/1 closuresDoorLock([{"attribute":"lockState","minimumReportInterval":0,"maximumReportInterval":3600,"reportableChange":0}], {"timeout":10000,"manufacturerCode":null,"disableDefaultResponse":true}) failed (Error: Status 'INVALID_DATA_TYPE')
                        at Endpoint. (/opt/iobroker/node_modules/zigbee-herdsman/dist/controller/model/endpoint.js:326:23)
                        at Generator.next ()
                        at fulfilled (/opt/iobroker/node_modules/zigbee-herdsman/dist/controller/model/endpoint.js:5:58))
                        2020-05-02 16:49:28.590 - info: zigbee.1 (11027) Configuring 0x000b57fffe46ebec V3-BTZB
                        2020-05-02 16:49:30.607 - error: zigbee.1 (11027) Failed to configure 0x000b57fffe46ebec V3-BTZB, attempt 3 (Error: ConfigureReporting 0x000b57fffe46ebec/1 closuresDoorLock([{"attribute":"lockState","minimumReportInterval":0,"maximumReportInterval":3600,"reportableChange":0}], {"timeout":10000,"manufacturerCode":null,"disableDefaultResponse":true}) failed (Error: Status 'INVALID_DATA_TYPE')
                        at Endpoint. (/opt/iobroker/node_modules/zigbee-herdsman/dist/controller/model/endpoint.js:326:23)
                        at Generator.next ()
                        at fulfilled (/opt/iobroker/node_modules/zigbee-herdsman/dist/controller/model/endpoint.js:5:58))
                        2020-05-02 16:49:31.618 - info: zigbee.1 (11027) Configuring 0x000b57fffe46ebec V3-BTZB
                        2020-05-02 16:49:33.630 - error: zigbee.1 (11027) Failed to configure 0x000b57fffe46ebec V3-BTZB, attempt 4 (Error: ConfigureReporting 0x000b57fffe46ebec/1 closuresDoorLock([{"attribute":"lockState","minimumReportInterval":0,"maximumReportInterval":3600,"reportableChange":0}], {"timeout":10000,"manufacturerCode":null,"disableDefaultResponse":true}) failed (Error: Status 'INVALID_DATA_TYPE')
                        at Endpoint. (/opt/iobroker/node_modules/zigbee-herdsman/dist/controller/model/endpoint.js:326:23)
                        at Generator.next ()
                        at fulfilled (/opt/iobroker/node_modules/zigbee-herdsman/dist/controller/model/endpoint.js:5:58))
                        2020-05-02 16:49:34.631 - info: zigbee.1 (11027) Configuring 0x000b57fffe46ebec V3-BTZB
                        2020-05-02 16:49:36.649 - error: zigbee.1 (11027) Failed to configure 0x000b57fffe46ebec V3-BTZB, attempt 5 (Error: ConfigureReporting 0x000b57fffe46ebec/1 closuresDoorLock([{"attribute":"lockState","minimumReportInterval":0,"maximumReportInterval":3600,"reportableChange":0}], {"timeout":10000,"manufacturerCode":null,"disableDefaultResponse":true}) failed (Error: Status 'INVALID_DATA_TYPE')
                        at Endpoint. (/opt/iobroker/node_modules/zigbee-herdsman/dist/controller/model/endpoint.js:326:23)
                        at Generator.next ()
                        at fulfilled (/opt/iobroker/node_modules/zigbee-herdsman/dist/controller/model/endpoint.js:5:58))
                        2020-05-02 16:49:43.076 - info: zigbee.1 (11027) Zigbee: stop joining
                        2020-05-02 16:52:52.952 - info: host.raspberrypi stopInstance system.adapter.zigbee.1 (force=false, process=true)
                        2020-05-02 16:52:52.964 - info: host.raspberrypi stopInstance system.adapter.zigbee.1 send kill signal
                        2020-05-02 16:52:52.965 - info: zigbee.1 (11027) Got terminate signal TERMINATE_YOURSELF
                        2020-05-02 16:52:52.967 - info: zigbee.1 (11027) cleaned everything up...
                        2020-05-02 16:52:52.970 - info: zigbee.1 (11027) Zigbee: disabling joining new devices.
                        2020-05-02 16:52:53.470 - info: zigbee.1 (11027) terminating
                        2020-05-02 16:52:53.471 - info: zigbee.1 (11027) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
                        2020-05-02 16:52:53.970 - info: host.raspberrypi stopInstance system.adapter.zigbee.1 killing pid 11027
                        2020-05-02 16:52:54.028 - info: host.raspberrypi instance system.adapter.zigbee.1 terminated with code 156 (156)
                        2020-05-02 16:52:55.524 - info: host.raspberrypi instance system.adapter.zigbee.1 started with pid 18536
                        2020-05-02 16:52:57.823 - info: zigbee.1 (18536) starting. Version 1.1.1 in /opt/iobroker/node_modules/iobroker.zigbee, node: v12.16.2
                        2020-05-02 16:52:57.869 - error: zigbee.1 (18536) Serial port not selected! Go to settings page.
                        2020-05-02 16:52:57.873 - info: zigbee.1 (18536) Starting Zigbee...
                        2020-05-02 16:52:58.322 - info: zigbee.1 (18536) Coordinator firmware version: {"type":"ConBee2","meta":{"transportrev":0,"product":0,"majorrel":38,"minorrel":74,"maintrel":0,"revision":"0x264a0700"}}
                        2020-05-02 16:52:58.523 - info: zigbee.1 (18536) Unable to disable LED, unsupported function.
                        2020-05-02 16:52:58.524 - info: zigbee.1 (18536) --> transmitPower : normal
                        2020-05-02 16:52:58.525 - info: zigbee.1 (18536) Unable to set transmit power, unsupported function.
                        2020-05-02 16:52:58.530 - info: zigbee.1 (18536) Currently 1 devices are joined:
                        2020-05-02 16:52:58.533 - info: zigbee.1 (18536) Configuring 0x000b57fffe46ebec V3-BTZB
                        2020-05-02 16:52:58.540 - info: zigbee.1 (18536) 0x000b57fffe46ebec (addr 61935): V3-BTZB - Danalock BT/ZB smartlock (EndDevice)
                        2020-05-02 16:52:58.541 - info: zigbee.1 (18536) Zigbee started
                        2020-05-02 16:53:02.407 - error: zigbee.1 (18536) Failed to configure 0x000b57fffe46ebec V3-BTZB, attempt 1 (Error: ConfigureReporting 0x000b57fffe46ebec/1 closuresDoorLock([{"attribute":"lockState","minimumReportInterval":0,"maximumReportInterval":3600,"reportableChange":0}], {"timeout":10000,"manufacturerCode":null,"disableDefaultResponse":true}) failed (Error: Status 'INVALID_DATA_TYPE')
                        at Endpoint. (/opt/iobroker/node_modules/zigbee-herdsman/dist/controller/model/endpoint.js:326:23)
                        at Generator.next ()
                        at fulfilled (/opt/iobroker/node_modules/zigbee-herdsman/dist/controller/model/endpoint.js:5:58))
                        2020-05-02 16:53:30.919 - info: zigbee.1 (18536) Configuring 0x000b57fffe46ebec V3-BTZB
                        2020-05-02 16:53:33.426 - error: zigbee.1 (18536) Failed to configure 0x000b57fffe46ebec V3-BTZB, attempt 2 (Error: ConfigureReporting 0x000b57fffe46ebec/1 closuresDoorLock([{"attribute":"lockState","minimumReportInterval":0,"maximumReportInterval":3600,"reportableChange":0}], {"timeout":10000,"manufacturerCode":null,"disableDefaultResponse":true}) failed (Error: Status 'INVALID_DATA_TYPE')
                        at Endpoint. (/opt/iobroker/node_modules/zigbee-herdsman/dist/controller/model/endpoint.js:326:23)
                        at Generator.next ()
                        at fulfilled (/opt/iobroker/node_modules/zigbee-herdsman/dist/controller/model/endpoint.js:5:58))
                        2020-05-02 16:53:47.481 - info: zigbee.1 (18536) Configuring 0x000b57fffe46ebec V3-BTZB
                        2020-05-02 16:53:49.984 - error: zigbee.1 (18536) Failed to configure 0x000b57fffe46ebec V3-BTZB, attempt 3 (Error: ConfigureReporting 0x000b57fffe46ebec/1 closuresDoorLock([{"attribute":"lockState","minimumReportInterval":0,"maximumReportInterval":3600,"reportableChange":0}], {"timeout":10000,"manufacturerCode":null,"disableDefaultResponse":true}) failed (Error: Status 'INVALID_DATA_TYPE')
                        at Endpoint. (/opt/iobroker/node_modules/zigbee-herdsman/dist/controller/model/endpoint.js:326:23)
                        at Generator.next ()
                        at fulfilled (/opt/iobroker/node_modules/zigbee-herdsman/dist/controller/model/endpoint.js:5:58))
                        2020-05-02 16:56:02.105 - info: zigbee.1 (18536) Configuring 0x000b57fffe46ebec V3-BTZB
                        2020-05-02 16:56:07.125 - error: zigbee.1 (18536) Failed to configure 0x000b57fffe46ebec V3-BTZB, attempt 4 (Error: ConfigureReporting 0x000b57fffe46ebec/1 closuresDoorLock([{"attribute":"lockState","minimumReportInterval":0,"maximumReportInterval":3600,"reportableChange":0}], {"timeout":10000,"manufacturerCode":null,"disableDefaultResponse":true}) failed (Error: Status 'INVALID_DATA_TYPE')
                        at Endpoint. (/opt/iobroker/node_modules/zigbee-herdsman/dist/controller/model/endpoint.js:326:23)
                        at Generator.next ()
                        at fulfilled (/opt/iobroker/node_modules/zigbee-herdsman/dist/controller/model/endpoint.js:5:58))
                        2020-05-02 16:56:53.605 - info: zigbee.1 (18536) Configuring 0x000b57fffe46ebec V3-BTZB
                        2020-05-02 16:56:57.118 - error: zigbee.1 (18536) Failed to configure 0x000b57fffe46ebec V3-BTZB, attempt 5 (Error: ConfigureReporting 0x000b57fffe46ebec/1 closuresDoorLock([{"attribute":"lockState","minimumReportInterval":0,"maximumReportInterval":3600,"reportableChange":0}], {"timeout":10000,"manufacturerCode":null,"disableDefaultResponse":true}) failed (Error: Status 'INVALID_DATA_TYPE')
                        at Endpoint. (/opt/iobroker/node_modules/zigbee-herdsman/dist/controller/model/endpoint.js:326:23)
                        at Generator.next ()
                        at fulfilled (/opt/iobroker/node_modules/zigbee-herdsman/dist/controller/model/endpoint.js:5:58))
                        

                        ... und wieder zeigt available nicht den richtigen zustand an

                        hab die batterie erneut rausgenommen ... wieder kein kontakt bzw kein lock / unlock möglich
                        neustart der instanz bring nichts

                        2020-05-02 17:28:36.558 - info: host.raspberrypi stopInstance system.adapter.zigbee.1 (force=false, process=true)
                        2020-05-02 17:28:36.570 - info: host.raspberrypi stopInstance system.adapter.zigbee.1 send kill signal
                        2020-05-02 17:28:36.571 - info: zigbee.1 (3673) Got terminate signal TERMINATE_YOURSELF
                        2020-05-02 17:28:36.573 - info: zigbee.1 (3673) cleaned everything up...
                        2020-05-02 17:28:36.576 - info: zigbee.1 (3673) Zigbee: disabling joining new devices.
                        2020-05-02 17:28:37.076 - info: zigbee.1 (3673) terminating
                        2020-05-02 17:28:37.078 - info: zigbee.1 (3673) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
                        2020-05-02 17:28:37.576 - info: host.raspberrypi stopInstance system.adapter.zigbee.1 killing pid 3673
                        2020-05-02 17:28:37.629 - info: host.raspberrypi instance system.adapter.zigbee.1 terminated with code 156 (156)
                        2020-05-02 17:28:39.129 - info: host.raspberrypi instance system.adapter.zigbee.1 started with pid 5617
                        2020-05-02 17:28:41.476 - info: zigbee.1 (5617) starting. Version 1.1.1 in /opt/iobroker/node_modules/iobroker.zigbee, node: v12.16.2
                        2020-05-02 17:28:41.510 - info: zigbee.1 (5617) Starting Zigbee...
                        2020-05-02 17:28:41.928 - info: zigbee.1 (5617) Coordinator firmware version: {"type":"ConBee2","meta":{"transportrev":0,"product":0,"majorrel":38,"minorrel":74,"maintrel":0,"revision":"0x264a0700"}}
                        2020-05-02 17:28:42.131 - info: zigbee.1 (5617) Unable to disable LED, unsupported function.
                        2020-05-02 17:28:42.132 - info: zigbee.1 (5617) --> transmitPower : normal
                        2020-05-02 17:28:42.134 - info: zigbee.1 (5617) Unable to set transmit power, unsupported function.
                        2020-05-02 17:28:42.142 - info: zigbee.1 (5617) Currently 1 devices are joined:
                        2020-05-02 17:28:42.148 - info: zigbee.1 (5617) Configuring 0x000b57fffe46ebec V3-BTZB
                        2020-05-02 17:28:42.162 - info: zigbee.1 (5617) 0x000b57fffe46ebec (addr 61935): V3-BTZB - Danalock BT/ZB smartlock (EndDevice)
                        2020-05-02 17:28:42.164 - info: zigbee.1 (5617) Zigbee started
                        2020-05-02 17:29:42.783 - error: zigbee.1 (5617) Failed to configure 0x000b57fffe46ebec V3-BTZB, attempt 1 (Error: Bind 0x000b57fffe46ebec/1 closuresDoorLock from '0x00212effff05994f/1' failed (undefined)
                        at Endpoint. (/opt/iobroker/node_modules/zigbee-herdsman/dist/controller/model/endpoint.js:244:23)
                        at Generator.throw ()
                        at rejected (/opt/iobroker/node_modules/zigbee-herdsman/dist/controller/model/endpoint.js:6:65))
                        

                        das gerät scheint zwar kontakt zu haben, aber kommunikation ist nicht möglich

                        wieder lässt sich das Lock nicht aus der instanz löschen und beim pairing erscheint dann folgendes

                        2020-05-02 17:47:24.636 - info: zigbee.1 (5617) Do action on 0x000b57fffe46ebec V3-BTZB
                        2020-05-02 17:47:34.795 - info: zigbee.1 (5617) Do action on 0x000b57fffe46ebec V3-BTZB
                        2020-05-02 17:48:07.605 - info: zigbee.1 (5617) Do action on 0x000b57fffe46ebec V3-BTZB
                        2020-05-02 17:48:12.949 - info: zigbee.1 (5617) Zigbee: allowing new devices to join.
                        2020-05-02 17:48:24.967 - error: zigbee.1 (5617) Failed to do action 0x000b57fffe46ebec V3-BTZB, attempt 1 (TypeError: Cannot read property 'stack' of undefined
                        at Object.action (/opt/iobroker/node_modules/iobroker.zigbee/lib/zigbeecontroller.js:360:69))
                        2020-05-02 17:48:34.975 - error: zigbee.1 (5617) Failed to do action 0x000b57fffe46ebec V3-BTZB, attempt 1 (TypeError: Cannot read property 'stack' of undefined
                        at Object.action (/opt/iobroker/node_modules/iobroker.zigbee/lib/zigbeecontroller.js:360:69))
                        2020-05-02 17:49:07.984 - error: zigbee.1 (5617) Failed to do action 0x000b57fffe46ebec V3-BTZB, attempt 1 (TypeError: Cannot read property 'stack' of undefined
                        at Object.action (/opt/iobroker/node_modules/iobroker.zigbee/lib/zigbeecontroller.js:360:69))
                        2020-05-02 17:49:19.007 - info: zigbee.1 (5617) Zigbee: stop joining
                        

                        ich hoffe sehr, dass meine ausführung helfen ... bin auch gerne bereit weitere test zu machen

                        danke schön

                        plasma :-)

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

                        @Plasmachef sagte in Zigbee Adapter und Conbee Unterstützung:

                        Failed to configure 0x000b57fffe46ebec V3-BTZB, attempt 1

                        der Danalock bekommt "Failed to configure 0x000b57fffe46ebec V3-BTZB" .. ergo keine konfiguration vom Conbee...

                        ist ja hat beta ..

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

                        PlasmachefP 1 Antwort Letzte Antwort
                        0
                        • arteckA arteck

                          @Plasmachef sagte in Zigbee Adapter und Conbee Unterstützung:

                          Failed to configure 0x000b57fffe46ebec V3-BTZB, attempt 1

                          der Danalock bekommt "Failed to configure 0x000b57fffe46ebec V3-BTZB" .. ergo keine konfiguration vom Conbee...

                          ist ja hat beta ..

                          PlasmachefP Offline
                          PlasmachefP Offline
                          Plasmachef
                          schrieb am zuletzt editiert von Plasmachef
                          #89

                          @arteck sagte in Zigbee Adapter und Conbee Unterstützung:

                          @Plasmachef sagte in Zigbee Adapter und Conbee Unterstützung:

                          Failed to configure 0x000b57fffe46ebec V3-BTZB, attempt 1

                          der Danalock bekommt "Failed to configure 0x000b57fffe46ebec V3-BTZB" .. ergo keine konfiguration vom Conbee...

                          ist ja hat beta ..

                          danke für die schnelle Antwort :-)

                          was heißt das jetzt für mich?
                          wie kann ich unterstützen / helfen? ... was braucht ihr /du?

                          arteckA 1 Antwort Letzte Antwort
                          0
                          • PlasmachefP Offline
                            PlasmachefP Offline
                            Plasmachef
                            schrieb am zuletzt editiert von
                            #90

                            im übrigen hab ich festgestellt, dass ich die "verbrannten instanzen" zurücksetzen kann, indem ich unter /iobroker-data die verzeichnisse zigbee_0 bzw zigbee_1 entferne, nachdem ich die instanzen gelöscht hatte.

                            1 Antwort Letzte Antwort
                            0
                            • PlasmachefP Plasmachef

                              @arteck sagte in Zigbee Adapter und Conbee Unterstützung:

                              @Plasmachef sagte in Zigbee Adapter und Conbee Unterstützung:

                              Failed to configure 0x000b57fffe46ebec V3-BTZB, attempt 1

                              der Danalock bekommt "Failed to configure 0x000b57fffe46ebec V3-BTZB" .. ergo keine konfiguration vom Conbee...

                              ist ja hat beta ..

                              danke für die schnelle Antwort :-)

                              was heißt das jetzt für mich?
                              wie kann ich unterstützen / helfen? ... was braucht ihr /du?

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

                              @Plasmachef ich garnix... da ich den Conbee und das Danalok nicht habe.. kann ich dir nix zu sagen.. sry

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

                              1 Antwort Letzte Antwort
                              0
                              • c_hoch_bC Offline
                                c_hoch_bC Offline
                                c_hoch_b
                                schrieb am zuletzt editiert von c_hoch_b
                                #92

                                Moin,

                                ich habe jetzt angefangen meine Geräte zu Pairen und bei dem Hue-Dimmer-Switch bekomme ich diverse Fehlermeldungen (siehe Log) das einbinden wird aber abgeschlossen. Doch ohne funktion.
                                Hab auch schon mehrfach Gelöscht und neu-Gepairt, leider ohne Erfolg.

                                
                                zigbee.0	2020-05-03 09:54:04.677	error	at rejected (/opt/iobroker/node_modules/zigbee-herdsman/dist/controller/model/endpoint.js:6:65))
                                zigbee.0	2020-05-03 09:54:04.677	error	at Generator.throw (<anonymous>)
                                zigbee.0	2020-05-03 09:54:04.677	error	at Endpoint.<anonymous> (/opt/iobroker/node_modules/zigbee-herdsman/dist/controller/model/endpoint.js:244:23)
                                zigbee.0	2020-05-03 09:54:04.677	error	(1328) Failed to configure 0x001788010807ecb2 RWL021, attempt 1 (Error: Bind 0x001788010807ecb2/1 genOnOff from '0x00212effff048af7/1' failed
                                
                                

                                Raspi 4, MacOS, CCU 2, Conbee2, HomeKit/ Yahka, Homebridge, Hue,-Bulb/Switches/Sensors, Harmony, Kodi, Tado, Osram, Xiaomi, HomeMatic, Marantz, VU+, Alexa (Echo‘s)

                                c_hoch_bC 1 Antwort Letzte Antwort
                                0
                                • c_hoch_bC c_hoch_b

                                  Moin,

                                  ich habe jetzt angefangen meine Geräte zu Pairen und bei dem Hue-Dimmer-Switch bekomme ich diverse Fehlermeldungen (siehe Log) das einbinden wird aber abgeschlossen. Doch ohne funktion.
                                  Hab auch schon mehrfach Gelöscht und neu-Gepairt, leider ohne Erfolg.

                                  
                                  zigbee.0	2020-05-03 09:54:04.677	error	at rejected (/opt/iobroker/node_modules/zigbee-herdsman/dist/controller/model/endpoint.js:6:65))
                                  zigbee.0	2020-05-03 09:54:04.677	error	at Generator.throw (<anonymous>)
                                  zigbee.0	2020-05-03 09:54:04.677	error	at Endpoint.<anonymous> (/opt/iobroker/node_modules/zigbee-herdsman/dist/controller/model/endpoint.js:244:23)
                                  zigbee.0	2020-05-03 09:54:04.677	error	(1328) Failed to configure 0x001788010807ecb2 RWL021, attempt 1 (Error: Bind 0x001788010807ecb2/1 genOnOff from '0x00212effff048af7/1' failed
                                  
                                  
                                  c_hoch_bC Offline
                                  c_hoch_bC Offline
                                  c_hoch_b
                                  schrieb am zuletzt editiert von
                                  #93

                                  @c_hoch_b
                                  beim Hue Motion Sensor sieht es auch nicht besser aus...

                                  
                                  zigbee.0	2020-05-03 10:03:01.460	error	at fulfilled (/opt/iobroker/node_modules/zigbee-herdsman/dist/controller/model/endpoint.js:5:58))
                                  zigbee.0	2020-05-03 10:03:01.460	error	at Generator.next (<anonymous>)
                                  zigbee.0	2020-05-03 10:03:01.460	error	at Endpoint.<anonymous> (/opt/iobroker/node_modules/zigbee-herdsman/dist/controller/model/endpoint.js:326:23)
                                  zigbee.0	2020-05-03 10:03:01.460	error	(1328) Failed to configure 0x0017880106f46ae3 SML001, attempt 1 (Error: ConfigureReporting 0x0017880106f46ae3/2 genPowerCfg([{"attribute":"bat
                                  
                                  

                                  könnte es mit LightLink zusammenhängen??

                                  Raspi 4, MacOS, CCU 2, Conbee2, HomeKit/ Yahka, Homebridge, Hue,-Bulb/Switches/Sensors, Harmony, Kodi, Tado, Osram, Xiaomi, HomeMatic, Marantz, VU+, Alexa (Echo‘s)

                                  PlasmachefP 1 Antwort Letzte Antwort
                                  0
                                  • c_hoch_bC c_hoch_b

                                    @c_hoch_b
                                    beim Hue Motion Sensor sieht es auch nicht besser aus...

                                    
                                    zigbee.0	2020-05-03 10:03:01.460	error	at fulfilled (/opt/iobroker/node_modules/zigbee-herdsman/dist/controller/model/endpoint.js:5:58))
                                    zigbee.0	2020-05-03 10:03:01.460	error	at Generator.next (<anonymous>)
                                    zigbee.0	2020-05-03 10:03:01.460	error	at Endpoint.<anonymous> (/opt/iobroker/node_modules/zigbee-herdsman/dist/controller/model/endpoint.js:326:23)
                                    zigbee.0	2020-05-03 10:03:01.460	error	(1328) Failed to configure 0x0017880106f46ae3 SML001, attempt 1 (Error: ConfigureReporting 0x0017880106f46ae3/2 genPowerCfg([{"attribute":"bat
                                    
                                    

                                    könnte es mit LightLink zusammenhängen??

                                    PlasmachefP Offline
                                    PlasmachefP Offline
                                    Plasmachef
                                    schrieb am zuletzt editiert von
                                    #94

                                    @c_hoch_b Arteck hat mir bei

                                    Failed to configure 0x0017880106f46ae3 SML001
                                    

                                    so geantwortet:

                                    " .. ergo keine konfiguration vom Conbee...

                                    ist ja hat beta .."

                                    siehe paar Einträge drüber!

                                    c_hoch_bC 1 Antwort Letzte Antwort
                                    0
                                    • PlasmachefP Plasmachef

                                      @c_hoch_b Arteck hat mir bei

                                      Failed to configure 0x0017880106f46ae3 SML001
                                      

                                      so geantwortet:

                                      " .. ergo keine konfiguration vom Conbee...

                                      ist ja hat beta .."

                                      siehe paar Einträge drüber!

                                      c_hoch_bC Offline
                                      c_hoch_bC Offline
                                      c_hoch_b
                                      schrieb am zuletzt editiert von
                                      #95

                                      @Plasmachef
                                      schräg... meine Aqara Sensoren/Schalter werden ohne Probleme erkannt und laufen.

                                      Und ausgerechnet die HUE-Sachen machen Probleme...

                                      Raspi 4, MacOS, CCU 2, Conbee2, HomeKit/ Yahka, Homebridge, Hue,-Bulb/Switches/Sensors, Harmony, Kodi, Tado, Osram, Xiaomi, HomeMatic, Marantz, VU+, Alexa (Echo‘s)

                                      PlasmachefP 1 Antwort Letzte Antwort
                                      0
                                      • c_hoch_bC c_hoch_b

                                        @Plasmachef
                                        schräg... meine Aqara Sensoren/Schalter werden ohne Probleme erkannt und laufen.

                                        Und ausgerechnet die HUE-Sachen machen Probleme...

                                        PlasmachefP Offline
                                        PlasmachefP Offline
                                        Plasmachef
                                        schrieb am zuletzt editiert von
                                        #96

                                        @c_hoch_b

                                        ich kauf mir jetzt einen "CC2531 ZigBee USB-Sick" dann ist das Thema durch :-)

                                        c_hoch_bC 1 Antwort Letzte Antwort
                                        0
                                        • PlasmachefP Plasmachef

                                          @c_hoch_b

                                          ich kauf mir jetzt einen "CC2531 ZigBee USB-Sick" dann ist das Thema durch :-)

                                          c_hoch_bC Offline
                                          c_hoch_bC Offline
                                          c_hoch_b
                                          schrieb am zuletzt editiert von
                                          #97

                                          @Plasmachef
                                          lt. Amazon ist der Dienstag hier ;-)

                                          Raspi 4, MacOS, CCU 2, Conbee2, HomeKit/ Yahka, Homebridge, Hue,-Bulb/Switches/Sensors, Harmony, Kodi, Tado, Osram, Xiaomi, HomeMatic, Marantz, VU+, Alexa (Echo‘s)

                                          PlasmachefP 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

                                          740

                                          Online

                                          32.4k

                                          Benutzer

                                          81.4k

                                          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