A Space VC system template serves as the blueprint for all rooms created under it. This article describes the structure and configuration options available within a Space VC template, including Properties, Devices, Macros, and Room Options.
Properties
The Properties section contains general metadata about the template:
- System Name: The friendly name of the system template.
- System Repository Name: An auto-populated global identifier used internally by Innomesh.
- System Description: A brief description of the system type and its intended use.
- System Author: Auto-populated with the name of the user who created the template.
- System Type: The room category. Supported values are General, Boardroom, Breakout Area, Collaboration Space, Conference Room, Control Room, Exhibition Hall, Foyer, Huddle Space, Laboratory, Lecture Theatre, Meeting Room, Office, Signage, Simulation Room, Stadium, Teaching Space, and Tutorial Room.
- Template Version: The configuration version number, formatted as major.minor.revision (for example, 1.0.0).
- Is Portable: When enabled, marks rooms created from this template as portable (expected to be offline during normal operation). Alerts for portable rooms are diverted to the Suppressed Alerts tab.
Devices
The Devices section defines the hardware that will be present in rooms using this template. Space VC templates support six device categories:
All device types share common fields: a unique ID (auto-generated), a friendly Name, and a Driver specifying the software used to control the device. Device-level flags include Is Portable (suppresses alerts for not-always-connected devices), PDU Connected (suppresses alerts while the room is powered off), and Disable (removes the device from the active configuration). The main device view supports a Download as CSV action for exporting the current list.
Native
Native devices communicate directly with the Crestron control system using CIP. Required fields: Type, Driver, Name, ID, and IPID (the Crestron IPID used to control the device).
IP
IP devices communicate over the network using TCP/IP. Required fields: Type, Driver, Name, ID, and Model. Advanced Settings include IP Port, Baud Rate, Username, and Password.
ComPort
ComPort devices communicate via serial. Required fields: Type, Driver, Name, ID, Model, ComPort Device Port, ComPort Device ID, and optional Username / Password.
EISC
EISC (Ethernet Intersystem Communication) devices bridge separate Crestron control systems over the network. Required fields: Type, Driver, Name, ID, IPID, and IP Address.
Gateway
Gateway devices are controlled through another device rather than directly. Required fields: Type, Driver, Name, ID, and Gateway Device ID (the ID of the IP device through which this device communicates).
Cresnet
Cresnet devices connect via the Crestron proprietary Cresnet bus. Required fields: Type, Driver, Name, ID, and Cresnet ID.
Macros
Macros define custom actions that are triggered automatically by events or schedules. Each macro contains a trigger (defining when it activates) and one or more actions (defining what it does).
Time-Based Triggers
Time-based triggers execute at a specified time on designated days. The time is set in HH:mm:ss format, and days accept values such as “Monday, Tuesday” or shorthand like “Weekday” and “Weekend.”
Event-Based Triggers
Event-based triggers execute when a specified property on an object changes to a particular value. Configuration includes the object GUID, the property name, the target value, and optional dictionary key or list index fields for complex properties.
Each trigger element accepts ID, Disable, and (for time triggers) Time / Days, or (for event triggers) Guid, Property, Key, Index, and Value.
Actions
Each action element contains:
| Field | Description |
|---|---|
| ID | Unique identifier for this action. |
| Disable | If true, the action is ignored. |
| Script | The lambda script that defines the action. |
| Device ID | Required when the device keyword is used in the lambda script; specifies the device the script refers to (defined under #/Devices/IP/ID). |
| Delay | Delay (in seconds) between the trigger firing and the action executing. |
For a collection of ready-to-use macro scripts, see Macros.
Room Options
The Room Options section allows administrators to select which template configuration items can be managed at the room level. Only the items selected here will be visible to users when they edit a room based on this template.
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 at the room level.
Room-level settings override template settings when both exist.