I am fairly new to Control4, but quickly getting up to speed.
I am posting both as an end-user, and also as a new employee of a company that installs Control4. I had them install light switches, thermostats, cameras, door locks, etc., along with a couple of Control4 controllers, to automate a lot of my home, so I can demo various functions to potential customers.
Anyway, it's all working quite well, with the occasional quirk. I previously used a Harmony Hub/Remote, linked with Alexa, and used Voice Control to turn on my Theater Room, and really liked it. So I enabled the Control4 skill in my Alexa account, am able to customize names for various devices, lights, scenes, etc., and to me, it adds huge convenience over reaching for a phone, the Control4 Tablet, etc.
But (there's always one but, isn't there!), one of the quirks is a bit annoying:
I created a Lighting Scene that would turn all the downstairs lights off in my home, and I can activate it by Phone, Tablet, Voice by Alexa, etc. Then I thought it would be even better if I built in a few delays, to keep certain lights on so I could see while walking from the Family Room, where the Echo Dot is located, to the stairs to our bedroom. In Composer Pro, I added a 10 second delay for 1 light, and a 20 second delay for another light. When activated from either Composer Pro, the Control4 App on my phone, or the Control4 tablet, it works exactly as desired, giving me time to get upstairs before the final lights are turned off.
But when I activate this same Scene with an Alexa voice command, all lights turn off Immediately, and the delays don't occur.
I have disabled and re-enabled this Scene within the Alexa App. I deleted the Scene from Alexa, disabled it within the Alexa section of my personal Control4 log-in, re-enabled it there, rediscovered it within Alexa, etc. I renamed it from "All LIghts" to "Downstairs Lights" to avoid possible confusion. But no matter what I do, when I tell Alexa to activate this scene, all the lights go off immediately, without the delays that are actually programmed into the Scene.
This may just be a quirk or limitation of the Alexa interface, but it just seems so strange, as theoretically, it's simply activating the same Scene in Control4, which works as it should when activated from the other sources.
Am I missing a step here?
Thanks.