NEWS
Test Alpha Homekit-Controller 0.0.x
-
@apollon77
Hmm, bin jetzt nicht sicher, was Du meinst. Mein ioBroker läuft auf einem Raspberry Pi und hat keinen Stick oder so.
Er steht im Dachgeschoss, der Weather hängt außen vor der Küche und ist verbunden mit einem HomePod mini im Wohnzimmer. Da ich im Haus 9 HomePod minis verteilt habe, sollte das Thread-Netzwerk im ganzen Haus verfügbar sein und die HomePod minis sind ja ebenfalls per Wifi verbunden. So dachte ich, daß das alles auch irgendwie in den ioBroker zu bringen sei? -
@invidianer ok dann mal langsam. Der Adapter kann maximal über BLE mit dem Gerät direkt reden - wenn es nicht schon gepaired ist. Das sollte Ggf zu weit weg sein.
Wenn der adapter thread könnte gäbs ne Auswahl und du bräuchtest Hardware dafür. Weiterhin HomeKit via Thread ist noch nicht offengelegt … also bitte genau lesen was der Adapter kann und möglich ist. -
@apollon77
Ok, danke! -
Hallo zusammen,
danke @apollon77 für die Mühe der Enticklung des Adapters.
Sofern der Adapter das erfüllt, was ich mir gerade vorstelle, wäre das für mich ein riesen Pluspunkt den ich schon lange vermisse.Ich besitze ein Nuki Smartlock. Ich möchte dieses eigentlich lokal, ohne Bridge nutzen. Denn die Bridge möchte zwangsläufig ins Internet.
Nun habe in der Nuki App Homekit und Bluetooth aktiviert. Weiterhin habe ich der virtuellen Maschine auf der ioBroker läuft ein Bluetooth Dongle zugewiesen. Leider findet der Adapter keine Geräte. Wüsstest du wie wir uns dem annähern könnten?Grüße!
homekit-controller.0 2021-11-15 13:01:45.876 debug state homekit-controller.0.info.connection changed: false (ack = true) homekit-controller.0 2021-11-15 13:01:45.654 info starting. Version 0.3.3 in /opt/iobroker/node_modules/iobroker.homekit-controller, node: v12.22.4, js-controller: 3.3.18 homekit-controller.0 2021-11-15 13:01:45.600 info Plugin sentry Sentry Plugin disabled for this process because sending of statistic data is disabled for the system homekit-controller.0 2021-11-15 13:01:45.596 debug Plugin sentry Initialize Plugin (enabled=true) homekit-controller.0 2021-11-15 13:01:44.798 debug Objects client initialize lua scripts homekit-controller.0 2021-11-15 13:01:44.796 debug Objects create User PubSub Client homekit-controller.0 2021-11-15 13:01:44.794 debug Objects create System PubSub Client homekit-controller.0 2021-11-15 13:01:44.792 debug Objects client ready ... initialize now homekit-controller.0 2021-11-15 13:01:44.759 debug Redis Objects: Use Redis connection: 127.0.0.1:9001 homekit-controller.0 2021-11-15 13:01:14.455 info Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason homekit-controller.0 2021-11-15 13:01:14.454 info terminating homekit-controller.0 2021-11-15 13:01:14.448 info Got terminate signal TERMINATE_YOURSELF
-
@hc-yami Der Haken bei Bluetooth in der Konfig ist gesetzt? Ansonsten ist das Debug Log viel zu kurz ... Entweder da fehlt nahezu alles oder was anderes ist komisch bei Dir
-
Hallo,
habe versucht eine meross MSL120 E27 Lampe zu verbinden. Zuerst mit der meross App die Lampe ins WLAN gebracht und funktioniert dann auch mit der App. Im Homekit Adapter findet er sie aber nicht. Gibts hier noch etwas zu beachten? Firmwareupdate für die Lampe hab ich auch schon durchgeführt.
-
@ritter wenn du sie registrierst dann ist sie danach in der meross App und in deinem
Apple Home drin und gepaired. Geh auf dein Apple Home App (nicht in die meross App!!) und entferne das Gerät dort. Danach sollte sie aufzufinden sein. Siehe auch Adapter readme -
@apollon77 Ich habe sie nur in der meross App gekoppelt. Ich habe keine Apple Geräte und sie damit auch nicht in Apple Home drin. Ist das vorher notwendig sie mit Apple Home zu koppeln? Dachte ich muss sie nur mit der App ins WLAN bringen. Sonst bräuchte ich ja einen Apple Home Emulator den es wahrscheinlich nicht gibt.
-
@ritter Hi,
ok, wenn Du sicher bist das es nicht gekoppelt ist und das das Gerät Apple Home unterstützt und dein iobroker Rechner im gleichen netzsegment wie die WLAN Lampe ist und so UDP Pakete geroutet werden dann kannst Du den Adapter mal im Debug Log starten. Dann solltest DU sehen falls Sie erkannt und verworfen wird oder sowas
-
Laut Lampen Karton wird es unterstützt. Es sind auch bei beiden Lampen diese Pins mit QR Code drauf und die Meross APP zeigt auch diesen PIN an.
Windows Rechner wo iobroker inst. ist hat IP: 192.168.1.31 SUB: 255.255.255.252.0
Die Lampe: 192.168.3.142homekit-controller.0 2021-12-05 15:37:30.175 debug state homekit-controller.0.info.connection changed: false (ack = true) homekit-controller.0 2021-12-05 15:37:30.109 info starting. Version 0.3.3 in C:/iobroker/node_modules/iobroker.homekit-controller, node: v14.15.4, js-controller: 3.3.21 homekit-controller.0 2021-12-05 15:37:29.005 debug Plugin sentry Initialize Plugin (enabled=true) homekit-controller.0 2021-12-05 15:37:28.786 debug statesDB connected homekit-controller.0 2021-12-05 15:37:28.786 debug States connected to redis: 0.0.0.0:9000 homekit-controller.0 2021-12-05 15:37:28.760 debug States create User PubSub Client homekit-controller.0 2021-12-05 15:37:28.760 debug States create System PubSub Client homekit-controller.0 2021-12-05 15:37:28.743 debug Redis States: Use Redis connection: 0.0.0.0:9000 homekit-controller.0 2021-12-05 15:37:28.741 debug objectDB connected homekit-controller.0 2021-12-05 15:37:28.734 debug Objects connected to redis: 0.0.0.0:9001 homekit-controller.0 2021-12-05 15:37:28.705 debug Objects client initialize lua scripts homekit-controller.0 2021-12-05 15:37:28.704 debug Objects create User PubSub Client homekit-controller.0 2021-12-05 15:37:28.703 debug Objects create System PubSub Client homekit-controller.0 2021-12-05 15:37:28.702 debug Objects client ready ... initialize now homekit-controller.0 2021-12-05 15:37:28.655 debug Redis Objects: Use Redis connection: 0.0.0.0:9001 homekit-controller.0 2021-12-05 15:37:24.397 info Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason homekit-controller.0 2021-12-05 15:37:24.397 debug Plugin sentry destroyed homekit-controller.0 2021-12-05 15:37:24.396 info terminating homekit-controller.0 2021-12-05 15:37:24.394 info Got terminate signal TERMINATE_YOURSELF homekit-controller.0 2021-12-05 15:36:22.991 debug sendTo "getDiscoveredDevices" to system.adapter.admin.0 from system.adapter.homekit-controller.0 homekit-controller.0 2021-12-05 15:36:22.990 debug Response to Command getDiscoveredDevices: {"success":true,"error":false} homekit-controller.0 2021-12-05 15:36:22.990 debug Message getDiscoveredDevices received: {"command":"getDiscoveredDevices","message":null,"from":"system.adapter.admin.0","callback":{"message":null,"id":302,"ack":false,"time":1638714982989},"_id":95084731}) homekit-controller.0 2021-12-05 15:36:21.524 debug sendTo "getDiscoveredDevices" to system.adapter.admin.0 from system.adapter.homekit-controller.0 homekit-controller.0 2021-12-05 15:36:21.524 debug Response to Command getDiscoveredDevices: {"success":true,"error":false} homekit-controller.0 2021-12-05 15:36:21.520 debug Message getDiscoveredDevices received: {"command":"getDiscoveredDevices","message":null,"from":"system.adapter.admin.0","callback":{"message":null,"id":301,"ack":false,"time":1638714981508},"_id":95084730})
-
@ritter Naja 192.168.1 vs 192.168.3 sind zwei Netzsegmente ... Ich kenne jetzt Deine Routerkonfiguration nicht oder du musst sicherstellen das UDP Pakete geroutet werden oder einen ioBroker Slave in das andere Netzsegment stellen.
Ohne UDP Pakete gibt es generell kein Apple HomeKit (auch nicht mit Apple App - es sei denn das Handy wäre dann auch in dem netz wie die Lampe).
-
@apollon77 Aber ist es mit der Netzmaske: 255.255.255.252.0 nicht ein Segment? Alle anderen Geräte finden sich untereinander wie das mit UDP ist weis ich nicht, braucht man das nicht auch für VOIP das geht jedenfalls.
-
Hab der Lampe über die FritzBox jetzt diese Adresse zugewiesen: 192.168.1.142 aber keine Änderung.
-
@ritter sagte in Test Alpha Homekit-Controller 0.0.x:
Hab der Lampe über die FritzBox jetzt diese Adresse zugewiesen: 192.168.1.142 aber keine Änderung.
Hab jetzt noch ein Firmwareupdate für den 24 Port Switch gemacht und nun findet er die Lampe und kann gesteuert werden.
-
@ritter Na Cool, also war da doch irgendwas mit UDP Routing
-
Ja, vielleicht aber nur Zufall denn die zweite Lampe findet er nicht.
-
@ritter Vllt auch ins gleiche Netzsegment bringen?
-
Auch schon probiert. Zumindest weis ich jetzt das die Lampen es generell können.
-
@ritter Generell versuch doch mal ob Du sie per iOS Handy an Apple Home anlernen kannst ... wenn das geht lern Sie wieder ab und versuch nochmal
-
@apollon77
Hallo,
kann man die Eve Geräte nur über einen Extend koppeln, oder geht das auch direkt über Bluetooth?
Über bluetooth sehe ich die Geräte im Adapter kann sie identifizieren aber nicht erfolgreich pairen,
über den Extend funktierte es einwandfrei.2021-12-11 11:09:50.667 - debug: homekit-controller.0 (55192) BLE-F5:A0:3F:34:7E:71 Discovered BLE device: {"name":"Eve Degree 053B","CoID":76,"TY":6,"AIL":49,"SF":1,"DeviceID":"f5:a0:3f:34:7e:71","ACID":10,"GSN":1,"CN":3,"CV":2,"c#":3,"id":"f5:a0:3f:34:7e:71","ci":10,"availableToPair":true} 2021-12-11 11:09:50.669 - debug: homekit-controller.0 (55192) Service: {"name":"Eve Degree 053B","CoID":76,"TY":6,"AIL":49,"SF":1,"DeviceID":"f5:a0:3f:34:7e:71","ACID":10,"GSN":1,"CN":3,"CV":2,"c#":3,"id":"f5:a0:3f:34:7e:71","ci":10,"availableToPair":true} 2021-12-11 11:09:51.163 - debug: homekit-controller.0 (55192) state homekit-controller.0.BLE-F5:A0:3F:34:7E:71.info.connectionType changed: BLE (ack = true) 2021-12-11 11:09:51.181 - debug: homekit-controller.0 (55192) state homekit-controller.0.BLE-F5:A0:3F:34:7E:71.info.id changed: f5:a0:3f:34:7e:71 (ack = true) 2021-12-11 11:09:51.195 - debug: homekit-controller.0 (55192) state homekit-controller.0.BLE-F5:A0:3F:34:7E:71.info.connected changed: false (ack = true) 2021-12-11 11:09:51.215 - debug: homekit-controller.0 (55192) state homekit-controller.0.BLE-F5:A0:3F:34:7E:71.admin.isPaired changed: false (ack = true) 2021-12-11 11:09:51.232 - debug: homekit-controller.0 (55192) state homekit-controller.0.BLE-F5:A0:3F:34:7E:71.info.lastDiscovered changed: 1639217390670 (ack = true) 2021-12-11 11:11:54.863 - debug: homekit-controller.0 (55192) Discovered BLE device changed: 91:09:30:d3:27:4b/Eve Room 632D 2021-12-11 11:11:54.864 - debug: homekit-controller.0 (55192) BLE-91:09:30:D3:27:4B Discovered BLE device: {"name":"Eve Room 632D","CoID":76,"TY":6,"AIL":49,"SF":1,"DeviceID":"91:09:30:d3:27:4b","ACID":10,"GSN":1,"CN":1,"CV":2,"c#":1,"id":"91:09:30:d3:27:4b","ci":10,"availableToPair":true} 2021-12-11 11:11:54.865 - debug: homekit-controller.0 (55192) Service: {"name":"Eve Room 632D","CoID":76,"TY":6,"AIL":49,"SF":1,"DeviceID":"91:09:30:d3:27:4b","ACID":10,"GSN":1,"CN":1,"CV":2,"c#":1,"id":"91:09:30:d3:27:4b","ci":10,"availableToPair":true} 2021-12-11 11:11:54.911 - debug: homekit-controller.0 (55192) state homekit-controller.0.BLE-91:09:30:D3:27:4B.info.connectionType changed: BLE (ack = true) 2021-12-11 11:11:54.921 - debug: homekit-controller.0 (55192) state homekit-controller.0.BLE-91:09:30:D3:27:4B.info.connectionType changed: BLE (ack = true) 2021-12-11 11:11:54.954 - debug: homekit-controller.0 (55192) state homekit-controller.0.BLE-91:09:30:D3:27:4B.info.id changed: 91:09:30:d3:27:4b (ack = true) 2021-12-11 11:11:55.000 - debug: homekit-controller.0 (55192) state homekit-controller.0.BLE-91:09:30:D3:27:4B.info.connected changed: false (ack = true) 2021-12-11 11:11:55.094 - debug: homekit-controller.0 (55192) state homekit-controller.0.BLE-91:09:30:D3:27:4B.admin.isPaired changed: false (ack = true) 2021-12-11 11:11:55.117 - debug: homekit-controller.0 (55192) state homekit-controller.0.BLE-91:09:30:D3:27:4B.info.lastDiscovered changed: 1639217514866 (ack = true) 2021-12-11 11:11:55.133 - debug: homekit-controller.0 (55192) state homekit-controller.0.BLE-91:09:30:D3:27:4B.admin.pairWithPin changed: (ack = true) 2021-12-11 11:11:55.149 - debug: homekit-controller.0 (55192) state homekit-controller.0.BLE-91:09:30:D3:27:4B.admin.identify changed: false (ack = true) 2021-12-11 11:12:23.945 - debug: homekit-controller.0 (55192) Message getDiscoveredDevices received: {"command":"getDiscoveredDevices","message":null,"from":"system.adapter.admin.0","callback":{"message":null,"id":18,"ack":false,"time":1639217543942},"_id":54081580}) 2021-12-11 11:12:23.946 - debug: homekit-controller.0 (55192) Response to Command getDiscoveredDevices: {"success":true,"error":false,"devices":[{"id":"BLE-91:09:30:D3:27:4B","serviceType":"BLE","connected":false,"discovered":true,"availableToPair":true,"discoveredName":"Eve Room 632D","discoveredCategory":"Sensor","pairedWithThisInstance":false},{"id":"BLE-F5:A0:3F:34:7E:71","serviceType":"BLE","connected":false,"discovered":true,"availableToPair":true,"discoveredName":"Eve Degree 053B","discoveredCategory":"Sensor","pairedWithThisInstance":false},{"id":"IP-AB:34:18:95:31:5D","serviceType":"IP","connected":false,"discovered":true,"availableToPair":false,"discoveredName":"IOBroker 83D1","discoveredCategory":"Bridge","pairedWithThisInstance":false},{"id":"IP-0E:6C:79:7B:0B:81","serviceType":"IP","connected":false,"discovered":true,"availableToPair":false,"discoveredName":"Homebridge 4B75","discoveredCategory":"Bridge","pairedWithThisInstance":false},{"id":"IP-58:47:6A:51:5B:FE","serviceType":"IP","connected":false,"discovered":true,"availableToPair":false,"discoveredName":"IN-8003FHD-PoE(c7)","discoveredCategory":"IP Camera","pairedWithThisInstance":false},{"id":"BLE-D9:13:F4:11:E9:11","serviceType":"BLE","connected":false,"discovered":true,"availableToPair":false,"discoveredName":"Eve Degree 053B","discoveredCategory":"Sensor","pairedWithThisInstance":false}]} 2021-12-11 11:12:23.948 - debug: homekit-controller.0 (55192) sendTo "getDiscoveredDevices" to system.adapter.admin.0 from system.adapter.homekit-controller.0 2021-12-11 11:12:30.870 - debug: homekit-controller.0 (55192) Message identify received: {"command":"identify","message":{"deviceId":"BLE-91:09:30:D3:27:4B"},"from":"system.adapter.admin.0","callback":{"message":{"deviceId":"BLE-91:09:30:D3:27:4B"},"id":19,"ack":false,"time":1639217550868},"_id":54081581}) 2021-12-11 11:12:30.871 - debug: homekit-controller.0 (55192) Device BLE-91:09:30:D3:27:4B: Identify triggered 2021-12-11 11:12:33.562 - debug: homekit-controller.0 (55192) Response to Command identify: {"success":true,"error":false} 2021-12-11 11:12:33.564 - debug: homekit-controller.0 (55192) sendTo "identify" to system.adapter.admin.0 from system.adapter.homekit-controller.0 2021-12-11 11:12:35.072 - debug: homekit-controller.0 (55192) Message getDiscoveredDevices received: {"command":"getDiscoveredDevices","message":null,"from":"system.adapter.admin.0","callback":{"message":null,"id":20,"ack":false,"time":1639217555070},"_id":54081582}) 2021-12-11 11:12:35.073 - debug: homekit-controller.0 (55192) Response to Command getDiscoveredDevices: {"success":true,"error":false,"devices":[{"id":"BLE-91:09:30:D3:27:4B","serviceType":"BLE","connected":false,"discovered":true,"availableToPair":true,"discoveredName":"Eve Room 632D","discoveredCategory":"Sensor","pairedWithThisInstance":false},{"id":"BLE-F5:A0:3F:34:7E:71","serviceType":"BLE","connected":false,"discovered":true,"availableToPair":true,"discoveredName":"Eve Degree 053B","discoveredCategory":"Sensor","pairedWithThisInstance":false},{"id":"IP-AB:34:18:95:31:5D","serviceType":"IP","connected":false,"discovered":true,"availableToPair":false,"discoveredName":"IOBroker 83D1","discoveredCategory":"Bridge","pairedWithThisInstance":false},{"id":"IP-0E:6C:79:7B:0B:81","serviceType":"IP","connected":false,"discovered":true,"availableToPair":false,"discoveredName":"Homebridge 4B75","discoveredCategory":"Bridge","pairedWithThisInstance":false},{"id":"IP-58:47:6A:51:5B:FE","serviceType":"IP","connected":false,"discovered":true,"availableToPair":false,"discoveredName":"IN-8003FHD-PoE(c7)","discoveredCategory":"IP Camera","pairedWithThisInstance":false},{"id":"BLE-D9:13:F4:11:E9:11","serviceType":"BLE","connected":false,"discovered":true,"availableToPair":false,"discoveredName":"Eve Degree 053B","discoveredCategory":"Sensor","pairedWithThisInstance":false}]} 2021-12-11 11:12:35.073 - debug: homekit-controller.0 (55192) sendTo "getDiscoveredDevices" to system.adapter.admin.0 from system.adapter.homekit-controller.0 2021-12-11 11:12:40.256 - debug: homekit-controller.0 (55192) Message identify received: {"command":"identify","message":{"deviceId":"BLE-F5:A0:3F:34:7E:71"},"from":"system.adapter.admin.0","callback":{"message":{"deviceId":"BLE-F5:A0:3F:34:7E:71"},"id":21,"ack":false,"time":1639217560254},"_id":54081583}) 2021-12-11 11:12:40.256 - debug: homekit-controller.0 (55192) Device BLE-F5:A0:3F:34:7E:71: Identify triggered 2021-12-11 11:12:42.661 - debug: homekit-controller.0 (55192) Response to Command identify: {"success":true,"error":false} 2021-12-11 11:12:42.661 - debug: homekit-controller.0 (55192) sendTo "identify" to system.adapter.admin.0 from system.adapter.homekit-controller.0 2021-12-11 11:12:44.179 - debug: homekit-controller.0 (55192) Message getDiscoveredDevices received: {"command":"getDiscoveredDevices","message":null,"from":"system.adapter.admin.0","callback":{"message":null,"id":22,"ack":false,"time":1639217564177},"_id":54081584}) 2021-12-11 11:12:44.179 - debug: homekit-controller.0 (55192) Response to Command getDiscoveredDevices: {"success":true,"error":false,"devices":[{"id":"BLE-91:09:30:D3:27:4B","serviceType":"BLE","connected":false,"discovered":true,"availableToPair":true,"discoveredName":"Eve Room 632D","discoveredCategory":"Sensor","pairedWithThisInstance":false},{"id":"BLE-F5:A0:3F:34:7E:71","serviceType":"BLE","connected":false,"discovered":true,"availableToPair":true,"discoveredName":"Eve Degree 053B","discoveredCategory":"Sensor","pairedWithThisInstance":false},{"id":"IP-AB:34:18:95:31:5D","serviceType":"IP","connected":false,"discovered":true,"availableToPair":false,"discoveredName":"IOBroker 83D1","discoveredCategory":"Bridge","pairedWithThisInstance":false},{"id":"IP-0E:6C:79:7B:0B:81","serviceType":"IP","connected":false,"discovered":true,"availableToPair":false,"discoveredName":"Homebridge 4B75","discoveredCategory":"Bridge","pairedWithThisInstance":false},{"id":"IP-58:47:6A:51:5B:FE","serviceType":"IP","connected":false,"discovered":true,"availableToPair":false,"discoveredName":"IN-8003FHD-PoE(c7)","discoveredCategory":"IP Camera","pairedWithThisInstance":false},{"id":"BLE-D9:13:F4:11:E9:11","serviceType":"BLE","connected":false,"discovered":true,"availableToPair":false,"discoveredName":"Eve Degree 053B","discoveredCategory":"Sensor","pairedWithThisInstance":false}]} 2021-12-11 11:12:44.180 - debug: homekit-controller.0 (55192) sendTo "getDiscoveredDevices" to system.adapter.admin.0 from system.adapter.homekit-controller.0 2021-12-11 11:13:06.470 - debug: homekit-controller.0 (55192) Message pairDevice received: {"command":"pairDevice","message":{"deviceId":"BLE-F5:A0:3F:34:7E:71","pin":"629-15-584"},"from":"system.adapter.admin.0","callback":{"message":{"deviceId":"BLE-F5:A0:3F:34:7E:71","pin":"629-15-584"},"id":23,"ack":false,"time":1639217586468},"_id":54081585}) 2021-12-11 11:13:09.388 - debug: homekit-controller.0 (55192) BLE-F5:A0:3F:34:7E:71 Start Homekit Device Client initialization 2021-12-11 11:13:17.555 - debug: homekit-controller.0 (55192) BLE-F5:A0:3F:34:7E:71 Start Homekit Device Client initialization 2021-12-11 11:13:17.557 - debug: homekit-controller.0 (55192) Service: {"name":"Eve Degree 053B","CoID":76,"TY":6,"AIL":49,"SF":1,"DeviceID":"f5:a0:3f:34:7e:71","ACID":10,"GSN":1,"CN":3,"CV":2,"c#":3,"id":"f5:a0:3f:34:7e:71","ci":10,"availableToPair":false} 2021-12-11 11:13:17.574 - debug: homekit-controller.0 (55192) state homekit-controller.0.BLE-F5:A0:3F:34:7E:71.admin.pairWithPin deleted 2021-12-11 11:13:17.602 - debug: homekit-controller.0 (55192) Discovered BLE device changed: f5:a0:3f:34:7e:71/Eve Degree 053B 2021-12-11 11:13:17.605 - debug: homekit-controller.0 (55192) BLE-F5:A0:3F:34:7E:71 Discovered BLE device: {"name":"Eve Degree 053B","CoID":76,"TY":6,"AIL":49,"SF":0,"DeviceID":"f5:a0:3f:34:7e:71","ACID":10,"GSN":1,"CN":3,"CV":2,"c#":3,"id":"f5:a0:3f:34:7e:71","ci":10,"availableToPair":false} 2021-12-11 11:13:17.606 - debug: homekit-controller.0 (55192) BLE-F5:A0:3F:34:7E:71 Device initialization already in progress ... ignore call 2021-12-11 11:13:17.612 - debug: homekit-controller.0 (55192) Discovered BLE device changed: f5:a0:3f:34:7e:71/Eve Degree 053B 2021-12-11 11:13:17.613 - debug: homekit-controller.0 (55192) BLE-F5:A0:3F:34:7E:71 Discovered BLE device: {"name":"Eve Degree 053B","CoID":76,"TY":6,"AIL":49,"SF":0,"DeviceID":"f5:a0:3f:34:7e:71","ACID":10,"GSN":2,"CN":3,"CV":2,"c#":3,"id":"f5:a0:3f:34:7e:71","ci":10,"availableToPair":false} 2021-12-11 11:13:17.613 - debug: homekit-controller.0 (55192) BLE-F5:A0:3F:34:7E:71 Device initialization already in progress ... ignore call 2021-12-11 11:13:17.622 - debug: homekit-controller.0 (55192) state homekit-controller.0.BLE-F5:A0:3F:34:7E:71.admin.identify deleted 2021-12-11 11:13:18.049 - debug: homekit-controller.0 (55192) Response to Command pairDevice: {"success":true,"error":false} 2021-12-11 11:13:18.049 - debug: homekit-controller.0 (55192) sendTo "pairDevice" to system.adapter.admin.0 from system.adapter.homekit-controller.0 2021-12-11 11:19:49.584 - debug: homekit-controller.0 (55192) Discovered BLE device changed: f5:a0:3f:34:7e:71/Eve Degree 053B 2021-12-11 11:19:49.584 - debug: homekit-controller.0 (55192) BLE-F5:A0:3F:34:7E:71 Discovered BLE device: {"name":"Eve Degree 053B","CoID":76,"TY":6,"AIL":49,"SF":0,"DeviceID":"f5:a0:3f:34:7e:71","ACID":10,"GSN":3,"CN":3,"CV":2,"c#":3,"id":"f5:a0:3f:34:7e:71","ci":10,"availableToPair":false} 2021-12-11 11:19:49.585 - debug: homekit-controller.0 (55192) BLE-F5:A0:3F:34:7E:71 Start Homekit Device Client initialization 2021-12-11 11:19:49.585 - debug: homekit-controller.0 (55192) Service: {"name":"Eve Degree 053B","CoID":76,"TY":6,"AIL":49,"SF":0,"DeviceID":"f5:a0:3f:34:7e:71","ACID":10,"GSN":3,"CN":3,"CV":2,"c#":3,"id":"f5:a0:3f:34:7e:71","ci":10,"availableToPair":false}