A client asks for one button by the door that turns off every light, lowers the shades and stops the music. A smart switch cannot do that on its own, and a companion switch certainly cannot. So what is a scene controller, and where does it fit in a hub-based system? This guide explains what the device does, how it differs from the switches beside it, and what to check before you put one on the wall.
What is a scene controller?
A scene controller is a wall keypad or remote with several buttons, each of which triggers a scene: a saved set of states for many devices, such as lights, shades and audio. The buttons send commands, and a hub or controller carries them out. Unlike a smart switch, it may switch no load of its own.
What is a scene controller, in plain terms
A scene is a snapshot: kitchen lights at half, dining lights low, the shades down, a thermostat setback. A scene controller is the button that recalls it. Press “Dinner” and the hub sends the right command to every device in that scene, whatever circuit or room it is on.
Most scene controllers are one of three forms:
- Wired keypad: sits in a wall box like a switch, powered from the circuit, with a row of buttons. Some also switch or dim a local load.
- Battery wall panel: mounts flat on the wall or in a decorator plate with no wiring, so it can go where no box exists.
- Handheld remote: the same idea in a tabletop or portable form.
The buttons are inputs, not power switches. The hub decides what each does, so it can change without touching a wire.
Scene controller vs companion switch vs smart switch
These three often share a gang box, which is why they get confused. The difference is what the button talks to.
| Device | What a press does | Load it switches | Needs a hub |
|---|---|---|---|
| Smart switch or dimmer | Switches or dims its own circuit | Yes, one load | No for local use; yes for scenes and apps |
| Companion or auxiliary switch | Tells the paired smart switch to act | No; mirrors one load elsewhere | No |
| Scene controller | Sends a button event that triggers a scene | Often none; some keypads add one | Usually yes |
A companion switch is a remote for one smart switch, as set out in our guide to wiring a 3-way smart switch. Whether the local load needs a switch or a dimmer is covered in smart dimmer vs smart switch. A scene controller sits a level above both: it does not care which circuit a light is on, because it talks to the hub, not the wiring.
Where a scene controller sits in a hub-based system
In a typical system the hub, panel or automation controller holds the scenes. The scene controller is one of its inputs, alongside sensors, schedules and the app. The chain looks like this:
- The user presses a button.
- The keypad reports which button and how it was pressed.
- The hub looks up what that event is programmed to do.
- The hub sends commands to each device in the scene.
This is why a scene can include things on other protocols or in other rooms: shades, lighting, a thermostat, even audio, as long as the hub can control them. Shade scenes in particular are set out in our motorized shade automation guide.
Some systems also allow a direct link. On Z-Wave this is called association: the keypad is told to send a command straight to a group of devices, so a button keeps working even when the hub is down. It is fast and robust but limited to simple commands. Full scenes that mix device types normally run in the hub.
Z-Wave scene controller and other protocols
A Z-Wave scene controller reports each button to the hub, and the specification defines how. The Z-Wave Alliance specification for developers states that every Z-Wave device has a device type, a role type and a list of command classes it supports. Button reporting is one of those command classes, so the hub has to support the same one, or the buttons show up but do nothing useful. The radio layer underneath is the international recommendation ITU-T G.9959.
Zigbee, Thread-based and proprietary lighting systems have their own scene keypads, and the rule is the same: the keypad and the hub must speak one protocol. Our Z-Wave vs Zigbee comparison covers the mesh radios, and extending Z-Wave range helps when a keypad at the far end of the house drops commands.
Button events: press, hold and multi-tap
A multi button scene switch gets more out of each button than its count suggests. Z-Wave developer documentation for wall controllers describes separate reports for a single press, the start of a hold and the release, and the button reports can include double, triple and further taps. That lets one button carry several actions:
- Single press: recall the scene.
- Double tap: a second scene, such as all off for the floor.
- Hold and release: raise or lower, used for dimming a group or moving shades.
Which events a keypad sends, and which a hub can act on, varies by model and software. Check both data sheets before you promise a client a double-tap scene.
Button LEDs and status sync
Most keypads have an LED per button, and this is where installs most often disappoint. Forum threads on multi-button keypads keep returning to the same complaint: the LEDs show the wrong state. A button lights when pressed, but if the scene is changed from the app or another keypad, the light stays on.
Good practice:
- Choose a keypad whose LEDs the hub can set independently of any local load. Makers call this setting by different names, often a status mode.
- Program the hub to update every keypad LED when a scene starts or ends, from whatever source.
- Decide what “on” means for each button, such as the scene active or any light in the scene on, and write it down for the client.
Choosing and planning a scene keypad
Wired or battery
A wired keypad needs a box and power; many need a neutral, which our smart switch neutral wire guide explains. A battery panel goes anywhere but needs battery changes. Use wired where the box exists and battery where it does not.
Button count and engraving
More buttons are not always better. Plan the scenes first, then pick the count. Engraved or labelled buttons help guests and clients; an unlabelled six-button keypad becomes a guessing game.
Programming in the hub
Set the scenes before the visit ends: build each scene from the devices’ current states, assign it to the button and event, test from every keypad and the app, then confirm the LEDs follow. If the client uses smart bulbs, read smart switch vs smart bulb so a wall control never cuts their power.
Where to find lighting and shade controls
The lighting control category lists remote and multi-location dimmers and a dimmer and keypad combo. The motorized shades category lists keypads with raise and lower buttons, such as a 6-button keypad with raise and lower, and the Z-Wave category covers hub-based devices. All sit in the Security, Surveillance and Control division. For compatibility, pricing and availability, ask your sales representative through the Bursma contact page or at the Grand Rapids area branch, or open a Bursma dealer account.
Frequently asked questions
Does a scene controller need a hub?
Usually. The hub stores the scenes and sends the commands. Some protocols let a keypad control devices directly, such as Z-Wave association, but only for simple commands.
Can a scene controller also control a light directly?
Some can. Certain wired keypads switch or dim a local load as well as sending scene buttons. Others switch nothing and only send events.
Is a scene controller the same as a companion switch?
No. A companion switch controls one paired smart switch and its load. A scene controller triggers scenes across many devices through a hub.
Why do my scene controller LEDs show the wrong state?
The LED usually reflects the last button press, not the scene’s real state. Program the hub to update each LED when the scene changes from any source.