Direct answer
For the Nest Hub Max, device power, local radio/LAN, hub/controller and provider cloud should be separated. First, check power/status and control another device on the same platform.
What this covers
- Nest Hub Max (GA00639)
- Google Nest/Home device; Matter/Thread role, wired/battery power, subscription and Google Home migration vary.
- The specific fault this record addresses: is offline or unavailable
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
The device lost power rather than lost network
What separates it The status indicator is dark, not blinking an error. A device that is genuinely offline usually still shows something; a device with no power shows nothing at all and is easy to misread as a connectivity fault.
How to confirm Check the outlet, transformer or battery directly rather than through the app. On a switched outlet, confirm the switch. On a shared circuit, confirm nothing else tripped a breaker.
- 2
The router was replaced, renamed or its password changed
What separates it Several devices went offline at once, or the device went offline on a date that matches an ISP visit or a router change. Devices hold credentials and cannot be told about a change; they simply stop connecting.
How to confirm Compare the number of offline devices against the number of devices on that network. One device offline is a device problem. Everything offline is a network problem, and re-adding devices one at a time is wasted work until the network is settled.
- 3
The device is at the edge of usable signal, not out of range
What separates it It works after a reboot and drops again hours or days later, or it works in summer and fails in winter when doors and windows stay shut. Marginal signal is intermittent by nature; genuine out-of-range is consistent.
How to confirm Read the signal strength the device itself reports in the app — not the phone's bars in the same room. Move the device or add a mesh node and see whether the drop interval lengthens.
- 4
The router assigned a new address and the device did not recover
What separates it The device reappears after a reboot and disappears after roughly the DHCP lease interval, or after a power cut that restarted the router before the device.
How to confirm Check the router's client list for two entries with the device's name, or for a lease that expired without renewing. A DHCP reservation for the device's MAC address removes this failure mode permanently.
- 5
The provider's own service is degraded
What separates it Everything local is fine, the device's status light indicates a normal connection, and other people report the same thing at the same time. Nothing you change at home has any effect.
How to confirm Check the provider's status page before touching anything. Devices reset and re-added during a provider outage produce a second, real problem on top of the first.
- 6
The router's client isolation or a new firewall rule is blocking it
What separates it The device joined successfully in the past and now cannot, with no change at the device end. Router firmware updates can enable IoT isolation, band steering or DNS filtering that was previously off.
How to confirm Compare the router's current settings against what changed. A router that auto-updated on the date the device went offline is the strongest single clue available.
- 7
The device is on a network that changed band behaviour
What separates it A mesh system or router firmware update enabled band steering, and the device now receives a 5 GHz steer it cannot honour. It appears offline while the router believes it is connected.
How to confirm Look for the device in the router's client list. Present in the client list but offline in the app is a very different problem from absent in both.
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.
- How many devices are offline, and whether they share a hub, a band, a circuit or an outdoor location. One offline device and all of them offline are different investigations.
- The last-seen timestamp for each offline device, which frequently identifies the shared event that caused it.
- What changed on or near that date: router replacement, ISP visit, firmware update, password change, house guest, power cut, weather.
- The device's status indicator pattern right now, read at the device rather than in the app.
- The signal strength the device reports for itself, which is not the same as the phone's signal in that room.
- Whether the device still appears in the router's connected-client list. Present there but offline in the app narrows the fault to the provider path.
Count what is offline before investigating any one device
ReversibleOne device offline out of many is a device fault. All of them offline is a network or provider fault, and every minute spent on an individual accessory is wasted. This single count decides which half of this page applies to you.
Check the provider's status page
ReversibleA provider-side outage cannot be fixed at home, and devices reset or re-added during one create a second real problem on top of the first. This check costs thirty seconds and prevents the most expensive mistake on this page.
Verify power at the device, not in the app
ReversibleLook at the status indicator on the hardware. A dark indicator is a power problem; a blinking one is a network problem. The app cannot distinguish these because it has lost contact either way.
Look for the device in the router's client list
ReversiblePresent in the client list but offline in the app narrows the fault to the path between the router and the provider. Absent from both means the device never rejoined the local network at all.
Establish what changed on the last-seen date
ReversibleRouter replacement, an ISP visit, a firmware update, a password change or a power cut on that date explains more offline devices than every device-side check combined. Devices hold credentials and cannot be told a network changed.
Restore power and network in the correct order
ReversibleRouter first, then hub, then accessories, allowing each to come fully up before starting the next. Restarting everything at once produces address conflicts that look exactly like the fault you are trying to clear.
Reserve the device's address at the router
ReversibleA DHCP reservation against the device's MAC address removes the lease-expiry failure mode permanently. This is the fix for a device that comes back on reboot and disappears again days later.
Re-add only the accessory that actually failed
Reset / data riskRemoving a whole home or hub to recover one accessory discards every automation, permission and share attached to it. Re-add the single failed device and confirm both local and remote control before touching anything else.
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
- GA00639. Google Nest/Home device; Matter/Thread role, wired/battery power, subscription and Google Home migration vary.
- Device — smart DISPLAY with camera
- A larger smart display with a touchscreen, speaker and a built-in CAMERA (for video calls, Face Match, and home monitoring) — powered by Google Assistant. Mains powered. So its symptoms are display/assistant/camera and Wi-Fi, not a phone's.
- Camera & privacy
- The camera enables Google Duo/Meet calls and can act as a Nest camera for home monitoring; a physical switch disables the camera and mic — if the camera 'doesn't work', check that switch is not off. Home monitoring history needs Nest Aware.
- Assistant & platform
- Runs on Google Assistant via the Google Home app; note Google has been transitioning some Assistant features to Gemini, and older Nest displays' feature set can change with updates.
- 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 Hub Max when it is offline or unavailable. 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.
- !The provider confirms an account-side or service-side fault — no local change will resolve it and repeated re-adds risk locking the device.
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". Same speaker/display connection article; offline status for this device class is a Wi-Fi-connection symptom. 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 GA00639 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
The camera on my Nest Hub Max isn't working.+
First check the physical camera/mic switch on the back or top — sliding it off disables the camera and microphone for privacy, and this is the most common reason the camera appears dead (the screen usually shows a camera-off indicator). Slide it back on. Then confirm the Hub Max is on Wi-Fi and updated in the Google Home app, and that permissions for video calls/home monitoring are set. Home-monitoring recording history requires Nest Aware; live view and calls do not.
Everything went offline at once. Where do I start?+
At the router or the hub, not at any device. Simultaneous failure across unrelated hardware is the signature of a shared dependency, and re-adding devices one by one before that dependency is fixed is work you will have to repeat.
Only one device is offline and the rest are fine. What does that rule out?+
It rules out the router, the internet connection and the provider — all of which would take the others with them. What remains is that device's own power, its own radio path, and its own account state.
The device comes back when I reboot it and drops again days later.+
That interval is the clue. A drop that recurs on a roughly fixed schedule usually tracks the router's DHCP lease. A reservation for the device's MAC address at the router removes it permanently, where rebooting only resets the clock.
Does a weak signal show as offline or as slow?+
Both, in sequence. Marginal signal degrades first — slower live view, late notifications, missed events — and only then drops out. A device that went straight from perfect to absent is more likely a power or credential problem than a signal one.
Why did my devices go offline after I got a new router?+
Because they still hold the old network's name and password, and nothing can tell them otherwise. Setting the new router to the old network name and password is often faster than re-adding every device, and is worth doing before the first re-add.
The app says offline but the light on the device looks normal.+
Then the local link is probably fine and the break is further along — between the router and the provider, or at the provider itself. Check the provider's status page and the router's internet connection before doing anything to the device.
Should I reset the device?+
Not as a first step, and not during a provider outage. A reset discards local settings and, on a shared device, can discard other people's access. Establish what is actually broken first — reset is a recovery action, not a diagnostic one.
Is it safe to delete the home to fix one accessory?+
No, and it is rarely necessary. Deleting a home or hub destroys every automation, permission and share attached to it. Remove and re-add the single failed accessory instead.
My router updated itself and now the device will not connect.+
Router firmware updates can turn on band steering, IoT client isolation or DNS filtering that was previously off. Compare the current settings against the defaults for those three specifically — a device that worked for a year and stopped on an update date is describing a router change, not a device failure.
In what order should I restart things?+
Router first, fully up, then the hub, fully up, then accessories. Restarting everything simultaneously produces address conflicts and rejoin storms that look exactly like the original fault, which is how a five-minute check turns into an afternoon.
How long should I wait before deciding it did not come back?+
Give the router several minutes to finish handing out addresses, and battery devices longer still — several report on a duty cycle and will not check in immediately. Judging at thirty seconds produces false failures and unnecessary resets.
Does the number of devices on my network matter?+
It can. Consumer routers have finite client tables, and a household with dozens of connected devices can exceed one. The symptom is that a device drops whenever a new one joins, which reads as random until the pattern is spotted.
The device shows in my router's client list but offline in the app.+
That is a useful, specific result: the device joined the local network successfully, so credentials, band and signal are all fine. The break is between the router and the provider — DNS filtering, a firewall rule, or the provider's own service.
Does this answer apply to every Google Nest model?+
No. It is scoped to GA00639. Google Nest/Home device; Matter/Thread role, wired/battery power, subscription and Google Home migration vary.
What should I record before troubleshooting offline or unavailable?+
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 offline, unavailable. The ordered checks preserve that evidence.
When should I stop and use qualified service?+
Protect security devices and avoid deleting the entire home for one offline accessory.
Answer for the exact device and software version shown above.