User`s guide

X10CONFIG(5) X10CONFIG(5)

INACTIVE_TIMEOUT directive

Most security sensors transmit a signal with their current state (known as a "heatbeat") every 60-90 minutes

to let the host system knowtheyare operational.

RFXSensors do the same thing every 40 or 80 minutes, depending on whether hardware conﬁgured for fast

or slowsampling.

Oregon sensors transmit at intervals of 11 to 120 seconds, depending on model.

Heyu records the times the signals are received. The commands ´heyu sensorfault´ and ´heyu showsen-

sors´ compare the elapsed times since the last receivedsignals with the value speciﬁed with this directive to

judge whether a sensor has become inactive.

The value for this directive may be speciﬁes in seconds or in hh:mm:ss format. The default is 4:00:00 or 4

hours. Example:

INACTIVE_TIMEOUT 4:00:00

This directive (or its default) can be overridden for a speciﬁc sensor having a heartbeat by appending the

parameters "IATO hh:mm:ss" to the ALIAS directive which maps that sensor to a Hu addresss.

INACTIVE_HANDLING directive.

The parameter choice is NEW or OLD, with the default being NEW.Choosing OLD reverts to the previous

wayHeyuhandled the situation when a sensor having a heartbeat failed to send a signal within the interval

deﬁned by the INACTIVE_TIMEOUT directive.See man page x10scripts(5) for details.

ARM_LOGIC directive

The value of this directive may be speciﬁed as STRICT,LOOSE, or MEDIUM. The default is MEDIUM.

When speciﬁed as STRICT,the state of the security ﬂags may be changed from "disarmed" to "armed" or

"armpending" and vice-versa, but no changes between "armed" and "armpending" or between "home" and

"away" are allowed. I.e., the system must be in the "disarmed" state before any´heyu arm ...´ command

can takeeffect.

When speciﬁed as LOOSE all changes are allowed. A ramiﬁcation is that the ´arm max ...´ command when

the system is already in the "armed" state will effectively disarm the system - put it in the "armpending"

state - for the duration speciﬁed by the ARM_MAX_DELAYdirective for as long as this command contin-

ues to be executed.

When speciﬁed as MEDIUM, all changes are allowed except the transition from "armed" to "armpending".

Example:

ARM_LOGIC MEDIUM

===============================================

The following experimental directivesare otherwise undocumented and may or may not be useful for test-

ing, hacking, or troubleshooting purposes.

===============================================

CM11A_QUERY_DELAYdirective

On some systems a short delay appears to be required between a message from the CM11A that it has

incoming powerline data and Heyu´s polling for that data. The parameter for this directive speciﬁes the

delay time in milliseconds. The default is 0, indicating no delay.Use of this directive may resolvethe

problem when Heyu reports: "The interface didn’tanswer a getinfo response." when attempting to receive

incoming powerline data.

local 27