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 
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".
That's like when someone doesn't understand what you said (or doesn't speak your language) and wants you to leave them alone, so makes perfect sense! Alexa is basically saying I have no idea what you said but if I say OK will you stop talking to me? 
3 Likes
Is there a way to pull the cookie status via rule machine to notify me in the event I need to refresh it? Mine hasn't updated in 92 days.
Echo Speaks has notifications built in, you can send it to any notification device.
6 Likes
Appreciate pointing me to that section. Never poked around in the notifications area.
Hi,
I have these errors and warnings in my log and can't decipher them.
EchoApp (v4.2.2.0) | wakeupServerResp Exception: java.lang.Exception: No response data exists for async request
EchoApp (v4.2.2.0) | wakeupServerResp | Stack Trace: java.lang.Exception: No response data exists for async request
at hubitat.scheduling.AsyncResponse.getData(AsyncResponse.groovy:71)
at user_app_tonesto7_Echo_Speaks_167.wakeupServerResp(user_app_tonesto7_Echo_Speaks_167.groovy:2228)
EchoApp (v4.2.2.0) | wakeupServerResp Server may be down / unreachable
EchoApp (v4.2.2.0) | wakeupServerResp: 503
Can someone help me out?
I really appreciate any help you can provide.
If you are not sure Alexa heard you correctly, ask her "Alexa, what did you hear"? She will play back what she heard, which might be what you said, or not.
4 Likes
just deployed echo speaks server to docker on a synology, and after copying in the callbackURL, echo speaks on the hub is showing the internal docker bridged IP, and not the externally routable one. The echo speaks page shows the proper one.
Any way to fix this?
It SEEMS to be preventing it from working (which makes sense since the hub can't get to the .66 address, just .6 (which is the subnet the hub is on)
Check my write up, it shows you how to tell the server what IP to use.
1 Like
Thank you sir! That seems to have done it. just had to set "ipAddress" under advanced settings,
Thanks!
Not that it seems to affect anything, but my Echo Speaks server running in Docker on a Synology NAS stops unexpectedly every five days like clockwork. Thank goodness for auto restart! The app itself continues chugging along nicely. Love it.
Yeah I have the restart in my instructions as well. Someone in one of the threads found an exit statement somewhere in the code they think is probably killing the process under certain circumstances right after the cookie refresh. Sounds like that's what yours is doing.
2 Likes
Hi all,
Has anyone been getting errors in the last couple of days?? I have mine set on a synology nas and it’s been working flawlessly until a a couple of days ago when I started getting these errors in the logs:
getAvailableWakeWords Response Exception | Status: (500) | Msg: status code: 500, reason phrase: Internal Server Error
And I get notifications through the Hubitat app from echo speaks saying:
Echo speaks data refresh issue: the echo speaks app has NOT received any device data from Amazon in the last (14066) seconds. There may be an issue with network
I think these issues only started occurring since the cookie was last updated recently. I tried a manual cookie refresh which seemed to work but then I still got the same errors
1 Like
Nope, I haven’t seen these. Echo Speaks service is running locally on a Rasp Pi 4b, it just refreshes the cookie every 5 days like clockwork. Now, Comcast Xfinity Gbit has been going up/down for the past week as they make some changes, but I just switch over to our AT&T DSL that we have as a second feed for reliability
1 Like
I migrated from a C7 to a C8 on Friday (9 March). I just noticed today that my cookie refresh is failing with this error in the Hubitat logs: "EchoApp (v4.2.2.0) | Amazon Cookie Refresh FAILED 408". (I'm unsure if this started immediately after the migration since my logs don't go back that far.) Is there something I need to do because of the hub change? Or does this just look like a normal Amazon hiccup?
408 is a server timeout, should resolve itself.
