Tested that in the app and worked fine. Added to my test piston (attached) as the last command, and that was the only one the device spoke. waits seemed to work on the last command but the previous two were not heard.
Screenshots in the Documentation are missing
thanks for the heads up
I just pushed up the fix
the only item i can see is the … in the text.
I have got myself truly aggravated.
I have gone through this installation 3 times and still cant get Echo Speaks functioning. Everything is installing exactly how the wiki describes. In the end my devices show up saying online but I can never get my test announcements to work. What am I missing? I’ve been reading through these 2400 comments for nearly 2 hours. I’ve also gone through the common problems link on the wiki and don’t see anything detailing what to do when everything installs and deploys correctly but the devices dont respond. Help. Me. Please.
are you testing using the device ui or inside the smartapp
From the smart app
Made no difference to try in incognito mode still same error.
Do I need to go through the clone forked repository, configure github to sync with SmartThings tutorial? I thought once we publish the echo speaks repo and get the update via repo working that is all I need to do to get updates?
So, I removed the three dots (is there any related restriction) and modified the piston to include 3 individual sequence statements with 3 individual echo references. then added a 4th one with 3 statements by a single echo object. the results are the same where only the last statement comes/plays thru the device. more so, there is no wait - the last one (has “second time” in the text) is played immediately, as if the previous ones are ignored (although they show in the log, see attached).
Hope this additional info is helpful
not sure why i didnt see it before.
WebCoRE is executing all three commands at once. They are basically overwriting each other then amazon is rate-limiting
Hmmm, is that documented anywhere (in webcore’s documentation)? I do know that if you put location::wait as part of the flow, they are actually getting sequenced, but that is ugly (but, if that is the only way, so be it ).
Is there anyway to control the parallelism?
add all of those into one executeSequenceCommand() Amazon will execute them sequentially
Will try, that is what did not work earlier. btw - the piston level setting for parallelism are off
@tonesto7 I use the random speak command and it never failed me, but no I get nothing using it. Below is my piston, please take a look.
that piston is working for me…
I’m having such a lot of fun with this app, thank you so much for working on it!
I have a piston to play an ambient sound sourced from Spotify in the bathroom when it’s occupied. It plays fine but for some reason it always pauses itself after about a minute of playback. Does anyone know why?
hmm… It’s nothing i’ve seen occur before, but I don’t have spotify so it’s not something i’ve been able to test much.
I wonder if other users are experiencing this issue.
Thanks for making the music search available in the executesequence() command!
Just to let you know that ES will now convert a date input such as “3 February” into a temp ie: ( 3 degrees F)
Any suggestions on why mine isn’t working? UPDATE: I find that it works, but not all the time. So either it is on my end or Amazon’s end.