Automatically adjusting a discovery range for discovering wireless control devices

Abstract

Beacon messages can be used to debug load control systems. The load control system may include control devices, each including a beacon transmitting circuit configured to transmit a beacon message including an identifier associated with the control device. Network devices, such as mobile devices, can discover the control devices based on beacon messages received from them. In response to the discovery of a control device, it can be added to a temporary group of control devices for co-configuration and / or control. The control device can be discovered based on the signal strength at the time the beacon message is received. Mobile devices can adjust a discovery threshold used to discover a target number of control devices in the load control system.

Description

[0001] Cross-reference to related applications

[0002] This application claims the benefit of U.S. Provisional Patent Application No. 63 / 019,049, filed May 1, 2020, and U.S. Provisional Patent Application No. 63 / 071,183, filed August 27, 2020, the contents of which are incorporated herein by reference in their entirety. Background Technology

[0003] A load control system may include electrical loads (e.g., lighting loads) and load control devices (e.g., ballasts, LED drivers, etc.) for controlling the power to the lighting loads. The load control devices may be controlled by messages from remote control devices or sensors (e.g., occupancy sensors, etc.) capable of sending instructions to the load control devices via messages to control the electrical loads. The load control devices may receive communications from a system controller for performing load control, which may be programmed using configuration information for controlling the load control devices within the system. After the devices are installed in the load control system, the load control system can be debugged to achieve proper configuration and communication of the devices, thereby controlling the electrical loads.

[0004] Typically, after a load control system is installed in a location such as a residence or office, the system controller can assign link addresses to the lighting control devices controlled by the system controller. Link addresses are used to send commands to the load control devices to control the electrical load. This assignment can be random. For example, the system controller may be able to control multiple lighting control devices, such as lighting ballasts or LED drivers, and can randomly assign a different link address to each lighting control device.

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

[0006] To control the load controllers at desired locations, during commissioning, users may have to identify the lighting loads controlled by the lighting controllers with assigned link addresses and associate those link addresses with their identified locations within the building. Because a building may contain many lighting controllers with unknown link addresses (e.g., in different rooms, on different floors, etc.), users may have to power the lighting loads with known link addresses and search for the location of the controlled (e.g., turning on, flashing, etc.) lighting loads within the building to associate the physical location of the lighting controller with its assigned link address. The controlled light may be located in a different room than the room currently occupied by the user configuring the system, potentially requiring the user to move between different rooms within the building to commission the system.

[0007] A similar time-consuming process can be implemented to configure other devices in the load control system. Identifying the location of control devices in the system and associating them to achieve appropriate load control during system commissioning can be time-consuming and expensive. Summary of the Invention

[0008] A load control system can be commissioned as described herein for controlling one or more electrical loads. During commissioning of the load control system, one or more control devices can be identified and / or selected for co-configuration and / or control. The selected control devices can be included in a temporary group of target devices for configuration and / or control. For example, the load control system may include lighting control devices that can be selected and / or grouped for co-control at a location or area. Control devices can be added to and / or removed from the temporary group for co-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, for controlling the temporary group of control devices based on messages received from the control source device.

[0009] Beacon messages can be used to debug load control systems. For example, a load control system may include lighting control devices, each including a beacon (e.g., a control device beacon) transmitting circuit configured to transmit a corresponding beacon message including an identifier associated with the lighting control device. Network devices can discover the lighting control devices based on beacon messages received from them. In response to the discovery of the lighting control device, it can be added to a temporary group of lighting control devices for co-configuration and / or control.

[0010] Beacon messages can be emitted periodically and / or in response to triggering events. For example, beacon messages can be emitted in response to a message, actuation of a button on a control device, or in response to an occupancy status detected by an occupancy sensor. Lighting controls in a load control system can communicate directly with an occupancy sensor (e.g., installed in the same luminaire), and the lighting controls can emit beacon messages (e.g., periodic emission of each beacon message or a start beacon message) in response to an occupancy status detected by the occupancy sensor.

[0011] A lighting control device may transmit a control device beacon message (e.g., enter configuration mode) upon 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 may receive the mobile device beacon message and may determine the Received Signal Strength Indicator (RSSI) at the time of receipt. If the RSSI at the time of receipt of the mobile device beacon message is greater than or equal to the discovery threshold, the lighting control device may transmit the control device beacon message. If the RSSI at the time of receipt of the mobile device beacon message is less than the discovery threshold (e.g., the mobile device is outside the detection range of the lighting control device), the lighting device may stop transmitting the control device beacon message.

[0012] Control devices can be detected based on the signal strength when a corresponding beacon message is received. For example, if the signal strength when a corresponding beacon message for a lighting control device is received is higher than a detection threshold, the lighting control device can be detected. The detection threshold can be adjusted to detect other control devices within a wider or more limited detection range. For example, the detection threshold can be adjusted (e.g., by a mobile device) such that the number of control devices receiving mobile device beacon messages higher than the detection threshold (e.g., and transmitting corresponding control device beacon messages) is within a target range. The target range can have a low-side threshold and a high-side threshold. For example, the target range can be 15 to 25 devices. If the number of control devices receiving mobile device beacon messages is greater than the target range, the detection threshold can be increased; if the number of control devices receiving mobile device beacon messages is less than the target range, the detection threshold can be decreased. The amount of adjustment to the detection threshold can depend on the number of control devices receiving mobile device beacon messages.

[0013] For example, a mobile device can transmit a mobile device beacon message that includes a detection threshold. If a given control device receives a mobile device beacon message with a signal strength higher than the detection threshold, the control device can respond to the mobile device beacon message by transmitting a control device beacon message. The mobile device can count the number of control devices responding to the mobile device beacon message within a predefined time period (e.g., the number of detected control devices). If the number of detected control devices is within a target range, the mobile device may not change the detection threshold. If the number of detected control devices is below the defined range, the mobile device can transmit a second mobile device beacon message with a reduced detection threshold. Conversely, if the number of detected control devices is above the target range, the mobile device can transmit a mobile device beacon message with an increased detection threshold. If the number of detected control devices is closer to the target range, the mobile device can increase or decrease the detection threshold by a relatively small amount, and if the number of control devices is further away from the target range, the mobile device can increase or decrease the detection threshold by a relatively large amount.

[0014] After receiving a mobile device beacon message with a signal strength above a detection threshold (e.g., even if the control device receives a second mobile device beacon message including the second detection threshold with a signal strength below the second detection threshold), the control device may continue to transmit control device beacon messages during the detection period. When the mobile device increases the detection threshold, the mobile device may start an adjustment timer and may maintain the detection threshold (e.g., not increase the detection threshold) until the adjustment timer expires, in an attempt to improve the accuracy of counting the number of detected control devices.

[0015] The control device can implement hysteresis for entering and exiting a discovery range (e.g., a configuration mode) based on a discovery threshold. Implementing hysteresis can be used to make the control device more likely to remain in its current state (e.g., within or outside the configuration mode) regardless of minor fluctuations in signal strength when receiving continuous mobile device beacon messages. For example, the discovery range can be based on a discovery threshold and a first offset for entering the discovery range (e.g., entering the configuration mode), and based on the discovery threshold and a second offset (e.g., the same as and / or different from the first offset) for exiting the discovery range (e.g., exiting the configuration mode). The mobile device can include one or more offsets in the mobile device beacon message. The offsets can be pre-stored in the memory of the control device. Alternatively, the mobile device can include an entry discovery threshold and / or an exit discovery threshold in the mobile device beacon message. The entry discovery threshold can be greater than the discovery threshold, while the exit discovery threshold can be less than the discovery threshold. The control device can use the offset(s), the entry discovery threshold, and / or the exit discovery threshold to determine whether to transmit a control device beacon message (e.g., whether to enter the configuration mode, remain in the configuration mode, or exit the configuration mode). For example, if the control device is not currently in a configuration mode for transmitting control device beacon messages, the control device can add a first offset to the discovery threshold, thereby increasing the discovery threshold. The control device can then compare the received signal strength (such as Received Signal Strength Indicator (RSSI)) when a mobile device beacon message is received with the increased discovery threshold or the entry discovery threshold to determine whether to transmit the control device beacon message. If the control device is currently in a configuration mode for transmitting control device beacon messages, the control device can subtract a second offset from the discovery threshold, thereby decreasing the discovery threshold. The control device can then compare the received signal strength when a mobile device beacon message is received with the decreased discovery threshold or the exit discovery threshold to determine whether to continue transmitting control device beacon messages. Offsets and / or entry and exit discovery thresholds can be used in addition to and / or as an alternative to the discovery period. Attached Figure Description

[0016] Figure 1 A representative load control system is shown for configuring and / or controlling one or more control devices using beacon messages.

[0017] Figure 2A A representative load control environment is shown, in which... Figure 1 The load control system shown can be implemented to configure and / or control one or more control devices using beacon messages.

[0018] Figure 2B It is used in Figure 1 A diagram illustrating an example network for communication within a load control system.

[0019] Figure 3 This is a system diagram that illustrates a representative control system used to configure and / or control one or more control devices using beacon messages.

[0020] Figure 4 It is a flowchart that depicts an example program (e.g., a debugger) used to debug a control system.

[0021] Figure 5 It is a system flowchart that depicts an example message flow for discovering control devices to achieve the claiming and / or association of control devices.

[0022] Figure 6 It is a flowchart that depicts an example procedure for discovering control devices to achieve the claiming and / or association of control devices.

[0023] Figure 7 This is another flowchart that depicts an example procedure for discovering control devices and providing feedback to implement configuration and / or control using beacon messages.

[0024] Figure 8A It is a flowchart that depicts an example procedure for transmitting control device beacon messages to enable the configuration and / or control of the control device.

[0025] Figure 8B This is another flowchart that depicts an example procedure for transmitting control device beacon messages to enable configuration and / or control of the control device.

[0026] Figure 9 It is a flowchart that depicts an example procedure for adjusting the discovery threshold used to discover the control device in order to configure and / or control the control device.

[0027] Figure 10 This is a block diagram illustrating an example network device as described herein.

[0028] Figure 11 This is a block diagram of the example system controller.

[0029] Figure 12 This is a block diagram illustrating an example load control device.

[0030] Figure 13 This is a block diagram illustrating an example control source device. Detailed Implementation

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

[0032] Commissioning a load control system may include identifying and / or associating control source devices and / or control target devices for individual and / or joint control. Devices can be associated with each other by storing their identifiers together in memory. Control devices can be associated in temporary groups to allow control of devices within those groups. Devices can be associated with temporary groups by storing their identifiers together with temporary group identifiers in memory. These associations can be stored on control devices or other devices within the load control system and referenced for appropriate responses, thereby enabling load control among associated devices in the system.

[0033] Beacon messages (e.g., control device beacon messages) can be used to identify and / or select control devices for co-configuration and / or control. Selected control devices may be temporarily grouped for configuration and / or control. Control device beacon messages may include unique identification information that can be used to identify and / or select control devices for co-configuration and / or control in a load control environment. Control device beacon messages may indicate or be used to indicate the proximity or location of a device and / or the current state of the device. Control device beacon messages may include a primary identifier and a secondary identifier for the control device (e.g., a load control device). The primary identifier may include a unique identifier for the corresponding control device, while the secondary identifier may include a unique identifier for the control device type, and vice versa. The primary and secondary identifiers may be used in combination to identify the unique identifier of the control device.

[0034] Network devices (e.g., mobile devices) may also transmit beacon messages (e.g., mobile device beacon messages). Mobile device beacon messages may include unique identification information that can be used to identify the network device and / or a detection threshold. Furthermore, beacon transmitting devices may transmit beacon messages (e.g., location beacon messages). Location beacon messages may include unique identification information that can be used to identify the location of the beacon transmitting device and / or a detection threshold. The beacon transmitting device may be a control device, or it may be a device independent of a control device.

[0035] Beacon messages (e.g., control device beacon messages, location beacon messages, and / or mobile device beacon messages) can be transmitted as radio frequency (RF) communication signals or as other types of signals that can be received by another control device, network device, and / or beacon transmitter adjacent to the device transmitting the beacon message. Beacon messages can be transmitted as short-range RF communication signals. For example, a beacon message can be an RF signal that is periodically transmitted using a short-range wireless communication protocol (e.g., Bluetooth and / or Bluetooth Low Energy (BLE) protocol). When a beacon message is transmitted using an RF communication signal, the beacon message can be identified by a device to indicate that the device is near or within the location of the device transmitting the beacon message. The proximity of the device to the beacon transmitter can be determined by the signal strength when the RF communication signal of the beacon message is received.

[0036] A load control system can be commissioned by using beacon messages to set up or configure control devices for performing load control. As described herein, control devices can be associated with each other and / or with a location using beacon messages. Location-associated control devices can be implemented to perform load control at that location.

[0037] Figure 1 A representative load control system 100 for configuring and / or controlling one or more control devices using beacon messages is illustrated. The load control system 100 may include a lighting fixture 110 (e.g., a panel luminaire) 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 electrical force supplied to the lighting loads 112 of the lighting fixture 110. The lighting control device 114 may be mounted inside the lighting fixture 110, on the outer surface of the lighting fixture 110, and / or adjacent to the lighting fixture 110 (e.g., on its exterior). The lighting control device 114 of the lighting fixture 110 may operate as a control target device for controlling the electrical force supplied to the lighting loads 112 to control the intensity level of the lighting fixture 110 in response to messages received from a control source device.

[0038] The load control system 100 may include lighting fixtures 120a-120c controlled by a load controller 121. Each of the lighting fixtures 120a-120c may have a corresponding lighting load(s) 122a-122c (e.g., LED light sources) and a corresponding lighting control device 124a-124c (e.g., LED drivers) for controlling the amount of power supplied to the corresponding lighting load(s) of the lighting fixture(s). The load controller 121 may be coupled to the lighting control device 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 device 124a-124c, thereby individually controlling the lighting loads 122a-122c. The load controller 121 can operate as a control target device for controlling lighting control devices 124a-124c that control the power supplied to lighting loads 122a-122c, in response to messages received from the control source device to control the intensity level of lighting fixtures 120a-120c. Furthermore, the load control system 100 can include lighting fixtures with multiple controllable light sources, which can be controlled by a single load controller (such as load controller 121).

[0039] 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) for controlling the electrical force supplied to the internal lighting load of the controllable light source 132. For example, the controllable light source 132 may be screwed into a standard Edison lamp holder of the lighting fixture 130. The controllable light source 132 of the lighting fixture 130 may operate as a control target device for controlling the intensity level of the lighting load of the controllable light source 132 in response to a message received from a control source device. Although lighting control devices 114, 124a-124c, and the controllable light source 132 may be provided as example control target devices, the load control system 100 may include other control target devices, such as, for example, motorized curtains, temperature control devices, and / or plug-in load control devices.

[0040] The illumination levels of lighting fixtures 110, lighting control devices 124a-124c, and / or controllable light sources 132 can be controlled according to lighting control commands received from a control source device. The control source device may be able to transmit messages via wired and / or wireless signals to a control target device (e.g., a load control device such as a lighting control device) to control an electrical load (e.g., a lighting load). Example control source devices in the load control system 100 may include an occupancy sensor 134, a remote control device 136, and / or another control source device capable of transmitting messages to lighting control devices 114, lighting control devices 124a-124c, and / or controllable light sources 122 to perform control. The load control system 100 may also include a system controller 140 and network devices, such as mobile devices 150, that can also operate as control source devices. For example, mobile device 150 may include a smartphone and / or a tablet computer.

[0041] The lighting control can be controlled in response to lighting control commands received from control source devices (e.g., occupancy sensor 134, remote control device 136, system controller 140, mobile device 150, and / or another control source device) to control the electrical power supplied to the lighting load 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. The lighting level can be controlled according to lighting control configuration information, such as preset configurations, zone configurations, occupancy configurations, and / or timing schedule configuration information that can be stored at the lighting control devices 114, 124a-124c, controllable light source 132, and / or system controller 140 or mobile device 150. The lighting control commands can be transmitted over a wireless communication network via radio frequency (RF) signal 102.

[0042] Occupancy sensor 134 can be a control source device configured to detect occupancy and / or vacancy in a space where load control system 100 is installed. Occupancy sensor 134 can transmit a message via RF communication signal 102 in response to detecting occupancy or vacancy. Although Figure 1The occupancy sensor 134 is shown transmitting messages via RF communication signal 102, but the occupancy sensor 134 can also communicate via wired communication. The system controller 140 can be configured to turn on and off lighting loads (e.g., lighting loads 112, 122a-122c, and / or controllable light source 122) of one or more lighting fixtures respectively in response to receiving an occupancy signal and an idle signal. The occupancy sensor 134 can also operate as an idle sensor, allowing the lighting loads to be manually turned on by the user and / or automatically turned off in response to detecting an idle signal from the sensor (e.g., the lighting loads do not turn on in response to detecting an occupancy condition). Examples of load control systems with occupancy and vacancy sensors are described in more detail in the following patents: U.S. Patent No. 8,009,042, jointly assigned, entitled “RADIO-FREQUENCY LIGHTING CONTROL SYSTEM WITH OCCUPANCY SENSING,” published August 30, 2011; U.S. Patent No. 8,199,010, entitled “METHOD AND APPARATUS FOR CONFIGURING AWIRELESS SENSOR,” published June 12, 2012; and U.S. Patent No. 8,228,184, entitled “BATTERY-POWERED OCCUPANCY SENSOR,” published July 24, 2012, the entire disclosure of which is incorporated herein by reference.

[0043] Although occupancy sensor 134 may be shown external to lighting fixture 110, sensor 116 may be integrated into lighting fixture 110 and / or communicate directly (e.g., wired or wirelessly) with lighting control device 114 of lighting fixture 110 to control lighting load 112. Furthermore, load controller 121 may be connected to sensor 126. Sensors 116 and 126 may be used to control lighting fixture 110 and / or lighting control devices 124a-124c, respectively. Sensors 116 and 126 may be occupancy sensors, visible light sensors (e.g., cameras), daylight sensors, optical sensors, and / or any other type of sensor. Sensors 116 and 126 may be occupancy sensors capable of detecting occupancy / vacancy status (e.g., using infrared signals). Sensors 116 and 126 may be visible light sensors (e.g., cameras) capable of detecting changes within the visible space of sensors 116 and 126.

[0044] Sensors 116 and 126 can be configured to operate similarly to occupancy sensor 134, but can communicate directly with lighting control device 114 and load controller 121 of lighting fixture 110, respectively. For example, lighting control device 114 of lighting fixture 110 can turn lighting load 112 on and off in response to receiving occupancy and idle signals from sensor 116, respectively. Similarly, load controller 121 can turn lighting loads 122a-122c on and off in response to receiving occupancy and idle signals from sensor 126, respectively.

[0045] The remote control device 136 may be a control source device configured to transmit messages via RF communication signal 102 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 in response to actuation of one or more buttons on the remote control device 136. Although Figure 1 The diagram shows the remote control device 136 transmitting messages via RF communication signal 102, but the remote control device 136 can also communicate via wired communication. The remote control device 136 can be a wall switch, dimmer switch, or another remote control device for controlling electrical loads. The system controller 140 can also initiate one or more messages.

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

[0047] System controller 140 can communicate directly with mobile device 150 via wired and / or wireless communication. System controller 140 can also communicate with mobile device 150 via network communication device 142. Network communication device 142 can be a wireless access point, such as, for example, 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 Wi-Fi, Wi-MAX, etc.) to allow mobile device 150 to communicate with other computing devices and / or networks (e.g., via the Internet). System controller 140 can also communicate with network communication device 142 via communication link 144, which can be a wired and / or wireless communication link. Although system controller 140 and network communication device 142 are... Figure 1 While shown as a separate device, network communication device 142 may be included in system controller 140. Network communication device 142 may also be configured to communicate with network devices, such as processing device 160 (e.g., personal computer and / or laptop computer), via communication link 146 (which may be a wired and / or wireless communication link).

[0048] Mobile device 150 can be implemented 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) for performing load control. Mobile device 150 can be a cellular phone (e.g., a smartphone), tablet computer, personal digital assistant, personal computer, laptop computer, wearable computing device (e.g., glasses, watch, wristband, etc.), or other mobile computing device.

[0049] Mobile device 150 may transmit beacon messages (e.g., mobile device beacon messages). Mobile device beacon messages may include, for example, a beacon message identifier. For instance, the beacon message identifier may be a unique identifier identifying mobile device 150 (e.g., or an application running on mobile device 150), and / or a non-unique identifier, such as the identifier of the manufacturer of the mobile device and / or control device of the group, region, building, load control system, and / or load control system 100. Mobile device beacon messages may also include a discovery threshold TH. RSSI The control device can receive mobile device beacon messages and can compare the received signal strength (such as Received Signal Strength Indicator (RSSI)) when a mobile device beacon message is received with the detection threshold TH. RSSI A comparison is made. If the signal strength when a mobile device beacon message is received is greater than or equal to the detection threshold TH, then... RSSI(For example, if the control device is within the detection range of the mobile device 150), the control device can enter a configuration mode. The control device can transmit a control device beacon message when entering the configuration mode. This occurs when the control device is receiving signals above the detection threshold TH. RSSI When receiving a mobile device beacon message, the control device may continue to transmit control device beacon messages (e.g., until the control device has completed control and / or configuration). If the control device stops receiving mobile device beacon messages, the control device may continue to transmit control device beacon messages for a given time period (e.g., 4 seconds), and may stop transmitting control device beacon messages after the end of the time period.

[0050] Mobile device 150 can discover control devices (e.g., control source devices and / or control target devices) upon receiving a control device beacon message transmitted from a control device. The control device beacon message can be a beacon message transmitted from a control device and includes a unique identifier that identifies the corresponding control device (e.g., control source device and / or control target device). For example, the control device beacon message may include a number corresponding to a corresponding load control device or another unique identifier. The unique identifier may be a unique network identifier (e.g., a route locator). The beacon message may include an address (e.g., a network address), a joiner identifier (e.g., a joiner ID), and / or any other type of device identification data. The control device beacon message may also, or alternatively, include a unique identifier corresponding to the device type of the control device. For example, the control device beacon message may include identifiers for lighting control devices, sensors (e.g., occupancy sensors, etc.), remote control devices, and / or other types of control devices.

[0051] Mobile device 150 can adjust the discovery threshold TH based on the number of control device beacon messages received by mobile device 150 from control device (e.g., the number of discovered control devices). RSSI Mobile device 150 can adjust the detection threshold TH. RSSIThis ensures that the number of control devices detected is within a target range (e.g., between 15 and 25 devices). The target range for detected control devices can have a low-side threshold and a high-side threshold, which define the number of control devices within the detection range. The target range for detected control devices can be predefined and / or defined by the user of mobile device 150. The target range for detected control devices can be modified based on, for example, the size of the load control system (e.g., the number of control devices in load control system 100 and / or the physical size of the area where 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 load control system 100 (e.g., lighting fixtures or sensors). Mobile device 150 can adjust the detection threshold TH emitted in the mobile device beacon. RSSI This is to attempt to control the number of control devices emitting control device beacon messages in a given area. For example, mobile device 150 can determine whether the number of detected control devices is within the target range and adjust the detection threshold TH. RSSI The number of control devices detected by the transmission control device beacon message can be adjusted by adjusting the detection range (e.g., the radius of the detection range).

[0052] If the number of detected control devices is within the target range, the mobile device 150 can maintain the detection threshold TH. RSSI If the number of detected control devices is less than the target range (e.g., less than 15 devices), the mobile device 150 can lower the detection threshold TH. RSSI (For example, increasing the radius of the detection range). If the number of detected control devices exceeds the target range (e.g., more than 25 devices), the mobile device 150 can increase the detection threshold TH. RSSI (For example, reducing the radius of the detection range). The mobile device 150 increases or decreases the detection threshold TH. RSSI The amount can depend on the number of control devices detected. For example, when the number of detected devices is closer to the target range (e.g., the number of detected control devices is between 26 and 40), the mobile device 150 can detect the threshold TH. RSSI The mobile device can increase the detection threshold by a smaller amount when the number of detected devices is further away from the target range (e.g., the number of detected control devices is greater than 40 devices).

[0053] When the mobile device 150 increases, the detection threshold TH is detected. RSSIAt that time, mobile device 150 may start an adjustment timer. If mobile device 150 again determines that the number of detected control devices is higher than the target range, mobile device 150 may determine whether the adjustment timer has expired. If the adjustment timer has expired, mobile device 150 may increase the detection threshold TH. RSSI And start the adjustment timer. If the adjustment timer has not yet expired, the mobile device 150 can maintain the detection threshold TH for the duration of the adjustment timer. RSSI Using an adjustment timer ensures that the mobile device accurately counts the number of detected control devices and prevents the mobile device from increasing the detection threshold TH. RSSI The threshold TH is adjusted too frequently. RSSI (For example, preventing mobile devices from overcalibrating the detection threshold TH) RSSI ).

[0054] Mobile device 150 can detect threshold TH RSSI Adjust (e.g., increase or decrease) a predefined amount. The predefined amount may depend on, for example, the difference between the number of detected control devices and the target range, and / or whether the detection threshold TH of the mobile device 150 is increased or decreased. RSSI (For example, whether the number of detected control devices is greater than or less than the target range). Increasing the detection threshold TH with mobile devices 150. RSSI Compared to the previous time, when the mobile device 150 decreases the detection threshold TH RSSI In this case, the predefined quantity can be larger. For example, the target range can be 15 to 25 devices. If the number of detected control devices is 10, then mobile device 150 can detect the threshold TH. RSSI This reduces the detection threshold by approximately 2 dBm, and if the number of detected control devices is 30, the mobile device 150 can detect the threshold TH. RSSI Increased by approximately 1 dBm.

[0055] To prevent the control device from fluctuating between identifying itself as being within and outside the detection range over a period of time, the control device can start a timer (e.g., a detection timer) after determining that the control device is within the detection range. The detection timer can define a detection period, which expires when the timer reaches a predefined value (e.g., when the detection period ends). The detection period can be a time interval (e.g., 2 seconds, 4 seconds, 8 seconds, etc.) during which the control device... RSSI The detection cycle begins when the received signal strength (e.g., RSSI) of the mobile device beacon message is reached, and allows the control device to maintain its state as a detected device during the detection period (e.g., by maintaining the state of the IN-RANGE flag). For example, when the control device receives a mobile device beacon message with a received signal strength (e.g., RSSI) less than the detection threshold TH...RSSI After receiving a mobile device beacon message with a received signal strength (e.g., RSSI) of the mobile device, the control device can determine whether the mobile device is within detection range during the detection period. If the control device has received a mobile device beacon message with a received signal strength greater than the detection threshold during the detection period, the control device can determine that the mobile device is within detection range during the detection period.

[0056] For example, the control device may receive a first discovery threshold TH including the first discovery threshold at the first time instance T1. RSSI1 The first mobile device beacon message. The control device can measure the received signal strength when it receives the first mobile device beacon message. If the received signal strength is greater than or equal to a first detection threshold TH RSSI1 If the control device determines that it is within detection range, it enters configuration mode and / or transmits a first control device beacon message. The control device can start a detection timer. The detection timer can run for one detection cycle (e.g., 2 seconds, 4 seconds, or 8 seconds). Whenever the control device receives a mobile device beacon message exceeding the detection threshold included in the mobile device beacon message, the control device can reset the detection timer. The control device can then receive a second detection threshold TH included in the second time instance T2. RSSI2 The second mobile device beacon message. First detection threshold TH RSSI1 Second detection threshold TH RSSI2 They can have the same value or different values. The control device can measure the received signal strength when it receives a second mobile device beacon message. If the received signal strength is less than the second detection threshold TH... RSSI2 If the detection period has not yet passed, the control device can determine whether the detection period has elapsed (e.g., whether the detection timer is running). If the detection period has not yet passed, the control device can remain in configuration mode and can transmit a second control device beacon message. If the detection period has passed, the control device can determine that it is out of detection range and can exit configuration mode.

[0057] The control device can be based on the detection threshold TH RSSI A lag is implemented for entering and exiting a discovery scope (e.g., configuration mode). For example, the discovery scope could be based on an entry discovery threshold TH for entering a discovery scope (e.g., entering configuration mode). 进入 (For example, the threshold TH was found) RSSI Add the first threshold offset TH 偏移1 And based on the exit discovery threshold TH for the exit discovery scope (e.g., exit configuration mode). 退出 (For example, the threshold TH was found) RSSI Subtract the second threshold offset TH 偏移2The mobile device 150 may include one or more threshold offsets in the beacon message. For example, the beacon message may include a first threshold offset TH. 偏移1 Second threshold offset TH 偏移2 Alternatively, the first threshold offset TH 偏移1 Second threshold offset TH 偏移2 It can be pre-stored in the memory of the control device. First threshold offset TH 偏移1 and / or second threshold offset TH 偏移2 They can have the same value, or the first threshold offset TH. 偏移1 and / or second threshold offset TH 偏移2 These can have different values. The control device can use a first threshold offset TH. 偏移1 and / or second threshold offset TH 偏移2 This determines whether to enter or exit configuration mode. For example, as described herein, the control device can receive beacon messages and determine the received signal strength (e.g., RSSI) when a beacon message is received. If the control device determines that the RSSI is greater than or equal to the entry discovery threshold TH... 进入 Then the control device can enter the configuration mode. The control device can offset the first threshold TH. 偏移1 Add to the detection threshold TH RSSI This may result in the entry into the detection threshold TH. 进入 (For example, an increased detection threshold). For instance, a beacon message could indicate a detection threshold of approximately -60 dBm. RSSI The value, and the first threshold offset TH 偏移1 It can be 5dBm. Therefore, if the control device receives a beacon message with an RSSI greater than or equal to -55dBm, the control device can enter configuration mode. Alternatively, the beacon message may include an entry into the discovery threshold TH. 进入 .

[0058] After the control device has entered the configuration mode, it can receive a second beacon message from the mobile device 150. The control device can then determine the beacon message based on the received signal strength (e.g., RSSI) at the time of receipt and the discovery threshold TH indicated in the second beacon message. RSSI The value and / or one or more threshold offsets (e.g., the first threshold offset TH) 偏移1 and / or second threshold offset TH 偏移2 This determines whether to exit configuration mode. For example, the control device can determine this from the detection threshold TH. RSSI Subtract the second threshold offset TH 偏移2 This can generate the exit discovery threshold TH 退出(For example, a reduced detection threshold). For instance, a beacon message could indicate a detection threshold of approximately -60 dBm TH. RSSI The value, and the second threshold offset TH 偏移2 It can be 5dBm. Therefore, if the control device receives the second beacon message with an RSSI greater than or equal to -65dBm, the control device can remain in configuration mode, and if the control device receives the second beacon message with an RSSI less than -65dBm, the control device exits configuration mode. Alternatively, the second beacon message may include an exit discovery threshold TH. 进入 .

[0059] In addition to using a threshold offset, the control device can use a discovery cycle when determining whether to exit configuration mode. For example... Figure 8A As shown, the control device can receive information including the detection threshold TH. RSSI The first value of the first mobile device beacon message. The first threshold can be offset by TH. 偏移1 Applied to the detection threshold TH RSSI The first value of TH makes it possible to enter the detection threshold TH. 进入 Greater than the received discovery threshold TH RSSI The control device can determine that it is above the entry detection threshold TH. 进入 The control device receives a first mobile device beacon message based on the received signal strength. The control device can then determine that the device is within detection range and can enter configuration mode. The control device can start a timer or record the amount of time that has elapsed since the control device received the first mobile device beacon message. The control device can later receive information including a detection threshold TH. RSSI The second value of the second mobile device beacon message. The second threshold can be offset by TH. 偏移2 Applied to the detection threshold TH RSSI The second value of makes the exit discovery threshold TH 退出 Less than the detection threshold TH RSSI The control device can determine that it is below the exit detection threshold TH. 退出 The received signal strength is determined by the second mobile device beacon message, which indicates that the control device is outside the detection range and should exit configuration mode. However, if the amount of time that has elapsed since the control device received the first mobile device beacon message is less than the detection period, the control device can remain in configuration mode.

[0060] Implementing a hysteresis (e.g., in addition to or as an alternative to the discovery cycle) can prevent control devices at the edge of the discovery range from rapidly entering and exiting configuration mode due to fluctuations in the received signal strength when receiving continuous beacon messages. Offset the first threshold TH 偏移1 Add to the detection threshold THRSSI (For example, to determine the entry detection threshold TH) 进入 This makes it less likely that a control device not currently in configuration mode will enter configuration mode. However, once a control device has entered configuration mode, the detection threshold TH... RSSI Subtract the second threshold offset TH 偏移2 (For example, to determine the exit discovery threshold TH) 退出 This makes it less likely that the control device will exit configuration mode due to relatively small fluctuations in signal strength when receiving beacon messages. Furthermore, as described herein, mobile device 150 can adjust the discovery threshold TH based on the number of control devices in configuration mode at a given time (e.g., the number of control devices from which mobile device 150 is receiving control device beacon messages). RSSI If the control device rapidly alternates between entering and exiting configuration modes, the mobile device 150 can detect the threshold TH. RSSI The value is adjusted a relatively large number of times. Therefore, using a threshold offset can reduce the impact on the detection threshold TH. RSSI The number of times the value is unnecessarily adjusted.

[0061] Control device beacon messages can be transmitted from control devices in the load control system 100 via RF communication signal 104. For example, control device beacon messages can be transmitted from lighting control device 114 of lighting fixture 110, load controller 121, controllable light source 132, occupancy sensor 134, remote control device 136, and / or another type of control device. Furthermore, control device beacon messages can be transmitted via RF signal 102. RF communication signals 102 and 104 can be wireless communication signals transmitted via wireless communication protocols (e.g., standard protocols such as ZigBee, Z-Wave, Bluetooth, Bluetooth Low Energy (BLE), Wi-Fi, or THREAD; proprietary communication protocols such as CLEAR CONNECT protocols (e.g., CLEAR CONNECT Type A and / or CLEAR CONNECT Type X protocols) and / or any suitable communication protocol). RF communication signals 102 and 104 can be different signal types (e.g., protocol, bandwidth, etc.). For example, RF communication signal 104 can be transmitted via a short-range wireless communication link using a short-range wireless communication protocol (e.g., Bluetooth and / or Bluetooth Low Energy (BLE) protocol). RF communication signal 102 can be communicated via a wireless network communication link using a wireless network communication protocol (e.g., CLEAR CONNECT and / or THREAD protocol) and / or any other suitable communication protocol that can be used for communication between control devices (e.g., between a control target device and a control source device). One of the RF communication signals (e.g., RF communication signal 102) can be used to control an electrical load during operation of the load control system 100, and one of the RF communication signals (e.g., RF communication signal 104) can be used to discover control devices and debug the load control system 100.

[0062] RF communication signals 102 and 104 can be transmitted via communication circuitry (e.g., a transceiver) in the respective control device or via a separate beacon transmitter. The beacon transmitter for the control device can be included in or near the control device to indicate the relative position of the respective control device by transmitting control device beacon messages. RF communication signal 102 can be transmitted via the same communication circuitry as RF communication signal 104 or via a different communication circuitry.

[0063] Network device 150 can emit optical signal 109 via optical transmitter 108. Optical transmitter 108 may be, for example, a laser pointer and may be detachable from network device 150. For example, the optical transmitter may be able to be inserted into a port on network device 150 (e.g., headphone jack, USB port, etc.). Load control devices for lighting fixtures (e.g., load control devices 114 of lighting fixture 110, load control devices 124a-124c of lighting fixtures 120a-120c, and / or the internal load control device of the controllable light source 132 of lighting fixture 130) can receive optical signal 109 from optical transmitter 108 (e.g., which may be attached to network device 150 or another device). For example, each lighting load may include one or more internal detectors configured to perform optical feedback on light emitted from the respective lighting load, and the load control device may be configured to receive optical signal 109 through the one or more internal detectors of the respective lighting load. Furthermore, the load control device for the lighting fixture (e.g., load control device 114 for lighting fixture 110) can be configured to receive the light signal 109 via a corresponding sensor (e.g., sensor 116). For example, sensor 116 may be able to detect different types of light signals in the space. The load control device for the lighting fixture can record a reference ambient light level in the area where the lighting fixture is located. The load control device for the lighting fixture may be able to detect the intensity of the light signal 109 received from network device 150 or another device capable of emitting the light signal 109.

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

[0065] The load control system 100 may include one or more beacon transmitters, which may be location beacon transmitters, such as beacon transmitter 180. Beacon transmitter 180 (e.g., a location beacon transmitter) may be located at workstation 182. The location beacon transmitter may transmit beacon messages (e.g., location beacon messages) via RF communication signals 102 and / or 104. Beacon messages transmitted by the location beacon transmitter may include beacon messages conveying a unique identifier. The beacon messages may be associated with the location where the location beacon transmitter is located, such as workstation 182, an office, a conference room, a portion of an office or conference room, or another location.

[0066] Beacon messages transmitted by a location beacon transmitter may include a unique identifier, which the mobile device 150 and / or system controller 140 may associate with the physical location where the location beacon transmitter is located. If multiple location beacon messages are detected, the user may associate the unique identifier of the beacon message with the strongest signal with the nearest physical location. The physical location may also be determined based on the geographic location of the mobile device 150.

[0067] Mobile device 150 can discover beacon messages transmitted by a location beacon transmitter for configuring and / or controlling one or more control devices in a load control system. For example, mobile device 150 can discover beacon messages transmitted by a location beacon transmitter and can associate a unique identifier of the beacon message with a unique identifier found in one or more control device beacon messages (e.g., beacon messages transmitted by control devices). When a location beacon transmitter is discovered by the mobile device, the control devices associated with the unique identifiers of the beacon messages transmitted by the location beacon transmitter can be co-controlled.

[0068] Beacon messages can be transmitted periodically or in response to a triggering event from the control device and / or the location beacon transmitter. The triggering event can be the receipt of a message. The triggering event can be sent in the message from the mobile device 150 or another device (e.g., occupancy sensor 134, remote control device 136, or another control source device). The system controller 140 can automatically control the transmission of beacon messages by transmitting messages based on periodic triggering events (e.g., timer expiration). In response to a message, the control device and / or the location beacon transmitter can enter a configuration mode and begin transmitting beacon messages. The message can trigger the transmission of beacon messages or the periodic transmission of beacon messages over a period of time.

[0069] The transmission of a beacon message can be triggered by a message transmitted on the same or different RF communication signals and / or protocols and / or channels. For example, the transmission of a beacon message can be triggered by an optical signal. For devices capable of performing bidirectional communication on RF communication signal 104, mobile device 150 can send a message to these devices on RF communication signal 104, the message causing these devices to transmit a beacon message on RF communication signal 102. Since the transmission of a beacon message can be performed as unidirectional communication from a control device, the transmission of a beacon message can be triggered by a message transmitted via another communication protocol and / or using another communication signal. For example, a control device can receive a message via RF communication signal 102, the message triggering the transmission of a beacon message from a control device in a load control system on RF communication signal 104.

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

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

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

[0073] Mobile device 150 can interpret information received in beacon messages and perform commissioning and / or control of load control system 100, or mobile device 150 can transmit information to another device to perform commissioning and / or control. For example, mobile device 150 can transmit information received in beacon messages and / or user input received on mobile device 150 to system controller 140 for configuration and / or control of load control system 100.

[0074] When commissioning the load control system 100, the mobile device 150 and / or system controller 140 can organize the received beacon messages into a list. The mobile device 150 and / or system controller 140 can sort the list based on a ranging method. For example, the 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 strongest RSSI can be listed first in the list.

[0075] Mobile device 150 can discover beacon messages and determine beacon message identifiers. Mobile device 150 and / or system controller 140 can be configured and / or controlled by selecting beacon message identifiers. Each of the discovered beacon messages can be selected for configuration and / or control, or beacon messages discovered above a discovery threshold can be selected for configuration and / or control. The discovery threshold can define a discovery range (e.g., an area around mobile device 150 and / or system controller 140 where control devices can be discovered). Mobile device 150 and / or system controller 140 can group and associate control devices identified by beacon messages to achieve load control in load control system 100. Mobile device 150 and / or system controller 140 can automatically add the identifier of the selected beacon message to the group of control devices to be associated to achieve load control.

[0076] One or more lighting fixtures can be configured and / or controlled using an optical signal (e.g., optical signal 109). The lighting fixtures (e.g., lighting fixtures 110, 120a-120c, and / or 130) can receive the optical signal 109 from an optical emitter 108 (e.g., which may be attached to a network device 150 or another device). For example, the lighting fixtures can be configured to receive the optical signal via an internal detector of the lighting load and / or via a corresponding sensor (e.g., sensor 116). The lighting fixtures can provide feedback to indicate that the lighting fixture has received the optical signal 109. For example, the lighting fixtures can cause the corresponding lighting load to emit light in a first color. The lighting fixtures can measure the corresponding signal strength when the optical signal 109 is received and can transmit a corresponding indication of the signal strength (e.g., as part of a beacon message). For example, the signal strength can be expressed as a normalized signal strength (e.g., relative to a corresponding reference ambient light level).

[0077] Network device 150 (e.g., or system controller 140) can select one or more lighting fixtures for configuration and / or control based on an indication of signal strength. For example, network device 150 can select a lighting fixture that receives light signal 109 with the highest signal strength for configuration and / or control. The selected lighting fixture can provide feedback indicating that it has been selected for configuration and / or control. For example, the lighting fixture can cause the corresponding lighting load to emit light in a second color. Once the configuration and / or control of the selected lighting fixture is complete, network device 150 can select another lighting fixture (e.g., a lighting fixture that receives light signal 109 with the second highest signal strength) for configuration and / or control. The lighting fixture that has been configured and / or controlled can provide feedback indicating that it has been configured and / or controlled. For example, the lighting fixture can cause the corresponding lighting load to emit light in a third color.

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

[0079] Preset configuration 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 these settings. Users can select preset configuration 192 on user interface 152 to set the intensity level of one or more lighting fixtures to be controlled according to the preset. Different presets can be configured to set different lighting levels for different occasions, such as a bedtime preset for when a user is going to bed, a movie preset for when a user is watching TV or a movie, an departure preset for when a user leaves the building, a home preset for when a user is in the building, or any other preset that the user can define for a particular occasion.

[0080] Users can select zone configuration 194 on user interface 152 to define one or more zones for lighting fixtures to be controlled. Control devices discovered and added to a group as described herein can each be included in a zone, such that the group identifier (e.g., a 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 the device group for configuration and / or control. Different zones can be controlled individually by sending lighting control commands to the zones to set them to different lighting levels. The associated device identifier of the identified lighting fixtures in a zone can be stored at mobile device 150 and / or system controller 140 as the defined zone configuration 194 for controlling the lighting fixtures in the defined zones. Zone configuration 194 can be sent in a message to system controller 140 and / or the lighting fixtures in the defined zones for storage to control the lighting fixtures according to zone configuration 194.

[0081] Users can select an occupancy configuration 196 on user interface 152 to define one or more lighting fixtures for control based on whether a space is occupied or vacant. In response to occupancy commands and / or vacancy commands received from occupancy sensors (such as occupancy sensor 134), different lighting fixtures can be controlled to different lighting levels.

[0082] Users can select a timer schedule configuration 198 on the user interface 152 to define a timer schedule for one or more lighting fixtures. Based on the timer schedule, which can be monitored by the system controller 140, different lighting fixtures can be controlled to different lighting levels (e.g., on / off, predefined intensity levels, etc.).

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

[0084] like Figure 2AAs shown, a control device (e.g., a lighting control device for lighting fixture 210a) can be selected for configuration and / or control, and can provide feedback to user 205 (e.g., installer) to identify the device that has been selected for configuration and / or control. A control device can be claimed and / or associated with a configuration identifier (e.g., a zone or group identifier for being added to a network) of configuration data used to implement load control in load control environment 201. The configuration identifier can be a fixture, group, zone, area, and / or location defined by configuration data (e.g., lighting control configuration information) that can be generated by design software. For example, feedback can be provided by the control device to indicate that the control device is ready to be claimed, has been selected for claim, and / or has been claimed. A control device can be claimed by selecting a configuration identifier to be associated with it. A control device being claimed can transmit a unique identifier (e.g., a number) to mobile device 250. By creating an association between the configuration identifier and the unique identifier of the control device, the control device can be associated with the configuration identifier. The mobile device can store the unique identifier and information about the association between the configuration identifier and the control device in the configuration data. After the control device is claimed, it can join the network and / or be configured and / or controlled by user 205. For example, user 205 can send one or more commands to the control device via a mobile device.

[0085] During the process of claiming a control device and / or associating the control device with a configuration identifier in configuration data, the control device can be configured to communicate with the mobile device 250 via a first wireless communication medium (e.g., via RF communication signal 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 signal 202 transmitted over a wireless communication network). After being claimed, the control device can be configured to join the wireless communication network. For example, the control device can join the wireless communication network by transmitting the association between the control device and the configuration identifier to a remote device. After joining the wireless communication network, the control devices can communicate with each other via the wireless communication network during normal operation.

[0086] Configuration data can define the operation and / or function of the load control system 200. The configuration data may include representations of control devices in the load control system 200 (e.g., lighting fixtures 210a-210d, occupancy sensor 234, remote control device 236, sensors 216a-216d, etc.), and configuration identifiers of the control devices (e.g., fixture, group, zone, area, and / or location). For example, the configuration data can define the function of the control devices, such as how lighting fixtures 210a-210d respond to occupancy sensor 234 and / or remote control device 236. For example, the configuration data can be configured using design software executed by a processing device (e.g., processing device 160) before claiming the control device and / or associating the control device with the corresponding configuration identifier of the control device in the configuration data. Furthermore, the configuration data can be configured, for example, by a mobile device 250, while the mobile device claims the control device and / or associates the control device with the configuration identifier of the control device in the configuration data. After the control device has joined a wireless communication network, the configuration data can be transmitted to the control device via the wireless communication network.

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

[0088] After entering configuration mode, mobile device 250 can transmit (e.g., periodically) beacon messages (e.g., mobile device beacon messages). Mobile device 250 can transmit mobile device beacon messages via a first wireless communication medium 204 (e.g., via a short-range wireless communication link using a short-range wireless communication protocol). Mobile device beacon messages can include, for example, a beacon message identifier. For example, the beacon message identifier can be a unique identifier identifying mobile device 250 (e.g., or an application running on mobile device 250), and / or a non-unique identifier, such as the identifier of the manufacturer of the mobile device and / or control device of a group, area, building, load control system, and / or load control system 200. Mobile device beacon messages can also include a discovery threshold. The control device can receive mobile device beacon messages and can compare the received signal strength indicator (RSSI) of the received mobile device beacon message with the discovery threshold. For example, the RSSI can be the signal strength at the time the mobile device beacon message is received. When a mobile device's beacon message identifier matches a specific beacon message identifier and / or received signal strength indicator greater than or equal to a detection threshold (e.g., the control device is within the detection range of mobile device 250), each control device can enter a configuration mode. For example, the specific beacon message identifier can be predetermined and / or stored in the control device's memory. Mobile device 250 can adjust the detection threshold included in the mobile device's beacon message to adjust the mobile device's detection range.

[0089] After entering configuration mode, the control devices (e.g., the lighting control devices of lighting fixtures 210a-210d) can each transmit (e.g., periodically) control device beacon messages. The control devices can transmit control device beacon messages via the first wireless communication medium 204. Each control device beacon message may include a unique identifier of the control device transmitting the corresponding beacon message. Furthermore, after entering configuration mode, the control devices can be ready to be claimed by the mobile device 250. After entering configuration mode (e.g., in response to receiving a mobile device beacon message), 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 claimed. 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 a mobile device beacon message) to indicate to the user that the control devices are within the detection range of the mobile device 250 and are ready to be claimed. In addition, feedback can be provided by causing the lighting load to flash, increasing and / or decreasing the intensity level of the lighting load, increasing and / or decreasing the color temperature of the lighting load, and / or providing other visual feedback to the user 205. The type of feedback can be indicated in a mobile device beacon message transmitted by the mobile device 250, and / or can be pre-programmed and stored at the control device (e.g., lighting fixtures 210a-210d).

[0090] As user 205 moves around the load control environment 201 with mobile device 250, the control devices within the mobile device's detection range may change. When control devices (e.g., lighting control devices of lighting fixtures 210a-210d) begin receiving mobile device beacon messages as the user moves around, these control devices can enter a configuration mode (e.g., ready to be claimed), begin transmitting their control device beacon messages, and provide feedback (e.g., change to the first color). Furthermore, when control devices fall outside the detection range and / or wireless range of mobile device 250 as the user moves around (e.g., stop receiving mobile device beacon messages), these control devices can exit the configuration mode after a timeout period (e.g., one minute). As a result, these control devices can stop transmitting their control device beacon messages and stop providing feedback (e.g., turn off).

[0091] Mobile device 250 can receive control device beacon messages from one or more control devices. For example, mobile device 250 can receive control device beacon messages from the lighting control device of lighting fixture 210a and select this lighting control device for claiming (e.g., for joining a network). Mobile device 250 can sort the received control device beacon messages based on the received signal strength indicator of the respective control device beacon message. For example, if the received signal strength indicator of the control device beacon message from the lighting control device of lighting fixture 210a is the maximum received signal strength indicator of the received control device beacon messages, then mobile device 250 can select the lighting control device for claiming.

[0092] Mobile device 250 can send a connection message to a control device that receives a control device beacon message with the maximum received signal strength. For example, 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 a connection message from mobile device 250. Furthermore, the connection message can indicate to the control device that the control device has been discovered and selected for claiming. For example, the connection message can be sent via RF communication signal 204 (e.g., directly from mobile device 250). For example, mobile device 250 can connect to a single control device at a time (e.g., select a single control device to be claimed at a time).

[0093] In response to receiving a connection message, the control device (e.g., lighting fixture 210a) can provide feedback to the user 205 to indicate that lighting fixture 210a has been selected for claiming. 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 second color (e.g., blue) after entering configuration mode (e.g., in response to receiving a mobile device beacon message) to indicate to the user that this control device has been selected for claiming. Figure 2A As shown, lighting fixture 210a can be illuminated in a second color, while other lighting fixtures 210b-210d can be illuminated in a first color. Furthermore, feedback can be provided by causing the lighting loads to flash, increasing and / or decreasing the intensity level of the lighting loads, increasing and / or decreasing the color temperature of the lighting loads, and / or providing other visual feedback to user 205. The type of feedback can be indicated in a connection message from mobile device 250, and / or can be pre-programmed and stored at the control device (e.g., lighting fixtures 210a-210d).

[0094] As user 205 moves around the load control environment 102 with mobile device 250, the received signal strength indicator of the received control device beacon messages received by the mobile device may change. As a result, the control device beacon message with the maximum received signal strength indicator of the received control device beacon message provides feedback (e.g., by changing to a second color). Mobile device 250 can be configured to disconnect from a previous control device (e.g., by sending a message to the previous control device), which can stop providing feedback (e.g., changing from the second color to the first color, since the control device may still be within the mobile device's detection range). Furthermore, mobile device 250 can send a connection message to a new control device with a received control device beacon message having the maximum received signal strength. Therefore, this control device can be selected for claiming and begins providing feedback (e.g., changing to the second color).

[0095] After entering the configuration mode, the mobile device 250 can emit (e.g., periodically emit) light signals (e.g., light signal 109). The mobile device 250 can emit light signals via an attached light emitter (not shown). The control device can receive the light signals via sensors (e.g., sensors 216a-216d) and / or the internal detectors of the lighting loads of the lighting fixtures 210a-210b, and can measure the signal strength of the received light signals. The control device can enter the configuration mode when each of the control devices receives a light signal, or the control device can enter the configuration mode before receiving a light signal.

[0096] Upon entering configuration mode, the control device (e.g., lighting fixtures 210a-210d) can provide feedback to user 205 to indicate that the control device is ready to be claimed. 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 a light signal) to indicate to the user that the control device has received a light signal and is ready to be claimed. Furthermore, feedback can be provided by causing the lighting load to flash, increasing and / or decreasing the intensity level of the lighting load, increasing and / or decreasing the color temperature of the lighting load, and / or providing other visual feedback to user 205. The feedback type can be pre-programmed and stored at the control device (e.g., lighting fixtures 210a-210d).

[0097] After entering the configuration mode, the control devices (e.g., the lighting control devices of lighting fixtures 210a-210d) can each transmit (e.g., periodically transmit) an indication of the signal strength when one or more of the light signals are received. The control devices can transmit the indications via the first wireless communication medium 204. Each indication may include a unique identifier of the control device that transmitted the light signal. Furthermore, after entering the configuration mode, the control devices can be ready to be claimed by the mobile device 250.

[0098] As user 205 moves around the load control environment 201 with mobile device 250, the control devices receiving light signals may change. One or more control devices not receiving light signals may be in a configuration mode. When control devices in configuration mode (e.g., lighting control devices of lighting fixtures 210a-210d) begin receiving light signals as the user moves around, these control devices may begin emitting their signal strength indicators and providing feedback (e.g., changing to a first color). Furthermore, when control devices stop receiving light signals as the user moves around, these control devices may stop emitting their signal strength indicators and stop providing feedback (e.g., turning off) after a timeout period (e.g., one minute).

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

[0100] Mobile device 250 can send a connection message to a selected control device. For example, mobile device 250 and control device can be configured to establish a connection (e.g., a bidirectional communication connection) in response to the control device receiving a connection message from mobile device 250. Furthermore, the connection message can indicate to the control device that the control device has been discovered and selected for claiming. For example, the connection message can be sent via RF communication signal 204 (e.g., directly from mobile device 250). For example, mobile device 250 can connect to a single control device at a time (e.g., select a single control device to be claimed at a time).

[0101] In response to receiving a connection message, the control device (e.g., lighting fixture 210a) can provide feedback to the user 205 to indicate that lighting fixture 210a has been selected for claiming. 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 second color (e.g., blue) after entering configuration mode (e.g., in response to receiving a connection message) to indicate to the user that this control device has been selected for claiming. Figure 2A As shown, lighting fixture 210a can be illuminated in a second color, while other lighting fixtures 210b-210d can be illuminated in a first color. Furthermore, feedback can be provided by causing the lighting load to flash, increasing and / or decreasing the intensity level of the lighting load, increasing and / or decreasing the color temperature of the lighting load, and / or providing other visual feedback to user 205. The type of feedback can be indicated in a connection message from mobile device 250, and / or can be pre-programmed and stored at the control device (e.g., lighting fixtures 210a-210d). Lighting fixtures that have been configured and / or controlled can provide feedback to indicate that they have been configured and / or controlled. For example, a lighting fixture can cause the corresponding lighting load to emit light in a third color.

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

[0103] In response to being claimed (e.g., in response to receiving a claim message), a control device (e.g., lighting fixture 210a) can provide feedback to user 205 to indicate that lighting fixture 210a has been claimed (e.g., for joining a network). 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 third color (e.g., green) after being claimed. Furthermore, feedback can be provided by causing the lighting load to flash, increasing and / or decreasing the intensity level of the lighting load, increasing and / or decreasing the color temperature of the lighting load, and / or providing other visual feedback to user 205. The type of feedback can be indicated in the claim message from mobile device 250, or it can be pre-programmed and stored at the control device (e.g., lighting fixtures 210a-210d).

[0104] In response to being claimed, the control device can exit the configuration mode and enter the join mode. In the join mode, the control device can stop continuously transmitting (e.g., periodically transmitting) control device beacon messages on the first wireless communication medium 204. For example, the control device can periodically switch between the first wireless communication medium 204 and the second wireless communication medium 204 (e.g., a wireless communication network). The control device can monitor the wireless communication network 202 to determine if a request to join the wireless communication network is being transmitted on the wireless communication network. If the mobile device 250 needs to reconnect to the control device while in configuration mode, the control device can continue to periodically transmit control device beacon messages via the first wireless communication medium (e.g., at a lower rate than in configuration mode). After the control device has joined the wireless communication network 202, configuration data can be transmitted to the control device via the wireless communication network.

[0105] Figure 2B This is an illustration of an example network 260 that allows communication between devices in a load control system (e.g., load control system 100 and / or load control system 200). Network 260 can include any suitable network to facilitate communication in a load control system or Internet of Things (IoT) environment. Various control devices of load control system 200 can communicate with each other via network 260. Figure 2B As shown, network 260 may include a single network partition. Furthermore, network 260 may be an example of a network partition (e.g., a subnet or subnetwork) within a larger network. For example, network 260 may be an example of a network partition within a larger network consisting of multiple network partitions. Network 260 is an example network, and the techniques described herein can be applied to other networks, for example, that include more or fewer devices than network 260.

[0106] Figure 2BThe circular nodes can represent devices that are joined to network 260 and attached to other devices (e.g., various control devices of load control system 100 and / or load control system 200). A device attached to at least one other device on network 260 can communicate with other devices (e.g., other devices attached to another device on network 260). Communication within network 260 can be facilitated by links (e.g., attachments) established within network 260. (See reference...) Figure 2B Links between devices can be indicated by lines (e.g., solid and dashed lines) connecting the respective devices.

[0107] Figure 2B One or more of the devices shown can join network 260 via a joining procedure. Network 260 may be a mesh network, and each device can exchange network credentials with a debugging device (e.g., a system controller or mobile device). These network credentials allow the device to join network 260 and enable it to communicate on network 260. The device may be able to communicate with other devices using a different wireless protocol, but without network credentials, it may be unable to communicate with or attach to other devices on network 260. Network credentials may include a joiner identifier (e.g., or any other identifier), which the device can use to join network 260 and communicate with another device.

[0108] Devices can be claimed (e.g., via a claiming procedure) before being added to network 260. For example, a claiming procedure can be used to identify devices (e.g., individual devices and / or groups of devices) for addition to network 260. As part of the claiming procedure, a device can exchange credentials with a testing device to enable the device to communicate on network 260. Without such credential exchange, a device may not be able to obtain a joiner ID and may not be able to communicate on network 260.

[0109] A device attached to at least one other device on network 260 may assume and / or be assigned a corresponding role in the network. For example, these roles may 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). The role of a device may indicate the functionality and / or capabilities of the device relative to network 260.

[0110] like Figure 2BAs shown, network 260 may include a leader device 262. Leader device 262 can manage other devices attached to network 260. For example, leader device 262 can assign and maintain router identifiers (e.g., router IDs) for each of router devices 264a-264d. For example, each of router devices 264a-264d can be assigned a unique router identifier. Leader device 262 can assign and maintain the roles of other devices. Leader device 262 can be configured as a gateway for network 260. For example, the leader device can be a means of facilitating communication between network 260 and other networks or network segments (e.g., routing messages to and receiving messages from networks). Reference Figure 2A System controller (e.g., Figure 2A The system controller 240 shown can be an example of a leader device 262. Furthermore, devices in a load control system that can be assigned the role of a router device can be assigned the role of a leader device (e.g., a control device).

[0111] Network 260 may include one or more router devices 264a-264d. Leader device 262 may support and be attached to multiple router devices (e.g., more than 30 router devices). Leader device 262 may operate as a router device. Router devices 264a-264d on network 200 (e.g., leader device 262 attached to network 260) may communicate with each other, for example, to form a mesh network. Router devices 264a-264d may communicate with each other (e.g., as indicated by the solid lines connecting router devices 264a-264d). Router devices 264a-264d may communicate with leader device 262 directly or through one or more other router devices (e.g., as indicated by the solid lines connecting leader device 262 to router devices 264a and 264c). Router devices 264a-264d may receive messages and route said messages to other devices on network 260 (e.g., terminal devices 266a, 266b). For example, router devices 264a-264d can receive / transmit messages between or with each other for transmitting messages received from an attached device to another device attached to another router device. Now refer to... Figure 2A The load control system 200 shown, such as a device powered externally by the AC trunk (e.g., not a 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 a router device.

[0112] Network 260 may include one or more terminal devices 266a, 266b (e.g., a maximum or minimum number of terminal devices). Each terminal device 266a, 266b may be attached to another device on network 200 (e.g., a parent device) and may transmit and / or receive messages through attached router devices 264a-264d. For example, terminal devices 266a, 266b may each identify data to one or more of the router devices 264a-264d via a transmit address (e.g., a network address), a joiner identifier (e.g., for network authentication), and / or other types of device identifiers. Although in Figure 2B The diagram shows two terminal devices 266a and 262b, each attached to a different router device, but each router device 264a-264d can support multiple terminal devices (e.g., more than 500 terminal devices). Reference Figure 2A The load control system 200, system controller 240, input devices (e.g., remote control device 232 and / or occupancy sensor 230), and / or load control devices (e.g., lighting control devices for lighting fixtures 210a-210d) may be Figure 2B Examples of terminal devices 266a and 266b shown.

[0113] For example, based on changes in network 260, leader device 262 can update the roles of devices communicating within network 260 (e.g., or confirm role updates). In one example, when a device is attached to network 260, this device can be assigned a specific role, and leader device 262 can update this device's role based on changes in network conditions. Changes in network conditions may include: increased messaging traffic, the attachment of other devices, changes in signal strength, etc. Updates to the assigned roles of devices can be based on the device's capabilities. Leader device 262 can update the role of this device to a router device by assigning a router identifier (ID) to the device.

[0114] Devices attached to network 260 can also operate as parent and child devices. A leader device (e.g., leader device 262) and router devices (e.g., router devices 264a-264d) attached to one or more terminal devices (e.g., terminal devices 266a, 266b) can operate as parent devices. Terminal devices (e.g., terminal devices 266a, 266b) attached to the leader device (e.g., leader device 262) and / or router devices (e.g., one of router devices 264a-264d) can operate as child devices. As parent devices, leader device 262 and router devices 264a-264d can each be attached to one or more child devices (e.g., one or more of terminal devices 266a, 266b, as described herein). Furthermore, leader device 262 and router devices 264a-264d can store and / or relay messages sent by their respective attached child devices. For example, leader device 262 and router device 264 can receive messages from their respective sub-devices and route the received messages to the intended recipient device (e.g., directly or through the corresponding parent device of the intended recipient device). Similarly, leader device 262 and router devices 264a-264d can receive messages intended for their respective sub-devices and route the messages to the appropriate sub-devices.

[0115] like Figure 2B As shown, the relationship between a sub-device and its corresponding parent device (e.g., attachment) can be represented by dashed lines. Router device 264a can receive messages intended for terminal device 266a and forward the messages to terminal device 266a. Since router device 264a is configured as the parent device of terminal device 266a, terminal device 266a can send messages to router device 264a, and router device 264a can route the messages to the intended recipient. For example, when terminal device 266a intends to send a message to terminal device 266b, terminal device 266a can initially send the message to router device 264a. Router device 264a can route the message to router device 264b (e.g., the parent device of terminal device 266b), and then router device 264b can forward the message to terminal device 266b.

[0116] In network 260, router devices (e.g., leader device 262 and router devices 264a-264d) can periodically transmit announcement messages indicating the presence of router devices on the network. These announcement messages can be used to calculate the cost and / or quality of communication in network 260. Each router device can receive the announcement message, which includes an identifier of the router device transmitting the announcement message, and measure the Received Signal Strength Indicator (RSSI) of the received announcement message. The RSSI can be used to calculate the link quality (e.g., Link Quality Indicator (LQI)) at the time the announcement message was received. Each router device (e.g., leader device 262 and router devices 264a-264d) can send the announcement message as a multicast message. The announcement messages transmitted by the router devices can be received by adjacent router devices that share a single-hop communication link with the router device that transmitted the announcement message. The single-hop communication link may enable the direct transmission of messages (e.g., digital messages) from one router device to another via unicast and / or multicast communication. For example, router devices 264a and 264c can be adjacent devices sharing a single-hop communication link with leader device 262, because router devices 264a and 264c can directly send digital messages to and / or directly receive digital messages from leader device 262. A single-hop communication link can be a communication link on which router devices can directly receive announcement messages with a quality higher than a given link quality (e.g., LQI greater than 0).

[0117] After a router device receives a periodic advertisement message from another router device, the router device can calculate the link quality (e.g., LQI) of the communication link through which the advertisement message was received. The LQI can be calculated as a predefined number within a range indicating different link qualities of the communication link between the two devices. For example, the LQI can be indicated by values ​​0, 1, 2, or 3. Different indicators of the LQI can be assigned based on the RSSI of the received advertisement message and the link margin relative to a predefined reception level.

[0118] The child device can receive advertisement messages from its parent router device or a router device other than the child device's parent device (e.g., an auxiliary parent device or a router device other than the child device's auxiliary parent device). For example, a router device can transmit advertisement messages to enable other control devices to determine that a network has been formed and that a device that hears the advertisement message can attempt to attach to the router (e.g., communicate over the network). Devices can receive and track advertisement messages transmitted by routers to determine whether they are able to communicate over the network. Furthermore, or alternatively, advertisement messages transmitted by the respective routers can provide other routers with the ability to measure communication signals (e.g., RSSI) between the respective routers attached to the network (e.g., routers can use this communication signal to update their respective routing tables or routing information). As described herein, the child device can measure the Received Signal Strength Indicator (RSSI) of the received advertisement messages.

[0119] The sub-device may create and maintain an auxiliary parent table. The auxiliary parent table may include a list of auxiliary parents to which the corresponding sub-device is configured to communicate (e.g., synchronize with multicast messages and / or receive multicast messages). Furthermore, the auxiliary parent table may include an indication (e.g., RSSI) of the received signal strength of each auxiliary parent device of the sub-device. For example, the auxiliary parent table may include a rolling average of the received signal strength indicators of each auxiliary parent device of the sub-device. The sub-device may similarly create and / or maintain a router table. The router table may include routers from which the corresponding sub-device has received messages (e.g., advertisement messages). Furthermore, the router table may include an indication of the RSSI of messages received from each router in the router table. Alternatively, the sub-device may maintain a general router table. The router table may include each router from which the corresponding sub-device has received advertisement messages, and the received signal strength indicator of each corresponding router. The router table may also include an indication of whether a corresponding router is a parent device or an auxiliary parent device of the sub-device. As used herein, the term auxiliary parent table can refer to a table separate from the router table or a subset of routers in the router table that serve as synchronous auxiliary parent devices for child devices.

[0120] Each router device can send / broadcast an advertisement message including path costs to one or more other router devices in network 260. A router device that receives path cost information from a router device that sent the advertisement message can update the corresponding path cost information in its local router table (e.g., by adding the link cost it uses to communicate with the router device that sent the advertisement message to the path cost in the received message). Each router device can use its locally stored path cost information to identify paths through which it can transmit digital messages. Each router device can update its corresponding locally stored router table with the calculated lowest path cost to communicate with other router devices in network 260.

[0121] By periodically updating link quality (e.g., LQI and / or LQO), link cost, and / or path cost, and by transmitting path cost information to other router devices in periodic announcement messages, each router device can have up-to-date path cost information for transmitting digital messages to other router devices in network 260. A router device can use the optimal communication path (e.g., the lowest-cost path) to transmit digital messages to another device. This routing mechanism allows router devices to detect when other router devices have left network 260, or when the path cost between routers has changed, and to calculate the next lowest-cost path to maintain connectivity with other router devices in network 260.

[0122] As described in this article, Network 260 can allow load control systems (e.g., Figure 2A The devices in the load control system 200 shown communicate with each other. Terminal devices 266a and 266b may 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 may communicate with another terminal device in the load control system via RF communication.

[0123] refer to Figure 2B The remote control device 232 can operate as a terminal device to transmit digital messages, including indications of user input and / or control commands for controlling another terminal device (e.g., the lighting control device for lighting fixtures 210a-210d). The remote control device 232 can communicate via one or more intermediate parent devices (e.g., leader devices and / or router devices). The leader devices and / or router devices can communicate with one or more other leader devices and / or router devices in the network to route messages to other terminal devices (e.g., the lighting control devices for lighting fixtures 210a-210d) for load control.

[0124] The control device beacon message described herein as being transmitted from a control device can be an announcement message indicating the presence of a control device on the network. The control device beacon message may include a unique identifier of the control device (e.g., a network identifier) ​​transmitted in the announcement message and / or network information, such as link quality or link cost for communication between devices in the network. Other devices (e.g., other control devices, mobile devices, system controllers, etc.) may receive and track announcement messages transmitted by the control device in the control device beacon to determine the presence of a control device on the network and / or whether the control device is capable of communicating over the network.

[0125] Figure 3 This is a system diagram that illustrates an example control system 300 (e.g., Figure 1 The load control system 100 shown in Figure 1 and / or the load control system 200 shown in Figure 2 are illustrated. Figure 3 As shown, the control system 300 may include load control devices for commissioning, such as lighting control devices 310 (e.g., lighting control devices 114 for lighting fixture 110, lighting control devices 124a-124c for lighting fixtures 120a-120c, controllable light sources 122 for lighting fixtures, and / or lighting control devices for lighting fixtures 210a-210d, 220a-220d). The lighting control device 310 can be commissioned by configuring it for lighting control. The lighting control device 310 can be configured for lighting control by being claimed in the configuration data of the control system 300, assigned to different luminaires, groups, zones, and / or locations, and / or added to a communication link 312 (such as a wireless communication network). The lighting control device 310 can be configured by defining preset scenes or other lighting control parameters, through which the lighting control device 310 can be controlled.

[0126] 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 device 310 via a communication link 312 to perform lighting control during operation based on lighting control configuration information previously stored thereon (e.g., on the system controller 340). The lighting control configuration information may include preset configurations, zone configurations, occupancy configurations, and / or timing schedule configurations for controlling the lighting control device 310.

[0127] Lighting control configuration information can be generated by a network device, such as a processing device 360 ​​(e.g., a personal computer or laptop computer). The processing device 360 ​​can be a network device on which design software can be executed to configure (e.g., claim, diagnose, associate, etc.) and / or design a load control system within a load control environment. The processing device 360 ​​can generate a control database including lighting control configuration information (e.g., load control parameters) based on the floor plan and design of the lighting control system. The processing device 360 ​​can generate project code identifiers for identifying items within which the floor plan and / or the control database for controlling devices in the floor plan are stored. The lighting control configuration information in the control database can be stored at the lighting fixture 310 or the system controller 340 for implementing lighting control based on said information. The processing device 360 ​​can communicate with the system controller 340 via a communication link 342. The communication link 342 can be a wired or wireless communication link, such as, for example, an Ethernet link and / or a local area network HTTPS communication link.

[0128] System controller 340 can send lighting control configuration information to lighting control device 310 and / or control lighting control device 310 according to the lighting control configuration information. System controller 340 can communicate with lighting control device 310 via communication link 312 (e.g., wireless communication network). Communication link 312 may include RF communication signals transmitted via one or more protocols (e.g., standard network communication protocols, proprietary communication protocols, and / or any suitable communication protocols as described above). Communication link 312 may also include a wired network communication link.

[0129] After generating lighting control configuration information at processing device 360, processing device 360 ​​can share the lighting control configuration information with other devices for updating and / or assisting in the debugging of control system 300. For example, processing device 360 ​​can store the lighting control configuration information on a remote data source such as cloud server 370 for access by other devices. Processing device 360 ​​can communicate with cloud server 370 via communication link 372. Communication link 372 can achieve communication via wired and / or wireless signals. The lighting control configuration information can be stored together with a project identifier at processing device 360 ​​and / or cloud server 370 for differentiation from other projects.

[0130] The control system 300 may include a network device, such as a mobile device 350 (e.g., a smartphone or tablet computer), which may be implemented to claim (e.g., discover) control devices (e.g., lighting control device 310) used for commissioning the control system 300. The mobile device 350 may allow a user to access a control database within the control system 300 for a project and discover the lighting control device 310 configured for said project. The lighting control device 310 may be discovered by the mobile device 350 via a wireless communication link 352 (e.g., a short-range wireless communication link). The wireless communication link 352 may allow the transmission of beacon messages or other short-range RF communications. The wireless communication link 352 may include RF signals transmitted using a short-range communication protocol (e.g., BLE).

[0131] Mobile device 350 can access lighting control configuration information from the control database from cloud server 370 and / or from processing device 360. Mobile device 350 can communicate with cloud server 370 via communication link 372. Mobile device 350 can communicate with processing device 360 ​​via wireless communication link 352. Mobile device 350 can also or alternatively access lighting control configuration information from the control database via a direct wired connection (such as a Universal Serial Bus (USB) cable) and / or computer-readable media (such as a USB drive or other external storage).

[0132] Mobile device 350 can run an application locally to aid in debugging control system 300. Users can select buttons on the application to synchronize lighting control configuration information within the application with lighting control configuration information stored for projects on cloud server 370. Users of mobile device 350 can access area and zone information within the lighting control configuration information for assigning discovered lighting control devices 310.

[0133] When a lighting control device 310 is assigned to a luminaire, group, zone, and / or location at a mobile device 350, lighting control configuration information can be updated and sent to a cloud server 370. For example, a lighting control device identifier and / or beacon message identifier for each lighting control device 310 can be stored along with an associated area, zone, and / or location within the zone for appropriate control. The lighting control configuration information can then be accessed by a processing device 360 ​​and sent to a system controller 340 and / or the lighting control device 310 for implementing lighting control based on the updated assignment.

[0134] Figure 4This is a flowchart depicting an example program 400 (e.g., a debugging program) for debugging a control system such as a load control system (e.g., load control system 100). Program 400 can be implemented by one or more devices. For example, program 400 can be implemented by a system controller (e.g., system controllers 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). Program 400 can begin at 402.

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

[0136] At 406, configuration data (e.g., all or part of a 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 configuration data to the mobile device via a cloud server. When the configuration data is ready to be transferred (e.g., when the control device of the control system is ready to be claimed and / or associated with a configuration identifier (e.g., a zone or group identifier for joining a network) of the configuration data), the processing device can transfer the configuration data to the cloud server via the Internet (e.g., via communication link 372 using IP and / or HTTP communication). The processing device can display an item code (e.g., a unique code for an item in a load control system being debugged). For example, the item code may include an alphanumeric sequence. The user can enter the item code into a configuration application running on the mobile device. The mobile device can transmit the item code to the cloud server, which can then transmit the configuration data to the mobile device. Furthermore, the processing device can display machine-readable codes, such as barcodes and / or quick response (QR) codes, and the mobile device can scan the machine-readable codes to identify the item code. When the processing device and / or mobile device do not have internet access, at 406, configuration data can be transferred from the processing device to the mobile device (e.g., direct transmission) via a direct wired connection (such as a Universal Serial Bus (USB) cable) and / or a computer-readable medium (such as a USB drive or other external storage). Alternatively, configuration data can be transferred from the processing device to the mobile device (e.g., direct transmission) via a short-range wireless communication link (e.g., via communication link 352).

[0137] At 408, a control device of the load control system can be claimed and / or associated with a configuration identifier in the configuration data (e.g., a luminaire, group, zone, area, and / or location that can be defined by the configuration data). For example, at 408, as part of a configuration procedure (e.g., a claim procedure and / or an association procedure), a mobile device can claim a control device and / or associate the control device with a configuration identifier in the configuration data. For example, a mobile device can begin transmitting (e.g., periodically transmitting) mobile device beacon messages via a short-range wireless communication link (e.g., via communication link 352). A control device receiving a mobile device beacon message and located within the mobile device's detection range can be configured to transmit a corresponding control device beacon message. A mobile device can receive control device beacon messages from multiple control devices and can select a control device from which it receives control device beacon messages (e.g., the control device from which it receives a control device beacon message with the strongest received signal strength indicator) to claim. An installer can select a configuration identifier from the mobile device to associate with the current control device to initiate the claim of the control device. The installer can move a mobile device around the building where the load control system is installed to claim and associate each control device. When each control device is claimed, the claiming control device can send a unique identifier (e.g., a number) to the mobile device, and the mobile device can store the unique identifier and information about the association between the configuration identifier and the control device in the configuration data. The configuration process can end when the installer has completed the claiming of control devices (e.g., the mobile device has claimed all or part of the control devices in the load control system).

[0138] Before being claimed at point 408, the control device can (e.g., continuously) listen for mobile device beacon messages on a short-range wireless communication link (e.g., communication link 352). After being claimed at point 408, the control device can enter join mode. In join mode, the control device can periodically switch between listening for mobile device beacon messages and listening for requests to join the wireless communication network (e.g., communication link 312). Switching between listening for mobile device beacon messages and listening for requests to join the wireless communication network allows the control device to be ready to join the wireless communication network while still allowing the mobile device to connect to one or more of the control devices (e.g., to correct errors made when claiming the control device, or to revoke the claim to the control device).

[0139] At 410, configuration data (e.g., updated during the configuration process as described at 408) can be transmitted from the mobile device to the system controller. For example, the configuration data can be transmitted from the mobile device to the system controller via a processing device. For example, the mobile device can be configured to transmit the configuration data to the processing device via a cloud server, via a direct wired connection, and / or via a short-range wireless communication link (e.g., as described above at 406). The processing device can then (e.g., via communication link 342) transmit the configuration data (e.g., all or part of a configuration database) to the system controller or another debugging device. The debugging device can be a device on a wireless communication network used to add other devices to the network. For example, the debugging device can 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 a cloud server (e.g., not transmit configuration data to the processing device). Additionally, the mobile device can be configured to transmit (e.g., directly transmit) configuration data to the system controller via a direct wired connection and / or via a short-range wireless communication link.

[0140] Configuration data may include device identification data received from a control device, such as a lighting fixture. A system controller or other commissioning device may receive device identification data from multiple devices. For example, multiple devices may have participated in a claiming process executed at 408. For each device participating in the claiming process, the network device may transmit device identification data to the system controller or other commissioning device. Device identification data for each device may be transmitted individually (e.g., not simultaneously). The system controller or other commissioning device may indicate to the user (e.g., via an application running on a separate computing device) how many devices have been claimed to be added to the network and / or how many devices need to be claimed to be added to the network. For example, the network device may display a list of each control device in the area (e.g., in text or graphical form). Once the system controller or other commissioning device has received device identification data for a particular lighting fixture, the color of that lighting fixture may be changed. The system controller or other commissioning device may aggregate the device identification data received from the devices and may generate a single list of lighting fixtures.

[0141] The system controller or other debugging device can operate in offline mode (e.g., the debugging device may be disconnected from the Internet or otherwise unable to access specific online services used during debugging). The network device can transmit device identification data to the system controller or other debugging device via, for example, RF signals, USB transmission, etc. (e.g., direct transmission to the debugging device). Alternatively, the network device can transmit device identification data to the system controller or other debugging 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 via a cable with USB connectors at both ends. The network device can transmit device identification data to the processing device via a physical connection. The network device can be physically connected to the system controller or other debugging device via a wired digital communication link (e.g., via an Ethernet link). The processing device can transmit device identification data to the system controller or other debugging device via a wired digital communication link. The network device can transmit device identification data by transferring (e.g., copying) the device identification data to an external drive (e.g., removable memory). The external drive can be connected to the processing device, and the processing device can transfer (e.g., copy) the device identification data from the external drive to local memory. The processing device can store the device identification data in memory. The processing device can then transmit the device identification data to the debugging device via a wired digital communication link. The debugging device can also store the device identification data in its memory.

[0142] At 412, the control device claimed at 408 can be added to the wireless communication network (e.g., communication link 312). The system controller can operate as a debugging device for adding the control device to the wireless communication network. After the control device is added to the wireless communication network, the control devices can communicate with each other via the wireless communication network during normal operation. Furthermore, the control device can stop monitoring the network on which mobile device beacon messages are received and can communicate on the wireless communication network (e.g., exclusively). At 414, configuration data can be transmitted to the control device. For example, the system controller can transmit the portion of the configuration database related to the corresponding control device to this control device.

[0143] Figure 5 This is a system flowchart that depicts an example message flow for discovering control devices in a load control system. For example, control devices can be discovered to enable configuration (e.g., claiming, diagnosing, associating, etc.) and / or control of them. Figure 5 The system flowchart shown can be used to depict the execution Figure 4 The RF messages transmitted between control devices in the program 400 shown. For example... Figure 5As shown, a network device (e.g., a mobile device) can communicate directly with one or more control devices (e.g., a lighting control device). For example, the network device and the control device are connected wirelessly. Alternatively, the network device can communicate with the control device through a system controller. For example, the network device can communicate with the system controller wirelessly, while the system controller can communicate with the control device via a wired connection. Although Figure 5 The lighting control device is shown, but other control devices may also be used.

[0144] For example, control devices can be discovered to enable configuration (e.g., claiming, diagnosing, associating, etc.) and / or control of the control devices. Figure 5 As shown, the load control system may include a moving device 502 and lighting fixtures 504a and 504b. Lighting fixtures 504a and 504b may include corresponding load control devices configured to control corresponding lighting loads. The lighting control devices in lighting fixtures 504a and 504b may be RF-enabled devices, including communication circuitry capable of transmitting messages via RF signals. Sensors 505a and 505b may be occupancy sensors, visible light sensors (e.g., cameras), daylight sensors, optical sensors, and / or any other type of sensor.

[0145] like Figure 5 As shown, mobile device 502 can transmit configuration mode message 506 to lighting fixtures 504a and 504b. Configuration mode message 506 can instruct the lighting control devices of lighting fixtures 504a and 504b to enter a configuration mode (e.g., claim mode and / or association mode). Configuration mode message 506 can be transmitted via RF communication signals (e.g., using a short-range wireless communication protocol) and / or optical signals. Configuration mode message 506 can be sent as a multicast message (e.g., a beacon message) received by the lighting control devices of lighting fixtures 504a and 504b. Lighting fixtures 504a and 504b can enter configuration mode without receiving configuration mode message 506.

[0146] After transmitting the configuration mode message 506, the mobile device 502 can perform the discovery of lighting control devices in lighting fixtures 504a and 504b. The lighting control devices in lighting fixtures 504a and 504b can be discovered by the mobile device sending a discovery request message 508. The discovery request message 508 can be transmitted to identify lighting control devices selected to claim and join the network. The discovery request message 508 may include a discovery threshold, and the lighting control devices of lighting fixtures 504a and 504b can determine whether they are within the discovery range of the mobile device 502 by determining whether the Received Signal Strength Indicator (RSSI) of the received discovery request message 508 is greater than or equal to the discovery threshold (e.g., the discovery threshold included in the received discovery request message 508).

[0147] The discovery request message 508 may be transmitted in an RF signal, such as an RF beacon message transmitted from the mobile device 502. Lighting control devices 504a and / or 504b may provide a first type of feedback indicating that the lighting control device has received and / or the discovery request message 508. Feedback may be provided by causing the lighting load to flash, 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 providing other visual feedback to the user.

[0148] 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 corresponding beacon messages for discovery at mobile device 502 (e.g., in response to entering a configuration mode). Mobile device 502 can determine the signal strength when different discovery response messages 510a and 510b are received to identify the lighting control device associated with the strongest beacon message.

[0149] Based on discovery response messages 510a and 510b, mobile device 502 can determine which of the lighting control devices in lighting fixtures 504a and 504b is selected to be claimed for joining the network. The discovery response message 510a or 510b associated with the strongest signal strength can be selected for claiming for joining the network.

[0150] like Figure 5As shown, mobile device 502 can determine that the lighting control device of lighting fixture 504a is receiving a discovery request message 508 with the highest signal strength, or that mobile device 502 is receiving a beacon message signal from the lighting control device of lighting fixture 504a with the highest signal strength. Mobile device 502 can select lighting control device 504a for configuration (e.g., claim and / or associate). 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 exchanging credentials between mobile device 502 and the lighting control device of lighting fixture 504a to create a secure connection for secure communication. Connection message 512 can indicate to the lighting control device of lighting fixture 504a that the lighting control device has been selected for configuration (e.g., claim and / or associate). Alternatively, mobile device can communicate with lighting fixture 504a without establishing a connection.

[0151] 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 a second type of feedback in response to the establishment of a connection 512 between the lighting control device 504a and the mobile device 502. Feedback can be provided by causing the lighting load to flash, 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 providing other visual feedback to the user.

[0152] After establishing a connection 512 with the lighting control device of lighting fixture 504a, mobile device 502 can associate the lighting fixture with configuration data. The mobile device can receive confirmation that the lighting control device of lighting fixture 504a has received the 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 a configuration message 516 to lighting fixture 504a. Configuration message 516 can indicate that lighting fixture 504a has been claimed and / or associated with the selected configuration identifier. Configuration message 516 may include, for example, an indication that lighting control device 504a has been claimed, a unique identifier of 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 process (e.g., a claiming process, an association process, a diagnostic process, etc.). Control messages, including control commands for controlling lighting fixtures, can also be sent at point 516. Mobile device 502 can receive 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. Connection message 512, configuration message 516, and / or acknowledgment message 518 can be transmitted and / or received via RF communication signals.

[0153] The lighting control device 504a can provide a third type of feedback indicating that the lighting control device has received the configuration message 516. Feedback can be provided by causing the lighting load to flash, 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 providing other visual feedback to the user.

[0154] Figure 6 This is a flowchart depicting an example procedure 600 for discovering a control device to achieve claiming and / or associating with the control device. Procedure 600 may be executed as part of a configuration procedure (e.g., a claiming procedure and / or an association procedure). Procedure 600 may be implemented by one or more devices. For example, procedure 600 may be executed by a mobile device (e.g., mobile devices 150, 250, 350) to claim the control device and / or associate the control device with a configuration identifier of configuration data of a load control system (e.g., as executed at 408 of procedure 400). For example, procedure 600 may be executed at 602 in response to a button (e.g., a virtual button or a soft button) on a user interface (e.g., user interface 500) that actuates the mobile device.

[0155] At 604, the mobile device may enter a configuration mode (e.g., claim mode and / or association mode). At 606, the mobile device may begin periodically transmitting beacon messages (e.g., mobile device beacon messages). The mobile device may be configured to transmit mobile device beacon messages via a short-range wireless communication link. The mobile device beacon message may include, for example, a discovery threshold and / or a unique identifier that identifies the mobile device (e.g., or an application running on the mobile device). When one of the control devices receives a 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., the control device is within the detection range of the mobile device), the control device may enter a configuration mode (e.g., claim mode and / or association mode) and begin transmitting (e.g., periodically transmitting) beacon messages (e.g., control device beacon messages). The mobile device may adjust the discovery threshold included in the mobile device beacon message to adjust the detection range of the mobile device.

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

[0157] When the mobile device successfully establishes a connection with the control device at 614, at 616, the mobile device can determine whether it has received an instruction from the user via the mobile device's user interface (e.g., user interface 500) to associate the control device with one of the configuration identifiers in the configuration data. For example, the mobile device can receive a selection of a configuration identifier (e.g., a luminaire, group, zone, area, and / or location that can be defined by the configuration data) to associate with the control device to which the mobile device is connected. Furthermore, the mobile device can receive a selection of one or more other control devices (e.g., a control source device associated 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 the instruction to associate the control device with one of the configuration identifiers at 616, the mobile device can create an association between the control device and the selected configuration identifier in the configuration data at 618. To associate the control device with other control devices identified in the configuration identifier, the mobile device can store the control device's configuration identifier along with the associated configuration identifier in memory. The associated configuration identifier can be sent from the mobile device to the control device via a connection for storage at the control device. The associated configuration identifiers can be stored locally at the control device, enabling the control device to send messages to and / or receive messages from the associated devices to achieve load control.

[0158] At 620, the mobile device may transmit a configuration message (e.g., a claim message, association message, diagnostic message, etc.) to a control device to which the mobile device is connected. The configuration message may indicate that the control device has been claimed and / or associated with a selected configuration identifier in the configuration data. In response to receiving the configuration message, the control device may transmit an acknowledgment message (e.g., a claim confirmation message) to the mobile device. The claim confirmation message may include a unique identifier (e.g., a number) of the control device from which the claim confirmation message was transmitted. Before sending the claim message, the mobile device may check whether the control device has already been claimed. If the control device has already been claimed, the mobile device may block the transmission of an additional claim message and proceed to 622.

[0159] If the mobile device does not receive a claim confirmation message from the control device at 622, procedure 600 may loop to allow the mobile device to attempt to connect to the same control device or a different control device. The claim confirmation message may include a unique identifier (e.g., a number) of the control device. When the mobile device receives a claim confirmation message from the control device to which it is connected at 622, at 624, the mobile device may store the unique identifier of the control device and associated information (e.g., a configuration identifier associated with the control device) in memory. The unique identifier stored during the claim procedure may be a device that can be added to the network (e.g., individually or in batches) during the joining procedure. Associated information may be stored to identify the control device associated with the claimed control device used to join the network.

[0160] If at 616 the mobile device does not receive an instruction to associate the control device connected to the mobile device with one of the configuration identifiers, but receives an instruction at 626 to unassociate the control device with the associated configuration identifier, the mobile device can unassociate the control device with the associated configuration identifier at 628 and delete the unique identifier and association information of the control device from memory at 630. The mobile device can send messages to (multiple) control devices to remove the association from the memory of (multiple) control devices.

[0161] If the mobile device fails to claim and / or associate the control device with the configuration identifier in the configuration data at 632, procedure 600 may loop to allow the mobile device to attempt to connect to different or the same control device (e.g., if the control device was just declaimed and / or unassociated at 626). When the mobile device completes claiming and / or associating the control device at 632 (e.g., the user actuates a button on the mobile device's user interface to end the configuration procedure), the mobile device may exit configuration mode at 634, and procedure 600 may terminate. Furthermore, the mobile device may stop periodically transmitting mobile device beacon messages at 634.

[0162] Control devices can provide different types of feedback to indicate different information to the user. For example, a lighting control device can provide feedback indicating that it has been detected and / or selected for configuration and / or control (e.g., the control device emits a beacon message received by the mobile device that is above a detection threshold). A lighting control device selected for configuration and / or control can flash (e.g., at a varying frequency), increase and / or decrease the intensity level of the lighting load, increase and / or decrease the color temperature of the lighting load, illuminate the lighting load with a predefined color or color temperature, and / or provide another visual feedback to the user through the lighting load.

[0163] The selected lighting control device, which transmits a beacon message with the strongest signal strength received by the mobile device, can provide different types of feedback. For example, a lighting control device that transmits a beacon message with the strongest signal strength received by the mobile device can 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 distinguishes the lighting control device.

[0164] After a lighting control device has been configured (e.g., assigned to a zone and / or area), it can provide different types of feedback. For example, a lighting control device assigned to a zone or area in the lighting control configuration information can flash at a different rate than an unassigned device selected for configuration and / or control, increase / decrease the intensity level of the lighting load at a different rate than an unassigned device selected for configuration and / or control, increase / decrease the color temperature of the lighting load at a different rate than an unassigned device selected for configuration and / or control, illuminate the lighting load with a different color or color temperature than an unassigned device selected for configuration and / or control, and / or provide the user with other visual feedback that distinguishes the assigned lighting control device.

[0165] Feedback types can be pre-programmed at the lighting control unit and / or provided to the lighting control unit in a message. For example, the feedback type can be provided in a configuration message where the lighting control unit has been selected for configuration and / or control and / or in another message from a device in the load control system to the lighting control unit.

[0166] Figure 7 It is a flowchart illustrating the configuration of a load control system (e.g., load control system 100 and / or...). Figure 2A The load control system 200 shown illustrates an example program 700 for the control device to claim and / or associate the control device. Program 700 can be executed as part of a configuration program (e.g., a claim program and / or an association program). Program 700 can be implemented by a control device (e.g., a lighting control device). However, other control devices can similarly execute one or more parts of program 700. During program 700, the lighting control device can provide different types of feedback. Program 700 can be executed when the lighting control device is not yet in configuration mode (e.g., the lighting control device has not entered configuration mode and begins periodically transmitting control device beacon messages upon power-up).

[0167] Procedure 700 can reduce RF traffic (e.g., RF transmissions) in an area. RF traffic in an area (e.g., in a building where lighting control devices are installed) can be generated by control devices in a load control system and other devices in the area (such as other beacon transmitters, wireless network access points, etc.). For example, method 700 can be implemented when network devices, mobile devices, system controllers, and / or other control devices identify that the number of control devices in the load control system exceeds a device counting threshold (e.g., greater than 25, 50, 100, etc.). For example, if the number of control devices in the load control system exceeds the threshold, there may be relatively high RF traffic (e.g., interference) when the control devices simultaneously transmit beacon messages. Alternatively, procedure 700 can be implemented when network congestion exceeding a threshold is detected at a device (e.g., lighting control device, system controller, network device, mobile device, etc.). For example, network congestion may exceed the threshold when the probability of message reception drops below the reception probability threshold (e.g., the message may need to be retransmitted more than the retransmission threshold). Program 700 can reduce 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 a lower collision rate between transmitted and / or dropped messages. Identification of the possibility of high RF traffic and / or network congestion can be provided manually by the user (e.g., using a user interface on a mobile device) and / or automatically by one or more control devices of the load control system (e.g., the system controller).

[0168] like Figure 7As shown, 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 devices 150, 250, 350), procedure 700 may begin at 702. The mobile device beacon message may be transmitted in response to a configuration mode entered at the mobile device (e.g., claim mode and / or association mode) (e.g., in response to a button selection on an application at the mobile device). While the mobile device is in configuration mode, the mobile device beacon message may be transmitted periodically. The mobile device beacon message may include a beacon message identifier for the mobile device. For example, the beacon message identifier may be a unique identifier identifying the mobile device (e.g., or an application running on the mobile device), and / or a non-unique identifier, such as the identifier of the manufacturer of the mobile device and / or control device for a group, area, building, load control system, and / or load control system. 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 (e.g., using a short-range wireless communication protocol). The mobile device can determine the Received Signal Strength Indicator (RSSI) of the received network device beacon message (e.g., the signal strength at the time the network device beacon message was received). The RSSI of the mobile device beacon message can be compared with a discovery threshold (e.g., a detection threshold). The discovery threshold can be received in the mobile device beacon message and / or pre-configured at the lighting control device. The discovery threshold can be configured by the user of the mobile device, pre-configured on the mobile device and / or the lighting control device, and / or configured by the network (e.g., received from the system controller).

[0169] At point 704, it can be determined whether the lighting control device is within the detection range of the mobile device. For example, the lighting control device can determine if it is within the detection range of the mobile device by determining whether the Received Signal Strength Indicator (RSSI) of a received mobile device beacon message is greater than or equal to a detection threshold (e.g., a detection threshold included in the received mobile device beacon message). If the lighting control device determines at point 704 that it is within the detection range of the mobile device, then at point 705, the lighting control device can enter a configuration mode (e.g., claim mode and / or association mode). Furthermore, if the beacon message identifier of the received mobile device beacon message is a specific (e.g., predetermined) beacon message identifier, the lighting control device can enter (e.g., only) the configuration mode. The configuration mode can be a mode in which the mobile device can (e.g., locally and / or at the system controller) store the association between a unique identifier of the lighting control device and a configuration identifier of configuration data. The stored association enables the identification of the associated control device to perform load control or otherwise respond to messages from the associated device during normal operation. For example, entering 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 at 704 that the lighting control device is not within the detection range of the mobile device, then procedure 700 can end at 728.

[0170] Mobile device beacon messages can operate as triggering events to induce lighting control devices to transmit beacon messages (e.g., control device beacon messages). At 706, the lighting control device can begin periodically transmitting control device beacon messages. Control device beacon messages may include a beacon message identifier for the lighting control device and / or a device type. For example, the beacon message identifier for the control device may be a unique identifier identifying the lighting control device, and / or a non-unique identifier, such as the identifier of the manufacturer of the mobile device and / or control device for a group, area, building, load control system, and / or load control system 100. Control device beacon messages may be transmitted in response to receiving a mobile device beacon message with a Received Signal Strength Indicator (RSSI) greater than a discovery threshold and / or the beacon message identifier of the received mobile device beacon message being a specific (e.g., predetermined) beacon message identifier.

[0171] At point 708, the lighting control device can provide a first feedback type indicating that it has entered a configuration mode. This first feedback type can be provided by causing the lighting load to flash, 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 providing other visual feedback to the user. When the lighting control device falls outside the detection range of the mobile device (e.g., after a timeout period following the lighting control device falling outside the wireless range of the mobile device), the lighting control device can cease providing the first feedback type. If the lighting control device re-enters the detection range of the mobile device (e.g., after a timeout period following the lighting control device falling outside the detection range), the lighting control device can resume providing the first feedback type.

[0172] At point 710, it can be determined whether the lighting control device is connected to the mobile device. For example, the lighting control device can determine whether a control device beacon message transmitted by the lighting control device has been received at the mobile device at the strongest received signal strength indicator (RSSI) of a lighting control device in configuration mode (e.g., those lighting control devices that have not yet been claimed). For example, the lighting control device can receive a message indicating that the control device beacon message has been received at the mobile device at the strongest RSSI of a control device in configuration mode. For example, the message may 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.

[0173] If the lighting control device does not receive a connection message at 710 (e.g., the lighting control device's beacon message control signal has not yet been received with the strongest received signal strength indicator), then at 712, the lighting control device can determine whether it is still within the mobile device's detection range (e.g., still receiving mobile device beacon messages). If the lighting control device is still within the mobile device's detection range at 712, then at 708, the lighting control device can continue to provide the first feedback type again. If the lighting control device is no longer within the detection range at 712, then at 714, the lighting control device can stop providing feedback (e.g., the first feedback type), exit the configuration mode at 716, and procedure 700 can end at 728. Furthermore, at 714, the control device can stop periodically transmitting control device beacon messages.

[0174] When the lighting control device is connected to a mobile device at 712 (e.g., in response to a control device beacon message from the lighting control device being received with the strongest received signal strength indicator of the lighting control device in configuration mode), the lighting control device can provide a second feedback type at 718. The second feedback type can distinguish the lighting control device from other lighting control devices that provide the first feedback type. For example, the second feedback type can be provided by causing the lighting load to flash, 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 providing the user with visual feedback different from the first feedback type.

[0175] In one example, a lighting control device in configuration mode can illuminate each corresponding lighting load in orange to indicate that the lighting control device is in configuration mode, and a lighting control device that has transmitted a control device beacon message received by the mobile device with the strongest received signal strength indicator can illuminate its corresponding lighting load in blue. Blue lighting loads can indicate to the user the lighting control device selected for claiming and / or associating. Blue lighting loads can also indicate to the user the lighting control device most likely closest to the mobile device among the discovered lighting control devices. Orange lighting loads can indicate to the user those lighting loads within the mobile device's discovery range and / or in configuration mode. Furthermore, orange lighting loads can indicate to the user those lighting control devices and / or lighting loads that are operating normally.

[0176] The lighting control devices in the discovered group of devices (e.g., a single lighting control device) can provide a second feedback type at a given time. As the user moves around with the mobile device, control device beacon messages from another lighting control device can be received with a stronger received signal strength indicator. The mobile device can transmit one or more messages configured to cause a change in the lighting load providing the second feedback type. The mobile device can cause a different lighting load to provide the second feedback type by transmitting a message (e.g., a connection message) with the identifier of the updated lighting control device from which the strongest control device beacon message is received. The mobile device can disconnect the bidirectional communication connection with the lighting control device currently providing the second feedback type, and this lighting control device can stop providing the second feedback type. The lighting control device can revert to providing the first feedback type or stop providing feedback entirely (e.g., if the lighting control device fails to receive a mobile device beacon message from the mobile device within a predefined time period). Therefore, if at 710 the lighting control device determines that the beacon message control signal of the lighting control device is not received with the strongest received signal strength indicator, then at 712, while the lighting control device is still within the detection range of the mobile device, the lighting control device can provide the first feedback type again at 708.

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

[0178] If the lighting control device has not been claimed and / or assigned a configuration identifier at 720, and the beacon message control signal of the lighting control device is still received by the mobile device at 710 with the strongest received signal strength indicator, the lighting control device may continue to provide the second feedback type at 718. However, if the lighting control device determines at 710 that the beacon message control signal of the lighting control device is no longer received with the strongest received signal strength indicator, and the lighting control device is still within the detection range of the mobile device at 712, the lighting control device may again provide the first feedback type at 708.

[0179] When the lighting control device at location 720 has been claimed and / or assigned a configuration identifier, the lighting control device at location 722 can provide a third type of feedback. The third type of feedback distinguishes the lighting control device from other control devices in configuration modes that provide the first and / or second feedback types. For example, the third type of feedback can be provided by causing the lighting load to flash, 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 providing the user with visual feedback different from the first and / or second feedback types.

[0180] In one example, a lighting control device within the mobile device's detection range (e.g., in configuration mode) can illuminate each corresponding lighting load in orange to indicate a lighting control device within the mobile device's detection range (e.g., unclaimed and without the strongest control device beacon message signal received by the mobile device). A lighting control device with a control device beacon message received by the mobile device with the strongest received signal strength indicator (e.g., and declaimed) can illuminate the corresponding lighting load in blue, and a claimed lighting control device can illuminate the corresponding lighting load in green. Green lighting loads can indicate to the user that a lighting control device has been claimed and / or assigned a configuration identifier. Lighting control devices claimed and assigned to different luminaires, groups, and / or zones can provide different types of feedback (e.g., illuminating the lighting load in a different color, flashing in a different manner, illuminating the lighting load at a different color temperature or dimming level, etc.).

[0181] A third feedback type may also be provided in response to other configuration information used for configuring (e.g., claiming, diagnosing, associating, etc.) and / or controlling the lighting control device. For example, a third feedback type may be provided after the lighting control device has been configured with scene, dimming level, and / or other lighting control information to complete the configuration (e.g., claiming, diagnosing, associating, etc.) and / or control of the lighting control device. After providing the third feedback type at 722, at 724, the lighting control device may transmit a message (e.g., a claim confirmation message) including the lighting control device's unique identifier (e.g., a number). The lighting control device may then enter a join mode at 726. In join mode, the lighting control device may stop continuously transmitting (e.g., periodically transmitting) control device beacon messages via a short-range wireless communication link and may periodically switch between transmitting control device beacon messages and listening for requests to join the wireless communication network (e.g., as performed at 412 of procedure 400). Procedure 700 may end at 728.

[0182] The first, second, and / or third feedback types can be provided by the lighting control device when it is in a configuration mode (e.g., receiving a mobile device beacon message at or above a detection threshold). The lighting control device can stop providing feedback when the mobile device moves away from the lighting control device, causing the received signal strength indicator of the mobile device beacon message to fall below the detection threshold.

[0183] If the lighting control device is removed from a previous assignment or its claim status is removed, the lighting control device may cease providing a third feedback type. When the lighting control device is in configuration mode, it may revert to a first and / or second feedback type. The lighting control device may cease providing feedback when it is outside the detection range of a mobile device (e.g., no mobile device beacon message at or above a detection threshold is received). The lighting control device may automatically exit configuration mode and / or cease providing feedback when it fails to receive a mobile device beacon message from the mobile device within a timeout period (e.g., this indicates the mobile device may be outside detection range). The lighting control device may also automatically exit configuration mode and / or cease providing feedback when it receives a message from the mobile device and determines that the received signal strength indicator of the mobile device beacon message is below a detection threshold, and / or receives an indication in the message that the lighting device is outside detection range (e.g., even though the lighting control device is within wireless communication range with the mobile device), the lighting control device may also or alternatively exit configuration mode and / or cease providing feedback. Although procedure 700 may be described with reference to a lighting control device, other types of control devices may be implemented similarly.

[0184] Load control system (e.g., Figure 1 The load control system 100 shown may include a relatively large number of control devices (e.g., more than 50 or more than 100), one or more of which can communicate on a network (e.g., network 260). For example, as described herein, control devices may periodically transmit control device beacon messages, which may increase network congestion as the number of control devices increases. In addition to control device beacon messages, control devices may also transmit other types of messages in the network for controlling electrical loads within the load control system. As the number of control devices in the load control system increases, wireless (e.g., RF) traffic in the network environment may increase proportionally. With increased RF traffic in the network environment, message loss and / or message collisions may occur, which may lead to increased latency and / or reduced reliability. One or more procedures can be used to reduce RF traffic in the network environment.

[0185] To reduce RF traffic in a network environment, various procedures can be implemented to reduce the number of messages transmitted in the network environment. Periodic message transmissions (e.g., control device beacon messages or other periodic messages) can be restricted to help reduce network congestion more than non-periodic messages (e.g., messages transmitted in response to actuation on a control device). A mobile device can transmit (e.g., continuously or periodically) a mobile device beacon message to trigger a message transmission from a control device in the network. The mobile device beacon message may include a discovery threshold (e.g., a detection threshold). If a given control device receives a mobile device beacon with a signal strength (e.g., a received signal strength indicator) above the discovery threshold, the control device can transmit one or more messages. For example, a control device can receive a mobile device beacon signal above the discovery threshold and respond by transmitting (e.g., periodically) a control device beacon message. Although control device beacon messages can be described herein as being transmitted in response to mobile device beacon messages, other types of message transmissions can be similarly controlled as described herein.

[0186] If the discovery threshold in the mobile device beacon message is too low, a relatively large number of control devices may transmit corresponding control device beacon messages, which could lead to increased latency and / or reduced reliability. As described herein, a mobile device can receive control device beacon messages triggered by a mobile device beacon message at a control device. 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 not be able to discover some of the control devices, even if those control devices may be located near the mobile device. Conversely, if the discovery threshold is too high, too few control devices may transmit control device beacon messages in response to a mobile device beacon message.

[0187] The received signal strength of RF communications (such as mobile device beacon messages) can be variable 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 where the mobile device and / or control device is located, the physical properties of the mobile device and / or control device, and radio interference from other devices in the area. Because the received signal strength of RF communications can be variable, the number of control devices that receive mobile device beacon messages above a detection threshold can be variable. Therefore, the number of control devices that receive mobile device beacon messages above a detection threshold (e.g., the number of control devices detected) can be affected by these factors and / or environmental conditions. In one example, a mobile device with a more powerful transceiver or antenna with a higher RF transmission capability can detect more control devices above the same detection threshold compared to a less powerful transceiver or antenna with a lower RF transmission capability. Furthermore, the number of control devices detected can change as the mobile device moves around the area.

[0188] To control the number of control devices discovered by mobile device discovery beacons, the mobile device can adjust (e.g., periodically adjust) the discovery threshold included in the mobile device beacon messages. The mobile device can (e.g., periodically) monitor the number of control device beacon messages received in response to the mobile device discovery beacon messages and adjust the discovery threshold such that the number of control devices discovered at any given time remains within a target range. For example, the mobile device can adjust the discovery threshold such that the number of discovered control devices is below a low-side threshold TH. 低 With high-side threshold TH 高 The number of devices detected can be between 15 and 25 (e.g., between 15 and 25 devices). The amount by which the detection threshold is adjusted can depend on the number of control devices detected. For example, when the number of detected devices is closer to the target range (e.g., between 1 and 14 or 26 and 40), the mobile device can adjust the detection threshold by a smaller amount, while when the number of detected control devices is further away from the target range (e.g., less than 1 or greater than 40), the mobile device can adjust the detection threshold by a larger amount.

[0189] Once the number of control devices discovered is within the low-side threshold TH 低 and high-side threshold TH 高Within the defined scope, the mobile device can select one or more control devices for configuration (e.g., claiming, associating, etc.) and / or control. After the selected control device has completed configuration and / or control, the control device can continue to emit its control device beacon. The mobile device can continue to count the control devices among the number of discovered control devices and can maintain the discovery threshold at the same level. Alternatively, the mobile device can determine that a control device has completed configuration and / or control and can remove this control device from the number of discovered control devices. The mobile device can then increase the discovery threshold so that the number of discovered control devices is again reduced by the lower threshold TH. 低 and high-side threshold TH 高 Within the defined range. Furthermore, the control device may cease transmitting its control device beacons. If this causes the number of control device beacons received by the mobile device (e.g., the number of detected control devices) to drop below the low-side threshold TH... 低 The mobile device can then increase the detection threshold.

[0190] Figure 8A This is a flowchart depicting an example procedure 800 for detecting when a control device in a load control system (e.g., load control system 100) is within the detection range. Procedure 800 may be executed as part of a configuration procedure (e.g., a claim procedure, an association procedure, or other configuration procedure). Procedure 800 may be implemented by a control device (e.g., a lighting control device or another control device) to determine whether the control device is within the detection range of a mobile device. While a control device may be provided as an example device for determining whether a control device is within the detection range of a mobile device, the mobile device may similarly execute one or more portions of procedure 800. For example, the mobile device may determine whether a control device is within the detection range.

[0191] Program 800 may begin at 802. Program 800 may be executed periodically. For example, the control device may transmit its control device beacon messages at a given rate (e.g., transmission rate), and program 800 may execute at approximately the same rate. Therefore, the time between consecutive executions of program 800 may be approximately the same as the transmission period of the control device beacon messages. At 804, the control device may receive mobile device beacon messages from the mobile device. The mobile device beacon messages may be transmitted in response to the mobile device entering a configuration mode (e.g., claim mode, association mode, or another configuration mode), for example, in response to selecting a button on an application on the mobile device. While the mobile device is in configuration mode, the mobile device beacon messages may be transmitted periodically. The mobile device beacon messages may include a beacon message identifier and / or a discovery threshold for the mobile device. The beacon message identifier may be an identifier of an application running on the mobile device. The mobile device beacon messages may be transmitted using a short-range wireless communication protocol via RF communication signals. The discovery threshold may define the discovery range.

[0192] At point 806, the control device can determine whether it is within the detection range of the mobile device. The control device can compare the received signal strength indicator (RSS) when receiving a mobile device beacon message with a detection threshold included in the mobile device beacon message. When the RSS indicator of the control device is greater than the detection threshold, the control device can determine that it is within the detection range. If the RSS indicator when receiving a mobile device beacon message at the control device is lower than the detection threshold, the control device can determine that it is outside the detection range. When the RSS indicator when receiving a mobile device beacon message is equal to the detection threshold, the control device can be configured to be either within or outside the detection range.

[0193] If the control device determines at 806 that it is within detection range, the control device can set the IN_RANGE flag. For example, at 808, the control device can set the IN_RANGE flag to a value indicating that the control device is within detection range (e.g., 1, true, or another value indicating that the control device is determined to be within detection range). The control device can check the value of the IN_RANGE flag before transmitting a control device beacon message in response to receiving a mobile device beacon message.

[0194] The control device may receive multiple mobile device beacon messages at 804 and determine at 806, over a period of time, that it fluctuates between being within and outside the detection range. This may occur more frequently for control devices at the edge of the detection range (e.g., relatively close to the detection threshold). This fluctuation may be caused by the variability of RF communication on the network and may cause the mobile device to have to update the number of detected control devices more frequently. To prevent the control device from fluctuating between identifying itself as being within and outside the detection range over a period of time, the control device may start a timer (e.g., a detection timer) after determining at 806 that the control device is within the detection range. The detection timer may define a detection period, which expires when the timer reaches a predefined value (e.g., when the detection period ends). The detection period may be a time interval (e.g., 2 seconds, 4 seconds, 8 seconds, etc.) that begins when the control device receives a mobile device beacon message with a received signal strength greater than the detection threshold and allows the control device to continue to maintain its status as a detected device during the detection period (e.g., by maintaining the state of the IN-RANGE flag).

[0195] If the control device determines at 806 that it is outside the detection range, then at 810, the control device can determine whether it was within the detection range during the detection period. If the control device has received a mobile device beacon message with a value greater than the detection threshold during the detection period, the control device can determine that it was within the detection range during the detection period. If the control device determines at 810 that it was outside the detection range included in the mobile device beacon message at 806 and was not within the detection period (e.g., the detection timer has not yet started or has expired), the control device can clear the IN_RANGE flag at 812. For example, at 812, 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 the detection range (e.g., 0, false, or another value indicating that the control device is outside the detection range). At 814, the control device can determine whether the IN_RANGE flag is set (e.g., whether the value of the IN_RANGE flag indicates that the control device is within the detection range). If the control device determines that the IN_RANGE flag is set, the control device may transmit a control device beacon message at 816, and program 800 may terminate at 818. If the IN_RANGE flag is not set, program 800 may terminate at 818 (e.g., the control device does not need to transmit a control device beacon message).

[0196] A mobile device can send multiple consecutive mobile device beacon messages within a relatively short period of time. A control device located at the edge of the detection range (e.g., based on a detection threshold included in the mobile device beacon messages) can receive some of the mobile device beacon messages with a received signal strength (e.g., RSSI) above the detection threshold and some with a received signal strength below the detection threshold. Therefore, the control device can rapidly alternate between entering and exiting a configuration mode. This can cause the control device to indicate to the user that it is within and outside the detection range, for example, by flashing and / or illuminating in a given color, which can be visually distracting. Because the mobile device can adjust the detection threshold based on the number of control devices within the detection range (e.g., in configuration mode), having one or more control devices alternate in this way can result in the mobile device making a relatively large number of unnecessary adjustments.

[0197] These situations can be addressed by utilizing the discovery threshold TH. RSSI Implementing hysteresis avoidance makes it more likely that a control device in a given state (e.g., within or outside a configuration mode) will remain in that state. The control device can achieve this by using one or more threshold offsets (e.g., such as...). Figure 8B (as shown) and / or discovery cycle (e.g., as shown) Figure 8A (As shown) to implement hysteresis. Threshold offset can be used to determine the updated discovery threshold (e.g., an increased or decreased discovery threshold). Threshold offset and / or discovery period can make a control device that is in configuration mode at a given time more likely to remain in configuration mode for performing configuration, because the control device can remain in configuration mode for a longer period of time after entering configuration mode. Threshold offset can also make a control device that is outside the discovery range for entering configuration mode remain outside the discovery range.

[0198] Figure 8B This is a flowchart depicting an example procedure 850 for detecting whether a control device in a load control system (e.g., load control system 100) is within the detection range. Procedure 850 may be executed as part of a configuration procedure (e.g., a claim procedure, an association procedure, or other configuration procedure). Procedure 850 may be implemented by a control device (e.g., a lighting control device or another control device) to determine whether the control device is within the detection range of a mobile device. While a control device may be provided as an example device for determining whether it is within the detection range of a mobile device, the mobile device may similarly execute one or more portions of procedure 850. For example, the mobile device may determine whether a control device is within the detection range.

[0199] Program 850 may begin at 852. Program 850 may be executed periodically or in response to another triggering event. For example, the control device may transmit its control device beacon message at a given rate (e.g., transmission rate), and program 850 may execute at approximately the same rate. Therefore, the time between consecutive executions of program 850 may be approximately the same as the transmission period of the control device beacon message. The mobile device beacon message may be transmitted in response to the mobile device entering a configuration mode (e.g., claim mode, association mode, or another configuration mode), for example, in response to selecting a button on an application at the mobile device. While the mobile device is in configuration mode, the mobile device beacon message may be transmitted periodically.

[0200] At 854, the control device can receive mobile device beacon messages from the mobile device. The mobile device beacon message may include a beacon message identifier for the mobile device, one or more threshold offsets, and / or a discovery threshold TH. RSSI The threshold offset can be pre-stored in the memory of the control device. The beacon message identifier can be an identifier of an application running on the mobile device. Mobile device beacon messages can be transmitted using short-range wireless communication protocols via RF communication signals. Threshold TH is then discovered. RSSI The scope of discovery can be defined.

[0201] At point 856, the control device can determine the discovery threshold TH based on the received mobile device beacon messages. RSSI For example, mobile device beacon messages may include a discovery threshold TH. RSSI The indication. Threshold TH was detected. RSSI It can have a value of approximately -60 dBm. At 858, the control device can determine whether the IN_RANGE flag is set. For example, when the control device enters the detection range (e.g., the control device enters configuration mode), the IN_RANGE flag can be set to a value (e.g., 1, True, or another value indicating that the control device is determined to be within the detection range). When the control device exits the detection range (e.g., the control device exits configuration mode), 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 the detection range (e.g., 0, False, or another value indicating that the control device is outside the detection range). For example, when a detection period (e.g., 2 seconds, 4 seconds, or 8 seconds) has elapsed since the control device last received a mobile device beacon message with a signal strength above the detection threshold, 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 the detection range.

[0202] If the control unit determines at 858 that the IN_RANGE flag is not set (e.g., it was not set previously), the control unit can determine at 860 whether it is within the detection range. The control unit can then determine this based on the detection threshold TH. RSSI Implement hysteresis for entering and exiting discovery scopes (e.g., configuration modes). For example, the discovery scope may be based on a first threshold offset TH used for entering a discovery scope (e.g., entering a configuration mode). 偏移1 This differs from the second threshold offset TH used for exiting the discovery scope (e.g., exiting configuration mode). 偏移2 First threshold offset TH 偏移1 Second threshold offset TH 偏移2 They can have the same value or different values. For example, the first threshold offset TH 偏移1 Second threshold offset TH 偏移2 Each can have a value of 5dBm. For example... Figure 8B As shown, the control device can be based on the detection threshold TH RSSI First threshold offset TH 偏移1 The Received Signal Strength Indicator (RSSI) when the control device receives a beacon message from the mobile device. RX To determine whether it is within the detection range, the control device can offset the first threshold TH. 偏移1 Add to the detection threshold TH RSSI This makes the detection threshold TH RSSI Increase to, for example, the threshold TH for detection 进入 Alternatively, mobile device beacon messages may include a discovery threshold TH. RSSI and the entry detection threshold TH 进入 First threshold offset TH 偏移1 This allows the detection threshold TH to be determined. RSSI (For example, entering the detection threshold TH) 进入 The threshold is set to be offset from the second threshold TH for exiting the discovery scope (e.g., exiting configuration mode). 偏移2 A stronger RSSI value. For example, a threshold TH was found. RSSI It can be approximately -60dBm, first offset TH 偏移1 It can be 5dBm, and the control device can add these two values ​​together to reach the detection threshold TH. 进入 The value is -55dBm. The control device can display the Received Signal Strength Indicator (RSSI). RX With the entry detection threshold TH 进入A comparison is made to determine if the control device is within detection range and whether it should enter configuration mode. Using hysteresis makes it more likely that a control device located at the edge of detection range will be determined to be outside the detection range for entering configuration mode. This helps avoid the control device being affected by the magnitude of the received signal strength (RSSI) when receiving consecutive beacon messages. RX The situation of quickly entering and exiting configuration mode due to fluctuations.

[0203] If the control device at 860 determines the Received Signal Strength Indicator (RSSI) RX Less than the entry detection threshold TH 进入 (For example, if the control device is not within detection range), then procedure 850 can proceed to 870 (for example, without setting the IN_RANGE flag). If the control device determines the Received Signal Strength Indicator (RSSI) at 860... RX Greater than or equal to the detection threshold TH 进入 (For example, if the control device is within detection range), the mobile device can set the IN_RANGE flag at 862. For example, at 862, the control device can set the IN_RANGE flag to a value indicating that the control device is within detection range (e.g., 1, true, or another value indicating that the control device is determined to be within detection range). The control device can check the value of the IN_RANGE flag before transmitting a control device beacon message in response to receiving a mobile device beacon message. Procedure 850 can proceed to 870.

[0204] If the control unit determines at 858 that the IN_RANGE flag has been set, it can determine at 866 whether it remains within the detection range. The control unit can then determine this based on the detection threshold TH. RSSI Implement hysteresis for entering and exiting discovery scopes (e.g., configuration modes). Figure 8B As shown, the control device can be based on the detection threshold TH RSSI Second threshold offset TH 偏移2 The Received Signal Strength Indicator (RSSI) when the control device receives a beacon message from the mobile device. RX This determines whether it remains within the detection range. The control device can determine this from the detection threshold TH. RSSI Subtract the second threshold offset TH 偏移2 This makes the detection threshold TH RSSI Reduced to, for example, the exit discovery threshold TH 退出 Alternatively, mobile device beacon messages may include a discovery threshold TH. RSSI and exit discovery threshold TH 退出 For example, the threshold TH was found. RSSI It can be approximately -60dBm, second threshold offset TH偏移2 It can be 5dBm, and the control device can add these two values ​​together to reach the exit detection threshold TH. 退出 The value is -65dBm. Although in Figure 8B Not shown, but the control device can detect the threshold TH. RSSI Subtract the second threshold offset TH 偏移2 (It can be less than the first threshold offset TH) 偏移1 This establishes a lower detection threshold for exiting configuration mode. The control unit can use the Received Signal Strength Indicator (RSSI) to set this threshold. RX Exit discovery threshold TH for exit configuration mode 退出 A comparison is made to determine whether the control device is still within detection range (e.g., whether the control device should exit configuration mode). This can help avoid the control device being affected by the Received Signal Strength Indicator (RSSI) when receiving continuous beacon messages. RX The situation of quickly entering and exiting configuration mode due to fluctuations.

[0205] If the control device at 866 determines the Received Signal Strength Indicator (RSSI) RX Greater than or equal to the exit discovery threshold TH 退出 (For example, the control unit is still within detection range), then procedure 850 can proceed to 870 (for example, without clearing the IN_RANGE flag). If at 866 the control unit determines the Received Signal Strength Indicator (RSSI) RX Less than the exit discovery threshold TH 退出 If (for example, the control device is outside the detection range), the mobile device can clear the IN_RANGE flag at 868. For example, at 868, the control device can clear the IN_RANGE flag from memory or set it to a value indicating that the control device is outside the detection range (e.g., 0, false, or another value indicating that the control device is outside the detection range). The control device can also determine whether a detection period (e.g., 2 seconds, 4 seconds, or 8 seconds) has elapsed since the control device last received a mobile device beacon message with a signal strength above a detection threshold. If the control device determines that the detection period has elapsed, it can clear the IN_RANGE flag at 868.

[0206] The control device may check the value of the IN_RANGE flag before transmitting a control device beacon message in response to receiving a mobile device beacon message. At 870, the control device may determine whether the IN_RANGE flag is set (e.g., whether the value of the IN_RANGE flag indicates that the control device is within detection range). If the control device determines that the IN_RANGE flag is set or otherwise indicates that the control device is within detection range, then at 872, the control device may transmit the control device beacon message. Procedure 850 may end at 874. If the IN_RANGE flag is not set or otherwise indicates that the control device is outside detection range, then procedure 850 may end at 874. For example, when outside detection range, the control device may fail to transmit the control device beacon message.

[0207] Figure 9 This is a flowchart depicting an example procedure 900 for discovering control devices in a load control system (e.g., load control system 100). Procedure 900 can be executed as part of a configuration procedure (e.g., a claim procedure, an association procedure, or another configuration procedure). Procedure 900 can be implemented by a mobile device (e.g., a network device). For example, procedure 900 can be executed periodically by a mobile device (e.g., every second, every ten seconds, every minute, etc.) to monitor the number of control devices transmitting control device beacon messages, thereby allowing adjustment of the number of control devices transmitting control device beacon messages on the network. However, other control devices can similarly execute one or more portions of procedure 900.

[0208] Procedure 900 may begin at 902. At 904, the mobile device may count the number of control devices (e.g., detected control devices) within the mobile device's detection range. The mobile device may 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 the area where the mobile device is located. The mobile device may transmit a message including a detection threshold TH. RSSI Mobile device beacon messages. If the control device sends a message with a value greater than the detection threshold TH... RSSI (For example, such as) Figure 8A (as shown) and / or greater than the detection threshold TH RSSI Add the first threshold offset TH 偏移1 (For example, such as) Figure 8BIf a mobile device receives a mobile device beacon message with a signal strength value (e.g., a received signal strength value), the control device can transmit its control device beacon message. If the mobile device receives a control device beacon message from the control device, the mobile device can determine that this control device is within detection range. Therefore, the mobile device can count the number of detected 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 record (e.g., a log) of each control device beacon it receives, along with accompanying information (e.g., the identifier of the control device from which it received the beacon and / or the time the beacon was received). The mobile device can count the number of detected control devices by determining the number of unique control devices from which it received the beacon within a given time period.

[0209] As described in this article, the control device can operate at a speed greater than the detection threshold TH. RSSI The signal strength received is used to receive mobile device beacon messages, and the control device beacon continues to be transmitted for at least one detection period. Even if it is determined that the subsequently received mobile device beacon message is less than the detection threshold TH... RSSI (For example, such as) Figure 8A (as shown) and / or less than the detection threshold TH RSSI Subtract the second threshold offset TH 偏移2 (For example, such as) Figure 8B (As shown) After this, the control device can also continue to transmit control device beacon messages during the detection cycle. To prevent the detection range from being adjusted too frequently, the mobile device can adjust the detection range at the detection threshold TH. RSSI After being adjusted (e.g., increased), the threshold TH is found to be adjusted (e.g., increased) again. RSSI Previously, the adjustment timer was allowed to expire. The adjustment timer could have a value greater than the detection period of the control device, allowing control devices no longer within detection range to stop transmitting control device beacon messages. Using an adjustment timer prevents mobile devices from adjusting (e.g., increasing) the detection threshold TH too frequently. RSSI and the overcorrection detection threshold TH RSSI .

[0210] At point 906, the mobile device can determine whether the adjustment timer has expired. If the mobile device determines at point 906 that the adjustment timer has expired, the mobile device can increase or decrease the detection threshold TH based on the number of detected control devices. RSSI If the mobile device determines at point 906 that the adjustment timer has not yet expired, the mobile device can lower the detection threshold TH based on the number of detected control devices. RSSI However, the detection threshold TH cannot be increased. RSSIFor example, the mobile device can wait for the adjustment timer to expire at 906 so that it can perform the detection threshold TH at 910 and 914. RSSI The increase in TH. This is due to the discovery of the threshold TH. RSSI In this document, it is exemplarily described as a received signal strength indicator value, thus revealing the threshold TH. RSSI Increasing the threshold can reduce the number of control devices within the detection range (e.g., because fewer control devices can receive signals with a detection threshold exceeding the increased threshold TH). RSSI The received signal strength indicator value of the mobile device beacon message). Due to the increased detection threshold TH RSSI This can be used to reduce the number of control devices within the detection range, so the mobile device can wait at 906 for adjusting the detection threshold TH before attempting to reduce the number of control devices within the detection range. RSSI The adjustment timer expires. The mobile device can wait for the adjustment timer period to expire before attempting to further reduce the number of control devices within the detection range, to prevent the reduction of the detection range from occurring too frequently and to avoid impacting the detection threshold TH. RSSI Potential overcorrection.

[0211] The mobile device can reduce the detection threshold TH at 920 and 924 without waiting for the adjustment timer to expire at 906. RSSI Mobile devices can reduce the detection threshold TH. RSSI This increases the number of control devices within the detection range without waiting for the adjustment timer to expire. Alternatively, mobile devices can lower the detection threshold TH. RSSI Previously, it was determined whether the adjustment timer had expired, and if the adjustment timer had not expired, the reduction of the detection threshold TH could be suppressed. RSSI .

[0212] When the number of devices detected 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), the mobile device can detect the threshold TH. RSSI Adjusting to a smaller amount, and when the number of detected control devices is further away from the target range (e.g., greater than 40 or less than 5), the mobile device can detect the threshold TH. RSSI Adjust to a larger amount. For the detection threshold TH... RSSI The adjustment amount can correspond to the threshold number of detected control devices relative to the target range. For example, at 908, the mobile device can adjust the number of detected control devices relative to a first high-side threshold TH. 高1 (For example, 40 control devices) are compared. The first high-side threshold TH 高1 It can be higher than the second-highest side threshold TH 高2(For example, 25 control units) a higher side threshold further away from the target range (e.g., 15 to 25 control units). While a first higher side threshold TH is provided... 高1 Second highest side threshold TH 高2 As an example, however, the mobile device may be configured with additional thresholds ranging from a maximum high-side threshold to a minimum high-side threshold, wherein the maximum and minimum high-side thresholds are set to adjust the detection threshold TH. RSSI The number of thresholds for the control devices discovered.

[0213] When the number of detected control devices is greater than the first high-side threshold TH at location 908, the mobile device determines that the number of detected control devices is greater than the first high-side threshold TH. 高1 At that time, the mobile device can detect the threshold TH at 910. RSSI Increase the first threshold increment Δ 增量1 This is an attempt to reduce the number of control devices within the detection range. First threshold increment Δ 增量1 It can be greater than the second threshold increment Δ 增量2 This is to attempt to reduce the number of control devices discovered by a larger amount. For example, the first threshold increment Δ 增量1 This could be, for example, about 2 dBm, which could set the detection threshold TH. RSSI The received signal strength indicator value increases from -4dBm to -2dBm. The mobile device can then begin transmitting (e.g., periodically) with an increased detection threshold TH. RSSI Mobile device beacon messages (e.g., one or more mobile device beacon messages).

[0214] If the mobile device determines at 908 that the number of detected control devices is less than (or equal to) the first high-side threshold TH 高1 Then the mobile device can determine at 912 whether the number of detected control devices is higher than the second high-side threshold TH. 高2 The second high-side threshold TH 高2 It can be less than the first high-side threshold TH 高1 If the mobile device determines that the number of detected control devices is greater than the second high-side threshold TH 高2 Then at point 914, the mobile device can detect the threshold TH. RSSI Increase the second threshold increment Δ 增量2 The second threshold increment Δ 增量2 It can be lower than the first threshold increment Δ 增量1 For example, because of the second high-side threshold TH 高2 Compared to the first high-side threshold TH 高1 Closer to the target range. For example, the second threshold increment Δ 增量2 It could be around 1 dBm, which could reduce the detection threshold TH. RSSIThe received signal strength indicator value increases from -2dBm to -1dBm. The mobile device can then begin transmitting (e.g., periodically) with an increased detection threshold TH. RSSI Mobile device beacon messages (e.g., one or more mobile device beacon messages).

[0215] If the mobile device increases the detection threshold TH RSSI (For example, at 910 or 914), the mobile device can then start an adjustment timer at 916. As described herein, the adjustment timer can be initialized to a value greater than the detection period of the control device. The adjustment timer can be initialized to a multiple of the detection period of the control device. For example, when the detection period of the control device is set to 4 seconds, the adjustment timer can be initialized to a value of 8 seconds. After the mobile device starts the adjustment timer at 916, program 900 can terminate at 928.

[0216] If the mobile device determines at 912 that the number of detected control devices is less than (e.g., less than or equal to) the second high-side threshold TH 高2 Then the mobile device can determine whether to lower the detection threshold TH. RSSI The mobile device can correlate the number of detected control devices with one or more low-side thresholds (TH). 低 Comparisons were made to determine the reduction threshold TH. RSSI The quantity. At 918, the mobile device can correlate the number of detected control devices with the first low-side threshold TH. 低1 (For example, a control device) is compared. The first low-side threshold TH 低1 It can be lower than the second lower side threshold TH 低2 (For example, 15 control units) are further away from the low-side threshold of the target range. While a first low-side threshold TH is provided... 低1 Second low-side threshold TH 低2 As an example, however, the mobile device may be configured with additional thresholds ranging from a maximum low-side threshold to a minimum low-side threshold, wherein the maximum low-side threshold and the minimum low-side threshold settings are used to adjust the detection threshold TH. RSSI The number of thresholds for the control devices discovered.

[0217] When the mobile device determines at point 918 that the number of detected control devices is less than the first low-side threshold TH 低1 At that time, the mobile device can detect the threshold TH at 920. RSSI Decrease the first threshold by Δ 减量1 This is an attempt to increase the number of control devices within the detection range. First threshold reduction Δ 减量1 The reduction Δ can be greater than the second threshold. 减量2This is to attempt to increase the number of control devices discovered by a larger amount. For example, the first threshold decrease Δ 减量1 It could be around 4 dBm, which could reduce the detection threshold TH. RSSI The received signal strength indicator value decreases from -2dBm to -6dBm. The mobile device can then begin transmitting (e.g., periodically) with a reduced detection threshold TH. RSSI Mobile device beacon messages (e.g., one or more mobile device beacon messages).

[0218] If the mobile device determines at 918 that the number of detected control devices is greater than (or equal to) the first low-side threshold TH 低1 Then the mobile device can determine at 922 whether the number of detected control devices is less than the second low-side threshold TH. 低2 The second low-side threshold TH 低2 It can be greater than the first low-side threshold TH 低1 (For example, closer to the target range). If the mobile device determines that the number of detected control devices is less than the second low-side threshold TH 低2 Then at point 924, the mobile device can detect the threshold TH. RSSI Decrease the second threshold by Δ 减量2 The second threshold reduction Δ 减量2 The amount can be reduced by Δ if it is less than the first threshold. 减量1 For example, because of the second low-side threshold TH 低2 Compared to the first lower-side threshold TH 低1 Closer to the target range. For example, the second threshold reduction Δ 减量2 It could be around 2 dBm, which could reduce the detection threshold TH. RSSI The received signal strength indicator value decreases from -2dBm to -4dBm. The mobile device can then begin transmitting (e.g., periodically) with an increased detection threshold TH. RSSI Mobile device beacon messages (e.g., one or more mobile device beacon messages).

[0219] If mobile devices lower the detection threshold TH RSSI (For example, at 920 or 924), then at 926, the moving device can cause the adjustment timer to expire (e.g., stop and clear the adjustment timer as if it had expired). As described herein, by reducing the detection threshold TH RSSI After the adjustment timer expires, the mobile device can immediately increase the detection threshold TH when it executes procedure 900 again. RSSI (For example, at 910 or 914) (For example, at the threshold TH) RSSI(In cases where a slight decrease leads to a sharp increase in the number of control devices discovered). After the moving device causes the adjustment timer to expire at 926, program 900 can end at 928.

[0220] While examples are provided for the threshold number of control devices detected and the values ​​used to increase or decrease the detection threshold, other values ​​can be implemented. For example, a mobile device can adjust the detection threshold by a larger amount (e.g., a higher percentage) when the number of control devices within the detection range is less than the target range, compared to when the number of control devices within the detection range is greater than the target range. In one example, the detection threshold could be increased by a multiple of 2 dBm when the number of control devices within the detection range is less than the target range, while it could be decreased by a multiple of 1 dBm when the number of control devices within the detection range is greater than the target range. This could help allow a larger number of control devices to be able to transmit control device beacons over the network in an attempt to ensure at least a minimum level of communication on the network.

[0221] Figure 10 This is a block diagram illustrating an example network device 1000 (e.g., a mobile device and / or processing device) as described herein. The network device 1000 may include control circuitry 1002 for controlling the functions of the network device 1000. Control circuitry 1002 may include one or more general-purpose processors, special-purpose processors, conventional processors, digital signal processors (DSPs), microprocessors, integrated circuits, programmable logic devices (PLDs), application-specific integrated circuits (ASICs), etc. Control circuitry 1002 may perform signal encoding, data processing, power control, image processing, input / output processing, and / or any other functions that enable the network device 1000 to perform as described herein.

[0222] The control circuit 1002 can store information in and / or retrieve information from the memory 1004. The memory 1004 may include non-removable memory and / or removable memory. Non-removable memory may include random access memory (RAM), read-only memory (ROM), hard disk, and / or any other type of non-removable memory storage device. Removable memory may include a user identity module (SIM) card, memory stick, memory card (e.g., a digital camera memory card), and / or any other type of removable memory.

[0223] Network device 1000 may include a camera 1006 capable of communicating with control circuitry 1002. The camera may include a digital camera or other optical device capable of generating images or videos (e.g., image sequences) for capture using visible light at network device 1000. The camera may include a light capable of flashing, modulating, or turning on / off in response to signals received from the control circuitry.

[0224] Network device 1000 may include a wireless communication circuit 1010 for wirelessly transmitting and / or receiving information. For example, the wireless communication circuit 1010 may include an RF transceiver for transmitting and receiving RF communication signals via antenna 1012, or other communication modules capable of performing wireless communication. The wireless communication circuit 1010 may communicate with control circuit 1002 to transmit information to and / or from control circuit 1002. For example, the wireless communication circuit 1010 may transmit information from control circuit 1002 via network communication signals. The wireless communication circuit 1010 may also transmit information received via network communication signals to control circuit 1002.

[0225] Network device 1000 may include a wireless communication circuit 1018 for wirelessly transmitting and / or receiving information. For example, wireless communication circuit 1018 may include an RF transceiver for transmitting and receiving RF communication signals via antenna 1017, or other communication modules capable of performing wireless communication. Wireless communication circuit 1018 may communicate with control circuit 1002 to transmit information to and / or from control circuit 1002. For example, wireless communication circuit 1018 may transmit information from control circuit 1002 via network communication signals. Wireless communication circuit 1018 may transmit information received via network communication signals to control circuit 1002. Wireless communication circuit 1018 may communicate via the same or different networks and / or protocols as wireless communication circuit 1010. For example, wireless communication circuit 1018 may communicate via a short-range RF protocol (e.g., NFC, BLE, or another short-range RF protocol), and wireless communication circuit 1010 may communicate via another RF network or protocol (e.g., proprietary protocol, WIFI, cellular, etc.).

[0226] The control circuit 1002 can also communicate with the display 1008. The display 1008 can provide information to the user in the form of graphics and / or text display. The control circuit 1002 can send signals to the display 1008 or parts thereof to modulate and / or turn the display on and / or off, thereby transmitting information from the display 1008. The communication between the display 1008 and the control circuit 1002 can be bidirectional, because the display 1008 may include a touchscreen module capable of receiving information from the user and providing such information to the control circuit 1002.

[0227] Network device 1000 may include actuator 1016. Control circuitry 1002 may receive user input in response to actuator 1016. For example, control circuitry 1002 may be operable to receive button presses from a user on network device 1000 to make selections or perform other functions on network device 1000.

[0228] Network device 1000 may include optical transmitter 1020. As part of a claim and / or join process, optical transmitter 1020 may be used to transmit optical signals to one or more control devices (e.g., lighting control devices).

[0229] One or more modules within network device 1000 may be powered by power supply 1014. For example, power supply 1014 may include an AC power supply or a DC power supply. Power supply 1014 may generate a DC supply voltage V. CC This is used to power the modules within the network device 1000.

[0230] Figure 11 This is a block diagram of an example system controller 1100. System controller 1100 may include control circuitry 1110, which may include one or more of a processor (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 suitable processing device. Control circuitry 1110 may perform signal encoding, data processing, image processing, power control, input / output processing, and / or any other function that enables system controller 1100 to perform as described herein. System controller 1100 may include wired communication circuitry 1112, which may be coupled to, for example, an Ethernet jack. Wired communication circuitry 1112 may be adapted to connect to a wired digital communication link (e.g., an Ethernet communication link) to allow control circuitry 1110 to communicate with network communication devices on the network. Wired communication circuitry 1112 may be configured to wirelessly connect to a network, for example, using Wi-Fi technology to transmit and / or receive network communication signals.

[0231] System controller 1110 may include wireless communication circuitry 1116, for example, including an RF transceiver coupled to an antenna for transmitting and / or receiving RF communication signals. Wireless communication circuitry 1116 may communicate using a network or protocol different from that of wired communication circuitry 1112, for example, proprietary protocols (e.g., [example protocol name]). (Protocol). Control circuit 1110 may be coupled to wireless communication circuit 1116 for transmitting messages via RF communication signals, for example, to control the load control device in response to messages received via wired communication circuit 1112. Control circuit 1110 may be configured to receive messages, for example, from the load control device and / or other control source devices.

[0232] Control circuitry 1110 may receive user input in response to actuator 1120. For example, control circuitry 1110 may be operable to associate system controller 1100 with one or more devices of a load control system in response to actuation of actuator 1120. System controller 1100 may include additional actuators that control circuitry 1110 may respond to.

[0233] Control circuitry 1110 may store information in and / or retrieve information from memory 1118. Memory 1118 may include non-removable memory and / or removable memory for storing computer-readable media. Non-removable memory may include random access memory (RAM), read-only memory (ROM), hard disk, and / or any other type of non-removable memory storage device. Removable memory may include a user identity module (SIM) card, memory stick, memory card (e.g., a digital camera memory card), and / or any other type of removable memory. Control circuitry 1110 may access memory 1118 to obtain executable instructions and / or other information that can be used by system controller 1100. Control circuitry 1110 may store a device identifier of the device associated with system controller 1100 in memory 1118. Control circuitry 1110 may access instructions in memory 1118 for transmitting instructions and / or performing other functions described herein.

[0234] System controller 1100 may include methods for generating DC supply voltage V CC The power supply 1124 is used to power the control circuitry 1110, wired communication circuitry 1112, wireless communication circuitry 1116, memory 1118, and / or other circuitry of the system controller 1100. The power supply 1124 may be coupled to a power supply connector 1126 (e.g., a USB port) to receive a supply voltage (e.g., DC voltage) and / or to draw current from an external power source.

[0235] Figure 12 This is a block diagram illustrating an example load control device 1200. The load control device 1200 can be a control target device, such as a lighting control device. The load control device 1200 can be a dimmer switch, an electronic switch, an electronic ballast for a lamp, an LED driver for an LED light source, or other load control device. The load control device 1200 may include communication circuitry 1202. Communication circuitry 1202 may include an RF receiver, an RF transceiver, or other communication module capable of performing wired and / or wireless communication. Wireless communication can be performed via antenna 1216.

[0236] The communication circuit 1202 can communicate with the control circuit 1204. The control circuit 1204 may include one or more general-purpose processors, special-purpose processors, conventional processors, digital signal processors (DSPs), microprocessors, integrated circuits, programmable logic devices (PLDs), application-specific integrated circuits (ASICs), etc. The control circuit 1204 can perform signal encoding, data processing, power control, input / output processing, or any other function that enables the load control device 1200 to perform as described herein.

[0237] Control circuitry 1204 may store information in memory 1206 and / or retrieve information therefrom. For example, memory 1206 may maintain an associated device identifier and / or a device database of executable instructions for execution as described herein. Memory 1206 may include non-removable memory and / or removable memory. Load control circuitry 1208 may receive instructions from control circuitry 1204 and may control electrical load 1210 based on the received instructions. Load control circuitry 1208 may receive power through live wire connection 1212 and neutral wire connection 1214 and may supply a certain amount of power to electrical load 1210. Electrical load 1210 may include a lighting load or any other type of electrical load.

[0238] Control circuit 1204 may receive information from occupancy sensor 1222. The information received from the occupancy sensor may include an indication of occupancy or vacancy status. Occupancy sensor 1222 may include an infrared (IR) sensor, a visible light sensor, or other sensors capable of detecting movement. Occupancy sensor may send an indication to control circuit 1204 in response to detecting movement (e.g., a major or minor movement event).

[0239] Control circuit 1204 can communicate with beacon transmitting circuit 1224 (e.g., short-range communication circuit) to transmit beacon messages. For example, beacon transmitting circuit 1224 can transmit beacon messages via RF communication signals. Beacon transmitting circuit 1224 can be a unidirectional or bidirectional communication circuit capable of receiving information on the same network and / or protocol used to transmit beacon messages. Information received at beacon transmitting circuit 1224 can be provided to control circuit 1204.

[0240] The control circuit 1204 can receive information from the visible light sensor 1226 (e.g., a camera). As part of the claim and / or join process, the visible light sensor 1226 can be used, for example, to receive light signals from a network device.

[0241] Control circuitry 1204 can illuminate visual indicator 1218 to provide feedback to the user. For example, control circuitry 1204 can cause visual indicator 1218 to flash or strobe to indicate an occupancy status identified by occupancy sensor 1222, i.e., that configuration mode has been entered, or to provide other feedback from load control device 1200. Control circuitry 1204 is operable to illuminate visual indicator 1218 in different colors. Visual indicator 1218 can be illuminated by, for example, one or more light-emitting diodes (LEDs). Load control device 1200 may include more than one visual indicator.

[0242] Figure 13 This is a block diagram illustrating an example control source device 1300 as described herein. Control source device 1300 may be a remote control device, an occupancy sensor, a visible light sensor, and / or another control source device. Control source device 1300 may include control circuitry 1302 for controlling the functions of control source device 1300. Control circuitry 1302 may include one or more general-purpose processors, special-purpose processors, conventional processors, digital signal processors (DSPs), microprocessors, integrated circuits, programmable logic devices (PLDs), application-specific integrated circuits (ASICs), etc. Control circuitry 1302 may perform signal encoding, data processing, power control, input / output processing, or any other function that enables control source device 1300 to perform as described herein.

[0243] The control circuit 1302 can store information in the memory 1304 and / or retrieve information from it. As described herein, the memory 1304 may include non-removable memory and / or removable memory.

[0244] The control source device 1300 may include communication circuitry 1308 for transmitting and / or receiving information. Communication circuitry 1308 may transmit and / or receive information via wired and / or wireless communication. Communication circuitry 1308 may include a transmitter, an RF transceiver, or other circuitry capable of performing wired and / or wireless communication. Communication circuitry 1308 may communicate with control circuitry 1302 for transmitting and / or receiving information.

[0245] Control circuitry 1302 can also communicate with input circuitry 1306. Input circuitry 1306 may include actuators (e.g., one or more buttons) or sensor circuitry (e.g., occupancy sensor circuitry, camera or other visible light sensing circuitry, etc.) for receiving input that can be sent to a device for controlling an electrical load. For example, a control source device may receive input from input circuitry 1306 to place control circuitry 1302 into a configuration mode and / or transmit associated messages from the control source device. Control circuitry 1302 may receive information from input circuitry 1306 (e.g., indication that a button has been actuated or information sensed). Each module within control source device 1300 may be powered by power supply 1310.

[0246] Although features and elements have been described above in specific combinations, features or elements may be used alone or in any combination with other features and elements. The programs described herein may be implemented in computer programs, software, or firmware incorporated in a computer-readable medium for execution by a computer or processor. Examples of computer-readable media include electronic signals (transmitted via wired or wireless connections) and computer-readable storage media. Examples of computer-readable storage media include, but are not limited to, read-only memory (ROM), random access memory (RAM), removable magnetic disks, and optical media such as CD-ROMs and DVDs.

Claims

1. A mobile device comprising: Processor, the processor being configured to: Transmit a first mobile device beacon message, including a first detection threshold, to one or more control devices; Receive one or more control device beacon messages transmitted by the control device in response to the first mobile device beacon message; The number of detected control devices is determined based on the received control device beacon messages; The number of discovered control devices is compared with a target range, wherein the target range is defined by a first target number of discovered control devices and a second target number of discovered control devices, wherein control device beacon messages are to be received from the plurality of control devices in response to the first mobile device beacon message; Determine that the number of control devices discovered is greater than a first target number within the target range or less than a second target number within the target range; The first discovery threshold is adjusted to a second discovery threshold based on the determination that the number of discovered control devices is greater than or less than the target range, wherein the first discovery threshold is configured to decrease to the second discovery threshold in response to determining that the number of discovered control devices is less than a second target number of the target range, and wherein the first discovery threshold is configured to increase to the second discovery threshold in response to determining that the number of discovered control devices is greater than a first target number of the target range. as well as Transmit a second mobile device beacon message that includes the second detection threshold.

2. The mobile device of claim 1, wherein the processor is further configured to: The further the number of detected control devices is from the target range, the larger the first detection threshold will be adjusted.

3. The mobile device of claim 1, wherein the processor is further configured to: In response to determining that the number of detected control devices is greater than a first target number within the target range, the first detection threshold is increased by a first threshold increment to a second detection threshold.

4. The mobile device of claim 1, wherein the processor is further configured to: The adjustment timer is initialized to an adjusted value to delay any further increase in the first detection threshold until the adjustment timer expires; and The first detection threshold is maintained until the adjustment timer expires.

5. The mobile device of claim 3, wherein the processor is further configured to: It is determined that the number of discovered control devices is greater than the third target number of discovered control devices, wherein the third target number of discovered control devices is less than the first target number of discovered control devices; and In response to determining that the number of detected control devices is greater than the third target number of detected control devices, the first detection threshold is increased by a second threshold increment less than the first threshold increment to a second detection threshold.

6. The mobile device of claim 1, wherein the processor is further configured to: In response to determining that the number of detected control devices is less than the second target number within the target range, the first detection threshold is reduced to the second detection threshold.

7. The mobile device of claim 6, wherein the processor is further configured to: It is determined that the number of discovered control devices is less than the third target number of discovered control devices, wherein the third target number of discovered control devices is greater than the first target number of discovered control devices; and In response to determining that the number of detected control devices is less than the third target number of detected control devices, the first detection threshold is reduced by a second threshold reduction less than the first threshold reduction to the second detection threshold.

8. A method for detecting a control device, performed by a mobile device, the method comprising: Transmit a first mobile device beacon message, including a first detection threshold, to one or more control devices; Receive one or more control device beacon messages transmitted by the control device in response to the first mobile device beacon message; The number of detected control devices is determined based on the received control device beacon messages; The number of discovered control devices is compared with a target range, wherein the target range is defined by a first target number of discovered control devices and a second target number of discovered control devices, wherein control device beacon messages are to be received from the plurality of control devices in response to the first mobile device beacon message; Determine that the number of control devices discovered is greater than a first target number within the target range or less than a second target number within the target range; The first discovery threshold is adjusted to a second discovery threshold based on the determination that the number of discovered control devices is greater than or less than the target range, wherein the first discovery threshold is configured to decrease to the second discovery threshold in response to determining that the number of discovered control devices is less than a second target number of the target range, and wherein the first discovery threshold is configured to increase to the second discovery threshold in response to determining that the number of discovered control devices is greater than a first target number of the target range. as well as Transmit a second mobile device beacon message that includes the second detection threshold.

9. The method of claim 8, further comprising: The further the number of detected control devices is from the target range, the larger the first detection threshold will be adjusted.

10. The method of claim 8, further comprising: In response to determining that the number of detected control devices is greater than a first target number within the target range, the first detection threshold is increased by a first threshold increment to the second detection threshold.

11. The method of claim 8, further comprising: The adjustment timer is initialized to an adjustment value to delay any further increase in the first detection threshold until the adjustment timer expires; as well as The first detection threshold is maintained until the adjustment timer expires.

12. The method of claim 10, further comprising: It is determined that the number of discovered control devices is less than the third target number of discovered control devices, wherein the third target number of discovered control devices is greater than the first target number of discovered control devices; as well as In response to determining that the number of detected control devices is greater than the third target number of detected control devices, the first detection threshold is increased by a second threshold increment less than the first threshold increment to the second detection threshold.

13. The method of claim 8, further comprising: In response to determining that the number of detected control devices is less than the second target number within the target range, the first detection threshold is reduced to the second detection threshold.

14. The method of claim 13, further comprising: It is determined that the number of discovered control devices is less than the third target number of discovered control devices, wherein the third target number of discovered control devices is greater than the first target number of discovered control devices; as well as In response to determining that the number of detected control devices is less than the third target number of detected control devices, the first detection threshold is reduced by a second threshold reduction less than the first threshold reduction to the second detection threshold.

15. The method of claim 8, wherein the first mobile device beacon message includes an entry discovery threshold greater than the first discovery threshold, and the second mobile device beacon message includes an exit discovery threshold less than the second discovery threshold, wherein the entry discovery threshold is configured by the control device to determine that the control device has entered the discovery range of the mobile device, and wherein the exit discovery threshold is configured by the control device to determine that the control device has exited the discovery range of the mobile device.

16. A load control system, comprising: A mobile device configured to transmit a first mobile device beacon message including a first detection threshold; as well as Control device, the control device being configured to: Receive the beacon message from the first mobile device; Based on the received signal strength when the first mobile device beacon message is received and the first detection threshold, the control device is determined to be within the detection range of the mobile device; and In response to the control device being within the detection range, a control device beacon message is transmitted; The mobile device is further configured to: Receive the control device beacon message transmitted by the control device in response to the first mobile device beacon message; The number of detected control devices is determined based on control device beacon messages received from multiple control devices, including the control device mentioned above. The number of discovered control devices is compared with a target range, wherein the target range is defined by a first target number of discovered control devices and a second target number of discovered control devices, wherein control device beacon messages are to be received from the plurality of control devices in response to the first mobile device beacon message; Determine that the number of control devices discovered is greater than a first target number within the target range or less than a second target number within the target range; The first discovery threshold is adjusted to a second discovery threshold based on the determination that the number of discovered control devices is greater than or less than the target range, wherein the first discovery threshold is configured to decrease to the second discovery threshold in response to determining that the number of discovered control devices is less than a second target number of the target range, and wherein the first discovery threshold is configured to increase to the second discovery threshold in response to determining that the number of discovered control devices is greater than a first target number of the target range. as well as Transmit a second mobile device beacon message that includes the second detection threshold.

17. The load control system of claim 16, wherein the moving device is further configured to: The further the number of detected control devices is from the target range, the larger the detection threshold will be adjusted.

18. The load control system of claim 16, wherein the moving device is further configured to: In response to determining that the number of detected control devices is greater than a first target number within the target range, the first detection threshold is increased by a first threshold increment to a second detection threshold.

19. The load control system of claim 16, wherein the moving device is further configured to: The adjustment timer is initialized to an adjusted value to delay any further increase in the first detection threshold until the adjustment timer expires; and The detection threshold is maintained until the adjustment timer expires.

20. The load control system of claim 18, wherein the moving device is further configured to: It is determined that the number of discovered control devices is greater than the third target number of discovered control devices, wherein the third target number of discovered control devices is less than the first target number of discovered control devices; and In response to determining that the number of detected control devices is greater than the third target number of detected control devices, the first detection threshold is increased by a second threshold increment less than the first threshold increment to a second detection threshold.

21. The load control system of claim 16, wherein the moving device is further configured to: In response to determining that the number of detected control devices is less than the second target number within the target range, the first detection threshold is reduced to the second detection threshold.

22. The load control system of claim 21, wherein the moving device is further configured to: It is determined that the number of discovered control devices is less than the third target number of discovered control devices, wherein the third target number of discovered control devices is greater than the first target number of discovered control devices; and In response to determining that the number of detected control devices is less than the third target number of detected control devices, the first detection threshold is reduced by a second threshold reduction less than the first threshold reduction to the second detection threshold.

23. The load control system of claim 16, wherein the control device is further configured to determine the control device within the detection range based on an entry detection threshold and an exit detection threshold.

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

25. The load control system of claim 24, wherein the control device is configured to determine that the control device includes the detection range, and the control device is configured to: Determine whether the control device is in configuration mode; The entry discovery threshold and the exit discovery threshold are calculated based on the received discovery threshold and one or more threshold offsets; as well as The received signal strength when the first mobile device beacon message is received is compared with the entry detection threshold.

26. The load control system as described in claim 24, wherein, The first mobile device beacon message includes one or more threshold offsets.

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

28. The load control system of claim 16, wherein the first mobile device beacon message includes an entry discovery threshold greater than the received discovery threshold, and the second mobile device beacon message includes an exit discovery threshold less than the second discovery threshold, and wherein the control device is further configured to: Based on the received signal strength when the first mobile device beacon message is received and the entry detection threshold, it is determined that the control device has entered the detection range of the mobile device. Receive the beacon message from the second mobile device; and Based on the received signal strength when the second mobile device beacon message is received and the exit detection threshold, it is determined that the control device has exited the detection range of the mobile device.

29. A load control system, comprising: A mobile device configured to transmit a mobile device beacon message including a discovery threshold; as well as Control device, the control device being configured to: Receive the beacon message from the first mobile device; Measure the strength of the received signal when the beacon message from the mobile device is received; Based on the received signal strength and the received detection threshold, the control device is determined to be within the detection range of the mobile device; In response to determining that the control device is within the detection range, a control device beacon message is transmitted; Receive beacon messages from the second mobile device; Measure the strength of the received signal when the beacon message from the second mobile device is received; Based on the received signal strength of the second mobile device beacon message and the received detection threshold, the control device is determined to be outside the detection range of the mobile device; as well as The control device continues to transmit beacon messages during the 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 detection range of the mobile device based on the received signal strength of the second mobile device beacon message, a threshold offset, and the received detection 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 the exit discovery threshold; and Based on the received signal strength of the second mobile device beacon message and the exit detection threshold, the control device determines that the mobile device is outside its detection range.

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 entry discovery threshold; and Based on the received signal strength and the entry detection threshold, the control device determines the detection range of the mobile device.

33. A load control system, comprising: A mobile device configured to transmit a first mobile device beacon message including a first detection threshold; as well as Control device, the control device being configured to: Receive the beacon message from the first mobile device; Based on the received signal strength when the first mobile device beacon message is received and the entry detection threshold that is greater than the first detection threshold, it is determined that the control device has entered the detection range of the mobile device. When the control device is within the detection range, it transmits a control device beacon message; Receive a second mobile device beacon message from the mobile device, the second mobile device beacon message including a second discovery threshold; as well as Based on the received signal strength when the second mobile device beacon message is received and the exit detection threshold which is less than the second detection threshold, it is determined that the control device has exited the detection range of the mobile device.

34. The load control system of claim 33, wherein the control device is further configured to: determine the entry discovery threshold by adding a first threshold offset to the first discovery threshold, and determine the exit 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 offset is equal to the second threshold offset.

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

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

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

39. The load control system of claim 33, wherein the control device is configured to determine that the control device includes the detection range, and the control device is configured to: Determine whether the control device is in configuration mode; Calculate one or more of the entry or exit thresholds based on the received discovery threshold and one or more threshold offsets; and The received signal strength when the first mobile device beacon message is received is compared with the entry discovery threshold or the exit 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 the configuration mode; The exit discovery threshold is calculated based on the received discovery threshold and one of the one or more threshold offsets; and The received signal strength when the first mobile device beacon message is received is compared with the exit discovery threshold.

41. The load control system of claim 39, wherein the control device is further configured to: It is determined that the control device is not in the configuration mode; The entry detection threshold is calculated based on the received detection threshold and one or more threshold offsets; and The received signal strength when the first mobile device beacon message is received is compared with the entry detection threshold.

42. The load control system of claim 33, wherein the moving device is further configured to: Receive the control device beacon message transmitted by the control device; The number of detected control devices is determined based on control device beacon messages received from multiple control devices, including the control device mentioned above. Compare the number of the discovered control devices with the target range; The detection threshold is adjusted based on whether the number of detected control devices is greater than or less than the target range; and Transmit a second mobile device beacon message that includes the adjusted detection threshold.

43. The load control system of claim 33, wherein the control device is further configured to: In response to the launch control beacon, a first feedback type is provided; Receive an indication that the control device has been selected for configuration; and In response to receiving the indication that the control device has been selected for configuration, a second feedback type is provided.

44. The load control system of claim 43, wherein the control device is further configured to: Receive an indication that the control device has been claimed; and In response to receiving the indication that the control device has been claimed, a third type of feedback is provided.

45. The load control system of claim 33, wherein the moving device is further configured to: Receive control device beacon messages transmitted by multiple control devices, including the aforementioned control device; Determine that the control device beacon message transmitted by the control device is received with the highest received signal strength; and A connection message is sent to the control device.

46. ​​The load control system of claim 45, wherein the control device beacon message includes a unique identifier associated with the control device, and wherein the mobile device is further configured to: It is determined that the mobile device is connected to the control device; Select the configuration identifier for the control device; Create an association between the unique identifier associated with the control device and the selected configuration identifier; and The association between the unique identifier associated with the control device and the selected configuration identifier is stored.

47. A control device comprising: A communication circuit configured to receive a first mobile device beacon message from a mobile device, including a first discovery threshold. as well as Control circuit, the control circuit being configured to: Instructions to receive the first mobile device beacon message from the communication circuit; Based on the received signal strength when the first mobile device beacon message is received and the entry detection threshold that is greater than the first detection threshold, it is determined that the control device has entered the detection range of the mobile device. When the control device is within the detection range, it transmits a control device beacon message; An indication to receive a second mobile device beacon message from the communication circuit, the second mobile device beacon message including a second discovery threshold; as well as Based on the received signal strength when the second mobile device beacon message is received and the exit detection threshold which is less than the second detection threshold, it is determined that the control device has exited the detection range of the mobile device.

48. The control device of claim 47, wherein the control device is configured to: determine the entry discovery threshold by adding a first threshold offset to the first discovery threshold, and determine the exit discovery threshold by subtracting a second threshold offset from the second discovery threshold.

49. The control device of claim 48, wherein the first threshold offset is equal to the second threshold offset.

50. The control device of claim 48, wherein the control device is configured to: receive the first threshold offset in the first mobile device beacon message, and receive the second threshold offset in the second mobile device beacon message.

51. The control device of claim 48, wherein the control device is configured to retrieve the first threshold offset and the second threshold offset from a memory.

52. The control device of claim 47, wherein the control device is configured to receive the entry discovery threshold in the first mobile device beacon message and the exit discovery threshold in the second mobile device beacon message.

53. The control device of claim 47, wherein the control device is configured to determine that the control device includes the detection range, and the control device is configured to: Determine whether the control device is in configuration mode; Calculate one or more of the entry or exit thresholds based on the received discovery threshold and one or more threshold offsets; and The received signal strength when the first mobile device beacon message is received is compared with the entry discovery threshold or the exit discovery threshold.

54. The control device of claim 53, wherein the control device is further configured to: Determine that the control device is in the configuration mode; The exit discovery threshold is calculated based on the received discovery threshold and one of the one or more threshold offsets; and The received signal strength when the first mobile device beacon message is received is compared with the exit discovery threshold.

55. The control device of claim 53, wherein the control device is further configured to: It is determined that the control device is not in the configuration mode; The entry detection threshold is calculated based on the received detection threshold and one or more threshold offsets; and The received signal strength when the first mobile device beacon message is received is compared with the entry detection threshold.

56. The control device of claim 47, wherein the communication circuitry is further configured to receive a second mobile device beacon message including a second detection threshold and one or more offsets, and wherein the control circuitry is further configured to: Instructions to receive the second mobile device beacon message from the communication circuit; Based on the received signal strength when the second mobile device beacon message is received, the second detection threshold, and at least one threshold offset among one or more threshold offsets, the control device is determined to be within the detection range of the mobile device. as well as In response to the control device being within the detection range, a second control device beacon message is transmitted.

57. The control device of claim 47, wherein the control circuit is further configured to: In response to transmitting the control device beacon message, control the electrical power supplied to one or more lighting loads of the lighting fixtures associated with the control device to provide a first feedback type; The communication circuit receives an indication that the control device has been selected for configuration. as well as In response to receiving the indication that the control device has been selected for configuration, the electrical force supplied to the one or more lighting loads is controlled to provide a second feedback type.

58. The control device of claim 57, wherein the control circuit is further configured to: The communication circuit receives an indication that the control device has been claimed; and In response to receiving the indication that the control device has been claimed, the electrical force supplied to the one or more lighting loads is controlled to provide a third type of feedback.

59. A method for detecting a control device, the method comprising: The control device receives a first mobile device beacon message including a first detection threshold. Based on the received signal strength when the first mobile device beacon message is received and the entry detection threshold that is greater than the received detection threshold, it is determined that the control device has entered the detection range of the mobile device. When the control device is within the detection range, it transmits a control device beacon message; The control device receives a second mobile device beacon message including a second detection threshold. as well as Based on the received signal strength when the second mobile device beacon message is received and the exit detection threshold which is less than the second detection threshold, it is determined that the control device has exited the detection range of the mobile device.

60. The method of claim 59, further comprising: The entry discovery threshold is determined by adding a first threshold offset to the first discovery threshold, and the exit discovery threshold is determined by subtracting a second threshold offset from the second discovery threshold.

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

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

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

64. The method of claim 59, wherein the first mobile device beacon message includes the entry discovery threshold, and wherein the second mobile device beacon message includes the exit discovery threshold.

65. The method of claim 59, wherein determining the control device within the detection range comprises: Determine whether the control device is in configuration mode; Calculate one or more of the entry or exit thresholds based on the received discovery threshold and one or more threshold offsets; and The received signal strength when the first mobile device beacon message is received is compared with the entry discovery threshold or the exit discovery threshold.

66. The method of claim 65, further comprising: Determine that the control device is in the configuration mode; The exit discovery threshold is calculated based on the received discovery threshold and one of the one or more threshold offsets; as well as The received signal strength when the first mobile device beacon message is received is compared with the exit discovery threshold.

67. The method of claim 65, further comprising: It is determined that the control device is not in the configuration mode; The entry detection threshold is calculated based on the received detection threshold and one of the one or more threshold offsets; as well as The received signal strength when the first mobile device beacon message is received is compared with the entry detection threshold.

68. The method of claim 59, further comprising: The control device receives a second mobile device beacon message including a second detection threshold and one or more offsets. Based on the received signal strength when the second mobile device beacon message is received, the second detection threshold, and at least one threshold offset among one or more threshold offsets, the control device is determined to be within the detection range of the mobile device. as well as In response to the control device being within the detection range, a second control device beacon message is transmitted.

69. The method of claim 59, further comprising: In response to transmitting the control device beacon message, control the electrical power supplied to one or more lighting loads of the lighting fixtures associated with the control device to provide a first feedback type; Receive an indication that the control device has been selected for configuration; as well as In response to receiving the indication that the control device has been selected for configuration, the electrical force supplied to the one or more lighting loads is controlled to provide a second feedback type.

70. The method of claim 69, further comprising: Receive an indication that the control device has been claimed; as well as In response to receiving the indication that the control device has been claimed, the electrical force supplied to the one or more lighting loads is controlled to provide a third type of feedback.

71. A load control system, comprising: A mobile device configured to transmit a first mobile device beacon message including a first detection threshold; as well as Multiple control devices, wherein each of the multiple control devices is configured to: Receive the beacon message from the first mobile device; Based on the received signal strength when the first mobile device beacon message is received and the first detection threshold, the control device is determined to be within the detection range of the mobile device; and In response to the control device being within the detection range, a control device beacon message is transmitted; The mobile device is further configured to: Receive the control device beacon message transmitted by the plurality of control devices in response to the first mobile device beacon message; The number of detected control devices is determined based on the received control device beacon messages; The number of discovered control devices is compared with a target range, wherein the target range is defined by a first target number of discovered control devices and a second target number of discovered control devices, wherein control device beacon messages are to be received from the plurality of control devices in response to the first mobile device beacon message; Determine that the number of control devices discovered is greater than a first target number within the target range or less than a second target number within the target range; The first discovery threshold is adjusted to a second discovery threshold based on the determination that the number of discovered control devices is greater than or less than the target range, wherein the first discovery threshold is configured to decrease to the second discovery threshold in response to determining that the number of discovered control devices is less than a second target number of the target range, and wherein the first discovery threshold is configured to increase to the second discovery threshold in response to determining that the number of discovered control devices is greater than a first target number of the target range. as well as Transmit a second mobile device beacon message that includes the second detection threshold.

72. The load control system of claim 71, wherein the moving device is further configured to: The further the number of detected control devices is from the target range, the larger the first detection threshold will be adjusted.

73. The load control system of claim 71, wherein the moving device is further configured to: In response to determining that the number of detected control devices is greater than a first target number within the target range, the first detection threshold is increased by a first threshold increment to the second detection threshold.

74. The load control system of claim 71, wherein the moving device is further configured to: The adjustment timer is initialized to an adjusted value to delay any further increase in the first detection threshold until the adjustment timer expires; and The first detection threshold is maintained until the adjustment timer expires.

75. The load control system of claim 73, wherein the moving device is further configured to: It is determined that the number of discovered control devices is greater than the third target number of discovered control devices, wherein the third target number of discovered control devices is less than the first target number of discovered control devices; and In response to determining that the number of detected control devices is greater than the third target number of detected control devices, the first detection threshold is increased by a second threshold increment less than the first threshold increment to the second detection threshold.

76. The load control system of claim 71, wherein the moving device is further configured to: In response to determining that the number of detected control devices is less than the second target number within the target range, the first detection threshold is reduced to the second detection threshold.

77. The load control system of claim 76, wherein the moving device is further configured to: It is determined that the number of discovered control devices is less than the third target number of discovered control devices, wherein the third target number of discovered control devices is greater than the first target number of discovered control devices; and In response to determining that the number of detected control devices is less than the third target number of detected control devices, the first detection threshold is reduced by a second threshold reduction less than the first threshold reduction to the second detection threshold.

78. The load control system of claim 71, wherein each of the plurality of control devices is further configured to determine the control device within the detection range based on an entry detection threshold and an exit detection threshold.

79. The load control system of claim 78, wherein each of the plurality of control devices is configured to determine the entry discovery threshold and the exit discovery threshold based on the received discovery threshold and one or more threshold offsets.

80. The load control system of claim 79, wherein each of the plurality of control devices is configured to determine that it includes each of the plurality of control devices within the detection range, and each control device is configured to: Determine whether the control device is in configuration mode; The entry discovery threshold and the exit discovery threshold are calculated based on the received discovery threshold and one or more threshold offsets; as well as The received signal strength when the first mobile device beacon message is received is compared with the entry detection threshold.

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

82. The load control system of claim 79, wherein the one or more threshold offsets are pre-stored in the corresponding memory of each of the plurality of control devices.

83. The load control system of claim 71, wherein the first mobile device beacon message includes an entry discovery threshold greater than the received discovery threshold, and the second mobile device beacon message includes an exit discovery threshold less than the second discovery threshold, and wherein each of the plurality of control devices is further configured to: Based on the received signal strength when the first mobile device beacon message is received and the entry detection threshold, it is determined that the control device has entered the detection range of the mobile device. Receive the beacon message from the second mobile device; and Based on the received signal strength when the second mobile device beacon message is received and the exit detection threshold, it is determined that the control device has exited the detection range of the mobile device.

84. The load control system of claim 71, wherein each of the plurality of control devices is configured to: Receive beacon messages from the second mobile device; Measure the strength of the received signal when the beacon message from the second mobile device is received; Based on the received signal strength of the second mobile device beacon message and the received detection threshold, the control device is determined to be outside the detection range of the mobile device; as well as The control device continues to transmit beacon messages during the discovery period.

85. The load control system of claim 83, wherein each of the plurality of control devices is further configured to: determine that the control device is outside the detection range of the mobile device based on the received signal strength magnitude, threshold offset, and received detection threshold of the second mobile device beacon message.

86. A non-transitory computer-readable storage medium having stored thereon program instructions that, when executed by a control circuit, cause the control circuit to perform the method of any one of claims 8-15.

87. A mobile device comprising: Control circuit; as well as A memory coupled to the control circuit for storing instructions that, when executed from the memory, cause the control circuit to perform the method of any one of claims 8-15.

88. A mobile device comprising components for performing the method of any one of claims 8-15.

89. A non-transitory computer-readable storage medium having stored program instructions thereon, which, when executed by a control circuit, cause the control circuit to perform the method of any one of claims 59-70.

90. A control device comprising: Control circuit; as well as A memory coupled to the control circuit for storing instructions that, when executed from the memory, cause the control circuit to perform the method of any one of claims 59-70.

91. A control device comprising components for performing the method of any one of claims 59-70.

Images