Skip to content
Innomesh
Room Manager

Space VC Room Overview

⚠️ Warning
Space VC is being sunset. New Space deployments for room control will be offered in Space CE only. Existing Space VC rooms will continue to be supported.

A Space VC room is a configured system based on a template blueprint. The key principle is that room configuration will take precedence over the system template configuration. This article covers the main sections of a Space VC room and how they work together.

🚨 Caution
Updating a system template will cause every room created from it to restart, with a brief period of downtime for each room. Only update a template when its rooms are not in use.

Properties

The Properties section contains general room information, including the following fields.

  • Room Name: A friendly identifier for the room.
  • Room Repository Name: An auto-populated global identifier used across the platform.
  • Room Author: Pre-populated with the name of the room creator.
  • Room Location: The physical location of the room, used for timezone determination.
  • Helpdesk Number: The support extension number displayed in the room user interface.
  • In Maintenance: Marks the room as under construction or refurbishment. When enabled, alerts are diverted to the Suppressed Alerts list.
  • Is Portable: Marks the room as expected to be offline during normal operation. When enabled, connectivity alerts are suppressed.

Devices

Space VC rooms support six categories of devices.

  • Native: Crestron native devices with Type, IPID, and IP address fields.
  • IP: Network devices with Model, hostname or IP address, and optional port, baud rate, and credentials.
  • ComPort: Serial devices with Model, ComPort Device Port, and ComPort Device ID. Advanced settings cover Baud Rate, Username, and Password.
  • EISC: Ethernet Intersystem Communication devices with IPID and IP address.
  • Gateway: Devices accessed through another device, referencing a gateway device ID.
  • Cresnet: Devices on the Crestron Cresnet bus.

All device types share common elements: a unique ID (auto-generated), a friendly Name, and a Driver that defines the software interface for device control.

Macros

Macros are automated action sequences triggered by conditions. Each macro includes an ID, a disable flag, a friendly name, and delay settings.

Time Triggers

Time triggers execute actions at specific times on designated days. These are useful for scheduled operations such as powering down displays at end of day.

The Days field accepts a comma-separated list of day names, or one of the shorthand values:

  • Monday, Tuesday, Thursday — specific days
  • Weekday — Monday to Friday
  • Weekend — Saturday or Sunday

Event Triggers

Event triggers execute actions when device properties match specified values. For example, a trigger could fire when a particular device property changes state.

Actions

Actions are lambda scripts that define what occurs when a trigger activates. Each action references a device ID and can include an optional delay in seconds.

On this page