oberkc

That is what I was thinking. It looks as if you have confirmed this. Your test program looks exactly like what you need to do with your lights, except without the random parts. I am glad it works for you.

I am not sure I followed. Two program scheme versus same program? When you say it does not work...care to clarify? How are you sure. I enjoy this kind of problem and it helps me better understand the ISY programming. If you care to post your latest program, I would love to see it.

Let us know how it works for you

Make sure you choose the "then" path Front Bedroom Light A If From Sunset - 30 minutes To 9:00:00PM (same day) Then Repeat 4 times Run Program 'Front Bedroom Light B' (then)<<wait 40 minutes<< Else - No Actions - (To add one, press 'Action') I continue to believe it conceivable that the 40 (or some time) delay is advisable, but that it must be in program A (rather than the 25 minute delay in . Otherwise the program "then" path will run 4 consecutive times immediately, with the second, third, and fourth times starting before the first, second, and third occurrences finish. The reason I say this is that I don't believe that the repeat will wait until the end of program B before starting (repeating) again. Given this understanding, I also don't believe the 25 minute wait in program B will have any effect. If it is mandatory lights out at 10:00, you can always modify the programs to look like this, to be sure: Front Bedroom Light A If From Sunset - 30 minutes To 9:00:00PM (same day) Then Repeat 4 times Run Program 'Front Bedroom Light B' (then path) wait 40 minutes Else - Set 'Front Bedroom Light' Off <<

You may have to add some parentheses: If From Sunset To 10:00:00PM (same day) And ( Status 'Outside-Front Door Lights' is Off Or Status 'Outside-West Side Landscape L' is Off Or Status 'Outside-East Side Landscape L' is Off Or Status 'Outside-Balcony Lights' is Off ) Then Set 'Outside-Front Door Lights' On Set 'Outside-Balcony Lights' On Set 'Outside-West Side Landscape L' On Set 'Outside-East Side Landscape L' On Else - No Actions - (To add one, press 'Action') You may also find some reliability benefits in creating a scene with all four lights as responders and turning the scene on rather than turning four lights on individually.

That is not completely accurate. WAIT (or REPEAT) statements don't CAUSE re-evaluation. Rather, I understand it as returning control of the program to the "if" statement SHOULD the IF conditions change. In your case in the second program, your "if" condition would be evaluated at at two times only: sunset and at 9:00pm. (This is what CAUSES the evaluation). If, by chance, the evaluation occurs during a WAIT or REPEAT statement, then the program will be interrupted. This is true except in the cases where your program steps include WAIT or REPEAT. I now understand why your second program has a 40 minute wait period at the end. I suggest a different approach to your programs: Front Bedroom Light A If From Sunset To 9:00:00PM (same day) Then Repeat 4 times Run Program 'Front Bedroom Light B' (then) Wait 40 minutes Else - No Actions - (To add one, press 'Action') Front Bedroom Light B If Then Wait 20 minutes (Random) Set 'Front Bedroom Light' On Wait 20 minutes (Random) Set 'Front Bedroom Light' Off Else - No Actions - (To add one, press 'Action') The performance of your program would be slightly different, but I suspect in acceptable ways. I think, too, that this will lessen the chance that you will find lights on all night.

Yeah, burning the house down would be bad. But if it (your second program, conditions from sunset to 9:00p) evaluates as false during one of your wait statements, you may exerience a case where the lights fail to go off as expected. If your sunsets are as late as ours in the summer months, you could frequently have a condition where your lights are on, your program is the second "wait" period, and 9:00p occurs. At this time, the second program's conditions would trigger an evaluation, which would cease the program execution before the light is turned off. For that matter, it could happen at any time of the year since you repeat the program up to four times. Do you have your second program "disabled"? Anyhow, if you experience this condition (lights remaining on after you expect them to be off), you may want to look at this as a possibility.

jerlands, I have spent little time in Houston, but is it possible that the period of time between sunset and 9:00pm is less than 40 minutes during certain times of the year? If so, is there a risk that your Front Bedroom Light B program may evaluate as false during the second wait period, causing a failure to turn the light off in extreme random cases? Out of curiousity, why did you include "if" conditions as part of the second program?

One other difference that I see between status and control is the that by using status, you are relying on the device (motion sensor in this case) to control the on, off, and time in-between. By using control, you can simply watch for "on" signals and then use the ISY-99 to control the timing and shutoff. I have the same perception as LeeG which is consistent with your assumptions. The status is based on an ISY-99 maintained table of current status (which can be seen at the admin panel, my lighting). If the ISY recieves an on command from a motion sensor, the status will turn to on and remain so until it recieves an off command from that sensor. That is my understanding Yes, also my understanding It can happen, but if so this typcially indicates a communication problem which needs to be solved. It appeared to me that the ISY has a default program which queried the system every night at 0300 (or something like that). Does yours include such a program? All consistent with my understanding. If the ISY misses the transaction, then this would constitute, in my mind, a communication problem, which should be fixed. If the ISY "misses" things, you will not be happy with the performance of you system. But, you are correct. Scenes will continue to work without the ISY. I believe there is a limit to the number of retries. Perhaps three? I found them neither pointless of imprecise.

There is a discussion in the wiki about the use of motions sensors in the bath: http://www.universal-devices.com/mwiki/index.php?title=ISY-99i/ISY-26_INSTEON:Using_Motion_Sensors_in_Bathrooms There are also several posts about motion sensor programming in the forums. Here are a few examples to look at if you have not already. http://forum.universal-devices.com/viewtopic.php?t=5154&highlight=motion+sensor http://forum.universal-devices.com/viewtopic.php?t=4215&postdays=0&postorder=asc&highlight=motion+sensors&start=30 http://forum.universal-devices.com/viewtopic.php?t=5204&highlight=motion+sensors Your stated requirements are pretty straight-forward, but there are typically complications that arise after further thought. For example, do you want the motion program disabled if you manually turn on the switch? The general approach that I use is as follows (two programs): Motion Program: if time is from 0001 to 0530 (same day) and control motion sensor turned on then run timer program (then path) else Timer Program: if then set bathroom light on wait 15 minutes set bathroom light off else Perhaps if you posted your latest program, it would be nothing more than a simple tweak to get it working.

I can't tell if you are describing how it is, or how you want it to be. I would help if you describe the devices in your current "scene". Is the "kichen" part of that scene? What insteon device directly controls the pendents? What other insteon devices are in that scene and what loads do they directly control. Within that scene, which devices are defined as "controllers"? One option is to create a second scene...the one with just the pendants. This scene could have all the same devices as your kitchen scene, but a different controller. Or you could define different on levels for your kitchen scene, depending on which controller initiates it. For example, if your kitchen scene has two devices (say switch 1 and switch 2) defined as controllers, switch 1 can initiate full bright for all devices in the scene, switch 2 can be set to initiate 50% for pendants and off (or very low, depending on device version) for the rest.

The quick and simple answer is yes. This is also true with "repeat" commands. LeeG offered the standard solution for this "problem".

I recall certain insteon devices which would fail to accept certain settings from the ISY unless power was cycled. Have you tried temporarily shutting off power to the in-linelinc to see if this has any affect?

I will think some more on it. I agree, this is strange behavior. If I come up with some other ideas, I will post back, but I am drawing a blank right now. Another option is to use the insteon IRLinc and keep the ISY where it works. But I agree....I would want to find out what the problem is here.

I am not a reader of those messages, but I wonder if the "Hops Left=0" part is an indication of a device not responding. Just to get the conversation rolling: do you have access points? Are they close to the remotelinc? did you put your remotelinc into linking mode?

Do you have access points or some other means of bridging the legs of your house electrical system? When installed in your living room, what other electronic devices (home theater?) stuff is plugged in along with your ISY?

There are lot's of examples and subtle variations on the motion sensor program. It is definitely worth some time searching them out. In the mean time, make it simple: if control motion sensor is switched on then set light on wait 10 minutes set light off else If your requirements get a bit complicated (different reponse if light is manually turned on), the fine folks around here can discuss other options.

I suspect the reason your program is not working has little to do with KPL toggle or non-toggle. I suspect you need to make some adjustments to your IOLinc. Setting your relay on, waiting 13 seconds, then turning it off will not keep your relay open for thirteen seconds. Furthermore, how your relay responds to on and off commands is part of your IOLinc settings. Then Set 'Outdoor / Gate / Gate Relay' On Wait 13 seconds Set 'Outdoor / Gate / Gate Relay' Off The duration of the length of time the relay stays open is a setting. Whether your IOLinc responds to on, off, or both is part of the settings. Whether your relay is normally opened or normally closed is part of a setting. My suggestion is to open the settings from the ISY-99 admin panel and review them from the wiki: http://www.universal-devices.com/mwiki/index.php?title=ISY-99i/ISY-26_INSTEON:Linking_an_I/O_Linc Pay special attention to the "momentary" versus "latching" modes. How is yours set up? Is it in momentary setting (versus latching). How long is your momentary hold time? If in momentary, is it momentary A, B, or C? I cannot confirm, but if the IOlinc allows momentary hold times of 13 seconds, I would use this option to open your gate. Then, you would have only to send one command (no waits, no second commands) to your IOlinc to open the gate. The command required would depend on whether the setting is momentary A, B, or C. If the settings do not allow a momentary hold time as long as you need, I suggest putting your IOLinc into "latching" mode, and proceeding much as you have already done with your program. (You may find that changing this one setting would cause your existing program to work.) So you have a sensor hooked up to your IOLinc relay? After you check the settings in your IOLinc, and review the meaning of each from the wiki, I am hoping that you could report back if you have further questions about your setup. If so, please let us know how your IOLinc is configured.

Being unsure if the garybixler solution worked for you, perhaps there is an alternative. Given that it appears the the program condition evaluates every time the temperature changes (forcing a restart of programs with a wait condition), I thought that there was an alternative. I am also a fan of folders, so I tend to favor them, even if alternatives exist. Folder condition: If Status 'Living Room / Venstar House' > 71° (Temperature) the run the programs in this folder Program in the folder: if time is 0000 or time is 0100 or time is 0200 or time is 0300 . . . or time is 2300 then Set 'Living Room / Venstar House' Fan On Wait 10 minute Set 'Living Room / Venstar House' Fan Auto //turn fan off else While it is not quite as elegant, taking the temperature out of the program conditions will avoid the re-triggering of the program every time the temperature changes a degree.

Indeed! I would add this to my first program. if time from sunset to sunrise (next day) And Status 'EntryLightsEast' is not On And Status 'EntryLightsWest' is not On And Control Motion Sensor switched on <<<<<<then Set Scene 'FrontPorchControl' On Wait timeout period Set Scene 'frontPorchControl' off else But I like kingwr solution just as well.

Based on what I have read at places like this, I understand that some insteon devices are limited in capability such that they cannot be used as controllers. (Perhaps they don't broadcast status?) This includes certain lamplincs and appliancelincs. I would not be surprised if the outletlinc is such a device. If so, I assume status or control from such devices cannot be used as a program condition, either. If you want to perform a quick test, open the event viewer, then manually activate your outletlinc. If you see communication traffic, you may be OK. If not, I suspect you may not be able to do what you want.

That is quite the complicated web of programs there. It seems overly so, to me. What is the EntryLightControlStatus used for? This is your folder condition? Which programs are in this folder? You appear to have two entry lights (east and west). Do you want to disable the motion program if a SPECIFIC (east? west?) one is on, EITHER are on, or only if BOTH are on? If one light is on manually, how do you want this to affect motion control of the other? If both lights are on as a result of motion, and you manually activate only one switch, how do you want this to affect the automatic off of the second switch? If both lights are to remain on, are you willing to manually turn off two switches or do you want a single switch control of both lights? What devices are in your "frontporchcontrol" scene and which of these are controllers? Writing without fully understanding your requirements, why not take advantage of the oft-maligned feature that stops programs from executing when there is a change in entry conditions: Program 1 if time from sunset to sunrise (next day) And Status 'EntryLightsEast' is not On And Status 'EntryLightsWest' is not On then Set Scene 'FrontPorchControl' On Wait timeout period Set Scene 'frontPorchControl' off else This program would not execute if either a) during the day or if EITHER of the entry lights are on. Furthermore, if (after the scene is turned on and during the wait period) EITHER of the entry lights are turned on manually, the execution will stop and BOTH lights will remain on until both are turned off manually. The problem I foresee with this is the potential that sunrise occurs during a wait period. If so, the lights will remain on. To counter this possibility, I would add a second program: if time is sunrise then Set Scene 'frontPorchControl' off What am I missing?

Don't worry about the Beta versions. Get the latest, I say.

Nice!

Yup. Just take care to use the correct connections on the ISY-99. "network" connection goes to router. "Port A" goes to PLM.