TJF1960

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

Ditto, Thanks Michel! Tim

Upgraded to 3.3.9, without updating cert., and this works perfectly now. Thanks Michel! And thank you wrj0 for bringing it up! Tim

Hi Michel, The links provided in your Java announcement are for 3.3.9, the admin console link works but as johncrab pointed out the Dashboard link doesn't. Is it alright to use the 3.3.9 admin console with 3.3.8? Thanks, Tim

I have tried everything I could think of and still cannot get the network resource to get thru. I just reverted back to 3.2.6 and it works perfectly every time. Then upgraded to 3.3.1 which was the next firmware update and the network resource no longer works. Something changed between the two versions. Could it have anything to do with security certificates?

I have the same exact problem, was working on my ISY994 in the current rev at the time of the post (I believe it was 3.2.6), then the next rev it only worked sometimes, but most of the time it wouldn't. Since then with later revs it hasn't worked at all for me. I could never figure out why. If you figure it out please post back. Thanks, Tim

Very nicely done! Great Job!

Makes sense. Then you would definitely need 2 programs. Just change the first one like so: If the device is on at 50% or higher this program will not run Then. If you want the device off after 8:30P then change the 2nd program to:

I agree with oberkc. The reason is the "And Status 'Under Cabinet' is Off" in the If section. Anytime the status of "Under Cabinet" changes this program will re-evaluate. So if between Sunset - 8:30P and the Under Cabinet is Off The program will evaluate to true and turn it On. Once it turns on, the status of the device changed from Off to On which forces the program False which runs the Else of the program which turns Off the device. Once the device turns off its status changes from On to Off which forces the program True again...and on and on. To remedy the situation either remove the Status of the device or break the program into two programs. I personally prefer using Status in this situation if for no other reason to help keep powerline comm. to a minimum. If the device is already on, why send a command to turn it on again? Likewise with your existing program it will send the signal for the device to turn off even if it is already off. For instance everytime 8:30PM hits it will run the Else as well as everytime the status changes of the device the Else will run. Try this: If From Sunset To 8:30:00PM (same day) And Status 'Under Cabinet' is Off Then Set Scene 'Under Cabinet' On Else If From 8:30PM To Sunset (next day) And Status 'Under Cabinet' is On Then Set Scene 'Under Cabinet' Off Else

Same here, all went well from .7 to .8 and the only kpl that the backlight adjustment quit working on is now functioning as normal. Thanks, Tim