KeyPadLinc LED Status

[vcholman]

Didn't intent to confuse you. You are correct I originally had one scene. Another member suggested I put the sensor in a seperate scene, it too worked fine.

Then I read your post and saw your one scene. So I changed my scenes back to one to match yours. It worked, but the LED status buttons were not in sync witht the doors. They were lit when the doors were closed.

As a quick correction, I enabled Trigger Reverse. No the LEDS in my keypads light up when the doors are open.

 

My sensor / Option / Toggle is set to Non-Toggle ON

 

Does this sound correct?

[stusviews]

Trigger reverse will cause difficulties in the long run. The nightly query will eventually reverse the trigger reverse. The solution is to use a different magnetic contact switch. This is the most recommended magnetic contact switch.

[vcholman]

Hi,

 

Have been unable to figure out how to get the LED inside my KeyPadLinc to turn on when being controlled by a program. This would be useful when viewing a keypad to know if a light is turned on. Can this be done, and if so; how would I accomplish this? 

 

BTW: All my buttons in my KeyPadLinc are part of a Scene, and all functions work fine.

 

 

 

Thanks,

[oberkc]

Yes, one can use a program to change the status of a keypad button. The button must be part of a scene. The program turns the scene on/off.

[kzboray]

This is an example of how you can control the indicator lights via scenes.

If      Control KeypadLinc - Button B is ON
     Or Status KeypadLinc - Button B Status is ON

Then
          Set Fan Medium Scene ON 75% - This is setting the correct indicator light to on
          Set FanLinc Motor Medium - Sets the actual speed on the fan
Else

You have to have a scene for each button and the desired on/off status that you want for all buttons when that scene is active/ON.

[vcholman]

kzboray,

 

Under STATUS, there is no "ON" option. There is "OFF" and "RESPONDING".

Do you  think RESPONDING will work in place of ON?

[vcholman]

kzboray,

 

 

Your example was for a ceiling fan, I'm controlling exterior lights using a IO Linc module. My KeyPadLinc I'm using button B.

Here is a copy of my program for the button. The other pic insert is my Scene for the Button.

 

 

 

Do you have any other suggestion or corrections?

 

Thanks,

 

[stusviews]

The scene shows the I/O Linc as a responder not a controller. In any case, to control a button LED, create a scene that includes the button as a responder and use programs to turn the button LED on and/or off.

 

DR Dine Out Button
If
        Status  'CR / Devices / CR FanLinc-Light 50' is not Off
     Or Status  'KT / Devices / KT Ceiling 50' is not Off
     Or Status  'LR / Devices / LR Ceiling Light KPL 20' is not Off
 
Then
        Set Scene 'DR / Scenes / DR Front Off Button' On
 
Else
        Set Scene 'DR / Scenes / DR Front Off Button' Off
 

 

[vcholman]

^{Getting close, I was able to get the LED inside the KPL button to turn on under program control. However when the program ended, the IO Linc turned off, but the KPL status LED started to flash.}

^{I'm guessing there is a conflict.}

 

^{I changed my KPL button to a Controller}

^{Created a simple scene with the KPL button as a responder}

 

^{Created program to control the KPL scene listed above.}

 

^{Here are my settings}

 

 

 

 

 

[vcholman]

BTW: All my KPL buttons are set to TOGGLE if this makes a difference.

[vcholman]

I need to make a correction.

 

Under program control, the LED inside the KPL button turns on.

 

When the program ends, the LED inside the KPL stays on but the lights turn off as expected.

 

When I manually press the lit KPL button, this is when it starts to flash.

[oberkc]

Let me seek some clarification...You are using an IOLinc to control some ceiling lights?  Are you using the relay, somehow, to activate these lights? 

 

If your IOLinc is defined as a controller in your scene, it would be the sensor.  How is this wired?

 

Flashing LED could indicate a communication problem with something.  It could also mean non-toggle mode.  Do any of those sound more likely than the other?

 

I must admit to having a little difficulty trying to get my head around what you are trying to accomplish here.  Perhaps it is time to back away a bit, clear all the scenes and programs related to the two devices, and start fresh by describing what you want to achieve.  I thought this started off as a garage thing, now a light thing. 

[vcholman]

You are correct, this is no longer a garage thing. I mostly understand how to configure my switches and scenes for them to operate correctly when manually pressing the buttons.

 

Since then, I have been experimenting with programs. Recently I noticed the status LED behind my KeyPadLinc buttons were not lightning up when that function was being controlled to turn by a program.

 

To clarify what I am trying to accomplish is to have the status LED light up behind each of the 8 buttons when they are being instructed to turn on by a program.  

 

Outside my home, I have coach lights that are hard-wired to Insteon's Micro On/Off modules. These modules are setup in scenes to be turned on or off when I press a KPL button. All this works fine when I manually press the KPL button. Also if I turn on the Micro on/off module using the MobiLinc app on my phone or by turning on the module inside the ISY admin console, the coach lights turn on as well as the status LED behind the KPL button.

 

Now I have moved on by controlling several lights inside my home under program control. I would like to be able to glance at my KeyPadLincs and see what buttons are active.

 

This is where I need some assistance to help understand if I need to setup a separate scene to update the LED status for all my KPL.

 

As of now, I have deleted all my LED status scenes. Can you describe and show me an example how to get the KPL status LED to light up when being turned on by a program.

 

Attached is the scenes I have created for the KPL labeled "Foyer" I'm working with. Button "B" is labeled "IO Linc: Entry Lamps".

 

 

 

 

 

[oberkc]

Ok. So the IOLinc is no longer a relevant device here.

 

So..the device called "IO Linc: Entry Lamps" is a keypad button and the device called "Foyer-B:Entry Lamps" is a micro module? I sure would never have guessed that by the naming convention.

 

Why do you have the IO Linc device for the foyerB scene a controller, but a responder in the other scenes?

 

When you create a program to turn on the scene "foyer:B-Entry Lamps" does the keypad button not light up? In your program(s) that controls "several lights inside" your home, are you turning on the micro modules or turning on the scenes?

[vcholman]

Hi Oberkc,

 

The naming convention is correct.

 

Device "IO Linc: Entry Lamps" is the Micro module that the lamps are directly wired to. I will rename this device to "Micro: Entry Lamps".

 

The keypad is "Foyer-B: Entry Lamps". Foyer-B is the KPL's room location, B is the button, Entry Lamps identifies what is being controlled.

 

I have corrected all my other Micro devices to be controllers.

 

Last night I was successful in getting the keypad's status led for my Entry Lamps to turn on and off when the micro module was turning on and off.

 

This is how I accomplished this...

 

Now that I have the status led for one KPL button working, I will create the programs for the other buttons.

 

This all takes time to understand, but I'm getting there.

 

 

 

 

 

 

[vcholman]

To answer your last question: I'm turning on the scene.

 

Is this correct?

[oberkc]

If you are turning on the scene with the program, it should not be necessary to create separate programs to turn on the keypad buttons. Since the keypad buttons are part of the scene being turned on by the original programs, the keypad button should already be on.

 

The only thing that comes to mind is that responder levels for the keypad button are set at some low level (or off) or that you have some xommunication issues with your insteon network.

 

But, it does appear that you have correctly figured out how to turn on a keypad button via program.

[vcholman]

^{Interesting if I turn on the device as an action in the program, I can choose ON or OFF.}

 

^{If I turn on the device using a scene, I can only choose LED on levels from 0 to 15 and off levels from 0 to 7.}

 

^{Because of this, I'm turning on the device. This might explain why I'm using programs to turn on the KPL LEDS. Is this what you were referring in your first paragraph?}

 

^{I do have my KeyPads LEDs OFF level set to 1 and the ON level set to 10. This is so they can be seen in the dark.}

 

^{Not sure if I understand what you mean by the responder levels being set to some low level. Would my ON level of 10 and OFF level of 1 explain this question?}

 

^{I agree, it should not be necessary to create separate programs for each key to have the LED be in the correct on/off state when being controlled by a program.}

^{If you think there is a better way to accomplish this?}

[oberkc]

Cant go into details right now, but it sounds as if you are not using the correct program statement to turn on the original scene. Will respond more fully at a later time.

[oberkc]

If I turn on the device using a scene, I can only choose LED on levels from 0 to 15 and off levels from 0 to 7.

 

This statement leads me to believe that you are not using a command to turn on a scene.  Rather, it appears you are using a command to change the backlight levels of a device.  A command to turn on a scene does, indeed, have ON and OFF options.  One of my programs, for example, looks like this:

 

Evening Interior (at home) - [iD 0004][Parent 0019][Run At Startup]

 

If

        From    Sunset  -  1 hour  and 30 minutes

        To      11:00:00PM (same day)

 

Then

        Set Scene 'Interior (home)' On   <<<< turns a scene ON

        Run Program 'Hue Bedroom Programs' (Then Path)

        Run Program 'Hue Light Office' (Then Path)

 

Else

        Run Program 'Evening Off' (If)

 

Make sure you are choosing an "action">>>"your devices">>>"scene name">>>"ON"

 

Because of this, I'm turning on the device. This might explain why I'm using programs to turn on the KPL LEDS. Is this what you were referring in your first paragraph?

 

Yes

 

Not sure if I understand what you mean by the responder levels being set to some low level. Would my ON level of 10 and OFF level of 1 explain this question?

With insteon, one can have a responder level set to OFF.  This means that when a scene controller sends an ON command, the responder with such a level would turn OFF.  Make sure that your keypad ON level is set to ON, and not OFF.  Otherwise, you could turn on the scene via program and the keypad button would turn off.

 

I agree, it should not be necessary to create separate programs for each key to have the LED be in the correct on/off state when being controlled by a program.

 

it should not.  It is not.

 

If you think there is a better way to accomplish this?

Yes, I do.  Hopefully, my suggestions are becoming more clear.

[vcholman]

Live is getting better

 

You were correct, I was choosing the DEVICE from within my programs and not the SCENE.

 

I disabled all my KPL LED status programs, which used to update the keypad's LEDS.

Still have my Scenes to allow the keypad's LEDs to update.

 

One of my programs, I have it set to turn on 6 of the 8 functions on my Foyer keypadlinc for 30 seconds, then off.

 

Watching the keypad is fun. The 6 buttons light up in sequence, then they turn off when the device or Micro modules are turning off.

 

Sure am happy I didn't need to write all those separate programs.

 

You did an excellent job! I really appreciate your patience and support.

 

 

Thank you,

[vcholman]

Hi Oberkc,

 

Ran into another snafu yesterday.

 

My patio lights were originally wired up for 3-way switches. One switch in the master bedroom and the other in the family room. I replaced them with Insteon's 2477D switchlinc dimmers. One room in my home I installed a 8 button KPL. Two of the secondary buttons are configured to control the patio lights, I guess the secondary buttons are acting as a 4-way switch. The KPL turns on and off the patio lights and both 2477D switches LEDs indicate the on/off status, If I turn on the patio lights from either of the 2 2477D switches, the status LED inside the assigned secondary KPL buttons light up. This is exactly what I want.

 

Now for the snafu question. I want to have another 8 button KPL in another room in the house to be able to turn on/off the same patio lights. The problem is I'm unable to add the two patio lights 2477D switches as controllers to the scene for the additional KPL. I get a message that says these device (2477D's) are already controllers for my first KPL and will only allow me to set them as responders for my second KPL.  

 

Is this a limitation how many devices and be added to a KPL as controllers? I would think each additional KPL in different rooms would act 3-way, 4-way, 5-way... switch.

 

The attachments are how I have my patio flood lights setup with my first (working) KPL.

 

Any suggestions?

 

Vance

 

 

[oberkc]

No practical limits of which I am aware. Certainly there are no prohibitions about scene having four devies. The error message you describe makes me suspect you are trying to create a second scene, rather than adding the new button to the existing scene.

 

Alternatively, is it possible that the ISY believe that the "new" KPL is already part of a scene?

[stusviews]

A device can be a controller for only one scene. You can have as many controllers for the scene as you want, thus enabling an n-way configuration. If you do want an n-way configuration, then there should be one and only one scene for it. It seems that you are trying to create more than one scene to accomplish what you want.

[vcholman]

Stusviews,

 

You were dead on accurate. I was trying to create a separate scene for the same devices. I now have 3 KPL's controlling the patio lights, all using the ONE scene.

Wow...The force is strong with you!

 

Thank you,