Sonoff SNZB-03P Zigbee Motion Sensor: Honest Review 2026

The Homelab Bench is reader-supported. As an Amazon Associate we earn from qualifying purchases; this article contains affiliate links.

Verdict

The Sonoff SNZB-03P is the easiest budget Zigbee PIR sensor to recommend for Home Assistant in 2026. It pairs instantly via Zigbee2MQTT or ZHA, delivers a genuinely fast 5-second clear timeout, and runs for around three years on a single CR2477 cell — all at a budget price. If you need tighter configuration control or a wider field of view, step up to the Aqara P1; if you want the most bulletproof hardware and don’t mind paying a premium, the Philips Hue sensor is still the benchmark.

Quick-Pick Table

Sonoff SNZB-03P — The Main Event

The SNZB-03P is Sonoff’s second-generation Zigbee 3.0 PIR sensor, built to replace the original SNZB-03, which had a fixed one-minute clear timeout that made it frustrating for lighting automations. It is a battery-powered passive infrared sensor in a compact bullet-shaped housing that comes with a magnetic swivel base — mount it with the included 3M pad or a couple of screws. Dimensions are 44 × 44 × 65 mm at 54 g. Indoor use only; there is no water resistance rating.

Key Specs

• Protocol: Zigbee 3.0 (EFR32MG22 radio)
• Detection range: 6 m (20 ft), 110° field of view
• Clear timeout: Adjustable 5–60 seconds (was fixed at ~60 s on the SNZB-03)
• Battery: CR2477 (3 V), rated for up to 3 years
• Operating temperature: −10 °C to 60 °C
• Extra sensor: Ambient light (dim/bright flag)
• HA integrations: Zigbee2MQTT and ZHA, fully local

Strengths

Instant drop-in for Home Assistant. Because it is a standard Zigbee 3.0 end device running on the EFR32MG22 chip, it is recognised automatically by both Zigbee2MQTT and ZHA the moment you put it into pairing mode — hold the button for five seconds until the LED blinks slowly, then hit Add Device in your Zigbee integration. No cloud account, no eWeLink app, no custom quirks file needed. All state updates stay on your local network even if your internet drops entirely.

Genuinely fast timeout. The biggest complaint about the old SNZB-03 was the fixed ~60-second wait before the occupancy entity reset to clear. The SNZB-03P lets you set that window anywhere between 5 and 60 seconds, which means lights in a hallway or loo can turn off in five seconds flat after you leave rather than keeping them burning for a full minute. Real-world testing confirms the timeout fires reliably at the configured value.

Three-year battery life on a common cell. The switch to CR2477 roughly doubles the battery reservoir compared to the old CR2450, and Sonoff’s rated three-year life is credible at moderate trigger frequency. The CR2477 is a standard coin cell, widely available and inexpensive.

Drawbacks

The lux sensor is a binary flag, not a live reading. In Zigbee2MQTT the ambient light entity exposes only “dim” or “bright” — not a numeric lux value — and it only updates when motion fires, not continuously. That creates a feedback loop in naive automations: the light turning on gets read back as “bright” on the next trigger, which can block your “only turn on when dark” condition from firing correctly. The fix is to use the illuminance flag as a gate condition evaluated at the moment of motion, not as a live ambient tracker — but it’s a papercut you shouldn’t have to work around. This behaviour is well documented in the Zigbee2MQTT device page and in community reports.

110° field of view is modest. Competing sensors in the same price bracket now offer 150–170°. For a long corridor or a large open room, 110° is often enough — but in a wide living room you may need two units to get full coverage without a dead zone near the edges.

ZHA entity duplication quirk. Some users have reported that ZHA creates two separate entities — Motion and Occupancy — for the same sensor when first pairing. Using the Occupancy entity is the right one for automation triggers; the Motion entity can be safely ignored or disabled. It does not affect function but it can confuse a fresh setup.

Check price: Amazon UK | Amazon US | Amazon IE

Aqara Motion Sensor P1 — Best Mid-Range Upgrade

The Aqara P1 (model MS-S02) is a compact Zigbee 3.0 PIR sensor that sits a step above the SNZB-03P on almost every configurable axis. At 33 × 33 × 41.6 mm and 33 g it is noticeably smaller and lighter, runs on two CR2450 cells with an advertised five-year battery life, and ships with a 360° swivel stand. No Aqara hub or cloud account is needed when you use Zigbee2MQTT or ZHA — Zigbee2MQTT exposes sensitivity level (low/medium/high), a configurable detection interval, and a trigger LED switch as editable entities directly in Home Assistant.

If you are building automations that need to know whether a space is actually empty before switching off lights, the P1’s adjustable sensitivity modes let you tune detection distance rather than relying on placement alone. Its 170° field of view up to 2 m and 150° up to 7 m makes it substantially better than the SNZB-03P for wide rooms and angled ceiling mounts. For readers who already run a portfolio of Zigbee motion sensors, the P1 is a natural step up whenever you need granular control rather than just a trigger.

Strengths

• Five-year rated battery life on 2× CR2450 — industry-leading for a PIR sensor at this size.
• Adjustable sensitivity (low/medium/high distance modes) and configurable detection interval exposed natively in Zigbee2MQTT — no hacks needed.
• 170°/150° dual-zone FOV gives much better room coverage than 110° competitors.
• Fully local in Zigbee2MQTT or ZHA — no Aqara hub or account required.

Drawbacks

• Aqara’s official documentation states Zigbee2MQTT and third-party USB dongles are not officially supported; full functionality may vary, and OTA firmware updates are not guaranteed outside the Aqara ecosystem. Community support is strong, but it’s worth knowing Aqara’s stance.
• The five-year battery figure assumes the motion LED is disabled and the detection timeout is set to at least 30 seconds; heavy-traffic locations or short timeouts will shorten real-world life noticeably.

Check price: Amazon UK | Amazon US | Amazon IE

Philips Hue Indoor Motion Sensor — Premium Reliability Benchmark

The Philips Hue indoor motion sensor (SML004 and its successors) has been the community’s go-to recommendation when people are tired of chasing flaky cheap sensors. It is a Zigbee sensor that adds motion, ambient light (lux), and temperature readings in a single unit, with a roughly 100° field of view and a 7 m / 23 ft range. It runs on 2× AAA batteries, rated for around two years. It pairs with Zigbee2MQTT and ZHA without needing a Hue Bridge, though the Bridge is recommended for the most reliable mesh behaviour. The light and temperature entities both expose in Home Assistant, which makes it unusually useful for multi-trigger automations — for example, only activating AC when motion is detected and temperature is above a threshold. For context on how PIR sensors stack up against radar-based alternatives, see our deep dive on mmWave vs PIR motion sensors.

Strengths

• Motion, lux, and temperature all in one unit — the most sensor data per device of any PIR in this roundup.
• Flexible mounting: screw, magnetic back, or freestanding on a shelf.
• Regarded by long-term HA community members as the most consistently reliable Zigbee PIR radio in sustained real-world use.

Drawbacks

• Some users running the sensor directly via ZHA (without the Hue Bridge) have experienced sensors going unavailable after a day or two, requiring re-pairing. This is a known issue in the HA community, particularly on ZHA with newer SML003/SML004 hardware revisions. Zigbee2MQTT tends to be more stable for direct pairing.
• Premium pricing puts it in a very different bracket from the SNZB-03P. If you are deploying sensors across six or eight rooms, the cost adds up fast.

Check price: Amazon UK | Amazon US | Amazon IE

SNZB-03P vs SNZB-03: Do You Need to Upgrade?

If you already own the original SNZB-03, the single most compelling reason to upgrade is the timeout. The old model locked you into roughly 60 seconds of occupancy-on after the last detected movement — annoying for lights, actively bad for energy monitoring automations. The SNZB-03P brings that down to as little as 5 seconds. Add the larger battery capacity (CR2477 vs CR2450), the bonus ambient light flag, and a more flexible ball-mount design, and the P model is simply the better sensor in every measurable way. Keep your old SNZB-03 units in lower-traffic spots like utility rooms or sheds where the minute-long timeout is less noticeable.

Home Assistant Setup: What to Expect

With Zigbee2MQTT the SNZB-03P exposes four entities out of the box: occupancy (binary sensor), illuminance (dim/bright enum), motion timeout (number, 5–60 s, writable), and battery percentage. Use the occupancy entity — not the motion entity — as your automation trigger; the motion entity is a secondary report that some setups expose separately. The illuminance flag is only updated when motion fires, so treat it as a condition to check at trigger time rather than a live sensor state. Automations that gate on “illuminance == dim” at the moment of the occupancy trigger work cleanly without feedback loops.

With ZHA the experience is similar, though some users see duplicate Motion and Occupancy entities on first pair. Disable the Motion entity and work with Occupancy. The timeout is configurable from the ZHA device page. No extra scripts, no HACS add-ons, no cloud tokens — just a Zigbee coordinator (SONOFF ZBDongle-E or ZBDongle-P work well, as will any EFR32-based or CC2652-based stick). If you are still deciding on coordinator hardware, our best budget Zigbee hubs guide covers the options.

Who Should Buy the SNZB-03P?

• Deploying five or more motion sensors on a budget — the per-unit cost is low enough that you can cover every room without wincing at the total.
• Hallways, stairs, and bathrooms — small spaces where the 110° FOV is rarely a limitation and the 5-second timeout genuinely shines.
• New to Zigbee PIR sensors — it pairs cleanly, the entities are obvious, and the community support for this specific model in Zigbee2MQTT is solid.

Who Should Look Elsewhere?

• Large open-plan rooms — get the Aqara P1’s 170° FOV instead, or consider a dedicated mmWave presence sensor for rooms where someone might sit still for long periods.
• Outdoors — the SNZB-03P has no water-resistance rating. See our best Zigbee outdoor motion sensors guide for options designed for the elements.
• Maximum reliability at any cost — the Philips Hue sensor has the longer track record for staying on the mesh without intervention.

How We Chose

Products were evaluated against four criteria: confirmed local control via Zigbee2MQTT or ZHA with no cloud dependency, Zigbee 3.0 compliance, verified availability on major marketplaces, and real-world feedback from Home Assistant community forums and independent reviewer testing. Specs were cross-referenced against official Sonoff, Aqara, and Philips documentation. No manufacturer provided review samples or payment for inclusion.

FAQ

Does the Sonoff SNZB-03P work with Home Assistant without the eWeLink cloud?

Yes, completely. The SNZB-03P is a standard Zigbee 3.0 end device and is recognised immediately by both Zigbee2MQTT and ZHA using any compatible coordinator. Your internet connection can be down entirely and the sensor keeps firing automations locally as long as your Zigbee hub is powered on.

What is the difference between the SNZB-03 and SNZB-03P?

Three meaningful differences: the SNZB-03P’s clear timeout is configurable between 5 and 60 seconds (the old model was fixed at roughly 60 seconds); the battery has increased in capacity from CR2450 to CR2477; and the P model adds a basic ambient light flag. The physical design also moved to a ball-on-magnetic-base form factor that is easier to angle precisely.

Can I use the SNZB-03P as a presence sensor for someone sitting still?

No. Like all PIR sensors it detects movement caused by body heat crossing the sensor’s detection zones. A perfectly still person will not trigger it after the initial detection. If you need true presence detection — someone asleep on a sofa, someone working at a desk — you need a dedicated mmWave radar sensor. Our mmWave presence sensor guide covers the best options for Home Assistant.