Evidently it affects a subset of those installing the ES server under Docker.
1 Like
Yep, that was the ticket! Had not until now understood that this env var was required for Docker installs using the pre-fabbed Container image, but evidently so.
Happily, adding it brought the ES app up to speed on where the server lives:
From
To
Thanks for steering me straight! Will leave these posts here for others similarly afflicted.
1 Like
Got this working in Docker Desktop on Windows. In case anyone wants to run this with an old-fashioned Docker run command...
docker run -d --name echo-speaks -e LOG_LEVEL=debug -e TZ=America/New_York -e ipAddress=192.168.50.15 -p 8091:8091 --restart always tonesto7/echo-speaks-server:latest
Change IP and TZ as needed. You can also leave the debug and TZ environment variables out if you'd like. Navigate to IP:port and follow setup then return to Echo Speaks app in Hubitat for callback URL. Works perfectly for me.
I can't get past the Amazon Authorization after it send the # code to verify the amazon login. The page keeps refreshing and if I do happen to get it in in time I get a page error Cannot POST /ap/cvf/approval/verifyOtp
Tried different browsers and the same thing.
Anyone know how I can get past this issue?
some people reported, that they have to try several times.
I have, can't get the Amazon OTP to get authorized.
I use OTP via an authenticator app and had no issues on my end. I know not helpful, but it does work. Not sure what the issue might be.
graceful setting timeout for PID: 1
3-12-2023 - 1:30:55pm info: -- Echo Speaks Web Service Starting Up! Takes about 10 seconds before it's available... --
getRemoteCookie...
3-12-2023 - 1:30:55pm info: ** Echo Speaks Config Service (v2.8.0) is Running at (IP: 192.168.0.95 | Port: 8091) | ProcessId: 1 **
3-12-2023 - 1:30:55pm info: ** On Heroku: (false) **
3-12-2023 - 1:30:55pm info: Checking for Server Version Updates...
Alexa-Cookie: Use as Login-Amazon-URL: amazon.com
Alexa-Cookie: Use as Base-Amazon-URL: amazon.com
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
Alexa-Cookie: Use as Accept-Language: en-US
Alexa-Cookie: Proxy-Mode enabled if needed: 192.168.0.95:8091 to listen on 0.0.0.0
Proxy Init: loaded temp data store â– â– â– fallback former data
Proxy Init: reuse frc from former data
Proxy Init: reuse map-md from former data
Proxy Init: reuse deviceId from former data
3-12-2023 - 1:30:55pm error: generateAlexaCookie: You can try to get the cookie manually by opening http://192.168.0.95:8091/ with your browser.
3-12-2023 - 1:30:55pm debug: Alexa Login Status: There was an error
3-12-2023 - 1:30:56pm info: Server Version is Up-to-Date.
Thanks for the OTP authenticator app suggestion, that worked.
1 Like
My synology will show this message:
Docker container tonesto7-echo-speaks-server1 stopped unexpectedly
It looks to be happening regularly every five days. Is this expected and normal? What exactly is happening?
There is some sort of bug that causes it to exit right after the cookie refresh in some cases. If you set the restart policy to always restart it will just fire back up again and is not a concern.
Can't seem to get this working with docker container on my Synology box. Was working fine on Heroku before. Any suggestions?
I got it working... was reading through the other thread and saw people recommend restarting the Docker container... after I did that, I was able to get the Amazon login to stick.
1 Like
buried in this thread is a 'dont use the beta' comment that went undisputed.
recently while working on improving my cookie monitor tile - I found that comment. Following a later blurb - use HPM to unmatch, then rematch to the NONE beta improved me a lot and gave me this as well: (note the app and driver version update). That in conjunction with the ES Tile is no providing me excellent monitoring and function.
I got everything but the Amazon authentication to work. When I click the Goto Login Page, I get this.
[Alexa Logo]
404
Sorry, we couldn't find that page.
Now I have gotten as far as logging in to the Amazon page
Amazon Alexa Cookie Retrieved Successfully
You will be redirected back to the config page in 5 seconds.
then 5s later it is back at the Blue button (goto login page).
After logging in and it redirects you back DO NOT press the save button, that seems like it clears the login for me.
Thanks. I tried that too. The button never changes to orange for me.
Is anyone else getting a 502 error when connection to the web ui.
Echo speaks is working and I have tried this on several browsers.
