If I add a Virtual Motion Device what does the auto inactive ASAP do?
Virtual means it's not a "real" device and that something else is going to set Active motion or Inactive motion. This is often used to accumulate multiple motion sensors into one. You'd create Rules to detect when any of a group of Motion sensors went active and then another Rule that wouldn't set Inactive on the virtual until they all went inactive, for example.
But some don't want that second Rule... they have Any Motion turn the Virtual Active and then set the virtual to turn itself inactive automatically N seconds later.
Apparently ASAP is 3ms
dev:5 2022-08-22 06:46:22.829 am info pseudoMotion is inactive
dev:5 2022-08-22 06:46:22.826 am info pseudoMotion is active
dev:5 2022-08-22 06:46:02.673 am info pseudoMotion is inactive
dev:5 2022-08-22 06:46:02.670 am info pseudoMotion is active
dev:5 2022-08-22 06:45:59.273 am warn description logging is: true
dev:5 2022-08-22 06:45:59.271 am warn debug logging is: true
dev:5 2022-08-22 06:45:59.268 am info updated...
Thank you for the reply and apologies if I don't use the correct terminology. I hope I grasp the basic idea. My virtual motion sensor is triggered by my BlueIris camera system. However, I believe the cameras only post active and thus the sensor will not reset to inactive and so I have to use the Auto Inactive. The time delays seem straight forward but there is also ASAP in the drop down list. What specifically does that option do / mean? If I set Auto Inactive to ASAP what happens, when does the switch change to inactive, based on what criteria?
Sorry typed up my reply and did not see the rest of your reply.
Yes, I was editing my reply as my test results came in. Narrowing my answer, making more and more correct.
I see, thought I was shockingly lazy and/or blind 
