jeremypsl
(Jérémy P.)
October 3, 2024, 7:30pm
1
Hello,
I use Google Cloud for TTS, with tts.google_cloud_say until last update.
Now if i read documentation correctly, i should use tts.speak.
Here is an example of my automation :
action: tts.speak
target:
entity_id: tts.google_cloud
data:
media_player_entity_id: media_player.sonos
cache: false
But it’s not working, no error message but no sound !!!
If i use tts.google_translate, no problem…
action: tts.speak
target:
entity_id: tts.google_translate_fr_fr
data:
media_player_entity_id: media_player.sonos
cache: false
Help !
jeremypsl
(Jérémy P.)
October 4, 2024, 5:51pm
3
Interesting but im not sure.
Gav_in
(Gavin)
October 4, 2024, 7:29pm
4
Seems 2024.10.1 (just released) has some TTS fixes in there… might be worth a look
Several threads about this right now:
Gav_in
(Gavin)
October 4, 2024, 7:40pm
6
They are both after 2024.10.0 release (despite one of the thread titles)…try 2024.10.1 as it reportedly has a fix
jeremypsl
(Jérémy P.)
October 4, 2024, 7:42pm
7
Still not working.
In Assist settings, when i click to try a TTS service, it’s working with Google Translate but not with Google Cloud : “Error playing audio.”
Sure, only to inform to others that there are new threads coming up constantly about the same subject. No need to open new ones.
1 Like
jeremypsl
(Jérémy P.)
October 4, 2024, 8:08pm
9
This is the error i get in log :
Enregistreur: homeassistant.components.tts
Source: components/tts/__init__.py:1080
intégration: Text-to-speech (TTS) (documentation, problèmes)
S'est produit pour la première fois: 21:50:45 (17 occurrences)
Dernier enregistrement: 22:07:01
Error on load tts: af71d61b60fb474925712400ea7f2283aa70d387_fr-fr_5903e9c71d_tts.google_cloud not in cache!
Error on load tts: af71d61b60fb474925712400ea7f2283aa70d387_fr-fr_b1aae47e40_tts.google_cloud not in cache!
Error on load tts: af71d61b60fb474925712400ea7f2283aa70d387_fr-fr_221a26d1c1_tts.google_cloud not in cache!
Error on load tts: 372ea08cab33e71c02c651dbc83a474d32c676ea_fr-fr_b1aae47e40_tts.google_cloud not in cache!
vaemarr
(Vaemarr)
October 10, 2024, 1:09am
10
Im having issues myself since this update.
Failed to perform the action tts.google_cloud. InvalidDataError: Unable to retrieve info for http://172.18.0.71:8123/api/tts_proxy/a94a8fe5ccb19ba61c4c0873d391e987982fbbd3_en-au_408e309469_google_cloud.mp3: Server returned 404 Not Found
and
Error on load tts: 4e9b2aecd98522e7b4ed893adb659db90fec93f1_en-au_408e309469_google_cloud not in cache!
This is generated when testing from the developer section and testing the service directly outside of automations.
If I stream media to the speaker from Music Assistant, it works fine. Its only this Google Cloud integration failing.
1 Like
milesroper
(Milesroper)
October 10, 2024, 10:47am
11
Just wanted to mention im on 10.1 and are still getting the above error.
henrikbla
(Henrik Blåfield)
October 10, 2024, 10:57am
12
Fix should be coming in 2024.10.2.
home-assistant:dev
← cdce8p:revert-enum
opened 09:36PM - 05 Oct 24 UTC
## Proposed change
This reverts commit 1bc63a61be8057850f68e0ff4e0c94563d5a41c9… .
Fixes #127518
I opened #125220 originally as the mypy error stated that `AudiEncoding` doesn't support `__getitem__` lookups. Seems that is a false-positive. Mypy doesn't recognize the enum metaclass of `proto.Enum`.
## Type of change
<!--
What type of change does your PR introduce to Home Assistant?
NOTE: Please, check only 1! box!
If your PR requires multiple boxes to be checked, you'll most likely need to
split it into multiple PRs. This makes things easier and faster to code review.
-->
- [ ] Dependency upgrade
- [x] 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
<!--
Details are important, and help maintainers processing your PR.
Please be sure to fill out additional details, if applicable.
-->
- This PR fixes or closes issue: fixes #
- This PR is related to issue:
- Link to documentation pull request:
## Checklist
<!--
Put an `x` in the boxes that apply. You can also fill these out after
creating the PR. If you're unsure about any of them, don't hesitate to ask.
We're here to help! This is simply a reminder of what we are going to look
for before merging your code.
-->
- [ ] 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][dev-checklist]
- [ ] I have followed the [perfect PR recommendations][perfect-pr]
- [ ] The code has been formatted using Ruff (`ruff format 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][docs-repository]
If the code communicates with devices, web services, or third-party tools:
- [ ] The [manifest file][manifest-docs] 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.
<!--
This project is very active and we have a high turnover of pull requests.
Unfortunately, the number of incoming pull requests is higher than what our
reviewers can review and merge so there is a long backlog of pull requests
waiting for review. You can help here!
By reviewing another pull request, you will help raise the code quality of
that pull request and the final review will be faster. This way the general
pace of pull request reviews will go up and your wait time will go down.
When picking a pull request to review, try to choose one that hasn't yet
been reviewed.
Thanks for helping out!
-->
To help with the load of incoming pull requests:
- [ ] I have reviewed two other [open pull requests][prs] in this repository.
[prs]: https://github.com/home-assistant/core/pulls?q=is%3Aopen+is%3Apr+-author%3A%40me+-draft%3Atrue+-label%3Awaiting-for-upstream+sort%3Acreated-desc+review%3Anone+-status%3Afailure
<!--
Thank you for contributing <3
Below, some useful links you could explore:
-->
[dev-checklist]: https://developers.home-assistant.io/docs/development_checklist/
[manifest-docs]: https://developers.home-assistant.io/docs/creating_integration_manifest/
[quality-scale]: https://developers.home-assistant.io/docs/integration_quality_scale_index/
[docs-repository]: https://github.com/home-assistant/home-assistant.io
[perfect-pr]: https://developers.home-assistant.io/docs/review-process/#creating-the-perfect-pr
1 Like
I’m on 2024.10.2 And the error resolved for a few runs, and is now back in effect and blocking all functionality. Every time gives the same error:
Error on load tts: ed906bed9527bd402587788415f7d44b4b83934d_en-us_bd8615e924_tts.google_cloud not in cache!
The actual filename changes, but it’s always that error.
ctml
October 23, 2024, 1:02am
15
Same issue and I am on 2024.10.3. Have you found any workarounds?
G2740
(Dave)
October 25, 2024, 1:24pm
16
I use the the Nabu Casa cloud and it quit working. 2024.10.3. Was working. Kind of just waiting…
alias: Aqara Back Door Has Opened
description: “”
triggers:
entity_id:
binary_sensor.aqara_back_door_opening
from: “off”
to: “on”
trigger: state
conditions:
actions:
metadata: {}
data:
message: Back Door Has Opened
data:
ttl: 0
priority: high
action: notify.mobile_app_sm_sxxx
delay:
hours: 0
minutes: 0
seconds: 2
milliseconds: 0
action: notify.mobile_app_sm_sxxx
metadata: {}
data:
message: TTS
data:
ttl: 0
priority: high
tts_text: Back Door Has Opened
mode: single
TTS has been unavailable from version 2024.10 to the latest 2024.10.4, and it was working normally before 2024.10 . Do you have any suggestions for the following error? Thank you.
G2740
(Dave)
October 27, 2024, 4:13pm
18
Mine started working again all by itself.
No new updates.
Did go thru my phone settings, but don’t think I changed anything that would have had any impact.
Odd.
torano
October 28, 2024, 11:46am
19
It now works for me with Core 2024.10.4.
G2740
(Dave)
October 28, 2024, 1:57pm
20
Yep, 2024.10.4 must have fixed mine too.
G2740
(Dave)
October 28, 2024, 2:49pm
21
I take that back. What I just found is if my notifications phone setting volume slider is at zero in settings, HA TTS works.
If I slide the volume up to 50 percent so I can hear other notifications sounds, than HA doesn’t announce TTS, but does make the sound I assigned for that notification. Weird.
My automation sends a notification and waits 2 seconds then is supposed to speak to me about whats open.
Some setting or something or HA cloud, companion app setting, Samsung? Haven’t figured that out yet if it is that. Or me.