User`s guide

X10CONFIG(5) X10CONFIG(5)
Launch conditions can be quite simple, like´A1 on´, or quite complex. In addition, there are special launch
condition for extraordinary situations: −powerfail´, ´-rfflood´, ´-timeout´.
See x10scripts(5) for a full description of launch conditions.
Keep in mind that Heyu will normally launch a script only for the first set of launch conditions which are
satisfied, i.e., only one script is launched per signal or special condition, although this restriction can be
overridden. Launch conditions are tested in the order theyappear in the configuration file.
The symbol ´::´ (twocolons) is always required (so that Heyu can distinguish when the launch conditions
end and the command line starts).
Exec options are zero or more of the following:
-xtend (or simply -x) Create an environment compatible with Xtend scripts.
(No other options are compatible with -xtend.)
-rawlevel(or simply -r) Use native raw dimlevels instead of percentages
for state bitmaps in the Heyu environment.
-noenv(or simply -n) Provide no additional environment variables
beyond those already in the user´s environment.
The <command line> can be anyexecutable binary,shell script, or shell command.
Examples:
SCRIPT D1 on :: doorbell_actions.sh
SCRIPT -l wake_em_up C1 on :: play $HOME/music/reveille.wav
SCRIPT -l PowerFail -powerfail :: echo "There was a power failure" | mail
SCRIPT -l RF_Flood -rfflood :: heyu on Siren
SCRIPT -l Timeout -timeout timer2 :: echo "Timeout on Timer number 2" | mail
If a script directive references an alias in place of a housecode|unitcode, the alias directive must have been
defined earlier in the configuration file.
LAUNCHER directive
This optional directive can wholly or in part specify the condition or conditions under which the associated
script will be executed (or ´launched´).
The format is:
LAUNCHER <script label> <launch conditions>; <launch conditions>; ...
where:
<script label> identifies the associated script with the same label.
See x10scripts(5) for a full description of what can appear in <launch conditions>.
Multiple launchers for the same script may be continued on the same line following a semicolon, or may be
configured as separate LAUNCHER lines.
Example:
If no launch condition was specified in the ´wake_em_up´ script above,itwould be specified in a launcher
likethis:
LAUNCHER wake_em_up C1 on
local 15