Skip to content
Innomesh
Room Manager

Space CE Room Overview

Space CE rooms are created from system templates but operate with greater independence compared to Space VC rooms. Template updates do not automatically propagate to rooms, and software versions can diverge. Innomesh flags synchronisation issues between rooms and their templates to help maintain environmental uniformity.

Space CE rooms share three primary configuration sections: Properties, Devices, and Macros.

Properties

The Properties section contains the following configuration fields.

  • Template Version: The system template version deployed against the room.
  • Room Name: A friendly identifier for the room.
  • Room Repository Name: An auto-populated global identifier based on the room name.
  • Room Author: Automatically populated with the creator’s name.
  • In Maintenance: Marks rooms under construction or refurbishment. When enabled, alerts are diverted to the Suppressed Alerts list.
  • Is Portable: Designates portable rooms. Connectivity and communication alerts are redirected to the suppressed tab when enabled.

Devices

Main View

The device configuration displays several key elements.

  • Types: IP or Gateway devices, with Pulse monitoring optionally included.
  • Device Fields: Properties describing key device characteristics.
  • Actions: Information, duplication, editing, and deletion options for each device.
  • CSV Export: Download device lists as CSV files for external reference.
  • Add Device: Button to create new devices.
  • Update: Allows isolated Space CE or Pulse template updates.

Adding a New Device

When creating a device, several checkboxes are available.

  • In Maintenance: Suppresses device alerts during maintenance periods.
  • Is Portable: For devices not always connected, such as removable equipment.
  • PDU Connected: Indicates a power distribution unit connection. Suppresses alerts when the device is powered off.
  • Disable: Removes the device from the active configuration.

Standard fields vary by device type but always include Device Name, Driver, and ID.

Device Types

IP Devices require the following fields: Type, Driver, Name, ID, Model, and Hostname or IP Address. An Advanced Connection Settings menu, hidden by default, expands to reveal additional options including Port, Baud Rate, Username, and Password.

Gateway Devices require: Type, Driver, Name, ID, and a Gateway Device ID that references the IP device through which the gateway device communicates.

Macros

Macros execute custom lambda script actions triggered by events or schedules.

Macro Elements

  • ID: A unique identifier. The recommended format is macro.trigger.[device].operation.
  • Disable: Ignores the macro when set to true.
  • Name: A friendly identifier for the macro.
  • Time Triggers: Schedule-based execution using HH:mm:ss format with day specification. Accepted values for Days include a comma-separated list such as Monday, Tuesday, Thursday, or the shorthand Weekday (Monday to Friday) or Weekend (Saturday or Sunday).
  • Event Triggers: Property-based execution using GUID, Property, Key/Index, and Value matching.
  • Actions: Executed scripts referencing a Device ID, with an optional delay in seconds.
On this page