Hi everyone.

 

Someone knows how to do this?

 

I read the entire document for this 2334-222 8-buttons keypad from Insteon and it says to tap the keypad button we want as a responder. But when I do that, it stops the blinking of the green led from the keypad without the double beeps and it does not work. 

I seem to have once been able to link the two buttons, but it was by holding the on/off button for 6 secondes, which lit the lights of the living room, while I want those lights to be turned off when I press the «all off» scene button...

 

Any help would be welcome. :/

In the Admin Console, start by creating a scene to be controlled by the controlling button on the KPL - make sure you add that button as a *controller*, not just responder.

 

Then drag the button that is the responder into the same scene.

 

Done.

Thank you Mwester.

 

After watching and reading more informations, you made me realized that we better create the scenes with the Admin console, even though it is easy to do it locally. (except for my small problem mentioned on this thread)

 

But now, I am wondering why the console does not detect the scenes programmed locally?

 

Should I restore the devices to factory default and redo the scenes on the console to avoid conflicts?

By example, I have a dimmer module for a lamp in my child's room, and I wanted to make a crosslink between the two devices. It worked. But when I use the console to control the wall dimmer, I see the led light move but it does not control the module. When I use the wall dimmer manually, it works...

Can someone explain?

When you use the Admin Console to control a device, only that device is controlled, not any of its links. To do otherwise can result in an infinite loop. If you want to control both a device and its links, then control the scene, not the device.

Should I restore the devices to factory default and redo the scenes on the console to avoid conflicts?

 

 

I believe if you perform "restore device" you will remove any links to other devices you have created by manually linking and only those created through the use of ISY will remain.

 

 

Jon...

Thank you Mwester.

 

After watching and reading more informations, you made me realized that we better create the scenes with the Admin console, even though it is easy to do it locally. (except for my small problem mentioned on this thread)

 

But now, I am wondering why the console does not detect the scenes programmed locally?

 

Should I restore the devices to factory default and redo the scenes on the console to avoid conflicts?

 

By example, I have a dimmer module for a lamp in my child's room, and I wanted to make a crosslink between the two devices. It worked. But when I use the console to control the wall dimmer, I see the led light move but it does not control the module. When I use the wall dimmer manually, it works...

 

Can someone explain?

As jon posted above use the Restore command on the device.

 

Right click on the device in the device tree in the Admin Console and select restore from the fall down menu.

No need to Factory restore it to do this but I would anyway....

 

   after much advise and bad times I always do a Factory restore on any device I bring home before adding to ISY.

You can do a Factory Restore on a device any time and then do a Restore from the Admin Console and it will repair and replace ll the links that ISY knows about.

 

In the future it is best to let the Admin Console manage all the links used by creating them there.

Wow. I will never mess with manual linking ever again.

I first tried the restore option from the ISY menu. It did not work, the previous links where still active.

 

Then I did the hard reset (pulling the set pin, then pushing it in until the long beep stops)

 

It worked, my keypad was like when I opened the box, except it was still linked to the ISY. But, my scene were only working from the admin console, not working when pushing the buttons.

 

I then redid the admin console restore. What I understand is that the manual restore erase every links, while the console restore repairs the links written in the controller. BUT, after that, when I pushed a keypad button, it just opened all the lights linked to it by the scene to the maximum (which is not my scene at all) I then notice that the scene was still written correctly in the console, but when clicking on the keypad button that acts as the controller of the scene in the list under the scene, it was set like that : everything at 100%. So basically, the controller was functioning properly, but the memory of the scene was erased from the device. I readjusted the levels, and now it works fine.

 

There is just on more thing though : what toggle option should I use if I basically just want those keypad button to trigger a lighting pattern without needing to turn it off? I would rather press another button for the next scene. 

 

Example : we arrive home, we press B for the entire first floor to lit at dimmed levels. Then we start cooking, we press C for the kitchen lights to go at 100% without closing the living room and dining room lights. Then we dine, we want all the lights of the first floor to turn off and only the dining table light to be at 45%. Etc.

 

If I do that, every keypad button is considered on, the led of the button is lit and if a presse another time those buttons, it turns everything off. I dont want my guests to have to go dark before I can switch to another scene...

 

Thanks in advance for your precious help to a newby. I hope this thread will be usefull for one or two newcomers like me.

In the scene that you want active, turn off the other buttons. For example, for the button C scenes, set button B to off. The next time you press button B, it will turn the B scene On, not off.

That's a good idea. Although, wouldn't I need to add a one second wait time or something? Because, if a light is set to open to 50% on C , and B is suppose to open it at 100%. But closing B will send a closing message to the light, at the same time as opening C will send a message to the light to open at 50%, won't it bug?

In any cases, I fond a way that seems to work. First, the scene button are set to non-toggle and just signal

"On". And, the led behind the buttons is set to off. So, it does not look weird when buttong are On and it works.

Sending a signal (on or off) to a device affects only that device, not any of its links. So if you use a scene to turn off button B, only button B's LED turns off, not any of the devices that button B controls.

Wow. I will never mess with manual linking ever again.

 

.......

Now that we have set the ISY "hook" you have an obsession hobby for life a while..

@Stusviews  Thanks for the explanation. At first, it did not work : because I added the keypad buttons to the scene and set them to 0%. When using the console, it worked. When using the controller button, it worked, but lit the led of all keypad buttons!

Then, from the scrolling down menu of the scene, in the controller button (red) submenu I set the other keypad buttons to 0% too. And it works.

 

How come I need to program the scene, and then program it again in the sub menu of the controller button?


@Larryllix    Yeah, it seems like that I'll be okay!