If your Google Home keeps disconnecting from wifi at roughly the same time, don’t factory-reset it yet.
Record the speaker’s local IP address, wait for the next drop, and compare it.
Reserve the address only if it changed.
If every Google or Nest device goes offline together, skip the reservation. That’s a router, internet or Google service problem, not one speaker losing its address.
One speaker or all of them?
Why Google Home keeps disconnecting from wifi
Open the Google Home app before changing a setting. Check the other speakers, displays and Nest products in the same home.
| What went offline | First check | What it rules out |
|---|---|---|
| One speaker at the same time or after a router restart | Compare its local IP before and after | A reservation won’t help unless the address changes |
| One speaker in a distant room | Run it near the router for a day | Stable service nearby points to coverage or interference |
| Every Google or Nest device | Test the internet on a phone with mobile data off | If the phone also fails, start with the router or ISP |
| The app says offline but voice still works | Update and reopen the Home app | The speaker may still be connected |
Google’s connection guide makes the same whole-home distinction. When every Nest product is offline, Google tells you to restart the router and check power, the ISP and Nest service status.
That order matters. A static address can’t restore an internet outage.
Test the home connection with cellular data turned off. If a phone on the same Wi-Fi can’t load a page, write down the outage time and start with the router or ISP. If the phone works, check the Nest service status and update the Home app before changing LAN settings.
Also separate “offline in the app” from a speaker that can’t answer. If voice commands still work, don’t reboot the network just to refresh one stale app screen. Close and reopen the app, confirm you’re viewing the correct Home, and test the speaker again.
Prove the IP changed before you reserve it
DHCP is the router service that assigns local addresses. A lease renewal normally happens without drama, so the fact that your router uses DHCP isn’t proof of a fault.
You need two snapshots.
- Open the router’s connected-device or DHCP-client page while the speaker works. Save the speaker name, MAC address and local IP.
- After the next disconnect, open the same page before rebooting anything. Compare the IP and whether the router still lists the speaker.
- If the IP changed and the problem follows that change, create a reservation. If it didn’t, leave DHCP alone and move to the signal checks below.
This also separates two failures that look alike. A speaker missing from the router has lost Wi-Fi; a speaker still listed under the same IP may have an app-discovery or internet-service problem.
Don’t rely on a remembered last digit. A screenshot taken before and after the drop is enough.
An address change is evidence, not a verdict. Home devices normally renew DHCP leases without disconnecting. Use a reservation only when the drop occurs with the change more than once, or when the speaker becomes reachable again after the router gives it a stable address.
Reserve the address without guessing at the range
On Google Wifi or Nest Wifi, Google documents DHCP IP reservation in the Home app under Wi-Fi, Network settings and Advanced networking. Choose DHCP IP reservations, add a reservation, select the speaker and save an address.
A reservation makes the network assign “the same IP address to a specific device whenever that device connects.”
Use the address suggested by the router or an unused address its own interface accepts. Don’t copy a random number from an online example, and don’t configure a manual static IP on the speaker.
Google notes that the device may need to disconnect and reconnect before it receives the reserved address. Reboot the speaker once after saving, then confirm that the router shows the reserved IP.
Save a screenshot of the reservation too. If the speaker drops again while the router still lists the same MAC and reserved IP, the reservation test is finished. Remove it only if you need the address for another device; otherwise move to coverage, app and internet-service checks.
On another router, the label may be DHCP reservation, address reservation or static lease. The job is the same: bind the speaker’s MAC address to one local IP inside that router’s configuration.
If the IP stayed stable, test distance and network type
Move only the problem speaker close to the router and leave it there long enough to cross its usual failure time. If it stays online, the useful fix is coverage, placement or interference—not a reservation.
Walls, cabinets and other 2.4GHz equipment can matter more than the number of signal bars shown during setup. Change one condition at a time so you know what helped.
Don’t split 2.4GHz and 5GHz merely because a forum says every Google speaker needs 2.4GHz. Band support varies by model. Google’s current setup guidance says to try both bands when a dual-band router offers them.
Network type can stop setup or discovery too. Google lists captive-portal and 802.1X enterprise networks as incompatible, and it warns that guest networks can make troubleshooting difficult.
If the speaker sits on a guest network, move the phone and speaker to the main home network. Don’t disable multicast, IPv6, QoS and security features as a batch; that destroys the evidence you just collected.
Reboot once and reset last
A reboot and a factory reset are different. Google says a reboot can fix several speaker or display issues without erasing setup, while a factory reset removes the stored configuration.
Reboot one speaker after applying a verified reservation or after the router is stable. If the entire home went offline, restart the router first and let it finish before judging the speaker.
Use a factory reset only after the speaker fails close to the router, keeps the same IP, the internet works for other devices and the Home app is current. At that point you’ve ruled out the cheaper explanations.
If a light rather than a speaker is misbehaving, an LED strip that flashes after switch-off belongs to a different troubleshooting path. That’s an electrical-control symptom.
Do this now: take the first screenshot of the speaker’s IP and MAC address. The next drop will tell you whether “fix the IP first” applies to your network or whether you should leave DHCP alone.
More in this section: Smart home troubleshooting starts here.
Bolt & Bulb covers what goes wrong after the unboxing: devices that drop off Wi-Fi, dimmers that flicker with LED bulbs, locks that will not fit a rental door. The site draws on manufacturer documentation, platform support pages and release notes, and attributed owner reports in public forums.