-
-
Notifications
You must be signed in to change notification settings - Fork 31.8k
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
Did google_tts change once again? No TTS from google_translate for #43801
Comments
Yes, I confirm the same problem with me. It happened at night. I did not make any configuration changes in HA. |
Have problem too. :( |
google_translate documentation |
Just to add onto this, I am getting the same problem whenever I try to use the TTS integration. Clearing my logs, and then trying to send a message to a media player device, I get the following two errors.
|
Same problem |
Same problem. |
|
It might be related/the same issue as here [Error in TTS #123]Hypnos3/node-red-contrib-cast#123 |
This comment has been minimized.
This comment has been minimized.
Just a little information. If you are using Cloud Nabu Casa, you can change the service from tts.google_say to tts.cloud_say and it will work like this. EDIT: That is also not a solution, because all my TTS automations was in the language of Hungarian, now it drops error: "Not supported language hu". Both Service have problems then :( |
@majkers Please don't ping people to pull them into the conversation. That is considered impolite. Thanks 👍 |
@marvin-w did some good work here. Anybody else who'd like to test his fixes? You can do so by using the changed files as
|
Nabu Casa does only support BUT.... there is a change inbound that will allow other languages to, including |
Just as information, the changes will be implemented in 0.118.5? Thank you. |
0.119, scheduled for 13 Dec.
Op wo 2 dec. 2020 22:27 schreef colethegamer123 <notifications@github.com>:
… Just as information, the changes will be implemented in 0.118.5? Thank you.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#43801 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AH7Z5EQAED6RZW4UC2Q6S3DSS2WKJANCNFSM4UIVOFWA>
.
|
Aww that is really too bad, having to wait more than 10 more days without notifications ..... seriously glad this got sorted (thanks!) |
You don't have to wait if you are comfortable enough to install a custom_component: |
Did this and it worked! Will remove once the update is out. Thank you for the quick fix. |
Also working for me. Perfect solution. Thanks for your proactive hard work and also for the installation guide for the new ones. |
thanks, great idea! |
it worked for me too, thanks a lot |
Strange, because those are the exact two languages I tested it with. What is your config? And what version of HA are you running? How do you trigger the TTS? |
duh, thought had re-saved my files from the previous edit to tts.cloud_say back to tts.google_say again. but I hadn't... so sorry for the confusion.
thanks so much |
Will the 0.119 release also fix the same issue in the Node-Red Cast module I mentioned above ? |
@muzzak123 You should ask that with the node-red cast module. This is Home Assistant, not Node-RED. The changes here do not apply, as both are written in completely different programming languages. |
@frenck - I'm sorry I don't understand your comment above ? Aren't you also the sponsor for the Node Red plugin. That was the reason I mentioned it to you. |
That could be true, but it is not linked to this issue as it is a completely other piece of software. Please create an issue at that code base. |
Not working for me. :(
|
@muzzak123 https://github.com/Hypnos3/node-red-contrib-cast (That is not me). |
That use case ( type something in the media player TTS box) was tested too and worked. I just confirmed that it works here, locally, again. There might be something wrong with your setup. Did you download the raw files? How did you configure tts? |
Before it was worked good with this setup: `tts:
|
What does your log say? |
Nothing special: |
I don't see the google translate custom component being loaded. Ensure you placed the files in |
btw, its going to be release version 1.0 ! |
The files are gone...Error 404 |
Yeah, that's because it got merged. I'll update the link - try this one: |
Thanks. It works |
Perfect. That was the problem. Thank You!! |
I know this Google TTS issue has been resolved, but in the spirit of getting off the cloud, had anyone thought about integrating mycroft's 'mimic' TTS utility? https://mycroft-ai.gitbook.io/docs/mycroft-technologies/mimic-overview |
Alright, this is all getting off-topic a bit. The issue has been fixed and merged to dev and currently in the beta as well. Thanks all 👍 |
The problem
As of today, all google_tts notifications stopped working once again, without any change on my side in the config. As far as I can see, no automatic updates have happened in the backend, supervisor is still on 2020.11.0.
Environment
Problem-relevant
configuration.yaml
Traceback/Error logs
Additional information
The text was updated successfully, but these errors were encountered: