1 pointI don't know if this helps or not - here is what I found after some testing - if I set it to: sleep://1000 It works - I get a one second pause and then the next command executes. I did a radical color change so I could see what was going on. Anything above that (e.g. sleep://10000) and I still get a 1 second pause. It's almost like the coding for the "test" mode is stuck - that it's converting whatever one puts into the command to 1000 ms.