oberkc

I may also have to apologize to you. I think I gave you bad advice. I thought simple motion programs could be handled in a single program, but may even have to break it into two programs (pretty common solution). For your motion program, try the following approach: If Time is from 1100 To sunrise (next day) Then Run next program (then path) Else Nothing Next program: If Nothing Then Turn all the lights on Wait 5 minutes Turn all the lights off Else Nothing

Is the motion sensor part of any scenes? Are the lights part of any scenes?

Posts crossed. Did you not expect them to be on? Did they turn off unexpectedly?

Well, your first program turns them on at sunset and off at 11. What time did you arrive home? Did you create any scenes that include the motion sensor (controller) and lights (as responder)? If so, delete the scene.

I actually like the else clause. This guards against the possibilty when sunrise occurs during the 5 miunte wait period. Without the else clause, the lights would remain on.

Looks good to me

I don't see any reason why a single program would not work for your schedule. If you don't want to use a scene as sdynak suggested, try: Front Porch Light - [iD 0004][Parent 0001] If From Sunset To 11:00:00PM (same day) Then Set 'Outdoor: Front Porch Light' On Set 'Outside: Garage Lights' On Set 'Outdoor: Garden Patio Light' On Set 'Outdoor: Walkway Lights' On Else Set 'Outdoor: Front Porch Light' Off Set 'Outside: Garage Lights' Off Set 'Outdoor: Garden Patio Light' Off Set 'Outdoor: Walkway Lights' Off Regarding the motion sensors, I expect your program should work with one minor modification: If From 11:05:00PM To Sunrise (next day) And Control 'Driveway Sensor-Sensor' is On <<<change to "control" rather than "status" Then Set 'Outside: Garage Lights' On Set 'Outdoor: Front Porch Light' On Set 'Outdoor: Garden Patio Light' On Set 'Outdoor: Walkway Lights' On Wait 5 minutes Set 'Outdoor: Garden Patio Light' Off Set 'Outside: Garage Lights' Off Set 'Outdoor: Front Porch Light' Off Set 'Outdoor: Walkway Lights' Off Else Set 'Outside: Garage Lights' Off Set 'Outdoor: Front Porch Light' Off Set 'Outdoor: Garden Patio Light' Off Set 'Outdoor: Walkway Lights' Off

There is one thing that favors the IOLinc: no batteries to change.

Ah, yes. That is how I do it as well. Had I seen that, I would not have felt compelled to jump into this thread. Thank you for the clarification.

Techman, In the hopes that there is a better way to do things than I have done in the past, I wanted to try your method. Unfortunately, I cannot find a way to create an action that exactly matches your syntax. How did you create this action? BTW, I am on v4.5.4

that sounds about right to me. And, ues, some programs will always be true (if control xxx is switched on) when self-triggered. Some will always be false (if control xxx is not switched on). Some can be either (if control xxx is switched on and time is from sunrise to sunset).

Once a program is triggered, the entire condition is evaluated. Theat evaluation will return either TRUE or FALSE. Based upon the evaluation, THEN (true) or ELSE (false) will run. In some cases, yes, it is possible that one path could never run. It all depends on the entire condition.

Gerry, If there are conditions besides an integer variable that do not act as program triggers, I am having trouble remembering what they would be. The bigger issue is understanding when (not if) a specific condition would trigger a program. For example, a "control-on" condition acts as a trigger only when that particluar device is acted upon locally, and only when triggered on (regardless of current state). Of course you could completely disable a program is you do not wish it to self trigger.

Gerry, Please note that it is only programs containing "wait" and "repeat" statements that would be interrupted. In no case, as I understand, would you have more than one case of a program running at any given time. If a program is retriggered, xurrent execution would halt.

To be sure I understand... you have a load connected to a switchlinc, and you wish to adjust the "on level" (aka local level) such that it goes to a different level when you directly press that switchlinc. Correct? The general format for this program command is something like: if ... then in scene switchlinc set switchlinc level to xx% <<<where both switchlincs are the same device. Please forgive the inexact syntax. I was too lazy to look it up exactly.

Does not sound normal to me. My gut is: -communication problem -broken links or similar What happens if you restore the affected devices?

Yes, scene size would also be a contributing factor I expect

Short of reducing the number of devices, the only thing i can think to do would be to reduce the number of scenes.

As an aside, i also find it interesting that relatively few questions on this forum are related to programming issues anymore. Just looking at the active topics of the last couple of days (about 20), this may be the only one. I am not sure what one can conclude from this, but it is at least interesting to me.

The trigger part confuses most of us, I suspect. For example, i offer the following program... If Time is from sunset To sunrise (next day) Then Turn on a light Else Turn off a light Many would assume that such a program is in a continuous evaluation mode and would force a light to stay on at night and off during the day. Should the light be manually turned off during hours of darkness, they believe this program would automatically turn it back on. In truth, this particular condition has two triggers: sunset and sunrise. It is only at these two trigger points each day that this program would run. The rest of the time, this program sits idle. Each statement in a condition could be a trigger. A program will run when one or more individual triggers is met. once triggered, the entire condition is evaluated, either ligically true or false. There are some other subtleties, but this is the big one. Looking over the manual and wiki again, I agree that this could be made more clear.

Yes, i understand your points. Unfortunately, those sources I mentioned are, in response to your earlier question, all that I know. I dont even remember where I learned most of my ISY programming skills, but i suspect it was a ombintion of all those resources you mentioned. I also assume that the amount of activity on the forums is an indicator that others also find them less-than-comprehensive. Just as likely is that many dont bother to read them at all, so I applaud your hours spent studying this stuff. I find the big thing is to realize that each program condition is also the program trigger. I find the conditions and actions, themselves, to be relatively intuitive. It is in the understanding of what triggers a condition to be evaluated that took a bit of practice. Unfortunately, I doubt that this is much help for you.

I dont know what you have seenor missed. There are quick start guides, user manuals, the wiki, and videos.

DerekN, in retrospect, I wonder if switch B was, in fact, a controller, but the responder level for switch A was somehow set to zero.

I have noticed that some of the insteon devices have a "resume dim" feature. I do not know which switches you have or whether they have such a feature, but I could imagine that enabling this feature could solve your problem. Unfortunately, I have not done much experimenting with this, so I cannot offer a lot of help here.

I agree with jratliff here. There are lots of ways to do it. There are also questions you should probably ask yourself. - do I still want motion to turn the lights on, even when my keypad button is ON? - what do I want to happen when the lights are on and I turn OFF my keypad button? - what do I want to happen when the lights are OFF and I turn ON the keypad button? - is the motion sensor and switch part of a scene together? Depending on answers to questions such as these you could try variations like: if control motion sensor is switched on then turn on light else nothing if status keypad button is off and status motion sensor is off then turn off lights else nothing