Michel Kohanim

Hello silverton38, Thanks so very much for your assistance. It's indeed appreciated. Would you be kind enough to go to Program Summary tab and check for any programs that are currenlty Running? If there are any, plase try and stop them and let me know if that helps the issue. Furthermore, please go to Tools | Diagnostics | Event Viewer on Level 3 and let me know if you see anything. Thanks again and with kind regards, Michel

Hello Robin, Are you still on 2.8.3 or back to 2.8.2? Would you be kind enough to try: http://www.universal-devices.com/99i/2.8.3/admin.jnlp If it lets you login, then would you please try turning something on/off and let me know if it works? With kind regards, Michel

Hello silverton38, Apologies for the inconvenience. Can you try and turn something on and off and let me know whether or not it works? Please note that we had to renew our Java certificate and it might have something to do with that. It would be great if you could try http://www.universal-devices.com/99i/2.8.3 ... this will put a Java icon in your system tray which will enable you to double click on it to see whether or not there are any errors. With kind regards, Michel

Hello all with 2.8.3 issues. I do apologize for the inconvenience. Would you be kind enough to let me know whether or not you are using static IP address for your ISY? With kind regards, Michel

Hi Illusion, Thanks so very much for the update. Please note that there are two distinct scenarios: 1. Using i2 for database manipulation 2. Using i2 for Get/Set attribute methods Just because ISY is using i1 for database manipulation does not mean that it does not use i2 for Get/Set methods. As a matter of fact, that's what the calibration does: it tries to figure out whether or not the device supports Get/Set methods using i2. With kind regards, Michel

Hello rLav, Thanks so very much for the update. Did you clear you Java cache? With kind regards, Michel

Hi LeeG, Thanks so very much for the explanation. I did try it here and indeed ISY is using i2 (in Automatic mode). Perhaps the device was added using the third method OR once added, ISY could not ensure that i2 commands were supported. Wtih kind regards, Michel

Hello all, Release 2.8.3 Beta is now available. Although this firmware has been tested thoroughly, please note that this is still a beta firmware. Please do be kind enough to : 1. Test Linking/Adding Devices/Creating and/or Modifying Scenes and Adjusting Scenes within programs 2. Observe any type of network anomaly For a list of changes, please take a look at this post: http://forum.universal-devices.com/view ... =6475#6475 Please note that ISY-26 is no longer included in the firmware builds. Instructions 1. Please backup your ISY (File | Backup ISY) 2. Please download the firmware for your platform - please do not unzip ISY 99 Only - http://www.universal-devices.com/update ... _2.8.3.zip 3. It is very important that you use your current ISY's Admin Console to perform the upgrade by going to your http://your.isy.ip.address/admin. For MAC users, if upgrade fails, please try https://your.isy.ip.address/admin 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: http://www.universal-devices.com/mwiki/ ... 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. 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.3 - applet f. http://www.universal-devices.com/99i/2.8.3/admin.jnlp - Java application 8. 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: http://www.universal-devices.com/mwiki/ ... rtificates IMPORTANT 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. Thanks and with kind regards, Michel

Hi Illusion, I contacted SH today with respect to this specific issue and they said that the firmware has not changed in any of the V36s. So, my v36 should be equal to your v36. I just cannot understand why mine works and yours does not. I think the best thing to do for me would be to order one of these new KPLs and see how they behave. My only explanation is that the newer v36s changed something. With kind regards, Michel

Hi Andrew, I do apologize. "I" was using the wrong URL to test. This is indeed broken in 2.8.2 and above because we tried to fix the issue with null names. We'll fix it in the next release. With kind regards, Michel

Hi gfridland, Just so that I understand: 1. You have a KPL based on the status of which a scene is turned on/off 2. The same scene includes one of the buttons in the KPL Correct? With kind regards, Michel

Hi Andrew, What URL are you using? I tested this and it works fine (just providing the address). With kind regards, Michel

Hello silverton38, Apologies for the inconvenience. V2.7.15 had an issue where you could enter a null for the name of nodes and this caused the Admin Console to throw and exception. Please try the following URL instead: http://www.universal-devices.com/99i/2.8.2/admin.jnlp Once you have the node renamed properly, you can go back to the original URL. With kind regards, Michel

Hi gfridland, Would you please go to Tools | Diagnostics | Scene Test and choose the scene to which the problematic KPL belongs. Does this fail or succeed? With kind regards, Michel

Hello Illusion, We will have to contact SmartHome. Perhaps the newer switches have changed the firmware/behavior without our knowledge. Just to be clear, all these switches show v36, correct? With kind regards, Michel

Illusion, What you are experiencing is NOT right. Automatic mode should work for your KPL (I explicitly tested V36). It's odd that factory reset didn't fix the issue ... I am at a loss. How old is your KPL V36? With kind regards, Michel

Hello gfridland, It's possible but before going any further, please go to Configuration | System and make sure Wait while busy reading is checked (lower left box). With kind regards, Michel

Hi Tom, Apologies for the inconvenience. There used to be a bug with null names which caused the symptoms you are experiencing. Please try: http://www.universal-devices.com/99i/2.8.2/admin.jnlp If that does not work, please send your backup to Rand (support@universal-devices.com) ... he's a master of fixing it! With kind regards, Michel

Hello osullys, Are you trying to send RS232 commands to ISY? Unfortunately that would not work. On the other hand, you can send REST (network requests) to ISY and you will find many examples here: http://forum.universal-devices.com/viewtopic.php?t=2252 With kind regards, Michel

Hi Brian, DHCP Offer-name is only sent in the following conditions: 1. ISY is rebooted and it's trying to get a new lease 2. ISY is trying to renew the lease In the case where ISY has a lease and the router is rebooted, and if ISY does not know that the router has been rebooted, then it will not try to renew/rebind and thus the unknown. With kind regards, Michel

Hello Illusion, I think the major problem is that the event viewer is giving out too much information. i1 and i2 are two methods of communicating with devices. This said, however, i2 has different flavors: 1. using i2 to configure the database 2. using i2 to set/get operational parameters In Automatic mode, ISY gets the engine version and if indeed the version is i2, then it will use i2 get/set methods as long as they are supported. If not, then it reverts to using PEEK/POKE. As far as database management, ISY never uses i2 for anything else except: 1. Motion Sensors 2. TriggerLincs 3. Some EZxxx devices Do you have anything else in that scene or is it just a scene for the buttons on that KPL? With kind regards, Michel

Hi Illusion, Thanks. I did check the code and we have not truncated the subject line at all. The only change has been the addition of Sent timestamp (the actual time the email was sent from ISY) and I do not think that would impact the subject line truncation. We'll check into the terms and conditions issue. With kind regards, Michel

Hi Billy, I do apologize for the inconvenience. I know exactly how it feels to have to deal with erratic behavior (in the past 2 weeks, I've replaced my Sony laptop 6 times and perhaps have broken the world record). Although it might be ISY but it's going to be quite difficult fixing it if we cannot reproduce it. I sure hope that the sensor is the issue. With kind regards, Michel

Hello johnmsch, That's quite odd. You should see: ISY99-HOME-AUTO Can you tell me what's your ISY's firmware version? With kind regards, Michel

Hello Illusion, Thanks so very much for the suggestion. Are you saying that the title of notifications used to be longer and now they are truncated? As far as terms and conditions, we will look into it ... I do have Snow Leopard myself and I have not been able to reproduce it but we'll continue digging in. With kind regards, Michel