Michel Kohanim

Hello Steve, I just tested this and you are 100% correct: 1. The controller flashes 2 times before actually sending the off group command. this is 100% normal for any non-toggle button (for toggle buttons, everything is instantaneous) 2. The responders turn off with a delay the duration of which is equal to the length of time it takes for the button to blink twice 3. Functionally, everything works as programmed Now, what worries me the most is that the blinking non-toggle button is THE NORMAL behavior where as what HouseLinc does, to me, is not normal. So, perhaps they possess some secret ingredient that we have not been privy to but I seriously doubt it since memory locations and semantics for KPLs are pretty well established. In summary, I am so very sorry that I cannot be of further assistance since the devices are behaving in a manner in which I deem normal ... I really wished I could have a better answer for you. With kind regards, Michel

Hi dss, Would you be kind enough to click on Set Options (in the IOLinc view) and let me know if you have Relay Follows Input checked? Thanks and with kind regards, Michel

dss, got it, thanks. I am going to start troubleshooting immediately. With kind regards, Michel

Hi dss, Thanks so very much for the details. One last question: Did you not expect to see that status when you first started the Admin Console and that's why you queried it to make sure? In essence, I am trying to figure out if the IOLinc sent a group command that ISY mistook for the output (instead of input). With kind regards, Michel It is the output. The input isn't connected to anything. The output connects to the fireplace dry contact control (normally closed). I have it included in one scene that includes two Controlincs (button #4) that turn it on/off. I also have a program that turns it off at 1:30am.

Hello dss, Thanks so very much for the feedback. We will get right on it. Is it the output or the input that has the wrong state? If the output, is it in any other scenes? If the input, is it controlling a scene? With kind regards, Michel

sorka, would you be kind enough to use the account settings in the previous post and let me know? You can also look in your logs for errors starting with -5000x. They will give me clues as to what's causing the problems you are experiencing. With kind regards, Michel

Hello sorka, Here are the answers to your questions: 1. Yes, during full restore, the battery operated devices (RL and Sensor) are restored first 2. Auto discover does not work since the motion sensor does not respond to ID Req (for some reason) 3. You can remove a device regardless of its state. ISY will try 3 times to communicate and then it will remove it from ISY With kind regards, Michel

Hi sorka, Why is it smtp.aol.com if you are trying gmail? The first thing you have to do is to ENABLE POP in your gmail account without which nothing will work. If you wish, you can test using the following account: server: smtp.gmail.com port: 587 user id: isyalerts@gmail.com password: holamola from: anything TLS: checked I am not sure why ISY does not work with AOL especially if it uses regular auth login. With kind regards, Michel

Hi Dave, It seems that the upgrade is failing. We have been able to reproduce this problem and are working on a fix now. With kind regards, Michel

Hello Dave, This is indeed odd since, just to make sure, I reinstalled 2.6.15 on my ISY26 and it shows the correct version. Would you be kind enough to telnet to ISY, issue VE and let me know the results? If it shows 2.6.14 then it was not upgraded correctly. With kind regards, Michel

Hi steve_p, Within the scene, click on button D. To your right, change the onlevel for the load of the same KPL to 2% and NOT 0. This is a firmware issue and 2% is the workaround. With kind regards, Michel

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