TJF1960

I will have to take your word on that, since I dont know the current conditions. Well, this is what happened. I made the changes listed above to this program yesterday. This morning when I turned the whole house fan on it turned back off. I went thru the code line by line and got to the line in question (And $sAlarmSys_Z31_LaudryRm_Door is 0). I checked the door that variable is controlled by and it was open, the admin console reported the variable as “1†which is correct. But in order for this program to be true this line needs to be 0! So I did some fooling around with the program, even re-creating a new program. No matter what I did the program continued to evaluate as true. Until I moved that line in question to above the other variables in parentheses, then the program worked as intended. Very good points. Although no, I haven’t had to force the evaluation. In fact once I moved the line in question up and saved the program the console reported the program as false. I then moved the line back into its original place (as in program 2), saved the program and the console reported the program as true again. I did this a couple of times just to make sure I wasn’t crazy. Each time I moved the line and saved the program the console reported the opposite state. And, just to be clear that line movement was the only change to the program made between saving and checking program status. And the conditions all stayed the exact same between tests. Another good point. As you suggested I removed the action part of the program, then moved the problem line in question down to where it was in program 2, saved and checked the status which had changed from false to true. So the action doesn’t seem to affect this problem. I am bewildered! There has got to be a simple explanation but I don’t know what it is. Thanks, Tim

The first program was the original, before the addition of a sensor. I included this program in the post to show its placement of "And $sAlarmSys_Z31_LaudryRm_Door is 0†(which is the line having trouble with) in reference to the other sensors. The 2nd program was modified from the first to include "$sAlarmSys_Z26_MasterBed_Door is 1" which is the new sensor. Because of the application both "$sAlarmSys_Z26_MasterBed_Door" and "$sAlarmSys_Z06_MasterWindow" were required to be "And" then "Or" as a pair with the other sensors. Hence the inclusion of the OR Parentheses around the two. The parentheses addition and the sensor addition are the only two differences between program 1 and 2. Basically this program is one of a number of programs used to control our whole house fans based on different conditions including temp and door/windows open/closed. Door and window sensors control variables. Variables which = 1 are open, 0 = closed. This particular program is looking for at least one of the first two variables to be closed or the combination of variable 3 and 4 to be closed then it is looking for the 5th variable to be open then finally either the 6th or 7th variable to be open. Once those conditions are met the program evaluates true. The problem I was having and am trying to understand why is the placement of "And $sAlarmSys_Z31_LaudryRm_Door is 0" in programs 2 and 3 is making a difference. Program 2 evaluates true in the admin. console, when it shouldn't based on the current conditions. Then simply moving "And $sAlarmSys_Z31_LaudryRm_Door is 0" up in order as depicted in program three, then saving the program, the admin console shows the program as False, which is, as it should based on the conditions. Thanks, Tim

I have this one program which has been working fine for months. I added a sensor which then required the program to change slightly. The change included adding the additional sensor and another set of parentheses. These 3 programs are all the same the only difference is the placement of “And $sAlarmSys_Z31_LaudryRm_Door is 0†in the program. Also, all of the status of all the sensors and devices were such that the program should have been FALSE. But depending on the placement of the above referenced And statement some of these programs turned true! This is the original program which worked fine and its current state is False per admin console: If Program 'WH Fan Sw Status' is False And-( | Status 'Devices / WH Fan LR' is On | Or Status 'Devices / WH Fan LR Hi/Low' is On -) And-( | $sAlarmSys_Z05_SlidingDoor is 1 | Or $sAlarmSys_Z08_KitchenWindow is 1 | Or $sAlarmSys_Z06_MasterWindow is 1 -) And $sAlarmSys_Z31_LaudryRm_Door is 0 And-( | $sAlarmSys_Z09_LRtoWR_Door is 0 | Or $sAlarmSys_Z11_WRtoBack_Door is 0 -) Then Set Scene 'Scenes / Whole House Fan's / WH Fan LR' Off Else - No Actions - (To add one, press 'Action') This is the same program after the minor changes. It should still be False but the admin console reports it as True: If Program 'WH Fan Sw Status' is False And-( | Status 'Devices / WH Fan LR' is On | Or Status 'Devices / WH Fan LR Hi/Low' is On -) And-( | $sAlarmSys_Z05_SlidingDoor is 1 | Or $sAlarmSys_Z08_KitchenWindow is 1 | Or-( | | $sAlarmSys_Z06_MasterWindow is 1 | | And $sAlarmSys_Z26_MasterBed_Door is 1 | -) -) And $sAlarmSys_Z31_LaudryRm_Door is 0 And-( | $sAlarmSys_Z09_LRtoWR_Door is 0 | Or $sAlarmSys_Z11_WRtoBack_Door is 0 -) Then Set Scene 'Scenes / Whole House Fan's / WH Fan LR' Off Else - No Actions - (To add one, press 'Action') After quite a bit of time I finally found that if I moved the above referenced line up in the program that the program would finally evaluate False as it should: If Program 'WH Fan Sw Status' is False And-( | Status 'Devices / WH Fan LR' is On | Or Status 'Devices / WH Fan LR Hi/Low' is On -) And $sAlarmSys_Z31_LaudryRm_Door is 0 And-( | $sAlarmSys_Z05_SlidingDoor is 1 | Or $sAlarmSys_Z08_KitchenWindow is 1 | Or-( | | $sAlarmSys_Z06_MasterWindow is 1 | | And $sAlarmSys_Z26_MasterBed_Door is 1 | -) -) And-( | $sAlarmSys_Z09_LRtoWR_Door is 0 | Or $sAlarmSys_Z11_WRtoBack_Door is 0 -) Then Set Scene 'Scenes / Whole House Fan's / WH Fan LR' Off Else - No Actions - (To add one, press 'Action') In a nutshell, on my system anyway, it seems that the single And statement placed right after a double set of parentheses gets ignored allowing the program to evaluate true. I even created a new program adding all of the same components in the same order and produced the same results (I was thinking maybe some sort of glitch in the original program). Anyway, this last program works as it should now but I was just curious as to why placement of this one line changes the evaluation like it does? Thanks, Tim

Thanks LeeG, That’s what I wasn’t sure about, if the ISY turned the status of the zone off based on the assumption due to the timeout. Tim

The OP’s sample program takes 6 hours to fully run. If the power was restored at 0400 the program would start then stop at 0601 because the 6 hours were up, thus leaving his Irr – 2 on until the timeout ended in the EZFlora for that zone. One thing I am not sure of is whether the ISY acknowledges the zone time out (entered and saved to EZFlora using ISY console)and then would change the status after the EZFlora timeout. I created this program to test what happens after reboot: If From 11:20:00AM For 1 hour And Status 'Devices / WR1 KPL 1 Ceil Lite' is not On And Module 'Climate' Temperature >= 80 °F Then Set 'Devices / WR1 KPL 1 Ceil Lite' On Send Notification to 'Tim' Else - No Actions - (To add one, press 'Action') After reboot the “Devices/WR1 KPL1 Ceil Lite†turned on and notification was sent. As another test I deleted all of the IF conditions except the time from/for and rebooted. The Light didn’t turn on. The program was true as per the Program Summary page but by itself it didn't execute the program. In order for the program to excute it needs a trigger- other than just the time from/for. Tim

Well, I would think it would run based on my understanding….but I could be wrong….its been known to happen…..After a reboot the ISY evaluates programs. If the power fail/restore occurred within the 6 hour window shouldn’t that program evaluate true and run? Perhaps someone with direct knowledge could chime in. Tim

Unless of course there is a power outage at 12:00AM and lasts longer than the "Missed Schedule Grace Period" time set in the ISY in which case the irrigation program wouldn't run that day. With the "For 6 hours" added in to the code the irrigation should run when power was restored within the 6 hour window. Tim

Hello Michel, Installed 3.1.4 the day it was released - everything went smoothly. However today I noticed my sprinklers hadn't run. We had rain a couple of days ago so I didn't expect them to run until today. After looking into the previous day rain programs I created I found that what used to be " If Rain Today 0.1 inches" now was "0.01" inch, and the same for 0.2" now 0.02" and so on up to 1 inch. In 3.1.3 these programs ran fine. It appears that these values in the programs changed from 1/10 to 1/100 because of the Rain Today enhancements made in 3.1.4? If so then anyone using rain today values should double check their programs. Thanks, Tim

Hi Illusion, Thanks for keeping us updated. It will be interesting to see if the switch starts to ghost on now. Any bets? Tim

I can confirm the code text color change. I was able to print screen in both 3.1.3 and your link Michel but I havent been able to upload the images to this post. I did have some of the same problems with the 2.8.16 console as sanders2222 did but not as bad, not sure why. Running windows 7, and using http://www.universal-devices.com/99i/3.1.3/admin.jnlp - Java application Tim

An app called athome http://forum.universal-devices.com/viewtopic.php?t=4801 works well with the original iPad and iPod Touch, not sure with iPad 2 though, but its worth checking out. Tim

For what its worth it is possible to use a triggerlinc or ms as a controller of a scene (linked to and controller of a SL relay or dimmer) and use the adjust scene in programs to control the on levels and ramp rate when turned on by the ms or triggerlinc. Similar to using adjust scene in programs for local control. Tim

Yes, the ISY writes the local on levels to the dimmer, what you are trying to do should work. Problems with the on/off status in the gui do indicate something is not right. I have found sometimes rebooting the ISY and PLM will clear up strange issues, but aside from that I am sure LeeG or Michel can/will offer further assistance. Tim

To test I just created a new scene with a SL Dimmer as a controller, no other devices are in the scene (although that shouldn't matter). Went back to a program, selected "adjust scene" and that SL Dimmer showed up in the drop down box for "In Scene" whereas that device wasn't an option before it was made a controller in the new scene. I should have asked what platform version for the ISY are you on and what does the ISY report the version is for the dimmer you want to scene adjust? Also, are there any devices showing in the drop down box or just scenes? Tim Edit: I just re-read your first post and see you are on 3.1.2 same as mine. Sorry. What is the version reported of the dimmer?

As I recall the device needs to be in a scene as a controller. Once a scene is created with the device as a controller that device will appear in the drop down box. Then you may select the device as you were correctly trying to do. To power cycle a SL you can just pull the set tab out at the bottom of the rocker switch for 10 or so seconds which removes power from the device. Tim

Andy, Agreed, it is confusing. To expand upon Lee and apostolakisl’s comments try thinking of it this way. Once a wait or repeat is reached in the program any trigger change in the “if†during execution will cause the program to re-evaluate during the wait or repeat. If none of the triggers change after execution has begun then the program will not re-evaluate. A single time schedule in the “if†does not cause automatic re-evaluation by itself because the trigger (1:00pm) didn’t change (its merely waiting for 1:00pm in order to trigger). Tim

Shouldn't the variable be set for 14 in order for the program to run "then" every 15 days?

Andy, Just for clarification is variable “$Cleaning_Day “ an Integer or State variable (guessing Integer)? Thanks, Tim

Along with LeeG's comments you could drop the second program by adding a wait after "Set 'Garage Door Relay' Off" then add it again. If Time is 10:00:00PM And Status 'Garage Door Sensor' is On Then Set 'Garage Door Relay' Off Wait 1 Minute Set 'Garage Door Relay' Off Else - No Actions - (To add one, press 'Action') If the Garage Door Sensor does not turn off by the end of the wait period the second "Set 'Garage Door Relay' Off command will run. If the sensor does turn off within the wait period the program will turn false and not run the second command. Tim

Confirmed on mine as well. Thanks, Tim

I have a slightly different take on it. Since the program is not looking for a “switched Off†from the motion, once it does switch off it will not affect the program – running or not. If at anytime during the “wait†the motion is switched on again or the state of either variable changes (I am assuming the programs are “stateâ€) then the program will re-evaluate immediately. If the condition evaluates true it will start the “then†over again. If it evaluates false the program will stop running and the program will turn false immediately, not completing the “then†section (in other words “Set Scene 'Closet Lights / Closet light Switch' Off†will not occur). Is it possible that during the wait either one of the variable states may be changing which would halt the program? Tim Edit: As far as needing the brackets, I don’t use them unless I am using and/or combo’s and they are absolutely needed. I don’t believe you need them in this program. It has been my experience that having the 3 conditions listed as you have them without the brackets will evaluate anytime any one or more change state, but the “then†should not run unless all 3 “if†conditions are true. In answer to your other question, without brackets the order would be from the top down as far as I understand it.

Hi Chris, Thank you. Just so I understand correctly, Is device query run first to initialize device status then on to step 1 - 5? Thanks, Tim

jca001, I am old school with programs and haven’t done much with variables. As such I have been trying to figure out a program using variables to accomplish the same results as the 3 program examples above (Reboot Away KPL Off, Reboot Away KPL On and Reboot Away KPL Status). It seems to me, at least as far as I can see, it would still require 3 programs + variable. But I do not have the experience with variables as some of you do. I know it would be asking a lot but could you provide example programs and variables to demonstrate how you would replace the 3 programs mentioned? Thanks, Tim

After power is restored to the ISY what is the boot sequence (including Run at Startup commands) and now that variables have been introduced where exactly do they fall in the sequence? Thanks, Tim

aLF, Yes, set the program to “Run at Startup†Yes except, if I followed your original post correctly, you would want to turn the away scene "off" at start up (in your example above). The only problem is if you were home and the power cycled off-on the ISY would still turn the scene Away off even though you are home. If you want the ISY to remember the state of your Away program and scene after a reboot I would suggest the following: Program: Reboot Away KPL Status If Status 'KPL Button' is not On Or Status 'APL ' is not On Then Set Program 'Reboot Away KPL Off Set' To Run At Startup Set Program 'Reboot Away KPL On Set' To Not Run At Startup Else Set Program 'Reboot Away KPL On Set' To Run At Startup Set Program 'Reboot Away KPL Off Set' To Not Run At Startup Program: Reboot Away KPL Off Set If - No Conditions - (To add one, press 'Schedule' or 'Condition') Then Set Scene 'KPL Button and APL' Off Else - No Actions - (To add one, press 'Action') Program: Reboot Away KPL On Set If - No Conditions - (To add one, press 'Schedule' or 'Condition') Then Set Scene 'KPL Button and APL' On Else - No Actions - (To add one, press 'Action') I use these programs for my own Away programs, only I turn "On" the KPL buttons to indicate I am Away, and turn them "Off" when I am home. So I had to reverse the logic in these examples (hope I got them correct). Program: Reboot Email If - No Conditions - (To add one, press 'Schedule' or 'Condition') Then Set Program 'Reboot Email' To Run At Startup Wait 15 seconds Send Notification to 'Tim' Wait 1 minute Run Program 'Reboot Email' (Else Path) Else - No Actions - (To add one, press 'Action') This is the program I use to send notification of a reboot. Remember to initially set this program to "run at reboot." Tim