Michel Kohanim

to_lighter, We never figured out why you cannot upgrade your ISY while I can remotely. If you don't wish to find the root cause, then please send your URL + userid/pwd to tech@universal-devices.com and I'll upgrade it for you remotely. On the other hand, if you would like to figure out the root cause, then please set up a time with our tech support. Drosen, Hi, hope all is well. Is this a 99 or 26? And, did ISY reboot after it finished the upgrade? With kind regards, Michel

Hi, this is to get this post to stay on top. With kind regards, Michel

Hello all, Release 2.6.15 (RC1) is now available at Release 2.6.14 is now available at forum.universal-devices.com/viewtopic.php?t=2251. With kind regards, Michel No, that's here. This Release 2.6.15 is there Been awake long Michel? Rand

Release 2.6.15 beta is now available and may be downloaded immediately . For fixes and enhancements, please peruse our beta forum at http://forum.universal-devices.com/viewtopic.php?t=930. You may also post your comments/questions and issues relating to 2.6.15 to this forum. This release provides the following important features: 1. 99i Series Optional Modules (Help->Purchase Modules) --> Webserver Module: allows you to use your ISY as a mini webserver to serve up your own files, applications, etc. You need this module for the REST interface (see developers forum) 2. i2 Support Please make sure you go back to automatic mode (Link Management->Advanced Options->Automatic). In this mode, all database communications are in i1 mode (except for motion sensor) and all i2 applicable commands use i2. This is the best mode to use. Bugs -none IMPORTANT 1. For those upgrading from release 2.6 --->Please note that releases 2.6.1 and above will use default HTTP/HTTPS ports of 80/443 respectively. As such, before upgrading Disable Internet Access --->You will have to upgrade to release 2.6.5 ( http://forum.universal-devices.com/viewtopic.php?t=1409 ) before upgrading to release 2.6.13 --->If you are upgrading from 2.6.1, please make sure you export all your programs and store them in a safe place 2. If you have used bookmarks, please update them accordingly. If you have problems finding ISY, try http://www.universal-devices.com/99i 3. As always, please take a backup of your ISY There are no significant changes in this release except those identified as bugs and subsequently fixed. INSTRUCTIONS for ISY-26 - Userid = isy - Password = autoupdate -- Step 1 - Download the update from http://www.universal-devices.com/update ... nsteon.zip do not unzip and DO NOT USE A PREVIOUSLY SAVED COPY! - Login to Admin Console - Choose Help->Manually Upgrade My Lighting and choose the file you downloaded in the previous step -- Step 2 - Download the update from http://www.universal-devices.com/update ... nsteon.zip do not unzip - Login to Admin Console - Choose Help->Manually Upgrade My Lighting and choose the file you downloaded in the previous step INSTRUCTIONS for ISY 99i Series - Userid = isy - Password = autoupdate - Download the update from http://www.universal-devices.com/update ... nsteon.zip do not unzip - Login to Admin Console - Choose Help->Manually Upgrade My Lighting and choose the file you downloaded in the previous step - Important: After upgrading, please close Admin Console, close all web browser processes, clear your Java cache, and reopen Admin Console. If there are any web browser processes running, the Java cache will not be cleared.

Hello Michael, Sincere apologies since we had a problem (user error) with our CRM application today and thus we did not receive your ticket. If you have Solid RX, then it means that ISY cannot communicate with your PLM. If none of the LEDs are lit, then please do be kind enough to send an email to tech@universal-devices.com and request for a replacement unit. Again, I do apologize for not getting back to you sooner. With kind regards, Michel

Hi smileyw, With the KPL timer, the only controller link you can have is with the main button. Subsequently, any other buttons you depress, are going to turn on/off all the responders for the amount of time dictated by the button you pressed. Now, you can use timer buttons as responders in scenes and that's why you have 8 of them in the tree. With kind regards, Michel

Tim, thanks so very much for the update. I do appreciate it very much. With kind regards, Michel

Hi Jim, Yes, it means that ISY could not connect to your mail server (timed out). With kind regards, Michel Yes, Michel - and thank you for taking the time to explain. The bottom line seems to be - .14 may, or may not, fix group com issues with new devices. I have a good test switch that has been a prime example of the group com problems. I'll see what happens and let you know. It will take up to a week for me to be sure - due to the intermittent nature of the problem. Jim H.

Hello gfrnd, Since you have dyndns, all you have to do is to enter your dyndns name. As far as installing certificates, please make sure you are LOCAL to your ISY otherwise the process will not work (insecure) . With kind regards, Michel

Hello IndyMike, You are right on. One comment though: Even if ISY tries to create a duplicate record, the device's firmware stops (or used to stop) it. The main problem is not writing. The main problem is reading: in order to write a record, we first have to read it, modify its contents, and write it back. In numerous occasions, some of the newer devices do NOT send the correct record (for some unknown reason) and thus the corruption. You can test this theory by doing a Device Link table on an i2 device. But, again - and as you suggested - I am not sure what the underlying cause is; I just know the symptoms. With kind regards, Michel

AD8BC, Thanks so very much for the update. With kind regards, Michel

Hi Wayne, Thanks so very much for the steps to reproduce the problems. I am going to take a look. When you remove devices from scenes, the records are deleted LOGICALLY which means that they start with 22. Otherwise, we would have to do a restore after each remove which would take hours. If this is the only issue you are noticing, then it's 100% normal and as designed. I will check into what you listed shortly. With kind regards, Michel

smanes, I do not think that the problem is privileged vs. unprivileged port; the problem is that ISY keeps a socket open (so that you get status feedback) and thus most firewall software do not like it unless you put ISY in their "white" list. Unfortunately, Kaspersky did not have the feature to exclude a device from the list. Furthermore, you can assign ANY port you'd like to ISY (through the shell/telnet) and, if you do, would you be kind enough to keep us posted with your progress? With kind regards, Michel Thanks. I read the thread and kept playing with settings in Kaspersky A/V (unsuccessfully) until I moved everything to a laptop on the network and disabled Kaspersky entirely. That didn't work either until I used Internet Explorer, then it was happy. For some reason, JRE didn't like Firefox 3. Having to disable a popular Windows virus checker in order to use the ISY99 is bad news. Can the ISY99 be set to run on an unprivileged port so virus checkers won't be interested in it, or won't this make a difference?

Hello smanes, There's surely a communication problem causing this. Is your PLM plugged into the same outlet as your HouseLinc's PLM used to be plugged into? If not, please give it a try. With kind regards, Michel

Hi Wayne, Are you saying that "without doing any type of programming" RemoteLinc has now developed its own links? If so, then this is surely a firmware bug in the RL. If not, then would you be kind enough to let me know the steps you took before this happened and the symptoms? siegeld, Did you get a chance to talk to Steve L? I think your devices are defective OR you would need AccessPoints to make sure the signals get to your switches. Please do keep me posted as it's very important for me to get to the bottom of this. With kind regards, Michel

Hello Jim, Thanks so very much and you got it right. Please do be sure to keep us posted. Mike and Jim (Mass), Thanks so very much for the confirmation. Mine also works ... I'll try to figure out what's causing reakhavoc's issues. With kind regards, Michel Yes, Michel - and thank you for taking the time to explain. The bottom line seems to be - .14 may, or may not, fix group com issues with new devices. I have a good test switch that has been a prime example of the group com problems. I'll see what happens and let you know. It will take up to a week for me to be sure - due to the intermittent nature of the problem. Jim H.

Hi reakhavok, -14 means that your login was not accepted (authentication failure). I think there might be a bug we've introduced. Would you be kind enough to contact me via email? I am going to try and have a build for you test (tech@universal-devices.com). With kind regards, Michel

Hi reakhavok, Thanks so very much for the update. We added a little more debugging information in the log. Would you be kind enough to retry a notification, check the log, and see if there are any errors? Thanks and with kind regards, Michel

Hi reakhavok, Would you be kind enough to let me know whether or not you are using gmail? Also, just to make sure it's not network related, would you be kind enough to try Synchronize with NTP button and see if it fails? With kind regards, Michel

Hello AD8BC, Yes, please do so! With kind regards, Michel

dss, I am not going to talk on the behalf of SmartHome, but from what I see, CRC and error handling IS the problem (especially in LampLincs where duplicate records are created). i.e. in light of transmission errors, what should the device do? I cannot make any other comments beyond that mostly because it will be taken out of context in other forums. Jim, I am so very sorry for not answering your question. From my perspective, there are sensitivity issues with some of the newer devices which can be solved by using Access Points. This said, however, if you've had signal issues and used 2.6.13, then on top of signal related issues, you would also experience programming and corruption issues. The core issue is signal/error handling and 2.6.13 just exacerbated it. So, now, if you have factory reset your device, restored it using 2.6.4 (in automatic mode), and still have intermittent scene activation and group commands - and if they used to work properly using older devices - then the only answer - unfortunately - is the addition of more access points. If I manufactured accesspoints, I would send all a couple for free. Does this answer your question? With kind regards,

Hi Jim, It is usually very convenient for all to declare victory and point fingers. Since 2.6.14 is EQUAL to 2.6.13 in i1 mode (only), therefore, I can only conclude the following: 1. Programming database records using extended messages does not work and it may corrupt the device ... the only solution is factory reset of the device and not to use extended messages for programming purposes (2.6.14/automatic mode, uses standard messaging for everything except motion sensors) 2. In 2.6.13, most new devices were being programmed in i2 (automatic mode), and thus the likelihood of corrupted devices 3. In our test experiments with real installations (not test lab), most (not all) of these issues were solved by adding access points As such, and at the moment, I think the problem is that extended messages are NOT being correctly repeated by i1 devices and thus sensitivity issues. I do take the blame for using extended messages for programming purposes in the first place and I attribute it to lack of clear and definitive cooperation between SH/UDI. All this said, however, missed scene commands/activations have nothing to do with i1/i2 modes. So, if factory reset and restore do not help (in case the device is corrupted), then one might need extra AccessPoints. And if that doesn't work, then it might be noise, and finally if all fails then it's a defective device. So, in short, 2.6.14 may have solved the programming issues but the signal issues are completely beyond the control of ISY and 100% in the realm of device to device communications. With kind regards, Michel

Hi Tim, I do apologize for the inconvenience. Please choose one of your problematic devices (hopefully the lamplinc), remove it from ISY, do a factory reset on it, and then add it back in ISY. If this does not solve the issue - and if possible - please move your device close to your PLM. If this solves the issue then - as much as I hate to say it - the problem is that the signals are not getting to your device (not being repeated). If not, then you have a defective device. In all likelihood, the problem is signal related and the messages are not being repeated. With kind regards, Michel

Hi Robert, Please make sure you have remote access enabled, and then send your URL/credentials/address of the KPL in question to support@universal-devices.com . We'll check it out remotely. With kind regards, Michel

Hi Robert, This is the strangest thing ever ... would you be kind enough to send me the two digit cat.subcat that you see in the top center (right below the name) of the Admin Console for this device? In the meantime, I am going to send this issue to SH to see if they know of anything that might have caused this. With kind regards, Michel