This article describes how to configure motorised blind coverings in a Space CE room. Blinds can be controlled from the room’s touch panel, with options for device connection, control methods, and remote access permissions.
Blinds that use Preset or Fader control are driven by the room’s lighting control system — typically a Dynalite or C-Bus controller. This article refers to that device as the lighting controller. Relay-controlled blinds are driven by a digital IO (relay) device instead.
Field reference
| Field | Description | Default |
|---|---|---|
ID | Unique identifier for the blind within the room configuration | - |
Label | Display name shown on the UI | Blind |
Device ID | References a device defined in the device configuration | - |
Disable | When true, the blind is excluded from the room. Disable also applies to individual channel entries | false |
Type | Relay trigger mode: pulse, double pulse, latch, or reverse latch | pulse |
Trigger Method | Relay contact type: normally open or normally closed | normally closed |
Open Trigger ID | The open trigger value. Its meaning depends on the control method (see below) | - |
Close Trigger ID | The close trigger value. Follows the same rules as Open Trigger ID | - |
Stop Trigger ID | The stop trigger value. Follows the same rules as Open Trigger ID. For Relay blinds, if this is 0 or omitted the system activates both the open and close relays at once as a stop command | - |
Control Method | How the blind is driven: Relay, Preset, or Fader | Relay |
Area ID | Lighting controller area. Relevant only for Dynalite-controlled blinds (see below) | 0 |
Remote Controllable | Expose the blind to remote control surfaces | false |
Remote Name | Name shown on remote surfaces | the value of Label |
Control Method semantics
Control Method tells Space CE how the blind is physically driven. Choose the one that matches the device wired to the blind:
- Relay: controls the blind by activating relay channels on a digital IO device.
- Preset: recalls a stored preset on a lighting controller or DSP device.
- Fader: sets a fader level on a lighting controller channel. Requires a
Channelsarray to be defined.
Trigger value by control method
The Open, Close, and Stop trigger values are interpreted according to the control method:
| Control Method | Meaning of the trigger value |
|---|---|
| Relay | The relay channel number to activate |
| Preset | The preset number to recall on the lighting controller or DSP |
| Fader | The fader level to set on the lighting channel (typically 0 to 255, depending on the controller) |
Area ID: when it applies
Area ID is only relevant for Dynalite-controlled blinds, where it identifies the Dynalite area. For C-Bus, do not rely on Area ID: the C-Bus application number travels with the trigger or preset value itself, not through Area ID.
Channels
Channels define the lighting controller group channels used with the Fader control method on C-Bus and Dynalite devices.
| Field | Description | Default |
|---|---|---|
Disable | Excludes the channel from initialisation when true | false |
Channel ID | The physical channel. For C-Bus this is the group address; for Dynalite this is the channel number | - |
Only Channel ID (and Disable) applies per channel. A channel-level ID, if present, is ignored.
Duplicate Channel ID values within the same blind are ignored.
Worked example
The example below shows two blinds driven by a Dynalite controller, using numeric trigger values.
[
{ "ID": "blind.1", "Label": "Sheer", "Device ID": "dev.lighting.controller.1", "Area ID": 36, "Open Trigger ID": 1, "Close Trigger ID": 4, "Stop Trigger ID": 2 },
{ "ID": "blind.2", "Label": "Blockouts", "Device ID": "dev.lighting.controller.1", "Area ID": 24, "Open Trigger ID": 1, "Close Trigger ID": 4, "Stop Trigger ID": 2 }
]