Back to SONOFF Guides
SONOFF

How to Fix Sonoff Zigbee Motion Sensor Delays

SONOFF GuideSmart Sensors
medium difficulty 15-20 minutes 31 views 0 found helpful Where this fix applies: Global Updated
This guide applies to: SONOFF Sonoff Motion Sensor Latency (SNZB motion sensors on Zigbee mesh)
At a glance — most common causes
  • SNZB-03 cooldown between reports (by design)
  • Weak Zigbee mesh adding latency
  • Sensor far from a router/bridge
15-20 minutes13 solutions coveredmedium level

Expert Review & Technical Scope

DeviceSONOFF Sonoff Motion Sensor Latency
Model CoverageSNZB motion sensors on Zigbee mesh
Fix Time15-20 minutes
DifficultyMedium
Required Toolszigbee map, fresh battery
Network / ProtocolZigbee

Problem Description

Your SONOFF SNZB-03 motion sensor detects movement but the event arrives in eWeLink or Home Assistant with a noticeable delay — 1-5 seconds after you walk past it. Or the sensor misses motion events entirely when you walk through the zone shortly after a previous detection. The SNZB-03 has a built-in 60-second cooldown period after each detection, and Zigbee mesh routing adds additional latency.

Why This Happens in Real Homes

SONOFF SNZB-03 motion delays have two flavors. The first is by design: to save battery, the sensor has a cooldown (around a minute) before it reports motion again after clearing, so a second person right after the first may not re-trigger it immediately. The second is network latency from a weak Zigbee mesh.

Know the cooldown is normal for battery Zigbee PIRs, then address genuine lag by strengthening the mesh — add mains-powered Zigbee routers so the sensor's report reaches the bridge quickly — and reduce interference by keeping your WiFi off the Zigbee channel. Move the sensor closer to a router, replace a weak battery, and optimize your automation's response. Aiming the sensor so motion crosses its field also improves how fast it catches movement.

Symptoms

  • Motion sensor slow to trigger
  • Delay before it reports motion
  • Lights turn on late
  • Detection lag
  • Misses quick passes
  • Slow automations from motion
  • Reports motion late
  • Inconsistent timing

Recognize these? Here's what usually causes it.

Common Causes

  • SNZB-03 cooldown between reports (by design)
  • Weak Zigbee mesh adding latency
  • Sensor far from a router/bridge
  • Interference delaying reports
  • Automation/hub processing delay
  • Low battery
  • Firmware issue
  • Placement/angle limiting detection

Most fixes happen in the first 3 steps.

Warning

Do not judge sensor performance from one event; test repeated motion cycles.

Tools & Requirements

zigbee mapfresh battery

Step-by-Step Solution

1

Understand the SNZB-03 cooldown period

The SONOFF SNZB-03 Zigbee motion sensor has a built-in cooldown (re-trigger) period of approximately 60 seconds by default. After detecting motion, it goes blind for 60 seconds before it can detect motion again. This is a hardware/firmware limitation designed to conserve battery — the PIR sensor stays inactive during cooldown. The SNZB-03P (newer model) has a configurable cooldown period that can be reduced to 10 seconds via the eWeLink app. Check your model number on the device body to know which version you have.

2

Check the Zigbee mesh route

Motion events travel from the SNZB-03 to the Zigbee Bridge via the mesh network. If the sensor is far from the bridge and the route goes through multiple Zigbee routers (repeaters): each hop adds 10-50ms of latency. With 3-4 hops, the delay can reach 200ms — noticeable when triggering lights. To reduce hops: add a powered Zigbee device (SONOFF ZBMINI or a Zigbee smart plug) closer to the motion sensor. Powered Zigbee devices act as routers and create shorter paths. Battery sensors like the SNZB-03 are end devices and do not route traffic.

3

Reduce WiFi interference on the Zigbee channel

The SONOFF Zigbee Bridge operates on Zigbee channel 11 (2.405 GHz) by default, which overlaps with WiFi channels 1-3. If your WiFi router is on channel 1: the Zigbee signal competes with WiFi traffic, causing packet retransmissions and delays. Fix: change your WiFi router to channel 6 or 11 (which do not overlap with Zigbee channel 11). Or, if using the Zigbee Bridge Pro or a ZHA/Zigbee2MQTT setup: change the Zigbee channel to 25 or 26 (2.475-2.480 GHz), which sits above all WiFi channels.

4

Check the battery level

Low battery causes delayed or missed motion events on the SNZB-03. The sensor reduces its wake frequency to conserve power as the battery drops. Check the battery level in eWeLink > bridge device > Sub-devices > SNZB-03. Below 20%: replace the CR2450 battery (SNZB-03) or CR2477 (SNZB-03P). Use a brand-name battery (Energizer, Panasonic) — cheap batteries often report full voltage but drop quickly under load, causing intermittent sensor behavior that is hard to diagnose.

5

Adjust the sensitivity setting on the SNZB-03P

The newer SNZB-03P has adjustable sensitivity: Low, Medium, High. In eWeLink > bridge device > Sub-devices > SNZB-03P > Settings > Sensitivity. Low sensitivity requires larger or closer movement to trigger, which can feel like a delay because you need to walk further into the detection zone before it fires. Set sensitivity to High for fastest triggering. The detection range on High is about 6 meters at a 110° angle. On Low, effective range drops to about 3 meters. If you have the original SNZB-03: sensitivity is fixed and cannot be adjusted in software.

Quick Solutions

Understand the motion re-trigger cooldown (about a minute)
Strengthen the Zigbee mesh (add routers)
Move the sensor closer to a router/bridge
Reduce interference (WiFi channel)
Optimize the automation/hub response
Replace the battery
Update firmware
Aim the sensor so motion crosses its field

Still having issues? This is usually the deeper cause below.

If the sensor still misses events after repositioning, check whether a scheduled 'home' or 'away' mode is overriding the sensitivity setting silently.

Pro Tip

Measure latency before and after topology changes to validate improvements.

Real-World Insight

Notification delays over 2 minutes are almost never the device's fault — background app restrictions quietly re-enable themselves after every OS update.

What Usually Goes Wrong
  • SNZB-03 cooldown between reports (by design)
  • Weak Zigbee mesh adding latency
  • Sensor far from a router/bridge
  • Interference delaying reports
  • Automation/hub processing delay
Best Sonoff Motion Sensor Latency Options

Most popular upgrades chosen by Sonoff Motion Sensor Latency owners.

As an Amazon Associate we earn from qualifying purchases.

Official Manufacturer Manual

SONOFF provides official product documentation through their online manual rather than downloadable PDF. Access setup guides, troubleshooting steps, and product specifications for your Sonoff Motion Sensor Latency.

View Sonoff Motion Sensor Latency Online Manual

Source: sonoff.tech

Need More Help? SONOFF Support

Note: The contact information below connects you directly to SONOFF's official customer support team, not Trunetto. They can help with warranty claims, device replacements, and advanced technical issues.