AP isolation (also called client isolation or station isolation) is a router or access point setting that stops devices connected to the same Wi-Fi network from communicating directly with each other, while still letting each of them reach the internet normally. That’s why the symptom is so confusing: your phone and your smart plug are both connected, both have internet, and the app still says “device not found,” because the app is trying to talk to the plug directly across the local network, and this setting is specifically built to stop exactly that. Checking whether AP isolation is enabled, usually in your router’s wireless or guest-network settings, is the fastest way to confirm or rule this out.
What AP isolation actually does
Normally, every device on the same Wi-Fi network can see and talk to every other device on it directly, the same way two laptops on the same office network can share a printer or a file. AP isolation removes that. Each connected device still gets internet access through the router, but the router refuses to pass traffic between two devices that are both connected to it locally. From each device’s point of view, it’s alone on the network except for the router itself.
This setting exists for a real reason: it’s the standard way to protect strangers from each other on a shared or public network, which is why it’s on by default on most guest networks and a lot of public Wi-Fi. The problem is that the same setting sometimes ends up enabled, or defaults to on, on a household’s main network, or specifically on the guest network a smart home device was connected to for convenience.
Why “same network, same room” still fails
This is the specific pattern that points at AP isolation over other causes: the device and the controlling app (or hub) are provably on the same network, sometimes even the same room, and it still doesn’t work. That rules out most Wi-Fi problems, which are usually about one device being on a different band, a different network name, or genuinely out of range. AP isolation doesn’t care about distance or signal strength. It blocks the connection even at zero feet apart, because it isn’t a range problem at all. It’s a router policy deciding that these two devices, even though they’re both connected, aren’t allowed to talk to each other.
A related giveaway: if the device works fine when controlled entirely through the cloud (an app command routes out to the internet and back down to the device) but fails specifically for anything that needs local discovery or local control, that split behavior also points at isolation rather than a connectivity failure, since cloud round-trips don’t require two local devices to reach each other directly.
Checking whether it’s on
Most routers expose this under wireless settings, sometimes labeled “AP Isolation,” “Client Isolation,” “Station Isolation,” or occasionally folded into a guest network’s own settings screen as something like “Allow guests to see each other.” The exact wording and location depend heavily on your router’s manufacturer and firmware, so treat this as what to look for rather than a fixed path to follow, and check both your main network’s settings and your guest network’s settings separately, since they’re often configured independently.
If your smart home devices are connected to a guest network rather than your primary one, isolation on guest networks is frequently on by default specifically because guest networks are designed to keep visiting devices from reaching each other, which makes them a poor fit for smart home devices that need to be found by an app or hub on the same network.
The trade-off worth knowing before you turn it off
Disabling AP isolation isn’t free. It exists to stop devices on a shared network from reaching each other, and turning it off means every device on that network, not just the smart home ones, can now see and potentially reach every other device on it too. On a household’s own private network with a small number of trusted devices, that’s usually an acceptable trade for getting your smart devices working. On a network shared with guests, a shared building’s Wi-Fi, or any network you don’t fully control, disabling isolation gives every connected device more visibility into every other one, which is worth weighing before you flip the setting rather than after.
A middle option some routers support is isolating a separate network specifically built for smart home devices while leaving that network’s isolation off internally, so devices can find each other without also being visible to whatever else is on your main network. That’s a bigger network change than this article covers, but it’s worth knowing the option exists if isolation keeps coming up as a recurring conflict.
What this doesn’t explain
AP isolation is one of several settings that can make a device technically connected but effectively invisible to the rest of your network. If disabling isolation doesn’t fix it, mDNS and multicast traffic being blocked is the next thing to check, since it produces a nearly identical symptom for a different reason: the device can be reached directly, but the discovery broadcast that tells your app it exists never arrives. If devices are dropping off entirely rather than just failing to be found, that’s a different problem covered in the router running out of addresses to hand out or the device, radio, router or cloud diagnostic order, which is the right starting point whenever you’re not sure which of these applies.
FAQ
Is AP isolation the same thing as a firewall?
No. A firewall typically controls traffic between your network and the outside internet. AP isolation controls traffic between devices that are already inside the same local network as each other.
Why would my router have AP isolation on by default?
It’s a common default on guest networks specifically, to keep visiting devices from reaching each other or anything else on your network. Some routers also ship with it on by default on the main network as a general security posture, which is worth checking rather than assuming isn’t the case.
Will turning off AP isolation fix every “device not found” problem?
No. It fixes the specific case where isolation is the actual cause. If it’s off already, or turning it off doesn’t help, the problem is more likely mDNS and multicast traffic, or something unrelated to local discovery entirely.
Does AP isolation affect wired (Ethernet) devices too?
It depends on the router. Some routers apply isolation only to the wireless radio, leaving wired devices able to reach everything normally; others apply it network-wide. Check your specific router’s documentation for how its implementation scopes the setting.
Can I isolate just some devices and not others?
Basic AP isolation is usually all-or-nothing for the network it’s applied to. Selectively isolating specific devices from each other while leaving others able to communicate generally requires more advanced router or firewall features than a simple isolation toggle provides.
Sources referenced in this article
- TP-Link, What Is AP Isolation? (And When to Enable It).
https://www.tp-link.com/us/blog/2586/what-is-ap-isolation-and-when-to-enable-it-/(accessed 2026-07-20). Source of the mechanism description and the guest-network default behavior. - XDA Developers, Your router has a feature called “AP isolation” and you should consider turning it on right now.
https://www.xda-developers.com/your-router-ap-isolation-and-you-should-consider-turning-it-on/(accessed 2026-07-20). Source supporting the security rationale behind the setting and its trade-off.
Review interval: 12 months (router firmware and default settings can change).