Michel Kohanim

Hello all, Just wanted to let you know that Release 3.1.7 Beta is now available. With kind regards, Michel

Hello all, I am happy to announce the availability of our 3.1.7 release! For a list of changes, please take a look at this post. IMPORTANT 1. This is a major release with very many changes to address performance and system stability especially in the case of adverse network conditions. Almost all parts of the framework have been touched in one way or another. The reason for the massive changes is related to Chrome's out of band HTTPS handling and support for 2048 bit SSL certificates. Although the whole firmware has been thoroughly tested, please do note that it is still beta and thus if you have mission critical applications, installation of this firmware is not recommended. 2. Please note that Network Resource modules are now running in their own task. This might have some ramifications as calling network resources from programs no longer waits for the resource to complete. As such, a) you will experience quicker handling of network resources/programs and if you are using DSCLinc and WebLinc, your programs may behave a little differently. Please do test your network resources thoroughly 3. 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. 4. 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 5. 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 Things to test: - New supported devices - System instability and network issues especially system hang (even though the programs continue to run) - Network resources and programs For a discussion of variables, please look at our Program Variables forum. Notes: 1. ISY-26 is no longer included in the firmware builds 2. Due to the sensitive nature of supporting MorningLinc, users now must agree to terms and conditions upon Admin Console start up otherwise the dialog keeps popping up every time the Admin Console is started 3. 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. 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 OR 994i Series 3. Important (If upgrading from 2.8.5 through 2.8.14) Due to invalid Java certificate chain, please make sure to remove all Universal Devices certificates from Java: a. Close all browser sessions b. Open Java Control Panel (Java Preferences on MAC) c. Click on the Security tab. Remove all Universal Devices certificates (on MAC, click on the '-' button at the bottom) e. Clear your Java Cache 4. Login to the Admin Console and choose Help | Manually Upgrade [the name of your system] 5. Choose the file saved in step 2 MAC users: if upgrade fails, please add https://your.isy.ip.address to ISY Finder (see 3f above) 6. After the upgrade, ISY reboots. Please do ensure to clear your Java Cache 7. 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.1.7 - applet f. http://www.universal-devices.com/99i/3.1.7/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

Hi Joe, Please just wait! Obviously you can link them to your devices but please note that any device restore will get rid of those links since ISY does not know they exist. With kind regards, Michel

Matapan, You can add them as responders to scenes. One for lock and one for unlock. With kind regards, Michel

Hi Tim, Just went through this setup again and mine are working fine. Is it possible to ask for just one replacement? This makes no sense at all! With kind regards, Michel

Hello bruinlax, Apologies for tardy reply. Boy, that's quite strange. Unfortunately without a debug build, there's not much you can get out of the shell except for some run time information. Now, is it possible that vbs is losing the userid/password? If so, that would explain everything: ISY is going to DOS mode (does not allow any more access for a while). Please take a look at your Error Log and check for -100xx errors. With kind regards, Michel

Hi apostolakisl, It is very important to know how long the AC was left on. If 24 hours and they were not in synch, then I suspect a bug. With kind regards, Michel

How long was the Admin Console on? With kind regards, Michel

Hi Tim, Ok, I have 1711 Rev 2.0 installed and working properly and reliably. Here's my configuration: 1. Jumper 5 is shorted 2. I used Add New INSTEON Device and chose Motion Sensor from the list Please note that if you use anything but Automatic in Link Management | Advanced Options, then you are bound to have intermittent issues. Hope this helps. With kind regards, Michel

Hi, Yes, that's what I mean. 2 minutes is unlikely but I am not sure whether or not you were looking at Program Summary while testing ... is it possible that Admin Console lost connection to ISY? With kind regards, Michel

Hello apostolakisl, The accuracy of the clock on the Admin Console is within the past 5 minutes. So, Admin Console gets the time from ISY, does it's one incrementing, and then synchs after 5 minutes again (to reduce the load on ISY). With kind regards, Michel

Hi bruinlax, Apologies for the inconvenience. First of all, 3.1.6 is a beta release which might not be stable enough for your test cases. Can you tell me the frequency of calls to /rest? Are they quickly (say every few seconds) and does ISY have access to the outside world? Also, please note that if you bombard ISY with /rest requests - and if they are to command devices - all ISY http tasks might block till the first command is completed. So, if you have a device that is not communicating, all other tasks are going to wait. Depending on what you are doing, this might take a minute or so. With kind regards, Michel

Hi Elvis, Thanks so very much for the update. Currently we have an issue whereby if DNS is not reachable and if you have programs that use DNS service, after about an hour, we lose all our buffers (slowly). Still have not been able to figure out the cause but are very close. With kind regards, Michel

Hi Tim, Working on it as we speak. I shall keep you posted. With kind regards, Michel

Hi Tim, Thanks so very much for the update. When you link the motion sensor directly to your device, does it control the device. I am having some intermittent problems with a new motion sensor as well. We do need to get to the bottom of this since it seems to be more prevalent that I had expected. With kind regards, Michel

Hello Elvis, We were going to have 3.1.7 this morning but found a little bug which seems to be eating up buffers especially when you use Chrome. As such, I do not think we are going to have 3.1.7 released this weekend. Sincere apologies. With kind regards, Michel

Hello Steigs, The best method for factory resetting ISY is [ulr=http://www.universal-devices.com/mwiki/index.php?title=ISY-99i/ISY-26_INSTEON]outlined here[/url]. You will also have to factory reset your PLM at the minimum and all your devices if necessary. With kind regards, Michel

Hello rmlinnovator, Unfortunately we do not have any plans. This said, SmartHome has regular training sessions all of which include training on ISY as well. With kind regards, Michel

Hello Karl, I do apologize for the inconvenience. There seems to be some network issues here which would be best solved over the phone. Please do be kind enough to contact our tech support team. With kind regards, Michel

mitch236, Let me chime in. As LeeG suggested, you cannot communicate with MorningLinc UNLESS there's a link in the database you won't be able to communicate with MorningLinc from ISY. As such, please do be kind enough to follow the instruction as provided by LeeG and retry. With kind regards, Michel

Hello remedy1234, I still have not heard back from SmartHome ... the thing is that I am not even sure a new Motion Sensor will fix this issue. I finally got the new Motion Sensor and I cannot reproduce any of these problems so it's quite hard to decide what the issue is. Can you tell me the exact procedure you followed to add the Motion Sensor? Did you use the drop down and made sure your Motion Sensor is in programming mode? With kind regards, Michel

Hello buzzhazzard, Thanks for the update. Yes, you can still control your devices and your programs should work. And, yes, when you get a new PLM, all you have to do is to do a File | Restore Modem (PLM) and you should be done. One more question: have you ever done File | Remove Modem? If so, that explains all the issues because this function removes all the links from your PLM and restore will basically restore nothing. With kind regards, Michel

Hi Joe, Thanks so very much for the steps to reproduce the issue ... it did help: the problem is in the UI and not 3.1.6 firmware. This should be fixed in 3.1.7 wherein we basically had to massively change our networking framework. With kind regards, Michel

Hello kevinohara80, This is excellent! Thanks so very much for sharing ... now if we could only get a less expensive quote from Salesforce.com! With kind regards, Michel

Hello buzzhazzard, I am so very sorry but I think the PLM might have lost all its links (this does happen occasionally). What you want to do is to go to Tools | Diagnostics | Show PLM Link table, click on start, and when completed please click on the count button. If the number is 0 or low, then the PLM has lost all its links and I do recommend replacing it. In the meantime, you could try File | Restore Modem. With kind regards, Michel