Thanks, then why does my ES seem to be working correctly? I'm getting the announcements as I would expect
Because the app that used to run in Heroku is intended to fetch an Alexa cookie that echo speaks uses to login to your Amazon account. We were under the impression that had to happen every week or so, but evidently some users’ cookies have remained active for several weeks. Or a couple months, at this point.
When your Alexa cookie expires, echo speaks will stop working unless you pay Heroku to keep that cloud server running, or setup a local server instance.
The local server setup isn’t hard, there’s a few other recent threads dedicated to doing that.
4 Likes
Noob question as I have only recently started using Echo Speaks, using Alexa TTS for years and still using it in parallel...
How do I send a notification to all devices? With Alexa TTS there is an "All Echos" device that notification sends to all devices. Its not an announcement, just TTS. Curious what the equivalent is for Echo Speaks as I have mail, washer, and dryer notifications that I announce. Thanks!
1 Like
You can create an Echo Speaks Zone. And assign echoes to it and it will create a virtual echo device you can target.
Check out the ES Actions as well. They allow a ton of features that's are difficult to duplicate using RM and WebCore
5 Likes
I cant get echo speaks to work, i cant send test speech or announcement, i see all the device info , no issues to report on the app, here is the log i see for error
dev:10052023-02-09 02:06:31.055 PMerrorEcho (v4.2.2.0) | postCmdProcess Error | status: 400 | Msg: null
app:7562023-02-09 02:06:31.022 PMwarn EchoApp (v4.2.2.0) | finishWorkQ | 400 | Bad Request | [extList:[[cmdDt:1675969590363, cmdDesc:SpeakCommand, msgLen:6, isSSML:false, deviceId:756|echoSpeaks|G090U61091720V0M, callback:finishSendSpeak, msgDelay:2, message:volume, newVolume:100, oldVolume:null, cmdId:119]], nextOk:1675969593736]
app:7562023-02-09 02:06:12.955 PMwarn EchoApp (v4.2.2.0) | finishWorkQ | 400 | Bad Request | [extList:[[:]], nextOk:1675969575735]
app:7562023-02-09 02:06:00.729 PMwarn EchoApp (v4.2.2.0) | finishWorkQ | 400 | Bad Request | [extList:[[:], [:]], nextOk:1675969572499]
app:7562023-02-09 02:05:53.525 PMwarn EchoApp (v4.2.2.0) | finishWorkQ | 400 | Bad Request | [extList:[[:]], nextOk:1675969560256]
app:7562023-02-09 02:04:39.258 PMwarn EchoApp (v4.2.2.0) | finishWorkQ | 400 | Bad Request | [extList:[[:]], nextOk:1675969482030]
app:7562023-02-09 02:04:21.177 PMwarn EchoApp (v4.2.2.0) | finishWorkQ | 400 | Bad Request | [extList:[[:]], nextOk:1675969478799]
Just a guess, but the error message suggests there is no message (null). Did you enter text in the correct box before pressing the button?
Is it possible to add a parallelSetVolumeSpeakAndRestore() command to zones?
1 Like
FYI, this is what it looks like when your Echo Speaks cookie expires. I need to redo my RPi 0 W cookie server install. Planning to post a log of exactly how I did it for others who have asked about RPi 0 servers. I say "I". It's really you guys showing me how to do it! 
Mine expired 72 days ago. Echo Speaks is still working.
@Hal3 (and everyone), I have added instructions for deploying the cookie server on Portainer/docker-compose using a copy-paste yaml config file. Includes instructions for having it build a new image which should work on non-amd64 platforms such as Raspberry Pi systems. Please post any feedback on my thread: [GUIDE] Echo Speaks Server on Docker (and alternates)
2 Likes
I’ve been seeing this for a while. I haven’t noticed any issues either, but am mostly just using tts, not monitoring any Echo states.
1 Like
Same here. I just started seeing it over the weekend myself.
1 Like
My Cookie was updated 82 days ago. And still working too.
3 Likes
Anyone able to get song duration when playing music from Amazon?
I haven't touched my Echo Speaks for a long time. It is still working and I do not have a credit card on file with Heroku. Still waiting for the day it will stop working.....
Anyone using the Execute Routine Id function? I think Amazon may have killed that. I want to run an Alexa routine from webcore.
1 Like
I'm wondering if anyone else is having issues with Alexa's secondary prompts with echo speaks. This started a while back but I've been focus on migrating to the local cookie server so haven't pursued it until now.
I have a GE window AC in my office I have Hubitat control and the way I do it is the have echo speaks talks to the Geneva skill for GE. When setting the temperature I get a secondary 'are you sure' kind of prompt so I have hubitat delaying a few seconds then say yes. This has worked all along before. Now, the echo just makes a donk sound and the command quits.
So is there some new setting or known issue around this? The geneva skill works fine when I issue commands verbally to the same echo. And (while I'm working on rest980 to replace this method) I get the same thing when the iRobo skill ask if I want to mop after roomba is done.
