US20150148965A1 - Method to control a communication rate between a thermostat and a cloud based server - Google Patents

Abstract

A communication rate between a cloud-based server and an HVAC controller located within a building may be controlled based on the amount of power available at the HVAC controller. The cloud-based server may notify a user if the amount of power available at the HVAC controller is determined to be low.

Description

TECHNICAL FIELD
• The present disclosure relates generally to HVAC systems, and more particularly to HVAC controllers that accommodate and/or facilitate control of an HVAC system from a remote location.
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 control one or more environmental conditions within the building. In some cases, it may be desirable for a user to be able to affect the operation of an HVAC system from a remote location. In such cases, communication between a user's remote device and the HVAC controller located within a building may be routed through a web server or the like to which both the user's remote device and the HVAC controller are connected. What would be desirable are methods and systems for improving the reliability and/or user experience of such a system, particularly when the HVAC controller is powered by a local power source such as a battery.
SUMMARY
• The present disclosure relates generally to building controllers, and more particularly to building controllers that accommodate and/or facilitate control of a building control system from a remote location. In an illustrative embodiment, a building controller can include: an input/output block configured to send one or more control signals to control one or more building components; a communications port configured to send and/or receive messages via a communications network; an energy storage device for powering at least part of the building controller; and a controller operatively coupled to the input/output block, the communications port, and the energy storage device. The controller can be configured to determine an available amount of power stored in the energy storage device and to communicate, via the communications port, a message that is indicative of a delay until a subsequent communication time, wherein the delay is dependent upon the determined available amount of power stored in the energy storage device. In some cases, the delay may be increased as the amount of power stored in the energy storage device drops. This may help extend the operational life of the building controller in controlling the one or more building components of the building by reducing the power that is used to communicate over the communications network.
• In some cases, a server or the like may be in communication with the building controller, and may receive the message that is indicative of the delay until the subsequent communication time. When so provided, the server may not have to assume from a lack of communication from the building controller that some other failure has occurred. When the user attempts to interact with the building controller, the server may send a message to a user's remote computing device (computer, tablet, smart phone, etc.) indicating that the building controller is in a lower power state, and as such may not receive requests entered via the user's remote computing device until the next available communication time.
• 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 ofFIG. 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;
• FIG. 5 is a schematic block diagram of an illustrative web server; and
• FIGS. 6-9 provide examples of illustrative screens that may be displayed to a user via a user interface.
• 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.
• While an HVAC system is used as an example below, it is contemplated that the present disclosure is applicable to any building control system such as a lighting system, a security system, a fire system, a home automation system, and/or any other building control system, as desired.
• FIG. 1 is a schematic view of abuilding2 having an illustrative heating, ventilation, and air conditioning (HVAC) system4. WhileFIG. 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 system4 ofFIG. 1 includes one ormore HVAC components6, a system of ductwork and air vents including asupply air duct10 and areturn air duct14, and one ormore HVAC controllers18. The one ormore HVAC components6 may include, but are not limited to, a furnace, a heat pump, an electric heat pump, a geothermal heat pump, an electric heating unit, a backup 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 orwireless communication link20. 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 some cases, the HVAC controller(s)18 may be configured to communicate with one or more remote devices including a remote server and/or a user's mobile wireless device over a network.
• In the illustrative HVAC system4 shown inFIG. 1, the HVAC component(s)6 may provide heated air (and/or cooled air) via the ductwork throughout thebuilding2. As illustrated, the HVAC component(s)6 may be in fluid communication with every room and/or zone in thebuilding2 via theductwork10 and14, but this is not required. In operation, when a heat call signal is provided by the HVAC controller(s)18, an HVAC component6 (e.g. forced warm air furnace) may be activated to supply heated air to one or more rooms and/or zones within thebuilding2 viasupply air ducts10. The heated air may be forced throughsupply air duct10 by a blower orfan22. In this example, the cooler air from each zone may be returned to the HVAC component6 (e.g. forced warm air furnace) for heating viareturn air ducts14. Similarly, when a cool call signal is provided by the HVAC controller(s)18, an HVAC component6 (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 viasupply air ducts10. The cooled air may be forced throughsupply air duct10 by the blower orfan22. In this example, the warmer air from each zone may be returned to the HVAC component6 (e.g. air conditioning unit) for cooling viareturn air ducts14.
• FIG. 2 is a schematic view of anHVAC control system50 that facilitates remote access and/or control of the HVAC system4 shown inFIG. 1. The illustrativeHVAC control system50 includes an HVAC controller, as for example, HVAC controller18 (seeFIG. 1) that is configured to communicate with and control one ormore HVAC components6 of the HVAC system4. As discussed above, theHVAC controller18 may communicate with the one ormore HVAC components6 of the HVAC system4 via a wired or wireless link. Additionally, theHVAC controller18 may be adapted to communicate over one or more wired or wireless networks that may accommodate remote access and/or control of theHVAC controller18 via another device such as a smart phone, tablet, e-reader, laptop computer, personal computer, or the like. As shown inFIG. 2, theHVAC controller18 may include at least onecommunications port52 for communicating over afirst network54 and/or over asecond network58. In some cases, thefirst network54 may be a wireless local area network (LAN), and the second network58 (when provided) may be a wide area network or global network (WAN) including, for example, the Internet. In some cases, the wirelesslocal area network54 may include a router that provide a wireless access point and/or a network host device that is separate from theHVAC controller18. In other cases, the wirelesslocal area network54 may provide a wireless access point and/or a network host device that is part of theHVAC controller18. In some cases, the wirelesslocal area network54 may include a local domain name server (DNS), but this is not required for all embodiments. In some cases, the wirelesslocal area network54 may be an ad-hoc wireless network, but this is not required.
• In some cases, the HVACcontroller18 may be programmed to communicate over thesecond network58 with an external web service hosted by one or moreexternal web servers66. A non-limiting example of such an external web service is Honeywell's TOTAL CONNECT™ web service. TheHVAC controller18 may be configured to upload selected data via thesecond network58 to the external web service where it may be collected and stored on theexternal web server66. In some cases, the data may be indicative of the performance of the HVAC system4. Additionally, theHVAC controller18 may be configured to receive and/or download selected data, settings and/or services including software updates from the external web service over thesecond network58. 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, theHVAC controller18 may be configured to receive and/or download an HVAC operating schedule and operating parameter settings such as, for example, temperature setpoints, humidity set points, start times, end times, schedules, window frost protection settings, and/or the like from theweb server66 over thesecond network58. In some instances, theHVAC controller18 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, theHVAC controller18 may be configured to receive and/or download firmware and/or hardware updates such as, for example, device drivers from theweb server66 over thesecond network58. Additionally, theHVAC controller18 may be configured to receive local weather data, weather alerts and/or warnings, major stock index ticker data, and/or news headlines over thesecond network58. These are just some examples.
• Depending upon the application and/or where the HVAC user is located, remote access and/or control of theHVAC controller18 may be provided over thefirst network54 and/or thesecond network58. A variety of remote,wireless devices62 may be used to access and/or control theHVAC controller18 from a remote location (e.g. remote from the HVAC Controller18) over thefirst network54 and/orsecond network58 including, but not limited to, mobile phones including smart phones, tablet computers, laptop or personal computers, e-readers, and/or the like. In many cases, the remote,wireless devices62 are configured to communicate wirelessly over thefirst network54 and/orsecond network58 with theHVAC controller18 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 theremote device62 may be used to remotely access and/or control theHVAC controller18. The application program code (app) may be provided for downloading from the external web service hosted by the external web server66 (e.g. Honeywell's TOTAL CONNECT™ web service) to which theHVAC controller18 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 theHVAC controller18 at the user'sremote device62. 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 setpoints, 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'sremote device62 to theweb server66 and then, from theweb server66 to theHVAC controller18. In some cases, communications may flow in the opposite direction such as, for example, when a user interacts directly with theHVAC controller18 to change an operating parameter setting such as, for example, a schedule change or a set point change. The change made at theHVAC controller18 may then be routed to theweb server66 and then from theweb server66 to theremote device62 where it may reflected by the application program executed by theremote device62. In other cases, a user may be able to interact with theHVAC controller18 via a user interface provided by one or more web pages served up by theweb server66. The user may interact with the one or more web pages using a variety of internet capable devices to effect a change at theHVAC controller18 as well as view usage data and energy consumption date related to the usage of the HVAC system4. In still yet another case, communication may occur between the user'sremote device62 and theHVAC controller18 without being relayed through a server. These are just some examples.
• In some cases, theHVAC controller18 may be programmed to periodically poll theexternal web server66 via thesecond network58. The rate at which theHVAC controller18 polls theexternal web server66 may control the overall communication rate between theHVAC controller18, theweb server66, and a user'sremote device62. For example, in many cases, theweb server66 may be programmed to respond to theHVAC controller18 only when it is polled by theHVAC controller18 over a network such assecond network58. Until that time, theweb server66 may be programmed to buffer any data to be sent to theHVAC controller18 such as, for example, a set point change or a schedule change. Upon receiving a poll from theHVAC controller18 via thesecond network58, theweb server66 may be programmed to deliver the data in a rapid communication burst to the HVAC controller. In general, the more rapid the polling rate, the more rapidly a response may be received from theweb server66. Because theHVAC controller18 may be programmed to first poll theweb server66 before it may receive any data from theserver66 such as, for example, a set point change which the user may have effected through an app provided on theirremote device62, the polling rate may be the underlying factor driving the communication rate between a user'sremote device62, theweb server66, and theHVAC controller18. The amount of time that passes from when the user interacts with theHVAC controller18 via their remote device62 (e.g. the user changes a temperature set point), the interaction is delivered to theHVAC controller18 from the user'sremote device62 via theweb server66, and when the user actually experiences the change at theHVAC controller18 may be referred to as message latency. User satisfaction and usability may be associated with the message latency between theHVAC controller18, theweb server66 and the user'sremote device62. In some cases, message latency may also be experienced when the user is interacting with theHVAC controller18 at the user interface provided at theHVAC controller18. Thus, a faster polling rate may be expected to produce lower message latencies which may be desirable when the user is located in close proximity to theHVAC controller18 because the user may observe the effect of their interaction with a minimal amount of waiting time. If the message latency is too slow, the user may be concerned that communication between theweb server66, theHVAC controller18 and/or the user's remote device has been disrupted. Because a faster polling rate may utilize a greater amount of energy, in some cases, the polling rate may be dependent upon the amount of available energy at theHVAC controller18.
• In other cases, theweb server66 may be configured to periodically poll theHVAC controller18. In some cases,HVAC controller18 may be programmed to response to theweb server66 only when it is polled by theweb server66 over a network such assecond network58. Until that time, theHVAC controller18 may be programmed to buffer any data to be sent to theweb server66 such as, for example, a set point change or a schedule change made at theHVAC controller18, a current temperature reading, or an indication of a user's proximity to theHVAC controller18. Upon receiving a poll from theweb server66 via thesecond network58, theHVAC controller18 may be programmed to deliver the data in a rapid communication burst to theweb server66. As discussed herein, the rate at which theHVAC controller18 is polled by theexternal web server66 may affect the message latency between theHVAC controller18, theweb server66, and a user'sremote device62. A faster polling rate may be expected to produce lower message latencies. In addition, if the message latency is too slow, the user may be concerned that communication between theweb server66, theHVAC controller18 and/or the user's remote device has been disrupted.
• FIG. 3 is a schematic block diagram of theillustrative HVAC controller18 shown inFIG. 2. As discussed above with reference toFIG. 2, theHVAC controller18 may be accessed and/or controlled from a remote location over thefirst network54 and/or thesecond network58 using aremote wireless device62 such as, for example, a smart phone, a tablet computer, a laptop or personal computer, an e-reader, and/or the like. In some instances, theHVAC controller18 may be a thermostat, but this is not required. As shown inFIG. 3, theHVAC controller18 may include acommunications block60 having afirst communications port52 for communicating over a first network (e.g. wireless LAN) and asecond communications port56 for communicating over a second network (e.g. WAN or the Internet). Thefirst communications port52 can be a wireless communications port including a wireless transceiver for wirelessly sending and/or receiving signals over afirst wireless network54. Similarly, thesecond communications port56 may be a wireless communications port including a wireless transceiver for sending and/or receiving signals over asecond wireless network58. In some cases, thesecond communications port56 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 theHVAC controller18 or may be provided as a separate device.
• Theillustrative HVAC controller18 may include a processor (e.g. microprocessor, microcontroller, etc.)64 and amemory72. TheHVAC controller18 may also include auser interface108, but this is not required. In some cases,HVAC controller18 may include a timer (not shown). The timer may be integral to theprocessor64 or may be provided as a separate component. Thememory72 of theillustrative HVAC controller18 may be in communication with theprocessor64. Thememory72 may be used to store any desired information, such as the aforementioned control algorithm, set points, schedule times, diagnostic limits such as, for example, differential pressure limits, delta T limits, and the like. Thememory72 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, theprocessor64 may store information within thememory72, and may subsequently retrieve the stored information from thememory72.
• TheHVAC controller18 may also optionally include an input/output block (I/O block)78 for receiving one or more signals from the HVAC system4 and/or for providing one or more control signals to the HVAC system4. For example, the I/O block78 may communicate with one ormore HVAC components6 of the HVAC system4. Alternatively, or in addition, the I/O block78 may communicate with another controller, which is in communication with one or more HVAC components of the HVAC system4, such as a zone control panel in a zoned HVAC system, equipment interface module (EIM) (e.g. EIM34 shown inFIG. 1) or any other suitable building control device.
• In some cases, an optional power-stealingblock82 may be connected to one or more wires of the I/O block78, and may be configured to steal power from the one or more wires of the I/O block78. The power stolen from the one or more wires of the I/O block may be stored in anenergy storage device86, which may be used to at least partially power theHVAC controller18. In some cases, theenergy storage device86 may be capacitor or a rechargeable battery. In some instances, the energy storage device may include a non-rechargeable battery. In some cases, theHVAC controller18 may include a back-up source of energy such as, for example, a battery that may be used to supplement power supplied to theHVAC controller18 when the amount of available power stored by theenergy storage device86 is less than optimal or is insufficient to power certain applications. Certain applications or functions performed by the HVAC controller may require a greater amount of energy than others. If there is an insufficient amount of energy stored in theenergy storage device86, then, in some cases, certain applications and/or functions may be prohibited by theprocessor64.
• TheHVAC controller18 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, theHVAC controller18 may include aninternal temperature sensor90, as shownFIG. 3, but this is not required. TheHVAC controller18 may communicate with one or more remote temperature sensors, humidity sensors, and/or occupancy sensors located throughout the building or structure. Additionally, 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, theHVAC controller18 may include asensor92 that is configured determine if a user is in proximity to the building controller. In some cases, thesensor92 may be a motion sensor or a proximity sensor such as, for example, a passive infrared (PIR) sensor. In certain cases in which thesensor92 is a motion sensor or a proximity sensor, thesensor92 may be located remotely from theHVAC controller18 and may be in wireless communication with theHVAC controller18 via one of the communication ports.
• In other cases, thesensor92 may be configured to determine that the user is near or expected to be near theHVAC controller18 based, at least in part, on the location data provided by a location based service application program executed by a user'sremote device62 that the user utilizes to interact with theHVAC controller18 from a remote location. The location data generated by the location based services app may be transmitted from the user'sremote device62 directly to theHVAC controller18 or, in some cases, may be transmitted to theHVAC controller18 via a server66 (e.g. Honeywell's TOTAL CONNECT™ server) to which both theHVAC controller18 and the user'sremote device62 may be connected. In some cases, thesensor92 may be configured to determine that the user or, more specifically, the user'sremote device62 has crossed a proximity boundary relative to the location of theHVAC controller18 based on location data provided by the user's remote device that the user utilizes to interact with theHVAC controller18. Thesensor92 may determine that the user has crossed a proximity boundary by comparing the location data generated by the user'sremote device62 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 theHVAC controller18.
• In yet another example, thesensor92 may be configured to determine that the user is in proximity to or is expected to be in proximity to theHVAC controller18 upon detecting that the user'sremote device62 is connected to the building's wireless network which, in some cases, may be the same network to which theHVAC controller18 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, thesensor92 may be configured to determine that a user is in proximity to theHVAC controller18 upon sensing a user's interaction with theHVAC controller18 via the user interface provided at theHVAC controller18. For example, thesensor92 may be configured to sense when the screen of theuser interface108 is touched and/or when a button provided at theuser interface108 is pressed by a user. In some cases, the button may be a touch sensitive region provided on theuser interface108 when theuser interface108 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 theuser interface108.
• In some cases, upon detecting or determining that a user is in proximity to the HVAC controller, thesensor92 may deliver a signal to theprocessor64 indicating that the user is in proximity to theHVAC controller18. In other cases, upon detecting or determining that a user is in proximity to the HVAC controller, thesensor92 may be configured to transmit a signal to aremote server66 over asecond network58 via thecommunications block60.
• Theuser interface108, when provided, may be any suitable user interface that permits theHVAC controller18 to display and/or solicit information, as well as accept one or more user interactions with theHVAC controller18. For example, theuser interface108 may permit a user to locally enter data such as temperature set points, humidity set points, starting times, ending times, schedule times, diagnostic limits, responses to alerts, and the like. In one embodiment, theuser interface108 may be a physical user interface that is accessible at theHVAC controller18, 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, theuser interface108 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, theuser interface108 may be a dynamic graphical user interface.
• In some instances, theuser interface108 need not be physically accessible to a user at theHVAC controller18. Instead, theuser interface108 may be avirtual user interface108 that is accessible via thefirst network54 and/orsecond network58 using a mobile wireless device such as one of thoseremote devices62 previously described herein. In some cases, thevirtual user interface108 may be provided by an app exacted by a user's remote device for the purposes of remotely interacting with theHVAC controller18. Through thevirtual user interface108 provided by the app on the user'sremote device62, the user may make changes to temperature set points, humidity set points, starting times, ending times, schedule times, diagnostic limits, respond to alerts, update their user profile, view energy usage data, and/or the like. In some instances, changes made by a user to theHVAC controller18 via auser interface108 provided by an app on the user'sremote device62 may be first transmitted to anexternal web server66. Theexternal web server66 may receive and accept any user inputs entered via thevirtual user interface108 provided by the app on the user'sremote device62, 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, and/or changes to a user's profile, theexternal web server66 may update the control algorithm, as applicable, and transmit at least a portion of the updated control algorithm over thesecond network58 to theHVAC controller18 where it is received via thesecond communications port56 and may be stored in thememory72 for execution by theprocessor64. In some cases, the user may observe the effect of their inputs atuser interface108 of theHVAC controller18.
• As discussed herein, the communication rate between theprocessor64 and theweb server66 may affect the message latency from when the user interacts with the user interface of theirremote device62 to effect a change at theHVAC controller18 and when a message corresponding to the user's interaction with theremote device62 is communicated to theHVAC controller18. TheHVAC controller18 may be configured such that the user experiences lower message latencies when theHVAC controller18 has a full amount of available power stored in theenergy storage device86. The message latency may increase as less power is available to theHVAC controller18 from theenergy storage device86.
• In some instances, a virtual user interface of theHVAC controller18 may include one or more web pages that are broadcasted over the second network58 (e.g. WAN or the Internet) by an external web server (e.g. web server66). The one or more web pages forming thevirtual user interface108 may be hosted by an external web service and may be associated with a user account having one or more user profiles. Theexternal web server66 may receive and accept user inputs entered via a virtual user interface (e.g. the user interface of the remote device62), and associate the user input with a user's account on the external web service. If the user inputs include changes to the existing control algorithm including 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 changes to a user's profile, theexternal web server66 may update the control algorithm, as applicable, and transmit at least a portion of the updated control algorithm over thesecond network58 to theHVAC controller18 where it is received via thesecond communications port56 and may be stored in thememory72 for execution by theprocessor64. In some cases, the user may observe the effect of their inputs entered via the virtual user interface (e.g. the user interface of the remote device62). Rather than using web pages, it is contemplated that the virtual user interface may be provided by an application program (app) that is running on aremote device62. The application program may exchange information with theweb server66.
• In some cases, a user may utilize thelocal user interface108 of the HVAC controller18 (if provided) and/or avirtual user interface108 of a remote device as described herein for interacting with theHVAC controller18. In some cases, thevirtual user interface108 may provide more advanced capabilities to the user than the local user interface of theHVAC controller18.
• FIG. 4 is a front view of anillustrative HVAC controller18 including alocal user interface108 located at theHVAC controller18. Thelocal user interface108 provided at theHVAC controller18 may be in addition to, or in the alternative to, a virtual user interface that may be provided by an application program executed by a user'sremote device62 and/or that may be viewed as one or more web pages served up by aweb server66, as discussed herein. As shown inFIG. 4, thelocal user interface108 may include adisplay94 disposed within ahousing96. In some cases, thedisplay94 may be a touch screen display. Theuser interface108 may include one or more touch sensitive regions98a-98cprovided on thedisplay94, each touch sensitive region defining a button through which the user may interact with theHVAC controller18. Alternatively, or in addition, thelocal user interface108 may include one ormore buttons102aand102bthat may be provided separate from thedisplay94 through which the user may interact with theHVAC controller18. In some cases, thebuttons102a,102bmay be touch sensitive capacitive buttons. In other cases, thebuttons102a,102bmay be hard, physical buttons or soft keys. It will be generally understood that the size and shape of the display as well as the number and location of the various buttons can vary.
• Thehousing96 may be fabricated from any suitable material. As shown inFIG. 4, thehousing96 may have a cylindrical shape with a generally circular foot print, but this is not required. In some cases, thehousing96 may be a two-part housing and may include arotating ring106 which may form part of theuser interface108, and which may provide another mechanism for accepting an input from a user. For example, the user may rotate thering106 to increase or decrease an operating parameter set point or to change information viewed on thedisplay94 by advancing from a first screen to a second screen displayed on thedisplay94. In some cases, while thelocal user interface108 that is provided at theHVAC controller18 is capable of receiving user interactions, a more advanced ordetailed user interface108 for more fully interacting with theHVAC controller18 may be provided by an application program executed at a user'sremote device62 and/or by one or more web pages served up by a web server such asweb server66, as described herein.
• Referring back toFIG. 3, theprocessor64 may be programmed to 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 system4 shown inFIG. 1. Theprocessor64, 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 thememory72 of theHVAC controller18 and, in some cases, may be received from an external web service over the second network. The control algorithm (or portion thereof) stored locally in thememory72 of theHVAC controller18 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 thememory72 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, theprocessor64 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 system4 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 theprocessor64 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 local user interface, and/or through an external web service and delivered to the HVAC controller via thesecond network58 where they may be stored in thememory72 for reference by theprocessor64.
• In some cases, theprocessor64 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 thememory72 of theHVAC controller18 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, theprocessor64 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 system4 is located may be unoccupied for an extended period of time. In some cases, multiple user profiles may be associated with theHVAC controller18. In certain cases, where two or more user profiles are associated with theHVAC controller18, theprocessor64 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.
• Additionally, in some cases, when theHVAC controller18 is in communication with aweb server66 such as shown inFIG. 2, theprocessor64 may be programmed to periodically poll theweb server66, as discussed herein, according to an initial polling rate. The initial polling rate may be set by the manufacturer, installer or the like, and may be selected such that it utilizes a minimal amount of energy stored in theenergy storage device86 while at the same time maintains a satisfactory level of communication between theHVAC controller18 and theweb server66 to achieve a desirable user experience.
• In some cases, theprocessor64 may be programmed to control the polling rate between theHVAC controller18 and theweb server66 according to an available amount of power stored in theenergy storage device86. Theprocessor64 may be programmed to determine the amount of available energy stored by the energy storage device85 and increase or decrease the communication rate between theHVAC controller18 and the web server by increasing or decreasing the amount of time that occurs between when a first message is transmitted by theprocessor64 to theserver66 via thecommunications block60 and when a second message is transmitted by theprocessor64 to theserver66 via thecommunications block60. The amount of time that passes between when the first message is transmitted from theHVAC controller18 to theserver66 and when the second message is transmitted may be referred to as the delay time. The delay time may range from less than half a second to greater than two hours depending upon the application and/or the amount of available power stored in theenergy storage device86 as determined by theprocessor64. When the device is fully powered, the initial delay between two or more communications transmitted by theprocessor64 to theweb server66 via the communications port may be relatively short. For example, the initial delay time between messages utilized by theprocessor64 may be approximately five seconds. This is just an example. It will be generally understood that the initial delay time between messages transmitted by theprocessor64 may be less than or greater than 5 seconds. In some cases, the initial delay time may be determined and programmed by the manufacturer. Theprocessor64 may change the delay time from its initial, default value dependent upon the amount of available power stored in theenergy storage device86. Changing the communication rate dependent upon the amount of available power stored in theenergy storage device86 may help conserve the available amount of power so that theHVAC controller18 can continue to control the HVAC system for a longer time period. In some cases, theprocessor64 may be configured to enter a sleep mode between communications transmitted to theweb server66 to conserve the available power stored in theenergy storage device86. When theprocessor64 is in sleep mode, thecommunications block60 may be placed in a low power state such that it consumes a minimal amount of energy, which may facilitate conservation of the available power stored in theenergy storage device86.
• In some cases, theprocessor64 may be configured to determine if the available amount of power is below a predetermined threshold. The predetermined threshold may be a default threshold value determined by the manufacturer, installer, or user. In one example, a user may select an energy conservation mode through auser interface108 of theHVAC controller18. Selection of an energy conservation mode may cause theprocessor64 to utilize a different predetermined threshold value other than the default value set by the manufacturer. In some cases, the predetermined threshold value associated with an energy conservation mode may be greater than the default value. This is just one example. Regardless, if theprocessor64 determines that the amount of power is below a predetermined threshold value, theprocessor64 may be programmed to increase the delay between the transmissions of two or more communications to theweb server66. The delay may be increased relative to the delay that was utilized when the amount of available power was above the predetermined threshold or relative to a default delay. The amount of increase in the delay may be dependent on the amount of available power remaining in theenergy storage device86. In general, the less available power the greater the increase in the delay.
• In some cases, upon determining a new delay time, which is dependent upon the amount of available power stored in the energy source, theprocessor64 may be configured to transmit a message to theweb server66 that may include an indication of the delay time until a subsequent communication. For example, for a first amount of available power stored in theenergy storage device86, theprocessor64 may communicate a first message to theweb server66 via thecommunications block60 that is indicative of a first delay time until a subsequent communication time, and for a second amount of available power stored in theenergy storage device86, theprocessor64 may communicate a second message to theweb server66 via thecommunications block60 that is indicative of a second delay time until a subsequent communication time. In some cases, the first available amount of power may be greater than the second available amount of power, and the first delay time may be less than the second delay time. In one example, the first delay time may be less than about ten seconds and the second delay time may be greater than about thirty seconds. In other instances, the first delay time may be less than about ten seconds and the second delay time may be greater than about ten minutes. In still other examples: the first delay time may be less than about ten seconds and the second delay time may be less than twenty seconds; the first delay time may be less than about twenty seconds and the second delay time may be less than about forty five seconds; the first delay time may be less than about forty-five seconds and the second delay time may be less than about ten minutes; and the first delay time may be less than about forty-five seconds and the second delay time may be greater than about ten minutes up to about two hours. These are just some examples.
• Theprocessor64 may be programmed such that it is fully functional when full power is available from theenergy storage device86. For example, when full power is available from theenergy storage device86, theprocessor64 may be configured to receive and make 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. In addition, theprocessor64 may be able to receive and execute firmware and software updates including, for example, a firmware upgrade.
• When less than full power is available from theenergy storage device86, the functionality of theprocessor64 may be limited and/or certain actions may be prohibited. For example, when the amount of available power is determined by theprocessor64 to be below a first predetermined threshold indicating that the HVAC controller is not fully charged, then only select functions may be carried out by theprocessor64. In some cases, theprocessor64 may be programmed to execute selected functions and/or prohibit certain actions when the amount of available power stored in theenergy storage device86 is determined to be less than about 75% of the full available power. For example, in some instances, firmware and/or software updates may be prohibited by theprocessor64, but theprocessor64 may still permit 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. Additionally, the delay time between when a first message is transmitted to the web server via thecommunications block60 and when a second message is transmitted may be increased by at least 50% and up to about 500% or more. In one example, the delay between transmission of a first message and a second message may be increased from about 5 seconds to about 20 seconds. This is just one example.
• In other cases, when the amount of available power stored in theenergy storage device86 is determined to be less than a second predetermine threshold and is indicative of low power availability, then theprocessor64 may be limited to executing simple, basic functions, may delay some functions, and may prohibit other functions. For example, when the amount of available power stored in the energy storage device is determined to be less than about 40% of the full available power, then theprocessor64 may be unable to send and/or receive data to and from the web server, update an operating schedule, and/or change an operating mode. Firmware updates and/or software upgrades may be prohibited. Theprocessor64 may permit a temperature set point and/or humidity setpoint to be changed; however, theprocessor64 may initiate a delay between when the set point change is accepted and when it is actually implemented at theHVAC controller18. Additionally, the delay time between when a first message is transmitted to the web server via thecommunications block60 and when a second message is transmitted may be increased by at least 50% and up to about 500% or more. In one example, the delay time between transmission of a first message and a second message may be increased from about 20 seconds to about 45 seconds. This is just one example.
• In still yet other cases, when the amount of available power stored in theenergy storage device86 is determined to be less than a third predetermined threshold and is indicative of critically low available power, then very limited functions may be permitted by theprocessor64. In instances, wherein the amount of available power stored in theenergy storage device86 is determined to be less about 25% of the full available power, theprocessor64 may be configured to transmit a message to theweb server66 via thecommunications block60 that indicates when the next message from theHVAC controller18 may be expected. For example, in one instance, theprocessor64 may transmit a message indicating that power at theHVAC controller18 is critically low and that transmission of a subsequent message may occur in approximately one hour. In other instances, theprocessor64 may transmit a message indicating that power at theHVAC controller18 is critically low and that transmission of a subsequent message may occur in approximately two hours, four hours, six hours, and/or the like. In some cases, theprocessor64 may be further programmed to display a message to the user via theuser interface108 that notifies the user that the power in thecontroller18 is critically low. In other cases, theserver66 may be configured transmit a message notifying the user that the power is critically low via SMS text message or email message. In addition, theprocessor64 may be programmed increase the delay time from the previous delay time to at least one hour and enter a sleep mode.
• FIG. 5 is a schematic view of anillustrative server66 that may be in communication with theHVAC controller18 over a network, as described herein. Theserver66 may be adedicated web server66 such as, for example, Honeywell's TOTAL CONNECT™ web server that provides a web service in which both theHVAC controller18 and the user'sremote device62 may be enrolled. Theserver66 may be coupled to theHVAC controller18 over thesecond network58 via a gateway and/or via a local area network located within the user's home such as described above (see, for example,FIG. 2). Additionally, theserver66 may be accessed by a user over thesecond network58 using aremote device62.
• As shown inFIG. 5, theserver66 may include at least one input/output port110 for sending and/or receiving data oversecond network58 to and from theHVAC controller18 and/or the user'sremote device62. Theserver66 may also include adata storage device114, and acontroller118 coupled to theinput output port110 and thedata storage device114. In some cases, thecontroller118 may be configured to implement aweb application122 for serving up one or more web pages over thesecond network58 via the input/output port110. The one or more web pages may be accessed and viewed by a user through the user interface of any number of internet capable or WiFi-enabled remote devices such as, for example, a user's smart phone or tablet computer using a standard web browser. In some cases, the one or more web pages may provide avirtual user interface108 for controlling theHVAC controller18. Through the one or more web pages forming thevirtual user interface108, a user may enter or change various HVAC operating parameters including, but not limited, to temperature set points, humidity set points, starting times, ending times, schedule times, diagnostic limits, and/or the like, as well as respond to one or more alerts. While web pages are used as one example, it is contemplated that theserver66 may interact with a user via an application program running on the user'sremote device62.
• In some cases, theserver66 may facilitate communication between a user'sremote device62 and theHVAC controller18 by translating input from the user'sremote device62 to theHVAC controller18. For example, a user may make a change to theHVAC controller18 through the user interface provided by an app executed on theirremote device62. This change is then transmitted from the user'sremote device62 to theweb server66. Theweb server66 may then send a message to theHVAC controller18. Similarly, if a change to theHVAC controller18 is made at the HVAC controller, a message indicating the change may be transmitted from theHVAC controller18 to theserver66, and then theserver66 may send a message to the user's remote device where the change may be reflected by an app executed on the user's remote device.
• As discussed herein, in some cases, theHVAC controller18 may be programmed to periodically poll theexternal web server66 via thesecond network58. The rate at which theHVAC controller18 polls theexternal web server66 may control, at least in part, the overall communication rate between theHVAC controller18, theweb server66, and a user'sremote device62. Typically, a faster polling rate may be expected to produce lower message latencies which may be desirable when the user is located in close proximity to theHVAC controller18 because the user may observe the effect of their interaction with a minimal amount of waiting time. If the message latency is too slow, the user may become concerned that communication between theweb server66, theHVAC controller18 and/or the user's remote device has been disrupted. Because a faster polling rate may use a greater amount of energy, in some cases, the polling rate may be dependent upon the amount of available energy at theHVAC controller18.
• In some cases, theserver66 may receive at least one message from theHVAC controller18 that is related to the available amount of power stored in theenergy storage device86 of theHVAC controller18 as determined by theprocessor64. In some cases, as discussed herein, at least one message may indicate a measure related to the delay time until a subsequent message may be expected to be transmitted by theHVAC controller18 to theserver66. Upon receiving at least one message indicating a measure related to the delay time, thecontroller118 may be programmed to determine a power status of theHVAC controller18 based on the measure related to the delay time include in the message. For example, in one instance, thecontroller118 may be configured to determine that theHVAC controller18 is no longer fully powered when the delay time indicated by the message received from theHVAC controller18 is greater than a first predetermined threshold. In another instance, thecontroller118 may be configured to determine that theHVAC controller18 has a low power status when the delay time indicated by the message received from theHVAC controller18 is greater than a second predetermined threshold. In yet another instance, thecontroller118 may determine that theHVAC controller18 has a critically lower power status when the delay time indicated by the message received from theHVAC controller18 is greater than a third predetermined threshold. The message may include an actual delay time (e.g. 1 minute), or may include a parameter (e.g. power status) that theserver66 then translates into an actual delay time. Because theserver66 is informed by theHVAC controller18 of a communication delay, theserver66 will not report a disruption in communication or a communication error when theHVAC controller18 enters an extended sleep period. This may eliminate false reporting of a communication error.
• In other cases, theserver66 may be configured to periodically poll theHVAC controller18 located within the building via thesecond network58. Thecontroller118 may be programmed to control the communication rate based, at least in part, on the amount of available power stored in the energy storage device of theHVAC controller18. For example, thecontroller118 may be configured to change a communication rate between theHVAC controller18 and theserver66 in response to receiving a message from theHVAC controller18 that indicates that theHVAC controller18 has a lower power status. For example, as discussed herein, if a message received from theHVAC controller18 in response to a poll from theserver66 indicates that the HVAC controller has a lower power status, then thecontroller118 may be programmed to change the delay between successive transmission of messages during subsequent communication between theHVAC controller18 and theserver66. In many cases, thecontroller118 may increase the delay time between successive messages transmitted between theHVAC controller18 and theserver66. For example, in one instance, thecontroller118 may be configured to increase the delay time between two or messages transmitted between theHVAC controller18 and theserver66 from a first delay time to a second delay time in response to receiving a message from theHVAC controller18 indicating that the power status of theHVAC controller18 is less than 100 percent. The second delay time may be greater than the first delay time. In another instance, thecontroller118 may be configured to increase the delay time between two or messages transmitted between theHVAC controller18 and theserver66 from the second delay time to a third delay time in response to receiving a message from theHVAC controller18 indicating that theHVAC controller18 has a low power status. The third delay time may be greater than the second delay time. In yet another instance, thecontroller118 may be configured to increase the delay time between two or messages transmitted between theHVAC controller18 and theserver66 from the third delay time to a fourth delay time in response to receiving a message from theHVAC controller18 indicating that theHVAC controller18 has a critically low power status.
• In some cases, thecontroller118 may be further programmed to buffer one or more messages to be transmitted from theserver66 to theHVAC controller18 until the next subsequent communication time based on the delay time. When the next message is received from theHVAC controller18, thecontroller118 may transmit the buffered messages to theHVAC controller18 over thesecond network58 via the input/output port110 in a rapid communication burst. The one or more buffered messages transmitted from thecontroller118 to theHVAC controller18 may include 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. In some cases, these changes may be reflective of changes made by a user via auser interface108 provided at the user'sremote device62 or via one or more web pages served up the by theserver66. Additionally, the one or more buffered messages may include firmware and/or software upgrades. As discussed herein, whether or not theHVAC controller18 is able to implement the changes included in the one or more buffered messages transmitted by theserver66 may be dependent on the amount of available power stored in theenergy storage device86 of theHVAC controller18. TheHVAC controller18 may also buffer messages that are to be transmitted to theserver66. For example, if a user changes a set point at the local user interface of the HVAC controller, this change may be buffered until the next communication time. Also, any alerts or other information that should be transmitted to theserver66 may be buffered by the HVAC controller. When the next communication time arrives, the HVAC controller may transmit the buffered messages to theserver66 in a rapid communication burst.
• Additionally, thecontroller118 of theserver66 may be further configured to transmit a message to a user indicative of the power status of theHVAC controller18 in response to determining that theHVAC controller18 has a lower power status based on the delay time indicated by the message received from theHVAC controller18 or upon receiving a message indicative of the lower power status of theHVAC controller18. In some cases, thecontroller118 may be programmed to transmit a user message indicating the lower power status of theHVAC controller18 over thesecond network58 via the input/output port110 to the user'sremote device62. In some cases, the user message may be an alert that alerts the user to the low power status of theHVAC controller18 and/or notifies the user as to a possible service disruption between theHVAC controller18 and theserver66. The message transmitted by thecontroller118 may include a command which may cause the user'sremote device62 to display the user message on the display of the user interface of the user's remote device indicating the lower power status of theHVAC controller18. In some cases, the user message indicative of the lower power status of theHVAC controller18 may be displayed by an app executed by the user'sremote device62. In other cases, the user message may be transmitted as an SMS text message or an email message. An SMS text message transmitted by thecontroller118 may be received by the user'sremote device62 and displayed on the display of the user interface of the user's remote device by the text messaging application program executed by the user'sremote device62. An email message transmitted by thecontroller118 may be received at the user's email address that is associated with the user's account or profile on the web service (e.g. Honeywell's TOTAL CONNECT™ web service). The email from thecontroller118 may be accessed and displayed on the display of the user interface of theremote device62 by any number of email services that may be accessed using a web browser provided on the user's remote device. Additionally, the user message transmitted by thecontroller118 may be displayed on the display of theuser interface108 located at theHVAC controller18.
• FIGS. 6-9 are illustrative screens including a user message that may be displayed to a user via auser interface108 provided by an app executed by a user'sremote device62 or by one or more web pages that may be served up over the network via theserver66. In some cases, similar screens may be displayed on the display of the local user interface provided at theHVAC controller18.
• Screen150, shown inFIG. 6, includes an illustrative example of afirst user message154 that may be displayed on the display of the user interface of theHVAC controller18 and/or a user'sremote device62 upon determining that theHVAC controller18 has a lower power status. For example, as discussed herein, thecontroller118 may determine that the amount of available power stored in theenergy storage device86 at theHVAC controller18 is less than 100 percent based on the delay time indicated by the message received from theHVAC controller18. Thefirst user message154 may include an indication of the power status of theHVAC controller18. In some cases, the power status indication may be provided as a short text string156 describing the power status of the HVAC controller18 (e.g. power is less than 100%, low power, medium power, power critical, etc.). Theuser message154 also may include additional information about the lower power status. For example, in some cases, the additional information may describe an action taken by theHVAC controller18 in response to the lower power status. In other cases, abattery status indicator158 depicting abattery160 representing the amount of available power may be displayed. Thebattery status indicator158 may include anindication162 of the percentage of power remaining in theenergy storage device86. As shown inFIG. 6, theindication162 of the percentage of remaining available power stored in theenergy storage device86 may be displayed adjacent to depiction of thebattery160. Additionally, in some cases, thebattery status indicator158 may change colors from green, to yellow, to orange, to red to visually indicate to the user the power status of theHVAC controller18. The user may acknowledge theuser message154 by selecting anokay button166 or other similar button that may displayed on the display of the user interface adjacent to theuser message154.
• Screen180, shown inFIG. 7, includes an illustrative example of asecond user message184 that may be displayed on the display of the user interface of theHVAC controller18 and/or user'sremote device62 upon determining that theHVAC controller18 has a low power status. For example, as discussed herein, thecontroller118 may determine that the amount of available power stored in theenergy storage device86 at theHVAC controller18 is low based on the delay time indicated by the message received from theHVAC controller18. Thesecond user message184 may include an indication of the low power status of theHVAC controller18. In some cases, the low power status indication may be provided as ashort text string186 describing the power status of the HVAC controller18 (e.g. low power). Theuser message184 also may include additional information about the low power status. For example, in some cases, the additional information may indicate to the user that only selected functions may be carried out theHVAC controller18 and/or which functions may be prohibited due to the low power status of theHVAC controller18. Additionally, in other cases, abattery status indicator188 depicting abattery190 representing the amount of available power may be displayed in addition to or instead of theuser message184. Thebattery status indicator188 may include anindication192 of the percentage of power remaining in theenergy storage device86. As shown inFIG. 7, theindication192 of the percentage of remaining available power stored in theenergy storage device86 may be displayed adjacent to depiction of thebattery190. Additionally, in some cases, thebattery status indicator188 may change colors from green, to yellow, to orange, to red to visually indicate to the user the power status of theHVAC controller18. In this example, thebattery status indicator158 may be orange to visually indicate the low power status of theHVAC controller18. The user may acknowledge theuser message184 by selecting an okay button196 or other similar button that may displayed on the display of the user interface adjacent to theuser message184.
• Screen200, shown inFIG. 8, includes an illustrative example of athird user message204 that may be displayed on the display of the user interface of theHVAC controller18 and/or the user's remote device upon determining that theHVAC controller18 has a critically low power status. For example, as discussed herein, thecontroller118 may determine that the amount of available power stored in theenergy storage device86 at theHVAC controller18 is critically low based on the delay time indicated by the message received from theHVAC controller18. Thesecond user message204 may include an indication of the critically low power status of theHVAC controller18. In some cases, the power status indication may be provided as ashort text string206 describing the power status of the HVAC controller18 (e.g. power is critical or critically low power). Theuser message204 also may include additional information about the low power status. For example, in some cases, the additional information may indicate to the user that only selected functions may be carried out theHVAC controller18 and/or which functions may be prohibited based due to the low power status of theHVAC controller18. In other cases, theuser message204 may include auser prompt208, prompting the user to take a desired action to address the low power state of theHVAC controller18. For example, theuser prompt208 may prompt the user to add a common wire (C-wire) to the wiring configuration for the HVAC system4 to supply power to theHVAC controller18. In other cases, theuser prompt208 may prompt the user to change their battery or temporarily operate the fan to power theHVAC controller18 in order to charge theenergy storage device86. These are just cases. In addition to theuser message204 and/oruser prompt208, abattery status indicator212 depicting abattery214 representing the amount of available power may be displayed. Thebattery status indicator212 may include anindication216 of the percentage of power remaining in theenergy storage device86. As shown inFIG. 8, theindication216 of the percentage of remaining available power stored in theenergy storage device86 may be displayed adjacent to depiction of thebattery214. Additionally, in some cases, thebattery status indicator212 may change colors from green, to yellow, to orange, to red to visually indicate to the user the power status of theHVAC controller18. In this example, thebattery status indicator212 may be red to visually indicate the low power status of theHVAC controller18. The user may acknowledge theuser message204 by selecting anokay button220 or other similar button that may displayed on the display of the user interface adjacent to theuser message204.
• FIG. 9 shows ascreen250 including an example of anillustrative user message254 that may be displayed to the user on the display of a user interface of theHVAC controller18 and/or user'sremote device62 when thecontroller118 determines that theHVAC controller18 has been restored to full power. Thecontroller118 may determine thatHVAC controller18 has been restored to full power based on a decrease in the delay time indicated by a message received from theHVAC controller18. Theuser message254 may include an indication of the full power status of theHVAC controller18. In some cases, the power status indication may be provided as ashort text string206 describing the power status of the HVAC controller18 (e.g. full power or full power has been restored). In addition to theuser message254, abattery status indicator262 depicting abattery264 representing the amount of available power may be displayed. Thebattery status indicator262 may include anindication266 of the percentage of power available in theenergy storage device86. As shown inFIG. 9, theindication266 of the percentage of remaining available power stored in theenergy storage device86 may be displayed adjacent to depiction of thebattery264. Additionally, in some cases, thebattery status indicator212 may be green to visually indicate to the user the fully powered status of theHVAC controller18. The user may acknowledge theuser message254 by selecting anokay button270 or other similar button that may displayed on the display of theuser interface108.
• 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.

Claims (22)

What is claimed is:

1. A building controller, comprising:

an input/output block configured to send one or more control signals to control one or more building components;

a communications port configured to send and/or receive messages via a communications network;

an energy storage device for powering at least part of the building controller; and

a controller operatively coupled to the input/output block, the communications port, and the energy storage device, the controller is configured to determine an available amount of power stored in the energy storage device and is further configured to communicate, via the communications port, a message that is indicative of a delay until a subsequent communication time, wherein the delay is dependent upon the determined available amount of power stored in the energy storage device.

2. The building controller ofclaim 1, wherein:

for a first available amount of power stored in the energy storage device, the controller communicates a first message that is indicative of a first delay until a subsequent communication time; and

for a second available amount of power stored in the energy storage device, the controller communicates a second message that is indicative of a second delay until a subsequent communication time;

wherein the first available amount of power is greater than the second available amount of power, and the first delay is shorter than the second delay.

3. The building controller ofclaim 2, wherein the first delay is less than 10 seconds, and the second delay is greater than 30 seconds.

4. The building controller ofclaim 2, wherein the first delay is less than 10 seconds, and the second delay is greater than 10 minutes.

5. The building controller ofclaim 1, wherein the controller is configured to determine if the available amount of power is below a predetermined threshold and is indicative of a reduced power state of the energy storage device, and if so, the controller is configured to increase the delay relative to when the available amount of power is above the predetermined threshold.

6. The building controller ofclaim 5, wherein if the controller determines that the available amount of power is below the predetermined threshold, at least one function of the building controller are prohibited.

7. The building controller ofclaim 6, wherein the at least one function that is prohibited comprises performing a firmware upgrade for the building controller.

8. The building controller ofclaim 6, wherein the at least one function that is prohibited comprises changing one or more schedule parameters.

9. The building controller ofclaim 1, wherein the communications port comprises a wireless transceiver for wirelessly sending and/or receiving messages over a wireless network.

10. The building controller ofclaim 1, wherein the building controller is a thermostat.

11. The building controller ofclaim 1, wherein the controller is configured to enter the building controller into a sleep mode during the delay.

12. The building controller ofclaim 11, wherein, in the sleep mode, the communications port is in a lower power state.

13. A method of communicating with a building controller, wherein the building controller includes an energy storage device for powering at least part of the building controller, and a communications port for sending and/or receiving messages to an external server via a network at successive communication times separated by a delay, the method comprising:

determining an available amount of power stored in the energy storage device;

setting the delay between successive communication times, wherein the delay is set based, at least in part, on the determined amount of available power stored by the energy storage device.

14. The method ofclaim 13, further comprising determining if the available amount of power is below a predetermined threshold and is indicative of a reduced power state of the energy storage device, and if so, increasing the delay relative to when the available amount of power is above the predetermined threshold.

15. The method ofclaim 14, wherein if the available amount of power is determined to be below the predetermined threshold, prohibiting at least one function of the building controller.

16. The method ofclaim 15, wherein the at least one function that is prohibited comprises performing a firmware upgrade for the building controller.

17. The method ofclaim 15, wherein the at least one function that is prohibited comprises changing one or more schedule parameters.

18. The method ofclaim 13, further comprising entering the building controller into a sleep mode during the delay.

19. A system comprising a building controller in communication with a server over a network, the system comprising:

a building controller located within a building comprising:

a command module for sending one or more control signals to one or more building components;

a communications module for sending and/or receiving messages to and/or from a web server via a network;

a power module for powering at least part of the building controller;

a controller operatively coupled to the command module, the communications module, and the power module, the controller is configured to determine an available amount of power stored in the power module and is further configured to communicate, via the communications module, one or more messages that is related to the determined available amount of power stored in the power module; and

a server in communication with the building controller over the network, the server configured to receive the one or more messages that is related to the determined available amount of power stored in the power module of the building controller, the server further configured to transmit a message to a user device via the network, wherein the message notifies the user as to the power state of the building controller.

20. The system ofclaim 19, wherein the server does not report a communication failure.

21. The system ofclaim 19, wherein the server is configured to report a message indicative of the expected delay from a last message received from the building controller.

22. The system ofclaim 19, wherein the building controller and the server communicate at successive communication times separated by a delay, and wherein the delay is set based, at least in part, on the determined amount of available power stored by the power module.

Images