my device says it's connected to nest wifi pro but i have no internet, other devices work fine

Diagnosis

This issue is typically caused by a "stale" DHCP lease or an IP address collision within the 6GHz spectrum. Because other devices are working, the WAN connection to your ISP is healthy, but the specific handshake between the Nest WiFi Pro's 6E radio and the client device has failed. This often happens when a device transitions between the 2.4GHz, 5GHz, and 6GHz bands, causing the router to assign a new IP address while the device is still attempting to use the old one, resulting in a "Connected, no internet" status. Another common cause is the "Private Address" or "MAC Randomization" feature found in modern iOS and Android devices. The Nest WiFi Pro may see the device as a new entity every time it rotates its MAC address, leading to a conflict in the internal routing table where the router attempts to send data packets to a hardware address that is no longer active. You can confirm this by checking the Google Home app; if you see multiple entries for the same device (e.g., "iPhone" and "Unknown Device"), MAC randomization is the culprit.

How to Fix It

To resolve the routing conflict and refresh the IP assignment, follow these precise steps:

1. On the problematic device, go to Wi-Fi Settings and select "Forget this Network" for your Nest WiFi Pro SSID.
2. Power down the device completely. If it is a laptop, perform a full shutdown rather than a sleep/hibernate.
3. Open the Google Home app on your primary mobile device. Navigate to the Wi-Fi tab and select Devices.
4. Locate the affected device in the list. Tap the device name, then select the Pause button. Wait exactly 60 seconds to allow the DHCP lease to expire in the router's cache.
5. Tap Resume to reactivate the device's access.
6. Power the affected device back on. Re-select your Wi-Fi network and enter your password.
7. If the device is an iPhone or Android, go to the specific network settings for your home Wi-Fi and toggle Private Address or Randomized MAC to "Off" or "Device MAC" to ensure a consistent identity for the router.

If That Didn't Work

• Perform a DNS Flush: If the device is a Windows PC, open Command Prompt as Administrator and type ipconfig /flushdns followed by ipconfig /release and ipconfig /renew. This forces the device to request a fresh IP and DNS assignment from the Nest Pro, clearing any cached routing errors.
• Toggle the 6GHz Band: Some older 6E-compatible drivers struggle with the 6GHz transition. Try moving the device physically closer to a different Nest WiFi Pro point to force it to hand off from the 6GHz band to the 5GHz band. If internet returns, update the device's wireless network adapter drivers immediately.
• Check for IP Reservations: In the Google Home app, go to Wi-Fi > Advanced Settings > DHCP IP assignments. If the device has a static IP assigned that overlaps with another device's range, delete the reservation and let the router assign a dynamic IP.
• Hard Reboot the Mesh Node: If the device is connected to a specific point (satellite) rather than the main router, unplug the power cable from that specific point for 30 seconds. This clears the local ARP table of the node without resetting the entire network.

Heads Up

• Avoid Third-Party DNS: If you have configured custom DNS (like OpenDNS or Cloudflare) in the Google Home app, try reverting to "Automatic" to see if the issue is a DNS resolution failure rather than a connection failure.
• Firmware Sync: Ensure your Google Home app is updated to the latest version; Nest WiFi Pro firmware updates are pushed automatically, but the app interface can sometimes glitch and show "Connected" when the device is actually blocked by a parental control filter.
• 6GHz Interference: The 6GHz band has a shorter range than 5GHz. If the device is on the edge of the 6GHz coverage area, it may maintain a "connected" signal but experience 100% packet loss. Move the device 5 feet closer to the node to test stability.