Hi,
Since the Matter Server upgraded to v9.0.0 and above, we’ve noticed an issue where the Aqara FP300 Presence Sensor will show online when the Matter Server starts, for 15 minutes and will then go offline.
However, the device is still online and active in Apple Home.
The device was added in Apple Home first, then into Home Assistant. It is connected to the primary IKEA Thread boarder router, with 3 other boarder routers in the network.
Most other devices (all IKEA temperature and air quality sensors) stay connected. Sometimes the odd one will drop off too.
This is “resolved” by rebooting the server or restarting the Matter Server app.
Then, 15 minutes later it goes again. This is the log when filtering for the device ID:
2026-08-23 20:29:47.459 INFO CaseClient @1:b8•90fd New session with @1:b8 4↔2 address: udp://[fd30:2813:8eba:1:9e90:ab4:a53e:d275]:5540 fabric: 41c417db98d0fc26 (#1) SII: 6s SAI: 1.1s SAT: 500ms DMRev: 18 IMRev: 12 spec: 0x1040100 maxPaths: 5 CATs:
2026-08-23 20:29:47.459 INFO ClientNode server-2-134b.@1:b8 is online
2026-08-23 20:29:47.461 INFO IpServiceStatus @1:b8 Connected
2026-08-23 20:29:47.470 INFO ClientInteraction Read » @1:b8•90fd⇵38d3 bootstrap attributes: 1 events: 1
2026-08-23 20:29:48.800 INFO ClientInteraction Read « @1:b8•90fd⇵38d3 2↔2 attributes: 50 events: 0
2026-08-23 20:29:48.802 INFO ClientInteraction Subscribe » @1:b8•90fd⇵38d5 min: 0 max: 5m attributes: 1 events: 1
2026-08-23 20:29:54.971 INFO ClientInteraction Subscription successful « @1:b8•90fd⇵38d5 2↔3+1 id: 66491bcc interval: 5m timeout: 5m 38s
2026-08-23 20:29:54.971 NOTICE Controller~ndHandler Node @1:b8 availability changed to true (state: Connected)
2026-08-23 20:29:54.972 INFO WebSocketC~erHandler [0] Node @1:b8 availability changed to true
2026-08-23 20:29:54.972 INFO WebSocketC~erHandler [1] Node @1:b8 availability changed to true
2026-08-23 20:37:06.942 INFO ClientInteraction Read » @1:b8•90fd⇵38ec attributes: 3
2026-08-23 20:37:10.691 INFO ClientInteraction Read « @1:b8•90fd⇵38ec attributes: 3 events: 0
2026-08-23 20:38:30.969 INFO InteractionMessenger @1:b8•90fd⇵b6b3 Error sending success after final data report chunk [peer-unresponsive] Peer is no longer responding to active session (timed out after 1m 20s)
2026-08-23 20:40:18.318 INFO ClientInteraction Read » @1:b8•90fd⇵38ed attributes: 1
2026-08-23 20:40:18.418 INFO ClientInteraction Read » @1:b8•90fd⇵38ee attributes: 1
2026-08-23 20:41:50.006 INFO ClientNode server-2-134b.@1:b8 is offline
2026-08-23 20:42:40.984 INFO IpServiceStatus @1:b8 Resolving (address is unreachable)
2026-08-23 20:42:40.986 INFO PeerConnection @1:b8•unsecured#d715ec26dcacf800⇵38ef ip://[fd30:2813:8eba:1:9e90:ab4:a53e:d275]:5540 Connecting addr #: 1 attempt #: 1 connect time: 2ms addr time: 0 thread:25:connect
2026-08-23 20:42:49.378 INFO ClientSubscription Subscription 66491bcc to peer @1:b8 timed out after 5m 38s
2026-08-23 20:42:49.378 INFO ClientSubscription Replacing subscription to @1:b8 after loss
2026-08-23 20:42:49.379 INFO ClientSubscription Failed to probe reachability of peer @1:b8, resubscribe with new session
2026-08-23 20:42:57.592 INFO Session @1:b8•90fd Session ended
2026-08-23 20:44:50.009 INFO WebSocketC~erHandler [0] Node @1:b8 availability changed to false
2026-08-23 20:44:50.008 WARN Controller~ndHandler Node @1:b8 offline grace period expired, marking unavailable
2026-08-23 20:44:50.009 INFO WebSocketC~erHandler [6] Node @1:b8 availability changed to false
Has anyone else faced this issue and managed to resolve it? Or could it be an issue with the Matter Server?
HA Version Details:
Core 2026.8.3
Supervisor 2026.07.5
Operating System 18.2
Frontend 20260729.7
Matter Server Version: 9.2.0
Logs without filtering from the point of the device becoming marked as unavailable:
2026-08-23 20:41:50.006 INFO ClientNode server-2-134b.@1:b8 is offline
2026-08-23 20:41:50.008 ERROR WebSocketC~erHandler [0] WebSocket error response (read_attribute) 1e04f198dab2496ab0a9713a07cf3e1e [peer-unresponsive] Peer is no longer responding to active session (timed out after 1m 31s)
at MessageExchange.#sentMessageAckFailure (/app/node_modules/@matter/protocol/src/protocol/MessageExchange.ts:748:29)
at MessageExchange.#retransmitMessage (/app/node_modules/@matter/protocol/src/protocol/MessageExchange.ts:908:22)
at StandardTimer.callback (/app/node_modules/@matter/protocol/src/protocol/MessageExchange.ts:960:18)
at Timeout.<anonymous> (/app/node_modules/@matter/general/src/time/StandardTime.ts:122:18)
at listOnTimeout (node:internal/timers:635:17)
at process.processTimers (node:internal/timers:571:7)
2026-08-23 20:41:50.014 ERROR WebSocketC~erHandler [0] WebSocket error response (read_attribute) d0c0abc0909c48caa14c806e0043a7a5 [closed] Channel is closed
at DataReadQueue.read (/app/node_modules/@matter/general/src/util/DataReadQueue.ts:23:19)
at MessageExchange.#nextMessage (/app/node_modules/@matter/protocol/src/protocol/MessageExchange.ts:843:42)
at MessageExchange.nextMessage (/app/node_modules/@matter/protocol/src/protocol/MessageExchange.ts:808:31)
at InteractionClientMessenger.#nextMessage (/app/node_modules/@matter/protocol/src/interaction/InteractionMessenger.ts:162:45)
at InteractionClientMessenger.anyNextMessage (/app/node_modules/@matter/protocol/src/interaction/InteractionMessenger.ts:158:21)
at InteractionClientMessenger.waitFor (/app/node_modules/@matter/protocol/src/interaction/InteractionMessenger.ts:850:36)
at InteractionClientMessenger.readDataReports (/app/node_modules/@matter/protocol/src/interaction/InteractionMessenger.ts:875:50)
at readDataReports.next (<anonymous>)
at ClientInteraction.read (/app/node_modules/@matter/protocol/src/action/client/ClientInteraction.ts:265:26)
at async ClientStructure.mutate (/app/node_modules/@matter/node/src/node/client/ClientStructure.ts:258:30)
Caused by: [peer-unresponsive] Peer is no longer responding to active session (timed out after 1m 31s)
2026-08-23 20:41:50.773 INFO ClientEventEmitter Received event electricalEnergyMeasurement.cumulativeEnergyMeasured on server-2-134b.@1:9e.ep2 energyImported: { energy: 14331869, startTimestamp: 946684806, endTimestamp: 956256978, startSystime: 6964, endSystime: 9572179135 } energyExported: { energy: 0 }
2026-08-23 20:41:53.358 INFO ClientEventEmitter Received event electricalEnergyMeasurement.cumulativeEnergyMeasured on server-2-134b.@1:9d.ep2 energyImported: { energy: 2966853, startTimestamp: 946684800, endTimestamp: 956715193, startSystime: 1768, endSystime: 10030394755 } energyExported: { energy: 0 }
2026-08-23 20:42:23.601 INFO WebSocketC~erHandler [3] WebSocket connection closed
2026-08-23 20:42:23.970 INFO WebSocketC~erHandler [4] WebSocket connection established
2026-08-23 20:42:23.977 INFO WebSocketC~erHandler WebSocket server start_listening
2026-08-23 20:42:23.977 INFO WebSocketC~erHandler WebSocket server start_listening. Returned 23 nodes
2026-08-23 20:42:40.984 INFO IpServiceStatus @1:b8 Resolving (address is unreachable)
2026-08-23 20:42:40.986 INFO PeerConnection @1:b8•unsecured#d715ec26dcacf800⇵38ef ip://[fd30:2813:8eba:1:9e90:ab4:a53e:d275]:5540 Connecting addr #: 1 attempt #: 1 connect time: 2ms addr time: 0 thread:25:connect
2026-08-23 20:42:42.187 INFO ClientEventEmitter Received event electricalEnergyMeasurement.cumulativeEnergyMeasured on server-2-134b.@1:9c.ep2 energyImported: { energy: 10342015, startTimestamp: 946684800, endTimestamp: 956715613, startSystime: 1821, endSystime: 10030814106 } energyExported: { energy: 0 }
2026-08-23 20:42:49.378 INFO ClientSubscription Subscription 66491bcc to peer @1:b8 timed out after 5m 38s
2026-08-23 20:42:49.378 INFO ClientSubscription Replacing subscription to @1:b8 after loss
2026-08-23 20:42:49.379 INFO ClientSubscription Failed to probe reachability of peer @1:b8, resubscribe with new session
2026-08-23 20:42:50.769 INFO ClientEventEmitter Received event electricalEnergyMeasurement.cumulativeEnergyMeasured on server-2-134b.@1:9e.ep2 energyImported: { energy: 14331869, startTimestamp: 946684806, endTimestamp: 956257038, startSystime: 6964, endSystime: 9572239135 } energyExported: { energy: 0 }
2026-08-23 20:42:53.357 INFO ClientEventEmitter Received event electricalEnergyMeasurement.cumulativeEnergyMeasured on server-2-134b.@1:9d.ep2 energyImported: { energy: 2966853, startTimestamp: 946684800, endTimestamp: 956715253, startSystime: 1768, endSystime: 10030454755 } energyExported: { energy: 0 }
2026-08-23 20:42:57.592 INFO Session @1:b8•90fd Session ended
2026-08-23 20:43:02.177 INFO WebSocketC~erHandler [4] WebSocket connection closed
2026-08-23 20:43:02.516 INFO WebSocketC~erHandler [5] WebSocket connection established
2026-08-23 20:43:02.535 INFO WebSocketC~erHandler WebSocket server start_listening
2026-08-23 20:43:02.536 INFO WebSocketC~erHandler WebSocket server start_listening. Returned 23 nodes
2026-08-23 20:43:42.174 INFO ClientEventEmitter Received event electricalEnergyMeasurement.cumulativeEnergyMeasured on server-2-134b.@1:9c.ep2 energyImported: { energy: 10342073, startTimestamp: 946684800, endTimestamp: 956715673, startSystime: 1821, endSystime: 10030874106 } energyExported: { energy: 0 }
2026-08-23 20:43:50.961 INFO ClientEventEmitter Received event electricalEnergyMeasurement.cumulativeEnergyMeasured on server-2-134b.@1:9e.ep2 energyImported: { energy: 14331869, startTimestamp: 946684806, endTimestamp: 956257098, startSystime: 6964, endSystime: 9572299135 } energyExported: { energy: 0 }
2026-08-23 20:43:53.361 INFO ClientEventEmitter Received event electricalEnergyMeasurement.cumulativeEnergyMeasured on server-2-134b.@1:9d.ep2 energyImported: { energy: 2966853, startTimestamp: 946684800, endTimestamp: 956715313, startSystime: 1768, endSystime: 10030514755 } energyExported: { energy: 0 }
2026-08-23 20:43:57.236 INFO WebSocketC~erHandler [5] WebSocket connection closed
2026-08-23 20:43:57.515 INFO WebSocketC~erHandler [6] WebSocket connection established
2026-08-23 20:43:57.526 INFO WebSocketC~erHandler WebSocket server start_listening
2026-08-23 20:43:57.526 INFO WebSocketC~erHandler WebSocket server start_listening. Returned 23 nodes
2026-08-23 20:44:02.894 INFO ThreadDiag~csService no source xp=694DDEB4B1A84AC8 -> partial(no_credentials)
2026-08-23 20:44:02.894 INFO ThreadDiag~csService no source xp=29BCB4CF22192D08 -> partial(no_credentials)
2026-08-23 20:44:10.989 ERROR WebSocketC~erHandler [0] WebSocket error response (read_attribute) 028a43bea8d943faacd464d2d4d9350a [aborted] Operation aborted
at abort.throwIfAborted (/app/node_modules/@matter/general/src/util/Abort.ts:215:21)
at Peer.connect (/app/node_modules/@matter/protocol/src/peer/Peer.ts:454:24)
at runNextTicks (node:internal/process/task_queues:65:5)
at process.processTimers (node:internal/timers:568:9)
at async PeerExchangeProvider.connect (/app/node_modules/@matter/protocol/src/peer/PeerExchangeProvider.ts:59:9)
at async PeerExchangeProvider.initiateExchange (/app/node_modules/@matter/protocol/src/peer/PeerExchangeProvider.ts:83:17)
at async InteractionClientMessenger.create (/app/node_modules/@matter/protocol/src/interaction/InteractionMessenger.ts:925:26)
at async ClientInteraction.#begin (/app/node_modules/@matter/protocol/src/action/client/ClientInteraction.ts:1113:29)
Caused by: [peer-unreachable] Peer has been unreachable for 1m 30s
at abort.timeoutHandler (/app/node_modules/@matter/protocol/src/peer/Peer.ts:447:27)
at abort.timeoutHandler (/app/node_modules/@matter/general/src/util/Abort.ts:102:34)
at StandardTimer.callback (/app/node_modules/@matter/general/src/util/Abort.ts:126:37)
at Timeout.<anonymous> (/app/node_modules/@matter/general/src/time/StandardTime.ts:122:18)
at listOnTimeout (node:internal/timers:635:17)
at process.processTimers (node:internal/timers:571:7)
2026-08-23 20:44:10.991 ERROR WebSocketC~erHandler [0] WebSocket error response (read_attribute) 41412d59583a49b2b6db1f658b234011 [aborted] Operation aborted
at abort.throwIfAborted (/app/node_modules/@matter/general/src/util/Abort.ts:215:21)
at Peer.connect (/app/node_modules/@matter/protocol/src/peer/Peer.ts:454:24)
at async PeerExchangeProvider.connect (/app/node_modules/@matter/protocol/src/peer/PeerExchangeProvider.ts:59:9)
at async PeerExchangeProvider.initiateExchange (/app/node_modules/@matter/protocol/src/peer/PeerExchangeProvider.ts:83:17)
at async InteractionClientMessenger.create (/app/node_modules/@matter/protocol/src/interaction/InteractionMessenger.ts:925:26)
at async ClientInteraction.#begin (/app/node_modules/@matter/protocol/src/action/client/ClientInteraction.ts:1113:29)
at async ClientInteraction.read (/app/node_modules/@matter/protocol/src/action/client/ClientInteraction.ts:255:31)
at async ClientStructure.mutate (/app/node_modules/@matter/node/src/node/client/ClientStructure.ts:258:30)
Caused by: [peer-unreachable] Peer has been unreachable for 1m 30s
at abort.timeoutHandler (/app/node_modules/@matter/protocol/src/peer/Peer.ts:447:27)
at abort.timeoutHandler (/app/node_modules/@matter/general/src/util/Abort.ts:102:34)
at StandardTimer.callback (/app/node_modules/@matter/general/src/util/Abort.ts:126:37)
at Timeout.<anonymous> (/app/node_modules/@matter/general/src/time/StandardTime.ts:122:18)
at listOnTimeout (node:internal/timers:635:17)
at process.processTimers (node:internal/timers:571:7)
2026-08-23 20:44:42.171 INFO ClientEventEmitter Received event electricalEnergyMeasurement.cumulativeEnergyMeasured on server-2-134b.@1:9c.ep2 energyImported: { energy: 10342087, startTimestamp: 946684800, endTimestamp: 956715733, startSystime: 1821, endSystime: 10030934106 } energyExported: { energy: 0 }
2026-08-23 20:44:50.009 INFO WebSocketC~erHandler [0] Node @1:b8 availability changed to false
2026-08-23 20:44:50.008 WARN Controller~ndHandler Node @1:b8 offline grace period expired, marking unavailable
2026-08-23 20:44:50.009 INFO WebSocketC~erHandler [6] Node @1:b8 availability changed to false