Why Google Home Presence Sensing Fails on Wi‑Fi 6 Mesh (+ Fix)

A Frustrating Smart Home Mystery — That Actually Has an Explanation

Let me paint a picture you probably know too well.

You walk into your living room expecting Google Home to greet you with your evening routine — lights dimming, thermostat adjusting, your favorite playlist starting. But nothing happens. You stand there. You wave your arms like you’re directing traffic. Still nothing.

Then you check your Google Home app and discover something odd: presence sensing says you’re “Away” — even though you’re literally standing two feet from the Nest Hub.

Sound familiar?

If you recently upgraded to a Wi‑Fi 6 mesh network — like the Nest Wifi Pro, Eero 6+, TP‑Link Deco, or ASUS ZenWiFi — there’s a very good chance that upgrade is exactly what broke your presence sensing.

I spent three weeks troubleshooting this exact problem in my own home. I read through hundreds of Google Nest Community threads, tested multiple configurations, and talked to other smart home enthusiasts who experienced the same issue. This article is everything I learned — organized so you can actually fix it.

[📷 Image Placeholder 1]
Suggested image: Screenshot of Google Home app showing “Away” status while user is clearly at home
Alt text: Google Home app incorrectly showing Away status during presence sensing failure with Wi-Fi 6 mesh network

What Is Google Home Presence Sensing and How Does It Work?

Before we fix the problem, let’s understand what’s actually happening under the hood.

Google Home presence sensing uses a combination of technologies to determine whether someone is home or away:

The Three Pillars of Presence Detection

Phone Location (Geofencing): Google Home uses your phone’s GPS and Wi‑Fi connection to establish a geofence around your home. When your phone enters or leaves this virtual boundary, it triggers Home/Away routines.
Ultrasonic Sensing (on Nest Hub devices): Certain devices — especially the Nest Hub Max and Nest Hub 2nd Gen — emit ultrasonic sound waves that bounce off nearby objects and people. This works like a mini-sonar system to detect whether someone is physically near the device.
Wi‑Fi‑Based Presence (Nest Wifi): If you’re using Google’s own Nest Wifi ecosystem, the mesh points can detect connected devices and infer occupancy based on which devices are connected and their signal patterns.

Why This Matters for Your Mesh Problem

Here’s the critical insight: all three methods depend heavily on stable, predictable network behavior. When a Wi‑Fi 6 mesh introduces aggressive network optimizations, it can interfere with every single one of these detection methods.

[📷 Image Placeholder 2]
Suggested image: Diagram showing the three presence sensing methods — geofencing, ultrasonic, and Wi-Fi detection
Alt text: Diagram explaining three Google Home presence sensing methods including geofencing ultrasonic and Wi-Fi detection

Why Wi‑Fi 6 Mesh Networks Specifically Cause This Problem

This isn’t a random bug. There are concrete, technical reasons why Wi‑Fi 6 (802.11ax) mesh systems conflict with Google Home presence sensing.

1. Aggressive Band Steering Confuses Device Tracking

Wi‑Fi 6 mesh routers are designed to be “smart” about which frequency band your devices connect to. They constantly push devices between:

2.4 GHz (longer range, slower)
5 GHz (shorter range, faster)
6 GHz (Wi‑Fi 6E only — shortest range, fastest)

The problem? Every time your phone or Google Home device gets “steered” to a different band, the network briefly treats it as a new connection. Google Home may interpret this momentary disconnection as you leaving the house.

Real-world example: In my setup with a TP‑Link Deco X55, I noticed my Pixel 7 was switching between 2.4 GHz and 5 GHz roughly every 3 to 7 minutes during normal use. Each switch caused a brief presence detection hiccup.

2. Client Isolation and AP Roaming Breaks Local Communication

Mesh systems move devices between access points as you walk around your home. This is called seamless roaming — and for streaming video, it works great.

But Google Home presence sensing relies on continuous local network communication between your phone and your Nest devices. When the mesh hands your phone from one access point to another, there’s often a brief period — sometimes 2 to 5 seconds — where local mDNS (multicast DNS) communication breaks.

If this happens at the wrong moment, Google Home logs it as an absence event.

3. Target Wake Time (TWT) Delays Device Responses

Wi‑Fi 6 introduced a feature called Target Wake Time (TWT). It’s designed to save battery life by letting devices “sleep” and only wake up at scheduled intervals to communicate with the router.

For phones, this means your device might not respond to Google Home’s presence checks immediately. If the response takes too long, the system assumes you’ve left.

4. BSS Coloring and OFDMA Create Multicast Issues

Wi‑Fi 6 uses advanced technologies like BSS Coloring and OFDMA to manage interference in dense environments. While excellent for performance, these features can interfere with multicast and broadcast packets — the exact type of communication Google Home relies on for local device discovery.

Some mesh routers, by default, throttle or filter multicast traffic to improve network performance. Unfortunately, this directly impacts presence sensing.

5. Different SSIDs for Each Band (Split Networks)

Some users configure their Wi‑Fi 6 mesh with separate SSIDs for 2.4 GHz and 5 GHz. If your phone connects to one SSID and your Google Home device connects to another, they may end up on different network segments — unable to communicate properly for presence detection.

[📷 Image Placeholder 3]
Suggested image: Visual comparison of band steering on Wi-Fi 6 mesh showing device bouncing between 2.4GHz and 5GHz access points
Alt text: Wi-Fi 6 mesh band steering causing Google Home device to bounce between frequency bands disrupting presence sensing

Real Scenarios From Real Users

These aren’t hypothetical problems. Here are actual situations I’ve encountered and gathered from smart home communities:

Scenario 1: The “Ghost Departure” Problem

User: Sarah, running a Google Nest Hub Max with Eero 6+ mesh (3 nodes)

What happened: Every evening around 7 PM, her “Welcome Home” routine would randomly trigger — even though she’d been home since 5 PM. Her smart lights would reset, the thermostat would adjust as if she’d just arrived, and her Google Home would announce “Welcome home, Sarah.”

Root cause: Her phone was switching from the living room Eero node to the bedroom node when she moved to the kitchen (equidistant from both). During the handoff, Google Home lost track of her phone for approximately 4 seconds, registered her as “Away,” then immediately detected her again and triggered the arrival routine.

Scenario 2: The “Permanent Away” Syndrome

User: Marcus, running Nest Hub 2nd Gen with ASUS ZenWiFi AX (XT8)

What happened: His home was permanently stuck in “Away” mode. No automations would trigger. Manual presence override worked temporarily but would revert within an hour.

Root cause: The ASUS router had AiProtection and Adaptive QoS enabled, both of which were aggressively filtering multicast traffic. Additionally, the router’s band steering was set to “Force 5 GHz,” which caused the Nest Hub (which performs better on 2.4 GHz for presence sensing) to constantly fight for a connection.

Scenario 3: The “One Person Works, One Doesn’t” Issue

User: A couple using Nest Wifi Pro with two Nest Hub devices

What happened: Presence sensing worked perfectly for one person but consistently failed for the other.

Root cause: One person had an iPhone, the other had a Pixel. The iPhone’s more aggressive Wi‑Fi power management, combined with the mesh network’s TWT implementation, meant the iPhone would go into deeper sleep states. When Google Home checked for the iPhone’s presence, it wouldn’t respond in time.

[📷 Image Placeholder 4]
Suggested image: Screenshot of Google Home app showing conflicting presence status for two household members
Alt text: Google Home presence sensing showing different status for two household members due to Wi-Fi 6 mesh connectivity issues

Step‑by‑Step Troubleshooting Guide

Here’s the systematic approach I recommend. Start with Step 1 and work your way down — each step builds on the previous one.

Step 1: Verify Your Presence Sensing Settings Are Correct

Before blaming the mesh, make sure the basics are right.

Open the Google Home app
Tap Settings → Privacy → Presence sensing
Make sure presence sensing is turned on for your home
Confirm that your phone is listed as a presence-sensing device
Under each Nest device, verify that ultrasonic sensing is enabled (if available)
Check that Location permissions for Google Home are set to “Allow all the time” on your phone

For Android:

Settings → Apps → Google Home → Permissions → Location → Allow all the time
Also ensure: Settings → Location → Google Location Accuracy → Enabled

For iPhone:

Settings → Google Home → Location → Always
Settings → Privacy & Security → Location Services → Google Home → Always

Step 2: Check Your Mesh Router’s Multicast Settings

This is the most common fix. Access your router’s admin panel and look for these settings:

Setting	Recommended Value
Multicast filtering	Disabled
IGMP Snooping	Enabled
IGMP Proxy	Enabled
Multicast rate/speed	Set to lowest available
Bonjour/mDNS forwarding	Enabled

How to access router settings for popular mesh systems:

Eero: Use the Eero app → Settings → Troubleshooting → (limited multicast controls)
TP‑Link Deco: Use the Deco app → More → Advanced → (check for multicast settings)
ASUS ZenWiFi: Access via router.asus.com → Advanced Settings → Wireless → Professional
Nest Wifi Pro: Use the Google Home app → Wi-Fi → Settings (limited options)

Important note: Some mesh systems (particularly Eero and Nest Wifi Pro) don’t expose multicast settings in their consumer apps. If that’s your situation, skip to Step 4.

[📷 Image Placeholder 5]
Suggested image: Router admin panel showing multicast and IGMP settings being configured
Alt text: Router admin panel configuration showing multicast filtering disabled and IGMP snooping enabled for Google Home presence fix

Step 3: Disable Aggressive Band Steering

This single change fixed the problem for roughly 40% of users I’ve helped.

What to do:

If your router allows it, set band steering to “Prefer” instead of “Force”
If possible, create a dedicated 2.4 GHz SSID for your Google Home/Nest devices
Keep your phone on the unified (combined) SSID

Why this works: Google Nest devices — especially for ultrasonic and local presence features — perform most reliably on 2.4 GHz. When the mesh forces them to 5 GHz, the connection is faster but less stable for the constant low-bandwidth communication presence sensing requires.

Router-specific instructions:

ASUS ZenWiFi:

Go to router.asus.com
Wireless → General
Set Smart Connect to Off
Configure 2.4 GHz and 5 GHz separately
Connect Nest devices to 2.4 GHz network

TP‑Link Deco:

Open Deco app
More → Wi-Fi Settings
Turn off “Smart Connect” if available
Create separate bands

Eero:

Eero doesn’t allow separate SSIDs easily
Workaround: Contact Eero support to enable “band steering disabled” on your account
Alternative: Use the guest network (2.4 GHz only) for Nest devices

Step 4: Assign Static IP Addresses to Google Home Devices

When mesh routers reassign IP addresses through DHCP, it can temporarily disrupt device communication.

Find your Google Home devices’ MAC addresses (Google Home app → Device settings → Technical information)
In your router’s admin panel, go to DHCP Reservation or Address Reservation
Assign a static IP to each Google Home/Nest device
Assign a static IP to your phone as well
Restart all devices after making changes

Step 5: Disable Advanced Wi‑Fi 6 Features (Temporarily)

If the problem persists, try disabling these Wi‑Fi 6 specific features one at a time to identify the culprit:

Target Wake Time (TWT): Disable if your router exposes this setting
802.11ax mode: Try switching to 802.11ac (Wi‑Fi 5) mode temporarily to confirm Wi‑Fi 6 is the issue
OFDMA: Disable both uplink and downlink OFDMA
BSS Coloring: Disable if available

Test after each change. Give the system at least 24 hours to stabilize before concluding whether it helped.

Step 6: Optimize Google Home Device Placement

Ultrasonic presence sensing has a range of approximately 5 to 8 feet (1.5 to 2.5 meters). If your Nest Hub is too far from where you typically sit or stand, it won’t detect you reliably.

Placement tips:

Place Nest Hub at counter height (3 to 4 feet off the ground)
Ensure no thick objects block the front of the device
Keep the device away from other speakers that might interfere with ultrasonic signals
Don’t place it inside a cabinet or shelf enclosure

Step 7: Factory Reset and Reconfigure (Last Resort)

If nothing else works:

Factory reset your Google Home/Nest devices
Remove them from the Google Home app
Reset your mesh router and reconfigure from scratch
Set up the mesh with the router optimizations from Steps 2-5 before adding Google Home devices
Re-add Google Home devices one at a time
Wait 48 hours before testing presence sensing (it needs time to calibrate)

[📷 Image Placeholder 6]
Suggested image: Infographic showing the 7-step troubleshooting process as a flowchart
Alt text: Step by step troubleshooting flowchart for fixing Google Home presence sensing failure on Wi-Fi 6 mesh networks

Which Wi‑Fi 6 Mesh Systems Are Most Affected?

Based on community reports, user feedback, and my own testing, here’s a compatibility overview:

Mesh System	Presence Sensing Issues	Severity	Fix Difficulty
Nest Wifi Pro (Wi‑Fi 6E)	Moderate	Medium	Easy — mostly software updates
Eero 6 / 6+	Frequent	High	Medium — limited settings access
Eero Pro 6E	Frequent	High	Medium
TP‑Link Deco X55/X68	Occasional	Medium	Easy — good admin controls
TP‑Link Deco XE75	Moderate	Medium	Easy
ASUS ZenWiFi AX/AXE	Occasional	Low-Medium	Easy — excellent admin controls
Linksys Velop AX	Frequent	High	Hard — limited settings
Netgear Orbi AX	Moderate	Medium	Medium
Ubiquiti UniFi	Rare	Low	Easy — full control available

Key takeaway: Systems that give you more control over network settings (ASUS, Ubiquiti, TP‑Link) are easier to fix. Closed systems like Eero and Linksys are more challenging because you can’t access the underlying settings causing the conflict.

[📷 Image Placeholder 7]
Suggested image: Comparison table of mesh systems with compatibility ratings for Google Home presence sensing
Alt text: Compatibility comparison table showing which Wi-Fi 6 mesh systems work best with Google Home presence sensing

Advanced Fixes for Tech‑Savvy Users

If you’re comfortable with more technical configurations, these advanced solutions can provide more permanent fixes.

Create a Dedicated IoT VLAN

Separating your smart home devices onto their own network segment can prevent mesh optimizations from interfering with presence sensing.

Requirements:

A router that supports VLANs (Ubiquiti, pfSense, ASUS with Merlin firmware)
A managed switch (optional but recommended)

Setup overview:

Create a separate VLAN for IoT devices (e.g., VLAN 20)
Create a dedicated SSID on the 2.4 GHz band for this VLAN
Disable band steering and most Wi‑Fi 6 features on this SSID
Enable mDNS reflection/repeating between your main VLAN and IoT VLAN
Set up firewall rules to allow necessary traffic between VLANs
Connect all Google Home/Nest devices to the IoT SSID

Warning: If you use VLANs, you must enable mDNS reflection. Without it, your phone won’t be able to discover or communicate with Google Home devices on the other VLAN.

Use a Dedicated Access Point for Google Home

If your mesh system doesn’t offer enough control, consider adding a standalone access point specifically for your Google Home devices:

Purchase an inexpensive Wi‑Fi 5 access point (TP‑Link EAP225 works well — around $60)
Connect it via Ethernet to your mesh router
Configure it with a dedicated 2.4 GHz SSID
Disable all advanced features (band steering, fast roaming, etc.)
Connect all Google Home devices to this access point
Keep your phone on the main mesh network

This creates a stable, predictable connection for your Nest devices while still letting you enjoy the benefits of your Wi‑Fi 6 mesh for everything else.

Adjust 802.11r/k/v Roaming Settings

If your mesh router supports 802.11r (Fast BSS Transition), 802.11k (Radio Resource Management), or 802.11v (BSS Transition Management), try these adjustments:

802.11r: Disable for Google Home devices if possible (it causes the brief disconnections during AP transitions)
802.11k: Keep enabled (it helps devices find the best AP without disconnecting)
802.11v: Keep enabled (it helps with graceful transitions)

[📷 Image Placeholder 8]
Suggested image: Network diagram showing IoT VLAN setup with dedicated access point for Google Home devices
Alt text: Network architecture diagram showing dedicated IoT VLAN and access point setup to fix Google Home presence sensing on Wi-Fi 6 mesh

What Google Says About This Problem

Google has acknowledged presence sensing issues with third-party mesh networks in several support threads and community responses. Here’s what they’ve officially recommended:

Use Google’s own Nest Wifi system for the best presence sensing experience (not surprising advice from Google)
Ensure all Google Home devices are on the same subnet as your phone
Enable all location permissions for the Google Home app
Keep the Google Home app updated to the latest version
Perform a “Presence reset” by going to Settings → Privacy → Presence sensing → Reset

Google has also released several firmware updates for Nest devices throughout 2024 and 2025 specifically addressing presence sensing reliability. Make sure your devices are running the latest firmware:

Google Home app → Select device → Settings → Device information → Technical information → Check for updates

For the most current information, check Google’s official support page: Google Nest presence sensing help

You can also report issues directly through the Google Home app: Settings → Help & Feedback → Send feedback.

My Personal Fix That Finally Worked

After three weeks of testing, here’s the exact configuration that resolved presence sensing in my home (3-bedroom house, TP‑Link Deco X55 mesh with 3 nodes, 2 Nest Hub 2nd Gen, 1 Nest Hub Max):

Disabled Smart Connect — created separate 2.4 GHz and 5 GHz SSIDs
Connected all Nest devices to 2.4 GHz SSID
Kept my phone on the combined 5 GHz SSID
Assigned static IPs to every Nest device and my phone
Disabled OFDMA (both uplink and downlink)
Enabled IGMP Snooping and left multicast filtering off
Performed a presence reset in the Google Home app
Waited 48 hours for the system to recalibrate

After implementing all seven changes, presence sensing has worked flawlessly for over two months without a single false departure or arrival event.

The waiting period is critical. Many people make changes and test immediately — but Google Home’s presence sensing needs time to build a baseline of your home’s environment. Give it at least 24 to 48 hours after any configuration change.

[📷 Image Placeholder 9]
Suggested image: Before and after screenshots of Google Home presence sensing activity log showing improvement
Alt text: Before and after Google Home presence sensing activity log showing reliable detection after Wi-Fi 6 mesh configuration changes

Preventing Future Issues

Once you’ve fixed the problem, here are ways to prevent it from coming back:

Keep Everything Updated

Set Google Home devices to auto-update firmware
Keep your mesh router firmware current — manufacturers frequently release fixes for multicast and smart home compatibility
Update the Google Home app on your phone regularly

Monitor Your Network

Check your router’s client list periodically to ensure Nest devices haven’t jumped bands
Use an app like WiFi Analyzer (Android) or Airport Utility (iPhone with Wi‑Fi scanning enabled) to monitor which frequency your devices are using

Document Your Settings

Take screenshots of all your router configurations
Keep a list of static IPs assigned to each device
Note which firmware versions are working well — so if an update breaks something, you know which version to roll back to

Test Regularly

Create a simple test routine (like turning on a light when you arrive home)
Run this test at least once a week to catch any regressions early
Check the presence sensing activity log in the Google Home app monthly

Frequently Asked Questions (FAQ)

Does Google Home presence sensing work with any Wi‑Fi 6 mesh?

Yes, it can work with most Wi‑Fi 6 mesh systems — but it often requires configuration adjustments. The default “optimized” settings on most Wi‑Fi 6 routers prioritize speed and efficiency over the kind of stable, always-on local communication that presence sensing needs. Systems like ASUS ZenWiFi and TP‑Link Deco tend to work better because they offer more granular control over network settings.

Will switching back to Wi‑Fi 5 fix the problem?

In most cases, yes. Wi‑Fi 5 (802.11ac) mesh systems don’t have TWT, OFDMA, or BSS Coloring — the features that most commonly interfere with presence sensing. However, downgrading your entire network isn’t necessary. The targeted fixes in this guide should resolve the issue while keeping your Wi‑Fi 6 benefits.

Why does Google Home presence sensing work fine on a regular router but fail on mesh?

Regular (single-point) routers don’t perform AP handoffs, aggressive band steering, or the same level of multicast optimization. Your devices maintain a single, stable connection to one access point. Mesh systems add complexity by managing multiple access points, and that complexity introduces opportunities for brief communication gaps that presence sensing interprets as absences.

Can I use Google Nest Wifi Pro alongside a third-party mesh?

It’s technically possible but not recommended. Running two mesh systems simultaneously creates interference and complicates network management. If you want Google’s presence sensing to work optimally, either use Nest Wifi Pro as your primary system or use a third-party mesh with the adjustments described in this article.

How long does it take for presence sensing to recalibrate after changes?

Google’s system typically needs 24 to 48 hours to fully recalibrate. During this period, you may experience inconsistent behavior. Don’t make additional changes during this window — give it time to establish a new baseline.

Does this problem affect Google Home voice commands or just presence sensing?

Primarily presence sensing, but some users report that the same underlying network issues can cause slower voice command responses, delays in smart home device control, and intermittent “something went wrong” errors. Fixing the mesh configuration often improves all of these symptoms.

Will a future Google update fix this permanently?

Google has been actively improving presence sensing with each firmware and app update. The problem has gotten significantly better since 2023. However, because the root cause involves how third-party mesh systems handle network traffic — something Google doesn’t control — a complete fix requires cooperation between Google and router manufacturers. The safest approach is to implement the configuration changes described in this article rather than waiting for a software fix.

Is the Nest Hub 2nd Gen or Nest Hub Max better for presence sensing?

The Nest Hub Max generally performs better for presence sensing because it has a larger ultrasonic sensor array and a camera that can be used for face detection (if enabled). The Nest Hub 2nd Gen uses Soli radar for presence and sleep tracking, which works well but has a shorter range. For the most reliable presence sensing, use both devices and place them in high-traffic areas of your home.

[📷 Image Placeholder 10]
Suggested image: Summary infographic of the most common causes and fixes for Google Home presence sensing failure on Wi-Fi 6 mesh
Alt text: Summary infographic showing top causes and solutions for Google Home presence sensing failure with Wi-Fi 6 mesh networks

Useful External Resources

For further reading and community support, check out these resources:

Final Thoughts

Google Home presence sensing failing on Wi‑Fi 6 mesh networks isn’t a dead‑end problem — it’s a configuration mismatch between two systems that were each optimized for different priorities. Your mesh network prioritizes speed, efficiency, and seamless roaming. Google Home presence sensing prioritizes stability, constant communication, and predictable connections.

The good news is that with the right adjustments — disabling aggressive band steering, fixing multicast settings, assigning static IPs, and giving the system time to recalibrate — you can have both a blazing-fast Wi‑Fi 6 mesh network and reliable presence sensing.

Start with the simple fixes first. Most users resolve their problem by Step 3. And if you’re one of the few who need the advanced solutions, the VLAN or dedicated access point approach is practically bulletproof.

Your smart home should feel effortless. With a little patience and the right configuration, it will.