Progress!
I had to generate a public SSH key and link it to my Github account.
Moving forward
remote: Enumerating objects: 1615, done.
remote: Counting objects: 100% (468/468), done.
remote: Compressing objects: 100% (49/49), done.
remote: Total 1615 (delta 427), reused 419 (delta 419), pack-reused 1147
Receiving objects: 100% (1615/1615), 764.00 KiB | 4.47 MiB/s, done.
Resolving deltas: 100% (1081/1081), done.
I believe they are a brand of trousers
Ok, I have gotten my local Echo Speaks server working. In my case, I created it inside of a LXD container. You can use a Pi or a VM also. I tried the Docker container solution and it worked fine, but was more complicated than needed.
In my case, I used a LXD container that was Ubuntu 22.04.
So, on my LXD container, I simply installed the app with these steps.
sudo apt install nodejs
sudo apt install npm
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
You will want to set a static address on the instance where the Echo-Speaks server is running.
Next you will want to go to your Echo-Speaks app page on the Hubitat skill and choose the reset options loggle.
When you go back into the app, turn off the toggle to deploy to Heroku and you will get this screen.
Next, click on the "Deploy Server"
You will get a popup screen with a callback URL.
Copy the entire section in gray and then visit your Echo Speaks URL on the local server you built which will have your address with port 8091. In my case http://172.16.3.3:8091.
Paste the callback URL into the last field labelled callback URL and then click save settings.
You can exit this screen.
When you exit the screen with the gray block for the call back URL that you copied, the app should change to a screen like this.
When you click the amazon login page option, you will get a screen like this:
Click the go to login page option.
Once you type in your credentials, your screen should look like this.
At this point, you can exit that login screen and your Echo-Speaks app page on your echo speaks skill should refresh and look like this:
This means that Echo Speaks is working and using your local network (non-Heroku Cloud) for its login/cookie server.
VERY IMPORTANT: So, mine failed to tell me that I had logged in when I exited the login screen saying I was logged in. If this happens to you, simply reboot your LXD instance, your VM instance or your Pi and try the login again. That's what ultimately fixed it for me.
Hope this helps!
Went through this process and am stuck at
sudo pm2 startup
I get an error message “Init system not found”. Anyone knows what this means? TIA!
Ralph, normally the pm2 startup error would only happen if you are trying to run node.js under windows which is not supported.
@vmsman - great write up, I was able to follow it and get the server running on my Linux box. I didn't use LXD container (not familiar with containers), but was able to install the nodejs, npm and started the index.js.
Everything went pretty smoothly until I got stuck on the Amazon login (as you indicated), I ended up just stopping then restarting the index.js and then re-tried the Amazon login... and it worked.
sudo pm2 stop index.js
sudo pm2 start index.js
I mainly use Echo Speaks for controlling devices that only integrate with Alexa and not Hubitat. I use the "Voice CMD As Text" option and create routines in HE to control these Alexa only devices... and have become dependent on it.
Anyway... So happy to have my own local server and be free from Heroku, thanks again!
Thank you for the detailed instructions!
Are you saying that I can run this on my Pi in Pi OS without a container - like Docker in my case? That would simplify things for me.
I was not thinking about a static IP but that makes sense. I'm guessing a static local IP address for the Pi on my network, like 192.168.1.11, is not what we are talking about.
I am on Google Fiber. I know that there are various ways to set up a (free) static IP using outside services. If anyone knows a link to a good static IP service and a recipe I would certainly appreciate the information.
I may have asked this before. Is there a way to setup Alexa speaks on a windows 10 computer? I have one on 24/7.
If there is please include directions.
Thanks in advance.
Setup a VM that runs Linux. And install it there.
I have no idea how to accomplish this.
No, a LAN IP address for your RPi that doesn’t change. Don’t worry about your public/WAN IP address.
“Static IP” can be a confusing term, in that “static” means unchanging. But your router is probably using DHCP to assign IP addresses on your LAN. So what you want is a DHCP reservation, which is done in your router’s settings page.
The RPi continues to use DHCP, but it’s IP address won’t change because you told the router to always give it the same one.
“Static IP” in networking terminology means something different. So ignore that for now.
If you’re using a Pro (not home) version of Windows it’s easy with built-in (but optional to enable) features like Windows Subsystem for Linux and Hyper-V.
If you’re using a home version of windows, it’s not that hard but you may need to install an app like VMWare to create the VM.
Yes, my instructions assume that you will not be using Docker. The downside of using the Pi in this way might be that it would be perhaps a little harder to use the Pi for other applications at the same time. All that Docker does is to provide application virtualization through isolation in a container.
Scott, interesting use case. I use several Webcore pistons in my environment to facilitate calls to Echo Speaks for several informational and reactional speech responses. For me, I make Alexa simply a peripheral to HE. That means that I have the Hubitat skill enabled on Alexa, but I try not to specifically pair devices with Alexa. Part of that is that I want local control for all of my devices. Some time stop by my YouTube channel https://youtube.com/@scottibyte.
Yup that’s what UniFi calls DHCP reservation 
.
OK, any suggestions on a lightweight version of Linux? I haven't done this before, will probably have to spend some time on Youtube to figure this out.
I don't get why everyone is in such a panic.
This is from the app creator:
"I swear you guys are very impatient!
Just relax and use the current server... we have almost 3 months!
I will have the new version ready before then"
Looked at that and my brain just disintegrated. Unfortunately I'm a noob otherwise I'd lend a hand. I'm not sure if there's any special requirements to move from a regular Docker image to a Docker image within Container Station.
Not so much related to Heroku (I got that localized to a RPi recently, but I also with the change warnings realized I was running an older version of Echo Speaks. I started updating from couple of year old version to 4.x on apps; and as I got to the drivers, I noticed the WebSocket code is not published. My app works with a bunch of errors after I clicked on actions feature and got an error that won't clear either with restarts of app or HE. But I use Sharptools for front end, so I can play media and still control. I do notice also that he album art no longer shows and grouped speakers are in and out (it plays on one for one song and then all of them for another). Just curious with all the transitions I missed up until Heroku announcement, whether there is a gap in my upgrades or bug fixes. Since I have app error when I open, I cannot show the versions summary table, but it seems to be:
apps: ES app., actions, and zones- 4.2.0.7
drivers: ws- 4.1.9.2 (July 2021); device and device zone- 4.2.0.7
Download the Hubitat app
