oberkc

Bbuchanan99, The ELSE path in your program (turning off your keypad scene) will never run. Your condition wil always evaluate TRUE whn triggered. At what point do you want it to turn FALSE?

I do not see how variables will have any impact or relevance to the interaction between the ISY and Axis camera. Variables are mostly used in programs, either as a condition or action. I assume you interract with your camera through the network module and network commands/resources, no?

By having them in a scene, pressing one should cause all to go on/off. Setting the backlight levels to 15/5 can be done via the ISY admin console, choosing the device>settings. Blinking is not an inherent function of insteon and would require a program to accomplish. Is this important? Unfortunately, I cannot help with the Elk integration and things like "double F1" commands. Please clarify your question...are you wanting to create a program which triggers an elk action when any one of the multiple D buttons is toggled ON, and trigger a different elk action when toggled OFF? Is that your question?

User manual and wiki. You have already read the wiki. The user manual is available at the wiki. Beyond that, none that I am aware of. I go back to stusviews observation. The first question I ask is "why" do you want to use variables. Is this, simply, an intellectual challenge, a solution looking for a problem, or is there some task for which you believe variables are the only solution? Other than some pretty extreme stuff, it is my opinion that darn-near everything can be done without variables. Yes, they may make things cleaner and easier to follow at times, but you can do A LOT without them.

it might, if you have nested IF statements. We don't. However, understanding triggers and effect on wait statements, you could accomplish similar logic by: if open then run second program (then path) else nothing second program: if nothing then wait 15 minutes run third program (if path) else nothing third program (disabled) if open then wait 15 minutes notify else nothing

Wholly agree!

Are you asking how to create a variable, or where/why/how one would use a variable? I would expect that the starting point would be to create the variable.

dba62, While I agree with stusviews response (in regards to nested conditions as well whethernthis is a solution to your trigger reverse problem), the ISY does (in my estimation) provide sufficient flexibility and power to program the logic you propose. If you wish to discuss further, let us know. I definitely believe the best solution to a trigger reverse problem is to replace the sensor with one that works as needed for the application.

Rather than "status" as a condition, use "control". If Control "entry door sensor" is turned on Then Same.....

Being in a folder causes, basically, the program to be enabled or disabled, based upon the folder conditions. In your case, the program is essentially enabled at 10pm and disabled at sunrise. Only once enabled will the conditions trigger an evaluation and response. With "status" conditions, only a change of status would trigger an evaluation. So, at between 10 and sunrise, the program is looking for change in status as a trigger. If the status does not change after 10:00, it will never get triggered.

OK. Hopefully, I did not give you bad advice this time. As I asked before, also, make sure your motion sensor is not in any scenes.

Break it into two programs. Program 1 If From 11:00:00PM To Sunrise (next day) And Control 'Driveway Sensor-Sensor' is switched On then run program 2 (then path) else nothing Program 2 if nothing thenThen 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 nothing When one calls a program from another program, one must specify what part of the program to run. In this case, I want it to run the "then" path. (Not the IF path. Not the ELSE path.)

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.