Michel Kohanim

Hello all, I am happy to announce the availability of our 3.1.5 release! For a list of changes, please take a look at this post. IMPORTANT 1. Since we added support for 2048 bit SSL, we had to change some of the networking libraries so as to make sure the overall system performance is not impacted. For instance, during key handshake, in previous releases, most other sub tasks would stop. In this release, those sub tasks continue to function although at a slower pace (the CPU is hard at work). As such, please do be kind enough to watch for any network anomalies. 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, you must edit the programs using Irrigation variables and save the programs again. 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: - Irrigation Module -- Help | Purchase Modules | Irrigation Module ... you can use coupon code irrigation-promo-11 for $15.00 off (total will be $4.00) - New supported devices - Network activity 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) 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. 99i - http://isy/admin - applet (Windows only) b. 99i - http://isy/admin.jnlp - Java application (Windows only) a. 994i - http://or/admin - applet (Windows only) b. 994i - http://or/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.5 - applet f. http://www.universal-devices.com/99i/3.1.5/admin.jnlp - Java application Dashboard - not fully supported - http://www.universal-devices.com/99i/3. ... board.jnlp Thanks and with kind regards, Michel

Hello all, I am happy to announce the availability of our 3.1.5 release! For a list of changes, please take a look at this post. IMPORTANT 1. Since we added support for 2048 bit SSL, we had to change some of the networking libraries so as to make sure the overall system performance is not impacted. For instance, during key handshake, in previous releases, most other sub tasks would stop. In this release, those sub tasks continue to function although at a slower pace (the CPU is hard at work). As such, please do be kind enough to watch for any network anomalies. 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, you must edit the programs using Irrigation variables and save the programs again. 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: - Irrigation Module -- Help | Purchase Modules | Irrigation Module ... you can use coupon code irrigation-promo-11 for $15.00 off (total will be $4.00) - New supported devices - Network activity 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) 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. 99i - http://isy/admin - applet (Windows only) b. 99i - http://isy/admin.jnlp - Java application (Windows only) a. 994i - http://or/admin - applet (Windows only) b. 994i - http://or/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.5 - applet f. http://www.universal-devices.com/99i/3.1.5/admin.jnlp - Java application Dashboard - not fully supported - http://www.universal-devices.com/99i/3. ... board.jnlp Thanks and with kind regards, Michel

Hi Brian, Those options are only available on PRO version. With kind regards, Michel

Hi IM, Thank you. Have to figure out how to reproduce it. With kind regards, Michel

Hello IM, Definitely a bug and it's fixed in 3.1.5 (should be out today). With kind regards, Michel

Hi Zick, ISY tries to reconstruct everything based on available devices and configurations in ISY. So, let's say you had a scene with 3 devices/controllers: 1. You removed 2 of them with set button out. ISY now thinks that this scene has only one device 2. You add back the device; but since the device was not programmed by ISY to be removed from the scene, the device still thinks that it's part of a scene with 2 other controllers. But, ISY cannot find such as scene, so it assumes that one should be created I totally understand your desire NOT have 00 as the firmware version. This said, except for very specific versions of specific devices (e.g. KPL v2 which is obsolete), ISY does not use the version information. As such, if you do not have any specific questions/problems, please leave the system alone and as is unless you would like to rebuild the whole thing from scratch (unfortunately). With kind regards, Michel

Hello IM, Would you please let me know if you received an email after cycle complete? I think the problem is that the variables in the email are both pointing to water deficit (yesterday). With kind regards, Michel

Hello johnnyt, If you are getting a new PLM, you should replace it. No, this is not like factory reset. ISY rebuilds the links in your PLM and devices. Once you receive your new PLM, please follow the instructions in the link below: http://www.universal-devices.com/mwiki/ ... _.28PLM.29 With kind regards, Michel

Hi IM, Ah, I see. This is very good to know. So, traffic from turning on one scene may impact the accuracy of the progress bar. One last question, when the progress bar finally finishes and if you turn on/off a device, do you see the status updated on the Admin Console? With kind regards, Michel

Hello Spero, ISY uses queues to queue up operations: AL&N = Programs VAR = Variables SND = System Messages (such as whether or not the system is busy) Causes for the above: 1. Infinite loop in programs 2. Excessive (sub-millisecond) traffic from one or more of your devices (noise disguised as traffic coming from PLM). This is specifically the case for X10 messages The first thing I recommend is to disable all your Programs (on My Programs, choose Schedule and then uncheck Daily, Add to If, then save. If this fixes the issue, then the problem is case 1. If not - this might take a little longer - use Event Viewer on the last level (Device Communications ...) and look for any strange activity. With kind regards,

Hello rtt3821, I think it would be best to schedule a tech support call with our tech support team. With kind regards, Michel

Hello rt3821, sorry I missed your last post. It should be back up. Zick, UPnP is not very reliable for what you are trying to do. I recommend doing it manually. With kind regards, Michel

Hello Zick, I am not sure what you are referring to. What LeeG is saying is that if you DELETE a device from ISY, then ISY DELETES all links from it. If you have devices that have never been registered and then deleted from ISY, then you can use those options during linking/registration of the device to ISY. With kind regards, Michel

Hello Peter, If you use status, then the only time the program runs is if the status changes. As far as your other question, it's really subjective. Both approaches have the same efficiency. With kind regards, Michel

Hello Ski, I think it's best to start fresh with a new installation mostly because of the size of your installation. To backup your ISY programs, Right mouse click on My Programs and then choose Export. With kind regards, Michel

Hello IM, Thank you. Sincere apologies for tardy reply. So, in essence, when these query programs are run (which turn on a few buttons on KPLs), the progress bar does not behave properly. Now, is it possible that when the devices within the status scenes are updated, you have programs that do things based on the status of those devices? I really do not think the problem is the status programs itself BUT it's the result of thereof which is probably causing a range of other device activities/querying, etc. With kind regards, Michel

Hello johnnyt, This usually points to a defective PLM (unless you actually factory reset your PLM yourself). If you restore the same PLM, then in most cases (if nothing has changed), ISY does not touch the end devices. It simply recreates PLM links as it thinks the PLM should have it. With kind regards, Michel

Hello johnnyt, Please go to Tools | Diagnostics | Show PLM Link Table, click on Start and then wait for it to complete. When done, click on the Count button. How many links are there and how many devices/scenes do you have? With kind regards, Michel

Hi ski2020, My recommendation is to start with a new installation and a new PLM. Keep the old PLM in tact for backup. Also, backup only your programs, restore them and then updated them based on the new devices. This way, you are not bound by having to use the same device/location combination in the new house. BTW: congratulations on your new house! With kind regards, Michel

Hello IM, Can you copy/paste your status program? Progress bar is the best guess based on the number of operations on the queue and average time it takes to complete them. With every addition of commands, the number should increase and thus the progress bar might go multiple times. With kind regards, Michel

Hello aweaver, Please do be kind enough to send an email to tech@universal-devices.com and we'll send you the information. With kind regards, Michel

Hello Brignolo, I am not aware of any INSTEON device that can control HIDs or circuit breakers. The closest one is the 270 load controller but I am not sure how it would behave if it needed to control breakers. With kind regards, Michel

Hi Illusion, The errors are benign ... I really do not know what supports beep except those that explicitly have beep in their title. SWLs have gone through many revisions which have made tracking capabilities rather difficult. You might want to try Beep command on them and see if they beep. With kind regards, Michel

Hi Lee, Thank you and apologies for not reading your post more thoroughly. Yes, that does make sense ... as you said, the main problem is that we do not yet support PLM as a device so the messages received will be discarded since we do not know what to do with them. Thanks as always and with kind regards, Michel

Hello ryarber, Thanks so very much. There's indeed a bug where Irrigation Requirement is over-written by WB update if and only if they happen at the same time. This has been fixed for 3.1.5. This said, please note the following: Waits are interruptible. This means that if Irrigation Cycle changes in any shape or form such that the condition: - Is set to false, then the rest of the program will NOT run. The program stops at the Wait - Is set to true, then the program RESTARTS from the beginning So, it's best for Irrigation Complete to be the last entry in the Then. With kind regards, Michel