Trigger a Program with KPL Button -- Fast On

[geogecko]

I have an 8 button KPL that has a non-load button called "All On." After having responders linked to these type of buttons in the past, and our 2, going on 3 year old has found out how to operate KPLs, I want to change something.

 

Basically, I want the "All On" button, when double-tapped (fast on) to trigger a program in the ISY-99, that in turn, turns all the lights on. I've got the program setup, but it never triggers. Does the KPL button have to be linked to at least one responder before this would work? Does the KPL button need to be linked to the PLM or something?

[oberkc]

I do not believe it has to be linked, other than to the ISY/PLM. You did link it to the ISY, did you not? If not, then begin linking with the ISY and then set the KPL button to link status, adding the device to the ISY device list.

 

This is all by memory, but your if condition would be based on a "control" (not status).

 

If control "KPL Button" is faston

Then set scene "all house" on.

 

Or something like that. The ISY will, of course, create the correct verbage.

[geogecko]

Yep, exactly what I'm doing in the program, and the KPL is in the ISY device list.

 

I think it may be a problem with the KPL itself. I have 2 KPLs setup in the program (they both have an "All On" button), and the newer one works just fine, the older one just blinks when I try and do anything.

 

I'm restoring the KPL that doesn't seem to work. I think it is version 29, whatever that means. The other one is new, within the last 4-6 months.

[oberkc]

Blinking, at my house, suggests communication problems. I suggest opening the event viewer and trying your suspect keypad button. See if the event viewer captures the button press correctly. If not, you may have a bad KPL, or you may have some communication issues.

 

Also, try a scene test on your all house scene. Does it indicate any problems?

[geogecko]

The scene test works great, the scene even works from the newer KPL, just not the other one. Here is the event log, after double tapping the All On button on the non-working KPL.

 

Fri 01/29/2010 02:10:12 PM : [iNST-SRX ] 02 50 09.93.F2 00.00.07 CB 14 00 LTOFF-F(00)

Fri 01/29/2010 02:10:12 PM : [standard-Group][09.93.F2-->Group=7] Max Hops=3, Hops Left=2

Fri 01/29/2010 02:10:12 PM : [ 9 93 F2 7] DFOF 0

Fri 01/29/2010 02:10:12 PM : [iNST-SRX ] 02 50 09.93.F2 11.CD.BA 41 14 07 LTOFF-F(07)

Fri 01/29/2010 02:10:12 PM : [standard-Cleanup][09.93.F2-->ISY/PLM Group=7] Max Hops=1, Hops Left=0

[Michel Kohanim]

Hi geogecko,

 

I think the problem is actual communications between the KPL and your devices. How many of your devices in this scene are SWL 35s?

 

With kind regards,

Michel

[oberkc]

So it appears that your ISY is seeing even the old KPL. The scene test works, which suggests communication is good. Maybe one of the experts at reading these logs can confirm all is well.

 

I may have missed this earlier, but I now notice you have two buttons you want to use to trigger a scene. In your program, do you use two conditions? For example:

 

If control "KPL New Button" is faston

or if control "KPL Old Button" is faston

 

Then set scene "all house" on.

 

Are these two buttons used for anything else? What do you want to happen as a result of a single button press? Do you still have either of these two buttons as controllers of a scene or did you eliminate this as a result of the newfound skills of your 2-year-old?

[geogecko]

Thanks for the assistance.

 

For some of your questions, please see the attached images. Yes, you are correct, I don't want the actual KPL buttons linked to anything, because my 2 year old plays with the KPLs on a random basis. I thought, well, maybe that was the reason, so since I have two KPLs with the same two sets of buttons (All On, All Off), I just cross linked the buttons to each other, and that still doesn't work, so I removed those links. The All On Scene works fine from the Master.All On KPL button, just not from the older Nook.All On button.

 

As a side note, I upgraded from 2.7.0 to 2.7.7, and love the grouping feature for things such as KPL's, but is it normal that now the non-load buttons of the KPLs show up as devices? I don't really care for this, because the buttons (other than the load button) are not really considered devices.

 

 

[oberkc]

I don't really care for this, because the buttons (other than the load button) are not really considered devices.

 

I understand this to be normal. This is how it works at my house. In many applications, these are clearly devices. If you view them simply as controls, then I can see your point. If you view these buttons as "displays" or status indicators, then the term device might make more sense.

 

Your program is as I would create. And I would expect this to work. The only thing I can think is that your two all on buttons are somehow different buttons than the ones you think they are, but I am guessing you have this set up correctly.

 

I see a lot of traffic about bugs in various types of devices, or in devices that the ISY does not recognize, but this one does not look familiar to me. Perhaps there are others that can dive a little deeper into this possibility and into your log record.

 

Sorry I cannot help much more.

[geogecko]

The other thing that is interesting, is that the new KPL that works with this scene, had to be added manually, because the ISY did not recognize the device. The old KPL, that does not work, was recognized by the ISY.

 

Now that I'm running 2.7.7, I was thinking about wanting to readd the new KPL, since I would think it would recognize it properly with 2.7.7, but I'm not sure how to do that, without erasing all the links, and having to reprogram them.

 

Any tips on that?

 

I'm working on adding my RemoteLincs now, which haven't been in service for a year or more now, mainly due to the 2 year old. I think I will just use them both in the master bedroom, as a his/her's controller on our nightstands.

[oberkc]

I was thinking about wanting to readd the new KPL

 

I think there is an option to copy or replace a device, but I have never had the need and would have to look into this. I would check the wiki or the forum and search. indeed that sounds like a promising option.

 

One other thought I had was purely experimental. I began wondering if your trouble device does not have a fast on option. I thought, perhaps, to temporarily change the program to simple on, and see if it works. This may further substantiate proper communication or narrow the options down a bit if it works.

[Sub-Routine]

Is the button in non-toggle Off mode?

 

Fri 01/29/2010 02:10:12 PM : [iNST-SRX ] 02 50 09.93.F2 00.00.07 CB 14 00 LTOFF-F(00)

Fri 01/29/2010 02:10:12 PM : [standard-Group][09.93.F2-->Group=7] Max Hops=3, Hops Left=2

Fri 01/29/2010 02:10:12 PM : [ 9 93 F2 7] DFOF 0 ====== FastOff

Fri 01/29/2010 02:10:12 PM : [iNST-SRX ] 02 50 09.93.F2 11.CD.BA 41 14 07 LTOFF-F(07)

Fri 01/29/2010 02:10:12 PM : [standard-Cleanup][09.93.F2-->ISY/PLM Group=7] Max Hops=1, Hops Left=0

[geogecko]

How do I tell? I used to know how to do that with HouseLink, but have no idea with the ISY.

[Sub-Routine]

How do I tell? I used to know how to do that with HouseLink, but have no idea with the ISY.

 

When the KPL is selected you should see a button at the bottom for Toggle Mode.

 

Rand

[geogecko]

Thanks, found it. They are all in Toggle mode, the same as the other KPL that works.

[Sub-Routine]

Thanks, found it. They are all in Toggle mode, the same as the other KPL that works.

 

Please try to reset the button to Toggle or set it to Non-Toggle On.

[geogecko]

And we have a winner!

 

Put them in non-toggle mode, and that didn't work, put them back in toggle mode, and now all of a sudden, they work...

 

Any ideas on what that was all about?

[oberkc]

non-toggle off, or non-toggle on?

[geogecko]

Well, when you try and change it from toggle to non-toggle, it says to go set the button to on or off (physically), then to come back and hit OK. They were both off, so I just left them at that, so they were set to non-toggle off.

 

Then I tried the program again, and it did not work, so I changed them both back to toggle mode, and now they work. So they are back to the way they were, before I even started, I guess they just needed to be reset for some reason.