Smart thermostat as controller for legacy air conditioner

The smart thermostat system addresses the inefficiencies of legacy air conditioners by connecting a control board with a microcontroller unit to the HVAC device, enabling remote control and automation, thus reducing energy waste and improving comfort.

WO2025095937A1PCT designated stage expired Publication Date: 2025-05-08GOOGLE LLC
View PDF 4 Cites 0 Cited by

Patent Information

Application Number
PCT/US2023/036457
Authority / Receiving Office
WO · WO
Patent Type
Applications
Current Assignee / Owner
Filing Date
2023-10-31
Publication Date
2025-05-08

AI Technical Summary

Technical Problem

Legacy air conditioners often operate inefficiently due to manual control, leading to wasted energy when users forget to turn them off or adjust the temperature.

Method used

A smart thermostat system is connected to a legacy HVAC device via a control board with a communication interface and microcontroller unit, allowing for remote control and automation of the air conditioner's operations.

Benefits of technology

The system enables efficient energy use by allowing users to remotely control and automate the air conditioner's operations, reducing energy waste and improving comfort.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure US2023036457_08052025_PF_FP_ABST
    Figure US2023036457_08052025_PF_FP_ABST
Patent Text Reader

Abstract

A smart thermostat is configured to control the operation of a legacy HVAC device. As an example, a connection between a smart thermostat and a control board retrofitted to a legacy HVAC device is established. The control board includes a communication interface and a microcontroller unit. Input associated with controlling one or more operations of the legacy HVAC device is received from the smart thermostat. The microcontroller unit of the control board generates one or more instructions to perform the one or more operations of the legacy HVAC device and provides the one or more instructions to circuitry of the legacy HVAC device to perform the one or more operations.
Need to check novelty before this filing date? Find Prior Art

Description

SMART THERMOSTAT AS CONTROLLER FOR LEGACY AIR CONDITIONERTECHNICAL FIELD

[0001] This patent specification relates generally to controlling the operation of an air conditioner. More specifically, this disclosure describes using a thermostat as a smart controller for a legacy air conditioner.BACKGROUND

[0002] Smart-home devices are rapidly becoming part of the modem home experience. These devices may include thermostats, keypads, touch screens, and / or other control devices for controlling environmental systems, such as heating, ventilation, and air conditioning (HVAC) systems or lighting systems. The smart-home environment may also include smart appliances that interface with control and / or monitoring devices to increase the level of functionality and control provided to an occupant. Security systems, including cameras, keypads, sensors, motion detectors, glass-break sensors, microphones, and so forth, may also be installed as part of the smart-home architecture. Other smart-the home devices may include doorbells, monitoring systems, hazard detectors, smart lightbulbs, and virtually any other electronic device that can be controlled via a wired / wireless network.

[0003] While there are many types of smart-home devices, many devices within a home environment are non-smart devices (which may be referred to herein as a “legacy” device). For example, many air conditioners, such as window air conditioning units, or ductless mini-split air conditioners are non-smart devices. Manually controlling the operation of these traditional air conditioners can result in an in-efficient use of energy. For instance, a user may forget to turn off a legacy air condition or fail to adjust the temperature to a more economical setting before leaving, resulting in a waste of power.BRIEF SUMMARY

[0004] A system of one or more computers can be configured to perform particular operations or actions by virtue of having software, firmware, hardware, or a combination of them installed on the system that in operation causes or cause the system to perform the actions. One or more computer programs can be configured to perform particular operations or actions by virtue ofincluding instructions that, when executed by one or processors, cause the system to perform the actions. One general aspect includes a method. In some embodiments, a method may include establishing a connection between a smart thermostat and a control board retrofitted to a legacy HVAC device, where the control board includes a communication interface and a microcontroller unit (MCU). In some embodiments, the method also includes receiving, from the smart thermostat, input associated with controlling one or more operations of the legacy HVAC device. In some embodiments, the method also includes generating, via the microcontroller unit of the control board, one or more instructions to perform the one or more operations of the legacy HVAC device. In some embodiments, the method also includes providing the one or more instructions to circuitry of the legacy HVAC device to perform the one or more operations. Other embodiments of this aspect include corresponding computer systems, apparatus, and computer programs recorded on one or more computer storage devices, each configured to perform the actions of the methods.

[0005] Implementations may include one or more of the following features. In some embodiments, the method where establishing the connection may include establishing a wired connection to a plurality of HVAC control wires. Establishing the connection may include establishing a wireless connection. In some embodiments, the method may include determining, by a cloud-based HVAC control server system, at least one of the one or more operations for the legacy HVAC device to perform. In some embodiments, the method may include performing one or more level shift operations to adjust an input received from the smart thermostat to a compatible input to the circuitry of the MCU. Generating, the one or more instructions to perform the one or more operations of the legacy HVAC device is based on a type of the legacy HVAC device. In some embodiments, the method may include determining, by a cloud-based HVAC control server system, a type of the legacy HVAC device. Receiving the input associated with controlling the one or more operations of the legacy HVAC device is based, at least in part, on an automation script.Implementations of the described techniques may include hardware, a method or process, or computer software on a computer-accessible medium.

[0006] One general aspect includes a system. In some embodiments, a system includes a smart thermostat and a control board retrofitted to a legacy HVAC device. In some embodiments, the system also includes one or more processors. In some embodiments, the system also includes one or more memory devices may include instructions that, when executed by the one or more processors, cause the one or more processors to perform operations may include: establishing a connection between the smart thermostat and the control board; receiving, at the legacy HVAC device, input associated with controlling one or more operations of the legacy HVAC device; generating, via the control board, one or more instructions to perform the one or more operations of the legacy HVAC device; and causing the one or more instructions to execute on circuitry of the legacy HVAC device to perform the one or more operations. Other embodiments of this aspect include corresponding computer systems, apparatus, and computer programs recorded on one or more computer storage devices, each configured to perform the actions of the methods.

[0007] Implementations may include one or more of the following features. In some embodiments, the system where establishing the connection may include one or more of establishing a wired connection to a plurality of HVAC control wires, or establishing a wireless connection. The cloud-based HVAC server is configured to determine at least one of the one or more operations for the legacy HVAC device to perform. The legacy HVAC device is further configured to perform one or more level shift operations to adjust an input received from the smart thermostat to a compatible input to the circuitry of the legacy HVAC device. Generating the one or more instructions to perform the one or more operations of the legacy HVAC device is based on a type of the legacy HVAC device. The legacy HVAC device may include: the control board including: a connection interface configured to connect to one or more smart thermostats; and one or more microcontroller units configured to generate the one or more instructions.Implementations of the described techniques may include hardware, a method or process, or computer software on a computer-accessible medium.

[0008] One general aspect includes a non-transitory computer-readable medium may include instructions for establishing a connection between a smart thermostat and a control board retrofitted to a legacy HVAC device, where the control board includes a communication interface and a microcontroller unit. In some embodiments, the medium also includes receiving, from the smart thermostat, input associated with controlling one or more operations of the legacy HVAC device. In some embodiments, the medium also includes generating, via the microcontroller unit of the control board, one or more instructions to perform the one or more operations of the legacy HVAC device. The medium also includes providing the one or more instructions to circuitry of the legacy HVAC device to perform the one or more operations. Other embodiments of this aspect include corresponding computer systems, apparatus, and computer programs recorded on one or more computer storage devices, each configured to perform the actions of the methods.

[0009] Implementations may include one or more of the following features. The non-transitory computer-readable medium where establishing the connection may include establishing a wired connection to a plurality of HVAC control wires. Establishing the connection may include establishing a wireless connection. In some embodiments, the non-transitory computer-readable medium may include additional instructions that, when executed by the one or more processors, cause the one or more processors to perform additional operations may include determining, by a cloud-based HVAC server, at least one of the one or more operations for the legacy HVAC device to perform. In some embodiments, the non-transitory computer-readable medium may include additional instructions that, when executed by the one or more processors, cause the one or more processors to perform additional operations may include performing one or more level shift operations to adjust an input received from the smart thermostat to a compatible input to the circuitry of the MCU. Generating, the one or more instructions to perform the one or moreoperations of the legacy HVAC device is based on a type of the legacy HVAC device.Implementations of the described techniques may include hardware, a method or process, or computer software on a computer-accessible medium.

[0010] A further understanding of the nature and advantages of the present invention may be realized by reference to the remaining portions of the specification and the drawings. Also note that other embodiments may be described in the following disclosure and claims.BRIEF DESCRIPTION OF THE DRAWINGS

[0011] FIG. 1 is an example of a smart-home environment within which one or more of the devices, methods, systems, services, and / or computer program products described further herein will be applicable, according to some embodiments.

[0012] FIG. 2 illustrates a simplified block diagram of a representative network architecture that includes a smart-home network in accordance, according to some embodiments.

[0013] FIG 3 illustrates a simplified operating environment in which a server system interacts with client devices and smart devices and provides processing for controlling operation of a legacy HVAC system, according to some embodiments.

[0014] FIG. 4 illustrates a simplified block diagram of a representative smart thermostat controlling the operation of a legacy HVAC system, according to some embodiments.

[0015] FIG. 5 illustrates a simplified block diagram of a representative smart device, according to some embodiments.

[0016] FIG. 6A illustrates a simplified block diagram of a representative smart thermostat system connected using wires to a modified legacy HVAC system, according to some embodiments.

[0017] FIG. 6B illustrates a simplified block diagram of a representative smart thermostat system wirelessly connected to a modified legacy HVAC system, according to some embodiments.

[0018] FIG. 7 illustrates a flow chart of a method for a smart thermostat controlling the operation of a legacy HVAC system, according to some embodiments.

[0019] FIG. 8 illustrates a flowchart of a method for a legacy HVAC system receiving and processing instructions received from a smart thermostat, according to some embodiments.DETAILED DESCRIPTION

[0020] 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. It will be apparent to one skilled in the art that the present invention may be practiced without some or all of these specific details. In other instances, well known details have not been described in detail in order not to unnecessarily obscure the present invention.

[0021] 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.

[0022] FIG. 1 illustrates an example smart-home environment 100, according to some embodiments. The smart-home environment 100 includes a structure 150 (e.g., ahouse, office building, garage, or mobile home) with various integrated devices. It will be appreciated that devices may also be integrated into a smart-home environment 100 that does not include an entire structure 150, such as an apartment, condominium, or office space. Further, the smart-home environment 100 may control and / or be coupled to devices outside of the actual structure 150. Indeed, several devices in the smart-home environment 100 need not be physically within the structure 150. For example, a device controlling a pool heater 114 or irrigation system 116 may be located outside of the structure 150.

[0023] The term “smart-home environment” may refer to smart environments for homes such as a single-family house, but the scope of the present teachings is not so limited. The present teachings are also applicable, without limitation, to duplexes, townhomes, multi-unit apartment buildings, hotels, retail stores, office buildings, industrial buildings, and more generally any living space or workspace. Similarly, while the terms user, customer, installer, homeowner, occupant, guest, tenant, landlord, repair person, etc., may be used to refer to a person or persons acting in thecontext of some situations described herein, these references do not limit the scope of the present teachings with respect to the person or persons who are performing such actions. Thus, for example, the terms user, customer, purchaser, installer, subscriber, and homeowner may often refer to the same person in the case of a single-family residential dwelling, because the head of the household is often the person who makes the purchasing decision, buys the unit, and installs and configures the unit, as well as being one of the users of the unit. However, in other scenarios, such as a landlord-tenant environment, the customer may be the landlord with respect to purchasing the unit, the installer may be a local apartment supervisor, a first user may be the tenant, and a second user may again be the landlord with respect to remote control functionality. While the identity of the person performing the action may be germane to a particular advantage provided by one or more of the implementations, such an identity should not be construed in the descriptions that follow as necessarily limiting the scope of the present teachings to those individuals having those identities.

[0024] The depicted structure 150 includes a plurality' of rooms 152, separated at least partly from each other via walls 154. The walls 154 may include interior walls or exterior walls. Each room may further include a floor 156 and a ceiling 158. Devices may be mounted on, integrated with and / or supported by a wall 154, floor 156, or ceiling 158.

[0025] In some implementations, the integrated devices of the smart-home environment 100 include intelligent, multi-sensing, network-connected devices that integrate seamlessly with each other in a smart-home network and / or with a central server or a cloud-computing system to provide a variety of useful smart-home functions. The one or more smart hazard detectors 104 may include thermal radiation sensors directed at respective heat sources (e.g., a stove, oven, other appliances, a fireplace, etc ). For example, a smart hazard detector 104 in a kitchen 153 may include athermal radiation sensor directed at a stove / oven 112. A thermal radiation sensor may determine the temperature of the respective heat source (or a portion thereof) at which it is directed and may provide corresponding blackbody radiation data as output.

[0026] The smart doorbell 106 and / or the smart door lock 120 may detect a person’s approach to or departure from a location (e.g., an outer door), control doorbell / door locking functionality (e g., receive user inputs from a portable electronic device 166A to actuate bolt of the smart door lock 120), announce a person’s approach or departure via audio or visual devices, and / or control settings on a security system (e.g.. to activate or deactivate the security system when occupants go and come). In some implementations, the smart doorbell 106 may include some or all of thecomponents and features of the camera 118. In some implementations, the smart doorbell 106 includes a camera 118.

[0027] The smart alarm system 122 may detect the presence of an individual within close proximity (e.g., using built-in IR sensors), sound an alarm (e.g., through a built-in speaker, or by sending commands to one or more external speakers), and send notifications to entities or users within / outside of the smart-home network 100. In some implementations, the smart alarm system 122 also includes one or more input devices or sensors (e.g., keypad, biometric scanner, NFC transceiver, microphone) for verilying the identity of a user, and one or more output devices (e.g., display, speaker) for providing notifications. In some implementations, the smart alarm system 122 may also be set to an “armed” mode, such that detection of a trigger condition or event causes the alarm to be sounded unless a disarming action is performed.

[0028] In some implementations, the smart-home environment 100 may include one or more intelligent, multi-sensing, network-connected wall switches 108 (hereinafter referred to as “smart wall switches 108”), along with one or more intelligent, multi -sensing, network-connected wall plug interfaces 110 (hereinafter referred to as “smart wall plugs 110”). The smart wall switches 108 may detect ambient lighting conditions, detect room-occupancy states, and control a power and / or dim state of one or more lights. In some instances, smart wall switches 108 may also control a power state or speed of a fan, such as a ceiling fan. The smart wall plugs 110 may detect occupancy of a room or enclosure and control supply of power to one or more wall plugs (e.g., such that power is not supplied to the plug if nobody is at home).

[0029] In some implementations, the smart-home environment 100 of FIG. 1 may include a plurality of intelligent, multi-sensing, network-connected appliances 112 (hereinafter referred to as “smart appliances 112”), such as refrigerators, stoves, ovens, televisions, washers, dryers, lights, stereos, intercom systems, garage-door openers, floor fans, ceiling fans, wall air conditioners, pool heaters, irrigation systems, security systems, space heaters, window AC units, motorized duct vents, and so forth. In some implementations, when plugged in. an appliance may announce itself to the smart home network, such as by indicating what type of appliance it is, and it may automatically integrate with the controls of the smart home.

[0030] Such communication by the appliance to the smart home may be facilitated by either a wired or wireless communication protocol. The smart home may also include a variety of noncommunicating legacy appliances 140, such as older-model conventional heating, ventilation, and air conditioning (HVAC) units, washers / dryers, refrigerators, and / or the like, which may becontrolled by smart wall plugs 110. The smart-home environment 100 may further include a variety of partially communicating legacy appliances 142, such as infrared (“IR”) controlled wall air conditioners or other IR-controlled devices, which may be controlled by IR signals provided by the smart hazard detectors 104, hand-held remote controls, key FOBs, or the smart w all switches 108.

[0031] In some configurations, some / all of the smart-home devices, the non-communicating legacy devices, and / or the partially communicating devices within the smart-home environment 100 may be configured to communicate using any variety of custom of or standard wireless protocols (e.g., Matter, IEEE 802.15.4, Wi-Fi, ZigBee, 6L0WPAN, Thread, Z-Wave, Bluetooth Smart, ISA100.5A, WirelessHART, MiWi, etc.) and / or any of a variety of custom or standard wired protocols (e.g., Ethernet, HomePlug, etc.), or any other suitable communication protocol, including communication protocols not yet developed as of the filing date of this document.

[0032] The smart-home environment 100 may include one or more intelligent, multi-sensing, network-connected thermostats 102 (hereinafter referred to as “smart thermostats 102”), one or more intelligent, network-connected, multi-sensing hazard detection units 104 (hereinafter referred to as “smart hazard detectors 104”), one or more intelligent, multi-sensing, network-connected entry way interface devices 106 and 120 (hereinafter referred to as “smart doorbells 106” and “smart door locks 120”), one or more intelligent, multi-sensing, network-connected alarm systems 122 (hereinafter referred to as “smart alarm systems 122”), and one or more other intelligent, network-connected devices. The smart-home environment 100 may also include other smart home devices / controls, such as but not limited to monitoring systems (e.g., baby monitoring systems, elderly monitoring systems, handicapped monitoring systems, .. . ), home entertainment controls, energy conservation devices / controls, home control devices / controls, remote home management and monitoring devices / controls, safety.

[0033] In some implementations, the one or more smart thermostats 102 detect ambient climate characteristics (e.g., temperature and / or humidity) and control a HVAC system 103 accordingly. For example, a respective smart thermostat 102 includes an ambient temperature sensor.According to techniques described herein, the one or more smart thermostats 102 are configured to control one or more non-communicating legacy appliances 140, such as older-model conventional heating, ventilation, and air conditioning (HVAC) units and / or one or more partially communicating legacy appliances 142, such as infrared (“IR”) controlled wall air conditioners or mini-split air conditioning units, which may be controlled by IR signals provided by hand-heldremote controls, key FOBs, or other smart devices configured to interact with the partially communicating legacy appliances 140.

[0034] As will be discussed in more detail below, a legacy HVAC system, such as HVAC system 165 illustrated in FIGs. 3, 4, 6A, and 6B may be modified to include circuitry to communicate and be controlled by a smart thermostat. According to some examples, a printed circuit board (PCB) is coupled to and / or included within legacy devices, such as devices 103, 140 and / or 142. to perform operations relating to control the legacy device. For instance, the PCB may include a chipset to communicate with one or more smart-home devices using a wireless or wired protocol. In some configurations, the PCB may include a Thread chipset and use the Matter standard. Today, many smart-home devices are configured as Matter devices that use Thread.

[0035] Thread is an IP-based wireless mesh networking technology7, that is IPv6 based. Thread devices can join the same network as your other devices and talk directly to each other and the cloud. Thread is designed for Internet of Things (loT), and supports low-powered devices, such as battery-operated devices. The different Thread devices can form a mesh that delivers range and reliability7. Thread devices are also extremely responsive. Thread devices can join an existing home network through a Thread Border Router. Just like a Wi-Fi router can bridge Wi-Fi and Ethernet devices into a single network, a Thread Border Router allows Thread devices to become part of users' networks. In some configurations, one or more of the devices in the home environment may include Thread radios built-into them and act as Thread Border Routers.

[0036] Matter is an open standard for smart home technology7that allows devices to work with any Matter-certified ecosystem using a single protocol. Matter comes from the Connectivity Standards Alliance, an organization of hundreds of companies creating products for the smart home. In some cases, some / all the smart-home devices may natively support Matter for local connectivity and control. When a device is Matter certified it is configured to work with any7Matter-enabled app, ecosystem, or other Matter controller.

[0037] In some implementations, in addition to containing processing and sensing capabilities, devices 102, 104, 106, 108, 110. 112, 114, 116, 118, 120. and / or 122 (collectively referred to as ■‘the smart devices” or ‘‘the smart-home devices”) are capable of data communications and information sharing with other smart devices, a central server or cloud-computing system, and / or other devices that are network-connected. Data communications may be carried out using any of a variety of custom or standard wireless protocols (e.g., IEEE 802. 15.4, Wi-Fi, ZigBee, 6L0WPAN, Thread, Z-Wave. Bluetooth Smart, ISA! 00.5 A, WirelessHART, MiWi, etc.) and / or any of avariety of custom or standard wired protocols (e.g., Ethernet, HomePlug, etc.), or any other suitable communication protocol, including communication protocols not yet developed as of the filing date of this document.

[0038] In some implementations, the smart-home environment 100 may include one or more network-connected cameras 118 that are configured to provide video monitoring and security in the smart-home environment 100. The cameras 118 may be used to determine the occupancy of the structure 150 and / or particular rooms 152 in the structure 150, and thus may act as occupancy sensors. For example, video captured by the cameras 118 may be processed to identify the presence of an occupant in the structure 150 (e g., in a particular room 152). Specific individuals may be identified based, for example, on their appearance (e.g., height, face) and / or movement (e.g., their walk / gait). Cameras 118 may additionally include one or more sensors (e.g., IR sensors, motion detectors), input devices (e.g., microphone for capturing audio), and output devices (e.g., speaker for outputting audio). In some implementations, the cameras 118 may each be configured to operate in a day mode and in a low-light mode (e.g., a night mode). In some implementations, the cameras 118 each include one or more IR illuminators for providing illumination while the camera is operating in the low-light mode. In some implementations, the cameras 118 include one or more outdoor cameras. In some implementations, the outdoor cameras include additional features and / or components such as weatherproofing and / or solar ray compensation.

[0039] The smart-home environment 100 may additionally or alternatively include one or more other occupancy sensors (e.g., the smart doorbell 106, smart door locks 120, touch screens, IR sensors, microphones, ambient light sensors, motion detectors, smart nightlights 170, etc.). In some implementations, the smart-home environment 100 may include radio-frequency identification (RFID) readers (e.g., in each room 152 or a portion thereof) that determine occupancy based on RFID tags located on or embedded in occupants. For example, RFID readers may be integrated into the smart hazard detectors 104, and RFID tags may attached to clothing, and / or integrated in hand-held devices such as a smart phone.

[0040] The smart-home environment 100 may also include communication with devices outside of the physical home but within a proximate geographical range of the home. For example, the smart-home environment 100 may include a pool heater monitor 114 that communicates a current pool temperature to other devices within the smart-home environment 100 and / or receives commands for controlling the pool temperature. Similarly, the smart-home environment 100 may include an irrigation monitor 116 that communicates information regarding irrigation systemswithin the smart-home environment 100 and / or receives control information for controlling such irrigation systems.

[0041] By virtue of network connectivity, one or more of the smart home devices of FIG. 1 may further allow a user to interact with the device even if the user is not proximate to the device. For example, a user may communicate with a device using a computer (e.g., a desktop computer, laptop computer, or tablet) or some other portable electronic device 166 (e.g., a mobile phone, such as a smart phone). A webpage or application may be configured to receive communications from the user and control the device based on the communications and / or to present information about the device’s operation to the user. For example, the user may view a current set point temperature for a device (e.g., a stove) and adjust it using a computer. The user may be in the structure during this remote communication or outside the structure.

[0042] As discussed above, users may control smart devices in the smart-home environment 100 using a network-connected computer or portable electronic device 166. In some examples, some or all of the occupants (e.g., individuals who live in the home) may register their device 166 with the smart-home environment 100. Such registration may be made at a central server to authenticate the occupant and / or the device as being associated with the home and to give permission to the occupant to use the device to control the smart devices in the home. An occupant may use their registered device 166 to remotely control the smart devices of the home, such as when the occupant is at work or on vacation. The occupant may also use their registered device to control the smart devices when the occupant is actually located inside the home, such as when the occupant is sitting on a couch inside the home. It should be appreciated that instead of or in addition to registering devices 166, the smart-home environment 100 may make inferences about (1) which individuals live in the home and are therefore occupants, and (2) which devices 166 are associated with those individuals. As such, the smart-home environment may “learn” who is an occupant and permit the devices 166 associated with those individuals to control the smart devices of the home.

[0043] In some implementations, in addition to containing processing and sensing capabilities, devices 102, 104, 106, 108, 110, 112, 114, 116, 118, 120, and / or 122 (collectively referred to as “the smart devices” or “the smart-home devices”) are capable of data communications and information sharing with other smart devices, a central server or cloud-computing system, and / or other devices that are network-connected. Data communications may be carried out using any of a variety of custom or standard wireless protocols as described above.

[0044] In some implementations, the smart devices may serve as wireless or wired repeaters. In some implementations, a first one of the smart devices communicates with a second one of the smart devices via a wireless router. The smart devices may further communicate with each other via a connection (e.g., network interface 160) to a network, such as the Internet 162. Through the Internet 162, the smart devices may communicate with a server system 164 (also called a central server system and / or a cloud-computing system herein). The server system 164 may be associated with a manufacturer, support entity, or service provider associated with the smart device(s). In some implementations, a user is able to contact customer support using a smart device itself rather than needing to use other communication means, such as a telephone or Internet-connected computer. In some implementations, softw are updates are automatically sent from the server system 164 to smart devices (e.g., when available, when purchased, or at routine intervals).

[0045] In some implementations, the network interface 160 includes a conventional network device (e.g., a router), and the smart-home environment 100 of FIG. 1 includes a hub device 180 that is communicatively coupled to the network(s) 162 directly or via the network interface 160. The hub device 180 may be further communicatively coupled to one or more of the above intelligent, multi-sensing, network-connected devices (e.g., smart devices of the smart-home environment 100). Each of these smart devices optionally communicates with the hub device 180 using one or more radio communication networks available at least in the smart-home environment 100 (e.g., ZigBee, Z-Wave, Insteon, Bluetooth, Wi-Fi and other radio communication networks). In some implementations, the hub device 180 and devices coupled with / to the hub device can be controlled and / or interacted with via an application running on a smart phone, household controller, laptop, tablet computer, game console or similar electronic device. In some implementations, a user of such controller application can view' status of the hub device or coupled smart devices, configure the hub device to interoperate with smart devices newly introduced to the home network, commission new smart devices, and adjust or view settings of connected smart devices, etc. In some implementations the hub device extends the capabilities of low-capability smart devices to match the capabilities of the highly capable smart devices of the same type, integrates functionality' of multiple different device ty pes - even across different communication protocols, and is configured to streamline adding of new' devices and commissioning of the hub device. In some implementations, hub device 180 further comprises a local storage device for storing data related to, or output by, smart devices of smart-home environment 100. In some implementations, the data includes one or more of: video data output by a camera device, metadataoutput by a smart device, settings information for a smart device, usage logs for a smart device, and the like.

[0046] In some implementations, smart-home environment 100 includes a local storage device for storing data related to, or output by, smart devices of smart-home environment 100. In some implementations, the data includes one or more of: video data output by a camera device (e.g., camera 118), metadata output by a smart device, settings information for a smart device, usage logs for a smart device, and the like. In some implementations, local storage device is communicatively coupled to one or more smart devices via a smart home network. In some implementations, local storage device is selectively coupled to one or more smart devices via a wired and / or wireless communication network. In some implementations, local storage device is used to store video data when external network conditions are poor. For example, local storage device is used when an encoding bitrate of camera 118 exceeds the available bandwidth of the external network (e.g., network(s) 162). In some implementations, local storage device temporarily stores video data from one or more cameras (e.g., camera 118) prior to transferring the video data to a server system (e.g., server system 164). In some implementations, the smart-home environment 100 includes service robots 168 that are configured to carry out. in an autonomous manner, any of a variety of household tasks.

[0047] According to some examples, all / some of the smart devices can be controlled using an automation 174. Generally, an automation may be a script including a set of instructions that when executed are used to automate tasks in a smart home. As an example, a script may be used to lock the doors, turn off the lights, and adjust the temperature of an HVAC system (e.g., a legacy device modified to communicate with a smart thermostat) when you leave home, turn on lights when its dark outside and you are home, dim the lights when you watch a movie, raise the temperature of an HVAC system during the night, and the like. Scripts can be used to control a variety of smart devices, such as lights, audio devices, video devices, thermostats, locks, security systems, modified legacy devices to communicate within the home environment, and the like. In some configurations, the input to an HVAC system 174A may be a script that includes instructions in a programming language, such as YAML Ain’t Markup Language (YAML), Python, JavaScript, or some other programming language. Once a script is created, it can be triggered for execution by a variety of events, such as the time of day, the opening of a door, or the arrival of a person, and the like. In some examples, a user may issue a prompt, such as a natural language prompt to provide instructions to a legacy HVAC system. In some cases, a graphical user interface (GUI) may beused to interact with one or more devices. The GUIs may include UI elements that display information about the devices within the home environment.

[0048] FIG. 2 illustrates a simplified block diagram of a representative network architecture 200 that includes a smart home network 202 in accordance with some implementations. In some implementations, the smart devices 204 in the smart-home environment 100 (e.g., devices 102, 104, 106, 108, 110, 112, 114, 116, 118, 120, and / or 122) combine with the hub device 180 to create a mesh network in smart home network 202. In some examples, one or more legacy devices, such as one or more legacy HVAC systems, such as HVAC system 165, can be configured to be part of the mesh network in the smart home network 202. In these examples, the legacy devices may be configured to communicate with other smart devices, such as smart thermostats and / or other devices. In some implementations, one or more smart devices 204 in the smart home network 202 operate as a smart home controller. Additionally, and / or alternatively, hub device 180 operates as the smart home controller.

[0049] In some implementations, a smart home controller has more computing power than other smart devices. In some implementations, a smart home controller processes inputs (e.g., from smart devices 204, electronic device 166, and / or server system 164) and sends commands (e.g., to smart devices 204 in the smart home network 202) to control operation of the smart-home environment 100. In some implementations, some of the smart devices 204 in the smart home network 202 (e.g., in the mesh network) are “spokesman” nodes (e.g., 204-1) and others are “low- powered” nodes (e.g., 204-9). Some of the smart devices in the smart-home environment 100 are battery powered, while others have a regular and reliable power source, such as by connecting to wiring (e.g., to 120V line voltage wires) behind the walls 154 of the smart-home environment. The smart devices that have a regular and reliable pow er source are referred to as “spokesman” nodes. These nodes are typically equipped with the capability of using a wireless protocol to facilitate bidirectional communication with a variety of other devices in the smart-home environment 100, as well as with the server system 164. In some implementations, one or more “spokesman” nodes operate as a smart home controller. On the other hand, the devices that are battery powered are the “low-power” nodes. These nodes tend to be smaller than spokesman nodes and typically only communicate using wireless protocols that require very little power, such as Zigbee, ZWave, 6L0WPAN, Thread, Bluetooth, etc.

[0050] In some implementations, some low-power nodes may be incapable of bidirectional communication. These low-power nodes may send messages, but they are unable to “listen.” Thus, other devices in the smart-home environment 100, such as the spokesman nodes, need notsend information to these low-power nodes. In some implementations, some low-power nodes are capable of only a limited bidirectional communication. For example, other devices are able to communicate with the low-power nodes only during a certain time period.

[0051] In some implementations, the smart devices may serve as low-power and spokesman nodes to create a mesh network in the smart-home environment 100. In some implementations, individual low-power nodes in the smart-home environment may regularly send out messages regarding what they are sensing, and the other low-powered nodes in the smart-home environment - in addition to sending out their own messages - may forward these messages, thereby causing the messages to travel from node to node (i.e., device to device) throughout the smart home netw ork 202. In some implementations, the spokesman nodes in the smart home network 202, which are able to communicate using a relatively high-power communication protocol, such as IEEE 802. 11, are able to switch to a relatively low-power communication protocol, such as IEEE 802.15.4, to receive these messages, translate the messages to other communication protocols, and send the translated messages to other spokesman nodes and / or the server system 164 (using, e.g., the relatively high-pow er communication protocol). Thus, the low -powered nodes using low- power communication protocols can send and / or receive messages across the entire smart home network 202, as well as over the Internet 162 to the server system 164. In some implementations, the mesh network enables the server system 164 to regularly receive data from most or all of the smart devices in the home, make inferences based on the data, facilitate state synchronization across devices within and outside of the smart home network 202, and send commands to one or more of the smart devices to perform tasks in the smart-home environment.

[0052] The spokesman nodes and some of the low-powered nodes are capable of "listening.” Accordingly, users, other devices, and / or the server system 164 may communicate control commands to the low-powered nodes. For example, a user may use the electronic device 166 (e.g., a smart phone) to send commands over the Internet to the server system 164, which then relays the commands to one or more spokesman nodes in the smart home network 202. The spokesman nodes may use a low-power protocol to communicate the commands to the low -power nodes throughout the smart home netw ork 202, as well as to other spokesman nodes that did not receive the commands directly from the server system 164.

[0053] In some implementations, a smart nightlight 170, which is an example of a smart device 204, is a low-power node. In addition to housing a light source, the smart nightlight 170 houses an occupancy sensor, such as an ultrasonic or passive IR sensor, and an ambient light sensor, such as a photo resistor or a single-pixel sensor that measures light in the room. In some implementations,the smart nightlight 170 is configured to activate the light source when its ambient light sensor detects that the room is dark and when its occupancy sensor detects that someone is in the room. In other implementations, the smart nightlight 170 is simply configured to activate the light source when its ambient light sensor detects that the room is dark. Further, in some implementations, the smart nightlight 170 includes a low-power wireless communication chip (e.g., a ZigBee chip) that regularly sends out messages regarding the occupancy of the room and the amount of light in the room, including instantaneous messages coincident with the occupancy sensor detecting the presence of a person in the room. As described above, these messages may be sent wirelessly (e.g., using the mesh netw ork) from node to node (i.e., smart device to smart device) within the smart home network 202 as well as over the Internet 162 to the server system 164.

[0054] Other examples of low-power nodes include battery-operated versions of the smart hazard detectors 104. These smart hazard detectors 104 are often located in an area without access to constant and reliable power and may include any number and type of sensors, such as smoke / fire / heat sensors (e.g., thermal radiation sensors), carbon monoxide / dioxide sensors, occupancy / motion sensors, ambient light sensors, ambient temperature sensors, humidity sensors, and the like. Furthermore, smart hazard detectors 104 may send messages that correspond to each of the respective sensors to the other devices and / or the server system 164, such as by using the mesh network as described above.

[0055] Examples of spokesman nodes include smart doorbells 106, smart thermostats 102, smart wall switches 108, and smart wall plugs 110. These devices are often located near and connected to a reliable power source, and therefore may include more power-consuming components, such as one or more communication chips capable of bidirectional communication in a variety of protocols.

[0056] As explained above with reference to FIG. 1, in some implementations, the smart-home environment 100 of Figure 1 includes a hub device 180 that is communicatively coupled to the network(s) 162 directly or via the network interface 160. The hub device 180 is further communicatively coupled to one or more of the smart devices using a radio communication network that is available at least in the smart-home environment 100. Communication protocols used by the radio communication network include, but are not limited to, ZigBee, Z-Wave, Insteon, EuOcean, Thread, OSIAN, Bluetooth Low Energy and the like. In some implementations, the hub device 180 not only converts the data received from each smart device to meet the data format requirements of the network interface 160 or the network(s) 162, but also converts information received from the network interface 160 or the network(s) 162 to meet the data formatrequirements of the respective communication protocol associated with a targeted smart device. In some implementations, in addition to data format conversion, the hub device 180 further processes the data received from the smart devices or information received from the network interface 160 or the network(s) 1 2 preliminary. For example, the hub device 180 can integrate inputs from multiple sensors / connected devices (including sensors / devices of the same and / or different types), perform higher level processing on those inputs - e.g., to assess the overall environment and coordinate operation among the different sensors / devices - and / or provide instructions to the different devices based on the collection of inputs and programmed processing. It is also noted that in some implementations, the network interface 160 and the hub device 180 are integrated to one network device. Functionality7described herein is representative of particular implementations of smart devices, control application(s) running on representative electronic device(s) (such as a smart phone), hub device(s) 180, and server(s) coupled to hub device(s) via the Internet or other Wide Area Network (WAN). All or a portion of this functionality7and associated operations can be performed by any elements of the described system - for example, all or a portion of the functionality described herein as being performed by an implementation of the hub device can be performed, in different system implementations, in whole or in part on the server, one or more connected smart devices and / or the control application, or different combinations thereof.

[0057] FIG. 3 illustrates an embodiment of a system 300 that includes a smart thermostat 102 for controlling a traditional HVAC system. System 300 can include: cloud-based server system 164; network 162; mobile device 166; smart thermostat 102; and a modified legacy HVAC system 165.

[0058] Smart thermostat 102 can be a smart thermostat capable of connecting to network 162 and controlling a HVAC system 165. Smart thermostat 102 may include one or more processors that may execute special-purpose software stored in a memory of smart thermostat 102. Smart thermostat 102 can include one or more sensors, such as a temperature sensor or an ambient light sensor. Smart thermostat 102 can also include an electronic display. The electronic display may include a touch sensor that allows a user to interact with the electronic screen. Smart thermostat 102 may connect via network 162 to cloud-based sen- er system 164. For example, smart thermostat 102 may receive HVAC instructions from cloud-based server system 164 to be relayed to the HVAC system 165.

[0059] In some embodiments, smart thermostat 102 may connect via network 162 to mobile device 166 or one or more other computing devices (not shown). For example, smart thermostat 102 may receive heating or cooling instructions from a user’s mobile device 166. In someexamples, smart thermostat 102 will modify HVAC instructions based on the type of HVAC system 165. For example, smart thermostat 102 may receive an input, such as a setpoint temperature adjustment, at the thermostat that results in the HVAC instructions being modified / translated to control a particular type of HVAC system. For instance, first HVAC instructions can be generated by the server system 164, the control board 302, the smart thermostat 102, or some other component / device, based on a first type of HVAC system 165 and second HVAC instructions can be generated based on a second type of HVAC system 165.

[0060] Smart thermostat 102 may also be connected to an HVAC system 165 and may cause HVAC system 165 to provide heating or cooling until a setpoint temperature measured at smart thermostat 102 has been achieved. HVAC system 165 may be any type and / or brand of HVAC system such as: a window air conditioner, a mini-split unit, an electric water heater connected to a hydronic baseboard, an electric baseboard, a fan unit of forced air system, and the like. In some examples, the legacy HVAC system 165 is coupled to a control board 302 that is configured to receive instructions from a smart device, and cause the HVAC system 165 to perform the HVAC operations (e.g., the supported operations of the particular type and model of the HVAC system 165).

[0061] In some examples, a user of mobile device 166, or some other device, can connect via network 162 to smart thermostat 102 at the user’s home to monitor the status of smart thermostat 102 or send heating and cooling instructions to smart thermostat 102 that will in turn cause an HVAC system 165 to provide heating or cooling to the user’s home. Smart thermostat 102 may also be connected to an HVAC system 165 and may cause HVAC system 165 to provide heating or cooling until a setpoint temperature measured at smart thermostat 102 has been achieved.

[0062] Cloud-based server system 164 can include a plurality of services such as: API engine 211; communication interface 212; event scheduler 213; instructions engine 214; and a user management module 215. Cloud-based server system 164 can also include one or more databases such as HVAC database 218. Cloud-based server system 164 can also include processing system 219 that can coordinate the execution of the various functionalities provided by the plurality of services and can communicate with the one or more databases such as HVAC database 218.

[0063] API engine 211 may implement published interfaces from one or more external systems. The published interfaces may allow cloud-based server system 164 to interact with various external systems to request and exchange data. API engine 211 may also allow cloud-based serv er system 164 to communicate with various devices connected to network 162. For example, APIengine 211 may implement an interface for sending text messages, emails, or application notifications to mobile device 166. API engine 211 may also allow cloud-based server system 164 to send instructions to smart devices connected to network 162. For example, API engine 211 may implement an interface for smart thermostat 102 and / or HVAC system 165.

[0064] Communication interface 212 may be used to communicate with one or more wired networks. In some embodiments, a wired network interface may be present, such as to allow communication with a local area network (LAN). Communication interface 212 may also be used to communicate with distributed services across multiple virtual machines through a virtual network. Communication interface 212 may be used by one or more of the other processes to communicate with the other process or with external devices and services such as mobile device 166, or smart thermostat 102.

[0065] User management module 215 may include one or more processes for managing user accounts. For example, user management module 215 may access, modify, and store account details for a specific user account such as information for one or more devices owned and operated by a user associated with the account, various settings for programs a user account may be participating in and to what extent, payment methods, setpoint temperature preferences, or user account habits. User management module 215 may also provide user account-specific information to event scheduler 213 to help determine what events to schedule and when based on preferences associated with the user account. In some embodiments, user management module 215 may also send communications to a user associated with a user account, such as notifications or updates, or to an application on a mobile device 166 associated with the user account. For example, user management module 215 may send an email, text, or other information to a specific user account.

[0066] One or more databases, such as HVAC database 218, may store or otherwise make data accessible to cloud-based server system 164. HVAC database 218 may include data associated with different ty pes, and models of HVAC systems, HVAC instructions, as well as other data. The HVAC systems may include information about different types of HVAC systems that the smart thermostat 102 can interact with. For example, the HVAC systems information may indicate the supported operations of the different HVAC systems. The HVAC instructions information may include instructions used to control the different types of HVAC systems. For example, the HVAC instructions may include setpoint temperature instructions that when provided to the HVAC system instruct the HVAC system to move toward the set-point temperature.

[0067] Cloud-based server system 164 may include other databases for various purposes. For example, there may be a user database storing information specific to individual user accounts such as account details, HVAC system characteristics, setpoint temperature preferences, etc. The one or more databases, including HVAC database 218, may be implemented by one or more suitable database structures such as a relational database (e.g., SQL) or a NoSQL database (e.g., MongoDB).

[0068] Processing system 219 can include one or more processors. Processing system 219 may include one or more special-purpose or general-purpose processors. Such special-purpose processors may include processors that are specifically designed to perform the functions detailed herein. Such special-purpose processors may be ASICs or FPGAs which are general-purpose components that are physically and electrically configured to perform the functions detailed herein. Such general-purpose processors may execute special-purpose software that is stored using one or more non-transitory processor-readable mediums, such as random-access memory (RAM), flash memory, a hard disk drive (HDD), or a solid-state drive (SSD) of cloud-based server system 164.

[0069] FIG. 4 illustrates an embodiment of a smart thermostat system 400 that connects to legacy HVAC systems 165. Smart thermostat system 400 can include smart thermostat 102; network 162; cloud-based server system 164; backplate 360. As illustrated, smart thermostat 102 is wirelessly connected to HVAC system 165B via control board 302B, and connected via wires to HVAC system 165A via control board 302B. Smart thermostat 102 can include: electronic display- 311; touch sensor 312; network interface 313; event scheduler 314; ambient light sensor 315; temperature sensor 316; HVAC interface 318; housing 321; and cover 322.

[0070] Electronic display 31 1 may be visible through cover 322. In some embodiments, electronic display 311 is only visible when electronic display 311 is illuminated. In some embodiments, electronic display 311 is not a touch screen. Touch sensor 312 may allow one or more gestures, including tap and swipe gestures, to be detected. Touch sensor 312 may be a capacitive sensor that includes multiple electrodes. In some embodiments, touch sensor 312 is a touch strip that includes five or more electrodes.

[0071] Network interface 313 may be used to communicate with one or more wired or wireless networks. Network interface 313 may communicate with a wireless local area network such as a WiFi network. Additional or alternative network interfaces may also be present. For example, smart thermostat 102 may be able to communicate with a user device directly, such as by usingBluetooth®. Smart thermostat 102 may be able to communicate via a mesh network with various other home automation devices. Mesh networks may use relatively less power compared to wireless local area network-based communication, such as WiFi. In some embodiments, smart thermostat 102 can serve as an edge router that translates communications between a mesh network and a wireless network, such as a WiFi network. In some embodiments, a wired network interface may be present, such as to allow communication with a local area network (LAN). One or more direct wireless communication interfaces may also be present, such as to enable direct communication with a remote temperature sensor installed in a different housing external and distinct from housing 321. The evolution of wireless communication to fifth generation (5G) and sixth generation (6G) standards and technologies provides greater throughput with lower latency which enhances mobile broadband services. 5G and 6G technologies also provide new classes of services, over control and data channels, for vehicular networking (V2X), fixed wireless broadband, and the Internet of Things (loT). Smart thermostat 102 may include one or more wireless interfaces that can communicate using 5G and / or 6G networks.

[0072] Event scheduler 314 may schedule events to control one or more HVACs 165. For example, event scheduler 314 may help determine what events to schedule and when based on preferences associated with the user account (e.g., temperature settings, schedules associated with cooling, heating, ... ).

[0073] Ambient light sensor 315 may sense the amount of light present in the environment of smart thermostat 102. Measurements made by ambient light sensor 315 may be used to adjust the brightness of electronic display 311. In some embodiments, ambient light sensor 315 senses an amount of ambient light through cover 322. Therefore, compensation for the reflectivity of cover 322 may be made such that the ambient light levels are correctly determined via ambient light sensor 315. A light pipe may be present between ambient light sensor 315 and cover 322 such that in a particular region of cover 322, light that is transmitted through cover 322, is directed to ambient light sensor 315, which may be mounted to a printed circuit board (PCB), such as a PCB to which processing system 319 is attached.

[0074] One or more temperature sensors, such as remote temperature sensor 316, may be present within smart thermostat 102. Temperature sensor 316 may be used to measure the ambient temperature in the environment of smart thermostat 102. One or more additional temperature sensors that are remote from smart thermostat 102, such as remote temperature sensor 320, may additionally or alternatively be used to measure the temperature of the ambient environment. For example, one or more remote temperature sensors 320 placed throughout a home or building maybe connected to smart thermostat 102 in order to provide a more accurate representation of the ambient temperature throughout the home or building.

[0075] Cover 322 may have a transmissivity’ sufficient to allow illuminated portions of electronic display 311 to be viewed through cover 322 from an exterior of smart thermostat 102 by a user. Cover 322 may have a reflectivity sufficient such that portions of cover 322 that are not illuminated from behind appear to have a mirrored effect to a user viewing a front of thermostat 310.

[0076] HVAC interface 318 can include one or more interfaces that control whether a circuit involving various HVAC control wires that are connected either directly with thermostat 310 or with backplate 360 is completed. A heating system (e.g., furnace, heat pump), cooling system (e.g., air conditioner), and / or fan may be controlled via HVAC wires by opening and closing circuits that include the HVAC control wires. HVAC interface 318 may also be some form of wireless interface that controls a separate electronic unit that communicates with the HVAC system via HVAC wires. In some embodiments, HVAC interface 318 implements one or more communication protocols. For example, HVAC interface 318 may use a proprietary serial communication protocol over wires as specified by a manufacturer of the HVAC system. As another example, HVAC interface 318 may communicate wirelessly to an HVAC system that supports Thread®, Zigbee®, CHIP / Matter®, or any other suitable wireless communication protocol.

[0077] Processing system 319 can include one or more processors. Processing system 319 may include one or more special-purpose or general-purpose processors. Such special-purpose processors may include processors that are specifically designed to perform the functions detailed herein. Such special-purpose processors may be ASICs or FPGAs which are general-purpose components that are physically and electrically configured to perform the functions detailed herein. Such general-purpose processors may execute special-purpose software that is stored using one or more non-transitory processor-readable mediums, such as random access memory (RAM), flash memory, a hard disk drive (HDD), or a solid state drive (SSD) of smart thermostat 102.

[0078] Processing system 319 may output information for presentation to electronic display 311. Processing system 319 can receive information from touch sensor 312, ambient light sensor 316, and temperature sensor 317. Processing system 319 can perform bidirectional communication with network interface 313. Processing system 319 can control the HVAC system via HVAC interface 318. In some embodiments, process system 319 executes one or more softwareapplications or services stored on or otherwise accessible by smart thermostat 102. For example, one or more components of smart thermostat 102, such as event scheduler 314, may include one or more software applications or software services that may be executed by processing system 319.

[0079] Cloud-based server system 164 can maintain a user account mapped to smart thermostat 102. Smart thermostat 102 may periodically or intermittently communicate with cloud-based server system 164 to determine when to adjust the setpoint or some other operation of the HVAC system. A person may interact with thermostat 102 via computerized device 166, which may be a mobile device, smartphone, tablet computer, laptop computer, desktop computer, or some other form of computerized device that can communicate with cloud-based server system 1 4 via netw ork 162 or can communicate directly with thermostat 102 (e.g., via Bluetooth® or some other device-to-device communication protocol). A person can interact with an application executed on computerized device 166 to control or interact with thermostat 102.

[0080] FIG. 5 is a block diagram illustrating a representative smart device 166 in accordance with some implementations. In some implementations, the smart device 1 6 (e g., any devices of a smart-home environment 100, Figure 1) includes one or more processing units (e.g., CPUs, ASICs, FPGAs, microprocessors, and the like) 402, one or more communication interfaces 404, memory 406, communications module 442 with radios 440, and one or more communication buses 408 for interconnecting these components (sometimes called a chipset). In some implementations, the user interface 410 includes one or more output devices 412 that enable presentation of media content, including one or more speakers and / or one or more visual displays. In some implementations, the user interface 410 also includes one or more input devices 414, including user interface components that facilitate user input such as a keyboard, a mouse, a voice-command input unit or microphone, a touch screen display, a touch-sensitive input pad, a gesture capturing camera, or other input buttons or controls. Furthermore, some smart devices 166 use a microphone and voice recognition or a camera and gesture recognition to supplement or replace the keyboard. In some implementations, the smart device 166 includes one or more image / video capture devices 418 (e.g., cameras, video cameras, scanners, photo sensor units). The built-in sensors 490 may include, for example, one or more thermal radiation sensors, ambient temperature sensors, humidity sensors, IR sensors, occupancy sensors (e.g., using RFID sensors), ambient light sensors, motion detectors, accelerometers, and / or gyroscopes.

[0081] The radios 440 enable one or more radio communication netw orks in the smart-home environments, and allow a smart device 166 to communicate with other devices. In some implementations, the radios 440 are capable of data communications using any of a variety ofcustom or standard wireless protocols, custom or standard wired protocols, and / or any other suitable communication protocol, including communication protocols discussed or not discussed herein, or not yet developed as of the filing date of this document.

[0082] The communication interfaces 404 include, for example, hardware capable of data communications using any of a variety of custom or standard wireless protocols, and / or any of a variety7of custom or standard wired protocols, or any other suitable communication protocol, including communication protocols not yet developed as of the filing date of this document.

[0083] The memory 406 includes high-speed random-access memory, such as DRAM. SRAM, DDR RAM, or other random-access solid-state memory devices; and, optionally, includes nonvolatile memory, such as one or more magnetic disk storage devices, one or more optical disk storage devices, one or more flash memory devices, or one or more other non-volatile solid state storage devices. The memory 406, or alternatively the non-volatile memory within the memory 406, includes a non-transitory computer readable storage medium. In some implementations, the memory 406, or the non-transitory computer readable storage medium of the memory 406, stores the following programs, modules, and data structures, or a subset or superset thereof: operating logic 420 including procedures for handling various basic system senices and for performing hardware dependent tasks; a device communication module 422 for connecting to and communicating with other network devices (e.g., network interface 160, such as a router that provides Internet connectivity, networked storage devices, network routing devices, server system 164, etc.) connected to one or more networks 162 via one or more communication interfaces 404 (wired or wireless); an input processing module 426 for detecting one or more user inputs or interactions from the one or more input devices 414 and interpreting the detected inputs or interactions; a user interface module 428 for providing and displaying a user interface in which settings, captured data, and / or other data for one or more devices (e.g., the smart device 166, and / or other devices in smart-home environment 100) can be configured and / or viewed; one or more applications 430 for execution by the smart device (e.g., games, social network applications, smart home applications, and / or other web or non-web based applications) for controlling devices (e.g., executing commands, sending commands, and / or configuring settings of the smart device 166 and / or other client / electronic devices), and for reviewing data captured by devices (e.g., device status and settings, captured data, or other information regarding the smart device 166 and / or other client / electronic devices); a device-side module 432, which provides device-side functionalities for device control, data processing and data review, including but not limited to: a command receiving module 4320 for receiving, forwarding, and / or executing instructions andcontrol commands (e.g., from a client device, from a server system 164, from user inputs detected on the user interface 410, etc.) for operating the smart device 166; a data processing module 4322 for processing data captured or received by one or more inputs (e.g., input devices 414, image / video capture devices 418, location detection device 41 ), sensors (e.g., built-in sensors 490), interfaces (e.g., communication interfaces 404, radios 440), and / or other components of the smart device 166, and for preparing and sending processed data to a device for review (e.g., client devices for review by a user); device data 434 storing data associated with devices (e.g., the smart device 204), including, but is not limited to: account data 4340 storing information related to user accounts loaded on the smart device 166, wherein such information includes cached login credentials, smart device identifiers (e g., MAC addresses and UUIDs), user interface settings, display preferences, authentication tokens and tags, password keys, etc.; local data storage database 4342 for selectively storing raw or processed data associated with the smart device 166 (e.g., video surveillance footage captured by a camera 118); a bypass module 436 for detecting whether radio(s) 440 are transmitting signals via respective antennas coupled to the radio(s) 440 and to accordingly couple radio(s) 440 to their respective antennas either via a bypass line or an amplifier (e.g.. a low noise amplifier); and a transmission access module 438 for granting or denying transmission access to one or more radio(s) 440 (e.g., based on detected control signals and transmission requests).

[0084] Each of the above identified elements may be stored in one or more of the previously mentioned memory devices, and corresponds to a set of instructions for performing a function described above. The above identified modules or programs (i.e., sets of instructions) need not be implemented as separate software programs, procedures, or modules, and thus various subsets of these modules may be combined or otherwise rearranged in various implementations. In some implementations, the memory 406, optionally, stores a subset of the modules and data structures identified above. Furthermore, the memory 406, optionally, stores additional modules and data structures not described above.

[0085] FIG. 6A illustrates a simplified block diagram of a representative smart thermostat system 600 connected using wires to a modified legacy HVAC system 165A, according to some embodiments. System 600 can include: smart thermostat 102; and a modified legacy HVAC system 165 A that includes control board 302A.

[0086] In the example illustrated in FIG. 6A, the smart thermostat includes HVAC control wires 601 that include a power wire R, a Y1 wire to control stage 1 cooling, a Y2 wire to control stage 2 cooling, a W1 wire to control stage 1 heat pump, a W2 wire to control stage 2 heat pump, a G wireto control a fan, and a C common wire. In other examples, the HVAC control wires 610 may include fewer or more wires. The HVAC control wires are connected to the control board 302A that is configured to receive the control signals from the HVAC control wires.

[0087] In some configurations, the control board 302A includes a level shifter 604A and an MCU signal translator. The level shifter 604A is configured to translate the signals received from the smart thermostat 102 from one logic level or voltage domain to another, thereby allowing compatibility between circuits that have different voltage requirements. Depending on the circuits used in the smart thermostat 102 and / or the HVAC system 165 A. a level shifter 604A may / may not be utilized.

[0088] A microcontroller unit (MCU) signal translator 606A is configured to receive signals from the level shifter 604 and control the circuitry' of the legacy HVAC system 165A. The MCU signal translator 606A can incorporate a CPU (central processing unit), memory, and circuitry that implements the desired functionality to control the HVAC system 165A. In the current example, the MCU signal translator 606A is configured to receive signals R, Yl, Y2, Wl , W2, G, and C and output signals S (e.g., a 12v power signal), R used to start the compressor of the HVAC system 165 A, Cl used to set the fan speed to level 1, C2 used to set the fan speed to level 2, C3 used to set the fan speed to level 3, H to set the heat, and the common wire. The MCU signal translator 606A can be configured to control other types of HVAC systems 165.

[0089] FIG. 6B illustrates a simplified block diagram of a representative smart thermostat system 620 wirelessly connected to a modified legacy HVAC system 165B, according to some embodiments. System 620 can include: smart thermostat 102; and a modified legacy HVAC system 165B that includes control board 302B.

[0090] In the example illustrated in FIG. 6B, the smart thermostat is wireless connected to legacy HVAC system 165B. Instead of being connected via wires, the smart thermostat 102 is configured to wireless communicate instructions to control the HVAC system 165B. According to some configurations, the instructions may represent signal associated with HVAC control wires, such as HVAC control wires 601 (e.g., a power wire R, a Yl wire to control stage 1 cooling, a Y2 wire to control stage 2 cooling, a Wl wire to control stage 1 heat pump, a W2 wire to control stage 2 heat pump, a G wire to control a fan, and / or other wires). In other examples, the instructions may be associated with different functionality' of the HVAC system 165B, such as but not limited to turning on / off a fan, setting a fan speed, setting a temperature set point, turning on / off the heater, turning on / off a compressor, and the like.

[0091] In some configurations, the control board 302B includes a communication chipset, such as a thread chipset 608. As discussed above, thread is an IP-based wireless mesh networking technology, that is IPv6 based. Thread devices can join the same network as your other devices and talk directly to each other and the cloud. Thread is designed for Internet of Things (loT), and supports low-powered devices, such as battery -operated devices. The different Thread devices can form a mesh that delivers range and reliability. In other examples, a different communication chipset can be used.

[0092] A microcontroller unit (MCU) signal translator 606B is configured to receive input from the thread chipset 608 and control the circuitry of the legacy HVAC system 165B. The MCU signal translator 606B can incorporate a CPU (central processing unit), memory, and circuitry that implements the desired functionality to control the HVAC system 165B. In the current example, the MCU signal translator 606B is configured to output signals S (e.g., a 12v power signal), R used to start the compressor of the HVAC system 165B, Cl used to set the fan speed to level 1, C2 used to set the fan speed to level 2, C3 used to set the fan speed to level 3, H to set the heat, and the common wire. The MCU signal translator 606A can be configured to control other ty pes of HVAC systems 165.

[0093] Turning now to FIG. 7, a flowchart 700 of a method is illustrated for using a smart thermostat 102 to control a legacy HVAC device 165, according to some embodiments.

[0094] At 702, the smart thermostat is connected to a legacy HVAC system. As discussed above, the connection can be a wired / wireless connection. In some examples, a control board 302 is configured to receive wireless signals from the smart thermostat 102 and / or is configured to connect wires from smart thermostat 102 to inputs of the control board 302.

[0095] At 704. a determination is made to provide instructions to an HVAC system 165. As discussed above, the smart thermostat 102 may determine when to provide instructions to one or more HVAC systems 165. For instance, in some examples, the smart thermostat 102 may receive instructions from a server system 164 to perform an HVAC operation (e.g., generated in response to execution of an automation script, preferences of the user, and the like).

[0096] At 706. instructions can be generated for the HVAC system. As discussed above, the smart thermostat 102 may determine the type of HVAC system and generate instructions to control the desired functionality7of the HVAC system 165.

[0097] At 708, the instructions are provided to the HVAC system 165. As discussed above, the smart thermostat 102, and / or some other device / component may provide the instructions to the HVAC svstem 165.

[0098] FIG. 8 illustrates a flowchart 800 of a method for a legacy HVAC system 165 processing instructions received from a smart thermostat, according to some embodiments.

[0099] At 802, instructions are received from the smart thermostat 102. As discussed above, a control board 302 may be configured to receive instructions either through a wired connection and / or through a wireless connection.

[0100] At 804. a level shift can be performed when determine. As discussed above, some signals may need to be level shifted to work with the circuitry of the HVAC system 165. In these cases, a level shifter 604 may be used to shift the levels of the signals in order to work with the circuitry of the legacy HVAC system 165.

[0101] At 806, the signals / instructions are translated to control the desired operation of the HVAC system 165. As discussed above, an MCU signal translator 606 can be used to generate the signals.

[0102] At 808, the signals are provided to the HVAC system. As discussed above, the MCU signal translator 606 is configured to provide the signals to the circuitry’ of the HVAC system 165.

[0103] In the foregoing description, for the purposes of explanation, numerous specific details were set forth in order to provide a thorough understanding of various embodiments of the present invention, ft will be apparent, however, to one skilled in the art that embodiments of the present invention may be practiced without some of these specific details. In other instances, well-known structures and devices are shown in block diagram form.

[0104] The foregoing description provides exemplary' embodiments only, and is not intended to limit the scope, applicability, or configuration of the disclosure. Rather, the foregoing description of the exemplary embodiments will provide those skilled in the art with an enabling description for implementing an exemplary embodiment. It should be understood that various changes may be made in the function and arrangement of elements without departing from the spirit and scope of the invention as set forth in the appended claims.

[0105] Specific details are given in the foregoing description to provide a thorough understanding of the embodiments. However, it will be understood by one of ordinary skill in the art that the embodiments may be practiced without these specific details. For example, circuits,systems, networks, processes, and other components may have been show n as components in block diagram form in order not to obscure the embodiments in unnecessary detail. In other instances, well-known circuits, processes, algorithms, structures, and techniques may have been show n without unnecessary detail in order to avoid obscuring the embodiments.

[0106] Also, it is noted that individual embodiments may have been described as a process which is depicted as a flow chart, a flow7diagram, a data flow diagram, a structure diagram, or a block diagram. Although a flowchart may have described the operations as a sequential process, many of the operations can be performed in parallel or concurrently. In addition, the order of the operations may be re-arranged. A process is terminated when its operations are completed, but could have additional steps not included in a figure. A process may correspond to a method, a function, a procedure, a subroutine, a subprogram, etc. When a process corresponds to a function, its termination can correspond to a return of the function to the calling function or the main function.

[0107] The term '‘computer-readable medium’’ includes, but is not limited to portable or fixed storage devices, optical storage devices, wireless channels and various other mediums capable of storing, containing, or carrying instruction(s) and / or data. A code segment or machine-executable instructions may represent a procedure, a function, a subprogram, a program, a routine, a subroutine, a module, a software package, a class, or any combination of instructions, data structures, or program statements. A code segment may be coupled to another code segment or a hardw are circuit by passing and / or receiving information, data, arguments, parameters, or memorycontents. Information, arguments, parameters, data, etc., may be passed, forwarded, or transmitted via any suitable means including memory sharing, message passing, token passing, network transmission, etc.

[0108] Furthermore, embodiments may be implemented by hardware, software, firmw are, middleware, microcode, hardw are description languages, or any combination thereof. When implemented in software, firmware, middleware or microcode, the program code or code segments to perform the necessary tasks may be stored in a machine readable medium. A processor(s) may perform the necessary tasks.

[0109] In the foregoing specification, aspects of the invention are described with reference to specific embodiments thereof, but those skilled in the art will recognize that the invention is not limited thereto. Various features and aspects of the above-described invention may be used individually or jointly. Further, embodiments can be utilized in any number of environments andapplications beyond those described herein without departing from the broader spirit and scope of the specification. The specification and drawings are, accordingly, to be regarded as illustrative rather than restrictive.

[0110] Additionally, for the purposes of illustration, methods w ere described in a particular order. It should be appreciated that in alternate embodiments, the methods may be performed in a different order than that described. It should also be appreciated that the methods described above may be performed by hardware components or may be embodied in sequences of machineexecutable instructions, which may be used to cause a machine, such as a general-purpose or special-purpose processor or logic circuits programmed with the instructions to perform the methods. These machine-executable instructions may be stored on one or more machine readable mediums, such as CD-ROMs or other type of optical disks, floppy diskettes, ROMs, RAMs, EPROMs, EEPROMs, magnetic or optical cards, flash memory, or other types of machine- readable mediums suitable for storing electronic instructions. Alternatively, the methods may be performed by a combination of hardw are and software.

Claims

WHAT IS CLAIMED IS:

1. A method, comprising: establishing a connection between a smart thermostat and a control board retrofitted to a legacy HVAC device, wherein the control board includes a communication interface and a microcontroller unit (MCU); receiving, from the smart thermostat, input associated with controlling one or more operations of the legacy HVAC device; generating, via the microcontroller unit of the control board, one or more instructions to perform the one or more operations of the legacy HVAC device; and providing the one or more instructions to circuitry of the legacy HVAC device to perform the one or more operations.

2. The method of claim 1, wherein establishing the connection comprises establishing a wired connection to a plurality of HVAC control wires.

3. The method of claim 1, wherein establishing the connection comprises establishing a wireless connection.

4. The method of claim 1 , further comprising determining, by a cloud-based HVAC control server system, at least one of the one or more operations for the legacy HVAC device to perform.

5. The method of claim 1 , further comprising performing one or more level shift operations to adjust an input received from the smart thermostat to a compatible input to the circuitry of the MCU.

6. The method of claim 1, wherein generating, the one or more instructions to perform the one or more operations of the legacy HVAC device is based on a type of the legacy HVAC device.

7. The method of claim 6, further comprising determining, by a cloud-based HVAC control server system, a type of the legacy HVAC device.

8. The method of claim 1. wherein receiving the input associated with controlling the one or more operations of the legacy HVAC device is based, at least in part, on an automation script.

9. A system comprising: a smart thermostat and a control board retrofitted to a legacy HVAC device; one or more processors; and one or more memory devices comprising instructions that, when executed by the one or more processors, cause the one or more processors to perform operations comprising: establishing a connection between the smart thermostat and the control board; receiving, at the legacy HVAC device, input associated with controlling one or more operations of the legacy HVAC device; generating, via the control board, one or more instructions to perform the one or more operations of the legacy HVAC device; and causing the one or more instructions to execute on circuitry of the legacy HVAC device to perform the one or more operations.

10. The system of claim 9, wherein establishing the connection comprises one or more of establishing a wired connection to a plurality of HVAC control wires, or establishing a wireless connection.

11. The system of claim 9, further comprising a cloud-based HVAC server , wherein the cloud-based HVAC server is configured to determine at least one of the one or more operations for the legacy HVAC device to perform.

12. The system of claim 9, wherein the legacy HVAC device is further configured to perform one or more level shift operations to adjust an input received from the smart thermostat to a compatible input to the circuitry of the legacy HVAC device.

13. The system of claim 9, wherein generating the one or more instructions to perform the one or more operations of the legacy HVAC device is based on a type of the legacy HVAC device.

14. The system of claim 9, wherein the legacy HVAC device comprises: the control board including: a connection interface configured to connect to one or more smart thermostats; and one or more microcontroller units configured to generate the one or more instructions.

15. A non-transitory computer-readable medium comprising instructions that, when executed by one or more processors, cause the one or more processors to perform operations comprising: establishing a connection between a smart thermostat and a control board retrofitted to a legacy HVAC device, wherein the control board includes a communication interface and a microcontroller unit; receiving, from the smart thermostat, input associated with controlling one or more operations of the legacy HVAC device; generating, via the microcontroller unit of the control board, one or more instructions to perform the one or more operations of the legacy HVAC device; and providing the one or more instructions to circuitry of the legacy HVAC device to perform the one or more operations.

16. The non-transitory computer-readable medium of claim 15, wherein establishing the connection comprises establishing a wired connection to a plurality of HVAC control wires.

17. The non-transitory computer-readable medium of claim 15, wherein establishing the connection comprises establishing a wireless connection.

18. The non-transitory computer-readable medium of claim 15, comprising additional instructions that, when executed by the one or more processors, cause the one or more processors to perform additional operations comprising determining, by a cloud-based HVAC server, at least one of the one or more operations for the legacy HVAC device to perform.

19. The non-transitory computer-readable medium of claim 15, comprising additional instructions that, when executed by the one or more processors, cause the one or more processors to perform additional operations comprising performing one or more level shift operations to adjust an input received from the smart thermostat to a compatible input to the circuitry of the MCU.

20. The non-transitory computer-readable medium of claim 15, wherein generating, the one or more instructions to perform the one or more operations of the legacy HVAC device is based on a type of the legacy HVAC device.

Citation Information

Patent Citations

  • Stackable thermostat

    US20080147242A1

  • HVAC Communication Bus Decoders and Corresponding Methods

    US20150176854A1

  • Automated techniques for retrofitting devices

    US20170205807A1

  • HVAC forced air augmenting apparatus and method

    US20220018568A1