Hello,

I’m having an ongoing issue with my TP‑LINK Tapo P110 smart plugs where they don’t respond immediately when triggered from a device that sits on a different VLAN. The delay isn’t massive, but it’s noticeable enough to be frustrating—especially when I’m simply trying to turn lights on or off. What’s odd is that the Alexa smart speaker controlling them is on the same VLAN as the Tapo devices, so in theory the command path should be local and instant. Instead, there’s a hesitation that feels like something in the network path is getting in the way.

For context, everything here runs through a TP‑LINK Omada setup. I’ve got multiple Omada EAP225 access points connected to a smart PoE switch, and from there the network extends to the cottage via a pair of Pharos CPE510 outdoor access points in bridge mode. The whole system works brilliantly for general connectivity, and all other devices behave exactly as expected across VLANs. It’s only the Tapo smart plugs that seem to struggle with timely responses when the initiating device isn’t on their VLAN.

I’ve already tried the usual suspects: adjusting Wi‑Fi channels, tweaking transmit power, checking for interference, and making sure the VLAN rules aren’t overly restrictive. None of these changes have made any noticeable difference. At this point I’m wondering whether the Tapo devices are particularly sensitive to multicast, broadcast isolation, or cross‑VLAN discovery quirks—but I’m not certain.

If anyone has run into similar behaviour with Tapo devices, Omada networks, or VLAN‑segmented smart home setups, I’d really appreciate any suggestions. I’m especially interested in whether there are specific Omada settings, IGMP/mDNS considerations, or Tapo‑specific limitations that could explain this kind of delay. Any insights would be a huge help.

Many thanks,

Ben