Bummer.
The only thing I can think of is that UI6 is the problem. Even if I enter the wrong IP address for my Vera the delay is only about 15 seconds so that 6 minute delay is very unexpected.
Normally, even if the Vera does not immediately switch the light on or off (it might take a few seconds) VC continues on its merry way immediately without waiting for more than a fraction of a second.
Is there anything weird about your network setup? Is your VC machine on the same subnet as the Vera? (are the first 3 numbers in the IP address the same?). Do you have anything else worthy of note, like a VPN etc?
VC basically sends a simple HTTP request similar to what your browser sends and it doesn't really look at the response although it does wait for a confirmation that the message was received before continuing.
In terms of status reports that come back and generate events (if that option in enabled) that is handled in a completely separate process and should not really have anything to do with sending commands to the Vera unit.
Of course, if you request information in an action like
Vera.Get.Status then it will wait for a response from Vera until it times out but it should not take more than a minute before it gives up.
All I know about UI6 is that noone wants it, and I'm not going to install it. From what I've seen it will never get out of alpha either because they are working on UI7 but I'm not really holding my breath on that one either. UI5 might be ugly but it works and I don't really use the built-in UI anyway. I use only VC and AutHomation for Android to interact with my Vera.
I'm sorry we can't offer more in terms of practical solutions for you at this point. We have spent about an hour trying to recreate what is happening to you and we cannot figure it out.