Described herein are load control systems for controlling the amount of power that is delivered to an electrical load, such as a lighting load, for example. Such load control systems may be embodied in a two-part load control system that includes a load control device and a remote control device that may both be mounted to a single electrical wallbox.
Some prior art load control devices may be configured to control an electrical load in response to direct communication from a remote control device. Such load control devices may be difficult to configure based on the location of the load control device after installation. For example, the load control device may be installed in a ceiling, behind a wall, or in another difficult-to-reach or remote location. In such prior art systems, the user needs to access the load control device by hand to configure the device to respond to communications from a remote control device. This, of course, is difficult, if not impossible, for the user when the load control device is located in a difficult-to-reach or remote location.
In order to control the load 104 from one of the remote control devices, the load control device 106 may be configured to receive communications directly from that device. A button 108 on the load control device 106 may be used for configuring the load control system 100. The button 108 may be actuated, along with a button on the remote control device (e.g., button 116 on the remote control 110, button 118 on the daylight sensor 114, or button 120 on the occupancy sensor 112), to associate the remote control device with the load control device 106. Each associated remote control device may then be used to control the load via direct communication with the load control device 106.
If the user is done configuring remote control devices, at 212, for directly controlling the operation of the load control device 106, then the process 200 ends at 214. If the user is not done configuring remote control devices, at 212, and wishes to configure another remote control device (e.g., the daylight sensor 114 or the occupancy sensor 112) to directly control the operation of the load control device 106, the user may start the process 200 again at 202 using another remote control device (e.g., the daylight sensor 114 or the occupancy sensor 112).
In many installations, it may be desirable to install the load control device 106 in a hard-to-reach or remote location. For example, the load control device 106 may be mounted in the ceiling close to the lighting load 104 or in an electrical panel to minimize the electrical wiring that is needed. Accordingly, the load control device 106 may be installed such that the button 108 is difficult or impossible for the user to access. Typically, in such an installation, one or more remote control devices are associated with the load control device 106, and then the load control device 106 is installed in its permanent location. Consequently, subsequent association of additional remote control devices with the load control device 106, using the prior-art method 200 described above, may be difficult or impossible.
Accordingly, there is a need for a load control system that enables a user of the system to configure the load control device to operate with multiple remote control devices without having to access the load control device directly after the load control device is installed. It would be particularly desirable if the load control device and at least one of the remote control devices could be mounted to a single electrical wallbox. It would also be desirable if the load control device could provide power to operate the remote control device while both devices are mounted to the single electrical wallbox.
A load control system is disclosed herein for controlling an amount of power delivered from an AC power source to an electrical load. For example, the load control system may include a load control device and a remote control device for controlling operation of the load control device. The load control device may be adapted to be coupled in series electrical connection between the AC power source and the electrical load for controlling the amount of power delivered to the electrical load. The load control device may include a first inductive coil. The remote control device may include a power supply and a second inductive coil. The remote control device may be configured to charge the power supply using energy derived from magnetic coupling between the first inductive coil and the second inductive coil. The remote control device may also be configured to communicate information to the load control device via the magnetic coupling between the first inductive coil and the second inductive coil.
According to another embodiment, the system may include a load control device and a remote control device for controlling an operation of the load control device. The load control device may include a first near-field communication (NFC) module and the load control device may include a second NFC module. The remote control device may be configured to communicate information to the load control device, as described herein, via transmission of NFC radio signals to the first NFC module.
The load control device 306 may be associated with one or more remote control devices, such as a remote control 312, an occupancy sensor 314, a daylight sensor 316, or any other remote control device that is capable of controlling the load 304 through transmission of digital messages to the load control device 306. The load control device 306 may include a radio-frequency (RF) communication circuit for receiving the digital messages via RF signals 310. The RF communication circuit may include an RF receiver or RF transceiver, for example, capable of receiving the digital messages via the RF signals 310. The load control device 306 is operable to control the electrical load 304 in response to the digital messages received via the RF signals 310. In addition, the load control device 306 includes a button 308 for use in configuring the load control system 300 as described herein.
The remote control 312 includes an on button 318, an off button 326, a raise button 322, a lower button 320, and a preset button 324 that, when actuated, may be used to control the load 304. The remote control 312 may be mounted in the opening of a faceplate 328 as shown in
The load control system 300 may include other remote control devices for controlling the load 304 via the load control device 306, such as the occupancy sensor 314 and/or the daylight sensor 316, for example. In addition, the load control system 300 may include other types of input devices, such as, for example, vacancy sensors, temperature sensors, humidity sensors, security sensors, proximity sensors, keypads, key fobs, cell phones, smart phones, tablets, personal digital assistants, personal computers, timeclocks, audio-visual controls, and/or safety devices. In addition, the load control device 306 may be operable to receive the RF signals 310 from a central control transmitter, for example, for receiving a broadcast command, such as a timeclock command, a load shed command, or a demand response command. An example of a central control transmitter is described in greater detail in commonly-assigned U.S. Provisional Patent Application No. 61/654,562, filed Jun. 1, 2012, entitled LOAD CONTROL SYSTEM HAVING INDEPENDENTLY-CONTROLLED UNITS RESPONSIVE TO A BROADCAST TRANSMITTER, the entire disclosure of which is hereby incorporated by reference.
The occupancy sensor 314 and/or the daylight sensor 316 may be indirectly associated with the load control device 306 via the remote control 312. For example, after the remote control 312 is associated with the load control device 306, one or more of the buttons 318-326 on the remote control 312 may be actuated (e.g., by pressing and holding for a predetermined period of time) causing the remote control 312 to transmit a digital message to the load control device 306 for associating one or more other remote control devices (e.g., occupancy sensor 314 and/or daylight sensor 316) with the load control device 306. The digital message may cause the load control device 306 to automatically enter an association mode for associating with another remote control device (e.g., the occupancy sensor 314 or the daylight sensor 316).
The occupancy sensor 314 and the daylight sensor 316 are operable to transmit digital messages to the load control device 306, via the RF signals 310. The digital messages may be used for associating the remote control devices with the load control device 306 when the load control device 306 is in an association mode. The digital messages for associating the occupancy sensor 314 with the load control device 306 may be transmitted upon the actuation of button 338 (e.g., by pressing and holding button 338 for a predetermined period of time) on the occupancy sensor 314. The digital messages for associating the daylight sensor 316 may be transmitted upon the actuation of button 340 (e.g., by pressing and holding button 340 for a predetermined period of time) on the daylight sensor 316. Once the occupancy sensor 314 or the daylight sensor 316 has been associated with the load control device 306, the associated device (e.g., the occupancy sensor 314 or the daylight sensor 316) may transmit digital messages directly to the load control device 306 for controlling the operation of the load control device 306.
The occupancy sensor 314 may transmit digital messages for controlling the operation of the load control device 306 in response to detecting an occupancy condition (e.g., the presence of an occupant) or a vacancy condition (e.g., the absence of the occupant) in the vicinity of the occupancy sensor 314. The occupancy sensor 314 may be removably mountable to a ceiling or a wall in the space around the load control device 306 and/or the remote control 312. The occupancy sensor 314 may include an internal detector, e.g., a pyroelectric infrared (PIR) detector, which is housed in an enclosure 334, and may be operable to receive infrared energy from the occupant in the space via a lens 336 in the enclosure 334 to thus sense the occupancy condition in the vicinity of the occupancy sensor 314. The occupancy sensor 314 may process the output of the PIR detector to determine whether an occupancy condition or a vacancy condition is presently occurring in the space, for example, by comparing the output of the PIR detector to a predetermined occupancy voltage threshold. Alternatively, the internal detector may include an ultrasonic detector, a microwave detector, or any combination of PIR detectors, ultrasonic detectors, and/or microwave detectors. The occupancy sensor 314 may operate in an “occupied” state or a “vacant” state in response to the detections of occupancy or vacancy conditions, respectively, in the space. If the occupancy sensor 314 is in the vacant state and the occupancy sensor 314 determines that the space is occupied in response to the PIR detector, the occupancy sensor 314 may change to the occupied state.
Alternatively, the occupancy sensor 314 may be implemented as a vacancy sensor 314. The vacancy sensor 314 may operate to send digital messages to the load control device 306 to turn off the lighting load 304 when the vacancy sensor 314 detects a vacancy in the space. Therefore, when using vacancy sensors, the lighting load 304 may be turned on manually (e.g., in response to a manual actuation of the on button 318 of the remote control 312). Examples of RF load control systems having occupancy and vacancy sensors are described in greater detail in U.S. patent application Ser. No. 12/203,518, filed Sep. 3, 2008, and subsequently issued Aug. 30, 2011 as U.S. Pat. No. 8,009,042, entitled RADIO-FREQUENCY LIGHTING CONTROL SYSTEM WITH OCCUPANCY SENSING; U.S. patent application Ser. No. 12/203,500, filed Sep. 3, 2008, and subsequently issued May 10, 2011 as U.S. Pat. No. 7,940,167, entitled BATTERY-POWERED OCCUPANCY SENSOR; and U.S. patent application Ser. No. 12/371,027, filed Feb. 13, 2009, and subsequently issued Jun. 12, 2012 as U.S. Pat. No. 8,199,010, entitled METHOD AND APPARATUS FOR CONFIGURING A WIRELESS SENSOR, the entire disclosures of which are hereby incorporated by reference.
The daylight sensor 316 may be mounted so as to measure a total light intensity in the space around the daylight sensor 316 (e.g., in the vicinity of the lighting load 304 controlled by the load control device 306). The daylight sensor 316 may include an internal photosensitive circuit, e.g., a photosensitive diode, which may be housed in an enclosure 332 having a lens 330 for conducting light from outside the daylight sensor 316 towards the internal photosensitive diode. The daylight sensor 316 may be responsive to the total light intensity measured by the internal photosensitive circuit. Specifically, the daylight sensor 316 may be operable to wirelessly transmit digital messages (e.g., wireless signals) to the load control device 306 via the RF signals 310, such that the load control device 306 controls the present light intensity of the electrical load 304 in response to the total light intensity LT-SNSR measured by the daylight sensor 316. For example, the load control device 306 may control the present light intensity based on instructions/settings received in the digital messages. Examples of RF load control systems having daylight sensors are described in greater detail in U.S. patent application Ser. No. 12/727,956, filed Mar. 19, 2010, entitled WIRELESS BATTERY-POWERED DAYLIGHT SENSOR, and U.S. patent application Ser. No. 12/727,923, filed Mar. 19, 2010, entitled METHOD OF CALIBRATING A DAYLIGHT SENSOR, the entire disclosures of which are hereby incorporated by reference.
As a result of the association of the first remote control device (e.g., the remote control 312), at 404, the first remote control device (e.g., the remote control 312) may be used to directly control the load control device 306 at 406. For example, the load control device 306 may be responsive to messages received from the first remote control device (e.g., the remote control 312) that contain instructions/settings for controlling the load 304. The messages may include the unique identifier (e.g., serial number) of the first remote control device (e.g., the remote control 312), which the load control device 306 may use to determine that the messages containing the instructions/settings are from the associated first remote control device (e.g., the remote control 312). The load control device 306 may execute received instructions/settings for controlling the load 304 if the instructions settings are received from an associated device.
In an example, the load control device 306 may be taken out of association mode to receive messages for controlling the load 304 and/or to control the load 304. The load control device 306 may be taken out of association mode automatically (e.g., at the expiration of a period of time or after an association is finished). Alternatively, the load control device may be taken out of association mode when a user actuates the button 308 on the load control device 306 and/or one or more of the buttons on the first remote control device (e.g., one or more of the predetermined buttons 318-326 on the remote control 312).
The associated first remote control device (e.g., the remote control 312) may be used to further configure and setup the load control system 300. For example, the first remote control device (e.g., the remote control 312) may operate as a master control for the load control device 306 to allow for configuration of the load control device 306, e.g., to allow for association of subsequent remote control devices with the load control device 306. A user may use the first remote control device (e.g., the remote control 312) to indirectly associate another remote control device (e.g., the occupancy sensor 314 or the daylight sensor 316) with the load control device 306, at 408. For example, the user may actuate one or more buttons on the first remote control device (e.g., one or more of the predetermined buttons 318-326 on the remote control 312) to transmit an association message to the load control device 306, causing the load control device 306 to automatically enter an association mode for associating with a second remote control device (e.g., the occupancy sensor 314 or the daylight sensor 316).
The association message transmitted from the first remote control device (e.g., the remote control 312) at 408 may include the unique identifier (e.g., serial number) of the first remote control device (e.g., the remote control 312). The load control device 306 may determine that it has already been associated with the first remote control device (e.g., the remote control 312) based on a comparison of the unique identifier received in the association message with the unique identifiers stored in the load control device 306. When the load control device 306 determines that it is already associated with the first remote control device (e.g., the remote control 312) identified in the association message from the first remote control device (e.g., the remote control 312), it may automatically enter the association mode for associating with the second remote control device (e.g., the occupancy sensor 314 or the daylight sensor 316).
While the load control device 306 is in the association mode, the user may actuate a button on the second remote control device (e.g., button 338 on the occupancy sensor 314 or button 340 on the daylight sensor 316), such that the second remote control device (e.g., the occupancy sensor 314 or the daylight sensor 316) transmits an association message directly to the load control device 306. The association message from the second remote control device (e.g., the occupancy sensor 314 or the daylight sensor 316) may include a respective unique identifier (e.g., a serial number) that may be stored by the load control device 306.
As a result of the association of the second remote control device (e.g., the occupancy sensor 314 or the daylight sensor 316) at 408, the user may directly control the load control device 306, at 410, using the associated second remote control device (e.g., the occupancy sensor 314 or the daylight sensor 316). For example, the load control device 306 may be responsive to messages received directly from the second remote control device (e.g., the occupancy sensor 314 or the daylight sensor 316). The messages may include instructions/settings for controlling the load 304. The messages may also include the unique identifier (e.g., serial number) of the second remote control device (e.g., the occupancy sensor 314 or the daylight sensor 316), which the load control device 306 may use to determine that the messages containing the instructions/settings for controlling the load 304 are received from the second remote control device (e.g., the occupancy sensor 314 or the daylight sensor 316). To enable the receipt of messages for controlling the load 304 and/or control of the load 304 at the load control device 306, the load control device 306 may be taken out of association mode as described herein.
The process 400 may be implemented to associate any number of remote control devices with the load control device 306. If the user is done associating remote control devices at 412, the process 400 ends at 414. If the user is not done associating remote control devices and wishes to associate another remote control device at 412, the process 400 may return to 408 and the user may associate another remote control device with the load control device 306 as described herein.
Alternatively, the load control device 306 may be operable to control other types of electrical loads. For example, the load control device 306 may alternatively comprise an electronic dimming ballast for driving a fluorescent lamp; a light-emitting diode (LED) driver for driving an LED light source (e.g., an LED light engine); 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; a dimming circuit for controlling the intensity of an incandescent lamp, a halogen lamp, an electronic low-voltage lighting load, a magnetic low-voltage lighting load, or another type of lighting load; an electronic switch, controllable circuit breaker, or other switching device for turning electrical loads or appliances on and off; a plug-in load control device, controllable electrical receptacle, or controllable power strip for controlling one or more plug-in electrical loads; 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; a thermostat for a heating and/or cooling system; a temperature control device for controlling a heating, ventilation, and air conditioning (HVAC) system; an air conditioner; a compressor; an electric baseboard heater controller; a controllable damper; a humidity control unit; a dehumidifier; a water heater; a pool pump; a TV or computer monitor; an electric charger, such as an electric vehicle charger; and an alternative energy controller (e.g., a solar, wind, or thermal energy controller).
The screw-in controllable luminaire 504 may be operable to receive the RF signals 310 from the remote control 312, the occupancy sensor 314, and/or the daylight sensor 316 for controlling the light source 505. The screw-in controllable luminaire 504 also comprises a button 508 for use in associating remote control devices. For example, the button 508 may be used in associating the remote control 312 with the screw-in controllable luminaire (e.g., in a similar manner as the remote control 312 is associated with the load control device 306 as described herein). The occupancy sensor 314 and/or the daylight sensor 316 may then be indirectly associated with the screw-in controllable luminaire 504 using the remote control 312 (e.g., in a similar manner as the occupancy sensor 314 and the daylight sensor 316 are indirectly associated with the load control device 306 as described herein).
The motorized window treatment 554 may be operable to receive the RF signals 310 from remote control devices for controlling the position of the cellular shade fabric 555. For example, the motorized window treatment 554 may receive the RF signals 310 the remote control 312, the occupancy sensor 314, and/or the daylight sensor 316. The motor drive unit 558 may comprise a button (not shown) for use in associating the remote control devices with the motorized window treatment 554. For example, the button on the motor drive unit 558 may be used to associate the remote control 312 with the motorized window treatment 554 (e.g., in a similar manner as the remote control 312 is associated with the load control device 306 as described herein). The occupancy sensor 314 and/or the daylight sensor 316 may then be indirectly associated with the motorized window treatment 554 using the remote control 312 (e.g., in a similar manner as the occupancy sensor 314 and the daylight sensor 316 are indirectly associated with the load control device 306 as described herein).
The load control device 602 may include a radio-frequency (RF) communication circuit for receiving digital messages via RF signals 310 from the remote control 604. The RF communication circuit may include an RF receiver or RF transceiver, for example, capable of receiving the digital messages via the RF signals 310. The digital messages from the remote control 604 may include association messages for directly associating the remote control 604 or indirectly associating another remote control device (e.g., the occupancy sensor 606 or the daylight sensor 608). The digital messages from the remote control 604 may also include instructions/settings for controlling the load 304 via the load control device 602. The instructions/settings included in the digital messages may originate directly from the remote control 604 or from another associated remote control device (e.g., the occupancy sensor 606 or the daylight sensor 608). The load control device 602 is operable to control the electrical load 304 in response to the instructions/settings included in the received digital messages.
The remote control 604 includes an RF communication circuit for receiving digital messages from other remote control devices (e.g., the occupancy sensor 606 or the daylight sensor 608) and transmitting digital messages to the load control device 602 via the RF signals 310. The RF communication circuit may include an RF transceiver, for example, capable of transmitting and/or receiving the digital messages via the RF signals 310. Specifically, the remote control 604 is operable to receive digital messages including association information for another remote control device (e.g., the occupancy sensor 606 or the daylight sensor 608) and to transmit the association information to the load control device 602 to associate the other remote control device (e.g., the occupancy sensor 606 or the daylight sensor 608). The remote control 604 may also receive digital messages from another remote control device (e.g., the occupancy sensor 606 or the daylight sensor 608) that include instructions/settings for controlling the electrical load 304 and transmit digital messages including the received instructions/settings to the load control device 602 for controlling the electrical load 304.
As shown in
The associated first remote control device (e.g., the remote control 604) may be used to indirectly associate another remote control device (e.g., the occupancy sensor 606 or the daylight sensor 608) with the load control device 602, at 708. For example, the user may actuate one or more buttons on the first remote control device (e.g., one or more of the predetermined buttons 318-326 on the remote control 604) to transmit an association message to the load control device 602, causing the load control device 602 to automatically enter an association mode. While the load control device 602 is in the association mode, the user may actuate a button on a second remote control device (e.g., button 338 on the occupancy sensor 606 or button 340 on the daylight sensor 608), such that the second remote control device (e.g., the occupancy sensor 606 or the daylight sensor 608) transmits association information to the load control device 602 indirectly via the first remote control device (e.g., the remote control 604).
As a result of the association of the second remote control device (e.g., the occupancy sensor 606 or the daylight sensor 608), at 708, instructions/settings from the second remote control device (e.g., the occupancy sensor 606 or the daylight sensor 608) may be used by the load control device 602 for controlling the load 304. Thus, the second remote control device (e.g., the occupancy sensor 606 or the daylight sensor 608) may be used to indirectly control the load control device 602 via the first remote control device (e.g., the remote control 604), at 710. For example, the first remote control device (e.g., the remote control 604) may receive instructions/settings for controlling the load 304 from the second remote control device (e.g., the occupancy sensor 606 or the daylight sensor 608) and the first remote control device (e.g., the remote control 604) may forward the instructions/settings to the load control device 602. The load control device 602 may be responsive to messages received directly from the first remote control device (e.g., the remote control 604) that contain instructions/settings for controlling the load 304 from the second remote control device (e.g., the occupancy sensor 606 or the daylight sensor 608). The messages that include the instructions/settings for controlling the load 304 may also include the unique identifier (e.g., serial number) of the first remote control device (e.g., the remote control 604) from which the message is sent and/or the unique identifier (e.g., serial number) of the second remote control device (e.g., the occupancy sensor 606 or the daylight sensor 608) from which the instructions/settings originated. The load control device 602 may use the received unique identifier(s) to determine that the instructions/settings for controlling the load 304 are received from an associated remote control device.
The process 700 may be implemented to associate any number of remote control devices with the load control device 602. If the user is done associating remote control devices at 712, the process 700 ends at 714. If the user is not done associating remote control devices and wishes to associate another remote control device at 712, the process 700 may return to 708 and the user may associate another remote control device with the load control device 602 as described herein.
In an alternative embodiment, the second remote control device need not be associated with the load control device 602, as illustrated at 708, for example. Instead, the second remote control device may transmit instructions/setting for controlling the load 304 to the first remote control device and, because the first remote control device is already associated with the load control device 602, the first remote control device may forward the instructions/settings on as if they originated at the first remote control device. For example, the instructions/settings may be transmitted from the first remote control device in a message that includes the unique identifier (e.g., serial number) of the first remote control device.
The controller 802 may also control light-emitting diodes 810, which may be mounted on the printed circuit board. The light emitting diodes 810 may be arranged to illuminate status indicators on the front surface of the remote control 312, 604, for example, through a light pipe structure (not shown). The controller 802 may also be coupled to a memory 804 for storage and/or retrieval of unique identifiers (e.g., serial numbers) of the remote control 312, 604, instructions/settings for controlling the electrical load 304, programming instructions for communicating via a wireless communication link, and/or the like. The memory 804 may be implemented as an external integrated circuit (IC) or as an internal circuit of the controller 802. A battery 814, or other power supply for example, may generate a direct-current (DC) voltage VBATT for powering the controller 802, the memory 804, and other low-voltage circuitry of the remote control 312, 604.
The remote control 312, 604 further includes an RF communication circuit 806 for transmitting and/or receiving the RF signals 310. The RF communication circuit 806 may include an RF transmitter, an RF receiver, and/or an RF transceiver, for example. In an example, the RF communication circuit 806 may be used to receive RF signals 310 from another remote control device and/or transmit RF signals 310 to the load control device 306, 602. The RF communication circuit 806 may be configured to communicate via a Wi-Fi communication link, a Wi-MAX communication link, RF signals according to a proprietary RF communication protocol (e.g., Clear Connect™ protocol), and/or a Bluetooth® communication link. The RF communication circuit 806 may receive instructions/setting from the controller 802 and may transmit the instructions/settings, via the RF antenna 808.
The controller 802 may be capable of receiving and processing messages from the RF communication circuit 806. The controller 802 may also be capable of processing messages and sending them to the RF communication circuit 806 for transmission. Information in the messages received by the controller 802 from the RF communication circuit 806 may be stored in the memory 804. For example, the controller 802 may store association information and/or instructions/settings received from another remote control device in the memory 804 and may access the stored association information and/or instructions/settings for transmitting them to the load control device 306, 602 via the RF communication circuit 806.
The load control device 306, 602 may further include a controller 902 coupled to the drive circuit 908 for rendering the controllably conductive device 904 conductive or non-conductive to thus control the power delivered to the electrical load 304. The controller 902 may include a microcontroller, a programmable logic device (PLD), a microprocessor, an application specific integrated circuit (ASIC), a field-programmable gate array (FPGA), or any suitable processing device or control circuit. A zero-crossing detector 910 may determine the zero-crossings of the input AC waveform from the AC power supply 302. A zero-crossing may be the time at which the AC supply voltage transitions from positive to negative polarity, or from negative to positive polarity, at the beginning of each half-cycle. The controller 902 may receive the zero-crossing information from the zero-crossing detector 910 and may provide the control inputs to the drive circuit 908 to render the controllably conductive device 904 conductive and non-conductive at predetermined times relative to the zero-crossing points of the AC waveform.
The controller 902 may receive inputs from a mechanical actuator 308 (e.g., button, switch, etc.) that is mounted on a printed circuit board (not shown) of the load control device 306, 602. The controller 902 may also be coupled to a memory 912 for storage and/or retrieval of unique identifiers (e.g., serial numbers) of remote control devices, instructions/settings for controlling the electrical load 304, programming instructions for communicating via a wireless communication link, and/or the like. The memory 912 may be implemented as an external integrated circuit (IC) or as an internal circuit of the controller 902. A power supply 906 may generate a direct-current (DC) voltage VCC for powering the controller 902, the memory 912, and other low-voltage circuitry of the load control device 306, 602.
The load control device 306, 602 may further include an RF communication circuit 914 coupled to an antenna 916 for communicating via the RF signals 310. The RF communication circuit 914 may include an RF receiver capable of simply receiving the RF signals 310, and/or an RF transceiver capable of transmitting and/or receiving RF signals 310, for example. The RF communication circuit 914 may be configured to communicate via a Wi-Fi communication link, a Wi-MAX communication link, RF signals according to a proprietary RF communication protocol (e.g., Clear Connect™ protocol), and/or a Bluetooth® communication link. The RF communication circuit 914 may transmit and/or receive the RF signals 310 via the antenna 916. Examples of antennas for wall-mounted load control devices are described in greater detail in U.S. Pat. No. 5,982,103, issued Nov. 9, 1999, and U.S. Pat. No. 7,362,285, issued Apr. 22, 2008, both entitled COMPACT RADIO FREQUENCY TRANSMITTING AND RECEIVING ANTENNA AND CONTROL DEVICE EMPLOYING SAME, the entire disclosures of which are hereby incorporated by reference.
Before the remote control 312, 604 and the mounting structure 1006 are mounted to the wallbox 1008, for example, during installation of the load control system 300, 600, the remote control 312, 604 may be associated with the in-wall load control device 306, 602 as described herein. For example, a user may actuate the button 308 on the in-wall load control device 306, 602 to cause the in-wall load control device 306, 602 to enter an association mode. While the in-wall load control device 306, 602 is in the association mode, the user may actuate a predetermined one or more of the buttons 318-326 of the remote control 312, 604, such that the remote control 312, 604 transmits an association message to the in-wall load control device 306, 602. The in-wall load control device 306, 602 may use the information in the association message to associate the remote control 312, 604 with the in-wall load control device 306, 602. For example, the association message may include a unique identifier (e.g., a serial number) of the remote control 312, 604, which the in-wall load control device 306, 602 may store for association. Each digital message transmitted by the remote control 312, 604 for controlling operation of the in-wall load control device 306, 602 may include the unique identifier (e.g., serial number) of the remote control 312, 604. After association, the in-wall load control device 306, 602 may be responsive to messages containing the unique identifier (e.g., serial number) of the remote control 312, 604.
After the remote control 312, 604 is associated with the in-wall load control device 306, 602, the remote control 312, 604 and the mounting structure 1006 may be mounted to the wallbox 1008 and the user may actuate one or more of the buttons 318-326 of the remote control 312, 604 to further configure the load control system 300, 600 as described herein. In other words, the remote control 312, 604 may operate as a master control for the in-wall load control device 306, 602 to allow for configuration of the in-wall load control device 306, 602 while the in-wall load control device 306, 602 is installed in the wallbox 1008 and may be inaccessible to the user.
Rather than being installed in the electrical wallbox 1008, the in-wall load control device 306, 602 could alternatively be installed in an electrical closet, or mounted to a junction box, above a ceiling, or flush to a wall. In addition, the remote control 312, 604 could be mounted flush to a wall or implemented as a tabletop or handheld device.
The remote control 1108 may be charged via energy derived from the inductive coupling of the inductive coils 1104, 1106. For example, the remote control 1108 may include a battery 814 or other power source (not shown in
The inductive coils 1106 may also be used, with the battery charging circuit 1202 for example, to charge the battery 814. The inductive coils 1106 may transmit energy received via inductive coupling to the battery charging circuit 1202. The battery charging circuit 1202 may use the energy received from the inductive coils 1106 to charge the battery 814 for powering the controller 802, the RF communication circuit 806, and other low voltage circuitry of the remote control 1108. In an alternative embodiment in which the remote control 1108 is entirely powered from the inductive coupling of the inductive coils 1106 with the inductive coils 1104 of the load control device 1102, the remote control 1108 may not include a battery 814. For example, the inductive coils 1106 of the remote control 1108 may be housed in an enclosure (not shown) that may be approximately the same size as the battery 814 of the remote control 1108, for example, and may be adapted to be installed in the battery compartment of the remote control 1108 to thus power the controller 802, the RF communication circuit 806, and other low voltage circuitry of the remote control 1108.
The remote controls described herein may alternatively be operable to charge the battery 814 from energy derived from radio-frequency (RF) signals received by the RF communication circuit 806, for example, as described in U.S. Pat. No. 7,812,771, issued Oct. 12, 2010, entitled METHOD AND APPARATUS FOR IMPLEMENTATION OF A WIRELESS POWER SUPPLY, the entire disclosure of which is hereby incorporated by reference.
The remote control 1408 may be charged via energy derived from the NFC signals 1410. For example, the remote control 1408 may include a battery 814 or other power source (not shown in
The NFC module 1502 may also be used, with the battery charging circuit 1504 for example, to charge the battery 814. The NFC module 1502 may transmit energy received via the NFC signals 1410 to the battery charging circuit 1504. The battery charging circuit 1504 may use the energy from the NFC module 1502 to charge the battery 814 for powering the controller 802, the RF communication circuit 806, and other low voltage circuitry of the remote control 1408. In an alternative embodiment in which the remote control 1408 is entirely powered by the energy received via the NFC signals 1410, the remote control 1408 may not include a battery 814. For example, the NFC module 1502 of the remote control 1408 may be housed in an enclosure (not shown) that may be approximately the same size as the battery 814 of the remote control 1408, for example, and may be adapted to be installed in the battery compartment of the remote control 1408 to thus power the controller 802, the RF communication circuit 806, and other low voltage circuitry of the remote control 1408.
This application is a continuation of U.S. patent application Ser. No. 16/813,148, filed Mar. 9, 2020; which is a continuation of U.S. patent application Ser. No. 15/150,496, filed May 10, 2016, now U.S. Pat. No. 10,587,147 issued Mar. 10, 2020, which is a continuation of U.S. patent application Ser. No. 13/598,522, filed Aug. 29, 2012, now U.S. Pat. No. 9,368,025 issued on Jun. 14, 2016, all of which claim the benefit of commonly assigned Provisional U.S. Patent Application Ser. No. 61/528,492, filed on Aug. 29, 2011, the disclosures of each of which are hereby incorporated by reference herein in their entireties. This application is related to commonly assigned U.S. patent application Ser. No. 13/598,529, filed Aug. 29, 2012, entitled TWO-PART LOAD CONTROL SYSTEM MOUNTABLE TO A SINGLE ELECTRICAL WALLBOX, the disclosure of which is hereby incorporated by reference herein in its entirety.
Number | Name | Date | Kind |
---|---|---|---|
4864588 | Simpson et al. | Sep 1989 | A |
4932037 | Simpson et al. | Jun 1990 | A |
4995053 | Simpson et al. | Feb 1991 | A |
5239205 | Hoffman et al. | Aug 1993 | A |
5264761 | Johnson | Nov 1993 | A |
5340954 | Hoffman et al. | Aug 1994 | A |
5454077 | Cheron | Sep 1995 | A |
5488571 | Jacobs et al. | Jan 1996 | A |
5519704 | Farinacci et al. | May 1996 | A |
5602540 | Spillman, Jr. | Feb 1997 | A |
5627863 | Aslanis et al. | May 1997 | A |
5637930 | Rowen et al. | Jun 1997 | A |
5637964 | Hakkarainen et al. | Jun 1997 | A |
5736965 | Mosebrook et al. | Apr 1998 | A |
5812819 | Rodwin et al. | Sep 1998 | A |
5818128 | Hoffman et al. | Oct 1998 | A |
5838226 | Houggy et al. | Nov 1998 | A |
5848054 | Mosebrook et al. | Dec 1998 | A |
5905442 | Mosebrook et al. | May 1999 | A |
5982103 | Mosebrook et al. | Nov 1999 | A |
6167464 | Kretschmann | Dec 2000 | A |
6169377 | Byrde et al. | Jan 2001 | B1 |
6300727 | Bryde et al. | Oct 2001 | B1 |
6324089 | Symoen et al. | Nov 2001 | B1 |
6380696 | Sembhi et al. | Apr 2002 | B1 |
6437692 | Petite et al. | Aug 2002 | B1 |
6526581 | Edson | Feb 2003 | B1 |
6545434 | Sembhi et al. | Apr 2003 | B2 |
6687487 | Mosebrook et al. | Feb 2004 | B1 |
6803728 | Balasubramaniam et al. | Oct 2004 | B2 |
6807463 | Cunningham et al. | Oct 2004 | B1 |
6831569 | Wang et al. | Dec 2004 | B2 |
6856236 | Christensen et al. | Feb 2005 | B2 |
6859644 | Wang | Feb 2005 | B2 |
6876295 | Lewis | Apr 2005 | B1 |
6879806 | Shorty | Apr 2005 | B2 |
6891838 | Petite et al. | May 2005 | B1 |
6903650 | Murray | Jun 2005 | B2 |
6914533 | Petite | Jul 2005 | B2 |
6914893 | Petite | Jul 2005 | B2 |
6927547 | Walko et al. | Aug 2005 | B2 |
6980080 | Christensen et al. | Dec 2005 | B2 |
7035270 | Moore, Jr. et al. | Apr 2006 | B2 |
7053767 | Petite et al. | May 2006 | B2 |
7085627 | Bamberger et al. | Aug 2006 | B2 |
7089066 | Hesse et al. | Aug 2006 | B2 |
7102502 | Autret | Sep 2006 | B2 |
7103511 | Petite | Sep 2006 | B2 |
7106261 | Nagel et al. | Sep 2006 | B2 |
7126291 | Kruse et al. | Oct 2006 | B2 |
7211968 | Adamson et al. | May 2007 | B2 |
7218998 | Neale | May 2007 | B1 |
7219141 | Bonasia et al. | May 2007 | B2 |
7307542 | Chandler et al. | Dec 2007 | B1 |
7323991 | Eckert et al. | Jan 2008 | B1 |
7345270 | Jones et al. | Mar 2008 | B1 |
7346016 | Nielsen et al. | Mar 2008 | B2 |
7358927 | Luebke et al. | Apr 2008 | B2 |
7362285 | Webb et al. | Apr 2008 | B2 |
7408525 | Webb et al. | Aug 2008 | B2 |
7498952 | Newman, Jr. | Mar 2009 | B2 |
7525928 | Cutler | Apr 2009 | B2 |
7548216 | Webb et al. | Jun 2009 | B2 |
7573208 | Newman, Jr. | Aug 2009 | B2 |
7573436 | Webb et al. | Aug 2009 | B2 |
7598684 | Lys et al. | Oct 2009 | B2 |
7687744 | Walter et al. | Mar 2010 | B2 |
7697492 | Petite | Apr 2010 | B2 |
7714790 | Feldstein et al. | May 2010 | B1 |
7755505 | Johnson et al. | Jul 2010 | B2 |
7756086 | Petite et al. | Jul 2010 | B2 |
7756097 | Jehara et al. | Jul 2010 | B2 |
7756556 | Patel et al. | Jul 2010 | B2 |
7805134 | Mirza-Baig | Sep 2010 | B2 |
7821160 | Roosli et al. | Oct 2010 | B1 |
7852765 | Neuman et al. | Dec 2010 | B2 |
7853221 | Rodriguez et al. | Dec 2010 | B2 |
7889051 | Billig et al. | Feb 2011 | B1 |
8013732 | Petite et al. | Sep 2011 | B2 |
8031650 | Petite et al. | Oct 2011 | B2 |
8035255 | Kurs | Oct 2011 | B2 |
8146074 | Ito et al. | Mar 2012 | B2 |
8173920 | Altonen et al. | May 2012 | B2 |
8228163 | Cash et al. | Jul 2012 | B2 |
8254838 | Feldstein | Aug 2012 | B2 |
8339247 | Adamson et al. | Dec 2012 | B2 |
8364319 | Roosli | Jan 2013 | B2 |
8368310 | Roosli | Feb 2013 | B1 |
8379564 | Petite et al. | Feb 2013 | B2 |
8396007 | Gonia et al. | Mar 2013 | B2 |
8416074 | Sadwick | Apr 2013 | B2 |
8525372 | Huang | Sep 2013 | B2 |
8548607 | Belz et al. | Oct 2013 | B1 |
8598978 | Knode | Dec 2013 | B2 |
8742686 | Zampini, II et al. | Jun 2014 | B2 |
8792401 | Banks et al. | Jul 2014 | B2 |
8892261 | Hoonhout et al. | Nov 2014 | B2 |
9049753 | Wassel et al. | Jun 2015 | B1 |
9066381 | Valois et al. | Jun 2015 | B2 |
9178369 | Partovi | Nov 2015 | B2 |
9253857 | Van Der Werff | Feb 2016 | B2 |
9288228 | Suumaki | Mar 2016 | B2 |
9368025 | Carmen, Jr. | Jun 2016 | B2 |
9413171 | Neyhart | Aug 2016 | B2 |
9445482 | Brochu et al. | Sep 2016 | B2 |
9445485 | Reed | Sep 2016 | B2 |
9548797 | Green et al. | Jan 2017 | B1 |
9641959 | Brochu et al. | May 2017 | B2 |
9766645 | Imes et al. | Sep 2017 | B2 |
9767249 | Belz et al. | Sep 2017 | B1 |
10019047 | Bull | Jul 2018 | B2 |
10050444 | Neyhart | Aug 2018 | B2 |
10135629 | Browne, Jr. et al. | Nov 2018 | B2 |
10244086 | Newman, Jr. et al. | Mar 2019 | B2 |
10271407 | Pessina et al. | Apr 2019 | B2 |
10314132 | Wilde | Jun 2019 | B1 |
10516546 | Browne et al. | Dec 2019 | B2 |
10587147 | Carmen, Jr. | Mar 2020 | B2 |
10588204 | Pessina et al. | Mar 2020 | B2 |
10693558 | Economy | Jun 2020 | B2 |
20010024164 | Kawamura et al. | Sep 2001 | A1 |
20020043938 | Lys | Apr 2002 | A1 |
20020060530 | Sembhi et al. | May 2002 | A1 |
20020073183 | Yoon et al. | Jun 2002 | A1 |
20020087436 | Guthrie et al. | Jul 2002 | A1 |
20020113909 | Sherwood | Aug 2002 | A1 |
20020154025 | Ling | Oct 2002 | A1 |
20030034898 | Shamoon et al. | Feb 2003 | A1 |
20030040813 | Gonzales et al. | Feb 2003 | A1 |
20030109270 | Shorty | Jun 2003 | A1 |
20030151493 | Straumann et al. | Aug 2003 | A1 |
20030197993 | Mirowski et al. | Oct 2003 | A1 |
20040036624 | Ballew et al. | Feb 2004 | A1 |
20040052076 | Mueller et al. | Mar 2004 | A1 |
20040058706 | Williamson et al. | Mar 2004 | A1 |
20040059840 | Perego et al. | Mar 2004 | A1 |
20040193998 | Blackburn et al. | Sep 2004 | A1 |
20040217718 | Kumar et al. | Nov 2004 | A1 |
20050030153 | Mullet et al. | Feb 2005 | A1 |
20050045429 | Beker | Mar 2005 | A1 |
20050048944 | Wu | Mar 2005 | A1 |
20050156708 | Puranik et al. | Jul 2005 | A1 |
20050179558 | Williams et al. | Aug 2005 | A1 |
20050253538 | Shah et al. | Nov 2005 | A1 |
20050285547 | Piepgras et al. | Dec 2005 | A1 |
20060027081 | Chang et al. | Feb 2006 | A1 |
20060044152 | Wang | Mar 2006 | A1 |
20060109203 | Huber et al. | May 2006 | A1 |
20060154598 | Rudland et al. | Jul 2006 | A1 |
20060171332 | Barnum | Aug 2006 | A1 |
20060174102 | Smith et al. | Aug 2006 | A1 |
20060192697 | Quick et al. | Aug 2006 | A1 |
20060202851 | Cash et al. | Sep 2006 | A1 |
20060251059 | Otsu et al. | Nov 2006 | A1 |
20060256798 | Quick et al. | Nov 2006 | A1 |
20060273970 | Mosebrook et al. | Dec 2006 | A1 |
20060284734 | Newman, Jr. | Dec 2006 | A1 |
20060285150 | Jung et al. | Dec 2006 | A1 |
20070051529 | Soccoli et al. | Mar 2007 | A1 |
20070083294 | Bruno | Apr 2007 | A1 |
20070085699 | Walters et al. | Apr 2007 | A1 |
20070085700 | Walters et al. | Apr 2007 | A1 |
20070085701 | Walters et al. | Apr 2007 | A1 |
20070085702 | Walters et al. | Apr 2007 | A1 |
20070097993 | Bojahra et al. | May 2007 | A1 |
20070110192 | Steiner | May 2007 | A1 |
20070112939 | Wilson et al. | May 2007 | A1 |
20070121323 | Pawlik et al. | May 2007 | A1 |
20070165997 | Suzuki et al. | Jul 2007 | A1 |
20070176788 | Mor et al. | Aug 2007 | A1 |
20070229300 | Masato et al. | Oct 2007 | A1 |
20080055073 | Raneri et al. | Mar 2008 | A1 |
20080068126 | Johnson et al. | Mar 2008 | A1 |
20080068204 | Carmen et al. | Mar 2008 | A1 |
20080089266 | Orsat | Apr 2008 | A1 |
20080111491 | Spira | May 2008 | A1 |
20080136261 | Mierta | Jun 2008 | A1 |
20080136356 | Zampini et al. | Jun 2008 | A1 |
20080136663 | Courtney et al. | Jun 2008 | A1 |
20080147337 | Walters et al. | Jun 2008 | A1 |
20080148359 | Kezys et al. | Jun 2008 | A1 |
20080183316 | Clayton | Jul 2008 | A1 |
20080192767 | Howe et al. | Aug 2008 | A1 |
20080218099 | Newman | Sep 2008 | A1 |
20080258650 | Steiner et al. | Oct 2008 | A1 |
20080265799 | Sibert | Oct 2008 | A1 |
20080278297 | Steiner et al. | Nov 2008 | A1 |
20080284327 | Kang et al. | Nov 2008 | A1 |
20080297107 | Kato et al. | Dec 2008 | A1 |
20090001941 | Hsu et al. | Jan 2009 | A1 |
20090079268 | Cook et al. | Mar 2009 | A1 |
20090085408 | Bruhn | Apr 2009 | A1 |
20090102296 | Greene | Apr 2009 | A1 |
20090113229 | Cataldo et al. | Apr 2009 | A1 |
20090150004 | Wang et al. | Jun 2009 | A1 |
20090167484 | Burr | Jul 2009 | A1 |
20090206983 | Knode et al. | Aug 2009 | A1 |
20090227205 | Rofougaran | Sep 2009 | A1 |
20090251352 | Altonen et al. | Oct 2009 | A1 |
20090302782 | Smith | Dec 2009 | A1 |
20090315672 | Nantz et al. | Dec 2009 | A1 |
20090322251 | Hilgers | Dec 2009 | A1 |
20100012738 | Park | Jan 2010 | A1 |
20100031076 | Wan et al. | Feb 2010 | A1 |
20100052574 | Blakeley et al. | Mar 2010 | A1 |
20100052576 | Steiner et al. | Mar 2010 | A1 |
20100081375 | Rosenblatt et al. | Apr 2010 | A1 |
20100104255 | Yun et al. | Apr 2010 | A1 |
20100114242 | Doerr et al. | May 2010 | A1 |
20100127821 | Jones et al. | May 2010 | A1 |
20100134341 | Priest | Jun 2010 | A1 |
20100141153 | Recker et al. | Jun 2010 | A1 |
20100207532 | Mans | Aug 2010 | A1 |
20100207759 | Sloan et al. | Aug 2010 | A1 |
20100235008 | Forbes, Jr. et al. | Sep 2010 | A1 |
20100238001 | Veskovic | Sep 2010 | A1 |
20100238003 | Chan et al. | Sep 2010 | A1 |
20100244706 | Steiner et al. | Sep 2010 | A1 |
20100262296 | Davis et al. | Oct 2010 | A1 |
20100289430 | Stelzer et al. | Nov 2010 | A1 |
20100303099 | Rieken | Dec 2010 | A1 |
20110006908 | Frantz | Jan 2011 | A1 |
20110012738 | Nakamura et al. | Jan 2011 | A1 |
20110039137 | Engle et al. | Feb 2011 | A1 |
20110043163 | Baarman | Feb 2011 | A1 |
20110046792 | Imes et al. | Feb 2011 | A1 |
20110062914 | Park et al. | Mar 2011 | A1 |
20110078411 | Maclinovsky et al. | Mar 2011 | A1 |
20110095622 | Feldstein et al. | Apr 2011 | A1 |
20110121654 | Recker et al. | May 2011 | A1 |
20110202910 | Venkatakrishnan et al. | Aug 2011 | A1 |
20110208369 | Yang et al. | Aug 2011 | A1 |
20110244798 | Daigle et al. | Oct 2011 | A1 |
20110244897 | Shibuya | Oct 2011 | A1 |
20110282468 | Ashdown | Nov 2011 | A1 |
20110282495 | Fischer et al. | Nov 2011 | A1 |
20110305200 | Schoofs et al. | Dec 2011 | A1 |
20120018578 | Polcuch | Jan 2012 | A1 |
20120039400 | Rieken | Feb 2012 | A1 |
20120086561 | Ilyes et al. | Apr 2012 | A1 |
20120086562 | Steinberg | Apr 2012 | A1 |
20120091910 | Zhang et al. | Apr 2012 | A1 |
20120093039 | Rofougaran et al. | Apr 2012 | A1 |
20120094658 | Macias et al. | Apr 2012 | A1 |
20120097749 | Lashina | Apr 2012 | A1 |
20120108230 | Stepanian | May 2012 | A1 |
20120158203 | Feldstein | Jun 2012 | A1 |
20120163663 | Masoud et al. | Jun 2012 | A1 |
20120175969 | Maughan et al. | Jul 2012 | A1 |
20120235504 | Kesler et al. | Sep 2012 | A1 |
20120235579 | Chemel et al. | Sep 2012 | A1 |
20120239963 | Smith | Sep 2012 | A1 |
20120254961 | Kim et al. | Oct 2012 | A1 |
20120257543 | Baum et al. | Oct 2012 | A1 |
20120274670 | Lee et al. | Nov 2012 | A1 |
20120275391 | Cui et al. | Nov 2012 | A1 |
20120303768 | Fiennes | Nov 2012 | A1 |
20120306621 | Muthu | Dec 2012 | A1 |
20120315848 | Smith et al. | Dec 2012 | A1 |
20120322370 | Lee | Dec 2012 | A1 |
20120328302 | Iizuka et al. | Dec 2012 | A1 |
20130010018 | Economy | Jan 2013 | A1 |
20130014224 | Graves et al. | Jan 2013 | A1 |
20130026947 | Economy et al. | Jan 2013 | A1 |
20130030589 | Pessina et al. | Jan 2013 | A1 |
20130051375 | Chemishkian et al. | Feb 2013 | A1 |
20130063042 | Bora et al. | Mar 2013 | A1 |
20130073431 | Suro et al. | Mar 2013 | A1 |
20130100855 | Jung et al. | Apr 2013 | A1 |
20130134783 | Mohammediyan et al. | May 2013 | A1 |
20130187563 | Sasai et al. | Jul 2013 | A1 |
20130211844 | Sadwick | Aug 2013 | A1 |
20130223279 | Tinnakornsrisuphap et al. | Aug 2013 | A1 |
20130261821 | Lu et al. | Oct 2013 | A1 |
20130286889 | Cherian et al. | Oct 2013 | A1 |
20130322281 | Ludlow et al. | Dec 2013 | A1 |
20140070919 | Jackson et al. | Mar 2014 | A1 |
20140106735 | Jackson et al. | Apr 2014 | A1 |
20140163742 | Element | Jun 2014 | A1 |
20140163751 | Davis et al. | Jun 2014 | A1 |
20140175875 | Newman, Jr. et al. | Jun 2014 | A1 |
20140177469 | Neyhart | Jun 2014 | A1 |
20140180487 | Bull | Jun 2014 | A1 |
20140277805 | Browne, Jr. et al. | Sep 2014 | A1 |
20140289825 | Chan et al. | Sep 2014 | A1 |
20140304773 | Woods et al. | Oct 2014 | A1 |
20140339913 | Tsuji et al. | Nov 2014 | A1 |
20140375421 | Morrison et al. | Dec 2014 | A1 |
20140375428 | Park | Dec 2014 | A1 |
20150017973 | Gold | Jan 2015 | A1 |
20150097666 | Boyd et al. | Apr 2015 | A1 |
20150200925 | Agerstedt et al. | Jul 2015 | A1 |
20150239353 | Cregut | Aug 2015 | A1 |
20150259078 | Filipovic et al. | Sep 2015 | A1 |
20150342011 | Brochu et al. | Nov 2015 | A1 |
20160011660 | Wieder | Jan 2016 | A1 |
20160119032 | Choi et al. | Apr 2016 | A1 |
20160148449 | God et al. | May 2016 | A1 |
20160149411 | Neyhart | May 2016 | A1 |
20160254699 | Carmen, Jr. | Sep 2016 | A1 |
20160269363 | Southerland | Sep 2016 | A1 |
20160285550 | Economy | Sep 2016 | A1 |
20160352148 | Ichikawa et al. | Dec 2016 | A1 |
20170064798 | Economy et al. | Mar 2017 | A1 |
20170264452 | Vollmer et al. | Sep 2017 | A1 |
20180168019 | Baker et al. | Jun 2018 | A1 |
20180198893 | Newman, Jr. et al. | Jul 2018 | A1 |
20180205460 | Economy | Jul 2018 | A1 |
20180321722 | Bull | Nov 2018 | A1 |
20180324933 | Hammett et al. | Nov 2018 | A1 |
20190006846 | Neyhart | Jan 2019 | A1 |
20190037673 | Pessina et al. | Jan 2019 | A1 |
20200092003 | Economy | Mar 2020 | A1 |
20200195460 | Browne et al. | Jun 2020 | A1 |
Number | Date | Country |
---|---|---|
2892464 | Nov 2015 | CA |
101789978 | Jul 2010 | CN |
102006046489 | Apr 2008 | DE |
102009056152 | Jun 2011 | DE |
0767551 | Aug 2002 | EP |
1727399 | Nov 2006 | EP |
1693991 | Jul 2009 | EP |
2533675 | Jun 2016 | GB |
2011023819 | Feb 2011 | JP |
1999046921 | Sep 1999 | WO |
2001052515 | Jul 2001 | WO |
2001074045 | Oct 2001 | WO |
2002071689 | Sep 2002 | WO |
2001052515 | Oct 2002 | WO |
2002071689 | Nov 2002 | WO |
2003007665 | Jan 2003 | WO |
2004023849 | Mar 2004 | WO |
2004056157 | Jul 2004 | WO |
2006133172 | Dec 2006 | WO |
2007069129 | Jun 2007 | WO |
2008040454 | Apr 2008 | WO |
2008092082 | Jul 2008 | WO |
2008095250 | Aug 2008 | WO |
2009010916 | Jan 2009 | WO |
2010027412 | Mar 2010 | WO |
2010143130 | Dec 2010 | WO |
2011064244 | Jun 2011 | WO |
2018099793 | Jun 2018 | WO |
Entry |
---|
Texas Instruments “CC3000 smart Config” Available at http://processors.wiki.ti.com/index.php/CC3000_Smart_Config retrieved in Feb. 2, 2016, pp. 1-5. |
U.S. Appl. No. 16/102,357, filed Aug. 13, 2018. |
U.S. Appl. No. 16/030,310, filed Jul. 9, 2018. |
U.S. Appl. No. 16/113,548, filed Aug. 27, 2018. |
International Patent Application No. PCT/US2012/045067, International Search Report dated Oct. 29, 2012, 6 pages. |
International Patent Application No. PCT/US2012/045114, International Search Report dated Oct. 24, 2012, 5 pages. |
International Patent Application No. PCT/US2012/45096, International Search Report dated Apr. 2, 2013, 8 pages. |
“CEDIA 2012: Crestron Demos Home Technology Control Solution with NFC-Enabled Mobile Device” Available at http://www.youtube.com/watch?v=qXwoTJX14BE retrieved on Aug. 13, 2013, Video Provided on CD Media Sep. 8, 2012, pp. 1-2. |
“Crestron NFC Demo at CEDIA Expo 2012” Available at http://www.youtube.com/watch?v=FQ1f5vxwqnl Retrieved on Aug. 13, 2013, Transcript of Video provided on CD Media Sep. 10, 2012, pp. 1-2. |
“SimpleLink CC3000 Boosterpack Jump-Starts the Internet of Things” Available at http://www.youtube.com/watch?v=6kh0gOKMIQc Retrieved on Aug. 13, 2013, Transcript of Video provided on CD Media Jun. 6, 2013, 1 page. |
Black Rich “Clear Connect RF Technology” Lutron Electronics Company Inc., Aug. 2009, 16 pages. |
Grade Lisa “PalmOne Treo 600 Palm OS Smartphone from Sprint PCS” Oct. 28, 2013, Mobile Tech Review Document Available at: http://www.mobiletechreview.com/treo_600.htm, Retrieved on May 21, 2013, 4 pages. |
Grade Lisa “PalmOne Treo 650 Palm OS Smartphone: CDMA (Sprint) and GSM Versions” Dec. 10, 2004 Mobile Tech Review Document Available at: http://mobiletechreview.com/treo_650.htm, Retrieved on May 21, 2013, 6 pages. |
JSJSDesigns PLC “JS JS Products” Available at: http://www.jsjsdesigns.com/product.html, Nov. 11, 2010, 4 pages. |
Myers Dana “SimpleLink Wi-Fi CC3000-First Time Config Using PC” Available at http://www.youtube.com/watch?v=10U4NTgkLs Retrieved on Aug. 13, 2013, Transcript of Video provided on CD Media Dec. 18, 2012, pp. 1-2. |
Myers Dana “SimpleLink Wi-Fi CC3000-First Time Config with Smartphone” Available at http://www.youtube.com/watch?v=fxP9hnZysgo Retrieved on Aug. 13, 2013, Transcript of Video provided on CD Media Sep. 19, 2012, pp. 1-2. |
Rustybrick Inc. “iPhone 4 Morse Code Transmission App” Available at http://www.rustybrink.com/iphone-morse-code.php, Jan. 4, 2011, 3 pages. |
U.S. Appl. No. 16/715,507, filed Dec. 16, 2019. |
U.S. Appl. No. 16/813,022, filed Mar. 9, 2020. |
Number | Date | Country | |
---|---|---|---|
20220095437 A1 | Mar 2022 | US |
Number | Date | Country | |
---|---|---|---|
61528492 | Aug 2011 | US |
Number | Date | Country | |
---|---|---|---|
Parent | 16813148 | Mar 2020 | US |
Child | 17544286 | US | |
Parent | 15150496 | May 2016 | US |
Child | 16813148 | US | |
Parent | 13598522 | Aug 2012 | US |
Child | 15150496 | US |