Michel Kohanim

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

Hello apostolakisl, We will look into it ... it's surely a timing issue. With kind regards, Michel

Hello IM, Thank so very much for the feedback. I will have to defer this one to the Guru himself! Hi apostolakisl, unfortunately there cannot be a tutorial since all we have is what we got from SmartHome: level for On and level for Off. And, On is a function of Off. It would be ideal if someone with a lot of time on their hands could come up with a permutation of all the on/off value pairs and their impact on the backlight. With kind regards, Michel

Thanks Illusion. With kind regards, Michel

Hello Illusion, Can you try the 3.1.7 UI and let me know if you have the same issue? http://www.universal-devices.com/99i/3.1.7 Please note that you do not have to upgrade the firmware to test the 3.1.7 UI. With kind regards, Michel

Hello j0dan, LeeG is 100% correct. This said, the internal ISY .REC file stores some of those values (such as LED brightness) in the same .REC file. As such, I still think that the problem is not necessarily LED brightness but how we handle multiple tasks trying to update the same .REC file. With kind regards, Michel

Hello LeeG, thanks so very much for the help on V2 Motion Sensors. I am not sure what to think of v2 motion sensors because this exact behavior is reported multiple times. Mine works fine but there are many others that do not and factory reset works only part of the time (so, rlebel, you are one of the lucky ones!). wuench, sincere apologies: all WSDL files are in ISY's /WEB directory. You can also find them under: http://www.universal-devices.com/developers/wsdk/[version]/ ... where, for 3.1.7, version is 3.1.7! j0dan, 1. I do not think it's the LED brightness issue but some type of resource conflict when two tasks (for instance the reader tasks and the program task, working on the same database) 2. Yes, INSTEON database records are stored in .REC files. You can restore those files but we do not have an automated way to do so except for copying the files into the SD Cards I must say that I am so very sorry for this problem and that we are hard at work to find a resolution for this. I do apologize. With kind regards, Michel

Hello Brian, I am so very sorry that somehow we lost your post. I do apologize. Can you please let me know the status and where you are with the problem? Hi Gunnersen, RL2 is not yet supported but it's high on our list. With kind regards, Michel

Hello j0dan, Unfortunately not that I know of. Of course, you could restore a backup and then restore devices but that's even more troublesome. For now, may I humbly suggest disabling those programs? We are actively trying to figure out where the bug is and fix it. thedishking, I do apologize for the inconvenience. Would you be kind enough to send your Error Log (Tools | Error Log) to support@universal-devices.com? There's a known issue where incessant DNS resolution issues may cause a system hang. With kind regards, Michel

Hi Charles, There seems to be two issues: 1. The certificate stored in Java is not the right one ... please go to Java Preferences and remove all Universal Devices certificates, clear your java cache, and then go to http://www.universal-devices.com/99i/admin.jnlp 2. Your system is using the wrong jar files and therefore it's not finding the correct resource bundles to load. I am hoping that doing the above will fix this With kind regards, Michel

Hello all, Currently known issues with 3.1.7 1. For PRO series, the batch and battery buttons do not show up for a while on the Admin Console 2. In case of too many successive DNS errors, the unit may hang With kind regards, Michel

Hi all, Currently known issues with 3.1.7: 1. For PRO series, the batch and battery buttons do not show up for a while on the Admin Console 2. In case of too many successive DNS errors, the unit may hang With kind regards, Michel

Hello all, sincere apologies for tardy reply. polexian, any further explanation to reproduce would be greatly appreciated. As far as config and admin/advanced, do you mean the Javascript interface or the Admin Console? If latter, can you please be a little more specific? j0dan, sincere apologies ... this is one of those issues that is not reproducible easily so we have to basically walk through the code and guess what could contribute to it. It seems that our guess was not correct ... back to the drawing board! rlebel, please disable Open ADR in the Electricity configuration panel. I do not think the Motion Sensor and this error are related. Once Open ADR is disabled, then we can figure out what's causing the error. mohansen, thanks for the error log. It seems that the system goes into a deadlock once there are too many DNS resolution problems. We are looking into it. With kind regards, Michel

Hello brianbhc, It all depends on the client used. Most browsers convert the user@xxx.yyyy.zzz to the proper header inside the HTTP header. If your client supports this, then the answer is yes. Otherwise, the answer is no: ISY doe not understand user@ URLs. With kind regards, Michel

Hello jpjoe, Yes, that's a correctly formatted address. The main issue seems to be that the PLM cannot communicate with the RemoteLinc. Is this regular RemoteLinc or RemoteLinc2? If the latter, then ISY does not yet support it and it will not work. If the former, would you please use Event Viewer on Device Communications level, retry, and copy/paste the output here? With kind regards, Michel

Hello cmerlino, Unfortunately ISY does not support non-toggle mode for IRLinc TX. With kind regards, Michel