I have a simple program which sends a X10 command when a Keypadlinc button is turned ON:

 

If

Status 'KPL A' is On

Then

Send X10 'A1/On (3)'

Else

- No Actions -

 

When executed and the Keypadlinc button is turned on, the X10 device that is supposed to respond to the program does not respond.

 

I tried running the Then path of the program manually. This worked just fine.

 

Next, I tried adding delays in the program:

 

If

Status 'KPL A' is On

Then

Wait 2 seconds

Send X10 'A1/On (3)'

Else

- No Actions -

 

This worked, but the delay makes the program unusable in its context.

 

Sending multiple commands seemed to be the only workaround so far:

 

 

If

Status 'KPL A' is On

Then

Send X10 'A1/On (3)'

Send X10 'A1/On (3)'

Else

- No Actions -

 

 

Question: Is there a better way to implement this and eliminate the delay or duplicate command?

 

Presumably, this is an artifact of some power line signal collision that is occurring. The event log trace shows the X10 command clearly being transmitted.

It is due to the KeypadLinc sending additional messages beyond that which triggers the Program. Insteon devices handle that, X10 do not. Sending multiple commands is the same as adding a delay. I know of no other way than delaying the X10 traffic until the Insteon traffic is finished.

Would assigning X10 commands to the individual Keypadlinc buttons directly solve the problem?

If the device is Insteon there is no need to use X10 commands. To the question I think it would.