Motion sensors turn on lights. Presence sensors keep them on when you sit still. If you have ever waved your arms in a quiet office just to stop the lights from turning off, you know the difference. mmWave presence sensors close that gap. They detect micro‑movements like breathing, not just big steps. Used well, they make rooms feel responsive instead of fussy.
This guide walks you through a real‑world rollout. We will cover the hardware, placement, tuning, and reliability tricks that separate a quick demo from a setup you can trust every day.
Why mmWave for Presence?
PIR sensors (the little domes in many off‑the‑shelf motion detectors) are great for detecting motion. But they struggle when a person is still. Cameras can infer occupancy, but they raise privacy questions and often need cloud services. mmWave radar sits in the middle: it is privacy‑preserving, works in the dark, and picks up small motion without collecting images.
mmWave sensors emit low‑power radio waves and analyze the reflections. Modern modules can detect both dynamic motion and static micro‑motion within set ranges and zones. Many integrate simple signal processing and report clean states such as “moving target at 3.1 m” or “still presence in zone 2.”
What’s in the Box: Modules and Features That Matter
You will find two common frequency families:
- 24 GHz ISM modules: Wide availability, solid range (up to 6–8 m indoors). Examples include hobbyist‑friendly boards with UART/BLE and configurable gates. They are compact, low cost, and easy to integrate with microcontrollers.
- 60 GHz modules: Finer resolution, shorter range, and better zoning. Many consumer “AI presence” sensors use 60 GHz and expose room maps and multi‑zone detection via an app or local API. Great for high‑precision desk and room segmentation.
Key features to look for:
- Static vs dynamic sensitivity: Two separate thresholds let you distinguish a person breathing (static) from someone walking (dynamic). You want both for lights that stay on when people are seated.
- Configurable gates/zones: Set near/far ranges and ignore unwanted areas (like hallways visible through a doorway). Fine gating cuts false triggers.
- Hold times: How long the sensor reports “occupied” after motion fades. A sane hold time (e.g., 60–180 seconds) avoids flicker.
- Local API: UART, I2C, BLE, or native Wi‑Fi with an open profile. Local control is essential if you want reliability without cloud lock‑in.
- Mounting and antenna pattern: Look for a data sheet with detection cones, recommended height, and tilt guidelines. You want predictable coverage.
Placement That Works in Real Rooms
Start With a Coverage Sketch
Draw your space and mark where you need presence to hold lights or HVAC. For most rooms, one sensor covers 3–5 meters comfortably. Avoid pointing directly at moving hallway traffic that you do not want to trigger.
Mounting Tips
- Height: 1.2–2.2 m is typical. Wall mounts at chest height work well for desks and living rooms. Ceiling mounts excel in offices and bathrooms, especially 60 GHz units with zoned maps.
- Tilt: Angle the sensor to “look” at seated zones, not at the doorway or windows with blowing curtains.
- Avoid noise sources: Fans, AC vents, and thin, constantly moving drapes can create low‑level motion that looks like occupancy. Either tilt away or reduce sensitivity for the zones that see them.
- Walls and materials: mmWave can pass through thin non‑metal materials. If your sensor “sees” through drywall into the next room, shrink the far gate or add a physical baffle.
Multiple Sensors Without Chaos
In large areas, two sensors can give better coverage. mmWave modules generally tolerate each other, but if you see odd behavior:
- Mount at different angles and distances to reduce direct cross‑illumination.
- Lower the gain or sensitivity for overlap regions.
- Use different frequency families (24 vs 60 GHz) for neighboring zones if severe interference appears.
Tune the Sensor: A Practical Walkthrough
Many modules expose a simple configuration tool over serial, BLE, or a vendor app. The routine below fits most devices. Plan 15–20 minutes per room and a notepad to record your final settings.
Step 1: Baseline With No People
Power the sensor, open the configuration view, and let the room settle for one minute. Note any background activity readings. If you see persistent noise from HVAC vents or swaying plants, re‑aim or trim the detection gate that includes the source.
Step 2: Dynamic Motion Threshold
Walk into the room from the typical entry point. Watch the “moving target” value. Set dynamic sensitivity high enough that normal walking at your farthest desired distance is detected instantly, but not so high that small pet movement fires it from the edge of the cone.
Step 3: Static Presence Threshold
Sit in the intended spot (desk, couch, or conference table) and stay still for 30–60 seconds. Breathe normally. Increase static sensitivity until the sensor holds “occupied” without requiring fidgeting. If pets cause false holds, reduce static sensitivity for the lower zones or tighten the vertical field of view with tilt.
Step 4: Gates and Zones
Use the distance gates to limit detection to the actual room. If the far wall is 4.0 m, set the far gate to about 3.8 m. For 60 GHz sensors with maps, draw exclusion zones over doors, hallways, or open archways. This single step eliminates most false triggers.
Step 5: Hold Times and Grace Periods
Set a hold time that matches the task. Bathrooms may need 180–300 seconds to be kind. Desks and living rooms do well with 120–180 seconds. Layer your automations with an extra grace period timer before switching off, so a single missed micro‑motion does not plunge you into darkness.
Step 6: The “Stillness” Test
Repeat the sit‑still test while reading or typing. Lights should never flicker or timeout. If they do, bump static sensitivity slightly or add a small fallback rule, such as “if the light just turned off and a door opens within 10 seconds, turn it back on.”
Integrations: Local and Reliable
You can deploy mmWave presence alone, but it really shines when paired with a local automation engine. The goal is to keep everything on your network, fast, and private.
Common Integration Paths
- Microcontroller + local firmware: Many 24 GHz boards plug into ESP32 or similar. Use a local stack (e.g., open‑source firmware) to expose presence as a binary sensor, plus distance and confidence readings. This is highly reliable and offline‑friendly.
- Wi‑Fi presence devices: 60 GHz consumer sensors often speak directly to your home hub. Look for local APIs, MQTT, or LAN integrations so your automations do not depend on vendor clouds.
- Zigbee/Thread variants: A few mmWave presence sensors ride Zigbee or Thread for low power and mesh coverage. Make sure your hub supports the specific device profile for presence and zones.
Automation Patterns That Stick
- Lights with layers: Trigger on dynamic motion for fast “on.” Sustain with static presence for “stay on.” Add a night mode that dims instead of turning fully off after the grace period.
- HVAC and fans: Use room‑level presence to bias setpoints. For example, “occupied + working hours → temp 21°C; away → 18°C.” Add a maximum setback so the room never gets too far out of range.
- Desks and monitors: Detect seated presence to turn on task lighting and enable a smart power strip for chargers. Turn off after absence to cut vampire power.
- Bathrooms: Pair mmWave with a humidity sensor. Presence turns the fan on. Humidity extends runtime until the mirror is clear, then mmWave closes it down.
- Meeting rooms: Use two sensors for coverage. If either reports presence, mark the room as occupied in your calendar system. Release the room if both report empty for 10 minutes, even if a meeting is still on the calendar.
Reduce False Alarms Without Losing Sensitivity
Pets and Low Furniture
Many false holds come from pets curled on couches. Strategies:
- Lower static sensitivity for the bottom gate (0–1 m) if your module supports per‑gate tuning.
- Mount higher and tilt so the main lobe focuses at 1–1.5 m above the floor.
- Use sensor fusion: require both mmWave presence and pressure mat (or BLE phone proximity) for sustained nighttime lighting.
Fans and Curtains
Constant low‑speed motion can look like static presence. Fixes:
- Exclude the zone with map tools or gates.
- Tilt the sensor away from airflows.
- Set a minimum confidence threshold for static presence in software, ignoring brief low‑confidence spikes.
Through‑Wall Ghosts
Some installations detect motion in the next room. Remedies:
- Tighten far gates to end just short of the wall.
- Add a foam or 3D‑printed hood to narrow the field of view.
- Use a PIR “confirm” rule at the room entrance for turn‑on, with mmWave handling the hold.
Reliability Engineering: Treat It Like a Small System
Presence controls become part of everyday life. Build guardrails so they behave well under failure.
Fail‑Open vs Fail‑Closed
- Safety‑critical lights (stairs, hallways): fail‑open. If the sensor stops sending heartbeats, keep the lights on until it recovers.
- Energy saving cases (office lamps, fans): fail‑closed or default to manual switch control.
Heartbeats and Watchdogs
Have sensors publish a “I’m alive” status every 30–60 seconds. Your automation can watch for missed heartbeats and alert you. Reboot controllers automatically if a sensor hangs. Most microcontroller stacks support a hardware watchdog—turn it on.
Noise and Power
- Use a quality 5 V supply with low ripple if you power from USB. mmWave front‑ends dislike noisy rails.
- Keep RF modules away from switch‑mode power supplies and big metal objects that detune antennas.
- Secure connectors. Vibrations can jostle loose dupont leads over time; use proper housings or soldered headers.
Privacy and Safety
mmWave presence does not capture images or audio. It measures reflected radio energy to infer motion. That makes it a good choice for bedrooms, bathrooms, and offices where cameras would be intrusive.
On RF safety: these modules operate at very low power, far below consumer Wi‑Fi or phones. Follow the manufacturer’s mounting instructions and enclosure guidance. Do not modify the RF path with metal enclosures, and avoid direct contact with exposed boards. As with any electronics, keep modules away from water and high heat.
Case Studies You Can Copy
Small Office With Open Plan
Problem: Lights and HVAC wasted energy after people left. PIR sensors failed to hold when staff were quietly typing. Solution: two 24 GHz modules mounted at 2.1 m with shallow tilt, gates ending at 4.5 m to avoid hall traffic. Static sensitivity tuned to maintain presence when seated. HVAC setpoints shift 2°C after 20 minutes of no presence; lights dim to 30% for 5 minutes before off. Outcome: 22% reduction in lighting energy, no more hand‑waving.
Home Living Room + TV Area
Problem: TV nights triggered light flips when nobody moved for a while. Solution: a 60 GHz zoned sensor overhead, with an exclusion zone over the kitchen doorway. Lights turn on with motion, then hold on static presence. During “media mode” (TV on), presence dims accent lights to 20% instead of off, and relies on a 10‑minute absence before full off. Outcome: smooth lighting without mid‑movie surprises.
Bathroom With Quiet Fan
Problem: Fans either ran too long or cut out too soon. Solution: mmWave presence turns fan on instantly. A humidity sensor prolongs runtime until humidity returns within 5% of baseline. If presence is gone, a 2‑minute grace shuts the fan to avoid late‑night noise. Outcome: fog‑free mirrors and shorter average fan runtime.
Sensor Fusion: Better Together
mmWave excels at holding presence. Combine it with a few simple signals for rock‑solid automations:
- PIR: Fast “on” and directional triggers at doorways.
- Contact sensors: Doors and windows define context. “Door opened” can reset grace timers.
- BLE phone presence: Useful for personalizing scenes or avoiding false “occupied” when pets remain.
- Pressure mats or chair sensors: Great confirmation for seated tasks where you need absolute certainty.
Commissioning Checklist
- Decide the role: light control, HVAC bias, room booking, or all three.
- Choose frequency: 24 GHz for general rooms, 60 GHz for fine zoning.
- Plan coverage and avoidance zones on paper.
- Mount away from vents, fans, and moving drapes.
- Set dynamic sensitivity for quick “on.”
- Set static sensitivity for “stay on while still.”
- Draw gates or exclusion zones to prevent cross‑room triggers.
- Pick hold times and add grace periods in your automations.
- Establish heartbeats and alerts for sensor outages.
- Run a stillness test and a multi‑person test before calling it done.
Costs, Time, and What to Expect
Expect to spend $12–$25 per 24 GHz module and $50–$90 for polished 60 GHz room‑mapping sensors. Add an ESP32 or hub if needed, plus wiring or a USB power supply. Most rooms commission in under 30 minutes once you have a pattern. The payoff is long‑term comfort and fewer “smart home” annoyances.
Troubleshooting Quick Guide
Lights Turn Off While Seated
- Increase static sensitivity one step.
- Re‑aim to center the seated area in the main lobe.
- Lengthen hold time by 30–60 seconds and add a grace dim instead of immediate off.
False Occupancy at Night
- Reduce low‑gate sensitivity or raise mounting height to avoid pet zones.
- Exclude hallway or window zones that detect distant movement.
- Require both mmWave and a secondary signal (e.g., contact sensor closed) during night scenes.
Intermittent Drops or Weird Readings
- Check power supply quality and cable connections.
- Update firmware and reset to factory defaults, then retune.
- Move the sensor 20–30 cm to avoid standing waves caused by nearby metal.
Pro Tips for Advanced Setups
- Per‑zone logic: In a big room, set different hold times per zone. For example, longer near a reading chair, shorter near a passage.
- Confidence‑weighted automations: Some modules report signal strength. Use thresholds to prevent low‑confidence holds from keeping lights on indefinitely.
- Adaptive sensitivity: At night, reduce static sensitivity to avoid holds from pets while keeping dynamic sensitivity for human motion.
- Maintenance routine: Quarterly, run a quick stillness test and check heartbeats. Sensors do not drift much, but your furniture placement might.
Summary:
- mmWave presence detects micro‑motion for reliable “stay on” behavior without cameras.
- Choose 24 GHz for general coverage or 60 GHz for fine zoning and maps.
- Placement, tilt, and gating matter more than raw sensitivity.
- Tune dynamic and static thresholds separately, then add hold times and grace periods.
- Fuse mmWave with PIR, contacts, BLE, or mats for fewer false events.
- Engineer for reliability with heartbeats, watchdogs, and fail‑safe defaults.
- Respect privacy and safety: local processing and low‑power RF keep deployments calm.
- Expect fast commissioning and strong comfort and energy benefits once tuned.
