Abstract: Implementations relate to role change requests that can be delayed and/or implemented according to circumstances associated with an interaction between a user and an automated assistant. A role change request can cause a designation of auxiliary devices (e.g., earbuds and/or any other peripheral devices) to be changed, and at least cause a different auxiliary device to be tasked with directly communicating with a principal device (e.g., a cellular phone). For instance, when an auxiliary device is requesting a role change request during an assistant interaction, an operating system of the principal device can identify factors that form the basis for determining whether to immediately implement the role change request or, instead, to delay or refuse implementation of the role change request. When the factors indicate that the role change request is not particularly urgent, the operating system can cause the role change request to be delayed until the assistant interaction is complete.

Abstract: Implementations relate to role change requests that can be delayed and/or implemented according to circumstances associated with an interaction between a user and an automated assistant. A role change request can cause a designation of auxiliary devices (e.g., earbuds and/or any other peripheral devices) to be changed, and at least cause a different auxiliary device to be tasked with directly communicating with a principal device (e.g., a cellular phone). For instance, when an auxiliary device is requesting a role change request during an assistant interaction, an operating system of the principal device can identify factors that form the basis for determining whether to immediately implement the role change request or, instead, to delay or refuse implementation of the role change request. When the factors indicate that the role change request is not particularly urgent, the operating system can cause the role change request to be delayed until the assistant interaction is complete.

Abstract: Implementations relate to proactively aggregating client device data to append to client assistant data that is communicated to a server device in response to a user request to a client automated assistant. When a user request that is associated with, for example, a peripheral client device, is received at a client device, the client device can communicate, to a server device, data that embodies the user request (e.g., audio data and/or local speech recognition data), along with peripheral device data that was received before the client device received the user request. In this way, the client automated assistant can bypass expressly soliciting peripheral device data each time a user request is received at another client device. Instead, a peripheral device can proactively communicate device data to a client device so that the device data can be appended to request data communicated to the server device from a particular client device.

Abstract: Implementations relate to proactively aggregating client device data to append to client assistant data that is communicated to a server device in response to a user request to a client automated assistant. When a user request that is associated with, for example, a peripheral client device, is received at a client device, the client device can communicate, to a server device, data that embodies the user request (e.g., audio data and/or local speech recognition data), along with peripheral device data that was received before the client device received the user request. In this way, the client automated assistant can bypass expressly soliciting peripheral device data each time a user request is received at another client device. Instead, a peripheral device can proactively communicate device data to a client device so that the device data can be appended to request data communicated to the server device from a particular client device.

Abstract: Implementations relate to role change requests that can be delayed and/or implemented according to circumstances associated with an interaction between a user and an automated assistant. A role change request can cause a designation of auxiliary devices (e.g., earbuds and/or any other peripheral devices) to be changed, and at least cause a different auxiliary device to be tasked with directly communicating with a principal device (e.g., a cellular phone). For instance, when an auxiliary device is requesting a role change request during an assistant interaction, an operating system of the principal device can identify factors that form the basis for determining whether to immediately implement the role change request or, instead, to delay or refuse implementation of the role change request. When the factors indicate that the role change request is not particularly urgent, the operating system can cause the role change request to be delayed until the assistant interaction is complete.

Abstract: Implementations relate to proactively aggregating client device data to append to client assistant data that is communicated to a server device in response to a user request to a client automated assistant. When a user request that is associated with, for example, a peripheral client device, is received at a client device, the client device can communicate, to a server device, data that embodies the user request (e.g., audio data and/or local speech recognition data), along with peripheral device data that was received before the client device received the user request. In this way, the client automated assistant can bypass expressly soliciting peripheral device data each time a user request is received at another client device. Instead, a peripheral device can proactively communicate device data to a client device so that the device data can be appended to request data communicated to the server device from a particular client device.