[Deprecated] Amazon Alexa Text to Speech (TTS) v0.6.2 - Direct Integration (USA, Canada, UK, Italy, Australia, & Brazil)

Sadly not. Some sort of server is still required. In ST they are using a third party cloud server.

In the end cookie stuff will likely be all that remains of the original app code for me.

1 Like

I am going to try to get this set up, but all of my RPi's are running NodeJS v8 since that version works the best with google-assistant-relay. Not sure why I am clinging to assistant-relay, now that Hubitat supports native Chromecast integration. Nostalgia? :thinking:

@gabriele Thank you again for your contributions and the pull requests to the GitHub Repository for both the Alexa TTS Manager App and its ReadMe. I really appreciate the collaboration! I have updated the first post, with information regarding AlexaCookie.


UPDATE: I was able to get AlexaCookieNodeJs running without any obvious issues on a Raspberry Pi running NodeJS v8. My cookie was expired already, so this was a good test. It is working beautifully! :+1:

2 Likes

I've also got AlexaCookieNodeJs running with Node JS v8 on my Synology NAS. Great work guys!

1 Like

@ogiewon I have to admit that your app runs flawlessly compared to Echo Speaks which I have had nothing but problems with especially after code updates.

So I am sticking with your app.

1 Like

I'm not able to install pm2

Not sure why either.

nodejs --version

v8.11.1

(node:25129) [DEP0022] DeprecationWarning: os.tmpDir() is deprecated. Use os.tmpdir() instead.
npm ERR! Error: Method Not Allowed
npm ERR!     at errorResponse (/usr/share/npm/lib/cache/add-named.js:260:10)
npm ERR!     at /usr/share/npm/lib/cache/add-named.js:203:12
npm ERR!     at saved (/usr/share/npm/node_modules/npm-registry-client/lib/get.js:167:7)
npm ERR!     at FSReqWrap.oncomplete (fs.js:135:15)
npm ERR! If you need help, you may report this *entire* log,
npm ERR! including the npm and node versions, at:
npm ERR!     <http://github.com/npm/npm/issues>

npm ERR! System Linux 4.14.79-v7+
npm ERR! command "/usr/bin/node" "/usr/bin/npm" "install" "-g" "pm2"
npm ERR! cwd /root/alexa-speaks/hubitat-master/AlexaCookieNodeJs/AlexaCookieNodeJs
npm ERR! node -v v8.11.1
npm ERR! npm -v 1.4.21
npm ERR! code E405
npm ERR! 
npm ERR! Additional logging details can be found in:
npm ERR!     /root/alexa-speaks/hubitat-master/AlexaCookieNodeJs/AlexaCookieNodeJs/npm-debug.log
npm ERR! not ok code 0

From the log file

980 error Error: Method Not Allowed
980 error     at errorResponse (/usr/share/npm/lib/cache/add-named.js:260:10)
980 error     at /usr/share/npm/lib/cache/add-named.js:203:12
980 error     at saved (/usr/share/npm/node_modules/npm-registry-client/lib/get.js:167:7)
980 error     at FSReqWrap.oncomplete (fs.js:135:15)
981 error If you need help, you may report this *entire* log,
981 error including the npm and node versions, at:
981 error     <http://github.com/npm/npm/issues>
982 error System Linux 4.14.79-v7+
983 error command "/usr/bin/node" "/usr/bin/npm" "install" "-g" "pm2"
984 error cwd /root/alexa-speaks/hubitat-master/AlexaCookieNodeJs/AlexaCookieNodeJs
985 error node -v v8.11.1
986 error npm -v 1.4.21
987 error code E405
988 verbose exit [ 1, true ]

Try using sudo in front.

I was already root

It's nice to see you talk shit here as well...

Hatfield? McCoy?

4 Likes

How is my experience with your app "talking shit" ? I think you want everyone to just drool and gush over it.

Dan's app works. I don't need the other bells and whistles that your app has. All I want is my echos to speak and that's it.

Sorry you if you can't take a honest post.

Did you do anything specific to get this running on Synology? I keep getting a cannot find module error when I try to run "node AlexaCookie.js"

I feel i am missing something here. I get everything working on another box on my network. I get the refresh url and refresh options. the login cookie i post into the cookie but (unedited version) and it doesn't work. If i edit it then it will work. Anyone got any ideas why the AlexaCookieNode.js Refresh options string i get doesn't seem to work

If you just copy the refresh option, it should automatically extract login cookie.

Yesterday mine was unable to refresh cookie (last week was fine), I'm still trying to figure out the reason.

II had a message that the refresh fail. I opened the app and clicked the 'Force refresh now'. Log is below:

[app:2872](http://192.168.0.30/logs#app2872)2019-01-19 10:33:26.386 am [error](http://192.168.0.30/installedapp/configure/2872)'getCookie()': Error making Call (getMessage): Internal Server Error

[app:2872](http://192.168.0.30/logs#app2872)2019-01-19 10:33:26.384 am [error](http://192.168.0.30/installedapp/configure/2872)'getCookie()': Error making Call (Status): 500

[app:2872](http://192.168.0.30/logs#app2872)2019-01-19 10:33:26.376 am [error](http://192.168.0.30/installedapp/configure/2872)'getCookie()': Error making Call (Data): Error refreshing cookie =&gt; ERROR: Unexpected end of JSON input

[app:2872](http://192.168.0.30/logs#app2872)2019-01-19 10:33:26.300 am [info](http://192.168.0.30/installedapp/configure/2872)Alexa TTS: starting cookie download procedure

[app:2872](http://192.168.0.30/logs#app2872)2019-01-19 10:28:34.230 am [debug](http://192.168.0.30/installedapp/configure/2872)'updated()' called

[app:2872](http://192.168.0.30/logs#app2872)2019-01-19 10:28:26.254 am [info](http://192.168.0.30/installedapp/configure/2872)Alexa TTS: Request for new cookie sent succesfully, guid: 41363fa9-5e17-4765-bba7-54ab3a4d2f91

[app:2872](http://192.168.0.30/logs#app2872)2019-01-19 10:28:26.016 am [info](http://192.168.0.30/installedapp/configure/2872)Alexa TTS: starting cookie refresh procedure

I rebooted the raspberry pi where the NodeJS app is installed. No change. Any clues on what I need to do?

I had mine setup to refresh every day at 2am. Mainly was doing that to test for the next few weeks to see if it runs into any problems.

About 3 days ago it started failing to refresh. Not sure why as I have had the time to really dig in. The first night my server was off so I thought it was just that.

Original NodeJS library has been updated (probably Amazon has changed something on their side), I'll update proxy as soon as possible.

1 Like

I have had no experience with NodeJS prior to this. Do I need to update something on my RPi? If so, command line details on how to do that would be greatly appreciated.

Thanks!

:point_up: this would be very helpful @gabriele.

Thanks!

This update involves just Alexa-Cookie original library, so it's sufficient to replace your AlexaCookie/alexa-cookie/alexa-cookie.js file with this one:

Then if you have pm2 installed, restart application with command pm2 restart AlexaCookie

Here now it's refreshing properly.

1 Like

Thank @gabriele! I have updated my alexa-cookie.js file and have restarted AlexaCookie.

Note to other users - be sure to update the AlexaCookie/alexa-cookie/alexa-cookie.js file, not the AlexaCookie/AlexaCookie.js file!

2 Likes