ulrick65

Yes...a very Happy New Year to everyone as well. May the new year bring you health, wealth, happiness and some new toys...everybody needs more toys!

Likely because the light that you have in the conditions did not change state. ISY only evaluates the condition when one of the conditions change state. I am betting that it you turned that light brighter then 20% then less than 20% it would have. Which reminds me...using status < 20% will not recognize when the light is OFF. OFF is not < 20% as far as ISY is concerned. If you want to trigger when the light is less than 20% OR Off...you need to specify that. Just thought I would mention it in case you were not aware of this little quirk...

I never thought to look in the Control Panel! "Silly Eric...computers are for kids!"

Did you actually hear from SH? Sorry to make you sweat No, I went to their website for the 1700 and read the Spec Sheet...probably should have read that closer before! Here's the link: http://www.smarthome.com/manuals/30410a_spec.pdf

That makes sense...someday I gotta read up on how the guts of the protocol, linking, etc. works...I am interested. Any recommended reading you can point me to?

Good point Darrell, I hope Rand see's this...or he's gonna be pissed when it doesn't work tonight! When you uncheck On Days you can select individual days. When you uncheck Daily you should get a date selection box. However, might I suggest NOT using the date today, because of the bug described here? Instead, just look for the time being midnight (and remember to disable the program tomorrow).

Because after the first go around, it executes the ELSE portion each time...because you turn the light on and off, which is one of the conditions so it evaluates the If...since it is NOT 10:00:00, it runs the ELSE again...and so on.

I noticed that a few people lately have had issues that are finally resolved by clearing the java cache, reinstalling 2.6.13, etc. and I was wondering if maybe we need a good description on exactly what to do to clear the java cache when upgrading firmware. I remember from somewhere that java will not clear the cache if Internet Explorer is open. Problem is, if everyones works likes mine, the little java icon disappears once you close internet explorer. What I have been doing is when the icon is there, I right click on it and go to "Open Control Panel". I then close all sessions of Internet Explorer and then clear the cache. I am not sure if this right, wrong or helping in any way...however, I have not had issues like many others have. Then again, lots of people have not had the issues....so I don't know. Can anyone confirm the proper way to clear the cache? How about the proper way to install the new firmware updates (specifics for folks that might not be savy with this kind of thing)? Maybe I'm off base here, but it seems like it might alleviate some issues for people.

Did you download and install the correct version now from here: http://forum.universal-devices.com/viewtopic.php?t=2030 and do the whole clear cache, reinstall the firmware, clear cache thing? Yes, I am running the version from the above link with my 99i/Pro and don't get any failed messages.

Crap...mine is reporting around the same number and now that I think of it, it rarely changes much. Come to find out it DOES NOT sense humidity...you have to add an "optional module". I am not convinced even at that it will work with the 1700 model (which I have) you may need the 1800 for the optional module. The 1900 has it built in... Damn it...one of the reasons I liked this so much was I thought I could control humidity in my computer area by cycling the AC if the humidity gets too high, even tho the temp doesn't. SH website is a bit misleading as you said... Thanks for bringing this up...I guess! I felt better before though!

Because you are checking the status of the 'Hearth-5-Lamplinc' in the condition and then setting that same light on in the Then section...which makes the condition change and become false, which immediately runs the Else section...which changes that light again and the status changes and it becomes True...so it immediately runs the Then section...which sets the light again...etc. etc. etc.

When you select the schedule, at the bottom you will see a check box for "Daily". Turn that off and you will get a drop down box for a specific date.

I don't think it is that bad for me. I was polling every 15 minutes, but didn't really need it that often. After all, do I really care if the temp changes 1 degree? It does not send status updates...ever. So if someone changes it, you will not know it until the next poll. I think it works pretty good, at least for my needs.

That is still the case, you must query the stat to get updated temp readings, etc. There is no good way to log the info...you could do it with the event viewer...but not very pretty and certainly not a robust process.

Thats Cool Rand. The flashing part if fairly straightforward...the part about returning the lights to their (almost) previous settings is ingenious. I would have never thought of doing it that way! It never ceases to amaze me what can be done with this very simple system....with just some thought and creativity. When I first got the ISY, I thought "man...this is very basic and not near the amount of power I want...I am going to need a computer based system"...man was I wrong. I now have 24 hours to get mine done...my wife will be so proud! That reminds me, quick story: We got a new pest control guy today...he finishes up and after giving us the bill he says "I see these buttons and lighted switches all over the place...what is that?" I proceed to tell him...he thinks it's cool, etc. etc. Wife rolls her eyes and walks out of the kitchen. Man I love this stuff!!

Michel, Something I have been wondering about I2, I1, etc. that maybe you can clear up for me: I saw in one of your posts that you mentioned that the RL programs with I2...it takes a long time, goes out of program mode, etc. I think a lot of us agree that I2 is not helping us much...so one question: How did we program our RL's back when we had 2.6.8 and ISY was not I2 savy like it is in 2.6.13? Why don't we just change to I1 only and run that way? I am assuming because some devices (like the motion sensor) are I2 only? If that is the case, then let's say I didn't have ISY...I would not be able to use my new motion sensor with any SWL older than say 3.5? Just some things I wonder about when I sit alone in the dark... Thanks.

Hopefully this corrected your original problem as well?

It does. In fact it has two! One of them is a standard RJ45, but it is Serial not ethernet as to_lighter said. Common mistake...but as Michel warned, not one you want to make if you can avoid it. The port that goes to the PLM is a serial connection...labeled port B if my memory serves me, but that is way down in the basement and too far to walk right now!

The link you are showing there is for the ISY-26 not the ISY-99. The 99 version is below that in the post. Did you clear your Java Cache after upgrading the firmware? It sound like the firmware updated, but you are running the older version of the console. Right click on the little Java Icon down on the right and goto Console. Then, close down all Internet Explorer (or whatever browser you are using) windows. Then under "Tempory Internet Files" in the console, click setting and delete the temp files.

Weird one... What version of firmware are you running the ISY on? I assume you setup the KPL buttons as controllers in a scene with a SWL that is also a controller? Does the SWL work OK and the light comes on when you tap it? If so, does the KPL button come on when you turn the scene on from the SWL? Are these new devices that you just installed or had they been working before? Did you do a factory reset on them before installing them? If you don't have to much tied to things yet, I would remove the devices from ISY, do a factory reset on them (pull out the gap button, wait 10 secs, push it all the way in, wait 10 secs and then release). To me, unless I have a ton of stuff tied them already in ISY this is my first thing to try. It seems to me I read about someone else having a similar problem, but I would not find the post. Sorry I asked more questions then offered answers, I have lots of KPL's and have not seen this issue before...hopefully someone else has seen this.

It is because LED's are being controlled. If you can add an additional small bulb to it it should be enough to get it to shutoff completely. Some people use a "brick" transformer (like a cell phone charger or something) so they don't have to light a light.

Well...you can't way the folks in this forum don't try and help! First Rand gives the answer, I figure you might need a little more detail, so I give it some...then Mike follows up with details, examples, 8x10 color glossy's with circles and arrows and a paragraph on back explain what each one does...

Actually, when you click on a controller within the scene, you will see the sliders for that controller (it will say "Applied Locally" in brackets to the right off the controller name). For a KPL button A, it will show up. As you noticed, it will NOT show up for secondary KPL buttons (B through H). For your KPL (since it has no load) it only matters that it be something other than an onlevel of 0. If it has an onlevel of 0, it will not turn it's LED on when the scene is activated. As Mike said though...you would care if this were a SWL because you would want the LED bar to match the on level of the scene. I have made this mistake is the only reason I am jumping in here. It took me a while to figure out why the KPL led and the SWL leds where not working correctly. I figured since there no load there, I might as well set the onlevel to 0...that was a mistake. I would get used to setting it as it should be even if it doesn't have load...just my 2 cents. Yes, sorry I misunderstood your question. When clicking the controller within the scene, you will not see sliders for the controller because pressing the button on the controller will use the device's local on level and ramp rates. When clicking on the scene itself, the slider on the controller would indicate the on level and ramp rate used on that device when the scene is activated from the ISY (through programs or the admin console). Remember that a controller is inherently a responder as well. Like you said, since the device has no load and a KPL doesn't even have a ramping LED bar it doesn't matter to you what the on level and ramp rate are set to. However, if you use a SwitchLinc as a controller or attach a load to that KPL you might care.

I had this same problem and have a ton of programs to fix it...until I read a post on here a few weeks ago where MikeB said the same thing that Rand just said above! Just to give some more detail in case you don't understand what he means: Leave your current scenes as is. What you do is setup a seperate scene for each keypad button that you want to control JUST THE LED with. Add the Keypad button to the scene as a responder, no need to add a controller since you will be controlling these scenes with your program. For example: ScnKeypadButtonB - Contains the keypadlinc button B as a responder ScnKeypadButtonC - Contains the keypadlinc button C as a responder etc. In your IR program to turn on scene A for example, use Set Scene commands to turn off the button scenes for the buttons you want off. For example: Set Scene 'ScnKeypadButtonB' Off Set Scene 'ScnKeypadButtonC' Off etc.

I agree with you. As far as home control stuff goes, Insteon is a cheap solution....but when you get right down to it 50 bucks is still 50 bucks! I had an idea to make my own IOLinc and someday I will give it a try. A few relays, some solder and a keypadlinc should do the trick! My problem is the way I solder it will likely be 3 or 4 keypadlincs, several bandaids and a roll of solder before I get done screwing them up! Maybe I'll just buy the EZIO once they are stable with ISY!