Echo Speaks Will Not Maintain Amazon Login Status With Docker Installation

Hello Everyone,

Before I begin I want to acknowledge all the help and knowledge from the forum I have gained from reading about this subject. A special thank you to jtp10181 and the developer plantucha. I had absolutely no clue about docker, containers, hosting web sites on a Synology NAS but with their notes on the forum (and your as well) I think I have gotten most (hopefully it all correct).

After trying for 4 days though, I just can't get it to work. The login to Amazon will just not connect.

Following is what I have done, and the screenshots of the docker, web, and echo speaks installation. Can someone please tell me what I am doing wrong and help me get this to work. I don't want to do a restore and roll back to the Heroku version of the server install. It will not support a new echo device I purchased and I really like the idea of supporting the web portion locally on the my NAS.

Based on the things I have read, here are some of the ancillary things I have done during the installs.

  1. Rebooted Hubitat before and after Echo Speaks install.
  2. Tried installs using Chrome and Edge.
  3. Stopped Docker and Web Station many many times at various points.
  4. Tried both Echo Show & Echo Beta. Have been staying with Echo Beta.
  5. Tried the installs with & without 2-Factor authentication. Staying with 2-Factor authentication on.
  6. Rebooted NAS before installation, did the installation, rebooted after the installation. No help.

Docker Container Image


:

Docker Configuration Images:




Web Service Configuration Details:

Echo Speaks Install Images:





Note: The above is the only error I saw. Re-running the server install portion again was successful and it never occurred again.

If I can't get this working and have to restore and roll-back to the Heroku version, has anyone seen why a device would have its text and announce capability attributes set to no? This and reading the ability to host the web locally is what started me on this journey.

Thanks
Don

There are currently issues with Echo Speaks in general do to Amazon changes. Not sure if you have been reading the latest posts here

1 Like

Hi CaptWoody,

Thanks for getting back to me so quickly.

I am currently using the version below.

Hi CaptWoody,

I am currently using version v4.3.0.1 from HPM. It is marked Beta. I did try the only two version that are out there. I can't recall the other version but I don't think it was v4.1.0.0.

Do you think I should roll backwards?

Don

If you are trying a new install/instance, regardless of version, of ES it will not work with the changes Amazon has recently made.

The only things that work at the moment are existing installs, or restoring a previously working setup from a backup.

1 Like

Just completed the restore. Thank you for getting back to me. I am sure I would have spent countless hours still trying.

  • Don
2 Likes

The same thing happened to me. I restored a previous backup and all was fine. Then lost the cookie again. Tried several times to login and couldn't. Then hours later the cookie refreshed. I think now if it doesn't refresh on its own I'll just let it run.

1 Like

So far, all is good. I just added a Sonos ear 100 to add voice back to the Kitchen. I now have 7 alexa female voices making announcements and one deep male voice making the announcements in the kitchen. Sounds like a fight :-). Knowing this is an option for text announcements, Alexa voice will be turned off, and more Sonos device will be placed throughout the house [but in less numbers]. Once again, hats off to the Hubitat group for providing voice natively within the OS.

  • Don