Michel Kohanim

Hi Guys, Unfortunately the problem was that the loggers were not being registered in the log manager and thus the reason for not having any logs for the duration of 3.1.8. LeeG, are you saying that you cannot clear the logs? With kind regards, Michel

Hi polexian/Joe, I wished you had talked to us ... removing PLM does precisely the opposite of what you were trying to fix (you will not get any status updates from devices). Were you able to restore your backup and then restore PLM? With kind regards, Michel

Hello evilpete, I think that's an excellent idea. We should have the last updated timestamp for WB. With kind regards, Michel

Hello all, Just wanted to let you know that Release 3.1.9 is now available. Thanks and with kind regards, Michel

Hello all, I am happy to announce the availability of our 3.1.9 release! For a list of changes, please take a look at this post. This is a minor release to address the inability to download logs in 3.1.8. IMPORTANT 1. 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 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 Things to test: - Battery/Batch buttons - If you have an ActionTec router with WeatherBug, please do make sure ISY can get to the outside world and especially to WB Server - Network performance and status - 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.9 - applet f. http://www.universal-devices.com/99i/3.1.9/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

Thank you all for your suggestions and comments. 3.1.9 shall be released shortly. polexian, WHY would you want to remove the PLM from your ISY? That would KILL all your scenes and you will NOT receive any status updates from any of the devices. If you are not getting status feedback, in all likelihood, we are dealing with firewall issues. If you have already removed the PLM, you will HAVE TO restore your backup and then restore modem (PLM) for everything to work again. With kind regards, Michel

Hi Guys, Not receiving response from WB is completely normal: we do have a timeout for getting a response and if we do not get anything within that timeout, we consider the connection bad. If the server is busy, we might not be waiting long enough. And, we do not want to be waiting too long for a response from WB because it will impact the performance on other network resource modules. With kind regards, Michel

Tom, I am not sure I am comfortable with setting Java temp directory to the user directory. We do have other state information which we store in the temp directory as they should be. As I mentioned before, we use generic system wide properties that should behave the same across platforms. In the case of MAC, it does not. We will have to revisit this when we have more time. With kind regards, Michel

Hi Tim, thank you! Hi Mitch, Kaspersky is notorious for false-positive scenarios (and so is NOD32). With kind regards, Michel

Hello apostolakisl, Thanks so very much for the feedback. We'll surely revisit this issue as soon as we are comfortable system stability. With kind regards, Michel

Hello Mitch, Sincere apologies for all the troubles you have been having. Whatever you do, please do NOT factory reset your ISY as it will not fix this problem. This problem is related to the firewall software on your laptop. Have you recently updated the firewall software on your laptop (or installed a new one)? With kind regards, Michel

Hello all, With sincere apologies for the log issue. This has been verified as a bug and has already been fixed. We are currently debating on having a minor release to address this issue (firmware only) or wait for more bugs before releasing 3.1.9. Your comments and suggestions are quite welcome. In the meantime, I would sincerely appreciate it if you could test network/system stability and behavior especially when it comes to network resources. Thanks and with kind regards, Michel

Hi matapan, polexian is correct. Please note that the last few firmware updates revolved solely on eliminating system lockup regardless of the case. We have had discussions of using watchdog timers but we are striving for zero lockup. So, in case you were on 3.1.8 and you managed to lockup the system, please do be kind enough to let us know the steps to reproduce it so that we can fix it. Thanks and with kind regards, Michel

Hello apostolakisl, Thanks so very much for the update. We did go through the code yet again and that path has not been updated: i.e. we do make sure that the sequence of activities line up before processing the events. This said, we'll do a more thorough review once we are satisfied with stability of the system as a whole. With kind regards, Michel

Hi Tom, Yes, absolutely: System.getProperty("java.io.tmpdir"); With kind regards, Michel

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

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

Hello all, I am happy to announce the availability of our 3.1.8 release! For a list of changes, please take a look at this post. This is a stability/minor release to address issues found in 3.1.7. IMPORTANT 1. 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 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 Things to test: - Battery/Batch buttons - If you have an ActionTec router with WeatherBug, please do make sure ISY can get to the outside world and especially to WB Server - Network performance and status - 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.8 - applet f. http://www.universal-devices.com/99i/3.1.8/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

Thanks LeeG for verification. It shall be fixed in 3.1.8. With kind regards, Michel

Hi Tom, I do apologize ... I cannot fathom why Java would use a temp directory that MAC clears upon boot up. I guess this is yet another Java/MAC issue (I side with Java on this one since). We shall have a closer look but I must confess that this does not have a high priority and it's NOT trivial: our Java code is generic and it uses standard Java properties. It would be very difficult to have a "special" case just for MAC. It's not trivial since we have had to do this "special" case in multiple places and MAC is not very Java friendly. With kind regards, Michel

Hello ELA, I would hold off for 3.1.8 which should be out within a day or two and is much more stable. As far as RL, battery is an explanation but I do not think it's the cause since you got it to go to programming mode without it complaining. Obviously, you are the master of signal issues: was it close to an Access Point? Hello polexian, Thanks so very much ... good thing that at least the IR is working. One question with regards to status: did your ISY's IP address change (after the upgrade) AND do you have a firewall which might have had the old ISY's IP address in the white list but not the new one? Hello rlebel, That's quite strange! Are they all reported as 2420M? Has anyone else out there has the same issue? With kind regards, Michel

Hi Tom, Supporting multiple instances of Admin Console is definitely on our list and shall be done. As far as the other problem, the state of that dialog is stored in your temp directory (or what MAC considers temp). Is it at all possible that something or some program clears the user/temp directory on your MAC? With kind regards, Michel

Hi Tom, This has never been brought up as an issue and thus, if a bug, it has not been fixed. In all cases, though, I strongly recommend upgrading to our official 2.8.16 release. Please note that if you have installed an SSL certificate for your ISY, you must reinstall a new one before upgrading to 2.8.16 (--> you cannot upgrade remotely). Also, please make sure you are using the correct URL for the Admin Console. For the official release, the URL is http://www.universal-devices.com/99i/admin.jnlp . With kind regards, Michel

rlebel, you should. Please make sure you are using the latest UI. ELAAre you on 3.1.6 or 3.1.7? 3.1.6 did have some anomalies and intermittent communications which 3.1.7 should have fixed (see below my response to polexian). I truly apologize and I know how frustrating it could be to have to spend time on something that should be so simple (such as adding a replace function for dimmerrelays). As far as RLs with !, if ISY can indeed communicate with them, all you have to do is to press RL buttons and see if the status gets updated. polexian IR issue, we cannot reproduce either. It might be intermittent. Status updates: this should have been fixed from 3.1.6 to 3.1.7. As much information you can provide it would be appreciated. With kind regards,

Hello ELA, For each scene, there are two bytes in the Switch's link database which define the on level and ramp rate. For Relays, these values are 0s. A long time ago, when we tested replacing a switch with dimmer and vice versa, there were too many unexplained behavior that we decided not to support the replace function between unlike device types (mostly for support reasons). I am so very sorry I cannot give you a better answer. With kind regards, Michel