The five-dollar fix for hardware nobody is standing in front of
Every home lab eventually manufactures the same 2am problem: equipment that needs a finger, and nobody near it. A server wedged so hard that Wake-on-LAN won’t touch it. An air conditioner that only speaks infrared. A garage door whose manufacturer decided you were no longer the customer. None of this gear is broken — it just has an interface designed for a person standing directly in front of it.
The fix is to stand something in front of it for you. An ESP32 dev board costs less than a coffee, carries Wi-Fi and Bluetooth on the die, and — thanks to ESPHome — mostly doesn’t require writing firmware at all. I read a piece over on XDA that surveys several of these gadget revivals, and it’s a good tour. But I’d push the framing further for home lab people: the ESP32 isn’t a hobbyist toy, it’s remote hands. It is the cheapest out-of-band management you will ever buy.
Buy for the drawer, not the project
First mistake everyone makes: “an ESP32” is a family, not a chip. The original ESP32, the S3, the C3 and the C6 all carry the name and they are not interchangeable — different radios, different capabilities, and only some of them do the things a given project assumes.
- Classic ESP32 (WROOM/WROVER modules): the safe default, and the only variant with Bluetooth Classic. That matters for audio projects and some legacy tinkering.
- S3: more RAM, native USB, the one to grab for anything driving a screen.
- C3/C6: cheaper and smaller. Fine for sensors and blasters, wrong for Bluetooth Classic audio.
My advice is boring and I stand by it: buy five classic dev boards, put them in the drawer, and stop optimising. For things that get sealed into walls and ceilings, standardisation beats every other virtue.
Second: skip the soldering iron if you want. Pre-built modules exist for nearly everything below — IR transmitter boards, optocoupler breakouts, the works — and ESP Web Tools lets you flash firmware straight from a browser tab. The barrier to entry here is genuinely just willingness.
The project that pays for the whole drawer: a remote power and reset button
A PC’s power button is not magic. It shorts two pins on the motherboard’s front-panel header. Reset does the same on its own pair. The power LED is just a signal waiting to be read. Wire an ESP32 to those points through optocouplers and you can press the button from your phone, hold reset for five seconds, and — critically — know whether the machine is actually running.
This is the feature Wake-on-LAN pretends to cover. WoL handles “off”. It does nothing for “hung with the fans at 100%”, which is the failure mode that actually ruins nights. A reset you can press remotely plus a sensor reporting power state is out-of-band management, home lab edition, for about ten dollars.
The optocouplers matter more than people credit: they keep the ESP32 electrically isolated from the motherboard, so a wiring mistake costs you a five-dollar board instead of a motherboard. In ESPHome the whole thing is a configuration file, roughly:
# Remote finger for a server's front panel
switch:
- platform: gpio
pin: GPIO26 # opto across the PWR_BTN pins
id: power_button
name: "${hostname} power button"
restore_mode: ALWAYS_OFF
on_turn_on:
- delay: 300ms # roughly a human press
- switch.turn_off: power_button
binary_sensor:
- platform: gpio
pin:
number: GPIO33 # opto across the power LED header
inverted: true
mode:
input: true
pullup: true
name: "${hostname} powered"
device_class: power
One caveat the blog posts skip: the ESP32 needs power while the PC is off. Give it its own USB charger, or use a motherboard port that stays live in standby. Otherwise your remote hands go dark at exactly the moment you need them.
Infrared: making dumb appliances honest
Anything that obeys a remote control has an API — it’s just line-of-sight and one-way. An IR LED (or a two-dollar transmitter module) plus a receiver to capture the original codes, all through ESPHome, turns a non-smart air conditioner, fan or TV into something Home Assistant can automate. The aircon starts following a schedule instead of a habit; the TV volume can dip when a call starts. No cloud account, no vendor app, nothing phoning home to a company that will one day turn the whole thing off.
The garage door, back under local control
In late 2023 Chamberlain cut off third-party access to its MyQ platform, and Home Assistant’s response was instructive: rather than fight it, they removed the integration and pointed everyone at ratgdo. The ratgdo32 is an ESP32-based board that wires to the same low-voltage terminals as your wall button — and it speaks Security+ 2.0 natively. That detail is the whole game: on newer Chamberlain and LiftMaster openers the wall button isn’t a switch at all, it’s a serial device, and a dumb relay across the terminals achieves nothing. With ratgdo32 you get the door, the light, the lockout, and obstruction sensor status — locally, permanently, no subscription.
The one I’d skip
Bluetooth audio. It sounds like a perfect match — old speakers, new phone — but only the classic chip does Bluetooth Classic, the friendly firmware (Squeezelite-ESP32) wants 4MB of PSRAM, so you’re shopping WROVER modules, and the realistic ceiling is “acceptable in a kitchen”. If you want whole-home audio, buy proper gear once. Don’t spend three weekends teaching a five-dollar chip to almost do it.
The pattern worth taking away
The unifying idea is bigger than any single project: if a device has a button or a blinking LED, it has an interface, and a five-dollar board is the adapter between that interface and your network. Most “smart home” spending goes to buying new endpoints. The better trick is usually to keep the endpoint and replace the access.
Inspired by 4 forgotten gadgets an ESP32 can resurrect on the cheap (XDA Developers).