Direct answer
For the Nest Mini (2nd gen), band/security, signal, DHCP, power and cloud state should be isolated. First, test near the router on the supported network.
What this covers
- Nest Mini (2nd gen) (GA00781)
- Google Nest/Home device; Matter/Thread role, wired/battery power, subscription and Google Home migration vary.
- The specific fault this record addresses: will not stay connected to Wi-Fi
What it does not cover
- ×The same symptom on a different Google Nest product line, which has its own record and its own cited source
- ×An on-screen error code whose meaning has not been checked against this exact model's manual
- ×Live electrical, gas, sealed-system, internal battery-cell or structural repair — a technician boundary, not a self-service step
Differential
What actually causes this, and how to tell them apart
These are ordered by how often each one is the answer, not by how easy it is to try. The point of the middle column is that two causes producing the same headline symptom rarely produce the same detail — that detail is what tells you which one you have before you change anything.
- 1
Marginal signal rather than absent signal
What separates it It works after a reboot and degrades over hours or days. Live view starts slowly, notifications arrive late, then it drops. Genuine out-of-range is consistent; marginal signal is intermittent, and it gets worse when doors and windows stay shut or foliage fills in.
How to confirm Read the signal figure the device reports for itself in the app rather than the phone's bars in the same room — the phone has a far better antenna and a much larger battery. Move the device closer or add a mesh node and see whether the interval between drops lengthens.
- 2
Band steering is moving it to a band it cannot use
What separates it The router lists it as connected while the app calls it offline, or it connects perfectly on one visit and not at all on the next. Routers that advertise both bands under one name decide which one a client gets, and that decision can change.
How to confirm Look for the device in the router's client list and check which band it is associated with. Separating the 2.4 GHz network under its own name — even temporarily — settles this in one test.
- 3
The DHCP lease expires and is not renewed
What separates it The drop recurs on a roughly fixed schedule, and a reboot always fixes it for exactly the same length of time. The regularity is the tell — real radio problems are irregular.
How to confirm Compare the drop interval against the router's DHCP lease time. A reservation against the device's MAC address removes the failure mode permanently rather than resetting its clock.
- 4
The router's client table is full
What separates it The device drops when another device joins, and which device drops varies. Households with dozens of connected devices exceed consumer router limits without any warning message.
How to confirm Count the active clients in the router's list against its documented maximum. The symptom looks random until it is plotted against joins.
- 5
Interference on the channel rather than weak signal
What separates it Signal strength reads fine and the connection still stutters. Microwave ovens, cordless phones, baby monitors and dense neighbouring networks all occupy 2.4 GHz, and the symptom follows their use.
How to confirm Change the router's 2.4 GHz channel to 1, 6 or 11 — whichever is least occupied — and retest. Good signal with bad throughput is the signature of interference, not distance.
- 6
A router firmware update changed the security or isolation settings
What separates it The device worked for months and stopped on a date that matches an automatic router update. WPA3-only mode, IoT client isolation and DNS filtering are all defaults that have changed across firmware generations.
How to confirm Compare the router's current security mode against what the device supports. A device that needs WPA2 on a router switched to WPA3-only will fail in exactly this way with no useful error.
- 7
The mesh node it associates with is not the nearest one
What separates it The device is physically close to a node and still reports poor signal, because it associated with a distant node and mesh systems rarely force a client to move.
How to confirm Check which node the router's app says the device is on. Power-cycling the device near the intended node forces a fresh association and is the fastest way to test this.
- 8
Metal, masonry or glazing in the path
What separates it Signal drops sharply over a short distance. Foil-backed insulation, metal doors, wire-reinforced glass and low-emissivity window coatings attenuate 2.4 GHz far more than plain distance does.
How to confirm Move the device temporarily to a position with clear line of sight and compare the reported signal. A large change over a short move identifies an obstruction rather than range.
Before you touch a setting
Record this first — changing settings destroys the evidence
Every item below stops existing the moment a reset, re-pair or settings change is made. Written down first, they are what separates the causes above; recovered afterwards, they are guesswork.
- The interval between drops, to the nearest hour. A regular interval points at a lease or a schedule; an irregular one points at signal or interference.
- The signal strength the device reports for itself, read in the app, at the position it actually lives in.
- Whether the device appears in the router's client list while the app calls it offline — this single fact splits the investigation in half.
- Which access point or mesh node the device is associated with, and whether it is the nearest one.
- The router's security mode, channel and DHCP lease time, and whether the router has updated its own firmware recently.
- What else uses 2.4 GHz nearby and when: microwave, cordless phone, baby monitor, neighbouring networks.
Establish whether the drops are regular or irregular
ReversibleNote the time of several drops before changing anything. A regular interval is a lease or a schedule and is fixed at the router. An irregular one is signal, interference or power, and is fixed at the device. Changing settings before this is known destroys the pattern that identifies the fault.
Read the signal the device reports for itself
ReversibleUse the figure in the app for Nest Mini (2nd gen), not the phone's bars in the same room. A phone has a larger antenna and far more power available, and routinely shows good signal where the device has almost none.
Check whether the router still lists it while the app says offline
ReversiblePresent in the router's client list but offline in the app moves the fault past the radio link entirely — to DNS, a firewall rule or the provider. Absent from both keeps it at the radio.
Give the 2.4 GHz network its own name for one test
ReversibleBand steering under a shared name is the most common cause of a device that connects sometimes. Splitting the bands temporarily settles it in one test and can be reverted afterwards.
Move the 2.4 GHz radio to a clear channel
ReversibleSet the router to channel 1, 6 or 11 — whichever is least occupied nearby. Good reported signal with poor throughput is interference, and no amount of repositioning fixes a congested channel.
Reserve the device's address at the router
ReversibleA DHCP reservation against its MAC address permanently removes the lease-expiry failure mode. This is the correct fix for a device that fails on a schedule, where rebooting only restarts the clock.
Force a fresh association near the intended access point
ReversiblePower-cycle the device beside the node it should use. Mesh systems rarely move a client that has already associated, so a device can sit next to a node while talking to a distant one.
Confirm the router's security mode is one the device supports
ReversibleA router switched to WPA3-only will refuse a WPA2-only device with no useful error, and firmware updates have changed this default. Check this specifically before concluding the hardware has failed.
Verify across the previous drop interval, not across minutes
ReversibleRun the device past the longest interval it previously survived. A fix declared after five minutes on a fault that recurred every two days has proved nothing at all.
Model-specific
What is true of this model and not of its siblings
Generic advice for the product line fails here. Each item below is a property of this specific model family that changes which of the steps above apply to you.
- Model scope
- GA00781. Google Nest/Home device; Matter/Thread role, wired/battery power, subscription and Google Home migration vary.
- Device — compact smart SPEAKER (no screen)
- A small, affordable smart SPEAKER (2nd gen, no display) with Google Assistant for voice control, quick answers and smart-home commands. Modest sound for its size (that is the tier). Mains powered; symptoms are audio/assistant/Wi-Fi.
- Mic mute & groups
- A mic mute switch disables the hotword (an off mic is the usual 'won't respond' cause). It can join speaker groups for multi-room audio and pair with another Mini for stereo.
- Assistant & platform
- Runs on Google Assistant via the Google Home app; some features shift to Gemini over time via updates. Its small speaker is not meant for room-filling music.
- Power path
- Mains adapter into a standard outlet. Switched outlets and outlets on a circuit that trips are the two failure modes that present as device faults. Use the supplied adapter — third-party adapters that supply the right voltage at the wrong current are a common cause of intermittent restarts.
- Wi-Fi
- Joins on 2.4 GHz. A phone on 5 GHz cannot hand credentials to it reliably during setup, and a router that steers clients between bands under one network name will produce intermittent joins that look like a hardware fault.
- Microphone
- Carries a microphone with a hardware mute. A muted microphone is a physical switch state that no app setting overrides, and is the first thing to check for any voice or audio symptom.
- Symptom boundary
- This record covers Google Nest Nest Mini (2nd gen) when it will not stay connected to Wi-Fi. A different symptom on the same hardware, or this symptom on a different Google Nest product line, has its own record with its own causes and its own cited source.
Stop boundary
When this stops being a self-service repair
Continuing past any one of these costs more than the repair saves — in safety, in warranty, or in evidence a technician needs.
- !Reported signal is poor everywhere in the house, including beside the router, which points at the device's own radio rather than at placement.
- !The router cannot be configured — an ISP-supplied unit in a locked mode may need the provider to change band, channel or security settings.
Evidence ledger
Sources behind this answer
Visible sources support the visible claims. Home Product Support records the publisher, the fact used and the review date; community reports can suggest an issue but do not become a published fact on their own.
Where the manufacturer's article stops. Google Nest Help publishes this as "Fix Wi-Fi connection issues for your Google smart speaker or display". Google's own speaker/display Wi-Fi-connection article, more specific than the cross-product one used for the other 2 Nest groups. Verified reachable and title-matched via the Browser tool 2026-08-28. What that article does not carry is the model boundary — it is written for a product line, and GA00781 is the scope applied here. Where a control label, terminal, indicator pattern or reset sequence differs on your unit, the manual for that exact model is the authority, not this page and not the article.
Exact questions
Common follow-ups
My Nest Mini sounds weak / won't respond to voice.+
Two separate things. For weak sound: the Mini is a tiny speaker built for voice and casual listening, so limited bass and volume are the size, not a fault — group it with other speakers or use a Nest Audio for better music. For it not responding: check the microphone mute switch (an off mic stops the hotword), confirm it is online in the Google Home app with Voice Match set up, and restart it (unplug briefly). A muted mic is the most common 'won't respond' cause.
My phone shows full bars in the same room. Why does the device say the signal is poor?+
Because they are not comparable. A phone has a larger antenna, far more transmit power and a battery sized for it. A small smart-home device — particularly a battery one, which throttles its radio to save charge — routinely reports poor signal where a phone reports full. Use the figure the device reports for itself.
The drops happen at almost exactly the same interval. What is that?+
Regularity that precise is almost always the router's DHCP lease. The device loses its address, fails to renew it, and drops until something forces a rejoin. A reservation against its MAC address fixes it permanently; rebooting only restarts the clock.
Do I need to split my 2.4 and 5 GHz networks permanently?+
Not usually. Splitting them is the fastest way to prove whether band steering is the cause, and once proved, most routers allow the device to be pinned to a band without keeping the names separate. Keep the split only if pinning is unavailable.
Signal is good but the video still stutters. What does that mean?+
Good signal with poor throughput is interference, not distance. The 2.4 GHz band is shared with microwaves, cordless phones, baby monitors and every neighbouring network. Moving the router to channel 1, 6 or 11 — whichever is least occupied — addresses this where repositioning does not.
Would a Wi-Fi extender fix this?+
Only if the problem is genuinely range. An extender on a congested channel adds another talker to the same congested channel and can make throughput worse. Establish whether you have a range problem or an interference problem first — they look identical from the app and have opposite fixes.
It sits right next to a mesh node and still reports poor signal.+
It is probably associated with a different node. Mesh systems rarely force a client that has already joined to move, so a device can be inches from one node and talking to one across the house. Power-cycling it beside the intended node forces a fresh association.
My router updated itself and now it will not stay connected.+
Check the security mode first. WPA3-only, IoT client isolation and DNS filtering have all changed defaults across firmware generations, and a device that requires WPA2 will fail against a WPA3-only router with no message that says so.
How many devices can my network actually hold?+
Fewer than most people assume — consumer routers have finite client tables, and exceeding one produces drops with no error anywhere. The tell is that a device drops when a new device joins, and which one drops varies.
Does the metal door it is mounted on matter?+
Considerably. Metal, masonry, foil-backed insulation, wire-reinforced glass and low-emissivity window coatings all attenuate 2.4 GHz far more than plain distance. A large change in reported signal over a short move identifies an obstruction rather than range.
How long should I wait before calling it fixed?+
Longer than the previous drop interval. A device that used to drop every two days and has now run for ten minutes has proved nothing. This is the single most common way an unfixed Wi-Fi fault gets declared solved.
Should I give it a static IP address?+
A DHCP reservation at the router is better than a static address set on the device. The reservation keeps the router in charge of the address pool, so it cannot hand the same address to something else — which is the failure a manually set static address invites.
It shows in my router's client list but the app says offline.+
That is a genuinely useful result. The radio link, the credentials and the band are all fine, so everything in this page about signal and placement is ruled out. What remains is the path from the router onward — DNS filtering, a firewall rule, or the provider's own service.
Is 5 GHz better for this device?+
Not available to it — Nest Mini (2nd gen) joins on 2.4 GHz. That band is more congested but travels further through structure, which is the trade smart-home hardware is designed around. Attempting to force 5 GHz is not a fix here.
Does this answer apply to every Google Nest model?+
No. It is scoped to GA00781. Google Nest/Home device; Matter/Thread role, wired/battery power, subscription and Google Home migration vary.
What should I record before troubleshooting Wi-Fi or disconnecting?+
Record the complete model identifier, exact message or indicator, software/firmware where visible, the operating stage and what still works.
Why is a factory reset not the first step?+
A reset can erase accounts, networks, maps, schedules or preferences without distinguishing Wi-Fi, disconnecting. The ordered checks preserve that evidence.
When should I stop and use qualified service?+
Do not weaken router security for a legacy device without isolation.
Answer for the exact device and software version shown above.