Disclosure: Some links in this article are affiliate links. We may earn a commission on qualifying purchases at no extra cost to you.
Most "best motion sensor" roundups rank by battery life and detection range, and both numbers are close to useless for the thing you actually care about: how fast your lights turn on. A sensor with a 7-meter range and a 60-second blind time will leave you standing in the dark waving your arms like an idiot every time you walk back into a room within a minute of leaving it. That single spec — re-trigger time, sometimes called blind time or detection interval — decides whether a motion-triggered automation feels instant or feels broken, and it's the number almost nobody puts front and center.
This guide is built around that priority. Every sensor below is evaluated first on how it behaves inside Home Assistant via a local Zigbee coordinator (ZHA or Zigbee2MQTT) or Z-Wave JS, not through a manufacturer's cloud app. None of them need a brand-specific hub to work with Home Assistant — that's a persistent myth worth killing early, and we'll get to it in the next section.
You'll find both Zigbee and Z-Wave options here, split by what they're actually good at: cheap, fast-triggering PIRs for lighting automations; multi-sensors that bundle temperature, humidity, and lux for smarter conditional logic; and one mmWave alternative for the specific problem PIR can't solve — sensing that you're still in the room even when you're sitting still.
This is written for Home Assistant users running ZHA, Zigbee2MQTT, or Z-Wave JS who want sensors that pair directly to their own coordinator, stay reliably on the mesh, and respond fast enough to make "smart lighting" actually feel smart.
Quick Reference
| Sensor | Protocol | Re-trigger time | Bundled sensors | Best for |
|---|---|---|---|---|
| Aqara Motion Sensor P1 | Zigbee 3.0 | Configurable, 2 s minimum | Lux, device temp | Fast lighting automations |
| Aqara Motion Sensor (RTCGQ11LM) | Zigbee | Hardcoded 60 s | Lux, device temp | Avoid for lighting; fine for slow security use |
| SONOFF SNZB-03P | Zigbee 3.0 | Configurable, ~5 s minimum | None usable in ZHA | Best budget pick overall |
| Third Reality Motion Sensor R1 | Zigbee 3.0 (mmWave) | Adjustable via dev console | None | Motion in awkward, bulky-friendly spots |
| Philips Hue Motion Sensor | Zigbee | Fast, near-instant | Lux, ambient temp | Reliability-first, budget flexible |
| Ecolink PIR (PIRZWAVE2.5-ECO) | Z-Wave Plus | Standard PIR check-in | None | Long-range, pure security PIR |
| Fibaro Motion Sensor FGMS-001 | Z-Wave Plus | Configurable | Motion, temp, lux, accelerometer | Design-conscious 4-in-1 |
| Aeotec MultiSensor 6 | Z-Wave Plus | Configurable | Motion, temp, humidity, lux, UV, vibration | Maximum environmental data per node |
How Motion Detection Actually Works — and Why Blind Time Matters More Than Range
Every sensor in this guide except the Third Reality R1 uses a PIR (passive infrared) element — it detects the heat signature of a moving body crossing its field of view. PIR is motion detection, not presence detection: it fires when something moves, then goes quiet. If you sit still at a desk, a PIR sensor has nothing to report, which is why "the lights turned off while I was still in the room" is the most common complaint in every PIR thread on the Home Assistant forums. That's not a defect — it's the nature of the technology. If that's your specific problem, an mmWave presence sensor (covered further down) solves it; a PIR sensor never will, regardless of price.
The spec that determines how responsive a PIR feels is its blind time (also called re-trigger interval or detection interval): the cooldown period after a trigger during which the sensor ignores further motion. A sensor with a 60-second blind time will not report new motion for a full minute after the last trigger — walk back into the room 40 seconds later and the light won't come back on. A sensor with a 2–5 second blind time reads as instant. This single number matters more for lighting automations than detection range, and it's exactly what most buying guides skip.
Detection range on the box is also routinely inflated. Aqara's official spec sheet claims 7 meters for its motion sensors; Home Assistant Community members testing the same units report real-world detection closer to 1.5–3 meters. Treat every manufacturer range figure as a ceiling, not a guarantee, and mount accordingly — closer and more direct is safer than trusting the spec sheet.
Myth to kill immediately: you do not need the brand's hub. Aqara, SONOFF, and Third Reality all market their sensors as working with a proprietary bridge, but that's for their own apps and for HomeKit. Any Zigbee 3.0 sensor pairs directly to a generic Zigbee coordinator (a SONOFF ZBDongle, Home Assistant Connect ZBT-2, ConBee, or similar) through ZHA or Zigbee2MQTT, with zero cloud dependency. Z-Wave sensors work the same way through Z-Wave JS and a Z-Wave controller. The only genuine exception on this list is the Philips Hue Motion Sensor, where the official Home Assistant integration goes through a Hue Bridge for the most reliable experience — though it can also be paired raw to a Zigbee coordinator if you'd rather skip the Bridge.
One more mesh fact that trips people up: battery-powered PIR sensors are Zigbee/Z-Wave end devices. They don't route or repeat mesh traffic — only mains-powered devices like smart plugs and bulbs do that. A healthy sensor mesh depends on having enough mains-powered routers nearby, not on the sensors themselves. Aqara and Xiaomi devices in particular are known for dropping off meshes built on non-Aqara-friendly routers (older Centralite, GE, Iris, or Sylvania gear); bonding the sensor directly to the coordinator during pairing usually resolves this.
Best Budget Zigbee Motion Sensors
SONOFF SNZB-03P — The Best Value Pick
The SNZB-03P is the sensor most Home Assistant users should start with. It pairs to ZHA or Zigbee2MQTT with no SONOFF hub required, uses a single CR2477 coin cell rated around three years under normal use, and — crucially — its detection interval is configurable down to roughly 5 seconds in Zigbee2MQTT, out of a factory default of 60 seconds. That adjustability is what separates it from cheaper PIRs that lock you into a slow blind time.
Specs
- Zigbee 3.0, ZHA/Zigbee2MQTT native
- 1× CR2477 battery, ~3-year rated life
- 6 m range, 110° field of view (official)
- Detection interval configurable 5–60 s in Zigbee2MQTT
- 44 × 44 × 65 mm, magnetic base + adhesive + screws
Pros
- Fast, tunable re-trigger — the main reason to buy it
- Cheap enough to deploy in every room without a second thought
- Magnetic base makes aiming and repositioning trivial
Cons
- Internal light sensor exists but isn't exposed as a usable lux entity in ZHA
- ZHA creates a duplicate "Motion" entity alongside the working "Occupancy" entity — use Occupancy, ignore the other
- No temperature or tamper sensing
Verdict: For pure motion-to-light automations, this is the sensor to buy first and buy in bulk.
Perfect for: Anyone wiring up fast hallway, closet, or stairwell lighting on a budget.
Aqara Motion Sensor (RTCGQ11LM) — Good Sensor, Wrong Job
This is the original Aqara PIR, and it's still widely sold and widely recommended — often incorrectly. Zigbee2MQTT's own device page is explicit about its biggest limitation: the sensor ignores all motion for exactly 60 seconds after a trigger, and that value is hardcoded. Lowering it requires an actual hardware modification, not a configuration change. For a security-style sensor that just needs to report "something moved here recently," that's fine. For a hallway or bathroom light you want to feel responsive, it's a poor match.
Specs
- Zigbee, ZHA/Zigbee2MQTT native
- 1× CR2450 battery
- 7 m range, 170° field of view (official; real-world noticeably shorter)
- Hardcoded 60 s blind time
- 30 × 30 × 33 mm
Pros
- Wide field of view on paper
- Cheap and widely available
- Includes lux and device-temperature reporting
Cons
- 60-second blind time makes it a poor choice for lighting automations
- Real-world detection range commonly reported well under the 7 m spec
- Known to drop off mesh through incompatible third-party routers
Verdict: Buy this for a slow-changing security zone, not for a light switch replacement.
Perfect for: Low-frequency "was anyone in this room recently" automations — not fast lighting.
The Sensor to Buy for Fast Lighting Automations
Aqara Motion Sensor P1 (RTCGQ14LM)
The P1 fixes the exact problem the original Aqara sensor has: its detection interval is configurable all the way down to 2 seconds via Zigbee2MQTT, which makes it one of the fastest-feeling PIR sensors you can pair directly to a Home Assistant coordinator. It also reports lux above the 1,000-lux ceiling that trips up older sensors, which matters if you're gating automations on "only turn on lights if it's dark."
Specs
- Zigbee 3.0, ZHA/Zigbee2MQTT native
- 2× CR2450 batteries, rated up to 5 years (LED off, interval ≥30 s)
- 170° up to 2 m / 150° up to 7 m (official; real-world testers report closer to 1.5–3 m)
- Detection interval configurable 2–65,535 s
- Lux (above 1,000 lux) and device-temperature reporting
- 33.1 × 33.1 × 41.6 mm, adjustable stand
Pros
- Genuinely fast, tunable re-trigger — the best in the Zigbee lineup for this
- Usable lux sensor for darkness-gated automations
- Adjustable stand makes aiming easier than flat wall-mount designs
Cons
- Real-world range is meaningfully shorter than the spec sheet
- Setting changes (sensitivity, interval) frequently fail unless you wake the sensor first with a tap
- OTA firmware updates through Zigbee2MQTT are unreliable
Verdict: If you want one sensor per room that reacts instantly and reports usable lux, this is it — set the interval to 2–5 seconds and keep it near the coordinator or a router if you can.
Perfect for: Living rooms, offices, and any space where you want lights to feel instantaneous.
When PIR Isn't Enough: mmWave Presence
Third Reality Motion Sensor R1
If your real complaint is "the lights turn off while I'm sitting at my desk," no PIR sensor on this list will fix it — that's a presence problem, not a motion problem. The R1 uses 5.8 GHz mmWave radar instead of PIR, which lets it detect a stationary body rather than just movement. It pairs directly to ZHA or Zigbee2MQTT with no Third Reality hub required.
Specs
- Zigbee 3.0, mmWave radar (not PIR)
- 3× AA batteries, rated up to 3 years
- Adjustable range 1.5–9.5 m across 5 sensitivity levels
- Reports a combined motion/occupancy state, plus battery, voltage, and signal strength
- No lux or temperature reporting
- End device — does not repeat mesh traffic
Pros
- Actually detects stationary presence, not just movement
- Range and sensitivity adjustable on-device
- Works reliably under both ZHA and Zigbee2MQTT
Cons
- Bulkier than a typical PIR puck (three AA cells add size)
- Cooldown/clear time is only adjustable through the Zigbee2MQTT developer console, not a first-class setting
- No environmental sensors at all
Verdict: A solid, honestly-specced presence sensor for the one job PIR genuinely can't do — just budget for the extra bulk.
Perfect for: Desks, reading chairs, or any spot where "still there" needs to count as "occupied."
Premium Zigbee Pick: Philips Hue Motion Sensor
Hue's motion sensor costs noticeably more than the SONOFF or Aqara options, and the reason people keep buying it anyway is consistency: it's widely regarded as one of the fastest and most dependable PIRs in this category, with a usable lux sensor and ambient temperature reporting bundled in.
Specs
- Zigbee, integrates via Hue Bridge (recommended, fully local LAN API) or direct pairing to a Zigbee coordinator
- 2× AAA batteries (indoor model), multi-year life
- ~5 m range, roughly 100° field of view
- Fast, reliable re-trigger
- Ambient light (lux) and temperature reporting
- Articulating magnetic mount — the most flexible mounting in this lineup
Pros
- Best-in-class reliability and speed for a battery PIR
- Genuinely useful bundled lux and temperature data
- Mounting flexibility beats every flat wall-mount competitor here
Cons
- Noticeably pricier than the Zigbee budget options
- If configured in both the Hue app and Home Assistant simultaneously, automations can fight each other — pick one control path
- Some users report the battery entity missing from the Home Assistant integration
Verdict: If budget isn't the deciding factor, this is the most dependable PIR on this list, full stop.
Perfect for: Anyone who's been burned by flaky budget sensors and wants to stop troubleshooting.
Z-Wave Motion Sensors
Z-Wave gets skipped in most Zigbee-heavy roundups, which is a mistake — Z-Wave's sub-GHz frequency avoids 2.4 GHz congestion entirely, and Z-Wave JS now makes local integration in Home Assistant just as straightforward as ZHA. It's a legitimate option, especially if you're already running Z-Wave devices elsewhere in the house or want longer range with less interference.
Ecolink PIR Motion Detector (PIRZWAVE2.5-ECO) — Pure PIR, Long Range
No frills, no bundled sensors — just a long-range, reliable Z-Wave Plus PIR built for security-style coverage.
Specs
- Z-Wave Plus, S2 security, Z-Wave JS native
- 1× CR123A battery, ~3-year rated life
- ~39–45 ft detection radius, ±50° spread at max sensitivity
- Sensitivity set via a physical jumper (not a fine-grained software parameter)
- Pet immunity up to 55 lbs on newer Gen5 units
- Tamper reporting; no lux, temperature, or humidity
Pros
- Genuinely large coverage footprint for hallways, garages, and open living areas
- No cloud, no bridge, no frills — just a dependable PIR
- Pet-immune option available for households with dogs
Cons
- Sensitivity adjustment is jumper-based, not software-configurable
- No environmental data at all
- Coarser tuning than the Zigbee options above
Verdict: If you want one sensor to cover a whole room from a corner mount and don't need lux or temperature, this is the straightforward choice.
Perfect for: Garages, basements, and large rooms where range matters more than data.
Zooz 4-in-1 Sensor ZSE40 — Solid, but Discontinued
The ZSE40 bundles motion, temperature, humidity, and lux into a single Z-Wave Plus node with software-configurable trigger interval and sensitivity — genuinely useful specs. The catch: Zooz has discontinued this model in favor of its ZSE11 successor, so treat this as a "if you already own one" entry rather than a fresh recommendation, and expect limited stock.
Specs
- Z-Wave Plus (908.42 MHz US), Z-Wave JS native
- 1× CR123A (700-series) or 2× AAA (older v1)
- Trigger interval configurable 1–255 minutes; sensitivity 1–7
- 4-in-1: motion, temperature, humidity, lux
- Built-in tamper switch
Pros
- Real 4-in-1 sensor bundle for the price
- Software-adjustable trigger interval and sensitivity
Cons
- Officially discontinued — stock is limited and inconsistent
- Reports motion through burglar notification values (0/8) rather than a standard binary sensor in Home Assistant, which needs a small template workaround
- Being replaced by the newer Zooz ZSE11 — worth checking availability of that model instead
Verdict: A capable sensor if you can still find one in stock, but don't go out of your way to hunt down a discontinued model when a direct successor exists.
Perfect for: Existing Zooz households topping up their sensor count.
Fibaro Motion Sensor FGMS-001 — The Design-Forward 4-in-1
Fibaro's spherical "cat-eye" sensor is one of the most recognizable smart home devices ever made, and it backs the design up with a genuine 4-in-1 sensor bundle: motion, temperature, lux (0–32,000), and an accelerometer that doubles as tamper detection.
Specs
- Z-Wave Plus (908.4 MHz US), AES-128, firmware 3.2+ recommended for correct Z-Wave JS recognition
- 1× CR123A, ~2-year rated life
- ~7 m range, wide field of view (exact angle not officially published)
- Configurable blind time, re-trigger timer, and pet-immunity sensitivity
- Built-in accelerometer for tamper/vibration detection
- ~47 × 47 × 47 mm sphere, 24 g
Pros
- Real 4-in-1 sensor bundle including a genuinely useful lux range
- Configurable blind time and sensitivity, unlike most pure-PIR competitors
- Accelerometer-based tamper detection is a nice extra layer
Cons
- Make sure you're buying the Z-Wave SKU — a separate HomeKit-only version exists that will not join a Z-Wave network
- Older firmware isn't recognized correctly by Z-Wave JS; confirm v3.2+ before buying secondhand
- Environmental readings only report on a meaningful change (temperature/lux), not continuously, to save battery
Verdict: The most complete and best-designed Z-Wave sensor here, as long as you double-check the SKU before buying.
Perfect for: Living spaces where you want motion, temperature, and lux from one attractive, unobtrusive device.
Aeotec MultiSensor 6 — Maximum Data Per Node
The MultiSensor 6 packs six sensors into one Z-Wave Plus node: motion, temperature, humidity, lux, UV index, and vibration. It's the only sensor on this list with an optional USB power mode, which unlocks real-time reporting instead of battery-conserving throttled updates.
Specs
- Z-Wave Plus Gen5 (500-series), AES-128, Z-Wave JS native
- 2× CR123A or micro-USB power
- ~5 m range, 120° field of view
- Configurable motion timeout and sensitivity parameters
- Six sensors: motion, temperature, humidity, lux, UV, vibration/tamper
- Optional recessor and mounting-arm accessories sold separately
Pros
- The most environmental data of any sensor in this guide from a single node
- USB power mode enables real-time reporting instead of battery-throttled updates
- Reliable, rarely-missed motion detection within its stated range
Cons
- Battery life drops sharply in high-traffic areas — expect as little as 2–3 months at 200 triggers a day
- UV sensor is a niche feature most buyers won't use
- Higher per-node cost than a simple PIR
Verdict: If you want one node doing the work of six sensors and don't mind managing battery life (or wiring in USB power), this earns its price.
Perfect for: A single "smart corner" of a room where you want motion, climate, and light data all from one device.
One to Approach With Caution
Zigbee-based Tuya PIR sensors sold under names like NEO Coolcam show up frequently in budget searches, and the Zigbee variant in particular has a rougher track record in Home Assistant: it's been repeatedly misidentified by Zigbee2MQTT as an entirely different device type, occasionally reports empty or null values right after pairing, and doesn't expose a lux sensor at all. If you're comfortable troubleshooting device quirks and re-flashing device definitions, it can work — but it's not a sensor to recommend to someone who just wants something to pair and forget.
Which Motion Sensor Should You Choose?
Want fast, tunable lighting automations and don't mind a bit of setup fiddling: Aqara Motion Sensor P1, interval set to 2–5 seconds.
Want the cheapest sensor that still reacts fast: SONOFF SNZB-03P.
Want the most reliable sensor money can buy and budget isn't tight: Philips Hue Motion Sensor.
Your real problem is lights turning off while you're sitting still: Third Reality Motion Sensor R1 (mmWave), not another PIR.
You want long range for a garage, basement, or open living area: Ecolink PIR Motion Detector.
You want one node reporting motion, temperature, humidity, and lux together, and you like the design: Fibaro Motion Sensor FGMS-001.
You want maximum sensor data and don't mind managing battery life or wiring USB power: Aeotec MultiSensor 6.
Already on Z-Wave and want a 4-in-1 on a budget: Zooz 4-in-1 Sensor ZSE40 if you can find stock, otherwise check current availability of its ZSE11 successor.
Frequently Asked Questions
Q: Do I need the manufacturer's hub to use these sensors with Home Assistant?
No, for nearly every sensor in this guide. Zigbee sensors pair directly to any Zigbee 3.0 coordinator through ZHA or Zigbee2MQTT, and Z-Wave sensors pair directly to a Z-Wave controller through Z-Wave JS. The one partial exception is the Philips Hue Motion Sensor, where the official Home Assistant integration runs through a Hue Bridge for the most reliable experience, though direct Zigbee pairing is also possible.
Q: Why do my lights turn off while I'm still in the room?
That's a limitation of PIR technology, not a bug in a specific sensor. PIR detects movement, not stationary presence — if you stop moving, the sensor has nothing new to report and eventually the automation's timeout expires. If this is a recurring problem in a specific room, an mmWave presence sensor like the Third Reality R1 is built to solve exactly this.
Q: What's the difference between ZHA and Zigbee2MQTT for motion sensors?
Both are local, hub-free ways to run a Zigbee network in Home Assistant. In practice, Zigbee2MQTT tends to expose more configurable device attributes — including detection interval and sensitivity on sensors like the Aqara P1 and SONOFF SNZB-03P — while ZHA has closed much of that gap over time but can still lag on some manufacturer-specific tuning options.
Q: Why won't my Aqara sensor accept a new detection interval setting?
Aqara sensors sleep aggressively to conserve battery, and a configuration write sent to a sleeping device fails silently. Tap the sensor's reset button once to wake it immediately before sending the change, then retry.
Q: Are the lux sensors on these devices actually useful for "turn on lights only when dark" automations?
It depends on the sensor. The Aqara P1 and Fibaro FGMS-001 report usable lux values above the low caps that limit older devices. Several budget sensors, including the SONOFF SNZB-03P and the original Aqara RTCGQ11LM, either don't expose lux in ZHA or only update it on a motion trigger rather than continuously — fine for a rough day/night check, not for precise ambient-light automations.
Q: Should I choose Zigbee or Z-Wave for motion sensors specifically?
Neither protocol is inherently more reliable for motion detection — mesh quality matters more than protocol choice. Zigbee tends to offer more budget options and wider Zigbee2MQTT device support; Z-Wave's sub-GHz frequency avoids 2.4 GHz Wi-Fi congestion and tends to have stronger whole-home range on multi-sensor models like the Fibaro and Aeotec units. If you're already committed to one protocol elsewhere in the house, staying consistent usually beats mixing meshes.
Conclusion
The right motion sensor for Home Assistant isn't the one with the longest range on the box — it's the one whose blind time you can actually tune to match how you move through your home. For fast, responsive lighting, the Aqara Motion Sensor P1 and SONOFF SNZB-03P are the two sensors worth building around, with the Philips Hue Motion Sensor as the reliability upgrade if budget allows. If your problem is presence rather than motion, skip PIR altogether and go with the Third Reality R1. And if you're building out a whole-home Z-Wave mesh, the Fibaro FGMS-001 and Aeotec MultiSensor 6 pack in enough environmental data to justify running fewer, smarter nodes instead of more, dumber ones.
Whichever you choose, remember the two things that actually determine day-to-day satisfaction: confirm the sensor pairs to your own coordinator without a manufacturer hub, and tune the re-trigger interval before you decide the automation "doesn't work." Most disappointing motion sensor experiences are a blind-time problem, not a hardware problem.
