Why Smart Lights Turn Off While You Are Still in the Room

3 days ago

4 min read

Before buying a different sensor, check what the current one reports at the moment the light switches off. If it says the room is empty, investigate detection. If it still says occupied, investigate the automation. That one distinction saves a lot of unnecessary resetting.

For now, disable the affected automatic off rule or use a reliable manual control. Then troubleshoot one room and one rule at a time.

Research checked 24 October 2026. The examples below describe lighting logic; exact menus depend on your system.

Find which part is making the mistake

What you observe	Likely direction to investigate	First reversible check
Sensor changes to empty while you sit still	Detection method, angle, range or sensitivity	Watch its state from your usual seat
Sensor stays occupied but lights turn off	A timer, condition or competing rule	Read the automation history at that time
Light switches off after the same interval every time	Delay counted from the first trigger	Check what resets or cancels the timer
Sensor is unavailable	Power or communication	Check batteries and controller connection
Problem starts after another app is configured	Duplicate automation	Temporarily disable the second app's rule

These are diagnostic clues, not proof of a single cause. Record the time of one failure so you can compare the sensor event and light command.

When the light goes off, an empty sensor state points towards detection checks, while an occupied state points towards the automation rule. An unavailable sensor is unknown, not empty. — A matching timestamp separates a detection problem from a rule that switches off despite continued occupancy.

When the sensor says the room is empty

A motion sensor reports movement, not a guarantee that nobody remains. Someone reading, using a laptop or sitting behind furniture can outlast a short timeout. A longer delay is a reasonable first experiment, especially if automatic switch-off is merely a convenience.

For a presence sensor, check the seated position against its presence range and remove obstructions. Our placement guide provides a repeatable test.

On the MS605, Meross distinguishes the threshold for entering presence from the threshold for maintaining it. Its setup guide explains that an excessively high maintain threshold can cause false absence while you sit still. Adjust using the displayed readings, then retest the empty room too. Making detection easier can also make unwanted signals more noticeable.

Do not treat an unavailable sensor as an empty room. That is an unknown state. For ordinary household lighting, I'd have the off rule stop when occupancy information is missing and leave manual control available.

When the timer ignores you coming back

Consider a rule that says: movement detected, turn light on, wait five minutes, turn light off. If a second movement does not restart that wait, the original countdown can expire while you are still there.

Home Assistant documents this exact distinction: its Restart mode can restart the delay when a new trigger arrives, whereas Single mode ignores a new run while one is active. That fix only works when a new trigger actually occurs. A sensor that stays continuously occupied does not necessarily send a fresh state change for every movement.

A clearer design is to separate the on and off decisions:

Turn on when occupancy is detected and the room needs light.
Turn off only after a continuous period of confirmed absence.
Immediately before switching off, check that the room is still unoccupied and that no manual hold is active.

This is a suggested design, not a universal menu sequence. Use the equivalent supported conditions in your controller. For multiple sensors, “any occupied” should keep the room on; the off decision should require all relevant sensors to report absence. Test a person moving between their areas.

A suggested automatic-off sequence confirms continuous absence, waits the configured delay, rechecks absence and any manual hold, then switches off only if the conditions still pass. — Suggested logic: the off decision follows confirmed absence and a final condition check. Use the equivalent features supported by your controller.

Don't let the light defeat its own rule

An ambient-light threshold is useful when deciding whether to turn the light on. It can become awkward if the illuminated room then exceeds the threshold and a separate rule turns everything off.

Use daylight as an entry condition unless you have deliberately designed and tested ongoing brightness control. Also inspect schedules, bedtime routines and voice-assistant automations. The sensor may be working correctly while a different app issues the off command.

Home Assistant users can inspect automation traces to see which path ran. Its documentation also notes that restarts interrupt running delays and waits. Recheck behavior after a controller restart rather than assuming the previous countdown survived.

Give people a clear manual hold

A reading scene should not need constant movement to survive. A useful design is a named “Keep lights on” control that suspends automatic off until the user cancels it or a clearly stated reset condition occurs. Explain that behavior to the household.

Do not assume every feature called “Do not disturb” does this. Hue describes its setting as preventing motion from overriding an already active scene. That description is not a blanket promise to disable every off action.

Finish with four tests: enter, sit quietly, leave, and return before the delay ends. Then test the manual hold. If the sensor still cannot detect the activity you need, use the motion and presence sensor comparison to choose a suitable replacement with the correct controller requirements.