TJF1960

I just had the same thing happen to my ISY today. I deleted one KPL button from a scene , that is when I noticed that the KPL button was not listed in the device list column. I also noticed 1 KPL button which is used to set a folder true or false is also missing. "C" & "D" buttons are missing from 1 6 button KPL. The rest of the KPL's are listed, so far. I generated a topology and the buttons are listed there. I am running 2.7.4 and the KPL is 2486D v.2C Any suggestions on getting them back? Thanks in advance.

It looks like even though this motion sensor uses a relay to switch the load on and off it has some voltage on the red lead which will bleed off when hooked to a sizeable enough load (like a flood light), but the load on the yellow wire from the 2475S2 isn’t large enough to bleed that voltage down. I wonder, if you were to wire in a small night light, a 4 watt bulb, from the yellow and red connection to neutral, if that would take care of the problem? The 4 watt bulb would probably be enough to drain the voltage presented on the red wire of the motion enough so that the 2475S2 would then see a voltage closer to 0 when the motion is off. I am not sure why there is voltage on the red wire when the motion is off. Perhaps there is a capacitor across the relay contacts to help control contact pitting, or to help prevent voltage spikes from the contact closing and opening. If that is the case, there may be many motion detectors which might present this same problem. Please keep us posted on your progress. Tim

I installed 2.7.4, cleared the Java cache and still do not have the Electricity Tab in Config., System and Climate are the only two tabs. "About" shows 2.7.4 and Weather Info. There is not an Electricity option on the ISY's HTML page either. What can I try next? Thanks, Tim

Great, I will implement this and add this program to Run at Startup. Thank you very much for your help. Tim

Rand, Thank you for your valuable suggestions. I will try to keep it simple with programs. I do have many folders to try and keep programs organized. It can get overwhelming in the Program Summary tab though! That’s good to know. I thought the Wait action did consume processor cycles. One thing I liked about using the Last Run was my concern during a power outage, once power was restored the Last Run time was set in stone. How would a Wait action be handled once power is restored. In other words if the program is: (If conditions are met) turn on fan, Wait 10 minutes, Turn off fan, Wait 45 minutes, Run If. Will the ISY calculate the difference between the time the power went out to when power was back on and act based on that? Or will it run the program once the If statement is correct? Also if the fan was on during the power outage and an hour elapsed during the downtime, once power was restored will the ISY see that it should have shut the fan off during the outage and then shut the fan off, and then resume the program? Thanks, Tim

It is in the schedule section after the time selector drop down menus. It is the drop down selector for Time/Sunrise/Sunset/Last Run.

I would be glad to, I just hope I don’t embarrass myself with my newbie programming capabilities. So please just keep in mind I am still learning as you all review these. This is the main program and is titled "Fmly Rm Attic Fan" If Folder 'Vacation' is False And Program 'Fmly Rm Attic Fan Temp' is True And Program 'Fmly Rm Attic Fan Timer' is False Then Set Scene 'Fmly Rm Attic Fan Scene' On Wait 10 minutes Set Scene 'Fmly Rm Attic Fan Scene' Off Run Program 'Fmly Rm Attic Fan' (If) Else - No Actions - (To add one, press 'Action') This next program is titled "Fmly Rm Attic Fan Temp" and is used as a true / false statement. If the temperature is 80 degrees or hotter and the wind speed is 11 mph or less then the statement is true. [code]If Module 'Climate' Temperature >= 80 °F And Module 'Climate' Wind Speed Average <= 11 mph Then - No Actions - (To add one, press 'Action') Else - No Actions - (To add one, press 'Action') And the last program is titled "Fmly Rm Attic Timer" and is the Last Time Run which is also used as a true / false statement. If the last run time for the fan is between 5 seconds to 45 minutes then this statement is true. If From Last Run Time for 'Fmly Rm Attic Fan' + 5 seconds To Last Run Time for 'Fmly Rm Attic Fan' + 45 minutes (same day) Then - No Actions - (To add one, press 'Action') Else - No Actions - (To add one, press 'Action') Basically I want the fan to operate, when the temperature is in range for 10 minutes, then shut down for 45 minutes, then restart and continue this until the temperature is out of range. I know I could accomplish this using Wait and Repeat but I wanted to stay away from long Wait timers etc. and I thought this could be a nice clean way to go. I believe I can combine the “Fmly Rm Attic Fan Temp†program into the main program. I just haven’t done it yet. I likewise believe I could combine the “Fmly Rm Attic Fan Timer†into the main program as well, if it contained the variables (I believe this is the word to describe the < > = etc.) like the “Fmly Rm Attic Fan Temp†has. If my assumptions are correct, then these three programs could be combined into 1 simple little program. I have used the Last Run in several programs and it works really nicely as it is. But I have a few more that would benefit from the variables. Tim

Hello All, Forgive me if this has been asked / answered before, I have searched but didn’t find much on the subject. I am relatively new to the ISY-99i, and have learned so much from all of the posts on this forum. I recently became aware of and have been playing with the “Last Run†feature in Scheduling for programs. That is a nice feature. I have used it in more than a few programs. It seems to me that it would be very advantageous to include a “>†or “>=†variable to it. For example Time is Last Run + 4 hours > . This way the event would occur if the conditions were met anytime after the 4 hours since the last run time. The “From Last run To Last run†could be used but in a couple of my programs but the time could be 6 months to a year since the last run time and I don’t think the variable can stretch out that far. It seems to me that this addition could eliminate a quite a few extra support programs. Anyway I thought I would throw that out there and see what comes of it. I am always open to suggestions. Please keep up the good work and Thank You! Tim

Ok, Thank you for clearing that up for me. Tim

I am a little confused with this first post which is dated 2/7/08 for ver. 2.7.4 but yet ver 2.7.3 just became available in April of 2009???? Was 2.7.4 an edited into this first post just recently? Is 2.7.4 Beta available yet? Thanks, Tim

I cleared my Java catche. The Electricity Module is not listed in the ISY html page or "About" in the program gui. Is that option a pay for option, or is it included in 2.7.3? If it is a pay for option which add on module is it? The Brultech Electricity Module or the Open Auto Demand/Response Module? I guess I misunderstood from the first post. It sounded like this option was included in the new update but now it sounds like it may be a pay for option. Thanks, Tim

I just installed 2.7.3 last night, and for the life of me cannot find the Enable Electricity box, or anything with the word Electricity in the Configuration tab screen. I have 2 tabs in the config window, 1 is System and the other is Climate. To the right, at the bottom of the window has "Electricity Pricing (Base/Current): $0.00 / $0.00" (which is on every window not just the config tab). Any help would be appreciated. Thanks, Tim

I was under the impression that when Status was called up in a program that the ISY would poll that device. Thank you for clearing that up for me. And I like your example of grouping If Status statements together in one program and using the true/false from those programs in the main programs to simplify. Thanks again, Tim

When "Status" is used in the If line of a program and that program is evaluating, the device is polled. Sometimes a program may have quite a few devices to poll, which slows things down a bit, and increases network traffic. I have 3 programs used to control light output in the Kitchen. All three programs use the status of, in some cases, the same devices with minor differences in the If statement repeatedly. Therefore when all three programs are evaluating the ISY send a status request for each device, so the same device will be polled 3 times. In the interest of keeping network traffic to a minimum and reduce actuation times would it be reasonable to create a program for each device which the status is to be monitored. For instance: Program Kitchen Lite Staus If Status 'Kitchen Lite' is on Then Else etc., etc. for all devices So if the kitchen lite is on this statement would be true. When the light is turned off the status would be false. Now all three programs would be looking for true/false statements and not polling the devices. Would this make sense and would there be any problems this could create? Thanks, Tim

When I was making the decision to purchase the ISY I came across a thread on SH forum. I don’t remember the persons name but he was describing his system and he said once he purchased his ISY, he never looked back. That one statement pretty much sums it up for me as well. UDI's customer support is un-equaled. Add to that all of the information available on this forum, it has made learning/playing with the ISY easy and fun. I cannot even imagine my life now without the ISY! My hat is off to the UDI staff, and all those who have posted their experiences and solutions on this forum. Once I made the decision to purchase the ISY-99i, I Never Looked Back !!!