unable to pair Aqara FP2

[apollon77]

unable to pair Aqara FP2

[Apollon77]

Ok, the log is not really containing much. Please use the way described in readme to get a detailed log https://github.com/Apollon77/ioBroker.homekit-controller#debugging

[Byolock]

I don't see much more content in this but here it is :

2023-11-06 09:32:43.348  - debug: homekit-controller.0 (1377796) Redis Objects: Use Redis connection: 127.0.0.1:9001
2023-11-06 09:32:43.357  - debug: homekit-controller.0 (1377796) Objects client ready ... initialize now
2023-11-06 09:32:43.357  - debug: homekit-controller.0 (1377796) Objects create System PubSub Client
2023-11-06 09:32:43.358  - debug: homekit-controller.0 (1377796) Objects create User PubSub Client
2023-11-06 09:32:43.362  - debug: homekit-controller.0 (1377796) Objects client initialize lua scripts
2023-11-06 09:32:43.363  - debug: homekit-controller.0 (1377796) Objects connected to redis: 127.0.0.1:9001
2023-11-06 09:32:43.367  - debug: homekit-controller.0 (1377796) Redis States: Use Redis connection: 127.0.0.1:9000
2023-11-06 09:32:43.369  - debug: homekit-controller.0 (1377796) States create System PubSub Client
2023-11-06 09:32:43.369  - debug: homekit-controller.0 (1377796) States create User PubSub Client
2023-11-06 09:32:43.419  - debug: homekit-controller.0 (1377796) States connected to redis: 127.0.0.1:9000
2023-11-06 09:32:43.450  - debug: homekit-controller.0 (1377796) Plugin sentry Initialize Plugin (enabled=true)
2023-11-06 09:32:43.496  - error: homekit-controller.0 (1377796) adapter disabled
2023-11-06 09:32:43.556  - info: homekit-controller.0 (1377796) starting. Version 0.5.8 in /opt/iobroker/node_modules/iobroker.homekit-controller, node: v18.17.1, js-controller: 5.0.12
2023-11-06 09:32:43.643  - debug: homekit-controller.0 (1377796) Init 1 known devices without discovery ...
2023-11-06 09:32:43.644  - debug: homekit-controller.0 (1377796) Init IP-D0:EA:D3:70:E7:F7 as known device
2023-11-06 09:32:43.645  - info: homekit-controller.0 (1377796) IP-D0:EA:D3:70:E7:F7 (Presence-Sensor-FP2-BCEA) found without pairing data but available for pairing: Create basic objects
2023-11-06 09:32:43.646  - debug: homekit-controller.0 (1377796) Service: {"name":"Presence-Sensor-FP2-BCEA","address":"192.168.1.35","port":63428,"c#":2,"ff":2,"id":"D0:EA:D3:70:E7:F7","md":"PS-S02D","pv":"1.1","s#":1,"sf":1,"ci":10,"availableToPair":true}
2023-11-06 09:32:43.913  - debug: homekit-controller.0 (1377796) Discovered IP device up: D0:EA:D3:70:E7:F7/Presence-Sensor-FP2-BCEA
2023-11-06 09:32:43.914  - debug: homekit-controller.0 (1377796) IP-D0:EA:D3:70:E7:F7 Device Discovery Update - reinitialize device (config changed=true): {"name":"Presence-Sensor-FP2-BCEA","address":"192.168.1.35","port":55692,"c#":2,"ff":2,"id":"D0:EA:D3:70:E7:F7","md":"PS-S02D","pv":"1.1","s#":1,"sf":1,"ci":10,"availableToPair":true}
2023-11-06 09:32:43.914  - info: homekit-controller.0 (1377796) IP-D0:EA:D3:70:E7:F7 (Presence-Sensor-FP2-BCEA) found without pairing data but available for pairing: Create basic objects
2023-11-06 09:32:43.915  - debug: homekit-controller.0 (1377796) Service: {"name":"Presence-Sensor-FP2-BCEA","address":"192.168.1.35","port":55692,"c#":2,"ff":2,"id":"D0:EA:D3:70:E7:F7","md":"PS-S02D","pv":"1.1","s#":1,"sf":1,"ci":10,"availableToPair":true}
2023-11-06 09:32:43.930  - debug: homekit-controller.0 (1377796) state homekit-controller.0.IP-D0:EA:D3:70:E7:F7.info.connectionType changed: IP (ack = true)
2023-11-06 09:32:43.975  - debug: homekit-controller.0 (1377796) state homekit-controller.0.IP-D0:EA:D3:70:E7:F7.info.id changed: D0:EA:D3:70:E7:F7 (ack = true)
2023-11-06 09:32:44.025  - debug: homekit-controller.0 (1377796) state homekit-controller.0.IP-D0:EA:D3:70:E7:F7.info.address changed: 192.168.1.35 (ack = true)
2023-11-06 09:32:44.076  - debug: homekit-controller.0 (1377796) state homekit-controller.0.IP-D0:EA:D3:70:E7:F7.info.connected changed: false (ack = true)
2023-11-06 09:32:44.128  - debug: homekit-controller.0 (1377796) state homekit-controller.0.IP-D0:EA:D3:70:E7:F7.admin.isPaired changed: false (ack = true)
2023-11-06 09:32:44.180  - debug: homekit-controller.0 (1377796) state homekit-controller.0.IP-D0:EA:D3:70:E7:F7.info.lastDiscovered changed: 1699259563915 (ack = true)
2023-11-06 09:33:18.831  - debug: homekit-controller.0 (1377796) Message getDiscoveredDevices received: {"command":"getDiscoveredDevices","message":null,"from":"system.adapter.admin.0","callback":{"message":null,"id":235,"ack":false,"time":1699259598830},"_id":24048589})
2023-11-06 09:33:18.833  - debug: homekit-controller.0 (1377796) Response to Command getDiscoveredDevices: {"success":true,"error":false,"devices":[{"id":"IP-D0:EA:D3:70:E7:F7","serviceType":"IP","connected":false,"discovered":true,"availableToPair":true,"discoveredName":"Presence-Sensor-FP2-BCEA","discoveredCategory":"Sensor","pairedWithThisInstance":false}]}
2023-11-06 09:33:34.711  - debug: homekit-controller.0 (1377796) Message pairDevice received: {"command":"pairDevice","message":{"deviceId":"IP-D0:EA:D3:70:E7:F7","pin":"980-72-531"},"from":"system.adapter.admin.0","callback":{"message":{"deviceId":"IP-D0:EA:D3:70:E7:F7","pin":"980-72-531"},"id":236,"ack":false,"time":1699259614709},"_id":24048590})
2023-11-06 09:33:34.712  - info: homekit-controller.0 (1377796) Use PairMethod 0 to pair IP-D0:EA:D3:70:E7:F7
2023-11-06 09:33:34.713  - debug: homekit-controller.0 (1377796) IP-D0:EA:D3:70:E7:F7 Start Homekit Device Client initialization on 192.168.1.35:55692
2023-11-06 09:36:03.294  - debug: homekit-controller.0 (1377796) Message getDiscoveredDevices received: {"command":"getDiscoveredDevices","message":null,"from":"system.adapter.admin.0","callback":{"message":null,"id":237,"ack":false,"time":1699259763294},"_id":24048591})
2023-11-06 09:36:03.295  - debug: homekit-controller.0 (1377796) Response to Command getDiscoveredDevices: {"success":true,"error":false,"devices":[{"id":"IP-D0:EA:D3:70:E7:F7","serviceType":"IP","connected":false,"discovered":true,"availableToPair":true,"discoveredName":"Presence-Sensor-FP2-BCEA","discoveredCategory":"Sensor","pairedWithThisInstance":false}]}
2023-11-06 09:41:41.531  - debug: homekit-controller.0 (1377796) Discovered IP device down: D0:EA:D3:70:E7:F7/Presence-Sensor-FP2-BCEA
2023-11-06 09:53:24.657  - debug: homekit-controller.0 (1377796) Message getDiscoveredDevices received: {"command":"getDiscoveredDevices","message":null,"from":"system.adapter.admin.0","callback":{"message":null,"id":241,"ack":false,"time":1699260804656},"_id":24048595})
2023-11-06 09:53:24.658  - debug: homekit-controller.0 (1377796) Response to Command getDiscoveredDevices: {"success":true,"error":false,"devices":[{"id":"IP-D0:EA:D3:70:E7:F7","serviceType":"IP","connected":false,"discovered":true,"availableToPair":true,"discoveredName":"Presence-Sensor-FP2-BCEA","discoveredCategory":"Sensor","pairedWithThisInstance":false}]}
2023-11-06 09:53:30.767  - info: homekit-controller.0 (1377796) terminating
2023-11-06 09:53:30.768  - debug: homekit-controller.0 (1377796) Plugin sentry destroyed
2023-11-06 09:53:30.768  - info: homekit-controller.0 (1377796) Terminated (NO_ERROR): Without reason
2023-11-06 09:53:31.270  - info: homekit-controller.0 (1377796) terminating

[Apollon77]

There should be more output onthe Shell where you started the adapter manually ... please grab this log ... so the shell output

[Byolock]

Sorry i tried to redirect the output to a file for easier transfer, but that seemed to ignore some output. Heres the copy from the shell:

root@iobroker:/opt/iobroker# DEBUG=hap* node /opt/iobroker/node_modules/iobroker.homekit-controller/build/main.js 0 --debug --logs
2023-11-06 14:05:19.638  - debug: homekit-controller.0 (1391658) Redis Objects: Use Redis connection: 127.0.0.1:9001
2023-11-06 14:05:19.645  - debug: homekit-controller.0 (1391658) Objects client ready ... initialize now
2023-11-06 14:05:19.646  - debug: homekit-controller.0 (1391658) Objects create System PubSub Client
2023-11-06 14:05:19.646  - debug: homekit-controller.0 (1391658) Objects create User PubSub Client
2023-11-06 14:05:19.654  - debug: homekit-controller.0 (1391658) Objects client initialize lua scripts
2023-11-06 14:05:19.656  - debug: homekit-controller.0 (1391658) Objects connected to redis: 127.0.0.1:9001
2023-11-06 14:05:19.661  - debug: homekit-controller.0 (1391658) Redis States: Use Redis connection: 127.0.0.1:9000
2023-11-06 14:05:19.663  - debug: homekit-controller.0 (1391658) States create System PubSub Client
2023-11-06 14:05:19.663  - debug: homekit-controller.0 (1391658) States create User PubSub Client
2023-11-06 14:05:19.710  - debug: homekit-controller.0 (1391658) States connected to redis: 127.0.0.1:9000
2023-11-06 14:05:19.720  - debug: homekit-controller.0 (1391658) Plugin sentry Initialize Plugin (enabled=true)
2023-11-06 14:05:19.766  - error: homekit-controller.0 (1391658) adapter disabled
2023-11-06 14:05:19.830  - info: homekit-controller.0 (1391658) starting. Version 0.5.8 in /opt/iobroker/node_modules/iobroker.homekit-controller, node: v18.17.1, js-controller: 5.0.12
2023-11-06 14:05:42.887  - debug: homekit-controller.0 (1391658) Discovered IP device up: D0:EA:D3:70:E7:F7/Presence-Sensor-FP2-BCEA
2023-11-06 14:05:42.888  - debug: homekit-controller.0 (1391658) IP-D0:EA:D3:70:E7:F7 Discovered IP device: {"name":"Presence-Sensor-FP2-BCEA","address":"192.168.1.35","port":49269,"c#":2,"ff":2,"id":"D0:EA:D3:70:E7:F7","md":"PS-S02D","pv":"1.1","s#":1,"sf":1,"ci":10,"availableToPair":true}
2023-11-06 14:05:42.888  - info: homekit-controller.0 (1391658) IP-D0:EA:D3:70:E7:F7 (Presence-Sensor-FP2-BCEA) found without pairing data but available for pairing: Create basic objects
2023-11-06 14:05:42.888  - debug: homekit-controller.0 (1391658) Service: {"name":"Presence-Sensor-FP2-BCEA","address":"192.168.1.35","port":49269,"c#":2,"ff":2,"id":"D0:EA:D3:70:E7:F7","md":"PS-S02D","pv":"1.1","s#":1,"sf":1,"ci":10,"availableToPair":true}
2023-11-06 14:05:42.897  - debug: homekit-controller.0 (1391658) state homekit-controller.0.IP-D0:EA:D3:70:E7:F7.info.connectionType changed: IP (ack = true)
2023-11-06 14:05:42.939  - debug: homekit-controller.0 (1391658) state homekit-controller.0.IP-D0:EA:D3:70:E7:F7.info.connectionType changed: IP (ack = true)
2023-11-06 14:05:42.982  - debug: homekit-controller.0 (1391658) state homekit-controller.0.IP-D0:EA:D3:70:E7:F7.info.id changed: D0:EA:D3:70:E7:F7 (ack = true)
2023-11-06 14:05:43.026  - debug: homekit-controller.0 (1391658) state homekit-controller.0.IP-D0:EA:D3:70:E7:F7.info.address changed: 192.168.1.35 (ack = true)
2023-11-06 14:05:43.072  - debug: homekit-controller.0 (1391658) state homekit-controller.0.IP-D0:EA:D3:70:E7:F7.info.connected changed: false (ack = true)
2023-11-06 14:05:43.124  - debug: homekit-controller.0 (1391658) state homekit-controller.0.IP-D0:EA:D3:70:E7:F7.admin.isPaired changed: false (ack = true)
2023-11-06 14:05:43.176  - debug: homekit-controller.0 (1391658) state homekit-controller.0.IP-D0:EA:D3:70:E7:F7.info.lastDiscovered changed: 1699275942889 (ack = true)
2023-11-06 14:05:43.227  - debug: homekit-controller.0 (1391658) state homekit-controller.0.IP-D0:EA:D3:70:E7:F7.admin.pairWithPin changed:  (ack = true)
2023-11-06 14:05:43.276  - debug: homekit-controller.0 (1391658) state homekit-controller.0.IP-D0:EA:D3:70:E7:F7.admin.identify changed: false (ack = true)
2023-11-06 14:06:18.633  - debug: homekit-controller.0 (1391658) Message getDiscoveredDevices received: {"command":"getDiscoveredDevices","message":null,"from":"system.adapter.admin.0","callback":{"message":null,"id":251,"ack":false,"time":1699275978630},"_id":24048605})
2023-11-06 14:06:18.634  - debug: homekit-controller.0 (1391658) Response to Command getDiscoveredDevices: {"success":true,"error":false,"devices":[{"id":"IP-D0:EA:D3:70:E7:F7","serviceType":"IP","connected":false,"discovered":true,"availableToPair":true,"discoveredName":"Presence-Sensor-FP2-BCEA","discoveredCategory":"Sensor","pairedWithThisInstance":false}]}
2023-11-06 14:06:45.453  - debug: homekit-controller.0 (1391658) Message pairDevice received: {"command":"pairDevice","message":{"deviceId":"IP-D0:EA:D3:70:E7:F7","pin":"980-72-531"},"from":"system.adapter.admin.0","callback":{"message":{"deviceId":"IP-D0:EA:D3:70:E7:F7","pin":"980-72-531"},"id":252,"ack":false,"time":1699276005452},"_id":24048606})
2023-11-06 14:06:45.455  - info: homekit-controller.0 (1391658) Use PairMethod 0 to pair IP-D0:EA:D3:70:E7:F7
2023-11-06 14:06:45.456  - debug: homekit-controller.0 (1391658) IP-D0:EA:D3:70:E7:F7 Start Homekit Device Client initialization on 192.168.1.35:49269
  hap-controller:tlv Add 1 bytes for tag 6: 01 +0ms
  hap-controller:tlv Add 1 bytes for tag 0: 00 +1ms
  hap-controller:http-connection 192.168.1.35:49269 POST /pair-setup 060101000100 (application/pairing+tlv8) +0ms
2023-11-06 14:15:38.414  - debug: homekit-controller.0 (1391658) Discovered IP device down: D0:EA:D3:70:E7:F7/Presence-Sensor-FP2-BCEA

[Apollon77]

Ok if this is the fill log then the library sends a pair setup request but do not get any answer from the device and 7 mins later the devcie reported to be offline. So I would not see anything that the adapter/library cvan do different here. Did you tried to repower the aquara device?

[Byolock]

Yeah I did that. I also reinstalled the adapter, rebooted my iobroker and did a factory reset on the device. Nothing changed. Interesting behaviour I just noticed : the second i rebooted my iobroker the FP2 sensor started blinking its LED Signaling "loss to the hub", as if the sensor "thinks" its already attached to the homekit hub. That makes no sense though, because it's immediatly ready to pair again.

I think I'm out of luck here, i don't have any genuine apple homekit hub. Maybe im going to try Home Assistant to pair it. But probably I've to send it back.

[Apollon77]

Sorry that I could not help further for now

[Byolock]

So I finally got around installing Home Assistant and pairing it with it's home kit integration worked fine. The differences do start already before I enter the pairing code. With the IOBroker adapter the device does not react at all to a pairing request, with Home Assistant the Blue LED starts signaling immediately after pairing is started before even entering the pairing code. Both IOBroker and Home Assistant are installed identically : On a LXC container on top of a Proxmox Hypervisor inside a docker container with network set to "host". I installed the Hass adapter and as im seeing the FP2 states now in iobroker I think I can do with this workaround.

If you want to do further troubleshooting with logs from home assistant or anything feel free to reach out. Otherwise you should probably close this issue for now.

[Apollon77]

In fact it would be awesome to understand the difference. So yes if there are protocol level logs from homeassistant that I could compare to the JavaScript library one that might help to understand what's the difference. Formally we implemented the specs

[Apollon77]

@Byolock Do you think there could be comparing logs?