All Off button on Keypad Link...

[Tom Marek]

I really hate asking for help but I've been searching for an answer for over three hours. Due to strange switch problems and cross linking issues, I decided to factory reset all my Insteon switches and delete my ISY defined devices and start from scratch. The good news is I cleaned up all my linking and ramp rate issues using ISY and not the SmartHome method.

 

The bad news is I broke my "all off" Keypad link function and can't for the life of me figure out how to fix it. I took screen shots of the program tab and of the scenes/devices on the main tab before I started. I have a tabletop KPL on the nightstand. When button D is pushed, it used to flash on, all controlled lights would dim off, then the KPL D button would turn off. Now nothing happens at all other then the KPD D LED flashing on/off.

 

ISY version is 2.7.15.

 

My program looks like:

If

Control 'Headboard KPD_D_ALL OFF' is switched On (set to non-toggle off)

Or Control 'Headboard KPD_D_ALL OFF' is switched Off

 

Then

Set Scene 'My Lighting' Fade Down

Wait 3 seconds

Set Scene 'Keypad Secondary Buttons ALL' Off

Wait 30 seconds

Set Scent 'My Lighting' Query

 

Else

- No Actions

Any ideas? Thanks.

Tom

[Michel Kohanim]

Hi Tom,

 

No problem at all and I am sorry to hear that you are having such a difficult time.

 

First of all, I think what you need is an All Off/All On scene (not a program):

1. Put KPL button D as a controller

2. Put everything else as a responder

3. Click on the KPL button D in this new scene, and adjust desired on level/ramp rate for each responder

4. If you want button D to only turn the scene off, then, go to My Lighting, choose KPL Button D, at the bottom center of the screen choose Button Toggle Mode and make this button Toggle Off

 

 

With kind regards,

Michel

[oberkc]

Now nothing happens at all other then the KPD D LED flashing on/off

This concerns me. While I would prefer the proposed method of Michel, I would have also expected yours to work (or at least do something). The flashing LED makes is, I thought, an indication that the keypad is not seeing some response that it is expecting. Unless this button is in some other scene, then the only response it could be expecting would be from the PLM.

 

I would first open the event viewer. With the viewer open, I would press the KPL button. Does the event viewer show receipt of the command. My concern is that it is not. If not, then it is time to find out why not, and I would do this regardless of the method you ultimately choose for your "ALL OFF" scene.

[LeeG]

The flashing KPL button LED when a device fails to respond has been removed from later KPL firmware. A KPL button in non-toggle Off mode will flash a few times to confirm the button has been pressed. So will a non-toggle On mode button. Just the non-toggle Off mode button starts from an LED Off state.

[oberkc]

A KPL button in non-toggle Off mode will flash a few times to confirm the button has been pressed.

Ah! I missed the non-toggle off setting. Yes, this is likely why it is flashing, then. Though I had not known (or forgotten) about the elimination of the error flashing feature.

 

But, still, I would expect a response from his program and I am still curious about the possibility that the ISY is not getting the command.

 

Looking back, I am wondering also if it is possible that the action in the "then" response is changing and forcing a re-evaluation of the "if" conditions, thus halting further execution of the program. Perhaps this is the reason his program is not working as expected. Given my understanding of this possibility, perhaps removing the 'wait' statements would solve this problem.

[LeeG]

oberkc

 

I agree completely that the Program should work. Knowing if Events are received when the KPL button is pressed would determine whether to back up and look at links and device communication or forward at a Program/Scene issue.

 

Michel is also right in that the solution can be done with a Scene and non-toggle mode eliminating the need for a Program altogether.

 

I think Tom was the first to note the blinking KPL button feature went away. I was sorry to see it go. Likely made room for more functional capability in the KPL.

 

Lee

[Tom Marek]

First of all I want to thank all of your for your responses. I tried adding a scene and that solved the problem but... Being the curious type, I went back to the original configuration and looked at the event viewer. I saw the command being received but ISY ignored it.

 

Looking into my program structure I have a program called Normal for day-to-day operations of lights. This time of year I also have a program called Christmas that incorporates my xmas lighting. The program says between Nov 30 and Jan 1 run programs in this folder. Apparently now only the Christmas folder is running. Program summary shows Christmas=True and Normal=False. Both used to be true before I deleted all my devices the other day. Not sure what changed as I didn't delete any of the programming just the devices. I did have to fix the programming after rediscovering devices by adding the device names back in. I'll have to take another look at how the programs are called or figure out a way to rewrite this mess so I don't have to have duplicate entered in both Normal and Christmas folders.

 

Now on to trying to get my Elk M1G talking to my Insteon devices. Thanks again for the suggestions. They helped a lot.

 

Cheers!

Tom