How To Build Diy Smart Home Motion Sensor

Auto-generated transcript. Minor errors may exist. The audio is the authoritative version.

Opening Signature

You can walk into any big-box store and buy a smart motion sensor. So why would you ever build one yourself?

Because the off-the-shelf sensor you buy for forty bucks forces you into an ecosystem. The one you build for twenty-five dollars lets you own the data, choose the radio, and solve a problem that doesn’t exist in a box yet.

I’m Nick. You’re listening to *After the Install* — the show where we talk about what happens after you stop following the instructions and start actually owning your smart home.

Today, we’re building a motion sensor from scratch. And by “from scratch,” I mean you and a breadboard and about forty-five minutes on a Tuesday evening. No soldering iron required. No engineering degree. Just curiosity and a willingness to ask, “Why can’t I do this better than the box store?”

Context — Why DIY Makes Sense Right Now

Let’s talk about the market as it exists in November 2024.

You walk into a big-box store or open Amazon, and you see the same four or five options. Aqara motion sensors — about fifteen bucks each. But they need an Aqara hub, which is another forty dollars. Hue motion sensors — about forty dollars each. But they need the Hue Bridge, which is sixty dollars. And neither of those sensors talks to each other.

That’s ecosystem lock-in. You’re not buying a sensor. You’re buying a lease on a specific company’s walled garden.

Now, here’s the thing. The hardware inside those forty-dollar sensors costs about four dollars. The PIR element — the thing that actually detects heat changes — is a standard part that costs less than your morning coffee. The microcontroller inside is often a variant of the same chip you can buy for three dollars on a development board.

So why don’t more people build their own?

Because until about 2021, the software side was the barrier. You needed to write C++ code. You needed to understand interrupts, pull-up resistors, debounce timers. You needed to be a hobbyist with a soldering iron and a multimeter and a lot of patience for serial monitor debugging.

That’s changed.

Two things happened. First, the ESP32 microcontroller became ubiquitous and cheap — about six dollars on Amazon for a development board that includes WiFi and Bluetooth. Second, a project called ESPHome matured into something that’s genuinely approachable.

ESPHome lets you write a configuration file in YAML — that’s a simple text format — and it generates the firmware for you. You don’t write code. You write a recipe. The software does the compilation, the flashing, and the integration with Home Assistant.

This changes who can build a sensor. It’s no longer the domain of people who can recite the pinout of an ATmega328P from memory. It’s for anyone who’s willing to follow a ten-line template and plug in four wires.

And here’s the key phrase for this episode: This is about moving from being a tenant in your smart home to being the landlord.

You don’t ask permission from Aqara or Philips or Samsung to add a sensor. You build it. You configure it. You decide where the data goes and who sees it.

Point 1 — The “Why” — Strategic Control Over Cost and Data

Let me give you a specific comparison.

A three-pack of Aqara motion sensors on Amazon runs about sixty dollars as of this recording. That’s twenty dollars per sensor. But you also need the Aqara hub, which is another forty dollars. So your entry cost for three sensors is about a hundred bucks.

Now, let’s look at the DIY path.

An ESP32 development board — I recommend the HiLetgo ESP32 Development Board, which is about seven dollars on Amazon — paired with a standard HC-SR501 PIR motion sensor module at about three dollars. Add a breadboard for two dollars, some jumper wires for five dollars, and a micro-USB cable you probably already have in a drawer.

That’s about seventeen dollars for your first sensor. And the second one? You already have the ESPHome configuration. You already have Home Assistant set up. The marginal cost drops to about ten dollars per sensor — just the ESP32 and the PIR module.

But here’s the thing. The cost savings are real, but they’re not the main reason to do this.

The main reason is data ownership.

When an Aqara sensor detects motion, the signal goes to the Aqara hub, which processes it and sends a notification to your phone. On the way, that data passes through Aqara’s cloud servers. Now, I’m not saying Aqara is doing anything nefarious with that data. But the architecture means they *could*. And more importantly, if their cloud service goes down — which has happened — your motion sensor stops working.

With a DIY sensor, the motion detected signal goes directly from the ESP32 to your Home Assistant instance over your local WiFi network. No cloud. No third-party server. No subscription. The data never leaves your house.

I set this up in my office closet last year. The sensor sits on a shelf above the door, pointing down at the entryway. When I walk in, the light turns on. When I leave and the timer expires, the light turns off. That’s it. Simple. Local. Reliable.

And I know exactly what happens with that data because I wrote the configuration. It’s stored in my Home Assistant database on a Raspberry Pi in my basement. No one else’s server ever knows I got up for a midnight snack.

You’re not buying a product when you build a DIY sensor. You’re buying an open-ended capability. The same ESP32 that runs your motion sensor can also report temperature and humidity if you add a DHT22 sensor for another four dollars. It can monitor a door contact. It can control a relay. It’s a platform, not a product.

And that’s the strategic advantage. You’re not locked into one company’s roadmap. When Aqara decides to discontinue a hub or change their API, you don’t care. Your sensor works because you control the firmware.

Point 2 — The “How” — A Practical, Non-Scary Parts List and Assembly

Let me walk you through a build that requires exactly zero soldering.

You need four things.

First, the brain. The ESP32 dev board. I’m recommending WiFi for your first build because it’s the simplest path. The ESP32 is the Swiss Army knife of microcontrollers — powerful, well-supported, and the documentation is excellent. You can find a reliable one from HiLetgo or Drok on Amazon for about seven dollars.

Second, the eye. The HC-SR501 PIR motion sensor module. This is the standard. It’s been in production for over a decade. It’s not fancy. It works. You can get a five-pack on Amazon for about ten dollars.

Here’s what most people don’t know about this sensor. It has two small potentiometers on the back — little screw adjusters. One controls sensitivity, the other controls the delay time — how long the signal stays high after motion is detected. This is a physical feature that most smart sensors lack. With a commercial sensor, you adjust delay in an app. With this one, you turn a tiny screw with a jeweler’s screwdriver. It’s more tactile. It’s more reliable.

Third, the connection. The HC-SR501 has three pins: VCC, GND, and Signal. You connect VCC to the 5V pin on the ESP32. GND to GND. Signal to any GPIO pin — I use GPIO 4. That’s it. Three wires.

When I set this up in my office closet, I used a spare USB phone charger and a long micro-USB cable for power. The ESP32 draws about 80 milliamps. Any old charger works. It was trivial.

Fourth, the software. ESPHome.

This is the magic. You install the ESPHome add-on in Home Assistant. You create a new device. You paste in a configuration file that’s about ten lines long. It looks like this:

“binary_sensor: – platform: gpio pin: GPIO4 name: ‘Office Motion Sensor’ device_class: motion”

That’s it. That’s the whole configuration. ESPHome compiles that into firmware, flashes it to the ESP32 over USB, and the sensor appears in Home Assistant automatically.

This is less like building a circuit and more like following a recipe where the instructions talk back to you.

You plug in the ESP32. You open the ESPHome dashboard. You click “Install.” The software handles the WiFi credentials, the Home Assistant integration, everything. Ten minutes from opening the box to having a working sensor.

And the best part? If you want to change the behavior — make the delay longer, add a temperature sensor, change the GPIO pin — you edit the YAML file and click “Install” again. The ESP32 updates over WiFi. You don’t even need to unplug it.

Mid-Roll CTA

Staring at a list of parts is the hardest part. We’ve made it easy. Go to AfterTheInstall.com/motionsensor for our one-click shopping list on Amazon, a copy-paste-ready ESPHome YAML configuration file, and a quick-start guide. Download it for free. It’ll save you an hour of cross-referencing datasheets.

Point 3 — The “Next Level” — From Clunky Prototype to Polished Performer

You’ve got the breadboard working. The sensor triggers. Home Assistant shows motion. Congratulations. But the breadboard is not the finish line.

Let’s talk about turning that prototype into something that’s invisible and reliable.

First — and this is the number one mistake I see — placement.

PIR sensors detect heat changes, not motion. They have two slots in the sensor element, and the lens focuses infrared radiation onto those slots. When a warm body moves across the field of view, the signal changes between the two slots, and the sensor triggers.

That means anything that creates a heat change can cause false triggers. HVAC vents blowing warm or cold air. Windows that let in sunlight that heats the floor. Radiators. Space heaters. Even a pet walking by.

My first sensor faced a sunny window. The morning sun crept across the floor, warming it gradually. The PIR sensor interpreted that as motion. My lights turned on at sunrise every day for a week before I figured out what was happening. It thought sunset was a home invasion.

The fix is simple. Mount the sensor so it points across a doorway or hallway — perpendicular to the expected path of travel. Avoid pointing it at windows, vents, or anything that changes temperature. And keep it at least six feet away from your HVAC register.

Second — enclosures.

The breadboard is for testing. For a permanent install, you need a box. A three-dollar plastic project box from the hardware store makes it safe and clean. You drill a hole for the PIR sensor lens, a small hole for the LED indicator if you want one, and a strain relief for the power cable.

I use a 4x2x1 inch project box from Hammond. It’s about five dollars on Amazon. It has screw terminals on the inside, so I don’t even need solder. The whole assembly takes about fifteen minutes.

Third — power elegance.

The USB cable works for testing. For a ceiling mount, it’s ugly. A simple 5V USB wall converter wired directly into your ceiling light’s junction box is a pro move. You can buy a Mean Well IRM-03-5 power module for about eight dollars that converts 120V AC to 5V DC. It fits inside a standard junction box. Wire it in, connect the ESP32’s 5V and GND pins, and you have a sensor that looks like it was installed by an electrician.

It depends on your wiring and comfort level. If you’re not comfortable working with line voltage, stick with the USB cable and a nearby outlet. The sensor doesn’t care.

Fourth — the radio upgrade path.

WiFi is fine for one or two sensors. But if you build ten, your WiFi network gets cluttered. Each sensor maintains a constant connection to your access point. That’s ten devices on your network that don’t need to be there.

Enter Zigbee. That’s the low-power mesh protocol. A SONOFF Zigbee 3.0 USB dongle — about twenty dollars — plugs into your Home Assistant server and acts as a coordinator. Then you build your sensor using a Zigbee radio module instead of the ESP32. The CC2530 or the EBYTE E18-MS1-PCB are good options. They’re about five dollars each.

The advantage? Zigbee sensors run on batteries for years. They form a mesh network — each sensor extends the range of the others. And they don’t touch your WiFi at all.

The trade-off? The configuration is more complex. You need to flash the Zigbee module with custom firmware. It’s doable, but it’s not a first build.

Start with WiFi. Learn the workflow. Then upgrade.

The goal isn’t a science project on your shelf. It’s an invisible, reliable sentry in your wall.

CTA — Your First Step Today

Your project for today is not to build the sensor.

Your project for today is to take the single step that makes it possible.

Open your browser. Go to the Home Assistant website — home-assistant.io. If you already have Home Assistant running, open your instance. Look for the ESPHome add-on in the add-on store. Install it.

That’s it. That one action — installing ESPHome — opens the door. With that tool installed, you have the platform. You can flash a sensor in ten minutes.

Then head to our resource page at AfterTheInstall.com/motionsensor . Look at the simple parts list. Order just one set — one ESP32, one PIR sensor, one breadboard. Total cost: about seventeen dollars.

You can have the parts and the platform ready in two days. Two days from now, you can have a working motion sensor that you built, that you configured, and that reports to your own local server.

Our free guide walks you through the ESPHome install if you get stuck. It’s copy-paste simple. I promise.

Cross-Promo

If the idea of choosing the right radio protocol made your ears perk up, you need our deep-dive episode, “Zigbee vs. Z-Wave vs. WiFi: The No-BS Guide to Smart Home Radios.” We break down range, power consumption, latency, and ecosystem compatibility. Find it in our episode archive at AfterTheInstall.com .

Outro

Thanks for listening.

This is *After the Install*, helping you build a smarter home that’s actually smart for you.

I’m Nick. See you next week.