C-Bus occupancy and PIR sensors: how automatic lighting works

One of the most popular things our team gets asked to add to a C-Bus home is automatic lighting — you walk into the hallway at 2am and the lights ease up to a soft level on their own, then switch themselves off a few minutes after you’ve gone back to bed. That magic comes down to a small, unassuming device: the PIR occupancy sensor. In this article we’ll explain how it actually works, why it never switches the lights itself, and how the settings behind it decide whether the system behaves brilliantly or drives you up the wall.

What a PIR sensor actually does on a C-Bus network

PIR stands for passive infrared. The sensor watches for the heat signature of a person (or pet) moving across its field of view. The important thing to understand is that on C-Bus, a PIR is just another input unit — exactly like a Saturn, Neo or eDLT wall switch. When it detects movement, it doesn’t push power to a light. It simply puts a message onto the pink C-Bus cable that says, in effect, “Group Address 5 to Level 255” (lights on full) or “recall the Hallway Night scene”.

The diagram above shows how the pieces fit together. The sensor and the switches are talkers; they send commands. The light circuits are wired into an output unit — a relay or a dimmer such as an L5504D2U — and that output unit is the only thing that ever connects to the 230 V lighting load. When the dimmer hears the message addressed to its Group Address, it does the actual switching or dimming. This separation of “who asks” from “who switches” is the whole reason C-Bus is so flexible: any sensor can control any light, scene or even multiple rooms, all in software, without re-running a single cable.

The three settings that make or break it

Nine times out of ten when a customer rings us saying “the sensor’s playing up”, the sensor is perfectly fine — it’s a setting that needs a tweak. There are three you’ll hear us talk about.

1. The timeout

This is how long the lights stay on after the last movement was detected. Walk into the garage, the lights come on, and the timeout starts counting. Every time you move, the timer resets. Once you’ve been still (or have left) for the full timeout, the sensor sends the “off” message. Too short and the lights drop out while you’re standing at the workbench; too long and they burn away in an empty room. We usually start a hallway at a minute or two and a bathroom a bit longer, then fine-tune to how the family actually lives.

2. The light-level (lux) threshold

Most C-Bus PIRs include a built-in lux sensor that measures how bright the room already is. The threshold tells the sensor: only trigger the lights if it’s darker than this. That stops the hallway lights flicking on every time someone walks past in broad daylight, which wastes energy and looks silly. Set it well and the lights only assist when there’s genuinely not enough natural light.

3. The level or scene it sends

A PIR can send a simple “on at full brightness”, or it can recall a whole scene. This is where the nice touches come in — a low 15% “night” level for the hallway after midnight, or a brighter level during the evening. If your lights come on at the wrong brightness, it’s almost always this setting (or which scene is being recalled), not a hardware fault.

Where automatic lighting earns its keep

We fit occupancy sensors in plenty of Melbourne homes, and a few spots come up again and again:

• Hallways and stairwells — hands-free light when you’re carrying washing or half asleep, and a safe, dim night level so nobody’s hunting for a switch in the dark.
• Bathrooms and walk-in robes — lights on as you enter, off when you leave, no fuss.
• Garages and laundries — arms full of shopping or tools and the light’s already on for you.
• Outdoor and security/away lighting — paired with the C-Bus timeclock and an “away” mode, sensors can make the house look lived-in and light a path to the front door.

These last two — schedules and away modes — start crossing into proper automation. If that’s where you’re headed, our C-Bus automation guides go deeper, and the logic often lives in a Wiser Home Controller.

Coverage and mounting: why placement matters

A PIR can only react to what it can see. Each sensor has a coverage pattern — a fan of detection zones spreading out from the lens — and a recommended mounting height. Get either wrong and you’ll get blind spots. A few things we always consider on site:

• Mounting height. Ceiling sensors are designed for a particular height range. Mount too high and the coverage spreads thin and misses small movements; too low and the pattern is tight and short.
• Line of sight. PIRs detect movement across their zones better than straight towards them. Walking directly at a sensor can take a moment to register — we aim them so your normal path crosses the beams.
• Obstructions. A new wardrobe, a tall pot plant or a half-open door can block a chunk of the pattern. If a sensor that worked fine for two years suddenly misses you in one corner, check what’s moved into the room.
• Heat and draughts. Sensors can be fooled by heaters, fan vents or strong sunlight on the lens, so we keep them clear of those where we can.

Quick troubleshooting before you call us

If the automatic lighting isn’t behaving, run through this short sequence first. It’ll tell you a lot before we even arrive.

1. Lights won’t come on at all? Try it after dark. If they work at night but not by day, that’s the lux threshold doing its job — it thinks there’s already enough light. If they won’t come on even in the dark, check the manual switch still controls that circuit; if the switch works but the PIR doesn’t, it’s a sensor or programming issue.
2. Lights stay on too long? That’s the timeout set longer than you’d like — a five-minute tweak in the programming, not a fault.
3. Lights drop out while you’re still in the room? The timeout is too short for how you use the space, or you’re sitting in a coverage blind spot. Wave an arm — if they come back, it’s coverage.
4. Wrong brightness? The sensor is recalling the wrong level or scene. Common after a scene gets re-saved at a different level.
5. Sensor triggering at random? Look for a new heat source, a vent or sunlight hitting the lens, or a pet wandering through.

For a deeper diagnostic walk-through, see our C-Bus troubleshooting section. If you’d like to understand the difference between sensors and standard switches first, our C-Bus switches articles are a good companion read, and Clipsal’s own C-Bus product information covers the broader range.

The short version

A C-Bus PIR is a smart messenger, not a switch. It senses movement, checks whether it’s dark enough, and tells an output unit to bring your lights on at the right level — then tells them to switch off again once the room’s been empty long enough. Almost every “problem” is a timeout, lux or scene setting we can adjust, not a dead sensor.

If your automatic lighting isn’t quite nailing it — or you’d love to add it to a hallway, bathroom or garage — give us a shout. We tune these things to how you actually live, not a generic default. Reach out any time via our contact page and the DUKE team will sort you out. — Adam & the team.