I recently bought three FP300 multi-sensors, replacing FP2s. I installed them on Nov 25 and added them as Thread/Matter devices to an Aqara M3 hub as well as Home Assistant.
This worked fine for a while until one by one went offline. Their last online dates are Dec 6 13:04, Dec 8 21:32, Dec 8 21:34. Since then, the Aqara app and HA show them as offline and automations are not working. I‘ve restarted the M3, but that didn‘t help.
I have 42 Matter devices at home, most of them using Thread. All are working fine except the FP300 (including other Aqara products like G410 or E1). They are using plugin version 0.9.4.
I have not yet removed their batteries as they are hard to reach, but I also think that should not be necessary.
I saw that thread, but the symptom here is different. My sensors went fully offline, not stuck in “presence”.
I have a quick update to share. Support suspected this: “When bound to multiple platforms, there may be a situation where the battery drains quickly.” They asked me replace batteries (after a few days, not the advertised 2 years in Thread mode). As I didn’t have CR2450 around, I just removed the batteries and re-inserted them. This brought them back to life and HA reports 100% battery state…
However, not all three sensors behave identically now. 2 out of 3 are “online” both in the Aqara ecosystem as well as in Home Assistant. The third sensor is still “offline” in the Aqara app, but the app happily shows new events in the log as they occur when people enter or leave the room - the sensor is reachable from HA and automations work.
I suspect an issue with the multi fabric implementation. Which is surprising because I have several other Aqara Thread devices connected to multiple fabrics without this issue.
I have the same issue.
My 2 sensors worked in Homeassistant via Matter over Thread and now both of them are off in total.
I’m not able to bring them back into the system without resetting them in total and reincluding them from scratch.
Even removing the batteries does not help (this always helps on my 2 Lafaer LWR01 sensors which are also always off after a view weeks).
It is not a problem of the network. All of my other Matter over Thread sensors and Smart Plugs works well at the same place.
Does anyone found out how to bring the sensors back without re-including them ?
Otherwise I need to throw them away as they are part of my Alarm System
Good to hear I’m not alone. I’ve been writing with Aqara support for months as the sensors keep dropping offline. Like you, I use them as part of an alarm system and I’m really annoyed by the push notifications I get whenever a sensor becomes unavailable.
The solutions offered by Aqara support are not viable, e.g. removing them from all Matter fabrics except Aqara, switching from Thread to Zigbee, or creating a separate Thread network just for the FP300s. It’s been going in circles for very long now…
Like you, only the FP300s experience this kind of connectivity issue. All other Thread devices (including Aqara and non-Aqara products) don’t have that.
As this has thread been moved into the Developer Hub, I hope some Aqara engineer can chime in.
I’m wondering If this issue is related to the thread network or the thread border routers used. If used with HomePods and/or Apple TV I assume they are updated to the latest firmware.
My Thread network is maybe a bit larger than average with 8 border routers (3x Apple TV 4K, 1x ZBT-2, 1x Dirigera, 1x Aqara M3, 2x Aqara G410) and 10 Eve Energy as additional routers. The FP300s are added to multiple fabrics (HA, Apple Home, Aqara) - like most other devices which don’t face connectivity issues. Everything is up-to-date.
When I had issues with my thread network in general, the solution for me was to change the automatic bridge selection setting within the Apple Home App to a dedicated Apple TV. This is something you could try as well if you haven’t but tbh I don’t think this will help in your situation but might be worth a try
This is the latest from Aqara support (this case has been open since December 10, 2025):
Currently, we suggest that you try creating a new Thread network for the M3 hub to see if the frequent offline issue still occurs. This problem might be caused by the Thread network provided by Apple devices, and we are still investigating it.
I’m not going to even try this because that’s not what I bought the products for. The 2.4 GHz is already used by WiFi, Zigbee, and Thread, so I don’t want to dedicate another channel to Thread (I’ve already restricted 2.4 GHz WiFi to just channels 1 and 6 to make room around WiFi channel 11).
I’ve reset them, re-paired them, and exchanged batteries (as instructed by support). It usually lasts a few days until one or more of them go offline. I’ve also rebooted the M3 hub multiple times as requested and installed a firmware update on the M3.
I haven’t tried Zigbee as I honestly don’t care because I bought them as Matter-over-Thread sensors - that core functionality should just work.
Having the same issue. My thread network is based on an OTBR container, and I have two FP300 connected to HA that also go offline after a couple of days. I’m not having the same issue on my 30+ thread other devices.
Firmware: 1.0.7.3
Also, I don’t want to use them with Zigbee (I don’t have any Zigbee devices).
So an update. I removed the pairing with with apple home, and the Aqara app leaving only Homey Pro. It appears everything is now working. This leads me to believe there is an issue with how the FP300 handles multi-admin