Why your Home Assistant motion light turns off on you (and the Zigbee fix that comes first)

Description and use

Motion‑based lighting in Home Assistant frequently turns off while occupants remain present due to the default single mode and a fixed delay. Switching to restart mode, waiting for the sensor to stay off, and properly configuring triggers fixes the issue. Moving the Zigbee coordinator to a USB 2.0 port and selecting an interference‑free channel further stabilises the network.

Problem

Motion lights in Home Assistant often turn off while people are still present, fire at inappropriate times, and rely on sensors that drop from the Zigbee network.

Outcome

Lights now stay on until two minutes after the last motion, eliminating premature turn‑offs. Zigbee network becomes more reliable, reducing sensor dropouts.

Workflow

• 1. Change automation mode to restart. 2. Replace delay with wait_for_trigger on motion sensor off for 2 minutes. 3. Add to: in state triggers and for: where appropriate. 4. Optionally use a timer helper to prevent turning off manually lit lights. 5. Move Zigbee coordinator to a USB 2.0 extension cable. 6. Select a Zigbee channel (15, 20, or 25) before pairing. 7. Add mains-powered routers to create a mesh. 8. Set permit_join to false after pairing.

Evidence

The default, single, means that if the motion sensor fires again while the first run is still sleeping through its delay, the second trigger is dropped.

Source

USB 3.0 ports and the cables plugged into them radiate noise in the 2.4 GHz band, which is exactly where Zigbee lives.

Source