Michel Kohanim

Hi jsp, There's an option flag in ELK which lets it know what to do with received data (from ISY). Without the option - and in some cases, ELK simply returns it back to ISY as a command and thus you will see lights intermittently turn on/off. With kind regards, Michel

Hello RBC, You must type http://your.isy.ip.address/admin to go directly to the Admin Console. Otherwise, you will have to do double logon (one for HTML and one for the Admin Console). With kind regards, Michel

Thanks so very much IM. The i2 support for ICON was a different issue: 1. i2 as data transfer mode ... for this ISY fails since ICON returns an address which ISY does not expect 2. i2 as command mode ... we could not support this since during initialization, #1 failed So, in essence, we have now added an exception for ICON dimmers such that regardless of 1, ISY will always try i2 commands for backlight and other features. With kind regards, Michel

Hello johnnyt, Have you considered using http://www.universal-devices.com/99i/[version]/admin.jnlp instead? This will install an icon on your desktop and thus you will not need a browser. Furthermore, this link searches for ISY on the network so even if your IP changes, this will find it. With kind regards, Michel

Hello jsp, Yes, you will have to update the option field in ELK lighting configuration otherwise you will see intermittent operation of lights. With kind regards, Michel

Hi IM, Thanks so very much. I totally understand that the Admin Console must figure out the database size automatically but, if you don't mind, I would like to leave this as a very low priority since there's a workaround. Please advise. With kind regards, Michel

Hello IM, Can you do me a favor? Would you please use the Tools | Diagnostics menu item to retry and then choose your begin/end address (check the box next to the address). I tried this with one of our I2 devices and it seems to work fine. This said, unfortunately I do not have any Icons to test with. With kind regards, Michel

Hi Bruce, Thank you. Polling interval means the duration in time between requests to WB. 60 seconds is default and I do not think your ISP would mind 60 seconds. But, anything below that will have two side effects: 1. WB service might consider you a hacker and then block traffic from your ISY 2. Your ISP might consider you a hacker and then block traffic from your ISY With kind regards, Michel

Hello Illusion, Unfortunately unlike V2 thermostats, V1 thermostats do NOT report the correct status of FAN (there's no way to query them either) especially if you change them on the thermostat itself. With kind regards, Michel

Hi Illusion, As long as they are not of a different type (i.e. Dimmer vs. KPL or Dimmer vs. Relay), then the answer is yes. With kind regards, Michel

Hello johnnyt, Thanks so very much for the update. Would you please let me know the exact procedure (including URLs) you use to get to the Admin Console? With kind regards, Michel

Hello all, I have submitted a query to our tech rep at SmartHome. I shall keep you posted. With kind regards, Michel

Hello IM, Ah ... this is not good and it seems that we have to add more exceptions! What happens when you use i1 (regular PEEK/POKE)? Hello Bruce, The error is related to how long ISY waits for a response from the server. Currently, it's set to 5 seconds which is already way too high. May I ask what's your polling interval? With kind regards, Michel

Hi Greg, What is the firmware version of your thermostat? With kind regards, Michel

Hello all, Release 3.1.6 is now available. With kind regards, Michel

Hello all, Release 3.1.6 is now available. With kind regards, Michel

Hello all, I am happy to announce the availability of our 3.1.6 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 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 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: - New supported devices - Network activity - ELK causing system hang. Please DO NOT UPGRADE REMOTELY if you have this issue 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. 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/3.1.6 - applet f. http://www.universal-devices.com/99i/3.1.6/admin.jnlp - Java application Dashboard - not fully supported - http://www.universal-devices.com/99i/3. ... board.jnlp Thanks and with kind regards, Michel

Hello jsp, thanks so very much. Updated for 3.1.7. With kind regards, Michel

Hello JS, Sincere apologies. Do you have the correct Lat/Long for Montreal? If so, it'll be fixed immediately. We do have plans for adding more cities but I think it would be easier to add Custom names and then use the Locate Me button instead (ISY finds your Lat/Long based on your ISP). With kind regards, Michel

Hello egads, I am so very sorry for all the problems you've been having. First thing first: the reason you are not getting updates on the Admin Console could be related to three things: 1. When you first brought up the Admin Console, you did NOT accept the security certificate (signed by Universal Devices). This will prevent Java to communicate with the networking layer in completely random ways including not getting updates 2. You might be running an older version of Java 3. If you have a firewall software, ISY must be listed in the trusted zone What I recommend is this: 1. Spotlight | Java Preferences 2. Security tab ... click on Universal Devices Certificate (if there's one) and then remove it 3. Go to http://www.universal-devices.com/99i/admin.jnlp ... this should install an icon on your desktop. Use this icon instead Please do let me know if this fixes the issues. If not, please do be kind enough to call our tech support so that we can ensure you are up and running. With kind regards, Michel

Hello slice2020, Unfortunately we do not provide help/support in unlocking iPhones. This forum is dedicated to ISY and ISY related issues. With kind regards, Michel

Hi Paul, There are many iOS and Droid applications in our third party section which give you the same functionality + more: viewforum.php?f=73 With kind regards, Michel

Hi gadgetguru69, Are you certain you are entering the correct address? Do you see any type of communications with this device in the Event Viewer? With kind regards, Michel

Hello Mike, After a rather heated discussion with our team, I may have to retract my comments. MorningLinc status can never be queried and thus the state of the device is never known with any level of certainty. i.e. if you open/close your doors manually, the status will be out of synch with ISY. The only way ISY would know of the status is if the device was locked/unlocked from the ISY itself. For most doors, this is much more infrequent than opening and closing doors manually. So, any programs based on the status of MorningLinc might cause major security risks. With kind regards, Michel

j0dan, Apologies for the inconvenience. You can always call our tech support line and get live help (between 9 AM to 4 PM PDT). Quick questions: 1. Do you have any programs that change scene settings for these devices? 2. Do you see any file errors (.REC) in the Error Log? Breaking from the scene to me means that they no longer respond to scenes, correct? With kind regards, Michel