Quote:
Originally Posted by Catlady
I apologize. I went back and read the intervening posts, and I missed this option entirely.
But ... in my defense, what lunatic programmer decided that a voice command didn't need to be a voice command? It's ridiculous. And that's why my brain just skipped over the option to press the button for the routine-that-could-only-be-set-up-as-a-voice-command so that the routine didn't need to be triggered by a voice command. Seriously? This defies common sense so much, in my opinion, that even after reading the relevant posts again, I didn't get it; it took yet another reading for the light-bulb moment.
|
I think it is one of those things that you just have to know, and get over "that's stupid". To me it is very logical: it opens up a lot of possibilities. having troubles with a long verbal command, use a routine and shorten it up to " Alexa, abracadabra ". That nice new piece of hardware is "Alexa enabled", but doesn't have any UI in Alexa, use a routine.
You may not think it is logical, but somehow, it solved your problem, even though it is illogical.
What seems illogical to me is that they didn't do it sooner. And that they don't have widgets. And that they don't have parameter substitution for custom actions.
