2486S/WH6 Programming Question

[johnmsch]

With a 2486S, is it possible, via ISY99i programming to turn on button "B" when button "A" is pressed? Here's the scenario I'm trying to program.

 

I setup these two programs for button "B":

 

Shop Fan On:

If

Control 'Garage KeypadLinc - B' is switched On

Then

Set 'Shop Fan' On

Else

- No Actions - (To add one, press 'Action')

 

Shop Fan Delay Off:

If

Control 'Garage KeypadLinc - B' is switched Off

Then

Wait 10 minutes

Set 'Shop Fan' Off

Else

- No Actions - (To add one, press 'Action')

 

I have programmed button "A" to turn on/off 3 set of lights. I would like for button "A" to turn on the "B" button also. Of course, I can add this line to the "Then" section of the program "A" code:

Run Program 'Shop Fan On' (Then Path)

However, doing that would not actually turn on the "B" button. I have looked at all the possibilities when creating the program, but don't see an option to turn on or off one of the other buttons on the 2486S via an ISY program.

 

Is this possible?

[LeeG]

To control a Secondary KeypadLinc button define an ISY Scene and add the Secondary KeypadLinc button as a Responder. From a Program turn the Scene On/Off to turn the Secondary KeypadLinc button On/Off.

[johnmsch]

Thanks for the tip Lee. Can you point me to a tutorial/example of setting up scenes in the ISY? The only example I can find is doing a scene with just the buttons and doesn't involve the ISY.

 

I did create a scene in the main tab of the ISY console, and added that button as a responder.

I then went through these steps, but don't see the scene listed:

Program detail tab, select a program

Hit the Action button

Select Adjust scene

The "In Scene" dropdown box is empty and does not list my new scene

[LeeG]

johnmsch

 

Sounds like the Scene is defined correctly. A Secondary KPL button has nothing to "adjust" so it may not appear in the Adjust Scene selection list.

 

Use Insteon (rather than Adjust Scene), select Scene name and On or Off. The Scene names are not in collating sequence unless you restart the Admin Console. I defined a new Scene and added a Secondary KPL button as a Responder. My newscene appears at the bottom of the list. Then added an Action to a Then Clause using "Insteon" Set "newscene" "ON" to confirm I had not missed something.

 

On the UDI Wiki in the How-to Guide section, under Scenes is a step by step explanation on Scenes.

 

Lee

[johnmsch]

Ok, that worked, using "Insteon" instead of "Adjust Scene". The scene was indeed at the bottom of the list. So now when I press button A, all the garage lights come on, then button B lights up, but the shop fan does not come on.

 

As you can see from my original post in this thread, button B turns on the shop fan, which is wired to a 2466S ToggleLinc Relay. How can that B button turn on, but not start the shop fan? If I just hit the B button by itself, it lights up and the shop fan comes on. Hit it again, and the light goes off and 10 minutes later the fan goes off. Its just not doing that in the new scene.

 

Thanks for the How-to Scenes link. I read it over a couple of times and am really embarrassed. I spent almost 30 years programming computers, but this scene stuff still has me baffled! Guess it will take some time and experimenting for it all to sink in.

[LeeG]

johnmsch

 

You are making good progress. A basic Scene is an Insteon construct. The ISY makes defining Scenes pretty easy. Actually defining one ISY Scene results in multiple Insteon Scenes being generated under the covers. Any given Insteon Scene can have only 1 Controller. When you define an ISY Scene and add multiple Controllers, the ISY is actually generating multiple Insteon Scenes, 1 for each Controller and 1 additional which has the ISY PLM as the Controller, again all defined under the covers. It is this PLM Controller Scene that is used by Programs and the Admin Console.

 

If you want other devices to turn On/Off in addition to KeypadLinc Secondary button B, these devices must be added as Responders to the Scene. Insteon does not propagate Controller requests beyond the specific Responders. That is, when KPL Secondary button B is turned On by the ISY Scene, the KPL DOES NOT propagate the On request to KPL button B Responders. A Responder does not turn into a Controller when the responder is directed to turn On by another Controller device. This is consistent across the Insteon line.

 

There is a rather old but mostly still applicable insteondetails.pdf document that covers the basics of Insteon. The document is in the public space on insteon.net web site.

 

Lee

[johnmsch]

Ok, the light bulb over my head just went on. Its all starting to make sense now. That was a really great explanation of how all this works.

 

I'd still like to see someone put together a video, or a step-by-step example of setting up a scene using the admin console. The documentation I found is just too brief!

 

Thanks again for your replies. You are terrific resource and I appreciate you taking the time to help!

 

John

[johnmsch]

Oh yeah, its all falling into place now. I'm creating scenes like a madman!

 

I still don't understand the "Apply Changes To All Devices" checkbox in a scene. Under what circumstances would you check that, and when would you not?

 

Thanks!

[LeeG]

There is a Scene with 6 responders. The On Level for all 6 responders should be changed to 50%. Of course each individual responder On Level can be set to 50%. Or the "Apply Changes To All Devices" box can be checked which will result in a single line with On Level and Ramp Rate. When a change is made to that single line the change is applied to all the responders in the Scene.

 

The ISY User Guide has a good description of this and the "Copy Scene Attributes From ..." features.

[johnmsch]

Got it. Thanks again. Have a great weekend!