Yes, if you also need to control a SmartThings switch from within an Alexa routine. But for some, all they need is just the contact for triggering an Alexa routine from SmartThings.
Thanks for feedback. Keep monitoring for a while to see if it remains consistent.
Adding an auto-revert would be fairly trivial.
I just tested my groovy virtual Alexa switch that wasn’t working at all yesterday and was inconsistent before yesterday, and it’s working well. So this may have been fixed by Amazon today?
Nevermind. It’s just less inconsistent than yesterday. Please disregard.
I am getting consistent results using the multi-trigger device where I’m still getting inconsistent results switching back to the switch/sensor device.
However, controlling multiple devices with a single switch is not particularly useful for situations where I’m controlling the behavior of a single device (or perform a single action) with a scene or a Routine. For example, I have multiple virtual momentary buttons to represent the different inputs of my home theater and when one is triggered, it causes Alexa to issue a custom action to change to that particular input. I wouldn’t want to trigger all the virtual devices from one switch because I don’t want to all the different input commands to be run, only a specific one. So, can this model of having a switch in ST and only the sensor in Alexa work with a 1 switch to 1 sensor setup?
Also, auto-revert is really needed otherwise you can’t replicate the behavior of the momentary button without creating a Routine to turn off the sensor.
Thanks for setting this up for us to test!
I can try. I’m not really familiar with the CLI but let me take a look at see if I can follow the steps.
You can get the device IDs and other info from the API Browser+ which is a web interface to the ST APIs and don’t have to download the ST CLI.
Just pushed an update to Alexa Multi-Trigger test driver that now includes autorevert. You’ll find the new option in the contact device settings for new contact trigger devices that you create with this driver update. (In other words, any contact devices you’ve already created won’t have the option).
Driver Version: 2023-05-13T00:43:59.737274872
Not sure I’m understanding this. There is a separate dedicated switch (in each component) for each contact device created.
Couldn’t you create a virtual switch in SmartThings for each device you need to control from Alexa? And you would loop those changes back to Alexa (if you need to) via automations to change the contact device states via the Multi-trigger device. Sorry, I’m probably missing your point.
My thought (for now) was to minimize the proliferation of devices by putting 19 switches in one device and only having individual contact devices. But I know this doesn’t solve the 2-way control need, and yes, for that it certainly is possible to use a different approach to create individual contact and switch device ‘pairs’ that are synched by the driver. If the Alexa reliability issue isn’t resolved with the current Alexa combo devices, then I’ll take a look at doing a separate driver that uses that approach.
The other downside of my current Multi-trigger test driver approach is that other third-party integrations that don’t work with secondary components would also be out of luck, since they couldn’t access the switches.
It does work pretty reliably for me ( fingers crossed)
If i can give a suggestion is to make the trigger name take the name of the text we put in place of . In automations creation in smartthings it shows up as trigger 1, trigger 2… this makes it more difficult to not mess up automations.
Thanks for the work
Was gonna say the same thing
Actually, ignore everything I said about the single switch issue because I did things in a hurry and didn’t really think through how this could/should work
I understand the desire to minimize the proliferation of devices, but in your vEdge driver, each device that is created is independent of the vEdge creator device. I think it would be less confusing if the synced contact and switch device pairs were created in a similar manner.
As far as managing ST devices from Alexa, the existing vEdge devices work reliably for me. I have ST virtual presence sensors that Alexa sets the state based on its geo-location. The ST Routines that utilize those virtual devices have been working flawlessly even as the ST->Alexa triggering has been intermittent.
I created an Alexa Multi-Trigger and have set up 1 test trigger so far. It seems to be working reliability with Alexa after multiple tries.
And since I am getting near the 200 device limit I like idea of having 1 central administrator.
I don’t think this is possible but I’ll look into it. Generally the labels that are shown in the app’s routine creation screens are defined at the time the device is created, based on its pre-defined presentation. That doesn’t allow for dynamically changing those labels.
It’s possible there’s some trick I don’t know about…
I was forced yesterday to refresh all my virtual switches and physical sensors in Alexa routines when I lost all them for about 12 hours. So I was able to analyse which routines failed and can confirm also in my case that switches used by Alexa to run devices in ST run perfectly.
They are labeled on the device details screen, but I agree it’s not very convenient.
True, but you see that when creating Routines or Scenes, it will be a bit of a pain.
My issue is weird.
This doesn’t work if I open this button from within ST.
But if I play this routine within Alexa the Hoover comes on. I’ve made sure the times are ok.
Anyone any ideas?
I dont think it’s an issue with the Switch contact sensor combo because if you see below. I have 2 of these, one to stop the Hoover and one to start the hoover.
Stopping the Hoover works, but starting it doesn’t.
Also, I have other similar ones to turn on nursery star lights and to turn them off and the only ones that seem to work are turning things off, which is bizarre.