Back to Google Nest Guides
Google Nest

How Do I Assign a Static IP or DHCP Reservation to Nest Devices?

Google Nest GuideSecurity Cameras
medium difficulty 20-30 minutes for all devices 185 views 1 found helpful Updated
This guide applies to: Google Nest Google Nest Products (Nest Cam Indoor, Nest Cam Outdoor, Nest Cam Battery, Nest Cam Wired, Nest Thermostat, Nest Protect, Nest Hub)
At a glance — most common causes
  • Router DHCP lease time too short causing frequent IP renegotiation
  • Nest device WiFi chipset slow to respond to DHCP renewal causing lease expiration
  • Too many devices on the network exhausting the available DHCP address pool
20-30 minutes for all devices11 solutions coveredmedium level

Expert Review & Technical Scope

DeviceGoogle Nest Google Nest Products
Model CoverageNest Cam Indoor, Nest Cam Outdoor, Nest Cam Battery, Nest Cam Wired, Nest Thermostat, Nest Protect, Nest Hub
Fix Time20-30 minutes for all devices
DifficultyMedium
Required ToolsNo special tools required
Network / ProtocolWi-Fi / app-based troubleshooting context

Problem Description

Your Nest devices periodically go offline when the router assigns them a different IP address during DHCP lease renewal. Nest devices do not have a built-in option to set a static IP address from the device itself. The only way to give Nest devices a permanent IP is through DHCP reservation on your router which assigns the same IP to a specific device MAC address every time it connects. This is essential for stable smart home networks especially with multiple Nest cameras and is the most recommended fix on home automation forums for Nest reliability issues.

Symptoms

  • Nest cameras go offline briefly every few days then reconnect with a different IP
  • Nest thermostat loses WiFi connection periodically and takes several minutes to reconnect
  • Router logs show DHCP lease expired for Nest device MAC address
  • Multiple Nest devices drop offline at the same time suggesting DHCP pool exhaustion
  • Nest devices lose connection after every router reboot
  • Google Home app shows devices unreachable for 1 to 5 minutes during IP renewal

Recognize these? Here's what usually causes it.

Common Causes

  • Router DHCP lease time too short causing frequent IP renegotiation
  • Nest device WiFi chipset slow to respond to DHCP renewal causing lease expiration
  • Too many devices on the network exhausting the available DHCP address pool
  • Router does not persist DHCP leases across reboots assigning new IPs each time
  • IP address conflict between a Nest device and another device on the network
  • Router firmware bug causing random DHCP assignment failures for IoT devices

Most fixes happen in the first 3 steps.

Warning

Never assign a static IP directly on a Nest device because Nest products do not support manual IP configuration. Always use DHCP reservation on the router side. Also ensure reserved IPs are outside the dynamic DHCP pool range to prevent conflicts with other devices.

Step-by-Step Solution

1

List Nest device MAC addresses first

Collect MAC addresses for each Nest device from app/router before creating reservations. Correct mapping prevents accidental IP conflicts.

2

Create DHCP reservations on router

Assign fixed IP leases in router DHCP settings rather than hard-coding static IP on devices. Reservation approach preserves managed network control.

3

Reboot network and Nest devices

Restart router, then reboot Nest devices so they request reserved addresses cleanly. This ensures lease table updates are applied.

4

Verify reserved IP assignment and reachability

Confirm each device receives expected IP and remains reachable in app diagnostics. Incorrect assignment indicates reservation mismatch or duplicate MAC entry.

5

Monitor stability after reservation rollout

Watch connectivity for 24 hours to verify reduced disconnects and latency issues. Proper reservations stabilize cloud-device session continuity.

Quick Solutions

Create DHCP reservations for every Nest device on your network
Increase DHCP lease time to reduce renewal frequency
Expand DHCP pool if running out of available IP addresses
Reboot each Nest device after creating reservations to apply new IPs
Check for and resolve IP conflicts in router client list
Update router firmware to fix known DHCP bugs

Still having issues? This is usually the deeper cause below.

If this comes back after following these steps, check whether a recent app or firmware update reset a default setting — the fix works, but the setting gets reverted silently.

Pro Tip

Create a spreadsheet or note listing every smart home device on your network with its name, MAC address, and reserved IP. This becomes invaluable when troubleshooting network issues or setting up a new router. Update it whenever you add or remove devices.

Real-World Insight

This issue almost always looks more complex than it is — the majority of cases trace back to a single setting, a stale credential, or a default that shipped wrong.

What Usually Goes Wrong
  • Router DHCP lease time too short
  • Nest device WiFi chipset slow to respond to DHCP
  • Too many devices on the network exhausting the available
  • Router does not persist DHCP leases across reboots assigning
  • IP address conflict between a Nest device and another

Official Manufacturer Manual

If you need the complete manufacturer documentation for advanced setup, wiring diagrams, or detailed specifications, you can download the official manual below. The manual includes full technical instructions directly from the manufacturer and may help if your issue requires deeper troubleshooting.

Download the Official Google Nest Products Manual

Source: support.google.com

Need More Help? Google Nest Support

Note: The contact information below connects you directly to Google Nest's official customer support team, not Trunetto. They can help with warranty claims, device replacements, and advanced technical issues.

How Does Google Nest Compare?

Before replacing your Google Nest device, see how it stacks up against alternatives in our full comparison guides.