[RELEASE] Echo Speaks v3 + Actions

[Sebastien]

Good observation! Looks like the link is bad. I’ll try it with it fixed.

Yup, that was it.

@tonesto7, is that something that can easily be updated?

https://tonesto7.github.io/echo-speaks-docs/updates/server_update/

[Evilborg]

curious if this can be run locally instead on heroku

[cwwilson08]

i believe the answer is yes

[Evilborg]

Any docs on that ?

[cwwilson08]

I'm looking. I know he made it capable but vaguely remember him saying he didn't document well or at all.

[cwwilson08]

[RELEASE] Echo Speaks v3 + Actions

just run git clone https://github.com/tonesto7/echo-speaks-server cd echo-speaks-server npm start You will have to make sure to create a service to make it run on startup. Make sure to select local in the app and it should walk you through setting it up local (It's been a bit since i've tested this process so i'm not 100%)

@Evilborg

[alan564923]

@tonesto7

Not sure if this is related to the other issues, but in order to get 2.5 server, I uninstalled the App and reinstalled. When attempting to get the new app working, i'm getting this message:

So, i checked the Echo Speaks Device code and the Websockect code just imported.

Speaks:

WebSocket:

Note versions 3.6.2 for Speaks and 3.3.0 for Websocket. The log is showing:

after invtesting, it looks like the issue is the mininum version listed in the Echo Speaks SmartApp.

It wants 3.6.3 for the Speaks Device which is less than the released version of 3.6.2

Your assistance is appreciated.
Alan

[cjkeenan]

I too am having this issue, I tried to repair using the Hubitat Package Manager and it did not fix it.

[Evilborg]

Awesome I have it working..

To install it as a service in debian like OS do the following:

1. sudo npm install -g pm2
2. pm2 start index.js (use sudo if not installing under root account)
3. sudo pm2 save

[VilifiedFerret]

@dman2306 did you ever get this running on Pi? With the current issues i'm trying to see if I can port it over and have hit the same wall as you posted

@dman2306

log says

pi@raspberrypi:~/echo-speaks-server $ cat /home/pi/.npm/_logs/2019-12-10T03_05_40_695Z-debug.log
0 info it worked if it ends with ok
1 verbose cli [
1 verbose cli   '/home/pi/.nvm/versions/node/v13.3.0/bin/node',
1 verbose cli   '/home/pi/.nvm/versions/node/v13.3.0/bin/npm',
1 verbose cli   'start'
1 verbose cli ]
2 info using npm@6.13.3
3 info using node@v13.3.0
4 verbose run-script [ 'prestart', 'start', 'poststart' ]
5 info lifecycle echo-speaks-server@2.3.1~prestart: echo-speaks-server@2.3.1
6 info lifecycle echo-speaks-server@2.3.1~start: echo-speaks-server@2.3.1
7 verbose lifecycle echo-speaks-server@2.3.1~start: unsafe-perm in lifecycle true
8 verbose lifecycle echo-speaks-server@2.3.1~start: PATH: /home/pi/.nvm/versions/node/v13.3.0/lib/node_modules/npm/node_modules/npm-lifecycle/node-gyp-bin:/home/pi/echo-speaks-server/node_modules/.bin:/home/pi/.nvm/versions/node/v13.3.0/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/local/games:/usr/games
9 verbose lifecycle echo-speaks-server@2.3.1~start: CWD: /home/pi/echo-speaks-server
10 silly lifecycle echo-speaks-server@2.3.1~start: Args: [ '-c', 'npm index.js' ]
11 silly lifecycle echo-speaks-server@2.3.1~start: Returned: code: 1  signal: null
12 info lifecycle echo-speaks-server@2.3.1~start: Failed to exec start script
13 verbose stack Error: echo-speaks-server@2.3.1 start: `npm index.js`
13 verbose stack Exit status 1
13 verbose stack     at EventEmitter.<anonymous> (/home/pi/.nvm/versions/node/v13.3.0/lib/node_modules/npm/node_modules/npm-lifecycle/index.js:332:16)
13 verbose stack     at EventEmitter.emit (events.js:219:5)
13 verbose stack     at ChildProcess.<anonymous> (/home/pi/.nvm/versions/node/v13.3.0/lib/node_modules/npm/node_modules/npm-lifecycle/lib/spawn.js:55:14)
13 verbose stack     at ChildProcess.emit (events.js:219:5)
13 verbose stack     at maybeClose (internal/child_process.js:1027:16)
13 verbose stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:285:5)
14 verbose pkgid echo-speaks-server@2.3.1
15 verbose cwd /home/pi/echo-speaks-server
16 verbose Linux 4.19.75-v7+
17 verbose argv "/home/pi/.nvm/versions/node/v13.3.0/bin/node" "/home/pi/.nvm/versions/node/v13.3.0/bin/npm" "start"
18 verbose node v13.3.0
19 verbose npm  v6.13.3
20 error code ELIFECYCLE
21 error errno 1
22 error echo-speaks-server@2.3.1 start: `npm index.js`
22 error Exit status 1
23 error Failed at the echo-speaks-server@2.3.1 start script.
23 error This is probably not a problem with npm. There is likely additional logging output above.
24 verbose exit [ 1, true ]

[VilifiedFerret]

OK I used this method and pm2 and got the echo speaks node up and running, however I can't find how to then get web access to it to give it the echo speaks link from the Hubitat install, do I have to enable a web interface within PM2?

[VilifiedFerret]

@Evilborg is your echo speaks instance actually staying online? Mine crashes instantly.

[Evilborg]

Mine is running just great but not using a Pi for it -- the url is your-ip:8091

If its crashing see what /root/.pm2/logs/index-out.log has

[VilifiedFerret]

From the error log

[Evilborg]

Did you run npm install ?

[VilifiedFerret]

I ran this as per tonesto’s instructions:

just run

git clone https://github.com/tonesto7/echo-speaks-server
cd echo-speaks-server
npm start

And then installed and ran pm2 as per yours

[dman2306]

Looks like you figured it out yourself, but no I didn't. I gave up on Echo Speaks. While it's an awesome app that does a lot, it does way more than I need (I just want to use my Echo devices for TTS, I don't need another events engine, for example) and I feel like all this complexity was causing my hub to run slower. I haven't yet switched to anything else but not currently using ES anymore

[tonesto7]

Sorry about the version issues!

I don't get why I have merge issues with the code sometimes. I've corrected the issues and pushed out new versions of all of the code.

[tonesto7]

It can be run locally.

Just clone the GitHub - tonesto7/echo-speaks-server repo and run it like an npm package with npm start

[tonesto7]

It's weird that I can't run this with npm start anymore
If I run it under VSCode debug which uses the same command and works fine.