A Ring doorbell that has been stable for months starts dropping offline two or three times a week. The obvious explanations get ruled out quickly: it is hardwired, so it is not the battery. The Ring app shows three bars before every dropout, so it does not look like signal strength. Ring's status page shows no outage, and only this one device on this one network is affected.
When all three of those check out and the drops continue, the cause is almost always one of two things that Ring's built-in troubleshooting never examines: a Wi-Fi channel conflict with a neighbouring router, or DHCP lease failure on your own router. Ring's in-app diagnostics measure signal strength and nothing else, which is why the app keeps telling you the connection is fine while the device keeps disappearing.
Why full signal bars and a broken connection are not contradictory
Signal strength and connection quality are different measurements, and the Ring app only shows you the first one.
Signal strength is how loud the signal is. Connection quality is how clean it is. A loud signal sitting on a congested channel produces packet loss and connection timeouts in exactly the same way a weak signal does — but it displays as full bars, because the meter is measuring volume, not clarity.
Wi-Fi on the 2.4 GHz band is divided into channels 1 through 11 in the US, of which only 1, 6, and 11 do not overlap one another. If your router and a neighbour's router are broadcasting on the same channel, or on channels close enough to overlap, both networks are transmitting into the same space and interfering with each other. Devices that transmit in short, infrequent bursts — which is exactly what a doorbell does — are the first to suffer, because they are least likely to win contention for a noisy channel.
One clarification worth making, since it is stated incorrectly in a lot of guides: not every Ring doorbell is a 2.4 GHz-only device. Older and entry-level models are, but several models including the Video Doorbell Pro 2 support both 2.4 and 5 GHz. That matters for diagnosis, because a dual-band model sharing one SSID across both bands can also drop while switching between them — a separate cause covered later in this article. Check your specific model's specifications before assuming which band it is on.
DHCP lease failure — the second cause, and the quieter one
Your router hands out IP addresses through DHCP. Each assignment is a lease with an expiry, and before it expires the device must request a renewal. Two things can break this.
The first is pool exhaustion. If your router's DHCP pool holds 50 addresses and you have 48 devices, there is very little headroom, and a device that has been idle can find its address has been reassigned.
The second is renewal failure on an idle device. A doorbell can sit for hours without transmitting anything. When its renewal request coincides with a busy moment on the router, or with a short lease time, the renewal can fail silently. The device loses its address and drops offline — and because nothing dramatic happened, nothing in the Ring app explains it.
Short lease times make this considerably worse. Some ISP-supplied routers ship with a one-hour default, which means every idle device must successfully renew its address twenty-four times a day.
Diagnosing which one you have
Check for channel conflict — about two minutes
Install a Wi-Fi analyzer app on an Android phone and open the channel graph view. It plots every network within range against the channel it occupies.
Find your network on the graph and compare it to your neighbours'. If your peak sits on the same channel as one or more other networks, or overlaps them substantially, channel conflict is in play. Pay particular attention to networks with strong signal — a distant network on your channel matters far less than a close one.
Check DHCP status — about three minutes
Log into your router's admin panel and open the DHCP client list or connected-devices page. Count the devices. Then find the DHCP pool range under LAN or DHCP settings — a range such as 192.168.1.100 to 192.168.1.199 is a pool of 100 addresses.
If your device count is close to the pool size, exhaustion is contributing. While you are there, note the lease time. Anything at or below 24 hours means frequent renewals; one hour means very frequent renewals.
The fix for channel conflict
Step 1 — Set a fixed channel instead of Auto
In your router admin panel, open Wireless Settings, select the 2.4 GHz band, and change Channel from Auto to a specific value — whichever of 1, 6, or 11 showed the least neighbouring activity in your scan.
This fixes two problems at once. It moves you off the congested channel, and it stops the periodic channel changes that Auto mode performs. Every automatic channel change momentarily disconnects every device on the network. Most reconnect instantly and you never notice; a doorbell that was idle at that moment may not.
Step 2 — Set 2.4 GHz channel width to 20 MHz only
In the same section, find Channel Width or Bandwidth for the 2.4 GHz band. If it reads Auto or 20/40MHz, change it to 20MHz only.
A 40 MHz channel doubles available bandwidth but occupies twice as much of an already crowded band, which increases the number of networks you conflict with. A doorbell needs almost no bandwidth, so the narrower channel costs it nothing and gains it stability.
The fix for DHCP
Step 1 — Reserve a static address for the doorbell
In your router's DHCP settings, look for Address Reservation, Static DHCP, or DHCP Reservation. Find the doorbell in the client list — it will be listed with its MAC address — and reserve its current IP against that MAC.
The router now always issues the same address to that device and never returns it to the general pool, no matter how long the device stays quiet. Lease expiry is eliminated as a failure mode entirely. This is the single most effective change on this page.
Step 2 — Extend the lease time if reservations are unavailable
Some ISP-supplied routers do not offer reservations. If yours does not, raise the DHCP lease time to 72 hours, or to a "forever"/infinite option if one exists. Fewer renewal events means fewer opportunities for a renewal to fail.
Step 3 — Expand the pool if it is near capacity
If the client count is close to the pool size, widen the range. Changing an end address from 192.168.1.149 to 192.168.1.200 takes the pool from 50 addresses to 101 and removes contention. There is no downside to a larger pool on a home network.
If it still drops after both fixes
Open the Ring app, go to your device, and open Device Health. Read the RSSI value.
- Better than −60 — signal is strong. Distance is not your problem.
- −60 to −70 — marginal. Walls and distance are contributing.
- Below −70 — signal degradation is real and no router setting will compensate for it.
For marginal or poor RSSI, the remaining options are a mesh node or extender placed between the router and the door, or relocating the router closer to the front of the house. Note that a poorly placed extender can make things worse by adding a hop and halving throughput — put it roughly halfway, not next to the doorbell.
If your model is dual-band and your 2.4 and 5 GHz networks share one SSID, check whether the Ring app offers a network preference setting for your device and pin it to the 2.4 GHz network explicitly. Where that option is unavailable, splitting the bands into two separate SSIDs at the router and joining the doorbell to the 2.4 GHz one achieves the same thing. Every band switch is a brief disconnection and re-authentication, which reads as a dropout.
Three changes that look right and make it worse
Each of these is suggested constantly in forum threads, and each one can degrade a network that was only mildly unhealthy to begin with.
Turning off the 5 GHz band entirely. The reasoning — "the doorbell is on 2.4, so 5 is just noise" — is backwards. Phones, laptops, and TVs that would otherwise sit on 5 GHz all fall back to 2.4 GHz when you disable it, which is precisely the band you are trying to keep clear. Leave 5 GHz enabled so the bandwidth-hungry devices stay off the doorbell's band.
Putting the extender next to the doorbell. An extender repeats whatever signal it receives, so placing it at the weak end repeats a weak signal. It belongs roughly halfway between router and doorbell, where it still has a clean signal to relay. Placed badly, it also halves throughput for everything connected through it.
Raising transmit power to maximum. Many routers expose a transmit-power setting, and turning it up feels like the obvious move. It increases how far your signal reaches, which increases how many neighbouring networks you interfere with — and does nothing for the return path, since the doorbell's own transmit power is fixed. In a dense building this reliably makes things worse for everyone, including you.
The pattern behind all three: signal strength was never the problem. Adding more of it does not address a channel conflict or a lease failure, and in two of these three cases it actively compounds the interference.
When none of this is the cause
Four situations produce the same symptom and are not addressed by anything above.
- Chime or transformer undervoltage. A hardwired doorbell drawing insufficient voltage reboots intermittently, which looks identical to a network dropout. Device Health reports the voltage — if it is below the model's stated minimum, the problem is electrical, not network. This is more common after adding a smart chime.
- ISP-side disconnections. If other devices also lose connectivity at the same moments, the doorbell is a symptom rather than the cause. Check the router's system log for WAN disconnect entries before changing anything on the LAN side.
- Firmware mid-update. Devices go briefly offline while installing firmware. If the drops are isolated and Device Health shows a recent firmware version change, wait a few days before diagnosing further.
- Extreme cold. Battery-powered models lose usable capacity below freezing and can drop offline daily in winter while behaving perfectly in summer. If the drops began with the season rather than with a network change, that is the variable that moved.
Confirming the fix held
Do not judge this within a day. The failure pattern was two or three drops a week, so a quiet 24 hours proves nothing. Check Device Health after a full week and compare the RSSI reading and the last-seen history against what you recorded before the changes.
If reservations and a fixed channel are both in place and drops continue at the same rate, the cause is on the list in the previous section rather than in your router settings — and voltage is the one to check first, because it is the one most often mistaken for a Wi-Fi problem.
Seeing this on a dual-band model? Note which band the device is actually joined to before changing any channel settings — the fix differs depending on the answer, and the Ring app does not always make it obvious.
Comments
Post a Comment