It is not the job of Dispatcher or Routes or wifi throttle etc to throttle turnouts changes, or any other commands.
?
Sure, but then why Routes include the option to delay consecutive turnout commands, but Dispatcher does not? Inconsistency... Neither should have it, if what your wrote was strictly followed.
?
If your connection does not already have a method available to do that then ask that the connection provides the capability.
?
My connection is DCC++/DCC-EX. There doesn't seem to be an option available in DCC-EX to throttle turnout commands. I could probably try to modify the DCC-EX Arduino IDE code itself, but I'd rather not go that route, as it would be a nightmare to keep the DCC-EX up to date later... And EX-RAIL language available for automation seems to be too limited to do it...
?
I'll look into LogixNG...
?