SETUP ROUTINE TO FACILITATE USER SETUP OF AN HVAC CONTROLLER

TECHNICAL FIELD

This disclosure relates generally to HVAC systems, and more particularly, to HVAC controllers that may be used for controlling HVAC systems.

BACKGROUND

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 some cases, a user (typically a do-it-yourself homeowner) installing a new HVAC controller may have limited knowledge about the configuration of their existing HVAC system. This may present a challenge when configuring the new HVAC controller to control the various components of the existing HVAC system.

SUMMARY

This disclosure relates generally to HVAC systems, and more particularly, to HVAC controllers that may be used for controlling HVAC systems. In one illustrative embodiment, an HVAC controller configured to control one or more components of an HVAC system having a particular HVAC system configuration can include: a user interface including a display; a memory; and an output block for providing one or more control signals to the HVAC system. The output block can include a number or wiring terminals for accepting wires of the HVAC system. The wiring configuration between the wires of the HVAC system and the wiring terminals of the output block may be dependent on the particular HVAC system configuration of the HVAC system. When replacing an old HVAC controller with a new one, the wires that are available in the wall and/or were wired to the old HVAC controller provide information that may help determine the HVAC configuration of the HVAC system. The HVAC controller may further include a controller operatively coupled to the memory, the user interface and the output block. In some cases, the controller can be configured to display a guided-set up routine that includes two or more screens that guide a user to configure the new HVAC controller for controlling the particular HVAC system configuration of the HVAC system. At least one of the screens of the guided-set up routine can display a first selectable option and a second selectable option. The first selectable option may identify a first HVAC configuration setting and may further identify a first wiring configuration that corresponds to the first HVAC configuration setting. The second selectable option may identify a second HVAC configuration setting and may further identify a second wiring configuration that corresponds to the second HVAC configuration setting. In some cases, the first and second selectable options may be simultaneously displayed on a common screen.

In another illustrative embodiment, an HVAC controller configured to control one or more components of an HVAC system having a particular HVAC system configuration can include: a user interface including a display; a memory; and an output block for providing one or more control signals to the HVAC system. The output block can include a number or wiring terminals for accepting wires of the HVAC system. The wiring configuration between the wires of the HVAC system and the wiring terminals of the output block may be dependent on the particular HVAC system configuration of the HVAC system. The HVAC controller may further include a controller operatively coupled to the memory, the user interface and the output block. The controller may be configured to display one or more configuration screens used to configure the HVAC controller for controlling the particular HVAC system configuration, wherein at least one of the screens simultaneously displays a first selectable option and a second selectable option. The first selectable option may identify a first HVAC configuration setting, and the second selectable option may identify: (1) a second HVAC configuration setting; and (2) a wiring configuration that corresponds to the second HVAC configuration setting. In some instances, the first selectable option may also identify a wiring configuration that corresponds to the first HVAC configuration setting.

In another illustrative embodiment, an HVAC controller configured to control one or more components of an HVAC system having a particular HVAC system configuration can include: a user interface including a display; a memory; and an output block for providing one or more control signals to the HVAC system. The output block can include a number or wiring terminals for accepting wires of the HVAC system. In some cases, the wiring configuration between the wires of the HVAC system and the wiring terminals of the output block is dependent on the particular HVAC system configuration of the HVAC system. The HVAC controller may further include a controller operatively coupled to the memory, the user interface and the output block. The controller can be configured to display a guided-set up routine on the display having two or more screens that guide a user to configure the HVAC controller to control the particularly HVAC system configuration of the HVAC system. The guided-set up routine may solicit information from a user related to an equipment type contained in the particular HVAC system configuration as well information regarding the wiring configuration used by the user to wire the HVAC system to the wiring terminals of the output block of the HVAC controller. The controller can be configured to use the information related to the equipment type contained in the particular HVAC system configuration as well the information regarding the wiring configuration used by the user to wire the HVAC system to the wiring terminals of the output block to configure the HVAC controller to control the particular HVAC system configuration of the HVAC system.

The preceding summary is provided to facilitate an understanding of some of the innovative features unique to the present disclosure and is not intended to be a full description. A full appreciation of the disclosure can be gained by taking the entire specification, claims, drawings, and abstract as a whole.

BRIEF DESCRIPTION OF THE DRAWINGS

The disclosure may be more completely understood in consideration of the following description of various illustrative embodiments in connection with the accompanying drawings, in which:

FIG. 1 is a schematic view of an illustrative HVAC system servicing a building or structure;

FIG. 2 is a schematic view of an illustrative HVAC control system that may facilitate access and/or control of the HVAC system of FIG. 1;

FIG. 3 is a schematic block diagram of an illustrative HVAC controller;

FIG. 4 is a front, schematic view of an illustrative HVAC controller; and

FIG. 5-18 provide examples of illustrative screens that may be displayed to a user during a set-up process of the HVAC controller.

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 aspects of the disclosure to the particular illustrative embodiments described. On the contrary, the intention is to cover all modifications, equivalents, and alternatives falling within the spirit and scope of the disclosure.

DESCRIPTION

The following description should be read with reference to the drawings wherein like reference numerals indicate like elements throughout the several views. The description and drawings show several embodiments which are meant to illustrative in nature.

FIG. 1 is a schematic view of a building 2 having an illustrative heating, ventilation, and air conditioning (HVAC) system 4. While FIG. 1 shows a typical forced air type HVAC system, other types of HVAC systems are contemplated including, but not limited to, boiler systems, radiant heating systems, electric heating systems, cooling systems, heat pump systems, and/or any other suitable type of HVAC system, as desired. The illustrative HVAC system 4 of FIG. 1 includes one or more HVAC components 6, a system of ductwork and air vents including a supply air duct 10 and a return air duct 14, and one or more HVAC controllers 18. The one or more HVAC components 6 may include, but are not limited to, a furnace, a heat pump, an electric heat pump, a geothermal heat pump, an electric heating unit, an air conditioning unit, a humidifier, a dehumidifier, an air exchanger, an air cleaner, a damper, a valve, and/or the like.

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. When the communication link 20 is a wired communication link, the wiring configuration between the wires of the HVAC system 4 and the wiring terminals of the HVAC controller 18 will be dependent on the particular HVAC system configuration of the HVAC system 4. When replacing an old HVAC controller 18 with a new one, the wires that are available in the wall and/or were wired to the old HVAC controller may provide information that may help determine the HVAC configuration of the HVAC system 4.

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 a temperature sensor for sensing an 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 FIG. 1, the HVAC component(s) 6 may provide heated air (and/or cooled air) via the ductwork throughout the building 2. As illustrated, the HVAC component(s) 6 may be in fluid communication with every room and/or zone in the building 2 via the ductwork 10 and 14, but this is not required. In operation, when a heat call signal is provided by the HVAC controller(s) 18, an HVAC component 6 (e.g. forced warm air furnace) may be activated to supply heated air to one or more rooms and/or zones within the building 2 via supply air ducts 10. The heated air may be forced through supply air duct 10 by a blower or fan 22. In this example, the cooler air from each zone may be returned to the HVAC component 6 (e.g. forced warm air furnace) for heating via return air ducts 14. Similarly, when a cool call signal is provided by the HVAC controller(s) 18, an HVAC component 6 (e.g. air conditioning unit) may be activated to supply cooled air to one or more rooms and/or zones within the building or other structure via supply air ducts 10. The cooled air may be forced through supply air duct 10 by the blower or fan 22. In this example, the warmer air from each zone may be returned to the HVAC component 6 (e.g. air conditioning unit) for cooling via return air ducts 14. In some cases, the HVAC system 4 may include an internet gateway or other device 23 that may allow one or more of the HVAC components, as described herein, to communicate over a wide area network (WAN) such as, for example, the Internet.

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 FIG. 1, the air filter(s) 30 is installed in the return air duct 14, and may filter the air prior to the air entering the HVAC component 6, but it is contemplated that any other suitable location for the air filter(s) 30 may be used. The presence of the air filter(s) 30 may not only improve the indoor air quality, but may also protect the HVAC components 6 from dust and other particulate matter that would otherwise be permitted to enter the HVAC component.

In some cases, and as shown in FIG. 1, the illustrative HVAC system 4 may include an equipment interface module (EIM) 34. When provided, the equipment interface module 34 may be configured to measure or detect a change in a given parameter between the return air side and the discharge air side of the HVAC system 4. For example, the equipment interface module 34 may be adapted to measure a difference in temperature, flow rate, pressure, or a combination of any one of these parameters between the return air side and the discharge air side of the HVAC system 4. In some cases, the equipment interface module 34 may be adapted to measure the difference or change in temperature (delta T) between a return air side and discharge air side of the HVAC system 4 for the heating and/or cooling mode. The delta T for the heating mode may be calculated by subtracting the return air temperature from the discharge air temperature (e.g. delta T=discharge air temp.−return air temp.). For the cooling mode, the delta T may be calculated by subtracting the discharge air temperature from the return air temperature (e.g. delta T=return air temp.−discharge air temp.).

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 either cases, 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.

FIG. 2 is a schematic view of an HVAC control system 50 that facilitates remote access and/or control of the HVAC system 4 shown in FIG. 1, when desired. The illustrative HVAC control system 50 includes an HVAC controller, as for example, HVAC controller 18 (see FIG. 1) that is configured to communicate with and control one or more components 6 of the HVAC system 4. As discussed above, the HVAC controller 18 may communicate with the one or more components 6 of the HVAC system 4 via a wired or wireless link 20. Additionally, the HVAC controller 18 may be adapted to communicate over one or more wired or wireless networks that may accommodate remote access and/or control of the HVAC controller 18 via another device such as a smart phone, tablet, e-reader, laptop computer, personal computer, key fob, or the like. As shown in FIG. 2, the HVAC controller 18 may include a first communications port 52 for communicating over a first network 54, and in some cases, a second communications port 56 for communicating over a second network 58. In some cases, the first network 54 may be a wireless local area network (LAN), and the second network 58 (when provided) may be a wide area network or global network (WAN) including, for example, the Internet. In some cases, the wireless local area network 54 may provide a wireless access point and/or a network host device that is separate from the HVAC controller 18. In other cases, the wireless local area network 54 may provide a wireless access point and/or a network host device that is part of the HVAC controller 18. In some cases, the wireless local area network 54 may include a local domain name server (DNS), but this is not required for all embodiments. In some cases, the wireless local area network 54 may be an ad-hoc wireless network, but this is not required.

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 servers 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 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 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 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, 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 rather than or in addition to a local user interface at the HVAC controller 18. The application program code (app) may be provided for downloading from the external web service hosted by the external web server 66 (e.g. Honeywell's TOTAL CONNECT™ web service) to which the HVAC controller 18 may also be connected 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 the 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, configure or setup the HVAC controller, 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 local user interface of 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 other 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 change at the HVAC controller 18 as well as view usage data and energy consumption date related to the usage of the HVAC system 4. In still yet another case, communication may occur between the user's remote device 62 and the HVAC controller 18 without being relayed through a server. These are just some examples.

FIG. 3 is a schematic block diagram of illustrative HVAC controller 18. As discussed above with reference to FIG. 2, in some cases, the HVAC controller 18 may be accessed and/or controlled from a remote location over the first network 54 and/or the second network 58 using a remote wireless device 62 such as, for example, a smart phone, a tablet computer, a laptop or personal computer, a wireless network-enabled key fob, an e-reader, and/or the like. When so provided, and as shown in FIG. 3, the HVAC controller 18 may include a communications block 60 having a first communications port 52 for communicating over a first network (e.g. wireless LAN) and a second communications port 56 for communicating over a second network (e.g. WAN or the Internet). The first communications port 52 can be a wireless communications port including a wireless transceiver for wirelessly sending and/or receiving signals over a first wireless network 54. Similarly, the second communications port 56 may be a wireless communications port including a wireless transceiver for sending and/or receiving signals over a second wireless network 58. In some cases, the second communications port 56 may be in communication with a wired or wireless router or gateway for connecting to the second network, but this is not required. In some cases, the router or gateway may be integral to the HVAC controller 18 or may be provided as a separate device. Additionally, the HVAC controller 18 may include a controller (e.g. microcontroller, microcontroller, etc.) 64 and a memory 72. The HVAC controller 18 may also include a local user interface 108, but this is not required. In some cases, HVAC controller 18 may include a timer (not shown). The timer may be integral to the controller 64 or may be provided as a separate component. The memory 72 of the illustrative HVAC controller 18 may be in communication with the controller 64. The memory 72 may be used to store any desired information, such as the aforementioned control algorithm, set points, schedule times, configuration information, diagnostic limits such as, for example, differential pressure limits, delta T limits, and the like. The memory 72 may be any suitable type of storage device including, but not limited to, RAM, ROM, EPROM, flash memory, a hard drive, and/or the like. In some cases, the controller 64 may store information within the memory 72, and may subsequently retrieve the stored information from the memory 72.

In many cases, the HVAC controller 18 may include an input/output block (I/O block) 78 having a number of wire terminals (e.g. 80a-80c) for receiving one or more wires from the HVAC system 4. The I/O block having four wire terminals, as shown in FIG. 3, is just one example and is not intended to be limiting. Also, while the term I/O may imply both input and output, it is intended to include input only, output only, as well as both input and output. The I/O block 78 may be used to communicate one or more signals to and/or from one or more HVAC components 6 of the HVAC system 4. The HVAC controller 18 may have any number of wire terminals for accepting connections from one or more components 6 of the HVAC system 4. How many and which of the wire terminals are actually used at a particular installation will depend on the particular configuration of the HVAC system 4. Different HVAC systems 4 having different HVAC components and/or types of HVAC components 6. That is, the wiring configuration between the wires of the HVAC system and the wire terminals 80a-80d of the input/output block 78 may be dependent on the particular HVAC system configuration of the HVAC system 4. In some cases, one or more wire terminals 80a-80d of the I/O block 78 may communicate with another controller, which is in communication with one or more HVAC components of the HVAC system 4, such as a zone control panel in a zoned HVAC system, equipment interface module (EIM) (e.g. EIM 34 shown in FIG. 1) or any other suitable building control device. In any event, when replacing an old HVAC controller with a new one, the wires that are available in the wall and/or were wired to the old HVAC controller may provide information that can help determine the HVAC configuration of the existing HVAC system 4.

In some cases, the HVAC controller 18 may be powered by line-power connected to one or more of the terminals 80a-80d of the I/O block 78. In some cases, an optional power-stealing block 82 may be connected to one or more wire terminals of the I/O block 78, and may be configured to bleed or steal power from the one or more wire terminals of the I/O block 78. The power that is stolen may be stored in an energy storage device 86 that may be used to at least partially power the HVAC controller 18. In some cases, the energy storage device 86 may be capacitor or a rechargeable battery. Alternatively, or in addition, the HVAC controller 18 may include a back-up source of energy such as, for example, a battery that may be used to supplement power supplied to the HVAC controller 18 when the amount of available power is less than optimal or is insufficient to power certain applications. Certain applications or functions performed by the HVAC controller 18 may require a greater amount of energy than others. If there is an insufficient amount of energy available, then, in some cases, certain applications and/or functions may be prohibited by the controller 64.

The HVAC controller 18 may include one or more sensors such as for example, a temperature sensor, a humidity sensor, an occupancy sensor, a proximity sensor, and/or the like. In some cases, the HVAC controller 18 may include one or more internal temperature sensor 90, as shown FIG. 3, but this is not required. The HVAC controller 18 may communicate with one or more remote temperature sensors, humidity sensors, and/or occupancy sensors located throughout a building or structure. In some cases, the HVAC controller may communicate with a temperature sensor and/or humidity sensor located outside of the building or structure for sensing an outdoor temperature and/or humidity if desired.

In some cases, the HVAC controller 18 may include a sensor 92 that is configured determine if a user is in proximity to the building controller. In some cases, the sensor 92 may be a motion sensor or a proximity sensor such as, for example, a passive infrared (PIR) sensor. In certain cases in which the sensor 92 is a motion sensor or a proximity sensor, the sensor 92 may be located remotely from the HVAC controller 18 and may be in wireless communication with the HVAC controller 18 via one of the communication ports.

In other cases, the sensor 92 may be configured to determine that the user is near or expected to be near the HVAC controller 18 based, at least in part, on the location data provided by a location based service application program executed by a user's remote device 62 that the user utilizes to interact with the HVAC controller 18 from a remote location. The location data generated by the location based services app may be transmitted from the user's remote device 62 directly to the HVAC controller 18 or, in some cases, may be transmitted to the HVAC controller 18 via a server 66 (e.g. Honeywell's TOTAL CONNECT™ server) to which both the HVAC controller 18 and the user's remote device 62 may be connected. In some cases, the sensor 92 may be configured to determine that the user or, more specifically, the user's remote device 62 has crossed a proximity boundary relative to the location of the HVAC controller 18 based on location data provided by the user's remote device that the user utilizes to interact with the HVAC controller 18. The sensor 92 may determine that the user has crossed a proximity boundary by comparing the location data generated by the user's remote device 62 to a predetermined fix location. In some cases, the proximity boundary may be defined by a radius extending outward from the predetermined fix location, and the predetermined fixed location may be the location of the HVAC controller 18.

In yet another example, the sensor 92 may be configured to determine that the user is in proximity to or is expected to be in proximity to the HVAC controller 18 upon detecting that the user's remote device 62 is connected to the building's wireless network which, in some cases, may be the same network to which the HVAC controller 18 is also connected. Such functionality is shown and described in U.S. application Ser. No. 13/559,443 entitled “HVAC CONTROLLER WITH WIRELESS NETWORK BASED OCCUPANCY DETECTION AND CONTROL”, the entirety of which is incorporated by reference herein for all purposes.

In still other cases, the sensor 92 may be configured to determine that a user is in proximity to the HVAC controller 18 upon sensing a user's interaction with the HVAC controller 18 via a local user interface of the HVAC controller 18. For example, the sensor 92 may be configured to sense when the screen of a local user interface 108 is touched and/or when a button provided at the local user interface 108 is pressed by a user. In some cases, the button may be a touch sensitive region provided on the user interface 108 when the user interface 108 incorporates a touch screen display. In other cases, the button may be a hard button or soft key that is provided separate from a display of the user interface 108.

In some cases, upon detecting or determining that a user is in proximity to the HVAC controller, the sensor 92 may deliver a signal to the controller 64 indicating that the user is in proximity to the HVAC controller 18. In other cases, the upon detecting or determining that a user is in proximity to the HVAC controller, the sensor 92 may be configured to transmit a signal to a remote server 66 over a network 58 via the communications block 60.

The local user interface 108, when provided, may be any suitable user interface that permits the HVAC controller 18 to display and/or solicit information, and in some cases, accept one or more user interactions with the HVAC controller 18. For example, the user interface 108 may permit a user to locally enter data such as temperature set points, humidity set points, starting times, ending times, schedule times, configuration information, diagnostic limits, responses to alerts, and the like. In one embodiment, the user interface 108 may be a physical user interface that is accessible locally at the HVAC controller 18, and may include a display and/or a distinct keypad. The display may be any suitable display. In some instances, a display may include or may be a liquid crystal display (LCD), and in some cases a fixed segment display or a dot matrix LCD display. In other cases, the user interface 108 may be a touch screen LCD panel that functions as both display and keypad. The touch screen LCD panel may be adapted to solicit values for a number of operating parameters and/or to receive such values, but this is not required. In still other cases, the user interface 108 may be a dynamic graphical user interface.

In some instances, the user interface 108 need not be physically accessible to a user locally at the HVAC controller 18. Instead, the user interface 108 may be a remote virtual user interface 108 that is accessible via the first network 54 and/or second network 58 using a mobile wireless device such as one of those remote devices 62 previously described herein. In some cases, the remote virtual user interface 108 may be provided by an app exacted by a user's remote device for the purposes of remotely interacting with the HVAC controller 18. Through the virtual user interface 108 provided by the app on the user's remote device 62, the user may make change temperature set points, humidity set points, starting times, ending times, schedule times, configuration changes, diagnostic limits, respond to alerts, update their user profile, view energy usage data, and/or the like. Any changes made by a user to the HVAC controller 18 via a remote virtual user interface 108 provided by an app on the user's remote device 62 may be first transmitted to an external web server 66. The external web server 66 may receive and accept the user inputs entered via the remote virtual user interface 108 provided by the app on the user's remote device 62, and associate the user inputs with a user's account on the external web service. If the user inputs include any changes to the existing control algorithm including any temperature set point changes, humidity set point changes, schedule changes, start and end time changes, window frost protection setting changes, operating mode changes, configuration changes, and/or changes to a user's profile, the external web server 66 may update the control algorithm, as applicable, and transmit at least a portion of the updated control algorithm over the second network 58 to the HVAC controller 18 where it is received via the second port 56 and may be stored in the memory 72 for execution by the controller 64. In some cases, the user may observe the effect of their inputs at the HVAC controller 18.

In some cases, the virtual user interface 108 may include one or more web pages that are sent over the second network 58 (e.g. WAN or the Internet) by an external web server (e.g. web server 66). The one or more web pages forming the virtual user interface 108 may be hosted by an external web service and associated with a user account having one or more user profiles. The external web server 66 may receive and accept any user inputs entered via the virtual user interface and associate the user inputs with a user's account on the external web service. If the user inputs include changes to the existing control algorithm including any temperature set point changes, humidity set point changes, schedule changes, start and end time changes, window frost protection setting changes, operating mode changes, configuration changes, and/or changes to a user's profile, the external web server 66 may update the control algorithm, as applicable, and transmit at least a portion of the updated control algorithm over the second network 58 to the HVAC controller 18 where it is received via the second port 56 and may be stored in the memory 72 for execution by the controller 64. In some cases, the user may observe the effect of their inputs at the HVAC controller 18.

In some cases, a user may utilize one or more of the local user interface 108 provided at the HVAC controller 18 and/or a virtual user interface 108 as described herein. The two types of user interfaces 108 that may be used to interact with the HVAC controller 18 are not mutually exclusive of one another. However, in some cases, a virtual user interface 108 may provide more advanced capabilities to the user.

FIG. 4 is a front view of an illustrative HVAC controller 18 including a local user interface 108 at the HVAC controller 18. The local user interface 108 provided at the HVAC controller 18 may be in addition to, or in alternative to, a virtual user interface that may be provided by an application program executed by a user's remote device 62 or that may be viewed as one or more web pages served up by a web server 66, as discussed herein. As shown in FIG. 4, the local user interface 108 may include a display 94 housed by a housing 96. In some cases, the display 94 may be a touch screen display 94. The touch screen display 94 may include one or more touch sensitive regions (e.g. 98a-98d) corresponding to one or more selectable options that a user may select when interacting with the HVAC controller 18. FIG. 4 shows an exemplary Home screen that may be displayed on the display 94 when in use. While the local user interface 108 that is provided at the HVAC controller 18 is capable of receiving a user's interactions, a more advanced or detailed remote virtual user interface 108 for accessing and/or changing even more information may be provided by an application program executed at a user's remote device 62 or by one or more web pages served up by a web server such as web server 66, as described herein.

Referring back to FIG. 3, the controller 64 may operate in accordance with an algorithm that controls or at least partially controls one or more HVAC components of an HVAC system such as, for example, HVAC system 4 shown in FIG. 1. The controller 64, for example, may operate in accordance with a control algorithm that provides temperature set point changes, humidity set point changes, schedule changes, start and end time changes, window frost protection setting changes, operating mode changes, and/or the like. At least a portion of the control algorithm may be stored locally in the memory 72 of the HVAC controller 18 and, in some cases, may be received from an external web service over the second network 58. The control algorithm (or portion thereof) stored locally in the memory 72 of the HVAC controller 18 may be periodically updated in accordance with a predetermined schedule (e.g. once every 24 hours, 48 hours, 72 hours, weekly, monthly, etc.), updated in response to any changes to the control algorithm made by a user, and/or updated in response to a user's request. The updates to the control algorithm or portion of the control algorithm stored in the memory 72 may be received from an external web service over the second network. In some cases, the control algorithm may include settings such as set points.

In some cases, the controller 64 may operate according to a first operating mode having a first temperature set point, a second operating mode having a second temperature set point, a third operating mode having a third temperature set point, and/or the like. In some cases, the first operating mode may correspond to an occupied mode and the second operating mode may correspond to an unoccupied mode. In some cases, the third operating mode may correspond to a holiday or vacation mode wherein the building or structure in which the HVAC system 4 is located may be unoccupied for an extended period of time. In other cases, the third operating mode may correspond to a sleep mode wherein the building occupants are either asleep or inactive for a period of time. These are just some examples. It will be understood that the controller 64 may be capable of operating in additional modes as necessary or desired. The number of operating modes and the operating parameter settings associated with each of the operating modes may be established locally through a user interface, and/or through an external web service and delivered to the HVAC controller via the second network 58 where they may be stored in the memory 72 for reference by the controller 64.

In some cases, the controller 64 may operate according to one or more predetermined operating parameter settings associated with a user profile for an individual user. The user profile may be stored in the memory 72 of the HVAC controller 18 and/or may be hosted by an external web service and stored on an external web server. The user profile may include one or more user-selected settings for one or more operating modes that may be designated by the user. For example, the controller 64 may operate according to a first operating mode having a first temperature set point associated with a first user profile, a second operating mode having a second temperature set point associated with the first user profile, a third operating mode having a third temperature set point associated with the first user profile, and/or the like. In some cases, the first operating mode may correspond to an occupied mode, the second operating mode may correspond to an unoccupied mode, and the third operating mode may correspond to a vacation or extended away mode wherein the building or structure in which the HVAC system 4 is located may be unoccupied for an extended period of time. In some cases, multiple user profiles may be associated with the HVAC controller 18. In certain cases where two or more user profiles are associated with the HVAC controller 18, the controller 64 may be programmed to include a set of rules for determining which individual user profile takes precedence for controlling the HVAC system when both user profiles are active.

In some cases, the controller 64 may be programmed to execute a guided set-up routine that may guide a user through configuring the HVAC controller 18 to control one or more components 6 of their particular HVAC system 4. In some cases, the user may have limited knowledge about the particular HVAC system configuration. The guided set-up routine may be configured to guide a user through set-up of the HVAC controller 18 without requiring detailed knowledge of the particular HVAC system and/or without requiring the user to consult a technical manual or guide.

When executing the guided set-up routine, the controller 64 may be configured to display two or more screens via a user interface 108 that may guide a user through one or more steps necessary to configure the HVAC controller 18. In some cases, at least one of the screens may display one or more options that identifies an HVAC configuration setting and that further identifies a wiring configuration that is associated with or corresponds to the HVAC configuration setting. The wiring configuration between the wires of the HVAC system 4 and the wire terminals 80a-80d of the output block 78 of the HVAC controller 18 may be dependent on the particular HVAC system configuration of the HVAC system 4. When replacing an old HVAC controller with a new one, the wires that are available in the wall and/or were wired to the old HVAC controller provide information that may help determine the HVAC configuration of the HVAC system 4.

The one or more options that are displayed may be available for selection by a user through the user interface 108 (local user interface and/or remote virtual user interface), and may relate to a variety of HVAC configuration settings including, but not limited to: a type of heating and/or cooling equipment included in the particular HVAC system 4; a number of heating or cooling equipment stages such as, for example, single stage, two stage, and variable firing rate; a backup heat source; a changeover valve; a compressor; and/or the like. The user may select the appropriate HVAC setting based, at least in part, on the identified wiring configuration associated with the various displayed options. In many instances, the controller 64 does not automatically detect a wire connected to a terminal 80a-80d of the input/output block 78. The controller 64 may be programmed to control the one or more components 6 of the HVAC system 4 based on the option selected by the user via the guided set-up routine.

FIGS. 5-18 provide several examples of illustrative screens that may be displayed to the user on the display of a local user interface of an HVAC controller 18 and/or a remote virtual user interface, during set-up of an HVAC controller 18. In some cases, the one or more screens may guide a user through one or more steps necessary to configure the HVAC controller 18 to control a particular HVAC system 4 having a particular HVAC system configuration. In some cases, the particular sequence in which the various screens are displayed to the user and/or which screens are displayed may be dependent upon the user's response to a previous screen. For example, and referring to FIG. 5, if the user does not select the cooling option displayed on screen 150, then the controller 64 may be programmed to exclude any subsequent screens that relate to cooling equipment from the sequence of subsequent screens that may be displayed to the user during set-up of the HVAC controller 18.

In other cases, the sequence is a fixed sequence of predetermined screens that may be displayed to the user in a particular order. The user may utilize a button to advance from a first screen in the sequence to the last screen in the sequence, and each of the screens are displayed regardless of the user's response to a prompt provided on a previous screen. If the displayed screen is not applicable to the user's particular system, the user may advance through the sequence to the next applicable screen through selection of an appropriate button provided for this purpose.

FIG. 5 shows an example of a first screen 150 that may be displayed to a user on the display of a user interface 108 upon initiation of a set-up routine for configuring an HVAC controller 18 to control one or more components of a particular HVAC system 4. As shown in FIG. 5, screen 150 may include a user prompt 154 that prompts the user to identify what type of system the HVAC controller 18 is intended to control. In some cases, screen 150 may include one or more selectable options 158a, 158b that the user may select to indicate whether or not the HVAC controller 18 is intended to control a cooling system, a heating system, or both a heating and cooling system. In some cases, more than one option may be selected. For example, as shown in FIG. 5, both the cooling option 158a and the heating option 158b are selected indicating that the HVAC controller 18 will control and HVAC system having both heating and cooling HVAC components 6. The selectable options 158a, 158b may be displayed simultaneously on a common screen, as shown, or on separate screens, as desired.

In other cases, instead of prompting the user to select an option corresponding to their system type, screen 150 may include a user query that queries the user about a heating and/or cooling system. For example, screen 150 may query the user “Do you have heating?” and may provide “yes” and “no” checkboxes for selection by the user to indicate their system type. After indicating their HVAC system type through selection of the one or more selectable options 158a, 158b, the user may advance to the next applicable screen in the sequence through selection of a button such as, for example, NEXT button 162 provided for this purpose.

FIG. 6 shows an exemplary screen 170 that may be displayed in response to receiving an input from a user indicating that the HVAC controller is intended to control a heating system. As shown in FIG. 6, screen 170 may include a user prompt 174 that prompts a user to identify the type of heating equipment that the HVAC controller 18 is intended to control. In addition, screen 170 may include one or more selectable options 178a-178, each selectable option corresponding to a different type of heating system. For example, screen 170 may include: a first selectable option 178a corresponding to a forced air heating system; a second selectable option 178b corresponding to a heat pump heating system; and a third selectable option 178c corresponding to a hot water or steam heating system. These are just some examples.

In some cases, a HELP button 182 may be provided that, when selected by the user, may cause an additional screen 190, as shown in FIG. 7, to be displayed that may provide additional information about each of the different types of heating systems available for selection by a user through screen 170. In some cases, screen 190 may be provided as a separate screen. In other cases, screen 190 may be provided as a pop-up window or floating window that may be displayed over screen 170. In the illustrative embodiment shown, the user may return to screen 170 through selection of an OK button 192 or other similar button.

FIG. 8 shown an exemplary screen 200 that may be displayed in response to the user having selected the selectable option 178a corresponding to a forced air heating system through screen 170. As shown in FIG. 8, screen 200 may include a user prompt 204 that may prompt a user to identify the type of forced air heating system (gas/oil or electric) that the HVAC controller 18 is intended to control. In addition, screen 200 may include one or more selectable options 208a, 208b, each option 208a, 208b corresponding to a type of forced air heating system. For example, screen 200 may include a first selectable option 208a corresponding to a gas/oil type of forced air heating system, and a second selectable option 208b corresponding to an electric forced air heating system. In some cases, a HELP button 212 may be provided that, when selected by the user, may cause an additional screen 220, as shown in FIG. 9, to be displayed that may provide additional information about each of the different types of forced air heating systems available for selection by a user through screen 200. In some cases, screen 220 may be provided as a separate screen. In other cases, screen 220 may be provided as a pop-up window or floating window that may be displayed over screen 200. The user may return to screen 200 through selection of an OK button 214 or other similar button.

FIG. 10 shows an exemplary screen 230 that may be displayed through which a user may indicate a number of cooling stages that the HVAC controller 18 is intended to control. In some cases, screen 230 may be displayed in response to the user having selected the selectable option 208a or 208b though screen 200 shown in FIG. 8. As shown in FIG. 10, screen 230 may include a user prompt 234 that may prompt the user to identify the number of cooling stages (the user having previously indicated that the HVAC system includes a cooling component through screen 150 shown in FIG. 5). In addition, screen 230 may include one or more selectable options 238a, 238b, each option corresponding to a number of cooling stages. For example, as shown in FIG. 10, screen 230 may include a first selectable option 238a corresponding to a single cooling stage and a second selectable option 238b corresponding to two cooling stages. In some cases, each of the selectable options 238a, 238b corresponding to the number of cooling stages may include a brief description 240a, 240b identifying a wiring configuration associated with the particular number of stages. For example, selectable option 238a corresponding to a single cooling stage includes a short text sting indicating to the user that the Y (Yellow) wire leading from the HVAC system 4 is connected to the terminal labeled “Y” on the I/O block of the HVAC controller 18. Similarly, selectable option 238b corresponding to two cooling stages includes a short text string indicating to the user that both the Y and the Y2 wires are connected to the Y and Y2 terminals on the I/O block of the HVAC controller 18. Alternatively, or in addition to providing text strings, it is contemplated that wiring diagrams and/or pictures of an I/O block with the Y or Y and Y2 wires connected may be provided or linked to the appropriate selectable options 238a, 238b. In some cases, a user (typically a do-it-yourself homeowner) installing a new HVAC controller 18 may have limited knowledge about the configuration of their existing HVAC system 4, including the number of cooling stages in their HVAC system. This additional description facilitates selection of the appropriate number of cooling stages by a user based on which wires from the HVAC system 4 are connected to terminals on the I/O block of the new HVAC controller 18. After indicating the number of cooling stages through selection of the one or more selectable options 238a, 238b, the user may advance to the next applicable screen in the sequence through selection of a button such as, for example, NEXT button 242 provided for this purpose.

FIG. 11 shows an exemplary screen 250 that may be displayed through which a user may indicate a number of heating stages that the HVAC controller 18 is intended to control. In some cases, screen 250 may be displayed in response to the user having selected the selectable option 208a or 208b though screen 200 shown in FIG. 8. As shown in FIG. 10, screen 250 may include a user prompt 254 that may prompt the user to identify the number of heating stages (the user having previously indicated that the HVAC system includes a heating component through screen 150 shown in FIG. 5). In addition, screen 250 may include one or more selectable options 258a, 258b, each option corresponding to a number of heating stages. For example, as shown in FIG. 11, screen 250 may include a first selectable option 258a corresponding to a single heating stage and a second selectable option 258b corresponding to two heating stages. In some cases, each of the selectable options 258a, 258b corresponding to the number of heating stages may include a brief description 260a, 260b identifying a wiring configuration associated with the particular number of stages. For example, selectable option 258a corresponding to a single heating stage includes a short text sting indicating to the user that the W (White) wire leading from the HVAC system 4 is connected to the terminal labeled “W” on the I/O block of the HVAC controller 18. Similarly, selectable option 258b corresponding to two heating stages includes a short text string indicating to the user that both the W and the W2 wires are connected to the W and W2 terminals on the I/O block of the HVAC controller 18. Alternatively, or in addition to providing text strings, it is contemplated that wiring diagrams and/or pictures of an I/O block with the W or W and W2 wires connected may be provided or linked to the appropriate selectable options 258a, 258b. In some cases, a user (typically a do-it-yourself homeowner) installing a new HVAC controller 18 may have limited knowledge about the configuration of their existing HVAC system 4, including the number of heating stages in their HVAC system. This additional description facilitates selection of the appropriate number of heating stages by a user based on which wires from the HVAC system 4 are connected to terminals on the I/O block of the new HVAC controller 18. After indicating the number of heating stages through selection of the one or more selectable options 258a, 258b, the user may select a DONE button 262 to that, when selected by the user, may cause the controller 64 to complete the set-up process.

FIG. 12 shows an example screen 270 that may be displayed in setting up fan control of an HVAC system. In some cases, screen 270 may be displayed in addition to screens 230 and/or 250 related to the number of cooling and/or heating stages. As shown in FIG. 12, screen 270 includes a user prompt 274 that prompts the user to identify which of the heating system or thermostat controls the fan. In addition, screen 270 may include one or more selectable options 278a, 278b, each option 278a, 278b corresponding to a different mechanism through which the fan may be controlled. For example, as shown in FIG. 12, screen 270 may include a first selectable option 278a for indicating that the heating system will control the fan (i.e. through a furnace control board), and a second selectable option 278b for indicating that the HVAC controller 18 will control the fan. In addition, at least one of the selectable options 278a, 278b may include an indicator 280 indicating which mechanism is the most common for controlling the fan. The indicator 280 may be a short text string, as shown in FIG. 12, or may be an asterisk, a dot, or other similar notation that may be provided to indicate to the user that the option (in this case selectable option 278b) is the most common option. In some cases, a short text sting may be provided that indicates to the user that a fan wire (e.g. G wire) leading from the HVAC system 4 is connected to the fan terminal on the I/O block of the HVAC controller 18. In some cases, the user may select a DONE button 282 to that, when selected by the user, may cause the controller 64 to complete the set-up process.

FIG. 13 shows an example screen 300 related to a changeover valve that may be displayed in connection with selection by a user of selectable option 178b corresponding to heat pump system through screen 170 shown in FIG. 6. As shown in FIG. 13, screen 300 may include a user prompt 304 that may prompt the user to identify the type of changeover valve associated with the heat pump system. In addition, screen 300 may include one or more selectable options 308a, 308b, each option corresponding to a type of changeover valve. For example, screen 300 may include a first selectable option 308a corresponding to a cooling changeover valve and a second selectable option 308b corresponding to a heating cooling changeover valve. In some cases, each of the selectable options 308a, 308b corresponding to the different types of changeover valves (e.g. heating or cooling) may include a brief description 310a, 310b identifying a wiring configuration associated with the particular changeover valve. For example, selectable option 308a corresponding to cooling changeover valve may include a short text sting 310a indicating to the user that the O wire from the HVAC system 4 is connected to the O/B terminal of the HVAC controller 18. Similarly, selectable option 308b corresponding to a heating changeover valve may include a short text string 310b indicating to the user that the B wire from the HVAC system 4 is connected to the O/B terminal of the HVAC controller 18. This additional description is intended to facilitate selection of the appropriate changeover valve by a user based on which wire(s) from the HVAC system are connected to terminal(s) on the HVAC controller 18.

In some cases, at least one of the selectable options 308a, 308b may include an indicator 312 indicating which configuration setting is the most common. The indicator 312 may be a short text string, as shown in FIG. 13, or may be an asterisk, a dot, or other similar notation that may be provided to indicate to the user that the particular option (in this case selectable option 308a) is the most common option. In some cases, a HELP button 314 may be provided that, when selected by the user, may cause an additional screen 320, as shown in FIG. 14, to be displayed that may provide additional information about the different wiring configurations that may be associated with the different changeover valves. In some cases, screen 320 may be provided as a separate screen. In other cases, screen 320 may be provided as a pop-up window or floating window that may be displayed over screen 300. The user may return to screen 300 through selection of an OK button 322 or other similar button.

FIG. 15 shows another example screen 330 that may be displayed in connection with selection by a user of selectable option 178b corresponding to heat pump system through screen 170 shown in FIG. 6. As shown in FIG. 15, screen 330 may include a user prompt 334 that may prompt the user to identify the number of heat pump compressor stages. In addition, screen 330 may include one or more selectable options 338a, 338b, each option corresponding to a number of heat pump compressor stages. For example, as shown in FIG. 16, screen 330 may include a first selectable option 338a corresponding to a single heat pump compressor stage and a second selectable option 338b corresponding to two heat pump compressor stages. In some cases, each of the selectable options 338a, 338 corresponding to the number of heat pump compressor stages may include a brief description 340a, 340b identifying a wiring configuration associated with the particular number of compressor stages. For example, selectable option 338a corresponding to a single compressor stage includes a short text sting indicating to the user that the Y wire from the HVAC system 4 is connected to a terminal on the HVAC controller 18. Similarly, selectable option 338b corresponding to a two compressor stages includes a short text string indicating to the user that both the Y and the Y2 wires from the HVAC system 4 are connected to wire terminals provided on the HVAC controller 18. This additional description is intended to facilitate selection of the appropriate number of heat pump compressor stages by a user based on which wires from the HVAC system 4 are connected to terminals on the HVAC controller 18. In some cases, a HELP button 344 may be provided that, when selected by the user, may cause an additional screen 350, as shown in FIG. 16, to be displayed that may provide additional information about the different wiring configurations that may be associated with the different heat pump compressor stages. In some cases, screen 350 may be provided as a separate screen. In other cases, screen 350 may be provided as a pop-up window or floating window that may be displayed over screen 330. The user may return to screen 330 through selection of an OK button 352 or other similar button. After indicating the number of heat pump compressor stages through selection of the one or more selectable options 338a, 338b, the user may advance to the next applicable screen in the sequence through selection of a button such as, for example, NEXT button 342, provided for this purpose.

FIG. 17 shows another example screen 360 that may be displayed in connection with selection by a user of selectable option 178b corresponding to heat pump system through screen 170 shown in FIG. 6. As shown in FIG. 17, screen 360 may include a user prompt 364 that may prompt the user to indicate whether or not the HVAC system includes backup heat. In addition, as shown in FIG. 17, screen 360 may include a first selectable option 368a for indicating that the HVAC system does not have backup heat and a second selectable option 368b for indicating that the HVAC system includes backup heat. In some cases, at least one of the selectable options 368a 368b for indicating whether or not the HVAC system includes backup heat may include a brief description 370 identifying a wiring configuration associated with backup heat. For example, selectable option 368b indicating that the HVAC system includes backup heat includes a short text sting indicating to the user that the W2/Aux-E wire is connected to a terminal on the HVAC controller 18. This additional description is intended to help the user identify whether or not the HVAC system includes backup heat. In some cases, a HELP button 374 may be provided that, when selected by the user, may cause an additional screen 350, as shown in FIG. 18, to be displayed that may provide additional description of the wiring configuration associate with backup heat that may help the user identify whether or not the HVAC system includes backup heat. In some cases, screen 380 may be provided as a separate screen. In other cases, screen 380 may be provided as a pop-up window or floating window that may be displayed over screen 350. The user may return to screen 350 through selection of an OK button 382 or other similar button. After indicating whether or not the HVAV system includes backup heat through selection of the one or more selectable options 368a, 368b, the user may select a DONE button 372 to that, when selected by the user, may cause the controller 64 to complete the set-up process.

While FIGS. 5-18 are described as they relate to an HVAC controller 18 including a user interface having a display, as shown in FIG. 4, it will be generally understood that the same or a similar set of screens may be displayed on the display of a user interface of a user's remote device by an application program code that may be used for configuring an HVAC controller to control one or more components of an HVAC system. The app may provide a remote user interface 108 for interacting with the HVAC controller 18. Such an app may be available for download from a web service such as for, example, Honeywell's TOTAL CONNECT™ web service of Apple, Inc.'s ITUNES or Google's Google Play. In addition, the same or a similar set of screens may be displayed via one or more web pages served up by a web server such as, for example, web server 66 shown in FIG. 2, and may be accessed and viewed over a network via the user interface of any number of web-enabled devices including a user's smart phone, tablet, laptop or personal computer, an e-reader, and/or a web-enabled HVAC controller 18. The one or more web pages served up by the server may be available through a web-service such as, for example, Honeywell's TOTAL CONNECT™ web service, and may also provide a remote user interface 108 for interacting with the HVAC controller 18.

Having thus described several illustrative embodiments of the present disclosure, those of skill in the art will readily appreciate that yet other embodiments may be made and used within the scope of the claims hereto attached. Numerous advantages of the disclosure covered by this document have been set forth in the foregoing description. It will be understood, however, that this disclosure is, in many respect, only illustrative. Changes may be made in details, particularly in matters of shape, size, and arrangement of parts without exceeding the scope of the disclosure. The disclosure's scope is, of course, defined in the language in which the appended claims are expressed.

SETUP ROUTINE TO FACILITATE USER SETUP OF AN HVAC CONTROLLER

Information

Publication Number

Date Filed

Date Published

Inventors

Original Assignees

CPC

US Classifications

International Classifications

Abstract

Description

Claims