Setting KPL button status when defining a scene

[riojp02]

This is all new to me, I am learning a lot in these forum, but I am still uncertain about 'mutually exclusive' button on a KPL and how to define the status on the KPL 'a/b/c/d' buttons.

 

My understanding is that the 'mutually exclusive' function is best performed in the following way:

 

In 'scene A', where PKL.A/B/C/D are a controllers, If KPL.A is press, set controllers/responders KPL.B/C/D to OFF. and set other responders as desired. This works very well. Pressing KPL.A, PKL.B, KPL.C or KPL.D, will turn any other buttons OFF.

 

However, when I set 'scene A' to ON, using an ISY program, KPL.A/B/C/D are all turned ON.

 

It would be very nice if KPL.A/B/C/D status (ON/Off) could be defined at the 'scene' level. ie: When 'scene A' is turned on using other methods than the KPL buttons (timer, Program,...), set 'KPL.XX' to ON and other KPL.YY to OFF.

 

It is also my understanding, from reading these forums, that setting KPL.0 LOAD in a scene, from KPL.A, is not working in 2.7.8. Is this correct ?

 

An other improvement, would be to adjust the screen split when looking at a scene (or scene.controller). Currently, the 'Apply changes to all devices' AND/OR the 'Copy Scene Attribute From 'scene A' is in the center of the screen. If you have more than 6 'controller/responder' (on my screen), you have to scroll up and down, and scrolling with the wheel is very slow. It would be nice if this windows split could be adjusted to show more 'controller/responders'.

 

Jean-Pierre.

[Michel Kohanim]

Hi Jean-Pierre,

 

Thanks so very much for the feedback.

 

Yes, unfortunately you cannot have a mutex relationship between the load and the sub buttons.

 

You are absolutely correct about controlling the scene and the impact on Mutex buttons. Unfortunately, this is the case for any controller controlling those buttons (not just ISY/PLM).

 

Mutex relationships are local to the device and thus any group commands sent to that device which contradict the local settings are going to impact the state of those LEDs. As much as I hate to say this, I think this is a flaw with INSTEON KPLs: they should ignore commands that contradict the local mutex/follow settings.

 

Now, obviously, there are two very ugly workarounds neither one of which I really like:

1. To have scenes that cannot be controlled via ISY (this does not fix the issue if another controller controls these buttons)

2. To have multiple scenes one for each mutex button ... this makes more sense because, at the end of the day, they are different scenes. This said, however, this is basically a very bad use of PLM resources

 

As far as the split pane, I do agree ... when you have too many devices in the scene the scrolling becomes a little cumbersome. I'll see what we can do but I cannot promise anything immediate.

 

With kind regards,

Michel