TJF1960

Lee, thanks very much for the excellent explanation. I think at this point I will side with caution as I would much rather be safe than sorry. I will stick with automatic. Thanks again, Tim

I believe I have read in these forums that the recommended setting of “Link Management>Advanced Options†was “Automatic: ISY tries to find the most suitable messaging option†which I have had mine set for, forever. In the past when I have had the Event Viewer open and was either restoring or adding new devices I have always seen “using engine version i1. I don’t ever remember seeing version i2 on any of my SL, KPL’s etc (all are 2 years old or newer and purchased from SH). I was in a play full mood this evening and thought I would switch to “Device Reported: ISY uses the device reported messaging option†which I did and the busy hour glass came up immediately and the event viewer showed “writing 0 bytes to all devices.†Afterwards I restored a 8 button kpl which only took 30 seconds and the event viewer showed using i2. I switched back to automatic mode and restored the same kpl which took 1.5 minutes and the viewer showed i1. I couldn’t believe it, using i2 shaved 1 minute off of the restore. I remember waiting 5-10 minutes for some kpl’s to restore, it would have been so much quicker if i2 were used. All of my devices have been added with this selection in Automatic. And the devices have been added using “Link Management>New Insteon Device†using the address and auto discover. So my questions are: Am I doing something wrong? What is the preferred setting for linking/restoring normal Insteon products like SL, KPL’s etc.? Does it matter which setting it was in when the devices were first linked to the ISY? In other words did the devices add correctly even though i2 was not used when they were linked? I am on v3.1.6 Thanks, Tim

3 more questions for UDI about the reboot process. Is query of devices ran before step 1? At what point in the steps would DSCLink/WCLink data be accepted by the ISY? Now that we are at v3.1.6 have any of the above steps changed? Thanks, Tim

Hello ericdhvac, It sounds like your ms is linked directly to your bathroom light switch (SL?). If that is not the case then LeeG’s suggestion is the way to go. If however your ms is directly linked to the switchlink then the direct answer to your question is that you cannot program the sensor/ISY to disregard motion during specific times. However you can use a feature in the ISY called "Scene Adjust" in programs in which you can program the ISY to change the on/off levels of the ISY/Switchlink when motion is detected. For instance: If From 12:00:00AM To 6:00:00AM (same day) Then In Scene 'Bathroom Light' Set 'Bathroom Light' 15% (On Level) Else In Scene 'Bathroom Light' Set 'Bathroom Light' 100% (On Level) At 12AM this program will become true and run the “then†and adjust your light to turn on at 15% when the ms detects motion. At 6:00:01AM this program will become false and run the “else†which will adjust your lights to turn on to 80% with the ms. The effect will be from 12am to 6am when the ms detects motion the light will turn on to 15%, any other time outside of those hours the light will turn on to 80% when motion is detected. While the local on/off levels (local meaning when you physically turn the switch on) will be whatever it is set to. In other words the local on level is still independent of the levels the ms is set to. I am a little unclear about this statement “I currently have my hall bathroom light programmed to dim to 15% at 12am until 6am same day repeating this command every 5min., this works fine.†But it sounds like you will not need this program any longer (which should free up some resources as well as cut down on powerline transmission). Tim

Hi egads, Personally, anytime I purchase new or used Insteon devices I factory restore the device then add it into the ISY via “Link Management>New Insteon Device†and type in the address and Name and select “Auto Discover†and “Remove Existing Links.†It’s my feeling most people here do the same. Doing it this way you know that there are no previous links left in the device that can cause problems down the road. There are a few devices you must select the actual device from the drop down list for such as rf devices and Simplehomenet devices (if I remember correctly). But for the most part using “Auto Discover†is the way to go. You bet, it is very easy to upgrade to pro if you need to. You select “Help>Purchase Modules†then purchase the upgrade then UDI will take care of it via the internet! Tim

No problem! Addressing your original issue, it sounds like the admin console on the mac may not be updating properly. Question - when you turn a device on locally (toggle push or what ever) does the console update and show that device as turned on or off? If not someone with airport extreme experience will have to chime in. Tim

They won't be. Add "Set scene 'outside lights' Off" to the Else section of that program then they should turn off at sunrise.

Hello egads, While I may not be able to help you directly it will help to know what model ISY you have and what version is loaded into it "Help>About." Also what method you are using to access the admin. console (IE8 etc.) and what address you use (http://youripaddress etc). Tim

I was able to confirm being able use a program to dim a SL LED (running v3.1.5, note v3.1.4 didn’t but that was fixed in this rev) and the values were: 0% = full brightness 1% = off 100% = seems much dimmer than 100% Adjusting from the admin console: 0 = full bright 1 = off 255 = less than full bright but equals 100% from above The values for dimming via direct or programs seem to be equal to each other, although not quite scaled right. Tim

As a simple test just create a program to repeat beep every couple of seconds, run Then on that program and then go to the kpl and verify that is the noise you are hearing when power is applied or the set button is released. Tim

Ditto. And SL Relay LED brightness adjustment fixed as well. Thanks, Tim

Hi Drew, In your programs you listed I am assuming Variable1 is a state variable since an integer would never trigger the program. I don’t quite understand “old value.†ProgramB only will run when $Variable1 changes (unless it is called by another program or manually ran in the admin. console). If the variable changes from 1 to another number the program will run Else, and stay false until the variable1 = 1. At that time it runs Then and stays true. So in effect is always going to reflect the true, latest and most up to day status. Sorry, I don’t understand this question since the status of ProgramB is always going to be the newest and latest status of the variable. ProgramA will re-evaluate every time ProgramB changes state or when the LightSwitch1 is switched On. So ProgramA will not turn true until ProgramB is true and LightSwitch1 is switched on. I am sorry if I am mis-understanding what you are asking. Tim

Hi dzarn, Well, if I am understanding correctly, even with the time schedule I don’t see a reason you still couldn’t merge the two programs. If On Mon, Thu Time is 9:30:00PM And $RainDelayDaysLawn is 0 Then Set 'Irrigation / Sprinklers / Front Yard' On Wait 30 minutes Set 'Irrigation / Sprinklers / Front Yard' Off Set 'Irrigation / Sprinklers / Back Yard West' On Wait 30 minutes Set 'Irrigation / Sprinklers / Back Yard West' Off Set 'Irrigation / Sprinklers / Back Yard East' On Wait 30 minutes Set 'Irrigation / Sprinklers / Back Yard East' Off Else Send Notification to 'Drew Email' content 'Rain Delay Info' As long as the variable RainDelayDaysLawn is 0 then on Monday and Thursday at 9:30 PM this program will run. The only issue I see is that you will get a notification of Rain delay every time the variable changes from 0 to another number (assuming State Variable) and also at 9:30 on Monday or Thursday when this program evaluates false. As a side note I have been re-reading your original post and I may not be understanding your meaning: Can you elaborate a bit more? Were you having problems or just wanting to condsolidate? Thanks, Tim

Dzarn, I am curious as to why you cannot just merge these two programs together. If $RainDelayDaysLawn is 0 Then Set 'Irrigation / Sprinklers / Front Yard' On Wait 30 minutes Set 'Irrigation / Sprinklers / Front Yard' Off Set 'Irrigation / Sprinklers / Back Yard West' On Wait 30 minutes Set 'Irrigation / Sprinklers / Back Yard West' Off Set 'Irrigation / Sprinklers / Back Yard East' On Wait 30 minutes Set 'Irrigation / Sprinklers / Back Yard East' Off Else Send Notification to 'Drew Email' content 'Rain Delay Info' It appears that Check Rain Delay program will only evaluate and send the notification when the variable changes from 0 to another number. It also appears that the watering program only will run when the previous program is true. Unless of course there is more to these programs than meets the eye. Tim

isy99user, More than likely your "Catch up schedules at Restart" check box is checked in Configuration>System. After reboot any scheduled programs will run with this box checked. Tim

Right but in your example wouldn’t the last run statement be false until 5 minutes after Program 2 ran, then turn true for 5 minute then it would be false again? What I want is for my last run statement to be false for 5 minutes after the program last run then turn true - until the program runs again. Thanks, Tim

I may have figured it out. All of the times I have used this version of last run it has always been the trigger of the program. But for this program I require it to be a condition not the trigger. Could this be the case?

Today my question is about the use of “Last Run Time†in programs. I have used last run time in programs a lot but there is one program where I cannot figure out why they will not work. Hoping someone can shed some light. I did try to study up on the subject but when I did a search I got this result: "The following words in your search query were ignored because they are too common words: last run." I couldn't think of any other terms or combinations to use. I also checked the wiki but didn't find a whole lot on the subject. Basically if I create a simple program such: If Time is Last Run Time for 'Alarm Z01 Front Dr Sw' + 5 minutes Then - No Actions - (To add one, press 'Action') Else - No Actions - (To add one, press 'Action') Once this program is created and saved and “Alarm Z01 Front Dr Sw†is run, this program will turn true after 5 minutes after the last run time. Simple enough. So I have this program: If From Sunrise To 9:00:00PM (same day) And Folder 'Run If Away' is False And Control 'Devices / Frnt Drv MS SL' is switched On And Program 'Alarm Z01 Front Dr Sw' is False And Program 'Alarm Z20 Entry Hall PIR' is False Then Wait 1 second Send X10 'N5/On (3)' Else - No Actions - (To add one, press 'Action') This program works fine. Every time the Frnt Drv MS is switched on this program sends the x10 on signal. But now if I add 2 last run times (or even just 1 last run time) the program will never evaluate as true even though the last run time statements are be true. If From Sunrise To 9:00:00PM (same day) And Folder 'Run If Away' is False And Control 'Devices / Frnt Drv MS SL' is switched On And Program 'Alarm Z01 Front Dr Sw' is False And Program 'Alarm Z20 Entry Hall PIR' is False And Time is Last Run Time for 'Alarm Z01 Front Dr Sw' + 5 minutes And Time is Last Run Time for 'Alarm Z20 Entry Hall PIR' + 5 minutes Then Wait 1 second Send X10 'N5/On (3)' Else - No Actions - (To add one, press 'Action') Like I said earlier, I have used last run in at least 20 or more programs with great success, but this one has me stumped. Thanks, Tim

Thanks very much Chris, Tim

Hi Chris, sorry, I meant to add that to the post. Currently on V3.1.4 These programs were created some point in v3.1.2, before 3.1.3 release if that helps any. Thanks, Tim

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