bmercier

Hi Johnny, I woulld also add that it's better to avoid disabling/enabling programs within programs, especially if they are to run frequently. Each time, this writes to the nvram in the ISY. It would be better to catch it with variables, as this stays in memory, and does not write to nvram (unless you also change the init value). Benoit.

It's not a good idea to combine status and control conditions in the same program. I have played with this a lot, just to find out that control and status generates 2 different events if they relate to the same device. You first get an event for the control, the if is evaluated and the program runs accordingly. Then, the status change, cancels the program and retriggers the evaluation. The status is always the second event (no matter if it's a on, Fast on, etc), and the controls always evaluate to false, because the event is the status change. Perhaps this behavior has changed in recent firmwares, as apostolakisl suggest, but this was like that not so long ago. So for my own needs, I wanted to have different behavior for a Fast On, and a "normal" On (no matter how it was turned on). So I used a program triggered on a Fast On that sets a variable. Then, from a status change I can also check the variable, so I know it comes from the Fast On, or not. Benoit.

Look at this post from nstein. It allows to have your web page on another web server, and pass the rest requests to ISY and pass the user/pw at the same time. viewtopic.php?f=63&t=v6729&start=15 Benoit

jtara, I did not know roomie. That's great, I will look into that as well. The only thing I see is that someone could manually turn your scientific atlanta on or off, and it would break the state info. You could add a synchrolinc to your box, and know for sure if it is powered on or off. Thanks for sharing! Benoit.

As others have said, you need to have all of your lights listed in the If section. However, you can shorten your list by listing them only once, using this approach. Program Giant_If If Status 'RC / Cuisine' is On Or Status 'RC / Luminaire SAD' is On Or Status 'RC / Spot salon' is On ..... Then - No Actions - (To add one, press 'Action') Else - No Actions - (To add one, press 'Action') If Program 'Giant_If' is False Or Program 'Giant_If' is True Then ... This will run whenever there is any change of status of your lights listed in the Giant_If... Else - No Actions - (To add one, press 'Action') Benoit.

Hi Stealle, A nice thing to do for a "movie scene" is to use a synchrolinc on the TV which detects if it is turned on or off. As an example, when the TV is turned on in the everning, I use it to turn off the front lights and Dim the back lights to 18%, just enough to see the remote. When I turn off the TV, all lights in the room get to 50%. I also have a remotelinc to override this if need be. Now, a scene or a program? Depends. If the you only want your lights to follow the TV On & Off, scenes is the way to go. However, if you want to add any conditions, you need programs. An obvious one... you probably don't want the lights to turn on during day time. Therefore, you need programs. Let us know what you would like to achieve more specifically, and we can help. Benoit.

No, there can be only one instance. If you run this program from another program, it will be stopped and restarted, and run the then or else based on how you start it (runif, runthen or runelse). Then, at 7am or 12am, program if clause will be reevaluated, and then or else will run accordingly. Benoit

That's what I though. Thanks for the quick response! Benoit.

Hi, Is this a bad practice to play with the program enable/disable? Sometime, I would like the status event to be ignored. Instead of using variable, I was wondering if I can simply disable/re-enable programs like in the example below. Or if I should avoid it for some reason. Example: PROGRAM-1 If Control 'RC / Cuisine' is switched Fast On Then Wait 5 minutes Disable Program 'PROGRAM-2' Set 'RC / Cuisine' Off Enable Program 'PROGRAM-2' PROGRAM-2 If Status 'RC / Cuisine' is Off Then ... ... Actually, my concern is that if this setting gets written to nvram, then I probably want to avoid it as I don't want to keep writing to it. Thanks, Benoit.

I wanted to do the same thing, but due to city regulations, I can only water during odd days. Odd addressed can water during Odd days, and Even adresses during even days. So, if that can be useful to someone, here's what I did. This program runs daily: If Time is 12:02:00AM Then $iDayOfMonth += 1 $iDayOfMonth Init To $iDayOfMonth $iDayOfMonthDiv2 = $iDayOfMonth $iDayOfMonthDiv2 /= 2 $iDayOfMonthDiv2 *= 2 Run Program 'SetDoMOdd' (If) Else - No Actions - (To add one, press 'Action') If the day = day/2*2, then it's not an Odd day: If $iDayOfMonthDiv2 is $iDayOfMonth Then $sDoMOdd = 0 Else $sDoMOdd = 1 But we need to restart correctly at the beginning of each month. If Time is 12:01:00AM on 2011/09/01 Or Time is 12:01:00AM on 2011/10/01 Or Time is 12:01:00AM on 2011/11/01 Then $iDayOfMonth = 0 $iDayOfMonth Init To 0 Else - No Actions - (To add one, press 'Action') For now, this is not ideal as we need to hardcode the next few months, but that allowed me to get going for the fall. Perhaps eventually we will be able to extract the Day of the month in a variable, or set a schedule for every xth day of a month. Benoit.

Hi, Since pretty much day one (4-5 month ago), my ISY-99 just freezes after a few days operating. It needs to be reset once in a while. When it freezes: - HTTP does not respond - Telnet does not respond - No programs gets activated. - Does not responds to ELK lighting. - Ping DOES respond I don't have, at least initially, I did not have any sophisticated rules. All that I can think of is that integration with Elk was done almost day one. Perhaps it has something to do. I have upgrade firmware to 3.1.6, and still same issue. I don't have a UPS to plug it in, but I figure that if I can ping, it's not a power issue. What can it be? Thanks, Benoit