This feature request is 2-fold and I'm not exact sure on the best way to configure each:
1) Set priority on the order by which triggers are executed. For example, a certain situation cause multiple triggers. Sometimes, you want to certain triggers to execute first. Correct me if I am wrong here: but the "state" of the devices is captured at condition confirmation time and provided to all matching triggers? Or will the results (the changes it makes to the system) of the first trigger be provided as input to the second executed trigger?
2) Set priority on execution to the modem (e.g. Instead PowerLinc Modem). Many times, when multiple triggers and schedules invoke at the or near the same time; there is queue for processing. I would like to assign higher priority to the "turns lights on when I enter the room" and lower priority to "turn lights off when no motion in the room". So often; a timeout failure (no-acknowledgement) causes a lag of 10-15 seconds. This translates into lights turning on and off in rapid succession, once the timeout is cleared. Furthermore, some triggers/schedules are "activity intense"; hitting many devices (such as disabling the security system -- which in part will turn off all the random lighting that was on). When a failure occurs; all of the device changes queue and wait for an unreasonable amount of time.
What is considered a "large" deployment? I have > 200 insteon devices on the power network. What are some recommendations for reducing timeout-failures? All I can do is relink periodically; but quite honestly, relinking 50 motion sensors is a pain.