I have recently seen cases where some of my ST virtual switches are not getting updated after execution of the related Sharptools rule that sends an on (or off) command to the device.
The Sharptools log shows the command being sent, but the device in ST land never changes state, nor is there any history of the command there. The error also seems intermittent - it usually works as expected but not always.
(I tried creating a new virtual ST switch and corresponding rule, but the problem remains).
Can you share more details about the virtual switch? Is it using a particular driver? If so, have you checked the driver logs?
The rule showing that the command was sent successfully means that they command was handed off to SmartThings without any problem and it sounds like an internal SmartThings or driver issue.
I’ve seen it on two different (virtual) switches. One uses the ST stock virtual switch edge driver, another was uses a community sourced driver. I suspected the problem is on the ST side. In part posted here to see if this was a rare thing or others have seen it in the past.
I’ve not seen anything quite like this, but I have seen similar at least one similar case where the SmartThings API was accepting the command for a device, but the command wasn’t taking effect. I don’t recall the exact details and I couldn’t find it with a quick search through my notes either.