You shouldn’t have to wave at your lights.

You’re halfway through a chapter when the room goes dark.

You haven’t left. You haven’t fallen asleep. You’re sitting in the same chair, holding the same book.

So you wave an arm.

The lights come back on.

A few minutes later, you do it again.

Automatic lighting should make a room easier to use. When it keeps asking you to prove you’re there, something about the setup needs to change.

The fix might be a setting. It might be where the sensor is mounted. In some rooms, a different kind of sensor could help.

Many motion sensors use passive infrared sensing, usually shortened to PIR. They detect changes in infrared energy as someone moves through their view.

That works well when you walk into a hallway or cross a utility room. Sitting quietly gives the sensor less to work with.

The lighting rule usually includes a waiting period: if no movement is detected for a certain amount of time, turn off the lights. When the sensor misses your smaller movements, that timer can run out while you’re still there.

Some PIR sensors are designed to pick up small movements, such as turning a page. Coverage, sensitivity, and placement still matter. Lutron, for example, distinguishes between major and minor movement and provides settings for sensitivity and the shutoff delay. Lutron sensor guidance

Before buying anything, I’d check whether the sensor can see the chair where the problem happens. Then I’d look at the delay.

A timer that suits a hallway may be much too short for a reading corner.

Radar-based presence sensors offer another approach.

Often called mmWave sensors, they use radio waves to detect much smaller movements. That can help a system recognize that someone remains at a desk or on a sofa.

They still have to interpret a signal. “Presence” on the box does not mean the device knows with certainty whether a room is occupied.

Some models can also divide a room into zones. Aqara’s FP2, for example, documents small-movement detection and configurable areas within a room, without using a camera. That gives us a possible way to treat the desk, sofa, and doorway separately. Aqara FP2 capabilities

The useful result could be ordinary: you settle into your chair, and the reading light stays on until you leave.

Imagine an open living room with a desk in one corner and a passage to the kitchen.

Someone walking through might need a little light along the way. Someone working at the desk might want a task lamp. Someone watching a film might want the overhead lights to stay off.

A single “room occupied” rule has trouble expressing those differences.

With suitable sensing and compatible lighting, I could design separate responses:

• Movement through the passage brings on a low light when the room is dark.
• Presence at the desk keeps the task light on.
• A movie setting keeps the overhead lights off while people move around.

We would decide those behaviors with the people who use the room. Sitting on the sofa does not always mean you want a lamp switched on.

That is also why detecting someone and deciding what to do should be separate parts of the setup.

A presence sensor needs a view of the space it is meant to cover. Furniture, mounting position, and the room’s shape all affect where it can be useful.

It also needs help distinguishing relevant movement from the surroundings. Aqara’s setup guidance identifies fans, moving curtains, and plants as possible interference sources. Its configuration includes ways to mark those areas. FP2 installation manual

Pets deserve their own test. A dog walking through the room may be a reason to turn on a low light—or exactly the event you want the system to ignore. I wouldn’t promise that a sensor will reliably separate people from pets without testing the chosen setup.

I’d test the room as it is normally used: someone sitting quietly, two people entering and one leaving, the fan running, and movement through a nearby doorway.

That tells us more than walking past the sensor once and seeing a light turn on.

Even reliable sensing can become annoying if the rule ignores a person’s choice.

If you turn a lamp off to watch television, the next small movement should not immediately switch it back on.

For a Luvvo design, I’d agree on how manual changes affect the automation. Perhaps switching the light off pauses automatic control until the room has been empty for a while. Perhaps a physical button selects a reading or movie setting.

The return to normal operation should be clear, too. Nobody should have to remember which hidden setting stopped the lights from working yesterday.

A missing sensor reading also needs its own response. I wouldn’t treat “sensor unavailable” as proof that the room is empty.

There’s no reason to replace every motion sensor in the house.

A simple sensor may do everything you need in a passage or utility room. A longer delay or better placement may solve the reading-chair problem. More detailed presence sensing earns its place where those simpler changes fall short.

I’d start with one room and one clear complaint:

“The light turns off while I’m still sitting here.”

Then check the existing settings, look at what the sensor can actually detect, and test any changes during ordinary use.

At Luvvo, that is the work I’d want to do before recommending more equipment. The goal is a light that behaves the way you expect while you get on with your evening.

Have a room whose lights keep getting it wrong? Tell me what happens.