Echo Speaks does not speak

#1

1) Give a description of the problem
I’ve been trying to get my Echo devices to speak. I have Echo Speaks installed, and have ensured that it is updated to the latest version in the IDE. The various “say…” commands work fine, but I would like to use my own text. I have tried all of the “speak” options but to no avail.

The test piston is just a light switch piston I added the test to.

2) What is the expected behaviour?
I expected the “speak” or “speakText” commands to work.

3) What is happening/not happening?
It does not speak…

**4) Post a Green Snapshot of the piston

image
image.png1178×731 31.7 KB

5) Attach logs after turning logging level to Full
5/18/2020, 3:26:35 PM +701ms
+2ms ╔Received event [Office Accent Light Switch].button = pushed with a delay of 108ms
+89ms ║RunTime Analysis CS > 19ms > PS > 56ms > PE > 13ms > CE
+91ms ║Runtime (37989 bytes) successfully initialized in 56ms (v0.3.110.20191009) (89ms)
+92ms ║╔Execution stage started
+99ms ║║Comparison (enum) pushed gets (string) pushed = true (1ms)
+101ms ║║Cancelling condition #2’s schedules…
+102ms ║║Condition #2 evaluated true (6ms)
+103ms ║║Cancelling condition #1’s schedules…
+104ms ║║Condition group #1 evaluated true (state changed) (7ms)
+106ms ║║Cancelling statement #3’s schedules…
+233ms ║║Executed physical command [Office Accent Light].on() (122ms)
+234ms ║║Executed [Office Accent Light].on (125ms)
+290ms ║║Executed physical command [Office Accent Light].setLevel([100]) (53ms)
+291ms ║║Executed [Office Accent Light].setLevel (54ms)
+294ms ║║Cancelling statement #10’s schedules…
+365ms ║║Executed physical command [Echo Dot].playText([Testing, 1, 2, 3., 60]) (63ms)
+366ms ║║Executed [Echo Dot].playText (65ms)
+372ms ║║Comparison (enum) pushed gets (string) pushed = false (1ms)
+374ms ║║Cancelling condition #7’s schedules…
+375ms ║║Condition #7 evaluated false (5ms)
+376ms ║║Cancelling condition #6’s schedules…
+377ms ║║Condition group #6 evaluated false (state changed) (7ms)
+379ms ║╚Execution stage complete. (286ms)
+380ms ╚Event processed successfully (379ms)

Piston not firing Echo Speaks after wait
#2

Your log shows that the correct command was sent.
Most people have success with: Speak text "Testing"

Maybe try:
executeSequenceCommand
volume::50,, speak::Testing testing,, volume::30

pic

(careful with the required double colons and double commas)

Weather alert if it rains in my region
#3

@WCmore That did it, thanks!! Any idea why that works but the normal commands don’t? Also, is there a master reference to all of the commands? The wiki is pretty light.

#4

From what I have seen, certain versions of Alexa work better with certain commands.
(so don’t be afraid to test, because each of your devices may react differently)

#5

I never would have thought to use executeSequenceCommand.

#6

Try this link.
(most commands are found up top under Support > Device Attributes/Commands)

pic

#7

Perfect, thanks!

#8

Any idea if there is a way to pass a variable into the executeSequenceCommand? It looks like it only allows a string. I was hoping to provide a random message of my own making.

#9

In the “Value” box, you can wrap the string variable's name in curly brackets.

IE:

pic

#10

FYI, I have found sometimes when updating the device and/or SmartApp in the IDE, my echo devices won’t respond to speak commands until after I go into the echo speaks SmartApp within the SmartThings app and save. This seems to confirm the update and things start working again. I have made that a habit whenever I do updates. Not sure if this is effecting you but something to try. I have never used the executeSequenceCommand.

#11

@WCmore thanks again!

@guxdude I’ll try that this evening, but even if it doesn’t it looks like I have a pretty good solution.