User`s guide
X10CONFIG(5) X10CONFIG(5)
ORE_DISPLAY_COUNT directive
Determines whether the rawdata is displayed in the monitor/logfile for Oregon Wind and Rain sensors.
The parameter choises are YES or NO, with the default being NO.
RFXCOM_DISABLE directive
The RFXCOM RF receiverhardware may be configured to suppress signals from specific sensor types to
improve noise immunity and/or to ignore foreign signals from nearby sensors. Its use supercedes the direc-
tive RFXCOM_ENABLE, which is nowobsolete since newer RFXCOM firmware supports a wider variety
of signal types.
The syntax is:
RFXCOM_DISABLE <type> [<type> [<type> ...]]]
The signal types which may be disabled are currently:
OREGON
ARCTECH
ATIWONDER
KOPPLA
X10 (Standard and Security X10)
HE_UK (HomeEasy -UKand KAKU protocols)
HE_EU (HomeEasy -EUprotocol)
VISONIC (Receivable only by RFXCOM VISONIC receivers.)
All but HE_UK and HE_EU may be abbreviated to three characters.
Examples:
RFXCOM_DISABLE OREGON
RFXCOM_DISABLE ORE ARC ATI
RFXCOM_ENABLE directive
This is nowobsolete. See RFXCOM_DISABLE above.
===============================================
The following directivesprovide controls for Heyu´s security system features.
===============================================
ARM_MAX_DELAYdirective
When the ´heyu arm max ...´ command is entered at the command line or receivedfrom the RF auxiliary
device, Heyu´s security flag is initially set to "armpending". At the end of the delay (in seconds) specified
by this directive,the security flag is changed from "armpending" to "armed". The following example speci-
fies the delay to be 30 seconds:
ARM_MAX_DELAY30
The default for this directive is0(zero), which sets the "armed" flag immediately regardless of the "max" or
"min" parameter.
ARM_REMOTE directive
This directive controls the behavior of Heyu when an ´arm´ signal is receivedfrom an RF Security remote
(source RCVA). The allowed parameters are AUTOorMANUAL, with the default being AUTO. If set to
MANUAL, the signal does not automatically set the global security flags, thus allowing the signal to be
used to launch a script to customize the arming process, e.g., to first check that all doors and windows are
closed and takeanalternate action if theyare not. This directive has no effect for ´arm´ commands origi-
nating from the command line or other sources.
local 26










