I've implemented a driver that allows me to control X10 devices. It uses a raw socket interface.
It takes between one and two seconds after an X10 command is sent before another one can be sent. So, if I create a scene that includes these devices, I need delays between each on/off command.
I tried adding a sleep command in my driver in the on and off commands, but HE does not seem to allow sleeps in device driver code.
Does that mean I can't use scenes with them and should use Rules instead?
From experimentation in my old code one second is 95% reliable for me, two seconds is solid. So, I've been using 2 seconds.
I wouldn't have thought that much is needed, but I haven't actually analyzed how long a message send takes over power line carrier. I think only one bit (not byte) per 60 hz cycle, so that's pretty slow. But seconds? I haven't done that math.
But, I'm not sure why you'd want a limit, other than protect the user from himself.