Composer HE User Guide

Programming basics

Use the Control4® Composer HE Programming view to configure events and actions. In Composer HE, click Programming to display the Programming view.

 

Configuring is based on events. When an event starts, it triggers actions to take place.

 

Example: When the projector screen lowers (the 'event' starts), the receiver, DVD player, and projector all power on (the 'actions' of the receiver, DVD player, and project are all caused by the screen-lowering event).

 

To program the Control4 system, you use Composer HE to drag-and-drop events and actions for corresponding devices to a Script pane. Details about how to do this are explained below.

 

This table describes what events, actions and scripts are used when configuring the system, and how they are used.

 

Item Description
Events

All programming begins with events. An event is a “when” statement:  the trigger reporting that something happened, resulting in an automated action. Events happen instantaneously.

 

Example: On a keypad, pushing a button is one event. Actions all happen under events.

 

Other events include:

 

When the door opens

When it is 7:00 a.m.

When it is sunrise

Actions

After the event communicates to the system that something happened, it will send actions.

These methods are used to define actions:

  • Commands. The Commands tab displays all available commands for a selected item in the Device Actions tree. A command is a “do” statement. Commands are actions the Director tells the device to do so it performs a certain behavior.

Examples of commands include:

    • Light: on, off

    • VCR: play, stop, pause

    • CD Changer: go to disk

    • Security device: arm, disarm

    • TV: Power on/off, change channel

  • Conditionals. The Conditionals tab displays all available conditionals for a selected item in the Device Actions tree. A conditional is an “if” statement. An “if” statement asks a true/false question to the device.

Examples of conditionals include:

    • If door is open

    • If after 5 p.m.

    • If the light is greater than 50 percent

  • Delays. A Delay stalls a program from running to ensure that the actions happen at the right time.

Script The linking of events and actions is defined in the script. These events and actions move to the Script pane.

 

Tip: You can use Properties, Agents and Variables also to configure or program devices. These are considered advanced configuration and programming. See Programming with Agents for information.

 

Control4 basic programming consists of two parts:

 

  1. Define a device’s events that trigger the actions (left pane).
  2. Define a device’s actions to trigger when an event fires (right pane).

 

Refer to the steps in the next two figures to learn about the basic programming tasks.

 

  1. Define the device's events (follow the screen's steps and arrows below):

 

 

  1. Define the device's actions (follow the screen's steps and arrows below):

 

 

Note: Programming makes use of agents also, which let you include pre-programmed system functionality, for example, scheduling, delays, or setting up Lighting Scenes.

 

Example: To program around sunrise and sunset, you use the Scheduler agent. See Programming with Agents for information about using agents in programming.

Related topics:

Programming the System

Programming with Commands

Programming with Delay, Stop and Break Commands

Programming with Conditionals

Programming with Agents

See also:

Composer HE and System Documentation