Information Technology Reference
In-Depth Information
X10 Devices
X10 devices are not as flexible as the Ambient Orb in several ways,
but they are a great option when you don't have the budget for an
Ambient Orb. When thinking about implementing an X10 device as a
feedback mechanism, consider the following.
Requires:
Device capable of receiving X10 messages and a
home automation kit (e.g., FireCracker).
Advantages:
Cool factor, “glanceable,” and access to any elec-
trical device.
Disadvantages:
Binary information: the device is either on or
off. Just like the Orb, you must be within visual range to notice
that action needs to be taken. X10 devices are not useful to the
visually impaired.
An X10 device is another “glanceable” device with two distinct
differences: There are literally hundreds of different X10 devices to
choose from, and there are only two visual modes with an X10 device,
either on or off (you configure which mode indicates what). The effect
is similar to the Ambient Orb; we value a central, simple notification
to improve quality, and we rather like using something a little more fun
to do it. The X10 device is a relatively cost-effective solution to notify
all project members in visual range of the latest build status.
Listing 9-4 shows a CruiseControl config.xml file configured to
turn on X10 device(s) A2 and turn off X10 device(s) A3 using a
CM17A computer interface on COM1 whenever the build succeeds or
fails. This example demonstrates how to control two lava lamps as
homemade traffic lights (red and green).
4
CruiseControl config.xml File Configured to Trigger X10
LISTING 9-4
Devices
<publishers>
<!-- Successful Builds: Turn on Green Lava Lamp / Light -->
<x10
port="COM1"
4. Quick Start instructions are provided at
http://cruisecontrol.sourceforge.net/
