Smart Home Device Keeps Going Offline? An Ordered Checklist for Malaysian Homes

Answer up front — Work through it in this order: battery, distance from the hub, is the hub online, is your Wi-Fi actually up, is this a mains device that has lost power, is the app logged out. The mistake that costs people the most money is assuming a Zigbee device went offline because the internet is slow. Your Zigbee devices do not use your Wi-Fi at all — they talk to the hub, and the hub only needs your internet for the notification to reach your phone. Fixing a broadband plan will not fix a dead battery.

Before anything else: know which kind of device you are looking at

Most of the wasted money in this problem comes from treating every offline device the same way. Work out which of these you have, because the diagnostic path is completely different:

Once you know which row you are in, stop reading the other rows. The rest of this article is that order.

Step 1 — Is it the battery

This is the most common cause by a wide margin, and it is the one to rule out first because it takes ten seconds.

How to check, without guessing: open the Aqara Home app and look at the device. Aqara reports battery level for its battery-powered sensors, and it flags low battery before the device goes offline entirely. If the level is low, or the device has already dropped off, the battery is the first thing to change. Change it and see what happens.

Two things that catch people out:

• A "new" battery that has been sitting in a drawer for a year may already be weak. Batteries lose charge in storage. Use a fresh one of the type the device's manual specifies.
• A battery device that has been offline for weeks may have drained completely, and some devices need the sensor to be woken — a press, a reset of the device's own pairing state, or simply re-inserting the cell. If a fresh battery does not bring it back, re-pair that one device rather than resetting the whole hub.

Do not open a device, do not re-pair the whole system, and do not buy a new sensor before you have tried a battery. That is the sequence that saves the money.

Step 2 — Distance from the hub

Zigbee devices do not talk to the hub directly across the whole house. They relay. A device two rooms away may be reaching the hub through another device. This is normal and it is the design.

What causes a device to lose its route:

• It has been moved. A sensor that used to sit near the hub and now sits at the far end of the house has changed its route, and it may not find one.
• Something new is in the way. A new metal door, a new wall finish, a new piece of furniture pressed against a sensor, a cabinet door now closed where it used to be open.
• The house has more Zigbee devices than it had, so the route it was using no longer exists as a live path.

Check where the hub actually is and how far the device is from it. If the device sits at the back of a landed house and the hub is at the front, that is a coverage problem, not a device problem — and the fix is more mesh nodes, not new sensors. Repeaters and dead zones are covered in Zigbee mesh, repeaters and dead zones.

Step 3 — Is the hub itself online

Before you touch the individual device, look at the hub. This is the step people skip, and it is the one that explains the case where three different devices all went offline on the same afternoon.

• Is the hub powered? Check the power light, not the app.
• Is it connected to your network? Check the router.
• Did your broadband provider do something? A router reboot during a firmware update or a line fault will take the hub offline and take every notification with it.

If the hub is offline, every Zigbee device may still be working perfectly — they keep talking to each other — but the app will show them all as unreachable, and you will get no notifications. That is a hub problem, and no amount of new sensors will fix it.

Step 4 — Is your Wi-Fi up

Now check the internet, because this is the step that is often blamed on the wrong thing.

A broadband problem will make a Wi-Fi device — camera, doorbell, anything that talks to your router directly — drop or go unresponsive. A broadband problem will not make a Zigbee device drop. That distinction is the whole point: your Zigbee sensors and switches are on their own network, inside your house, and the only thing your internet does is carry the notification to your phone.

So the test is simple. If your Wi-Fi and phones are working fine on the same network, and a Zigbee device is showing offline in the app, your internet is not the cause. People upgrade their broadband plan on the strength of this misdiagnosis and it changes nothing. If a Wi-Fi device is offline and everything else on the network is fine, then the device's own Wi-Fi connection is the suspect — distance, interference, or a router that changed its network.

Step 5 — Is it a mains device that has lost power

For anything plugged in or hard-wired: a wall switch, a 20A module for the aircon or water heater, a smart plug, a relay.

Check three things, in this order:

1. The socket or switch feeding it. A smart plug in a socket that somebody switched off at the wall, or a relay module behind a switch that cuts its supply, is simply unpowered. The most common "fault" in this whole category is a switch somebody flipped.
2. The circuit breaker. Go to the DB and look. A smart switch or a 20A module on a shared circuit with a failed device can trip the breaker for that circuit. A tripped breaker is easy to see and easy to reset, and it explains several devices going at once.
3. The device's own behaviour. Some mains devices hold a state that survives a power cut, and some do not. If a device worked before a power cut and not after, that is a power-event question, not an offline question — and the answer is in the current documentation for your model.

If your mains device is fine and the hub is fine, the remaining explanation is the mesh route, which is step 2 again.

Step 6 — Is the app logged out

Rare, and it presents exactly like a whole-house failure, which is why it is on the list.

If the app has been signed out — because you changed your Aqara account, reset your phone, or the session expired — the app will show your devices as unreachable even though they are working perfectly. The house did not break. Open the app, and if it asks you to sign in again, that is the answer.

If you are signed in and it still shows offline, and you have access to more than one phone, sign in on a second device with the same account. If it works there, it is an app or phone problem. If it does not, it is a real device or hub problem and you are back at steps 1 to 5.

The Malaysian layout problem

Two things about Malaysian houses specifically, and both change the answer.

Concrete and thick walls. A landed or terrace has a lot of masonry between the front and the back of the house, and a Zigbee signal does not enjoy it. But note carefully: this is a distance and mesh problem, not an internet problem. A device in the back bedroom behind two concrete walls is not going to be fixed by a faster broadband line.

Multi-floor layouts. On a three-storey house, a device on the top floor is not automatically the problem. Check where the hub actually is. If the hub is on the ground floor and there are no Zigbee mains-powered devices in between, the top floor is thin, and the fix is a mains-powered repeater on a middle floor — a device that is always powered and always listening, so it can hold the route open. If there are already mains devices on the middle floor acting as repeaters, the top floor is covered and something else is wrong.

This is the most common misdiagnosis in a landed house: blaming the top floor when the hub is the problem, or the battery is the problem, and spending money on repeaters. Rule out steps 1 to 4 first.

If none of that works

In order:

1. Re-pair just that one device through the app. Do not reset the hub. This fixes a device that has lost its route or lost its pairing, and it costs nothing.
2. Check the hub's own connection and power once more, including whether anything changed on your network in the last few days — a new router, a new mesh node, a firmware update, a change of internet plan.
3. Screenshot what the app is showing before you do anything else, because it is the thing you will be asked for.
4. Reboot the hub as a last resort, and expect to re-do automations that reference it afterwards.
5. Contact us. Give us the device model, the hub model, and what the app was showing before you changed anything. We are the official Aqara distributor in Malaysia, with local stock, local warranty and local support, and support is exactly what this problem is.