Patent Description:
A 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 adjust the lighting level (e.g., dim the intensity) of the lighting devices.

Lighting 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 and/or toggling the group of lighting devices on and off. Multiple lighting devices in the system may be independently controlled by another lighting control device. Control of the lighting devices may be based on a user interaction at the lighting control device. The user interaction may span a period of time, over which the lighting control device may transmit multiple wireless signals. The wireless signals may include a command to control the lighting devices. As the signals are transmitted wirelessly, observed dimming performance may be negatively impacted by inherent latency due to the RF protocol used to communicate the wireless signals. Further, the lighting devices may become out of sync with one another and/or may not be controlled in a uniform manner. As a result, it may appear to a user that the lighting control device is not functioning properly (e.g., the lighting device is unable to control the lighting devices) and may result in a poor user experience.

<CIT> describes a remote control device that provides a retrofit solution for an existing switched control system. The remote control device may comprise a control circuit, a rotatable portion, a magnetic ring coupled to the rotatable portion, and first and second Hall-effect sensor circuits configured to generate respective first and second sensor control signals in response to magnetic fields generated by the magnetic elements. The control circuit may operate in a normal mode when the rotatable portion is being rotated, and in a reduced-power mode when the rotatable portion is not being rotated. The control circuit may disable the second Hall-effect sensor circuit in the reduced-power mode. The control circuit may detect movement of the rotatable portion in response to the first sensor control signal in the reduced-power mode and enable the second Hall-effect sensor circuit in response to detecting movement of the rotatable portion.

The invention relates to a remote control device according to claim <NUM>, a non-transitory tangible computer readable medium according to claim <NUM> and a method according to claim <NUM>. As disclosed herein, a remote control device for controlling lighting devices may be configured to detect a continued and/or excessive user interaction and reduce the number of command messages that are transmitted to prevent the lighting devices from producing undesirable visual effects. The remote control device may comprise a user interface and a processor configured to receive an indication of a user interaction via the user interface. The processor may periodically transmit command messages at a transmission frequency in response to a continued user interaction, where each of the command messages comprise a respective command for adjusting to a respective lighting level. The processor may start a usage timer in response to receiving the indication of the user interaction, and decrease the transmission frequency in response to the usage timer exceeding a usage threshold. For example, the user interface may comprise a rotation portion (e.g., a rotary knob) for receiving user inputs for raising and lowering a lighting level of the lighting devices (e.g., rotation of the rotation portion). The processor may illuminate a visual indicator of the user interface when the usage timer exceeds the usage threshold to indicate to the user that the remote control device has entered a reduced transmission state.

The processor may monitor usage of the rotation portion when the usage timer exceeds the usage threshold to determine if the transmission frequency should be decreased. The remote control device may measure an angular velocity of the rotation portion (e.g., angular distance of rotation over time) when the usage timer exceeds the usage threshold. For example, the remote control device may determine to decrease the transmission frequency if the angular velocity exceeds an angular velocity threshold. Also or alternatively, when the usage timer exceeds the usage threshold the remote control device may determine to decrease the transmission frequency if the change in the angular position of the rotation portion exceeds an angular position change threshold. The remote control device may determine a desired amount of change in a lighting level in response to the determined amount of change in the angular position of the rotation portion. The remote control device may determine to decrease the transmission frequency when the usage timer exceeds the usage threshold if, for example, the desired amount of change in the lighting level exceeds a lighting level change threshold.

The processor may be configured to decrease the transmission frequency by increasing the transmission interval from an initial value to an adjusted value (e.g., an increased transmission interval). For example, the adjusted value may be three to four times the initial value. The processor may be configured to decrease the transmission frequency to zero Hertz (e.g., such that the remote control device stops transmitting command messages). If the remote control device stops transmitting command messages, the remote control device may transmit a final command message in response to the processor detecting that the rotation (e.g., the continued user interaction) of the rotation portion of the user interface has stopped. The final command message may include a command for adjusting the lighting level based on the final position of the rotation portion.

The processor may be configured to decrease the transmission interval to the initial value (e.g., to return to a normal transmission state) when the rotation (e.g., the continued user interaction) of the rotation portion has stopped. For example, the processor may be configured to increase the transmission frequency to the initial frequency after a timeout period from when the processor detects that the rotation of the rotation portion has stopped.

<FIG> and <FIG> depict examples of a load control system <NUM> that may implement one or more message types for communicating messages (e.g., digital messages). As shown in <FIG>, the load control system <NUM> 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 <NUM> to an electric load in the load control system <NUM>.

Load 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 112a, 112b, and/or lighting device <NUM> (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.

A 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 <NUM>. The controller devices may include a wired or wireless device.

Control 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 <NUM>. The RF signals <NUM> may be communicated via an RF communication protocol (e.g., ZIGBEE; THREAD; near field communication (NFC); BLUETOOTH; BLUETOOTH LOW ENERGY (BLE), WI-FI; a proprietary communication protocol, such as CLEAR CONNECT or CLEAR CONNECT TYPE X, etc.). The digital messages may be transmitted as multicast messages and/or unicast messages via the RF signals <NUM>.

The lighting device <NUM> may be installed in a plug-in device <NUM>, such as a lamp (e.g., a table lamp). The plug-in device <NUM> may be coupled in series electrical connection between the AC power source <NUM> and the lighting device <NUM>. The plug-in device <NUM> may be plugged into an electrical receptacle <NUM> that is powered by the AC power source <NUM>. The plug-in device <NUM> may be plugged into the electrical receptacle <NUM> or a separate plug-in load control device that is plugged into the electrical receptacle <NUM> and configured to control the power delivered to the lighting device <NUM>.

The lighting devices 112a, 112b may be controlled by a wall-mounted load control device <NUM>. Though the lighting devices 112a, 112b are shown in <FIG>, any number of lighting devices may be implemented that may be supported by the wall-mounted load control device <NUM> and/or the AC power source <NUM>. The wall-mounted load control device <NUM> may be coupled in series electrical connection between the AC power source <NUM> and lighting devices 112a, 112b. The wall-mounted load control device <NUM> may include a mechanical switch <NUM> (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 <NUM> to the lighting devices 112a, 112b (e.g., for turning on and off the lighting devices 112a, 112b). The lighting devices 112a, 112b may be installed in respective ceiling mounted downlight fixtures 114a, 114b, or other lighting fixture mounted to another surface. The wall-mounted load control device <NUM> may be adapted to be wall-mounted in a standard electrical wallbox.

The remote control device <NUM> may be configured to transmit messages via the RF signals <NUM> for controlling the lighting devices 112a, 112b. For example, the remote control device <NUM> may be configured to transmit messages via the RF signals <NUM> to load control devices (e.g., the lighting devices 112a, 112b) that are within a wireless communication range of the remote control device. The remote control device <NUM> may be battery-powered.

The remote control device <NUM> may be a retrofit remote control device mounted over the toggle actuator of the mechanical switch <NUM>. The remote control device <NUM> may be configured to maintain the toggle actuator of the mechanical switch <NUM> 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 <NUM> to the lighting devices 112a, 112b. In addition, the remote control device <NUM> may be mounted to another structure (e.g., other than the toggle actuator of the mechanical switch <NUM>), 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 <NUM> may comprise a wall-mounted remote control device that replaces the previously-installed mechanical switch <NUM> and may be configured to operate as the remote control device <NUM> to control the lighting devices 112a, 112b (e.g., by transmitting messages via the RF signals <NUM>). Such a wall-mounted remote control device may derive power from the AC power source <NUM>.

The remote control device <NUM> may comprise a user interface having an actuation portion <NUM> (e.g., a "toggle" button), an intensity adjustment actuator, such as a rotation portion <NUM> (e.g., a rotary knob), and a visual indicator, such as a status indicator <NUM>. The actuation portion <NUM> may be actuated (e.g., pushed in towards the mechanical switch <NUM>) and the rotation portion <NUM> may be rotated (e.g., with respect to the mechanical switch <NUM>). The remote control device <NUM> may be configured to transmit messages including commands for turning the lighting devices 112a, 112b, <NUM> on and off in response to actuations (e.g., presses) of the actuation portion <NUM> and commands for adjusting a lighting level (e.g., an intensity or brightness) of the lighting devices 112a, 112b, <NUM> in response to actuations (e.g., rotations) of the rotation portion <NUM>. Though a rotation portion <NUM> is disclosed, the user interface of the remote control device <NUM> 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 lighting devices 112a, 112b may be turned on or off, or the lighting level may be adjusted, in response to the remote control device <NUM> (e.g., in response to actuations of the actuation portion <NUM> of the remote control device <NUM>). For example, the lighting devices 112a, 112b may be toggled on or off by a toggle event identified at the remote control device <NUM>. The toggle event may be a user event identified at the remote control device <NUM>. The actuation portion <NUM> of the remote control device <NUM> may be actuated to toggle the lighting devices 112a, 112b on or off. The rotation portion <NUM> of the remote control device <NUM> may be rotated to adjust the intensities of the lighting devices 112a, 112b. The toggle event may be identified when the rotation portion <NUM> of the remote control device <NUM> is turned by a predefined amount or for a predefined time, and/or the actuation portion <NUM> of the remote control device <NUM> is actuated. The lighting level of the lighting devices 112a, 112b may be increased or decreased by rotating the rotation portion <NUM> of the remote control device <NUM> in one direction or another, respectively. Though shown as comprising a rotary knob in <FIG> and <FIG>, the remote control device <NUM> 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.

The remote control device <NUM> may provide feedback (e.g., visual feedback) to a user of the remote control device <NUM> on the status indicator <NUM>. The status indicator <NUM> 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 <NUM>, and/or a status of the load control devices being controlled by the remote control device <NUM>. 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.

The status indicator <NUM> may be illuminated by one or more light emitting diodes (LEDs) for providing feedback. The status indicator <NUM> may be a light bar included around the entire perimeter of the remote control device <NUM>, or a portion thereof. The status indicator <NUM> may also, or alternatively be a light bar in a line on the remote control device <NUM>, such as when the remote control device is a paddle switch or a linear control, for example.

Example types of feedback may include illumination of the entire status indicator <NUM> (e.g., to different lighting levels), blinking or pulsing one or more LEDs in the status indicator <NUM>, changing the color of one or more LEDs on the status indicator <NUM>, and/or illuminating different sections of one or more LEDs in the status indicator <NUM> to provide animation (e.g., clockwise and counter clockwise animation for raising and lowering a lighting level). The feedback on the status indicator <NUM> may indicate a status of an electrical load or a load control device, such as a lighting level for lights (e.g., lighting devices 112a, 112b, <NUM>), 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 <NUM> may change based on the selection of different presets. For example, a different LED or LEDs may be illuminated on the status indicator <NUM> to identify different presets (e.g., preset lighting levels for the lighting devices 112a, 112b, <NUM>, and/or other preset configurations for load control devices).

The remote control device <NUM> may transmit digital messages via the RF signals <NUM> to control the lighting devices 112a, 112b, <NUM>. The remote control device <NUM> may be configured to transmit an on command for turning the lighting devices 112a, 112b, <NUM> on (e.g., an "on" event). For example, the on command may case the lighting devices 112a, 112b, <NUM> to turn on to a maximum lighting level (e.g., a maximum intensity, such as <NUM>%), to a predetermined lighting level, and/or to a previous lighting level (e.g., an "on" event). In addition, the remote control device <NUM> may be configured to transmit an off command for turning the lighting devices 112a, 112b, <NUM> off (e.g., <NUM>%). Further , the remote control device <NUM> may be configured to transmit a toggle command for toggling the state of the lighting devices 112a, 112b, <NUM> (e.g., causing the lighting devices to turn from off to on (e.g., an "on" event, or from on to off (e.g., an "off" event). The lighting level for the "on" event and/or the "off" event may also, or alternatively, be stored at the lighting devices 112a, 112b, <NUM>, 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 <NUM>. The digital messages may cause an "on" event when the remote control device <NUM> is rotated a predefined distance or time in one direction. As an example, the remote control device <NUM> may transmit digital messages when the remote control device <NUM> is identified as being rotated for <NUM> milliseconds (ms). The digital messages may indicate an "off" event when the remote control device <NUM> 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 actuation portion <NUM> of the remote control device <NUM> is actuated.

The remote control device <NUM> may be configured to adjust the intensities of the lighting devices 112a, 112b, <NUM> using absolute control in order to control the intensities of the lighting devices 112a, 112b, <NUM> to an absolute level (e.g., a specific level). For example, the remote control device <NUM> 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 cause an "on" event or an "off" event to turn the lighting devices 112a, 112b, <NUM> on or off, respectively. For example, the "on" event may be caused by a move-to-level command with a lighting level of <NUM>%, or another preset lighting level. The "off" event may be caused by a move-to-level command with a lighting level of <NUM>%.

In 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 <NUM>) at the remote control device <NUM>, the remote control device <NUM> may determine a starting point (e.g., a dynamic starting point) from which the lighting level of one or more of the lighting devices 112a, 112b, <NUM> may be controlled. Each rotation of the rotation portion <NUM> may cause the remote control device <NUM> 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 <NUM>), the remote control device <NUM> may transmit a status query message to the lighting devices 112a, 112b, <NUM> to query for a current status (e.g., after awakening from sleep mode). The current status of one or more of the lighting devices 112a, 112b, <NUM> may be used to set the dynamic starting point from which the remote control device <NUM> may perform control. For example, the remote control device <NUM> may set the dynamic starting point of the rotation portion <NUM> to the current lighting level (e.g., on, off, <NUM>%, <NUM>%, etc.) of the first of the lighting devices 112a, 112b, <NUM> to respond to the status query message, or a predefined lighting device 112a, 112b, <NUM>. Examples of remote control devices configured to transmit status query messages prior to transmitting commands are described in greater detail in commonly-assigned <CIT>, entitled CONTROLLING GROUPS OF ELECTRICAL LOADS,.

In another example, the remote control device <NUM> may set the dynamic starting point of the rotation portion <NUM> based on the lighting levels of multiple lighting devices 112a, 112b, <NUM>. The remote control device <NUM> may set the dynamic starting point of the rotation portion <NUM> to an average lighting level (e.g., on, off, <NUM>%, <NUM>%, etc.) of the lighting devices 112a, 112b, <NUM>, or a common lighting level (e.g., on, off, <NUM>%, <NUM>%, etc.) of a majority of the lighting devices 112a, 112b, <NUM>, for example. The remote control device <NUM> may set the dynamic starting point of the rotation portion <NUM> to a maximum lighting level of the lighting devices 112a, 112b, <NUM> when the rotation portion <NUM> is being rotated clockwise to raise the lighting level of the lighting devices, or a minimum level of the lighting devices 112a, 112b, <NUM> when the rotation portion <NUM> is being rotated counterclockwise to lower the lighting level of the lighting devices, for example. The status indicator <NUM> may be illuminated as feedback to reflect the dynamic starting point to the user. For example, the remote control device <NUM> may illuminate a portion of the status indicator <NUM> that reflects the lighting level that is set as the dynamic starting point.

The remote control device <NUM> may calculate an increase or decrease in the lighting level from the dynamic starting point based on the user interface event. For example, the remote control device <NUM> may calculate an increase or decrease in the lighting level based on the distance or amount of time the rotation portion <NUM> is turned. The rotation from the point of the initial interaction by the user with the rotation portion <NUM> may be used to identify the increase or decrease in the lighting level from the dynamic starting point. When the remote control device <NUM> includes a linear control, the remote control device <NUM> may calculate an increase or decrease in the lighting 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 the lighting level from the dynamic starting point.

The updated lighting level may be calculated from the user's initial interaction and stored at the remote control device <NUM>. The updated lighting level may be included in a move-to-level command that is transmitted from the remote control device <NUM> to the lighting devices 112a, 112b, <NUM> when the remote control device <NUM> is using absolute control.

The visual feedback displayed by the status indicator <NUM> may be provided in or derived from the information in the move-to-level command when the remote control device <NUM> is using absolute control. For example, the remote control device <NUM> may reflect the lighting level transmitted in the move-to-level command in the status indicator <NUM>.

The remote control device <NUM> may transmit digital messages configured to increase the lighting level of the lighting devices 112a, 112b, <NUM> when the rotation portion <NUM> is rotated in a direction (e.g., clockwise). As previously mentioned, the remote control device <NUM> may be configured to adjust the intensities of the lighting devices 112a, 112b, <NUM> to an absolute level using absolute control. In addition, or alternatively, the remote control device <NUM> may be configured to adjust the intensities of the lighting devices 112a, 112b, <NUM> using relative control to adjust the intensities of the light devices 112a, 112b, <NUM> by a relative amount. For example, the remote control device <NUM> may transmit digital messages configured to decrease the lighting level of the lighting devices 112a, 112b, <NUM> when the remote control device <NUM> 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 112a, 112b, <NUM> to change their respective lighting level by a predefined amount. The move-with-rate command may include an 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 112a, 112b, <NUM> to retain their relative or proportional lighting levels, and/or difference in respective lighting levels. The remote control device <NUM> 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 112a, 112b, <NUM>. The digital messages may also include a move-to-level-over-time command, which may include both a lighting level to which to control the lighting devices 112a, 112b, <NUM>, and an amount of time over which the lighting level may be changed at the lighting devices.

The remote control device <NUM> may transmit digital messages that include move-with-rate commands to increase or decrease the lighting level of the lighting devices 112a, 112b, <NUM> in predefined increments as the user turns the remote control device <NUM> a predefined distance or time in one direction or another. The remote control device <NUM> may continue to transmit digital messages to the lighting devices 112a, 112b, <NUM> as the user continues to turn the remote control device <NUM>. For example, the remote control device <NUM> 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 112a, 112b, <NUM> to each increase by ten percent (<NUM>%). The remote control device <NUM> may identify a continued rotation of a predefined distance or time and send digital messages to instruct the lighting devices 112a, 112b, <NUM> to increase by ten percent (<NUM>%) again.

The remote control device <NUM> may also, or alternatively, send digital messages for a direct command (e.g., "on" command, "off" command, toggle command, etc.) to turn on/off the lighting devices 112a, 112b, <NUM>. The remote control device <NUM> may transmit one or more digital messages to the lighting devices 112a, 112b, <NUM> when an on event or an off event are detected. For example, the remote control device <NUM> may identify a rotation or actuation and send digital messages to instruct the lighting devices 112a, 112b, <NUM> to turn on and/or off. The remote control device <NUM> may operate by sending a move-with-rate command after turning on. For example, the remote control device <NUM> may identify a rotation of a predefined distance or time after turning on and send digital messages to instruct the lighting devices 112a, 112b, <NUM> to increase and/or decrease their lighting levels by a predefined lighting level (e.g., approximately <NUM>%).

The remote control device <NUM> may transmit the digital messages as multicast messages and/or unicast messages via the RF signal <NUM>. For example, the digital messages including a direct command (e.g., an on command, an off command, and/or a toggle command) and/or a move-to-level command that causes an "on" event or an "off" event may be transmitted as multicast messages. In addition, the digital messages including the move-to-level command that causes the lighting devices 112a, 112b, <NUM> to adjust their intensities by a large amount may be transmitted as multicast messages. The multicast messages may be communicated efficiently from the remote control device <NUM> as a single message may be transmitted to multiple lighting devices, such as lighting devices 112a, 112b, <NUM>, at once. The load control instructions in the multicast messages may be received and implemented by multiple lighting devices, such as lighting devices 112a, 112b, <NUM>, 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. For example, the lighting devices 112a, 112b, <NUM> may not transmit acknowledgement messages to the remote control device <NUM> in response to receiving multicast messages from the remote control device.

The multicast messages may include a group identifier for controlling the lighting devices 112a, 112b, <NUM> that are a part of the multicast group. The lighting devices 112a, 112b, <NUM> 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 112a, 112b, <NUM> 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 112a, 112b, <NUM> may forward the multicast messages with the group identifier for identification and load control by other lighting devices associated with the group identifier. The group may be formed at commissioning or configuration of the load control system <NUM>. The remote control device <NUM> may generate the group identifier and send the group identifier to the lighting devices 112a, 112b, <NUM> and/or a system controller (e.g., a hub device) when the remote control device <NUM> 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 <NUM> and can respond to group messages.

The digital messages may also be transmitted via the RF signals <NUM> as multicast messages. The number of multicast messages sent in the wireless communication network may be limited according to a standard, for example, to prevent interference or link saturation on the network. For example, using the ZIGBEE® protocol, a remote control device may be prevented from transmitting more than nine (<NUM>) multicast messages over a nine (<NUM>) second period of time to control lighting devices. If the remote control device exceeds the limit, the lighting devices may lock up for a period of time (e.g., a number of seconds) before allowing control from another message. Thus, the transmission of multicast messages may be rate limited, which may cause communications to the lighting devices to be interrupted or limited. For example, communication to the lighting device may be stopped when the rate limit is exceeded, and the transition in lighting levels may be discrete or choppy, which may be undesirable.

Accordingly, digital messages including the move-to-level command that do not cause the lighting devices 112a, 112b, <NUM> to adjust their intensities by a large amount may be transmitted as multicast messages. 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 <NUM> directly to each of the lighting devices 112a, 112b, <NUM>. Also, or alternatively, unicast messages may be sent from the remote control device <NUM> to each of the lighting devices 112a, 112b, <NUM> via one or more hops (e.g., intermediary devices in the load control system that may retransmit the message to another control device for retransmission and/or to one of the respective lighting devices 112a, 112b, <NUM>). The remote control device <NUM> may individually send a unicast message to each of the lighting devices 112a, 112b, <NUM> with which the remote control device <NUM> is associated for performing load control. The remote control device <NUM> may have the unique identifier of each of the lighting devices 112a, 112b, <NUM> with which it is associated stored in memory. The remote control device <NUM> may generate a separate unicast message for each lighting device 112a, 112b, <NUM> and address the unicast messages to the lighting devices 112a, 112b, <NUM> independently. The unicast messages may also include the unique identifier of the remote control device <NUM>. The lighting devices 112a, 112b, <NUM> 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 112a, 112b, <NUM> 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 <NUM>. For example, when using some RF communication protocols (e.g., such as, ZIGBEE and THREAD), the lighting devices 112a, 112b, <NUM> may each transmit an acknowledgement message to the remote control device <NUM> in response to receiving a unicast message from the remote control device. However, for other RF communication protocols (e.g., such as, BLUETOOTH), the lighting devices 112a, 112b, <NUM> may not transmit acknowledgement messages to the remote control device <NUM> in response to receiving unicast messages from the remote control device.

Embodiments 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.

<FIG> shows an example of the load control system <NUM> having other devices. For example, the load control system <NUM> 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.

Examples of load control devices may include a motorized window treatment <NUM> and/or the lighting devices 112a, 112b, <NUM>, though other load control devices may be implemented. The controller devices may include the batter powered remote control device <NUM>, though other controller devices may be implemented. The controller devices may perform communications in a configuration similar to the remote control device <NUM> as described herein. The load control devices may perform communications in a configuration similar to the lighting devices 112a, 112b, <NUM> as described herein.

The load control devices may receive digital messages via wireless signals, e.g., radio-frequency (RF) signals <NUM>. The wireless signals may be transmitted by the controller devices. In response to the received digital messages, the respective lighting devices 112a, 112b, <NUM> may be turned on and off, and/or the intensities of the respective lighting devices 112a, 112b, <NUM> may be increased or decreased. In response to the received digital messages, the motorized window treatment <NUM> may increase or decrease a level of a covering material <NUM>.

The battery-powered remote control device <NUM> may include one or more actuators <NUM> (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 <NUM> may transmit RF signals <NUM> in response to actuations of one or more of the actuators <NUM>. The battery-powered remote control device <NUM> may be handheld. The battery-powered remote control device <NUM> may be mounted vertically to a wall, or supported on a pedestal to be mounted on a tabletop. The battery-powered remote control device <NUM> may be a wireless device capable of controlling a load control device via wireless communications. Examples of remote control devices are described in greater detail in commonly-assigned <CIT>, entitled WIRELESS BATTERY-POWERED REMOTE CONTROL HAVING MULTIPLE MOUNTING MEANS, and <CIT>, entitled WIRELESS BATTERY-POWERED REMOTE CONTROL WITH LABEL SERVING AS ANTENNA ELEMENT,.

The occupancy sensor <NUM> may be configured to detect occupancy and/or vacancy conditions in the space in which the load control system <NUM> is installed. The occupancy sensor <NUM> may transmit digital messages to load control devices via the RF communication signals <NUM> in response to detecting the occupancy or vacancy conditions. The occupancy sensor <NUM> 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 <NUM> may enter an association mode and may transmit association messages via the RF communication signals <NUM> in response to actuation of a button on the occupancy sensor <NUM>. Examples of RF load control systems having occupancy and vacancy sensors are described in greater detail in commonly-assigned <CIT>, entitled RADIO-FREQUENCY LIGHTING CONTROL SYSTEM WITH OCCUPANCY SENSING.

The daylight sensor <NUM> may be configured to measure a total light level in the space in which the load control system <NUM> is installed. The daylight sensor <NUM> may transmit digital messages including the measured light level via the RF communication signals <NUM> for controlling load control devices in response to the measured light level. The daylight sensor <NUM> may enter an association mode and may transmit association messages via the RF communication signals <NUM> in response to actuation of a button on the daylight sensor <NUM>. Examples of RF load control systems having daylight sensors are described in greater detail in commonly-assigned <CIT>, entitled WIRELESS BATTERY-POWERED DAYLIGHT SENSOR.

The motorized window treatment <NUM> may be mounted in front of a window for controlling the amount of daylight entering the space in which the load control system <NUM> is installed. The motorized window treatment <NUM> 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 system, or another suitable motorized window covering. The motorized window treatment <NUM> may include a motor drive unit <NUM> for adjusting the position of a covering material <NUM> of the motorized window treatment <NUM> in order to control the amount of daylight entering the space. The motor drive unit <NUM> of the motorized window treatment <NUM> may have an RF receiver and an antenna mounted on or extending from a motor drive unit <NUM> of the motorized window treatment <NUM>. The motor drive unit <NUM> may respond to digital messages to increase or decrease the level of the covering material <NUM>. The motor drive unit <NUM> of the motorized window treatment <NUM> 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 <CIT>, entitled MOTORIZED WINDOW TREATMENT, and <CIT>, entitled BATTERY-POWERED ROLLER SHADE SYSTEM.

Digital 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 112a, 112b, <NUM> and/or the motorized window treatment <NUM> during a configuration procedure of the load control system <NUM>, such that the lighting devices 112a, 112b, <NUM> and/or the motorized window treatment <NUM> may be responsive to digital messages transmitted by the controller devices via the RF signals <NUM>. Examples of associating wireless control devices during a configuration procedure are described in greater detail in commonly-assigned <CIT>, entitled RADIO-FREQUENCY LIGHTING CONTROL SYSTEM, and <CIT>, entitled TWO-PART LOAD CONTROL SYSTEM MOUNTABLE TO A SINGLE ELECTRICAL WALLBOX.

The load control system <NUM> may include a system controller <NUM> (e.g., a hub device or a system bridge) configured to enable communication with a network <NUM>, e.g., a wireless or wired local area network (LAN). For example, the system controller <NUM> may be connected to a network router (not shown) via a wired digital communication link <NUM> (e.g., an Ethernet communication link). The network router may allow for communication with the network <NUM>, e.g., for access to the Internet. The system controller <NUM> may be wirelessly connected to the network <NUM>, e.g., using wireless technology, such as WI-FI® technology, cellular technology, etc. The system controller <NUM> may be configured to transmit communication signals (e.g., RF signals <NUM>) to the lighting devices 112a, 112b, <NUM>, and/or the motorized window treatment <NUM> for controlling the devices in response to digital messages received from external devices via the network <NUM>. The system controller <NUM> may be configured to transmit and/or receive RF signals <NUM>. The system controller <NUM> may be configured to transmit digital messages via the network <NUM> for providing data (e.g., status information) to external devices.

The system controller <NUM> may operate as a central controller for the load control system <NUM>, 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 <NUM>. The system controller <NUM> may receive digital messages from a controller device and configure the digital message for communication to a load control device. For example, the system controller <NUM> may configure multicast messages and/or unicast messages for transmission as described herein. The system controller <NUM> may be on-site at the load control system <NUM> or at a remote location. Though the system controller <NUM> is shown as a single device, the load control system <NUM> may include multiple hubs and/or the functionality thereof may be distributed across multiple devices.

The load control system <NUM> may include a network device <NUM>, such as, a smart phone, a personal computer (PC), a laptop, a wireless-capable media device (e.g., a media player, gaming device, or television), a tablet device (e.g., a hand-held computing device), a wireless-communication-capable television, or any other suitable network communication or Internet-Protocol-enabled device. The network device <NUM> may be operable to transmit digital messages in one or more Internet Protocol packets to the system controller <NUM> via RF signals <NUM>, either directly or via the network <NUM>. The RF signals <NUM> may be communicated using a different protocol and/or wireless band than the RF signals <NUM>. In another example, the RF signals <NUM> and the RF signals <NUM> 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 <CIT>, entitled LOAD CONTROL DEVICE HAVING INTERNET CONNECTIVITY.

The network device <NUM> may include a visual display <NUM>. The visual display <NUM> 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 <NUM> may include a plurality of hard buttons, e.g., physical buttons (not shown), in addition to the visual display <NUM>. The network device <NUM> may download a product control application for allowing a user of the network device <NUM> to control the load control system <NUM>. In response to actuations of the displayed soft buttons and/or hard buttons, the network device <NUM> may transmit digital messages to the load control devices and/or the system controller <NUM> through the wireless communications described herein.

The operation of the load control system <NUM> may be programmed and configured using the system controller <NUM> and/or network device <NUM>. An example of a configuration procedure for a wireless load control system is described in greater detail in commonly-assigned <CIT>, entitled COMMISSIONING LOAD CONTROL SYSTEMS.

The lighting devices 112a, 112b, <NUM> may each be included in a group of lighting devices that are associated with a common control device, such as the remote control device <NUM>. For example, each of the lighting devices 112a, 112b, <NUM> may store the unique identifier of the remote control device <NUM> during an association mode to enable the lighting devices 112a, 112b, <NUM> to be controlled by digital messages from the remote control device <NUM> that include control instructions. The system controller <NUM> may store the associations between each of the lighting devices 112a, 112b, <NUM> and the remote control device <NUM> during an association mode. The association information may be used by the system controller <NUM> for routing digital messages to the lighting devices 112a, 112b, <NUM>, or the lighting devices 112a, 112b, <NUM> may receive digital messages from the remote control device <NUM> directly.

The remote control device <NUM> may be configured to transmit messages to the lighting devices 112a, 112b, <NUM> via the system controller <NUM>. For example, the remote control device <NUM> may be configured to transmit unicast messages to the system controller <NUM>. The system controller <NUM> may be configured to transmit an acknowledgement message to the remote control device <NUM> in response to receiving a unicast message from the remote control device. The system controller <NUM> may be configured to transmit unicast and/or multicast messages to the lighting devices 112a, 112b, <NUM> for controlling the lighting devices in response to the unicast message received from the remote control device <NUM>. For example, the remote control device <NUM> may send transmit a message including a toggle command or an on/off command (e.g., an "on" command or an "off" command) for controlling the lighting devices 112a, 112b, <NUM> to toggle the lighting devices 112a, 112b, <NUM> from an "on" state to an "off" state, or vice versa. The remote control device <NUM> may transmit a unicast message including the toggle command or the on/off command to the system controller <NUM>, which may transmit a multicast message that is received at each of the lighting devices 112a, 112b, <NUM> In addition, the remote control device <NUM> may transmit a unicast message including a move-to-level command or a move-with-rate command to the system controller <NUM>, which may transmit unicast messages that are independently directed to each of the lighting devices 112a, 112b, <NUM>.

The remote control device <NUM> may use the lighting 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 112a, 112b, <NUM>. For example, in response to the status query message from the remote control device <NUM>, the lighting device 112a may respond by transmitting a status response message indicating that the lighting device <NUM> is at a lighting level of <NUM>%. The remote control device <NUM> may set the lighting level identified by the lighting device <NUM> as the dynamic starting point upon which control of the lighting level for the group of lighting devices 112a, 112b, <NUM> may be performed. The remote control device <NUM> may identify a continued rotation for increasing the lighting level by an additional <NUM>%. The remote control device <NUM> may add this <NUM>% to the dynamic starting point of <NUM>% that was indicated as the current lighting level of the lighting device 112a that responded to the previous status query message from the remote control device <NUM>. The remote control device <NUM> may send a digital message to the group of lighting devices 112a, 112b, <NUM> to control the group of lighting devices 112a, 112b, <NUM> to an absolute lighting level of <NUM>%. The digital message may include a go-to-level command that is configured to control each of the lighting devices 112a, 112b, <NUM> to a lighting level of <NUM>%. Each of the lighting devices 112a, 112b, <NUM> may receive the digital message (e.g., as a unicast message or a multicast message) and be controlled to the absolute lighting level of <NUM>%, unless the lighting device is already at the indicated lighting level. When the group of lighting devices 112a, 112b, <NUM> are in the same state, the group of lighting devices 112a, 112b, <NUM> may be controlled as a group. For example, the group of lighting devices 112a, 112b, <NUM> may be controlled together from <NUM>% to <NUM>%. When the state of the group of lighting devices 112a, 112b, <NUM> is out of sync, the lighting devices 112a, 112b, <NUM> may be controlled differently to reach the indicated lighting level. For example, the lighting devices 112a, 112b, <NUM> that are above the indicated lighting level may decrease the lighting level to meet the indicated lighting level. The lighting devices 112a, 112b, <NUM> that are below the indicated lighting level may increase in the lighting level to meet the indicated lighting level. The lighting devices 112a, 112b, <NUM> 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 <NUM>.

The lighting devices 112a, 112b, <NUM> may fade from one lighting level to another lighting level (e.g., be dimmed between lighting levels over a fade time and/or at a fade rate) in response to receiving a command. For example, the lighting devices 112a, 112b, <NUM> may be dimmed at a rate or over a period of time such that each of the lighting devices 112a, 112b, <NUM> that is not already at the indicated lighting level reaches the lighting level at the same time. For example, the remote control device <NUM> may send the go-to-level command with an amount of time or fade rate over which the lighting devices 112a, 112b, <NUM> are to be dimmed until the lighting devices 112a, 112b, <NUM> reach the indicated lighting level (e.g., different fade rates or fade times may be transmitted to each of the lighting devices 112a, 112b, <NUM>). The lighting devices 112a, 112b, <NUM> may be dimmed over the indicated period of time to the lighting level indicated in the go-to-level command. When one or more of the lighting devices 112a, 112b, <NUM> are at different lighting levels, the lighting devices 112a, 112b, <NUM> may be sent unicast messages with different fade rates such that the lighting devices 112a, 112b, <NUM> at different lighting levels reach the lighting 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 lighting level may be increased or decreased.

The system controller <NUM> may operate as a parent device (e.g., a master device) that may be configured to monitor the state of child devices (e.g., slave devices), such as lighting devices 112a, 112b, <NUM>, 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 system controller <NUM> 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 112a, 112b, <NUM>, remote control device <NUM>, occupancy sensor <NUM>, daylight sensor <NUM>, network device <NUM>, motorized window treatment <NUM>, a remote computing device, etc.) may be assigned as a master device that operates as described herein for the system controller <NUM>. When a lighting device 112a, 112b, <NUM> is assigned as the master device, the lighting device 112a, 112b, <NUM> 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 system controller <NUM>.

The system controller <NUM> may keep track of the on/off state of each of the lighting devices 112a, 112b, <NUM> after being implemented in the load control system <NUM>. Upon initial implementation into the load control system, the system controller <NUM> may transmit a status query message to the lighting devices 112a, 112b, <NUM> to query for their current on/off state. The status query message may be sent as a multicast message, or individual unicast messages, to each of the lighting devices 112a, 112b, <NUM>. The lighting devices 112a, 112b, <NUM> may return the current on/off state, which may be stored locally thereon. The system controller <NUM> may identify commands communicated to the lighting devices 112a, 112b, <NUM> and maintain the current on/off state of the lighting devices 112a, 112b, <NUM> in memory. The digital messages that are communicated to the lighting devices 112a, 112b, <NUM> for controlling the on/off state may be monitored to determine the current on/off state, without sending an initial status query message. The system controller <NUM> may be powered and/or awake at all times (e.g., at all times than the lighting devices 112a, 112b, <NUM> are also powered), such that the system controller <NUM> is able to monitor the states of the lighting devices by listening to the messages transmitted by the lighting devices. In addition, the system controller <NUM> may enter a sleep mode and periodically wake up to transmit status query messages to the lighting devices 112a, 112b, <NUM> to determine the on/off states of the lighting devices.

When the system controller <NUM> receives an indication of a toggle event from the remote control device <NUM>, the system controller <NUM> may choose the command to send, or whether to send a command, to the lighting devices 112a, 112b, <NUM>. The decision at the system controller <NUM> may be based on the current on/off state of the lighting devices 112a, 112b, <NUM>. The system controller <NUM> may identify whether the on/off state across the group of lighting devices 112a, 112b, <NUM> is consistent. If the on/off state across the group of lighting devices 112a, 112b, <NUM> is consistent, the system controller <NUM> may send the toggle command, or an "on" command or "off" command, to the lighting devices 112a, 112b, <NUM> to toggle the on/off state of the group of lighting devices 112a, 112b, <NUM>.

The lighting devices 112a, 112b, <NUM> that change an on/off state in response to an "on" command or an "off" command may send a state update message to the system controller <NUM> to indicate the change in on/off state. The system controller <NUM> may receive the state update message from the lighting devices 112a, 112b, <NUM> 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 system controller <NUM> may be unresponsive. For example, the system controller <NUM> may send an "off" command to the lighting devices 112a, 112b, <NUM> and the lighting device <NUM> may update the on/off state to the "off" state. The lighting device <NUM> may send a response message to the system controller <NUM> to indicate the change in state. The system controller <NUM> may store the updated state and/or confirm the state of the unresponsive devices. The system controller <NUM> may, alternatively, store the updated state of the lighting device <NUM> after sending the command. As the system controller <NUM> may be maintaining the on/off state of the lighting devices 112a, 112b, <NUM>, the remote control device <NUM> may go to sleep after transmitting a message in response to the toggle event.

<FIG> are communication flow diagrams depicting example message flows for generating lighting control commands in response to an actuation of an actuator (e.g., the actuation portion <NUM> and/or the rotation portion <NUM> of the remote control device <NUM>). <FIG> 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 <NUM>) and generating lighting control commands in response to the identified status. As shown in <FIG>, a remote control device <NUM> may transmit a status query message <NUM> for identifying the status of lighting devices, such as lighting devices 204a, 204b (e.g., the lighting devices 112a, 112b, <NUM>). The status query message <NUM> 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 <NUM>). The status query message <NUM> may be sent as a multicast message (e.g., as shown in <FIG>) or individual unicast messages that are received by the lighting devices 204a, 204b.

The remote control device <NUM> may receive a response to the status query message <NUM> from each of the lighting devices 204a, 204b that receive the status query message <NUM> and/or with which the remote control device <NUM> is associated. For example, the lighting device 204a may transmit a status response message <NUM> in response to the status query message <NUM> that indicates that the lighting device 204a is in the off state. The lighting device 204b may transmit a status response message <NUM> in response to the status query message <NUM> that indicates that the lighting device 204b is in the on state. The status response messages may also, or alternatively, indicate a lighting level (e.g., an intensity or brightness), a color (e.g., a color temperature), or other status of the lighting device from which the status message is transmitted.

If the remote control device <NUM> determines that any of the lighting devices 204a, 204b are in the on state, the remote control device <NUM> may be configured to transmit a default toggle command, such as the off command <NUM>. The off command <NUM> may be sent as a multicast message (e.g., as shown in <FIG>) or individual unicast messages that are received by the lighting devices 204a, 204b. Though an off command <NUM> may be transmitted as the default toggle command as shown in <FIG>, the remote control device <NUM> may transmit an on command or another default command in response to identifying a status of one or more of the lighting devices 204a, 204b. The lighting device 204b may turn to the off state in response to receiving the off command <NUM>.

The remote control device <NUM> may determine the control instructions for being sent to the lighting devices 204a, 204b based on the status of one of the lighting devices 204a, 204b. For example, the remote control device <NUM> may determine the control instructions for being sent to the lighting devices 204a, 204b based on the status of a master lighting device or a lighting device that is first to respond to the status query message <NUM>. The remote control device <NUM> may control the state of both of the lighting devices, 204a, 204b 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.

As shown in <FIG>, the remote control device <NUM> may respond to the status of the first lighting device 204a, 204b to respond to a status query message. For example, a status query message <NUM> may be sent as a multicast message (e.g., as shown in <FIG>) or a unicast message to each lighting device 204a, 204b. The lighting device 204a may be the first device to receive the status query message <NUM> and/or from which a status response message <NUM> is received in response. The status response message <NUM> may indicate the status of the lighting device 204a, which may cause the remote control device <NUM> to send the opposite command (e.g., an on command <NUM>). The on command <NUM> may be sent as a multicast message (e.g., as shown in <FIG>) or a unicast message. While not shown in <FIG>, the lighting device 204b may be the first device to receive the status query message <NUM> and/or from which a status response message is received in response. The status response message may indicate the status of the lighting device 204b, which may cause the remote control device <NUM> to send the opposite command (e.g., the off command <NUM>). The off command <NUM> may be sent as a multicast message or a unicast message.

Though not shown in <FIG>, the remote control device <NUM> may scan for lighting devices 204a, 204b in a preferred state (e.g., on/off state, lighting intensity, color, etc.). The remote control device <NUM> may send the status query message as a unicast message to each of the lighting devices 204a, 204b or as a multicast message to both lighting devices 204a, 204b. The remote control device <NUM> may continue to send a status query message to each of the lighting devices 204a, 204b until one of the lighting devices returns a non-preferred state. For example, remote control device <NUM> may send the status query message <NUM> to the lighting device 204a and receive the status response message <NUM> prior to sending a status query message to the lighting device <NUM>. The remote control device <NUM> may stop scanning for lighting devices when the remote control device <NUM> 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 <NUM> has scanned each lighting device.

The remote control device <NUM> may transmit a status query message that requests a response from lighting devices in a particular state. For example, as shown in <FIG>, the remote control device <NUM> may transmit the status query message <NUM> that requests a response from lighting devices in the off state. The status query message <NUM> 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 <NUM>). The status query message <NUM> may be a multicast message (e.g., as shown in <FIG>) or individual unicast messages by the lighting devices 204a, 204b with which the remote control device <NUM> may be associated.

As the lighting device 204a is in the off state, the lighting device 204a may respond with the status response message <NUM> that indicates that the lighting device 204a is in the off state. The status response message <NUM> may indicate that the lighting device 204a is in the off state, or the transmission of the status response message <NUM> itself may indicate that the lighting device 204a is in the off state. As the lighting device 204b is in the on state, the lighting device 204b may be unresponsive to the status query message <NUM>.

The remote control device <NUM> may receive a response to the status query message <NUM> from the lighting device 204a and determine that at least one lighting device is in the off state. If the remote control device <NUM> determines that any of the lighting devices 204a, 204b are in the off state, the remote control device <NUM> may be configured to transmit a default toggle message, such as the on command <NUM>. The on command <NUM> may be sent as a multicast message or individual unicast messages that are received by the lighting devices 204a, 204b.

<FIG> 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 <NUM>) and generating lighting control commands in response to the identified status. As shown in <FIG>, the remote control device <NUM> may transmit a status query message <NUM> for identifying the intensity level of lighting devices, such as lighting devices 204a, 204b, 204c. The status query message <NUM> 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 <NUM>). The status query message <NUM> may be sent as a multicast message (e.g., as shown in <FIG>) or individual unicast messages that are received by the lighting devices 204a, 204b, 204c.

The remote control device <NUM> may determine the control instructions for being sent to the lighting devices 204a, 204b, 204c based on the status of one of the lighting devices 204a, 204b, 204c. For example, the remote control device <NUM> may determine the control instructions for being sent to the lighting devices 204a, 204b, 240c based on the status (e.g., a lighting level) of a first lighting device to respond to the status query message <NUM> (e.g., lighting device 204a as shown in <FIG>). The remote control device <NUM> may control the lighting levels of all of the lighting devices 204a, 204b, 204c by sending a command to go to a new lighting level that may be determined based on the lighting level of the first lighting device to respond to the status query message <NUM>. For example, the lighting device 204a may transmit a status response message <NUM> that may indicate that the lighting device 204a is at a lighting level of <NUM>%.

The remote control device <NUM> use the lighting level of the first lighting device 204a, 204b, 204c to respond to the status query message <NUM> to control the lighting devices 204a, 204b, 204c. In response to receiving the status response message <NUM> indicating that the lighting device 204a is at the lighting level of <NUM>%, the remote control device <NUM> may transmit a command message <NUM> including a move-to-level command (e.g., a go-to command) to go to a new lighting level LNEW of <NUM>% to the lighting device 204a. The remote control device <NUM> may then transmit a command message <NUM> to the lighting device 204b and a command message <NUM> to the lighting device 204c, where each of the command messages <NUM>, <NUM> including the same move-to-level command as included in the command message <NUM> (e.g., to go to the new lighting level LNEW of <NUM>%). The command messages <NUM>, <NUM>, <NUM> may be transmitted as unicast messages (e.g., as shown in <FIG>) or a multicast message. The remote control device <NUM> may be configured to determine a desired amount of change in the lighting level of the lighting devices 204a, 204b, 204c in response to an amount of rotation of the rotation portion (e.g., a change in an angular position of the rotation portion) since the rotation of the rotation portion first began until the command message <NUM> is transmitted, and to determine the new lighting level LNEW to which to control the lighting devices 204a, 204b, 204c in response to the desired amount of change in the lighting level.

The remote control device <NUM> may continue to transmit command messages to the lighting devices 204a, 204b, 204c as the rotation portion is rotated. For example, the remote control device <NUM> may transmit commands messages <NUM>, <NUM>, <NUM> to the respective lighting devices 204a, 204b, 204c, where the command messages all include a move-to-level command to go to a new lighting level LNEW of <NUM>%. The command messages <NUM>, <NUM>, <NUM> may be transmitted as unicast messages (e.g., as shown in <FIG>) or a multicast message. The remote control device <NUM> may be configured to determine the new lighting level LNEW to which to control the lighting devices 204a, 204b, 204c in response to an amount of rotation of the rotation portion since the command message <NUM> was transmitted until the command message <NUM> is transmitted. For example, the remote control device <NUM> may be configured to transmit the commands messages <NUM>, <NUM>, <NUM> at a transmission interval TTX (e.g., at a transmission frequency fTX) while the rotation portion of the remote control device is being rotated. For example, the transmission interval TTX may be a time of approximately <NUM> milliseconds.

The remote control device <NUM> may then transmit commands messages <NUM>, <NUM>, <NUM> to the respective lighting devices 204a, 204b, 204c, where the command messages all include a move-to-level command to go to a new lighting level LNEW of <NUM>%. The command messages <NUM>, <NUM>, <NUM> may be transmitted as unicast messages (e.g., as shown in <FIG>) or a multicast message. The remote control device <NUM> may be configured to determine the new lighting level LNEW to which to control the lighting devices 204a, 204b, 204c in response to an amount of rotation of the rotation portion since the command message <NUM> was transmitted until the command message <NUM> is transmitted.

When there are a large number of lighting devices in a load control system that receive command messages (e.g., via unicast messages) including, for example, move-to-level commands, there may be some latency between when a first lighting device receives a move-to-level command and adjusts to a particular lighting level, and when a final lighting devices receives the move-to-level command (e.g., the same move-to-level command) and adjusts to the same lighting level. This delay in adjustment may result in differences in the lighting levels of the first lighting device and the final lighting device that may not be noticeable to the human eye. However, if a user actuates the rotation portion is a continued and/or excessive manner, for example, by quickly rotating the rotation portion clockwise and counter-clockwise, the lighting devices may be controlled to different levels at different times, which may produce an undesirable visual effect for the user (e.g., differences in lighting levels that may be noticeable to the human eye).

The remote control device <NUM> may be configured to detect a continued and/or excessive user interaction and reduce the number of command messages that are being transmitted to prevent the lighting devices 204a, 204b, 204c from producing undesirable visual effects. For example, a user interaction with a rotation portion of a remote control device (e.g., the remote control device <NUM>) may be considered a continued user interaction when a rotation of the rotation portion lasts for predetermined period (e.g., ten seconds with less than three-second breaks in the movements). In addition, a user interaction with the rotation portion may be considered an excessive user interaction when a rotation of the rotation portion exceeds, for example, one full rotation per second. An example of a continued and excessive user interaction with the rotation portion may, for example, include when a user actuates the rotation portion by quickly rotating the rotation portion (e.g., rotating the rotation portion at an angular velocity that is greater than a predetermined threshold) clockwise and/or counter-clockwise for a predetermined period of time (e.g., ten seconds). A user interaction that may be continued, but not excessive, may be a slower rotation of the rotation portion (e.g., rotating the rotation portion at an angular velocity that is less than or equal to the predetermined threshold) over predetermined period of time (e.g., ten seconds) to increase the intensities of the lighting devices 204a, 204b, 204c from <NUM>% to <NUM>%. A user interaction that may be excessive, but not continued, may be a quick rotation of the rotation portion over one second to increase the intensities of the lighting devices 204a, 204b, 204c from <NUM>% to <NUM>%.

To detect a continued and/or excessive user interaction of the rotation portion, the remote control device <NUM> may start a usage timer when a rotation of the rotation portion first begins and decrease the transmission frequency fTX when the usage timer exceeds a usage threshold (e.g., approximately <NUM> seconds). In addition, the remote control device <NUM> may provide a visible indication by illuminating a visual indicator (e.g., blinking the visual indicator) when the usage timer exceeds the usage threshold to indicate to the user that the remote control device <NUM> has entered a reduced transmission state. The remote control device <NUM> may also monitor usage (e.g., angular velocity of rotation) of the rotation portion when the usage timer exceeds the usage threshold to determine if the transmission frequency fTX should be decreased. For example, the remote control device <NUM> may measure an angular velocity of the rotation portion (e.g., angular distance of rotation over time) when the usage timer exceeds the usage threshold, and determine to decrease the transmission frequency fTX if the angular velocity exceeds an angular velocity threshold. In addition, the remote control device <NUM> may measure the angular position of the rotation portion when the usage timer exceeds the usage threshold, and determine to decrease the transmission frequency fTX if a change in the angular position of the rotation portion exceeds an angular position change threshold. Further, the remote control device <NUM> may measure the desired amount of change when the usage timer exceeds the usage threshold, and determine to decrease the transmission frequency fTX if the desired amount of change in the lighting level exceeds a lighting level change threshold.

The remote control device <NUM> may be configured to decrease the transmission frequency fTX by increasing the transmission interval TTX from an initial value TINIT (e.g., approximately <NUM> milliseconds) to an adjusted value TADJ (e.g., an increased transmission interval). The adjusted value TADJ may be, for example, three to four times the initial value TINIT (e.g., approximately <NUM> to <NUM> milliseconds). Also, or alternatively, the remote control device <NUM> may be configured to decrease the transmission frequency fTX to zero Hertz (e.g., such that the remote control device stops transmitting command messages). If the remote control device <NUM> stops transmitting command messages, the remote control device may transmit a final command message in response to the processor detecting that the rotation (e.g., the continued user interaction) of the rotation portion of the user interface has stopped. The final command message may include a command for adjusting the lighting level based on a final position of the rotation portion.

The remote control device <NUM> may be configured to decrease the transmission interval TTX from the adjusted value TADJ back to the initial value TINIT (e.g., to return to a normal transmission state) when the rotation (e.g., the continued user interaction) of the rotation portion has stopped. For example, the remote control device <NUM> may be configured to decrease the transmission interval TTX back to the initial value TINIT after a timeout period from when the processor detects that the rotation of the rotation portion has stopped. The remote control device <NUM> may be configured to stop (e.g., pause) the usage timer when the rotation of the rotation portion has stopped and clear the usage timer after a timeout period from when the rotation stopped. An example of a remote control device that uses a usage timer to determine how long a rotation portion has been rotated is described in commonly-assigned in <CIT>, entitled BATTERY-POWERED CONTROL DEVICE.

<FIG> is a flowchart depicting an example method <NUM> for controlling (e.g., adjusting the lighting level of) at least one lighting device in a load control system. The method <NUM> may be performed at one or more devices in the load control system. For example, the method <NUM>, or portions thereof, may be performed at a remote control device (e.g., the remote control device <NUM>, <NUM>), another controller device (e.g., the remote control device <NUM>, the occupancy sensor <NUM>, the daylight sensor <NUM>, and/or the network device <NUM>), a system controller (e.g., the system controller <NUM>), a master device, a system controller, and/or another computing device. The method <NUM> may be performed: after awakening from a sleep state; after identifying a user interaction 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). For example, the method <NUM> may be executed at <NUM> by a remote control device in response to a rotation of a rotation portion (e.g., when the rotation portion <NUM> of the remote control device <NUM> is first rotated), which may cause the remote control device to wake up. The method <NUM> may be used by the remote control device to determine an initial state (e.g., an initial lighting level) for a lighting device (e.g., lighting devices 204a, 204b). The method <NUM> may be executed once when the remote control device wakes up in response to the rotation of the rotation portion.

At <NUM>, an initial position of the rotation portion may be stored. At <NUM>, a usage timer may be started. For example, the usage timer may be initialized to zero seconds and started, counting upwards over time. At <NUM>, a status query message requesting the present lighting level of the lighting device may be transmitted. At <NUM>, a determination may be made as to whether a response (e.g., a status response message) to the status query message has been received. If the response to the status query message fails to be received at <NUM>, a determination may be made as to whether a variable NTX-QUERY is equal to a maximum query value NQ-MAX at <NUM>. The variable NTX-QUERY may indicate the number of query messages that have been transmitted and the maximum query value NQ-MAX may indicate the maximum number of query messages that may be transmitted. If the variable NTX-QUERY is not equal to the maximum query value NQ-MAX at <NUM>, the variable NTX-QUERY may be incremented at <NUM> and another status query message for querying for the present lighting level of the lighting device may be transmitted at <NUM>. If, at <NUM>, the variable NTX-QUERY is equal to the maximum query value NQ-MAX(e.g., the number of status queries transmitted is equal to the maximum number of queries that may be transmitted), an error flag may be set at <NUM> to indicate an error condition. At <NUM>, the variable NTX-QUERY may be set (e.g., reset) to zero and, at <NUM>, the device performing the method <NUM> may enter a sleep state, before the method <NUM> exits. In addition, the device may stop and/or clear the usage timer when entering the sleep state at <NUM>.

If the response to the query message has been received at <NUM>, the received lighting level may be stored as an initial lighting level LINIT at <NUM>. At <NUM>, the variable NTX-QUERY may be set to zero. At <NUM>, a rotation event may be started. For example, a rotation event may start when rotation of the rotation portion begins (e.g., when the remote control device wakes-up) and the rotation event may end when the rotation portion has not been rotated for a predefined period of time. During the rotation event, the remote control device may periodically transmit command messages (e.g., move-to-level command messages) to the lighting device (e.g., during method <NUM> described below with reference to <FIG>). At <NUM>, the transmission interval TTX may be set to an initial value TINIT (e.g., to prepare for execution of the method <NUM>).

<FIG> is a flowchart depicting an example method <NUM> for controlling (e.g., adjusting the lighting level of) at least one lighting device in a load control system. The method <NUM> may be performed at one or more devices in the load control system. For example, the method <NUM> , or portions thereof, may be performed at a remote control device (e.g., the remote control device <NUM>, <NUM>), another controller device (e.g., the remote control device <NUM>, the occupancy sensor <NUM>, the daylight sensor <NUM>, and/or the network device <NUM>), a system controller (e.g., the system controller <NUM>), a master device, a system controller, and/or another computing device. The method <NUM> may be performed: after awakening from a sleep state; after identifying a user 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). For example, the method <NUM> may be executed periodically at <NUM> by a remote control device during a rotation event (e.g., which may be started at <NUM> of the method <NUM>). The method <NUM> may be used by the remote control device to transmit command messages (e.g., move-to-level command messages and repeat command messages) to control the lighting level of the lighting device during the rotation event. The method <NUM> may be executed periodically at the repeat interval TRP (e.g., half of the transmission interval TTX) until the device returns to a sleep state.

At <NUM>, a determination may be made as to whether rotation of the rotation portion (e.g., rotation of the rotation portion <NUM> of the remote control device <NUM>) has occurred. For example, when the method <NUM> is first executed after the rotation event has started, a determination may be made at <NUM> as to whether rotation of the rotation portion has occurred since an initial position (e.g., an initial angular position) of the knob is stored at <NUM> of the method <NUM> shown in <FIG>. When the method <NUM> is subsequently executed during the rotation event, a determination may be made at <NUM> as to whether rotation of the rotation portion has occurred within the last transmission interval TTX. If there has been rotation of the rotation portion at <NUM>, the amount of rotation of the rotation portion (e.g., a change in an angular potion of the rotation portion) may be determined at <NUM>. For example, when the method <NUM> is first executed after the rotation event has started, the amount of rotation of the rotation portion since the initial position of the knob (e.g., stored at <NUM> of the method <NUM>) may be determined at <NUM>. When the method <NUM> is subsequently executed during the rotation event, the amount of rotation of the rotation portion within the last transmission interval TTX (e.g., since the beginning of the last transmission interval TTX) may be determined at <NUM>. At <NUM>, a change ΔL in the lighting level due to the amount of rotation may be determined based on the amount of rotation within the last transmission interval TTX.

A lighting level LNEW (e.g., to which to control the lighting device) for a next move-to-level command message may be determined based on the determined change ΔL in the lighting level. For example, if a first move-to-level command message to be transmitted as part of the rotation event at <NUM>, the lighting level LNEW may be set equal to an initial intensity LINIT (e.g., as determined at <NUM> of the method <NUM>) plus the determined change ΔL in the lighting level at <NUM>. If the move-to-level command is not the first move-to-level command message to be transmitted as part of the rotation event at <NUM>, the lighting level LNEW may be set equal to the previous lighting level LNEW (e.g., the lighting level LNEW transmitted as part of the previous move-to-level command) plus the determined change ΔL in the lighting level at <NUM>. At <NUM>, a move-to-level command message may be transmitted. For example, the move-to-level command message may include the lighting level LNEW and a fade period TFD. As described herein, the fade period TFD may be the amount of time over which to transition to the new lighting level LNEW. The fade period TFD may be a period of time that is longer that the transmission interval TTX. The fade period TFD may be the same each time that the move-to-level command is transmitted.

If there has not been rotation of the rotation portion at <NUM> (e.g., within the last transmission interval TTX), the usage timer may be stopped (e.g., paused) at <NUM>. At <NUM>, a determination may be made as to whether a timeout period since the rotation stopped has expired (e.g., approximately a one to three seconds). If the timeout period has not expired at <NUM>, the method <NUM> may exit. If the timeout period has expired at <NUM>, the usage timer may be cleared (e.g., set to zero seconds) at <NUM>. At <NUM>, the transmission interval TTX may return (e.g., decreased) to the initial value TINIT. The rotation event may end at <NUM> and the device may enter a sleep state at <NUM>, before the method <NUM> exits.

<FIG> is a flowchart depicting an example method <NUM> for detecting an excessive user interaction of a user interface of a remote control device (e.g., the remote control device <NUM>, <NUM>) for controlling at least one lighting device in a load control system. The method <NUM> may be performed at one or more devices in the load control system. For example, the method <NUM> , or portions thereof, may be performed at the remote control device, another controller device (e.g., the remote control device <NUM>, the occupancy sensor <NUM>, the daylight sensor <NUM>, and/or the network device <NUM>), a system controller (e.g., the system controller <NUM>), a master device, a system controller, and/or another computing device. The method <NUM> may be performed: after awakening from a sleep state; after identifying a user 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). For example, the method <NUM> may be executed periodically at <NUM> by the remote control device during a rotation event (e.g., which may be started at <NUM> of the method <NUM>). The method <NUM> may be performed by the remote control device to detect an excessive user interaction of the user interface of the remote control device.

At <NUM>, a determination may be made as to whether the value of the usage timer (e.g., that was started at <NUM> of the method <NUM>) has exceed a usage threshold (e.g., approximately ten seconds). If the value of the usage timer has not exceeded the usage threshold at <NUM>, the method <NUM> may exit. If the value of the usage timer has exceeded the usage threshold at <NUM>, a determination made be made as to whether excessive rotation (e.g., an excessive user interaction) has been detected at <NUM>. For example, excessive rotation may be detected at <NUM> by measuring the angular velocity of the rotation portion and determining if the angular velocity exceeds an angular velocity threshold. Excessive rotation may also or alternatively be detected at <NUM> by determining if a change in the angular position of the rotation portion exceeds an angular position change threshold. Further, excessive rotation may be detected at <NUM> by determining if the desired amount of change in the lighting level (e.g., as determined at <NUM> of the method <NUM>) exceeds a lighting level change threshold. If an excessive rotation is not detected at <NUM>, the method <NUM> may exit.

If an excessive rotation is detected at <NUM>, the transmission frequency fTX may be decreased (e.g., by increasing the transmission interval TTX) at <NUM>. For example, the transmission frequency fTX may be decreased at <NUM> by increasing the transmission interval TTX from the initial value TINIT (e.g., approximately <NUM> milliseconds) to an adjusted value TADJ (e.g., an increased transmission interval), which may be, for example, three to four times the initial value TINIT (e.g., approximately <NUM> to <NUM> milliseconds). Also or alternatively, the transmission frequency fTX may be decreased to zero Hertz at <NUM>, such that the remote control device stops transmitting command messages (e.g., stops executing the method <NUM> shown in <FIG>). While not shown in <FIG>, if the transmission frequency fTX is decreased to zero Hertz, the remote control device may transmit a final command message in response to detecting that the rotation of the rotation portion of the user interface has stopped for a timeout period (e.g., rotation is not detected at <NUM> and the timeout period has expired at <NUM> of the method <NUM>). The final command message may include a command for adjusting the lighting level of the lighting device based on a final position of the rotation portion. At <NUM>, visible feedback may be provided to a user, before the method <NUM> exits. For example, the remote control device may illuminate a visual indicator (e.g., by blinking the visual indicator) at <NUM> to indicate to the user that the value of the transmission interval TTX has been set (e.g., increased) to the adjusted value TADJ.

<FIG> is a block diagram illustrating an example load control device, e.g., a load control device <NUM>, as described herein. The load control device <NUM> 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 <NUM> may include a communications circuit <NUM>. The communications circuit <NUM> may include a receiver, an RF transceiver, or other communications module capable of performing wired and/or wireless communications via communications link <NUM>. The communications circuit <NUM> may be in communication with a control circuit <NUM>. The control circuit <NUM> 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 <NUM> may perform signal coding, data processing, power control, input/output processing, or any other functionality that enables the load control device <NUM> to perform as described herein.

The control circuit <NUM> may store information in and/or retrieve information from the memory <NUM>. For example, the memory <NUM> may maintain a registry of associated control devices and/or control configuration instructions. The memory <NUM> may include a non-removable memory and/or a removable memory. The load control circuit <NUM> may receive instructions from the control circuit <NUM> and may control the electrical load <NUM> based on the received instructions. The load control circuit <NUM> may send status feedback to the control circuit <NUM> regarding the status of the electrical load <NUM>. The load control circuit <NUM> may receive power via the hot connection <NUM> and the neutral connection <NUM> and may provide an amount of power to the electrical load <NUM>. The electrical load <NUM> may include any type of electrical load.

The control circuit <NUM> may be in communication with an actuator <NUM> (e.g., one or more buttons) that may be actuated by a user to communicate user selections to the control circuit <NUM>. For example, the actuator <NUM> may be actuated to put the control circuit <NUM> in an association mode and/or communicate association messages from the load control device <NUM>.

<FIG> is a block diagram illustrating an example controller device <NUM> as described herein. The controller device <NUM> 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 <NUM> may include a control circuit <NUM> for controlling the functionality of the controller device <NUM>. The control circuit <NUM> 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 <NUM> may perform signal coding, data processing, power control, input/output processing, and/or any other functionality that enables the controller device <NUM> to perform as described herein.

The control circuit <NUM> may store information in and/or retrieve information from the memory <NUM>. The memory <NUM> may include a non-removable memory and/or a removable memory, as described herein.

The controller device <NUM> may include one or more light sources, such as one or more LEDs <NUM>, for providing feedback to a user. The one or more LEDs <NUM> may be included in a status indicator and may be controlled by the control circuit <NUM>. The control circuit <NUM> may control the LEDs <NUM> as described herein to provide feedback to the user.

The controller device <NUM> may include a communications circuit <NUM> for transmitting and/or receiving information. The communications circuit <NUM> may transmit and/or receive information via wired and/or wireless communications. The communications circuit <NUM> may include a transmitter, an RF transceiver, or other circuit capable of performing wired and/or wireless communications. The communications circuit <NUM> may be in communication with control circuit <NUM> for transmitting and/or receiving information.

The control circuit <NUM> may also be in communication with an input circuit <NUM>. The input circuit <NUM> 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 <NUM> may also comprise a proximity sensing circuit for sensing an occupant in the vicinity of the controller device <NUM>. For example, the controller device <NUM> may receive input from the input circuit <NUM> to put the control circuit <NUM> in an association mode and/or communicate association messages from the controller device <NUM>. The control circuit <NUM> may receive information from the input circuit <NUM> (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 <NUM> may comprise an actuator (e.g., a mechanical tactile switch) configured be actuated as an on/off event (e.g., in response to an actuation of the actuation portion <NUM>). The input circuit <NUM> may also comprise a rotational position sensing circuit (e.g., a magnetic sensing circuit, such as a Hall effect sensing circuit) for sensing rotations (e.g., the angular position and/or direction of rotation) of a rotation portion (e.g., the rotation portion <NUM>). Each of the modules within the controller device <NUM> may be powered by a power source <NUM>.

<FIG> is a block diagram illustrating an example network device <NUM> as described herein. The network device <NUM> may include the network device <NUM>, for example. The network device <NUM> may include a control circuit <NUM> for controlling the functionality of the network device <NUM>. The control circuit <NUM> 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 <NUM> may perform signal coding, data processing, power control, input/output processing, or any other functionality that enables the network device <NUM> to perform as described herein. The control circuit <NUM> may store information in and/or retrieve information from the memory <NUM>. The memory <NUM> 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.

The network device <NUM> may include a communications circuit <NUM> for transmitting and/or receiving information. The communications circuit <NUM> may perform wireless and/or wired communications. The communications circuit <NUM> may include an RF transceiver or other circuit capable of performing wireless communications via an antenna. Communications circuit <NUM> may be in communication with control circuit <NUM> for transmitting and/or receiving information.

The control circuit <NUM> may also be in communication with a display <NUM> for providing information to a user. The control circuit <NUM> and/or the display <NUM> may generate GUIs for being displayed on the network device <NUM>. The display <NUM> and the control circuit <NUM> may be in two-way communication, as the display <NUM> may include a touch screen module capable of receiving information from a user and providing such information to the control circuit <NUM>. The network device may also include an actuator <NUM> (e.g., one or more buttons) that may be actuated by a user to communicate user selections to the control circuit <NUM>.

Each of the modules within the network device <NUM> may be powered by a power source <NUM>. The power source <NUM> may include an AC power supply or DC power supply, for example. The power source <NUM> may generate a supply voltage Vcc for powering the modules within the network device <NUM>.

<FIG> is a block diagram illustrating an example system controller <NUM> (e.g., a hub device) as described herein. The system controller <NUM> may include a control circuit <NUM> for controlling the functionality of the system controller <NUM>. The control circuit <NUM> 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 <NUM> may perform signal coding, data processing, power control, input/output processing, or any other functionality that enables the system controller <NUM> to perform as described herein. The control circuit <NUM> may store information in and/or retrieve information from the memory <NUM>. The memory <NUM> 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.

The system controller <NUM> may include a communications circuit <NUM> for transmitting and/or receiving information. The communications circuit <NUM> may perform wireless and/or wired communications. The system controller <NUM> may also, or alternatively, include a communications circuit <NUM> for transmitting and/or receiving information. The communications circuit <NUM> may perform wireless and/or wired communications. Communications circuits <NUM> and <NUM> may be in communication with control circuit <NUM>. The communications circuits <NUM> and <NUM> may include RF transceivers or other communications modules capable of performing wireless communications via an antenna. The communications circuit <NUM> and communications circuit <NUM> may be capable of performing communications via the same communication channels or different communication channels. For example, the communications circuit <NUM> may be capable of communicating (e.g., with a network device, over a network, etc.) via a wireless communication channel and the communications circuit <NUM> may be capable of communicating (e.g., with control devices and/or other devices in the load control system) via another wireless communication channel.

The control circuit <NUM> may be in communication with an LED indicator <NUM> for providing indications to a user. The control circuit <NUM> may be in communication with an actuator <NUM> (e.g., one or more buttons) that may be actuated by a user to communicate user selections to the control circuit <NUM>. For example, the actuator <NUM> may be actuated to put the control circuit <NUM> in an association mode and/or communicate association messages from the system controller <NUM>.

Each of the modules within the system controller <NUM> may be powered by a power source <NUM>. The power source <NUM> may include an AC power supply or DC power supply, for example. The power source <NUM> may generate a supply voltage Vcc for powering the modules within the system controller <NUM>.

Claim 1:
A remote control device, comprising:
a user interface that comprises a rotation portion; and
a processor, configured to:
receive an indication of a rotation of the rotation portion via the user interface;
start a usage timer in response to receiving the indication of the rotation of the rotation portion;
periodically transmit command messages at a transmission frequency while the rotation portion is being rotated, each of the command messages comprising a respective command for adjusting to a respective lighting level, wherein each of the command messages are periodically transmitted at a transmission interval that is dependent on the transmission frequency, and wherein the transmission interval is a period of time between when each of the command messages are periodically transmitted;
detect an excessive rotation of the rotation potion, when an angular velocity of the rotation portion exceeds an angular velocity threshold and the usage timer exceeds a usage threshold, or when a change in an angular position of the rotation portion exceeds an angular position change threshold and the usage timer exceeds the usage threshold ; and
decrease the transmission frequency of the periodically transmitted command messages in response to the detected excessive rotation of the rotation portion.