Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

tts speak with Google translate seems to run partly in backgrond #37065

Open
paifre opened this issue Jan 23, 2025 · 0 comments
Open

tts speak with Google translate seems to run partly in backgrond #37065

paifre opened this issue Jan 23, 2025 · 0 comments

Comments

@paifre
Copy link

paifre commented Jan 23, 2025

Feedback

New to HA from Jeedom, I'm reimplementing scripts and automations
Fighting to be able to set volume of Google Cast speaker (nest mini) to announce a message (which is very unfortunately not an option), I discovered that if I put the current volume in a variable (media.set_volume), run tts.speak with Google translate then restore the initial volume right after, this is not working.
I have to set a delay after the tts.speak step and before the set_volume to restore the initial value if this step is right after. Else cast is done but with the initial volume which has overwritten the set_volume to higher level for the announce.

Sequence:

  • read initial volume
  • set volume to 1
  • tts.speak with google_translate as entity
  • set volume back to inital volume

So, imho, a mention in the documentation to add a delay (probably in relation with text length) is recommended if using set_volume right after. Else waiting for a trigger on the cast entity from playing to idle

URL

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

Version

2025.1.3

Additional information

No response

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant