Smart Home Troubleshooting Guide
Find the Layer, Fix the Fault

Think in layers

When you tap a button in an app, the command rarely goes straight to the device. Wikipedia's home automation article gives a simple example: the tablet sends a signal to the maker's cloud system, which then signals the light. In most homes the chain is longer still: phone, app, cloud, internet line, router, sometimes a hub, the device, and finally the power that keeps the device alive. A fault anywhere in that chain looks the same from the sofa: nothing happens.

Five checks before anything else

1. Note exactly what fails and what still works. One device, one brand, one room, or the whole house?
2. Note what changed recently: a new router, a password, an app update, a power cut, a new phone.
3. Try the device's own button or the wall control. If that works, the device and its power are fine.
4. Restart in order: router first, then any hub, then the device. Wait for each to settle before the next.
5. Open the maker's own app, not only Google Home or Alexa. The maker's app usually shows the clearest error.

Most problems narrow to a single layer after these five steps. Write down what you found; it saves repeating the tests and is exactly what anyone helping you will ask first.

Symptom map: where to go next

Each of those has its own page because the fixes run long. Router swaps are covered step by step in the guide to devices offline after a WiFi change. Band trouble during set-up is in the WiFi 2.4 GHz pairing guide. Weak Zigbee links are in the Zigbee range guide, and routines that stay silent are in the automations guide.

Pairing failures in general

Band problems are only one reason a device will not join. Before blaming the WiFi, rule out these, roughly in order of how often they turn up.

• Not really in pairing mode. Many devices have two blink patterns for two modes. Follow the manual's sequence exactly, and start again from a full reset if unsure.
• Still bound to someone else. A second-hand or returned device may be locked to the previous owner's account until they remove it. The app often says the device is already added.
• Wrong app or wrong region. Some brands run separate servers for different regions; a device sold for one region may not appear in an app set to another. The region-lock guide explains the China and global split.
• Phone permissions. Location, Bluetooth and nearby-device permissions are needed by many set-up apps.
• Hub required. If the device is Zigbee or Thread, it pairs to a hub, not to the phone or WiFi.

Ghost and duplicate devices

A ghost device is an entry that stays in an app after the real device is gone, reset or re-added. A duplicate is the same device shown twice, usually once under its old entry and once under its new one. They are harmless on their own but confusing, and voice assistants may try to control the dead copy.

Clean from the source outward: maker's app first, then the hub, then the voice assistant. Deleting only from the assistant usually brings the ghost back at the next sync.

When the app shows the wrong state

Sometimes the app says the light is on while the room is dark, or shows a curtain open that is closed. There are three common reasons. The first is a one-way device: an infrared hub only sends commands and never hears back, so the app shows what it last sent, not what the aircon is doing; the IR blaster guide explains the workarounds. The second is a manual change the app never heard about, such as someone using the original remote or a dumb wall switch that cut the power. The third is a slow or stuck cloud update, where the device did change but the app has not refreshed.

To tell them apart, pull down to refresh, then look at the device itself. If the device is right and the app wrong, it is a reporting issue, not a control fault. If routines rely on that state, they will act on wrong information, which is a common reason automations seem to misfire.

Device-specific faults

Some hardware has its own failure patterns worth a dedicated page. Curtain tracks that stall or reverse mid-way usually need limits re-learned or a mechanical check; see the curtain motor guide. Doorbells that ring at the door but not indoors are covered in the doorbell guide. When a speaker says a device is unavailable while the maker's app controls it fine, start with the voice assistant guide.

When everything fails at once

If every device in the house goes quiet together, the cause is almost never the devices. Check, in this order: is there power and is the router lit; is the internet line up; is it one brand's cloud that is down while other brands work. A whole-brand outage is out of your hands, and the best defence is a set-up where lights and switches keep working locally without the internet.

After a power cut, routers and hubs may take a while to come back and some devices give up searching before the network is ready. Restarting the stragglers once the router is stable usually fixes it.

Updates, resets and when to stop

Firmware and app updates fix many bugs and cause a few. If a fault started right after an update, check the maker's support notices before resetting anything. A factory reset is the last step, not the first: it wipes the device's settings and usually removes it from automations, so you rebuild more than you fix.

Stop and get help when a device is hot, smells of burning, buzzes, or trips power when switched on. Those are electrical faults, not app faults. Any mains electrical work, such as a new power point, a change at the distribution board or a hardwired switch that needs new wiring, must be done by an electrical contractor registered with Suruhanjaya Tenaga.

Keep a simple house record

Half of every troubleshooting session is working out what is installed and which account owns it. A one-page record ends that: each device, its room, its app, the owning account, how it connects, and where its reset button is. Update it when you add or remove anything, and keep the WiFi details with it. It also makes handing the house to a new owner or tenant far simpler.

How ClickBina helps

We trace smart home faults layer by layer, re-pair devices, clear ghost entries, fix routines and set up hubs and mesh WiFi where the network is the weak link. We do the smart device, app and low-voltage side of the job. For smart switches and anything wired into the mains, we supply the devices and set up the app, and the switch or wiring work is done by an electrical contractor registered with Suruhanjaya Tenaga that we coordinate. Tell us what fails, what still works and what changed recently.

Sources & references

• Wikipedia: Home automation (app commands travelling through the maker's cloud to the device).
• ClickBina guides on devices offline after a WiFi change, WiFi band pairing, Zigbee range, automations, curtain motors, doorbells, voice assistants, IR blasters and region servers.