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:
And/Or this when trying to log into Amazon:
Heroku is now adding another string to the url, and the "hostUrl" variable is not (cannot be) set to contain the full url upon deployment.
Example hostUrl set when deployed: echo-speaks-XXXXXXXXX.herokuapp.com
Fixed hostUrl: echo-speaks-XXXXXXXXX-YYYYYYYYYY.herokuapp.com
Hey there, got everything to work and they're all showing on my hubitat now. But only problem I'm having is thag they're showing all offline, except one of my devices (firetv) that's the only showing online and wondering if they all should be showing online?
Do you have the devices showing as offline on a segregated VLAN or behind some sort of firewall or DNS blocking system (like pi-hole)? I suspect they might be having issues checking in to one of the amazon services so the system thinks they are offline.
BTW the offline problem really has nothing to with Echo Speaks, the app is only reporting to you the info it gets from Amazon. So Amazon thinks they are offline.
With the cookie refresh not working, it may stop working at any time. Supposedly it is only supposed to work for a few weeks but a lot of people have reported it still works 200+ days later.
Sorry for the stupidity but don't really know what u mean by that. Very new to all this and doing as a hobby but all my devices at home are online and working normally. Except for two of them that I don't really use but all the other ones shows offline and are not working and tested all of them. Here some pictures to maybe help
When you say at the beginning of the lines that we implemented the server again, what do you mean, that everything is deleted and we reinstall it from scratch?
Its no a problem with Echo Speaks that I know of, it just gets the status info from the Amazon/Alexa server. So the app is being told the devices are offline by Amazon.
You might have better luck over on the actual Echo Speaks post or making a new post, maybe someone else has had this issue and will know how to fix it.
Fair warning, Heroku does not have a free option anymore so you may have to give them a credit card. You can do a local server free if you have an always on machine at home.
To re-deploy the Heroku server you would want to log into your Heroku dashboard, delete any existing sever instances. Then in the ES app on Hubitat reset the cookie server info Under Alexa Login Services > Manage Cookie Login Service > Reset Options > Reset Service Data. Turn that on then press done and close the app. Go back in and you can then re-deploy the server.
I am paying 5 euros for the Heroku service, which I don't understand because the cookies are not updated, I just realized now. So would I have to delete everything and implement it again?
Thank you so much for your help and not sure if I should have said but I'm in the UK and the reason it wasn't working was I was putting amazon.co.uk but changed to amazon.com and now all of them are online and working. Thanks you so much for your help
I have been having the damnest time getting the login to work and would appreciate any trouble-shooting help anyone could provide.
I am able to go through and edit the hostURL as outlined, save that, and restart. I then Open App and go through the Amazon login. It accepts my password, captcha, and Authenticator code but then spits back the following error...
The logs confirm it's using the hostURL, but the status seems to show a 404...
I assume I must be missing a step somewhere, but I've tried this several times over the past week, re-reading the instructions each time, and I keep getting the same result. Any suggestions or guidance would be appreciated.
I think the library being used is outdated and only supports certain 2FA methods. I am using an authenticator app to get the 6 digit code for my account and that works. There was one other user who posted and was having issues, finally figured out that switching the 2FA method fixed it.
