Controlling groups of electrical loads
Summary by NHIP
Load Control System with Status Query
The system includes lighting devices and a remote control device that identifies an actuation to toggle power states. Upon actuation, the remote device transmits a status query message to identify current on/off states before sending control digital messages to the group.
Claim Score by NHIP
Abstract
A load control system may include control devices for controlling electrical loads. The control devices may include load control devices, such as a lighting device for controlling an amount of power provided to a lighting load, and controller devices, such as a remote control device configured to transmit digital messages for controlling the lighting load via the load control device. The remote control device may communicate with the lighting devices via a hub device. The remote control device may detect a user interface event, such as a button press or a rotation of the remote control device. The remote control device or the hub device may determine whether to transmit digital messages as unicast messages or multicast messages based on the type of user interface event detected. The remote control device, or other master device, may synchronize and/or toggle an on/off state of lighting devices in the load control system.

Term
11.1 yearsleft in the term
Expires 20 October 2037.
- Priority and filed
- Granted
- Today
- Expires
20 claims: 3 independent, 17 dependent
- 1A load control system comprising:a group of lighting devices configured to control an amount of power provided to respective lighting loads;and a remote control device configured to: identify an actuation on the remote control device, wherein the actuation is configured to toggle an on/off state of the lighting devices;transmit a status query message for the on/off state to at least one lighting device of the group of lighting devices in response to the actuation to identify the on/off state of the at least one lighting device prior to controlling one or more lighting devices in the group of lighting devices;receive a status message from the at least one lighting device of the group of lighting devices, wherein the status message indicates a respective on/off state of the at least one lighting device;and transmit a digital message configured to control the on/off state of the one or more lighting devices in the group of lighting devices.
- 12A load control system comprising:a group of lighting devices configured to control an amount of power provided to respective lighting loads;and a remote control device configured to toggle an on/off state of the group of lighting devices by sending on commands and off commands, wherein the remote control device is configured to: identify a user interface event for toggling the on/off state of the group of lighting devices;transmit a default on command or a default off command to the group of lighting devices;determine that a state update message fails to be received in response to the default on command or the default off command after a predetermined period of time;and transmit an opposite command of the default on command or the default off command that was previously transmitted to the group of lighting devices.
- 17Broadest claimClaim Score 60, broad(NHIP)A load control system comprising:a group of lighting devices configured to control an amount of power provided to respective lighting loads;a remote control device configured to toggle an on/off state of the group of lighting devices;and a master device configured to: determine an on/off state of each lighting device in the group of lighting devices;store the on/off state of each lighting device in the group of lighting devices;receive a toggle command from the remote control device;determine, from the previously stored on/off state of the group of lighting devices, that the on/off state of the group of lighting devices are out of synchronization;and transmit, to the group of lighting devices, a command that is configured to synchronize the on/off state of the group of lighting devices.
Independent claims3
275 paragraphs in 5 sections, as filed
CROSS-REFERENCE TO RELATED APPLICATIONS
0001This application claims the benefit of U.S. Provisional Patent Application Nos. 62/411,286, filed Oct. 21, 2016, and 62/438,003, filed Dec. 22, 2016, the entire disclosures of which are incorporated by reference herein.
BACKGROUND
0002A user environment, such as a residence or an office building, for example, may be configured using various types of load control systems. A lighting control system may be used to control the lighting loads in a user environment. The lighting control system may include various devices, such as input devices and load control devices, capable of communicating via radio frequency (RF) communications. For example, a remote control device may be used to communicate with lighting devices (e.g., light bulbs) in the load control system to control the lighting level of the lighting devices. The devices may communicate in a network using RF communications, such as ZIGBEE® communications; BLUETOOTH® communications; or proprietary communications, such as CLEAR CONNECT™.
0003Lighting devices in the user environment may be collectively controlled by a common lighting control device that is capable of dimming the group of lighting devices or toggling the group of lighting devices on and off. One or more of the lighting devices in the system may be independently controlled by another lighting control device. This independent control of a subset of the lighting devices may cause some of the lighting devices to become out of sync with the rest of the group, such that some of the lighting control devices are turned “on,” while others are turned “off.” When the common lighting control device is actuated by a user to toggle the entire group of lighting devices (e.g., from on to off, or vice versa), the lighting devices that are out of sync with the others will remain out of sync. Each of the lighting devices will receive a multicast message that causes the lighting device to toggle from on to off or vice versa, such that the lighting devices that are in an “on” will be turned “off” and the lighting devices that are “off” will be turned “on.” To get the lighting devices in the entire group back in sync, the user may be required to independently control the lighting devices that are out of sync.
0004The control device that is used for controlling the lighting devices may also be capable of controlling other types of electrical loads and/or load control devices in the user environment. Different types of electrical loads and load control devices may be controlled very differently. For example, lighting devices may be dimmed, HVAC systems may control temperature, motorized window treatments may be raised and lowered, etc. As many different types of electrical loads and/or load control devices may be controlled in the user environment, the status of these electrical loads and/or load control devices may be helpful for performing user control within the user environment. The status of the electrical loads and/or load control devices may not be easily determined from a single status indicator that is universal for the various types of electrical loads. Thus, a default indicator may cause confusion to the end user as to the actual status of an electrical load or load control device being controlled thereby.
SUMMARY
0005As described herein, a remote control device may communicate with load control devices for controlling electrical loads (e.g., lighting devices, such as controllable lamps) using techniques to ensure that the electrical loads are controlled in a quick and organized manner. The remote control device may be configured to transmit wireless signals for synchronizing the state (e.g., the on/off state) and/or the intensities of multiple lighting devices. For example, the lighting devices may be controlled in response to an actuation of a toggle button of the remote control device in a manner that attempts to synchronize all of the lighting devices to the on state or the off state. In addition, the lighting devices may be controlled to the same lighting intensity levels in response to an actuation of an intensity adjustment actuator (e.g., rotations of a rotary knob) of the remote control device. Further, the remote control device may be configured to determine visual feedback to display on a status indicator (e.g., visual feedback of the intensity level of the lighting devices) using information regarding the lighting devices associated with the remote control device.
0006The remote control device may be a retrofit remote control device capable of being mounted over a toggle actuator of a wall-mounted mechanical switch (e.g., a light switch) that is controlling the power delivered to one or more of the lighting devices. The remote control device may transmit a command to the lighting devices (e.g., directly to the lighting devices) in response an actuation of a button of the remote control device (e.g., a toggle actuator or an intensity adjustment actuator). The remote control device may communicate with the lighting device via an intermediary device, e.g., a master device, such as a hub device or a designated one of the lighting devices. The master device may communicate with the lighting device and the remote control device via the same or different protocols. The master device may transmit a command to the lighting devices in response to an actuation of one of the buttons of the remote control device.
0007The remote control device may be a part of a load control system that may include a plurality of load control devices for directly controlling electrical power supplied to electrical loads, and controllers configured to transmit commands or signals to the load control devices to cause the load control devices to control the electrical loads. The load control devices may include a lighting device for controlling an amount of power provided to a lighting load, an audio device for controlling a speaker, a thermostat for controlling a setpoint temperature of a heating, ventilation, and air conditioning (HVAC) system, a motorized window treatment, or other similar load control devices which control electrical loads in a system. The controllers may include remote control devices or sensor devices, such as occupancy sensors, daylight sensors, etc.
0008The remote control device may be battery-powered. The remote control device may be configured to enter a sleep state after a period of inactivity (e.g., after a timeout period since a last actuation of a button of the remote control device). While in the sleep state, the remote control device may not be able to monitor the states of the lighting devices, which may be controlled by other devices. The remote control device may exit the sleep state in response to a user interface event (e.g., an actuation of one of the buttons). The user interface event may be a button press, a button hold, a rotation of the remote control device, or a portion thereof, by a defined amount, a soft button press, a finger swipe, etc., or any combination of these. The remote control may transmit digital messages via the wireless signals to the lighting devices and/or may illuminate the status indicator to display the visual feedback of the intensity level of the lighting devices after exiting the sleep state. The remote control device or the hub device may determine the digital messages to transmit based on the type of user interface event detected.
0009After waking up from the sleep state in response to an actuation of the toggle actuator, the remote control device may transmit (e.g., immediately transmit) a command (e.g., a synchronization command), such as an “on” command or an “off” command, to the lighting devices. The remote control device may determine which of the “on” command or the “off” command based on a pre-stored command and/or a stored state of the lighting devices. For example, if the remote control device has an off state stored in memory for the lighting devices, the remote control device may transmit an “on” command to the lighting devices upon waking from the sleep state. If the remote control device determines that no lighting devices have changed state in response to the transmitted command (e.g., the lighting devices were already in the state identified by the transmitted command), the remote control device may then transmit the opposite command to the lighting devices. For example, if the remote control device transmitted an “on” command to the lighting devices, but determined that no lighting devices changed state, the remote control device may transmit an “off” command to the lighting devices. The remote control device may update the pre-stored command and/or the stored state of the lighting devices whenever the remote control device has determined that the lighting devices have changed state in response to a transmitted command.
0010In another example, after waking up from the sleep state in response to an actuation of the toggle actuator, the remote control device may transmit (e.g., immediately transmit) a query message to request the present status (e.g., preset on/off state) of each of the lighting devices. When at least one response to the query message is received from the lighting devices (e.g., from at least one lighting device), the remote control may transmit an “on” command or an “off” command to the lighting devices. For example, the remote control device may determine which of the “on” command or the “off” command to transmit to the lighting devices based on the on/off state included in first response to the query message that is received.
0011When the remote control device is communicating with a master device (e.g., the hub device), the master device may determine which of the “on” command or the “off” command to transmit to the lighting devices in response to the actuation of the toggle actuator of the remote control device (e.g., to synchronize and/or toggle lighting devices).
0012After waking up from the sleep state in response to a rotation of the intensity adjustment actuator (e.g., the rotary knob), the remote control device may transmit (e.g., immediately transmit) a query message to request the present status (e.g., preset intensity level) of each of the lighting devices. When at least one response to the query message is received from the lighting devices (e.g., from at least one lighting device), the remote control may transmit a “move-to-level” command to the lighting devices. For example, the remote control device may determine the intensity level of the “move-to-level” command (e.g., the intensity level to which to control the lighting devices) based on the intensity level included in first response to the query message that is received. In response to a rotation of the rotary knob to increase the intensity levels of the lighting devices (e.g., a clockwise rotation), the remote control device may set the intensity level of the “move-to-level” command to the intensity level from the received response to the query plus an offset that may be dependent upon the amount of rotation of rotary knob since the beginning of the rotation. In response to a rotation of the rotary knob to decrease the intensity levels of the lighting devices (e.g., a counterclockwise rotation), the remote control device may set the intensity level of the “move-to-level” command to the intensity level from the received response to the query minus an offset that may be dependent upon the amount of rotation of rotary knob since the beginning of the rotation. Thus, the remote control device may determine a dynamic starting point for each new rotation of the rotary knob, e.g., from the intensity level included in first response to the query message that is received. The remote control device may determine an intensity level to display as feedback on the visible indicator in response to the intensity level included in first response to the query message that is received.
0013The remote control device or the master device may synchronize and/or toggle lighting devices in a load control system. A group of lighting devices may be controlled by a common controller device, such as the remote control device. A subset of the group of lighting devices may be independently controlled by other controller devices. The subset of the group of lighting devices may be controlled such that an on/off state of the subset of lighting devices is out of sync with the group of lighting devices having the common controller device. For example, the subset of lighting devices may be independently toggled to the opposite on/off state. The remote control device or the hub device may identify a toggle event to toggle the group of lighting devices and may synchronize and/or toggle lighting devices in a load control system. For example, a toggle event may be identified at the remote control device and the remote control device or the hub device may send a synchronization message to the subset of devices that are out of sync with the rest of the group. After the on/off state of the group of lighting devices have been synchronized, the group of lighting devices may be toggled in response to the toggle event.
BRIEF DESCRIPTION OF THE DRAWINGS
0014<figref idref="DRAWINGS">FIGS. 1A and 1B</figref> depict examples of a load control system that may implement one or more message types for communicating digital messages.
0015<figref idref="DRAWINGS">FIGS. 2A and 2B</figref> are system flow diagrams depicting example message flows for communicating digital messages between a remote control device and lighting devices in a load control system.
0016<figref idref="DRAWINGS">FIGS. 3A-3D</figref> are system flow diagrams depicting example message flows for querying for a current status of lighting devices and generating lighting control commands in response to the identified status.
0017<figref idref="DRAWINGS">FIGS. 4A and 4B</figref> are system flow diagrams depicting example message flows for communicating digital messages in a load control system that implements a hub device.
0018<figref idref="DRAWINGS">FIG. 5A</figref> is a flowchart depicting an example method for synchronizing and/or toggling lighting devices in a load control system.
0019<figref idref="DRAWINGS">FIG. 5B</figref> is a flowchart depicting an example method for synchronizing and/or toggling lighting devices in a load control system.
0020<figref idref="DRAWINGS">FIG. 6</figref> is a flowchart depicting an example method for synchronizing and/or toggling lighting devices in a load control system.
0021<figref idref="DRAWINGS">FIG. 7</figref> is a flowchart depicting an example method for synchronizing and/or toggling lighting devices in a load control system.
0022<figref idref="DRAWINGS">FIG. 8</figref> is a flowchart depicting an example method for synchronizing and/or toggling lighting devices in a load control system
0023<figref idref="DRAWINGS">FIG. 9</figref> is a flowchart depicting an example method for toggling lighting devices and/or sending state update messages in a load control system.
0024<figref idref="DRAWINGS">FIG. 10</figref> is a flowchart depicting an example method for synchronizing and/or toggling lighting devices in a load control system.
0025<figref idref="DRAWINGS">FIGS. 11A-11D</figref> are front views of a remote control device with a status indicator (e.g., a visual indicator) that may be illuminated to provide feedback (e.g., visual feedback).
0026<figref idref="DRAWINGS">FIG. 12</figref> is a graph that shows an example plot of the intensity of the status indicator in order to generate an animation.
0027<figref idref="DRAWINGS">FIGS. 13-20</figref> are front views of a remote control device with a status indicator that may be illuminated to provide feedback.
0028<figref idref="DRAWINGS">FIG. 21</figref> is a flowchart depicting an example method for determining the type of feedback to be provided on a status indicator of a remote control device.
0029<figref idref="DRAWINGS">FIG. 22</figref> is another flowchart depicting an example method for determining the type of feedback to be provided on a status indicator of a remote control device.
0030<figref idref="DRAWINGS">FIG. 23</figref> is a block diagram of an example load control device.
0031<figref idref="DRAWINGS">FIG. 24</figref> is a block diagram of an example controller device.
0032<figref idref="DRAWINGS">FIG. 25</figref> is a block diagram of an example network device.
0033<figref idref="DRAWINGS">FIG. 26</figref> is a block diagram of an example hub device.
DETAILED DESCRIPTION
0034<figref idref="DRAWINGS">FIGS. 1A and 1B</figref> depict examples of a load control system <b>100</b> that may implement one or more message types for communicating messages (e.g., digital messages). As shown in <figref idref="DRAWINGS">FIG. 1A</figref>, the load control system <b>100</b> may include various control devices, such as controller devices and/or load control devices. The controller device may send digital messages to the load control device to cause the load control device to control an amount of power provided from an AC power source <b>102</b> to an electric load in the load control system <b>100</b>.
0035Load control devices may control the electrical loads within a room and/or a building. Each load control device may be capable of directly controlling the amount of power provided to an electrical load in response to communication from a controller device. Example load control devices may include lighting devices <b>112</b><i>a</i>, <b>112</b><i>b </i>and/or lighting device <b>122</b> (e.g., a load control device in light bulbs, ballasts, LED drivers, etc.). The lighting devices may be a lighting load itself, or a device that includes the lighting load and a lighting load controller.
0036A controller device may indirectly control the amount of power provided to an electrical load by transmitting digital messages to the load control device. The digital messages may include control instructions (e.g., load control instructions) or another indication that causes the load control device to determine load control instructions for controlling an electrical load. Example controller devices may include a remote control device <b>116</b>. The controller devices may include a wired or wireless device.
0037Control devices (e.g., controller devices and/or load control devices) may communicate with each other and/or other devices via wired and/or wireless communications. The control devices may communicate using digital messages in a wireless signal. For example, the control devices may communicate via radio frequency (RF) signals <b>106</b>. The RF signals <b>106</b> may be communicated via an RF communication protocol (e.g., ZIGBEE®; near field communication (NFC); BLUETOOTH®; WI-FI®; a proprietary communication protocol, such as CLEAR CONNECT™, etc.). The digital messages may be transmitted as multicast messages and/or unicast messages via the RF signals <b>106</b>.
0038The lighting device <b>122</b> may be installed in a plug-in device <b>124</b>, such as a lamp (e.g., a table lamp). The plug-in device <b>124</b> may be coupled in series electrical connection between the AC power source <b>102</b> and the lighting device <b>122</b>. The plug-in device <b>124</b> may be plugged into an electrical receptacle <b>126</b> that is powered by the AC power source <b>102</b>. The plug-in device <b>124</b> may be plugged into the electrical receptacle <b>126</b> or a separate plug-in load control device that is plugged into the electrical receptacle <b>126</b> and configured to control the power delivered to the lighting device <b>122</b>.
0039The lighting devices <b>112</b><i>a</i>, <b>112</b><i>b </i>may be controlled by a wall-mounted load control device <b>110</b>. Though the lighting devices <b>112</b><i>a</i>, <b>112</b><i>b </i>are shown in <figref idref="DRAWINGS">FIG. 1A</figref>, any number of lighting devices may be implemented that may be supported by the wall-mounted load control device <b>110</b> and/or the AC power source <b>102</b>. The wall-mounted load control device <b>110</b> may be coupled in series electrical connection between the AC power source <b>102</b> and lighting devices <b>112</b><i>a</i>, <b>112</b><i>b</i>. The wall-mounted load control device <b>110</b> may include a mechanical switch <b>111</b> (e.g., a previously-installed light switch) that may be opened and closed in response to actuations of a toggle actuator (not shown) for controlling the power delivered from the AC power source <b>102</b> to the lighting devices <b>112</b><i>a</i>, <b>112</b><i>b </i>(e.g., for turning on and off the lighting devices <b>112</b><i>a</i>, <b>112</b><i>b</i>). The lighting devices <b>112</b><i>a</i>, <b>112</b><i>b </i>may be installed in respective ceiling mounted downlight fixtures <b>114</b><i>a</i>, <b>114</b><i>b </i>or other lighting fixture mounted to another surface. The wall-mounted load control device <b>110</b> may be adapted to be wall-mounted in a standard electrical wallbox.
0040The remote control device <b>116</b> may be configured to transmit messages via the RF signals <b>106</b> for controlling the lighting devices <b>112</b><i>a</i>, <b>112</b><i>b</i>. The remote control device <b>116</b> may be a retrofit remote control device mounted over the toggle actuator of the mechanical switch <b>111</b>. The remote control device <b>116</b> may be configured to maintain the toggle actuator of the mechanical switch <b>111</b>in the “on” position (e.g., by covering the switch when in the “on” position) to maintain the flow of power from the AC power source <b>102</b> to the lighting devices <b>112</b><i>a</i>, <b>112</b><i>b</i>. The remote control device <b>116</b> may comprise an actuation portion <b>117</b> that may be actuated (e.g., pushed in towards the mechanical switch <b>111</b>) and a rotation portion <b>118</b> (e.g., a rotary knob) that may be rotated (e.g., with respect to the mechanical switch <b>111</b>). Though a rotation portion <b>118</b> is disclosed, the remote control device <b>116</b> may include another type of intensity adjustment actuator, such as a linear slider, an elongated touch sensitive actuator, a rocker switch, separate raise/lower actuators, or another form of intensity adjustment actuator. The remote control device <b>116</b> may be battery-powered. In addition, the remote control device <b>116</b> may be mounted to another structure (e.g., other than the toggle actuator of the mechanical switch <b>111</b>), such a as wall, may be attached to a pedestal to be located on a horizontal surface, or may be handheld. Further, the wall-mounted load control device <b>110</b> may comprise a wall-mounted remote control device that replaces the previously-installed mechanical switch <b>111</b> and may be configured to operate as the remote control device <b>116</b> to control the lighting devices <b>112</b><i>a</i>, <b>112</b><i>b </i>(e.g., by transmitting messages via the RF signals <b>106</b>). Such a wall-mounted remote control device may derive power from the AC power source <b>102</b>.
0041The lighting devices <b>112</b><i>a</i>, <b>112</b><i>b </i>may be turned on or off, or the intensity level may be adjusted, in response to the remote control device <b>116</b> (e.g., in response to actuations of the actuation portion <b>117</b> of the remote control device <b>116</b>). For example, the lighting devices <b>112</b><i>a</i>, <b>112</b><i>b </i>may be toggled on or off by a toggle event identified at the remote control device <b>116</b>. The toggle event may be a user event identified at the remote control device <b>116</b>. The actuation portion <b>117</b> of the remote control device <b>116</b> may be actuated to toggle the lighting devices <b>112</b><i>a</i>, <b>112</b><i>b </i>on or off. The rotation portion <b>118</b> of the remote control device <b>116</b> may be rotated to adjust the intensities of the lighting devices <b>112</b><i>a</i>, <b>112</b><i>b</i>. The toggle event may be identified when the rotation portion <b>118</b> of the remote control device <b>116</b> is turned by a predefined amount or for a predefined time, and/or the actuation portion <b>117</b> of the remote control device <b>116</b> is actuated. The lighting level of the lighting devices <b>112</b><i>a</i>, <b>112</b><i>b </i>may be increased or decreased by rotating the rotation portion <b>118</b> of the remote control device <b>116</b> in one direction or another, respectively. Though shown as comprising a rotary knob in <figref idref="DRAWINGS">FIGS. 1A and 1B</figref>, the remote control device <b>116</b> may comprise a paddle switch that may be actuated by a user, a linear control on which a user may swipe a finger, a raise/lower slider, a rocker switch, or another type of control capable of receiving user interface events as commands.
0042The remote control device <b>116</b> may provide feedback (e.g., visual feedback) to a user of the remote control device <b>116</b> on a visual indicator, such as a status indicator <b>119</b>. The status indicator <b>119</b> may provide different types of feedback. The feedback may include feedback indicating actuations by a user or other user interface event, a status of electrical loads being controlled by the remote control device <b>116</b>, and/or a status of the load control devices being controlled by the remote control device <b>116</b>. The feedback may be displayed in response to user interface event and/or in response to messages received that indicate the status of load control devices and/or electrical loads.
0043The status indicator <b>119</b> may include one or more light emitting diodes (LEDs) for providing feedback. The status indicator <b>119</b> may be a light bar included around the entire perimeter of the remote control device <b>116</b>, or a portion thereof. The status indicator <b>119</b> may also, or alternatively be a light bar in a line on the remote control device <b>116</b>, such as when the remote control device is a paddle switch or a linear control, for example.
0044Example types of feedback may include illumination of the entire status indicator <b>119</b> (e.g., to different levels), blinking or pulsing one or more LEDs in the status indicator <b>119</b>, changing the color of one or more LEDs on the status indicator <b>119</b>, and/or illuminating different sections of one or more LEDs in the status indicator <b>119</b> to provide animation (e.g., clockwise and counter clockwise animation for raising and lowering a lighting level). The feedback on the status indicator <b>119</b> may indicate a status of an electrical load or a load control device, such as a lighting intensity level for lights (e.g., lighting devices <b>112</b><i>a</i>, <b>112</b><i>b</i>, <b>122</b>), a volume level for audio devices, a shade level for a motorized window treatment, and/or a speed for fans or other similar types of devices that operate at different speeds. The feedback on the status indicator <b>119</b> may change based on the selection of different presets. For example, a different LED or LEDs may be illuminated on the status indicator <b>119</b> to identify different presets (e.g., preset intensity levels for the lighting devices <b>112</b><i>a</i>, <b>112</b><i>b</i>, <b>122</b> and/or other preset configurations for load control devices).
0045The status indicator <b>119</b>, or a portion thereof, may be turned on or off to indicate the status of one or more of the lighting devices <b>112</b><i>a</i>, <b>112</b><i>b</i>, <b>122</b>. For example, the status indicator <b>119</b> may be turned off to indicate that the lighting devices <b>112</b><i>a</i>, <b>112</b><i>b</i>, <b>122</b> are in an off state. The entire status indicator, or portion thereof, may be turned on to indicate that the lighting devices <b>112</b><i>a</i>, <b>112</b><i>b</i>, <b>122</b> are in the on state. The portion of the status indicator <b>119</b> that is turned on may indicate the intensity level of one or more of the lighting devices <b>112</b><i>a</i>, <b>112</b><i>b</i>, <b>122</b>. For example, when the lighting devices <b>112</b><i>a</i>, <b>112</b><i>b</i>, <b>122</b> are at a 50% intensity level, 50% of the status indicator <b>119</b> may be turned on to reflect the intensity level of the lighting devices <b>112</b><i>a</i>, <b>112</b><i>b</i>, <b>122</b>.
0046The remote control device <b>116</b> may provide simple feedback or advanced feedback to the user on the status indicator <b>119</b>. The remote control device <b>116</b> may decide between multiple types of advanced feedback or between multiple types of simple feedback. For example, this decision may be based on the type of load control device associated with the remote control device <b>116</b> (e.g., lights, HVAC, motorized window treatment, audio device, fan, etc.). The remote control device <b>116</b> may be configured to provide different type of visual feedback (e.g., different types of simple and advanced feedback) by adjusting the intensity and/or color of the illumination, changing the portions of the status indicator <b>119</b> that are illuminated, and providing different animations.
0047Simple feedback may be provided in response to actuations or other user interface event received at the remote control device <b>116</b>. For example, simple feedback may indicate to a user that the remote control device <b>116</b> is operating correctly (e.g., in response to an actuation of the toggle button or a rotation). The simple feedback may illuminate or blink one or more LEDs in response to a button press. The simple feedback may indicate that the remote control device <b>116</b>, or a button thereon, was actuated. The simple feedback may indicate that a command has been selected in response to user interface event. For example, the simple feedback may provide a blinking sequence in response to actuations of a toggle event. The simple feedback may provide a solid illumination of the status indicator <b>119</b> at different lighting levels in response to clockwise and counterclockwise rotations of the remote control device <b>116</b> (e.g., as shown in <figref idref="DRAWINGS">FIGS. 11C-11D</figref>). As the simple feedback may provide information that does not indicate the status of a load control device, the status indicator <b>119</b> may operate more as a visual indicator of other types of status or may not indicate a status of a device at all.
0048The remote control device <b>116</b> may provide advanced feedback based on knowledge of the state of a load control device, such that the feedback may provide the state information to the user. For example, rotations of the remote control device <b>116</b> can cause the visual feedback to track the light level of the lighting devices <b>112</b><i>a</i>, <b>112</b><i>b</i>, <b>122</b>. The light level may be stored in the remote control device <b>116</b> (e.g., if there is one remote control device assigned to lighting devices <b>112</b><i>a</i>, <b>112</b><i>b</i>, <b>122</b> and lighting devices <b>112</b><i>a</i>, <b>112</b><i>b</i>, <b>122</b> may be controlled as a group from the dedicated remote control device <b>116</b>) or may be received by remote control device <b>116</b> in response to query messages transmitted from the remote control device <b>116</b>. For advanced feedback in response to a user interface event, such as a toggle event, the lights on the status indicator <b>119</b> may increase from off to an on light level when turning on the lighting devices <b>112</b><i>a</i>, <b>112</b><i>b</i>, <b>122</b>, and decrease from the on light level to off when turning off the lighting devices <b>112</b><i>a</i>, <b>112</b><i>b</i>, <b>122</b>.
0049The decision on type of feedback provided by the status indicator <b>119</b> may be made at the time of association of the remote control device <b>116</b> and stored at the remote control device <b>116</b>. The decision on the type of feedback provided by the status indicator <b>119</b> may be made dynamically. For example, the type of feedback displayed via the status indicator <b>119</b> may change depending on the information determined in response to a query message sent to the lighting devices <b>112</b><i>a</i>, <b>112</b><i>b</i>, <b>122</b> or other load control devices. The query message may be sent in response to an actuation on the remote control device <b>116</b> and/or in response to a sensing circuit (e.g., an occupancy sensing circuit and/or a proximity sensing circuit) sensing an occupant near the remote control device <b>116</b>. The remote control device <b>116</b> may wake up in response to an actuation and ping associated lighting devices <b>112</b><i>a</i>, <b>112</b><i>b</i>, <b>122</b> or other load control devices to determine a status of the electrical loads controlled by the associated load control devices.
0050The remote control device <b>116</b> may operate to provide different types of feedback (e.g., advanced feedback or simple feedback) based on information about the associated devices. For example, the remote control device <b>116</b> may provide different feedback on the status indicator <b>119</b> when associated with a master device than when not associated with the master device. The master device may be one of the lighting devices <b>112</b><i>a</i>, <b>112</b><i>b</i>, <b>122</b> or another load control device. The remote control device <b>116</b> may provide advanced feedback on the status indicator <b>119</b> when associated with a master device that is capable of providing the status of load control devices to the remote control device <b>116</b>. The remote control device <b>116</b> may provide simple feedback on the status indicator <b>119</b> when not associated with a master device.
0051The remote control device <b>116</b> may provide different feedback on the status indicator <b>119</b> based on the number of load control devices associated with the remote control device <b>116</b>. For example, the remote control device <b>116</b> may provide different feedback on the status indicator <b>119</b> when a single lighting device <b>112</b><i>a </i>is associated with the remote control device <b>116</b> than when multiple lighting devices <b>112</b><i>a</i>, <b>112</b><i>b</i>, <b>122</b> are associated with the remote control device <b>116</b>. When a single load control device is associated with the remote control device <b>116</b>, the remote control device <b>116</b> may provide advanced feedback on the status indicator <b>119</b>. When multiple load control devices are associated with the remote control device <b>116</b>, the remote control device <b>116</b> may provide simple feedback on the status indicator <b>119</b>. Simple feedback may be provided when the remote control device <b>116</b> is associated with multiple load control devices, as the load control devices may be different types of devices may be currently controlled differently, may be at different levels (e.g., different intensity levels), and/or may be at levels that are unknown to the remote control device <b>116</b>.
0052The remote control device <b>116</b> may provide different feedback on the status indicator based on whether the loads of the associated load control devices are in sync. When the loads are in sync (e.g., the same status is received for the associated load control devices), the remote control device <b>116</b> may provide advanced feedback on the status indicator <b>119</b>. For example, in response to a toggle event or a rotation (e.g., a predefined distance or time in a direction) for controlling an intensity level of the lighting devices <b>112</b><i>a</i>, <b>112</b><i>b</i>, <b>122</b>, the remote control device <b>116</b> may awaken from a sleep state and query the lighting devices <b>112</b><i>a</i>, <b>112</b><i>b</i>, <b>122</b> for their current state. The remote control device <b>116</b> may receive the current state (e.g., on/off state, lighting level, color, etc.) of the lighting devices <b>112</b><i>a</i>, <b>112</b><i>b</i>, <b>122</b> and determine that the lighting devices <b>112</b><i>a</i>, <b>112</b><i>b</i>, <b>122</b> are in the same state. The status indicator <b>119</b> on the remote control device <b>116</b> may indicate the status of the lighting devices <b>112</b><i>a</i>, <b>112</b><i>b</i>, <b>122</b> that is received in response to the query message. While the remote control device <b>116</b> remains awake, the status indicator <b>119</b> may reflect the updated status of one or more of the lighting devices <b>112</b><i>a</i>, <b>112</b><i>b</i>, <b>122</b> as the status changes. After a predefined period of time, the remote control device <b>116</b> may return to the sleep state. The status indicator <b>119</b> may be turned off in the sleep state to conserve battery power.
0053When the loads are out of sync (e.g., a different status is received for the associated load control devices), the remote control device <b>116</b> may provide simple feedback or advanced feedback on the status indicator <b>119</b>. For example, in response to a toggle event or a rotation (e.g., a predefined distance or time in a direction) for controlling an intensity level of the lighting devices <b>112</b><i>a</i>, <b>112</b><i>b</i>, <b>122</b>, the remote control device <b>116</b> may awaken from a sleep state and query the lighting devices <b>112</b><i>a</i>, <b>112</b><i>b</i>, <b>122</b> for their current state. The status indicator <b>119</b> on the remote control device <b>116</b> may indicate the status of one or more of the lighting devices <b>112</b><i>a</i>, <b>112</b><i>b</i>, <b>122</b> that is received in response to the query message. When the status of the lighting devices <b>112</b><i>a</i>, <b>112</b><i>b</i>, <b>122</b> are in sync, the remote control device <b>116</b> may provide advanced feedback such that the status indicator <b>119</b> on the remote control device <b>116</b> indicate the intensity level at which all of the lighting devices <b>112</b><i>a</i>, <b>112</b><i>b</i>, <b>122</b> are operating.
0054When the status of the lighting devices <b>112</b><i>a</i>, <b>112</b><i>b</i>, <b>122</b> are out of sync, the remote control device <b>116</b> may provide simple feedback on the status indicator <b>119</b>. For example, the status indicator <b>119</b> on the remote control device <b>116</b> may reflect the current state of the lighting device <b>112</b><i>a</i>, <b>112</b><i>b</i>, <b>122</b> that is the first to respond to the query message, or the state of a particular lighting device <b>112</b><i>a</i>, <b>112</b><i>b</i>, <b>122</b> in the group. For example, in response to the query message for the current state of the lighting devices <b>112</b><i>a</i>, <b>112</b><i>b</i>, <b>122</b>, the lighting device <b>112</b><i>a </i>may respond first that it is at a 10% intensity level. The status indicator <b>119</b> on the remote control device <b>116</b> may reflect the current state of the lighting device <b>112</b><i>a </i>on the status indicator <b>119</b>. The group of lighting devices <b>112</b><i>a</i>, <b>112</b><i>b</i>, <b>122</b> may be the lighting devices that have been associated in memory with the remote control device <b>116</b>, or otherwise stored in memory with a group identifier for being controlled together.
0055When the status of the lighting devices <b>112</b><i>a</i>, <b>112</b><i>b</i>, <b>122</b> are out of sync, the status indicator <b>119</b> may provide advanced feedback that represents the status of the group of lighting devices <b>112</b><i>a</i>, <b>112</b><i>b</i>, <b>122</b>. For example, status indicator <b>119</b> may indicate the average intensity of the group of lighting devices <b>112</b><i>a</i>, <b>112</b><i>b</i>, <b>122</b> or the state of the majority of the lighting devices <b>112</b><i>a</i>, <b>112</b><i>b</i>, <b>122</b>. The status indicator <b>119</b> may provide advanced feedback to indicate the state of the group of lighting devices <b>112</b><i>a</i>, <b>112</b><i>b</i>, <b>122</b> by lighting the entire status indicator <b>119</b> when a majority of the lighting devices <b>112</b><i>a</i>, <b>112</b><i>b</i>, <b>122</b> are in the on state, turning the status indicator <b>119</b> off when the majority of the lighting devices <b>112</b><i>a</i>, <b>112</b><i>b</i>, <b>122</b> are in the off state, lighting a portion of the status indicator <b>119</b> that identifies an average lighting level of the group of lighting devices <b>112</b><i>a</i>, <b>112</b><i>b</i>, <b>122</b>, increasing an intensity of the status indicator <b>119</b> to a percentage that reflects the intensity of the lighting devices <b>112</b><i>a</i>, <b>112</b><i>b</i>, <b>122</b>, etc.
0056When the status of the lighting devices <b>112</b><i>a</i>, <b>112</b><i>b</i>, <b>122</b> are out of sync, the status indicator <b>119</b> may provide simple or advanced feedback that indicates that the lighting devices <b>112</b><i>a</i>, <b>112</b><i>b</i>, <b>122</b> are out of sync. For example, the remote control device <b>116</b> may provide simple feedback by making the entire status indicator <b>119</b> lit, unlit, or flash to indicate that the lighting devices <b>112</b><i>a</i>, <b>112</b><i>b</i>, <b>122</b> are out of sync. The remote control device <b>116</b> may provide advanced feedback by blinking or pulsing the status indicator <b>119</b> while displaying the average intensity level of the lighting devices <b>112</b><i>a</i>, <b>112</b><i>b</i>, <b>122</b>, by periodically transitioning the status indicator <b>119</b> between the intensity levels of the lighting devices <b>112</b><i>a</i>, <b>112</b><i>b</i>, <b>122</b>, or by periodically transitioning the status indicator <b>119</b> between maximum and minimum intensity levels of the lighting devices <b>112</b><i>a</i>, <b>112</b><i>b</i>, <b>122</b>. When the group of lighting devices <b>112</b><i>a</i>, <b>112</b><i>b</i>, <b>122</b> are out of sync, no feedback may be provided, a constant feedback indication may be provided, or feedback may be provided (e.g., flashing LEDs) that indicates that the group of lighting devices are out of sync.
0057The remote control device <b>116</b> may be configured to display feedback (e.g., simple feedback) in response to determining that one or more of the lighting devices <b>112</b><i>a</i>, <b>112</b><i>b</i>, <b>122</b> are “missing.” For example, the remote control device may be configured to blink the entire status indicator <b>119</b> (e.g., in a particular color, such as red) and/or provide an animation to indicate that one or more of the lighting devices <b>112</b><i>a</i>, <b>112</b><i>b</i>, <b>122</b> are missing. The remote control device <b>116</b> may be configured to determine that one of the lighting devices <b>112</b><i>a</i>, <b>112</b><i>b</i>, <b>122</b> is missing, for example, in response to not receiving a response to a query message transmitted to that particular lighting device. For example, one of the lighting devices <b>112</b><i>a</i>, <b>112</b><i>b</i>, <b>122</b> may be “missing” if that lighting device has been removed from its fixture or lamp (e.g., unscrewed), is unplugged, is faulty, the corresponding light switch is turned off (e.g., light switch in a series is turned off, while others are on), and/or has reached end of life.
0058The feedback provided by the status indicator <b>119</b> may be automatically or dynamically updated according to different feedback modes during operation of the remote control device <b>116</b>. For example, the status indicator <b>119</b> may provide different types of feedback based on the state of the lighting devices <b>112</b><i>a</i>, <b>112</b><i>b</i>, <b>122</b> and/or the number of lighting devices <b>112</b><i>a</i>, <b>112</b><i>b</i>, <b>122</b> that are associated with the remote control device <b>116</b>. The remote control device <b>116</b> may provide advanced feedback on the status indicator <b>119</b> that indicates an intensity level of one or more lighting devices as a portion of the entire status indicator <b>119</b>. The remote control device <b>116</b> may provide simple feedback that illuminates the entire status indicator <b>119</b>. The simple feedback may be provided to illuminate the entire status indicator <b>119</b> to indicate one or more lighting devices in a group are in an on state, turn off the status indicator <b>119</b> to indicate that one or more lighting devices in the group are in the off state, and/or illuminate the status indicator <b>119</b> to different levels when raising or lowering intensity of one or more lighting devices in the group. The operation of different feedback modes may allow for more granular feedback of an individual load control device with which the remote control device <b>116</b> is associated, while preventing confusion that may be caused by providing feedback of a single device when the remote control device <b>116</b> is associated with multiple load control devices that are out of sync.
0059The remote control device <b>116</b> may provide advanced feedback if the load control devices (e.g., lighting devices <b>112</b><i>a</i>, <b>112</b><i>b</i>, <b>122</b>) with which the remote control device <b>116</b> is associated are not associated with other remote control devices. The remote control device <b>116</b> may provide simple feedback if one or more of the load control devices (e.g., lighting devices <b>112</b><i>a</i>, <b>112</b><i>b</i>, <b>122</b>) with which the remote control device <b>116</b> is associated are also associated with other remote control devices. This may allow for more granular feedback of a group of individual load control devices with which the remote control device <b>116</b> is associated, while preventing continuous updating or confusion when other remote control devices are controlling the multiple load control devices (e.g., lighting devices <b>112</b><i>a</i>, <b>112</b><i>b</i>, <b>122</b>).
0060The remote control device <b>116</b> may transmit digital messages via the RF signals <b>106</b> to control the lighting devices <b>112</b><i>a</i>, <b>112</b><i>b</i>, <b>122</b>. The remote control device <b>116</b> may be configured to adjust the intensities of the lighting devices <b>112</b><i>a</i>, <b>112</b><i>b</i>, <b>122</b> using absolute control in order to control the intensities of the lighting devices <b>112</b><i>a</i>, <b>112</b><i>b</i>, <b>122</b> to an absolute level (e.g., a specific level). For example, the remote control device <b>116</b> may transmit digital messages including a move-to-level command (e.g., a go-to-level or go-to command) that identifies a lighting level to which the lighting devices may change. The move-to-level command may include the amount of time over which the lighting level may be changed at the lighting devices. The move-to-level command may indicate an “on” event or an “off” event to turn the lighting devices <b>112</b><i>a</i>, <b>112</b><i>b</i>, <b>122</b> on or off, respectively. For example, the “on” event may be indicated with a 100% lighting level, or another preset lighting level. The “off” event may be indicated with a 0% intensity level. The lighting level for the “on” event and/or the “off” event may also, or alternatively, be stored at the lighting devices <b>112</b><i>a</i>, <b>112</b><i>b</i>, <b>122</b> and the lighting devices may change to the lighting level upon receiving an indication of the occurrence of the “on” event or “off” event at the remote control device <b>116</b>. The digital messages may indicate an “on” event when the remote control device <b>116</b> is rotated a predefined distance or time in one direction. As an example, the remote control device <b>116</b> may transmit digital messages when the remote control device <b>116</b> is identified as being rotated for 100 milliseconds (ms). The digital messages may indicate an “off” event when the remote control device <b>116</b> is rotated a predefined distance or time in the opposite direction. The digital messages may indicate an “on” event or an “off” event when the remote control device <b>116</b> is pressed (e.g., when a button on the face of the remote control device is pressed or the remote control device <b>116</b> is pressed in). The “on” event or “off” event may be indicated in a digital message with a toggle command that indicates for the lighting devices <b>112</b><i>a</i>, <b>112</b><i>b</i>, <b>122</b> to toggle from “on” to “off,” or vice versa.
0061In response to a user interface event (e.g., actuation, rotation, finger swipe, etc.) or a proximity sensing event (e.g., a sensing circuit sensing an occupant near the remote control device <b>116</b>) at the remote control device <b>116</b>, the remote control device <b>116</b> may determine a starting point (e.g., a dynamic starting point) from which the lighting level of one or more of the lighting devices <b>112</b><i>a</i>, <b>112</b><i>b</i>, <b>122</b> may be controlled. Each rotation of the rotation portion <b>118</b> may cause the remote control device <b>116</b> to determine the dynamic starting point from which control may be performed. In response to the user interface event and/or a proximity sensing event (e.g., a sensing circuit sensing an occupant near the remote control device <b>116</b>), the remote control device <b>116</b> may query the lighting devices <b>112</b><i>a</i>, <b>112</b><i>b</i>, <b>122</b> for a current status (e.g., after awakening from sleep mode). The current status of one or more of the lighting devices <b>112</b><i>a</i>, <b>112</b><i>b</i>, <b>122</b> may be used to set the dynamic starting point from which the remote control device <b>116</b> may perform control. For example, the remote control device <b>116</b> may set the dynamic starting point of the rotation portion <b>118</b> to the current intensity level (e.g., on, off, 10%, 20%, etc.) of the first of the lighting devices <b>112</b><i>a</i>, <b>112</b><i>b</i>, <b>122</b> to respond to the query, or a predefined lighting device <b>112</b><i>a</i>, <b>112</b><i>b</i>, <b>122</b>.
0062In another example, the remote control device <b>116</b> may set the dynamic starting point of the rotation portion <b>118</b> based on the intensity level of multiple lighting devices <b>112</b><i>a</i>, <b>112</b><i>b</i>, <b>122</b>. The remote control device <b>116</b> may set the dynamic starting point of the rotation portion <b>118</b> to an average intensity level (e.g., on, off, 10%, 20%, etc.) of the lighting devices <b>112</b><i>a</i>, <b>112</b><i>b</i>, <b>122</b>, or a common lighting intensity (e.g., on, off, 10%, 20%, etc.) of a majority of the lighting devices <b>112</b><i>a</i>, <b>112</b><i>b</i>, <b>122</b>, for example. The remote control device <b>116</b> may set the dynamic starting point of the rotation portion <b>118</b> to a maximum level of the lighting devices <b>112</b><i>a</i>, <b>112</b><i>b</i>, <b>122</b> when the rotation portion <b>118</b> is being rotated clockwise to raise the intensity level of the lighting devices, or a minimum level of the lighting devices <b>112</b><i>a</i>, <b>112</b><i>b</i>, <b>122</b> when the rotation portion <b>118</b> is being rotated counterclockwise to lower the intensity level of the lighting devices, for example. The status indicator <b>119</b> may be illuminated as feedback to reflect the dynamic starting point to the user. For example, the remote control device <b>116</b> may illuminate a portion of the status indicator <b>119</b> that reflects the lighting intensity that is set as the dynamic starting point.
0063The remote control device <b>116</b> may calculate an increase or decrease in intensity level from the dynamic starting point based on the user interface event. For example, the remote control device <b>116</b> may calculate an increase or decrease in intensity level based on the distance or amount of time the rotation portion <b>118</b> is turned. The rotation from the point of the initial interaction by the user with the rotation portion <b>118</b> may be used to identify the increase or decrease in intensity level from the dynamic starting point. When the remote control device <b>116</b> includes a linear control, the remote control device <b>116</b> may calculate an increase or decrease in intensity level based on the distance or amount of time the user swipes a finger up or down on the linear control. The user's finger swipe from the point of the initial interaction by the user with the linear control may be used to identify the increase or decrease in intensity level from the dynamic starting point.
0064The updated intensity level may be calculated from the user's initial interaction and stored at the remote control device <b>116</b>. The updated intensity level may be included in a move-to-level command that is transmitted from the remote control device <b>116</b> to the lighting devices <b>112</b><i>a</i>, <b>112</b><i>b</i>, <b>122</b> when the remote control device <b>116</b> is using absolute control.
0065The visual feedback displayed by the status indicator <b>119</b> may be provided in or derived from the information in the move-to-level command when the remote control device <b>116</b> is using absolute control. For example, the remote control device <b>116</b> may reflect the intensity level transmitted in the move-to-level command in the status indicator <b>119</b>.
0066The remote control device <b>116</b> may transmit digital messages configured to increase the lighting level of the lighting devices <b>112</b><i>a</i>, <b>112</b><i>b</i>, <b>122</b> when the rotation portion <b>118</b> is rotated in a direction (e.g., clockwise). As previously mentioned, the remote control device <b>116</b> may be configured to adjust the intensities of the lighting devices <b>112</b><i>a</i>, <b>112</b><i>b</i>, <b>122</b> to an absolute level using absolute control. In addition, or alternatively, the remote control device <b>116</b> may be configured to adjust the intensities of the lighting devices <b>112</b><i>a</i>, <b>112</b><i>b</i>, <b>122</b> using relative control to adjust the intensities of the light devices <b>112</b><i>a</i>, <b>112</b><i>b</i>, <b>122</b> by a relative amount. For example, the remote control device <b>116</b> may transmit digital messages configured to decrease the lighting level of the lighting devices <b>112</b><i>a</i>, <b>112</b><i>b</i>, <b>122</b> when the remote control device <b>116</b> is rotated in the opposite direction (e.g., counterclockwise). The digital messages may include a move-with-rate command, which may cause the lighting devices <b>112</b><i>a</i>, <b>112</b><i>b</i>, <b>122</b> to change their respective intensity level by a predefined amount. The move-with-rate command may include the amount of time over which the lighting level may be changed at the lighting devices. The move-with-rate command may cause the lighting devices <b>112</b><i>a</i>, <b>112</b><i>b</i>, <b>122</b> to retain their relative or proportional intensity levels, and/or difference in respective intensity levels. The remote control device <b>116</b> may send digital messages to increase or decrease the lighting level by a predefined amount when rotated a predefined distance or for a predefined time. The amount of the increase or decrease may be indicated in the digital messages or may be predefined at the lighting devices <b>112</b><i>a</i>, <b>112</b><i>b</i>, <b>122</b>.
0067The status indicator <b>119</b> may be controlled differently when the remote control device <b>116</b> is operating using relative control and when the remote control device <b>116</b> is operating using absolute control. The remote control device <b>116</b> may provide advanced feedback on the status indicator <b>119</b> when performing absolute control, as each of the load control devices (e.g., lighting devices <b>112</b><i>a</i>, <b>112</b><i>b</i>, <b>122</b>) may be in sync. The remote control device <b>116</b> may provide a simple feedback when performing relative control, as each of the load control devices (e.g., lighting devices <b>112</b><i>a</i>, <b>112</b><i>b</i>, <b>122</b>) may be out of sync. When using relative control, the status indicator <b>119</b> may not be illuminated to provide feedback of the intensity of the lighting devices <b>112</b><i>a</i>, <b>112</b><i>b</i>, <b>122</b>. The status indicator <b>119</b> may be illuminated to different intensities when the remote control device <b>116</b> is raising and lowering the intensity level of the lighting devices <b>112</b><i>a</i>, <b>112</b><i>b</i>, <b>122</b>. For example, the status indicator <b>119</b> may be illuminated to a first intensity (e.g., 66%) when raising the intensity level of the lighting devices <b>112</b><i>a</i>, <b>112</b><i>b</i>, <b>122</b> and a second intensity (e.g., 33%) when lowering the intensity level of the lighting devices <b>112</b><i>a</i>, <b>112</b><i>b</i>, <b>122</b>. Alternatively, or additionally, the status indicator <b>119</b> may be illuminated to match the maximum intensity or the minimum intensity of the group of lighting devices <b>112</b><i>a</i>, <b>112</b><i>b</i>, <b>122</b>.
0068The mode of control (e.g., relative control or absolute control) may be dynamically updated at the remote control device <b>116</b>. For example, the remote control device <b>116</b> may change the mode of control depending upon the number of the lighting devices <b>112</b><i>a</i>, <b>112</b><i>b </i><b>122</b> that are associated with the remote control device <b>116</b>. The remote control device <b>116</b> may use the relative control when associated with a single lighting device. The remote control device <b>116</b> may use the absolute control when associated with multiple lighting devices. The mode of control may also, or alternatively, be updated based on whether the lighting devices <b>112</b><i>a</i>, <b>112</b><i>b </i><b>122</b> are in sync or out of sync. The remote control device <b>116</b> may use the absolute control when the lighting devices <b>112</b><i>a</i>, <b>112</b><i>b </i><b>122</b> are in sync. The remote control device <b>116</b> use the relative control when the lighting devices <b>112</b><i>a</i>, <b>112</b><i>b </i><b>122</b> are out of sync.
0069The visual feedback provided by the status indicator <b>119</b> by be dynamically updated depending on the mode of control being used at the remote control device <b>116</b>. The remote control device <b>116</b> may provide feedback according to the simple feedback mode when using relative control and according to the advanced feedback mode when using absolute control. For example, the advanced feedback mode may provide feedback that indicates an intensity level of one or more lighting devices as a portion of the entire status indicator <b>119</b>. The simple feedback mode may provide simple feedback that illuminates the entire status indicator <b>119</b> to different levels when raising or lowering intensity.
0070The digital messages transmitted via the RF signals <b>106</b> may be multicast messages. For example, the digital messages including the move-to-level command may be transmitted as multicast messages. The multicast messages may include a group identifier for controlling the lighting devices <b>112</b><i>a</i>, <b>112</b><i>b</i>, <b>122</b> that are a part of the multicast group. The lighting devices <b>112</b><i>a</i>, <b>112</b><i>b</i>, <b>122</b> may be a part of the multicast group when they are associated with the group identifier (e.g., by having the group identifier stored thereon) for recognizing multicast messages transmitted to the group. The lighting devices <b>112</b><i>a</i>, <b>112</b><i>b</i>, <b>122</b> that are associated with the group identifier may recognize the multicast messages and control the corresponding lighting load according to the command in the multicast messages. The lighting devices <b>112</b><i>a</i>, <b>112</b><i>b</i>, <b>122</b> may forward the multicast messages with the group identifier for identification and load control by other lighting devices associated with the group identifier.
0071The group may be formed at commissioning or configuration of the load control system <b>100</b>. The remote control device <b>116</b> may generate the group identifier and send the group identifier to the lighting devices <b>112</b><i>a</i>, <b>112</b><i>b</i>, <b>122</b> and/or a hub device when the remote control device <b>116</b> is in an association mode (e.g., entered upon selection of one or more buttons). The devices that store the group identifier may be part of the group of devices that are associated with the remote control device <b>116</b> and can respond to group messages.
0072The remote control device <b>116</b> may transmit the digital messages as multicast messages and/or unicast messages via the RF signal <b>106</b>. For example, the digital messages including the move-with-rate command or the move-to-level command may be transmitted as unicast messages. Unicast messages may be sent from the remote control device <b>116</b> directly or via hops to each of the lighting devices <b>112</b><i>a</i>, <b>112</b><i>b</i>, <b>122</b>. The remote control device <b>116</b> may individually send a unicast message to each of the lighting devices <b>112</b><i>a</i>, <b>112</b><i>b</i>, <b>122</b> with which the remote control device <b>116</b> is associated for performing load control. The remote control device <b>116</b> may have the unique identifier of each of the lighting devices <b>112</b><i>a</i>, <b>112</b><i>b</i>, <b>122</b> with which it is associated stored in memory. The remote control device <b>116</b> may generate a separate unicast message for each lighting device <b>112</b><i>a</i>, <b>112</b><i>b</i>, <b>122</b> and address the unicast messages to the lighting devices <b>112</b><i>a</i>, <b>112</b><i>b</i>, <b>122</b> independently. The unicast messages may also include the unique identifier of the remote control device <b>116</b>. The lighting devices <b>112</b><i>a</i>, <b>112</b><i>b</i>, <b>122</b> may identify the unicast messages communicated to them by identifying their own unique identifier and/or a corresponding identifier of the remote that are stored in an association dataset. The lighting devices <b>112</b><i>a</i>, <b>112</b><i>b</i>, <b>122</b> may operate according to the instructions (e.g., load control instructions) in the digital messages comprising their own unique identifier and/or the unique identifier of an associated device, such as the remote control device <b>116</b>.
0073The multicast messages may be communicated more efficiently from the remote control device <b>116</b>, as a single message may be transmitted to multiple lighting devices, such as lighting devices <b>112</b><i>a</i>, <b>112</b><i>b</i>, <b>122</b>, at once. The multicast messages may be more reliable, as the multicast messages may be repeated by a receiving device, such that devices that fail to receive the message due to interference or signal strength may receive the multicast message upon the message being repeated. The load control instructions in the multicast messages may also be received and implemented by multiple lighting devices, such as lighting devices <b>112</b><i>a</i>, <b>112</b><i>b</i>, <b>122</b>, at the same time, or at nearly the same time with a minor delay due to differences in latency, as a single message is being received at a group of devices within the same wireless range. The difference in latency may be overcome by determining the latency at each of the lighting devices and compensating for the difference in latency at each lighting device by delaying the implementation of the load control instructions by the difference in latency. The load control instructions in the unicast messages may be received and implemented by multiple lighting devices <b>112</b><i>a</i>, <b>112</b><i>b</i>, <b>122</b> at different times, which may be caused by the difference in latency between the devices and/or the time to process and transmit each message, as a different message is being transmitted to each device in a wireless range.
0074The remote control device <b>116</b> may transmit digital messages that include move-with-rate commands (e.g., as unicast messages and/or multicast messages) to increase or decrease the lighting intensity level of the lighting devices <b>112</b><i>a</i>, <b>112</b><i>b</i>, <b>122</b> in predefined increments as the user turns the remote control device <b>116</b> a predefined distance or time in one direction or another. The remote control device <b>116</b> may continue to transmit digital messages to the lighting devices <b>112</b><i>a</i>, <b>112</b><i>b</i>, <b>122</b> as the user continues to turn the remote control device <b>116</b>. For example, the remote control device <b>116</b> may identify a rotation of a predefined distance or for a predefined time and send one or more digital messages to instruct the lighting devices <b>112</b><i>a</i>, <b>112</b><i>b</i>, <b>122</b> to each increase by ten percent (10%). The remote control device <b>116</b> may identify a continued rotation of a predefined distance or time and send digital messages to instruct the lighting devices <b>112</b><i>a</i>, <b>112</b><i>b</i>, <b>122</b> to increase by ten percent (10%) again.
0075The remote control device <b>116</b> may also, or alternatively, send digital messages for a move-to-level command (e.g., “on” command, “off” command, toggle command, etc.) to turn on/off the lighting devices <b>112</b><i>a</i>, <b>112</b><i>b</i>, <b>122</b>. The remote control device <b>116</b> may transmit one or more digital messages to the lighting devices <b>112</b><i>a</i>, <b>112</b><i>b</i>, <b>122</b> when an on event or an off event are detected. For example, the remote control device <b>116</b> may identify a rotation or actuation and send digital messages to instruct the lighting devices <b>112</b><i>a</i>, <b>112</b><i>b</i>, <b>122</b> to turn on/off. The remote control device <b>116</b> may operate by sending a move-with-rate command after turning on. For example, the remote control device <b>116</b> may identify a rotation of a predefined distance or time after turning on and send digital messages to instruct the lighting devices <b>112</b><i>a</i>, <b>112</b><i>b</i>, <b>122</b> to increase/decrease by a predefined intensity (e.g., ten percent (10%)).
0076Embodiments described herein are not limited to remote control devices, but other controller devices may also be used in the same, or similar, manner. For example, embodiments may include wired control devices and/or plug-in control devices that communicate digital messages as described herein.
0077<figref idref="DRAWINGS">FIG. 1B</figref> shows an example load control system <b>100</b> having other devices. For example, the load control system <b>100</b> may include other control devices, such as controller devices and/or load control devices. The load control devices may be capable of controlling the amount of power provided to a respective electrical load based on digital messages received from the controller devices, which may be input devices. The digital messages may include load control instructions or another indication that causes the load control device to determine load control instructions for controlling an electrical load.
0078Examples of load control devices may include a motorized window treatment <b>130</b> and/or the lighting devices <b>112</b><i>a</i>, <b>112</b><i>b</i>, <b>122</b>, though other load control devices may be implemented. The controller devices may include a remote control device <b>150</b>, an occupancy sensor <b>160</b>, a daylight sensor <b>170</b>, and/or a network device <b>190</b>, though other controller devices may be implemented. The controller devices may perform communications in a configuration similar to the remote control device <b>116</b> as described herein. The load control devices may perform communications in a configuration similar to the lighting devices <b>112</b><i>a</i>, <b>112</b><i>b</i>, <b>122</b> as described herein.
0079The load control devices may receive digital messages via wireless signals, e.g., radio-frequency (RF) signals <b>106</b> (e.g., ZIGBEE®; NFC; BLUETOOTH®; WI-FI®; or a proprietary communication channel, such as CLEAR CONNECT™, etc.). The wireless signals may be transmitted by the controller devices. In response to the received digital messages, the respective lighting devices <b>112</b><i>a</i>, <b>112</b><i>b</i>, <b>122</b> may be turned on and off, and/or the intensities of the respective lighting devices <b>112</b><i>a</i>, <b>112</b><i>b</i>, <b>122</b> may be increased or decreased. In response to the received digital messages, the motorized window treatment <b>130</b> may increase or decrease a level of a covering material <b>134</b>.
0080The battery-powered remote control device <b>150</b> may include one or more actuators <b>152</b> (e.g., one or more of an on button, an off button, a raise button, a lower button, or a preset button). The battery-powered remote control device <b>150</b> may transmit RF signals <b>106</b> in response to actuations of one or more of the actuators <b>152</b>. The battery-powered remote control device <b>150</b> may be handheld. The battery-powered remote control device <b>150</b> may be mounted vertically to a wall, or supported on a pedestal to be mounted on a tabletop. Examples of battery-powered remote control devices are described in greater detail in commonly-assigned U.S. Pat. No. 8,330,638, issued Dec. 11, 2012, entitled WIRELESS BATTERY-POWERED REMOTE CONTROL HAVING MULTIPLE MOUNTING MEANS, and U.S. Patent Application Publication No. 2012/0286940, published Nov. 15, 2012, entitled CONTROL DEVICE HAVING A NIGHTLIGHT, the entire disclosures of which are hereby incorporated by reference.
0081The remote control device <b>150</b> may be a wireless device capable of controlling a load control device via wireless communications. The remote control device <b>150</b> may be attached to the wall or detached from the wall. Examples of remote control devices are described in greater detail in U.S. Pat. No. 5,248,919, issued Sep. 28, 1993, entitled LIGHTING CONTROL DEVICE; U.S. Pat. No. 8,471,779, issued Jun. 25, 2013, entitled WIRELESS BATTERY-POWERED REMOTE CONTROL WITH LABEL SERVING AS ANTENNA ELEMENT; and U.S. Patent Application Publication No. 2014/0132475, published May 15, 2014, entitled WIRELESS LOAD CONTROL DEVICE, the entire disclosures of which are hereby incorporated by reference.
0082The occupancy sensor <b>160</b> may be configured to detect occupancy and/or vacancy conditions in the space in which the load control system <b>100</b> is installed. The occupancy sensor <b>160</b> may transmit digital messages to load control devices via the RF communication signals <b>106</b> in response to detecting the occupancy or vacancy conditions. The occupancy sensor <b>160</b> may operate as a vacancy sensor, such that digital messages are transmitted in response to detecting a vacancy condition (e.g., digital messages may not be transmitted in response to detecting an occupancy condition). The occupancy sensor <b>160</b> may enter an association mode and may transmit association messages via the RF communication signals <b>106</b> in response to actuation of a button on the occupancy sensor <b>160</b>. Examples of RF load control systems having occupancy and vacancy sensors are described in greater detail in commonly-assigned U.S. Pat. No. 8,009,042, issued Aug. 30, 2011, entitled RADIO-FREQUENCY LIGHTING CONTROL SYSTEM WITH OCCUPANCY SENSING; U.S. Pat. No. 8,199,010, issued Jun. 12, 2012, entitled METHOD AND APPARATUS FOR CONFIGURING A WIRELESS SENSOR; and U.S. Pat. No. 8,228,184, issued Jul. 24, 2012, entitled BATTERY-POWERED OCCUPANCY SENSOR, the entire disclosures of which are hereby incorporated by reference.
0083The daylight sensor <b>170</b> may be configured to measure a total light intensity in the space in which the load control system <b>100</b> is installed. The daylight sensor <b>170</b> may transmit digital messages including the measured light intensity via the RF communication signals <b>106</b> for controlling load control devices in response to the measured light intensity. The daylight sensor <b>170</b> may enter an association mode and may transmit association messages via the RF communication signals <b>106</b> in response to actuation of a button on the daylight sensor <b>170</b>. Examples of RF load control systems having daylight sensors are described in greater detail in commonly-assigned U.S. Pat. No. 8,410,706, issued Apr. 2, 2013, entitled METHOD OF CALIBRATING A DAYLIGHT SENSOR; and U.S. Pat. No. 8,451,116, issued May 28, 2013, entitled WIRELESS BATTERY-POWERED DAYLIGHT SENSOR, the entire disclosures of which are hereby incorporated by reference.
0084The motorized window treatment <b>130</b> may be mounted in front of a window for controlling the amount of daylight entering the space in which the load control system <b>100</b> is installed. The motorized window treatment <b>130</b> may include, for example, a cellular shade, a roller shade, a drapery, a Roman shade, a Venetian blind, a Persian blind, a pleated blind, a tensioned roller shade systems, or other suitable motorized window covering. The motorized window treatment <b>130</b> may include a motor drive unit <b>132</b> for adjusting the position of a covering material <b>134</b> of the motorized window treatment <b>130</b> in order to control the amount of daylight entering the space. The motor drive unit <b>132</b> of the motorized window treatment <b>130</b> may have an RF receiver and an antenna mounted on or extending from a motor drive unit <b>132</b> of the motorized window treatment <b>130</b>. The motor drive unit <b>132</b> may respond to digital messages to increase or decrease the level of the covering material <b>134</b>. The motor drive unit <b>132</b> of the motorized window treatment <b>130</b> may be battery-powered or may receive power from an external direct-current (DC) power supply. Examples of battery-powered motorized window treatments are described in greater detail in commonly-assigned U.S. Pat. No. 8,950,461, issued Feb. 10, 2015, entitled MOTORIZED WINDOW TREATMENT, and U.S. Pat. No. 9,115,537, issued Aug. 25, 2015, entitled BATTERY-POWERED ROLLER SHADE SYSTEM, the entire disclosures of which are hereby incorporated by reference
0085Digital messages transmitted by the controller devices may include a command and/or identifying information, such as a serial number (e.g., a unique identifier) associated with the transmitting controller device. Each of the controller devices may be associated with the lighting devices <b>112</b><i>a</i>, <b>112</b><i>b</i>, <b>122</b> and/or the motorized window treatment <b>130</b> during a configuration procedure of the load control system <b>100</b>, such that the lighting devices <b>112</b><i>a</i>, <b>112</b><i>b</i>, <b>122</b> and/or the motorized window treatment <b>130</b> may be responsive to digital messages transmitted by the controller devices via the RF signals <b>106</b>. Examples of associating wireless control devices during a configuration procedure are described in greater detail in commonly-assigned U.S. Patent Application Publication No. 2008/0111491, published May 15, 2008, entitled RADIO-FREQUENCY LIGHTING CONTROL SYSTEM, and U.S. Pat. No. 9,368,025, issued Jun. 14, 2016, entitled TWO-PART LOAD CONTROL SYSTEM MOUNTABLE TO A SINGLE ELECTRICAL WALLBOX, the entire disclosures of which are hereby incorporated by reference.
0086The load control system <b>100</b> may include a hub device <b>180</b> (e.g., a system bridge) configured to enable communication with a network <b>182</b>, e.g., a wireless or wired local area network (LAN). The hub device <b>180</b> may be connected to a router via a wired digital communication link <b>184</b> (e.g., an Ethernet communication link). The router may allow for communication with the network <b>182</b>, e.g., for access to the Internet. The hub device <b>180</b> may be wirelessly connected to the network <b>182</b>, e.g., using wireless technology, such as WI-FI® technology, cellular technology, etc. The hub device <b>180</b> may be configured to transmit communication signals (e.g., RF signals <b>106</b>) to the lighting devices <b>112</b><i>a</i>, <b>112</b><i>b</i>, <b>122</b> and/or the motorized window treatment <b>130</b> for controlling the devices in response to digital messages received from external devices via the network <b>182</b>. The hub device <b>180</b> may communicate via one or more types of RF communication signals (e.g., ZIGBEE®; NFC; BLUETOOTH®; WI-FI®; cellular; a proprietary communication channel, such as CLEAR CONNECT™, etc.). The hub device <b>180</b> may be configured to transmit and/or receive RF signals <b>106</b> (e.g., using ZIGBEE®; NFC; BLUETOOTH®; or a proprietary communication channel, such as CLEAR CONNECT™, etc.). The hub device <b>180</b> may be configured to transmit digital messages via the network <b>182</b> for providing data (e.g., status information) to external devices.
0087The RF signals <b>106</b> may be transmitted via one or more protocols. For example, the remote control device <b>116</b> and the remote control device <b>150</b> may communicate digital messages to lighting devices <b>112</b><i>a</i>, <b>112</b><i>b</i>, <b>122</b> via another protocol (e.g., ZIGBEE®, BLUETOOTH®, etc.) than other devices. For example, the occupancy sensor <b>160</b>, daylight sensor <b>170</b>, and/or motorized window treatment <b>130</b> may communicate via a proprietary communication channel, such as CLEAR CONNECT™. The hub device <b>180</b> may format digital communications using the appropriate protocol for the device. The hub device <b>180</b> may communicate using multiple protocols.
0088The hub device <b>180</b> may operate as a central controller for the load control system <b>100</b>, and/or relay digital messages between the control devices (e.g., lighting devices, motorized window treatments, etc.) of the load control system and the network <b>182</b>. The hub device <b>180</b> may receive digital messages from a controller device and configure the digital message for communication to a load control device. For example, the hub device <b>180</b> may configure multicast messages and/or unicast messages for transmission as described herein. The hub device <b>180</b> may be on-site at the load control system <b>100</b> or at a remote location. Though the hub device <b>180</b> is shown as a single device, the load control system <b>100</b> may include multiple hubs and/or the functionality thereof may be distributed across multiple devices.
0089The load control system <b>100</b> may include a network device <b>190</b>, such as, a smart phone (for example, an iPhone® smart phone, an Android® smart phone, or a Blackberry® smart phone), a personal computer, a laptop, a wireless-capable media device (e.g., MP3 player, gaming device, or television), a tablet device, (for example, an iPad® hand-held computing device), a WI-FT® or wireless-communication-capable television, or any other suitable network communication or Internet-Protocol-enabled device. The network device <b>190</b> may be operable to transmit digital messages in one or more Internet Protocol packets to the hub device <b>180</b> via RF signals <b>108</b>, either directly or via the network <b>182</b>. For example, the network device <b>190</b> may transmit the RF signals <b>108</b> to the hub device <b>180</b> via a WI-FI® communication link, a WIMAX® communications link, a BLUETOOTH® communications link, a near field communication (NFC) link, a cellular communications link, a television white space (TVWS) communication link, or any combination thereof. The RF signals <b>108</b> may be communicated using a different protocol and/or wireless band than the RF signals <b>106</b>. For example, the RF signals <b>108</b> may be configured for WI-FI® communication or cellular communication, while RF signals <b>106</b> may be configured for ZIGBEE®, BLUETOOTH®, or a proprietary communication channel, such as CLEAR CONNECT™. In another example, the RF signals <b>108</b> and the RF signals <b>106</b> may be the same. Examples of load control systems operable to communicate with network devices on a network are described in greater detail in commonly-assigned U.S. Patent Application Publication No. 2013/0030589, published Jan. 31, 2013, entitled LOAD CONTROL DEVICE HAVING INTERNET CONNECTIVITY, the entire disclosure of which is hereby incorporated by reference.
0090The network device <b>190</b> may include a visual display <b>192</b>. The visual display <b>192</b> may include a touch screen that may include, for example, a capacitive touch pad displaced overtop the visual display, such that the visual display may display soft buttons that may be actuated by a user. The network device <b>190</b> may include a plurality of hard buttons, e.g., physical buttons (not shown), in addition to the visual display <b>192</b>. The network device <b>190</b> may download a product control application for allowing a user of the network device <b>190</b> to control the load control system <b>100</b>. In response to actuations of the displayed soft buttons and/or hard buttons, the network device <b>190</b> may transmit digital messages to the load control devices and/or the hub device <b>180</b> through the wireless communications described herein.
0091The operation of the load control system <b>100</b> may be programmed and configured using the hub device <b>180</b> and/or network device <b>190</b>. An example of a configuration procedure for a wireless load control system is described in greater detail in commonly-assigned U.S. Patent Application Publication No. 2014/0265568, published Sep. 18, 2014, entitled COMMISSIONING LOAD CONTROL SYSTEMS, the entire disclosure of which is hereby incorporated by reference.
0092The lighting devices <b>112</b><i>a</i>, <b>112</b><i>b</i>, <b>122</b> may each be included in a group of lighting devices that are associated with a common control device, such as the remote control device <b>116</b>. For example, each of the lighting devices <b>112</b><i>a</i>, <b>112</b><i>b</i>, <b>122</b> may store the unique identifier of the remote control device <b>116</b> during an association mode to enable the lighting devices <b>112</b><i>a</i>, <b>112</b><i>b</i>, <b>122</b> to be controlled by digital messages from the remote control device <b>116</b> that include control instructions. The hub device <b>180</b> may store the associations between each of the lighting devices <b>112</b><i>a</i>, <b>112</b><i>b</i>, <b>122</b> and the remote control device <b>116</b> during an association mode. The association information may be used by the hub device <b>180</b> for routing digital messages to the lighting devices <b>112</b><i>a</i>, <b>112</b><i>b</i>, <b>122</b>, or the lighting devices <b>112</b><i>a</i>, <b>112</b><i>b</i>, <b>122</b> may receive digital messages from the remote control device <b>116</b> directly.
0093A subset of the lighting devices <b>112</b><i>a</i>, <b>112</b><i>b</i>, <b>122</b> may be associated with other controller devices (e.g., remote control device <b>150</b>, occupancy sensor <b>160</b>, daylight sensor <b>170</b>, network device <b>190</b>, etc.) that may be capable of turning the subset of the lighting devices <b>112</b><i>a</i>, <b>112</b><i>b</i>, <b>122</b> on and/or off. A subset of the lighting devices <b>112</b><i>a</i>, <b>112</b><i>b</i>, <b>122</b> may be controlled to a different intensity level than the other lighting devices. In an example, the lighting device <b>122</b> may be independently associated with the remote control device <b>150</b> and/or the network device <b>190</b>. The lighting device <b>122</b> may be separately controlled by the remote control device <b>150</b> and/or the network device <b>190</b>, such that the lighting device <b>122</b> may be turned on while the lighting devices <b>112</b><i>a</i>, <b>112</b><i>b </i>are turned off, or vice versa. In another example, the lighting device <b>122</b> may be separately controlled by the remote control device <b>150</b> and/or the network device <b>190</b>, such that the lighting device <b>122</b> may be dimmed to a different intensity level than the lighting devices <b>112</b><i>a</i>, <b>112</b><i>b. </i>
0094As a subset of the lighting devices <b>112</b><i>a</i>, <b>112</b><i>b</i>, <b>122</b> may be independently controlled, the group of lighting devices <b>112</b><i>a</i>, <b>112</b><i>b</i>, <b>122</b> may be in an inconsistent state (e.g., on/off state or intensity level). For example, the lighting device <b>122</b> may be controlled to an “on” state by the remote control device <b>150</b> or the network device <b>190</b>, while the lighting devices <b>112</b><i>a</i>, <b>112</b><i>b </i>are in an “off” state. Though lighting device <b>122</b> is provided in an opposite state in examples described herein, the on/off state of any of the lighting devices in a load control system <b>100</b> may be out of sync with others. The remote control device <b>116</b> may send a toggle command or an on/off command (e.g., an “on” command or an “off” command) to the group of lighting devices <b>112</b><i>a</i>, <b>112</b><i>b</i>, <b>122</b> to toggle the group of lighting devices <b>112</b><i>a</i>, <b>112</b><i>b</i>, <b>122</b> from an “on” state to an “off” state, or vice versa. The toggle command or the on/off command may be sent in a multicast message that is received at each of the lighting devices <b>112</b><i>a</i>, <b>112</b><i>b</i>, <b>122</b>, or in unicast messages that are independently directed to each of the lighting devices <b>112</b><i>a</i>, <b>112</b><i>b</i>, <b>122</b>. The toggle command or the on/off command may be communicated directly to the lighting devices <b>112</b><i>a</i>, <b>112</b><i>b</i>, <b>122</b>, or via the hub device <b>180</b>.
0095The lighting devices <b>112</b><i>a</i>, <b>112</b><i>b</i>, <b>122</b> may identify the toggle command received in the digital messages and toggle to the opposite state. In an example in which the lighting devices <b>112</b><i>a</i>, <b>112</b><i>b </i>are in the “off” state, the lighting devices <b>112</b><i>a</i>, <b>112</b><i>b </i>may identify the toggle command and turn to the “on” state. In the example in which the lighting device <b>122</b> is in the “on” state, the lighting device <b>122</b> may identify the toggle command received in the digital messages and toggle to the “off” state.
0096To synchronize the on/off state of the group of lighting devices <b>112</b><i>a</i>, <b>112</b><i>b</i>, <b>122</b>, the remote control device <b>116</b>, the remote control device <b>150</b>, or the network device <b>190</b> may transmit a digital message including a direct command (e.g., an “on” command or an “off” command) to the lighting devices <b>112</b><i>a</i>, <b>112</b><i>b</i>, <b>122</b> to control all of the lighting devices <b>112</b><i>a</i>, <b>112</b><i>b</i>, <b>122</b> to the same state. In addition, to synchronize the on/off state of the group of lighting devices <b>112</b><i>a</i>, <b>112</b><i>b</i>, <b>122</b>, the remote control device <b>116</b>, the remote control device <b>150</b>, or the network device <b>190</b> may transmit a digital message to a subset of the lighting devices that are out of sync with the other lighting devices to cause the subset of the lighting devices to change states (e.g., via a toggle command, an “on” command, or an “off” command). For example, in an example in which the lighting devices <b>112</b><i>a</i>, <b>112</b><i>b </i>are in the “off” state and the lighting device <b>122</b> is in the “on” state, the remote control device <b>116</b>, the remote control device <b>150</b>, or the network device <b>190</b> may transmit a digital message to the lighting device <b>122</b> to cause the lighting device <b>122</b> to change states (e.g., via a toggle command, an “on” command, or an “off” command), or transmit a digital message to the lighting devices <b>112</b><i>a</i>, <b>112</b><i>b </i>to cause the lighting devices <b>112</b><i>a</i>, <b>112</b><i>b </i>to change states (e.g., via a toggle command, an “on” command, or an “off” command).
0097The load control system <b>100</b> may be configured to automatically synchronize and/or toggle the on/off state of the group of lighting devices <b>112</b><i>a</i>, <b>112</b><i>b</i>, <b>122</b>. The remote control device <b>116</b> may identify a toggle event and query the lighting devices <b>112</b><i>a</i>, <b>112</b><i>b</i>, <b>122</b> for their current on/off state. The query message may be sent as a multicast message, or individual unicast messages, to each of the lighting devices <b>112</b><i>a</i>, <b>112</b><i>b</i>, <b>122</b>. The lighting devices <b>112</b><i>a</i>, <b>112</b><i>b</i>, <b>122</b> may return the current on/off state, which may be stored locally thereon.
0098The remote control device <b>116</b> may choose the command to send in response to the toggle event based on the current on/off state of one or more of the group of lighting devices <b>112</b><i>a</i>, <b>112</b><i>b</i>, <b>122</b>. The remote control device <b>116</b> may identify whether the on/off state across the group of lighting devices <b>112</b><i>a</i>, <b>112</b><i>b</i>, <b>122</b> is consistent. If the on/off state across the group of lighting devices <b>112</b><i>a</i>, <b>112</b><i>b</i>, <b>122</b> is consistent, the remote control device <b>116</b> may send the toggle command, an “on” command (if the lighting devices are off), or “off” command (if the lighting devices are on) to the lighting devices <b>112</b><i>a</i>, <b>112</b><i>b</i>, <b>122</b> to toggle the on/off state of the group of lighting devices <b>112</b><i>a</i>, <b>112</b><i>b</i>, <b>122</b>. If the on/off state across the group of lighting devices <b>112</b><i>a</i>, <b>112</b><i>b</i>, <b>122</b> is inconsistent, the remote control device <b>116</b> may send a direct command to all of the lighting devices <b>112</b><i>a</i>, <b>112</b><i>b</i>, <b>122</b> or a synchronization message to a subset of the lighting devices <b>112</b><i>a</i>, <b>112</b><i>b</i>, <b>122</b> to change the on/off state of the subset.
0099The direct command may be an “on” command or an “off” command. For example, where lighting device <b>122</b> indicates that the lighting device <b>122</b> is in an “on” state and lighting devices <b>112</b><i>a</i>, <b>112</b><i>b </i>indicate that the devices are each in the “off” state, the remote control device <b>116</b> may send either an “on” command or an “off” command to all of the lighting devices <b>112</b><i>a</i>, <b>112</b><i>b</i>, <b>122</b> to synchronize the on/off state across the lighting devices <b>112</b><i>a</i>, <b>112</b><i>b</i>, <b>122</b>. The remote control device <b>116</b> may send the direct command in a unicast message to each of the lighting devices. The remote control device <b>116</b> may send the direct command in a multicast message to each of the lighting devices.
0100The synchronization message may include an “on” command or an “off” command. For example, where lighting device <b>122</b> indicates that the lighting device <b>122</b> is in an “on” state and lighting devices <b>112</b><i>a</i>, <b>112</b><i>b </i>indicate that the devices are each in the “off” state, the remote control device <b>116</b> may send an “off” command to the lighting device <b>122</b> or an “on” command to the lighting devices <b>112</b><i>a</i>, <b>112</b><i>b </i>to synchronize the on/off state across the lighting devices <b>112</b><i>a</i>, <b>112</b><i>b</i>, <b>122</b>. The remote control device <b>116</b> may send the synchronization message as a unicast message to the lighting devices to be changed. The remote control device <b>116</b> may send the synchronization message as a multicast message that identifies the state of the devices that are intended to respond to the command in the synchronization message and leaves the on/off state of the other devices unchanged.
0101The synchronization message may include a toggle command directed to the subset of lighting devices to be toggled. For example, where the lighting device <b>122</b> indicates that the lighting device <b>122</b> is in an “on” state and the lighting devices <b>112</b><i>a</i>, <b>112</b><i>b </i>indicate that the devices are each in the “off” state, the remote control device <b>116</b> may send a toggle command to the lighting device <b>122</b> or a toggle command to the lighting devices <b>112</b><i>a</i>, <b>112</b><i>b </i>to synchronize the on/off state across the lighting devices <b>112</b><i>a</i>, <b>112</b><i>b</i>, <b>122</b>. The remote control device <b>116</b> may send the synchronization message as a unicast message to the lighting devices to be changed. The remote control device <b>116</b> may send the synchronization message as a multicast message that indicates the devices in the on/off state (e.g., “on” state or “off” state) that are to respond to the on/off command in the message.
0102The remote control device <b>116</b> may send a synchronization message to change the on/off state of a preferred subset of lighting devices. The remote control device <b>116</b> may send the synchronization message to change the on/off state of the subset of devices having the lesser number of devices for which the on/off state is to be changed. The remote control device <b>116</b> may default to “turning off” a subset of lighting devices. For example, the remote control device <b>116</b> may query the lighting devices <b>112</b><i>a</i>, <b>112</b><i>b</i>, <b>122</b> and when one of the lighting devices <b>112</b><i>a</i>, <b>112</b><i>b</i>, <b>122</b> returns an “on” state indicating that the device is on (e.g., such as lighting device <b>122</b>), the remote control device <b>116</b> may stop querying devices and send a synchronization message (e.g., via unicast or multicast) to the group of lighting devices <b>112</b><i>a</i>, <b>112</b><i>b</i>, <b>122</b> that includes an “off” command to tell the group of lighting devices <b>112</b><i>a</i>, <b>112</b><i>b</i>, <b>122</b> to turn off. The remote control device <b>116</b> may default to “turning on” a subset of lighting devices. For example, the remote control device <b>116</b> may query the lighting devices <b>112</b><i>a</i>, <b>112</b><i>b</i>, <b>122</b> and when one of the lighting devices <b>112</b><i>a</i>, <b>112</b><i>b</i>, <b>122</b> returns an “off” state indicating that the device is off (e.g., such as lighting devices <b>112</b><i>a</i>, <b>112</b><i>b</i>), the remote control device <b>116</b> may stop querying the devices and send a synchronization message (e.g., via unicast or multicast) to the group of lighting devices <b>112</b><i>a</i>, <b>112</b><i>b</i>, <b>122</b> that includes an “on” command to tell the group of lighting devices <b>112</b><i>a</i>, <b>112</b><i>b</i>, <b>122</b> to turn on.
0103The remote control device <b>116</b> may send a digital message after the synchronization message to toggle the group of synchronized lighting devices <b>112</b><i>a</i>, <b>112</b><i>b</i>, <b>122</b>. The remote control device <b>116</b> may receive a response to the synchronization message that indicates the state of each of the devices, or each of the devices that changed state in response to the synchronization message. The response may be a state update message. The remote control device <b>116</b> may send a digital message after the synchronization message to toggle the group of lighting devices <b>112</b><i>a</i>, <b>112</b><i>b</i>, <b>122</b>. For example, after the remote control device <b>116</b> toggles the on/off state of the lighting device <b>122</b> to the “off” state, the remote control device <b>116</b> may send an “on” command or a toggle command to the group of lighting devices <b>112</b><i>a</i>, <b>112</b><i>b</i>, <b>122</b>. Such a command may be sent after the synchronization message is sent, or after receiving a response to the synchronization message, to toggle the entire group of lighting devices <b>112</b><i>a</i>, <b>112</b><i>b</i>, <b>122</b>.
0104The remote control device <b>116</b> may send a synchronization message and wait for a subsequent toggle event. After receiving the toggle event, the remote control device <b>116</b> may query the group of lighting devices <b>112</b><i>a</i>, <b>112</b><i>b</i>, <b>122</b>. When the group of lighting devices <b>112</b><i>a</i>, <b>112</b><i>b</i>, <b>122</b> are in a consistent state (e.g., “on” state or “off” state), the remote control device <b>116</b> may send a toggle command, or an “on” or “off” command, to toggle the on/off state of the group of lighting devices <b>112</b><i>a</i>, <b>112</b><i>b</i>, <b>122</b>.
0105The remote control device <b>116</b> may maintain the next state command (e.g., “on” command or “off” command) to be sent from the remote control device <b>116</b> in response to the identification of the next toggle event. For example, the remote control device <b>116</b> may pre-store an “on” command after transmission of an “off” command, and pre-store an “off” command after transmission of an “on” command. When the toggle event is identified, the remote control device <b>116</b> may send the pre-stored state command (e.g., “on” command or “off” command).
0106The remote control device <b>116</b> may be a battery-powered remote control device that may enter a sleep mode to conserve battery power after a predetermined period of time has elapsed without receiving digital messages and/or user events. The remote control device may awaken from a sleep mode in response to a toggle event and may send the pre-stored “on” command or “off” command to the lighting devices <b>112</b><i>a</i>, <b>112</b><i>b</i>, <b>122</b>. The pre-stored command may be sent under the assumption that the on/off state of the lighting devices <b>112</b><i>a</i>, <b>112</b><i>b</i>, <b>122</b> has been unchanged by other controller devices since the storing of the pre-stored command. If the on/off state of the lighting devices <b>112</b><i>a</i>, <b>112</b><i>b</i>, <b>122</b> has gone unchanged by other controller devices since the last command from the remote control device <b>116</b>, or the on/off state of the lighting devices <b>112</b><i>a</i>, <b>112</b><i>b</i>, <b>122</b> has been returned to the on/off state indicated in the last command from the remote control device <b>116</b>, the pre-stored command may toggle the on/off state of the lighting devices <b>112</b><i>a</i>, <b>112</b><i>b</i>, <b>122</b> upon the remote control device <b>116</b> identifying a toggle event and awakening to send the command. If the on/off state of some of the lighting devices <b>112</b><i>a</i>, <b>112</b><i>b</i>, <b>122</b> has been changed by other controller devices since the last command from the remote control device <b>116</b>, the pre-stored command may act as a synchronization message for any of the lighting devices <b>112</b><i>a</i>, <b>112</b><i>b</i>, <b>122</b> that are out of sync. The lighting devices <b>112</b><i>a</i>, <b>112</b><i>b</i>, <b>122</b> that are already in the state indicated in the pre-stored command may be unresponsive to the pre-stored command.
0107The lighting devices <b>112</b><i>a</i>, <b>112</b><i>b</i>, <b>122</b> that change an on/off state in response to an “on” command or an “off” command may send a state update message to the remote control device <b>116</b> to indicate the change in on/off state. The remote control device <b>116</b> may receive the state update message from the lighting devices <b>112</b><i>a</i>, <b>112</b><i>b</i>, <b>122</b> that change state in response to the received “on” command or the received “off” command. The lighting devices that fail to change the on/off state in response to the command from the remote control device <b>116</b> may be unresponsive. For example, the remote control device <b>116</b> may send an “off” command to the lighting devices <b>112</b><i>a</i>, <b>112</b><i>b</i>, <b>122</b> and the lighting device <b>122</b> may update the on/off state to the “off” state. The lighting device <b>122</b> may send a response message to the remote control device <b>116</b> to indicate the change in state. The lighting devices <b>112</b><i>a</i>, <b>112</b><i>b </i>may be unresponsive, as they are already in the “off” state.
0108The remote control device <b>116</b> may stay awake to wait for an on/off state update from the lighting devices <b>112</b><i>a</i>, <b>112</b><i>b</i>, <b>122</b>. The remote control device <b>116</b> may poll the lighting devices <b>112</b><i>a</i>, <b>112</b><i>b</i>, <b>122</b> while awake. The lighting devices <b>112</b><i>a</i>, <b>112</b><i>b</i>, <b>122</b> may indicate a state change to an “on” state or an “off” state and send the updated state to the remote control device <b>116</b>. For example, as the lighting device <b>122</b> is indicated in <figref idref="DRAWINGS">FIG. 1B</figref> as being in the “on” state, the remote control device <b>116</b> may transmit an “off” command to the lighting device <b>122</b>, and the lighting device <b>122</b> may change to the “off” state. The lighting devices <b>112</b><i>a</i>, <b>112</b><i>b</i>, <b>122</b> may have stored thereon the identifiers (e.g., group numbers) of the controller devices that have subscribed to request state change updates for on/off states. The lighting device <b>122</b> may send a state update message to the remote control device <b>116</b>, which may be subscribed to receive the indication of the updated state. When the remote control device <b>116</b> receives the state update message, the remote control device <b>116</b> may assume that the operation was successful and may go to sleep. The state update message may be send from the lighting devices <b>112</b><i>a</i>, <b>112</b><i>b</i>, <b>122</b> as unicast messages. The remote control device <b>116</b> may stay asleep until a subsequent user event at the device.
0109The lighting devices <b>112</b><i>a</i>, <b>112</b><i>b</i>, <b>122</b> may already be in the indicated state received in the command from the remote control device <b>116</b>. For example, the lighting devices <b>112</b><i>a</i>, <b>112</b><i>b </i>may be in the “off” state, as illustrated in <figref idref="DRAWINGS">FIG. 1B</figref>, when the lighting devices <b>112</b><i>a</i>, <b>112</b><i>b </i>receive the “off” command. The lighting devices <b>112</b><i>a</i>, <b>112</b><i>b </i>may fail to provide a state update message when a state change fails to be performed in response to the received command. If the remote control device <b>116</b> fails to receive a state update message from each of the lighting devices <b>112</b><i>a</i>, <b>112</b><i>b</i>, <b>122</b>, the remote control device <b>116</b> may send the opposite on/off command (e.g., the “on” command). For example, when the remote control device <b>116</b> fails to receive a state update message from one of the lighting devices <b>112</b><i>a</i>, <b>112</b><i>b </i>(e.g., after a predefined period of time), the remote control device <b>116</b> may send the opposite on/off command (e.g., the “on” command) in a digital message (e.g., unicast or multicast message) to toggle the group of lighting devices <b>112</b><i>a</i>, <b>112</b><i>b</i>, <b>122</b>. The opposite on/off command may be sent, as a toggle event was identified and a subset of the lighting devices failed to toggle in response to the toggle event.
0110The pre-stored command may operate as a predicted state change. The pre-stored command may attempt to predict the appropriate on/off state change to be sent in response to a toggle event in an effort to reduce latency caused by additional messages that may be sent if none of the lighting devices <b>112</b><i>a</i>, <b>112</b><i>b</i>, <b>122</b> changed state in response to the transmitted state command. As the remote control device <b>116</b> may be a battery-powered device, the remote control device <b>116</b> may be in a sleep mode and may miss the changes in on/off state of lighting devices.
0111The pre-stored command may be used to identify the on/off state at the lighting devices <b>112</b><i>a</i>, <b>112</b><i>b</i>, <b>122</b>. The on/off state of the lighting device <b>122</b> may be identified by the state update message indicating that the lighting device <b>122</b> changed from the “on” state to the “off” state in response to the “off” command. The on/off state of the lighting devices <b>112</b><i>a</i>, <b>112</b><i>b </i>may be identified by the lack of response to the “off” command.
0112The remote control device <b>116</b> may respond to the failure to receive a state update message from a subset of the lighting devices <b>112</b><i>a</i>, <b>112</b><i>b</i>, <b>122</b>. For example, the remote control device <b>116</b> may send an “off” command to the lighting devices <b>112</b><i>a</i>, <b>112</b><i>b</i>, <b>122</b> (e.g., in a unicast or multicast message). As the lighting device <b>122</b> may be in the “on” state, the lighting device <b>122</b> may change to the “off” state. The lighting device <b>122</b> may send a state update message to the remote control device <b>116</b>. As the lighting devices <b>112</b><i>a</i>, <b>112</b><i>b </i>may already be in the “off” state, the lighting devices <b>112</b><i>a</i>, <b>112</b><i>b </i>may fail to send a state update message. The remote control device <b>116</b> may identify the failure to receive a response from the lighting device <b>112</b><i>a </i>and/or lighting device <b>112</b><i>b </i>and may send an opposite state command (e.g., the “on” command or toggle command) to the group of lighting devices <b>112</b><i>a</i>, <b>112</b><i>b</i>, <b>122</b>. The opposite state command may be sent in a multicast message, or individual unicast messages, to the lighting devices <b>112</b><i>a</i>, <b>112</b><i>b</i>, <b>122</b> to toggle the group of lighting devices <b>112</b><i>a</i>, <b>112</b><i>b</i>, <b>122</b> together. The remote control device <b>116</b> may choose to send the opposite state command (e.g., the “on” command or toggle command), as the lighting devices <b>112</b><i>a</i>, <b>112</b><i>b </i>failed to change an on/off state in response to the toggle event.
0113The remote control device <b>116</b> may default to sending an “off” command or an “on” command in response to a toggle event. If the remote control device <b>116</b> receives a state update message from each of the group of lighting devices <b>112</b><i>a</i>, <b>112</b><i>b</i>, <b>122</b>, the remote control device <b>116</b> may determine that the lighting devices <b>112</b><i>a</i>, <b>112</b><i>b</i>, <b>122</b> have been toggled and fail to send a subsequent on/off command to toggle the lighting devices <b>112</b><i>a</i>, <b>112</b><i>b</i>, <b>122</b>. If the remote control device <b>116</b> fails to receive a state update message from a subset of the group of lighting devices <b>112</b><i>a</i>, <b>112</b><i>b</i>, <b>122</b>, the remote control device <b>116</b> may determine that one or more of the lighting devices <b>112</b><i>a</i>, <b>112</b><i>b</i>, <b>122</b> failed to toggle and the remote control device <b>116</b> may send the opposite state command to toggle the group of lighting devices <b>112</b><i>a</i>, <b>112</b><i>b</i>, <b>122</b>. When a lighting device <b>112</b><i>a</i>, <b>112</b><i>b</i>, <b>122</b> is out of sync, the first message sent by the remote control device <b>116</b> may act as a synchronization message. The next message may act to toggle the lighting devices <b>112</b><i>a</i>, <b>112</b><i>b</i>, <b>122</b>.
0114The load control system <b>100</b> may be configured to control the group of lighting devices <b>112</b><i>a</i>, <b>112</b><i>b</i>, <b>122</b> based on a current state of one or more of the group of lighting devices <b>112</b><i>a</i>, <b>112</b><i>b</i>, <b>122</b>, or a subset thereof. The remote control device <b>116</b> may identify a toggle event or a rotation event (e.g., a predefined distance or time in a direction) for controlling an intensity level of the lighting devices <b>112</b><i>a</i>, <b>112</b><i>b</i>, <b>122</b> and query the lighting devices <b>112</b><i>a</i>, <b>112</b><i>b</i>, <b>122</b> for their current state. The current state of the lighting devices <b>112</b><i>a</i>, <b>112</b><i>b</i>, <b>122</b> may include their on/off state and/or intensity level. The toggle event or the rotation event may cause the remote control device <b>116</b> to awaken from a sleep state. In addition, the remote control device <b>116</b> may be awakened from the sleep state in response to a sensing circuit (e.g., an occupancy sensing circuit and/or a proximity sensing circuit) sensing an occupant near the remote control device <b>116</b> (e.g., a proximity sensing event). In response to the toggle event, the rotation event, or the proximity sensing event, the remote control device <b>116</b> may attempt to query the lighting devices <b>112</b><i>a</i>, <b>112</b><i>b</i>, <b>122</b> with which the remote control device <b>116</b> is associated for their current state. The query message may request the on/off state (e.g., in response to a toggle event) and/or an intensity level (e.g., in response to a rotation) of the lighting devices <b>112</b><i>a</i>, <b>112</b><i>b</i>, <b>122</b>. The query message may be sent as a multicast message, or individual unicast messages, to each of the lighting devices <b>112</b><i>a</i>, <b>112</b><i>b</i>, <b>122</b>. The lighting devices <b>112</b><i>a</i>, <b>112</b><i>b</i>, <b>122</b> may return the current on/off state and/or intensity level, which may be stored locally thereon.
0115After sending the query message to the lighting devices <b>112</b><i>a</i>, <b>112</b><i>b</i>, <b>122</b> for their current state, the remote control device <b>116</b> may wait a predefined period of time for a response. Once the remote control device <b>116</b> receives a response to the query from any of the lighting devices <b>112</b><i>a</i>, <b>112</b><i>b</i>, <b>122</b>, the remote control device <b>116</b> may perform control of the group of lighting devices <b>112</b><i>a</i>, <b>112</b><i>b</i>, <b>122</b> based on the received response. For example, the remote control device <b>116</b> may receive a response to the query message from lighting device <b>112</b><i>a </i>(e.g., the first lighting device from which the remote control device receives a response) and send a digital message to control the group of lighting devices <b>112</b><i>a</i>, <b>112</b><i>b</i>, <b>122</b> based on the response received from the lighting device <b>112</b><i>a</i>. In addition, the remote control device <b>116</b> may wait for responses from all of the lighting devices <b>112</b><i>a</i>, <b>112</b><i>b</i>, <b>122</b> before sending a digital message to control the group of lighting devices <b>112</b><i>a</i>, <b>112</b><i>b</i>, <b>122</b> based on the responses received from all of the lighting devices.
0116The query messages may be sent to the lighting devices <b>112</b><i>a</i>, <b>112</b><i>b</i>, <b>122</b> as a multicast message or as unicast messages. After sending the query message, the remote control device <b>116</b> may wait a predefined period of time for a response message. The response message from the lighting device <b>112</b><i>a </i>may be the first message received in response to the query message. After receiving the first response message from the lighting device <b>112</b>, the remote control device <b>116</b> may stop waiting for the remaining lighting devices <b>112</b><i>a</i>, <b>122</b> to respond and may perform subsequent control based on the first response message received from the lighting device <b>112</b><i>a</i>. Performing control based on a first response to a query message may reduce time lag that may be caused by waiting for response messages from other devices.
0117The query message may be sent to the lighting devices <b>112</b><i>a</i>, <b>112</b><i>b</i>, <b>122</b> in sequence. For example, the query message requesting the current state of the lighting devices <b>112</b><i>a</i>, <b>112</b><i>b</i>, <b>122</b> may be sent as a unicast message to a first lighting device <b>112</b><i>a </i>of the group of lighting devices <b>112</b><i>a</i>, <b>112</b><i>b</i>, <b>122</b>. The remote control device <b>116</b> may wait a predefined period of time for a response message from the lighting device <b>112</b><i>a</i>. If the remote control device <b>116</b> fails to receive a response message within the predefined period of time, the remote control device <b>116</b> may send a query message for the current state of a subsequent lighting device in the sequence. When a response message is received from a lighting device, the remote control device <b>116</b> may stop sending query messages to lighting devices and perform subsequent control based on the response message received from the lighting device.
0118If a current status is unreceived from one or more of the lighting devices <b>112</b><i>a</i>, <b>112</b><i>b</i>, <b>122</b> after the expiration of the predefined period of time or the completion of the sequence of lighting devices, the remote control device <b>116</b> may send another query message or start another sequence (e.g., up to a predefined number of times prior to performing control). When the remote control device <b>116</b> fails to receive a response to a query message for the current state of a lighting device (e.g., after the predefined number of times prior to performing control), the remote control device <b>116</b> may perform control of the lighting devices <b>112</b><i>a</i>, <b>112</b><i>b</i>, <b>122</b> based on a locally stored state of one or more lighting devices <b>112</b><i>a</i>, <b>112</b><i>b</i>, <b>122</b> (e.g., on/off state or intensity level) or send a default command (e.g., default on/off command or intensity level).
0119The remote control device <b>116</b> may use the on/off state of a lighting device to implement toggle logic for the group of lighting devices <b>112</b><i>a</i>, <b>112</b><i>b</i>, <b>122</b>. For example, when the lighting device <b>112</b><i>a </i>responds to a query message indicating that the lighting device <b>112</b><i>a </i>is in the “off” state, the remote control device <b>116</b> may send a digital message to the group of lighting devices <b>112</b><i>a</i>, <b>112</b><i>b</i>, <b>122</b> to turn the group of lighting devices <b>112</b><i>a</i>, <b>112</b><i>b</i>, <b>122</b> to the “on” state. When the responding lighting device <b>112</b><i>a </i>is in the “on” state, the remote control device <b>116</b> may send a digital message to the group of lighting devices <b>112</b><i>a</i>, <b>112</b><i>b</i>, <b>122</b> to turn the group of lighting devices <b>112</b><i>a</i>, <b>112</b><i>b</i>, <b>122</b> to the “off” state. When the group of lighting devices <b>112</b><i>a</i>, <b>112</b><i>b</i>, <b>122</b> are in the same state, the group of lighting devices <b>112</b><i>a</i>, <b>112</b><i>b</i>, <b>122</b> may be controlled as a group. When the on/off state of the group of lighting devices <b>112</b><i>a</i>, <b>112</b><i>b</i>, <b>122</b> is out of sync, the on/off state of the lighting devices that are already in the state indicated in the digital message may go unchanged in response to the digital message from the remote control device <b>116</b>.
0120The remote control device <b>116</b> may use the intensity level of a lighting device as a starting point (e.g., a dynamic starting point) upon which dimming is performed for the group of lighting devices <b>112</b><i>a</i>, <b>112</b><i>b</i>, <b>122</b>. For example, in response to the query from the remote control device <b>116</b>, the lighting device <b>112</b><i>a </i>may respond that it is at a 10% intensity level. The remote control device <b>116</b> may set the intensity level identified by the lighting device <b>122</b> as the dynamic starting point upon which control of the intensity for the group of lighting devices <b>112</b><i>a</i>, <b>112</b><i>b</i>, <b>122</b> may be performed. The remote control device <b>116</b> may identify a continued rotation for increasing the intensity level by an additional 20%. The remote control device <b>116</b> may add this 20% to the dynamic starting point of 10% that was indicated as the current intensity level of the lighting device <b>112</b><i>a </i>that responded to the previous query message from the remote control device <b>116</b>. The remote control device <b>116</b> may send a digital message to the group of lighting devices <b>112</b><i>a</i>, <b>112</b><i>b</i>, <b>122</b> to control the group of lighting devices <b>112</b><i>a</i>, <b>112</b><i>b</i>, <b>122</b> to an absolute intensity level of 30%. The digital message may include a go-to-level command that is configured to control each of the lighting devices <b>112</b><i>a</i>, <b>112</b><i>b</i>, <b>122</b> to a 30% intensity level. Each of the lighting devices <b>112</b><i>a</i>, <b>112</b><i>b</i>, <b>122</b> may receive the digital message (e.g., as a unicast message or a multicast message) and be controlled to the absolute intensity level of 30%, unless the lighting device is already at the indicated intensity level. When the group of lighting devices <b>112</b><i>a</i>, <b>112</b><i>b</i>, <b>122</b> are in the same state, the group of lighting devices <b>112</b><i>a</i>, <b>112</b><i>b</i>, <b>122</b> may be controlled as a group. For example, the group of lighting devices <b>112</b><i>a</i>, <b>112</b><i>b</i>, <b>122</b> may be controlled together from 10% to 30%. When the state of the group of lighting devices <b>112</b><i>a</i>, <b>112</b><i>b</i>, <b>122</b> is out of sync, the lighting devices <b>112</b><i>a</i>, <b>112</b><i>b</i>, <b>122</b> may be controlled differently to reach the indicated intensity level. For example, the lighting devices <b>112</b><i>a</i>, <b>112</b><i>b</i>, <b>122</b> that are above the indicated intensity level may decrease in intensity to meet the indicated intensity level. The lighting devices <b>112</b><i>a</i>, <b>112</b><i>b</i>, <b>122</b> that are below the indicated intensity level may increase in intensity to meet the indicated intensity level. The lighting devices <b>112</b><i>a</i>, <b>112</b><i>b</i>, <b>122</b> that are already in the state indicated in the digital message may go unchanged in response to the digital message from the remote control device <b>116</b>.
0121The lighting devices <b>112</b><i>a</i>, <b>112</b><i>b</i>, <b>122</b> may fade from one intensity level to another intensity level (e.g., be dimmed between intensity levels over a fade time and/or at a fade rate) in response to receiving a command. For example, the lighting devices <b>112</b><i>a</i>, <b>112</b><i>b</i>, <b>122</b> may be dimmed at a rate or over a period of time such that each of the lighting devices <b>112</b><i>a</i>, <b>112</b><i>b</i>, <b>122</b> that is not already at the indicated intensity level reaches the intensity level at the same time. For example, the remote control device <b>116</b> may send the go-to-level command with an amount of time or fade rate over which the lighting devices <b>112</b><i>a</i>, <b>112</b><i>b</i>, <b>122</b> are to be dimmed until the lighting devices <b>112</b><i>a</i>, <b>112</b><i>b</i>, <b>122</b> reach the indicated intensity level (e.g., different fade rates or fade times may be transmitted to each of the lighting devices <b>112</b><i>a</i>, <b>112</b><i>b</i>, <b>122</b>). The lighting devices <b>112</b><i>a</i>, <b>112</b><i>b</i>, <b>122</b> may be dimmed over the indicated period of time to the intensity level indicated in the go-to-level command. When one or more of the lighting devices <b>112</b><i>a</i>, <b>112</b><i>b</i>, <b>122</b> are at different intensity levels, the lighting devices <b>112</b><i>a</i>, <b>112</b><i>b</i>, <b>122</b> may be sent unicast messages with different fade rates such that the lighting devices <b>112</b><i>a</i>, <b>112</b><i>b</i>, <b>122</b> at different intensity levels reach the intensity level indicated in the go-to-level command at the same time. The fade time may vary in a predetermined amount for each level the intensity may be increased or decreased.
0122The hub device <b>180</b> may operate as a master device that may be configured to monitor the state of slave devices, such as lighting devices <b>112</b><i>a</i>, <b>112</b><i>b</i>, <b>122</b>, and determine the appropriate command to be transmitted in response to a user interface event based on the state of the slave devices. Though the hub device <b>180</b> may be described herein as being a master device for controlling a group of lighting devices, other control devices (e.g., one of the lighting devices <b>112</b><i>a</i>, <b>112</b><i>b</i>, <b>122</b>, remote control device <b>150</b>, occupancy sensor <b>160</b>, daylight sensor <b>170</b>, network device <b>190</b>, motorized window treatment <b>132</b>, a remote computing device, etc.) may be assigned as a master device that operates as described herein for the hub device <b>180</b>. When a lighting device <b>112</b><i>a</i>, <b>112</b><i>b</i>, <b>122</b> is assigned as the master device, the lighting device <b>112</b><i>a</i>, <b>112</b><i>b</i>, <b>122</b> may already know its own state, but may monitor the state of other slave devices. Though other devices may operate as the master device, they may still communicate via the hub device <b>180</b>.
0123The hub device <b>180</b>, or another master device, may generate an appropriate command to synchronize the lighting devices <b>112</b><i>a</i>, <b>112</b><i>b</i>, <b>122</b> when the lighting devices <b>112</b><i>a</i>, <b>112</b><i>b</i>, <b>122</b> are out of sync. The master device may be configured with default commands that synchronize the lighting devices <b>112</b><i>a</i>, <b>112</b><i>b</i>, <b>122</b>. For example, in response to a toggle command, the master device may determine that one or more of the lighting devices <b>112</b><i>a</i>, <b>112</b><i>b</i>, <b>122</b> are on and transmit an off command to put the lighting devices <b>112</b><i>a</i>, <b>112</b><i>b</i>, <b>122</b> in the off state. In response to a toggle command, the master device may determine that one or more of the lighting devices <b>112</b><i>a</i>, <b>112</b><i>b</i>, <b>122</b> are off and transmit an on command to put the lighting devices <b>112</b><i>a</i>, <b>112</b><i>b</i>, <b>122</b> in the on state.
0124The hub device <b>180</b>, or another master device, may automatically synchronize and/or toggle the on/off state of the group of lighting devices <b>112</b><i>a</i>, <b>112</b><i>b</i>, <b>122</b>. The remote control device <b>116</b> may identify a toggle event and send a digital message to the hub device <b>180</b> indicating that the toggle event has been identified. The digital message may include a toggle command, an “on” command, or an “off” command. The remote control device <b>116</b> may switch between the transmission of the “on” command and the “off” command each time the remote control device <b>116</b> identifies a toggle event. The digital message may include another indication that the remote control device <b>116</b> identified the toggle event. The hub device <b>180</b> may generate the commands to be sent for controlling the lighting devices <b>112</b><i>a</i>, <b>112</b><i>b</i>, <b>122</b> in response to the messages received from the remote control device <b>116</b> and/or the other controller devices in the load control environment.
0125The hub device <b>180</b> may keep track of the on/off state of each of the lighting devices <b>112</b><i>a</i>, <b>112</b><i>b</i>, <b>122</b> after being implemented in the load control system <b>100</b>. Upon initial implementation into the load control system, the hub device <b>180</b> may query the lighting devices <b>112</b><i>a</i>, <b>112</b><i>b</i>, <b>122</b> for their current on/off state. The query message may be sent as a multicast message, or individual unicast messages, to each of the lighting devices <b>112</b><i>a</i>, <b>112</b><i>b</i>, <b>122</b>. The lighting devices <b>112</b><i>a</i>, <b>112</b><i>b</i>, <b>122</b> may return the current on/off state, which may be stored locally thereon. The hub device <b>180</b> may identify commands communicated to the lighting devices <b>112</b><i>a</i>, <b>112</b><i>b</i>, <b>122</b> and maintain the current on/off state of the lighting devices <b>112</b><i>a</i>, <b>112</b><i>b</i>, <b>122</b> in memory. The digital messages that are communicated to the lighting devices <b>112</b><i>a</i>, <b>112</b><i>b</i>, <b>122</b> for controlling the on/off state may be monitored to determine the current on/off state, without sending an initial query message. The hub device <b>180</b> may be powered and/or awake at all times (e.g., at all times than the lighting devices <b>112</b><i>a</i>, <b>112</b><i>b</i>, <b>122</b> are also powered), such that the hub device is able to monitor the states of the lighting devices by listening to the messages transmitted by the lighting devices. In addition, the hub device <b>180</b> may enter a sleep mode and periodically wake up to transmit query messages to the lighting devices <b>112</b><i>a</i>, <b>112</b><i>b</i>, <b>122</b> to determine the on/off states of the lighting devices.
0126The hub device <b>180</b> may also, or alternatively, send a synchronization message to the lighting devices <b>112</b><i>a</i>, <b>112</b><i>b</i>, <b>122</b> to synchronize the group and identify an initial state for each lighting device <b>112</b><i>a</i>, <b>112</b><i>b</i>, <b>122</b>. The synchronization message may include an “on” command or an “off” command instructing each of the lighting devices <b>112</b><i>a</i>, <b>112</b><i>b</i>, <b>122</b> to turn on or off, respectively. The lighting devices <b>112</b><i>a</i>, <b>112</b><i>b</i>, <b>122</b> that are in the opposite state may be toggled, while the lighting devices <b>112</b><i>a</i>, <b>112</b><i>b</i>, <b>122</b> that are already in the indicated on/off state may remain in the indicated state. The lighting devices that perform a change of on/off state may send a state update message to the hub device <b>180</b>.
0127When the hub device <b>180</b> receives an indication of a toggle event from the remote control device <b>116</b>, the hub device <b>180</b> may choose the command to send, or whether to send a command, to the lighting devices <b>112</b><i>a</i>, <b>112</b><i>b</i>, <b>122</b>. The decision at the hub device <b>180</b> may be based on the current on/off state of the lighting devices <b>112</b><i>a</i>, <b>112</b><i>b</i>, <b>122</b>. The hub device <b>180</b> may identify whether the on/off state across the group of lighting devices <b>112</b><i>a</i>, <b>112</b><i>b</i>, <b>122</b> is consistent. If the on/off state across the group of lighting devices <b>112</b><i>a</i>, <b>112</b><i>b</i>, <b>122</b> is consistent, the hub device <b>180</b> may send the toggle command, or an “on” command or “off” command, to the lighting devices <b>112</b><i>a</i>, <b>112</b><i>b</i>, <b>122</b> to toggle the on/off state of the group of lighting devices <b>112</b><i>a</i>, <b>112</b><i>b</i>, <b>122</b>.
0128The hub device <b>180</b> may identify when the on/off state of the group of lighting devices <b>112</b><i>a</i>, <b>112</b><i>b</i>, <b>122</b> is inconsistent. For example, the hub device <b>180</b> may identify a digital message from the remote control device <b>150</b> or the network device <b>190</b> that causes the lighting device <b>122</b> to change in on/off state independent of the other lighting devices <b>112</b><i>a</i>, <b>112</b><i>b</i>. If the on/off state across the group of lighting devices <b>112</b><i>a</i>, <b>112</b><i>b</i>, <b>122</b> is inconsistent, the hub device <b>180</b> may send a synchronization message to a subset of the lighting devices <b>112</b><i>a</i>, <b>112</b><i>b</i>, <b>122</b> to change the on/off state of the subset in response to an identification of a toggle event. For example, when the hub device <b>180</b> identifies the lighting device <b>122</b> is in an “on” state and that lighting devices <b>112</b><i>a</i>, <b>112</b><i>b </i>are each in the “off” state, the hub device <b>180</b> may send an “off” command to the lighting device <b>122</b> or an “on” command to the lighting devices <b>112</b><i>a</i>, <b>112</b><i>b </i>to synchronize the on/off state across the lighting devices <b>112</b><i>a</i>, <b>112</b><i>b</i>, <b>122</b>. The hub device <b>180</b> may send the synchronization message as a unicast message to the lighting devices to be changed. The hub device <b>180</b> may send the synchronization message as a multicast message that includes an identified state of the devices to be changed (e.g., lighting devices in an “on” state or an “off” state). The synchronization message may change the on/off state of the devices currently in an identified state and leave the on/off state of the other devices unchanged. The hub device <b>180</b> may send the toggle command in the synchronization message (e.g., as a unicast message) to the lighting devices to be changed.
0129The hub device <b>180</b> may send a synchronization message to change the on/off state of a preferred subset of lighting devices. The hub device <b>180</b> may send the synchronization message to change the on/off state of the subset of devices having the lesser number of devices for which the on/off state is to be changed, as such a change may be less noticeable and may cause less messages to be sent in some instances. The hub device <b>180</b> may default to “turning off” a subset of lighting devices. For example, when the lighting devices <b>112</b><i>a</i>, <b>112</b><i>b</i>, <b>122</b> are out of sync, the hub device <b>180</b> may send a synchronization message (e.g., via unicast or multicast) to the group of lighting devices <b>112</b><i>a</i>, <b>112</b><i>b</i>, <b>122</b> that includes an “off” command to tell the group of lighting devices <b>112</b><i>a</i>, <b>112</b><i>b</i>, <b>122</b> to turn off. The hub device <b>180</b> may default to “turning on” a subset of lighting devices. For example, the hub device <b>180</b> may send a synchronization message (e.g., via unicast or multicast) to the group of lighting devices <b>112</b><i>a</i>, <b>112</b><i>b</i>, <b>122</b> that includes an “on” command to tell the group of lighting devices <b>112</b><i>a</i>, <b>112</b><i>b</i>, <b>122</b> to turn on.
0130The hub device <b>180</b> may send a digital message after the synchronization message to control the group of synchronized lighting devices <b>112</b><i>a</i>, <b>112</b><i>b</i>, <b>122</b>. The hub device <b>180</b> may receive a response to the synchronization message that indicates the state of each of the devices, or each of the devices that changed state in response to the synchronization message. The hub device <b>180</b> may send a digital message after the synchronization message to toggle the group of lighting devices <b>112</b><i>a</i>, <b>112</b><i>b</i>, <b>122</b>. For example, after the hub device <b>180</b> toggles the on/off state of the lighting device <b>122</b> to the “off” state, the hub device <b>180</b> may send an “on” command or a toggle command to the group of lighting devices <b>112</b><i>a</i>, <b>112</b><i>b</i>, <b>122</b>. Such a command may be sent after the synchronization message is sent, or after receiving a state update message in response to the synchronization message.
0131The hub device <b>180</b> may send a synchronization message and wait for an indication of a subsequent toggle event from the remote control device <b>116</b>. After receiving the indication of the toggle event, the hub device <b>180</b> may determine whether the group of lighting devices <b>112</b><i>a</i>, <b>112</b><i>b</i>, <b>122</b> are in a consistent state. When the group of lighting devices <b>112</b><i>a</i>, <b>112</b><i>b</i>, <b>122</b> are in a consistent state (e.g., “on” or “off” state), the hub device <b>180</b> may send a toggle command, or an “on” or “off” command, to toggle the state of the group of lighting devices <b>112</b><i>a</i>, <b>112</b><i>b</i>, <b>122</b>.
0132The lighting devices <b>112</b><i>a</i>, <b>112</b><i>b</i>, <b>122</b> that change an on/off state in response to an “on” command or an “off” command may send a state update message to the hub device <b>180</b> to indicate the change in on/off state. The hub device <b>180</b> may receive the state update message from the lighting devices <b>112</b><i>a</i>, <b>112</b><i>b</i>, <b>122</b> that change state in response to the received “on” command or the received “off” command. The lighting devices that fail to change the on/off state in response to the command from the hub device <b>180</b> may be unresponsive. For example, the hub device <b>180</b> may send an “off” command to the lighting devices <b>112</b><i>a</i>, <b>112</b><i>b</i>, <b>122</b> and the lighting device <b>122</b> may update the on/off state to the “off” state. The lighting device <b>122</b> may send a response message to the hub device <b>180</b> to indicate the change in state. The hub device <b>180</b> may store the updated state and/or confirm the state of the unresponsive devices. The hub device <b>180</b> may, alternatively, store the updated state of the lighting device <b>122</b> after sending the command. As the hub device <b>180</b> may be maintaining the on/off state of the lighting devices <b>112</b><i>a</i>, <b>112</b><i>b</i>, <b>122</b>, the remote control device <b>116</b> may go to sleep after transmitting a message in response to the toggle event.
0133The remote control device <b>116</b> may receive an indication when the hub device <b>180</b> and/or other control devices are implemented in the load control system <b>100</b>. The remote control device <b>116</b> may be associated with other controller devices (e.g., remote control device <b>150</b>, occupancy sensor <b>160</b>, daylight sensor <b>170</b>, network device <b>190</b>, etc.), or may be otherwise notified when the controller devices are associated with another device (e.g., a lighting device <b>112</b><i>a</i>, <b>112</b><i>b</i>, <b>122</b> or the hub device <b>180</b>) in the load control system <b>100</b>. The remote control device <b>116</b> may be associated with the hub device <b>180</b>, or may be otherwise notified (e.g., via a message from the hub device <b>180</b>, a notification of association from a lighting device <b>112</b><i>a</i>, <b>112</b><i>b</i>, <b>122</b> that associated with the hub device <b>180</b>, etc.) when the hub device <b>180</b> is implemented into the system <b>100</b>.
0134The remote control device <b>116</b> may provide feedback via the status indicator <b>117</b> in different feedback modes based information regarding the control devices to which the remote control device is associated. The decision on type of feedback provided by the status indicator <b>119</b> may be made at the time of association of the remote control device <b>116</b> and stored at the remote control device <b>116</b>. The decision on the type of feedback provided by the status indicator <b>119</b> may be made dynamically. For example, the type of feedback displayed via the status indicator <b>119</b> may change depending on the information determined in response to a query message sent to the lighting devices <b>112</b><i>a</i>, <b>112</b><i>b</i>, <b>122</b>, other load control devices, and/or the hub device <b>180</b>. The query message may be sent in response to an actuation on the remote control device <b>116</b>. The remote control device <b>116</b> may wake up in response to an actuation and ping associated lighting devices <b>112</b><i>a</i>, <b>112</b><i>b</i>, <b>122</b>, other load control devices, or a hub device <b>180</b> to determine a status of the electrical loads controlled by the associated load control devices.
0135The decision on the type of feedback provided by the status indicator <b>119</b> may be made at the remote control device <b>116</b> or at another device. For example, the decision on the type of feedback provided by the status indicator <b>119</b> may be made at a master device, such as the hub device <b>180</b> or one of the lighting devices <b>112</b><i>a</i>, <b>112</b><i>b</i>, <b>122</b>. The master device may query the load control devices for a given status, or maintain the status of the electrical loads locally based on feedback messages or messages being communicated for control of the electrical loads. When the remote control device <b>116</b> is being associated or awakens from a sleep state, a request may be sent to the master device for the type of feedback to be provided by the status indicator <b>119</b>. The type of feedback may be selected by a user or by the master device based on predefined rules and sent to the remote control device <b>116</b>. The remote control device <b>116</b> may then provide the type of feedback on the status indicator <b>119</b> that is received in the response.
0136As indicated above, the type of visual feedback may be user configurable. The network device <b>190</b> may configure the operation of the remote control device <b>116</b> (e.g., configure the feedback type used by the remote control device) without directly communicating with the remote control device <b>116</b>. For example, the network device <b>190</b> may display different feedback types to a user. The network device <b>190</b> may receive a selection of a feedback type from the user and communicate the selected feedback type via RF signals <b>108</b> to a master device, such as the hub device <b>180</b> or another master device (e.g., one of the lighting devices <b>112</b><i>a</i>, <b>112</b><i>b</i>, <b>122</b>). The user may select between simple feedback or advanced feedback for a given scenario (e.g., a number of associated devices, when the electrical loads are in sync our out of sync, when the remote control device <b>116</b> is associated with a master device or not associated with a master device, etc.), as described herein. The user may also select between different types of simple feedback or different types of advanced feedback for a given scenario (e.g., as will be described in greater detail below).
0137The user may choose between different intensity levels or colors to be provided via the status indicator <b>119</b> for different feedback types. The intensity levels or colors may correspond to different load control devices for which the feedback is being provided. For example, a different intensity level may be provided for the light source of the status indicator <b>119</b> when the feedback corresponds to light levels, volume levels, and/or fan speeds. A different color may be provided for the light source of the status indicator <b>119</b> when the feedback corresponds to light levels, volume levels, and/or fan speeds.
0138The master device may store the user-selected feedback type for being provided for the scenario in which the feedback type was selected (e.g., a number of associated devices, when the electrical loads are in sync our out of sync, when the remote control device <b>116</b> is associated with a master device or not associated with a master device, etc.). The remote control device <b>116</b> may retrieve the feedback type from the master device when the remote control device <b>116</b> next queries the master device. The remote control device <b>116</b> may store the feedback type in memory for future use when the corresponding scenario exists. The remote control device <b>116</b> may query for the feedback type each time the feedback is to be provided on the status indicator <b>119</b>.
0139Since the network device <b>190</b> is configured to store the selected feedback type on the master device for later retrieval by the remote control device <b>116</b> (e.g., in response to an actuation of the actuation portion <b>117</b> and/or the rotation portion <b>118</b>), the remote control device <b>116</b> does not need to provide a way for communicating directly with the network device <b>190</b>. For example, the remote control device <b>116</b> does not need to wake up periodically to determine if the network device <b>190</b> is attempting to communicate with the remote control device, which could lead to increased battery consumption and reduced life of the battery of the remote control device. This method of configuring the operation of the remote control device <b>116</b> could be used to configure other operating parameters of the remote control device <b>116</b>.
0140The remote control device <b>116</b> may operate to provide different types of feedback (e.g., advanced feedback or simple feedback) based on information about the associated devices. For example, the remote control device <b>116</b> may provide different feedback on the status indicator <b>119</b> when associated with a master device, such as the hub device <b>180</b> or other master device, than when not associated with the master device. The remote control device <b>116</b> may provide advanced feedback on the status indicator <b>119</b> when associated with the hub device <b>180</b> that is capable of providing the status of load control devices to the remote control device <b>116</b>. The remote control device <b>116</b> may provide simple feedback on the status indicator <b>119</b> when not associated with the hub device <b>180</b>.
0141The remote control device <b>116</b> may provide feedback via the status indicator <b>119</b> in different feedback modes based on whether the remote control device <b>116</b> is associated with the hub device <b>180</b> or another master device, such as one of the lighting devices <b>112</b><i>a</i>, <b>112</b><i>b</i>, <b>122</b>, for example. The remote control device <b>116</b> may provide advanced feedback when associated with a master device and provide simple feedback when not associated with a master device. When the remote control device <b>116</b> is associated with a master lighting device, the remote control device <b>116</b> may provide advanced feedback on the status indicator <b>119</b> and display the state of the master lighting device as feedback on the status indicator <b>119</b>. As the master device may synchronize the state of the lighting devices <b>112</b><i>a</i>, <b>112</b><i>b</i>, <b>122</b>, the remote control device <b>116</b> may provide advanced feedback that indicates an intensity level of the synchronized group of lighting devices <b>112</b><i>a</i>, <b>112</b><i>b</i>, <b>122</b>. In addition, the master device may collect and store the intensity levels of the group of lighting devices <b>112</b><i>a</i>, <b>112</b><i>b</i>, <b>122</b>, and may decide the level to display for advanced feedback if the lighting devices are out of sync. When the remote control device <b>116</b> is not associated with a master device, the remote control device <b>116</b> may provide simple feedback that illuminates the entire status indicator <b>119</b> to different levels when raising or lowering intensity of lighting devices <b>112</b><i>a</i>, <b>112</b><i>b</i>, <b>122</b>, or when the lighting devices <b>112</b><i>a</i>, <b>112</b><i>b</i>, <b>122</b> are on or off.
0142When the remote control device <b>116</b> is operating in the load control system <b>100</b> without other controller devices or the hub device <b>180</b>, the remote control device <b>116</b> may trust that an internally stored on/off state matches that of the lighting devices <b>112</b><i>a</i>, <b>112</b><i>b</i>, <b>122</b>. The remote control device <b>116</b> may send a toggle command or an on/off command in the next message transmitted in response to a toggle event to toggle the group of lighting devices <b>112</b><i>a</i>, <b>112</b><i>b</i>, <b>122</b>.
0143Though the remote control device <b>116</b> may be operating in the load control system <b>100</b> with other controller devices, the other controller devices may not be associated with the group of lighting devices <b>112</b><i>a</i>, <b>112</b><i>b</i>, <b>122</b> that are associated with the remote control device <b>116</b>. As the other controller devices may not be associated with the group of lighting devices <b>112</b><i>a</i>, <b>112</b><i>b</i>, <b>122</b>, the other controller devices may be unable to toggle the on/off state of the lighting devices <b>112</b><i>a</i>, <b>112</b><i>b</i>, <b>122</b>. The remote control device <b>116</b> may determine whether other controller devices are associated with the lighting devices <b>112</b><i>a</i>, <b>112</b><i>b</i>, <b>122</b> by querying the lighting devices <b>112</b><i>a</i>, <b>112</b><i>b</i>, <b>122</b> for associated devices. Each lighting device <b>112</b><i>a</i>, <b>112</b><i>b</i>, <b>122</b> may respond with the unique identifiers of devices associated with the device. The unique identifiers may indicate devices or device types (e.g., remote control devices, occupancy sensors, daylight sensors, network devices, hub devices, etc.) associated with the lighting devices <b>112</b><i>a</i>, <b>112</b><i>b</i>, <b>122</b>.
0144Each controller device may be associated with a lighting device <b>112</b><i>a</i>, <b>112</b><i>b</i>, <b>122</b> by sending a unique group identifier to the lighting device <b>112</b><i>a</i>, <b>112</b><i>b</i>, <b>122</b> while the lighting device <b>112</b><i>a</i>, <b>112</b><i>b</i>, <b>122</b> is in an association mode. The group of associated devices may have stored thereon the unique group identifier of the controller device. Other controller devices may query the lighting devices <b>112</b><i>a</i>, <b>112</b><i>b</i>, <b>122</b> to determine whether they are in the group of devices that may be controlled by messages (e.g., unicast or multicast messages) sent to the group. For example, remote control device <b>116</b> may query the lighting devices <b>112</b><i>a</i>, <b>112</b><i>b</i>, <b>122</b> for the group identifiers of other controller devices. The lighting device <b>122</b> may respond with the group identifier for the remote control device <b>150</b> and/or the network device <b>190</b>, which may be previously associated with the lighting device <b>122</b>. As the lighting devices <b>112</b><i>a</i>, <b>112</b><i>b </i>may be unassociated with other controller devices, or other controller devices of a specific device type (e.g., devices capable of toggling on/off state), the remote control device <b>116</b> may keep track of the on/off state of the lighting devices <b>112</b><i>a</i>, <b>112</b><i>b </i>and toggle the lighting devices <b>112</b><i>a</i>, <b>112</b><i>b </i>by sending a toggle command or opposing on/off commands in the next message transmitted in response to a toggle event. The remote control device <b>116</b> may operate as otherwise described herein with regard to the lighting device <b>122</b>, as the on/off state of the lighting device <b>122</b> may be out of sync with the lighting devices <b>112</b><i>a</i>, <b>112</b><i>b </i>due to the independent control of other controller devices.
0145The remote control device <b>116</b> may poll the associated lighting devices <b>112</b><i>a</i>, <b>112</b><i>b</i>, <b>122</b> for other associated controller devices after the expiration of a predetermined time interval. For example, the remote control device <b>116</b> may poll an associated lighting device <b>112</b><i>a</i>, <b>112</b><i>b</i>, <b>122</b> periodically for a predefined number of polling requests after associating with the lighting device <b>112</b><i>a</i>, <b>112</b><i>b</i>, <b>122</b>. The polling requests may be overridden by an actuation on the remote control device. The remote control device <b>116</b> may identify the override of the polling requests and assume that the internal on/off state of the associated lighting devices <b>112</b><i>a</i>, <b>112</b><i>b</i>, <b>122</b> is correct.
0146Though the remote control device <b>116</b> and/or the hub device <b>180</b> may be described for synchronizing and/or toggling the lighting devices <b>112</b><i>a</i>, <b>112</b><i>b</i>, <b>122</b>, other controller devices in the load control system <b>100</b> may be similarly implemented for synchronizing and/or toggling the lighting devices <b>112</b><i>a</i>, <b>112</b><i>b</i>, <b>122</b>. For example, the toggle event may be identified by the occupancy sensor <b>160</b> detecting an occupancy or vacancy condition in the load control environment <b>100</b>. The occupancy sensor <b>160</b> may transmit commands for synchronizing and/or toggling the lighting devices <b>112</b><i>a</i>, <b>112</b><i>b</i>, <b>122</b> in response to the toggle event, as described herein. The toggle event may be identified by the daylight sensor <b>170</b> detecting a daylight level above a predefined threshold in the load control environment <b>100</b>. The daylight sensor <b>170</b> may transmit commands for synchronizing and/or toggling the lighting devices <b>112</b><i>a</i>, <b>112</b><i>b</i>, <b>122</b> in response to the toggle event, as described herein.
0147<figref idref="DRAWINGS">FIGS. 2A and 2B</figref> are system flow diagrams depicting example message flows for communicating digital messages between a remote control device <b>202</b> and lighting devices <b>204</b><i>a</i>, <b>204</b><i>b </i>in a load control system. As shown in <figref idref="DRAWINGS">FIG. 2A</figref>, the remote control device <b>202</b> may transmit digital messages to toggle the on/off state of the lighting devices <b>204</b><i>a</i>, <b>204</b><i>b</i>. The digital messages may be used to synchronize the lighting devices <b>204</b><i>a</i>, <b>204</b><i>b</i>, or control the lighting devices <b>204</b><i>a</i>, <b>204</b><i>b </i>when they are in sync.
0148The remote control device <b>202</b> may store of the state of the lighting devices <b>204</b><i>a</i>, <b>204</b><i>b</i>. The remote control device <b>202</b> may maintain the state of the lighting devices <b>204</b><i>a</i>, <b>204</b><i>b </i>while the remote control device <b>202</b> is awake. When the state of the lighting devices <b>204</b><i>a</i>, <b>204</b><i>b </i>are out of sync, the remote control device <b>202</b> may send a digital message (e.g., including a toggle command, an intensity level, color, etc.) to synchronize the state of the lighting devices <b>204</b><i>a</i>, <b>204</b><i>b</i>. After determining the lighting devices <b>204</b><i>a</i>, <b>204</b><i>b </i>are in sync, the remote control device <b>202</b> may change the internally stored state of the lighting devices <b>204</b><i>a</i>, <b>204</b><i>b </i>to reflect any change of state. For example, the remote control device may flip the internal state of the lighting devices <b>204</b><i>a</i>, <b>204</b><i>b </i>in response to transmission of a toggle command, and/or receipt of a status message. The remote control device <b>202</b> may send a default command after awakening from a sleep mode and, after determining and storing the current state of the lighting devices <b>204</b><i>a</i>, <b>204</b><i>b </i>thereon, flip the current state of each of the lighting devices <b>204</b><i>a</i>, <b>204</b><i>b </i>stored thereon after transmission of each subsequent toggle command while the remote control device <b>202</b> remains awake.
0149Prior to the remote control device <b>202</b> transmitting an initial message (e.g., after awakening from a sleep state), an initial state of the lighting devices <b>204</b><i>a</i>, <b>204</b><i>b </i>may be out of sync. For example, the lighting device <b>204</b><i>a </i>may be in an off state and the lighting device <b>204</b><i>b </i>may be in an on state. The remote control device <b>202</b> may identify a user interface event (e.g., actuation, rotation, finger swipe, etc.) as a toggle event and transmit a default toggle command, such as an on command <b>206</b>, as an initial message (e.g., after awakening from a sleep state). The on command <b>206</b> may be a default command transmitted from the remote control device <b>202</b> or may be determined from the internally stored state of the lighting devices <b>204</b><i>a</i>, <b>204</b><i>b</i>. The on command <b>206</b> may be sent as a multicast message or individual unicast messages that are received by the lighting devices <b>204</b><i>a</i>, <b>204</b><i>b</i>. Though a toggle event and a toggle command are provided as examples, other user interface events and/or commands may be implemented. For example, a user interface event may be identified for increasing/decreasing an intensity level and a go-to-level command may be transmitted for increasing/decreasing the intensity level. Additionally, though <figref idref="DRAWINGS">FIG. 2A</figref> illustrates an on command <b>206</b> being transmitted as the initial message for synchronization of the lighting devices <b>204</b><i>a</i>, <b>204</b><i>b</i>, the remote control device <b>202</b> may initially transmit an off command or another command.
0150The lighting devices that change in state after receiving the on command <b>206</b> may send a state update message to the remote control device <b>202</b>. For example, as the lighting device <b>204</b><i>a </i>is in the off state, the lighting device <b>204</b><i>a </i>may turn to the on state in response to receiving the on command <b>206</b> and send a state update message <b>208</b> to the remote control device <b>202</b>. The state update message may indicate the updated state of the lighting device <b>204</b><i>a</i>, or the updated state may be inferred from receipt of the state update message <b>208</b>. As the remote control device <b>202</b> does not receive a state update message from the lighting device <b>204</b><i>b</i>, the remote control device <b>202</b> may assume that the lighting device <b>204</b><i>b </i>is already in the on state.
0151The remote control device <b>202</b> may operate as though the on command <b>206</b> is a synchronization message that synchronizes the lighting devices <b>204</b><i>a</i>, <b>204</b><i>b</i>. After transmitting the on command <b>206</b> and receiving the state update message <b>208</b>, the remote control device <b>202</b> may identify user interface events (e.g., actuations, rotations, finger swipes, etc.) and transmit digital messages to control the lighting devices <b>204</b><i>a</i>, <b>204</b><i>b </i>in response to those user interface events. The remote control device <b>202</b> may continue to update the internally stored state of the lighting devices <b>204</b><i>a</i>, <b>204</b><i>b </i>as the state of the devices changes.
0152As shown in <figref idref="DRAWINGS">FIG. 2B</figref>, the remote control device <b>202</b> may transmit one or more digital messages that include default commands to lighting device <b>204</b><i>a</i>, <b>204</b><i>b</i>. For example, the remote control device <b>202</b> may transmit a default toggle command, such as an on command <b>210</b>, to the lighting devices <b>204</b><i>a</i>, <b>204</b><i>b </i>as an initial command after a user interface event (e.g., after awakening from a sleep state in response to an actuation, rotation, finger swipe, etc.). As the lighting devices <b>204</b><i>a</i>, <b>204</b><i>b </i>may already be in the on state, the lighting devices <b>204</b><i>a</i>, <b>204</b><i>b </i>may be unresponsive to the on command <b>210</b>. When the remote control device <b>202</b> fails to receive a state update message in response to the on command <b>210</b> after a predetermined period of time, or fails to receive a state update message from each associated lighting device <b>204</b><i>a</i>, <b>204</b><i>b </i>after a predetermined period of time, the remote control device <b>202</b> may transmit the opposite command or another command. For example, the remote control device <b>202</b> may transmit the off command <b>212</b> after the remote control device <b>202</b> fails to receive a state update message in response to the on command <b>210</b>. The on command <b>210</b> and/or the off command <b>212</b> may be sent as a multicast message or individual unicast messages that are received by the lighting devices <b>204</b><i>a</i>, <b>204</b><i>b. </i>
0153The lighting devices that change in state after receiving the on command <b>210</b> or the off command <b>212</b> may send a state update message to the remote control device <b>202</b>. As the lighting devices <b>204</b><i>a</i>, <b>204</b><i>b </i>are in an on state, the lighting devices <b>204</b><i>a</i>, <b>204</b><i>b </i>may change to an off state and respond to the off command <b>212</b> and transmit respective state update messages <b>214</b>, <b>216</b>. The state update message may indicate the updated state of the lighting devices <b>204</b><i>a</i>, <b>204</b><i>b </i>or the updated state may be inferred from receipt of the state update messages <b>214</b>, <b>216</b>.
0154After receiving the state update messages <b>214</b>, <b>216</b>, the remote control device <b>202</b> may identify user interface events (e.g., actuations, rotations, finger swipes, etc.) and transmit digital messages to control the lighting devices <b>204</b><i>a</i>, <b>204</b><i>b </i>in response to those user interface events. Though <figref idref="DRAWINGS">FIG. 2B</figref> illustrates an on command <b>210</b> being transmitted as the initial message from the remote control device <b>202</b>, the remote control device <b>202</b> may initially transmit an off command or another command.
0155<figref idref="DRAWINGS">FIGS. 3A-3D</figref> are system flow diagrams depicting example message flows for generating lighting control commands in response to an actuation of an actuator (e.g., the actuation portion <b>117</b> and/or the rotation portion <b>118</b> of the remote control device <b>116</b>) and/or a sensing circuit sensing an occupant near the remote control device <b>116</b> (e.g., a proximity sensing event). <figref idref="DRAWINGS">FIGS. 3A-3C</figref> depict example message flows for querying for a current status of lighting devices in response to an actuation of a toggle actuator (e.g., the actuation portion <b>117</b>) and generating lighting control commands in response to the identified status. As shown in <figref idref="DRAWINGS">FIG. 3A</figref>, a remote control device <b>302</b> may transmit a status query message <b>306</b> for identifying the status of lighting devices, such as lighting devices <b>304</b><i>a</i>, <b>304</b><i>b</i>. The status query message <b>306</b> may be transmitted as an initial message (e.g., after awakening from a sleep state) after identifying a user interface event (e.g., actuation, rotation, finger swipe, etc.) and/or a proximity sensing event (e.g., a sensing circuit sensing an occupant near the remote control device <b>116</b>). The status query message <b>306</b> may be sent as a multicast message or individual unicast messages that are received by the lighting devices <b>304</b><i>a</i>, <b>304</b><i>b. </i>
0156The remote control device <b>302</b> may receive a response to the status query message <b>306</b> from each of the lighting devices <b>304</b><i>a</i>, <b>304</b><i>b </i>that receive the status query message <b>306</b> and/or with which the remote control device <b>302</b> is associated. For example, the lighting device <b>304</b><i>a </i>may transmit a status message <b>308</b> in response to the status query message <b>306</b> that indicates that the lighting device <b>304</b><i>a </i>is in the off state. The lighting device <b>304</b><i>b </i>may transmit a status message <b>310</b> in response to the status query message <b>306</b> that indicates that the lighting device <b>304</b><i>b </i>is in the on state. The status messages may also, or alternatively, indicate an intensity, color, or other status of the lighting device from which the status message is transmitted.
0157If the remote control device <b>302</b> determines that any of the lighting devices <b>304</b><i>a</i>, <b>304</b><i>b </i>are in the on state, the remote control device <b>302</b> may be configured to transmit a default toggle command, such as the off command <b>312</b>. The off command <b>312</b> may be sent as a multicast message or individual unicast messages that are received by the lighting devices <b>304</b><i>a</i>, <b>304</b><i>b</i>. Though an off command <b>312</b> may be transmitted as the default toggle command as shown in <figref idref="DRAWINGS">FIG. 3A</figref>, the remote control device <b>302</b> may transmit an on command or another default command in response to identifying a status of one or more of the lighting devices <b>304</b><i>a</i>, <b>304</b><i>b. </i>
0158The remote control device <b>302</b> may determine that the state of the lighting devices <b>304</b><i>a</i>, <b>304</b><i>b </i>is out of sync and may transmit a synchronization message to synchronize the state of the lighting devices <b>304</b><i>a</i>, <b>304</b><i>b</i>. For example, the remote control device <b>302</b> may send the off command <b>312</b> to synchronize the state of the lighting devices <b>304</b><i>a</i>, <b>304</b><i>b</i>. The synchronization message may include a command to control the lighting device <b>304</b><i>b </i>to the state of the lighting device <b>304</b><i>a</i>, or vice versa. Though an off command <b>312</b> may be transmitted as the synchronization message, the remote control device <b>302</b> may transmit an on command or another command to perform synchronization.
0159The lighting device <b>304</b><i>b </i>may turn to the off state in response to receiving the off command <b>312</b> and send a state update message <b>314</b> to the remote control device <b>302</b>. The state update message <b>316</b> may indicate the updated state of the lighting device <b>304</b><i>b</i>, or the updated state may be inferred from receipt the state update message <b>314</b> itself. As the lighting device <b>304</b><i>a </i>may already be in the off state, the lighting device <b>304</b><i>a </i>may be unresponsive to the off command <b>312</b>. This may limit unnecessary network communications in the system. The remote control device <b>302</b> may continue to identify user interface events and/or proximity sensing events, and control the lighting devices <b>304</b><i>a</i>, <b>304</b><i>b </i>in response to the user interface events and/or proximity sensing events.
0160The remote control device <b>302</b> may determine the control instructions for being sent to the lighting devices <b>304</b><i>a</i>, <b>304</b><i>b </i>based on the status of one of the lighting devices <b>304</b><i>a</i>, <b>304</b><i>b</i>. For example, the remote control device <b>302</b> may determine the control instructions for being sent to the lighting devices <b>304</b><i>a</i>, <b>304</b><i>b </i>based on the status of a master lighting device or a lighting device that is first to respond to the status query message <b>306</b>. The remote control device <b>302</b> may control the state of both of the lighting devices, <b>304</b><i>a</i>, <b>304</b><i>b </i>to respond to the status query message by sending a command to toggle the lighting devices, or may toggle the other lighting devices in order to synchronize the other devices with the state of the master lighting device or the first lighting device to respond.
0161The remote control device <b>302</b> may respond to the status of the first lighting device <b>304</b><i>a</i>, <b>304</b><i>b </i>to respond to a status query message. As shown in <figref idref="DRAWINGS">FIG. 3B</figref> a status query message <b>320</b> may be sent as a unicast message to each lighting device <b>304</b><i>a</i>, <b>304</b><i>b</i>, or as a multicast message. The lighting device <b>304</b><i>a </i>may be the first device to receive the status query message <b>320</b> and/or from which a status message <b>322</b> is received in response. The status message <b>322</b> may indicate the status of the lighting device <b>304</b><i>a</i>, which may cause the remote control device <b>302</b> to send the opposite command (e.g., the on command <b>324</b>). The on command <b>324</b> may be sent as a unicast or multicast message. As the lighting device <b>304</b><i>a </i>is updated, the status update message <b>326</b> may be received at the remote control device <b>302</b>.
0162As shown in <figref idref="DRAWINGS">FIG. 3C</figref> a status query message <b>330</b> may be sent as a unicast message to each lighting device <b>304</b><i>a</i>, <b>304</b><i>b</i>, or as a multicast message. The lighting device <b>304</b><i>b </i>may be the first device to receive the status query message <b>330</b> and/or from which a status message <b>332</b> is received in response. The status message <b>332</b> may indicate the status of the lighting device <b>304</b><i>b</i>, which may cause the remote control device <b>302</b> to send the opposite command (e.g., the off command <b>334</b>). The off command <b>334</b> may be sent as a unicast or multicast message. As the lighting device <b>304</b><i>b </i>is updated, the status update message <b>336</b> may be received at the remote control device <b>302</b>. The examples shown in <figref idref="DRAWINGS">FIGS. 3B and 3C</figref> may be implemented to synchronize the lighting devices <b>304</b><i>a</i>, <b>304</b><i>b </i>more quickly, as the remote control device <b>302</b> may respond to the status of the first device from which a response is received.
0163Though not shown in <figref idref="DRAWINGS">FIG. 3B</figref>, the remote control device <b>302</b> may scan for lighting devices <b>304</b><i>a</i>, <b>304</b><i>b </i>in a preferred state (e.g., on/off state, lighting intensity, color, etc.). The remote control device <b>302</b> may send the status query message as a unicast message to each of the lighting devices <b>304</b><i>a</i>, <b>304</b><i>b </i>or as a multicast message to both lighting devices <b>304</b><i>a</i>, <b>304</b><i>b</i>. The remote control device <b>302</b> may continue to send a status query message to each of the lighting devices <b>304</b><i>a</i>, <b>304</b><i>b </i>until one of the lighting devices returns a non-preferred state. For example, remote control device <b>302</b> may send the status query message <b>306</b> to the lighting device <b>304</b><i>a </i>and receive the status message <b>308</b> prior to sending a status query message to the lighting device <b>304</b>. The remote control device <b>302</b> may stop scanning for lighting devices when the remote control device <b>302</b> receives a status message from a lighting device that identifies the lighting device as being in a non-preferred state (e.g., state other than the preferred on/off state, lighting intensity, color, etc.), or when the remote control device <b>302</b> has scanned each lighting device.
0164The remote control device <b>302</b> may transmit a status query message that requests a response from lighting devices in a particular state. For example, as shown in <figref idref="DRAWINGS">FIG. 3B</figref>, the remote control device <b>302</b> may transmit a status query message <b>320</b> that requests a response from lighting devices in the off state. The status query message <b>320</b> may be transmitted as an initial message (e.g., after awakening from a sleep state) after identifying a user interface event (e.g., actuation, rotation, finger swipe, etc.) and/or a proximity sensing event (e.g., a sensing circuit sensing an occupant near the remote control device <b>116</b>). The status query message <b>320</b> may be a multicast message or individual unicast messages by the lighting devices <b>304</b><i>a</i>, <b>304</b><i>b </i>with which the remote control device <b>302</b> may be associated.
0165As the lighting device <b>304</b><i>a </i>is in the off state, the lighting device <b>304</b><i>a </i>may respond with a status message <b>322</b> that indicates that the lighting device <b>304</b><i>a </i>is in the off state. The status message <b>322</b> may identify that the lighting device <b>304</b><i>a </i>is in the off state, or the transmission of the status message <b>322</b> itself may indicate that the lighting device <b>304</b><i>a </i>is in the off state. As the lighting device <b>304</b><i>b </i>is in the on state, the lighting device <b>304</b><i>b </i>may be unresponsive to the status query message <b>320</b>.
0166The remote control device <b>302</b> may receive a response to the status query message <b>320</b> from the lighting device <b>304</b><i>a </i>and determine that at least one lighting device is in the off state. If the remote control device <b>302</b> determines that any of the lighting devices <b>304</b><i>a</i>, <b>304</b><i>b </i>are in the off state, the remote control device <b>302</b> may be configured to transmit a default toggle message, such as the on command <b>324</b>. The on command <b>324</b> may be sent as a multicast message or individual unicast messages that are received by the lighting devices <b>304</b><i>a</i>, <b>304</b><i>b. </i>
0167The remote control device <b>302</b> may receive a response to the status query message <b>320</b> from the lighting device <b>304</b><i>a </i>and identify that a response has not been received from the lighting device <b>304</b><i>b</i>. The remote control device <b>302</b> may assume, based on the response from the lighting device <b>304</b><i>a </i>and the lack of a response from the lighting device <b>304</b><i>b</i>, that the lighting devices <b>304</b><i>a</i>, <b>304</b><i>b </i>are out of sync. The remote control device <b>302</b> may determine control instructions for being sent to the lighting devices <b>304</b><i>a</i>, <b>304</b><i>b </i>based on the responses and/or lack of responses from the lighting devices <b>304</b><i>a</i>, <b>304</b><i>b</i>. For example, the remote control device <b>302</b> may transmit the on command <b>324</b> to change the state of the lighting device <b>304</b><i>a</i>. The lighting device <b>304</b><i>a </i>may turn on and transmit a state update message <b>326</b> to the remote control device <b>302</b>.
0168The remote control device <b>302</b> may transmit a status query message <b>320</b>, <b>330</b> that requests a response from lighting devices in another state, such as the on state, for example. The status query message <b>320</b>, <b>330</b> may be transmitted as an initial message (e.g., after awakening from a sleep state) after identifying a user interface event (e.g., actuation, rotation, finger swipe, etc.) and/or a proximity sensing event (e.g., a sensing circuit sensing an occupant near the remote control device <b>116</b>). The status query message <b>320</b>, <b>330</b> may be a multicast message or individual unicast messages received by the lighting devices <b>304</b><i>a</i>, <b>304</b><i>b </i>with which the remote control device <b>302</b> may be associated.
0169As shown in <figref idref="DRAWINGS">FIG. 3C</figref>, as the lighting device <b>304</b><i>b </i>is in the on state, the lighting device <b>304</b><i>b </i>may respond with a status message <b>332</b> that indicates that the lighting device <b>304</b><i>b </i>is in the on state. The status message <b>332</b> may identify that the lighting device <b>304</b><i>b </i>is in the on state, or the transmission of the status message <b>332</b> itself may indicate that the lighting device <b>304</b><i>b </i>is in the on state. As the lighting device <b>304</b><i>a </i>is in the off state, the lighting device <b>304</b><i>a </i>may be unresponsive to the status query message <b>330</b>.
0170The remote control device <b>302</b> may receive a response to the status query message <b>330</b> from the lighting device <b>304</b><i>b </i>and determine that at least one lighting device is in the on state. If the remote control device <b>302</b> determines that any of the lighting devices <b>304</b><i>a</i>, <b>304</b><i>b </i>are in the on state, the remote control device <b>302</b> may be configured to transmit a default toggle message, such as the off command <b>334</b>. The off command <b>334</b> may be sent as a multicast message or individual unicast messages that are received by the lighting devices <b>304</b><i>a</i>, <b>304</b><i>b. </i>
0171The remote control device <b>302</b> may receive a response to the status query message <b>330</b> from the lighting device <b>304</b><i>b </i>and identify that a response has not been received from the lighting device <b>304</b><i>a</i>. The remote control device <b>302</b> may assume, based on the response from the lighting device <b>304</b><i>b </i>and the lack of a response from the lighting device <b>304</b><i>a</i>, that the lighting devices <b>304</b><i>a</i>, <b>304</b><i>b </i>are out of sync. The remote control device <b>302</b> may determine control instructions for being sent to the lighting devices <b>304</b><i>a</i>, <b>304</b><i>b </i>based on the responses and/or lack of responses from the lighting devices <b>304</b><i>a</i>, <b>304</b><i>b</i>. For example, the remote control device <b>302</b> may transmit an off command <b>336</b> to change the state of the lighting device <b>304</b><i>b</i>. The lighting device <b>304</b><i>b </i>may turn on and transmit a state update message <b>336</b> to the remote control device <b>302</b>.
0172The control instructions in the off command <b>322</b> and the on command <b>332</b> may be default commands that are sent when lighting devices are out of sync, or the control instructions may be determined dynamically based on the response or lack of response to the status query messages <b>320</b>, <b>330</b>. Though an off command <b>322</b> and an on command <b>332</b> are provided as examples, other control instructions may be provided for synchronization, such as an intensity level, a color, etc.
0173<figref idref="DRAWINGS">FIG. 3D</figref> depicts an example message flow for querying for a current status (e.g., intensity levels) of lighting devices in response to an actuation of an intensity adjustment actuator (e.g., the rotation portion <b>118</b>) and generating lighting control commands in response to the identified status. As shown in <figref idref="DRAWINGS">FIG. 3D</figref>, a remote control device <b>302</b> may transmit a status query message <b>340</b> for identifying the intensity level of lighting devices, such as lighting devices <b>304</b><i>a</i>, <b>304</b><i>b</i>. The status query message <b>340</b> may be transmitted as an initial message (e.g., after awakening from a sleep state) after identifying a user interface event (e.g., actuation, rotation, finger swipe, etc.) and/or a proximity sensing event (e.g., a sensing circuit sensing an occupant near the remote control device <b>116</b>). The status query message <b>340</b> may be sent as a multicast message or individual unicast messages that are received by the lighting devices <b>304</b><i>a</i>, <b>304</b><i>b. </i>
0174The remote control device <b>302</b> may determine the control instructions for being sent to the lighting devices <b>304</b><i>a</i>, <b>304</b><i>b </i>based on the status of one of the lighting devices <b>304</b><i>a</i>, <b>304</b><i>b</i>. For example, the remote control device <b>302</b> may determine the control instructions for being sent to the lighting devices <b>304</b><i>a</i>, <b>304</b><i>b </i>based on the status of a first lighting device to respond to the status query message <b>306</b> (e.g., lighting device <b>304</b><i>a </i>as shown in <figref idref="DRAWINGS">FIG. 3D</figref>). The remote control device <b>302</b> may control the intensity levels of both of the lighting devices <b>304</b><i>a</i>, <b>304</b><i>b </i>by sending a command to go to the state of the master lighting device or the first lighting device to respond, or may toggle the other lighting devices in order to synchronize the other devices with the state of the master lighting device or the first lighting device to respond.
0175<figref idref="DRAWINGS">FIGS. 4A and 4B</figref> are system flow diagrams depicting example message flows for communicating digital messages in a load control system that implements a hub device <b>406</b> as a master device. Though the hub device <b>406</b> may be implemented as the master device, another master device may be similarly implemented, such as one of the lighting devices <b>404</b><i>a</i>, <b>404</b><i>b</i>, for example. A remote control device <b>402</b> may be in communication with the hub device <b>406</b> for transmitting commands in response to user interface events and/or receiving feedback. As shown in <figref idref="DRAWINGS">FIG. 4A</figref>, the remote control device <b>402</b> may identify a user interface event (e.g., actuation, rotation, finger swipe, etc.) that triggers a toggle command <b>408</b>, though other commands may also be communicated. The hub device <b>406</b> may receive the toggle command <b>408</b> and determine the control instructions for being sent to lighting devices <b>404</b><i>a</i>, <b>404</b><i>b </i>that are associated with the remote control device <b>402</b> for performing load control.
0176The hub device <b>406</b> may operate as a master device that maintains the current state of the lighting devices <b>404</b><i>a</i>, <b>404</b><i>b </i>and transmits a command for performing control based on the current state of the lighting devices <b>404</b><i>a</i>, <b>404</b><i>b</i>. For example, in response to the toggle command <b>408</b>, the hub device <b>406</b> may identify that the lighting devices <b>404</b><i>a</i>, <b>404</b><i>b </i>are both in the on state and send an off command <b>410</b> to change the state of the lighting devices <b>404</b><i>a</i>, <b>404</b><i>b</i>. The off command <b>410</b> may be sent as a multicast message or individual unicast messages to the lighting devices <b>404</b><i>a</i>, <b>404</b><i>b. </i>
0177The lighting devices <b>404</b><i>a</i>, <b>404</b><i>b </i>may send respective state update messages <b>414</b>, <b>416</b> to the hub device <b>406</b> to indicate a change of state in response to the off command <b>410</b> and/or the off command <b>412</b>. The hub device <b>406</b> may store the updated state of the lighting devices <b>404</b><i>a</i>, <b>404</b><i>b </i>for future reference for generating control instructions and/or providing feedback to the remote control device <b>402</b>. The hub device <b>406</b> may send a feedback message <b>418</b> to the remote control device <b>402</b> to identify the updated state of the lighting devices <b>404</b><i>a</i>, <b>404</b><i>b</i>. The remote control device <b>402</b> may provide feedback to a user on the status indicator <b>403</b> to indicate the updated state of the lighting devices <b>404</b><i>a</i>, <b>404</b><i>b </i>indicated in the feedback message <b>418</b>.
0178As shown in <figref idref="DRAWINGS">FIG. 4B</figref>, the remote control device <b>402</b> may identify a user interface event that triggers a toggle command <b>420</b> that is transmitted to the hub device <b>406</b>, though other commands may also be communicated. In response to the toggle command <b>408</b>, the hub device <b>406</b> may determine that the state of the lighting devices <b>404</b><i>a</i>, <b>404</b><i>b </i>are out of sync and synchronize the lighting devices <b>404</b><i>a</i>, <b>404</b><i>b</i>. The hub device <b>406</b> may identify that the lighting device <b>404</b><i>a </i>is in an off state and the lighting device <b>404</b><i>b </i>is in an on state and may transmit a synchronization message to the lighting devices <b>404</b><i>a</i>, <b>404</b><i>b</i>. The synchronization message may include a default toggle command, such as an off command <b>422</b> or an on command, when the lighting devices <b>404</b><i>a</i>, <b>404</b><i>b </i>are determined to be out of sync. The hub device may also, or alternatively, generate other lighting control instructions dynamically when the lighting devices <b>404</b><i>a</i>, <b>404</b><i>b </i>are determined to be out of sync. The off command <b>422</b> may be sent as a multicast message or individual unicast messages to the lighting devices <b>404</b><i>a</i>, <b>404</b><i>b. </i>
0179The lighting device <b>404</b><i>b </i>may send a state update message <b>426</b> to the hub device <b>406</b> to indicate a change of state in response to the off command <b>422</b> and/or the off command <b>424</b>. As the lighting device <b>404</b><i>a </i>may already be in the off state, the lighting device <b>404</b><i>a </i>may omit sending a state update message to prevent additional traffic from being communicated in the load control system. The hub device <b>406</b> may store the updated state of the lighting device <b>404</b><i>b </i>for future reference for generating control instructions and/or providing feedback to the remote control device <b>402</b>. The hub device <b>406</b> may send a feedback message <b>428</b> to the remote control device <b>402</b> to identify the updated state of the lighting devices <b>404</b><i>a</i>, <b>404</b><i>b</i>. The remote control device <b>402</b> may provide feedback to a user on the status indicator <b>403</b> to indicate the updated state of the lighting devices <b>404</b><i>a</i>, <b>404</b><i>b </i>indicated in the feedback message <b>428</b>.
0180<figref idref="DRAWINGS">FIG. 5A</figref> is a flowchart depicting an example method <b>500</b> for controlling (e.g., synchronizing and/or toggling) lighting devices in a load control system. The method <b>500</b> may be performed at one or more devices in the load control system. For example, the method <b>500</b>, or portions thereof, may be performed at a remote control device, another controller device, a hub device, a master device, and/or another computing device. The method <b>500</b> may be performed by a remote control device (e.g., the remote control device <b>116</b>) to query for a current status of lighting devices in response to an actuation of a toggle actuator (e.g., the actuation portion <b>117</b> of the remote control device <b>116</b>) and generate lighting control commands in response to the identified status (e.g., the identified statuses of all lighting devices as shown in <figref idref="DRAWINGS">FIG. 3A</figref>).
0181As shown in <figref idref="DRAWINGS">FIG. 5A</figref>, the method <b>500</b> may be executed periodically and/or in response to an actuation of an actuator (e.g., the actuation portion <b>117</b>) at <b>502</b>. At <b>504</b>, a determination may be made as to whether a toggle event is identified. A toggle event may be identified at a remote control device upon actuation of a portion of and/or a button on the remote control device (e.g., the actuation portion <b>117</b> of the remote control device <b>116</b>), or performing another toggle event at the remote control device. The toggle event may be detected at the remote control device or another device as described herein. If a toggle event is unidentified, at <b>504</b>, the method <b>500</b> may end, at <b>514</b>.
0182If a toggle event is identified, at <b>504</b>, a digital message may be sent, at <b>506</b>, to a group or all of lighting devices requesting a current on/off state. The request may be sent as a multicast message, or individual unicast messages, to each of the lighting devices. The lighting devices may return the current on/off state, which may be stored locally thereon.
0183At <b>508</b>, a determination may be made as to whether the on/off state of the lighting devices is consistent. If the on/off state of the group of lighting devices is consistent, a digital message may be sent, at <b>510</b>, to toggle the on/off state of the group of lighting devices. The digital message may include the toggle command, or an “on” command or “off” command, to instruct the lighting devices to toggle the local on/off state. The “on” command may be sent in response to an “off” state at the lighting devices. An “off” command may be sent in response to an “on” state at the lighting devices. The digital message for toggling the on/off state of the lighting devices may be sent as a multicast command to the group of lighting devices, or as individual unicast messages to each of the lighting devices.
0184If the on/off state across the group of lighting devices is determined to be inconsistent at <b>508</b>, a synchronization message may be sent to a subset of the lighting devices that are out of sync with the others at <b>510</b>. The synchronization message may be sent as a multicast message that indicates the on/off state of the lighting devices identified for responding to the command. For example, the synchronization message may instruct the lighting devices that are in the “on” state to turn “off.” The synchronization message may instruct the lighting devices that are in the “off” state to turn “on.” The synchronization message may be sent as a unicast message to each of the lighting devices to be synchronized. The command for changing the on/off state of the lighting devices that are out of sync may be an “on” command, an “off command, or a toggle command (e.g., where the command is sent in a unicast message or in a multicast message identifying the types of devices to respond). A determination may be made as to the subset of lighting devices (e.g., lighting devices in the “on” state or lighting devices in the “off” state) for being toggled for synchronization. The synchronization message may be sent to the subset of lighting devices having the lesser number of devices for which the on/off state is to be changed. A default setting may be configured at the device configured to send the synchronization message for “turning off” or “turning on” a subset of lighting devices with the synchronization message. After synchronizing the on/off state of the group of lighting devices at <b>510</b>, the method <b>500</b> may exit at <b>514</b>.
0185If the on/off state across the group of lighting devices is determined to be consistent at <b>508</b>, a digital message may be sent, at <b>512</b>, to toggle the group of synchronized lighting devices, before the method <b>500</b> exits at <b>514</b>. After the method <b>500</b> exits at <b>514</b>, the remote control device, or other battery-powered device, may enter a sleep mode. The identification of a toggle event at <b>504</b> may cause the remote control device, or other battery-powered device, to awake from a sleep mode or continue to stay awake for a period of time.
0186<figref idref="DRAWINGS">FIG. 5B</figref> is a flowchart depicting an example method <b>550</b> for controlling (e.g., synchronizing, toggling, and/or adjusting the intensity of) lighting devices in a load control system. The method <b>550</b> may be performed at one or more devices in the load control system. For example, the method <b>550</b>, or portions thereof, may be performed at a remote control device, another controller device, a hub device, a master device, and/or another computing device. The method <b>550</b> may be performed by a remote control device (e.g., the remote control device <b>116</b>) to query for a current status of lighting devices in response to an actuation of an actuator (e.g., the actuation portion <b>117</b> and/or the rotation portion <b>118</b> of the remote control device <b>116</b>) and generating lighting control commands in response to the identified status. For example, the remote control device <b>116</b> may be configured to generate a lighting control command in response to the identified on/off state of the first lighting device from which the remote control device receives a response (e.g., as shown in <figref idref="DRAWINGS">FIGS. 3B and 3C</figref>) or in response to the identified lighting intensity of the first lighting device from which the remote control device receives a response (e.g., as shown in <figref idref="DRAWINGS">FIG. 3D</figref>).
0187As shown in <figref idref="DRAWINGS">FIG. 5B</figref>, the method <b>550</b> may be executed periodically and/or in response to an actuation of an actuator (e.g., the actuation portion <b>117</b> or the rotation portion <b>118</b>) at <b>552</b>. At <b>554</b>, a digital message (e.g., query message) may be sent to a group or all of lighting devices requesting a current status of the lighting devices. The query message may be sent as a multicast message, or individual unicast messages, to each of the lighting devices. The lighting devices may return the current on/off state, which may be stored locally thereon. If a timeout is reached at <b>558</b> before a response to the query message is received at <b>556</b>, one or more of the lighting devices may be marked as “missing” at <b>559</b>. For example, the status indicator <b>119</b> may be illuminated (e.g., blinked or controlled to provide an animation) at <b>559</b>. The method <b>550</b> may end at <b>580</b>.
0188When a response to the query message is received at <b>556</b> (e.g., the first response to the query messages is received), a determination may be made, at <b>560</b>, as to whether a toggle actuation (e.g., a toggle event) has occurred. A toggle actuation may be identified at a remote control device upon actuation of a portion of and/or a button on the remote control device (e.g., the actuation portion <b>117</b> of the remote control device <b>116</b>), or performing another toggle event at the remote control device. The toggle actuation may be detected at the remote control device or another device as described herein. If a toggle actuation is identified at <b>560</b> and the on/off state included in the response to the query is the on state at <b>562</b>, a digital message including an “off” command may be sent at <b>564</b>, and the method may end at <b>580</b>. If the on/off state included in the response to the query is the off state at <b>562</b>, a digital message including an “on” command may be sent at <b>566</b>, and the method may end at <b>580</b>. The digital message including “on” and “off” commands may be sent as a multicast command to the group of lighting devices, or as individual unicast messages to each of the lighting devices.
0189If a toggle event is not identified at <b>560</b>, a determination may be made, at <b>568</b>, as to whether a raise actuation has occurred. A raise actuation may be identified at a remote control device upon actuation of a portion of and/or an intensity adjustment actuator on the remote control device (e.g., the rotation portion <b>118</b> of the remote control device <b>116</b>), or performing another actuation of an intensity adjustment actuator at the remote control device. The raise actuation (e.g., a clockwise rotation of the rotation portion <b>118</b>) may be detected at the remote control device or another device as described herein. If a raise actuation is identified at <b>568</b>, a digital message including a “move-to-level” command may be sent at <b>570</b>. The digital message including “move-to-off” command may be sent as a multicast command to the group of lighting devices, or as individual unicast messages to each of the lighting devices. The “move-to-level” command may cause all of the lighting devices to go to the intensity level included in the response to the query plus an offset that may be dependent upon the amount of rotation of the rotation portion <b>118</b>. The intensity level that was transmitted to the lighting devices in the “move-to-level” command (e.g., the intensity level included in the response to the query plus the offset) may be stored at the present intensity level of the lighting devices at <b>570</b>. In addition, the status indicator <b>119</b> may be illuminated, at <b>570</b>, to indicate the present intensity level of the lighting devices.
0190If the raise actuation is a continued raise actuation at <b>572</b>, another digital message including a “move-to-level” command may be sent at <b>570</b>. The “move-to-level” command may cause all of the lighting devices to go to the present intensity level plus an offset that may be dependent upon the amount of continued rotation of the rotation portion <b>118</b>. The present intensity level of the lighting devices may be updated again and the status indicator <b>119</b> may be illuminated to indicate the present intensity level (e.g., to track the present intensity level) at <b>570</b>. If the raise actuation is not a continued raise actuation at <b>572</b> (e.g., when the rotation of the rotation portion <b>118</b> has ended), the method <b>550</b> may end at <b>580</b>.
0191If a raise event is not identified at <b>568</b>, a determination may be made, at <b>574</b>, as to whether a lower actuation has occurred. A lower actuation may be identified at a remote control device upon actuation of a portion of and/or an intensity adjustment actuator on the remote control device (e.g., the rotation portion <b>118</b> of the remote control device <b>116</b>), or performing another actuation of an intensity adjustment actuator at the remote control device. The lower actuation (e.g., a counterclockwise rotation of the rotation portion <b>118</b>) may be detected at the remote control device or another device as described herein. If a lower actuation is identified at <b>574</b>, a digital message including a “move-to-level” command may be sent at <b>576</b>. The digital message including “move-to-off” command may be sent as a multicast command to the group of lighting devices, or as individual unicast messages to each of the lighting devices. The “move-to-level” command may cause all of the lighting devices to go to the intensity level included in the response to the query minus an offset that may be dependent upon the amount of rotation of the rotation portion <b>118</b>. The intensity level that was transmitted to the lighting devices in the “move-to-level” command (e.g., the intensity level included in the response to the query minus the offset) may be stored at the present intensity level of the lighting devices at <b>576</b>. In addition, the status indicator <b>119</b> may be illuminated, at <b>576</b>, to indicate the present intensity level of the lighting devices.
0192If the lower actuation is a continued lower actuation at <b>578</b>, another digital message including a “move-to-level” command may be sent at <b>570</b>. The “move-to-level” command may cause all of the lighting devices to go to the present intensity level minus an offset that may be dependent upon the amount of continued rotation of the rotation portion <b>118</b>. The present intensity level of the lighting devices may be updated again and the status indicator <b>119</b> may be illuminated to indicate the present intensity level (e.g., to track the present intensity level) at <b>576</b>. If the lower actuation is not a continued lower actuation at <b>578</b> (e.g., when the rotation of the rotation portion <b>118</b> has ended), the method <b>550</b> may end at <b>580</b>.
0193<figref idref="DRAWINGS">FIG. 6</figref> is a flowchart depicting an example method <b>600</b> for controlling (e.g., synchronizing and/or toggling) lighting devices in a load control system. The method <b>600</b> may be performed at one or more devices in the load control system. For example, the method <b>600</b>, or portions thereof, may be performed at one or more lighting devices, a hub device, a master device, and/or other load control devices. The method <b>600</b> may be performed by a lighting device (e.g., the lighting devices <b>112</b><i>a</i>, <b>112</b><i>b</i>, <b>122</b>) to respond to queries for a current status and to control an on/off state in response to commands (e.g., as shown in <figref idref="DRAWINGS">FIGS. 3A-3C</figref>).
0194As shown in <figref idref="DRAWINGS">FIG. 6</figref>, the method <b>600</b> may be executed periodically and/or in response to receiving a digital message at <b>602</b>. At <b>604</b>, a determination may be made as to whether a digital message has been received requesting a local on/off state of a lighting device. The request for the local on/off state may be received from a controller device, such as a remote control device, or a hub device. If a digital message is unreceived, at <b>604</b>, the method may proceed to <b>614</b>. If a digital message is received, at <b>604</b>, the local on/off state of a lighting device may be identified, at <b>606</b>. At <b>608</b>, the local on/off state may be sent in response to the request.
0195At <b>610</b>, a determination may be made as to whether a synchronization message has been received. The synchronization message may be received from a controller device, such as a remote control device, or a hub device in response to the local on/off state of the lighting device. If the synchronization message is received, at <b>610</b>, the on/off state of the lighting device may be toggled, at <b>612</b>, and the method <b>600</b> may end at <b>618</b>. The synchronization message may include a toggle command, an “on” command, or an “off” command that instruct the lighting device to toggle the local on/off state.
0196If the synchronization message is not received, at <b>610</b>, a determination may be made, at <b>614</b>, as to whether a digital message has been received to toggle a local on/off state of the lighting device. If the digital message has been received, at <b>614</b>, to toggle the local on/off state of the lighting device, the on/off state of the lighting load may be toggled, at <b>616</b>, and the method may end at <b>618</b>. If the digital message has not been received, at <b>614</b>, to toggle the local on/off state of the lighting device, the method <b>600</b> may end at <b>618</b>.
0197<figref idref="DRAWINGS">FIG. 7</figref> is a flowchart depicting an example method <b>700</b> for controlling (e.g., synchronizing and/or toggling) lighting devices in a load control system. The method <b>700</b> may be performed at one or more devices in the load control system. For example, the method <b>700</b>, or portions thereof, may be performed at a remote control device, another controller device, a hub device, a master device, and/or another computing device. The method <b>700</b> may be performed by a remote control device (e.g., the remote control device <b>116</b>) to generate lighting control commands in response to an actuation of a toggle actuator (e.g., the actuation portion <b>117</b> of the remote control device <b>116</b>) using a pre-stored on/off state (e.g., as shown in <figref idref="DRAWINGS">FIGS. 2A and 2B</figref>).
0198As shown in <figref idref="DRAWINGS">FIG. 7</figref>, the method <b>700</b> may be executed periodically and/or in response to an actuation of an actuator (e.g., the actuation portion <b>117</b>) at <b>702</b>. At <b>704</b>, a determination may be made as to whether a toggle event is identified. The toggle event may be detected at the remote control device or another device as described herein. If a toggle event is unidentified, at <b>704</b>, the method <b>700</b> may end, at <b>714</b>. The toggle event may cause a device, such as a battery-powered remote control device or other battery powered device, to awaken from a sleep mode. The device may enter the sleep mode after a predefined period of time has expired without receiving a toggle event or other user event on the device.
0199If a toggle event is identified, at <b>704</b>, a digital message may be sent to a group of lighting devices, at <b>706</b>. The digital message may be sent as a multicast message, or individual unicast messages, to each of the lighting devices. The digital message may include an “on” command or an “off” command. The “on” command or the “off” command may be a pre-stored command stored at the sending device. For example, a next state command (e.g., “on” command or “off” command) may be maintained in storage at a controller device for being sent in response to the identification of the next toggle event.
0200At <b>708</b>, a determination may be made as to whether a state update message has been received from the lighting devices. A state update message may be received from lighting devices that update an on/off state in response to an “on” command or an “off” command. The state update message may be received in response to the command sent at <b>706</b>, or a subsequent polling request. Polling requests for the current on/off state may be sent in intervals a predefined period of time after the command is sent at <b>706</b>. If a state update message is unreceived at <b>708</b> (e.g., after a predefined period of time), an opposite on/off command than the pre-stored command may be sent, at <b>710</b>. For example, if the pre-stored command sent at <b>706</b> was an “on” command, an “off” command may be sent at <b>710</b>, or vice versa. The opposite on/off command may be sent at <b>710</b> to cause the on/off state of the lighting devices to be toggled, as the on/off state of the lighting devices may go unchanged in response to the previous digital message sent at <b>706</b>. As a state update message failed to be received at <b>708</b>, the lighting devices may already be in the state indicated in the command. The method <b>700</b> may end at <b>714</b>.
0201If a state update message is received at <b>708</b> (e.g., within a predefined period of time), it may be determined that the lighting devices have been toggled. The pre-stored on/off command sent at <b>706</b> may act as a synchronization message to change the on/off state of a subset of the lighting devices, while other lighting devices may already be in the state indicated in the command. In another example, the digital message sent at <b>706</b> may toggle the entire group of lighting devices. As the lighting devices in the group have changed in on/off state in response to the pre-stored command, another on/off command may be generated and pre-stored at <b>712</b>, and the method may end at <b>714</b>. The pre-stored command may be flipped from the prior on/off command sent to at least a subset of the lighting devices. The pre-stored command may be the opposite on/off command of the pre-stored command sent at <b>706</b>. The pre-stored command may be the same command sent at <b>706</b> (e.g., when the opposite on/off command has already been sent at <b>710</b>). The pre-stored command may be stored in anticipation of the lighting devices remaining in the same on/off state until the next command sent from the device. In an example, a device, such as a battery-powered remote control device or other battery powered device, may pre-store the on/off command prior to entering a sleep mode and send the pre-stored command upon identifying a toggle event, at <b>704</b>.
0202<figref idref="DRAWINGS">FIG. 8</figref> is a flowchart depicting an example method <b>800</b> for controlling (e.g., synchronizing and/or toggling) lighting devices in a load control system. The method <b>800</b> may be performed at one or more devices in the load control system. For example, the method <b>800</b>, or portions thereof, may be performed at a remote control device, another controller device, a hub device, and/or another computing device. The method <b>800</b> may be performed by a remote control device (e.g., the remote control device <b>116</b>) to generate lighting control commands in response to an actuation of a toggle actuator (e.g., the actuation portion <b>117</b> of the remote control device <b>116</b>) using a default on/off state (e.g., as shown in <figref idref="DRAWINGS">FIGS. 2A and 2B</figref>).
0203As shown in <figref idref="DRAWINGS">FIG. 8</figref>, the method <b>800</b> may be executed periodically and/or in response to an actuation of an actuator (e.g., the actuation portion <b>117</b>) at <b>802</b>. At <b>804</b>, a determination may be made as to whether a toggle event is identified. The toggle event may be detected at the remote control device or another device as described herein. If a toggle event is unidentified (e.g., after a predefined period of time), at <b>804</b>, the method <b>800</b> may end, at <b>812</b>. The toggle event may cause a device, such as a battery-powered remote control device or other battery powered device, to awaken from a sleep mode. The device may enter the sleep mode after a predefined period of time has expired without receiving a toggle event or other user event on the device.
0204If a toggle event is identified, at <b>804</b>, a digital message may be sent to a group of lighting devices, at <b>806</b>. The digital message may be sent as a multicast message, or individual unicast messages, to each of the lighting devices. The digital message may include an “on” command or an “off” command. The command may be a default “on” command or a default “off” command that may be sent in response to each identification of a toggle event. For example, a default state command (e.g., “on” command or “off” command) may be maintained in storage for being sent in response to the identification of the each toggle event (e.g., upon awakening from a sleep mode).
0205At <b>808</b>, a determination may be made as to whether a state update message has been received from the lighting devices. A state update message may be received from lighting devices that update an on/off state in response to an “on” command or an “off” command. The state update message may be received in response to the command sent at <b>806</b>, or a subsequent polling request. Polling requests for the current on/off state may be sent in intervals a predefined period of time after the command is sent at <b>806</b>. If a state update message is unreceived at <b>808</b> (e.g., after a predefined period of time), an opposite on/off command than the default command may be sent, at <b>810</b>, and the method <b>800</b> may end at <b>812</b>. For example, if the default command sent at <b>806</b> was an “on” command, an “off” command may be sent at <b>810</b>, or vice versa. The opposite on/off command may be sent at <b>810</b> to cause a change to the on/off state of the lighting devices, as the on/off state of the lighting devices may go unchanged in response to the previous digital message sent at <b>806</b>. As a state update message failed to be received at <b>808</b>, the lighting devices may already be in the state indicated in the command. If a state update message is received at <b>808</b> (e.g., within a predefined period of time), the method <b>800</b> may end at <b>812</b>. If a toggle event is not identified at <b>804</b>, the device may enter the sleep mode and the method <b>800</b> may end at <b>812</b>.
0206<figref idref="DRAWINGS">FIG. 9</figref> is a flowchart depicting an example method <b>900</b> for controlling (e.g., synchronizing and toggling) lighting devices and/or sending state update messages in a load control system. The method <b>900</b> may be performed at one or more devices in the load control system. For example, the method <b>900</b>, or portions thereof, may be performed at one or more lighting devices, a hub device, and/or other load control devices. The method <b>900</b> may be performed by a lighting device (e.g., the lighting devices <b>112</b><i>a</i>, <b>112</b><i>b</i>, <b>122</b>) for controlling an on/off state in response to commands and sending status update messages (e.g., as shown in <figref idref="DRAWINGS">FIGS. 2A-2B</figref>).
0207As shown in <figref idref="DRAWINGS">FIG. 9</figref>, the method <b>900</b> may be executed periodically and/or in response to receiving a digital message at <b>902</b>. At <b>904</b>, a determination may be made as to whether a digital message has been received that includes an on/off command (e.g., an “on” command or an “off” command) for a lighting device. The on/off command may be received from a control device, such as a remote control device, or a hub device. If a digital message is unreceived, at <b>904</b>, the method may end at <b>916</b>. If a digital message is received, at <b>904</b>, the local on/off state of a lighting device may be identified, at <b>906</b>. At <b>908</b>, the local on/off state may be compared to the on/off command to determine whether the local on/off state matches the state indicated in the on/off command. If the local on/off state matches the state indicated in the on/off command, the method <b>900</b> may end at <b>916</b>. If the local on/off state fails to match the state indicated in the on/off command, the on/off state at the lighting device may be toggled, at <b>910</b>.
0208At <b>912</b>, a determination may be made as to whether the sending device from which the digital message was received at <b>904</b> is subscribed for receiving state update messages. The lighting device may have stored a list of identifiers of the devices that are subscribed for receiving state update messages. If the sending device is subscribed for state update messages, a state update message may be sent (e.g., via unicast messages), at <b>914</b>, to the device from which the digital message was received at <b>904</b>. The state update message may be sent, at <b>914</b>, in response to a polling request, or without receiving the polling request. The method <b>900</b> may end at <b>916</b>.
0209<figref idref="DRAWINGS">FIG. 10</figref> is a flowchart depicting an example method <b>1000</b> for synchronizing and/or toggling lighting devices in a load control system. The method <b>1000</b> may be performed at one or more devices in the load control system. For example, the method <b>1000</b>, or portions thereof, may be performed at a hub device and/or another master device. The other master device may be a remote control device, a lighting device, another control device, and/or another computing device.
0210As shown in <figref idref="DRAWINGS">FIG. 10</figref>, the method <b>1000</b> may be executed periodically and/or in response to receiving a digital message at <b>1002</b>. At <b>1006</b>, a determination may be made as to whether there has been a change in the on/off state of the lighting devices. A change in state may be identified, at <b>1006</b>, when a digital message is sent between control devices (e.g., such as a remote control device and a lighting device). The digital message may be relayed through the hub device or other master device. The hub device or other master device may listen for the digital messages otherwise communicated in the load control system (e.g., directly between control devices or otherwise communicated). The hub device or other master device may be subscribed to and/or receive state update messages from lighting devices that change an on/off state, which may enable updated on/off states to be identified from associated devices recognized by the hub device or other master device and unassociated devices that may be unrecognized by the hub device or other master device. The hub device or other master device may also query the lighting devices for their current on/off state or determine the current on/off state by listening to messages communicated between control devices in the load control system. The query message may be sent as a multicast message, or individual unicast messages, to each of the lighting devices.
0211If a change in the on/off state of a lighting device is identified, at <b>1006</b>, the updated on/off state may be maintained, at <b>1008</b>. A subset (e.g., one or more) of the lighting devices may be toggled. The toggling on the subset of lighting devices may be performed by a control device that is uncommon to the group of lighting devices capable of being controlled by a common control device. The hub device or other master device may have stored thereon the associated control devices for the group of lighting devices and/or the associated control devices for a subset of the lighting devices. For example, a group of lighting devices may be associated with a common remote control device, while a subset of the group may be associated with another remote control device or a network device. The subset of lighting devices may be toggled out of sync with the other lighting devices in the group. The hub device or other master device may maintain the on/off state of each of the lighting devices in the group and may know the devices that are out of sync.
0212At <b>1010</b>, a determination may be made as to whether an indication of a toggle event is received. A control device, such as a remote control device, may identify a toggle event and may send a digital message to the hub device or other master device. The digital message may include a toggle command, an “on” command, an “off” command, or another indication of a toggle event. If an indication of a toggle event is unreceived, at <b>1010</b>, the method <b>1000</b> may end, at <b>1020</b>.
0213If an indication of a toggle event is received, at <b>1010</b>, an on/off state of the lighting devices may be identified (e.g., retrieved from memory) at <b>1012</b>. The hub device or other master device may perform a lookup in memory of the on/off state of each of the lighting devices associated with the control device from which the indication of the toggle event is received. At <b>1014</b>, a determination may be made as to whether the on/off state of the lighting devices is consistent. If the on/off state of the group of lighting devices is consistent, a digital message may be sent, at <b>1018</b>, to toggle the on/off state of the group of lighting devices, and the method <b>1000</b> may end at <b>1020</b>. The digital message may include the toggle command, or an “on” command or “off” command, to instruct the lighting devices associated with the control device from which the indication of the toggle event was received to toggle the local on/off state. The “on” command may be sent in response to an “off” state at the lighting devices. An “off” command may be sent in response to an “on” state at the lighting devices. The digital message for toggling the on/off state of the lighting devices may be sent as a multicast command to the group of lighting devices, or as individual unicast messages to each of the lighting devices.
0214If the on/off state across the group of lighting devices is determined to be inconsistent, at <b>1014</b>, a synchronization message may be sent at <b>1016</b> to a subset of the lighting devices that are out of sync with the others, and the method <b>1000</b> may end at <b>1020</b>. The synchronization message may be sent as a multicast message that indicates the on/off state of the lighting devices identified for responding to the command. For example, the synchronization message may instruct the lighting devices that are in the “on” state to turn “off.” The synchronization message may instruct the lighting devices that are in the “off” state to turn “on.” The synchronization message may be sent as a unicast message to each of the lighting devices to be synchronized. The hub device or other master device may send the unicast message to each of the lighting devices associated with the control device from which the indication of a toggle event was received and that has an on/off state that is determined to be out of sync. The command for changing the on/off state of the lighting devices that are out of sync may be an “on” command, an “off command, or a toggle command (e.g., where the command is sent in a unicast message or in a multicast message identifying the types of devices to respond).
0215A determination may be made by the hub device or other master device as to the subset of lighting devices (e.g., lighting devices in the “on” state or lighting devices in the “off” state) for being toggled for synchronization. The synchronization message may be sent to the subset of lighting devices having the lesser number of devices for which the on/off state is to be changed. A default setting may be configured at the device configured to send the synchronization message for “turning off” or “turning on” a subset of lighting devices with the synchronization message.
0216The response to the synchronization message may be a state update message. The lighting devices that change an on/off state in response to an “on” command or an “off” command may send a state update message to the hub device or other master device to indicate the change in on/off state. The hub device or other master device may be subscribed to receiving state update messages at the associated lighting devices. The hub device or other master device may receive the state update message from the lighting devices that change state in response to the received “on” command or the received “off” command. The lighting devices that fail to change the on/off state in response to the command from the hub device or other master device may be unresponsive. The hub device or other master device may store the updated state and/or confirm the state of the unresponsive devices. The hub device or other master device may, alternatively, store the updated state of the lighting device after sending the command.
0217<figref idref="DRAWINGS">FIGS. 11A-11D</figref> show front views of a remote control device <b>1102</b> with a status indicator <b>1103</b> that may be illuminated to provide the feedback described herein. As shown in <figref idref="DRAWINGS">FIG. 11A</figref>, the remote control device <b>1102</b> may be configured to provide the feedback after the remote control device <b>1102</b> has been activated. For example, the remote control device <b>1102</b> may be configured to provide the feedback upon detecting a user near the control device and/or upon a user interface event being detected on a user interface of the remote control device <b>1102</b>. The user interface event may be an actuation of an actuation portion <b>1104</b> or a rotation of a rotation portion <b>1106</b>. The feedback may indicate that the remote control device <b>1102</b> is transmitting wireless communication signals (e.g., RF signals) in response to the activation. The remote control device <b>1102</b> may keep the status indicator <b>1103</b> illuminated for the duration of the event that triggered the feedback (e.g., while the rotation portion <b>1106</b> is being rotated). The remote control device <b>1102</b> may be configured to continue to illuminate the status indicator <b>1103</b> for a few seconds (e.g., 1-2 seconds) after the event, and then turn off the status indicator <b>1103</b> to conserve battery life.
0218The status indicator <b>1103</b> may be unlit (e.g., as shown in <figref idref="DRAWINGS">FIG. 11A</figref>) to provide feedback that the load control devices associated therewith are off. The LEDs in the status indicator <b>1103</b> may be turned on to a full intensity (e.g., as shown in <figref idref="DRAWINGS">FIG. 11B</figref>) when the load control devices associated therewith are on or a user interface event is detected. For example, the load control devices may be turned on in response to a toggle event recognized by actuating the actuation portion <b>1104</b> or rotating the rotation portion <b>1106</b>. The LEDs in the status indicator <b>1103</b> may be turned on to a full intensity to reflect the level of intensity of the loads controlled by a load control device. For example, the status indicator <b>1103</b> may reflect a high-end dimming level for lights, a fully-open or fully-closed position for shades, a full volume level for audio devices, a full speed for a fan, etc. When the actuation portion <b>1104</b> is pressed, the status indicator <b>1103</b> may blink between the two states shown in <figref idref="DRAWINGS">FIGS. 11A and 11B</figref> to provide feedback that the actuation portion <b>1104</b> was pressed and the remote control device <b>1102</b> is working.
0219The status indicator <b>1103</b> may be illuminated to provide the feedback in different manners (e.g., different intensities and/or colors) when the rotation portion <b>1106</b> is being rotated. For example, as shown in <figref idref="DRAWINGS">FIG. 11A</figref>, the status indicator <b>1103</b> may be fully illuminated to and maintained at a maximum light bar intensity L<sub>LB-MAX </sub>(e.g., 100%) when the rotation portion <b>1106</b> is being rotated clockwise or counterclockwise (e.g., to increase or decrease the intensity of lighting loads, shade levels, fan speed, volume, etc.) to provide simple feedback. As another example shown in <figref idref="DRAWINGS">FIG. 11C</figref>, for example, the status indicator <b>1103</b> may be illuminated to a first mid-level light bar intensity L<sub>LB-MID1 </sub>(e.g., 80%) that is less than the maximum light bar intensity L<sub>LB-MAX </sub>when the rotation portion <b>1106</b> is being rotated clockwise (e.g., to raise the intensity of lighting load loads, shade levels, fan speed, volume, etc.) to provide simple feedback that the rotation portion <b>1106</b> is being rotated. As shown in <figref idref="DRAWINGS">FIG. 11D</figref>, for example, the status indicator <b>1103</b> may be illuminated to a second mid-level light bar intensity L<sub>LB-MID2 </sub>(e.g., 40%) that is less than the first mid-level light bar intensity L<sub>LB-MID1 </sub>(and thus less than the maximum light bar intensity L<sub>LB-MAX</sub>) when the rotation portion <b>1106</b> is being rotated counterclockwise (e.g., to lower the intensity of the lighting loads, shade level, volume, etc.) to provide simple feedback that the rotation portion <b>1106</b> is being rotated.
0220Similarly, the status indicator <b>1103</b> may be illuminated with different colors to indicate different user inputs and/or the status of electrical loads or load control devices. For example, the status indicator <b>1103</b> may be illuminated with different colors to indicate that the intensity of a lighting load is being raised or lowered, a shade level is being raised or lowered, and/or a volume level is being raised or lowered. The status indicator <b>1103</b> may be illuminated with a red color when a lighting intensity is being raised and with a blue color when the lighting intensity is being lowered.
0221The status indicator <b>1103</b> may be illuminated in response to an actuation of the actuation portion <b>1104</b> to indicate that an electric load is being toggled on or off. For example, the status indicator <b>1103</b> may be illuminated to display an animation (e.g., a heartbeat animation) when a lighting load is being toggled on or off to provide simple feedback that the actuation portion <b>1104</b> has been actuated. <figref idref="DRAWINGS">FIG. 12</figref> shows an example plot of the intensity of the status indicator <b>1103</b> with respect to time in order to generate the animation. For example, the intensity of the status indicator <b>1103</b> may be quickly increased to a first intensity <b>1202</b> (e.g., the first mid-level light bar intensity L<sub>LB-MID1 </sub>as shown in <figref idref="DRAWINGS">FIG. 11C</figref>), quickly decreased to a second intensity <b>1204</b> (e.g., the second mid-level light bar intensity L<sub>LB-MID2 </sub>as shown in <figref idref="DRAWINGS">FIG. 11D</figref>), quickly increased to a third intensity <b>1206</b> (e.g., the maximum light bar intensity L<sub>LB-MAX </sub>as shown in <figref idref="DRAWINGS">FIG. 11B</figref>), and then quickly turned off. When the remote control device <b>1102</b> is operating in a spin-to-off mode, the status indicator <b>1103</b> may be illuminated to display an animation (e.g., the heartbeat animation described herein) when the intensity of the lighting load has reached a minimum intensity and is being turned off.
0222The status indicator <b>1103</b> may be illuminated to further indicate an amount of power being supplied to an electrical load. For example, instead of illuminating the entire light bar of the status indicator <b>1103</b>, the remote control device <b>1102</b> may illuminate a portion of the status indicator <b>1103</b>, and adjust the length of the illuminated portion in accordance with control applied by a user. For example, when the light bar of the status indicator <b>1103</b> is configured to have a circular shape, the illuminated portion may expand or contract around the circumference of the light bar in response to user interface events and/or adjustments in the status of electrical loads. The remote control device <b>1102</b> may adjust the intensity of the LED that is illuminating an end point of the illuminated portion of the status indicator <b>1103</b> to provide adjustment of the end point of the illuminated portion as is described in greater detail herein.
0223The remote control device <b>1102</b> may be configured to illuminate multiple portions of the status indicator <b>1103</b> to provide feedback. The multiple portions may be illuminated to provide different forms of animation on the status indicator <b>1103</b>. For example, as shown in <figref idref="DRAWINGS">FIG. 13</figref>, segments of the status indicator <b>1103</b> (e.g., having one or more LEDs to illuminate each segment) may be illuminated for predefined periods of time at each illumination configuration and the animation may change from one illumination configuration to the next at a constant rate when the rotation portion <b>1106</b> is being rotated (e.g., for simple feedback). The segments may be illuminated to indicate the direction of the rotation of the rotation portion <b>1106</b>, or the change in status of the electrical load. The segments may be illuminated from left to right through the illumination configurations shown in <figref idref="DRAWINGS">FIG. 13</figref> (e.g., such that the segments move in an upwards direction from the bottom to the top of the status indicator <b>1103</b>) to show an increase in the intensity of lighting loads, shade levels, volume, etc. The animation may repeat as long as the rotation portion <b>1106</b> is rotating. The segments may be illuminated from right to left through the illumination configurations shown in <figref idref="DRAWINGS">FIG. 13</figref> (e.g., such that the segments move in a downward direction from the top to the bottom of the status indicator <b>1103</b>) to show a decrease in the intensity of lighting loads, shade levels, fan speed, volume, etc. The segments may iterate in a predefined sequence to display an animation and the sequence may be repeated to indicate the rotation of the rotation portion <b>1106</b> and/or the continued change in status of the electrical load. Though a certain number of segments are shown, another number of segments and/or colors may be illuminated.
0224<figref idref="DRAWINGS">FIG. 14</figref> shows another example animation that may be displayed via the status indicator <b>1103</b> of the remote control device <b>1102</b>. As shown in <figref idref="DRAWINGS">FIG. 14</figref>, a single segment of the status indicator <b>1103</b> (e.g., having one or more LEDs to illuminate the segment) may be illuminated for predefined periods of time at each illumination configuration and the animation may change from one illumination configuration to the next at a constant rate when the rotation portion <b>1106</b> is being rotated (e.g., for simple feedback). The single segment may be illuminated in a clockwise or counterclockwise direction to indicate the direction of the rotation of the rotation portion <b>1106</b> or the change in the status of the electrical load. The single segment may be illuminated in a clockwise motion to show an increase in the intensity of lighting loads, shade levels, fan speed, volume, etc. (e.g., while rotating the rotation portion <b>1106</b> clockwise to increase the intensity). The single segment may be illuminated in a counterclockwise motion to show a decrease in the intensity of lighting loads, shade levels, fan speed, volume, etc. (e.g., while rotating the rotation portion <b>1106</b> counterclockwise to decrease the intensity). The single segment may iterate in a predefined sequence to display an animation and the sequence may be repeated to indicate the rotation of the rotation portion <b>1106</b> and/or the continued change in status of the electrical load. Though a single segment is shown, another number of segments and/or colors may be illuminated.
0225A single segment of the status indicator <b>1103</b> may be illuminated as shown in <figref idref="DRAWINGS">FIG. 14</figref> to provide simple feedback in response to an actuation of the actuation portion <b>1104</b>. For example, the single segment of the status indicator <b>1103</b> may be illuminated for predefined periods of time at each illumination configuration shown in <figref idref="DRAWINGS">FIG. 14</figref> and the animation may change from one illumination configuration to the next at a rate that increases with respect to time in response to an actuation of the actuation portion <b>1104</b> to turn on an electrical load (e.g., such as a ceiling fan) and at a rate that decreases with respect to time in response to an actuation of the actuation portion <b>1104</b> to turn off the electrical load.
0226<figref idref="DRAWINGS">FIG. 15</figref> shows another example animation that may be displayed via the status indicator <b>1103</b> of the remote control device <b>1102</b>. As shown in <figref idref="DRAWINGS">FIG. 15</figref>, segments of the status indicator <b>1103</b> including one or more LEDs may be illuminated from the left side of the status indicator <b>1103</b> to the right side of the status indicator <b>1103</b>, or vice versa. The segments of the status indicator <b>1103</b> may be illuminated from side to side in response to a rotation of the rotation portion <b>1106</b>, an actuation of the actuation potion <b>1104</b>, and/or the status of an electrical load. For example, the segments of the status indicator <b>1103</b> may be illuminated from the left side to the right side to provide simple feedback to indicate an actuation of the actuation portion <b>1104</b> to play a song, or that the song is currently playing, on an audio device. The segments may also, or alternatively, be illuminated from the left side to the right side to indicate a fan speed (e.g., side to side illumination increases in speed as fan speed increases, and decreases as fan speed decreases).
0227The animation shown in <figref idref="DRAWINGS">FIG. 15</figref> may begin as a single segment on the left or right side of the status indicator <b>1103</b>. The single segment may be illuminated for a predefined period of time and split into two segments that move to the opposing side of the status indicator <b>1103</b>. Each pair of segments may be illuminated together for a predefined period of time before the next segment is illuminated. The two segments may then come together as a single segment on the opposite side of the status indicator <b>1103</b>. The animation shown in <figref idref="DRAWINGS">FIG. 15</figref> may repeat a few times until the remote control device <b>1102</b> times out and turns off the status indicator <b>1103</b>. The animation may also repeat so long as the status of the electrical load remains the same, or until the actuation portion <b>1104</b> is actuated or the rotation portion <b>1106</b> stops rotating. Though a certain number of segments are shown, another number of segments and/or colors may be illuminated.
0228<figref idref="DRAWINGS">FIG. 16</figref> shows another example animation that may be displayed via the status indicator <b>1103</b> of the remote control device <b>1102</b>. As shown in <figref idref="DRAWINGS">FIG. 15</figref>, segments of the status indicator <b>1103</b> including one or more LEDs may be illuminated on the left side and the right side of the status indicator <b>1103</b>. The segments on the left and right side of the status indicator <b>1103</b> may be illuminated together for a period of time and then turn off for a period of time. The animation shown in <figref idref="DRAWINGS">FIG. 16</figref> may repeat a few times until the remote control device <b>1102</b> times out and turns off the status indicator <b>1103</b>. The animation may also be repeated until a user interface event is received on the remote control device <b>1102</b>, or a change in status is identified at an electrical load controlled by the remote control device <b>1102</b>. For example, the remote control device <b>1102</b> may provide the animation shown in <figref idref="DRAWINGS">FIG. 16</figref> on the status indicator <b>1103</b> to provide simple feedback in response to an actuation of the actuation potion <b>1104</b> to pause the music being played by an audio device. Though a certain number of segments are shown, another number of segments and/or colors may be illuminated.
0229The remote control device <b>1102</b> may be configured to illuminate different portions of the status indicator <b>1103</b> to provide advanced feedback, for example, of the intensity of electrical loads controlled by the remote control device <b>1102</b>.
0230<figref idref="DRAWINGS">FIG. 17</figref> shows a front view of the remote control device <b>1102</b> when the status indicator <b>1103</b> is illuminated to expand and contract in one direction to provide feedback (e.g., advanced feedback) that indicates the intensity of an electrical load. For example, the sequence shown in <figref idref="DRAWINGS">FIG. 17</figref> may be used to illustrate an intensity level of a lighting load or of the volume of an audio device as the intensity level increases (e.g., moving from left to right through the illumination configurations shown in <figref idref="DRAWINGS">FIG. 17</figref>) or decreases (e.g., moving from right to left through the illumination configurations shown in <figref idref="DRAWINGS">FIG. 17</figref>).
0231The remote control device <b>1102</b> may include a plurality of light sources (e.g., LEDs) configured to illuminate the status indicator <b>1103</b>. In response to an actuation of the remote control device <b>1102</b> to adjust the intensity level of the lighting load or the volume of the audio device, the remote control device <b>1102</b> may illuminate a subset of the light sources such that a portion <b>1105</b> of the status indicator <b>1103</b> is illuminated to indicate the intensity level corresponding to the actuation. The illuminated portion <b>1105</b> may begin at a starting point <b>1105</b>A (e.g., at the bottom of the status indicator <b>1103</b> as shown in <figref idref="DRAWINGS">FIG. 17</figref>) and end at an end point <b>1105</b>B (e.g., along the circumference of the status indicator <b>1103</b>). The length and/or intensity of the illuminated portion <b>1105</b> may be indicative of the intensity level of a lighting load or of a volume of an audio device. The subset of light sources may be illuminated uniformly to a common intensity. Alternatively, the subset of light sources may be illuminated to different intensities. For example, the remote control device <b>1102</b> may illuminate the end point <b>1105</b>B of the illuminated portion <b>1105</b> of the status indicator <b>1103</b> to a higher intensity than the rest of the illuminated portion and may decrease the intensity of the illuminated portion towards the starting point <b>1105</b>A. For example, the illuminated portion <b>1105</b> of the status indicator <b>1103</b> may display a gradient from the brightest intensity at the end point <b>1105</b>B to the dimmest intensity at the starting point <b>1105</b>A. This way, a user may still receive feedback based on the length of the illuminated portion, but less battery power may be consumed to provide the feedback. Alternatively, the dimmest intensity may be between the end point <b>1105</b>B and the starting point <b>1105</b>A.
0232To illustrate, the remote control device <b>1102</b> may be configured to increase the length of the illuminated portion <b>1105</b> (e.g., cause the end point <b>1105</b>B of the illuminated portion to move in a clockwise direction as shown in <figref idref="DRAWINGS">FIG. 17</figref>) when the intensity level of the lighting load or of the volume of the audio device is being raised. The remote control device <b>1102</b> may be configured to decrease the length of the illuminated portion <b>1105</b> (e.g., cause the end point <b>1105</b>B of the illuminate portion to move in a counterclockwise direction as shown in <figref idref="DRAWINGS">FIG. 17</figref>) when the intensity level of the lighting load or of the volume of the audio device is being lowered. This way, the illuminated portion <b>1105</b> may expand and contract as the intensity level of the lighting load or of the volume of the audio device is adjusted.
0233The illuminated portion <b>1105</b> may increase and decrease in size gradually or step between predefined segments that indicate a given intensity level. For example, the status indicator <b>1103</b> may step between illuminated segments to indicate that the present intensity of a lighting load is approximately 30%, approximately 60%, and approximately 90%, though the status indicator may be illuminated at any number of steps having a difference that is equivalent or inequivalent. When the lighting load or the volume is at a full intensity level (e.g., approximately full intensity level), the entire status indicator <b>1103</b> may be illuminated. When the remote control device <b>1102</b> is configured to control multiple lighting loads or audio devices, and set respective intensity levels of the multiple loads to different values, the remote control device <b>1102</b> may be configured to illuminate the status indicator <b>1103</b> to indicate an average of the respective intensity levels of the loads, to indicate the intensity level of a lighting load or audio device nearest to the remote control device <b>1102</b>, and/or the like.
0234In some examples, the remote control device <b>1102</b> may be configured to adjust the intensity of the light source illuminating the end point <b>1105</b>B of the illuminated portion <b>1105</b> to provide fine-tune adjustment of the position of the end point <b>1105</b>B. For example, the remote control device <b>1102</b> may adjust the intensity of the light source that illuminates the end point <b>1105</b>B between 1% and 100% to provide fine-tune adjustment of the position of the end point <b>1105</b>B. To illustrate, the remote control device <b>1102</b> may illuminate the status indicator <b>1103</b> to a length that indicates the intensity level of the lighting load or of the volume of the audio device controlled by the remote control device <b>1102</b> is at approximately 30%. At that point, the intensity of the light source illuminating the end point <b>1105</b>B may be set at 1%. As the intensity level of the lighting load or of the volume of the audio device is further adjusted toward 40%, the remote control device <b>1102</b> may adjust the intensity of the end point <b>1105</b>B between 1% and 100% with finer granularity to correspond to respective intermediate intensity levels that are between 30% and 40%. After the intensity level of the lighting load or of the volume of the audio device reaches 40%, the remote control device <b>1102</b> may illuminate an additional light source (e.g., to 1% intensity) to cause the length of the illuminated portion <b>1105</b> to expand. The remote control device <b>1102</b> may then adjust the intensity of the additional light source that is now illuminating the end point <b>1105</b>B between 1% and 100% as the intensity of the lighting load is being tuned towards a next level (e.g., 50%).
0235The remote control device <b>1102</b> may be configured to indicate a last-known intensity of the lighting load or of the volume of the audio device upon receiving a user interface event to turn on the lighting load or audio device, respectively. For example, before the lighting load or audio device was turned off, the remote control device <b>1102</b> may store the intensity level in a memory of the remote control device <b>1102</b> while quickly decreasing the length of the illuminated portion <b>1105</b> from the end point <b>1105</b>B to the starting point <b>1105</b>A. Subsequently, when the remote control device <b>1102</b> is actuated to turn the lighting load or audio device back on, the remote control device <b>1102</b> may illuminate the status indicator <b>1103</b> to quickly increase the length of the illuminated portion <b>1105</b> to correspond to the previously stored intensity level.
0236In the examples described herein, the display of the illuminated portion <b>1105</b> may be obstructed by a user's fingers that are manipulating the remote control device <b>1102</b>. For instance, as the user rotates the rotation portion <b>1106</b> of the remote control device <b>1102</b> to adjust the intensity level of the lighting load or of the volume of the audio device, the user's hand may block the leading edge (e.g., the end point <b>1105</b>B) of the illuminated portion <b>1105</b>. As a result, the user may not be able to determine whether the illuminated portion is expanding and contracting in response to the rotational movement of the rotation portion <b>1106</b>, and whether the intensity level of the electrical load is being adjusted properly.
0237The remote control device <b>1102</b> may control the manner in which the status indicator <b>1103</b> is illuminated to reduce the likelihood that a user's action may interfere with the feedback indication. For example, the remote control device <b>1102</b> may be configured to cause the end point <b>1105</b>B of the illuminated portion <b>1105</b> (e.g., as shown in <figref idref="DRAWINGS">FIG. 17</figref>) to move at a faster or slower angular speed than that of the rotation portion <b>1106</b> when the rotation portion is rotated. To illustrate, a user may, within a unit of time, rotate the rotation portion <b>1106</b> by x degrees in order to adjust the intensity (e.g., raise or lower) of the lighting load or of the volume of the audio device. In response, the remote control device <b>1102</b> may, within the same unit of time, cause the end point <b>1105</b>B of the illuminated portion <b>1105</b> to move by x+y or x−y degrees (e.g., in clockwise or counterclockwise direction) such that the leading edge of the illuminated portion <b>1105</b> represented by the end point <b>1105</b>B may move faster than (e.g., ahead of) or slower than (e.g., lagging behind) the user's hand. This way, despite obstruction by a user's hand, the user may still notice changes in the illuminated portion <b>1105</b> to know that control is being applied properly.
0238When the end point <b>1105</b>B of the illuminated portion <b>1105</b> is configured to move faster than (e.g., ahead of) the rotation portion <b>1106</b>, the remote control device <b>1102</b> may scale the full intensity range of the lighting load or of the volume of the audio device over less than a 360-degree rotation of the rotation portion <b>1106</b> so that the illuminated portion <b>1105</b> may expand or contract over the entire circumference of status indicator <b>1103</b> as the intensity level of the lighting load or of the volume of the audio device is being adjusted between the low-end and high-end of an intensity range. For example, the remote control device <b>1102</b> may be configured to scale the full intensity range of the lighting load or of the volume of the audio device over a 210-degree rotation of the rotation portion <b>1106</b>, such that when a rotational movement of the rotation portion <b>1106</b> reaches 210 degrees, the illuminated portion <b>1105</b> may cover the entire circumference of the status indicator <b>1103</b> (e.g., 360 degrees) to indicate that the intensity level of the lighting load or of the volume of the audio device has reached a maximum intensity. Such a technique may also reduce the amount of rotation used to adjust the intensity level of the lighting load or of the volume of the audio device between the low-end and the high-end. For example, the user may be able to adjust the intensity level over a greater range with less wrist movement.
0239The remote control device <b>1102</b> may be configured to illuminate a portion of the status indicator <b>1103</b> and cause the length of the illuminated portion <b>1105</b> to expand and contract (e.g., simultaneously from both end points <b>1105</b>A, <b>1105</b>B of the illuminated portion <b>1105</b>) to indicate the intensity level of the lighting load or of the volume of an audio device. The illuminated portion may be illuminated uniformly to a common intensity. Alternatively, different sections of the illuminated portion may be illuminated to different intensities. For example, the end point <b>1105</b>B of the illuminated portion of the status indicator <b>1105</b> may be illuminated to a higher intensity than the rest of the illuminated portion and the intensity of the illuminated portion <b>1105</b> may be decreased towards the starting point <b>1105</b>A. This way, a user may still receive feedback based on the length of the illuminated portion, but less battery power may be consumed to provide the feedback.
0240<figref idref="DRAWINGS">FIG. 18</figref> shows example front views of the remote control device <b>1102</b> when an illuminated portion <b>1105</b> of the status indicator <b>1103</b> is controlled to expand and contract from both end points <b>1105</b>A, <b>1105</b>B of the illuminated portion <b>1105</b> to provide feedback (e.g., advanced feedback) that indicates the intensity of an electrical load. For example, the sequence shown in <figref idref="DRAWINGS">FIG. 18</figref> may be used to illustrate an intensity level of a lighting load or of the volume of an audio device as the intensity level increases (e.g., moving from left to right through the illumination configurations shown in <figref idref="DRAWINGS">FIG. 18</figref>) or decreases (e.g., moving from right to left through the illumination configurations shown in <figref idref="DRAWINGS">FIG. 18</figref>).
0241As shown in <figref idref="DRAWINGS">FIG. 18</figref>, when an intensity adjustment actuator of the remote control device <b>1102</b> (e.g., the rotation portion <b>1106</b>) is actuated to adjust the intensity levels of the lighting devices, the status indicator <b>1103</b> may be illuminated to provide advanced feedback that indicates the intensity level to which the remote control device is controlling the lighting devices. When the remote control device <b>1102</b> is manipulated to raise the intensity level of the lighting load or the volume (e.g., via a rotation of the rotation portion <b>1106</b>), the remote control device <b>1102</b> may cause end points <b>1105</b>A, <b>1105</b>B of the illuminated portion <b>1105</b> to move (e.g., simultaneously) in respective clockwise and counterclockwise directions such that the length of the illuminated portion <b>1105</b> is extended to indicate that the intensity level is being raised. Similarly, when the remote control device <b>1102</b> is manipulated to lower the intensity level of the lighting load or of the volume of an audio device (e.g., via a rotation of the rotation portion <b>1106</b>), the remote control device <b>1102</b> may cause end points <b>1105</b>A, <b>1105</b>B of the illuminated portion <b>1105</b> to move (e.g., simultaneously) in respective counterclockwise and clockwise directions such that the length of the illuminated portion <b>1105</b> is shortened to indicate that the intensity level is being lowered.
0242The illuminated portion <b>1105</b> may increase and decrease in size gradually or step between predefined segments that indicate a given intensity level. For example, the status indicator <b>1103</b> may step between illuminated segments to indicate that the present intensity of a lighting load is approximately 30%, approximately 60%, and approximately 90%, though the status indicator may be illuminated at any number of steps having a difference that is equivalent or inequivalent. When the electrical load is at a full intensity level (e.g., approximately full lighting intensity or full volume level), the end points <b>1105</b>A, <b>1105</b>B may meet at the top of the status indicator <b>1103</b>, such that the status indicator <b>1103</b> is fully illuminated. The amount and/or speed of movement at end points <b>1105</b>A, <b>1105</b>B may be the same or may be different. The illuminated portion <b>1105</b> may be centered around a vertical axis of the remote control device <b>1102</b> when the control device is installed. As such, the illuminated portion <b>1105</b> may provide multiple intensity indications (e.g., on both the left half and the right half of the status indicator <b>1103</b>). Using such a mechanism, the likelihood of a user's hand obstructing the feedback indication may be reduced.
0243In the example shown in <figref idref="DRAWINGS">FIG. 18</figref>, when the remote control device <b>1102</b> is actuated (e.g., via the actuation portion <b>1104</b>) to turn the electrical load on or off, the status indicator <b>1103</b> may be illuminated to provide advanced feedback that indicates the intensity level to which the lighting devices are being turned on or from which the lighting devices are being turned off. When the actuation portion <b>1104</b> of the remote control device <b>1102</b> is actuated to turn the electrical load on, the status indicator <b>1103</b> may be illuminated (e.g., as an animation) to quickly increase the length of the illuminated portion <b>1105</b> (e.g., from both end points <b>1105</b>A, <b>1105</b>B) to correspond to a last-known intensity level of the electrical load before the electrical load was turned off. The remote control device <b>1102</b> may be configured to store the last-known intensity level of a lighting load or of a volume of an audio device in memory before the lighting load or audio device is turned off. When the actuation portion <b>1104</b> of the remote control device <b>1102</b> is actuated to turn an electrical load off, the status indicator <b>1103</b> may be controlled (e.g., as an animation) to quickly decrease the length of the illuminated portion <b>1105</b> (e.g., from both end points <b>1105</b>A, <b>1105</b>B toward the center of the illuminated portion <b>1105</b>) to indicate that the electrical load is being turned off. Prior to decreasing the length of the illuminated portion <b>1105</b>, the control device <b>1102</b> may be configured to store the intensity level of a lighting load or of a volume of an audio device in memory.
0244<figref idref="DRAWINGS">FIG. 19</figref> shows a front view of the remote control device <b>1102</b> when the status indicator <b>1103</b> is illuminated to provide feedback (e.g., advanced feedback) that indicates different settings for electrical loads. For example, the illuminations shown in <figref idref="DRAWINGS">FIG. 19</figref> may be used to illustrate different fan speeds for a motor load (such as a ceiling fan), presets for electrical loads (e.g., preset intensity levels for lighting loads), and selected scenes (e.g., presets including multiple electrical loads) of a load control system.
0245In response to an actuation of the actuation portion <b>1104</b> or a rotation of the rotation portion <b>1106</b>, the remote control device <b>1102</b> may turn on a fan or initiate a first preset. The remote control device <b>1102</b> may illuminate a segment of the status indicator <b>1103</b> (e.g., at the bottom of the remote control device <b>1102</b>) to indicate a first fan speed or first preset. In response to another actuation of the actuation portion <b>1104</b> or a rotation of the rotation portion <b>1106</b> (e.g., for a predefined distance or period of time), the remote control device <b>1102</b> may adjust the fan speed or preset. The remote control device <b>1102</b> may illuminate another segment of the status indicator <b>1103</b> (e.g., a next segment in a clockwise motion) to indicate a second fan speed or second preset. Different segments may continue to be illuminated in a clockwise manner as the fan speed increases or as presets change. Different segments may be illuminated in a counterclockwise manner as the fan speed decreases or as presets change (e.g., by actuating the actuation portion <b>1104</b> or rotating the rotation portion <b>1106</b> counterclockwise). When the fan speed is set to full, the last segment of the status indicator <b>1103</b> may be illuminated, or the entire status indicator <b>1103</b> may be illuminated, as shown in <figref idref="DRAWINGS">FIG. 19</figref>.
0246<figref idref="DRAWINGS">FIG. 20</figref> shows a front view of the remote control device <b>1102</b> when the status indicator <b>1103</b> is illuminated to provide feedback (e.g., advanced feedback) that indicates different shade positions for a motorized window treatment. In response to an actuation of the actuation portion <b>1104</b> or a rotation of the rotation portion <b>1106</b>, the remote control device <b>1102</b> may raise or lower a shade position for a motorized window treatment. The remote control device <b>1102</b> may illuminate a portion of the status indicator <b>1103</b> (e.g., from the top of the remote control device <b>1102</b>) to indicate the shade position. As shown in <figref idref="DRAWINGS">FIG. 20</figref>, the fully open position may be indicated by unilluminating the status indicator <b>1103</b>. As the shade position is lowered, the status indicator <b>1103</b> may be illuminated to indicate the position of the shade.
0247As shown in <figref idref="DRAWINGS">FIG. 20</figref>, when the remote control device <b>1102</b> is manipulate to lower the shade position of the motorized window treatment (e.g., via a rotation of the rotation portion <b>1106</b>), the remote control device <b>1102</b> may cause end points <b>1105</b>A, <b>1105</b>B of the illuminated portion <b>1105</b> to move (e.g., simultaneously) in respective counterclockwise and clockwise directions such that the length of the illuminated portion <b>1105</b> is extended to indicate that the shade position is being lowered. Similarly, when the remote control device <b>1102</b> is manipulated to raise the shade position of the motorized window treatment (e.g., via a rotation of the rotation portion <b>1106</b>), the remote control device <b>1102</b> may cause end points <b>1105</b>A, <b>1105</b>B of the illuminated portion <b>1105</b> to move (e.g., simultaneously) in respective clockwise and counterclockwise directions such that the length of the illuminated portion <b>1105</b> is shortened to indicate that the shade position is being raised.
0248The illuminated portion <b>1105</b> may increase and decrease in size gradually or step between predefined segments that indicate a given shade position. For example, the status indicator <b>1103</b> may step between illuminated segments to indicate that the shade position of a motorized window treatment is approximately 30% closed, approximately 60% closed, and approximately 90% closed, though the status indicator may be illuminated at any number of steps having a difference that is equivalent or inequivalent. When the shade position is fully closed, the end points <b>1105</b>A, <b>1105</b>B may meet at the bottom of the status indicator <b>1103</b>, such that the status indicator <b>1103</b> is fully illuminated. The amount and/or speed of movement at end points <b>1105</b>A, <b>1105</b>B may be the same or may be different. The illuminated portion <b>1105</b> may be centered around a vertical axis of the remote control device <b>1102</b> when the remote control device <b>1102</b> is installed. As such, the illuminated portion <b>1105</b> may provide multiple shade position indications (e.g., on both the left half and the right half of the status indicator <b>1103</b>). Using such a mechanism, the likelihood of a user's hand obstructing the feedback indication may be reduced.
0249In the example shown in <figref idref="DRAWINGS">FIG. 20</figref>, when the remote control device <b>1102</b> is actuated (e.g., via the actuation portion <b>1104</b>), the status indicator <b>1103</b> may be illuminated to quickly increase the length of the illuminated portion <b>1105</b> (e.g., from both end points <b>1105</b>A, <b>1105</b>B) to correspond to a last-known shade position. The remote control device <b>1102</b> may be configured to store the last-known shade position.
0250<figref idref="DRAWINGS">FIG. 21</figref> is a flowchart depicting an example method <b>2100</b> for determining the type of feedback to be provided on a status indicator of a remote control. The method <b>2100</b> may be performed at one or more devices in the load control system during an association procedure for associating the remote control device with another device. For example, the method <b>2100</b>, or portions thereof, may be performed at a remote control device, another controller device, a hub device, and/or another computing device.
0251As shown in <figref idref="DRAWINGS">FIG. 21</figref>, the method <b>2100</b> may begin at <b>2102</b>. At <b>2102</b>, an association message may be received. The association message may comprise information about devices in the system, such as association information that indicates the address and/or device type of the device or devices being associated with the remote control device. The addresses and device types in the association message may be stored in memory, at <b>2104</b>, for associating the remote control device with the device or devices indicated in the association message. At <b>2106</b>, a determination may be made as to whether a hub device is assigned to the remote control device. The determination at <b>2106</b> may be made based on the association information stored in memory. If a hub device is assigned to the remote control device, advanced feedback may be implemented at <b>2108</b> for the status indicator of the remote control device to indicate the status of one or more electrical loads or load control devices. The hub device may give the remote control device access to the status of the electrical loads or load control devices.
0252At <b>2110</b>, a determination may be made as to whether one load control device is assigned to the remote control device for being controlled by the remote control device. The determination at <b>2110</b> may be made based on the association information stored in memory. If one load control device is assigned to the remote control device, advanced feedback may be implemented at <b>2108</b> for the status indicator of the remote control device to indicate the status of the load control device or the electrical load controlled thereby. The status of a single load control device may be more easily indicated to a user than multiple load control devices. If multiple load control devices are assigned to the remote control device for being controlled thereby and the remote control device is not assigned to a hub device, simple feedback may be implemented at <b>2112</b> for the status indicator of the remote control device to indicate responses to user interface events on the remote control device.
0253The feedback type may be configured, at <b>2114</b>, based on the type of device or devices (e.g., lighting devices, temperature control devices, motorized window treatments, fans, audio devices, etc.) being controlled by the remote control device. Different device types may correspond to different types of simple feedback or advanced feedback, as there may be multiple types of simple feedback and/or multiple types of advanced feedback that may be provided by the status indicator on the remote control device. For example, the feedback type for lighting devices may be different than the feedback type for motorized window treatments or ceiling fans. Different types of devices may use the same feedback types, while others may not. For example, the intensity level of lighting devices and the intensity level of the volume for an audio device may be indicated using the same feedback type. The feedback type may be configured based on the device type or types indicated in the association information stored in memory. At <b>2116</b>, the method <b>2100</b> may end.
0254<figref idref="DRAWINGS">FIG. 22</figref> is a flowchart depicting an example method <b>2200</b> for determining the type of feedback to provide on a status indicator of a remote control device. The method <b>2200</b> may be performed on demand at one or more devices in the load control system to obtain feedback information at any time during operation of the remote control device. For example, the method <b>2200</b>, or portions thereof, may be performed at a remote control device, another controller device, a hub device, and/or another computing device.
0255As shown in <figref idref="DRAWINGS">FIG. 22</figref>, the method <b>2200</b> may begin at <b>2202</b>. At <b>2202</b>, a query response may be received for device information about devices in the system, such as status information associated with an electrical load or a load control device. The query response may be a status message received in response to a status query message for status information or a command for controlling the electrical load via the load control device. The query may be transmitted in response to the remote control device awakening from a sleep mode, after a predefined period of time, or in response to detection of a user interface event to control an electrical load. The query response or responses may include device information, which may indicate the number of devices associated with the remote control device, an identifier of the associated devices, the device types of the associated devices, and/or the status of the associated devices. The query response may be received from a hub device, a load control device, or another device in the load control system.
0256At <b>2204</b>, a determination may be made as to whether a hub device is assigned to the remote control device. The determination at <b>2106</b> may be made based on the association information stored in memory and/or other device information in the query responses received at <b>2202</b>. If a hub device is assigned to the remote control device, advanced feedback may be implemented at <b>2206</b> for the status indicator of the remote control device to indicate the status of one or more electrical loads or load control devices. The hub device may give the remote control device access to the status of the electrical loads or load control devices.
0257At <b>2208</b>, a determination may be made as to whether the status of each load or load control device being controlled by a remote control device is the same. For example, a determination may be made as to whether each lighting load is being controlled at the same intensity level. The determination at <b>2208</b> may be made based on the query response received at <b>2202</b>. If the status of each device is the same, the remote control device may implement advanced feedback to indicate the status of the electrical loads or load control devices. If the status of each load or load control device being controlled by the remote control device is determined, at <b>2208</b>, to be different, simple feedback may be implemented at <b>2210</b> for the status indicator of the remote control device to indicate responses to user interface events on the remote control device.
0258At <b>2212</b>, the feedback type may be configured based on the type of device or devices (e.g., lighting devices, temperature control devices, motorized window treatments, fans, audio devices, etc.) being controlled by the remote control device. Different device types may correspond to different types of simple feedback or advanced feedback, as there may be multiple types of simple feedback and/or multiple types of advanced feedback that may be provided by the status indicator on the remote control device. For example, the feedback type for lighting devices may be different than the feedback type for motorized window treatments or ceiling fans. Different types of devices may use the same feedback types, while others may not. For example, the intensity level of lighting devices and the intensity level of the volume for an audio device may be indicated using the same feedback type. The feedback type may be configured based on the device type or types indicated in the association information stored in memory or based on other device information in the query responses received at <b>2202</b>. At <b>2214</b>, the method <b>2200</b> may end.
0259<figref idref="DRAWINGS">FIG. 23</figref> is a block diagram illustrating an example load control device, e.g., a load control device <b>2300</b>, as described herein. The load control device <b>2300</b> may be a dimmer switch, an electronic switch, a lighting device (e.g., a light bulb, an electronic ballast for lamps, an LED driver for LED light sources, etc.), an AC plug-in load control device for controlling a plugged electrical load, a controllable electrical receptacle, a temperature control device (e.g., a thermostat), a motor drive unit for a motorized window treatment, a motor drive unit for a fan (e.g., ceiling fan), an audio device (e.g., a controllable speaker or playback device), an appliance, a security camera device, or other load control device. The load control device <b>2300</b> may include a communications circuit <b>2302</b>. The communications circuit <b>2302</b> may include a receiver, an RF transceiver, or other communications module capable of performing wired and/or wireless communications via communications link <b>2310</b>. The communications circuit <b>2302</b> may be in communication with a control circuit <b>2304</b>. The control circuit <b>2304</b> may include one or more general purpose processors, special purpose processors, conventional processors, digital signal processors (DSPs), microprocessors, integrated circuits, a programmable logic device (PLD), application specific integrated circuits (ASICs), or the like. The control circuit <b>2304</b> may perform signal coding, data processing, power control, input/output processing, or any other functionality that enables the load control device <b>2300</b> to perform as described herein.
0260The control circuit <b>2304</b> may store information in and/or retrieve information from the memory <b>2306</b>. For example, the memory <b>2306</b> may maintain a registry of associated control devices and/or control configuration instructions. The memory <b>2306</b> may include a non-removable memory and/or a removable memory. The load control circuit <b>2308</b> may receive instructions from the control circuit <b>2304</b> and may control the electrical load <b>2316</b> based on the received instructions. The load control circuit <b>2308</b> may send status feedback to the control circuit <b>2304</b> regarding the status of the electrical load <b>2316</b>. The load control circuit <b>2308</b> may receive power via the hot connection <b>2312</b> and the neutral connection <b>2314</b> and may provide an amount of power to the electrical load <b>2316</b>. The electrical load <b>2316</b> may include any type of electrical load.
0261The control circuit <b>2304</b> may be in communication with an actuator <b>2318</b> (e.g., one or more buttons) that may be actuated by a user to communicate user selections to the control circuit <b>2304</b>. For example, the actuator <b>2318</b> may be actuated to put the control circuit <b>2304</b> in an association mode and/or communicate association messages from the load control device <b>2300</b>.
0262<figref idref="DRAWINGS">FIG. 24</figref> is a block diagram illustrating an example controller device <b>2400</b> as described herein. The controller device <b>2400</b> may be a remote control device, an occupancy sensor, a daylight sensor, a window sensor, a temperature sensor, and/or the like. The controller device <b>2400</b> may include a control circuit <b>2402</b> for controlling the functionality of the controller device <b>2400</b>. The control circuit <b>2402</b> may include one or more general purpose processors, special purpose processors, conventional processors, digital signal processors (DSPs), microprocessors, integrated circuits, a programmable logic device (PLD), application specific integrated circuits (ASICs), or the like. The control circuit <b>2402</b> may perform signal coding, data processing, power control, input/output processing, and/or any other functionality that enables the controller device <b>2400</b> to perform as described herein.
0263The control circuit <b>2402</b> may store information in and/or retrieve information from the memory <b>2404</b>. The memory <b>2404</b> may include a non-removable memory and/or a removable memory, as described herein.
0264The controller device <b>2400</b> may include one or more light sources, such as one or more LEDs <b>2412</b>, for providing feedback to a user. The one or more LEDs <b>2412</b> may be included in a status indicator and may be controlled by the control circuit <b>2402</b>. The control circuit <b>2402</b> may control the LEDs <b>2412</b> as described herein to provide feedback to the user.
0265The controller device <b>2400</b> may include a communications circuit <b>2408</b> for transmitting and/or receiving information. The communications circuit <b>2408</b> may transmit and/or receive information via wired and/or wireless communications. The communications circuit <b>2408</b> may include a transmitter, an RF transceiver, or other circuit capable of performing wired and/or wireless communications. The communications circuit <b>2408</b> may be in communication with control circuit <b>2402</b> for transmitting and/or receiving information.
0266The control circuit <b>2402</b> may also be in communication with an input circuit <b>2406</b>. The input circuit <b>2406</b> may include an actuator (e.g., one or more buttons), a rotating or sliding portion, or a sensor circuit (e.g., an occupancy sensor circuit, a daylight sensor circuit, or a temperature sensor circuit) for receiving input that may be sent to a device for controlling an electrical load. The input circuit <b>2406</b> may also comprise a proximity sensing circuit for sensing an occupant in the vicinity of the controller device <b>2400</b>. For example, the controller device <b>2402</b> may receive input from the input circuit <b>2406</b> to put the control circuit <b>2402</b> in an association mode and/or communicate association messages from the controller device <b>2400</b>. The control circuit <b>2402</b> may receive information from the input circuit <b>2406</b> (e.g., an indication that a button has been actuated, a rotation portion has been rotated, or information has been sensed) and/or an indication of a proximity sensing event. The input circuit <b>2406</b> may be actuated as an on/off event. Each of the modules within the controller device <b>2400</b> may be powered by a power source <b>2410</b>.
0267<figref idref="DRAWINGS">FIG. 25</figref> is a block diagram illustrating an example network device <b>2500</b> as described herein. The network device <b>2500</b> may include the network device <b>190</b>, for example. The network device <b>2500</b> may include a control circuit <b>2502</b> for controlling the functionality of the network device <b>2500</b>. The control circuit <b>2502</b> may include one or more general purpose processors, special purpose processors, conventional processors, digital signal processors (DSPs), microprocessors, integrated circuits, a programmable logic device (PLD), application specific integrated circuits (ASICs), or the like. The control circuit <b>2502</b> may perform signal coding, data processing, power control, input/output processing, or any other functionality that enables the network device <b>2500</b> to perform as described herein. The control circuit <b>2502</b> may store information in and/or retrieve information from the memory <b>2504</b>. The memory <b>2504</b> may include a non-removable memory and/or a removable memory. The non-removable memory may include random-access memory (RAM), read-only memory (ROM), a hard disk, or any other type of non-removable memory storage. The removable memory may include a subscriber identity module (SIM) card, a memory stick, a memory card, or any other type of removable memory.
0268The network device <b>2500</b> may include a communications circuit <b>2508</b> for transmitting and/or receiving information. The communications circuit <b>2508</b> may perform wireless and/or wired communications. The communications circuit <b>2508</b> may include an RF transceiver or other circuit capable of performing wireless communications via an antenna. Communications circuit <b>2508</b> may be in communication with control circuit <b>2502</b> for transmitting and/or receiving information.
0269The control circuit <b>2502</b> may also be in communication with a display <b>2506</b> for providing information to a user. The control circuit <b>2502</b> and/or the display <b>2506</b> may generate GUIs for being displayed on the network device <b>2500</b>. The display <b>2506</b> and the control circuit <b>2502</b> may be in two-way communication, as the display <b>2506</b> may include a touch screen module capable of receiving information from a user and providing such information to the control circuit <b>2502</b>. The network device may also include an actuator <b>2512</b> (e.g., one or more buttons) that may be actuated by a user to communicate user selections to the control circuit <b>2502</b>.
0270Each of the modules within the network device <b>2500</b> may be powered by a power source <b>2510</b>. The power source <b>2510</b> may include an AC power supply or DC power supply, for example. The power source <b>2510</b> may generate a supply voltage Vcc for powering the modules within the network device <b>2500</b>.
0271<figref idref="DRAWINGS">FIG. 26</figref> is a block diagram illustrating an example hub device <b>2600</b> as described herein. The hub device <b>2600</b> may include a control circuit <b>2602</b> for controlling the functionality of the hub device <b>2600</b>. The control circuit <b>2602</b> may include one or more general purpose processors, special purpose processors, conventional processors, digital signal processors (DSPs), microprocessors, integrated circuits, a programmable logic device (PLD), application specific integrated circuits (ASICs), or the like. The control circuit <b>2602</b> may perform signal coding, data processing, power control, input/output processing, or any other functionality that enables the hub device <b>2600</b> to perform as described herein. The control circuit <b>2602</b> may store information in and/or retrieve information from the memory <b>2604</b>. The memory <b>2604</b> may include a non-removable memory and/or a removable memory. The non-removable memory may include random-access memory (RAM), read-only memory (ROM), a hard disk, or any other type of non-removable memory storage. The removable memory may include a subscriber identity module (SIM) card, a memory stick, a memory card, or any other type of removable memory.
0272The hub device <b>2600</b> may include a communications circuit <b>2608</b> for transmitting and/or receiving information. The communications circuit <b>2608</b> may perform wireless and/or wired communications. The hub device <b>2600</b> may also, or alternatively, include a communications circuit <b>2612</b> for transmitting and/or receiving information. The communications circuit <b>2612</b> may perform wireless and/or wired communications. Communications circuits <b>2608</b> and <b>2612</b> may be in communication with control circuit <b>2602</b>. The communications circuits <b>2608</b> and <b>2612</b> may include RF transceivers or other communications modules capable of performing wireless communications via an antenna. The communications circuit <b>2608</b> and communications circuit <b>2612</b> may be capable of performing communications via the same communication channels or different communication channels. For example, the communications circuit <b>2608</b> may be capable of communicating (e.g., with a network device, over a network, etc.) via a wireless communication channel (e.g., BLUETOOTH®, near field communication (NFC), WI-FI®, WIMAX®, cellular, etc.) and the communications circuit <b>2612</b> may be capable of communicating (e.g., with control devices and/or other devices in the load control system) via another wireless communication channel (e.g., WI-FI® or a proprietary communication channel, such as CLEAR CONNECT™).
0273The control circuit <b>2602</b> may be in communication with an LED indicator <b>2614</b> for providing indications to a user. The control circuit <b>2602</b> may be in communication with an actuator <b>2606</b> (e.g., one or more buttons) that may be actuated by a user to communicate user selections to the control circuit <b>2602</b>. For example, the actuator <b>2606</b> may be actuated to put the control circuit <b>2602</b> in an association mode and/or communicate association messages from the hub device <b>2600</b>.
0274Each of the modules within the hub device <b>2600</b> may be powered by a power source <b>2610</b>. The power source <b>2610</b> may include an AC power supply or DC power supply, for example. The power source <b>2610</b> may generate a supply voltage Vcc for powering the modules within the hub device <b>2600</b>.
0275Although features and elements are described herein in particular combinations, each feature or element can be used alone or in any combination with the other features and elements. For example, the functionality described herein may be described as being performed by a control device, such as a remote control device or a lighting device, but may be similarly performed by a hub device or a network device. The methods described herein may be implemented in a computer program, 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 over wired or wireless connections) and computer-readable storage media. Examples of computer-readable storage media include, but are not limited to, a read only memory (ROM), a random access memory (RAM), removable disks, and optical media such as CD-ROM disks, and digital versatile disks (DVDs).
Contents5
28 sheets
Sheet 1 Sheet 2 Sheet 3 Sheet 4 Sheet 5 Sheet 6 Sheet 7 Sheet 8 Sheet 9 Sheet 10 Sheet 11 Sheet 12 Sheet 13 Sheet 14 Sheet 15 Sheet 16 Sheet 17 Sheet 18 Sheet 19 Sheet 20 Sheet 21 Sheet 22 Sheet 23 Sheet 24 Sheet 25 Sheet 26 Sheet 27 Sheet 28
Every citation, both ways
| Document | Relation | Office | Cited during |
|---|---|---|---|
| US12322281B2 | Cited by | United States of America | Search report |
| WO2020236633A1 | Cited by | World Intellectual Property Organization (WIPO) | Applicant |
| WO2020236653A1 | Cited by | World Intellectual Property Organization (WIPO) | Applicant |
| US11172564B2 | Cited by | United States of America | Search report |
| EP4550940A1 | Cited by | European Patent Office (EPO) | Applicant |
| US11778716B2 | Cited by | United States of America | Applicant |
| US12426143B2 | Cited by | United States of America | Applicant |
| US11280131B2 | Cited by | United States of America | Search report |
| US2024426172A1 | Cited by | United States of America | Search report |
| US2023334979A1 | Cited by | United States of America | Search report |
| US11417203B2 | Cited by | United States of America | Applicant |
| US11696385B2 | Cited by | United States of America | Applicant |
| US11869345B2 | Cited by | United States of America | Applicant |
| US11715368B2 | Cited by | United States of America | Search report |
| US11812533B2 | Cited by | United States of America | Applicant |
| US11450992B2 | Cited by | United States of America | Applicant |
| US11425811B2 | Cited by | United States of America | Applicant |
| US12044069B2 | Cited by | United States of America | Search report |
| US12300097B2 | Cited by | United States of America | Applicant |
| US12065876B2 | Cited by | United States of America | Applicant |
| US2006055582A1 | Cites | United States of America | Applicant |
| US2007103326A1 | Cites | United States of America | Applicant |
| US2008111491A1 | Cites | United States of America | Applicant |
| US2008258650A1 | Cites | United States of America | Applicant |
| US2009128361A1 | Cites | United States of America | Applicant |
| US2011006879A1 | Cites | United States of America | Applicant |
| US2012286940A1 | Cites | United States of America | Applicant |
| US2013030589A1 | Cites | United States of America | Applicant |
| US2013110195A1 | Cites | United States of America | Applicant |
| US2014132475A1 | Cites | United States of America | Applicant |
| US2014177469A1 | Cites | United States of America | Applicant |
| US2014265568A1 | Cites | United States of America | Applicant |
| US2015077021A1 | Cites | United States of America | Applicant |
| US2015351205A1 | Cites | United States of America | Applicant |
| US2015371534A1 | Cites | United States of America | Applicant |
| US2015382436A1 | Cites | United States of America | Applicant |
| US2016073479A1 | Cites | United States of America | Applicant |
| US2017105176A1 | Cites | United States of America | Applicant |
| US2017255263A1 | Cites | United States of America | Applicant |
| US2018190451A1 | Cites | United States of America | Applicant |
| CN2596671Y | Cites | China | Applicant |
| US5248919A | Cites | United States of America | Applicant |
| US5264761A | Cites | United States of America | Applicant |
| US8009042B2 | Cites | United States of America | Applicant |
| US8199010B2 | Cites | United States of America | Applicant |
| US8228184B2 | Cites | United States of America | Applicant |
| US8330638B2 | Cites | United States of America | Applicant |
| US8410706B2 | Cites | United States of America | Applicant |
| US8451116B2 | Cites | United States of America | Applicant |
| US8471779B2 | Cites | United States of America | Applicant |
| US8950461B2 | Cites | United States of America | Applicant |
| US9049756B2 | Cites | United States of America | Applicant |
| US9115537B2 | Cites | United States of America | Applicant |
| US9208965B2 | Cites | United States of America | Applicant |
| US9368025B2 | Cites | United States of America | Applicant |
| US9418802B2 | Cites | United States of America | Applicant |
| US9520247B1 | Cites | United States of America | Applicant |
| US9583288B2 | Cites | United States of America | Applicant |
| US9799469B2 | Cites | United States of America | Applicant |
| US9959997B2 | Cites | United States of America | Applicant |
| US20060055582A1 | Cites | United States of America | Applicant |
| US20070103326A1 | Cites | United States of America | Applicant |
| US20080111491A1 | Cites | United States of America | Applicant |
| US20080258650A1 | Cites | United States of America | Applicant |
| US20090128361A1 | Cites | United States of America | Applicant |
| US20110006879A1 | Cites | United States of America | Applicant |
| US20120286940A1 | Cites | United States of America | Applicant |
| US20130030589A1 | Cites | United States of America | Applicant |
| US20130110195A1 | Cites | United States of America | Applicant |
| US20140132475A1 | Cites | United States of America | Applicant |
| US20140177469A1 | Cites | United States of America | Applicant |
| US20140265568A1 | Cites | United States of America | Applicant |
| US20150077021A1 | Cites | United States of America | Applicant |
| US20150351205A1 | Cites | United States of America | Applicant |
| US20150371534A1 | Cites | United States of America | Applicant |
| US20150382436A1 | Cites | United States of America | Applicant |
| US20160073479A1 | Cites | United States of America | Applicant |
| US20170105176A1 | Cites | United States of America | Applicant |
| US20170255263A1 | Cites | United States of America | Applicant |
| US20180190451A1 | Cites | United States of America | Applicant |
38 members in 6 offices
Members38
| Document | Office | Kind | |
|---|---|---|---|
| CA3040512A1 | Canada | A1 | |
| CA3157220A1 | Canada | A1 | |
| CA3157231A1 | Canada | A1 | |
| CA3208177A1 | Canada | A1 | |
| US2018114434A1 | United States of America | A1 | |
| US2018116040A1 | United States of America | A1 | |
| WO2018075976A1 | World Intellectual Property Organization (WIPO) | A1 | |
| US10342103B2 | United States of America | B2 | |
| EP3530080A1 | European Patent Office (EPO) | A1 | |
| US10420194B2This record | United States of America | B2 | |
| CN110268805A | China | A | |
| MX2019004462A | Mexico | A | |
| US2019297713A1 | United States of America | A1 | |
| US2020015341A1 | United States of America | A1 | |
| US10624184B2 | United States of America | B2 | |
| US10694613B2 | United States of America | B2 | |
| US2020205274A1 | United States of America | A1 | |
| US2020288559A1 | United States of America | A1 | |
| CN110268805B | China | B | |
| EP3530080B1 | European Patent Office (EPO) | B1 | |
| US11417203B2 | United States of America | B2 | |
| CN114980398A | China | A | |
| US2022327917A1 | United States of America | A1 | |
| MX2021014408A | Mexico | A | |
| EP4149212A1 | European Patent Office (EPO) | A1 | |
| US11715368B2 | United States of America | B2 | |
| CA3040512C | Canada | C | |
| US2023334979A1 | United States of America | A1 | |
| US11869345B2 | United States of America | B2 | |
| US2024096207A1 | United States of America | A1 | |
| EP4149212B1 | European Patent Office (EPO) | B1 | |
| EP4498759A2 | European Patent Office (EPO) | A2 | |
| MX388158B | Mexico | B | |
| US12300097B2 | United States of America | B2 | |
| US2025166493A1 | United States of America | A1 | |
| US12322281B2 | United States of America | B2 | |
| US2025182611A1 | United States of America | A1 | |
| EP4498759A3 | European Patent Office (EPO) | A3 |
77 transactions on the USPTO file
Allowed after 1 RCE.
- Non-final rejections
- 0
- Final rejections
- 0
- RCEs
- 1
- Appeals
- 0
Over time
Point at a mark for the transactionTransactions
| Event | Code | |
|---|---|---|
| Payment of Maintenance Fee, 4th Year, Large EntityM1551 | M1551 | |
| Recordation of Patent Grant MailedPGM/ | PGM/ | |
| Patent Issue Date Used in PTA CalculationAllowedPTAC | PTAC | |
| Email NotificationEML_NTR | EML_NTR | |
| Issue Notification MailedAllowedWPIR | WPIR | |
| Dispatch to FDCD1935 | D1935 | |
| Email NotificationEML_NTR | EML_NTR | |
| Mail Response to 312 Amendment (PTO-271)MN271 | MN271 | |
| Response to Amendment under Rule 312N271 | N271 | |
| Pubs Case Remand to TCPUBTC | PUBTC | |
| Application Is Considered Ready for IssuePILS | PILS | |
| Amendment after Notice of Allowance (Rule 312)AllowedA.NA | A.NA | |
| Miscellaneous Incoming LetterLET. | LET. | |
| Supplemental Papers - Oath or DeclarationC600 | C600 | |
| Issue Fee Payment VerifiedN084 | N084 | |
| Issue Fee Payment ReceivedIFEE | IFEE | |
| Email NotificationEML_NTR | EML_NTR | |
| Email NotificationEML_NTR | EML_NTR | |
| Filing Receipt - CorrectedFLRCPT.C | FLRCPT.C | |
| Change in Power of Attorney (May Include Associate POA)PA.. | PA.. | |
| Supplemental Papers - Oath or DeclarationC600 | C600 | |
| Miscellaneous Incoming LetterLET. | LET. | |
| Email NotificationEML_NTR | EML_NTR | |
| Printer Rush- No mailingTCPB | TCPB | |
| Mailing Corrected Notice of AllowabilityMCNOA | MCNOA | |
| Corrected Notice of AllowabilityCNOA | CNOA | |
| Pubs Case Remand to TCPUBTC | PUBTC | |
| Electronic ReviewELC_RVW | ELC_RVW | |
| Email NotificationEML_NTF | EML_NTF | |
| Mail Notice of AllowanceAllowedMN/=. | MN/=. | |
| Notice of Allowance Data Verification CompletedAllowedN/=. | N/=. | |
| Reasons for AllowanceEX.R | EX.R | |
| Information Disclosure Statement consideredIDSC | IDSC | |
| Disposal for a RCE / CPA / R129AbandonedABN9 | ABN9 | |
| Information Disclosure Statement (IDS) FiledM844 | M844 | |
| Request for Continued Examination (RCE)RCEX | RCEX | |
| Information Disclosure Statement (IDS) FiledWIDS | WIDS | |
| Workflow - Request for RCE - BeginBRCE | BRCE | |
| Information Disclosure Statement (IDS) FiledM844 | M844 | |
| Electronic ReviewELC_RVW | ELC_RVW | |
| Email NotificationEML_NTF | EML_NTF | |
| Mail Notice of AllowanceAllowedMN/=. | MN/=. | |
| Notice of Allowance Data Verification CompletedAllowedN/=. | N/=. | |
| Reasons for AllowanceEX.R | EX.R | |
| Examiner's Amendment CommunicationEX.A | EX.A | |
| Interview Summary - Examiner Initiated - TelephonicEXET | EXET | |
| Information Disclosure Statement consideredIDSC | IDSC | |
| Date Forwarded to ExaminerFWDX | FWDX | |
| Response to Election / Restriction FiledELC. | ELC. | |
| Information Disclosure Statement (IDS) FiledM844 | M844 | |
| Information Disclosure Statement (IDS) FiledWIDS | WIDS | |
| Electronic ReviewELC_RVW | ELC_RVW | |
| Email NotificationEML_NTF | EML_NTF | |
| Mail Restriction RequirementMCTRS | MCTRS | |
| Restriction/Election RequirementCTRS | CTRS | |
| Information Disclosure Statement consideredIDSC | IDSC | |
| Information Disclosure Statement (IDS) FiledWIDS | WIDS | |
| Information Disclosure Statement (IDS) FiledM844 | M844 | |
| Email NotificationEML_NTR | EML_NTR | |
| PG-Pub Issue NotificationPG-ISSUE | PG-ISSUE | |
| Case Docketed to Examiner in GAUDOCK | DOCK | |
| Case Docketed to Examiner in GAUDOCK | DOCK | |
| Application Dispatched from OIPEOIPE | OIPE | |
| Email NotificationEML_NTR | EML_NTR | |
| Application ready for PDX access by participating foreign officesCCRDY | CCRDY | |
| Application Is Now CompleteCOMP | COMP | |
| Filing ReceiptFLRCPT.O | FLRCPT.O | |
| Application Is Now CompleteCOMP | COMP | |
| Sent to Classification ContractorPGPC | PGPC | |
| FITF set to YES - revise initial settingFTFS | FTFS | |
| Cleared by OIPE CSRL194 | L194 | |
| Patent Term Adjustment - Ready for ExaminationPTA.RFE | PTA.RFE | |
| PTO/SB/69-Authorize EPO Access to Search ResultsSREXR141 | SREXR141 | |
| Applicants have given acceptable permission for participating foreignAPPERMS | APPERMS | |
| IFW Scan & PACR Auto Security ReviewSCAN | SCAN | |
| Entity Status Set To Undiscounted (Initial Default Setting or Status Change)BIG. | BIG. | |
| Initial Exam Team nnIEXX | IEXX |
11 legal events, as the office reported them to INPADOC
Over the term
Point at a mark for the eventEvents
| Event | Code | |
|---|---|---|
| Maintenance fee paymentMAFP | MAFP | |
| Information on status: patent grantGrantedPATENTED CASESTCF | STCF | |
| Information on status: patent application and granting procedure in generalPUBLICATIONS -- ISSUE FEE PAYMENT VERIFIEDSTPP | STPP | |
| Information on status: patent application and granting procedure in generalAWAITING TC RESP, ISSUE FEE PAYMENT VERIFIEDSTPP | STPP | |
| Information on status: patent application and granting procedure in generalAWAITING TC RESP., ISSUE FEE NOT PAIDSTPP | STPP | |
| AssignmentAS | AS | |
| AssignmentAS | AS | |
| Information on status: patent application and granting procedure in generalNOTICE OF ALLOWANCE MAILED -- APPLICATION RECEIVED IN OFFICE OF PUBLICATIONSSTPP | STPP | |
| Information on status: patent application and granting procedure in generalDOCKETED NEW CASE - READY FOR EXAMINATIONSTPP | STPP | |
| Information on status: patent application and granting procedure in generalNOTICE OF ALLOWANCE MAILED -- APPLICATION RECEIVED IN OFFICE OF PUBLICATIONSSTPP | STPP | |
| Fee payment procedureENTITY STATUS SET TO UNDISCOUNTED (ORIGINAL EVENT CODE: BIG.); ENTITY STATUS OF PATENT OWNER: LARGE ENTITYFEPP | FEPP |
Numbers
- Publication
- 10420194
- Application
- 15789912
Titles
- English
- Controlling groups of electrical loads
Patent term adjustment
- Applicant delay
- −47 days
- Net adjustment
- 0 days
Classification
- CPC, 20
- H05B31/50
- H05B37/0272
- G08C17/02
- G05B15/02
- H05B47/115
- H05B47/19
- H05B37/0218
- E06B9/38
- H05B37/0227
- G08C2201/12
- G08C2201/50
- G08C2201/70
- H05B47/199
- H05B47/1965
- H05B47/196
- Y02A30/24
- Y02B80/00
- H05B47/105
- Y02B20/40
- H05B47/11
- IPC, 6
- G05B19 18
- G05B11 01
- H05B37 02
- G05B15 02
- G08C17 02
- E06B9 38