What driver are you using? If it's the built-in driver, I'm not sure what might be going on with the built-in driver, but I don't see anything off hand that looks like it should cause this. But that would probably be clearer by looking at logs and using an actual device, which I do not have hooked up right now... (could try later)
If it's this one, typically authors make a post/topic here for apps or drivers, and that is often a good place to get help (but creating a new topic and linking to the existing one also works--and either by default will let the poster know something happened):
But if so, that one is mine. 
I also don't see anything that looks like it should cause this here either unless maybe the device doesn't report the configuration changes (which is how the status LEDs work) back as expected. But again, I might need to test that with an actual device.
When troubleshooting a rule, especially something like a custom command where the exact command and parameters are clear, it may be helpful to try the command directly from the device detail page in order to eliminate possible issues that stem from the rule itself (or generally speaking, whatever app you're using) and not the device or driver. So, I'd also suggest trying that here to see if you find reproducible behavior.
