-
Notifications
You must be signed in to change notification settings - Fork 0
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
"Get key failed from google" error #7
Comments
No updates on this??? |
This is very likely related to similar issues over at Home Assistant (home-assistant/core#42911, home-assistant/core#43801), gTTS (pndurette/gTTS#232) and thus gTTS token. As well as in the Node world of things like google-tts (zlargon/google-tts#33, zlargon/google-tts#35, zlargon/google-tts#36), where google-translate-tts is now a working implementation. I hope any fixers can be helped by my analysis of these changes. |
@Boudewijn26 would google-translate-tts work with nodered? Or another alternative that works with nodered? |
I can try to repackage google-translate-tts for nodered, but I've never done that before. If anyone else wants to make that contribution, it would be very welcome :) |
@JuniorGamingTime I really can't say. It already appears @ncpierson knows far better than I. My Google TTS adventures have been mostly limited to Python. I do hope someone with the relevant experience will also be able to chime in. |
Just added |
Omg thanks so much, ill get on it in a few minutes here. |
So far it seems to work well. How could I change the languages? Just i changing the "en-US" to a supported Google tts language? |
Only thing is that if i change the of the node in the settings, the node name stays as "text-to-speech" other languages seems to be working well too |
Yeah, the node properties has a "voice code" field which you can change. The supported codes are not really documented, but the list in this file should all be supported. Google also has a list but I don't think all the codes are supported. Google frequently adds support for more languages, though: https://cloud.google.com/speech-to-text/docs/languages |
Whoops, I never tested changing the node name, I just assumed it would work. I'll fix that. |
@JuniorGamingTime hi Thanks |
Yeah I always look for updates daily, soo I instantly updated it. No issues and it's been working great |
Just like the title says, I've been using this node for over a year with no issues. But now I keep getting this error. Any fix for this?
The text was updated successfully, but these errors were encountered: