oberkc

I don't know why you could not have two programs: if control KPL is switched on then turn off outletlinc else if from time xx:xx to time yy:yy then turn on outletlinc else turn off outletlinc Understand that if you happen to press your KPL button AFTER time xx:xx, it will stay off until the next day.

LeeG, Thanks for the explanation. I was not sure whether changing a responder level required any updates to the controller. I now understand that it does not.

Given your program, this could also be caused by the configuration of the motion sensor. I believe thay can be set to send only "on" commands. If yours is set this way, your program would not turn the lights off (except at sunrise). I am also assuming your elk zone is not in a constand "violated" state.

I believe motion sensors can be set only to on (100%) or off. This is not as I understand it. I understand that it is the responder level that controls response to a motion sensor (or any other controller). There may be a couple of things going on here. First, I wonder (not sure) if one can change attributes of a scene containing a motion sensor. Since motion sensors are battery-operated, they cannot be re-programmed without first putting into linking mode (or within a few minutes of sending a status change). Second (more likely), responder levels can vary based upon which controller is initiating the scene. For example, a "scene on" level can be different if initiated by the ISY versus the motion sensor. Is it possible that you are reducing the master scene levels while leaving the response to a motion sensor at 100%?

Functionally, it should. The difference with scenes is that you may notice a bit quicker response. Otherwise, there is no functional difference that I can see. One nice thing about scenes, however, is that they will continue to work even should something happen to the PLM or ISY.

I believe ANY change in status will trigger an evaluation. The path it takes from there depends on the results of the evaluation. If 'kitchen_oh' is a dimmer, then "on" means full 100%. Anything less will result in a "false" indication, running the "then" path.

Given that I do not think your program is at fault, I would look at other things. -it appears that you manually typed your program into the forum, correct? Make sure there are not any subtle differences (am/pm errors, for example) -check to see if the scene is working. From the ISY control panel, manually turn the scene on. Did it work? -Like LeeG suggests, check program last run time. Is it running at the times you expect? It is possible to disable programs or to include them in folders that are, themselves, disabled. Otherwise, this is pretty simple and not much can go wrong, short of device failure or communication issue.

If Status 'Kitchen_oh' is On Then Wait 2 seconds Set Scene 'Media_Keypad_D' On Set Scene 'Garage_Keypad_D' On Set Scene 'Frontdoor_Keypad_D' On Else Wait 2 seconds Set Scene 'Media_Keypad_D' Off Set Scene 'Garage_Keypad_D' Off Set Scene 'Frontdoor_Keypad_D' Off This looks to me like you are trying to use a program where a scene would be a better solution. Why not get rid of this program and make 'kitchen-oh' controller of the other three scenes?

Then that explains your use of non-toggle off instead of on. It sounds as if you have a good handle on how this works and made good choices. In your case, I like the query approach offered by arw01. Perhaps a program triggered by a keypad button or change of state of your sensor?

The reason that I like "non-togge ON" is that there is only ONE way that the KPL button turns off: when directed by the IOLinc sensor as a result of the door closing. I prefer to have confidence that the door is closed. Alternatively, the suggestion by arw01 may work as well.

I see nothing wrong with the program that would fail to turn on the light a 5pm.

I agree that there may be updates to the devices and firmware that render some details obsolete, but I would argue that the theory is still accurate. -Wire relay so that closed door = sensor off. Conncet relay wire to opener or button. - make two scenes, one with sensor as controller of button, second with button as controller of relay. -Configure button as non-toggle on. -configure relay to respond to "on" commands in momentary mode If there is a particular detail that is stumping you, bring it up.

I suspect you may have some transition problems around 10pm. The extent depends on the time-out period of your motion sensor. Lets assume that you detect motion at 959pm. Lets assume that 10pm occurs befor the motion sensor sends an "off" command and the first program turns false. Under these conditions, I assume that the light would stay on indefinitely.

. Unfortunately, the beep at sunrise WAS a specifically identified problem ..

Your KPL STAYS ON when you press fast off? Yes, it sounds like there might be some interesting (and unexpected) interractions between the scenes and programs.

Since this button does not appear to be a controller of any scene, how does it "toggle the stair light"? Are you saying that the button does not change status in response to any of the thee listed devices?

Most of my programs fail to include an "else" set of program steps. I was going to use the from/to timer as an example, but apostolakisl beat me to it. I like the variable approach for cases where you have multiple programs using a common condition, but probably prefer program folders for this. If from time x to time y then run the programs in this foler if from time y to time x then run the programs in this folder Either (variable or folder) will work fine, but specific individual needs may make one approach more benificial than another

Keep in mind that this will run ANY time that the program condition is triggered and evaluated as "false". Your program will be triggered upon one of three conditions: sunset, sunrise, and reciept of an "off" command from the "remote entry". At sunrise, the condition is triggered. There was no reciept of an "off" command, which meant that the condition was false>>>run "else". To me, this appears to be normal for ISY. I assume you will have to break this into two programs. The first: If Control 'Remote Entrance' is switched Off And From Sunrise + 1 second To Sunset - 46 minutes (same day) Then Set 'Condition' On Set 'Foyer' 1 (Beep Duration) Set 'Foyer' 1 (Beep Duration) Set 'Foyer' 1 (Beep Duration) Set 'Foyer' 1 (Beep Duration) else the second: If Control 'Remote Entrance' is switched Off And From Sunset-46 minutes To sunrise + 1 second (next day) Then Set 'Condition' On Set Scene 'ALL LIGHTS and PLUGS - CONDIT' Fast Off Wait 2 seconds Set Scene 'Sunset OUT OF HOUSE' On

http://wiki.universal-devices.com/index ... e_Door_Kit

You may indeed be looking at this wrong. Why would the lights shut off in two minutes? Is the motion sensor defined as a controller of any scene? If not , what program would turn off you lights in two minutes? I believe Xathros is correct, you lights will not go off, and "control" is a better approach if you want to use a program to control you motion lights. Or follow vyrolen suggestions... Not use a program and use the motion sensor as a scene controller based upon the built in funtion. The benefits of using a program are several. You have greater flexibility over time periods. You can introduce other condiotins, such as time, light status. You can make adjustments without having to open the motion sensor.

It would probably be easiest to check your actual program. Until then... Your original question was with regards to using a KPL button as an indicator without mentioning that you wanted to use that same KPL to control a scene. This definitely adds another layer of complication. In retrospect, two programs or one probably makes no difference. Given your latest set of requirements: I would keep the scenes as you have defined. I would then create a program: if control KPL3 is switched off or control KPL4 is switch off then set KPL1 off What you did not state was what, if anything, you want to happen to KPL1 if you separately turn both KPL3 and KPL4 on. You also did not mention how you define "on" with the outlet dimmers. Is this 100%? Do you expect KPL1 to go off when you DIM one or more of the lamps? Do you want KPL1 to go off ONLY when the lamps are full off? Answers to these questions will affect your program(s).

This cable is, in my estimation, the switched power to the fixture. Black is power, white is neutral. Good. White and red are, currently, the two travellers to the other three-way switch. Good. As LeeG states, red is hot. It is the unswitched power. I expect that you will find the red wire in the other box connected to the black (common) screw. You are in GREAT shape here. You have unswitched hot. You have a neutral. You know which cable goes to your fixture (cable 1). In this location, remove cable 2 red from the other blacks and cap. Connect cable 2 black to the blacks. Connect black of your new switch to these blacks, as well. Connect cable 2 white to the bundle of whites. Connect switch white to this bundle, as well. Connect switch red to cable 1 black. The only loose cable you should now have is cable 2 red. In the other switch location, you have red, black, and white. White is now neutral. Black is now unswitched hot. Red is nothing...cap it. Cap the red wire from the switch (it is not needed). Connect black to black and white to white. Your wiring is complete. Cross link the two switches. You are done.

When you say "Garage configuration has two black wires and one white", is that all!? Please describe entire garage configuration in terms such as: this is a single switch box. there are two cables entering the box. one cable has two conductors, black and white. the second cable has three conductors, black white and red.

Program I'm using: If Status OutletLinc Dimmer #1 is OFF OR Status OutletLinc Dimmer #2 is OFF Then Set KPL Button 1 Off. Else It's as if the ISY takes an instant before it recognizes both Outlets are on. I believe the problem is that when you turn on KPL1, the outletlincs respond with a change in status, triggering your program. I find it rarely to be good practice to have a program "then" condition that can trigger an evaluation of the "if" path. Perhaps it would be worth trying breaking that program into two: if: original conditions then run second program "then path" Second program: if then original path

The only problem with this approach is that it does not afford the ability to override the motion sensor by manually turning on the light