
The diagram at left depicts the structure of a whole-house automation (WHA) solution hub architecture. The master controller is always central to the logical architecture of a WHA system, thus the term hub, as the other sub-systems or components connect to the master similar to spokes in a wagon wheel. This architecture is prevalent due to the need for a central respository and executor of the custom logic programmed in the system enabling the reaction the homeowner desires when certain events are detected by the system.
Note the master controller is typically a proprietary or general purpose computer. The typical operating systems for these computers could be Windows, Linux, or a custom OS developed by the manufacturer. The master controller, in addition to executing custom logic, provides complementary services such as a scheduler, scene configuration, system modes or variables, interface customization, and email notification. And yes, the master controller could be a Windows PC running a WHA software package. But if the master is a proprietary box it normally can plug into your home data network for configuration, management, data/media retrieval, and remote access options.
Most WHA systems have the ability to expand to support larger homes by adding slave controllers. The slave can replicate some functionality such as entertainment center control for homes having multiple centers. Typically a slave controller would be in another room in the home and may have specific lighting devices, thermostat, keypads, and audio/video components associated with it.
Note the master sends control information to A/V components and display information to touch panels and keypads. Communications to other sub-systems or the slave are typically two-way. The method and type of communication link varies by sub-system and manufacturer. However, communication to audio/video components has been limited to stick-on infrared emitter cables or a serial link. Ethernet connections are becoming more prevalent on new A/V components, but are typically used for configuration and firmware update as opposed to an interface to a WHA system. The communications link to the other components and sub-systems within the WHA solution is typically either direct connect, ethernet, or wireless. And is some cases X10 and UPB is also supported for lighting and/or thermostats.
Finally, the master/slave controllers, the touch panels, and keypads typically are produced by the manufacturer of the WHA system. Often the lighting devices and in some cases the thermostats are also produced by the same manufacturer. This is positive for quality control, full function, and seemless operation.
On the other hand, security systems are almost always standalone and must interface to the WHA system via an Ethernet or serial link. Some security systems also include lighting and thermostat options, but we know of none capable of controlling the entertainment center for a complete WHA solution.