I have been researching and tweaking code to get this to work with my echo dot, trying all the different available commands for speak. The test message in the APP plays on it, but when I try to use the commands in a piston, she doesn’t say anything. Am i missing something? Help!! Obviously this is just a test piston I’ve created to troubleshoot, I plan to use it for more exciting things!
Thought I saw somewhere where the wait command was causing issues. May want to try it without the wait or separate it from the wait from the Echo (i.e. With Location Do Wait 5 seconds).
The issue with wait commands is referring to there use in executeSequenceCommand() not in WebCore.
I’m wrapping up some fixes and new features for release right now
It doesn’t work without the wait command either. Or any other speak or announcement command either with out without volume controls. I’ve tried them all. I only added the wait to see if that helped. Thanks for trying to help tho
That’s very odd. Are you seeing any errors in the IDE logs?
Check under these logs while you try to execute the commands
I don’t think it likes the message being sent… I’m actually updating the documentation for the new release which makes the speak commands way more flexible and reliable.
I expect to release the update in the next few hours.
Sorry I’m know I’m probably posting in the wrong place but I believe I have integrated github to SmartThings IDE but when I update via repository and select the items in New (only on GitHub) I get an error:
Error: 500: internal server error
What do I do or what do I reference next?
Try again using an incognito or private browser tab.
I know i promised to push an update a few hours ago but i got hung up. Once i finish the new announcement test i’m ready to push out.
Notice: The announcement test in the app needs more work. It’s not setting the volume like I want before announcing.
Updated and tested the wait in the sequence - looks like still broken.
Wait is not broken… I’ve used it hundreds of times over the past few days
Send me your exact sequence string you are using
The first statement is executed but not heard on the the device, only the second one. I might be doing something wrong here, will be happy to learn and correct
@tonesto7 …Here’s a LONG speak command test. Worked like a champ! This is awesome. Woop woop!
out of curiousity why the waits at end?
Can you humor me and use the sequence tester in the app?
It’s under the main page > Device Tests > Sequence Creator Test
Test this sequence string please
volume::80,, speak::i'm testing wait number 1,, wait::5,, speak::waited 5 seconds,, wait::5,, speak::I waited 5 more seconds
The wait at the end is needed as it takes time for google assistant to detect the end of the text and start the broadcast.