yardman 49

I have been using IE 6 all along with the ISY-26, and have not yet switched over to IE 7, so I know that IE 6 will indeed work. Best wishes

Hello Mike: Actually, I was going to suggest that "Run at Reboot" be used. But I haven't tried it to see if that option is selected if the program will run anyway, without the need for reboot. I would think that it would just wait for the next reboot. Maybe you could first select "Run", then after the program starts executing, you could change it to "Run at Reboot", and it would continue to keep chugging along anyway, since you had already told it to Run. Then it would also restart after rebooting. Or, the logic of the ISY may be set such that if you just set it up as "Run", it inherently knows to restart it at reboot. I think that "Run at Reboot" may be more for programs that only need to run "unconditionally" at reboot, such as a program that turns something on or off only after a power failure or other ISY reboot. If a program is simply set to "Run" all the time, I would think that even if the ISY rebooted, it would restart the program automatically. I'm certain that Michel will be able to clarify this for us. Best wishes,

Hello Rand: You wrote: Thanks for that tidbit of information! I noticed a weird behavior the other day involving a KPL A button, and this explains what happened. You are a wealth of information! But maybe you have been talking to Dave directly, or my brain is foggy today. It seemed that what Dave was asking was that he wanted KPL A to be a scene controller, but wants it to turn on a scene without actually turning on its own load. Am I understanding this correctly? Best wishes,

Hello Dave: I just reread you post, and realized that I didn't exactly answer your question correctly. You stated that you want to "use button A to control a scene that doesn't include the load that I have connected to the integrated dimmer". Wow, this is making my head spin! So you actually have a load connected to the KPL A dimmer, but you don't want the load to come on when you press the KPL A button, but rather you want other lights to come on? So then how exactly would you ever turn that load on at all????? You could use my explanation that I gave previously, but then simply detach the load from the red wire on the KPL. Be certain to then cap off the red wire on the KPL. Then the load will never turn on, but the KPL with control other lights. I don't think that you've explained everything to us totally. What exactly are you trying to do? One last caveat: if the scene that you are controlling with KPL A includes some of the secondary buttons from the same KPL, you will not be able to control them. But you can write a Program through the ISY that could turn them on or off in response to KPL A being turned on or off. Best wishes

Hello Dave: What you want to do should work, I think. First, through the ISY make a group (scene) and add the devices that you want to be Responders. Then add KPL A last as a Controller. Then in the ISY GUI navigate to that scene, and find the KPL A controller. It will be in red italics. Click on that entry. You will then see the individual levels for the Responder devices. Set the levels that you want for each device, as well as the desired ramp rate for each device (if applicable). That should take care of it. When you then push KPL A to "On", those linked devices should also come on to their desired levels. They should also go off when you turn KPL A to Off. To set the "On" level for the local KPL A load, you can simply go to the KPL A device itself under "My Lighting", drag the slider on that view to set the KPL A level, then walk over to the KPL A and do a single quick push on the air-gap button. That shouid set the local level. You can also perform an "air-gap" to set the local level. If you do the "air-gap" rather than pushing it, this will also save whatever KPL A local ramp rate that you have set through the ISY. Please let us know how this works. Best wishes,

Hello Mike: I've never tried this, but how about if you eliminate the conditional time statement entirely, and only keep the "Then" statement. Then, in the Program Summary, you change the program to "Run" instead of enable? Once you do that, won't the program just keep running? Best wishes,

Hello Mo: Thanks for the update. Boy that does sound like strange behavior. I also didn't know that you had the 99. Since you didn't specify, I thought you had the ISY-26. My ISY-26 did not come with any "default" program that did a system status query at 3 am. Are the 99s coming through this way? Has anyone else seen this? Best wishes,

Hello Dave: The only way to upgrade the firmware on the PLM is to order a new one from SmartHome. You can try asking for a replacement , but may not get one from them. As far as I know, you will want Firm61 or later for the PLM. The firmware upgrade for the ISY (2.6) is on the UDI website. Please be certain to get that and upgrade the ISY before you start any programming. Best wishes,

Did you create any programs in the ISY? It sounds as though you have a program written that turns off all of your lights, and is set to "run at reboot".. Keep in mind that the "Run" command at reboot will jump to the "Then" section and run your program, ignoring the conditional "If" section. So if you have a conditional time for such a program, using "Run at Reboot" will ignore the time condition statement and just run the program's "Then" section. Best wishes,

yardman 49, You missed it by one code drop; the following was added to the 2.5 RC1 drop, and of course is in the final release (2.6): - 'Restore Device' now removes links to unknown devices - 'Restore Device' now removes duplicate links - 'Restore Device' now moves keypad led links to front of link database - 'Restore Device' now ensures link to PLM for responder only devices Complete list: http://forum.universal-devices.com/viewtopic.php?t=266 Great news! Thanks so much, Chris! Best wishes

Hello Mike and everyone: I was running 2.4.15 (2.5) until recently, and this never seemed to work correctly for me. I always had to remove the primary, then add it back in. I've recently gone to 2.6, but I haven't tried Chris' suggestion with 2.6.

Hello Mike: I do a similar thing with the ISY; I even have a program folder called "Cleanups". I keep all my programs that I use to monitor or "cleanup" KPL secondary button status lights in this folder! Here's an example: ********************************************* 1) I have a group (scene) that I call "Basement Normal Preset". In this scene, I have some switches turning on to preset levels, and other switches turning off. 2) Also in the scene are secondary buttons from a KPL in the basement. 3) The scene is controlled by both a Remotelinc in the basement and my Kitchen KPL button "G". 4) I want all the basement KPL secondaries to show the "true" status of their linked devices after the scene is turned "on". However, some of those devices are being turned "off" when the scene is turned "on"; if I then include the basement KPL secondaries for the scene "off" devices, those secondaries will actually show "on", even though the actual devices go off (the problem that you are experiencing). 5) My solution is two fold: first, I leave the buttons that need to be "off" out of the scene completely, and only put the "off" devices into the scene, along with the "on" devices and their respective "on" basement KPL secondaries. These then all respond as desired when the scene is activated. Then, to set the proper states of those secondaries that should be "off" when the scene is activated, I then "fix" those secondaries by means of the following "program": If Control 'Kitch KPL G - Lower Level' is switched On Or Control 'Kitch KPL G - Lower Level' is switched Off Or Control 'Bsmt RTL 5 - Normal Preset' is switched On Or Control 'Bsmt RTL 5 - Normal Preset' is switched Off Then Wait 3 seconds Set Scene 'Basement Normal Cleanup' Off Else - No Actions - (To add one, press 'Action') **************************************** The scene "Basement Cleanup" is the group that includes all of the "off" secondaries for the "Basement Normal Preset" scene. This has actually worked out very well for me. The "wait 3 seconds" is necessary to allow the group cleanup messages to stop bouncing around after the scene is activated. If you don't put that in, you may get the Remotelinc or control KPL status lights to go into "spastic flashing mode". I use this same concept for other similar scenes. I have not used "Else" statements for these. How would the "Else" statements be used for these, Rand? Best wishes,

Nice catch, Rand! This probably should go in the Wiki.

Hello Jeff: You mentioned that there are two versions of the JRE on your computer. So then you may want to uninstall both, and then install the version that comes on the CD that came with the ISY. On my system (Windows XP SP2) that shows as version 1.6.0_02. Under "Add/Remove" programs, it shows as "Java 6 update 2". I have the same version on my laptop. Also on both my systems, J2RE version 1.4.2 is installed. On my main system, it is 1.4.2_03, while on my laptop it is 1.4.2_01. So it appears that I also have two version of the JRE on my systems also. I don't know how applications handle Java. It is possible that each applications calls out the specific version of Java that it requires, or maybe a "minimum" version number, so that multiple Java installations can co-exist on the same system. I would probably start with using the version on the CD only and see how that works, after you've removed all previous versions. Maybe Chris or Michel can reply here to let us know what is the best version of the JRE to use for Vista. Best wishes,

Hello Jeff: I see that you've upgraded the JRE. But have you tried to completely uninstall Java, reboot your system, and then reinstall Java? If you haven't yet done so, it probably wouldn't hurt. It could be that there's some setting that's corrupt in the system Registry on that computer, and doing a complete uninstall and reinstall may fix it. Another thing that you may have already tried would be to disable the local Java cache completely (disable "Keep temporary files"). I've never tried that, but it would be interesting to see what happens. Finally, have you tried to force an ISY reboot through the Admin shell (RS command)? I think that unplugging the unit and plugging it back in effectively does the same thing. After you reboot or power cycle the ISY will go through and do an all device query, so the activity lights will be firing for a while. Once they stop, then try to log back in to the ISY. The only reason that I suggest this is that I too access my ISY through both my main system and my laptop. It seems as though the ISY remembers the last state of the GUI display depending on which system I am logging in through. This may just be a local Java cache feature. But maybe Chris or Michel can comment as to whether the ISY tracks the system login identities. If so, then maybe that helps explain what you are seeing. I hope that you can get this resolved and then report back with the solution! Best wishes,

Hello Jeff: You've probably already thought of this, but I was wondering if you've tried clearing out the Java cache?? Best wishes,

Hello Joe: The ISY support for X10 works well enough for my purposes. I started the "tabs" request post because I had wanted a little more "direct" control, which is why I proposed the "extra tab". UDI made it clear from the beginning that the ISY would not support X10. I believe that it was only after requests from users that X10 support was added. I know that it wasn't until I heard about the X10 support being added that I finally jumped in and bought my ISY. So I am grateful that they added it. I'm happy with the way the ISY handles X10 triggers and programs. For instance, I can use an ISY program to send out an X10 command when it receives a different X10 house code. Or when it receives an Insteon command. Or when a timer runs. So it is very flexible in this reqard. You could almost consider it to be a "Insteon/X10 bridge". So in terms of features at this point, adding a little more direct control (for testing communication, for example), would be desirable, but it isn't a show stopper (at least for me). The only X10 problem that I've seen is with the PLM itself, which is a SmartHome product. Michel (CEO of UDI) recently said that the latest PLM revision from SmartHome (firmware 61) should improve the sensitivity of the PLM to incoming signals. We'll have to wait until someone gets one and reports back here on the forums. I hope that this helps. If you have specific questions regarding your X10 applications, please feel free to post them here and one of the users will most likely have an answer. Best wishes,

Hello Rand and Michel: I'm find the same thing as Rand. I don't see any option to "Replace...with.." when I right mouse clicked on my existing RL, even after I had already added the new RL to the ISY. Best wishes,

Hello Michel and everyone: I've received a replacment RemoteLinc from SmartHome to replace one that's been eating batteries. I am still using 2.4.15 ISY firmware, as things have been running OK, and I don't want to "break anything" until we're certain that 2.5 RC1 is healthy. So if I haven't tried RC1 yet. That being said, I cannot find a "Replace...with..." command for the RemoteLinc in version 2.4.15. Has this option been introduced with RC1?? Thanks.

Hello MikeB and Michel: Mike, I'm curious as to whether you've had a chance to see if the Rev 1.5 KPL has fixed the "Must Add Primary Button Last to Scenes including Secondaries" problem that has always plagued the KPLs. I am very curious about this, as to me this is even more aggravating than the "cannot control Primary from Secondaries" problem that 1.5 is suppose to fix. If not, would you mind running an experiment on this? Also, if Michel, Chris or anyone can give us a layman's synopsis of what features have been added or changed in Insteon 2, this would also be great. Best wishes,

Hello Michel: you wrote: Thanks so much for the explanation. I'm going to start a new thread and see if you, Chris, MikeB, or anyone else on here knows exactly what changes we can expect from I2. Best wishes,

Greetings Michel: you wrote: I guess that I missed this somewhere. Maybe I was sleeping in class! But what is Insteon 2, when will it be available, and what effect will it have on the ISY?? ************************************ Also: what did you think about my request? I wasn't just asking this for myself, really. It just would seem to be a lot less confusing for everyone if the GUI somehow showed in the lighting control view that we really don't have the ability to control the ramp rate, even through direct ISY control. Thanks!

Hello Michel and Mike: Thanks for the replies. I guess that using two scenes might be best. But I did find a workaround: I set the dimmed level to 50% for my Christmas group (scene). Then in my "on" program for my Christmas lights, I invoke the "Fast On" for that group, instead of just "On". this sets the initial on state of the lights to 100%. Finally, in my "off" program, I invoke the group "On" command first at 11 pm; this then sets my lights to 50% (the group preset dimmed level). Then an hour later I invoke the group "off" command, thus turning the lights completely off. ************************ When someone gets a chance, I still need an explanation of what "Dim" and "Bright" do in programs, and how best to use them. Thank you.

Hello all: I need some advice on the following: I have 4 LampLincs that are running the Christmas candelabras in my front windows. I have them on from sunset to 11pm at full on. I then want them to drop at 11pm to a "dimmed" level for the next few hours, since they are pretty bright. Do I have to make two separate scenes for the candelabras, one at full on, and one at a dimmed level? I notice that there is an Insteon scene program command in the ISY called "dim". But when I pick that option, it doesn't say "how much" it will dim. So I'm confused on how to use that feature for a scene. Thanks in advance for your advice.

Hello Michel: I'm currently running 2.4.15. I just noticed something that may have always been this way, but I'm not certain. When setting the ramp rate of a Togglelinc dimmer or LampLinc, although I can change the local ramp rate slider, it will not change the dim rate when the light is turned on or off from the ISY GUI. I knew that you could not change the rate at the switch via the GUI without an air gap being done, but I thought that I remembered that the GUI ramp rate slider would change the ramp rate when the device was directly controlled by the GUI. And by "directly controlled", I also mean not as part of a group, but directly from the lighting view. If this is "normal", then I was wondering if you could change the device "ramp rate sliders" in the GUI ton say "Applied Locally", the same as for the controller devices in the scenes. That way, several months from now when I've forgotten this again, I will see the ramp sliders in red and say "oh, that won't work without doing an air gap". Thanks