- No automation configured
- Daylight sensor blocking trigger
- Wrong room assigned
Problem Description
Your Philips Hue motion sensor is not controlling the lights the way you expect: either it does not turn them on when you walk in, or it turns them on but never turns them off because it never reports occupancy clear once the room goes still. Which fix applies depends on whether the sensor runs on the Hue Bridge or on a third-party Zigbee hub such as Zigbee2MQTT, ZHA, or deCONZ, because each one handles the no-motion timeout in a completely different place. The sensor uses 2 AAA batteries in the rear compartment and reports motion on the Zigbee occupancy cluster.
Why This Happens in Real Homes
This usually happens when daylight threshold settings are stricter than expected or when Zigbee signal quality drops at the sensor location. The sensor can still report intermittently, but automations fail to fire consistently at the room level.
Start by lowering daylight sensitivity and validating battery and placement before rebuilding automations. In most homes, tuning threshold + signal path fixes missed triggers.
Symptoms
- Motion detected but lights don't turn on
- Sensor shows no motion events
- Lights turn on then immediately off
- Wrong lights activated
- Daylight sensor not working
Recognize these? Here's what usually causes it.
Common Causes
- No automation configured
- Daylight sensor blocking trigger
- Wrong room assigned
- Sensor battery dead
- Too far from Bridge
Most fixes happen in the first 3 steps.
Outdoor Hue motion sensor is weather-resistant but keep it under an overhang to extend lifespan.
Tools & Requirements
These tools will help you complete this fix.
As an Amazon Associate we earn from qualifying purchases.
Step-by-Step Solution
Check battery level and online status
Open the Hue app and go to Settings, then Accessories, and select the sensor to read its battery and connection state. A weak set of AAA batteries often leaves the sensor showing online while it stops sending reliable motion reports, so swap in fresh AAAs in the rear compartment before chasing anything more complex. If the sensor shows offline entirely, it has dropped off the network and needs the mesh and pairing checks below.

Needed for this step
Duracell Coppertop Double AA Batteries with Pow...
This helps complete the fix you are currently reading.
$6.96Check the room, scene, and time-of-day rules
A sensor that looks dead is often just mapped to the wrong behavior. In the Hue app open the automation tied to this sensor and confirm the room or zone, the day and night scenes, and any time window. A common trap is a night-only automation that does nothing during daylight, or a daytime light threshold set so low that the sensor decides the room is already bright enough and skips turning lights on.
Fix placement and sensitivity
Mount the sensor about 4 feet up at chest height, aimed across the room rather than at a doorway, and keep it off direct sunlight, HVAC vents, and reflective surfaces that throw false or missed reads. Hot air moving across the lens trips a PIR sensor erratically. If it misses people, raise the sensitivity in the app; if it triggers on pets or a heat vent, lower it.
Check the Zigbee mesh path
The sensor is battery powered and does not route, so it leans on always-powered Zigbee devices between it and the hub. If the nearest mains-powered bulb or plug is far away or behind thick walls, motion reports arrive late or get dropped. Add a powered Hue device within range of the sensor to give it a strong hop back to the Bridge or coordinator, then retest.
Find out where the off-timer actually lives
If the lights come on but never go off, the cause is almost always the no-motion timeout, and where you set it depends on your setup. On the Hue Bridge the sensor never sends an occupancy-clear at all; the Bridge runs the timer, so open the motion automation in the Hue app and set turn off lights after no motion for your chosen number of minutes. If you have moved the sensor onto a third-party Zigbee hub, the clear is generated by that hub instead, which the next steps cover.
Set the occupancy timeout on your Zigbee hub
The Hue sensor does not stream a steady no-motion signal. It reports occupancy when it sees you, repeats at about 5 and 10 seconds, then goes quiet, so your hub timer is what flips the state to clear. In Zigbee2MQTT open the device settings and set occupancy_timeout to the seconds you want, where any value up to 10 means 10 seconds and anything above 10 is taken as seconds. In ZHA or deCONZ set the PIR occupied-to-unoccupied delay on the occupancy cluster, cluster 0x0406. If that timeout is left at 0, blank, or an extreme value, the state never returns to clear and the lights stay on.
Rebuild occupancy reporting after a re-pair
Removing and re-adding the sensor does not by itself restore the reporting bindings on the occupancy cluster, which is why a re-pair alone often does not bring the occupancy-clear back. In ZHA, open the device and run Reconfigure Device to re-establish reporting on cluster 0x0406; in Zigbee2MQTT use the Reconfigure button on the device page. While you are there, confirm your automation is keyed off the occupancy entity and not the separate motion or on_off entity, since that one can stay in the detected state for about 2 minutes and keep the lights on past the real timeout.
Drive the automation from a no-motion timer
Because the sensor mutes instead of repeating clears, the reliable pattern is a timer rather than waiting for a guaranteed off message. Restart a no motion for X minutes countdown on every motion report and switch the lights off when it expires, so a single missed occupancy-clear cannot strand the lights on. The sensor own no-motion read can lag a few minutes on some hubs, and a hub-side timer gives you exact, predictable control instead.
Quick Solutions
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.
Hue motion sensors (model numbers SML001 through SML004) have a built-in cooldown and will not report fresh motion for several seconds after a detection, so very short test walks back and forth can look like missed triggers when the sensor is simply in its cooldown window. Place the sensor at chest height, about 4 feet, for the most reliable human detection.
This issue almost always looks more complex than it is — the majority of cases trace back to a single setting, a stale credential, or a default that shipped wrong.
- No automation configured
- Daylight sensor blocking trigger
- Wrong room assigned
- Sensor battery dead
- Too far from Bridge
Before you go — try one of these (they fix most cases).
Official Manufacturer Manual
If you need the complete manufacturer documentation for advanced setup, wiring diagrams, or detailed specifications, you can download the official manual below. The manual includes full technical instructions directly from the manufacturer and may help if your issue requires deeper troubleshooting.
Download the Official Philips Hue Motion Sensor ManualSource: philips.com
Need More Help? Philips Hue Support
Note: The contact information below connects you directly to Philips Hue's official customer support team, not Trunetto. They can help with warranty claims, device replacements, and advanced technical issues.
How Does Philips Hue Compare?
Before replacing your Philips Hue device, see how it stacks up against alternatives in our full comparison guides.
Accessories owners commonly pair with Philips Hue Motion Sensor.

Blink Mini - Compact indoor plug-in smart security camera...

Blink Mini - Compact indoor plug-in smart security camera...

Blink Mini - Compact indoor plug-in smart security camera...
As an Amazon Associate we earn from qualifying purchases.
Guide Improvements
- Updated July 2, 2026
Added a fix path for the Hue motion sensor turning lights on but never turning them off, covering the no-motion timeout on the Hue Bridge versus third-party Zigbee hubs (Zigbee2MQTT, ZHA, deCONZ).
What changed:- Added steps for the lights-won't-turn-off case, explaining the sensor reports motion then goes quiet while the hub's timer produces the occupancy-clear
- Documented where to set the no-motion timeout: Hue Bridge automation, Zigbee2MQTT occupancy_timeout, and the ZHA and deCONZ PIR occupied-to-unoccupied delay on cluster 0x0406
- Explained why removing and re-pairing does not restore the occupancy-clear, and added the Reconfigure Device step to rebuild reporting bindings
- Added guidance to key automations off the occupancy entity, not the motion or on_off entity that lingers about 2 minutes
- Recommended driving the automation from a no-motion timer so a single missed occupancy-clear cannot leave the lights on
Source: User Feedback





