Battery-operated wireless zone controllers having multiple states of power-related operation

Description

BACKGROUND OF THE INVENTION

1. Field of the Invention

The present invention relates to a system and method for directing heating and cooling air from an air handler to various zones in a home or commercial structure.

2. Description of the Related Art

Most traditional home heating and cooling systems have one centrally-located thermostat that controls the temperature of the entire house. The thermostat turns the Heating, Ventilating, and Air-Conditioner (HVAC) system on or off for the entire house. The only way the occupants can control the amount of HVAC air to each room is to manually open and close the register vents throughout the house.

Zoned HVAC systems are common in commercial structures, and zoned systems have been making inroads into the home market. In a zoned system, sensors in each room or group of rooms, or zones, monitor the temperature. The sensors can detect where and when heated or cooled air is needed. The sensors send information to a central controller that activates the zoning system, adjusting motorized dampers in the ductwork and sending conditioned air only to the zone in which it is needed. A zoned system adapts to changing conditions in one area without affecting other areas. For example, many two-story houses are zoned by floor. Because heat rises, the second floor usually requires more cooling in the summer and less heating in the winter than the first floor. A non-zoned system cannot completely accommodate this seasonal variation. Zoning, however, can reduce the wide variations in temperature between floors by supplying heating or cooling only to the space that needs it.

A zoned system allows more control over the indoor environment because the occupants can decide which areas to heat or cool and when. With a zoned system, the occupants can program each specific zone to be active or inactive depending on their needs. For example, the occupants can set the bedrooms to be inactive during the day while the kitchen and living areas are active.

A properly zoned system can be up to 30 percent more efficient than a non-zoned system. A zoned system supplies warm or cool air only to those areas that require it. Thus, less energy is wasted heating and cooling spaces that are not being used.

In addition, a zoned system can sometimes allow the installation of smaller capacity equipment without compromising comfort. This reduces energy consumption by reducing wasted capacity.

Unfortunately, the equipment currently used in a zoned system is relatively expensive. Moreover, installing a zoned HVAC system, or retrofitting an existing system, is far beyond the capabilities of most homeowners. Unless the homeowner has specialized training, it is necessary to hire a specially-trained professional HVAC technician to configure and install the system. This makes zoned HVAC systems expensive to purchase and install. The cost of installation is such that even though the zoned system is more efficient, the payback period on such systems is many years. Such expense has severely limited the growth of zoned HVAC systems in the general home market.

BRIEF DESCRIPTION OF THE INVENTION

The system and method disclosed herein solves these and other problems by providing an Electronically-Controlled Register vent (ECRV) that can be easily installed by a homeowner or general handyman. The ECRV can be used to convert a non-zoned HVAC system into a zoned system. The ECRV can also be used in connection with a conventional zoned HVAC system to provide additional control and additional zones not provided by the conventional zoned HVAC system. In one embodiment, the ECRV is configured have a size and form-factor that conforms to a standard manually-controlled register vent. The ECRV can be installed in place of a conventional manually-controlled register vent—often without the use of tools.

In one embodiment, the ECRV is a self-contained zoned system unit that includes a register vent, a power supply, a thermostat, and a motor to open and close the register vent. To create a zoned HVAC system, the homeowner can simply remove the existing register vents in one or more rooms and replace the register vents with the ECRVs. The occupants can set the thermostat on the EVCR to control the temperature of the area or room containing the ECRV. In one embodiment, the ECRV includes a display that shows the programmed setpoint temperature. In one embodiment, the ECRV includes a display that shows the current setpoint temperature. In one embodiment, the ECRV includes a remote control interface to allow the occupants to control the ECRV by using a remote control. In one embodiment, the remote control includes a display that shows the programmed temperature and the current temperature. In one embodiment, the remote control shows the battery status of the ECRV.

In one embodiment, the EVCR includes a pressure sensor to measure the pressure of the air in the ventilation duct that supplies air to the EVCR. In one embodiment, the EVCR opens the register vent if the air pressure in the duct exceeds a specified value. In one embodiment, the pressure sensor is configured as a differential pressure sensor that measures the difference between the pressure in the duct and the pressure in the room.

In one embodiment, the ECRV is powered by an internal battery. A battery-low indicator on the ECRV informs the homeowner when the battery needs replacement. In one embodiment, one or more solar cells are provided to recharge the batteries when light is available. In one embodiment, the register vent include a fan to draw additional air from the supply duct in order to compensate for undersized vents or zones that need additional heating or cooling air.

In one embodiment, one or more ECRVs in a zone communicate with a zone thermostat. The zone thermostat measures the temperature of the zone for all of the ECRVs that control the zone. In one embodiment, the ECRVs and the zone thermostat communicate by wireless communication methods, such as, for example, infrared communication, radio-frequency communication, ultrasonic communication, etc. In one embodiment, the ECRVs and the zone thermostat communicate by direct wire connections. In one embodiment, the ECRVs and the zone thermostat communicate using powerline communication.

In one embodiment, one or more zone thermostats communicate with a central controller.

In one embodiment, the EVCR and/or the zoned thermostat includes an occupant sensor, such as, for example, an infrared sensor, motion sensor, ultrasonic sensor, etc. The occupants can program the EVCR or the zoned thermostat to bring the zone to different temperatures when the zone is occupied and when the zone is empty. In one embodiment, the occupants can program the EVCR or the zoned thermostat to bring the zone to different temperatures depending on the time of day, the time of year, the type of room (e.g. bedroom, kitchen, etc.), and/or whether the room is occupied or empty. In one embodiment, various EVCRs and/or zoned thermostats thought a composite zone (e.g., a group of zones such as an entire house, an entire floor, an entire wing, etc.) intercommunicate and change the temperature setpoints according to whether the composite zone is empty or occupied.

In one embodiment, the home occupants can provide a priority schedule for the zones based on whether the zones are occupied, the time of day, the time of year, etc. Thus, for example, if zone corresponds to a bedroom and zone corresponds to a living room, zone can be given a relatively lower priority during the day and a relatively higher priority during the night. As a second example, if zone corresponds to a first floor, and zone corresponds to a second floor, then zone can be given a higher priority in summer (since upper floors tend to be harder to cool) and a lower priority in winter (since lower floors tend to be harder to heat). In one embodiment, the occupants can specify a weighted priority between the various zones.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 shows a home with zoned heating and cooling.

FIG. 2 shows one example of a conventional manually-controlled register vent.

FIG. 3A is a front view of one embodiment of an electronically-controlled register vent.

FIG. 3B is a rear view of the electronically-controlled register vent shown in FIG. 3A.

FIG. 4 is a block diagram of a self-contained ECRV.

FIG. 5 is a block diagram of a self-contained ECRV with a remote control.

FIG. 6 is a block diagram of a locally-controlled zoned heating and cooling system wherein a zone thermostat controls one or more ECRVs.

FIG. 7A is a block diagram of a centrally-controlled zoned heating and cooling system wherein the central control system communicates with one or more zone thermostats and one or more ECRVs independently of the HVAC system.

FIG. 7B is a block diagram of a centrally-controlled zoned heating and cooling system wherein the central control system communicates with one or more zone thermostats and the zone thermostats communicate with one or more ECRVs.

FIG. 8 is a block diagram of a centrally-controlled zoned heating and cooling system wherein a central control system communicates with one or more zone thermostats and one or more ECRVs and controls the HVAC system.

FIG. 9 is a block diagram of an efficiency-monitoring centrally-controlled zoned heating and cooling system wherein a central control system communicates with one or more zone thermostats and one or more ECRVs and controls and monitors the HVAC system.

FIG. 10 is a block diagram of an ECRV for use in connection with the systems shown in FIGS. 6-9.

FIG. 11 is a block diagram of a basic zone thermostat for use in connection with the systems shown in FIGS. 6-9.

FIG. 12 is a block diagram of a zone thermostat with remote control for use in connection with the systems shown in FIGS. 6-9.

FIG. 13 shows one embodiment of a central monitoring system.

FIG. 14 is a flowchart showing one embodiment of an instruction loop for an ECRV or zone thermostat.

FIG. 15 is a flowchart showing one embodiment of an instruction and sensor data loop for an ECRV or zone thermostat.

FIG. 16 is a flowchart showing one embodiment of an instruction and sensor data reporting loop for an ECRV or zone thermostat.

FIG. 17 shows an ECRV configured to be used in connection with a conventional T-bar ceiling system found in many commercial structures.

FIG. 18 shows an ECRV configured to use a scrolling curtain to control airflow as an alternative to the vanes shown in FIGS. 2 and 3.

FIG. 19 is a block diagram of a control algorithm for controlling the register vents.

DETAILED DESCRIPTION OF THE INVENTION

FIG. 1 shows a home 100 with zoned heating and cooling. In the home 100, an HVAC system provides heating and cooling air to a system of ducts. Sensors 101-105 monitor the temperature in various areas (zones) of the house. A zone can be a room, a floor, a group of rooms, etc. The sensors 101-105 detect where and when heating or cooling air is needed. Information from the sensors 101-105 is used to control actuators that adjust the flow of air to the various zones. The zoned system adapts to changing conditions in one area without affecting other areas. For example, many two-story houses are zoned by floor. Because heat rises, the second floor usually requires more cooling in the summer and less heating in the winter than the first floor. A non-zoned system cannot completely accommodate this seasonal variation. Zoning, however, can reduce the wide variations in temperature between floors by supplying heating or cooling only to the space that needs it.

FIG. 2 shows one example of a conventional manually-controlled register vent 200. The register 200 includes one or more vanes 201 that can be opened or closed to adjust the amount of air that flows through the register 200. Diverters 202 direct the air in a desired direction (or directions). The vanes 201 are typically provided to a mechanical mechanism so that the occupants can manipulate the vanes 201 to control the amount of air that flows out of the register 200. In some registers, the diverters 202 are fixed. In some registers, the diverters 202 are moveable to allow the occupants some control over the direction of the airflow out of the vent. Registers such as the register 200 are found throughout homes that have a central HVAC system that provides heating and cooling air. Typically, relatively small rooms such as bedrooms and bathrooms will have one or two such register vents of varying sizes. Larger rooms, such as living rooms, family rooms, etc., may have more than two such registers. The occupants of a home can control the flow of air through each of the vents by manually adjusting the vanes 201. When the register vent is located on the floor, or relatively low on the wall, such adjustment is usually not particularly difficult (unless the mechanism that controls the vanes 201 is bent or rusted). However, adjustment of the vanes 201 can be very difficult when the register vent 200 is located so high on the wall that it cannot be easily reached.

FIG. 3 shows one embodiment of an Electronically-Controlled Register Vent (ECRV) 300. The ECRV 300 can be used to implement a zoned heating and cooling system. The ECRV 300 can also be used as a remotely control register vent in places where the vent is located so high on the wall that is cannot be easily reached. The ECRV 300 is configured as a replacement for the vent 200. This greatly simplifies the task of retrofitting a home by replacing one or more of the register vents 200 with the ECRVs 300. In one embodiment, shown in FIG. 3, the ECRV 300 is configured to fit into approximately the same size duct opening as the conventional register vent 200. In one embodiment, the ECRV 300 is configured to fit over the duct opening used by the conventional register vent 200. In one embodiment, the ECRV 300 is configured to fit over the conventional register 200, thereby allowing the register 200 to be left in place. A control panel 301 provides one or more visual displays and, optionally, one or more user controls. A housing 302 is provided to house an actuator to control the vanes 201. In one embodiment, the housing 302 can also be used to house electronics, batteries, etc.

FIG. 4 is a block diagram of a self-contained ECRV 400, which is one embodiment of the ECRV 300 shown in FIGS. 3A and 3B and the ECRV shown in FIG. 18. In the ECRV 400, a temperature sensor 406 and a temperature sensor 416 are provided to a controller 401. The controller 401 controls an actuator system 409. In one embodiment, the actuator 409 provides position feedback to the controller 401. In one embodiment, the controller 401 reports actuator position to a central control system and/or zone thermostat. The actuator system 409 provided mechanical movements to control the airflow through the vent. In one embodiment, the actuator system 409 includes an actuator provided to the vanes 201 or other air-flow devices to control the amount of air that flows through the ECRV 400 (e.g., the amount of air that flows from the duct into the room). In one embodiment, an actuator system includes an actuator provided to one or more of the diverters 202 to control the direction of the airflow. The controller 401 also controls a visual display 403 and an optional fan 402. A user input device 408 is provided to allow the user to set the desired room temperature. An optional sensor 407 is provided to the controller 401. In one embodiment, the sensor 407 includes an air pressure and/or airflow sensor. In one embodiment, the sensor 407 includes a humidity sensor. A power source 404 provides power to the controller 401, the fan 402, the display 403, the temperature sensors 406, 416, the sensor 407, and the user input device 408 as needed. In one embodiment, the controller 401 controls the amount of power provided to the fan 402, the display 403, the sensor 406, the sensor 416, the sensor 407, and the user input device 408. In one embodiment, an optional auxiliary power source 405 is also provided to provide additional power. The auxiliary power source is a supplementary source of electrical power, such as, for example, a battery, a solar cell, an airflow (e.g., wind-powered) generator, the fan 402 acting as a generator, a nuclear-based electrical generator, a fuel cell, a thermocouple, etc.

In one embodiment, the power source 404 is based on a non-rechargeable battery and the auxiliary power source 405 includes a solar cell and a rechargeable battery. The controller 401 draws power from the auxiliary power source when possible to conserve power in the power source 404. When the auxiliary power source 405 is unable to provide sufficient power, then the controller 401 also draws power from the power source 404.

In an alternative embodiment, the power source 404 is configured as a rechargeable battery and the auxiliary power source 405 is configured as a solar cell that recharges the power source 404.

In one embodiment, the display 403 includes a flashing indicator (e.g., a flashing LED or LCD) when the available power from the power sources 404 and/or 405 drops below a threshold level.

The home occupants use the user input device 408 to set a desired temperature for the vicinity of the ECRV 400. The display 403 shows the setpoint temperature. In one embodiment, the display 403 also shows the current room temperature. The temperature sensor 406 measures the temperature of the air in the room, and the temperature sensor 416 measures the temperature of the air in the duct. If the room temperature is above the setpoint temperature, and the duct air temperature is below the room temperature, then the controller 401 causes the actuator 409 to open the vent. If the room temperature is below the setpoint temperature, and the duct air temperature is above the room temperature, then the controller 401 causes the actuator 409 to open the vent. Otherwise, the controller 401 causes the actuator 409 to close the vent. In other words, if the room temperature is above or below the setpoint temperature and the temperature of the air in the duct will tend to drive the room temperature towards the setpoint temperature, then the controller 401 opens the vent to allow air into the room. By contrast, if the room temperature is above or below the setpoint temperature and the temperature of the air in the duct will not tend to drive the room temperature towards the setpoint temperature, then the controller 401 closes the vent.

In one embodiment, the controller 401 is configured to provide a few degrees of hysteresis (often referred to as a thermostat deadband) around the setpoint temperature in order to avoid wasting power by excessive opening and closing of the vent.

In one embodiment, the controller 401 turns on the fan 402 to pull additional air from the duct. In one embodiment, the fan 402 is used when the room temperature is relatively far from the setpoint temperature in order to speed the movement of the room temperature towards the setpoint temperature. In one embodiment, the fan 402 is used when the room temperature is changing relatively slowly in response to the open vent. In one embodiment, the fan 402 is used when the room temperature is moving away from the setpoint and the vent is fully open. The controller 401 does not turn on or run the fan 402 unless there is sufficient power available from the power sources 404, 405. In one embodiment, the controller 401 measures the power level of the power sources 404, 405 before turning on the fan 402, and periodically (or continually) when the fan is on.

In one embodiment, the controller 401 also does not turn on the fan 402 unless it senses that there is airflow in the duct (indicating that the HVAC air-handler fan is blowing air into the duct). In one embodiment, the sensor 407 includes an airflow sensor. In one embodiment, the controller 401 uses the fan 402 as an airflow sensor by measuring (or sensing) voltage generated by the fan 402 rotating in response to air flowing from the duct through the fan and causing the fan to act as a generator. In one embodiment, the controller 401 periodically stop the fan and checks for airflow from the duct.

In one embodiment, the sensor 406 includes a pressure sensor configured to measure the air pressure in the duct. In one embodiment, the sensor 406 includes a differential pressure sensor configured to measure the pressure difference between the air in the duct and the air outside the ECRV (e.g., the air in the room). Excessive air pressure in the duct is an indication that too many vents may be closed (thereby creating too much back pressure in the duct and reducing airflow through the HVAC system). In one embodiment, the controller 401 opens the vent when excess pressure is sensed.

The controller 401 conserves power by turning off elements of the ECRV 400 that are not in use. The controller 401 monitors power available from the power sources 404, 405. When available power drops below a low-power threshold value, the controls the actuator 409 to an open position, activates a visual indicator using the display 403, and enters a low-power mode. In the low power mode, the controller 401 monitors the power sources 404, 405 but the controller does not provide zone control functions (e.g., the controller does not close the actuator 409). When the controller senses that sufficient power has been restored (e.g., through recharging of one or more of the power sources 404, 405, then the controller 401 resumes normal operation.

Whistling and other noises related to turbulence can be a problem when air of a certain velocity passes through an orifice or opening In one embodiment, the controller 401 uses the physical parameters of the vent to estimate when airflow through the vent may cause undesirable noises such as whistling and the like. The controller 401 can then avoid relatively small vent openings (e.g., smaller partial openings) of the vent that produce unacceptable noises. Since whistling and other such noises are dependent on how much the vent is open and the air pressure across the vent, the openings that would cause unacceptable noises may vary depending on which other vents in the zone system are open or closed. By using data from the pressure/airflow sensor 407 and the dimensions of the vent, the controller 401 can calculate which settings are likely to produce whistling and other noises at any given time and thus, vary the allowed settings accordingly. In one embodiment, a microphone or other acoustic sensor is provided to the controller 401 such that the controller can sense acoustic noise created by air flowing through the vent. In one embodiment, the controller evaluates the amplitude of the noise detected by the acoustic sensor to determine whether unacceptable noise is being produced. In one embodiment, the controller 401 performs spectral properties of the noise (e.g., by using Fourier transform, wavelet transform, etc.) to determine whether unacceptable noise is being produced. The use of a booster fan in connection with the ECRV increases the possibility of noise. The controller 401 can also use noise estimates or measurements to help determine if a booster fan and/or the allowable speed for the fan.

If too many vents are closed off, then the remaining vents, even when completely open, may cause unacceptable noises. In one embodiment, the controller 401 informs the zone thermostats and/or control systems described below that a vent is producing noise. The zone thermostat and/or control system can then open other vents to reduce the pressure, instruct the blower fan to operate at a lower speed, turn off or reduce the speed of booster fans in the ductwork, etc.

FIG. 5 is a block diagram of a self-contained ECRV 500 with a remote control interface 501. The ECRV 500 includes the power sources 404, 405, the controller 401, the fan 402, the display 403, the temperature sensors 406, 416, the sensor 407, and the user input device 408. The remote control interface 501 is provided to the controller 401, to allow the controller 401 to communicate with a remote control 502. The controller 502 sends wireless signals to the remote control interface 501 using wireless communication such as, for example, infrared communication, ultrasonic communication, and/or radio-frequency communication.

In one embodiment, the communication is one-way, from the remote control 502 to the controller 401. The remote control 502 can be used to set the temperature setpoint, to instruct the controller 401 to open or close the vent (either partially or fully), and/or to turn on the fan. In one embodiment, the communication between the remote control 502 and the controller 401 is two-way communication. Two-way communication allows the controller 401 to send information for display on the remote control 502, such as, for example, the current room temperature, the power status of the power sources 404, 405, diagnostic information, etc.

The ECRV 400 described in connection with FIG. 4, and the ECRV 500 described in connection with FIG. 5 are configured to operate as self-contained devices in a relatively stand-alone mode. If two ECRVs 400, 500 are placed in the same room or zone, the ECRVs 400, 500 will not necessarily operate in unison. FIG. 6 is a block diagram of a locally-controlled zoned heating and cooling system 600 wherein a zone thermostat 601 monitors the temperature of a zone 608. ECRVs 602, 603 are configured to communicate with the zone thermostat 601. One embodiment of the ECRVs 620-603 is shown, for example, in connection with FIG. 10. In one embodiment, the zone thermostat 601 sends control commands to the ECRVs 602-603 to cause the ECRVs 602-603 to open or close. In one embodiment, the zone thermostat 601 sends temperature information to the ECRVs 602-603 and the ECRVs 602-603 determine whether to open or close based on the temperature information received from the zone thermostat 601. In one embodiment, the zone thermostat 601 sends information regarding the current zone temperature and the setpoint temperature to the ECRVs 602-603.

In one embodiment, the ECRV 602 communicates with the ECRV 603 in order to improve the robustness of the communication in the system 600. Thus, for example, if the ECRV 602 is unable to communicate with the zone thermostat 601 but is able to communicate with the ECRV 603, then the ECRV 603 can act as a router between the ECRV 602 and the zone thermostat 601. In one embodiment, the ECRV 602 and the ECRV 603 communicate to arbitrate opening and closing of their respective vents.

The system 600 shown in FIG. 6 provides local control of a zone 608. Any number of independent zones can be controlled by replicating the system 600. FIG. 7A is a block diagram of a centrally-controlled zoned heating and cooling system wherein a central control system 710 communicates with one or more zone thermostats 707708 and one or more ECRVs 702-705. In the system 700, the zone thermostat 707 measures the temperature of a zone 711, and the ECRVs 702, 703 regulate air to the zone 711. The zone thermostat 708 measures the temperature of a zone 712, and the ECRVs 704, 705 regulate air to the zone 711. A central thermostat 720 controls the HVAC system 720.

FIG. 7B is a block diagram of a centrally-controlled zoned heating and cooling system 750 that is similar to the system 700 shown in FIG. 7A. In FIG. 7B, the central system 710 communicates with the zone thermostats 707, 708, the zone thermostat 707 communicates with the ECRVs 702, 703, the zone thermostat 708 communicates with the ECRVs 704, 705, and the central system 710 communicates with the ECRVs 706, 707. In the system 750, the ECRVs 702-705 are in zones that are associated with the respective zone thermostat 707, 708 that controls the respective ECRVs 702-705. The ECRVs 706, 707 are not associated with any particular zone thermostat and are controlled directly by the central system 710. One of ordinary skill in the art will recognize that the communication topology shown in FIG. 7B can also be used in connection with the system shown in FIGS. 8 and 9.

The central system 710 controls and coordinates the operation of the zones 711 and 712, but the system 710 does not control the HVAC system 721. In one embodiment, the central system 710 operates independently of the thermostat 720. In one embodiment, the thermostat 720 is provided to the central system 710 so that the central system 710 knows when the thermostat is calling for heating, cooling, or fan.

The central system 710 coordinates and prioritizes the operation of the ECRVs 702-705. In one embodiment, the home occupants and provide a priority schedule for the zones 711, 712 based on whether the zones are occupied, the time of day, the time of year, etc. Thus, for example, if zone 711 corresponds to a bedroom and zone 712 corresponds to a living room, zone 711 can be given a relatively lower priority during the day and a relatively higher priority during the night. As a second example, if zone 711 corresponds to a first floor, and zone 712 corresponds to a second floor, then zone 712 can be given a higher priority in summer (since upper floors tend to be harder to cool) and a lower priority in winter (since lower floors tend to be harder to heat). In one embodiment, the occupants can specify a weighted priority between the various zones.

Closing too many vents at one time is often a problem for central HVAC systems as it reduces airflow through the HVAC system, and thus reduces efficiency. The central system 710 can coordinate how many vents are closed (or partially closed) and thus, ensure that enough vents are open to maintain proper airflow through the system. The central system 710 can also manage airflow through the home such that upper floors receive relatively more cooling air and lower floors receive relatively more heating air.

FIG. 8 is a block diagram of a centrally-controlled zoned heating and cooling system 800. The system 800 is similar to the system 700 and includes the zone thermostats 707, 708 to monitor the zones 711, 712, respectively, and the ECRVs 702-705. The zone thermostats 707, 708 and/or the ECRVs 702-705 communicate with a central controller 810. In the system 800, the thermostat 720 is provided to the central system 810 and the central system 810 controls the HVAC system 721 directly.

The controller 810 provides similar functionality as the controller 710. However, since the controller 810 also controls the operation of the HVAC system 721, the controller 810 is better able to call for heating and cooling as needed to maintain the desired temperature of the zones 711, 712. If all, or substantially, all of the home is served by the zone thermostats and ECRVs, then the central thermostat 720 can be eliminated.

In some circumstances, depending on the return air paths in the house, the controller 810 can turn on the HVAC fan (without heating or cooling) to move air from zones that are too hot to zones that are too cool (or vice versa) without calling for heating or cooling. The controller 810 can also provide for efficient use of the HVAC system by calling for heating and cooling as needed, and delivering the heating and cooling to the proper zones in the proper amounts. If the HVAC system 721 provides multiple operating modes (e.g., high-speed, low-speed, etc.), then the controller 810 can operate the HVAC system 721 in the most efficient mode that provides the amount of heating or cooling needed.

FIG. 9 is a block diagram of an efficiency-monitoring centrally-controlled zoned heating and cooling system 900. The system 900 is similar to the system 800. In the system 900 the controller 810 is replaced by an efficiency-monitoring controller 910 that is configured to receive sensor data (e.g., system operating temperatures, etc.) from the HVAC system 721 to monitor the efficiency of the HVAC system 721.

FIG. 10 is a block diagram of an ECRV 1000 for use in connection with the systems shown in FIGS. 6-9. The ECRV 1000 includes the power sources 404, 405, the controller 401, the fan 402, the display 403, and, optionally the temperature sensors 416 and the sensor 407, and the user input device 408. A communication system 1081 is provided to the controller 401. The remote control interface 501 is provided to the controller 401, to allow the controller 401 to communicate with a remote control 502. The controller 502 sends wireless signals to the remote control interface 501 using wireless communication such as, for example, infrared communication, ultrasonic communication, and/or radio-frequency communication.

The communication system 1081 is configured to communicate with the zone thermometer and, optionally, with the central controllers 710, 810, 910. In one embodiment, the communication system 1081 is configured to communicate using wireless communication such as, for example, infrared communication, radio communication, or ultrasonic communication.

FIG. 11 is a block diagram of a basic zone thermostat 1100 for use in connection with the systems shown in FIGS. 6-9. In the zone thermostat 1100, a temperature sensor 1102 is provided to a controller 1101. User input controls 1103 are also provided to the controller 1101 to allow the user to specify a setpoint temperature. A visual display 1110 is provided to the controller 1101. The controller 1101 uses the visual display 1110 to show the current temperature, setpoint temperature, power status, etc. The communication system 1181 is also provided to the controller 1101. The power source 404 and, optionally, 405 are provided to provide power for the controller 1100, the controls 1101, the sensor 1103, the communication system 1181, and the visual display 1110.

In systems where a central controller 710, 810, 910 is used, the communication method used by the zone thermostat 1100 to communicate with the ECRV 1000 need not be the same method used by the zone thermostat 1100 to communicate with the central controller 710, 810, 910. Thus, in one embodiment, the communication system 1181 is configured to provide one type of communication (e.g., infrared, radio, ultrasonic) with the central controller, and a different type of communication with the ECRV 1000.

In one embodiment, the zone thermostat is battery powered. In one embodiment, the zone thermostat is configured into a standard light switch and receives electrical power from the light switch circuit.

FIG. 12 is a block diagram of a zone thermostat 1200 with remote control for use in connection with the systems shown in FIGS. 6-9. The thermostat 1200 is similar to the thermostat 1100 and includes, the temperature sensor 1102, the input controls 1103, the visual display 1110, the communication system 1181, and the power sources 404, 405. In the zone thermostat 1200, the remote control interface 501 is provided to the controller 1101.

In one embodiment, an occupant sensor 1201 is provided to the controller 1101. The occupant sensor 1201, such as, for example, an infrared sensor, motion sensor, ultrasonic sensor, etc. senses when the zone is occupied. The occupants can program the zone thermostat 1201 to bring the zone to different temperatures when the zone is occupied and when the zone is empty. In one embodiment, the occupants can program the zoned thermostat 1201 to bring the zone to different temperatures depending on the time of day, the time of year, the type of room (e.g. bedroom, kitchen, etc.), and/or whether the room is occupied or empty. In one embodiment, a group of zones are combined into a composite zone (e.g., a group of zones such as an entire house, an entire floor, an entire wing, etc.) and the central system 710, 810, 910 changes the temperature setpoints of the various zones according to whether the composite zone is empty or occupied.

FIG. 13 shows one embodiment of a central monitoring station console 1300 for accessing the functions represented by the blocks 710, 810, 910 in FIGS. 7, 8, 9, respectively. The station 1300 includes a display 1301 and a keypad 1302. The occupants can specify zone temperature settings, priorities, and thermostat deadbands using the central system 1300 and/or the zone thermostats. In one embodiment, the console 1300 is implemented as a hardware device. In one embodiment, the console 1300 is implemented in software as a computer display, such as, for example, on a personal computer. In one embodiment, the zone control functions of the blocks 710, 810, 910 are provided by a computer program running on a control system processor, and the control system processor interfaces with personal computer to provide the console 1300 on the personal computer. In one embodiment, the zone control functions of the blocks 710, 810, 910 are provided by a computer program running on a control system processor provided to a hardware console 1300. In one embodiment, the occupants can use the Internet, telephone, cellular telephone, pager, etc. to remotely access the central system to control the temperature, priority, etc. of one or more zones.

FIG. 14 is a flowchart showing one embodiment of an instruction loop process 1400 for an ECRV or zone thermostat. The process 1400 begins at a power-up block 1401. After power up, the process proceeds to an initialization block 1402. After initialization, the process advances to a “listen” block 1403 wherein the ECRV or zone thermostat listens for one or more instructions. If a decision block 1404 determines that an instruction has been received, then the process advances to a “perform instruction” block 1405, otherwise the process returns to the listen block 1403.

For an ECRV, the instructions can include: open vent, close vent, open vent to a specified partially-open position, report sensor data (e.g., airflow, temperature, etc.), report status (e.g., battery status, vent position, etc.), and the like. For a zone thermostat, the instructions can include: report temperature sensor data, report temperature rate of change, report setpoint, report status, etc. In systems where the central system communicates with the ECRVs through a zone thermostat, the instructions can also include: report number of ECRVs, report ECRV data (e.g., temperature, airflow, etc.), report ECRV vent position, change ECRV vent position, etc.

In one embodiment, the listen block 1403 consumes relatively little power, thereby allowing the ECRV or zone thermostat to stay in the loop corresponding to the listen block 1403 and conditional branch 1404 for extended periods of time.

Although the listen block 1403 can be implemented to use relatively little power, a sleep block can be implemented to use even less power. FIG. 15 is a flowchart showing one embodiment of an instruction and sensor data loop process 1500 for an ECRV or zone thermostat. The process 1500 begins at a power-up block 1501. After power up, the process proceeds to an initialization block 1502. After initialization, the process advances to a “sleep” block 1503 wherein the ECRV or zone thermostat sleeps for a specified period of time. When the sleep period expires, the process advances to a wakeup block 1504 and then to a decision 1505. In the decision block 1505, if a fault is detected, then a transmit fault block 1506 is executed. The process then advances to a sensor block 1507 where sensor readings are taken. After taking sensor readings, the process advances to a listen-for-instructions block 1508. If an instruction has been received, then the process advances to a “perform instruction” block 1510; otherwise, the process returns to the sleep block 1503.

FIG. 16 is a flowchart showing one embodiment of an instruction and sensor data reporting loop process 1600 for an ECRV or zone thermostat. The process 1600 begins at a power-up block 1601. After power up, the process proceeds to an initialization block 1602. After initialization, the process advances to a check fault block 1603. If a fault is detected then a decision block 1604 advances the process to a transmit fault block 1605; otherwise, the process advances to a sensor block 1606 where sensor readings are taken. The data values from one or more sensors are evaluated, and if the sensor data is outside a specified range, or if a timeout period has occurred, then the process advances to a transmit data block 1608; otherwise, the process advances to a sleep block 1609. After transmitting in the transmit fault block 1605 or the transmit sensor data block 1608, the process advances to a listen block 1610 where the ECRV or zone thermostat listens for instructions. If an instruction is received, then a decision block advances the process to a perform instruction block 1612; otherwise, the process advances to the sleep block 1609. After executing the perform instruction block 1612, the process transmits an “instruction complete message” and returns to the listen block 1610.

The process flows shown in FIGS. 14-16 show different levels of interaction between devices and different levels of power conservation in the ECRV and/or zone thermostat. One of ordinary skill in the art will recognize that the ECRV and zone thermostat are configured to receive sensor data and user inputs, report the sensor data and user inputs to other devices in the zone control system, and respond to instructions from other devices in the zone control system. Thus the process flows shown in FIGS. 14-16 are provided for illustrative purposes and not by way of limitation. Other data reporting and instruction processing loops will be apparent to those of ordinary skill in the art by using the disclosure herein.

In one embodiment, the ECRV and/or zone thermostat “sleep,” between sensor readings. In one embodiment, the central system 710 sends out a “wake up” signal. When an ECRV or zone thermostat receives a wake up signal, it takes one or more sensor readings, encodes it into a digital signal, and transmits the sensor data along with an identification code.

In one embodiment, the ECRV is bi-directional and configured to receive instructions from the central system. Thus, for example, the central system can instruct the ECRV to: perform additional measurements; go to a standby mode; wake up; report battery status; change wake-up interval; run self-diagnostics and report results; etc.

In one embodiment, the ECRV provides two wake-up modes, a first wake-up mode for taking measurements (and reporting such measurements if deemed necessary), and a second wake-up mode for listening for commands from the central system. The two wake-up modes, or combinations thereof, can occur at different intervals.

In one embodiment, the ECRVs use spread-spectrum techniques to communicate with the zone thermostats and/or the central system. In one embodiment, the ECRVs use frequency-hopping spread-spectrum. In one embodiment, each ECRV has an Identification code (ID) and the ECRVs attaches its ID to outgoing communication packets. In one embodiment, when receiving wireless data, each ECRV ignores data that is addressed to other ECRVs.

In one embodiment, the ECRV provides bi-directional communication and is configured to receive data and/or instructions from the central system. Thus, for example, the central system can instruct the ECRV to perform additional measurements, to go to a standby mode, to wake up, to report battery status, to change wake-up interval, to run self-diagnostics and report results, etc. In one embodiment, the ECRV reports its general health and status on a regular basis (e.g., results of self-diagnostics, battery health, etc.).

In one embodiment, the ECRV use spread-spectrum techniques to communicate with the central system. In one embodiment, the ECRV uses frequency-hopping spread-spectrum. In one embodiment, the ECRV has an address or identification (ID) code that distinguishes the ECRV from the other ECRVs. The ECRV attaches its ID to outgoing communication packets so that transmissions from the ECRV can be identified by the central system. The central system attaches the ID of the ECRV to data and/or instructions that are transmitted to the ECRV. In one embodiment, the ECRV ignores data and/or instructions that are addressed to other ECRVs.

In one embodiment, the ECRVs, zone thermostats, central system, etc., communicate on a 900 MHz frequency band. This band provides relatively good transmission through walls and other obstacles normally found in and around a building structure. In one embodiment, the ECRVs and zone thermostats communicate with the central system on bands above and/or below the 900 MHz band. In one embodiment, the ECRVs and zone thermostats listen to a radio frequency channel before transmitting on that channel or before beginning transmission. If the channel is in use, (e.g., by another device such as another central system, a cordless telephone, etc.) then the ECRVs and/or zone thermostats change to a different channel. In one embodiment, the sensor, central system coordinates frequency hopping by listening to radio frequency channels for interference and using an algorithm to select a next channel for transmission that avoids the interference. In one embodiment, the ECRV and/or zone thermostat transmits data until it receives an acknowledgement from the central system that the message has been received.

Frequency-hopping wireless systems offer the advantage of avoiding other interfering signals and avoiding collisions. Moreover, there are regulatory advantages given to systems that do not transmit continuously at one frequency. Channel-hopping transmitters change frequencies after a period of continuous transmission, or when interference is encountered. These systems may have higher transmit power and relaxed limitations on in-band spurs.

In one embodiment, the controller 401 reads the sensors 406, 407, 416 at regular periodic intervals. In one embodiment, the controller 401 reads the sensors 406, 407, 416 at random intervals. In one embodiment, the controller 401 reads the sensors 406, 407, 416 in response to a wake-up signal from the central system. In one embodiment, the controller 401 sleeps between sensor readings.

In one embodiment, the ECRV transmits sensor data until a handshaking-type acknowledgement is received. Thus, rather than sleep if no instructions or acknowledgements are received after transmission (e.g., after the instruction block 1510, 1405, 1612 and/or the transmit blocks 1605, 1608) the ECRV retransmits its data and waits for an acknowledgement. The ECRV continues to transmit data and wait for an acknowledgement until an acknowledgement is received. In one embodiment, the ECRV accepts an acknowledgement from a zone thermometer and it then becomes the responsibility of the zone thermometer to make sure that the data is forwarded to the central system. The two-way communication ability of the ECRV and zone thermometer provides the capability for the central system to control the operation of the ECRV and/or zone thermometer and also provides the capability for robust handshaking-type communication between the ECRV, the zone thermometer, and the central system.

In one embodiment of the system 600 shown in FIG. 6, the ECRVs 602, 603 send duct temperature data to the zone thermostat 601. The zone thermostat 601 compares the duct temperature to the room temperature and the setpoint temperature and makes a determination as to whether the ECRVs 602, 603 should be open or closed. The zone thermostat 601 then sends commands to the ECRVs 602, 603 to open or close the vents. In one embodiment, the zone thermostat 601 displays the vent position on the visual display 1110.

In one embodiment of the system 600 shown in FIG. 6, the zone thermostat 601 sends setpoint information and current room temperature information to the ECRVs 602, 603. The ECRVs 602, 603 compare the duct temperature to the room temperature and the setpoint temperature and makes a determination as to whether to open or close the vents. In one embodiment, the ECRVs 602, 603 send information to the zone thermostat 601 regarding the relative position of the vents (e.g., open, closed, partially open, etc.).

In the systems 700, 750, 800, 900 (the centralized systems) the zone thermostats 707, 708 send room temperature and setpoint temperature information to the central system. In one embodiment, the zone thermostats 707, 708 also send temperature slope (e.g., temperature rate of rise or fall) information to the central system. In the systems where the thermostat 720 is provided to the central system or where the central system controls the HVAC system, the central system knows whether the HVAC system is providing heating or cooling; otherwise, the central system used duct temperature information provide by the ECRVs 702-705 to determine whether the HVAC system is heating or cooling. In one embodiment, ECRVs send duct temperature information to the central system. In one embodiment, the central system queries the ECRVs by sending instructions to one or more of the ECRVs 702-705 instructing the ECRV to transmit its duct temperature.

The central system determines how much to open or close ECRVs 702-705 according to the available heating and cooling capacity of the HVAC system and according to the priority of the zones and the difference between the desired temperature and actual temperature of each zone. In one embodiment, the occupants use the zone thermostat 707 to set the setpoint and priority of the zone 711, the zone thermostat 708 to set the setpoint and priority of the zone 712, etc. In one embodiment, the occupants use the central system console 1300 to set the setpoint and priority of each zone, and the zone thermostats to override (either on a permanent or temporary basis) the central settings. In one embodiment, the central console 1300 displays the current temperature, setpoint temperature, temperature slope, and priority of each zone.

In one embodiment, the central system allocates HVAC air to each zone according to the priority of the zone and the temperature of the zone relative to the setpoint temperature of the zone. Thus, for example, in one embodiment, the central system provides relatively more HVAC air to relatively higher priority zones that are not at their temperature setpoint than to lower priority zones or zones that are at or relatively near their setpoint temperature. In one embodiment, the central system avoids closing or partially closing too many vents in order to avoid reducing airflow in the duct below a desired minimum value.

In one embodiment, the central system monitors a temperature rate of rise (or fall) in each zone and sends commands to adjust the amount each ECRV 702-705 is open to bring higher priority zones to a desired temperature without allowing lower-priority zones to stray too far form their respective setpoint temperature.

In one embodiment, the central system uses predictive modeling to calculate an amount of vent opening for each of the ECRVs 702-705 to reduce the number of times the vents are opened and closed and thereby reduce power usage by the actuators 409. In one embodiment, the central system uses a neural network to calculate a desired vent opening for each of the ECRVs 702-705. In one embodiment, various operating parameters such as the capacity of the central HVAC system, the volume of the house, etc., are programmed into the central system for use in calculating vent openings and closings. In one embodiment, the central system is adaptive and is configured to learn operating characteristics of the HVAC system and the ability of the HVAC system to control the temperature of the various zones as the ECRVs 702-705 are opened and closed. In an adaptive learning system, as the central system controls the ECRVs to achieve the desired temperature over a period of time, the central system learns which ECRVs need to be opened, and by how much, to achieve a desired level of heating and cooling for each zone. The use of such an adaptive central system is convenient because the installer is not required to program HVAC operating parameters into the central system. In one embodiment, the central system provides warnings when the HVAC system appears to be operating abnormally, such as, for example, when the temperature of one or more zones does not change as expected (e.g., because the HVAC system is not operating properly, a window or door is open, etc.).

In one embodiment, the adaptation and learning capability of the central system uses different adaptation results (e.g., different coefficients) based on whether the HVAC system is heating or cooling, the outside temperature, a change in the setpoint temperature or priority of the zones, etc. Thus, in one embodiment, the central system uses a first set of adaptation coefficients when the HVAC system is cooling, and a second set of adaptation coefficients when the HVAC system is heating. In one embodiment, the adaptation is based on a predictive model. In one embodiment, the adaptation is based on a neural network.

FIG. 17 shows an ECRV 1700 configured to be used in connection with a conventional T-bar ceiling system found in many commercial structures. In the ECRV 1700, an actuator 1701 (as one embodiment of the actuator 409) is provided to a damper 1702. The damper 1702 is provided to a diffuser 1703 that is configured to mount in a conventional T-bar ceiling system. The ECRV 1700 can be connected to a zoned thermostat or central system by wireless or wired communication.

In one embodiment, the sensors 407 in the ECRVs include airflow and/or air velocity sensors. Data from the sensors 407 are transmitted by the ECRV to the central system. The central system uses the airflow and/or air velocity measurements to determine the relative amount of air through each ECRV. Thus, for example, by using airflow/velocity measurements, the central system can adapt to the relatively lower airflow of smaller ECRVs and ECRVs that are situated on the duct further from the HVAC blower than ECRVs which are located closer to the blower (the closer ECRVs tend to receive more airflow).

In one embodiment, the sensors 407 include humidity sensors. In one embodiment, the zone thermostat 1100 includes a zone humidity sensor provided to the controller 1101. The zone control system (e.g., the central system, the zone thermostat, and/or ECRV) uses humidity information from the humidity sensors to calculate zone comfort values and to adjust the temperature setpoint according to a comfort value. Thus, for example, in one embodiment during a summer cooling season, the zone control system lowers the zone temperature setpoint during periods of relative high humidity, and raises the zone setpoint during periods of relatively low humidity. In one embodiment, the zone thermostat allows the occupants to specify a comfort setting based on temperature and humidity. In one embodiment, the zone control system controls the HVAC system to add or remove humidity from the heating/cooling air.

FIG. 18 shows a register vent 1800 configured to use a scrolling curtain 1801 to control airflow as an alternative to the vanes shown in FIGS. 2 and 3. An actuator 1802 (one embodiment of the actuator 409) is provided to the curtain 1801 to move the curtain 1801 across the register to control the size of a register airflow opening In one embodiment, the curtain 1801 is guided and held in position by a track 1803.

In one embodiment, the actuator 1802 is a rotational actuator and the scrolling curtain 1801 is rolled around the actuator 1802, and the register vent 1800 is open and rigid enough to be pushed into the vent opening by the actuator 1802 when the actuator 1802 rotates to unroll the curtain 1801.

FIG. 19 is a block diagram of a control algorithm 1900 for controlling the register vents. For purposes of explanation, and not by way of limitation, the algorithm 1900 is described herein as running on the central system. However, one of ordinary skill in the art will recognize that the algorithm 1900 can be run by the central system, by the zone thermostat, by the ECRV, or the algorithm 1900 can be distributed among the central system, the zone thermostat, and the ECRV. In the algorithm 1900, in a block 1901 of the algorithm 1900, the setpoint temperatures from one or more zone thermostats are provided to a calculation block 1902. The calculation block 1902 calculates the register vent settings (e.g., how much to open or close each register vent) according to the zone temperature, the zone priority, the available heating and cooling air, the previous register vent settings, etc. as described above. In one embodiment, the block 1902 uses a predictive model as described above. In one embodiment, the block 1902 calculates the register vent settings for each zone independently (e.g., without regard to interactions between zones). In one embodiment, the block 1902 calculates the register vent settings for each zone in a coupled-zone manner that includes interactions between zones. In one embodiment, the calculation block 1902 calculates new vent openings by taking into account the current vent openings and in a manner configured to minimize the power consumed by opening and closing the register vents.

Register vent settings from the block 1902 are provided to each of the register vent actuators in a block 1903, wherein the register vents are moved to new opening positions as desired (and, optionally, one or more of the fans 402 are turned on to pull additional air from desired ducts). After setting the new vent openings in the block 1903, the process advances to a block 1904 where new zone temperatures are obtained from the zone thermostats (the new zone temperatures being responsive to the new register vent settings made in block 1903). The new zone temperatures are provided to an adaptation input of the block 1902 to be used in adapting a predictive model used by the block 1902. The new zone temperatures also provided to a temperature input of the block 1902 to be used in calculating new register vent settings.

As described above, in one embodiment, the algorithm used in the calculation block 1902 is configured to predict the ECRV opening needed to bring each zone to the desired temperature based on the current temperature, the available heating and cooling, the amount of air available through each ECRV, etc. The calculating block uses the prediction model to attempt to calculate the ECRV openings needed for relatively long periods of time in order to reduce the power consumed in unnecessarily by opening and closing the register vents. In one embodiment, the ECRVs are battery powered, and thus reducing the movement of the register vents extends the life of the batteries. In one embodiment, the block 1902 uses a predictive model that learns the characteristics of the HVAC system and the various zones and thus the model prediction tends to improve over time.

In one embodiment, the zone thermostats report zone temperatures to the central system and/or the ECRVs at regular intervals. In one embodiment, the zone thermostats report zone temperatures to the central system and/or the ECRVs after the zone temperature has changed by a specified amount specified by a threshold value. In one embodiment, the zone thermostats report zone temperatures to the central system and/or the ECRVs in response to a request instruction from the central system or ECRV.

In one embodiment, the zone thermostats report setpoint temperatures and zone priority values to the central system or ECRVs whenever the occupants change the setpoint temperatures or zone priority values using the user controls 1102. In one embodiment, the zone thermostats report setpoint temperatures and zone priority values to the central system or ECRVs in response to a request instruction from the central system or ECRVs.

In one embodiment, the occupants can choose the thermostat deadband value (e.g., the hysteresis value) used by the calculation block 1902. A relatively larger deadband value reduces the movement of the register vent at the expense of larger temperature variations in the zone.

In one embodiment, the ECRVs report sensor data (e.g., duct temperature, airflow, air velocity, power status, actuator position, etc.) to the central system and/or the zone thermostats at regular intervals. In one embodiment, the ECRVs report sensor data to the central system and/or the zone thermostats whenever the sensor data fails a threshold test (e.g., exceeds a threshold value, falls below a threshold value, falls inside a threshold range, or falls outside a threshold range, etc.). In one embodiment, the ECRVs report sensor data to the central system and/or the zone thermostats in response to a request instruction from the central system or zone thermostat.

In one embodiment, the central system is shown in FIGS. 7-9 is implemented in a distributed fashion in the zone thermostats 1100 and/or in the ECRVs. In the distributed system, the central system does not necessarily exists as a distinct device, rather, the functions of the central system can be are distributed in the zone thermostats 1100 and/or the ECRVs. Thus, in a distributed system, FIGS. 7-9 represent a conceptual/computational model of the system. For example, in a distributed system, each zone thermostat 100 knows its zone priority, and the zone thermostats 1100 in the distributed system negotiate to allocate the available heating/cooling air among the zones. In one embodiment of a distributed system, one of the zone thermostat assumes the role of a master thermostat that collects data from the other zone thermostats and implements the calculation block 1902. In one embodiment of a distributed system, the zone thermostats operate in a peer-to-peer fashion, and the calculation block 1902 is implemented in a distributed manner across a plurality of zone thermostats and/or ECRVs.

In one embodiment, the fans 402 can be used as generators to provide power to recharge the power source 404 in the ECRV. However, using the fan 402 in such a manner restricts airflow through the ECRV. In one embodiment, the controller 401 calculates a vent opening for the ECRV to produce the desired amount of air through the ECRV while using the fan to generate power to recharge the power source 404 (thus, in such circumstance) the controller would open the vanes more than otherwise necessary in order to compensate for the air resistance of the generator fan 402. In one embodiment, in order to save power in the ECRV, rather than increase the vane opening, the controller 401 can use the fan as a generator. The controller 401 can direct the power generated by the fan 402 into one or both of the power sources 404, 405, or the controller 401 can dump the excess power from the fan into a resistive load. In one embodiment, the controller 401 makes decisions regarding vent opening versus fan usage. In one embodiment, the central system instructs the controller 401 when to use the vent opening and when to use the fan. In one embodiment, the controller 401 and central system negotiate vent opening versus fan usage.

In one embodiment, the ECRV reports its power status to the central system or zone thermostat. In one embodiment the central system or zone thermostat takes such power status into account when determining new ECRV openings. Thus, for example, if there are first and second ECRVs serving one zone and the central system knows that the first ECRVs is low on power, the central system will use the second ECRV to modulate the air into the zone. If the first ECRV is able to use the fan 402 or other airflow-based generator to generate electrical power, the central system will instruct the second ECRV to a relatively closed position in and direct relatively more airflow through the first ECRV when directing air into the zone.

It will be evident to those skilled in the art that the invention is not limited to the details of the foregoing illustrated embodiments and that the present invention may be embodied in other specific forms without departing from the spirit or essential attributed thereof; furthermore, various omissions, substitutions and changes may be made without departing from the spirit of the inventions. For example, although specific embodiments are described in terms of the 900 MHz frequency band, one of ordinary skill in the art will recognize that frequency bands above and below 900 MHz can be used as well. The wireless system can be configured to operate on one or more frequency bands, such as, for example, the HF band, the VHF band, the UHF band, the Microwave band, the Millimeter wave band, etc. One of ordinary skill in the art will further recognize that techniques other than spread spectrum can also be used and/or can be used instead spread spectrum. The modulation uses is not limited to any particular modulation method, such that modulation scheme used can be, for example, frequency modulation, phase modulation, amplitude modulation, combinations thereof, etc. The one or more of the wireless communication systems described above can be replaced by wired communication. The one or more of the wireless communication systems described above can be replaced by powerline networking communication. The foregoing description of the embodiments is, therefore, to be considered in all respects as illustrative and not restrictive, with the scope of the invention being delineated by the appended claims and their equivalents.

Claims

1. A zone controller, comprising: a sensor for sensing pressure within a duct; anda controller configured to: operate the zone controller in a first state and a second state; andalternate the zone controller between the first state and the second state over a period of time, the second state being configured such that the zone controller is configured to: monitor the pressure within the duct via measurements from the sensor; andcommunicate a pressure measurement for the pressure within the duct, as measured by the sensor, from the zone controller to a central controller located remote from the zone controller.
2. The zone controller of claim 1, wherein while the zone controller is in the second state, the zone controller is configured to both: monitor the pressure within the duct via measurements from the sensor; andcommunicate the pressure measurement for the pressure within the duct as measured by the sensor from the zone controller to the central controller.
3. The zone controller of claim 1, wherein, while the zone controller is set to the first state, the zone controller sleeps between the measurements made by the sensor of the pressure within the duct.
4. The zone controller of claim 1, wherein the zone controller comprises: a communication interface configured to communicate environmental condition data, for an environmental zone associated with the zone controller, to the central controller; anda temperature sensor configured to monitor temperature of the environmental zone associated with the zone controller.
5. The zone controller of claim 1, wherein the zone controller comprises a battery-powered power source.
6. The zone controller of claim 1, wherein the controller of the zone controller is further configured to: receive a wake-up signal instructing the zone controller to change from the first state to the second state; andin response to the reception of the wake-up signal, change an operational state of the zone controller from the first state to the second state such that a communication interface is activated for sending communications to another device.
7. The zone controller of claim 1, wherein the controller is configured to alternate between the first state and the second state after a predetermined period of time.
8. The zone controller of claim 1, wherein the controller of the zone controller is further configured to: receive a communication from the central controller including: an instruction to perform a measurement;an instruction to enter the first state;an instruction to enter the second state;an instruction to report battery status;an instruction to change a period of time at which the zone controller will change from the first state to the second state; oran instruction to run self-diagnostics and report results thereof to the central controller.
9. The zone controller of claim 8, wherein the controller of the zone controller is further configured to perform the instruction included in the received communication.
10. The zone controller of claim 1, wherein the zone controller is further configured to: alternate to a third state, the third state being a state in which the zone controller is configured to receive, wirelessly, instructions from the central controller.
11. The zone controller of claim 1, wherein the first state of the zone controller is configured such that the controller of the zone controller monitors the pressure in the duct using the measurements from the sensor.
12. The zone controller of claim 1, wherein the zone controller is arranged on-board an electronically-controlled register vent for controlling airflow from a central heating, ventilation, and air conditioning (HVAC) system through the duct into one of multiple environmental zones.
13. A method for controlling a zone controller, the method comprising: alternating, over time, an operation of the zone controller between a first state and a second state;monitoring, by the zone controller, pressure within a duct that provides airflow from a central heating, ventilation, and air conditioning (HVAC) system to an environmental zone associated with the zone controller, while in at least one of the first state or the second state;communicating pressure data for the environmental zone associated with the zone controller from the zone controller to a central controller, while in the second state but not in the first state; andcontrolling actuation of an electronically-controlled register vent at least partially based on the pressure data.
14. The method for controlling the zone controller of claim 13, wherein the zone controller is arranged on-board the electronically-controlled register vent that controls airflow from the duct into one of the multiple environmental zones from the central heating, ventilation, and air conditioning (HVAC) system.
15. The method for controlling the zone controller of claim 13, the method further comprising: in response to the central controller analyzing the pressure data for the environmental zone, receiving, from the central controller, by the zone controller, an instruction to actuate the electronically-controlled register vent.
16. The method for controlling the zone controller of claim 13, the method further comprising: logging, by the zone controller, pressure data while in the first state; andcommunicating, by the zone controller, the logged environmental data from the zone controller to the central controller while in the second state.
17. The method for controlling the zone controller of claim 13, further comprising: monitoring, by the zone controller, the pressure within the duct associated with the zone controller while in the second state;deriving, by the zone controller, pressure data while in the second state; andcommunicating the pressure data from the zone controller to the central controller while in the second state.
18. The method for controlling the zone controller of claim 13, further comprising powering the zone controller using one or more batteries.
19. The method for controlling the zone controller of claim 13, the method further comprising: receiving an instruction from the central controller while in the second state;determining whether the instruction includes an identifier associated with the zone controller;ignoring the instruction when it is determined that the instruction does not include the identifier of the zone controller; andperforming an operation indicated by the instruction when it is determined that the instruction does include the identifier of the zone controller.
20. The method for controlling the zone controller of claim 19, wherein the instruction is an instruction to report battery status, and performing the operation includes determining a battery status of the zone controller and communicating the battery status of the zone controller to the central controller.
21. A vent control system, comprising: a central controller; anda plurality of zone controllers remotely located from and in wireless communication with the central controller, each zone controller further comprising: a sensor for sensing pressure associated with a duct; anda controller configured to: operate the zone controller in a first state and a second state; andalternate the zone controller between the first state and the second state over a period of time, the second state being configured such that the zone controller is configured to perform at least one of: monitor the pressure within the duct via measurements from the sensor; andcommunicate a pressure measurement for the pressure within the duct, as measured by the sensor, from the zone controller to the central controller.
22. The vent control system of claim 21, wherein while each zone controller is set to the first state, the zone controller sleeps between the measurements made by the sensor of the pressure within the duct.
23. A zone controller, comprising: a sensor for sensing pressure within a duct; anda controller configured to: operate the zone controller in a first state and a second state; andalternate the zone controller between the first state and the second state over a period of time, the second state being configured such that the zone controller is configured to: monitor the pressure within the duct via measurements from the sensor; andcommunicate a pressure measurement for the pressure within the duct, as measured by the sensor, from the zone controller to a central controller located remote from the zone controller, wherein the zone controller is arranged on-board an electronically-controlled register vent for controlling airflow from a central heating, ventilation, and air conditioning (HVAC) system through the duct into one of multiple environmental zones.
24. The zone controller of claim 23, wherein, while the zone controller is set to the first state, the zone controller sleeps between the measurements made by the sensor of the pressure within the duct.
25. The zone controller of claim 23, wherein the zone controller comprises a battery-powered power source.
26. The zone controller of claim 23, wherein the first state of the zone controller is configured such that the controller of the zone controller monitors the pressure in the duct using the measurements from the sensor.
27. A zone controller, comprising: a sensor for sensing pressure within a duct; anda controller configured to: operate the zone controller in a first state and a second state; andalternate the zone controller between the first state and the second state over a period of time, the second state being configured such that the zone controller is configured to perform at least one of: monitor the pressure within the duct via measurements from the sensor; andcommunicate a pressure measurement for the pressure within the duct, as measured by the sensor, from the zone controller to a central controller located remote from the zone controller,wherein while the zone controller is set to the first state, the zone controller sleeps between the measurements made by the sensor of the pressure within the duct.
28. The zone controller of claim 27, wherein the zone controller is arranged on-board an electronically-controlled register vent for controlling airflow from a central heating, ventilation, and air conditioning (HVAC) system through the duct into one of multiple environmental zones.
29. The zone controller of claim 27, wherein the zone controller is further configured to: alternate to a third state, the third state being a state in which the zone controller is configured to receive, wirelessly, instructions from the central controller.
30. The zone controller of claim 27, wherein the first state of the zone controller is configured such that the controller of the zone controller monitors the pressure in the duct using the measurements from the sensor.
31. A zone controller, comprising: a sensor for sensing pressure within a duct;a communication interface configured to communicate environmental condition data, for an environmental zone associated with the zone controller, to a central controller;a temperature sensor configured to monitor temperature of the environmental zone associated with the zone controller; anda controller configured to: operate the zone controller in a first state and a second state; andalternate the zone controller between the first state and the second state over a period of time, the second state being configured such that the zone controller is configured to perform at least one of: monitor the pressure within the duct via measurements from the sensor; andcommunicate, via the communication interface, a pressure measurement for the pressure within the duct, as measured by the sensor, from the zone controller to the central controller located remote from the zone controller.
32. The zone controller of claim 31, wherein the controller of the zone controller is further configured to: receive a wake-up signal instructing the zone controller to change from the first state to the second state; andin response to the reception of the wake-up signal, change an operational state of the zone controller from the first state to the second state such that a communication interface is activated for sending communications to another device.
33. The zone controller of claim 31, wherein the controller of the zone controller is further configured to: receive a communication from the central controller including: an instruction to perform a measurement;an instruction to enter the first state;an instruction to enter the second state;an instruction to report battery status;an instruction to change a period of time at which the zone controller will change from the first state to the second state; oran instruction to run self-diagnostics and report results thereof to the central controller.
34. The zone controller of claim 33, wherein the controller of the zone controller is further configured to perform the instruction included in the received communication.
35. A zone controller, comprising: a sensor for sensing pressure within a duct; anda controller configured to: operate the zone controller in a first state and a second state;alternate the zone controller between the first state and the second state over a period of time, the second state being configured such that the zone controller is configured to perform at least one of: monitor the pressure within the duct via measurements from the sensor; andcommunicate a pressure measurement for the pressure within the duct, as measured by the sensor, from the zone controller to a central controller located remote from the zone controller;receive a wake-up signal instructing the zone controller to change from the first state to the second state; andin response to receiving the wake-up signal, change an operational state of the zone controller from the first state to the second state such that a communication interface is activated for sending communications to another device.
36. The zone controller of claim 35, wherein the zone controller comprises: the communication interface configured to communicate environmental condition data, for an environmental zone associated with the zone controller, to the central controller; anda temperature sensor configured to monitor temperature of the environmental zone associated with the zone controller.
37. The zone controller of claim 35, wherein the zone controller comprises a battery-powered power source.
38. The zone controller of claim 37, wherein the controller of the zone controller is further configured to: receive a communication from the central controller including: an instruction to perform a measurement;an instruction to enter the first state;an instruction to enter the second state;an instruction to report battery status;an instruction to change a period of time at which the battery-operated zone controller will change from the first state to the second state; oran instruction to run self-diagnostics and report results thereof to the central controller.
39. A zone controller, comprising: a sensor for sensing pressure within a duct; anda controller configured to: operate the zone controller in a first state and a second state; andalternate the zone controller between the first state and the second state over a period of time, the second state being configured such that the zone controller is configured to: monitor the pressure within the duct via measurements from the sensor; andcommunicate a pressure measurement for the pressure within the duct, as measured by the sensor, from the zone controller to a central controller located remote from the zone controller, wherein the controller is configured to alternate between the first state and the second state after a predetermined period of time.
40. The zone controller of claim 39, wherein the controller of the zone controller is further configured to: receive a wake-up signal instructing the zone controller to change from the first state to the second state; andin response to receiving the wake-up signal, change an operational state of the zone controller from the first state to the second state such that a communication interface is activated for sending communications to another device.
41. The zone controller of claim 39, wherein the zone controller is further configured to: alternate to a third state, the third state being a state in which the zone controller is configured to receive, wirelessly, instructions from the central controller.
42. A zone controller, comprising: a sensor for sensing pressure within a duct; anda controller configured to: operate the zone controller in a first state and a second state; andalternate the zone controller between the first state and the second state over a period of time, the second state being configured such that the zone controller is configured to perform at least one of: monitor the pressure within the duct via measurements from the sensor; andcommunicate a pressure measurement for the pressure within the duct, as measured by the sensor, from the zone controller to a central controller located remote from the zone controller; andalternate to a third state, the third state being a state in which the zone controller is configured to receive, wirelessly, instructions from the central controller.
43. The zone controller of claim 42, wherein, while the zone controller is set to the first state, the zone controller sleeps between the measurements made by the sensor of the pressure within the duct.
44. The zone controller of claim 42, wherein the first state of the zone controller is configured such that the controller of the zone controller monitors the pressure in the duct using the measurements from the sensor.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. Ser. No. 14/182,759, filed Feb. 18, 2015, which is a continuation of U.S. Ser. No. 13/269,155, filed Oct. 7, 2011, which is a continuation of U.S. Ser. No. 11/669,066, filed Jan. 30, 2007, now U.S. Pat. No. 8,033,479, issued Oct. 11, 2011, which is a continuation-in-part application of U.S. Ser. No. 10/959,362, filed Oct. 6, 2004, now U.S. Pat. No. 7,168,627, issued Jan. 30, 2007, which are hereby incorporated by reference in their entirety for all purposes.

US Referenced Citations (413)

Number	Name	Date	Kind
3640455	Romanelli	Feb 1972	A
3724534	Weatherston	Apr 1973	A
3991357	Kaminski	Nov 1976	A
4157506	Spencer	Jun 1979	A
4183290	Kucharczyk	Jan 1980	A
4223831	Szarka	Sep 1980	A
4308991	Peinetti et al.	Jan 1982	A
4330047	Ruspa et al.	May 1982	A
4335847	Levine	Jun 1982	A
4407447	Sayegh	Oct 1983	A
4408711	Levine	Oct 1983	A
4417687	Grant	Nov 1983	A
4615380	Beckey	Oct 1986	A
4646964	Parker et al.	Mar 1987	A
4656835	Kidder et al.	Apr 1987	A
4657179	Aggers et al.	Apr 1987	A
4661914	Mulokey et al.	Apr 1987	A
4674027	Beckey	Jun 1987	A
4685614	Levine	Aug 1987	A
4695246	Beilfuss et al.	Sep 1987	A
4716957	Thompson et al.	Jan 1988	A
4742475	Kaiser et al.	May 1988	A
4751961	Levine et al.	Jun 1988	A
4754697	Asselbergs	Jul 1988	A
4809593	Asselbergs	Mar 1989	A
4824012	Tate	Apr 1989	A
4830095	Friend	May 1989	A
RE32960	Levine	Jun 1989	E
4842510	Grunden et al.	Jun 1989	A
4846399	Asselbergs	Jul 1989	A
4872828	Mierzwinski et al.	Oct 1989	A
4886110	Jackson	Dec 1989	A
4897798	Cler	Jan 1990	A
4942348	Nilssen	Jul 1990	A
4948040	Kobayashi et al.	Aug 1990	A
4948044	Cacciatore	Aug 1990	A
D310873	Asselbergs	Sep 1990	S
4955806	Grunden et al.	Sep 1990	A
4971136	Mathur et al.	Nov 1990	A
5065813	Berkeley et al.	Nov 1991	A
5088645	Bell	Feb 1992	A
5127464	Butler et al.	Jul 1992	A
5158477	Testa et al.	Oct 1992	A
5161606	Berkeley et al.	Nov 1992	A
5175439	Haerer et al.	Dec 1992	A
5211332	Adams	May 1993	A
5224648	Simon et al.	Jul 1993	A
5240178	Dewolf et al.	Aug 1993	A
5244146	Jefferson et al.	Sep 1993	A
5255179	Zekan et al.	Oct 1993	A
5271558	Hampton	Dec 1993	A
5301101	MacArthur et al.	Apr 1994	A
5303767	Riley	Apr 1994	A
5318104	Shah et al.	Jun 1994	A
5347982	Binzer et al.	Sep 1994	A
5348078	Dushane et al.	Sep 1994	A
5352930	Ratz	Oct 1994	A
5364304	Hampton	Nov 1994	A
5381950	Aldridge	Jan 1995	A
5395042	Riley et al.	Mar 1995	A
5449319	Dushane et al.	Sep 1995	A
5452762	Zillner, Jr.	Sep 1995	A
5467921	Shreeve et al.	Nov 1995	A
5476221	Seymour	Dec 1995	A
5489238	Asselbergs	Feb 1996	A
5495887	Kathnelson et al.	Mar 1996	A
5499196	Pacheco	Mar 1996	A
5506569	Rowlette	Apr 1996	A
5533668	Erikson	Jul 1996	A
5535814	Hartman	Jul 1996	A
5544036	Brown, Jr. et al.	Aug 1996	A
5555927	Shah	Sep 1996	A
5570837	Brown et al.	Nov 1996	A
5595342	McNair et al.	Jan 1997	A
5611484	Uhrich	Mar 1997	A
5622221	Genga, Jr. et al.	Apr 1997	A
5635896	Tinsley et al.	Jun 1997	A
5644173	Elliason et al.	Jul 1997	A
5697552	McHugh et al.	Dec 1997	A
5700993	Counsell et al.	Dec 1997	A
5711480	Zepke et al.	Jan 1998	A
5736795	Zuehlke et al.	Apr 1998	A
5761083	Brown, Jr. et al.	Jun 1998	A
5802467	Salazar et al.	Sep 1998	A
5808294	Neumann	Sep 1998	A
5810245	Heitman et al.	Sep 1998	A
5819840	Wilson et al.	Oct 1998	A
5839654	Weber	Nov 1998	A
5863246	Bujak, Jr.	Jan 1999	A
5902183	D'Souza	May 1999	A
5903139	Kompelien	May 1999	A
5909378	De Milleville	Jun 1999	A
5918474	Khanpara et al.	Jul 1999	A
5924017	Pinter et al.	Jul 1999	A
5926776	Glorioso et al.	Jul 1999	A
5944098	Jackson	Aug 1999	A
5950709	Krueger et al.	Sep 1999	A
5977964	Williams et al.	Nov 1999	A
6023938	Taras et al.	Feb 2000	A
6060719	DiTucci et al.	May 2000	A
6062482	Gauthier et al.	May 2000	A
6066843	Scheremeta	May 2000	A
6072784	Agrawal et al.	Jun 2000	A
6084518	Jamieson	Jul 2000	A
6095427	Hoium et al.	Aug 2000	A
6098893	Berglund et al.	Aug 2000	A
6102749	Lynn et al.	Aug 2000	A
6116512	Dushane et al.	Sep 2000	A
6145752	Jackson	Nov 2000	A
6216956	Ehlers et al.	Apr 2001	B1
6222719	Kadah	Apr 2001	B1
6250382	Rayburn et al.	Jun 2001	B1
6259944	Margulis et al.	Jul 2001	B1
6275160	Ha	Aug 2001	B1
6322443	Jackson	Nov 2001	B1
6338677	White	Jan 2002	B1
6349883	Simmons et al.	Feb 2002	B1
6356038	Bishel	Mar 2002	B2
6356204	Guindi et al.	Mar 2002	B1
6363422	Hunter et al.	Mar 2002	B1
6370894	Thompson et al.	Apr 2002	B1
6385510	Hoog et al.	May 2002	B1
6415205	Myron et al.	Jul 2002	B1
6453687	Sharood et al.	Sep 2002	B2
6478233	Shah	Nov 2002	B1
6488081	Rayburn et al.	Dec 2002	B2
6491094	Rayburn et al.	Dec 2002	B2
6509838	Payne et al.	Jan 2003	B1
6513723	Mueller et al.	Feb 2003	B1
6519509	Nierlich et al.	Feb 2003	B1
6566768	Zimmerman et al.	May 2003	B2
6574581	Bohrer et al.	Jun 2003	B1
6604023	Brown et al.	Aug 2003	B1
6619055	Addy	Sep 2003	B1
6619555	Rosen	Sep 2003	B2
6622115	Brown et al.	Sep 2003	B1
6622925	Carner et al.	Sep 2003	B2
6634422	Rayburn	Oct 2003	B2
6645066	Gutta et al.	Nov 2003	B2
6657418	Carner et al.	Dec 2003	B2
6692349	Brinkerhoff et al.	Feb 2004	B1
6760319	Gerten et al.	Jul 2004	B1
6769482	Wagner et al.	Aug 2004	B2
6794771	Orioff	Sep 2004	B2
6798341	Eckel et al.	Sep 2004	B1
6851621	Wacker et al.	Feb 2005	B1
6851967	Miyoshi et al.	Feb 2005	B2
6886754	Smith et al.	May 2005	B2
6891838	Petite et al.	May 2005	B1
6909921	Bilger	Jun 2005	B1
6912429	Bilger	Jun 2005	B1
6975958	Bohrer et al.	Dec 2005	B2
6983889	Alles	Jan 2006	B2
6990821	Singh et al.	Jan 2006	B2
6997390	Alles	Feb 2006	B2
7014124	Gottlieb	Mar 2006	B2
7024336	Salsbury et al.	Apr 2006	B2
7055759	Wacker et al.	Jun 2006	B2
7057506	Bash et al.	Jun 2006	B2
7083109	Pouchak	Aug 2006	B2
7135965	Chapman, Jr. et al.	Nov 2006	B2
7149727	Nicholls et al.	Dec 2006	B1
7149729	Kaasten et al.	Dec 2006	B2
7156316	Kates	Jan 2007	B2
7156318	Rosen	Jan 2007	B1
7163156	Kates	Jan 2007	B2
7167079	Smyth et al.	Jan 2007	B2
7168627	Kates	Jan 2007	B2
7181317	Amundson et al.	Feb 2007	B2
7200467	Amundson et al.	Feb 2007	B2
7188482	Sadegh et al.	Mar 2007	B2
7289887	Rodgers	Oct 2007	B2
7360370	Shah et al.	Apr 2008	B2
7379791	Tamarkin et al.	May 2008	B2
RE40437	Rosen	Jul 2008	E
7434742	Mueller et al.	Oct 2008	B2
7455236	Kates	Nov 2008	B2
7455237	Kates	Nov 2008	B2
7460690	Cohen et al.	Dec 2008	B2
7469550	Chapman, Jr. et al.	Dec 2008	B2
7476988	Mulhouse et al.	Jan 2009	B2
7510126	Rossi et al.	Mar 2009	B2
7537171	Mueller et al.	May 2009	B2
7558648	Hoglund et al.	Jul 2009	B2
7562536	Harrod et al.	Jul 2009	B2
7571865	Nicodem et al.	Aug 2009	B2
7605714	Thompson et al.	Oct 2009	B2
7634504	Amundson	Dec 2009	B2
7644869	Hoglund et al.	Jan 2010	B2
7702424	Cannon et al.	Apr 2010	B2
7703694	Mueller et al.	Apr 2010	B2
D614976	Skafdrup et al.	May 2010	S
7748640	Roher et al.	Jul 2010	B2
7755220	Sorg et al.	Jul 2010	B2
7755480	Aritsuka et al.	Jul 2010	B2
7784704	Harter	Aug 2010	B2
7802618	Simon et al.	Sep 2010	B2
7832465	Zou et al.	Nov 2010	B2
7837128	Helt et al.	Nov 2010	B2
7837958	Crapser et al.	Nov 2010	B2
7844764	Williams	Nov 2010	B2
7847681	Singhal et al.	Dec 2010	B2
7848900	Steinberg et al.	Dec 2010	B2
7849698	Harrod et al.	Dec 2010	B2
7854389	Ahmed	Dec 2010	B2
7904209	Podgorny et al.	Mar 2011	B2
7904830	Hoglund et al.	Mar 2011	B2
8010237	Cheung et al.	Aug 2011	B2
8019567	Steinberg et al.	Sep 2011	B2
8033479	Kates	Oct 2011	B2
8037022	Rahman et al.	Oct 2011	B2
8067912	Mullin	Nov 2011	B2
8090477	Steinberg	Jan 2012	B1
8091375	Crawford	Jan 2012	B2
8131207	Hwang et al.	Mar 2012	B2
8131497	Steinberg et al.	Mar 2012	B2
8174381	Imes et al.	May 2012	B2
8180492	Steinberg	May 2012	B2
8219249	Harrod et al.	Jul 2012	B2
8265798	Imes	Sep 2012	B2
8415829	Di Cristofaro	Apr 2013	B2
8695888	Kates	Apr 2014	B2
9182140	Kates	Nov 2015	B2
9194599	Kates	Nov 2015	B2
9222692	Kates	Dec 2015	B2
9273879	Kates	Mar 2016	B2
9303889	Kates	Apr 2016	B2
9316407	Kates	Apr 2016	B2
9353963	Kates	May 2016	B2
9353964	Kates	May 2016	B2
9618223	Kates	Apr 2017	B2
9995497	Kates	Jun 2018	B2
10126011	Kates	Nov 2018	B2
20010024968	Gibbons et al.	Sep 2001	A1
20010048030	Sharood et al.	Dec 2001	A1
20020017107	Bailey et al.	Feb 2002	A1
20020074865	Zimmerman et al.	Jun 2002	A1
20020134849	Disser	Sep 2002	A1
20030037555	Street et al.	Feb 2003	A1
20030064335	Canon	Apr 2003	A1
20030066897	Carner et al.	Apr 2003	A1
20030090243	Atherton	May 2003	A1
20030231001	Bruning	Dec 2003	A1
20040095237	Chen et al.	May 2004	A1
20040120084	Readio et al.	Jun 2004	A1
20040130454	Barton	Jul 2004	A1
20040176022	Thrasher et al.	Sep 2004	A1
20040193324	Hoog et al.	Sep 2004	A1
20040194484	Zou	Oct 2004	A1
20040209209	Chodacki et al.	Oct 2004	A1
20040211200	McMillan et al.	Oct 2004	A1
20040224627	Van Becelaere et al.	Nov 2004	A1
20040238651	Juntunen et al.	Dec 2004	A1
20040245349	Smith	Dec 2004	A1
20040249479	Shorrock	Dec 2004	A1
20050017873	Liu et al.	Jan 2005	A1
20050040250	Wruck	Feb 2005	A1
20050043907	Eckel et al.	Feb 2005	A1
20050053063	Madhavan	Mar 2005	A1
20050055432	Rodgers	Mar 2005	A1
20050082053	Halabi	Apr 2005	A1
20050090915	Geiwitz	Apr 2005	A1
20050095978	Blunn et al.	May 2005	A1
20050096102	Mock et al.	May 2005	A1
20050122233	Isoyama et al.	Jun 2005	A1
20050125083	Kiko	Jun 2005	A1
20050128067	Zakrewski	Jun 2005	A1
20050150968	Shearer	Jul 2005	A1
20050156731	Chapman et al.	Jul 2005	A1
20050159846	Van Ostrand et al.	Jul 2005	A1
20050189429	Breeden	Sep 2005	A1
20050192915	Ahmed et al.	Sep 2005	A1
20050194455	Alles	Sep 2005	A1
20050194456	Tessier et al.	Sep 2005	A1
20050246408	Chung	Nov 2005	A1
20050270151	Winick	Dec 2005	A1
20050280421	Yomoda et al.	Dec 2005	A1
20050284622	Nichols	Dec 2005	A1
20060071086	Kates	Apr 2006	A1
20060071087	Kates	Apr 2006	A1
20060071089	Kates	Apr 2006	A1
20060077917	Brahmajosyula et al.	Apr 2006	A1
20060102731	Mueller et al.	May 2006	A1
20060105697	Aronstam et al.	May 2006	A1
20060124759	Rossi et al.	Jun 2006	A1
20060147003	Archacki et al.	Jul 2006	A1
20060149395	Archacki et al.	Jul 2006	A1
20060186214	Simon et al.	Aug 2006	A1
20060196953	Simon et al.	Sep 2006	A1
20060208099	Chapman et al.	Sep 2006	A1
20070037507	Liu	Feb 2007	A1
20070038787	Harris et al.	Feb 2007	A1
20070043478	Ehlers et al.	Feb 2007	A1
20070045431	Chapman, Jr. et al.	Mar 2007	A1
20070045441	Ashworth et al.	Mar 2007	A1
20070082601	Desrochers et al.	Apr 2007	A1
20070095518	Kates	May 2007	A1
20070102149	Kates	May 2007	A1
20070114295	Jenkins	May 2007	A1
20070115827	Boehnke et al.	May 2007	A1
20070115902	Shamoon et al.	May 2007	A1
20070119957	Kates	May 2007	A1
20070119958	Kates	May 2007	A1
20070131787	Rossi et al.	Jun 2007	A1
20070157639	Harrod	Jul 2007	A1
20070205297	Finkam et al.	Sep 2007	A1
20070208461	Chase	Sep 2007	A1
20070221741	Wagner et al.	Sep 2007	A1
20070228183	Kennedy et al.	Oct 2007	A1
20070233323	Wiemeyer et al.	Oct 2007	A1
20070241203	Wagner et al.	Oct 2007	A1
20070296280	Sorg et al.	Dec 2007	A1
20070298706	Hudon et al.	Dec 2007	A1
20080015740	Osann	Jan 2008	A1
20080015742	Kulyk et al.	Jan 2008	A1
20080099568	Nicodem et al.	May 2008	A1
20080128523	Hoglund et al.	Jun 2008	A1
20080133956	Fadell	Jun 2008	A1
20080147242	Roher et al.	Jun 2008	A1
20080161977	Takach et al.	Jul 2008	A1
20080179052	Kates	Jul 2008	A1
20080179053	Kates	Jul 2008	A1
20080183335	Poth et al.	Jul 2008	A1
20080185450	Kwon et al.	Aug 2008	A1
20080191045	Harter	Aug 2008	A1
20080273754	Hick et al.	Nov 2008	A1
20080317292	Baker et al.	Dec 2008	A1
20090045263	Mueller et al.	Feb 2009	A1
20090057425	Sullivan et al.	Mar 2009	A1
20090057427	Geadelmann et al.	Mar 2009	A1
20090065595	Kates	Mar 2009	A1
20090140056	Leen	Jun 2009	A1
20090140064	Schultz et al.	Jun 2009	A1
20090140065	Juntunen et al.	Jun 2009	A1
20090143879	Amundson et al.	Jun 2009	A1
20090143880	Amundson et al.	Jun 2009	A1
20090143918	Amundson et al.	Jun 2009	A1
20090171862	Harrod et al.	Jul 2009	A1
20090194601	Flohr	Aug 2009	A1
20090236433	Mueller et al.	Sep 2009	A1
20090243842	Mitchell et al.	Oct 2009	A1
20090254225	Boucher et al.	Oct 2009	A1
20090259713	Blumrich et al.	Oct 2009	A1
20090261174	Butler et al.	Oct 2009	A1
20090297901	Kilian et al.	Dec 2009	A1
20090327354	Resnick et al.	Dec 2009	A1
20100000239	Lifson et al.	Jan 2010	A1
20100006660	Leen et al.	Jan 2010	A1
20100012737	Kates	Jan 2010	A1
20100019051	Rosen	Jan 2010	A1
20100025483	Hoeynck et al.	Feb 2010	A1
20100050004	Hamilton et al.	Feb 2010	A1
20100058450	Fein et al.	Mar 2010	A1
20100070084	Steinberg et al.	Mar 2010	A1
20100070086	Harrod et al.	Mar 2010	A1
20100070234	Steinberg et al.	Mar 2010	A1
20100084482	Kennedy et al.	Apr 2010	A1
20100084918	Fells	Apr 2010	A1
20100114382	Ha et al.	May 2010	A1
20100131112	Amundson et al.	May 2010	A1
20100156608	Bae et al.	Jun 2010	A1
20100163633	Barrett et al.	Jul 2010	A1
20100163635	Ye	Jul 2010	A1
20100167783	Alameh et al.	Jul 2010	A1
20100168924	Tessier et al.	Jul 2010	A1
20100179704	Ozog	Jul 2010	A1
20100181964	Huggins et al.	Jul 2010	A1
20100211224	Keeling et al.	Aug 2010	A1
20100250009	Lifson et al.	Sep 2010	A1
20100261465	Rhoads et al.	Oct 2010	A1
20100262298	Johnson et al.	Oct 2010	A1
20100262299	Cheung et al.	Oct 2010	A1
20100280667	Steinberg	Nov 2010	A1
20100289643	Trundle et al.	Nov 2010	A1
20100298985	Hess et al.	Nov 2010	A1
20100305771	Rodgers	Dec 2010	A1
20100308119	Steinberg et al.	Dec 2010	A1
20100318227	Steinberg et al.	Dec 2010	A1
20110001812	Kang et al.	Jan 2011	A1
20110025257	Weng	Feb 2011	A1
20110046792	Imes et al.	Feb 2011	A1
20110046805	Bedros et al.	Feb 2011	A1
20110046806	Nagel et al.	Feb 2011	A1
20110054699	Imes et al.	Mar 2011	A1
20110077758	Tran et al.	Mar 2011	A1
20110077896	Steinberg et al.	Mar 2011	A1
20110078675	Van Camp et al.	Mar 2011	A1
20110151837	Winbush	Jun 2011	A1
20110152024	Kuehl	Jun 2011	A1
20110160913	Parker et al.	Jun 2011	A1
20110185895	Freen	Aug 2011	A1
20110253796	Posa et al.	Oct 2011	A1
20110282937	Deshpande et al.	Nov 2011	A1
20110307103	Cheung et al.	Dec 2011	A1
20110307112	Barrilleaux	Dec 2011	A1
20120017611	Coffel et al.	Jan 2012	A1
20120024969	Kates	Feb 2012	A1
20120065935	Steinberg et al.	Mar 2012	A1
20120085831	Kopp	Apr 2012	A1
20120101637	Imes et al.	Apr 2012	A1
20120158350	Steinberg et al.	Jun 2012	A1
20120221151	Steinberg	Aug 2012	A1
20120248211	Warren et al.	Oct 2012	A1
20120252430	Imes et al.	Oct 2012	A1
20140158336	Kates	Jun 2014	A1
20140158337	Kates	Jun 2014	A1
20140158338	Kates	Jun 2014	A1
20140158778	Kates	Jun 2014	A1
20140158780	Kates	Jun 2014	A1
20150330657	Kates	Nov 2015	A1
20160091220	Kates	Mar 2016	A1
20160231013	Kates	Aug 2016	A1
20160259351	Barrett et al.	Sep 2016	A1

Foreign Referenced Citations (27)

Number	Date	Country
1001873	Apr 1990	BE
1187966	May 1985	CA
2202008	Feb 2000	CA
202004010819	Nov 2004	DE
207295	Jan 1987	EP
447458	Sep 1991	EP
196069	Dec 1991	EP
510807	Oct 1992	EP
632234	Jan 1995	EP
697571	Feb 1996	EP
710804	May 1996	EP
710804	Dec 1997	EP
1614975	Jan 2006	EP
1275037	Feb 2006	EP
2671372	Jul 1992	FR
2294828	May 1996	GB
59106311	Jun 1984	JP
01252850	Oct 1989	JP
09298780	Nov 1997	JP
10023565	Jan 1998	JP
20556	Oct 2001	SI
2005019740	Mar 2005	WO
2006041599	Apr 2006	WO
2006041599	Sep 2006	WO
2007027554	Mar 2007	WO
2008054938	May 2008	WO
2008094166	Aug 2008	WO

Non-Patent Literature Citations (122)

Entry
“Final Office Action”, U.S. Appl. No. 14/182,964, dated Aug. 20, 2015, 8 pages.
“First Action Interview Office Action”, U.S. Appl. No. 14/811,526, dated Jan. 22, 2016, 5 pages.
“Nest Learning Thermostat: Unboxing and Review [Online]”, retrieved from the Internet: <URL: http://www.youtube.com/watch?v=KrgcOL4oLzc> [retrieved on Aug. 22, 2013], Feb. 2012., 2 pages.
“Non-Final Office Action”, U.S. Appl. No. 11/669,066, dated Dec. 8, 2010, 9 pages.
“Notice of Allowance”, U.S. Appl. No. 11/669,066, dated Aug. 1, 2011, 7 pages.
“Notice of Allowance”, U.S. Appl. No. 14/182,964, dated Oct. 28, 2015, 7 pages.
“Notice of Allowance”, U.S. Appl. No. 14/183,091, dated Dec. 14, 2015, 16 pages.
“Notice of Allowance”, U.S. Appl. No. 14/183,114, dated Nov. 23, 2015, 7 pages.
“Notice of Allowance”, U.S. Appl. No. 14/183,222, dated Nov. 30, 2015, 17 pages.
“Notice of Allowance”, U.S. Appl. No. 14/827,180, dated Feb. 9, 2016, 7 pages.
“Preinterview First Office Action”, U.S. Appl. No. 14/182,964, dated Apr. 15, 2015, 4 pages.
“Preinterview First Office Action”, U.S. Appl. No. 14/183,114, dated May 1, 2015, 4 pages.
“Restriction Requirement”, U.S. Appl. No. 11/669,066, dated Aug. 2, 2010, 7 pages.
Kates,“Multi-Nodal Thermostat Control System”, U.S. Appl. No. 14/811,526, filed Jul. 28, 2015, 34 pages.
Kates,“Systems and Methods for Wirelessly-Enabled HVAC Control”, U.S. Appl. No. 14/827,180, filed Aug. 14, 2015, 33 pages.
“Non-Final Office Action”, U.S. Appl. No. 14/811,526, dated Sep. 20, 2016, 12 pages.
“Notice of Allowance”, U.S. Appl. No. 14/811,526, dated Jan. 30, 2017, 7 pages.
6 Zone HVAC Control Unit, Residential Control Systems, Inc. (RCS) Product Specification Model ZC6R, Feb. 2002, 2 pages.
A 6-1 Device: Intelligent Residential Control Introduced by Carrier [online]. Carrier Corporation, Jan. 21, 2004. Retrieved from the Internet: <URL: http://www.global.carrier.com/details/0.CLI1_DIV28_ETI8093.00.html>, 2 pages.
Aprilaire Electronic Thermostats Model 8355 User's Manual, Research Products Corporation, Dec. 2000, 16 pages.
Automatically Control Your In-Wall or In-Floor Registers! [online] Smarthome, 2004. Retrieved from the Internet: <URL: http://www.smarthome.com/3096.html>, 1 page.
Automation for Your Home, RCS Product Catalog, Jun. 2004, 14 pages.
Braeburn 5300 Installer Guide, Braeburn Systems, LLC, Dec. 9, 2009, 10 pages.
Braeburn Model 5200, Braebum Systems, LLC, Jul. 20, 2011, 11 pages.
Comfort System: Commercial VAV & Zone Control Systems Product Specification, Jackson Systems, LLC, Mar. 2003, 14 pages.
DIY Zoning: Can I Do It?, [online] Vadim Tkachenko, Sep. 2004. [Retrieved on Sep. 23, 2004] Retrieved from the Internet: <URL: http://diy-zoning.sourceforge.net/Advanced/prerequisites.html>, 4 pages.
DIY Zoning: Dampers [online] Vadim Tkachenko, Sep. 2004. [Retrieved on Sep. 23, 2004] Retrieved from the Internet: < URL: http://diy-zoning.sourceforge.net/Advanced/dampers.html>, 3 pages.
DIY Zoning: Passive Mode, [online] Vadim Tkachenko, Sep. 2004. [Retrieved on Sep. 23, 2004] Retrieved from the Internet: < URL: http://diy-zoning.sourceforge.net/Advanced/passive_mode.html>, 2 pages.
DIY Zoning: Release Notes, [online] Vadim Tkachenko, Sep. 2004. [Retrieved on Sep. 23, 2004] Retrieved from the Internet: < URL: http://diy-zoning.sourceforge.net/Advanced/release_notes.html>, 4 pages.
DIY Zoning: Technical FAQ, [online] Vadim Tkachenko, Sep. 2004. [Retrieved on Sep. 23, 2004] Retrieved from the Internet: < URL: http://diy-zoning.sourceforge.net/Advanced/faq.html>, 11 pages.
DIY Zoning: Total Control, [online] Vadim Tkachenko, Sep. 2004. [Retrieved on Sep. 23, 2004] Retrieved from the Internet: < URL: http://diy-zoning.sourceforge.net/Advanced/total_control.html>, 3 pages.
Indoor: Home Comfort: Fans/Air Conditioning: Blower Booster [online] Improvements Catalog, 2003 [Retrieved on Sep. 30, 2004] Retrieved from the Internet: <URL: http://www.improvementscatalog.com/product.asp?product=49254zz&dept%5Fid=10100.html>, 1 page.
Want to Prevent Over Pressure Buildup in Your HVAC System? [online] Smarthome, 2004 [Retrieved on Sep. 30, 2004] Retrieved from the Internet: <URL: http://www.smarthome.com/3072.html> 1 page.
Ecobee Smart Si Thermostat Installation Manual, Ecobee, Apr. 3, 2012, 40 pages.
Ecobee Smart Si Thermostat User Manual, Ecobee, Apr. 3, 2012, 44 pages.
Ecobee Smart Thermostat Installation Manual, Jun. 29, 2011, 20 pages.
Ecobee Smart Thermostat User Manual, May 11, 2010, 20 pages.
Electric Heat Lock Out on Heat Pumps, Washington State University Extension Energy Program, Apr. 2010, pp. 1-3.
Honeywell Installation Guide FocusPRO TH6000 Series, Honeywell International, Inc., Jan. 5, 2012, 24 pages.
Honeywell Operating Manual FocusPro TH6000 Series, Honeywell International, Inc., Mar. 25, 2011, 80 pages.
Honeywell Prestige IAQ Product Data 2, Honeywell International, Inc., Jan. 12, 2012, 126 pages.
Honeywell Prestige THX9321 and TXH9421 Product Data, Honeywell International, Inc., 68-0311, Jan. 2012, 126 pages.
Honeywell Prestige THX9321-9421 Operating Manual, Honeywell International, Inc., Jul. 6, 2011, 120 pages.
Hunter Internet Thermostat Installation Guide, Hunter Fan Co., Aug. 14, 2012, 8 pages.
Introducing the New Smart Si Thermostat, Datasheet [online]. Ecobee, Mar. 2012 [retrieved on Feb. 25, 2013]. Retrieved from the Internet: <URL: https://www.ecobee.com/solutions/home/smart-si/>, Mar. 12, 2012, 4 pages.
Lennox ComfortSense 5000 Owners Guide, Lennox Industries, Inc., Feb. 2008, 32 pages.
Lennox ComfortSense 7000 Owners Guide, Lennox Industries, Inc., May 2009, 15 pages.
Lennox iComfort Manual, Lennox Industries, Inc., Dec. 2010, 20 pages.
Lux PSPU732T Manual, Lux Products Corporation, Jan. 6, 2009, 48 pages.
NetX RP32-WIFI Network Thermostat Consumer Brochure, Network Thermostat, May 2011, 2 pages.
NetX RP32-WIFI Network Thermostat Specification Sheet, Network Thermostat, Feb. 28, 2012, 2 pages.
RobertShaw Product Manual 9620, Maple Chase Company, Jun. 12, 2001, 14 pages.
RobertShaw Product Manual 9825i2, Maple Chase Company, Jul. 17, 2006, 36 pages.
SYSTXCCUIZ01-V Infinity Control Installation Instructions, Carrier Corp, May 31, 2012, 20 pages.
T8611G Chronotherm IV Deluxe Programmable Heat Pump Thermostat Product Data, Honeywell International Inc., Oct. 1997, 24 pages.
TB-PAC, TB-PHP, Base Series Programmable Thermostats, Carrier Corp, May 14, 2012, 8 pages.
The Perfect Climate Comfort Center PC8900A W8900A-C Product Data Sheet, Honeywell International Inc, Apr. 2001, 44 pages.
TP-PAC, TP-PHP, TP-NAC, TP-NHP Performance Series AC/HP Thermostat Installation Instructions, Carrier Corp, Sep. 2007, 56 pages.
Trane Communicating Thermostats for Fan Coil, Trane, May 2011, 32 pages.
Trane Communicating Thermostats for Heat Pump Control, Trane, May 2011, 32 pages.
Trane Install XL600 Installation Manual, Trane, Mar. 2006, 16 pages.
Trane XL950 Installation Guide, Trane, Mar. 2011, 20 pages.
Venstar T2900 Manual, Venstar, Inc., Apr. 2008, 113 pages.
Venstar T5800 Manual, Venstar, Inc., Sep. 7, 2011, 63 pages.
VisionPro TH8000 Series Installation Guide, Honeywell International, Inc., Jan. 2012, 12 pages.
VisionPro TH8000 Series Operating Manual, Honeywell International, Inc., Mar. 2011, 96 pages.
VisionPro Wi-Fi Programmable Thermostat User Guide, Honeywell International, Inc, Aug. 2012, 48 pages.
White Rodgers (Emerson) Model 1F81-261 Installation and Operating Instructions, White Rodgers, Apr. 15, 2010, 8 pages.
White Rodgers (Emerson) Model IF98EZ-1621 Homeowner's User Guide, White Rodgers, Jan. 25, 2012, 28 pages.
U.S. Appl. No. 10/959,361, Notice of Allowance dated Oct. 11, 2006, 7 pages.
U.S. Appl. No. 10/959,361, Restriction Requirement dated May 31, 2006, 5 pages.
U.S. Appl. No. 10/959,362, Notice of Allowance dated Oct. 11, 2006, 7 pages.
U.S. Appl. No. 10/959,362, Restriction Requirement dated May 31, 2006.
U.S. Appl. No. 10/959,494, Notice of Allowance dated Oct. 26, 2006, 7 pages.
U.S. Appl. No. 10/959,494, Restriction Requirement dated Apr. 27, 2006 , 6 pages.
U.S. Appl. No. 11/613,090, Non-final office action dated Apr. 22, 2008.
U.S. Appl. No. 11/613,090, Notice of Allowance dated Oct. 3, 2008, 6 pages.
U.S. Appl. No. 11/613,090, Restriction Requirement dated Mar. 3, 2008, 6 pages.
U.S. Appl. No. 11/613,110, Non-Final Office Action dated Jul. 22, 2008, 6 pages.
U.S. Appl. No. 11/613,110, Non-Final Office Action dated Feb. 1, 2008, 7 pages.
U.S. Appl. No. 11/613,110, Restriction Requirement dated Nov. 15, 2007, 6 pages.
U.S. Appl. No. 11/613,116, Non-Final Office Action dated Apr. 23, 2008, 7 pages.
U.S. Appl. No. 11/613,116, Notice of Allowance dated Oct. 9, 2008, 7 pages.
U.S. Appl. No. 11/613,116, Restriction Requirement dated Jan. 16, 2008, 6 pages.
U.S. Appl. No. 13/269,155, Non-Final Office Action dated Aug. 22, 2013, 9 pages.
U.S. Appl. No. 13/269,155, Notice of Allowance dated Dec. 6, 2013, 9 pages.
Akhlaghinia et al., Occupancy Monitoring in Intelligent Environment through Integrated Wireless Localizing Agents, IEEE, 2009, 7 pages.
Akhlaghinia et al., Occupant Behaviour Prediction in Ambient Intelligence Computing Environment, Journal of Uncertain Systems, vol. 2, No. 2, 2008, pp. 85-100.
Allen et al., Real-Time Earthquake Detection and Hazard Assessment by ElarmS Across California, Geophysical Research Letters, vol. 36, L00B08, 2009, pp. 1-6.
Arens et al., Demand Response Enabling Technology Development, Phase I Report: Jun. 2003-Nov. 2005, Jul. 27, P:/DemandRes/UC Papers/DR-Phase1Report-Final DraftApril24-26.doc, University of California Berkeley, pp. 1-108.
Arens et al., New Thermostat Demand Response Enabling Technology, Poster, University of California Berkeley, Jun. 10, 2004.
Bourke, Server Load Balancing, O'Reilly & Associates, Inc., Aug. 2001, 182 pages.
Bryant, SYSTXBBUID01 Evolution Control Installation Instructions, Feb. 2004, 12 pages.
Chatzigiannakis et al., Priority Based Adaptive Coordination of Wireless Sensors and Actors, Q2SWinet '06, Oct. 2006, pp. 37-44.
Deleeuw, Ecobee WiFi Enabled Smart Thermostat Part 2: The Features Review, retrieved from <URL: http://www.homenetworkenabled.com/content.php?136-ecobee-WiFi-enabled-Smart-Thermostat-Part-2-The-Features-review> [retrieved on Jan. 8, 2013], Dec. 2, 2011, 5 pages.
Gao et al., The Self-Programming Thermostat: Optimizing Setback Schedules Based on Home Occupancy Patterns, In Proceedings of the First ACM Workshop on Embedded Sensing Systems for Energy-Efficiency in Buildings, Nov. 3, 2009, 6 pages.
Loisos et al., Buildings End-Use Energy Efficiency: Alternatives to Compressor Cooling, California Energy Commission, Public Interest Energy Research, Jan. 2000, 80 pages.
Lu et al., The Smart Thermostat: Using Occupancy Sensors to Save Energy in Homes, In Proceedings of the 8th ACM Conference on Embedded Networked Sensor Systems, Nov. 3-5, 2010, pp. 211-224.
Mozer, The Neural Network House: An Environmental that Adapts to its Inhabitants, Proceedings of the American Association for Artificial Intelligence SS-98-02,1998, pp. 110-114.
International Application No. PCT/US2007/008322, International Search Report and Written opinion dated Feb. 13, 2009, 4 pages.
Ros et al., Multi-Sensor Human Tracking with the Bayesian Occupancy Filter, IEEE, 2009, 8 pages.
White et al., A Conceptual Model for Simulation Load Balancing, Proceedings of the 1998 Spring Simulation Interoperability Workshop, 1998, pp. 1-7.
Wong et al., Maximum Likelihood Estimation of ARMA Model with Error Processes for Replicated Observations, National University of Singapore, Department of Economics, Working Paper No. 0217, Feb. 2002, pp. 1-19.
“Final Office Action”, U.S. Appl. No. 14/811,526, dated May 13, 2016, 10 pages.
“Corrected Notice of Allowance”, U.S. Appl. No. 14/183,114, dated Mar. 4, 2016, 2 pages.
“Corrected Notice of Allowance”, U.S. Appl. No. 14/183,091, dated Mar. 8, 2016, 2 pages.
“Corrected Notice of Allowance”, U.S. Appl. No. 14/827,180, dated Mar. 8, 2016, 2 pages.
“Corrected Notice of Allowance”, U.S. Appl. No. 14/183,222, dated Mar. 15, 2016, 2 pages.
“Corrected Notice of Allowance”, U.S. Appl. No. 14/827,180, dated May 3, 2016, 2 pages.
“Pre-Interview First Office Action”, U.S. Appl. No. 14/951,206, dated Dec. 26, 2017, 4 pages.
“Pre-Interview Office Action”, U.S. Appl. No. 14/977,298, dated Oct. 27, 2017, 4 pages.
“Restriction Requirment”, U.S. Appl. No. 14/951,206, dated Sep. 28, 2017, 7 pages.
Derfler, et al., “How Networks Work”, Que Corporation, Millennium Edition, 2000, pp. 188-189.
“First Action Interview Office Action”, U.S. Appl. No. 14/977,298, dated Feb. 22, 2018, 5 pages.
“First Action Interview Office Action”, U.S. Appl. No. 14/951,206, dated Feb. 6, 2018, 5 pages.
“Notice of Allowance”, U.S. Appl. No. 14/951,206, dated Mar. 27, 2018, 8 pages.
“Final Office Action”, U.S. Appl. No. 14/977,298, dated May 17, 2018, 9 pages.
U.S. Appl. No. 14/182,759, filed Feb. 18, 2014, now U.S. Pat. No. 9,182,140 issued Nov. 10, 2015.
U.S. Appl. No. 13/269,155, filed Oct. 7, 2011, now U.S. Pat. No. 8,695,888 issued Apr. 15, 2014.
U.S. Appl. No. 11/669,066, filed Jan. 30, 2007, now U.S. Pat. No. 8,033,479 issued Oct. 11, 2011.
U.S. Appl. No. 10/959,362, filed Oct. 6, 2004, now U.S. Pat. No. 7,168,627 issued Jan. 30, 2007.
“Notice of Allowance”, U.S. Appl. No. 14/977,298, dated Sep. 5, 2018, 7 pages.

Related Publications (1)

	Number	Date	Country
	20160025363 A1	Jan 2016	US

Continuations (3)

	Number	Date	Country
Parent	14182759	Feb 2014	US
Child	14877733		US
Parent	13269155	Oct 2011	US
Child	14182759		US
Parent	11669066	Jan 2007	US
Child	13269155		US

Continuation in Parts (1)

	Number	Date	Country
Parent	10959362	Oct 2004	US
Child	11669066		US

Battery-operated wireless zone controllers having multiple states of power-related operation

Information

Patent Number

Date Filed

Date Issued

Inventors

Original Assignees

Examiners

Agents

CPC

Field of Search

CPC

International Classifications

Disclaimer

Term Extension

Abstract