The short answer
Most delay comes from commands travelling to a cloud server and back instead of staying on your network. Local control, a hub, and a fixed address for each device remove the majority of it. Wi-Fi congestion and devices in deep sleep account for most of the rest.
Pressing a button and waiting several seconds for a light is the fastest way to make a household stop using smart home features. The delay is rarely the device being slow. It is the path the command takes.
Where the time actually goes
When you tap a light in an app, a typical cloud-connected device does this: your phone sends the command to the manufacturer’s server, the server authenticates it, finds your device, and sends a message down the connection the device holds open, and the device acts. That is four network hops, at least two of them across the internet, and it happens even when your phone and the light are two metres apart.
A locally controlled device skips all of that. Your phone or hub talks straight to the device over your own network, and the response is typically under 200 milliseconds, which feels instant.
Fix 1: enable local control
- Matter-certified devices control locally by design once added to a Matter-capable hub. This is the main practical benefit of Matter and the reason it is worth preferring when buying.
- Apple Home runs locally through a home hub such as a HomePod or Apple TV. If you have HomeKit-compatible devices and no hub, adding one changes response times dramatically.
- Google and Amazon both support local execution for many routines and devices, but it is not universal and not always visible. Devices that respond instantly to a voice command and slowly to an app tap are usually running locally for one path and not the other.
- Home Assistant runs everything locally by design and is the definitive answer if you are willing to run it. It integrates with cloud-only devices too, though those keep their latency.
Fix 2: use the right radio for the job
Wi-Fi is the wrong protocol for a light switch, and it is used because it needs no hub. Its weaknesses in this role are real: every device must maintain a connection, each consumes an address, and a busy network makes them all sluggish.
Zigbee, Z-Wave and Thread are mesh protocols built for this. Each mains-powered device relays for the others, latency is low, and forty devices on a Zigbee network cause less trouble than ten on Wi-Fi. They need a hub, which is the cost. If you have more than about fifteen smart devices, moving to a mesh protocol is the single biggest improvement available.
Count the devices on your router’s client list. Many consumer routers become unreliable somewhere between 30 and 50 connected clients, and a smart home reaches that faster than people expect. Sluggish response across all devices at once is the classic symptom of a router at its limit.
Fix 3: clean up the network
Reserve a fixed address for every smart device
Do it in the router’s DHCP reservation list. This eliminates the re-discovery delay that happens when an address changes, and it makes troubleshooting far easier.
Split the bands or create an IoT network
A separate 2.4GHz network for smart devices keeps them from competing with laptops and TVs, and it solves the pairing problems that band steering causes.
Set 2.4GHz channel width to 20MHz
Wider channels on a crowded band increase collisions and delay, and smart devices are the first to suffer.
Add an access point near device clusters
A group of devices at the edge of coverage will all respond slowly. Coverage in the places devices actually live matters more than coverage where people sit.
Check for a device retrying constantly
One device with a bad connection can generate a lot of traffic. The router’s client list with connection times and signal strength will usually reveal it.
Fix 4: understand battery devices
Battery-powered sensors, buttons and locks sleep almost all the time in order to last a year on a coin cell. They wake on a schedule or on an event. A command sent to a sleeping device waits until it wakes, which is why a battery smart lock can take several seconds while a mains-powered bulb is instant.
This is a design trade-off rather than a fault. Where response time matters, choose a mains-powered device. Where battery life matters, accept the delay.
Fix 5: simplify automations
Automations that run in the cloud add their own delay, and chained automations multiply it. A motion sensor that triggers a cloud routine that then commands three lights will always be slower than a direct local binding between a sensor and a light. Most hub platforms support such direct bindings, sometimes called device links or direct associations, and they respond in tens of milliseconds because no hub is involved at all once configured.
Also check for conflicting automations. Two routines that both control the same light, one of them slow, produce inconsistent timing that looks like a network fault.
Be careful about putting smart devices on a guest network to isolate them. Guest networks usually enable client isolation, which blocks the local communication that makes everything fast, forcing all control back through the cloud. A separate IoT network without isolation is what you want, not a guest network.
What good looks like
On a well-configured local system, a wall switch or app tap lights a bulb in under a quarter of a second, a motion sensor triggers a light in about half a second, and a voice command takes one to two seconds, most of which is speech processing rather than the device. If yours are several times that, the cause is almost certainly a cloud round trip or a congested 2.4GHz band.
Why is voice control faster than the app sometimes?
Because a voice assistant with local execution can send the command directly to the device, while the app may still route through the manufacturer’s cloud. Different paths, different latency.
Will a better router fix slow smart home devices?
It helps if the current one is struggling with the number of clients, which is common. It will not help if the delay is a cloud round trip, since that happens outside your house entirely.
Is Matter worth buying into?
For local control and cross-platform compatibility, yes. It is the most practical route to instant response without committing to a single manufacturer’s ecosystem.
Do smart devices work when the internet is down?
Locally controlled ones do, including physical switches and hub automations. Cloud-dependent ones do not, which is a good argument for local control beyond just speed.
How many devices can a home Wi-Fi network handle?
Consumer routers typically become unreliable between 30 and 50 clients, though it varies widely. Mesh protocols such as Zigbee, Z-Wave and Thread handle far more, which is why large smart homes use them.
In short
Get the commands off the internet and onto your own network: a hub, Matter or Apple Home with a home hub, or Home Assistant. Reserve fixed addresses, give smart devices their own 2.4GHz network at 20MHz width, and add coverage where the devices are rather than where you sit. Accept that battery devices will always be slower, and use mains-powered ones wherever response time matters.
