API command to force disconnect

I feel like this would be a common support question, but I couldn't find anything that matched what I was trying to say.  Perhaps I just wasn't using the correct wording.

I understand that USB is designed as a single-connection protocol.  I understand that VirtualHere allows users to connect to and disconnect from any desired device in the API.

I am writing code that will run in automation.  There is a single device that will occasionally be needed during automated builds.  Reasonably frequently, a build may fail due to a project code issue, which will cause the built system to exit.  I'm concerned that automation code that uses the API USE command may not always have opportunity to issue a STOP USING command if the build should fail or be killed in an unaffected way.  If I understand correctly, this would prevent any other code from using the API from connecting to the device until someone manually disconnected it on the machine that connected to it.

It would be helpful if VirtualHere's client USB drivers could automatically connect on use and automatically disconnect after a timeout, but I suspect this is technically impossible.

Instead, it would be acceptable if there were a command that could be sent from a machine that would force-disconnect the device from any other user; as a machine started its build, it could first ensure the device were available, even if another build had left it connected.  (Of course this would break if two builds at once needed the same device; but this is not a problem VirtualHere can solve.)  I know the GUI can  Disconnect from user if the client is started with the -a switch.  But I can't find an API command to do the equivalent.

Does such a command exist in the API?  If not, could one be added?

#2

Its already there

"STOP USING"

that will disconnect you OR another user who is using the device

#3

I tested STOP USING, but it only worked when on the same machine as the other user.

If machine X has connected to the device, and machine Y attempts to STOP USING, my exercises showed it didn't work... I'll try again tomorrow to be sure.

#4

It definitely does work, its equivalent to the -a argument via the GUI