Once in a great while I get a send failed from a device that is activated from a motion sensor (via Insteon). I was wondering, how many times is a command resent before it triggers this log error state?
Since it does not happen very often I'm thinking of inserting another command delayed buy a few seconds. I hate to do this for all of the commands but I guess as long as it does not bog down the system then I figure there is nothing lost.

Dave

Hi Dave,

Different PowerLincs have different numbers of retries, but they all try multiple times and increase the hop count several times for more mesh coverage (repeating from other modules). Trigger Actions that send INSTEON commands after receiving motion sensor commands do occasionally cause problems because of collisions between the motion sensor sending cleanup commands and Indigo trying to send commands via the PowerLinc. In theory, the collisions are supposed to be handled by the PowerLinc, but it doesn't seem to always work.

A few tips: 1) do not directly link the motion sensor to any module if you are having Indigo send a command, 2) you can try adding a slight delay in the action panel (.02 minutes), 3) try moving your AccessPoint RFs around to different outlets to change up the signal paths.

Thanks for the info and tips.