Michel Kohanim

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

Hi Tim, We admit defeat: We had a requirement to provide the correct status for button groupings and mutex buttons. The only way we could accomplish this was to use the abstract concept of a scene. As such, you can now do button groupings using scenes but this would break the mutex groupings without scenes (as you noted). Therefore, we have decided to leave both methods intact with the caveat that if you use manual grouping (not in scenes) you will not have the correct status. With kind regards, Michel

Hi Bobby, Thank you! -5011 means that ISY tried to contact the client (Admin Console) and failed. My recommendations: 1. Please do ensure that ISY is in the white/trusted list on your Avast (this has been reported before with the same symptoms) 2. Please do be kind enough to upgrade to 2.7.12 With kind regards, Michel

Hi huddadudda, This was done only because you requested it ... since they are two different types of devices there might be some issues that we are not aware of. As such, would you be kind enough to test and let us know what you find? With kind regards, Michel

Hi Raman, Thanks so very much for the feedback. Verified that this is indeed a bug and an action was taken to fix this immediately. The fix should be available in our next release. With kind regards, Michel

Hi guys, Apologies for the inconvenience: that was an oversight on our part and has already been fixed. If you cannot wait for the next release, simply use the following URL: http://www.universal-devices.com/99i/2.7.12 OR http://www.universal-devices.com/99i/2.7.12/admin.jnlp With kind regards, Michel

Hi Mark, Good question! The answer is: it all depends on the version of your ISY's firmware. Here's the structure of the URLs on our website: http://www.universal-devices.com/platform/[firmware_version] 1. platform is mandatory ... so, /99i will always have the last official release of the Admin Console 2. firmware_version is optional .. so, /99i/2.7.12 points to the Admin Console for firmware 2.7.12 So, if your ISY's firmware is equal to the [firmware_version] in the above URL, then there's absolutely no difference between pointing your browser to ISY or going to our website, except for: The Admin Console from our website "searches" the network for your ISY (so this is good if you have forgotten your ISY's IP address), whereas the Admin Console from ISY already "knows" where ISY is. With kind regards, Michel W

Hi Denis, I think the problem is the SD Card itself. Please do ensure that the SD Card is seated properly. If that fails, we do need a new SD Card and your backup. I already sent you an email. With kind regards, Michel

Hello, You need to ask if they offer any Demand Response programs. And, if so, what system do they use. With kind regards, Michel

Hello ingeborgdot, Some utilities also provide Open Auto Demand Response solutions which ISY supports. Flex Your Power is CA only ... I totally agree ... you should have never been sent a used unit. Please do let us know if you need our assistance in getting it replaced. With kind regards, Michel

Hi upstatemike, What happens if you go to Tools | Diagnostics | Show ISY Links table for that device? Do you get anything? If not, then the problem is that: a. There are pending device writes for that device b. The configuration file for that device is missing or is corrupt With kind regards, Michel

Hi bkpky, 1. Wait is interrupted when the condition turns to false. So, while waiting and if the conditions is turned to false, the statements following wait will not run 2. Please do be kind enough to use the correct URL for 2.7.12: http://your.isy.ip.address/admin http://your.isy.ip.address/admin.jnlp http://www.universal-devices.com/99i/2.7.12/ http://www.universal-devices.com/99i/2.7.12/admin.jnlp Any of the above URLs should detect your dual band lamplinc. With kind regards, Michel