AUTOMATIC ADJUSTMENT OF A DISCOVERY RANGE TO DISCOVER WIRELESS CONTROL DEVICES

Abstract

A load control system can be implemented using beacon messages. The load control system may include control devices, each of which includes a beacon transmitter circuit configured to transmit a beacon message comprising an identifier associated with the control device. A network device, such as a mobile device, can discover a control device based on the beacon message 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 to be configured and / or controlled collectively. Control devices can be discovered based on the signal strength at which the beacon messages are received. A mobile device can set a discovery threshold to discover a target number of control devices in the load control system.

Description

This application claims the benefit of U.S. provisional patent application no. 363 / 019,049, filed on May 1, 2020, and U.S. provisional patent application no. 363 / 071,183, filed on August 27, 2020, the contents of which are incorporated herein in full by reference. BACKGROUND Load control systems can include electrical loads (e.g., lighting loads, etc.) and load control devices (e.g., ballasts, LED drivers, etc.) to control the electrical power supplied to the lighting loads. Load control devices can be controlled by messages from remote control devices or sensors (e.g., occupancy sensors, etc.) capable of sending instructions via messages to the load control devices to manage the electrical loads. Load control devices can receive communications to perform load control from a system controller, which can be programmed with configuration information to control the load control devices within the system.After the devices are installed in the load control systems, the load control systems can be started up to enable the proper configuration and communication of the devices in order to control the electrical loads. Typically, after a load control system is installed in a location, such as a residence, office, or similar, the system controller can assign link addresses to the lighting control devices it controls. These link addresses can then be used to send instructions to the load control devices to manage electrical loads. This assignment can be randomized. For example, a system controller might be able to manage multiple lighting control devices, such as lighting ballasts or LED drivers, and could randomly assign a different link address to each device. It is difficult to determine which link address was assigned to a load control device at a specific location after installation to enable control of electrical loads at that location from other devices, such as remote control devices, occupancy sensors, or the system controller. For example, a floor plan may identify a load control device and its corresponding location in a room or building, while the system controller may store a list of assigned link addresses, and the location of the load control device assigned to a particular link address may be unknown. To control load control devices at a desired location, during the commissioning procedure, users may need to identify a lighting load controlled by a lighting control device with an assigned link address and associate that link address with the identified location in the building. Because a building may contain many lighting control devices (e.g., in different rooms, on different floors, etc.) with unknown link addresses, users may need to supply power to a lighting load using a known link address and then locate the lighting load being controlled (e.g., turning on, flashing, etc.) within the building in order to associate the physical location of the lighting control device with its assigned link address.The lights being controlled may be in rooms different from the one currently occupied by the user configuring the system, which may require the user to move around the building to different rooms to start the system. Similar time-consuming processes may be implemented to configure other devices in the load control system. The process of identifying the location of control devices in the system and associating the devices during system commissioning to enable proper load control can be costly and time-consuming. SUMMARY. A load control system, as described herein, can be commissioned to control one or more electrical loads. During the commissioning of a load control system, one or more control devices can be discovered and / or selected for collective configuration and / or control. The selected control devices can be included in a temporary group of target control 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 location or zone. Control devices can be added to and / or removed from the 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 device, to enable control of the temporary group of control devices based on messages received from the control source device. The load control system can be activated using beacon messages. For example, the load control system might include lighting control devices, each of which includes a beacon transmitter circuit (e.g., a control device beacon) configured to transmit a beacon message comprising an identifier associated with the lighting control device. A network device can discover a lighting control device based on the beacon message received from the lighting control device. In response to the discovery of the lighting control device, the lighting control device can be added to a temporary group of lighting control devices to be configured and / or controlled collectively. The beacon message can be transmitted periodically and / or in response to a triggering event. For example, the beacon message can be transmitted in response to a message, a button being pressed on the control device, or in response to an occupancy condition detected by an occupancy sensor. A lighting control device in the load control system can be in direct communication with an occupancy sensor (e.g., installed in the same fixture), and the lighting control device can transmit beacon messages (e.g., every beacon message or initiate a periodic transmission of beacon messages) in response to the occupancy condition detected by the occupancy sensor. A lighting control device can transmit a control device beacon message (e.g., to enter configuration mode) after receiving a mobile device beacon message transmitted by a mobile device (e.g., a network device). The mobile device beacon message may include a discovery threshold. The lighting control device can receive the mobile device beacon message and determine the Received Signal Strength Indicator (RSSI) at which the mobile device beacon message was received. The lighting control device can transmit the control device beacon message if the Received Signal Strength Indicator at which the mobile device beacon message was received is greater than or equal to the discovery threshold.The lighting device may stop transmitting the beacon message from the control device if the received signal strength indicator at which the beacon message was received from the mobile device is less than the discovery threshold (e.g., the mobile device is out of the discovery range of the lighting control device). Control devices can be discovered based on the signal strength at which their respective beacon messages are received. For example, a lighting control device can be discovered when the signal strength at which its beacon message is received exceeds a discovery threshold. The discovery threshold can be adjusted to discover other control devices within a broader or narrower range. For example, the discovery threshold can be adjusted (e.g., by the mobile device) so that the number of control devices receiving the mobile device's beacon message above the discovery threshold (e.g., and MA / t / ZUZÓ / UUΊ (which transmit the beacon message from the respective control device) is within a target range. The target range can have a low-side threshold value and a high-side threshold value. For example, the target range can be 15 to 25 devices. The discovery threshold can be increased if the number of control devices receiving the beacon message from the mobile device is greater than the target range and decreased if the number of control devices receiving the beacon message from the mobile device is less than the target range. The amount by which the discovery threshold is adjusted can depend on the number of control devices receiving the beacon message from the mobile device. For example, a mobile device can transmit a mobile device beacon message that includes a discovery threshold. A control device can respond to the mobile device's beacon message by transmitting a control device beacon message if the control device receives the mobile device's beacon message with a signal strength greater than the discovery threshold. The mobile device can count a number of control devices that respond to its beacon message within a predefined time period (e.g., a number of discovered control devices). If the number of discovered control devices falls within the target range, the mobile device may not change the discovery threshold.If the number of discovered control devices is less than the defined range, the mobile device can transmit a second mobile device beacon message with a reduced discovery threshold. Conversely, if the number of discovered control devices is greater than the target range, the mobile device can transmit a mobile device beacon message with an increased discovery threshold. The mobile device can increase or decrease the discovery threshold by a relatively smaller amount if the number of discovered control devices is closer to the target range, and by a relatively larger amount if the number of control devices is farther from the target range. A control device can continue transmitting a beacon message from the control device during a discovery period after receiving a beacon message from the mobile device with a signal strength greater than the discovery threshold (e.g., even if the control device receives a second beacon message from the mobile device that includes a second discovery threshold at a signal strength below the second discovery threshold). The mobile device can initiate an adjustment timer when the discovery threshold is raised and can maintain the discovery threshold (e.g., not raise the discovery threshold) until the adjustment timer has finished in an attempt to improve the accuracy of the count of the number of discovered control devices. The control device can implement hysteresis to enter and exit the discovery range (e.g.The configuration mode is based on the discovery threshold. Hysteresis can be used to increase the likelihood that the control device will remain in its current state (e.g., in or out of configuration mode) despite minor fluctuations in the signal strength with which successive beacon messages from the mobile device are received. For example, the discovery range can be based on the discovery threshold and a first offset to enter the discovery range (e.g., enter configuration mode) and on the discovery threshold and a second offset (e.g., the same as and / or different from the first offset) to exit the discovery range (e.g., exit configuration mode). The mobile device can include one or more offsets in its beacon message.The offsets can be pre-stored in the control device's memory. Alternatively, the mobile device can include an incoming discovery threshold and / or an outgoing discovery threshold in its beacon message. The incoming discovery threshold can be higher than the outgoing discovery threshold, and the outgoing discovery threshold can be lower than the outgoing discovery threshold. The control device can use the offset(s), the incoming discovery threshold, and / or the outgoing discovery threshold to determine whether to transmit a control device beacon message (e.g., whether to enter, remain in, or exit a configuration mode).For example, if the control device is not currently in configuration mode to transmit a beacon message from the control device, the control device can add the first offset to the discovery threshold to increase the discovery threshold. The control device can then compare the amplitude of the received signal strength, such as a Received Signal Strength Indicator (RSSI), at which the beacon message from the mobile device was received with the increased discovery threshold or the input discovery threshold to determine whether to transmit the beacon message from the control device. If the control device is currently in configuration mode to transmit the beacon message from the control device, the control device can subtract the second offset from the discovery threshold to decrease the discovery threshold.The control device can then compare the amplitude of the received signal strength at which the beacon message was received from the mobile device with the reduced discovery threshold or the outgoing discovery threshold to determine whether to continue transmitting the beacon message from the control device. Offsets and / or incoming and outgoing discovery thresholds can be used in addition to and / or as an alternative to the discovery period. BRIEF DESCRIPTION OF THE DRAWINGS Figure 1 illustrates a representative load control system for configuring and / or controlling one or MA / t / ZUZÓ / UUΊ more control devices using beacon messages. Figure 2A illustrates a representative load control environment in which the load control system shown in Figure 1 can be implemented to configure and / or control one or more control devices using beacon messages. Figure 2B is an illustrative network diagram for communication in the load control system of Figure 1. Figure 3 is a system diagram that illustrates a representative control system for configuring and / or controlling one or more control devices using beacon messages. Figure 4 is a flowchart that represents an illustrative procedure (e.g., a start-up procedure) for starting up a control system. Figure 5 is a system flowchart that illustrates message flows for discovering control devices to enable their attribution and / or association. Figure 6 is a flowchart that illustrates a procedure for discovering control devices to enable their attribution and / or association. Figure 7 is another flowchart that represents an illustrative procedure for discovering control devices and providing feedback to enable configuration and / or control using beacon messages. Figure 8A is a flowchart that represents an illustrative procedure for transmitting a beacon message from the control device to enable the configuration and / or control of a control device. Figure 8B is another flowchart that represents an illustrative procedure for transmitting a control device beacon message to enable the configuration and / or control of a control device. Figure 9 is a flowchart that represents an illustrative procedure for adjusting a discovery threshold in order to discover control devices to enable the configuration and / or control of control devices. Figure 10 is a block diagram illustrating an illustrative network device as described herein. Figure 11 is an illustrative block diagram of a system controller. Figure 12 is an illustrative block diagram of a load control device. Figure 13 is a block diagram that illustrates an illustrative control source device. DETAILED DESCRIPTION To implement a load control system, one or more control devices can be identified and / or selected for collective configuration and / or control to enable load control. The control devices may include at least one control target device (e.g., a load control device) and at least one control source device. Control target devices can control an electrical load based on messages received from associated control source devices. A single control device in the load control system can function as both a control target 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 as a control source device to transmit messages to another load control device for controlling an electrical load. The implementation of a load control system may include the identification and / or association of control source devices and / or control target devices for individual and / or collective control. Devices can be associated with each other by storing their device identifiers together in a memory. Control devices can be temporarily grouped to enable control of the devices within the group. Devices can be associated with a temporary group by storing their device identifiers in a memory with a temporary group identifier. These associations can be stored on the control devices or other devices in the load control system and used as a reference to ensure appropriate responses for enabling load control between associated devices in the system. Control devices can be identified and / or selected for collective configuration and / or control using beacon messages (e.g., control device beacon messages). Selected control devices can be temporarily grouped to enable their configuration and / or control. Control device beacon messages can include unique identification information that can be used to identify and / or select control devices for collective configuration and / or control in a load control environment. Control device beacon messages can indicate or be used to indicate the proximity or location of a device and / or the current status of the device. Control device beacon messages can include a primary identifier and a secondary identifier for a control device (e.g., a load control device).The primary identifier may include the unique identifier of the corresponding control device, and the secondary identifier may include the unique identifier for the type of control device, or vice versa. The primary and secondary identifiers may be used in combination to identify the unique identifier of the control device. A network device (e.g., a mobile device) can also transmit a beacon message (e.g., a mobile device beacon message). The mobile device beacon message may include unique identifying information that can be used to identify the network device and / or a discovery threshold. Additionally, a beacon transmitter can transmit a beacon message (e.g., a location beacon message). The location beacon message may include unique identifying information that can be used to identify the location of the beacon transmitter and / or a discovery threshold. The beacon transmitter may be a control device, or it may be a device independent of a control device. Beacon messages (e.g., control device beacon messages, a location beacon message, and / or a mobile device beacon message) can be transmitted as radio frequency (RF) communication signals or other types of signals that can be received by another control device, a network device, and / or a beacon transmitter in the vicinity of the device that transmitted the beacon message. Beacon messages can be transmitted as short-range RF communication signals. For example, beacon messages can be RF signals that are periodically communicated using a short-range wireless communication protocol (e.g., such as Bluetooth and / or Bluetooth Low Energy (BLE) protocols).When a beacon message is transmitted using an RF communication signal, the message can be identified by a device to indicate that the device is near or at the location of the device that transmitted the beacon message. The proximity of the device to a beacon transmitter can be determined by the signal strength at which the RF communication signal of the beacon message is received. A load control system can be implemented by preparing or configuring the control devices for load control using beacon messages. The control devices can be associated with each other and / or with a location using beacon messages, as described herein. The control devices associated with a location can then be deployed for load control at that location. Figure 1 illustrates a representative load control system 100 for configuring and / or controlling one or more control devices using beacon messages. The load control system 100 may include a lighting fixture 110 (e.g., a panel 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 loads 112 of the lighting fixture 110. The lighting control device 114 may be installed inside the lighting fixture 110, on an external surface of the lighting fixture 110, and / or adjacent to (e.g., externally to) the lighting fixture 110.The lighting control device 114 of the lighting fixture 110 can function as a target control device to control the amount of power supplied to the lighting loads 112 in order to control an intensity level of the lighting fixture 110 in response to messages received from control source devices. The load control system 100 may include lighting fixtures 120a-120c controlled by a load controller 121. Each lighting fixture 120a-120c may have respective lighting loads 122a-122c (e.g., LED light sources) and a respective lighting control device 124a-124c (e.g., an LED driver) to control the amount of power supplied to the respective lighting loads of the lighting fixture. The load controller 121 may be coupled to the lighting control devices 124a-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-124c, thereby individually controlling the lighting loads 122a-122c.The 121 charge controller can function as a target control device to control the 124a-124c lighting control devices in order to regulate the power supplied to the 122a-122c lighting loads and control the intensity levels of the 120a-120c lighting fixtures in response to messages received from the control source devices. Additionally, the 100 load control system can include a lighting fixture with multiple controllable light sources that can be controlled by a single charge controller, such as the 121 charge controller. The load control system 100 may also include a lighting fixture 130 (e.g., a downlight fixture) having 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) to control the amount of power supplied to an internal lighting load of the controllable light source 132. For example, the controllable light source 132 may be screwed into a standard Edison screw thread of the lighting fixture 130. The controllable light source 132 of the lighting fixture 130 may function as a control target device to control the intensity level of the lighting load of the controllable light source 132 in response to messages received from control source devices.While the lighting control device 114, the lighting control devices 124a-124c and the controllable light source 132 may be provided as illustrative control target devices, the load control system 100 may include other control target devices, such as, for example, a motorized window treatment, a temperature control device and / or a plug-in load control device. The illumination level of the lighting fixture 110, the lighting control devices 124a-124c, and / or the controllable light source 132 can be controlled according to lighting control instructions received from a control source device. A control source device can communicate messages to a control target device (e.g., a load control device such as a lighting control device) via wired and / or wireless signals to control an electrical load (e.g., a lighting load). Illustrative control source devices in the load control system 100 can include an occupancy sensor 134, a remote control device 136, and / or another control source device capable of communicating messages to the lighting control device 114, the lighting control devices 124a-124c, and / or the controllable light source 122 to perform control.The load control system 100 may also include a system controller 140 and a network device, such as a mobile device 150, which may also function as a control source device. For example, the mobile device 150 may include a smartphone and / or a tablet. The amount of power supplied to the lighting loads 112 of the lighting fixture 110, the lighting loads 122a-122c of the lighting control devices 124a-124c, and / or the controllable light source 132 can be controlled in response to lighting control instructions received from a control source device (e.g., the occupancy sensor 134, the remote control device 136, the system controller 140, the mobile device 150, and / or another control source device). The lighting level can be controlled according to lighting control configuration information, such as a default configuration, zone configurations, occupancy configuration, and / or schedule configuration information that can be stored in the lighting control device 114, the lighting control devices 124a-124c, the controllable light source 132, and / or the system controller 140 or the mobile device 150.Lighting control instructions can be transmitted over a wireless communication network via radio frequency (RF) signals 102. The occupancy sensor 134 can be a control source device configured to detect occupancy and / or vacancy conditions in the space where the load control system 100 is installed. The occupancy sensor 134 can transmit messages via RF communication signals 102 in response to detecting occupancy or vacancy conditions. Although Figure 1 shows the occupancy sensor 134 communicating messages via RF communication signals 102, the occupancy sensor 134 can also communicate via wired communication. The system controller 140 can be configured to switch the lighting loads of one or more lighting fixtures (e.g., lighting loads 112, 122a-122c, and / or the controllable light source 122) on and off in response to receiving an occupancy signal and a vacancy signal, respectively.Occupancy sensor 134 can function as an unoccupancy sensor, so that lighting loads are only manually switched on by a user and / or automatically switched off in response to the detection of an unoccupancy signal from the sensor (e.g., the lighting load does not switch on in response to the detection of an occupancy condition). Examples of load control systems having both occupancy and unoccupancy sensors are described in greater detail in jointly owned U.S. patent no. 8,009,042, issued August 30, 2011, entitled "Radio-frequency Lighting Control System with Occupancy Sensing"; and U.S. patent no. 8,199,010, issued June 12, 2012, entitled "Method and Apparatus for Configuring a Wireless Sensor." and U.S. patent η.θ8,228,184, issued on July 24, 2012, entitled BATTERY-POWERED OCCUPANCY SENSOR, the full descriptions of which are incorporated herein by reference.While the occupancy sensor 134 can be shown as external to the lighting fixture 110, a sensor 116 can be incorporated into the lighting fixture 110 and / or be in direct communication (e.g., wired or wireless) with the lighting control device 114 of the lighting fixture 110 to control the lighting loads 112. Additionally, the load controller 121 can be connected to a sensor 126. The sensors 116 and 126 can be used to control the lighting fixture 110 and / or the lighting control devices 124a-124c, respectively. The sensors 116 and 126 can be occupancy sensors, visible light sensors (e.g., cameras), sunlight sensors, optical sensors, and / or any other type of sensor. The sensors 116 and 126 can be occupancy sensors capable of detecting occupancy / vacancy conditions (e.g., using infrared signals). Sensors 116, 126 can be visible light sensors (e.g., camera) capable of detecting changes in the visible space of sensors 116, 126. Sensors 116 and 126 can be configured to operate similarly to occupancy sensor 134, but they can communicate directly with the lighting control device 114 of lighting fixture 110 and the load controller 121, respectively. For example, the lighting control device 114 of lighting fixture 110 can switch lighting loads 112 on and off in response to receiving an occupancy signal and an unoccupied signal, respectively, from sensor 116. Similarly, the load controller 121 can switch lighting loads 122a-122c on and off in response to receiving an occupancy signal and an unoccupied signal, respectively, from sensor 126. The remote control device 136 can be a control source device configured to transmit messages 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 RF communication signals 102 in response to the activation of one or more buttons on the remote control device 136. Although Figure 1 shows the remote control device 136 communicating messages via RF communication signals 102, the remote control device 136 can also communicate via wired communication. The remote control device 136 can be a wall switch, a dimmer, or another remote control device for controlling an electrical load. The system controller 140 can also originate one or more messages. System controller 140 can be configured to transmit one or more messages to the lighting control device 114 of the lighting fixture 110, the load controller 121, and / or the controllable light source 132 in response to messages received from associated control source devices, such as the occupancy sensor 134, the remote control device 136, the mobile device 150, and / or another control source device. System controller 140 can communicate with the lighting control device 114 in the lighting fixture 110, the load controller 121, and / or the controllable light source 132 via wired and / or wireless communication. For example, system controller 140 can communicate with the lighting control device 114 of the lighting fixture 110, the load controller 121, and / or the controllable light source 132 via RF communication signals 102.The system controller 140 can communicate with other lighting accessory lighting control devices (e.g., a group of lighting control devices, etc.) in the load control system 100. System controller 140 can communicate with mobile device 150 directly via wired and / or wireless communications. System controller 140 can communicate with mobile device 140 via a network communication device 142. Network communication device 142 can be a wireless access point, such as a wireless router and / or modem. Network communication device 142 can communicate with mobile device 150 via network communication signals 106 (e.g., network communication signals using the Wi-Fi protocol, WiMAX protocol, etc.) to enable mobile device 150 to communicate with other computing devices and / or networks (e.g., via the internet). System controller 140 can communicate with network communication device 142 via a communication link 144, which can be a wired and / or wireless communication link.Although system controller 140 and network communication device 142 are shown as separate devices in Figure 1, network communication device 142 may be included in system controller 140. Network communication device 142 may also be configured to communicate with a network device, such as a processing device 160 (e.g., personal computer and / or laptop), through a communication link 146, which may be a wired and / or wireless communication link. Mobile device 150 can be deployed to configure load control system 100. For example, mobile device 150 can be used to discover and / or associate load control devices (e.g., control source devices and / or control target devices) to perform load control. Mobile device 150 can be a cell phone (e.g., smartphone), a tablet, a personal digital assistant, a personal computer, a laptop, a wearable computing device (e.g., glasses, a watch, a bracelet, etc.), or another mobile computing device. Mobile device 150 can transmit a beacon message (e.g., a mobile device beacon message). The mobile device beacon message can include, for example, a beacon message identifier. For example, the beacon message identifier can be a unique identifier that identifies mobile device 150 (e.g., or an application running on mobile device 150) 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 the load control system 100 control devices. The mobile device beacon message can also include a Urssi discovery threshold.Control devices can receive the beacon message from the mobile device and compare the received signal strength amplitude, such as a Received Signal Strength Indicator (RSSI), at which the beacon message was received from the mobile device with the Urssi discovery threshold. A control device can enter configuration mode if the signal strength at which the beacon message was received from the mobile device is greater than or equal to the Urssi discovery threshold (e.g., the control device is within the mobile device's discovery range of 150). After entering configuration mode, the control device can transmit a beacon message.The control device may continue transmitting the control device beacon message as long as it receives the mobile device beacon message above the single-intensity discovery threshold (e.g., until the control device has completed control and / or configuration). If the control device stops receiving the mobile device beacon message, it may continue transmitting the control device beacon message for a specified period (e.g., 4 seconds) and may stop transmitting the control device beacon message once that period has ended. The 150 mobile device can discover control devices (e.g., control source devices and / or control target devices) after receiving control device beacon messages transmitted from the control devices. Control device beacon messages can be beacon messages transmitted from the control devices and include a unique identifier that identifies the corresponding control devices (e.g., control source devices and / or control target devices). For example, a control device beacon message might include a serial number or other unique identifier corresponding to a respective load control device. The unique identifier might be a unique network identifier (e.g., a routing locator). The beacon message might include an address (e.g., a network address), a join identifier (e.g., a network address), or a link identifier (e.g., a network address)., union ID) and / or any other type of device identification data. Control device beacon messages may additionally or alternatively include a unique device type identifier for the corresponding control device. For example, control device beacon messages may include an identifier for lighting control devices, sensors (e.g., occupancy sensors, etc.), remote control devices, and / or other types of control devices. Mobile Device 150 can adjust the Urssi discovery threshold based on the number of control device beacon messages it receives from control devices (e.g., the number of discovered control devices). Mobile Device 150 can adjust the Urssi discovery threshold so that the number of discovered control devices is within a target range (e.g.(between 15 and 25 devices). The target scope of discovered control devices can have a low-side threshold value and a high-side threshold value that defines the number of control devices in the discovery scope. The target scope of discovered control devices can be predefined and / or defined by a user of the mobile device 150. The target scope of discovered control devices can be modified based on, for example, the size of the load control system (e.g., the number of control devices in the load control system 100 and / or the physical size of the area in which the load control system 100 is located), the type of load control system 100 (e.g., residential or commercial), and / or the type of control devices in the load control system 100 (e.g., lighting fixtures or sensors).The Mobile Device 150 can adjust the Urssi discovery threshold transmitted by the Mobile Device beacon in an attempt to control the number of control devices transmitting control device beacon messages within a given area. For example, the Mobile Device 150 can determine if the number of discovered control devices is within the target range and adjust the Urssi discovery threshold to adjust the discovery range (e.g., the radius of the discovery range) and, therefore, the number of discovered control devices transmitting control device beacon messages. If the number of discovered control devices is within the target range, the Mobile Device 150 can maintain the Urssi discovery threshold. If the number of discovered control devices is less than the target range (e.g., fewer than 15 devices), the Mobile Device 150 can decrease the Urssi discovery threshold (e.g., to increase the radius of the discovery range). If the number of discovered control devices is greater than the target range (e.g., more than 25 devices), the Mobile Device 150 can increase the Urssi discovery threshold (e.g., decrease the radius of the discovery range). The amount by which the Mobile Device 150 increases or decreases the Urssi discovery threshold may depend on the number of discovered control devices.For example, the mobile device 150 can increase the Urssi discovery threshold by a smaller amount when the number of discovered devices is closer to the target range (e.g., the number of discovered control devices is between 26 and 40 control devices), and by a larger amount when the number of discovered devices is further from the target range (e.g., the number of discovered control devices is more than 40 devices). Mobile device 150 can initiate an adjustment timer when it increases the Urssi discovery threshold. If mobile device 150 again determines that the number of discovered control devices exceeds the target range, it can determine whether the adjustment timer has expired. If the adjustment timer has expired, mobile device 150 can increase the Urssi discovery threshold and initiate the adjustment timer. If the adjustment timer has not expired, mobile device 150 can maintain the Urssi discovery threshold for the duration of the adjustment timer. Using an adjustment timer can ensure that the mobile device accurately counts the number of detected control devices and can prevent it from adjusting the Urssi detection threshold too frequently when increasing the Urssi discovery threshold (e.g.,To prevent the mobile device from overcorrecting the Urssi discovery threshold, the mobile device 150 can adjust (e.g., increase or decrease) the Urssi discovery threshold by a predefined amount. This predefined amount can depend, for example, on the difference between the number of discovered control devices and the target range, and / or whether the mobile device 150 is increasing or decreasing the Urssi discovery threshold (e.g., if the number of discovered control devices is greater or less than the target range). The predefined amount can be greater when the mobile device 150 decreases the Urssi discovery threshold compared to when the mobile device 150 increases the Urssi discovery threshold. For example, the target range might be from 15 to 25 devices.If the number of discovered control devices is 10, the mobile device 150 can decrease the Urssi discovery threshold by approximately 2 dBm, while if the number of discovered control devices is 30, the mobile device 150 can increase the Urssi discovery threshold by approximately 1 dBm. To prevent a control device from fluctuating between identifying itself as being within and outside the discovery range over time, the control device can initiate a timer (e.g., a discovery timer) after determining that it is within the discovery range. The discovery timer can define a discovery period that ends when the timer reaches a predefined value (e.g., when the discovery period ends). The discovery period can be a time interval (e.g., 2 seconds, 4 seconds, 8 seconds, etc.) that begins when the control device receives a beacon message from the mobile device with a received signal strength amplitude (e.g.,The control device can determine if it was within range of discovery during the discovery period if it received a beacon message from the mobile device with a received signal strength amplitude (RSSI) greater than the Urssi discovery threshold. This allows the control device to maintain its status as a discovered device (e.g., by maintaining an IN-RANGE flag) during the discovery period. For example, after the control device receives a beacon message from the mobile device with a received signal strength amplitude (RSSI) less than the Urssi discovery threshold, the control device can determine if it was within range of discovery during the discovery period. For example, a control device might receive a first beacon message from the mobile device that includes a first Urssh discovery threshold at a first time point Ti. The control device might measure the received signal strength amplitude at which it received the first beacon message from the mobile device. If the received signal strength amplitude is greater than or equal to the first Urssh discovery threshold, the control device might determine that it is within discovery range, enter a configuration mode, and / or transmit a first beacon message. The control device might then initiate a discovery timer. The discovery timer might run for a discovery period (e.g., 2, 4, or 8 seconds).The control device can reset the discovery timer each time it receives a beacon message from the mobile device above a discovery threshold included in the mobile device's beacon message. The control device can then receive a second beacon message from the mobile device that includes a second discovery threshold, Urssi2, at a second time point, T2. The first discovery threshold, Urssh, and the second discovery threshold, Urssiz, can have the same value or different values. The control device can measure the received signal strength amplitude at which it received the second beacon message from the mobile device. If the received signal strength amplitude is less than the second discovery threshold, Urssi2, the control device can determine whether the discovery period has elapsed (e.g.,(if the discovery timer is running). If the discovery period has not yet elapsed, the control device may remain in configuration mode and may transmit a second beacon message with the Urssi discovery threshold indicated in the second beacon message, and / or one or more threshold offsets (e.g., the first threshold offset Udespi and / or the second threshold offset Udesp2). For example, the control device may subtract the second threshold offset Udesp2 from the Urssi discovery threshold, which may result in the outgoing discovery threshold Usalida (e.g., a decrease in the discovery threshold). For example, a beacon message may indicate an Urssi discovery threshold value of approximately -60 dBm, and the second threshold offset Udespz may be 5 dBm.Therefore, the control device can remain in configuration mode if it receives the second beacon message at an RSSI greater than or equal to -65 dBm, and exit configuration mode if it receives the second beacon message at an RSSI less than -65 dBm. Alternatively, the second beacon message can include the output discovery threshold Uintrate. In addition to using threshold offsets, the control device can use a discovery period when determining whether to exit configuration mode. As shown in Figure 8A, a control device may receive an initial beacon message from the mobile device that includes an initial discovery threshold value, Urssi. The initial threshold offset, Udespi, can be applied to the initial discovery threshold value, Urssi, such that the incoming discovery threshold, Uentrada, is greater than the received discovery threshold, Urssi. The control device can then determine that it received the initial beacon message from the mobile device at a received signal strength amplitude above the incoming discovery threshold, Uentrada. The control device can therefore determine that it is within discovery range and can enter configuration mode.The control device can start a timer or otherwise record the amount of time that has elapsed since the control device received the first beacon message from the mobile device. The control device may later receive a second beacon message from the mobile device that includes a second Urssi discovery threshold value. The second threshold offset Udesp2 can be applied to the second Urssi discovery threshold value so that the outgoing Usalida discovery threshold is lower than the Urssi discovery threshold. The control device may determine that it received the second beacon message from the mobile device at a received signal strength amplitude below the outgoing Usalida discovery threshold, indicating that the control device is out of discovery range and should exit configuration mode.However, the control device can remain in configuration mode if the amount of time that has elapsed since the control device received the first beacon message from the mobile device is less than a discovery period. Implementing hysteresis (e.g., in addition to or as an alternative to the discovery period) can prevent a situation where a control device at the edge of its discovery range rapidly enters and exits configuration mode due to fluctuations in the received signal strength amplitude at which successive beacon messages are received. Adding the first threshold offset Udespi to the discovery threshold Urssi (e.g., to determine the entry discovery threshold Uentrada) can make it less likely that a control device not currently in configuration mode will enter it. However, once the control device has entered configuration mode, subtracting the second threshold offset Udesp2 from the discovery threshold Urssi (e.g., to determine the entry discovery threshold Uentrada) can also reduce the likelihood of a control device not currently in configuration mode entering configuration mode.To determine the Usalida exit discovery threshold, the control device may be less likely to exit configuration mode due to relatively minor fluctuations in the signal strength at which beacon messages are received. Furthermore, as described herein, the mobile device 150 may adjust the Urssi discovery threshold based on the number of control devices in configuration mode (e.g., the number of control devices from which the mobile device 150 receives a beacon message) at any given time.If a control device rapidly alternates between entering and exiting configuration mode, the mobile device 150 may make a relatively large number of adjustments to the Urssi discovery threshold value. Therefore, using threshold offsets can reduce the number of unnecessary adjustments made to the Urssi discovery threshold value. Beacon messages from the control device can be transmitted via RF communication signals 104 from the control devices in the load control system 100. For example, beacon messages from the control device 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 other types of control devices.In addition, the control device's beacon messages can be transmitted via RF 102 signals. RF 102 and RF 104 communication signals can be wireless communication signals that communicate via a wireless communication protocol (e.g., via a standard protocol such as Zigbee, Z-Wave, Bluetooth, Bluetooth Low Energy (BLE), Wi-Fi, or Thread; via a proprietary communication protocol such as Clear Connect (e.g., Clear Connect Type A and / or Clear Connect Type X) and / or any suitable communication protocol). RF 102 and RF 104 communication signals can be of a different signal type (e.g., protocol, bandwidth, etc.).For example, RF communication signals 104 can communicate via a short-range wireless communication link using a short-range wireless communication protocol (e.g., such as BLUETOOTH and / or BLUETOOTH LOW ENERGY (BLE) protocols). RF communication signals 102 can communicate via a wireless network communication link using a wireless network communication protocol (e.g., such as CLEAR CONNECT and / or THREAD protocols), and / or any other suitable communication protocol 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., RF communication signals 102) can be used to control electrical loads during the operation of the load control system 100, and one of the RF communication signals (e.g., RF communication signals 104) to discover control devices and start the load control system 100. The RF communication signals 102 and 104 can be communicated through a communication circuit (e.g., transceiver) in the respective control devices, or through a separate beacon transmitter. Beacon transmitters for a control device can be integrated into, or located near, the control device to indicate the relative location of the corresponding control device transmitting the beacon messages. The RF communication signal 102 can be communicated through the same communication circuit as the RF communication signal 104, or through a different communication circuit. The network device 150 can transmit optical signals 109 via an optical transmitter 108. The optical transmitter 108 can be, for example, a laser pointer, and can be detached from the network device 150. For example, the optical transmitter can be inserted into a port (e.g., headphone jack, USB port, etc.) on the network device 150. The load control devices of the lighting fixtures (e.g., the load control device 114 of the lighting fixture 110, the load control devices 124a-124c of the lighting fixtures 120a-120c, and / or the internal load control device of the controllable light source 132 of the lighting fixture 130) can receive the optical signals 109 from the optical transmitter 108 (e.g., which can be attached to the network device 150 or another device).For example, lighting loads may comprise one or more internal detectors configured to provide optical feedback on the light emitted from the respective lighting load, and load control devices may be configured to receive optical signals 109 via the one or more internal detectors of the respective lighting loads. Furthermore, the load control devices of the lighting fixtures (e.g., the load control device 114 of the lighting fixture 110) may be configured to receive optical signal 109 via their respective sensors (e.g., sensor 116). For example, the sensors 116 may be capable of detecting different types of optical signals in the space. The load control devices of the lighting fixtures may record a reference ambient light level in an area where the lighting fixtures are located.The load control devices of the lighting fixtures may be able to detect an intensity at which an optical signal 109 is received from the network device 150 or another device capable of transmitting the optical signal 109. The load control devices for the lighting fixtures can receive optical signals 109 from the optical transmitter 108 (e.g., which may be connected to the network device 150 or another device). The load control devices for the lighting fixtures can determine the signal strength at which an optical signal 109 was received and can transmit an indication of the signal strength to the network device 150 (e.g., via the system controller 114 and the load controller 121, respectively). The optical signals 109 can be used as part of the configuration and / or control of the lighting fixture 110, the lighting fixtures 120a-120c, and / or the lighting fixture 130. The network device 150 can select a lighting fixture for configuration and / or control based on the signal strength indications.For example, network device 150 can select a lighting fixture 110 for configuration and / or control based on a determination that the optical signal 109 was received at the internal detectors of the lighting loads 112 and / or sensor 116 with the highest signal strength (e.g., the highest normalized signal strength). The internal detectors of the lighting loads and / or sensor 116 can be used to record the reference ambient light levels in the areas where the lighting fixture 110 and the lighting fixtures 120a-120c are located, respectively. The signal strengths can be indicated as normalized signal strengths (e.g., relative to the respective reference ambient light levels). The load control system 100 may include one or more beacon transmitters, which may be location beacon transmitters, such as a beacon transmitter 180. The beacon transmitter 180 (e.g., the location beacon transmitter) may be located at a workstation 182. The location beacon transmitter may communicate a beacon message (e.g., a location beacon message) via RF communication signals 102 and / or 104. The beacon message transmitted by the location beacon transmitter may include a beacon message that communicates a unique identifier. The beacon message may be associated with a location where the location beacon transmitter resides, such as workstation 182, an office, a conference room, part of an office or conference room, or another location. The beacon message transmitted by the location beacon transmitter may include a unique identifier that the mobile device 150 and / or the system controller 140 can associate with a physical location where the location beacon transmitter resides. If multiple location beacon messages are detected, the user can associate the unique identifier of the beacon message with the strongest signal strength with the nearest physical location. The physical location can also be determined, either additionally or alternatively, from the geolocation of the mobile device 150. The mobile device 150 can discover the beacon message transmitted by the location beacon transmitter to configure and / or control one or more control devices in the load control system. For example, the mobile device 150 can discover the beacon message transmitted by the location beacon transmitter and associate the unique identifier of the beacon message with the discovered unique identifier of one or more beacon messages from the control device (e.g., beacon messages transmitted by the control devices). The control devices associated with the unique identifier of the beacon message transmitted by the location beacon transmitter can be collectively controlled when the location beacon transmitter is discovered by the mobile devices. Beacon messages can be transmitted from the control devices and / or the location beacon transmitter periodically, or in response to a triggering event. The triggering event can be the reception of a message. The triggering event can be sent in a 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 can automatically control the communication of beacon messages by transmitting a message based on a periodic triggering event (e.g., the completion of a timer). In response to a message, the control devices and / or the location beacon transmitter can enter a configuration mode and begin transmitting beacon messages.The message can trigger a beacon message transmission or the periodic transmission of beacon messages over a period of time. Beacon message transmission can be triggered by a message transmitted on the same or different RF communication signals, protocols, and / or channels. For example, beacon message transmission can be triggered by an optical signal. For devices capable of bidirectional communication on RF communication signal 104, the mobile device 150 can send a message to devices on RF communication signal 104, causing them to transmit beacon messages on RF communication signal 102. Since beacon message transmission can also be performed as unidirectional communication from a control device, it can be triggered by a message sent on a different communication protocol and / or using a different communication signal.For example, control devices can receive a message via RF communication signals 102 that triggers the transmission of beacon messages from the control devices in the load control system via RF communication signals 104. The message that triggers the transmission of beacon messages can be communicated to the control devices and / or the location beacon transmitter directly or indirectly through another device. For example, mobile device 150 can send a message to system controller 140 to trigger beacon messages from the control devices in the load control system. Another message can be sent from system controller 140 using RF communication signals 102 to trigger the transmission of beacon messages from the control devices and / or the location beacon transmitter. Control devices configured to receive RF communication signals 102 can then begin transmitting beacon messages using RF communication signals 104. The triggering event can be a button press on a device. One-way and / or two-way communication devices can transmit beacon messages in response to a button press on the device. The device identifier (e.g., device identification data) received in a device's beacon messages can be used to determine the device identifier for communicating with the device on another network or network protocol. For example, mobile device 150 might receive the beacon message from lighting fixture 110 via RF communication signals 102, and the unique identifier in the beacon message might correspond to the unique identifier for communicating with the lighting fixture on another network using RF communication signals 104. The unique identifier on each network or network protocol might have a different format, but it may include a portion of the identifier (e.g., the primary identifier) ​​that is reassigned on each network to support the communication facility. Mobile device 150 can interpret the information received in beacon messages and perform the commissioning and / or control of the load control system 100, or mobile device 150 can send the information to another device to enable commissioning and / or control. For example, mobile device 150 can send the information received in beacon messages and / or user input received on mobile device 150 to system controller 140 to configure and / or control the load control system 100. By activating the load control system 100, the mobile device 150 and / or the system controller 140 can classify the received beacon messages into a list. The mobile device 150 and / or the system controller 140 can sort the list based on a range method. For example, mobile device 150 and / or system controller 140 can sort the list based on the Received Signal Strength Indicator (RSSI) of each beacon message. The control device that transmitted the beacon message with the highest RSSI will be first in the list. Mobile device 150 can discover beacon messages and determine beacon message identifiers. Mobile device 150 and / or system controller 140 can select the beacon message identifiers to be configured and / or controlled. Each discovered beacon message can be selected for configuration and / or control, or beacon messages discovered above a certain discovery threshold can be selected for configuration and / or control. The discovery threshold can define a discovery scope (e.g., an area around mobile device 150 and / or system controller 140 in which control devices can be discovered). Mobile device 150 and / or system controller 140 can group control devices identified through beacon messages and associate the devices to enable load control in load control system 100.The mobile device 150 and / or the system controller 140 can automatically add the identifiers of the selected beacon messages to a group of control devices to be associated to enable load control. One or more lighting fixtures can be configured and / or controlled using optical signals (e.g., optical signals 109). The lighting fixtures (e.g., lighting fixture 110, lighting fixtures 120a-120c, and / or lighting fixture 130) can receive optical signals 109 from the optical transmitter 108 (e.g., which may be connected to network device 150 or another device). For example, the lighting fixtures can be configured to receive the optical signal through the internal detectors of the lighting loads of the lighting fixtures and / or their respective sensors (e.g., sensors 116). A lighting fixture can provide feedback to indicate that it has received optical signals 109. For example, the lighting fixture can cause a respective lighting load to illuminate in a first color.Lighting accessories can measure the respective signal strengths at which optical signals 109 are received and can transmit respective indications of these signal strengths (e.g., as part of a beacon message). For example, signal strengths can be indicated as normalized signal strengths (e.g., relative to respective reference ambient light levels). The network device 150 (e.g., or the system controller 140) can select one or more lighting fixtures for configuration and / or control based on signal strength indications. For example, the network device 150 can select a lighting fixture that received the highest signal strength from optical signal 109 for configuration and / or control. The selected lighting fixture can provide feedback to indicate that it has been selected for configuration and / or control. For example, the lighting fixture can cause a respective lighting load to illuminate in a second color. Once the configuration and / or control of the selected lighting fixture is complete, the network device 150 can select another lighting fixture (e.g.,, which received optical signal 109 at the second highest signal strength) for configuration and / or control. 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, lighting fixtures may cause a respective lighting load to illuminate in a third color. The control configuration parameters for the control device group can be configured on the mobile device 150 and / or the system controller 140 based on user input received through a user interface 152 on the mobile device 150. The mobile device 150 can display the lighting control configuration 190 on the user interface 152. For example, the lighting control configurations 190 can include default settings 192, zone settings 194, occupancy settings 196, and / or schedule settings 198 that can be configured for the control device group. The mobile device 150 can display the dimmer 199 on the user interface 152.For example, dimmer 199 can be used to control one or more lighting fixtures in real time and / or to set lighting levels for one or more of the default settings 192, zone settings 194, occupancy settings 196, and / or schedule settings 198. For example, the dimmer can be used to decrease a lighting level for one or more lighting fixtures at a particular time of day. The default settings 192 can be configured by adjusting the intensity level of one or more lighting fixtures using a virtual slider 199 (e.g., a virtual dimmer) and storing the configuration parameters. A user can select the default settings 192 in the user interface 152 to set an intensity level for one or more lighting fixtures to be controlled according to the default parameter.The different default parameters can be configured to set different lighting fixtures with different lighting levels for different occasions, such as a bedtime default parameter for when a user goes to sleep, a movie default parameter for when a user is watching TV or a movie, an away parameter when a user is not in the building, a home default parameter when the user is in the building, or any other default parameter that a user can define for an occasion. A user can select zone settings 194 in user interface 152 to define one or more zones of lighting fixtures to be controlled. Control devices that are discovered and added to a group as described herein can each be included in a zone, so that the group identifier (e.g., the temporary group identifier) ​​is also a zone identifier, or the zone identifier can indicate a subset of devices that have been discovered and added to a device group for configuration and / or control. Different zones can be controlled separately by sending lighting control instructions to a zone to establish zones with different lighting levels.The associated device identifiers of the lighting fixtures identified in a zone can be stored on the mobile device 150 and / or the system controller 140 as a defined zone configuration 194 to control the lighting fixtures in the defined zone. Zone configurations 194 can be sent in messages to the system controller 140 and / or the lighting fixtures in the defined zone to be stored for the purpose of controlling the lighting fixtures according to the zone configurations 194. A user can select occupancy settings 196 in user interface 152 to define one or more lighting fixtures to be controlled based on the occupancy or vacancy of a space. Different lighting fixtures can be controlled at different illumination levels in response to occupancy and / or vacancy commands received from an occupancy sensor, such as occupancy sensor 134. A user can select schedule settings 198 in user interface 152 to define a schedule for one or more lighting fixtures. Different lighting fixtures can be controlled at different illumination levels (e.g., on / off, a predefined intensity level, etc.) according to a schedule that can be monitored by system controller 140. Figure 2A illustrates a representative load control environment 202 in which a load control system 200 (e.g., the load control system 100 shown in Figure 1) can be implemented to configure and / or control one or more control devices using beacon messages and / or an optical signal. The load control system 200 may include a plurality of lighting fixtures 210a-210d (e.g., lighting device 110 and / or lighting device 130). Each of the lighting fixtures 210a-210d may comprise one or more lighting loads (e.g., lighting loads 112) and a lighting control device (e.g., lighting control device 114) to control the intensity and / or color of the lighting loads of the respective lighting fixture.Lighting fixtures 210a-210d may also each comprise a controllable light source, such as the controllable light source 132 shown in Figure 1. The lighting control devices of lighting fixtures 210a-210d may function as control target devices to control the respective lighting loads in response to a. MA / t / ZUZÓ / UUΊ the messages received from the control source devices. The control source devices of the load control system 200 may comprise an occupancy sensor 234 (e.g., occupancy sensor 134), a remote control device 236 (e.g., remote control device 136), and sensors 216a-216d mounted on the respective lighting fixtures 210a-210d (e.g., sensor 116). The sensors 216a-216d may be occupancy sensors, visible light sensors (e.g., cameras), sunlight sensors, optical sensors, and / or any other type of sensor. For example, one or more of the occupancy sensor 234 and / or the sensors 216a-216d may be visible light sensors (e.g., cameras). The load control system 100 may also comprise a system controller 240 (e.g., the system controller 140) and a network device, such as a mobile device 250 (e.g., the mobile device 150), which can also function as a control source device. For example, mobile device 250 can comprise a smartphone and / or a tablet. As shown in Figure 2A, control devices (e.g., the lighting control device of lighting fixture 210a) can be selected for configuration and / or control and can provide feedback to a user 205 (e.g., an installer) to identify the devices that have been selected for configuration and / or control. Control devices can be assigned and / or associated with configuration identifiers (e.g., zone or group identifiers by being connected to a network) from configuration data to enable load control in the load control environment 201. The configuration identifier can be a fixture, group, zone, area, and / or location that can be defined by the configuration data (e.g., lighting control configuration information) generated by the design software.For example, feedback can be provided by a control device to indicate that the control device is ready for attribution, has been selected for attribution, and / or has been attributed. A control device can be attributed by selecting a configuration identifier to associate with it. The control device being attributed can transmit a unique identifier (e.g., a serial number) to the 250 mobile device. The control device can be associated with the configuration identifier by creating an association between the configuration identifier and the control device's unique identifier. The mobile device can store the unique identifier, as well as information about the association between the configuration identifier and the control device, in the configuration data.After a control device is assigned, it can be joined to a network and / or configured and / or controlled by user 205. For example, user 205 can send one or more commands to a control device via the mobile device. During the process of assigning control devices and / or associating them with configuration data identifiers, the control devices can be configured to communicate with the mobile device 250 via a first wireless communication medium (e.g., via RF communication signals 204 using a short-range wireless communication protocol). During normal operation of the load control system 200, the control devices can be configured to communicate with each other via a second wireless communication medium (e.g., via RF communication signals 202 transmitted over a wireless communication network). After assignment, the control devices can be configured to join the wireless communication network.For example, control devices can join the wireless communication network by transmitting the association between the control device and the configuration identifier to a remote device. Once the control devices have joined the wireless communication network, they can communicate with each other during normal operation. Configuration data can define the operation and / or functionality of the load control system 200. This configuration data can include representations of the control devices (e.g., lighting fixtures 210a-210d, occupancy sensor 234, remote control devices 236, sensors 216a-216d, etc.) within the load control system 200, as well as the configuration identifiers (e.g., fixtures, groups, zones, areas, and / or locations) of the control devices. For example, the configuration data can define the functionality of the control devices, such as how the lighting fixtures 210a-210d respond to the occupancy sensor 234 and / or the remote control device 236. The configuration data can be configured using design software executed by a processing device (e.g.,The processing device 160, for example, can be used before the control devices are assigned and / or associated with the corresponding control device configuration identifier in the configuration data. Furthermore, the configuration data can be configured, for example, by the mobile device 250 while the mobile device is assigning and / or associating the control devices with the control device configuration identifier in the configuration data. The configuration data can then be transmitted to the control devices via the wireless communication network after the control devices have joined the wireless communication network. The mobile device 250 can be configured to assign control devices (e.g., lighting control devices for lighting fixtures 210a-210d, occupancy sensor 234, and / or remote control device 236) and / or associate control devices with a control device configuration identifier in the configuration data. Sensors 234a-234d can be used for assigning and / or associating control devices for configuration and / or control. User 205 can put the mobile device 250 into a configuration mode (e.g., an assignment mode and / or an association mode). For example, user 205 can press a button on the mobile device 250 to put it into configuration mode. In configuration mode, the mobile device 250 can discover beacon messages from control devices in the load control environment 201.As described herein, a control device can be attributed by associating a unique control device identifier with a configuration identifier. The mobile device 250 can transmit (e.g., periodically) a beacon message (e.g., a mobile device beacon message) after entering configuration mode. The mobile device 250 can transmit the mobile device beacon messages over the first wireless communication medium 204 (e.g., over a short-range wireless communication link using a short-range wireless communication protocol). The mobile device beacon message can include, for example, a beacon message identifier. For example, the beacon message identifier can be a unique identifier that identifies the mobile device 250 (e.g.or an application running 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 the load control system control devices 200. The mobile device beacon message may also include a discovery threshold. The control devices may receive the mobile device beacon message and may compare a Received Signal Strength Indicator (RSSI) from the received mobile device beacon message with the discovery threshold. For example, the Received Signal Strength Indicator may be the signal strength at which the mobile device beacon message was received.Each control device can enter configuration mode when the mobile device's beacon message identifier matches a specific beacon message identifier and / or the received signal strength indicator is greater than or equal to the discovery threshold (e.g., the control device is within the mobile device's discovery range). For example, the specific beacon message identifier can be predefined and / or stored in the control device's memory. The mobile device can adjust the discovery threshold included in the mobile device's beacon message to adjust the mobile device's discovery range. After entering configuration mode, the control devices (e.g., lighting control devices of lighting fixtures 210a-210d) can each transmit (e.g., periodically) a control device beacon message. The control devices can transmit the control device beacon messages via the first wireless communication medium 204. Each control device beacon message can include the unique identifier of the control device that transmitted the respective beacon message. Furthermore, the control devices can be prepared to be assigned by the mobile device 250 after entering configuration mode. After entering configuration mode (e.g., in response to receiving the mobile device beacon message), the control devices (e.g.Lighting accessories 210a-210d can provide feedback to user 205 to indicate that control devices are ready to be assigned. This feedback can be provided by changing a lighting load state in lighting accessory 210a. For example, lighting accessory 210a can change to a first color (e.g., orange) after entering configuration mode (e.g., in response to receiving the beacon message from the mobile device) to indicate to the user that the control device is within the mobile device's discovery range 250 and is ready to be assigned.In addition, feedback can be provided by flashing the lighting load, increasing and / or decreasing the intensity level of the lighting load, increasing and / or decreasing the color temperature of the lighting load, and / or other visual feedback provided to the user 205. The type of feedback can be indicated in the mobile device beacon message transmitted by the mobile device 250 and / or can be preprogrammed and stored in the control device (e.g., lighting accessories 210a-210d). As user 205 moves around the load control environment 201 with mobile device 250, the control devices within the mobile device's discovery range may change. When control devices (e.g., lighting control devices for lighting fixtures 210a-210d) begin receiving the beacon message from the mobile device as the user moves, those control devices may enter configuration mode (e.g., prepare to be assigned), begin transmitting their control device beacon message, and provide feedback (e.g., change to the first color). Furthermore, when control devices are outside the discovery range of mobile device 250 and / or outside the mobile device's wireless range (e.g.,As the user moves, these control devices may exit configuration mode after a timeout (e.g., one minute). As a result, these control devices stop transmitting their beacon message from the control device and cease providing feedback (e.g., they power down). The 250 mobile device can receive control device beacon messages from one or more control devices. For example, the 250 mobile device can receive the control device beacon message from the lighting control device of lighting fixture 210a and select that lighting control device for allocation (e.g., to join). (ML / t / ZUZO / UU 1 the network). The Mobile Device 250 can classify received control device beacon messages based on the received signal strength indicators of the respective control device beacon message. For example, the Mobile Device 250 can select the lighting control device of lighting fixture 210a to be assigned if the received signal strength indicator of that lighting control device's beacon message is the highest received signal strength indicator of the received control device beacon messages. The Mobile Device 250 can send a connection message to the control device upon receiving a beacon message from the control device at the maximum received signal strength. For example, the Mobile Device 250 and the control device can be configured to establish a connection (e.g., a bidirectional communication connection) in response to the control device receiving the connection message from the Mobile Device 250. Furthermore, the connection message can inform the control device that the control device has been discovered and selected for allocation. For example, the connection message can be sent via RF communication signals 204 (e.g., directly from the Mobile Device 250). For instance, the Mobile Device 250 can connect to only one control device at a time (e.g., to select a single control device for allocation). In response to receiving the connection message, the control device (e.g., lighting fixture 210a) can provide feedback to user 205 to indicate that lighting fixture 210a has been selected for assignment. This feedback can be provided by changing the lighting load state of lighting fixture 210a. For example, lighting fixture 210a might change to a second color (e.g., blue) after entering configuration mode (e.g., in response to receiving the beacon message from the mobile device) to indicate to the user that the control device is selected for assignment. As shown in Figure 2A, lighting fixture 210a might illuminate in the second color, while the other lighting fixtures 21 Ob-21 ​​Od might illuminate in the first color.In addition, feedback can be provided by flashing the lighting load, increasing and / or decreasing the intensity level of the lighting load, increasing and / or decreasing the color temperature of the lighting load and / or other visual feedback provided to the user 205. The type of feedback can be indicated in the mobile device connection message 250 and / or can be preprogrammed and stored in the control device (e.g., lighting accessories 210a-210d). As user 205 moves around the load control environment 102 with mobile device 250, the signal strength indicators received from the control device's beacon messages by the mobile device may change. As a result, the control device beacon message with the highest received signal strength indicator provides feedback (e.g., by turning to the second color). Mobile device 250 can be configured to break the connection with the previous control device (e.g., by sending a message to the previous control device), which can stop the feedback (e.g., changing from the second color to the first color, since the control device may still be within the mobile device's discovery range).Furthermore, the 250 mobile device can transmit a connection message to the new control device that has received a beacon message from the control device with the maximum received signal strength. Therefore, that control device can be selected to be assigned and begin providing feedback (e.g., changing to the second color). The mobile device 250 can transmit (e.g., periodically) optical signals (e.g., optical signals 109) after entering configuration mode. The mobile device 250 can transmit the optical signal via an attached optical transmitter (not shown). The control devices can receive the optical signal via internal detectors in the lighting loads of the lighting fixtures 210a-210b and / or sensors (e.g., sensors 216a-216d), and can measure the intensity of the received optical signal. Each control device can enter configuration mode upon receiving the optical signal, or the control devices can enter configuration mode before receiving the optical signal. After entering configuration mode, the control devices (e.g., lighting fixtures 210a-210d) can provide feedback to the user 205 to indicate that the control devices are ready to be assigned. This feedback can be provided by changing the state of the lighting load in lighting fixture 210a. For example, lighting fixture 210a can change to a first color (e.g., orange) after entering configuration mode (e.g., in response to receiving optical signals) to indicate to the user that the control device has received the optical signals and is ready to be assigned.In addition, feedback can be provided by flashing the lighting load, increasing and / or decreasing the intensity level of the lighting load, increasing and / or decreasing the color temperature of the lighting load and / or other visual feedback provided to the user 205. The type of feedback can be preprogrammed and stored in the control device (e.g., lighting accessories 210a-210d). After entering configuration mode, the control devices (e.g., lighting control devices of lighting fixtures 210a-210d) can each transmit (e.g., periodically) an indication of the signal strength at which one or more of the optical signals were received. The control devices can transmit the indications via the first wireless communication medium 204. Each indication can include the unique identifier of the control device that transmitted the optical signals. Furthermore, the control devices can be prepared to be assigned by the mobile device 250 after entering configuration mode. As user 205 moves around the load control environment 201 with the mobile device 250, the control devices receiving optical signals may change. One or more control devices not receiving optical signals may be in configuration mode. When control devices (e.g., the lighting control devices of lighting fixtures 210a-210d) in configuration mode begin receiving optical signals as the user moves, these control devices may begin transmitting their signal strength indication and providing feedback (e.g., turning to the first color). Furthermore, when control devices stop receiving the optical signal as the user moves, these control devices may stop transmitting their signal strength indications and cease providing feedback (e.g., turning to the first color)., turn off) after a waiting time (e.g., one minute). The mobile device 250 can receive signal strength indications from one or more control devices. For example, the mobile device 250 can receive signal strength indications from the lighting control device of lighting fixture 210a and select that lighting control device for allocation (e.g., to join the network). The mobile device 250 (e.g., and / or the system controller 240) can select a lighting control device for allocation based on signal strength indications. For example, the mobile device 250 can select the lighting control device of lighting fixture 210a for allocation if lighting fixture 210a received the optical signal at maximum signal strength. The Mobile Device 250 can send a connection message to the selected control device. For example, the Mobile Device 250 and the control device can be configured to establish a connection (e.g., a bidirectional communication connection) in response to the control device receiving the connection message from the Mobile Device 250. Additionally, the connection message can inform the control device that it has been discovered and selected for allocation. For example, the connection message can be sent via RF communication signals 204 (e.g., directly from the Mobile Device 250). For instance, the Mobile Device 250 can connect to only one control device at a time (e.g., to select a single control device for allocation). In response to receiving the connection message, the control device (e.g., lighting fixture 210a) can provide feedback to user 205 to indicate that lighting fixture 210a has been selected for allocation. This feedback can be provided by changing the lighting load state of lighting fixture 210a. For example, lighting fixture 210a can change to a second color (e.g., blue) after entering configuration mode (e.g., in response to receiving the connection message) to indicate to the user that the control device is selected for allocation. As shown in Figure 2A, lighting fixture 210a can illuminate in the second color, while the other lighting fixtures 210b–210d can illuminate in the first color.In addition, feedback can be provided by flashing the lighting load, increasing and / or decreasing the intensity level of the lighting load, increasing and / or decreasing the color temperature of the lighting load, and / or other visual feedback provided to the user. The type of feedback can be indicated in the mobile device connection message and / or can be pre-programmed and stored in the control device (e.g., lighting accessories). A lighting accessory for which configuration and / or control has been completed can provide feedback to indicate that the lighting accessory has been configured and / or controlled. For example, lighting accessories can cause a respective lighting load to illuminate in a third color. When the desired control device (e.g., the lighting control device of lighting fixture 210a) is selected for assignment (e.g., mobile device 250 is connected to the lighting control device and the lighting fixture is set to the second color), user 205 can press a button (e.g., a programmable or virtual button displayed on a user interface 252 of mobile device 250) on the mobile device 250 to assign (e.g., and / or associate) the selected lighting control device. For example, user 205 can select a zone or group (e.g., displayed on mobile device 250) to associate with the selected lighting control device in order to assign that lighting control device. Therefore, assignment and association can occur simultaneously.The Mobile Device 250 can transmit an assignment message to the selected lighting control device in response to the selection of the zone or group on the Mobile Device, indicating that the control device has been assigned and / or associated. Additionally, the selected lighting control device can transmit a confirmation message (e.g., an assignment confirmation message) to the Mobile Device 250 in response to receiving the assignment message. The assignment confirmation message can include a unique identifier (e.g., a serial number) of the selected lighting control device. In response to attribution (e.g., upon receiving the attribution message), the control device (e.g., lighting fixture 210a) can provide feedback to user 205 to indicate that lighting fixture 210a has been attributed (e.g., to join the network). This feedback can be provided by changing the state of the lighting load in lighting fixture 210a. For example, lighting fixture 210a might change to a third color (e.g., green) after attribution. Additionally, feedback can be provided by flashing the lighting load, increasing and / or decreasing the intensity level of the lighting load, increasing and / or decreasing the color temperature of the lighting load, and / or other visual feedback provided to user 205.The type of feedback can be indicated in the attribution message of the mobile device 250 or can be preprogrammed and stored in the control device (e.g., lighting accessories 21 Oa-21 Od). In response to its assignment, the control device can exit configuration mode and enter a joining mode. In joining mode, the control device can cease continuously transmitting (e.g., periodically transmitting) the control device beacon message on the first wireless medium 204. For example, the control device can periodically switch between the first wireless medium 204 and the second wireless medium 204 (e.g., the wireless network). The control device can monitor the wireless network 202 to determine if a request to join the wireless network is being transmitted on that network. The control device can continue to periodically transmit the control device beacon message over the first wireless medium (e.g., the wireless network).(at a slower speed than in configuration mode) in case the mobile device 250 needs to reconnect to the control device while the mobile device is in configuration mode. After the control devices have joined the wireless communication network 202, the configuration data can be transmitted to the control devices via the wireless communication network. Figure 2B illustrates a sample network 260 that can enable communication between devices in a load control system (e.g., load control system 100 and / or load control system 200). The network 260 can include any network suitable for facilitating communication within a load control system or an Internet of Things (IoT) environment. The various control devices in load control system 200 can communicate with each other via the network 260. As shown in Figure 2B, the network 260 can comprise a single network partition. Alternatively, the network 260 can be an example of a network partition (e.g., a subnet) within a larger network. For example, the network 260 can be an example of a network partition in a larger network composed of multiple network partitions.The 260 network is an illustrative network and the techniques described herein can be applied to other networks, for example, to include more or fewer devices than the 260 network. The circled nodes in Figure 2B can represent devices connected to network 260 and coupled to other devices in network 260 (e.g., the various control devices of load control system 100 and / or load control system 200). A device coupled to at least one other device in network 260 can communicate with other devices (e.g., those coupled to another device in network 260). Communication in network 260 can be facilitated by links (e.g., auxiliary devices) established in network 260. With reference to Figure 2B, the links between devices can be indicated by lines (e.g., solid and dashed lines) connecting the respective devices. One or more of the devices shown in Figure 2B can join the 260 network through a join procedure. The 260 network can be a mesh network, and each device can exchange network credentials with a launching device (e.g., the system controller or mobile device) that allows the device to join the 260 network and enables it to communicate on the 260 network. A device may be able to communicate with other devices using another wireless protocol, but it may not be able to communicate with, or join, other devices on the 260 network without the network credentials. The network credentials can include a join identifier (e.g., or any other identifier) ​​that the device can use to join the 260 network and communicate with another device. A device can be assigned (e.g., through an assignment procedure) before joining the 260 network. For example, the assignment procedure can be used to identify devices (e.g., individual devices and / or groups of devices) to join the 260 network. As part of the assignment procedure, a device can exchange credentials with a commissioning device to enable the device to communicate on the 260 network. Without this credential exchange, the device might not obtain the join ID and would not be able to communicate on the 260 network. Devices connected to at least one other device in network 260 can adopt and / or be assigned a respective role in the network. For example, roles can include: a leader device (e.g., leader device 262), a router device (e.g., router devices 264a-264d), and / or a terminal device (e.g., terminal devices 266a and 266b). A device's role can indicate its functions and / or capabilities with respect to network 260. As illustrated in Figure 2B, network 260 can include a leader device 262. The leader device 262 can manage other devices connected to network 260. For example, the leader device 262 can assign and maintain router identifiers (e.g., router IDs) for each of the router devices 264a-264d. For example, a unique router identifier can be assigned to each of the router devices 264a-264d. The leader device 262 can assign and maintain roles for other devices. The leader device 262 can be configured as a gateway for network 260. For example, the leader device can be a device that facilitates communication (e.g., routes and receives messages) between network 260 and other networks or network partitions. With reference to Figure 2A, a system controller (e.g., the 240 system controller shown in Figure 2A) can be an example of a leading device 262.Furthermore, a device in a load control system that is capable of being assigned the role of a router device can be assigned the role of the leader device (e.g., a control device). Network 260 can include one or more 264a-264d router devices. The 262 leader device can be compatible with and coupled to multiple router devices (e.g., more than 30 router devices). The 262 leader device can function as a router device. The 264a-264d router devices in network 200 (e.g., coupled to the 262 leader device in network 260) can communicate with each other, for example, to form a mesh network. The 264a-264d router devices can communicate with each other (e.g., as indicated by the solid lines connecting the 264a-264d router devices). Router devices 264a-264d can be in communication with the leader device 262, either directly or through one or more other router devices (e.g., as indicated by the solid lines connecting the leader device 262 to router devices 264a and 264c).Router devices 264a-264d can receive and route messages to other devices on the 260 network (e.g., terminal devices 266a, 266b). For example, router devices 264a-264d can receive / transmit messages between devices, or among themselves, to communicate messages received from one device connected to another router device. With reference to the load control system 200 shown in Figure 2A, a device that, for example, receives power externally via an AC current (e.g., a non-battery-powered device) can 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-210d can be assigned the role of router devices. Network 260 may include one or more terminal devices 266a, 266b (e.g., full or minimal terminal devices). Each terminal device 266a, 266b may be coupled to another device (e.g., a primary device) in network 200 and may transmit and / or receive messages through a coupled router device 264a-264d. For example, terminal devices 266a, 266b may each transmit an address (e.g., a network address), a join identifier (e.g., for network authentication), and / or other types of device identification data to one or more router devices 264a-264d. Although Figure 2B illustrates two terminal devices 266a, 262b and each is connected to different router devices, each router device 264a-264d can support multiple terminal devices (e.g., more than 500 terminal devices). With reference to the load control system 200 in Figure 2A, the system controller 240, the input devices (e.g., the remote control device 232 and / or the occupancy sensor 230) and / or the load control devices (e.g., the lighting control devices of the lighting fixtures 210a-210d) can be examples of the terminal devices 266a, 266b shown in Figure 2B. The lead device 262 can update the roles (e.g., or confirm role updates) of devices communicating on network 260, for example, based on changes in network 260. For instance, a device might be assigned a specific role when it joins network 260, and the lead device 262 can update that role based on changes in network conditions. These changes might include increased message traffic, additional devices connecting, changes in signal strength, and so on. Updates to a device's assigned role can be based on the device's capabilities. The lead device 262 can update a device's role to that of a router by assigning a router ID to the device. Devices connected to other devices in the 260 network can function as primary and secondary devices. The lead device (e.g., lead device 262) and the router devices (e.g., router devices 264a-264d) connected to one or more terminal devices (e.g., terminal devices 266a, 266b) can function as primary devices. Terminal devices (e.g., terminal devices 266a, 266b) connected to a lead device (e.g., lead device 262) and / or a router device (e.g., one of the router devices 264a-264d) can function as secondary devices. As primary devices, the leader device 262 and the router devices 264a-264d can each be coupled to one or more secondary devices (e.g., one or more of the terminal devices 266a, 266b, as described herein).Furthermore, the lead device 262 and the router devices 264a-264d can store and / or forward messages sent by their respective coupled secondary devices. For example, the lead device 262 and the router devices 264 can receive messages from their respective secondary devices and route the received messages to the intended receiving device (e.g., either directly or via the respective primary device of the intended receiving device). Similarly, the lead device 262 and the router devices 264a-264d can receive messages intended for their respective secondary devices and route the message to the appropriate secondary device. As shown in Figure 2B, the relationship (e.g., coupling) between a secondary device and its respective primary device can be indicated by dashed lines. Router device 264a can receive messages intended for terminal device 266a and forward the message to terminal device 266a. Because router device 264a is configured as the primary device of terminal device 266a, terminal device 266a can transmit messages 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 then route the message to router device 264b (e.g.,The primary device of terminal device 266b) and the router device 264b can then forward the message to terminal device 266b. In network 260, the routers (e.g., the lead device 262 and routers 264a-264d) can periodically transmit advertisement messages indicating their presence on the network. These advertisement messages can be used to calculate the cost and / or quality of communications on network 260. Each router can receive an advertisement message that includes an identifier of the transmitting router and measures the Received Signal Strength Indicator (RSSI) of the received advertisement message. The Received Signal Strength Indicator can be used to calculate the link quality at which the advertisement message is received (e.g., Link Quality Index (LQI)). Each router (e.g., the lead device 262 and routers 264a-264d) can send an advertisement message as a multicast message.Advertisement messages transmitted by a router can be received by neighboring routers that share a single-hop communication link with the transmitting router. A single-hop communication link can transmit messages (e.g., digital messages) from one router via unicast and / or multicast communication directly to another router. For example, routers 264a and 264c can be neighboring devices that share a single-hop communication link with the lead router 262, since routers 264a and 264c can send digital messages directly to and / or receive digital messages directly from the lead router 262.A single-hop communication link can be a communication link in which router devices can directly receive advertisement messages above a certain link quality (e.g., LQI greater than 0). After a router receives a periodic advertisement message from another router, it can calculate the link quality (e.g., LQI) of the communication link through which the advertisement message is received. The LQI can be calculated as a predefined number within a range that indicates different link qualities for the communication link between the two devices. For example, the LQI can be indicated by values ​​of 0, 1, 2, or 3. Different LQI values ​​can be assigned based on the RSSI of the received advertisement message and a link margin relative to a predefined reception level. A secondary device can receive advertisement messages from a primary router or from a router other than the primary device of the secondary device (e.g.,(a primary auxiliary device or a router device that is not a primary auxiliary device of the secondary device). For example, the router device can broadcast advertisement messages to allow other control devices to determine that a network has been formed and that the device listening for the advertisement message can attempt to connect to the router (e.g., to communicate across the network). Devices can receive and track the advertisement messages broadcast by routers to determine if the device can communicate across the network. In addition, or alternatively, the advertisement messages broadcast by a respective router can provide other routers with the ability to measure a communication signal (e.g., RSSI) between the respective routers connected to the network (e.g., which the routers can use to update their respective routing tables or routing information).As described herein, the secondary device can measure a received signal strength indicator (RSSI) of received advertisement messages. Secondary devices can create and maintain a table of auxiliary primary devices. This table can include a list of auxiliary primary devices with which a respective secondary device is configured to communicate (e.g., synchronized with and / or enabled to receive multicast messages). Additionally, the table can include an indication of the received signal strength (e.g., an RSSI) for each of the secondary device's auxiliary primary devices. For example, the table might include a moving average of the received signal strength indicators for each of the secondary device's auxiliary primary devices. Similarly, secondary devices can create and / or maintain a routing table.The routing table can include the routers from which a respective secondary device has received messages (e.g., advertisement messages). Additionally, the routing table can include an indication of the RSSI of the messages received from each of the routers in the routing table. Alternatively, secondary devices can maintain a generic routing table. This routing table can include each of the routers from which a respective secondary device has received advertisement messages and an indicator of the received signal strength for each of the respective routers. The routing table can also include an indication of whether a respective router is a primary device of the secondary device or an auxiliary primary device of the secondary device.As used herein, the expression auxiliary primary device table may refer to a table separate from the routing table or. MA / t / ZUZÓ / UUΊ M a subset of the routing table that includes routers that are synchronized auxiliary primary devices of the secondary device. Each router can send / broadcast an advertisement message containing the path cost to one or more routers on network 260. Routers that receive the path cost information from the router that sent the advertisement message can update their respective path cost information in their local routing tables (e.g., by adding their link cost for communication with the router that sent the advertisement message to the path cost in the received message). Each router can use the locally stored path cost information to identify the path through which digital messages can be communicated. Each router can update its locally stored routing table with the lowest calculated path cost to communicate with other routers on network 260. By periodically updating link quality (e.g., LQI and / or LQO), link cost, and / or path cost, and by communicating the path cost to other routers in periodic announcement messages, each router can have up-to-date path cost information to communicate digital messages to other routers on the 260 network. The router can then use the best communication path (e.g., the lowest-cost path) to communicate digital messages to another device. This routing mechanism allows routers to detect when other routers have disconnected from the 260 network, or if the path cost between routers has changed, and calculate the next lowest-cost path to maintain connectivity with other routers on the 260 network. As described herein, network 260 can enable communication between devices in a load control system (e.g., load control system 200 shown in Figure 2A). Terminal devices 266a and 266b can include load control devices (e.g., control target devices) and / or input devices (e.g., control source devices) that communicate 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 communications. With reference to Figure 2B, the remote control device 232 can function as a terminal device to communicate digital messages comprising user input prompts and / or control instructions to control another terminal device (e.g., the lighting control devices of lighting fixtures 210a-210d). The remote control device 232 can communicate through one or more intermediary primary devices, such as 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 on the network to route messages to the other terminal device (e.g., the lighting control devices of lighting fixtures 210a-210d) to perform load control. The control device beacon messages described herein as being transmitted from control devices may be advertisement messages that indicate the presence of a control device on the network. These beacon messages may include a unique identifier for the control device (e.g., a network identifier) ​​transmitted within the advertisement message and / or network information, such as link quality or link cost for communications between devices on the network. Other devices (e.g., other control devices, a mobile device, a system controller, etc.) may receive and track the advertisement messages transmitted by the control devices in the control device beacons to determine the presence of the control device on the network and / or whether the control device can communicate over the network. Figure 3 is a system diagram illustrating an illustrative control system 300 (e.g., the load control system 100 shown in Figure 1 and / or the load control system 200 shown in Figure 2). As shown in Figure 3, the control system 300 may include load control devices, such as lighting control devices 310 (e.g., the lighting control device 114 of lighting fixtures 110, the lighting control devices 124a-124c of lighting fixtures 120a-120c, the controllable light source 122 of the lighting fixture, and / or the lighting control devices of lighting fixtures 210a-210d, 220a-220d) for commissioning. The 310 lighting control devices can be put into operation by configuring the 310 lighting control devices for lighting control.The 310 lighting control devices can be configured for lighting control by being assigned to different fixtures, groups, zones, and / or locations in the 300 control system configuration data and / or connected to the 312 communication link, such as a wireless communication network. The 310 lighting control devices can be configured by defining default scenes or other lighting control parameters, which then govern their operation. The control system 300 may include a system controller 340 (e.g., system controller 140). The system controller 340 may communicate with the lighting control devices 310 via communication link 312 to perform lighting control based on lighting control configuration information that may be pre-stored there (e.g., in the system controller 340) during operation. Lighting control configuration ML / E / ZuZo / uuZo may include default configurations, zone configurations, occupancy configurations and / or schedule configurations to control 310 lighting control devices. Lighting control configuration information can be generated by a network device, such as a 360 Processing Device (e.g., a personal computer or laptop). The 360 ​​Processing Device can be a network device on which design software can be run to configure (e.g., assign, diagnose, associate, etc.) and / or control the load control system design within a load control environment. The 360 ​​Processing Device can generate a control database that includes lighting control configuration information (e.g., load control parameters) based on the floor plan and design of the lighting control system. The 360 ​​Processing Device can generate a project code identifier to identify the project in which the floor plan and / or control database for the control devices are stored.The lighting control configuration information from the control database can be stored in the 310 lighting fixtures or the 340 system controller to enable lighting control based on that information. The 360 ​​processing device can communicate with the 340 system controller via the 342 communication link. The 342 communication link can be a wired or wireless link, such as an Ethernet link and / or a local network HTTPS link, for example. System controller 340 can send lighting control configuration information to lighting control devices 310 and / or control lighting control devices 310 based on that lighting control configuration information. System controller 340 can communicate with lighting control devices 310 via communication link 312 (e.g., a wireless communication network). Communication link 312 can include RF communication signals transmitted via one or more protocols (e.g., a standard network communication protocol, a proprietary communication protocol, and / or any suitable communication protocol as previously mentioned). Communication link 312 can also include a wired network communication link. After generating the lighting control configuration information on the processing device 360, the processing device 360 ​​can share this information with other devices to update and / or collaborate on the commissioning of the control system 300. For example, the processing device 360 ​​can store the lighting control configuration information in a remote data source, such as a cloud server 370, for access by other devices. The processing device 360 ​​can communicate with the cloud server 370 via a communication link 372. The communication link 372 can enable communication via wired and / or wireless signals.Lighting control configuration information can be stored on the 360 ​​processing device and / or the 370 cloud server with a project identifier to differentiate it from other projects. The control system 300 may include a network device, such as a mobile device 350 (e.g., a smartphone or tablet), which can be deployed to attribute (e.g., discover) control devices (e.g., lighting control devices 310) to operate the control system 300. The mobile device 350 may allow a user to access a control database for a project in the control system 300 and discover the lighting control devices 310 to configure them for the project. The lighting control devices 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 enable the transmission of beacon messages or other short-range RF communications.The 352 wireless communication link may comprise RF signals that communicate using a short-range communication protocol (e.g., BLE). The mobile device 350 can access lighting control configuration information from the control database via the cloud server 370 and / or the processing device 360. The mobile device 350 can communicate with the cloud server 370 via communication link 372. The mobile device 350 can communicate with the processing device 360 ​​via wireless communication link 352. The mobile device 350 can also access the lighting control configuration information from 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 disk or other external storage device. The 350 mobile device can run a local application to assist in the commissioning of the 300 control system. The user can select a button in the application to synchronize the lighting control configuration information within the application with the lighting control configuration information stored for a project on the 370 cloud server. A user of the 350 mobile device can access area and zone information within the lighting control configuration information to assign the discovered 310 lighting control devices. As the 310 lighting control devices are assigned to fixtures, groups, zones, and / or locations on the 350 mobile device, the lighting control configuration information can be updated and sent to the 370 cloud server. For example, the lighting control device identifiers and / or beacon message identifiers of each 310 lighting control device can be stored with an associated area, zone, and / or position within a zone for appropriate control. The 360 ​​processing device can then access the lighting control configuration information and send it to the 340 system controller and / or the 310 lighting control devices to enable lighting control based on the updated assignments. Figure 4 is a flowchart representing an illustrative procedure 400 (e.g., a commissioning procedure) for commissioning a control system, such as a load control system (e.g., load control system 100). Procedure 400 can be implemented by one or more devices. For example, procedure 400 can be implemented by a system controller (e.g., system controller 140, 240, 340), a cloud server (e.g., cloud server 170, 370), and / or a network device, such as a mobile device (e.g., mobile device 150, 250, 350) and / or a processing device (e.g., processing device 160, 360). Procedure 400 can begin in 402. In 404, the load control system can be designed (e.g., as part of a design procedure).For example, the load control system can be designed using design software running on the processing device. The design software can be configured to generate configuration data that defines the operation and / or functionality of the load control system. This configuration data can be stored in a configuration database (e.g., on the processing device, cloud server, mobile device, and / or system controller). The processing device can store the configuration data (e.g., the configuration database) within a project (e.g., which may include other identifying information for a building in which the load control system can be installed). The configuration data may include representations of the control devices (e.g., lighting fixtures, occupancy sensors, remote control devices, etc.).in the load control system, as well as the configuration identifiers (e.g., identifiers for fixtures, groups, zones, areas, and / or locations) of the control devices. For example, configuration data can define the functionality of the control devices (e.g., how lighting fixtures respond to occupancy sensors and / or remote control devices). 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 described later in 414). The control parameters can be used by the control devices and / or the system controller to control electrical loads during normal operation (e.g., after procedure 400 has been completed). ML / E / ZuZo / uuZo In section 406, configuration data (e.g., all or part of the configuration database) can be transferred from the processing device to the mobile device (e.g., as part of a configuration data transfer procedure). For example, the processing device can be configured to transfer the configuration data to the mobile device via the cloud server. When the configuration data is ready to be transferred (e.g., when the control devices of the control system are ready to be assigned and / or associated with configuration identifiers (e.g., zone or group identifiers for joining a network) from the configuration data), the processing device can transmit the configuration data to the cloud server via the internet (e.g., via communication link 372 using IP and / or HTTP communications).The processing device can display a project code (e.g., a unique code for the load control system project being commissioned). For example, the project code might consist of an alphanumeric sequence. A user can enter the project code into a configuration application running on the mobile device. The mobile device can transmit the project code to the cloud server, which can then transmit the configuration data back to the mobile device. Alternatively, 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, the configuration data can be transferred (e.g.,, be transmitted directly) 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 disk or other external memory in 406. In addition, configuration data can be transmitted (e.g., transmitted directly) from the processing device to the mobile device via a short-range wireless communication link (e.g., via communication link 352). In 408, load control system control devices can be assigned and / or associated with configuration identifiers from the configuration data (e.g., accessories, groups, zones, areas, and / or locations that can be defined using the configuration data). For example, the mobile device can assign and / or associate control devices with configuration identifiers from the configuration data as part of a configuration procedure (e.g., an assignment procedure and / or an association procedure) in 408. For example, the mobile device can begin transmitting (e.g., periodically transmitting) a mobile device beacon message via a short-range wireless communication link (e.g., via communication link 352).Control devices that receive beacon messages from the mobile device and are within the mobile device's discovery range can be configured to transmit a beacon message from their respective control device. The mobile device can receive beacon messages from multiple control devices and can select the control device from which a beacon message was received for attribution (e.g., the control device with the highest received signal strength indicator). The installer can then select the configuration identifier to which the current control device is associated from the mobile device to initiate control device attribution.The installer can move the mobile device around the building where the load control system is installed to assign and associate each control device. As control devices are assigned, the control device being assigned can transmit a unique identifier (e.g., a serial number) to the mobile device, and the mobile device can store this unique identifier, along with information about the association between the configuration identifier and the control device, in the configuration data. When the installer has finished assigning the control devices (e.g., the mobile device has assigned all or some of the control devices in the load control system), the configuration procedure can end. Before their allocation on 408, control devices can continuously monitor (e.g., continuously) the mobile device's beacon message on the short-range wireless communication link (e.g., communication link 352). After their allocation on 408, control devices can enter a joining mode. In joining mode, control devices can periodically switch between monitoring the mobile device's beacon message and monitoring a request to join a wireless communication network (e.g., communication link 312). Switching between monitoring the mobile device's beacon message and monitoring the wireless communication network join request allows control devices to prepare to join the wireless communication network while simultaneously allowing the mobile device to connect to one or more of the control devices (e.g., the mobile device).e.g., to correct errors during the allocation of a control device, or to unassign a control device). In 410, configuration data (e.g., as updated during the configuration procedure in 408) can be transferred from the mobile device to the system controller. For example, 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 configuration data to the processing device via the cloud server, via a direct wired connection, and / or via a short-range wireless communication link (e.g., as described above in 406). ML / t / ZUZÓ / UUΊ The processing device can then transmit configuration data (e.g., all or part of the configuration database) to the system controller or another commissioning device (e.g., via communication link 342). The commissioning device can be a device on a wireless communication network used to connect other devices to the network. For example, the commissioning device could be a system controller, a lighting control device, a control source device, etc. Furthermore, the mobile device can be configured to transmit configuration data to the system controller via the cloud server (e.g., without transmitting the configuration data to the processing device). Additionally, the mobile device can be configured to transmit (e.g., transmit directly) the configuration data to the system controller via a direct wired connection and / or via a short-range wireless communication link. Configuration data may include device identification data received from control devices, such as lighting fixtures. The system controller or other commissioning device may receive device identification data from multiple devices. For example, multiple devices may have participated in the allocation procedure performed in 408. For each device that participated in the allocation procedure, the network device may transfer device identification data to the system controller or other commissioning device. The device identification data for each device may be transferred separately (e.g., not simultaneously). The system controller or other commissioning device may instruct a user (e.g.,(via an application running on a separate computing device) how many devices have been assigned to join the network and / or how many devices still need to be assigned to join the network. For example, the network device can display a list of each control device in the area (e.g., graphically or as text). The color of a lighting fixture can change once the system controller or commissioning device has received the device identification data for that lighting fixture. The system controller or other commissioning device can aggregate the device identification data received from the devices and generate a single list of lighting fixtures. The system controller or other commissioning device may be operating in offline mode (e.g., the commissioning device may be disconnected from the internet or otherwise unable to access a particular online service used during commissioning). The network device may transfer device identification data to the system controller or other commissioning device (e.g., directly to the commissioning device) via, for example, an RF signal, a USB transfer, and / or similar means. Additionally, the network device can transfer device identification data to the system controller or another commissioning device via a processing device. The network device can be physically connected to the processing device (e.g., via USB). For example, the network device and the processing device can be connected by a cable with USB connectors at each end. The network device can then transfer the device identification data to the processing device through this physical connection. Alternatively, the network device can be physically connected to the system controller or another commissioning device via a wired digital communication link (e.g., via an Ethernet link).The processing device can transfer the device identification data to the system controller or another commissioning device via the wired digital communication link. Alternatively, the network device can transfer the device identification data by transferring (e.g., copying) the data to an external disk (e.g., removable storage). The external disk can then be connected to the processing device, and the processing device can transfer (e.g., copy) the device identification data from the external disk to local memory. The processing device can store the device identification data in this memory. Finally, the processing device can transfer the device identification data to the commissioning device via the wired digital communication link.The startup device can also store the device identification data in memory. In section 412, the control devices assigned in section 408 can join a wireless communication network (e.g., communication link 312). The system controller can act as a commissioning device to connect the control devices to the wireless communication network. After the control devices have joined the wireless communication network, they can communicate with each other during normal operation. Furthermore, the control devices can stop monitoring the network on which the beacon message from the mobile device was received and can communicate exclusively on the wireless communication network. In section 414, configuration data can be transferred to the control devices.For example, the system controller can transmit a portion of the configuration database relevant to a respective control device to that control device. Figure 5 is a system flow diagram illustrating message flows for discovering control devices in a load control system. For example, a control device can be discovered to enable configuration (e.g., attribution, diagnostics, association, etc.) and / or control of the control device. For example, the system flow diagrams depicted in Figure 5 might represent RF messages communicated between control devices performing procedure 400, as shown in Figure 4. As shown in Figure 5, a network device (e.g., a mobile device) can communicate directly with one or more control devices (e.g., lighting control devices). Alternatively, the network device and control devices can communicate wirelessly.Alternatively, the network device can communicate with the control devices through 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 devices via a wired connection. Although the lighting control devices are shown in Figure 5, other control devices can be used. For example, a control device can be discovered to enable configuration (e.g., attribution, diagnostics, association, etc.) and / or control of the control device. As shown in Figure 5, the load control system can include a mobile device 502 and lighting fixtures 504a, 504b. The lighting fixtures 504a, 504b can include respective load control devices configured to control their respective lighting loads. The lighting control devices in the lighting fixtures 504a, 504b can be RF-capable devices that include a communication circuit capable of transmitting messages via RF signals. The sensors 505a, 505b can be occupancy sensors, visible light sensors (e.g., cameras), sunlight sensors, optical sensors, and / or any other type of sensor.As shown in Figure 5, the mobile device 502 can transmit a configuration mode message 506 to the lighting fixtures 504a and 504b. The configuration mode message 506 can instruct the lighting control devices of the lighting fixtures 504a and 504b to enter a configuration mode (e.g., an attribution mode and / or an association mode). The configuration mode message 506 can be transmitted via RF communication signals (e.g., using a short-range wireless communication protocol) and / or optical signals. The configuration mode message 506 can be sent as a multicast message (e.g., a beacon message) that is received by the lighting control devices of the lighting fixtures 504a and 504b. The lighting fixtures 504a and 504b can enter configuration mode without receiving the configuration mode message 506. After transmitting configuration mode message 506, mobile device 502 can perform the discovery of lighting control devices in lighting fixtures 504a and 504b. The mobile device can discover these lighting control devices by sending discovery request message 508. Discovery request message 508 can be transmitted to identify the selected lighting control devices to be assigned for network integration. The discovery request message 508 may include a discovery threshold and the lighting control devices of the lighting devices 504a, 504b may determine that they are within a discovery range of the mobile device 502 by determining if the Received Signal Strength Indicator (RSSI) of the received discovery request message 508 is greater than or equal to a discovery threshold (e.g. the discovery threshold included in the received discovery request message 508). The discovery request message 508 can be transmitted on an RF signal, such as an RF beacon message transmitted from the mobile device 502. The lighting control device 504a and / or the lighting control device 504b can provide a first type of feedback indicating that the lighting control device has received the discovery request message 508. The feedback can be provided by flashing a lighting load, increasing and / or decreasing the intensity level of the lighting load, increasing and / or decreasing the color temperature of the lighting load, illuminating the lighting load with a predefined color (e.g., orange), illuminating the lighting load with a predefined color temperature, and / or other visual feedback provided to the user. Mobile device 502 can receive discovery response messages 510a and 510b from the lighting control devices of lighting fixtures 504a and 504b. The lighting control devices in lighting fixtures 504a and 504b can transmit discovery response messages 510a and 510b as respective beacon messages to be discovered by mobile device 502 (e.g., in response to entering configuration mode). Mobile device 502 can determine the signal strengths at which the different discovery response messages 510a and 510b are received to identify the lighting control device associated with the strongest beacon message. Based on discovery response messages 510a and 510b, the mobile device 502 can determine which of the lighting control devices in the lighting fixtures 504a and 504b is selected for attribution in order to join the network. Discovery response messages 510a and 510b associated with the strongest signal strength can be selected for attribution in order to join the network. As shown in Figure 5, mobile device 502 can determine that the lighting control device of lighting fixture 504a is receiving discovery request message 508 at the highest signal strength, or that mobile device 502 is receiving beacon message signals from the lighting control device of lighting fixture 504a at the highest signal strength. Mobile device 502 can select lighting control device 504a for configuration (e.g., attribution and / or association). Mobile device 502 can establish a connection 512 (e.g., a bidirectional connection) with the lighting control device of lighting fixture 504a. The connection can be a BLE connection.Connection 512 can be established by mobile device 502 and the lighting control device of lighting fixture 504a by exchanging credentials to create a secure connection for secure communication. The connection message 512 can indicate to the lighting control device of lighting fixture 504a that the lighting control device is selected for configuration (e.g., attribution and / or association). Alternatively, the mobile device can communicate with lighting fixture 504 without establishing a connection. The lighting control device 504a can provide a second type of feedback indicating that the lighting control device 540a has been selected for configuration. For example, the lighting control device 504a can provide this second type of feedback in response to the establishment of connection 512 between the lighting control device 504a and the mobile device 502. This feedback can be provided by flashing a lighting load, increasing and / or decreasing the intensity level of the lighting load, increasing and / or decreasing the color temperature of the lighting load, illuminating the lighting load with a predefined color (e.g., blue), illuminating the lighting load with a predefined color temperature, and / or other visual feedback provided to the user. After establishing connection 512 to the lighting control device of lighting fixture 504a, mobile device 502 can associate the lighting fixture with the configuration data. The mobile device can receive confirmation that the lighting control device of lighting fixture 504a received connection message 512 and / or a unique identifier (e.g., a configuration identifier) ​​selected for the lighting control device of lighting fixture 504a. Mobile device 502 can associate the lighting control device of lighting fixture 504a with the unique identifier and can transmit configuration message 516 to the lighting fixture 504a. Configuration message 516 can indicate that the lighting fixture 504a has been assigned and / or associated with the selected configuration identifier.Configuration message 516 can include, for example, an indication that lighting control device 504a has been assigned, a unique identifier for mobile device 502 (e.g., an application running on mobile device 502), and / or other association information. Configuration message 516 can be used as part of a configuration procedure (e.g., an assignment procedure, an association procedure, a diagnostic procedure, etc.). A control message can be sent, either separately or alternatively, in 516 and include control instructions for operating the lighting control devices of the lighting fixtures. Mobile device 502 can receive an acknowledgment message 518 from lighting control device 504a. For example, acknowledgment message 518 can confirm that lighting control device 504a has received configuration message 516.The connection message 512, the configuration message 516 and / or the confirmation message 518 can be transmitted and / or received via RF communication signals. The lighting control device 504a can provide a third type of feedback indicating that the lighting control device has received configuration message 516. The feedback can be provided by flashing a lighting load, increasing and / or decreasing the intensity level of the lighting load, increasing and / or decreasing the color temperature of the lighting load, illuminating the lighting load with a predefined color (e.g., green), illuminating the lighting load with a predefined color temperature, and / or other visual feedback provided to the user. Figure 6 is a flowchart representing an illustrative procedure 600 for discovering control devices to enable the attribution and / or association of control devices. Procedure 600 can be executed as part of a configuration procedure (e.g., an attribution procedure and / or an association procedure). Procedure 600 can be implemented by one or more devices. For example, procedure 600 can be executed by a mobile device (e.g., mobile device 150, 250, 350) to attribute control devices and / or associate control devices with configuration identifiers of configuration data in a load control system (e.g., as performed in 408 of procedure 400). For example, procedure 600 can be executed in 602 in response to the actuation of a button (e.g., a virtual or programmable button) in a user interface (e.g., a computer)., the user interface 500) of the mobile device. In 604, the mobile device can enter a configuration mode (e.g., an attribution mode and / or an association mode). In 606, the mobile device can begin periodically transmitting beacon messages (e.g., mobile device beacon messages). The mobile device can be configured to transmit mobile device beacon messages over a short-range wireless communication link. The mobile device beacon message can include, for example, a unique identifier that identifies the mobile device (e.g., or an application running on the mobile device) and / or a discovery threshold. When one of the control devices receives the mobile device beacon message and the received signal strength indicator of the mobile device beacon message is greater than or equal to the discovery threshold included in the mobile device beacon message (e.g.,When the control device is within the mobile device's discovery range, the control device can enter a configuration mode (e.g., an attribution mode and / or an association mode) and begin transmitting (e.g., periodically) a beacon message (e.g., a control device beacon message). The mobile device can adjust the discovery threshold included in the mobile device beacon message to adjust the mobile device's discovery range. In 608, the mobile device can discover (e.g., receive) control device beacon messages transmitted by control devices in response to the mobile device receiving its beacon message. Each control device beacon message can include the unique identifier of the control device that transmitted the respective beacon message. In 610, the mobile device can identify the control device beacon message with the highest Received Signal Strength Indicator (RSSI) among the received control device beacon messages. In 612, the mobile device can transmit a connection message to the control device that transmitted the control device beacon message identified in 610 (e.g., the control device beacon message with the highest RSSI).For example, in response to the control device receiving the connection message from the mobile device, the mobile device and the control device can be configured to establish a connection (e.g., a bidirectional communication connection). Additionally, the connection message can inform the control device that it has been selected for allocation. If the mobile device cannot establish the connection in step 614, procedure 600 can be repeated in a loop to allow the mobile device to attempt to connect to the same control device or a different one. When the mobile device successfully establishes a connection with the control device at 614, the mobile device can determine whether an instruction to associate the control device with one of the configuration identifiers from the configuration data has been received from a user via the mobile device's user interface (e.g., user interface 500) at 616. For example, the mobile device may receive a selection of a configuration identifier (e.g., an accessory, group, zone, area, 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 additional control devices (e.g.,(Control source devices to associate with a control target device, or vice versa) to associate with the control device to which the mobile device is connected. When the mobile device receives an instruction to associate the control device with one of the configuration identifiers in 616, the mobile device can create an association between the control device and the selected configuration identifier from the configuration data. ML / E / ZuZo / uuI in 618. To associate the control device with other control devices identified in the configuration identifiers, the mobile device can store the control device's configuration identifier along with the associated configuration identifiers in memory. The associated configuration identifiers can be sent to the control device via the mobile device connection for storage on the control device. Alternatively, the associated configuration identifiers can be stored locally on the control device, enabling the control device to send messages to and / or receive messages from associated devices to facilitate load control. The mobile device can transmit a configuration message (e.g., an attribution message, an association message, a diagnostic message, etc.) to the control device to which the mobile device is connected in 620. The configuration message can indicate that the control device has been assigned and / or associated with the configuration identifier selected from the configuration data. In response to receiving the configuration message, the control device can transmit a confirmation message (e.g., an attribution confirmation message) to the mobile device. The attribution confirmation message can include a unique identifier (e.g., a serial number) of the control device from which the attribution confirmation message is transmitted. Before sending the attribution message, the mobile device can check whether the control device has already been assigned.If the control device has already been assigned, the mobile device can prevent the transmission of an additional assignment message and proceed to 622. If the mobile device does not receive an attribution confirmation message from the control device at 622, procedure 600 can be repeated in a loop to allow the mobile device to attempt to connect to the same control device or a different one. The attribution confirmation message can include a unique identifier (e.g., a serial number) of the control device. When the mobile device receives the confirmation message from the control device to which it is connected at 622, the mobile device can store the control device's unique identifier and association information (e.g., the configuration identifier to which the control device is associated) in memory at 624. The unique identifiers stored during the attribution procedure can be those of devices that can join the network (e.g.,(individually or in a batch) during a joining procedure. The association information can be stored to identify the control devices associated with the control devices that are assigned to join the network. If 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 in 616, but receives an instruction to unassociate the control device with an associated configuration identifier in 626, the mobile device can unassociate the control device with the associated configuration identifier in 628 and remove the unique identifier of the control device and association information from memory in 630. The mobile device can send a message to the control devices to remove the association from memory on the control devices. If the mobile device has not finished assigning and / or associating control devices to the configuration identifiers in configuration data 632, procedure 600 may loop to allow the mobile device to attempt to connect to a different control device or the same control device (e.g., if the control device assignment and / or association was recently overridden in 626). When the mobile device finishes assigning and / or associating control devices in 632 (e.g., the user presses a button on the mobile device's user interface to end the configuration procedure), the mobile device can exit configuration mode in 634, and procedure 600 can terminate. Additionally, the mobile device may stop periodically transmitting mobile device beacon messages in 634. Control devices can provide different types of feedback to indicate different information to the user. For example, a lighting control device might provide feedback indicating that it has been discovered and / or selected for configuration and / or control (e.g., control devices that relay beacon messages received by the mobile device above the discovery threshold). Lighting control devices selected for configuration and / or control might flash (e.g., at varying frequencies), increase / decrease the intensity level of the lighting load, increase / decrease the color temperature of the lighting load, illuminate the lighting load with a predefined color or color temperature, and / or provide the user with other visual feedback through the lighting load. Selected lighting control devices that have the beacon message received on the mobile device with the highest signal strength can provide a different type of feedback.For example, the lighting control device that transmitted the beacon message from the control device with the highest signal strength received by the mobile device may flash at a different rate than other control devices selected for configuration and / or control, increase / decrease the intensity 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, illuminate the lighting load with a different color or color temperature than other control devices selected for configuration and / or control, and / or provide the user with other visual feedback that differentiates the lighting control device. After the lighting control device has been configured (e.g., assigned to an area and / or zone), the lighting control device may provide a different type of feedback.For example, lighting control devices that have been assigned to an area or zone in the lighting control configuration information may flash at a different rate than unassigned devices selected for configuration and / or control, increase / decrease the intensity 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, illuminate the lighting load in a different color or color temperature than unassigned devices selected for configuration and / or control, and / or provide the user with other visual feedback that differentiates the assigned lighting control devices. Feedback types can be pre-programmed into lighting control devices and / or provided in a message to the lighting control devices. For example, feedback types can be provided in the configuration message that a lighting control device has been selected for configuration and / or control, and / or in another message to the lighting control devices from a device in the load control system. Figure 7 is a flowchart illustrating an example of procedure 700 for configuring control devices in a load control system (e.g., load control system 100 and / or load control system 200 shown in Figure 2A) to assign and / or associate the control devices. Procedure 700 can be executed as part of a configuration procedure (e.g., an assignment procedure and / or an association procedure). Procedure 700 can be implemented by a control device (e.g., a lighting control device). However, other control devices can similarly perform one or more parts of procedure 700. During procedure 700, the lighting control device can provide different types of feedback. Procedure 700 can be executed when the lighting control device is not already in a configuration mode (e.g.,e.g., the lighting control device did not enter a configuration mode or begin periodically transmitting beacon messages from the control device upon being switched on). Procedure 700 can reduce RF traffic (e.g., RF transmissions) in an area. RF traffic in an area (e.g., in a building where the lighting control device is installed) can be generated by the load control system's control devices, as well as by other devices in the area, such as other beacon devices, wireless network access points, etc. Method 700 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 above 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 above the threshold, there may be a relatively high amount of RF traffic (e.g.,(interference) if the control devices transmit beacon messages simultaneously. Additionally or alternatively, procedure 700 can be implemented when network congestion exceeding a threshold is detected on a device (e.g., a lighting control device, a system controller, a network device, a mobile device, etc.). Network congestion may exceed a threshold when the probability of receiving a message falls below a certain probability of reception threshold (e.g., it may be necessary to retransmit the message a number of times greater than a certain retransmission threshold).Procedure 700 can reduce the amount of RF traffic in the area where the load control system is located, for example, by reducing the number of control devices transmitting beacon messages at any given time, which can result in fewer transmission collisions and / or lost messages. The likelihood of high RF traffic and / or network congestion can be identified manually by a user (e.g., using a mobile device user interface) and / or automatically by one or more of the load control system's control devices (e.g., the system controller). As shown in Figure 7, procedure 700 can begin at 702, for example, when the lighting control device receives a beacon message (e.g., a mobile device beacon message) from a network device, such as a mobile device (e.g., mobile device 150, 250, 350). The mobile device beacon message can be transmitted in response to entry into a configuration mode (e.g., an attribution mode and / or an association mode) on the mobile device (e.g., in response to a button selection in an application on the mobile device). The mobile device beacon message can be transmitted periodically while the mobile device is in configuration mode. The mobile device beacon message can include a mobile device beacon message identifier. For example, the beacon message identifier can be a unique identifier that identifies the mobile device (e.g.,or an application running on the mobile device) 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 the load control system's control devices. The beacon message identifier may be an identifier of an application running on the mobile device. The mobile device's beacon message may be transmitted via RF communication signals (e.g., using a short-range wireless communication protocol). The mobile device may determine a received signal strength indicator (e.g., RSSI) from the received network device's beacon message (e.g., the signal strength at which the network device's beacon message is received). The received signal strength indicator of the mobile device's beacon message may be compared to a discovery threshold (e.g., a discovery threshold).The discovery threshold can be received in the mobile device's beacon message and / or preconfigured on the lighting control device. The discovery threshold can be configured by a mobile device user, be preconfigured on the mobile device and / or the lighting control device, and / or be configured by a network (e.g., received from the system controller). In 704, it can be determined whether the lighting control device is within the mobile device's discovery range. For example, the lighting control device can determine that it is within the mobile device's discovery range by determining whether the Received Signal Strength Indicator (RSSI) of the received mobile device beacon message is greater than or equal to a discovery threshold (e.g., the discovery threshold included in the received mobile device beacon message). If the lighting control device determines that it is within the mobile device's discovery range in 704, the lighting control device can enter a configuration mode (e.g., an attribution mode and / or an association mode) in 705. Additionally, the lighting control device can enter (e.g.(Only enter) configuration mode if the beacon message identifier of the received mobile device beacon message is a particular beacon message identifier (e.g., default). Configuration mode can be a mode in which the mobile device can store associations between unique identifiers of lighting control devices and configuration identifiers of configuration data (e.g., locally and / or on the system controller). The stored associations can enable the identification of associated control devices to perform load control or otherwise respond to messages from associated devices during normal operation. For example, entry into configuration mode can be triggered in response to a mobile device beacon message received by the lighting control device.If the lighting control device determines that the lighting control device is not within the discovery range of the mobile device in 704, procedure 700 can terminate in 728. The mobile device's beacon message can act as a trigger event to activate a lighting control device to transmit a beacon message (e.g., a beacon message from the control device). In 706, the lighting control device can begin to MA / t / ZUZÓ / UUΊ periodically transmit the control device beacon message. The control device beacon message may include a lighting control device beacon message identifier and / or a device type. For example, the control device beacon message identifier may be a unique identifier that identifies the lighting control device and / or a non-unique identifier, such as an identifier of a group, area, building, load control system, and / or mobile device manufacturer and / or the load control system control devices.The control device beacon message may be communicated in response to the receipt of a mobile device beacon message with a Received Signal Strength Indicator (RSSI) greater than the discovery threshold and / or the beacon message identifier of the received mobile device beacon message is a particular beacon message identifier (e.g., default). The lighting control device may provide a first type of feedback, as described in section 708, indicating that the lighting control device has entered configuration mode. This first type of feedback may be provided by flashing a lighting load, increasing and / or decreasing the intensity level of the lighting load, increasing and / or decreasing the color temperature of the lighting load, illuminating the lighting load with a predefined color (e.g., orange), illuminating the lighting load with a predefined color temperature, and / or other visual feedback provided to the user. The lighting control device may cease providing this first type of feedback when it is out of the mobile device's discovery range (e.g., when the device is not in range).(after a waiting period since the lighting control device has been out of wireless range of the mobile device). The lighting control device can resume the first type of feedback if the lighting control device comes back within discovery range of the mobile device (e.g., after a waiting period since the lighting control device has been out of discovery range). It can be determined in 710 whether the lighting control device is connected to the mobile device. For example, the lighting control device can determine if the beacon message from the control device has been received by the mobile device with the highest Received Signal Strength Indicator (RSSI) among the lighting control devices in configuration mode (e.g., lighting control devices that have not yet been assigned). For example, the lighting control device may receive a message indicating that the beacon message from the control device has been received by the mobile device with the highest RSSI among the control devices in configuration mode. For example, the message could be a connection message initiating the establishment of a connection (e.g.,, a two-way communication connection) between the mobile device and the lighting control device. If the lighting control device did not receive a connection message (e.g., the lighting control device's beacon message control signal was not received with the highest received signal strength indicator) in 710, the lighting control device can determine whether the lighting control device is still within the mobile device's discovery range (e.g., is still receiving beacon messages from the mobile device) in 712. If the lighting control device is still within the lighting control device's discovery range in 712, the lighting control device can continue providing the first type of feedback again in 708. If the lighting control device is no longer within the discovery range in 712, the lighting control device can stop providing feedback (e.g., the first type of feedback) in 714, exit configuration mode in 716 and procedure 700 can end in 728. In addition, the control device can periodically stop transmitting control device beacon messages in 714. When the lighting control device is connected to the mobile device (e.g., in response to receiving the beacon message from the lighting control device with the highest signal strength indicator received from the lighting control devices in configuration mode) at 712, the lighting control device can provide a second type of feedback at 718. The second type of feedback can differentiate the lighting control device from the other lighting control devices that provide the first type of feedback.For example, the second type of feedback can be provided by flashing a lighting load, increasing and / or decreasing the intensity level of the lighting load, increasing and / or decreasing the color temperature of the lighting load, illuminating the lighting load with a predefined color (e.g., blue), illuminating the lighting load with a predefined color temperature, and / or other visual feedback provided to the user that is different from the first type of feedback. In one example, lighting control devices in configuration mode can illuminate each corresponding lighting load in orange to indicate that they are in configuration mode. The lighting control device that transmitted the beacon message received by the mobile device with the highest received signal strength indicator can then illuminate a corresponding lighting load in blue. The blue illumination can indicate to the user which lighting control device was selected for attribution and / or association. ML / E / ZuZo / uuZo M Blue lights can indicate to the user which lighting control device, among the discovered lighting control devices, is likely closest to the mobile device. Orange lights can indicate to the user which lighting control devices are within the mobile device's discovery range and / or are in configuration mode. Additionally, orange lights can indicate to the user which lighting control devices and / or lighting control devices are functioning properly. A lighting control device (e.g., a single lighting control device) in the uncovered group of devices can provide the second type of feedback at any given time. As the user walks with the mobile device, a beacon message can be received from another lighting control device with a higher received signal strength indicator. The mobile device can communicate one or more messages configured to change the lighting load providing the second type of feedback. The mobile device can cause a different lighting load to provide the second type of feedback by transmitting a message (e.g., a connection message) that has the updated identifier of the lighting control device from which the beacon message of the stronger control device is received.The mobile device may break the bidirectional communication connection with the lighting control device that is currently providing the second type of feedback, and that lighting control device may stop providing the second type of feedback. The lighting control device may resume providing the first type of feedback, or stop providing feedback altogether (e.g., if the lighting control device is unable to receive a beacon message from the mobile device within a predefined time period).Therefore, if the lighting control device determines that the lighting control device's beacon message control signal was not received with the highest received signal strength indicator at 710, the lighting control device may provide the first type of feedback again at 708 if the lighting control device is still within the mobile device's discovery range at 712. After providing the second type of feedback in 718, it can be determined in 720 whether the lighting control device has been attributed and / or assigned to a configuration identifier from the configuration data. For example, the lighting control device may receive a message (e.g., an attribution message) indicating that the lighting control device has been attributed. Furthermore, the message may indicate that the lighting control device has been assigned to a configuration identifier. The configuration identifier can be a fixture, group, zone, area, and / or location, which can be defined by the configuration data. ML / E / ZuZo / uuY configuration (e.g., lighting control configuration information) generated by the design software. The configuration identifier can represent a fixture, group, and / or zone at a physical location in 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 fixture, group, and / or zone so that the lighting control message can respond to messages configured to devices to control the fixture, group, and / or zone. If the lighting control device has not been attributed and / or assigned a configuration identifier in 720, the lighting control device may continue to provide the second type of feedback in 718 if the mobile device is still receiving the beacon message control signal from the lighting control device with the highest received signal strength indicator in 710. However, if the lighting control device determines that the beacon message control signal from the lighting control device is no longer being received with the highest received signal strength indicator in 710, the lighting control device may then provide the first type of feedback again in 708 if the lighting control device is still within the mobile device's discovery range in 712. When the lighting control device has been assigned a configuration identifier in 720, it can provide a third type of feedback in 722. This third type of feedback can differentiate the lighting control device from other control devices in configuration mode that provide the first and / or second types of feedback. For example, the third type of feedback can be provided by flashing a lighting load, increasing and / or decreasing the intensity level of the lighting load, increasing and / or decreasing the color temperature of the lighting load, or illuminating the lighting load with a predefined color (e.g.,(green), the illumination of the lighting load with a predefined color temperature and / or other visual feedback provided to the user that is different from the first type of feedback and / or the second type of feedback. In one example, lighting control devices that are within the discovery range of the mobile device (e.g., that are in configuration mode) may illuminate each corresponding lighting load in orange to indicate the lighting control devices that are within the discovery range of the mobile device (e.g., are within the discovery range of the mobile device) (e.g., were not assigned and do not have the strongest control device beacon message signal received by the mobile device).The lighting control device that receives the beacon message from the control device with the highest received signal strength indicator (e.g., and is not yet assigned) can illuminate a corresponding lighting load in blue, and lighting control devices that have been assigned can illuminate a corresponding lighting load in green. The green lighting load can indicate to the user which lighting control devices have already been assigned and / or assigned to a configuration identifier. Lighting control devices assigned to different fixtures, groups, and / or zones can provide different types of feedback (e.g., illuminating lighting loads with different colors, flashing differently, illuminating lighting loads with different color temperatures or dimming levels, etc.). The third type of feedback can be provided, either additionally or alternatively, in response to other configuration information for setting up (e.g., attribution, diagnostics, association, etc.) and / or controlling the lighting control device. For example, the third type of feedback can be provided after the lighting control device is configured with scenes, dimming levels, and / or other lighting control information to complete the setup (e.g., attribution, diagnostics, association, etc.) and / or control of the lighting control device. After providing the third type of feedback in 722, the lighting control device can transmit a message (e.g., an attribution confirmation message) that includes a unique identifier (e.g., serial number) of the lighting control device in 724.Next, the lighting control device can enter a bonding mode at 726. In bonding mode, the lighting control device can stop continuously transmitting (e.g., periodically transmitting) the control device's beacon message over the short-range wireless communication link, and can periodically switch between transmitting the control device's beacon message and waiting for a bonding request to a wireless communication network (e.g., as performed at 412 of procedure 400). Procedure 700 can terminate at 728. The first type of feedback, second type of feedback, and / or third type of feedback can be provided by a lighting control device while the lighting control device is in configuration mode (e.g., it receives the beacon message from the mobile device at or above the discovery threshold). When the mobile device moves away from the lighting control device, such that the signal strength indicator for the beacon message from the mobile device falls below the discovery threshold, the lighting control device may stop providing feedback. If a lighting control device is removed from a previous assignment or its assigned status is removed, the lighting control device may stop providing the third type of feedback. The lighting control device may revert to the first and / or second type of feedback when it is in configuration mode. Lighting control devices may stop providing feedback when they are outside the mobile device's discovery range (e.g., they do not receive the mobile device's beacon message at or above the discovery threshold).Lighting control devices may automatically exit configuration mode and / or cease providing feedback when they cannot receive a beacon message from the mobile device within a specified timeout period (e.g., indicating that the mobile device may be out of discovery range). Alternatively, lighting control devices may also exit configuration mode and / or cease providing feedback when they receive a message from the mobile device and determine, based on the signal strength indicator received from the mobile device's beacon message, that it is below a discovery threshold and / or an indication in the message that the lighting device is out of discovery range (e.g.,(while the lighting control device is within wireless range of the mobile device's communications). Although procedure 700 can be described by referring to lighting control devices, other types of control devices can be implemented similarly. A load control system (e.g., the load control system 100 shown in Figure 1) may include a relatively large number of control devices (e.g., more than 50 or more than 100), one or more of which may communicate on a network (e.g., network 260). For example, as described herein, control devices may periodically transmit control device beacon messages, which can increase network congestion as the number of control devices increases. In addition to control device beacon messages, control devices may communicate other types of messages on the network to control electrical loads within the load control system. As the number of control devices in the load control system increases, the amount of wireless (e.g., RF) traffic in the network environment may increase proportionally.As the amount of RF traffic in the network environment increases, messages may be lost and / or collisions may occur, which can lead to higher latency and / or lower reliability. One or more procedures can be used to reduce the amount of RF traffic in the network environment. To reduce the amount of RF traffic in the network environment, procedures can be implemented to reduce the number of messages transmitted. Periodic message transmissions (e.g., control device beacon messages or other periodic messages) can be limited to help reduce network congestion even more than aperiodic messages (e.g., messages transmitted in response to actuations in control devices). The mobile device can transmit (e.g., continuously or periodically) a mobile device beacon message to trigger message transmission from control devices on the network. The mobile device beacon message can include a discovery threshold. If a given control device receives the mobile device beacon with a signal strength (e.g.,If the received signal strength indicator (indicator of signal strength) exceeds the discovery threshold, the control device may transmit one or more messages. For example, the control device may receive the beacon signal from the mobile device above the discovery threshold and respond by transmitting (e.g., periodically) control device beacon messages. While the control device beacon messages may be described herein as being transmitted in response to the mobile device beacon message, other types of message transmissions may be controlled in a similar manner as described herein. If the discovery threshold in the mobile device's beacon message is too low, a relatively large number of control devices may transmit their respective beacon messages, which can lead to increased latency and / or decreased reliability. As described herein, the mobile device can receive control device beacon messages that are triggered in the control devices by the mobile device's beacon messages. If the mobile device receives a relatively large number of control device beacon messages from other control devices, collisions may occur, and the mobile device may not receive control device beacon messages from some of the control devices. If the mobile device cannot receive control device beacon messages from some of the control devices (e.g.,(due to collisions), the mobile device may fail to discover some control devices, even if the control device is located close to the mobile device. Conversely, if the discovery threshold is too high, very few control devices may transmit control device beacon messages in response to the mobile device's beacon message. The strength of the signal received from RF communications, such as beacon messages from the mobile device, can vary due to one or more factors and / or environmental conditions, such as the physical location and / or orientation of the mobile device (e.g., relative to each control device), the geometry of the area in which the mobile device and / or control devices are located, the physical properties of the mobile device and / or control devices, and interference. Wireless ML / E / ZuZo / uuY from other devices in the area, etc. Since the signal strength received from RF communication can vary, the number of control devices receiving the beacon message from the mobile device above the discovery threshold can also vary. Consequently, the number of control devices receiving the beacon message from the mobile device above the discovery threshold (e.g., the number of control devices discovered) can be affected by these factors and / or environmental conditions. For example, a mobile device with a more powerful transceiver or antenna with greater RF transmission capabilities may discover more control devices above the same discovery threshold than a mobile device with a less powerful transceiver or antenna with lower RF transmission capabilities.Additionally, the number of discovered control devices may change as the mobile device moves through the area. To control the number of control devices discovered by the mobile device's discovery beacon, the mobile device can adjust (e.g., periodically) the discovery threshold included in its beacon message. The mobile device can monitor (e.g., periodically) the number of control device beacon messages received in response to its discovery beacon message and adjust the discovery threshold so that the number of control devices discovered at any given time falls within a target range. For example, the mobile device can adjust the discovery threshold so that the number of control devices discovered falls within a low-side threshold (Ulow) and a high-side threshold (Uhigh) (e.g., between 15 and 25 devices).The amount by which the discovery threshold is adjusted can depend on the number of discovered control devices. For example, the mobile device may adjust the discovery threshold by a smaller amount when the number of discovered devices is closer to the target range (e.g., between 1 and 14 or 26 and 40), and adjust the discovery threshold by a larger amount when the number of discovered devices is further from the target range (e.g., less than 1 and more than 40). Once the number of discovered control devices falls within the range defined by the low-side threshold (Ubajo) and the high-side threshold (Ualto), the mobile device can select one or more control devices for configuration (e.g., attribution, association, etc.) and / or control. After the selected control device has completed configuration and / or control, it can continue transmitting its control device beacon. The mobile device can continue counting the control device in the number of discovered control devices and can maintain the discovery threshold at the same level. Alternatively, the mobile device can determine that the control device has completed configuration and / or control and remove the control device from the number of discovered control devices. ML / E / ZuZo / uuY control discovered. Then, the mobile device can increase the discovery threshold so that the number of discovered control devices is again within the range defined by the low-side threshold Ulow and the high-side threshold Uhigh. In addition, the control device can stop transmitting its control device beacon. If this causes the number of control device beacons received by the mobile device (e.g., the number of discovered control devices) to fall below the low-side threshold Ulow, the mobile device can increase the discovery threshold. Figure 8A is a flowchart illustrating an illustrative procedure 800 for discovering when a control device in a load control system (e.g., load control system 100) is within a discovery scope. Procedure 800 can be executed as part of a configuration procedure (e.g., an attribution procedure, an association procedure, or another configuration procedure). Procedure 800 can be implemented by a control device (e.g., a lighting control device or other control device) to determine whether the control device is within the discovery scope of a mobile device.While a control device may be provided as an illustrative device to determine if the control device is within the mobile device's discovery scope, the mobile device can similarly perform one or more parts of the 800 procedure. For example, the mobile device can determine if the control devices are within the discovery scope. Procedure 800 can begin at 802. Procedure 800 can be executed periodically. For example, the control device can transmit its control device beacon message at a given rate (e.g., a transmission rate), and procedure 800 can be executed at approximately the same rate. Therefore, the time between successive executions of procedure 800 can be approximately the same as the transmission period of the control device beacon message. At 804, the control device can receive a mobile device beacon message from the mobile device. The mobile device beacon message can be transmitted in response to input from the mobile device in a configuration mode (e.g., an assignment mode, an association mode, or another configuration mode), for example, in response to a button selection in an application on the mobile device.The mobile device beacon message can be transmitted periodically while the mobile device is in setup mode. The mobile device beacon message can include a mobile device beacon message identifier and / or the discovery threshold. The beacon message identifier can be an identifier of an application running on the mobile device. The mobile device beacon message can be transmitted via RF communication signals using a short-range wireless communication protocol. The discovery threshold can define the discovery range. In 806, the control device can determine if it is within the mobile device's discovery range. The control device compares the received signal strength indicator at which the mobile device's beacon message was received with the discovery threshold included in the mobile device's beacon message. The control device can determine that it is within discovery range when its received signal strength indicator is greater than the discovery threshold. If the received signal strength indicator at which the mobile device's beacon message was received on the control device is less than the discovery threshold, the control device can determine that it is outside discovery range.The control device can be configured to be in the discovery range or out of the discovery range when the received signal strength indicator at which the beacon message was received from the mobile device is equal to the discovery threshold. If the control device determines that it is within discovery range on 806, the control device can set an IN RANGE flag. For example, the control device can set the IN_RANGE flag to a value (e.g., 1, TRUE, or another value indicating that the control device is determined to be within discovery range) that indicates the control device is within discovery range on 808. The control device can check the value of the IN RANGE flag before transmitting a control device beacon message in response to receiving a beacon message from the mobile device. The control device may receive multiple mobile device beacon messages on 804 and fluctuate between determining, on 806, that it is within discovery range and outside of discovery range over a period of time. This may occur more frequently for control devices located at the edge of discovery range (e.g., relatively close to the discovery threshold). This fluctuation may be caused by variability in RF communications on the network and may require the mobile device to update the number of discovered control devices more frequently. To prevent a control device from fluctuating between identifying itself as within discovery range and outside of discovery range over a period of time, the control device may initiate a timer (e.g.,, a discovery timer) after determining that the control device is within the discovery scope in 806. The discovery timer can define a discovery period that ends when the timer reaches a predefined value (e.g., when the discovery period ends). The discovery period can be a period of time (e.g., 2 seconds, 4 seconds, 8). MA / t / ZUZÓ / UUΊ seconds, etc.) which begins when the control device receives a beacon message from the mobile device with a received signal strength amplitude that is greater than the discovery threshold and allows the control device to continue maintaining its status as a discovered device (e.g., by maintaining the IN-RANGE flag status) during the discovery period. If the control device determines that it is out of range of discovery in 806, it can determine whether it was within range of discovery during the discovery period in 810. The control device can determine that it is within range of discovery during the discovery period if it has received a beacon message from the mobile device with a value greater than the discovery threshold during the discovery period. If the control device determines in 810 that it is outside the range of discovery included in the beacon message from the mobile device in 806 and is not within the discovery period (e.g., the discovery timer has not started or has finished), the control device can clear the INRANGE flag in 812.For example, the control device can clear the IN-RANGE flag from memory or set the IN_RANGE flag to a value indicating that the control device is out of discovery range (e.g., 0, FALSE, or another value indicating that the control device is out of discovery range) in 812. In 814, the control device can determine whether the IN RANGE flag is set (e.g., whether the IN RANGE flag value indicates that the control device is within discovery range). If the control device determines that the IN RANGE flag is set, the control device can transmit a control device beacon message in 816, and procedure 800 can terminate in 818. If the IN_RANGE flag is not set, procedure 800 can terminate in 818 (e.g., without the control device transmitting the control device beacon message). A mobile device can send several successive mobile device beacon messages within a relatively short period. A control device that is at the edge of the discovery range (e.g., based on a discovery threshold included in the mobile device beacon messages) may receive some of the mobile device beacon messages with a received signal strength amplitude (e.g., RSSI) above the discovery threshold and some of the mobile device beacon messages with a received signal strength amplitude below the discovery threshold. Therefore, the control device may rapidly switch between entering and exiting configuration mode. This can cause the control device to indicate to the user that it is both inside and outside the discovery range, e.g.causing the device to flash and / or blink a given color, which can be visibly disruptive to the user. Because the mobile device can adjust the discovery threshold based on the number of control devices present at the discovery threshold (e.g., in setup mode), having one or more control devices switched on in this way can cause the mobile device to make a relatively large number of unnecessary adjustments. These situations can be avoided by implementing hysteresis with the Urssi discovery threshold, which can make it more likely that a control device in a given state (e.g., in or out of configuration mode) will remain in that state. The control device can implement hysteresis using one or more threshold offsets (e.g., as shown in Figure 8B) and / or a discovery period (e.g., as shown in Figure 8A). The threshold offsets can be used to determine an updated discovery threshold (e.g., an increased or decreased discovery threshold).Threshold shifts and / or the discovery period can make it more likely that a control device that is in configuration mode at a given time will remain in configuration mode to perform the configuration, since the control device can remain in configuration mode for a longer period of time after entering configuration mode. Threshold shifts can also make it more likely that a control device that is out of discovery range will remain out of discovery range after entering configuration mode. Figure 8B is a flowchart illustrating an illustrative procedure 850 for discovering that a control device in a load control system (e.g., load control system 100) is within a discovery scope. Procedure 850 can be executed as part of a configuration procedure (e.g., an attribution procedure, an association procedure, or another configuration procedure). Procedure 850 can be implemented using a control device (e.g., a lighting control device or other control device) to determine whether the control device is within the discovery scope of a mobile device.While a control device may be provided as an illustrative device to determine if it is within the mobile device's discovery scope, the mobile device may similarly perform one or more parts of procedure 850. For example, the mobile device may determine if control devices are within the discovery scope. Procedure 850 can begin at 852. Procedure 850 can run periodically or in response to a triggering event. For example, the control device can transmit its control device beacon message at a given rate (e.g., a transmission rate), and procedure 850 can run at approximately the same rate. Therefore, the time between successive executions of procedure 850 can be approximately the same as the transmission period of the control device's beacon message. The mobile device's beacon message can be transmitted in response to the mobile device entering a configuration mode (e.g., an assignment mode, an association mode, or another configuration mode), for example, in response to a button selection in an application on the mobile device. The mobile device's beacon message can be transmitted periodically while the mobile device is in configuration mode. In 854, the control device can receive a mobile device beacon message from the mobile device. The mobile device beacon message may include a mobile device beacon message identifier, one or more threshold offsets, and / or an Urssi discovery threshold. The threshold offsets may be pre-stored in the control device's memory. The beacon message identifier may be an identifier of an application running on the mobile device. The mobile device beacon message may be transmitted via RF communication signals using a short-range wireless communication protocol. The Urssi discovery threshold may define the discovery range. In 856, the control device can determine the Urssi discovery threshold from the beacon message received from the mobile device. For example, the beacon message from the mobile device might include an indication of the Urssi discovery threshold. The Urssi discovery threshold might have a value of approximately -60 dBm. In 858, the control circuit can determine whether an IN-RANGE flag is set. For example, the IN-RANGE flag might be set to a value (e.g., 1, TRUE, or another value indicating that the control device has been determined to be within discovery range) when the control device enters discovery range (e.g., the control device enters a configuration mode). The control device might clear the IN-RANGE flag from memory or set the IN-RANGE flag to a value indicating that the control device is out of discovery range (e.g., the control device enters a configuration mode).e.g., 0, FALSE, or another value indicating that the control device is out of discovery range) when the control device leaves discovery range (e.g., the control device exits configuration mode). For example, the control device may clear the IN RANGE indicator from memory or set the IN RANGE indicator to a value indicating that the control device is out of discovery range when a discovery period (e.g., 2, 4, or 8 seconds) has elapsed since the control device last received a beacon message from the mobile device at a signal strength greater than a discovery threshold. If the control device determines at 858 that the IN_RANGE flag is not set (e.g., it was not previously set), the control device can determine whether it is within the discovery scope at 860. The control device can implement hysteresis to enter and exit the discovery scope (e.g., configuration mode) based on the discovery threshold Udespi. For example, the discovery scope can be based on a first threshold offset Udespi used to enter the discovery scope (e.g., enter configuration mode) that is different from a second threshold offset Udespi used to exit the discovery scope (e.g., exit configuration mode). The first threshold offset Udespi and the second threshold offset Udespi can have the same value or different values.For example, the first threshold shift Udespi and the second threshold shift Udesp2 can each have a value of 5 dBm. As shown in Figure 8B, the control device can determine whether it is within discovery range based on the discovery threshold Urssi, a first threshold shift Udespi, and a received signal strength indicator RSSIrx at which the control device received the beacon message from the mobile device. The control device can add the first threshold shift Udespi to the discovery threshold Urssi, so that the discovery threshold Urssi increases, e.g., to an incoming discovery threshold Uentrada. Alternatively, the beacon message from the mobile device can include both the discovery threshold Urssi and the incoming discovery threshold Uentrada. The first threshold shift Udespi can cause the discovery threshold Urssi (e.g., to 5 dBm) to increase.For example, the input discovery threshold (Uinput) is set to a higher RSSI value than the second threshold offset (Udespi2) to exit the discovery range (e.g., exit configuration mode). For example, the discovery threshold (Uinssi) might be approximately -60 dBm, the first offset (Udespi) might be 5 dBm, and the control device might add the two values ​​to reach a value of -55 dBm for the input discovery threshold (Uinput). The control device can compare the received signal strength indicator (RSSIrx) with the input discovery threshold (Uinput) to determine whether the control device is within the discovery range and whether the control device should enter configuration mode.Using hysteresis can make it more likely that a control device at the edge of the discovery range will determine that it is outside the discovery range and enter configuration mode. This can help prevent a situation where the control device rapidly enters and exits configuration mode due to fluctuations in the received RSSIrx signal strength amplitude at which successive beacon messages are received. If the control device determines that the received signal strength indicator RSSIrx is less than the input discovery threshold Uentrada (e.g., the control device does not If the control device determines that the received signal strength indicator RSSIrx is greater than or equal to the input discovery threshold Uintra (e.g., the control device is within the discovery range) at 860, the procedure 850 can continue to 870 (e.g., without setting the INRANGE flag). If the control device determines that the received signal strength indicator RSSIrx is greater than or equal to the input discovery threshold Uintra (e.g., the control device is within the discovery range) at 860, the mobile device can set the IN_RANGE flag at 862. For example, the control device can set the IN RANGE flag to a value (e.g., 1, TRUE, or another value indicating that the control device is determined to be within the discovery range) that indicates that the control device is within the discovery range at 862.The control device can check the IN RANGE flag value before transmitting a control device beacon message in response to receiving a beacon message from the mobile device. Procedure 850 can then proceed to 870. If the control device determines at 858 that the IN RANGE flag has been set, it can determine whether it remains within the discovery range at 866. The control device can implement hysteresis to enter and exit the discovery range (e.g., configuration mode) based on the Urssi discovery threshold. As shown in Figure 8B, the control device can determine whether it remains within the discovery range based on the Urssi discovery threshold, the second threshold offset Udespz, and the received signal strength indicator RSSIrx at which the control device received the beacon message from the mobile device. The control device can subtract the second threshold offset Udesps from the Urssi discovery threshold, so that the Urssi discovery threshold decreases, e.g., to an exit discovery threshold Usalida.Alternatively, the mobile device's beacon message can include the Urssi discovery threshold and the Usalida exit discovery threshold. For example, the Urssi discovery threshold might be approximately -60 dBm, the second threshold offset Udesps might be 5 dBm, and the control device might add the two values ​​to arrive at a value of -65 dBm for the Usalida exit discovery threshold. Although not shown in Figure 8B, the control device might subtract the second threshold offset Udespz, which can be smaller than the first threshold offset Udespi, from the Urssi discovery threshold to set a lower discovery threshold for exiting configuration mode.The control device can compare the received signal strength indicator RSSIrx with the exit discovery threshold Usalida to determine if the control device is still within discovery range (e.g., if the control device should exit configuration mode). This can help prevent situations where the control device rapidly enters and exits configuration mode due to fluctuations in the received signal strength indicator. RSSIrx to which successive beacon messages are received. If the control device determines that the received signal strength indicator RSSIrx is greater than or equal to the output discovery threshold Usalida (e.g., the control device is still within discovery range) at 866, procedure 850 can proceed to 870 (e.g., without clearing the IN_RANGE flag). If the control device determines that the received signal strength indicator RSSIrx is less than the output discovery threshold Usalida (e.g., the control device is outside discovery range) at 866, the mobile device can clear the IN_RANGE flag at 868. For example, the control device can clear the IN_RANGE flag from memory or set the IN_RANGE flag to a value indicating that the control device is outside discovery range (e.g., 0, FALSE, or another value indicating that the control device is outside discovery range) at 868.The control device can also determine if a discovery period (e.g., 2, 4, or 8 seconds) has elapsed since the control device last received a beacon message from the mobile device with a signal strength greater than a discovery threshold. If the control device determines that the discovery period has elapsed, it can clear the IN_RANGE flag at 868. The control device can check the value of the IN_RANGE flag before transmitting a control device beacon message in response to receiving a beacon message from the mobile device. At 870, the control device can determine whether the IN_RANGE flag is set (e.g., whether the IN_RANGE flag value indicates that the control device is within discovery range). If the control device determines that the IN_RANGE flag is set or indicates that the control device is within discovery range, the control device can transmit a control device beacon message at 872. Procedure 850 can terminate at 874. If the IN_RANGE flag is not set or indicates that the control device is outside discovery range, procedure 850 can terminate at 874.For example, the control device may fail to transmit the control device beacon message when it is out of discovery range. Figure 9 is a flowchart illustrating an example of procedure 900 for discovering a control device in a load control system (e.g., load control system 100). Procedure 900 can be executed as part of a configuration procedure (e.g., an attribution procedure, an association procedure, or another configuration procedure). Procedure 900 can be implemented by a mobile device (e.g., a network device). For example, the mobile device can perform procedure 900 periodically (e.g., every second, ten seconds, one minute, etc.) to monitor the number of control devices transmitting a control device beacon message, allowing adjustment of the number of control devices transmitting control device beacon messages on the network.However, other control devices can similarly perform one or more parts of procedure 900. Procedure 900 can begin at 902. At 904, the mobile device can count the number of control devices within its discovery range (e.g., discovered control devices). The mobile device can transmit a mobile device beacon message and count the number of control devices that transmit control device beacon messages in response to the mobile device beacon message. For example, there may be one or more control devices in an area where the mobile device is located. The mobile device can transmit a mobile device beacon message that includes a discovery threshold. A control device can transmit its control device beacon message if it receives the mobile device beacon message at a signal strength value (e.g.,with a received signal strength value) greater than the Urssi discovery threshold (e.g., as shown in Figure 8A) and / or greater than the Urssi discovery threshold plus the first Udespi threshold shift (e.g., as shown in Figure 8B). The mobile device can determine that a control device is within discovery range if the mobile device receives a control device beacon message from that control device. Therefore, the mobile device can count the number of discovered control devices by counting the number of control device beacon messages received by the mobile device within a given time period (e.g., approximately 4 seconds). For example, the mobile device can maintain a log (e.g., a record) of each control device beacon it receives, along with the corresponding information (e.g.,, an identifier of the control device from which the beacon was received and / or a time at which the beacon was received). The mobile device can count the number of control devices discovered by determining a number of unique control devices from which a beacon was received in the specified time period. As described herein, control devices can receive the beacon message from the mobile device at a received signal strength amplitude greater than the Urssi discovery threshold and continue transmitting beacons from the control device for at least one discovery period. Control devices can continue transmitting beacon messages from the control device during the discovery period even after determining that subsequently received beacon messages from the mobile device are less than the Urssi discovery threshold (e.g., as shown in Figure 8A) and / or less than the Urssi discovery threshold minus the second threshold offset Udespz (e.g., as shown in Figure 8B). To avoid excessively frequent adjustments to the discovery range, the mobile device can wait for an adjustment timer to expire after it has been adjusted (e.g.,The Urssi discovery threshold is adjusted (increased) before the Urssi discovery threshold is adjusted again. The adjustment timer can be longer than the discovery period for control devices to allow control devices that are no longer within the discovery range to stop transmitting control device beacon messages. Using an adjustment timer can prevent the mobile device from adjusting (e.g., increasing) the Urssi discovery threshold too frequently and overcorrecting the Urssi discovery threshold. At 906, the mobile device can determine if the adjustment timer has finished. If the mobile device determines that the adjustment timer has finished at 906, it can increase or decrease the Urssi discovery threshold based on the number of control devices discovered.If the mobile device determines that the adjustment timer has not finished at 906, the mobile device may decrease the Urssi discovery threshold, but not increase it, based on the number of discovered control devices. For example, the mobile device may wait for the adjustment timer to finish at 906 to perform increases to the Urssi discovery threshold at 910 or 914. Since the Urssi discovery threshold is described herein by way of example as a received signal strength indicator value, an increase in the Urssi discovery threshold may reduce the number of control devices within the discovery range (e.g., because fewer control devices can receive the beacon message from the mobile device with received signal strength indicator values ​​that exceed the increased Urssi discovery threshold).Because the increased Urssi discovery threshold can be used to reduce the number of control devices in the discovery scope, the mobile device may wait for the adjustment timer to finish at 906 to adjust the Urssi discovery threshold before attempting to reduce the number of control devices in the discovery scope. The mobile device may wait for the adjustment timer period to finish before attempting further reductions in the number of control devices in the discovery scope to prevent discovery scope decreases from occurring too frequently and potentially overcorrecting the Urssi discovery threshold. The mobile device may not wait for the adjustment timer to finish at 906 to decrease the Urssi discovery threshold at 920 or 924.The mobile device can lower the Urssi discovery threshold to increase the number of control devices within the discovery range without waiting for the adjustment timer to finish. Alternatively, the mobile device can determine whether the adjustment timer has finished before lowering the Urssi discovery threshold, and can refrain from lowering the Urssi discovery threshold if the adjustment timer has not finished. The mobile device can adjust the Urssi discovery threshold by a smaller amount when the number of discovered devices is closer to the target range (e.g., between 26 and 40 on the high side or between 5 and 14 on the low side), and by a larger amount when the number of discovered devices is further from the target range (e.g., more than 40 or less than 5). The amount of the Urssi discovery threshold adjustment can correspond to a threshold number of discovered control devices relative to the target range. For example, the mobile device can compare the number of discovered control devices to a first high-side threshold value (e.g., 40 control devices) at 908. The first high-side threshold value can be a high-side threshold value that is further from the target range (e.g., 40 control devices)., 15 to 25 control devices) than a second high-side threshold value Ualto2 (e.g., 25 control devices). While the first high-side threshold value Ualtoi and the second high-side threshold value Ualtos are provided as examples, the mobile device can be configured with additional thresholds that vary from a higher high-side threshold value to a lower high-side threshold value that sets the threshold number of discovered control devices to adjust the Urssi discovery threshold. When the mobile device determines at 908 that the number of discovered control devices exceeds the first high-side threshold value Ualtoi, the mobile device may increase the Urssi discovery threshold by a first threshold increment Δινοι at 910 in an attempt to reduce the number of control devices within the discovery range. The first threshold increment Δινοι may be larger than a second threshold increment Δινοι in an attempt to reduce the number of discovered control devices by a greater amount. For example, the first threshold increment Δινοι may be approximately 2 decibel-milliwatts (dBm), which may increase the value of the Urssi discovery threshold received signal strength indicator from -4 dBm to -2 dBm. The mobile device may then begin transmitting (e.g., periodically transmitting) mobile device beacon messages (e.g.,, one or more mobile device beacon messages) with the increased Urssi discovery threshold. If the mobile device determines that the number of discovered control devices is less than (or equal to) the first high-side threshold value Ualtoi at 908, the mobile device can determine if the number of discovered control devices is greater than the second high-side threshold value Ualto2 at 912. The second high-side threshold value Ualto2 can be less than the first high-side threshold value Ualtoi. If the mobile device determines that the number of discovered control devices is greater than the second high-side threshold value Ualto2, the mobile device can ML / E / ZuZo / uuZo increase the Urssi discovery threshold in the second threshold increment AiNC2en 914. The second threshold increment Dinos can be smaller than the first threshold increment Ainci, for example, because the second high-side threshold value Ualto2 is closer to the target range than the first high-side threshold value Ualtoi-. For example, the second threshold increment Dino2 can be approximately 1 dBm, which can increase the Urssi discovery threshold received signal strength indicator value from -2 dBm to -1 dBm. Then, the mobile device can begin transmitting (e.g., periodically transmitting) mobile device beacon messages (e.g., one or more mobile device beacon messages) with the Urssi discovery threshold increased. If the mobile device increases the Urssi discovery threshold (e.g., to 910 or 914), the mobile device can start the setting timer at 916.As described herein, the adjustment timer can be started at a value greater than the control device discovery period. The adjustment timer can be started at a multiple of the control device discovery period. For example, the adjustment timer can be started at 8 seconds when the control device discovery period is set to 4 seconds. After the mobile device starts the adjustment timer at 916, procedure 900 can end at 928. If the mobile device determines that the number of discovered control devices is less than (e.g., less than or equal to) the second high-side threshold value Ualto2 at 912, the mobile device can determine whether to decrease the discovery threshold Urssi. The mobile device can compare the number of discovered control devices with one or more low-side thresholds Ubajo to determine an amount to decrease the discovery threshold Urssi. The mobile device can compare the number of discovered control devices with the first low-side threshold value Ubajoi (e.g., 1 control device) at 918. The first low-side threshold value Ubajoi can be a low-side threshold value that is further from the target range than a second low-side threshold value Ubajo2 (e.g., 15 control devices).While the first low-side threshold value Ubajoi and the second low-side threshold value Ubajo2 are provided as examples, the mobile device can be configured with additional thresholds ranging from an upper to a lower low-side threshold value that sets the threshold number of discovered control devices to adjust the Urssi discovery threshold. When the mobile device determines at 918 that the number of discovered control devices is less than the first low-side threshold value Ubajoi, the mobile device may decrease the Urssi discovery threshold by a first Adeci threshold decrement at 920 in an attempt to increase the number of control devices within the discovery scope. The first Adeci threshold decrement may be greater than a second Adec2 threshold decrement. ML / E / ZuZo / uuY attempt to increase the number of discovered control devices by a larger amount. For example, the first Adeci threshold decrement can be approximately 4 dBm, which can decrease the Received Signal Strength Indicator value of the discovery threshold Urssi from -2 dBm to -6 dBm. The mobile device can then begin transmitting (e.g., periodically transmitting) mobile device beacon messages (e.g., one or more mobile device beacon messages) with the decreased discovery threshold Urssi. If the mobile device determines that the number of discovered control devices is greater than (or equal to) the first low-side threshold value Ubajoi at 918, the mobile device can determine if the number of discovered control devices is less than the second low-side threshold value Ubajo2 at 922. The second low-side threshold value Ubajo2 can be greater than the first low-side threshold value Ubajoi (e.g.(closer to the target range). If the mobile device determines that the number of discovered control devices is less than the second low-side threshold value Ubajo2, the mobile device can decrease the Urssi discovery threshold by the second ADec2 threshold decrement by 924. The second ADec2 threshold decrement can be smaller than the first Adeci threshold decrement, for example, because the second low-side threshold value Ubajo2 is closer to the target range than the first low-side threshold value Ubajoi. For example, the second Adecp threshold decrement can be approximately 2 dBm, which can decrease the Urssi discovery threshold received signal strength indicator value from -2 dBm to -4 dBm. The mobile device can then begin transmitting (e.g., periodically) mobile device beacon messages (e.g.,If the mobile device decreases the Urssi discovery threshold (e.g., to 920 or 924), it can terminate the adjustment timer (e.g., stop and clear the adjustment timer as if it had finished) at 926. As described herein, upon terminating the adjustment timer after decreasing the Urssi discovery threshold, the mobile device can immediately increase the Urssi discovery threshold (e.g., to 910 or 914) the next time it executes procedure 900 (e.g., if a slight decrease in the Urssi discovery threshold results in a dramatic increase in the number of discovered control devices). After the mobile device terminates the adjustment timer at 926, procedure 900 can terminate at 928. While examples of threshold values ​​for the number of discovered control devices and values ​​for increasing or decreasing the discovery threshold are provided, other values ​​can be implemented. For example, the mobile device can adjust the discovery threshold by a larger amount (e.g., a higher percentage) when the count of control devices in the discovery range is less than the target range. ML / E / ZuZo / uuY M comparison with when the control device count is greater than the target range. In one example, the discovery threshold can be increased in multiples of 2 dBm when the control device count in the discovery range is less than the target range, while the discovery threshold can be reduced in multiples of 1 dBm when the control device count in the discovery range is greater than the target range. This can help enable a greater number of control devices to transmit control device beacons on the network in an attempt to ensure at least a minimum level of network communication. Figure 10 is a block diagram illustrating an example of a network device 1000 (e.g., a mobile device and / or a processing device) as described herein. The network device 1000 may include a control circuit 1002 to control the functionality of the network device 1000. The control circuit 1002 may include one or more general-purpose processors, special-purpose processors, conventional processors, digital signal processors (DSPs), microprocessors, integrated circuits, a programmable logic device (PLD), application-specific integrated circuits (ASICs), and / or the like.The control circuit 1002 can perform signal encoding, data processing, power control, image processing, input / output processing and / or any other functionality that enables the network device 1000 to operate as described herein. Control circuit 1002 can store information in and / or retrieve information from memory 1004. Memory 1004 can include non-removable and / or removable memory. Non-removable memory can include random access memory (RAM), read-only memory (ROM), a hard drive, and / or any other type of non-removable memory storage. Removable memory can include a subscriber identity module (SIM) card, a removable memory card (e.g., a digital camera memory card), and / or any other type of removable memory. The network device 1000 may include a camera 1006 that can communicate with the control circuit 1002. The camera may include a digital camera or other optical device capable of generating images or videos (e.g., image sequences) to be captured on the network device 1000 using visible light. The camera may include a light capable of flashing, modulating, or turning on in response to signals received from the control circuit. The network device 1000 may include a wireless communication circuit 1010 for transmitting and / or receiving information wirelessly. For example, the wireless communication circuit 1010 may include an RF transceiver for transmitting and receiving RF communication signals via an antenna 1012 or another communication module capable of wireless communication. The wireless communication circuit 1010 may communicate with the control circuit 1002 to transmit information to and / or from the control circuit 1002. For example, the wireless communication circuit 1010 may send information from the control circuit 1002 via network communication signals. The wireless communication circuit 1010 may send information to the control circuit 1002 that is received via network communication signals. The network device 1000 may include a wireless communication circuit 1018 for transmitting and / or receiving information wirelessly. For example, the wireless communication circuit 1018 may include an RF transceiver for transmitting and receiving RF communication signals via an antenna 1017 or another communication module capable of wireless communication. The wireless communication circuit 1018 may communicate with the control circuit 1002 to transmit information to and / or from the control circuit 1002. For example, the wireless communication circuit 1018 may send information from the control circuit 1002 via network communication signals. The wireless communication circuit 1018 may send information to the control circuit 1002 that is received via network communication signals.Wireless communication circuit 1018 can communicate over the same network and / or protocol, or a different one, than wireless communication circuit 1010. For example, wireless communication circuit 1018 can communicate over a short-range RF protocol (e.g., NFC, BLE, or another short-range RF protocol), and wireless communication circuit 1010 can communicate over a different RF protocol or network (e.g., a dedicated protocol, Wi-Fi, cellular, etc.). Control circuit 1002 can also communicate with a display 1008. Display 1008 can provide information to a user in the form of a graphical and / or textual display. Control circuit 1002 can signal display 1008, or parts thereof, to modulate and / or turn the display on and / or off to communicate information from display 1008. Communication between display 1008 and control circuit 1002 can be bidirectional, as display 1008 can include a touchscreen module capable of receiving input from a user and providing that input to control circuit 1002. Network device 1000 may include an actuator 1016. Control circuit 1002 may respond to actuator 1016 to receive user input. For example, control circuit 1002 may be configured to receive a button press from a user on network device 1000 to make a selection or perform other functionality on network device 1000. The 1000 network device may include an optical transmitter 1020. The optical transmitter 1020 can be used to transmit an optical signal to one or more control devices (e.g., lighting control devices) as part of an allocation and / or bonding procedure. One or more of the modules in the 1000 network device can be powered by a 1014 power supply. The 1014 power supply can include an AC power supply or a DC power supply, for example. The 1014 power supply can generate a DC supply voltage Vcc to power the modules within the 1000 network device. Figure 11 is a block diagram of an illustrative system controller 1100. The system controller 1100 may comprise a control circuit 1110, which may include one or more processors (e.g., a microprocessor), a microcontroller, a programmable logic device (PLD), a field-programmable gate array (FPGA), an application-specific integrated circuit (ASIC), or any other suitable processing device. The control circuit 1110 may perform signal encoding, data processing, image processing, power control, input / output processing, and / or any other functionality that enables the system controller 1100 to perform as described herein. The system controller 1100 may comprise a hardwired communication circuit 1112 that may be coupled to, for example, an Ethernet connector.The wired communication circuit 1112 can be adapted to connect to a wired digital communication link (e.g., an Ethernet communication link) to enable the control circuit 1110 to communicate with network communication devices on a network. The wired communication circuit 1112 can also be configured to connect wirelessly to the network, e.g., using Wi-Fi technology to transmit and / or receive network communication signals. The system controller 1110 may comprise a wireless communication circuit 1116, for example, which includes an RF transceiver coupled to an antenna for transmitting and / or receiving RF communication signals. The wireless communication circuit 1116 may communicate using a network or protocol different from the wired communication circuit 1112, such as a dedicated protocol (e.g., the ClearConnect® protocol). The control circuit 1110 may be coupled to the wireless communication circuit 1116 to transmit messages via RF communication signals, for example, to control load control devices in response to messages received via the wired communication circuit 1112. The control circuit 1110 may be configured to receive messages from, for example, the load control devices and / or other control source devices. The control circuit 1110 can be sensitive to an actuator 1120 to receive user input. For example, the control circuit 1110 can be configured to associate the system controller 1100 with one or more devices in a load control system in response to actuations of the actuator 1120. The system controller 1100 can comprise additional actuators to which the control circuit 1110 can be sensitive. Control circuit 1110 can store information in and / or retrieve information from memory 1118. Memory 1118 can include non-removable and / or removable memory for storing computer-readable media. Non-removable memory can include random-access memory (RAM), read-only memory (ROM), a hard disk, and / or any other type of non-removable memory storage. Removable memory can include a subscriber identity module (SIM) card, a memory card (e.g., a digital camera memory card), and / or any other type of removable memory. Control circuit 1110 can access memory 1118 for executable instructions and / or other information that can be used by system controller 1100.Control circuit 1110 can store the device identifiers of the devices to which system controller 1100 is associated in memory 1118. Control circuit 1110 can access instructions in memory 1118 to transmit instructions and / or perform other functions described herein. The system controller 1100 may include a power supply 1124 for generating a DC supply voltage Vcc to power the control circuit 1110, the wired communication circuit 1112, the wireless communication circuit 1116, the memory 1118, and / or other circuits of the system controller 1100. The power supply 1124 may be connected to a power supply connector 1126 (e.g., a USB port) to receive a supply voltage (e.g., a DC voltage) and / or to draw current from an external power source. Figure 12 is a block diagram illustrating an example of a load control device 1200. The load control device 1200 may be a control target device, such as a lighting control device, for example.The load control device 1200 may be a dimmer, an electronic switch, an electronic ballast for lamps, an LED driver for LED light sources, or another load control device. The load control device 1200 may include a communication circuit 1202. The communication circuit 1202 may include an RF receiver, an RF transceiver, or another communication module capable of wired and / or wireless communication. Wireless communication may be carried out via an antenna 1216. The communication circuit 1202 can communicate with a control circuit 1204. The control circuit 1204 can include one or more general-purpose processors, special-purpose processors, conventional processors, digital signal processors (DSPs), microprocessors, integrated circuits, a programmable logic device (PLD), application-specific integrated circuits (ASIO), or similar components. The control circuit 1204 can perform signal encoding, data processing, power control, input / output processing, and any other functionality that enables the load control device 1200 to operate as intended. ΜΛ / Ε / ΖυΖο / υυΊ describes herein. The control circuit 1204 can store information in and / or retrieve information from a memory 1206. For example, memory 1206 can maintain a device database of associated device identifiers and / or executable instructions for performance as described herein. Memory 1206 can include non-removable and / or removable memory. The load control circuit 1208 can receive instructions from the control circuit 1204 and can control the electrical load 1210 based on the received instructions. The load control circuit 1208 can receive power through the hot-swappable connection 1212 and the neutral connection 1214 and can supply power to the electrical load 1210. The electrical load 1210 can include a lighting load or any other type of electrical load. The control circuit 1204 can receive information from the occupancy sensor 1222.The information received from the occupancy sensor may include an indication of an occupied or unoccupied condition. The occupancy sensor 1222 may include an infrared (IR) sensor, a visible light sensor, or another sensor capable of detecting motion. The occupancy sensor may send an indication to the control circuit 1204 in response to motion detection (e.g., a primary motion event or a secondary motion event). Control circuit 1204 can communicate with beacon transmitter circuit 1224 (e.g., a short-range communication circuit) to transmit beacon messages. Beacon transmitter circuit 1224 can communicate beacon messages via RF communication signals, for example. Beacon transmitter circuit 1224 can be a one-way communication circuit or a two-way communication circuit capable of receiving information on the same network and / or protocol in which the beacon messages are transmitted. The information received by beacon transmitter circuit 1224 can be provided to control circuit 1204. The control circuit 1204 can receive information from a visible light sensor 1226 (e.g., a camera). The visible light sensor 1226 can be used to receive an optical signal, for example, from a network device, as part of an allocation and / or bonding procedure. The control circuit 1204 can illuminate a visual indicator 1218 to provide feedback to a user. For example, the control circuit 1204 can cause the visual indicator 1218 to flash or strobe to indicate an occupancy condition identified by the occupancy sensor 1222, which was entered into a configuration mode, or to provide other feedback from the load control device 1200. The control circuit 1204 can be configured to illuminate the visual indicator 1218 in different colors. The visual indicator 1218 can be illuminated, for example, by one or more light-emitting diodes (LEDs). The load control device 1200 can comprise more than one visual indicator. Figure 13 is a block diagram illustrating an example control source device 1300 as described herein. The control source device 1300 may be a remote control device, an occupancy sensor, a visible light sensor, and / or another control source device. The control source device 1300 may include a control circuit 1302 to control the functionality of the control source device 1300. The control circuit 1302 may include one or more general-purpose processors, special-purpose processors, conventional processors, digital signal processors (DSPs), microprocessors, integrated circuits, a programmable logic device (PLD), application-specific integrated circuits (ASICs), or similar components.The control circuit 1302 can perform signal encoding, data processing, power control, input / output processing, or any other functionality that enables the control source device 1300 to perform as described herein. The control circuit 1302 can store information in memory 1304 and / or retrieve information from it. Memory 1304 may include non-removable memory and / or removable memory, as described herein. The control source device 1300 may include a communication circuit 1308 for transmitting and / or receiving information. The communication circuit 1308 may transmit and / or receive information via wired and / or wireless communications. The communication circuit 1308 may include a transmitter, an RF transceiver, or other circuit capable of carrying out wired and / or wireless communications. The communication circuit 1308 may be in communication with the control circuit 1302 for transmitting and / or receiving information. The control circuit 1302 can also communicate with an input circuit 1306. The input circuit 1306 can include an actuator (e.g., one or more buttons) or a sensor circuit (e.g., an occupancy sensor circuit, camera, or other visible light detection circuit, etc.) to receive inputs that can be sent to a device to control an electrical load. For example, the control source device can receive an input from the input circuit 1306 to put the control circuit 1302 into a configuration mode and / or communicate association messages from the control source device. The control circuit 1302 can receive information from the input circuit 1306 (e.g., an indication that a button has been pressed or information has been detected). Each of the modules within the control source device 1300 can be powered by a power supply 1310. Although the features and elements are described above in particular combinations, a feature or element may be used alone or in any combination with the other features and elements. The procedures described herein may be implemented in a computer program, software, or firmware embedded in a computer-readable medium for execution by a computer or processor. Examples of computer-readable media include electronic signals (transmitted through connections) Wired or wireless ML / E / ZuZo / uu΅Ί and computer-readable storage media. Examples of computer-readable storage media include, but are not limited to, read-only memory (ROM), random-access memory (RAM), removable disks, and optical media such as CD-ROMs and digital versatile discs (DVDs).

Claims

1. A mobile device comprising: a processor configured to: transmit a first mobile device beacon message including a first discovery threshold to one or more control devices; receive one or more control device beacon messages transmitted by the control devices; determine a number of discovered control devices based on the received control device beacon messages; compare the number of discovered control devices to a target range; adjust the first discovery threshold based on whether the number of discovered control devices is greater or less than the target range; and transmit a second mobile device beacon message including the adjusted discovery threshold.

2. The mobile device of claim 1, wherein the processor is further configured to: adjust the first discovery threshold by a greater amount the further the number of discovered control devices is from the target range.

3. The mobile device of claim 1, wherein the processor is further configured to: determine that the number of discovered control devices is greater than a first high-side threshold value greater than the target range; and increase the first discovery threshold by a first threshold increment.

4. The mobile device of claim 3, wherein the processor is further configured to: start an adjustment timer at an adjustment value to delay a further increase of the discovery threshold until the completion of the adjustment timer; and maintain the first discovery threshold prior to the completion of the adjustment timer.

5. The mobile device of claim 3, wherein the processor is further configured to: determine that the number of discovered control devices is greater than a second high-side threshold value greater than the target range, wherein the second high-side threshold value is closer to the target range than the first low-side threshold value; and increase the first discovery threshold by a second threshold increment that is less than the first threshold increment.

6. The mobile device of claim 1, wherein the processor is further configured to: determine that the number of discovered control devices is less than a first low-side threshold value; and decrease the first discovery threshold by a first threshold decrement.

7. The mobile device of claim 6, wherein the processor is further configured to: determine that the number of discovered control devices is less than a second low-side threshold value greater than the target range, wherein the second low-side threshold value is closer to the target range than the first low-side threshold value; and decrease the first discovery threshold by a second threshold decrement that is less than the first threshold decrement.

8. A method comprising: transmitting a first mobile device beacon message that includes a first discovery threshold to one or more control devices; receiving one or more control device beacon messages transmitted by the control devices; determining a number of discovered control devices based on the received control device beacon messages; comparing the number of discovered control devices to a target range; adjusting the first discovery threshold based on whether the number of discovered control devices is greater or less than the target range; and transmitting a second mobile device beacon message that includes the adjusted discovery threshold.

9. The method of claim 8, further comprising: adjusting the first discovery threshold by a greater amount the further the number of discovered control devices is from the target range.

10. The method of claim 8, further comprising: determining that the number of discovered control devices is greater than a first high-side threshold value greater than the target range; and increasing the first discovery threshold by a first threshold increment.

11. The method of claim 10, further comprising: initiating an adjustment timer at an adjustment value to delay a further increase of the discovery threshold until the completion of the adjustment timer; and maintaining the first discovery threshold prior to the completion of the adjustment timer.

12. The method of claim 10, further comprising: determining that the number of discovered control devices is greater than a second high-side threshold value greater than the target range, wherein the second high-side threshold value is closer to the target range than the first low-side threshold value; and increasing the first discovery threshold by a second threshold increment that is less than the first threshold increment.

13. The method of claim 8, further comprising: determining that the number of discovered control devices is less than a first low-side threshold value; and decreasing the first discovery threshold by a first threshold decrement.

14. The method of claim 13, further comprising: determining that the number of discovered control devices is less than a second low-side threshold value greater than the target range, wherein the second low-side threshold value is closer to the target range than the first low-side threshold value; and decreasing the first discovery threshold by a second threshold decrement that is less than the first threshold decrement.

15. The method of claim 8, wherein the first beacon message from the mobile device includes an incoming discovery threshold that is greater than the first discovery threshold and the second beacon message from the mobile device includes an outgoing discovery threshold that is less than the set discovery threshold, wherein the incoming discovery threshold is configured to be used by a control device to determine that the control device has entered a discovery range of the mobile device, and wherein the outgoing discovery threshold is configured to be used by the control device to determine that the control device has exited a discovery range of the mobile device.

16. A load control system comprising: a mobile device configured to transmit a first mobile device beacon message that includes a discovery threshold; and a control device configured to: receive the first mobile device beacon message; determine that the control device is within the mobile device's discovery range based on a received signal strength amplitude at which the first mobile device beacon message was received and the received discovery threshold; and in response to the control device being within the discovery range, transmit a control device beacon message; wherein the mobile device is further configured to: receive the control device beacon message transmitted by the control device;determine a number of discovered control devices based on control device beacon messages received from a plurality of control devices including the control device; compare the number of discovered control devices to a target range; adjust the discovery threshold based on whether the number of discovered control devices is greater or less than the target range; and transmit a second mobile device beacon message that includes the adjusted discovery threshold.

17. The load control system of claim 16, wherein the mobile device is further configured to: adjust the discovery threshold by a greater amount the further the number of discovered control devices is from the target range.

18. The load control system of claim 16, wherein the mobile device is further configured to: determine that the number of discovered control devices is greater than a first high-side threshold value greater than the target range; and increase the discovery threshold by a first threshold increment.

19. The load control system of claim 18, wherein the mobile device is further configured to: start an adjustment timer at an adjustment value to delay a further increase of the discovery threshold until the completion of the adjustment timer; and maintain the discovery threshold prior to the completion of the adjustment timer.

20. The load control system of claim 18, wherein the mobile device is further configured to: determine that the number of discovered control devices is greater than a second high-side threshold value greater than the target range, wherein the second high-side threshold value is closer to the target range than the first low-side threshold value; and increase the discovery threshold by a second threshold increment that is less than the first threshold increment.

21. The load control system of claim 16, wherein the mobile device is further configured to: determine that the number of discovered control devices is less than a first low-side threshold value; and decrease the discovery threshold by a first threshold decrement.

22. The load control system of claim 21, wherein the mobile device is further configured to: determine that the number of discovered control devices is less than a second low-side threshold value greater than the target range, wherein the second low-side threshold value is closer to the target range than the first low-side threshold value; and decrease the discovery threshold by a second threshold decrement that is less than the first threshold decrement.

23. The load control system of claim 16, wherein the control device is further configured to determine that the control device is within the discovery range based on an input discovery threshold value and an output discovery threshold value.

24. The load control system of claim 23, wherein the control device is configured to determine the input discovery threshold value and the output discovery threshold value based on the received discovery threshold and one or more threshold offsets.

25. The load control system of claim 24, wherein the control device configured to determine that the control device is within the discovery range comprises the control device being configured to: determine whether the control device is within a configuration mode; calculate the incoming discovery threshold and the outgoing discovery threshold based on the received discovery threshold and one or more threshold offsets; and compare the received signal strength amplitude at which the first beacon message from the mobile device was received with the incoming discovery threshold.

26. The load control system of claim 24, wherein the first beacon message from the mobile device includes one or more threshold offsets.

27. The load control system of claim 24, wherein one or more threshold displacements are pre-stored in a memory of the control device.

28. The load control system of claim 16, wherein the first beacon message ML / E / ZuZo / uuJ from the mobile device includes an incoming discovery threshold that is greater than the received discovery threshold and the second beacon message from the mobile device includes an outgoing discovery threshold that is less than the set discovery threshold, and wherein the control device is further configured to: determine that the control device has entered the discovery range of the mobile device based on the received signal strength amplitude at which the first beacon message from the mobile device was received and the incoming discovery threshold; receive the second beacon message from the mobile device;and determine that the control device has moved out of the mobile device's discovery range based on a received signal strength amplitude at which the second beacon message was received from the mobile device and the exit discovery threshold.

29. A load control system comprising: a mobile device configured to transmit mobile device beacon messages that include a discovery threshold; and a control device configured to: receive a first beacon message from the mobile device; measure a received signal strength amplitude at which the beacon message was received from the mobile device; determine that the control device is within a discovery range of the mobile device based on the received signal strength amplitude and the received discovery threshold; transmit a control device beacon message in response to the determination that the control device is within the discovery range.receive a second beacon message from the mobile device; measure a received signal strength amplitude at which the second beacon message from the mobile device was received; determine that the control device is outside the discovery range of the mobile device based on the received signal strength amplitude of the second beacon message from the mobile device and the received discovery threshold; and continue transmitting the control device's beacon message for a discovery period.

30. The load control system of claim 29, wherein the control device is further configured to determine that the control device is outside the discovery range of the mobile device based on the received signal strength amplitude of the mobile device's beacon message, a threshold offset, and the received discovery threshold.

31. The load control system of claim 30, wherein the control device is further configured to: subtract the threshold offset from the received discovery threshold to generate an outgoing discovery threshold; and determine that the control device is outside the mobile device's discovery range based on the received signal strength amplitude of the mobile device's second beacon message and the outgoing discovery threshold.

32. The load control system of claim 29, wherein the control device is further configured to: add a threshold offset to the received discovery threshold to generate an incoming discovery threshold; and determine that the control device is within the mobile device's discovery range based on the received signal strength amplitude and the incoming discovery threshold.

33. A load control system comprising: a mobile device configured to transmit a first mobile device beacon message that includes a first discovery threshold; and a control device configured to: receive the first mobile device beacon message; determine that the control device has entered a discovery range of the mobile device based on a received signal strength amplitude at which the first mobile device beacon message was received and an incoming discovery threshold that is greater than the first discovery threshold; transmit a control device beacon message when the control device is within the discovery range; receive a second mobile device beacon message from the mobile device, the second mobile device beacon message including a second discovery threshold;and determine that the control device has moved out of the mobile device's discovery range based on a received signal strength amplitude at which the second beacon message was received from the mobile device and an exit discovery threshold that is less than the second discovery threshold.

34. The load control system of claim 33, wherein the control device is further configured to determine the incoming discovery threshold by adding a first threshold offset to the first discovery threshold, and to determine the outgoing discovery threshold by subtracting a second threshold offset from the second discovery threshold.

35. The load control system of claim 34, wherein the first threshold displacement is equal to the second threshold displacement.

36. The load control system of claim 34, wherein the control device is configured to receive the first threshold offset in the first beacon message from the mobile device and to receive the second threshold offset in the second beacon message from the mobile device.

37. The load control system of claim 34, wherein the control device is configured to retrieve the first and second threshold offsets from memory.

38. The load control system of claim 33, wherein the control device is configured to receive the incoming discovery threshold in the first beacon message from the mobile device and to receive the outgoing discovery threshold in the second beacon message from the mobile device.

39. The load control system of claim 33, wherein the control device configured to determine that the control device is within the discovery range comprises the control device being configured to: determine whether the control device is within a configuration mode; calculate one or more of an input discovery threshold or an output discovery threshold based on the received discovery threshold and one or more threshold offsets; and compare the received signal strength amplitude at which the first beacon message from the mobile device was received with the input discovery threshold or the output discovery threshold.

40. The load control system of claim 39, wherein the control device is further configured to: determine that the control device is in configuration mode; calculate the output discovery threshold based on the received discovery threshold and one or more threshold offsets; and compare the received signal strength amplitude at which the first beacon message was received from the mobile device with the output discovery threshold.

41. The load control system of claim 39, wherein the control device is further configured to:

56. The control device of claim 47, wherein the communication circuit is further configured to receive a second beacon message from the mobile device comprising a second discovery threshold and one or more offsets, and wherein the control circuit is further configured to: receive, from the communication circuit, an indication of the second beacon message from the mobile device; determine that the control device is within a discovery range of the mobile device based on a received signal strength amplitude at which the second beacon message from the mobile device, the second discovery threshold, and at least one of the one or more threshold offsets were received; and in response to the control device being within the discovery range,transmit a second beacon message from the control device.

57. The control device of claim 47, wherein the control circuit is further configured to: control an amount of power supplied to one or more lighting loads of a lighting fixture associated with the control device to provide a first type of feedback in response to the transmission of the beacon message from the control device; receive, via the communication circuit, an indication that the control device has been selected for configuration; and control the amount of power supplied to the one or more lighting loads to provide a second type of feedback in response to the receipt of the indication that the control device has been selected for configuration.

58. The control device of claim 57,wherein the control circuit is further configured to: receive, via the communication circuit, an indication that the control device has been assigned; and control the amount of power supplied to one or more lighting loads to provide a third type of feedback in response to receiving the indication that the control device has been assigned.

59. A method comprising: receiving, in a control device,a first beacon message from the mobile device that includes a first discovery threshold; determining that the control device has entered a discovery range of a mobile device based on a received signal strength amplitude at which the first beacon message from the mobile device was received and an entry discovery threshold that is 100 times greater than the received discovery threshold; transmitting a beacon message from the control device when the control device is within discovery range; receiving, on the control device,a second beacon message from the mobile device that includes a second discovery threshold; and determining that the control device has left the discovery range of the mobile device based on a received signal strength amplitude at which the second beacon message from the mobile device was received and an outgoing discovery threshold that is less than the second discovery threshold.

60. The method of claim 59, further comprising determining the incoming discovery threshold by adding a first threshold shift to the first discovery threshold, and determining the outgoing discovery threshold by subtracting a second threshold shift from the second discovery threshold.

61. The method of claim 60, wherein the first threshold shift is equal to the second threshold shift.

62. The method of claim 60,wherein the first beacon message from the mobile device comprises the first threshold offset and the second beacon message from the mobile device comprises the second threshold offset.

63. The method of claim 60, wherein the first and second threshold offsets are pre-stored in a memory of the control device.

64. The method of claim 59, wherein the first beacon message from the mobile device comprises the incoming discovery threshold and wherein the second beacon message from the mobile device comprises the outgoing discovery threshold.

65. The method of claim 59,wherein determining that the control device is within the discovery range comprises: determining whether the control device is in a configuration mode; calculating one or more incoming discovery thresholds or outgoing discovery thresholds based on the received discovery threshold and one or more threshold offsets; and comparing the received signal strength amplitude at which the first beacon message from the mobile device was received with the incoming discovery threshold or outgoing discovery threshold.

66. The method of claim 65,further comprising: determining that the control device is in configuration mode; calculating the outgoing discovery threshold based on the received discovery threshold 101 and one or more threshold offsets; and comparing the received signal strength amplitude at which the first beacon message from the mobile device was received with the outgoing discovery threshold.

67. The method of claim 65, further comprising: determining that the control device is not in configuration mode; calculating the incoming discovery threshold based on the received discovery threshold and one or more threshold offsets; and comparing the received signal strength amplitude at which the first beacon message from the mobile device was received with the incoming discovery threshold.

68. The method of claim 59, further comprising: receiving, at the control device,a second beacon message from the mobile device that includes a second discovery threshold and one or more offsets; determining that the control device is within a discovery range of the mobile device based on a received signal strength amplitude at which the second beacon message from the mobile device, the second discovery threshold, and at least one of the one or more threshold offsets were received; and in response to the control device being within the discovery range, transmitting a second beacon message from the control device.

69. The method of claim 59,further comprising: controlling an amount of power supplied to one or more lighting loads of a lighting fixture associated with the control device to provide a first type of feedback in response to the transmission of the control device's beacon message; receiving an indication that the control device has been selected for configuration; and controlling the amount of power supplied to the one or more lighting loads to provide a second type of feedback in response to receiving the indication that the control device has been selected for configuration.

70. The method of claim 69,which further comprises: receiving an indication that the control device has been assigned; and controlling the amount of power supplied to one or more lighting loads to provide a third type of feedback in response to receiving the indication that the control device has been assigned.

Images