Abstract:
An electrical control system includes one or more battery-powered RF switches capable of acting as a master or slave or both within the electrical control system. The battery-powered RF switch includes a top housing and a bottom housing. The battery-powered RF switch also includes a printed circuit boar assembly that includes switch sensors, a dimmer button, and an LED indicator. The battery-powered RF switch also includes a manually-operated on/off switch, battery receptacles within the housing, batteries positioned within the battery receptacles and a battery retaining bracket for removably holding the batteries in place within the battery receptacles. The battery-powered RF switch is capable of being mounted to a vertical surface by applying double-sided adhesive to the back side of the housing and pressing the housing against the vertical surface.

Description:
CROSS REFERENCE TO RELATED APPLICATIONS 
     The present application is related to the following: U.S. patent application Ser. No. 11/332,765, filed on Jan. 13, 2006, U.S. patent application Ser. No. 11/332,673, filed on Jan. 13, 2006, U.S. patent application Ser. No. 11/332,690, filed on Jan. 13, 2006, U.S. patent application Ser. No. 11/332,073, filed on Jan. 13, 2006, U.S. patent application Ser. No. 11/332,691, filed on Jan. 13, 2006, U.S. patent application Ser. No. 11/332,728, filed on Jan. 13, 2006, and U.S. patent application Ser. No. 11/332,055, filed on Jan. 13, 2006, the disclosures of which are incorporated herein by reference. 
     BACKGROUND 
     The present disclosure relates in general to lighting and in particular to an electrical control system. 
    
    
     
       BRIEF DESCRIPTION OF THE DRAWINGS 
         FIG. 1  is a schematic illustration of an exemplary embodiment of a control system. 
         FIG. 2  is a schematic illustration of an exemplary embodiment of master nodes. 
         FIG. 3  is a schematic illustration of an exemplary embodiment of slave nodes. 
         FIG. 4  is a schematic illustration of an exemplary embodiment of a hand held radio frequency controller. 
         FIG. 5  is a schematic illustration of an exemplary embodiment of the controller of the radio frequency controller of  FIG. 4 . 
         FIG. 6  is a schematic illustration of an exemplary embodiment of the menu state machine of the application programs of the controller of  FIG. 5 . 
         FIG. 7  is a schematic illustration of an exemplary embodiment of a communication pathway of the associate engine of the menu state machine of  FIG. 6 . 
         FIG. 8  is a schematic illustration of an exemplary embodiment of the scenes engine of the menu state machine of  FIG. 6 . 
         FIG. 9  is a schematic illustration of an exemplary embodiment of a scene in the scenes engine of  FIG. 8 . 
         FIG. 10  is a schematic illustration of an exemplary embodiment of the event engine of the menu state engine of  FIG. 6 . 
         FIG. 11  is a schematic illustration of an exemplary embodiment of an event in the event engine of  FIG. 10 . 
         FIG. 12  is a schematic illustration of an exemplary embodiment of the system panic engine of the menu state engine of  FIG. 6 . 
         FIG. 13  is a schematic illustration of an exemplary embodiment of a panic group in the system panic engine of  FIG. 12 . 
         FIG. 14  is a schematic illustration of an exemplary embodiment of the away engine of the menu state engine of  FIG. 6 . 
         FIG. 15  is a schematic illustration of an exemplary embodiment of an away group in the away engine of  FIG. 14 . 
         FIG. 16  is a schematic illustration of an exemplary embodiment of the memory of the radio frequency controller of  FIG. 4 . 
         FIG. 17  is a schematic illustration of an exemplary embodiment of the devices database of the memory of  FIG. 16 . 
         FIG. 18  is a schematic illustration of an exemplary embodiment of the node information frame for the devices database of  FIG. 17 . 
         FIG. 19  is a schematic illustration of an exemplary embodiment of the keypad of the radio frequency controller of  FIG. 4 . 
         FIGS. 19   a  and  19   b  are side and front view illustrations of an exemplary embodiment of the housing of the hand held radio frequency controller. 
         FIG. 20  is a schematic illustration of an exemplary embodiment of the main menu during operation of the radio frequency controller of  FIG. 4 . 
         FIG. 21  is a flow chart illustration of an exemplary embodiment of a method of operating the radio frequency controller of  FIG. 4  to turn on or off all of the slave nodes within an all on/off group. 
         FIGS. 22   a - 22   b  is a flow chart and schematic illustration of an exemplary embodiment of a method of highlighting a device in the system. 
         FIGS. 23   a - 23   b  is a flow chart illustration of an exemplary embodiment of a method of controlling a highlighted in the system. 
         FIGS. 24   a - 24   c  is a flow chart illustration of an exemplary embodiment of a method of installing a device in the system. 
         FIGS. 25   a - 25   b  is a flow chart illustration of an exemplary embodiment of a method of associating devices in the system. 
         FIGS. 26   a - 26   b  is a flow chart illustration of an exemplary embodiment of a method of uninstalling a device from the system. 
         FIG. 27  is a flow chart illustration of an exemplary embodiment of a method of removing a device from the system. 
         FIGS. 28   a - 28   d  is a flow chart illustration of an exemplary embodiment of a method of replacing a device in the system. 
         FIGS. 29   a - 29   b  is a flow chart illustration of an exemplary embodiment of a method of controlling a device in the system. 
         FIG. 30  is a flow chart illustration of an exemplary embodiment of a method of selecting child protection for a device in the system. 
         FIG. 31  is a flow chart illustration of an exemplary embodiment of a method of renaming a device in the system. 
         FIGS. 32   a - 32   b  is a flow chart illustration of an exemplary embodiment of a method of configuring a device in the system. 
         FIGS. 33   a - 33   b  is a flow chart and schematic illustration of an exemplary embodiment of a method of viewing the version of a device in the system. 
         FIGS. 34   a - 34   b  is a flow chart illustration of an exemplary embodiment of a method of selecting a level of functionality for all switch operation of devices in the system. 
         FIGS. 35   a - 35   d  is a flow chart and schematic illustration of an exemplary embodiment of a method of creating scenes in the system. 
         FIG. 36  is a flow chart illustration of an exemplary embodiment of a method of deleting scenes in the system. 
         FIGS. 37   a - 37   b  is a flow chart illustration of an exemplary embodiment of a method of editing scenes in the system. 
         FIG. 38  is a flow chart illustration of an exemplary embodiment of a method of activating scenes in the system. 
         FIG. 39  is a flow chart illustration of an exemplary embodiment of a method of deactivating scenes in the system. 
         FIGS. 40   a - 40   b  is a flow chart and schematic illustration of an exemplary embodiment of a method of creating events in the system. 
         FIG. 41  is a flow chart illustration of an exemplary embodiment of a method of deleting events in the system. 
         FIG. 42  is a flow chart illustration of an exemplary embodiment of a method of editing events in the system. 
         FIG. 43  is a flow chart illustration of an exemplary embodiment of a method of activating events in the system. 
         FIG. 44  is a flow chart illustration of an exemplary embodiment of a method of deactivating events in the system. 
         FIG. 45  is a flow chart illustration of an exemplary embodiment of a method of selecting a date and time for the system. 
         FIGS. 46   a - 46   b  is a flow chart and schematic illustration of an exemplary embodiment of a method of configuring a panic group for the system. 
         FIG. 47  is a flow chart illustration of an exemplary embodiment of a method of selecting a language for the system. 
         FIGS. 48   a - 48   b  is a flow chart and schematic illustration of an exemplary embodiment of a method of displaying a system version for the system. 
         FIGS. 49   a - 49   c  is a flow chart and schematic illustration of an exemplary embodiment of a method of replicating a configuration of the system. 
         FIGS. 50   a - 50   c  is a flow chart and schematic illustration of an exemplary embodiment of a method of updating a configuration of the system. 
         FIGS. 51   a - 51   b  is a flow chart and schematic illustration of an exemplary embodiment of a method of editing an away group of the system. 
         FIG. 52  is a flow chart illustration of an exemplary embodiment of a method of activating an away group of the system. 
         FIG. 53  is a flow chart illustration of an exemplary embodiment of a method of deactivating an away group of the system. 
         FIG. 54  is a schematic illustration of an exemplary embodiment of a table top RF controller for the system. 
         FIG. 54   a  is a front view illustration of an exemplary embodiment of the housing of the table top radio frequency controller. 
         FIG. 55  is a schematic illustration of an exemplary embodiment of a wall mount RF controller for the system. 
         FIG. 55   a  is a front view illustration of an exemplary embodiment of the installation of the wall mount RF controller. 
         FIG. 56  is a schematic illustration of an exemplary embodiment of a USB RF controller for the system. 
         FIG. 57  is a schematic illustration of an exemplary embodiment of an RF switch for the system. 
         FIG. 57   a  is a perspective illustration of an exemplary embodiment of the RF switch. 
         FIG. 58  is a schematic illustration of an exemplary embodiment of the controller of the RF switch. 
         FIG. 59  is a schematic illustration of an exemplary embodiment of the state engine of the controller of the RF switch. 
         FIG. 60  is a schematic illustration of an exemplary embodiment of the memory of the RF switch. 
         FIG. 61  is a schematic illustration of an exemplary embodiment of the device database of the memory of the RF switch. 
         FIG. 62  is a flow chart illustration of an exemplary embodiment of a method of installation for the RF switch. 
         FIG. 63  is a flow chart illustration of an exemplary embodiment of a method of change of state for the RF switch. 
         FIGS. 64   a  and  64   b  is a flow chart and schematic illustration of an exemplary embodiment of a method of association for the RF switch. 
         FIG. 65  is a flow chart illustration of an exemplary embodiment of a method of child protection for the RF switch. 
         FIGS. 66   a  to  66   c  is a flow chart illustration of an exemplary embodiment of a method of delayed off for the RF switch. 
         FIGS. 67   a  and  67   b  is a flow chart illustration of an exemplary embodiment of a method of panic mode for the RF switch. 
         FIG. 68  is a flow chart illustration of an exemplary embodiment of a method of loss of power detection for the RF switch. 
         FIG. 69  is a schematic illustration of an exemplary embodiment of an RF receptacle for the system. 
         FIG. 69   a  is a perspective illustration of an exemplary embodiment of the RF receptacle. 
         FIG. 70  is a schematic illustration of an exemplary embodiment of the controller of the RF receptacle. 
         FIG. 71  is a schematic illustration of an exemplary embodiment of the state engine of the controller of the RF receptacle. 
         FIG. 72  is a schematic illustration of an exemplary embodiment of the memory of the RF receptacle. 
         FIG. 73  is a schematic illustration of an exemplary embodiment of the device database of the memory of the RF receptacle. 
         FIG. 74  is a flow chart illustration of an exemplary embodiment of a method of installation for the RF receptacle. 
         FIG. 75  is a flow chart illustration of an exemplary embodiment of a method of turning on the RF receptacle. 
         FIG. 76  is a flow chart illustration of an exemplary embodiment of a method of change of state for the RF receptacle. 
         FIGS. 77   a  and  77   b  is a flow chart and schematic illustration of an exemplary embodiment of a method of association for the RF receptacle. 
         FIG. 78  is a flow chart illustration of an exemplary embodiment of a method of child protection for the RF receptacle. 
         FIGS. 79   a  to  79   c  is a flow chart illustration of an exemplary embodiment of a method of delayed off for the RF receptacle. 
         FIGS. 80   a  and  80   b  is a flow chart illustration of an exemplary embodiment of a method of panic mode for the RF receptacle. 
         FIG. 81  is a flow chart illustration of an exemplary embodiment of a method of loss of power detection for the RF receptacle. 
         FIG. 82  is a schematic illustration of an exemplary embodiment of an RF smart dimmer for the system. 
         FIG. 82   a  is a perspective illustration of an exemplary embodiment of the RF smart dimmer. 
         FIG. 83  is a schematic illustration of an exemplary embodiment of the controller of the RF smart dimmer. 
         FIG. 84  is a schematic illustration of an exemplary embodiment of the state engine of the controller of the RF smart dimmer. 
         FIG. 85  is a schematic illustration of an exemplary embodiment of the memory of the RF smart dimmer. 
         FIG. 86  is a schematic illustration of an exemplary embodiment of the device database of the memory of the RF smart dimmer. 
         FIG. 87  is a flow chart illustration of an exemplary embodiment of a method of installation for the RF smart dimmer. 
         FIG. 88  is a flow chart illustration of an exemplary embodiment of a method of operating the RF smart dimmer. 
         FIGS. 89   a - 89   b  is a flow chart illustration of an exemplary embodiment of a method of operating the RF smart dimmer. 
         FIGS. 90   a  and  90   b  is a flow chart of an exemplary embodiment of a method of operating the RF smart dimmer. 
         FIG. 91  is a flow chart of an exemplary embodiment of a method of operating the RF smart dimmer. 
         FIGS. 92   a  to  92   c  is a flow chart illustration of an exemplary embodiment of a method of delayed off for the RF smart dimmer. 
         FIGS. 93   a  and  93   b  is a flow chart and schematic illustration of an exemplary embodiment of a method of association for the RF smart dimmer. 
         FIG. 94  is a flow chart illustration of an exemplary embodiment of a method of child protection for the RF smart dimmer. 
         FIGS. 95   a  and  95   b  is a flow chart illustration of an exemplary embodiment of a method of panic mode for the RF smart dimmer. 
         FIG. 96  is a flow chart illustration of an exemplary embodiment of a method of loss of power detection for the RF smart dimmer. 
         FIG. 97  is a schematic illustration of an exemplary embodiment of a battery powered RF switch for the system. 
         FIG. 98  is a schematic illustration of an exemplary embodiment of the controller of the battery powered RF switch. 
         FIG. 99  is a schematic illustration of an exemplary embodiment of the state engine of the controller of the battery powered RF switch. 
         FIG. 100  is a schematic illustration of an exemplary embodiment of the memory of the battery powered RF switch. 
         FIG. 101  is a schematic illustration of an exemplary embodiment of the device database of the memory of the battery powered RF switch. 
         FIG. 102  is a flow chart illustration of an exemplary embodiment of a method of installation for the battery powered RF switch. 
         FIG. 103  is a flow chart illustration of an exemplary embodiment of a method of change of state for the battery powered RF switch. 
         FIGS. 104   a  and  104   b  is a flow chart and schematic illustration of an exemplary embodiment of a method of association for the battery powered RF switch. 
         FIG. 105  is a flow chart illustration of an exemplary embodiment of a method of child protection for the battery powered RF switch. 
         FIGS. 106   a  to  106   c  is a flow chart illustration of an exemplary embodiment of a method of delayed off for the battery powered RF switch. 
         FIGS. 107   a  and  107   b  is a flow chart illustration of an exemplary embodiment of a method of panic mode for the battery powered RF switch. 
         FIG. 108  is a flow chart illustration of an exemplary embodiment of a method of loss of power detection for the battery powered RF switch. 
         FIG. 109  is a schematic illustration of an exemplary embodiment of an RF dimmer for the system. 
         FIG. 109   a  is an illustration of an exemplary embodiment of an RF dimmer. 
         FIG. 110  is a schematic illustration of an exemplary embodiment of the controller of the RF dimmer. 
         FIG. 111  is a schematic illustration of an exemplary embodiment of the state engine of the controller of the RF dimmer. 
         FIG. 112  is a schematic illustration of an exemplary embodiment of the memory of the RF dimmer. 
         FIG. 113  is a schematic illustration of an exemplary embodiment of the device database of the memory of the RF dimmer. 
         FIG. 114  is a flow chart illustration of an exemplary embodiment of a method of installation for the RF dimmer. 
         FIG. 115  is a flow chart illustration of an exemplary embodiment of a method of operating the RF dimmer. 
         FIG. 116  is a flow chart illustration of an exemplary embodiment of a method of operating the RF dimmer. 
         FIGS. 117   a  to  117   c  is a flow chart illustration of an exemplary embodiment of a method of delayed off for the RF dimmer. 
         FIGS. 118   a  and  118   b  is a flow chart and schematic illustration of an exemplary embodiment of a method of association for the RF dimmer. 
         FIG. 119  is a flow chart illustration of an exemplary embodiment of a method of child protection for the RF dimmer. 
         FIGS. 120   a  and  120   b  is a flow chart illustration of an exemplary embodiment of a method of panic mode for the RF dimmer. 
         FIG. 121  is a flow chart illustration of an exemplary embodiment of a method of loss of power detection for the RF dimmer. 
         FIG. 122  is a schematic illustration of an exemplary embodiment of an RF thermostat. 
         FIG. 123  is a schematic illustration of an exemplary embodiment of a control system. 
         FIG. 124  is a schematic illustration of the system of  FIG. 123 . 
         FIG. 125  is a graphical illustration of an exemplary embodiment of the operation of the system of  FIG. 123 . 
         FIG. 126  is an illustration of an exemplary embodiment of a battery powered RF switch. 
         FIG. 127  is an exploded view of the battery powered RF switch of  FIG. 126 . 
         FIG. 128  is an exploded view of an exemplary embodiment of a method of mounting the battery powered RF switch of  FIG. 126  on a surface. 
         FIG. 129  is an illustration of an exemplary embodiment of the battery powered RF switch of  FIG. 126  mounted onto a surface. 
         FIG. 130  is an exploded view of an exemplary embodiment of a method of mounting the battery powered RF switch of  FIG. 126  on a surface. 
         FIG. 131  is an illustration of an exemplary embodiment of the battery powered RF switch of  FIG. 130  mounted onto a surface. 
         FIG. 132  is an exploded view of an exemplary embodiment of a method of mounting the battery powered RF switch of  FIG. 126  on a surface. 
         FIG. 133  is an illustration of an exemplary embodiment of the battery powered RF switch of  FIG. 132  mounted onto a surface. 
         FIGS. 134   a - 134   b  is a flow chart illustration of an exemplary embodiment of a method of associating devices in the system. 
     
    
    
     DETAILED DESCRIPTION 
     Referring now to  FIG. 1 , a control system  100  includes one or more master nodes  102  that are adapted to control and monitor the operation of one or more slave nodes  104 . In an exemplary embodiment, the master nodes  102  and the slave nodes  104  are operably coupled by one or more communication interfaces  106  that may, for example, include one or more of the following: radio frequency (RF), Internet Protocol (IP), power line, or other conventional communication interfaces. 
     Referring now to  FIG. 2 , in an exemplary embodiment, the master nodes  102  may include one or more of the following: a hand held RF controller  202 , a table top RF controller  204 , a wall mounted RF controller  206 , and/or a Universal Serial Bus (USB) RF Controller  208 . 
     Referring now to  FIG. 3 , in an exemplary embodiment, the slave nodes  104  may include one or more of the following: an RF switch  302 , an RF receptacle  304 , an RF smart dimmer  306 , a battery operated RF switch  308 , an RF dimmer  310 , and a thermostat device  312 . 
     Referring now to  FIG. 4 , in an exemplary embodiment, the hand held RF controller  202  includes a controller  402  that is operably coupled to an RF transceiver  404 , a memory  406 , a network interface  408 , a keypad  410 , a user interface  412 , a display  414 , and a battery  416 . 
     In an exemplary embodiment, the controller  402  is adapted to control and monitor the operation of the RF transceiver  404 , the memory  406 , the network interface  408 , the keypad  410 , the user interface  412 , the display  414 , and the battery  416 . In an exemplary embodiment, the controller  402  includes one or more of the following: a conventional programmable general purpose controller, an application specific integrated circuit (ASIC), or other conventional controller devices. In an exemplary embodiment, the controller  402  includes a model ZW0201 controller, commercially available from Zensys A/S. 
     Referring now to  FIG. 5 , in an exemplary embodiment, the controller  402  includes an operating system  502 , application programs  504 , and a boot loader  506 . In an exemplary embodiment, the operating system  502  includes a serial communications driver  502   a , a memory driver  502   b , a display driver  502   c , and a button input driver  502   d . In an exemplary embodiment, the serial communications driver  502   a  controls serial communications using the RF serial transceiver  404 , the memory driver  502   b  controls the memory  406 , the display driver  502   c  controls the generation of all text and graphics on the display  414 , and the button input driver  502   d  debounces button inputs provided by a user using the keypad  410 . In an exemplary embodiment, the serial communications driver  502   a  includes a Z-Wave™ serial API driver that implements a Z-Wave™ serial API protocol. The Z-Wave™ serial API driver that implements a Z-Wave™ serial API protocol are both commercially available from Zensys A/S. 
     In an exemplary embodiment, the application programs  504  include a menu-state engine  504   a . In an exemplary embodiment, the menu-state engine  504   a  permits an operator of the hand held RF controller  202  to customize the operation of the system  100 . 
     Referring now to  FIG. 6 , in an exemplary embodiment, the menu state engine  504   a  includes a device engine  602   a , a scenes engine  602   b , an events engine  602   c , a system engine  602   d , and an away engine  603   e.    
     In an exemplary embodiment, the device engine  602   a  permits the operator of the hand held RF controller  202  to customize the operation of at least some of the aspects of the master and slave nodes,  102  and  104 , respectively. In an exemplary embodiment, the device engine  602   a  includes a device install engine  602   aa , a device associate engine  602   ab , a device uninstall engine  602   ac , a device remove engine  602   ad , a device replace engine  602   ae , a device control engine  602   af , a device child protection engine  602   ag , a device rename engine  602   ah , a device configure engine  602   ai , a device version engine  602   aj , and a device all switch engine  602   ak.    
     In an exemplary embodiment, the device install engine  602   aa  permits an operator of the hand held RF controller  202  to install one or more master and/or slave nodes,  102  and  104 , respectively, into the system  100 . In an exemplary embodiment, as illustrated in  FIG. 7 , the device associate engine  602   ab  permits the operator of the hand held RF controller  202  to associate one or more master and/or slave nodes,  102  and  104 , with one another to thereby define a communication pathway  702  that includes the associated nodes, e.g.,  704   a  and  704   b . As a result, communications between a source node  706  and a destination node  708  within the system  100  may employ the defined pathway  702 . 
     In an exemplary embodiment, the device uninstall engine  602   ac  permits an operator of the hand held RF controller  202  to uninstall one or more master and/or slave nodes,  102  and  104 , respectively, out of the system  100 . In an exemplary embodiment, the device remove engine  602   ad  permits an operator of the hand held RF controller  202  to remove one or more master and/or slave nodes,  102  and  104 , respectively, from the system  100 . 
     In an exemplary embodiment, the device replace engine  602   ae  permits an operator of the hand held RF controller  202  to replace one or more master and/or slave nodes,  102  and  104 , respectively, with other master and/or slave nodes in the system  100 . In an exemplary embodiment, the device control engine  602   af  permits an operator of the hand held RF controller  202  to control one or more master and/or slave nodes,  102  and  104 , respectively, in the system  100 . 
     In an exemplary embodiment, the device child protection engine  602   ag  permits an operator of the hand held RF controller  202  to define the level of child protection for one or more master and/or slave nodes,  102  and  104 , respectively, in the system  100 . In an exemplary embodiment, the device rename engine  602   ah  permits an operator of the hand held RF controller  202  to rename one or more master and/or slave nodes,  102  and  104 , respectively, in the system  100 . 
     In an exemplary embodiment, the device configure engine  602   ai  permits an operator of the hand held RF controller  202  to configure one or more master and/or slave nodes,  102  and  104 , respectively, in the system  100 . In an exemplary embodiment, the device version engine  602   aj , permits an operator of the hand held RF controller  202  to determine and/or configure the version of one or more master and/or slave nodes,  102  and  104 , respectively, in the system  100 . 
     In an exemplary embodiment, the device all switch engine  602   ak  permits an operator of the hand held RF controller  202  to define and configure the operation of the master and/or slave nodes,  102  and  104 , respectively, to be included in an all switch group defined within the system  100 . 
     In an exemplary embodiment, as illustrated in  FIG. 8 , the scenes engine  602   b  permits the operator of the hand held RF controller  202  to customize, define, and otherwise control the operation of one or more scenes, e.g.,  802   a - 802   f , using one or more of the slave nodes  102  in the system  100 . In an exemplary embodiment, as illustrated in  FIG. 9 , each scene  802  defines the operating states, e.g.,  904   a - 904   f  one or more corresponding slave nodes  102   a - 102   f , in the system  100 . 
     In an exemplary embodiment, the scenes engine  602   b  includes a scenes create engine  602   ba , a scenes delete engine  602   bb , a scenes edit engine  602   bc , a scenes activate engine  602   bd , and a scenes deactivate engine  602   be.    
     In an exemplary embodiment, the scenes create engine  602   ba  permits an operator of the hand held RF controller  202  to create one or more scenes  802  in the system  100 . In an exemplary embodiment, the scenes delete engine  602   bb  permits an operator of the hand held RF controller  202  to delete one or more scenes  802  from the system  100 . 
     In an exemplary embodiment, the scenes edit engine  602   bc  permits an operator of the hand held RF controller  202  to edit one or more scenes  802  in the system  100 . In an exemplary embodiment, the scenes activate engine  602   bd  permits an operator of the hand held RF controller  202  to activate one or more scenes  802  in the system  100 . In an exemplary embodiment, the scenes deactivate engine  602   be  permits an operator of the hand held RF controller  202  to deactivate one or more scenes  802  in the system  100 . 
     In an exemplary embodiment, as illustrated in  FIG. 10 , the events engine  602   c  permits the operator of the hand held RF controller  202  to customize, define, and otherwise control the operation of one or more events, e.g.,  1002   a - 1002   d , using one or more of the slave nodes  102  in the system  100 . In an exemplary embodiment, as illustrated in  FIG. 11 , each event  1002  includes a time of occurrence  1102 , a day of occurrence  1104 , an event type  1106 , the scene to be used in the event  1108 , and whether the event is active or inactive  1110 . 
     In an exemplary embodiment, the events engine  602   c  includes an events create engine  602   ca , an events delete engine  602   cb , an events edit engine  602   cc , an events activate engine  602   cd , and an events deactivate engine  602   ce.    
     In an exemplary embodiment, the events create engine  602   ca  permits an operator of the hand held RF controller  202  to create one or more events  1002  in the system  100 . In an exemplary embodiment, the events delete engine  602   cb  permits an operator of the hand held RF controller  202  to delete one or more events  1002  from the system  100 . 
     In an exemplary embodiment, the events edit engine  602   cc  permits an operator of the hand held RF controller  202  to edit one or more events  1002  in the system  100 . In an exemplary embodiment, the events activate engine  602   cd  permits an operator of the hand held RF controller  202  to activate one or more events  1002  in the system  100 . In an exemplary embodiment, the events deactivate engine  602   ce  permits an operator of the hand held RF controller  202  to deactivate one or more events  1002  in the system  100 . 
     In an exemplary embodiment, the system engine  602   d  includes a system date/time engine  602   da , a system panic engine  602   db , a system language engine  602   dc , a system version engine  602   dd , a system replicate engine  602   de , and a system update engine  602   df.    
     In an exemplary embodiment, the system date/time engine  602   da  permits an operator of the hand held RF controller  202  to enter and/or edit the date and time of the system  100 . 
     In an exemplary embodiment, as illustrated in  FIG. 12 , the system panic engine  602   db  permits an operator of the hand held RF controller  202  to define a panic group  1202  within the system  100 . In an exemplary embodiment, as illustrated in  FIG. 13 , the panic group  1202  includes one or more slave nodes  104  and corresponding panic modes of operation  1302  for each of the slave nodes included in the panic group  1202 . 
     In an exemplary embodiment, the system language engine  602   dc  permits an operator of the hand held RF controller  202  to define the language to be used in the system  100 . In an exemplary embodiment, the system version engine  602   dd  permits an operator of the hand held RF controller  202  to view the system version of the system  100  on, for example, the display  414 . 
     In an exemplary embodiment, the system replicate engine  602   de  permits an operator of the hand held RF controller  202  to replicate one or more aspects of the hand held RF controller into another master node  102  to be used in the system  100 . In an exemplary embodiment, the system update engine  602   df  permits an operator of the hand held RF controller  202  to update one or more aspects of the operating system  502  or application programs  504  to be used in the system  100 . 
     In an exemplary embodiment, as illustrated in  FIG. 14 , the away engine  602   e  permits an operator of the hand held RF controller  202  to define an away group  1402  within the system  100 . In an exemplary embodiment, as illustrated in  FIG. 15 , the away group  1402  includes one or more slave nodes  104  and corresponding away modes of operation  1502  for each of the slave nodes included in the away group  1402 . 
     In an exemplary embodiment, the away engine  602   e  includes an away group edit engine  602   ea , an away group activate engine  602   eb , and an away group deactivate engine  602   ec.    
     In an exemplary embodiment, the away group edit engine  602   ea  permits an operator of the hand held RF controller  202  to edit one or more aspects of the away group  1402  to be used in the system  100 . In an exemplary embodiment, the away group activate engine  602   eb  permits an operator of the hand held RF controller  202  to activate one or more aspects of the away group  1402  used in the system  100 . In an exemplary embodiment, the away group deactivate engine  602   ec  permits an operator of the hand held RF controller  202  to deactivate one or more aspects of the away group  1402  used in the system  100 . 
     In an exemplary embodiment, the RF transceiver  404  is operably coupled to and controlled by the controller  402 . In an exemplary embodiment, the RF transceiver  404  transmits and receives RF communications to and from other master and slave nodes,  102  and  104 , respectively. In an exemplary embodiment, the RF transceiver  404  may, for example, include one or more of the following: a conventional RF transceiver, and/or the model ZW0201 RF transceiver commercially available from Zensys A/S. 
     In an exemplary embodiment, the memory  406  is operably coupled to and controlled by the controller  402 . In an exemplary embodiment, as illustrated in  FIG. 16 , the memory  406  includes a copy of the operating system  1602 , a copy of the application programs  1604 , a devices database  1606 , scenes database  1608 , an events database  1610 , a system database  1612 , an away database  1614 , a communications pathway database  1616 , and a failed node ID listing  1618 . In an exemplary embodiment, the memory  406  includes a model 24LC256 non volatile memory, commercially available from Microchip. 
     In an exemplary embodiment, as illustrated in  FIGS. 17 and 18 , the devices database  1606  includes a node information frame  1702  for each of the nodes in the system  100  that each include a generic device class  1802 , a specific device class  1804 , a command class  1806 , a protection command class  1808 , a version command class  1810 , a manufacturing proprietary command class  1810 , and an all switch command class  1812 . In an exemplary embodiment, the devices database  1606  includes database information used by at least the devices engine  602   a.    
     In an exemplary embodiment, the scenes database  1608  includes database information used by at least the scenes engine  602   b . In an exemplary embodiment, the events database  1610  includes database information used by at least the events engine  602   c . In an exemplary embodiment, the system database  1612  includes database information used by at least the system engine  602   d . In an exemplary embodiment, the away database  1614  includes database information used by at least the away engine  602   e.    
     In an exemplary embodiment, the communications pathway database  1616  includes database information regarding the communication pathways  702 , and the failed node ID listing  1618  includes information regarding the master and slave nodes,  102  and  104 , respectively, that have failed in the system  100 . 
     In an exemplary embodiment, the network interface  408  is operably coupled to and controlled and monitored by the controller  402 . In an exemplary embodiment, the network interface  408  permits the hand held RF controller  202  to communicate with external devices via conventional communication interfaces such as, for example, internet protocol. 
     In an exemplary embodiment, the keypad  410  is operably coupled to and controlled and monitored by the controller  402 . In an exemplary embodiment, the keypad  410  permits a user of the hand held RF controller  202  to input information into the controller to thereby control the operation of the controller. In an exemplary embodiment, as illustrated in  FIG. 19 , the keypad  410  includes an alpha-numeric keypad  1902 , navigation buttons  1904 , an OK button  1906 , a BACK button  1908 , one or more user programmable HOT BUTTONS  1910 , ON button  1912   a , OFF button  1912   b , a PANIC button  1914 , and one or more user programmable MENU KEYS  1916 . 
     In an exemplary embodiment, the user interface  412  is operably coupled to and controlled and monitored by the controller  402 . In an exemplary embodiment, the user interface  412  permits a user of the hand held RF controller  202  to interface with the controller to thereby monitor and control the operation of the controller. 
     In an exemplary embodiment, the display  414  is operably coupled to and controlled and monitored by the controller  402 . In an exemplary embodiment, the display  414  permits a user of the hand held RF controller  202  to interface with the controller to thereby monitor and control the operation of the controller. In an exemplary embodiment, the display  414  includes a model JCM13064D display, commercially available from Jinghua. 
     In an exemplary embodiment, the battery  416  provides electrical power for and is operably coupled to all of the elements of the hand held RF controller  202 . 
     In an exemplary embodiment, as illustrated in  FIGS. 19   a  and  19   b , the elements of the hand held RF controller  202  may be positioned within and supported by a housing  1920  having a cover  1922  that defines one or more openings for the keypad  410 , including one or more of the alpha-numeric keypad  1902 , the navigation buttons  1904 , the OK button  1906 , the BACK button  1908 , the ALL ON button  1912   a , the ALL OFF button  1912   b , the PANIC button  1914 , and the MENU keys  1916 , and the display  414 . 
     Referring now to  FIG. 20 , in an exemplary embodiment, during the operation of the hand held RF controller  202 , the controller implements a menu-based program  2000  having a main menu  2002  in which a user of the hand held RF controller may initially select: DEVICES  2004 , SCENES  2006 , EVENTS  2008 , SYSTEM  2010 , or AWAY  2012  using the keypad  410 . 
     In an exemplary embodiment, user selection of DEVICES  2004  permits the user to control, monitor and/or configure one or more aspects of the master and slave nodes,  102  and  104 , respectively of the system  100  using the device engine  602   a . In an exemplary embodiment, user selection of SCENES  2006  permits the user to control, monitor, and/or configure one or more aspects of the scenes  802  of the system  100  using the scenes engine  602   b . In an exemplary embodiment, user selection of EVENTS  2008  permits the user to control, monitor, and/or configure one or more aspects of the events  1002  of the system  100  using the event engine  602   c . In an exemplary embodiment, user selection of SYSTEM  2010  permits the user to control, monitor, and/or configure one or more aspects of the system  100  using the system engine  602   d . In an exemplary embodiment, user selection of AWAY  2012  permits the user to control, monitor, and/or configure one or more aspects of the away group  1402  of the system  100  using the away engine  602   e.    
     After selecting DEVICES  2004 , the user of the hand held RF controller  202  may then select: INSTALL  2004   a , ASSOCIATE  2004   b , UNINSTALL  2004   c , REMOVE  2004   d , REPLACE  2004   e , CONTROL  2004   f , CHILD PROTECTION  2004   g , RENAME  2004   h , CON FIGURE 2004   i , VERSION  2004   j , or ALL SWITCH  2004   k . In an exemplary embodiment, user selection of: a) INSTALL  2004   a , b) ASSOCIATE  2004   b , c) UNINSTALL  2004   c , d) REMOVE  2004   d , e) REPLACE  2004   e , f) CONTROL  2004   f , g) CHILD PROTECTION  2004   g , h) RENAME  2004   h , i) CON FIGURE 2004   i , j) VERSION  2004   j , or  k ) ALL SWITCH  2004   k  permits the user to control, monitor, and/or configure one or more aspects of: a) the installation of master and/or slave nodes,  102  and  104 , respectively; b) the association of slave nodes; c) the uninstallation of master and/or slave nodes; d) the removal of master and/or slave nodes; e) the replacement of master and/or slave nodes; f) the control of master and/or slave nodes; g) child protection for master and/or slave nodes; h) renaming master and/or slave nodes; i) configuring master and/or slave nodes; j) controlling, editing, and monitoring the version of master and/or slave nodes; or k) configuring and controlling the slave nodes in the all switch group, respectively, in the system  100  using the devices engine  602   a.    
     After selecting SCENES  2006 , the user of the hand held RF controller  202  may then select: CREATE  2006   a , DELETE  2006   b , EDIT  2006   c , ACTIVATE  2006   d , or DEACTIVATE  2006   e . In an exemplary embodiment, user selection of a) CREATE  2006   a , b) DELETE  2006   b , c) EDIT  2006   c , d) ACTIVATE  2006   d , or  e ) DEACTIVATE  2006   e  permits the user to control, monitor, and/or configure one or more aspects of: a) creating scenes  802 ; b) deleting scenes; c) editing scenes; d) activating scenes; or e) deactivating scenes, respectively, in the system  100  using the scenes engine  602   b.    
     After selecting EVENTS  2008 , the user of the hand held RF controller  202  may then select: CREATE  2008   a , DELETE  2008   b , EDIT  2008   c , ACTIVATE  2008   d , or DEACTIVATE  2008   e . In an exemplary embodiment, user selection of a) CREATE  2008   a , b) DELETE  2008   b , c) EDIT  2008   c , d) ACTIVATE  2008   d , or  e ) DEACTIVATE  2008   e  permits the user to control, monitor, and/or configure one or more aspects of: a) creating events  1002 ; b) deleting events; c) editing events; d) activating events; or e) deactivating events, respectively, in the system  100  using the event engine  602   c.    
     After selecting SYSTEM  2010 , the user of the hand held RF controller  202  may then select: DATE/TIME  2010   a , PANIC  2010   b , LANGUAGE  2010   c , VERSION  2010   d , REPLICATE  2010   e , or UPDATE  2010   f . In an exemplary embodiment, user selection of a) DATE/TIME  2010   a , b) PANIC  2010   b , c) LANGUAGE  2010   c , d) VERSION  2010   d , e) REPLICATE  2010   e , or  f ) UPDATE  2010   f  permits the user to control, monitor, and/or configure one or more aspects of: a) the date and time for the system  100 ; b) the configuration and operation of the panic group  1202 ; c) the language used in the system; d) the version of one or more aspects of the system; e) replicating master and/or slave nodes, or f) updating one or more aspects of the system, respectively, in the system using the system engine  602   d.    
     After selecting AWAY  2012 , the user of the hand held RF controller  202  may then select: EDIT  2012   a , ACTIVATE  2012   b , or DEACTIVATE  2012   c . In an exemplary embodiment, user selection of a) EDIT  2012   a , b) ACTIVATE  2012   b , or  c ) DEACTIVATE  2012   c  permits the user to control, monitor, and/or configure one or more aspects of: a) the configuration and operation of the away group  1402 ; b) activation of the away group; or c) deactivation of the away group, respectively, in the system using the away engine  602   e.    
     Referring now to  FIG. 21 , in an exemplary embodiment, during the operation of the hand held RF controller  202 , the controller implements a method  2100  in which all of the slave nodes  104 , within a user defined all on/off group, may be turned on or off. In particular, in step  2102 , the controller  302  determines if the ON button  1912   a  has been depressed by the user. If the ON button  1912  has been depressed by the user, the controller  302  turns on all of the slave nodes  104  within the all on/off group in step  2104 . Alternatively, if the controller determines that the OFF button  1912   b  has been depressed by the user in step  2106 , then the controller  302  turns off all of the slave nodes  104  within the all on/off group in step  2108 . In this manner, the hand held RF controller  202  may control the operation of all of the slave nodes  104  included within the all on/off group. 
     Referring now to  FIGS. 22   a  and  22   b , in an exemplary embodiment, during the operation of the hand held RF controller  202 , the controller implements a method  2200  in which the controller determines if a numeric button has been depressed on the keypad  1902  by a user in step  2202 . If a numeric button has been depressed on the keypad  1902  by a user, then a device access display screen  2204  is displayed on the display  414  that includes a highlighted device  2206  that corresponds to the numeric button depressed highlighted in step  2208 . In this manner, the hand held RF controller  202  permits a user to quickly and efficiently select, view and/or edit the configuration and operational details for a particular master and slave node,  102  and  104 , respectively. 
     Referring now to  FIGS. 23   a  and  23   b , in an exemplary embodiment, during the operation of the hand held RF controller  202 , after highlighting a selected device using the method  2200 , the controller implements a method  2300  in which the controller determines if a highlighted device  2206  has been selected on the display  414  in step  2302 . If a highlighted device  2206  has been selected, the hand held RF controller  202  then determines if the ON or OFF buttons,  1912   a  or  1912   b , respectively, have been depressed on the keypad  410  by a user in step  2304 . If the ON or OFF buttons,  1912   a  or  1912   b , respectively, have been depressed on the keypad  410  by a user, then the hand held RF controller  202  then determines if the highlighted device  2206  supports on or off operational states in step  2306 . If the highlighted device  2206  does not support on or off operational states, then the hand held RF controller  202  prompts the user to enter a value for the desired operational state of the highlighted device  2206  in step  2308 . For example, if the highlighted device  2206  is a thermostat, the hand held RF controller  202  may prompt the user for the desired temperature setting and/or whether air conditioning or heating is desired. 
     Alternatively, if the highlighted device  2206  does support on or off operational states, then the hand held RF controller  202  determines if the highlighted device  2206  supports dimming or brightening operational states in step  2310 . If the highlighted device  2206  supports dimming or brightening operational states, then the hand held RF controller  202  determines if the ON or OFF button,  1912   a  or  1912   b , respectively, were depressed by a user for predetermined minimum time period in step  2312 . If the ON or OFF button,  1912   a  or  1912   b , respectively, were depressed by a user for predetermined minimum time period, then the hand held RF controller  202  brightens or dims the highlighted device  2206  in step  2314 . Alternatively, if the ON or OFF button,  1912   a  or  1912   b , respectively, were not depressed by a user for predetermined minimum time period, then the hand held RF controller  202  determines if the highlighted device  2206  permits a delay in turning the device on or off in step  2316 . If the highlighted device  2206  permits a delay in turning the device on or off, then the hand held RF controller  202  turns the device on or off with a predetermined time delay in step  2318 . Alternatively, if the highlighted device  2206  does not permit a delay in turning the device on or off, then the hand held RF controller  202  turns the device on or off without a predetermined time delay in step  2320 . 
     Alternatively, if the highlighted device  2206  does not support dimming or brightening operational states, then the hand held RF controller  202  determines if the highlighted device  2206  permits a delay in turning the device on or off in step  2322 . If the highlighted device  2206  permits a delay in turning the device on or off, then the hand held RF controller  202  turns the device on or off with a predetermined time delay in step  2324 . Alternatively, if the highlighted device  2206  does not permit a delay in turning the device on or off, then the hand held RF controller  202  turns the device on or off without a predetermined time delay in step  2326 . In this manner, the hand held RF controller  202  permits a user to quickly and efficiently control the operational state of a particular slave node  104 , and thereby control the operational state of the highlighted device  2206  by: a) turning the device on or off without a time delay; b) turning the device on or off with a time delay; or c) brighten or dim the device. 
     Referring now to  FIGS. 24   a - 24   c , in an exemplary embodiment, during the operation of the hand held RF controller  202 , after a user sequentially selects DEVICES  2004  and INSTALL  2004   a , using the menu-based program  2000 , the controller implements a method  2400  in which the controller permits a user to install one or more devices, such as, for example, master and slave nodes,  102  and  104 , respectively, in the system  100 . In particular, in step  2402  the hand held RF controller  202  determines if a user has selected the installation of a device in the system  100 . If the user has selected the installation of device in the system  100 , then the display  414  of the hand held RF controller  202  prompts the user to press the install button on the device to be installed in the system in step  2404 . Depression of the install button on the device to be installed in the system  100  will cause the device to be installed in the system to transmit the node information frame  1702  for the device to the hand held RF controller  202 . 
     If the node information frame  1702  for the device to be installed in the system  100  is received by the hand held RF controller  202  in step  2406 , then the controller will permit the installation of the device to proceed in step  2408 . As part of the installation of the device into the system  100 , the hand held RF controller  202  will also scan the node information frame  1702  for the device to be installed in the system  100  in step  2410 . 
     Alternatively, if the node information frame  1702  for the device to be installed in the system  100  is not received by the hand held RF controller  202  in step  2406 , then the controller will determine if the installation of the device has been canceled by the user in step  2412 . If the hand held RF controller  202  determines that the installation of the device has been canceled by the user, then the controller will display an installation cancellation message on the display  414  in step  2414 . If the hand held RF controller  202  determines that the installation of the device has not been canceled by the user in step  2412 , then the controller will determine if a predetermined timeout has occurred in step  2416 . If the hand held RF controller  202  determines that a predetermined timeout has occurred, then the controller will display an installation cancellation message on the display  414  in step  2414 . 
     If the hand held RF controller  202  determines that the installation of the device in steps  2408  and  2410  did not occur within a predetermined timeout in step  2418 , then the controller will display an installation cancellation message on the display  414  in step  2414 . Alternatively, if the hand held RF controller  202  determines that the installation of the device in steps  2408  and  2410  did occur within a predetermined timeout in step  2418 , then the controller will determine if the installed device can be a static controller by interrogating the node information frame  1702  for the installed device in step  2420 . 
     If the hand held RF controller  202  determines that the installed device can be a static controller in step  2420 , then the controller will determine if the installed device can be a system information server by interrogating the node information frame  1702  for the installed device in step  2422 . If the hand held RF controller  202  determines that the installed device can be a system information server in step  2422 , then the controller will designate the installed device as a system information server for the system  100  in step  2424 . When the installed device provides a system information server, it stores a record of the configuration and operational details of the system  100 . As a result, it provides an archival back-up record of the design and operation of the system  100 . 
     If: a) the hand held RF controller  202  determines that the installed device cannot be a static controller in step  2420 , b) the controller determines that the installed device cannot be a system information server in step  2422 , or c) after completing step  2424 , the controller determines if the installed device supports an all switch command class in step  2426 . If the hand held RF controller  202  determines that the installed device supports an all switch command class in step  2426 , then the controller adds the installed device to the away group  1402  in step  2428 . 
     Referring now to  FIGS. 25   a - 25   b , in an exemplary embodiment, during the operation of the hand held RF controller  202 , after a user sequentially selects DEVICES  2004  and ASSOCIATE  2004   b , using the menu-based program  2000 , the controller implements a method  2500  in which the controller permits a user to associate devices, such as, for example, master and slave nodes,  102  and  104 , respectively, to define a communication pathway  702  within the system  100 . In particular, in step  2502  the hand held RF controller  202  determines if a user has selected the association of a device in the system  100  with a communication pathway  702 . If the user has selected the association of device in the system  100  with a communication pathway  702 , then the display  414  of the hand held RF controller  202  prompts the user to press the associate button on the device to be designated as a destination node  708  within a communication pathway in the system in step  2504 . Depression of the associate button on the device to be designated as a destination node  708  within a communication pathway  702  in the system  100  will cause the device to transmit the node information frame  1702  for the device to the hand held RF controller  202 . 
     If the node information frame  1702  for the device to be designated as a destination node  708  within a communication pathway  702  in the system  100  is received by the hand held RF controller  202  in step  2506 , then the display  414  of the hand held RF controller  202  prompts the user to press the associate button on the device to be designated as a source node  706  within a communication pathway  702  in the system  100  in step  2508 . If the node information frame  1702  for the device to be designated as a source node  706  within a communication pathway  702  in the system  100  is received by the hand held RF controller  202  in step  2510 , then the sequentially associated nodes are associated with one another in the communication pathway  702  and designated as destination and source nodes,  708  and  706 , respectively, in step  2512 . 
     Alternatively, if the node information frame  1702  for the device to be designated as a destination node  708  within the communication pathway  702  in the system  100  is not received by the hand held RF controller  202  in step  2506 , then the controller determines if a user has cancelled the association in step  2514 . If the hand held RF controller  202  determines that a user has cancelled the association, then the association is cancelled in step  2516 . 
     Referring now to  FIGS. 26   a - 26   b , in an exemplary embodiment, during the operation of the hand held RF controller  202 , after a user sequentially selects DEVICES  2004  and UNINSTALL  2004   c , using the menu-based program  2000 , the controller implements a method  2600  in which the controller permits a user to uninstall one or more devices, such as, for example, master and slave nodes,  102  and  104 , respectively, from the system  100 . In particular, in step  2602  the hand held RF controller  202  determines if a user has selected the uninstallation of a device from the system  100 . If the user has selected the uninstallation of device from the system  100 , then the display  414  of the hand held RF controller  202  prompts the user to press the uninstall button on the device to be uninstalled from the system in step  2604 . Depression of the uninstall button on the device to be uninstalled in the system  100  will cause the device to be uninstalled in the system to transmit the node information frame  1702  for the device to the hand held RF controller  202 . 
     If the node information frame  1702  for the device to be uninstalled in the system  100  is received by the hand held RF controller  202  in step  2606 , then the controller will permit the uninstallation of the device from the system  100  to proceed in step  2608 . 
     Alternatively, if the node information frame  1702  for the device to be uninstalled from the system  100  is not received by the hand held RF controller  202  in step  2606 , then the controller will determine if the uninstallation of the device has been canceled by the user in step  2610 . If the hand held RF controller  202  determines that the uninstallation of the device has been canceled by the user, then the controller will cancel the uninstallation in step  2612 . If the hand held RF controller  202  determines that the uninstallation of the device has not been canceled by the user in step  2610 , then the controller will determine if a predetermined timeout has occurred in step  2614 . If the hand held RF controller  202  determines that a predetermined timeout has occurred, then the controller will cancel the uninstallation in step  2612 . 
     If the hand held RF controller  202  determines that the uninstallation of the device in steps  2606  and  2608  did not occur within a predetermined timeout in step  2616 , then the controller will cancel the uninstallation in step  2612 . Alternatively, if the hand held RF controller  202  determines that the uninstallation of the device in steps  2606  and  2608  did occur within a predetermined timeout in step  2616 , then the controller will uninstall the device from the system  100  in step  2618 . 
     Referring now to  FIG. 27 , in an exemplary embodiment, during the operation of the hand held RF controller  202 , after a user sequentially selects DEVICES  2004  and REMOVE  2004   d , using the menu-based program  2000 , the controller implements a method  2600  in which the controller permits a user to remove one or more devices, such as, for example, master and slave nodes,  102  and  104 , respectively, from the system  100 . In particular, in step  2702  the hand held RF controller  202  determines if a user has selected the removal of a device from the system  100 . If the user has selected the removal of device from the system  100 , then the display  414  of the hand held RF controller  202  prompts the user to select the device to be removed from the system in step  2704 . 
     If the hand held RF controller  202  determines that the device selected by a user for removal from the system  100  is listed in the failed node ID listing  1618  in step  2706 , then the device is removed from the system in step  2708 . Alternatively, if the hand held RF controller  202  determines that the device selected by a user for removal from the system  100  is not listed in the failed node ID listing  1618  in step  2706 , then the removal of the device is canceled in step  2710 . 
     Referring now to  FIGS. 28   a - 28   d , in an exemplary embodiment, during the operation of the hand held RF controller  202 , after a user sequentially selects DEVICES  2004  and REPLACE  2004   e , using the menu-based program  2000 , the controller implements a method  2800  in which the controller permits a user to replace one or more devices, such as, for example, master and slave nodes,  102  and  104 , respectively, with one or more other devices, such as, for example, master and slave nodes,  102  and  104 , respectively, within the system  100 . In particular, in step  2802  the hand held RF controller  202  determines if a user has selected the replacement of a device within the system  100 . If the user has selected the replacement of device within the system  100 , then the display  414  of the hand held RF controller  202  prompts the user to select the device to be replaced within the system in step  2804 . 
     If the hand held RF controller  202  determines that the device selected by a user for replacement within the system  100  is listed in the failed node ID listing  1618  in step  2806 , then the device may be replaced within the system in step  2808 . Alternatively, if the hand held RF controller  202  determines that the device selected by a user for replacement within the system  100  is not listed in the failed node ID listing  1618  in step  2806 , then the replacement of the device is canceled in step  2810 . 
     If the device may be replaced within the system in step  2808 , then the display  414  of the hand held RF controller  202  prompts the user to press the install button on the replacement device to be installed in the system in step  2812 . Depression of the install button on the replacement device to be installed in the system  100  will cause the replacement device to be installed in the system to transmit the node information frame  1702  for the device to the hand held RF controller  202 . 
     If the node information frame  1702  for the replacement device to be installed in the system  100  is received by the hand held RF controller  202  in step  2814 , then the controller will permit the installation of the replacement device to proceed in step  2816 . As part of the installation of the device into the system  100 , the hand held RF controller  202  will also scan the node information frame  1702  for the replacement device to be installed in the system  100  in step  2818 . 
     Alternatively, if the node information frame  1702  for the replacement device to be installed in the system  100  is not received by the hand held RF controller  202  in step  2814 , then the controller will determine if the installation of the replacement device has been canceled by a user in step  2820 . If the hand held RF controller  202  determines that the installation of the replacement device has been canceled by a user, then the controller will cancel the replacement in step  2822 . If the hand held RF controller  202  determines that the installation of the replacement device has not been canceled by a user in step  2820 , then the controller will determine if a predetermined timeout has occurred in step  2824 . If the hand held RF controller  202  determines that a predetermined timeout has occurred, then the controller will cancel the replacement in step  2822 . 
     If the hand held RF controller  202  determines that the installation of the replacement device in steps  2816  and  2818  did not occur within a predetermined timeout in step  2826 , then the controller will cancel the replacement in step  2822 . Alternatively, if the hand held RF controller  202  determines that the installation of the replacement device in steps  2816  and  2818  did occur within a predetermined timeout in step  2826 , then the controller will determine if the installed replacement device can be a static controller by interrogating the node information frame  1702  for the installed replacement device in step  2828 . 
     If the hand held RF controller  202  determines that the installed replacement device can be a static controller in step  2828 , then the controller will determine if the installed device can be a system information server by interrogating the node information frame  1702  for the installed replacement device in step  2830 . If the hand held RF controller  202  determines that the installed replacement device can be a system information server in step  2830 , then the controller will designate the installed replacement device as a system information server for the system  100  in step  2832 . When the installed replacement device provides a system information server, it stores a record of the configuration and operational details of the system  100 . As a result, it provides an archival back-up record of the design and operation of the system  100 . 
     If: a) the hand held RF controller  202  determines that the installed replacement device cannot be a static controller in step  2828 , b) the controller determines that the installed replacement device cannot be a system information server in step  2830 , or c) after completing step  2832 , the controller determines if the installed replacement device supports an all switch command class in step  2834 . If the hand held RF controller  202  determines that the installed replacement device supports an all switch command class in step  2834 , then the controller adds the installed replacement device to the away group  1402  in step  2836 . 
     Referring now to  FIGS. 29   a - 29   b , in an exemplary embodiment, during the operation of the hand held RF controller  202 , after a user sequentially selects DEVICES  2004  and CONTROL  2004   f , using the menu-based program  2000 , the controller implements a method  2900  in which the controller permits a user to control one or more devices, such as, for example, master and slave nodes,  102  and  104 , respectively, within the system  100 . In particular, in step  2902  the hand held RF controller  202  determines if a user has selected the control of a device within the system  100 . If the user has selected the control of a device within the system  100 , then the display  414  of the hand held RF controller  202  prompts the user to select the device to be controlled within the system in step  2904 . 
     Once a user of the hand held RF controller  202  has selected the device to be controlled, the node data for the selected device is then retrieved by the controller. In and exemplary embodiment, the node data for the selected device includes the node information frame  1702  for the selected device. If the node data for the selected device is retrieved by the hand held RF controller  202  within a predetermined time out period in step  2906 , then the controller examines the node data for the selected device in step  2908 . Alternatively, if the node data for the selected device is not retrieved by the hand held RF controller  202  within a predetermined time out period in step  2906 , then the controller cancels the control of the selected device in step  2910  and displays an error message on the display  414  in step  2912 . 
     After examining the node data for the selected device in step  2908 , the hand held RF controller  202  then determines if the selected device is controllable in step  2914 . If the hand held RF controller  202  determines that the selected device is controllable, the controller then determines if the command class for the selected device is one recognized by the system  100  in step  2916 . If the command class for the selected device is one recognized by the system  100 , then the hand held RF controller  202  will use the command class for the selected device to control the selected device in step  2918 . Alternatively, if the command class for the selected device is not one recognized by the system  100 , then the hand held RF controller  202  will use a basic command class for the selected device to control the selected device in step  2920 . 
     Alternatively, if, after examining the node data for the selected device in step  2908 , the hand held RF controller  202  then determines if the selected device is not controllable in step  2914 , then the controller cancels the control of the selected device in step  2922  and displays an error message on the display  414  in step  2924 . 
     Referring now to  FIG. 30 , in an exemplary embodiment, during the operation of the hand held RF controller  202 , after a user sequentially selects DEVICES  2004  and CHILD PROTECTION  2004   g , using the menu-based program  2000 , the controller implements a method  3000  in which the controller permits a user to control the level of child protection for one or more devices, such as, for example, master and slave nodes,  102  and  104 , respectively, within the system  100 . In particular, in step  3002  the hand held RF controller  202  determines if a user has selected the control of a device within the system  100 . If the user has selected the control the level of child protection of device within the system  100 , then the display  414  of the hand held RF controller  202  prompts the user to select the device for which the level of child protection will be controlled within the system in step  3004 . 
     Once a user of the hand held RF controller  202  has selected the device for which the level of child protection will be controlled, the node data for the selected device is then retrieved by the controller. In an exemplary embodiment, the node data for the selected device includes the node information frame  1702  for the selected device. If the node data for the selected device is retrieved by the hand held RF controller  202  within a predetermined time out period in step  3006 , then the controller permits a user to select the level of child protection for the selected device in step  3008 . 
     In an exemplary embodiment, the possible levels of child protection that may be selected in step  3008  may include one or more of the following: 1) no child protection; 2) sequence child protection; and/or 3) remote control child protection. In an exemplary embodiment, no child protection is the default level of child protection. In an exemplary embodiment, sequence child protection requires a user of a device to depress one or push buttons provided on the device in a predetermined sequence within a predetermined time period in order to enable the use to adjust an operating state of the device. In an exemplary embodiment, sequence child protection requires a user of a device to depress a push button provided on the device three times in a row within two seconds in order to enable the use to adjust an operating state of the device. In an exemplary embodiment, remote control child protection only permits a user to change an operational state of a device by using the hand held RF controller  202 . 
     Alternatively, if the node data for the selected device is not retrieved by the hand held RF controller  202  within a predetermined time out period in step  3006 , then the controller cancels the control of the level of child protection for the selected device in step  3010  and displays an error message on the display  414  in step  3012 . 
     Referring now to  FIG. 31 , in an exemplary embodiment, during the operation of the hand held RF controller  202 , after a user sequentially selects DEVICES  2004  and RENAME  2004   h , using the menu-based program  2000 , the controller implements a method  3100  in which the controller permits a user to rename one or more devices, such as, for example, master and slave nodes,  102  and  104 , respectively, within the system  100 . In particular, in step  3102  the hand held RF controller  202  determines if a user has selected the renaming of a device within the system  100 . If the user has selected the renaming of a device within the system  100 , then the display  414  of the hand held RF controller  202  prompts the user to select the device to be renamed within the system in step  3104 . 
     Once a user of the hand held RF controller  202  has selected the device that will be renamed, the node data for the selected device is then retrieved by the controller. In an exemplary embodiment, the node data for the selected device includes the node information frame  1702  for the selected device. If the node data for the selected device is retrieved by the hand held RF controller  202  within a predetermined time out period in step  3106 , then the controller permits a user to rename the selected device in step  3108 . Alternatively, if the node data for the selected device is not retrieved by the hand held RF controller  202  within a predetermined time out period in step  3106 , then the controller cancels the renaming of the selected device in step  3110  and displays an error message on the display  414  in step  3112 . 
     Referring now to  FIGS. 32   a - 32   b , in an exemplary embodiment, during the operation of the hand held RF controller  202 , after a user sequentially selects DEVICES  2004  and CON FIGURE 2004   i , using the menu-based program  2000 , the controller implements a method  3200  in which the controller permits a user to configure one or more devices, such as, for example, master and slave nodes,  102  and  104 , respectively, within the system  100 . In particular, in step  3202  the hand held RF controller  202  determines if a user has selected the configuring of a device within the system  100 . If the user has selected the configuring of a device within the system  100 , then the display  414  of the hand held RF controller  202  prompts the user to select the device to be configured within the system in step  3204 . 
     Once a user of the hand held RF controller  202  has selected the device that will be configured, the node data for the selected device is then retrieved by the controller. In an exemplary embodiment, the node data for the selected device includes the node information frame  1702  for the selected device. If the node data for the selected device is retrieved by the hand held RF controller  202  within a predetermined time out period in step  3206 , then the controller permits a user to configure the selected device in step  3208 . In an exemplary embodiment, the configuration data  3208   a  for the selected device includes: the value for the off delay for the selected device, the value for the panic on time for the selected device, the value for panic enabled for the selected device, the power loss preset value for the selected device, and the power on state value for the selected device. 
     In an exemplary embodiment, the value for the off delay for the selected device may, for example, be 1 second. In an exemplary embodiment, the value for the panic on time for the selected device may, for example, be 1 second. In an exemplary embodiment, the value for panic enabled for the selected device may, for example, be PANIC ENABLED. In an exemplary embodiment, the power loss preset value for the selected device may, for example, be the permissible tolerance in the power supply. In an exemplary embodiment, the power on state value for the selected device may, for example, be operational state of the device prior to the loss of power. 
     Alternatively, if the node data for the selected device is not retrieved by the hand held RF controller  202  within a predetermined time out period in step  3206 , then the controller cancels the configuring of the selected device in step  3210  and displays an error message on the display  414  in step  3212 . 
     Referring now to  FIGS. 33   a - 33   b , in an exemplary embodiment, during the operation of the hand held RF controller  202 , after a user sequentially selects DEVICES  2004  and VERSION  2004   j , using the menu-based program  2000 , the controller implements a method  3300  in which the controller permits a user to view the device version for one or more devices, such as, for example, master and slave nodes,  102  and  104 , respectively, within the system  100 . In particular, in step  3302  the hand held RF controller  202  determines if a user has selected the viewing of the version of a device within the system  100 . If the user has selected the viewing of the version of a device within the system  100 , then the display  414  of the hand held RF controller  202  prompts the user to select the device to be configured within the system in step  3304 . 
     Once a user of the hand held RF controller  202  has selected the device for which the version will be viewed, the node data for the selected device is then retrieved by the controller. In an exemplary embodiment, the node data for the selected device includes the node information frame  1702  for the selected device. If the node data for the selected device is retrieved by the hand held RF controller  202  within a predetermined time out period in step  3306 , then the controller permits a user to view the version information for the selected device in step  3308 . In an exemplary embodiment, the version information  3308   a  for the selected device includes: the node ID value for the selected device, the application value for the selected device, the protocol value for the selected device, the library value for the selected device, the manufacturer value for the selected device, the product type value for the selected device, and the product ID value for the selected device. 
     In an exemplary embodiment, the node ID value for the selected device may, for example, be a numeric value. In an exemplary embodiment, the application value for the selected device may, for example, be a numeric decimal value. In an exemplary embodiment, the protocol value for the selected device may, for example, be a numeric decimal value. In an exemplary embodiment, the library value for the selected device may, for example, be a numeric decimal value. In an exemplary embodiment, the manufacturer value for the selected device may, for example, be an alpha-numeric value. In an exemplary embodiment, the product type value for the selected device may, for example, be an alpha-numeric value. In an exemplary embodiment, the product ID value for the selected device may, for example, be an alpha-numeric value. 
     Alternatively, if the node data for the selected device is not retrieved by the hand held RF controller  202  within a predetermined time out period in step  3306 , then the controller cancels the viewing the version of the selected device in step  3310  and displays an error message on the display  414  in step  3312 . 
     Referring now to  FIGS. 34   a - 34   b , in an exemplary embodiment, during the operation of the hand held RF controller  202 , after a user sequentially selects DEVICES  2004  and ALL SWITCH  2004   k , using the menu-based program  2000 , the controller implements a method  3400  in which the controller permits a user to control the level of functionality for all switch for one or more devices, such as, for example, master and slave nodes,  102  and  104 , respectively, within the system  100 . In particular, in step  3402  the hand held RF controller  202  determines if a user has selected the controlling of the level of functionality for all switch of a device within the system  100 . If the user has selected the controlling of the level of functionality for all switch of a device within the system  100 , then the display  414  of the hand held RF controller  202  prompts the user to select the device for which the level of functionality for all switch will be configured within the system in step  3404 . 
     Once a user of the hand held RF controller  202  has selected the device for which the level of functionality for all switch will be configured, the node data for the selected device is then retrieved by the controller. In an exemplary embodiment, the node data for the selected device includes the node information frame  1702  for the selected device. If the node data for the selected device is retrieved by the hand held RF controller  202  within a predetermined time out period in step  3406 , then the controller determines if the selected device support all switch functionality in step  3408 . If the hand held RF controller  202  determines that the selected device supports all switch functionality, then the controller permits a user to configure the level of functionality for all switch for the selected device in step  3310 . In an exemplary embodiment, the level of all switch functionality  3310   a  for the selected device may be: not included, all on only, all off only, all on and off only. 
     In an exemplary embodiment, the node ID value for the selected device may, for example, be a numeric value. In an exemplary embodiment, the application value for the selected device may, for example, be a numeric decimal value. In an exemplary embodiment, the protocol value for the selected device may, for example, be a numeric decimal value. In an exemplary embodiment, the library value for the selected device may, for example, be a numeric decimal value. In an exemplary embodiment, the manufacturer value for the selected device may, for example, be a alpha-numeric value. In an exemplary embodiment, the product type value for the selected device may, for example, be a alpha-numeric value. In an exemplary embodiment, the product ID value for the selected device may, for example, be a alpha-numeric value. 
     Alternatively, if the node data for the selected device is not retrieved by the hand held RF controller  202  within a predetermined time out period in step  3406  or if the selected device does not support all switch functionality in step  3408 , then the controller cancels the configuring of the level of all switch functionality for the selected device in step  3412  and displays an error message on the display  414  in step  3414 . 
     Referring now to  FIGS. 35   a - 35   d , in an exemplary embodiment, during the operation of the hand held RF controller  202 , after a user sequentially selects SCENES  2006  and CREATE  2006   a , using the menu-based program  2000 , the controller implements a method  3500  in which the controller permits a user to create a scene using one or more devices, such as, for example, master and slave nodes,  102  and  104 , respectively, within the system  100 . In particular, in step  3502  the hand held RF controller  202  determines if a user has selected creating a scene within the system  100 . If the user has selected creating a scene within the system  100 , then the display  414  of the hand held RF controller  202  prompts the user to enter the name of the scene to be created within the system in step  3504 . 
     Once a user of the hand held RF controller  202  has selected the name of the scene to be created in the system  100  in step  3504 , the controller then waits for a user of the controller to select defining the scene to be created in step  3506 . Once a user of the hand held RF controller  202  has selected defining the scene to be created in the system  100  in step  3506 , the controller then waits for a user of the controller to select devices for the scene to be created in step  3508 . 
     If the hand held RF controller  202  determines that the selected device for the scene to be created are not controllable in step  3510 , then the controller cancels the selection of the device for the scene to be created and displays an error message on the display  414  in step  3512  and then allows a user of the controller to continue selecting devices for the scene to be created in step  3508 . 
     Alternatively, if the hand held RF controller  202  determines that the selected device for the scene to be created is controllable in step  3510 , then the controller enters the operational level for the device selected for the new scene in step  3514 . The hand held RF controller  202  then waits for a user of the hand held RF controller  202  to indicate whether the selection of devices for the scene to be created in the system  100  has been completed in step  3516 . If the selection of devices for the scene to be created in the system  100  is indicated by a user as not completed in step  3516 , then the hand held RF controller  202  waits for a user of the controller to select devices for the scene to be created in step  3508 . 
     In an exemplary embodiment, as illustrated in  FIG. 35   c , the system  100  includes the following scenes: BEDTIME, MORNING, MOVIETIME, MUSIC, FUN TIME, DINNER, and AWAY. In an exemplary embodiment, as illustrated in  FIG. 35   d , the scene MORNING includes devices: LIVING ROOM LIGHT, HALL LIGHT, BEDROOM LIGHT, PORCH LIGHT, FRONT DOOR LIGHT, and KITCHEN LIGHT having operational values of ON, OFF, 50%, OFF, ON, and OFF. 
     In an exemplary embodiment, during the operation of the method  3500 , the system  100  may provide one or more predetermined names for scenes for selection by the user in order speed up the process of scene creation. 
     Referring now to  FIG. 36 , in an exemplary embodiment, during the operation of the hand held RF controller  202 , after a user sequentially selects SCENES  2006  and DELETE  2006   b , using the menu-based program  2000 , the controller implements a method  3600  in which the controller permits a user to delete a scene from the system  100 . In particular, in step  3602  the hand held RF controller  202  determines if a user has selected deleting a scene within the system  100 . If the user has selected deleting a scene within the system  100 , then the display  414  of the hand held RF controller  202  prompts the user to enter the name of the scene to be deleted from the system in step  3604 . Once a user of the hand held RF controller  202  has selected the name of the scene to be deleted from the system  100  in step  3604 , the controller then waits for a user of the controller to confirm the deletion of the scene in step  3606 . 
     Referring now to  FIGS. 37   a - 37   b , in an exemplary embodiment, during the operation of the hand held RF controller  202 , after a user sequentially selects SCENES  2006  and EDIT  2006   c , using the menu-based program  2000 , the controller implements a method  3700  in which the controller permits a user to edit a scene using one or more devices, such as, for example, master and slave nodes,  102  and  104 , respectively, within the system  100 . In particular, in step  3702  the hand held RF controller  202  determines if a user has selected editing a scene within the system  100 . If a user has selected editing a scene within the system  100 , then the display  414  of the hand held RF controller  202  prompts the user to enter the name of the scene to be edited within the system in step  3704 . 
     Once a user of the hand held RF controller  202  has selected the name of the scene to be edited in the system  100  in step  3704 , the controller then waits for a user of the controller to confirm the editing of the scene in step  3706 . Once a user of the hand held RF controller  202  has confirmed editing of the scene in the system  100  in step  3706 , the controller then waits for a user of the controller to select devices for the scene to be edited in step  3708 . 
     If the hand held RF controller  202  determines that the selected device for the scene to be edited are not controllable in step  3710 , then the controller cancels the selection of the device for the scene to be edited and displays an error message on the display  414  in step  3712  and then allows a user of the controller to continue selecting devices for the scene to be created in step  3708 . 
     Alternatively, if the hand held RF controller  202  determines that the selected device for the scene to be created is controllable in step  3710 , then the controller enters the operational level for the device selected for the scene to be edited in step  3714 . The hand held RF controller  202  then waits for a user of the hand held RF controller  202  to indicate whether the selection of devices for the scene to be edited in the system  100  has been completed in step  3716 . If the selection of devices for the scene to be edited in the system  100  is indicated by a user as not completed in step  3716 , then the hand held RF controller  202  waits for a user of the controller to select devices for the scene to be created in step  3708 . 
     In an exemplary embodiment, during the operation of the method  3700 , a user of the hand held RF controller  202  may edit one or more of the following aspects of a selected scene: the name of the scene, the number of the scene, the devices to be included in the scene, and the operational states of the devices to be included in the scene. 
     Referring now to  FIG. 38 , in an exemplary embodiment, during the operation of the hand held RF controller  202 , after a user sequentially selects SCENES  2006  and ACTIVATE  2006   d , using the menu-based program  2000 , the controller implements a method  3800  in which the controller permits a user to activate a scene within the system  100 . In particular, in step  3802  the hand held RF controller  202  determines if a user has selected activating a scene within the system  100 . If a user has selected activating a scene within the system  100 , then the display  414  of the hand held RF controller  202  prompts the user to enter the name of the scene to be activated within the system in step  3804 . 
     Once a user of the hand held RF controller  202  has selected the name of the scene to be activated in the system  100  in step  3804 , the controller then waits for a user of the controller to confirm the activation of the scene in step  3806 . Once a user of the hand held RF controller  202  has confirmed activating the scene in the system  100  in step  3806 , the controller then activates the selected scene in the system  100 . Once the hand held RF controller  202  determines that the selected scene has been activated in step  3808 , the controller permits a user of the system  100  to activate additional scenes in step  3802 . 
     Referring now to  FIG. 39 , in an exemplary embodiment, during the operation of the hand held RF controller  202 , after a user sequentially selects SCENES  2006  and DEACTIVATE  2006   e , using the menu-based program  2000 , the controller implements a method  3900  in which the controller permits a user to deactivate a scene within the system  100 . In particular, in step  3902  the hand held RF controller  202  determines if a user has selected deactivating a scene within the system  100 . If a user has selected deactivating a scene within the system  100 , then the display  414  of the hand held RF controller  202  prompts the user to enter the name of the scene to be deactivated within the system in step  3904 . 
     Once a user of the hand held RF controller  202  has selected the name of the scene to be deactivated in the system  100  in step  3804 , the controller then waits for a user of the controller to confirm the deactivation of the scene in step  3906 . Once a user of the hand held RF controller  202  has confirmed deactivating the scene in the system  100  in step  3906 , the controller then deactivates the selected scene in the system  100 . Once the hand held RF controller  202  determines that the selected scene has been deactivated in step  3908 , the controller permits a user of the system  100  to deactivate additional scenes in step  3902 . 
     Referring now to  FIGS. 40   a - 40   b , in an exemplary embodiment, during the operation of the hand held RF controller  202 , after a user sequentially selects EVENTS  2008  and CREATE  2008   a , using the menu-based program  2000 , the controller implements a method  4000  in which the controller permits a user to create an event using one or more user defined scenes within the system  100 . In particular, in step  4002  the hand held RF controller  202  determines if a user has selected creating an event within the system  100 . If the user has selected creating an event within the system  100 , then the display  414  of the hand held RF controller  202  prompts the user to enter the name of the event to be created within the system in step  4004 . 
     Once a user of the hand held RF controller  202  has selected the name of the event to be created in the system  100  in step  4004 , the controller then permits a user of the controller to enter the parameters  4006   a  of the event in step  4006 . In an exemplary embodiment, the parameters  4006   a  of the event include: the time of the event, the day of the event, the type of event, the scene to be used in the event, and the activity level of the event. If the event parameters have been completed in step  4008 , then the hand held RF controller  202  permits a user to create further events in step  4002 . 
     Referring now to  FIG. 41 , in an exemplary embodiment, during the operation of the hand held RF controller  202 , after a user sequentially selects EVENTS  2008  and DELETE  2008   b , using the menu-based program  2000 , the controller implements a method  4100  in which the controller permits a user to delete an event from the system  100 . In particular, in step  4102  the hand held RF controller  202  determines if a user has selected deleting an event from the system  100 . If the user has selected deleting an event from the system  100 , then the display  414  of the hand held RF controller  202  prompts the user to enter the name of the event to be deleted from the system in step  4104 . Once a user of the hand held RF controller  202  has selected the name of the event to be deleted from the system  100  in step  4104 , the controller then waits for a user of the controller to confirm the deletion of the event in step  4106 . 
     Referring now to  FIG. 42 , in an exemplary embodiment, during the operation of the hand held RF controller  202 , after a user sequentially selects EVENTS  2008  and EDIT  2008   c , using the menu-based program  2000 , the controller implements a method  4200  in which the controller permits a user to edit an event in the system  100 . In particular, in step  4202  the hand held RF controller  202  determines if a user has selected editing an event in the system  100 . If the user has selected editing an event in the system  100 , then the display  414  of the hand held RF controller  202  prompts the user to enter the name of the event to be edited in the system in step  4204 . Once a user of the hand held RF controller  202  has selected the name of the event to be edited in the system  100  in step  4204 , the controller then waits for a user of the controller to edit the parameters of the event in steps  4206  and  4208 . 
     In an exemplary embodiment, during the operation of the method  4200 , in steps  4206  and  4208 , a user of the hand held RF controller  202  may edit one or more of the following aspects of a selected event: the name of the event, the number of the event, the scenes to be included in the scene, the operational states of the scenes to be included in the event, and the timing of the event. 
     Referring now to  FIG. 43 , in an exemplary embodiment, during the operation of the hand held RF controller  202 , after a user sequentially selects EVENTS  2008  and ACTIVATE  2008   d , using the menu-based program  2000 , the controller implements a method  4300  in which the controller permits a user to activate an event within the system  100 . In particular, in step  4302  the hand held RF controller  202  determines if a user has selected activating an event within the system  100 . If a user has selected activating an event within the system  100 , then the display  414  of the hand held RF controller  202  prompts the user to enter the name of the event to be activated within the system in step  4304 . 
     Once a user of the hand held RF controller  202  has selected the name of the event to be activated in the system  100  in step  4304 , the controller then waits for a user of the controller to confirm the activation of the event in step  4306 . Once a user of the hand held RF controller  202  has confirmed activating the event in the system  100  in step  4306 , the controller then activates the selected event in the system  100 . Once the hand held RF controller  202  activates the selected event in step  4306 , the controller permits a user of the system  100  to activate additional events in step  4302 . 
     Referring now to  FIG. 44 , in an exemplary embodiment, during the operation of the hand held RF controller  202 , after a user sequentially selects EVENTS  2008  and DEACTIVATE  2008   e , using the menu-based program  2000 , the controller implements a method  4400  in which the controller permits a user to deactivate an event within the system  100 . In particular, in step  4402  the hand held RF controller  202  determines if a user has selected deactivating an event within the system  100 . If a user has selected deactivating an event within the system  100 , then the display  414  of the hand held RF controller  202  prompts the user to enter the name of the event to be deactivated within the system in step  4404 . 
     Once a user of the hand held RF controller  202  has selected the name of the event to be deactivated in the system  100  in step  4404 , the controller then waits for a user of the controller to confirm the deactivation of the event in step  4406 . Once a user of the hand held RF controller  202  has confirmed deactivating the event in the system  100  in step  4406 , the controller then deactivates the selected event in the system  100 . Once the hand held RF controller  202  deactivates the selected event in step  4406 , the controller permits a user of the system  100  to deactivate additional events in step  4402 . 
     Referring now to  FIG. 45 , in an exemplary embodiment, during the operation of the hand held RF controller  202 , after a user sequentially selects SYSTEM  2010  and DATE/TIME  2010   a , using the menu-based program  2000 , the controller implements a method  4500  in which the controller permits a user to select the date and time for the system  100 . In particular, in step  4502  the hand held RF controller  202  determines if a user has selected entering the date and time for the system  100 . If a user has selected entering the date and time for the system  100 , then the display  414  of the hand held RF controller  202  prompts the user to enter the date and time for the system in step  4504 . Once a user of the hand held RF controller  202  has entered and confirmed the date and time of the system in step  4506 , the controller then permits a user of the controller to enter another date and time for the system  100  in step  4502 . 
     Referring now to  FIGS. 46   a - 46   b , in an exemplary embodiment, during the operation of the hand held RF controller  202 , after a user sequentially selects SYSTEM  2010  and PANIC  2010   b , using the menu-based program  2000 , the controller implements a method  4500  in which the controller permits a user to configure the panic group  1202  for the system  100 . In particular, in step  4602  the hand held RF controller  202  determines if a user has selected configuring the panic group  1202  for the system  100 . If a user has selected configuring the panic group  1202  for the system  100 , then the display  414  of the hand held RF controller  202  prompts the user to select a device such as, for example, a master or slave node,  102  or  104 , respectively, for inclusion in the panic group of the system in step  4604 . After a user of the hand held RF controller  202  has selected a device for inclusion in the panic group  1202  of the system  100  in step  4604 , the controller then determines if the selected device for inclusion in the panic group of the system supports a panic operation in step  4606 . 
     If the hand held RF controller  202  determines that the device selected for inclusion in the panic group  1202  of the system  100  does not support a panic operation in step  4606 , then the controller displays an error message on the display  414  of the controller and cancels the selection of the device in step  4608 , and permits a user of the controller to select another device in step  4604 . Alternatively, if the hand held RF controller  202  determines that the device selected for inclusion in the panic group  1202  of the system  100  does support a panic operation in step  4606 , then the selected device is added to the panic group for the system in step  4610 . 
     If a user of the hand held RF controller  202  indicates that more devices will be selected for inclusion in the panic group  1202  of the system  100  in step  4612 , then the controller permits a user of the controller to select more devices for inclusion in the panic group for the system in step  4604 . 
     Referring now to  FIG. 47 , in an exemplary embodiment, during the operation of the hand held RF controller  202 , after a user sequentially selects SYSTEM  2010  and LANGUAGE  2010   c , using the menu-based program  2000 , the controller implements a method  4700  in which the controller permits a user to select the language for the system  100 . In particular, in step  4702  the hand held RF controller  202  determines if a user has selected entering the language for the system  100 . If a user has selected entering the language for the system  100 , then the display  414  of the hand held RF controller  202  prompts the user to enter the language for the system in step  4704 . Once a user of the hand held RF controller  202  has entered and confirmed the language of the system in step  4706 , the controller then permits a user of the controller to enter another language for the system  100  in step  4702 . 
     Referring now to  FIGS. 48   a - 48   b , in an exemplary embodiment, during the operation of the hand held RF controller  202 , after a user sequentially selects SYSTEM  2010  and VERSION  2010   d , using the menu-based program  2000 , the controller implements a method  4800  in which the controller permits a user to display the version  4800   a  for the system  100 . In particular, in step  4802  the hand held RF controller  202  determines if a user has selected displaying the version of the system  100 . If a user has selected viewing the version of the system  100 , then the display  414  of the hand held RF controller  202  displays the version  4800   a  of the system in step  4804 . 
     Referring now to  FIGS. 49   a - 49   c , in an exemplary embodiment, during the operation of the hand held RF controller  202 , after a user sequentially selects SYSTEM  2010  and REPLICATE  2010   e , using the menu-based program  2000 , the controller implements a method  4900  in which the controller permits a user to replicate the configuration of a system  100  contained within a first device, such as, for a example a first master node  102   a  into another device such as, for example, a second master node  102   b . In particular, in step  4902  the hand held RF controller  202  determines if a user has selected replicating the configuration of the system  100 . If a user has selected replicating the configuration of the system  100 , then the display  414  of the hand held RF controller  202  prompts a user of the controller to enter the name of the device to be replicated from in step  4904  and the name of the device to be replicated to in step  4906 . 
     After a user of the hand held RF controller  202  has entered the name of the device to be replicated from in step  4904  and the name of the device to be replicated to in step  4906 , the node information for both of the devices is transmitted to the controller. If the node information for both of the devices is not received by the hand held RF controller  202  within a predetermined timeout period in step  4908 , then replication is canceled in step  4910  and the display  414  of controller displays an error message in step  4912 . 
     Alternatively, if the node information for both of the devices is received by the hand held RF controller  202  within a predetermined timeout period in step  4908 , then the display  414  of the controller prompts a user of the controller to select the portions of the configuration of the system  100  to be replicated from the first master node  102   a  to the second master node  102   b  in step  4914 . After a user of the hand held RF controller  202  selects the portions of the configuration of the system  100  to be replicated from the first master node  102   a  to the second master node  102   b  in step  4914 , the replication of the configuration of the system begins in step  4916 . 
     If the replication of the configuration of the system  100  is not completed within a predetermined timeout period in step  4918 , then replication is canceled in step  4920  and the display  414  of the hand held RF controller  202  displays an error message in step  4922 . Alternatively, if the replication of the configuration of the system  100  is completed within a predetermined timeout period in step  4918 , then the hand held RF controller  202  prompts a user of the controller to indicate if additional replications are to be performed in step  4924 . If a user of the hand held RF controller  202  indicates that additional replications of the configuration of the system  100  are to be performed, the controller then permits a user to select further replications in step  4902 . 
     Referring now to  FIGS. 50   a - 50   c , in an exemplary embodiment, during the operation of the hand held RF controller  202 , after a user sequentially selects SYSTEM  2010  and UPDATE  2010   f , using the menu-based program  2000 , the controller implements a method  5000  in which the controller permits a user to update one or more aspects of the configuration of a system  100  in a device, such as, for a example a master node  102 . In particular, in step  5002  the hand held RF controller  202  determines if a user has selected updating the configuration of the system  100  in a device. If a user has selected updating the configuration of the system  100  in a device, then the display  414  of the hand held RF controller  202  prompts a user of the controller to enter the name of the device to be updated in step  5004 . 
     After a user of the hand held RF controller  202  has entered the name of the device to be updated in step  5004 , the node information for the device is transmitted to the controller. If the node information for the selected device is not received by the hand held RF controller  202  within a predetermined timeout period in step  5006 , then the update is canceled in step  5008  and the display  414  of controller displays an error message in step  5010 . 
     Alternatively, if the node information for both of the selected device is received by the hand held RF controller  202  within a predetermined timeout period in step  5006 , then the display  414  of the controller prompts a user of the controller to insert a firmware  5012   a  containing the system update into a firmware interface  5012   b  in the device selected for updating in step  5012 . After a user of the hand held RF controller  202  has inserted the firmware  5012   a  containing the system update into the firmware interface  5012   b  in the device selected for updating, the updating of the configuration of the system  100  in the selected device begins in step  5014 . 
     If the updating of the configuration of the system  100  into the selected device is not completed within a predetermined timeout period in step  5016 , then the update is canceled in step  5018  and the display  414  of the hand held RF controller  202  displays an error message in step  5020 . Alternatively, if the update of the configuration of the system  100  in the selected device is completed within a predetermined timeout period in step  5016 , then the hand held RF controller  202  prompts a user of the controller to indicate if additional updates are to be performed in step  5022 . If a user of the hand held RF controller  202  indicates that additional updates of the configuration of the system  100  are to be performed, the controller then permits a user to select further updates in step  5002 . 
     Referring now to  FIGS. 51   a - 51   b , in an exemplary embodiment, during the operation of the hand held RF controller  202 , after a user sequentially selects AWAY  2012  and EDIT  2012   a , using the menu-based program  2000 , the controller implements a method  5100  in which the controller permits a user to edit the away group  1402  of the system  100 . In particular, in step  5102  the hand held RF controller  202  determines if a user has selected editing the away group  1402  of the system  100 . If a user has selected editing the away group  1402  of the system  100 , then a user of the hand held RF controller  202  may then edit the away group in step  5104 . If a user of the hand held RF controller  202  has not completed editing the away group  1402  of the system  100  in step  5106 , the user may continue editing in step  5104 . 
     Referring now to  FIG. 52 , in an exemplary embodiment, during the operation of the hand held RF controller  202 , after a user sequentially selects AWAY  2012  and ACTIVATE  2012   b , using the menu-based program  2000 , the controller implements a method  5200  in which the controller permits a user to activate the away group  1402  of the system  100 . In particular, in step  5202  the hand held RF controller  202  determines if a user has selected activating the away group  1402  of the system  100 . If a user has selected activating the away group  1402  of the system  100 , then the hand held RF controller  202  requests the user to confirm the activation of the away group in step  5204 . If a user of the hand held RF controller  202  confirms the activation of the away group  1402  of the system  100  in step  5204 , then the controller randomly controls the operation of the devices included in the away group in step  5206 . 
     Referring now to  FIG. 53 , in an exemplary embodiment, during the operation of the hand held RF controller  202 , after a user sequentially selects AWAY  2012  and DEACTIVATE  2012   c , using the menu-based program  2000 , the controller implements a method  5300  in which the controller permits a user to deactivate the away group  1402  of the system  100 . In particular, in step  5302  the hand held RF controller  202  determines if a user has selected deactivating the away group  1402  of the system  100 . If a user has selected deactivating the away group  1402  of the system  100 , then the hand held RF controller  202  requests the user to confirm the deactivation of the away group in step  5304 . If a user of the hand held RF controller  202  confirms the deactivation of the away group  1402  of the system  100  in step  5304 , then the controller resumes normal control of the operation of the devices included in the away group in step  5306 . 
     Referring now to  FIG. 54 , an exemplary embodiment of a table top RF controller  204  includes a controller  402  that is operably coupled to an RF transceiver  404 , a memory  406 , a network interface  408 , a keypad  410 , a user interface  412 , a display  414 , a battery  416 , and a power adaptor  5402 . In an exemplary embodiment, the power adaptor  5402  is adapted to be coupled to an external source of power and for adapting and coupling the external source of power to the controller  402 , the RF transceiver  404 , the memory  406 , the network interface  408 , the keypad  410 , the user interface  412 , and the display  414 . 
     In an exemplary embodiment, within the exception of the addition of the power adaptor  5402 , the design and operation of the table top RF controller  204  is substantially identical to the design and operation of the hand held RF controller  202 . 
     In an exemplary embodiment, as illustrated in  FIG. 54   a , the elements of the table top controller  204  may be positioned within and supported by a housing  5404  having a cover  1922  that defines one or more openings for the keypad  410 , including one or more of the navigation buttons  1904 , the OK button  1906 , the BACK button  1908 , the HOT buttons  1910 , the ALL ON button  1912   a , the ALL OFF button  1912   b , the PANIC button  1914 , and the MENU keys  1916 , and the display  414 . 
     Referring now to  FIG. 55 , an exemplary embodiment of a wall mount RF controller  206  includes a controller  402  that is operably coupled to an RF transceiver  404 , a memory  406 , a network interface  408 , a keypad  410 , a user interface  412 , a display  414 , a battery  416 , and a power adaptor  5402 . In an exemplary embodiment, a power adaptor  5402  is adapted to be coupled to an external source of power and for adapting and coupling the external source of power to the controller  402 , the RF transceiver  404 , the memory  406 , the network interface  408 , the keypad  410 , the user interface  412 , and the display  414 . 
     In an exemplary embodiment, the design and operation of the wall mount RF controller  206  is substantially identical to the design and operation of the table top controller  204 . 
     In an alternative embodiment, the operation of the wall mount RF controller  206  is limited to the control of scenes  802 . In particular, in an alternative embodiment, the menu state engine  504   a  of the wall mount RF controller  206  only includes a scene engine  602   b  that only enables a main menu  2002  that permits a selection of scenes  2006 . 
     In an exemplary embodiment, as illustrated in  FIG. 55   a , the wall mount RF controller  206  may be positioned and mounted upon a surface  5502  using a cover plate  5504  that defines an opening  5504   a  for one or more of the hot buttons  1910  and the display  414 . In an exemplary embodiment, one or more of hot buttons  1910  permit a user of the wall mount RF controller  206  to select one or more corresponding scenes  802  for implementation by the system  100 . In an exemplary embodiment, the cover plate  5504  further defines one or more additional openings  5504   b  for mounting one or more corresponding other devices adjacent to the wall mount RF controller  206  such as, for example, the RF dimmer  310 . 
     Referring now to  FIG. 56 , an exemplary embodiment of a USB RF controller  208  includes a controller  402  that is operably coupled to an RF transceiver  404 , a memory  406 , a network interface  408 , a keypad  410 , a user interface  412 , a display  414 , a battery  416 , and a power adaptor  5402 . In an exemplary embodiment, a power adaptor  5402  is adapted to be coupled to an external source of power and for adapting and coupling the external source of power to the controller  402 , the RF transceiver  404 , the memory  406 , the network interface  408 , the keypad  410 , the user interface  412 , and the display  414 . 
     In an exemplary embodiment, the design and operation of the wall mount RF controller  206  is substantially identical to the design and operation of the table top controller  204 . 
     In an alternative embodiment, the network interface  408  of the USB RF controller  208  enables a user of the USB RF controller to remotely control and interface with the system  100  using a network interface such as, for example, the Internet. In this manner, a user of the USB RF controller  208  may, for example, remotely configure the system from long distances using a desktop, laptop, portable digital assistant, cell phone, or other suitable device capable of being operably coupled to the USB RF controller. 
     Referring now to  FIG. 57 , an exemplary embodiment of an RF switch  302  includes a controller  5702  that is operably coupled to: a memory  5704  including a non-volatile memory  5706 , an RF transceiver  5708 , a light switch touch pad  5710 , an install button  5712 , an uninstall button  5714 , an LED indicator light  5716 , an associate button  5718 , and a network interface  5720 . In an exemplary embodiment, a conventional power supply  5722  is operably coupled to the RF switch  302  for powering the operation of the RF switch, and the RF switch controllably couples and decouples a load  5724  to and from the power supply. 
     Referring to  FIG. 57   a , in an exemplary embodiment, the RF switch  302  includes a housing  5726 , for containing and supporting the elements of the RF switch, and a cover  5728  that defines an opening  5828   a  for the light switch touch pad  5710  and an opening  5828   b  for one or more other buttons  5730  that may, for example, include one or more of the following: the install button  5712 , the uninstall button  5714 , and the associate button  5718 . In an exemplary embodiment, the RF switch  302  further includes an external RF antenna  5732  that is operably coupled to the RF transceiver  5708 . 
     In an exemplary embodiment, the controller  5702  is adapted to monitor and control the operation of the memory  5704  including a non-volatile memory  5706 , the RF transceiver  5708 , the light switch touch pad  5710 , the install button  6712 , the install button  5714 , the LED indicator light  5716 , the associate button  5718 , and the network interface  5720 . In an exemplary embodiment, the controller  5702  includes one or more of the following: a conventional programmable general purpose controller, an application specific integrated circuit (ASIC), or other conventional controller devices. In an exemplary embodiment, the controller  5702  includes a model ZW0201 controller, commercially available from Zensys A/S. 
     Referring now to  FIG. 58 , in an exemplary embodiment, the controller  5702  includes an operating system  5802 , application programs  5804 , and a boot loader  5806 . In an exemplary embodiment, the operating system  502  includes a serial communications driver  5802   a , a memory driver  5802   b , a display driver  5802   c , and a button input driver  5802   c . In an exemplary embodiment, the serial communications driver  5802   a  controls serial communications using the RF serial transceiver  5708 , the memory driver  5802   b  controls the memory  5704  including the non volatile memory  5706 , the display driver  5802   c  controls the LED indicator light  5716 , and the button input driver  5802   d  debounces button inputs provided by a user using one or more of: the light switch touchpad  5710 , the install button  5712 , the uninstall button  5714 , and the associate button  5718 . In an exemplary embodiment, the serial communications driver  5802   a  includes a Z-Wave™ serial API driver that implements a Z-Wave™ serial API protocol. The Z-Wave™ serial API driver that implements a Z-Wave™ serial API protocol are both commercially available from Zensys A/S. 
     In an exemplary embodiment, the application programs  5804  include a state engine  5804   a . In an exemplary embodiment, the state engine  5804   a  permits a user of one or more of the master nodes  102  to configure, control and monitor the operation of the RF switch  302 . 
     Referring now to  FIG. 59 , in an exemplary embodiment, the state engine  5804   a  includes an installation engine  5902 , a change of state engine  5904 , an association engine  5906 , a child protection engine  5908 , a delayed off engine  5910 , a panic mode engine  5912 , and a loss of power detection engine  5914 . 
     In an exemplary embodiment, the installation engine  5902  monitors the operating state of the RF Switch  302  and provides an indication to a user of the system  100  as to whether or not the switch has been installed in the system. In this manner, the installation engine  5902  facilitates the installation of the RF switch  302  into the system  100 . 
     In an exemplary embodiment, the change of state engine  5904  monitors the operating state of the RF switch  302  and, upon a change in operating state, transmits information to one or more of the master nodes  102  regarding the configuration of the RF switch. 
     In an exemplary embodiment, the association engine  5906  is adapted to monitor and control the operation of the RF switch  302  when the RF switch is associated with one or more communication pathway  702 . 
     In an exemplary embodiment, the child protection engine  5908  is adapted to monitor and control the operation of the RF switch  302  when the RF switch is operated in a child protection mode of operation. 
     In an exemplary embodiment, the delayed off engine  5910  is adapted to monitor and control the operation of the RF switch  302  when the RF switch is operated in a delayed off mode of operation. 
     In an exemplary embodiment, the panic mode engine  5912  is adapted to monitor and control the operation of the RF switch  302  when the RF switch is operated in a panic mode of operation. 
     In an exemplary embodiment, the loss of power detection engine  5914  is adapted to monitor the operating state of the RF switch  302  and, upon the loss of power, save the operating state of the RF switch  302  into the non volatile memory  5706 . Upon the resumption of power to the RF switch  302 , the loss of power detection engine  5914  then retrieves the stored operating state of the RF switch  302  from the non volatile memory  5706  and restores the operating state of the RF switch. 
     In an exemplary embodiment, the memory  5704 , including the non volatile memory  5706 , is operably coupled to and controlled by the controller  5702 . In an exemplary embodiment, as illustrated in  FIG. 60 , the memory  5704 , including the non volatile memory  5706 , includes a copy of the operating system  6002 , a copy of the application programs  6004 , a device database  6006 , a scenes database  6008 , an events database  6010 , an away database  6012 , and a system database  6014 . In an exemplary embodiment, the memory  406  includes a model 24LC256 non volatile memory, commercially available from Microchip. 
     In an exemplary embodiment, the device database  6006  includes information that is specific to the RF switch  302 . In an exemplary embodiment, as illustrated in  FIG. 61 , the device database  6006  includes the node information frame  1702  for the RF switch  302 , an association database  6102  for the RF switch, a child protection database  6104  for the RF switch, a delayed off database  6106  for the RF switch, a panic database  6108  for the RF switch, and an operating state database  6110  for the RF switch. In an exemplary embodiment, the association database  6102  for the RF switch  302  includes information regarding the communication pathways  702  associated with the RF switch. In an exemplary embodiment, the child protection database  6104  for the RF switch  302  includes information regarding the operating characteristics of the RF switch when child protection is enabled. In an exemplary embodiment, the delayed off database  6106  for the RF switch  302  includes information regarding the operating characteristics of the RF switch when delayed off is enabled. In an exemplary embodiment, the panic database  6108  for the RF switch  302  includes information regarding the operating characteristics of the RF switch when panic is enabled. In an exemplary embodiment, the operating state database  6110  for the RF switch  302  includes information representative of the operating state of the RF switch. 
     In an exemplary embodiment, the device database  6006  includes one or more of the following information: 
     
       
         
               
               
               
               
               
             
               
               
               
               
               
             
           
               
                   
               
               
                   
                   
                   
                 Default 
                   
               
               
                 Parameter 
                 Offset 
                 Size 
                 Value 
                 Description 
               
               
                   
               
             
             
               
                   
               
             
          
           
               
                 Child 
                 1 
                 1 
                 0 
                 This is the child protection 
               
               
                 Protection 
                   
                   
                   
                 mode for the RF switch 302. 
               
               
                 Mode 
                   
                   
                   
                 The default value of 0 
               
               
                   
                   
                   
                   
                 corresponds to no child 
               
               
                   
                   
                   
                   
                 protection. 
               
               
                 Off Delay 
                 2 
                 1 
                 10 
                 This is the number of 
               
               
                   
                   
                   
                   
                 seconds that the RF switch 
               
               
                   
                   
                   
                   
                 302 will flash the LED 
               
               
                   
                   
                   
                   
                 indicator 5716 before 
               
               
                   
                   
                   
                   
                 switching off the load 5724. 
               
               
                 Panic On 
                 3 
                 1 
                 1 
                 This is the number of seconds 
               
               
                 Time 
                   
                   
                   
                 the load 5724 will be on 
               
               
                   
                   
                   
                   
                 while in panic mode. 
               
               
                 Panic Off 
                 4 
                 1 
                 1 
                 This is the number of seconds 
               
               
                 Time 
                   
                   
                   
                 the load 5724 will be off 
               
               
                   
                   
                   
                   
                 while in panic mode. 
               
               
                 Load State 
                 5 
                 1 
                 0 
                 This is the operational state 
               
               
                   
                   
                   
                   
                 of the load 5724. The default 
               
               
                   
                   
                   
                   
                 value is for the load to be 
               
               
                   
                   
                   
                   
                 OFF. 
               
               
                 All Switch 
                 6 
                 1 
                 0xFF 
                 This indicates the 
               
               
                 State 
                   
                   
                   
                 operational state of the RF 
               
               
                   
                   
                   
                   
                 switch 302 with regard to the 
               
               
                   
                   
                   
                   
                 all switch group. The default 
               
               
                   
                   
                   
                   
                 is for the RF switch 302 to 
               
               
                   
                   
                   
                   
                 be included in the all switch 
               
               
                   
                   
                   
                   
                 group for both All ON and All 
               
               
                   
                   
                   
                   
                 OFF. 
               
               
                 Location 
                 7 
                 25 
                 “Lighted 
                 This is the location name. 
               
               
                   
                   
                   
                 Switch” 
                 There is a maximum of 24 
               
               
                   
                   
                   
                   
                 characters plus a null 
               
               
                   
                   
                   
                   
                 terminator. 
               
               
                 Load Boot 
                 32 
                 1 
                 LAST 
                 This is the state the load 
               
               
                 State 
                   
                   
                 VALUE 
                 5724 takes upon booting up 
               
               
                   
                   
                   
                   
                 the RF switch 302. 
               
               
                 Panic Mode 
                 33 
                 1 
                 Enabled 
                 This controls whether Panic 
               
               
                 Enable 
                   
                   
                   
                 Mode is enabled or disabled. 
               
               
                 Associated 
                 34 
                 5 
                 0 
                 The node IDs of nodes 
               
               
                 Nodes 
                   
                   
                   
                 associated with the RF switch 
               
               
                   
                   
                   
                   
                 302. 
               
               
                   
               
             
          
         
       
     
     In an exemplary embodiment, the scenes database  6008  includes information regarding the scenes  802  that include the RF switch  302 . In an exemplary embodiment, the events database  6010  includes information regarding the events  1002  that include the RF switch  302 . In an exemplary embodiment, the away database  6012  includes information regarding the away group  1402  that includes the RF switch  302 . In an exemplary embodiment, the system database  6014  includes system information that includes the RF switch  302 . 
     In an exemplary embodiment, the RF transceiver  5708  is operably coupled to and controlled and monitored by the controller  5702 . In an exemplary embodiment, the RF transceiver  5708  transmits and receives RF communications to and from other master and slave nodes,  102  and  104 , respectively. In an exemplary embodiment, the RF transceiver  5708  may, for example, include one or more of the following: a conventional RF transceiver, and/or the model ZW0201 RF transceiver commercially available from Zensys A/S. 
     In an exemplary embodiment, the light switch touch pad  5710  is a conventional light switch touch pad and is operably coupled to and controlled and monitored by the controller  5702 . In an exemplary embodiment, the light switch touch pad  5710  permits an operator of the RF switch  302 , in combination with the system  100 , to select the desired mode of operation of the load  5724 . 
     In an exemplary embodiment, the install button  5712  is operably coupled to and controlled and monitored by the controller  5702 . In an exemplary embodiment, the install button  5712  permits an operator of the RF switch  302 , in combination with the system  100 , to install the RF switch into the system. 
     In an exemplary embodiment, the uninstall button  5714  is operably coupled to and controlled and monitored by the controller  5702 . In an exemplary embodiment, the uninstall button  5714  permits an operator of the RF switch  302 , in combination with the system  100 , to uninstall the RF switch from the system. 
     In an exemplary embodiment, the LED indicator light  5716  is operably coupled to and controlled and monitored by the controller  5702 . 
     In an exemplary embodiment, the associate button  5718  is operably coupled to and controlled and monitored by the controller  5702 . In an exemplary embodiment, the associate button  5718  permits an operator of the RF switch  302 , in combination with the system  100 , to associate the RF switch with communication pathways  702  in the system. 
     Referring to  FIG. 62 , in an exemplary embodiment, during operation of the RF switch  302 , the RF switch implements a method of installation  6200  in which, if the RF switch has been operably coupled to the power supply  5722 , then the LED indicator lights  5716  are operated to indicate this operational state in steps  6202  and  6204 . Then, if the RF switch  302  has been installed in the system  100 , then the LED indicator lights  5716  are operated to indicate this operational state in steps  6206  and  6208 . In an exemplary embodiment, the LED indicator lights  5716  flash on an off to indicate the operational state in steps  6202  and  6204 , and the LED indicator lights  5716  are turned on to indicate the operational state in steps  6206  and  6208 . In this manner, an operator of the system  100  is provided with a visual and highly effective indication of the operational state of the RF switch  302  that is local to the RF switch. This permits an installer of the RF switch  302 , in a large house or commercial building, with an effective means of determining the operational state of the RF switch  302  that is both local to the RF switch and avoids the need to interrogate a master node  102  to determine the operational state. 
     Referring to  FIG. 63 , in an exemplary embodiment, during operation of the RF switch  302 , the RF switch implements a method of detecting a change of state  6300  in which, if the operating state of the RF switch has changed, then the node information frame  1702  for the RF switch is transmitted to one or more of the master nodes  102  of the system  100  using the RF transceiver  5708  in steps  6302  and  6304 . 
     Referring to  FIGS. 64   a - 64   b , in an exemplary embodiment, during operation of the RF switch  302 , the RF switch implements a method of association  6400  in which it is first determined if the RF switch is associated with a plurality of slave nodes  104 , e.g., slave nodes  104   a  and  104   b , and thereby is associated with a plurality of communication pathways, e.g., communication pathways  702   a  and  702   b , in step  6402 . If the RF switch is associated with a plurality of slave nodes  104  and thereby is associated with a plurality of communication pathways  702 , then a communication from the source node  706  that is principally directed to, and directly affects, only one of the destination nodes  708   a , is transmitted by multicasting the communication to all of the nodes associated with the RF switch  302  in step  6404 . I.e., the communication is transmitted by the RF switch  302  through all of the communication pathways,  702   a  and  702   b , that the RF switch is associated with thereby transmitting the communication to the slave nodes,  104   a  and  104   b , and the destination nodes,  708   a  and  708   b . The communication is then single-casted to only the nodes directly affected by the communication in step  6406 . I.e., the communication is only transmitted by the RF switch  302  through the communication pathway  702   a  thereby transmitting the communication to the slave node  104   a  and the destination node  708   a . In this manner, the communication of the information to the affected nodes in the system  100  is assured by performing a multi-cast prior to a single-cast. 
     Referring to  FIG. 65 , in an exemplary embodiment, during operation of the RF switch  302 , the RF switch implements a method of child protection  6500  in which it is first determined if the RF switch has active child protection functionality in step  6502 . If the RF switch  302  has active child protection functionality, then it is then determined if the RF switch has sequence control or remote control child protection functionality in step  6504 . 
     If the RF switch  302  has sequence control child protection functionality, then, in order to permit local manual operation of the switch, a user must depress the touchpad  5710  three times in step  6506 . If a user of the RF switch  302  depresses the touchpad  5710  three times in step  6506 , then local manual operation of the RF switch, using the touchpad  5710 , is permitted in step  6508 . 
     Alternatively, if the RF switch  302  has remote control child protection functionality, then, local manual operation of the switch, using the touchpad  5710 , is not permitted. Consequently, if the RF switch  302  has remote control child protection functionality, then local manual operation of the switch, using the touchpad  5710 , is not permitted in step  6510 . As a result, control of the RF switch  302  is provided by one or more of the master nodes  102  of the system  100 . 
     Referring to  FIGS. 66   a  to  66   c , in an exemplary embodiment, during operation of the RF switch  302 , the RF switch implements a method of delayed off  6600  in which it is first determined if the touchpad  5710  of the RF switch is in an on position in step  6602 . If the touchpad  5710  of the RF switch  302  is in an on position, then it is then determined if the RF switch has remote control protection in step  6604 . If the RF switch  302  has remote control protection, then, local manual operation of the switch, using the touchpad  5710 , is not permitted. 
     If the RF switch  302  does not have remote control protection, then it is then determined if the RF switch has sequence control protection in step  6606 . If the RF switch  302  has sequence control protection, then, if a user of the RF switch depresses the touchpad  5710  of the RF switch three times in step  6608  or if the RF switch  302  does not have sequence control protection, then it is determined if the touchpad was depressed for at least some predefined minimum time period in step  6610 . 
     If the touchpad  5710  of the RF switch  302  was depressed for at least some predefined minimum time, then it is determined if the touchpad was also subsequently depressed in step  6612 . If the touchpad  5710  of the RF switch  302  was also subsequently depressed, then the load  5724  that is operably coupled to the RF switch is turned off in step  6614 . If the touchpad  5710  of the RF switch  302  was not also subsequently depressed, then it is determined if the RF switch  302  will be controlled by one or more of the master nodes  102  in step  6616 . 
     If the RF switch  302  will be controlled by one or more of the master nodes  102 , then the operational state of the RF switch is controlled by one or more of the master nodes  102  in step  6618 . Alternatively, if the RF switch  302  will not be controlled by one or more of the master nodes  102 , then the LED indicator light  5716  of the RF switch are flashed in step  6620 . The RF switch  302  is then operated to turn off the load  5724  operably coupled to the RF switch after a predetermined time period in step  6622 , and then the LED indicator light  5716  of the RF switch are turned off in step  6624 . 
     Referring to  FIGS. 67   a  to  67   b , in an exemplary embodiment, during operation of the RF switch  302 , the RF switch implements a method of panic mode operation method  6700  in which it is first determined if a panic mode operation has been selected by a user of the system  100  in step  6702 . In an exemplary embodiment, a panic mode operation may be selected by a user of the system  100  by operating one or more of the master nodes  102  of the system. 
     If a panic mode operation has been selected by a user of the system  100 , then the RF switch  302  is operated in accordance with the operating parameters assigned to the RF switch during a panic mode of operation as, for example, contained within the panic database  6108 , in step  6704 . If the touchpad  5710  of the RF switch  302  is then depressed in step  6706 , then the RF switch is operated to decouple the load  5724  from the power supply  5722  in step  6708 . The panic mode of operation is then canceled in step  6710 . 
     Alternatively, if the touchpad  5710  of the RF switch  302  is not then depressed in step  6706 , then, if the panic mode of operation is canceled by a master node  102  of the system in step  6712 , then the RF switch is operated to decouple the load  5724  from the power supply  5722  in step  6714 . The panic mode of operation is then canceled in step  6716 . 
     Alternatively, if the panic mode of operation is not canceled by a master node  102  of the system in step  6712 , then the RF switch  302  is operated in accordance with the panic mode duty cycle settings for the RF switch contained within, for example, the panic database  6108 , in step  6718 . In an exemplary embodiment, the panic mode duty cycle settings define an amount of time to couple the load  5724  to the power supply  5722  and an amount of time to decouple the load from the power supply. For example, if the load  5724  is a light, operation of the RF switch  302  in a panic mode of operation will turn the light on and off in accordance with the panic mode duty cycle settings for the RF switch. If a panic mode of operation is canceled by a user of the system  100  in step  6720 , then the operation of the RF switch  302  will return to normal in step  6722 . 
     Referring to  FIG. 68 , in an exemplary embodiment, during operation of the RF switch  302 , the RF switch implements a method of loss of power detection method  6700  in which it is first determined if a loss of power has occurred, for example, by monitoring the power supply  5722  in step  6702 . If a loss of power is detected in step  6802 , then the current operational state of the RF switch  302  is stored in the RF switch operational state database  6110  within the non-volatile memory  5704  of the RF switch in step  6804 . It is then determined if power has been restored to the RF switch  302 , for example, by monitoring the power supply  5722  in step  6806 . If power has been restored to the RF switch  302 , then the current operational state of the RF switch  302  is retrieved from the RF switch operational state database  6110  within the non-volatile memory  5704 , and the operational state of the RF switch is restored to the operational state defined within the RF switch operational state database  6110  in step  6808 . 
     In an exemplary embodiment, the design, operation and functionality of the light switch touch pad  5710 , the install button  5712 , the uninstall button  5714 , and the associate button  5718  may be combined into a single push button. 
     Referring now to  FIG. 69 , an exemplary embodiment of an RF receptacle  304  includes a controller  6902  that is operably coupled to: a memory  6904  including a non-volatile memory  6906 , an RF transceiver  6908 , an on/off switch  6910 , an install button  6912 , an uninstall button  6914 , an LED indicator light  6916 , an associate button  6918 , a network interface  6920 , a conventional top plug receptacle  6922 , and a conventional bottom plug receptacle  6924 . In an exemplary embodiment, a conventional power supply  6926  is operably coupled to the RF receptacle  304  for powering the operation of the RF receptacle, and the RF receptacle controllably couples and decouples 1 st  and 2 nd  loads,  6928  and  6930 , respectively, to and from the power supply. 
     Referring to  FIG. 69   a , in an exemplary embodiment, the RF receptacle  304  includes a housing  6932 , for containing and supporting the elements of the RF receptacle, and a cover  6934  that defines top and bottom plug openings,  6934   a  and  6934   b , for the top and bottom plug receptacles,  6922  and  6924 , respectively, an opening  6934   c  for one or more buttons  6936  that may, for example, include one or more of the following: the on/off switch  6910 , the install button  6912 , the uninstall button  6914 , and the associate button  6918 , and an opening  6934   d  for the LED indicator  6916 . In an exemplary embodiment, the RF receptacle  304  further includes an external RF antenna  6938  that is operably coupled to the RF transceiver  6908 . 
     In an exemplary embodiment, the controller  6902  is adapted to monitor and control the operation of the memory  6904 , including a non-volatile memory  6906 , the RF transceiver  6908 , the on/off switch  6910 , the install button  6912 , the uninstall button  6914 , the LED indicator light  6916 , the associate button  6918 , the network interface  6920 , the top plug receptacle  6922 , and the bottom plug receptacle  6924 . In an exemplary embodiment, the controller  6902  includes one or more of the following: a conventional programmable general purpose controller, an application specific integrated circuit (ASIC), one or more conventional relays for controllably coupling or decoupling one or both of the plug receptacles,  6922  and  6924 , to or from the loads,  6928  and  6930 , respectively, or other conventional controller devices. In an exemplary embodiment, the controller  6902  includes a model ZW0201 controller, commercially available from Zensys A/S. 
     Referring now to  FIG. 70 , in an exemplary embodiment, the controller  6902  includes an operating system  7002 , application programs  7004 , and a boot loader  7006 . In an exemplary embodiment, the operating system  7002  includes a serial communications driver  7002   a , a memory driver  7002   b , a display driver  7002   c , and a button input driver  7002   c . In an exemplary embodiment, the serial communications driver  7002   a  controls serial communications using the RF serial transceiver  6908 , the memory driver  7002   b  controls the memory  6904 , including the non volatile memory  6906 , the display driver  7002   c  controls the LED indicator light  6916 , and the button input driver  7002   d  debounces button inputs provided by a user using the on/off switch  6910 , the install button  6912 , the uninstall button  6914 , and the associate button  6918 . In an exemplary embodiment, the serial communications driver  7002   a  includes a Z-Wave™ serial API driver that implements a Z-Wave™ serial API protocol. The Z-Wave™ serial API driver that implements a Z-Wave™ serial API protocol are both commercially available from Zensys A/S. 
     In an exemplary embodiment, the application programs  7004  include a state engine  7004   a . In an exemplary embodiment, the state engine  7004   a  permits a user of one or more of the master nodes  102  to configure, control and monitor the operation of the RF receptacle  304 . 
     Referring now to  FIG. 71 , in an exemplary embodiment, the state engine  7004   a  includes an installation engine  7102 , a change of state engine  7104 , an association engine  7106 , a child protection engine  7108 , a delayed off engine  7110 , a panic mode engine  7112 , and a loss of power detection engine  7114 . 
     In an exemplary embodiment, the installation engine  7102  monitors the operating state of the RF receptacle  304  and provides an indication to a user of the system  100  as to whether or not the RF receptacle has been installed in the system. In this manner, the installation engine  5902  facilitates the installation of the RF receptacle  304  into the system  100 . 
     In an exemplary embodiment, the change of state engine  7104  monitors the operating state of the RF receptacle  304  and, upon a change in operating state, transmits information to one or more of the master nodes  102  regarding the configuration of the RF receptacle. 
     In an exemplary embodiment, the association engine  7106  is adapted to monitor and control the operation of the RF receptacle  304  when the RF receptacle is associated with one or more communication pathway  702 . 
     In an exemplary embodiment, the child protection engine  7108  is adapted to monitor and control the operation of the RF receptacle  304  when the RF receptacle is operated in a child protection mode of operation. 
     In an exemplary embodiment, the delayed off engine  7110  is adapted to monitor and control the operation of the RF receptacle  304  when the RF receptacle is operated in a delayed off mode of operation. 
     In an exemplary embodiment, the panic mode engine  7112  is adapted to monitor and control the operation of the RF receptacle  304  when the RF receptacle is operated in a panic mode of operation. 
     In an exemplary embodiment, the loss of power detection engine  7114  is adapted to monitor the operating state of the RF receptacle  304  and, upon the loss of power, save the operating state of the RF receptacle  304  into the non volatile memory  6906 . Upon the resumption of power to the RF receptacle  304 , the loss of power detection engine  7114  then retrieves the stored operating state of the RF receptacle  304  from the non volatile memory  6906  and restores the operating state of the RF receptacle. 
     In an exemplary embodiment, the memory  6904 , including the non volatile memory  6906 , is operably coupled to and controlled and monitored by the controller  6902 . In an exemplary embodiment, as illustrated in  FIG. 72 , the memory  6904 , including the non volatile memory  6906 , includes a copy of the operating system  7202 , a copy of the application programs  7204 , a device database  7206 , a scenes database  7208 , an events database  7210 , an away database  7212 , and a system database  7214 . In an exemplary embodiment, the memory  6904  includes a model 24 LC256 memory, commercially available from Microchip. In an exemplary embodiment, the non volatile memory  6906  includes a model 24 LC256 memory, commercially available from Microchip. 
     In an exemplary embodiment, the device database  7206  includes information that is specific to the RF receptacle  304 . In an exemplary embodiment, as illustrated in  FIG. 73 , the device database  7206  includes the node information frame  1702  for the RF receptacle  304 , an association database  7302  for the RF receptacle, a child protection database  7304  for the RF receptacle, a delayed off database  7306  for the RF receptacle, a panic database  7308  for the RF receptacle, and an operating state database  7310  for the RF receptacle  304 . In an exemplary embodiment, the association database  7302  for the RF receptacle  304  includes information regarding the communication pathways  702  associated with the RF receptacle. In an exemplary embodiment, the child protection database  7304  for the RF receptacle  304  includes information regarding the operating characteristics of the RF receptacle when child protection is enabled. In an exemplary embodiment, the delayed off database  7306  for the RF receptacle  304  includes information regarding the operating characteristics of the RF receptacle when delayed off is enabled. In an exemplary embodiment, the panic database  7308  for the RF receptacle  304  includes information regarding the operating characteristics of the RF receptacle when panic is enabled. In an exemplary embodiment, the operating state database  7310  for the RF receptacle  304  includes information representative of the operating state of the RF receptacle. 
     In an exemplary embodiment, the device database  7206  includes one or more of the following information: 
     
       
         
               
               
               
               
               
             
               
               
               
               
               
             
           
               
                   
               
               
                   
                   
                   
                 Default 
                   
               
               
                 Parameter 
                 Offset 
                 Size 
                 Value 
                 Description 
               
               
                   
               
             
             
               
                   
               
             
          
           
               
                 Child 
                 1 
                 1 
                 0 
                 This is the child protection 
               
               
                 Protection 
                   
                   
                   
                 mode of operation for the RF 
               
               
                 Mode 
                   
                   
                   
                 receptacle 304. 
               
               
                 Off Delay 
                 2 
                 1 
                 10 
                 This is the number of seconds 
               
               
                   
                   
                   
                   
                 that the RF receptacle 304 
               
               
                   
                   
                   
                   
                 will flash the LED indicator 
               
               
                   
                   
                   
                   
                 6916 before switching off one 
               
               
                   
                   
                   
                   
                 or both of the loads, 6928 
               
               
                   
                   
                   
                   
                 and/or 6930. 
               
               
                 Panic On 
                 3 
                 1 
                 1 
                 This is the number of seconds 
               
               
                 Time 
                   
                   
                   
                 the loads, 6928 and/or 6930, 
               
               
                   
                   
                   
                   
                 will be on while in panic 
               
               
                   
                   
                   
                   
                 mode. 
               
               
                 Panic Off 
                 4 
                 1 
                 1 
                 This is the number of seconds 
               
               
                 Time 
                   
                   
                   
                 the loads, 6928 and/or 6930, 
               
               
                   
                   
                   
                   
                 will be off while in panic 
               
               
                   
                   
                   
                   
                 mode. 
               
               
                 Load State 
                 5 
                 1 
                 0 
                 This is the operational state 
               
               
                   
                   
                   
                   
                 of the loads, 6928 and/or 
               
               
                   
                   
                   
                   
                 6930. The default value is 
               
               
                   
                   
                   
                   
                 for the loads, 6928 and/or 
               
               
                   
                   
                   
                   
                 6930, to be OFF. 
               
               
                 All Switch 
                 6 
                 1 
                 0xFF 
                 This is the state of the 
               
               
                 State 
                   
                   
                   
                 loads, 6928 and/or 6930, 
               
               
                   
                   
                   
                   
                 inclusion in the all switch 
               
               
                   
                   
                   
                   
                 group. The default is for the 
               
               
                   
                   
                   
                   
                 loads, 6928 and/or 6930, to be 
               
               
                   
                   
                   
                   
                 included for both All ON and 
               
               
                   
                   
                   
                   
                 All OFF. 
               
               
                 Location 
                 7 
                 25 
                 Duplex 
                 This is the location name. 
               
               
                   
                   
                   
                 Receptacle 
                 There is a maximum of 24 
               
               
                   
                   
                   
                   
                 characters plus a null 
               
               
                   
                   
                   
                   
                 terminator. 
               
               
                 Load Boot 
                 32 
                 1 
                 LAST 
                 This is the state the loads, 
               
               
                 State 
                   
                   
                 VALUE 
                 6928 and/or 6930, takes on 
               
               
                   
                   
                   
                   
                 booting up the RF receptacle 
               
               
                   
                   
                   
                   
                 304. 
               
               
                 Panic Mode 
                 33 
                 1 
                 Enabled 
                 This controls whether Panic 
               
               
                 Enable 
                   
                   
                   
                 Mode is enabled or disabled 
               
               
                   
                   
                   
                   
                 for the loads, 6928 and/or 
               
               
                   
                   
                   
                   
                 6930. 
               
               
                   
               
             
          
         
       
     
     In an exemplary embodiment, the scenes database  7208  includes information regarding the scenes  802  that include the RF receptacle  304 . In an exemplary embodiment, the events database  7210  includes information regarding the events  1002  that include the RF receptacle  304 . In an exemplary embodiment, the away database  7212  includes information regarding the away group  1402  that includes the RF receptacle  304 . In an exemplary embodiment, the system database  7214  includes system information that includes the RF receptacle  304 . 
     In an exemplary embodiment, the RF transceiver  6908  is operably coupled to and controlled by the controller  6902 . In an exemplary embodiment, the RF transceiver  6908  transmits and receives RF communications to and from other master and slave nodes,  102  and  104 , respectively. In an exemplary embodiment, the RF transceiver  6908  may, for example, include one or more of the following: a conventional RF transceiver, and/or the model ZW0201 RF transceiver commercially available from Zensys A/S. 
     In an exemplary embodiment, the on/off switch  6910  is a conventional on/off switch and is operably coupled to and controlled and monitored by the controller  6902 . In an exemplary embodiment, the on/off switch  6910  permits an operator of the RF receptacle  304 , in combination with the system  100 , to select the desired mode of operation of the RF receptacle  304 . 
     In an exemplary embodiment, the install button  6912  is operably coupled to and controlled and monitored by the controller  6902 . In an exemplary embodiment, the install button  6912  permits an operator of the RF receptacle  304 , in combination with the system  100 , to install the RF receptacle into the system. 
     In an exemplary embodiment, the uninstall button  6914  is operably coupled to and controlled and monitored by the controller  6902 . In an exemplary embodiment, the uninstall button  6914  permits an operator of the RF receptacle  304 , in combination with the system  100 , to uninstall the RF receptacle from the system. 
     In an exemplary embodiment, the LED indicator light  6916  is operably coupled to and controlled and monitored by the controller  6902 . 
     In an exemplary embodiment, the associate button  6918  is operably coupled to and controlled and monitored by the controller  6902 . In an exemplary embodiment, the associate button  6918  permits an operator of the RF receptacle  304 , in combination with the system  100 , to associate the RF receptacle with communication pathways  702  in the system. 
     In an exemplary embodiment, the network interface  6920  is operably coupled to and controlled and monitored by the controller  6902 . In an exemplary embodiment, the network interface  6920  permits an operator of the RF receptacle  304 , in combination with the system  100 , to network the RF receptacle with one or more networks such as, for example, local area networks, wide area networks, or the Internet. 
     In an exemplary embodiment, the top plug receptacle  6922  is coupled to and controlled by the controller  6902  and is adapted to receive a conventional male plug for operably coupling the top plug receptacle to the 1 st  load  6928 . In an exemplary embodiment, the controller  6902  controllably couples or decouples the top plug receptacle  6922  to or from the power supply  6926 . In this manner, electrical power is provided to or denied to the 1 st  load  6928 . 
     In an exemplary embodiment, the bottom plug receptacle  6924  is coupled to and controlled by the controller  6902  and is adapted to receive a conventional male plug for operably coupling the bottom plug receptacle to the 2 nd  load  6930 . In an exemplary embodiment, the controller  6902  controllably couples or decouples the bottom plug receptacle  6924  to or from the power supply  6926 . In this manner, electrical power is provided to or denied to the 2 nd  load  6930 . 
     Referring to  FIG. 74 , in an exemplary embodiment, during operation of the RF receptacle  304 , the RF receptacle implements a method of installation  7400  in which, if the RF receptacle has been operably coupled to the power supply  6926 , then the LED indicator lights  6916  are operated to indicate this operational state in steps  7402  and  7404 . Then, if the RF receptacle  304  has been installed in the system  100 , then the LED indicator lights  6916  are operated to indicate this operational state in steps  7406  and  7408 . In an exemplary embodiment, the LED indicator lights  6916  flash on an off to indicate the operational state in steps  7402  and  7404 , and the LED indicator lights are turned on to indicate the operational state in steps  7406  and  7408 . In this manner, an operator of the system  100  is provided with a visual and highly effective indication of the operational state of the RF receptacle  304  that is local to the RF receptacle. This permits an installer of the RF receptacle  304 , in a large house or commercial building, with an effective means of determining the operational state of the RF receptacle  304  that is both local to the RF receptacle and avoids the need to interrogate a master node  102  to determine the operational state. 
     Referring to  FIG. 75 , in an exemplary embodiment, during operation of the RF receptacle  304 , the RF receptacle implements a method of operation  7500  in which, it is determined if a command has been received from a master node  102  to couple the power supply  6926  to one or more both of the plug receptacles,  6922  and  6944 , in step  7502 . If a command has been received from a master node  102  to couple the power supply  6926  to one or more both of the plug receptacles,  6922  and  6944 , then it is determined if the RF receptacle  304  includes a single plug receptacle or a pair of plug receptacles in step  7504 . In an exemplary embodiment, for example, the RF receptacle  304  may include: a) a pair of plug receptacle that are both operably coupled to and controlled by the controller  6902 ; b) a pair of plug receptacles with only one of the plug receptacles operably coupled to and controlled by the controller and the other plug receptacle directly coupled to the power supply  6926 ; or c) a single plug receptacle that is operably coupled to and controlled by the controller. 
     If the RF receptacle  304  includes only a single plug receptacle that is operably coupled to and controlled by the controller  6902 , then the single plug receptacle is operably coupled to the power supply  6926  in step  7506 . Alternatively, if the RF receptacle  304  includes only a pair of plug receptacles that are operably coupled to and controlled by the controller  6902 , then-both of the plug receptacles are operably coupled to the power supply  6926  in step  7508 . 
     Referring to  FIG. 76 , in an exemplary embodiment, during operation of the RF receptacle  304 , the RF receptacle implements a method of detecting a change of state  7600  in which, if the operating state of the RF receptacle has changed, then the node information frame  1702  for the RF receptacle is transmitted to one or more of the master nodes  102  of the system  100  using the RF transceiver  6908  in steps  7602  and  7604 . 
     Referring to  FIGS. 77   a - 77   b , in an exemplary embodiment, during operation of the RF receptacle  304 , the RF receptacle implements a method of association  7700  in which it is first determined if the RF receptacle is associated with a plurality of slave nodes  104 , e.g., slave nodes  104   a  and  104   b , and thereby is associated with a plurality of communication pathways, e.g., communication pathways  702   a  and  702   b , in step  7702 . If the RF receptacle  304  is associated with a plurality of slave nodes  104  and thereby is associated with a plurality of communication pathways  702 , then a communication from the source node  706  that is principally directed to, and directly affects, only one of the destination nodes  708   a , is transmitted by multicasting the communication to all of the nodes associated with the RF receptacle  304  in step  7704 . I.e., the communication is transmitted by the RF receptacle  304  through all of the communication pathways,  702   a  and  702   b , that the RF receptacle is associated with thereby transmitting the communication to the slave nodes,  104   a  and  104   b , and the destination nodes,  708   a  and  708   b . The communication is then single-casted to only the nodes directly affected by the communication in step  6406 . I.e., the communication is only transmitted by the RF receptacle  304  through the communication pathway  702   a  thereby transmitting the communication to the slave node  104   a  and the destination node  708   a . In this manner, the communication of the information to the affected nodes in the system  100  is assured by performing a multi-cast prior to a single-cast. 
     Referring to  FIG. 78 , in an exemplary embodiment, during operation of the RF receptacle  304 , the RF receptacle implements a method of child protection  7800  in which it is first determined if the RF receptacle has active child protection functionality in step  7802 . If the RF receptacle  304  has active child protection functionality, then it is then determined if the RF receptacle has sequence control or remote control child protection functionality in step  7804 . 
     If the RF receptacle  304  has sequence control child protection functionality, then, in order to permit local manual operation of the switch, a user must depress the on/off switch  6910  three times in step  7806 . If a user of the RF receptacle  304  depresses the on/off switch  6910  three times in step  7806 , then local manual operation of the RF receptacle, using the on/off switch  6910 , is permitted in step  7808 . 
     Alternatively, if the RF receptacle  304  has remote control child protection functionality, then, local manual operation of the receptacle, using the on/off switch  6910 , is not permitted. Consequently, if the RF receptacle  304  has remote control child protection functionality, then local manual operation of the receptacle, using the on/off switch  6910 , is not permitted in step  7810 . As a result, control of the RF receptacle  304  is provided by one or more of the master nodes  102  of the system  100 . 
     Referring to  FIGS. 79   a  to  79   c , in an exemplary embodiment, during operation of the RF receptacle  304 , the RF receptacle implements a method of delayed off  7900  in which it is first determined if the on/off switch  6910  of the RF receptacle is in an on position in step  7902 . If the on/off switch  6910  of the RF receptacle  304  is in an on position, then it is then determined if the RF receptacle has remote control protection in step  7904 . If the RF receptacle  304  has remote control protection, then, local manual operation of the receptacle, using the on/off switch  6910 , is not permitted. 
     If the RF receptacle  304  does not have remote control protection, then it is then determined if the RF receptacle has sequence control protection in step  7906 . If the RF receptacle  304  has sequence control protection, then, if a user of the RF receptacle depresses the on/off switch  6910  of the RF receptacle three times in step  7908  or if the RF receptacle  304  does not have sequence control protection, then it is determined if the on/off switch was depressed for at least some predefined minimum time period in step  7910 . 
     If the on/off switch  6910  of the RF receptacle  304  was depressed for at least some predefined minimum time, then it is determined if the on/off switch was also subsequently depressed in step  7912 . If the on/off switch  6910  of the RF receptacle  304  was also subsequently depressed, then one or both of the loads,  6928  and  6930 , that are operably coupled to one or more both of the plug receptacles,  6922  and  6924 , the RF receptacle are decoupled from the power supply  6926  in step  7914 . If the on/off switch  6910  of the RF receptacle  304  was not also subsequently depressed, then it is determined if the RF receptacle  304  will be controlled by one or more of the master nodes  102  in step  7916 . 
     If the RF receptacle  304  will be controlled by one or more of the master nodes  102 , then the operational state of the RF receptacle is controlled by one or more of the master nodes  102  in step  7918 . Alternatively, if the RF receptacle  304  will not be controlled by one or more of the master nodes  102 , then the LED indicator light  6916  of the RF receptacle are flashed in step  7920 . The RF receptacle  304  is then operated to turn off on or more of the loads,  6928  and  6930 , operably coupled to the RF receptacle after a predetermined time period in step  7922 , and then the LED indicator light  6916  of the RF receptacle are turned off in step  7924 . 
     Referring to  FIGS. 80   a  to  80   b , in an exemplary embodiment, during operation of the RF receptacle  304 , the RF receptacle implements a method of panic mode operation method  8000  in which it is first determined if a panic mode operation has been selected by a user of the system  100  in step  8002 . In an exemplary embodiment, a panic mode operation may be selected by a user of the system  100  by operating one or more of the master nodes  102  of the system. 
     If a panic mode operation has been selected by a user of the system  100 , then the RF receptacle  304  is operated in accordance with the operating parameters assigned to the RF receptacle during a panic mode of operation as, for example, contained within the panic database  7308 , in step  8004 . If the on/off switch  6910  of the RF receptacle  304  is then depressed in step  8006 , then the RF receptacle is operated to decouple one or both of the loads,  6928  and  6930 , from the power supply  6926  in step  8008 . The panic mode of operation is then canceled in step  8010 . 
     Alternatively, if the on/off switch  6910  of the RF receptacle  304  is not then depressed in step  8006 , then, if the panic mode of operation is canceled by a master node  102  of the system in step  8012 , then the RF receptacle is operated to decouple one or both of the loads,  6928  and  6930 , from the power supply  6926  in step  8014 . The panic mode of operation is then canceled in step  8016 . 
     Alternatively, if the panic mode of operation is not canceled by a master node  102  of the system in step  8012 , then the RF receptacle  304  is operated in accordance with the panic mode duty cycle settings for the RF receptacle contained within, for example, the panic database  7308 , in step  8018 . In an exemplary embodiment, the panic mode duty cycle settings define an amount of time to couple one or both of the loads,  6928  and  6930 , to the power supply  6926  and an amount of time to decouple one or both of the loads from the power supply. For example, if the load  6928  is a light, operation of the RF receptacle  304  in a panic mode of operation will turn the light on and off in accordance with the panic mode duty cycle settings for the RF receptacle. If a panic mode of operation is canceled by a user of the system  100  in step  8020 , then the operation of the RF receptacle  304  will return to normal in step  8022 . 
     Referring to  FIG. 81 , in an exemplary embodiment, during operation of the RF receptacle  304 , the RF receptacle implements a method of loss of power detection method  8100  in which it is first determined if a loss of power has occurred, for example, by monitoring the power supply  6926  in step  8102 . If a loss of power is detected in step  8102 , then the current operational state of the RF receptacle  304  is stored in the RF receptacle operational state database  7310  within the non-volatile memory  6906  of the RF receptacle in step  8104 . It is then determined if power has been restored to the RF receptacle  304 , for example, by monitoring the power supply  6926  in step  8106 . If power has been restored to the RF receptacle  304 , then the current operational state of the RF receptacle  304  is retrieved from the RF receptacle operational state database  7310  within the non-volatile memory  6906 , and the operational state of the RF receptacle is restored to the operational state defined within the RF receptacle operational state database  7310  in step  8108 . 
     In an exemplary embodiment, the design, operation and functionality of the on/off switch  6910 , the install button  6912 , the uninstall button  6914 , and the associate button  6918  may be combined into a single push button. 
     Referring now to  FIG. 82 , an exemplary embodiment of an RF smart dimmer  306  includes a controller  8202  that is operably coupled to: a memory  8204 , including a non-volatile memory  8206 , an RF transceiver  8208 , a light switch touch pad  8210 , an install button  8212 , an uninstall button  8214 , an LED indicator light  8216 , an associate button  8218 , a network interface  8220 , a brighten button  8222 , a dimmer button  8224 , a manual dimmer preset button  8226 , and a loss of power detector  8228 . In an exemplary embodiment, a conventional power supply  8230  is operably coupled to the RF smart dimmer  306  for powering the operation of the RF smart dimmer, and the RF smart dimmer controllably couples and decouples a load  8232  to and from the power supply. 
     In an exemplary embodiment, the controller  8202  is adapted to monitor and control the operation of the memory  8204 , including a non-volatile memory  8206 , the RF transceiver  8208 , the light switch touch pad  8210 , the install button  8212 , the uninstall button  8214 , the LED indicator light  8216 , the associate button  8218 , the network interface  8220 , the brighten button  8222 , the dimmer button  8224 , the manual dimmer preset button  8226 , and the loss of power detector  8228 . In an exemplary embodiment, the controller  8202  includes one or more of the following: a conventional programmable general purpose controller, an application specific integrated circuit (ASIC), or other conventional controller devices. In an exemplary embodiment, the controller  8202  includes a model ZW0201 controller, commercially available from Zensys A/S. 
     Referring now to  FIG. 83 , in an exemplary embodiment, the controller  8202  includes an operating system  8302 , application programs  8304 , and a boot loader  8306 . In an exemplary embodiment, the operating system  8302  includes a serial communications driver  8302   a , a memory driver  8302   b , a display driver  8302   c , and a button input driver  8302   d . In an exemplary embodiment, the serial communications driver  8302   a  controls serial communications using the RF serial transceiver  8208 , the memory driver  8302   b  controls the memory  8204 , including the non volatile memory  8206 , the display driver  8302   c  controls the LED indicator light  8216 , and the button input driver  8302   d  debounces button inputs provided by a user using one or more of: the light switch touchpad  8210 , the install button  8212 , the uninstall button  8214 , the associate button  8218 , the brighten button  8222 , the dimmer button  8224 , and the manual dimmer preset button  8226 . In an exemplary embodiment, the serial communications driver  8302   a  includes a Z-Wave™ serial API driver that implements a Z-Wave™ serial API protocol. The Z-Wave™ serial API driver that implements a Z-Wave™ serial API protocol are both commercially available from Zensys A/S. 
     In an exemplary embodiment, the application programs  8304  include a state engine  8304   a . In an exemplary embodiment, the state engine  8304   a  permits a user of one or more of the master nodes  102  to configure, control and monitor the operation of the RF smart dimmer  306 . 
     Referring now to  FIG. 84 , in an exemplary embodiment, the state engine  8304   a  includes an installation engine  8402 , a change of state engine  8404 , an association engine  8406 , a child protection engine  8408 , a delayed off engine  8410 , a panic mode engine  8412 , and a loss of power detection engine  8414 . 
     In an exemplary embodiment, the installation engine  8402  monitors the operating state of the RF smart dimmer  306  and provides an indication to a user of the system  100  as to whether or not the RF smart dimmer has been installed in the system. In this manner, the installation engine  8402  facilitates the installation of the RF smart dimmer  306  into the system  100 . 
     In an exemplary embodiment, the change of state engine  8404  monitors the operating state of the RF smart dimmer  306  and, upon a change in operating state, transmits information to one or more of the master nodes  102  regarding the configuration of the RF smart dimmer. 
     In an exemplary embodiment, the association engine  8406  is adapted to monitor and control the operation of the RF smart dimmer  306  when the RF smart dimmer is associated with one or more communication pathway  702 . 
     In an exemplary embodiment, the child protection engine  8408  is adapted to monitor and control the operation of the RF smart dimmer  306  when the RF smart dimmer is operated in a child protection mode of operation. 
     In an exemplary embodiment, the delayed off engine  8410  is adapted to monitor and control the operation of the RF smart dimmer  306  when the RF smart dimmer is operated in a delayed off mode of operation. 
     In an exemplary embodiment, the panic mode engine  8412  is adapted to monitor and control the operation of the RF smart dimmer  306  when the RF smart dimmer is operated in a panic mode of operation. 
     In an exemplary embodiment, the loss of power detection engine  8414  is adapted to monitor the operating state of the RF smart dimmer  306  and, upon the loss of power, save the operating state of the RF smart dimmer into the non volatile memory  8206 . Upon the resumption of power to the RF smart dimmer  306 , the loss of power detection engine  8414  then retrieves the stored operating state of the RF smart dimmer  306  from the non volatile memory  8206  and restores the operating state of the RF smart dimmer. 
     In an exemplary embodiment, the memory  8204 , including the non volatile memory  8206 , is operably coupled to and controlled by the controller  8202 . In an exemplary embodiment, as illustrated in  FIG. 85 , the memory  8204 , including the non volatile memory  8206 , includes a copy of the operating system  8502 , a copy of the application programs  8504 , a device database  8506 , a scenes database  8508 , an events database  8510 , an away database  8512 , and a system database  8514 . In an exemplary embodiment, the memory  8204  includes a model 24LC256 non volatile memory, commercially available from Microchip. 
     In an exemplary embodiment, the device database  8506  includes information that is specific to the RF smart dimmer  306 . In an exemplary embodiment, as illustrated in  FIG. 86 , the device database  7206  includes the node information frame  1702  for the RF smart dimmer  306 , a preset database  7302  for the RF smart dimmer, a delayed off database  7304  for the RF smart dimmer, an association database  7306  for the RF smart dimmer, a child protection database  7308  for the RF smart dimmer, a panic database  7310  for the RF smart dimmer, and an operating state database  7312  for the RF smart dimmer. In an exemplary embodiment, the preset database  7302  includes information regarding the preset levels of the RF smart dimmer  306 . In an exemplary embodiment, the delayed off database  7304  for the RF smart dimmer  306  includes information regarding the operating characteristics of the RF smart dimmer when delayed off is enabled. In an exemplary embodiment, the association database  7306  for the RF smart dimmer  306  includes information regarding the communication pathways  702  associated with the RF smart dimmer. In an exemplary embodiment, the child protection database  7308  for the RF smart dimmer  306  includes information regarding the operating characteristics of the RF smart dimmer when child protection is enabled. In an exemplary embodiment, the panic database  7310  for the RF smart dimmer  306  includes information regarding the operating characteristics of the RF smart dimmer when panic is enabled. In an exemplary embodiment, the operating state database  7312  for the RF smart dimmer  306  includes information representative of the operating state of the RF smart dimmer. 
     In an exemplary embodiment, the device database  8506  includes one or more of the following information: 
     
       
         
               
               
               
               
               
             
               
               
               
               
               
             
           
               
                   
               
               
                   
                   
                   
                 Default 
                   
               
               
                 Parameter 
                 Offset 
                 Size 
                 Value 
                 Description 
               
               
                   
               
             
             
               
                   
               
             
          
           
               
                 Child 
                 1 
                 1 
                 0 
                 This is the level of child 
               
               
                 Protection 
                   
                   
                   
                 protection for the RF smart 
               
               
                 Mode 
                   
                   
                   
                 dimmer 306. The default 
               
               
                   
                   
                   
                   
                 value of 0 corresponds to no 
               
               
                   
                   
                   
                   
                 child protection for the RF 
               
               
                   
                   
                   
                   
                 smart dimmer. 
               
               
                 Off Delay 
                 2 
                 1 
                 10 
                 This is the number of seconds 
               
               
                   
                   
                   
                   
                 that the RF smart dimmer 306 
               
               
                   
                   
                   
                   
                 will flash the LED indicator 
               
               
                   
                   
                   
                   
                 8216 before switching off the 
               
               
                   
                   
                   
                   
                 load 8232. 
               
               
                 Panic On 
                 3 
                 1 
                 1 
                 This is the number of seconds 
               
               
                 Time 
                   
                   
                   
                 the load 8232 will be on 
               
               
                   
                   
                   
                   
                 while in panic mode. 
               
               
                 Panic Off 
                 4 
                 1 
                 1 
                 This is the number of seconds 
               
               
                 Time 
                   
                   
                   
                 the load 8232 will be off 
               
               
                   
                   
                   
                   
                 while in panic mode. 
               
               
                 Load Level 
                 5 
                 1 
                 0 
                 This is the state of the load 
               
               
                   
                   
                   
                   
                 8232. The default value is 
               
               
                   
                   
                   
                   
                 for the load 8232 to be OFF. 
               
               
                 All Switch 
                 6 
                 1 
                 0 
                 This is the operational 
               
               
                 State 
                   
                   
                   
                 status of the RF smart dimmer 
               
               
                   
                   
                   
                   
                 306 with regard to inclusion 
               
               
                   
                   
                   
                   
                 in the all switch group. The 
               
               
                   
                   
                   
                   
                 default is for the RF smart 
               
               
                   
                   
                   
                   
                 dimmer 306 to be excluded 
               
               
                   
                   
                   
                   
                 from both all ON and all OFF. 
               
               
                 Location 
                 7 
                 25 
                 “Smart 
                 This is the location name. 
               
               
                   
                   
                   
                 Dimmer” 
                 There is a maximum of 24 
               
               
                   
                   
                   
                   
                 characters plus a null 
               
               
                   
                   
                   
                   
                 terminator. 
               
               
                 Power Loss 
                 32 
                 1 
                 6 
                 This is the number of zero 
               
               
                 Preset 
                   
                   
                   
                 crossings not detected that 
               
               
                   
                   
                   
                   
                 will trigger the operational 
               
               
                   
                   
                   
                   
                 state of the load 8232 level 
               
               
                   
                   
                   
                   
                 to be saved to non volatile 
               
               
                   
                   
                   
                   
                 memory 8206. 
               
               
                 Level Boot 
                 33 
                 1 
                 LAST 
                 This is the operational state 
               
               
                 State 
                   
                   
                 VALUE 
                 the load 8232 takes on boot. 
               
               
                 Panic Mode 
                 34 
                 1 
                 Enabled 
                 This controls whether Panic 
               
               
                 Enable 
                   
                   
                   
                 Mode is enabled or disabled. 
               
               
                 Associated 
                 35 
                 5 
                 0 
                 The node IDs of associated 
               
               
                 Nodes 
                   
                   
                   
                 nodes. 
               
               
                 Preset 
                 40 
                 1 
                 4 
                 The preset level of the 
               
               
                 Level 
                   
                   
                   
                 load 8232. 
               
               
                 Ramp Time 
                 41 
                 1 
                 3 
                 The number of seconds to 
               
               
                   
                   
                   
                   
                 ramp the load 8232 from 0% 
               
               
                   
                   
                   
                   
                 to 100%. 
               
               
                   
               
             
          
         
       
     
     In an exemplary embodiment, the scenes database  8508  includes information regarding the scenes  802  that include the RF smart dimmer  306 . In an exemplary embodiment, the events database  8510  includes information regarding the events  1002  that include the RF smart dimmer  306 . In an exemplary embodiment, the away database  8512  includes information regarding the away group  1402  that includes the RF smart dimmer  306 . In an exemplary embodiment, the system database  8514  includes system information that includes the RF smart dimmer  306 . 
     In an exemplary embodiment, the RF transceiver  8208  is operably coupled to and controlled and monitored by the controller  8202 . In an exemplary embodiment, the RF transceiver  8208  transmits and receives RF communications to and from other master and slave nodes,  102  and  104 , respectively. In an exemplary embodiment, the RF transceiver  8208  may, for example, include one or more of the following: a conventional RF transceiver, and/or the model ZW0201 RF transceiver commercially available from Zensys A/S. 
     In an exemplary embodiment, the light switch touch pad  8210  is a conventional light switch touch pad and is operably coupled to and controlled and monitored by the controller  8202 . In an exemplary embodiment, the light switch touch pad  8210  permits an operator of the RF switch  302 , in combination with the system  100 , to select the desired mode of operation of the load  8232 . 
     In an exemplary embodiment, the install button  8212  is operably coupled to and controlled and monitored by the controller  8202 . In an exemplary embodiment, the install button  8212  permits an operator of the RF smart dimmer  306 , in combination with the system  100 , to install the RF smart dimmer into the system. 
     In an exemplary embodiment, the uninstall button  8214  is operably coupled to and controlled and monitored by the controller  8202 . In an exemplary embodiment, the uninstall button  8214  permits an operator of the RF smart dimmer  306 , in combination with the system  100 , to uninstall the RF smart dimmer from the system. 
     In an exemplary embodiment, the LED indicator light  8216  is operably coupled to and controlled and monitored by the controller  8202 . 
     In an exemplary embodiment, the associate button  8218  is operably coupled to and controlled and monitored by the controller  8202 . In an exemplary embodiment, the associate button  8218  permits an operator of the RF smart dimmer  306 , in combination with the system  100 , to associate the RF smart dimmer with communication pathways  702  in the system. 
     In an exemplary embodiment, the network interface  8220  is operably coupled to and controlled and monitored by the controller  8202 . In an exemplary embodiment, the network interface  8220  permits RF smart dimmer  306 , in combination with the system  100 , to be networked with other device within and outside of the system. 
     In an exemplary embodiment, the brighten button  8222  is operably coupled to and controlled and monitored by the controller  8202 . In an exemplary embodiment, the brighten button  8222  permits an operator of the RF smart dimmer  306 , in combination with the system  100 , to increase the level of current provided by the power supply  8230  to the load  8232 . 
     In an exemplary embodiment, the dimming button  8224  is operably coupled to and controlled and monitored by the controller  8202 . In an exemplary embodiment, the dimming button  8224  permits an operator of the RF smart dimmer  306 , in combination with the system  100 , to decrease the level of current provided by the power supply  8230  to the load  8232 . 
     In an exemplary embodiment, the manual dimmer preset button  8226  is operably coupled to and controlled and monitored by the controller  8202 . In an exemplary embodiment, the manual dimmer preset button  8226  permits an operator of the RF smart dimmer  306 , in combination with the system  100 , to select one or more preset levels of current provided by the power supply  8230  to the load  8232 . 
     In an exemplary embodiment, the loss of power detector  8228  is operably coupled to and controlled and monitored by the controller  8202 . In an exemplary embodiment, the loss of power detector  8228  permits an operator of the RF smart dimmer  306 , in combination with the system  100 , to detect a loss of electrical power from the power supply  8230 . 
     Referring to  FIG. 87 , in an exemplary embodiment, during operation of the RF smart dimmer  306 , the RF smart dimmer implements a method of installation  8700  in which, if the RF smart dimmer has been operably coupled to the power supply  8230 , then the LED indicator lights  8216  are operated to indicate this operational state in steps  8702  and  8704 . Then, if the RF smart dimmer  306  has been installed in the system  100 , then the LED indicator lights  8216  are operated to indicate this operational state in steps  8706  and  8708 . In an exemplary embodiment, the LED indicator lights  8216  flash on an off to indicate the operational state in steps  8702  and  8704 , and the LED indicator lights  8216  are turned on to indicate the operational state in steps  8706  and  8708 . In this manner, an operator of the system  100  is provided with a visual and highly effective indication of the operational state of the RF smart dimmer  306  that is local to the RF smart dimmer. This permits an installer of the RF smart dimmer  306 , in a large house or commercial building, with an effective means of determining the operational state of the RF smart dimmer  306  that is both local to the RF smart dimmer and avoids the need to interrogate a master node  102  to determine the operational state. 
     Referring to  FIG. 88 , in an exemplary embodiment, during operation of the RF smart dimmer  306 , the RF smart dimmer implements a method of operation  8800  in which it is determined if the on/off switch  8210  of the RF smart dimmer has been depressed in step  8802 . If the on/off switch  8210  of the RF smart dimmer  306  has been depressed, then it is determined if the RF smart dimmer has been installed in the system  100  in step  8804 . If the RF smart dimmer  306  has been installed in the system  100 , then the node information frame  1702  for the RF smart dimmer is transmitted to one or more of the master nodes  102  of the system  100  using the RF transceiver  8208  in step  8806 . 
     Alternatively, if the RF smart dimmer  306  has not been installed in the system  100 , or after the node information frame  1702  for the RF smart dimmer is transmitted to one or more of the master nodes  102  of the system  100 , it is determined if the on/off switch  8210  of the RF smart dimmer has been released in step  8808 . If the on/off switch  8210  of the RF smart dimmer  306  has been released, then the RF smart dimmer operably gradually couples the power supply  8230  to the load  8232  in accordance with the preset levels in step  8810 . For example, if the load  8232  is a light, in step  8810 , the RF smart dimmer  306  gradually increases the lighting level of the light to the preset level. 
     Referring to  FIGS. 89   a  and  89   b , in an exemplary embodiment, during operation of the RF smart dimmer  306 , the RF smart dimmer implements a method of operation  8900  in which it is determined if the RF smart dimmer  306  is operably coupling the power supply  8230  to the load  8232  in step  8902 . For example, if the load  8232  is a light, in step  8902 , it is determined if the light is on. If the RF smart dimmer  306  is operably coupling the power supply  8230  to the load  8232 , then it is determined if a user of the smart dimmer  306  has depressed the brighten or dimming buttons,  8222  or  8224 , respectively, in step  8904 . If a user of the RF smart dimmer  306  has depressed the brighten or dimming buttons,  8222  or  8224 , respectively, then the RF smart dimmer increases or decreases the preset level of current supplied to the load  8232  by the power supply  8203  in step  8906 . For example, in step  8906 , if the load  8232  is a light, then, if the brighten button  8222  was depressed, the preset lighting level is increased. Alternatively, for example, in step  8906 , if the load  8232  is a light, then, if the dimming button  8224  was depressed, the preset lighting level is decreased. 
     Alternatively, if the RF smart dimmer  306  is not operably coupling the power supply  8230  to the load  8232 , then it is determined if a user of the smart dimmer  306  has depressed the brighten or dimming buttons,  8222  or  8224 , respectively, in steps  8908  and  8910 . If a user of the RF smart dimmer  306  has depressed the brighten or dimming buttons,  8222  or  8224 , respectively, then the RF smart dimmer increases or decreases the preset level of current supplied to the load  8232  by the power supply  8203  to the maximum levels in step  8912 . For example, in step  8912 , if the load  8232  is a light, then, if the brighten button  8222  was depressed, the preset lighting level is increased to maximum possible level. Alternatively, for example, in step  8912 , if the load  8232  is a light, then, if the dimming button  8224  was depressed, the preset lighting level is decreased to the minimum possible level. 
     Referring to  FIGS. 90   a  and  90   b , in an exemplary embodiment, during operation of the RF smart dimmer  306 , the RF smart dimmer implements a method of operation  9000  in which it is determined if the RF smart dimmer  306  is operably coupling the power supply  8230  to the load  8232  in step  9002 . For example, if the load  8232  is a light, in step  8902 , it is determined if the light is on. If the RF smart dimmer  306  is operably coupling the power supply  8230  to the load  8232 , then it is determined if the preset levels for the RF smart dimmer were set by one or more of the master nodes  102  in step  9004 . If the preset levels for the RF smart dimmer  306  were set by one or more of the master nodes  102 , then level of current supplied by the power supply  8230  to the load  8232  is set to the preset level defined by the master nodes  102  in step  9006 . For example, if the load  8232  is a light, then, in step  9006 , the lighting level of the light is set to the preset lighting levels defined by the master nodes  102 . 
     Alternatively, if the RF smart dimmer  306  is not operably coupling the power supply  8230  to the load  8232 , then it is determined if any of the master nodes  102  have directed the RF smart dimmer to operably couple the power supply  8230  to the load  8232  in step  9008 . If any of the master nodes  102  have directed the RF smart dimmer  306  to operably couple the power supply  8230  to the load  8232 , then the RF smart dimmer couples the power supply  8230  to the load  8232  using the preset current levels contained within the preset database  7302  of the device database  7206  of the non volatile memory  8206  of the RF smart dimmer in step  9010 . 
     Referring to  FIG. 91 , in an exemplary embodiment, during operation of the RF smart dimmer  306 , the RF smart dimmer implements a method of operation  9100  in which it is determined if the RF smart dimmer  306  is operably coupling the power supply  8230  to the load  8232  in step  9102 . For example, if the load  8232  is a light, in step  9102 , it is determined if the light is on. If the RF smart dimmer  306  is not operably coupling the power supply  8230  to the load  8232 , then it is determined if the on/off switch  8210  of the RF smart dimmer has been depressed for at least some preset time in step  9104 . If the on/off switch  8210  of the RF smart dimmer  306  has been depressed for at least some preset time, then RF smart dimmer is operated to supply the maximum level of current from the power supply  8230  to the load  8232  in step  9106 . For example, if the load  8232  is a light, then, in step  9106 , the lighting level of the light is set to the maximum possible level. 
     Referring to  FIGS. 92   a  to  92   c , in an exemplary embodiment, during operation of the RF smart dimmer  306 , the RF smart dimmer implements a method of delayed off  9200  in which it is first determined if the touchpad  8210  of the RF smart dimmer is in an on position in step  9202 . If the touchpad  8210  of the RF smart dimmer  306  is in an on position, then it is then determined if the RF smart dimmer has remote control protection in step  9204 . If the RF smart dimmer  306  has remote control protection, then, local manual operation of the RF smart dimmer is not permitted. 
     If the RF smart dimmer  306  does not have remote control protection, then it is then determined if the RF smart dimmer has sequence control protection in step  9206 . If the RF smart dimmer  306  has sequence control protection, then, if a user of the RF smart dimmer depresses the touchpad  8210  of the RF smart dimmer three times in step  9208  or if the RF smart dimmer does not have sequence control protection, then it is determined if the touchpad was depressed for at least some predefined minimum time period in step  9210 . 
     If the touchpad  8210  of the RF smart dimmer  306  was depressed for at least some predefined minimum time, then it is determined if the touchpad was also subsequently depressed in step  9212 . If the touchpad  8210  of the RF smart dimmer  306  was also subsequently depressed, then the load  8232  that is operably coupled to the RF smart dimmer  306  is turned off in step  9214 . If the touchpad  8210  of the RF smart dimmer  306  was not also subsequently depressed, then it is determined if the RF smart dimmer  306  will be controlled by one or more of the master nodes  102  in step  9216 . 
     If the RF smart dimmer  306  will be controlled by one or more of the master nodes  102 , then the operational state of the RF smart dimmer is controlled by one or more of the master nodes  102  in step  9218 . Alternatively, if the RF smart dimmer  306  will not be controlled by one or more of the master nodes  102 , then the LED indicator light  8216  of the RF smart dimmer are flashed in step  9220 . The RF smart dimmer  306  is then operated to turn off the load  8232  operably coupled to the RF smart dimmer after a predetermined time period in step  9222 , and then the LED indicator light  8216  of the RF smart dimmer are turned off in step  9224 . 
     Referring to  FIGS. 93   a - 93   b , in an exemplary embodiment, during operation of the RF smart dimmer  306 , the RF smart dimmer implements a method of association  9300  in which it is first determined if the RF smart dimmer is associated with a plurality of slave nodes  104 , e.g., slave nodes  104   a  and  104   b , and thereby is associated with a plurality of communication pathways, e.g., communication pathways  702   a  and  702   b , in step  6402 . If the RF smart dimmer  306  is associated with a plurality of slave nodes  104  and thereby is associated with a plurality of communication pathways  702 , then a communication from the source node  706  that is principally directed to, and directly affects, only one of the destination nodes  708   a , is transmitted by multicasting the communication to all of the nodes associated with the RF smart dimmer in step  9304 . I.e., the communication is transmitted by the RF smart dimmer  306  through all of the communication pathways,  702   a  and  702   b , that the RF smart dimmer is associated with thereby transmitting the communication to the slave nodes,  104   a  and  104   b , and the destination nodes,  708   a  and  708   b . The communication is then single-casted to only the nodes directly affected by the communication in step  9306 . I.e., the communication is only transmitted by the RF smart dimmer  306  through the communication pathway  702   a  thereby transmitting the communication to the slave node  104   a  and the destination node  708   a . In this manner, the communication of the information to the affected nodes in the system  100  is assured by performing a multi-cast prior to a single-cast. 
     Referring to  FIG. 94 , in an exemplary embodiment, during operation of the RF smart dimmer  306 , the RF smart dimmer implements a method of child protection  9400  in which it is first determined if the RF smart dimmer has active child protection functionality in step  9402 . If the RF smart dimmer  306  has active child protection functionality, then it is then determined if the RF smart dimmer has sequence control or remote control child protection functionality in step  9404 . 
     If the RF smart dimmer  306  has sequence control child protection functionality, then, in order to permit local manual operation of the switch, a user must depress the touchpad  8210  three times in step  9406 . If a user of the RF smart dimmer  306  depresses the touchpad  8210  three times in step  9406 , then local manual operation of the RF smart dimmer is permitted in step  9408 . 
     Alternatively, if the RF smart dimmer  306  has remote control child protection functionality, then, local manual operation of the RF smart dimmer is not permitted. Consequently, if the RF smart dimmer  306  has remote control child protection functionality, then local manual operation of the RF smart dimmer is not permitted in step  9410 . As a result, control of the RF smart dimmer  306  is provided by one or more of the master nodes  102  of the system  100 . 
     Referring to  FIGS. 95   a  to  95   b , in an exemplary embodiment, during operation of the RF smart dimmer  306 , the RF smart dimmer implements a method of panic mode operation method  9500  in which it is first determined if a panic mode operation has been selected by a user of the system  100  in step  9502 . In an exemplary embodiment, a panic mode operation may be selected by a user of the system  100  by operating one or more of the master nodes  102  of the system. 
     If a panic mode operation has been selected by a user of the system  100 , then the RF smart dimmer  306  is operated in accordance with the operating parameters assigned to the RF smart dimmer during a panic mode of operation as, for example, contained within the panic database  7310 , in step  9504 . If the touchpad  8210  of the RF smart dimmer  306  is then depressed in step  9506 , then the RF smart dimmer is operated to decouple the load  8232  from the power supply  8230  in step  9508 . The panic mode of operation is then canceled in step  9510 . 
     Alternatively, if the touchpad  8210  of the RF smart dimmer  306  is not then depressed in step  9506 , then, if the panic mode of operation is canceled by a master node  102  of the system in step  9512 , then the RF smart dimmer is operated to decouple the load  8232  from the power supply  8230  in step  9514 . The panic mode of operation is then canceled in step  9516 . 
     Alternatively, if the panic mode of operation is not canceled by a master node  102  of the system in step  9512 , then the RF smart dimmer  306  is operated in accordance with the panic mode duty cycle settings for the RF smart dimmer contained within, for example, the panic database  7310 , in step  9518 . In an exemplary embodiment, the panic mode duty cycle settings define an amount of time to couple the load  8232  to the power supply  8230  and an amount of time to decouple the load from the power supply. For example, if the load  8232  is a light, operation of the RF smart dimmer  306  in a panic mode of operation will turn the light on and off in accordance with the panic mode duty cycle settings for the RF smart dimmer. If a panic mode of operation is canceled by a user of the system  100  in step  9520 , then the operation of the RF smart dimmer  306  will return to normal in step  9522 . 
     Referring to  FIG. 96 , in an exemplary embodiment, during operation of the RF smart dimmer  306 , the RF smart dimmer implements a method of loss of power detection method  9600  in which it is first determined if a loss of power has occurred, for example, by monitoring the power supply  8230  in step  9602 . If a loss of power is detected in step  9602 , then the current operational state of the RF smart dimmer  306  is stored in the RF smart dimmer operational state database  7312  within the non-volatile memory  8206  of the RF smart dimmer in step  9604 . It is then determined if power has been restored to the RF smart dimmer  306 , for example, by monitoring the power supply  8230  in step  9606 . If power has been restored to the RF smart dimmer  306 , then the current operational state of the RF smart dimmer is retrieved from the RF switch operational state database  7312  within the non-volatile memory  8206 , and the operational state of the RF smart dimmer is restored to the operational state defined within the RF smart dimmer operational state database  7312  in step  9608 . 
     In an exemplary embodiment, the design, operation and functionality of the on/off switch  8210 , the install button  8212 , the uninstall button  8214 , and the associate button  8218  may be combined into a single push button. 
     Referring now to  FIG. 97 , an exemplary embodiment of a battery powered RF switch  308  includes a controller  9702  that is operably coupled to: a memory  9704 , including a non-volatile memory  9706 , an RF transceiver  9708 , a light switch touch pad  9710 , an install button  9712 , an uninstall button  9714 , an LED indicator light  9716 , an associate button  9718 , a network interface  9720 , and a battery  9722 . In an exemplary embodiment, the battery powered RF switch  308  is operably coupled to and controls the operation of a device that is associated with the battery powered RF switch such as, for example, an RF receptacle  9724  that controllably operably couples a load  9726  to a power supply  9728 . 
     In an exemplary embodiment, the controller  9702  is adapted to monitor and control the operation of the memory  9704  including a non-volatile memory  9706 , the RF transceiver  9708 , the light switch touch pad  9710 , the install button  9712 , the uninstall button  9714 , the LED indicator light  9716 , the associate button  9718 , and the network interface  9720 . In an exemplary embodiment, the controller  9702  includes one or more of the following: a conventional programmable general purpose controller, an application specific integrated circuit (ASIC), or other conventional controller devices. In an exemplary embodiment, the controller  9702  includes a model ZW0201 controller, commercially available from Zensys A/S. 
     Referring now to  FIG. 98 , in an exemplary embodiment, the controller  9702  includes an operating system  9802 , application programs  9804 , and a boot loader  9806 . In an exemplary embodiment, the operating system  9802  includes a serial communications driver  9802   a , a memory driver  9802   b , a display driver  9802   c , and a button input driver  9802   d . In an exemplary embodiment, the serial communications driver  9802   a  controls serial communications using the RF serial transceiver  9708 , the memory driver  9802   b  controls the memory  9704 , including the non volatile memory  9706 , the display driver  9802   c  controls the LED indicator light  9716 , and the button input driver  9802   d  debounces button inputs provided by a user using one or more of: the light switch touchpad  9710 , the install button  9712 , the uninstall button  9714 , and the associate button  9718 . In an exemplary embodiment, the serial communications driver  9802   a  includes a Z-Wave™ serial API driver that implements a Z-Wave™ serial API protocol. The Z-Wave™ serial API driver that implements a Z-Wave™ serial API protocol are both commercially available from Zensys A/S. 
     In an exemplary embodiment, the application programs  9804  include a state engine  9804   a . In an exemplary embodiment, the state engine  9804   a  permits a user of one or more of the master nodes  102  to configure, control and monitor the operation of the battery powered RF switch  308 . 
     Referring now to  FIG. 99 , in an exemplary embodiment, the state engine  9804   a  includes an installation engine  9902 , a change of state engine  9904 , an association engine  9906 , a child protection engine  9908 , a delayed off engine  9910 , a panic mode engine  9912 , and a loss of power detection engine  9914 . 
     In an exemplary embodiment, the installation engine  9902  monitors the operating state of the battery powered RF switch  308  and provides an indication to a user of the system  100  as to whether or not the battery powered RF switch has been installed in the system. In this manner, the installation engine  9902  facilitates the installation of the battery powered RF switch  308  into the system  100 . 
     In an exemplary embodiment, the change of state engine  9904  monitors the operating state of the battery powered RF switch  308  and, upon a change in operating state, transmits information to one or more of the master nodes  102  regarding the configuration of the battery powered RF switch. 
     In an exemplary embodiment, the association engine  9906  is adapted to monitor and control the operation of the battery powered RF switch  308  when the battery powered RF switch is associated with one or more communication pathway  702 . 
     In an exemplary embodiment, the child protection engine  9908  is adapted to monitor and control the operation of the battery powered RF switch  308  when the battery powered RF switch is operated in a child protection mode of operation. 
     In an exemplary embodiment, the delayed off engine  9910  is adapted to monitor and control the operation of the battery powered RF switch  308  when the battery powered RF switch is operated in a delayed off mode of operation. 
     In an exemplary embodiment, the panic mode engine  9912  is adapted to monitor and control the operation of the battery powered RF switch  308  when the battery powered RF switch is operated in a panic mode of operation. 
     In an exemplary embodiment, the loss of power detection engine  9914  is adapted to monitor the operating state of the battery powered RF switch  308  and, upon the loss of power, save the operating state of the battery powered RF switch into the non volatile memory  9706 . Upon the resumption of power to the battery powered RF switch  308 , the loss of power detection engine  9914  then retrieves the stored operating state of the battery powered RF switch  308  from the non volatile memory  9706  and restores the operating state of the battery powered RF switch. 
     In an exemplary embodiment, the memory  9704 , including the non volatile memory  9706 , is operably coupled to and controlled by the controller  9702 . In an exemplary embodiment, as illustrated in  FIG. 100 , the memory  9704 , including the non volatile memory  9706 , includes a copy of the operating system  10002 , a copy of the application programs  10004 , a device database  10006 , a scenes database  10008 , an events database  10010 , an away database  10012 , and a system database  10014 . In an exemplary embodiment, the memory  9704  includes a model 24LC256 non volatile memory, commercially available from Microchip. 
     In an exemplary embodiment, the device database  10006  includes information that is specific to the battery powered RF switch  308 . In an exemplary embodiment, as illustrated in  FIG. 101 , the device database  10006  includes the node information frame  1702  for the battery powered RF switch  308 , an association database  10102  for the battery powered RF switch, a child protection database  10104  for the battery powered RF switch, a delayed off database  10106  for the battery powered RF switch, a panic database  10108  for the battery powered RF switch, and an operating state database  10110  for the battery powered RF switch. In an exemplary embodiment, the association database  10102  for the battery powered RF switch  308  includes information regarding the communication pathways  702  associated with the battery powered RF switch. In an exemplary embodiment, the child protection database  10104  for the battery powered RF switch  308  includes information regarding the operating characteristics of the battery powered RF switch when child protection is enabled. In an exemplary embodiment, the delayed off database  10106  for the battery powered RF switch  308  includes information regarding the operating characteristics of the battery powered RF switch when delayed off is enabled. In an exemplary embodiment, the panic database  10108  for the battery powered RF switch  308  includes information regarding the operating characteristics of the battery powered RF switch when panic is enabled. In an exemplary embodiment, the operating state database  10110  for the battery powered RF switch  308  includes information representative of the operating state of the battery powered RF switch. 
     In an exemplary embodiment, the scenes database  10008  includes information regarding the scenes  802  that include the battery powered RF switch  308 . In an exemplary embodiment, the events database  10010  includes information regarding the events  1002  that include the battery powered RF switch  308 . In an exemplary embodiment, the away database  10012  includes information regarding the away group  1402  that includes the battery powered RF switch  308 . In an exemplary embodiment, the system database  10014  includes system information that includes the battery powered RF switch  308 . 
     In an exemplary embodiment, the RF transceiver  9708  is operably coupled to and controlled by the controller  9702 . In an exemplary embodiment, the RF transceiver  9708  transmits and receives RF communications to and from other master and slave nodes,  102  and  104 , respectively. In an exemplary embodiment, the RF transceiver  9708  may, for example, include one or more of the following: a conventional RF transceiver, and/or the model ZW0201 RF transceiver commercially available from Zensys A/S. 
     In an exemplary embodiment, the light switch touch pad  9710  is a conventional light switch touch pad and is operably coupled to and controlled and monitored and monitored by the controller  9702 . In an exemplary embodiment, the light switch touch pad  9710  permits an operator of the battery powered RF switch  308 , in combination with the system  100 , to select the desired mode of operation of the receptacle  9724  and, correspondingly, the load  9726 . 
     In an exemplary embodiment, the install button  9712  is operably coupled to and controlled and monitored by the controller  9702 . In an exemplary embodiment, the install button  9712  permits an operator of the battery powered RF switch  308 , in combination with the system  100 , to install the battery powered RF switch into the system. 
     In an exemplary embodiment, the uninstall button  9714  is operably coupled to and controlled and monitored by the controller  9702 . In an exemplary embodiment, the uninstall button  9714  permits an operator of the battery powered RF switch  308 , in combination with the system  100 , to uninstall the battery powered RF switch from the system. 
     In an exemplary embodiment, the LED indicator light  9716  is operably coupled to and controlled and monitored by the controller  9702 . 
     In an exemplary embodiment, the associate button  9718  is operably coupled to and controlled and monitored by the controller  9702 . In an exemplary embodiment, the associate button  9718  permits an operator of the battery powered RF switch  308 , in combination with the system  100 , to associate the battery powered RF switch with communication pathways  702  in the system. 
     In an exemplary embodiment, the network interface  9720  is operably coupled to and controlled and monitored by the controller  9702 . In an exemplary embodiment, the network interface  9720  permits an operator of the battery powered RF switch  308  to network the battery operated RF switch with one or more elements within or outside of the system. 
     In an exemplary embodiment, the battery  9722  is operably coupled to, and provides electrical power to, all of the elements of the battery powered RF switch  308 . In several exemplary embodiments, the battery  9722  is combined, or substituted, with other types of portable power supplies such as, for example, solar power. In several exemplary embodiments, the battery  9722  is combined, or substituted, with other types of portable power generation such as, for example, power generated by capturing the kinetic energy input into the on/off switch  9710  to generate electrical power. 
     Referring to  FIG. 102 , in an exemplary embodiment, during operation of the battery powered RF switch  308 , the battery powered RF switch implements a method of installation  10200  in which, if the battery powered RF switch has been operably coupled to the battery  9722 , then the LED indicator lights  9716  are operated to indicate this operational state in steps  10202  and  10204 . Then, if the battery powered RF switch  308  has been installed in the system  100 , then the LED indicator lights  9716  are operated to indicate this operational state in steps  10206  and  10208 . In an exemplary embodiment, the LED indicator lights  9716  flash on an off to indicate the operational state in steps  10202  and  10204 , and the LED indicator lights  9716  are turned on to indicate the operational state in steps  10206  and  10208 . In this manner, an operator of the system  100  is provided with a visual and highly effective indication of the operational state of the battery powered RF switch  308  that is local to the battery powered RF switch. This permits an installer of the battery powered RF switch  308 , in a large house or commercial building, with an effective means of determining the operational state of the battery powered RF switch that is both local to the battery powered RF switch and avoids the need to interrogate a master node  102  to determine the operational state. 
     Referring to  FIG. 103 , in an exemplary embodiment, during operation of the battery powered RF switch  308 , the battery powered RF switch implements a method of detecting a change of state  10300  in which, if the operating state of the battery powered RF switch has changed, then the node information frame  1702  for the battery powered RF switch is transmitted to one or more of the master nodes  102  of the system  100  using the RF transceiver  9708  in steps  10302  and  10304 . 
     Referring to  FIGS. 104   a - 104   b , in an exemplary embodiment, during operation of the battery powered RF switch  308 , the battery powered RF switch  308  implements a method of association  10400  in which it is first determined if the battery powered RF switch is associated with a plurality of slave nodes  104 , e.g., slave nodes  104   a  and  104   b , and thereby is associated with a plurality of communication pathways, e.g., communication pathways  702   a  and  702   b , in step  6402 . If the battery powered RF switch  308  is associated with a plurality of slave nodes  104  and thereby is associated with a plurality of communication pathways  702 , then a communication from the source node  706  that is principally directed to, and directly affects, only one of the destination nodes  708   a , is transmitted by multicasting the communication to all of the nodes associated with the battery powered RF switch in step  10404 . I.e., the communication is transmitted by the battery powered RF switch  308  through all of the communication pathways,  702   a  and  702   b , that the battery powered RF switch is associated with thereby transmitting the communication to the slave nodes,  104   a  and  104   b , and the destination nodes,  708   a  and  708   b . The communication is then single-casted to only the nodes directly affected by the communication in step  10406 . I.e., the communication is only transmitted by the battery powered RF switch  308  through the communication pathway  702   a  thereby transmitting the communication to the slave node  104   a  and the destination node  708   a . In this manner, the communication of the information to the affected nodes in the system  100  is assured by performing a multi-cast prior to a single-cast. 
     Referring to  FIG. 105 , in an exemplary embodiment, during operation of the battery powered RF switch  308 , the battery powered RF switch implements a method of child protection  10500  in which it is first determined if the battery powered RF switch has active child protection functionality in step  10502 . If the battery powered RF switch  308  has active child protection functionality, then it is then determined if the battery powered RF switch has sequence control or remote control child protection functionality in step  10504 . 
     If the battery powered RF switch  308  has sequence control child protection functionality, then, in order to permit local manual operation of the battery powered RF switch, a user must depress the touchpad  9710  three times in step  10506 . If a user of the battery powered RF switch  308  depresses the touchpad  9710  three times in step  10506 , then local manual operation of the battery powered RF switch, using the touchpad  9710 , is permitted in step  10508 . 
     Alternatively, if the battery powered RF switch  308  has remote control child protection functionality, then, local manual operation of the battery powered RF switch, using the touchpad  9710 , is not permitted. Consequently, if the battery powered RF switch  308  has remote control child protection functionality, then local manual operation of the battery powered RF switch, using the touchpad  9710 , is not permitted in step  10510 . As a result, control of the battery powered RF switch  308  is provided by one or more of the master nodes  102  of the system  100 . 
     Referring to  FIGS. 106   a  to  106   c , in an exemplary embodiment, during operation of the battery powered RF switch  308 , the battery powered RF switch implements a method of delayed off  10600  in which it is first determined if the touchpad  9710  of the battery powered RF switch is in an on position in step  10602 . If the touchpad  9710  of the battery powered RF switch  308  is in an on position, then it is then determined if the battery powered RF switch has remote control protection in step  10604 . If the battery powered RF switch  308  has remote control protection, then, local manual operation of the battery powered RF switch, using the touchpad  9710 , is not permitted. 
     If the battery powered RF switch  308  does not have remote control protection, then it is then determined if the battery powered RF switch has sequence control protection in step  10606 . If the battery powered RF switch  308  has sequence control protection, then, if a user of the battery powered RF switch depresses the touchpad  9710  of the battery powered RF switch three times in step  10608  or if the battery powered RF switch does not have sequence control protection, then it is determined if the touchpad was depressed for at least some predefined minimum time period in step  10610 . 
     If the touchpad  9710  of the battery powered RF switch  308  was depressed for at least some predefined minimum time, then it is determined if the touchpad was also subsequently depressed in step  10612 . If the touchpad  9710  of the battery powered RF switch  308  was also subsequently depressed, then the battery powered RF switch controls the RF receptacle  9724  to turn off the load  9726  in step  10614 . If the touchpad  9710  of the battery powered RF switch  308  was not also subsequently depressed, then it is determined if the battery powered RF switch  308  will be controlled by one or more of the master nodes  102  in step  10616 . 
     If the battery powered RF switch  308  will be controlled by one or more of the master nodes  102 , then the operational state of the battery powered RF switch is controlled by one or more of the master nodes  102  in step  10618 . Alternatively, if the battery powered RF switch  308  will not be controlled by one or more of the master nodes  102 , then the LED indicator light  9716  of the battery powered RF switch are flashed in step  10620 . The battery powered RF switch  308  is then operated to control the RF receptacle  9724  to turn off the load  9726  after a predetermined time period in step  10622 , and then the LED indicator light  9716  of the battery powered RF switch are turned off in step  10624 . 
     Referring to  FIGS. 107   a  to  107   b , in an exemplary embodiment, during operation of the battery powered RF switch  308 , the battery powered RF switch implements a method of panic mode operation method  10700  in which it is first determined if a panic mode operation has been selected by abuser of the system  100  in step  10702 . In an exemplary embodiment, a panic mode operation may be selected by a user of the system  100  by operating one or more of the master nodes  102  of the system. 
     If a panic mode operation has been selected by a user of the system  100 , then the battery powered RF switch  308  is operated in accordance with the operating parameters assigned to the battery powered RF switch during a panic mode of operation as, for example, contained within the panic database  10108 , in step  10704 . If the touchpad  9710  of the battery powered RF switch  308  is then depressed in step  10706 , then the battery powered RF switch is operated to control the RF receptacle  9724  to decouple the load  9726  from the power supply  9728  in step  10708 . The panic mode of operation is then canceled in step  10710 . 
     Alternatively, if the touchpad  9710  of the battery powered RF switch  308  is not then depressed in step  10706 , then, if the panic mode of operation is canceled by a master node  102  of the system in step  10712 , then the battery powered RF switch is operated to control the RF receptacle  9724  to decouple the load  9726  from the power supply  9728  in step  10714 . The panic mode of operation is then canceled in step  10716 . 
     Alternatively, if the panic mode of operation is not canceled by a master node  102  of the system in step  10712 , then the battery powered RF switch  308  is operated in accordance with the panic mode duty cycle settings for the battery powered RF switch contained within, for example, the panic database  10108 , in step  10718 . In an exemplary embodiment, the panic mode duty cycle settings define an amount of time to operate the RF receptacle  9724  to couple the load  9726  to the power supply  9728  and an amount of time to operate the RF receptacle to decouple the load from the power supply. For example, if the load  9726  is a light, operation of the battery powered RF switch  308  in a panic mode of operation will turn the light on and off in accordance with the panic mode duty cycle settings for the battery powered RF switch. If a panic mode of operation is canceled by a user of the system  100  in step  10720 , then the operation of the battery powered RF switch  308  will return to normal in step  10722 . 
     Referring to  FIG. 108 , in an exemplary embodiment, during operation of the battery powered RF switch  308 , the battery powered RF switch implements a method of loss of power detection method  10800  in which it is first determined if a loss of power has occurred, for example, by monitoring the battery  9722  in step  10802 . If a loss of power is detected in step  10802 , then the current operational state of the battery powered RF switch  308  is stored in the battery powered RF switch operational state database  10110  within the non-volatile memory  9706  of the battery powered RF switch in step  10804 . It is then determined if battery power has been restored to the battery powered RF switch  308 , for example, by monitoring the battery  9722  in step  10806 . If battery power has been restored to the battery powered RF switch  308 , then the current operational state of the battery powered RF switch  308  is retrieved from the battery powered RF switch operational state database  10110  within the non-volatile memory  9706 , and the operational state of the battery powered RF switch is restored to the operational state defined within the battery powered RF switch operational state database  10110  in step  10808 . 
     In an exemplary embodiment, the design, operation and functionality of the on/off switch  9710 , the install button  9712 , the uninstall button  9714 , and the associate button  9718  may be combined into a single push button. 
     In an exemplary embodiment, the battery operated RF switch  308  includes one or more elements and/or operational aspects of the RF smart dimmer  306 . [ 0467 ] Referring now to  FIG. 109 , an exemplary embodiment of an RF dimmer  310  includes a controller  10902  that is operably coupled to: a memory  10904 , including a non-volatile memory  10906 , an RF transceiver  10908 , a light switch touch pad  10910 , an install button  10912 , an uninstall button  10914 , an LED indicator light  10916 , an associate button  10918 , a network interface  10920 , a brighten button  10922 , a dimmer button  10924 , and a loss of power detector  10926 . In an exemplary embodiment, a conventional power supply  10930  is operably coupled to the RF dimmer  310  for powering the operation of the RF dimmer, and the RF dimmer controllably couples and decouples a load  10932  to and from the power supply. 
     In an exemplary embodiment, the controller  10902  is adapted to monitor and control the operation of the memory  10904 , including a non-volatile memory  10906 , the RF transceiver  10908 , the light switch touch pad  10910 , the install button  10912 , the uninstall button  10914 , the LED indicator light  10916 , the associate button  10918 , the network interface  10920 , the brighten button  10922 , the dimmer button  10924 , and the loss of power detector  10926 . In an exemplary embodiment, the controller  10902  includes one or more of the following: a conventional programmable general purpose controller, an application specific integrated circuit (ASIC), or other conventional controller devices. In an exemplary embodiment, the controller  10902  includes a model ZW0201 controller, commercially available from Zensys A/S. 
     Referring now to  FIG. 110 , in an exemplary embodiment, the controller  10902  includes an operating system  11002 , application programs  11004 , and a boot loader  11006 . In an exemplary embodiment, the operating system  11002  includes a serial communications driver  11002   a , a memory driver  11002   b , a display driver  11002   c , and a button input driver  11002   d . In an exemplary embodiment, the serial communications driver  11002   a  controls serial communications using the RF serial transceiver  10908 , the memory driver  11002   b  controls the memory  10904 , including the non volatile memory  10906 , the display driver  11002   c  controls the LED indicator light  10916 , and the button input driver  11002   d  debounces button inputs provided by a user using one or more of: the light switch touchpad  10910 , the install button  10912 , the uninstall button  10914 , the associate button  10918 , the brighten button  10922 , and the dimmer button  10924 . In an exemplary embodiment, the serial communications driver  11002   a  includes a Z-Wave™ serial API driver that implements a Z-Wave™ serial API protocol. The Z-Wave™ serial API driver that implements a Z-Wave™ serial API protocol are both commercially available from Zensys A/S. 
     In an exemplary embodiment, the application programs  11004  include a state engine  11004   a . In an exemplary embodiment, the state engine  11004   a  permits a user of one or more of the master nodes  102  to configure, control and monitor the operation of the RF dimmer  310 . 
     Referring now to  FIG. 111 , in an exemplary embodiment, the state engine  11004   a  includes an installation engine  11102 , a change of state engine  11104 , an association engine  11106 , a child protection engine  11108 , a delayed off engine  11110 , a panic mode engine  11112 , and a loss of power detection engine  11114 . 
     In an exemplary embodiment, the installation engine  11102  monitors the operating state of the RF dimmer  310  and provides an indication to a user of the system  100  as to whether or not the RF dimmer has been installed in the system. In this manner, the installation engine  11102  facilitates the installation of the RF dimmer  310  into the system  100 . 
     In an exemplary embodiment, the change of state engine  11104  monitors the operating state of the RF dimmer  310  and, upon a change in operating state, transmits information to one or more of the master nodes  102  regarding the configuration of the RF dimmer. 
     In an exemplary embodiment, the association engine  11106  is adapted to monitor and control the operation of the RF dimmer  310  when the RF dimmer is associated with one or more communication pathway  702 . 
     In an exemplary embodiment, the child protection engine  11108  is adapted to monitor and control the operation of the RF dimmer  310  when the RF dimmer is operated in a child protection mode of operation. 
     In an exemplary embodiment, the delayed off engine  11110  is adapted to monitor and control the operation of the RF dimmer  310  when the RF dimmer is operated in a delayed off mode of operation. 
     In an exemplary embodiment, the panic mode engine  11112  is adapted to monitor and control the operation of the RF dimmer  310  when the RF dimmer is operated in a panic mode of operation. 
     In an exemplary embodiment, the loss of power detection engine  11114  is adapted to monitor the operating state of the RF dimmer  310  and, upon the loss of power, save the operating state of the RF dimmer into the non volatile memory  10906 . Upon the resumption of power to the RF dimmer  310 , the loss of power detection engine  11114  then retrieves the stored operating state of the RF dimmer  310  from the non volatile memory  10906  and restores the operating state of the RF dimmer. 
     In an exemplary embodiment, the memory  10904 , including the non volatile memory  10906 , is operably coupled to and controlled by the controller  10902 . In an exemplary embodiment, as illustrated in  FIG. 112 , the memory  10904 , including the non volatile memory  10906 , includes a copy of the operating system  11202 , a copy of the application programs  11204 , a device database  11206 , a scenes database  11208 , an events database  11210 , an away database  11212 , and a system database  11214 . In an exemplary embodiment, the memory  10904  includes a model 24LC256 non volatile memory, commercially available from Microchip. 
     In an exemplary embodiment, the device database  11206  includes information that is specific to the RF dimmer  310 . In an exemplary embodiment, as illustrated in  FIG. 113 , the device database  11206  includes the node information frame  1702  for the RF dimmer  310 , a delayed off database  11304  for the RF dimmer, an association database  11306  for the RF dimmer, a child protection database  11308  for the RF dimmer, a panic database  11310  for the RF dimmer, and an operating state database  11312  for the RF dimmer. In an exemplary embodiment, the delayed off database  11304  for the RF dimmer  310  includes information regarding the operating characteristics of the RF dimmer when delayed off is enabled. In an exemplary embodiment, the association database  11306  for the RF dimmer  310  includes information regarding the communication pathways  702  associated with the RF dimmer. In an exemplary embodiment, the child protection database  11308  for the RF dimmer  310  includes information regarding the operating characteristics of the RF dimmer when child protection is enabled. In an exemplary embodiment, the panic database  11310  for the RF dimmer  310  includes information regarding the operating characteristics of the RF dimmer when panic is enabled. In an exemplary embodiment, the operating state database  11312  for the RF dimmer  310  includes information representative of the operating state of the RF dimmer. 
     In an exemplary embodiment, the scenes database  11208  includes information regarding the scenes  802  that include the RF dimmer  310 . In an exemplary embodiment, the events database  11210  includes information regarding the events  1002  that include the RF dimmer  310 . In an exemplary embodiment, the away database  11212  includes information regarding the away group  1402  that includes the RF dimmer  310 . In an exemplary embodiment, the system database  11214  includes system information that includes the RF dimmer  310 . 
     In an exemplary embodiment, the RF transceiver  10908  is operably coupled to and controlled by the controller  10902 . In an exemplary embodiment, the RF transceiver  10908  transmits and receives RF communications to and from other master and slave nodes,  102  and  104 , respectively. In an exemplary embodiment, the RF transceiver  10908  may, for example, include one or more of the following: a conventional RF transceiver, and/or the model ZW0201 RF transceiver commercially available from Zensys A/S. 
     In an exemplary embodiment, the light switch touch pad  10910  is a conventional light switch touch pad and is operably coupled to and controlled and monitored by the controller  10902 . In an exemplary embodiment, the light switch touch pad  10910  permits an operator of the RF dimmer  310 , in combination with the system  100 , to select the desired mode of operation of the load  10932 . 
     In an exemplary embodiment, the install button  10912  is operably coupled to and controlled and monitored by the controller  10902 . In an exemplary embodiment, the install button  10912  permits an operator of the RF dimmer  310 , in combination with the system  100 , to install the RF dimmer into the system. 
     In an exemplary embodiment, the uninstall button  10914  is operably coupled to and controlled and monitored by the controller  10902 . In an exemplary embodiment, the uninstall button  10914  permits an operator of the RF dimmer  310 , in combination with the system  100 , to uninstall the RF dimmer from the system. 
     In an exemplary embodiment, the LED indicator light  10916  is operably coupled to and controlled and monitored by the controller  10902 . 
     In an exemplary embodiment, the associate button  10918  is operably coupled to and controlled and monitored by the controller  10902 . In an exemplary embodiment, the associate button  10918  permits an operator of the RF dimmer  310 , in combination with the system  100 , to associate the RF dimmer with communication pathways  702  in the system. 
     In an exemplary embodiment, the network interface  10920  is operably coupled to and controlled and monitored by the controller  10902 . In an exemplary embodiment, the network interface  10920  permits the RF dimmer  310 , in combination with the system  100 , to be networked with other device within and outside of the system. 
     In an exemplary embodiment, the brighten button  10922  is operably coupled to and controlled and monitored by the controller  10902 . In an exemplary embodiment, the brighten button  10922  permits an operator of the RF dimmer  310 , in combination with the system  100 , to increase the level of current provided by the power supply  10930  to the load  10932 . 
     In an exemplary embodiment, the dimming button  10924  is operably coupled to and controlled and monitored by the controller  10902 . In an exemplary embodiment, the dimming button  10924  permits an operator of the RF dimmer  310 , in combination with the system  100 , to decrease the level of current provided by the power supply  10930  to the load  10932 . 
     In an exemplary embodiment, the loss of power detector  10926  is operably coupled to and controlled and monitored by the controller  10902 . In an exemplary embodiment, the loss of power detector  10926  permits an operator of the RF dimmer  310 , in combination with the system  100 , to detect a loss of electrical power from the power supply  10930 . 
     Referring to  FIG. 114 , in an exemplary embodiment, during operation of the RF dimmer  310 , the RF dimmer implements a method of installation  11400  in which, if the RF dimmer has been operably coupled to the power supply  10230 , then the LED indicator lights  10916  are operated to indicate this operational state in steps  11402  and  11404 . Then, if the RF dimmer  310  has been installed in the system  100 , then the LED indicator lights  10916  are operated to indicate this operational state in steps  11406  and  11408 . In an exemplary embodiment, the LED indicator lights  10916  flash on an off to indicate the operational state in steps  11402  and  11404 , and the LED indicator lights  10916  are turned on to indicate the operational state in steps  11406  and  11408 . In this manner, an operator of the system  100  is provided with a visual and highly effective indication of the operational state of the RF dimmer  310  that is local to the RF dimmer. This permits an installer of the RF dimmer  310 , in a large house or commercial building, with an effective means of determining the operational state of the RF dimmer that is both local to the RF dimmer and avoids the need to interrogate a master node  102  to determine the operational state. 
     Referring to  FIG. 115 , in an exemplary embodiment, during operation of the RF dimmer  310 , the RF dimmer implements a method of operation  11500  in which it is determined if the on/off switch  10910  of the RF dimmer has been depressed in step  11502 . If the on/off switch  10910  of the RF dimmer  310  has been depressed, then it is determined if the RF dimmer has been installed in the system  100  in step  11504 . If the RF dimmer  310  has been installed in the system  100 , then the node information frame  1702  for the RF dimmer is transmitted to one or more of the master nodes  102  of the system  100  using the RF transceiver  10908  in step  11506 . 
     Alternatively, if the RF dimmer  310  has not been installed in the system  100 , or after the node information frame  1702  for the RF dimmer is transmitted to one or more of the master nodes  102  of the system  100 , it is determined if the on/off switch  10910  of the RF dimmer has been released in step  11508 . If the on/off switch  10910  of the RF dimmer  310  has been released, then the RF dimmer operably gradually couples the power supply  10930  to the load  10932  in accordance with the preset levels in step  11510 . For example, if the load  10932  is a light, in step  11510 , the RF dimmer  310  gradually increases the lighting level of the light to the preset level. 
     Referring to  FIG. 116 , in an exemplary embodiment, during operation of the RF dimmer  310 , the RF dimmer implements a method of operation  11600  in which it is determined if the RF dimmer  310  is operably coupling the power supply  10930  to the load  10932  in step  11602 . For example, if the load  10932  is a light, in step  11602 , it is determined if the light is on. If the RF dimmer  310  is operably coupling the power supply  10930  to the load  10932 , then it is determined if a user of the RF dimmer  310  has depressed the brighten or dimming buttons,  10922  or  10924 , respectively, in step  11604 . If a user of the RF dimmer  310  has depressed the brighten or dimming buttons,  10922  or  10924 , respectively, then the RF dimmer increases or decreases the level of current supplied to the load  8232  by the power supply  8203  in step  11606 . For example, in step  11606 , if the load  10932  is a light, then, if the brighten button  10922  was depressed, the lighting level is increased. Alternatively, for example, in step  11606 , if the load  10932  is a light, then, if the dimming button  10924  was depressed, the lighting level is decreased. 
     Referring to  FIGS. 117   a  to  117   c , in an exemplary embodiment, during operation of the RF dimmer  310 , the RF dimmer implements a method of delayed off  11700  in which it is first determined if the touchpad  10910  of the RF dimmer is in an on position in step  11702 . If the touchpad  10910  of the RF dimmer  310  is in an on position, then it is then determined if the RF dimmer has remote control protection in step  11704 . If the RF dimmer  310  has remote control protection, then, local manual operation of the RF dimmer is not permitted. 
     If the RF dimmer  310  does not have remote control protection, then it is then determined if the RF dimmer has sequence control protection in step  11706 . If the RF dimmer  310  has sequence control protection, then, if a user of the RF dimmer depresses the touchpad  10910  of the RF dimmer three times in step  11708  or if the RF dimmer does not have sequence control protection, then it is determined if the touchpad was depressed for at least some predefined minimum time period in step  11710 . 
     If the touchpad  11710  of the RF dimmer  310  was depressed for at least some predefined minimum time, then it is determined if the touchpad was also subsequently depressed in step  11712 . If the touchpad  10910  of the RF dimmer  310  was also subsequently depressed, then the load  10932  that is operably coupled to the RF dimmer  310  is turned off in step  11714 . If the touchpad  10910  of the RF dimmer  310  was not also subsequently depressed, then it is determined if the RF dimmer  310  will be controlled by one or more of the master nodes  102  in step  11716 . 
     If the RF dimmer  310  will be controlled by one or more of the master nodes  102 , then the operational state of the RF dimmer is controlled by one or more of the master nodes  102  in step  11718 . Alternatively, if the RF dimmer  310  will not be controlled by one or more of the master nodes  102 , then the LED indicator light  10916  of the RF dimmer are flashed in step  11720 . The RF dimmer  310  is then operated to turn off the load  10932  operably coupled to the RF dimmer after a predetermined time period in step  11722 , and then the LED indicator light  10916  of the RF dimmer are turned off in step  11724 . 
     Referring to  FIGS. 118   a - 118   b , in an exemplary embodiment, during operation of the RF dimmer  310 , the RF dimmer implements a method of association  11800  in which it is first determined if the RF dimmer is associated with a plurality of slave nodes  104 , e.g., slave nodes  104   a  and  104   b , and thereby is associated with a plurality of communication pathways, e.g., communication pathways  702   a  and  702   b , in step  11802 . If the RF dimmer  310  is associated with a plurality of slave nodes  104  and thereby is associated with a plurality of communication pathways  702 , then a communication from the source node  706  that is principally directed to, and directly affects, only one of the destination nodes  708   a , is transmitted by multicasting the communication to all of the nodes associated with the RF smart dimmer in step  9304 . I.e., the communication is transmitted by the RF dimmer  310  through all of the communication pathways,  702   a  and  702   b , that the RF dimmer is associated with thereby transmitting the communication to the slave nodes,  104   a  and  104   b , and the destination nodes,  708   a  and  708   b . The communication is then single-casted to only the nodes directly affected by the communication in step  11806 . I.e., the communication is only transmitted by the RF dimmer  310  through the communication pathway  702   a  thereby transmitting the communication to the slave node  104   a  and the destination node  708   a . In this manner, the communication of the information to the affected nodes in the system  100  is assured by performing a multi-cast prior to a single-cast. 
     Referring to  FIG. 119 , in an exemplary embodiment, during operation of the RF dimmer  310 , the RF dimmer implements a method of child protection  11900  in which it is first determined if the RF dimmer has active child protection functionality in step  11902 . If the RF dimmer  310  has active child protection functionality, then it is then determined if the RF dimmer has sequence control or remote control child protection functionality in step  11904 . 
     If the RF dimmer  310  has sequence control child protection functionality, then, in order to permit local manual operation of the RF dimmer, a user must depress the touchpad  10910  three times in step  11906 . If a user of the RF dimmer  310  depresses the touchpad  10910  three times in step  11906 , then local manual operation of the RF dimmer is permitted in step  11908 . 
     Alternatively, if the RF dimmer  310  has remote control child protection functionality, then, local manual operation of the RF dimmer is not permitted. Consequently, if the RF dimmer  310  has remote control child protection functionality, then local manual operation of the RF dimmer is not permitted in step  11910 . As a result, control of the RF dimmer  310  is provided by one or more of the master nodes  102  of the system  100 . 
     Referring to  FIGS. 120   a  to  120   b , in an exemplary embodiment, during operation of the RF dimmer  310 , the RF dimmer implements a method of panic mode operation method  12000  in which it is first determined if a panic mode operation has been selected by a user of the system  100  in step  12002 . In an exemplary embodiment, a panic mode operation may be selected by a user of the system  100  by operating one or more of the master nodes  102  of the system. 
     If a panic mode operation has been selected by a user of the system  100 , then the RF dimmer  310  is operated in accordance with the operating parameters assigned to the RF dimmer during a panic mode of operation as, for example, contained within the panic database  11310 , in step  12004 . If the touchpad  10910  of the RF dimmer  310  is then depressed in step  12006 , then the RF dimmer is operated to decouple the load  10932  from the power supply  10930  in step  12008 . The panic mode of operation is then canceled in step  12010 . 
     Alternatively, if the touchpad  10910  of the RF dimmer  310  is not then depressed in step  12006 , then, if the panic mode of operation is canceled by a master node  102  of the system in step  12012 , then the RF dimmer is operated to decouple the load  10932  from the power supply  10930  in step  12014 . The panic mode of operation is then canceled in step  12016 . 
     Alternatively, if the panic mode of operation is not canceled by a master node  102  of the system in step  12012 , then the RF dimmer  310  is operated in accordance with the panic mode duty cycle settings for the RF dimmer contained within, for example, the panic database  11310 , in step  12018 . In an exemplary embodiment, the panic mode duty cycle settings define an amount of time to couple the load  10932  to the power supply  10930  and an amount of time to decouple the load from the power supply. For example, if the load  10932  is a light, operation of the RF dimmer  310  in a panic mode of operation will turn the light on and off in accordance with the panic mode duty cycle settings for the RF dimmer. If a panic mode of operation is canceled by a user of the system  100  in step  12020 , then the operation of the RF dimmer  310  will return to normal in step  12022 . 
     Referring to  FIG. 121 , in an exemplary embodiment, during operation of the RF dimmer  310 , the RF dimmer implements a method of loss of power detection method  12100  in which it is first determined if a loss of power has occurred, for example, by monitoring the power supply  10930  in step  12102 . If a loss of power is detected in step  12102 , then the current operational state of the RF dimmer  310  is stored in the RF dimmer operational state database  11312  within the non-volatile memory  10906  of the RF dimmer in step  12104 . It is then determined if power has been restored to the RF dimmer  310 , for example, by monitoring the power supply  10930  in step  12106 . If power has been restored to the RF dimmer  310 , then the current operational state of the RF dimmer is retrieved from the RF dimmer operational state database  11312  within the non-volatile memory  10906 , and the operational state of the RF dimmer is restored to the operational state defined within the RF dimmer operational state database  11312  in step  12108 . 
     Referring to  FIG. 122 , an exemplary embodiment of an RF thermostat  312  includes a conventional commercially available RF thermostat that is operably coupled to a conventional HVAC system  12202  and a conventional power supply  12204 . In an exemplary embodiment, the RF thermostat  312  is adapted to monitor and control the operation of the HVAC system  12202  in a conventional manner while operating in the system  100  under the control of one or more of the master nodes  102 . 
     In an exemplary embodiment, the RF thermostat  312  is further adapted to implement one or more of the operational aspects of one or more of the RF switch  302 , the RF receptacle  304 , the RF smart dimmer  306 , the battery operated RF switch  308 , and the RF dimmer  310 . 
     In an exemplary embodiment, one or more of the slave nodes  104  of the system  100  are adapted to control and/or monitor the operation of one or more other slave nodes. In this manner, one or more of the slave nodes  104  of the system  100  may act as surrogate master nodes for one or more of the other slave nodes of the system. 
     Referring to  FIG. 123 , an exemplary embodiment of a control system  12300  includes the control system  100  and one or more slave nodes  12302  operably coupled to one or more of the master nodes  102  of the control system  100 . 
     Referring to  FIG. 124 , in an exemplary embodiment, one or more of the master nodes  102  include a power line communication interface (PLC)  12402  that is operably coupled to PLC interfaces  12302   a , provided in each of the slave nodes, e.g.,  12302   i ,  12302   i+1 , and  12302   N , for communication with the slave nodes, using a conventional power supply circuit  12404 , including a neutral terminal  12406 , a hot terminal  12408 , and a load  12410  coupled to the neutral and hot terminals. 
     Referring to  FIG. 125 , in an exemplary embodiment, during operation of the control system  12300 , the master node  102  communicates with one or more of the slave nodes  12302  using the loop current  12502  of the power supply circuit  12404  and the slave nodes communicate with the master node  102  using the loop voltage  12504  of the power supply circuit. In particular, master to slave communication  12506  occurs when the line voltage  12508  of the power supply circuit  12404  has zero crossings  12510  and slave to master communication  12512  occurs when the line voltage  12508  of the power supply circuit  12404  has zero crossings  12514 . 
     In an exemplary embodiment, those elements and operational aspects of the control system  12300  that relate to and support the master to slave communication  12506  and the slave to master communication  12512  are provided as disclosed in U.S. Pat. No. 6,815,625, the disclosure of which is incorporated herein by reference. 
     In an exemplary embodiment, the slave nodes  12302  of the control system  12300  include one or more of the following: the RF switch  302 , the RF receptacle  304 , the RF smart dimmer  306 , the battery operated RF switch  308 , the RF dimmer  310 , and/or the RF thermostat  312  with the network interfaces,  5720 ,  6920 ,  8220 ,  9720 ,  10920 , and/or  12220  including PLC interfaces  12302   a.    
     In an exemplary embodiment, one or more of the operational elements and/or functionalities of the systems  100  and/or  12300  are localized and/or non-localized to thereby provide a system having elements and/or functionalities that are distributed among the elements, e.g., the master and slave nodes,  102  and  104 , respectively, of the system. 
     In several exemplary embodiment, the radio frequency communication interfaces of the systems,  100  and  12300 , may in addition, or in the alternative, use other types of signals such as, for example, infrared, acoustic, or other signals that do not employ a power line conductor. 
     Referring to  FIGS. 126 and 127 , in an exemplary embodiment, the battery powered RF switch  308  includes a top housing  12702  that defines upper and lower mounting holes,  12702   a  and  12702   b , a bottom housing  12704  that defines upper and lower mounting grooves,  12704   a  and  12704   b , a printed circuit board assembly  12706  that includes switch sensor buttons  12706   a , a dimmer button  12706   b , and an LED indicator  12706   c , an on/off switch  12708 , batteries,  12710   a  and  12710   b , a battery retaining bracket  12712 , a double-sided adhesive layer  12714 , and mounting screws,  12716   a  and  12716   b.    
     Referring to  FIGS. 128 and 129 , in an exemplary embodiment, the battery powered RF switch  308  is mounted onto a surface  12800  by adhesively affixing the switch to the surface using the adhesive layer  12714 , threadably affixing the switch to the surface using the mounting screws,  12716   a  and  12716   b , and then placing a conventional switch cover face plate  12802 , over and around the periphery of the switch. In this manner, the battery powered RF switch  308  may be positioned virtually anywhere on the surface  12800 , and then easily relocate to another location on the surface or another surface entirely. 
     Referring to  FIGS. 130 and 131 , in an exemplary embodiment, the battery powered RF switch  308  may be mounted onto the surface  12800  next to a conventional wall switch  13002  and then a conventional switch cover face plate  13004  may be placed, over and around the periphery of the switches. In this manner, the battery powered RF switch  308  may be ganged with conventional wall switches. 
     Referring to  FIGS. 132 and 133 , in an exemplary embodiment, the battery powered RF switch  308  may be mounted onto the surface  12800  next to a plurality of conventional wall switches,  13002   a  and  13002   b , and then a conventional switch cover face plate  13202  may be placed, over and around the periphery of the switches. In this manner, the battery powered RF switch  308  may be ganged with a plurality of conventional wall switches. 
     Referring now to  FIGS. 134   a - 134   b , in an exemplary embodiment, during the operation of the hand held RF controller  202 , after a user sequentially selects DEVICES  2004  and ASSOCIATE  2004   b , using the menu-based program  2000 , the controller implements a method  13400  in which the controller permits a user to associate devices, such as, for example, master and slave nodes,  102  and  104 , respectively, to define a communication pathway  702  within the system  100 . In particular, in step  13402  a user of the hand held RF controller  202  may select a source node  706  for the communication pathway  702 . After a user of the hand held RF controller  202  selects a source node  706  for the communication pathway  702 , if the source node is a battery power device such as, for example, the battery powered RF switch  308 , the user of the hand held RF controller  202  will then depress the associate button on the battery powered source node  706  in step  13406 . 
     If the source node  706  is not a battery power device or after the user of the hand held RF controller  202  has depressed the associate button on the battery powered source node, then the user of the hand held RF controller may select a destination node  708  for the communication pathway  702  in step  13408 . After a user of the hand held RF controller  202  has selected a destination node  708  for the communication pathway  702 , then the configuration of the communication pathways is loaded into respective memories of the controller, the source node  706 , and the destination node in step  13410 . 
     It is understood that variations may be made in the foregoing without departing from the scope of the disclosure. 
     Any foregoing spatial references such as, for example, “upper,” “lower,” “above,” “below,” “rear,” “between,” “vertical,” “angular,” etc., are for the purpose of illustration only and do not limit the specific orientation or location of the structure described above. 
     In several exemplary embodiments, it is understood that one or more of the operational steps in each embodiment may be omitted. Moreover, in some instances, some features of the present disclosure may be employed without a corresponding use of the other features. Moreover, it is understood that one or more of the above-described embodiments and/or variations may be combined in whole or in part with any one or more of the other above-described embodiments and/or variations. 
     Although exemplary embodiments of this disclosure have been described in detail above, those skilled in the art will readily appreciate that many other modifications, changes and/or substitutions are possible in the exemplary embodiments without materially departing from the novel teachings and advantages of this disclosure. Accordingly, all such modifications, changes and/or substitutions are intended to be included within the scope of this disclosure as defined in the following claims. In the claims, means-plus-function clauses are intended to cover the structures described herein as performing the recited function and not only structural equivalents, but also equivalent structures.