When you say they are non-functioning, what exactly do you mean? For example, can you operate the switches manually from their Controls screen?
I can turn the lights on and off in SmartThings. If I attempt to turn the Virtual Switch on, nothing. I should add that all of these lights have WIZ bulbs. But, as I said, some of the Virtual Switches work fine and others do not. All the wall switches are in a permanent ON position. So, it’s only thru the WIZ integration they are operated. I tried turning the integration OFF and then reactivated it. Everything remains the same.
Figured it out. For some reason, the routines/automations for those switches were disabled. No idea how that happened. Thank you
1 Like
Thank you! This worked perfectly for me getting Alexa voice integration with my zooz multi relay (zen16). I didn’t have any issues setting this up and I feel like Michael Knight when I talk into my fitbit and say “open big garage door” and it goes up.
3 Likes
Ran into a weird issue with the virtual momentary switches. They wouldn’t stay off. With all the associated routines disabled, if I manually turned the switch off in smartthings it would immediately turn back on, like it’s doing the opposite of what you expect.
I fixed it by pressing the momentary trigger in the device details in the Smartthings app, then it seemed to revert back to the correct behaviour.
Just letting you all know 
Sounds like you have auto-revert configured in the device settings.
Of course, otherwise it isn’t a “momentary” right? Am just confused why it would revert to on instead of going back to off after being switched on. Is this intentional or did I confuse some kind of internal “toggle” state for a moment? Is there an intentional trick to changing which way round it is?
The ‘Button effect’ setting allows you to define the behavior either way. This provides max configurability.
1 Like
Sorry, yes I see. So the question that remains is how did the behaviour change without the setting changing?
I have some 50+ multi -trigger virtual switches running since the problem created with virtual switches by Alexa a couple of months back. As I use rules, all my notifications are through Alexa and this trigger works great. I have all of them configured to Auto Revert.
Not a real problem but I would comment that at least twice a switch has ‘changed itself’ from auto revert OFF to auto revert ON. Means I have to unselect autorevert on the child switch, turn off on the main switch and then select again. Haven’t been able to seen any reason for this but on seeing this post I remembered.
BTW Thanks for your work, and I do hope @TAustin you maintain the Multi Trigger.
1 Like
Wow that’s a new one: device settings changing all by themselves?! We’re going to have to keep an eye on this one. I’ve no idea how that can happen, as device setting changes are user-initiated and strictly in the realm of the SmartThings app. The driver only gets notified of changes. Nevertheless, I’ll double check the code to see if there’s any way this could inadvertently happen.
3 Likes
I’ve been noticing a new issue with virtual contact sensors (with embedded switches). Note, this is not for Alexa integrations.
Sometimes the contact sensor will open or close but the switch component will not turn on or off in sync. This is particularly puzzling because my routines generally only interact with the switch component. This has caused a few routine failures. Haven’t been able to pin down what has been causing it.
As an Example:
Routine 1: If ContactSwitch A is On then Turn on ContactSwitch B
Result: ContactSwitch B: Contact Open, Switch Off
Any suggestions?
@TAustin I made it happen again and I don’t think the setting itself is changing, at least not from what I can see in the Smartthings app.
I had 2 routines that could on occasion run at the same time. Both were set to “turn on” the momentary. It seems that this can be what switches the revert behaviour until you manually poke the momentary trigger in the app.
Hope this helps clarify.
Also want to echo the sentiment of @Johnnybegoode. Thanks for maintaining this. It’s the glue that makes this stuff work for me.
If you can reproduce the problem, it would be helpful to see the driver activity logs. Do you have the SmartThings CLI?
I have noticed in the passed week that occasionally device state changes are being ignored by SmartThings. If these lost state changes happen, they can cause these kind of nasty problems.
When you look at history, are you seeing the changes you would expect for both the momentary button and switch? If one is changing but the other isn’t, it sounds like a lost state change.
Some driver logs that show it happening in real time would be useful so we can report this to SmartThings.
Hi @TAustin,
I am using your vEdge Creator driver for some automations I have over my home and I find that is not working 100% of the time. This is not a big deal in the cases where is a button that I am pressing which is triggering the automation. In those cases I notice it, then I press the button again and then it works.
But some other automations are based on temperature of the room and it would trigger a fan which is managed through RF bridge which doesn’t have integration with ST, so the solution I am using is Alexa in the middle with your driver. In this case the automation is triggered, the switch and the contact sensor from your driver are activated/opened in ST, but nothing happens in Alexa, so it doesnt trigger the fan. This is not always happening but when does, it is quite inconvenient.
Have you noticed this issue happening? is this a known issue with a possible solution?
Many thanks!
A post was merged into an existing topic: Routines being automatically disabled?
You may not have seen the earlier discussion regarding Alexa triggering, so the first thing I’d ask is did you create the SEPARATE contact device for your Alexa switch? You have to go into device Settings to enable it. The built-in contact is no longer reliable as an Alexa trigger; it needs to be a separate contact device.
I’d like to remove the embedded contact from the Alexa switch device to eliminate uncertainty, but there are folks who rely on it for other purposes.
1 Like
This is a SmartThings platform issue you should take up on another community topic.
Yes, sorry if I wasn’t clear. In the settings of the virtual switch I have selected Separate Contact and the automation in Alexa is being triggered by the contact sensor.
Yesterday I noticed that the switch was Active, while the contact sensor was closed. Could it be the cause? That they get unsync for whatever reason?