If a smart device worked fine for weeks or months and has only recently started going offline, start by asking what changed on the network, not by resetting the device. A device with a working history has already ruled out a bad setup, the wrong app, or a pairing mistake. The most likely causes, in the order worth checking, are: a router setting that changed on its own (firmware update, ISP push, or automatic band management), growing wireless interference as more devices joined the same network, or a problem with the vendor’s cloud service rather than anything in your house.
That order matters. Most troubleshooting guides give the same generic checklist to everyone: restart the router, restart the device, check the signal, update the firmware, reset as a last resort. That checklist is fine for a device that never worked. It wastes time on one that did.
What “it worked before” already tells you
A device with a real track record gives you information a brand-new setup doesn’t have. If it connected, stayed connected, and responded reliably for a stretch of time, you can rule out several things immediately:
- The device’s own Wi-Fi setup process worked, so it isn’t a pairing problem.
- It’s on the right account and in the right app, so it isn’t an account-linking mistake.
- It was compatible with your router’s security settings at some point, so a mismatch that would block it from connecting at all is unlikely to be the root cause of an intermittent drop.
What’s left is narrower: something changed. Routers push firmware automatically. ISPs sometimes reconfigure customer equipment remotely without an obvious notification. A neighbor’s new mesh system or a new baby monitor changed how crowded the 2.4 GHz band is around your home. Or the device itself degraded a battery-powered sensor’s battery is lower now than it was three months ago, or the device has simply aged.
The four-way elimination order
Rather than guessing, work through four buckets in order, starting with the one most likely to explain a device that used to work:
- The router. Something changed in its settings, its firmware, or how it manages Wi-Fi bands. This is the single most common cause of a previously-stable device suddenly misbehaving, because routers update themselves without asking.
- The radio environment. More devices, more neighboring networks, or a new source of interference nearby (a microwave, a new mesh access point, a baby monitor) crowding the same channel your device depends on.
- The device itself. Aging hardware, a low battery, or firmware on the device that needs its own update.
- The vendor’s cloud service. Less common for a purely local drop, but worth ruling out if the device shows as connected in its own app but doesn’t respond to commands.
Full detail on running each of these tests belongs in is it the device, the radio, the router or the cloud this is the ordered map of where to look, that page is the actual test for each branch.
The most common cause first: a router setting you didn’t change
Before touching the device at all, check whether your router recently updated itself. Firmware updates and ISP-pushed configuration changes are the most frequent cause of a device that was stable and then wasn’t, and they are also the easiest to overlook because nobody in the house did anything.
Two router behaviors specifically cause this pattern for smart devices:
- Band steering turning on or changing behavior after an update, which pushes a device toward a radio band it struggles with. If your device drops specifically when it’s close to the router (where the signal is strongest and steering is most aggressive), this is worth checking first see band steering and smart home problems.
- A combined network name hiding the 2.4 GHz band a device depends on behind automatic band selection. If several devices dropped around the same time, not just one, this is a stronger candidate see splitting your 2.4 GHz and 5 GHz network names.
Growing interference: when more neighbors means fewer working channels
If your router’s settings genuinely haven’t changed, the radio environment around it might have. Apartment buildings and dense neighborhoods add new networks constantly, and 2.4 GHz only has three channels that don’t overlap with each other. A device that had a clear channel to itself six months ago may now be sharing space with several new neighbors’ routers. See finding the least crowded 2.4 GHz channel for how to check this without guessing.
When it really is the device
If the router hasn’t changed, the radio environment is clean, and the vendor’s status page shows no outage, what’s left is the device itself. Battery-powered sensors lose reliability as the battery drains, well before the app shows a low-battery warning. Devices with years of continuous uptime can also simply degrade a symptom worth naming honestly rather than blaming the network indefinitely when the evidence points elsewhere.
Why the generic checklist wastes an hour here
A device that never connected in the first place needs a different set of questions entirely is the app set up correctly, is the device in pairing mode, is the phone on the right network. None of that applies to a device with a working history, and running through it anyway is exactly what most troubleshooting guides ask you to do, because they’re written for both situations at once. Separating the two up front is the fastest way to stop re-checking things that already worked.
FAQ
Does restarting the router actually fix this, or is it just a temporary patch?
A restart can clear a temporary glitch, but if the device drops again within a day or two, the underlying cause (a router setting, growing interference, or an aging device) hasn’t changed, and the restart only bought time.
My device shows as “online” in its app but won’t respond to commands. Is that the same problem?
Not necessarily. A device that shows online but doesn’t respond often points toward the vendor’s cloud service rather than your local network check the manufacturer’s own status page before assuming it’s something in your house.
Should I just factory reset the device and set it up again?
A factory reset is worth trying only after the router, radio, and cloud checks turn up nothing, because it throws away the “it worked before” evidence and puts you back in generic-setup territory.
Is this the same as a device that never connected in the first place?
No. A device that never worked is almost always a setup, account, or pairing issue. A device that worked and then stopped is almost always something that changed on the network or in the device itself, which is what this guide addresses.
How do I know if it’s one device or the whole network?
If a second, unrelated device also started misbehaving around the same time, look at the router and the radio environment first. If it’s genuinely isolated to one device, the device itself becomes a more likely culprit.