Patent Grant
10873632
This patent specification relates to system monitoring and control, such as the monitoring and control of heating, ventilation, and air conditioning (HVAC) systems. More particularly, this patent specification relates to methods, systems and related computer program products for provisioning, supporting, maintaining, and/or remotely controlling one or more network-connected thermostats.
Substantial effort and attention continues toward the development of newer and more sustainable energy supplies. The conservation of energy by increased energy efficiency remains crucial to the world's energy future. According to an October 2010 report from the U.S. Department of Energy, heating and cooling account for 56% of the energy use in a typical U.S. home, making it the largest energy expense for most homes. Along with improvements in the physical plant associated with home heating and cooling (e.g., improved insulation, higher efficiency furnaces), substantial increases in energy efficiency can be achieved by better control and regulation of home heating and cooling equipment. By activating heating, ventilation, and air conditioning (HVAC) equipment for judiciously selected time intervals and carefully chosen operating levels, substantial energy can be saved while at the same time keeping the living space suitably comfortable for its occupants.
It would be beneficial, at both a societal level and on a per-home basis, for a large number of homes to have their existing older thermostats replaced by newer, microprocessor controlled “intelligent” thermostats having more advanced HVAC control capabilities that can save energy while also keeping the occupants comfortable. To do this, these thermostats will need more information from the occupants as well as the environments where the thermostats are located. Preferably, these thermostats will also be capable of connection to computer networks, including both local area networks (or other “private” networks) and wide area networks such as the Internet (or other “public” networks), in order to obtain current and forecasted outside weather data, cooperate in so-called demand-response programs (e.g., automatic conformance with power alerts that may be issued by utility companies during periods of extreme weather), enable users to have remote access and/or control thereof through their network-connected device (e.g., smartphone, tablet computer, PC-based web browser), and other advanced functionalities that may require network connectivity.
Among other requirements, the successful implementation of intelligent network-connected thermostats into widespread, practical everyday use in a large number of homes and business requires the deployment of computers, networks, software systems and other network infrastructure capable of providing the necessary provisioning, data management, and support. Data communications methods between the intelligent thermostats and centrally provided management servers (which can also be termed “cloud-based” management servers), needs to be responsive, robust, and scalable. At the same time, the hardware and methodologies employed need to be compatible with, and workable in view of, a large installed base of conventional routers and network services that are already in homes and business, such that widespread adoption of the network-connected intelligent thermostats be commercially feasible.
One further issue that needs to be addressed in promoting the adoption of intelligent network-connected thermostats relates to the level of sophistication and effort required to install, configure, and manage such thermostats. As the benefits of these intelligent thermostats are realized, a broad range of individuals and businesses will inevitably be interested in their adoption. People calculating the reduced costs and energy savings might be ready to purchase such a device yet may hesitate when it comes to installation, configuration, and management. Some may wonder whether they will be able to follow the instructions provided in the installation and user manual provided with the thermostat. Adding a network connection to the thermostat device can further complicate matters if the users are not adept in computers and networking.
To overcome these and other associated issues, it is important that the intelligent thermostat is easily installed, configured, and managed. Complex installation instructions with numerous steps should be avoided as they might be confusing to a large number of users and prevent the intelligent thermostat from being installed or set up correctly. Installation problems may also arise if the installation requires a user to enter numerous codes and network addresses on the intelligent thermostat and/or other pieces of equipment. Instead, the intelligent thermostat installation and configuration should be achievable even by a user with limited experience and knowledge in “tech”.
One further issue that needs to be addressed in promoting the adoption of intelligent network-connected thermostats relates to the human-machine interface the will be experienced by the user when interacting with such thermostats. It would be desirable to provide intelligent network-connected thermostat and an associated cloud-based provisioning, management, and control system therefor that not only saves energy, but that also provides a user-friendly, intuitive, pleasant, and appealing experience for the user. In addition to providing such positive and compelling experiences directly at the user interface of the physical thermostat itself (i.e., the “walk-up” user interface), it would be desirable to provide such positive and compelling user experiences when the user is interacting remotely with their network-connected thermostat over a computer network using their computer web browser, smartphone, tablet computer, or other remote access device.
It is to be appreciated that although exemplary embodiments are presented herein for the particular context of HVAC system control, there are a wide variety of other resource usage contexts for which the embodiments are readily applicable including, but not limited to, water usage, air usage, the usage of other natural resources, and the usage of other (i.e., non-HVAC-related) forms of energy, as would be apparent to the skilled artisan in view of the present disclosure. Therefore, such application of the embodiments in such other resource usage contexts is not outside the scope of the present teachings.
Aspects of the present invention provide methods, systems and related architectures for facilitating the provisioning, installation, configuration, control, and/or management of a network-connected thermostat. In one preferred embodiment, there is provided a method for secure automated association or “pairing” of a wirelessly communicating thermostat with a user account on a cloud-based thermostat management system in a manner that reduces or minimizes an amount of user effort involved. Upon first installation and power-up of the thermostat (or subsequently thereto, such as for a re-installation or factory reset), the thermostat automatically instantiates wireless connection to an integrated router associated with a local area network (“private network router”) that serves the home, business, or other structure (“enclosure”) in which the thermostat is installed, the thermostat walking the user through wireless network selection (if multiple wireless networks are present) and wireless network security password entry (if required) by virtue of an intuitive user interface on the thermostat that includes an electronic display. The thermostat, which is located on a private network served by the private network router, is configured and programmed to then instantiate communication with the cloud-based thermostat management system, which is located on a public network such as the Internet. The cloud-based thermostat management system maintains a unique account identifier (such as an e-mail address) for each user account that has been created, and a unique thermostat identifier (such as a MAC address) for each thermostat unit that has been manufactured. In a method directed to pairing the newly installed thermostat with an associated user account with reduced or minimal user effort, the cloud-based thermostat management server keeps track, for each user account, of a public network address from which that user most recently accessed their user account on the cloud-based thermostat management server, such tracking being applicable for both previously established user accounts and newly established user accounts. Upon instantiation of communication with the cloud-based thermostat management system, the newly installed but as-yet unpaired thermostat (“pairing candidate thermostat”) transmits thermostat metadata information associated therewith, including its unique thermostat identifier, to the cloud-based thermostat management server, this information being appended with the public network address of the private network router on its way out to the cloud-based thermostat management server. The cloud-based thermostat management server then makes a determination whether the pairing candidate thermostat can be automatically associated with a user account identifier, based on a comparison of (i) the public network address of the pairing candidate thermostat's private network router and (ii) the tracked public network addresses from which user accounts have recently been accessed. In the event there is a match between the public network address of the pairing candidate thermostat's private network router the public network address from which one user account has recently been accessed, than an automatic association is established between the unique thermostat identifier for that thermostat and the unique account identifier for that user account. In the event that there is no such match, or in the event that any of a plurality of predetermined safeguard methods or criteria are not met, then the user is prompted on the thermostat user interface display to manually assist in the pairing process. For the manual assistance process, the thermostat is provided with an easy-to-remember passcode from the cloud-based thermostat management server, and then displays that easy-to-remember pass code to the user on the thermostat display along with a request for the user to log into their user account on the cloud-based management server, or to establish their user account if one is not yet established, and then enter that passcode when so prompted. According to some embodiments, the predetermined safeguard methods or criteria include displaying the user account identifier (e.g., the user's e-mail address) on the thermostat display screen, and requesting an affirmative confirmation input from the user into the thermostat.
Thus, in one scenario that is expected to be relatively common, a user will drive home with their new thermostat, log into the cloud-based management server to establish an account (e.g., tomsmith3@mailhost.com) from a computing device in their home which connects to the Internet using the same wireless-capable router that the thermostat will be using, and then install and power up their thermostat. In this case, there will be a match between the public network address of their thermostat's private network router and the tracked public network addresses from which they established their user account, and so there will be an automated association or “pairing” of their new thermostat's unique thermostat identifier and their user account identifier on the cloud-based management server. During the initial setup process, the user will simply encounter a safeguard message on the thermostat display, such as “Connect to tomsmith3@mailhost.com?” and will readily provide a confirmatory input since they are familiar with their own e-mail address, and the pairing process will be complete. Advantageously, however, even in some less common or complex scenarios for which such automated pairing may not result in a match, or for which the predetermined safeguard methods or criteria are not met, the user will still be provided with a relatively simple manual assistance process to establish the pairing at the cloud-based management server as described above. According to some embodiments, the predetermined safeguard methods or criteria further include canceling any pairing associations (i.e., requiring manual assistance) in any of the following cases: (i) two different user accounts have been logged into from the same public network address now being used by the thermostat's private network router within the past 24 hours (or other suitable time window), and (ii) there are two different pairing candidate thermostats simultaneously accessing the cloud-based thermostat management server from the same public network address. Other heuristics or testing methods directed to detecting particular cases of ambiguity, mistake, or likely mismatch can optionally be applied as additional safeguards without departing from the scope of the present teachings.
According to another preferred embodiment, a method of configuring a thermostat for communication with a computer device over a network connection is provided. To connect the thermostat on the network, a user configures a wireless network interface controller associated with the thermostat connecting the thermostat to a private network (e.g., by entering a wireless passcode, selecting from plural available networks, etc.). A router on the private network provides connectivity from the thermostat to a public network where a thermostat management system is located. Once the thermostat is connected to its private network, the thermostat sends thermostat metadata to be registered with a thermostat identifier in a thermostat registration pool on the thermostat management system, the thermostat metadata being appended with the public network address of the router on its way to the thermostat management server. The public network address associated with the thermostat is shared by the router with other computer devices and thermostats located on the same private network. The thermostat management system pairs the thermostat registered in the thermostat registration pool to a thermostat management account on the thermostat management system when it is determined that the thermostat is on a same private network as a computer device that has recently accessed the thermostat management account. The pairing operation allows the thermostat to be accessed by the thermostat management account over the public network through the thermostat management system.
Another aspect of the present invention includes creating a thermostat management account on a thermostat management system to be used to communicate with a thermostat having network connectivity. In one embodiment, a thermostat access client running on a computer device on a private network accesses a thermostat management system on a public network. The thermostat access client requests the thermostat management system to provision a thermostat management account using an account name. The thermostat management account will be used to communicate with at least one thermostat registered on the thermostat management system. As part of the provisioning operation, the thermostat management system associates the public network address used by the computer device to access the thermostat management system from the private network. This public network address is used to identify thermostats on the same private network as the computer device and therefore suitable for pairing with the thermostat management account. As previously described, the same public network address is shared by the router with computer devices and thermostats located on the same private network. Once it is created, the thermostat management account on the thermostat management system may be paired to a thermostat on the same private network when the corresponding public network addresses match. Once again, the pairing operation allows the newly created thermostat management account to access and communicate with the thermostat through the thermostat management system.
Yet another aspect of the invention includes uses logic on the thermostat management system to automatically facilitate a pairing of the thermostat with the thermostat communication account. In one embodiment, the thermostat management system detects that a computer device on a private network has established or otherwise accessed a thermostat management account on the thermostat management system. For example, this may occur if a computer device executes a thermostat access client that accesses the thermostat management account. The thermostat management system receives a public network address associated with the computer device accessing the thermostat management account. Next, the thermostat management system retrieves thermostat metadata from the thermostat, which communication will include a public network address provided by a router on the private network associated the thermostat. An automated association or pairing between the thermostat management account and the thermostat is established if the public network address registered with the thermostat metadata matches the public network address used by other the computer device to access the thermostat management account. Accordingly, the thermostat management account is paired with the thermostat if a comparison indicates that the thermostat has the same public network address as the computer device accessing the thermostat management account. Pairing the thermostat management account to the thermostat allows the thermostat management account to communicate with the thermostat over the public network through the thermostat management system.
In the following detailed description, for purposes of explanation, numerous specific details are set forth to provide a thorough understanding of the various embodiments of the present invention. Those of ordinary skill in the art will realize that these various embodiments of the present invention are illustrative only and are not intended to be limiting in any way. Other embodiments of the present invention will readily suggest themselves to such skilled persons having the benefit of this disclosure.
In addition, for clarity purposes, not all of the routine features of the embodiments described herein are shown or described. One of ordinary skill in the art would readily appreciate that in the development of any such actual embodiment, numerous embodiment-specific decisions may be required to achieve specific design objectives. These design objectives will vary from one embodiment to another and from one developer to another. Moreover, it will be appreciated that such a development effort might be complex and time-consuming but would nevertheless be a routine engineering undertaking for those of ordinary skill in the art having the benefit of this disclosure.
It is to be appreciated that while one or more embodiments are described further herein in the context of typical HVAC system used in a residential home, such as single-family residential home, the scope of the present teachings is not so limited. More generally, thermostats according to one or more of the preferred embodiments are applicable for a wide variety of enclosures having one or more HVAC systems including, without limitation, duplexes, townhomes, multi-unit apartment buildings, hotels, retail stores, office buildings and industrial buildings. Further, it is to be appreciated that while the terms user, customer, installer, homeowner, occupant, guest, tenant, landlord, repair person, and the like may be used to refer to the person or persons who are interacting with the thermostat or other device or user interface in the context of one or more scenarios described herein, these references are by no means to be considered as limiting the scope of the present teachings with respect to the person or persons who are performing such actions.
Some embodiments of thermostat 110 in
As used herein, a “learning” thermostat refers to a thermostat, or one of plural communicating thermostats in a multi-thermostat network, having an ability to automatically establish and/or modify at least one future setpoint in a heating and/or cooling schedule based on at least one automatically sensed event and/or at least one past or current user input. As used herein, a “primary” thermostat refers to a thermostat that is electrically connected to actuate all or part of an HVAC system, such as by virtue of electrical connection to HVAC control wires (e.g. W, G, Y, etc.) leading to the HVAC system. As used herein, an “auxiliary” thermostat refers to a thermostat that is not electrically connected to actuate an HVAC system, but that otherwise contains at least one sensor and influences or facilitates primary thermostat control of an HVAC system by virtue of data communications with the primary thermostat. In one particularly useful scenario, the thermostat 110 is a primary learning thermostat and is wall-mounted and connected to all of the HVAC control wires, while the remote thermostat 112 is an auxiliary learning thermostat positioned on a nightstand or dresser, the auxiliary learning thermostat being similar in appearance and user-interface features as the primary learning thermostat, the auxiliary learning thermostat further having similar sensing capabilities (e.g., temperature, humidity, motion, ambient light, proximity) as the primary learning thermostat, but the auxiliary learning thermostat not being connected to any of the HVAC wires. Although it is not connected to any HVAC wires, the auxiliary learning thermostat wirelessly communicates with and cooperates with the primary learning thermostat for improved control of the HVAC system, such as by providing additional temperature data at its respective location in the enclosure, providing additional occupancy information, providing an additional user interface for the user, and so forth.
It is to be appreciated that while certain embodiments are particularly advantageous where the thermostat 110 is a primary learning thermostat and the remote thermostat 112 is an auxiliary learning thermostat, the scope of the present teachings is not so limited. Thus, for example, while certain initial provisioning methods that automatically pair associate a network-connected thermostat with an online user account are particularly advantageous where the thermostat is a primary learning thermostat, the methods are more generally applicable to scenarios involving primary non-learning thermostats, auxiliary learning thermostats, auxiliary non-learning thermostats, or other types of network-connected thermostats and/or network-connected sensors. By way of further example, while certain graphical user interfaces for remote control of a thermostat may be particularly advantageous where the thermostat is a primary learning thermostat, the methods are more generally applicable to scenarios involving primary non-learning thermostats, auxiliary learning thermostats, auxiliary non-learning thermostats, or other types of network-connected thermostats and/or network-connected sensors. By way of even further example, while certain methods for cooperative, battery-conserving information polling of a thermostat by a remote cloud-based management server may be particularly advantageous where the thermostat is a primary learning thermostat, the methods are more generally applicable to scenarios involving primary non-learning thermostats, auxiliary learning thermostats, auxiliary non-learning thermostats, or other types of network-connected thermostats and/or network-connected sensors.
Enclosure 100 further includes a private network accessible both wirelessly and through wired connections and may also be referred to as a Local Area Network or LAN. Network devices on the private network include a computer 124, thermostat 110 and remote thermostat 112 in accordance with some embodiments of the present invention. In one embodiment, the private network is implemented using an integrated router 122 that provides routing, wireless access point functionality, firewall and multiple wired connection ports for connecting to various wired network devices, such as computer 124. Other embodiments may instead use multiple discrete switches, routers and other devices (not shown) to perform networking functions equivalent to or in addition to those provided by integrated router 122.
Integrated router 122 further provides network devices access to a public network, such as the Internet, provided enclosure 100 has a connection to the public network generally through a cable-modem, DSL modem and a service provider of the Internet or other public network. The Internet and other public networks are sometimes referred to as a Wide-Area Network or WAN. In one embodiment, integrated router 122 may direct communications to other devices on these networks using a network protocol such as TCP/IP. If the communications is directed to a device or service outside the private network, integrated router 122 may route the communications outside the private network to the public network such as the Internet.
In some embodiments, thermostat 110 may wirelessly communicate with remote thermostat 112 over the private network or through an ad hoc network formed directly with remote thermostat 112. During communication with remote thermostat 112, thermostat 110 may gather information remotely from the user and from the environment detectable by the remote thermostat 112. For example, remote thermostat 112 may wirelessly communicate with the thermostat 110 providing user input from the remote location of remote thermostat 112 or may be used to display information to a user, or both. Like thermostat 110, embodiments of remote thermostat 112 may also include sensors to gather data related to occupancy, temperature, light and other environmental conditions. In an alternate embodiment, remote thermostat 112 may also be located outside of the enclosure 100.
In accordance with some embodiments, a computer device 124 in enclosure 100 may remotely control thermostat 110 by accessing a thermostat management account through a thermostat management system (not shown in
In heating, heating coils or elements 242 within air handler 240 provide a source of heat using electricity or gas via line 236. Cool air is drawn from the enclosure via return air duct 246 through filter 270, using fan 238 and is heated through heating coils or elements 242. The heated air flows back into the enclosure at one or more locations via supply air duct system 252 and supply air registers such as register 250. In cooling, an outside compressor 230 passes a gas such as Freon through a set of heat exchanger coils 244 to cool the gas. The gas then goes through line 232 to the cooling coils 234 in the air handler 240 where it expands, cools and cools the air being circulated via fan 238. A humidifier 254 may optionally be included in various embodiments that returns moisture to the air before it passes through duct system 252. Although not shown in
In the embodiment illustrated, thermostat 110 is enclosed by housing 316 with a forward-facing surface including a cover 304 and a grille member 308. The grille member 308 is designed to compliment the sleek, simple, uncluttered and elegant design of thermostat 110 to while facilitating the integration and operation of sensors located within housing 316 of the thermostat. Notably, included in the thermostat according to some preferred embodiments is passive infrared (PIR) occupancy sensors and temperature sensors behind grille member 308. Additional sensors may also include an ambient light sensor (not shown) and an active proximity sensor (not shown) positioned near the top of the thermostat just behind the cover 304. Some embodiments of housing 316 include a backplate 314 and a head unit 312. Housing 316 provides an attractive and durable configuration for one or more integrated sensors used by thermostat 110 and contained therein.
A central display area 306 of cover 304 allows information related to the operation of the thermostat to be displayed while an outer area 310 of cover 304 may be made opaque using a paint or smoke finish. For example, central display area 306 may be used to display a current temperature as illustrated in
Embodiments of thermostat 110 are circular in shape and have an outer ring 312 for receiving user input. Side view of thermostat 110 in
Head unit 312 of thermostat 110 slides onto backplate (not shown) and further includes head unit front 402 and head unit frame 404. The head unit front 402 includes outer ring 302, central display area 306 and outer area 310 of cover 304 and grille member 308 designed in accordance with embodiments of the present invention.
According to some embodiments, for the combined purposes of inspiring user confidence and further promoting visual and functional elegance, the thermostat 110 is controlled by only two types of user input, the first being a rotation of the outer ring 302 as illustrated in
According to some embodiments, multiple types of user input may be generated depending on the way a pushing inward of head unit front 402 is effectuated. In some embodiments a single brief push inward of head unit front 402 until the audible and/or tactile click occurs followed by a release (single click) can be interpreted as one type of user input (also referred to as an “inward click”). In other embodiments, pushing the head unit front 402 in and holding with an the inward pressure for an amount of time such as 1-3 seconds can be interpreted as another type of user input (also referred to as a “press and hold”). According to some further embodiments, other types of user input can be effectuated by a user such as double and/or multiple clicks, and pressing and holding for longer and/or shorter periods of time. According to other embodiments, speed-sensitive or acceleration-sensitive rotational inputs may also be implemented to create further types of user inputs (e.g., a very large and fast leftward rotation specifies an “Away” occupancy state, while a very large and fast rightward rotation specifies an “Occupied” occupancy state).
The embodiments described herein are advantageously configured to be compatible with a large variety of conventional integrated routers that service a large population of homes and businesses. Thus, by way of example only and not by way of limitation, the router (not shown) that services the private network 502 of
Thermostat access client 516 is a client application designed in accordance with aspects of the present invention to access the thermostat management system 506 over public network 504, which is a wide area network such as the Internet. Because thermostat access client 516 is designed to execute on different devices, multiple client applications may be developed using different technologies based on the requirements of the underlying device platform or operating system. In some cases, thermostat access client 516 may be implemented using a markup language such as HTML and related technologies displayed inside of a web-browser technology such as SAFARI®, FIREFOX®, or INTERNET EXPLORER®. In some embodiments, computer 512 may run thermostat access client 516 by navigating to a particular URL on the Internet and displaying web pages delivered from a web server hosted by thermostat management system 506.
In yet another embodiment, thermostat access client 516 may be a stand-alone application or “app” designed to be downloaded and run on a specific device such as smartphone 508 or a tablet 510 device running the Apple iOS operating system, Android operating system, or others. Developers create these stand-alone applications using a set of application programming interfaces (APIs) and libraries provided by the device manufacturer packaged in software development toolkit or SDK. Once completed, the “app” is made available for download to the respective device through an application store or “app” store curated by the app store owners to promote quality, usability and customer satisfaction.
In one embodiment, thermostat management system 506 illustrated in
Thermostat 110 and remote thermostat 112 may be accessed remotely from numerous different locations on the private network 502 or public network 504. As will be described in further detail hereinbelow, upon installation a thermostat such as thermostat 110 first registers with the thermostat management system 506 and then requests the thermostat management system create a pairing between the thermostat and a corresponding thermostat management account. Thereafter, a device such as a tablet 518 may be connected to public network 504 directly or through a series of other private networks (not shown) yet still access these thermostats, while outside the private network where they are located, by way of thermostat management system 520. In one embodiment, a tablet 518 running the Apple iOS operating system may remotely access to these thermostats through the thermostat management system 506 and thermostat management account using an iOS “app” version of thermostat access client 516. Pairing thermostats with the thermostat management account allows tablet 518 and other computer devices to remotely control, gather data, and generally interact with thermostats such as thermostat 110 and remote thermostat 112.
In one embodiment, thermostat management system 506 distributes the task of communication and control with the thermostats to one or more thermostat management servers 520. These thermostat management servers 520 may coordinate communication, manage access, process data and analyze results using data produced by thermostats such as thermostat 110 and remote thermostat 112. Intermediate and final results from computations on these servers 520, as well as raw data, may be stored temporarily or archived on thermostat databases 522 for future reference and use. Thermostat management servers 520 may also send a portion of the data along with control information, and more generally any of a variety of different kinds of information, back to thermostat 110 and remote thermostat 112. Results from the thermostat management servers 520 may also be stored in one or more thermostat databases 522 for subsequent access by a device such as tablet 518 running thermostat access client 516.
These thermostat management servers 520 each may perform one or several discrete functions, may serve as redundant fail-over servers for these different discrete functions or may share performance of certain discrete functions in tandem or in a cluster as well as other combinations performing more complex operations in parallel or distributed over one or more clusters of computers. In some embodiments, one of the thermostat management servers 520 may correspond directly to a physical computer or computing device while in other embodiments, the thermostat management servers 520 may be virtualized servers running on one or more physical computers under the control of a virtual machine computing environment such as provided by VMWARE of Palo Alto, Calif. or any other virtual machine provider. In yet another embodiment, the thermostat management servers 520 and thermostat databases 522 are provisioned from a “cloud” computing and storage environment such as the Elastic Compute Cloud or EC2 offering from Amazon.com of Seattle, Wash. In an EC2 solution, for example, the thermostat management servers 520 may be allocated according to processor cycles and storage requirements rather than according to a number of computers, either real or virtual, thought to be required for the task at hand.
In some embodiments, the thermostat management servers 520 making up this thermostat management system 506 may manage thermostats located in multiple enclosures across various geographic locations and time-zones. Each enclosure may use one or several thermostats in accordance with embodiments of the present invention to control one or several HVAC systems, such as HVAC system 120 in
One embodiment of registration server 602 provides a number of services related to registering a thermostat on the thermostat management system 506 and preparing it for pairing with a thermostat management account. In operation, the registration server 602 may be first accessed by a thermostat when the thermostat is wired to the HVAC of an enclosure and then connected to the Internet through a private network. To make the thermostat known on system 520, the thermostat sends thermostat metadata from the private network to the public network, such as the Internet, and then onto processing by registration server 602. Preferably, the thermostat metadata includes a unique thermostat identifier, such as one that is assigned at the time of manufacturing. As the communication that sends the thermostat metadata passes through the network address translator (NAT) of the router (not shown) that serves private network 502, it is appended with the public network address of that router, which is thus the public address that is “used” by the thermostat to communicate over the public network. The thermostat identifier is used to identify the thermostat from other thermostats being registered by registration server 602 and may be based, in part or in whole, on a media access control (MAC) address assigned to the NIC of the thermostat. As one security measure against registering unauthorized devices, registration server 602 may compare the MAC address in the thermostat metadata against a list of valid MAC addresses provided by the manufacturer of the thermostat or NIC component. In accordance with one embodiment, the thermostat registration is complete when the registration server 602 provisions an entry in a thermostat registration pool and marks the thermostat entry ready to be paired with a thermostat management account. Entries in the thermostat registration pool may be referenced by their unique thermostat identifier, the public network address that they used (or, more particularly, the public address of the private network router through which they connect to the Internet), and optionally other relevant metadata associated with the thermostat.
In some embodiments, update server 604 attempts to update software, firmware and configuration updates to each of the thermostats registered in the thermostat registration pool. If metadata from entries in the registration pool exclude versioning information, update server may need to further query each thermostat for current versions installed. Update server 604 may access entries in the registration pool and then use corresponding network addresses in each entry to connect to the associated thermostat over the public network or private network, or both.
If newer software versions exist than currently used on a thermostat, update server 604 proceeds to send software updates to the thermostat over the public network. For example, update server may use file transfer protocols such as ftp (file transfer protocol), tftp (trivial file transfer protocol) or more secure transfer protocols when uploading the new software. Once uploaded, installation and update of the software on the thermostat may occur immediately through an auto-update option on the thermostat or manually through the interface of the thermostat as requested by a user.
One embodiment of pairing server 606 facilitates the association or “pairing” of a thermostat with a thermostat management account on thermostat management account server 612. The term “thermostat management account” can be used interchangeably with “user account” herein unless specified otherwise. Once the thermostat is paired with a user account, a rich variety of network-enabled capabilities are enabled as described further herein and in one or more of the commonly assigned incorporated applications, supra. For example, once pairing has been achieved, a person with access to the thermostat management account may access the thermostat (through the thermostat management system 506 using the thermostat access client 516) for a variety of purposes such as seeing the current temperature of the home, changing the current setpoint, changing the mode of the thermostat between “home” and “away”, and so forth. Moreover, the thermostat management system 506 can then start tracking the various information provided by the thermostat which, in turn, enables a rich variety of cloud-based data aggregation and analysis that can be used to provide relevant reports, summaries, updates, and recommendations to the user either through the thermostat display itself, through the thermostat access client 516, or both. A variety of other capabilities, such as demand-response actions in which the thermostat management server sends an energy alert and/or sends energy-saving setpoint commands to the thermostats of users who have enrolled in such programs, can be carried out.
In view of the importance of establishing a pairing between the thermostat and a thermostat management account, there is provided an ability for a fallback method of pairing, which can be termed a “manually assisted” method of pairing, that can take effect and be carried out in the event that the convenient auto-pairing methods described further hereinbelow cannot be securely and reliably carried out for a particular installation. The manually assisted method, which is described further in relation to
According to a preferred “auto-pairing” method, the pairing server 606 may automatically pair or “auto-pair” a thermostat management account to a thermostat if both are located on the same private network. If the thermostat and thermostat management account are associated with the same private network, embodiments of the present invention presume the thermostat is at the user's home, office, or other area where the user should also have control of the device. To make this determination automatically, the pairing server 606 compares the public network address that was used to register the thermostat over the Internet with the public network address used by the computer device that has most recently been used to access the thermostat management account. Since the thermostat and computer device only have private network addresses, the router on the private network they share inserts the same public network address into their packets thus allowing the two devices to access servers, services, and other devices on the Internet. “Auto-pairing” takes advantage of this fact and automatically pairs devices sharing the same public network address. This is particularly advantageous from a user standpoint in that the user is not bothered with the need to enter a passcode or other alphanumerical identifier in order to achieve the pairing process, and avoids the concern that a user may inadvertently enter incorrect codes or identifiers into the system. Details on auto-pairing and manually assisted pairing are described in further detail later herein.
Thermostat front end user-interface (UI) server 608 facilitates the generation and presentation of intuitive, user-friendly graphical user-interfaces that allow users to remotely access, configure, interact with, and control one or more of their network-connected thermostats 110/112 from a computer web browser, smartphone, tablet, or other computing device. The user-friendly graphical user-interfaces can also provide useful tools and interfaces that do not necessarily require real-time connectivity with the thermostats 110/112 with examples including, for some embodiments, providing user interfaces for displaying historical energy usage, historical sensor readings and/or occupancy patterns, allowing the user to learn about and/or enroll in demand-response programs, provide social networking forums that allow users to interact with each other in informative, competitive, fun ways that promote energy savings, provide access to local information including weather, public safety information, neighborhood calendar events, and local blogs, and more generally provide services and information associated with a comprehensive “energy portal” functionality. Examples of intuitive, user-friendly graphical user-interfaces provided by the UI server 608 according to one or more preferred embodiments are described further infra with respect to
In some embodiments, a thermostat access client user-interface displays an image of a house representing a primary enclosure paired to the thermostat management account in the thermostat management system. Thermostat front end UI server 608 may further instruct the thermostat access client, such as thermostat access client 516 in
Thermostat backend server 610 manages the storage of data used by various thermostat management servers in the thermostat management system 506. In some embodiments, thermostat backend server 610 may manage storage of the thermostat registration pool data used by the registration server 602 or may organize and store new software updates and releases for the update server 604. In another embodiment, thermostat backend server 610 may also store heating and cooling related data (i.e., date and time HVAC system was in either heating or cooling mode within the enclosure), sensor information, battery-level data, alarms, etc. associated with an enclosure that was sent to the thermostat management system 506 by thermostats registered therewith, and in some embodiments and provide pre-computed heating and cooling schedules, applications, and other data for download over the public network for use by the thermostats.
In some embodiments, thermostat management account server 612 is used to create new accounts and update existing accounts on thermostat management system 506. To access their thermostat over a thermostat access client 516 and enjoy the benefits of thermostat connectedness, the user is first required to create of a thermostat management account (“user account”) on thermostat management account server 612 using their thermostat access client 516. Accordingly, users execute the thermostat access client 516 on a computer or other computer device to access the thermostat management account server 612. The thermostat management account server 612 should receive at least the zip code and/or city and state for the enclosure in which the thermostat is (or will be) installed, such that weather information provided by a weather service can be accessed and downloaded to the thermostat, which can be used as part of its optimal enclosure characterization and HVAC control algorithms. Optionally, a variety of other information including a user's contact information, enclosure street addresses, and so forth can also be received. Primary options associated with the thermostat management account server 612 include pairing one or more thermostats to the correct thermostat management account through pairing operations provided by pairing server 606. However, even if the account is not yet paired with a thermostat, the user may use the thermostat management account to access local information including weather, public safety information, neighborhood calendar events, local blogs and more information based upon the user's contact information, locale and other interests.
With network connectivity available (step 704—Yes), a user may first need to configure a network connection, preferably wireless, between the NIC associated with the thermostat and the private network in the enclosure (step 708). In some implementations, the thermostat may automatically suggest joining a wireless network with the strongest wireless signal as the signal strength is likely strongest from a network within the enclosure. For example, the thermostat may suggest joining the wireless network with the highest received signal strength indicator (RSSI). A user may confirm that the thermostat join the wireless network on the interface to the thermostat. In other implementations, the thermostat may display the SSIDs from nearby wireless networks on a display such as in display 306 in
Once connected to the private network, the thermostat transmits thermostat metadata information associated therewith, including its unique thermostat identifier, to the thermostat management system 506, this information being appended with the public network address of the private network router on its way therethrough and out to the thermostat management system 506 (step 710). Registration is carried out that makes information related to the thermostat available on the thermostat management system and is a precursor to pairing the thermostat with a thermostat management account. To complete the registration, a server associated with the thermostat management system such as registration server 602 may create a new entry in a thermostat registration pool with the aforementioned data and metadata associated with the thermostat held for later processing. Depending on the implementation, the thermostat may be able to receive software and firmware updates from the thermostat management system once it is registered with the system.
The cloud-based thermostat management system maintains a unique account identifier (such as an e-mail address) for each user account that has been created, and a unique thermostat identifier (such as a MAC address) for each thermostat unit that has been manufactured. The cloud-based thermostat management server keeps track, for each user account, of a public network address from which that user most recently accessed their user account on the cloud-based thermostat management server, such tracking being applicable for both previously established user accounts and newly established user accounts.
In some embodiments, a thermostat may have already been paired to a thermostat management account (step 712—Yes), which can be detected based on the unique thermostat identifier sent at step 710, and thus the pairing is already established (step 722). In some embodiments, the thermostat identifier, the MAC address assigned to the NIC for example, may be used to find an entry for the thermostat in the thermostat registration pool and then cross-referenced with a list of thermostat management accounts. Unless the initial pairing is deleted or removed, a thermostat paired with one account may not be available for pairing with another account. On the other hand, it is to be appreciated that a single thermostat management account can be paired with multiple different thermostat.
If the thermostat has not already been paired to a thermostat management account (step 712—No) (i.e., is a “pairing candidate thermostat”), then at step 714 the thermostat management server makes a determination whether the pairing candidate thermostat can be automatically associated with a thermostat management account, based on a comparison of (i) the public network address of the thermostat's private network router and (ii) the tracked public network addresses from which thermostat management account have recently been accessed. In the event there is such a match (step 716—Yes) between the public network address of the pairing candidate thermostat's private network router the public network address from which one user account has recently been accessed, than an automatic association is established, at least tentatively, between the unique thermostat identifier for that thermostat and the unique account identifier for that thermostat management account. Upon such positive match, however, it is preferable that at least one safeguard test (718) be made in which the thermostat management account identifier (e.g., the user's e-mail address) on the thermostat display screen (see
However, if no match is found at step 716, or if any of the safeguard tests (718, 720) are not satisfied, then it is required that a manually assisted pairing process take place (step 719) in order to have the pairing affirmatively established (step 722). Optionally, if no match is found at step 716, the user may be invited to establish and/or log into their thermostat management account, whereupon the steps 714-716 are then repeated to see if a match occurs.
For manually assisted pairing, the thermostat may receive from pairing server 606 a seven character alphanumeric passcode sequence to be displayed on the thermostat display, with one example being shown in
According to some embodiments, the predetermined safeguards carried out at step 720 can comprise the cancelation of any tentative pairing associations (i.e., requiring manual assistance) in any of the following cases: (i) two different user accounts have been logged into from the same public network address now being used by the thermostat's private network router within the past 24 hours (or other suitable time window), and (ii) there are two different pairing candidate thermostats simultaneously accessing the cloud-based thermostat management server from the same public network address.
The pairing server may receive a confirmation passcode from a thermostat management account requesting a pairing be made with the respective thermostat displaying the passcode. (804) If the server confirms a passcode match between the thermostat and the thermostat management account (806—Yes), the system pairs the thermostat to the thermostat management account. (808) If there is not a passcode match, some embodiments may submit a notification to the thermostat management account that the passcode provided does not match the registered thermostat in the thermostat management system. (810) For example, this might occur if the passcode has been entered into the account incorrectly. It may also occur if the passcode has been displayed on the thermostat display beyond a predetermined time interval, such as 3 hours, and has timed-out or been removed from the system.
As illustrated in this schematic, thermostat registration pool 910 includes a list of all currently registered thermostats in the system having thermostat identifiers 18:B4:30:01:63:E1, 18:B4:30:01:63:E7, 18:B4:30:01:63:E3, and 18:B4:30:01:63:E9, and corresponding public network addresses or public addresses 75.52.8.12, 75.22.4.21, 68.21.4.12, and 68.21.4.15. A confirm field in the thermostat registration pool 910 with a “Yes” entry indicates that thermostats 18:B4:30:01:63:E1, 18:B4:30:01:63:E7, and 18:B4:30:01:63:E3 have been affirmatively paired with accounts bob123@gmail.com and matt@gunn.com, respectively, from thermostat management accounts 912, these pairings being indicated by the arrowed lines between the tables 910 and 912 in
In
The schematic in
To help ensure the thermostat is paired with the right account, some embodiments may include one or several additional confirmation operations for safeguarding purposes. In some embodiments, a thermostat frontend UI server 608 (see
If the user does not cancel the pairing, one embodiment as illustrated in the dialog 924 in
In some embodiments, confirmation dialog 934 helps ensure pairing server 908 does not automatically pair a thermostat to a thermostat management account until a user authorizes it. In other embodiments, the confirmation may also be used to limit accidentally autopairing a thermostat to the wrong thermostat management account if multiple users are on the same private network. For example, a retail store or coffee shop may try to pair a thermostat using a shread private network with multiple customers who are also accessing their thermostat management accounts. If this latter condition occurs, the thermostat management table such as thermostat management table in
Embodiments of the present invention further receive a public network address associated with the thermostat management account provided by a router on a private network. (938) As previously described, devices on a private network generally share a public network address with the router providing the private network with access to the public network such as the Internet. The router device on the private network use the NAT table entries to bridge between addresses used on private and public networks. One embodiment stores the public network address associated with the computer device accessing the thermostat management account in a thermostat management account table 913 in
In another embodiment, the pairing server retrieves thermostat metadata including a public network address from a registration of the thermostat with the thermostat management system. (942) In some embodiments, a thermostat attached to a private network initially requests access and registration on the thermostat management system to obtain data, updates, and eventually pairing with a thermostat management account. During the registration, the thermostat may provides thermostat metadata information to be entered in a thermostat registration pool, such as thermostat registration pool 910. This thermostat metadata information includes a public network address and thermostat identifier in one embodiment. At the time of registration, the public network address is provided by the router on the private network where the thermostat is located. In one embodiment, autopairing relies on the same public network address used by the thermostat being shared by the router with computer devices, thermostats and other services on the private network.
Embodiments of the present invention determines whether the public network address associated with the thermostat management account is the same as the public network address associated with the thermostat. (944) As previously described, the public network addresses should match if the computer device that accessed the thermostat management account is on the same private network as the thermostat. However, if the public network address for the thermostat and thermostat management account are different, (944—No) an alternate approach to pairing the thermostat management account with a thermostat may be necessary. (952)
Embodiments of the present invention presume that the thermostat management account is accessed from the same private network where the thermostat is located. As an added measure of authorization, one embodiment requests a confirmation to pair the thermostat and thermostat management account through a dialog displayed on the thermostat. (946) The confirmation may request a user setting up the thermostat to operate the interface on the thermostat and confirm a pairing with a particular thermostat management account. As an example, the thermostat 932 in
In combining these elements together, embodiments of the present invention provide an inviting and intuitive interface for accessing, programming and controlling one or more thermostats associated with and installed in one or several enclosures. Additionally, the elements of the user interface further provide access to related information of weather, data, local community information, energy saving information, emergency response information, and other data as it relates to each of one or more enclosures associated with a user's thermostat management account. In some embodiments, account name 1002 provides the name of the thermostat management account currently using the thermostat access client as illustrated in
Since primary enclosure selection 1018 is identified by focus indicator 1022, background area 1008 of the user interface displays a primary visual weather 1010 representing a current weather in the vicinity of the primary enclosure associated with primary enclosure selection 1018. Some embodiments of primary visual weather 1010 may animate various weather image elements representing clouds, rain, snow and other weather conditions to further emphasize the weather pattern at the primary enclosure. Time of day may also be reflected by the lightness or darkness of images in primary visual weather 1010 depending on the time zone associated with the location of the primary enclosure, which in this case appears to be daytime as reflected in primary visual weather 1010 in
An away indicator 1019 appears as different colors in a window 1017 of the house image of primary enclosure selection 1018 and in the width of the outline of the inverted “U” shaped door-like image along the front of the house image. For example, a color in the window and door appearing as a golden yellow color may indicate that someone is presently occupying the house or office but if the color turns dark or black then it shows that the house or office is unoccupied.
In some embodiments, the primary enclosure selection 1018 also displays a thermostat selection 1016 for each of the thermostats used within the actual primary enclosure. It appears that the primary enclosure selection 1018 with the label “HOME” in this example represents a primary residence or home having only one thermostat as represented by thermostat selection 1016 displayed in the foreground area 1014. Upon selecting thermostat selection 1016 in some embodiments, focus indicator 1022 slides under thermostat selection 1016 and the user interface presents another portion of the interface for setting up heating and cooling setpoints according to a schedule.
Once a primary enclosure is selected, the user interface of the thermostat access client displays the primary enclosure selection and associated thermostat selections (1034). In some embodiments, the individual thermostat selection may show a corresponding temperature inside or near the primary enclosure. Both the primary enclosure selection and corresponding thermostat selections appear in a foreground area of the user interface as it is displayed on a display device. For example, the primary enclosure selection may appear as an image of a house as illustrated by primary enclosure selection 1018 appearing in foreground area 1014 in
The user interface of the thermostat access client further displays a primary visual weather and an approximate time of day at a geographic location of the primary enclosure. (1036) In one embodiment, this primary visual weather may be displayed like primary visual weather 1010 in
If just one enclosure is paired to the thermostat management account, (1038—No), the user interface continues to display the just primary enclosure selection as previously described. (1034) In alternate embodiments, a secondary enclosure paired to the thermostat management account (1038—Yes) is displayed as a secondary enclosure selection in accordance with further embodiments of the user interface. The secondary enclosure selection is visually deemphasized and appears smaller when compared with the primary enclosure selection. To further deemphasize, the secondary enclosure selection may also be placed in the foreground area but appear behind the primary enclosure selection. Like the primary enclosure selection, secondary enclosure selection may look like a house such as depicted by secondary enclosure selection 1020 appearing in foreground area 1014 in
When no selections are made, (1042—No) embodiments of the user interface continues to display the same primary enclosure selection as previously described (1034). In alternate embodiments, the user interface may receive a selection of the secondary enclosure selection thereby causing a change in the primary and secondary enclosures represented by the user interface. (1042—Yes) For example, a user's selection of the secondary enclosure selection causes the secondary enclosure to assume the role of the primary enclosure and then become displayed as the primary enclosure selection on the user interface. In turn, the previous primary enclosure assumes the role of the secondary enclosure and is displayed as the second enclosure selection, visually deemphasized on the user interface. (1044) To illustrate an example of this user interface interaction,
In accordance with the present invention,
In accordance with other embodiments, thermostat dialog 1110 available under settings 1106 in
Example setpoints 1212 and 1214 added to the selectable horizontal bar 1210 can be readily understood thereby simplifying the overall scheduling of the thermostat. For example, a cooling setpoint 1212 of “79” degrees placed at the “8:00” location on the selectable horizontal bar 1210 should cause the HVAC to turn on the air conditioner and “cool” if the temperature exceeds the “79” degree temperature after “8:00”. The subsequent cooling setpoint 1214 of “80” degrees at “9:00” should cause the HVAC to turn on the air conditioner and “cool” only if the temperature then exceeds “80” degrees after “9:00”.
In accordance with another embodiment,
Based on the identified enclosure, one embodiment may then display a heating and cooling schedule for the thermostat on the user interface of the computer device as one or more vertically stacked horizontal bars corresponding to one or more days in the heating and cooling schedule for the thermostat. (1204) Each horizontal bar includes a range of time in one day measured along a horizontal direction of each horizontal bar in the schedule. For example, a horizontal bar at the left most range may start a day at 12:00 midnight or 00:00 on a 24 hour schedule and run to the right until the schedule ends at 11:59 pm or 23:59.
The interface also displays a setpoint selection as a geometric shape located on one of the one or more vertically stacked horizontal bars (1206). In embodiment, the setpoint selection has at least one temperature threshold indicated by a value displayed in the center of the geometric shape. Preferably, the geometric shape is a round circle or concentric circles however other shapes may also be used. For example, a single value such as 70 may indicate a 70 degree threshold while two values such as 62/76 indicates a range associated with the setpoint selection. Depending on the color or colors, one embodiment of the setpoint selection indicates a thermal preference for operating an HVAC system. For example, a “red” colored geometric shape may indicate to heat until the temperature threshold associated with the setpoint selection is reached. Two colors such as “red” and “black” coupled with two threshold levels, such as 62/76 may indicate to heat until a lower threshold of 62 is met and then cool if an upper threshold amount 76 is exceeded.
In a further aspect of the user interface, the schedule for heating and cooling may receive a selection on one of the several horizontal bar to interact with one or more setpoint selections at a particular time interval. (1208) For example, the selection may be from a mouse or other pointing device indicating a selection on the screen of a computer running a thermostat access client and user interface in accordance with the present invention. One embodiment determines if the time interval selected on the horizontal bar already has a setpoint selection. (1210) If no setpoint selection exists at the time interval (1210—No), the selection by the pointing device may indicate to add a setpoint at the time interval of the one horizontal bar. (1212) The setpoint selection added may indicate either heating, cooling or both and may also specify one or two thresholds for operating the setpoint. A thermal preference for cooling may be indicated by making the geometric shape “blue” while a thermal preference for heating may be indicated with a geometric shape that is “red”.
Alternatively, if a setpoint exists at the time interval (1210—Yes), the selection by the pointing device may further indicate to delete the setpoint through an additional indication. (1214—Yes) For example, a right click or double-click of a mouse within the thermostat access client in the user interface could indicate that a particular existing setpoint at a time interval on one horizontal bar should be deleted. (1216) However, if the pointing device does not indicate to delete the setpoint (1214—No), the selection by the pointing device may instead be used to modify the setpoint along the horizontal bar. For example, the user interface may be used to modify the temperature threshold, time interval, or thermal preference for the set point at the particular time interval and day in the schedule. (1218)
Accordingly, various modifications may be made without departing from the spirit and scope of the invention. Indeed, various user interfaces for operating thermostats, HVACSs and other devices have been provided yet the designs are meant to be illustrative and not limiting as to the scope of the overall invention. While methods and systems have been described for pairing thermostats using autopairing and passcode pairing, it is contemplated that these methods and system may be applied to any device on a private network attempting to pair with an account. For example, embodiments of the present invention are not limited to network attached thermostats but any device connected to a network such as set-top boxes, streaming server devices, streaming service applications, computers, mobile phones, voice-over-IP phones, or anything that might benefit from an autopairing function in accordance with embodiments of the present invention. In the case of user interfaces, numerous flowcharts have been provided representing the operation of these user interfaces yet it is contemplated that the steps presented in association with these interfaces may be interchanged, reordered and mixed and remain within the scope of aspects of the present invention. It is to be further appreciated that the term thermostat, as used hereinabove and hereinbelow, can include thermostats having direct control wires to an HVAC system, and can further include thermostats that do not connect directly with the HVAC system, but that sense an ambient temperature at one location in an enclosure and cooperatively communicate by wired or wireless data connections with a separate thermostat unit located elsewhere in the enclosure, wherein the separate thermostat unit does have direct control wires to the HVAC system. Accordingly, the invention is not limited to the above-described embodiments, but instead is defined by the appended claims in light of their full scope of equivalents.
This patent application is a continuation of U.S. patent application Ser. No. 14/984,876 filed on Dec. 30, 2015, which is a continuation of U.S. patent application Ser. No. 14/469,577 filed on Aug. 26, 2014, which is a continuation of U.S. patent application Ser. No. 13/275,311 filed Oct. 17, 2011. Each of these applications is incorporated herein by reference. The subject matter of this patent specification relates to the subject matter of the following commonly assigned applications: U.S. Ser. No. 12/881,430 filed Sep. 14, 2010; U.S. Ser. No. 12/881,463 filed Sep. 14, 2010; U.S. Ser. No. 61/415,771 filed Nov. 19, 2010; U.S. Ser. No. 61/429,093 filed Dec. 31, 2010; U.S. Ser. No. 12/984,602 filed Jan. 4, 2011; U.S. Ser. No. 12/987,257 filed Jan. 10, 2011; U.S. Ser. No. 13/033,573 filed Feb. 23, 2011; U.S. Ser. No. 29/386,021, filed Feb. 23, 2011; U.S. Ser. No. 13/034,666, U.S. Ser. No. 13/034,674 and U.S. Ser. No. 13/034,678 filed Feb. 24, 2011; U.S. Ser. No. 13/038,191 filed Mar. 1, 2011; U.S. Ser. No. 13/038,206 filed Mar. 1, 2011; U.S. Ser. No. 29/399,609 filed Aug. 16, 2011; U.S. Ser. No. 29/399,614 filed Aug. 16, 2011; U.S. Ser. No. 29/399,617 filed Aug. 16, 2011; U.S. Ser. No. 29/399,618 filed Aug. 16, 2011; U.S. Ser. No. 29/399,621 filed Aug. 16, 2011; U.S. Ser. No. 29/399,623 filed Aug. 16, 2011; U.S. Ser. No. 29/399,625 filed Aug. 16, 2011; U.S. Ser. No. 29/399,627 filed Aug. 16, 2011; U.S. Ser. No. 29/399,630 filed Aug. 16, 2011; U.S. Ser. No. 29/399,632 filed Aug. 16, 2011; U.S. Ser. No. 29/399,633 filed Aug. 16, 2011; U.S. Ser. No. 29/399,636 filed Aug. 16, 2011; U.S. Ser. No. 29/399,637 filed Aug. 16, 2011; U.S. Ser. No. 13/199,108, filed Aug. 17, 2011; U.S. Ser. No. 13/267,871 filed Oct. 6, 2011; U.S. Ser. No. 13/267,877 filed Oct. 6, 2011; U.S. Ser. No. 13/269,501 filed Oct. 7, 2011; U.S. Ser. No. 29/404,096 filed Oct. 14, 2011; U.S. Ser. No. 29/404,097 filed Oct. 14, 2011; U.S. Ser. No. 29/404,098 filed Oct. 14, 2011; U.S. Ser. No. 29/404,099 filed Oct. 14, 2011; U.S. Ser. No. 29/404,101 filed Oct. 14, 2011; U.S. Ser. No. 29/404,103 filed Oct. 14, 2011; U.S. Ser. No. 29/404,104 filed Oct. 14, 2011; U.S. Ser. No. 29/404,105 filed Oct. 14, 2011; U.S. Ser. No. 13/275,311 filed Oct. 17, 2011; and U.S. Ser. No. 13/275,307 filed Oct. 17, 2011.
| Number | Name | Date | Kind |
|---|---|---|---|
| 4276925 | Palmieri | Jul 1981 | A |
| 4316577 | Adams et al. | Feb 1982 | A |
| 4460125 | Barker et al. | Jul 1984 | A |
| 4751961 | Levine et al. | Jun 1988 | A |
| 4768706 | Parfitt | Sep 1988 | A |
| 5005365 | Lynch | Apr 1991 | A |
| 5224648 | Simon et al. | Jul 1993 | A |
| 5261481 | Baldwin et al. | Nov 1993 | A |
| 5294047 | Schwer et al. | Mar 1994 | A |
| 5395042 | Riley et al. | Mar 1995 | A |
| 5415346 | Bishop | May 1995 | A |
| 5460327 | Hill et al. | Oct 1995 | A |
| 5482209 | Cochran et al. | Jan 1996 | A |
| 5485954 | Guy et al. | Jan 1996 | A |
| 5555927 | Shah | Sep 1996 | A |
| 5566879 | Longtin | Oct 1996 | A |
| 5603451 | Helander et al. | Feb 1997 | A |
| 5627531 | Posso et al. | May 1997 | A |
| 5673850 | Uptegraph | Oct 1997 | A |
| 5808602 | Sellers | Sep 1998 | A |
| 5931378 | Schramm | Aug 1999 | A |
| 5973662 | Singers et al. | Oct 1999 | A |
| 6020881 | Naughton et al. | Feb 2000 | A |
| 6032867 | Dushane et al. | Mar 2000 | A |
| 6098893 | Berglund et al. | Aug 2000 | A |
| 6122603 | Budike, Jr. | Sep 2000 | A |
| 6164374 | Rhodes et al. | Dec 2000 | A |
| 6206295 | LaCoste | Mar 2001 | B1 |
| 6213404 | Dushane et al. | Apr 2001 | B1 |
| 6286764 | Garvey et al. | Sep 2001 | B1 |
| 6298285 | Addink et al. | Oct 2001 | B1 |
| 6453687 | Sharood et al. | Sep 2002 | B2 |
| 6502758 | Cottrell | Jan 2003 | B2 |
| 6513723 | Mueller et al. | Feb 2003 | B1 |
| 6519509 | Nierlich et al. | Feb 2003 | B1 |
| D471825 | Peabody | Mar 2003 | S |
| 6619055 | Addy | Sep 2003 | B1 |
| 6622925 | Carner et al. | Sep 2003 | B2 |
| 6644557 | Jacobs | Nov 2003 | B1 |
| 6789739 | Rosen | Sep 2004 | B2 |
| 6798341 | Eckel et al. | Sep 2004 | B1 |
| 6851621 | Wacker et al. | Feb 2005 | B1 |
| D503631 | Peabody | Apr 2005 | S |
| 6891838 | Petite et al. | May 2005 | B1 |
| 6909921 | Bilger | Jun 2005 | B1 |
| 6951306 | DeLuca | Oct 2005 | B2 |
| 7000849 | Ashworth et al. | Feb 2006 | B2 |
| 7038667 | Vassallo et al. | May 2006 | B1 |
| 7055759 | Wacker et al. | Jun 2006 | B2 |
| 7083109 | Pouchak | Aug 2006 | B2 |
| 7108194 | Hankins, II | Sep 2006 | B1 |
| 7114554 | Bergman et al. | Oct 2006 | B2 |
| 7135965 | Chapman, Jr. et al. | Nov 2006 | B2 |
| 7141748 | Tanaka et al. | Nov 2006 | B2 |
| 7159790 | Schwendinger et al. | Jan 2007 | B2 |
| 7222800 | Wruck | May 2007 | B2 |
| 7258280 | Wolfson | Aug 2007 | B2 |
| 7264175 | Schwendinger et al. | Sep 2007 | B2 |
| 7287709 | Proffitt et al. | Oct 2007 | B2 |
| 7289887 | Rodgers | Oct 2007 | B2 |
| 7299996 | Garrett et al. | Nov 2007 | B2 |
| 7333880 | Brewster et al. | Feb 2008 | B2 |
| D566587 | Rosen | Apr 2008 | S |
| 7427926 | Sinclair et al. | Sep 2008 | B2 |
| 7434742 | Mueller et al. | Oct 2008 | B2 |
| 7451937 | Flood et al. | Nov 2008 | B2 |
| 7455240 | Chapman, Jr. et al. | Nov 2008 | B2 |
| 7460690 | Cohen et al. | Dec 2008 | B2 |
| 7469550 | Chapman, Jr. et al. | Dec 2008 | B2 |
| 7509753 | Nicosia et al. | Mar 2009 | B2 |
| 7537171 | Mueller et al. | May 2009 | B2 |
| 7555364 | Poth et al. | Jun 2009 | B2 |
| 7558648 | Hoglund et al. | Jul 2009 | B2 |
| 7565813 | Pouchak | Jul 2009 | B2 |
| 7571865 | Nicodem et al. | Aug 2009 | B2 |
| 7575179 | Morrow et al. | Aug 2009 | B2 |
| 7584899 | de Pauw et al. | Sep 2009 | B2 |
| 7600694 | Helt et al. | Oct 2009 | B2 |
| D603277 | Clausen et al. | Nov 2009 | S |
| 7624931 | Chapman, Jr. et al. | Dec 2009 | B2 |
| 7634504 | Amundson | Dec 2009 | B2 |
| 7641126 | Schultz et al. | Jan 2010 | B2 |
| 7693582 | Bergman et al. | Apr 2010 | B2 |
| 7702424 | Cannon et al. | Apr 2010 | B2 |
| 7703694 | Mueller et al. | Apr 2010 | B2 |
| D614976 | Skafdrup et al. | May 2010 | S |
| 7726581 | Naujok et al. | Jun 2010 | B2 |
| 7845576 | Siddaramanna et al. | Dec 2010 | B2 |
| 7890195 | Bergman et al. | Feb 2011 | B2 |
| 7900849 | Barton et al. | Mar 2011 | B2 |
| 7904209 | Podgorny et al. | Mar 2011 | B2 |
| 7904830 | Hoglund et al. | Mar 2011 | B2 |
| 8037022 | Rahman et al. | Oct 2011 | B2 |
| D651529 | Mongell et al. | Jan 2012 | S |
| 8131207 | Hwang et al. | Mar 2012 | B2 |
| D660732 | Bould et al. | May 2012 | S |
| 8195313 | Fadell et al. | Jun 2012 | B1 |
| 8196185 | Geadelmann et al. | Jun 2012 | B2 |
| 8239922 | Sullivan et al. | Aug 2012 | B2 |
| 8280536 | Fadell et al. | Oct 2012 | B1 |
| D677180 | Plitkins et al. | Mar 2013 | S |
| 8442695 | Imes et al. | May 2013 | B2 |
| D687043 | Matas et al. | Jul 2013 | S |
| D687044 | Ruff et al. | Jul 2013 | S |
| D687045 | Plitkins et al. | Jul 2013 | S |
| D687046 | Plitkins et al. | Jul 2013 | S |
| D687047 | Hales et al. | Jul 2013 | S |
| D687050 | Matas et al. | Jul 2013 | S |
| D687056 | Matas et al. | Jul 2013 | S |
| D687057 | Plitkins et al. | Jul 2013 | S |
| D687058 | Corcoran et al. | Jul 2013 | S |
| D687059 | Bruck et al. | Jul 2013 | S |
| 8478447 | Fadell et al. | Jul 2013 | B2 |
| D687459 | Sloo et al. | Aug 2013 | S |
| D687851 | Sloo et al. | Aug 2013 | S |
| 8510255 | Fadell et al. | Aug 2013 | B2 |
| D690322 | Matas et al. | Sep 2013 | S |
| D691629 | Matas et al. | Oct 2013 | S |
| 8550368 | Butler et al. | Oct 2013 | B2 |
| D696677 | Corcoran et al. | Dec 2013 | S |
| 8606374 | Fadell et al. | Dec 2013 | B2 |
| D697526 | Bruck et al. | Jan 2014 | S |
| D697930 | Crabtree et al. | Jan 2014 | S |
| D697960 | Crabtree et al. | Jan 2014 | S |
| D701515 | Matas et al. | Mar 2014 | S |
| D701869 | Matas et al. | Apr 2014 | S |
| 8727611 | Huppi et al. | May 2014 | B2 |
| 8752771 | Warren et al. | Jun 2014 | B2 |
| 8757507 | Fadell et al. | Jun 2014 | B2 |
| D711916 | Matas et al. | Aug 2014 | S |
| 8843239 | Mighdoll et al. | Sep 2014 | B2 |
| 8918219 | Sloo et al. | Dec 2014 | B2 |
| 9026254 | Warren et al. | May 2015 | B2 |
| 9092040 | Fadell et al. | Jul 2015 | B2 |
| 9089279 | Mucignat et al. | Aug 2015 | B2 |
| 9104211 | Fadell et al. | Aug 2015 | B2 |
| 9223323 | Matas et al. | Dec 2015 | B2 |
| 9261287 | Warren et al. | Feb 2016 | B2 |
| 9279595 | Mighdoll | Mar 2016 | B2 |
| 9494332 | Filson et al. | Nov 2016 | B2 |
| 9605858 | Warren et al. | Mar 2017 | B2 |
| 10142421 | Mighdoll et al. | Nov 2018 | B2 |
| 20020005435 | Cottrell | Jan 2002 | A1 |
| 20030034898 | Shamoon et al. | Feb 2003 | A1 |
| 20030040279 | Ballweg | Feb 2003 | A1 |
| 20030112262 | Adatia et al. | Jun 2003 | A1 |
| 20030150927 | Rosen | Aug 2003 | A1 |
| 20030231001 | Bruning | Dec 2003 | A1 |
| 20030233454 | Alkhatib et al. | Dec 2003 | A1 |
| 20040034484 | Solomita, Jr. et al. | Feb 2004 | A1 |
| 20040095237 | Chen et al. | May 2004 | A1 |
| 20040256472 | DeLuca | Dec 2004 | A1 |
| 20050043907 | Eckel et al. | Feb 2005 | A1 |
| 20050053063 | Madhavan | Mar 2005 | A1 |
| 20050055432 | Rodgers | Mar 2005 | A1 |
| 20050090915 | Geiwitz | Apr 2005 | A1 |
| 20050119793 | Amundson et al. | Jun 2005 | A1 |
| 20050159847 | Shah et al. | Jul 2005 | A1 |
| 20050194456 | Tessier et al. | Sep 2005 | A1 |
| 20050204997 | Fournier | Sep 2005 | A1 |
| 20060147003 | Archacki et al. | Jul 2006 | A1 |
| 20060206220 | Amundson | Sep 2006 | A1 |
| 20070001830 | Dagci et al. | Jan 2007 | A1 |
| 20070012052 | Butler et al. | Jan 2007 | A1 |
| 20070022469 | Cooper et al. | Jan 2007 | A1 |
| 20070045430 | Chapman et al. | Mar 2007 | A1 |
| 20070045433 | Chapman et al. | Mar 2007 | A1 |
| 20070045444 | Gray et al. | Mar 2007 | A1 |
| 20070050732 | Chapman et al. | Mar 2007 | A1 |
| 20070084941 | de Paul et al. | Apr 2007 | A1 |
| 20070114295 | Jenkins | May 2007 | A1 |
| 20070115902 | Shamoon et al. | May 2007 | A1 |
| 20070158442 | Chapman et al. | Jul 2007 | A1 |
| 20070173978 | Fein et al. | Jul 2007 | A1 |
| 20070225867 | Moorer et al. | Sep 2007 | A1 |
| 20070227721 | Springer et al. | Oct 2007 | A1 |
| 20070228183 | Kennedy et al. | Oct 2007 | A1 |
| 20070241203 | Wagner et al. | Oct 2007 | A1 |
| 20070257120 | Chapman et al. | Nov 2007 | A1 |
| 20080015742 | Kulyk et al. | Jan 2008 | A1 |
| 20080048046 | Wagner et al. | Feb 2008 | A1 |
| 20080054082 | Evans et al. | Mar 2008 | A1 |
| 20080099568 | Nicodem et al. | May 2008 | A1 |
| 20080215240 | Howard et al. | Sep 2008 | A1 |
| 20080221737 | Josephson et al. | Sep 2008 | A1 |
| 20080245480 | Knight et al. | Oct 2008 | A1 |
| 20080290183 | Laberge et al. | Nov 2008 | A1 |
| 20090001180 | Siddaramanna et al. | Jan 2009 | A1 |
| 20090057424 | Sullivan et al. | Mar 2009 | A1 |
| 20090057425 | Sullivan et al. | Mar 2009 | A1 |
| 20090057426 | Sullivan et al. | Mar 2009 | A1 |
| 20090057427 | Geadelmann et al. | Mar 2009 | A1 |
| 20090057428 | Geadelmann et al. | Mar 2009 | A1 |
| 20090062964 | Sullivan et al. | Mar 2009 | A1 |
| 20090140056 | Leen | Jun 2009 | A1 |
| 20090140057 | Leen | Jun 2009 | A1 |
| 20090140060 | Stoner et al. | Jun 2009 | A1 |
| 20090140064 | Schultz et al. | Jun 2009 | A1 |
| 20090143916 | Boll et al. | Jun 2009 | A1 |
| 20090194601 | Flohr | Aug 2009 | A1 |
| 20090261174 | Butler et al. | Oct 2009 | A1 |
| 20090283603 | Peterson et al. | Nov 2009 | A1 |
| 20100023865 | Fulker | Jan 2010 | A1 |
| 20100058450 | Fein et al. | Mar 2010 | A1 |
| 20100063832 | Brown | Mar 2010 | A1 |
| 20100084482 | Kennedy et al. | Apr 2010 | A1 |
| 20100125652 | Rantapuska et al. | May 2010 | A1 |
| 20100163633 | Barrett et al. | Jul 2010 | A1 |
| 20100168924 | Tessier et al. | Jul 2010 | A1 |
| 20100198425 | Donovan | Aug 2010 | A1 |
| 20100211224 | Keeling et al. | Aug 2010 | A1 |
| 20100235004 | Thind | Sep 2010 | A1 |
| 20100243231 | Rosen | Sep 2010 | A1 |
| 20100273610 | Johnson | Oct 2010 | A1 |
| 20100289643 | Trundle et al. | Nov 2010 | A1 |
| 20100318227 | Steinberg et al. | Dec 2010 | A1 |
| 20110001812 | Kang et al. | Jan 2011 | A1 |
| 20110015797 | Gilstrap | Jan 2011 | A1 |
| 20110015798 | Golden et al. | Jan 2011 | A1 |
| 20110015802 | Imes | Jan 2011 | A1 |
| 20110022242 | Bukhin et al. | Jan 2011 | A1 |
| 20110029488 | Fuerst et al. | Feb 2011 | A1 |
| 20110046806 | Nagel et al. | Feb 2011 | A1 |
| 20110054710 | Imes et al. | Mar 2011 | A1 |
| 20110077758 | Tran et al. | Mar 2011 | A1 |
| 20110078675 | Van Camp et al. | Mar 2011 | A1 |
| 20110151837 | Winbush, III | Jun 2011 | A1 |
| 20110282937 | Deshpande et al. | Nov 2011 | A1 |
| 20120005590 | Lombard et al. | Jan 2012 | A1 |
| 20120101637 | Imes et al. | Apr 2012 | A1 |
| 20120126020 | Filson et al. | May 2012 | A1 |
| 20120126021 | Warren et al. | May 2012 | A1 |
| 20120130546 | Matas et al. | May 2012 | A1 |
| 20120233478 | Mucignat et al. | Sep 2012 | A1 |
| 20120252430 | Imes et al. | Oct 2012 | A1 |
| 20120291068 | Khushoo | Nov 2012 | A1 |
| Number | Date | Country |
|---|---|---|
| 135487 | Jun 2002 | CN |
| 1354847 | Jun 2002 | CN |
| 101313262 | Nov 2008 | CN |
| 101467131 | Jun 2009 | CN |
| 19609390.2 | Sep 1997 | DE |
| 0434926 | Jul 1991 | EP |
| 0720077 | Jul 1996 | EP |
| 0802471 | Oct 1997 | EP |
| 1065079 | Jan 2001 | EP |
| 1731984 | Dec 2006 | EP |
| 2157492 | Feb 2010 | EP |
| 2212317 | May 1992 | GB |
| S59106311 | Jun 1984 | JP |
| H02-12508 | Jan 1990 | JP |
| 09298780 | Nov 1997 | JP |
| H10-023565 | Jan 1998 | JP |
| 2002087050 | Mar 2002 | JP |
| 2003054290 | Feb 2003 | JP |
| 2007-053639 | Jan 2007 | JP |
| 2009-164689 | Jul 2009 | JP |
| 2010-034853 | Feb 2010 | JP |
| 2014-507018 | Mar 2014 | JP |
| 1024986 | Jun 2005 | NL |
| 248851 | Jun 2002 | WO |
| 2008054938 | May 2008 | WO |
| 2009073496 | Jun 2009 | WO |
| 2011128416 | Oct 2011 | WO |
| Entry |
|---|
| Office Action dated Aug. 20, 2019 in Canadian Patent Application No. 2,852,902, all pages. |
| Japanese Office Action dated Nov. 25, 2014, for Japanese Patent Application No. 2014-537103 filed on Oct. 5, 2012, all pages. |
| Chinese Office Action dated Dec. 17, 2014, for Chinese Patent Application No. 201280050837.6 filed on Oct. 5, 2012, all pages. |
| International Search Report and Written Opinion dated Jan. 22, 2013 for International Patent Application No. PCT/US2012/059116 filed Oct. 5, 2012, all pages. |
| International Preliminary Report on Patentability dated May 1, 2014 for International Patent Application No. PCT/US2012/059116 filed Oct. 5, 2012, all pages. |
| Notice of Publication dated Jul. 2, 2014 in Chinese Patent Application No. 201280050837.6, all pages. |
| Office action dated Dec. 17, 2014 in Chinese Patent Application No. 201280050837.6, all pages. |
| Notice of Decision to Grant dated Apr. 15, 2016 in Chinese Patent Application No. 201280050837.6, all pages. |
| Notice of Allowance dated Mar. 23, 2015 in Japanese Patent Application No. 2014-537103, all pages. |
| Office action dated Aug. 17, 2018 in Canadian Patent Application No. 2,852,902, all pages. |
| Office action dated Oct. 23, 2015 in European Patent Application No. 12841021.4, all pages. |
| Notice of Publication dated Nov. 2, 2016 in Chinese Patent Application No. 201610509236.7, all pages. |
| Office action dated Aug. 18, 2017 in Chinese Patent Application No. 201610509236.7, all pages. |
| Notice of Decision to Grant dated Aug. 2, 2018 in Chinese Patent Application No. 201610509236.7, all pages. |
| Office action dated Apr. 10, 2018 in Chinese Patent Application No. 201610509236.7, all pages. |
| Extended European Search Report dated Sep. 29, 2016 in European Patent Application No. 16182356.2, all pages. |
| Notice of Publication dated Dec. 14, 2016 in European Patent Application No. 16182356.2, all pages. |
| Digi X-Grid Device Partners Developer's Guide, Digi International, [retrieved on Nov. 6, 2012]. Retrieved from the Internet: <URL: https://doc-0g-94-docsviewer.googleusercontent.com/viewer/securedownload/dsn1aovipa7I846Isfcf94nedj8q2p4u/e99579ivh1m690fr43qed9d370c1a0n5/1354725000000/Ymw=/AGZ5hq8Bjb>, Oct. 18, 2010, 12 pages. |
| Energy Joule, Ambient Devices, Jul. 23, 2011, [retrieved on Aug. 1, 2012]. Retrieved from: http://web.archive.org/web/20110723210421/http://www.ambientdevices.com/products/energyjoule.html, all pages. |
| Honeywell CT2700, An Electronic Round Programmable Thermostat—User's Guide, Honeywell, Inc., 1997, all pages. |
| Honeywell CT8775A,C, The digital Round Non-Programmable Thermostats—Owner's Guide, Honeywell International Inc., 2003, all pages. |
| Honeywell T8700C, An Electronic Round Programmable Thermostat—Owner's Guide, Honeywell, Inc., 1997, all pages. |
| Honeywell T8775, The Digital Round Thermostat, Honeywell, 2003, 2 pages. |
| Honeywell T8775AC Digital Round Thermostat Non-Programmable Thermostats Owner's Guide, Manual No. 69-1679EF-1, www.honeywell.com/yourhome, Jun. 2004, pp. 1-16. |
| ICY 3815TT-001 Timer-Thermostat Package Box, ICY BV Product Bar Code No. 8717953007902, 2009, 2 pages. |
| Introducing the New Smart Si Thermostat, Datasheet [online]. Ecobee, Mar. 2012 [retrieved on Feb. 25, 2013]. Retrieved from the Internet: <URL: https://www.ecobee.com/solutions/home/smart-si/>, Mar. 12, 2012, 4 pages. |
| The Clever Thermostat, ICY BV Web Page, http://www.icy.nl/en/consumer/products/clever-thermostat, ICY BV, 2012, 1 page. |
| The Clever Thermostat User Manual and Installation Guide, ICY BV ICY3815 Timer-Thermostat, 2009, pp. 1-36. |
| U.S. Appl. No. 60/512,886, Volkswagen Rotary Knob for Motor Vehicle—English Translation of German Application filed Oct. 20, 2003. |
| Arens et al., “Demand Response Electrical Appliance Manager—User Interface Design, Development and Testing”, Poster, Demand Response Enabling Technology Development, University of California Berkeley, Retrieved from dr.berkeley.edu/dream/posters/2005_6GUIposter.pdf, 2005, 1 page. |
| Arens et al., “Demand Response Enabled Thermostat—Control Strategies and Interface”, Demand Response Enabling Technology Development Poster, University of California Berkeley, Retrieved from dr.berkeley.edu/dream/posters/2004_11CEC_TstatPoster.pdf, 2004, 1 page. |
| Arens et al., “Demand Response Enabling Technology Development”, Phase I Report: Jun. 2003-Nov. 2005, Jul. 27, P:/DemandRes/UC Papers/DR-Phase1Report-Final DraftApril24-26.doc, University of California Berkeley, pp. 1-108. |
| Arens et al., “New Thermostat Demand Response Enabling Technology”, Poster, University of California Berkeley, Jun. 10, 2004. |
| Auslander et al., “UC Berkeley DR Research Energy Management Group”, Power Point Presentation, DR ETD Workshop, State of California Energy Commission, Jun. 11, 2007, pp. 1-35. |
| Bourke, “Server Load Balancing”, O'Reilly & Associates, Inc., Aug. 2001, 182 pages. |
| Chen et al., “Demand Response-Enabled Residential Thermostat Controls”, Abstract, ACEEE Summer Study on Energy Efficiency in Buildings, Mechanical Engineering Dept. and Architecture Dept., University of California Berkeley, 2008, pp. 1-24 through 1-36. |
| Green, “Thermo Heat Tech Cool”, Popular Mechanics Electronic Thermostat Guide, Oct. 1985, pp. 155-158. |
| Meier et al., “Thermostat Interface Usability: A Survey”, Ernest Orlando Lawrence Berkeley National Laboratory, Environmental Energy Technologies Division, Berkeley California, Sep. 2010, pp. 1-73. |
| Peffer et al., “A Tale of Two Houses: The Human Dimension of Demand Response Enabling Technology from a Case Study of Adaptive Wireless Thermostat”, Abstract, ACEEE Summer Study on Energy Efficiency in Buildings, Architecture Dept. and Mechanical Engineering Dept., University of California Berkeley, 2008, pp. 7-242 through 7-253. |
| Peffer et al., “Smart Comfort at Home: Design of a Residential Thermostat to Achieve Thermal Comfort, and Save Money and Peak Energy”, University of California Berkeley, Mar. 2007, 1 page. |
| Salus, “S-Series Digital Thermostat Instruction Manual—ST620 Model No. Instruction Manual”, www.salus-tech.com, Version 005, Apr. 29, 2010, 24 pages. |
| Sanford, “iPod (Click Wheel) (2004)”, www.apple-history.com [retrieved on Apr. 9, 2012]. Retrieved from: http://apple-history.com/ipod, Apr. 9, 2012, 2 pages. |
| White et al., “A Conceptual Model for Simulation Load Balancing”, Proc. 1998 Spring Simulation Interoperability Workshop, 1998, 7 pages. |
| Wright et al., “DR ETD—Summary of New Thermostat, TempNode, & New Meter (UC Berkeley Project)”, Power Point Presentation, Public Interest Energy Research, University of California Berkeley. Retrieved from: http://dr.berkeley.edu/dream/presentations/2005_6CEC.pdf, 2005, pp. 1-49. |
| Chinese Office Action dated Sep. 23, 2015, for Chinese Patent Application No. 201280050837.6, 7 pages. English Translation. |
| Extended European Search Report dated Nov. 3, 2014, for European Application No. 12841021.4, 9 pages. |
| Non-Final Office Action dated Mar. 27, 2014, for U.S. Appl. No. 13/275,311, 12 pages. |
| Notice of Publication dated Sep. 20, 2012, for U.S. Appl. No. 13/275,311, 1 page. |
| Final Office Action dated Sep. 29, 2015, for U.S. Appl. No. 14/469,577, 10 pages. |
| Non-Final Office Action dated May 11, 2015, for U.S. Appl. No. 14/469,577, 6 pages. |
| Notice of Publication dated Feb. 26, 2015, for U.S. Appl. No. 14/469,577, page. |
| Notice of Grounds of Rejection for Japanese Patent Application No. 2015-087419, dated Apr. 5, 2016, 5 pages. English Translation. |
| CN Patent Application No. 201610509236.7 filed Oct. 5, 2012, Office Action dated Aug. 18, 2017, all pages. |
| Decision to Grant a European Patent dated Aug. 19, 2016 in European Patent Application No. 12841021.4, all pages. |
| Number | Date | Country | |
|---|---|---|---|
| 20190037024 A1 | Jan 2019 | US |
| Number | Date | Country | |
|---|---|---|---|
| Parent | 14984876 | Dec 2015 | US |
| Child | 16152879 | US | |
| Parent | 14469577 | Aug 2014 | US |
| Child | 14984876 | US | |
| Parent | 13275311 | Oct 2011 | US |
| Child | 14469577 | US |
