How to set up motion-triggered lighting that doesn’t annoy you

Motion-triggered lighting is one of those automations that’s brilliant when it’s done properly and absolutely maddening when it isn’t. Nine times out of ten when a customer rings us frustrated, it’s the same story: the pantry light won’t stay on while they’re standing still reading a label, or the hallway lights blaze on at 2am full brightness and wake the whole house. The good news is that Control4 gives you plenty of control to get this right — it’s just a matter of setting it up with a bit of thought.

Here’s how we approach motion lighting in real Melbourne homes so it feels helpful rather than annoying.

Occupancy sensors vs motion sensors — know the difference

This is where a lot of bad automation starts. People use the words interchangeably, but they behave very differently.

• Motion sensors trigger when they detect movement and then go quiet. If you stop moving — sitting still at a desk, standing at the bench reading a recipe — the sensor stops reporting and your timeout starts counting down. Great for a quick walk-through space.
• Occupancy sensors are smarter. They keep “holding” the room as occupied as long as there’s any presence, even subtle movement, and only release when the space is genuinely empty. Far better for rooms where you linger.

Most modern sensors can do both — it’s about how you programme the logic. The rule of thumb we use: walk-through spaces (hallways, robes, garages, laundries) suit motion logic with a short timeout. Spaces you occupy (studies, bathrooms, kids’ rooms) suit occupancy logic with a longer hold.

Timeouts: the single biggest cause of annoyance

The timeout is how long the lights stay on after the last detected movement. Set it too short and you’re plunged into darkness mid-task. Set it too long and lights burn for ages in empty rooms, which defeats half the point.

Here’s a starting point we’ve landed on after programming hundreds of these:

• Hallway / passage: 1–2 minutes. You’re passing through, you don’t need it lingering.
• Walk-in robe: 3–5 minutes. Enough to get dressed without doing star jumps to keep the light on.
• Bathroom: 8–12 minutes. Showers and grooming mean long periods of low movement.
• Garage: 5–10 minutes. You’re often head-down under the bonnet or sorting boxes.
• Laundry / pantry: 3–5 minutes.

The trick is that the timer should reset every time motion is re-detected. With occupancy logic, you don’t even need a generous timeout because the sensor keeps the room “held” while you’re in it — the timeout only matters once you’ve actually left.

Only-at-night conditions

You almost never want motion lighting firing during the day, especially in rooms with plenty of natural light. The cleanest way to handle this is to wrap your motion automation in a condition so it only runs at night.

Control4 makes this easy because it tracks sunrise and sunset for your exact location. We typically set lights to activate on motion only between sunset and sunrise — sometimes with a buffer, like 30 minutes before sunset, so it kicks in as the light fades on a grey Melbourne afternoon rather than waiting for the clock.

This one change alone makes motion lighting feel far less intrusive. Your hallway doesn’t light up every time you walk past at midday, but it’s there the moment you need it after dark.

Lux / daylight lockout — the smarter version

Sunrise and sunset times are a good baseline, but they don’t know it’s a dark, overcast day or that a particular room is gloomy even at noon. That’s where a lux (light level) lockout comes in.

If your sensor has a built-in light-level reading — many do — we can add a condition that says “only turn the lights on if the ambient light is below X lux.” So:

• Bright, sunny afternoon and the room’s already well lit? Motion is ignored. No light.
• Dim, stormy day or after dusk? Motion triggers the light as expected.

This is the most natural-feeling setup of the lot, because it responds to how dark the room actually is rather than what time the clock says. It’s especially good for north-facing rooms that stay bright into the evening, or internal hallways with no windows that are dim all day.

Room by room: where motion lighting really shines

Hallways and passages

Short timeout, low brightness after dark. We love setting hallways to come on at a gentle 20–30% in the small hours so a midnight trip to the bathroom doesn’t blind anyone. During the early evening they can come up brighter. This kind of time-aware dimming is one of the nicest touches and it’s pure programming.

Walk-in robes

Occupancy logic with a 3–5 minute hold, only when it’s dark enough to need it. Nobody wants the robe light dying while they’re deciding between two shirts. If the robe has a door sensor, we can even pair it so the light comes on the instant the door opens.

Garages

Garages are great candidates because your hands are usually full. A 5–10 minute timeout, triggered by motion at the door and inside, means you’re never fumbling for a switch with a box in your arms. We often link garage lighting to the roller door too, so it lights up automatically as you pull in.

How to set it up in Control4

If you’ve got Composer HE access on your system (OS 3.4 or later), here’s the general shape of what’s involved. If not, this is exactly the sort of thing our team sets up remotely or on a service visit.

1. Identify your sensor type. Check whether your sensor reports motion only, or full occupancy, and whether it provides a lux reading. This determines your logic.
2. Create the “on” event. Programme the lighting load or scene to activate when the sensor detects motion/occupancy.
3. Add your conditions. Wrap the action in conditions: only run between sunset and sunrise, and/or only if the lux reading is below your chosen threshold.
4. Set time-aware brightness. Use separate conditions so the light comes on dim (say 25%) in the late-night hours and brighter in the evening.
5. Programme the timeout. Set the room’s “off” delay to suit how it’s used, and make sure motion re-triggering resets the timer.
6. Test it for a few days. Live with it. Note any moment it annoys you, then nudge the timeout or lux threshold. Good motion lighting is tuned, not set-and-forget on day one.

For the full picture on building these kinds of rules, see our automation guides, and if you’re pairing motion with dimming and scenes, our lighting articles are worth a read. Control4 also publishes good background on how lighting and sensor agents work over at control4.com.

When it needs our programming

A simple “motion on, timeout off” can sometimes be set up from a touchscreen or the app. But the moment you want layered conditions — sunset windows, lux lockouts, different brightness by time of day, occupancy holds — you’re into Composer territory, and that’s where we come in.

And a quick but important note: any new fixed lighting circuits, switch changes or anything touching the switchboard is licensed-electrician work under AS/NZS 3000 here in Australia. Our team handles all of that side properly and safely. You can read more about why on our electrical standards page. Adding sensors and reprogramming logic on an existing, correctly wired system is the part we can often do without pulling anything apart.

Get the timeouts right, lock it to night or low light, and use occupancy logic where people actually linger — do those three things and motion lighting goes from a daily irritation to something you genuinely forget is even there. That’s the goal: lights that just quietly do the right thing.

If yours is misbehaving and you’d rather we just sorted it, give us a yell. We’ve tuned plenty of these and we’re happy to dial yours in so it stops annoying you for good. Cheers — Adam and the DUKE team.