Comments (19)
Just started happening to me tonight after months of working just fine.
from node-red-contrib-cast.
Same here. The error message switches from "Not able to get media file via google-tts:get key failed from google" when trying to execute it multiple times to sometimes to: "Client error reported:connect EHOSTUNREACH 192.168.174.108:8009"
from node-red-contrib-cast.
Yes, this is a issue because google has chaged something.
zlargon/google-tts#22
I already had try to fix this several days ago. Can you please test with the latest version 0.2.1?
from node-red-contrib-cast.
Version 0.2.1 fixed this issue
from node-red-contrib-cast.
hello, i have the same problem. i use version 0.2.4. it says: Not able to get media file via google-tts:get key failed from google
from node-red-contrib-cast.
Are you sure, that you have installed version 0.2.4?
I have tested it and have no problems.
from node-red-contrib-cast.
Can you please check that you have installed google-tts-api version 0.0.4?
from node-red-contrib-cast.
I had also a cast client errot. It turned out that the ip adress has changed during DSL router reconfiguration.
Here is my debug log:
24.1.2019, 09:38:11node: Google Home mini
msg : string[62]
"Client error reported:connect EHOSTUNREACH 192.168.101.28:8009"
from node-red-contrib-cast.
Can you please check that you have installed google-tts-api version 0.0.4?
yes, i checked. i have cast 0.2.4 and google-tts-api 0.0.4. By the way: i checked to send a audio-file - that works.
from node-red-contrib-cast.
@kiai72: The node just simply do to convert the textz message by using google-tts-api to a audio file which is send to the cast device. So thee error "Not able to get media file via google-tts:get key failed from google" comes from google-tts-api. This error should be fixed in google-tts-api with version 0.0.4.
Sorry I can not help here.
from node-red-contrib-cast.
@drose28357: The Error "Client error reported:connect EHOSTUNREACH 192.168.101.28:8009" states, that the google home mini is not accessible at IP "192.168.101.28" from the Node-Red instance.
- Is this the right IP Address of your Google Home Mini?
- Has the new DSL Router any firewall settings that the Device running NodeRed can not access the Google Home mini with this IP?
from node-red-contrib-cast.
@kiai72: The node just simply do to convert the textz message by using google-tts-api to a audio file which is send to the cast device. So thee error "Not able to get media file via google-tts:get key failed from google" comes from google-tts-api. This error should be fixed in google-tts-api with version 0.0.4.
Sorry I can not help here.
sure! i just wonder, why it works for you. is there any setup for google-tts-api/key that i have to do ?
Bye the way: i know your tool "just sends a audio file" at the moment. Can we enhance it to send a broadcast message instead ? After a broadcast message - the previous stream continues! that would be helpful for my case.
from node-red-contrib-cast.
Yes. Can you give me more information how to "send a broadcast message"?
I was not able to find an example.
from node-red-contrib-cast.
Yes. Can you give me more information how to "send a broadcast message"?
I was not able to find an example.
as far as i know broadcast is only possible between "assistant devices" (2 home, a google assist on android and a home, ...).
there a project that does this: https://github.com/greghesp/assistant-relay
it's standalone, not node-red. but maybe it's interessting for you?
from node-red-contrib-cast.
Yes this is interesting.
But I think that is a completely different approach. Here you have to get a google API key. That would be something for a new node and nothing for this.
Since I currently lack the time and I'm running too many projects at the same time, I can not say yet if and when I can take a closer look.
from node-red-contrib-cast.
I collecting that into this issue:
#35
from node-red-contrib-cast.
Same for me, it's been ok for a few months until the TTS errors start happening a couple of weeks ago. Casting audio files stored in Google drive is working though.
from node-red-contrib-cast.
Seeing the same issue with error "Not able to get media file via google-tts:get token key failed from google"
from node-red-contrib-cast.
I updated the cast plugin in NodeRed and it seems to work again
from node-red-contrib-cast.
Related Issues (20)
- Error in TTS HOT 41
- loosing connection HOT 7
- google-tts:get token key failed from google HOT 1
- Cast content of imageUrl when casting a simple text message. HOT 2
- can't set image url HOT 2
- Files are playing simultaneously when using msg.urlList HOT 2
- playback status HOT 4
- Can't Stream Audio or TTS - Not able to launch DefaultMediaReceiver HOT 5
- No longer playing text file, fails with Not Able to Load Media HOT 12
- Error in TTS
- NodeRed exits with msg.payload not equal to timestamp HOT 2
- Cast dashboard (URL) HOT 2
- tts HOT 2
- "cast" node crashing Node Red HOT 2
- node.error causing Nodered to crash HOT 3
- Open URL does not work HOT 4
- Loosing connection
- message is stucked sometimes and queued
- unable to connect
- TypeError: node.error is not a function
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from node-red-contrib-cast.