Program Blocks
In previous version of the controller firmware, each automation program was constructed of a single line that consisted of a
trigger, one or two optional conditions, and a command. Enhanced automation programs are now constructed in blocks to create
a simpler, yet more flexible programming environment. Each program block may contain multiple triggers, multiple conditions,
and multiple commands.
“Every” Program Trigger
A new program trigger has been added which allows a program block to be activated every so many seconds, minutes, or hours.
This trigger is specified with an associated timer; when the timer expires, the program block is processed, and then the timer is
reset.
This program trigger is used to evaluate conditions on an ongoing basis, by the length of the specified time. For example:
EVERY 5 SECONDS
AND IF THERMOSTAT 1 IS GREATER THAN 75
THEN BEDROOM FAN ON
Relational Operators in Conditions
For each condition, you have the ability to utilize relational operators. Each condition includes an operator and one or two values
to check. Relational operators include equal to, not equal to, less than, greater than, is even, is odd, is a multiple of, and set
membership checks. Greater than and less than operators allow for an extra value to be specified to check if a certain item is
greater than or less than another item by more than the specified amount. For example:
WHEN ARM AWAY
AND IF WINDOW FLAG CURRENT VALUE IS LESS THAN 10
THEN THERMOSTAT 1 OFF
“And/Or” Logic Operators in Conditions
A program statement with “And” specifies a conditional expression that must be true for the remainder of the program block to be
processed. A program statement with “Or” combines two or more groups of “And” statements, such that as long as all the “And”
statements in one of the groups are true, the commands in the “Then” group is processed.
For example:
WHEN ARM AWAY
AND IF LIVING ROOM ON
AND IF DINING ROOM ON
OR
AND IF DARK
THEN ALL HOUSE LIGHTS OFF
Enhanced Conditions
Conditions can reference properties of units, security status, zones, thermostats, temperature and humidity sensors, time, date,
audio, access control, messages, as well as constants and user settings. The condition can be evaluated by just about anything the
LEVITON controller knows about.
a. Units: current state, previous state, timer, and level.
b. Security: security mode, current mode including exit delay, arming code, entry timer, exit timer, alarm status,
horn (sounder) status, and digital communicator status for each security area.
c. Zones: loop reading, current state, arming state, and alarm state.
Kommentare zu diesen Handbüchern