KPL's and Triggers

[GPG]

I started this thread, because triggers seem to be the solution to keeping the KPL LEDs in sync. It always annoyed me that the PLC would not update the KPL LEDs for timed events.

 

My ISY is v2.1. I set up an 8 button KPL and Lamplinc to test. The two lower buttons I set up as scenes KPLg and KPLh. They have no links to any other device and it seems you have to have them in a scene for them to show up in the Trigger Response drop down list. I created two triggers: (1) If the LL is >OFF turn button KPLh on and KPLg off, (2) If the LL is OFF, turn off KPLh and turn on KPLg. I then set up two scheduled events: the first to turn the LL on and the second to turn the LL off. Sure enough, the KPL buttons correctly indicated the state of the LL.

 

I'll be working on a more practical and complex setup later today and will report my results, but here are some of my initial observations:

 

1-The trigger interface is fairly easy to figure out. I spent around an hour getting the first test to work the way I wanted it to, at which point I had a pretty good idea how to setup, edit and delete triggers.

 

2- Local control of the LL, does not update the KPL buttons. However, performing a query on the LL does update the LEDs. I tried to set up a schedule to perform a query on the LL every 5 minuts, but so far I haven't gotten it to work (there should probably be a separate thead for shcedule problems).

 

3-The trigger conditions are ON, Off On/Off, but no 'changed since last query'. If I'm correct here, it then would take 2 triggers to control one KPL button on/off status. As someone else already suggested, the current limit of 20 triggers probably needs some upward adjustment.

[Michel Kohanim]

I started this thread, because triggers seem to be the solution to keeping the KPL LEDs in sync. It always annoyed me that the PLC would not update the KPL LEDs for timed events.

 

My ISY is v2.1. I set up an 8 button KPL and Lamplinc to test. The two lower buttons I set up as scenes KPLg and KPLh. They have no links to any other device and it seems you have to have them in a scene for them to show up in the Trigger Response drop down list. I created two triggers: (1) If the LL is >OFF turn button KPLh on and KPLg off, (2) If the LL is OFF, turn off KPLh and turn on KPLg. I then set up two scheduled events: the first to turn the LL on and the second to turn the LL off. Sure enough, the KPL buttons correctly indicated the state of the LL.

 

Bravo!! You've surely done a better job of explaining how scenes triggers should be applied than any of us here at UDI. Thanks so very much.

 

 

I'll be working on a more practical and complex setup later today and will report my results, but here are some of my initial observations:

 

1-The trigger interface is fairly easy to figure out. I spent around an hour getting the first test to work the way I wanted it to, at which point I had a pretty good idea how to setup, edit and delete triggers.

 

2- Local control of the LL, does not update the KPL buttons. However, performing a query on the LL does update the LEDs. I tried to set up a schedule to perform a query on the LL every 5 minuts, but so far I haven't gotten it to work (there should probably be a separate thead for shcedule problems).

You are right; we haven't been able to sense LampLinc load situations due to a variety of reasons and mostly due to LLs not being capable of acting as controllers. We are trying to come up with a workaround.

 

3-The trigger conditions are ON, Off On/Off, but no 'changed since last query'. If I'm correct here, it then would take 2 triggers to control one KPL button on/off status.

You are 100% correct. Your suggestion is already added as it does makes much more sense to have triggers that follow the state of the controlling devices.

 

 

As someone else already suggested, the current limit of 20 triggers probably needs some upward adjustment.

Already working on it ... lookout for version 2.3.

 

Thanks so very much for your suggestions,

Regards,

[GPG]

I ran into the same problem regarding one KPL button not being able to control another one, which is described in detiail in the "Is it better to use a scene or a trigger for all on/off? " thread.

 

Another suggestion for triggers would be to provide for an ELSE response, maybe via another window. The point being to allow for a trigger like:

If CONDITION then RESPONSES else RESPONSES. This would also eliminate having to use two triggers.

[Michel Kohanim]

I ran into the same problem regarding one KPL button not being able to control another one, which is described in detiail in the "Is it better to use a scene or a trigger for all on/off? " thread.

 

Another suggestion for triggers would be to provide for an ELSE response, maybe via another window. The point being to allow for a trigger like:

If CONDITION then RESPONSES else RESPONSES. This would also eliminate having to use two triggers.

 

Or, we might even have a better solution. Thanks for your suggestions and we appreciate your patience. Please continue sending us your suggestions.

 

With regards,