Michel Kohanim

Hi Peter, Thanks so very much: this is great! I have moved up the priority now that we have this public domain version! We should have it implemented in one of our next releases. Thanks again and with kind regards, Michel

Hi Peter, The main problem is that the paper itself is copyrighted. We contacted the contact person on the paper at least twice but he never replied. From business perspective, we might be liable in case they want to exercise their copyright. I welcome any pointers, contacts, documents, links etc. which would explicitly state that the algorithm could be used freely or via some type of agreement. With kind regards, Michel

Hello RLIKWARTZ, Can this program be enabled? Can you make a simple program that loops through some iterations: 1. Enables program A 2. Runs Then on program A 3. Waits few seconds In Program A, in the Then simply have it disable itself. While this is going on, please go to the Program Summary tab and notice the enable/disable status of Program A. If it disables itself then there must be something else wrong somewhere else. With kind regards, Michel

Hello Peter, Unfortunately not because the algorithm is copyrighted and we have not been able to get the organization to respond to our queries. Sorry. With kind regards, Michel

Hello Mahon, I tried the original program but I really do not think status vs. control is going to make any difference. With kind regards, Michel

Hello Mahon, We tested your exact program here and it always worked fine. This is a little strange because, although a great idea (using Control vs. Status), I do not think it's going to solve the problem you are having! With kind regards, Michel

Hello stevehoyt, What is happening is that ISY cannot communicate with the thermostat ... is it possible to do a swap? i.e. plug the good dongle to the bad thermostat and vice versa. If the problem moves with the dongle, then you have a defective dongle. If the good dongle stops communicating with ISY, then the problem is that the signal is not reaching your thermostat. With kind regards, Michel

Hi Hult, In addition, the method should be GET and not PUT. With kind regards, Michel

Hi Darin, ISY is fully capable of executing your algorithm + more. This said, though, ISY does not allow you to write shell scripts ... instead, you would use ISY programs which are created using Admin Console. Please checkout this article for more information on ISY programming: http://www.universal-devices.com/mwiki/ ... e#Programs . Furthermore, ISY is event driven so the status of all your devices are evaluated as they change: you can have programs based on changes in status and therefore you would not necessarily need your second program to query the status. With kind regards, Michel

Hello dcardellini, Thanks so very much for the update. So, basically, no proxy settings are needed when you use PUTTY-SSH. That's awesome! I have to give it a try ... With kind regards, Michel

matapan, Please call our tech support to schedule a call. mjtyson, You should have a Universal Devices certificate in the Security tab. If you don't, then you will have all sorts of problems. I do use iMAC and I do have Universal Devices certificate. With kind regards, Michel

Hi Ryan, It has to be in X501 format. Also, hopefully your certificate is older since I noticed that GoDadday no longer provides 1024 bit security (their weakest is 2048). With kind regards, Michel

Hi all, Apologies. Confirmed and shall be fixed in the next release. The problem is only for Program Heat/Program Cool. With kind regards, Michel

Hi simonsez, I am not sure what "my own certificates" mean. What you have to do: 1. Make sure you are local 2. Create a Certificate Signing Request (SSL Certificate Management | Generate Certificate Request to CA) 3. Send it to your CA 4. Once it's signed, then use SSL Certificate Management | Receive Certificate from CA and Install Please note that max strength for ISY is 128 (1024) and not higher. You can always use CACert.org to create free certificates. With kind regards, Michel

Please try adding the proxy to your Java Control Panel | Networking and retry. With kind regards, Michel

Hello stevehoyt, This does not make sense. I tested this very many times and I get the setpoint. Please make sure you have 2.8.16 by go to Help | About. With kind regards, Michel

simonsez, Nothing goes to our server; the only thing happening is that the applet is downloaded from our server, searches for your ISY on the local network (that's why you cannot do it remotely), and then from then on the interaction is between ISY and wherever the Admin Console is running. With kind regards, Michel

Hello Mahon, The next time this happens, please go to Program Summary tab and check the last runtime column. Is it as you suspect (say in the morning at 10:00 AM)? Also, when the motion sensor turns on the light, does ISY show the correct state for both the motion sensor and the light? If not, then the problem is perhaps residual links in your Motion Sensor responding to some unrelated event. With kind regards, Michel

Hello matapan, Please try using http://www.universal-devices.com/99i/2.8.16/admin.jnlp to upgrade. This is very important! NewTech, thanks so very much for the update! It's quite a relief!!! With kind regards, Michel

Hello stevehoyt, I just checked the HTML page and it does indeed have the setpoints show up. Can you tell me in what mode is your thermostat? With kind regards, Michel

Hi Bjorn, REST uses HTTP priority which is one of the highest priorities. By not responding, what do you mean? Is it possible that you have a low timeout set for your connect/read timeout in the client? With kind regards, Michel

Hello dcardellini, Thanks so very much for the update. Unfortunately, you will have to manually set the proxy in Java Control Panel (Control Panel | Java | Network Settings). I assume currently your settings are direct and do not use the proxy. With kind regards, Michel

Hello all, Release 2.8.16 is now available: http://forum.universal-devices.com/viewtopic.php?t=5958 With kind regards, Michel

Thanks again to everyone for helping with this Beta cycle. Release 2.8.16 is now our official release. With kind regards, Michel ---------------------------------------------------------------------------------- Hello all, Thanks so very much for your continued support and help during this beta cycle. At this point, this release is quite stable and perhaps one of our most robust and feature filled releases. None of this would have been possible without your help and input. This shall be the last release in this cycle and, if no show stoppers are found within the coming week, it shall become our official release. Thanks again so very much. Things to test: Not much except ensuring that your current configuration continues to perform flawlessly. For a list of changes, please take a look at this post: http://forum.universal-devices.com/view ... =6475#6475 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 Instructions: 1. Please backup your ISY (File | Backup ISY) 2. Please download the firmware for your platform - please do not unzip ISY 99i Series: http://www.universal-devices.com/update ... 2.8.16.zip ISY 992i Series: http://www.universal-devices.com/update ... 2.8.16.zip ISY 994i Series: http://www.universal-devices.com/update ... 2.8.16.zip 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 self-signed certificate before doing the upgrade: http://www.universal-devices.com/mwiki/ ... rtificates 4. Important Due to invalid Java certificate chain in releases 2.8.5 and above, 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 ( http://www.universal-devices.com/mwiki/ ... Java_Cache ) f. Go to http://www.universal-devices.com/99i/2.8.16/admin.jnlp 5. Login to the Admin Console and choose Help | Manually Upgrade [the name of your system] 6. 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) 7. After the upgrade, ISY reboots. Please do ensure to clear your Java Cache: http://www.universal-devices.com/mwiki/ ... Java_Cache 8. IMPORTANT Once upgrade is completed and ISY reboots, use any of the following methods to access your ISY's Admin Console: a. http://isy/admin - applet (Windows only) b. 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/2.8.16 - applet f. http://www.universal-devices.com/99i/2.8.16/admin.jnlp - Java application Thanks and with kind regards, Michel

Thank you. Please do the following: 1. Upgrade to 2.8.15 2. On your remote desktop, go to http://www.universal-devices.com/99i/2.8.15/admin.jnlp 3. In ISY Finder, click on the Add Button and then enter your URL (http://192.168.1.101) ... without the "admin" part 4. Let me know if ISY Finder finds your ISY. If so, double click on it and let me know if you are still getting errors With kind regards, Michel