Michel Kohanim

Hello Baypointe, The Floorplan does indeed expand the tree but you should see another dialog. Please note that we have not done anything with the Floorplan for more than 3 years now and it shall be removed in one of our future releases. As far as intermittent issues, I think it would be best to setup a call with our tech support team rather than going back and forth on the forum. Since the log shows that the status changed (system means that the device sent a response to ISY), then I suspect that the device is sending something to ISY on its own. This means that the device has been linked to ISY. So, what you need to do is to figure out to what devices is this device linked. j0dan, 3.1.8 or 3.1.9? With kind regards, Michel

robandcathy, Please upgrade to 3.1.9 as soon as you can. 3.1.6 had some bugs including a corrupted backup ... so, if you have a backup from 3.1.6, it's corrupted. The reason you see those errors is because Java has not been configured for your browser. You may want to use the application: http://www.universal-devices.com/99i/admin.jnlp With kind regards, Michel

Hi Tim, I am not sure what you are doing but something is quite amiss! The error says that you are trying to access the SSL port (443) using HTTP. What URL are you using? Have you reconfigured your network? You might want to try our website URL for the current firmware version you have in your ISY: http://www.universal-devices.com/99i/[version]/admin.jnlp If you have our official 2.8.16 release, you can simply remove the version from the URL. With kind regards, Michel

polexian, Finish does the same exact thing. In all cases, we have to take the PLM out of linking mode and we wanted this to be explicit by forcing the use of the Finish button. Moshe/rlebel, would you please let me know: 1. Which iPhone application you are using? 2. Do you have this problem locally or when on 3G? With kind regards, Michel

Hi polexian, Yes, I did! X should NOT close that dialog. Only clicking the Finish button should. If clicking the Finish button does not close that dialog, then there is a bug. This said, based on your previous problems with the Admin Console, I still think you have a conflict with previous version of Admin Console. I strongly recommend clearing your Java Cache and then going to http://www.universal-devices.com/99i/3.1.9/admin.jnlp . With kind regards, Michel

Hello ELA, I guarantee you that the problem is firewall and, in 99.99% of the cases, the filters applied by the firewall are NOT removed even if you disable the firewall. What we need to do is to put ISY's IP address (or URL) in the trusted zone/whitelist for Avast. As far as the other question, there are two types of information: 1. Configuration such as nodes, system/network config, etc. which are PULLED by the Admin Console from ISY. This will not pose any problems to the firewall 2. Status updates (things that might change frequently) which are PUSHED to the Admin Console in which case the firewall might block it since it might consider it as an attack With kind regards, Michel

Hello all, sincere apologies for tardy reply. ELA, please do contact our tech support and let us help you get unfrustrated! The problem is firewall blocking ISY from sending updates to the computer. As far as the program not running, that's a little more serious and it would really help if our tech support team can log into your system and see what's going on. Tim, are you still having issues with WOL not being sent? I did a quick test and it works fine here. As far as the errors, it does not make sense because we now log authentication errors only if the attempt is greater than 1. Who is 192.168.0.167? Is that DSCLink? io_guy, do you always send the userid/password with every request from DSCLink? With kind regards, Michel

Hi polexian, Thank you. This does not make sense unless the computer was trying to use the old version of the UI. Would you be kind enough to let me know which URL you use to access ISY? With kind regards, Michel

Hi Joe, Thanks for the update. I am a little confused, the only way to remove the PLM is through File | Remove Modem (PLM). Are we talking about the same thing? Or, did you have the HouseLinc PLM (or some other PLM) linked to ISY? As far as statuses disappearing, you mention HTML. Are we talking about our HTML page OR are we talking about the Admin Console? With kind regards, Michel

Hello LeeG, thanks so very much for the clarification! Teken, the reason you are not seeing the status of devices at work is probably because you either have corporate firewalls or a software firewall which blocks ISY from publishing events to your computer at work. Do you know what type of firewall you have? With kind regards, Michel

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