Aqara Devices Keep Dropping Off in Your Singapore Home? Here's the Home Assistant Fix

If your Aqara switches, lights or locks have started acting up, going quiet, slow to respond, or just gone altogether, it is a fair guess you are not the only one in your block dealing with it. We get asked about this often enough that it is worth writing down properly: what actually causes it, and what we have done about it on real jobs.

Quick Answer

• Most of the time it is not the Aqara device that is broken, it is Zigbee mesh interference. Something broadcasting on 2.4GHz nonstop crowds out the Zigbee signal, and it does not have to be inside your own home. In HDB and condo blocks it is often an upstairs or downstairs neighbour's equipment sitting in the same spot on their floor. Devices furthest from your Home Assistant hub become slow or unresponsive rather than fully offline.
• The fix is usually more Zigbee router devices (mains powered ones like smart plugs) placed to create alternate relay paths, for example along windows, since glass blocks 2.4GHz far less than concrete or brick walls.
• Sometimes it is firmware, which shows up as a device going "unavailable" in Home Assistant. This matters most for Aqara door locks, which need a separate Aqara Hub to bridge into Home Assistant, unlike most other Aqara devices that run directly on Zigbee2MQTT.
• Occasionally it is a genuine hardware fault, usually on lights, where the only real fix is replacing the unit. This is rare. From what we have seen, Aqara hardware is generally well made.
• Layman Smart Home People are Home Assistant system integrators who work with Aqara hardware on Singapore installs. We are not an Aqara-authorised repair centre, but we diagnose and fix exactly these kinds of Zigbee mesh and integration issues as part of a Home Assistant setup.

---

"Dropping Off" Usually Means One of Three Different Things

People use "dropping off" to describe three fairly different problems, and the fix is different for each:

1. Unresponsive or laggy - the device is still on the network, but commands are slow or sometimes do not go through at all.
2. Unavailable - Home Assistant shows the device as offline or unreachable, even though it is powered and nearby.
3. Gone from the network entirely - the device has to be re-paired to show up again at all.

Knowing which one you are dealing with matters, because the causes and fixes are not the same.

---

The Most Common Cause: Your Zigbee Network Is Fighting for Airspace

Zigbee runs on the 2.4GHz band, the same band as WiFi, Bluetooth, and a lot of other consumer gadgets. In a Singapore HDB or condo, that band can get crowded fast, especially with neighbouring WiFi networks, wireless cameras, or anything else broadcasting on 2.4GHz continuously.

When that happens, it is usually not that a device drops off entirely. It is that the Zigbee mesh struggles to relay messages reliably, and devices furthest from your Home Assistant hub feel it the most, since their messages have to hop through more of the crowded space to get back.

It does not even have to come from inside your own unit. HDB and condo blocks often repeat the same floor plan on every level, so if an upstairs or downstairs neighbour has a router or other 2.4GHz device sitting in roughly the same spot on their floor, that interference can stack vertically through the floor slabs and create a dead zone at that exact spot in your home too.

A Real Example From One of Our Projects

On one project, the Aqara switches at the far end of the house were consistently slow to respond, sometimes not registering a command at all, while switches closer to the hub worked fine. They were not dropping off the network. They were just struggling to relay messages back and forth reliably.

The fix we used was to add more Zigbee router devices, in this case smart plugs, positioned along the side of the house near the windows. This gave the mesh an alternate path to relay messages from one end of the house to the other, routing along the outside of the building where glass causes far less signal loss than the concrete and brick in between rooms. Once those extra router devices were in place, the far end of the house stopped lagging.

This is the kind of diagnosis we do as Home Assistant integrators on every project. It is rarely about replacing the Aqara device itself, it is about giving the Zigbee mesh a better path to work with.

---

When It's Firmware: Devices Showing "Unavailable"

Sometimes the cause is firmware rather than interference. A device shows up as unavailable in Home Assistant even though it is powered and within range, because it is not communicating properly.

This is particularly relevant for Aqara door locks. Unlike most Aqara devices such as switches, sensors and lights, which connect directly over Zigbee2MQTT, Aqara locks need a separate Aqara Hub to bridge into Home Assistant. That extra hop is one more place where a firmware hiccup can cause communication problems, which is why locks tend to be more finicky about this than a simple switch.

---

Gone From the Network Entirely? Try Putting It Back Into Pairing Mode First

If a device has properly disappeared, not showing up in the Aqara app or in Zigbee2MQTT at all, the first thing to try is putting it back into pairing mode while your Home Assistant setup is listening for new devices. The general steps differ by device type:

• Switches and smart plugs: press and hold the button for about 5 to 10 seconds until the LED starts blinking quickly. Honestly, there is not much practical difference between "resetting" it and "pairing" it here, holding the button does both at the same time, so just be ready to add it again once the LED starts blinking.
• Lights: power cycle the light off and on a few times in a row, generally about 3 to 5 times, and it should drop back into pairing mode on its own.
• Curtain and blind motors: press and hold the reset button until the LED starts blinking, much the same as switches.
• Sensors (motion, door and window, temperature): most have a small physical button you press and hold to put the sensor back into pairing mode.
• Door locks: these do not pair the same way as the others. You add or re-add the lock through the Aqara Home app itself, rather than through Home Assistant or Zigbee2MQTT directly. It is worth doing this properly even beyond just fixing connectivity, since adding the lock to an Aqara Hub (such as the M100 or M3) through the app unlocks extra functionality, and that same step is also what lets us bring the lock into HomeKit.

If you have gone through the pairing steps for your device type and it still refuses to show up, that is when it is worth suspecting a genuine hardware fault rather than a pairing hiccup.

---

When It's Actually the Hardware (Rare)

If re-pairing does not bring a device back, occasionally the issue really is the device itself. We have seen Aqara lights drop out of Zigbee2MQTT entirely, most likely down to a hardware fault, whether a bad batch of components or a firmware issue baked into the unit. In these cases, the only real fix is to replace the device.

This is genuinely rare. From what we have seen, Aqara makes solid hardware overall, and in most of the cases we get called out for, the device itself is fine and the problem is the mesh or the firmware, not the unit.

---

We're Home Assistant Integrators, Not Aqara Dealers

Worth being upfront about this: Layman Smart Home People are not Aqara-authorised dealers or an official repair centre. We are Home Assistant system integrators who use Aqara hardware, among other brands, as part of the systems we design and install for Singapore homes.

What that means in practice is when Aqara devices in your Home Assistant setup start acting up, we can diagnose whether it is mesh interference, firmware, or genuine hardware failure, and fix or route around it as part of your overall system, rather than just telling you to contact Aqara support.

FAQ