Debugging and controlling a load control device

Abstract

A load control system can be debugged using beacons. The load control system can include control devices, each of which includes a beacon transmitting circuit configured to transmit a beacon including an identifier associated with the control device. A network device such as a mobile device can discover the control device based on the beacon received from the control device. In response to the discovery of the control device, the control device can be added to a temporary group of control devices for collective configuration and / or control. The control device can be discovered based on the signal strength at which the beacon is received. The control device can provide feedback to a user in response to an acknowledgement message to indicate to the user that the control device has been added to the temporary group. After the control device is removed from the temporary group, the control device can stop providing the feedback.

Description

[0001] Cross - Reference to Related Applications

[0002] This application claims the benefit of U.S. Provisional Patent Application No. 62 / 815,692, filed on Mar. 8, 2019; U.S. Provisional Patent Application No. 62 / 817,481, filed on Mar. 12, 2019; U.S. Provisional Patent Application No. 62 / 896,268, filed on Sep. 5, 2019; U.S. Provisional Patent Application No. 62 / 898,500, filed on Sep. 10, 2019; and U.S. Provisional Patent Application No. 62 / 879,227, filed on Jul. 26, 2019, the disclosures of which are incorporated herein by reference in their entireties. Background Art

[0003] A load control system may include an electrical load (e.g., a lighting load, etc.) and a load control device (e.g., a ballast, a light - emitting diode (LED) driver, etc.) for controlling the electrical power to the lighting load. The load control device may be controlled by a message from a remote control device or a sensor (e.g., an occupancy sensor, etc.), and the remote control device or sensor is capable of sending instructions to the load control device via a digital message for controlling the electrical load. The load control device may receive communication from a system controller for performing load control, and the system controller is programmable with configuration information for controlling the load control devices in the system. After installing the device in the load control system, the load control system can be debugged to achieve proper configuration and communication of the device for controlling the electrical load.

[0004] Generally, after installing a load control system in a location (such as a residence, an office, etc.), the system controller may assign a link address to the lighting control devices controlled by the system controller. The link address can be used to send instructions to the load control device for controlling the electrical load. This assignment may be random. For example, the system controller may be able to control multiple lighting control devices, such as lighting ballasts or LED drivers, and may randomly assign different link addresses to each lighting control device.

[0005] It is difficult to determine the link address assigned to a load control device at a specific location after installation to enable control of the electrical load at a location from other devices (such as a remote control device, an occupancy sensor, or the system controller). For example, a floor plan may identify the load control devices and their corresponding locations in a room or a building, while the system controller may store a list of the assigned link addresses, and the location of the load control device to which the link address is assigned is unknown.

[0006] To control a load control device at a desired location, during a commissioning process, a user may have to identify lighting loads controlled by lighting control devices having assigned link addresses and associate the link addresses with the identified locations in a building. Since a building may include many lighting control devices with unknown link addresses (e.g., in different rooms, floors, etc.), the user may have to power the lighting loads with known link addresses and search for the locations in the building of the lighting loads being controlled (e.g., turned on, flashed, etc.) in order to associate the physical locations of the lighting control devices with the assigned link addresses of the lighting control devices. The lights being controlled may be in different rooms than the room currently occupied by the user configuring the system, which may cause the user to have to move around the building to different rooms back and forth to commission the system.

[0007] The commissioning process may include engaging lighting control devices to a network. If a building includes many lighting control devices, it may be time-consuming to engage each lighting control device individually. Additionally, the building may not have access to the Internet while the commissioning process is being performed. The lighting control devices may not be able to be engaged to the network without Internet access.

[0008] Similar time-consuming processes may be implemented to configure other devices in a load control system. The process of identifying the locations of control devices in a system and associating the devices to achieve proper load control during system commissioning may be time-consuming and expensive. SUMMARY

[0009] A load control system may be commissioned as described herein for controlling one or more electrical loads. During commissioning of the load control system, one or more control devices may be discovered and / or selected for collective configuration and / or control. The selected control devices may be included in a temporary group of control target devices for configuration and / or control. For example, a load control system may include lighting control devices that can be selected and / or grouped for collective control in a certain location or area. Control devices may be added to and / or removed from a temporary group for collective configuration and / or control. The temporary group may also include at least one control source device, such as an occupancy sensor or a remote control sensor, for enabling control of the temporary group of control devices based on messages received from the control source device.

[0010] The load control system may be commissioned using beacons. For example, a load control system may include lighting control devices, each including a beacon transmission circuit configured to transmit a respective beacon including an identifier associated with the lighting control device. A network device may discover the lighting control devices based on the beacons received from the lighting control devices. In response to the discovery of a lighting control device, the lighting control device may be added to a temporary group of lighting control devices for collective configuration and / or control.

[0011] Beacons can be emitted periodically and / or in response to a trigger event. For example, beacons can be emitted in response to a digital message, actuation of a button on a control device, or in response to an occupancy condition detected by an occupancy sensor. A lighting control device in a load control system can communicate directly with an occupancy sensor (e.g., installed in the same luminaire), and the lighting control device can emit a beacon (e.g., each beacon, or initiate periodic emission of beacons) in response to an occupancy condition detected by the occupancy sensor.

[0012] Control devices can be discovered based on the signal strength at which the corresponding beacons are received. For example, a lighting control device can be discovered when the signal strength at which the corresponding beacon of the lighting control device is received is above a discovery threshold. The discovery threshold can be adjusted to discover other control devices in a wider or more limited range.

[0013] A configuration message can be sent to a control device, indicating that the control device has been added to a temporary group selected for collective configuration and / or control. The control device can provide feedback to the user in response to an acknowledgement message to indicate that they have been added to the temporary group. For example, a lighting control device can provide feedback via the corresponding lighting load in response to an acknowledgement message to indicate to the user that the lighting control device has been added to the temporary group. The lighting control device can provide feedback by causing the corresponding lighting load to blink on and off; increasing or decreasing the brightness level of the corresponding lighting load; or enhancing and dimming the color (e.g., color temperature) of the corresponding lighting load.

[0014] A network device can display the discovered devices among the lighting control devices in the temporary group for collective configuration or control. The network device can receive an indication to remove at least one of the discovered devices in the temporary group from the temporary group. For example, a user can select one or more devices to remove from the temporary group. The network device can remove the indicated device from the group and can send a digital message to the removed device. The digital message can cause the removed device to stop providing feedback via the corresponding lighting load.

[0015] An occupancy sensor in a load control system can emit a beacon to a lighting control device to provide feedback on the occupancy / vacancy emission range of the occupancy sensor to the user. The lighting control device can receive the beacon from the occupancy sensor and compare the signal strength at which the beacon from the occupancy sensor is received with a wireless threshold corresponding to the occupancy / vacancy emission range of the occupancy sensor. In response to the signal strength of the beacon from the occupancy sensor being higher than the wireless threshold, the lighting control device can provide feedback by changing the state of the corresponding lighting load. The lighting control device providing feedback can indicate the occupancy / vacancy emission range of the occupancy sensor starting from the current location of the occupancy sensor to assist in configuring the placement of the occupancy sensor in the space.

[0016] A network device and a commissioning device (e.g., a system controller) can be used to couple lighting control devices in a load control system to a network. For example, the lighting control devices can be coupled to the network when the network device and / or the system controller are operating in an offline mode. The lighting control devices can be first solicited by the network device. Soliciting a lighting control device can include: highlighting the lighting control device on a display of the network device; assigning the lighting control device to a zone; receiving device identification data from the lighting control device; and / or transmitting configuration information to the lighting control device. Once each lighting control device within a given zone has been solicited, the network device can transmit the received device identification data to the system controller. The lighting control devices can then be coupled to the network by the system controller. For example, the system controller can send a coupling request to a subset of the lighting control devices. Upon receiving a response to the coupling request from the lighting control device, the system controller can couple the lighting control device to the network. BRIEF DESCRIPTION OF THE DRAWINGS

[0017] Figure 1 Illustrate a representative load control system for using beacons to configure and / or control one or more control devices.

[0018] Figure 2A 、 Figure 2B 、 Figure 2C and Figure 2D Illustrate a representative load control environment in which the Figure 1 illustrated load control system can be implemented for using beacons to configure and / or control one or more control devices.

[0019] Figure 2E is a diagram of an exemplary network for communication within a load control system for Figure 1 the same.

[0020] Figure 3 is a system diagram illustrating a representative control system for using beacons to configure and / or control one or more control devices.

[0021] Figure 4A is a flowchart depicting an exemplary method (e.g., a commissioning procedure) for commissioning a control system.

[0022] Figure 4B is a flowchart depicting an exemplary method of a solicitation procedure for soliciting devices for commissioning a control system in an offline mode.

[0023] Figure 4C is a flowchart depicting an exemplary method of a coupling procedure for coupling devices in a control system to a network in an offline mode.

[0024] Figure 4D and Figure 4EIt is a system flowchart depicting an exemplary message flow for discovering a control device for implementing a claim for and / or associating with a control device.

[0025] Figures 5A to 5J It is an exemplary screenshot of a user interface for implementing the configuration and / or control of a lighting control device via a network device.

[0026] Figure 6A It is a flowchart depicting an exemplary method for discovering a control device for implementing a claim for and / or associating with a control device.

[0027] Figure 6B It is another flowchart depicting an exemplary method for discovering a control device for implementing a claim for and / or associating with a control device.

[0028] Figure 7A It is a flowchart depicting an exemplary method for discovering a control device using a beacon and providing feedback for implementing configuration and / or control.

[0029] Figure 7B It is another flowchart depicting an exemplary method for discovering a control device using a beacon and providing feedback for implementing configuration and / or control.

[0030] Figure 7C It is yet another flowchart depicting an exemplary method for discovering a control device using a beacon and providing feedback for implementing configuration and / or control.

[0031] Figure 8 It shows an exemplary interface that can be displayed on a network device for configuring and / or controlling one or more control devices.

[0032] Figure 9 It is a flowchart depicting an exemplary method for discovering a control device using a beacon for implementing configuration and / or control.

[0033] Figure 10 It is a flowchart depicting another exemplary method for discovering a control device using a beacon for implementing configuration and / or control.

[0034] Figure 11 It is a flowchart depicting an exemplary method for transmitting configuration data of a load control system.

[0035] Figure 12 It is a block diagram illustrating an exemplary network device as described herein.

[0036] Figure 13 It is a block diagram of an exemplary system controller.

[0037] Figure 14 It is a block diagram illustrating an exemplary load control device.

[0038] Figure 15 It is a block diagram illustrating an exemplary control source device. Detailed implementation

[0039] To debug a load control system, one or more control devices can be identified and / or selected for collective configuration and / or control to achieve load control. The control devices can include at least one control target device (e.g., a load control device) and at least one control source device. The control target device can control an electrical load based on messages received from an associated control source device. A single control device in the load control system can be both a control target device and a control source device. For example, a load control device can operate as a control target device to receive messages for controlling an electrical load, and can operate as a control source device to transmit messages to another load control device for controlling the electrical load.

[0040] Debugging the load control system can include identifying and / or associating control source devices and / or control target devices for individual and / or collective control. Devices can be associated with each other by storing their identifiers together in a memory. Control devices can be associated in a temporary group to allow control of the devices in the group. Devices can be associated with a temporary group by storing their identifiers together with a temporary group identifier in a memory. The association can be stored at the control device or at other devices in the load control system, and is referenced to appropriately respond to achieve load control between the associated devices in the system.

[0041] Beacons (e.g., control device beacons) can be used to identify and / or select control devices for collective configuration and / or control. The selected control devices can be temporarily grouped for configuration and / or control. The control device beacon can include unique identification information, which can be used to identify and / or select control devices for collective configuration and / or control in a load control environment. The control device beacon can indicate or be used to indicate the proximity or location of the device and / or the current state of the device. The control device beacon can include a primary identifier and a secondary identifier of the control device (e.g., a load control device). The primary identifier can include the unique identifier of the corresponding control device, and the secondary identifier can include the unique identifier of the control device type, or vice versa. The primary identifier and the secondary identifier can be combined to identify the unique identifier of the control device.

[0042] A network device (e.g., a mobile device) may also transmit a beacon (e.g., a mobile device beacon). The mobile device beacon may include unique identification information that can be used to identify the network device and / or a received signal strength discovery threshold. Additionally, a beacon transmitting device may transmit a beacon (e.g., a location beacon). The location beacon may include unique identification information that can be used to identify the location of the beacon transmitting device and / or a received signal strength discovery threshold. The beacon transmitting device may be a control device, or the beacon transmitting device may be a device independent of the control device.

[0043] A beacon (e.g., a control device beacon, a location beacon, and / or a mobile device beacon) may be transmitted as a radio frequency (RF) communication signal or as another type of signal that can be received by another control device, network device, and / or beacon transmitting device in close proximity to the device transmitting the beacon. The beacon may be transmitted as a short-range RF communication signal. For example, the beacon may be an RF signal that uses a communication protocol or a Bluetooth Low Energy (BLE) communication protocol to convey. When transmitting a beacon using an RF communication signal, the beacon may be identified by the device to indicate that the device is within the proximity or location of the device transmitting the beacon. The proximity of the device to the beacon transmitting device may be determined by the signal strength at which the RF communication signal of the beacon is received. Although the beacon may be described herein as using a communication protocol to convey, other RF communication protocols may be implemented. For example, the beacon may use a Near Field Communication (NFC) protocol, a protocol, a WI-FI communication protocol, and / or other RF communication protocols to transmit.

[0044] The control device may be set or configured using a beacon to perform load control for debugging a load control system. The control devices may be associated with each other and / or with locations using beacons, as described herein. Control devices associated with locations may be implemented to perform load control at those locations.

[0045] Figure 1Illustrate a representative load control system 100 for configuring and / or controlling one or more control devices using beacons. The load control system 100 may include a lighting fixture 110 (e.g., a panel lighting fixture) having one or more lighting loads 112 (e.g., light-emitting diode (LED) light sources 208). The lighting fixture 110 may also include a lighting control device 114 (e.g., an LED driver) for controlling the amount of power supplied to the lighting load 112 of the lighting fixture 110. The lighting control device 114 may be installed within the lighting fixture 110, mounted to an outer surface of the lighting fixture 110, and / or mounted adjacent to the lighting fixture 110 (e.g., outside the lighting fixture 110). The lighting control device 114 of the lighting fixture 110 may operate as a controlled target device to control the amount of power supplied to the lighting load 112 in response to a message received from a control source device to control the brightness level of the lighting fixture 110.

[0046] The load control system 100 may include lighting fixtures 120a to 120c controlled by a load controller 121. Each of the lighting fixtures 120a to 120c may have one or more respective lighting loads 122a to 122c (e.g., LED light sources) and respective lighting control devices 124a to 124c (e.g., LED drivers) for controlling the amount of power supplied to the one or more respective lighting loads of the lighting fixtures. The load controller 121 may be coupled to the lighting control devices 124a to 124c via a communication link 125 (e.g., a wired digital communication link). The load controller 121 may be configured to individually control the lighting control devices 124a to 124c to thus individually control the lighting loads 122a to 122c. The load controller 121 may operate as a controlled target device to control the lighting control devices 124a to 124c in response to a message received from a control source device to control the power supplied to the lighting loads 122a to 122c to control the brightness levels of the lighting fixtures 120a to 120c. Additionally, the load control system 100 may include lighting fixtures having multiple controllable light sources that can be controlled by a single load controller, such as the load controller 121.

[0047] The load control system 100 may further include a lighting fixture 130 (e.g., a downlight), and the lighting fixture 130 has a controllable light source 132 (e.g., a controllable LED lamp). The controllable light source 132 may include an integrated lighting control device (e.g., an LED driver) for controlling the amount of power supplied to the internal lighting load of the controllable light source 132. For example, the controllable light source 132 may be screwed into a standard Edison socket of the lighting fixture 130. The controllable light source 132 of the lighting fixture 130 may operate as a control target device to control the brightness level of the lighting load of the controllable light source 132 in response to a message received from a control source device. Although the lighting control device 114, the lighting control devices 124a to 124c, and the controllable light source 132 are provided as exemplary control target devices, the load control system 100 may include other control target devices, such as, for example, electric window coverings, temperature control devices, and / or plug-in load control devices.

[0048] The lighting levels of the lighting fixture 110, the lighting control devices 124a to 124c, and / or the controllable light source 132 may be controlled according to lighting control instructions received from a control source device. The control source device may be capable of communicating a message to a control target device (e.g., a load control device, such as a lighting control device) via a wired and / or wireless signal to control an electrical load (e.g., a lighting load). Exemplary control source devices in the load control system 100 may include an occupancy sensor 134, a remote control device 136, and / or another control source device capable of communicating a message to the lighting control device 114, the lighting control devices 124a to 124c, and / or the controllable light source 122 to perform control. The load control system 100 may further include a system controller 140 and a network device (such as a mobile device 150), which may also operate as control source devices. For example, the mobile device 150 may include a smart phone and / or a tablet computer.

[0049] The amount of power delivered to the lighting load 112 of the lighting fixture 110, the lighting loads 122a to 122c of the lighting control devices 124a to 124c, and / or the controllable light source 132 may be controlled in response to lighting control instructions received from a control source device (e.g., an occupancy sensor 134, a remote control device 136, a system controller 140, a mobile device 150, and / or another control source device). The lighting level may be controlled according to lighting control configuration information that may be stored at the lighting control device 114, the lighting control devices 124a to 124c, the controllable light source 132, and / or the system controller 140 or the mobile device 150, such as preset configuration, regional configuration, occupancy configuration, and / or scheduling configuration information. The lighting control instructions may be transmitted over a wireless communication network (e.g., a Thread network) via a radio frequency (RF) signal 102).

[0050] The occupancy sensor 134 can be a control source device configured to detect occupancy and / or vacancy conditions in the space in which the load control system 100 is installed. The occupancy sensor 134 can transmit a message via the RF communication signal 102 in response to detecting an occupancy or vacancy condition. The RF signal 102 can communicate the message via one or more protocols (e.g., standard communication protocols such as WI- NFC; Thread; and / or proprietary communication protocols such as CLEAR CONNECT TM 、Z-WAVE). Although Figure 1 illustrates the occupancy sensor 134 communicating a message via the RF communication signal 102, the occupancy sensor 134 can communicate via wired communication.

[0051] The system controller 140 can be configured to turn on or off the lighting load of one or more lighting fixtures (e.g., lighting loads 112, 122a to 122c, and / or controllable light sources 122) in response to receiving an occupancy signal and a vacancy signal, respectively. The occupancy sensor 134 can operate as a vacancy sensor such that the lighting load can be manually turned on by a user and / or automatically turned off in response to detecting a vacancy signal from the sensor (e.g., the lighting load does not turn on in response to detecting an occupancy condition). Examples of load control systems with occupancy and vacancy sensors are described in more detail in the following co-assigned patents: U.S. Patent No. 8,009,042, titled "RADIO-FREQUENCY LIGHTING CONTROL SYSTEM WITH OCCUPANCY SENSING," issued on August 30, 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 hereby incorporated by reference.

[0052] Although the occupancy sensor 134 may be shown as being located outside the luminaire 110, the sensor 116 may be incorporated within the luminaire 110 and / or communicate directly (e.g., wired or wirelessly) with the lighting control device 114 of the luminaire 110 for controlling the lighting load 112. Additionally, the load controller 121 may be connected to the sensor 126. The sensors 116, 126 may be used to control the luminaire 110 and / or the lighting control devices 124a-124c, respectively. The sensors 116, 126 may be occupancy sensors, visible light sensors (e.g., cameras), daylight sensors, optical sensors, and / or any other type of sensor. The sensors 116, 126 may be occupancy sensors capable of detecting occupancy / vacancy conditions (e.g., using infrared signals). The sensors 116, 126 may be visible light sensors (e.g., cameras) capable of detecting changes within the visible space of the sensors 116, 126.

[0053] The sensors 116, 126 may be configured to operate similarly to the occupancy sensor 134, but may communicate directly with the lighting control device 114 of the luminaire 110 and the load controller 121, respectively. For example, the lighting control device 114 of the luminaire 110 may turn on and off the lighting load 112 in response to receiving occupancy and vacancy signals from the sensor 116, respectively. Similarly, the load controller 121 may turn on and off the lighting loads 122a-122c in response to receiving occupancy and vacancy signals from the sensor 126, respectively.

[0054] The remote control device 136 may be a control source device configured to transmit a message to the system controller 140 and / or directly to the lighting control device 114, the load controller 121, and / or the controllable light source 122 via an RF communication signal 102 in response to actuation of one or more buttons of the remote control device 136. Although Figure 1 the remote control device 136 is shown communicating a message via the RF communication signal 102, the remote control device 136 may communicate via wired communication. The remote control device 136 may be a wall switch, a dimmer switch, or another remote control device for controlling an electrical load. The system controller 140 may also originate one or more messages.

[0055] The system controller 140 may be configured to transmit one or more messages to the lighting control device 114, the load controller 121, and / or the controllable light source 132 of the lighting fixture 110 in response to messages received from an associated control source device such as the occupancy sensor 134, the remote control device 136, the mobile device 150, and / or another control source device. The system controller 140 may communicate with the lighting control device 114, the load controller 121, and / or the controllable light source 132 in the lighting fixture 110 via wired and / or wireless communication. For example, the system controller 140 may communicate with the lighting control device 114, the load controller 121, and / or the controllable light source 132 in the lighting fixture 110 via the RF communication signal 102. The system controller 140 may communicate with other lighting control devices (e.g., a group of lighting control devices, etc.) of the lighting fixtures in the load control system 100.

[0056] The system controller 140 may communicate directly with the mobile device 150 via wired and / or wireless communication. The system controller 140 may communicate with the mobile device 140 via the network communication device 142. The network communication device 142 may be a wireless access point such as, for example, a wireless router and / or a modem. The network communication device 142 may communicate with the mobile device 150 via the network communication signal 106 (e.g., a network communication signal, using protocol, WI- protocol, etc.) to allow the mobile device 150 to communicate with other computing devices and / or networks (e.g., via the Internet). The system controller 140 may communicate with the network communication device 142 via the communication link 144, and the communication link 144 may be a wired and / or wireless communication link. For example, the wireless communication link may allow the system controller 140 to wirelessly communicate with the network communication device 106 using cellular, WI- near field communication (NFC), etc. Although the system controller 140 and the network communication device 142 are shown as separate devices in Figure 1 the network communication device 142 may be included in the system controller 140. The network communication device 142 may also be configured to communicate with network devices such as the processing device 160 (e.g., a personal computer and / or a laptop computer) via the communication link 146, and the communication link 146 may be a wired and / or wireless communication link.

[0057] The mobile device 150 can be implemented to configure the load control system 100. For example, the mobile device 150 can be used to discover and / or associate load control devices (e.g., control source devices and / or control target devices) for performing load control. The mobile device 150 can be a cellular phone (e.g., a smart phone), a tablet computer, a personal digital assistant, a personal computer, a laptop computer, a wearable computing device (e.g., glasses, a watch, a wristband, etc.), or other mobile computing devices.

[0058] The mobile device 150 can transmit a beacon (e.g., a mobile device beacon). The mobile device beacon can include, for example, a beacon identifier. For example, the beacon identifier can be a unique identifier that identifies the mobile device 150 (e.g., or an application executed on the mobile device 150), and / or a non-unique identifier, such as an identifier of a group, a region, a building, a load control system, and / or a manufacturer of the mobile device and / or control device of the load control system 100. The mobile device beacon can also include a received signal strength discovery threshold. The control device can receive the mobile device beacon and can compare the received signal strength indicator (RSSI) at which the mobile device beacon is received with the received signal strength discovery threshold. If the signal strength at which the mobile device beacon is received is greater than or equal to the received signal strength discovery threshold (e.g., the control device is within the discovery range of the mobile device 150), the control device can enter a configuration mode. The control device can transmit a control device beacon when entering the configuration mode.

[0059] The mobile device 150 can discover the control device when receiving a control device beacon transmitted from a control device (e.g., a control source device and / or a control target device). The control device beacon can be a beacon transmitted from a control device and includes a unique identifier that identifies the corresponding control device (e.g., a control source device and / or a control target device). For example, the control device beacon can include a serial number or another unique identifier corresponding to the respective load control device. The unique identifier can be a beacon identifier. The beacon can include an address (e.g., a network address), a peer identifier (e.g., a peer ID), and / or any other kind of device identification data. The control device beacon can also or alternatively include a unique identifier of the device type of the corresponding control device. For example, the control device beacon can include an identifier for a lighting control device, a sensor (e.g., an occupancy sensor, etc.), a remote control device, and / or other types of control devices.

[0060] A control device beacon can be transmitted from a control device in the load control system 100 via the RF communication signal 104. For example, the control device beacon can be transmitted from the lighting control device 114 of the lighting fixture 110, the load controller 121, the controllable light source 132, the occupancy sensor 134, the remote control device 136, and / or another type of control device. Additionally, the control device beacon can be transmitted via the RF signal 102. The RF communication signal 102 and the RF communication signal 104 can be wireless communication signals communicated via a wireless communication protocol (e.g., via a standard protocol, such as Near Field Communication (NFC); and / or via a proprietary protocol, such as Clear ). The RF communication signal 102 and the RF communication signal 104 can be of different signal types (e.g., protocol, bandwidth, etc.). For example, the RF communication signal 104 can be communicated via Bluetooth Low Energy (BLE) or another short-range wireless communication protocol, while the RF communication signal 102 can include a standard protocol (e.g., Thread, Zigbee, or other standard communication protocols) and / or a proprietary protocol (e.g., Clear or other proprietary communication protocols) that can be used for communication between control devices (e.g., control target devices and control source devices). One of the RF communication signals (e.g., the RF communication signal 102) can be used to control an electrical load during operation of the load control system 100, and one of the RF communication signals (e.g., the RF communication signal 104) can be used to discover control devices and commission the load control system 100.

[0061] The RF communication signals 102, 104 can be communicated via a communication circuit (e.g., a transceiver) in the corresponding control device or via a separate beacon transmitting device. The beacon transmitting device for the control device can be included in or near the control device to indicate the relative position of the corresponding control device by transmitting the control device beacon. The RF communication signal 102 can be communicated via the same communication circuit or a different communication circuit as the RF communication signal 104.

[0062] The network device 150 may transmit an optical signal 109 via the optical transmitter 108. The optical transmitter 108 may be, for example, a laser pointer and may be detachable from the network device 150. For example, the optical transmitter may be insertable into a port (e.g., a headphone jack, a USB port, etc.) on the network device 150. The load control device of the lighting fixture (e.g., the load control device 114 of the lighting fixture 110, the load control devices 124a to 124c of the lighting fixtures 120a to 120c, and / or the internal load control device of the controllable light source 132 of the lighting fixture 130) may receive the optical signal 109 from the optical transmitter 108 (e.g., the optical transmitter 108 may be attached to the network device 150 or another device). For example, each lighting load may include one or more internal detectors configured to perform optical feedback on the light emitted from the corresponding lighting load, and the load control device may be configured to receive the optical signal 109 via one or more internal detectors of the corresponding lighting load. Additionally, the load control device of the lighting fixture (e.g., the load control device 114 of the lighting fixture 110) may be configured to receive the optical signal 109 via a corresponding sensor (e.g., the sensor 116). For example, the sensor 116 may be capable of detecting different types of optical signals in the space. The load control device of the lighting fixture may record the baseline ambient light level in the area where the lighting fixture is located. The load control device of the lighting fixture may be capable of detecting the intensity at which the optical signal 109 is received from the network device 150 or another device capable of transmitting the optical signal 109.

[0063] The load control device of the lighting fixture may receive the optical signal 109 from the optical transmitter 108 (e.g., the optical transmitter 108 may be attached to the network device 150 or another device). The load control device of the lighting fixture may determine the signal intensity at which the optical signal 109 is received and may transmit an indication of the signal intensity to the network device 150 (e.g., via the system controller 114 and the load controller 121, respectively). The optical signal 109 may be used as part of the configuration and / or control of the lighting fixture 110, the lighting fixtures 120a to 120c, and / or the lighting fixture 130. The network device 150 may select a lighting fixture for configuration and / or control based on the indication of the signal intensity. For example, the network device 150 may select the lighting fixture 110 for configuration and / or control based on determining that the optical signal 109 is received at the highest signal intensity (e.g., the highest normalized signal intensity) at the internal detector of the lighting load 112 and / or the sensor 116. The internal detector and / or the sensor 116 of the lighting load may be used to record the baseline ambient light level in the areas where the lighting fixture 110 and the lighting fixtures 120a to 120c are located, respectively. The signal intensity may be indicated as a normalized signal intensity (e.g., relative to the corresponding baseline ambient light level).

[0064] The load control system 100 may include one or more beacon transmitting devices, such as beacon transmitting device 180, which may be a location beacon transmitting device. The beacon transmitting device 180 (e.g., the location beacon transmitting device) may be located at the workstation 182. The location beacon transmitting device may communicate a beacon (e.g., a location beacon) via RF communication signals 102 and / or 104. The beacon transmitted by the location beacon transmitting device may include a beacon that conveys a unique identifier. The beacon may be associated with the location where the location beacon transmitting device resides, such as the workstation 182, an office, a meeting room, a part of an office or a meeting room, or another location.

[0065] The beacon transmitted by the location beacon transmitting device may include a unique identifier with which the mobile device 150 and / or the system controller 140 may be associated with the physical location where the location beacon transmitting device resides. If multiple location beacons are detected, the user may associate the unique identifier of the beacon with the strongest signal strength with the nearest physical location. The physical location may also or alternatively be determined based on the geographical location of the mobile device 150.

[0066] The mobile device 150 may detect the beacon transmitted by the location beacon transmitting device for configuring and / or controlling one or more control devices in the load control system. For example, the mobile device 150 may detect the beacon transmitted by the location beacon transmitting device and may associate the unique identifier of the beacon with the unique identifier detected from one or more control device beacons (e.g., beacons transmitted by control devices). When the mobile device detects the location beacon transmitting device, the control devices associated with the unique identifier of the beacon transmitted by the location beacon transmitting device may be jointly controlled.

[0067] Beacons may be transmitted periodically or in response to a trigger event from the control device and / or the location beacon transmitting device. The trigger event may be the receipt of a message. The trigger event may be sent in the message from the mobile device 150 or another device (e.g., the occupancy sensor 134, the remote control device 136, or another control source device). The system controller 140 may automatically control the communication of the beacon by communicating a message based on a periodic trigger event (e.g., the expiration of a timer). In response to the message, the control device and / or the location beacon transmitting device may enter a configuration mode and start transmitting beacons. The message may trigger the transmission of the beacon or the periodic transmission of the beacon within a certain time period.

[0068] The transmission of the beacon can be triggered by a message transmitted on the same or a different RF communication signal and / or protocol and / or channel. For example, the transmission of the beacon can be triggered by an optical signal. For a device capable of performing two-way communication on RF communication signal 104, the mobile device 150 can send a message on RF communication signal 104 to the device, and the message causes the device to convey a beacon on RF communication signal 102. Since the transmission of the beacon can be performed as a one-way communication from the control device, the transmission of the beacon can be triggered by a message transmitted on another communication protocol and / or using another communication signal. For example, the control device can receive a message via RF communication signal 102, and the message triggers the transmission of the beacon from the control device in the load control system on RF communication signal 104.

[0069] The message that triggers the transmission of the beacon can be communicated directly or indirectly via another device to the control device and / or the location beacon transmitting device. For example, the mobile device 150 can send a message to the system controller 140 to trigger the transmission of the beacon from the control device in the load control system. Another message can be sent from the system controller 140 using RF communication signal 102 to trigger the transmission of the beacon from the control device and / or the location beacon transmitting device. The control device configured to receive RF communication signal 102 can start transmitting the beacon using RF communication signal 104.

[0070] The triggering event can be the actuation of a button on the device. The one-way communication device and / or the two-way communication device can transmit a beacon in response to the actuation of a button on the device.

[0071] The device identifier (e.g., device identification data) received from the device in the beacon can be used to determine the device identifier for communicating with the device on another network or network protocol. For example, the mobile device 150 can receive a beacon from the lighting fixture 110 via RF communication signal 102, and the unique identifier in the beacon can correspond to the unique identifier for communicating with the lighting fixture on another network using RF communication signal 104. The unique identifier on each network or network protocol can have a different format, but can include a part of the identifier (e.g., the primary identifier), and this part is used for different purposes on each network to facilitate communication.

[0072] The mobile device 150 can interpret the information received in the beacon and perform debugging and / or control of the load control system 100, or the mobile device 150 can send the information to another device for debugging and / or control. For example, the mobile device 150 can send the information received in the beacon and / or the user input received on the mobile device 150 to the system controller 140 for configuring and / or controlling the load control system 100.

[0073] When debugging the load control system 100, the mobile device 150 and / or the system controller 140 may classify the received beacons into a list. The mobile device 150 and / or the system controller 140 may sort the list based on a ranging method. For example, the mobile device 150 and / or the system controller 140 may sort the list based on the received signal strength indicator (RSSI) of each beacon. The control device that transmits the beacon with the strongest RSSI may be listed first in the list.

[0074] The mobile device 150 may discover the beacons and determine the beacon identifiers. The mobile device 150 and / or the system controller 140 may select the beacon identifiers for configuration and / or control. Each of the discovered beacons may be selected for configuration and / or control, or the beacons discovered above a received signal strength discovery threshold may be selected for configuration and / or control. The received signal strength discovery threshold may define a discovery range (e.g., the area around the mobile device 150 and / or the system controller 140 where control devices can be discovered). The mobile device 150 and / or the system controller 140 may group the control devices identified via the beacons and associate the devices for load control in the load control system 100. The mobile device 150 and / or the system controller 140 may automatically add the identifiers of the selected beacons to a group of control devices to be associated for load control implementation.

[0075] Optical signals (e.g., optical signal 109) may be used to configure and / or control one or more lighting fixtures. The lighting fixtures (e.g., lighting fixture 110, lighting fixtures 120a to 120c, and / or lighting fixture 130) may receive the optical signal 109 from an optical transmitter 108 (e.g., the optical transmitter 108 may be attached to the network device 150 or another device). For example, the lighting fixture may be configured to receive the optical signal via an internal detector and / or a corresponding sensor (e.g., sensor 116) of the lighting load of the lighting fixture. The lighting fixture may provide feedback to indicate that the lighting fixture has received the optical signal 109. For example, the lighting fixture may cause the corresponding lighting load to illuminate in a first color. The lighting fixture may measure the corresponding signal strength at which the optical signal 109 is received and may transmit a corresponding indication of the signal strength (e.g., as part of a beacon). For example, the signal strength may be indicated as a normalized signal strength (e.g., relative to a corresponding baseline ambient light level).

[0076] The network device 150 (e.g., or the system controller 140) may select one or more of the lighting fixtures for configuration and / or control based on an indication of signal strength. For example, the network device 150 may select the lighting fixture that receives the optical signal 109 at the highest signal strength for configuration and / or control. The selected lighting fixture may provide feedback to indicate that the lighting fixture has been selected for configuration and / or control. For example, the lighting fixture may cause the corresponding lighting load to illuminate in a second color. Once the configuration and / or control of the selected lighting fixture has been completed, the network device 150 may select another lighting fixture (e.g., which receives the optical signal 109 at the second highest signal strength) for configuration and / or control. The lighting fixture for which the configuration and / or control has been completed may provide feedback to indicate that the lighting fixture has been configured and / or controlled. For example, the lighting fixture may cause the corresponding lighting load to illuminate in a third color.

[0077] The control settings for a group of control devices may be configured at the mobile device 150 and / or the system controller 140 based on input received from the user via the user interface 152 of the mobile device 150. The mobile device 150 may display a lighting control configuration 190 on the user interface 152. For example, the lighting control configuration 190 may include preset configurations 192, zone configurations 194, occupancy configurations 196, and / or scheduling configurations 198 that may be configured for a group of control devices. The mobile device 150 may display a dimmer 199 on the user interface 152. For example, the dimmer 199 may be used to control one or more lighting fixtures in real time and / or set the lighting level for one or more of the preset configurations 192, zone configurations 194, occupancy configurations 196, and / or scheduling configurations 198. For example, the dimmer may be used to lower the lighting level of one or more lighting fixtures at a certain time of day.

[0078] The preset configuration 192 may be configured by adjusting the brightness level of one or more lighting fixtures using a virtual slider 199 (e.g., a virtual dimmer) and storing the settings. The user may select the preset configuration 192 on the user interface 152 to set the brightness level of one or more lighting fixtures to be controlled according to the preset. Different presets may be configured to set the lighting fixtures to different lighting levels for different occasions, such as a bedtime preset for when the user goes to bed, a movie preset for when the user watches TV or a movie, a leave preset for when the user leaves the building, a home preset for when the user is in the building, or any other preset that the user may define for a certain occasion.

[0079] A user may select a zone configuration 194 on the user interface 152 to define one or more zones of lighting fixtures for control. Each of the control devices found and added to a group as described herein may be included within a zone such that a group identifier (e.g., a temporary group identifier) is also a zone identifier, or a zone identifier may indicate a subset of devices that have been found and added to a group of devices for configuration and / or control. Different zones may be controlled individually by sending lighting control instructions to a zone to set the zone to a different lighting level. The associated device identifiers of the identified lighting fixtures in a zone may be stored at the mobile device 150 and / or the system controller 140 as a defined zone configuration 194 for controlling the lighting fixtures in the defined zone. The zone configuration 194 may be sent in a message to the system controller 140 and / or the lighting fixtures in the defined zone for storage to control the lighting fixtures according to the zone configuration 194.

[0080] A user may select an occupancy configuration 196 on the user interface 152 to define one or more lighting fixtures for control based on occupancy or vacancy of a space. Different lighting fixtures may be controlled to different lighting levels in response to occupancy commands and / or vacancy commands received from an occupancy sensor such as occupancy sensor 134.

[0081] A user may select a scheduling configuration 198 on the user interface 152 to define a schedule for one or more lighting fixtures. Different lighting fixtures may be controlled to different lighting levels (e.g., on / off, pre-defined brightness levels, etc.) according to a schedule that may be monitored by the system controller 140.

[0082] Figure 2A Illustrate a representative load control environment 202 in which a load control system 200 (e.g., Figure 1 the load control system 100 shown) may be implemented for configuring and / or controlling one or more control devices using beacons and / or optical signals. The load control system 200 may include a plurality of lighting fixtures 210a - 210d (e.g., lighting fixture 110 and / or lighting fixture 130). Each of the lighting fixtures 210a - 210d may include one or more lighting loads (e.g., lighting load 112), and a lighting control device (e.g., lighting control device 114) for controlling the brightness and / or color of the lighting load of the corresponding lighting fixture. Each of the lighting fixtures 210a - 210d may also include a controllable light source, such as Figure 1The controllable light source 132 shown. The lighting control devices of the lighting fixtures 210a to 210d can operate as controlled target devices for controlling the corresponding lighting loads in response to messages received from the control source devices. The control source devices of the load control system 200 can include an occupancy sensor 234 (e.g., occupancy sensor 134), a remote control device 236 (e.g., remote control device 136), and sensors 216a to 216d (e.g., sensors 116) installed in the corresponding lighting fixtures 210a to 210d. The sensors 216a to 216d can be occupancy sensors, visible light sensors (e.g., cameras), daylight sensors, optical sensors, and / or any other type of sensors. For example, one or more of the occupancy sensor 234 and / or the sensors 216a to 216d can be visible light sensors (e.g., cameras). The load control system 100 can also include a system controller 240 (e.g., system controller 140) and a network device (such as a mobile device 250 (e.g., mobile device 150)), which can also operate as control source devices. For example, the mobile device 250 can include a smart phone and / or a tablet computer.

[0083] As Figure 2A shown, a control device (e.g., the lighting control device of the lighting fixture 210a) can be selected for configuration and / or control, and can provide feedback to the user 205 (e.g., installer) to identify the device that has been selected for configuration and / or control. The control device can be solicited and / or associated with a configuration identifier of the configuration data (e.g., a regional or group identifier for joining a network) for implementing load control in the load control environment 201. The configuration identifier can be a luminaire, group, region, area, and / or location defined by configuration data (e.g., lighting control configuration information) generated by design software. For example, the feedback can be provided by the control device to indicate that the control device is ready to be solicited, has been selected for solicitation, and / or has been solicited. The control device can be solicited by selecting a configuration identifier to be associated with the control device. The control device being solicited can transmit a unique identifier (e.g., a serial number) to the mobile device 250. The control device can be associated with the configuration identifier by creating an association between the configuration identifier and the unique identifier of the control device. The mobile device can store the unique identifier and information about the association between the configuration identifier and the control device in the configuration data. After soliciting the control device, it can be joined to the network and / or can be configured and / or controlled by the user 205. For example, the user 205 can send one or more commands to the control device via the mobile device.

[0084] During the process of claiming a control device and / or associating a control device with a configuration identifier of configuration data, the control device may be configured to communicate with the mobile device 250 via a first wireless communication medium (e.g., using Bluetooth technology via the RF communication signal 204). During normal operation of the load control system 200, the control devices may be configured to communicate with each other via a second wireless communication medium (e.g., via RF communication signals 202 transmitted on a wireless communication network such as or Zigbee network). After being claimed, the control device may be configured to attach to the wireless communication network. For example, the control device may be attached to the wireless communication network by transmitting the association between the control device and the configuration identifier to a remote device. After the control device is attached to the wireless communication network, the control devices may communicate with each other via the wireless communication network during normal operation.

[0085] The configuration data may define the operation and / or functionality of the load control system 200. The configuration data may include representations of control devices (e.g., lighting fixtures 210a to 210d, occupancy sensors 234, remote control devices 236, sensors 216a to 216d, etc.) in the load control system 200, as well as configuration identifiers of the control devices (e.g., luminaires, groups, areas, zones, and / or locations). For example, the configuration data may define the functionality of the control devices, e.g., how the lighting fixtures 210a to 210d respond to the occupancy sensors 234 and / or remote control devices 236. The configuration data may be configured using design software executed by a processing device (e.g., processing device 160) prior to claiming the control device and / or associating the control device with the corresponding configuration identifier of the control device in the configuration data. Additionally, the configuration data may be configured, for example, by the mobile device 250 when the mobile device is claiming the control device and / or associating the control device with the configuration identifier of the control device in the configuration data. After the control device has attached to the wireless communication network, the configuration data may be transmitted to the control device via the wireless communication network.

[0086] The mobile device 250 may be configured to claim control devices (e.g., lighting control devices for lighting fixtures 210a to 210d, occupancy sensors 234, and / or remote control devices 236) and / or associate the control devices with the configuration identifiers of the control devices in the configuration data. Sensors 234a to 234d may be used to claim and / or associate control devices for configuration and / or control. The user 205 may cause the mobile device 250 to enter a configuration mode (e.g., a claim mode and / or an association mode). For example, the user 205 may press a button on the mobile device 250 to cause the mobile device to enter the configuration mode. In the configuration mode, the mobile device 250 may discover the beacons of the control devices in the load control environment 201. As described herein, a control device may be claimed by associating the unique identifier of the control device with a configuration identifier.

[0087] After entering the configuration mode, the mobile device 250 may transmit (e.g., periodically transmit) a beacon (e.g., a mobile device beacon). The mobile device 250 may transmit the mobile device beacon via the first wireless communication medium 204 (e.g., using low power (BLE) technology via a short-range wireless communication link). The mobile device beacon may include, for example, a beacon identifier. For example, the beacon identifier may be a unique identifier that identifies the mobile device 250 (e.g., or an application executed on the mobile device 250), and / or a non-unique identifier, such as an identifier of a group, area, building, load control system, and / or the manufacturer of the mobile device and / or control device of the load control system 200. The mobile device beacon may also include a received signal strength discovery threshold. The control device may receive the mobile device beacon and may compare the received signal strength indicator (RSSI) of the received mobile device beacon with the received signal strength discovery threshold. For example, the received signal strength indicator may be the signal strength at which the mobile device beacon is received. When the beacon identifier of the mobile device matches a specific beacon identifier and / or the received signal strength indicator is greater than or equal to the received signal strength discovery threshold (e.g., the control device is within the discovery range of the mobile device 250), each of the control devices may enter the configuration mode. For example, the specific beacon identifier may be predetermined and / or stored in the memory of the control device. The mobile device 250 may adjust the received signal strength discovery threshold included in the mobile device beacon to adjust the discovery range of the mobile device.

[0088] After entering the configuration mode, each control device (e.g., the lighting control device of lighting fixtures 210a to 210d) may transmit (e.g., transmit periodically) a control device beacon. The control device may transmit the control device beacon via the first wireless communication medium 204 (e.g., using BLE technology). Each control device beacon may include a unique identifier of the control device that transmits the corresponding beacon. Additionally, after entering the configuration mode, the control device may become ready to be solicited by the mobile device 250. After entering the configuration mode (e.g., in response to receiving a mobile device beacon), the control device (e.g., lighting fixtures 210a to 210d) may provide feedback to the user 205 to indicate that the control device is ready to be solicited. The feedback may be provided by changing the state of the lighting load in lighting fixture 210a. For example, lighting fixture 210a may turn into a first color (e.g., orange) after entering the configuration mode (e.g., in response to receiving a mobile device beacon) to indicate to the user that the control device is within the discovery range of the mobile device 250 and ready to be solicited. Additionally, the feedback may be provided by causing the lighting load to flash on and off; increasing and / or decreasing the brightness level of the lighting load; increasing and / or decreasing the color temperature of the lighting load; and / or providing other visual feedback to the user 205. The type of feedback may be indicated in the mobile device beacon transmitted by the mobile device 250 and / or may be pre-programmed and stored at the control device (e.g., lighting fixtures 210a to 210d).

[0089] As the user 205 moves the mobile device 250 back and forth around the load control environment 201, the control devices within the discovery range of the mobile device may change. When the control devices (e.g., the lighting control devices of lighting fixtures 210a to 210d) start receiving the mobile device beacon as the user moves back and forth, those control devices may enter the configuration mode (e.g., become ready to be solicited), start transmitting their control device beacons, and provide feedback (e.g., turn into a first color). Additionally, when the control devices fall out of the discovery range of the mobile device 250 and / or out of the wireless range of the mobile device 250 (e.g., stop receiving the mobile device beacon) as the user moves back and forth, those control devices may exit the configuration mode after a timeout period (e.g., one minute). Accordingly, those control devices may stop transmitting their control device beacons and stop providing feedback (e.g., turn off).

[0090] The mobile device 250 may receive control device beacons from one or more of the control devices. For example, the mobile device 250 may receive a control device beacon from the lighting control device of the lighting fixture 210a and select the lighting control device for solicitation (e.g., for joining the network). The mobile device 250 may rank the received control device beacons based on the received signal strength indicator of the respective control device beacons. For example, if the received signal strength indicator of the control device beacon from the lighting control device of the lighting fixture 210a is the maximum received signal strength indicator of the received control device beacons, the mobile device 250 may select the lighting control device for solicitation.

[0091] The mobile device 250 may send a connection message to the control device having the received control device beacon with the maximum received signal strength. For example, the mobile device 250 and the control device may be configured to establish a connection (e.g., a two-way communication connection) in response to the control device receiving the connection message from the mobile device 250. Additionally, the connection message may indicate to the control device that the control device has been discovered and selected for solicitation. For example, the connection message may be sent via the RF communication signal 204 (e.g., directly from the mobile device 250). For example, the mobile device 250 may connect to a single control device at a certain time (e.g., to select a single control device for solicitation at a certain time).

[0092] In response to receiving the connection message, the control device (e.g., the lighting fixture 210a) may provide feedback to the user 205 to indicate that the lighting fixture 210a has been selected for solicitation. The feedback may be provided by changing the state of the lighting load in the lighting fixture 210a. For example, the lighting fixture 210a may turn into a second color (e.g., blue) after entering the configuration mode (e.g., in response to receiving the mobile device beacon) to indicate to the user that the control device has been selected for solicitation. As Figure 2A shown, the lighting fixture 210a may light up in the second color, while the other lighting fixtures 210b to 210d may light up in the first color. Additionally, the feedback may be provided by causing the lighting load to flash on and off; increasing and / or decreasing the brightness level of the lighting load; increasing and / or decreasing the color temperature of the lighting load; and / or providing other visual feedback to the user 205. The type of feedback may be indicated in the connection message from the mobile device 250 and / or may be pre-programmed and stored at the control device (e.g., the lighting fixtures 210a to 210d).

[0093] As user 205 moves the mobile device 250 around the load control environment 102 back and forth, the received signal strength indicator of the received control device beacon received by the mobile device may change. Accordingly, the control device beacon having the maximum received signal strength indicator of the received control device beacon provides feedback (e.g., by changing to a second color). The mobile device 250 may be configured to disconnect from the previous control device (e.g., by sending a message to the previous control device), and the previous control device may stop providing feedback (e.g., changing from the second color to the first color since the control device may still be within the discovery range of the mobile device). Additionally, the mobile device 250 may transmit a connection message to the new control device having the received control device beacon with the maximum received signal strength. Accordingly, the control device may be selected for claiming and may start providing feedback (e.g., changing to the second color).

[0094] After entering the configuration mode, the mobile device 250 may transmit (e.g., periodically transmit) an optical signal (e.g., optical signal 109). The mobile device 250 may transmit the optical signal via an attached optical transmitter (not shown). The control device may receive the optical signal via an internal detector and / or sensor (e.g., sensors 216a to 216d) of the lighting load of the lighting fixtures 210a to 210b, and may measure the signal strength of the received optical signal. Each of the control devices may enter the configuration mode when the control device receives the optical signal, or the control device may enter the configuration mode before receiving the optical signal.

[0095] After entering the configuration mode, the control device (e.g., lighting fixtures 210a to 210d) may provide feedback to the user 205 to indicate that the control device is ready to be claimed. The feedback may be provided by changing the state of the lighting load in the lighting fixture 210a. For example, the lighting fixture 210a may change to a first color (e.g., orange) after entering the configuration mode (e.g., in response to receiving the optical signal) to indicate to the user that the control device has received the optical signal and is ready to be claimed. Additionally, the feedback may be provided by causing the lighting load to blink on and off; increasing and / or decreasing the brightness level of the lighting load; increasing and / or decreasing the color temperature of the lighting load; and / or providing other visual feedback to the user 205. The feedback type may be pre-programmed and stored at the control device (e.g., lighting fixtures 210a to 210d).

[0096] After entering the configuration mode, each control device (e.g., the lighting control devices of lighting fixtures 210a to 210d) may transmit an indication of the signal strength at which one or more of the received optical signals are located (e.g., transmit periodically). The control device may transmit the indication via the first wireless communication medium 204 (e.g., using BLE technology). Each indication may include a unique identifier of the control device that transmits the optical signal. Additionally, after entering the configuration mode, the control device may become ready to be solicited by the mobile device 250.

[0097] As the user 205 moves the mobile device 250 back and forth around the load control environment 201, the control devices that receive the optical signal may change. One or more control devices that are not receiving the optical signal may be in the configuration mode. When the control devices in the configuration mode (e.g., the lighting control devices of lighting fixtures 210a to 210d) start receiving the optical signal as the user moves back and forth, those control devices may start transmitting their signal strength indications and provide feedback (e.g., change to a first color). Additionally, when the control devices stop receiving the optical signal as the user moves back and forth, those control devices may stop transmitting their signal strength indications and stop providing feedback (e.g., turn off) after a timeout period (e.g., one minute).

[0098] The mobile device 250 may receive signal strength indications from one or more of the control devices. For example, the mobile device 250 may receive a signal strength indication from the lighting control device of the lighting fixture 210a and select the lighting control device for solicitation (e.g., for joining the network). The mobile device 250 (e.g., and / or the system controller 240) may select a lighting control device for solicitation based on the signal strength indication. For example, if the lighting fixture 210a receives the optical signal at the highest signal strength, the mobile device 250 may select the lighting control device of the lighting fixture 210a for solicitation.

[0099] The mobile device 250 may send a connection message to the selected control device. For example, the mobile device 250 and the control device may be configured to establish a connection (e.g., a two-way communication connection) in response to the control device receiving the connection message from the mobile device 250. Additionally, the connection message may indicate to the control device that the control device has been discovered and selected for solicitation. For example, the connection message may be sent via the RF communication signal 204 (e.g., directly from the mobile device 250). For example, the mobile device 250 may connect to a single control device at a certain time (e.g., to select a single control device for solicitation at a certain time).

[0100] In response to receiving a connection message, a control device (e.g., lighting fixture 210a) may provide feedback to user 205 to indicate that lighting fixture 210a has been selected for claiming. The feedback may be provided by changing the state of the lighting load in lighting fixture 210a. For example, lighting fixture 210a may change to a second color (e.g., blue) after entering a configuration mode (e.g., in response to receiving a connection message) to indicate to the user that the control device has been selected for claiming. As Figure 2A shown, lighting fixture 210a may illuminate with the second color while other lighting fixtures 210b to 210d may illuminate with the first color. Additionally, feedback may be provided by causing the lighting load to flash on and off; increasing and / or decreasing the brightness level of the lighting load; increasing and / or decreasing the color temperature of the lighting load; and / or providing other visual feedback to user 205. The type of feedback may be indicated in the connection message from mobile device 250 and / or may be pre-programmed and stored at the control device (e.g., lighting fixtures 210a to 210d). A lighting fixture for which configuration and / or control has been completed may provide feedback to indicate that the lighting fixture has been configured and / or controlled. For example, the lighting fixture may cause the corresponding lighting load to illuminate with a third color.

[0101] When the desired control device (e.g., the lighting control device of lighting fixture 210a) is selected for claiming (e.g., mobile device 250 is connected to the lighting control device and the lighting fixture is the second color), user 205 may actuate a button on mobile device 250 (e.g., a soft button or virtual button displayed on user interface 252 of mobile device 250) to claim (e.g., and / or associate) the selected lighting control device. For example, user 205 may select a zone or group (e.g., displayed on mobile device 250) to associate with the selected lighting control device to claim the lighting control device. Thus, claiming and associating may occur simultaneously. Mobile device 250 may transmit a claim message to the selected lighting control device in response to selecting a zone or group on the mobile device to indicate that the control device has been claimed and / or associated. Additionally, the selected lighting control device may transmit an acknowledgement message (e.g., a claim acknowledgement message) to mobile device 250 in response to receiving the claim message. The claim acknowledgement message may include a unique identifier (e.g., a serial number) of the selected lighting control device.

[0102] In response to being solicited (e.g., in response to receiving a solicitation message), the control device (e.g., lighting fixture 210a) may provide feedback to the user 205 to indicate that the lighting fixture 210a has been solicited (e.g., for network engagement). The feedback may be provided by changing the state of the lighting load in the lighting fixture 210a. For example, after being solicited, the lighting fixture 210a may transition to a third color (e.g., green). Additionally, feedback may be provided by causing the lighting load to blink on and off; increasing and / or decreasing the brightness level of the lighting load; increasing and / or decreasing the color temperature of the lighting load; and / or providing other visual feedback to the user 205. The type of feedback may be indicated in the solicitation message from the mobile device 250 or may be pre-programmed and stored at the control device (e.g., lighting fixtures 210a to 210d).

[0103] In response to being solicited, the control device may exit the configuration mode and enter the engagement mode. In the engagement mode, the control device may stop continuously transmitting (e.g., periodically transmitting) control device beacons on the first wireless communication medium 204. For example, the control device may periodically switch between the first wireless communication medium 204 (e.g., using BLE technology) and the second wireless communication medium 204 (e.g., a wireless communication network). The control device may listen to the wireless communication network 202 to determine whether to transmit a request to engage the wireless communication network on the wireless communication network. In the case where the mobile device 250 needs to reconnect to the control device while the mobile device is in the configuration mode, the control device may continue to periodically transmit control device beacons via the first wireless communication medium (e.g., at a lower rate than in the configuration mode). After the control device has engaged the wireless communication network 202, configuration data may be transmitted to the control device via the wireless communication network.

[0104] Figure 2B Illustrate another example for configuring and / or controlling a control device in a representative load control environment 201 (e.g., Figure 1 the load control system 100 shown). Figure 2BThe illustrated example can implement the configuration and / or control of one or more control devices (e.g., using beacons). The load control system 200 can include a plurality of lighting fixtures 220a to 220d (e.g., lighting fixtures 120a to 120c) that can be controlled by a load controller 221 (e.g., load controller 121). Each of the lighting fixtures 220a to 220d can include one or more lighting loads (e.g., lighting loads 122a to 122c), and lighting control devices (e.g., lighting control devices 124a to 124c) for controlling the brightness and / or color of the lighting loads of the corresponding lighting fixtures. The load controller 221 can be coupled to the lighting control devices in the lighting fixtures 220a to 220d via a communication link 225 (e.g., a wired digital communication link). The load controller 221 can be configured to control the lighting fixtures 220a to 220d individually. The load controller 221 can operate as a controlled target device to control the lighting fixtures 220a to 220d in response to a message received from a control source device.

[0105] The load controller 221 can be connected to a sensor 226 (e.g., sensor 126). The sensor 226 can be used to control the lighting fixtures 220a to 220d. The sensor 226 can be an occupancy sensor capable of detecting occupancy / vacancy conditions (e.g., using infrared signals). The sensor 226 can be a sensor capable of detecting changes in the visible space of the sensor 226 (e.g., a camera). The sensor 226 can be an occupancy sensor, a visible light sensor (e.g., a camera), a daylight sensor, an optical sensor, and / or any other type of sensor. The sensor 226 can communicate directly with the load controller 221.

[0106] For example, the load control devices of the lighting fixtures 220a to 220d may be capable of detecting different types of optical signals in the space. For example, each of the lighting loads of the lighting fixtures 220a to 220d can include one or more internal detectors configured to perform optical feedback on the light emitted from the corresponding lighting load, and the load control device can be configured to receive an optical signal 109 via the one or more internal detectors of the corresponding lighting load. The load control devices of the lighting fixtures 220a to 220d can each record the baseline ambient light level in the area where the lighting fixture is located. The load control devices of the lighting fixtures 220a to 220d can each be capable of detecting the intensity at which one or more of the received optical signals are received. For example, the load control devices of the lighting fixtures 220a to 220d may be capable of detecting the intensity at which an optical signal is received from a network device 250 or another device capable of emitting an optical signal. The network device 250 can emit an optical signal via an optical transmitter 209. Additionally, the optical transmitter 209 can be, for example, a laser pointer and can be detachable from the network device 250.

[0107] The load controller 221 can be discovered and / or selected for the configuration and / or control of a set of lighting fixtures 220a to 220d. For example, the lighting fixtures 220a to 220d may not be able to communicate directly with the mobile device 250. The lighting fixtures 220a to 220d can communicate with the load controller 221 via, for example, wired communication and / or direct communication. The lighting fixtures 220a to 220d can have sub-addresses that can be used by the lighting fixture 221 to communicate directly with the lighting fixtures 220a to 220d to generate a preset or other lighting configuration in response to a command on the network. The load controller 221 can provide the sub-addresses of the lighting fixtures 220a to 220d to the mobile device 250 for the implementation of the configuration of individual lighting fixtures. A preset or other lighting configuration can be uploaded to the load controller 221 for individual control. The load controller 221 can be solicited and / or joined to the network such that the load controller 221 receives communications on the network for controlling the lighting fixtures 220a to 220d.

[0108] The control devices (e.g., lighting fixtures 210a to 210d) can enter a configuration mode. For example, the control devices can enter the configuration mode after receiving a configuration mode message (e.g., a mobile device beacon) from the mobile device 250. The load controller 221 can receive the configuration mode message from the mobile device 250 via the communication link 225 and can cause the control devices to enter the configuration mode. After entering the configuration mode, the control devices (e.g., lighting fixtures 210a to 210d) can provide feedback to the user 205 to indicate that the control devices are ready to be solicited. The feedback can be provided by changing the state of the lighting load in the lighting fixture 210a. For example, the lighting fixture 210a can turn into a first color (e.g., orange) after entering the configuration mode (e.g., in response to receiving an optical signal) to indicate to the user that the control device is ready to be solicited. Additionally, the feedback can be provided by causing the lighting load to blink on and off; increasing and / or decreasing the brightness level of the lighting load; increasing and / or decreasing the color temperature of the lighting load; and / or providing other visual feedback to the user 205. The feedback type can be pre-programmed and stored at the control devices (e.g., lighting fixtures 210a to 210d).

[0109] One or more of the control devices can start transmitting (e.g., transmitting periodically) corresponding control device beacons after entering the configuration mode. For example, a control device that receives an optical signal can transmit a control device beacon. Alternatively, the control device can start transmitting a control device beacon after receiving a mobile device beacon from the mobile device 250. Each control device beacon can include, for example, an identifier of the control device that transmits the control device beacon.

[0110] As user 205 moves the mobile device 250 back and forth around the load control environment 201, the control devices that receive the optical signal and / or the mobile device beacon may change. When the control devices (e.g., the lighting control devices of lighting fixtures 210a to 210d) start receiving the optical signal and / or the mobile device beacon as the user moves back and forth, those control devices may start transmitting their control device beacons and provide feedback (e.g., change to a first color). Additionally, when the control devices stop receiving the optical signal and / or the mobile device as the user moves back and forth, those control devices may stop transmitting their control device beacons to the load controller 221 and stop providing feedback (e.g., turn off) after a timeout period (e.g., one minute).

[0111] The mobile device 250 may receive the control device beacon and may select a lighting fixture for solicitation. For example, the mobile device 250 may select lighting fixture 210a for solicitation (e.g., for engaging the network). The mobile device 250 (e.g., and / or the system controller 240) may select a lighting control device for solicitation based on the signal strength (e.g., RSSI) of the control device beacon. For example, if the control device beacon sent by lighting fixture 210a is received at the highest RSSI at the mobile device 250, the mobile device 250 may select the lighting control device of lighting fixture 210a for solicitation.

[0112] The mobile device 250 may send a selection message to the selected lighting fixture via the load controller 221. The selection message may indicate to the load controller 221 and / or the selected lighting fixture that the lighting fixture is selected for configuration and / or control. The load controller 221 may forward the selection message to the selected lighting control device, or the load controller 221 may send a separate selection message to the selected lighting fixture.

[0113] In response to receiving the selection message, the control device (e.g., lighting fixture 210a) may provide feedback to user 205 to indicate that lighting fixture 210a has been selected for solicitation. The feedback may be provided by changing the state of the lighting load in lighting fixture 210a. For example, lighting fixture 210a may change to a second color (e.g., blue) in response to receiving the selection message to indicate to the user that the control device has been selected for solicitation. As Figure 2BAs shown, the lighting fixture 210a can emit a second color, while the other lighting fixtures 210b to 210d can emit a first color. Additionally, feedback can be provided by causing the lighting load to flash on and off; increasing and / or decreasing the brightness level of the lighting load; increasing and / or decreasing the color temperature of the lighting load; and / or providing other visual feedback to the user 205. The type of feedback can be indicated in a selection message from the mobile device 250 and / or can be pre-programmed and stored at the control device (e.g., the lighting fixtures 210a to 210d). The lighting fixtures for which configuration and / or control has been completed can provide feedback to indicate that the lighting fixtures have been configured and / or controlled. For example, the lighting fixture can cause the corresponding lighting load to be illuminated in a third color.

[0114] When a desired control device (e.g., the lighting control device of the lighting fixture 210a) is selected for solicitation (e.g., the mobile device 250 is connected to the lighting control device and the lighting fixture is of the second color), the user 205 can actuate a button on the mobile device 250 (e.g., a soft button or virtual button displayed on the user interface 252 of the mobile device 250) to solicit (e.g., and / or associate) the selected lighting control device. For example, the user 205 can select a region or group (e.g., displayed on the mobile device 250) to be associated with the selected lighting control device to solicit the lighting control device. Thus, solicitation and association can occur simultaneously. The mobile device 250 can transmit a configuration message (e.g., a solicitation message) to the selected lighting control device via the load controller 221 in response to selecting a region or group on the mobile device, to indicate that the control device has been solicited and / or associated. For example, the mobile device 250 can transmit the configuration message to the load controller 221 via wireless communication, and the load controller 221 can forward the configuration message to the selected control device via the communication link 225. The configuration message can include, for example, the configuration identifier of the control device. Additionally, the selected lighting control device can transmit an acknowledgment message (e.g., a solicitation acknowledgment message) to the mobile device 250 via the load controller 221 in response to receiving the configuration message.

[0115] In response to being solicited (e.g., in response to receiving a configuration message), a control device (e.g., lighting fixture 210a) may provide feedback to user 205 to indicate that the lighting fixture 210a has been solicited (e.g., for network engagement). The feedback may be provided by changing the state of the lighting load in the lighting fixture 210a. For example, after being solicited, the lighting fixture 210a may transition to a third color (e.g., green). Additionally, feedback may be provided by causing the lighting load to blink on and off; increasing and / or decreasing the brightness level of the lighting load; increasing and / or decreasing the color temperature of the lighting load; and / or providing other visual feedback to user 205. The type of feedback may be indicated in a solicitation message from the mobile device 250 or may be pre-programmed and stored at the control device (e.g., lighting fixtures 210a to 210d).

[0116] In response to being solicited, the control device may exit the configuration mode and enter the engagement mode. In the engagement mode, the control device may stop continuously transmitting (e.g., periodically transmitting) control device beacons on the first wireless communication medium 204. For example, the control device may periodically switch between the first wireless communication medium 204 (e.g., using BLE technology) and the second wireless communication medium 204 (e.g., a wireless communication network). The control device may listen to the wireless communication network 202 to determine whether to transmit a request to engage the wireless communication network on the wireless communication network. In the case where the mobile device 250 needs to reconnect to the control device when the mobile device is in the configuration mode, the control device may continue to periodically transmit control device beacons via the first wireless communication medium (e.g., at a lower rate than in the configuration mode). After the control device has engaged the wireless communication network 202, configuration data may be transmitted to the control device via the wireless communication network.

[0117] Figure 2C Illustrate another example for configuring and / or controlling a control device using beacons and / or optical signals in a representative load control environment 201. As Figure 2BAs shown, a control device (e.g., the lighting control device of lighting fixture 210a) can be selected for configuration and / or control, and feedback can be provided to user 205 to identify the device that has been selected for configuration and / or control. For example, the control device can provide feedback to indicate that the control device has been selected for solicitation and / or associated with other control devices for load control in load control environment 201. Mobile device 250 can be configured to solicit control devices (e.g., the lighting control devices of lighting fixtures 210a to 210d, occupancy sensor 234, remote control device 236, and / or sensors 216a to 216d) and / or associate the control devices with the configuration identifiers of the configuration data of load control system 200. User 205 can cause mobile device 250 and / or system controller 240 to enter a configuration mode (e.g., solicitation mode and / or association mode). For example, user 205 can press a button on mobile device 250 to add and / or edit a set of control devices in load control environment 201 (e.g., a room or other part of a building). In the configuration mode, mobile device 250 can discover messages (e.g., control device beacons) transmitted by control devices in load control environment 201. The messages can be communicated periodically or in response to messages communicated from mobile device 250 via RF communication signals 202, 204 (e.g., directly or via system controller 240) and / or via optical signals.

[0118] The lighting control devices of lighting fixtures 210a to 210d can each transmit a control device beacon including their unique identifiers. Mobile device 250 can receive the control device beacon from the lighting control device of lighting fixture 210a and select lighting fixture 210a for configuration and / or control (e.g., based on the signal strength of their beacon identifiers). Each of the discovered control devices can be selected for configuration and / or control, or a control device that transmits a beacon discovered above a received signal strength discovery threshold can be selected for configuration and / or control (e.g., for solicitation and / or association with the configuration identifier of the configuration information of load control system 200). The control device beacon can also include the signal strength of one or more optical signals received by the lighting control devices of lighting fixtures 210a to 210d, and a control device that receives an optical signal with a received signal strength above the signal strength discovery threshold can be selected for configuration and / or control (e.g., for solicitation and / or association with the configuration identifier of the configuration information of load control system 200). Mobile device 250 can automatically add the selected unique identifier to a set (e.g., a temporary set) of control devices for performing configuration and / or control.

[0119] The mobile device 250 may send a confirmation message to the lighting control device of the lighting fixture 210a, the confirmation message indicating that the lighting control device has been discovered and selected for configuration and / or control. The confirmation message may be sent via the RF communication signals 202, 204 (e.g., directly from the mobile device 250 and / or via the system controller 240).

[0120] The confirmation message may include a temporary group identifier, which may be stored at the lighting fixture 210a for identifying subsequent messages including configuration information and / or control information. The temporary group identifier may be used to communicate to the control device for debugging or configuration when the mobile device 250 is in the configuration mode during the commissioning or configuration (e.g., solicitation, diagnosis, association, etc.) and / or control of the load control system. After the commissioning or other configuration of the load control system, the temporary group identifier may be removed from the control device or otherwise not used. In another example, during the operation of the load control system, the temporary group identifier may be used as the group identifier for multiple groups of control devices (e.g., area or other group control devices).

[0121] In response to the confirmation message, the lighting fixture 210a may provide feedback to the user 205 to indicate that the lighting fixture 210a has been selected for configuration and / or control. The feedback may be provided by changing the state of the lighting load in the lighting fixture 210a. For example, the feedback may be provided by causing the lighting load to flash on and off; increasing and / or decreasing the brightness level of the lighting load; increasing and / or decreasing the color (e.g., color temperature) of the lighting load; and / or providing other visual feedback to the user 205. The type of feedback may be indicated in the confirmation message from the mobile device 250 or may be pre-programmed and stored at the lighting fixtures 210a to 210d.

[0122] As the user 205 moves the mobile device 250 back and forth around the load control environment 201, the mobile device 250 may discover the control device beacons of additional lighting fixtures 210b to 210d and automatically select the unique identifiers in the beacons for configuration and / or control in the load control environment 210. Each of the selected lighting fixtures 210b to 210d may receive the confirmation message from the mobile device 250 and provide similar feedback to the user 205 to indicate that the lighting fixture has been selected for configuration and / or control.

[0123] When selecting lighting fixtures 210b to 210d, the lighting fixtures can be automatically added to a set of control devices (e.g., ad-hoc group, zone, or other group control devices) for collective configuration and / or control. As user 205 moves around load control environment 201 with mobile device 250, the received signal strength indicator of the received control device beacons (e.g., the signal strength at which different control device beacons are received at mobile device 250) can vary. After a control device has been selected for configuration and / or control, the control devices can remain selected and can provide feedback indicating that the control devices have been selected until they are deselected or the configuration (e.g., commissioning, diagnostics, association, etc.) and / or control (e.g., configuration procedure) of the devices has been completed. For example, lighting fixture 210a can continue to provide feedback indicating that lighting fixture 210a has been selected for configuration and / or control until lighting fixture 210a receives a message indicating that lighting fixture 210a has been deselected or a message indicating that the configuration procedure for configuring the load control system has been completed. The message can be sent from mobile device 250 or system controller 240. For example, mobile device 250 can transmit a message to deselect a control device in response to a user selection on mobile device 250 to deselect the control device. Mobile device 250 can also or alternatively transmit a message to deselect a control device in response to the received signal strength indicator of a control device beacon dropping below a received signal strength discovery threshold (e.g., when the control device beacon is not detected or drops below another threshold for a certain period of time).

[0124] Control devices that transmit beacons having a received signal strength indicator (e.g., RSSI) that meets or exceeds a received signal strength discovery threshold can be selected for configuration and / or control. Mobile device 250 can filter out the unique identifiers of control device beacons having a received signal strength indicator below the received signal strength discovery threshold. The received signal strength discovery threshold can be pre-defined and / or dynamically set at mobile device 250. For example, the received signal strength discovery threshold can be received from another device and stored at mobile device 250. Mobile device 250 can also or alternatively set the received signal strength discovery threshold in response to a user selection.

[0125] The mobile device 250 can receive control device beacons via RF communication signals 202, 204 and compare the received signal strength indicators of the RF communication signals 202, 204 with a received signal strength discovery threshold. A control device that transmits a control device beacon received by the mobile device 250 at a received signal strength indicator below the received signal strength discovery threshold may not be selected for configuration and / or control in the load control environment 201. Making the discovery process based on the received signal strength indicator of the RF communication signals 202, 204 enables a more finely tuned discovery process. For example, the mobile device 250 filtering control device beacons received at a received signal strength below the received signal strength discovery threshold can enable physical boundaries (e.g., walls, ceilings, floors, partitions, etc.) within the load control environment 201 to begin to help define groups of control devices to be associated for collective load control. Physical boundaries within the load control environment 201 can interfere with the RF communication signals 202, 204 and can prevent the receipt of the RF communication signals 202, 204 from devices located outside the physical boundaries (e.g., other rooms, other cubicles, etc.) at a received signal strength above the received signal strength discovery threshold.

[0126] Lighting fixtures 210a to 210d that transmit control device beacons received by the mobile device 250 at a received signal strength indicator at or above the received signal strength discovery threshold can automatically be added to a group of control devices (e.g., a temporary group, a zone, or other group of control devices) for collective configuration and / or control in the load control environment 201. For example, control device beacons of the lighting fixtures 210a to 210d received by the mobile device 250 at a received signal indicator strength greater than -5 dBm can be discovered, and unique identifiers can be associated with configuration identifiers in a storage device for collective control in the load control environment 201.

[0127] If the mobile device 250 identifies that the received signal strength indicator of the control device beacon received from one of the lighting fixtures 210a to 210d is higher than the discovery threshold, the mobile device 250 may send an acknowledgement message to the lighting fixture (e.g., directly and / or via the system controller 240), and the lighting fixture may provide feedback to the user 205. For example, the mobile device 250 may identify that the signal strength of the RF communication signals 202, 204 received from the lighting fixture 210a in the control device beacon is higher than the received signal strength discovery threshold, and may send an acknowledgement message to the lighting fixture 210a, the acknowledgement message indicating that the lighting fixture 210a has been selected for configuration and / or control in the load control environment 201. The lighting fixture 210a may provide feedback to the user 205 to indicate that the lighting fixture 210a has been selected for configuration and / or control in the load control environment 201. The feedback may be provided by changing the state of the lighting load in the lighting fixture 210a. For example, the feedback may be provided by causing the lighting load to blink (e.g., flash) on and off; increasing and / or decreasing (e.g., strobe) the brightness level of the lighting load; adjusting the color of the lighting load; increasing and / or decreasing the color temperature of the lighting load; and / or providing other visual feedback to the user 205. The type of feedback may be indicated in the acknowledgement message from the mobile device 250, or may be pre-programmed and stored at the lighting fixtures 210a to 210d. The brightness level, color, or color temperature may be changed based on the received signal strength indicator of the RF communication signals 202, 204 currently received at the mobile device 250. For example, the brightness level and / or color temperature level may increase and / or decrease for each dBm at which the RF communication signals 202, 204 are received at the mobile device 250. The brightness level and / or color temperature level may be limited to the upper threshold of the strongest received signal strength indicator of the RF communication signals 202, 204 received at the mobile device 250. The brightness level and / or color temperature level may have a lower threshold of the weakest received signal strength indicator of the RF communication signals 202, 204 received at the mobile device 250.

[0128] When the control device beacon is received and / or when the received signal strength indicator of the beacon is below the received signal strength discovery threshold, the mobile device 250 and / or the system controller 240 may automatically deselect the control device that transmits the control device beacon to prevent it from being configurable and / or controllable. Alternatively, the control device may be manually deselected via an application running on the mobile device 250 (e.g., by the user 205). For example, the user 205 may select the devices to be removed from the list of control devices selected for configuration and / or control in the load control environment 201. The control device (e.g., identified by its unique identifier) may be removed from a set of control devices for configuration and / or control (e.g., a temporary group, a region, or other group of control devices). The received signal strength discovery threshold for deselecting the control device may be the same as or different from the received signal strength discovery threshold for selecting the control device for configuration and / or control. After the control device has been deselected and / or removed from the group, the control device may provide feedback indicating that they have been deselected and / or removed from the group. For example, similar to the devices that have been selected and / or added to the group for collective configuration and / or control, the lighting fixture 210a may blink, change color, or stop providing feedback.

[0129] The received signal strength discovery threshold may be changed to configure and / or control different control devices. For example, the user 205 may use an application running on the mobile device 250 to adjust the received signal strength discovery threshold. The received signal strength discovery threshold may be increased to select other lighting control devices for configuration and / or control, such as the lighting control devices in the lighting fixtures 210b to 210d. The received signal strength discovery threshold may be decreased to limit the lighting control devices selected for configuration and / or control. For example, the received signal strength discovery threshold may be limited such that a single lighting fixture (such as the lighting fixture 210a) may be selected for configuration and / or control at a certain moment as the mobile device 250 moves back and forth around the load control environment 201. When increasing and decreasing the received signal strength discovery range, control devices may be automatically added to and / or removed from the group for configuration and / or control (e.g., a temporary group, a region, or other group of control devices). When the control device is deselected and / or removed from the group, a message may be sent to the lighting control device that has been deselected and / or removed, causing the lighting control device to stop providing feedback to the user 205 in response to the message.

[0130] In another example, a message can be sent to a device to cause the device to provide feedback indicating that a control device is within discovery range, but subsequent buttons can be selected to configure and / or control different control devices. For example, a received signal strength discovery threshold can be set to a level such that each of the lighting control devices in lighting fixtures 210a to 210d can be discovered and / or selected for configuration and / or control. The mobile device 250 can send a message to each of the lighting fixtures 210a to 210d and instruct the lighting fixtures 210a to 210d to provide feedback to the user 205 that the lighting fixtures 210a to 210d have been discovered and / or selected for configuration and / or control. Although the lighting fixtures 210a to 210d can provide feedback, the received signal strength discovery threshold can be adjusted to adjust the lighting control devices in the lighting fixtures 210a to 210d to be selected for configuration and / or control in the load control environment 201. The lighting control devices can be automatically selected and / or deselected for configuration and / or control when adjusting the received signal strength discovery threshold, or the received signal strength discovery threshold can be adjusted and then the lighting control devices can be selected for configuration and / or control (e.g., in response to confirmation from the user). The user 205 can reduce the received signal strength discovery threshold to a range that includes messages from the lighting control device of lighting fixture 210a but not messages from the lighting control devices of lighting fixtures 210b to 210c. Another message can be sent to the lighting control devices of lighting fixtures 210b to 210d to cause the lighting fixtures 210b to 210d to stop providing feedback. The user 205 can select a button on the mobile device 250 to select the currently discovered lighting control device of lighting fixture 210a for configuration and / or control in the load control environment 210.

[0131] The user 205 can lock the received signal strength discovery threshold (e.g., after adjustment), and as the user 205 walks back and forth around the load control environment 201 with the mobile device 250, the mobile device 250 can continue to select control devices for configuration and / or control. After the user locks the received signal strength discovery threshold, the control devices within the defined discovery range can be automatically selected for configuration and / or control in the load control environment 201. The user 205 can then move back and forth around the load control environment 201 to continue automatically selecting control devices for configuration and / or control. The lighting control devices 210a to 210d within the discovery range can provide feedback as the user 205 walks back and forth with the mobile device 250. For example, the lighting control devices 210a to 210d within the discovery range can turn into a predefined color as the user 205 walks back and forth with the mobile device 250 to indicate to the user 205 the lighting control devices 210a to 210d that can be configured and / or controlled.

[0132] As user 205 moves the mobile device 250 back and forth around the load control environment 201, control devices (such as lighting fixture 210a) that have been selected for configuration and / or control may become undiscoverable. For example, the mobile device 250 may move outside the wireless range of the RF communication signals 202, 204 by which the control device beacon may be communicated. After a control device has been selected for configuration and / or control, the control device is configurable and / or controllable and may provide feedback indicating that the control device is still configurable and / or controllable until the device is deselected or the configuration (e.g., claiming, diagnosing, associating, etc.) and / or control (e.g., configuration procedure) of the device has ended. For example, the lighting control device of lighting fixture 210a may be configurable and / or controllable until the lighting control device is deselected, even if the lighting control device of lighting fixture 210a may become outside the discovery range determined according to the received signal strength discovery threshold.

[0133] Control devices in the load control environment 201 that transmit control device beacons may cause interference to other control devices communicating on the same network and / or protocol. Such interference may prevent the discovery of control devices that are transmitting control device beacons and would otherwise be discoverable without interference. To reduce such interference, a control device may stop transmitting the control device beacon after receiving an acknowledgement message indicating that the control device has been discovered and / or selected for configuration and / or control. The control device may continue to provide feedback to user 205 indicating that the device has been selected for configuration and / or control, but may stop transmitting the control device beacon to avoid interference and / or conserve battery in battery-powered devices.

[0134] Occupancy sensing technology can be implemented to select control devices for configuration and / or control in a load control environment 201. Sensors 216a through 216d in corresponding lighting fixtures 210a through 210d can be used to select lighting fixtures 210a through 210d for configuration and / or control. Sensors 216a through 216d can be occupancy sensors, visible light sensors (e.g., cameras), daylight sensors, optical sensors, and / or any other type of sensor. Sensors 216a through 216d can be visible light sensors (e.g., cameras). Sensors 216a through 216d can act as occupancy sensors. For example, when sensor 216a detects an occupancy condition, a signal can be sent from sensor 216a to the lighting control device of lighting fixture 210a. The lighting control device of lighting fixture 210a can transmit a control device beacon that is communicated to mobile device 250. Mobile device 250 can select lighting fixture 210a for configuration and / or control. After lighting fixture 210a has been selected for configuration and / or control in load control environment 201, lighting fixture 210a can provide feedback in response to the occupancy condition and / or a message received from mobile device 250 (e.g., an acknowledgement message).

[0135] Sensors 216a through 216d can identify different activity levels. For example, sensors 216a through 216d can identify large motion events (e.g., above a predefined high-end motion level) and small motion events (e.g., above a predefined low-end motion level) within the visible area of the sensors. Sensors 216a through 216d can send an occupancy condition when identifying a defined occupancy state or a defined activity level. User 205 can walk under lighting fixture 210a and perform a large motion event (e.g., a quick wave or other movement above a predefined threshold) to trigger an occupancy condition that can be identified by sensor 216a. User 205 can walk under a set of lighting fixtures 210a through 210d that will be detected by corresponding sensors 216a through 216d and select lighting fixtures in the walking path for configuration and / or control (e.g., as a temporary group).

[0136] Other control devices may be selected for configuration and / or control in the load control environment 201. For example, the occupancy sensor 234 and / or the remote control device 236 may be discovered via a configuration program (e.g., a solicitation program and / or an association program) to select them for configuration and / or control in the load control environment 201. The configuration program may be initiated by actuating a button on the occupancy sensor 234 or the remote control device 236. The occupancy sensor 234 and / or the remote control device 236 may be one-way communication devices that may not be able to receive the RF communication signals 202, 204. Actuation of the button may cause the device to set its unique identifier as a beacon. The mobile device 250 may discover the control device that transmits the control device beacon and automatically select the discovered device for configuration and / or control.

[0137] When the occupancy sensor 234 is in a configuration mode (e.g., a solicitation mode and / or an association mode), a message for discovering the occupancy sensor 234 may be triggered upon detection of an occupancy condition. The occupancy sensor 234 may identify different activity levels. For example, the occupancy sensor 234 may identify a large motion event (e.g., above a predefined high-end motion level) and a small motion event (e.g., above a predefined low-end motion level) within the visible area of the occupancy sensor 234. The large motion event or the small motion event may be used to discover the occupancy sensor 234. After detecting the large motion event and / or the small motion event, the occupancy sensor 234 may transmit a message that may be received by the mobile device 250. The occupancy sensor 234 may be automatically selected for configuration and / or control, or the received signal strength indicator of the message may be compared with a received signal strength discovery threshold to select the occupancy sensor 234 for configuration and / or control in the load control environment 201.

[0138] An optical signal may be used to select a control device (e.g., the lighting fixture 210a) for configuration and / or control. The mobile device 250 may transmit (e.g., periodically transmit) an optical signal (e.g., via the optical transmitter 209). The control device may receive the optical signal via an internal detector and / or sensor (e.g., sensors 216a to 216d) of the lighting load of the lighting fixtures 210a to 210d, and may measure the signal strength of one or more of the received optical signals. The mobile device 250 may transmit a configuration mode message to the load control devices of the lighting fixtures 210a to 210d (e.g., directly and / or via the system controller 240) before transmitting the optical signal, and each of the control devices may enter the configuration mode when the control device receives the configuration mode message. Alternatively, each of the control devices may enter the configuration mode when the control device receives the optical signal. One or more control devices may be individually selected for association with a group for configuration and / or control.

[0139] A lighting fixture that receives an optical signal can provide feedback to a user 205 to indicate that the lighting fixture has received the optical signal. The feedback can be provided by changing the state of a lighting load in the lighting fixture. For example, the feedback can be provided by causing the lighting load to blink (e.g., flash) on and off; increasing and / or decreasing (e.g., dim) the brightness level of the lighting load; adjusting the color of the lighting load; increasing and / or decreasing the color temperature of the lighting load; and / or providing other visual feedback to the user 205.

[0140] After entering the configuration mode, each of the control devices (e.g., the lighting control devices of lighting fixtures 210a to 210d) can transmit (e.g., periodically transmit) an indication of the signal strength at which the optical signal is received. The mobile device 250 can receive the signal strength indication from one or more of the control devices. The mobile device 250 can select a lighting control device to solicit based on the signal strength indication. The mobile device 250 can send a connection message (e.g., a solicitation message and / or an acknowledgement message) to the selected control device.

[0141] As the user 205 moves the mobile device 250 back and forth around the load control environment 201, additional lighting fixtures 210b to 210d can receive the optical signal. Each lighting fixture that receives the optical signal can provide feedback to the user 205 indicating that the lighting fixture is receiving the optical signal. The mobile device can automatically select one or more of the lighting fixtures for configuration and / or control in the load control environment 210. Each of the selected lighting fixtures 210b to 210d can receive an acknowledgement message from the mobile device 250 and provide similar feedback to the user 205 to indicate that the lighting fixture has been selected for configuration and / or control.

[0142] After a control device has been selected for configuration and / or control, the control device can be displayed to the user 205 on the user interface 252 of the mobile device 250. The user 205 can select a device to remove from a list of control devices that have been selected for configuration and / or control in the load control environment 201. The lighting control devices 210a to 210d that have been selected for configuration and / or control can provide visual feedback to the user 205. For example, the lighting control devices 210a to 210d that have been selected for configuration and / or control can turn on or off, blink, adjust to a predefined brightness, and / or change to a predefined color (e.g., green).

[0143] One or more of the devices selected for configuration and / or control may be identified for configuration and / or control at a given time. For example, user 205 and / or mobile device 250 may identify lighting control devices 210a-210d for configuration. The lighting control devices may be identified by user selection on mobile device 250. In another example, the lighting control devices may be automatically identified as the devices from which mobile device 250 receives the strongest control device beacon. Identifying lighting control devices 210a-210d for configuration and / or control may provide a different type of feedback than other control devices selected for configuration and / or control. For example, the identified lighting control devices may turn a different color (e.g., blue). This may allow user 205 to visually identify the devices being configured.

[0144] When a device is deselected for configuration and / or control, a message may be sent to the control device (e.g., a lighting control device among lighting fixtures 210a-210d) to indicate that the control device has been deselected. The message may cause the control device to stop providing feedback that the device was selected for configuration and / or control. For example, lighting fixture 210a may stop providing feedback to user 205 after receiving an indication that lighting fixture 210a has been deselected. Any configuration information (e.g., claim information and / or association information) (e.g., including unique identifiers of a temporary group of devices selected for configuration and / or control or control devices in the temporary group) stored thereon at the deselected control device may be deleted.

[0145] After a list of control devices to be configured and / or controlled in a load control environment is included, the user may select a button on mobile device 250 (e.g., via user interface 252) to trigger association of the selected devices. If configuration information (e.g., a unique identifier of a temporary group or a control device in the temporary group) related to a control temporary group of devices selected for configuration and / or control has not been communicated to the control devices in the temporary group, the configuration information may be communicated to the devices. For example, when a message including a temporary group identifier is received from occupancy sensor 234, remote control device 236, system controller 240, and / or mobile device 250, the temporary group identifier may be communicated to lighting fixtures 210a-210d for control implementation. The control devices may be configured (e.g., claimed and / or associated) by transmitting an identifier of a control device selected for configuration and / or control to other devices selected for configuration and / or control for storage on the other devices.

[0146] The temporary group control device may be associated with a unique identifier of a location. For example, a temporary group identifier for implementing control of devices in a temporary group may be a location beacon. The location beacon may be discovered and communicated to the temporary group devices for performing control at the location.

[0147] Figure 2D Illustrate another example of using a beacon to configure and / or control a control device in a representative load control environment 201. As Figure 2D shown, lighting fixtures 210a, 210b may be used to provide feedback indicating the occupancy / vacancy emission range 205 of the occupancy sensor 230. Failure to properly communicate a message from the occupancy / vacancy sensor to other devices in the system results in a communication error. The occupancy sensor 234 may be configured to transmit a beacon (e.g., a ranging beacon) that can be received at the lighting fixtures 210a, 210b to provide feedback to the user 205 regarding the emission range 205 associated with the occupancy sensor 234. After the occupancy sensor 234 is in the ranging mode, the occupancy sensor 234 may transmit the ranging beacon to the lighting control devices of the lighting fixtures 210a to 210d to indicate the lighting fixtures 210a to 210d that receive the ranging beacon or receive the ranging beacon at or above a predefined ranging threshold to provide feedback. The feedback may indicate the emission range 205 of the occupancy sensor 234 and / or the lighting control devices that may respond to the occupancy and / or vacancy conditions detected by the occupancy sensor 234.

[0148] The occupancy sensor 234 may transmit a ranging beacon via the RF communication signal 204. The ranging beacon may include a ranging threshold that may indicate a sufficient received signal strength indicator corresponding to the transmission range 205 of the occupancy sensor 234. The ranging threshold may also or alternatively be pre-defined at the lighting control devices of the lighting fixtures 210a to 210d. The lighting control devices of the lighting fixtures 210a, 210b that receive a message from the occupancy sensor 234 at a received signal strength indicator at or above the ranging threshold may provide feedback to the user 205 to indicate the transmission range 205 of the occupancy sensor 234. The feedback may be provided for a certain period of time after receiving the ranging beacon. If another ranging beacon is not received, or another ranging beacon is received at a received signal strength indicator below the ranging threshold, then during a pre-defined period of time, the lighting control devices of the lighting fixtures 210a, 210b may stop providing feedback at the end of the pre-defined period of time. The lighting fixtures 210c, 210d that receive a ranging beacon from the occupancy sensor 234 at a received signal strength indicator below the wireless threshold and / or that fail to receive a ranging beacon from the occupancy sensor may not be able to provide feedback to the user 205. The feedback may assist the user 205 in placing the occupancy sensor 234 within the load control environment 201. The feedback may indicate when a message is properly communicated to the control devices in the system, and / or when the transmission range of the occupancy sensor 234 overlaps with another occupancy sensor in the same area.

[0149] Figure 2E FIG. is a diagram of an exemplary network 260 that may permit communication between devices in a load control system (e.g., load control system 100 and / or load control system 200). The network 260 may include any suitable network that facilitates communication in a load control system or an Internet of Things (IoT) environment. For example, the network 260 may use network protocols. The various control devices of the load control system 200 may communicate with each other via the network 260. As Figure 2E shown, the network 260 may include a single network partition. Additionally, the network 260 may be an instance of a network partition (e.g., a sub-network or subnet) within a larger network. For example, the network 260 may be an instance of a network partition within a larger network composed of multiple network partitions. The network 260 is an exemplary network, and the techniques described herein may be applied to other networks that include, for example, more or fewer devices compared to the network 260.

[0150] Figure 2EThe circled nodes may represent devices that are coupled to and attached to other devices (e.g., various control devices of load control system 100 and / or load control system 200) on network 260. A device attached to at least one other device on network 260 may communicate with other devices (e.g., another device to which it is attached on network 260). Communication within network 260 may be facilitated by links (e.g., attachments) established within network 260. Referring Figure 2E , the links between devices may be indicated by lines (e.g., solid and dashed lines) connecting the respective devices.

[0151] Figure 2D One or more of the illustrated devices may be coupled to network 260 via an enrollment process. Network 260 may be a mesh network, and each device may exchange network credentials with a commissioning device (e.g., a system controller or a mobile device), thereby allowing the device to be coupled to network 260 and enabling the device to communicate on network 260. A device may be able to communicate with other devices using another wireless protocol, but may not be able to communicate with or attach to other devices on network 260 without network credentials. Network credentials may include an enrollment party identifier (e.g., or any other identifier) that the device may use to enroll in network 260 and communicate with another device.

[0152] A device may be solicited (e.g., via a solicitation process) before being coupled to network 260. For example, a solicitation process may be used to identify devices (e.g., individual devices and / or groups of devices) for coupling to network 260. As part of the solicitation process, the device may exchange credentials with a commissioning device to enable the device to communicate on network 260. Without this credential exchange, the device will not obtain an enrollment party ID and may not be able to communicate on network 260.

[0153] A device attached to at least one other device on network 260 may assume and / or be assigned a corresponding role in the network. For example, roles may include: a leader device (e.g., leader device 262), a router device (e.g., router devices 264a to 264d), and / or a terminal device (e.g., terminal devices 266a and 266b). The role of a device may indicate the function and / or capabilities of the device relative to network 260.

[0154] As Figure 2EAs illustrated, network 260 may include a leadership device 262. The leadership device 262 may manage other devices attached to the network 260. For example, the leadership device 262 may assign and maintain a router identifier (e.g., router ID) for each of router devices 264a to 264d. For example, each of router devices 264a to 264d may be assigned a unique router identifier. The leadership device 262 may assign and maintain the roles of other devices. The leadership device 262 may be configured as the gateway of the network 260. For example, the leadership device may be a device that facilitates communication (e.g., round-trip routing and receiving messages) between the network 260 and other networks or network partitions. Refer to Figure 2A , the system controller (e.g., Figure 2A the system controller 240 shown) may be an instance of the leadership device 262. Additionally, a device within the load control system that is capable of being assigned the role of a router device may be assigned the role of the leadership device (e.g., a control device).

[0155] The network 260 may include one or more router devices 264a to 264d. The leadership device 262 may support and be attached to multiple router devices (e.g., more than 30 router devices). The leadership device 262 may operate as a router device. The router devices 264a to 264d on the network 200 (e.g., attached to the leadership device 262 on the network 260) may communicate with each other, for example, to form a mesh network. The router devices 264a to 264d may communicate with each other (e.g., as indicated by the solid lines connecting the router devices 264a to 264d). The router devices 264a to 264d may communicate with the leadership device 262 directly or through one or more other router devices (e.g., as indicated by the solid lines connecting the leadership device 262 to the router devices 264a and 264c). The router devices 264a to 264d may receive messages and route the messages to other devices on the network 260 (e.g., terminal devices 266a, 266b). For example, the router devices 264a to 264d may receive / transmit messages between devices or among themselves for communicating a message received from an attached device to another device attached to another router device. Now refer to Figure 2A the load control system 200 shown, for example, a device externally powered by an AC grid (e.g., a device that is not battery-powered) may be assigned the role of a router device. For example, the system controller 240 and / or the lighting control devices of the lighting fixtures 210a to 210d may be assigned the role of a router device.

[0156] Network 260 may include one or more terminal devices 266a, 266b (e.g., full or minimal terminal devices). Each of the terminal devices 266a, 266b may be attached to another device (e.g., a parent device) on network 200 and may transmit and / or receive messages via the attached router devices 264a to 264d. For example, each of the terminal devices 266a, 266b may transmit an address (e.g., a network address), a joining party identifier (e.g., for network authentication), and / or other types of device identification data to one or more of the router devices 264a to 264d. Although two terminal devices 266a, 262b are shown in Figure 2E and each is attached to a different router device, each of the router devices 264a to 264d may support multiple terminal devices (e.g., more than 500 terminal devices). Referring to Figure 2A the load control device 200, the system controller 240, an input device (e.g., the remote control device 232 and / or the occupancy sensor 230), and / or a load control device (e.g., the lighting control device for the lighting fixtures 210a to 210d) may be Figure 2E examples of the terminal devices 266a, 266b shown.

[0157] The leader device 262 may update (or confirm a role update for) the roles of the devices communicating within network 260 based on changes to network 260. In one example, a device may be assigned a certain role when the device is attached to network 260, and the leader device 262 may update the role of the device based on changes in network conditions. Changes in network conditions may include: increased message traffic, attachment of other devices, changes in signal strength, etc. The update of the assigned role of a device may be based on the capabilities of the device. The leader device 262 may update the role of the device to a router device by assigning a router identifier (ID) to the device.

[0158] Devices attached to other devices on network 260 can further operate as parent and child devices. A leading device (e.g., leading device 262) and router devices (e.g., router devices 264a to 264d) attached to one or more terminal devices (e.g., terminal devices 266a, 266b) can operate as parent devices. Terminal devices (e.g., terminal devices 266a, 266b) attached to the leading device (e.g., leading device 262) and / or a router device (e.g., one of router devices 264a to 264d) can operate as child devices. As parent devices, the leading device 262 and router devices 264a to 264d can each be attached to one or more child devices (e.g., one or more of terminal devices 266a, 266b, as described herein). Additionally, the leading device 262 and router devices 264a to 264d can store and / or relay messages sent by their respective attached child devices. For example, the leading device 262 and router devices 264 can receive messages from their respective child devices and route the received messages to the intended recipient device (e.g., directly or via the respective parent device of the intended recipient device). Similarly, the leading device 262 and router devices 264a to 264d can receive messages destined for their respective child devices and route the messages to the appropriate child device.

[0159] As Figure 2E indicated, the relationship (e.g., attachment) between a child device and its corresponding parent device can be indicated by a dashed line. Router device 264a can receive a message destined for terminal device 266a and forward the message to terminal device 266a. When router device 264a is configured as the parent device of terminal device 266a, terminal device 266a can transmit a message to router device 264a, and router device 264a can route the message to the intended recipient. For example, when terminal device 266a intends to transmit a message to terminal device 266b, terminal device 266a can initially transmit the message to router device 264a. Router device 264a can route the message to router device 264b (e.g., the parent device of terminal device 266b), and then router device 264b can forward the message to terminal device 266b.

[0160] As described herein, network 260 can allow communication between devices in a load control system (e.g., Figure 2A the load control system 200 shown). Terminal devices 266a, 266b can include load control devices (e.g., control target devices) and / or input devices (e.g., control source devices) for communicating with other devices in the load control system. For example, terminal device 266a can communicate with another terminal device in the load control system via RF communication.

[0161] Referring toFigure 2A The remote control device 232 can operate as a terminal device for communicating digital messages, which include instructions input by a user and / or control commands for controlling another terminal device (e.g., the lighting control devices of the lighting fixtures 210a to 210d). The remote control device 232 can communicate via one or more intermediate parent devices such as, for example, a leader device and / or a router device. The leader device and / or the router device can communicate with one or more other leader devices and / or router devices in the network to route messages to other terminal devices (e.g., the lighting control devices of the lighting fixtures 210a to 210d) for performing load control.

[0162] Figure 3 is an illustration of an exemplary control system 300 (e.g., Figure 1 the load control system 100 shown and / or Figures 2A to 2C the load control system 200 shown). As Figure 3 shown, the control system 300 can include load control devices for commissioning, such as lighting control devices 310 (e.g., the lighting control device 114 of the lighting fixture 110, the lighting control devices 124a to 124c of the lighting fixtures 120a to 120c, the controllable light sources 122 of the lighting fixtures, and / or the lighting control devices of the lighting fixtures 210a to 210d, 220a to 220d). The lighting control device 310 can be commissioned by configuring the lighting control device 310 for lighting control. The lighting control device 310 can be configured to perform lighting control by being solicited; being assigned to different luminaires, groups, zones, and / or locations in the configuration data of the control system 300; and / or being coupled to a communication link 312, such as a wireless communication network. The lighting control device 310 can be configured by defining preset scenes or other lighting control parameters by which the lighting control device 310 can be controlled.

[0163] The control system 300 can include a system controller 340 (e.g., the system controller 140). The system controller 340 can communicate with the lighting control device 310 via the communication link 312 for performing lighting control according to lighting control configuration information that can be stored thereon (e.g., stored on the system controller 340) during previous operations. The lighting control configuration information can include preset configurations, zone configurations, occupancy configurations, and / or scheduling configurations for controlling the lighting control device 310.

[0164] Illumination control configuration information can be generated by a network device such as processing device 360 (e.g., a personal computer or laptop). Processing device 360 can be a network device on which design software can be executed to configure (e.g., solicit, diagnose, associate, etc.) and / or control the design of a load control system within a load control environment. Processing device 360 can generate a control database including illumination control configuration information (e.g., load control parameters) based on a floor plan and design of the illumination control system. Processing device 360 can generate a project code identifier that is used to identify the floor plan and / or the project in which the control database for controlling the devices in the floor plan is stored. The illumination control configuration information of the control database can be stored in lighting fixture 310 or system controller 340 for implementing illumination control according to the information. Processing device 360 can communicate with system controller 340 via communication link 342. Communication link 342 can be a wired or wireless communication link, such as for example an Ethernet link and / or a local area network HTTPS communication link.

[0165] System controller 340 can send the illumination control configuration information to lighting control device 310 and / or control lighting control device 310 according to the illumination control configuration information. System controller 340 can communicate with lighting control device 310 via communication link 312 (e.g., a wireless communication network). Communication link 312 can include RF communication signals communicated via one or more protocols (e.g., standard communication protocols, such as WI- NFC; Thread; and / or private communication protocols, such as CLEAR CONNECT TM 、Z-WAVE). Communication link 312 can include an Ethernet link or other wired network communication links.

[0166] After generating the illumination control configuration information at processing device 360, processing device 360 can share the illumination control configuration information with other devices to update and / or assist in the debugging of control system 300. For example, processing device 360 can store the illumination control configuration information on a remote data source (such as cloud server 370) for access by other devices. Processing device 360 can communicate with cloud server 370 via communication link 372. Communication link 372 can communicate via wired and / or wireless signals (e.g., using Internet Protocol (IP) and / or Hypertext Transfer Protocol (HTTP) communication). The illumination control configuration information can be stored at processing device 360 and / or cloud server 370 together with a project identifier used to distinguish it from other projects.

[0167] The control system 300 may include a network device, such as a mobile device 350 (e.g., a smart phone or a tablet), which may be implemented to solicit (e.g., discover) a control device (e.g., the lighting control device 310) for commissioning the control system 300. The mobile device 350 may allow a user to access a control database of items in the control system 300 and discover the lighting control device 310 for configuration for the item. The lighting control device 310 may be discovered by the mobile device 350 via a wireless communication link 352 (e.g., a short-range wireless communication link). The wireless communication link 352 may allow beacon communication or other short-range RF communication. The wireless communication link 352 may include an RF signal communicated using a communication protocol or a low-power (BLE) communication protocol. Although the wireless communication link 352 may be described herein as including an RF signal communicated using a communication protocol, other short-range RF communication protocols may be implemented. For example, the wireless communication link 352 may include an RF signal communicated using a near field communication (NFC) protocol, a WI-FI communication protocol, and / or other RF communication protocols.

[0168] The mobile device 350 may access lighting control configuration information of the control database from a cloud server 370 and / or a processing device 360. The mobile device 350 may communicate with the cloud server 370 via a communication link 372. The mobile device 350 may communicate with the processing device 360 via the wireless communication link 352. The mobile device 350 may also or alternatively access lighting control configuration information of the control database via a direct wired connection (such as a universal serial bus (USB) cable) and / or a computer-readable medium (such as a USB drive or other external memory).

[0169] The mobile device 350 may locally execute an application thereon to assist in commissioning the control system 300. A user may select a button on the application to synchronize the lighting control configuration information in the application with the lighting control configuration information stored for an item in the cloud server 370. A user of the mobile device 350 may access area and region information in the lighting control configuration information for allocating the discovered lighting control device 310.

[0170] When allocating the lighting control device 310 to a luminaire, group, region, and / or location at the mobile device 350, the lighting control configuration information may be updated and sent to the cloud server 370. For example, the lighting control device identifier and / or beacon identifier of each lighting control device 310 may be stored together with the location in the associated area, region, and / or district for corresponding control. Then the lighting control configuration information may be accessed by the processing device 360 for sending to the system controller 340 and / or the lighting control device 310 for implementing lighting control according to the updated allocation.

[0171] Figure 4A is a flowchart depicting an exemplary method 400 (e.g., a debugging program) for debugging a control system such as a load control system (e.g., load control system 100). The method 400 can be implemented by one or more devices. For example, the method 400 can be implemented by a system controller (e.g., system controllers 140, 240, 340), a cloud server (e.g., cloud servers 170, 370), and / or a network device such as a mobile device (e.g., mobile devices 150, 250, 350) and / or a processing device (e.g., such as processing devices 160, 360). The method 400 can start at 402.

[0172] At 404, a load control system can be designed (e.g., as part of a design program). For example, design software running on a processing device can be used to design the load control system. The design software can be configured to generate configuration data that can define the operation and / or functionality of the load control system. The configuration data can be stored in a configuration database (e.g., on a processing device, a cloud server, a mobile device, and / or a system controller). The processing device can store the configuration data (e.g., the configuration database) in a project (e.g., which can include other identification information of a building in which the load control system can be installed). The configuration data can include a representation of control devices (e.g., lighting fixtures, occupancy sensors, remote control devices, etc.) in the load control system, as well as configuration identifiers of the control devices (e.g., fixture, group, zone, area, and / or location identifiers). For example, the configuration data can define the functionality of the control devices (e.g., how lighting fixtures respond to occupancy sensors / or remote control devices). The configuration data can define lighting control configuration information including control parameters that can be stored in the control devices and / or the system controller (e.g., as will be described at 414 below). The control parameters can be used by the control devices and / or the system controller to control an electrical load during normal operation (e.g., after the method 400 is completed).

[0173] At 406, configuration data (e.g., all or part of a configuration database) can be transferred from a processing device to a mobile device (e.g., as part of a configuration data transfer program). For example, the processing device can be configured to transfer configuration data to the mobile device via a cloud server. When the configuration data is ready to be transferred (e.g., when the control device of the control system is ready to be requested and / or associated with a configuration identifier of the configuration data (e.g., a region or group identifier for joining a network)), the processing device can transmit the configuration data to the cloud server via the Internet (e.g., using IP and / or HTTP communication via communication link 372). The processing device can display a project code (e.g., a code unique to the project of the load control system being debugged). For example, the project code can include an alphanumeric sequence. The user can type the project code into a configuration application running on the mobile device. The mobile device can transmit the project code to the cloud server, and the cloud server can transmit the configuration data to the mobile device. Additionally, the processing device can display a machine-readable code, such as a barcode and / or a Quick Response (QR) code, and the mobile device can scan the machine-readable code to determine the project code. When the processing device and / or the mobile device do not have Internet access, at 406, the configuration data can be transferred (e.g., directly transmitted) from the processing device to the mobile device via a direct wired connection (such as a Universal Serial Bus (USB) cable) and / or a computer-readable medium (such as a USB drive or other external memory). Further, the configuration data can be transmitted (e.g., directly transmitted) from the processing device to the mobile device via a short-range wireless communication link (e.g., using or BLE technology via communication link 352).

[0174] At 408, a control device of the load control system may be solicited and / or associated with a configuration identifier of configuration data (e.g., a luminaire, group, area, zone, and / or location that may be defined by the configuration data). For example, at 408, as part of a configuration procedure (e.g., a solicitation procedure and / or an association procedure), a mobile device may solicit the control device and / or associate the control device with the configuration identifier of the configuration data. For example, the mobile device may start transmitting (e.g., periodically transmitting) a mobile device beacon via a short-range wireless communication link (e.g., using BLE technology via communication link 352). A control device that receives the mobile device beacon and is within the discovery range of the mobile device may be configured to transmit a corresponding control device beacon. The mobile device may receive control device beacons from multiple control devices and may select the control device from which it receives the control device beacon (e.g., the control device from which it receives the control device beacon under the strongest received signal strength indicator) to solicit. An installer may select, from the mobile device, the configuration identifier to associate the current control device with to initiate a solicitation of the control device. The installer may move the mobile device around the building in which the load control system is installed to solicit and associate each of the control devices. When soliciting each of the control devices, the solicited control device may transmit a unique identifier (e.g., a serial number) to the mobile device, and the mobile device may store the unique identifier and the association between the configuration identifier and the control device in the configuration data. When the installer finishes soliciting the control devices (e.g., the mobile device has solicited all or a portion of the control devices of the load control system), the configuration procedure may end.

[0175] Before being solicited at 408, the control device may listen (e.g., continuously) for mobile device beacons on a short-range wireless communication link (e.g., communication link 352). After being solicited at 408, the control device may enter an engagement mode. In the engagement mode, the control device may periodically switch between listening for mobile device beacons (e.g., using BLE technology) and listening for requests to engage a wireless communication network (e.g., communication link 312). Switching between listening for mobile device beacons and listening for requests to engage a wireless communication network may allow the control device to be ready to engage the wireless communication network while still allowing the mobile device to connect to one or more of the control devices (e.g., to correct an error made when soliciting the control device, or to cancel the solicitation of the control device).

[0176] At 410, configuration data (e.g., updated during the configuration procedure as at 408) can be transferred from the mobile device to the system controller. For example, the configuration data can be transferred from the mobile device to the system controller via the processing device. For example, the mobile device can be configured to transfer the configuration data to the processing device (e.g., as described above at 406) via a cloud server, via a direct wired connection, and / or via a short-range wireless communication link. The processing device can then transmit the configuration data (e.g., all or a portion of the configuration database) to the system controller or another debug party device (e.g., via communication link 342). The debug party device can be a device on a wireless communication network (e.g., a network) for engaging other devices to the network. For example, the debug party device can be a system controller, a lighting control device, a control source device, etc. Additionally, the mobile device can be configured to transmit the configuration data to the system controller via a cloud server (e.g., without transmitting the configuration data to the processing device). Further, the mobile device can be configured to transmit (e.g., directly transmit) the configuration data to the system controller via a direct wired connection and / or via a short-range wireless communication link.

[0177] The configuration data can include device identification data received from control devices such as lighting fixtures. The system controller or other debug party device can receive the device identification data of multiple devices. For example, multiple devices may have participated in the discovery procedure performed at 408. For each device participating in the discovery procedure, the network device can transfer the device identification data to the system controller or other debug party device. The device identification data of each device can be transferred individually (e.g., not simultaneously). The system controller or other debug party device can indicate to the user (e.g., via an application program executed on a separate computing device) how many devices have been discovered for engagement to the network and / or how many devices remain to be discovered for engagement to the network. For example, the network device can display a list of each control device in the area (e.g., in text or graphical form). Once the system controller or other debug party device has received the device identification data of the lighting fixture, the color of the lighting fixture can be changed. The system controller or other debug party device can aggregate the device identification data received from the devices and can generate a single list of the lighting fixtures.

[0178] The system controller or other debugging party device may operate in an offline mode (e.g., the debugging party device may be disconnected from the Internet or otherwise unable to access specific online services used during debugging). The network device may transmit device identification data to the system controller or other debugging party device (e.g., directly to the debugging party device) via, for example, an RF signal, a USB transfer, etc. Additionally, the network device may transmit device identification data to the system controller or other debugging party device via a processing device. The network device may be physically connected to the processing device (e.g., via USB). For example, the network device and the processing device may be connected by an electrical cord having a USB connector at either end. The network device may transmit device identification data to the processing device via the physical connection. The network device may be physically connected to the system controller or other debugging party device via a wired digital communication link (e.g., via an Ethernet link). The processing device may transmit device identification data to the system controller or other debugging party device via the wired digital communication link. The network device may transmit device identification data by transmitting (e.g., copying) the device identification data to an external drive (e.g., removable memory). The external device may be connected to the processing device, and the processing device may transmit (e.g., copy) the device identification data from the external drive to local memory. The processing device may store the device identification data in the memory. The processing device may then transmit the device identification data to the debugging party device via the wired digital communication link. The debugging party device may also store the device identification data in the memory.

[0179] At 412, the control device requested at 408 may be coupled to a wireless communication network (e.g., communication link 312). The system controller may operate as a debugging party device for coupling the control device to the wireless communication network. After the control device is coupled to the wireless communication network, the control devices may communicate with each other via the wireless communication network during normal operation. Additionally, the control devices may stop monitoring the network on which mobile device beacons are received and may communicate (e.g., exclusively) on the wireless communication network. At 414, configuration data may be transmitted to the control devices. For example, the system controller may transmit the portion of the configuration database associated with the respective control device to the control device.

[0180] Figure 4B and Figure 4C are flowcharts illustrating exemplary methods 420, 435, which illustrate detailed portions of a debugging procedure. Methods 420, 435 may be performed during a debugging procedure (e.g., Figure 4Aduring the commissioning process of the method 400 shown, for configuring and / or controlling one or more control devices, such as lighting fixtures (e.g., lighting control devices associated with lighting fixtures). Each lighting fixture may include a lighting load (e.g., a lamp, an LED light source, etc.), and a lighting control device for controlling the amount of power supplied to the lighting load (e.g., a dimmer, an LED driver, a ballast, etc.).

[0181] Figure 4B The method 420 shown may be executed Figure 4A during the claim process shown at 408 of the method 400 shown. The method 420 or portions thereof may be implemented by one or more devices of a load control system (e.g., the load control system 100), such as, for example, network devices such as mobile devices (e.g., mobile devices 150, 250), system controllers (e.g., system controllers 140, 240 or other control devices), and / or other control devices of the load control system (e.g., the lighting control devices of lighting fixtures 110, 120 or lighting fixtures 210a to 210d; remote control devices 136, 232; and / or occupancy sensors 134, 234) may execute the method 420 or portions thereof. For example, other control devices may similarly execute one or more portions of the method 420.

[0182] The method 420 may be executed when one or more devices are in an offline mode. For example, network devices (e.g., mobile devices 150, 250), system controllers (e.g., system controllers 140, 240 or other control devices), and / or other control devices in the load control system (e.g., the lighting control devices of lighting fixtures 110, 120 or lighting fixtures 210a to 210d; remote control devices 136, 232; and / or occupancy sensors 134, 234) may be in an offline mode. When a device is disconnected from the Internet (e.g., via Wi-Fi, cellular, and / or another communication network) or a specific online service (e.g., a service for accessing information used during commissioning) that can be accessed via wired or wireless communication, the device may be in an offline mode. For example, the method 420 may be executed during a commissioning process to configure a load control system in a building before a wired local area network, a wireless local area network, and / or another suitable wired or wireless communication network has been installed and / or configured in the building. The method 420 may be executed when one or more devices in the load control system are otherwise unable to access information via an online service (e.g., unable to log in to the service, access rights are temporarily unavailable, etc.). During the implementation of the method 420, the device may be able to communicate via local wired and / or wireless communication (e.g., low energy (BLE), communicate directly via Wi-Fi Direct, Near Field Communication (NFC), and / or other wireless communications to share information. The local wireless communication can be short-range wireless communication.

[0183] Method 420 can be used to solicit one or more control devices (e.g., lighting control devices associated with lighting fixtures) in a given area (e.g., a building in which a load control system is installed) for attachment to a network. Method 420 can have the advantage of being able to execute when there is no connection to the Internet in the area. The solicitation procedure can be used to collect device identification data from one or more control devices and / or to send configuration information to the control devices. The solicitation procedure illustrated in Method 420 can be executed for each control device (e.g., lighting fixture) in the area. The solicitation of devices can also be performed by different users and / or devices, and the solicited devices can be batched together for attachment to the network.

[0184] As Figure 4B shown, Method 420 can begin at 422. At 424, one or more control devices can be highlighted for identification and / or configuration. The control devices can be highlighted in response to, for example, a user of a network device entering the range of a control device (e.g., a lighting fixture) and / or the control device receiving a signal (e.g., an optical signal). For example, the user can highlight a control device by physically moving the network device closer to a control device in a given area and / or by pointing an optical transmitter at the control device and emitting an optical signal. The highlighted control device can be the control device in the given area that is closest to the user (e.g., the network device). The network device can determine whether a control device is the closest based on the signal strength of a message received from the control device and / or based on the signal strength of an optical signal at the control device. The control device can indicate that it has been highlighted, for example, by providing a feedback type to a user in the room as described herein. For example, a lighting fixture can provide feedback by transitioning to a predefined color (e.g., blue) to indicate that the lighting fixture is highlighted.

[0185] At 426, the highlighted control device can be associated with a configuration identifier. For example, the network device can receive a user's selection of a configuration identifier to associate the configuration identifier with the highlighted control device. Alternatively, the network device can select a configuration identifier for the control device based on configuration data. The configuration data can be stored in a configuration database (e.g., on a processing device, cloud server, mobile device, and / or system controller). The processing device can store the configuration data (e.g., the configuration database) in a project (e.g., which can include other identification information of a building in which the load control system can be installed). The configuration data can include representations of control devices in the load control system (e.g., lighting fixtures, occupancy sensors, remote control devices, etc.), and configuration identifiers of the control devices (e.g., fixture, group, zone, area, and / or location identifiers). For example, the configuration data can define the functionality of the control device (e.g., how a lighting fixture responds to an occupancy sensor / or a remote control device).

[0186] At 428, the network device can receive device identification data from the highlighted control device (e.g., a lighting control device that controls the highlighted lighting fixture). For example, the network device can receive an address (e.g., a Thread network address), an attachment party ID (e.g., for network authentication), a unique identifier (e.g., a serial number), and / or other types of device identification data. Method 420 can be performed when the control device is transmitting (e.g., beaconing), such that the network device can receive the device identification data from a signal (e.g., a beacon signal) transmitted by the control device. The device identification data can be transmitted via the same communication medium used to transmit the beacon signal (e.g., BLE communication) or another RF communication medium.

[0187] After receiving the device identification data from the control device, at 430, the network device may transmit configuration information to the control device. For example, the configuration information may include a timestamp, a selected configuration identifier, a network device identifier / application identifier (e.g., to indicate to the device the control device being sought), and / or channel information (e.g., which may assist the control device in joining the correct network). The timestamp may be used (e.g., automatically) to resolve conflicts that may be caused by multiple users debugging simultaneously and in the same space. The network device identifier / application identifier may be used to determine which user previously sought the control device. The channel information may be used to accelerate the control device's joining procedure. For example, when the control device joins the network, there may be multiple RF channels / frequencies available for use. The control device may scan through the available RF channels / frequencies to determine on which RF channel / frequency the system controller is located. The channel information may allow the control device to achieve a more efficient scan by guiding the control device to prefer the channel provided during the request. The configuration information may include a logical load identifier that identifies a logical representation of the load in the design. The logical load identifier may be created when the user creates the load. The logical load identifier may allow the user to understand that the control device was sought without accessing the Internet.

[0188] The configuration information may be transmitted via an RF communication signal. In response to receiving the configuration information, the control device may indicate that the control device has been assigned to a certain luminaire and / or area by providing a feedback type as described herein. For example, the lighting control device may indicate that the lighting control device has been assigned to the luminaire and / or area by causing the corresponding lighting luminaire to provide feedback. For example, the lighting luminaire may turn into a predefined color (e.g., green) to indicate that the lighting luminaire has been assigned to the luminaire and / or area. At 432, the network device may store the device identification data received from the control device in a memory. For example, the device identification data of each control device may be stored on the application together with a floor plan identifier that identifies the physical location of the control device.

[0189] At 434, a determination may be made as to whether to identify and / or configure additional control devices in the area. The network device may compare a list of control devices for which it has received device identification data during the commissioning process with a list of control devices to be configured within the area. The network device may prompt the user to indicate whether to identify and / or configure any additional control devices. For example, the network device may display one or more buttons (e.g., "Continue" and "Done", or just "Done") on a display of the network device and determine whether to identify and / or configure additional control devices based on the button selected by the user. This may allow the user to identify and / or configure a subset of devices in the area or across multiple areas. The user or another user may return to identify and / or configure other control devices. The network device may also automatically detect when device identification data has been received from each of the control devices in a given area or project, and method 420 may end at 434. The network device may (e.g., prior to executing method 420) generate a list of control devices to be configured within the area. For example, the network device may generate the list by scanning QR codes present on each control device and adding each control device to the list. Then at 434, the network device may determine whether the commissioning process has been completed for each control device on the list.

[0190] If it is determined that there are one or more control devices to be identified and / or configured (e.g., commissioned) in the area or region, method 420 may return to 424. In fact, a determination that there are one or more control devices to be identified and / or configured may be made when another control device is highlighted for identification and / or configuration. If it is determined that device identification and / or configuration (e.g., the commissioning process) has been completed, method 420 may end.

[0191] Commissioning control devices (e.g., lighting control devices associated with lighting fixtures) by commissioning each control device and then proceeding to connect the control device to the network (e.g., rather than commissioning and connecting each control device and then proceeding to the next control device) may have several advantages. For example, control devices may be commissioned when one or more devices in the system are otherwise unable to access information via an online service (e.g., unable to log in to the service, access rights are temporarily unavailable, etc.). Additionally, commissioning control devices in this manner may allow multiple users or devices to commission control devices, and / or may allow control devices in one or more areas to be commissioned at different times. Further, control devices may be commissioned before the network infrastructure (e.g., local area network) and / or network devices (e.g., routers, switches, and / or processors) have been installed in the area.

[0192] The control device may use one or more network protocols to send transmissions. For example, an unclaimed control device may use BLE communication to send messages (e.g., beacons). The unclaimed control device may continuously use BLE communication to send signals. After the control device is claimed, the control device may use an alternative network protocol. For example, the control device may alternately use the protocol and / or BLE communication. The control device may use the protocol to communicate in order to receive a join request sent by the system controller. The control device may use BLE communication to send a signal (e.g., if a network device comes back into range and the user adjusts / corrects the selection of the control device).

[0193] After the control device has been claimed, a join procedure may be executed to join the control device to the network. Figure 4C FIG. 435 is a flowchart of an exemplary method that may be executed during the join procedure. For example, method 435 may be executed during the join procedure shown at 412 of method 400 shown in Figure 4A FIG. The join procedure may be used to join the control device to the network such that the control device can be controlled via commands sent over the network.

[0194] The join procedure may be executed immediately after the claim procedure, or there may be a certain time period between the execution of the two procedures. The claiming of the devices may also be performed by different users and / or devices, and the claimed devices may be batched together for joining the network using the join procedure. Performing the claim and join procedures in this manner may have advantages compared to, for example, claiming and joining each control device individually and then proceeding to the next control device. For example, one or more control devices may be claimed while the network device and / or system controller is operating in an offline mode. The control device may be joined to the network when the network device and / or system controller is no longer operating in the offline mode.

[0195] The system controller may send a join request message to request that a control device (e.g., a lighting control device associated with a lighting fixture) join the network. In a larger installation with a greater number of control devices attempting to join the network simultaneously, the system controller may receive multiple response messages from the terminal devices that receive the join request message. The greater the number of devices that receive the join request message, the greater the number of response messages the system controller may receive and the higher the likelihood of trouble when processing one or more of the received responses. Additionally, the greater the number of response messages communicated, the greater the likelihood of completely preventing conflicts in the responses received by the system controller.

[0196] Method 435 may begin at 436. At 438, the system controller and / or the debugging party device may select a subset of control devices (e.g., lighting control devices that control a subset of lighting fixtures) to couple to the network. The subset may be selected to reduce the number of response messages communicated and / or received. The system controller may select the subset based on a random selection. For example, the system controller may create a list of each control device within the area or retrieve the list from memory. The system controller may randomly select control devices from the list of control devices and add them to the subset list. The system controller may randomly select the control devices to add to the subset list (e.g., rather than adding control devices by area, type, function, etc.) in order to increase the chance that at least one control device on the subset list is within range of the system controller (e.g., and thus able to receive the coupling party request transmitted by the system controller). The system controller may continue to randomly select control devices until the subset list has reached a predetermined size (e.g., 20) or a predetermined percentage of the number of control devices in the list. The predetermined size of the subset list may be determined based on, for example, the number of control devices within the area.

[0197] Using a random subset of control devices may reduce conflicts between transmissions. For example, reducing conflicts may be useful when there are a large number of control devices performing a coupling procedure (e.g., dozens or hundreds of control devices). There may be a relatively large number of control devices (e.g., up to 200 control devices in the network), and each control device (e.g., or a relatively large set of them) may attempt to couple simultaneously when it is powered on or receives power. This may cause conflicts between messages, and due to the receipt of additional messages at the system controller, the processing of these messages may delay the processing of previously received messages. For example, a system controller that sends a single coupling party request to each of the control devices within a given area may cause delays due to the system controller having to process too many messages simultaneously. Additionally, there may be multiple system controllers sending coupling party requests, which may increase the probability of conflicts between two transmissions. One or more devices may be outside the range of the system controller, and the system controller may waste power and / or time resources in an attempt to contact these devices. Using Method 435 to couple control devices to the network may limit the number of devices attempting to couple at a given moment in order to increase the chance that the devices can successfully couple to the network.

[0198] As the size of the subset list decreases, the chance that each of the devices on the subset list is outside the range of the system controller may increase. Thus, the size of the subset list may be selected such that the probability that at least one device on the subset list is within the range of the system controller is relatively high. For example, the size of the subset list may be selected to balance conflict reduction with probability increase. Once a device has coupled to the network, it may be used to couple other devices to the network. For example, a device that has coupled to the network may be used as a repeater.

[0199] When adding a control device to the subset list, the system controller may indicate that the control device has been added to the subset list. For example, the system controller may update the list of control devices to indicate that the control device has been added to the subset list. The system controller may create a separate list that contains the device identification data of the control devices that have been added to the subset list.

[0200] At 440, the system controller may transmit a join party request message to a selected subset of control devices. For example, the system controller may send a message (e.g., via one or more wireless signals) to the lighting control devices that control a selected subset of lighting fixtures. The join party request message may include, for example, the device identification data of each lighting fixture in the subset. The system controller may broadcast the join party request message such that the join party request message can be received by each of the control devices (e.g., lighting control devices) in the area. A control device that receives the join party request message may determine whether to respond to the join party request message based on whether the join party request message includes the device identification data of the control device. For example, if the join party request message does not include the device identification data of the control device, the control device may ignore the join party request message.

[0201] Upon receiving the join party request message, each control device (e.g., each lighting control device that controls one of the selected subset of lighting fixtures) may transmit a response message to the system controller. The control device may transmit the response message via one or more wireless signals. The response message may include, for example, an indication of receiving the join party request message. The system controller may monitor for responses after transmitting the join party request message. At 442, the system controller may determine whether the system controller has received at least one response message. If the system controller has received at least one response message from a control device that has not been joined to the network, then at 444, the system controller may join the control device to the network. Once the system controller has joined the control device to the network, the system controller may ignore other response messages to the join party request message from the control device, and / or transmit an indication message indicating that the control device has been joined to the network to the control device. The system controller may add the control device to the list of control devices that have been joined to the network. Upon receiving the indication message, the control device may stop transmitting response messages to the join party request message. After the system controller has joined the control device to the network, method 435 may return to 442. The system controller may repeat 444 until the system controller does not receive any response messages to the join party request message.

[0202] If the system controller determines at 442 that a response message has not been received, it may determine at 446 whether a timeout has occurred. For example, the system controller may monitor for a response message to the join request message for a predetermined amount of time. If the system controller receives a response message within the predetermined amount of time, the system controller may determine that a timeout has not occurred, and method 435 may return to 442. If the system controller does not receive a response message within the predetermined amount of time, or receives a response message from a lighting control device that has already joined the network, the system controller may determine that a timeout has occurred, and method 435 may proceed to 448.

[0203] At 448, a determination may be made as to whether each of the control devices has joined the network. The system controller and / or processing device may determine whether each device has joined the network based on a list of each of the control devices in the area. When a device joins the network, the system controller and / or processing device may remove the device from the list of each of the control devices in the area. For example, if each of the control devices in the area has been removed from the list, the system controller and / or processing device may determine that each control device has joined the network.

[0204] If it is determined that additional control devices are to join the network, method 435 may return to 438, and the system controller may randomly select another subset list (e.g., not including control devices that have already joined the network) from the list of each of the control devices in the area. The system controller may continue to join devices until each control device has joined the network. If the system controller determines that each of the control devices has joined the network, method 435 may end.

[0205] When the system controller has access to the Internet, the system controller may be able to join each control device one at a time (e.g., because the system controller may access information for the join procedure while debugging is occurring). Performing the solicitation and / or joining while having access to the Internet may allow information to go from the control device to the network device and from the network device to the system controller (e.g., via the cloud) to join the network. In performing an online debugging procedure, the device closest to the system controller may be debugged first, and the network may be expanded as the network grows away from the system controller. Performing the debugging procedure in this way may be restrictive in terms of how devices are added to the network. For example, control devices closer to the system controller may be debugged, and then control devices farther from the system controller may be debugged because the farther devices may not be able to communicate directly with the system controller (e.g., they are too far away), or because there may not be a path to the system controller (e.g., there are no other mesh devices within range).

[0206] Figure 4D and Figure 4Eis a system flow diagram depicting an exemplary message flow for discovering control devices in a load control system. For example, control devices can be discovered to enable configuration (e.g., claiming, diagnosing, associating, etc.) and / or control of the control devices. For example, Figure 4D and Figure 4E the depicted system flow diagram can depict RF messages communicated between control devices executing Figure 6A the method 600 shown and / or Figure 6B the method 650 shown. As Figure 4D shown, a network device (e.g., a mobile device) can communicate directly with one or more control devices (e.g., lighting control devices). For example, the network device and the control device communicate via a wireless connection. Alternatively, as Figure 4E shown, the network device can communicate with the control device via a system controller. For example, the network device can communicate with the system controller via a wireless connection, and the system controller can communicate with the control device via a wired connection. Although Figure 4D and Figure 4E show lighting control devices, other control devices can be used.

[0207] Figure 4D is a system flow diagram depicting an exemplary message flow for discovering control devices in a load control system. For example, control devices can be discovered to enable configuration (e.g., claiming, diagnosing, associating, etc.) and / or control of the control devices. As Figure 4D shown, the load control system can include a mobile device 1602 and lighting fixtures 1604a, 1604b. The lighting fixtures 1604a, 1604b can include corresponding load control devices configured to control corresponding lighting loads. The lighting control devices in the lighting fixtures 1604a, 1604b can be RF-capable devices including communication circuitry capable of communicating messages via RF signals. The lighting control device in the lighting fixture 1604a can communicate with a sensor 1605a capable of detecting visible light communication. The lighting control device in the lighting fixture 1604b can communicate with a sensor 1605b capable of detecting visible light communication. The sensors 1605a, 1605b can be occupancy sensors, visible light sensors (e.g., cameras), daylight sensors, optical sensors, and / or any other type of sensor.

[0208] As Figure 4D shown, the mobile device 1602 can transmit a configuration mode message 1606 to the lighting fixtures 1604a, 1604b. The configuration mode message 1606 can indicate that the lighting control devices of the lighting fixtures 1604a, 1604b should enter a configuration mode (e.g., a claiming mode and / or an associating mode). The configuration mode message 1606 can be via an RF communication signal (e.g., It is transmitted by a low-power (BLE) signal) and / or an optical signal. The configuration mode message 1606 can be sent as a multicast message (e.g., a beacon message), which is received by the lighting control devices of the lighting fixtures 1604a, 1604b. The lighting fixtures 1604a, 1604b can enter the configuration mode without receiving the configuration mode message 1606.

[0209] After transmitting the configuration mode message 1606, the mobile device 1602 can perform discovery of the lighting control devices in the lighting fixtures 1604a, 1604b. The lighting control devices in the lighting fixtures 1604a, 1604b can be discovered by sending a discovery request message 1608 from the mobile device. The discovery request message 1608 can be transmitted to identify the lighting control device to be solicited for joining the network.

[0210] The discovery request message 1608 can be transmitted in an RF signal (such as an RF beacon, e.g., a BLE signal) transmitted from the mobile device 1602. The discovery request message 1608 can be transmitted as an optical signal, which can be transmitted to discover the lighting control devices of the lighting fixtures 1604a, 1604b. The optical signal can be transmitted (e.g., from the mobile device 1602 or another device with an optical transmitter) and identified by the sensors 1605a, 1605b of the lighting fixtures 1604a, 1604b. The lighting fixture 1604a and / or the lighting fixture 1604b can include one or more light sources (e.g., LED lights). Each light source can have a separate sensor (e.g., a detector), which can be used to measure, for example, the optical signal, the baseline ambient light level at the light source, etc. The optical transmitter can be attached to, connected to, and / or integrated into the mobile device 1602. The sensors 1605a, 1605b can communicate with the load control devices of the lighting fixtures 1604a, 1604b (e.g., via wired or wireless communication). The sensors 1605a, 1605b can provide an indication to the lighting control devices of the lighting fixtures 1604a, 1604b that the optical signal has been identified (e.g., at or above a predefined threshold). The optical signal can include light at one or more visible wavelengths. The optical signal can be received, where the optical signal has different signal intensities (e.g., brightness) at each of the sensors 1605a, 1605b. The control circuit in the sensors 1605a, 1605b or the lighting control device can determine the corresponding signal intensities at which the optical signal is received.

[0211] The lighting control device 1604a and / or the lighting control device 1604b may provide a first feedback type indicating that the lighting control device has received and / or detected the request message 1608. The feedback may be provided by causing the lighting load to flash on and off; increasing and / or decreasing the brightness level of the lighting load; increasing and / or decreasing the color temperature of the lighting load; causing the lighting load to illuminate a predefined color (e.g., orange); causing the lighting load to illuminate a predefined color temperature; and / or providing other visual feedback to the user.

[0212] The mobile device 1602 may receive discovery response messages 1610a, 1610b from the lighting control devices of the lighting fixtures 1604a, 1604b. The discovery response messages 1610a, 1610b may include the signal strengths at which the discovery request messages 1608 were received at the lighting fixtures 1604a, 1604b, respectively. As Figure 4D shown, the mobile device 1602 may receive separate message discovery response messages 1610a, 1610b from each of the lighting control devices of the lighting fixtures 1604a, 1604b indicating the signal strengths at which the discovery request messages 1608 were received at the corresponding lighting fixtures 1605a, 1604b. For example, when the discovery request message 1608 is transmitted in an optical signal, the discovery response messages 1610a, 1610b may include the corresponding signal strengths (e.g., brightness) at which the optical signal was received. When the discovery request message 1608 is transmitted in an RF signal, the discovery response messages 1610a, 1610b may include the corresponding RSSI values at which the discovery request message 1608 was received. The signal strength may be indicated as an absolute value (e.g., in lux) and / or a relative value in the discovery response messages 1610a, 1610b. The discovery response messages 1610a, 1610b may include the corresponding identifiers of the lighting fixtures 1604a, 1604b and / or the baseline ambient light level.

[0213] Although the discovery response messages 1610a, 1610b may be transmitted as a response to the discovery request message 1608, the lighting control devices in the lighting fixtures 1604a, 1604b may transmit the discovery response messages 1610a, 1610b as corresponding beacon messages for discovery (e.g., in response to entering a configuration mode) at the mobile device 1602. The mobile device 1602 may determine the signal strengths at which different discovery response messages 1610a, 1610b are received to determine the lighting control device associated with the strongest beacon.

[0214] Based on the discovery response messages 1610a, 1610b, the mobile device 1602 can determine which of the lighting control devices in the lighting fixtures 1604a, 1604b is selected for solicitation to join the network. The discovery response messages 1610a, 1610b associated with the strongest signal strength can be selected for solicitation to join the network. For example, based on the discovery response messages 1610a, 1610b, the mobile device 1602 can determine which of the lighting fixtures 1604a, 1604b received the discovery request message 1608 at the highest signal strength (e.g., when the discovery request message 1608 is an optical signal). For example, the mobile device 1602 can compare the signal strengths indicated in the discovery response messages 1610a, 1610b to identify the lighting fixtures 1604a, 1604b that received the discovery request message 1608 at the highest signal strength. The mobile device 1602 can determine the normalized signal strength of the lighting fixture based on the baseline ambient light level and signal strength at the lighting fixture, and can identify the lighting fixtures 1604a, 1604b that received the discovery request message 1608 at the highest normalized signal strength. Additionally, based on the discovery response messages 1610a, 1610b, the mobile device 1602 can determine the signal strengths at which different discovery response messages 1610a, 1610b were received to determine the lighting control device associated with the strongest signal strength (e.g., when the discovery request message 1608 is a BLE signal). For example, the mobile device 1602 can compare the signal strengths of the discovery response messages 1610a, 1610b to identify the lighting fixtures 1604a, 1604b associated with the highest signal strength.

[0215] As Figure 4D shown, the mobile device 1602 can determine that the lighting control device of the lighting fixture 1604a is receiving the discovery request message 1608 at the highest signal strength, or that the mobile device 1602 is receiving a beacon signal from the lighting control device of the lighting fixture 1604a at the highest signal strength. The mobile device 1602 can select the lighting control device 1604a for configuration (e.g., solicitation and / or association). The mobile device 1602 can establish a connection 1612 (e.g., a two-way connection) with the lighting control device of the lighting fixture 1604a. The connection can be a BLE connection. The connection 1612 can be established by the mobile device 1602 and the lighting control device of the lighting fixture 1604a exchanging credentials for creating a secure connection for secure communication using the credentials. The connection message 1612 can indicate to the lighting control device of the lighting fixture 1604a that the lighting control device is selected for configuration (e.g., solicitation and / or association). Alternatively, the mobile device can communicate with the lighting fixture 1604 without creating a connection.

[0216] The lighting control device 1604a can provide a second feedback type indicating that the lighting control device 1640a has been selected for configuration. For example, the lighting control device 1604a can provide the second feedback type in response to the establishment of a connection 1612 between the lighting control device 1604a and the mobile device 1602. The feedback can be provided by causing the lighting load to flash on and off; increasing and / or decreasing the brightness level of the lighting load; increasing and / or decreasing the color temperature of the lighting load; causing the lighting load to illuminate a predefined color (e.g., blue); causing the lighting load to illuminate a predefined color temperature; and / or providing other visual feedback to the user.

[0217] After establishing the connection 1612 with the lighting control device of the lighting fixture 1604a, the mobile device 1602 can associate the lighting fixture with configuration data. The mobile device can receive an acknowledgment that the lighting control device of the lighting fixture 1604a has received the connection message 1612 and / or a unique identifier (e.g., a configuration identifier) for the selected lighting control device of the lighting fixture 1604a. The mobile device 1602 can associate the lighting control device of the lighting fixture 1604a with the unique identifier and can transmit a configuration message 1616 to the lighting fixture 1604a. The configuration message 1616 can indicate that the lighting fixture 1604a has been requested and / or associated with the selected configuration identifier. The configuration message 1616 can include, for example, an indication that the lighting control device 1604a has been requested, the unique identifier of the mobile device 1602 (e.g., an application running on the mobile device 1602), and / or other association information. The configuration message 1616 can be used as part of a configuration procedure (e.g., a request procedure, an association procedure, a diagnostic procedure, etc.). Control messages can also or alternatively be sent at 1616, the control messages including control instructions for the lighting control device of the lighting fixture. The mobile device 1602 can receive an acknowledgment message 1618 from the lighting control device 1604a. For example, the acknowledgment message 1618 can confirm that the lighting control device 1604a has received the configuration message 1616. The connection message 1612, the configuration message 1616, and / or the acknowledgment message 1618 can be transmitted and / or received via an RF communication signal.

[0218] The lighting control device 1604a can provide a third feedback type indicating that the lighting control device has received the configuration message 1616. The feedback can be provided by causing the lighting load to flash on and off; increasing and / or decreasing the brightness level of the lighting load; increasing and / or decreasing the color temperature of the lighting load; causing the lighting load to illuminate a predefined color (e.g., green); causing the lighting load to illuminate a predefined color temperature; and / or providing other visual feedback to the user.

[0219] As Figure 4D shown, the mobile device 1602 can, for example, via an RF communication signal (e.g., The low-power (BLE) signal communicates directly with the lighting control devices 1604a and 1604b. Figure 4E illustrates an example similar to the Figure 4D example shown. In Figure 4E , the mobile device 1602 can communicate with the lighting control devices 1604a and 1604b via the system controller 1650 (which can act as a repeater) to convey one or more messages between the mobile device 1602 and the lighting control devices 1604a and 1604b. For example, as Figure 4E shown, the mobile device 1602 can send one or more messages to the system controller 1650 (e.g., via an RF communication signal). The system controller 1650 can send one or more messages to and / or receive one or more messages from the lighting control devices 1604a and 1604b (e.g., via a wired or wireless connection). The system controller 1650 can forward the messages received from the lighting control devices 1604a and 1604b to the mobile device 1602. When the mobile device 1602 communicates with the system controller 1650 for RF communication, the Figure 4E example shown can be used. For example, the lighting control devices 1604a and 1604b may not be able to send or receive messages via the RF communication signal.

[0220] Figure 4E is a system flow chart depicting an exemplary message flow for discovering control devices in a load control system. For example, control devices can be discovered to enable solicitation, diagnosis, configuration, control, and / or association of the control devices. As Figure 4E shown, the load control system can include a mobile device 1652, a system controller 1650, and lighting control devices 1654a, 1654b. The lighting control devices 1654a, 1654b can control corresponding lighting loads. For example, the mobile device can communicate with the lighting control devices 1654a, 1654b via the system controller.

[0221] As Figure 4E shown, the mobile device 1652 can transmit a configuration mode message 1656 to the system controller 1650. The configuration mode message 1656 can be similar to Figure 4DThe configuration mode message 1606 shown. The configuration mode message 1656 may indicate that the lighting control devices 1654a, 1654b should enter a configuration mode (e.g., a solicitation mode and / or an association mode). The system controller 1650 may send the configuration mode message 1656 to the lighting control devices 1654 and 1654b (e.g., via a wired or wireless connection), or the system controller may send separate configuration mode messages 1657a, 1657b indicating that the lighting control devices 1654a, 1654b should enter a configuration mode to the lighting control devices 1654a and 1654b. The configuration mode message 1656 may be transmitted via an RF communication signal (e.g., a low power (BLE) signal, a WiFi signal, and / or a cellular signal). The configuration mode message 1656 may be sent as a broadcast message (e.g., a beacon), a multicast message, and / or a separate unicast message. The lighting fixtures 1604a, 1604b may enter a configuration mode without receiving the configuration mode message 1656 (e.g., or separate configuration mode messages 1657a, 1657b).

[0222] After transmitting the configuration mode message 1656, the mobile device 1652 may transmit a discovery request message 1608 (e.g., an optical signal) to the lighting control devices 1654a, 1654b. The discovery request message 1608 may be an optical signal. The lighting control devices 1654a and 1654b may receive the discovery request message 1608 via sensors 1655a, 1655b. The sensors 1605a, 1605b may be occupancy sensors, visible light sensors (e.g., cameras), daylight sensors, optical sensors, and / or any other type of sensor. The lighting fixture 1604a and / or the lighting fixture 1604b may include one or more light sources (e.g., LED lights). Each light source may have a separate sensor (e.g., a detector) that may be used to measure, for example, an optical signal, a baseline ambient light level at the light source, etc. The lighting control devices 1654a, 1654b may determine the respective signal strengths (e.g., brightness) of the discovery request message 1608. The lighting control devices 1654a and 1654b may send discovery response messages 1659a and 1659b to the system controller 1650, respectively. The discovery response messages 1659a and 1659b may be similar to Figure 4D the discovery response messages 1610a and 1610b shown. The discovery response messages 1659a and 1659b may include the signal strengths of the discovery request message 1608 received at the lighting control devices 1654a and 1654b, respectively. The signal strengths may be indicated as absolute values (e.g., in lux) and / or relative values in the discovery response messages 1659a and 1659b.

[0223] The lighting control device 1654a and / or the lighting control device 1654b may provide a first feedback type indicating that the lighting control device has received the configuration mode message 1656 and / or the discovery request message 1608. The feedback may be provided by causing the lighting load to flash on and off; increasing and / or decreasing the brightness level of the lighting load; increasing and / or decreasing the color temperature of the lighting load; causing the lighting load to illuminate a predefined color (e.g., orange); causing the lighting load to illuminate a predefined color temperature; and / or providing other visual feedback to the user.

[0224] The system controller 1650 may receive the discovery response messages 1659a and 1659b from the lighting control devices 1654a and 1654b, respectively, and may send the combined discovery response message 1660 to the mobile device 1652. The combined discovery response message 1660 may include the signal strength of the discovery request message 1608 at multiple lighting control devices. Alternatively, the system controller 1650 may forward the discovery response messages 1659a and 1659b to the mobile device 1652. The signal strength may be indicated as an absolute value (e.g., in lux) and / or a relative value in the combined discovery response message 1660.

[0225] Based on the combined discovery response message 1660 and / or the discovery response messages 1659a and 1659b, the mobile device 1652 may determine which of the lighting control devices 1654a and 1654b is receiving the discovery request message 1608 at the highest normalized signal strength. For example, the mobile device 1652 may determine the normalized signal strength by comparing the signal strength indicated in the combined discovery response message 1660 with the baseline ambient light level recorded by the mobile device 1652, the system controller 1650, the lighting control device 1654a, and / or the lighting control device 1654b. As Figure 4E shown, the mobile device may determine that the lighting control device 1654a is receiving the discovery request message 1608 at the highest normalized signal strength.

[0226] Alternatively, the discovery request message 1608 may not be transmitted, and the lighting control devices 1654a, 1654b may transmit discovery response messages 1659a, 1659b after receiving an acknowledgement mode message 1656 (e.g., without receiving the discovery request message 1608). The lighting fixtures 1654a, 1654b may transmit the discovery response messages 1659a, 1659b as respective beacons (e.g., control device beacons). For example, the discovery response messages 1659a, 1659b may be RF signals (e.g., BLE signals). The discovery response messages 1659a, 1659b may include respective identifiers of the lighting fixtures 1654a, 1654b. The lighting fixtures 1654a, 1654b may broadcast the discovery response messages 1659a, 1659b. The mobile device 1652 may receive the discovery response messages 1659a, 1659b and may measure the respective received signal strength indicators (RSSIs) of the discovery response messages 1659a, 1659b. The mobile device 1652 may select a lighting fixture for configuration and / or control based on the RSSI. For example, the mobile device 1652 may select the lighting fixture that transmits the discovery response message with the highest RSSI for configuration and / or control.

[0227] The mobile device may select the lighting control device 1654a for configuration (e.g., claim and / or associate). The mobile device 1652 may send a selection message 1662 to the system controller 1650. The selection message 1662 may indicate to the system controller 1650 and / or the lighting control device 1654a that the lighting control device 1654a is selected for configuration and / or control. The system controller 1650 may forward the selection message 1662 to the lighting control device 1654a, or the system controller 1650 may send a separate selection message to the lighting control device 1654a.

[0228] The lighting control device 1654a may provide a second type of feedback indicating that the lighting fixture 1654a has received the selection message 1662 from the mobile device 1652 via the system controller 1650. The feedback may be provided by causing the lighting load to blink on and off; increasing and / or decreasing the brightness level of the lighting load; increasing and / or decreasing the color temperature of the lighting load; causing the lighting load to illuminate a predefined color (e.g., blue); causing the lighting load to illuminate a predefined color temperature; and / or providing other visual feedback to the user.

[0229] Upon receiving the association message 1664, the mobile device 1652 may associate the lighting control device 1654a with a unique identifier and may transmit a configuration message 1666 to the system controller 1650. The configuration message 1666 may include, for example, an indication that the lighting control device 1654a has been claimed, the unique identifier of the mobile device 1652 (e.g., an application running on the mobile device 1652), and / or other association information. The configuration message 1666 may be used as part of a configuration program (e.g., a claiming program, an association program, a diagnostic program, etc.) and / or part of a control program. The system controller 1650 may forward the configuration message 1666 to the lighting control device 1654a, or the system controller 1650 may send a separate configuration message 1667 to the lighting control device 1654a.

[0230] The lighting control device 1654a may provide a third type of feedback indicating that the lighting control device has received the configuration message 1666. The feedback may be provided by causing the lighting load to flash on and off; increasing and / or decreasing the brightness level of the lighting load; increasing and / or decreasing the color temperature of the lighting load; causing the lighting load to illuminate a predefined color (e.g., green); causing the lighting load to illuminate a predefined color temperature; and / or providing other visual feedback to the user.

[0231] After receiving the configuration message 1666, the lighting control device 1654a may transmit an acknowledgement message 1668 to the system controller 1650. For example, the acknowledgement message 1668 may confirm that the lighting control device 1654a has received the configuration message 1666. The system controller 1650 may forward the acknowledgement message 1668 to the mobile device 1652, or the system controller 1650 may send a separate acknowledgement message to the mobile device 1652. The selection message 1662, the association message 1664, the configuration message 1666, and / or the acknowledgement message 1618 may be transmitted and / or received via an RF communication signal and / or via a wired connection.

[0232] Figures 5A to 5JExemplary screenshots of a user interface 500 for implementing the configuration (e.g., solicitation and / or association) of lighting control devices in a load control system (e.g., load control system 100) are illustrated. The user interface 500 may be displayed on a network device such as a mobile device (e.g., mobile devices 150, 250, 350). For example, the mobile device may display the user interface 500 during a configuration data transfer program (e.g., as executed at 406 of method 400) and / or a configuration program (e.g., a solicitation program and / or an association program as executed at 408 of method 400). The mobile device may locally execute an application program for displaying the user interface 500. Additionally, a remote computing device (e.g., system controllers 140, 240, 340 and / or cloud server 370) may generate the user interface 5000 for display on the mobile device via a local application (e.g., a browser or other application).

[0233] As Figure 5A shown, the user may type a project code into the project code box 502 on the mobile device to access configuration data of a configuration database (e.g., a lighting control database) of a project. The project code may be used to identify a project that has been created by design software executable on a processing device (e.g., as executed by the processing device at 404 of method 400). The project code may be used to retrieve the configuration database of the project that has been created. The project may be a predefined project that is locally accessible and / or accessible from a remote data source (e.g., cloud server 370). The mobile device may retrieve the control database of the project indicated by the project code in response to the user selecting the "Type Project" button 504. The mobile device may utilize the project code to access lighting control configuration information stored in the control database to configure and / or control lighting control devices in the load control system.

[0234] The configuration data (e.g., lighting control configuration information) may include configuration identifiers (e.g., luminaires, groups, areas, zones, and / or locations) to which control devices may be assigned for implementing control (e.g., collective control) during normal operation. As Figure 5B shown, after typing the project code and accessing the configuration data, the user may select one of the areas 506 for configuration within the load control environment. The areas 506 may be retrieved from the control database of the project. The areas 506 may be identified by a building, floor, room, or other area identifier. The areas 506 may be partitioned by sub-areas. The user interface 500 may indicate the number 508 of lighting control devices within each area 506 and / or the number 509 of lighting control devices within the project (e.g., as determined according to the control database). The user interface may indicate the number of lighting control devices that have been assigned (e.g., already assigned) to an area and / or otherwise configured within each area.

[0235] A configuration database (e.g., of the defined area 506 and / or the lighting control device) may be pre-defined and / or defined within the application that executes the user interface 500. For example, the configuration database may be pre-defined using design software, which may be used to configure the building design and / or the number of luminaires in each area of the building design (e.g., at 404 of method 400). The design software may store a configuration identifier (e.g., the name of the area 506 and / or the lighting control device) together with a project code for accessing the project on the mobile device in the configuration database of the project. The name of each of the lighting control devices 508 may be stored in the control database of the project together with a unique identifier and / or a beacon identifier that can be emitted by the lighting control device.

[0236] Now referring to Figure 5C , the user may select the area 506a for configuration. The type 510 of lighting control device that can be configured in the area 506a may be displayed to the user. The user may select one of the lighting control device types 510 to begin configuration in the load control system. For example, the lighting control device types 510 may include floodlights (e.g., light bulbs and / or downlights) and linear lights (e.g., elongated luminaires). Although some lighting control device types 510 are provided as examples, other lighting control device types may be configured similarly. Additionally, although lighting control devices are provided as exemplary devices, other control devices may be configured similarly as described herein.

[0237] After the user selects one of the lighting control devices 510 for configuration, the mobile device may begin a discovery procedure to identify the selected lighting control device type. As Figure 5D shown, the lighting control device 510a (e.g., which may be a floodlight) may be selected for discovery and / or for configuration and / or control. For example, the mobile device may enter a configuration mode (e.g., a solicitation mode and / or an association mode) and begin to transmit (e.g., periodically transmit) a mobile device beacon via a short-range wireless communication link (e.g., using BLE technology). Additionally, the lighting control device may begin to periodically transmit a control device beacon in response to power-on, in response to detecting actuation of a button, and / or in response to receiving a message. In one example, the mobile device may send a message that causes the lighting control device 510a to begin transmitting a control device beacon (e.g., directly to the selected lighting control device 510a or via the system controller).

[0238] Those lighting control devices (e.g., floodlights) that receive the mobile device beacon and are within the discovery range of the mobile device can enter a configuration mode (e.g., a solicitation mode and / or an association mode) and start transmitting (e.g., transmitting periodically) corresponding control device beacons. The lighting control devices within the discovery range of the mobile device can also provide feedback to the user. For example, the feedback can be to change the lighting load of the discovered lighting control device to a first color (e.g., orange). This feedback can indicate to the user the lighting control devices that have been discovered and / or are ready to be solicited. The user can move the mobile device to discover different lighting control devices in the area. Additionally, the mobile device can send a message to the discovered lighting control device to cause the lighting control device to provide feedback to the user.

[0239] The mobile device can receive the control device beacon transmitted by the lighting control device. The user interface 500 can indicate the lighting control devices that have been discovered and / or selected by the mobile device for solicitation and / or association with a configuration identifier. As described herein, the discovered lighting control devices can include the control devices that receive the mobile device beacon (e.g., within the discovery range of the mobile device) at a received signal strength discovery threshold higher than a certain value. The user interface can indicate the lighting control devices that have been assigned to a configuration identifier and / or otherwise configured in the load control system. The mobile device can retrieve this information by performing a lookup in the configuration data using the beacon identifier received in the control device beacon from the discovered lighting control device.

[0240] Now referring to Figure 5E , the mobile device can identify the lighting control devices within the discovered lighting control devices for solicitation and / or association with a configuration identifier. The user interface can indicate that the lighting control devices have been identified. The user interface can display a graphical representation 512 of the lighting control device, and the graphical representation 512 indicates the device type and / or feedback type of the identified lighting control device. The lighting control device with the strongest received signal strength indicator of the control device beacon received by the mobile device can be automatically selected as the lighting control device for solicitation and / or association. In response to the actuation of the next button 514, the lighting control device with the next strongest received signal strength indicator can be selected as the lighting control device for solicitation and / or association. In response to the actuation of the previous button 516, the previously selected lighting control device can be selected again as the lighting control device for solicitation and / or association. Additionally, the mobile device can also or alternatively identify the lighting control device for solicitation and / or association based on the user's selection from the list of lighting control devices displayed on the user interface 500.

[0241] A mobile device may send a message configured to cause an identified lighting control device for claiming and / or association to provide another type of feedback. For example, the feedback may be to change the lighting load to a second color (e.g., blue). Different types of feedback may allow a user to distinguish the claimed and / or associated lighting control device from other lighting control devices (e.g., other discovered lighting control devices that are of a first color). To cause the lighting control device to change the provided feedback, the mobile device may transmit (e.g., directly transmit) a message that includes the beacon identifier of the identified lighting control device for claiming and / or association. For example, the message may be a connection message that initiates the establishment of a connection (e.g., a two-way communication connection) between the mobile device and the lighting control device. The lighting control device that identifies its beacon identifier in the message may establish a connection with the mobile device and change the provided feedback type. In another example, the system controller may receive the message and may communicate with the identified lighting control device to cause the lighting control device to change the provided feedback type.

[0242] The user may assign a lighting control device to a region by selecting the region assignment button 518. Selection of the region assignment button 518 may allow the user to assign the lighting control device to one of a plurality of regions 520, as Figure 5F shown. The region 520 may be a predefined region in the area 506a. For example, the region 520 and / or the area 506a may be predefined in a configuration database using design software. The region 520 and / or the area 506a may also or alternatively be defined in the user interface 500 upon claiming and / or association. The user interface 500 may indicate the number 522 of predefined lighting control devices that can be assigned to each region 520 and the number of lighting control devices that have been assigned to each region 520.

[0243] The user interface 500 may display an assignment button 524 that may allow the user to assign the identified lighting control device to the corresponding region 520. Each of the regions 520 may have a corresponding assignment button 524 for assigning the identified lighting control device to the corresponding region.

[0244] After each of the identified lighting control devices is assigned to an area 520, the lighting control device may transmit device identification data to the network device. The device identification data may include, for example, an address (e.g., a Thread network address), a joining party ID, and / or any other kind of device identification data. After receiving the device identification data from the lighting control device, the network device may store the device identification in a memory. The network device may transmit configuration information to the lighting control device. For example, the configuration data may include a timestamp, a network device identifier / application identifier, and / or channel information (e.g., which may assist the lighting control device in joining the correct Thread network). The network device may store the device identification data in a memory. The network device may display on a user interface a notification (not shown) notifying the user that the network device has received the device identification data.

[0245] The network device may transmit configuration data to the lighting control device. For example, the configuration data may include a timestamp, a network device identifier / application identifier, and / or channel information (e.g., which may assist the lighting control device in joining the correct Thread network). The configuration data may be transmitted via an RF communication signal. The lighting control device may indicate that it has received the configuration data by causing a corresponding lighting fixture to turn into a predefined color (e.g., green).

[0246] After selecting the assign button 524, the user may assign the lighting control device to a lighting fixture (e.g., a location) within the area 520. As Figure 5G shown, the selection of the assign button 524 corresponding to one of the areas 520 may allow the user to assign the identified lighting control device to one of the multiple lighting fixtures 526 of the area 520. The user interface 500 may display the selected area 520a to which the identified lighting control device may be assigned. The user interface may also display the number of lighting fixtures 526 within the area 520a to which the lighting control device within the area 520a may be assigned. The number and / or identification of the lighting fixtures 526 within the area 520a may be predefined in the lighting control configuration information or defined in the user interface. Each of the lighting fixtures 526 may correspond to a given location within the area in the lighting control configuration information. For example, each of the lighting fixtures 526 may correspond to a given physical location within the area on a floor plan.

[0247] A lighting control device can be assigned to a given luminaire 526 within area 520a. The lighting control device can be assigned to the given luminaire 526 by a user. For example, the user can select a given luminaire 526 within the area or drag a graphical representation 512 of the lighting control device to the given luminaire 526 within area 520a. The lighting control device can be automatically assigned to a luminaire 526 within area 520a. The luminaire 526 can be automatically and randomly assigned to an unassigned luminaire 526, or can be automatically assigned to the next empty luminaire 526 within area 520a. The user interface can display a trail 528 identifying a series of graphical representations 512 of the lighting control device on the path to the assigned luminaire 526 in area 520a. The mobile device can store area identifiers and / or luminaire identifiers associated with the lighting control device identifier to assign the lighting control device to area 520a and / or the given luminaire 516, respectively.

[0248] After claiming a lighting control device and / or assigning it to one of the luminaires 526 within area 520a, the lighting control device can provide different feedback types to indicate that the lighting control device has been assigned to a luminaire within the area. For example, the mobile device can send a message to the lighting control device (e.g., directly or via a system controller) to indicate that the lighting control device has been claimed and / or assigned to a luminaire within the area. The lighting control device can provide different feedback types in response to the message. For example, the lighting control device can change the color of the lighting load from blue to green. The user interface 500 can illustrate the change in the feedback type provided by the lighting control device.

[0249] After the lighting control device has been assigned to one of the luminaires 526 within area 520a, the mobile device can identify another lighting control device for claiming and / or assigning to area 520a and / or otherwise configuring and / or controlling. As Figure 5HAs shown, the user interface 500 can identify the requested and / or assigned luminaires 526 within area 520a, as well as the unrequested and / or unassigned luminaires 526 within area 520a. The requested and / or assigned luminaires 526 can display a graphical representation that indicates the type of feedback provided by a device (e.g., a green light) that has been requested and / or assigned in area 520a. The user interface can display a graphical representation 512 to indicate that another lighting control device has been identified for being requested and / or assigned to the luminaires 526 within area 520a and / or otherwise configured and / or controlled. The identified lighting control device can be the lighting control device from which the mobile device is receiving the strongest received signal strength indicator of a control device beacon having an unrequested control device. As the user moves the mobile device back and forth around the load control environment, the identified lighting control device can be updated. The mobile device can send a message that causes the lighting control device to provide feedback to the user to indicate the device that has been identified for being requested and / or associated with the luminaire. The feedback can be similar to the type of feedback indicated by the graphical representation 512 displayed in the user interface 500.

[0250] The next identified lighting control device can be requested and / or assigned to the luminaires 526 within area 520a, and the user interface 500 can be updated to reflect the addition of the lighting control device to area 520a, as Figure 5I shown. The user can continue to move back and forth around the load control environment to identify lighting control devices for being requested and / or assigned to area 520a, and request the identified lighting control devices and / or assign the identified lighting control devices to the area, as described herein. After each luminaire 526 in area 520a has been requested and / or assigned, the user can navigate to another area for requesting and / or assigning lighting control devices.

[0251] The user interface can allow the user to unassign a lighting control device from the luminaires 526 in the area and / or from the area. As Figure 5J shown, after the user selects a lighting control device that has been assigned to a luminaire 526 in area 520a, the user interface can display an unassign button 530 that is configured to unassign the selected lighting control device from the luminaire 526 and area 520a. The user can select the unassign button 530 to remove the association of the area identifier and / or luminaire identifier with the lighting control device identifier to unassign the lighting control device from area 520a and / or from the luminaire 526, respectively. A graphical representation 532 can be displayed to indicate the feedback provided by the unassigned luminaire. The feedback can be the same as the feedback provided before the lighting control device was assigned to the luminaire 526 within area 520a.

[0252] When a user assigns lighting control devices to different areas of a load control system, each area may provide different feedback types to distinguish itself from other areas. For example, each area in a room may light up a different color.

[0253] Multiple users may configure (e.g., claim, diagnose, associate, etc.) and / or control the load control system. To prevent multiple users from accessing and configuring the same lighting fixture, a single user may be able to claim a lighting control device at a given time. In response to claiming the control device and / or assigning the control device to a lighting fixture, the mobile device may send an indication to the control device that the control device has been claimed. For example, upon receiving a message indicating that the control device has been claimed, the control device may be claimed. The mobile device may send a user identifier and / or a mobile device identifier to be stored at the control device to indicate the user and / or device that has claimed the control device. When the control device has been claimed by a mobile device, the control device may be non-discoverable and / or prevented from being selected by another mobile device for claiming and / or assigning to a lighting fixture.

[0254] Since the claimed control device may still emit a control device beacon, another mobile device may discover the claimed lighting control device and attempt to select the lighting control device for claiming and / or assigning to a lighting fixture. In response to a confirmation message from the mobile device that the lighting control device has been selected by another mobile device, the lighting control device may send a message indicating that the lighting control device has been claimed. The message may include the user identifier and / or the mobile device identifier of the user and / or device that has claimed the lighting control device. The mobile device of a user attempting to claim a lighting control device that has already been claimed may provide the user with a notification that the lighting control device has been claimed. The notification may include the user identifier and / or the mobile device identifier of the user and / or device that has claimed the lighting control device.

[0255] Each user or mobile device of the debugging system may have different feedback types for lighting control devices that are discovered, selected, identified for claiming and / or allocation, or otherwise configured. For example, each user may have a different color scheme for the devices selected for claiming. Each user may also have a different color for the devices that the user has allocated to a zone or otherwise configured, such that lighting control devices configured by another user can be identified. For example, a lighting control device discovered by the mobile device of a first user may light up with a first color, and a lighting control device discovered by the mobile device of a second user may light up with a second color. The color or other feedback type may be stored at the lighting control device. For example, a lighting control device allocated to a location within a zone may have a user identifier, mobile device identifier, and / or color or other feedback type stored thereon, such that when the lighting control device is discovered by a mobile device, this information can be provided to the mobile device and / or the color or other feedback type can be provided to the user. The user may also or alternatively rename another identifier or store it at the lighting control device, such that another user can identify the lighting control device as having been configured.

[0256] Since each lighting control device may have a device type stored thereon, the user may allocate lighting control devices to zones by device type. The mobile device may identify lighting control devices of different device types among the lighting control devices selected for configuration and / or control. For example, a portion of the lighting control devices may be identified as "downlights", while another portion of the lighting control devices may be identified as "track lights". The mobile device may automatically allocate lighting control devices of the same device type to different zones. The allocation of lighting control devices by device type to zones may be performed in response to the user's actuation of a button on the mobile device. The allocation of lighting control devices by device type to zones may be performed on the unallocated lighting control devices after other lighting control devices have been allocated to zones. The allocation of lighting control devices by device type to zones may be performed for each lighting control device selected for configuration and / or control rather than a single identified lighting control device selected for configuration and / or control.

[0257] Figure 6Ais a flowchart depicting an exemplary method 600 for discovering a control device for implementing a claim for and / or associating with a control device. Method 600 may be executed as part of a configuration program (e.g., a claim program and / or an association program). Method 600 may be implemented by one or more devices. For example, method 600 may be executed by a mobile device (e.g., mobile devices 150, 250, 350) to claim a control device and / or associate a control device with a configuration identifier of configuration data of a load control system (e.g., as performed at 408 of method 400). For example, method 600 may be executed at 602 in response to actuation of a button (e.g., a virtual button or a soft button) on a user interface of the mobile device (e.g., user interface 500).

[0258] At 604, the mobile device may enter a configuration mode (e.g., a claim mode and / or an association mode). At 606, the mobile device may start periodically transmitting a beacon (e.g., a mobile device beacon). The mobile device may be configured to transmit the mobile device beacon via a short-range wireless communication link (e.g., using BLE technology). The mobile device beacon may include, for example, a unique identifier identifying the mobile device (e.g., or an application executed on the mobile device) and / or a received signal strength discovery threshold. When one of the control devices receives the mobile device beacon and the received signal strength indicator of the mobile device beacon is greater than or equal to the received signal strength discovery threshold included in the mobile device beacon (e.g., the control device is within the discovery range of the mobile device), the control device may enter a configuration mode (e.g., a claim mode and / or an association mode) and start transmitting (e.g., periodically transmitting) a beacon (e.g., a control device beacon). The mobile device may adjust the received signal strength discovery threshold included in the mobile device beacon to adjust the discovery range of the mobile device.

[0259] At 608, the mobile device may discover (e.g., receive) a control device beacon transmitted by the control device in response to receiving the mobile device beacon. Each control device beacon may include a unique identifier of the control device transmitting the corresponding beacon. At 610, the mobile device may identify the control device beacon having the strongest received signal strength indicator (RSSI) of the received control device beacon. At 612, the mobile device may transmit a connection message to the control device transmitting the control device beacon identified at 610 (e.g., the control device beacon having the strongest RSSI). For example, in response to the control device receiving the connection message from the mobile device, the mobile device and the control device may be configured to establish a connection (e.g., a two-way communication connection). Additionally, the connection message may indicate to the control device that the control device has been selected for claiming. If the mobile device is unable to establish a connection at 614, method 600 may loop to allow the mobile device to attempt to connect to the same control device or a different control device.

[0260] When the mobile device successfully establishes a connection with the control device at 614, the mobile device can determine at 616 whether an instruction has been received from the user via the user interface of the mobile device (e.g., user interface 500) to associate the control device with one of the configuration identifiers of the configuration data. For example, the mobile device can receive a selection of a configuration identifier (e.g., a lamp, group, area, region, and / or location that can be defined by the configuration data) to associate with the control device to which the mobile device is connected. Additionally, the mobile device can receive a selection of one or more other control devices (e.g., a control source device for associating with a control target device, or a control target device for associating with a control source device) to associate with the control device to which the mobile device is connected. When the mobile device receives an instruction at 616 to associate the control device with one of the configuration identifiers, the mobile device can create an association at 618 between the control device and the selected configuration identifier of the configuration device. To associate the control device with other control devices identified in the configuration identifier, the mobile device can store the configuration identifier of the control device together with the associated configuration identifier in the memory. The associated configuration identifier can be sent from the mobile device to the control device via the connection for storage at the control device. The associated configuration identifier can be locally stored at the control device such that the control device can send messages to and / or receive messages from the associated devices for load control implementation.

[0261] At 620, the mobile device can transmit a configuration message (e.g., a solicitation message, an association message, a diagnostic message, etc.) to the control device to which the mobile device is connected. The configuration message can indicate that the control device has been solicited and / or associated with the selected configuration identifier of the configuration data. In response to receiving the configuration message, the control device can transmit an acknowledgment message (e.g., a solicitation acknowledgment message) to the mobile device. The solicitation acknowledgment message can include the unique identifier (e.g., a serial number) of the control device from which the solicitation acknowledgment message is transmitted. Before sending the solicitation message, the mobile device can check whether the control device has been solicited. If the control device has been solicited, the mobile device can prevent the transmission of additional solicitation messages and proceed to 622.

[0262] If, at 622, the mobile device does not receive a solicitation confirmation message from the control device, method 600 may loop to allow the mobile device to attempt to connect to the same or a different control device. The solicitation confirmation message may include a unique identifier (e.g., serial number) of the control device. When, at 622, the mobile device receives a solicitation confirmation message from the control device to which the mobile device is connected, at 624 the mobile device may store the unique identifier of the control device and associated information (e.g., a configuration identifier associated therewith by the control device) in a memory. The unique identifier stored during the solicitation procedure may be a device that can be joined to the network (e.g., individually or in batches) during the joining procedure. The associated information may be stored to identify the control device associated with the control device being solicited for joining the network.

[0263] If, at 616, the mobile device does not receive an instruction to associate the control device to which the mobile device is connected with one of the configuration identifiers, but at 626 receives an instruction to disassociate the control device from the associated configuration identifier, then at 628 the mobile device may disassociate the control device from the associated configuration identifier and, at 630, delete the unique identifier of the control device and the associated information from the memory. The mobile device may send a message to one or more control devices to remove the association from the memory at the one or more control devices.

[0264] If, at 632, the mobile device does not complete soliciting a control device and / or associating the control device with a configuration identifier of the configuration data, method 600 may loop to allow the mobile device to attempt to connect to a different or the same control device (e.g., if at 626 the control device was not exactly solicited and / or not associated). When, at 632, the mobile device completes soliciting and / or associating a control device (e.g., the user actuates a button on the user interface of the mobile device to end the configuration procedure), at 634 the mobile device may exit the configuration mode and method 600 may end. Additionally, at 634, the mobile device may stop periodically transmitting the mobile device beacon.

[0265] The control device may provide different types of feedback to indicate different information to the user. For example, a lighting control device may provide a feedback type to indicate that the lighting control device has been discovered and / or selected for configuration and / or control (e.g., the control device transmits a beacon received by the mobile device above a discovery threshold). The lighting control device selected for configuration and / or control may blink (e.g., at different frequencies), increase / decrease the brightness level of the lighting load, increase / decrease the color temperature of the lighting load, cause the lighting load to illuminate a predefined color or color temperature, and / or provide another visual feedback to the user via the lighting load.

[0266] The selected lighting control device with the beacon received at the strongest signal strength at the mobile device can provide different feedback types. For example, a lighting control device that transmits a control device beacon with the strongest signal strength received by the mobile device can blink at a different rate than other control devices selected for configuration and / or control, increase / decrease the brightness level of the lighting load at a different rate than other control devices selected for configuration and / or control, increase / decrease the color temperature of the lighting load at a different rate than other control devices selected for configuration and / or control, cause the lighting load to light up with a different color or color temperature than other control devices selected for configuration and / or control, and / or provide other visual feedback to the user to distinguish the lighting control device.

[0267] After the lighting control device has been configured (e.g., assigned to a zone and / or area), the lighting control device can provide different feedback types. For example, a lighting control device that has been assigned to a zone or area in the lighting control configuration information can blink at a different rate than unassigned devices selected for configuration and / or control, increase / decrease the brightness level of the lighting load at a different rate than unassigned devices selected for configuration and / or control, increase / decrease the color temperature of the lighting load at a different rate than unassigned devices selected for configuration and / or control, light up with a different color or color temperature than unassigned devices selected for configuration and / or control, and / or provide other visual feedback to the user to distinguish the assigned lighting control device.

[0268] The feedback types can be pre-programmed at the lighting control device and / or provided to the lighting control device in the information. For example, the feedback types can be provided to the lighting control device in a configuration message in which the lighting control device has been selected for configuration and / or control and / or in another message from a device in the load control system.

[0269] As Figure 6A shown, the mobile device can use a mobile device beacon to trigger a control device (e.g., a lighting control device) to enter a configuration mode. For example, the mobile device can transmit a mobile device beacon via an RF communication signal. Figure 6B illustrates an example similar to the Figure 6A example shown. As Figure 6BAs shown, the mobile device can use an optical signal to trigger the control device to enter the configuration mode. For example, the optical signal can be light at a given wavelength. The optical signal can perform better than an RF beacon, for example, in a location where other RF services may interfere with the transmission of RF beacons to / from the control device. Additionally, the optical signal can have greater accuracy than the beacon. For example, using a directional (e.g., focused) light beam can help determine which one of multiple control devices has been selected for configuration. Using an RF beacon to identify or select a specific control device may be less accurate due to interference and inconsistencies in RF communication. The use of the optical signal can be regardless of whether the control device is already connected to a wireless network, while the beacon may not be received by the control device if the control device is not connected to the wireless network.

[0270] Figure 6B is a flowchart depicting an exemplary method 650 for discovering a control device for the purpose of implementing a claim for and / or association with the control device. Method 650 can be executed as part of a configuration program (e.g., a claim program and / or an association program). Method 650 can be implemented by one or more devices. For example, method 650 can be executed by a mobile device (e.g., mobile devices 150, 250, 350) to claim a control device and / or associate the control device with a configuration identifier of configuration data of a load control system (e.g., as performed at 408 of method 400). For example, method 650 can be executed at 652 in response to the actuation of a button (e.g., a virtual button or a soft button) on a user interface (e.g., user interface 500) of the mobile device.

[0271] At 654, the mobile device can enter the configuration mode (e.g., the claim mode and / or the association mode). At 656, the mobile device can transmit a configuration mode message to the control device. The configuration mode message can include, for example, a unique identifier that identifies the mobile device (e.g., or an application program executed on the mobile device). The configuration mode message can indicate that the control device should enter the discovery mode. The control device can enter the discovery mode in response to the configuration mode message.

[0272] At 658, the mobile device may record the baseline ambient light level in the area in which the control device is located. The area may be, for example, a room in a building. The mobile device may record via a photosensor, a visible light sensor (e.g., a camera), and / or other suitable sensors that may be integrated into and / or connected to the mobile device. Additionally, at 658, the control devices may each record the baseline ambient light level at the respective control device (e.g., using an integrated detector and / or a sensor at the control device) and transmit the baseline ambient light level to the mobile device. At 660, one or more optical signals (e.g., optical signal 109) may be transmitted to the control devices. For example, the mobile device may start transmitting optical signals using an optical transmitter (e.g., optical transmitter 108) that may be connected to the mobile device. Additionally, the optical signals may be transmitted by a laser pointer or a similar device included in or attached to the mobile device. The optical transmitter may also be separate from the mobile device and independently activated by the user. The optical signals may be transmitted at a given wavelength (e.g., which may be between approximately 400 nm and 700 nm). The wavelength at which the optical signals are transmitted may be a predefined wavelength to which the internal detector and / or the sensors of the control device may respond. The optical signals may be transmitted in the direction of aiming at one of the control devices.

[0273] At 662, the mobile device may receive one or more discovery response messages from the control devices. The discovery response messages may indicate that the control devices have received the optical signals. Each discovery response message received from a control device may include the respective optical signal intensity at which the control device received the optical signal. The discovery response messages may be transmitted via RF, for example, using BLE or another RF communication protocol. The discovery response messages may also or alternatively be conveyed from the control devices via the optical signals. For example, a lighting control device may change the brightness and / or color of a lighting load to communicate the discovery response message (e.g., and the optical signal intensity) back to the mobile device. At 664, the mobile device may determine which control device received the optical signal at the highest signal intensity. For example, the mobile device may determine the normalized optical signal intensity of each control device from which the mobile device received a discovery response message at 662. The mobile device may calculate the normalized optical signal intensity of the control device by subtracting the baseline ambient light level from the optical signal intensity received from the control device in the discovery response message, where the baseline ambient light level is the baseline ambient light level recorded by the mobile device at 658 or the baseline ambient light level recorded by the control device at 658 and received by the mobile device. Alternatively, each control device may determine the respective normalized optical signal intensity by subtracting the baseline ambient light level from the optical signal intensity measured by the control device and may transmit an indication of the normalized optical signal intensity to the mobile device. The mobile device may compare the determined normalized optical signal intensities and may determine which control device has the highest normalized optical signal intensity.

[0274] At 666, the mobile device may transmit a connection message to the control device determined at 664 to have the highest normalized optical signal strength. For example, in response to the control device receiving the connection message from the mobile device, the mobile device and the control device may be configured to establish a connection (e.g., a two-way communication connection). The connection may be established by the mobile device and the control device exchanging credentials for creating a secure connection for secure communication using the credentials. The connection message may indicate to the control device that the control device has been selected for solicitation. If the mobile device is unable to establish a connection at 668, method 650 may return to 662 to allow the mobile device to attempt to connect to the same control device or a different control device. The mobile device may receive an additional discovery response message from the control device including the optical signal strength, or use the optical signal strength in a previously received discovery response message. For example, at 664, the mobile device may determine the control device having the next highest normalized optical signal strength and attempt to connect to the control device.

[0275] When the mobile device successfully establishes a connection with the control device at 668, at 670 the mobile device may determine whether an instruction has been received from the user via the user interface of the mobile device (e.g., user interface 500) to associate the control device with one of the configuration identifiers of the configuration data. For example, the mobile device may receive a selection of a configuration identifier (e.g., a lamp, group, area, region, and / or location that may be defined by the configuration data) to associate with the control device to which the mobile device is connected. Additionally, the mobile device may receive a selection of one or more other control devices (e.g., a control source device for associating with a control target device, or a control target device for associating with a control source device) to associate with the control device to which the mobile device is connected. When the mobile device receives an instruction at 670 to associate the control device with one of the configuration identifiers, at 672 the mobile device may create an association between the control device and the selected configuration identifier of the configuration device. To associate the control device with other control devices identified in the configuration identifier, the mobile device may store the configuration identifier of the control device together with the associated configuration identifier in a memory. The associated configuration identifier may be sent from the mobile device to the control device via the connection for storage at the control device. The associated configuration identifier may be stored locally at the control device such that the control device may send messages to and / or receive messages from the associated devices for load control.

[0276] At 674, the mobile device may transmit a configuration message (e.g., a solicitation message, an association message, a diagnostic message, etc.) to a control device to which the mobile device is connected. The configuration message may indicate that the control device has been solicited for attachment to the network. The configuration message may indicate that the control device has been associated with a selected configuration identifier of configuration data. In response to receiving the configuration message, the control device may transmit a solicitation confirmation message to the mobile device. The solicitation confirmation message may include a unique identifier (e.g., a serial number) of the control device from which the solicitation confirmation message is transmitted. Before sending the configuration message, the mobile device may check whether the control device has been solicited. If the control device has been solicited, the mobile device may prevent the transmission of additional configuration messages and proceed to 678.

[0277] If at 676 the mobile device does not receive a solicitation confirmation message from the control device, method 650 may return to 662 to allow the mobile device to attempt to connect to the same control device or a different control device. The mobile device may receive an additional configuration message from the control device that includes an optical signal strength, or use the optical signal strength in a previously received configuration message. For example, at 664 the mobile device may determine the control device having the next highest normalized optical signal strength and attempt to connect to the control device.

[0278] When at 676 the mobile device receives a solicitation confirmation message from the control device to which the mobile device is connected, at 678 the mobile device may store the unique identifier of the control device and corresponding association information (e.g., the configuration identifier with which the control device is associated) in a memory. The unique identifier stored during the solicitation procedure may be a device that may be attached to the network (e.g., individually or in batches) during an attachment procedure. The association information may be stored to identify the control device associated with the control device solicited for attachment to the network.

[0279] Looking back at 670 again, if at 670 the mobile device does not receive an instruction to associate the control device to which the mobile device is connected with one of the configuration identifiers, but at 680 receives an instruction to disassociate the control device from the associated configuration identifier, then at 682 the mobile device may disassociate the control device from the associated configuration identifier and at 684 delete the unique identifier of the control device and the association information from the memory. The mobile device may send a message to one or more control devices to remove the association from the memory at the one or more control devices.

[0280] If, at 686, the mobile device does not complete claiming the control device and / or associating the control device with the configuration identifier of the configuration data, method 650 may return to 662 to allow the mobile device to attempt to connect to the same or a different control device (e.g., if the control device happens not to be claimed and / or associated at 680). When, at 686, the mobile device completes claiming and / or associating the control device (e.g., the user actuates a button on the user interface of the mobile device to end the configuration procedure), at 688 the mobile device may exit the configuration mode, and method 650 may end. Additionally, at 688, the mobile device may stop transmitting the optical signal.

[0281] Figure 7A is an example of an exemplary method 700 for configuring a control device of a load control system (e.g., load control system 100 and / or Figure 2A the load control system 200 shown) for claiming and / or associating the control device. The flowchart of method 700 may be executed as part of a configuration procedure (e.g., a claiming procedure and / or an associating procedure). Method 700 may be implemented by a control device such as a lighting control device (e.g., lighting control devices 110, 210a to 210d, 310). However, other control devices may similarly execute one or more parts of method 700. During method 700, the lighting control device may provide different types of feedback. Method 700 may be executed after the lighting control device enters a configuration mode (e.g., a claiming mode and / or an associating mode) when the lighting control device is powered on. When in the configuration mode, the lighting control device may transmit (e.g., periodically transmit) a beacon (e.g., a control device beacon). The control device beacon may include a unique identifier of the lighting control device and / or the device type. The control device beacon may be transmitted via an RF communication signal (e.g., a low power (BLE) signal).

[0282] As Figure 7AAs shown, method 700 may begin at 702. For example, the mobile device may periodically execute method 700. At 704, a determination may be made as to whether a lighting control device has been discovered (e.g., added to a discovered control device in a temporary group) by a network device such as a mobile device (e.g., mobile devices 150, 250, 350). For example, there may be a temporary group including one or more discovered control devices. The determination may be made based on whether the lighting control device has received an indication that the lighting control device has been discovered from the mobile device (e.g., the mobile device may send the indication when receiving a control device beacon from the lighting control device). For example, the determination may be made in response to receiving a confirmation message from the mobile device including an indication that the lighting control device has been discovered from the mobile device. The confirmation message may include a temporary group identifier and / or a feedback type to provide to indicate that the lighting control device has been discovered. If the lighting control device is not within the discovery range of the mobile device at 704, method 700 may end.

[0283] If the lighting control device has been discovered at 704, at 706 the lighting control device may provide a first feedback type indicating that the lighting control device has been discovered (e.g., within the discovery range of the mobile device). The feedback may be provided by causing the lighting load to blink on and off; increasing and / or decreasing the brightness level of the lighting load; increasing and / or decreasing the color temperature of the lighting load; causing the lighting load to light up a predefined color; causing the lighting load to light up a predefined color temperature; and / or providing other visual feedback to the user. When the lighting control device falls outside the discovery range of the mobile device (e.g., after a timeout phase when the lighting control device falls outside the discovery range), the lighting control device may stop providing the first feedback type.

[0284] A determination may be made at 708 as to whether a control device beacon transmitted by the lighting control device has been received at the mobile device under the strongest received signal strength indicator (RSSI) of the discovered lighting control device. For example, the lighting control device may receive a message indicating that the mobile device has received the control device beacon of the lighting control device under the strongest received signal strength indicator of the discovered lighting control device. The message may be similar to the confirmation message indicating that the lighting control device has been discovered. If at 708 the lighting control device determines that the beacon control signal of the lighting control device has not been received under the strongest received signal strength indicator, then if the lighting control device is still within the discovery range of the mobile device at 704, at 706 the lighting control device may continue to provide the first feedback type again.

[0285] In response to detecting at 708 that a beacon control signal of a lighting control device has been received under the strongest received signal strength indicator, the lighting control device may provide a second feedback type at 710. The second feedback type may distinguish the lighting control device from other discovered control devices that provide a first feedback type. For example, the second feedback type may be provided by causing the lighting load to flash on and off; increasing and / or decreasing the brightness level of the lighting load; increasing and / or decreasing the color temperature of the lighting load; causing the lighting load to illuminate a predefined color; causing the lighting load to illuminate a predefined color temperature; and / or providing other visual feedback different from the first feedback type to the user.

[0286] In one example, the discovered lighting control device may cause each corresponding lighting load to illuminate orange to indicate the discovered lighting control device, and the lighting control device that transmits a control device beacon with the strongest received signal strength indicator received by the mobile device may cause the corresponding lighting load to illuminate blue. The blue lighting load may indicate to the user the lighting control device selected from the discovered lighting control devices for solicitation and / or association. The blue lighting load may indicate to the user the lighting control device that is most likely to be closest to the mobile device. The orange lighting load may indicate to the user those lighting loads within the discovery range of the mobile device and / or in the configuration mode. Additionally, the orange lighting load may indicate to the user those lighting control devices and / or lighting loads that are operating properly.

[0287] The lighting control device among the discovered devices (e.g., a single lighting control device) may provide the second feedback type at a given time. As the user walks around with the mobile device, a control device beacon of another lighting control device may be received under a stronger received signal strength indicator. The mobile device may communicate one or more messages configured to cause a change to the lighting load providing the second feedback type. The mobile device may cause different lighting loads to provide the second feedback type by transmitting a message within the wireless range of the temporary group with the identifier of the updated lighting control device from which it received the control device beacon with the strongest received signal strength indicator. The lighting control device currently providing the second feedback type may receive the message and stop providing the second feedback type since the received identifier is associated with another lighting control device. The lighting control device may return to providing the first feedback type or stop providing feedback altogether (e.g., if the mobile device fails to receive a message within a predefined time period). Thus, if at 708 the lighting control device determines that it has not received the beacon control signal of the lighting control device under the strongest received signal strength indicator, then if at 704 the lighting control device is still within the range of the mobile device, at 706 the lighting control device may provide the first feedback type again.

[0288] After providing the second feedback type at 710, a determination may be made at 712 as to whether the lighting control device has been requested and / or assigned a configuration identifier for the configuration data (e.g., a zone or group identifier for joining to a network). For example, the lighting control device may receive a message (e.g., a request message) indicating that the lighting control device has been requested. Additionally, the message may indicate that the lighting control device has been assigned a configuration identifier. The configuration identifier may be a luminaire, group, zone, area, and / or location defined by configuration data (e.g., lighting control configuration information) generated by design software. The configuration identifier may represent a luminaire, group, and / or zone at a certain physical location within a building and may be indicated on a floor plan. The message may be transmitted by a mobile device. The message may include the configuration identifier of the luminaire, group, and / or zone such that the lighting control message may respond to a message configured to control devices in the luminaire, group, and / or zone.

[0289] If the lighting control device has not been requested and / or assigned a configuration identifier at 712, then if the lighting control device is still receiving the beacon control signal of the lighting control device under the strongest received signal strength indicator at 708, the lighting control device may continue to provide the second feedback type at 710. However, if the lighting control device determines at 708 that it is no longer receiving the beacon control signal of the lighting control device under the strongest received signal strength indicator, then if the lighting control device is still within the range of the mobile device at 704, the lighting control device may provide the first feedback type again at 706.

[0290] When the lighting control device has been claimed and / or assigned to a configuration identifier at 712, the lighting control device may provide a third feedback type at 714. The third feedback type may distinguish the lighting control device from other discovered control devices that provide the first feedback type and / or the second feedback type. For example, the third feedback type may be provided by causing the lighting load to flash on and off; increasing and / or decreasing the brightness level of the lighting load; increasing and / or decreasing the color temperature of the lighting load; causing the lighting load to illuminate a predefined color; causing the lighting load to illuminate a predefined color temperature; and / or providing other visual feedback different from the first feedback type and / or the second feedback type to the user. In one example, a discovered lighting control device (e.g., not assigned to a zone luminaire or area and not having the strongest beacon signal received by the mobile device) may cause each corresponding lighting load to illuminate orange to indicate the lighting control device that has been discovered (e.g., within the wireless range of the mobile device), a lighting control device having the strongest beacon signal received by the mobile device (e.g., and not assigned to a zone luminaire and / or area) may cause the corresponding lighting load to illuminate blue, and a lighting control device that has been assigned to a zone luminaire and / or area may cause the corresponding lighting load to illuminate green. The green lighting load may indicate to the user a lighting control device that has been claimed and / or assigned to a configuration identifier other than the discovered lighting control device.

[0291] Lighting control devices assigned to different luminaires, groups, and / or areas may provide different types of feedback (e.g., causing the lighting load to illuminate different colors, flash in different ways, illuminate different color temperatures or dimming levels, etc.).

[0292] The third feedback type may also or alternatively be provided in response to other configuration information for configuring (e.g., claiming, diagnosing, associating, etc.) and / or controlling the lighting control device. For example, the third feedback type may be provided when the lighting control device is configured with a scene, dimming level, and / or other lighting control information to complete the configuration (e.g., claiming, diagnosing, associating, etc.) and / or control of the lighting control device. After providing the third feedback type at 714, the lighting control device may transmit a message (e.g., a claim confirmation message) including the unique identifier (e.g., serial number) of the lighting control device at 716. At 718, the lighting control device may then enter an engagement mode. Method 700 may end at 720. In the engagement mode, the lighting control device may stop continuously transmitting (e.g., periodically transmitting) a control device beacon via a short-range wireless communication link and may periodically switch between transmitting a control beacon (e.g., using BLE technology) and listening for a request to join an associated wireless communication network (e.g., as performed at 412 of method 400).

[0293] When the lighting control device is within the discovery range and / or the ad-hoc group, the lighting control device may provide a first feedback type, a second feedback type, and / or a third feedback type. When the mobile device moves away from the lighting control device such that the lighting control device is outside the discovery range and / or the ad-hoc group, the lighting control device may stop providing feedback.

[0294] If the lighting control device is removed from a previous assignment or other configurations (e.g., claims, diagnostics, associations, etc.) and / or controls of the lighting control device are removed, the lighting control device may stop providing the third feedback type. When the lighting control device is being configured and / or controlled (e.g., the lighting control device is in the discovered ad-hoc group lighting control device being configured and / or controlled), the lighting control device may return to the first feedback type and / or the second feedback type. When the lighting control device is outside the discovery range of the mobile device (e.g., removed from the discovered ad-hoc group lighting control device being configured and / or controlled), the lighting control device may stop providing feedback. When the lighting control device fails to receive a message from the mobile device within a predefined time period (e.g., indicating that the mobile device may be outside the wireless range), the lighting control device may automatically remove itself from the ad-hoc group and / or stop providing feedback. Additionally or alternatively, when the lighting control device receives a message from the mobile device and determines the signal strength of the message or receives an indication that the lighting device is outside the discovery range in the message (e.g., when the lighting control device is within the wireless communication range from the mobile device), the lighting control device may remove itself from the ad-hoc group and / or stop providing feedback. Although method 700 may be described with reference to a lighting control device, other types of control devices may be implemented similarly.

[0295] Figure 7B is a flowchart of an exemplary method 750 for configuring a control device of a load control system (e.g., load control system 100 and / or Figure 2A the load control system 200 shown) for claim and / or association of the control device. Method 750 may be executed as part of a configuration program (e.g., a claim program and / or an association program). Method 750 may be implemented by a control device (e.g., a lighting control device). However, other control devices may similarly execute one or more parts of method 750. During method 750, the lighting control device may provide different types of feedback. When the lighting control device is not in a configuration mode (e.g., the lighting control device does not enter the configuration mode when powered on and does not start periodically transmitting a control device beacon), method 750 may be executed.

[0296] With Figure 7ACompared with method 700, method 750 can reduce RF traffic (e.g., RF transmissions) in a region. The RF traffic in the region (e.g., in a building where lighting control devices are installed) can be generated by the control devices of the load control system and other devices in the region (such as other beacon devices, wireless network access points, etc.). Method 750 can be implemented, for example, when a network device, a mobile device, a system controller, and / or other control devices identify that the number of control devices in the load control system is higher than a device count threshold (e.g., greater than 25, 50, 100, etc.). For example, if the number of control devices in the load control system is higher than the threshold, there may be a relatively large amount of RF traffic (e.g., interference) if the control devices transmit beacons simultaneously. Additionally or alternatively, method 750 can be implemented when network congestion exceeding a threshold is detected at a device (e.g., a lighting control device, a system controller, a network device, a mobile device, etc.). For example, network congestion can exceed the threshold when the probability of message reception has dropped below a reception probability threshold (e.g., when the number of times a message may need to be retransmitted is greater than a retransmission threshold). Method 750 can reduce the amount of RF traffic present in the region where the load control system is located, for example, by reducing the number of control devices transmitting beacons at any given time (which can reduce the incidence of collisions between transmissions and / or the incidence of discarded messages). The identification of a high amount of RF traffic and / or the likelihood of network congestion can be provided manually by a user (e.g., using the user interface of a mobile device), and / or automatically by one or more of the control devices of the load control system (e.g., the system controller).

[0297] As Figure 7B shown, for example, when a lighting control device receives a beacon (e.g., a mobile device beacon) from a network device such as a mobile device (e.g., mobile devices 150, 250, 350), method 750 can begin at 752. The mobile device beacon can be transmitted in response to entering a configuration mode at the mobile device (e.g., in response to the selection of a button on an application on the mobile device). The mobile device beacon can be transmitted periodically while the mobile device is in the configuration mode. The mobile device beacon can include a beacon identifier of the mobile device. For example, the beacon identifier can be a unique identifier identifying the mobile device (e.g., or an application executed on the mobile device), and / or a non-unique identifier, such as an identifier of a group, a region, a building, a load control system, and / or a manufacturer of the mobile device and / or control device of the load control system. The beacon identifier can be an identifier of an application running on the mobile device. The mobile device beacon can be transmitted via an RF communication signal (e.g., It is transmitted using a low-power (BLE) signal. The mobile device can determine the received signal strength indicator (RSSI) of the received network device beacon (e.g., the signal strength at which the received network device beacon is located). The received signal strength indicator of the mobile device beacon can be compared with a received signal strength discovery threshold (e.g., the received signal strength discovery threshold). The received signal strength discovery threshold can be received in the mobile device beacon and / or pre-configured at the lighting control device. The received signal strength discovery threshold can be configured by the user of the mobile device, pre-configured on the mobile device and / or the lighting control device, and / or configured by the network (e.g., received from the system controller).

[0298] At 754, a determination can be made as to whether the lighting control device is within the discovery range of the mobile device. For example, the lighting control device can determine that the lighting control device is within the discovery range of the mobile device by determining whether the received signal strength indicator (RSSI) of the received mobile device beacon is greater than or equal to the received signal strength discovery threshold (e.g., the received signal strength discovery threshold included in the received mobile device beacon). If at 754 the lighting control device determines that the lighting control device is within the discovery range of the mobile device, then at 755 the lighting control device can enter a configuration mode (e.g., a solicitation mode and / or an association mode). Additionally, the lighting control device can enter the configuration mode when (e.g., only when) the beacon identifier of the received mobile device beacon is a specific (e.g., predetermined) beacon identifier. The configuration mode can be a mode in which the mobile device can store the association of the unique identifier of the lighting control device with the configuration identifier of the configuration data (e.g., locally and / or at the system controller). The stored association can enable the identification of the associated control device for performing load control during normal operation or otherwise responding to messages from the associated device. For example, entering the configuration mode can be triggered in response to the mobile device beacon received by the lighting control device. If at 754 the lighting control device determines that the lighting control device is not within the discovery range of the mobile device, then method 750 can end at 778.

[0299] A mobile device beacon can operate as a trigger event for triggering a lighting control device to transmit a beacon (e.g., a control device beacon). At 756, the lighting control device can start transmitting the control device beacon periodically. The control device beacon can include a beacon identifier of the lighting control device and / or the device type. For example, the beacon identifier of the control device can be a unique identifier that identifies the lighting control device, and / or a non-unique identifier, such as an identifier of a group, a region, a building, a load control system, and / or a manufacturer of the mobile device and / or the control device of the load control system 100. The control device beacon can be communicated in response to receiving a mobile device beacon having a received signal strength indicator (RSSI) greater than a received signal strength discovery threshold and / or the beacon identifier of the received mobile device beacon being a specific (e.g., predetermined) beacon identifier.

[0300] At 758, the lighting control device can provide a first type of feedback indicating that the lighting control device has entered a configuration mode. The first type of feedback can be provided by causing the lighting load to flash on and off; increasing and / or decreasing the brightness level of the lighting load; increasing and / or decreasing the color temperature of the lighting load; causing the lighting load to light up a predefined color (e.g., orange); causing the lighting load to light up a predefined color temperature; and / or providing other visual feedback to the user. When the lighting control device falls outside the discovery range of the mobile device (e.g., after a timeout phase when the lighting control device falls outside the wireless range of the mobile device), the lighting control device can stop providing the first type of feedback. If the lighting control device enters the discovery range of the mobile device (e.g., after a timeout phase when the lighting control device falls outside the discovery range), the lighting control device can resume providing the first type of feedback.

[0301] At 760, a determination can be made as to whether the lighting control device is connected to the mobile device. For example, the lighting control device can determine whether it has received, at the mobile device, the control device beacon transmitted by the lighting control device under the strongest received signal strength indicator (RSSI) of the lighting control devices in the configuration mode (e.g., those lighting control devices that have not been claimed). For example, the lighting control device can receive a message indicating that the mobile device has received the control device beacon under the strongest RSSI of the control devices in the configuration mode. For example, the message can be a connection message that initiates the establishment of a connection (e.g., a two-way communication connection) between the mobile device and the lighting control device.

[0302] If the lighting control device does not receive a connection message at 760 (e.g., has not received the beacon control signal of the lighting control device under the strongest received signal strength indicator), the lighting control device can determine at 762 whether the lighting control device is still within the discovery range of the mobile device (e.g., whether it is still receiving the mobile device beacon). If the lighting control device is still within the discovery range of the mobile device at 762, the lighting control device can continue to provide the first feedback type again at 758. If the lighting control device is no longer within the discovery range at 762, the lighting control device can stop providing feedback (e.g., the first feedback type) at 764, exit the configuration mode at 766, and method 700 can end at 778. Additionally, at 764, the control device can stop periodically transmitting the control device beacon.

[0303] When the lighting control device is connected to the mobile device at 762 (e.g., in response to receiving the control device beacon of the lighting control device under the strongest received signal strength indicator of the lighting control device in the configuration mode), the lighting control device can provide a second feedback type at 768. The second feedback type can distinguish the lighting control device from other lighting control devices that provide the first feedback type. For example, the second feedback type can be provided by causing the lighting load to flash on and off; increasing and / or decreasing the brightness level of the lighting load; increasing and / or decreasing the color temperature of the lighting load; causing the lighting load to light up a predefined color (e.g., blue); causing the lighting load to light up a predefined color temperature; and / or providing other visual feedback different from the first feedback type to the user.

[0304] In one example, the lighting control device in the configuration mode can cause each corresponding lighting load to light up orange to indicate that the lighting control device is in the configuration mode, and the lighting control device that transmits the control device beacon received by the mobile device under the strongest received signal strength indicator can cause the corresponding lighting load to light up blue. The blue lighting load can indicate to the user the lighting control device selected for claiming and / or associating. The blue lighting load can indicate to the user the lighting control device that is most likely to be closest to the mobile device among the discovered lighting control devices. The orange lighting load can indicate to the user those lighting loads within the discovery range of the mobile device and / or in the configuration mode. Additionally, the orange lighting load can indicate to the user to properly operate those lighting control devices and / or lighting loads.

[0305] A lighting control device (e.g., a single lighting control device) in a set of discovered devices can provide a second feedback type at a given time. As the user walks around with a mobile device, a control device beacon of another lighting control device can be received under a stronger received signal strength indicator. The mobile device can communicate one or more messages configured to cause a change to a lighting load that provides the second feedback type. The mobile device can cause different lighting loads to provide the second feedback type by transmitting a message (e.g., a connection message) with the identifier of the updated lighting control device from which it received the strongest control device beacon. The mobile device can disconnect the two-way communication connection with the lighting control device that is currently providing the second feedback type, and the lighting control device can stop providing the second feedback type. The lighting control device can return to providing the first feedback type or stop providing feedback altogether (e.g., if the lighting control device fails to receive a mobile device beacon from the mobile device within a predefined time period). Thus, if at 760 the lighting control device determines that it has not received a beacon control signal of the lighting control device under the strongest received signal strength indicator, then if at 762 the lighting control device is still within the range of the mobile device, at 758 the lighting control device can provide the first feedback type again.

[0306] After providing the second feedback type at 768, a determination can be made at 770 as to whether the lighting control device has been claimed and / or assigned a configuration identifier for configuration data. For example, the lighting control device can receive a message (e.g., a claim message) indicating that the lighting control device has been claimed. Additionally, the message can indicate that the lighting control device has been assigned a configuration identifier. The configuration identifier can be a luminaire, group, zone, area, and / or location defined by configuration data (e.g., lighting control configuration information) generated by design software. The configuration identifier can represent a luminaire, group, and / or zone at a certain physical location within a building and can be indicated on a floor plan. The message can be transmitted by the mobile device. The message can include the configuration identifier of the luminaire, group, and / or zone such that the lighting control message can respond to a message configured to control devices in the luminaire, group, and / or zone.

[0307] If at 770 the lighting control device has not been claimed and / or assigned a configuration identifier, then if at 760 the mobile device is still receiving the beacon control signal of the lighting control device under the strongest received signal strength indicator, at 768 the lighting control device can continue to provide the second feedback type. However, if at 760 the lighting control device determines that it is no longer receiving the beacon control signal of the lighting control device under the strongest received signal strength indicator, then if at 762 the lighting control device is still within the range of the mobile device, at 758 the lighting control device can provide the first feedback type again.

[0308] When the lighting control device has been claimed and / or assigned to a configuration identifier at 770, the lighting control device may provide a third feedback type at 772. The third feedback type may distinguish the lighting control device from other control devices in a configuration mode that provide the first feedback type and / or the second feedback type. For example, the third feedback type may be provided by causing the lighting load to flash on and off; increasing and / or decreasing the brightness level of the lighting load; increasing and / or decreasing the color temperature of the lighting load; causing the lighting load to illuminate a predefined color (e.g., green); causing the lighting load to illuminate a predefined color temperature; and / or providing other visual feedback different from the first feedback type and / or the second feedback type to the user.

[0309] In one example, a lighting control device within the discovery range of a mobile device (e.g., in a configuration mode) may cause each corresponding lighting load to illuminate orange to indicate a lighting control device within the discovery range of the mobile device (e.g., within the discovery range of the mobile device) (e.g., not claimed and not having the strongest control device beacon signal received by the mobile device). A lighting control device having a control device beacon received by the mobile device under the strongest received signal strength indicator (e.g., and not claimed) may cause the corresponding lighting load to illuminate blue, and a lighting control device that has been claimed may cause the corresponding lighting load to illuminate green. The green lighting load may indicate to the user a lighting control device that has been claimed and / or assigned to a configuration identifier. Lighting control devices claimed and assigned to different luminaires, groups, and / or areas may provide different types of feedback (e.g., causing the lighting load to illuminate different colors, flashing in different ways, causing the lighting load to illuminate different color temperatures or dimming levels, etc.).

[0310] The third feedback type may also or alternatively be provided in response to other configuration information for configuring (e.g., claiming, diagnosing, associating, etc.) and / or controlling the lighting control device. For example, the third feedback type may be provided when the lighting control device is configured with a scene, dimming level, and / or other lighting control information to complete the configuration (e.g., claiming, diagnosing, associating, etc.) and / or control of the lighting control device. After providing the third feedback type at 772, the lighting control device may transmit a message (e.g., a claim confirmation message) including the unique identifier (e.g., serial number) of the lighting control device at 774. At 776, the lighting control device may then enter an engagement mode. In the engagement mode, the lighting control device may stop continuously transmitting (e.g., periodically transmitting) control device beacons via a short-range wireless communication link and may periodically switch between transmitting a control beacon (e.g., using BLE technology) and listening for requests to join an associated wireless communication network (e.g., as performed at 412 of method 400). Method 750 may end at 778.

[0311] When the lighting control device is in a configuration mode (e.g., receiving a mobile device beacon at or above a received signal strength discovery threshold), the lighting control device may provide a first feedback type, a second feedback type, and / or a third feedback type. When the mobile device moves away from the lighting control device such that the received signal strength indicator of the mobile device beacon is below the received signal strength discovery threshold, the lighting control device may stop providing feedback.

[0312] If the lighting control device is removed from a previous assignment or the claim status of the lighting control device is removed, the lighting control device may stop providing the third feedback type. When the lighting control device is in the configuration mode, the lighting control device may return to the first feedback type and / or the second feedback type. When the lighting control is outside the discovery range of the mobile device (e.g., not receiving a mobile device beacon at or above a received signal strength discovery threshold), the lighting control device may stop providing feedback. When the lighting control device fails to receive a mobile device beacon from the mobile device within a timeout period (e.g., thereby indicating that the mobile device may be outside the discovery range), the lighting control device may automatically exit the configuration mode and / or stop providing feedback. Additionally or alternatively, when the lighting control device receives a message from the mobile device and determines that the received signal strength indicator of the mobile device beacon is less than the received signal strength discovery threshold and / or receives an indication that the lighting device is outside the discovery range in the message (e.g., when the lighting control device is within the wireless communication range from the mobile device), the lighting control device may exit the configuration mode and / or stop providing feedback. Although method 750 may be described with reference to a lighting control device, other types of control devices may be implemented similarly.

[0313] As Figure 7B shown, the mobile device may select a control device (e.g., a lighting control device) to be configured and / or controlled based on the signal strength of a control device beacon transmitted by the control device and ...

Claims

1. A load control system, comprising: a plurality of lighting fixtures; and a commissioning party device configured to: receive respective device identification data from each of the plurality of lighting fixtures via a mobile device; select a first subset of the plurality of lighting fixtures for joining to a network; and using the respective device identification data received from each of the first subset of the plurality of lighting fixtures, transmit a respective joining party request message to each of the first subset of the plurality of lighting fixtures; wherein each of the first subset of the plurality of lighting fixtures is configured to: receive an association message from the mobile device including a respective configuration identifier; in response to receiving the association message, transmit the respective device identification data to the mobile device; and in response to transmitting the respective device identification data to the mobile device, receive a respective joining party request message from the commissioning party device.

2. The load control system according to claim 1, wherein the commissioning party device is configured to operate in an offline mode.

3. The load control system according to claim 1, wherein each of the first subset of the plurality of lighting fixtures is configured to indicate that the lighting fixture has been associated with the respective configuration identifier by providing a first feedback type.

4. The load control system according to claim 3, wherein each of the first subset of the plurality of lighting fixtures is configured to provide the first feedback type by lighting up in a first color.

5. The load control system according to claim 1, wherein each of the first subset of the plurality of lighting fixtures is configured to: monitor a first wireless communication link for the association message; and after receiving the association message, alternately use the first wireless communication link to transmit the respective device identification data and monitor a second wireless communication link for the joining party request message.

6. The load control system according to claim 5, wherein after joining to the network, each of the first subset of the plurality of lighting fixtures is configured to communicate using the second wireless communication link.

7. The load control system according to claim 1, wherein the commissioning party device is configured to: select the first subset of the plurality of lighting fixtures based on random selection.

8. The load control system according to claim 1, wherein the commissioning party device is further configured to: select a second subset of the plurality of lighting fixtures for joining to the network, wherein the second subset includes one or more lighting fixtures that have not yet joined to the network; and join the second subset of the lighting fixtures to the network.

9. The load control system according to claim 1, wherein the load control system further includes the mobile device, and wherein the mobile device is configured to determine whether respective device identification data has been received from each of the plurality of lighting fixtures based on a comparison of a list of lighting fixtures that have received their respective device identification data with a list of the plurality of lighting fixtures.

10. The load control system according to claim 1, wherein the load control system further comprises the mobile device, and wherein the mobile device is configured to associate each lighting fixture in the first subset of the plurality of lighting fixtures with a corresponding configuration identifier based on an input from a user of the mobile device.

11. The load control system according to claim 1, wherein the device identification data includes one or more of a corresponding address, a corresponding engagement party ID, or a corresponding unique identifier for each of the plurality of lighting fixtures.

12. The load control system according to claim 10, further comprising a cloud server, wherein the mobile device is further configured to: Determine a project code; Transmit the project code to the cloud server; and Receive configuration data from the cloud server.

13. The load control system according to claim 12, wherein the project code comprises an alphanumeric sequence.

14. The load control system according to claim 13, wherein the mobile device is configured to determine the project code based on an input from the user of the mobile device.

15. The load control system according to claim 12, wherein the mobile device is configured to determine the project code by scanning a machine-readable code using a camera of the mobile device.

16. The load control system according to claim 15, further comprising a processing device configured to display the machine-readable code on a display of the processing device, wherein the mobile device is further configured to determine the project code by scanning the display of the processing device.

17. The load control system according to claim 12, wherein the project code includes a security key, and wherein the cloud server is configured to: Receive the security key from the mobile device; Authenticate the security key; and Transmit the configuration data to the mobile device.

Images