Debugging the Load Control System

Abstract

The present invention relates to a debugging load control system. A load control system may include a control device for controlling the power supplied to an electrical load. The control device may include a control source device and a control target device. The control target device may control the power supplied to the electrical load based on a digital message received from the control source device. The control device may include a load control discovery device capable of sending discovery messages configured to discover control devices within a location. The discovered control devices may be organized by signal strength and provided to a network device to enable association of the discovered control devices within the location. Discovery messages may be sent within an established discovery range. The discovery range may be adjusted to discover different control devices. Different control devices may be identified as load control discovery devices for discovering different control devices.

Description

[0001] This application is a divisional application of the patent application with the application number 201680070358.9 (PCT / US2016 / 059590), the international filing date of which is October 28, 2016, and the invention title of which is "Debugging a Load Control System", and was filed on May 31, 2018.

[0002] Cross - reference to Related Applications

[0003] This application claims priority to U.S. Provisional Patent Application No. 62 / 249,117, filed on October 30, 2015; U.S. Provisional Patent Application No. 62 / 279,409, filed on January 15, 2016; and U.S. Provisional Patent Application No. 62 / 326,466, filed on April 22, 2016. Background Art

[0004] A user environment (such as a residential or office building) can be configured using various types of load control systems. A lighting control system can be used to control lighting loads in the user environment. An electric window covering control system can be used to control the natural light provided to the user environment. A heating, ventilation, and air conditioning (HVAC) system can be used to control the temperature in the user environment.

[0005] Each load control system can include various control devices, including input devices and load control devices. The load control device can receive digital messages, which can include load control instructions for controlling an electrical load from one or more input devices. The load control device can be capable of directly controlling the electrical load. The input device can be capable of indirectly controlling the electrical load via the load control device.

[0006] Examples of load control devices can include lighting control devices (e.g., dimmer switches, electronic switches, ballasts, or light - emitting diode (LED) drivers), electric window coverings, temperature control devices (e.g., thermostats), AC plug - in load control devices, etc. Examples of input devices can include remote control devices, occupancy sensors, daylight sensors, temperature sensors, and / or the like.

[0007] In order for the load control device to identify the instructions received from the input device, the load control system can be debugged so that the load control device can recognize the digital messages received from the input device. As part of the debugging of the load control system, the load control device and the input device can be configured so that these devices are associated with each other for recognizing the messages transmitted between the associated devices and performing load control based on such messages.

[0008] Some prior art commissioning processes allow for the implementation of advanced features (e.g., demand response, whole building control, energy consumption reporting, etc.) during the normal operation of a load control system. However, these processes can be very time-consuming and complex, and require a trained commissioning agency to complete the commissioning process. Before the commissioning process can be initiated, a database defining the control devices, the relationships (e.g., associations) between the control devices, and the operation of the control devices of the load control system must be created using, for example, a computer. Therefore, trained personnel must identify each of the control devices to be installed in a building for performing load control, generate the associations between the control devices, and use a computer to program the operation of the control devices to generate the database prior to the commissioning process. Then during the commissioning process, one or more trained commissioning agents must download the database to the control devices of the load control system and then map the programming in the database to the physical control devices installed in the building, which can be a very time-consuming and expensive task.

[0009] Other prior art commissioning processes may be less complex, can be completed in less time, and do not require trained commissioning agents. However, the load control systems that may be commissioned using such processes lack the advanced features provided by the more complex load control systems described above. In addition, the less complex commissioning process may require the contractor configuring the load control system to press a button on a load control device (which may be located in a ceiling or some other remote location) and a corresponding input device (e.g., a remote control device) to associate the two devices with each other for load control to be achieved. During the normal operation of these load control systems, the load control device can receive messages from the associated input device and execute a limited number of predefined commands based on the predefined messages that can be sent from the input device. Although the association of the devices can be completed more quickly in such a commissioning process, the ultimate control is less advanced. Associating a large group of devices by pressing a button on each device can also be time-consuming because the contractor may have to climb a ladder and press the button on the device in the ceiling (or other location in the room, such as a wall) multiple times.

[0010] The above-described commissioning process requires knowledge of each device associated with the load control system. Some of the above commissioning processes also require physically actuating buttons on each input device and / or knowing the location of each of the control devices associated with the load control system. Identifying the location of each of the control devices in the load control system can be particularly difficult because the location of the control devices is typically installed before the communication address assigned to convey load control instructions to the devices. Such difficulties can cause an individual commissioning the system to spend a significant amount of time searching for the specific devices to be configured and, once found, performing a lengthy configuration method to enable the devices to control electrical loads in the location. Thus, the current commissioning process for load control systems can be time-consuming and inconvenient. Summary of the Invention

[0011] A commissioning process can be implemented that uses a network device (e.g., a mobile computing device) to efficiently configure a load control system and allow the configuration of advanced features. The use of the network device can eliminate or at least limit pressing buttons on load control devices (e.g., which may be located in hard-to-reach locations). Although the commissioning process can use a network device, the configuration process can provide instructions and be very intuitive for an individual implementing the commissioning process (e.g., a contractor who may have performed a prior commissioning process).

[0012] The commissioning process described herein can also assist in discovering control devices in the load control system. Discovery of the control devices in the system can be performed using control devices that are already part of the load control system. For example, discovery of a load control device (e.g., a load control device in a lighting fixture and / or in a ceiling) can be initiated by actuating a button on an input device (e.g., a remote control device) located near the load control device to be discovered and that can be used to control the load control device during normal operation of the load control system. The discovered load control devices can be displayed on a visual display of the network device (e.g., in an organized list or dataset), and the contractor can select from the list displayed on the network device the load control devices to be associated with the selected input device. The remote control device can be within easy reach of the contractor, and the contractor may not need to climb a ladder to complete the discovery and association of the control devices.

[0013] The debugging process described herein can allow for the implementation of advanced features without the time-consuming and advanced steps of the complex debugging processes of the prior art. While the contractor is performing the debugging process, the input devices and load control devices discovered can be organized into zones in a timely manner. The defined zones, each including input devices and load control devices, can be used by the load control system during normal operation to provide advanced features. The debugging process described herein can also allow for flexibility and scalability in the design of the load control system, as additional features and programming can be easily added and / or adjusted at a later date (e.g., after the debugging process is completed).

[0014] The debugging process can be used to configure a load control system that can include control devices for controlling the amount of power supplied to an electrical load. The control devices can include control source devices and / or control target devices. The control target devices can be capable of controlling the amount of power supplied to the electrical load based on digital messages received from the control source devices. The control source devices and / or control target devices can also be implemented to assist in discovering other control devices in the load control system, which can avoid incorporating additional devices into the load control system.

[0015] The digital messages can include load control instructions or another indication that causes the control target devices to determine load control instructions for controlling the electrical load. The load control system can also include a system controller for monitoring the operation of the control source devices and / or control target devices and sending digital messages including global commands (e.g., demand response commands, on commands, off commands, clock event commands, etc.) to the control target devices and / or control source devices.

[0016] The load control system can be debugged to enable the control of the electrical load based on commands. For example, the load control devices can be associated with each other and stored in association information that can be used to transmit digital commands for controlling the electrical devices in the system. The association information can include unique identifiers of one or more associated devices. The load control system can include a load control discovery device for sending discovery messages to the control devices when the control devices are within an established discovery range associated with the load control discovery device. The load control discovery device can be a control target device and / or a control source device installed in the system for performing load control. The load control discovery device can be used to discover the control target devices and / or control source devices. The load control discovery device can be a dedicated load control discovery device. The load control discovery device can broadcast messages (e.g., discovery messages) within the established discovery range. The control target devices and / or control source devices can be associated with each other based on the broadcast messages.

[0017] The system controller can receive an acknowledgment message from a control device that received a message (e.g., a discovery message). The acknowledgment message can include an identification of the control device that received the message (e.g., the discovery message) and / or the signal strength (e.g., received signal strength indication) at which the message (e.g., the discovery message) was received at the control device. After the system controller has identified that the message (e.g., the discovery message) has been broadcast, the acknowledgment message can be received in response to a query from the system controller. The signal strength can be automatically sent from the control device when the message (e.g., the discovery message) is received. The system controller and / or network device can filter the discovered devices according to defined discovery criteria.

[0018] The system controller can define an organized data set of the discovered control devices. The data set can be organized according to the signal strength at which the discovered control devices received the discovery message. The data set can be organized according to the signal strength at which the load control discovery device sent the discovery message. The discovered control devices can be added to and / or removed from the data set. For example, the discovered control devices can be added to and / or removed from the data set by increasing and / or decreasing the transmission power and / or threshold (e.g., received power threshold) of the message (e.g., the discovery message). Other discovery criteria can be used to filter the discovered devices and organize a subset of the control devices in the data set. The system controller can send the organized data set to the network device. The network device can generate a user interface that includes the organized data set and / or a portion of the organized data set. The user interface can allow the user to assign a control device as a load control discovery device, associate and / or disassociate a control device with another control device, associate and / or disassociate a control device with a location, and / or identify a control device.

[0019] The discovery message can include an indication of the type of device that can respond to the discovery message. The discovery message can include a device identifier (e.g., the identifier of the load control discovery device). The control device can identify the device identifier to trigger a message that identifies the signal strength at which the discovery message was received. The discovery message can be sent from a dedicated discovery device. The dedicated discovery device can be a device that can be used to send discovery messages to control devices during a discovery mode (e.g., a dedicated discovery mode). The dedicated discovery mode can be enabled and last for a period of time, can be enabled / disabled when indicated by the user, and / or can be configured as a static mode on the dedicated discovery device. The discovery message can be a message for one or more activities. For example, the discovery message can be a message for associating control devices, controlling control devices, and / or discovering control devices.

[0020] A discovery range for sending discovery messages can be established based on transmission power, signal strength at which discovery messages can be received, and / or a threshold (e.g., received power threshold). For example, a discovery range for sending discovery messages can be established based on transmission power, received signal strength, and / or a threshold indicated at a network device and / or stored at a system controller. The discovery range can be segmented according to one or more discovery zones. The discovery zones can be identified by transmission power, received signal strength, and / or a threshold (e.g., received power threshold). Discovery messages can be sent within the discovery range and can identify the discovery zones to which a control device can respond. If a discovery message is received at the identified signal strength, the discovery zone can be identified by the received signal strength to which the control device can respond. The discovery range can be adjustable (e.g., incrementally adjustable). For example, the discovery range can be adjusted at a network device and / or at a system controller. The established discovery range can be determined by ignoring information received from control devices outside the established discovery range.

[0021] Different control devices can be identified as load control discovery devices. The control devices can have different transmission powers for establishing different discovery ranges. The control devices can be in different locations for discovering different control devices within the discovery range. The established discovery range for discovery and / or associating control devices can correspond to the transmission power of the system controller. The system controller can adjust the transmission power to discover control devices within the established discovery range.

[0022] A control source device can be associated with a control target device during a configuration process such that the control target device responds to the associated control source device during normal operation. A network device with a visual display can be used to perform the configuration process to associate the control source device and the control target device. The control source device can use a zone configuration process to be associated with the control target device on a zone-by-zone basis. For example, the zone configuration process can be repeated for each load control zone (e.g., load control environment and / or room) of a building. Each control source device located in a zone can be associated with a control target device that will respond to the control source device (e.g., by stepping through each control source device in the zone one by one). Each control source device can be associated with the control target devices in the zone. The control source devices can be associated with the control target devices of the zone in any order. For example, a first control source device can first be associated with one or more control target devices, and then a second control source device can be associated with one or more control target devices, or vice versa.

[0023] A control source device can be selected to be associated with one or more control target devices in a region by actuating a button on the control source device. The network device can display a list of control target devices within the discovery range of the control source device that is found to have a button actuated. The network device and / or the system controller can associate the control source device with one or more of the control target devices when a control target device is selected from the list displayed on the network device.

[0024] The network device can store the association information of the control source device and the control target device in each region and can send the association information to the system controller that can store the association information. The system controller and / or the network device can build and store a list of control source devices in each region and a list of control target devices associated with the control source devices in each region. As part of the region configuration process, the system controller and / or the network device can build a list of the control source device and the control target device when the control source device is associated with the control target device. BRIEF DESCRIPTION OF THE DRAWINGS

[0025] Figures 1A - 1C is a perspective view diagram depicting an example environment for associating control devices.

[0026] Figure 2 is a diagram of an example discovery range for performing discovery and / or association of control devices.

[0027] Figure 3 shows an example flowchart of an example discovery process for discovering control devices and associating them.

[0028] Figure 4 is a flowchart of an example method for discovering control devices and associating them.

[0029] Figure 5 is a flowchart of an example discovery process for discovering control devices and associating them.

[0030] Figure 6 is an example graphical user interface (GUI) that can be implemented for discovery and / or association of control devices.

[0031] Figure 7 is an example GUI that can be implemented for discovery of control devices and / or association of control devices with locations.

[0032] Figures 8A - 8J illustrates an example GUI that can be displayed on a visual display of a network device during a region configuration process.

[0033] Figures 9A - 9CThe figure is an example flowchart showing an example discovery process for discovering and associating control devices.

[0034] Figure 10 It is a flowchart of an example area configuration process for associating control devices in a load control environment.

[0035] Figure 11A and Figure 11B The figure shows an example GUI that can be displayed on a visual display of a network device for configuring operating settings of an area.

[0036] Figures 12A - 12C The figure shows an example GUI that can be displayed on a visual display of a network device for configuring control devices of an area.

[0037] Figure 13 The figure shows an example GUI that is displayed on a visual display of a network device for configuring presets for buttons of control devices in an area having more than one type of load control device.

[0038] Figure 14 It is a block diagram of an example network device.

[0039] Figure 15 It is a block diagram of an example system controller.

[0040] Figure 16 It is a block diagram of an example control target device.

[0041] Figure 17 It is a block diagram of an example control source device. Detailed Description

[0042] Figure 1A Depicts a representative load control environment 100 (e.g., a load control area) including a load control system. The load control system can be debugged to enable control of electrical devices in the load control system. Debugging of the load control system can include associating control devices, which can include control source devices and / or control target devices. As Figure 1AAs shown, rooms 102, 104, and 106 in a building can be equipped with one or more controlled target devices, for example, load control devices for controlling electrical loads within the room or building. Each load control device can be capable of directly controlling the amount of power supplied to the electrical load and can be controlled by a control source device. Example controlled target devices can include lighting fixtures 108a, 108b, 108c, 108d in room 102; lighting fixtures 138a, 138b, 138c, 138d in room 104; and lighting fixtures 146a, 146b, 146c, 146d in room 106. Each lighting fixture can include a lighting load (e.g., an LED light source) and a corresponding lighting control device for controlling the corresponding lighting load of the lighting fixture (e.g., an LED driver, a ballast, a dimming or switching module that can interface with the driver or ballast, or other lighting control devices). Other example controlled target devices can include electric window treatments 120 having a motor drive unit (e.g., including a motor) for controlling the position of the covering material 122, a temperature control device for controlling an HVAC system (e.g., a thermostat 136), and / or an AC plug-in load control device 124 for controlling plug-in electrical loads, such as a floor lamp 126, a table lamp, or another electrical device plugged into the AC plug-in load control device 124. The AC plug-in load control device 120 can be plugged into an electrical outlet 130.

[0043] The control devices (e.g., control source devices and / or controlled target devices) can communicate with each other and / or other devices via wired and / or wireless communication links. For example, the control devices can communicate via a radio frequency (RF) signal 172. The RF signal 172 can be sent via any known RF communication technology and / or protocol (e.g., near field communication (NFC); a proprietary communication channel, such as CLEAR CONNECT TM etc.). A control device can be both a controlled target device and a control source device.

[0044] A control source device can be an input device that indirectly controls the amount of power supplied to an electrical load by sending a digital message to a controlled target device. The digital message can include a control instruction (e.g., a load control instruction) or another indication that causes the controlled target device to determine a load control instruction for controlling the electrical load. Example control source devices can include remote control devices 116, 142, and 154, an occupancy sensor 112, a daylight sensor 150, a window sensor 180, and / or a network device 128. The control source device can include a wired or wireless device. The control source device can include a control device such as a dimmer switch, an electronic switch, etc.

[0045] The load control system 100 can be debugged to enable the control of an electrical load based on commands transmitted between control devices (e.g., a control source device and a control target device) configured to control the electrical load. For example, the control devices can be associated with each other and the association information can be stored thereon or at other devices, and the association information can be used to transmit and identify digital commands for the electrical devices in the control system at the associated devices. The association information can include unique identifiers of one or more associated devices. The association information can be stored at the control devices or at other devices that can be implemented to enable the transmission and / or identification of digital commands between the control devices.

[0046] The remote control devices 116, 142, and 154 can be wireless devices capable of controlling a target device via wireless communication. The remote control devices 116, 142, and 154 can be attached to or detached from a wall. Examples of remote control devices are described in more detail in the following U.S. patents: U.S. Patent No. 5,248,919, titled LIGHTING CONTROL DEVICE, issued September 28, 1993; U.S. Patent No. 8,471,779, titled WIRELESS BATTERY POWERED REMOTE CONTROL WITH LABEL SERVING ANTENNA ELEMENT, issued June 25, 2013; and U.S. Patent Application Publication No. 2014 / 0132475, titled WIRELESS LOAD CONTROL DEVICE, published May 15, 2014, the entire disclosures of which are incorporated herein by reference.

[0047] The occupancy sensor 112 can be configured to detect occupancy and / or vacancy conditions in the load control environment 100 in which the load control system is installed. The occupancy sensor 112 can send a digital message to a control target device via the RF communication signal 172 in response to detecting an occupancy or vacancy condition. The occupancy sensor 112 can operate as a vacancy sensor such that the digital message is sent in response to detecting a vacancy condition (e.g., the digital message may not be sent in response to detecting an occupancy condition). The occupancy sensor 112 can enter an association mode in response to actuation of a button 114 on the occupancy sensor 112 and can send an association message via the RF communication signal 172. Examples of RF load control systems with occupancy and / or vacancy sensors are described in more detail in the following U.S. patents: U.S. Patent No. 8,009,042, titled RADIO-FREQUENCY LIGHTING CONTROL SYSTEM WITH OCCUPANCY SENSING, issued on August 10, 2011; U.S. Patent No. 8,199,010, titled METHOD AND APPARATUS FOR CONFIGURING A WIRELESS SENSOR, issued on June 12, 2012; and U.S. Patent No. 8,228,184, titled BATTERY-POWERED OCCUPANCY SENSOR, issued on July 24, 2012, the entire disclosures of which are incorporated herein by reference.

[0048] The daylight sensor 150 can be configured to measure the total light intensity in the visible area of the load control environment 100 in which the load control system is installed. The daylight sensor 150 can send a digital message including the measured light intensity via the RF communication signal 172 for controlling the control target device in response to the measured light intensity. The daylight sensor 150 can enter an association mode in response to actuation of a button 152 on the daylight sensor 150 and can send an association message via the RF communication signal 172. Examples of RF load control systems with daylight sensors are described in more detail in the following U.S. patents: U.S. Patent No. 8,410,706, titled METHOD OF CALIBRATING A DAYLIGHT SENSOR, issued on April 2, 2013; and U.S. Patent No. 8,451,116, titled WIRELESS BATTERY-POWERED DAYLIGHT SENSOR, issued on May 28, 2013, the entire disclosures of which are incorporated herein by reference.

[0049] The window sensor 180 can be configured to measure the external light intensity from outside the load control environment 100 in which the load control system is installed. The window sensor 180 can be mounted on the facade of a building, such as the outside or inside of a window, to measure the external natural light intensity depending on the position of the sun in the sky. The window sensor 180 can detect when direct sunlight shines directly into the window sensor 180, is reflected onto the window sensor 180, or is blocked by an external device such as a cloud or a building, and can send a digital message indicating the measured light intensity. The window sensor 180 can send a digital message including the measured light intensity via the RF communication signal 172. The digital message can be used to control an electrical load via one or more controlled target devices. The window sensor 180 can enter an association mode in response to actuation of a button on the window sensor 180 and can send an association message via the RF communication signal 172.

[0050] The load control environment 100 can include other types of control source devices, such as, for example, temperature sensors, humidity sensors, radiometers, overcast sensors, shadow sensors, pressure sensors, smoke detectors, carbon monoxide detectors, air quality sensors, motion sensors, security sensors, proximity sensors, clamp sensors, zoning sensors, keypads, multi-zone control units, slider control units, kinetic or solar remote controls, key fobs, cell phones, smartphones, tablets, personal digital assistants, personal computers, laptops, clocks, audio-visual controls, security devices, power monitoring devices (e.g., power meters, energy meters, utility sub-meters, utility rate meters, etc.), central control transmitters, residential controllers, commercial controllers, industrial controllers, or any combination of control source devices.

[0051] The load control environment 100 can include a system controller 160 operable to send and / or receive digital messages via wired and / or wireless communication. For example, the system controller 160 can be configured to send and / or receive the RF communication signal 172 to communicate with one or more control devices (e.g., control source devices and / or controlled target devices). For example, the system controller 160 can transfer digital messages between associated control devices. The system controller 160 can be coupled to one or more wired control devices (e.g., control source devices and / or controlled target devices) via a wired digital communication link. The system controller 160 can be located on-site at the load control environment 100 or at a remote location. Although the system controller 160 is shown as a single device, the load control environment 100 can include multiple system controllers and / or its functions can be distributed across multiple devices.

[0052] The system controller 160 can also or alternatively communicate via the RF communication signal 170 (e.g., NFC; Honeycomb; proprietary communication channels such as CLEAR CONNECT TM etc.) for communication. The system controller 160 can use the RF communication signal 170 to communicate via the Internet 164 or other networks. Different protocols and / or radio frequency bands than the RF communication signal 172 can be used to send the RF communication signal 170. For example, or a cellular signal can be used to send the RF communication signal 170, and another RF communication protocol (such as or a proprietary communication protocol) can be used to send the RF communication signal 172. The same protocol and / or radio frequency band as the RF communication signal 172 can be used to send the RF communication signal 170. For example, or a proprietary communication protocol can be used to send the RF communication signal 170 and the RF communication signal 172.

[0053] The system controller 160 can be configured to send and receive digital messages between control devices. For example, the system controller 160 can send a digital message to a control target device in response to a digital message received from a control source device. The digital message can include associated information to be stored at the control device or control instructions for controlling an electrical load. The control instructions can be used to control the electrical load of the control target device or to control the electrical load according to control configuration information. The system controller 160 can receive control instructions from a control source device and can perform a lookup of the control target device associated with the control source device. The system controller 160 can send a digital message including the control instructions to the associated control target device for controlling the electrical load. The system controller 160 can store the associated information from the associated messages transmitted between control devices, or can query the control devices for the associated information stored thereon.

[0054] Once the control source device is associated with the control target device, the control source device can send a digital message to the control target device to cause the control target device to control the amount of power provided to the electrical load. For example, the associated remote control device 116 can instruct the lighting control devices of the lighting fixtures 108a, 108b, 108c, 108d to increase or decrease the lighting levels of the respective lighting loads, instruct the motorized window covering 120 to raise or lower the covering material 122, instruct the AC plug-in load control device 124 to raise or lower the lighting level of the floor lamp 126, and / or instruct the temperature control device 136 to raise or lower the temperature in one or more rooms. The associated occupancy sensor 112 can send similar instructions to the control target device based on the detection of the occupied or vacant condition within the room 102. The daylight sensor 150 can send similar digital messages to the control target device based on the monitoring of the amount of natural light within the room 106.

[0055] A control device (including the load control discovery device 190) can discover and / or perform an association with the system controller 160. The control device can send an association message to the system controller 160 and / or the system controller 160 can send an association message to the control device. The identifier of the system controller 160 can be stored in the control device for detecting communications from the system controller 160. The identifier of the control device can be stored in the system controller 160 for detecting communications from other control devices.

[0056] The system controller 160 can include control configuration information that can be used to control one or more controlled target devices. For example, the control configuration information can include a preset configuration. The system controller 160 can generate a digital message according to the preset configuration to set the dimming level of the lighting fixture to a predefined level, to set the level of the covering material 122 to a predefined level, to set the dimming level of the electric lamp 126 to a predefined level, or to set the temperature of the temperature control device 136 to a predefined level. Different presets can be configured to control different controlled target devices to differently control the corresponding electrical loads. Example preset configurations can include a bedtime preset for when the user goes to bed, a movie watching preset for when the user watches TV or a movie, a time preset for when the user leaves the building, a home preset for the time the user is in the building, or other preset configurations that the user can define for an occasion.

[0057] The control configuration information can include a zone configuration. The zone configuration can define one or more zones in which the controlled target devices are defined to be controlled. A zone can be a group of control devices associated with a group identifier. The controlled target devices in different zones can be controlled individually by sending a digital message with a control instruction for each zone. Different zones can be identified by a zone identifier (e.g., a group identifier), and the zone identifier can be stored in the system controller 160 and / or the control device in the zone. Each zone can be defined as a location with a zone identifier as the location identifier. Although a zone can be described herein as a location with a location identifier, other zone configurations can be implemented similarly as described herein for locations.

[0058] The load control environment 100 can include a network device 128. The network device 128 can perform wired and / or wireless communications. Examples of the network device 128 can include a wireless phone, a tablet, a laptop, a personal digital assistant (PDA), a wearable device (e.g., a watch, glasses, etc.) or another computing device. The network device 128 can be a user device operated by the user 132. The network device 128 can communicate via an RF communication signal 170 (e.g., signal, Send digital messages over signals (such as RF signals, cellular signals, etc.) to communicate wirelessly. The network device 128 can transmit digital messages in response to the actuation of one or more buttons on the network device 128. Examples of load control systems for devices with support (such as smart phones and tablet devices) are described in more detail in the following U.S. patents: U.S. Patent Application Publication No. 2013 / 0030589, titled LOAD CONTROL DEVICE HAVING INTERNET CONNECTIVITY, published on January 11, 2013; and U.S. Patent No. 9,413,171, titled NETWORK ACCESS COORDINATION OF LOAD CONTROL DEVICES, issued on August 9, 2016, the entire disclosures of which are incorporated herein by reference.

[0059] The network device 128 can use digital messages sent via the RF communication signal 170 (e.g., RF signals, RF signals, cellular signals, etc.) to communicate with the system controller 160 to allow the network device 128 to associate control devices (e.g., control source devices and / or control target devices) and / or control electrical loads. When the RF communication signal 170 and the RF communication signal 172 are transmitted on the same communication protocol and / or the same frequency band, the network device 128 can operate as the system controller 160 as described herein.

[0060] The network device 128 can execute applications locally to display information received from the system controller 160 and / or receive user input for transmitting information to the system controller 160. The network device 128 can include a visual display 110 for displaying information to the user 132 and can be configured to receive user input from the user 132. The system controller 160 can be accessed at the network device 128 via a web interface (e.g., a web browser) and / or via a control application (e.g., a load control application and / or a configuration application). The user 132 can generate and store association information on the network device 128 for associating control source devices and control target devices.

[0061] The associated information can be stored in the form of a table or a database that associates a unique identifier (e.g., a serial number) of a controlled target device with the location and / or unique identifier (e.g., a serial number) of one or more control source devices. The associated information can include device type identifiers indicating the device type of the controlled target device (e.g., a lighting control device, an electric window covering, a plug-in load control device, a temperature control device, etc.) and / or the type of the control source device (e.g., a remote control device, an occupancy sensor, a daylight sensor, a window sensor, etc.). The associated information can be sent from the network device 128 to the system controller 160. The system controller 160 can store the associated information. The system controller 160 can identify the associated information corresponding to each controlled target device by identifying the unique identifiers of the controlled target device and the corresponding associated devices (e.g., the unique identifier of the control source device) to send the associated information to each controlled target device for storage thereon. The system controller 160 can identify other information corresponding to each controlled target device, such as control configuration information, and can send the information to each controlled target device for storage thereon so that the controlled target device can respond according to the information.

[0062] A control device can be associated with a location to enable control of an electrical load in that location. A control device can also be associated with other control devices in the location to enable control of the electrical load. For example, a control device can be associated with a location by storing a location identifier at the control device so that the control device can detect digital messages sent to the control devices in the identified location. A control device (e.g., a controlled target device) can be associated with other control devices (e.g., control source devices) by storing the identifiers of the control devices so that the control device (e.g., the controlled target device) can detect digital messages sent from the associated control devices (e.g., control source devices) for controlling the electrical load. When a controlled target device is associated with a control source device, the controlled target device can respond to the control source device.

[0063] The location of a control device can be discovered relative to the locations of other control devices in the load control environment 100. As Figure 1A shown, a control device (e.g., a control source device and / or a controlled target device) can send messages within a discovery range 134 that can be received by other control devices within the discovery range 134. The messages can be dedicated discovery messages that can be recognized as discovery messages by the receiving devices or other messages that can be sent in the load control environment 100 and can be interpreted as discovery messages. For example, the messages can be association messages for associating devices in the load control environment 100, and / or the messages can be control messages for controlling devices in the load control environment 100.

[0064] A control device that sends a discovery message (e.g., a dedicated discovery message or a message otherwise interpreted as a discovery message) can be identified as a load control discovery device 190. The load control discovery device 190 can be a device that performs one or more activities. For example, the load control discovery device 190 can be a control source device (e.g., a remote control device 116) that controls the amount of power supplied to an electrical load by sending digital messages to a control target device and / or a control device that sends a discovery message to one or more control devices.

[0065] The load control discovery device 190 can be a dedicated load control discovery device 190. For example, the dedicated load control discovery device 190 can be a device (e.g., a control device) that can be used to send a discovery message to a control device and / or a system controller 160 during a dedicated discovery mode. The dedicated discovery mode can be enabled for a period of time, can be enabled / disabled when an indication is received by a user, and / or can be configured as a static mode on the dedicated discovery device. The discovery message can be a message for discovering a control device and / or a system controller 160. The discovery message can be a message for one or more activities. For example, the discovery message can be a message configured to discover a control device and / or a system controller 160, and the discovery message can be a message configured to associate a control device with another control device and / or a system controller 160. The discovery message can be a control message configured to discover a control device and control the control device that receives the discovery message.

[0066] Figure 1A An example is shown where a control source device (e.g., a remote control device 116) is assigned as a load control discovery device 190 that can send a discovery message within a discovery range 134, but other control devices can also be assigned as load control discovery devices 190. The discovery range 134 can correspond to the transmission power of the load control discovery device 190 (e.g., an adjustable transmission power). The load control discovery device 190 can be preconfigured for a location. For example, the load control discovery device 190 can be stored at the system controller 160 as a load control discovery device for an identified location, stored at the load control discovery device 190, and / or stored at other devices at the identified location. The discovery message sent by the load control discovery device 190 can be received by other devices (such as other control devices and / or the system controller 160).

[0067] The device can receive discovery messages and determine whether the discovery messages are received with a signal strength higher than a received power threshold (e.g., a predefined signal strength). The predefined signal strength can be received from the system controller 160 and / or can be preconfigured during manufacturing. The control device that receives the discovery message can report the receipt of the discovery message. The control device that receives the discovery message can report the received signal strength of the discovery message. The control device can report the receipt of the discovery message and / or the received signal strength to another control device (e.g., a control source device, a control target device, etc.). The control device that receives the discovery message can report the receipt of the discovery message and / or the received signal strength to the system controller 160. The control device and / or the system controller 160 can store the control device that receives the discovery message and provide the identifier of the control device to the network device 128. The network device 128 can display the control device to the user 132 in association with a location and / or other control devices.

[0068] Since each control device can be associated with a location, a list of control devices in a given location can be invoked at the network device 128 (e.g., from direct storage or from the system controller 160). The control device can be associated with, de-associated from, or de-associated from other devices. The association and de-association of devices can enable the configuration and / or reconfiguration of control devices in a defined area. A location can be defined and / or redefined by discovering devices and updating the associations. The control device can be installed and / or associated by someone different from the user 132 who operates or manages the operation of the control devices in the space. Discovering a control target device by a control source device can enable the configuration or reconfiguration of a location to optimize the control of the control device according to the use of the space. The use of the location can be changed or can be different from that originally identified in the plan (e.g., such as when the devices are installed in rooms 102, 104, 106). Therefore, the discovery of devices within the discovery range 134 of the load control discovery device 190 can enable the user 132 to redefine the associated devices for a given location.

[0069] The device can receive discovery messages and determine whether a discovery message is received within the discovery range and / or discovery zone. The discovery range can be divided into one or more discovery zones. The discovery zone can be identified by the received signal strength at which the discovery message can be received, and / or can be identified by another identifier (such as the transmission power and / or threshold of the discovery message (e.g., the received power threshold)). The discovery message can be sent within the discovery range and can identify the discovery zone to which the device can respond. If the discovery message is received with the identified signal strength, the discovery zone can be identified by the received signal strength or the range of received signal strengths at which the control device can respond.

[0070] The discovery message sent by the load control discovery device 190 can be a broadcast message that can be broadcast within the established discovery range 134. The discovery message can include information identifying the load control discovery device 190 from which the discovery message is sent. The discovery message can indicate the type of control device (e.g., remote control device, occupancy sensor, lighting control device, etc.), a unique identifier (e.g., serial number) that can identify the load control discovery device 190, a link address for directly communicating with the load control discovery device 190, whether the device is a control target device or a control source device, and / or other information about the device.

[0071] The discovery range 134 can depend on the transmission power of the sending device and / or the range of transmission power. For example, the discovery range 134 can be based on the transmission power of the digital message sent from the load control discovery device 190 or the distance at which the digital message will be sent. The transmission power of the sending device can be adjustable to adjust the area of the discovery range 134.

[0072] The discovery range 134 can also or alternatively depend on a threshold. For example, the discovery range 134 can depend on the received power threshold of the receiving device. For example, the discovery range 134 can depend on the signal strength at which the control device receives the digital message from the load control discovery device 190. The signal strength can be the signal strength indicated by the received signal strength indicator (RSSI) at each receiving device. The RSSI can be defined as a measure of the power level at which the receiving device is receiving the digital message from the sending device. Each receiving device can compare the RSSI of the received message with the received power threshold (which can be stored in the memory of each receiving device) and can respond to the received message if the RSSI is greater than the received power threshold. The received power threshold of each receiving device can be adjustable to adjust the area of the discovery range 134. For example, the discovery message can include the received power threshold against which the receiving control device can compare the RSSI of the received signal (e.g., the discovery message).

[0073] The discovery range 134 can be divided into multiple discovery zones with different RSSI values and / or ranges. For example, the discovery range 134 can be decomposed into discovery zones each associated with a different group of devices (e.g., devices that receive the discovery message with the same signal strength and / or within the same signal strength range). Selecting control devices within one or more specific discovery zones can limit the number of devices that simultaneously send responses to reduce or prevent interference from occurring between devices located in different discovery zones. Control devices that respond to the discovery message in different zones can be aggregated by selecting control devices from more than one discovery zone. For example, based on the positions of the control devices in different zones, the control devices in different zones can be presented to the user 132 and / or provided to the control devices independently.

[0074] As Figure 1A shown above, the transmission power of the load control discovery device 190 can define the discovery range 134. The discovery range 134 can be defined based on the minimum signal strength (e.g., minimum RSSI) to the maximum signal strength (e.g., maximum RSSI). The minimum signal strength can define the outer edge of the discovery range 134. The maximum signal strength can define the inner region (e.g., the region inside the discovery range 134), within which devices can be prevented from responding to discovery messages. The maximum signal strength can be set such that the inner region is relatively smaller (e.g., zero feet away from the load control discovery device 190). Sending discovery messages at the load control discovery device 190 can start at the inner region. For example, the load control discovery device can start sending at zero feet away from the load control discovery device 190 and incrementally send beyond zero feet away from the load control discovery device 190.

[0075] Control devices within the discovery range 134 can respond to discovery messages sent from the load control discovery device 190. Each control device can calculate the RSSI of each corresponding discovery message received. One or more control devices can be organized based on the RSSI of each corresponding discovery message received. The system controller 160 and / or the network device 128 can organize the control devices. For example, the system controller 160 and / or the network device 128 can organize the control devices based on the RSSI of each corresponding discovery message received. Control devices that receive discovery messages with an RSSI higher than the received power threshold in the signal can be within the discovery range 134, and control devices that receive discovery messages with an RSSI lower than the received power threshold in the signal can be outside the discovery range 134.

[0076] The load control discovery device 190 can be a control device (e.g., a control source or a control target) pre-installed in a load control system for performing load control. Since the load control discovery device 190 and / or the control devices to be discovered can communicate using a different protocol from the network device 128, the system controller 160 can identify responses to discovery messages and provide the discovered devices to the network device 128. Using a control device installed for performing load control as the load control discovery device 190 can reduce the number of devices for performing discovery and / or association.

[0077] It is found that the discovery range 134 may be affected by interference. For example, the walls, floors, or ceilings separating rooms 102, 104, and 106 may cause interference. A control device that receives a discovery message within the same discovery range and / or the same discovery area as another control device may cause interference. The interference can degrade the signal strength of the discovery message. This degradation can reduce the discovery range 134 of the discovery message sent from the load control discovery device 190 (e.g., among rooms 102, 104, and / or 106). As Figure 1A shown, the discovery range 134 can be degraded by the wall between room 102 and room 104 and by the ceiling and floor between room 102 and room 106, such that the discovery range 134 projects further into room 102 where there is less interference. Although the discovery range 134 is Figure 1A illustrated by a circle in, however, the discovery range 134 can define an area other than a circular area.

[0078] RSSI or signal strength can be a discovery criterion that can be used to discover devices in the load control environment 100. One or more discovery criteria can be used to discover devices in the load control environment 100. The discovery criteria can include the amount of time since the device was powered on. If a control device is powered on before or after the amount of time indicated in the discovery criterion, the control device can be filtered out from the discovered devices. The control device can start an internal timer when powered on and can identify when the threshold amount of time for being discovered has been met. In another example, the control device can provide the amount of time since the internal timer started, and another device (such as the system controller 160 or the network device 128) can identify when the threshold amount of time for being discovered has been met.

[0079] The discovery criteria can include the load state of the electrical load controlled by the control device. For example, the load state can be the on / off state of the electrical load controlled by the load control device. The load state can be the dimming level or range of dimming levels of a lighting load. The control device can identify the load state of the electrical load and identify when the load state for being discovered has been met. In another example, the control device can provide the load state to another device, such as the system controller 160 or the network device 128, which can identify when the load state for being discovered has been met. The load state included in the discovery criteria can allow the user 132 to adjust the load state of the electrical load using the devices that the user 132 wishes to discover. For example, the user 132 can change the on / off state of lighting fixtures 108a and 108b to the "on" state for discovery, and the user 132 can leave the on / off state of lighting fixtures 108c and 108d in the "off" state to be filtered out by the discovery criteria.

[0080] Discovery criteria can include an occupancy state or activity level identified by an occupancy sensor, such as occupancy sensor 112. For example, occupancy sensor 112 can identify an occupied condition or a vacant condition, which can be used to discover occupancy sensor 112. Occupancy sensor 112 can identify different activity levels. For example, the occupancy sensor can identify primary motion events (e.g., above a predefined motion level) and secondary motion events (e.g., below a predefined motion level) within the visible area of occupancy sensor 112. The primary motion event or the secondary motion event can be used to discover occupancy sensor 112. Occupancy sensor 112 can send a response message when identifying the defined occupancy state or the defined activity level. The occupancy state and / or the activity level can be used to discover devices other than occupancy sensors. The occupancy state and / or the activity level can be identified by occupancy sensor 112 and occupancy sensor 112 can send a discovery message to devices within the discovery range. The discovery message from occupancy sensor 112 can identify the occupancy state and / or the activity level identified at occupancy sensor 112.

[0081] Discovery criteria can include devices that have previously been associated with a location and / or a device. For example, the discovered devices can include devices that have previously been discovered and / or previously stored in the association information at another device. The discovery message can include a request for the associated devices and the identifiers of the associated devices can be returned as a response. The discovery message can include the identifier of a specific device (e.g., a previously discovered device), and the discovery message can ask the control device whether it has been associated with that device. The response to the discovery message can include an answer to the request, or a device that is de-associated from the identified control device can not respond.

[0082] Discovery criteria can be stored at the control device to decide whether to respond to a discovery message according to the defined criteria. Each discovery criterion can be responded to independently, or a combination of criteria can be identified for the response. The discovery criteria can be updated in the load control device in an update message from system controller 160 and / or network device 128. The discovery criteria can be defined at the network device and sent to the control device to determine whether to respond to a discovery message. The discovery message can define the discovery criteria for responding when identified at the control device.

[0083] A discovery message can request that the control device provide identified discovery criteria, and the system controller 160 and / or the network device 128 can filter the discovered devices based on the discovery criteria provided by the control device. For example, the discovery message can request that the control device provide the RSSI at which the discovery message was received, the amount of time since power-on, the load state, and / or the occupancy state or activity level identified by the occupancy sensor. The control device can provide the requested information, or provide a null value if the requested information is not identified at the control device, and can provide the system and / or one or more criteria to the system controller 160 and / or the network device 128 for filtering the discovered devices.

[0084] One of the discovery criteria can be used to initially discover devices, and the criteria can be further filtered based on other criteria. For example, a control device that receives a discovery message with a certain signal strength (e.g., RSSI) can be used to generate an initial data set. Other discovery criteria can be used to further filter the initial data set. The discovery criteria can be provided to the user 132 on the network device 128 for selection to further filter the number of devices discovered in the data set. The discovery criteria can be provided to the user 132 sequentially and / or in a randomly generated order. Instructions can be provided to the user 132 on the network device 128 to indicate the manner in which the user 132 is to further filter the discovered devices. For example, the network device 128 can instruct the user 132 to enter room 102 to discover the devices in room 102. The network device 128 can instruct the user 132 to enter room 102 to discover the devices in room 102. The network device 128 can instruct the user 132 to make a primary movement near the device to be discovered so that the occupancy sensor 112 can detect the primary movement event and send a digital message used by the system controller 160 and / or the network device 128 to filter the discovered devices. The discovery criteria can be selected by the user to limit the number of discovered devices.

[0085] The transmission of the discovery message can be triggered by actuating a button on the load control discovery device 190 and / or receiving a discovery trigger message. For example, the load control discovery device 190 can be recognized as the remote control device 116. The load control discovery device 190 can be recognized as a dedicated load control discovery device. The user 132 can actuate a button, a series of buttons (e.g., for a predefined period of time), and / or perform other commands on the load control discovery device 190 to send a discovery message. Actuating the button for different periods of time can set the load control discovery device 190 to different modes. For example, actuating the button on the load control discovery device 190 (e.g., the remote control device 116) for three seconds can set the load control discovery device 190 to the association mode, in which the load control discovery device 190 can send an association message to the control target device. In this example, actuating the button on the load control discovery device 190 (e.g., the remote control device 116) for six seconds can set the load control discovery device 190 to the discovery mode, in which the load control discovery device 190 can send a discovery message to the control target device. The load control discovery device 190 can also or alternatively receive a discovery trigger message from the system controller 160 or the network device 128. The network device 128 can receive the actuation of the button by the user 132 and can send a discovery trigger message to the load control discovery device 190, or send an indication to the system controller 160 to send a discovery trigger message.

[0086] The transmission of the discovery message can be performed by a sensor in the load control environment. For example, the load control discovery device can be an occupancy sensor, which can send a digital message when identifying an occupancy condition (e.g., an occupied room) and / or a vacant condition (e.g., an unoccupied room). The occupancy condition and / or the vacant condition can be interpreted as a discovery message by other devices (e.g., when the device is in the discovery mode). The user can enter or leave the room to trigger the transmission of a discovery message at the location of the occupancy sensor to discover the devices at that location.

[0087] A control device that receives a discovery message from the load control discovery device 190 can be a two-way communication device that can receive the discovery message and can confirm the receipt of the discovery message to the system controller 160 (e.g., lighting control devices in lighting fixtures 108a, 108b, 108c, 108d, electric window supplies 120, AC plug-in load control devices 124, etc.). The control device can identify the discovery message as coming from the load control discovery device 190 and can store an indication of the receipt of the discovery message. The control device can identify the discovery message by the device identifier of the load control discovery device 190 that is de-associated with the control device, the device identifier of the load control discovery device 190 that is associated with the control device and identified as the load control discovery device 190, and / or the discovery message identifier. The control device can store the signal strength at which the discovery message was received (e.g., received signal strength indication (RSSI)) and / or the control device can store a threshold (e.g., received power threshold). The control device can report the signal strength to one or more other devices, and / or the control device can report to one or more devices whether the signal strength is below or above the received power threshold. For example, the control device can report the signal strength to other control devices, to the network device 128, and / or to the system controller 160. The control device can also or alternatively report whether the signal strength is below or above the received power threshold. If the signal strength (e.g., RSSI) is above the threshold (e.g., predefined received power threshold), then the receipt of the discovery message can be reported.

[0088] A control device that is a one-way communication device (e.g., occupancy sensor 112, window sensor 180, daylight sensor 150, remote control device 154, remote control device 142, etc.) may not be able to receive discovery information. The one-way communication device can send a discovery message to the load control discovery device 190 and / or the system controller 160 for detection and / or association. The discovery message can include the identifier of the sending device. To send the discovery message, the user 132 can actuate a button on the one-way communication device. The user 132 can actuate the button 118 on the remote control device, the button 144 on the remote control device 142, the button 156 on the remote control device 154, the button 152 on the daylight sensor 150, the button 114 on the occupancy sensor 112, and / or the like. To trigger the sending of discovery information at the daylight sensor 150, the user 132 can also or alternatively send a laser signal that can be recognized by the daylight sensor 150. Although some control devices can be described as two-way communication devices, any control device can include a button for sending a discovery message.

[0089] When the load control discovery device 190 can receive messages from the control device, the two-way communication device can also send discovery messages or responses to discovery messages sent from the load control discovery device 190. The load control discovery device 190 can determine the signal strength at which messages from the control device are received. The load control discovery device 190 can internally record the identified devices and / or signal strength. The load control discovery device 190 can provide the identified devices and / or signal strength to the system controller 160 and / or the network device 128. Although some devices may be described as one-way communication devices or two-way communication devices, these devices can be configured for one-way or two-way communication.

[0090] The system controller 160 and / or the network device 128 can be used to coordinate the discovery and association of control devices in a location. The user 132 can actuate a button on the network device 128 to discover devices in the location, and the network device 128 can request discovery information from the system controller 160. The system controller 160 can receive the request and can send a digital message that places the control device in discovery mode. The digital message that places the control device in discovery mode can be the same message as the discovery trigger message used to trigger a discovery message at the load control discovery device 190, or it can be a different message. Once in discovery mode, the control device can know to listen for discovery messages. The user 132 can actuate a button on the control device to enter discovery mode. For example, the user can actuate one or more buttons on the load control discovery device 190 (e.g., for a predefined period of time) to send a digital message to the system controller 160 and / or other control devices to enter discovery mode.

[0091] The control device may send a digital message to the system controller 160 to confirm receipt of the discovery message. The digital message may include the device identifier of the load control discovery device 190 and / or the signal strength at which the discovery message was received. The digital message may be sent to the system controller 160 in response to a request from the system controller 160 (e.g., after the system controller 160 itself receives the discovery message). The request from the system controller 160 may include a request to confirm receipt of a message from a device with the device identifier of the load control discovery device 190 and / or the received signal strength of the message. If the discovery message was received at a signal strength higher than a predefined threshold (e.g., a received power threshold), the request from the system controller 160 may include a request to confirm receipt of the discovery message from the load control discovery device 190 and / or the received signal strength of the message. The request from the system controller 160 may include a request for the device identifier and / or the received signal strength of messages received from non-associated devices from which messages have been received (e.g., since entering discovery mode). The request from the system controller 160 may include a request for the device identifier and / or the received signal strength of messages received from load control discovery devices from which messages have been received (e.g., since entering discovery mode).

[0092] The system controller 160 may provide the discovered devices to the network device 128 for display to the user 132. The system controller 160 may organize the discovered devices for display to the user 132 for association. The system controller 160 may organize the discovered control devices in an organized data set (e.g., an ascending or descending list) organized by the signal strength at which the discovery message was received at each device. The system controller 160 may remove from the data set any device that received the discovery message at a signal strength below a predefined threshold (e.g., a received power threshold). The system controller 160 may include a predefined number of devices with the maximum signal strength in the data set. The system controller 160 may send the organized data set to the network device 128 for display to the user 132.

[0093] Although the coordination of discovery and / or association of control devices is described herein as being performed at the system controller 160, this functionality may be implemented in the control devices themselves. One or more control devices (e.g., lighting control devices in lighting fixtures 108a, 108b, 108c, 108d, remote control device 116, etc.) may be used to coordinate the discovery and / or association of control devices (e.g., control devices within a location). One or more central control devices may receive requests to place control devices in discovery mode and may send digital messages to place control devices in discovery mode. The digital messages may be sent to control devices in the vicinity of one or more central control devices. The digital message to place a control device in discovery mode may be the same message as the discovery trigger message used to trigger a discovery message at the load control discovery device 190, or may be a different message. Once in discovery mode, the control device may know to listen for discovery messages. One or more central control devices may collect discovery information (e.g., acknowledgments of receipt of discovery messages and / or signal strength at which discovery messages were received) from other control devices and may provide the discovery information to the network device 128. One or more central control devices may receive association information from the network device 128 and send the association information or relevant portions thereof to other control devices.

[0094] The network device 128 may organize the discovered devices for display to the user 132 for performing association. The network device 128 may organize the discovered control devices in an organized data set (e.g., ascending or descending list) organized by the signal strength at which discovery messages were received at each device. For example, the network device 128 may first display the control device that received the discovery message with the highest RSSI, and then display devices that received discovery messages with lower RSSI in descending order. The network device 128 may remove from the data set any device that received a discovery message at a signal strength below a predefined threshold (e.g., received power threshold). The network device 128 may include a predefined number of devices with the maximum signal strength in the data set.

[0095] The user 132 may select a control device (e.g., a lighting control device in lighting fixtures 108a, 108b, 108c, 108d) from the discovered devices displayed on the network device 150. The selected control device may be associated with the load control discovery device 190 used to discover control devices within the discovery range 134. The network device 150 may generate association information regarding the load control discovery device 190 and the selected control device in response to input received from the user 132. The selected control device may also be associated with control devices other than the load control discovery device 190 (e.g., control source devices).

[0096] User 132 may configure, at network device 128, association information and / or control configuration information for discovered control devices. The discovered control devices may be associated with one or more location identifiers that identify locations within the load control environment 100. These locations may be identified by user 132 (e.g., from a list of predefined locations) or may be one or more predefined locations associated with the load control discovery device 190 (e.g., the location where the load control discovery device is installed).

[0097] Network device 128 may access the association information stored at system controller 160. The association information may include device identifiers of the discovered devices, location identifiers of the discovered devices, and / or identifiers of associated control devices. User 132 may disassociate a discovered control device from a previously associated control device by making a selection on network device 128. User 132 may associate a discovered control device with other control devices by making a selection on network device 128.

[0098] User 132 may access the control configuration information stored at system controller 160. User 132 may edit the currently stored control configuration information for a discovered control device by making a selection on network device 128. User 132 may generate and store control configuration information for a discovered control device by making a selection on network device 128.

[0099] Network device 128 may send the association information and / or control configuration information to system controller 160 (e.g., upon actuation of a button by user 132). System controller 160 may store the updated association information and / or control configuration information thereon. System controller 160 may send the association information and / or control configuration information to the control devices to update the association information and / or control configuration information stored at the control devices. System controller 160 may broadcast the updated association information and / or control configuration information to the control devices so that the control devices identify the updated respective association information and / or control configuration information (if any) for local storage thereon.

[0100] Figure 1BAn example load control environment 100 is shown having a control target device identified as a load control discovery device 190. For example, a lighting control device in lighting fixture 108a may be identified as a load control discovery device 190 at system controller 160 and / or at the lighting control device 108 itself. The load control discovery device 190 may be predefined for a location or switched between control devices. The load control discovery device 190 may be switched between control devices via a command from network device 128 (e.g., a command from network device 128 to system controller 160). A user 132 may select a control device to be identified as a load control discovery device 190, and the identifier of the selected control device may be stored as the load control discovery device 190 (e.g., at system controller 160, network device 128, the control device identified as the load control discovery device 190, and / or other control devices). The lighting control device of lighting fixture 108a may be identified as a load control discovery device 190 to discover a different set of control devices than the remote control device 116 identified as a load control discovery device 190 in Figure 1A A different set of control devices than the remote control device 116 identified as a load control discovery device 190 in

[0101] After the load control discovery device 190 is switched, an organized data set of discovered devices may be deleted, reorganized, and / or rebuilt. For example, if the load discovery device 190 is deassociated from one or more control devices, and / or if the load control discovery device 190 is configured in a way that will affect the signal strength of a control device receiving discovery messages from a different load control discovery device 190, then the organized data set may be deleted.

[0102] For example, if a control device is associated with and / or deassociated from a load control discovery device 190, and / or if the signal strength of a control device receiving discovery messages from a different load control discovery device 190 changes over time, then the organized data set may also be reorganized. For example, the organized data set may be reorganized to account for devices associated with another load control discovery device 190, where the discovery messages received from the associated load control discovery device 190 have a greater or lesser signal strength compared to the discovery messages from a previously associated load control discovery device. If the same control device is deassociated from a load control discovery device, e.g., if the load control discovery device is removed from a room or the control device is associated with another load control discovery device, then the organized data set may be reorganized.

[0103] An organized data set of the discovered devices can be reconstructed. The reconstructed organized data set can be a supplement to or a replacement for a pre-existing organized data set. For example, if a control device is removed as a load control device and another control device is assigned as the load control device, the organized data set can be reconstructed. The organized data set can be reconstructed, for example, to account for a load control device having an association different from a previous association.

[0104] The discovery range 134 of different types of load control discovery devices can be the same or different. The user 132 can establish the discovery range 134 at the network device 128 or can pre-define the discovery range 134. If the discovery range 134 is established at the network device 128, the established range can be transmitted to the system controller 160 and / or the load control discovery device 190 for storage thereon.

[0105] Any control device (e.g., a control source device and / or a control target device) can be identified as the load control discovery device 190. The control device can be assigned as the load control discovery device 190 at the system controller 160, at the network device 128, and / or at the control device itself. The load control discovery device 190 can be switched between control devices. As Figure 1B shown, the load control discovery device 190 can be switched between the lighting control device of the lighting fixture 108a, the lighting control device of the lighting fixture 108b, the lighting control device of the lighting fixture 108c, the lighting control device of the lighting fixture 108d, the motorized window covering 120, the occupancy sensor 112, the AC plug-in load control device 124, and / or other control devices. For example, the load control discovery device 190 can be switched from the lighting control device of the lighting fixture 108a to the lighting control device of the lighting fixture 108d to discover and associate devices in different locations within the room 102. The load control discovery device 190 can be switched between control devices via a command from the network device 128. For example, the load control discovery device 190 can be switched between these control devices in response to the user 132 selecting one of the control devices on the network device 128. The network device 128 can send a message to the system controller 160. The system controller 160 and / or the network device 128 can send a message to the remote control device 116 that the device has been unassigned as the load control discovery device 190. The remote control device 116 is like Figure 1AAs shown previously assigned as the load control discovery device 190. The system controller 160 and / or the network device 128 may send a message to the lighting control device of the lighting fixture 108a that the device has been assigned as the load control discovery device 190. The load control discovery device 190 can be switched between control devices by actuating a button (e.g., button 114 on the occupancy sensor) on the corresponding control device used by the user 132 to be assigned as the load control discovery device 190.

[0106] The discovery range 134 can be calculated from the load control discovery device 190 such that identifying different control devices as the load control discovery device 190 can allow different devices to be discovered. As described above, the load control discovery device 190 can be switched between control devices (e.g., from a previous load control discovery device to another load control discovery device). When the load control discovery device 190 is switched between control devices, discovery messages can be sent within the discovery range 134 of different control devices. For example, if the load control discovery device 190 is switched from the remote control device 116 to the lighting control device of the lighting fixture 108a, the center of the discovery range 134 can move from the location of the remote control device 116 to the lighting control device of the lighting fixture 108a (e.g., in response to the user's selection of the control device assigned as the load control discovery device 190 on the network device). When the load control discovery device 190 can be a movable device (e.g., the remote control device 116, which may be removable from the wall and carried by the user 132), the discovery range 134 can move with the same load control discovery device 190.

[0107] The discovery message can be sent multiple times. For example, the discovery message can be sent multiple times to identify control devices located within the motion discovery range 134 and / or identify control devices that were not previously identified due to interference. Control devices identified as the result of sending multiple messages can be aggregated. The aggregated control devices can be provided to the user 132. For example, the aggregated control devices can be provided to the user 132 via the network device 128. When responding to subsequent discovery messages, control devices that previously responded to a discovery message can be ignored. A control device can respond to the first discovery message received and omit responses thereafter, or respond to each received discovery message. Subsequent discovery messages can identify control devices that previously responded to a discovery message, e.g., to prevent the discovered control devices from having to respond again.

[0108] There can be more than one load control discovery device 190. The load control discovery device 190 can be defined for different groups of control devices, such as different groups of control devices in a physical space. For example, a control device located in the first part of room 102 can be identified as the load control discovery device 190 for discovering control devices in the first part of room 102, and another control device located in the second part of room 102 can be identified as another load control discovery device for discovering control devices in the second part of room 102. In another example, the control devices in each of rooms 102, 104, and 106 can be identified as the corresponding load control discovery devices for the rooms in which the devices are located. The control device located most centrally in a room or a part of a room can be identified as the load control discovery device 190.

[0109] A digital message can be sent to a control device to instruct the control device to identify itself and / or the corresponding electrical load, so that user 132 can identify the control device designated as the load control discovery device 190. The identified control device can be a control device discovered at a certain location. User 132 can actuate a button on network device 128 to instruct the control device to perform the identification. An identification message can be sent from system controller 160 to the identified device. The identified control device can receive the identification message and control the electrical load according to the control instructions for identifying the device. System controller 160 can know the type of the identified control device and can send control instructions corresponding to the type of the control device. System controller 160 can send a general identification message that can be detected by the identified device and can look up control instructions locally.

[0110] User 132 can actuate a button on a control device to assign the control device as the load control discovery device 190. For example, user 132 can actuate a button 118 on remote control device 116 or load control discovery device 190 (e.g., for a predetermined period of time) to send a digital message to system controller 160 for instructing system controller 160 to identify remote control device 116 as the load control discovery device 190. An identification message can be sent from system controller 160 to the identified control device. Remote control device 116 or load control discovery device 190 can also or alternatively communicate directly with the control device to request identification. The identified device can receive the identification message and control the electrical load according to the control instructions for identifying the device.

[0111] User 132 may actuate a button on the remote control device 116 or the load control discovery device 190 (e.g., for a predetermined period of time) to identify another control device (e.g., by flashing or otherwise identifying the device) as the load control discovery device 190 or to assign the identified control device as the load control discovery device 190. This may allow user 132 to traverse the control devices and select one control device as the load control discovery device 190. The control devices traversed to be identified as the load control discovery device 190 may be control devices that have been discovered during the discovery mode or other devices (e.g., devices within the discovery range of the remote control device 116 or the load control discovery device 190).

[0112] Different control devices may perform identification differently. The load control device may increase and / or decrease the amount of power provided to the corresponding electrical load. The lighting control device in the lighting fixture may turn on, turn off, raise the dimming level, lower the dimming level, or flash the corresponding lighting load. The motorized window covering 120 may raise or lower the height of the covering material 122 or swing with the window covering at the current height. The AC plug-in load control device 124 may turn on, turn off, raise, lower, or flash the floor lamp 126, or otherwise increase and / or decrease the amount of power provided to the electrical load controlled by the plug-in load control device 124. The control device may also or alternatively include an LED that may be turned on, turned off, or flashed for identification.

[0113] After the control device has been identified, user 132 may select the identified device on the network device 128 for identifying the control device as the load control discovery device 190. User 132 may identify different control devices as the load control discovery device 190 and discover different devices by moving the established discovery range 134 within a location or to a different location.

[0114] When the control devices in rooms 104 and 106 are outside the established discovery range 134, these control devices may not be able to receive discovery messages from the load control discovery device 190. As Figure 1C shown, the established discovery range 134 may be configurable. For example, the established discovery range 134 may be configured by adjusting (e.g., incrementally increasing or decreasing) the signal strength (e.g., transmit power) of the load control discovery device 190 and / or by adjusting (e.g., increasing or decreasing) a threshold (e.g., receive power threshold). The discovery range 134 may increase (e.g., incrementally increase) as the transmit power of the load control discovery device 190 is increased and / or as the receive power threshold is decreased. When the discovery range 134 is increased, the number of control devices within the discovery range may increase. As Figure 1A andFigure 1B As shown, the discovery range 134 can be adjusted to the adjusted discovery range 158. Using the established adjusted discovery range 158, the load control discovery device 190 can discover and / or associate other control devices (such as the temperature control device 136 and / or the remote control device 154) that enter the adjusted discovery range 158.

[0115] Although Figure 1C the adjusted discovery range 158 is shown as a larger discovery range than the discovery range 134, the discovery range 134 can also be adjusted to a smaller discovery range, which can include fewer control devices. When attempting to discover devices in room 102, the discovery range 134 can be made smaller to avoid discovering control devices in other locations (such as room 104 and / or room 106). The user 132 can adjust the discovery range or move the discovery range to another location to discover control devices within the location based on the size of the room or the location of various control devices. When the discovery range is increased, decreased, and / or moved, the display provided on the network device 128 can be updated accordingly. For example, when the discovery range is moved from one location to another, the network device 128 can show the control devices in the updated discovery range. Additionally or alternatively, when the discovery range is moved from one location to another, the aggregation of control devices from each discovery range can be identified. Devices can be displayed on the network device in an ordered list based on signal strength.

[0116] The temperature control device 136 and / or the remote control device 154 can be detected by sending discovery messages within the adjusted discovery range 158. The daylight sensor 150, the lighting control devices of the lighting fixtures 146a, 146b, 146c, 146d, and the lighting control devices of the lighting fixtures 138a, 138c can also be within the adjusted discovery range 158. The lighting control devices of the lighting fixtures 138b, 138d and the remote control device 142 can be outside the adjusted discovery range 158 and may not receive the discovery messages sent within the adjusted discovery range 158. For example, control devices outside the discovery range 158 can send (e.g., upon actuation of a button or receipt of a trigger message) discovery information to the load control discovery device 190 and / or the system controller 160 because control devices outside the discovery range 158 can have a greater transmission power.

[0117] A discovery range corresponding to the size of the location where the device is to be discovered can be selected. For example, the transmission power of the load control discovery device 190 can be adjusted (e.g., increased or decreased) such that the transmission power of the load control discovery device 190 corresponds to the size of the location. A control device with a greater transmission power can be identified as the load control discovery device 190 to increase the discovery range in a larger room. Each location can have a size identifier indicating the size of each corresponding location. The transmission power of the load control discovery device 190 can be assigned, or a control device with a corresponding transmission power can be identified as the load control discovery device 190, so as to enable discovery of control devices in locations with the identified size. The system controller 160 and / or the network device 128 can store the transmission power of the control device and perform the assignment of the load control discovery device 190 based on the transmission power of the control device and the size of the location. The size of the location can be input on the network device 128.

[0118] The transmission power of the load control discovery device 190 and / or other control devices can be adjusted (e.g., increased or decreased) by a predetermined amount during the discovery mode. The adjusted (e.g., increased and / or decreased) transmission power can be greater than and / or less than the transmission power of the load control discovery device 190 and / or the control device during operation for controlling an electrical load. The adjusted transmission power during the discovery mode can enable the control device and / or the load control discovery device 190 to discover more and / or fewer devices while conserving power at the control device and / or the load control discovery device 190 during other uses (e.g., transmission of load control messages). The adjusted transmission power can be sent from the network device 128 (e.g., directly or via the system controller 160).

[0119] The load control discovery device 190 can communicate with the control device via one or more intermediate devices. For example, a discovery message can be received at the control device and an acknowledgement and / or signal strength can be transmitted via one or more other control devices in the system. One or more intermediate devices can be used to ensure a greater likelihood of receiving the acknowledgement and / or signal strength at the load control discovery device 190. When the control device is sending a discovery message to the load control discovery device 190 (e.g., for a unidirectional communication device), the signal strength of each message received at the intermediate device can be appended to the message being transmitted. The load control discovery device 190 and / or the system controller 160 can add the signal strengths together to determine the relative distance of the control device.

[0120] The control device can interact with other control devices and / or store information of other control devices (e.g., location information, signal strength information, device identifiers, and other identification information). For example, the control device can store information about neighboring control devices so that these control devices can forward information of neighboring devices. A neighboring control device can be a control device that receives a digital message at a predefined signal strength. The neighboring control device can be configured by the network device 128 and / or the system controller 160 and can be transmitted to the control device for storage thereon.

[0121] The control device can receive a discovery message and store the signal strength associated with the received discovery message. The control device can transmit the signal strength at which the discovery message is received to neighboring devices, and the neighboring devices can forward the signal strength to other devices, such as the system controller 160. The control device that receives the discovery message can also or alternatively forward the discovery message to neighboring devices so that control devices outside the discovery range 134 can still be discovered. The control device can add the signal strength of the digital message received from the neighboring device to the signal strength of the received discovery message and report the combined signal strength to the system controller 160.

[0122] Control devices can be sorted and / or grouped according to the corresponding signal strengths. For example, a control device that determines the signal strength of the received discovery message can determine the assumed signal strength of other control devices based on the signal strength determined by the control device. Neighboring control devices can be assumed to have similar signal strengths. The assumed signal strength of a control device can depend on where the control device for which the signal strength is assumed is located within a predefined distance from the source of the discovery message (e.g., the load control discovery device 190). For example, by determining the signal strength of the neighboring control devices of a control device, the system controller 160 can directionally calculate the difference between a control device that is -50 dB away from the system controller 160 and a control device that is -50 dB away from the system controller 160 and -20 dB away from a control device selected to have a satisfactory signal strength.

[0123] Existing association information can be discovered by the system controller 160 and / or the load control discovery device 190. The control device can send association information (e.g., associated device identifier) indicating the device associated with the control device. The association information can be in the discovery message or in a response request for the discovery information. The network device 128 can request a specific control source device identifier to determine whether the control target device is associated with the specific control source device.

[0124] The system controller 160 may discover one or more control devices within a broadcast control group. The broadcast control group may include one or more control devices of an identified device type, one or more control devices within a defined location, and / or one or more control devices sharing another set of characteristics. The group characteristics may be discovery criteria by which control devices may be filtered for discovery. The control devices within the broadcast control group may be simultaneously controlled by the system controller 160. The control devices included in the broadcast control group may receive a group identifier and store the group identifier such that the control devices included within the broadcast control group may respond to digital messages sent to the group and include the group identifier. For example, the system controller 160 may create a lighting control device group that includes the lighting control devices of lighting fixtures 108a, 108b, 108c, and 108d. The system controller 160 may instruct the lighting control devices of lighting fixtures 108a, 108b, 108c, and 108d within the lighting control device group to turn on or off as a group.

[0125] Multiple load control discovery devices 190 may be implemented to perform discovery and / or association of control devices. Each of the load control discovery devices 190 may send discovery messages to the same devices and / or different devices. The system controller 160 may receive the device identifiers of the discovered control devices and / or the signal strength associated with the discovered devices and remove duplicate device identifiers. The system controller 160 may maintain the association signal strength for the device identifier of the maximum signal strength. The system controller 160 may organize the device identifiers (e.g., in an ascending or descending list by signal strength) after the duplicate device identifiers have been removed, or the system controller 160 may remove the organized device identifiers with lower signal strength.

[0126] The system controller 160 may discover when the established discovery ranges 134, 158 overlap with the established ranges of another load control discovery device 190. For example, the system controller 160 may discover that the established discovery ranges 134, 158 overlap with the established ranges of another load control discovery device 190 when the system controller 160 receives duplicate information from the same device. The system controller 160 may adjust one or more discovery ranges to avoid overlap or may indicate the overlap to the user 132 on the network device 128.

[0127] Load control discovery devices can communicate with each other (e.g., directly or via system controller 160). When load control discovery device 190 receives a discovery message, load control discovery device 190 can discover that the established discovery ranges 134, 158 overlap with the established range of another load control discovery device 190. Load control discovery device 190 can adjust the discovery ranges 134, 158 or indicate the overlap to system controller 160 and / or network device 128.

[0128] Figure 2 is a diagram depicting example discovery ranges for performing discovery and / or association of control devices. As Figure 2 shown, the established discovery range 208 can be adjustable. A user can increase or decrease the established discovery range 208 (e.g., between -3 dBm and -9 dBm) to discover and / or associate control devices in a larger or smaller area. The established discovery range 208 can be measured from load control discovery device 202. The established discovery range 208 can be determined based on the distance at which load control discovery device 202 is configured to send and / or receive information. The established discovery range 208 can be determined by increasing or reducing the distance at which load control discovery device 202 is configured to send and / or receive information.

[0129] The discovery range 208 can be established by adjusting the signal strength (e.g., transmit power) of the signal sent by load control discovery device 202 and / or by adjusting a threshold (e.g., receive power threshold). For example, the signal strength can be increased or decreased between -9 dBm and -3 dBm. The receive power threshold can be increased or decreased, e.g., from -9 dBm to -7 dBm. Load control discovery device 202 can broadcast discovery messages to control devices within the established discovery range 208 and / or within a predefined receive power threshold, and / or receive messages from control devices within the established discovery range 208 and / or within a predefined receive power threshold. Load control discovery device 202 can determine control devices within the established discovery range 208 and / or receive power threshold based on response messages received from the control devices. Other devices (such as system controllers, network devices, or control devices that receive the discovery message) can determine whether a control device is within the established discovery range 208 and / or receive power threshold based on response messages received from the control devices.

[0130] The discovery range 208 can be established by ignoring information received from control devices outside the discovery range 208 (e.g., at the load control discovery device 202, the system controller, or the network device). For example, the load control discovery device 202 can have a static signal strength of -3 dBm and the established discovery range 208 can be -9 dBm. In this case, the load control discovery device 202 can broadcast discovery messages to control devices within the -3 dBm region and can receive response messages from control devices within the -3 dBm region. The distance of each control device can be determined based on the received signal strength of the message from the control device. When the received signal strength of the control device is below a threshold (e.g., a received power threshold), the control device can be determined to be outside the established discovery range 208 (e.g., between -9 dBm and -3 dBm) and can be ignored as a discovered device.

[0131] Figure 3 An example flowchart illustrating an example discovery process 300 as described herein. For example, the discovery process 300 can allow for the discovery and / or association of one or more control devices (e.g., control source devices and / or control target devices) for one or more areas in a building. The discovery process 300 can be performed for a specific area in the building to enable the association of one or more control source devices in the area with one or more control target devices in the area such that the control source devices can control the control target devices in the area and can further include configuring the system controller such that the system controller can control the discovered devices in each specific area (e.g., automatically via a scheduler, via user input through a network device, etc.).

[0132] The discovery process 300 can be implemented using one or more devices such as one or more control devices 302 and / or 304 (e.g., a control source device and / or a control target device), a system controller 306, and / or a network device 308. The network device 308 can interface / communicate with the system controller 306 via a communication network, e.g., via a web-based interface provided by the system controller 306 (although other interfaces can be used). The system controller 306 can in turn communicate with the control devices 302 and / or 304 via a communication network that can be the same or different from the network used by the network device 308. The control device 304 can be a control source device (e.g., one or more remote control devices, occupancy sensors, daylight sensors, window sensors, etc.) and / or a control target device (e.g., one or more lighting control devices for lighting fixtures, motorized window treatments, temperature control devices, AC plug load control devices, etc.). One of the control devices 304 can be assigned as the load control discovery device 302, which can be operable to communicate with the other control devices 304 and / or the system controller 306. The process 300 can include additional, fewer, or other devices and / or messages as discussed herein. The process 300 can include steps in other sequences.

[0133] As Figure 3 shown, an association mode trigger message can be sent to the system controller 306 at 320 to place the system controller 306 in the association mode. For example, alternatively, the system controller 306 can be placed in the association mode by actuation of a button on the system controller 306 and / or by an association mode trigger message received from another device such as the control device 304. During the association mode at the system controller 306, the system controller 306 can listen for discovery messages from the load control discovery device.

[0134] A discovery message can be transmitted from the load control discovery device 302 at 322. The discovery message can include a unique identifier of the load control discovery device 302. Transmission of the discovery message by the load control discovery device 302 can be triggered by actuation of a button on the load control discovery device 302, receipt of a discovery trigger message from another device (e.g., from the system controller), or another trigger. The discovery message transmitted at 322 can be a broadcast message received by one or more control devices 304 and / or the system controller 306. In response to receiving the discovery message, one or more control devices 304 can calculate the RSSI value of the discovery message. In response to receiving the discovery message transmitted at 322, the system controller 306 can broadcast a query message at 324 to find devices that have received the discovery message from the load control discovery device 302. The query message can include the unique identifier of the load control discovery device 302 and can request a device response to indicate whether the device has received the discovery message from the identified load control discovery message. The query of the discovered devices can include discovery criteria for finding control devices that meet the discovery criteria. The discovery criteria can include the RSSI or signal strength of the received discovery message, the amount of time since the device was powered on, the load state of the electrical load controlled by the control device (e.g., on state, off state, dimming level, etc.), the occupancy state or activity level identified by an occupancy sensor, the identification of a previously associated location and / or device, and / or another discovery criterion. The discovery criteria can be used to narrow a large group of devices to reduce the set of discovered devices that can communicate simultaneously on the network. The discovery criteria can also be user-selected to enable the user to reduce the list of devices discovered for association.

[0135] In addition to comparing the identifiers received in the discovery message and the query message to determine whether they should respond to the query, control devices 304 that also meet the discovery criteria can also respond to the query at 326. The response can include the calculated RSSI value and the unique identifier of the control device. Each control device can transmit its corresponding response message at a random time. Although the discovery criteria can be described as in the query message sent at 324, the discovery criteria can be indicated in the discovery message sent at 322 or can be otherwise pre-stored in the control device 304. The system controller 306 can identify the control devices 304 that have responded at 326 and generate an organized data set of the discovered control devices for transmission to the network device 308. The organized data set can be a list of the discovered devices in ascending or descending order based on the RSSI value. The organized data set can include the unique identifier or a subset of each of the discovered devices. The devices can be relatively organized by the signal strength of the RSSI value or according to other discovery criteria.

[0136] The system controller 306 can provide the discovered devices to the network device 308 at 328. The discovered devices can be provided via a display on a web interface or can be provided at 328 via other digital messages for a local display interface at the network device 308. Although the system controller 306 can be described as generating an organized data set of the discovered devices, the discovered devices can be provided to the network device 308 at 328 along with a response to the discovery criteria and / or the network device 308 can locally generate an organized data set of the discovered devices.

[0137] The network device 308 can generate association information including the discovered devices. For example, the network device 308 can receive a user selection for a control source device and a control target device associated for a defined area. The network device 308 can also or alternatively receive a user selection for a control source device or a control target device associated with a load control discovery device 302 assigned for a defined area. The association information can be sent to the system controller 306 at 330 for local storage thereon. The association information or a portion thereof can be sent to the control device 304 at 332 to enable the transfer of messages between the associated devices.

[0138] As described in the discovery process 300, the load control discovery device 302 can be used to send discovery messages to the control devices 304 in a given area and can display the discovered devices to a user on the network device 308 for debugging the system. The association information or a portion thereof can be used by the system controller 306 to relay digital messages to the appropriate devices within the load control system. The association information can be used by the control device 304 to identify messages to which the control device 304 can respond. The load control discovery device 302 can be a control device capable of sending and / or receiving digital messages for controlling an electrical load. The load control discovery device 302 can be assigned based on the proximity of the device within an area (e.g., to discover devices in an area to which the load control discovery device is relatively closer). Using a control device in the system to discover other devices and enabling the display of the discovered devices on the network device 308 in a manner indicating the relative proximity of the devices according to the discovery criteria enables efficient discovery and association of the devices while debugging the system.

[0139] Figure 4 is a block diagram depicting an example method 400 for the discovery and association of control devices. As Figure 4As shown, method 400 may start at 402. At 404, a discovery trigger message may be sent. The discovery trigger message may be sent by a system controller (such as system controllers 160, 306). For example, the discovery trigger message may be sent by system controllers 160, 306 upon receiving an indication from network devices 128, 308. The control device 304 may identify the discovery trigger message and enter a discovery mode to listen for discovery messages, or a separate message may be sent from system controllers 160, 306 to cause the control device 304 to enter the discovery mode.

[0140] The sending of a discovery message may be identified at 406. The discovery message may be identified by system controllers 160, 306 upon receipt. System controllers 160, 306 may request confirmation of the receipt of the discovery message at 408. A control device 304 that receives a discovery message or a discovery message having a signal strength above a predefined threshold (e.g., a received power threshold) may confirm the receipt of the discovery message by transmitting a digital message at 408 along with the identifier of the control device 304 and / or the signal strength at which the discovery message was received (e.g., RSSI).

[0141] System controllers 160, 306 may identify discovery messages received at load control discovery devices 190, 202, 302 at 410. For example, a unidirectional communication device may transmit a discovery message including the device identifier of the sending device to the load control discovery devices 190, 202, 302 to be discovered. The load control discovery devices 190, 202, 302 may store the signal strength at which the discovery message was received and may provide the device identifier of the control device 304 from which the message was received and the corresponding signal strength to system controllers 160, 306. In another example, system controllers 160, 306 may identify the discovery message received from the unidirectional communication device and the signal strength at which the device was received. Although method 400 may describe the identification of discovery messages and the coordination of control device 304 as being performed at system controllers 160, 306, this functionality may be implemented by other devices (e.g., by control device 304, etc.).

[0142] At 412, system controllers 160, 306 may organize the discovered control devices 304 into an organized data set. The organized data set may be a list of device identifiers and / or corresponding signal strengths. The identifiers of the discovered devices may be sorted according to signal strength (e.g., sorted from highest signal strength to lowest signal strength). System controllers 160, 306 and / or network devices 128, 308 may remove control devices 304 having corresponding signal strengths below a predefined threshold (e.g., received power threshold) from the organized data set. System controllers 160, 306 and / or network devices 128, 308 may include control devices 304 having corresponding signal strengths above the predefined threshold in the organized data set. The organized data set may be determined by network devices 128, 308 or the organized data set may be provided by system controllers 160, 306 to network devices 128, 308 at 414. For example, an organized list of device identifiers and / or corresponding signal strengths may be provided to network devices 128, 308.

[0143] System controllers 160, 306 may receive association information from network devices 128, 308 at 416. Control devices 304 may be associated with each other via commands on network devices 128, 308. For example, network devices 128, 308 may have buttons (e.g., soft buttons or hard buttons) for associating one control device (e.g., a control source device) with another control device (e.g., a control target device). Network devices 128, 308 may provide buttons for control devices having signal strengths above a predefined threshold. A user may associate a control device with another control device by selecting the corresponding control device displayed on network devices 128, 308 and / or by the user selecting the association button on network devices 128, 308.

[0144] The association information received from network devices 128, 308 may include the association of device identifiers with location identifiers. The association information may also include the association between control devices 304. System controllers 160, 306 may also or alternatively receive control configuration information from network devices 128, 308, the control configuration information including preset control instructions for the identified control devices 304. System controllers 160, 306 may associate control devices 304 at 418. For example, system controllers 160, 306 may locally store the association information and / or send the associated device identifiers to control devices 304 for local storage thereon. The control configuration information may also be stored at system controllers 160, 306 and / or at the corresponding control devices 304. Method 400 may end at 420.

[0145] Figure 5is a block diagram depicting an example method 500 for controlling discovery and association of devices. As Figure 5 shown, method 500 can begin at 502. At 504, a discovery trigger can be received. The discovery trigger can be received, for example, as a message for controlling discovery of devices 190, 202, 302 and / or as an actuation of a button of the load control discovery devices 190, 202, 302. The discovery trigger can indicate a discovery range for sending a discovery message or the discovery range can be preconfigured. For example, the discovery message can indicate the size of the location where the control device is being discovered or can explicitly identify the discovery range. For example, the discovery range can be established by configuring a wireless signal to cover a defined area or by ignoring information obtained from outside the defined area.

[0146] At 506, the load control discovery devices 190, 202, 302 can send a discovery message. The load control discovery devices 190, 202, 302 can send the discovery message at an identified transmit power (e.g., identified in the discovery trigger message, locally predefined, etc.). The discovery message can include an identifier of the load control discovery devices 190, 202, 302 and / or a location identifier for defining a location. The discovery message can include a discovery message identifier that identifies the message as a discovery message. The discovery message can be an association message for a control device identified as the load control discovery devices 190, 202, 302. The discovery message can identify the discovery range from the discovery trigger message and / or local storage. The discovery message can be sent directly from the load control discovery devices 190, 202, 302. For example, the load control discovery devices 190, 202, 302 can send the discovery message to the control device 304 at 504 in response to the load control discovery devices 190, 202, 302 receiving the discovery trigger message.

[0147] At 508, the load control discovery devices 190, 202, 302 can receive a discovery message from the control device 304. For example, the load control discovery devices 190, 202, 302 can receive the discovery message from a one-way communication device and / or a control device outside the discovery range. The discovery message can also or alternatively be sent in response to a request from the load control discovery devices 190, 202, 302. The discovery message can include a device identifier of the control device 304 from which the discovery message is sent. The discovery message can be an association message from the control device 304.

[0148] At 510, the load control discovery devices 190, 202, 302 can identify and store the signal strength of the discovery messages received from the control device 304. The signal strength can be identified by the RSSI at which the discovery message is received. At 512, the control device identifier of the control device 304 from which the discovery message is received can be provided to the system controllers 160, 306. The signal strength at which the discovery message is received at the load control discovery devices 190, 202, 302 can also be provided to the system controllers 160, 306. The control device identifier and / or the signal strength can be provided in response to a request from the system controllers 160, 306. The control device identifier and / or the signal strength can also or alternatively be provided to the network devices 128, 308 when the network devices 128, 308 and the load control discovery devices 190, 202, 302 communicate via the same communication signal (e.g., in response to a request). The signal strengths can be organized in a list at the system controllers 160, 306 (e.g., sorted from highest signal strength to lowest signal strength). The control device 304 and / or the signal strength can be provided to the network devices 128, 308 in the organized list (e.g., sorted from highest signal strength to lowest signal strength).

[0149] At 514, the system controllers 160, 306 can receive association information and / or control configuration information from the network devices 128, 308 and store the association information and / or control configuration information. The association information and / or the control configuration information can be configured at the network devices 128, 308 by user selection. The system controllers 160, 306 can send the updated association information and / or control configuration information to the corresponding devices. The system controllers 160, 306 can use the association information and / or control configuration information to send digital messages to control the electrical loads in the load control environment. Method 500 can end at 516.

[0150] Although the signal strength can be implemented as a discovery criterion for discovering control devices in method 500, other discovery criteria can also or alternatively be implemented. The system controllers 160, 306 can use the initial discovery criteria to discover an initial set of control devices. The system controllers 160, 306 and / or the network devices 128, 308 can use subsequent discovery criteria to further filter the discovered devices. The discovery criteria can be prompted to the user at the network devices 128, 308 and the discovered devices can be further filtered based on each criterion selected by the user.

[0151] Figure 6 An example graphical user interface (GUI) 602 that can be used to perform the association of control devices at network devices such as network devices 128, 308 is depicted. As Figure 6As shown, the example GUI 602 can present options for the user to select. Although the options can be presented to the user via buttons in the GUI 602, the options can also be presented via a drop-down list, check boxes, etc. The options can include options for selecting a device, options for assigning a device as a load control discovery device 190, 202, 302, options for assigning one device to another device, options for assigning a location to a device, and / or options for identifying a device. The device can relate to a control device (e.g., a control source device and / or a control target device).

[0152] The GUI 602 can include a list of discovered control devices 630. The list of discovered control devices 630 can be displayed in response to a selection of the discovery button 604. The discovery button 604 can be selected to request (e.g., to the system controllers 160, 306 and / or the load control discovery devices 190, 202, 302) the discovery of control devices within the discovery range 606. The devices in the discovery range 606 can be organized in an organized data set according to signal strength. For example, the control devices can be sorted (e.g., from the highest signal strength to the lowest signal strength) on the network devices 128, 308 according to signal strength. The network devices 128, 308 can display the control devices having a corresponding signal strength higher than a predefined threshold in the organized data set. The control devices can be displayed with corresponding signal strength indicators 608 indicating the relative signal strength of the discovered control devices 630. The discovered control devices 630 can be displayed to indicate the device type and / or whether the device is a control target device and / or a control source device. The load control discovery devices 190, 202, 302 can be included in the discovered control devices 630 for association with a location and / or a device.

[0153] The GUI 602 can display corresponding load control discovery device assignment buttons 632 for one or more of the discovered control devices 630. At the network devices 128, 308, the load control discovery device assignment buttons 632 can be selected by the user to assign the corresponding discovered control devices 630 as load control discovery devices 190, 202, 302. The network devices 128, 308 can transmit messages to other devices (e.g., the system controllers 160, 306, the identified load control discovery devices 190, 202, 302, other control devices, etc.) to identify the assigned control device 630 as a load control discovery device 190, 202, 302. For example, assigning the remote control device 116 as a load control discovery device 190, 202, 302 can specify that the remote control device 116 is the transmitter and / or originator of discovery messages, as described herein.

[0154] The control device that has been assigned as the load control discovery device 190, 202, 302 can be removed from the load control discovery devices 190, 202, 302 by selecting the load control discovery device assignment button 632. When the load control discovery device assignment button 632 is selected for the identified load control discovery devices 190, 202, 302, the network devices 128, 308 can send messages to other devices (e.g., the system controllers 160, 306, the identified load control discovery devices 190, 202, 303, other control devices, etc.) to remove the control device 630 as the identification of the load control discovery devices 190, 202, 302.

[0155] The user can select a discovery range 606 for the load control discovery devices 190, 202, 302. A drop-down box or other button (not shown) on the GUI 602 can be used to establish the discovery range 606. Referring again to FIG. 1, assigning the remote control device 116 as the load control discovery device 190, 202, 302 can specify the discovery range 134 centered on the remote control device 116. For example, if the load control discovery device assignment button 632 corresponding to the remote control device is selected, the discovery range 134 can be sent to the system controllers 160, 306 and / or the remote discovery device 116 for calculating the transmission power or reception threshold for the discovery range of the discovery messages sent from the load control discovery devices 190, 202, 302. The options for the discovery range 606 can vary according to the type of one or more devices assigned as the load control discovery devices 190, 202, 302. The discovery range 606 can be configured based on the transmission power of the devices enumerated and / or selected as the load control discovery devices 190, 202, 302. For example, if the enumerated and / or selected devices can send and / or receive transmissions up to twenty feet, the discovery range 606 can be established between zero and twenty feet or at a predefined number of positions corresponding to the selected devices.

[0156] As Figure 6 shown, the GUI 602 can include device association buttons 634 for one or more of the discovered control devices 630. The device association buttons 634 can be selected by the user to associate the corresponding discovered control device 630 with other control devices. For example, the device association button 634 corresponding to the remote control device and the electric window supplies can be selected to associate the device identifiers of the discovered remote control device and the electric window supplies. The network devices 128, 308 can send messages to other devices (e.g., the system controllers 160, 306, the associated devices, other control devices, etc.) to identify the association.

[0157] The GUI 602 can identify the control source device and the control target device and can allow an association between the control source device and the control target device. The GUI 602 can disallow an association between devices of the same type (e.g., a control source device and a control source device, a control target device and a control target device, etc.).

[0158] The device association button 634 can be selected by the user to disassociate a previously associated control device 630. When the device association button 634 is selected for a discovery control device 630 that has been associated or selected for association, the association can be removed and the network devices 128, 308 can send a message to other devices (e.g., the system controllers 160, 306, associated devices, other control devices, etc.) to remove the association. The associated device can be indicated such that the user can remove the association.

[0159] A discovered control device 630 can be selected to identify other association information of the selected control device. For example, a discovered control device 630 can be selected to identify the device identifier of a device that is currently associated with the selected control device, and the device can include an undiscovered device. The user can select one or more of the device identifier and the device association button 634 of the corresponding discovered control device 630 to associate or disassociate the discovered control device 630 with the selected device. The network devices 128, 308 can send a message to other devices (e.g., the system controllers 160, 306, associated devices, other control devices, etc.) to update the association information.

[0160] The GUI 602 can include a location association button 636 for one or more of the discovered control devices 630. The location association button 636 can be selected by the user to associate the corresponding discovered control device 630 with a location. For example, referring again to FIG. 1, the remote control device 116 can be associated with a meeting room (e.g., meeting room A), a living room, etc. The location can be a preconfigured location (e.g., a predefined location such as the load control discovery devices 190, 202, 302) or can prompt the user to select a location for assignment. The network devices 128, 308 can send a message to other devices (e.g., the system controllers 160, 306, associated devices, other control devices, etc.) to identify the association with the location. The location association can be included in the association information of the device and can be updated with the device association.

[0161] The location association button 636 can be selected by a user to disassociate a discovered control device 630 from a previously associated location. When the location association button 636 is selected for a discovered control device that is already associated with a location or is selected for association with a location, the association can be removed and the network devices 128, 308 can send messages to other devices (e.g., system controllers 160, 306, associated devices, other control devices, etc.) to remove the association with the location.

[0162] A discovered control device 630 can be selected to identify other locations associated with the discovered control device 630. For example, a discovered control device 630 can be selected to identify the location identifier of the location currently associated with the selected control device. A user can select one or more of the location identifiers and device association buttons 634 of the corresponding discovered control device 630 to associate or disassociate the discovered control device 630 with the selected location. The network devices 128, 308 can send messages to other devices (e.g., system controllers 160, 306, associated devices, other control devices, etc.) to update the association information.

[0163] The GUI 602 can include device identification buttons 638 for one or more of the discovered control devices 630. The device identification buttons 638 can be selected by a user to identify the corresponding discovered control device 630 to the user. Selection of the device identification button 638 for a corresponding device can cause the network devices 128, 308 to send a digital message to the system controllers 160, 306 and / or the device to identify itself to the user. The digital message can include load control instructions corresponding to a control device for controlling an electrical load (e.g., controlling the corresponding electrical load, turning on an LED on the device, turning off an LED on the device, flashing an LED on the device, performing an audible identification, etc.) to identify the device. Alternatively, the digital message can be a request for the device to identify itself, and the system controllers 160, 306 and / or the device can determine the load control instructions locally.

[0164] Devices can be identified for configuration and / or association. For example, once the device identification button 638 corresponding to a remote control device is selected on the GUI 602, the remote control device can be instructed to identify itself to the user. The remote control device can identify itself visually or audibly. The light control device can identify itself by flashing the corresponding lighting fixture. The thermostat can identify itself by flashing an indicator light, providing a message on the thermostat display, and / or providing an identification via the HVAC system controlled by the thermostat. The thermostat can provide an indication via the HVAC system by turning the HVAC system on or off, increasing or decreasing the temperature of the HVAC system, etc. The motorized window covering can identify itself by moving the corresponding covering material it controls.

[0165] Although the GUI 602 includes respective buttons 632, 634, 636, 638 for each of the discovered control devices 630 to identify selections of respective functions for the identified devices, the GUI 602 may include one or more load control discovery device assignment buttons 632, device association buttons 634, location association buttons 636, and / or device identification buttons 638. For example, the GUI 602 may include a single load control discovery device assignment button 632, device association button 634, location association button 636, and / or device identification button 638 corresponding to the discovered control devices 630 and / or the identified location. The discovered control devices 630 may be displayed as buttons to be selected to identify the devices, and the buttons 632, 634, 636, 638 may be selected to indicate the respective functions for the identified devices.

[0166] Figure 7 Depict an example graphical user interface (GUI) 700 that may be used to perform location association at a network device (such as network devices 128, 308). The GUI 700 may be used to select a location 714 that may be associated or disassociated with a discovered control device. For example, the GUI 700 may be displayed at the network devices 128, 308 when the location association button 636 ( Figure 6 shown in) is selected. Different locations 714 may be displayed on the GUI 700 for association with the control device. The locations 714 may be displayed by name and / or by identifier.

[0167] The locations 714 may be displayed to indicate the identity and / or category of the location. For example, as Figure 7 shown, the locations 714 may include conference rooms (e.g., Conference Room A 702, Conference Room B 704, Conference Room C 706, etc.), a cafeteria 708, offices (e.g., Office A 710, Office B 712, etc.), and / or the like. The locations 714 may be presented as buttons that a user may select to associate a discovered control device with one or more of the locations 714.

[0168] Figures 8A - 8JIllustrated are example graphical user interfaces (GUIs) that can be displayed on a visual display of a network device (e.g., the visual display 110 of the network device 128 shown in FIG. 1) during a zone configuration process. These GUIs can be displayed via a web interface (e.g., generated by a system controller or other remote device) and / or by a control application executed by the network device. The zone configuration process illustrated in these GUIs can allow a user to associate one or more control source devices (e.g., input devices such as the remote control device 116, remote control device 142, remote control device 154, occupancy sensor 112, and / or daylight sensor 150 shown in FIG. 1) with one or more control target devices (e.g., lighting control devices in the lighting fixtures shown in FIG. 1, motorized window treatments 120, plug load control devices 124, temperature control device 136 shown in FIG. 1) in a particular zone.

[0169] As Figure 8A shown, a user interface 800 can be displayed during a zone configuration process on a network device. The user interface 800 can allow a user to select an option 802 (e.g., a "Create Zone" option) on the network device to create a zone in a load control system. The zone can be defined to associate and control devices in the system. The network device can assign a name (e.g., a unique name) to the zone being configured. As Figure 8B shown, the network device can receive a name in a zone name text field 812 of a zone name screen 810.

[0170] As Figure 8C shown, the network device can receive the type of a control source device (e.g., the type of an input device) to be associated with one or more of the control target devices (e.g., a lighting control device of a lighting fixture) in the defined zone from an input device selection screen 820. For example, the network device can display a remote control device option 822 from which a user can select (e.g., Input device selection screen 820 for remote control device option), occupancy sensor option 824, or daylight sensor option 826. The remote control device option 822 may allow a user to select the type of remote control device to be added to the defined area. The occupancy sensor option 824 may allow a user to select the type of occupancy sensor to be added to the defined area. The daylight sensor option 826 may allow a user to select the type of daylight sensor to be added to the defined area. The type of device may be predefined for each option as a device configurable within the system. The input device selection screen 820 may include an option 828 indicating that none of the indicated devices can be included in the area. If none of the indicated devices are included in the area, the network device may request the system controller to query the control devices again to identify the devices that received the discovery message. The signal strength of the query may be changed to incorporate a larger range to attempt to discover other devices.

[0171] The input device option may allow a user to select the type of device to be assigned as a load control discovery device. The network device may display a button actuation instruction screen 830, as Figure 8D shown, to assign the device as a load control discovery device and / or send a discovery message. The button actuation instruction screen may include an image 832 that illustrates to the user the instructions for entering the discovery mode for the selected device. The image 832 may, for example, instruct the user to actuate the button of the selected input device, after which the user may press and hold the appropriate button of the input device located in the area. For example, if the remote control device option 822 is selected on the input device selection screen 802, the image 832 of the button actuation instruction screen 830 may be an image of a remote control device (e.g., a 5-button remote control device) instructing the user to press and hold the bottom button of the remote control device for a defined period of time (e.g., 6 seconds), as Figure 8D shown. The selected device may send a discovery message when executing the instructions for discovering control devices in the area.

[0172] The network device may display one or more alternative device options 834 for the identified device type. The alternative device options 834 may each be selected to change the image 832 on the button actuation instruction screen 830 to an image of the selected remote control device and the corresponding instructions for that device. Remote control devices may have different numbers of buttons and may display appropriate instructions for the identified remote control device. If the occupancy sensor option 824 or the daylight sensor option 826 is selected on the device input selection screen 820, the image 832 of the button actuation instruction screen 830 may be an image of the occupancy sensor or the daylight sensor, respectively, with appropriate instructions for actuating the buttons on each of those sensor devices.

[0173] The network device can receive and display a list of control devices within the discovery range of the input device. The list of control devices can include many different types of control devices, or the types of control devices can be displayed on a separate screen. As Figure 8E shown, the list of discovered control devices can include a list of lighting fixtures that contain lighting control devices that respond to the sent discovery message. The network device can display a fixture identification screen 840 of a list 842 with a fixture identifier 844 (e.g., when the user selects to view the list of fixtures to be added). Although the fixture identification screen 840 is provided as an example, screens of other discovered control devices or a general control device screen can be similarly displayed.

[0174] The list 842 of fixture identifiers 844 can be displayed in an order determined by reducing the signal strength based on the proximity of the fixture to the input device on which the button is actuated (e.g., as described herein). The fixture identifier 844 of the lighting control device characterized by the highest signal strength can be located at the top of the list 842. The network device can display additional fixtures when it recognizes a selection of more fixture options 843. The additional fixtures can be the next group of fixtures in the list of fixtures organized according to signal strength. The list of fixtures can be cycled until returning to the original list of fixtures including the fixture that received the discovery message with the highest signal strength.

[0175] The network device can receive an indication for identifying one of the lighting control devices in the lighting fixture through the user's selection of a flash option 845 next to the corresponding fixture identifier 844 of the lighting control device in the list 844. The network device can send a message to the system controller or directly to the lighting control device to cause the lighting control device to flash the lighting load in the lighting fixture. Other identification options can be displayed and / or selected to identify the control devices displayed in the list in other ways.

[0176] The user can select one or more of the lighting control devices to be associated with the selected input device by selecting a selection icon 846 next to the fixture identifier 844 of the corresponding lighting control device in the list 842. As Figure 8F shown, when the network device receives a selection of a selection icon 846 in the list 842, the selection icon can change to a check icon 848 indicating that the lighting control device with the fixture identifier 844 is selected to be associated with the identified input device. The network device can receive a selection of the flash option 845 to confirm each lighting control device to be associated with the input device. The user can confirm that the lighting control device is in this area (e.g., in the load control environment 100 and / or room 102 shown in FIG. 1).

[0177] When the user has selected the lighting control device in the lighting fixture to be associated with the identified input device (e.g., actuating a button thereon), the network device can receive a selection of the next option 849 on the fixture identification screen 840. The network device can identify the fixture identifier of the lighting control device in the selected lighting fixture to be associated with the input device. The input device and the selected fixture identifier can be stored in the association information at the network device. The network device can send the association information to the system controller and / or the identified device (e.g., or the control target device) in the association information for storage thereon. Although the next option 849 can be identified for generating the association information and / or sending the association message to other devices, the association information can be generated and / or sent for the device when the corresponding selection icon 846 is selected.

[0178] If the lighting control device in the selected lighting fixture has not been included in the currently defined area, the network device can add the fixture identifier to the list of fixture identifiers for defining the area. The network device can add the input device identifier of the input device to the list of input device identifiers for defining the area and store the association information regarding the association between the input device and the lighting control device in the selected lighting fixture. The system controller (e.g., the system controller 160 shown in FIG. 1) can also construct and store the list of fixture identifiers, the list of input devices, and the association information.

[0179] After the association information has been generated for the input device in the defined area, the network device can allow the user to associate other types of control target devices with the identified input device, select another input device to be added to the defined area for generating the association information, or define another area. For example, the user can actuate a button on an occupancy sensor to identify the occupancy sensor as a load control discovery device and send a discovery message from the occupancy sensor. The occupancy sensor can be associated with one or more discovered control devices in the area.

[0180] As Figure 8G shown, the network device can receive and display a list (e.g., list 842) of lighting control devices in the lighting fixtures within the discovery range of the occupancy sensor. The network device can include an indication 850 of association below the fixture identifiers 844 of the load control devices in those lighting fixtures previously associated with the input device. For example, the indication 850 of association can indicate that the load control device in the lighting fixture was previously associated with a remote control device. The indication 850 of association can identify to the user the fixture identifiers 844 of the load control devices in the lighting fixtures that can be associated with the occupancy sensor. For example, the user may wish to associate the occupancy sensor with the load control device in the lighting fixture previously associated with the remote control device. As Figure 8HAs shown, the network device can receive a selection of the selection icon 846 adjacent to the equipment identifier 844 with the associated indication 850, such that the check icon 848 is displayed. The associated indication 850 can also or alternatively indicate a location that may have been associated with the control device. The associated indication 850 can be displayed to identify the equipment that has been configured for a given area, as this information may not be obvious in the list of equipment 842, and the list can identify devices in the order of the signal strength at which the discovery messages were received.

[0181] The area configuration process can be repeated for each area of the building. To associate input devices in an area adjacent to a previously configured area (e.g., the currently configured area), the network device can display information about control devices, such as load control devices in lighting equipment (e.g., previously associated or assigned lighting equipment) in the previously configured area. The network device or system controller can identify control devices for the previously configured area and allow the user to select previously configured devices for association.

[0182] As Figure 8I shown, the network device can display the equipment identifier 844' of the lighting control device in the previously associated lighting equipment in the list 842' of previously associated devices on the equipment identification screen 840. The previously associated control devices can be displayed without performing additional discovery of the devices, or the previously discovered devices can be displayed in response to discovery messages being discovered. The previously discovered messages can be omitted from the list 842 of discovered devices. If the network device identifies a selection of the equipment identifier 844' of a load control device in one of the previously associated lighting equipment, the network device and / or system controller can add the identified device to the association information of the input devices in the defined area.

[0183] As Figure 8J shown, the network device can display a warning window 850 to allow the user to confirm that the user wants to associate an input device with a load control device in the previously associated lighting equipment. The warning window 850 can be superimposed on the screen for adding equipment, or can be provided in a separate screen. If the network device identifies a selection of the confirmation option 852 of the warning window 850, the network device can remove the equipment identifier of the load control device in the previously associated lighting equipment from the list 842' of equipment identifiers for the previously configured area and add the equipment identifier to the list 842 of equipment identifiers for the currently configured area. If the user selects the cancel option 854 on the warning window 850, the network device can maintain the lists of equipment identifiers for the previously configured area and the area currently being configured.

[0184] Figures 8A - 8J The display configuration on the display screen illustrated in FIG. may enable the association of control devices in a load control environment. The display screen may be presented sequentially as the user selection is recognized at the network device, or presented in another order other than the display. The display configuration may enable the area configuration process to define or redefine control areas within the load control system after the installation of the device, and may define control areas according to the devices used for control and their corresponding locations. Since many control devices may be installed in the load control system, when debugging the load control system or otherwise updating the configuration of the load control system, many devices and options for configuring those devices may be provided to the user. Figures 8A - 8J The display configuration illustrated in FIG. may be used to optimize the limited display area on the network device.

[0185] For example, Figures 9A - 9C Another example flowchart showing an example area configuration process 900 that may allow a user (e.g., user 132 in FIG. 1) to configure one or more control source devices (e.g., one or more remote control devices, occupancy sensors, daylight sensors, window sensors, etc.) and control target devices (e.g., one or more lighting control devices for lighting fixtures, electric window treatments, temperature control devices, AC plug load control devices, etc.) for one or more areas in a building is shown. Such configuration may include, for each area in the building, associating one or more control source devices in the area with one or more control target devices in the area such that the control source devices can control the control target devices in the area. The configuration may further include configuring the system controller such that the system controller can control the devices in each area (e.g., automatically through a scheduler, through user input via the network device, etc.).

[0186] As described herein, the configuration process 900 can be implemented using one or more devices such as the control source device 902, one or more control target devices 904, the system controller 906, and / or the network device 908. The network device 908 can interface / communicate with the system controller 906 via a communication network through, for example, a web-based interface provided by the system controller 906 (although other interfaces can be used). The system controller 906 can in turn communicate with the control device 904 via a communication network that can be the same or a different network as that used by the network device 908. The system controller 906 can communicate with the control source device 902 and / or one or more control target devices 904. The control source device 902 can be assigned as a load control discovery device that can communicate with the control target device 904 and / or the system controller 906. The process 900 can include additional, fewer, or other devices and / or messages as discussed herein. The process 900 can include steps in other sequences.

[0187] Starting at 920, a region or location can be created at the network device 908 and the region can be defined at the system controller 906 by being sent to the system controller 906. The region can be created by a user via the network device 908 (such as through a graphical user interface), which can indicate to the system controller 906 that the user wishes to create / define a region. Defining the region can correspond to a specific area (such as room 102 of FIG. 1). The system controller 906 can assign, at 920, the name received in the message to this region. The system controller 906 can define the region in a database, for example, according to the identifier in the message received at 920.

[0188] At 922, the network device 908 can, for example in response to a user selection, indicate to the system controller 906 to add a control source device to the defined region. In response, at 924, the system controller 906 can present, via the network device 908, a list of possible control source devices that the user can add to the region. At 926, the network device 908 can send, for example in response to a user selection, the selected type of control source device. The selected type of control source device can correspond to the control source device 902 that can be installed in the defined region (for example, as a remote control device or a sensor).

[0189] In response to selecting a type of control source device, at 928 the system controller 906 can instruct the user to actuate the control source device 902 located in the defined area, such as by pressing a button on the device, via the network device 908 for example. At 930, the system controller 906 (e.g., automatically or via the network device at the request of the user) can transmit / send a discovery trigger message on the network to one or more control target devices 904 that may be within the communication range of the system controller 906. Upon receiving the message, the control target device 904 can enter a discovery mode in which it will listen for discovery messages. Some control target devices 904 can be in the area being configured (e.g., area 102), and other control target devices 904 can be in other areas that may not currently be configured (e.g., area 104 shown in FIG. 1). For example, the control target devices 904 installed in the area being configured (e.g., area 102) and the control target devices 904 located in other areas that have not yet been configured (e.g., area 104) can receive the discovery trigger message and enter the discovery mode to listen for discovery messages.

[0190] At 932, a discovery message can be sent from the control source device 902. For example, the user can actuate a button or a combination of buttons on the control source device 902 located in the defined area, or can send a trigger message to the control source device 902 (such as via the system controller 906). Upon receiving the actuation or trigger message, the control source device 902 can transmit / send a discovery message on the network. The discovery message can be a broadcast message. As described herein, the discovery message can include a unique identifier of the control source device, the device type of the control source device, an indication of the message type, etc. The system controller 906 and the control target devices 904 within the transmission range of the control source device 902, for example, can receive the discovery message. For example, the control target devices 904 installed in a specific area being configured (e.g., area 102) and the control target devices 904 located in other areas that are not currently configured (e.g., area 104) can receive the discovery message at 932.

[0191] In response to receiving a discovery message, the control target device 904 can calculate the RSSI value of the discovery message as received by the device. In response to receiving the discovery message, at 933 the system controller 906 can convey to the user, e.g., via the network device 908, that the control source device 902 has been detected. A message identifying the detection of the control source device can include specific information about the device (e.g., information included in the discovery message such as device type, unique identifier, discovery criteria, etc.). At 934, the system controller 906 can transmit / send on the network a request for confirmation of the receipt of the discovery message to the control target device 904 that may be within the communication range of the system controller 906. This message can include the unique identifier of the control source device 902 as a request for confirmation of receiving the discovery message from the identified control source device 902.

[0192] In response to receiving a request for a confirmation message from the system controller 906, each respective control target device 904 can determine whether it received the discovery message and, if so, compare the identifier in the discovery message with the identifier in the request for the confirmation message. If the identifiers match, the control target device 904 can transmit / send a confirmation message to the system controller 906, as Figure 9B shown at 936. If the identifiers do not match, the control target device may not respond (e.g., reduce network traffic) or can respond with a negative confirmation. As described herein, the confirmation message can include the unique identifier of the respective control target device 904, the device type of the control target device 904, the respective calculated RSSI value, etc. According to another example, each control target device 904 can calculate / determine a respective random value and transmit its respective confirmation message relative to the calculated random value. Such a process can cause the control target devices 904 to transmit their respective confirmation messages at random times relative to each other, thereby reducing and / or preventing network interference / contention resulting from the devices transmitting substantially simultaneously and the system controller 906 missing one or more messages.

[0193] At 936, the system controller 906 can receive the transmitted confirmation messages from one or more control target devices 904. The system controller 906 can wait a preconfigured duration since transmitting the request for the confirmation message to ensure receipt of each of the transmitted confirmation messages. At 938, the system controller 906 can convey / present to the user, e.g., via the network device 908, information about the control target devices 904 from which the system controller 906 received confirmation messages. This information can include the unique identifier of the respective control target device 904, the type of the respective control target device 904, etc. As discussed herein, the system controller 906 can report / enumerate each of the control target devices 904 from which it received a confirmation message.

[0194] As noted elsewhere herein, control target devices 904 in a region being configured (e.g., region 102) can be detected and control target devices 904 located in other regions (e.g., region 104) can be detected. To assist a user in identifying / distinguishing control target devices of interest, the system controller 906 can filter the control target devices 904 by RSSI values to show the user control target devices that are relatively closer to the control source device that sent the discovery message. A control target device 904 with a higher / stronger RSSI value has a greater likelihood of being in the region currently being configured. Filtering can include sorting a list of control target devices 904 by RSSI value (e.g., in descending order) to show those control target devices whose determined RSSI value is above a predefined received power threshold, and / or showing the top "X" control target devices with the highest RSSI values, etc. Other variations are possible.

[0195] For example, assume that the system controller 906 reports multiple control target devices 904 to the network device 908 and the user cannot discern which control target devices 904 in the region being configured (e.g., region 102) correspond to the control target devices present on the network device. The user, e.g., via the network device 908, can select one or more of the listed control target devices 904 and at 940 indicate to the system controller 906 to cause the selected control target devices 904 to identify themselves to the user. The control target devices 904 can identify themselves by delivering audible and / or visual signals to the user. This can include, for example, the control target device 904 itself providing a signal (e.g., emitting an audible sound, causing an LED to blink), or the control target device 904 causing its corresponding load to provide a signal (e.g., a light turning on, off, or blinking, a shade moving up / down, etc.).

[0196] Upon receiving a request from the user, at 942 the system controller 906 can transmit / send one or more messages over the network to the indicated control target devices 904 to instruct the control target devices 904 to provide identification. In response to the message, the indicated control target devices 904 can provide audible and / or visual signals to the user. At 944, the user, e.g., via the network device 908, can indicate to the system controller 906 to cause one or more of the control target devices 904 selected at 940 to stop delivering audible and / or visual signals to the user. Upon receiving the request, the system controller 906 can at 946 transmit one or more messages over the network to the indicated control target devices 904 to instruct these control target devices to stop providing signals. In response to the message, the control target devices can stop providing audible and / or visual signals to the user. Identifying the devices can assist the user in associating the correct devices at the network device 908.

[0197] At 948, a user can provide association information to the system controller 906, for example, via the network device 908. The association information can be provided to instruct the system controller 906 to, for example, associate the control source device 902 with one or more control target devices 904 presented to the user at 938, and associate the control source device and the one or more control target devices with a defined area (e.g., area 102).

[0198] Upon receiving a request, at 950 the system controller 906 can store in the database, for example, association information (e.g., identifiers, types, etc.) about the control source device 902 and the indicated one or more control target devices 904, an indication that the control source device 902 and the one or more control target devices 904 are associated such that the control source device 902 can control the one or more control target devices 904, and the control source device 902 and the one or more control target devices 904 are associated with a defined area (e.g., area 102). The system controller 906 can transmit the association information to the one or more control target devices 904 indicated by the user at 950. The association information can include various pieces of information that the control target devices 904 can store in their memory / database. This information can include, for example, an identifier of the control source device 902 to instruct the control target devices 904 to listen for and act on control messages transmitted by the control source device 902 (e.g., dim / raise light, raise / lower shade, etc.), an identifier of the system controller 906 to instruct the control target devices 904 to listen for and act on control messages transmitted by the system controller 906 (e.g., dim / raise light, raise / lower shade, etc.), an indication of the area to which the control target device has been assigned, etc. This information can include, for example, one or more identifiers that associate the control target device 902 with one or more broadcast control groups. The control groups can allow, for example, the system controller 906 to broadcast control messages using the corresponding identifiers. When a control target device 904 receives such a message and recognizes that it is part of its group, it can act on the message. For example, such messages can be used to dim each dimmable ballast / driver in a given area.

[0199] As Figure 9C As shown, at 952 the network device 908 can send control configuration information to the system controller 906. The control configuration information can be configured by the user at the network device 908. In response to this information, at 954 and / or 956 the system controller 906 can transmit one or more control configuration information messages to the control source device 902 and / or the control target devices 904 via the network.

[0200] As a partial result of the messages at 952, 954, 956, for example, at 958 the control source device 902 can control one or more associated control target devices. For example, assume that the control source device 902 is a remote control. Actuation of a button on the device by the user can cause the device to transmit a message on the network. One or more associated control target devices 904 configured to listen for messages from the control source device 902 can receive the message and execute the indicated instructions.

[0201] At 960, when the user associates the control source device 902 and the control target device 904 and associates these devices with a defined area (e.g., area 102), the user can use the network device 908 to configure the system controller 906 to control one or more control target devices 904. For example, the user can configure the system controller 906 to automatically control one or more control target devices 904 (e.g., automatically control lighting control devices for lighting fixtures to dim the fixtures at a set time). The system controller 906 can be configured in response to control configuration information received from the network device 908 at 960. In response to such configuration, when, for example, the set time occurs, the system controller 906 can transmit control instructions, i.e., one or more control messages, to one or more control target devices 904 via the network at 962. One or more control target devices 904 configured to listen for messages from the system controller 906 can receive the message and execute the indicated instructions. In response to such commands, the system controller 906 can transmit one or more configuration messages to one or more lighting control devices via the network to dim the lighting fixtures. Other configuration examples are possible.

[0202] Now refer to Figures 9A - 9CExample variations of the configuration process 900. As mentioned above, the system controller 906 can report / enumerate each control target device 904 from which it receives an acknowledgment message. However, as pointed out above, the user can detect control target devices in the area being configured (e.g., area 102) and in other areas (e.g., area 104). As noted, it may be desirable to assist the user in identifying / distinguishing the control target devices of interest 904. Alternatively and / or additionally, as pointed out above, when the control target device 904 transmits an acknowledgment message, even with random transmission, there may be network interference in the case of a large number of devices transmitting messages. According to an example variation of process 900, the process can continue similar to the process described above via step 933. However, at 934, when transmitting a request for an acknowledgment message, the system controller 906 can include in the message a discovery range or band that can correspond to a minimum RSSI value and a maximum RSSI value, e.g., (10 to -50 dBm). As an additional criterion for the control target device 904 to transmit an acknowledgment message to the system controller 906, the corresponding control target device 904 can determine whether its corresponding RSSI value is within the indicated range. If its corresponding RSSI value is within the range, the control target device 904 can transmit the acknowledgment message to the system controller 906 as described in step 936. Again, the message can be transmitted at a random time. Mechanisms other than a range can be used. For example, the system controller 906 can transmit a single value (e.g., -50 dBm), and the control target device 904 can transmit an acknowledgment message to the system controller 906 if its corresponding RSSI value is higher than the said value.

[0203] The system controller 906 can wait again for a preconfigured duration since transmitting the request for the acknowledgment message to receive an acknowledgment message from the control target device. If, at the end of the duration, the system controller 906 fails to receive an acknowledgment message (or less than a predefined threshold number) from the control target device 904, the system controller 906 can repeat step 934 and can automatically transmit a subsequent (e.g., second) request for the acknowledgment message on the network, but at the same time the discovery range is modified. Alternatively, the system controller 906 can report the lack of response to the user, e.g., via the network device 908, and cause the user to initiate the system controller 906 to transmit a subsequent request for the acknowledgment message. The modified range can be a range that includes the previously transmitted range (in whole or in part), or can be a range that is contiguous with the prior range (e.g., the prior range can be 10 to -50 dBm and the next range can be -51 dBm to -54 dBm, etc.).

[0204] Similar to step 936, in response to receiving a subsequent request for a confirmation message from system controller 906, the corresponding controlled target device 904 can determine whether its corresponding RSSI value is within a modified range specified in the subsequent request for the confirmation message, and transmit a confirmation message to system controller 906 if its corresponding RSSI value is within the modified range. Again, the message can be transmitted at a random time. System controller 906 can wait again for a preconfigured duration since transmitting the subsequent request for the confirmation message to receive a confirmation message from controlled target device 904. If, at the end of the duration, system controller 906 has not been able to receive a confirmation message from controlled target device 904, system controller 906 can repeat step 934 again and can automatically transmit an additional (e.g., third) request for the confirmation message on the network, but at the same time find that the range is modified again (e.g., the first range can be 10 to -50 dBm, the second range can be -51 dBm to -54 dBm, and the third range can be -55 to -57 dBm, etc.). Assuming that system controller 906 does receive a reception from controlled target device 904, the process can continue as similarly discussed at step 938.

[0205] According to another aspect of this example, at 938 the user can determine that one or more controlled target devices of interest are not shown in the discovered devices provided to the user via network device 908 (e.g., because controlled target device 904 did not respond with a confirmation message at step 936). Here, the user, for example via network device 908, can instruct system controller 906 to find additional controlled target devices 904. In response to such a request, system controller 906 can transmit another request for a confirmation message on the network as similarly transmitted at step 934, but at the same time find that the range is modified as discussed above.

[0206] Figure 10 is a flowchart of an example area configuration process 1000 for associating a control source device with controlled target devices in a load control area such as load control environment 100 shown in FIG. 1. Area configuration process 1000 can be implemented using one or more devices such as network devices, system controllers, one or more control devices, etc. Area configuration process 1000 can allow a user (e.g., user 132 shown in FIG. 1) to associate one or more control source devices (e.g., input devices) with one or more controlled target devices in a specific area. Area configuration process 1000 can be repeated for different areas of a building.

[0207] Area configuration process 1000 can begin at 1002, such as when the user selects an area creation screen such as Figure 8AWhen the "Create Area" option on the area creation screen 800 shown in [figure number] is selected, the user can assign a name (e.g., a unique name) to the area currently configured at 1004. At 1006, the user can select the type of control source device (e.g., the type of input device) to be associated with one or more of the control target devices (e.g., lighting control devices for lighting fixtures) in the area. For example, the network device can display an input device selection screen from which the user can select control device options, such as the input device selection screen 820 shown in [figure number]. The control device options can be different types of control source devices to be added to the area. Figure 8C as shown in the input device selection screen 820.

[0208] At 1008, a button on the input device can be actuated to put the input device in an association and / or discovery mode. The network device can display a button actuation instruction screen, such as the button actuation instruction screen 830 shown in [figure number], to indicate to the user how to put the input device in the association and / or discovery mode. After appropriately actuating the button on the input device at 1008, the network device can receive and display a list of control devices within the discovery range of the input device at 1010. The network device can display a control device identification screen, which can include a list of control source devices and / or control target devices. The control device identification screen can be similar to the fixture identification screen 840 shown in [figure number]. The list of control devices can be displayed in an order determined by increasing or decreasing the signal strength based on the proximity of the input device on which the button was actuated at 1008. Figure 8D as shown in the button actuation instruction screen 830. Figure 8E as shown in the fixture identification screen 840.

[0209] When the network device receives a selection for each of the control devices to be associated with the input device, the network device can associate the selected control devices with the input device at 1012 in the area configuration process 1000. If the selected control devices are not already included in the current area at 1014, the network device can add the fixture identifiers to the list of fixture identifiers for the area at 1016. The network device can add the input device identifier of the input device to the list of input device identifiers for the area at 1018 and store the association information regarding the association between the input device and the selected control devices at 1020. Although these steps are described herein as being performed by the network device, the system controller or the control device can also build and store the list of control devices, the list of input devices, and the association information.

[0210] If the zone configuration process 1000 is not completed at 1022 (e.g., if there are more input devices in the current zone to be associated with the control device), the zone configuration process 1000 can loop to allow the network device to receive at 1006 a selection of another input device to be associated with one or more of the control target devices in the zone. For example, a user can actuate a button on another control source device to associate that control source device with one or more control target devices in the zone. When the user has completed the configuration of the current zone at 1022, the zone configuration process 1000 can exit. The zone configuration process 1000 can be repeated for each zone of the building.

[0211] Figure 11A and Figure 11B Examples of graphical user interfaces (GUIs) that can be displayed on a visual display of the network device (e.g., the visual display 110 of the network device 128 shown in FIG. 1) for configuring operational settings of a zone (e.g., during or after the zone configuration process 1000). These GUIs can be displayed via a web interface (e.g., generated by a system controller or other remote device) and / or by a control application executed by the network device. The network device can be configured to display a device settings screen 1100. The device settings screen 1100 can display configuration options for configuring the current zone (e.g., zone occupancy configuration options 1102 and zone tuning configuration options 1104). The configuration options can be displayed on the device settings screen 1100 based on the type of input device that has been associated with the control target devices in the zone. For example, if at least one remote control device and at least one occupancy sensor have been associated with a load control device in lighting fixtures in the zone, the zone occupancy configuration options 1102 and zone tuning configuration options 1104 can be displayed on the device settings screen 1100 as shown in Figure 11A If at least one daylight sensor is associated with a control target device (such as a lighting control device in lighting fixtures) in the zone, the zone daylight configuration options 1106 can be displayed on the device settings screen 1100 as shown in Figure 11B In response to a selection of the zone occupancy configuration option 1102, the network device can display a zone occupancy configuration screen (not shown) that allows adjustment of the occupancy configuration (e.g., sensitivity, timeout, etc.) for the zone. In response to a selection of the zone tuning configuration option 1104, the network device can display a zone tuning configuration screen (not shown) that allows adjustment of the dimming range settings (e.g., high-end trim, low-end trim, etc.) for the zone. In response to a selection of the zone daylight configuration option 1106, the network device can display a zone daylight configuration screen (not shown) that allows adjustment of the daylight settings (e.g., daylight gain, etc.) for the zone.

[0212] ​

[0213] The network device can receive a selection of one of the input devices in the list 1106 of previously discovered and / or associated control devices. The list 1106 of previously discovered and / or associated control devices can include devices for a common area or for different areas. The selection of a previously discovered and / or associated control device can allow configuration information (e.g., association information and / or control configuration information) to be displayed and / or modified for storage.

[0214] Figures 12A - 12C Diagrams can be displayed on a visual display of the network device (e.g., the visual display 110 of the network device 128 shown in FIG. 1) as an example graphical user interface (GUI) for configuring control devices in an area (e.g., during or after the area configuration process 1000). These GUIs can be displayed via a web interface (e.g., generated by a system controller or other remote device) and / or by a control application executed by the network device.

[0215] The network device can display a control device configuration screen 1200 that displays configuration options for configuring the currently selected control device. For example, the control device configuration screen can display configuration options for configuring the currently selected remote control device (such as the remote control device 130) as shown in Figure 12A . The control device configuration screen 1200 can be displayed when selecting a previously discovered and / or associated control device in the list 1106 shown in Figure 11A and Figure 11B . For example, the network device can receive a name for the control device and assign the name to the control device currently being configured by entering the name in the control device name text field 1202. The network device can receive instructions for programming the operation of the control device through the user's selection of the programming option 1204. The control device configuration screen 1200 can include an associated device identifier 1206 indicating the number of associated devices controlled by the input device currently being configured. The control device configuration screen 1200 can include an identification button 1208 for sending instructions to the associated devices controlled by the input device so that the associated devices identify themselves. For example, it can be indicated that the lighting control device in the associated lighting fixtures causes the corresponding lighting load to flash.

[0216] The network device can display a control device programming screen 1210 in response to the selection of the programming option 1214. As shown in Figure 12BAs shown, the control device programming screen 1210 may display a preset intensity adjustment window 1212, and the preset intensity adjustment window 1212 may allow for the implementation of adjustment of the preset intensity of the lighting control device for the lighting fixtures in the area. During the control operation, the lighting control device may control the intensity of the controlled lighting load to the preset intensity in response to the actuation of a preset button of the remote control device being programmed currently. The preset intensity adjustment window 1212 may include a single slider control 1214 for adjusting (e.g., simultaneously adjusting) the preset intensity of each of the lighting control devices for the lighting fixtures in the area (e.g., simultaneously adjusting the preset intensity of each of the lighting control devices in the area to a single level). The preset intensity adjustment window 1212 may include an increase icon 1216 for increasing the preset intensity by a predetermined amount (e.g., in response to a single actuation of the increase icon) and a decrease icon 1218 for decreasing the preset intensity by a predetermined amount (e.g., in response to a single actuation of the decrease icon).

[0217] The control device programming screen 1210 may display individual device configuration options 1219 (e.g., “Set by Fixture” option) to allow for the implementation of adjustment of the preset intensity of the load control device for each of the individual lighting fixtures in the area. As Figure 12C shown, the network device may display a preset adjustment screen 1220 in response to the selection of the individual device configuration option 1219. The preset adjustment screen 1220 may display separate preset intensity adjustment windows 1222A, 1222B for each of the lighting control devices for the lighting fixtures in the area (e.g., two fixtures as Figure 12C shown). Each preset intensity level adjustment window 1222A, 1222B may include slider controls 1224A, 1224B for adjusting the preset intensity of the lighting control device for the corresponding lighting fixture. Each preset intensity adjustment window 1222A, 1222B may include an increase icon 1226A, 1226B for increasing the preset intensity by a predetermined amount and a decrease icon 1228A, 1228B for decreasing the preset intensity by a predetermined amount. In response to the actuation of a preset button of the remote control device during the control operation, the lighting control devices may each control the intensity of the controlled lighting load to the corresponding preset intensity set in the preset adjustment screen 1220. The preset intensity may be stored at the network device, the system controller, and / or the lighting control device itself. The preset adjustment screen 1220 may display fixture group level control options 1229 (e.g., “Same Level for Fixture Group” option) to be provided to return to the control device programming screen 1210 to allow for adjustment of each of the preset intensities of the load control devices for the lighting fixtures in the area in response to the single slider control 1214 of the preset intensity adjustment window 1212.

[0218] Figure 13The illustration can be displayed on a visual display of a network device (e.g., the visual display 110 of the network device 128 shown in FIG. 1) for another example graphical user interface (GUI) for button configuration of control devices in an area having more than one type of load control device. The GUI can be displayed via a web interface (e.g., generated by a system controller or other remote device) and / or a control application executed by the network device.

[0219] The area being configured can include one or more load control devices. For example, the area can include one or more of the following types of load control devices: lighting control devices for dimmable lighting fixtures (e.g., dimmable electric lights), lighting control devices for switched lighting fixtures (e.g., switched electric lights), contact closure output (CCO) devices, and controllable outlets. The network device can display a preset programming screen 1300, which can allow adjustment of preset settings for the load control devices in the area. During a control operation, the load control devices can control a controlled electrical load according to the preset settings in response to actuation of a button of a remote control device or other control source device being currently programmed. The preset programming screen 1300 can display a plurality of preset adjustment windows 1302A, 1302B, 1302C, 1302D for each of the different types of load control devices in the area.

[0220] As Figure 13 shown, the preset programming screen 1300 can display a dimmable electric light preset adjustment window 1302A to allow adjustment of a preset intensity level for the lighting control device of the dimmable lighting fixtures in the area. The dimmable electric light preset adjustment window 1302A can include a slider control 1304A for adjusting the preset intensity level for each of the lighting control devices of the dimmable lighting fixtures in the area. The dimmable electric light preset adjustment window 1302A can include an increase icon 1306A for increasing the preset intensity level by a predetermined amount and a decrease icon 1308A for decreasing the preset intensity level by a predetermined amount.

[0221] The preset programming screen 1300 can display a switched electric light preset adjustment window 1302B for adjusting the preset state of the lighting control device of the switched lighting fixture, a contact closure output preset adjustment window 1302C for adjusting the preset state of the contact closure output device, and a socket preset adjustment window 1302D for adjusting the preset state of the controlled socket device. The switched electric light preset adjustment window 1302B, the contact closure output preset adjustment window 1302C, and the socket preset adjustment window 1302D can each display preset state options 1305B, 1305C, 1305D. For example, the displayed preset state options 1305B, 1305C, 1305D can be as Figure 13Shown as on, off, and unaffected.

[0222] Figure 14 is a block diagram illustrating an example network device 1400 as described herein. For example, network device 1400 may include network device 128 shown in FIG. 1. Network device 1400 may include control circuitry 1402 for controlling the functions of network device 1400. Control circuitry 1402 may include one or more general-purpose processors, dedicated processors, conventional processors, digital signal processors (DSPs), microprocessors, integrated circuits, programmable logic devices (PLDs), application-specific integrated circuits (ASICs), etc. Control circuitry 1402 may perform signal encoding, data processing, power control, input / output processing, or any other function that enables network device 1400 to perform as described herein. Control circuitry 1402 may store information in and / or retrieve information from memory 1404. Memory 1404 may include non-removable memory and / or removable memory. Non-removable memory may include random access memory (RAM), read-only memory (ROM), a hard disk, or any other type of non-removable memory. Removable memory may include a subscriber identity module (SIM) card, a memory stick, a memory card, or any other type of removable memory.

[0223] Network device 1400 may include communication circuitry 1408 for transmitting and / or receiving information. Communication circuitry 1408 may perform wireless and / or wired communication. Communication circuitry 1408 may include an RF transceiver or other circuitry capable of performing wireless communication via an antenna. Communication circuitry 1408 may communicate with control circuitry 1402 to transmit and / or receive information.

[0224] Control circuitry 1402 may also communicate with display 1406 to provide information to a user. Processor 1402 and / or display 1406 may generate a GUI for being displayed on network device 1400. Display 1406 and control circuitry 1402 may be in two-way communication because display 1406 may include a touchscreen module capable of receiving information from a user and providing such information to control circuitry 1402. The network device may also include actuators 1412 (e.g., one or more buttons), which may be actuated by a user to convey a user selection to control circuitry 1402.

[0225] Each module within network device 1400 may be powered by a power supply 1410. For example, power supply 1410 may include an AC power supply or a DC power supply. Power supply 1410 may generate a supply voltage Vcc for powering the modules within network device 1400.

[0226] Figure 15is a block diagram illustrating an example system controller 1500 as described herein. The system controller 1500 may include control circuitry 1502 for controlling the functions of the system controller 1500. The control circuitry 1502 may include one or more general-purpose processors, dedicated processors, conventional processors, digital signal processors (DSPs), microprocessors, integrated circuits, programmable logic devices (PLDs), application-specific integrated circuits (ASICs), etc. The control circuitry 1502 may perform signal encoding, data processing, power control, input / output processing, or any other function that enables the system controller 1500 to perform as described herein. The control circuitry 1502 may store information in and / or retrieve information from a memory 1504. The memory 1504 may include non-removable memory and / or removable memory. The non-removable memory may include random access memory (RAM), read-only memory (ROM), a hard disk, or any other type of non-removable memory. The removable memory may include a subscriber identity module (SIM) card, a memory stick, a memory card, or any other type of removable memory.

[0227] The system controller 1500 may include communication circuitry 1506 for sending and / or receiving information. The communication circuitry 1506 may perform wireless and / or wired communication. The system controller 1500 may also or alternatively include communication circuitry 1508 for sending and / or receiving information. The communication circuitry 1506 may perform wireless and / or wired communication. The communication circuitry 1506 and 1508 may communicate with the control circuitry 1502. The communication circuitry 1506 and 1508 may include an RF transceiver or other communication module capable of performing wireless communication via an antenna. The communication circuitry 1506 and the communication circuitry 1508 may be capable of performing communication via the same communication channel or different communication channels. For example, the communication circuitry 1506 may be capable of communicating (e.g., communicating with a network device, communicating over a network, etc.) via a wireless communication channel (e.g., near field communication (NFC), cellular, etc.), and the communication circuitry 1508 may be capable of communicating (e.g., communicating with a control device and / or other devices in a load control system) via another wireless communication channel (e.g., or a proprietary communication channel such as CLEAR CONNECT TM ).

[0228] The control circuit 1502 can communicate with the LED indicator 1512 to provide an indication to the user. The control circuit 1502 can communicate with the actuator 1514 (e.g., one or more buttons), and the actuator 1514 can be actuated by the user to transmit a user selection to the control circuit 1502. For example, the actuator 1514 can be actuated to place the control circuit 1502 in an associated mode and / or transmit an associated message from the system controller 1500.

[0229] Each module within the system controller 1500 can be powered by the power supply 1510. For example, the power supply 1510 can include an AC power supply or a DC power supply. The power supply 1510 can generate a supply voltage Vcc for powering the modules within the system controller 1500.

[0230] Figure 16 is a block diagram illustrating an example control target device (e.g., the load control device 1600) as described herein. The load control device 1600 can be a dimmer switch, an electronic switch, an electronic ballast for an electric lamp, an LED driver for an LED light source, an AC plug-in load control device, a temperature control device (e.g., a thermostat), a motor drive unit for an electric window covering, or other load control device. The load control device 1600 can include a communication circuit 1602. The communication circuit 1602 can include a receiver, an RF transceiver, or other communication modules capable of performing wired and / or wireless communication via the communication link 1610. The communication circuit 1602 can communicate with the control circuit 1604. The control circuit 1604 can include one or more general-purpose processors, dedicated processors, conventional processors, digital signal processors (DSPs), microprocessors, integrated circuits, programmable logic devices (PLDs), application-specific integrated circuits (ASICs), etc. The control circuit 1604 can perform signal encoding, data processing, power control, input / output processing, or any other function that enables the load control device 1600 to perform as described herein.

[0231] The control circuit 1604 can store information in and / or retrieve information from the memory 1606. For example, the memory 1606 can maintain a registry of associated control devices and / or control configuration instructions. The memory 1606 can include non-removable memory and / or removable memory. The load control circuit 1608 can receive instructions from the control circuit 1604 and can control the electrical load 1616 based on the received instructions. The load control circuit 1608 can send status feedback regarding the status of the electrical load 1616 to the control circuit 1604. The load control circuit 1608 can receive power via the hot connection 1612 and the neutral connection 1614 and can provide a certain amount of power to the electrical load 1616. The electrical load 1616 can include any type of electrical load.

[0232] The control circuit 1604 can communicate with an actuator 1618 (e.g., one or more buttons), and the actuator 1618 can be actuated by a user to transmit a user selection to the control circuit 1604. For example, the actuator 1618 can be actuated to place the control circuit 1604 in an association mode or a discovery mode and can transmit an association message or a discovery message from the load control device 1600.

[0233] Figure 17 is a block diagram illustrating an example control source device 1700 as described herein. The control source device 1700 can be a remote control device, an occupancy sensor, a daylight sensor, a window sensor, a temperature sensor, and / or the like. The control source device 1700 can include a control circuit 1702 for controlling the functions of the control source device 1700. The control circuit 1702 can include one or more general-purpose processors, dedicated processors, conventional processors, digital signal processors (DSPs), microprocessors, integrated circuits, programmable logic devices (PLDs), application-specific integrated circuits (ASICs), etc. The control circuit 1702 can perform signal encoding, data processing, power control, input / output processing, or any other function that enables the control source device 1700 to operate as described herein.

[0234] The control circuit 1702 can store information in and / or retrieve information from a memory 1704. As described herein, the memory 1704 can include non-removable memory and / or removable memory.

[0235] The control source device 1700 can include a communication circuit 1708 for sending and / or receiving information. The communication circuit 1708 can send and / or receive information via wired and / or wireless communication. The communication circuit 1708 can include a transmitter, an RF transceiver, or other circuitry capable of performing wired and / or wireless communication. The communication circuit 1708 can communicate with the control circuit 1702 to send and / or receive information.

[0236] The control circuit 1702 can also communicate with an input circuit 1706. The input circuit 1706 can include an actuator (e.g., one or more buttons) or a sensor circuit (e.g., an occupancy sensor circuit, a daylight sensor circuit, or a temperature sensor circuit) for receiving an input that can be sent to the device to control an electrical load. For example, the control source device can receive an input from the input circuit 1706 to place the control circuit 1702 in an association mode and / or transmit an association message from the control source device. The control circuit 1702 can receive information (e.g., an indication that a button has been actuated or sensed information) from the input circuit 1706. Each module within the control source device 1700 can be powered by a power supply 1710.

[0237] Although the features and elements are described herein in particular combinations, each feature or element may be used alone or in any combination with other features and elements. The methods described herein may be implemented with a computer program, software, or firmware included in a computer-readable medium for execution by a computer or processor. Examples of computer-readable media include electronic signals (sent via wired or wireless connections) and computer-readable storage media. Examples of computer-readable storage media include, but are not limited to, read-only memory (ROM), random access memory (RAM), removable disks, and optical media such as CD-ROM disks and digital versatile disks (DVDs).

Claims

1. A system controller, comprising: at least one communication circuit configured to send and receive digital messages; and a control circuit for: receiving an association mode trigger message; and in response to receiving the association mode trigger message: identifying one of the plurality of control devices as a load control discovery device; wherein the plurality of control devices includes one or more control source devices and one or more control target devices; causing the load control discovery device to broadcast a discovery message; broadcasting a query message to the plurality of control devices, the query message for requesting a response from the plurality of control devices to indicate whether the plurality of control devices have received the discovery message from the load control discovery device; receiving a response message from each of one or more control devices among the plurality of control devices that have received the discovery message above a predefined signal strength threshold; transmitting information to a network device, the information indicating one or more control devices among the plurality of control devices that have received the discovery message above the predefined signal strength threshold; and receiving association information from the network device to form an association between the control source devices and control target devices included in the plurality of control devices, such that the control source devices enable the associated control target devices to control an operably coupled electrical load.

2. The system controller according to claim 1, wherein, the control circuit is configured to: sort the one or more control devices among the plurality of control devices according to the respective signal strength of the discovery message received by each of the one or more control devices among the plurality of control devices.

3. The system controller according to claim 2, wherein, the control circuit is configured to: sort the one or more control devices among the plurality of control devices in descending order of the respective signal strength.

4. The system controller according to claim 2, wherein, the control circuit is configured to define the predefined signal strength threshold.

5. The system controller according to claim 2, wherein, the control circuit is configured to store the received association information.

6. The system controller according to claim 1, wherein, the control circuit is configured to: receive the discovery message from the load control discovery device via the at least one communication circuit, wherein the load control discovery device is identified based on the discovery message received from the load control discovery device; and wherein, in order to receive a response message from each of the one or more control devices among the plurality of control devices, the control circuit: receives a response message including a device identifier associated with the corresponding control device.

7. The system controller according to claim 6, wherein, the control circuit is configured to: send a request via the at least one communication circuit to the plurality of control devices to confirm receipt of the discovery message; and Receiving the response message from each of the plurality of control devices in response to the request for confirming receipt of the discovery message.

8. The system controller according to claim 7, wherein, in order to receive the response message from each of the one or more control devices among the plurality of control devices, the control circuit receives a response message from each of the one or more control devices among the plurality of control devices, the response message including the signal strength at which the corresponding control device received the discovery message.

9. A load control system, comprising: a plurality of control devices; wherein the plurality of control devices includes a control source device and a control target device; wherein the control target device is configured to control the amount of power supplied to an electrical load based on a digital message received from the control source device; wherein at least one of the control source device or the control target device is determined to be a load control discovery device configured to send a discovery message to the plurality of control devices; and wherein each of the plurality of control devices identifies the signal strength of the received discovery message and determines whether the identified signal strength is above a predefined signal strength threshold; and a system controller; wherein the system controller is configured to broadcast a query message to the plurality of control devices, the query message for requesting a response from the plurality of control devices, thereby indicating whether the plurality of control devices received a discovery message from the load control discovery device; wherein the system controller is configured to receive an acknowledgement from one or more control devices among the plurality of control devices that received the discovery message above the predefined signal strength threshold; wherein the system controller is configured to notify a network device of the one or more control devices among the plurality of control devices that received the discovery message above the predefined signal strength threshold; and wherein the system controller is configured to receive association information from the network device, the association information indicating an association between at least two control devices among the one or more control devices among the plurality of control devices, so as to enable control of the electrical load at the location.

10. The load control system according to claim 9, wherein, the system controller is configured to: sort the one or more control devices among the plurality of control devices according to the respective signal strength of the discovery message received by each of the one or more control devices among the plurality of control devices.

11. The load control system according to claim 10, wherein, the system controller is configured to: sort the one or more control devices among the plurality of control devices in descending order of the respective signal strength.

12. The load control system according to claim 10, wherein, the system controller defines the predefined signal strength threshold.

13. A method for configuring a load control system, the method comprising: receiving an association mode trigger message via a communication circuit communicatively coupled by a control circuit; and in response to the control circuit receiving an associated mode trigger message: through the control circuit, identifying one of the plurality of control devices as a load control discovery device; wherein the plurality of control devices includes one or more control source devices and one or more control target devices; and through the control circuit causing the load control discovery device to broadcast a discovery message to the plurality of control devices; through the control circuit, broadcasting a query message to the plurality of control devices, the query message being used to request a response from the plurality of control devices, thereby indicating whether the plurality of control devices has received the discovery message from the load control discovery device; through the control circuit, receiving a response message from each of one or more control devices among the plurality of control devices that have received the discovery message above a predefined signal strength threshold; through the control circuit, transmitting information to the network device, the information indicating the one or more control devices among the plurality of control devices that have received the discovery message above the predefined signal strength threshold; and through the control circuit, receiving association information from the network device via a communicatively coupled communication circuit to form an association between the control source device and the control target device included in the plurality of control devices, whereby the control source device enables the associated control target device to control an operatively coupled electrical load.

14. The method according to claim 13, further comprising: sorting one or more of the plurality of control devices by the control circuit according to the respective signal strength of the discovery message received by each of the one or more control devices among the plurality of control devices.

15. The method according to claim 14, wherein, sorting one or more of the plurality of control devices according to the respective signal strength further comprises: sorting one or more of the plurality of control devices by the control circuit in descending order of the respective signal strength of the received discovery message.

16. The method according to claim 14, further comprising: defining the predefined signal strength threshold by the control circuit.

17. The method according to claim 14, further comprising: storing the received association information by the control circuit.

18. The method according to claim 13, further comprising: receiving the discovery message from the load control discovery device by the control circuit via the communicatively coupled communication circuit, wherein the load control discovery device is identified based on the discovery message received from the load control discovery device; and wherein receiving a response message from each of one or more control devices among the plurality of control devices that have received the discovery message further comprises: receiving, by the control circuit, a response message including a device identifier from each of one or more control devices among the plurality of control devices.

19. The method according to claim 18, further comprising: sending, by the control circuit, a request for confirming receipt of the discovery message to the plurality of control devices via the communication circuit; and In response to the request for confirming reception of the discovery message, the response message is received from each of the one or more control devices among the plurality of control devices via the communication circuit by the control circuit.

20. The method according to claim 19, wherein, receiving the response message from each of the one or more control devices among the plurality of control devices further comprises: receiving, by the control circuit via the communication circuit, from each of the one or more control devices among the plurality of control devices, a response message including a signal strength at which the corresponding control device received the discovery message.

Images