Google Assistant SDK conversation agent

[tronikos]

Proposed change

Implement Google Assistant SDK conversation agent.

Users need to add in the configuration.yaml:

conversation:

and then they can click on the microphone in the up right corner to start a conversation with Google Assistant either by typing or talking to the microphone. Example:

Type of change

• Dependency upgrade
• Bugfix (non-breaking change which fixes an issue)
• New integration (thank you!)
• New feature (which adds functionality to an existing integration)
• Deprecation (breaking change to happen in the future)
• Breaking change (fix/feature causing existing functionality to break)
• Code quality improvements to existing code or addition of tests

Additional information

• This PR fixes or closes issue: fixes #
• This PR is related to issue:
• Link to documentation pull request: Google Assistant SDK: Document conversation agent home-assistant.io#25657

Checklist

• The code change is tested and works locally.
• Local tests pass. Your PR cannot be merged unless tests pass
• There is no commented out code in this PR.
• I have followed the development checklist
• The code has been formatted using Black (black --fast homeassistant tests)
• Tests have been added to verify that the new code works.

If user exposed functionality or configuration variables are added/changed:

• Documentation added/updated for www.home-assistant.io

If the code communicates with devices, web services, or third-party tools:

• The manifest file has all fields filled out correctly.
  Updated and included derived files by running: python3 -m script.hassfest.
• New or updated dependencies have been added to requirements_all.txt.
  Updated by running python3 -m script.gen_requirements_all.
• For the updated dependencies - a link to the changelog, or at minimum a diff between library versions is added to the PR description.
• Untested files have been added to .coveragerc.

To help with the load of incoming pull requests:

• I have reviewed two other open pull requests in this repository.

[balloob]

The way conversation_id is used that when a conversation is initiated, it is set to None.

Then in your response you return a conversation ID such that follow-up responses work.

Now in this case it doesn't seem like you're passing conversation_id so you should set conversation_id=None here, as it's not used.

Suggested change

	response=intent_response, conversation_id=conversation_id
	response=intent_response, conversation_id=None

Now in your screenshot I did notice that it's allowing follow-up commands, so I am not sure how that works then 🤷

[tronikos]

Both DefaultAgent and AlmondAgent (the only other two agents) do exactly the same thing. conversation_id starts with None and is never modified.

Anyway for Google Assistant we cannot really have many concurrent conversations, see https://github.com/tronikos/gassist_text/blob/main/src/google/assistant/embedded/v1alpha2/embedded_assistant.proto#L314-L318

[balloob]

Yeah neither can do conversations.