I have been told that virtual switches are no longer supported in Alexa. So I created a virtual contact sensor. This just trigger correctly but since it is not a switch, but I need to figure out a way to show the context switch is closed. Any ideas or am I heading in the wrong direction?
When did that happen? - I have two or three virtual switches that I use daily in Alexa, and as of this AM, they were working just fine..
Something change, like today, that I missed? -
Did you try creating a Virtual Switch (I know that works in HE), and then exposing it to the Alexa App - Was there some error reported or ? - What exactly isn't supported any more?
1 Like
Virtual switches work fine. It is possible that @griffin meant that they canât be used as triggers for Alexa automations?
One of them (VS) I use as a trigger for an Alexa automation - Now I'll need to double check if that stopped working (it's not something that I routinely use).. I could easily make it a contact it needed..
That is correct. That is why I am trying to use a virtual contact center.
As long as the virtual switch youâve projected into Alexa uses a driver that exposes both switch (on|off) and contact sensor (open|closed) capabilities/methods then youâll be fine.
One such example would be the quite commonplace âvirtual momentary switchâ driver.
3 Likes
if you want a device that can be both a contact sensor and a switch and stay in sync, check out uDTH.
2 Likes
I should not have stayed up all night before coming here. Lack of sleep really screwed me up. Virtual switches work just fine in Alexa. Just not as a trigger.
AFAIK, this is true of switches in general, and this has always been the case.
2 Likes
