If your Google Home keeps disconnecting from wifi at roughly the same time every day, stop resetting it. The speaker is almost certainly fine. What’s happening is that your router hands out IP addresses on a timer, and when that timer expires it gives the speaker a different address than the one it had — so give the speaker a permanent address instead, and the nightly drop usually stops.
That’s the short version. Below is how to tell whether that’s actually your problem, the exact setting to change, and the four router options that break smart speakers quietly enough that most people never suspect them.
Why Google Home keeps disconnecting from wifi at the same hour
Your router runs a service called DHCP. It’s the thing that assigns an address to every phone, laptop and speaker that joins your network, and it doesn’t assign them forever. Each address comes with a lease, and most consumer routers set that lease to 24 hours.
When the lease runs out, the router renews it. Usually it hands back the same address and nothing happens. Sometimes it doesn’t — because another device grabbed that address while the speaker was idle, or because the router rebooted, or because the lease table filled up.
Now the speaker has a new address. But your phone, your Chromecast, and any speaker group you built still have the old one cached. The speaker is online and answering, and your app still says it’s offline.
The tell is the timing. Random drops throughout the day point at signal or interference. Drops that cluster around the same hour, or that show up after every router reboot, point at the lease.
You can check this without guessing. Open your router’s admin page and find the connected-devices or DHCP-clients list, then note the address next to the speaker. Check it again the next day. If the number changed, the lease is your problem and the rest of this page will fix it. If it stayed the same, skip ahead to the router settings.
Reserve an IP address for the speaker
A DHCP reservation tells the router “this specific device always gets this specific address.” The lease still renews. It just renews to the same number every time.
If you’re on Google Wifi or Nest Wifi, it’s in the Google Home app, and Google documents the steps in Set DHCP IP reservation or a static IP address for a device:
- Open the Google Home app and go to Wi-Fi → Network settings → Advanced networking.
- Tap DHCP IP reservations, then Add IP reservations.
- Pick the speaker from the device list.
- Enter the address you want it to keep and tap Save.
One caveat from Google’s own documentation, and it trips people up:
“You may need to disconnect this device from your Wi-Fi network and reconnect it before it is assigned the reserved IP.”
So after you save, unplug the speaker for ten seconds. Otherwise it keeps running on the old lease and you’ll think the fix didn’t work.
On a third-party router the feature exists under a different name. Look for DHCP reservation, address reservation, static lease, or bind IP to MAC, usually under LAN or DHCP settings. You’ll need the speaker’s MAC address, which is in the Google Home app under the device’s settings.
Pick an address outside the range your router hands out automatically. If your router’s DHCP pool is 192.168.1.100 to 192.168.1.200, reserve something like 192.168.1.50. That way nothing else can ever claim it.
Four router settings that quietly break smart speakers
If the reservation doesn’t hold, the problem is usually one of these. None of them announce themselves — the speaker just behaves badly.
| Setting | What to do | Why |
|---|---|---|
| AP isolation / client isolation | Turn off | Stops devices on the same network from seeing each other. Your phone can’t reach the speaker at all. |
| IGMP snooping / multicast | Turn on | Casting and speaker groups run on multicast. Without it, groups fall apart. |
| Guest network | Move the speaker off it | Guest networks isolate clients by design. Same problem as AP isolation. |
| Aggressive QoS | Turn off or exempt the speaker | Some routers throttle low-traffic devices as idle, which reads as a dropout. |
Google publishes its own list of network types that don’t work with Home and Nest devices — captive portals, enterprise networks with a login page, and networks where client isolation is enforced. It’s worth reading before you blame the hardware: Wi-Fi networks that are incompatible or aren’t recommended.
When it’s the network, not the speaker
Here’s how to tell the difference in about two minutes.
Move the speaker to within a few feet of the router and leave it for a day. If it stays connected, you have a coverage or interference problem, not a configuration one. Thick walls, a microwave, and 2.4GHz baby monitors all sit on the same band and all cause exactly this symptom.
If it drops even next to the router, it’s configuration. Go back to the reservation and the table above.
Band choice matters here too. The Nest Mini (2nd gen) supports 802.11b/g/n/ac on both 2.4GHz and 5GHz, so it can use either. Many routers broadcast both bands under one name and decide for you, which is called band steering — and mid-session steering is a known cause of brief dropouts on smart speakers. Splitting the bands into two named networks and putting the speaker on one of them removes that variable. It’s ugly. It also works.
Still dropping after all that
Two things are left, in this order.
Disable IPv6 on the router temporarily. Some ISP-supplied routers run a broken IPv6 implementation, and Google speakers will prefer it and then fail quietly. If disabling it fixes the drops, you’ve found your answer and you can take it up with your ISP.
Then factory reset the speaker and set it up fresh — but only last. A reset wipes the speaker’s stored network profile, which is worth doing if the profile is corrupt, and worth nothing at all if the problem was the lease. That’s why it’s step nine and not step one, even though it’s the first thing every forum thread suggests.
One thing that isn’t this problem, in case you landed here from the wrong symptom: if a light rather than a speaker is misbehaving — an LED strip that flashes after you switch it off — that’s leakage current on the mains side. It looks like a smart-home fault and it isn’t one.
Do this first: open the Google Home app, set a DHCP reservation for the speaker, then unplug it for ten seconds. If the drops were happening on a daily rhythm, that single change is the one that ends them.
More in this section: Smart home troubleshooting starts here.
Three apartments, three full smart-home teardowns and re-installs. I write about the things that go wrong after the unboxing: devices that drop off Wi-Fi, dimmers that flicker with LED bulbs, locks that will not fit a rental door. Every fix here is one I have done or verified in owner forums, with sources linked.