Creating Trigger Actions

Trigger Actions are the starting point for defining your home automation logic. Create Trigger Actions to define automated responses to INSTEON or X10 commands, motion detectors, remote controls, emails sent to Indigo, device state changes, variable value changes, power failure detection, etc.

Creating a Trigger Action

Trigger Type: INSTEON Command Received

Use the Type INSTEON Command Received to trigger an action when INSTEON commands are sent from a device, like a KeypadLinc, and then received by the PowerLinc interface. Select the INSTEON command from the Received popup that you want to cause the trigger, along with the Device from which the command was sent. For devices with multiple buttons, like the KeypadLinc and ControLinc, you can also choose which button press causes the trigger via the Using button popup.

Tip: The Double Tab On and Double Tap Off command types are useful for triggering lighting scenes at a wall switch (like the SwitchLinc). For example, you could create a Double Tap Off trigger action that turns off all the lights in the house when a SwitchLinc near the back door is pressed twice.

Trigger Type: X10/RF Command Received

Use the Type X10/RF Command Received to trigger an action when X10 commands are sent from a device, like a SwitchLinc 2-Way Dimmer, and then received by the X10 or RF interface. Select the X10 command from the Received popup that you want to cause the trigger, along with the Device or X10 Address for that command.

Choose A/V Button Pressed from the Received popup to trigger an action using one of the X10 universal remote controls, such as those included in the X10 "Entertainment Anywhere" kits.

Trigger Type: Device State Changed

Use the Type Device State Change to trigger an action whenever a device's state changes. For example, you could create a Trigger Action for whenever a specific light's brightness becomes greater than 75% or for when your thermostat's temperature drops below 55 degrees.

A device state can change as a result of the following: a direct INSTEON or X10 command sent to that device from a remote control or motion detector, a device action Indigo has sent the device, or the reception of a new status state from the device itself.

Unlike INSTEON modules, not all X10 modules transmit their current states when they are changed directly at the device itself. For example, in order for Indigo to know that you have turned a hallway light on at the light switch itself, the light switch module must be a 2-way module that can transmit X10 signals back to Indigo. We recommend that our users only purchase these 2-way X10 modules in cases where Indigo needs to be aware of the status changes triggered at the device itself. Each X10 transmitter in your system will reduce the X10 signal strength throughout your home wiring. Read our online X10 troubleshooting information if you are having problems reliably sending or receiving X10 commands.

Trigger Type: Variable Changed

Use the Type Variable Changed to trigger an action whenever an Indigo variable value changes. Variable values can change as a result of a Modify Variable action or from the user directly modifying the value. See the using variables section for more information about using variables.

Trigger Type: Indigo Server Startup

Use the Type Indigo Server Startup to trigger an action when the Indigo Server process is first launched.

Trigger Type: Power Failure

Use the Type Power Failure to trigger an action whenever the computer interface detects a power failure. For Indigo to receive this information from the computer interface, the computer running Indigo must be connected to an uninterruptible power supply (UPS). Otherwise, the command from the interface will be sent to a computer with no power.

Trigger Type: Interface Connection Initialized

Use the Type Interface Connection Initialized to trigger an action whenever the communication between Indigo and the interface is successfully started.

Trigger Type: Interface Connection Failure

Use the Type Interface Connection Failure to trigger an action whenever the communication between Indigo and the interface fails. An unplugged USB cable or a malfunctioning interface can cause this error.

Trigger Type: Email Received (Pro only feature)

Use the Type Email Received to trigger an action based on emails sent to Indigo. You can trigger an action if any email is received, or restrict the trigger to emails that contain phrases within the subject title and/or specific sender email addresses. See the configuring email settings section for more information about having Indigo send and receive emails.

Defining the Trigger Condition

Select the Condition panel to define what conditions must be met before the action is executed. For example, you could have a motion detector trigger that only executes the action when the condition If dark is satisfied.

Defining the Actions

Lastly, select the Actions panel to define the actions you want to occur, such as turning on a device or sending an email. For information about creating actions, see the creating actions section.