Hey! We’ll fix why your Google Home automation is not triggering. When you can still control devices manually in the Google Home app (or by voice), but Routines, Home & Away, or other Google Home automations don’t run, the cause is usually one of these buckets: starter/condition setup, home/household permissions, presence sensing / location services, device sync / cloud integration, or Wi-Fi stability (especially for plugs/lights on 2.4 GHz).

Quick questions so we don’t guess:
• What kind of automation: time-based (sunset/sunrise), voice starter, sensor starter, or Home & Away (presence-based)?
• Which controller device: Nest Hub/Nest Mini, Pixel/Android phone, iPhone, or multiple?
• Do you see “Automation ran” in Activity/History, or does it look like it never fires?
• Which devices are in the action: smart lights, smart plugs, thermostat, cameras, or third-party services (Hue/SmartThings/Smart Life/Kasa)?
• Any recent change: new router, changed Wi-Fi password, enabled WPA3, moved devices to a guest network, updated the Google Home app, or moved to a new home address/time zone?

Drop those details and I’ll walk you through a reliable “checklist” that fixes most cases of Google Home routines not working.

Great detail — and your symptoms match a classic combo: Google Home Home & Away not working because location/presence sensing is blocked plus a Works with Google integration that needs a refresh (Hue device sync) so the Google Home app thinks devices are offline at the moment the routine tries to run.

Here’s the simple model: Google Home automations run only if the starter fires (sunset/presence/voice), the home has correct address/time zone, and the target device is “reachable” in Google Home (even if it works inside the vendor app). If any piece is stale, you get routines not running or “ran but did nothing.”

We’ll fix this in a safe order:
1) Verify the Home structure, address, and time zone so sunset triggers are correct.
2) Verify presence sensing (location services + permissions + battery optimization) so Home & Away triggers aren’t blocked.
3) Force a clean device sync and refresh Hue so “offline” status disappears.
4) Confirm Wi-Fi basics (2.4 GHz stability, no guest isolation, no random router blocking) so devices stay online.

Yes — mixed devices are fine, but Home & Away can get flaky if one person’s location permissions are restricted, or if the home is set to rely on presence sensing but only one member is “eligible.” Also, sunset/sunrise routines depend on the home address and correct time zone inside Google Home.

Step 1 — Confirm Home address + time zone (fixes sunset routines)
1) Open Google Home app → select your Home → Settings → confirm the home address is correct (not a previous address).
2) On your phone: Settings → Date & time → set Automatic time and Automatic time zone.
3) In the Automation/Routine: open the sunset starter and re-save it (this often refreshes sunrise/sunset calculations after changes).

Step 2 — Check Home & Away settings (presence-based automations)
In Google Home app → Settings → Presence sensing / Home & Away:
• Make sure presence is enabled for the home.
• Confirm which devices are used for presence (phones, Nest hubs, etc.).
• Ensure you and your partner are both added as home members and have the right access level (not “limited”).

Next we’ll fix the #1 real-world blocker: location permission + battery optimization.

That’s almost certainly it. Google Home Home & Away depends on background location updates. If Android battery optimization pauses Google Home (or Google Play services location updates), the presence starter can’t fire consistently — so you’ll see Google Home automations not running even though everything else “works.”

Step 3 — Fix location permissions + battery optimization (most important)
On your Pixel (Android):
1) Settings → Apps → Google Home → Permissions → Location → set to Allow all the time.
2) Settings → Apps → Google Home → Battery → set to Unrestricted (or “Don’t optimize”).
3) Make sure Location is ON system-wide and that “precise location” is enabled if your phone offers it.

On iPhone:
1) Settings → Privacy & Security → Location Services → Google Home → set to Always (if available) and enable Precise Location.
2) Allow Background App Refresh for Google Home (so it can update presence).

After doing that, toggle Home/Away once manually (Home → Away → Home) and give it a full test: leave the area and see if it flips within a few minutes. While we wait, we’ll also fix the “offline in Google Home” symptom so routines can actually control your lights every time.

Exactly — when a device works in the vendor app but appears offline in Google Home, it’s usually a stale Works with Google link, a cached device state, or the integration token needs a refresh. That will absolutely cause a Google Home Routine not triggering the action, because the automation “fires” but can’t reach the target device in Google’s view.

Step 4 — Force a clean device refresh (fastest fix)
1) In the Google Home app, pull down to refresh the home screen (this forces a device state refresh).
2) Say: “Hey Google, sync my devices.” (this triggers a sync for connected services).
3) Check Activity/History in Google Home after the routine time: if it says it ran, but nothing happened, that’s usually device availability/sync.

Step 5 — Re-link Hue (if “sync devices” doesn’t fix it)
1) Google Home app → Settings → Works with Google → find Philips Hue → disconnect/unlink.
2) Reconnect Hue and re-assign devices to the correct rooms.
3) After re-linking, run the routine manually once (tap “Play”/Run) to confirm actions execute instantly.

We’ll also do one “silent killer” check next: Wi-Fi and router settings that cause brief disconnects right at routine time (2.4 GHz stability, guest isolation, WPA3 transition issues).

Yes on both. Two very common causes of Google Home automation not triggering consistently are: (1) guest network isolation (devices can’t talk locally and sometimes get limited connectivity), and (2) WPA3 mixed/transition mode confusing older IoT devices so they drop off briefly. A routine can “fire” but fail if the device is offline at that exact moment.

Step 6 — Stabilize Wi-Fi for smart devices (especially 2.4 GHz)
1) Move automation-critical devices (smart plugs, bulbs, hubs/bridges) off guest Wi-Fi and onto the main network. Guest mode often has “client isolation” or blocks LAN discovery.
2) If you use WPA3 “mixed mode,” test switching to WPA2 temporarily. If offline states disappear, keep WPA2 for IoT or use WPA3 only if every device supports it cleanly.
3) Keep IoT devices on strong 2.4 GHz coverage (better range). If your router has a setting to reduce band steering aggressiveness, that can prevent dropouts.
4) Reboot in a clean order: router/modem → Hue Bridge (if used) → Nest Hub/Nest Mini → then test the routine again.

Optional “advanced” checks if you still see weirdness
• If your router has AP isolation / “Block LAN access,” keep it OFF for devices you want automations to control.
• If you have two routers (ISP modem + router), avoid double NAT by using bridge mode or AP mode appropriately.
Next we’ll do one more high-impact step: refresh the Google Home app itself so cached automations and device states don’t keep returning.

Smart move — a surprising number of “not triggering” cases are actually a routine that’s disabled, limited to the wrong device, or has a condition that’s never true. Also, two automations can fight each other (one turns lights on, another immediately turns them off).

Step 7 — Audit the automation (starter → conditions → actions)
In the Google Home app:
1) Go to Automations (or Routines) and open the one that’s failing.
2) Confirm it’s enabled (toggle ON) and tied to the correct Home (some people accidentally edit a different home/household).
3) Check the starter (sunset/time/presence). For sunset: confirm it’s “At sunset” for your home address, and try re-saving it.
4) If there are conditions (only if someone is home / only at night / only on weekdays), temporarily remove conditions to test.
5) Review the actions: make sure it’s controlling the correct lights (sometimes devices duplicate after a re-link).

Step 8 — Check Activity/History to see what failed
After a missed trigger, open Home app Activity and look for the automation event. If it shows “ran” but actions failed, that points to device sync/connectivity. If it never shows, the starter (time/presence) didn’t fire — permissions/time zone are the usual suspects.

If you want an extra reliability boost, we can also create a “fallback”: a second routine at a fixed time (e.g., 10 minutes after sunset) so your lights still come on even if the sunset calculation glitches.

Clearing cache is a great “next step” before you do anything drastic — especially if the Google Home app UI gets stuck showing offline devices or edits don’t seem to save properly.

Before reinstalling (fast ladder)
• Update the Google Home app and your Nest Hub/Nest Mini firmware (updates can quietly fix automation bugs).
• Android: Settings → Apps → Google Home → Storage → Clear cache (not data yet). Restart the phone.
• Re-run “sync my devices” after any integration changes (Hue/SmartThings/Smart Life).
• Re-check router changes didn’t revert (guest Wi-Fi, WPA mode, isolation toggles).

When reinstall is worth it
• Automations won’t save, buttons don’t respond, or the app keeps showing the wrong home/household state.
• You see persistent “offline” status for devices that are online in every other app, even after a sync.

If you reinstall, sign back into the same Google account, confirm you’re in the correct Home, then test one automation at a time so you can tell exactly what fixed your Google Home routines not working problem.

Love it — that’s the exact “full fix” sequence for most cases where Google Home automations aren’t triggering.

Summary: verify home address/time zone for sunset routines, enable presence sensing with correct location permissions (and disable battery restrictions), keep automation devices on the main Wi-Fi (avoid guest isolation), use a stable Wi-Fi security mode for IoT (often WPA2), refresh Works with Google links (Hue/SmartThings/etc.) with sync my devices, and audit routine conditions that block starters.

Want help tuning your setup for maximum reliability (multiple phones, multiple speakers, mixed iOS/Android, or complex starters)? Open the chat and an expert will guide you in real time.