Michel Kohanim

jwagner010, Please remove them and add them back in. With kind regards, Michel

Hi clark21236, What problem do you have with Google Chrome and 2.6.7? As far as the EEPROM, thanks so very much for bringing it up; there's a limit to the number of writes to an EEPROM. This was a heavily requested feature and we implemented it. We will have to educate our users about the ramifications of the usage of this feature. With kind regards, Michel

Hello sca123, Apologies for a tardy reply. If you have any firewalls installed, please do be kind enough to checkout http://forum.universal-devices.com/viewforum.php?f=3 . If it still fails, please contact us (support@universal-devices.com) and we'll figure it out. With kind regards, Michel

Hi Gary, Please accept my sincere apology. Another unit shall be on its way to you tomorrow. With kind regards, Michel

Hello Gary, Thanks so very much for giving this a try. If you don't mind, please try the following two more experiments: 1. Change the network cable 2. Reboot your router If neither of these take care of the situation, please confirm your shipping address to "sales@universal-devices.com" subject RMA. In any case, you also have a defective PLM (that's why ISY goes to SAFE MODE) and thus I strongly recommend getting a new PLM as well. Again, sincere apologies for what you've had to go through, With kind regards, Michel

Hi Gary, It should get a DHCP address from your router. Would you be kind enough to try and set a static IP address (CT) and see whether or not it shows up on your network? If this does not work, then I will immediately send you another ISY to test with. In some cases, if you have a defective PLM (the power fluctuated outside the bounds of the regulator in ISY), then you will experience network issues. Otherwise, ISY should always be able to get a DHCP address ... With kind regards, Michel

Mr. Funk, I do apologize for the inconvenience. Would you be kind enough to let me know what version/revision of PLM you have? ISY goes into SAFE MODE if and only if it cannot communicate with the PLM. Please advise. With kind regards, Michel

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

Rich, At the first glance, the logs might seem wrong but, when you get to understand our code, then everything makes sense. The priority for the updater task is much higher than the priority for the reader task. So, when you add a wait, you are just basically telling the updater to "wait". While the updater is waiting, the reader continues to read. In English: if you look at your logs, they both have the same lines but in different orders. The order MAKES sense based on what you have. What I can conclude from the logs are: 1. ISY senses the family room light has turned off (accurate) 2. ISY activates the scene (accurate) Would be kind enough to do the following experiment: 1. Use the Family Room Stairs scene with any other switch except the Family Room Light. See if it has the same problem 2. Do the reverse, use any other scene with Family Room Light and see if has the same issue Please let me know of the outcome as this will tell me where the problem is originating from. Thanks and with kind regards, Michel

Hi kclark, Apologies for a tardy reply ... yes, indeed but with a very low priority (unfortunately). With kind regards, Michel

Hi Brian, Thanks for the update and yes, please do keep us posted. I would sincerely appreciate it. With kind regards, Michel

Hi Brian, Is this only the issue of wrong time in the programs or does the Admin Console also shows the wrong sunset time? With kind regards, Michel

Hi keribi, Good to hear and my pleasure! Now, all you have to do is to create a scene and drop them both in there as controllers (they are controlling one another). With kind regards, Michel

Hello keribi, Yes, you need to link them through ISY. This way, ISY knows when you press the All On/Off and will update the statuses accordingly. With kind regards, Michel

Description Version 2.6.7 User defined SMTP settings enables one to use his/her own SMTP service for notifications. Advantages 1. more secure especially if used in conjunction with a Gmail account (using TLS) 2. is not bound by UDI hosting SLAs We certainly recommend a Gmail account mostly because it's quite secure using TLS . How to use it From the Configuration page in the SMTP Settings section: 1. Un-check Use Default 2. Enter the SMTP setting for your ISP. If your ISP does not require authentication, please do not enter anything for Userid and/or Password Example Here is an example settings for Gmail: SMTP Server: smtp.gmail.com SMTP Port: 587 Userid: isy-notifications@gmail.com Password: helloworld!2 Use TLS: checked Limitations TLS has only been tested with Gmail and may not work with other providers.

Release 2.6.7 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.7 to the same forum. 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 2. If you have used bookmarks, please update them accordingly. If you have problems finding ISY, try http://www.universal-devices.com/99i 3. If you are upgrading from 2.6.1, please make sure you export all your programs and store them in a safe place 4. As always, please take a backup of your ISY Due to massive changes in this release, please do be kind enough to thoroughly test those functions most important to you specifically schedules, triggers, , Web Services, system lockups, and SMTP defined account. INSTRUCTIONS - Userid = isy - Password = autoupdate - For ISY-26, download the update from http://www.universal-devices.com/update ... nsteon.zip do not unzip - For ISY-99i Series, 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. LIMITATIONS - None

Hello keribi, Is your RL linked to your ISY and participates in scenes? With kind regards, Michel

Hi franky, I just wanted to let you know that this indeed turned out to be a bug (thanks so very much for finding it). It's fixed and shall be included in the next drop. Please note that, for some reason, Button A (the load) may act erratically. With kind regards, Michel

ctviggen, I am so very sorry to hear this and I do apologize for the inconvenience. Are you on Vista? If so, please: 1. Go to C:\Users\Your-Account-Name\AppData\LocalLow 2. Delete all occurrences of udi_frame.state and udi_tree.state If this solves the problem, then you are on a backlevel firmware and should - at the least - upgrade to the latest official release. Please do let me know. With kind regards, Michel

Doug, thanks so very much! With kind regards, Michel

Hello dss, Unfortunately we have not heard anything back from SmartHome/Labs ... I am so terribly sorry. With kind regards, Michel Is this a bug in the Keypadlinc relay? If so I might as well return mine before I put them in. Has this problem been solved? Or is it in the firmware and cannot be solved?

Hi Walter, I do not think so but I could be wrong. The last time I read the specs, it only allowed for preset to be set (heat/cool setpoints) so that you could use your RL buttons to go to a preset. I would appreciate any feedback since this is the next area we are going to work on. With kind regards, Michel

Hello Jay M, Yes, all should be controllers (they are controlling one another). And, yes, unfortunately you will have to remove and then add them back in. With kind regards, Michel

Hello Doug, Thanks so very much for the update. This is rather odd since I use Firefox as well. Now that you have it working with IE, would you be kind enough to try it again with Firefox? With kind regards, Michel

Hello accessha, With sincere apologies. This is a known issue on 2.6.6 ... you may want to downgrade to 2.6.5 or wait for 2.6.7 which should be available shortly. With kind regards, Michel