You have to use the port
1 Like
I'm an idiot. Y'all are too kind dealing with my fumbling around. This absolutely worked and many many thanks!
See message below RE: me being an idiot. Thank you so much for your help!
1 Like
Hi there
Just a quick question, I am sure this has been covered but I cant find the details.
I ported the Echo Speaks Service to a local pi and all working good.
But how is the best way to update the service please?
This is the current status...
I appreciate your guidance in advance
BTW Happy Christmas to all forum contributors and members
Anyone give some advice on a docker deployment on Portainer on a Asustor NAS.
I keep getting an error of
"2023-12-12T13:30:19.607212528Z exec /usr/local/bin/docker-entrypoint.sh: exec format error"
Greatly depends on how you have it installed. Docker or not?
Found this on the googler
exec format erroris an error you get when you try to run a binary for architecture X on a machine with architecture Y, and the machine is not set up to translate CPU instructions from X to Y.
Try following this from the guide:
1 Like
I finally got around to setting up echo speaks. I have the echo speaks server running on an always on Windows 10 box with NodeJS and NSSM and everything seems to be working fine; the HE echo speaks app shows that the login status is good, I see all of my echo dots, and “Speech Test” and “Announcement Test” work as expected. The only oddity is that I’m seeing the following errors in the log consistently every 6-7 minutes:
Anyone have any idea what might be wrong?
Looks towards the bottom of the main Echo Speaks thread, there is a code edit to make it stop. Amazon changed something and broke whatever that feature is (seems to not be important).
2 Likes
Yup, that did it--thanks!
Thanks for the incredible directions! There so clear and helpful !!!!
I tried the local url and went back and forth and confirmed it does not work, where as the cloud version does.. ( i restarted container each time) do i have it wrong. I clipped the end of both : )
Second question ... if this is on a laptop that is not online all the time....will that be problematic?
Thx
Tim
local url is wrong
shoud be http://192.168.1.118/apps/api/862/receiveData?access_token=xxxxx
assuming that is the ip of your hubitat
1 Like
Bingo that worked!
So the other question...what if on my nephews laptop that is not always on... if he cookies status good, when does echo speak refresh cookies....ie,. when not "good" or proactively while still "good".
Sorry one more q...with the callback having the option of cloud version...is there any chance that I could run a docker container in MN for a cookie server for my nephew in FL ?
Thanks again for all the help.
Tim
A lot of people have gone months with a broken server before they even notice, so I think it will be OK. As long as it is able to refresh it every once and while. He could also force a refresh every couple of weeks while the laptop is running.
The only problem might be that I think the "local" server does not support using an URL as the way for the ES app to contact it, so if your server IP changes then the app wont be able to find it. Might be able to get around it using my patch for Heroku so you can put in a custom URL, but may need to do a fake Heroku deployment and then change the URL to point to a DDNS for your remote server.
So I've had so much trouble with the pi, that I decided to setup port forwarding and want to setup another container with an echo server for my nephew in FL.
I did the following
docker run -e ipAddress=192.168.1.118 -p 8092:8092 --name echo-speaks-server-jeremy --restart=unless-stopped -d tonesto7/echo-speaks-server
when I look at the container ...it says its using port 8091 ...how do I get it to use port 8092
also is the name important ? i.e. is it ok to call it echo-speaks-server-jeremy ?
Thx
Tim
Yes the name can be anything.
The port you have specified is the port forwarding from outside the container to inside it. You also need to tell the server to listed on that port.
Add -e PORT=8092
docker run -e ipAddress=192.168.1.118 -e PORT=8092 -p 8092:8092 --name echo-speaks-server-jeremy --restart=unless-stopped -d tonesto7/echo-speaks-server
To do this you will need to remove the container you created first, so it can be created again with the proper command.
1 Like
thanks again for the help...so i using remote admin (soooo handy), I signed into his hub in FL and installed echo speak and then when I try and configure it, I get the message with the call back info that I need to put on the cookie server... but there is no other options for configuring...I don't see any where I can update the link so that his hub will access my cookie server over the internet ...I need to change it to match the ddns address of the cookie server. What am I missing... thx again !!!!
You could try my patched code here: Echo Speaks - Heroku new deployment workarounds
I do not remember if my patch will show up and work for a local server, or only when you do Heroku. That's why I said you might need to set it up as a Heroku setup but then just point it to your server instead.
1 Like
I imported your code and tried selecting Heroku but never got a chance to pick a serverHostOverride... I'm looking through the code but admittedly not good at it... is there a way for the serverHostOverride to be a box like
FYI to access the server remotely its something like
