DISCOVERY PROCEDURE FOR A REMOTE FAN-SPEED CONTROL DEVICE IN A WIRELESS LOAD CONTROL SYSTEM

Description

CROSS-REFERENCE TO RELATED APPLICATIONS

This application claims priority to U.S. Provisional Patent Application No. 63/659,602, filed Jun. 13, 2024, which is incorporated by reference herein in its entirety.

BACKGROUND

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 the user environment. A motorized window treatment control system may be used to control the natural light provided to the user environment. A heating, ventilation, and air-conditioning (HVAC) system may be used to control the temperature in the user environment. Each load control system may include various control devices, including input devices and load control devices. The load control devices may receive messages, which may include control data, for controlling an electrical load from one or more of the input devices. The load control devices may be capable of directly controlling an electrical load. The input devices may be capable of indirectly controlling the electrical load via the load control device. Examples of load control devices may include lighting control devices (e.g., a dimmer switch, an electronic switch, a ballast, or a light-emitting diode (LED) driver), a motor control device (e.g., for a ceiling fan or exhaust fan), a motorized window treatment, a temperature control device (e.g., a thermostat), an AC plug-in load control device, and/or the like. Examples of input devices may include remote-control devices, occupancy sensors, daylight sensors, temperature sensors, and/or the like.

SUMMARY

Systems, methods, and apparatus are described herein for configuring (e.g., activating) a fan-speed control device in a wireless control system using a network device. The fan-speed control device may be configured to control a rotational speed of a ceiling fan. The power to the fan-speed control device may be cycled, or the fan-speed control device may receive another indication (e.g., via a message or actuation of a button), and the fan-speed control device may enter a discovery mode. The fan-speed control device may control the rotational speed of the ceiling fan to turn off the ceiling fan in response to entering the discovery mode. The fan-speed control device may transmit a discovery request message in the discovery mode for being discovered by a network device.

The network device may display an indicator representing the discovered fan-speed control devices on a visible display in response to receiving the discovery request messages from the fan-speed control devices. The network device may receive a selection of the indicator representing one of the discovered fan-speed control devices. The network device may transmit a message including an identify command to the fan speed control device for identifying the fan-speed control device for activation.

The fan-speed control device may control the rotational speed of the ceiling fan to turn the ceiling fan on at an identification speed in response to receiving the identify command at the fan-speed control device. The user may identify the fan-speed control device corresponding to the ceiling fan being identified in the space. The network device may receive an input from the user to activate the fan-speed control device to which the identify command was transmitted. The network device may store a device identifier of the fan-speed control device in response to receiving the input to activate the fan-speed control device.

The network device may transmit an activation message to the selected control device and/or one or more other devices in the load control system for activating the selected control device in the load control system. The activation message may include activation data that may establish and/or activate the selected control device in the load control system, such that the selected control device may be configured to communicate with other control devices of the load control system. In some examples, the activation data may include one or more portions of the system configuration data and may be transmitted to the selected control device along with the activation, such as a device name, a device type, a device location, a system configuration identifier (e.g., a configuration address for communicating with other control devices), and/or other network credentials for communicating on a wireless network. In addition, the one or more other portions of the system configuration data (e.g., programming data and/or association data) may be transmitted to the selected control device along with the activation data as a result of activating the selected control device in the load control system, such as associated control devices, one or more operational settings, and/or programming data.

After receiving the selection of the indicator representing the fan-speed control device and prior to transmitting the message including the identify command, the network device may receive a warning notifying the user to ensure that there are no obstructions preventing the ceiling fan controlled by the fan speed control device from rotating. The network device may receive an input indicating a confirmation that there are no obstructions preventing the ceiling fan controlled by the fan speed control device from rotating prior to sending the message including the identify command to the fan-speed control device.

The fan-speed control device may store a first rotational speed at which the ceiling fan is controlled. After the fan-speed control device enters a discovery mode, is discovered, and receives the identify command, the fan-speed control device may control the ceiling fan at a second rotational speed to turn the ceiling fan on at the identification speed in response to receiving the identify command. After the fan-speed control device is activated, the fan-speed control device may return to controlling the ceiling fan at the first rotational speed.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a diagram of an example load control system for controlling the operation of one or more electrical devices, such as ceiling fans.

FIGS. 2A-2C illustrate an example screen (e.g., a graphical user interface window) that may be used to activate a remotely-located fan-speed control device in a wireless control system.

FIG. 3 is a simplified block diagram of an example fan-speed control device.

FIG. 4 is a simplified block diagram of an example processing device.

FIG. 5 is a flowchart of an example procedure that may be executed by a processing device of a wireless control system to activate a remotely-located fan-speed control device.

FIG. 6 is a flowchart of an example procedure that may be executed by a fan speed control device to activate the fan-speed control device in a wireless control system.

DETAILED DESCRIPTION

FIG. 1 is a diagram of an example load control system 100 for controlling the operation of one or more electrical devices (e.g., electrical loads), such as first and second ceiling fans 110a, 110b. The first and second ceiling fans 110a, 110b may each receive power from a power source, such as an alternating-current (AC) power source or a direct-current (DC) power source. The first and second ceiling fans 110a, 110b may be installed on the ceiling of a room 101 or another space in a building. Each of the first and second ceiling fans 110a, 110b may comprise a respective motor load, such as first and second motors 112a, 112b (e.g., fan motors), for rotating a plurality of respective blades 114a, 114b to circulate the air in the room 101. For example, each of the first and second ceiling fans 110a, 110b may comprise three blades 114a, 114b as shown in FIG. 1. Each of the first and second ceiling fans 110a, 110b may also comprise a housing 116a, 116b for housing the motor 112a, 112b, respectively, and a base portion 118a, 118b for mounting the ceiling fan 110a, 110b, respectively, to the ceiling of the room 101.

The first and second ceiling fans 110a, 110b may be coupled to the power source via a circuit breaker 102 (e.g., a switching circuit and/or mechanical switch), which may be located in a breaker panel 104, such that the first and second ceiling fans 110a, 110b are coupled to a circuit 105 (e.g., the same circuit). The first and second ceiling fans 110a, 110b may be electrically connected to and capable of receiving power from the power source when the circuit breaker 102 is closed (e.g., conductive). The first and second ceiling fans 110a, 110b may be electrically disconnected from the power source and unpowered when the circuit breaker 102 is open (e.g., non-conductive). While FIG. 1 shows only the circuit 105, the load control system 100 may comprise other circuits to which other ceiling fans may be coupled and which may be controlled by other circuit breakers in the breaker panel 104 and/or another breaker panel.

The load control system 100 may also, or alternatively, comprise one or more control devices configured to control the one or more electrical devices (e.g., electrical loads), such as the first and second ceiling fans 110a, 110b. The control devices may include input devices and/or load control devices, such as a first fan-speed control device 120a for controlling the motor 112a of the first ceiling fan 110a and a second fan-speed control device 120b for controlling the motor 112b of the second ceiling fan 110b. The first and second fan-speed control devices 120a, 120b may each be electrically coupled in series between the power source and the first and second ceiling fans 110a, 110b, respectively. The first and second fan-speed control devices 120a, 120b may each be mounted remotely, for example, to a respective junction box above a ceiling and/or behind a wall of the room 101. The first and second fan-speed control devices 120a, 120b may each comprise a respective internal motor control circuit configured to control the first and second ceiling fans 110a, 110b by controlling a respective load current I_LOAD1, I_LOAD2 conducted through the motors 112a, 112b of the first and second ceiling fans 110a, 110b, respectively. The first and second fan-speed control devices 120a, 120b may be configured to control the first and second ceiling fans 110a, 110b to turn the first and second ceiling fans 110a, 110b on and off and/or to adjust a respective rotational speed S_FAN1, S_FAN2 of the first and second ceiling fans 110a, 110b, respectively. Each of the first and second fan-speed control devices 120a, 120b may be configured to control the respective rotational speed S_FAN1, S_FAN2 of the first and second ceiling fans 110a, 110b, respectively, to a number of discrete speeds (e.g., available speeds). For example, the respective rotational speed S_FAN1, S_FAN2 of the first and second ceiling fans 110a, 110b may be controlled to one of seven discrete speeds at a time. In addition, the first and second load control devices 120a, 120b may each be configured to adjust a respective direction of rotation of the first and second ceiling fans 110a, 110b, respectively.

The first and second fan-speed control devices 120a, 120b may be configured to communicate (e.g., transmit and/or receive) messages (e.g., digital message) via wired signals and/or wireless signals, such as radio-frequency (RF) signals 106. For example, the first and second fan-speed control devices 120a, 120b may be configured to control the first and second ceiling fans 110a, 110b, respectively, in response to control data (e.g., commands) received in the messages via the RF signals 106. The load control system 100 may include a wireless control system comprising control devices capable of communicating via wireless control signals, such as such as radio-frequency (RF) signals 106. The first and second fan-speed control devices 120a, 120b may each comprise one or more wireless communication circuits for transmitting and/or receiving messages via the RF signals 106. A first wireless communication circuit of each of the first and second fan-speed control devices 120a, 120b may be capable of communicating on a first wireless communication link (e.g., a wireless network communication link) and/or communicating using a first wireless protocol (e.g., a wireless network communication protocol, such as the CLEAR CONNECT protocol (e.g., the CLEAR CONNECT A and/or the CLEAR CONNECT X protocols) and/or the THREAD protocol) via the RF signals 106. A second wireless communication circuit of each of the first and second fan-speed control devices 120a, 120b may be capable of communicating on a second wireless communication link (e.g., a short-range wireless communication link) and/or communicating using a second wireless protocol (e.g., a short-range wireless communication protocol, such as the BLUETOOTH and/or BLUETOOTH LOW ENERGY (BLE) protocols) via the RF signals 106.

The load control system 100 may comprise other load control devices installed for controlling other types of electrical loads. For example, the load control devices may include lighting control devices configured to control one or more respective lighting loads; daylight control devices, such as motorized window treatments configured to control an electrical motor to move a position of a window treatment or covering material; plug-in load control devices for controlling a plug-in electrical load that is plugged into an outlet; temperature control devices, such as a thermostat, that may be coupled to a heating, ventilation, and air conditioning (HVAC) system via a control link for controlling a temperature in the room 101; audio/visual control devices or appliances; a screw-in luminaire including a dimmer circuit and an incandescent or halogen lamp; a screw-in luminaire including a ballast and a compact fluorescent lamp; a screw-in luminaire including an LED driver and an LED light source; an electronic switch, controllable circuit breaker, or other switching device for turning an appliance on and off; a motor control unit for controlling a motor load, such as a ceiling fan or an exhaust fan; a drive unit for controlling a motorized window treatment or a projection screen; motorized interior or exterior shutters; an air conditioner; a compressor; an electric baseboard heater controller; a controllable damper; a variable air volume controller; a fresh air intake controller; a ventilation controller; hydraulic valves for use radiators and radiant heating system; a humidity control unit; a humidifier; a dehumidifier; a water heater; a boiler controller; a pool pump; a refrigerator; a freezer; a television or computer monitor; a video camera; an amplifier; an elevator; a power supply; a generator; an electric charger, such as an electric vehicle charger; an alternative energy controller; and/or another type of load control device.

The load control system 100 may comprise one or more input devices configured to communicate with one or more load control devices via RF signals 106. For example, the load control system 100 may include a remote control device 140 for transmitting messages including control data (e.g., commands) for controlling one or more electrical loads via the load control devices. The messages may be transmitted from the remote control device 140 in response to an input event, such as a button press. The remote control device 140 (e.g., a remote fan-speed control device) may transmit messages (e.g., digital message) including control data (e.g., commands) for controlling the first and second ceiling fans 110a, 110b via the RF signals 106. For example, the remote control device 140 may be battery-powered, and may be handheld, mounted to a wall, and/or mounted to a pedestal to be placed on a tabletop. The remote control device 140 may comprise a plurality of buttons, such as, for example, an on button 142, an off button 144, a raise-speed button 146, and/or a lower-speed button 148. For example, the remote control device 140 may be configured to transmit the messages including the control data to the first and second fan-speed control devices 120a, 120b for causing the first and second fan-speed control devices 120a, 120b to control the first and second ceiling fans 110a, 110b, respectively, in response to actuations of one or more of the on button 142, the off button 144, the raise-speed button 146, and/or the lower-speed button 148. The first and second fan-speed control devices 120a, 120b may be configured to turn on the first and second ceiling fans 110a, 110b, respectively, in response to actuations of the on button 142, and/or to turn off the first and second ceiling fans 110a, 110b, respectively, in response to actuations of the off button 144. The first and second fan-speed control devices 120a, 120b may be configured to increase the rotational speed of the motors 112a, 112b of the first and second ceiling fans 110a, 110b, respectively, in response to actuations of the raise-speed button 146, and/or decrease the rotational speed of the motors 112a, 112b of the first and second ceiling fans 110a, 110b, respectively, in response to actuations of the lower-speed button 148. One will recognize that the first and second fan-speed control devices 120a, 120b may also and/or alternatively be configured to receive control signals from a control device via a wired communication link.

The load control system 100 may include one or more other input devices, such as a sensor device configured to transmit messages including control data (e.g., commands) for controlling one or more electrical loads. The sensor device may be configured to transmit messages via the RF signals 106 to one or more other devices in the load control system 100 in response to an input event, such as a sensor measurement event. The sensor device may operate as an occupancy sensor configured to detect occupancy and vacancy conditions. The sensor device may operate as a visible light sensor (e.g., including a camera or other device capable of sensing visible light). The load control system 100 may comprise other types of input devices, such as, for example, temperature sensors, humidity sensors, radiometers, cloudy-day sensors, shadow sensors, pressure sensors, smoke detectors, carbon monoxide detectors, air-quality sensors, motion sensors, security sensors, proximity sensors, fixture sensors, partition sensors, multi-zone control units, slider control units, kinetic or solar-powered remote controls, key fobs, cell phones, smart phones, tablets, personal digital assistants, personal computers, laptops, timeclocks, audio-visual controls, safety devices, power monitoring devices (e.g., such as power meters, energy meters, utility submeters, utility rate meters, etc.), central control transmitters, residential controllers, commercial controllers, industrial controllers, and/or another type of input device.

The load control system 100 may also comprise one or more system processing devices, such as a system controller 150, that may be configured to transmit and/or receive messages via wired and/or wireless communications. For example, the system controller 150 may be configured to transmit and/or receive the RF signals 106, to communicate with one or more control devices of the load control system 100 (e.g., the first and second fan-speed control devices 120a, 120b and/or the remote control device 140). The system controller 140 may be coupled to one or more wired control devices of the load control system 100 via a wired digital communication link. The system controller 150 may also, or alternatively, be capable of communicating on a third wireless communication link (e.g., a network communication link) and/or communicating using a third wireless protocol (e.g., a network communication protocol, such as Internet protocol, Ethernet-based protocols, WI-FI protocols, or other suitable network protocols), via the RF signals 106. For example, the system controller 150 may be configured to transmit and/or receive messages on a network (e.g., a local area network and/or a wide area network, such as the Internet), via the RF signals 106. The system controller 150 may transmit messages to the first and second fan-speed control devices 120a, 120b in response to messages received via the network. The messages may include configuration data for configuring the first and second fan-speed control devices 120a, 120b and/or control data (e.g., commands) for controlling the first and second fan-speed control devices 120a, 120b. In some examples, the system controller 150 may be configured to transmit and receive messages between the control devices of the load control system 100. For example, the system controller 150 may transmit messages to the first and second fan-speed control devices 120a, 120b for controlling the first and second ceiling fans 110a, 110b, respectively, in response to the messages received from the remote control device 140 (e.g., via the RF signals 106).

A network device 160 may be in communication with the first and second fan-speed control devices 120a, 120b and/or the system controller 150 for configuring and/or controlling the control devices of the load control system 100. The network device 160 may comprise a wireless phone, a tablet, a laptop, a personal digital assistant (PDA), a wearable device (e.g., a watch, glasses, etc.), or other computing device. The network device 160 may be operated by a user 162. For example, the network device 160 may comprise a visible display 164 for displaying a graphical user interface (GUI) for displaying information for the user 162 and receiving inputs from the user 162. The network device 160 may be configured to communicate with the first and second fan-speed control devices 120a, 120b via the RF signals 106 (e.g., using the short-range wireless communication protocol on the short-range wireless communication link). In addition, or alternatively, the network device 160 may be configured to communicate with the system controller 150 via the RF signals 106 (e.g., using the network communication protocol on the network communication link). Further, the network device 160 may be configured to transmit and/or receive beacon signals that may be used to commission the load control system 100 via the short-range wireless communication link (e.g., using the RF signals 106).

The load control devices of the load control system 100 (e.g., the first and second fan-speed control devices 120a, 120b) may be configured to control the electrical loads (e.g., the first and second ceiling fans 110a, 110b) in response to inputs received from the input devices (e.g., the remote control device 140) and/or the system processing devices (e.g., the system controller 150) based on system configuration data (e.g., programming data and/or association data), which may be stored in a system configuration database. The system configuration database and/or portions of the system configuration database may be stored as configuration data on one or more of the devices of the loads control system 100. The system configuration data may include configuration settings (e.g., operational settings) that may be configured for operation of the control devices. A computing device, such as the network device 160 or other suitable network device, may be configured to define the system configuration data in response to inputs received from the user 162. For example, the network device 160 may be configured to execute a design configuration application (e.g., design configuration software and/or graphical user interface (GUI) software) to display the graphical user interface on the visible display 164 for displaying configuration options and/or receiving the inputs from the user 162 to generate the system configuration data.

After the control devices of the load control system 100 (e.g., the load control devices, the input devices, and/or the system processing devices) are installed, the load control system 100 may be enabled for operation during a commissioning procedure. For example, the network device 160 may be configured to coordinate the commissioning procedure in response to inputs received from the user 162. The network device 160 may be configured to define the system configuration data prior to and/or during the commissioning procedure of the load control system 100. The system configuration data may comprise a device object for each of the control devices in the load control system 100. The device objects of the system configuration data may each comprise one or more of a device name, a device type, a device location, a system configuration identifier (e.g., a configuration address), one or more operational settings, and/or programming data. The one or more operational settings may define operational characteristics for how the device operates (e.g., based on the programming data). For example, the one or more operational settings may comprise high-end and/or low-end intensity levels (e.g., for a lighting control device), raised and/or lowered limit positions (e.g., for a motorized window treatment), a sensitivity level (e.g., for an input device, such as a sensor), one or more fan speeds (e.g., for controlling the first and second ceiling fans 110a, 110b), etc. The programming data may be configured with a preset identifier (e.g., a scene identifier) for operating according to the operational settings in response to triggering of a preset (e.g., a scene). The operational settings may define how the control devices operate to control the electrical loads of the load control system 100 (e.g., thresholds or other programmed settings defining how the control devices operate). In addition, each of the device objects of the system configuration data may be configured to store a device identifier (e.g., a unique identifier of the control device of the load control system 100, such as a serial number) that allows the control device of that device object to communicate with the other control devices of the load control system 100. For example, the device identifier of each of the device objects of the system configuration data may be received and stored in the system configuration data during the commissioning procedure.

The control devices of the load control system 100 may be activated (e.g., as a step of the commissioning procedure) to establish the control devices in the load control system 100 (e.g., during an activation process), such that the control devices may be configured to communicate with each other (e.g., via the RF signals 106). During the activation process, the network device 160 may be configured to transmit a discovery initiation message (e.g., a discovery initiation beacon message) to the control devices of the load control system 100. In some examples, the network device 160 may be configured to repetitively (e.g., periodically) transmit the discovery initiation message during the activation procedure. The discovery initiation message may be transmitted as a broadcast message to control devices configured to receive the discovery initiation message, a multicast message configured to be received by a group of control devices, or a unicast message identifying a target control device for receiving the discovery initiation message. The discovery initiation message may identify one or more control devices for being triggered to a discovery mode in response to receipt of the discovery initiation message. The discovery initiation message may include a discovery initiation identifier, which may be a unique identifier (e.g., a serial number) of the network device 160 and/or the design configuration application executed by the network device 160. In response to receiving the discovery initiation message, the control devices of the load control system 100 may be configured to enter a discovery mode. In some examples, the control devices of the load control system 100 may be configured to enter the discovery mode, when a received signal magnitude (e.g., a received signal strength indicator) of the received discovery initiation message exceeds a discovery threshold. In another example, the control devices of the load control system 100 may enter the discovery mode in response to actuation of a button located thereon, in response to detecting a cycling of power to a circuit to which the control devices are electrically coupled, and/or via another triggering event for triggering the discovery mode at the control devices.

When in the discovery mode, the control devices of the load control system 100 may be configured to transmit a discovery request message (e.g., a discovery request beacon message) to the network device 160. In some examples, the control devices of the load control system 100 may be configured to repetitively (e.g., periodically) transmit the discovery request message while in the discovery mode. The discovery request message may include a device identifier, which may be a unique identifier (e.g., a serial number) of the control device that transmitted the discovery request message. The discovery request message may include a device type (e.g., fan-speed control device). The discovery request message may be transmitted as a broadcast message to control devices configured to receive the discovery request message, a multicast message configured to be received by a group of control devices, or a unicast message identifying a target control device (e.g., the network device) for receiving the discovery request message.

The network device 160 may receive discovery request messages from one or more of the control devices of the load control system 100. The network device 160 may be configured to display on the visible display 164 a device list of one or more of the control devices of the load control system 100 from which the network device 160 received the discovery request messages. The user 162 may select one of the control devices in the device list to activate. In some examples, the control devices of the load control system 100 that are listed in the device list may be configured to provide a visible indication in the space in which the control device is installed, so that the user 162 can locate the control devices in the space. For example, a lighting control device may be configured to blink a controlled lighting load and/or cause the controlled lighting load to turn a particular color. In addition, or alternatively, a motorized window treatment may be configured to cause a covering material (e.g., shade fabric) to move back and forth (e.g., up and down) over a short distance (e.g., perform a wiggle movement). A fan (e.g., the first and second ceiling fans 110a, 110b) may be configured to turn on and/or off for a predefined period of time and/or to a predefined speed. Further, a system processing device (e.g., such as the system controller 150) may be configured to blink and/or control the color of a light source (e.g., a light-emitting diode) on the system processing device that is visible to the user 162 in the space.

After the user 162 selects one of the control devices from the device list displayed on the visible display 164 of the network device 160, the network device 160 may activate the selected control device by transmitting an activation message to the selected control device and storing the device identifier of the selected control device (e.g., as received in the discovery request message) in the device object in the system configuration data. For example, the network device may transmit the device identifier of the selected control device to one or more other devices (e.g., system controller or other control devices) to activate the selected control device for enabling communication with and/or control of the selected control device by transmission of messages including the device identifier. In addition, the user 162 may provide inputs via the graphical user interface to configure operational settings and/or define programming data for the selected control device after the control device is activated. In some examples, the operational settings and/or programming data in the device object of the system configuration data for the selected control device may have been previously populated (e.g., prior to the commissioning procedure). The network device may transmit an activation message to the selected control device and/or one or more other devices in the load control system 100 for activating the selected control device in the load control system. The activation message may include activation data that may establish and/or activate the selected control device in the load control system, such that the selected control device may be configured to communicate with other control devices of the load control system 100. In some examples, the activation data may include one or more portions of the system configuration data and may be transmitted to the selected control device along with the activation, such as a device name, a device type, a device location, a system configuration identifier (e.g., a configuration address for communicating with other control devices), and/or other network credentials for communicating on a wireless network. In addition, the one or more other portions of the system configuration data (e.g., programming data and/or association data) may be transmitted to the selected control device along with the activation data as a result of activating the selected control device in the load control system, such as associated control devices, one or more operational settings, and/or programming data.

The user 162 may then continue the commissioning procedure by selecting another control device from the device list to activate (e.g., until each of the control devices of the load control system 100 is activated). In some examples, when the control device can be accessed by the user 162, the user 162 may actuate an actuator (e.g., a button) on the control device to select the control device for activation (e.g., as with the remote control device 140 that is located such that the user 162 may actuate one of the buttons of the remote control device 140 to select the remote control device 140 for activation).

Some of the control devices of the load control system 100 (e.g., such as the first and second fan-speed control devices 120a, 120b) may not be able to easily provide visible indication in the space in which the control devices are installed. For example, since the first and second fan-speed control devices 120a, 120b may be hidden from view (e.g., mounted above a ceiling, behind a wall, and/or in the respective base portions 118a, 118b), the first and second fan-speed control devices 120a, 120b may not be able to blink and/or change the color of a light source on the first and second fan-speed control devices 120a, 120b to provide the visible indication. In addition, or alternatively, the first and second ceiling fans 110a, 110b may not comprise light sources that the first and second fan-speed control devices 120a, 120b can control to provide the visible indication. Further, the first and second ceiling fans 110a, 110b may be characterized by high inertias, such that the respective rotational speeds S_FAN1, S_FAN2 may not be quickly changed to provide a visible indication in the movement of the respective blades 114a, 114b (e.g., such as a wiggle movement). As a result, the user 162 may not be able to distinguish between the first and second fan-speed control devices 120a, 120b to select, from the device list displayed on the visible display 164, one of the first and second fan-speed control devices 120a, 120b to activate. In addition, or alternatively, since the first and second fan-speed control devices 120a, 120b may be remotely-located, the user 162 may not be able to actuate an actuator (e.g., a button on the first and second fan-speed control devices 120a, 120b) to select the first and second fan-speed control devices 120a, 120b for activation.

To activate one of the first and second fan-speed control devices 120a, 120b, the network device 160 may prompt the user to cycle power to the circuit 105 to which the first and second fan-speed control devices 120a, 120b are electrically coupled. For example, the user 162 may cycle power to the circuit 105 to which the first and second fan-speed control devices 120a, 120b are electrically coupled by opening and then subsequently closing the circuit breaker 102 in the breaker panel 104. When powering up (e.g., after the power is cycled to the circuit 105), the first and second fan-speed control devices 120a, 120b may be configured to enter the discovery mode. For example, the first and second fan-speed control devices 120a, 120b may be configured to enter the discovery mode for a period of time (e.g., approximately five minutes) and then exit (e.g., automatically exit) the discovery mode. After entering the discovery mode, the first and second fan-speed control devices 120a, 120b may be configured to transmit a discovery request message to the network device 160. The network device 160 may be configured to include (e.g., only include) in the device list displayed on the visible display 164 the control device on the circuit 105 to which power was just cycled (e.g., the first and second fan-speed control devices 120a, 120b). In this manner, the length of the device list (e.g., the number of control devices listed in the device list) may be smaller than when the control devices of the load control system 100 enter the discover mode in response to receiving the discovery initiation message from the network device 160. This may allow for identifying control devices for being activated more easily (e.g., in a faster manner) than filtering through a larger number of control devices identifying themselves for potential activation by transmitting a discovery initiation message. The user 162 may be presented with the device list that does includes control devices that have cycled power or from which a discovery request message is received above a threshold signal strength to limit the number of control devices, such that the first and second fan-speed control devices 120a, 120b, that may be identified. This may allow for identifying control devices for being activated more easily (e.g., in a faster manner) than filtering through a larger number of control devices identifying themselves for potential activation. When the first and second fan-speed control devices 120a, 120b enter the discovery mode, the first and second fan-speed control devices 120a, 120b may turn off the first and second ceiling fans 110a, 110b. Each of the first and second fan-speed control devices 120a, 120b may be turned off when entering the discovery mode to assist the user in identifying one of the fan-speed control devices 120a, 120b that is controlling the respective ceiling fan 110a, 110b to rotate later in the activation process (e.g., as will be described in greater detail below).

The user 162 may select one of the first and second fan-speed control devices 120a, 120b in the device list to activate. The network device 160 may prompt the user to choose one of the first and second fan-speed control devices 120a, 120b in the device list to provide a visible indication in the space. In response to a selection of one of the first and second fan-speed control devices 120a, 120b in the device list, the network device 160 may display a warning on the visible display 164, where the warning notifies the user 162 to ensure that there are no obstructions preventing the respective ceiling fan 110a, 110b of the selected one of the first and second fan-speed control devices 120a, 120b from spinning (e.g., rotating). Using the graphical user interface displayed on the visible display 164, the user 162 may provide an input that there are no obstructions preventing the respective ceiling fan 110a, 110b of the selected one of the first and second fan-speed control devices 120a, 120b from spinning. The network device 160 may then transmit a message including an identify command to the selected one of the first and second fan-speed control devices 120a, 120b, which may turn on the respective ceiling fan 110a, 110b with the rotational speed S_FAN1, S_FAN2 set to an identification speed SID. Since both of the first and second fan-speed control devices 120a, 120b turned off the respective ceiling fans 110a, 110b when entering the discovery mode and the selected one of the first and second fan-speed control devices 120a, 120b is now the only one rotating, the user 162 may be able to easily identify the selected one of the first and second fan-speed control devices 120a, 120b. The user 162 may select (e.g., reselect) the one of the first and second fan-speed control devices 120a, 120b that was previously selected and the network device 160 may activate the selected one of the first and second fan-speed control devices 120a, 120b by transmitting an activation message to the selected one of the first and second fan-speed control devices 120a, 120b and storing the device identifier of the selected one of the first and second fan-speed control devices 120a, 120b in the device object in the system configuration data. The user 162 may provide inputs via the graphical user interface to configure operational settings and/or define programming data for the selected fan-speed control device 120a, 120b after the one of the first and second fan-speed control devices 120a, 120b is activated.

FIGS. 2A-2C illustrate an example screen 200 (e.g., a graphical user interface (GUI) window) that may be used to activate one or more remotely-located load control devices, such as remotely-located fan-speed control devices (e.g., the first and second fan-speed control devices 120a, 120b). The fan-speed control devices may be configured to control respective ceiling fans (e.g., the ceiling fans 110a, 110b). For example, the screen 200 may be displayed on a visible display of a network device (e.g., the visible display 164 of the network device 160). The network device may be configured to display a graphical user interface on the visible display for displaying configuration options and/or receiving the inputs from a user (e.g., the user 162) to generate the system configuration data and/or active the remotely-located fan-speed control devices.

After receiving discovery request messages from one or more of the fan-speed control devices, the network device may be configured to display a device list 210 that includes device indicators 212 (e.g., names or other identifiers) of the fan-speed control devices from which the discovery request messages were received (e.g., as shown in FIG. 2A). For example, each of the indicators 212 may comprise a device type of each of the fan-speed control devices and/or a type of electrical load that is controlled by each of the fan-speed control devices (e.g., “ceiling fan”). Each of the indicators 212 may comprise at least a portion of a device identifier (e.g., a unique identifier, such as a serial number) of each of the fan-speed control devices from which the discovery request messages were received. The screen 200 may include an identify button 214 proximate to (e.g., next to) each of the device indicators 212 in the device list 210. The user may select one of the identify buttons 214 for selecting the respective fan-speed control device to provide a visible identification in the space in which the respective ceiling fans are installed.

In response to an actuation of one of the identify buttons 214, the network device may display a pop-up window 220 including a warning 222 that notifies the user to indicate that there are no obstructions preventing the respective ceiling fan of the selected fan-speed control device from spinning (e.g., rotating) as shown in FIG. 2B. The pop-up window 220 may include a confirm button 226 and/or a cancel button 224. In response to an actuation of a cancel button 224 on the pop-up window 220, the network device may be configured to close the pop-up window 220 without causing any of the fan-speed control devices to provide a visible indication in the space in which the respective ceiling fan is installed. The screen 200 may appear as shown in FIG. 2A after selection of the cancel button 224.

The network device may be configured to transmit a message including an identify command for causing the selected fan-speed control device to provide a visible indication in the space in which the respective ceiling fan is installed. For example, in response to an actuation of the confirm button 226 on the pop-up window 220, the network device may be configured to transmit a message including an identify command for causing the selected fan-speed control device to provide a visible indication in the space in which the respective ceiling fan is installed and/or close the pop-up window 220. The network device may be configured to display an activate button 230 next to the device indicator 212 of the selected fan-speed control device (e.g., as shown in FIG. 2C). If the user wants to activate the selected fan-speed control device, the user may actuate the activate button 230 and the network device may activate the selected fan-speed control devices by transmitting an activation message to the selected fan-speed control device and storing a device identifier of the selected fan-speed control device in a device object in system configuration data. Though the pop-up window 220 is displayed to include the warning 222 and/or the network device may be configured to transmit a message that includes the identify command in response to actuation of the confirm button 226, the identify command may be transmitted in response to selection of one of the identify buttons 214 and/or another actuation on the screen 200.

FIG. 3 is a simplified block diagram of an example of a fan-speed control device 300 that may be deployed as, for example, the first and second fan-speed control devices 120a, 120b of the load control system 100 shown in FIG. 1. The fan-speed control device 300 may include a hot terminal H that may be adapted to be coupled to a power source 302, such as an alternating-current (AC) power source. In some examples, the power source 302 may comprise a direct-current (DC) power source. The fan-speed control device 300 may include a controlled-hot terminal CH that may be adapted to be coupled to an electrical load, such as a motor load 304. In one example, the motor load 304 may be a motor of a ceiling fan (e.g., the motor 112a, 112b of the respective first and second ceiling fans 110a, 110b). The fan-speed control device 300 may include a load control circuit, such as a motor control circuit 310, coupled in series electrical connection between the power source 302 and the motor load 304. The motor control circuit 310 may be configured to control the power delivered to the motor load 304. The fan-speed control device 300 may include a control circuit 320 configured to control the motor control circuit 310 to control the power delivered to the motor load 304 to thus control a rotational speed S_MOTOR of the motor load 304. The control circuit 320 may include one or more of a processor (e.g., a microprocessor), a microcontroller, a programmable logic device (PLD), a field programmable gate array (FPGA), an application specific integrated circuit (ASIC), or any suitable controller or processing device. Though a single control circuit is illustrated, one or more control circuits may be implemented in the fan-speed control device 300.

The motor control circuit 310 may be capable of controlling the rotational speed S_MOTOR of the motor load 304 to a number of discrete speeds (e.g., seven discrete speeds), such as a first speed S₁ (e.g., a minimum speed), a second speed S₂, a third speed S₃, a fourth speed S₄, a fifth speed S₅, a sixth speed S₆, and/or a seventh speed S₇ (e.g., a maximum speed). For example, the speeds S₁-S₇ may increase in speed in order (e.g., from the first speed S₁ to the seventh speed S₇). The motor control circuit 310 may comprise a first controllable switching circuit 312a, a second controllable switching circuit 312b, a third controllable switching circuit 312c, and/or a fourth controllable switch circuit 312d. For example, the first, second, third, and/or fourth controllable switching circuits 312a, 312b, 312c, 312d may each comprise a bidirectional semiconductor switch, such as a thyristor (e.g., a triac or one or more silicon-controlled rectifiers), a field-effect transistor (FET) in a rectifier bridge, two FETs in anti-series connection, one or more insulated-gate bipolar junction transistors (IGBTs), and/or other suitable bidirectional semiconductor switches. In addition, the first, second, third, and/or fourth controllable switching circuits 312a, 312b, 312c, 312d may each comprise a relay or other suitable controllably conductive device. The control circuit 320 may be configured to control (e.g., independently control) the first, second, third, and/or fourth controllable switching circuits 312a, 312b, 312c, 312d to render the first, second, third, and/or fourth controllable switching circuits 312a, 312b, 312c, 312d conductive and non-conductive.

The first controllable switching circuit 312a may be coupled in series with a first capacitor C314a, such that the series combination of the first controllable switching circuit 312a and the first capacitor C314a may be coupled in series between the hot terminal H and the controlled-hot terminal CH. The second controllable switching circuit 312b may be coupled in series with a second capacitor C314b, such that the series combination of the second controllable switching circuit 312b and the second capacitor C314b may be coupled in series between the hot terminal H and the controlled-hot terminal CH. The third controllable switching circuit 312c may be coupled in series with a third capacitor C314c, such that the series combination of the third controllable switching circuit 312c and the third capacitor C314c may be coupled in series between the hot terminal H and the controlled-hot terminal CH. For example, the first, second, and third capacitors C314a, C314b, C314c may have different capacitances, e.g., approximately 1 μF, 2.2 μF, and 3.3 μF, respectively. The fourth controllable switching circuit 312d may be coupled (e.g., directly coupled) in series between the hot terminal H and the controlled-hot terminal CH. The series combination of the first controllable switching circuit 312a and the first capacitor C314a, the series combination of the second controllable switching circuit 312b and the second capacitor C314b, the series combination of the third controllable switching circuit 312c and the third capacitor C314c and the fourth controllable switching circuit 312d may be coupled in parallel with each other. In addition, the motor control circuit 310 may comprise a first resistor R316a coupled in parallel with the first capacitor C314a for discharging the first capacitor C314a when the first controllable switching circuit 312a is non-conductive, a second resistor R316b coupled in parallel with the second capacitor C316b for discharging the second capacitor C316b when the second controllable switching circuit 312b is non-conductive, and/or a third resistor R316c coupled in parallel with the third capacitor C316c for discharging the third capacitor C316c when the third controllable switching circuit 312c is non-conductive.

The control circuit 320 may be configured to render (e.g., independently render) the first, second, third, and/or fourth controllable switching circuits 312a, 312b, 312c, 312d conductive and non-conductive to control a magnitude of a load current I_LOAD conducted through the motor load 304 to control the rotational speed S_MOTOR of the motor load 304 to one or more of the number of speeds S₁-S₇. The control circuit 320 may be configured to render the first controllable switching circuit 312a conductive to electrically couple the first capacitor C314a in series between the power source 302 and the motor load 304 to control the rotational speed S_MOTOR of the motor load 304 to the first speed S₁. The control circuit 320 may be configured to render the second controllable switching circuit 312b conductive to electrically couple the second capacitor C314b in series between the power source 302 and the motor load 304 to control the rotational speed S_MOTOR of the motor load 304 to the second speed S₂. The control circuit 320 may be configured to render the third controllable switching circuit 312c conductive to electrically couple the third capacitor C314c in series between the power source 302 and the motor load 304 to control the rotational speed S_MOTOR of the motor load 304 to the third speed S₃. The control circuit 320 may be configured to render the first and third controllable switching circuits 312a, 312c conductive to electrically couple the first and third capacitors C314a, C314c in parallel between the power source 302 and the motor load 304 to control the rotational speed S_MOTOR of the motor load 304 to the fourth speed S₄. The control circuit 320 may be configured to render the second and third controllable switching circuits 312b, 312c conductive to electrically couple the second and third capacitors C314b, C314c in parallel between the power source 302 and the motor load 304 to control the rotational speed S_MOTOR of the motor load 304 to the fifth speed S₅. The control circuit 320 may be configured to render the first, second, and third controllable switching circuits 312a, 312b, 312c conductive to electrically couple the first, second, and third capacitors C314a, C314b, C314c in parallel between the power source 302 and the motor load 304 to control the rotational speed S_MOTOR of the motor load 304 to the sixth speed S₆. The control circuit 320 may be configured to render the fourth controllable switching circuit 312d conductive to bypass the first, second, and third capacitors C314a, C314b, C314c to control the rotational speed S_MOTOR of the motor load 304 to the seventh speed S₇.

In the example described herein, the control circuit 320 may not render the first and second controllable switching circuits 312a, 312b conductive to electrically couple the first and second capacitors C314a, C314b in parallel between the power source 302 and the motor load 304 to control the motor load 304 to control the rotational speed S_MOTOR of the motor load 304 to an eighth speed S₈. This may have been done because of the particular capacitances selected for the respective first, second, and third capacitors C314a, C314b, C314C. For instance, if the first, second, and third capacitors C314a, C314b, C314c may have capacitances of approximately 1 μF, 2.2 μF, and 3.3 μF, respectively, then the total capacitance created when the first and second controllable switching circuits 312a, 312b are rendered conductive (e.g., 1 μF+2.2 μF=3.2 μF) is substantially equal to the total capacitance created when just the third controllable switching circuits 312c is rendered conductive (e.g., 3.3 μF), so this operation is not performed by the control circuit 320 in some examples. However, if the capacitances of the first, second, and third capacitors C314a, C314b, C314c are selected to be different values (e.g., where the combined capacitance of the first and second capacitors C314a, C314b does not equal the capacitance of the third capacitor C314c), then the control circuit 320 may be configured to render the first and second controllable switching circuits 312a, 312b conductive to electrically couple the first and second capacitors C314a, C314b in parallel between the power source 302 and the motor load 304 to control the rotational speed S_MOTOR of the motor load 304 to the eighth speed S_POS-8, such that the fan-speed control device 300 may be configured with up to eight speeds S₁-S₈. For example, in some examples, the eighth speed S₈ may be between the third speed S₃ and the fourth speed S₄.

The fan-speed control device 300 may include a power supply 330. The power supply 330 may generate a direct-current (DC) supply voltage V_CC for powering the control circuit 320 and the other low-voltage circuitry of the fan-speed control device 300. The power supply 330 may be coupled between the hot terminal H and the controlled-hot terminal CH (e.g., in parallel with the motor control circuit 310). The power supply 330 may be configured to conduct a charging current through the motor load 304 to generate the DC supply voltage V_CC.

The fan-speed control device 300 may comprise a zero-crossing detector 322 (e.g., a zero-cross detect circuit) electrically coupled between the hot terminal H and the controlled-hot terminal CH. The zero-crossing detector 322 may be configured to generate a zero-cross detect signal V_ZC that indicates the zero-crossing points of an AC mains line voltage generated by the power source 302. The control circuit 320 may receive the zero-cross detect signal V_ZC and may be configured to render the controllable switching circuits 312a, 312b, 312c, 314d of the motor control circuit 410 based on the zero-cross detect signal V_ZC. For example, the control circuit 320 may be configured to render the controllable switching circuits 312a, 312b, 312c, 312d conductive and non-conductive at approximately the zero-crossings of the AC mains line voltage as determined from the zero-cross detect signal V_ZC received from the zero-crossing detector 322.

The fan-speed control device 300 may comprise a memory 324 that may be communicatively coupled to the control circuit 320 for the storage and/or retrieval of data. The memory 324 may be implemented as an external integrated circuit (IC) or as an internal circuit of the control circuit 320. The memory 324 may comprise a computer-readable storage media or machine-readable storage media that maintains computer-executable instructions for performing one or more procedure and/or functions as described herein. For example, the memory 324 may comprise computer-executable instructions or machine-readable instructions that when executed by the control circuit 320 configure the control circuit 320 to provide one or more portions of the procedures described herein. The control circuit 320 may access the instructions from the memory 324 for being executed to cause the control circuit 320 to operate as described herein, or to operate one or more other devices as described herein. The memory 324 may comprise computer-executable instructions for executing configuration software. For example, the control circuit 320 may be configured to store in and retrieve from the memory 324 configuration data for configuring the fan-speed control devices of the load control system and/or control data for controlling the fan-speed control devices of the load control system. The configuration data may include a portion of the system confirmation data of the load control system 100. For example, the control circuit 320 may be configured to store in and retrieve from the memory 324 configuration settings (e.g., operational settings), programming data, association data (e.g., unique identifiers of control devices of the load control system), etc. In addition, the control circuit 320 may be configured to store in and retrieve from the memory 324 operational parameters, such as, the present rotational speed and/or direction of the motor load 304 controlled by the fan-speed control device 300), etc. For example, the operational characteristics stored in the memory 324 may be configured during a configuration procedure of the fan-speed control device 300. The control data may be included in one or more commands for controlling the motor load 304. The control circuit 320 may be responsive to the control data in message that include a device identifier (e.g., a unique identifier of the fan-speed control device 300, such as a serial number). The control circuit 320 may use the control data to control the motor control circuit 310 (e.g., based on the configuration settings or operational settings).

The fan-speed control device 300 may comprise a communication circuit 326 configured to communicate (e.g., transmit and/or receive) messages. For example, the communication circuit 326 may comprise one or more wired communication circuits and/or wireless communication circuits. The one or more wired communication circuits and/or wireless communication circuits of the communication circuit 326 may be implemented as external integrated circuits (ICs) or as internal circuits of the control circuit 320. For example, the one or more wireless communication circuits of the communication circuit 326 may include for example, one or more a radio-frequency (RF) transceivers coupled to a respective antenna for transmitting and/or receiving RF signals. In addition, the one or more wireless communication circuits of the communication circuit 326 may also include an RF transmitter for transmitting RF signals, an RF receiver for receiving RF signals, or an infrared (IR) transmitter and/or receiver for transmitting and/or receiving IR signals. The one or more wireless communication circuits of the communication circuit 326 may be capable of performing communication via the same communication channels or different communication channels. In some examples, the communication circuit 326 may be configured to communicate via a network, such as a wireless or wired local area network (LAN), e.g., for access to the Internet. In addition, the communication circuit 326 may be configured to communicate via a control network (e.g., a wired or wireless control communication link) for communicating with the fan-speed control devices of the load control system. The control circuit 320 may be configured to receive messages including control data (e.g., one or more commands) for controlling the motor load 304 via the communication circuit 326. The control circuit 320 may be responsive to the control data in message that include a device identifier (e.g., a unique identifier of the fan-speed control device 300, such as a serial number). The control circuit 320 may use the control data to control the motor control circuit 310 to adjust the rotational speed S_MOTOR of the motor load 304. In addition, the control circuit 320 may be configured to transmit, to an external fan-speed control device via the communication circuit 326, messages including control data (e.g., one or more commands) for controlling a motor load controlled by the external fan-speed control device. Further, the control circuit 320 may be configured to receive messages (e.g., including feedback data, such as status information of the fan-speed control devices) from the fan-speed control devices via the communication circuit 326.

The fan-speed control device 300 may further comprise a user interface circuit 328. The user interface circuit 328 may comprise one or more input circuits for receiving inputs. For example, the user interface circuit 328 may comprise one or more actuators configured to be actuated in response to actuation of one or more respective buttons of the fan-speed control device 300. In addition, the user interface circuit 328 may comprise a touch sensitive circuit (e.g., a capacitive or resistive touch element) that may be responsive to actuations (e.g., touch actuations) of a touch sensitive surface of the fan-speed control device 300. The control circuit 320 may be configured to generate control data (e.g., one or more commands) for controlling the motor load 304 in response to the user inputs received via the user interface circuit 328. The control circuit 320 may use the control data to control the motor control circuit 310 to adjust the rotational speed S_MOTOR of the motor load 304. Further, the user interface circuit 328 may comprise one or more light sources configured to illuminate visual indicators of the fan-speed control device 300 for providing feedback information to a user.

During an activation process of a commissioning procedure, the fan-speed control device 300 may be established in the load control system (e.g., during an activation procedure configured to activate the fan-speed control device 300 in the load control system), such that the fan-speed control device 300 may be configured to communicate with other control devices of the load control system (e.g., via the RF signals 106). When powering up (e.g., after the power is cycled to the fan-speed control device 300), the control circuit 320 may be configured to enter the discovery mode. For example, the control circuit 320 may be configured to enter the discovery mode for a timeout period (e.g., approximately five minutes) and then exit (e.g., automatically exit) the discovery mode. The control circuit 320 may be configured to implement a timer to determine when the timeout period expires.

After entering the discovery mode, the control circuit 320 may be configured to transmit a discovery request message via the communication circuit 326. The discovery request message may include the device identifier of the fan-speed control device 300. In response to receiving a message including an identify command via the communication circuit 326, the control circuit 320 may control the motor control circuit 310 to cause the motor load 304 to rotate at an identification speed S_ID. Variations in motors of ceiling fans (e.g., such as manufacturer, model, version, type, etc.) may cause the motor load 304 to operate differently from one motor load to the next. For example, when the control circuit 320 is controlling the motor control circuit 310 to set the rotational speed S_MOTOR to one of the discrete speeds S₁-S₇ (e.g., the available speeds), the actual resulting rotational speed S_MOTOR may be different from one motor load to the next. In addition, some motor loads may not be able to turn on at one or more of the lower speeds of the discrete speeds S₁-S₇. The identification speed SID may be one of the discrete speeds S₁-S₇ that may be relatively low, but large enough such that most motor loads are able to turn on at the identification speed S_ID. For example, the identification speed S_ID may be the third speed. S₃. The identification speed S_ID may be set to a predefined relatively low speed (e.g., as compared to the seventh speed S₇) to avoid damage when obstructions are near the ceiling fan during the activation process. The predefined identification speed SID may be set to a particular predefined speed that is one of the total discrete speeds (e.g., the third speed S₃ of the discrete speeds S₁-S₇). The predefined identification speed SID may be set to a particular one of the discrete speeds that is higher than the lowest discrete speed (e.g., the first speed S₁ of the discrete speeds S₁-S₇), but closer to the lowest discrete speed than the highest discrete speed (e.g., the seventh speed S₇ of the discrete speeds S₁-S₇). In some cases, the identification speed S_ID may be set to the lowest available speed (e.g., the first speed S₁). The identification speed S_ID may be configurable by a user input via the network device. For example, the network device may display a list of the fan speeds, or a subset of available fan speeds (e.g., S₁ to S₃) for user selection on the network device.

The control circuit 320 may be configured to receive an activation message while in the discovery mode, and may store activation data received in the activation message in the memory 322. The activation data may establish the fan-speed control device in the load control system, such that the fan-speed control device may be configured to communicate with other control devices of the load control system. The activation data may include one or more portions of the system configuration data and may be transmitted to the selected control device along with the activation, such as a device name, a device type, a device location, a system configuration identifier (e.g., a configuration address for communicating with other control devices), and/or other network credentials for communicating on a wireless network. In addition, the one or more other portions of the system configuration data (e.g., programming data and/or association data) may be transmitted to the selected control device along with the activation data as a result of activating the selected control device in the load control system, such as associated control devices, one or more operational settings, and/or programming data

When the fan-speed control device 300 has been activated and/or in response to the timeout timer expiring, the control circuit 320 may be configured to exit the discovery mode and control the rotational speed S_MOTOR to a previous speed S_PREV to which the control circuit 320 was controlling the rotational speed S_MOTOR of the motor load 304 prior to entering the discovery mode.

FIG. 4 is a block diagram of an example processing device 400, which may be deployed as the system controller 150, the network device 160, a computing device (e.g., a computer and/or a server) running configuration software (e.g., design configuration software) and/or a graphical user interface (GUI) software, and/or another processing device The processing device 400 may comprise a control circuit 410 configured to generate configuration data for configuring the operation of one or more control devices of a load control system (e.g., the load control system 100). In some examples, the control circuit 410 may be configured to generate control data (e.g., commands) for controlling one or more load control devices, such as fan-speed control devices (e.g., the fan-speed control devices 120a, 120b). The control circuit 410 may include one or more of a processor (e.g., a microprocessor), a microcontroller, a programmable logic device (PLD), a field programmable gate array (FPGA), an application specific integrated circuit (ASIC), or any suitable controller or processing device.

The processing device 400 may comprise a power source 420 for producing a power source voltage V_PS. For example, the power source 420 may comprise one or more batteries and/or a photo-voltaic power source (e.g., a solar cell). In addition, the power source 420 may comprise one or more energy storage elements, such as super capacitors and/or rechargeable batteries. Further, the power source 420 may also be configured to receive power from an external power source, such as an external direct-current (DC) power source or an alternating-current (AC) power source. The processing device 400 may also comprise a power supply 422 that may be configured to receive the power source voltage V_PS and generate a DC supply voltage V_CC for powering the control circuit 410 and other circuitry (e.g., low-voltage circuitry) of the processing device 400.

The processing device 400 may comprise a memory 412 that may be communicatively coupled to the control circuit 410 for the storage and/or retrieval of data. The memory 412 may be implemented as an external integrated circuit (IC) or as an internal circuit of the control circuit 410. The memory 412 may comprise a computer-readable storage media or machine-readable storage media that maintains computer-executable instructions for performing one or more procedures and/or functions as described herein. For example, the memory 412 may comprise computer-executable instructions or machine-readable instructions that when executed by the control circuit 410 configure the control circuit 410 to provide one or more portions of the procedures described herein. The control circuit 410 may access the instructions from the memory 412 for being executed to cause the control circuit 410 to operate as described herein, or to operate one or more other devices as described herein. The memory 412 may comprise computer-executable instructions for executing configuration software. For example, the control circuit 410 may be configured to store in and retrieve from the memory 412 configuration data for configuring the fan-speed control devices of the load control system and/or control data for controlling the fan-speed control devices of the load control system. The configuration data may include a portion of the system confirmation data of the load control system. For example, the control circuit 410 may be configured to store in and retrieve from the memory 412 configuration settings (e.g., operational settings), programming data, association data (e.g., unique identifiers of control devices of the load control system), etc. In addition, the control circuit 410 may be configured to store in and retrieve from the memory 412 operational parameters, such as, the present rotational speed and/or direction of the motor load 304 controlled by the fan-speed control device 300, etc. For example, the operational characteristics stored in the memory 412 may be configured during a configuration procedure of the processing device 400. The control data may be included in one or more commands for controlling an electrical load, such as the motor load 304 of fan-speed control device 300. The control data in a message may include a device identifier (e.g., a unique identifier of the fan-speed control device 300, such as a serial number).

The processing device 400 may comprise a communication circuit 414 configured to communicate (e.g., transmit and/or receive) messages. For example, the communication circuit 414 may comprise one or more wired communication circuits and/or wireless communication circuits. The one or more wired communication circuits and/or wireless communication circuits of the communication circuit 414 may be implemented as external integrated circuits (ICs) or as internal circuits of the control circuit 410. For example, the one or more wireless communication circuits of the communication circuit 414 may include for example, one or more a radio-frequency (RF) transceivers coupled to a respective antenna for transmitting and/or receiving RF signals. In addition, the one or more wireless communication circuits of the communication circuit 414 may also include an RF transmitter for transmitting RF signals, an RF receiver for receiving RF signals, and/or an infrared (IR) transmitter and/or receiver for transmitting and/or receiving IR signals. The one or more wireless communication circuits of the communication circuit 414 may be capable of performing communication via the same communication channels or different communication channels. In some examples, the communication circuit 414 may be configured to communicate via a network, such as a wireless or wired local area network (LAN), e.g., for access to the Internet. In addition, the communication circuit 414 may be configured to communicate via a control network (e.g., a wired or wireless control communication link) for communicating with the fan-speed control devices of the load control system. The control circuit 410 may be configured to transmit messages including control data (e.g., one or more commands) for controlling the fan-speed control devices via the communication circuit 414. In addition, the control circuit 410 may be configured to receive messages (e.g., including feedback data, such as status information of the fan-speed control devices) from the fan-speed control devices via the communication circuit 414.

The processing device 400 may further comprise a user interface circuit 416. The user interface circuit 416 may comprise one or more input circuits for receiving inputs. For example, the user interface circuit 416 may comprise one or more actuators configured to be actuated in response to actuation of one or more respective buttons of the processing device 400. In addition, the user interface circuit 416 may comprise a touch sensitive circuit (e.g., a capacitive or resistive touch element) that may be responsive to actuations (e.g., touch actuations) of a touch sensitive surface of the processing device 400 (e.g., a touch screen). Further, the user interface circuit 416 may comprise one or more light sources configured to illuminate visual indicators of the processing device 400 for providing feedback information to a user. In some examples, the user interface circuit 416 may comprise a visual display.

The control circuit 410 of the processing device 400 may be configured to define system configuration data for the load control system in response to inputs received via the user interface circuit 416. For example, the control circuit 410 may be configured to execute a design configuration application (e.g., design configuration software) to display the graphical user interface on the visible display of the user interface circuit 416 for displaying configuration options and/or receiving the inputs from the user to generate the system configuration data. The control circuit 410 of the processing device 400 may be configured to coordinate a commissioning procedure in response to inputs received via the user interface circuit 416. During an activation process of the commissioning procedure, the control circuit 410 may be configured to transmit a discovery initiation message (e.g., a discovery initiation beacon message) via the communication circuit 414. In some examples, the control circuit 410 may be configured to repetitively (e.g., periodically) transmit the discovery initiation message during the activation procedure. The discovery initiation message may include a discovery initiation identifier, which may be a unique identifier (e.g., a serial number) of the processing device 400 and/or the design configuration application executed by the control circuit 410. In some example, the control circuit 410 may be configured to display on the visible display of the user interface circuit 416 a prompt to cause the user to cycle power to a circuit on which one or more remotely-located fan-speed control devices are coupled.

The control circuit 410 may be configured to receive discovery request messages (e.g., discovery request beacon messages) from one of more control devices (e.g., remotely-located fan-speed control devices) of the load control system via the communication circuit 414. The discovery request message may include a device identifier, which may be a unique identifier (e.g., a serial number) of the control device that transmitted the discovery request message. The control circuit 410 may be configured to display on the visible display of the user interface circuit 416 a device list of the control devices of the load control system from which the control circuit 410 received the discovery request messages. In response to a selection of one of the control devices (e.g., a fan-speed control device) in the device list, the control circuit 410 may display on the visible display of the user interface circuit 416 a warning that notifies the user to ensure that there are no obstructions preventing the respective ceiling fan of the selected fan-speed control device from spinning (e.g., rotating). Upon receiving a confirmation that there are no obstructions preventing the respective ceiling fan of the selected one fan-speed control device from spinning (e.g., in response to an input received via the user interface circuit 416), the control circuit 410 may transmit a message including an identify command to the selected fan-speed control device. In response to receiving an indication to activate the selected fan-speed control device (e.g., to which the message including the identify command was transmitted), the control circuit 410 may activate the selected fan-speed control device by transmitting an activation message to the selected fan-speed control device and storing the device identifier of the selected fan-speed control device in the device object in the system configuration data (e.g., in the memory 412).

FIG. 5 is a flowchart of an example procedure 500 that may be executed by a network device (e.g., the network device 160 of the load control system 100 and/or the processing device 400) to configure (e.g., activate) a fan-speed control device (e.g., the fan-speed control devices 120a, 120b, 300). The procedure 500 may be executed by a control circuit of the network device (e.g., a control circuit of the network device 160 and/or the control circuit 410 of the processing device 400). For example, the control circuit may execute the procedure 500 at 510 in response to receiving user inputs via a user interface of the network device (e.g., from a user via a graphical user interface displayed on a visible display). One or more portions of the procedure 500 may be stored as computer-executable instructions configured to be stored in memory for execution on one or more control circuits. Though the procedure 500 may be described as being implemented on a single device, such as a single network device, one or more portions of the procedure 500 may be implemented by one or more devices, such as multiple network devices or a network device and one or more system controllers or other processing devices.

As shown in FIG. 5, the control circuit of the network device may determine, at 512, whether an indication has been received to activate one or more remotely-located control devices (e.g., remotely-located fan-speed control devices) in the load control system. For example, the control circuit may receive a user input to activate one or more remotely-located fan-speed control devices in the load control system via the graphical user interface. If the control circuit fails to receive an indication to activate the one or more remotely-located fan-speed control devices at 512 (e.g., within a predefined period of time), the procedure 500 may end at 538. If the control circuit receives an indication to activate the one or more remotely-located fan-speed control devices at 512, the control circuit may prompt the user to cycle the power to the remotely-located fan-speed control devices at 514. For example, the control circuit may prompt the user to cycle the power to one or more remotely-located fan-speed control devices via the graphical user interface.

To activate one or more of the remotely-located fan-speed control devices, the control circuit of the network device may prompt the user to cycle power to a circuit to which the one or more of the remotely-located control devices are electrically coupled. The user may cycle power to the circuit to which the one or more of the remotely-located fan-speed control devices are electrically coupled by opening and then subsequently closing a circuit breaker in a breaker panel (e.g., the circuit breaker 102 in the circuit panel 104). When powering up (e.g., after the power is cycled to the circuit), the fan-speed control devices may each enter a discovery mode. Though the procedure 500 illustrates the cycling of power to cause the fan-speed control devices to enter the discovery mode, the fan-speed control devices may enter the discovery mode in response to one or more other triggering events, such as receipt of a discovery initiation message (e.g., a discovery initiation beacon message or another message from the network device) or an actuation of an actuator (e.g., button) thereon.

After entering the discovery mode, the fan-speed control devices may each transmit a discovery request message. At 516, the control circuit may determine whether a discovery request message is received via the communication circuit from one or more of the fan-speed control devices. Each of the discovery request messages may include a device identifier, which may be a unique identifier (e.g., a serial number) of the fan-speed control device that transmitted the discovery request message. Each of the discovery request messages may also include a device type (e.g., fan-speed control device) and/or other system configuration data.

If the control circuit receives a discovery request message at 516, the control circuit may add an indicator for the discovered fan-speed control device (e.g., indicated by the device identifier in the discovery request message) to a device list at 518 for being displayed to the user. For example, the indicator of the discovered fan-speed control device may include the device type and/or at least a portion of the device identifier of the discovered fan-speed control device. The indicator of the discovered fan-speed control device may include other system configuration data associated with the discovered fan-speed control device. The control circuit may continue to add identifiers for discovered fan-speed control devices to the device list at 518 when additional discovery request messages are received at 516. The control circuit of the network device may include (e.g., only include) in the device list identifiers for fan-speed control devices on the circuit to which power was just cycled. In this manner, the length of the device list (e.g., the number of identifiers listed in the device list) may be smaller than when control devices of the load control system enter the discovery mode in response to receiving a discovery initiation message from the network device. This may allow for identifying control devices for being activated more easily (e.g., in a faster manner) than filtering through a larger number of control devices identifying themselves for potential activation by transmitting a discovery initiation message. The control circuit of the network device may stop adding identifiers for control devices to the device list after a timeout period, in response to a user selection, and/or after a predefined number of control devices are discovered and/or added to the device list.

At 520, the control circuit may determine whether one of the identifiers of the remotely-located fan-speed control device in the device list has been selected for providing a visible indication in the space. The control circuit may display a warning at 522 in response to the selection of the indicator of the remotely-located fan-speed control device. The control circuit may identify the selection of the indicator of the remotely-located fan-speed control device and display the warning at 522. The warning may notify the user to ensure that there are no obstructions preventing the respective ceiling fan of the selected fan-speed control device from spinning (e.g., rotating). The control circuit may determine, at 524, whether a confirmation is provided via user input that there are no obstructions preventing the respective ceiling fan of the selected fan-speed control device from spinning or whether a cancelation is received at 526 for canceling the visible indication. If the control circuit receives an indication to cancel the visible indication, the procedure 500 may return to determining if a discovery request message has been received at 516 and/or awaiting a selection of one of the devices in the device list at 520. If the control circuit of the network device receives a confirmation that there are no obstructions preventing the respective ceiling fan of the selected fan-speed control device from spinning (e.g., rotating) at 524, the control device may transmit a message at 528 including an identify command to the selected fan-speed control device. Though an example is provided for displaying the warning at 522 and transmitting the message at 528 to identify the remotely-located fan-speed control device in response to the confirmation at 524, the procedure 500 may transmit the identify command at 528 in response to receiving the selection of the fan-speed control device at 520 (e.g., without providing the warning). The identify command may be configured to cause the fan-speed control device to turn on a respective ceiling fan with a rotational speed S_FAN1, S_FAN2 set to an identification speed S_ID. The identification speed S_ID may be included in the identify command transmitted at 528 or may be preprogrammed at the fan-speed control device.

After the user detects that the fan-speed control device is identifying itself in the space, the user may decide whether this is the remotely-located fan-speed control device to be activated. The control circuit may determine, at 530, whether a user input is received to activate the fan-speed control device that has been selected for identification. The control circuit may continue to wait for the user input to activate the fan-speed control device for a period of time. The control circuit may receive an indication that the remotely-located fan-speed control identifying itself is not the remotely-located fan-speed control to be activated (e.g., via a user input) and cancel the current procedure and/or provide the device list for selection of another device for identification at 520. The control circuit may receive a user selection (e.g., reselection) of the fan-speed control device that was previously selected for identification and the control circuit may determine, at 530, to activate the selected fan-speed control device. The control circuit may store the device identifier for the selected fan-speed control device in the device object in the system configuration data at 532. At 534, the control circuit of the network device may transmit an activation message to the selected fan-speed control device. The activation message may include activation data that may establish the fan-speed control device in the load control system, such that the fan-speed control device may be configured to communicate with other control devices of the load control system. In addition, the control circuit may receive inputs to configure operational settings and/or define programming data for the selected fan-speed control device and/or transmit the operational settings and/or defined programming data to the selected fan-speed control device. The activation data may include one or more portions of system configuration data (e.g., programming data and/or association data) generated as a result of activating the fan-speed control device 300 in the load control system, such as a device name, a device type, a device location, a system configuration identifier (e.g., a configuration address), other network credentials for communicating on a wireless network, associated control devices, one or more operational settings, and/or programming data.

At 536, the control circuit may determine whether there are more remotely-located fan-speed devices to be activated. For example, the control circuit may receive a user input to activate one or more additional control devices (e.g., fan-speed control devices) and proceed to activate previously discovered devices and/or discover additional devices for activation. If there are no other remotely-located fan-speed control devices to be activated at 536, the procedure may end at 538. The control circuit may determine that there are no other remotely-located fan-speed control devices based on a user input or after a lack of user input after a period of time.

FIG. 6 is a flowchart of an example procedure 600 that may be executed by a fan-speed control device (e.g., the fan-speed control devices 120a, 120b of the load control system 100, and/or the fan-speed control device 300) to configure (e.g., activate) the fan-speed control device. The procedure 600 may be executed by a control circuit of the control device (e.g., control circuits of the fan-speed control devices 120a, 120b, and/or the control circuit 320 of the fan-speed control device 300). For example, the control circuit may execute the procedure 600 at 610 in response to powering up (e.g., as part of a start-up routing of the control circuit). The control circuit may power up in response to the user cycling power to a circuit to which the fan-speed control device is electrically coupled. The user may cycle power to the circuit to which the fan-speed control device is electrically coupled by opening and then subsequently closing a circuit breaker in a breaker panel (e.g., the circuit breaker 102 in the breaker panel 104).

When powering up (e.g., after the power is cycled to the circuit), the control circuit of the fan-speed control device may enter a discovery mode at 612. After entering the discovery mode, the fan-speed control device may start a timeout timer at 614. The timeout timer may be used to determine the amount of time the control circuit of the fan-speed control device is to be in the discovery mode and/or transmitting discovery messages. The control circuit of the fan-speed control device may store a present speed of the ceiling fan in memory at 616 as a previous speed S_PREV to which the control circuit may return the ceiling fan at a later time. The present speed may be one of a number of discrete speeds (e.g., seven discrete speeds) at which the fan-speed control device may operate the ceiling fan. The previous speed S_PREV may be a fan speed of zero or off, if the fan-speed control device is not activating/spinning the fan, but is in a discovery mode. At 618, the control circuit of the fan-speed control device may turn off the ceiling fan. Each of the fan-speed control devices may turn off their corresponding ceiling fans during the discovery mode to assist the user in identifying one of the fan-speed control devices that is controlling the respective ceiling fan to rotate.

At 620, the fan-speed control device may transmit one or more discovery request messages. For example, the discovery request messages may be transmitted repeatedly or periodically during the discovery mode. At 622, the control circuit of the fan-speed control device may determine whether an identify command is received (e.g., which may be transmitted in response to receipt of the discovery request message(s)). The control circuit may receive the identify command from a network device, for example. The control circuit of the fan-speed control device may await a timeout period to determine whether the identify command is received at 622. The timeout period may be the same or different period of time to which the timeout timer is set at 614. If the control circuit of the fan-speed control device identifies that the timeout period has expired at 624 (e.g., without receiving the identify command), the control circuit may control the ceiling fan to the previous speed S_PREV that is stored in memory at 634. The control circuit may then exit the discovery mode at 636 and the procedure 600 may end at 638. Though the control circuit is described as exiting the discovery mode after controlling the ceiling fan to the previous speed S_PREV that is stored in memory at 634 after exiting the discovery mode.

If the control circuit of the fan-speed control device receives the identify command at 622 (e.g., prior to the timeout at 624), the control circuit of the fan-speed control device may turn on the ceiling fan to an identification speed SID at 626. The identification speed SID may be included in the identify command received from another device (e.g., transmitted at 528) or may be preprogrammed in memory at the fan-speed control device. At 628, the control circuit of the fan-speed control device may determine whether an activation message is received. The activation message may be received from the network device, for example. The activation message may be transmitted by the network device (e.g., in response to an actuation at the network device) to activate the fan-speed control device in the load control system for enabling communications with other control devices and/or control in the load control system. After the fan-speed control device identifies itself, the user may fail to activate the identified device by transmitting the activation message. The control circuit of the fan-speed control device may await a timeout period to determine whether the identify command is received at 628. The timeout period may be the same or different period of time to which the timeout timer is set at 614 and/or 624. If the control circuit of the fan-speed control device determines that the timeout period has expired at 630, the control circuit may control the ceiling to the previous speed S_PREV that is stored in memory at 634. The control circuit may then exit the discovery mode at 636 and the procedure 600 may end at 638.

If the control circuit of the fan-speed control device receives the activation message at 628 prior to the timeout at 630, the control circuit of the fan-speed control device may store activation data at 632. The activation data may be received in the activation message. The activation data may establish the fan-speed control device in the load control system, such that the fan-speed control device may be configured to communicate with other control devices of the load control system. In addition, the control circuit of the fan-speed control device may receive operational settings and/or define programming data. The activation data may include one or more portions of system configuration data (e.g., programming data and/or association data) and may be transmitted to the selected control device along with the activation,, such as a device name, a device type, a device location, a system configuration identifier (e.g., a configuration address for communicating with other control devices), and/or other network credentials for communicating on a wireless network. After the fan-speed control device is activated, the control circuit of the fan-speed control device may control the ceiling to the previous speed S_PREV that is stored in memory at 634. The fan-speed control device may also, or alternatively, receive operational settings and/or programming data from the programming device for updating the operational settings and/or programming thereon in memory. The control circuit may then exit the discovery mode at 636 and the procedure 600 may end at 638.