Michel Kohanim

Hello Dwight, Quite odd and very unlikely (or, let's say impossible) for ISY to do things on its own. Would you be kind enough to forward the email notification you got to support@universal-devices.com? With kind regards, Michel

Hello loganjw, MAC has a [dictatorial] tendency of unzipping files automatically after download. ISY needs the file in tact and thus you have to tell MAC not to unzip. You can try: Unchecking 'open safe files' in the General tab of Safari's preferences. With kind regards, Michel

Hello dennisric, Thanks so very much ... At this point, I think it would be best to contact our support team so that we can log in to your computer and see what's going on. I do apologize for the inconvenience. With kind regards, Michel

Hello apostolakisl, Would you please send your logs to support@universal-devices.com? With kind regards, Michel

Hello dennisric, By ELK Console do you mean the Java applet or do you mean ELK RP? Can you connect to your ELK from ELK RP using network, the IP address that you have in ISY and port 2101? With kind regards, Michel

Hi Tim, Those errors are file system errors. We are trying to figure out why some of the nodes were not migrated properly. There are two cases: 1. File access (which is not the case in your situation) 2. The had wrong values to start with With kind regards, Michel

Hello Teken, I am so very sorry to hear about all the problems you had. Can you please: 1. Change your userid/password to admin/admin 2. Take a backup 3. Send your backup along with the Error Log to support@universal-devices.com With kind regards, Michel

Hello LeeG, Thanks so very much. Hi Tim, do you have any -1100xx errors in your Error Log? If you do, can you please send me your error log? With kind regards, Michel

Hello dennisric, Please include any 4 or 6 digit number in the Access Code field and retry. With kind regards, Michel

Hello Andy, You should be able to ... 1. The first thing I check is to make sure the on level for ApplianceLinc is not set to zero in the scene for the KPL button 2. Do a link compare between ISY and the Device (Diagnostics | Show Device Link Table and Diagnostics | Show ISY Link Table) ... are they in synch? 3. And lastly, I would remove the KPL button from the scene and add it back to the scene With kind regards, Michel

Hello all, In 3.2.x, ISY has to migrate specific information about devices so that we properly apply different communication modes based on different devices. There seems to be some corner cases where the migration might not succeed: 1. The information ISY already had was out of synch 2. ISY could not read the configuration Do any of you see -1100x (.REC) errors in your Error Log starting from after the upgrade to 3.2.0? With kind regards, Michel

Thanks LeeG. We are looking into it. With kind regards, Michel

Hello all, I am happy to announce the availability of our 3.2.1 release! For a list of changes, please take a look at this post. This is a minor release to fixed the bugs introduced in 3.2.0 when we introduced support for I2CS devices (including FanLinc). In addition, we added support for a couple of new INSTEON devices. Know Issues None Things to test: - Make sure the programs can be loaded - Random variables - Register and manage I2CS devices, FanLinc, and TempLinc - Make notifications are working again using friendly names (i.e. fname lname:account) Important Information 1. Important If you have already installed a self signed certificate and your current firmware is 2.7.10 and below, you must reinstall a new one before the upgrade. 2. Please note that Safari does not support SSL session reuse and thus might take an exorbitant amount of time to communicate with ISY. As such, when using 2048 bit SSL, it's best not to use Safari. 3. If you are using the Irrigation Module and are upgrading from releases prior to 3.1.5, you must edit the programs using Irrigation variables and save the programs again. Irrigation module is no longer on promotion 4. Upgrading from 3.1.3 and below: If you are using WeatherBug Module's Rain Today in your programs, please note that the precision has changed from 1/10 to 1/100 and thus your programs might not run properly 5. For a discussion of variables, please look at our Program Variables forum. Instructions: 1. Please backup your ISY (File | Backup ISY). If you are backing up a 3.1.6 system, please note that the backups are corrupted. If you have a backup from prior releases, you should be OK 2. Please download the firmware for your platform - please do not unzip ISY 99i Series ISY 994i Series 3. Login to the Admin Console and choose Help | Manually Upgrade [the name of your system] 4. Choose the file saved in step 2 5. After the upgrade, ISY reboots. Please do ensure to clear your Java Cache 6. IMPORTANT Once upgrade is completed and ISY reboots, use any of the following methods to access your ISY's Admin Console: a. 99/994i - http://isy/admin - applet (Windows only) b. 99/994i - http://isy/admin.jnlp - Java application (Windows only) c. http://your.isy.ip.address/admin - applet d. http://your.isy.ip.address/admin.jnlp - Java application e. http://www.universal-devices.com/99i/3.2.1 - applet f. http://www.universal-devices.com/99i/3.2.1/admin.jnlp - Java application Dashboard - not fully supported - http://www.universal-devices.com/99i/3. ... board.jnlp 8. Please backup your system again Thanks and with kind regards, Michel

Hello all, We have not done anything for LED brightness in 3.2.x ... the only changes where I2CS related so they might have had a negative impact. We shall take a closer look. With kind regards, Michel

Hi, Just a caveat, if you have thermostats, sending All On/All Off will cause the thermostat to go to an undefined state. I strongly advise against using it. With kind regards, Michel

Hello Eric, Apologies for tardy reply. It should take seconds. I suspect that you didn't accept the security warnings and thus Java is throwing an exception. The best thing to do would be: 1. Clear your Java cache 2. Clear your certificates (Java Control Panel | Security | Certificates) 3. Make sure you are local to ISY 4. Go to https://www.universal-devices.com/ssl/insteon With kind regards, Michel

Hello bryanlut, I am so very sorry to hear. Since you can communicate with one of your devices, i do not think the PLM is dead. Has anything else changed in your INSTEON network? One suggestion I have is - if and only if possible - move your PLM to a different location and see if you can get some of your other devices to link. With kind regards, Michel

Thanks Jim ... we shall look into it. With kind regards, Michel

Hello remedy1234, Are you using up/down or are you setting specific set points? It should ISY does not do anything differently. If your program is in Program Auto, the only way ISY can make permanent changes is if you change the mode to something other than Program.

Hello LeeG, Thanks so very much for the detailed analysis. We're investigating and should find a fix shortly. With kind regards, Michel

Hi Andy, instead of using backspace, double click on the row and try to edit. Is it still cut off? With kind regards, Michel

Hi Jim, would you please go to Help | About and let me know: 1. The UI Version 2. A list of modules you have installed Also, is it that ISY locks up or just the Admin Console? With kind regards, Michel

Hello remedy1234, As MikeBro correctly notes, if your thermostat is in Program mode, ISY cannot adjust the set points properly. With kind regards, Michel

Hello rwright, Are you local to ISY? Also, would you please reboot ISY, look at the front panel, and let me know the sequence of lights on the front of the unit? With kind regards, Michel

Hi Tim, How are you adjusting the set points on ISY? Are you using up/down or are you going to specific set points? With kind regards, Michel