How to Read Your Router’s DHCP Lease Table to Find a Device That Stopped Checking In

When a smart-home device stops checking in, the first instinct is usually to reboot it, re-pair it, or factory-reset it. A more useful first step is to look at the router’s DHCP lease table. The lease table is the router’s record of which devices asked for an IP address, when they asked, and how long the router agreed to hold that address for them. It sits at the intersection of network addressing, device identity, and failure-mode analysis. For anyone running a residential or small-office smart-home system that is supposed to be dependable, the lease table is one of the few diagnostic views that shows you what the network saw, not what an app claims is true.

This article explains what the DHCP lease table actually contains, how to find it on common router firmware, and how to use it to distinguish between a device that is offline, a device that is online but unreachable, and a device that is silently using a different address than you expect. It also covers the tradeoffs of static leases, reserved addresses, and the occasional case where the dumb alternative—checking a power strip—is the smarter first move.

What the DHCP Lease Table Is and What It Is Not

DHCP, the Dynamic Host Configuration Protocol, is the mechanism by which a router hands out IP addresses to devices on the local network. When a device connects, it sends a DHCP request. The router responds with an offer that includes an IP address, a lease duration, the subnet mask, the default gateway, and usually one or more DNS servers. The lease table is the router’s current list of those offers and their state.

A typical lease table entry includes:

• Hostname — the name the device reported, if any.
• MAC address — the hardware address of the device’s network interface.
• IP address — the address currently assigned or reserved.
• Lease expiration — when the assignment ends if the device does not renew.
• Connection type — Ethernet, Wi-Fi, or sometimes a specific band.

What the lease table is not is a live presence map. A device can hold a valid lease while being completely unreachable. It can also be reachable while showing no lease at all, if it was configured with a static IP address outside the DHCP pool. The lease table tells you what the router agreed to, not what is currently responding to pings.

For smart-home operators, this distinction matters. A wall switch that stopped reporting to its hub may still hold a lease. A camera that appears in the app as offline may have a lease that expired three days ago. The lease table gives you a timestamped clue about when the device last successfully negotiated with the network.

Why a Stopped Device Still Shows Up in the Lease Table

Most consumer routers default to lease times between 12 and 24 hours. Some use longer windows. During that window, the router will keep listing the device even if the device has been unplugged, reset, or moved to another network. The entry remains until the lease expires or until the router’s DHCP service is restarted.

This is useful for diagnosis. If a device stopped checking in at 2:00 a.m. and its lease still shows an expiration time of 10:00 a.m., you know the device was connected recently enough to renew. If the lease expired and the device has not reappeared, the failure likely happened before the expiration time. If the device never appears in the table at all, the problem may be at the physical layer, the device’s network stack, or a mismatched Wi-Fi credential.

One common failure mode in small-office and residential systems is a device that drops off Wi-Fi, fails to reconnect, and then gets a new IP address when it finally does reconnect. The app may still be looking for the old address. The lease table shows both the old expired entry and the new active entry, which is often the fastest way to spot the address change.

Finding the DHCP Lease Table on Common Routers

The exact path varies by firmware, but the table is usually under a section called DHCP, LAN, Network, Attached Devices, or Client List. On many consumer routers, the attached-devices list is a simplified view of the lease table. The full table, with expiration times and MAC addresses, is often one menu level deeper.

Typical paths

• ASUS: Network Map > Clients, or LAN > DHCP Server
• TP-Link: DHCP > DHCP Clients List
• Netgear: Attached Devices, or Advanced > Setup > LAN Setup
• Ubiquiti UniFi: Clients, with lease information in the client properties panel
• OpenWrt: Status > DHCP Leases, or Network > DHCP and DNS
• pfSense/OPNsense: Status > DHCP Leases

If your router is managed through an ISP-provided app, the lease table may be hidden or absent. In that case, you can often get the same information from a device that is already on the network by using a network scanner, but the router’s own table is more authoritative because it includes lease state.

Step-by-Step: Using the Lease Table to Diagnose a Missing Device

1. Identify the device by MAC address, not by name

Hostnames are unreliable. Many smart devices report generic names like “ESP_8F3A2B” or “unknown.” The MAC address is the stable identifier. If you do not know the device’s MAC address, check the label on the device, the original box, or the app’s device-information screen. Some devices print the MAC on a small sticker near the power input.

Once you have the MAC, search the lease table for it. Most router interfaces allow you to sort or filter by MAC. If the MAC is present, note the IP address and lease expiration. If it is absent, the device has not successfully requested a lease during the current table window.

2. Compare the lease state to the device’s reported state

If the device’s app says it is offline, but the lease table shows an active lease, the device is likely still connected to the network but not reachable by the app’s cloud service or hub. That points to a service-level failure, not a network-level failure. Reboot the hub or the cloud integration before touching the device.

If the lease table shows an expired lease and no renewal, the device lost its network connection before the lease ended. That points to Wi-Fi instability, power loss, or a device crash. Check the device’s power state first, then its Wi-Fi signal.

If the lease table shows no entry at all, the device may be configured with a static IP, may be on a different subnet, or may have failed before it could complete a DHCP exchange. Check the device’s own network settings if you can reach it through a direct connection or a configuration mode.

3. Check for duplicate or conflicting leases

Some routers will show two entries for the same MAC address: one expired and one active. This happens when a device reconnects and receives a different IP. It is not necessarily a problem, but it can confuse apps and hubs that cache the old address. If you see this pattern, consider assigning a DHCP reservation so the device always receives the same IP.

Conflicting leases can also occur when two devices end up with the same IP address. This is rare on a healthy DHCP server, but it can happen after a router reboot, a power outage, or when someone manually assigns an address inside the DHCP pool. The lease table will show the conflict if the router detects it. The fix is usually to shorten the lease time, move static assignments outside the pool, or reboot the offending device.

DHCP Reservations vs. Static IPs: A Tradeoff Worth Understanding

When a device keeps disappearing or changing addresses, the common advice is to give it a static IP. There are two ways to do that: configure the address on the device itself, or create a DHCP reservation on the router. They are not equivalent.

A DHCP reservation tells the router to always assign the same IP to a specific MAC address. The device still uses DHCP. This is the more maintainable option for most smart-home gear because the router remains the single source of truth. If you replace the router, you can recreate the reservations in one place.

A static IP configured on the device bypasses DHCP entirely. The device will not appear in the lease table at all, which removes one diagnostic signal. It also creates a risk of address conflicts if the static address falls inside the DHCP pool and the router hands that address to something else. If you use static IPs, keep them outside the DHCP pool and document them somewhere you will actually look.

For devices that need to be reachable by a hub or a local controller, a DHCP reservation is usually the better default. It preserves the lease-table visibility while giving you a stable address. The main exception is a device that has unreliable DHCP behavior or that needs to work during a router outage. In those cases, a static IP may be justified, but you should accept the loss of lease-table diagnostics as a tradeoff.

When the Lease Table Is Not the Right Tool

The lease table is a network-layer view. It will not tell you if a device’s firmware crashed, if a sensor is reporting bad data, or if a cloud service is down. It will also not help with devices that use protocols other than IP, such as Z-Wave, Zigbee, or Bluetooth. Those devices appear in the lease table only if they have an IP-capable bridge or hub, and the bridge’s lease state is not the same as the end device’s state.

There are also cases where the dumb alternative is smarter. If a device stopped checking in and the lease table shows an expired lease, the first thing to check is whether the device has power. A wall switch that was accidentally turned off at the breaker, a camera with a loose barrel connector, or a smart plug that was unplugged by someone looking for an outlet will all show the same lease-table signature as a network failure. Checking power takes thirty seconds and requires no router access.

Similarly, if the device is battery-powered and has been in storage, it may have entered a deep-sleep state and stopped renewing its lease. The lease table will show an expired entry, but the fix is a physical wake-up, not a network change.

Reading Lease Times as a Failure-Mode Signal

Lease duration is a configurable parameter on most routers, and it has a subtle effect on how failures appear. A short lease time, such as one hour, means the lease table is a more current picture of the network. Devices that disappear will drop out of the table quickly. A long lease time, such as seven days, means the table retains entries for devices that have been gone for a while, which can be useful for historical diagnosis but can also clutter the view.

For a small smart-home network, a lease time between 12 and 24 hours is a reasonable default. It balances table freshness against DHCP chatter. If you are actively debugging a device that keeps dropping, temporarily shortening the lease time to one hour can make the table more responsive to the device’s connection attempts. Just remember to set it back when you are done, or you will increase DHCP traffic for no ongoing benefit.

Some devices renew their lease at odd intervals or fail to renew until the lease is nearly expired. If you see a device that repeatedly appears with a new lease after a gap, that is a sign of intermittent connectivity. The gap length, compared to the lease duration, can tell you whether the device is losing power, losing Wi-Fi, or crashing and rebooting.

Documenting What You Find

One of the most underrated maintenance practices for a small smart-home system is keeping a simple network inventory. A text file or a spreadsheet with each device’s MAC address, expected IP address, lease type, and physical location will save hours of diagnosis later. When a device stops checking in, you can compare the current lease table against your inventory and immediately see what changed.

This is not a one-time task. Devices get replaced, routers get swapped, and addresses get reassigned. A quarterly review of the lease table against your inventory is a low-effort way to catch problems before they become failures. It also gives you a baseline for what “normal” looks like on your network, which makes anomalies easier to spot.

If you want a more structured approach to this kind of review, the article on auditing the small systems that quietly run your week covers a repeatable process for checking the devices and services that keep a home or small office running.

Common Lease Table Patterns and What They Mean

Active lease, device unreachable

The device has a valid IP assignment but does not respond to pings or app requests. This usually means the device is powered but its application layer has failed, or a firewall rule is blocking traffic. Reboot the device remotely if possible, or check the router’s client isolation settings.

Expired lease, no renewal

The device was connected at some point but has not renewed. Check power, Wi-Fi signal, and whether the device was moved. If the device is battery-powered, check the battery level.

No lease entry at all

The device has not completed a DHCP exchange during the current table window. Check physical connectivity, Wi-Fi credentials, and whether the device is configured with a static IP.

Multiple entries for the same MAC

The device has reconnected and received a different address. This is common after a router reboot or a device power cycle. Consider a DHCP reservation to stabilize the address.

Lease entry with a hostname you do not recognize

An unknown device has joined the network. This may be a new smart device, a guest’s phone, or something less benign. Check the MAC address against a vendor lookup tool and decide whether to block it.

Tools That Complement the Lease Table

The lease table is a starting point, not a complete diagnostic suite. A few other tools fill in the gaps:

• Ping and traceroute — confirm whether an IP address is actually reachable.
• ARP table — shows the router’s current IP-to-MAC mappings, which can reveal devices that are active but not in the DHCP lease table.
• Network scanners — such as nmap or mobile apps like Fing, can enumerate devices on the local subnet and identify open ports.
• Router logs — many routers log DHCP events, which can show when a device requested, renewed, or released a lease.

Used together, these tools give you a layered view of the network. The lease table tells you what the router agreed to. The ARP table tells you what the router is actually talking to. Ping tells you what responds. Logs tell you what happened over time.

When to Escalate Beyond the Lease Table

If the lease table shows a healthy, active lease for a device that still will not check in, the problem is above the network layer. That means the device’s application, the hub, the cloud service, or the integration between them is at fault. Reboot the hub, check the service status page for the device’s cloud platform, and look at the device’s own logs if it exposes them.

If the lease table shows no entry and the device is known to be powered and configured correctly, the problem may be at the radio or driver level. A device that cannot complete a DHCP exchange despite a strong Wi-Fi signal may have a corrupted network stack. A factory reset is a reasonable next step, but only after you have ruled out simpler causes.

For devices that are critical to the operation of the home or office, consider whether the device’s failure mode is acceptable. A device that silently drops off the network and requires manual intervention is a reliability problem, not just a configuration problem. The lease table can help you quantify how often that happens, which is useful when deciding whether to replace the device or move it to a more reliable connection method.

Frequently Asked Questions

Why does my device show an active lease but still appear offline in the app?

An active lease means the device successfully obtained an IP address from the router. If the app still shows it as offline, the failure is likely above the network layer: the device’s application crashed, the hub lost its pairing, or the cloud service is unreachable. Reboot the hub or the device’s cloud integration before assuming the network is at fault.

How can I find a device’s MAC address if it is not labeled on the device?

Check the device’s app under device information or network settings. Many apps display the MAC address there. If the device is currently connected, the router’s lease table or attached-devices list will show it. For devices that are offline and unlabeled, the original packaging or the manufacturer’s support page may list the MAC format or a lookup method.

Should I use a DHCP reservation or a static IP for my smart-home devices?

For most devices, a DHCP reservation is the better choice. It keeps the device visible in the lease table, centralizes address management on the router, and avoids conflicts with the DHCP pool. A static IP configured on the device is useful when the device must work during a router outage or has unreliable DHCP behavior, but it removes the device from the lease table and requires careful documentation.

What does it mean if a device’s lease expired and it never renewed?

An expired lease with no renewal means the device stopped communicating with the router before the lease ended. The most common causes are power loss, Wi-Fi signal degradation, a device crash, or the device being moved out of range. Check power and physical placement first, then look at the device’s Wi-Fi signal strength and any router logs for DHCP events.

Can I use the lease table to find devices that are not smart-home gear?

Yes. The lease table shows every device that uses DHCP on the network, including phones, laptops, printers, and media players. This makes it useful for spotting unknown devices that may have joined the network. If you see a hostname or MAC address you do not recognize, investigate it before assuming it is benign.