DHCP Reservations & Static IPs for Smart-Home Devices

If a smart plug, camera, or hub keeps becoming unreachable after a router reboot — or an automation that pings a device by IP suddenly fails — the usual cause is a changing IP address. By default, your router hands out addresses via DHCP, and those addresses can rotate over time. A DHCP reservation tells the router to always give a specific device the same IP, which is the safest fix for most homes. A true static IP set on the device itself is a stronger tool you only need in narrow cases. This guide explains the difference, when each matters, and exactly how to set them up.

DHCP reservation vs. static IP: what's the difference?

The two get used interchangeably, but they work in opposite directions and have different failure modes.

Method	Where it's set	How it works	Best for
DHCP reservation	Your router	Router maps the device's MAC address to a fixed IP and always assigns it	Almost all smart-home devices
Static IP	The device itself	Device ignores DHCP and uses an address you typed in manually	Devices without router access, or networks with no DHCP

The practical reason to prefer reservations: the router stays the single source of truth. It knows which addresses are spoken for, so it won't hand the same IP to something else. A device-side static IP is invisible to the router's DHCP pool — if you pick an address inside that pool, the router may later lease it to another gadget, and now two devices fight over one IP. Many smart-home apps also don't expose a static-IP field at all, which is another reason reservations win in practice.

When do you actually need a fixed IP?

Most Wi-Fi smart devices work fine with normal DHCP because you reach them through a cloud account or a hub, not by typing an address. You genuinely benefit from a fixed IP when something on your network points at the device by IP:

• Cameras feeding a local NVR or RTSP stream — the recorder is configured with the camera's address.
• Local integrations — Home Assistant, Homebridge, or a custom dashboard that polls a device directly.
• Port forwarding — remote access rules that must point at one unchanging internal address.
• Hubs and bridges — a Hue Bridge, Thread border router, or controller you'd like to find reliably for diagnostics.
• Printers, NAS, and "server" gear that other devices connect to.

If none of those apply, a fixed IP usually isn't necessary — and if a cloud-connected device keeps dropping off, the cause is more often Wi-Fi band steering or signal than addressing. Our guides on devices going offline and 2.4GHz vs 5GHz cover those root causes.

How to set a DHCP reservation (the recommended method)

The exact menu names vary by router brand, but the flow is the same everywhere. Look under the LAN, DHCP, or "Connected Devices" area of your router's app or web interface.

1. 1Find the device’s MAC address
2. 2Open your router’s DHCP/reservation settings
3. 3Bind that MAC to the IP you want
4. 4Reboot the device to pick up the new lease

1. Identify the device's MAC address. This is the device's permanent hardware ID. Find it in the router's list of connected clients, on a sticker on the device, or in the manufacturer's app under device or network info. Match it carefully — names like "ESP-3F2A" can be cryptic, so cross-check the IP the device currently holds.
2. Open your router's reservation tool. In most router apps this lives under DHCP settings, "IP reservation," or "address reservation." On mesh systems (eero, Google/Nest Wifi, Deco) it's usually inside the individual device's detail screen as an option like "Reserve IP."
3. Assign the IP. Pick an address in your subnet (commonly 192.168.x.x). Many routers auto-fill the device's current IP — accepting that is the easiest, conflict-free choice.
4. Save, then renew the lease. Reboot the device or toggle its Wi-Fi so it requests a fresh address. Confirm it now shows the reserved IP in the client list.

One nice side effect: keeping your hub on a known address makes diagnostics far easier when it acts up. If yours drops connections, pair this with stabilizing a flaky hub.

If you must set a static IP on the device

Some cameras and niche gear only offer device-side static configuration. If so, avoid IP conflicts by choosing an address outside your router's DHCP range.

1. Check your DHCP range in the router (e.g., it leases 192.168.1.100–192.168.1.200).
2. Pick an address below or above that pool — for example 192.168.1.50 — so the router never tries to lease it to anything else.
3. Match the rest of the settings to your network: subnet mask (usually 255.255.255.0), gateway (your router's IP), and DNS (your router's IP, or a public resolver).

A wrong gateway or DNS is the most common reason a manually configured device connects to Wi-Fi but can't reach the internet or its cloud service.

A note on Thread, Zigbee, and Z-Wave devices

This whole topic only applies to IP-based devices — Wi-Fi gear and Ethernet hubs. Zigbee and Z-Wave accessories don't have IP addresses at all; they talk to a hub over their own radio mesh, so there's nothing to reserve. Thread devices do use IPv6, but addressing is handled by the Thread network and border router, not your DHCP server — you don't manually reserve those either. If you're sorting out which devices live on Wi-Fi versus a mesh radio, see Wi-Fi vs Thread vs Zigbee. The reservation step matters only for the Wi-Fi device or the hub/bridge itself.

Frequently asked questions

Will a DHCP reservation stop my smart device from going offline?

Only if the dropouts are caused by a changing IP — for example, an integration or NVR losing track of the device after a lease change. If the device disconnects from Wi-Fi entirely, the cause is usually signal strength, band steering, or router behavior, not addressing. Work through a full offline-fix checklist first.

How many reservations can I create?

Most consumer routers support dozens, which is plenty for a typical home. There's no real downside to reserving every important device — hubs, cameras, printers, and anything referenced by IP. You generally don't need to reserve simple cloud-only plugs and bulbs.

Do reservations survive a router reset or replacement?

Reservations are stored in the router's configuration, so a factory reset or a new router erases them — you'd recreate them (or restore a config backup). Device-side static IPs survive a router change but must be re-checked against the new router's subnet and DHCP range to avoid conflicts.

Should I put smart devices on their own SSID or VLAN too?

That's a separate, complementary step. A dedicated 2.4GHz network for IoT improves stability regardless of addressing; reservations then keep those devices findable. See our smart-home Wi-Fi network guide.

Sources

• Home Assistant — documentation on local device discovery and IP-based integrations
• Connectivity Standards Alliance — Matter — networking model for Matter over Wi-Fi and Thread
• Thread Group — Thread overview — how Thread handles IPv6 addressing and border routers
• Samsung SmartThings — hub and connected-device setup reference