Adding 2nd Keypad link button to scene

[lithiumus]

I created a "night" scene that turns all the lights off in the house except the outside lights and dims the hallway lights.  All the switches are responders.

 

I added a single Keypadlinc button A from a 6 button keypad as a controller.  I set the Toggle to On.  This worked perfectly.  I would press the A and it would blink twice and then stay off and would activate the scene as expected.

 

I wanted to add another button from a different keypadlinc to also activate the "night" scene.  I added it as a controller as well and set the Toggle to On...  however, when I press button A to activate the "night" scene, the other keypadlinc C controller would light up and stay on.  If I press A again, it activates "night" and A stays off but C LED stays on.  If I press C, it also activates the "night" scene and turns the A button LED on so both button LEDs are on which is not what I want.  I tried to write a program but the only insteon control available is on/off dim values.

 

Any ideas on how I could add the 2nd or 3rd button but have all the LEDs stay off when another controller activates the "night" scene?

Edited March 31, 2017 by lithiumus

[stusviews]

Create a scene with the buttons as responders. Use a program to turn off the button scene x seconds after either "night" button/scene controller is set On.

[oberkc]

Litiumus,

 

What I find interesting in your post is that, in the second paragraph, you state that the original keypad button is in non-toggle ON mode, yet you say it blinks twice then turns OFF!? I find that to be abnormal. My buttons, configured such, would flash and stay ON (much like your second button). The question, in my mind, is what is different about your first and second button xonfiguration that would cause the.different behavior?

 

Regardless, I can think of no better solution than stusviews suggested approach.

[lithiumus]

Create a scene with the buttons as responders. Use a program to turn off the button scene x seconds after either "night" button/scene controller is set On.

 

Ah yes!  As always...  the master Jedi's wisdom is demonstrated!  I really need to expand my mind...  Thanks for showing me the way!

[lithiumus]

Litiumus,

 

What I find interesting in your post is that, in the second paragraph, you state that the original keypad button is in non-toggle ON mode, yet you say it blinks twice then turns OFF!? I find that to be abnormal. My buttons, configured such, would flash and stay ON (much like your second button). The question, in my mind, is what is different about your first and second button xonfiguration that would cause the.different behavior?

 

Regardless, I can think of no better solution than stusviews suggested approach.

 

Hey oberkc, when I press the Keypadlinc A/B/C/D button, the button LED blinks twice, sends an ON signal to the scene and the button LED stays unlit.  I believe this is the expected and normal behavior.  non-Toggle OFF should do the exact same except send an OFF signal to the scene which I do not want as I'm turning some lights on with the "night" scene.

 

Based on what stu is saying it's making sense now...  when 2 controllers are added to a scene, they are both controllers and responders.  When I press button A, it acts as a controller and ALL other buttons act as a responder including button C which is the other controller.  Even though I have set the scene to turn off button C as well as the button A controller command of the scene...  button C still stays on.  May have something to do with the timing which Stu may have eluded to with the delayed program to turn off the buttons as responders.

[oberkc]

Lithiumus,

 

Based on my experiences, a botton set to non-toggle ON will, when pressed, flash a couple of times, then stay ON. Based upon that, i find the behavior you describe more like: unexpected and abnormal.

[lithiumus]

Lithiumus,

 

Based on my experiences, a botton set to non-toggle ON will, when pressed, flash a couple of times, then stay ON. Based upon that, i find the behavior you describe more like: unexpected and abnormal.

 

hey oberkc,

 

I'm just a noob but a Keypadlinc button LED that stays on when pressed and then LED off when pressed again would be configured as Toggle.  A non-toggle by definition should not keep the LED on and should stay off while sending either "on" command or "off" command depending on what you decide.

 

None of my Keypadlincs in Non-Toggle mode will keep the LED on after you press it.  It only blinks twice then stays off.  Did the behavior change with newer versions?

[lithiumus]

However...  if the Keypadlnc LED is already on and you change it to non-toggle...  the button LED will stay lit when you press it.  It will blink 2 times and stay on.  So basically the Keypadlinc stops toggling the LED and seems to ignore whatever state the LED of the button is...  if it's already on, then it stays on and if it's already off, it stays off in non-toggle mode.

 

My problem is that the LED is responding to the "on" command from another controller...  which will soon be addressed!

Edited March 31, 2017 by lithiumus

[oberkc]

if it's already on, then it stays on and if it's already off, it stays off in non-toggle mode.

 

A non-toggle by definition should not keep the LED on and should stay off while sending either "on" command or "off" command depending on what you decide.

 

hello lithiumus, 

 

based on my experience, there are two non-toggle modes: non-toggle ON and non-toggle OFF.  In non-toggle ON mode, it will flash then stay on, regardless of starting state.  In non-toggle OFF mode, it will flash and stay off, regardless of starting state.  I know of no "non-toggle" mode where it simply stays in whatever state it started.  I find this experience consistent with the manual for the keypad, as well as the options available from the ISY admin panel.  I have no opinion on what it "should" do...only what it does in my house.

 

Either I misunderstand what you are saying, or our experiences and expectations are different.

 

None of my Keypadlincs in Non-Toggle mode will keep the LED on after you press it.  It only blinks twice then stays off.  Did the behavior change with newer versions?

 

My oldest keypads are about 7 years old.  My newest about a year.  I have noticed no change in behavior regarding toggle mode.

[stusviews]

The KPL non-Toggle option changed a few years ago. The older options were Toggle, non-Toggle On and non-Toggle Off. The last option, non-Toggle Off was eliminated, but the ISY still has all options and only the ISY should be used to select the mode of choice.

 

That said, what oberkc indicated is still true. In non-Toggle mode the button LED will end up in the selected mode no matter how many times it's pushed and will always send the selected signal each time it's pushed. The only way to change the illumination of the button's LED is to place the button as a responder in a scene and use a program to set the scene on or off no matter the selected mode.

[lithiumus]

Thanks guys.  That clears it up.  I was actually able to get the keypadlinc button to turn off via the scene and the controller commands without having to use a program.  I guess it was working as it should in non-toggle ON and when I adjusted the scene and both controllers to set the keypadlinc button OFF, the key now blinks twice and stays off they way I want it to.

 

Thanks again and sorry for the confusion!

 

I think the reason the button was turning off when there was only 1 controller in the scene was because I either had the scene or the controller command set the button to OFF.  When I added the other controller, I didn't set its command to also set the button to off.  Now the Scene and both controller commands are setting the button to off so it's working as I wanted.

Edited April 3, 2017 by lithiumus