Michel Kohanim

Hello intellihome, Yes, you can restore your 2.7.15 backup on 2.8.16. Please do make sure you have a good backup before formatting the SD Card. With kind regards, Michel

Hello Candide, Would you please check the error log and see what type of errors you see for CLI-WBUG? With kind regards, Michel

Hello bocaray, Please read the following article: http://www.watchguard.com/infocenter/ed ... 135177.asp At the bottom they have instructions for setting up NAT 1:1. With kind regards, Michel

Hello gadgetfreak, The nodes behave as follows: 1. Fan ... the status of the FAN 2. Heat ... the thermostat is CALLING for heat 3. Cool ... the thermostat is CALLING for cool Please note that "calling" is NOT the same as mode. Mode is what you expect the thermostat to do and "calling" is what is currently happening in the thermostat. With kind regards, Michel

Hello gadgetfreak, © is for Cool setpoint and (H) is for Heat setpoint. With kind regards, Michel

Hi guys, thanks so very much for the update. Illusion, the forum duplicate was my bug ... I hit the submit button then quickly pressed back to check something (thinking that our slow forum would never be able to actually post the topic in that short amount of time) and then submitted again. Unfortunately I have yet to figure out how to merge the posts. With kind regards, Michel

Hello sperok, Size of queues are event dependent. This said, having programs that check for conditions and set variables or call other programs are not a problem; you can have 100s of them all happening within fractions of a second. The problem arises when your programs call device dependent activities (such as querying a large scene or turning on/off 10s of large scenes quickly and outcome of which would cause other programs to call other scenes, etc.). In short, you would want to limit things such as: Query My Lighting every 1 second (the query itself takes a lot longer than 1 second and with all the events generated, you will eventually fill up the queue). With kind regards, Michel

Hello Elvis, We do surely take these issues quite seriously and this bug was an oversight. This said, however, as reliable and robust we would like ISY to be, it was never designed with those application in mind. This is clearly stated in our Disclaimers & Terms/Conditions of Use and especially since we added support for door locks. In any case, I do apologize and this shall be fixed as soon as possible. With kind regards, Michel

Hello Elvis, You are 100% correct; the fact that you are 1000s of miles away and with a system that does not respond is quite bad. I had no clue this bug would show itself under any other circumstances besides having ELK RP connected and thus kept postponing this fix till we have our ELK module. I do apologize and this shall be fixed in the next release. Hello dennisric, Are you referring to the number of columns on the AJAX interface? If so, you would not actually see any change unless you are on a mobile device with a low resolution. With kind regards, Michel

Hi Ski, Yes, but if and only if you do not have the latest 2413S. Please make sure you take a backup before you do anything. With kind regards, Michel

Hello Elvis, Thanks so very much for the detail steps to reproduce. Have you tried 3.1.5? The main issue is that ISY makes a connection to ELK and keeps that connection open. Obviously, the system should not hang when ELK/router are rebooted but, at the moment, ISY does not know that any of those systems are rebooted. I think that during reboot, ELK sends a command/status that ISY does not expect. We do not use watchdog timers since we would never ever be able to figure out the root cause. We will definitely look into this and see if we can fix it before the ELK module. With kind regards, Michel

Thanks IM! Thanks Mark. With kind regards, Michel

Hello rossarmstrong, As you suggested, it's quite subjective! My personal preference is using scenes wherever they have already been defined and if you have more than just a couple of devices. From my perspective: Pros for using scenes: 1. All devices respond at the same time 2. Less INSTEON traffic 3. You can add/remove devices from the scene, change on levels/ramp rates, without having to change the programs (one at a time for each device) Cons for using scenes: 1. Not as reliable especially if you have SWL v35s With kind regards, Michel

Hi IM, My pleasure. Can you please verify the fix in 3.1.5? With kind regards, Michel

Hello johnnyt, What you need to do is to have your motion sensors close to you (and the PLM). Look at the Admin Console and when you see a Green "Writing" arrow as the icon for the motion sensor, then put the motion sensor in programming mode. 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

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,