How to Tell If a Light Switch Is Bad: A Network-First Guide for Leviton Smart Switches

Before you replace a 'dead' Leviton smart switch, walk up to it and press the paddle. If the relay clicks and the light responds, the switch is not the problem. The problem is somewhere in the network path between that switch and its controller. No replacement device is going to fix a path problem.

A switch that works locally but drops off the app is almost always a Zigbee or Wi-Fi issue. A switch that fails to click when line voltage is present at its terminals is a hardware failure. The first case covers roughly eight out of ten 'failed' smart switches we pull out of walls. The second case is much rarer than most people assume.

My own education on this cost about $970, one frustrated customer, and a very quiet ride back to the shop. The checklist below is what I wish I'd had that week.

The 15-minute test: how to tell if a light switch is bad

For a standard switch, the test is straightforward. Turn off the breaker, remove the switch, set your multimeter to continuity, and probe the screw terminals. With the switch in the on position, you should read near zero resistance. In the off position, you should read an open circuit. If the meter says the opposite, the contacts are gone.

But most of the calls we get aren't about standard switches anymore. They're about Leviton smart switches, and they fail differently. Run this test before you pull anything off the wall:

1. Press the paddle and listen for the relay. A healthy smart switch makes a clean click each time you toggle it. If you hear the click and the light responds, the switching part is working.
2. If the relay clicks but the light doesn't respond, the issue is downstream: a loose neutral, a bad connection on the load wire, or an LED driver that won't play nicely with the switch. The switch hasn't died.
3. If the paddle works but the app doesn't, stop looking at the switch and start looking at the network. The local click proves the device has power and its controls are functioning. What's missing is the communication path.

No click at all? Confirm line voltage at the switch before you condemn it. A tripped breaker or a loose splice looks exactly like a dead switch.

Why I'm not guessing: the $970 replacement order

Since 2017, my team has commissioned lighting controls for commercial buildings, and I've kept a replacement log for every device we've pulled. The most humbling entry in that log is from spring 2022.

A clinic called about a wing of patient rooms where the lights would ignore the automation schedule once or twice a day, then work fine for hours. No error message. No pattern. Everything I'd read about Zigbee troubleshooting said the same thing: reset the device, re-pair it, replace it if necessary. So we did exactly that. When re-pairing didn't hold, we replaced six Leviton Zigbee switches. When another cluster started acting up a week later, we replaced six more.

The embarrassing truth is that all twelve removed switches worked perfectly on the bench. Every relay clicked. Every device joined our test network on the first attempt. They were never bad. Six went back into stock, and six would have gone back as warranty claims if we hadn't tested them first.

The real failure was a single Zigbee repeater that a cleaning crew had unplugged from a wall outlet in a back hallway. The devices that relied on that route suddenly had no path to the controller, so commands timed out. The symptoms looked exactly like intermittent hardware failure. I want to say we caught it by reading the coordinator's log, but I'd be lying if I said we didn't need a manufacturer support call to find it.

That project changed our diagnostic order. It should have changed it after the first three switches, but it took all twelve for the lesson to stick. Now our rule is simple: replace one switch when it fails alone, investigate when it fails with friends.

Read the Zigbee layers before you replace another switch

The term 'Zigbee layers' sounds academic until a device stops responding. Zigbee, the protocol used by Leviton's Decora Smart Zigbee products, is maintained by the Connectivity Standards Alliance and runs on IEEE 802.15.4 radios. When I diagnose a problem, I think in three layers:

• Application layer: where commands, scenes, schedules, and device bindings live.
• Network layer: the mesh routing that decides how a command travels from the coordinator to the right device.
• MAC/PHY layer: the actual 2.4 GHz radio link between devices.

If a switch responds to local paddle presses, the bottom of that stack is probably fine. Power is there, the relay is there, and the radio is probably fine too. So when a command fails, look at the network route between the Zigbee coordinator and the switch. An off-the-wall re-pair doesn't fix a mesh problem; it just creates a second broken relationship.

In a healthy Zigbee network, the mesh repairs itself within minutes. But in a sparse setup, a device can sit orphaned for hours when its preferred parent disappears. It still works when you press it. It just isn't connected to the mesh anymore. Replacing the device doesn't recreate the route. Rejoining it to a live parent does.

If you're going the Zigbee DIY route, buy a coordinator that gives you access to logs or at least a clear device list. When something 'dies,' the log will tell you which layer stopped responding. That information is worth more than any spare switch you can keep on a shelf.

What if you installed a Leviton wifi smart switch?

Leviton wifi smart switch models don't use Zigbee. They connect to your 2.4 GHz Wi-Fi network, and they fail differently. But the diagnostic order should be the same: confirm local control first, then attack the network.

We've seen a Leviton wifi smart switch that worked at the wall but couldn't be reached in the app for days at a time. The hardware was fine. The router was steering the 2.4 GHz device onto a band or channel it couldn't hold, and the switch kept losing its association. A router reboot brought it back every time. The customer wanted a new switch. The switch didn't need replacing.

If a wifi smart switch drops offline after a router change, check the network name, password, band steering settings, and signal strength before you check the hardware. A switch that works locally is telling you the truth. Listen to it.

The same layer confusion shows up in fiber links

Our scope also includes structured cabling, and Leviton fiber connectors show up in a lot of the racks we build. The same 'blame the visible component' reflex happens there too.

A few years ago, a client was convinced their 10G backbone was failing at the patch panel. They had already ordered replacement Leviton fiber connectors for an entire row of links before we arrived. We measured optical power first. The connectors were fine, the patch cables were fine, and the glass was fine. The SFP transceiver at the far end was dying. No amount of fresh connectors was going to fix a failing light source.

That project reinforced what I learned in the clinic: a connector can't fix a transceiver, and a switch can't fix a Zigbee route. I'd rather spend ten minutes explaining a mesh than spend an afternoon replacing good hardware.

When a bad light switch is actually bad

Let me not talk you out of a legitimate replacement. Real hardware failures happen. Less than one in ten of the switches we pull turn out to be genuinely defective, in my experience, but that one still deserves to be found. These are the cases where hardware is the right suspect:

• Heat, smell, or buzzing. A switch that is hot to the touch, humming, or smells like burning plastic should come out immediately.
• Multiple failures after a surge. Lightning or a utility surge can kill the electronics in a whole bank of smart switches at once.
• No local response with confirmed power. If line voltage is present at the switch and the relay still won't click, the internal switching components have failed.

What we don't do anymore is replace a row of switches because the app shows them offline. Offline is a symptom. The question is which layer went down.

I should also be clear about the limits of my own experience. This comes from commercial retrofit work and the typical residential troubleshooting we get pulled into, not from a lab study. Your building may be different. If you're not comfortable testing for line voltage or working inside a junction box, call an electrician.

One last habit: ask the building staff if anyone moved, unplugged, or replaced a router, repeater, or smart plug in the past few weeks. They'll say no. Then it turns out somebody did. Ask anyway. It's the cheapest diagnostic step I know, and it's saved us from replacing a lot of perfectly good Leviton switches.