User`s guide

X10CONFIG(5) X10CONFIG(5)

overthat is more likely an error.) But this limit may be changed with conﬁguration directive

MAX_PPARMS.

MAX_PPARMS directive

Speciﬁes the highest numbered positional parameter allowed in a scene. The number may have any value

between 1 and 999. The default is 8.

STATUS_TIMEOUT directive

Speciﬁes howlong Heyu will wait for a module to reply to a status command before timing out. The

default is 2 seconds. Some modules, SwitchLinc dimmers in particular,may require increasing this to 3.

The allowed limits for this directive are 1-5 seconds. (Don’tuse a value anyhigher than the minimum

needed for satisfactory status reporting.) Example:

STAT US_TIMEOUT 2

SPF_TIMEOUT directive

Speciﬁes howlong Heyu will wait for a module to reply to a "SPecial Function" status command before

timing out. The default is 3 seconds. To date, there is only one special function in Heyu, the display of the

temperature as encoded in a preset command returned from a two-way thermostat or remote thermometer.

(See below.)

RCS_DECODE directive

RCS_TEMPERATURE directive

This is the same directive - use either but not both. The name has been changed since Heyu nowsupports

decoding other RCS status reports such as fan status on/offinaddition to temperature.

This directive instructs the Heyu monitor to decode and display the status reports encoded in a Preset com-

mand transmitted from a two-way thermostat or remote thermometer employing the algorithm used by the

RCS TX15-B and TXB16 thermostats (shown as a table in the thermostat user´s guide).

The Smarthome TempLinc Model 1625 remote thermometer uses the same algorithm for the temperature

report, which is:

temperature = -60 + 32*(unit - 11) + (preset_level-1)

If the Heyu State Engine is running, the decoded temperature is stored at the (ﬁctitious) unit 0 address H0,

where ´H´ is the housecode of the thermostat or thermometer.Itcan be recovered with the ´heyu rcstemp

H´ command. Provided a valid temperature has been stored, anyscript launched by Heyu can recoverthe

temperature as the value of environment variable X10_H0 or the environment variable alias for H0. (Since

these environment variables are created only if valid data has been stored, a check for their existance, e.g., [

"X10_H0" != "" ], may be required before using them in a script or shell command.)

*** WARNING - WARNING - WARNING ***

The use of Heyu or anyother power-line protocol software to control a heater lacking a built-in failsafe

mechanism is not only unwise, it is hazardous to life and downright foolhardy.DON´T DO IT!

This directive may have the values: OFF for no decoding; a list if housecodes enclosed in square [] brackets

for which decoding is to be performed; or ALL to decode anyhousecode. The default is OFF.

Examples:

RCS_DECODE OFF (no decoding)

RCS_DECODE [CFH] (decode on housecodes C, F,and H)

RCS_DECODE ALL (decode on anyhousecode)

Note: This directive need not be used in order to query the thermostat with the ´heyu rcs_req ...´ or ´heyu

temp_req ...´ commands - it only enables the temperature or other status to be displayed in Heyu´s monitor,

regardless of whether or not the thermostat´s transmission was initiated by these commands. (The

local 11