Hi,

Quick question related to programs. I am trying to initiate a program when a switch (in this case an I3 paddle) has changed (I don't care what has changed - anything will do).

When I look at the "If" options for a control (namely the I3 paddle) - there is a multitude of possibilities (on/off/fast on/fast off/fade up/fade down ....yada yada yada). Is there anything in the "if" option testing a control just to ask "if this control did anything"? - so therefore reducing (or eliminating) a multitude of "or" statements?

This becomes particularly apparent/inefficient when I am trying to perform this set of tests across three switches - so I have 9 "or" statements for each switch - so 27 or statements in the program - I come from a programming background (not this kind) and having this many "or" statements was a little silly (usually there were single line alternatives).

Not that I know of. I'd look for control on and control off events (with Or statements).

I dont have an I3, but this two line condition should accomplish what you want (assume its available for an i3).

If

'Garage Sink' is not switched Off

Or 'Garage Sink' is switched Off

@SMonk this could become an issue with a looping program. I'd suggest something like @dbwarner5 has or even a status check.

"device" Status is not "Off"

Then you could also have a: "device" Status is not "On"

The loop comes into play for your other program. What are you trying to do when this device status changes? You might be creating more problems than it's worth.

Remember that "Control" = "Switched" = physical operation of the device (i.e. not a program or controller operating the device). If you're going for something for only when the device is physically adjusted then you would need to use the control option and you would potentially need to account for each control option. Otherwise, you would be able to use status and could use the "ON" or "Off" status and then the "Not" "on"/"off" or even < > options.

Just depends on what you're ultimately trying to accomplish with the other side of this program. What have you attempted so far (that might not be working)?

Please share the programs - RIGHT CLICK on the program and select "COPY to Clipboard" (last menu option - be sure you select "COPY to clipboard" - NOT export!) then paste as text into your reply.

5 hours ago, SMonk said:

Hi,

Quick question related to programs. I am trying to initiate a program when a switch (in this case an I3 paddle) has changed (I don't care what has changed - anything will do).

When I look at the "If" options for a control (namely the I3 paddle) - there is a multitude of possibilities (on/off/fast on/fast off/fade up/fade down ....yada yada yada). Is there anything in the "if" option testing a control just to ask "if this control did anything"? - so therefore reducing (or eliminating) a multitude of "or" statements?

This becomes particularly apparent/inefficient when I am trying to perform this set of tests across three switches - so I have 9 "or" statements for each switch - so 27 or statements in the program - I come from a programming background (not this kind) and having this many "or" statements was a little silly (usually there were single line alternatives).

@SMonk , this all depends on how fine you want to slice this onion...

If you want to detect state changes then @dbwarner5 advice will perform well. For the ON state this will catch:

• Standard on (to preset level)

• Additional button press (to 100% level

• Fast ON

It will not catch fade up (or analogous fade down). While these are rare, I do have guests that regularly tap and hold switches to brighten lights.

After many years I have given up on educating family/friends on proper dimmer usage and have incorporated fade up/down in my programming.

To be fair, they have acquiesced on a multitude of my failings... Fair is fair

4 hours ago, dbwarner5 said:

I dont have an I3, but this two line condition should accomplish what you want (assume its available for an i3).

If

'Garage Sink' is not switched Off

Or 'Garage Sink' is switched Off

Ok - perfect - that is much simpler. Will incorporate this knowledge. I could potentially then also incorporate tests about "state" - thanks all.

49 minutes ago, IndyMike said:

@SMonk , this all depends on how fine you want to slice this onion...

If you want to detect state changes then @dbwarner5 advice will perform well. For the ON state this will catch:

• Standard on (to preset level)

• Additional button press (to 100% level

• Fast ON

It will not catch fade up (or analogous fade down). While these are rare, I do have guests that regularly tap and hold switches to brighten lights.

After many years I have given up on educating family/friends on proper dimmer usage and have incorporated fade up/down in my programming.

To be fair, they have acquiesced on a multitude of my failings... Fair is fair

Interesting on the using the switches to dim the lights - are we not supposed to do that? I do it all the time in one of our rooms - curious about what the alternative might be?

9 minutes ago, SMonk said:

Interesting on the using the switches to dim the lights - are we not supposed to do that? I do it all the time in one of our rooms - curious about what the alternative might be?

It's simply difficult to detect with a program. You have to add specific tests (triggers) for Fade Up/Fade Down. I don't happen to use the feature, but many of my family members do. I've been out-voted (even though I've declared our household a Monarchy).

3 minutes ago, IndyMike said:

It's simply difficult to detect with a program. You have to add specific tests (triggers) for Fade Up/Fade Down. I don't happen to use the feature, but many of my family members do. I've been out-voted (even though I've declared our household a Monarchy).

Ah yes - I have a similar monarchy at my house. Appears I am at the bottom of the totem pole - and that includes the dog…..

Again, I dont have an i3, but for some ideas for you, the traditional Insteon paddle switch has lots of options, both built in and via programming. All of them can become triggers via control or state, depending on what you are trying to accomplish

Built in:

1) On: single tap on top to turn to preset on level and ramp rate

2) On when on: ramps to 100% from preset level

3) Fast On: double tap on top to turn to 100% instantly

4) Off: single tap on bottom to turn off at preset ramp rate

5) Fast Off: double tap on bottom to turn off instantly.

6) Press and hold on: Ramps up slowly

7) Press and hold off: Ramps down slowly

Via Programming

1) On when On at less than 100%: When light is not off, not at 100% and on is pressed

2) On when at 100%: When light is at 100% and on is pressed once

3) Fast On when On at less than 100%: Double tap on when light is not at zero and not at 100%

4) Fast On when at 100%: when light is at 100% and a double on is pressed

5) Off when off: Off press when light is at zero

6) Off when at on at less than 100%: when light is not at 100% and not zero, off is pressed

7) Off when light is at 100%: when light is at 100% and off is pressed

8) Fast Off when off: double tap off when light is at zero

9) Fast Off when on at less than 100%

10) Fast Off when at 100%

These can get VERY CONVOLUTED, but they are all options. I have a simpler version of just on when at 100% in my basement game area, where each light changes the whole basement to a scene that corresponds to that switch / game (ie pingpong, pool, darts etc). Also the bottom switch at the stairs, I have an off when off that turns on the stair lights and then after a delay turns off all the basement lights.

WARNING. we have guest bedrooms there as well so I needed to add a trigger variable to the folder that enables these programs as it really can confuse guests!