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

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

Community Forum

donate donate
  1. ioBroker Community Home
  2. Deutsch
  3. Tester
  4. Test Alpha Homekit-Controller 0.0.x

NEWS

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

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

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

Test Alpha Homekit-Controller 0.0.x

Geplant Angeheftet Gesperrt Verschoben Tester
260 Beiträge 27 Kommentatoren 43.0k Aufrufe 24 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.
  • apollon77A apollon77

    @strathcole Ok, sorry aber mit so nem kastrierten Log kann ich nix anfangen. Gern auch per E-mail an iobroker@fischer-ka.de in vollständig mit Link zu dem Thema hier. Danke

    StrathColeS Offline
    StrathColeS Offline
    StrathCole
    schrieb am zuletzt editiert von
    #105

    @apollon77 Okay, schicke ich per Mail.

    SolarWatt-Anlage mit 9,6 kWp – KOSTAL Plenticore Plus 10 – BYD B-Box HV 8,96 – Viessmann Vitocal 333g – Zehnder ComfoD 350 (Comfoair 350) mit RS232-Ethernet-Konverter

    1 Antwort Letzte Antwort
    0
    • StrathColeS StrathCole

      @apollon77 sagte in Test Alpha Homekit-Controller 0.0.x:

      @strathcole ppuuhhh da antwortet das device nicht so wie es sollte beim pairen.
      Kannst du es mir Apple Home App Pairen?

      Habe keinerlei iOS Geräte. Daher kann ich so etwas leider nicht testen.

      Ansonsten musst du mit mehr debug machen wie es hier im thread weiter oben steht --> https://forum.iobroker.net/post/720099

      .0","callback":{"message":{"deviceId":"BLE-XXXXXXXXX","pin":"xxxx-xxxx"},"id":226,"ack":false,"time":1639987045204},"_id":6119781})
        hap-controller:gatt-connection connect peripheral +16s
        hap-controller:gatt-connection XXXXXXXXX/XXXXXXXXX Write for characteristic 0000004f0000100080000026bb765291 0003000d00 +4s
        hap-controller:gatt-connection XXXXXXXXX/XXXXXXXXX Received data for characteristic 0000004f0000100080000026bb765291 0200000300010101 +59ms
        hap-controller:gatt-connection disconnect peripheral +1ms
        hap-controller:gatt-connection Peripheral disconnected +15ms
      2021-12-20 08:57:28.894  - debug: homekit-controller.0 (7491) BLE-XXXXXXXXX Start Homekit Device Client initialization
        hap-controller:gatt-connection connect peripheral +20ms
        hap-controller:tlv Add 1 bytes for tag 6: 01 +23s
        hap-controller:tlv Add 1 bytes for tag 0: 00 +1ms
        hap-controller:tlv Add 6 bytes for tag 1: 060101000100 +1ms
        hap-controller:tlv Add 1 bytes for tag 9: 01 +1ms
        hap-controller:gatt-connection XXXXXXXXX/XXXXXXXXX Write for characteristic 0000004c0000100080000026bb765291 0002000b000b000106060101000100090101 +3s
        hap-controller:gatt-connection XXXXXXXXX/XXXXXXXXX Received data for characteristic 0000004c0000100080000026bb765291 0200009d0101ff06010203ff9c87f60bd1cf8502b3b4 +2s
        hap-controller:gatt-connection XXXXXXXXX/XXXXXXXXX Received data for characteristic 0000004c0000100080000026bb765291  +45ms
        hap-controller:tlv Read 255 bytes for tag 1: 06010203ff9c87f60bd1cf8502b3b4 +2s
        hap-controller:tlv Read 1 bytes for tag 6: 02 +1ms
        hap-controller:tlv Read 255 bytes for tag 3: 9c87f60bd1cf8502b3b4 +1ms
      2021-12-20 08:57:33.303  - debug: homekit-controller.0 (7491) Response to Command pairDevice: {"success":false,"error":"Cannot pair with device BLE-XXXXXXXXX because of error undefined (undefined): M2: Missing salt"}
      2021-12-20 08:57:33.305  - debug: homekit-controller.0 (7491) sendTo "pairDevice" to system.adapter.admin.0 from system.adapter.homekit-controller.0
      

      Vom Device:

      {
        "type": "folder",
        "common": {
          "name": "Nuki_324566 (BLE-XXXXXXXXX)"
        },
        "native": {
          "serviceType": "BLE",
          "id": "BLE-XXXXXXXXX",
          "lastService": {
            "name": "Nuki_xxxxxxx",
            "CoID": 76,
            "TY": 6,
            "AIL": 49,
            "SF": 1,
            "DeviceID": "yyyyyyyyyyyy",
            "ACID": 6,
            "GSN": 1,
            "CN": 2,
            "CV": 2,
            "c#": 2,
            "id": "XXXXXXXXX",
            "ci": 6,
            "availableToPair": true
          }
        },
        "from": "system.adapter.homekit-controller.0",
        "user": "system.user.admin",
        "ts": 1639986435029,
        "_id": "homekit-controller.0.BLE-XXXXXXXXX",
        "acl": {
          "object": 1636,
          "owner": "system.user.admin",
          "ownerGroup": "system.group.administrator"
        }
      }```
      apollon77A Offline
      apollon77A Offline
      apollon77
      schrieb am zuletzt editiert von
      #106

      @strathcole PS: Also wnen das Log wirklich so ist dann ist es ... ja ... so das die Nuki nicht nach Apple Home Spec antwortet. Es fehlt der "Salt" in den Daten die das Gerät auf die erste Pair Anfrage zurückgibt.

      Von daher müsste man echt versuchen ob es mit Apple Home geht. Wenn ja muss man ggf experimentieren. Wenn Apple home auch nicht tut musst du dich an den Nuki Support wenden. Ggf mal schauen ob es Firmware updates gibt?

      Beitrag hat geholfen? Votet rechts unten im Beitrag :-) https://paypal.me/Apollon77 / https://github.com/sponsors/Apollon77

      • Debug-Log für Instanz einschalten? Admin -> Instanzen -> Expertenmodus -> Instanz aufklappen - Loglevel ändern
      • Logfiles auf Platte /opt/iobroker/log/… nutzen, Admin schneidet Zeilen ab
      1 Antwort Letzte Antwort
      1
      • luup smartL Offline
        luup smartL Offline
        luup smart
        schrieb am zuletzt editiert von
        #107

        Hallo @apollon77 ,
        ich habe ein Problem mit meinem Eve Degree und Eve Thermo.
        Der Adapter findet die Geräte und man hat auch die Auswahl sie zu identifizieren oder zu pairen. Leider kommt bei beiden Geräten immer eine Fehlermeldung.

        hier die Fehlermeldung beim identifizieren:
        Error_identify_eve.png

        und die Fehlermeldung die ich beim pairen bekomme:
        Error_Eve_homekit.png

        Hier wäre auch mal ein debug log, in dem ich versuche zu identifizieren und zu pairen.
        Siehst du vielleicht an was es liegen könnte?

        2021-12-20 21:32:40.373 - info: host.raspberrypi "system.adapter.homekit-controller.0" enabled
        2021-12-20 21:32:40.543 - info: host.raspberrypi instance system.adapter.homekit-controller.0 started with pid 7772
        2021-12-20 21:32:41.792 - debug: homekit-controller.0 (7772) Redis Objects: Use Redis connection: 127.0.0.1:9001
        2021-12-20 21:32:41.860 - debug: homekit-controller.0 (7772) Objects client ready ... initialize now
        2021-12-20 21:32:41.864 - debug: homekit-controller.0 (7772) Objects create System PubSub Client
        2021-12-20 21:32:41.867 - debug: homekit-controller.0 (7772) Objects create User PubSub Client
        2021-12-20 21:32:41.869 - debug: homekit-controller.0 (7772) Objects client initialize lua scripts
        2021-12-20 21:32:41.951 - debug: homekit-controller.0 (7772) Objects connected to redis: 127.0.0.1:9001
        2021-12-20 21:32:41.955 - silly: homekit-controller.0 (7772) redis psubscribe cfg.o.system.user.*
        2021-12-20 21:32:41.962 - debug: homekit-controller.0 (7772) objectDB connected
        2021-12-20 21:32:41.976 - debug: homekit-controller.0 (7772) Redis States: Use Redis connection: 127.0.0.1:9000
        2021-12-20 21:32:42.034 - debug: homekit-controller.0 (7772) States create System PubSub Client
        2021-12-20 21:32:42.036 - debug: homekit-controller.0 (7772) States create User PubSub Client
        2021-12-20 21:32:42.065 - debug: homekit-controller.0 (7772) States connected to redis: 127.0.0.1:9000
        2021-12-20 21:32:42.066 - debug: homekit-controller.0 (7772) statesDB connected
        2021-12-20 21:32:42.350 - debug: homekit-controller.0 (7772) Plugin sentry Initialize Plugin (enabled=true)
        2021-12-20 21:32:42.898 - info: homekit-controller.0 (7772) starting. Version 0.3.3 in /opt/iobroker/node_modules/iobroker.homekit-controller, node: v14.18.2, js-controller: 3.3.21
        2021-12-20 21:32:43.131 - silly: homekit-controller.0 (7772) States system redis pmessage system.adapter.homekit-controller.0.logLevel/system.adapter.homekit-controller.0.logLevel:{"val":"silly","ack":true,"ts":1640032363116,"q":0,"from":"system.adapter.homekit-controller.0","lc":1639997736189}
        2021-12-20 21:32:43.168 - debug: homekit-controller.0 (7772) Init 3 known devices without discovery ...
        2021-12-20 21:32:43.170 - info: homekit-controller.0 (7772) BLE-D0:90:C0:FA:26:0A (Eve Degree CE8E) found without pairing data but available for pairing: Create basic objects
        2021-12-20 21:32:43.171 - debug: homekit-controller.0 (7772) Service: {"name":"Eve Degree CE8E","CoID":76,"TY":6,"AIL":49,"SF":1,"DeviceID":"d0:90:c0:fa:26:0a","ACID":10,"GSN":9,"CN":3,"CV":2,"c#":3,"id":"d0:90:c0:fa:26:0a","ci":10,"availableToPair":true}
        2021-12-20 21:32:43.193 - silly: homekit-controller.0 (7772) States user redis pmessage homekit-controller.0.*/homekit-controller.0.info.connection:{"val":false,"ack":true,"ts":1640032363175,"q":0,"from":"system.adapter.homekit-controller.0","user":"system.user.admin","lc":1639996763128}
        2021-12-20 21:32:43.197 - debug: homekit-controller.0 (7772) state homekit-controller.0.info.connection changed: false (ack = true)
        2021-12-20 21:32:43.248 - debug: homekit-controller.0 (7772) Discovered IP device up: E3:51:E1:BD:E4:9B/Philips hue - 2237EF
        2021-12-20 21:32:43.249 - debug: homekit-controller.0 (7772) IP-E3:51:E1:BD:E4:9B Discovered IP device: {"name":"Philips hue - 2237EF","address":"192.168.178.77","port":8080,"c#":32,"ff":1,"id":"E3:51:E1:BD:E4:9B","md":"BSB002","pv":"1.1","s#":307,"sf":0,"ci":2,"availableToPair":false}
        2021-12-20 21:32:43.249 - info: homekit-controller.0 (7772) IP-E3:51:E1:BD:E4:9B (Philips hue - 2237EF) found without known pairing data and already paired: ignoring
        2021-12-20 21:32:43.306 - silly: homekit-controller.0 (7772) States user redis pmessage homekit-controller.0.*/homekit-controller.0.BLE-D0:90:C0:FA:26:0A.info.connectionType:{"val":"BLE","ack":true,"ts":1640032363304,"q":0,"from":"system.adapter.homekit-controller.0","user":"system.user.admin","lc":1639997024319}
        2021-12-20 21:32:43.307 - debug: homekit-controller.0 (7772) state homekit-controller.0.BLE-D0:90:C0:FA:26:0A.info.connectionType changed: BLE (ack = true)
        2021-12-20 21:32:43.318 - silly: homekit-controller.0 (7772) States user redis pmessage homekit-controller.0.*/homekit-controller.0.BLE-D0:90:C0:FA:26:0A.info.id:{"val":"d0:90:c0:fa:26:0a","ack":true,"ts":1640032363315,"q":0,"from":"system.adapter.homekit-controller.0","user":"system.user.admin","lc":1639997024340}
        2021-12-20 21:32:43.320 - debug: homekit-controller.0 (7772) state homekit-controller.0.BLE-D0:90:C0:FA:26:0A.info.id changed: d0:90:c0:fa:26:0a (ack = true)
        2021-12-20 21:32:43.351 - silly: homekit-controller.0 (7772) States user redis pmessage homekit-controller.0.*/homekit-controller.0.BLE-D0:90:C0:FA:26:0A.info.connected:{"val":false,"ack":true,"ts":1640032363348,"q":0,"from":"system.adapter.homekit-controller.0","user":"system.user.admin","lc":1639997024348}
        2021-12-20 21:32:43.353 - debug: homekit-controller.0 (7772) state homekit-controller.0.BLE-D0:90:C0:FA:26:0A.info.connected changed: false (ack = true)
        2021-12-20 21:32:43.372 - silly: homekit-controller.0 (7772) States user redis pmessage homekit-controller.0.*/homekit-controller.0.BLE-D0:90:C0:FA:26:0A.admin.isPaired:{"val":false,"ack":true,"ts":1640032363370,"q":0,"from":"system.adapter.homekit-controller.0","user":"system.user.admin","lc":1639997024359}
        2021-12-20 21:32:43.374 - debug: homekit-controller.0 (7772) state homekit-controller.0.BLE-D0:90:C0:FA:26:0A.admin.isPaired changed: false (ack = true)
        2021-12-20 21:32:43.389 - silly: homekit-controller.0 (7772) States user redis pmessage homekit-controller.0.*/homekit-controller.0.BLE-D0:90:C0:FA:26:0A.info.lastDiscovered:{"val":1640032363173,"ack":true,"ts":1640032363386,"q":0,"from":"system.adapter.homekit-controller.0","user":"system.user.admin","lc":1640032363386}
        2021-12-20 21:32:43.390 - debug: homekit-controller.0 (7772) state homekit-controller.0.BLE-D0:90:C0:FA:26:0A.info.lastDiscovered changed: 1640032363173 (ack = true)
        2021-12-20 21:32:43.403 - info: homekit-controller.0 (7772) BLE-51:E5:E1:EE:94:26 (Eve Degree CE8E) found without pairing data but available for pairing: Create basic objects
        2021-12-20 21:32:43.403 - debug: homekit-controller.0 (7772) Service: {"name":"Eve Degree CE8E","CoID":76,"TY":6,"AIL":49,"SF":1,"DeviceID":"51:e5:e1:ee:94:26","ACID":10,"GSN":4,"CN":3,"CV":2,"c#":3,"id":"51:e5:e1:ee:94:26","ci":10,"availableToPair":true}
        2021-12-20 21:32:43.444 - silly: homekit-controller.0 (7772) States user redis pmessage homekit-controller.0.*/homekit-controller.0.BLE-51:E5:E1:EE:94:26.info.connectionType:{"val":"BLE","ack":true,"ts":1640032363441,"q":0,"from":"system.adapter.homekit-controller.0","user":"system.user.admin","lc":1639997204892}
        2021-12-20 21:32:43.446 - debug: homekit-controller.0 (7772) state homekit-controller.0.BLE-51:E5:E1:EE:94:26.info.connectionType changed: BLE (ack = true)
        2021-12-20 21:32:43.506 - silly: homekit-controller.0 (7772) States user redis pmessage homekit-controller.0.*/homekit-controller.0.BLE-51:E5:E1:EE:94:26.info.id:{"val":"51:e5:e1:ee:94:26","ack":true,"ts":1640032363504,"q":0,"from":"system.adapter.homekit-controller.0","user":"system.user.admin","lc":1639997204923}
        2021-12-20 21:32:43.508 - debug: homekit-controller.0 (7772) state homekit-controller.0.BLE-51:E5:E1:EE:94:26.info.id changed: 51:e5:e1:ee:94:26 (ack = true)
        2021-12-20 21:32:43.518 - silly: homekit-controller.0 (7772) States user redis pmessage homekit-controller.0.*/homekit-controller.0.BLE-51:E5:E1:EE:94:26.info.connected:{"val":false,"ack":true,"ts":1640032363516,"q":0,"from":"system.adapter.homekit-controller.0","user":"system.user.admin","lc":1639997204935}
        2021-12-20 21:32:43.521 - debug: homekit-controller.0 (7772) state homekit-controller.0.BLE-51:E5:E1:EE:94:26.info.connected changed: false (ack = true)
        2021-12-20 21:32:43.535 - silly: homekit-controller.0 (7772) States user redis pmessage homekit-controller.0.*/homekit-controller.0.BLE-51:E5:E1:EE:94:26.admin.isPaired:{"val":false,"ack":true,"ts":1640032363533,"q":0,"from":"system.adapter.homekit-controller.0","user":"system.user.admin","lc":1639997204947}
        2021-12-20 21:32:43.537 - debug: homekit-controller.0 (7772) state homekit-controller.0.BLE-51:E5:E1:EE:94:26.admin.isPaired changed: false (ack = true)
        2021-12-20 21:32:43.596 - silly: homekit-controller.0 (7772) States user redis pmessage homekit-controller.0.*/homekit-controller.0.BLE-51:E5:E1:EE:94:26.info.lastDiscovered:{"val":1640032363404,"ack":true,"ts":1640032363594,"q":0,"from":"system.adapter.homekit-controller.0","user":"system.user.admin","lc":1640032363594}
        2021-12-20 21:32:43.597 - debug: homekit-controller.0 (7772) state homekit-controller.0.BLE-51:E5:E1:EE:94:26.info.lastDiscovered changed: 1640032363404 (ack = true)
        2021-12-20 21:32:43.617 - info: homekit-controller.0 (7772) BLE-BD:1D:5A:A0:4B:BD (Eve Thermo 4A8B) found without pairing data but available for pairing: Create basic objects
        2021-12-20 21:32:43.618 - debug: homekit-controller.0 (7772) Service: {"name":"Eve Thermo 4A8B","CoID":76,"TY":6,"AIL":49,"SF":1,"DeviceID":"bd:1d:5a:a0:4b:bd","ACID":9,"GSN":2,"CN":5,"CV":2,"c#":5,"id":"bd:1d:5a:a0:4b:bd","ci":9,"availableToPair":true}
        2021-12-20 21:32:43.650 - silly: homekit-controller.0 (7772) States user redis pmessage homekit-controller.0.*/homekit-controller.0.BLE-BD:1D:5A:A0:4B:BD.info.connectionType:{"val":"BLE","ack":true,"ts":1640032363648,"q":0,"from":"system.adapter.homekit-controller.0","user":"system.user.admin","lc":1639999277985}
        2021-12-20 21:32:43.653 - debug: homekit-controller.0 (7772) state homekit-controller.0.BLE-BD:1D:5A:A0:4B:BD.info.connectionType changed: BLE (ack = true)
        2021-12-20 21:32:43.671 - silly: homekit-controller.0 (7772) States user redis pmessage homekit-controller.0.*/homekit-controller.0.BLE-BD:1D:5A:A0:4B:BD.info.id:{"val":"bd:1d:5a:a0:4b:bd","ack":true,"ts":1640032363669,"q":0,"from":"system.adapter.homekit-controller.0","user":"system.user.admin","lc":1639999278008}
        2021-12-20 21:32:43.672 - debug: homekit-controller.0 (7772) state homekit-controller.0.BLE-BD:1D:5A:A0:4B:BD.info.id changed: bd:1d:5a:a0:4b:bd (ack = true)
        2021-12-20 21:32:43.726 - silly: homekit-controller.0 (7772) States user redis pmessage homekit-controller.0.*/homekit-controller.0.BLE-BD:1D:5A:A0:4B:BD.info.connected:{"val":false,"ack":true,"ts":1640032363724,"q":0,"from":"system.adapter.homekit-controller.0","user":"system.user.admin","lc":1639999278041}
        2021-12-20 21:32:43.728 - debug: homekit-controller.0 (7772) state homekit-controller.0.BLE-BD:1D:5A:A0:4B:BD.info.connected changed: false (ack = true)
        2021-12-20 21:32:43.750 - silly: homekit-controller.0 (7772) States user redis pmessage homekit-controller.0.*/homekit-controller.0.BLE-BD:1D:5A:A0:4B:BD.admin.isPaired:{"val":false,"ack":true,"ts":1640032363748,"q":0,"from":"system.adapter.homekit-controller.0","user":"system.user.admin","lc":1639999278076}
        2021-12-20 21:32:43.752 - debug: homekit-controller.0 (7772) state homekit-controller.0.BLE-BD:1D:5A:A0:4B:BD.admin.isPaired changed: false (ack = true)
        2021-12-20 21:32:43.770 - silly: homekit-controller.0 (7772) States user redis pmessage homekit-controller.0.*/homekit-controller.0.BLE-BD:1D:5A:A0:4B:BD.info.lastDiscovered:{"val":1640032363618,"ack":true,"ts":1640032363766,"q":0,"from":"system.adapter.homekit-controller.0","user":"system.user.admin","lc":1640032363766}
        2021-12-20 21:32:43.774 - debug: homekit-controller.0 (7772) state homekit-controller.0.BLE-BD:1D:5A:A0:4B:BD.info.lastDiscovered changed: 1640032363618 (ack = true)
        2021-12-20 21:32:45.307 - debug: homekit-controller.0 (7772) Discovered BLE device up: 51:e5:e1:ee:94:26/Eve
        2021-12-20 21:32:45.308 - debug: homekit-controller.0 (7772) BLE-51:E5:E1:EE:94:26 Discovered BLE device: {"name":"Eve","CoID":76,"TY":6,"AIL":49,"SF":1,"DeviceID":"51:e5:e1:ee:94:26","ACID":10,"GSN":4,"CN":3,"CV":2,"c#":3,"id":"51:e5:e1:ee:94:26","ci":10,"availableToPair":true}
        2021-12-20 21:32:45.309 - info: homekit-controller.0 (7772) BLE-51:E5:E1:EE:94:26 (Eve) found without pairing data but available for pairing: Create basic objects
        2021-12-20 21:32:45.310 - debug: homekit-controller.0 (7772) Service: {"name":"Eve","CoID":76,"TY":6,"AIL":49,"SF":1,"DeviceID":"51:e5:e1:ee:94:26","ACID":10,"GSN":4,"CN":3,"CV":2,"c#":3,"id":"51:e5:e1:ee:94:26","ci":10,"availableToPair":true}
        2021-12-20 21:32:45.857 - silly: homekit-controller.0 (7772) States user redis pmessage homekit-controller.0.*/homekit-controller.0.BLE-51:E5:E1:EE:94:26.info.connectionType:{"val":"BLE","ack":true,"ts":1640032365847,"q":0,"from":"system.adapter.homekit-controller.0","user":"system.user.admin","lc":1639997204892}
        2021-12-20 21:32:45.859 - debug: homekit-controller.0 (7772) state homekit-controller.0.BLE-51:E5:E1:EE:94:26.info.connectionType changed: BLE (ack = true)
        2021-12-20 21:32:45.952 - silly: homekit-controller.0 (7772) States user redis pmessage homekit-controller.0.*/homekit-controller.0.BLE-51:E5:E1:EE:94:26.info.id:{"val":"51:e5:e1:ee:94:26","ack":true,"ts":1640032365950,"q":0,"from":"system.adapter.homekit-controller.0","user":"system.user.admin","lc":1639997204923}
        2021-12-20 21:32:45.955 - debug: homekit-controller.0 (7772) state homekit-controller.0.BLE-51:E5:E1:EE:94:26.info.id changed: 51:e5:e1:ee:94:26 (ack = true)
        2021-12-20 21:32:45.969 - silly: homekit-controller.0 (7772) States user redis pmessage homekit-controller.0.*/homekit-controller.0.BLE-51:E5:E1:EE:94:26.info.connected:{"val":false,"ack":true,"ts":1640032365967,"q":0,"from":"system.adapter.homekit-controller.0","user":"system.user.admin","lc":1639997204935}
        2021-12-20 21:32:45.971 - debug: homekit-controller.0 (7772) state homekit-controller.0.BLE-51:E5:E1:EE:94:26.info.connected changed: false (ack = true)
        2021-12-20 21:32:45.990 - silly: homekit-controller.0 (7772) States user redis pmessage homekit-controller.0.*/homekit-controller.0.BLE-51:E5:E1:EE:94:26.admin.isPaired:{"val":false,"ack":true,"ts":1640032365987,"q":0,"from":"system.adapter.homekit-controller.0","user":"system.user.admin","lc":1639997204947}
        2021-12-20 21:32:45.992 - debug: homekit-controller.0 (7772) state homekit-controller.0.BLE-51:E5:E1:EE:94:26.admin.isPaired changed: false (ack = true)
        2021-12-20 21:32:46.011 - silly: homekit-controller.0 (7772) States user redis pmessage homekit-controller.0.*/homekit-controller.0.BLE-51:E5:E1:EE:94:26.info.lastDiscovered:{"val":1640032365311,"ack":true,"ts":1640032366009,"q":0,"from":"system.adapter.homekit-controller.0","user":"system.user.admin","lc":1640032366009}
        2021-12-20 21:32:46.012 - debug: homekit-controller.0 (7772) state homekit-controller.0.BLE-51:E5:E1:EE:94:26.info.lastDiscovered changed: 1640032365311 (ack = true)
        2021-12-20 21:32:46.049 - debug: homekit-controller.0 (7772) Discovered BLE device up: bd:1d:5a:a0:4b:bd/Eve Thermo 4A8B
        2021-12-20 21:32:46.049 - debug: homekit-controller.0 (7772) BLE-BD:1D:5A:A0:4B:BD Discovered BLE device: {"name":"Eve Thermo 4A8B","CoID":76,"TY":6,"AIL":49,"SF":1,"DeviceID":"bd:1d:5a:a0:4b:bd","ACID":9,"GSN":2,"CN":5,"CV":2,"c#":5,"id":"bd:1d:5a:a0:4b:bd","ci":9,"availableToPair":true}
        2021-12-20 21:32:46.050 - info: homekit-controller.0 (7772) BLE-BD:1D:5A:A0:4B:BD (Eve Thermo 4A8B) found without pairing data but available for pairing: Create basic objects
        2021-12-20 21:32:46.051 - debug: homekit-controller.0 (7772) Service: {"name":"Eve Thermo 4A8B","CoID":76,"TY":6,"AIL":49,"SF":1,"DeviceID":"bd:1d:5a:a0:4b:bd","ACID":9,"GSN":2,"CN":5,"CV":2,"c#":5,"id":"bd:1d:5a:a0:4b:bd","ci":9,"availableToPair":true}
        2021-12-20 21:32:46.119 - silly: homekit-controller.0 (7772) States user redis pmessage homekit-controller.0.*/homekit-controller.0.BLE-BD:1D:5A:A0:4B:BD.info.connectionType:{"val":"BLE","ack":true,"ts":1640032366116,"q":0,"from":"system.adapter.homekit-controller.0","user":"system.user.admin","lc":1639999277985}
        2021-12-20 21:32:46.121 - debug: homekit-controller.0 (7772) state homekit-controller.0.BLE-BD:1D:5A:A0:4B:BD.info.connectionType changed: BLE (ack = true)
        2021-12-20 21:32:46.134 - silly: homekit-controller.0 (7772) States user redis pmessage homekit-controller.0.*/homekit-controller.0.BLE-BD:1D:5A:A0:4B:BD.info.id:{"val":"bd:1d:5a:a0:4b:bd","ack":true,"ts":1640032366132,"q":0,"from":"system.adapter.homekit-controller.0","user":"system.user.admin","lc":1639999278008}
        2021-12-20 21:32:46.136 - debug: homekit-controller.0 (7772) state homekit-controller.0.BLE-BD:1D:5A:A0:4B:BD.info.id changed: bd:1d:5a:a0:4b:bd (ack = true)
        2021-12-20 21:32:46.186 - silly: homekit-controller.0 (7772) States user redis pmessage homekit-controller.0.*/homekit-controller.0.BLE-BD:1D:5A:A0:4B:BD.info.connected:{"val":false,"ack":true,"ts":1640032366184,"q":0,"from":"system.adapter.homekit-controller.0","user":"system.user.admin","lc":1639999278041}
        2021-12-20 21:32:46.187 - debug: homekit-controller.0 (7772) state homekit-controller.0.BLE-BD:1D:5A:A0:4B:BD.info.connected changed: false (ack = true)
        2021-12-20 21:32:46.202 - silly: homekit-controller.0 (7772) States user redis pmessage homekit-controller.0.*/homekit-controller.0.BLE-BD:1D:5A:A0:4B:BD.admin.isPaired:{"val":false,"ack":true,"ts":1640032366200,"q":0,"from":"system.adapter.homekit-controller.0","user":"system.user.admin","lc":1639999278076}
        2021-12-20 21:32:46.204 - debug: homekit-controller.0 (7772) state homekit-controller.0.BLE-BD:1D:5A:A0:4B:BD.admin.isPaired changed: false (ack = true)
        2021-12-20 21:32:46.223 - silly: homekit-controller.0 (7772) States user redis pmessage homekit-controller.0.*/homekit-controller.0.BLE-BD:1D:5A:A0:4B:BD.info.lastDiscovered:{"val":1640032366052,"ack":true,"ts":1640032366221,"q":0,"from":"system.adapter.homekit-controller.0","user":"system.user.admin","lc":1640032366221}
        2021-12-20 21:32:46.225 - debug: homekit-controller.0 (7772) state homekit-controller.0.BLE-BD:1D:5A:A0:4B:BD.info.lastDiscovered changed: 1640032366052 (ack = true)
        2021-12-20 21:32:46.884 - silly: homekit-controller.0 (7772) States system redis pmessage io.messagebox.system.adapter.homekit-controller.0/io.messagebox.system.adapter.homekit-controller.0:{"command":"getDiscoveredDevices","message":null,"from":"system.adapter.admin.0","callback":{"message":null,"id":323,"ack":false,"time":1640032366881},"_id":26091375}
        2021-12-20 21:32:46.886 - debug: homekit-controller.0 (7772) Message getDiscoveredDevices received: {"command":"getDiscoveredDevices","message":null,"from":"system.adapter.admin.0","callback":{"message":null,"id":323,"ack":false,"time":1640032366881},"_id":26091375})
        2021-12-20 21:32:46.888 - debug: homekit-controller.0 (7772) Response to Command getDiscoveredDevices: {"success":true,"error":false,"devices":[{"id":"BLE-D0:90:C0:FA:26:0A","serviceType":"BLE","connected":false,"discovered":true,"availableToPair":true,"discoveredName":"Eve Degree CE8E","discoveredCategory":"Sensor","pairedWithThisInstance":false},{"id":"BLE-51:E5:E1:EE:94:26","serviceType":"BLE","connected":false,"discovered":true,"availableToPair":true,"discoveredName":"Eve","discoveredCategory":"Sensor","pairedWithThisInstance":false},{"id":"BLE-BD:1D:5A:A0:4B:BD","serviceType":"BLE","connected":false,"discovered":true,"availableToPair":true,"discoveredName":"Eve Thermo 4A8B","discoveredCategory":"Thermostat","pairedWithThisInstance":false},{"id":"IP-E3:51:E1:BD:E4:9B","serviceType":"IP","connected":false,"discovered":true,"availableToPair":false,"discoveredName":"Philips hue - 2237EF","discoveredCategory":"Bridge","pairedWithThisInstance":false}]}
        2021-12-20 21:32:46.890 - debug: homekit-controller.0 (7772) sendTo "getDiscoveredDevices" to system.adapter.admin.0 from system.adapter.homekit-controller.0
        2021-12-20 21:32:58.260 - silly: homekit-controller.0 (7772) States system redis pmessage io.messagebox.system.adapter.homekit-controller.0/io.messagebox.system.adapter.homekit-controller.0:{"command":"identify","message":{"deviceId":"BLE-D0:90:C0:FA:26:0A"},"from":"system.adapter.admin.0","callback":{"message":{"deviceId":"BLE-D0:90:C0:FA:26:0A"},"id":324,"ack":false,"time":1640032378257},"_id":26091376}
        2021-12-20 21:32:58.262 - debug: homekit-controller.0 (7772) Message identify received: {"command":"identify","message":{"deviceId":"BLE-D0:90:C0:FA:26:0A"},"from":"system.adapter.admin.0","callback":{"message":{"deviceId":"BLE-D0:90:C0:FA:26:0A"},"id":324,"ack":false,"time":1640032378257},"_id":26091376})
        2021-12-20 21:32:58.263 - debug: homekit-controller.0 (7772) Device BLE-D0:90:C0:FA:26:0A: Identify triggered
        2021-12-20 21:32:58.270 - debug: homekit-controller.0 (7772) Response to Command identify: {"success":false,"error":"Cannot identify device BLE-D0:90:C0:FA:26:0A because of error undefined: Cannot read property 'state' of undefined"}
        2021-12-20 21:32:58.271 - debug: homekit-controller.0 (7772) sendTo "identify" to system.adapter.admin.0 from system.adapter.homekit-controller.0
        2021-12-20 21:33:03.495 - silly: homekit-controller.0 (7772) States system redis pmessage io.messagebox.system.adapter.homekit-controller.0/io.messagebox.system.adapter.homekit-controller.0:{"command":"identify","message":{"deviceId":"BLE-51:E5:E1:EE:94:26"},"from":"system.adapter.admin.0","callback":{"message":{"deviceId":"BLE-51:E5:E1:EE:94:26"},"id":326,"ack":false,"time":1640032383492},"_id":26091378}
        2021-12-20 21:33:03.497 - debug: homekit-controller.0 (7772) Message identify received: {"command":"identify","message":{"deviceId":"BLE-51:E5:E1:EE:94:26"},"from":"system.adapter.admin.0","callback":{"message":{"deviceId":"BLE-51:E5:E1:EE:94:26"},"id":326,"ack":false,"time":1640032383492},"_id":26091378})
        2021-12-20 21:33:03.498 - debug: homekit-controller.0 (7772) Device BLE-51:E5:E1:EE:94:26: Identify triggered
        2021-12-20 21:33:06.195 - debug: homekit-controller.0 (7772) Response to Command identify: {"success":false,"error":"Cannot identify device BLE-51:E5:E1:EE:94:26 because of error undefined: undefined"}
        2021-12-20 21:33:06.196 - debug: homekit-controller.0 (7772) sendTo "identify" to system.adapter.admin.0 from system.adapter.homekit-controller.0
        2021-12-20 21:33:17.701 - silly: homekit-controller.0 (7772) States system redis pmessage io.messagebox.system.adapter.homekit-controller.0/io.messagebox.system.adapter.homekit-controller.0:{"command":"identify","message":{"deviceId":"BLE-BD:1D:5A:A0:4B:BD"},"from":"system.adapter.admin.0","callback":{"message":{"deviceId":"BLE-BD:1D:5A:A0:4B:BD"},"id":327,"ack":false,"time":1640032397698},"_id":26091379}
        2021-12-20 21:33:17.702 - debug: homekit-controller.0 (7772) Message identify received: {"command":"identify","message":{"deviceId":"BLE-BD:1D:5A:A0:4B:BD"},"from":"system.adapter.admin.0","callback":{"message":{"deviceId":"BLE-BD:1D:5A:A0:4B:BD"},"id":327,"ack":false,"time":1640032397698},"_id":26091379})
        2021-12-20 21:33:17.703 - debug: homekit-controller.0 (7772) Device BLE-BD:1D:5A:A0:4B:BD: Identify triggered
        2021-12-20 21:33:19.811 - debug: homekit-controller.0 (7772) Response to Command identify: {"success":false,"error":"Cannot identify device BLE-BD:1D:5A:A0:4B:BD because of error undefined: undefined"}
        2021-12-20 21:33:19.813 - debug: homekit-controller.0 (7772) sendTo "identify" to system.adapter.admin.0 from system.adapter.homekit-controller.0
        2021-12-20 21:33:40.333 - silly: homekit-controller.0 (7772) States system redis pmessage io.messagebox.system.adapter.homekit-controller.0/io.messagebox.system.adapter.homekit-controller.0:{"command":"pairDevice","message":{"deviceId":"BLE-51:E5:E1:EE:94:26","pin":"343-86-912 "},"from":"system.adapter.admin.0","callback":{"message":{"deviceId":"BLE-51:E5:E1:EE:94:26","pin":"343-86-912 "},"id":328,"ack":false,"time":1640032420331},"_id":26091380}
        2021-12-20 21:33:40.335 - debug: homekit-controller.0 (7772) Message pairDevice received: {"command":"pairDevice","message":{"deviceId":"BLE-51:E5:E1:EE:94:26","pin":"343-86-912 "},"from":"system.adapter.admin.0","callback":{"message":{"deviceId":"BLE-51:E5:E1:EE:94:26","pin":"343-86-912 "},"id":328,"ack":false,"time":1640032420331},"_id":26091380})
        2021-12-20 21:33:43.349 - debug: homekit-controller.0 (7772) Response to Command pairDevice: {"success":false,"error":"Cannot retrieve BLE PairMethod for device BLE-51:E5:E1:EE:94:26 because of error undefined: undefined"}
        2021-12-20 21:33:43.350 - debug: homekit-controller.0 (7772) sendTo "pairDevice" to system.adapter.admin.0 from system.adapter.homekit-controller.0
        apollon77A 1 Antwort Letzte Antwort
        0
        • luup smartL luup smart

          Hallo @apollon77 ,
          ich habe ein Problem mit meinem Eve Degree und Eve Thermo.
          Der Adapter findet die Geräte und man hat auch die Auswahl sie zu identifizieren oder zu pairen. Leider kommt bei beiden Geräten immer eine Fehlermeldung.

          hier die Fehlermeldung beim identifizieren:
          Error_identify_eve.png

          und die Fehlermeldung die ich beim pairen bekomme:
          Error_Eve_homekit.png

          Hier wäre auch mal ein debug log, in dem ich versuche zu identifizieren und zu pairen.
          Siehst du vielleicht an was es liegen könnte?

          2021-12-20 21:32:40.373 - info: host.raspberrypi "system.adapter.homekit-controller.0" enabled
          2021-12-20 21:32:40.543 - info: host.raspberrypi instance system.adapter.homekit-controller.0 started with pid 7772
          2021-12-20 21:32:41.792 - debug: homekit-controller.0 (7772) Redis Objects: Use Redis connection: 127.0.0.1:9001
          2021-12-20 21:32:41.860 - debug: homekit-controller.0 (7772) Objects client ready ... initialize now
          2021-12-20 21:32:41.864 - debug: homekit-controller.0 (7772) Objects create System PubSub Client
          2021-12-20 21:32:41.867 - debug: homekit-controller.0 (7772) Objects create User PubSub Client
          2021-12-20 21:32:41.869 - debug: homekit-controller.0 (7772) Objects client initialize lua scripts
          2021-12-20 21:32:41.951 - debug: homekit-controller.0 (7772) Objects connected to redis: 127.0.0.1:9001
          2021-12-20 21:32:41.955 - silly: homekit-controller.0 (7772) redis psubscribe cfg.o.system.user.*
          2021-12-20 21:32:41.962 - debug: homekit-controller.0 (7772) objectDB connected
          2021-12-20 21:32:41.976 - debug: homekit-controller.0 (7772) Redis States: Use Redis connection: 127.0.0.1:9000
          2021-12-20 21:32:42.034 - debug: homekit-controller.0 (7772) States create System PubSub Client
          2021-12-20 21:32:42.036 - debug: homekit-controller.0 (7772) States create User PubSub Client
          2021-12-20 21:32:42.065 - debug: homekit-controller.0 (7772) States connected to redis: 127.0.0.1:9000
          2021-12-20 21:32:42.066 - debug: homekit-controller.0 (7772) statesDB connected
          2021-12-20 21:32:42.350 - debug: homekit-controller.0 (7772) Plugin sentry Initialize Plugin (enabled=true)
          2021-12-20 21:32:42.898 - info: homekit-controller.0 (7772) starting. Version 0.3.3 in /opt/iobroker/node_modules/iobroker.homekit-controller, node: v14.18.2, js-controller: 3.3.21
          2021-12-20 21:32:43.131 - silly: homekit-controller.0 (7772) States system redis pmessage system.adapter.homekit-controller.0.logLevel/system.adapter.homekit-controller.0.logLevel:{"val":"silly","ack":true,"ts":1640032363116,"q":0,"from":"system.adapter.homekit-controller.0","lc":1639997736189}
          2021-12-20 21:32:43.168 - debug: homekit-controller.0 (7772) Init 3 known devices without discovery ...
          2021-12-20 21:32:43.170 - info: homekit-controller.0 (7772) BLE-D0:90:C0:FA:26:0A (Eve Degree CE8E) found without pairing data but available for pairing: Create basic objects
          2021-12-20 21:32:43.171 - debug: homekit-controller.0 (7772) Service: {"name":"Eve Degree CE8E","CoID":76,"TY":6,"AIL":49,"SF":1,"DeviceID":"d0:90:c0:fa:26:0a","ACID":10,"GSN":9,"CN":3,"CV":2,"c#":3,"id":"d0:90:c0:fa:26:0a","ci":10,"availableToPair":true}
          2021-12-20 21:32:43.193 - silly: homekit-controller.0 (7772) States user redis pmessage homekit-controller.0.*/homekit-controller.0.info.connection:{"val":false,"ack":true,"ts":1640032363175,"q":0,"from":"system.adapter.homekit-controller.0","user":"system.user.admin","lc":1639996763128}
          2021-12-20 21:32:43.197 - debug: homekit-controller.0 (7772) state homekit-controller.0.info.connection changed: false (ack = true)
          2021-12-20 21:32:43.248 - debug: homekit-controller.0 (7772) Discovered IP device up: E3:51:E1:BD:E4:9B/Philips hue - 2237EF
          2021-12-20 21:32:43.249 - debug: homekit-controller.0 (7772) IP-E3:51:E1:BD:E4:9B Discovered IP device: {"name":"Philips hue - 2237EF","address":"192.168.178.77","port":8080,"c#":32,"ff":1,"id":"E3:51:E1:BD:E4:9B","md":"BSB002","pv":"1.1","s#":307,"sf":0,"ci":2,"availableToPair":false}
          2021-12-20 21:32:43.249 - info: homekit-controller.0 (7772) IP-E3:51:E1:BD:E4:9B (Philips hue - 2237EF) found without known pairing data and already paired: ignoring
          2021-12-20 21:32:43.306 - silly: homekit-controller.0 (7772) States user redis pmessage homekit-controller.0.*/homekit-controller.0.BLE-D0:90:C0:FA:26:0A.info.connectionType:{"val":"BLE","ack":true,"ts":1640032363304,"q":0,"from":"system.adapter.homekit-controller.0","user":"system.user.admin","lc":1639997024319}
          2021-12-20 21:32:43.307 - debug: homekit-controller.0 (7772) state homekit-controller.0.BLE-D0:90:C0:FA:26:0A.info.connectionType changed: BLE (ack = true)
          2021-12-20 21:32:43.318 - silly: homekit-controller.0 (7772) States user redis pmessage homekit-controller.0.*/homekit-controller.0.BLE-D0:90:C0:FA:26:0A.info.id:{"val":"d0:90:c0:fa:26:0a","ack":true,"ts":1640032363315,"q":0,"from":"system.adapter.homekit-controller.0","user":"system.user.admin","lc":1639997024340}
          2021-12-20 21:32:43.320 - debug: homekit-controller.0 (7772) state homekit-controller.0.BLE-D0:90:C0:FA:26:0A.info.id changed: d0:90:c0:fa:26:0a (ack = true)
          2021-12-20 21:32:43.351 - silly: homekit-controller.0 (7772) States user redis pmessage homekit-controller.0.*/homekit-controller.0.BLE-D0:90:C0:FA:26:0A.info.connected:{"val":false,"ack":true,"ts":1640032363348,"q":0,"from":"system.adapter.homekit-controller.0","user":"system.user.admin","lc":1639997024348}
          2021-12-20 21:32:43.353 - debug: homekit-controller.0 (7772) state homekit-controller.0.BLE-D0:90:C0:FA:26:0A.info.connected changed: false (ack = true)
          2021-12-20 21:32:43.372 - silly: homekit-controller.0 (7772) States user redis pmessage homekit-controller.0.*/homekit-controller.0.BLE-D0:90:C0:FA:26:0A.admin.isPaired:{"val":false,"ack":true,"ts":1640032363370,"q":0,"from":"system.adapter.homekit-controller.0","user":"system.user.admin","lc":1639997024359}
          2021-12-20 21:32:43.374 - debug: homekit-controller.0 (7772) state homekit-controller.0.BLE-D0:90:C0:FA:26:0A.admin.isPaired changed: false (ack = true)
          2021-12-20 21:32:43.389 - silly: homekit-controller.0 (7772) States user redis pmessage homekit-controller.0.*/homekit-controller.0.BLE-D0:90:C0:FA:26:0A.info.lastDiscovered:{"val":1640032363173,"ack":true,"ts":1640032363386,"q":0,"from":"system.adapter.homekit-controller.0","user":"system.user.admin","lc":1640032363386}
          2021-12-20 21:32:43.390 - debug: homekit-controller.0 (7772) state homekit-controller.0.BLE-D0:90:C0:FA:26:0A.info.lastDiscovered changed: 1640032363173 (ack = true)
          2021-12-20 21:32:43.403 - info: homekit-controller.0 (7772) BLE-51:E5:E1:EE:94:26 (Eve Degree CE8E) found without pairing data but available for pairing: Create basic objects
          2021-12-20 21:32:43.403 - debug: homekit-controller.0 (7772) Service: {"name":"Eve Degree CE8E","CoID":76,"TY":6,"AIL":49,"SF":1,"DeviceID":"51:e5:e1:ee:94:26","ACID":10,"GSN":4,"CN":3,"CV":2,"c#":3,"id":"51:e5:e1:ee:94:26","ci":10,"availableToPair":true}
          2021-12-20 21:32:43.444 - silly: homekit-controller.0 (7772) States user redis pmessage homekit-controller.0.*/homekit-controller.0.BLE-51:E5:E1:EE:94:26.info.connectionType:{"val":"BLE","ack":true,"ts":1640032363441,"q":0,"from":"system.adapter.homekit-controller.0","user":"system.user.admin","lc":1639997204892}
          2021-12-20 21:32:43.446 - debug: homekit-controller.0 (7772) state homekit-controller.0.BLE-51:E5:E1:EE:94:26.info.connectionType changed: BLE (ack = true)
          2021-12-20 21:32:43.506 - silly: homekit-controller.0 (7772) States user redis pmessage homekit-controller.0.*/homekit-controller.0.BLE-51:E5:E1:EE:94:26.info.id:{"val":"51:e5:e1:ee:94:26","ack":true,"ts":1640032363504,"q":0,"from":"system.adapter.homekit-controller.0","user":"system.user.admin","lc":1639997204923}
          2021-12-20 21:32:43.508 - debug: homekit-controller.0 (7772) state homekit-controller.0.BLE-51:E5:E1:EE:94:26.info.id changed: 51:e5:e1:ee:94:26 (ack = true)
          2021-12-20 21:32:43.518 - silly: homekit-controller.0 (7772) States user redis pmessage homekit-controller.0.*/homekit-controller.0.BLE-51:E5:E1:EE:94:26.info.connected:{"val":false,"ack":true,"ts":1640032363516,"q":0,"from":"system.adapter.homekit-controller.0","user":"system.user.admin","lc":1639997204935}
          2021-12-20 21:32:43.521 - debug: homekit-controller.0 (7772) state homekit-controller.0.BLE-51:E5:E1:EE:94:26.info.connected changed: false (ack = true)
          2021-12-20 21:32:43.535 - silly: homekit-controller.0 (7772) States user redis pmessage homekit-controller.0.*/homekit-controller.0.BLE-51:E5:E1:EE:94:26.admin.isPaired:{"val":false,"ack":true,"ts":1640032363533,"q":0,"from":"system.adapter.homekit-controller.0","user":"system.user.admin","lc":1639997204947}
          2021-12-20 21:32:43.537 - debug: homekit-controller.0 (7772) state homekit-controller.0.BLE-51:E5:E1:EE:94:26.admin.isPaired changed: false (ack = true)
          2021-12-20 21:32:43.596 - silly: homekit-controller.0 (7772) States user redis pmessage homekit-controller.0.*/homekit-controller.0.BLE-51:E5:E1:EE:94:26.info.lastDiscovered:{"val":1640032363404,"ack":true,"ts":1640032363594,"q":0,"from":"system.adapter.homekit-controller.0","user":"system.user.admin","lc":1640032363594}
          2021-12-20 21:32:43.597 - debug: homekit-controller.0 (7772) state homekit-controller.0.BLE-51:E5:E1:EE:94:26.info.lastDiscovered changed: 1640032363404 (ack = true)
          2021-12-20 21:32:43.617 - info: homekit-controller.0 (7772) BLE-BD:1D:5A:A0:4B:BD (Eve Thermo 4A8B) found without pairing data but available for pairing: Create basic objects
          2021-12-20 21:32:43.618 - debug: homekit-controller.0 (7772) Service: {"name":"Eve Thermo 4A8B","CoID":76,"TY":6,"AIL":49,"SF":1,"DeviceID":"bd:1d:5a:a0:4b:bd","ACID":9,"GSN":2,"CN":5,"CV":2,"c#":5,"id":"bd:1d:5a:a0:4b:bd","ci":9,"availableToPair":true}
          2021-12-20 21:32:43.650 - silly: homekit-controller.0 (7772) States user redis pmessage homekit-controller.0.*/homekit-controller.0.BLE-BD:1D:5A:A0:4B:BD.info.connectionType:{"val":"BLE","ack":true,"ts":1640032363648,"q":0,"from":"system.adapter.homekit-controller.0","user":"system.user.admin","lc":1639999277985}
          2021-12-20 21:32:43.653 - debug: homekit-controller.0 (7772) state homekit-controller.0.BLE-BD:1D:5A:A0:4B:BD.info.connectionType changed: BLE (ack = true)
          2021-12-20 21:32:43.671 - silly: homekit-controller.0 (7772) States user redis pmessage homekit-controller.0.*/homekit-controller.0.BLE-BD:1D:5A:A0:4B:BD.info.id:{"val":"bd:1d:5a:a0:4b:bd","ack":true,"ts":1640032363669,"q":0,"from":"system.adapter.homekit-controller.0","user":"system.user.admin","lc":1639999278008}
          2021-12-20 21:32:43.672 - debug: homekit-controller.0 (7772) state homekit-controller.0.BLE-BD:1D:5A:A0:4B:BD.info.id changed: bd:1d:5a:a0:4b:bd (ack = true)
          2021-12-20 21:32:43.726 - silly: homekit-controller.0 (7772) States user redis pmessage homekit-controller.0.*/homekit-controller.0.BLE-BD:1D:5A:A0:4B:BD.info.connected:{"val":false,"ack":true,"ts":1640032363724,"q":0,"from":"system.adapter.homekit-controller.0","user":"system.user.admin","lc":1639999278041}
          2021-12-20 21:32:43.728 - debug: homekit-controller.0 (7772) state homekit-controller.0.BLE-BD:1D:5A:A0:4B:BD.info.connected changed: false (ack = true)
          2021-12-20 21:32:43.750 - silly: homekit-controller.0 (7772) States user redis pmessage homekit-controller.0.*/homekit-controller.0.BLE-BD:1D:5A:A0:4B:BD.admin.isPaired:{"val":false,"ack":true,"ts":1640032363748,"q":0,"from":"system.adapter.homekit-controller.0","user":"system.user.admin","lc":1639999278076}
          2021-12-20 21:32:43.752 - debug: homekit-controller.0 (7772) state homekit-controller.0.BLE-BD:1D:5A:A0:4B:BD.admin.isPaired changed: false (ack = true)
          2021-12-20 21:32:43.770 - silly: homekit-controller.0 (7772) States user redis pmessage homekit-controller.0.*/homekit-controller.0.BLE-BD:1D:5A:A0:4B:BD.info.lastDiscovered:{"val":1640032363618,"ack":true,"ts":1640032363766,"q":0,"from":"system.adapter.homekit-controller.0","user":"system.user.admin","lc":1640032363766}
          2021-12-20 21:32:43.774 - debug: homekit-controller.0 (7772) state homekit-controller.0.BLE-BD:1D:5A:A0:4B:BD.info.lastDiscovered changed: 1640032363618 (ack = true)
          2021-12-20 21:32:45.307 - debug: homekit-controller.0 (7772) Discovered BLE device up: 51:e5:e1:ee:94:26/Eve
          2021-12-20 21:32:45.308 - debug: homekit-controller.0 (7772) BLE-51:E5:E1:EE:94:26 Discovered BLE device: {"name":"Eve","CoID":76,"TY":6,"AIL":49,"SF":1,"DeviceID":"51:e5:e1:ee:94:26","ACID":10,"GSN":4,"CN":3,"CV":2,"c#":3,"id":"51:e5:e1:ee:94:26","ci":10,"availableToPair":true}
          2021-12-20 21:32:45.309 - info: homekit-controller.0 (7772) BLE-51:E5:E1:EE:94:26 (Eve) found without pairing data but available for pairing: Create basic objects
          2021-12-20 21:32:45.310 - debug: homekit-controller.0 (7772) Service: {"name":"Eve","CoID":76,"TY":6,"AIL":49,"SF":1,"DeviceID":"51:e5:e1:ee:94:26","ACID":10,"GSN":4,"CN":3,"CV":2,"c#":3,"id":"51:e5:e1:ee:94:26","ci":10,"availableToPair":true}
          2021-12-20 21:32:45.857 - silly: homekit-controller.0 (7772) States user redis pmessage homekit-controller.0.*/homekit-controller.0.BLE-51:E5:E1:EE:94:26.info.connectionType:{"val":"BLE","ack":true,"ts":1640032365847,"q":0,"from":"system.adapter.homekit-controller.0","user":"system.user.admin","lc":1639997204892}
          2021-12-20 21:32:45.859 - debug: homekit-controller.0 (7772) state homekit-controller.0.BLE-51:E5:E1:EE:94:26.info.connectionType changed: BLE (ack = true)
          2021-12-20 21:32:45.952 - silly: homekit-controller.0 (7772) States user redis pmessage homekit-controller.0.*/homekit-controller.0.BLE-51:E5:E1:EE:94:26.info.id:{"val":"51:e5:e1:ee:94:26","ack":true,"ts":1640032365950,"q":0,"from":"system.adapter.homekit-controller.0","user":"system.user.admin","lc":1639997204923}
          2021-12-20 21:32:45.955 - debug: homekit-controller.0 (7772) state homekit-controller.0.BLE-51:E5:E1:EE:94:26.info.id changed: 51:e5:e1:ee:94:26 (ack = true)
          2021-12-20 21:32:45.969 - silly: homekit-controller.0 (7772) States user redis pmessage homekit-controller.0.*/homekit-controller.0.BLE-51:E5:E1:EE:94:26.info.connected:{"val":false,"ack":true,"ts":1640032365967,"q":0,"from":"system.adapter.homekit-controller.0","user":"system.user.admin","lc":1639997204935}
          2021-12-20 21:32:45.971 - debug: homekit-controller.0 (7772) state homekit-controller.0.BLE-51:E5:E1:EE:94:26.info.connected changed: false (ack = true)
          2021-12-20 21:32:45.990 - silly: homekit-controller.0 (7772) States user redis pmessage homekit-controller.0.*/homekit-controller.0.BLE-51:E5:E1:EE:94:26.admin.isPaired:{"val":false,"ack":true,"ts":1640032365987,"q":0,"from":"system.adapter.homekit-controller.0","user":"system.user.admin","lc":1639997204947}
          2021-12-20 21:32:45.992 - debug: homekit-controller.0 (7772) state homekit-controller.0.BLE-51:E5:E1:EE:94:26.admin.isPaired changed: false (ack = true)
          2021-12-20 21:32:46.011 - silly: homekit-controller.0 (7772) States user redis pmessage homekit-controller.0.*/homekit-controller.0.BLE-51:E5:E1:EE:94:26.info.lastDiscovered:{"val":1640032365311,"ack":true,"ts":1640032366009,"q":0,"from":"system.adapter.homekit-controller.0","user":"system.user.admin","lc":1640032366009}
          2021-12-20 21:32:46.012 - debug: homekit-controller.0 (7772) state homekit-controller.0.BLE-51:E5:E1:EE:94:26.info.lastDiscovered changed: 1640032365311 (ack = true)
          2021-12-20 21:32:46.049 - debug: homekit-controller.0 (7772) Discovered BLE device up: bd:1d:5a:a0:4b:bd/Eve Thermo 4A8B
          2021-12-20 21:32:46.049 - debug: homekit-controller.0 (7772) BLE-BD:1D:5A:A0:4B:BD Discovered BLE device: {"name":"Eve Thermo 4A8B","CoID":76,"TY":6,"AIL":49,"SF":1,"DeviceID":"bd:1d:5a:a0:4b:bd","ACID":9,"GSN":2,"CN":5,"CV":2,"c#":5,"id":"bd:1d:5a:a0:4b:bd","ci":9,"availableToPair":true}
          2021-12-20 21:32:46.050 - info: homekit-controller.0 (7772) BLE-BD:1D:5A:A0:4B:BD (Eve Thermo 4A8B) found without pairing data but available for pairing: Create basic objects
          2021-12-20 21:32:46.051 - debug: homekit-controller.0 (7772) Service: {"name":"Eve Thermo 4A8B","CoID":76,"TY":6,"AIL":49,"SF":1,"DeviceID":"bd:1d:5a:a0:4b:bd","ACID":9,"GSN":2,"CN":5,"CV":2,"c#":5,"id":"bd:1d:5a:a0:4b:bd","ci":9,"availableToPair":true}
          2021-12-20 21:32:46.119 - silly: homekit-controller.0 (7772) States user redis pmessage homekit-controller.0.*/homekit-controller.0.BLE-BD:1D:5A:A0:4B:BD.info.connectionType:{"val":"BLE","ack":true,"ts":1640032366116,"q":0,"from":"system.adapter.homekit-controller.0","user":"system.user.admin","lc":1639999277985}
          2021-12-20 21:32:46.121 - debug: homekit-controller.0 (7772) state homekit-controller.0.BLE-BD:1D:5A:A0:4B:BD.info.connectionType changed: BLE (ack = true)
          2021-12-20 21:32:46.134 - silly: homekit-controller.0 (7772) States user redis pmessage homekit-controller.0.*/homekit-controller.0.BLE-BD:1D:5A:A0:4B:BD.info.id:{"val":"bd:1d:5a:a0:4b:bd","ack":true,"ts":1640032366132,"q":0,"from":"system.adapter.homekit-controller.0","user":"system.user.admin","lc":1639999278008}
          2021-12-20 21:32:46.136 - debug: homekit-controller.0 (7772) state homekit-controller.0.BLE-BD:1D:5A:A0:4B:BD.info.id changed: bd:1d:5a:a0:4b:bd (ack = true)
          2021-12-20 21:32:46.186 - silly: homekit-controller.0 (7772) States user redis pmessage homekit-controller.0.*/homekit-controller.0.BLE-BD:1D:5A:A0:4B:BD.info.connected:{"val":false,"ack":true,"ts":1640032366184,"q":0,"from":"system.adapter.homekit-controller.0","user":"system.user.admin","lc":1639999278041}
          2021-12-20 21:32:46.187 - debug: homekit-controller.0 (7772) state homekit-controller.0.BLE-BD:1D:5A:A0:4B:BD.info.connected changed: false (ack = true)
          2021-12-20 21:32:46.202 - silly: homekit-controller.0 (7772) States user redis pmessage homekit-controller.0.*/homekit-controller.0.BLE-BD:1D:5A:A0:4B:BD.admin.isPaired:{"val":false,"ack":true,"ts":1640032366200,"q":0,"from":"system.adapter.homekit-controller.0","user":"system.user.admin","lc":1639999278076}
          2021-12-20 21:32:46.204 - debug: homekit-controller.0 (7772) state homekit-controller.0.BLE-BD:1D:5A:A0:4B:BD.admin.isPaired changed: false (ack = true)
          2021-12-20 21:32:46.223 - silly: homekit-controller.0 (7772) States user redis pmessage homekit-controller.0.*/homekit-controller.0.BLE-BD:1D:5A:A0:4B:BD.info.lastDiscovered:{"val":1640032366052,"ack":true,"ts":1640032366221,"q":0,"from":"system.adapter.homekit-controller.0","user":"system.user.admin","lc":1640032366221}
          2021-12-20 21:32:46.225 - debug: homekit-controller.0 (7772) state homekit-controller.0.BLE-BD:1D:5A:A0:4B:BD.info.lastDiscovered changed: 1640032366052 (ack = true)
          2021-12-20 21:32:46.884 - silly: homekit-controller.0 (7772) States system redis pmessage io.messagebox.system.adapter.homekit-controller.0/io.messagebox.system.adapter.homekit-controller.0:{"command":"getDiscoveredDevices","message":null,"from":"system.adapter.admin.0","callback":{"message":null,"id":323,"ack":false,"time":1640032366881},"_id":26091375}
          2021-12-20 21:32:46.886 - debug: homekit-controller.0 (7772) Message getDiscoveredDevices received: {"command":"getDiscoveredDevices","message":null,"from":"system.adapter.admin.0","callback":{"message":null,"id":323,"ack":false,"time":1640032366881},"_id":26091375})
          2021-12-20 21:32:46.888 - debug: homekit-controller.0 (7772) Response to Command getDiscoveredDevices: {"success":true,"error":false,"devices":[{"id":"BLE-D0:90:C0:FA:26:0A","serviceType":"BLE","connected":false,"discovered":true,"availableToPair":true,"discoveredName":"Eve Degree CE8E","discoveredCategory":"Sensor","pairedWithThisInstance":false},{"id":"BLE-51:E5:E1:EE:94:26","serviceType":"BLE","connected":false,"discovered":true,"availableToPair":true,"discoveredName":"Eve","discoveredCategory":"Sensor","pairedWithThisInstance":false},{"id":"BLE-BD:1D:5A:A0:4B:BD","serviceType":"BLE","connected":false,"discovered":true,"availableToPair":true,"discoveredName":"Eve Thermo 4A8B","discoveredCategory":"Thermostat","pairedWithThisInstance":false},{"id":"IP-E3:51:E1:BD:E4:9B","serviceType":"IP","connected":false,"discovered":true,"availableToPair":false,"discoveredName":"Philips hue - 2237EF","discoveredCategory":"Bridge","pairedWithThisInstance":false}]}
          2021-12-20 21:32:46.890 - debug: homekit-controller.0 (7772) sendTo "getDiscoveredDevices" to system.adapter.admin.0 from system.adapter.homekit-controller.0
          2021-12-20 21:32:58.260 - silly: homekit-controller.0 (7772) States system redis pmessage io.messagebox.system.adapter.homekit-controller.0/io.messagebox.system.adapter.homekit-controller.0:{"command":"identify","message":{"deviceId":"BLE-D0:90:C0:FA:26:0A"},"from":"system.adapter.admin.0","callback":{"message":{"deviceId":"BLE-D0:90:C0:FA:26:0A"},"id":324,"ack":false,"time":1640032378257},"_id":26091376}
          2021-12-20 21:32:58.262 - debug: homekit-controller.0 (7772) Message identify received: {"command":"identify","message":{"deviceId":"BLE-D0:90:C0:FA:26:0A"},"from":"system.adapter.admin.0","callback":{"message":{"deviceId":"BLE-D0:90:C0:FA:26:0A"},"id":324,"ack":false,"time":1640032378257},"_id":26091376})
          2021-12-20 21:32:58.263 - debug: homekit-controller.0 (7772) Device BLE-D0:90:C0:FA:26:0A: Identify triggered
          2021-12-20 21:32:58.270 - debug: homekit-controller.0 (7772) Response to Command identify: {"success":false,"error":"Cannot identify device BLE-D0:90:C0:FA:26:0A because of error undefined: Cannot read property 'state' of undefined"}
          2021-12-20 21:32:58.271 - debug: homekit-controller.0 (7772) sendTo "identify" to system.adapter.admin.0 from system.adapter.homekit-controller.0
          2021-12-20 21:33:03.495 - silly: homekit-controller.0 (7772) States system redis pmessage io.messagebox.system.adapter.homekit-controller.0/io.messagebox.system.adapter.homekit-controller.0:{"command":"identify","message":{"deviceId":"BLE-51:E5:E1:EE:94:26"},"from":"system.adapter.admin.0","callback":{"message":{"deviceId":"BLE-51:E5:E1:EE:94:26"},"id":326,"ack":false,"time":1640032383492},"_id":26091378}
          2021-12-20 21:33:03.497 - debug: homekit-controller.0 (7772) Message identify received: {"command":"identify","message":{"deviceId":"BLE-51:E5:E1:EE:94:26"},"from":"system.adapter.admin.0","callback":{"message":{"deviceId":"BLE-51:E5:E1:EE:94:26"},"id":326,"ack":false,"time":1640032383492},"_id":26091378})
          2021-12-20 21:33:03.498 - debug: homekit-controller.0 (7772) Device BLE-51:E5:E1:EE:94:26: Identify triggered
          2021-12-20 21:33:06.195 - debug: homekit-controller.0 (7772) Response to Command identify: {"success":false,"error":"Cannot identify device BLE-51:E5:E1:EE:94:26 because of error undefined: undefined"}
          2021-12-20 21:33:06.196 - debug: homekit-controller.0 (7772) sendTo "identify" to system.adapter.admin.0 from system.adapter.homekit-controller.0
          2021-12-20 21:33:17.701 - silly: homekit-controller.0 (7772) States system redis pmessage io.messagebox.system.adapter.homekit-controller.0/io.messagebox.system.adapter.homekit-controller.0:{"command":"identify","message":{"deviceId":"BLE-BD:1D:5A:A0:4B:BD"},"from":"system.adapter.admin.0","callback":{"message":{"deviceId":"BLE-BD:1D:5A:A0:4B:BD"},"id":327,"ack":false,"time":1640032397698},"_id":26091379}
          2021-12-20 21:33:17.702 - debug: homekit-controller.0 (7772) Message identify received: {"command":"identify","message":{"deviceId":"BLE-BD:1D:5A:A0:4B:BD"},"from":"system.adapter.admin.0","callback":{"message":{"deviceId":"BLE-BD:1D:5A:A0:4B:BD"},"id":327,"ack":false,"time":1640032397698},"_id":26091379})
          2021-12-20 21:33:17.703 - debug: homekit-controller.0 (7772) Device BLE-BD:1D:5A:A0:4B:BD: Identify triggered
          2021-12-20 21:33:19.811 - debug: homekit-controller.0 (7772) Response to Command identify: {"success":false,"error":"Cannot identify device BLE-BD:1D:5A:A0:4B:BD because of error undefined: undefined"}
          2021-12-20 21:33:19.813 - debug: homekit-controller.0 (7772) sendTo "identify" to system.adapter.admin.0 from system.adapter.homekit-controller.0
          2021-12-20 21:33:40.333 - silly: homekit-controller.0 (7772) States system redis pmessage io.messagebox.system.adapter.homekit-controller.0/io.messagebox.system.adapter.homekit-controller.0:{"command":"pairDevice","message":{"deviceId":"BLE-51:E5:E1:EE:94:26","pin":"343-86-912 "},"from":"system.adapter.admin.0","callback":{"message":{"deviceId":"BLE-51:E5:E1:EE:94:26","pin":"343-86-912 "},"id":328,"ack":false,"time":1640032420331},"_id":26091380}
          2021-12-20 21:33:40.335 - debug: homekit-controller.0 (7772) Message pairDevice received: {"command":"pairDevice","message":{"deviceId":"BLE-51:E5:E1:EE:94:26","pin":"343-86-912 "},"from":"system.adapter.admin.0","callback":{"message":{"deviceId":"BLE-51:E5:E1:EE:94:26","pin":"343-86-912 "},"id":328,"ack":false,"time":1640032420331},"_id":26091380})
          2021-12-20 21:33:43.349 - debug: homekit-controller.0 (7772) Response to Command pairDevice: {"success":false,"error":"Cannot retrieve BLE PairMethod for device BLE-51:E5:E1:EE:94:26 because of error undefined: undefined"}
          2021-12-20 21:33:43.350 - debug: homekit-controller.0 (7772) sendTo "pairDevice" to system.adapter.admin.0 from system.adapter.homekit-controller.0
          apollon77A Offline
          apollon77A Offline
          apollon77
          schrieb am zuletzt editiert von
          #108

          @luup-smart Ok, also Beim Degree oben ging Identify und nur pair hat gesponnen :-(

          Dann bitte ebenso fr die identifies die nicht gehen ein "mehr Debug" ala https://forum.iobroker.net/post/720099

          Beitrag hat geholfen? Votet rechts unten im Beitrag :-) https://paypal.me/Apollon77 / https://github.com/sponsors/Apollon77

          • Debug-Log für Instanz einschalten? Admin -> Instanzen -> Expertenmodus -> Instanz aufklappen - Loglevel ändern
          • Logfiles auf Platte /opt/iobroker/log/… nutzen, Admin schneidet Zeilen ab
          luup smartL 1 Antwort Letzte Antwort
          0
          • apollon77A apollon77

            @luup-smart Ok, also Beim Degree oben ging Identify und nur pair hat gesponnen :-(

            Dann bitte ebenso fr die identifies die nicht gehen ein "mehr Debug" ala https://forum.iobroker.net/post/720099

            luup smartL Offline
            luup smartL Offline
            luup smart
            schrieb am zuletzt editiert von
            #109

            @apollon77 Okay, hier wäre der log. :)

            Debug_shell_homekit-controller

            apollon77A 1 Antwort Letzte Antwort
            0
            • luup smartL luup smart

              @apollon77 Okay, hier wäre der log. :)

              Debug_shell_homekit-controller

              apollon77A Offline
              apollon77A Offline
              apollon77
              schrieb am zuletzt editiert von
              #110

              @luup-smart

              hap-controller:gatt-connection connect peripheral +0ms
              hap-controller:gatt-connection disconnect peripheral +3s
              hap-controller:gatt-connection Peripheral disconnected +50ms

              Der Adapter bekommt keine verbindung. Ist das BLE Device frei und nicht von jemand anderem Belegt wie radar2 oder so?

              Aufgabe von "rfkill"?

              Beitrag hat geholfen? Votet rechts unten im Beitrag :-) https://paypal.me/Apollon77 / https://github.com/sponsors/Apollon77

              • Debug-Log für Instanz einschalten? Admin -> Instanzen -> Expertenmodus -> Instanz aufklappen - Loglevel ändern
              • Logfiles auf Platte /opt/iobroker/log/… nutzen, Admin schneidet Zeilen ab
              luup smartL 1 Antwort Letzte Antwort
              0
              • apollon77A apollon77

                @luup-smart

                hap-controller:gatt-connection connect peripheral +0ms
                hap-controller:gatt-connection disconnect peripheral +3s
                hap-controller:gatt-connection Peripheral disconnected +50ms

                Der Adapter bekommt keine verbindung. Ist das BLE Device frei und nicht von jemand anderem Belegt wie radar2 oder so?

                Aufgabe von "rfkill"?

                luup smartL Offline
                luup smartL Offline
                luup smart
                schrieb am zuletzt editiert von
                #111

                @apollon77 Das BLE Device sollte frei sein. Also ich hab keine andern Adapter die BLE verwenden.

                pi@raspberrypi:~ $ rfkill
                ID TYPE      DEVICE      SOFT      HARD
                 0 wlan      phy0   unblocked unblocked
                 1 bluetooth hci0   unblocked unblocked
                1 Antwort Letzte Antwort
                0
                • StrathColeS StrathCole

                  @apollon77 sagte in Test Alpha Homekit-Controller 0.0.x:

                  @strathcole ppuuhhh da antwortet das device nicht so wie es sollte beim pairen.
                  Kannst du es mir Apple Home App Pairen?

                  Habe keinerlei iOS Geräte. Daher kann ich so etwas leider nicht testen.

                  Ansonsten musst du mit mehr debug machen wie es hier im thread weiter oben steht --> https://forum.iobroker.net/post/720099

                  .0","callback":{"message":{"deviceId":"BLE-XXXXXXXXX","pin":"xxxx-xxxx"},"id":226,"ack":false,"time":1639987045204},"_id":6119781})
                    hap-controller:gatt-connection connect peripheral +16s
                    hap-controller:gatt-connection XXXXXXXXX/XXXXXXXXX Write for characteristic 0000004f0000100080000026bb765291 0003000d00 +4s
                    hap-controller:gatt-connection XXXXXXXXX/XXXXXXXXX Received data for characteristic 0000004f0000100080000026bb765291 0200000300010101 +59ms
                    hap-controller:gatt-connection disconnect peripheral +1ms
                    hap-controller:gatt-connection Peripheral disconnected +15ms
                  2021-12-20 08:57:28.894  - debug: homekit-controller.0 (7491) BLE-XXXXXXXXX Start Homekit Device Client initialization
                    hap-controller:gatt-connection connect peripheral +20ms
                    hap-controller:tlv Add 1 bytes for tag 6: 01 +23s
                    hap-controller:tlv Add 1 bytes for tag 0: 00 +1ms
                    hap-controller:tlv Add 6 bytes for tag 1: 060101000100 +1ms
                    hap-controller:tlv Add 1 bytes for tag 9: 01 +1ms
                    hap-controller:gatt-connection XXXXXXXXX/XXXXXXXXX Write for characteristic 0000004c0000100080000026bb765291 0002000b000b000106060101000100090101 +3s
                    hap-controller:gatt-connection XXXXXXXXX/XXXXXXXXX Received data for characteristic 0000004c0000100080000026bb765291 0200009d0101ff06010203ff9c87f60bd1cf8502b3b4 +2s
                    hap-controller:gatt-connection XXXXXXXXX/XXXXXXXXX Received data for characteristic 0000004c0000100080000026bb765291  +45ms
                    hap-controller:tlv Read 255 bytes for tag 1: 06010203ff9c87f60bd1cf8502b3b4 +2s
                    hap-controller:tlv Read 1 bytes for tag 6: 02 +1ms
                    hap-controller:tlv Read 255 bytes for tag 3: 9c87f60bd1cf8502b3b4 +1ms
                  2021-12-20 08:57:33.303  - debug: homekit-controller.0 (7491) Response to Command pairDevice: {"success":false,"error":"Cannot pair with device BLE-XXXXXXXXX because of error undefined (undefined): M2: Missing salt"}
                  2021-12-20 08:57:33.305  - debug: homekit-controller.0 (7491) sendTo "pairDevice" to system.adapter.admin.0 from system.adapter.homekit-controller.0
                  

                  Vom Device:

                  {
                    "type": "folder",
                    "common": {
                      "name": "Nuki_324566 (BLE-XXXXXXXXX)"
                    },
                    "native": {
                      "serviceType": "BLE",
                      "id": "BLE-XXXXXXXXX",
                      "lastService": {
                        "name": "Nuki_xxxxxxx",
                        "CoID": 76,
                        "TY": 6,
                        "AIL": 49,
                        "SF": 1,
                        "DeviceID": "yyyyyyyyyyyy",
                        "ACID": 6,
                        "GSN": 1,
                        "CN": 2,
                        "CV": 2,
                        "c#": 2,
                        "id": "XXXXXXXXX",
                        "ci": 6,
                        "availableToPair": true
                      }
                    },
                    "from": "system.adapter.homekit-controller.0",
                    "user": "system.user.admin",
                    "ts": 1639986435029,
                    "_id": "homekit-controller.0.BLE-XXXXXXXXX",
                    "acl": {
                      "object": 1636,
                      "owner": "system.user.admin",
                      "ownerGroup": "system.group.administrator"
                    }
                  }```
                  apollon77A Offline
                  apollon77A Offline
                  apollon77
                  schrieb am zuletzt editiert von apollon77
                  #112

                  @strathcole Dduuuuuu ... weil ich grad mit nem anderen user dran bin: Wie hast Du denn die PIN eingegeben? Mit oder Ohne Bindestriche? Falls ohne Bindestriche ... mach mal mit XXX-XX-XXX?

                  UUUUNDDDD: Bring mal das Schloss in den Pairing Modus bevor du es versuchst!!! Der andere User hatte den Fehler mit "No salt " auch als das gerät NICHT im Pairing Modus war. Falls du als nächstes nen fehler bekommst das er die PairingMethod nicht ermitteln kann -> GitHub version versuchen

                  Beitrag hat geholfen? Votet rechts unten im Beitrag :-) https://paypal.me/Apollon77 / https://github.com/sponsors/Apollon77

                  • Debug-Log für Instanz einschalten? Admin -> Instanzen -> Expertenmodus -> Instanz aufklappen - Loglevel ändern
                  • Logfiles auf Platte /opt/iobroker/log/… nutzen, Admin schneidet Zeilen ab
                  StrathColeS 1 Antwort Letzte Antwort
                  0
                  • apollon77A apollon77

                    @strathcole Dduuuuuu ... weil ich grad mit nem anderen user dran bin: Wie hast Du denn die PIN eingegeben? Mit oder Ohne Bindestriche? Falls ohne Bindestriche ... mach mal mit XXX-XX-XXX?

                    UUUUNDDDD: Bring mal das Schloss in den Pairing Modus bevor du es versuchst!!! Der andere User hatte den Fehler mit "No salt " auch als das gerät NICHT im Pairing Modus war. Falls du als nächstes nen fehler bekommst das er die PairingMethod nicht ermitteln kann -> GitHub version versuchen

                    StrathColeS Offline
                    StrathColeS Offline
                    StrathCole
                    schrieb am zuletzt editiert von
                    #113

                    @apollon77 Danke fürs weiter Untersuchen.

                    Die PIN-Varianten habe ich alle durch. XXXXXXXX, XXXX-XXXX und XXX-XX-XXX

                    Allerdings kommt jetzt mit der Github-Variante eine ganz neue Meldung:
                    Response to Command pairDevice: {"success":false,"error":"Cannot pair with device BLE-XX:XX:XX:XX:XX because of error undefined (undefined): pair-setup characteristic not found"}

                    SolarWatt-Anlage mit 9,6 kWp – KOSTAL Plenticore Plus 10 – BYD B-Box HV 8,96 – Viessmann Vitocal 333g – Zehnder ComfoD 350 (Comfoair 350) mit RS232-Ethernet-Konverter

                    apollon77A 2 Antworten Letzte Antwort
                    0
                    • StrathColeS StrathCole

                      @apollon77 Danke fürs weiter Untersuchen.

                      Die PIN-Varianten habe ich alle durch. XXXXXXXX, XXXX-XXXX und XXX-XX-XXX

                      Allerdings kommt jetzt mit der Github-Variante eine ganz neue Meldung:
                      Response to Command pairDevice: {"success":false,"error":"Cannot pair with device BLE-XX:XX:XX:XX:XX because of error undefined (undefined): pair-setup characteristic not found"}

                      apollon77A Offline
                      apollon77A Offline
                      apollon77
                      schrieb am zuletzt editiert von
                      #114

                      @strathcole mit oder ohne das Gerät im
                      Pair Modus zu haben? Also mach mal so wie vorher auch.

                      Beitrag hat geholfen? Votet rechts unten im Beitrag :-) https://paypal.me/Apollon77 / https://github.com/sponsors/Apollon77

                      • Debug-Log für Instanz einschalten? Admin -> Instanzen -> Expertenmodus -> Instanz aufklappen - Loglevel ändern
                      • Logfiles auf Platte /opt/iobroker/log/… nutzen, Admin schneidet Zeilen ab
                      StrathColeS 1 Antwort Letzte Antwort
                      0
                      • StrathColeS StrathCole

                        @apollon77 Danke fürs weiter Untersuchen.

                        Die PIN-Varianten habe ich alle durch. XXXXXXXX, XXXX-XXXX und XXX-XX-XXX

                        Allerdings kommt jetzt mit der Github-Variante eine ganz neue Meldung:
                        Response to Command pairDevice: {"success":false,"error":"Cannot pair with device BLE-XX:XX:XX:XX:XX because of error undefined (undefined): pair-setup characteristic not found"}

                        apollon77A Offline
                        apollon77A Offline
                        apollon77
                        schrieb am zuletzt editiert von
                        #115

                        @strathcole ANsonsten nochmal neu GitHub bitte :-) (Manuell adapter nach Update neu starten)

                        Beitrag hat geholfen? Votet rechts unten im Beitrag :-) https://paypal.me/Apollon77 / https://github.com/sponsors/Apollon77

                        • Debug-Log für Instanz einschalten? Admin -> Instanzen -> Expertenmodus -> Instanz aufklappen - Loglevel ändern
                        • Logfiles auf Platte /opt/iobroker/log/… nutzen, Admin schneidet Zeilen ab
                        StrathColeS 1 Antwort Letzte Antwort
                        0
                        • apollon77A apollon77

                          @strathcole mit oder ohne das Gerät im
                          Pair Modus zu haben? Also mach mal so wie vorher auch.

                          StrathColeS Offline
                          StrathColeS Offline
                          StrathCole
                          schrieb am zuletzt editiert von StrathCole
                          #116

                          @apollon77 sagte in Test Alpha Homekit-Controller 0.0.x:

                          @strathcole mit oder ohne das Gerät im
                          Pair Modus zu haben? Also mach mal so wie vorher auch.

                          Habe beides versucht. Mit und ohne pair modus. Selbes Ergebnis (siehe unten).

                          @apollon77 sagte in Test Alpha Homekit-Controller 0.0.x:

                          @strathcole ANsonsten nochmal neu GitHub bitte :-) (Manuell adapter nach Update neu starten)

                          Leider weiterhin Cannot pair with device BLE-XXX because of error undefined (undefined): pair-setup characteristic not found.
                          Beim zweiten Versuch ohne Pairing-Modus kam dann wieder "Salt not found" und beim dritten Versuch (mit Pairing-Modus) dann nur noch: Response to Command pairDevice: {"success":false,"error":"Cannot pair with device BLE-XXX because of error undefined (undefined): undefined"}. Wenn dieser Fehler kommt (also undefined), dauert es aber auch ziemlich lange, so als würde er dann in einen Timeout rennen. Zwischen Start Homekit Device Client initialization und dem Fehler liegen fast genau 20 Sekunden jedes Mal. Wärend beim "Missing Salt" der Fehler schon nach 2 Sekunden kommt.

                          SolarWatt-Anlage mit 9,6 kWp – KOSTAL Plenticore Plus 10 – BYD B-Box HV 8,96 – Viessmann Vitocal 333g – Zehnder ComfoD 350 (Comfoair 350) mit RS232-Ethernet-Konverter

                          1 Antwort Letzte Antwort
                          0
                          • apollon77A apollon77

                            @strathcole ANsonsten nochmal neu GitHub bitte :-) (Manuell adapter nach Update neu starten)

                            StrathColeS Offline
                            StrathColeS Offline
                            StrathCole
                            schrieb am zuletzt editiert von StrathCole
                            #117

                            @apollon77 Nachtrag dazu: Die 20 Sekunden scheinen der Zeitraum zu sein, nach dem dann das Nuki den Pairing-Modus wieder abschaltet. Dann gehen die LED wieder aus und gleichzeitig kommt dann die Fehlermeldung. Und ohne den Modus kommt wie gesagt immer das mit Missing Salt.

                            Es scheinen 30 Sekunden zu sein, nicht 20. Denke mal, der Unterschied sind die Sekunden, die ich brauche vom Pairing-Modus an bis Pin-Eingabe.
                            hap-controller:gatt-connection Peripheral disconnected +30s

                            Log von Pair-Modus aktivieren über PIN-Eingabe bis Fehlermeldung habe ich gemailt.

                            SolarWatt-Anlage mit 9,6 kWp – KOSTAL Plenticore Plus 10 – BYD B-Box HV 8,96 – Viessmann Vitocal 333g – Zehnder ComfoD 350 (Comfoair 350) mit RS232-Ethernet-Konverter

                            1 Antwort Letzte Antwort
                            0
                            • apollon77A Offline
                              apollon77A Offline
                              apollon77
                              schrieb am zuletzt editiert von
                              #118

                              Ja soweit war ich mit dem anderen user auch. Es scheint so als ob der "Pairing Modus" eher dafür ist das Nuki mit seiner Bridge zu Pairen und gar nicht für HomeKit :-) Scheinbar ist Homekit Pairing in dem Zeitraum aus - was den oben genannten Fehler erklärt.

                              Es ist auch so - zumindestens im test - das sich das Nuki auch gar nicht mit Apple Home direkt Pairen lässt, sondern das ganze nur über die Nuki App geht, wo es dann danach in Apple Home ist - also die Nuki App pusht das Gerät zu Apple Home .... Das könnte es erklären warum es mit dem Adapter nicht geht. Da wären wir dann aber soweit raus :-(

                              Beitrag hat geholfen? Votet rechts unten im Beitrag :-) https://paypal.me/Apollon77 / https://github.com/sponsors/Apollon77

                              • Debug-Log für Instanz einschalten? Admin -> Instanzen -> Expertenmodus -> Instanz aufklappen - Loglevel ändern
                              • Logfiles auf Platte /opt/iobroker/log/… nutzen, Admin schneidet Zeilen ab
                              StrathColeS 2 Antworten Letzte Antwort
                              0
                              • apollon77A apollon77

                                Ja soweit war ich mit dem anderen user auch. Es scheint so als ob der "Pairing Modus" eher dafür ist das Nuki mit seiner Bridge zu Pairen und gar nicht für HomeKit :-) Scheinbar ist Homekit Pairing in dem Zeitraum aus - was den oben genannten Fehler erklärt.

                                Es ist auch so - zumindestens im test - das sich das Nuki auch gar nicht mit Apple Home direkt Pairen lässt, sondern das ganze nur über die Nuki App geht, wo es dann danach in Apple Home ist - also die Nuki App pusht das Gerät zu Apple Home .... Das könnte es erklären warum es mit dem Adapter nicht geht. Da wären wir dann aber soweit raus :-(

                                StrathColeS Offline
                                StrathColeS Offline
                                StrathCole
                                schrieb am zuletzt editiert von
                                #119

                                @apollon77 also in der Nuki Anleitung steht nur, dass man in der Home App den QR scannen soll und das dann angeblich geht. Aber wie gesagt, steht mir leider kein iOS Gerät zur Verfügung. Nutzen alle Android.

                                SolarWatt-Anlage mit 9,6 kWp – KOSTAL Plenticore Plus 10 – BYD B-Box HV 8,96 – Viessmann Vitocal 333g – Zehnder ComfoD 350 (Comfoair 350) mit RS232-Ethernet-Konverter

                                apollon77A 1 Antwort Letzte Antwort
                                0
                                • apollon77A apollon77

                                  Ja soweit war ich mit dem anderen user auch. Es scheint so als ob der "Pairing Modus" eher dafür ist das Nuki mit seiner Bridge zu Pairen und gar nicht für HomeKit :-) Scheinbar ist Homekit Pairing in dem Zeitraum aus - was den oben genannten Fehler erklärt.

                                  Es ist auch so - zumindestens im test - das sich das Nuki auch gar nicht mit Apple Home direkt Pairen lässt, sondern das ganze nur über die Nuki App geht, wo es dann danach in Apple Home ist - also die Nuki App pusht das Gerät zu Apple Home .... Das könnte es erklären warum es mit dem Adapter nicht geht. Da wären wir dann aber soweit raus :-(

                                  StrathColeS Offline
                                  StrathColeS Offline
                                  StrathCole
                                  schrieb am zuletzt editiert von
                                  #120

                                  @apollon77 ach ja, ich habe übrigens ein Nuki 3.0 pro. Nur falls das relevant ist.

                                  SolarWatt-Anlage mit 9,6 kWp – KOSTAL Plenticore Plus 10 – BYD B-Box HV 8,96 – Viessmann Vitocal 333g – Zehnder ComfoD 350 (Comfoair 350) mit RS232-Ethernet-Konverter

                                  1 Antwort Letzte Antwort
                                  0
                                  • StrathColeS StrathCole

                                    @apollon77 also in der Nuki Anleitung steht nur, dass man in der Home App den QR scannen soll und das dann angeblich geht. Aber wie gesagt, steht mir leider kein iOS Gerät zur Verfügung. Nutzen alle Android.

                                    apollon77A Offline
                                    apollon77A Offline
                                    apollon77
                                    schrieb am zuletzt editiert von
                                    #121

                                    @strathcole sagte in Test Alpha Homekit-Controller 0.0.x:

                                    also in der Nuki Anleitung steht nur, dass man in der Home App den QR scannen soll und das dann angeblich geht.

                                    Naja der andere user hat es so halt auch nicht hinbekommen sondern nur über die Nuki App

                                    Beitrag hat geholfen? Votet rechts unten im Beitrag :-) https://paypal.me/Apollon77 / https://github.com/sponsors/Apollon77

                                    • Debug-Log für Instanz einschalten? Admin -> Instanzen -> Expertenmodus -> Instanz aufklappen - Loglevel ändern
                                    • Logfiles auf Platte /opt/iobroker/log/… nutzen, Admin schneidet Zeilen ab
                                    StrathColeS 1 Antwort Letzte Antwort
                                    0
                                    • apollon77A apollon77

                                      @strathcole sagte in Test Alpha Homekit-Controller 0.0.x:

                                      also in der Nuki Anleitung steht nur, dass man in der Home App den QR scannen soll und das dann angeblich geht.

                                      Naja der andere user hat es so halt auch nicht hinbekommen sondern nur über die Nuki App

                                      StrathColeS Offline
                                      StrathColeS Offline
                                      StrathCole
                                      schrieb am zuletzt editiert von
                                      #122

                                      @apollon77 Na gut, dann … warte ich einfach mal, bis mir irgendwann irgendwer unterkommt, der hier mit einem iPhone reinschneit :laughing:

                                      SolarWatt-Anlage mit 9,6 kWp – KOSTAL Plenticore Plus 10 – BYD B-Box HV 8,96 – Viessmann Vitocal 333g – Zehnder ComfoD 350 (Comfoair 350) mit RS232-Ethernet-Konverter

                                      apollon77A 1 Antwort Letzte Antwort
                                      0
                                      • StrathColeS StrathCole

                                        @apollon77 Na gut, dann … warte ich einfach mal, bis mir irgendwann irgendwer unterkommt, der hier mit einem iPhone reinschneit :laughing:

                                        apollon77A Offline
                                        apollon77A Offline
                                        apollon77
                                        schrieb am zuletzt editiert von
                                        #123

                                        @strathcole Naja das it der andere User, aber kommen auch nicht so wirklich weiter bis auf die Details die ich oben schon gesagt hab

                                        Beitrag hat geholfen? Votet rechts unten im Beitrag :-) https://paypal.me/Apollon77 / https://github.com/sponsors/Apollon77

                                        • Debug-Log für Instanz einschalten? Admin -> Instanzen -> Expertenmodus -> Instanz aufklappen - Loglevel ändern
                                        • Logfiles auf Platte /opt/iobroker/log/… nutzen, Admin schneidet Zeilen ab
                                        1 Antwort Letzte Antwort
                                        0
                                        • M Offline
                                          M Offline
                                          Minta79
                                          schrieb am zuletzt editiert von
                                          #124

                                          Ich nutze seit gestern den Adapter in Version 0.3.3. Leider steht die Instanz nach kurzer Zeit immer auf "Nicht Verbunden mit Gerät oder Dienst". Ich habe einen Onvis-Türkontakt per Bluetooth verbunden. Hat jemand einen Tipp für mich, was das Problem sein könnte?

                                          apollon77A 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

                                          692

                                          Online

                                          32.4k

                                          Benutzer

                                          81.5k

                                          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