A Space CE system template serves as the base configuration that forms the blueprint of a room. Unlike Space VC, updating a Space CE template does not automatically affect rooms that have already been created from it.
The configuration options available for a Space CE template depend on the software version in use. The core configuration sections are described below, with detailed articles for each.
Configuration Sections
| Section | Description | Details |
|---|---|---|
| Properties | General metadata: system name, description, version, type, portability flag | Properties |
| Devices | Hardware definitions (IP devices and gateway devices) with drivers, models, and connection settings | AV Sources |
| AV Sources | Video and content source configurations | AV Sources |
| AV Destinations | Display and output endpoint definitions | AV Destinations |
| Default Routes | Automatic AV routing on room power-on and device connection | Default Routes & Hot Plug Routes |
| Conditional Routing | Rule-based AV routing based on room state or device status | Conditional Routing |
| Macros | Event-based and time-based automation workflows | Macros |
| Recorder | Lecture and presentation recording device configuration | Recorder |
| Lighting | Lighting presets, dimming, and zone control | Lighting |
| Blinds | Motorised blind and shade control | Blinds |
| Room Options | Controls which template settings are editable at the room level | See below |
Properties
The Properties section captures general metadata for the template. Available fields include System Name, System Repository Name (auto-populated from the System Name), System Description, Template Version (in major.minor.revision format, e.g. 1.0.0), System Author (auto-populated with the creator), and the Is Portable flag (marks rooms as expected to go offline; all alerts divert to the Suppressed Alerts tab on the Portal Hotlist).
System Types
Also available: Signage.
Devices
Devices are split into two categories, selectable in the centre column:
- IP Devices: Controlled directly over the network.
- Gateway Devices: Controlled via another device, and may be abstract (e.g. a lighting fader).
Pulse monitoring devices can also be included in the template.
Device fields
Fields common to all device types:
- Type — Device type (e.g. Camera, Projector, Audio Fader).
- Driver — The driver Space CE uses to control the device.
- Name — Friendly name for the device.
- ID — Auto-generated unique identifier (e.g.
dev.display.1). - Model — Device model.
IP devices expose Advanced Settings for IP Port, Username, and Password. Gateway devices include a Gateway Device ID field that references the device through which this device communicates.
Device-level flags
- Is Portable: Alerts from this device divert to the Suppressed list (useful for devices that aren’t always connected, e.g. a display on a removable trolley).
- PDU Connected: Indicates the device is connected to a power distribution unit and only powers on with the room. Alerts divert to Suppressed while the room is powered off.
- Disable: Removes the device from the active configuration.
The device list in each category can be exported as a CSV file using the download button in the main device view.
Macros
Macros are custom actions, defined as scripts, that fire on a trigger. Triggers can be event-based (e.g. when the system powers on) or time-based (optionally restricted to specific days).
Time Triggers
| Field | Description |
|---|---|
| ID | Unique identifier for this trigger. |
| Disable | If true, the trigger is ignored. |
| Time | 24-hour time in HH:mm:ss format. |
| Days | Comma-separated days (e.g. Monday, Tuesday), Weekday, or Weekend. |
Event Triggers
| Field | Description |
|---|---|
| ID | Unique identifier for this trigger. |
| Disable | If true, the trigger is ignored. |
| Guid | GUID of the object generating the event. |
| Property | Object property the event relates to. |
| Key | For Dictionary properties, the key used to access the value. |
| Index | For List properties, the index used to access the value. |
| Value | The property value that triggers the macro when matched. |
Actions
| Field | Description |
|---|---|
| ID | Unique identifier for this action. |
| Disable | If true, the action is ignored. |
| Script | The script that defines the action. |
| Device ID | Required when the device keyword is used in the lambda script; references an IP device ID. |
| Delay | Delay (in seconds) between the trigger firing and the action executing. |
Room Options
The Room Options section allows administrators to select which template configuration items can be managed at the room level. When managing rooms, users will only see the items selected here.
This is particularly useful for enforcing organisational standards when external contractors or standard (non-administrator) users are deploying rooms. By limiting visibility, administrators ensure that only approved settings can be modified during deployment.
Options Menu
After a template has been created, a dropdown Options menu provides the following utilities:
- Download as JSON: Export the template configuration for backup or sharing
- Push Configuration: Push template changes to connected rooms
- Set Available Devices: Restrict which device drivers can be used (Device Configuration Enforcement/)
- Load Template from File: Import a template from a JSON file
- Duplicate Template: Create a copy with all settings
- Delete Template: Permanently remove the template