Piston fires but Echo Dot doesn't speak

#1

1) Give a description of the problem
I really don’t know what’s going on with this, it worked for a while (about an hour) and then just stopped. The piston is firing and the echo dot is receiving the command in the ST IDE but no speech

2) What is the expected behaviour?
Once motion changes to active the echo dot should say “Hello”

3) What is happening/not happening?
No speech from dot

4) Post a Green Snapshot of the pistonimage

image
image.png1178×462 20.6 KB

5) Attach logs after turning logging level to Full
(PASTE YOUR LOGS HERE THEN HIGHLIGHT ALL OF THE LOGS AND CLICK ON THE </> ICON TO FORMAT THEM CORRECTLY)
6/2/2019, 3:27:34 PM +413ms
+2ms ╔Received event [Kitchen].motion = active with a delay of 81ms
+131ms ║RunTime Analysis CS > 18ms > PS > 79ms > PE > 34ms > CE
+134ms ║Runtime (37464 bytes) successfully initialized in 79ms (v0.3.10c.20190522) (131ms)
+136ms ║╔Execution stage started
+149ms ║║Comparison (enum) active changes_to (string) active = true (1ms)
+151ms ║║Cancelling condition #2’s schedules…
+153ms ║║Condition #2 evaluated true (9ms)
+155ms ║║Cancelling condition #1’s schedules…
+156ms ║║Condition group #1 evaluated true (state changed) (13ms)
+159ms ║║Cancelling statement #3’s schedules…
+601ms ║║Executed physical command [Echo - Kitchen dot].speak([Hello]) (433ms)
+602ms ║║Executed [Echo - Kitchen dot].speak (436ms)
+606ms ║╚Execution stage complete. (470ms)
+607ms ╚Event processed successfully (607ms)

#2

Sorry but could someone delete this please, I have discovered it was the cookie in Echo speaks. Have to look around to see why it expires after such a short period. Thanks.

#3

I have experience a similar issue, my piston that ran an Echo speak command execute but Echo no longer speaks. What is the echo speaks cookie that you are referring to?

#4

I would recommend to keep the post.
I’m sure some people will have the same issue and they can find the solution here…

#5

Hi did anyone answer you - I have the same issue … so its a cookie issue ?? where

#6

Nobody replied so I have tried clearing the service data again and redeploying the app (again). Same issue, cookie is only good for up to 36 hours and then it just stops working again.

If you go into Echo Speaks smartapp in Smartthings, and scroll down to Alexa login Service, tap to modify and at the bottom there are toggles to refresh Alexa cookie. That’s what worked for me anyway. There are further reset options below that but use them as a last resort.