Chris Jahn

As MikeB and Sub-Routine have suggested, it looks like the link to your fan was not created using the ISY. The simplest way to see if the ISY is receiving status changes is to open the new Event Viewer. As events occur, they appear in the viewer. What you would be looking for in this case is ST, indicating a status change.

I should have also mentioned that you can do a non-conditional sequence such as the following: On Mon/Wed/Fri, do E1 at 8:00pm, E2 at 8:11pm, E3 at 8:22pm If On Mon, Wed, Fri Time is 8:00:00PM Then Send X10 'E1/On (3)' Wait 10 minutes Send X10 'E1/Off (11)' Wait 1 minute Send X10 'E2/On (3)' Wait 10 minutes Send X10 'E2/Off (11)' Wait 1 minute Send X10 'E3/On (3)' Wait 10 minutes Send X10 'E3/Off (11)' Else - No Actions - (To add one, press 'Action')

The ISY is designed to have many small programs, and thus having one per zone is the way to go for this. I'm not sure how a sequence would work better because you would still have to schedule each zone anyway, and thus it would be one big program vs 12 small ones. An advantage of having the 12 programs is that in the Program Summary screen you can see the Last time each individual zone ran (and the Next time as of version 2.6.5). You can also easily enable/disable individual zones if necessary from that screen. To organize the 12 programs, I would create a 'Sprinkler' folder and put all 12 programs in there. You could then use Folder Conditions as a means of controlling whether they are enabled/disabled as a group.

Here's a few answers ... Yes, each program will be run. There is no chance for a "collision" here, although you cannot determine the order in which they will run. The ISY waits its turn, and sends out commands only when there is no Insteon traffic. Of course that doesn't prevent someone from hitting a switch a split second after the ISY has issued an Insteon command. ISY does retries for long running commands such as Restore Device, adding a device to a scene, crawling the network etc.. For simple Insteon commands issued by programs, or simple on/off etc. commands from the Admin Console there are no retries.

The simplest way to handle this is to use the current status of the bedroom fan as your condition. In this example, if the fan ever exceeds 45% then it will be reset to 45% 15 minutes later (regardless of what switch or other control was used to set it above 45% in the first place). I would also suggest you set this program to 'Run at Restart' when you upgrade to 2.6.5 or higher (do not use the current 'Run at Reboot' for this). If Status 'Bedroom Fan' > 45% Then Wait 15 minutes Set 'Bedroom Fan' 45% Else - No Actions - (To add one, press 'Action')

This following problem has been fixed in release 2.6.5 Here is the program in question: If From Sunset - 1 hour To Sunrise + 1 hour (next day) And Status 'Rec Room Stairs Top' is Off And ( Control 'Rec Room Theater Front' is switched Off Or Control 'Rec Room Theater Front' is switched Fast Off Or Control 'Rec Room Theater Front' is switched Fade Down ) Then Set Scene 'Rec Room Stairs 3-way' Fade Up Wait 5 seconds Set Scene 'Rec Room Stairs 3-way' Fade Stop Else - No Actions - (To add one, press 'Action') I've tested the sunset/sunrise (next day) and have found no problems apart from the following one (which was pointed out to me by a few people on the forum). When you save the program, the initial setting for the schedule is based on the current day. This is a problem on the first day only, and only if the start time of a schedule is the previous day (or earlier) and the end time is the current day (or later). For example, If you save the program on Thursday 11:30PM, the initial schedule will be: sunset - 1 hour on Thursday to sunrise + 1 hour on Friday but if, for example, you save the program on Friday 12:05AM (i.e. 35 minutes later), the initial schedule will be: sunset - 1 hour on Friday to sunrise + 1 hour on Saturday Therefore in the second example, the schedule doesn't kick-in until Friday evening. We may be able to fix this bug in this release, but no guarantees. Please let me know if you are experiencing a bug other than what I have described here.

Bernhard, Looks like you practically did it with your pseudo code ... All you need to do is go to the program details screen and create one program per zone. Here are two programs matching the ones in your post. If On Mon, Wed, Fri Time is 8:00:00PM Then Send X10 'E1/On (3)' Wait 10 minutes Send X10 'E1/Off (11)' Else - No Actions - (To add one, press 'Action') If On Tue, Thu Time is 8:00:00PM Then Send X10 'E2/On (3)' Wait 15 minutes Send X10 'E2/Off (11)' Else - No Actions - (To add one, press 'Action')

I can see the need for a defined order, unfortunately its not an easy fix. I'm not sure if it will make it into this release.

No!! I see what you are getting at ... there is no predefined order for running programs running at startup. In the configuration screen you can specify if you want schedules to catchup: -- If selected then all programs are caught up from the beginning of the day. -- If it is not selected then they are run based on the grace period specified. The grace period is also used for upcoming schedules as well and is only used for 'Time is' entries.

The ISY queries all devices at startup, during this time no programs run. When the query is finished, the 'Run At Startup' programs run, followed by any programs that were triggered/scheduled to run. There was a change in 2.6.4 such that "Run At Reboot" is now "Run At Startup", and, more importantly it does a Run (If) now, instead of a Run Then. In the program summary, you can look at the last run time and Status to determine which programs ran when, and which path they took (Then path for Status=True, Else path for Status=False).

RatRanch, I've added it, it will be in the next drop.

Not quite correct, the grace period is only used for Time is entries, not From/To or From/For.

brobin, Not sure why it would have worked, unless maybe your C and D conditions where never True, or it just so happened that A was always True when C and/or D were True.

Yes 'Repeat Every 0 seconds' loops like you would expect; it loops until the program is stopped, or the Then or Else is run again. Not sure why you are using the (Random) option here for your two seconds. Yes, looks good.

Illusion, Yes, you need parenthesis, basically 'ANDs' are grouped together A or B or C and D is the same as A or B or (C and D) What I think you want is (A or B or C) and D

mccrean, This bug was identified in another forum, here's the link: http://forum.universal-devices.com/viewtopic.php?t=1189

You can experiment a bit, either using multiple Dim actions, or Fade Down/Fade Stop. Here's a couple of examples that do roughly the same thing: If IR 'All Off' is Pressed Then Set Scene 'My Lighting' Dim Set Scene 'My Lighting' Dim Set Scene 'My Lighting' Dim Set Scene 'My Lighting' Dim Wait 15 seconds Set Scene 'My Lighting' Off Else - No Actions - (To add one, press 'Action') If Control '08.55.40.1' is switched Off Then Set Scene 'My Lighting' Fade Down Wait 2 seconds Set Scene 'My Lighting' Fade Stop Wait 15 seconds Set Scene 'My Lighting' Off Else - No Actions - (To add one, press 'Action')

Yes, using Fade Stop is required, and is the key for doing brighten/dim. Note that in our programs, Held means Press&Hold Here are the programs, using four IR Buttons named 'Brighten','Dim','Light On','Light Off' Program: Brighten all lights If IR 'Brighten' is Held And IR 'Brighten' is not Released Then Set Scene 'My Lighting' Fade Up Else Set Scene 'My Lighting' Fade Stop Program: Dim all lights If IR 'Dim' is Held And IR 'Dim' is not Released Then Set Scene 'My Lighting' Fade Down Else Set Scene 'My Lighting' Fade Stop Program: Turn Lights On or Off If IR 'Light On' is Pressed And IR 'Light Off' is not Pressed Then Set Scene 'My Lighting' On Else Set Scene 'My Lighting' Off

For two button operation, you can use these programs to dim/brighten, and to toggle the lights on/off: Program: Fade Up all lights If IR 'TV : Channel +' is Held And IR 'TV : Channel +' is not Released Then Set Scene 'My Lighting' Fade Up Else Set Scene 'My Lighting' Fade Stop Program: Fade Down all lights If IR 'TV : Channel -' is Held And IR 'TV : Channel -' is not Released Then Set Scene 'My Lighting' Fade Down Else Set Scene 'My Lighting' Fade Stop Program: Toggle all lights on/off If IR 'TV : Channel +' is Pressed And IR 'TV : Channel -' is not Pressed Then Set Scene 'My Lighting' On Else Set Scene 'My Lighting' Off

As Darrell mentioned, using the ISY in this way should never be considered as a replacement of a medic/emergency alert system, but instead only to supplement it for the son's peace of mind. Having said that, the safest way to use it would for it to be proactive, basically, sending a notification when things are fine. By doing it this way, the abscence of a notification indicates there is something wrong (or a false alarm because the ISY couldn't send the notification for some reason). To answer your question, yes, you can have a program X listen for certain controls in the house, and have program Y run based on the last run time of program X + some amount of time.

You can't do that directly, but you could instead do the reverse ... change your set time to the earliest time, and have the program(s) either run at that time, or wait until the appropriate time.

Thanks for the detailed explanations and examples, it may help in finding the bug or misunderstanding (I'm not sure which one it is yet!) Assuming its a bug, I'm not sure if we'll have a fix for it in this release.

You are correct, it does not make a difference. Just so there is no confusion, moving the schedule condition to the top of the IF is not required. In general, schedule entries can be placed anywhere just like any other condition in the IF, including within parentheses.

Here is the program in question: If From Sunset - 1 hour To Sunrise + 1 hour (next day) And Status 'Rec Room Stairs Top' is Off And ( Control 'Rec Room Theater Front' is switched Off Or Control 'Rec Room Theater Front' is switched Fast Off Or Control 'Rec Room Theater Front' is switched Fade Down ) Then Set Scene 'Rec Room Stairs 3-way' Fade Up Wait 5 seconds Set Scene 'Rec Room Stairs 3-way' Fade Stop Else - No Actions - (To add one, press 'Action') I've tested the sunset/sunrise (next day) and have found no problems apart from the following one (which was pointed out to me by a few people on the forum). When you save the program, the initial setting for the schedule is based on the current day. This is a problem on the first day only, and only if the start time of a schedule is the previous day (or earlier) and the end time is the current day (or later). For example, If you save the program on Thursday 11:30PM, the initial schedule will be: sunset - 1 hour on Thursday to sunrise + 1 hour on Friday but if, for example, you save the program on Friday 12:05AM (i.e. 35 minutes later), the initial schedule will be: sunset - 1 hour on Friday to sunrise + 1 hour on Saturday Therefore in the second example, the schedule doesn't kick-in until Friday evening. We may be able to fix this bug in this release, but no guarantees. Please let me know if you are experiencing a bug other than what I have described here.

To fix your problem, remove 'Deck Spot Status' from the Folder because it doesn't need to be controlled by the Folder conditions anyway. As for why it isn't working, I'd have to see the exact Folder conditions and see if I can recreate the problem. You are correct in assuming that if the Folder enables programs to run at 10:00PM, then your 'Deck Spots Status' program should run at 10:01PM if 'Deck Spots' is not On.