The Lighting section defines the lighting controls available in a Space CE room. Administrators use it to expose scene recalls, dimmer faders, and on/off switches on the touch panel, and to drive lighting automatically at startup, during presentations, and at shutdown.
Lighting is configured from four control types — Presets, Channel Presets, Faders, and Toggles — giving explicit, granular control over individual controller presets, dimmer faders, and switches.
Key terms
| Term | Meaning |
|---|---|
| C-Bus | A Clipsal lighting-control ecosystem. |
| Dynalite | A Philips lighting-control ecosystem. |
| DSP | Digital signal processor, an audio device (e.g. a Q-SYS core) that can also recall lighting-style presets. |
| Lighting controller | The device that physically drives the lights. Both C-Bus and Dynalite controllers are lighting controllers. |
| Fader | A continuously variable dimmer level, as opposed to a fixed preset or a simple on/off switch. |
Across every control list, the Invisible field (boolean, default false) hides the control from the touch panel while still allowing it to be recalled by automation such as macros and default routes.
Areas and channels
Both C-Bus and Dynalite organise a lighting controller into areas, and each area into channels. Space CE addresses lights the same way: presets, faders, and toggles name the Area they act on, and faders and toggles then name the individual Channel IDs within that area.
Area— the group of lights a control acts on. Recalling a preset sets that whole area to a stored scene; a fader or toggle acts on the channels you list within the area.Channel ID— an individual dimmer or circuit within the area.
Each ecosystem has its own name for these:
| Space CE field | C-Bus | Dynalite |
|---|---|---|
Area | Application number | Area number |
Channel ID | Group address | Channel number |
A single physical lighting controller can drive many presets, faders, toggles, and blinds at once — each is simply addressed by its own Area (and, for faders and toggles, its Channel IDs).
Lighting controls
Presets
Presets recall a specific preset index, area, or scene on an integrated lighting controller. Use a preset when the lighting controller already stores the scene and you only need to trigger it.
| Field | Description | Default |
|---|---|---|
ID | Unique identifier | - |
Label | Display name for the preset | - |
Device ID | Lighting controller device that stores the preset | - |
Area | Area designation. For C-Bus this is the application number; for Dynalite this is the area number | empty |
Fade Time | Fade duration in milliseconds | -1 (use the controller’s own default) |
Value | The preset target level or preset number to recall | - |
Invisible | Hide the preset from the touch panel | false |
Remote Controllable | Expose the preset to remote control surfaces | false |
Remote Name | Name shown on remote surfaces | the value of Label |
Channel Presets
Channel Presets compose a scene by explicitly setting one or more faders to target levels, without sending a hardware scene recall. Use a Channel Preset when you want Space CE to build a scene from your own faders rather than relying on a preset stored on the controller.
| Field | Description | Default |
|---|---|---|
ID | Unique identifier | - |
Label | Display name on the touch panel | - |
Invisible | Hide while still allowing automation recall | false |
Remote Controllable | Expose to remote control surfaces | false |
Remote Name | Name shown on remote surfaces | the value of Label |
Each Channel Preset carries a Channel Values array. Each entry sets one fader:
| Field | Description |
|---|---|
Fader ID | References a fader defined in the Faders section |
Value | Target level for that fader (0 to 100) |
Faders
Faders provide continuous dimmer control over specific lighting channels. Use a fader when the end user needs a variable dimmer rather than a fixed scene.
| Field | Description | Default |
|---|---|---|
ID | Unique identifier | - |
Label | Display name | - |
Device ID | Lighting controller device | - |
Area | Application area designation (C-Bus application number, Dynalite area number) | empty |
Fade Time | Default fade duration in milliseconds | -1 (use the controller’s own default) |
Invisible | Hide from the interface | false |
Remote Controllable | Expose to remote control surfaces | false |
Remote Name | Name shown on remote surfaces | the value of Label |
Each fader carries a Channel array. Each entry names one physical channel:
| Field | Description |
|---|---|
ID | Channel entry identifier |
Channel ID | Physical channel on the controller. For C-Bus this is the group address; for Dynalite this is the channel number |
Toggles
Toggles provide simple on/off control for lighting channels. Use a toggle for a single-button switch such as house lights or a projector-screen light.
| Field | Description | Default |
|---|---|---|
ID | Unique identifier | - |
Label | Display name | - |
Device ID | Controller device | - |
Area | Area designation (C-Bus application number, Dynalite area number) | empty |
Fade Time | Fade duration in milliseconds | -1 (use the controller’s own default) |
Toggle On ID | Preset recalled for the on state, for a preset-based toggle (see below) | - |
Toggle Off ID | Preset recalled for the off state, for a preset-based toggle (see below) | - |
Toggle On Value | Level applied to the toggle’s channels for the on state, for a channel-based toggle (see below) | 100 |
Toggle Off Value | Level applied to the toggle’s channels for the off state, for a channel-based toggle (see below) | 0 |
Invisible | Hide from the interface | false |
Remote Controllable | Expose to remote control surfaces | false |
Remote Name | Name shown on remote surfaces | the value of Label |
A toggle can be driven in one of two ways. Choose one:
- Preset-based: set
Toggle On IDandToggle Off IDto preset numbers stored on the lighting controller. Use this when the on and off states are already defined as presets on the controller. - Channel-based: set
Toggle On Value(default100) andToggle Off Value(default0) to the levels applied to the toggle’s own channels. Use this when there is no stored preset and you want Space CE to set a level directly.
Each toggle also carries a Channel array with the same ID and Channel ID fields as a fader.
Settings
The Lighting > Settings object drives automatic lighting behaviour.
| Field | Description | Default |
|---|---|---|
Default Preset | The preset recalled when the room mode changes (on startup and shutdown) | empty |
Presentation Preset | The preset recalled when a source is routed to a display destination | empty |
Time Based Shutdown Preset | Preset or scene recalled on a time-based shutdown | empty |
Auto Lighting Enabled | Whether Space CE recalls the above presets automatically | false |
Manually Controlled | Marks the room’s lighting as operated by manual controls external to Space CE, such as a wall panel (see below) | false |
On the touch panel
Each control type has a fixed presentation, so the choice you make here decides what the room’s users see.
| Control | How it appears |
|---|---|
Presets and Channel Presets | One button per preset, labelled with its Label. Pressing a button recalls that preset directly |
Faders | A dimmer fader, labelled with its Label |
Toggles | A single on/off button |
Two fields change what is shown rather than what it does:
Invisiblehides a control from the panel while leaving it available to macros, default routes, and the automatic recalls inSettings. Use it for scenes that should run without a user being able to trigger them.Auto Lighting EnabledinSettingsis what makesDefault PresetandPresentation Presetfire on their own. With it off, those presets are configured but never recalled automatically.
A room with no lighting controls gets no lighting area on the panel, so an empty Lighting section is the right way to leave lighting out of a room rather than adding hidden controls.
Which control to use and when
- Use a Preset when the scene already lives on the lighting controller and you only need to trigger it by number.
- Use a Channel Preset when you want to build a scene inside Space CE from your own faders, without relying on a controller-stored scene.
- Use a Fader when the end user needs a continuously variable dimmer.
- Use a Toggle when a single on/off switch is enough. Pick preset-based toggles (
Toggle On ID/Toggle Off ID) when the states are stored presets, and channel-based toggles (Toggle On Value/Toggle Off Value) when Space CE should set levels directly.
Worked example
Channel Presets and Faders
{
"Channel Presets": [
{ "ID": "preset.high", "Label": "High", "Channel Values": [ { "Fader ID": "fader.1", "Value": "100" } ] },
{ "ID": "preset.off", "Label": "Off", "Channel Values": [ { "Fader ID": "fader.1", "Value": "0" } ] }
],
"Faders": [
{
"ID": "fader.1", "Label": "Scenes", "Device ID": "dev.lighting.controller.1", "Area": "202", "Fade Time": 301,
"Channel": [ { "ID": "channel.1", "Channel ID": "1" } ]
}
]
}