Michel Kohanim

Hi Jeff, Please do take a backup of your 2.7.8. In most cases, the migration phase in 2.7.12, will migrate all your configurations properly. In rare cases (and specifically related to KPLs) and if and only if you have any problems, you have two choices: 1. Redo those scenes OR 2. Use a backup from 2.7.7 (or below) Again, I really do not think you are going to have any problems. Just to be safe, take a backup of your 2.7.8 and export your programs. With kind regards, Michel

Hi Mark, If you do not have user accounts off on Vista/Windows 7, then the file will not be stored in any location except in Java's temp directory. With kind regards, Michel

Hi AnthemAVM, They might be unrelated OR perhaps another device on your network is using port 444. For custom ports, it's always best to use a number above 1200 (1500 and above are much safer). If you can access your ISY, I wouldn't worry about infrequent mem/error lights. If they become frequent, then we have to figure out the cause: you might want to reboot your router especially if you use ISY to configure port forwarding. With kind regards, Michel

Hi justin.cool, I'd have to agree with oberkc ... if the main button is not listed to the right then we either have a bug or that the main KPL button is not added to the scene. Please advise. With kind regards, Michel

Hi justin.cool, Are you trying to turn the load OFF using one of its own sub buttons? If so, unfortunately this will not work. You would have to use a very small on level instead (if it's not a relay). With kind regards, Michel

Hi Jeff, Sincere apologies ... wrong library version was installed. Please do be kind enough to clear your java cache and retry: http://www.universal-devices.com/ssl/insteon With kind regards, Michel

Hi mitch236, ISY does not really care what your external IP address is. It simply shows you that IP for your information. ISY does check for external IP address changes if and only if its own IP configuration has changed. With kind regards, Michel

Hello mbrett, Please forward your Google invoice to sales@universal-devices.com ... it shall be taken care of. With kind regards, Michel

Hi ljm, In most cases you do not need programs. The main question is how does the current switch in your garage door works? i.e. if you took the wires that are connected to the switch out: 1. What happens if you short them? 2. What happens if you disconnect them? 3. What happens if you short them again? If the answer is that 1 opens (or closes) and 3 closes (or opens), then you are correct: indeed you would need a program since your garage apparatus is toggled. On the other hand, if 1 opens (or closes) and 2 closes (or opens) and 3 is equal to 1, then all you need are: 1. Latching mode in IOLinc 2. Non Toggle Off on your KPL button 3. The wires to the IOLinc are connected to NC or NO depending on what 2 is. i.e. if 2 causes the door to open, then you connect to NO. Otherwise, you connect to NC. With kind regards, Michel

Hi Mark, I think we found the problem. Would you be kind enough to do a test with any of the following URLs: http://www.universal-devices.com/99i/2.7.12/admin.jnlp OR http://www.universal-devices.com/99i Thanks again and with kind regards, Michel

Hi Steve, I am not sure why this would be the case. Query All (from the Admin Console) clears all the statuses and therefore any status is a change. In programs, Query All does not clear all the statuses ... So, are you referring to QueryAll in programs or through the Admin Console? With kind regards, Michel

Hi Mark, thanks SO very much. This indeed helps a lot. With kind regards, Michel

Hi madcodger, Is this a homeseer interface question? ISY does not have any scene status. With kind regards, Michel

Hi Illusion, Thanks so very much for the Java console output: it's indeed what I had expected: your JNLP is using Java 1.6 but your applet is using Java 1.5. I am not sure how MAC would decide what engine version to use but using 1.5 is indeed the issue. The WB module is a bug! Thanks again and with kind regards, Michel

Hi mbrett, Please do ensure that you are using the correct URL: http://your.isy.ip.address/admin http://your.isy.ip.address/admin.jnlp http://www.universal-devices.com/99i/2.7.10 http://www.universal-devices.com/99i/2.7.10/admin.jnlp And, I strongly recommend upgrading to 2.7.12. With kind regards, Michel

Hi mitch236, ISY does not like inconsistencies and that's why it will try its best to write all the pending changes. The main thing that we have to figure out is why the 0101 green arrow does not go away (in all likelihood, it cannot communicate with your device). What I recommend is to take one of those devices, factory reset it, and do a restore on it. If you still see 0101 green arrow, then it means that either that device is defective or that something (noise/signal strength) is preventing ISY to communicate with that device. With kind regards, Michel

Hi mitch236, ISY already does that. The default is 3 times and you can increase/decrease it in the shell. With kind regards, Michel

Illusion, I still think that the applet is using Java 1.5 ... it should not and that's the issue (our applet is complied with Java 1.6 and there's a mismatch). Clarence, If you do not want to include EZRain zones in scenes, then I do not see any problems. If you want to include EZRain in scenes, then it might not work. With kind regards, Michel

Hi smurt, -2 = device communications error. For a list of error codes, please checkout: http://www.universal-devices.com/mwiki/ ... r_Messages Although I have heard excellent review of Indigo, I am not at all familiar with it and therefore I won't be able to offer any comparative analysis. For direct command and control of devices, ISY expects the device to respond back with an acknowledgment. If one is not forthcoming, then ISY lets the user know that there has been communication errors (i.e. the device did not respond to ISY). If you never had any communication errors using Indigo, I would imagine: 1. The location of the PLM for Indigo is much more strategic than the location for ISY's PLM 2. Something was introduced to your electrical environment that did not exist before 3. Perhaps Indigo didn't catch communication errors in the same way that ISY does With kind regards, Michel

Hi Illusion, The only problem is this: Java Plug-in 1.5.0 Using JRE version 1.5.0_22 Java HotSpot(TM) Client VM User home directory = /Users/XXXX (obscured) This is using your J2SE 5.0 for some reason instead of 6.0. Would you be kind enough to try http://your.isy.ip.address/admin.jnlp? Hi Mark, Yes !!!! With kind regards, Michel

Hi KenUD, ISY does not automatically generate traffic! ISY's traffic can be categorized into two sections: 1. Change of state which is multi casted by devices back to the PLM 2. Commands sent from ISY to devices either through programs or direct load control In short, there's nothing to disable! With kind regards, Michel

Illlusion, You have a back level Java plugin. You need Java 1.6 ... please ensure: 1. You have the latest 1.6 Java installed 2. In your Java Preferences, J2SE 1.6 is listed at the top and 1.5 below it Huddadudda, Thanks so very much and very much looking forward to hearing good news from you. With kind regards, Michel

Hi Illusion, Would you be kind enough to tell me what URL you are using? Furthermore, would you please turn on the Java Console (use the Finder and look for Java Properties | Advanced | Show Java Console) and let me know what you see when you access the Admin Console. Thanks and with kind regards, Michel

Thanks so very much Steve. We are on it! With kind regards, Michel

Hi ryarber, This is quite odd. Can you turn on/off your lamplinc and let me know if you still have this error? With kind regards, Michel