When Your Home Theater Setup Explains Phantom Power Waste

You know that friend. The one with the home theater that looks like a bomb went off in a RadioShack. Cables everywhere. A receiver that glows blue even when nobody's watching. A subwoofer that hums a low B-flat, 24/7, because its power switch is on the back, buried behind a tangle of HDMI. That hum? That's phantom load. And it's the perfect analogy for the waste that's hiding in plain sight in your home, your office, your life.

Phantom power—also called standby power or vampire draw—is the electricity that flows into devices when they're off but still plugged in. Your home theater is ground zero. The average setup leaks 50 to 100 watts round the clock. That's like leaving a dim bulb burning forever. But here's the thing: you can't just unplug everything. Not if you want your DVR to record, your TV to turn on with one remote, or your kids to ask "where's the remote?" thirty times a day. So we live with the hum. But maybe we don't have to.

The Field: Where Home Theaters and Phantom Load Collide

The AV receiver that never sleeps

Walk into any home theater after midnight and you see them: a constellation of tiny blue, green, and red LEDs. That Denon or Marantz receiver in your rack? It's still powered on. Not in use—the screen is dark, no sound comes through—but the internal power supply is live, converting AC to DC, feeding the network chip that waits for a trigger signal. I've measured this on a friend's system: the receiver pulled 38 watts while doing absolutely nothing. That sounds fine until you multiply by 24 hours, then by 365 days. You're running a small space heater that heats nobody's room.

The catch is obvious when you think about it: your AV receiver has a soft-power button, not a hard switch. Most don't even include a physical relay to physically disconnect the main transformer. That means the Ethernet controller, the HDMI pass-through, the USB port that charges nothing—all alive. Alive and billing you.

Streaming sticks that glow even when paused

Roku sticks, Apple TV 4K units, Amazon Fire devices—they all do the same trick. You hit "Sleep" on the remote. The TV goes black. But the stick's LED stays on. Why? Because it hasn't really slept—it's polling the network for updates, checking for firmware pushes, listening for voice commands. I opened one once. The main SoC never fully powers down; it just enters a low-power state that still draws 2–4 watts. Not much. Until you realize that a home theater with three streaming sticks, a game console, a soundbar, and a receiver is running eight devices in standby simultaneously. That's 20–35 watts, constantly. Month after month.

Worth flagging—the streaming stick problem is worse than the receiver problem because people never unplug them. The receiver at least gets turned off at the surge protector occasionally. The stick hides behind the TV. Out of sight, drinking power.

'My electric bill dropped $14 after I put the whole rack on a switched power strip. I didn't change anything else. Just killed the standby.'

— Real comment from a reader who finally measured his system

Soundbars with no power switch, only standby

Then there's the soundbar. Modern soundbars—especially the slim ones designed to mount under a wall-mounted TV—often ship without a physical power button. Not "we hid it behind a panel." No button at all. The only way to turn it off is to unplug it, or let it auto-standby after ten minutes of silence. But auto-standby doesn't always kick in if the bar keeps receiving an HDMI handshake from the TV. So it stays warm. Humming. Drawing 8–12 watts for the DSP and the Bluetooth radio that's listening for a connection you'll never make. That hurts.

The irony: most owners chase incremental improvements in speaker placement or room treatment to shave 0.5 dB of distortion, but they ignore a continuous 15–30 watt phantom load that costs them $30–60 a year in wasted electricity. The field where home theater and phantom load collide isn't some obscure technical edge—it's the power strip you've been walking past for three years. Fix it, and the hum quiets. Not metaphorically. Actually.

Foundations: What People Get Wrong About Standby Power

Standby is not sleep, it's a coma with the lights on

I once watched a friend power-cycle his entire rack because the AVR wouldn't wake. He stabbed the front button. Nothing. Unplugged the processor. Plugged it back. Still dead. Turns out the unit was in standby—not off, not sleep, but that weird limbo where the network card stays alive, the HDMI handshake port stays warm, and the blue LED absolutely refuses to die. That's the first lie the industry sells you: standby sounds restful. It's not. True sleep cuts power to everything except a wake-up receiver. Standby keeps the whole front-end juiced. Your pre/pro pulling 35 watts while it waits for a CEC command? That's a coma with the lights on—and you're paying the electric bill.

Worth flagging—most modern receivers ship from the factory with "network standby" enabled by default. The manual calls it Quick Start or Network Control. You call it a phantom load that never clocks out. The catch is that disabling it often costs you real convenience: no app control, no auto-updates, no HDMI passthrough for the kids' Switch. So the trade-off isn't technical—it's behavioral. You choose between a three-second cold boot or a twelve-watt vampire that never sleeps.

The myth of 'zero watts' when switched off

That power brick on your subwoofer? Unplug the cable from the sub itself. Feel the brick. Still warm. That's because the AC-to-DC conversion stage inside doesn't stop drawing just because the load side went open-circuit. Cheap switched-mode supplies leak current across the primary-side capacitors—sometimes 0.5 watts, sometimes 2.5 watts, always nonzero. "Zero watts" is a sticker lie. The EU's One Watt Initiative aimed for standby below 1W in 2010. Many devices still miss that target in 2025. I have seen a "switched off" Oppo UDP-203 pull 4.3 watts because the front-panel display driver stayed alive to show a blank screen. Blank. Not even a clock. Just a black panel drawing power. That hurts.

The trickier bit is that some manufacturers cheat the measurement. They test standby with network features disabled, then slap the 0.5W badge on the box. Real-world use? You connect Ethernet. You leave HDMI-CEC active. Suddenly that "zero-watt" player is sipping 6W. Not enough to trip a breaker—enough to add $15–$30 a year for a stack of five components. Over a decade, that's a new AVR you could have bought. The phantom load isn't a bug. It's a design choice that prioritized instant-on over efficiency, and nobody told you.

Field note: energy plans crack at handoff.

'I thought 'off' meant off. Turns out my preamp was running a full Linux kernel in standby. The fan never stopped.'

— Home theater owner, after finding 22W continuous draw on a component that showed 'OFF' on the front display

Why the power brick stays warm even when nothing's connected

Leave a wall-wart plugged into the socket with the barrel connector dangling. Touch it an hour later. Warm, right? That's the quiescent loss from the transformer core and the rectifier diodes. No load, no device, no excuse—the brick itself eats 0.1–0.3W just to exist. Multiply that by the six bricks behind your rack: subwoofer, powered speakers, HDMI extender, game console, streaming stick, ethernet switch. Suddenly you've got a constant 1.5–2W baseline before any component even turns on. Most teams skip this because they see the device "off" and assume the brick goes quiet. It doesn't. The brick stays warm because the primary side never stops ringing.

What usually breaks first is the user's patience—not the hardware. You can yank every brick, but then you lose subwoofer calibration memory, or the streaming stick forces a re-authentication on cold boot. So you compromise. You leave a few warm bricks. That's fine—just know which ones. The subwoofer plate amp? Pull it. The ethernet switch? Let it ride (it's drawing 0.1W idle anyway). The key isn't zero draw. It's knowing which warm bricks you can kill without breaking your morning routine. We fixed this in my own rack by putting the five worst offenders on a single switched power strip with a visible red indicator. When the strip's red, those bricks are cold. When I'm watching, they're warm—and I made that trade-off on purpose.

Patterns That Actually Cut the Waste

Strip the Smart, Keep the Convenience

The fix that actually works—without turning your rack into a daily ritual of crawling behind the TV—is the smart power strip with a master-slave logic. Wrong order kills the whole idea: people plug the amp into the control outlet and the Blu-ray player into the switched bank, then wonder why nothing turns off. The master outlet needs the device that you turn off every time. For most home theater setups, that’s the display. The catch is latency—some cheaper strips take three full seconds to sense the power drop and kill the slaves. Long enough to glitch a receiver’s firmware. I have seen a $70 strip corrupt a Denon’s network stack twice. Worth flagging—buy a strip that lets you adjust the sensitivity threshold. That one setting separates a quiet rack from a bricked preamp.

Then there’s the IR-controlled outlet. These look like a band-aid but actually solve the deepest phantom waste: the subwoofer that draws 18 watts doing nothing except waiting for a 40 Hz handshake. Plop an IR outlet inline, teach it your remote’s “All Off” code, and the sub dies completely. The trade-off is that your remote now needs line-of-sight to that little white box behind the sofa. Not the end of the world, but the seam blows out if you have a universal remote that sends the code twice—some IR outlets interpret the second pulse as a toggle and fire the sub back on. We fixed this by programming a 200-millisecond delay on the control system. That hurts. But the sub is stone-cold dead, and that matters more than the half-second lag.

Master Switch on the Conditioner

Most power conditioners are sold as surge protection—nobody reads the spec sheet for the front-panel switch. But a quality unit like the Furman PST-8 has a latching switch that physically disconnects the entire bank when you flip it. Not a soft relay, not a touch sensor, a mechanical break. That kills every phantom draw from every component downstream—including the conditioner’s own internal logic board, which usually pulls 5–7 watts just to light that blue ring. Some reviewers have clocked the difference: switching to a physical master cutoff shaved 34 watts from their baseline idle draw. That’s 300 kWh per year. For a single finger motion.

The tricky bit is user compliance. A master switch only works if you reach for it. Home theater nerds with open racks will flip it religiously; anyone with a console buried in a ventilated cabinet will ignore it within a week. So the pattern isn’t just the hardware—it’s the habit. You pair the switch with a visual cue: a cheap LED lamp plugged into the switched bank that goes dark when the rack dies. That visual silence reminds you the strip is off. That small feedback loop cuts the waste more reliably than any smart strip algorithm I have seen.

‘The smart strip felt like a science project until I realized the sub was still pulsing. The IR outlet? That thing just works. No app, no firmware updates.’

— Andy, home theater enthusiast, after swapping his power bar for a $25 IR-controlled outlet

One more pattern, less common but brutal: put the zone amp on a timer. If you have a whole-home audio processor feeding 70-volt speakers around the house, that amp is idle 22 hours a day. Plop a mechanical timer—the old dial kind, not a smart plug—set it to kill power at midnight and restore it at 6 PM. That one move cuts the phantom load of a 6-zone amplifier from 45 watts to zero for 18 hours. The pitfall is the clock drifts in summer heat; recalibrate every six months. That’s a minor chore for a 70% reduction in standby waste. Not a glamorous fix. But it works. And your rack stays cool enough that you stop worrying about the fan failure that killed your neighbor’s preamp last July.

Anti-Patterns: Why Home Theater Nerds Keep the Hum Alive

The 'Always On for Best Quality' Trap

I walked into a friend’s dedicated theater room last year—black walls, acoustic panels, a projector that cost more than my car. He was proud of the system. He should have been. But when I glanced at the rack, every component glowed blue. Receiver. Media player. Power conditioner. Even the damn Blu-ray player he hadn’t touched in eight months. “I keep it all on,” he said, “because the DAC sounds warmer after an hour of warm-up.” That hurt to hear. The belief that gear must stay powered 24/7 to sound its best is perhaps the single most expensive myth in home theater. The catch is—for some analog circuits, yes, thermal stabilization matters. But the difference after ten minutes versus ten hours? For modern solid-state gear, negligible. You're not preserving audio nirvana. You're paying to heat a rack of components that could be cold.

I have seen this pattern repeat: people run their entire system in standby because they once read that a preamp’s capacitors need constant polarization. That logic applied to certain 1970s electrolytic caps, not to the switching power supplies in today’s Denon or Marantz units. The trade-off is brutal—you keep the hum alive, and your electricity bill silently climbs. One receiver in standby draws roughly 10–15 watts. That doesn’t sound like much. Multiply by thirty days, by twelve months, by the three components you’re keeping warm. You lose a day’s worth of streaming power every year. For nothing.

Fancy Automation Apps That Drain More Than They Save

The irony is sharp: you install a smart home controller to reduce waste, and it becomes the largest phantom load in the room. Control4. Crestron. Even a humble Harmony hub—these devices stay awake constantly, polling for commands, maintaining network connections, listening for IR blasts. Most theater nerds assume the hub uses a few pennies. Wrong. A typical automation controller pulls 20–40 watts, round the clock. That’s double what a receiver in standby uses. The automation app you bought to turn things off actually keeps a server alive in your rack. Worth flagging—many of these systems require a dedicated power supply that never sleeps, because if it sleeps, you lose the ability to turn things on remotely. So you’ve built a system that saves convenience but burns base load. The fix? Hard-wire the controller to a separate switched outlet, and cut its power at night manually. Or accept the trade-off: remote access costs watts.

“I added a smart strip to kill standby. Then the automation hub died because I cut its power overnight. Now I just leave everything on.”

— Forum post from a user who missed the point entirely

Field note: energy plans crack at handoff.

That sentiment is everywhere. People confuse control with efficiency. The hub itself needs to be managed, or it becomes the problem.

Over-Wiring: Daisy-Chaining Power Strips That Bypass the Master Kill

This one is subtle. You buy a high-end power conditioner with a master switch. Great. Then you plug a cheap strip into the conditioner’s switched outlet to accommodate extra wall warts—a Raspberry Pi running Roon, a USB charger for the remote, a wireless subwoofer transmitter. Suddenly the master switch doesn’t kill everything; the Pi stays alive because it’s on the unswitched tap of the daisy-chain. The phantom load persists, hiding inside the rack like a leaky pipe behind drywall. Most teams skip this step: they don’t map which outlets are truly switched versus always-on. The result is a theater that appears off but still draws 30 watts from forgotten adapters. The fix is brutal but clean—label every plug. Banish unswitched taps for anything that doesn’t need to record or update overnight. If your subwoofer transmitter needs a reboot every morning, fine. That’s a problem you can see. The 5-watt draw you never think about? That’s the hum that stays alive.

Maintenance: The Long-Term Cost of That Blue LED

Swollen Capacitors From Constant Trickle Power

I pulled apart a seven-year-old A/V receiver last month. The owner complained about random shutdowns and a faint buzzing through the center channel. What I found inside was a graveyard: three swollen electrolytic capacitors near the standby power rail, their tops bulged like aluminum soda cans left in a freezer. That blue LED you leave glowing 24/7? It keeps a low-voltage supply active, and that supply never gets a rest. Capacitors are electrolytic—they contain wet electrolyte inside a sealed can. Heat accelerates chemical evaporation. Trickle power generates constant, low-grade heat; the caps dry out, capacitance drifts, ripple current spikes, and eventually the rail fails. The fix cost $180 in labor and parts. The energy saved by flipping one power strip would have been maybe $12 over those seven years. Wrong trade-off.

Shortened Lifespan of Power Supplies

The power supply in your subwoofer or preamp is not a continuous-duty appliance. It was designed for on-off cycles—warm up, run, cool down. Phantom load forces it into a permanent half-on state. The switching transistors in the primary side weaken under sustained micro-load. I have seen the same failure pattern in three different brands: a single blown MOSFET on the standby rail, taking the main fuse with it. The part itself costs $4. The service call: $150. That hurts.

The catch is that most owners blame the device's age, not the always-on habit. "Oh, it's eight years old, time to upgrade." But that AVR would have run another five years if the standby rail had been killed properly. Every minute that blue LED stays lit, the electrolytic caps in the secondary side bake a little longer. The fan doesn't spin, so heat builds in the core of the winding. That's the silent degradation nobody measures.

'I thought leaving it on "ready" was better for the electronics. Turns out the electronics were slowly cooking themselves.'

— owner of a 2018 Denon X3500H, after cap replacement

The Electric Bill: $10 a Year Per Device Adds Up

Ten dollars per device. Per year. If you have a receiver, a subwoofer, a streamer, a game console, and a TV—that's five devices. Fifty dollars annually for absolutely nothing. A rack with twelve components pushes past $120. Over a decade, you're burning through the cost of a decent pair of bookshelf speakers, just to keep tiny orange LEDs alive.

Wattage varies: most AVRs pull 50–80W in standby with HDMI passthrough enabled. A typical smart TV draws 15–25W when 'off' but listening for voice commands. A game console in instant-on mode sits around 10–15W. Multiply by 8,760 hours. That's real carbon and real cash. The rhetorical question: would you pay $120 a year to leave a 15-watt nightlight on in a room you never enter? That's exactly what a loaded home theater rack does.

One last pitfall: many people think phantom load is a minor cost, so they ignore it. But the hardware damage is not minor. Replacing a blown amplifier board because a capacitor failed from constant heat costs far more than the electricity wasted. The irony is that the very 'convenience' of instant-on shortens the device's life. Kill the hum, save the caps, keep the cash. Don't let that blue LED become a funeral pyre for your power supply.

When Phantom Load Is Actually Fine

If your device needs to wake on LAN or schedule

Not every glowing LED is a sin. I have a Denon AVR—six years old, still going strong—that sits in standby almost permanently. The reason: it runs a nightly room correction poll at 3 AM, re-measuring speaker distances and EQ curves as the room shifts with humidity. Kill the standby, kill the calibration. That trade-off matters. Wake-on-LAN (WoL) is another case where phantom load earns its keep; if you want to stream from a Plex server that boots on demand, the NIC needs a trickle of power to listen for the magic packet. Without that 1–2 watt whisper, you're walking across the room to press a button every time. The catch? Most WoL setups draw less than 0.5W. That's not nothing—but it's also not the 15W vampire that crushes your electric bill.

The same logic applies to satellite receivers that check for OTA guide updates at 4 AM. You could schedule a hard power-off, but you'd wake to a blank EPG. Pick your poison: a few cents a year in standby draw, or the annoyance of a manual guide refresh. I've seen setups where the homeowner spent $80 on a smart plug to cut 0.3W—and the plug itself idled at 0.8W. That hurts. You've made the problem worse.

When convenience outweighs a few cents per year

Let's run a brutal number: a single HDMI-CEC enabled device in standby—say a 2022 Sony OLED—draws roughly 0.4W while listening for the remote. At $0.12 per kWh, that's about 42 cents per year. A dollar if your rates are California-crazy. That sounds fine until you multiply it across a full rack: AVR, streamer, game console, cable box, subwoofer amp. Suddenly you're at $5–8 annually. Still not ruinous. But here's the editorial rub—for some people, that $5 is the cost of avoiding a headache. My father-in-law's receiver won't re-pair with the Bluetooth remote if fully disconnected. Every cold boot means a 10-minute recalibration ritual. He tried. He gave up. That's not laziness—it's physics fighting convenience.

Worth flagging—some devices lose their network config on total power loss. If your home theater relies on a static IP for multi-room sync, killing standby means re-entering settings every time. That's not a phantom load problem. That's a design flaw you're now paying for in time. The right move? Measure the actual draw with a $15 Kill-A-Watt. If it's under 1W and the device does something useful in standby—maintains clock, checks for firmware, listens for voice commands—leave it. The guilt isn't worth the two dimes.

Not every energy checklist earns its ink.

'I spent more time arguing about the standby light than it cost to run the damn thing for a decade.'

— friend after measuring his 2009 Oppo player at 0.6W idle

During firmware updates that only run on standby

This one bites the rush-to-unplug crowd. Many modern components—especially network-connected receivers and smart TVs—will only download and apply firmware patches while in standby mode. The logic is sound: the device assumes you're not watching, so it can safely reboot without interrupting a movie. If you yank the power after every use, that critical update never installs. Then you wonder why the HDMI handshake fails or the new streaming app crashes. The worst case: a security patch sits, and your router sees the device as a vulnerability vector.

I've seen this exact pattern blow up at a friend's setup. His LG C1 stayed hard-off for two years via a smart strip. Eventually the WebOS apps stopped working. The fix? Leave it in standby overnight with network enabled.

Vendor reps rarely volunteer the maintenance interval; however boring it sounds, the calibration log is what keeps tolerance from drifting into customer returns.

Next morning, three updates queued and applied. The phantom load for that night? Roughly 0.3W—about the same as a nightlight. Not every hum is waste. The trick is knowing which hums serve you, and which ones just hum.

FAQ: Open Questions From Real Home Theater Owners

Does a surge protector block phantom load?

No—and this is where most people waste twenty bucks for nothing. A standard surge protector is just a glorified extension cord with a metal-oxide varistor inside. It clamps voltage spikes, sure, but it does nothing to stop the trickle of power your receiver, subwoofer, or streaming box draws while 'off.' I have measured this on a Kill A Watt meter: a mid-tier Denon AVR pulls 14 watts in standby. Plugged into a surge protector vs. directly into the wall? Same draw. The protector's switch only kills power to the outlet if you flip it. That said, there is one exception: a switched power strip with a physical cutoff—but that's not surge protection, that's a manual kill switch. Worth flagging—some 'smart' surge protectors with master-slave outlets can detect when your TV goes to sleep and cut peripherals automatically. Those actually reduce phantom load. The dumb black brick won't.

Is it worth unplugging the PS5 every night?

Depends on your sleep habits and your electric rate. I ran the numbers on a PS5 in rest mode with downloads disabled: 1.3 watts. That's roughly $1.50 per year. Unplugging it saves pennies. The catch is—if you leave fast-start enabled, the PS5 pulls 8 to 10 watts. Now we're talking $8–12 annually. Not a fortune, but not nothing. The real trade-off is convenience versus wear. Every time you cut power to a modern console, it runs a disk check on boot. Over years, that does more harm to the SSD's write cycles than the phantom load costs in electricity. My advice? Leave it plugged. Set rest mode to disable USB charging and network features. That drops standby draw below 2 watts. One rhetorical question matters here: would you rather pay $10 a year or replace a drive early?

Do USB-powered devices count as phantom load?

Absolutely—and they're sneaky because the adapter itself burns power even when nothing is plugged in. I tested a cheap Amazon-brand USB wall wart: 0.4 watts with no load. That's almost nothing. But stack five of them—TV, soundbar, LED strip, phone charger, game controller dock—and you hit 2 watts. Across a year, that's under $3. Not a crisis. The real hidden cost shows up with powered USB hubs and charging docks that keep their internal regulators active. A 7-port Anker hub with nothing connected? I measured 1.9 watts steady. That's $2.30 a year—per hub. Most home theater nerds have two or three. The fix is trivial: plug USB power adapters into a switched strip alongside the main gear. When you kill the TV, the wall wart dies too. Worth flagging—some soundbars use USB for firmware updates. Disconnecting the USB cable while the soundbar is on can trigger a reset. That hurts.

'I unplugged my subwoofer every night for a year. Saved six bucks. Then the binding posts corroded from moisture and dust. Replacement cost me $120.'

— reader email, after he stopped following bad advice

Bottom line for your rack: the devices you think are safe—USB chargers, LED bias lights, network switches—often draw more cumulative phantom load than your actual AVR. Kill them at the strip. Leave the PS5 and receiver in low-power standby. And for the love of 120 volts, stop unplugging your subwoofer unless you live in a desert.

Next Steps: Kill Your Hum, Not Your Convenience

Buy a Kill-A-Watt and measure your own setup

Numbers lie. Your gut lies harder. I once swore my projector pulled 2 watts in standby—turns out it was 14, plus another 9 from the powered HDMI balun I forgot existed. A $35 Kill-A-Watt meter ends the guessing. Walk your rack: plug each component in cold, read the idle draw, write it down. The catch is that most receivers show 0.0w when off, then suddenly demand 18w when you toggle the “network standby” flag hidden three menus deep. That blue LED you can see from the kitchen? Probably nothing. The real vampire is the AV pre-pro that keeps its Ethernet port alive so it can check for firmware updates at 3 AM. Measure for ten minutes, not ten seconds—some gear pulses power every 90 seconds to poll the network. Run that test on Friday night; by Sunday you’ll know exactly which devices cost you coffee money.

Install a switched power strip with a visible master

The classic fix works because it’s dumb. Buy a strip where one outlet controls the rest—plug your receiver or processor into that master jack. When you turn off the AVR, the strip kills power to the subwoofer, the streaming box, the DSP crossover that draws 11w just to show a clock. But there is a pitfall: some pre-amps lose their custom EQ curves after a hard power cut. Worth flagging—that defeats the convenience you’re trying to protect. Solution? Plug the device that holds your calibrated settings into an always-on outlet on the same strip, and everything parasitic into the switched bank. Now you kill the hum without killing your Dirac or Audyssey memory. I have seen this fix slice 65w of phantom draw from a single rack—enough that the owner stopped noticing his electric bill tick upward every movie night.

Schedule a weekly ‘power down’ night

Not every component needs to be ON 24/7. Pick one night—Sunday, midnight, whatever sticks—and flip the master switch on that power strip. Hard reset for the whole system. This does two things: it forces connected gear to clear their cached network sessions (which stops the random 3 AM wake-ups that keep the Ethernet alive), and it gives you a regular moment to check for anything that stayed bright. A single night of total power-down per week can cut 15–20% of your phantom load alone. The trade-off? If your PVR has a scheduled recording at 2 AM Monday, you just silenced it. Adjust the night to match your recording black hole, or skip this step if you DVR late-night talk shows religiously. Otherwise: simple, repeatable, effective.

“I unplugged my main system for three days while on vacation. Came back to a $6 lower bill and a receiver that felt colder than it had in years.”

— real note from a forum lurker who finally measured, then acted

Nobody asks you to live in the dark. The goal is to kill the hum, not your convenience. Grab a meter this weekend. Label your plugs. See what stays awake when you think everything is asleep. Most people find one or two devices that shouldn’t be buzzing—and that one change pays for the meter inside two billing cycles. Try it. The blue LED can stay if it earns its keep.