Michel Kohanim

Hi Vince, Thanks so very much. We just ordered two more HTC EVO phones and Nick, the inventor of ISY AJAX, is going to take a look and see how we can make things look nicer on Droid. With kind regards, Michel

Blaine, Thanks so very much for the feedback and we do not consider feedback and suggestions threatening. As much as we would love to add as many features as possible but our resources are finite and thus we do things based on priorities and ROI. And - I very much hope I am not offending you: promises of large sales we have had in 100s some of which we implemented but all of which produced zero sales. If this is as important as it sounds, we would be delighted to make a project out of it for you provided that we understand the ROI and your level of commitment. Above and beyond this, our focus is to methodically add features for our existing customers base. We do have forecast in our requirements but it has low priority. With kind regards, Michel

Hi kaisersoze, I am so very sorry ... I must have missed your post. mohansen/kaisersoze, unfortunately it would be quite difficult for ISY to sense power loss without a battery backup and an extra switching power supply to switch to battery during power loss. One ugly solution might be the support for pinging a network device (something that's always on such as your router) and if that does not respond then assume power loss. But, this is ugly too since one has to make sure not to issue too many pings and all sorts of other side effects such as router is not responding but you still have power. With kind regards, Michel

Hi Vince, It's working intermittently on my HTC phone. Trying to get to the root cause. With kind regards, Michel

Hi Andrew, Thanks so very much for the detailed explanation. ISY does store everything that has to be restored in a configuration file including memory locations. An Event Viewer trace would be of great importance in finding any bugs. Hi ronbo, I am so very sorry to hear. Before restoring your KPL, did you do a compare to see if there are any mismatches? Also, what was the root cause of any problems before restoring the KPL? With kind regards, Michel

Hi barkster, Thank you. There was one more report of an issue similar to yours and the problem was fixed (temporarily) by resetting the thermostat (just unplug the dongle and plug it back in). Also, please note the following: 1. Cool setpoint cannot be greater than Heat setpoint ... the thermostat will automatically revert 2. The difference between cool and heat setpoints cannot be more than 2 ... again, the thermostat will automatically revert With kind regards, Michel

Mr. Blackstone, It would be best if you tried your own mail server and left the From field blank. If you do not have one, please do let us and we'll help you set one up on gmail. With kind regards, Michel

Hi andrewm, It would really help us if we have an event viewer output so that we can debug and find root cause. Or, at the minimum, some history such as: 1. How was this device added originally? 2. What was the nature of misbehavior? Obviously, had we found the bug, it would have been fixed and thus not a pita. I appreciate your help. With kind regards, Michel

Hello Phil, Apologies for the inconvenience. When you are local, the Admin Console uses the HTTP port. When you are report, it's up to you to add the :port suffix to the URL. All this said, I am sure this must be frustrating. Please do not hesitate to contact us (below) so that we can schedule a remote session and configure your router for you. With kind regards,

Hello Jim, Apologies for the inconvenience. Do you mean 3.1.17? I think we may have found a bug in the UI in 3.1.17. Please try leaving the "From" field blank. Please do let us know what you find. With kind regards, Michel

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