I used Echo speaks extensively back when ST supported it. I wish I could remember who posted the following method of getting your Alexa devices to interact with ST, as I couldn't get the original webcore pistons to fire correctly.
So I made a few new rules in hubitat and have it working again, although I have a few things to tweak with regard to volume and playlists.
If you are interested, you need to set up 2 rules in Hubitat, 2 routines in Alexa and two virtual switches.
The two Alexa routines need to be linked to the virtual switches. For example,
Alexa Routine named AA answer yes
When you say: Alexa, yes please
Action: AA Answer Yes (virtual Switch) turn on
Alexa Routine named AA answer no
When you say: Alexa, no thank you
Action: AA answer yes (virtual switch) turn on
Then you need to have two rules set up in hubitat.
Since I set my first rule up in simple automations, I have it set to 1 minute, but in reality it should be around 30 seconds. If you run more than one question or routing within within the specified time (plus time for responses and actions) minute it will overlap. So keeping it shorter is better, but I don't have enough things going on to worry about the extra time in this step.
That will just take the answer that you give alexa, turn on the switch and then reset the switch to get it ready for the next time you run a question rule.
The next rule I made in RM, it doesn't have to be very detailed, but in my case I want my wife to be able to dry off, and exit the shower into the sink area before Alexa asks her the question.
Basically take the above and simplify it to:
- Trigger
- Ask question
- Wait (half of answer time or around 15-20 seconds)
- Determine yes or no
Run yes or no action - OPTIONAL - add the no response action. Sometimes it was difficult to know if alexa didn't hear us, or just errored, etc... So adding the no response just lets me know that that it thinks there was no input.
However, using step 5 also allows all of your questions to have three possible rule actions. Just treat it like a third answer. A non response triggers the third option.
We not only use it to turn on the lights and stop the motion in the bathroom while she gets ready, I've automated some Plex actions so that if we are all alone at night, it sets lights when we turn on plex or the tv. But if we have company, or are busy doing other things and want to leave the lights on then it leaves everything alone.
So basically if you sometimes want a scene, want to be able to conditionally activate a rule, pause a rule or at least have the choice via voice...
