I found something similar, a "Response Designer" for (Switch) Trigger Events.
So, it can be done in the EchoSpeaks app, but not in a rule?
Does that mean the trigger for the Rule cannot be the same as the trigger event specified in the EchoSpeaks app? Otherwise, how would I know which runs first, or whether they try to run at same time?
Also, seems the speech designer is available for an "announcement" but not under speaks.
Not sure I know the difference between speak and announcement. From the Alexa app, an announcement has a preceding chime, but I didn't hear that when I tested the action in the Hubitat EchoSpeaks app.
My apologies I got sidetracked when you said Response Designer -> I immediately went to Echo Speaks and Speech Designer. Trigger for the rule and ES Action could be the same, but then theyāll attempt to fire at the same instant. Could have the rule set a momentry switch or some other trigger for ES if you want to control when it speaks.
Havenāt tried it, but it occurs to me that you may be able to put the SSML in a variable and then speak the variable frm the ruleā¦
I didn't try to synchronize the speech with actions in the Rule. I don't care exactly when the speech occurs, as long as they don't somehow collide.
I had to add delays between rule actions to get them to run reliably. The rule actions issue http requests and run custom methods that issue http requests. They didn't work reliably until I added delay actions. Here, (as a delay action) the minimum delay is 1 second--much longer than I need, but it's ok.
I doesn't seem to hurt anything (yet) to let the speech action from the EchoSpeaks runs in "parallel" with the Rules actions.
I really like having one voice for the "OK", which says Alexa recognized the utterance.
Having another voice that includes what was done in the action makes it easier to debug when things go wrong. Alexa misunderstood? Something in my backend failed?