Skip to content
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 #46

Closed
philpownall opened this issue Sep 19, 2018 · 8 comments · May be fixed by #47
Closed

get key failed from google #46

philpownall opened this issue Sep 19, 2018 · 8 comments · May be fixed by #47

Comments

@philpownall
Copy link

I've been happily using google-home-notifier for quite some time, but have recently started encountering this error:

Error: get key failed from google
at /home/pi/MyHouse/node_modules/google-tts-api/lib/key.js:27:13
at
at process._tickCallback (internal/process/next_tick.js:188:7)

The error message originates in the key.js module as indicated:
try {
eval(html.match(/TKK=eval('(.*)');/g)[0]); // TKK = '405291.1334555331'
if (TKK === null) throw null;
} catch (e) {
throw new Error('get key failed from google');
}

I've tried removing and reinstalling node.js and google-home-notifier, I've tried rebooting the Google Home, and I've tried calling googlehome.device and googlehome.ip to no avail ; does anyone have any idea where I go from here? Is it some sort of authorization error from google?

@tani-github
Copy link

me too.
I've been happily using google-home-notifier for quite some time, but
I also saw the same error today.
Will it be fixed?

-status
rasbery pi -> google-home-notifier -> googlehome
-error
Error: get key failed from google
at /home/pi/dev/google-home-notifier/node_modules/google-tts-api/lib/key.js:27:13
at process._tickCallback (internal/process/next_tick.js:68:7)

I think that
can not acquire TKK by accessing this site(https://translate.google.com/) on rasberry pi.

@horihiro
Copy link

This is a problem which 'google-tts' must be fixed, not this library.
zlargon/google-tts#13

And @ncpierson has already fixed this problem ( great work! ).
zlargon/google-tts#14

So I think it works well by using next version of 'google-tts'.

@horihiro
Copy link

New version of google-tts is released.
You have to update package.json of google-home-notifier and re-install.

Before

  "dependencies": {
      :
    "google-tts-api": "0.0.2",
      :
  }

After

  "dependencies": {
      :
    "google-tts-api": "0.0.3",
      :
  }

@cookemmm
Copy link

do you have the steps that need to be performed to complete the update and reinstall?

@philpownall
Copy link
Author

Updated google-tts-api as indicated and verified that google homre notifier is happily making announcements again.

@sebsebseb1982
Copy link

Hi could you update google-home-notifier with this fix please ?

@specklesmike
Copy link

specklesmike commented Feb 7, 2019

Note: 2019
In ~/.node-red/node_modules/google-home-notify`

edit package.json and change the dependency on 'google-tts-api' from '0.0.2-alpha1' to '0.0.3', so it reads:

"dependencies": {
"bluebird": "3.5.1",
"castv2-client": "^1.2.0",
"google-tts-api": "0.0.4"
}

Update the dependency
npm update

Restart node-red
node-red-stop
node-red-start

cgmckeever added a commit to cgmckeever/google-home-notifier that referenced this issue Apr 27, 2019
@cgmckeever
Copy link

Not sure why this isn;t updated in Master, but I just proposed a quick PR for it. Seems to be the fix, at least for me

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

7 participants