Problem Toggling Virtual On/Off Device using Action Groups

The goal is to have my Z-Wave remote toggle a particular device ON and OFF with the press of button 1 (toggle function).

This is how I set it up, but I am having some issues:

I created 2 action groups. One Action Group runs a Python script to turn the device ON, the other action group turns it OFF. These separate scripts work in isolation.

I then created a Virtual On/Off Device, specifying the appropriate Action Group for On Group and Off Group. I did not check Supports Toggling for now.

I then created a trigger that looks for a Z-Wave command of button 1 pressed, and an action that says Toggle On/Off (Light/Appliance Control) for the Virtual On/Off Device above.

So the problem is that the On/Off python script command never makes it to the device.

If I turn on Supports Toggling in the Virtual Device, and select the On Action Group, the device will turn on, but never off.

I read the documentation, but clearly still don't understand how Virtual Devices are supposed to work, or maybe what I am doing is overcomplicating things.

FYI - the devices in question are TP-Link, and I am going back to Python scripts for everything because I have been having issues with the TP-Link plugin. The Python scripts are solid for what I want to do.

You can't use the Toggle on/off device command if the device doesn't support toggling. Which your Virtual Device does not. So you need to combine the scripts into one script that can actually toggle the device. If you can't query the device in the script to see the current state then you should use an Indigo variable to keep track of the state.

Actually, you can keep the scripts you have, and just write a simple script that checks an Indigo variable, turns the device on or off, then updates the variable.

Or you could do it just in the trigger with no additonal scripts at all.

Put a condition on the trigger to check an indigo variable. If off, then run the on script. Then a second action to change the variable to on.

Then duplicate the trigger with the reversed logic. If on, run the off script. And update the variable to off.

Yes, you now have two triggers, One to turn it on, one to turn it off.

Or you could do it just in the trigger with no additonal scripts at all.

Put a condition on the trigger to check an indigo variable. If off, then run the on script. Then a second action to change the variable to on.

Then duplicate the trigger with the reversed logic. If on, run the off script. And update the variable to off.

Yes, you now have two triggers, One to turn it on, one to turn it off.

This is what I did, and works great, thank you.