ioBroker.homekit-controller icon indicating copy to clipboard operation
ioBroker.homekit-controller copied to clipboard

Published 20 hours ago • verified publisher icon Apollon77

unable to pair Aqara FP2

Open Byolock opened this issue 1 year ago • 11 comments

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.

Byolock avatar Nov 04 '23 09:11 Byolock