[GUIDE] Echo Speaks Server on Docker (or without)

[jkudave]

@Marx

Is there a way to check?

I haven't used Portainer in a while, but as I recall, you should see your environment variables in the container.

To that note, there are only 2 other environment variables other than Port that are set. You can see them below. The callback URL variable is optional. You can set that from the app web page during Echo Speaks setup.

Set environment variables

environment:
  - useHeroku=false
  - hubPlatform=Hubitat
  
 ## Set callback URL here if you want
 ##- appCallbackUrl=

[nclark]

@aaiyar

Portainer does make container management easy.

Got it installed on my Pi4 and the EchoSpeaks went nicely except for the fact that using 2 factor authentication on Amazon.ca gave me a bunch of errors and when I finally turned that off all went well.

[jtp10181]

@Marx

I tried and failed multiple times to deploy Echo Speaks to a Raspberry PI running Portainer Agent. Portainer Server is running on Synology.

Did you do this?

@jtp10181

NOTE: ARM or other non-amd64 systems (ex: Raspberry Pi)

If you need to build the image for a non-amd64 system, replace the image definition with this build definition instead.

    # Replace image definition with build for non-amd64 systems
    build: https://github.com/tonesto7/echo-speaks-server.git

[neerav.modi]

@aaiyar

You may wish to evaluate the use of Portainer to maintain your Docker containers.

@neerav.modi

Agreed. I already added that to my personal notes for my local linux server setup to strongly consider Portainer next time.

@aaiyar, I just went ahead and did it. Wow! I like it. Now I can do the other stuff with it!

Bit of a pain getting it working, because I didn't find @jtp10181's answers in another thread until after. Oh well. Now I understand the process and containers better. Win!

[jtp10181]

@neerav.modi

because I didn't find @jtp10181's answers in another thread until after

Answers for what? If something is missing from this guide let me know and I can fix it.

[Marx]

Yes. It worked last year when I had Portainer CE installed on the Raspberry. I consolidated and moved containers over the weekend which included replacing Portainer CE on the Raspberry with Portainer Agent. From my new Portainer CE (on Synology) I tried to deploy Echo Speaks to the Raspberry using Docker Compose with the image definition modified (as I did last year). Installation failed.

[neerav.modi]

@jtp10181

Answers for what? If something is missing from this guide let me know and I can fix it.

You had provided Docker installation instructions in another thread. Nothing missing here.

I just created a Docker / Portainer install guide for linux-based systems, essentially just dumping all of the commands I used and liberally add comments. Please link it in your guide above.

[christian.busch]

Hi, I got this working on my synology / docker. I keep getting "Amazon cookie refresh failed 408" errors for weeks but it's working.
Anyone know what to do about that 408 error?
I as wondering also where I can find the access token (?access_token=XXXXXX-XXXX-XXXX-XXXX-XXXXXXXX) for the callback URL?

[jtp10181]

When you do the server setup via the Hubitat app it gives you the access token to use.

If you don't have the callback url set correctly then the cookie server wont be able to send anything back to the hub.

It sounds like you got it working at least once, and sometimes that will work for a long time without needing to refresh the cookie. The refresh interval it does is very aggressive but prevents it from unexpectedly getting disconnected.

Sounds like you need to reset it on the Hubitat app, and go through the setup again. You can leave your docker container running.