Just confirming I seem to run into the same problem. My thread border router is an apple tv/homepods. I can connect the Lafaer sensor to Apple’s Home and then pair the same sensor to Home Assistant by putting it in pair mode in Apple Home (getting the pair code from apple home). This works perfectly fine, I can also make the sensor available to Homey via Home Assistant community app.
But if I try with a new sensor to do the same, first Apple home → pair mode → connect to Homey it sees the sensor, it starts to configure it. It even puts it back to normal mode. And then it starts to try and find it and it errors out. Same if I first start with Homey and not connect the sensor to Apple at all. Same process same error.
Running Homey SHS on Mac Mini, host mode. (using homey app on iphone btw).
Homey [log][ManagerCloud] Proxy POST /api/manager/drivers/pairsession/a6a43501-a663-4fec-b869-c2bbe5d40432/heartbeat
Server HTTP POST /manager/drivers/pairsession/a6a43501-a663-4fec-b869-c2bbe5d40432/heartbeat
Server HTTP POST /manager/drivers/pairsession/a6a43501-a663-4fec-b869-c2bbe5d40432/heartbeat → Success 204
Homey [log][ManagerCloud] Proxy POST /api/manager/drivers/pairsession/a6a43501-a663-4fec-b869-c2bbe5d40432/heartbeat
Server HTTP POST /manager/drivers/pairsession/a6a43501-a663-4fec-b869-c2bbe5d40432/heartbeat
Server HTTP POST /manager/drivers/pairsession/a6a43501-a663-4fec-b869-c2bbe5d40432/heartbeat → Success 204
Homey [log][ManagerCloud] Proxy POST /api/manager/drivers/pairsession/a6a43501-a663-4fec-b869-c2bbe5d40432/heartbeat
Server HTTP POST /manager/drivers/pairsession/a6a43501-a663-4fec-b869-c2bbe5d40432/heartbeat
Server HTTP POST /manager/drivers/pairsession/a6a43501-a663-4fec-b869-c2bbe5d40432/heartbeat → Success 204
Homey [log][ManagerCloud] Proxy POST /api/manager/drivers/pairsession/a6a43501-a663-4fec-b869-c2bbe5d40432/heartbeat
Server HTTP POST /manager/drivers/pairsession/a6a43501-a663-4fec-b869-c2bbe5d40432/heartbeat
Server HTTP POST /manager/drivers/pairsession/a6a43501-a663-4fec-b869-c2bbe5d40432/heartbeat → Success 204
Homey [log][ManagerCloud] Proxy POST /api/manager/drivers/pairsession/a6a43501-a663-4fec-b869-c2bbe5d40432/heartbeat
Server HTTP POST /manager/drivers/pairsession/a6a43501-a663-4fec-b869-c2bbe5d40432/heartbeat
Server HTTP POST /manager/drivers/pairsession/a6a43501-a663-4fec-b869-c2bbe5d40432/heartbeat → Success 204
Homey [log][ManagerCloud] Proxy POST /api/manager/drivers/pairsession/a6a43501-a663-4fec-b869-c2bbe5d40432/heartbeat
Server HTTP POST /manager/drivers/pairsession/a6a43501-a663-4fec-b869-c2bbe5d40432/heartbeat
Server HTTP POST /manager/drivers/pairsession/a6a43501-a663-4fec-b869-c2bbe5d40432/heartbeat → Success 204
Homey [log][ManagerCloud] Proxy POST /api/manager/drivers/pairsession/a6a43501-a663-4fec-b869-c2bbe5d40432/heartbeat
Server HTTP POST /manager/drivers/pairsession/a6a43501-a663-4fec-b869-c2bbe5d40432/heartbeat
Server HTTP POST /manager/drivers/pairsession/a6a43501-a663-4fec-b869-c2bbe5d40432/heartbeat → Success 204
Homey [log][ManagerCloud] Proxy POST /api/manager/drivers/pairsession/a6a43501-a663-4fec-b869-c2bbe5d40432/heartbeat
Server HTTP POST /manager/drivers/pairsession/a6a43501-a663-4fec-b869-c2bbe5d40432/heartbeat
Server HTTP POST /manager/drivers/pairsession/a6a43501-a663-4fec-b869-c2bbe5d40432/heartbeat → Success 204
Homey [log][ManagerCloud] Proxy POST /api/manager/drivers/pairsession/a6a43501-a663-4fec-b869-c2bbe5d40432/heartbeat
Server HTTP POST /manager/drivers/pairsession/a6a43501-a663-4fec-b869-c2bbe5d40432/heartbeat
Server HTTP POST /manager/drivers/pairsession/a6a43501-a663-4fec-b869-c2bbe5d40432/heartbeat → Success 204
Homey [log][ManagerCloud] Proxy POST /api/manager/drivers/pairsession/a6a43501-a663-4fec-b869-c2bbe5d40432/heartbeat
Server HTTP POST /manager/drivers/pairsession/a6a43501-a663-4fec-b869-c2bbe5d40432/heartbeat
Server HTTP POST /manager/drivers/pairsession/a6a43501-a663-4fec-b869-c2bbe5d40432/heartbeat → Success 204
Homey [log][ManagerApiLocal] IO homey:manager:energy:getLiveReport
Homey [log][ManagerApiLocal] IO homey:manager:energy:getLiveReport → Success 200
Homey [log][ManagerApiLocal] IO homey:manager:drivers:emitPairingEvent
Homey [log][ManagerMatterLocal] [Pairing:0x7b548283] Start
Homey [log][ManagerMatterLocal] [Pairing:0x7b548283] Got status update: SEARCHING (-0x01, Unknown)
Homey [log][ManagerMatterLocal] Updating PAA certs
Homey [log][ManagerMatterLocal] DCLs: https://on.dcl.csa-iot.org. Git: false
Homey [log][ManagerApiLocal] IO homey:manager:drivers:emitPairingEvent → Success 204
Homey [log][ManagerMatterLocal] [Pairing:0x7b548283] Starting pairing with payload
Homey [log][ManagerMatterLocal] [Pairing:0x7b548283] Pairing to device…
Homey [log][ManagerApiLocal] IO homey:manager:drivers:emitPairingHeartbeat
Homey [log][ManagerApiLocal] IO homey:manager:drivers:emitPairingHeartbeat → Success 204
Homey [log][ManagerApiLocal] IO homey:manager:drivers:emitPairingHeartbeat
Homey [log][ManagerApiLocal] IO homey:manager:drivers:emitPairingHeartbeat → Success 204
Homey [log][ManagerApiLocal] IO homey:manager:drivers:emitPairingHeartbeat
Homey [log][ManagerApiLocal] IO homey:manager:drivers:emitPairingHeartbeat → Success 204
Homey [log][ManagerApiLocal] IO homey:manager:drivers:emitPairingHeartbeat
Homey [log][ManagerApiLocal] IO homey:manager:drivers:emitPairingHeartbeat → Success 204
Homey [log][ManagerApiLocal] IO homey:manager:drivers:emitPairingHeartbeat
Homey [log][ManagerApiLocal] IO homey:manager:drivers:emitPairingHeartbeat → Success 204
Homey [log][ManagerApiLocal] IO homey:manager:drivers:emitPairingHeartbeat
Homey [log][ManagerApiLocal] IO homey:manager:drivers:emitPairingHeartbeat → Success 204
Homey [err][ManagerMatterLocal] [Pairing:0x7b548283] Finished with error: Could not pair node (Matter code: TIMEOUT (0x0032))
Homey [err][ManagerMatterLocal] [Pairing:0x7b548283] Failed: Could not pair node (Matter code: TIMEOUT (0x0032)) (at stage: unknown)
