[RELEASE] Echo Speaks V4

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! :slightly_smiling_face:

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'm getting this today about every 30 minutes. Device still seems to work though.

1 Like

This another api change, that @tonesto7 may have to look at.

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

NTF here.


image

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.

I have several rules using the echo speaks voiceCmdAsText command and they all still seem to be working. I don't have anythign that responds back though, so can't say if that is an issue.

I have a rule that skips some alarms when there is no school and every time Alexa asks if you want to cancel all the recurring alarms so I have to wait 4 seconds and send a No. That still works AFAIK.

I have noticed other random things though like if I verbally say to turn on the Family Room Fan it just makes the "donk" sound as you call it but then does nothing. If I say Turn on the Family Room CEILING Fan, it will say OK and turn it on.

I just attribute it to Alexa getting senile, it seems to be getting dumber the longer I have it, you would think they would improve it over time but obviously Amazon is not in this for us, just for data and cash.

3 Likes

Ok, thanks, maybe I'll try tweaking the timing of the secondary prompt and see if it changes the behavour :slight_smile:

Sometimes, I say "Alexa turn on the fireplace" and she says "OK" and nothing happens. She is SUPPOSED to answer "I am turning on the fireplace" and it turns on. Sometimes I have to repeat the command to get the correct answer and action. So, maybe she just does not hear me correctly and just answers "OK".