Patent Description:
Smart-home devices, such as smart outlets, smart lights, smart speakers, home assistant devices, smart thermostats, and smart hazard detectors are becoming common in homes worldwide. Effectively allowing a single controller device to control various smart-home devices that having varying capabilities and that receive commands from different cloud-based server systems can result in significant technical challenges.

<CIT> relates to a multi-function thermostat. Further, <CIT> describes an arbitration-based voice recognition in the context of an audio playback device.

Features of exemplary embodiments are defined in the dependent claims.

Smart-home devices may be controlled using a smart-home controller device. A smart-home controller device may be a wireless or mobile computerized device, such as a smartphone, tablet computer, laptop computer, dedicated home-controller device, or some other form of computerized device, that may execute an application that allows a user to control the functionality of one or more smart-home devices. The smart-home controller device may communicate with a cloud-based host server system. The cloud-based host system may communicate with various smart-home devices and may communicate with other cloud-based system to control smart-home devices that cannot be directly controlled by the cloud-based host system (e.g., smart devices manufactured and sold by other manufacturers).

The smart-home controller device may provide an interface that allows for smart-home devices to be controlled together and/or using a single input regardless of whether each smart-home device is controlled by the cloud-based host system or through another cloud-based system. The smart-home controller device may allow for smart-devices to be grouped based on location and/or function. Within such an arrangement, a common control element may be provided that allows a user to provide a single input that indicates a command that is to be implemented at multiple smart-home devices, regardless of whether the smart-home devices are controlled directly by the cloud-based host server system and/or through a separate cloud-based server system.

The smart-home controller device may additionally be configured to reclassify various types of smart-home devices based on user behavior. Such a reclassification may allow the smart-home controller device to determine when to send a command to a smart-home device more accurately and effectively. When a smart-home device is initially registered with the smart-home controller device or the registration is edited, a user may name the smart-home device and/or identify characteristics of the smart-home device. The words (and/or parts of words) submitted as part of the name may be compared to a smart-home device function database. The use of a particular word, part of a word, or phrase within a name of a smart-home device may be indicative of the smart-home device being used to perform a particular function. As an example, a smart outlet plug, if given the name of "dining room light" by a user, the smart outlet plug can be expected to control whether power is provided to a light located within the dining room. The smart-home controller device may classify the smart outlet plug in a lighting group (e.g., a dining room lighting group) because while the smart device is a smart outlet plug, it is effectively functioning as a controller for a light. Thus, if a user provides a command that indicates all of the lights within the dining room should be turned on or off, the smart-home controller device or cloud-based host server system may send the command to the smart outlet plug since it controls a light.

Additionally or alternatively, voice-based commands may be provided by a user to the smart-home controller device to control the functionality of multiple smart-home devices. The user may speak a command that does not correspond to a particular smart-home device or a predefined group of smart-home devices. For example, a user may say "turn on the dining room lights and the kitchen fan" or "turn off the dining room and the living room lights. " Embodiments detailed herein detail how a custom controller may be generated that controls at least one common function across all of the smart-home devices indicated in the spoken command. This interactive custom controller may allow a user to further change the state of the multiple smart-home devices that were the subject of the initial spoken command. The custom controller may include a graphical representation of a power button that, referring to the first example, controls both the dining room lights and the kitchen fan or, referring to the second example, all of the smart lights in the dining room and the living room. This custom controller may present some or all of the functions that all of the smart-home devices that were indicated in the spoken command have in common. Additionally or alternatively, the custom controller may present one or more functions that can only be performed at some of the smart-home devices indicated in the spoken command. For example, referring back to the example of the dining room lights and the kitchen fan, the custom controller may include a dimmer control that does not affect the state of the fan but allows at least a subset of the lights in the dining room to be dimmed via additional user input.

Further detail regarding the above embodiments and additional embodiments is provided in relation to the figures. While the following description is focused on smart-home devices, it should be understood that other forms of smart-devices may be controlled as detailed other than smart-home devices. For instance, smart devices in a factory, office, deployed in the field, or some other form of smart devices may be controlled as detailed herein. <FIG> illustrates a block diagram of an embodiment of a smart-home system <NUM>. Smart-home system <NUM> may include smart-home devices <NUM> (<NUM>-<NUM>, <NUM>-<NUM>, <NUM>-<NUM>, <NUM>-<NUM>, <NUM>-<NUM>); cloud-based host server system <NUM>; cloud-based server systems <NUM> (<NUM>-<NUM>, <NUM>-<NUM>); and smart-home controller devices <NUM>.

Smart-home devices <NUM> represent various smart-home devices that may be present in a particular structure <NUM> (e.g., a home, an apartment, a condominium, an office, a warehouse, a factory, etc.). Smart-home devices <NUM> may have differing sensors on-board and may or may not have the ability to output information (e.g., via sound, light, or an electronic display). Specific forms of smart-home devices <NUM> are detailed in relation to <FIG>. In the illustrated embodiment of system <NUM>, five smart-home devices <NUM> are presented. This number of smart-home devices is for example purposes only; in other embodiments, fewer or greater numbers of smart-home devices may be present within or at structure <NUM>. Each of smart-home devices <NUM> may be able to perform some form of function in response to a command received from an associated form of cloud-based server system (<NUM>, <NUM>). For example, possible commands may be instructions to turn on, turn off, dim, lock, unlock, play, pause, stop, turn the volume up, turn the volume down, mute, hush, turn the temperature up, turn the temperature down, etc..

Smart-home devices <NUM> may have been acquired from varying sources. For example, a first entity (e.g., manufacturer) may produce smart-home devices <NUM>-<NUM> and <NUM>-<NUM>, a second entity may produce smart-home device <NUM>-<NUM>, and a third entity may produce smart-home devices <NUM>-<NUM> and <NUM>-<NUM>. Such an arrangement in which smart-home devices from multiple entities is present within structure <NUM> may be fairly common: while a user may desire the feature set of one type of smart-home device, for another type of smart-home device, another entity may provide benefits that the user prefers.

Each smart-home device of smart-home devices <NUM> may communicate with a form of a cloud-based server system (<NUM>, <NUM>). That is, each entity that provides smart-home devices may operate or have operated on its behalf a cloud-based server system that can receive data from its associated smart-home devices and send data (e.g., commands) to its associated smart-home devices. Cloud-based host server system <NUM> may communicate directly with smart-home devices <NUM>-<NUM> and <NUM>-<NUM>. In this description, "directly" refers to the a server system communicating with a smart-home device via one or more networks without any additional intervening smart-home server systems. For example, the communication between smart-home device <NUM>-<NUM> and cloud-based host server system <NUM> may occur via a local wireless network (WLAN) provided by a router within structure <NUM>. The router may be connected to an Internet service provider (ISP) that provides a wired or wireless communication link to the Internet. Cloud-based host server system <NUM> may be connected with the Internet, thus allowing data to be passed between smart-home device <NUM>-<NUM> and cloud-based host server system <NUM>.

For other entities, separate cloud-based server systems may control associated smart-home devices: smart-home device <NUM>-<NUM> communicates directly with cloud-based server system <NUM>-<NUM> and smart-home devices <NUM>-<NUM> and <NUM>-<NUM> communicate directly with cloud-based server system <NUM>-<NUM>. Cloud-based host server system <NUM> can additionally communicate with other cloud-based server systems <NUM> through one or more application programming interfaces (APIs). Therefore, cloud-based host server system <NUM> can receive data from and control smart-home devices <NUM>-<NUM> through <NUM>-<NUM>, albeit not directly because communication via cloud-based server systems <NUM>-<NUM> and <NUM>-<NUM> is used. Further detail regarding cloud-based host server system <NUM> is provided in relation to <FIG>.

Smart-home controller devices <NUM> may serve as an interface for one or more users to interact with cloud-based host server system <NUM> to receive data from and control smart-home devices <NUM>. Some or all of smart-home controller devices <NUM> may each receive auditory commands in the form of speech spoken by a user. Further, each of smart-home controller devices <NUM> may have a display or touchscreen that allows graphical user interfaces (GUIs) to be presented to the users. Smart-home controller devices <NUM> can include: smartphone <NUM>; tablet computer <NUM>; and laptop computer <NUM>. Other forms of smart-home controller devices <NUM> may be possible, such as a dedicated smart-home device controller computerized device, a desktop computer, or a gaming device. Further detail regarding a smart-home controller device is provided in relation to <FIG>.

<FIG> illustrates an embodiment of a smart-home environment <NUM> with additional detail regarding smart-home devices. Smart-home <NUM> represents an embodiment of structure <NUM> that includes multiple smart-home devices. The depicted smart-home environment <NUM> includes a structure <NUM>, which can include, e.g., a house, office building, garage, or mobile home. It will be appreciated that devices can also be integrated into a smart-home environment <NUM> that does not include an entire structure <NUM>, such as an apartment, condominium, or office space. Further, the smart-home environment can control and/or be coupled to devices outside of the actual structure <NUM>. Indeed, several devices in the smart-home environment need not physically be within the structure <NUM> at all. For example, a device controlling a pool heater <NUM> or irrigation monitor <NUM> can be located outside of the structure <NUM>.

The depicted structure <NUM> includes a plurality of rooms <NUM>, separated at least partly from each other via walls <NUM>. The walls <NUM> can include interior walls or exterior walls. Each room can further include a floor <NUM> and a ceiling <NUM>. Devices can be mounted on, integrated with and/or supported by a wall <NUM>, floor <NUM> or ceiling <NUM>.

In some embodiments, the smart-home environment <NUM> of <FIG> includes a plurality of smart-home devices, including intelligent, multi-sensing, network-connected devices, that can integrate seamlessly with each other and/or with a central server or a cloud-computing system to provide any of a variety of useful smart-home objectives. The smart-home environment <NUM> may include one or more intelligent, multi-sensing, network-connected thermostats <NUM> (hereinafter referred to as "smart thermostats <NUM>"), one or more intelligent, network-connected, hazard detectors <NUM>, and one or more intelligent, multi-sensing, network-connected entryway interface devices <NUM> (hereinafter referred to as "smart doorbells <NUM>"). According to embodiments, the smart thermostat <NUM> detects ambient climate characteristics (e.g., temperature and/or humidity) and controls a HVAC system <NUM> accordingly. The hazard detector <NUM> may detect the presence of a hazardous substance or a substance indicative of a hazardous substance (e.g., smoke, fire, or carbon monoxide). The smart doorbell <NUM> may detect a person's approach to or departure from a location (e.g., an outer door), control doorbell functionality, announce a person's approach or departure via audio or visual means, or control settings on a security system (e.g., to activate or deactivate the security system when occupants go and come).

In some embodiments, the smart-home environment <NUM> of <FIG> further includes one or more intelligent, multi-sensing, network-connected wall switches <NUM> (hereinafter referred to as "smart wall switches <NUM>"), and/or with one or more intelligent, multi-sensing, network-connected outlet interfaces <NUM> (hereinafter referred to as "smart wall plugs <NUM>" or "smart outlets"). The smart wall switches <NUM> 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 <NUM> may also control a power state or speed of a fan, such as a ceiling fan. The smart wall plugs <NUM> (or smart outlet plugs) 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). Further, such smart wall plugs or smart outlet plugs may turn on or off electricity to a connected device based on a command received from an associated cloud-based server system (e.g., <NUM>, <NUM>-<NUM>, <NUM>-<NUM>).

In some embodiments, one or more smart indoor security cameras may be present such as indoor security camera <NUM>. Indoor security camera <NUM> may wirelessly communicate with a cloud server system to capture and record video and audio. Indoor security camera <NUM> may be able to detect motion, recognize a resident (e.g., via facial detection), and detect the presence of a resident or other person via audio (e.g., detection of a human voice). Indoor and outdoor security cameras may be used to determine when a resident leaves home (for example, an OBM behavior may be a time range during the day when a resident typically leaves home, such as between <NUM> AM and <NUM> PM) or returns home. In some embodiments, as previously detailed, this data may be supplemented with location data derived from an electronic device, such as a smartphone, that a resident typically carries when going out. If the smartphone is forgotten by the resident, data from the cameras may be used to determine that the smartphone has been left behind and the resident has left the residence (e.g., a camera detects the resident leaving, the smartphone remains stationary in the residence, and there is no movement detected within the residence for a threshold period of time). When the environment is darkened, indoor security camera <NUM> may use infrared to detect the presence of a resident and/or other persons in the camera's field-of-view.

In some embodiments, one or more smart outdoor security cameras may be present such as outdoor security camera <NUM>. Outdoor security camera <NUM> may wirelessly communicate with a cloud server system to capture and record video and audio and may function similarly to indoor security camera <NUM>. Outdoor security camera <NUM> may include weatherproofing to protect against the outdoor environment. Outdoor security camera <NUM> may be able to detect motion, recognize a resident (e.g., via facial detection), and detect the presence of a resident or other person via audio (e.g., detection of a human voice). At night, outdoor security camera <NUM> may use infrared to detect the presence of a resident and/or other persons in the camera's field-of-view.

In some embodiments, one or more home assistant devices may be present in the residence, such as home assistant device <NUM>. Home assistant device <NUM> may include one or more microphones. Home assistant device <NUM> may detect and analyze human speech and may be able to detect speech and/or movement by the resident. Clips of captured human speech may be provided to cloud-based host server system <NUM> for analysis. A response may be provide to home assistant device <NUM>, which may output the response in the form of spoken audio. Cloud-based host server system <NUM> may cause one or more other smart-home devices in home environment <NUM> to perform a function based on a command identified from the received human speech.

Still further, in some embodiments, the smart-home environment <NUM> of <FIG> includes a plurality of intelligent, multi-sensing, network-connected appliances <NUM> (hereinafter referred to as "smart appliances <NUM>"), such as refrigerators, stoves and/or ovens, televisions, washers, dryers, lights, stereos, intercom systems, garage-door openers, floor fans, ceiling fans, wall air conditioners, pool heaters, irrigation systems, security systems, and so forth. According to embodiments, the network-connected appliances <NUM> are made compatible with the smart-home environment by cooperating with the respective manufacturers of the appliances. For example, the appliances can be space heaters, window AC units, motorized duct vents, etc. When plugged in, an appliance can announce itself to the smart-home network, such as by indicating what type of appliance it is, and it can automatically integrate with the controls of the smart-home. Such communication by the appliance to the smart-home can be facilitated by any wired or wireless communication protocols known by those having ordinary skill in the art. The smart-home also can include a variety of non-communicating legacy appliances <NUM>, such as old conventional washer/dryers, refrigerators, lights, and the like which can be controlled, albeit coarsely (ON/OFF), by virtue of the smart wall plugs <NUM>. The smart-home environment <NUM> can further include a variety of partially communicating legacy appliances <NUM>, such as infrared ("IR") controlled wall air conditioners or other IR-controlled devices, which can be controlled by IR signals provided by the hazard detectors <NUM> or the smart wall switches <NUM>.

According to embodiments, the smart thermostats <NUM>, the hazard detectors <NUM>, the smart doorbells <NUM>, the smart wall switches <NUM>, the smart wall plugs <NUM>, and other devices of the smart-home environment <NUM> are modular and can be incorporated into older and new houses. For example, the devices are designed around a modular platform consisting of two basic components: a head unit and a back plate, which is also referred to as a docking station. Multiple configurations of the docking station are provided so as to be compatible with any home, such as older and newer homes. However, all of the docking stations include a standard head-connection arrangement, such that any head unit can be removably attached to any docking station. Thus, in some embodiments, the docking stations are interfaces that serve as physical connections to the structure and the voltage wiring of the homes, and the interchangeable head units contain all of the sensors, processors, user interfaces, the batteries, and other functional components of the devices.

The smart-home environment <NUM> 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 <NUM> may include a pool heater monitor <NUM> that communicates a current pool temperature to other devices within the smart-home environment <NUM> or receives commands for controlling the pool temperature. Similarly, the smart-home environment <NUM> may include an irrigation monitor <NUM> that communicates information regarding irrigation systems within the smart-home environment <NUM> and/or receives control information for controlling such irrigation systems. According to embodiments, an algorithm is provided for considering the geographic location of the smart-home environment <NUM>, such as based on the zip code or geographic coordinates of the home. The geographic information is then used to obtain data helpful for determining optimal times for watering; such data may include sun location information, temperature, due point, soil type of the land on which the home is located, etc..

By virtue of network connectivity, one or more of the smart-home devices of <FIG> can further allow a user to interact with the device even if the user is not proximate to the device. For example, a user can communicate with a device using a computer (e.g., a desktop computer, laptop computer, or tablet) or other portable electronic device <NUM> (e.g., a smartphone). A webpage or app can 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 can view a current setpoint temperature for a device and adjust it, using a computer. The user can be in the structure during this remote communication or outside the structure.

As discussed, users can control and interact with the smart thermostat, hazard detectors <NUM>, and other smart devices in the smart-home environment <NUM> using a network-connected computer or portable electronic device <NUM>. In some examples, some or all of the occupants (e.g., individuals who live in the home) can register their electronic device <NUM> with the smart-home environment <NUM>. Such registration can be made at cloud-based host server system <NUM> (or whichever cloud-based server system is associated with the entity that provided the smart-home devices to be controlled) 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 can use their registered electronic device <NUM> 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 electronic devices <NUM>, the smart-home environment <NUM> makes inferences about which individuals live in the home and are therefore occupants and which electronic devices <NUM> are associated with those individuals. As such, the smart-home environment "learns" who is an occupant and permits the electronic devices <NUM> associated with those individuals to control the smart devices of the home.

In some embodiments, in addition to containing processing and sensing capabilities, each of the devices <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, and <NUM> (collectively referred to as "the smart devices") is capable of data communications and information sharing with any other of the smart devices, as well as to any central server or cloud-computing system or any other device that is network-connected anywhere in the world. The required data communications can be carried out using any of a variety of custom or standard wireless protocols (Wi-Fi, ZigBee, 6LoWPAN, etc.) and/or any of a variety of custom or standard wired protocols (CAT6 Ethernet, HomePlug, etc.).

According to embodiments, all or some of the smart devices can serve as wireless or wired repeaters. For example, a first one of the smart devices can communicate with a second one of the smart devices via a wireless router <NUM>. The smart devices can further communicate with each other via a connection to a network, such as the Internet <NUM>. Through the Internet <NUM>, the smart devices can communicate with a cloud-computing system <NUM>, which can include one or more centralized or distributed server systems. The cloud-computing system <NUM> can be associated with a manufacturer, support entity, or service provider associated with the device. For one embodiment, a user may be able to contact customer support using a device itself rather than needing to use other communication means such as a telephone or Internet-connected computer. Further, software updates can be automatically sent from cloud-computing system <NUM> to devices (e.g., when available, when purchased, or at routine intervals).

According to embodiments, the smart devices combine to create a mesh network of spokesman and low-power nodes in the smart-home environment <NUM>, where some of the smart devices are "spokesman" nodes and others are "low-powered" nodes. Some of the smart devices in the smart-home environment <NUM> 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 <NUM> of the smart-home environment. The smart devices that have a regular and reliable power source are referred to as "spokesman" nodes. These nodes are equipped with the capability of using any wireless protocol or manner to facilitate bidirectional communication with any of a variety of other devices in the smart-home environment <NUM> as well as with the cloud-computing system <NUM>. On the other hand, the devices that are battery powered are referred to as "low-power" nodes. These nodes tend to be smaller than spokesman nodes and can only communicate using wireless protocols that require very little power, such as Zigbee, 6LoWPAN, etc. Further, some, but not all, low-power nodes are incapable of bidirectional communication. These low-power nodes send messages, but they are unable to "listen". Thus, other devices in the smart-home environment <NUM>, such as the spokesman nodes, cannot send information to these low-power nodes.

As described, the smart devices serve as low-power and spokesman nodes to create a mesh network in the smart-home environment <NUM>. Individual low-power nodes in the smart-home environment 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 - repeat the messages, thereby causing the messages to travel from node to node (i.e., device to device) throughout the smart-home environment <NUM>. The spokesman nodes in the smart-home environment <NUM> are able to "drop down" to low-powered communication protocols to receive these messages, translate the messages to other communication protocols, and send the translated messages to other spokesman nodes and/or cloud-computing system <NUM>. Thus, the low-powered nodes using low-power communication protocols are able to send messages across the entire smart-home environment <NUM> as well as over the Internet <NUM> to cloud-computing system <NUM>. According to embodiments, the mesh network enables cloud-computing system <NUM> to regularly receive data from all of the smart devices in the home, make inferences based on the data, and send commands back to one of the smart devices to accomplish some of the smart-home objectives described herein.

As described, the spokesman nodes and some of the low-powered nodes are capable of "listening. " Accordingly, users, other devices, and cloud-computing system <NUM> can communicate controls to the low-powered nodes. For example, a user can use the portable electronic device <NUM> (e.g., a smartphone) to send commands over the Internet to cloud-computing system <NUM>, which then relays the commands to the spokesman nodes in the smart-home environment <NUM>. The spokesman nodes drop down to a low-power protocol to communicate the commands to the low-power nodes throughout the smart-home environment, as well as to other spokesman nodes that did not receive the commands directly from the cloud-computing system <NUM>.

An example of a low-power node is a smart nightlight <NUM>. In addition to housing a light source, the smart nightlight <NUM> houses an occupancy sensor, such as an ultrasonic or passive IR sensor, and an ambient light sensor, such as a photoresistor or a single-pixel sensor that measures light in the room. In some embodiments, the smart nightlight <NUM> 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 embodiments, the smart nightlight <NUM> is simply configured to activate the light source when its ambient light sensor detects that the room is dark. Further, according to embodiments, the smart nightlight <NUM> includes a low-power wireless communication chip (e.g., 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 mentioned above, these messages may be sent wirelessly, using the mesh network, from node to node (i.e., smart device to smart device) within the smart-home environment <NUM> as well as over the Internet <NUM> to cloud-computing system <NUM>.

Other examples of low-powered nodes include battery-operated versions of the hazard detectors <NUM>. These hazard detectors <NUM> are often located in an area without access to constant and reliable (e.g., structural) power and, as discussed in detail below, may include any number and type of sensors, such as smoke/fire/heat sensors, carbon monoxide/dioxide sensors, occupancy/motion sensors, ambient light sensors, temperature sensors, humidity sensors, and the like. Furthermore, hazard detectors <NUM> can send messages that correspond to each of the respective sensors to the other devices and cloud-computing system <NUM>, such as by using the mesh network as described above.

Examples of spokesman nodes include smart doorbells <NUM>, smart thermostats <NUM>, smart wall switches <NUM>, and smart wall plugs <NUM>. These devices <NUM>, <NUM>, <NUM>, and <NUM> are often located near and connected to a reliable power source, and therefore can include more power-consuming components, such as one or more communication chips capable of bidirectional communication in any variety of protocols.

Further included and illustrated in the exemplary smart-home environment <NUM> of <FIG> are service robots <NUM> each configured to carry out, in an autonomous manner, any of a variety of household tasks. For some embodiments, the service robots <NUM> can be respectively configured to perform floor sweeping, floor washing, etc. Tasks such as floor sweeping and floor washing can be considered as "away" or "while-away" tasks for purposes of the instant description, as it is generally more desirable for these tasks to be performed when the occupants are not present. For other embodiments, one or more of the service robots <NUM> are configured to perform tasks such as playing music for an occupant, serving as a localized thermostat for an occupant, serving as a localized air monitor/purifier for an occupant, serving as a localized baby monitor, serving as a localized hazard detector for an occupant, and so forth, it being generally more desirable for such tasks to be carried out in the immediate presence of the human occupant. For purposes of the instant description, such tasks can be considered as "human-facing" or "human-centric" tasks.

As noted in relation to <FIG>, not all of the above detailed smart-home devices may be associated with a same manufacturer or entity that provides service for the smart-home device. Therefore, the smart-home devices in smart-home environment <NUM> may be controlled using different cloud-based server systems. For example, smart-home devices made by a first manufacturer may be controlled via cloud-based host server system <NUM>, while smart-home devices made by a second manufacturer may be controlled via cloud-based server system <NUM>-<NUM> and smart-home devices made by a third manufacturer may be controlled via cloud-based server system <NUM>-<NUM>. By way of example, three cloud-based server systems, including cloud-based host server system is illustrated in <FIG>; in other embodiments, a greater or fewer number of cloud-based server systems may be present.

<FIG> illustrates a block diagram of an embodiment of a cloud-based host server system <NUM>. Cloud-based host server system <NUM> may communicate directly with various smart-home devices, may interface with other cloud-based server systems (to communicate indirectly with smart-home devices provided by third-party manufacturers), and/or may analyze recorded voice samples received from smart-home devices. Cloud-based host server system <NUM> may include one or more computer server systems that include components such as network interfaces, processors, communication buses, non-transitory computer readable storage mediums, memories, etc. Various components illustrated as part of cloud-based host server system may be performed using dedicated special-purpose hardware, firmware, or general-purpose hardware executing special-purpose software. It should be understood that the various components of cloud-based host server system <NUM> may be broken out into a greater number of components or combined into a fewer number of components in different embodiments. Cloud-based host server system <NUM> may include: smart device control engine <NUM>; controller communication interface <NUM>; audio communication interface <NUM>; semantics engine <NUM>; assistant engine <NUM>; smart device cloud API <NUM>; direct smart-device control API <NUM>; smart-device control library <NUM>; and one or more smart device and account databases <NUM>.

Direct smart device control API <NUM> may be used to communicate directly with various smart-home devices. The smart devices controlled via direct smart device control API <NUM> may be manufactured or otherwise distributed by a same entity that operates or has cloud-based host server system <NUM> operated on its behalf. Through direct smart device control API <NUM>, data from various smart-home devices may be received and commands may be transmitted to such smart-home devices. Direct smart device control API <NUM> may format commands appropriately for communication to smart devices and may format received data appropriately for analysis by smart device control engine <NUM>. In contrast, smart device cloud API <NUM> may be used to communicate with various smart-home devices through other cloud-based server systems. The smart devices controlled via smart device cloud API <NUM> may be manufactured or otherwise distributed by a different entity than the entity that operates or has cloud-based host server system <NUM> operated on its behalf. Through smart device cloud API <NUM>, data from various third-party smart-home devices may be received and commands may be transmitted to such third-party smart-home devices. Smart device cloud API <NUM> may format commands appropriately for communication to smart devices and may format received data appropriately for analysis by smart device control engine <NUM>. Therefore, smart device cloud API <NUM> may have access to a library of command types and data types available for each third-party smart device.

Controller communication interface <NUM> may communicate with various smart-home controller devices. Through controller communication interface <NUM>, requests for a command to be executed by one or more smart-home devices may be received. In some situations, the command may be intended to be executed by one or more smart-home devices directly communicated with by cloud-based host server system <NUM> via direct smart device control API <NUM> and one or more smart devices indirectly communicated with via smart device cloud API <NUM>. Controller communication interface <NUM> may also be used by smart device control engine <NUM> to send information about data received from smart devices that communicate with cloud-based host server system <NUM> via smart device cloud API <NUM> and direct smart device control API <NUM>.

Smart device control library <NUM> may be a library of the various functions that can be performed using smart devices that are directly communicated with via direct smart device control API <NUM>. When a type of smart device is registered with cloud-based host server system <NUM>, smart device control library <NUM> may be accessed to determine the particular functions which the smart device can perform and the particular commands available to be transmitted to smart-device control library <NUM>.

Smart device and account databases <NUM> may serve to store indications of smart-home devices that have been registered with cloud-based host server system <NUM> with a particular user account. Requests to control a smart-home device received via controller communication interface <NUM> may be required to be linked with the same user account as indicated in smart device an account databases <NUM> for security purposes. Therefore, a user may only have permission to control the smart-home devices that have been linked to the user's account. In some embodiments, a user name and password is required to access the user account. In other embodiments, additional security measures may be taken, such as biometrics or two-factor identification. One or more smart device an account databases <NUM> may also store indications of third-party smart-home devices that have been registered with cloud-based host server system <NUM>.

Audio communication interface <NUM> may serve to receive an audio clip captured by a smart-home controller, home assistant device, or some other smart-home device through which a user can submit a spoken command. Semantics engine <NUM> may perform natural language processing to determine what the user said, possibly including: a command; and the device for which the command is intended. Synthesized voice responses may be provided in response to the user via audio communication interface <NUM>.

Vocal or spoken commands that are not directed to smart-home devices may be processed by assistant engine <NUM>. For example, such spoken commands may be requesting data from some other source, such as the Internet. As an example, a request may be for weather information, the time, sports scores, a translation, a stock quote, calendar information, etc. semantics engine <NUM> may route smart-home device requests to smart device control engine <NUM>.

Smart device control engine <NUM> may receive commands from controller communication interface <NUM> and as interpreted by semantics engine <NUM>. Smart device control engine <NUM> may access smart device and account databases <NUM> to determine the smart devices associated with a particular account. Smart-device control engine may determine the appropriate smart-home devices to transmit a command and may transmit the command via smart device cloud API <NUM> (to the corresponding cloud-based server system that communicates directly with the smart-home device) and via direct smart device control API <NUM>. Smart device control engine <NUM> may send smart device identifiers indicative of the smart devices that have been sent a command based on a spoken command to the smart-home controller via controller communication interface <NUM>. Therefore, smart-home controller may receive information identifying the smart-home devices that were affected by a spoken command.

<FIG> illustrates a block diagram of an embodiment of a smart-home controller device. Smart-home controller device <NUM> may perform multiple functions, including: presenting a graphical interface for a user to view the status of and control multiple smart-home devices (of which some of the smart-home devices may be controlled via different entities' cloud-based server systems); and receive and send vocal commands spoken by a user. Smart-home control device <NUM> may be a computerized device that includes components such as wireless (and/or wired) network interfaces, processors, communication buses, non-transitory computer readable storage mediums, memories, etc. Various components illustrated as part of smart-home controller device <NUM> may be performed using dedicated special-purpose hardware, firmware, or general-purpose hardware executing special-purpose software. It should be understood that the various components of smart-home controller device <NUM> may be broken out into a greater number of components or combined into a fewer number of components in different embodiments. Smart-home controller device <NUM> may include: voice-based assistant engine <NUM> and smart-home control application <NUM>, which may be executed by underlying processing hardware of smart-home controller device <NUM>. In some embodiments, smart-home control application <NUM> is downloaded onto smart-home controller device <NUM> from an application store. In other embodiments, smart-home controller device <NUM> may be purpose-built to have the functionality of smart-home control application <NUM>. Voice-based assistant engine <NUM> may be triggered by a user speaking a key phrase or a user providing input to initiate listening. The user may then speak a vocal command that is passed to the cloud-based host server system for analysis and execution. A synthesized speech response may be output by voice-based assistant engine <NUM> based on data received in response to the vocal command passed to the cloud-based server system. Voice-based assistant engine <NUM> may execute regardless of whether smart-home control application <NUM> is being executed. In some embodiments, voice-based assistant engine <NUM> is incorporated as part of an operating system (OS) being executed by smart-home controller device <NUM>.

Smart-home control application <NUM> may include: smart-home control interface creation engine <NUM>; smart-home device registration engine <NUM>; customized controller interface generation engine <NUM>; voice-based assistant engine <NUM>; function-specific term database <NUM>; and smart-home device function database <NUM>. Smart-home device registration engine <NUM> may receive information about a new smart-home device that is the registered with smart-home control application <NUM> and cloud-based host server system <NUM>, regardless of whether the smart-home device is directly controlled by cloud-based host server system or controlled via another cloud-based server system. As part of the registration process, a user may be requested to provide information about the smart-home device. For example, the user may be requested to provide a name for the smart-home device. The user may typically name the smart-home device based on the function performed by the smart-home device and the location. For example, a user may select a name such as "kitchen light" to describe a smart light in the kitchen. As another example, "kitchen light" may be used for a smart outlet plug in the kitchen to which a conventional light is connected. Registration data received by smart-home device registration engine <NUM> may be stored locally and may also be transmitted to cloud-based host server system <NUM>. Functions that can be performed by the smart-home device may be discovered during the smart-home device registration process. Indications of such functions may be stored to smart-home device function database <NUM> in association with an identifier of the smart-home device. Indications of the available functions may be retrieved from the cloud-based host computer system. For third-party smart-home devices, the cloud-based host computer system may request and retrieve indications of such functions from the cloud-based server system operated by the entity that provided the third-party smart-home device. Alternatively, the cloud-based host server system may maintain a database of available functions of third-party smart-home devices.

When the user provides a name for a smart-home device as part of the registration process, if the ultimate function of the smart-home device is not inherently determined by the type of smart device itself, function-specific term database <NUM> may be used to determine the intended use of a smart-home device from the user's name for the smart-home device. For example, a smart outlet plug can be used to control a variety of types of devices, such as a legacy appliance, a light, electronics, etc. A user may be expected to name the smart outlet plug something related to the device it is controlling, such as "bedroom window fan" or "dining room light. " Function specific term database may store a variety of terms that are linked to a specific category of smart-home device. Table <NUM> provides some examples of terms and the associated smart-home device categories.

If, during the registration process, a user provides a function specific term in the name of the smart-home device that performs an ambiguous function, based on the function specific term being present, smart-home device registration engine <NUM> may classify the smart-home device as being part of the smart-home device category mapped to the function specific term. For example, a smart outlet plug that has been named "dining room lamp" may be classified as part of the lighting smart-home device category. While <FIG> shows function specific term database <NUM> as part of smart-home control application <NUM>, in other embodiments, function-specific term database <NUM> may be remotely located and may be accessible by smart-home device registration engine <NUM>. For instance, function-specific term database <NUM> may be stored by cloud-based host server system <NUM>.

Voice-based assistant engine <NUM> may function similarly to voice-based assistant engine <NUM>, but may be incorporated as part of smart-home control application <NUM> and may specifically be used for providing smart-home related commands. Voice-based assistant engine <NUM> may capture an audio clip via a microphone of the smart-home controller device <NUM> in response to a user saying a trigger phrase or providing some form of user input indicating that the user desires to provide a voice-based command. The captured audio may be transmitted from voice-based assistant engine <NUM> to audio communication interface <NUM> of cloud-based host server system <NUM>. The audio may be analyzed at the cloud-based host server system rather than at smart-home controller device <NUM>. In response to sending the captured audio, voice-based assistant engine <NUM> may receive a response from the cloud-based host computer system indicating the smart-home identifiers of the smart-home devices that were sent to command based on a spoken command in the captured audio. The response may also indicate the updated state of the smart-home devices to which the command was sent.

Smart-home control interface creation engine <NUM> may create graphical interfaces that can be interacted with by user via a touchscreen or other form of user input device and is presented by smart-home controller device <NUM> or otherwise output for presentation (e.g., to a separate monitor). Smart-home control interface creation engine <NUM> may create an output user interfaces such as those detailed in relation to <FIG>. Smart-home control interface creation engine <NUM> may create individual tiles or coins that control both smart-home devices via direct smart device control API <NUM> and third-party smart-home devices via smart device cloud API <NUM>.

Smart-home device function database <NUM> may store an indication of each smart-home device that is controlled via smart-home control application <NUM> and the functions that can be performed at each of the smart-home devices. For example, many smart-home devices may be able to be turned on and off, some smart lights may be able to be dimmed, smart thermostats may be able to receive a temperature setting, etc. Smart-home device function database <NUM> may be accessed by smart-home control interface creation engine <NUM> to determine the functions that can be performed by a particular smart-home device. Smart-home control interface creation engine <NUM> may access smart-home device function database <NUM> to determine what functions are in common across particular smart-home devices such that a single control can be presented that controls multiple smart-home devices, even if some of such smart-home devices are provided by different entities and are controlled via different cloud-based server systems.

Customized controller interface generation engine <NUM> may be used in conjunction with voice-based assistant engine <NUM>. In response to a voice command, voice-based assistant engine <NUM> may receive smart device identifiers for the smart devices affected by a spoken command. When these smart device identifiers are received, the identifiers may be passed to customized controller interface generation engine <NUM>. Customized controller interface generation engine <NUM> may access smart-home device function database <NUM> to determine one or more functions that each of the smart-home devices have in common. A graphical control may be created that allows a user to control the same group of smart-home devices that was indicated in the spoken command. This control may include at least one common function across each of the smart-home devices. The control may also include one or more functions that are specific to a subset of the smart-home devices that was indicated in the spoken command. Therefore, customized controller interface generation engine <NUM> may generate a graphical interface after a spoken command has been submitted via voice-based assistant engine <NUM> and may allow a user to provide user input in the form of touch or some other form of on-screen control for the same set of smart-home devices that was previously controlled via a vocal command. Additionally or alternatively, customized controller interface generation engine <NUM> may be used with voice-based assistant engine <NUM>.

<FIG> represent various control interfaces that may be presented by smart-home controller devices <NUM>. In the illustrated embodiments, a smartphone <NUM> is used as an example of the smart-home controller device. In some embodiments, the control interfaces are presented using a touchscreen, in other embodiments, a separate user input device, such as a mouse is used to interact with the control interfaces. <FIG> represent control interfaces that may be output by smart-home control application <NUM> for presentation by smart-home controller device <NUM> or a display device connected with smart-home controller device <NUM>. <FIG> illustrates an embodiment of a control interface <NUM> that may be presented by a smart-home controller device, such as smartphone <NUM>.

Top interface region <NUM> is devoted to whole-home smart-device controls. Top interface region <NUM> is labeled with location <NUM> that is indicative of the entire structure or other form of place where the smart-home devices are installed. Controls with top interface region <NUM> can include: off element <NUM>; on element <NUM>; play element <NUM>; thermostat element <NUM>; camera element <NUM>; add element <NUM>; and settings element <NUM>.

The controls indicated by elements <NUM>-<NUM> pertain to smart-home devices controlled directly via the cloud-based host server system and third-party smart-home devices controlled by the cloud-based host server system via another cloud-based server system operated by another entity. Off element <NUM>, when selected by a user, may trigger the smart-home control application to instruct the cloud-based host server system to turn off all lighting-related smart-home devices at location <NUM> that are located in lower location subcategories. (In other embodiments, when off element <NUM> is selected, a choice may be presented as to whether to turn off lighting-related devices for a given room or within the entire structure. ) On element <NUM>, when selected by a user, may trigger the smart-home control application to instruct the cloud-based host server system to turn on all lighting-related smart-home devices at location <NUM> that are located in lower location subcategories. (In other embodiments, when on element <NUM> is selected, a choice may be presented as to whether to turn off lighting-related devices for a given room or within the entire structure. ) Play element <NUM>, when selected by a user, may trigger the smart-home control application to instruct the cloud-based host server system to play or cease playing sound via eligible smart-home devices at location <NUM> that are located in lower location subcategories. Thermostat element <NUM>, when selected by a user, may trigger the smart-home control application to instruct the cloud-based host server system to adjust the temperature or adjust an away/home setting at all smart thermostats installed in location <NUM> that are located in lower location subcategories. Camera element <NUM>, when selected by a user, may trigger the smart-home control application to instruct the cloud-based host server system to stream video feeds to the smart-home control device for presentation from all cameras installed at location <NUM> that are located in lower location subcategories. Add element <NUM> may allow an additional function to be added to top interface region <NUM> based on one or more smart-home devices present in lower location subcategories. Alternatively, add element <NUM> may be used to link or register a new device. Settings element <NUM>, when selected by a user, may trigger the smart-home control application to present various settings that a user is permitted to adjust for controlling smart-home devices located in lower location subcategories.

Based on received registration information received from a user via smart-home device registration engine <NUM>, smart-home devices may be classified into one or more location subcategories. Location subcategories may be presented within control interface <NUM> at a lower location than top interface region <NUM>. A first location subcategory presenting in control interface <NUM> is location subcategory <NUM> that has location <NUM> of "Attic. " A user may specify location <NUM> and indicate which smart-home devices are installed at location <NUM>. All smart-home devices indicated as being at location <NUM> are included in location subcategory <NUM>. In the illustrated embodiment, three smart-home devices (of which at least some may be third-party smart-home devices) is indicated by smart-home device count <NUM>, which is presented near location <NUM>. In the illustrated embodiment, two lights are present at location <NUM>, therefore control element <NUM>, which may also be referred to as a control "coin" or "tile" is presented that includes: <NUM>) a graphic that represents a group of the type of smart-home device and may be selected to present control elements for the individual lights; <NUM>) a title of the group of lights ("Attic lights"), and control elements that allow the group of lights to be controlled using a single user input (by a user selecting "off' or "on"). Additionally, location subcategory <NUM> may include a smart-home device (in this case, a home assistant device) that can be used as a speaker. Control element <NUM> include: <NUM>) a graphic element that represents the type of smart-home device; and <NUM>) a user-assigned title of the smart-home device. Additional location subcategories may be presented by control interface <NUM> by a user scrolling down, such as seen in the embodiment of <FIG>.

Additionally present in control interface <NUM> is spoken command control element <NUM>. By a user selecting audio command control element <NUM>, voice-based assistant engine <NUM> may be activated to capture audio using a microphone of smart-home controller device <NUM>. This audio may be transmitted to cloud-based host server system <NUM> for analysis. When a user scrolls up or down within control interface <NUM>, spoken command control element <NUM> remains fixed on control interface <NUM> such that while smart-home control application <NUM> is open, the user has an on-screen option to provide a spoken command to control the smart-home devices.

<FIG> illustrates an embodiment of a control interface <NUM> that may be presented by a smart-home controller device that includes grouped smart-home devices based on location. In control interface <NUM>, location subcategories <NUM> and <NUM> are presented. Location subcategory <NUM> corresponds to location <NUM> and has four devices as indicated by smart-home device count <NUM>. If a user selects location <NUM>, interface <NUM> of <FIG> may be presented. In the illustrated embodiment, three lights are present at location <NUM>, therefore control element <NUM> may include: <NUM>) a graphic that represents a group of the type of smart-home device and may be selected to present control elements for the individual lights and/or the current state of the group of lights; <NUM>) a title of the group of lights ("Dining room lights"), and control elements that allow the group of lights to be collectively controlled using a single user input (by a user selecting "off' or "on"). Control element <NUM> may allow a user to pair a speaker at location <NUM> with a source (e.g., the smart-home control device) for output of sound.

Location subcategory <NUM> which corresponds to location <NUM> only includes one smart-device as indicated by smart-device count <NUM>. Control element <NUM> visually represents a smart door lock and indicates the current state of the door lock (unlocked).

<FIG> illustrates an embodiment of a control interface <NUM> that may be presented by smart-home controller device <NUM> for a particular location subcategory. Control interface <NUM> may be presented when a user selects location <NUM> in control interface <NUM>. In interface <NUM>, control elements are presented for: <NUM>) groups of smart-home devices of the same type; and <NUM>)each individual smart-home device. Control element <NUM> and control element <NUM> may function as detailed in relation to <FIG>. Additionally, control elements <NUM>, <NUM>, and <NUM> are presented. Control element <NUM> may correspond to a smart light that is directly controlled by cloud-based host server system <NUM> via direct smart device control API <NUM>. Control element <NUM> may correspond to a smart light made or distributed by another entity that is controlled by cloud-based host server system <NUM> via smart-device cloud API <NUM> and the entity's cloud-based server system. The graphical representations presented as part of control elements <NUM> and <NUM> may differ to illustrate the that each smart light is from a different manufacturer or entity. However, both of these smart lights can be controlled using the single control of control element <NUM>.

Control element <NUM> comprises a graphical representation of a smart outlet plug. This smart outlet plug may have been grouped as part of the smart lights of location <NUM> on the basis of the name for the smart outlet plug provided for a user including the word "lamp. " The graphical representation may remain as a smart outlet plug. In some embodiments the smart outlet plug is included as part of location <NUM> based on the word "dining" being used as part of the user-provided name.

<FIG> illustrates an embodiment of a control interface <NUM> that may be presented by smart-home controller device <NUM> that can be used to control multiple smart-home devices. Control interface <NUM> may be presented when control element <NUM> in selected from control interface <NUM> or interface <NUM>. Of control interface <NUM>, at least one control element controls all smart-elements within the selected group <NUM>. Smart device count <NUM> indicates the number of smart devices that are controlled by the at least one control element that controls all smart-elements within the selected group <NUM>. Control interface <NUM> may allow a single user input to control multiple smart lights which include smart lights controlled directly by cloud-based host server system and smart lights controlled via another cloud-based server system. Power control element <NUM> may control power for every smart light (that support a power control function) at location <NUM> and its state may be indicated by state <NUM>. Therefore, with one instance of user input, a user can turn on or off all lights within the dining room, regardless of the manufacturer or entity from which the smart light was obtained. Dimmer control element <NUM> may allow for controlling the dim level of all smart-lights at location <NUM> that support the feature of dimming. Therefore, while power control element <NUM> controls all smart lights within selected group <NUM>, control element <NUM> only controls smart lights that support the feature (which may be all or some of the smart lights within selected group <NUM>). For example, a light controlled by a smart outlet plug, such as control element <NUM>, may not be able to control brightness.

Various methods may be performed using the systems and control interfaces of <FIG>. <FIG> illustrates an embodiment of a method <NUM> for integrating control of multiple cloud-based smart-home devices. Steps of method <NUM> may be performed using smart-home controller device <NUM>, which may be executing smart-home control application <NUM>. Smart-home controller device <NUM> may be functioning as part of system <NUM> and smart-home environment <NUM> of <FIG> and <FIG>, respectively.

At block <NUM>, the smart-home control application <NUM> may receive registration for a first smart-home device by the smart-home control application or the registration information may be received by the cloud-based host server system. This smart-home device may be associated with the manufacture or entity that operates cloud-based host server system <NUM>. Therefore, the first smart-home device may be controlled via direct smart device control API <NUM>. As part of the registration process, the user may provide a user-defined name for the smart-home device. The user may, additionally or alternatively, provide a location that indicates a room or other area within or at a structure where the first smart-home device is located or will be located. In some embodiments, the location is selected from a predefined list of locations available within smart-home control application <NUM>. For example, smart-home control application <NUM> may list the names of rooms that are commonly found within a residential home. In other embodiments, a user may specify a custom name for the location. In still other embodiments, the location at which the smart-home device was installed may be inferred from a name for the smart-home device defined by the user. For example, if the name includes the word "dining" it may be determined that the first smart-home device is installed in a dining room. The registration information may also include an identifier of the smart-home device which can be used to register the smart-home device with the cloud-based host computer system and, if necessary, with the cloud-based server system with which the cloud-based host computer system can communicate. In some embodiments, the cloud-based host computer system may return in indication of the type of smart device being registered and functions that the smart-home device is capable of performing. For the purposes of the remainder of method <NUM>, it is assumed that the first smart-home device was registered with the cloud-based host computer system and the first smart-home device communicates directly with the cloud-based host computer system.

At block <NUM>, registration information for a second smart-home device may be received by the smart-home control application or the registration information may be received by the cloud-based host server system. Registration for the second smart-home device may proceed similarly to block <NUM>. In the illustrated embodiment of method <NUM>, the second smart-home device is controlled via a cloud-based server system distinct from the cloud-based host server system. Therefore, when the second smart-home devices registered with the cloud-based host server system, the cloud-based host server system may provide at least some of the registration information to the cloud-based server system. In response, the cloud-based server system may provide indications of functions that may be performed by the second smart-home device. For the purpose of method <NUM>, the first smart-home device and the second smart-home device are of a same type (e.g., are both types of smart lights) and have at least one function in common, such as both devices can be turned on and off (e.g., a "power function"). However, the first smart-home device in the second smart-home device are provided by different manufacturers or entities and are controlled using different cloud-based systems.

At block <NUM>, a determination may be made by the smart-home control application <NUM> that a common function exists for the first smart-home device and the second smart-home device. In some embodiments, block <NUM> may be performed by the cloud-based host server system. This determination may be made by comparing a list of available functions for the first smart-home device determined during the registration of block <NUM> and the list of available functions for the second smart-home device determined during the registration of block <NUM>. Block <NUM> may only be performed if the first smart-home device and the second smart-home device are determined to be of the same type (e.g., lights, speakers, locks, fans, thermostats, etc.). Block <NUM> may further include determining that the first smart-home device in the second smart-home device are being or have been installed at the same location (e.g., within a same room).

At block <NUM>, the first smart-home device and the second smart-home device may be assigned to a common operating characteristic group by the smart-home control application. In some embodiments, block <NUM> may be performed by the cloud-based host server system. In some embodiments, the first smart-home device in the second smart-home device may be assigned to multiple common operating characteristic groups. For example, a first common operating characteristic group may be created for all smart-home devices of the same type within a structure. For example, such an arrangement may allow a control element such as element <NUM> and element <NUM> to control all smart lights within a structure. Alternatively or additionally, a second common operating characteristic group may be created for all smart-home devices of the same type within a particular location at a structure. For example, such an arrangement may allow for a control element such as control element <NUM> to control all smart lights in the dining room, regardless of the entity that provided the smart light.

At block <NUM>, the smart-home control application may provide a control element that includes a control for allowing a user to control the common function determined at block <NUM>. Therefore, by a user providing a single input to the control, the user can adjust a function or setting of multiple smart-home devices. In the example of method <NUM>, the single input may adjust a function at the first smart-home device in the second smart-home device, which are controlled via different cloud-based systems.

At block <NUM>, user input may be received to the control of the control element that allows a user to control the common function. A single instance of user input may be received at block <NUM>, such as a single touch or a single click. As an example, referring to control element <NUM>, a user may touch the "on" control to turn three smart lights on or the "off' control to turn three smart lights off. In this example, "on" and "off' would be common functions across the multiple smart lights. At block <NUM>, the smart-home control application may cause the smart-home controller device to transmit a message to the cloud-based host system that indicates smart-home device identifiers of the first smart-home device in the second smart-home device (and any other smart-home devices that are of the same type, and, possibly location). The message may also include an indication of the command or function to be performed by each of the smart-home devices. In some embodiments, the user input may be provided to a device other than the device executing the smart-home control application. For instance, the user input may be provided to the cloud-based host server system.

At block <NUM>, in response to the received message, the cloud-based host server system may cause the first smart-home device to perform the commander function. This may be performed by the cloud-based host server system communicating with the first smart-home device via direct smart device control API <NUM>. Additionally, in response the received message, the cloud-based host server system may send an indication of the second smart-home device identifier and the command or function to a cloud-based server system that communicates with the second smart-home device. The cloud-based server system may then instruct the second smart-home device to perform the command or function. Therefore, by user providing a single user input at block <NUM>, smart devices controlled via different cloud-based server systems may each be controlled. In some embodiments, the cloud-based server system may provide an acknowledgment as to whether the second smart-home device performed the command or function to the cloud-based host system. Additionally or alternatively, the cloud-based host server system may provide an acknowledgment to the smart-home control application indicating whether the function or command has been performed by the first smart-home device and/or the second smart-home device. Such an acknowledgment may permit presentation of an interface of the smart-home control application to be updated to reflect the current state of the first and second smart-home devices.

<FIG> illustrates an embodiment of a method <NUM> for determining how to group a smart-home device. Steps of method <NUM> may be performed using smart-home controller device <NUM>, which may be executing smart-home control application <NUM>. Smart-home controller device <NUM> may be functioning as part of system <NUM> and smart-home environment <NUM> of <FIG> and <FIG>, respectively.

At block <NUM>, registration information may be received for a first smart-home device, as in block <NUM> of <FIG>. As part of the registration process, the user may provide a user-defined name for the smart-home device. The user may, additionally or alternatively, provide a location that indicates a room or other area within or at a structure where the first smart-home device is located or will be located. In some embodiments, the location is selected from a predefined list of locations available within smart-home control application <NUM>. For example, smart-home control application <NUM> may list the names of rooms that are commonly found within a residential home. In other embodiments, a user may specify a custom name for the location. The first smart-home device may communicate directly with the cloud-based host server system or through another cloud-based server system if it is a smart-home device manufactured or distributed by a third-party.

At block <NUM>, a determination may be made at the first smart-home devices eligible to perform multiple of functions. Block <NUM> may be performed by the smart-home application or by the cloud-based host server system. Which functions may be performed by the first smart-home device may be based on inquiry being made to the cloud-based host server system or a cloud-based server system which communicates with the cloud-based host server system. In other embodiments, a database may be maintained locally by the smart-home control application that indicates the available functions of various types of smart-home devices. An identifier of the first smart-home device may be used by either the smart-home host server system or the smart-home control application to perform a lookup within the database. As an example, a smart outlet plug may be considered one type of smart-home device that is eligible to perform multiple types of functions. The smart-home outlet plug may be able to turn on and off a device that is plugged into the smart-home all the plug. Therefore, the function of first smart-home device may be considered to be the function of whatever devices plugged into the smart-home outlet plug. Typical devices that may be plugged into the smart-home all the plug may be a light, a fan, or a small appliance (e.g., coffee maker, toaster oven, etc.).

Based on block <NUM> being determined that the first smart-home devices eligible to perform multiple types of functions, a comparison may be made at block <NUM> to compare the user-defined name received at block <NUM> with the database of function specific terms. The database a function specific terms may be similar to those presented in Table <NUM>. The comparison of block <NUM> may be performed locally by the smart-home controller application or may be performed remotely by the cloud-based host server system. Block <NUM> may be performed by the smart-home application or by the cloud-based host server system.

At block <NUM>, based on the comparison of block <NUM>, a determination may be made as far as the intended function of the first smart-home device. Block <NUM> may be performed by the smart-home application or by the cloud-based host server system. Therefore, while the first smart-home device may be of a first type, the way the first smart-home devices being used may be more accurately described based on its intended function. As an example of this consider a smart-home outlet plug that is connected with a light. From a user's point of view, the first smart-home device is causing the light to function as a smart light. Therefore, the smart-home outlet plug may have its intended function be determined as lighting.

At block <NUM>, the first smart-home device may be grouped with a second smart-home device based on the intended function of the first smart-home device matching the function of the second smart-home device by the smart-home application or by the cloud-based host server system. Returning to the previous example, the smart outlet plug may be grouped with a smart light (the second smart-home device) due to the intended function of the first smart-home device matching the function of the smart light. Another example of this can be seen in <FIG>, in which control element <NUM> controls a smart outlet plug as part of a group of lights that includes control element <NUM> and control element <NUM>. The intended function of the smart outlet plug is determined to match a function of the other lamps.

Additionally, grouping may be further based on location within a structure. For example, a smart outlet plug may only be grouped with a second smart-home device that matches the smart outlet plug's intended function if the smart-home outlet plug in the second smart-home device are indicated as being present at a same location. In some embodiments, similar to the user defined name being analyzed for an intended function using a database of function specific terms, the user defined name may be analyzed for an intended location using a database of location names. Therefore, rather than a user selecting a location from a list or otherwise providing a specific location, the user defined name may be used to determine the location.

As detailed in relation to <FIG>, a voice-based assistant engine may be used to control smart-home devices. Such a voice-based assistant engine may function as part of smart-home control application <NUM> or be separately executed by smart-home controller device <NUM>, such as by or part of an operating system of smart-home controller device <NUM>. <FIG> illustrate embodiments of interfaces that may be presented using a smart-home controller device. In the illustrated embodiments, a smartphone <NUM> is used as an example of the smart-home controller device.

<FIG> illustrates an embodiment of an audio command control <NUM> that may be presented when a smart-home controller device is ready to capture an audio sample. Audio command control <NUM> may be presented when a user has selected spoken command control element <NUM>. Alternatively, a user may speak a trigger phrase (e.g., "OK Home Assistant") or provide some other form of input (e.g., squeezing the sides of the smart-home controller device). Once audio command control <NUM> is active, one or more microphones of the smart-home controller device may be being used to capture audio from the environment.

<FIG> illustrates an embodiment of an audio command control <NUM> that may be presented while capturing an audio sample. When a user starts speaking a command, as the audio is received, a voice recognition process may be performed at the cloud-based server system. Text that represents the speech (representative text <NUM>) may be presented via audio command control <NUM>. In other embodiments, the speech is analyzed locally by the voice-based assistant engine rather than being sent to the cloud for analysis. Presentation of the text of the words being recognized from the spoken command allows a user to confirm the spoken command is being interpreted correctly. In the example of <FIG>, a user has spoken "turn off the dining room lights and turn off the living rooms lights. " Therefore, with this single command, the user is trying to collectively control both smart lights in dining room and living room.

<FIG> illustrates an embodiment of an interface <NUM> that includes a custom interface control <NUM> that can control a common function across smart-home devices indicated in the audio sample. Interface <NUM> is presented in response to the command indicated by representative text <NUM> being performed. Custom location group <NUM> indicates the group of locations indicated by the user in the spoken command. Smart device count <NUM> indicates the total number of smart-home devices that were controlled based on the spoken command indicated by representative text <NUM>. Control element <NUM> may allow for control of all smart-home devices indicated by smart device count <NUM> to perform a function that is common to all of the smart-home devices that were controlled based on the spoken command. In this case, control element <NUM> can receive user input to adjust whether the previously-controlled smart-home devices are turned on or off.

In some embodiments, one or more additional control elements may be present. In this embodiment, control element <NUM> is present, which is a dimmer control that allows for some or all of the controlled smart-home devices to have their brightness controlled. By control element <NUM> being present, this is an indication that at least one of the smart-home devices controlled via the spoken command can have its brightness controlled. In some embodiments, control element <NUM> may only be presented and available if this function is available across all smart-home devices controlled by the spoken command indicated by representative text <NUM>.

<FIG> illustrates an embodiment of a custom interface <NUM> allows a user to view video streams indicated in the audio sample. Custom interface <NUM> may presented in response to a user providing an audio command of "show all of my video feeds. " This command may result in each video feed that is received by the smart-home host server system being output for presentation to custom interface <NUM>. Title <NUM> may be representative of the custom group of videos that the user indicated in the voice command. Device count <NUM> indicates the number of video streams linked to the user's account. Each video stream (<NUM>, <NUM>, <NUM>) may be presented for viewing.

<FIG> illustrates an embodiment of a method <NUM> for using captured voice to generate an interactive custom interface controller. Steps of method <NUM> may be performed using smart-home controller device <NUM>, which may be executing smart-home control application <NUM>. Smart-home controller device <NUM> may be functioning as part of system <NUM> and smart-home environment <NUM> of <FIG> and <FIG>, respectively.

At block <NUM>, a local recording may be captured using the smart-home controller device that includes a spoken command intended by the user to be directed to multiple smart-home devices. Alternatively, the recording may be captured using some other device. These multiple smart-home devices may be spread among multiple locations or concentrated at a particular location. These multiple smart-home devices may also represent a subset of smart-home devices located at a particular location. The multiple smart-home devices may be of different types or of the same type. The multiple smart-home devices may include smart-home devices that are directly controlled by the cloud-based host server system and may include smart-home devices that are controlled by the cloud-based host server system via another cloud-based server system. Therefore, the user has considerable flexibility in the smart-home devices that can be controlled using a single spoken command. As previously detailed the smart-home controller device may be ready to receive a spoken command when an interface similar to that of audio command control <NUM> is presented.

At block <NUM>, the vocal recording may be transmitted to the cloud-based host server system to analyze the contents and meaning. In other embodiments, the vocal recording may be analyzed locally. The vocal recorded captured at block <NUM> may be transmitted as the audio is received to the cloud-based host server system to allow for analysis as the voice recording is still being received. At block <NUM>, the vocal recording may be translated from audio into text by the cloud-based host server system. In other embodiments, the vocal recording may be analyzed locally by the smart-home controller device. A semantics engine may analyze the intended meaning of the text including the command to be performed and the smart-home devices at which the command is intended to be executed.

At block <NUM>, the command may be transmitted to the smart-home devices determined at block <NUM>. The command may be transmitted to smart-home devices with which the cloud-based host server system directly communicates and smart-home devices with which the smart-home host server system communicates with via another cloud-based server system. In some embodiments, the smart-home controller device may communicate directly with the cloud-based host server systems associated with various smart-home devices. At block <NUM>, a response may be transmitted to the smart-home controller device at which the vocal recording was initially received. The response may indicate smart-home device identifiers indicative of each smart-home device to which the command was transmitted by the smart-home host server system. Therefore, if the smart-home host server system sent the command to six smart-home devices, six smart-home identifiers would be transmitted to the smart-home controller device. In some embodiments, rather than the smart-home devices being controlled via cloud-based server systems, the smart-home controller device may communicate with and control the smart-home devices directly (e.g., via a direct wireless communication method or via a mesh network).

At block <NUM>, the smart-home device identifiers may be received and then analyzed by the smart-home control application being executed by the smart-home controller device. Each of the smart-home device identifiers may be used to identify the associated smart-home devices and access a smart-home device function database to determine what one or more functions (or intended functions) each smart-home device is capable of. This analysis may include determining if there are one or more functions in common across all of the smart-home devices that were controlled via the spoken command this analysis may also include determining if there one or more functions in common across some of the smart-home devices that were controlled via the spoken command. (In other embodiments, such a function may be present at only one of the smart-home devices that were previously controlled via the voice-based command. ) In some embodiments, rather than the analysis of block <NUM> being performed at the application executed by the smart-home controller device, the analysis may be performed by the cloud-based host server system to determine what functions each device is capable of and determine if one or more functions are in common across the smart-home devices.

If there is at least one function that is in common across all of the smart-home devices that were controlled via the spoken command, a custom interface controller may be generated at block <NUM> that includes one or more controls that allow for user control of the one or more common functions of the smart-home devices that were the subject of the spoken command. This custom interface controller may not have been available to a user via the application prior to block <NUM>. For example, no interface controller may be available that controls lights in two distinct rooms. Therefore, block <NUM> results in the creation of an interface at block <NUM> that otherwise would not exist or be available. The custom interface controller may also include one or more controls that control one or more functions that are in common across some of the smart-home devices that were controlled via the spoken command. Therefore, the presented custom interface controller allows a user to provide additional input to control the smart-home devices that were previously controlled via a voice-based command. In some embodiments, even if there is not one function in common across the smart-home devices indicated by the spoken command, a custom interface controller may be generated that includes a control for a majority of the smart-home devices controlled via the spoken command.

Using the custom interface controller generated at block <NUM> that is being output for presentation, a user may provide user input (e.g., via touch) to further control all or some of the smart-home devices previously controlled via the spoken command. In response to such further input, the smart-home control application may determine one or more commands to be performed by the smart-home devices. The command, along with the smart-home device identifiers indicative of the smart-home devices that are to perform the command may be transmitted to the cloud-based host server system for execution. The cloud-based host server system then may control one or more smart-home devices directly and/or may communicate with one or more other cloud-based server systems to control the corresponding smart-home devices.

Claim 1:
A method (<NUM>) for using captured voice to generate a custom interface controller, the method being carried out by a system and comprising:
capturing (<NUM>), via a mobile device (<NUM>) of the system, a vocal recording from a user, wherein the vocal recording comprises a spoken command directed to a plurality of smart-home devices (<NUM>-<NUM> - <NUM>-<NUM>), for which one or more common functions are determined by the system, and wherein the vocal recording additionally indicates a type of smart-home device (<NUM>-<NUM> - <NUM>-<NUM>);
transmitting (<NUM>), by the mobile device (<NUM>), the vocal recording to a cloud-based server system (<NUM>) of the system;
analyzing (<NUM>), by the cloud-based server system (<NUM>), the received vocal recording to determine the spoken command and the plurality of smart-home devices (<NUM>-<NUM> - <NUM>-<NUM>);
transmitting (<NUM>), by the cloud-based server system (<NUM>), the command to the plurality of smart-home devices (<NUM>-<NUM> - <NUM>-<NUM>) for execution;
transmitting (<NUM>), by the cloud-based server system (<NUM>), a response to the mobile device (<NUM>) that comprises smart-home device identifiers of the plurality of smart-home devices (<NUM>-<NUM>- <NUM>-<NUM>);
receiving (<NUM>), by an application (<NUM>) executed by the mobile device (<NUM>), the response from the cloud-based server system (<NUM>); and
generating (<NUM>), by the application (<NUM>) executed by the mobile device (<NUM>), the custom interface controller that controls, based on a single user input on a touchscreen, the one or more common functions of each smart-home device (<NUM>-<NUM> - <NUM>-<NUM>) of the plurality of smart-home devices (<NUM>-<NUM> - <NUM>-<NUM>).