Motion-Triggered Light Hold Time Calculator

Motion-Triggered Light Hold Time Calculator

Estimate a motion light timeout from room activity, expected movement gaps, sensor miss rate, retrigger margin, lighting load, and daily visits.

🎯Motion lighting presets
💡Hold time inputs
Different sensor styles have different minor-motion strength and post-timeout dead time.
Count separate sessions where the light turns on and later times out.
Use a larger value for reading, sitting, showering, folding laundry, or blocked line-of-sight.
Most occupancy sensors count this delay from the last detected motion.
The calculator estimates timing behavior for lighting automation. Confirm final timeout, sensitivity, vacancy mode, and load ratings against the exact sensor and controller used.
Suggested hold setting
--
nearest practical timeout
False-off risk
--
per quiet-motion interval
Daily light runtime
--
occupied plus hold time
Monthly lighting energy
--
based on entered watts

Detailed timing breakdown

Motion timing spec grid
1-30Common wall timeout minutes
3-300DIY PIR hold seconds
3 secTypical PIR reset gap
10-30Common control minutes
W x hLighting energy formula
5%Comfort risk target
2xStill-task multiplier
15 secStarter retrigger buffer
📊Hold setting reference table
Hold band Best space pattern Motion gap handled Main tradeoff
15 to 60 secondsCabinet lights, stair LEDs, test modeContinuous walking or hand movementVery efficient but intolerant of pauses
1 to 3 minutesHallways, pantries, entry closetsShort pass-through gapsGood for quick visits, poor for still tasks
5 to 8 minutesLaundry, utility, garage accessModerate task gapsBalanced for repeated short activity
10 to 15 minutesBathrooms, kitchens, workbench zonesQuiet periods and partial sensor blockageLower false-offs with more after-vacancy runtime
20 to 30 minutesOffices, reading rooms, stalls, large roomsLong stillness between detectable motionsMost comfortable, highest wasted hold time
🔍Sensor comparison grid
Sensor type
Typical hold
Minor motion
Retrigger note
Energy bias
Best use
Wall-switch PIR
1-30 min
Medium
After last motion
Balanced
Rooms with clear line-of-sight
Ceiling PIR
5-30 min
Medium
Wide field helps
Balanced
Garages, laundry, utility spaces
Dual-tech
5-20 min
High
PIR plus acoustic motion
Comfort
Offices and quiet bathrooms
mmWave presence
1-10 min
Very high
Presence refreshes often
Efficient
Still occupancy and desk areas
DIY PIR module
3-300 sec
Low
May have reset dead time
Efficient
LED strips and low-voltage projects
🚪Room activity reference table
Space Entries per day Stay length Quiet-motion gap
Hallway pass-through20 to 600.2 to 1 min0.1 to 0.4 min
Pantry or closet4 to 200.5 to 4 min0.3 to 1 min
Bathroom5 to 143 to 15 min2 to 6 min
Laundry or utility2 to 102 to 12 min1 to 4 min
Home office1 to 630 to 180 min5 to 20 min
Garage task area2 to 123 to 45 min1 to 8 min
Runtime and energy reference table
Light load 1 hour per day 3 hours per day 6 hours per day
12 W LED strip0.36 kWh/month1.08 kWh/month2.16 kWh/month
36 W fixture group1.08 kWh/month3.24 kWh/month6.48 kWh/month
60 W room lighting1.80 kWh/month5.40 kWh/month10.80 kWh/month
120 W garage lights3.60 kWh/month10.80 kWh/month21.60 kWh/month
Actionable hold-time tips
Tune to the quietest real task. Walk through the space normally, then test the longest still activity. If the light drops while occupied, increase hold time or reduce missed detections before chasing energy savings.
Protect the retrigger window. Add a small buffer for sensor reset time, wireless latency, hub automation delay, and fade-off time so a new motion event can refresh the timer cleanly.

Have you ever washed your hands and had the light flicker out as soon as you stood still? Yes. You probably know the frustration. But it’s not a sensor malfunction, it’s a hold time setting mismatched for human activity.

Motion sensors aren’t magical switches that “just know” when to turn on/off. No. They’re timing mechanisms based off their guesses regarding how long they expect you to be moving around within the same space.

Why Motion Sensors Turn Off Too Soon

Achieving appropriate timing (aka optimizing between energy waste vs. The whole purpose of a hold time calculator for motion-triggered lights is to balance energy waste and comfort, which is why one can actualy be useful. To that end, I think fundamental issue with motion sensor hold times is that each room require a different level of patience for the light.

For example, a hallway is used as a transit area, where you’d expect someone moving through rapidly in-and-out of the room. Ideally once you’re gone, the light dies away quickly (so you’re not wasting electricity running down the hall). An office/bathroom, on the other hand, has much more static use-cases (standing at the mirror, reading, doing laundry), where large gaps can be expected between moments when something move into range. Having your sensor timeout every 90 seconds is going to fight you all day. Being able to describe behavior of the room helps you understand exactly what’s needed, rather than shooting in the dark.

People find the idea of retrigger margin confusing. When sensors trip/switch, there’s a little bit of dead time until sensor resets. In some cases, it’s only seconds long (but if you have a narrow hold period), then that delay is costing you. Move an inch; miss the window; get cut off. Include a small buffer into your math and it compensate for hardware limitations. And a few additional seconds of grace time won’t cost a ton of money (in terms of energy usage) but will save you from being cut-off and frustrated.

And then there’s another wrinkle: What about when the sensors see that you’re being still? That’s where passive infrared units gets tripped up; a person sitting quietly at your desk might appear just as if she left the room completely. Millimeter-wave or dual-technology sensors does a better job detecting subtle changes in a person’s breath or posture. But even they have limits in how often they update what they “see.” To account for the imperfection, the calculator include an allowance for missed events. In other words, it recognizes that no sensor is perfect and it will help you create a timeout window that accounts for its occasional blind spots.

The typical argument for putting in occupancy sensors are energy savings, but bad timing will defeat this purpose. You’ll want to set the hold time long enough so the sensor doesn’t turn off while you’re still in the room (false-off), but not so high than you waste power by keeping the light on for 20 minutes after everyone has vacated. That is just wasting power for the sake of convenience. Too low of a hold time results in fast cycling, which annoys people and burns up bulbs. The right setting lie somewhere in between, and we need to look at how people use the space to find it.

How many times per day does someone go in? How long does each trip last? These factors drive the runtime estimate; the raw wattage don’t matter quite as much. To make this easy, they include some reference data next to the calculator so you know what numbers looks like in normal use cases. For example, compare how an office with sustained stillness is different than a garage with bursty activity.

It’s enough to prevent over-engineering. You do not need to fine-tune all settings to the last decimal point. Usually rough approximations according to typical user behavior will work out just fine. Automation should be as invisible as possible, and still feel practical. Not exact control you should of constantly tweak.

The room becomes a conversation between you and the machine. You move, it responds, and then it waits for you to leave. When the wait time aligns with your rhythm, you forget there’s a sensor there. That’s the sweet spot.

It takes a little thought up front adjusting these variables, but the payoff is lighting that works with your habits, not against them. You won’t have to stumble around in the dark while trying to brush your teeth. It is just light that knows when to stay and when to go.

Motion-Triggered Light Hold Time Calculator

Leave a Comment