Jump to content

Method to Reset/Update Keypad Button LEDs to Correct Status


panzer948

Recommended Posts

Hi,

 

Getting my new system complete with several keypadlincs using the ISY994i for programming etc.  So far everything is running smooth. However, with several keypads installed throughout my house, with many controlling some of the same scenes and lights as other keypadlincs, I have noticed a annoying little problem. After awhile, many of the KeypadLinc buttons have an incorrect status on or off than what the device is actually on.  This could be a dedicated scene button or single light controler, etc.  Is there a program or query you could run every so often to reset these status lights on my keypad lincs?  I was thinking I could at least get them reset once a day while sleeping.  Am I missing something else here?  It just would be nice to know you don't have to hit a button twice just because its in the wrong status condition.

Link to comment

Hi,

 

Getting my new system complete with several keypadlincs using the ISY994i for programming etc.  So far everything is running smooth. However, with several keypads installed throughout my house, with many controlling some of the same scenes and lights as other keypadlincs, I have noticed a annoying little problem. After awhile, many of the KeypadLinc buttons have an incorrect status on or off than what the device is actually on.  This could be a dedicated scene button or single light controler, etc.  Is there a program or query you could run every so often to reset these status lights on my keypad lincs?  I was thinking I could at least get them reset once a day while sleeping.  Am I missing something else here?  It just would be nice to know you don't have to hit a button twice just because its in the wrong status condition.

 

That isn't a solution to your problem.

 

You either have noise on the line or poor coupling / bridging of the Insteon network. This also assumes you did in fact linked them (KPL's) correctly as a Controller in all of the scenes.

Link to comment

Hmm. I'm pretty sure they are all controllers in the scenes (for those buttons that control scenes).  They all seem to work fine though, just the status is sometimes off forcing me to hit a button twice.

 

You can confirm if they are controllers by looking at the tree on the right when you select each device. It will tell you its association etc. If this proves to be correct and they are controllers you need to confirm proper coupling / bridging.

 

Have you done this in your Insteon network outlined in the full users manual?

Link to comment

Okay will check tonight when I get home.

 

If coupling is good and confirmed via the 4 tap method. The remaining culprit is noise on the line whether it be noise makers, signal suckers.

 

NOTE: Best practices state you should always hard reset your devices prior to enrolling them into the ISY. This will ensure the device is at a default state and any testing links and programs are deleted. 

Link to comment

Just a quick note of what I found. First a little background. I am currently using 3 keypadlincs on one level that each have similar assigned buttons to control a mixture of scenes or individual loads (that they are wired into). Note that some scenes may control one light while another may include that light and three others.  So I noticed that when I hit one of my scene buttons; all three of the keypads change the status correctly for that particular scene assigned to their button.  In addition, if a scene includes the main load that each keypadlinc is controlling; that too will update the status correctly.  The only buttons that do not change their status are buttons that are used as controllers of a scene involving individual lights to other responders (i.e., other keypadlinc loads or switchlinc controllers).  For example, each of my keypads has a scene labeled "dinner time"; which essentially turns on all of the lights downstairs.  This includes lights controlled as the main loads for each of the keypads.  All of the status LED lights on the buttons for those are updated correctly.  However, other buttons assigned as smaller scene controllers to control one of the lights of the same scene (i.e. say just kitchen lights) does not indicate a status change when turning on dinner time (unless that keypad linc is the load controller for that light set).  So in a sense I was expecting if a scene cuts on several lights; then a button assigned as a scene to control just one of these individual lights should also show a status change of on.  I hope that makes sense.  See attached file for setup.

post-6109-0-54071400-1421799914_thumb.jpg

Link to comment

I am not sure I understand how you are setting things up, but here are some thoughts based upon how I do it

For the kitchen lights you have a few kpls that are controllers of the kitchen lights scene. The kitchen lights are also responders of the dinner time scene. You also need to include the hall keypad kitchen and the two other Kpl buttons that control the kitchen lights scene as responders to the dinner time scene.

The next part is much debated and has to do with your own preferences and what it means to have a scene on. For our dining scene which has numerous members including the kitchen lights switchlinc and 3 Kpl buttons that are controllers of the kitchen lights. I set the two Kpl buttons that control the dining scene to non toggle on. So anytime the button is pressed the scene is activated, the two dining Kpl buttons are on. If I turn off the kitchen lights, I say that the dining scene is no longer "on" so I want the two dining kpls to turn off. For this I use monitoring programs. I frequently reference this linc for a full explanation:

http://www.adamsj.com/isy/basementA.htm

 

I create a scene called dining kpls with both dining kpls as responders. Monitoring program is something like this:

If status kitchen lights is not on

Or status island lights is not on

Then set scene dining kpls off.

(I would have to check my actual program to see if I have the condition include and dining Kpl is on).

 

Now the flip side is what if I turn on the dining scene by turning on all scene members individually. There is a monitoring program for that too.

If status kitchen lights is not off

And status island lights is not off

Then set scene dining kpls on.

 

I can use the all off button to turn all the lights off. Or we can activate another scene. I hope this is somewhat helpful.

Eric

Link to comment

However, other buttons assigned as smaller scene controllers to control one of the lights of the same scene (i.e. say just kitchen lights) does not indicate a status change when turning on dinner time

 

Are those "other buttons" assigned as responders to "dinner time" (they should be, if you want them to come on in response to dinner time).

 

The fact that one scene turns on lights that are also part of another scene does not automatically cause controllers of the other scene to come on.

Link to comment

Are those "other buttons" assigned as responders to "dinner time" (they should be, if you want them to come on in response to dinner time).

 

The fact that one scene turns on lights that are also part of another scene does not automatically cause controllers of the other scene to come on.

Both great answers that I will look into. I like the idea of having monitoring programs.  But it appears one remedy is to setup the buttons that are controllers for a smaller portion of a larger scene (such as my "kitchen scene" that turns on only 1 set out of 4 sets of lights that are part of my "dinner scene") to also be responders to the larger scence (i.e., dinner).  Will give it a try tonight!

Link to comment

If all you want is to ensure that controllers for kitchen scene come on when you press dinner scene, then including as responder to dinner scene is likely best option.

 

If, in retrospect, your interests are broader and you want the kitchen scene controller button to come on when any individual light within the kitchen scene is on for any reason, I would tend to favor the programmatic approach described by erick.

 

As with many cases, it all depends on what you are trying to achieve.

Link to comment

Yeah just to add after reading just the first few posts on here, how do you know it's a communication problem to the people suggesting that?  This might be as simple as a KPL button being a controller of a scene with a lamp as the responder in it.  The KPL turns the lamp on and off, LED light works as expected.  However if you turn the lamp off manually or from your phone, the KPL still shows it is on as the scene technically is still on.  If that's all the issue is, then a simple program like "If status of lamp is on and status of lamp is not off, Then set KPL1.B.LED Scene to ON, else set KPL1.B.LED Scene to OFF" where KPL1.B.LED is a scene that just has the KPL button in there as a responder.

Link to comment
  • 2 weeks later...

Yeah just to add after reading just the first few posts on here, how do you know it's a communication problem to the people suggesting that?  This might be as simple as a KPL button being a controller of a scene with a lamp as the responder in it.  The KPL turns the lamp on and off, LED light works as expected.  However if you turn the lamp off manually or from your phone, the KPL still shows it is on as the scene technically is still on.  If that's all the issue is, then a simple program like "If status of lamp is on and status of lamp is not off, Then set KPL1.B.LED Scene to ON, else set KPL1.B.LED Scene to OFF" where KPL1.B.LED is a scene that just has the KPL button in there as a responder.

Okay yes, I think this is the only issue.  Becase I had to go out of town for work undexpectlely, I didn't get a chance to try the various fixes.  THis sounds like a likely issue.  So it looks like I first will need to setup a scene where the KPL individual botton LEDs are responders.  I need to look into this.

Link to comment

Yeah just to add after reading just the first few posts on here, how do you know it's a communication problem to the people suggesting that?  This might be as simple as a KPL button being a controller of a scene with a lamp as the responder in it.  The KPL turns the lamp on and off, LED light works as expected.  However if you turn the lamp off manually or from your phone, the KPL still shows it is on as the scene technically is still on.  If that's all the issue is, then a simple program like "If status of lamp is on and status of lamp is not off, Then set KPL1.B.LED Scene to ON, else set KPL1.B.LED Scene to OFF" where KPL1.B.LED is a scene that just has the KPL button in there as a responder.

I tried to set it up as you described but can't seem to get the scene correct. For one, I'm not sure how to setup a scene that just impacts the LED light.  I did create a "hallway LED scene" that had that kepadlinc button as a responder.  I didn't see an option to make it just for the LED light.  Not sure if it matters but the hallway-keypad-hallway is the direct load (A button) for one of my keypad lincs (in hallway).  As far as the program.  I didn't have the option to set it up "if status of lamp is on"  it would only give me the options for responding, percent on, or off.  Basically, with this setup when I hit one of my scenes that is suppose to turn on the hallway lights; it does briefly before turning it off.  So its operating the light and not the LED. See below for how I did program.

 

If

        Control 'Hall Keypad-Hallway' is switched On

    And Status  'Hall Keypad-Hallway' is not Off

 

Then

        Set Scene 'Hallway LED' On

 

Else

        Set Scene 'Hallway LED' Off

 

Just redid the above but substituted the Kitchen keypad button for both the scene and program above. Since it wasn't a direct load button it seemed to work better; but the LED still doesn't come on with a scene that has "kitchen" as one of the sets of lights in a larger scene (aka dinner time which has kitchen and several other lights).  Althought if I press another keypad linc button that is a controller for "kitchen" then the LED on the other Keypad responds correctly.

 

Link to comment

Archived

This topic is now archived and is closed to further replies.


×
×
  • Create New...