Device - Igloo Core Engine (Remote)

The Triggers and Actions system now supports controlling remote instances of the Igloo Core Engine over the local network. Unlike the local Igloo Core Engine device, the Remote Igloo Core Engine device communicates via network API calls and requires an API Key for authentication. This key must match the API Key configured on the target remote Igloo Core Engine instance before any API messages can be sent.

Device Configuration

The settings for Remote Igloo Core Engine devices are stored in:

C:\ProgramData\Igloo Vision\IglooCoreEngine\settings\triggers and actions\devices\remoteice\RemoteICESettings.xml

Below is an example configuration file for a Remote Igloo Core Engine device:

<devICEs>
    <devICE>
        <network uuid="" name="180 Cylinder">
            <ipAddress>192.168.1.2</ipAddress> 
            <port>10000</port>
            <APIKey></APIKey>
        </network>
    </devICE>
</devICEs>

• uuid: A unique identifier for the Remote device. This should not be edited manually, it will be auto generated at runtime. When creating a new device set the uuid to be empty.

• name: A unique identifier for the Remote device.

• ipAddress: The IP address of the remote instance.

• port: The port number on which the remote instance listens for API messages, typically 10000

• APIKey: The authentication key required for API communication. This is the last two segments of the API key of the remote machine

Actions

The Remote device exposes the same set of events and tree structure as the local Igloo Core Engine device, although populating the list of layers is not supported at this time.

Once the Remote device is configured, its actions appear within the Triggers and Actions system. You can link these actions to triggers such as session loads or user interactions. When a trigger fires, the Remote device sends the corresponding API message to perform the desired action on the remote instance.

Example Use Case

1. Define a Trigger:
   For example, when a new session is loaded, the trigger fires.

2. Link the Trigger to a Remote Action:
   Associate the trigger with the Load Session action.

3. Action Execution:
   Upon trigger activation, the Remote device sends an API message to the remote instance. The remote Igloo Core Engine instance responds by loading the specified session.