Keypad Link Programing

[arf1410]

Can my ISY be used to program my 6 button ISY Keypad link - ie basic re-assignment of the A/B/C/D buttons to different tasks?  The keypad link is part of my ISY setup, and I can activate buttons via the ISY, but can't figure out how to change things?

[larryllix]

Sure.

Write a program for each button and put whatever you want in each program.

Configure your KPL to non-toggle On mode.

If
     control  KPL.Button.A is Switched On
Then
    do whatever
Else
   -----

KPL LEDs can have levels changed with programs in the admin console (all for one setting) but LED On/Off can only be done with scenes. Of course, then use programs to activate the scenes.

[arf1410]

Currently, the Keypad is directly configured ... even if my ISY is disconnected, the keypad, say, button A will turn on and off the garage light.  Can the ISY be used to directly reprogram the keypad ... to change button A from controlling the garage light ... to controlling the hall light, such that the keypad will function if the ISY is turned off ...

[larryllix]

1 hour ago, arf1410 said:

Currently, the Keypad is directly configured ... even if my ISY is disconnected, the keypad, say, button A will turn on and off the garage light.  Can the ISY be used to directly reprogram the keypad ... to change button A from controlling the garage light ... to controlling the hall light, such that the keypad will function if the ISY is turned off ...

If I understand you correctly, you want to modify the scene used with each key?  I don't think this is possible but you can dump the scene links and use programs to make the KPL key operate anything you want and change it with programming.

The extra program usage time taken is not usually a problem for manually operated devices, but Motion Sensor to Lamp systems should not have the extra In/out of ISY delay. It is annoying.
This extra time delay is not due to ISY CPU speed. It is due to the Insteon protocol taking time and waiting for all the Hops to finish, needed or not.

[larryllix]

@arf1410 You can add an extra logic line in your programs like this offering two (or more) paths for any event trigger.

If
     control  KPL.Button.A is Switched On
  AND
   it's nighttime
Then
    do whatever
Else
   -----

 

If
     control  KPL.Button.A is Switched On
  AND
    it's NOT nightTime
Then
    do whatever
Else
   -----

[arf1410]

Say button A is already programmed to directly turn on the garage light,  not going thru the ISY. The instructions above will add extra tasks, they won't stop the keypad from turning in the garage light.

[larryllix]

1 hour ago, arf1410 said:

Say button A is already programmed to directly turn on the garage light,  not going thru the ISY. The instructions above will add extra tasks, they won't stop the keypad from turning in the garage light.

Nope they won't but I don't use many scenes created directly between devices.  I prefer the control I get when ISY handles them.
Exceptions are between MSes and the Lamps they control (for speed of response), every unit in my home for security flashing, and a few Gathering room scenes (reading, TV watching, Movie Watching, Bright, Full On all affecting the same group of bulbs)

I think If you want to break the path between the LED and the garage light you have to dump the scene connection and use programs. You just create scenes for each LED and monitor/slave programs to operate the scenes like this.

If
   status garage Light is On
Then
   Wait 2 seconds   <--- avoids signal clashes in the same box
    set scene.LED.A On
Else
   Wait 2 seconds
   set scene.LED.A Off

Now whatever or whoever turns the light on or off,  the LED will follow.

[lilyoyo1]

The A button is always connected to the load itself. You cannot change that. It will always trigger the light regardless of how programmed.

[arf1410]

32 minutes ago, lilyoyo1 said:

The A button is always connected to the load itself. You cannot change that. It will always trigger the light regardless of how programmed.

That might be true for the 8 button keypadlinc, but my 6-button has a large top and bottom button connected to the load, but buttons A/B/C/D are programmable and not load connected.

 

[larryllix]

2 hours ago, arf1410 said:

That might be true for the 8 button keypadlinc, but my 6-button has a large top and bottom button connected to the load, but buttons A/B/C/D are programmable and not load connected.

 

I think there is some confusion in key terminology  here.
If you remove the front cover from a 6 key KPL there are the same 8 switches underneath. Conversion (change of key count)  kits are available.

[lilyoyo1]

4 hours ago, arf1410 said:

That might be true for the 8 button keypadlinc, but my 6-button has a large top and bottom button connected to the load, but buttons A/B/C/D are programmable and not load connected.

 

I misunderstood what you were asking. I was thinking it was an 8 button connected to the load. The A button can be assigned to whatever you want it to be. If you no longer want it controlling the garage load simply unlink it from the device that it's link to which control that load.

[kclenden]

Simple answer - Yes, you can use the ISY to program keypad buttons so that they control things even if the ISY is powered down.

First you create a scene in the ISY.  Next you drag the devices you want to be controlled to that scene and add them as "responders".  Finally you drag the devices you want to control the responders to the scene and add them as "Controllers".  The ISY writes the necessary "links" to each device's memory so that even when the ISY is powered off, the responders will react when the controllers command them.

After you've added the responders and controllers to the scene, you can go back and edit what happens when the scene is activated.  So if you have some responders that are dimmers, you can configure them to come up at 50% instead of 100%.  This information is also written to the devices so that even without the ISY present, they will react accordingly.