Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

unable to pair Aqara FP2 #307

Open
Byolock opened this issue Nov 4, 2023 · 12 comments
Open

unable to pair Aqara FP2 #307

Byolock opened this issue Nov 4, 2023 · 12 comments
Labels
question Further information is requested

Comments

@Byolock
Copy link

Byolock commented Nov 4, 2023

Describe the bug
After the FP2 device is detected and I enter the pass code nothing happens. It does not pair successfully.

To Reproduce
Steps to reproduce the behavior:

  1. Go to 'Instances'
  2. Click on 'homekit-controller'
  3. Go to 'Devices'
  4. Find the FP2 Device
  5. Enter Pairing Code
  6. No Pairing occurs

Expected behavior
Device should be paired after a few seconds.

Screenshots & Logfiles

Logfile 
2023-11-04 10:26:20.453  - info: host.iobroker stopInstance system.adapter.homekit-controller.0 (force=false, process=true)
--
2023-11-04 10:26:20.456  - silly:  homekit-controller.0 (1234331) States system redis pmessage  system.adapter.homekit-controller.0.sigKill/system.adapter.homekit-controller.0.sigKill:{"val":-1,"ack":false,"ts":1699089980455,"q":0,"from":"system.host.iobroker","lc":1699089980455}
2023-11-04 10:26:20.457  - info: homekit-controller.0 (1234331) Got terminate signal TERMINATE_YOURSELF
2023-11-04 10:26:20.461  - info: homekit-controller.0 (1234331) terminating
2023-11-04 10:26:20.462  - debug: homekit-controller.0 (1234331) Plugin sentry destroyed
2023-11-04 10:26:20.462  - info: homekit-controller.0 (1234331) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
2023-11-04 10:26:20.498  - info: host.iobroker stopInstance system.adapter.homekit-controller.0 send kill signal
2023-11-04 10:26:20.963  - info: homekit-controller.0 (1234331) terminating
2023-11-04 10:26:20.978  - info: host.iobroker instance system.adapter.homekit-controller.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
2023-11-04 10:26:23.530  - info: host.iobroker instance system.adapter.homekit-controller.0 started with pid 1234370
2023-11-04 10:26:23.782  - debug: homekit-controller.0 (1234370) Redis Objects: Use Redis connection: 127.0.0.1:9001
2023-11-04 10:26:23.790  - debug: homekit-controller.0 (1234370) Objects client ready ... initialize now
2023-11-04 10:26:23.791  - debug: homekit-controller.0 (1234370) Objects create System PubSub Client
2023-11-04 10:26:23.791  - debug: homekit-controller.0 (1234370) Objects create User PubSub Client
2023-11-04 10:26:23.795  - debug: homekit-controller.0 (1234370) Objects client initialize lua scripts
2023-11-04 10:26:23.796  - debug: homekit-controller.0 (1234370) Objects connected to redis: 127.0.0.1:9001
2023-11-04 10:26:23.797  - silly: homekit-controller.0 (1234370) redis psubscribe cfg.o.system.user.*
2023-11-04 10:26:23.799  - silly: homekit-controller.0 (1234370) redis psubscribe cfg.o.enum.*
2023-11-04 10:26:23.799  - silly: homekit-controller.0 (1234370) objectDB connected
2023-11-04 10:26:23.800  - debug: homekit-controller.0 (1234370) Redis States: Use Redis connection: 127.0.0.1:9000
2023-11-04 10:26:23.801  - debug: homekit-controller.0 (1234370) States create System PubSub Client
2023-11-04 10:26:23.802  - debug: homekit-controller.0 (1234370) States create User PubSub Client
2023-11-04 10:26:23.847  - debug: homekit-controller.0 (1234370) States connected to redis: 127.0.0.1:9000
2023-11-04 10:26:23.849  - silly: homekit-controller.0 (1234370) statesDB connected
2023-11-04 10:26:23.872  - debug: homekit-controller.0 (1234370) Plugin sentry Initialize Plugin (enabled=true)
2023-11-04 10:26:23.992  - info:  homekit-controller.0 (1234370) starting. Version 0.5.8 in  /opt/iobroker/node_modules/iobroker.homekit-controller, node: v18.17.1,  js-controller: 5.0.12
2023-11-04 10:26:24.010  - silly:  homekit-controller.0 (1234370) States system redis pmessage  system.adapter.homekit-controller.0.logLevel/system.adapter.homekit-controller.0.logLevel:{"val":"silly","ack":true,"ts":1699089983999,"q":0,"from":"system.adapter.homekit-controller.0","lc":1699089158114}
2023-11-04 10:26:24.050  - debug: homekit-controller.0 (1234370) Init 1 known devices without discovery ...
2023-11-04 10:26:24.051  - debug: homekit-controller.0 (1234370) Init IP-D0:EA:D3:70:E7:F7 as known device
2023-11-04 10:26:24.053  - info:  homekit-controller.0 (1234370) IP-D0:EA:D3:70:E7:F7  (Presence-Sensor-FP2-BCEA) found without pairing data but available for  pairing: Create basic objects
2023-11-04 10:26:24.055  - debug:  homekit-controller.0 (1234370) Service:  {"name":"Presence-Sensor-FP2-BCEA","address":"192.168.1.35","port":50596,"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-04 10:26:24.443  - debug: homekit-controller.0 (1234370) Discovered IP device up: D0:EA:D3:70:E7:F7/Presence-Sensor-FP2-BCEA
2023-11-04 10:26:24.443  - debug: homekit-controller.0 (1234370) IP-D0:EA:D3:70:E7:F7 Discovery device update, unchanged config-number, ignore
2023-11-04 10:26:24.444  - debug:  homekit-controller.0 (1234370) IP-D0:EA:D3:70:E7:F7 Device Discovery  Update - reinitialize device (config changed=false):  {"name":"Presence-Sensor-FP2-BCEA","address":"192.168.1.35","port":50596,"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-04 10:26:24.444  - info:  homekit-controller.0 (1234370) IP-D0:EA:D3:70:E7:F7  (Presence-Sensor-FP2-BCEA) found without pairing data but available for  pairing: Create basic objects
2023-11-04 10:26:24.445  - debug:  homekit-controller.0 (1234370) Service:  {"name":"Presence-Sensor-FP2-BCEA","address":"192.168.1.35","port":50596,"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-04 10:26:24.455  - silly:  homekit-controller.0 (1234370) States user redis pmessage  homekit-controller.0.*/homekit-controller.0.IP-D0:EA:D3:70:E7:F7.info.connectionType:{"val":"IP","ack":true,"ts":1699089984454,"q":0,"from":"system.adapter.homekit-controller.0","user":"system.user.admin","lc":1699088918010}
2023-11-04 10:26:24.456  - debug: homekit-controller.0 (1234370) state homekit-controller.0.IP-D0:EA:D3:70:E7:F7.info.connectionType changed: IP (ack = true)
2023-11-04 10:26:24.499  - silly:  homekit-controller.0 (1234370) States user redis pmessage  homekit-controller.0.*/homekit-controller.0.IP-D0:EA:D3:70:E7:F7.info.id:{"val":"D0:EA:D3:70:E7:F7","ack":true,"ts":1699089984498,"q":0,"from":"system.adapter.homekit-controller.0","user":"system.user.admin","lc":1699088918012}
2023-11-04 10:26:24.501  - debug: homekit-controller.0 (1234370) state homekit-controller.0.IP-D0:EA:D3:70:E7:F7.info.id changed: D0:EA:D3:70:E7:F7 (ack = true)
2023-11-04 10:26:24.551  - silly:  homekit-controller.0 (1234370) States user redis pmessage  homekit-controller.0.*/homekit-controller.0.IP-D0:EA:D3:70:E7:F7.info.address:{"val":"192.168.1.35","ack":true,"ts":1699089984550,"q":0,"from":"system.adapter.homekit-controller.0","user":"system.user.admin","lc":1699088918013}
2023-11-04 10:26:24.553  - debug: homekit-controller.0 (1234370) state homekit-controller.0.IP-D0:EA:D3:70:E7:F7.info.address changed: 192.168.1.35 (ack = true)
2023-11-04 10:26:24.603  - silly:  homekit-controller.0 (1234370) States user redis pmessage  homekit-controller.0.*/homekit-controller.0.IP-D0:EA:D3:70:E7:F7.info.connected:{"val":false,"ack":true,"ts":1699089984602,"q":0,"from":"system.adapter.homekit-controller.0","user":"system.user.admin","lc":1699088918015}
2023-11-04 10:26:24.604  - debug: homekit-controller.0 (1234370) state homekit-controller.0.IP-D0:EA:D3:70:E7:F7.info.connected changed: false (ack = true)
2023-11-04 10:26:24.656  - silly:  homekit-controller.0 (1234370) States user redis pmessage  homekit-controller.0.*/homekit-controller.0.IP-D0:EA:D3:70:E7:F7.admin.isPaired:{"val":false,"ack":true,"ts":1699089984654,"q":0,"from":"system.adapter.homekit-controller.0","user":"system.user.admin","lc":1699088918017}
2023-11-04 10:26:24.657  - debug: homekit-controller.0 (1234370) state homekit-controller.0.IP-D0:EA:D3:70:E7:F7.admin.isPaired changed: false (ack = true)
2023-11-04 10:26:24.708  - silly:  homekit-controller.0 (1234370) States user redis pmessage  homekit-controller.0.*/homekit-controller.0.IP-D0:EA:D3:70:E7:F7.info.lastDiscovered:{"val":1699089984445,"ack":true,"ts":1699089984706,"q":0,"from":"system.adapter.homekit-controller.0","user":"system.user.admin","lc":1699089984706}
2023-11-04 10:26:24.709  - debug:  homekit-controller.0 (1234370) state  homekit-controller.0.IP-D0:EA:D3:70:E7:F7.info.lastDiscovered changed:  1699089984445 (ack = true)
2023-11-04 10:26:57.710  - silly:  homekit-controller.0 (1234370) 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":129,"ack":false,"time":1699090017710},"_id":24048480}
2023-11-04 10:26:57.711  - debug:  homekit-controller.0 (1234370) Message getDiscoveredDevices received:  {"command":"getDiscoveredDevices","message":null,"from":"system.adapter.admin.0","callback":{"message":null,"id":129,"ack":false,"time":1699090017710},"_id":24048480})
2023-11-04 10:26:57.711  - debug:  homekit-controller.0 (1234370) 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-04 10:26:57.711  - silly:  homekit-controller.0 (1234370) sendTo "getDiscoveredDevices" to  system.adapter.admin.0 from system.adapter.homekit-controller.0
2023-11-04 10:27:00.455  - silly:  homekit-controller.0 (1234370) 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":130,"ack":false,"time":1699090020455},"_id":24048481}
2023-11-04 10:27:00.456  - debug:  homekit-controller.0 (1234370) Message getDiscoveredDevices received:  {"command":"getDiscoveredDevices","message":null,"from":"system.adapter.admin.0","callback":{"message":null,"id":130,"ack":false,"time":1699090020455},"_id":24048481})
2023-11-04 10:27:00.456  - debug:  homekit-controller.0 (1234370) 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-04 10:27:00.456  - silly:  homekit-controller.0 (1234370) sendTo "getDiscoveredDevices" to  system.adapter.admin.0 from system.adapter.homekit-controller.0
2023-11-04 10:27:09.291  - silly:  homekit-controller.0 (1234370) States system redis pmessage  io.messagebox.system.adapter.homekit-controller.0/io.messagebox.system.adapter.homekit-controller.0:{"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":131,"ack":false,"time":1699090029290},"_id":24048482}
2023-11-04 10:27:09.291  - debug:  homekit-controller.0 (1234370) 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":131,"ack":false,"time":1699090029290},"_id":24048482})
2023-11-04 10:27:09.291  - info: homekit-controller.0 (1234370) Use PairMethod 0 to pair IP-D0:EA:D3:70:E7:F7
2023-11-04 10:27:09.291  - debug: homekit-controller.0 (1234370) IP-D0:EA:D3:70:E7:F7 Start Homekit Device Client initialization on 192.168.1.35:50596

Versions:

  • Adapter version: v0.5.8
  • JS-Controller version: 5.0.12
  • Node version: v18.17.1
  • Operating system: debian 10

Additional context
A few Minutes after the Pairing attempt the fp2 has its led blinking blue, signaling loss of connection from the hub. The Aqara app has a notification saying "network abnormal", but reaches the device just fine. The notification disappears after clicking on the "try again" text inside that notification.
@Apollon77
Copy link
Owner

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

@Apollon77 Apollon77 added the question Further information is requested label Nov 4, 2023
@Byolock
Copy link
Author

Byolock commented Nov 6, 2023

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
Copy link
Owner

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

@Byolock
Copy link
Author

Byolock commented Nov 6, 2023

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
Copy link
Owner

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
Copy link
Author

Byolock commented Nov 6, 2023

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
Copy link
Owner

Sorry that I could not help further for now

@Byolock
Copy link
Author

Byolock commented Nov 14, 2023 •
edited
Loading

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
Copy link
Owner

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
Copy link
Owner

@Byolock Do you think there could be comparing logs?

@stale Stale
Copy link

stale bot commented Mar 17, 2024

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs within the next 7 days. Please check if the issue is still relevant in the most current version of the adapter and tell us. Also check that all relevant details, logs and reproduction steps are included and update them if needed. Thank you for your contributions.
Dieses Problem wurde automatisch als veraltet markiert, da es in letzter Zeit keine Aktivitäten gab. Es wird geschlossen, wenn nicht innerhalb der nächsten 7 Tage weitere Aktivitäten stattfinden. Bitte überprüft, ob das Problem auch in der aktuellsten Version des Adapters noch relevant ist, und teilt uns dies mit. Überprüft auch, ob alle relevanten Details, Logs und Reproduktionsschritte enthalten sind bzw. aktualisiert diese. Vielen Dank für Eure Unterstützung.

@ticaki
Copy link

ticaki commented Jan 11, 2025

I use 2 FP2 and I was able to integrate both of them stably. They have been running for over 1 month now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
question Further information is requested
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@Apollon77 @Byolock @ticaki