WebCoRE asks a question, my voice response determines the action

text-to-speech
answer
query
voice
alexa

#184

Ya beat me to it! I had mine originally built with the simple yes/no responses. But, as you said, since then, Alexa reserved “yes” and “no” for their use. - making those no longer function properly. Now I use “Yes please” and “No thank you” as appropriate. Works just like the original intent.


#185

Ahhh okay - I missed that part so my apologies and thank you for pointing it out. I’ve got it working now! Time to start adding more of them!


#186

While I am thinking of it, I’d like to make a call out to the community:

If anyone can suggest a one syllable word to represent “Yes” and “No”, I would love some ideas and feedback here. My goal is to keep the phrase as short as possible, yet somewhat natural.


I am debating using “True” and “False”. I could reword my questions a bit to match.

IE:
webCoRE asks, “The trash is already at the street… True or false?”
I respond, “Alexa, False”
webCoRE speaks, “Don’t wait too long… There’s a 45% chance of rain in an hour”


Any other mono-syllabic ideas besides “True” and “False”…??


#187

For the record, we can make duplicate Routines in Alexa, that all do the same thing, using a different phrase. It takes a tiny bit extra time to make those extra Routines, but it allows for anyone in the family to use an answer that fits them.

So, for example, let’s say the household has Proper Patricia, Binary Billy, Military Michelle and Surfer Stanley… The following four phrases (Routines) can all turn on “Answer Yes”

  • Alexa, Yes please
  • Alexa, True
  • Alexa, Affirmative
  • Alexa, Far out!

Along the same lines, I could make four Routines to turn on “Answer No”

  • Alexa, No thanks
  • Alexa, False
  • Alexa, Negative
  • Alexa, Gnarly

If we are creative here, the same two SimSwitches can handle many types of questions…
(even beyond the typical Yes/No variety).


If you already have the Routines created (as my first post), then the quickest way to do this is:
Phone > Alexa App > Hamburger menu > Routines > “Alexa, yes please” > Three dot menu >
pic

Then, all you have to do is use a different phrase. I just tested half of these phrases, and they properly turned on the correct SimSwitch. Many other words or phrases will also work, which means that our questions can actually get much more complex. (as long as we keep in mind the 3 possible outcomes)


I’d still love to hear some alternative short phrases, if anyone thinks of any…


#188

My phrases are kind of long but they seem to work. I just tell the person what to say.

I just add the command that needs to be said. My wife can never remember what I tell here to say, so Alexa tells us after the question is asked.

Plus I always make the more common response as the default so you don’t have to say anything.

True and False seems ok to.


#189

Now that I am using Echo Speaks and can determine which Echo device I am talking to, and which device should respond, this opens up a whole new world of possibilities. @WCmore, thank you sir!


#190

I had installed Echo Speaks on my Hubitat hub awhile back but since I am still running my ST hub as a remote to my HE hub, I left most of the Echo speaks stuff on it.

Yesterday I finally moved over the pistons from ST to Hubitat that determine which device you speak to. My ceiling fan routine which generally took about 15 to 20 seconds to respond in ST takes 5 seconds on a Hubitat hub.


#191

Weird…my piston works in about 5 seconds. What does your piston look like?


#192

I thought that delay was because Alexa does not report that info in a timely manner.
(meaning, I thought it was entirely outside of webCoRE’s influence)


#193

There’s a trick to it. If you use getDeviceActivity, it cuts down the time significantly.


#194

Oh right… Different command… Different delay…
(which should be the same in Hubitat, I imagine)


#195

I think we already had this discussion. As I said in the other thread, I call a common piston with getDeviceActivity, then have a global set that the calling piston uses to determine which device. The biggest delay was getting the global updated between pistons. That seems much faster in HE.