Error occurred during Google Cloud TTS call: 400 Request contains an invalid argument.

[wifiuk]

The problem

I'm trying to get Google Cloud TTS working, I have the integration setup in the .yaml file but when I ask it to speak I get the below in the logs:

Error occurred during Google Cloud TTS call: 400 Request contains an invalid argument.

What version of Home Assistant Core has the issue?

Home Assistant 2022.7.3

What was the last working version of Home Assistant Core?

No response

What type of installation are you running?

Home Assistant OS

Integration causing the issue

Google Cloud TTS

Link to integration documentation on our website

https://www.home-assistant.io/integrations/google_cloud/

Diagnostics information

`Error occurred during Google Cloud TTS call: 400 Request contains an invalid argument. Traceback (most recent call last): File "/usr/local/lib/python3.10/site-packages/google/api_core/grpc_helpers.py", line 50, in error_remapped_callable return callable_(*args, **kwargs) File "/usr/local/lib/python3.10/site-packages/grpc/_channel.py", line 946, in call return _end_unary_response_blocking(state, call, False, None) File "/usr/local/lib/python3.10/site-packages/grpc/_channel.py", line 849, in _end_unary_response_blocking raise _InactiveRpcError(state) grpc._channel._InactiveRpcError: <_InactiveRpcError of RPC that terminated with: status = StatusCode.INVALID_ARGUMENT details = "Request contains an invalid argument." debug_error_string = "{"created":"@xxxxxxxxxxxxxxxxxxxx","description":"Error received from peer ipv4:x.x.x.x:443","file":"src/core/lib/surface/call.cc","file_line":952,"grpc_message":"Request contains an invalid argument.","grpc_status":3}"

The above exception was the direct cause of the following exception:

Traceback (most recent call last): File "/usr/src/homeassistant/homeassistant/components/google_cloud/tts.py", line 286, in async_get_tts_audio response = await self.hass.async_add_executor_job( File "/usr/local/lib/python3.10/concurrent/futures/thread.py", line 58, in run result = self.fn(*self.args, **self.kwargs) File "/usr/local/lib/python3.10/site-packages/google/cloud/texttospeech_v1/services/text_to_speech/client.py", line 633, in synthesize_speech response = rpc( File "/usr/local/lib/python3.10/site-packages/google/api_core/gapic_v1/method.py", line 154, in call return wrapped_func(*args, **kwargs) File "/usr/local/lib/python3.10/site-packages/google/api_core/grpc_helpers.py", line 52, in error_remapped_callable raise exceptions.from_grpc_error(exc) from exc google.api_core.exceptions.InvalidArgument: 400 Request contains an invalid argument.`

Example YAML snippet

# Text to speech
tts:
  - platform: google_cloud
    key_file: googlecloud.json
    language: en-GB
    gender: female
    voice: en-GB-Neural2-A
    encoding: mp3
    speed: 1
    pitch: 0
    gain: 1.5
    text_type: ssml

Anything in the logs that might be useful for us?

No response

Additional information

No response

[probot-home-assistant[bot]]

google_cloud documentation google_cloud source _{^{(message by IssueLinks)}}

[probot-home-assistant[bot]]

Hey there @lufton, mind taking a look at this issue as it has been labeled with an integration (google_cloud) you are listed as a code owner for? Thanks! _{^{(message by CodeOwnersMention)}}

[wifiuk]

Any thoughts on this?

[wifiuk]

is @lufton even looking at these? seems many are closing due to inactivity...

[lufton]

is @lufton even looking at these? seems many are closing due to inactivity...

Sorry, guys, I'm not maintaining this component right now. I'm from Ukraine and left all of my possession behind on Feb 24, including PC and Smart Home stuff ) So I have other more vital questions.

[wifiuk]

Totally understandable, can it be assigned to someone else?

[wifiuk]

can it be assigned to someone else?

[github-actions[bot]]

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.