The present disclosure pertains to Heating, Ventilation, and/or Air Conditioning (HVAC) systems. More particularly, the present disclosure pertains to HVAC controllers, such as thermostats, with programmable schedules.
Heating, Ventilation, and/or Air Conditioning (HVAC) systems are often used to control the comfort level within a building or other structure. Such HVAC systems typically include an HVAC controller that controls various HVAC components of the HVAC system in order to affect and/or control one or more environmental conditions within the building. In many cases, the HVAC controller is mounted to an internal wall of the building and provides control signals to various HVAC components of the HVAC system. In some cases, the HVAC controller operates the HVAC system in accordance with a programmable schedule that may be stored in memory within the HVAC controller. A user such as, for example, a homeowner may manipulate the programmable schedule via a user interface of the HVAC controller. Improvements in the hardware, user experience, and functionality of such HVAC controllers would be desirable.
The disclosure is directed to an HVAC controller that may be configured to control one or more HVAC components within an HVAC system. The HVAC controller may include a user interface, such as but not limited to a touchscreen display, that enables a user to view and/or manipulate settings within the HVAC controller including but not limited to parameters of a programmable schedule. In some cases, the HVAC controller may provide the user with a better user experience when viewing and/or editing the programmable schedule.
In a particular example of the disclosure, an HVAC controller may be configured to control one or more HVAC components in accordance with a programmable schedule that includes a plurality of schedule periods. The HVAC controller may include a housing for housing several components, including a touch screen display that is accessible from outside the housing, a memory and a controller that is operably coupled to the memory and to the touch screen display. The controller may be configured to control the one or more HVAC components in accordance with the programmable schedule and may be further configured to permit a user to navigate through a linearly ordered series of screens to display each of the plurality of schedule periods of the programmable schedule. In some instances, each displayed schedule period screen may concurrently display a plurality of schedule parameters on the touch screen display, where each of the schedule parameters can be individually selected by the user for editing by touching the corresponding schedule parameter via the touch screen display. The controller may be further configured to permit the user to edit the selected schedule parameter and to permit the user to navigate to another of the plurality of schedule periods of the programmable schedule after selecting and/or editing a selected schedule parameter.
In another example of the disclosure, an HVAC controller may be configured to control one or more HVAC components in accordance with a programmable schedule that includes a plurality of schedule periods. The HVAC controller may include a fixed segment touch screen display, a memory configured to store the programmable schedule and a controller that is operably coupled to the memory and the fixed segment touch screen display. The controller may be configured to control the one or more HVAC components in accordance with the programmable schedule and may include a schedule edit mode. In the schedule edit mode, the controller may permit a user to navigate to a selected one of the plurality of schedule periods, concurrently display a plurality of parameters for the selected one of the plurality of schedule periods on the fixed segment touch screen display, permit the user to select any one of the concurrently displayed plurality of parameters for editing by touching the selected one of the plurality of parameters on the fixed segment touch screen display, and permit the user to change a value of the selected one of the plurality of parameters by interacting with the fixed segment touch screen display.
In another example of the disclosure, an HVAC controller may be configured to control one or more HVAC components in accordance with a programmable schedule that includes a plurality of schedule periods. The HVAC controller may include a touch screen display defining a plurality of individual touch regions each located at a fixed location on the touch screen display. A memory may be configured to store a programmable schedule having a plurality of schedule periods, each of the plurality of schedule periods including a plurality of schedule parameters. A controller may be operably coupled to the memory and the touch screen display and may be configured to control the one or more HVAC components in accordance with the programmable schedule. The controller may be further configured to permit a user to navigate through a linearly ordered series of screens using one or more of the plurality of individual touch regions to sequentially display each of the plurality of schedule periods of the programmable schedule, wherein each displayed schedule period may include a plurality of schedule parameters concurrently displayed on the touch screen display with at least one of the plurality of schedule parameters displayed at a location on the touch screen display that overlaps with a corresponding one of the plurality of individual touch regions. The controller may be further configured to permit a user to individually select one of the at least one of the plurality of schedule parameters for editing by touching the corresponding individual touch region, and to permit the user to edit the selected one of the plurality of schedule parameters by touching one or more of the individual touch regions that are defined for that purpose.
The above summary of some embodiments is not intended to describe each disclosed embodiment or every implementation of the present disclosure. The Figures, and Detailed Description, which follow, more particularly exemplify some of these embodiments.
The disclosure may be more completely understood in consideration of the following description of various illustrative embodiments of the disclosure in connection with the accompanying drawings, in which:
While the disclosure is amenable to various modifications and alternative forms, specifics thereof have been shown by way of example in the drawings and will be described in detail. It should be understood, however, that the intention is not to limit the disclosure to the particular embodiments described. On the contrary, the intention is to cover all modifications, equivalents, and alternatives falling within the spirit and scope of the disclosure.
For the following defined terms, these definitions shall be applied, unless a different definition is given in the claims or elsewhere in this specification.
All numeric values are herein assumed to be modified by the term “about,” whether or not explicitly indicated. The term “about” generally refers to a range of numbers that one of skill in the art would consider equivalent to the recited value (i.e., having the same function or result). In many instances, the terms “about” may include numbers that are rounded to the nearest significant figure.
The recitation of numerical ranges by endpoints includes all numbers within that range (e.g. 1 to 5 includes 1, 1.5, 2, 2.75, 3, 3.80, 4, and 5).
As used in this specification and the appended claims, the singular forms “a”, “an”, and “the” include plural referents unless the content clearly dictates otherwise. As used in this specification and the appended claims, the term “or” is generally employed in its sense including “and/or” unless the content clearly dictates otherwise.
It is noted that references in the specification to “an embodiment”, “some embodiments”, “other embodiments”, etc., indicate that the embodiment described may include one or more particular features, structures, and/or characteristics. However, such recitations do not necessarily mean that all embodiments include the particular features, structures, and/or characteristics. Additionally, when particular features, structures, and/or characteristics are described in connection with one embodiment, it should be understood that such features, structures, and/or characteristics may also be used connection with other embodiments whether or not explicitly described unless clearly stated to the contrary.
The present disclosure is directed generally at building automation systems. Building automation systems are systems that control one or more operations of a building. Building automation systems can include HVAC systems, security systems, fire suppression systems, energy management systems and other systems. While HVAC systems with HVAC controllers are used as an example below, it should be recognized that the concepts disclosed herein can be applied to building automation systems more generally.
It is contemplated that the HVAC controller(s) 18 may be configured to control the comfort level in the building or structure by activating and deactivating the HVAC component(s) 6 in a controlled manner. The HVAC controller(s) 18 may be configured to control the HVAC component(s) 6 via a wired or wireless communication link 20. In some cases, the HVAC controller(s) 18 may be a thermostat, such as, for example, a wall mountable thermostat, but this is not required in all embodiments. Such a thermostat may include (e.g. within the thermostat housing) or have access to one or more temperature sensor(s) for sensing ambient temperature at or near the thermostat. In some instances, the HVAC controller(s) 18 may be a zone controller, or may include multiple zone controllers each monitoring and/or controlling the comfort level within a particular zone in the building or other structure.
In the illustrative HVAC system 4 shown in
In some cases, the system of vents or ductwork 10 and/or 14 can include one or more dampers 24 to regulate the flow of air, but this is not required. For example, one or more dampers 24 may be coupled to one or more HVAC controller(s) 18, and can be coordinated with the operation of one or more HVAC components 6. The one or more HVAC controller(s) 18 may actuate dampers 24 to an open position, a closed position, and/or a partially open position to modulate the flow of air from the one or more HVAC components to an appropriate room and/or zone in the building or other structure. The dampers 24 may be particularly useful in zoned HVAC systems, and may be used to control which zone(s) receives conditioned air from the HVAC component(s) 6.
In many instances, one or more air filters 30 may be used to remove dust and other pollutants from the air inside the building 2. In the illustrative example shown in
In some cases, and as shown in
In some cases, the equipment interface module 34 may include a first temperature sensor 38a located in the return (incoming) air duct 14, and a second temperature sensor 38b located in the discharge (outgoing or supply) air duct 10. Alternatively, or in addition, the equipment interface module 34 may include a differential pressure sensor including a first pressure tap 39a located in the return (incoming) air duct 14, and a second pressure tap 39b located downstream of the air filter 30 to measure a change in a parameter related to the amount of flow restriction through the air filter 30. In some cases, the equipment interface module 34, when provided, may include at least one flow sensor that is capable of providing a measure that is related to the amount of air flow restriction through the air filter 30. In some cases, the equipment interface module 34 may include an air filter monitor. These are just some examples.
When provided, the equipment interface module 34 may be configured to communicate with the HVAC controller 18 via, for example, a wired or wireless communication link 42. In other cases, the equipment interface module 34 may be incorporated or combined with the HVAC controller 18. In some instances, the equipment interface module 34 may communicate, relay or otherwise transmit data regarding the selected parameter (e.g. temperature, pressure, flow rate, etc.) to the HVAC controller 18. In some cases, the HVAC controller 18 may use the data from the equipment interface module 34 to evaluate the system's operation and/or performance. For example, the HVAC controller 18 may compare data related to the difference in temperature (delta T) between the return air side and the discharge air side of the HVAC system 4 to a previously determined delta T limit stored in the HVAC controller 18 to determine a current operating performance of the HVAC system 4.
In some cases, the HVAC controller 18 may be programmed to communicate over the second network 58 with an external web service hosted by one or more external web server(s) 66. A non-limiting example of such an external web service is Honeywell's TOTAL CONNECT™ web service. The HVAC controller 18 may be configured to upload selected data via the second network 58 to the external web service where it may be collected and stored on the external web server 66. In some cases, the data may be indicative of the performance of the HVAC system 4. Additionally, the HVAC controller 18 may be configured to receive and/or download selected data, settings and/or services sometimes including software updates from the external web service over the second network 58. The data, settings and/or services may be received automatically from the web service, downloaded periodically in accordance with a control algorithm, and/or downloaded in response to a user request. In some cases, for example, the HVAC controller 18 may be configured to receive and/or download an HVAC operating schedule and operating parameter settings such as, for example, temperature set points, humidity set points, start times, end times, schedules, window frost protection settings, and/or the like from the web server 66 over the second network 58. In some instances, the HVAC controller 18 may be configured to receive one or more user profiles having at least one operational parameter setting that is selected by and reflective of a user's preferences. In still other instances, the HVAC controller 18 may be configured to receive and/or download firmware and/or hardware updates such as, for example, device drivers from the web server 66 over the second network 58. Additionally, the HVAC controller 18 may be configured to receive local weather data, weather alerts and/or warnings, major stock index ticker data, traffic data, and/or news headlines over the second network 58. These are just some examples.
Depending upon the application and/or where the HVAC user is located, remote access and/or control of the HVAC controller 18 may be provided over the first network 54 and/or the second network 58. A variety of remote wireless devices 62 may be used to access and/or control the HVAC controller 18 from a remote location (e.g. remote from the HVAC Controller 18) over the first network 54 and/or second network 58 including, but not limited to, mobile phones including smart phones, tablet computers, laptop or personal computers, wireless network-enabled key fobs, e-readers, and/or the like. In many cases, the remote wireless devices 62 are configured to communicate wirelessly over the first network 54 and/or second network 58 with the HVAC controller 18 via one or more wireless communication protocols including, but not limited to, cellular communication, ZigBee, REDLINK™, Bluetooth, WiFi, IrDA, dedicated short range communication (DSRC), EnOcean, and/or any other suitable common or proprietary wireless protocol, as desired.
In some cases, an application program code (i.e. app) stored in the memory of the remote device 62 may be used to remotely access and/or control the HVAC controller 18. The application program code (app) may be downloaded from an external web service, such as the web service hosted by the external web server 66 (e.g. Honeywell's TOTAL CONNECT™ web service) or another external web service (e.g. ITUNES® or Google Play). In some cases, the app may provide a remote user interface for interacting with the HVAC controller 18 at the user's remote device 62. For example, through the user interface provided by the app, a user may be able to change operating parameter settings such as, for example, temperature set points, humidity set points, start times, end times, schedules, window frost protection settings, accept software updates and/or the like. Communications may be routed from the user's remote device 62 to the web server 66 and then, from the web server 66 to the HVAC controller 18. In some cases, communications may flow in the opposite direction such as, for example, when a user interacts directly with the HVAC controller 18 to change an operating parameter setting such as, for example, a schedule change or a set point change. The change made at the HVAC controller 18 may be routed to the web server 66 and then from the web server 66 to the remote device 62 where it may reflected by the application program executed by the remote device 62.
In some cases, a user may be able to interact with the HVAC controller 18 via a user interface provided by one or more web pages served up by the web server 66. The user may interact with the one or more web pages using a variety of internet capable devices to effect a setting or other change at the HVAC controller 18, and in some cases view usage data and energy consumption data related to the usage of the HVAC system 4. In some cases, communication may occur between the user's remote device 62 and the HVAC controller 18 without being relayed through a server such as external server 66. These are just some examples.
In some instances, the programmable schedule may be known as a 7 day schedule, in which each of the seven days of the week may be uniquely programmed but are not required to be. In some cases, the programmable schedule may be known as a 5-2 schedule, in which each of the weekdays Monday through Friday share a first programming schedule and the weekend days Saturday and Sunday share a second programming schedule. In some cases, the programmable schedule may be known as a 5-1-1 schedule, in each of the weekdays Monday through Friday share a first programming schedule, and Saturday and Sunday each can have their own unique schedule.
In some cases, the HVAC controller 90 may include a housing 92. In some instances, the housing 92 may be considered as forming the outer structure of the thermostat 82 (e.g. see
In some cases, the controller 98 may be configured to permit a user to navigate through a linearly ordered series of screens on the touch screen display 94 to sequentially display one or more of the plurality of schedule periods of the programmable schedule, wherein each displayed schedule period screen includes a plurality of schedule parameters concurrently displayed on the touch screen display 94 that, as will be discussed, can be individually selected by the user for editing by touching the corresponding schedule parameter via the touch screen display 94. In some cases, a linearly ordered series of screens may pertain to a series of screens, each pertaining to a single day, showing several schedule parameters on the screen. For example, a first screen showing one or more schedule parameters for Monday, followed by a second screen showing one or more schedule parameters for Tuesday, and so on. The one or more schedule parameters shown for Tuesday may be the same schedule parameters (although they may have different values) as the one or more schedule parameters shown for Monday, for example, although they do not have to be. In some cases, a linearly ordered series of screens may pertain to a sequential series of screens, each showing a particular time period within a single day (or a group of days such as MON-FRI, or SAT-SUN), showing several schedule parameters pertaining to that particular time period. For example, a first screen may show schedule parameters for a WAKE period on a Thursday, followed by a second screen showing schedule parameters for an AWAY period on Thursday, and so on. In some cases, a linearly ordered series of screens may pertain to a sequential series of screens, each showing a particular time period within a single day, showing several schedule parameters pertaining to that particular time period, and after the screens that pertain to the day (or group of days) are displayed, a similar series of screens may be displayed for the following day (or group of days), and so on.
In some cases, a user may be able to move sequentially through the screens, Monday to Tuesday, Tuesday to Wednesday, and so on. In some cases as illustrated, each of the screens 100, 102, 104 also display a back arrow 114 and a forward arrow 116. A user may sequentially scroll through the screens 100, 102, 104 (and others) simply by pressing the back arrow 114 and/or the forward arrow 116. For example, if currently viewing the screen 100, pressing the forward arrow 116 will cause the screen 102 to appear on the touch screen display 94. If currently viewing the screen 102, pressing the back arrow 114 will cause the screen 100 to reappear on the touch screen display 94. If currently viewing the screen 102, pressing the forward arrow 116 will cause a subsequent screen, for Wednesday as the date parameter 106, to appear.
It will be appreciated that the day parameter 106 may display a single day of the week, or may display a range of days. For example, in a seven day programmable schedule, each day of the week may be uniquely programmed and thus the day parameter 106 may display a single day of the week. In a five-two programmable schedule, the five weekdays Monday through Friday are not uniquely programmed, and in these cases the day parameter 106 may for example display “MON-FRI”.
In some cases, the controller 98 is configured to permit the user to edit the selected schedule parameter and then to navigate to another of the plurality of schedule periods of the programmable schedule after selecting and/or editing a selected schedule parameter. This may be seen, for example, in
In some cases, as seen for example in
As discussed with respect to
In some cases, a user may scroll sequentially through several time periods for a single day (or group of days) by pressing the back arrow 114 and/or the forward arrow 116, as desired. This is illustrated for example in
In
In some cases, the P1 indicator 136 may be selected by simply pressing the P1 indicator 136, particularly if the P1 indicator 136 corresponds to a touch point on the screen 94. In some instances, the P1 indicator 136 may be selected by moving forward or backwards from a display displaying a different time period by pressing the back arrow 114 and/or the forward arrow 116, as desired. For example, from the screen 130 shown in
It will be appreciated that
In some cases, the home screen 150 as shown in
Across the center of the home screen 150, the HVAC controller 90 may be seen as displaying a current temperature icon 158 and a current temperature setpoint icon 160. In some cases, the current temperature icon 158 is displayed in a larger or otherwise more noticeable font so that the user can easily read the current temperature. Display of the current temperature setpoint icon 160 provides the user with quick verification that the system is working correctly, i.e., that the current temperature matches the temperature setpoint. This also enables the user to see, via display of the current temperature setpoint, if the current temperature setpoint is as expected. For example, if the HVAC controller 90 is operating under a programmable schedule that expects the house to be empty at a particular time of day, the temperature setpoint may be chosen more for energy efficiency than for comfort. If a person has unexpectedly stayed home that day, they will be able to see that the temperature setpoint has been automatically adjusted for energy efficiency, and they can temporarily adjust the temperature setpoint to maintain their comfort without waiting for the house temperature to drop (or increase) to that energy efficient setting.
The illustrative home screen 150 also includes a mode icon 162 that informs the user what mode the system is in, such as heat mode (as illustrated), cool mode, or system off. A fan icon 164 informs the user as to what mode the system fan is in. In some cases, the fan mode may be AUTO, meaning that the fan only runs when the conditioning equipment (e.g. heater, air conditioner, humidifier, etc.) is running. If the system is in heat mode (as shown), for example, having the fan mode in AUTO means the fan will only run when the furnace burner is running (plus a short time period before burner ignition and a short time period after the burner goes off). If in cool mode, and the fan mode is AUTO, the fan will only run when the air conditioning is running (plus a short time period after the air conditioner goes off). In some cases, the fan mode may be ON, in which case the fan runs continuously to help circulate air within the house, or perhaps to accommodate an air exchanger. A MINUS button 166 and a PLUS button 168, which may for example represent the previously discussed MINUS button 124 (
Across the bottom of the home screen 150, the HVAC controller 90 may be seen as displaying a MODE button 170, a MENU button 172 and a FAN button 174. In some cases, the MODE button 170, the MENU button 172 and/or the FAN button 174 may each coincide with touch points formed within the touch screen display 94. It will be appreciated that in some cases, the MODE button 170 may, for example, be used to change the system from heat mode to cool mode, or cool mode to heat mode, or from heat mode to OFF or from cool mode to OFF. The FAN button 174 may be used to change the fan mode from ON to AUTO, or from AUTO to ON, for example. The MENU button 172 enables a user to reach various menus that are programmed into the HVAC controller 90 and thus can be displayed on the display 94. In some cases, one of the menus that may be reached via the MENU button 172 is a schedule menu, an example of which is shown in
The SCHEDULE screen 182 may, for example, include a back button 188 that enables the user to return to the home screen 150. A select button 190 enables the user to instruct the HVAC controller 90 to enter the scheduling menu so that the user can make any desired changes to the programmable schedule. In some cases, it will be appreciated that the back button 188 and the select button 190 each coincide with touch points formed in the touch screen display 94. In some cases, the back button 188 may largely share a location with the MODE button 170 (
In a schedule in which weekdays are all treated identically, the PERIOD SELECTOR identifier 202 may display a range of days, such as MON-FRI, or M-F, as illustrated. In other schedules, for example, in a seven day schedule, a single day of the week may be displayed, such as MON, or TUES, as appropriate. As can be seen, the PERIOD SELECTOR identifier 202 also indicates a currently displayed PERIOD. As seen in the screen 200, the WAKE period has been identified. In some cases, particularly if a total of four time periods are being used, the PERIOD SELECTOR identifier 202 may alternately read WAKE, AWAY, HOME and SLEEP, as appropriate. The screen includes the BACK button 184 and the FORWARD button 186 that may be used, for example, to advance between adjacent screens, as shown in
The back button 188 enables the user to return a previous screen, such as but not limited to, the home screen 150. The select button 190 enables the user to instruct the HVAC controller 90 to enter the scheduling menu so that the user can make any desired changes to the programmable schedule. The screen 200 includes a SCHED ON/OFF button 228. In some cases, the SCHED ON/OFF button 228 may be used if a user wishes to not operate in accordance with a schedule, but rather just wants to run the HVAC controller 90 manually (or in accordance with a geo-fence capability if provided). If they are hot, they turn down the temperature. If cold, they turn it up. Comparing
From the screen 200, pressing the FORWARD button 186 may cause the HVAC controller 90 to display a screen 230, as seen in
If a user wishes to edit one of the displayed parameters, they may simply press the desired icon. For example, pressing the TIME icon 244 may cause the HVAC controller 90 to display a screen 260, as shown in
In some cases, pressing the select button 190 also causes the HVAC controller 90 to move on and display an active set point.
In
It should be understood that this disclosure is, in many respects, only illustrative. Changes may be made in details, particularly in matters of shape, size, and arrangement of steps without exceeding the scope of the disclosure. This may include, to the extent that it is appropriate, the use of any of the features of one example embodiment being used in other embodiments.
Number | Name | Date | Kind |
---|---|---|---|
3656112 | Paul | Apr 1972 | A |
3900842 | Calabro et al. | Aug 1975 | A |
4079366 | Wong | Mar 1978 | A |
4174807 | Smith et al. | Nov 1979 | A |
4206872 | Levine | Jun 1980 | A |
4215408 | Games et al. | Jul 1980 | A |
4224615 | Penz | Sep 1980 | A |
4235368 | Neel | Nov 1980 | A |
4264034 | Hyltin et al. | Apr 1981 | A |
4267966 | Neel et al. | May 1981 | A |
4270573 | Sturman et al. | Jun 1981 | A |
4296334 | Wong | Oct 1981 | A |
4298946 | Hartsell et al. | Nov 1981 | A |
4308991 | Peinetti et al. | Jan 1982 | A |
4337822 | Hyltin et al. | Jul 1982 | A |
4357665 | Korff | Nov 1982 | A |
4382544 | Stewart | May 1983 | A |
4386649 | Hines et al. | Jun 1983 | A |
4388692 | Jones et al. | Jun 1983 | A |
4399510 | Hicks | Aug 1983 | A |
4429299 | Kabat et al. | Jan 1984 | A |
4431134 | Hendricks et al. | Feb 1984 | A |
4442972 | Sahay et al. | Apr 1984 | A |
4446913 | Krocker | May 1984 | A |
4479604 | Didner | Oct 1984 | A |
4506827 | Jamieson et al. | Mar 1985 | A |
4510398 | Culp et al. | Apr 1985 | A |
4511979 | Amirante | Aug 1985 | A |
4551812 | Gurr et al. | Nov 1985 | A |
4556865 | Fukagawa et al. | Dec 1985 | A |
4591988 | Klima et al. | May 1986 | A |
4606401 | Levine et al. | Aug 1986 | A |
4608560 | Allgood | Aug 1986 | A |
4621336 | Brown | Nov 1986 | A |
4622544 | Bially et al. | Nov 1986 | A |
4630670 | Wellman et al. | Dec 1986 | A |
4642607 | Strom et al. | Feb 1987 | A |
4657179 | Aggers et al. | Apr 1987 | A |
4656835 | Kiddler | Aug 1987 | A |
4717333 | Carignan | Jan 1988 | A |
4725001 | Carney et al. | Feb 1988 | A |
4730941 | Levine et al. | Mar 1988 | A |
4742475 | Kaiser et al. | May 1988 | A |
4771185 | Feron et al. | Sep 1988 | A |
4783800 | Levine | Nov 1988 | A |
4819714 | Otsuka et al. | Apr 1989 | A |
4837731 | Levine et al. | Jun 1989 | A |
4881686 | Mehta | Nov 1989 | A |
4909041 | Jones | Mar 1990 | A |
4916328 | Culp, III | Apr 1990 | A |
4918439 | Wozniak et al. | Apr 1990 | A |
4924404 | Reinke, Jr. | May 1990 | A |
4948040 | Kobayashi et al. | Aug 1990 | A |
4992779 | Sugino et al. | Feb 1991 | A |
4997029 | Otsuka et al. | Mar 1991 | A |
5003457 | Ikei et al. | Mar 1991 | A |
5012973 | Dick et al. | May 1991 | A |
5038851 | Mehta | Aug 1991 | A |
5053752 | Epstein et al. | Oct 1991 | A |
5065813 | Berkeley et al. | Nov 1991 | A |
5086385 | Launey et al. | Feb 1992 | A |
5088645 | Bell | Feb 1992 | A |
5107918 | McFarlane et al. | Apr 1992 | A |
5140310 | DeLuca et al. | Aug 1992 | A |
5153837 | Shaffer et al. | Oct 1992 | A |
5161606 | Berkeley et al. | Nov 1992 | A |
5170935 | Federspiel et al. | Dec 1992 | A |
5181653 | Foster et al. | Jan 1993 | A |
5230482 | Ratz et al. | Jul 1993 | A |
5238184 | Adams | Aug 1993 | A |
5251813 | Kniepkamp | Oct 1993 | A |
5259445 | Pratt et al. | Nov 1993 | A |
5270952 | Adams et al. | Dec 1993 | A |
5289362 | Liebl et al. | Feb 1994 | A |
5329991 | Mehta et al. | Jul 1994 | A |
5348078 | Dushane et al. | Sep 1994 | A |
5386577 | Zenda | Jan 1995 | A |
5392042 | Pellon | Feb 1995 | A |
5395042 | Riley et al. | Mar 1995 | A |
5412377 | Evans et al. | May 1995 | A |
5461558 | Patsiokas et al. | Oct 1995 | A |
5481481 | Frey et al. | Jan 1996 | A |
5482209 | Cochran et al. | Jan 1996 | A |
5526422 | Keen | Jun 1996 | A |
5537106 | Mitsuhashi | Jul 1996 | A |
5544036 | Brown, Jr. et al. | Aug 1996 | A |
5566879 | Longtin | Oct 1996 | A |
5570837 | Brown et al. | Nov 1996 | A |
5644173 | Elliason et al. | Jul 1997 | A |
5673850 | Uptegraph | Oct 1997 | A |
5782296 | Mehta | Jul 1998 | A |
5802467 | Salazar et al. | Sep 1998 | A |
5818428 | Eisenbrandt et al. | Oct 1998 | A |
5873519 | Beilfuss | Feb 1999 | A |
5886697 | Naughton et al. | Mar 1999 | A |
5901183 | Garin et al. | May 1999 | A |
5902183 | D'Souza | May 1999 | A |
5909378 | De Milleville | Jun 1999 | A |
5937942 | Bias et al. | Aug 1999 | A |
5947372 | Tiernan | Sep 1999 | A |
6009355 | Obradovich et al. | Dec 1999 | A |
6020881 | Naughton et al. | Feb 2000 | A |
6032867 | Dushane et al. | Mar 2000 | A |
6059195 | Adams et al. | May 2000 | A |
6081197 | Garrick et al. | Jun 2000 | A |
6121875 | Hamm et al. | Sep 2000 | A |
6140987 | Stein et al. | Oct 2000 | A |
6144971 | Sunderman et al. | Nov 2000 | A |
6192282 | Smith et al. | Feb 2001 | B1 |
6196467 | Dushane et al. | Mar 2001 | B1 |
6208331 | Singh et al. | Mar 2001 | B1 |
6236326 | Murphy | May 2001 | B1 |
6256378 | Iggulden et al. | Jul 2001 | B1 |
6285912 | Ellison et al. | Sep 2001 | B1 |
6290140 | Pesko et al. | Sep 2001 | B1 |
6305611 | Proffitt et al. | Oct 2001 | B1 |
6315211 | Sartain et al. | Nov 2001 | B1 |
6318639 | Toth | Nov 2001 | B1 |
6323882 | Jerome et al. | Nov 2001 | B1 |
6330806 | Beaverson et al. | Dec 2001 | B1 |
6344861 | Naughton et al. | Feb 2002 | B1 |
6351693 | Monie et al. | Feb 2002 | B1 |
6398118 | Rosen et al. | Jun 2002 | B1 |
6478233 | Shah | Nov 2002 | B1 |
6502758 | Cottrell | Jan 2003 | B2 |
6518957 | Lehtinen et al. | Feb 2003 | B1 |
6553777 | Dillenback | Apr 2003 | B2 |
6578770 | Rosen | Jun 2003 | B1 |
6580950 | Johnson et al. | Jun 2003 | B1 |
6581848 | Plica | Jun 2003 | B1 |
6595430 | Shah | Jul 2003 | B1 |
6619555 | Rosen | Sep 2003 | B2 |
6621507 | Shah | Sep 2003 | B1 |
6628997 | Fox et al. | Sep 2003 | B1 |
6658303 | Hatemata | Dec 2003 | B2 |
6685098 | Okano et al. | Feb 2004 | B2 |
6687678 | Yorimatsu et al. | Feb 2004 | B1 |
6718213 | Enberg | Apr 2004 | B1 |
6782706 | Holmes et al. | Aug 2004 | B2 |
6783079 | Carey et al. | Aug 2004 | B2 |
6786421 | Rosen | Sep 2004 | B2 |
6789739 | Rosen | Sep 2004 | B2 |
6824069 | Rosen | Nov 2004 | B2 |
6833990 | LaCroix et al. | Dec 2004 | B2 |
6845918 | Rotondo | Jan 2005 | B2 |
6851621 | Wacker et al. | Feb 2005 | B1 |
6886754 | Smith et al. | May 2005 | B2 |
6975958 | Bohrer et al. | Dec 2005 | B2 |
6983889 | Alles | Jan 2006 | B2 |
6997390 | Alles | Feb 2006 | B2 |
7001495 | Essalik | Feb 2006 | B2 |
D518744 | Rosen | Apr 2006 | S |
7028912 | Rosen | Apr 2006 | B1 |
7050026 | Rosen | May 2006 | B1 |
7089066 | Hesse et al. | Aug 2006 | B2 |
7114554 | Bergman et al. | Oct 2006 | B2 |
7130719 | Ehlers et al. | Oct 2006 | B2 |
7142948 | Metz | Nov 2006 | B2 |
7146253 | Hoog et al. | Dec 2006 | B2 |
7152802 | Kell et al. | Dec 2006 | B2 |
7152806 | Rosen | Dec 2006 | B1 |
7156318 | Rosen | Jan 2007 | B1 |
7302642 | Smith et al. | Nov 2007 | B2 |
7306165 | Shah | Dec 2007 | B2 |
7310559 | Walko, Jr. | Dec 2007 | B2 |
7320110 | Shah | Jan 2008 | B2 |
7455240 | Chapman, Jr. et al. | Nov 2008 | B2 |
7460933 | Chapman, Jr. et al. | Dec 2008 | B2 |
7556207 | Mueller | Jul 2009 | B2 |
7604046 | Bergman et al. | Oct 2009 | B2 |
7624931 | Chapman, Jr. et al. | Dec 2009 | B2 |
7636604 | Bergman et al. | Dec 2009 | B2 |
D610027 | Li et al. | Feb 2010 | S |
7693582 | Bergman et al. | Apr 2010 | B2 |
7706923 | Amundson et al. | Apr 2010 | B2 |
7861941 | Schultz et al. | Jan 2011 | B2 |
7890195 | Bergman et al. | Feb 2011 | B2 |
8032254 | Amundson et al. | Oct 2011 | B2 |
8083154 | Schultz et al. | Dec 2011 | B2 |
8219251 | Amundson | Jul 2012 | B2 |
8244383 | Bergman et al. | Aug 2012 | B2 |
8306669 | Smith et al. | Nov 2012 | B1 |
8346396 | Amundson | Jan 2013 | B2 |
8523084 | Siddaramanna et al. | Sep 2013 | B2 |
8527096 | Pavlak et al. | Sep 2013 | B2 |
8620460 | Bergman et al. | Dec 2013 | B2 |
8893032 | Bruck et al. | Nov 2014 | B2 |
9014860 | Moore et al. | Apr 2015 | B2 |
9026253 | Majewski et al. | May 2015 | B2 |
9081393 | Lunacek et al. | Jul 2015 | B2 |
9388998 | Khoury et al. | Jul 2016 | B2 |
20010029585 | Simon et al. | Oct 2001 | A1 |
20010052459 | Essalik et al. | Dec 2001 | A1 |
20020085037 | Leavitt | Jul 2002 | A1 |
20020092779 | Essalik et al. | Jul 2002 | A1 |
20030034897 | Shamoon et al. | Feb 2003 | A1 |
20030034898 | Shamoon et al. | Feb 2003 | A1 |
20040245352 | Smith | Dec 2004 | A1 |
20040260411 | Cannon | Dec 2004 | A1 |
20040262410 | Hull | Dec 2004 | A1 |
20050108091 | Sotak et al. | May 2005 | A1 |
20050119766 | Amundson et al. | Jun 2005 | A1 |
20060004492 | Terlson et al. | Jan 2006 | A1 |
20060030954 | Bergman | Feb 2006 | A1 |
20070029397 | Mueller et al. | Feb 2007 | A1 |
20070045441 | Ashworth et al. | Mar 2007 | A1 |
20070228182 | Wagner et al. | Oct 2007 | A1 |
20070257120 | Chapman, Jr. et al. | Nov 2007 | A1 |
20090045263 | Mueller et al. | Feb 2009 | A1 |
20090140056 | Leen | Jun 2009 | A1 |
20100106305 | Pavlak et al. | Apr 2010 | A1 |
20120318135 | Hoglund et al. | Dec 2012 | A1 |
20130027412 | Roddy | Jan 2013 | A1 |
20130060385 | Leen | Mar 2013 | A1 |
20130158720 | Zywicki | Jun 2013 | A1 |
20130227413 | Thorsander | Aug 2013 | A1 |
20130338838 | Moore | Dec 2013 | A1 |
20130345882 | Dushane | Dec 2013 | A1 |
20140118285 | Poplawski | May 2014 | A1 |
20140316581 | Fadell | Oct 2014 | A1 |
20140321092 | Novotny et al. | Oct 2014 | A1 |
20140324229 | Leen et al. | Oct 2014 | A1 |
20150094865 | Choi | Apr 2015 | A1 |
20150204569 | Lorenz et al. | Jul 2015 | A1 |
20150327084 | Ramachandran et al. | Nov 2015 | A1 |
20150355371 | Ableitner et al. | Dec 2015 | A1 |
20160018127 | Gourlay et al. | Jan 2016 | A1 |
20160209072 | Golden et al. | Jul 2016 | A1 |
Number | Date | Country |
---|---|---|
3334117 | Apr 1985 | DE |
0070414 | Jan 1983 | EP |
0678204 | Mar 2000 | EP |
0985994 | Mar 2000 | EP |
1033641 | Sep 2000 | EP |
1074009 | Feb 2001 | EP |
2711230 | Apr 1995 | FR |
WO 9711448 | Mar 1997 | WO |
WO 9739392 | Oct 1997 | WO |
WO 0152515 | Jul 2001 | WO |
WO 0179952 | Oct 2001 | WO |
Entry |
---|
“A Full Range of Alternative User Interfaces for Building Occupants and Operators,” http://www.automatedbuildings.com/news/jan00/articles/andover/andover.htm, 5 pages, dated Jan. 2000, printed Sep. 20, 2004. |
“CorAccess Systems/in Home,” http://web.archive.org/web20011212084427/www.coraccess.com/home.html, 1 page, copyright 2001, printed Aug. 19, 2004. |
“HAI Company Background,” http://www.homeauto.com/AboutHAI/abouthai_main.htm, 2 pages, printed Aug. 19, 2004. |
“High-tech options take hold in new homes—200-08-28—Dallas Business Journal,” http://bizjournals.com/dallas/stories/2000/08/28/focus4, 3 pages, dated Aug. 28, 2000, printed Aug. 19, 2004. |
“Home Toys Review—TouchLinc”, http://www.hometoys.com/htinews/aug99/reviews/touchlinc/touchlinc.htm, 3 pages, dated Aug. 1999, printed Autust 20, 2004. |
“Mark of Excellence Award Finalist Announced,” http://64.233.167.104/search?Q=cache:ciOA2YtYaBIJ:www.hometoys.com/releases/mar. . . , 6 pages, Leopard Touchscreen on p. 2, dated prior to Mar. 4, 2000, printed Aug. 20, 2004. |
“Product Review—Philips Pronto Remote Control,” http://hometheaterhifi.com/volume_6_2/philipsprontoremotecontrol.html, 5 pages, dated May 1999, printed Aug. 20, 2004. |
“RC X10 Automation Forum: Control your Heating and Cooling System with Pronto(1/1),” http://www.remotecentral.com/cgi-bin/mboard/rc-x10/thread.cgi?12, 2 pages, dated Apr. 23, 1999, printed Aug. 20, 2004. |
“Spotlight on integrated systems,” Custom Builder, vol. 8, No. 2, p. 66(6), Mar.-Apr. 1993. |
ADI, “Leopard User Manual,” 93 pages, 2001. |
Adicon 2500, “The Automator,” 4 pages, Oct.-Dec. 2000. |
ADT Security Services, “iCenter Advanced User Interface 8142ADT,” Installation and Setup Guide, 5 pages, May 2001; First Sale Feb. 2001. |
ADT Security Systems, “iCenter Advanced User Interface 8142ADT User Guide,” pp. 1-136, 2001. |
Aprilaire Electronic Thermostats Models 8344, 8346, 8348, 8363, 8365, 8366 Operating Instructions, 8 pages, 2003. |
Aube Technologies, Electronic Thermostat for Heating System Model TH135-01, 5 pages, Aug. 14, 2001. |
Aube Technologies, TH140-28 Electronic Programmable Thermostat, Installation Instructions and User Guide, pp. 1-4, Jan. 22, 2004. |
Blake et al., “Seng 310 Final Project Demo Program” Illustration, 3 pages, Apr. 6, 2001. |
Blake et al., “Seng 310 Final Project” Report, dated Apr. 6, 2001. |
Blister Pack Insert from a Ritetemp 8082 Touch Screen Thermostat Product, 2 pages, 2002. |
Braeburn Model 3000 Owner's Manual, pp. 1-13, 2001. |
Braeburn Model 5000 Owners Manual, pp. 1-17, 2001. |
BRK Electronics Maximum Protection Plus Ultimate Convenience Smoke Alarm, 24 pages, Sep. 2000. |
BRK First Alert, User's Manual, Smoke and Fire Alarms, pp. 1-7, Nov. 2002. |
Business Wire, “MicroTouch Specialty Products Group to Capitalize on Growing Market for Low-Cost Digital Matrix Touchscreens,” p1174 (2 pages), Jan. 6, 1999. |
Cardio Manual, available at http://www.secant.ca/En/Documentation/Cardio2é-Manual.pdf, Cardio Home Automation Inc., 55 pages, printed Sep. 28, 2004. |
Cardio, by Secant; http://www.hometoys.com/htinews/apr98/reviews/cardio.htm, “HTINews Review,” Feb. 1998, 5 pages, printed Sep. 14, 2004. |
Carrier Microelectronic Programmable Thermostat Owner's Manual, pp. 1-24, May 1994. |
Carrier TSTATCCRFO1 Programmable Digital Thermostat, pp. 1-21, prior to Apr. 21, 2005. |
Carrier, “Programmable Dual Fuel Thermostat,” Installation, Start-Up & Operating Instructions, pp. 1-12, Oct. 1998. |
Carrier, “Programmable Thermostats,” Installation, Start-Up & Operating Instructions, pp. 1-16, Sep. 1998. |
Carrier, “Standard Programmable Thermostat,” Homeowner's Manual, pp. 1-8 pages, 1998. |
Carrier, “Thermidistat Control,” Installation, Start-Up, and Operating Instructions, pp. 1-12, Aug. 1999. |
Climatouch, User Manual, Climatouch CT03TSB Thermostat, Climatouch CT03TSHB Thermostat with Humidity Control, Outdoor UHF Temperature Transmitter 217S31, 19 pages, printed Sep. 15, 2004. |
CorAccess, “Companion 6,” User Guide, pp. 1-20, Jun. 17, 2002. |
Danfoss RT51/51RF & RT52/52RF User Instructions, 2 pages, Jun. 2004. |
DeKoven et al., “Designing Collaboration in Consumer Products,” 2 pages, 2001. |
DeKoven et al., “Measuring Task Models in Designing Intelligent Products,” 2 pages, Jan. 13-16 2002. |
Domotique Secant Home Automation—Web Page, available at http://www.secant.ca/En/Company/Default.asp, 1 page, printed Sep. 28, 2004. |
Firex Smoke Alarm, Ionization Models AD, ADC Photoelectric Model Pad, 4 pages, prior to Apr. 21, 2005. |
Freudenthal et al., “Communicating extensive smart home functionality to users of all ages: the design of a mixed-initiative multimodal thermostat-interface,” pp. 34-39, Mar. 12-13, 2001. |
Gentex Corporation, HD135, 135° Fixed Temperature Heat Detector AC Powered, 120V, 60Hz with Battery Backup, Installation Instructions—Owner's Information, pp. 1-5, Jun. 1, 1998. |
Gentex Corporation, 9000 Series, Photoelectric Type Single Station/Multi-Station Smoke Alarms AC Powered with Battery Backup, Installation Instructions—Owner's Information, pp. 9-1 to 9-6, Jan. 1, 1993. |
Home Automation, Inc., “OmniPro Owner's Manual,” 153 pages, prior to Dec. 27, 2010. |
Home Automation, Inc., “OmniTouch Touchscreen Model 32A00-1, Uses Guide,” Document No. 32R00-1 Rev A, 15 pages, Aug. 2003. |
Honeywell Brivis Deluxe Programmable Thermostat, pp. 1-20, 2002. |
Honeywell Brivis T8602C Chronotherm IV Deluxe Programmable Thermostats, Installation Instructions, pp. 1-12, 2002. |
Honeywell CT8602C Professional Fuel Saver Thermostat, pp. 1-6, 1995. |
Honeywell Electronic Programmable Thermostat, Owner's Guide, pp. 1-20, 2003. |
Honeywell Electronic Programmable Thermostats, Installation Instructions, pp. 1-8, 2003. |
Honeywell News Release, “Honeywell's New Sysnet Facilities Integration System for Boiler Plant and Combustion Safety Processes,” 4 pages, Dec. 15, 1995. |
Honeywell T8002 Programmable Thermostat, Installation Instructions, pp. 1-8, 2002. |
Honeywell T8602A,B,C,D and TS8602A.0 Chronotherm Ill Fuel Saver Thermostats, Installation Instructions, pp. 1-12, 1995. |
Honeywell T8602D Chronotherm IV Deluxe Programmable Thermostats, Installation Instructions, pp. 1-12, 2002. |
Honeywell TH8000 Series Programmable Thermostats, Owner's Guide, pp. 1-44, 2004. |
Honeywell, “Excel Building Supervisor-Integrated R7044 and FS90 Ver. 2.0,” Operator Manual, 70 pages, Apr. 1995. |
Honeywell, “FocusPRO TH6000 Series Programmable Thermostat, Operating Manual,” 26 pages, Mar. 2011. |
Honeywell, “Introduction of the S7350A Honeywell WebPAD Information Appliance,” Home and Building Control Bulletin, 2 pages, Aug. 29, 2000; Picture of WebPad Device with touch screen, 1 Page; and screen shots of WebPad Device, 4 pages. |
Honeywell, “W7006A Home Controller Gateway User Guide,” 31 pages, Jul. 2001. |
Honeywell, MagicStat® CT3200 Programmable Thermostat, Installation and Programming Instructions, pp. 1-24, 2001. |
http://www.cc.gatech.edu/computing/classes/cs6751_94_fall/groupc/climate-2/nodel.html, “Contents,” 53 pages, printed Sep. 20, 2004. |
http://www.hometoys.com/htinews/apr99/releases/ha101.htm, HTI News Release, pp. 1-3, printed Oct. 28, 2004. |
http://www.ritetemp.info/rtMenu_13.html, Rite Temp 8082, 8 pages, printed Jun. 20, 2003. |
http://www.thermostatsales.com, Robertshaw, “9610 Digital Programmable Thermostat,” 3 pages, printed Jun. 17, 2004. |
http://www.thermostatsales.com, Robertshaw, “9700 Deluxe Programmable Thermostat” 3 pages, printed Jun. 17, 2004. |
http://www.thermostatsales.com, Robertshaw, “9710 Deluxe Programmable Thermostat,” 3 pages, printed Jun. 17, 2004. |
http://www.thermostatsales.com, Robertshaw, “9720 Deluxe Programmable Thermostat,” 3 pages, printed Jun. 17, 2004. |
Hunter, “44200/44250,” Owner's Manual, 32 pages, prior to Jul. 7, 2004. |
Hunter, “44300/44350,” Owner's Manual, 35 pages, prior to Jul. 7, 2004. |
Hunter, “Auto Saver 550”, Owner's Manual Model 44550, 44 pages, prior to Jul. 7, 2004. |
Install Guide for Ritetemp Thermostat 8082, 6 pages, 2002. |
Invensys™, “9700i 9701i 9715i 9720i Deluxe Programmable Thermostats,” User's Manual, pp. 1-28, prior to Jul. 7, 2004. |
Lennox User's Manual, “Network Control Panel (NCP),” pp. 1-18, Nov. 1999. |
Lux ELV1 Programmable Line Voltage Thermostat, Installation Instructions, 3 pages, prior to Jul. 7, 2004. |
Lux TX500 Series Smart Temp Electronic Thermostat, 3 pages, prior to Jul. 7, 2004. |
Lux TX9000 Installation, 3 pages, prior to Apr. 21, 2005. |
Lux, “511 Series Smart Temp Electronic Thermostat,” Owner's Manual, 3 pages, prior to Jul. 7, 2004. |
Lux, “600 Series Smart Temp Electronic. Thermostat,” Owner's Manual, 3 pages, prior to Jul. 7, 2004. |
Lux, “602 Series Multi-Stage Programmable Thermostat,” Owner's Manual, 2 pages, prior to Jul. 7, 2004. |
Lux, “605/2110 Series Programmable Heat Pump Thermostat,” Owner's Manual, 3 pages, prior to Jul. 7, 2004. |
Lux, “700/9000 Series Smart Temp Electronic Thermostat,” Owner's Manual, 3 pages, prior to Jul. 7, 2004. |
Lux, “PSPH521 Series Programmable Heat Pump Thermostat,” Owner's Manual, 3 pages, prior to Jul. 7, 2004. |
Lux, “TX1500 Series Smart Temp Electronic Thermostat,” Owner's Manual, 6 pages, prior to Jul. 7, 2004. |
Matty, “Advanced Energy Management for Home Use”, in IEEE Transactions on Consumer Electronics, vol. 35, No. 3, Aug. 1989. |
Metasys, “HVAC PRO for Windows User's Manual,” 308 pages, 1998. |
Mounting Template for Ritetemp Thermostat 8082, 1 page, 2002. |
Proliphix, “Web Enabled IP Thermostats, Intelligent HVAC Control,” Proliphix Inc., 2 pages, on or before Aug. 28, 2004. |
Quick Start Guide for Ritetemp Thermostat 8082, 1 page, 2002. |
Remote Control Power Requirement for Ritetemp Thermostat 8082, 1 page, 2002. |
Raji, “Smart Networks for Control,” Jun. 1994, IEEE Spectrum. pp. 49-55. |
Ritetemp Operation 8029, 3 pages, Jun. 19, 2002. |
Ritetemp Operation 8050, 5 pages, Jun. 26, 2002. |
Ritetemp Operation 8085, pp. 1-6, prior to Apr. 21, 2005. |
Sealed Unit Parts Co., Inc., Supco & CTC Thermostats . . . loaded with features, designed for value!, 6 pages, prior to Apr. 21, 2005. |
Totaline Model P474-1035 Owner's Manual Programmable 5-2 Day Digital Thermostat, pp. 1-21, Apr. 2003. |
Totaline Star CPE230RF, Commercial Programmable Thermostat Wireless Transmitter, Owner's Manual, pp. 1-16, Oct. 1998. |
Totaline Star P/N P474-0130 Non-Programmable Digital Thermostat Owner's Manual, pp. 1-22, prior to Apr. 21, 2005. |
Totaline, “1 for All programmable Digital Thermostat,” Owner's Manual P/N P374-1100FM, 23 pages, Nov. 1998. |
Totaline, “1 for All Programmable Digital Thermostat,” Owner's Manual P/N P474-1050, 21 pages, Nov. 1998. |
Totaline, “1 for All Programmable Digital Thermostat,” Owner's Manual P/N P374-1100, 24 pages, Apr. 2001. |
Totaline, “Intellistat Combination Temperature and Humidity Control,” Owner's Manual P/N P374-1600, 25 pages, Jun. 2001. |
Totaline, “Programmable Thermostat Configurable for Advanced Heat Pump or Dual Fuel Operation,” Owner's Manual P/N P374-1500, 24 pages, Jun. 1999. |
Totaline, “Instructions P/N P474-1010”, Manual, 2 pages, Dec. 1998. |
Totaline, “Programmable Thermostat”, Homeowner's Guide, 27 pages, Dec. 1998. |
Totaline, “Wireless Programmable Digital Thermostat,” Owner's Manual 474-1100RF, 21 pages, 2000. |
Trane, “System Programming, Tracer Summit Version 14, BMTW-SVP01 D-EN,” 623 pages, 2002. |
Trouble Shooting Guide for Ritetemp Thermostat 8082, 1 page, 2002. |
Vantage Expands Controls for Audio/Video, HVAC and Security, http://www.hometoys.com/htinews/aug99/releases/vantage03.htm, 2 pages, dated Aug. 3, 1999, printed Aug. 20, 2004. |
Visor Handheld User Guide, 280 pages, Copyright 1999-2000. |
Warmly Yours, “Model TH111GFCI-P (120 VAC),” Manual, pp. 1-4, prior to Jul. 7, 2004. |
White-Rodgers 1F80-224 Programmable Electronic Digital Thermostat, Installation and Operation Instructions, 8 pages, prior to Apr. 21, 2005. |
White-Rodgers Comfort-Set III Thermostat, pp. 1-44, prior to Jul. 7, 2004. |
White-Rodgers Installation Instructions for Heating & Air Conditioning IF78 Non-Programmable Thermostat, 6 pages, prior to Apr. 21, 2005. |
White-Rodgers Installation Instructions for Heating & Air Conditioning IF78 5/2 Day Programmable Thermostat, 7 pages, prior to Jul. 7, 2004. |
White-Rodgers, “Installation Instructions for Heating & Air Conditioning IF72 5/2 Day Programmable Heat Pump Thermostat ” 8 pages, prior to Jul. 7, 2004. |
White-Rodgers, “Comfort-Set 90 Series Thermostat,” Manual, pp. 1-24, prior to Jul. 7, 2004. |
White-Rodgers, 1F80-240 “(for Heating Only systems) Programmable Electronic Digital Thermostat,” Installation and Operation Instructions, 8 pages, prior to Jul. 7, 2004. |
White-Rodgers, 1F80-241 “Programmable Electronic Digital Thermostat,” Installation and Operation Instructions, 6 pages, prior to Jul. 7, 2004. |
White-Rodgers, 1F80-261 “Programmable Electronic Digital Thermostat,” Installation and Operation Instructions, 8 pages, prior to Jul. 7, 2004. |
White-Rodgers, 1F81-261 “Programmable Electronic Digital Multi-Stage Thermostat,” Installation and Operation Instructions, 8 pages, prior to Jul. 7, 2004. |
White-Rodgers, 1F82-261 “Programmable Electronic Digital Heat Pump Thermostat,” Installation and Operation Instructions, 8 pages, prior to Jul. 7, 2004. |
White-Rodgers, Comfort-Set 90 Series Premium, 4 pages, prior to Apr. 21, 2005. |
www.icmcontrols.com, Simplecomfort, SC3000 Single Stage Heat/Single Stage Cool or Single Stage Heat Pump/Manual Changeover, 1 page, prior to Jul. 7, 2004. |
www.icmcontrols.com, Simplecomfort, SC3001 Single Stage Heat/Single Stage Cool or Single Stage Heat Pump/Manual Changeover, 1 page, prior to Jul. 7, 2004. |
www.icmcontrols.com, Simplecomfort, SC3006 Single Stage Heat/Single Stage Cool or Single Stage Heat Pump/Manual Changeover, 1 page, prior to Jul. 7, 2004. |
www.icmcontrols.com, Simplecomfort, SC3201 2 Stage Heat Pump Manual Changeover, 1 page, prior to Jul. 7, 2004. |
www.icmcontrols.com, Simplecomfort, SC3801 2 Stage Heat/2 Stage Cool 2 Stage Heat Pump/Audio Changeover, 1 page, prior to Jul. 7, 2004. |
Number | Date | Country | |
---|---|---|---|
20180023838 A1 | Jan 2018 | US |