[RELEASE] Echo Speaks V4

First time, complete virgin install. The Heroku app was "successfully deployed", I hit View and get the Goto [Amazon] Login page/button (documentation steps 6 & 7) but rather than being asked for my Amazon credentials I get "There's nothing here yet".

Ideas? Pretty sure I missed a step configuring Heroku.

Heroku requires a monthly fee. Why not run your own cookie server?

There's lots of option to run in a container on a NAS, docker install, Linux VM, RPi, etc.

Unfortunately, I don't know that there's a definitive step by step how to for all of them.

I'm a big iron guy and figured out how to get it running on a Ubunutu VM on my Win10 machine, so probably anyone can do it.

Take a look through a few of these and decide what platform you want to install on and go from there.

1 Like

Is everyone getting tons of errors from Echo Speaks these days? I got the impression that you all were and they were harmless. But, I'm getting a lot of low memory errors so I'm looking at everything. Of note, Echo Speaks seems to work just fine. Examples in the past few minutes:

I have not gotten any errors in the past 3 days.
I did do the patch to fix the playlist error, but that is not the error you are getting there.

It is saying the server may be down, not sure if thats the cookie server or the Amazon server it is complaining about.

Do you have any sort of DNS based ad blocking on your network that could be blocking something?

Otherwise you might try rebooting your router/modem and then shut down and reboot the hub. See if that clears it up at all.

Yep, I’ve been seeing similar. Alexa seems to be off her meds. Seems to be subsiding.

https://downdetector.com/status/aws-amazon-web-services/

The wakeup server messages are referring to your ES server that you stood up.

I would check it is running and network accessible.

UGH! Yes, THAT'S WHAT I HAD RUNNING ON THAT OTHER RPi. I thought it wasn't doing anything. I shut it down a couple of weeks ago. Thanks @nh.schottfam! And @jtp10181 where's the patch to fix the playlist error? I'm getting those too.

See this post up above: [RELEASE] Echo Speaks V4 - #1483 by jtp10181

1 Like

Done. Thanks jtp.

It seems that the latest generation Echo Show 5 is being found as an unknown device. @tonesto7 can we get that device correctly added? Does anyone have this device working correctly?

See my post upthread:

1 Like

I copied the code for one of the older Echo Show 5s and changed the attribute to the new Show 5. It works beautifully.

Many thanks!

1 Like

I don't pay anything. Free Heroku account works fine. Am I missing something? I don't use Echo speaks for more than a few phrases.

I believe we were all under the impression, due to announcements from Heroku, that what previously was available for free, including the types of accounts that echo speaks relied on for cookie refresh, would require some monthly payment.

Maybe it’s possible to use Heroku in a way that stays below a threshold and avoids actually getting charged for usage?

I switched to a local cookie server last November when Heroku’s announced pricing changes went into effect, so I’m not sure.

2 Likes

Just looked at my Heroku account and my deployment date was June 30, 2022. Maybe I'm on a grandfathered free account? :man_shrugging:

My Echo Speaks is also still working with the free Heroku account.

1 Like

Well, my Echo Speaks server is just gone. So I recreated it on a raspberry pi. I must be doing something wrong because while I did get a cookie this IP address shown below is WRONG. I don't even have a 10.x network at home. How do I set this to the correct IP address? I can't find that... The port is correct, but the IP is wrong. Should be 192.168.4.129 Thanks folks. Feel like an idiot here lately.
image

It's correct on the server itself though.

Stumped.

Guessing you deployed with docker? Docker uses its own internal bridge networking which messes with the IP detection. My guide shows how to override the IP detection and set it. [GUIDE] Echo Speaks Server on Docker (and alternates)

2 Likes

Heroku may have been up-selling when asked by users if some free apps could continue to work?