No longer playing text file, fails with Not Able to Load Media
Diez66 opened this issue · 12 comments
Not sure what information I can send you, so please ask, but over the last couple of days I have had 2 of my three google home minis failing to play text to speech, up until then, perfect.
I made resets, I factory reset the two non playing devices, now all 3!! do not play texts, even the "was OK" device.
The node reports, ("Not able to load media:Load failed Not able to load the media.") in the debug. All hear is the Chime.
This is the same with both my flow and your example flow.
I can send an mp3 file , using your example, and this is OK most of the time but about 20% of the time, this also says; "unable to load media"
Node red V1.2.3, on Raspberry pi3 standalone and V1.3.3 on an instance on a Raspberry pi4 in a Docker container.
node-red-contrib-cast V0.2.17
Yes Google is once again subtly reminding us we aren't supposed to use this endpoint the way we are...
You might temporarily get back to working by factory resetting the unit to clear the session that has triggered the CAPTCHA on the endpoint that is blocking you, but it will just come back eventually. It's time to start looking at alternatives. While my node (node-red-contrib-castv2) works a little different, the solves I've begun collecting here should be applicable to the node-red-contrib-cast node as well in general, you'll just need to adjust the MEDIA cast to conform to this node's format.
I am unsure if the "new" base64 encoded based endpoint Google started using in Nov 2020 suffers from the same rate limiting CAPTCHA, but its not a drop in replacement. That WIKI page has a flow that will help you expose your own wrapping endpoint that will allow using that though instead of the old translate.google.com endpoint. I'd love to get some more testers around that to see if it does because its more palatable than asking people to setup a whole Google Cloud account and attach a credit card to use the full Google TTS API...
I also started a list of other providers on that page that people have had luck using as a drop in replacement (though different voice engines, etc. so it won't sound like a Google Home anymore). For a lot of people, those are gonna be easier to setup.
Cheers.
Well, that's a pain and, Thanks for getting back.
I have now seen other discussions, you are in, where there is more info which sums to about the same.
I have looked at the Google stuff and I see things like, 60 minutes a month (15sec in lumps) and 4 million characters and if exceeded , cerching!
So Thanks, I will keep reading and maybe set up the required account, love cloud providers give and TAKE. I guess that is the always the way or the world. I also hate to give out "open ended" credit details.
I found some other node red "Play" nodes, they also suffer from, I guess, the same problem(ish)
I may try and find a Home Assistant route but that will take some time as I don't know what I am doing so need to find out first. (Will it even work, let you know)
Auch bei mir tritt das Problem seit ein paar Tagen auf und ließ sich auch nicht durch zurücksetzen des Google Home Mini lösen.
Yes, it stopped working - the problem is the same as 6 months ago. Plays a beep to start playback, but no message. :((((
Hardware: Mini, Nest..
SO, looks like a long term problem at least via this way.
Home assistant seems to have similar issues with it's ways being "dissuaded" by the great provider!
I have looked to biting the bullet and getting an account but getting a bit lost in the try to sign up?.
If I do get an account do you have a node that should play ball?
I will also try other, suggested, routes as I do like what the TTS ability gives me at home.
Anyway, thanks for what you have produced here, I could have not got this far without these nodes.
Some problem over here, , even the wife is asking me why there is isnt a message anymore when the washing machine is ready ;-)
also here same problem with nest
The tts is now working again. But with a creepy voice.
I had same trouble for some days. But become normal without action today.
The voice of GH has changed.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
This issue has been automatically closed because it has not had recent activity. Thank you for your contributions.