TJF1960

Hi Walt, Wow, that was quick! It took them literally 4 or 5 business days to respond to my request. I cannot offer any assistance and I read in another thread that Michel was out until tomorrow I believe, just to let you know. I am sure he will be able to get you fixed up though. Tim

Good deal! It did take them 4 or 5 days to reply back to me. I was really suprised my area is good to go because it is a simi rural area here. Here's to hoping your area is good to go as well!

Hi Walt, Not sure if you had come across this page or not http://www.pge.com/myhome/saveenergymoney/energysavingprograms/han/eligibility/index.shtml but you can fill out your info and pge will let you know if you are in a HAN service area or not. I had the same problem with phone numbers and cs agents I spoke with.

So if I understand correctly, then based on your program the only time the tstat fan will switch back to Auto is 20 minutes after the Sensor is Off. If the sensor is cycling every 4-5 minutes for the next 6 hours then the tstat fan will not shut off for approx. 6 hours. If that is what you had in mind I think it should work perfectly.

Might I suggest, and using your first program in the first post as a guide, create a new State variable named something like “sOutsideTempOver60 and then a new program outside of your conditional folders such: If Module ‘Climate’ Temperature>=60 Then Set ‘sOutsideTempOver60’ 1 Else Set ‘sOutsideTempOver60’ 0 Then in your first program replace the Module ‘Climate†Temp line with “sOutsideTempOver60 is 1†This way the only time your AC program will re evaluate due to outside temp will be when the outside temp crosses over or under 60 degrees. Also, If you do not want the AC program to re evaluate at 5AM or 8AM as it is doing now you can remove that schedule and replace using the folder condition as such: If Folder ‘Armed Away’ is True And sTempOver60 is 1 Then Set 'Indoor / HVAC / Main House / HVAC Main House' Fan Auto Set 'Indoor / HVAC / Main House / HVAC Main House' Mode Auto Wait 3 seconds Set 'Indoor / HVAC / Main House / HVAC Main House' 80° (Cool Setpoint) Set 'Indoor / HVAC / Main House / HVAC Main House' 60° (Heat Setpoint) Else - No Actions - (To add one, press 'Action') Now with the conditions in this program the only time the program will evaluate true is when the alarm is first armed away and the outside temp is over 60 or if the alarm is in the armed mode while the temp crosses over 60.

Yes it has been my experience. But like I said, comm issues will alter the results of the program. Good question about the order. I just tested the order and it did not make a difference. I am not sure exactly why it works this way. Perhaps since programs are event triggered the first trigger sets the evaluation in motion and at the time of the trigger the status of the lite was off which caused the program to evaluate as false. Then the status changed of the light triggering the second evaluation again as false because at that moment the control was not being switched on. Plus, I keep going back in my head to what the op has stated that these same programs work fine in other parts of his house and that this problem occurred after he replaced a SL with a DB SL which suggests either the DB SL is defective, his wiring is defective or something in the powerline has changed causing poor comm issues.

oberkc, if I understand what you are saying correctly then I sadly have to disagree with you this time. I have seen this type of program structure work in the past. I have also seen comm. problems cause the program to malfunction if there were less than 1 or 2 hops left. I just ran a test with this program: If Status 'WR Bench Lite' is On And Control 'WR Bench Lite' is switched On Then Set 'Vent Fan' On Else - No Actions - (To add one, press 'Action') When the Bench lite is off and the switch is turned On the program executes Else (actually it executes false twice). If the Bench Lite is On and is switched On the program executes Then (and stays true). If the Bench Lite is On and the switch is turned Off the program executes Else. In the first test where the light was off and the switch was turned on, the switch turning on caused the program to evaluate but at the exact moment the switch was turned on the status of the light in fact was off so the program evaluated false. When the status of the light updated to On the program re-evaluated but because the program evaluated when the status change occurred the control switching on didn't occur the program evaluated false again. To test I added an integer variable to the Else condition which would +1 for every evaluation which ran the Else.

The reason for this is that once the program runs true it changes the variable state (of which it is monitoring in the IF)..which causes the program to run again, this time false. If the programs were working perfectly when the old switchlinc was in place and if the electrical connections are good and tight on the new dualband I would suspect the new dualband and would suggest either reinstalling the old switchlinc as an added test or if you have another dualband available try installing that one and testing. Odds may be slim that the dualband is defective..but its a possiblility.

Upgrade went without a hitch. Finder launches right into admin console without prompting. Thanks, Tim

johnnyt, This bug only occurs when you manually query a device not when the query is part of a program.

Hi Xathros, I ran into this a few months back. If you manually query a device it will trigger a program then/else. But the nightly queries do not. Nor do device queries via a program. Tim

I would try to swap one of the lights with an incandescent to see if the added load dampens the flickering of the LEDs.

How about If Control 'Switchlinc' is turn On And Control 'Switchlinc' is not turned Off Then Wait 15 Min Set 'Switchlinc' Off

Hello Mark, I found this calculator in the wiki, not sure if it is the one you are looking for or not. http://irrigation.wsu.edu/Content/Calculators/General/Set-Times.php In case you haven't checked, the wiki has some examples and info for irrigation. Just type irrigation in the wiki search. http://wiki.universal-devices.com/index.php?title=ISY-99i/ISY-26_INSTEON:User_Guide Hope it helps, Tim

Same experience here. It took very little time from my email to the modules being ported over. The thing that took me the longest was getting my router to accept the static IP address...but that was in no way the ISY's fault. All in all it was very painless. The only words of wisdom I can suggest is to just take your time and don't attempt it while you are in a rush.

I originally started off with what you had in mind, basically: If Sunrise to Sunset (same day) Then Set 'Devices / MB Sink Lite' 60% (Backlight Level) and so on Else Set 'Devices / MB Sink Lite' 20% (Backlight Level) So that at Sunrise the devices would get set brighter, then at sunset they would dim down. Then it evolved to only occuring if we were at home, the daylight brightness was down to a certain level and the LED levels had already been changed and need to revert back. All which takes two programs to function Program: Backlight Adjust Hi If $sAway_Status is 0 And Program 'ISY Reboot' is False And $sWC1_DayLight_130_Status is 1 And $iMB_BackLite_Day_Adj is 0 Then Wait 30 seconds Set 'Devices / MB Sink Lite' 60% (Backlight Level) Set 'Devices / MB Shower Fan' 60% (Backlight Level) Set 'Devices / MB Ceiling Lite' 60% (Backlight Level) Set 'Devices / MB Ceiling Fan' 60% (Backlight Level) Set 'Devices / MB Bed Lites' 60% (Backlight Level) $iMB_BackLite_Day_Adj = 1 $iMB_BackLite_Day_Adj Init To 1 Else - No Actions - (To add one, press 'Action') Program: Backlight Adjust Low If $sAway_Status is 0 And Program 'ISY Reboot' is False And $sWC1_DayLight_130_Status is 0 And $iMB_BackLite_Day_Adj is 1 Then Wait 30 seconds Set 'Devices / MB Sink Lite' 25% (Backlight Level) Set 'Devices / MB Shower Fan' 25% (Backlight Level) Set 'Devices / MB Ceiling Lite' 25% (Backlight Level) Set 'Devices / MB Ceiling Fan' 25% (Backlight Level) Set 'Devices / MB Bed Lites' 25% (Backlight Level) $iMB_BackLite_Day_Adj = 0 $iMB_BackLite_Day_Adj Init To 0 Else - No Actions - (To add one, press 'Action')

Yeah, I remember that tripping me up as well! Glad you have it working.

Does manually switching the front porch switch on then off update the status in the admin console of the ISY correctly? Does the first program turn true and false with manually operating the switch? Is the second program being enabled and disabled? Also the first program, I think the enable and disable lines are reversed. They were correct a few posts up but got reversed in the last post.

Hmm. If the light is turned on with the switch the first program should turn true and stay true until the switch is turned off. When that program is true the second program will not turn true when the motion sensor is tripped, it should only evaluate false. Is the motion sensor directly linked to the switch?

You might try a program which monitors the switch: Program: Front Porch Switch If Control 'Front Porch Switch' is switched On And Control 'Front Porch Switch' is not switched Off Then Else - No Actions - (To add one, press 'Action') Then change the second If to read: If Control 'M4 - Front Porch - Sensor' is switched On And Program 'Front Porch Switch' is False Then Set 'Front Porch Switch' On Wait 5 seconds Set 'Front Porch Switch' Off Else - No Actions - (To add one, press 'Action')

Try putting a piece of black electrical tape over the IR hole on the ISY and see if the IR log entries stop.

Hi Tom, Glad it worked out for you. Actually its not multiple instances. Anytime there is a Wait in the action, either in the Then or the Else and something changes in the If the program will re-evaluate. In this case the only trigger is the bell button being pushed. The Integer variable will not cause a re-evaluation. Anyway, glad it worked and thanks for posting back. Tim

Hello, Try this If Door Bell Switch is Switched On and Integer Var1 is 0 Then Ring Bell Set Integer Var1 = 1 Wait 5 minutes Set Integer Var1 = 0 Else Tim edit: The first time the door bell switch is pushed and the var1 is 0 the program will run and ring the bell once. But the second time within the waiting period the button is pushed the program will evaluate as Fasle. So try adding a Wait 5 minutes followed by Set Integer Var1 = 0 to the Else section. Then once the switch is pushed a second time and the program evaluates to False the timer will start again. 5 minutes after they stop pushing the button the var1 will be reset to 0 which will allow the program to run and ring the bell when the switch is pushed.

JimS, Beta's can be buggy that’s why they are called beta's. Stick with Final Releases if you do not want to help contribute to them. Besides the fact that UDI had to recode everything just to support the curve ball Insteon's new protocol threw at them. Btw the only "brand issue" I see is Insteon..they should be doing a much better job of supporting and informing companies like UDI of upcoming changes. aaronb, I whole heartedly agree with you.

wrj0, So glad you got it working! I messed my cert. up a few months ago and was out of town before I realized I couldn't access the ISY thru Mobilink or Conductor. Once I got back Michel walked me thru deleting it..been afraid to mess with it since! Very happy to hear, thanks for posting back. Tim