[RELEASE] Echo Speaks V4

[wiegout]

Actually no, I followed the instructions at

Echo Speaks Local Cookie Authorization Server - ScottiByte's Discussion Forum
ALTERNATE INSTALLATION OF ECHO SPEAKS AUTHORIZATION SERVER WITHOUT DOCKER

On your target server, install the dependencies:

sudo apt install nodejs
sudo apt install npm

Now get and install the Echo Speaks Server application.

npm i https://github.com/tonesto7/echo-speaks-server
sudo npm install -g pm2
cd node_modules/echo-speaks-server
sudo pm2 start index.js
sudo pm2 list
sudo pm2 save
sudo pm2 startup
sudo pm2 save

I just reinstalled it and it still has the 10.x address. Ugh...

[wiegout]

very interesting. If I do an "ifconfig -a" on my RPi eth0 is 192.168.4.129. BUT wg0 is 10.110.227.1. I need to get the Echo Speaks server to return the IP of eth0 not wg0. I am also running a WireGuard server on this pi. Anyone know how to get it to use the first IP (eth0) not some other random one?

[jtp10181]

@wiegout I cover this way up above as well, here you go.

@jtp10181

EDIT4: Sorry I finally found the way to just launch pm2 and set the variable. PM2 - Environment Variables | Best Practices | PM2 Documentation

So looks like if you already have pm2 setup you could restart it like this to set the variable.
Replace 'app' with the name of the app when you run pm2 list

ipAddress=192.168.4.3 pm2 restart app --update-env

May need to run a pm2 save again after this as well, not sure but it wont hurt anything.

EDIT: Added link to my GUIDE to the about fixing the IP on pm2 for future reference.

[wiegout]

This worked!
$ cd node_modules/echo-speaks-server/
sudo ipAddress=192.168.4.129 pm2 restart index.js --update-env
sudo pm2 save

Thank you so much!

[jtp10181]

In case its not obvious, make sure you have a DHCP reservation set for that device so the IP does not change, or it will break it and you have to figure it out all over again.

[nh.schottfam]

please share the changes, or post a pull request so we can get this into the code

[wiegout]

Yep. IPs of all my servers and anything smart home related are reserved. I appreciate you mentioning this though. Thanks again for helping an old retired IT guy here. Too much Pickleball and not enough Linux. Cheers!

[jkudave]

@nh.schottfam

please share the changes, or post a pull request so we can get this into the code

"A11QM4H9HGV71H" : [ c: [ "a", "t" ], i: "echo_show_5", n: "Echo Show 5 (Gen3)" ],

I already posted a pull request.

[Bruce123]

I recently moved from C-5 to C-8 hub and I've just noticed that my Echo Speaks is not working anymore and checking the log, I see this error.

Also, when I checked the cookie refresh, the last time it did it was 232 days ago.

What's strange is that I can play my music fine on Sharptools hence it took me this long to notice this.

Can someone help me diagnose this? TIA.

[terminal3]

If you changed hubs you needed to redeploy the server. Did you do that?

[user5948]

New to the Hubitat world; finally ditching SmartThings. I followed the steps on the documentation on installing and setting up the app. All good until I try to use the Amazon login page. When I click that step, I just get a new window with a Heroku error saying there's nothing there. Same issue on PC and iOS. Any suggestions?

[jtp10181]

Did you deply the Heroku server?

Server Configuration - Echo Speaks Documentation

[user5948]

Yup, dutifully followed all the steps through 6, then got stuck when the login page wouldn't open.

[jtp10181]

Use the reset option and try again maybe? I have never used Heroku, always used a local server.

[user5948]

I did try resetting it and installing a new instance through Heroku, same result. I'd love to not have to pay for Heroku, so if you have advice on how to set it up on a local server, I'd be happy to try that!

[jtp10181]

Check This, second post has non-docker instruction links as well.

[GUIDE] Echo Speaks Server on Docker (or without)

A compilation of instructions and tips to get Echo Speaks running locally through docker Other Guides and Links are in the next post, including how to install without Docker! Installing echo-speaks-server on Docker This assumes you already have docker / docker-compose / portainer installed and operational on your chosen platform. Portainer / Docker-Compose If you already have Portainer installed this is the easiest way to install and manage the container. You can create the container manual…

[jsarcone]

I'm sorry for bringing this up. I know it's been brought up many times before. However, from a traditional deployment of the cookie server that's definitely changed. In addition, I have wiped out my Raspberry Pi server and dedicated it to this deployment and it's been months and I still cannot get the locally installed server to work.

Let's start with the native server on Heroku. After attempting to try to get the locally installed cookie server to work I attempted to fall back to Heroku. I did a redeploy on that platform like I've done many times before and it would not find the URL and give you the following view.

When I reviewed the app settings the URL is not presented the same way as it used to be. If you're already deployed this is not an issue only for new deployments.

If I follow that link the server does appear.

So, I don't see a way around this problem.

And now for the locally installed server, I've tried with docker without docker and either I'm in a login loop where it doesn't take the cookie, or it does and then reverts back to being unconfigured or back to Heroku.

I rebuilt my Raspberry Pi to follow the following setup for Portainer / Docker-Compose.
And I cannot get the Hubitat application to recognize the login. According to the log files with the container I do get a cookie, but the Hubitat application does not see it.

The page does display with the container popup.

Login

Back to

I have tried everything, and I cannot seem to find where the problem is.
Now, I cannot move forward or backward. I’m now just stuck.

[jtp10181]

@jsarcone

And I cannot get the Hubitat application to recognize the login.

Did you follow my tips at the bottom of the guide?

• If you get red error text that you still need to login:
  • Restart the docker container
  • Click the Amazon Login Page button
  • Log in again (do not click Save at bottom)
  • Close the server login tab, and the main app should refresh

[jsarcone]

Drove me crazy but it seems like that's working. Thank you very much.
I hope I don't have the secondary issue where it loses its mind and it won't refresh the cookie or thinks it's back to heruko.

Thanks!

[gmAU]

Firstly thanks for so quickly adding the new echo pop device after I submitted the details!

I have an issue with using the “search Sirius XM” function on a WHA speaker group. Does anyone have any suggestions? It won’t play, if I select speakers individually it will. I was thinking of using an Alexa routine and calling that.. any other ideas?

Thanks