stusviews

If the program is enabled when the conditions are met, then it will run.

If you enabled the program when you were within range of the MS, then the 2nd program may run. BTW, did the THEN or ELSE execute?

There is no option to bypass (or save) login credentials. This is done for security.

Post your program. Explain what each label represents.

Right click on My Programs to initiate a search (Find/Replace).

Here's a link to the manual if that's what you're missing.

Sometimes the simplest solutions are the most elusive

Here's the entire statement: Statement Execution OrderWithin the Then or Else clause of a program, statements are executed from top to bottom in the order in which they occur. When a statement calls another program, the called program begins executing, and the calling program immediately continues execution with the next statement in sequence--it does not wait for the called program to complete before continuing. A series of statements within a Then clause (or within an Else clause), up to the next Wait or Repeat statement, are atomic. In other words, all such statements are executed before the conditions of the program are retested. The program's conditions are reevaluated each time a Wait or Repeat statement is encountered, and at the end of each iteration of a Repeat loop. What this means is that if a program's Then clause changes a condition which causes the program's overall condition to become false (or if the program's Else clause changes a condition which causes the program's overall condition to become true), the current atomic statement group will complete, and at that point execution will transfer from the Then clause (or the Else clause) to the Else clause (or the Then clause). Therefore, if a Then clause (or an Else clause) contains no Wait or Repeat statements, the entire clause is atomic, and will complete before the program's conditions are reevaluated. Thus, a Wait or Repeat will execute as expected unless a statement prior to the Wait or Repeat caused to value of the condition(s) to change.

shadowb, The ISY has a different construct for the situation you proposed, that is A is turned On and then B is turned On. Because each press occurs in an instant, two different button presses occurring simultaneously is virtually not possible. Also, the ISY does not have nested IFs, for example, IF A is turned On, then IF B is turned On doesn't exist because THEN cannot contain a condition. Using "Status" is one approach. If Status A is ON And Status B is ON depends on both A and B being on concurrently. The order in which the devices are turned on doesn't matter, only that both devices are on AND at least one device changed from OFF to ON. Another, more complex method requires multiple programs: Prog1 If Control A is switched ON Or Control B is switched ON Then Run 'Prog2' Prog2 B (disabled, only running Prog1 will cause this program to run) If Control A is switched ON Or Control B is switched ON And (Status A is ON Or Status b is ON ) Then .... There are bunches of more complex methods including using variables that analyze the state of each device, perform multiple tests, etc.

Nope. "A series of statements within a Then clause (or within an Else clause), up to the next Wait or Repeat statement, are atomic. In other words, all such statements are executed before the conditions of the program are retested. The program's conditions are reevaluated each time a Wait or Repeat statement is encountered, and at the end of each iteration of a Repeat loop."

Compound statements include one or more AND or OR conditions. Do you mean nested IF statements?

From the Wiki: "What this means [wrt/Wait or Repeat] is that if a program's Then clause changes a condition which causes the program's overall condition to become false (or if the program's Else clause changes a condition which causes the program's overall condition to become true), the current atomic statement group will complete, and at that point execution will transfer from the Then clause (or the Else clause) to the Else clause (or the Then clause)." Program conditions are usually evaluated as soon as a change occurs unless there's a Wait or Repeat at the end of which the program conditions are evaluated. But, that's only for statements following the Wait or Repeat clause. In you original example, there are no statements following the Wait, so the program will terminate at the end of the Wait duration and will not be evaluated again (until the next trigger).

Do you have a particular situation where order matters?

If you assigned a port for the ISY, then use http://your.isy.ip.address:port/admin.jnlp

The statement will be true at 0600am. Run 'program_name' will re-evaluate the condition(s). The only thing a Wait statement does is bide time until the interval has elapsed, then the program will continue. If no statements follow the wait, then the program will terminate.

If Control 'Keypad-Peter - A' is switched Off Or Control 'Keypad-Peter - A' is switched On <-- add this statement

The program runs as soon as the conditions are true and stops when it's done or the conditions become false, whichever occurs first.

No. At the end of the interval the program will terminate.

If Time is 10:00:00PM And Status 'Garage 1 Sensor' is On <--- This checks if the garage door is open Then Set 'Garage 1 Relay' On <--- This trips the momentary contact relay Else - No Actions - (To add one, press 'Action')

The air gap is just that. Pulling it out creates a space (air) between to contacts. It can be pulled almost entirely out while still maintaining minimal contact. It's important to pull the air gap out so that the detent is engaged.

The only LED bulbs I've ever experienced flicker with are dimmables on a dimmer. Non-dimmable bulbs on a relay/on-off device have never flickered.

To set the program status colors, right click on Programs, select Status Icons

Finally, something to watch on a watch while on-watch

This hot water heater controller will apply power when power is restored--even if it was turned off prior to losing power. I fully agree that having the ApplianceLinc to default to On was not a good idea. But, I can definitely think of some uses for that behavior. BTW, the ApplianceLinc Owner's Manual does state that the device will return to the On state if power is removed Restoring Power to ApplianceLinc ApplianceLinc stores all of its settings in non-volatile memory, even when unplugged. In the event of a power loss, ApplianceLinc will automatically return the device/lamp being controlled to the on/off position it had before the power was interrupted. Similarly, if ApplianceLinc is plugged into an outlet controlled by a wall switch and you turn the switch off, ApplianceLinc will turn the device/lamp back on to its prior on/off position when you turn the wall switch back on.

That's a wonderful find. Thanks for the effort and report.