Illusion

So here it is almost exactly a year later. I have 3 new KPLs. Just purchased. And again I can only achieve a dark 'Off' bottom KPL button by using the manual method. Nothing I seem to do within the ISY will make this button go dark. Has anyone had success turning off the 'Off' back light using the ISY. I would be very interested in how that is done if anyone has had success with it. And just to be clear, we are talking about a 6 button KPL with the KPL in the off condition. I like the bottom off button to be dark when the unit is off.

Sure. No problem. Get a 24VAC transformer (like for a sprinkler system), wire it to R and C of the new upstairs T-Stat, plug it in, . Put Insteon adapters is both upstairs and downstairs t-stats. Create programs that use the conditions of the upstairs t-stat to make the down stairs t-stat do what you want. The possibilities are endless. Of course, doing the remote idea of oberkc's will be much cheaper and may get you exactly what you want, but probably not easy to control with Insteon and tie into an Away setting.

Copy. Thanks for the quick reply... as always.

Possible bug Just added a 2477SA2 NC dual band 240V 30A controller for my water heater. The 'On' button in the Admin Console turns the device off. The only way to get the device to to on (and stop the flow of electricity to my water heater) is to use the 'Fast On' in the admin console. If I then use the 'off', 'fast off', or 'on' it will turn the device off. Also, shouldn't this device have 3 nodes? 1 for controlling the relays, and 2 for sensing "Load On" and "Load Off". As it is now, if I wanted to use this included feature it seems that I would have to use the tap linking method.

Rand, I am talking about physically changing the switch. I press the button on my RelayLinc. If I hold the switch down, the device turns on as expected, but the ISY still thinks the device is off. I have had programs that run based on the local 'fade' up of a RelayLinc. They work fine, but I never noticed before today that when I turn those devices on via holding down the switch that the device state is incorrectly reported in the ISY.

RelayLinc.. If I "fade up" a RelayLinc (any version I have) the RelayLinc turns on as expected, the ISY recognizes the event, and can run programs based on that, but the ISY incorrectly shows the device status as 'Off' Still. The reverse is true for a "fade down" event. So I can cause an event that the ISY is aware of and where the status of a device is incorrect. Bug?

I was just browsing around. I was showing someone at work how I could access my home remotely. I was not changing anything. Just going to the t-stat pages, the favorites, and the device list and looking at device states.

My ISY locked up on me for the first time in history yesterday. I was accessing it remotely using the MobiLinc app for my iPhone and it stopped responding. When I got home the PWR and MEM lights were on and the ISY was non-responsive. After re-boot and export of the log file I see this: 0 CLI-WBu Mon 2010/05/10 12:19:22 PM System -140005 0 null Mon 2010/05/10 07:12:31 PM System Start 0 /CONF/E Mon 2010/05/10 07:12:28 PM System -110022 0 /CONF/A Mon 2010/05/10 07:12:28 PM System -110022 0 /CONF/F Mon 2010/05/10 07:12:28 PM System -110022 Just thought you would like to know as up until this event, my ISY has never had a stability issue ever.

Mac updated to Snow Leopard 10.6.3 from Leopard 10.5.8 per email conversations with Michel. Automatic update within the Admin Console fails due to the invalid length issue at 13% Manual upgrade works when accessing the ISY through Safari using Https secure access with timeout set to 25000 Snow Leopard does indeed fix the myriad of issue I have experienced over the last year with Java compatibilities. Small bug: When I minimize the admin console the icon that shows on the dock is the ugly house (which I hate) instead of the nice planet icon that is represented by the java application. All seems well. $29 operating system upgrade money well spent.

Mac OS X Leopard 10.5.8 Access through Java Application: Automatic upgrade failed at 13% due to invalid length Manual upgrade failed at 13% due to invalid length Access through browsers http and https with java preferences set to run within the browser process: FireFox: Unable to access admin console Safari: Unable to access admin console Access through browsers http and https with java preferences set to run in their own process: FireFox: Unable to access admin console Safari: http: Manual upgrade failed at 13% due to invalid length https with timeout set to 25000: Success. Upgraded to 2.7.15 The previous statements are the same findings as the last few betas I have installed. However, we have a new and much more serious problem. I can no longer use the java application to access the Admin Console in 2.7.15 It now shows the same error regarding class file as the applet shows when trying to run the applet in the browser instead of in its own process. The error is something like "unsupportedClassVersionError: Bad version number in .class file" I have downgraded to 2.7.14 as it is too difficult to change the java settings anytime I want to access my ISY.

Can I try the automatic upgrade from within the Admin Console, or do you recommend sticking with the manual method described here?

yes. Set a program to run at startup. if the program is running (true) the isy has restarted.

Swithlinc Relay v.3A Programmaticly set LED backlight brightness to: 100% led is bright 50% can't see much change to the eye 1% led is very very dim but still on 0% led is screaming bright. Like twice as bright as 100%

I do see your point. Just a different way of looking at it. I have spent so long looking at it the way it is, that now, I just accept it as perfectly logical and correct. I can see it from your perspective as well. You could just add the line "run if" of 'Garage Door / Garage Door-Sensor' to the 'then' after the 20s wait. Then it should do exactly what you are talking about. Now again, you get to pick exactly when the 'if' is evaluated. I think this adds even more flexibility to the program. You are clearly very intelligent, and have obviously thought about this quite a bit, but I respectfully disagree with you. To a simpleton such as myself, I think about it in very simple terms. If the program is not enabled, the 'if' part of the program is turned off. I see it as separate and distinct from the 'then' and the 'else'. I have many programs that have no 'if' and I just use the 'then'. I also have programs that have no 'if', 'then', or 'else' used as flags, controlling their 'true'/'false' nature from other programs. I also often run the 'then' from other programs and would not want the 'if' evaluated in this case.

If the program is not enabled, the 'if' will not be evaluated unless called specifically. You do this from another program but then that is it. The 'if' gets evaluated just there. If the 'if' were true at the time, the then will run. There will be no additional evaluation of the 'if' from that point on unless called again from a program. This is necessary. If the 'if' were to get evaluated again, it would be the same as having the program enabled and then we would loose all the functionality of being able to force an evaluation at a time of our choosing. I have hundreds of programs that would fail if the ISY did not perform in this exact manner.

Michel, I can get to the admin console using safari if I change the java prefs to have applets run in their own process.

Success using this method to upgrade 2.7.13 to 2.7.14 on a Mac running 10.5.8 (Leopard) on the first try. I retain the unusual issue of the Java applet calling on 1.5 instead of 1.6 and so I cannot run the ISY admin console from inside a browser, only with the jnlp application. Also, version 1 t-stat adapters do not appear to updating their 'Fan State' with either a programmatic nor manual 'Query'

Jeff, I do not know that this will work as I have not had time to upgrade to the latest but... On 2.7.13 I could not get the upgrade to complete using any of the prescribed methods. What finally worked for me was to change Java prefs to have applets run in their own process, and then use Safari to open the admin console. When I was done I switched the Java prefs back to have applets run in the browser process, as that choice breaks lots of other stuff. Once installed, I use the JNLP exclusively to access my ISY.

My ISY draws about 1.5W. I measured this when I was building my UPS power supply for it. http://forum.universal-devices.com/view ... 4309#24309 Not sure how much the PLM pulls.

Downgraded to 2.7.12 and confirmed loss of t-stat query capability there as well. I have version 1 t-stat adapters, and near as I can tell, I have no way to query them through a program.

I have changed the t-stat 'null' to "Query" and saved. When I reload the programs, 'null' has retruned, and "Query" has been removed.

Thanks, I missed that. All programs changed to Heat or Cool setpoints instead of just setpoints. The t-stat has to be mode heat AND setpoint other than 58 to be true...

It appears that all my t-stat querys in programs have been changed to 'null' in one of these upgrades.

Ah, but if I run the applet in the browser's process I have no access to the admin console whatsoever. Remember, I am on a Mac running Leopard and for some reason the applet calls up Java 1.5 if it runs in the browser. The only way for me to get to the admin console through a browser is if I changed the setting so the applet runs in its own process and I use Safari

Damn you ryarber! I now have to completly reconsider my whole approach to my outdoor motion activated lighting. I thought I had this all figured out, and then you come along with that little jewel... Up til now I have been using programs to disable other programs when I manually activate the outdoor lights. This method of yours may be vastly better. I will have to give it great thought...