Object Status

A Status Parameter is a special type of parameter used to represent the current state of an object.

In many ways, it behaves like a normal parameter, but it is read-only. This means it can be observed and used by other systems, but it cannot be written directly like a regular parameter.

Status Parameters are typically used by objects that establish connections, communicate with external systems, or receive live data.

Examples include:

• devices

• protocol objects

• sensor objects

• tracking-related objects

Logic or utility objects such as workflows, variables, or presets usually do not provide a Status Parameter.

---

Visual Representation

The color of the Status Parameter is also used as the status indicator in the Project Tree.

Objects that provide a status parameter display a small colored status indicator next to their name. The color reflects the current state of the object and updates automatically when the status changes.

This allows users to quickly identify connection states, errors, or activity directly in the project structure without opening the Inspector.

---

Status Types

The following status types are available in Grid Studio.

The displayed status text may vary depending on the device or integration, but the underlying status type remains the same.

Status Type	Color
Undefined	⚫
Active	🟢
Connected	🟢
Disconnect	🔴
Device Error	🔴
Connection Error	🔴
Invalid Settings	🔴
Standby	🟡
Disabled	⚪
Tracked State Live	🟢
Tracked State False	🔴
Tracked State Timeline	🔵
Connecting	🔵

---

Read-Only Behavior

Because a Status Parameter is read-only, it can only be used as a source of information.

This means:

• it can be read in workflows

• it can be read in modifiers

• it can be accessed in scripting

• it can be displayed in widgets

However, it cannot be directly written by:

• workflow actions

• modifier outputs

• manual parameter editing

For this reason, workflows and modifiers do not provide Set actions or outputs for Status Parameters.

---

Status Events in Workflows

Status Parameters can generate standard onChange events like other parameters.

However, objects that provide a Status Parameter often also expose additional predefined status events.

These predefined events are only available when the object itself is added to a workflow — not when only the Status Parameter is used.

Examples of such predefined events may include:

• On Connected

• On Live

• On Disconnected

This provides a more direct and convenient way to react to common state changes without manually checking the status value.

---

Typical Use Cases

Status Parameters are commonly used for:

• monitoring device connection state

• checking whether a system is live or standby

• detecting configuration problems

• reacting to device errors

• driving dashboards or status widgets

Because they are read-only and standardized, they are particularly useful for monitoring and automation.

---

Status Logging

Status changes can also be recorded in the Log.

Status logging can be enabled or disabled for individual objects through the Inspector.

To configure status logging:

1. Select the object.

2. In the Inspector header, click the ( I ) icon.

3. Open the Log submenu.

4. Enable or disable Status Updates.

When enabled, changes of the object's status parameter are written to the log. This can be useful for monitoring device connections, debugging integrations, or tracking system state changes over time.

Note that status logging may be disabled by default depending on the object type or integration.