Echo speaks install error

[dropshadow]

i have been using echo speaks / paid heroku for a long time without issue. recently i had to change my amazon password, and i guess at some point that broke the integration between hubitat and heroku. i did not get the proper 2fa method, heroku sent me a code to my phone number, but then the page error out:

finally, i just decided to restart and rebuild a new app. now i am stuck. i am trying to deploy a new server but i get this message in heroku:

any advice? can you still setup echo speaks + heroku from scratch?

or does anyone know how to deploy a new echo speaks app within heroku from scratch without going thru the hubitat interface/integration, and then connecting it back to hubitat?

[jtp10181]

Echo Speaks - Heroku new deployment workarounds

NOTE: Heroku no longer has a free option, so you may need to give a credit card and pay monthly to setup a new deployment. If you have any sort of always-on computer at home you can use a local server for free: [GUIDE] Echo Speaks Server on Docker (or without) Heroku new deployment workarounds for Echo Speaks If you are trying to deploy a new Heroku server for Echo Speaks... You may be getting this right after you deploy: [image] And/Or this when trying to log into Amazon: [image] Heroku …

[dropshadow]

i am a paid heroku user. the error states "cloud.hubitat.com" it not a valid git repository - valid github could not be found. this is not a free/paid issue. i am not interested in running docker, but thanks.

[jtp10181]

Did you read that entire post?

[dropshadow]

i did. changing the URL is not available until after server deployment has started - i can't even get the server deployment started yet, so i cannot edit anything.

i am on step 2 of this " Now tap on the Deploy to Heroku button."

Server Configuration - Echo Speaks Documentation

the page that comes up is above error page stating invalid git repository.

[chrisbvt]

@dropshadow

i am not interested in running docker, but thanks.

I used the nodejs and npm method on an old PI 3 to setup the cookie server. It was pretty painless to set it up just copy-pasting in the commands given in the tutorial.

[jtp10181]

Last time I tested it, worked fine. I would have to try it again on my dev hub.

[dropshadow]

@chrisbvt

I used the nodejs and npm method on an old PI 3 to setup the cookie server. It was pretty painless to set it up just copy-pasting in the commands given in the tutorial.

ok. i will keep that in mind as a last resort. the last time i had to fiddle with this was in 2022. i haven't touched it in years and echo speaks worked great, no fail in almost 3 years. i dont mind the $5 a month especially for something that is turn key, but i will keep docker in mind if the app cannot be made to work. thanks.

[aaiyar]

@dropshadow

will keep docker in mind

FWIW, I don’t know how at @chrisbvt is doing it, but it is possible to run the Echo Speaks server on bare metal Linux. For those who prefer that ….. or who dislike Docker.

[chrisbvt]

@aaiyar

I don’t know how at @chrisbvt is doing it

From the Guide for setting it up

@jtp10181

Linux: Installing echo-speaks-server without Docker

You need Node.js and npm installed first (this may vary depending on your OS):

sudo apt install nodejs
sudo apt install npm

Install and Run the Server:

Log in with the user who will run the server (does not need to be root).
Change to directory you wish to run the server from (can be home folder, subfolders will be created).

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

Complete the setup through the Echo Speaks app on Hubitat!

[jtp10181]

I think I figured this out. When you get the purple "Deploy to Heroku" button right click on it and copy the link. Paste that into a text editor (notepad or whatever). In front of heroku.com add www. so it is https://www.heroku.com/<leave everything else alone>

Then copy and paste that link into a new browser window to deploy.
Then follow my guide to edit the vars and get it working.

If this works I can edit the code on my fork to fix the deploy url.

[dropshadow]

thanks guys, but i drank the microsoft kool-aid a long time ago, lmao. i run win server 2019 at home 24/7, so i might look at the win option later.

[dropshadow]

@jtp10181

Then follow my guide to edit the vars and get it working.

If this works I can edit the code on my fork to fix the deploy url.

making progress! adding www did make the deploy button work. however...

i was able to deploy the app and get to the amazon login. i was running into the 2fa problem, so i enabled authenticator, and amazon accepted my 2fa response. i get to the interstitial page which says:

Amazon Alexa Cookie Retrieved Successfully

You will be redirected back to the config page in 5 seconds.

but when i am redirected back to the login page, it just says login like before. it does not say "authentication good!" like step 8 of the setup documentation. i checked my echo speaks app, and it says at the top:

"Login Issue:
You are no longer logged in to Amazon. Please complete the Authentication Process on the Server Login Page!"

i tried several times to go thru the login process, i tried using incognito mode, but i could not get to "authentication good!"

[jtp10181]

Did you edit the hostUrl on the Heroku server?

In Heroku try clicking More .. Restart Dyno
I know restarting the server usually fixes that login issue, maybe it will work on Heroku also.

[dropshadow]

@jtp10181

Did you edit the hostUrl on the Heroku server?

In Heroku try clicking More .. Restart Dyno
I know restarting the server usually fixes that login issue, maybe it will work on Heroku also.

yes, i did edit the hostURL:

and then i More > Restart all dynos

[jtp10181]

I would restart it again. It happens with the stand alone server too where it gets stuck like that and wont log in. Then if you restart the server it works fine the next try.

[dropshadow]

@jtp10181

I would restart it again. It happens with the stand alone server too where it gets stuck like that and wont log in. Then if you restart the server it works fine the next try.

restarted several times. app seems to not be able to login:

2025-01-20T00:11:04.836938+00:00 heroku[web.1]: Restarting
2025-01-20T00:11:04.839656+00:00 heroku[web.1]: State changed from up to starting
2025-01-20T00:11:05.314013+00:00 heroku[web.1]: Stopping all processes with SIGTERM
2025-01-20T00:11:05.329184+00:00 app[web.1]: removing path
2025-01-20T00:11:05.329494+00:00 app[web.1]: SIGTERM
2025-01-20T00:11:05.329525+00:00 app[web.1]: clean
2025-01-20T00:11:05.329545+00:00 app[web.1]: 0
2025-01-20T00:11:05.329558+00:00 app[web.1]: graceful setting timeout for PID: 2
2025-01-20T00:11:05.382281+00:00 heroku[web.1]: Process exited with status 0
2025-01-20T00:11:08.701092+00:00 heroku[web.1]: Starting process with command `node index.js`
2025-01-20T00:11:09.436731+00:00 app[web.1]: (node:2) [DEP0040] DeprecationWarning: The `punycode` module is deprecated. Please use a userland alternative instead.
2025-01-20T00:11:09.436769+00:00 app[web.1]: (Use `node --trace-deprecation ...` to show where the warning was created)
2025-01-20T00:11:09.442023+00:00 app[web.1]: 1-20-2025 - 12:11:09am info: 	-- Echo Speaks Web Service Starting Up! Takes about 10 seconds before it's available... --
2025-01-20T00:11:09.443072+00:00 app[web.1]: getRemoteCookie...
2025-01-20T00:11:09.446200+00:00 app[web.1]: 1-20-2025 - 12:11:09am info: 	** Echo Speaks Config Service (v2.8.0) is Running at (IP: 0.0.0.0 | Port: 25363) | ProcessId: 2 **
2025-01-20T00:11:09.446511+00:00 app[web.1]: 1-20-2025 - 12:11:09am info: 	** On Heroku: (true) **
2025-01-20T00:11:09.446758+00:00 app[web.1]: 1-20-2025 - 12:11:09am info: 	Checking for Server Version Updates...
2025-01-20T00:11:09.651223+00:00 app[web.1]: Alexa-Cookie: Use as Login-Amazon-URL: amazon.com
2025-01-20T00:11:09.651306+00:00 app[web.1]: Alexa-Cookie: Use as Base-Amazon-URL: amazon.com
2025-01-20T00:11:09.651362+00:00 app[web.1]: Alexa-Cookie: Use as User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/51.0.2704.103 Safari/537.36
2025-01-20T00:11:09.651380+00:00 app[web.1]: Alexa-Cookie: Use as Accept-Language: en-US
2025-01-20T00:11:09.651419+00:00 app[web.1]: Alexa-Cookie: Proxy-Mode enabled if needed: echo-speaks-XXXXXXXXX-YYYYYYYYYYYY.herokuapp.com to listen on 0.0.0.0
2025-01-20T00:11:09.653423+00:00 app[web.1]: 1-20-2025 - 12:11:09am error: 	generateAlexaCookie: You can try to get the cookie manually by opening https://echo-speaks-XXXXXXXXX-YYYYYYYYYYYY.herokuapp.com/ with your browser.
2025-01-20T00:11:09.653933+00:00 app[web.1]: 1-20-2025 - 12:11:09am debug: 	Alexa Login Status: There was an error
2025-01-20T00:11:09.789146+00:00 heroku[web.1]: State changed from starting to up
2025-01-20T00:11:09.779590+00:00 app[web.1]: 1-20-2025 - 12:11:09am info: 	** ServerVersion Sent to Hubitat Endpoint Successfully! **
2025-01-20T00:11:09.828785+00:00 app[web.1]: 1-20-2025 - 12:11:09am info: 	Server Version is Up-to-Date.

[jtp10181]

Did you use my forked code and set the host url manually in the app on HE also?

This is my test setup I ran earlier today, so I know it can work

[dropshadow]

@jtp10181

Did you use my forked code and set the host url manually in the app on HE also?

when i was working thru the other thread, i thought i saw something that said your forked code was incorporated into v 4.2.4.0. did i read that wrong? i did a clean install and everything is 4.2.4.0 in my HE. if i need to apply your code changes, i can do that, but i will have to get back to this later in the evening. wife is screaming that we are supposed to go out to dinner, sigh.

[jtp10181]

That note is saying I updated my fork to incorporate the 4.2.40 updates from upstream. You have to use that forked code so you can manually set the server URL on the HE side.