Short answer
Aqara Zigbee sensors commonly go offline when they attach through weak or incompatible routers, sit at the edge of coverage, have low battery, or are affected by Zigbee/Wi-Fi interference. The fix is usually mesh planning, not repeated factory resets.
Next step
Need a final setup and reliability path?
$1.99 setup + reliability report
Send your scene, devices, hubs, and target ecosystem. We will return what to connect, what hub is missing, which features may not work, reliability risks, fallback checks, and what to buy or avoid.
Symptoms this page covers
- Aqara sensor offline
- last_seen stops updating
- Sensor works after re-pair then drops
- Low LQI
- Events are delayed
Likely causes
- The sensor is attached through a Zigbee router that Aqara devices do not handle well.
- The coordinator or router is too far away from the battery sensor.
- Low battery or cold location reduces radio stability.
- Zigbee channel interference causes missed reports.
- Availability settings mark a sleepy sensor offline even when it still reports events.
Fix checklist
- Check the sensor parent route and whether several failed sensors share the same router.
- Move the sensor closer to the coordinator or a known-good router and watch last_seen over 24 hours.
- Replace the battery before changing coordinator firmware or deleting devices.
- Avoid pairing Aqara sensors through random bulbs or weak plug routers.
- Document last_seen, LQI, battery, and route before re-pairing.
Avoid these mistakes
- Do not keep deleting and re-pairing the same sensor without changing its route.
- Do not assume every mains Zigbee device is a good router for Aqara end devices.
- Do not move Zigbee and Wi-Fi channels blindly without recording the current setup.
FAQ
Should I factory reset Aqara Zigbee sensors first?
Usually no. First confirm the controller, hub, network, and integration path. Resetting too early can remove useful evidence about which ecosystem or Thread network currently owns the device.
What should I check before buying another hub?
Check whether you already have the required Matter Controller, Thread Border Router, vendor hub, Zigbee coordinator, and Home Assistant service. Use the linked calculator or diagnostic tool before purchasing extra hardware.
Can SmartHomeCompat guarantee this fix for Home Assistant?
No. These pages are based on official docs, product information, public compatibility data, and community issue patterns. They are designed to narrow the likely setup path and reveal missing pieces.
Should I use Aqara Hub, Matter, or a direct Home Assistant path?
Use Aqara Hub when you want vendor-managed setup and Aqara app features. Use Matter when cross-ecosystem sharing is more important. Use direct Home Assistant paths such as ZHA, Zigbee2MQTT, or HomeKit Controller when local control and entity exposure matter more.
Feedback
Help improve this compatibility data
Smart home compatibility changes quickly. Send a report, request a missing device, flag information that needs another review, or tell us if a paid setup diagnosis would save you time.
Describe your devices, hubs, blocker, reliability risk, and the report output that would save you time.
Tell us which device, hub, bridge, protocol, or ecosystem should be added next.
Flag outdated, incomplete, or unclear setup guidance so it can be reviewed.
Choose a gateway, bridge, interface, or conversion path for KNX, BACnet, Modbus, DALI, Matter, Zigbee, Z-Wave, MQTT, or Home Assistant.