@scott.taylor you can check the shortcut history found under your account settings of the Wyze app to see what IFTTT automations have run. You won’t see a reference to IFTTT but you will see actions that were a result of an IFTTT applet.
Virtual switches are the easiest way to do things like turn on motion detection or sound detection. Because IFTTT is so limited when it comes to what you can do per applet you would need an applet per action. Applet to turn on motion, another to turn off motion and the same for turning on and off sound detection.
On the STs side you would need virtual switches for each of these actions and some scripting to turn on and off those virtual switches so that they will match the status IFTTT has called for.
If you click the switch in ST to turn on motion detection, when you click the switch to turn it off, you would need to automate the process of switching the On virtual switch back to off. This is all pretty easy using Webcore and Smartthings.
Hopefully in the future Wyze will allow access to shortcuts either through direct API access to players like Smartthings, Hubitat and IFTTT. This would make things much easier.
I gave up on Smartthings 6 months ago and moved to Hubitat. That platform offers a connection with IFTTT that helps a bit with what you are trying to do. Instead of having individual virtual switches for each off on choice you can have a single switch for both off and on.
Using the Webhooks service in IFTTT you can relay instructions to Wyze for your cameras. A virtual switch turns on Motion detection in IFTTT. Then when that switch is turned off in STs a command is sent to Wyze using Webhooks to turn motion off. This method reduces the need for both on and off virtual switches and keeps your virtual switch in sync with the wyzecam detection status.
You can do this same thing in Smartthings using Webcore which does the webhooks connection between Smartthings and Wyze.