Test Alpha Homekit-Controller 0.0.x

Minta79

@apollon77 Ich wüsste nicht, in welchem Adapter es noch verwendet werden sollte. Der Zustand bleibt leider so. Stand jetzt über nen Tag in dem Zustand. Im Log wiederholt es sich dann...
Bildschirmfoto 2021-12-26 um 00.25.38.png

apollon77

@minta79 Hm, kann nur raten ... ist irgendwas auf dem Bluetooth level. Da müssmer jetzt mal ganz tief reingehen

Bitte sicherstellen das alles aktuell ist ... apt update && apt dist-upgrade
Bitte auch mal sudo hciconfig hci0 reset versuchen
Was sagt uname -a ? ALao welcher Kernel (ggf nach Updates und nach einem Reboot)
Was sagt lsusb?
Was für ein gert ist es? Raspi3 oder was?

Dann wäre cool wenn du in einer Shell mal sudo hcidump -t -x >log.txt laufen lassen kannst und dann den Adapter startest.... Dann das log.txt File mal hochladen zusammen mit dem iobroker debug log

EDIT: Den Adapter starten am besten wie hier --> https://forum.iobroker.net/post/720099 beschrieben in einem zweiten Shell Fenster ... dann die Shell Ausgaben

pql

Hi,

laut Readme unterstützt der Controller keine Thread Devices... Bezieht sich das auch auf Eve Geräte die mittlerweile als "based on Thread" betitelt sind? Oder sollen diese funktionieren?

apollon77

@pql eve ist meines Wissens thread UND Ble Bzw wlan. Ich kenne bisher kein „exklusiv thread“ gerät auf dem Markt. Von daher sollte es dennoch gehen. Musst halt schauen was das Gerät in Summe so kann

tklein

Hallo,

was kann ich tun, damit der Adapter grün wird? Der VP2 Steckerleiste habe ich inzwischen resetet. Wird mir jetzt nicht mehr angezeigt. Ferner find ich keinen DP, wo ich das Pairing triggern könnte.

Im Log steht dieses:

homekit-controller.0	2022-02-08 11:52:17.280	info	(7899) IP-7D:15:F7:88:80:A6 (iobroker 064B) found without known pairing data and already paired: ignoring
homekit-controller.0	2022-02-08 11:52:17.071	info	(7899) starting. Version 0.3.3 in /opt/iobroker/node_modules/iobroker.homekit-controller, node: v14.17.0, js-controller: 3.3.22

bzw:

pi@raspberrypi-iob:~ $ DEBUG=hap* node /opt/iobroker/node_modules/iobroker.homekit-controller/build/main.js 0 --debug --logs
2022-02-08 12:05:23.596  - debug: homekit-controller.0 (9559) Redis Objects: Use Redis connection: 127.0.0.1:9001
2022-02-08 12:05:23.677  - debug: homekit-controller.0 (9559) Objects client ready ... initialize now
2022-02-08 12:05:23.682  - debug: homekit-controller.0 (9559) Objects create System PubSub Client
2022-02-08 12:05:23.685  - debug: homekit-controller.0 (9559) Objects create User PubSub Client
2022-02-08 12:05:23.688  - debug: homekit-controller.0 (9559) Objects client initialize lua scripts
2022-02-08 12:05:24.690  - debug: homekit-controller.0 (9559) Objects connected to redis: 127.0.0.1:9001
2022-02-08 12:05:24.706  - debug: homekit-controller.0 (9559) objectDB connected
2022-02-08 12:05:24.710  - debug: homekit-controller.0 (9559) Redis States: Use Redis connection: 127.0.0.1:9000
2022-02-08 12:05:24.857  - debug: homekit-controller.0 (9559) States create System PubSub Client
2022-02-08 12:05:24.859  - debug: homekit-controller.0 (9559) States create User PubSub Client
2022-02-08 12:05:24.895  - debug: homekit-controller.0 (9559) States connected to redis: 127.0.0.1:9000
2022-02-08 12:05:24.896  - debug: homekit-controller.0 (9559) statesDB connected
2022-02-08 12:05:25.908  - debug: homekit-controller.0 (9559) Plugin sentry Initialize Plugin (enabled=true)
2022-02-08 12:05:26.405  - error: homekit-controller.0 (9559) adapter disabled
2022-02-08 12:05:26.412  - info: homekit-controller.0 (9559) starting. Version 0.3.3 in /opt/iobroker/node_modules/iobroker.homekit-controller, node: v14.17.0, js-controller: 3.3.22
2022-02-08 12:05:26.529  - debug: homekit-controller.0 (9559) state homekit-controller.0.info.connection changed: false (ack = true)
2022-02-08 12:05:26.567  - debug: homekit-controller.0 (9559) Discovered IP device up: 7d:15:f7:88:80:a6/iobroker 064B
2022-02-08 12:05:26.568  - debug: homekit-controller.0 (9559) IP-7D:15:F7:88:80:A6 Discovered IP device: {"name":"iobroker 064B","address":"192.168.0.20","port":43409,"c#":78,"ff":0,"id":"7d:15:f7:88:80:a6","md":"not configured","pv":"1.1","s#":1,"sf":0,"ci":2,"availableToPair":false}
2022-02-08 12:05:26.570  - info: homekit-controller.0 (9559) IP-7D:15:F7:88:80:A6 (iobroker 064B) found without known pairing data and already paired: ignoring
2022-02-08 12:05:31.690  - warn: homekit-controller.0 (9559) Got terminate signal. Checking desired PID: 0 vs own PID 9559
2022-02-08 12:05:31.753  - warn: homekit-controller.0 (9559) Got terminate signal. Checking desired PID: 9577 vs own PID 9559
2022-02-08 12:06:04.274  - warn: homekit-controller.0 (9559) Got terminate signal. Checking desired PID: 0 vs own PID 9559
2022-02-08 12:06:04.377  - warn: homekit-controller.0 (9559) Got terminate signal. Checking desired PID: 9633 vs own PID 9559
^C2022-02-08 12:06:14.527  - debug: homekit-controller.0 (9559) Plugin sentry destroyed
2022-02-08 12:06:14.529  - info: homekit-controller.0 (9559) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason

apollon77

@tklein Naja der Adapter wird grün wenn er mit mindestens einem Gerät verbunden ist - bei dir ist er mit keinem Gerät verbunden - ergo Gelb.

Wenn der Adapter sagt das das gerät bereits gepaired ist dann ist das erstmal so. Dann musst DU das Gerät resetten oder aus von da wo es gepaired ist wieder unpairen, Ein Gerät kann nur mit einem Controller gepaired sein.

tklein

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

Wenn der Adapter sagt das das gerät bereits gepaired ist dann ist das erstmal so. Dann musst DU das Gerät resetten oder aus von da wo es gepaired ist wieder unpairen, Ein Gerät kann nur mit einem Controller gepaired sein.

thx dafür. Das eine gepairte ist ja der iobroker als bridge selber. Die schaltbare Steckdosenleiste hatte ich ja resettet. Aber wo/wie kann ich den Pairingcode dann eingeben? Ich habe ja nicht den DP, mit dem ich das Triggern kann. So hatte ich das zumindest bei Github gelesen.

apollon77

@tklein wenn er ein Gerät als „ready to pair“ findet dann erscheint der state Bzw in der ui gibt es die Möglichkeit es zu pairen. Das debug log zeigt das dann auch so an … war bei dir oben aber nicht der Fall. Also sicher das reset geklappt hat?

tklein

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

Also sicher das reset geklappt hat?

jetzt sieht es zmindest etwas besser aus, Pairen geht aber immer nch nicht. Den Pin habe ich mit xxx-xx-xxx angegeben. Im DP und in der GUI-Popup

Nachtrag:

Jetzt konnte ich erfolgreich pairen. Keine Ahnung warum die Steckerleiste doppelt drin ist (mit unterschiedlichen IDs:

apollon77

@tklein

1.) EHOSTUNREACH bedeutet das das gerät in deinem Netzwerk nicht erreichbar war zu dem Zeitpunkt

2.) Was heisst "in Vocolinc App konfiguriert"? Hast du es dann dort gepaired? Naja dann kanns nicht nochmal sein

3.) Ich denke das Gerät hat mit dem Reset (oder dem pairing) seine ID gendert, damit kennt der Adapter beide. Kannst du in den Adapter-Objekten löschen

tklein

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

1.) EHOSTUNREACH bedeutet das das gerät in deinem Netzwerk nicht erreichbar war zu dem Zeitpunkt
--> thx für die Info
2.) Was heisst "in Vocolinc App konfiguriert"? Hast du es dann dort gepaired? Naja dann kanns nicht nochmal sein
--> nachdem es nach dem reset nicht geklappt hatte, habe ich das Device in der entsprechende App angelernt. Mir war/ist nicht bekannt, wie nach einem Device ohne konfigurierten WLAN nur mit dem Code eine Verbindung mit dem IOB erstellt werden kann
3.) Ich denke das Gerät hat mit dem Reset (oder dem pairing) seine ID gendert, damit kennt der Adapter beide. Kannst du in den Adapter-Objekten löschen
--> ok, werde ich dann löschen

pql

@apollon77 Versuche ein Eve Energy zu koppeln, aber ohne Erfolg.
Hardware ist ein RPI4 mit integriertem Bluetooth.

Noch eine Idee?

2022-02-13 12:30:06.032  - debug: homekit-controller.0 (17060) Discovered BLE device up: 0d:30:8f:xx:xx:xx/Eve Energy EA06
2022-02-13 12:30:06.033  - debug: homekit-controller.0 (17060) BLE-0D:30:8F:xx:xx:xx Discovered BLE device: {"name":"Eve Energy EA06","CoID":76,"TY":6,"AIL":49,"SF":1,"DeviceID":"0d:30:8f:xx:xx:xx","ACID":7,"GSN":1,"CN":3,"CV":2,"c#":3,"id":"0d:30:8f:xx:xx:xx","ci":7,"availableToPair":true}
2022-02-13 12:30:06.035  - info: homekit-controller.0 (17060) BLE-0D:30:8F:xx:xx:xx (Eve Energy EA06) found without pairing data but available for pairing: Create basic objects
2022-02-13 12:30:06.036  - debug: homekit-controller.0 (17060) Service: {"name":"Eve Energy EA06","CoID":76,"TY":6,"AIL":49,"SF":1,"DeviceID":"0d:30:8f:xx:xx:xx","ACID":7,"GSN":1,"CN":3,"CV":2,"c#":3,"id":"0d:30:8f:xx:xx:xx","ci":7,"availableToPair":true}
2022-02-13 12:30:06.088  - debug: homekit-controller.0 (17060) state homekit-controller.0.BLE-0D:30:8F:xx:xx:xx.info.connectionType changed: BLE (ack = true)
2022-02-13 12:30:06.114  - debug: homekit-controller.0 (17060) state homekit-controller.0.BLE-0D:30:8F:xx:xx:xx.info.id changed: 0d:30:8f:xx:xx:xx (ack = true)
2022-02-13 12:30:06.136  - debug: homekit-controller.0 (17060) state homekit-controller.0.BLE-0D:30:8F:xx:xx:xx.info.connected changed: false (ack = true)
2022-02-13 12:30:06.158  - debug: homekit-controller.0 (17060) state homekit-controller.0.BLE-0D:30:8F:xx:xx:xx.admin.isPaired changed: false (ack = true)
2022-02-13 12:30:06.171  - debug: homekit-controller.0 (17060) state homekit-controller.0.BLE-0D:30:8F:xx:xx:xx.info.lastDiscovered changed: 1644751806037 (ack = true)
2022-02-13 12:30:36.166  - debug: homekit-controller.0 (17060) Message getDiscoveredDevices received: {"command":"getDiscoveredDevices","message":null,"from":"system.adapter.admin.0","callback":{"message":null,"id":77,"ack":false,"time":1644751836163},"_id":61388363})
2022-02-13 12:30:36.167  - debug: homekit-controller.0 (17060) Response to Command getDiscoveredDevices: {"success":true,"error":false,"devices":[{"id":"BLE-0D:30:8F:xx:xx:xx","serviceType":"BLE","connected":false,"discovered":true,"availableToPair":true,"discoveredName":"Eve Energy EA06","discoveredCategory":"Outlet","pairedWithThisInstance":false},{"id":"BLE-14:36:5E:xx:xx:xx","serviceType":"BLE","connected":false,"discovered":true,"availableToPair":false,"discoveredName":"Nuki_XXXXX","discoveredCategory":"Lock","pairedWithThisInstance":false}]}
2022-02-13 12:30:36.169  - debug: homekit-controller.0 (17060) sendTo "getDiscoveredDevices" to system.adapter.admin.0 from system.adapter.homekit-controller.0
2022-02-13 12:30:48.359  - debug: homekit-controller.0 (17060) Message pairDevice received: {"command":"pairDevice","message":{"deviceId":"BLE-0D:30:8F:xx:xx:xx","pin":"yyy-yy-yyy"},"from":"system.adapter.admin.0","callback":{"message":{"deviceId":"BLE-0D:30:8F:xx:xx:xx","pin":"yyy-yy-yyy"},"id":78,"ack":false,"time":1644751848356},"_id":61388364})
  hap-controller:gatt-connection connect peripheral +0ms
  hap-controller:gatt-connection dbc159db8b1b/db:c1:59:db:8b:1b Write for characteristic 0000004f0000100080000026bb765291 0003001100 +857ms
  hap-controller:gatt-connection dbc159db8b1b/db:c1:59:db:8b:1b Received data for characteristic 0000004f0000100080000026bb765291 0200000300010102 +58ms
  hap-controller:gatt-connection disconnect peripheral +1ms
  hap-controller:gatt-connection Peripheral disconnected +16ms
2022-02-13 12:30:49.301  - info: homekit-controller.0 (17060) Use PairMethod 0 to pair BLE-0D:30:8F:xx:xx:xx
2022-02-13 12:30:49.303  - debug: homekit-controller.0 (17060) BLE-0D:30:8F:xx:xx:xx Start Homekit Device Client initialization
  hap-controller:gatt-connection connect peripheral +8ms
  hap-controller:gatt-connection Peripheral disconnected +308ms
2022-02-13 12:30:49.616  - debug: homekit-controller.0 (17060) Response to Command pairDevice: {"success":false,"error":"Cannot pair with device BLE-0D:30:8F:xx:xx:xx because of error undefined (undefined): undefined"}
2022-02-13 12:30:49.617  - debug: homekit-controller.0 (17060) sendTo "pairDevice" to system.adapter.admin.0 from system.adapter.homekit-controller.0

apollon77

@pql In dem Fall bekommt das Adapter keine Antwort vom Gerät. Geht ein Identify? Ich hab inzwischen so bissl da sGefühl das der RPI "Onboard" BLE zickig ist ... ggf mal mit nem BLE USB Stick versuchen?

pql

@apollon77 Identify funktioniert, Gerät blinkt entsprechend und der Debug bestätigt dies auch mit einem "Success"

2022-02-13 13:36:36.527  - debug: homekit-controller.0 (28302) Message identify received: {"command":"identify","message":{"deviceId":"BLE-0D:30:8F:xx:xx:xx"},"from":"system.adapter.admin.0","callback":{"message":{"deviceId":"BLE-0D:30:8F:xx:xx:xx"},"id":95,"ack":false,"time":1644755796524},"_id":61388381})
2022-02-13 13:36:36.529  - debug: homekit-controller.0 (28302) Device BLE-0D:30:8F:xx:xx:xx: Identify triggered
  hap-controller:gatt-connection connect peripheral +0ms
  hap-controller:tlv Add 1 bytes for tag 1: 01 +0ms
  hap-controller:gatt-connection dbc159db8b1b/db:c1:59:db:8b:1b Write for characteristic 000000140000100080000026bb765291 00020002000300010101 +924ms
  hap-controller:gatt-connection dbc159db8b1b/db:c1:59:db:8b:1b Received data for characteristic 000000140000100080000026bb765291 020000 +59ms
  hap-controller:gatt-connection disconnect peripheral +0ms
  hap-controller:gatt-connection Peripheral disconnected +17ms
2022-02-13 13:36:37.538  - debug: homekit-controller.0 (28302) Response to Command identify: {"success":true,"error":false}
2022-02-13 13:36:37.542  - debug: homekit-controller.0 (28302) sendTo "identify" to system.adapter.admin.0 from system.adapter.homekit-controller.0

USB BLE Stick hab ich nicht zur Hand, müsste mir dann erst einen besorgen

apollon77

@pql Also beimn Pairen sieht man das das Gerät auf den Connect versuch antwortet wo die unterstützten Pairing Methoden gelesen werden.Danach aber eine zweite Verbindung nicht annimmt um das eigentliche Pairing zu machen. Ich schaue nachher nochmal

EDIT: Code Seitig sieht an sich alles korrekt aus ... keine Ahnung warum das zickt und kann es auch nicht nachstellen

pql

@apollon77 Hab jetzt einen USB Stick, gleiches Spiel; Identify funktioniert, Pairing nicht.

Log-Output ist diesmal aber etwas mehr was den Pairing Connect an geht.. Es kommt auf jeden Fall etwas zurück

2022-02-15 17:46:01.425  - debug: homekit-controller.0 (3773) Message pairDevice received: {"command":"pairDevice","message":{"deviceId":"BLE-0D:30:8F:xx:xx:xx","pin":"xxx-xx-xxx"},"from":"system.adapter.admin.0","callback":{"message":{"deviceId":"BLE-0D:30:8F:xx:xx:xx","pin":"xxx-xx-xxx"},"id":16,"ack":false,"time":1644943561422},"_id":32016392})
  hap-controller:gatt-connection connect peripheral +16s
  hap-controller:gatt-connection dbc159db8b1b/db:c1:59:db:8b:1b Write for characteristic 0000004f0000100080000026bb765291 0003001100 +538ms
  hap-controller:gatt-connection dbc159db8b1b/db:c1:59:db:8b:1b Received data for characteristic 0000004f0000100080000026bb765291 0200000300010102 +75ms
  hap-controller:gatt-connection disconnect peripheral +0ms
  hap-controller:gatt-connection Peripheral disconnected +2s
2022-02-15 17:46:04.048  - info: homekit-controller.0 (3773) Use PairMethod 0 to pair BLE-0D:30:8F:xx:xx:xx
2022-02-15 17:46:04.051  - debug: homekit-controller.0 (3773) BLE-0D:30:8F:xx:xx:xx Start Homekit Device Client initialization
  hap-controller:gatt-connection connect peripheral +7ms
  hap-controller:tlv Add 1 bytes for tag 6: 01 +19s
  hap-controller:tlv Add 1 bytes for tag 0: 00 +1ms
  hap-controller:tlv Add 6 bytes for tag 1: 060101000100 +0ms
  hap-controller:tlv Add 1 bytes for tag 9: 01 +0ms
  hap-controller:gatt-connection dbc159db8b1b/db:c1:59:db:8b:1b Write for characteristic 0000004c0000100080000026bb765291 0002000f000b000106060101000100090101 +435ms
  hap-controller:gatt-connection dbc159db8b1b/db:c1:59:db:8b:1b Received data for characteristic 0000004c0000100080000026bb765291 0200009d0101ff06010203ff78b224faeea2de3cf805707ecd32546d248663b4689e88ff20ccefbeb56632d66398a9baea47555684b3b09ec4afe72c4ed3c33f5ce78c69fa7191cad76c879e22e51321de66442d9c89850c39546c8e3643679ac751d8d539b0c73c56dd8280be4d14215ee81e1eeb14cc05061cb6e486aeb00699207138d0577e288bba6fb6c23c97c3157f69f2ba8da537ad274cab0d5f76cff5b4ae9a828cdac434a42bcbe0132f8c3638a48de223a01d2ba06c92284efbaa3b25c3742ac138b1ad182fa614d12fdfa44cb89ccf3323cf92e8d7627dcdb1ba27403853fea875693785a68ee6731e96172ad3f04677bc57a36352f5b0ff5e +583ms
  hap-controller:gatt-connection Peripheral disconnected +45ms
2022-02-15 17:46:05.118  - debug: homekit-controller.0 (3773) Response to Command pairDevice: {"success":false,"error":"Cannot pair with device BLE-0D:30:8F:xx:xx:xx because of error undefined (undefined): undefined"}
2022-02-15 17:46:05.119  - debug: homekit-controller.0 (3773) sendTo "pairDevice" to system.adapter.admin.0 from system.adapter.homekit-controller.0

apollon77

@pql Inndem Fall kommt er etwas weiter aber das Gerät macht immer noch einen Disconnect. IST es vllt zu nah oder zu weit weg? mal frisch resetten?

Also wenn ich es richtig verstehe, dann sagen die Daten das 500 Byte kommen, es sind aber nur 150 und dann disconnect ...

pql

@apollon77 frisch resettet (mehrfach) und näher dran leider ohne Erfolg. Gleiche Thematik.

Aber ok, dann wird das wohl am Eve Energy liegen. Direktes Pairing mit iOS funktioniert tadelos.

apollon77

@pql ich hab auch einen eve Energy undeniable mir tut alles - aber von nem Mac aus.

Also du könntest jetzt nochmal das hci debugging parallel laufen lassen. Siehe troubleshooting in der readme. Vllt sieht man da noch was.

Fortune95

@apollon77
So bin gerade mal wieder mit Eve am testen aber mit gleichem Ergebnis....
Über BLE zickt er immer noch.

2022-02-16 19:05:03.537 - debug: homekit-controller.0 (115079) Redis Objects: Use Redis connection: 127.0.0.1:9001
2022-02-16 19:05:03.642 - debug: homekit-controller.0 (115079) Objects client ready ... initialize now
2022-02-16 19:05:03.647 - debug: homekit-controller.0 (115079) Objects create System PubSub Client
2022-02-16 19:05:03.650 - debug: homekit-controller.0 (115079) Objects create User PubSub Client
2022-02-16 19:05:03.753 - debug: homekit-controller.0 (115079) Objects client initialize lua scripts
2022-02-16 19:05:03.779 - debug: homekit-controller.0 (115079) Objects connected to redis: 127.0.0.1:9001
2022-02-16 19:05:03.816 - debug: homekit-controller.0 (115079) Redis States: Use Redis connection: 127.0.0.1:6379
2022-02-16 19:05:03.828 - debug: homekit-controller.0 (115079) States create System PubSub Client
2022-02-16 19:05:03.830 - debug: homekit-controller.0 (115079) States create User PubSub Client
2022-02-16 19:05:03.846 - debug: homekit-controller.0 (115079) States connected to redis: 127.0.0.1:6379
2022-02-16 19:05:03.913 - debug: homekit-controller.0 (115079) Plugin sentry Initialize Plugin (enabled=true)
2022-02-16 19:05:04.430 - info: homekit-controller.0 (115079) starting. Version 0.4.3 in /opt/iobroker/node_modules/iobroker.homekit-controller, node: v14.19.0, js-controller: 4.0.10
2022-02-16 19:05:04.709 - debug: homekit-controller.0 (115079) state homekit-controller.0.info.connection changed: false (ack = true)
2022-02-16 19:05:04.710 - debug: homekit-controller.0 (115079) Init 2 known devices without discovery ...
2022-02-16 19:05:04.711 - debug: homekit-controller.0 (115079) Init IP-10:92:E9:E7:AE:8F as known device
2022-02-16 19:05:04.713 - info: homekit-controller.0 (115079) IP-10:92:E9:E7:AE:8F (Eve Extend C054) found without pairing data but available for pairing: Create basic objects
2022-02-16 19:05:04.714 - debug: homekit-controller.0 (115079) Service: {"name":"Eve Extend C054","address":"192.168.95.50","port":8080,"c#":12,"ff":1,"id":"10:92:E9:E7:AE:8F","md":"Eve Extend 20EAB9901","pv":"1.1","s#":1,"sf":1,"ci":2,"availableToPair":true}
2022-02-16 19:05:04.765 - debug: homekit-controller.0 (115079) state homekit-controller.0.IP-10:92:E9:E7:AE:8F.info.connectionType changed: IP (ack = true)
2022-02-16 19:05:04.778 - debug: homekit-controller.0 (115079) state homekit-controller.0.IP-10:92:E9:E7:AE:8F.info.id changed: 10:92:E9:E7:AE:8F (ack = true)
2022-02-16 19:05:04.792 - debug: homekit-controller.0 (115079) state homekit-controller.0.IP-10:92:E9:E7:AE:8F.info.address changed: 192.168.95.50 (ack = true)
2022-02-16 19:05:04.804 - debug: homekit-controller.0 (115079) state homekit-controller.0.IP-10:92:E9:E7:AE:8F.info.connected changed: false (ack = true)
2022-02-16 19:05:04.827 - debug: homekit-controller.0 (115079) state homekit-controller.0.IP-10:92:E9:E7:AE:8F.admin.isPaired changed: false (ack = true)
2022-02-16 19:05:04.841 - debug: homekit-controller.0 (115079) state homekit-controller.0.IP-10:92:E9:E7:AE:8F.info.lastDiscovered changed: 1645034704716 (ack = true)
2022-02-16 19:05:04.860 - debug: homekit-controller.0 (115079) Init BLE-EA:80:43:5F:2E:FE as known device
2022-02-16 19:05:04.861 - info: homekit-controller.0 (115079) BLE-EA:80:43:5F:2E:FE (Eve Degree 5980) found without pairing data but available for pairing: Create basic objects
2022-02-16 19:05:04.862 - debug: homekit-controller.0 (115079) Service: {"name":"Eve Degree 5980","CoID":76,"TY":6,"AIL":49,"SF":1,"DeviceID":"ea:80:43:5f:2e:fe","ACID":10,"GSN":1,"CN":3,"CV":2,"c#":3,"id":"ea:80:43:5f:2e:fe","ci":10,"availableToPair":true}
2022-02-16 19:05:04.900 - debug: homekit-controller.0 (115079) state homekit-controller.0.BLE-EA:80:43:5F:2E:FE.info.connectionType changed: BLE (ack = true)
2022-02-16 19:05:04.913 - debug: homekit-controller.0 (115079) Discovered IP device up: 10:92:E9:E7:AE:8F/Eve Extend C054
2022-02-16 19:05:04.914 - debug: homekit-controller.0 (115079) IP-10:92:E9:E7:AE:8F Discovered IP device: {"name":"Eve Extend C054","address":"192.168.95.50","port":8080,"c#":14,"ff":1,"id":"10:92:E9:E7:AE:8F","md":"Eve Extend 20EAB9901","pv":"1.1","s#":1,"sf":0,"ci":2,"availableToPair":false}
2022-02-16 19:05:04.915 - info: homekit-controller.0 (115079) IP-10:92:E9:E7:AE:8F (Eve Extend C054) found without known pairing data and already paired: ignoring
2022-02-16 19:05:04.930 - debug: homekit-controller.0 (115079) state homekit-controller.0.BLE-EA:80:43:5F:2E:FE.info.id changed: ea:80:43:5f:2e:fe (ack = true)
2022-02-16 19:05:04.943 - debug: homekit-controller.0 (115079) state homekit-controller.0.BLE-EA:80:43:5F:2E:FE.info.connected changed: false (ack = true)
2022-02-16 19:05:04.966 - debug: homekit-controller.0 (115079) state homekit-controller.0.BLE-EA:80:43:5F:2E:FE.admin.isPaired changed: false (ack = true)
2022-02-16 19:05:04.979 - debug: homekit-controller.0 (115079) state homekit-controller.0.BLE-EA:80:43:5F:2E:FE.info.lastDiscovered changed: 1645034704863 (ack = true)
2022-02-16 19:05:05.002 - debug: homekit-controller.0 (115079) Discovered IP device up: 47:FB:8F:AA:80:82/Eve Extend 726E
2022-02-16 19:05:05.003 - debug: homekit-controller.0 (115079) IP-47:FB:8F:AA:80:82 Discovered IP device: {"name":"Eve Extend 726E","address":"169.254.182.94","port":8080,"c#":5,"ff":1,"id":"47:FB:8F:AA:80:82","md":"Eve Extend 20EAB9901","pv":"1.1","s#":1,"sf":0,"ci":2,"availableToPair":false}
2022-02-16 19:05:05.004 - info: homekit-controller.0 (115079) IP-47:FB:8F:AA:80:82 (Eve Extend 726E) found without known pairing data and already paired: ignoring
2022-02-16 19:05:05.636 - debug: homekit-controller.0 (115079) Discovered BLE device up: f6:36:ed:19:09:14/Eve Thermo 8FE8
2022-02-16 19:05:05.636 - debug: homekit-controller.0 (115079) BLE-F6:36:ED:19:09:14 Discovered BLE device: {"name":"Eve Thermo 8FE8","CoID":76,"TY":6,"AIL":49,"SF":0,"DeviceID":"f6:36:ed:19:09:14","ACID":9,"GSN":8861,"CN":5,"CV":2,"c#":5,"id":"f6:36:ed:19:09:14","ci":9,"availableToPair":false}
2022-02-16 19:05:05.637 - info: homekit-controller.0 (115079) BLE-F6:36:ED:19:09:14 (Eve Thermo 8FE8) found without known pairing data and already paired: ignoring
2022-02-16 19:05:05.951 - debug: homekit-controller.0 (115079) Discovered IP device up: 77:a2:42:96:a1:50/ioBroker B13E
2022-02-16 19:05:05.951 - debug: homekit-controller.0 (115079) IP-77:A2:42:96:A1:50 Discovered IP device: {"name":"ioBroker B13E","address":"192.168.95.212","port":44763,"c#":21,"ff":0,"id":"77:a2:42:96:a1:50","md":"not configured","pv":"1.1","s#":1,"sf":0,"ci":2,"availableToPair":false}
2022-02-16 19:05:05.952 - info: homekit-controller.0 (115079) IP-77:A2:42:96:A1:50 (ioBroker B13E) found without known pairing data and already paired: ignoring
2022-02-16 19:05:07.173 - debug: homekit-controller.0 (115079) Discovered BLE device up: ea:80:43:5f:2e:fe/Eve
2022-02-16 19:05:07.174 - debug: homekit-controller.0 (115079) BLE-EA:80:43:5F:2E:FE Discovered BLE device: {"name":"Eve","CoID":76,"TY":6,"AIL":49,"SF":1,"DeviceID":"ea:80:43:5f:2e:fe","ACID":10,"GSN":1,"CN":3,"CV":2,"c#":3,"id":"ea:80:43:5f:2e:fe","ci":10,"availableToPair":true}
2022-02-16 19:05:07.174 - info: homekit-controller.0 (115079) BLE-EA:80:43:5F:2E:FE (Eve) found without pairing data but available for pairing: Create basic objects
2022-02-16 19:05:07.175 - debug: homekit-controller.0 (115079) Service: {"name":"Eve","CoID":76,"TY":6,"AIL":49,"SF":1,"DeviceID":"ea:80:43:5f:2e:fe","ACID":10,"GSN":1,"CN":3,"CV":2,"c#":3,"id":"ea:80:43:5f:2e:fe","ci":10,"availableToPair":true}
2022-02-16 19:05:07.218 - debug: homekit-controller.0 (115079) state homekit-controller.0.BLE-EA:80:43:5F:2E:FE.info.connectionType changed: BLE (ack = true)
2022-02-16 19:05:07.237 - debug: homekit-controller.0 (115079) state homekit-controller.0.BLE-EA:80:43:5F:2E:FE.info.id changed: ea:80:43:5f:2e:fe (ack = true)
2022-02-16 19:05:07.268 - debug: homekit-controller.0 (115079) state homekit-controller.0.BLE-EA:80:43:5F:2E:FE.info.connected changed: false (ack = true)
2022-02-16 19:05:07.334 - debug: homekit-controller.0 (115079) state homekit-controller.0.BLE-EA:80:43:5F:2E:FE.admin.isPaired changed: false (ack = true)
2022-02-16 19:05:07.354 - debug: homekit-controller.0 (115079) state homekit-controller.0.BLE-EA:80:43:5F:2E:FE.info.lastDiscovered changed: 1645034707176 (ack = true)
2022-02-16 19:05:07.736 - debug: homekit-controller.0 (115079) Message getDiscoveredDevices received: {"command":"getDiscoveredDevices","message":null,"from":"system.adapter.admin.0","callback":{"message":null,"id":51,"ack":false,"time":1645034707733},"_id":61965836})
2022-02-16 19:05:07.738 - debug: homekit-controller.0 (115079) Response to Command getDiscoveredDevices: {"success":true,"error":false,"devices":[{"id":"BLE-EA:80:43:5F:2E:FE","serviceType":"BLE","connected":false,"discovered":true,"availableToPair":true,"discoveredName":"Eve","discoveredCategory":"Sensor","pairedWithThisInstance":false},{"id":"IP-10:92:E9:E7:AE:8F","serviceType":"IP","connected":false,"discovered":true,"availableToPair":false,"discoveredName":"Eve Extend C054","discoveredCategory":"Bridge","pairedWithThisInstance":false},{"id":"IP-47:FB:8F:AA:80:82","serviceType":"IP","connected":false,"discovered":true,"availableToPair":false,"discoveredName":"Eve Extend 726E","discoveredCategory":"Bridge","pairedWithThisInstance":false},{"id":"BLE-F6:36:ED:19:09:14","serviceType":"BLE","connected":false,"discovered":true,"availableToPair":false,"discoveredName":"Eve Thermo 8FE8","discoveredCategory":"Thermostat","pairedWithThisInstance":false},{"id":"IP-77:A2:42:96:A1:50","serviceType":"IP","connected":false,"discovered":true,"availableToPair":false,"discoveredName":"ioBroker B13E","discoveredCategory":"Bridge","pairedWithThisInstance":false}]}
2022-02-16 19:05:12.329 - debug: homekit-controller.0 (115079) Message identify received: {"command":"identify","message":{"deviceId":"BLE-EA:80:43:5F:2E:FE"},"from":"system.adapter.admin.0","callback":{"message":{"deviceId":"BLE-EA:80:43:5F:2E:FE"},"id":52,"ack":false,"time":1645034712328},"_id":61965837})
2022-02-16 19:05:12.330 - debug: homekit-controller.0 (115079) Device BLE-EA:80:43:5F:2E:FE: Identify triggered
2022-02-16 19:05:17.002 - debug: homekit-controller.0 (115079) Response to Command identify: {"success":true,"error":false}
2022-02-16 19:05:18.514 - debug: homekit-controller.0 (115079) Message getDiscoveredDevices received: {"command":"getDiscoveredDevices","message":null,"from":"system.adapter.admin.0","callback":{"message":null,"id":53,"ack":false,"time":1645034718512},"_id":61965838})
2022-02-16 19:05:18.515 - debug: homekit-controller.0 (115079) Response to Command getDiscoveredDevices: {"success":true,"error":false,"devices":[{"id":"BLE-EA:80:43:5F:2E:FE","serviceType":"BLE","connected":false,"discovered":true,"availableToPair":true,"discoveredName":"Eve","discoveredCategory":"Sensor","pairedWithThisInstance":false},{"id":"IP-10:92:E9:E7:AE:8F","serviceType":"IP","connected":false,"discovered":true,"availableToPair":false,"discoveredName":"Eve Extend C054","discoveredCategory":"Bridge","pairedWithThisInstance":false},{"id":"IP-47:FB:8F:AA:80:82","serviceType":"IP","connected":false,"discovered":true,"availableToPair":false,"discoveredName":"Eve Extend 726E","discoveredCategory":"Bridge","pairedWithThisInstance":false},{"id":"BLE-F6:36:ED:19:09:14","serviceType":"BLE","connected":false,"discovered":true,"availableToPair":false,"discoveredName":"Eve Thermo 8FE8","discoveredCategory":"Thermostat","pairedWithThisInstance":false},{"id":"IP-77:A2:42:96:A1:50","serviceType":"IP","connected":false,"discovered":true,"availableToPair":false,"discoveredName":"ioBroker B13E","discoveredCategory":"Bridge","pairedWithThisInstance":false}]}
2022-02-16 19:05:34.097 - debug: homekit-controller.0 (115079) Message pairDevice received: {"command":"pairDevice","message":{"deviceId":"BLE-EA:80:43:5F:2E:FE","pin":"843-54-008"},"from":"system.adapter.admin.0","callback":{"message":{"deviceId":"BLE-EA:80:43:5F:2E:FE","pin":"843-54-008"},"id":54,"ack":false,"time":1645034734094},"_id":61965839})
2022-02-16 19:05:38.076 - info: homekit-controller.0 (115079) Use PairMethod 0 to pair BLE-EA:80:43:5F:2E:FE
2022-02-16 19:05:38.078 - debug: homekit-controller.0 (115079) BLE-EA:80:43:5F:2E:FE Start Homekit Device Client initialization
2022-02-16 19:05:47.900 - debug: homekit-controller.0 (115079) Response to Command pairDevice: {"success":false,"error":"Cannot pair with device BLE-EA:80:43:5F:2E:FE because of error undefined (undefined): undefined"}
2022-02-16 19:05:48.355 - debug: homekit-controller.0 (115079) Discovered BLE device changed: ea:80:43:5f:2e:fe/Eve Degree 5980
2022-02-16 19:05:48.357 - debug: homekit-controller.0 (115079) BLE-EA:80:43:5F:2E:FE Discovered BLE device: {"name":"Eve Degree 5980","CoID":76,"TY":6,"AIL":49,"SF":0,"DeviceID":"ea:80:43:5f:2e:fe","ACID":10,"GSN":2,"CN":3,"CV":2,"c#":3,"id":"ea:80:43:5f:2e:fe","ci":10,"availableToPair":false}
2022-02-16 19:05:48.358 - info: homekit-controller.0 (115079) BLE-EA:80:43:5F:2E:FE (Eve Degree 5980) found without known pairing data and already paired: ignoring
2022-02-16 19:06:32.001 - debug: homekit-controller.0 (115079) Message getDiscoveredDevices received: {"command":"getDiscoveredDevices","message":null,"from":"system.adapter.admin.0","callback":{"message":null,"id":58,"ack":false,"time":1645034791999},"_id":61965843})
2022-02-16 19:06:32.002 - debug: homekit-controller.0 (115079) Response to Command getDiscoveredDevices: {"success":true,"error":false,"devices":[{"id":"IP-10:92:E9:E7:AE:8F","serviceType":"IP","connected":false,"discovered":true,"availableToPair":false,"discoveredName":"Eve Extend C054","discoveredCategory":"Bridge","pairedWithThisInstance":false},{"id":"BLE-EA:80:43:5F:2E:FE","serviceType":"BLE","connected":false,"discovered":true,"availableToPair":false,"discoveredName":"Eve Degree 5980","discoveredCategory":"Sensor","pairedWithThisInstance":false},{"id":"IP-47:FB:8F:AA:80:82","serviceType":"IP","connected":false,"discovered":true,"availableToPair":false,"discoveredName":"Eve Extend 726E","discoveredCategory":"Bridge","pairedWithThisInstance":false},{"id":"BLE-F6:36:ED:19:09:14","serviceType":"BLE","connected":false,"discovered":true,"availableToPair":false,"discoveredName":"Eve Thermo 8FE8","discoveredCategory":"Thermostat","pairedWithThisInstance":false},{"id":"IP-77:A2:42:96:A1:50","serviceType":"IP","connected":false,"discovered":true,"availableToPair":false,"discoveredName":"ioBroker B13E","discoveredCategory":"Bridge","pairedWithThisInstance":false}]}
2022-02-16 19:06:58.307 - info: homekit-controller.0 (115079) Got terminate signal TERMINATE_YOURSELF
2022-02-16 19:06:58.322 - info: homekit-controller.0 (115079) terminating
2022-02-16 19:06:58.325 - debug: homekit-controller.0 (115079) Plugin sentry destroyed
2022-02-16 19:06:58.326 - info: homekit-controller.0 (115079) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
2022-02-16 19:07:04.162 - debug: homekit-controller.0 (115115) Redis Objects: Use Redis connection: 127.0.0.1:9001
2022-02-16 19:07:04.275 - debug: homekit-controller.0 (115115) Objects client ready ... initialize now
2022-02-16 19:07:04.282 - debug: homekit-controller.0 (115115) Objects create System PubSub Client
2022-02-16 19:07:04.286 - debug: homekit-controller.0 (115115) Objects create User PubSub Client
2022-02-16 19:07:04.375 - debug: homekit-controller.0 (115115) Objects client initialize lua scripts
2022-02-16 19:07:04.393 - debug: homekit-controller.0 (115115) Objects connected to redis: 127.0.0.1:9001
2022-02-16 19:07:04.471 - debug: homekit-controller.0 (115115) Redis States: Use Redis connection: 127.0.0.1:6379
2022-02-16 19:07:04.489 - debug: homekit-controller.0 (115115) States create System PubSub Client
2022-02-16 19:07:04.490 - debug: homekit-controller.0 (115115) States create User PubSub Client
2022-02-16 19:07:04.501 - debug: homekit-controller.0 (115115) States connected to redis: 127.0.0.1:6379
2022-02-16 19:07:04.551 - debug: homekit-controller.0 (115115) Plugin sentry Initialize Plugin (enabled=true)
2022-02-16 19:07:05.037 - info: homekit-controller.0 (115115) starting. Version 0.4.3 in /opt/iobroker/node_modules/iobroker.homekit-controller, node: v14.19.0, js-controller: 4.0.10
2022-02-16 19:07:05.299 - debug: homekit-controller.0 (115115) state homekit-controller.0.info.connection changed: false (ack = true)
2022-02-16 19:07:05.311 - debug: homekit-controller.0 (115115) Init 2 known devices without discovery ...
2022-02-16 19:07:05.312 - debug: homekit-controller.0 (115115) Init IP-10:92:E9:E7:AE:8F as known device
2022-02-16 19:07:05.314 - info: homekit-controller.0 (115115) IP-10:92:E9:E7:AE:8F (Eve Extend C054) found without pairing data but available for pairing: Create basic objects
2022-02-16 19:07:05.315 - debug: homekit-controller.0 (115115) Service: {"name":"Eve Extend C054","address":"192.168.95.50","port":8080,"c#":12,"ff":1,"id":"10:92:E9:E7:AE:8F","md":"Eve Extend 20EAB9901","pv":"1.1","s#":1,"sf":1,"ci":2,"availableToPair":true}
2022-02-16 19:07:05.367 - debug: homekit-controller.0 (115115) state homekit-controller.0.IP-10:92:E9:E7:AE:8F.info.connectionType changed: IP (ack = true)
2022-02-16 19:07:05.384 - debug: homekit-controller.0 (115115) state homekit-controller.0.IP-10:92:E9:E7:AE:8F.info.id changed: 10:92:E9:E7:AE:8F (ack = true)
2022-02-16 19:07:05.405 - debug: homekit-controller.0 (115115) state homekit-controller.0.IP-10:92:E9:E7:AE:8F.info.address changed: 192.168.95.50 (ack = true)
2022-02-16 19:07:05.417 - debug: homekit-controller.0 (115115) state homekit-controller.0.IP-10:92:E9:E7:AE:8F.info.connected changed: false (ack = true)
2022-02-16 19:07:05.441 - debug: homekit-controller.0 (115115) state homekit-controller.0.IP-10:92:E9:E7:AE:8F.admin.isPaired changed: false (ack = true)
2022-02-16 19:07:05.456 - debug: homekit-controller.0 (115115) state homekit-controller.0.IP-10:92:E9:E7:AE:8F.info.lastDiscovered changed: 1645034825317 (ack = true)
2022-02-16 19:07:05.485 - debug: homekit-controller.0 (115115) Init BLE-EA:80:43:5F:2E:FE as known device
2022-02-16 19:07:05.486 - info: homekit-controller.0 (115115) BLE-EA:80:43:5F:2E:FE (Eve) found without pairing data but available for pairing: Create basic objects
2022-02-16 19:07:05.487 - debug: homekit-controller.0 (115115) Service: {"name":"Eve","CoID":76,"TY":6,"AIL":49,"SF":1,"DeviceID":"ea:80:43:5f:2e:fe","ACID":10,"GSN":1,"CN":3,"CV":2,"c#":3,"id":"ea:80:43:5f:2e:fe","ci":10,"availableToPair":true}
2022-02-16 19:07:05.527 - debug: homekit-controller.0 (115115) Discovered IP device up: 10:92:E9:E7:AE:8F/Eve Extend C054
2022-02-16 19:07:05.528 - debug: homekit-controller.0 (115115) IP-10:92:E9:E7:AE:8F Discovered IP device: {"name":"Eve Extend C054","address":"192.168.95.50","port":8080,"c#":14,"ff":1,"id":"10:92:E9:E7:AE:8F","md":"Eve Extend 20EAB9901","pv":"1.1","s#":1,"sf":0,"ci":2,"availableToPair":false}
2022-02-16 19:07:05.529 - info: homekit-controller.0 (115115) IP-10:92:E9:E7:AE:8F (Eve Extend C054) found without known pairing data and already paired: ignoring
2022-02-16 19:07:05.547 - debug: homekit-controller.0 (115115) state homekit-controller.0.BLE-EA:80:43:5F:2E:FE.info.connectionType changed: BLE (ack = true)
2022-02-16 19:07:05.553 - debug: homekit-controller.0 (115115) Discovered IP device up: 47:FB:8F:AA:80:82/Eve Extend 726E
2022-02-16 19:07:05.554 - debug: homekit-controller.0 (115115) IP-47:FB:8F:AA:80:82 Discovered IP device: {"name":"Eve Extend 726E","address":"169.254.182.94","port":8080,"c#":5,"ff":1,"id":"47:FB:8F:AA:80:82","md":"Eve Extend 20EAB9901","pv":"1.1","s#":1,"sf":0,"ci":2,"availableToPair":false}
2022-02-16 19:07:05.555 - info: homekit-controller.0 (115115) IP-47:FB:8F:AA:80:82 (Eve Extend 726E) found without known pairing data and already paired: ignoring
2022-02-16 19:07:05.571 - debug: homekit-controller.0 (115115) state homekit-controller.0.BLE-EA:80:43:5F:2E:FE.info.id changed: ea:80:43:5f:2e:fe (ack = true)
2022-02-16 19:07:05.585 - debug: homekit-controller.0 (115115) state homekit-controller.0.BLE-EA:80:43:5F:2E:FE.info.connected changed: false (ack = true)
2022-02-16 19:07:05.606 - debug: homekit-controller.0 (115115) state homekit-controller.0.BLE-EA:80:43:5F:2E:FE.admin.isPaired changed: false (ack = true)
2022-02-16 19:07:05.618 - debug: homekit-controller.0 (115115) state homekit-controller.0.BLE-EA:80:43:5F:2E:FE.info.lastDiscovered changed: 1645034825487 (ack = true)
2022-02-16 19:07:05.750 - debug: homekit-controller.0 (115115) Message getDiscoveredDevices received: {"command":"getDiscoveredDevices","message":null,"from":"system.adapter.admin.0","callback":{"message":null,"id":59,"ack":false,"time":1645034825748},"_id":61965844})
2022-02-16 19:07:05.752 - debug: homekit-controller.0 (115115) Response to Command getDiscoveredDevices: {"success":true,"error":false,"devices":[{"id":"BLE-EA:80:43:5F:2E:FE","serviceType":"BLE","connected":false,"discovered":true,"availableToPair":true,"discoveredName":"Eve","discoveredCategory":"Sensor","pairedWithThisInstance":false},{"id":"IP-10:92:E9:E7:AE:8F","serviceType":"IP","connected":false,"discovered":true,"availableToPair":false,"discoveredName":"Eve Extend C054","discoveredCategory":"Bridge","pairedWithThisInstance":false},{"id":"IP-47:FB:8F:AA:80:82","serviceType":"IP","connected":false,"discovered":true,"availableToPair":false,"discoveredName":"Eve Extend 726E","discoveredCategory":"Bridge","pairedWithThisInstance":false}]}
2022-02-16 19:07:06.006 - debug: homekit-controller.0 (115115) Discovered IP device up: 77:a2:42:96:a1:50/ioBroker B13E
2022-02-16 19:07:06.007 - debug: homekit-controller.0 (115115) IP-77:A2:42:96:A1:50 Discovered IP device: {"name":"ioBroker B13E","address":"192.168.95.212","port":44763,"c#":21,"ff":0,"id":"77:a2:42:96:a1:50","md":"not configured","pv":"1.1","s#":1,"sf":0,"ci":2,"availableToPair":false}
2022-02-16 19:07:06.008 - info: homekit-controller.0 (115115) IP-77:A2:42:96:A1:50 (ioBroker B13E) found without known pairing data and already paired: ignoring
2022-02-16 19:07:07.862 - debug: homekit-controller.0 (115115) Discovered BLE device up: ea:80:43:5f:2e:fe/Eve Degree 5980
2022-02-16 19:07:07.863 - debug: homekit-controller.0 (115115) BLE-EA:80:43:5F:2E:FE Discovered BLE device: {"name":"Eve Degree 5980","CoID":76,"TY":6,"AIL":49,"SF":0,"DeviceID":"ea:80:43:5f:2e:fe","ACID":10,"GSN":2,"CN":3,"CV":2,"c#":3,"id":"ea:80:43:5f:2e:fe","ci":10,"availableToPair":false}
2022-02-16 19:07:07.864 - info: homekit-controller.0 (115115) BLE-EA:80:43:5F:2E:FE (Eve Degree 5980) found without known pairing data and already paired: ignoring
2022-02-16 19:07:12.512 - debug: homekit-controller.0 (115115) Message identify received: {"command":"identify","message":{"deviceId":"BLE-EA:80:43:5F:2E:FE"},"from":"system.adapter.admin.0","callback":{"message":{"deviceId":"BLE-EA:80:43:5F:2E:FE"},"id":60,"ack":false,"time":1645034832511},"_id":61965845})
2022-02-16 19:07:12.514 - debug: homekit-controller.0 (115115) Device BLE-EA:80:43:5F:2E:FE: Identify triggered
2022-02-16 19:07:23.539 - debug: homekit-controller.0 (115115) Response to Command identify: {"success":false,"error":"Cannot identify device BLE-EA:80:43:5F:2E:FE because of error undefined: Identify returned error status: 5"}
2022-02-16 19:07:27.848 - debug: homekit-controller.0 (115115) Discovered BLE device up: f6:36:ed:19:09:14/Eve Thermo 8FE8
2022-02-16 19:07:27.849 - debug: homekit-controller.0 (115115) BLE-F6:36:ED:19:09:14 Discovered BLE device: {"name":"Eve Thermo 8FE8","CoID":76,"TY":6,"AIL":49,"SF":0,"DeviceID":"f6:36:ed:19:09:14","ACID":9,"GSN":8861,"CN":5,"CV":2,"c#":5,"id":"f6:36:ed:19:09:14","ci":9,"availableToPair":false}
2022-02-16 19:07:27.850 - info: homekit-controller.0 (115115) BLE-F6:36:ED:19:09:14 (Eve Thermo 8FE8) found without known pairing data and already paired: ignoring
2022-02-16 19:07:27.861 - debug: homekit-controller.0 (115115) Discovered BLE device changed: f6:36:ed:19:09:14/Eve Thermo 8FE8
2022-02-16 19:07:27.862 - debug: homekit-controller.0 (115115) BLE-F6:36:ED:19:09:14 Discovered BLE device: {"name":"Eve Thermo 8FE8","CoID":76,"TY":6,"AIL":49,"SF":0,"DeviceID":"f6:36:ed:19:09:14","ACID":9,"GSN":8862,"CN":5,"CV":2,"c#":5,"id":"f6:36:ed:19:09:14","ci":9,"availableToPair":false}
2022-02-16 19:07:27.862 - info: homekit-controller.0 (115115) BLE-F6:36:ED:19:09:14 (Eve Thermo 8FE8) found without known pairing data and already paired: ignoring
2022-02-16 19:08:47.689 - debug: homekit-controller.0 (115115) Discovered BLE device changed: f6:36:ed:19:09:14/Eve Thermo 8FE8
2022-02-16 19:08:47.691 - debug: homekit-controller.0 (115115) BLE-F6:36:ED:19:09:14 Discovered BLE device: {"name":"Eve Thermo 8FE8","CoID":76,"TY":6,"AIL":49,"SF":0,"DeviceID":"f6:36:ed:19:09:14","ACID":9,"GSN":8863,"CN":5,"CV":2,"c#":5,"id":"f6:36:ed:19:09:14","ci":9,"availableToPair":false}
2022-02-16 19:08:47.692 - info: homekit-controller.0 (115115) BLE-F6:36:ED:19:09:14 (Eve Thermo 8FE8) found without known pairing data and already paired: ignoring
2022-02-16 19:09:35.906 - debug: homekit-controller.0 (115115) Discovered BLE device up: 9b:3d:c6:d0:82:9b/Eve
2022-02-16 19:09:35.907 - debug: homekit-controller.0 (115115) BLE-9B:3D:C6:D0:82:9B Discovered BLE device: {"name":"Eve","CoID":76,"TY":6,"AIL":49,"SF":0,"DeviceID":"9b:3d:c6:d0:82:9b","ACID":9,"GSN":8239,"CN":5,"CV":2,"c#":5,"id":"9b:3d:c6:d0:82:9b","ci":9,"availableToPair":false}
2022-02-16 19:09:35.907 - info: homekit-controller.0 (115115) BLE-9B:3D:C6:D0:82:9B (Eve) found without known pairing data and already paired: ignoring
2022-02-16 19:09:51.356 - debug: homekit-controller.0 (115115) Discovered BLE device up: 91:90:ed:a6:89:85/Eve
2022-02-16 19:09:51.357 - debug: homekit-controller.0 (115115) BLE-91:90:ED:A6:89:85 Discovered BLE device: {"name":"Eve","CoID":76,"TY":6,"AIL":49,"SF":0,"DeviceID":"91:90:ed:a6:89:85","ACID":9,"GSN":6582,"CN":5,"CV":2,"c#":5,"id":"91:90:ed:a6:89:85","ci":9,"availableToPair":false}
2022-02-16 19:09:51.357 - info: homekit-controller.0 (115115) BLE-91:90:ED:A6:89:85 (Eve) found without known pairing data and already paired: ignoring
2022-02-16 19:10:59.889 - debug: homekit-controller.0 (115115) Discovered BLE device changed: ea:80:43:5f:2e:fe/Eve Degree 5980
2022-02-16 19:10:59.891 - debug: homekit-controller.0 (115115) BLE-EA:80:43:5F:2E:FE Discovered BLE device: {"name":"Eve Degree 5980","CoID":76,"TY":6,"AIL":49,"SF":0,"DeviceID":"ea:80:43:5f:2e:fe","ACID":10,"GSN":3,"CN":3,"CV":2,"c#":3,"id":"ea:80:43:5f:2e:fe","ci":10,"availableToPair":false}
2022-02-16 19:10:59.893 - info: homekit-controller.0 (115115) BLE-EA:80:43:5F:2E:FE (Eve Degree 5980) found without known pairing data and already paired: ignoring

NEWS

Test Alpha Homekit-Controller 0.0.x

Support us

1.5k
Online

30.5k
Users

76.9k
Topics

1.2m
Posts

NEWS

Test Alpha Homekit-Controller 0.0.x

Support us

1.5kOnline

30.5kUsers

76.9kTopics

1.2mPosts

1.5k
Online

30.5k
Users

76.9k
Topics

1.2m
Posts