Michel Kohanim

Hello apostolakisl, ISY programs are event driven and thus evaluated every time the event applies to conditions in the program, the program is evaluated. The only exception is integer variables (not state variables). With kind regards, Michel

Hi Teken, It basically means that the last subscriber didn't close the session properly and ISY expired it because it didn't respond to events. It's benign as long as it does not happen by itself and throws you out. With kind regards, Michel

Hi barkster, Thank you. Quick questions: 1. Do you ever use the All On/All Off button? 2. Do you or have you in the past used SmartLinc in combination with MobiLinc? With kind regards, Michel

Hi Vince, Thanks so very much! With kind regards, Michel

Hi Vince, We will look into this ... can you tell me how does the interface look on your computer's browser? With kind regards, Michel

Hi barkster: 1. What mode is your thermostat in? 2. What's your firmware version? With kind regards, Michel

Hello all, Thanks to all your help in test and debugging, 3.1.17 is now our official release. With kind regards, Michel

Hello all, Thanks to all your help in test and debugging, 3.1.17 is now our official release. With kind regards, Michel

Hello all, Thanks to everyone who went through the 3.1.x Beta Cycle, I am happy to announce that 3.1.17 is now our official release. For a list of changes, please take a look at this post. If you are already running 3.1.17, no other action is necessary. For those new to 3.1.17, the most important features included in this release are: 1. Program Variables 2. ELk Module 3. Irrigation Module 4. Performance improvements 5. Support for Zigbee RCS Thermostats/Load Controllers and Brultech Energy Monitors in 994iZ Series Important Information 1. Due to the sensitive nature of supporting MorningLinc/ELK Security Systems, 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 2. 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. 3. 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 4. 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. 5. 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 6. 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 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 ISY 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 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/ - applet f. http://www.universal-devices.com/99i/admin.jnlp - Java application Dashboard - not fully supported - http://www.universal-devices.com/99i/dashboard.jnlp 8. Please backup your system again Thanks and with kind regards, Michel

Hi Andy, We are on track for the SEP version by beginning/mid March. With kind regards, Michel

Hi johnnyt, Yes, correct on all counts. With kind regards, Michel

io_guy, Sounds good. We'll investigate the level of complexity ... just have to find the right balance between functionality and generic-ness. With kind regards, Michel

Hello everyone, We did send an email to WeatherBug and got a canned response back. I think it would be wise for everyone with missing data points to contact WeatherBug directly. With kind regards, Michel

Hello morreale, I am afraid that there's really something wrong with the INSTEON setup. What you are experiencing is not normal and adding queries and checking the status simply masks the cause of all these problems. Is it possible to run the scene test during those times that the programs are supposed to run? Perhaps at those moments there are devices on that contribute to the instability of INSTEON signals. With kind regards, Michel

Hi johnnyt, Please do be kind enough to contact Bob directly. There's something very wrong with your setup. We do have very many customers with HS plugin and none have reported the issues you are. With kind regards, Michel

Hi Andrew, I agree with all your points. At the end of the day, the Admin Console should give you the diagnostic tools you need. With kind regards, Michel

Hello morreale, Thank you. May I assume that in some cases these devices do in fact respond properly? We basically have to find a pattern. With kind regards, Michel

Hello auger66, Thank you. Can you please take a look at your error logs and look for any -5000x errors? With kind regards, Michel

nlaredo, Our pleasure and thanks so very much for taking the time to let us know! With kind regards, Michel

Hi johnnyt, Please do send an email to support@universal-devices.com and let's setup a remote session. There's something either wrong with your unit or with how you have the programs running. I still do not understand why your system gets busy after each save unless there are many things running and causing heavy load. Those errors basically mean that client, such as the Admin Console, sent a close notify but has not yet closed the socket properly. The only times those messages should cause alarm is if they are repeated every 10 seconds for more than 3 minutes. With kind regards, Michel

Hello no clue, As long as I know, iRule does not yet support ISY feedback. With kind regards, Michel

Hi johnnyt, Thank you. I think it would be best for you to send all those programs impacted by this variable to support@universal-devices.com. There's basically nothing wrong with this program and I am very much concerned that there are things happening in your system causing it to be slow. In the meantime, when you have slow response times, can you please pay attention to the activity on the Mem light on ISY? That would give us an indication of how much activity there is on the file system. I am still thinking that there might be some tight loops somewhere causing all the performance issues. If all else fails, I would like to login to your system remotely and see what's going on. And, a final thought, in most systems the bottle neck is usually the file system (including on all computers except perhaps SSDs). As I mentioned before, ISY puts a lock around each file and thus if you have multiple tasks requiring the lock, obviously there's going to be a performance hit. With kind regards, Michel

Hi auger66, Was it that you didn't receive any notifications or was it that you got wrong notifications. If you didn't get any, did you check to see if the program actually ran? As far as TriggerLincs, there's a big problem with these devices and that is the fact that they cannot be queried. So, if ISY is rebooted, there's basically no way to figure out what state they are in. With kind regards, Michel

johnnyt, I do apologize for not getting back to you sooner. Garbage collection means nothing to us because we manage the whole memory. We actually know where each object is in the memory. As far as SD card read/write, io_guy is 100% correct and we do have wear_leveling. We have systems out there that have been running for more than 3 years without reboot. As far as notifications, whenever you change the state variable, all programs depending on it are re-evaluated. Can you copy and paste the program for which you have problems with notifications? With kind regards, Michel

auger66, I do not understand why you had to redo all your programs. The mail server configuration piece has nothing to do with programs. With kind regards, Michel