I have a couple Sengled bluetooth bulbs connected to Alexa as dimmers, Alexa controls them just fine as individual bulbs or in a group
Would like to either control them directly via HE (haven't found a solution yet), or create an Alexa routine that uses HE virtual switches as a trigger (When this happens) to turn off the group with the Sengled bulbs in it
I can't see the virtual switches in an Alexa routine (when this happens) either as a VS or when placed into a group.
Alexa Routines can only be triggered by a Motion or Contact sensor, not a switch. This is an Alexa issue, not a Hubitat issue.
To get around this limitation, you could use my Virtual Motion-Switch driver. It allows you to use the Switch on/off commands in Hubitat, while using the Motion active/inactive states as triggers in an Alexa Routine.
Every once in a while Alexa will get forgetful... Try removing the switch from the Alexa Echo Skill app, save and exit (this should invalidate the rule on Alexa also). Go back into the app and re-add the switch, then go into Alexa and re-point the routine to the switch.
Finally got it working to turn the light on via an Alexa Routine, however the v-switch-motion device (using the driver suggest above by @ogiewon) doesn't stay active, since it goes inactive with a few seconds, so Alexa turns the lights off right away
Here is what I have, a simple V-Switch gets turned on, RM Rule then turns on the new v-Switch-Motion which is passed to Alexa, she turns the light on,
Create a new driver using the code I posted and use it instead. Alexa will respond to either a motion sensor (your first implementation) or a contact sensor. A motion sensor by definition will eventually go from active (switch on) to inactive (switch off), A contact switch can stay open or closed until some other action changes it.
Ahhh...sorry about that. I actually use it in the reverse fashion...Amazon turns on the switch, which triggers a motion event in Hubitat momentarily. My driver automatically resets itself to be read for the next event...
You’re wanting to go the opposite way, and the driver posted by @thebearmay should do the trick.
Just use a Hubitat Virtual Switch. Make sure to enable the “Auto Off” option on the virtual switch. Share that switch with Alexa and simply “turn it on” in an Alexa Routine based on a voice phrase trigger. Then, in Hubitat, use that virtual switch as a trigger in RM to run your Hubitat automation.
I have installed the Virtual Motion with Switch driver, Created a new device for it and it works from the Device app. The problem is I cannot get the device to show in Alexa, I have removed and re-selected it several times but it refuses to display either on PC or tablet. Is it related to this worrying line ? " If you include a device that isn't compatible with Alexa it will just be ignored and not sent to Alexa."