Michel Kohanim

Hi tim2u, No problem. Unfortunately the promotion was for beta testers. We did plan to have a promotion for the holidays but had a very hard time finding enough time to do it properly. With kind regards, Michel

Hi Teken, I am so very sorry to hear. Please plug back in and observe the status of the lights on the front of the unit and report back. With kind regards, Michel

Hi nickoonce, There lies the problem. I do not think your router's new firmware has fixed the issue with reservations. You basically have two choices: 1. Use static IP address for ISY 2. Use DHCP without reservation With kind regards, Michel

matapan, 3.1.15 will not fix that issue. 3.1.16 would. With kind regards, Michel

smurt, If your ISY is setup with DHCP, then it has to renew its lease when the lease expires. If your DHCP lease in the router is 1 minute, then ISY will try to renew at 20 seconds before the lease expires. If you see a lot of those, then it means that your router is NOT responding to ISY and thus ISY keeps trying to renew the lease. It will eventually give up and then you will not have network connectivity. If you have a NetGear router and if you are using DHCP reservations, then you have to upgrade the firmware on your NetGear router as it did have major problems with DHCP reservation. Wtih kind regards, Michel

Hi nickoonce, This problem is due to the firmawre in the NetGear router if you have DHCP reservations. Can you tell me if you have DHCP reservation in your router for your ISY? Wtih kind regards, Michel

Hi matapan, You can use scenes to create groupings. In short, it means that you can have the following scenarios (on the same KPL): 1. A group of one or more buttons turn on/off as a group 2. Turning one could turn a group of one or more buttons off With kind regards, Michel

Hi everyone, With your help, Chris did figure out the problem and we are currently working on a fix. As LeeG noted (quite ingeniously I might add) the problem has to do with how we handle group cleanup messages. The problem is isolated and it only happens in cases of extreme communication problems. With kind regards, Michel

Hi Brian H, It takes a while for the changes to propagate to all other name servers (approximately 1 hour). Do you use www.universal-devices.com or just universal-devices.com? With kind regards, Michel

Hello everyone, I do apologize for all the trouble accessing our website for which I take full blame: we changed DNS servers for universal-devices to Network Solutions and they decided to include "Under Construction" in the records. This has already been rectified. Again, sincere apologies and please do let us know if you experience further problems. With kind regards, Michel

Hi Christian, The only way to disable IR is to remove the sensor. Linking issues, I think everyone else has already covered all possible cases and things to try. With kind regards, Michel

Hi tim2u, If you are trying to figure out how much water you need for irrigation, may I humbly suggest our Irrigation Module (http://www.universal-devices.com/mwiki/ ... ion_Module)? Yes, we do have plans to support variable assignments but, at the same time, we have so many other plans! I really cannot give you an ETA. With kind regards, Michel

Hi Jeff, Common areas are still under development. With kind regards, Michel

Hi Teken, It should have been fixed. With kind regards, Michel

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

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

Hello all, I am happy to announce the availability of our 3.1.15 release! For a list of changes, please take a look at this post. This is a minor release which could have major implications: the newer INSTEON devices (such as InLineLine) require the 3rd byte of responder links to be 1. The older devices didn't care about this value and thus ISY set them to 0. The theory is that the older devices do NOT care about this value and thus we are now setting the 3rd byte for all devices to 1. Although we have tested this extensively with existing/old devices, it's strongly recommended you do make sure that adding older devices and moving them into scenes, would continue to work. ELK Integration Module is no longer on sale! Thanks to everyone for helping and making this module a huge success. Important Information 1. ISY-26 is no longer included in the firmware builds 2. Due to the sensitive nature of supporting MorningLinc/ELK Security Systems, 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. 4. Please note that Network Resource modules are now running in their own task. This might have some ramifications as calling network resources from programs no longer waits for the resource to complete. As such, a) you will experience quicker handling of network resources/programs and if you are using DSCLinc and WebLinc, your programs may behave a little differently. Please do test your network resources thoroughly 5. 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. 6. 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 7. 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 8. For a discussion of variables, please look at our Program Variables forum. Things to test: - Adding devices - Moving devices to scenes - Removing devices from scenes Instructions: 1. Please backup your ISY (File | Backup ISY). If you are backing up a 3.1.6 system, please note that the backups are corrupted. If you have a backup from prior releases, you should be OK 2. Please download the firmware for your platform - please do not unzip ISY 99i Series ISY 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 3c 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.15 - applet f. http://www.universal-devices.com/99i/3.1.15/admin.jnlp - Java application Dashboard - not fully supported - http://www.universal-devices.com/99i/3. ... board.jnlp 8. Please backup your system again Thanks and with kind regards, Michel

Hi Chris, Thank you and I got your email. May I humbly suggest trying the same outlet as your previous PLC. This will rule out noise/phase issues on the current outlet. Also, if you are trying to install RF devices (especially thermostats) you have to make sure that the baby monitor does not interfere. 3.1.15 should be out shortly and you might want to give it a try as 2.8.16 does not have support for all the new devices. With kind regards, Michel

Hello oatflake, No, Admin Console does HTTP auth. The problem is when you are searching for ISY, you may NOT already know the credentials (that's how all discovery protocols are designed) and thus a few of those files in /WEB should be generic. We'll see what we can do to password protect index. With kind regards, Michel

Hello oatflake, There are very many files in /WEB that should not be password protected otherwise the Admin Console (and UPnP) will not find ISY on the network. Perhaps we can make only INDEX.HTM password protected? With kind regards, Michel

Chris, When you get a chance please send an email to support@universal-devices.com. I think you have one of those dual band PLMs that might be causing all these errors. It's very important for us to get you a new PLM. With kind regards, Michel

Hi matapan, Search! Try "keypadlinc v2d". Please note that each word should be at least 3 characters You have to be much more specific as far as the applications that prevent these errors (which are communications between devices so I am not sure what applications can do to alleviate any of this). Any links? Right mouse click on the node, choose Properties and then check the Load button

Hello everyone, Just received the API documentation ... there a configuration bits that can be set to: a) allow the timer functions to remain active to send group commands Initial testing on the beta unit was not successful. We just ordered a new unit to test these configuration bits. With kind regards, Michel

Hello everyone! As you may know, we have had couple of reported instance of programs not behaving properly. We need your help to get to the bottom of this issue since we have not been able to reproduce this problem. If you DO have a program that behaves (or at one pointed behaved) improperly, please do post to: viewtopic.php?f=25&t=7633 Thanks in advance and with kind regards, Michel

Chris, In addition to Teken's suggestions above, please note that PLC was MUCH more powerful (transmit) than the current PLM you have. On the other hand, the PLM is dual band so it would give you more flexibility as far as bridging the phases. The first question I have is whether or not your PLM is connected to the same outlet as the PLC used to be connected to? The second question is whether or not you still have your PLC online and, if so, is PowerHome still communicating with some (or all) of your devices? And, finally, if you are still having problems it's best to call our tech support team and schedule a remote session since troubleshooting via forum is perhaps not that efficient. With kind regards, Michel