Geofence plus schedule for a building controller

Information

  • Patent Grant
  • 10488062
  • Patent Number
    10,488,062
  • Date Filed
    Friday, July 22, 2016
    8 years ago
  • Date Issued
    Tuesday, November 26, 2019
    4 years ago
  • CPC
  • Field of Search
    • CPC
    • F24F11/0034
    • F24F2011/0035
    • F24F2011/0047
    • H04W4/021
  • International Classifications
    • F24F11/30
    • H04W4/021
    • F24F120/10
    • F24F140/60
    • F24F120/12
    • F24F110/00
    • F24F120/20
    • F24F11/65
    • F24F11/56
    • F24F11/61
    • Term Extension
      27
Abstract
A building control system that uses geofencing in conjunction with a time-based schedule when control one or more building systems. In one example, geofencing may be used to determine if the building is occupied or unoccupied. If the building is determined to be unoccupied via geofencing, the building controller may control to an unoccupied setpoint. If the building is determined to be occupied via geofencing, the HVAC controller may control in accordance with a time-based schedule.
Description
TECHNICAL FIELD

The present disclosure pertains to building control systems such as Heating, Ventilation, and/or Air Conditioning (HVAC) systems, security systems, lighting systems and the like. More particularly, the present disclosure pertains to methods and systems for controlling such building control systems.


BACKGROUND

Building control systems are used to control conditions within a building or other structure. Example building control systems include HVAC systems, security systems, and lighting systems. HVAC systems, for example, are often used to control the comfort level within a building or other structure. In some cases, and to save energy, an HVAC controller may be configure to control to a more energy efficient setpoint when the building is expected to be unoccupied than when the building is expected to be occupied. In some instances, geofencing may be used to determine if the building is occupied or unoccupied. If the building is determined to be occupied, the HVAC controller may control to an occupied setpoint, and if the building is determined to be unoccupied, the HVAC controller may control to an unoccupied setpoint. What would be desirable is to provide additional control options when the building is determined to be occupied.


SUMMARY

The present disclosure pertains to building control systems such as Heating, Ventilation, and/or Air Conditioning (HVAC) systems, security systems, lighting systems and the like. More particularly, the present disclosure pertains to methods and systems for controlling such building control systems.


In a particular example of the disclosure, a method of operating a building controller that is configured to control one or more building systems in combination with a mobile device that has location services includes identifying if the mobile device is inside a geofence or outside the geofence. In some cases, and if the mobile device is identified to be outside the geofence, the building controller may control at least one building system in accordance with an AWAY setting. If the mobile device is identified to be inside the geofence, the building controller may control the at least one building system in accordance with a current time in conjunction with a time-based HOME schedule, wherein the time-based HOME schedule includes two or more time periods each with a corresponding HOME setting. When the current time is in one of the two or more time periods of the time-based HOME schedule, the building controller controls the at least one building system in accordance with the corresponding HOME setting. This may be considered as combining geofencing and time based scheduling.


In another example of the disclosure, a method of operating an HVAC controller that is configured to control one or more HVAC components of a building in combination with a mobile device that has location services includes identifying if the mobile device is inside a geofence or outside the geofence. In some cases, and if the mobile device is identified to be outside the geofence, at least one HVAC component of the building may be controlled in accordance with an AWAY setting that sets one or more HVAC parameters for use when the building is unoccupied. If the mobile device is identified to be inside the geofence, the at least one HVAC component of the building may be controlled in accordance with a time-based HOME schedule, wherein the time-based HOME schedule includes two or more time periods each with a corresponding HOME setting, wherein the HOME setting for a first one of the two or more time periods is different from the HOME setting for a second one of the two or more time periods.


In another example of the disclosure, a method of operating a building controller that is configured to control one or more building systems in combination with a plurality of mobile devices that each have location services includes identifying if each of the plurality of mobile devices is inside a corresponding geofence or outside the corresponding geofence. In some cases, if all of the plurality of mobile devices are identified to be outside their corresponding geofence, the building controller may control at least one building system in accordance with an AWAY setting. If one or more of the plurality of mobile devices are identified to be inside their corresponding geofence, the building controller may control the at least one building system in accordance with a time-based HOME schedule, wherein the time-based HOME schedule includes two or more time periods each with a corresponding HOME setting.


The preceding summary is provided to facilitate an understanding of some of the features of 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 FIGURES

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



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 perspective view of an illustrative thermostat assembly that may be used in the HVAC system of FIG. 1 or FIG. 2;



FIG. 4 is a schematic view of an illustrative HVAC controller that may, for example, form part of the HVAC system of FIG. 1 or FIG. 2;



FIG. 5 is a schematic view of an illustrative HVAC controller that may, for example, form part of the HVAC system of FIG. 1 or FIG. 2;



FIG. 6 is a schematic view of an illustrative mobile device that may, for example, be used in combination with the HVAC system of FIG. 1 or FIG. 2;



FIG. 7 is a schematic view of an illustrative server that may, for example, form part of the HVAC system of FIG. 1 or FIG. 2;



FIG. 8 is a timing diagram showing an example of using geofencing in combination with a time-based schedule;



FIG. 9 is a flow diagram showing an illustrative method of operating a building controller in combination with a mobile device having location services;



FIG. 10 is a flow diagram showing an illustrative method of operating an HVAC controller in combination with a mobile device having location services;



FIG. 11 is a flow diagram showing an illustrative method of operating a building controller in combination with a plurality of mobile devices each having location services; and



FIGS. 12A through 12G provide illustrative but non-limiting screenshots of operating an HVAC controller in combination with a mobile device having location services.





While the disclosure is amenable to various modifications and alternative forms, specifics thereof have been shown by way of example in the drawings and will be described in detail. It should be understood, however, that the intention is not to limit the disclosure to the particular embodiments described. On the contrary, the intention is to cover all modifications, equivalents, and alternatives falling within the spirit and scope of the disclosure.


DESCRIPTION

For the following defined terms, these definitions shall be applied, unless a different definition is given in the claims or elsewhere in this specification.


All numeric values are herein assumed to be modified by the term “about,” whether or not explicitly indicated. The term “about” generally refers to a range of numbers that one of skill in the art would consider equivalent to the recited value (i.e., having the same function or result). In many instances, the terms “about” may include numbers that are rounded to the nearest significant figure.


The recitation of numerical ranges by endpoints includes all numbers within that range (e.g. 1 to 5 includes 1, 1.5, 2, 2.75, 3, 3.80, 4, and 5).


As used in this specification and the appended claims, the singular forms “a”, “an”, and “the” include plural referents unless the content clearly dictates otherwise. As used in this specification and the appended claims, the term “or” is generally employed in its sense including “and/or” unless the content clearly dictates otherwise.


It is noted that references in the specification to “an embodiment”, “some embodiments”, “other embodiments”, etc., indicate that the embodiment described may include one or more particular features, structures, and/or characteristics. However, such recitations do not necessarily mean that all embodiments include the particular features, structures, and/or characteristics. Additionally, when particular features, structures, and/or characteristics are described in connection with one embodiment, it should be understood that such features, structures, and/or characteristics may also be used connection with other embodiments whether or not explicitly described unless clearly stated to the contrary.


The present disclosure is directed generally at building automation systems. Building automation systems are systems that control one or more operations of a building. Building automation systems can include HVAC systems, security systems, fire suppression systems, energy management systems and other systems. While HVAC systems with HVAC controllers are used as an example below, it should be recognized that the concepts disclosed herein can be applied to building automation systems more generally.



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 type of HVAC system and/or the particular HVAC equipment used may depend on the geographic region. For example, natural gas fired forced air furnaces may be more common in the northern regions of the Unites States, while electric heat may be more common in the southwest. Boiler systems may be more common in the northeast region of the United States, as well as in Europe. These are just some examples.


The illustrative forced air type 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. In some cases, the HVAC controller(s) 18 may be a thermostat, such as, for example, a wall mountable thermostat, but this is not required in all embodiments. Such a thermostat may include (e.g. within the thermostat housing) or have access to one or more temperature sensor(s) for sensing ambient temperature at or near the thermostat. In some instances, the HVAC controller(s) 18 may be a zone controller, or may include multiple zone controllers each monitoring and/or controlling the comfort level within a particular zone in the building or other structure.


In the illustrative HVAC system 4 shown in 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, in addition to controlling the HVAC under the direction of the thermostat, 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 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 and cooling modes may be calculated by subtracting the return air temperature from the discharge air temperature (e.g. delta T=discharge air temperature−return air temperature).


In some cases, the equipment interface module 34 may include a first temperature sensor 38a located in the return (incoming) air duct 14, and a second temperature sensor 38b located in the discharge (outgoing or supply) air duct 10. Alternatively, or in addition, the equipment interface module 34 may include a differential pressure sensor including a first pressure tap 39a located in the return (incoming) air duct 14, and a second pressure tap 39b located downstream of the air filter 30 to measure a change in a parameter related to the amount of flow restriction through the air filter 30. In some cases, the equipment interface module 34, when provided, may include at least one flow sensor that is capable of providing a measure that is related to the amount of air flow restriction through the air filter 30. In some cases, the equipment interface module 34 may include an air filter monitor. These are just some examples.


When provided, the equipment interface module 34 may be configured to communicate with the HVAC controller 18 via, for example, a wired or wireless communication link 42. In other cases, the equipment interface module 34 may be incorporated or combined with the HVAC controller 18. In some instances, the equipment interface module 34 may communicate, relay or otherwise transmit data regarding the selected parameter (e.g. temperature, pressure, flow rate, etc.) to the HVAC controller 18. In some cases, the HVAC controller 18 may use the data from the equipment interface module 34 to evaluate the system's operation and/or performance. For example, the HVAC controller 18 may compare data related to the difference in temperature (delta T) between the return air side and the discharge air side of the HVAC system 4 to a previously determined delta T limit stored in the HVAC controller 18 to determine a current operating performance of the HVAC system 4.


In some cases, the HVAC system 4 may include ventilation. There are a number of different types of ventilation systems. Examples include passive ventilation or mechanical ventilation. Mechanical ventilation may, for example, include an actuatable damper 27 that may be disposed within a duct 25 and connected to the return air duct 14. When the damper 27 is open, fresh air from outside may be pulled into the return air duct 14 and thus into the building 2. In some cases, the actuatable damper 27 may be connected via a control line 29 to the EIM 34. It will be appreciated that additional examples of mechanical ventilation include an ERV (energy recovery ventilator) or an HRV (heat recovery ventilator).



FIG. 2 is a schematic view of an illustrative HVAC control system 50 that facilitates remote access and/or control of the illustrative HVAC system 4 shown in FIG. 1. The HVAC control system 50 may be considered a building automation system or part of a building automation system. 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 HVAC components 6 of the HVAC system 4. As discussed above, the HVAC controller 18 may communicate with the one or more HVAC components 6 of the HVAC system 4 via a wired or wireless link 20. Additionally, the HVAC controller 18 may 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, communications over a second network 58 may pass through a gateway 57, but this is not required in all cases. 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 server(s) 66. A non-limiting example of such an external web service is Honeywell's TOTAL CONNECT™ web service. The HVAC controller 18 may be configured to upload selected data via the second network 58 to the external web service where it may be collected and stored on the external web server 66. In some cases, the data may be indicative of the performance of the HVAC system 4. Additionally, the HVAC controller 18 may be configured to receive and/or download selected data, settings and/or services sometimes including software updates from the external web service over the second network 58. The data, settings and/or services may be received automatically from the web service, downloaded periodically in accordance with a control algorithm, and/or downloaded in response to a user request. In some cases, for example, the HVAC controller 18 may be configured to receive and/or download an HVAC operating schedule and operating parameter settings such as, for example, temperature setpoints, humidity setpoints, start times, end times, schedules, window frost protection settings, and/or the like from the web server 66 over the second network 58. In some instances, the HVAC controller 18 may be configured to receive one or more user profiles having at least one operational parameter setting that is selected by and reflective of a user's preferences. In still other instances, the HVAC controller 18 may be configured to receive and/or download firmware and/or hardware updates such as, for example, device drivers from the web server 66 over the second network 58. Additionally, the HVAC controller 18 may be configured to receive local weather data, weather alerts and/or warnings, major stock index ticker data, traffic data, and/or news headlines over the second network 58. These are just some examples.


Depending upon the application and/or where the HVAC user is located, remote access and/or control of the HVAC controller 18 may be provided over the first network 54 and/or the second network 58. A variety of remote wireless devices 62 may be used to access and/or control the HVAC controller 18 from a remote location (e.g. remote from the HVAC Controller 18) over the first network 54 and/or second network 58 including, but not limited to, mobile phones including smart phones, tablet computers, laptop or personal computers, wireless network-enabled key fobs, e-readers, and/or the like. In many cases, the remote wireless devices 62 are configured to communicate wirelessly over the first network 54 and/or second network 58 with the HVAC controller 18 via one or more wireless communication protocols including, but not limited to, cellular communication, ZigBee, REDLINK™, Bluetooth, WiFi, IrDA, dedicated short range communication (DSRC), EnOcean, and/or any other suitable common or proprietary wireless protocol, as desired.


In some cases, an application program code (i.e. app) stored in the memory of the remote device 62 may be used to remotely access and/or control the HVAC controller 18. The application program code (app) may be downloaded from an external web service, such as the web service hosted by the external web server 66 (e.g. Honeywell's TOTAL CONNECT™ web service) or another external web service (e.g. ITUNES® or Google Play). In some cases, the app may provide a remote user interface for interacting with the HVAC controller 18 at the user's remote device 62. For example, through the user interface provided by the app, a user may be able to change operating parameter settings such as, for example, temperature setpoints, humidity setpoints, start times, end times, schedules, window frost protection settings, accept software updates and/or the like. Communications may be routed from the user's remote device 62 to the web server 66 and then, from the web server 66 to the HVAC controller 18. In some cases, communications may flow in the opposite direction such as, for example, when a user interacts directly with the HVAC controller 18 to change an operating parameter setting such as, for example, a schedule change or a setpoint change. The change made at the HVAC controller 18 may be routed to the web server 66 and then from the web server 66 to the remote device 62 where it may reflected by the application program executed by the remote device 62.


In some cases, a user may be able to interact with the HVAC controller 18 via a user interface provided by one or more web pages served up by the web server 66. The user may interact with the one or more web pages using a variety of internet capable devices to effect a setting or other change at the HVAC controller 18, and in some cases view usage data and energy consumption data related to the usage of the HVAC system 4. In some cases, communication may occur between the user's remote device 62 and the HVAC controller 18 without being relayed through a server such as external server 66. These are just some examples.



FIG. 3 is a perspective view of an illustrative thermostat assembly 80. In some instances, the thermostat assembly 80 may be considered as an example of the HVAC controller 18 referenced in FIGS. 1 and 2. In some instances, the thermostat assembly 80 may include a thermostat 82 and a trim piece 84. The thermostat 82 may include a user interface 86 which, in some cases, may be a touch screen display such as a fixed segment touch screen display or a dot matrix touch screen display. It will be appreciated that if the user interface 86 is a fixed segment touch screen display, the ability of the thermostat 82 to rearrange what is displayed on the user interface 86 may be somewhat limited. In some cases, it will be appreciated that a touch screen display may, for example, have any number of distinct touch points where the touch screen display is configured to sense that the touch point has been touched or is being touched. In some cases, the touch screen display may have a relatively limited number of distinct touch points in order to reduce costs, for example.



FIG. 4 is a schematic view of an illustrative HVAC controller 90 that may, for example, be configured to control one or more HVAC components (such as but not limited to the HVAC component(s) 6 shown in FIG. 1 as part of the HVAC system 4) in accordance with one or more comfort parameters that define desired temperatures for particular time periods. In some cases, the HVAC controller 90 may utilize geofencing in controlling operation of the HVAC system 4 or portions thereof. In geofencing, a user may, for example, set one or more HOME comfort parameters that the HVAC controller 90 can use in controlling the HVAC system 4 when someone is home and one or more AWAY comfort parameters that the HVAC controller 90 can use in controlling the HVAC system 4 when the home is unoccupied. In some cases, one or more HOME comfort settings and/or on or more AWAY comfort parameters may be set by the user using the user interface 94 of the HVAC controller 90. In some cases, as will be discussed, the user may set or edit one or more HOME comfort settings and/or on or more AWAY comfort parameters utilizing a mobile device such as a smartphone, for example. Comfort parameters may include a heating temperature setpoint, a cooling temperature setpoint, ventilation setting, humidification and/or dehumidification settings, and/or any other suitable parameters or settings. In some cases, geofencing relies upon knowing the location of each user's mobile device (such as but not limited to a smartphone) relative to a pre-defined geofence boundary disposed about the home to determine if the home is occupied or unoccupied.


In some cases, the HVAC controller 90 may operate in accordance with a programmable schedule. The programmable schedule may include a plurality of schedule time periods. For example, in some cases, the programmable schedule may include four different time periods for each day. These four time periods may be identified as WAKE, AWAY, HOME and SLEEP. In some instances, the programmable schedule may include additional time periods. In some cases, the programmable schedule may include fewer than four distinct time periods, such as only HOME and SLEEP time periods. In some cases, different days of the week may have a different number of time periods.


In some instances, the programmable schedule may be known as a 7 day schedule, in which each of the seven days of the week may be uniquely programmed but are not required to be. In some cases, the programmable schedule may be known as a 5-2 schedule, in which each of the weekdays Monday through Friday share a first programmable schedule and the weekend days Saturday and Sunday share a second programmable schedule. In some cases, the programmable schedule may be known as a 5-1-1 schedule, in each of the weekdays Monday through Friday share a first programmable schedule, and Saturday and Sunday each can have their own unique schedule.


In some cases, a user may elect to use geofencing in conjunction with a time-based schedule. For example, geofencing may be used to determine if the building is occupied or unoccupied. If the building is determined to be unoccupied via geofencing, the HVAC controller may control to an unoccupied setpoint. If the building is determined to be occupied via geofencing, the HVAC controller may control in accordance with a time-based schedule.


In some cases, a user may decide not to use geofencing or a programmable schedule, but instead may elect to operate their HVAC controller in a manual mode. In a manual mode, the user would simply select a heating temperature setpoint for a heating mode and a cooling temperature setpoint for a cooling mode. If they are cold in the heating mode, the user could manually bump up the heating temperature setpoint a few degrees. If they are hot in the cooling mode, the user could manually drop the cooling temperature setpoint a few degrees.


In some cases, the HVAC controller 90 may include a housing 92. In some instances, the housing 92 may be considered as forming the outer structure of the thermostat 82 (FIG. 3), although this is not required in all cases. A user interface 94 may be housed by the housing 92 in such a way as to be accessible from outside of the housing 92. In some cases, for example, the user interface 94 may form a portion of an outer surface, such as the front of the outer surface, of the housing 92. In some cases, the user interface 94 may be a touch screen display. In some instances, the user interface 94 may be a fixed segment touch screen display, and may for example have a limited number of distinct touch points. In some cases, the user interface 94 may be a dot matrix touch screen display, and in some cases essentially an entire surface of the a dot matrix touch screen display 94 may provide touch points.


The illustrative HVAC controller 90 includes a controller 96 that may be configured to operate an algorithm that at least partially controls the HVAC system of the building, and outputs one or more control signals 98 to the HVAC system. In some cases, the algorithm may reference or otherwise utilize a plurality of equipment setup parameters that setup the algorithm to control the particular HVAC equipment that is used in the HVAC system of the building. These equipment setup parameters may, for example, be defined and parameter values for these equipment setup parameters may be entered during an initial configuration of the HVAC controller 90. In some cases, the algorithm may also reference or otherwise utilize one or more comfort parameters that define one or more comfort setpoints used by the algorithm when controlling the at least part of the HVAC system of the building.



FIG. 5 is a schematic view of an illustrative HVAC controller 100 that may, for example, be configured to control one or more HVAC components (such as but not limited to the HVAC component(s) 6 shown in FIG. 1 as part of the HVAC system 4. In some cases, the HVAC controller 100 may be considered as including any or all of the functionality described with respect to the HVAC controller 90, and vice versa. In some cases, the HVAC controller 100 may include a housing 92. In some instances, the housing 92 may be considered as forming the outer structure of the thermostat 82 (FIG. 3), although this is not required in all cases. A touch screen display 102 may be housed by the housing 92 in such a way as to be accessible from outside of the housing 92. In some cases, for example, the touch screen display 102 may form a portion of an outer surface, such as the front of the outer surface, of the housing 92. In some cases, the touch screen display 102 may be a fixed segment touch screen display, and may for example have a limited number of distinct touch points. In some cases, the touch screen display 102 may be a dot matrix touch screen display, and in some cases essentially an entire surface of the touch screen display 102 may provide touch points.


The illustrative HVAC controller 100 includes the controller 96 that may be configured to operate an algorithm that at least partially controls the HVAC system of the building, and outputs one or more control signals 98 to the HVAC system. In some cases, the algorithm may reference or otherwise utilize a plurality of equipment setup parameters that setup the algorithm to control the particular HVAC equipment that is used in the HVAC system of the building. These equipment setup parameters may, for example, be defined and parameter values for these equipment setup parameters may be entered during an initial configuration of the HVAC controller 90. In some cases, the algorithm may also reference or otherwise utilize one or more comfort parameters that define one or more comfort setpoints used by the algorithm when controlling the at least part of the HVAC system of the building.


The HVAC controller 100 may include a memory 104 in order to store a plurality of equipment setup parameters that setup the HVAC controller to control the particular HVAC equipment that is used in the HVAC system of the building as well as one or more comfort parameters that define one or more comfort setpoints used by the HVAC controller when controlling the at least part of the HVAC system of the building. In some cases, the controller 96 may be operably coupled to the touch screen display 102 and to the memory 104. The controller 96 may be configured to control at least a portion of the HVAC system based at least in part on the plurality of equipment setup parameters.



FIG. 6 is a schematic view of a mobile device 120 that may be used to facilitate operation of an HVAC controller. In some instances, the mobile device 120 may be considered as being an example of the remote wireless device 62 referenced in FIG. 2. In some cases, the mobile device 120 may include a user interface 122, a wireless communication port 124 and a controller 126 that is operatively coupled to the user interface 122 and the wireless communication port 124. In some cases, the mobile device 120 may include location services 128 that is operatively coupled with the controller 126. In some cases, the controller 126 may be configured to turn the location services 128 on and/or off in order for the mobile device 120 to determine its location. In some cases, the location services 128 may include GPS functionality. In some instances, the location services 128 may include an ability to triangulate from a cellular signal. In some cases, the location services 128 may utilize Wi-Fi to assist in determining a current position of the mobile device 120. In some cases, the mobile device 120 may also include a memory 130 that is operatively coupled to the controller 126 and may, for example, store information pertaining to a geofence boundary.


In some cases, the controller 126 may be configured to obtain a current location of the mobile device 120 via the location services 128 and to compare the current location with a geofence boundary that is stored in the memory 130. The controller 126 may communicate the current location relative to the geofence boundary to a remote server such as the server 66 (FIG. 2) via the wireless communication port 124, for example. In some cases, the controller 126 may only communicate whether the mobile device 120 is inside the geofence boundary or outside the geofence boundary. In some instances, the controller 126 may only communicate information indicating that a geofence boundary crossing has occurred, and optionally may include an indication of whether the geofence boundary crossing was an incoming crossing (moving towards the home) or an outgoing crossing (moving away from the home). These are just some examples.


In some cases, the user interface 122 may include or otherwise be a touch screen display that is configured to display information from the controller 126 as well as to solicit input from the user. The wireless communication port 124 may, for example, enable the mobile device 120 to communicate wirelessly with a network 54 (FIG. 2) and thus communicate with an HVAC controller such as the thermostat 18 (FIG. 2) and/or communicate with a network 58 (FIG. 2) and thus communicate with a server such as the external server 66 (FIG. 2) that can communicate with an HVAC controller.


In some cases, the controller 126 may be configured to display on the user interface 122 one or more screens that permit a user to view and/or edit various parameters such as scheduling parameters. For example, in some cases, a user may be able to view and/or edit scheduling parameters pertaining to geofencing on their mobile device 120. In some cases, it will be appreciated that the user may also be able to view and/or edit scheduling parameters related to geofencing on the user interface 94 (FIG. 4) of their HVAC controller 90. In some cases, scheduling parameters pertaining to geofencing may include but may not be limited to one or more HOME comfort settings that the HVAC controller 90 (or the HVAC controller 100) may utilize in controlling one or more HVAC components when geofencing indicates that someone is home. In some cases, the one or more HOME comfort settings may include a first HOME comfort setting corresponding to a first period of time and a second HOME comfort setting corresponding to a second period of time that is different from the first period of time. For example, a user may want to have a HOME comfort setting that takes effect during the day (and someone is home) and a different HOME comfort setting that takes effect during the evening and overnight (and someone is home). Scheduling parameters pertaining geofencing may include but may not be limited to one or more AWAY comfort settings that the HVAC controller 90 (or the HVAC controller 100) may utilize in controlling one or more HVAC components when geofencing indicates that nobody is home. Comfort settings, include HOME comfort settings and AWAY comfort settings, may include heating temperature setpoints, cooling temperature setpoints, ventilation setpoints, humidification and/or dehumidification settings, and the like.


In some cases, the memory 130 of the mobile device 120 may store an application that can be run by the controller 126 of the mobile device 120 that enables the features described herein. In some cases, some functionality or software may reside partially on the mobile device 120 and partially on a server 132 schematically illustrated in FIG. 7. In some cases, the server 132 may be considered as being an example of the remote server 66 shown in FIG. 2. Referring to FIG. 7, the server 132 may include an input/output 134 by which information is sent from the server 132 to remote devices such as the mobile device 120 (FIG. 6) and/or the HVAC controller 90 (FIG. 4). In some instances, the server 132 may also receive information from remote devices such as the mobile device 120 and/or the HVAC controller 90 (or the HVAC controller 100). The illustrative server 132 also includes a memory 136 and a controller 138. The memory 136 is operably coupled to the controller 138 such that the controller 138 has access to information stored in the memory 136. It will be appreciated that the input/output 134 may also be operably coupled to the controller 138 as shown.



FIG. 8 is a timing diagram showing an example of using geofencing in combination with a time-based schedule. It has been found that a time-based schedule and geofencing can work together to provide a homeowner with improved energy efficiency and comfort. FIG. 8 shows a time-based schedule 142 over time. The time-based schedule 142 includes a HOME temperature setpoint 142a that is active during a HOME time period and a SLEEP temperature setpoint 142b that is active during a SLEEP time period. The HOME temperature setpoint 142a may be followed when geofencing indicates that someone is home and the current time is within the HOME time period. As illustrated, the HOME time period extends from about 7:00 AM to about 9:00 PM. The SLEEP time period extends from about 9:00 PM to about 6:00 PM. In the example shown, the time-based schedule 142 is followed when geofencing indicates that someone is home. An AWAY temperature setpoint as shown in region 146c of a temperature setpoint record 146, which is typically more energy efficient that the HOME and SLEEP temperature setpoints 142a and 142b, is used when geofencing indicates that the home is unoccupied.



FIG. 8 also shows a geofencing record 144. As can be seen, the geofencing record 144, which is based at least in part on the location services of the users' mobile devices, indicates that someone is home until about 9:00 AM, that everyone was AWAY from about 9:00 AM to about 6:00 PM, and then someone was home from about 6:00 PM through the rest of the evening. A temperature setpoint record 146 demonstrates the interaction between the time-based schedule 142 and the geofencing record 144. Given the relationships between HOME, AWAKE and SLEEP temperatures, it will be appreciated that this graph indicates a heating schedule.


From 6:00 AM to 7:00 AM, region 146a of the temperature setpoint record 146 indicates that the HVAC controller controls the HVAC system in accordance with the SLEEP temperature setpoint 142b of the time-based schedule 142, since this time falls within the SLEEP time period and the geofencing record 144 indicates that the home is occupied. From 7:00 AM to 9:00 AM, region 146b of the temperature setpoint record 146 indicates that the HVAC controller controls the HVAC system in accordance with the HOME temperature setpoint 142a of the time-based schedule 142, since this time falls within the HOME time period and the geofencing record 144 indicates that the home is still occupied. At 9:00 AM, the geofencing record 144 indicates that the home becomes unoccupied. In response, and as seen in region 146c of the temperature setpoint record 146, the temperature drops to an AWAY temperature setpoint that, as indicated, may be lower (e.g. more energy efficient) than both the SLEEP temperature setpoint and the HOME temperature setpoint. At about 6:00 PM, the geofencing record 144 indicates that the home becomes occupied. In response, and as seen in region 146d of the temperature setpoint record 146, The temperature reverts to the HOME temperature until 9:00 PM, since this time falls within the HOME time period of the time-based schedule 142 and the geofencing record 144 indicates that the home is again occupied. At 9:00 PM, the geofencing record 144 still indicates that the home is occupied, and thus the temperature drops to the SLEEP temperature setpoint of the time-based schedule 142. As shown in FIG. 8, the SLEEP temperature setpoint may be intermediate between the HOME and AWAY temperature setpoints, as seen at region 146e of the temperature setpoint record 146.



FIGS. 9 through 11 are flow diagrams showing illustrative methods of operating a building controller. In some cases, the building controller controls at least one building system such as a security system, a lighting system and/or an HVAC system. In some cases, the building controller may be an HVAC controller such as the HVAC controller 90 (FIG. 4) and/or the HVAC controller 100 (FIG. 5). It will be appreciated that at least some of the steps illustrated may be carried out at least in part by an HVAC controller such as the HVAC controller 90 (or the HVAC controller 100). In some cases, at least some of the steps illustrated may be carried out at least in part by a server such as the server 132 and/or the remote server 66. In some cases, at least some of the steps illustrated may be carried out by a mobile device such as the mobile device 120 operating an appropriate application.


In FIG. 9, a method 150 includes an optional block 152 at which one or more settings may be programmed in the field. In some cases, this includes programming one or more settings via the user interface 122 of the mobile device 120. In some cases, this includes programming one or more settings via the user interface 94 of the HVAC controller 90 (or via the touch screen display 102 of the HVAC controller 100). Illustrative but non-limiting examples of such settings include programming a time-based HOME schedule, which may include programming a HOME setting for each of the two or more periods (e.g. HOME, SLEEP) of the time-based HOME schedule. Another example includes programming one or more geofence settings, such as a geofence radius and one or more AWAY settings.


At decision block 154, a determination is made as whether the mobile device is inside a geofence or is outside the geofence. In some instances, this determination may be made by a controller within the mobile device or within a remote server, for example. In some cases, the determination may be made by a remote server based on an indication of a geofence crossing received from a mobile device. In some cases, the determination may be made by the mobile device and communicated to a server. In some cases, the server may operatively communicate to a building controller whether the mobile device is identified to be inside the geofence or outside the geofence. In some instances, the server may instruct the building controller to control the at least one building system in accordance with a particular setpoint.


If it is determined that the mobile device is outside the geofence, control is passed to block 158, wherein the at least one building system may be controlled via the building controller in accordance with an AWAY setting, such as an AWAY setpoint. If it is determined that the mobile device is inside the geofence, control is passed to block 156, wherein the at least one building system may be controlled via the building controller in accordance with a current time in conjunction with a time-based schedule. The time-based schedule may include two or more time periods (e.g. HOME, SLEEP) each with a corresponding HOME setting, and wherein when the current time is in one of the two or more time periods of the time-based HOME schedule, the building controller may control the at least one building system in accordance with the corresponding HOME setting.


In some cases, the AWAY setting may include a temperature setpoint that represents an energy-savings temperature setting. In some cases, the HOME setting of a first one of the two or more time periods may include a temperature setpoint that represents a first comfort temperature setting, and the HOME setting of a second one of the two or more time periods may include a temperature setpoint that represents a second comfort temperature setting that is different from the first comfort temperature setting. In some cases, the first one of the two or more time periods may correspond to a portion of a day when the user of the mobile device is expected to be awake, and the second one of the two or more time periods may correspond to a portion of a day when the user of the mobile device is expected to be asleep.


In FIG. 10, a method 160 of operating an HVAC controller that is configured to control one or more HVAC components of a building in combination with a mobile device that has location services includes identifying if the mobile device is inside a geofence or outside the geofence, as generally indicated at decision block 162. If the mobile device is identified to be inside the geofence, control is passed to block 164, where the at least one HVAC component of the building may be controlled in accordance with a time-based HOME schedule. The time-based HOME schedule may include two or more time periods each with a corresponding HOME setting, wherein the HOME setting for a first one of the two or more time periods is different from the HOME setting for a second one of the two or more time periods. If the mobile device is identified to be outside the geofence, control is passed to block 166, wherein at least one HVAC component of the building may be controlled in accordance with an AWAY setting that sets one or more HVAC parameters for use when the building is not occupied.


In FIG. 11, a method 170 of operating a building controller that is configured to control one or more building systems in combination with a plurality of mobile devices that each have location services includes identifying if each of the plurality of mobile devices is inside a corresponding geofence or outside the corresponding geofence, as generally indicated at block 172. In some cases, each of the plurality of mobile devices have the same corresponding geofence about a home. In some cases, and if all of the plurality of mobile devices are identified to be outside their corresponding geofence about the home, the building controller may control at least one building system in accordance with an AWAY setting, as seen at block 174. In some cases, and if one or more of the plurality of mobile devices are identified to be inside their corresponding geofence, the building controller may control the at least one building system in accordance with a time-based HOME schedule. The time-based HOME schedule may include two or more time periods (e.g. HOME, SLEEP) each with a corresponding HOME setting, as indicated at block 176. In some cases, a first one of the two or more time periods may correspond to a portion of a day when at least some of the users of the plurality of mobile devices are expected to be awake, and a second one of the two or more time periods may correspond to a portion of the day when all of the users of the plurality of mobile devices are expected to be asleep.



FIGS. 12A through 12G provide illustrative but non-limiting examples of screens that may be displayed on the mobile device 120 (FIG. 6) and/or on a screen of the HVAC controller 90 (or 100) pertaining to combining functionality of a time-based schedule with geofencing. FIG. 12A shows a screen 200 that may be displayed when a user is configuring their HVAC controller. The illustrative screen 200 includes a navigation bar 202 that has, as shown, a Location tab 204 and a Time tab 206. While not illustrated, in some cases the navigation bar 202 may include additional tabs. As can be seen, the Location tab 204 has been selected, as indicated by an indicator bar 210 disposed adjacent the Location tab 204. In some cases, the indicator bar 210 may instead be manifested by bolding the Location tab 204, or having the Location tab 204 flash, or blink, or appear in a different color. As can be seen, the screen 200 includes an information section 212 that informs the user of some features and functions of geofencing. A LEARN MORE button 214, if selected, may enable the user to learn more about geofencing. A USE GEOFENCING button 216, if selected, selects geofencing as the desired control option, and proceeds to one or more additional screens that enable the user to make geofencing-related setting choices.



FIG. 12B shows a screen 240 that enables a user to set HOME temperature setpoints for when geofencing indicates that the home is occupied, as indicated by a query 242. An icon 244 includes an up arrow 244a and a down arrow 244b that may be used as desired to increase or decrease a cooling temperature setpoint 244c. An icon 246 includes an up arrow 246a and a down arrow 246b that may be used as desired to increase or decrease a heating temperature setpoint 246c. A BACK button 248 and a NEXT button 250 may be used to navigate linearly between screens. In this example, selecting the NEXT button 250 causes a screen 260 of FIG. 12C to be displayed. The screen 260 of FIG. 12C enables the user to select AWAY heating and cooling temperature setpoints for when geofencing indicates that the home is unoccupied, as indicated by the query 242.


Pressing the NEXT button 250 on the screen 260 may cause a screen 270 of FIG. 12D to be displayed. The screen 260 includes an inquiry 272 that asks the user if they want to setup a time based schedule to be used in conjunction with geofencing. An infographic 274 informs the user that they can have their thermostat operate in accordance with a comfortable temperature for sleeping, when geofencing indicates that the home is occupied. The screen 260 includes a YES button 276 that may be selected to set up a SLEEP time and temperature, and a NO button 278 that the user may select if they choose not to set up a SLEEP time and temperature. Selecting the YES button 276 may cause a screen 280, as seen in FIG. 12E, to be displayed.


In FIG. 12E, the screen 280 includes an inquiry 282 asking the user to indicate what time they typically go to sleep and what time they typically wake up. A sleep start bar 284 displays a starting time for SLEEP, and the user may be able to modify the starting time by selecting the sleep start bar 284 and then adjusting the start time accordingly. A sleep end bar 286 displays an ending time for SLEEP, and the user may be able to modify the ending time by selecting the sleep end bar 286 and then adjusting the ending time accordingly. An inquiry 288 asks the user to indicate their desired sleeping temperature setpoints. An icon 244 includes an up arrow 244a and a down arrow 244b that may be used as desired to increase or decrease a cooling temperature setpoint 244c. An icon 246 includes an up arrow 246a and a down arrow 246b that may be used as desired to increase or decrease a heating temperature setpoint 246c. The BACK button 248 may be used to return to a previous screen. The NEXT button 250, if selected, may cause a screen 290, as seen in FIG. 12F, to be displayed.


In FIG. 12F, the screen 290 permits the user to review their settings for when they are home and when they are away. In particular, a WHEN I'M HOME header 292 introduces a home settings bar 294 that includes a heating temperature setpoint and a cooling temperature setpoint to use when geofencing indicates that the home is occupied and the current time is outside of the SLEEP period. A sleep settings bar 296 shows the starting and ending times for the SLEEP period as well as the heating and cooling temperature setpoints to use when geofencing indicates that the home is occupied and the current time is within the SLEEP period. A WHEN I'M AWAY header 298 introduces an away settings bar 300 that includes a heating temperature setpoint and a cooling temperature setpoint to use when geofencing indicates that the home is not occupied, regardless of time of day. A DONE button 302 enables the user to exit and return to a previous menu.


Returning briefly to FIG. 12D, if the user selects the NO button 278, a screen 310 may be displayed, as seen in FIG. 12G. In FIG. 12G, the screen 310 permits the user to review their settings for when they are home and when they are away. In particular, the WHEN I'M HOME header 292 introduces the home settings bar 294 that includes a heating temperature setpoint and a cooling temperature setpoint to use when geofencing indicates that the home is occupied. The WHEN I'M AWAY header 298 introduces the away settings bar 300 that includes a heating temperature setpoint and a cooling temperature setpoint to use when geofencing indicates that the home is not occupied. A DONE button 302 enables the user to exit and return to a previous menu. In some cases, as illustrated, the screen 310 may include a CREATE SLEEP SETTINGS icon 312 that, if selected, may cause the screen 240 (FIG. 12B) to be displayed.


It should be understood that this disclosure is, in many respects, only illustrative. Changes may be made in details, particularly in matters of shape, size, and arrangement of steps without exceeding the scope of the disclosure. This may include, to the extent that it is appropriate, the use of any of the features of one example embodiment being used in other embodiments.

Claims
  • 1. A method of operating a building controller that is configured to control one or more building systems in combination with a smartphone that has location services and a user interface, the method comprising: storing a time-based HOME schedule including two or more time periods, the two or more time periods including at least a first time period with a first HOME setting and a second time period with a second HOME setting;identifying via the building controller whether the smartphone is inside a geofence or outside the geofence;in response to identifying that the smartphone is outside the geofence, controlling via the building controller at least one building system in accordance with an AWAY setting that over-rides at least part of the time-based HOME schedule; andin response to identifying that the smartphone is inside the geofence, controlling via the building controller the at least one building system in accordance with a current time in conjunction with the time-based HOME schedule, wherein controlling the at least one building system in accordance with the current time in conjunction with the time-based HOME schedule comprises: controlling the at least one building system with the first HOME setting when the current time is in the first time period and in response to identifying that the smartphone is inside the geofence; andcontrolling the at least one building system with the second HOME setting when the current time is in the second time period and in response to identifying that the smartphone is inside the geofence.
  • 2. The method of claim 1, further comprising programming the two or more time periods of the time-based HOME schedule via one or more screens that are displayed on the user interface of the smartphone.
  • 3. The method of claim 1, further comprising programming the HOME setting for each of the two or more time periods of the time-based HOME schedule via one or more screens that are displayed on the user interface of the smartphone.
  • 4. The method of claim 1, further comprising programming the AWAY setting via one or more screens that are displayed on the user interface of the smartphone.
  • 5. The method of claim 1, further comprising programming the geofence via one or more screens that are displayed on the user interface of the smartphone.
  • 6. The method of claim 1, wherein identifying whether the smartphone is inside the geofence or outside the geofence is based on an indication of a geofence crossing received from the smartphone.
  • 7. The method of claim 1, wherein identifying whether the smartphone is inside the geofence or outside the geofence is determined by the smartphone and communicated to a server.
  • 8. The method of claim 7, further comprising: receiving, by the building controller from the server, an indication of whether the smartphone is identified to be inside the geofence or outside the geofence.
  • 9. The method of claim 7, further comprising: controlling the at least one building system in accordance with the AWAY setting in response to receiving, by the building controller from the server, an indication that the smartphone is outside the geofence by the server; andcontrolling the at least one building system in accordance with the current time in conjunction with the time-based HOME schedule in response to receiving, by the building controller from the server, an indication that the smartphone is inside the geofence by the server.
  • 10. The method of claim 1, wherein the at least one building system comprises a security system, a lighting system, and/or an HVAC system.
  • 11. The method of claim 1, wherein: the AWAY setting comprises a temperature setpoint that represents an energy-savings temperature setting;the first HOME setting of the first time period comprises a temperature setpoint that represents a first comfort temperature setting; andthe second HOME setting of the second time period comprises a temperature setpoint that represents a second comfort temperature setting that is different from the first comfort temperature setting.
  • 12. The method of claim 11, wherein the first time period corresponds to a portion of a day in which the user of the smartphone is expected to be awake.
  • 13. The method of claim 12, wherein the second time period corresponds to a portion of a day in which the user of the smartphone is expected to be asleep.
  • 14. A method of operating an HVAC controller that is configured to control one or more HVAC components of a building in combination with a smartphone that has location services, the HVAC controller utilizing an AWAY setting and a time-based HOME schedule in controlling the one or more HVAC components of the building, the method comprising: identifying via the HVAC controller whether the smartphone is inside a geofence or outside the geofence;in response to identifying that the smartphone is outside the geofence, controlling via the HVAC controller at least one HVAC component of the building in accordance with the AWAY setting that over-rides at least part of the time-based HOME schedule by setting one or more HVAC parameters for use when the building is not occupied; andin response to identifying via the HVAC controller that the smartphone is inside the geofence, controlling via the HVAC controller the at least one HVAC component of the building in accordance with the time-based HOME schedule,wherein the time-based HOME schedule includes two or more time periods, the two or more time periods including at least a first time period with a first HOME setting for when the smartphone is identified to be inside the geofence and a second time period with a second HOME setting for when the smartphone is identified to be inside the geofence,wherein the first HOME setting for the first time period is different from the second HOME setting for the second time period.
  • 15. The method of claim 14, wherein: the AWAY setting comprises a temperature setpoint that represents an energy-savings temperature setting;the first HOME setting of the first time period comprises a temperature setpoint that represents a comfort temperature setting when the user is awake; andthe second HOME setting of the second time period comprises a temperature setpoint that represents a comfort temperature setting when the user is asleep.
  • 16. A method of operating a building controller that is configured to control one or more building systems in combination with a plurality of smartphones that each have location services, the method comprising: identifying via the building controller whether each of the plurality of smartphones is inside a corresponding geofence or outside the corresponding geofence;in response to identifying via the building controller that one or more of the plurality of smartphones are inside their corresponding geofence, controlling via the building controller the at least one building system in accordance with a time-based HOME schedule, wherein the time-based HOME schedule includes two or more time periods, the two or more time periods including at least a first time period with a first HOME setting and a second time period with a second HOME setting, wherein controlling the at least one building system in accordance with the time-based HOME schedule comprises: controlling the at least one building system with the first HOME setting when a current time is in the first time period and in response to identifying that the one or more of the plurality of smartphones are inside their corresponding geofence; andcontrolling the at least one building system with the second HOME setting when the current time is in the second time period and in response to identifying that the one or more of the plurality of smartphones are inside their corresponding geofence; andwhen all of the plurality of smartphones are identified to be outside their corresponding geofence, controlling via the building controller at least one of the one or more building systems in accordance with an AWAY setting that over-rides at least part of the time-based HOME schedule.
  • 17. The method of claim 16, wherein the plurality of smartphones have the same corresponding geofence.
  • 18. The method of claim 16, wherein: the AWAY setting comprises a temperature setpoint that represents an energy-savings temperature setting;the first HOME setting of the first time period comprises a temperature setpoint that represents a comfort temperature setting when the users are awake; andthe second HOME setting of the second time period comprises a temperature setpoint that represents a second comfort temperature setting when the users are asleep.
  • 19. The method of claim 18, wherein the first time period of the two or more time periods corresponds to a portion of a day in which at least some of the users of the plurality of smartphones are expected to be awake, and the second time period of the two or more time periods corresponds to a portion of the day in which all of the users of the plurality of smartphones are expected to be asleep.
US Referenced Citations (856)
Number Name Date Kind
1522169 Young Jan 1925 A
2227549 McNeill Jan 1941 A
2462162 Christensen et al. Feb 1949 A
2839670 Gladstone Jun 1958 A
2854610 Waters et al. Sep 1958 A
2879363 Mucher Mar 1959 A
2961625 Sian Nov 1960 A
2980875 Sivacek Apr 1961 A
3087134 McOrlly Apr 1963 A
3147457 Gill et al. Sep 1964 A
3747045 Stross Jul 1973 A
3779079 Snook Dec 1973 A
3793604 Duggan et al. Feb 1974 A
3815074 Nagata Jun 1974 A
3818213 Rochford et al. Jun 1974 A
3832668 Berman Aug 1974 A
3868620 McBride, Jr. et al. Feb 1975 A
3884363 Ajlouny May 1975 A
4079366 Wong Mar 1978 A
4104976 Landau, Jr. et al. Aug 1978 A
4117257 Thomas Sep 1978 A
4174807 Smith et al. Nov 1979 A
4206872 Levine Jun 1980 A
4214353 Kalina Jul 1980 A
4216384 Hurley Aug 1980 A
4224615 Penz Sep 1980 A
4264034 Hyltin et al. Apr 1981 A
4276536 Wisnia Jun 1981 A
4296334 Wong Oct 1981 A
4298946 Hartsell et al. Nov 1981 A
4308991 Peinetti et al. Jan 1982 A
4317102 Vranas Feb 1982 A
4332352 Jaeger Jun 1982 A
4333069 Worth et al. Jun 1982 A
4337822 Hyltin et al. Jul 1982 A
4337893 Flanders et al. Jul 1982 A
4341345 Hammer et al. Jul 1982 A
4345162 Hammer et al. Aug 1982 A
4347443 Whitney Aug 1982 A
4373664 Barker et al. Feb 1983 A
4379483 Farley Apr 1983 A
4382544 Stewart May 1983 A
4386649 Hines et al. Jun 1983 A
4388692 Jones et al. Jun 1983 A
4431134 Hendricks et al. Feb 1984 A
4442972 Sahay et al. Apr 1984 A
4446913 Krocker May 1984 A
4479604 Didner Oct 1984 A
4498650 Smith et al. Feb 1985 A
4503471 Hanajima et al. Mar 1985 A
4506827 Jamieson et al. Mar 1985 A
4514787 Kaneko et al. Apr 1985 A
4556169 Zervos Dec 1985 A
4560973 Grimm et al. Dec 1985 A
4583182 Breddan Apr 1986 A
4585164 Butkovich et al. Apr 1986 A
4606401 Levine et al. Aug 1986 A
4621336 Brown Nov 1986 A
4622544 Bially et al. Nov 1986 A
4628201 Schmitt Dec 1986 A
4646964 Parker et al. Mar 1987 A
4685025 Carlomagno Aug 1987 A
4708558 Musil Nov 1987 A
4717333 Carignan Jan 1988 A
4725001 Carney et al. Feb 1988 A
4748552 Seino May 1988 A
4764766 Aoyama et al. Aug 1988 A
4797568 Gumbs Jan 1989 A
4808841 Ito et al. Feb 1989 A
4837731 Levine et al. Jun 1989 A
4839636 Zeiss Jun 1989 A
4881686 Mehta Nov 1989 A
4888726 Struger et al. Dec 1989 A
4899129 MacFadyen et al. Feb 1990 A
4912463 Li Mar 1990 A
4918439 Wozniak et al. Apr 1990 A
4941829 Estes et al. Jul 1990 A
4942613 Lynch Jul 1990 A
4948040 Kobayashi et al. Aug 1990 A
4969508 Tate et al. Nov 1990 A
4990987 Boucher et al. Feb 1991 A
4992779 Sugino et al. Feb 1991 A
4997029 Otsuka et al. Mar 1991 A
5005365 Lynch Apr 1991 A
5008775 Schindler et al. Apr 1991 A
5012973 Dick et al. May 1991 A
5036698 Conti Aug 1991 A
5038851 Meth Aug 1991 A
5043531 Gutenson et al. Aug 1991 A
5053752 Epstein et al. Oct 1991 A
5065813 Berkeley et al. Nov 1991 A
5086385 Launey et al. Feb 1992 A
5088645 Bell Feb 1992 A
5126686 Tam Jun 1992 A
5140310 DeLuca et al. Aug 1992 A
5149200 Shiokawa et al. Sep 1992 A
5161606 Berkeley et al. Nov 1992 A
5170935 Federspiel et al. Dec 1992 A
5172565 Wruck et al. Dec 1992 A
5181653 Foster et al. Jan 1993 A
5187655 Post et al. Feb 1993 A
5187797 Nielsen et al. Feb 1993 A
5213417 Yamada et al. May 1993 A
5218399 Izumi et al. Jun 1993 A
5218552 Stirk et al. Jun 1993 A
5226723 Chen Jul 1993 A
5230482 Ratz et al. Jul 1993 A
5237305 Ishikuro et al. Aug 1993 A
5238184 Adams Aug 1993 A
5239745 Hofsass Aug 1993 A
5251813 Kniepkamp Oct 1993 A
5259445 Pratt et al. Nov 1993 A
5270915 Tomita et al. Dec 1993 A
5271410 Wolzinger et al. Dec 1993 A
5272477 Tashima et al. Dec 1993 A
5289362 Liebl et al. Feb 1994 A
5291063 Adishian Mar 1994 A
5317304 Choi May 1994 A
5321382 Mizukoshi et al. Jun 1994 A
5329991 Metha et al. Jul 1994 A
5348078 Dushane et al. Sep 1994 A
5351035 Chrisco Sep 1994 A
5367282 Clem Nov 1994 A
5386577 Zenda Jan 1995 A
5390206 Rein et al. Feb 1995 A
5392223 Caci Feb 1995 A
5404934 Carlson et al. Apr 1995 A
5412291 Payne et al. May 1995 A
5414618 Mock et al. May 1995 A
5429649 Robin Jul 1995 A
5432938 Ohashi Jul 1995 A
5436609 Chan et al. Jul 1995 A
5442340 Dykema Aug 1995 A
5449234 Gipp et al. Sep 1995 A
5457478 Frank Oct 1995 A
5459374 Thoeny et al. Oct 1995 A
5479155 Zeinstra et al. Dec 1995 A
5482209 Cochran et al. Jan 1996 A
5495887 Kathnelson et al. Mar 1996 A
5506572 Hills et al. Apr 1996 A
5526422 Keen Jun 1996 A
5537106 Mitcuhashi Jul 1996 A
5539633 Hildebrand et al. Jul 1996 A
5544036 Brown, Jr. et al. Aug 1996 A
5565843 Meyvis Oct 1996 A
5566879 Longtin Oct 1996 A
5570085 Bertsch Oct 1996 A
5570837 Brown et al. Nov 1996 A
5572438 Ehlers et al. Nov 1996 A
5578797 Hewitt et al. Nov 1996 A
5590831 Manson et al. Jan 1997 A
5600311 Rice et al. Feb 1997 A
5603451 Helander et al. Feb 1997 A
5621662 Humphries et al. Apr 1997 A
5625968 Ashall May 1997 A
5654813 Whitworth Aug 1997 A
5668535 Hendiix et al. Sep 1997 A
5671083 Conner et al. Sep 1997 A
5673850 Uptegraph Oct 1997 A
5679137 Erdman et al. Oct 1997 A
5682206 Wehmeyer et al. Oct 1997 A
5684710 Ehlers et al. Nov 1997 A
5690277 Flood Nov 1997 A
5696695 Ehlers et al. Dec 1997 A
5711785 Maxwell Jan 1998 A
5722126 Reiter Mar 1998 A
5732691 Maiello et al. Mar 1998 A
5761083 Brown, Jr. et al. Jun 1998 A
5782296 Metha Jul 1998 A
5790977 Ezekiel Aug 1998 A
5810908 Gray et al. Sep 1998 A
5818428 Eisenbrandt et al. Oct 1998 A
5829862 Ferrell Nov 1998 A
5833134 Ho et al. Nov 1998 A
5838226 Houggy et al. Nov 1998 A
5838563 Dove et al. Nov 1998 A
5839654 Weber Nov 1998 A
5840094 Osendorf et al. Nov 1998 A
5842032 Bertsch Nov 1998 A
5862737 Chiu et al. Jan 1999 A
5873519 Beilfuss Feb 1999 A
5877957 Bennett Mar 1999 A
5884248 Hall Mar 1999 A
5886697 Naughton et al. Mar 1999 A
5901183 D' Souza May 1999 A
5902183 D' Souza May 1999 A
5903327 Hijii May 1999 A
5909429 Satyanarayana et al. Jun 1999 A
5915473 Ganesh et al. Jun 1999 A
5917141 Naquin, Jr. Jun 1999 A
5918292 Smith Jun 1999 A
5926776 Glorioso et al. Jul 1999 A
D413328 Kazama Aug 1999 S
5937942 Bias et al. Aug 1999 A
5938757 Bertsch Aug 1999 A
5940296 Meyer Aug 1999 A
5947372 Tiernan Sep 1999 A
5950709 Krueger et al. Sep 1999 A
5956025 Goulden et al. Sep 1999 A
5956487 Venkatraman et al. Sep 1999 A
5963446 Klein et al. Oct 1999 A
5963886 Candy et al. Oct 1999 A
5975737 Crater et al. Nov 1999 A
5982362 Crater et al. Nov 1999 A
6009355 Obradovich et al. Dec 1999 A
6013121 Chin et al. Jan 2000 A
6020881 Naughton et al. Feb 2000 A
6032208 Nixon et al. Feb 2000 A
6032867 Dushane et al. Mar 2000 A
D422594 Henderson et al. Apr 2000 S
6059195 Adams et al. May 2000 A
6061603 Papadopoulos et al. May 2000 A
6067477 Wewalaarachchi et al. May 2000 A
6081197 Garrick et al. Jun 2000 A
6084523 Gelnovatch et al. Jul 2000 A
6098116 Nixon et al. Aug 2000 A
6098893 Berglund et al. Aug 2000 A
6101824 Meyer et al. Aug 2000 A
6104399 Volkel Aug 2000 A
6104963 Cebasek et al. Aug 2000 A
6107669 Mokuya et al. Aug 2000 A
6112127 Bennett Aug 2000 A
6119125 Gloudeman et al. Sep 2000 A
6121875 Hamm et al. Sep 2000 A
6122603 Budike, Jr. Sep 2000 A
6134771 Nakamura et al. Oct 2000 A
6139177 Venkatraman et al. Oct 2000 A
6140987 Stein et al. Oct 2000 A
6141595 Gloudeman et al. Oct 2000 A
6145751 Ahmed et al. Nov 2000 A
6147868 Boutillier et al. Nov 2000 A
6149065 White et al. Nov 2000 A
6152375 Robison Nov 2000 A
6154128 Wookey et al. Nov 2000 A
6154681 Drees et al. Nov 2000 A
6157943 Meyer Dec 2000 A
6167316 Gloudeman et al. Dec 2000 A
6190442 Redner Feb 2001 B1
6192282 Smith et al. Feb 2001 B1
6196467 Dushane et al. Mar 2001 B1
6208331 Singh et al. Mar 2001 B1
6211626 Lys et al. Apr 2001 B1
6211782 Sandelman et al. Apr 2001 B1
6216956 Ehlers et al. Apr 2001 B1
6236326 Murphy May 2001 B1
6236443 Carlsen May 2001 B1
6255988 Bischoff Jul 2001 B1
6259074 Brunner et al. Jul 2001 B1
6260765 Natale et al. Jul 2001 B1
6282454 Papadopoulos et al. Aug 2001 B1
6285912 Ellison et al. Sep 2001 B1
6290140 Pesko et al. Sep 2001 B1
D448757 Okubo Oct 2001 S
6311105 Budike, Jr. Oct 2001 B1
6315211 Sartain et al. Nov 2001 B1
6318639 Toth Nov 2001 B1
6321637 Shanks et al. Nov 2001 B1
6330806 Beaverson et al. Dec 2001 B1
6334107 Gale et al. Dec 2001 B1
6350039 Lee Feb 2002 B1
6351693 Monie et al. Feb 2002 B1
6344861 Naughton et al. Mar 2002 B1
6353853 Gravlin Mar 2002 B1
6356282 Roytman et al. Mar 2002 B2
6366198 Allen et al. Apr 2002 B1
6385495 Bennett May 2002 B1
6385510 Hoog et al. May 2002 B1
6394359 Morgan May 2002 B1
6398118 Rosen et al. Jun 2002 B1
6400956 Richton Jun 2002 B1
6405099 Nagai et al. Jun 2002 B1
6448896 Bankus et al. Sep 2002 B1
6449726 Smith Sep 2002 B1
6453687 Sharood et al. Sep 2002 B2
D464948 Vasquez et al. Oct 2002 S
6460774 Sumida et al. Oct 2002 B2
6462654 Sandelman et al. Oct 2002 B1
6466132 Caronna et al. Oct 2002 B1
6478233 Shah Nov 2002 B1
6484061 Papadopoulos et al. Nov 2002 B2
6486874 Muthuswamy et al. Nov 2002 B1
6496168 Tomida Dec 2002 B1
6502758 Cottrell Jan 2003 B2
6507282 Sherwood Jan 2003 B1
6508171 Georges Jan 2003 B1
6518953 Armstrong Feb 2003 B1
6518957 Lehtinen et al. Feb 2003 B1
6519509 Nierlich et al. Feb 2003 B1
6529137 Roe Mar 2003 B1
6546419 Humpleman et al. Apr 2003 B1
6556899 Harvey et al. Apr 2003 B1
6574537 Kipersztok et al. Jun 2003 B2
6574581 Bohrer et al. Jun 2003 B1
6578770 Rosen Jun 2003 B1
6580950 Johnson et al. Jun 2003 B1
6581846 Rosen Jun 2003 B1
6588931 Betzner et al. Jul 2003 B2
6595430 Shah Jul 2003 B1
6596059 Greist et al. Jul 2003 B1
6597151 Price et al. Jul 2003 B1
6598056 Hull et al. Jul 2003 B1
D478051 Sagawa Aug 2003 S
6604023 Brown et al. Aug 2003 B1
6608560 Abrams Aug 2003 B2
6619555 Rosen Sep 2003 B2
6621507 Shah Sep 2003 B1
6639614 Kosslyn et al. Oct 2003 B1
6640141 Bennett Oct 2003 B2
6640145 Hoffberg et al. Oct 2003 B2
6643567 Kolk et al. Nov 2003 B2
6650322 Dai et al. Nov 2003 B2
6663010 Chene et al. Dec 2003 B2
6665613 Duvall Dec 2003 B2
6671586 Davis et al. Dec 2003 B2
6675193 Slavin et al. Jan 2004 B1
6685098 Okano et al. Feb 2004 B2
6717513 Sandelman et al. Apr 2004 B1
6721607 Brault Apr 2004 B2
6726112 Ho Apr 2004 B1
D492282 Lachello et al. Jun 2004 S
6681154 Nierlich et al. Jun 2004 B2
6756998 Bilger Jun 2004 B1
6783079 Carey et al. Aug 2004 B2
6786421 Rosen Sep 2004 B2
6789739 Rosen Sep 2004 B2
6801849 Szukala et al. Oct 2004 B2
6810307 Addy Oct 2004 B1
6810397 Oian et al. Oct 2004 B1
6824069 Rosen Nov 2004 B2
6833990 LaCroix et al. Dec 2004 B2
6842650 Bennett Jan 2005 B2
6842721 Kim et al. Jan 2005 B2
6851621 Wacker et al. Feb 2005 B1
6862498 Davis et al. Mar 2005 B2
6868293 Schurr et al. Mar 2005 B1
6868538 Nixon et al. Mar 2005 B1
6904385 Budike, Jr. Jun 2005 B1
6909891 Yamashita et al. Jun 2005 B2
6912429 Bilger Jun 2005 B1
6917373 Vong et al. Jul 2005 B2
6931445 Davis Aug 2005 B2
6961763 Wang et al. Nov 2005 B1
D512208 Kubo et al. Dec 2005 S
6973410 Seigel Dec 2005 B2
6975958 Bohrer et al. Dec 2005 B2
6988070 Kawasaki et al. Jan 2006 B2
6988671 Deluca Jan 2006 B2
6990335 Shamoon et al. Jan 2006 B1
7000849 Ashworth et al. Feb 2006 B2
7001495 Essalik et al. Feb 2006 B2
7009493 Howard et al. Mar 2006 B2
7010363 Donnelly et al. Mar 2006 B2
7027878 Bennett Apr 2006 B2
7028912 Rosen Apr 2006 B1
D520989 Miller May 2006 S
7050026 Rosen May 2006 B1
7055759 Wacker et al. Jun 2006 B2
7080358 Kuzmin Jul 2006 B2
7080941 Benjamin et al. Jul 2006 B1
7083109 Pouchak Aug 2006 B2
7083189 Ogata Aug 2006 B2
7089088 Terry et al. Aug 2006 B2
7108194 Hankins, II Sep 2006 B1
7127734 Amit Oct 2006 B1
7130719 Ehlers et al. Oct 2006 B2
7130720 Fisher Oct 2006 B2
D531588 Peh Nov 2006 S
D533515 Klein et al. Dec 2006 S
7146253 Hoog et al. Dec 2006 B2
7152058 Shotton et al. Dec 2006 B2
7152806 Rosen Dec 2006 B1
7155305 Hayes et al. Dec 2006 B2
D535573 Barton et al. Jan 2007 S
7156318 Rosen Jan 2007 B1
7159789 Schwendinger et al. Jan 2007 B2
7163156 Kates Jan 2007 B2
7184861 Petite Feb 2007 B2
7188002 Chapman, Jr. et al. Mar 2007 B2
7193498 Kawamoto et al. Mar 2007 B2
D542236 Klein et al. May 2007 S
7212887 Shah et al. May 2007 B2
7221984 Bennett May 2007 B2
7222800 Wruck May 2007 B2
7225054 Amundson et al. May 2007 B2
7231605 Ramakesavan Jun 2007 B1
7232075 Rosen Jun 2007 B1
7240289 Naughton et al. Jul 2007 B2
7257397 Shamoon et al. Aug 2007 B2
7261762 Kang et al. Aug 2007 B2
7266777 Scott et al. Sep 2007 B2
7272403 Creamer et al. Sep 2007 B2
7274973 Nichols et al. Sep 2007 B2
7279659 Gagas et al. Oct 2007 B2
7298833 Klein et al. Nov 2007 B2
7302642 Smith et al. Nov 2007 B2
7327250 Harvey Feb 2008 B2
7331187 Kates Feb 2008 B2
7333460 Vaisanen et al. Feb 2008 B2
7341201 Stanimirovic Mar 2008 B2
7343226 Ehlers et al. Mar 2008 B2
7354005 Carey et al. Apr 2008 B2
7364093 Garozzo Apr 2008 B2
7374327 Schexnaider May 2008 B2
7385500 Irwin Jun 2008 B2
RE40437 Rosen Jul 2008 E
7403838 Deen et al. Jul 2008 B2
7406353 Bennett Jul 2008 B2
7411489 Elwell et al. Aug 2008 B1
7416332 Rountree et al. Aug 2008 B2
7419532 Sellers et al. Sep 2008 B2
7434742 Mueller et al. Oct 2008 B2
7435278 Terlson Oct 2008 B2
D580801 Takach et al. Nov 2008 S
7451017 McNally Nov 2008 B2
7451606 Harrod Nov 2008 B2
7452396 Terlson et al. Nov 2008 B2
7454269 Dushane et al. Nov 2008 B1
7469151 Khan et al. Dec 2008 B2
7496627 Moorer et al. Feb 2009 B2
7500780 Miki et al. Mar 2009 B2
7505914 McCall Mar 2009 B2
7510126 Rossi et al. Mar 2009 B2
7542867 Steger et al. Jun 2009 B2
7551071 Bennett, III et al. Jun 2009 B2
7556207 Mueller et al. Jul 2009 B2
7565225 Dushane et al. Jul 2009 B2
7571865 Nicodem et al. Aug 2009 B2
7574208 Hanson et al. Aug 2009 B2
7578135 Mattheis Aug 2009 B2
7594960 Johansson Sep 2009 B2
7604046 Bergman et al. Oct 2009 B2
7614567 Chapman et al. Nov 2009 B2
7617691 Street et al. Nov 2009 B2
7636604 Bergman et al. Dec 2009 B2
7644591 Singh et al. Jan 2010 B2
7665019 Jaeger Feb 2010 B2
7668532 Shamoon et al. Feb 2010 B2
7676282 Bosley Mar 2010 B2
7703694 Mueller et al. Apr 2010 B2
7707189 Haselden et al. Apr 2010 B2
7713339 Johansson May 2010 B2
7739282 Smith et al. Jun 2010 B1
7768393 Nigam Aug 2010 B2
7770242 Sell Aug 2010 B2
7778734 Oswald et al. Aug 2010 B2
7793056 Boggs et al. Sep 2010 B2
7801646 Amundson et al. Sep 2010 B2
7812274 Dupont et al. Oct 2010 B2
7814516 Stecyk et al. Oct 2010 B2
7827495 Bells et al. Nov 2010 B2
7865252 Clayton Jan 2011 B2
7904209 Podgomy et al. Mar 2011 B2
7908211 Chen et al. Mar 2011 B1
7940907 Bennett, III et al. May 2011 B2
7941431 Bluhm et al. May 2011 B2
7949615 Ehlers et al. May 2011 B2
7953518 Kansal et al. May 2011 B2
7954726 Siddaramanna et al. Jun 2011 B2
7963454 Sullivan et al. Jun 2011 B2
7973678 Petricoin, Jr. et al. Jul 2011 B2
7984220 Gerard et al. Jul 2011 B2
8010237 Cheung et al. Aug 2011 B2
8018329 Morgan et al. Sep 2011 B2
8019567 Steinberg et al. Sep 2011 B2
8024073 Imes et al. Sep 2011 B2
8032254 Amundson et al. Oct 2011 B2
8063775 Reed et al. Nov 2011 B2
8064935 Shamoon et al. Nov 2011 B2
8065342 Borg et al. Nov 2011 B1
8087593 Leen Jan 2012 B2
8091794 Siddaramanna et al. Jan 2012 B2
8091796 Amundson et al. Jan 2012 B2
8095340 Brown Jan 2012 B2
8099195 Imes et al. Jan 2012 B2
8108076 Imes et al. Jan 2012 B2
8115656 Bevacqua et al. Feb 2012 B2
8125332 Curran et al. Feb 2012 B2
8126685 Nasle Feb 2012 B2
8126999 Bahl et al. Feb 2012 B2
8131401 Nasle Mar 2012 B2
8131506 Steinberg et al. Mar 2012 B2
8135413 Dupray Mar 2012 B2
8140279 Subbloie Mar 2012 B2
8150421 Ward Apr 2012 B2
8151234 Berkens et al. Apr 2012 B2
8167216 Schultz et al. May 2012 B2
8180492 Steinberg May 2012 B2
8195309 Hegde et al. Jun 2012 B2
8195313 Fadell et al. Jun 2012 B1
8196064 Krzyzanowski et al. Jun 2012 B2
8199113 Madonna et al. Jun 2012 B2
8202161 Leake et al. Jun 2012 B2
8205244 Nightingale et al. Jun 2012 B2
8206032 Wakabayashi Jun 2012 B2
8219219 Bennett Jul 2012 B2
8229722 Nasle Jul 2012 B2
8232877 Husain Jul 2012 B2
8239066 Jennings et al. Aug 2012 B2
8246246 Wakabayashi Aug 2012 B2
8255090 Frader-Thompson et al. Aug 2012 B2
8258654 Parsons Sep 2012 B2
8269620 Bullemer et al. Sep 2012 B2
8280536 Fadell et al. Oct 2012 B1
8301123 Roundtree et al. Oct 2012 B2
8301765 Goodman Oct 2012 B2
8332055 Veillette Dec 2012 B2
8334906 Lipton et al. Dec 2012 B2
8337081 Holmberg et al. Dec 2012 B1
8350697 Trundle et al. Jan 2013 B2
8386082 Oswald Feb 2013 B2
8390473 Kryzanowski et al. Mar 2013 B2
8396455 Carlson et al. Mar 2013 B2
8397411 Russo et al. Mar 2013 B2
8406162 Haupt et al. Mar 2013 B2
8412381 Nikovski et al. Apr 2013 B2
8412654 Montovo Apr 2013 B2
8423322 Steinberg et al. Apr 2013 B2
8427278 Petricoin, Jr. Apr 2013 B2
8428867 Ashley, Jr. et al. Apr 2013 B2
8429188 Aravamudan et al. Apr 2013 B2
8433344 Virga Apr 2013 B1
8442695 Imes et al. May 2013 B2
8457797 Imes et al. Jun 2013 B2
8491159 Recker et al. Jul 2013 B2
8509954 Imes et al. Aug 2013 B2
8510421 Matsuzaki et al. Aug 2013 B2
8523084 Siddaramanna et al. Sep 2013 B2
8531294 Slavin et al. Sep 2013 B2
8554374 Lunacek et al. Oct 2013 B2
8554714 Raymond et al. Oct 2013 B2
8571518 Imes et al. Oct 2013 B2
8577392 Raghunandan et al. Nov 2013 B1
8583566 Aravamudan et al. Nov 2013 B2
8587445 Rockwell Nov 2013 B2
8626344 Imes et al. Jan 2014 B2
8630741 Matsuoka et al. Jan 2014 B1
8634796 Johnson Jan 2014 B2
8648706 Ranjun et al. Feb 2014 B2
8659302 Warren et al. Feb 2014 B1
8666558 Wang et al. Mar 2014 B2
8670783 Klein Mar 2014 B2
8686841 Macheca et al. Apr 2014 B2
8798804 Besore et al. Aug 2014 B2
8810454 Cosman Aug 2014 B2
8812024 Obermeyer et al. Aug 2014 B2
8812027 Obermeyer et al. Aug 2014 B2
8829799 Recker et al. Sep 2014 B2
8840033 Steinberg Sep 2014 B2
8874129 Forutanpour et al. Oct 2014 B2
8886178 Chatterjee Nov 2014 B2
8890675 Ranjan et al. Nov 2014 B2
8909256 Fraccaroli Dec 2014 B2
8918219 Sloo et al. Dec 2014 B2
8941489 Sheshadri et al. Jan 2015 B2
8949231 Aravamudan et al. Feb 2015 B2
8965401 Sheshadri et al. Feb 2015 B2
8965406 Henderson Feb 2015 B2
8976025 Somasundaram et al. Mar 2015 B2
9019111 Sloo et al. Apr 2015 B1
9026261 Bukhin et al. May 2015 B2
9033255 Tessier et al. May 2015 B2
9055475 Lacatus et al. Jun 2015 B2
9065928 Huang et al. Jun 2015 B2
9071453 Shoemaker et al. Jun 2015 B2
9113298 Qiu Aug 2015 B2
9115656 Kosaka et al. Aug 2015 B2
9134715 Geadelmann et al. Sep 2015 B2
9167381 McDonald et al. Oct 2015 B2
9168927 Louboutin Oct 2015 B2
9183530 Schwarz et al. Nov 2015 B2
9210545 Sabatelli et al. Dec 2015 B2
9215560 Jernigan Dec 2015 B1
9219983 Sheshadri et al. Dec 2015 B2
9247378 Bisson et al. Jan 2016 B2
9288620 Menendez Mar 2016 B2
9307344 Rucker et al. Apr 2016 B2
9311685 Harkey et al. Apr 2016 B2
9313320 Zeilingold et al. Apr 2016 B2
9316456 Oliver Apr 2016 B1
9363772 Burks Jun 2016 B2
9414422 Belghoul et al. Aug 2016 B2
9433681 Constien et al. Sep 2016 B2
9449491 Sager et al. Sep 2016 B2
9587848 Adamik et al. Mar 2017 B2
9709295 Adamik et al. Jul 2017 B2
10177930 Bodkin Jan 2019 B1
20010010032 Ehlers et al. Jul 2001 A1
20010025349 Sharood et al. Sep 2001 A1
20010029585 Simon et al. Oct 2001 A1
20010038999 Hainey, II Nov 2001 A1
20010042684 Essalik et al. Nov 2001 A1
20010052459 Essalik et al. Dec 2001 A1
20020005435 Cottrell Jan 2002 A1
20020011923 Cunningham et al. Jan 2002 A1
20020022991 Sharood et al. Feb 2002 A1
20020033753 Imbo Mar 2002 A1
20020060701 Naughton et al. May 2002 A1
20020073254 Bertsch Jun 2002 A1
20020082746 Schubring et al. Jun 2002 A1
20020092779 Essalik et al. Jul 2002 A1
20020096572 Chene et al. Jul 2002 A1
20020138184 Kipersztok et al. Sep 2002 A1
20020147006 Coon et al. Oct 2002 A1
20020171624 Stecyk et al. Nov 2002 A1
20020173929 Seigel Nov 2002 A1
20030000692 Takaski et al. Jan 2003 A1
20030014179 Szukala et al. Jan 2003 A1
20030033156 McCall Feb 2003 A1
20030033230 McCall Feb 2003 A1
20030034897 Shamoon et al. Feb 2003 A1
20030034898 Shamoon et al. Feb 2003 A1
20030070544 Mulvaney et al. Apr 2003 A1
20030074088 Gonzales et al. Apr 2003 A1
20030074489 Steger et al. Apr 2003 A1
20030079387 Derose May 2003 A1
20030103075 Rosselot Jun 2003 A1
20030121652 Carey et al. Jul 2003 A1
20030123224 LaCroix et al. Jul 2003 A1
20030136135 Kim et al. Jul 2003 A1
20030142121 Rosen Jul 2003 A1
20030150926 Rosen Aug 2003 A1
20030150927 Rosen Aug 2003 A1
20030177012 Drennen Sep 2003 A1
20030178070 Glicken Sep 2003 A1
20040034484 Solomita Feb 2004 A1
20040193324 Hoog et al. Mar 2004 A1
20040074978 Rosen Apr 2004 A1
20040133314 Ehlers et al. Jul 2004 A1
20040245352 Smith Dec 2004 A1
20040262410 Hull Dec 2004 A1
20050083168 Beitenbach Apr 2005 A1
20050090915 Geiwitz Apr 2005 A1
20050096753 Arling et al. May 2005 A1
20050162282 Dresti et al. Jul 2005 A1
20050172056 Ahn Aug 2005 A1
20050194456 Tessier et al. Sep 2005 A1
20050219860 Schexnaider Oct 2005 A1
20050270151 Winick Dec 2005 A1
20060000919 Schwendinger et al. Jan 2006 A1
20060032379 Kates Feb 2006 A1
20060049694 Kates Mar 2006 A1
20060063522 McFarland Mar 2006 A1
20060071086 Kates Apr 2006 A1
20060072726 Klein et al. Apr 2006 A1
20060097063 Zeevi May 2006 A1
20060103549 Hunt et al. May 2006 A1
20060132458 Garfio et al. Jun 2006 A1
20060168342 Budde et al. Jul 2006 A1
20060186213 Carey et al. Aug 2006 A1
20060196953 Simon et al. Sep 2006 A1
20060219799 Schultz et al. Oct 2006 A1
20060242591 Van Dok et al. Oct 2006 A1
20060250578 Pohl et al. Nov 2006 A1
20060271214 Brown Nov 2006 A1
20060283697 Garfio Dec 2006 A1
20070013534 DiMaggio Jan 2007 A1
20070029397 Mueller et al. Feb 2007 A1
20070037605 Logan Feb 2007 A1
20070043477 Ehlers et al. Feb 2007 A1
20070043478 Ehlers Feb 2007 A1
20070045429 Chapman, Jr. et al. Mar 2007 A1
20070045431 Chapman, Jr. et al. Mar 2007 A1
20070060171 Sudit et al. Mar 2007 A1
20070061050 Hoffknecht Mar 2007 A1
20070099626 Lawrence et al. May 2007 A1
20070114293 Gugenheim May 2007 A1
20070114295 Jenkins May 2007 A1
20070121334 Bourdin et al. May 2007 A1
20070122789 Yoo May 2007 A1
20070129083 Creamer et al. Jun 2007 A1
20070146126 Wang Jun 2007 A1
20070138496 Zhao et al. Jul 2007 A1
20070225866 Moorer et al. Sep 2007 A1
20070233323 Wiemeyer et al. Oct 2007 A1
20070249319 Faulkner et al. Oct 2007 A1
20070250189 Rourke et al. Oct 2007 A1
20070277061 Ashe Nov 2007 A1
20070278320 Lunacek et al. Dec 2007 A1
20070289731 Deligiannis et al. Dec 2007 A1
20080015740 Osann, Jr. Jan 2008 A1
20080083234 Krebs et al. Apr 2008 A1
20080093460 Frantz et al. Apr 2008 A1
20080094230 Mock et al. Apr 2008 A1
20080120578 Wang et al. May 2008 A1
20080219319 Buckalew Sep 2008 A1
20080262820 Nasle Oct 2008 A1
20080281472 Podgorny et al. Nov 2008 A1
20080283621 Quirino et al. Nov 2008 A1
20090012704 Franco Jan 2009 A1
20090020307 Roach, Jr. Jan 2009 A1
20090052859 Greenberger et al. Feb 2009 A1
20090065596 Seem Mar 2009 A1
20090093234 Cai et al. Apr 2009 A1
20090140056 Leen Jun 2009 A1
20090140060 Stoner et al. Jun 2009 A1
20090140062 Amundson et al. Jun 2009 A1
20090143879 Amundsom et al. Jun 2009 A1
20090143880 Amundson et al. Jun 2009 A1
20090143916 Boll et al. Jun 2009 A1
20090143918 Amundson et al. Jun 2009 A1
20090165644 Campbell Jul 2009 A1
20090187499 Mulder et al. Jul 2009 A1
20090199212 Schneider Aug 2009 A1
20090240381 Lane Sep 2009 A1
20090302994 Rhee et al. Dec 2009 A1
20100008422 Shimizu et al. Jan 2010 A1
20100014277 Delany Jan 2010 A1
20100212198 Matsunaga et al. Jan 2010 A1
20100216465 Mubarek et al. Jan 2010 A1
20100026479 Tran Feb 2010 A1
20100034386 Choong et al. Feb 2010 A1
20100042940 Monday et al. Feb 2010 A1
20100081375 Rosenblatt et al. Apr 2010 A1
20100084482 Kennedy et al. Apr 2010 A1
20100107112 Jennings et al. Apr 2010 A1
20100127854 Helvick et al. May 2010 A1
20100131880 Lee et al. May 2010 A1
20100146071 Comerford et al. Jun 2010 A1
20100156628 Ainsbury et al. Jun 2010 A1
20100161574 Davidson et al. Jun 2010 A1
20100161706 Kim et al. Jun 2010 A1
20100179991 Lorch et al. Jul 2010 A1
20100197238 Pathuri et al. Aug 2010 A1
20100204834 Comerford et al. Aug 2010 A1
20100256823 Cherukuri et al. Oct 2010 A1
20100261465 Rhoads et al. Oct 2010 A1
20100280667 Steinberg Nov 2010 A1
20100289644 Slavin et al. Nov 2010 A1
20100304730 Huang et al. Dec 2010 A1
20110012433 Parsons Jan 2011 A1
20110015797 Gilstrap Jan 2011 A1
20110061527 Sullivan Mar 2011 A1
20110078515 Yasukawa Mar 2011 A1
20110093424 Zimmermann et al. Apr 2011 A1
20110153525 Benco et al. Jun 2011 A1
20110190910 Lombard et al. Aug 2011 A1
20110202185 Imes Aug 2011 A1
20110210862 Cumeralto et al. Sep 2011 A1
20110225859 Safavi Sep 2011 A1
20110231020 Ramachandran et al. Sep 2011 A1
20110256881 Huang Oct 2011 A1
20110271185 Chen et al. Nov 2011 A1
20110290893 Steinberg Dec 2011 A1
20110306304 Forutanpour et al. Dec 2011 A1
20120005590 Lombard et al. Jan 2012 A1
20120053739 Brian et al. Mar 2012 A1
20120065783 Fadell et al. Mar 2012 A1
20120066168 Fadell et al. Mar 2012 A1
20120078425 Gardenswartz Mar 2012 A1
20120086578 Moss et al. Apr 2012 A1
20120095749 Capretta Apr 2012 A1
20120130547 Fadell et al. May 2012 A1
20120131504 Fadell et al. May 2012 A1
20120172027 Partheesh et al. Jul 2012 A1
20120191257 Corcoran et al. Jul 2012 A1
20120209730 Garrett Aug 2012 A1
20120239221 Mighdoll et al. Sep 2012 A1
20120247187 Herz Oct 2012 A1
20120259466 Ray et al. Oct 2012 A1
20120284769 Dixon et al. Nov 2012 A1
20120307298 Ishige et al. Dec 2012 A1
20120318073 Zavodny et al. Dec 2012 A1
20120318135 Hoglund et al. Dec 2012 A1
20120318137 Ragland et al. Dec 2012 A1
20120318138 Bisson et al. Dec 2012 A1
20120319851 Hoglund et al. Dec 2012 A1
20120323374 Dean-Hendricks et al. Dec 2012 A1
20120323375 Dean-Hendricks et al. Dec 2012 A1
20120323377 Hoglund et al. Dec 2012 A1
20130024799 Fadell et al. Jan 2013 A1
20130027412 Roddy Jan 2013 A1
20130045760 Obermeyer et al. Feb 2013 A1
20130054863 Imes et al. Feb 2013 A1
20130061085 Raja Rao Mar 2013 A1
20130073094 Knapton et al. Mar 2013 A1
20130090767 Bruck et al. Apr 2013 A1
20130099009 Filson et al. Apr 2013 A1
20130099010 Filson et al. Apr 2013 A1
20130158714 Barton et al. Jun 2013 A1
20130158715 Barton et al. Jun 2013 A1
20130158717 Zywicki et al. Jun 2013 A1
20130158718 Barton et al. Jun 2013 A1
20130158720 Zywicki et al. Jun 2013 A1
20130184874 Frader-Thompson et al. Jul 2013 A1
20130204441 Sloo et al. Aug 2013 A1
20130225196 James et al. Aug 2013 A1
20130227126 Imes et al. Aug 2013 A1
20130231137 Hugie et al. Sep 2013 A1
20130238142 Nichols et al. Sep 2013 A1
20130245838 Zywicki et al. Sep 2013 A1
20130246944 Pandiyan et al. Sep 2013 A1
20130261804 Casilli Oct 2013 A1
20130261807 Zywicki et al. Oct 2013 A1
20130278384 McDowell et al. Oct 2013 A1
20130297078 Kolavennu Nov 2013 A1
20130305164 Karunamuni et al. Nov 2013 A1
20130310053 Srivastava et al. Nov 2013 A1
20130318217 Imes et al. Nov 2013 A1
20130331087 Shoemaker et al. Dec 2013 A1
20130332000 Imes et al. Dec 2013 A1
20130332007 Louboutin Dec 2013 A1
20130340993 Siddaramanna et al. Dec 2013 A1
20130345882 Dushane et al. Dec 2013 A1
20140031989 Bergman et al. Jan 2014 A1
20140031991 Bergman et al. Jan 2014 A1
20140070919 Jackson et al. Mar 2014 A1
20140085092 Fadell et al. Mar 2014 A1
20140149434 Aravamudan et al. May 2014 A1
20140156087 Amundson Jun 2014 A1
20140164118 Polachi Jun 2014 A1
20140167961 Finlow-Bates Jun 2014 A1
20140172176 Deilmann et al. Jun 2014 A1
20140184406 Trundle et al. Jul 2014 A1
20140197960 Taylor, Jr. et al. Jul 2014 A1
20140200718 Tessier Jul 2014 A1
20140244048 Ramachandran et al. Aug 2014 A1
20140266635 Roth et al. Sep 2014 A1
20140277762 Drew Sep 2014 A1
20140302879 Kim et al. Oct 2014 A1
20140316581 Fadell et al. Oct 2014 A1
20140319232 Gourlay et al. Oct 2014 A1
20140325398 Van de bruggen et al. Oct 2014 A1
20140330435 Stoner et al. Nov 2014 A1
20140337123 Neurenberg et al. Nov 2014 A1
20140349672 Kern et al. Nov 2014 A1
20140370911 Gorgenyi et al. Dec 2014 A1
20150009878 Kim et al. Jan 2015 A1
20150058779 Bruck et al. Feb 2015 A1
20150065161 Ganesh Mar 2015 A1
20150094860 Finnerty et al. Apr 2015 A1
20150094865 Choi et al. Apr 2015 A1
20150096876 Mittleman et al. Apr 2015 A1
20150097682 Rossi et al. Apr 2015 A1
20150097686 Fadell et al. Apr 2015 A1
20150097688 Bruck et al. Apr 2015 A1
20150097689 Logue et al. Apr 2015 A1
20150122575 Park et al. May 2015 A1
20150128050 Cormican et al. May 2015 A1
20150140994 Partheesh et al. May 2015 A1
20150141045 Qiu et al. May 2015 A1
20150159895 Quam Jun 2015 A1
20150159901 Quam et al. Jun 2015 A1
20150159903 Marak et al. Jun 2015 A1
20150159904 Barton Jun 2015 A1
20150163631 Quam Jun 2015 A1
20150163945 Barton et al. Jun 2015 A1
20150169895 Gkoulalas-Divanis et al. Jun 2015 A1
20150186497 Patton et al. Jul 2015 A1
20150195100 Imes et al. Jul 2015 A1
20150237470 Mayor et al. Aug 2015 A1
20150271638 Menayas et al. Sep 2015 A1
20150301543 Janoso et al. Oct 2015 A1
20160007156 Chiou et al. Jan 2016 A1
20160057572 Bojorquez Alfaro et al. Feb 2016 A1
20160142872 Bojorquez Alfaro et al. Feb 2016 A1
20160223998 Nicholson et al. May 2016 A1
Foreign Referenced Citations (88)
Number Date Country
2015201441 Oct 2015 AU
1976532 Jun 2007 CN
101311459 Nov 2008 CN
102449990 May 2012 CN
102665166 Sep 2012 CN
101676698 Nov 2012 CN
102934467 Feb 2013 CN
101689327 May 2013 CN
203949733 Nov 2014 CN
103282754 May 2015 CN
2036829 Jan 1972 DE
2404758 Aug 1975 DE
2321715 Jan 1983 DE
3334117 Apr 1985 DE
3703465 Aug 1988 DE
69001779 Jan 1994 DE
0070414 Jan 1983 EP
0434926 Aug 1995 EP
0678204 Mar 2000 EP
0985994 Mar 2000 EP
1033641 Sep 2000 EP
1074009 Jul 2001 EP
1143232 Oct 2001 EP
0735516 Jun 2004 EP
1515289 Mar 2005 EP
2138919 Dec 2009 EP
2607802 Jun 2013 EP
2675195 Dec 2013 EP
2849153 Mar 2015 EP
2711230 Apr 1995 FR
1116364 Jun 1968 GB
2333494 Jul 1999 GB
53009910 Jan 1978 JP
59086812 May 1984 JP
60116154 Jun 1985 JP
60211321 Oct 1985 JP
61005269 Jan 1986 JP
02156125 Jun 1990 JP
03038617 Feb 1991 JP
03209704 Sep 1991 JP
H10-23565 Jan 1993 JP
05079933 Mar 1993 JP
06036904 Feb 1994 JP
08153601 Nov 1996 JP
09306317 Nov 1997 JP
H9-298780 Nov 1997 JP
11126727 May 1999 JP
3156750 Apr 2001 JP
2008004627 Oct 2008 JP
2009293353 Dec 2009 JP
2012013564 Jan 2012 JP
5113691 Jan 2013 JP
5234043 Jul 2013 JP
5274948 Aug 2013 JP
5407492 Feb 2014 JP
2006029736 Apr 2006 KR
2012000906 Sep 2012 MX
WO-8501851 Apr 1985 WO
WO-9621264 Jul 1996 WO
WO 9711448 Mar 1997 WO
WO 9739392 Oct 1997 WO
WO-9808179 Feb 1998 WO
WO-9853677 Dec 1998 WO
WO 0043870 Jul 2000 WO
WO 0057259 Sep 2000 WO
WO 0152515 Jul 2001 WO
WO 0179952 Oct 2001 WO
WO 0223744 Mar 2002 WO
WO 0227687 Apr 2002 WO
WO-03032103 Apr 2003 WO
WO-2006096854 Sep 2006 WO
WO 2009034720 Mar 2009 WO
WO 2009036764 Mar 2009 WO
WO 2009067251 May 2009 WO
WO 2010021700 Feb 2010 WO
WO 2011011404 Jan 2011 WO
2011149600 Dec 2011 WO
WO 2012000107 Jan 2012 WO
WO 2012068517 May 2012 WO
WO 2013170791 Nov 2013 WO
WO 2014016705 Jan 2014 WO
WO 2014047501 Mar 2014 WO
WO 2014144323 Sep 2014 WO
WO 2014197320 Dec 2014 WO
WO-2014200524 Dec 2014 WO
WO-2015047739 Apr 2015 WO
WO-2015089116 Jun 2015 WO
WO-2015164400 Oct 2015 WO
Non-Patent Literature Citations (246)
Entry
Makwana, Divyang, “How to open desktop websites on mobile [Android Guide]”, mobigyaan.com, Feb. 27, 2016 (accessed from <<https://www.mobigyaan.com/how-to-open-desktop-websites-on-mobile-android-guide>> on Jul. 21, 2018) (Year: 2016).
Turner, Michele, “Introducing Family Accounts and Home/Away Assist”, Nest blog, Mar. 10, 2016 (accessed from <<https://nest.com/blog/2016/03/10/introducing-family-accounts-and-home-away-assist/>> on Jan. 18, 2019). (Year: 2016).
The International Search Report and Written Opinion for PCT Application No. PCT/US2017/043376.
“Comfort™ Programmable Owner's Manual,” Carrier Touch-N-Go™, 60 pages, 2010. Catalog No. 0M-TCPHP-4CA, Replaces: OM-TCPHP-3CA.
“CorAccess Systems/in Home,” http://web.archive.org/web20011212084427/www.coraccess.com/home.html, 1 page, copyright 2001, printed Aug. 19, 2004.
“HAI Company Background,” http://www.homeauto.com/AboutHAI/abouthai_main.htm, 2 pages, printed Aug. 19, 2004.
“High-tech options take hold in new homes—Aug. 28, 200—Dallas Business Journal,” http://bizjournals.com/dallas/stories/2000/08/28/focus4, 3 pages, dated Aug. 28, 2000, printed Aug. 19, 2004.
“Home Toys Review—TouchLinc”, http://www.hometoys.com/htinews/aug99/reviews/touchlinc/touchlinc.htm, 3 pages, dated Aug. 1999, printed Aug. 20, 2004.
“HTI News Release,” http://www.hometoys.com/htinews/apr99/releases/ha101.htm, 3 pages, Apr. 1999.
“Mark of Excellence Award Finalist Announced,” http://64.233.167.104/search?{dot over (Q)}32 cache:ciOA2YtYaBIJ:www.hometoys.com/releases/mar. . . , 6 pages, Leopard Touchscreen on p. 2, dated prior to Mar. 4, 2000, printed Aug. 20, 2004.
“Product Review—Philips Pronto Remote Control,” http://hometheaterhifi.com/volume_6_2/philipsprontoremotecontrol.html, 5 pages, dated May 1999, printed Aug. 20, 2004.
“RC X10 Automation Forum: Control your Heating and Cooling System with Pronto(1/1),” http://www.remotecentral.com/cgi-bin/mboard/rc-x10/thread.cgi?12, 2 pages, dated Apr. 23, 1999, printed Aug. 20, 2004.
“RCS X10 Thermostat Plug-in for Home Seer Beta Version,” 25 pages, Downloaded Sep. 9, 2011.
“Spotlight on Integrated Systems,” Custom Builder, V8, N2, p. 66(6), Mar.-Apr. 1993.
“Vantage Expands Controls for Audio/Video, HVAC and Security,” http://www.hometoys.com/htinews/aug99/releases/vantage03.htm, 2 pages, dated Aug. 3, 1999, printed Aug. 20, 2004.
ADI, “Leopard User Manual,” 93 pages, 2001.
Adicon 2500, “The Automator,” 4 pages, Oct.-Dec. 2000.
ADT Security Services, “iCenter AdVanced User Interface 8142ADT,” Installation and Setup Guide, 4 pages, May 2001.
AED Electronics, Inc., “Presenting Climatouch the Most Innovative Thermostat in the World!,” 2 pages, prior to Nov. 30, 2007.
Alarm.com “Company Information,” 1 page, printed Apr. 24, 2012.
Alarm.com “Keep it cozy,” 1 page, printed Apr. 24, 2012.
Allure, “Our Technology,” Allure Energy Inc., 1 page, 2012.
Andrews et al., “Clicky: User-Centric Input for Active Spaces,” 17 pages, Aug. 2004.
Aprilaire Electronic Thermostats Models 8344, 8346, 8348, 8363, 8365, 8366 Operating Instructions, 8 pages, 2003.
Aube Technologies, Electronic Thermostat for Heating System Model TH135-01, 5 pages, Aug. 14, 2001.
Aube Technologies, TH140-28 Electronic Programmable Thermostat, Installation Instructions and User Guide, pp. 1-4, Jan. 22, 2004.
AutomatedBuildings.com Article—“Thin Client” Solutions, “Pressure, Air Flow, Temperature, Humidity & Valves,” Dwyer Instruments, Inc., 5 pages, printed Sep. 20, 2004.
Balaji et al., “Sentinel: Occupancy Based HVAC Actuation Using Existing WiFi Infrastructure Within Commercial Buildings,” SenSys '13, 14 pages, Nov. 11-15, 2015.
Blake et al., “Seng 310 Final Project Demo Program” Illustration, 3 pages, Apr. 6, 2001.
Blake et al., “Seng 310 Final Project” Report, 52 pages, Apr. 6, 2001.
Blister Pack Insert from a Ritetemp 8082 Touch Screen Thermostat Product, 2 pages, 2002.
Braeburn Model 3000 Owner's Manual, pp. 1-13, 2001.
Braeburn Model 5000 Owner's Manual, pp. 1-17, 2001.
BRK Electronics Maximum Protection Plus Ultimate Convenience Smoke Alarm, 24 pages, Sep. 2000.
BRK First Alert, User's Manual, Smoke and Fire Alarms, pp. 1-7, Nov. 2002.
Business Wire, “MicroTouch Specialty Products Group to Capitalize on Growing Market for Low-Cost Digital Matrix Touchscreens,” p. 1174 (2 pages), Jan. 6, 1999.
Cardio Manual, available at http://www.secant.ca/En/Documentation/Cardio2é-Manual.pdf, Cardio Home Automation Inc., 55 pages, printed Sep. 28, 2004.
Cardio, by Secant; http://www.hometoys.com/htinews/apr98/reviews/cardio.htm, “HTINews Review,” Feb. 1998, 5 pages, printed Sep. 14, 2004.
Carrier Microelectronic Programmable Thermostat Owner's Manual, pp. 1-24, May 1994.
Carrier TSTATCCRF01 Programmable Digital Thermostat, pp. 1-21, prior to Apr. 21, 2005.
Carrier, “Edge Performance Programmable Owner's Manual,” 64 pages, 2007.
Carrier, “Programmable Dual Fuel Thermostats,” Installation, Start-Up & Operating Instructions, pp. 1-12, Oct. 1998.
Carrier, “Programmable Thermostats,” Installation, Start-Up & Operating Instructions, pp. 1-16, Sep. 1998.
Carrier, “Standard Programmable Thermostat,” Homeowner's Manual, pp. 1-8 pages, 1998.
Carrier, “Thermidistat Control,” Installation, Start-Up, and Operating Instructions, pp. 1-12, Aug. 1999.
Castle, “Ready for Thermostat Wars?,” available at http://greentechadvocates.com/2012/03/08/ready-for-thermostat-wars/, 3 pages, May 8, 2012.
Climatouch, User Manual, Climatouch CT03TSB Thermostat, Climatouch CT03TSHB Thermostat with Humidity Control, Outdoor UHF Temperature Transmitter 217S31, 19 pages, Printed Sep. 15, 2004.
“Petition for Inter Partes Review of U.S. Pat. No. 8,571,518 Pursuant to 35 U.S.C. 311-319, 37 CFR 42,” Inventor Imes et al., dated Oct. 29, 2014.
International Search Report for Corresponding Application No. PCT/US2010/042589 dated Nov. 22, 2010.
U.S. Appl. No. 14/640,984, filed Mar. 6, 2015.
U.S. Appl. No. 14/668,800, filed Mar. 25, 2015.
U.S. Appl. No. 14/696,662, filed Apr. 27, 2015.
U.S. Appl. No. 14/696,725, filed Apr. 27, 2015.
U.S. Appl. No. 14/933,948, filed Nov. 5, 2015.
U.S. Appl. No. 14/934,543, filed Nov. 6, 2015.
U.S. Appl. No. 14/938,595, filed Nov. 11, 2015.
U.S. Appl. No. 14/938,642, filed Nov. 11, 2015.
U.S. Appl. No. 14/964,264, filed Dec. 9, 2015.
U.S. Appl. No. 14/964,349, filed Dec. 9, 2015.
U.S. Appl. No. 15/048,902, filed Feb. 19, 2016.
U.S. Appl. No. 61/179,224, filed May 18, 2009.
CorAccess, “Companion 6,” User Guide, pp. 1-20, Jun. 17, 2002.
Danfoss RT51/51RF & RT52/52RF User Instructions, 2 pages, Jun. 2004.
DeKoven et al., “Designing Collaboration in Consumer Products,” 2 pages, 2001.
DeKoven et al., “Measuring Task Models in Designing Intelligent Products,” 2 pages, Jan. 13-16, 2002.
DESA Heating Products, “Wireless Hand-Held Remote Control Sets Models (C) GHRCB and (C) GHRCTB, Operating Instructions,” 4 pages, May 2003.
Ditosti, “Alarm.com Cloud Service May Prove to be Smartest Thermostat to Date,” downloaded from http://www.alarm.com/about/media/MediaGeneric.aspx?cmid=41, 2 pages, printed Feb. 29, 2012.
Do, “Programmable Communicating Thermostats for Demand Response in California,” DR ETD Workshop, 26 pages, Jun. 11, 2007.
Domotique Secant Home Automation—Web Page, available at http://www.secant.ca/En/Company/Defaultasp, 1 page, printed Sep. 28, 2004.
Edina Realty, “Warranties,” 3 pages, prior to 2014.
“Emme Core User Guide,” Version 1.1, 47 pages, Jan. 2011.
Firex Smoke Alarm, Ionization Models AD, ADC Photoelectric Model Pad, 4 pages, prior to Apr. 21, 2005.
Fluke, “561 HVAC Pro” Infrared Thermometer User's Manual, 22 pages, Downloaded May 24, 2012.
Freudenthal et al., “Communicating Extensive Smart Home Functionality to Users of All Ages: the Design of a Mixed-Initiative Multimodal Thermostat-Interface,” pp. 34-39, Mar. 12-13, 2001.
Gentex Corporation, HD135, 135° Fixed Temperature Heat Detector AC Powered, 120V, 60Hz With Battery Backup, Installation Instructions—Owner's Information, pp. 1-5, Jun. 1, 1998.
Gentex Corporation, 9000 Series, Photoelectric Type Single Station/Multi-Station Smoke Alarms Ac Powered With Battery Backup, Installation Instructions—Owner's Information, pp. 9-1 to 9-6, Jan. 1, 1993.
Green, “PM's Thermostat Guide,” Popular Mechanics, pp. 155-158, Oct. 1985.
Gupta et al., “Adding GPS-Control to Traditional Thermostats: An Exploration of Potential Energy Savings and Design Challenges,” Pervasive, LNCS 5538, pp. 95-114, 2009.
Gupta, “A Persuasive GPS-Controlled Thermostat System,” Master's Thesis, Massachusetts Institute of Technology, 89 pages, Sep. 2008.
Guttman, “Autoconfiguration for IP Networking: Enabling Local Communication,” 6 pages, IEEE Internet Computing, Jun. 2011.
Harris et al., “Optimizing Memory Transactions,” Microsoft Research Harvard University, 12 pages, May 25, 2012.
Honeywell Brivis Deluxe Programmable Thermostat, pp. 1-20, 2002.
Honeywell Brivis T8602C Chronotherm IV Deluxe Programmable Thermostats, Installation Instructions, pp. 1-12, 2002.
Honeywell CT8602C Professional Fuel Saver Thermostat, pp. 1-6, 1995.
Honeywell Electronic Programmable Thermostat, Owner's Guide, pp. 1-20, 2003.
Honeywell Electronic Programmable Thermostats, Installation Instructions, pp. 1-8, 2003.
Honeywell News Release, “Honeywell's New Sysnet Facilities Integration System for Boiler Plant and Combustion Safety ProcesSes,” 4 pages, Dec. 15, 1995.
Honeywell T8002 Programmable Thermostat, Installation Instructions, pp. 1-8, 2002.
Honeywell T8602A,B,C,D and TS8602A,C Chronotherm III Fuel Saver Thermostats, Installation Instructions, pp. 1-12, 1995.
Honeywell T8602D Chronotherm IV Deluxe Programmable Thermostats, Installation Instructions, pp. 1-12, 2002.
Honeywell TH8000 Series Programmable Thermostats, Owner's Guide, pp. 1-44, 2004.
Honeywell, “Excel Building Supervisor-Integrated R7044 and FS90 Ver. 2.0,” Operator Manual, 70 pages, Apr. 1995.
Honeywell, “Installation Guide: Wireless Entry/Exit Remote,” 12 pages, 2011.
Honeywell, “Introduction of the 57350A Honeywell WebPAD Information Appliance,” Home and Building Control Bulletin, 2 pages, Aug. 29, 2000; Picture of WebPad Device with touch screen, 1 Page; and screen shots of WebPad Device, 4 pages.
Honeywell, “RedLINK™ Wireless Comfort Systems,” RedLINK Wireless Technology, 8 pages, Aug. 2011.
Honeywell, “Total Connect Online Help Guide,” Revision A, 800-02577-TC, Mar. 2010.
Honeywell, “Total Connect User Guide,” Revision B, 34 pages, May 15, 2012.
Honeywell, “VisionPRO® 8000 Thermdstats,” Homeywell International Inc., 2 pages, downloaded May 24, 2012.
Honeywell, “W7006A Home Controller Gateway User Guide,” 31 pages, Jul. 2001.
Honeywell, MagicStat® CT3200 Programmable Thermostat, Installation and Programming Instructions, pp. 1-24, 2001.
Honeywell, Wireless Entry/Exit Remote, Operating Manual, 9 pages, 2011.
http://community.lockitron.com/notifications-geofencing-scheduling-sense-bluetooth/633, “Lockitron Community, Notifications, Geofencing, Scheduling, Sense/Bluetooth,” 14 pages, printed Oct. 29, 2014.
http://hunter-thermostats.com/hunter_programmable_thermostats.html, Hunter Thermostat 44668 Specifications, and 44758 Specifications, 2 pages, Printed Jul. 13, 2011.
http://stackoverflow.com/questions/14232712/tracking-multiple-20-locations-with-ios-geofencing, “Tracking Multiple (20+) Locations with iOS Geofencing—Stack Overflow,” 2 pages, printed Oct. 29, 2014.
http://www.alarm.com/about/media/MediaGeneric.aspx?cmid=39, “Alarm.com Cloud Services May Yield Smartest Thermostats on the Planet,” Alarm.com, 2 pages, printed Apr. 24, 2012.
http://www.allure-energy.com/aenf_jan9_12.html, “CES Gets First Look at EverSense,” Allure Energy, 2 pages, printed Feb. 17, 2015.
http://www.cc.gatech.edu/computing/classes/cs6751_94_fall/groupc/climate-2/node1.html, “Contents,” 53 pages, printed Sep. 20, 2004.
http://www.energyhub.com/news/earth-networks-and-energyhub-debut-e5-home-energy-d . . . , “Earth Networks and EnergyHub Debut e5 Home Energy Demand Response Program Based on Neighborhood-LEvel, Real-Time Weather,” EnergyHub, 2 pages, printed Jan. 24, 2012.
http://www.ritetemp.info/rtMenu_13.html, Rite Temp 8082, 6 pages, printed Jun. 20, 2003.
http://www.sync-blog.com/sync/2012/01/how-to-control-your-thermostat-from-anywhere- . . . , “How to Control Your Thermostat from Anywhere Without Breaking the Bank,” Sync(TM) Blog, 2 pages, printed Apr. 27, 2012.
http://www.thermostatsales.com, Robertshaw, “9610 Digital Programmable Thermostat,” 3 pages, printed Jun. 17, 2004.
http://www.thermostatsales.com, Robertshaw, “9700 Deluxe Programmable Thermostat” 3 pages, printed Jun. 17, 2004.
http://www.thermostatsales.com, Robertshaw, “9710 Deluxe Programmable Thermostat,” 3 pages, printed Jun. 17, 2004.
http://www.thermostatsales.com, Robertshaw, “9720 Deluxe Programmable Thermostat,” 3 pages, printed Jun. 17, 2004.
http:/IWww.pmev.tswire.com/nev.ts-releases/allure-energy-unveils-a-combination-of-ibeacon-and-nfc-enabled-smart-sensor-technology-known-as-aura-23885 . . . , “Allure Energy Unveils a Combination of iBeacon and NFC Enabled Smart Sensor Technology Known as Aura,” 6 pages, Jan. 6, 2014.
Hunter, “44200/44250,” Owner's Manual, 32 pages, prior to Jul. 7, 2004.
Hunter, “44300/44350,” Owner's Manual, 35 pages, prior to Jul. 7, 2004.
Hunter, “Auto Saver 550”, Owner's Manual Model 44550, 44 pages, prior to Jul. 7, 2004.
Hunter, “Model 44758 Remote Sensor,” Owner's Manual, 2 pages, Sep. 4, 2008.
Install Guide for Ritetemp Thermostat 8082, 6 pages, 2002.
Invensys™, “9700i 9701i 9715i 9720i Deluxe Programmable Thermostats,” User's Manual, pp. 1-28, prior to Jul. 7, 2004.
Jacobson, “Xfinity Expands Home Automation with Ecofactor Cloud-Based Enabled Thermostats,” downloaded from http://www.cepro.com/article/print/xfinity_expands_home_automation_with_ecofactor_cl . . . , 4 pages, Mar. 5, 2012.
LaMonica, “Smart Thermostat Links to Cloud for Energy Savings,” available at http://news.cnet.com/8031-11128_3-20086261-54/smart-thermost-links-to-cloud-for-ene . . . , 3 pages, printed Apr. 24, 2012.
Lennox, “Network Control Panel (NCP),” User's Manual, 18 pages, Nov. 1999.
Lennox, “Prodigy Control System,” Lennox Industries, 4 pages, May 25, 2012.
Logitech, “Harmony 880 Remote User Manual,” v. 1, pp. 1-15, prior to Nov. 30, 2007.
Lux ELV1 Programmable Line Voltage Thermostat, Installation Instructions, 3 pages, prior to Jul. 7, 2004.
Lux TX500 Series Smart Temp Electronic Thermostat, 3 pages, prior to Jul. 7, 2004.
Lux TX9000 Installation, 3 pages, prior to Apr. 21, 2005.
Lux, “9000RF Remote Instructions,” 2 pages, prior to Nov. 30, 2007.
Lux, “511 Series Smart Temp Electronic Thermostat,” Owner's Manual, 3 pages, prior to Jul. 7, 2004.
Lux, “600 Series Smart Temp Electronic Thermostat,” Owner's Manual, 3 pages, prior to Jul. 7, 2004.
Lux, “602 Series Multi-Stage Programmhble Thermostat,” Owner's Manual, 2 pages, prior to Jul. 7, 2004.
Lux, “605/2110 Series Programmable Heat Pump Thermostat,” Owner's Manual, 3 pages, prior to Jul. 7, 2004.
Lux, “700/9000 Series Smart Temp Electronic Thermostat,” Owner's Manual, 3 pages, prior to Jul. 7, 2004.
Lux, “PSPH521 Series Programmable Heat Pump Thermostat,” Owner's Manual, 3 pages, prior to Jul. 7, 2004.
Lux, “TX1500 Series Smart Temp Electronic Thermostat,” Owner's Manual, 6 pages, prior to Jul. 7, 2004.
Metasys, “HVAC PRO for Windows User's Manual,” 308 pages, 1998.
Mobile Integrated Solutions, LLC, “MobiLinc Take Control of Your Home, MobiLinc and Geo-Fence Awareness,” 9 pages, downloaded Mar. 27, 2015.
Mounting Template for Ritetemp Thermostat 8082, 1 page, 2002.
Mozer, “The Neural Network House: An Environment that Adapts to its Inhabitants,” Department of Computer Science and Institute of Cognitive Science University of Colorado, 5 pages, 1998.
OMRON Electronic Components, LLC, “Micro Tilt Sensor D6B,” Cat. No. JB301-E3-01, 6 pages, Mar. 2005.
OMRON Electronic Components, LLC, “Micro Tilt Sensor D6B,” Cat. No. BO2WAD1, 2 pages, Jun. 2002.
Operation Manual for Ritetemp Touch Screen Thermostat 8082, 8 pages, 2002.
Pan et al., “A Framework for Smart Location-Based Automated Energy Controls in a Green Building Testbed,” 6 pages, downloaded Jan. 30, 2015.
Proliphix, “Web Enabled IP Thermostats Intelligent HVAC Control,” Proliphix Inc., 2 pages, on or before Aug. 28, 2004.
Proliphix, “Web Enabled IP Thermostats, Ultimate in Energy Efficiency!,” Proliphix Inc., 2 pages, on or before Aug. 28, 2004.
Proliphix, Inc., “NT10e & NT20e,” 54 pages, on or before Aug. 30, 2005.
Quick Start Guide for Ritetemp Thermostat 8082, 1 page, 2002.
Remote Control Power Requirement for Ritetemp Thermostat 8082, 1 page, 2002.
Ritetemp Operation 8029, 3 pages, Jun. 19, 2002.
Ritetemp Operation 8050, 5 pages, Jun. 26, 2002.
Ritetemp Operation 8085, pp. 1-6, prior to Apr. 21, 2005.
Saravanan et al, “Reconfigurable Wireless Interface for Networking Sensors,” IJCSNS International Journal of Computer Science and Network Security, vol. 8 No. 7, pp. 270-276. Revised Jul. 20, 2008.
Screenshot of http://lagotek.com/index.html?currentSection=TouchIt, Lagotek, 1 page, prior to Mar. 29, 2012.
Sealed Unit Parts Co., Inc., Supco & CTC Thermostats . . . loaded with features, designed for value!, 6 pages, prior to Apr. 21, 2005.
Sharp Corporation, “GP1S036HEZ Phototransistor Output, Transmissive Photointerrupter with Tilt Direction (4-Direction) Detecting,” pp. 1-11, Oct. 3, 2005.
SmartAC, “Thermostat Programming Web Site Guide,” PG-WC-7E, 2 pages, 2009.
Travis Industries, Remote Fireplace Thermostat, Part #99300651, 6 pages, printed Feb. 3, 2003.
Trouble Shooting Guide for Ritetemp Thermostat 8082, 1 page, 2002.
Visor Handheld User Guide, 280 pages, Copyright 1999-2000.
Warmly Yours, “Model TH111GFCI-P (120 VAC),” Manual, pp. 1-4, prior to Jul. 7, 2004.
White-Rodgers 1F80-224 Programmable Electronic Digital Thermostat, Installation and Operation Instructions, 8 pages, prior to Apr. 21, 2005.
White-Rodgers Comfort-Set III Thermostat, pp. 1-44, prior to Jul. 7, 2004.
White-Rodgers Installation Instructions for Heating & Air Conditioning IF78 Non-Programmable Thermostat, 6 pages, prior to Apr. 21, 2005.
White-Rodgers Installation Instructions for Heating & Air Conditioning IF78 5/2 Day Programmable Thermostat, 7 pages, prior to Jul. 7, 2004.
White-Rodgers, “Installation Instructions for Heating & Air Conditioning IF72 5/2 Day Programmable Heat Pump Thermostat,” 8 pages, prior to Jul. 7, 2004.
White-Rodgers, “Comfort-Set 90 Series Thermostat,” Manual, pp. 1-24, prior to Jul. 7, 2004.
White-Rodgers, 1F80-240 “(for Heating Only systems) Programmable Electronic Digital Thermostat,” Installation and Operation Instructions, 8 pages, prior to Jul. 7, 2004.
White-Rodgers, 1F80-241 “Programmable Electronic Digital Thermostat,” Installation and Operation Instructions, 6 pages, prior to Jul. 7, 2004.
White-Rodgers, 1F80-261 “Programmable Electronic Digital Thermostat,” Installation and Operation Instructions, 8 pages, prior to Jul. 7, 2004.
White-Rodgers, 1F81-261 “Programmable Electronic Digital Multi-Stage Thermostat,” Installation and Operation Instructions, 8 pages, prior to Jul. 7, 2004.
White-Rodgers, 1F82-261 “Programmable Electronic Digital Heat Pump Thermostat,” Installation and Operation Instructions, 8 pages, prior to Jul. 7, 2004.
White-Rodgers, Comfort-Set 90 Series Premium, 4 pages, prior to Apr. 21, 2005.
www.icmcontrols.com, Simplecomfort, SC3000 Single Stage Heat/Single Stage Cool or Single Stage Heat Pump/Manual Changeover, 1 page, prior to Jul. 7, 2004.
www.icmcontrols.com, Simplecomfort, SC3001 Single Stage Heat/Single Stage Cool or Single Stage Heat Pump/Manual Changeover, 1 page, prior to Jul. 7, 2004.
www.icmcontrols.com, Simplecomfort, SC3006 Single Stage Heat/Single Stage Cool or Single Stage Heat Pump/Manual Changeover, 1 page, prior to Jul. 7, 2004.
SmartThings Inc., “2 Ecobee Si Thermostat + Geofencing,” 17 pages, downloaded Nov. 3, 2014.
St. John, “Smart Grid's Latest Cloud: Honeywell Cloud-Connected Thermostats,” 7 pages, Nov. 3, 2011.
Totaline Model P474-1035 Owner's Manual Programmable 5-2 Day Digital Thermostat, pp. 1-21, Apr. 2003.
Totaline Star CPE230RF, Commercial Programmable Thermostat Wireless Transmitter, Owner's Manual, pp. 1-16, Oct. 1998.
Totaline Star P/N P474-0130 Non-Programmable Digital Thermostat Owner's Manual, pp. 1-22, prior to Apr. 21, 2005.
Totaline, “1 for All Programmable Digital Thermostat,” Owner's Manual P/N P374-1100FM, 23 pages, Nov. 1998.
Totaline, “1 for All Programmable Digital Thermostat,” Owner's Manual P/N P474-1050, 21 pages, Nov. 1998.
Totaline, “1 for All Programmable Digital Thermostat,” Owner's Manual P/N P374-1100, 24 pages, Apr. 2001.
Totaline, “Intellistat Combination Temperature and Humidity Control,” Owner's Manual P/N P374-1600, 25 pages, Jun. 2001.
Totaline, “P/N P374-0431 Thermostat Remote Control and Receiver,” Owner's Manual, 11 pages, prior to Nov. 30, 2007.
Totaline, “P474-1100RF, P474-1100REC Wireless Thermostat,” 1 page, prior to Nov. 30, 2007.
Totaline, “Programmable Thermostat Configurable for Advanced Heat Pump or Dual Fuel Operation,” Owner's Manual P/N P374-1500, 24 pages, Jun. 1999.
Totaline, “Wireless Remote Sensor, Model P474-0401-1RF/REC,” 2 pages, prior to Nov. 30, 2007.
Totaline, “Instructions P/N P474-1010”, Manual, 2 pages, Dec. 1998.
Totaline, “Programmable Thermostat”, Homeowner's Guide, 27 pages, Dec. 1998.
Totaline, “Wireless Programmable Digital Thermostat,” Owner's Manual 474-1100RF, 22 pages, 2000.
Trane, “System Programming, Tracer Summit Version 14, BMTW-SVP01D-EN,” 623 pages, 2002.
Trane, “Wireless Zone Sensor. Where Will Wireless Technology Take You?,” 4 pages, Feb. 2006.
www.icmcontrols.com, Simplecomfort; SC3201 2 Stage Heat Pump Manual Changeover, 1 page, prior to Jul. 7, 2004.
www.icmcontrols.com, Simplecomfort, SC3801 2 Stage Heat/2 Stage Cool 2 Stage Heat Pump/Audio Changeover, 1 page, prior to Jul. 7, 2004.
Xytronix Research & Design, Inc., “X-300 User's Manual, Revision 1.2” 89 pages, Jul. 30, 2009.
“Energy User News,” Chilton Company, ISSN: 0162-9131, Mar. 1, 1997, 4 pp.
Andover Controls “Network News” Andover Controls Corporation, vol. 2, No. 2, 8 pages, 1997. (Applicant points out, in accordance with MPEP 609.04(a), that the year of publication, 1997 is sufficiently earlier than the effective U.S. filing date, so that the particular month of publication is not in issue.).
Andover Controls, “Andover Controls World,” Andover Controls Corporation , 4 pages, 1997. (Applicant points out, in accordance with MPEP 609.04(a), that the year of publication, 1997 is sufficiently earlier than the effective U.S. filing date, so that the particular month of publication is not in issue.).
Andover Controls, “Facility Management Unleashed,” Andover Controls Corporation, 6 pages, 2002. (Applicant points out, in accordance with MPEP 609.04(a), that the year of publication, 2002 is sufficiently earlier than the effective U.S. filing date, so that the particular month of publication is not in issue.).
Bay Controls LLC “Bayweb thermostat Advanced Model Owner's Manual”, Oct. 6, 2011, 31 pgs (Year: 2011).
Carrier ComfortChoice “Verifiable Demand Response, Two-Way Communicating Thermostat,” accessed from http://www.comfortchoice.com, 2007, 4 pp. (Applicant points out, in accordance with MPEP 609.04(a), that the year of publication, 2007 is sufficiently earlier than the effective U.S. filing date, so that the particular month of publication is not in issue.).
Carrier ComfortChoice, “Web Interface, User Guide,” Jan. 2002. 8 pp.
Central and Southwest Communications, “Customer Choice and Control Thermostat Touchpad, User Guide,” 69-1005, May 1996, 18 pp.
Comverge, Inc., “Adaptive Algorithms Yield Greater Performance,” 2 pages, prior to Jun. 28, 2007.
Comverge, Inc., “SuperStat Thermostat Family,” 2 pages, prior to Jun. 28, 2007.
Facility Robotics Solutions Direct, “Who We Are and What We Do,” Solutions Direct, 2 pages, Sep. 19, 1997.
Facility Robotics Solutions, “Where Can I go to Find Everything I Need to Put Together Lon Works-Based Automation Systems?,” Solutions Direct, 5 pages, prior to Jun. 28, 2007.
Federal Energy Regulatory Commission, “Assessment of Demand Response & Advanced Metering, Staff Report,” 228 pages, Aug. 2006.
Gentec, “Feature Focus, Threat Level Management,” 2 pages, 2013. (Applicant points out, in accordance with MPEP 609.04(a), that the year of publication, 2013 is sufficiently earlier than the effective U.S. filing date, so that the particular month of publication is not in issue.).
Higgins “First Time User Experiences,” 273 pages, downloaded May 12, 2015.
Higgins, “First Time User Experiences in Mobile Apps,” http:/lwww.kryshiggins.com/first-timeuser-exoeriences-in-mobile-aoos/, 14 pages, printed May 12, 2015.
“Amazon.com: Metal Wall Plate. Medium 10″ × 12″ Hanging Magnetic Spice Rack Wall Mount, Stainless Steel Plate for Backsplash or Cupboard . . . ” accessed from http://www.amazon.com/Magnetic-Spice-Stainless-Backsplash-Cupboard/dp/B009CUIYMO 5 pages, printed Jul. 23, 2015.
“Switchplates, Magnetic Wall Plates, Decorative Wall Plates, RQ Home,” http://www.rqhome.com/wall-plate-decor/metal-switch-plates.html, 3 pages, printed Jul. 23, 2015.
Honeywell, “TotalHome Energy Management System 2000, Specification Data,” 2 pages, 1996. (Applicant points out, in accordance with MPEP 609.04(a), that the year of publication, 1996 is sufficiently earlier than the effective U.S. filing date, so that the particular month of publication is not in issue.).
Honeywell Cannon Technologies Alliance, “Programmable Load Management Thermostat Weekday/Weekend (5-day/Saturday/Sunday) T7512A,B, User's Guide,” 32 pages, 2002. (Applicant points out, in accordance with MPEP 609.04(a), that the year of publication, 2002 is sufficiently earlier than the effective U.S. filing date, so that the particular month of publication is not in issue.).
Honeywell Cannon Technologies Alliance, “T7512A,B Programmable Load Management Thermostat, Installation Instructions,” 8 pages, 2002. (Applicant points out, in accordance with MPEP 609.04(a), that the year of publication, 2002 is sufficiently earlier than the effective U.S. filing date, so that the particular month of publication is not in issue.).
Honeywell, “CM907 Programmable Thermostat, Product Specification Sheet,” Honeywell Control Systems Limited, 7 pages, Sep. 2006. (Applicant points out, in accordance with MPEP 609.04(a), that the year of publication, 2006 is sufficiently earlier than the effective U.S. filing date, so that the particular month of publication is not in issue.).
Honeywell, “Excel Building Supervisor-Integrated R7044 and FS90 Ver. 2.0,” Operator Manual, 74-1268, 72 pages Apr. 1995. (Applicant points out, in accordance with MPEP 609.04(a), that the year of publication, 1995 is sufficiently earlier than the effective U.S. filing date, so that the particular month of publication is not in issue.).
Honeywell, “Programmable Load Controller Weekday/Weekend (5-day/Saturday/Sunday) Programmable Heat and/or Cool Conventional and Heat Pump T7512A,B,C, User's Guide,” 32 pages, 1996. (Applicant points out, in accordance with MPEP 609.04(a), that the year of publication, 1996 is sufficiently earlier than the effective U.S. filing date, so that the particular month of publication is not in issue.).
Honeywell, “R4525A Load Relay Module, Installation Instructions,” 69-0857-1, 4 pages, 1995. (Applicant points out, in accordance with MPEP 609.04(a), that the year of publication, 1995 is sufficiently earlier than the effective U.S. filing date, so that the particular month of publication is not in issue.).
Honeywell, “T7512A,B,C,D Programmable Load Controller, Installation Instructions,” 69-0988-1, 8 pages, 1997. (Applicant points out, in accordance with MPEP 609.04(a), that the year of publication, 1997 is sufficiently earlier than the effective U.S. filing date, so that the particular month of publication is not in issue.).
Honeywell, “T7525/T7526 Thermostat Touchpad, User Guide,” TotalHome, 16 pages, 1995. (Applicant points out, in accordance with MPEP 609.04(a), that the year of publication, 1995 is sufficiently earlier than the effective U.S. filing date, so that the particular month of publication is not in issue.).
Honeywell, “TotalHome Energy Management System 2000,” TotalHome, 12 pages, 1995. (Applicant points out, in accordance with MPEP 609.04(a), that the year of publication, 1995 is sufficiently earlier than the effective U.S. filing date, so that the particular month of publication is not in issue.).
Honeywell, “W8525A,B,C,D Control Module, Installation Instructions,” 69-0985, 8 pages, 1995. (Applicant points out, in accordance with MPEP 609.04(a), that the year of publication, 1995, is sufficiently earlier than the effective U.S. filing date, so that the particular month of publication is not in issue.).
“Download Free Muscle Car Theme for IOS4.0,” accessed from http://lhemes.mob.org,/gallery/134346/, 2 pages printed Jul. 16, 2015.
What is Desktop Theme? Definition From Whatis.com, “accessed from http://searchenterprisedesktop.techtarget.com/definition/desktop-theme,” 5 pages, printed Jul. 16, 2015.
“Community Showcase: Natural Landscapes 3 Theme—Microsoft Windows,” http://windows.microsoft.com/en-us/windows/community-showcase-landscapes-3-download-theme, 1 page, printed Jul. 16, 2015.
“How do I mount my Arlo cameras,” https://community.netgear.com/t5/Arlo-Knowledge-Base/How-do-l-mount-my-Arlo-cameras/ta-p/999, NETGEAR Communities, 4 pages, printed Jul. 23, 2015.
I-Stat, “Installation and Operation Manual, for Low Voltage (24VAC) Systems Only,” 14 pages, Nov. 2002.
LightStat, “Model RTPstat Thermostat,” accessed from http://www.lightstat.com 2 pages, prior to Jun. 28, 2007.
LuxPro “PSD122E, Installation and Operating Instructions,” 6 pages, prior to Jun. 28, 2007.
LuxPro, “PSP722E Everything Stat,” 2 pages, prior to Jun. 28, 2007.
SmartWay Solutions, Inc., “The Talking Thermostat, User's Guide,” 2 pages, downloaded Jul. 16, 2015.
“Maingate Home,” Comverge, accessed from http://www.comverge.com/printer.cfm on or about May 22, 2007, 1 page.
“EMi—Carrier's Internet Communicating Programmable Thermostat,”, Carrier, accessed from http://www.comfortchoice.carrier.com/details accessed on or about May 22, 2007, 1 pp.
“Carrier System Elements and Hardware,” Carrier, accessed from http://www.comfortchoice.carrier.com/details on or about May 22, 2007, 1 pp.
Trane, “Creating Input/Output Objects,” BMTW-SVP01D-EN, The American Standard Company, Nov. 2001, 196 pp.
“Controlling Your Nest Learning Thermostat from the Nest App or the Web,” Nest Support, accessed from https://nest.com/support/article/Controlling-your-Nest-Learning-Thermostatfrom-the-Nest-app-or-the-Web accessed on or about May 13, 2015, 14 pages.
Trane, “Using the Graphing Control Editor,” The American Standard Company, Nov. 2001, 181 pp.
http://www.lightstat.com/products/utility.asn, “Lightstat Products for Utility Demand Response and Load Curtailment Programs,” 2 pages, printed May 22, 2007.
http://www.comfortchoice.carrier.com/details printable, “Carrier How Does it Work?”, 1 page, printed May 22, 2007.
“The Thermostat of Choice for HVAC Automation,” Aprilaire Communicating Thermostat, accessed from http://www.smarthome.com/3020t.html, on or about May 16, 2007, 4 pages.
European Response to Communication dated Jan. 22, 2019 for corresponding Application Serial No. 17746337.9 filed on Aug. 19, 2019 (18 pp).
Related Publications (1)
Number Date Country
20180023836 A1 Jan 2018 US