Michel Kohanim

Hi someguy, SWL versions 40 and above (those with the beep feature) and dual band LampLincs and some newer version of KPLs are currently the only devices that support the beep command. All it does is a beep the duration for which is adjustable. Some may not honor the duration though and we have yet to figure out the exact values for those. So, in short, it will be a trial and error routine to figure out the beep duration. With kind regards, Michel

Hi Eric, The second message is OK; it simply means that ISY got duplicate messages from the motion sensor and ignored one of them. On the ones that you cannot link, may I humbly recommend doing a factory reset on it and retry. If it fails again, I must assume a defective (or low battery) motion sensor. With kind regards, Michel

Hi Eric, That's correct. Is it possible that your Motion Sensor is not near an Access Point? Also, please do ensure that Link Management | Advanced Options is set to Automatic. You may want to try the Event Viewer on Level 3 to make sure that you get a response back from your MS (i.e INST-SRX for each INST-ACK). If not, then surely your Motion Sensor is either not near an Access Point or the battery is low. With kind regards, Michel

Hi Eric, No ... you cannot link them as you would other INSTEON devices. What you need to do is to use Add New INSTEON Device and then choose the Motion Sensor from the list. With kind regards, Michel

Hi Jeff, Thank you. Would it be possible to connect your ISY directly to your router and let me know if that helps the issue. If it does (i.e. if everything works for a week or two without a problem), then I would like to send you a replacement unit to try. In the meantime, we would try everything we can to reproduce this issue (alas, not successful thus far) so that we ascertain where the problem comes from. With kind regards, Michel

Hello Jeff, Apologies for the inconvenience. 60001 means that ISY couldn't resolve the DNS entry for the NTP time server. Although I think these are related but I think the 60001 is the symptom of ISY not being able to get to the Internet. Looking at the code, the only reasons setting NTP time would happens so often are limited to: 1. NTP synch interval is set to a low interval (9 seconds in your case) 2. The IP address for your ISY changes every so often OR ISY is not able to renew its DHCP address So, I have the following questions: 1. What's the NTP synch interval in your system? 2. Do you use DHCP for your ISY, and if so, what is the lease time? 3. Is your ISY connected to a switch (is it a GigaBit switch) or directly to the router? When you have this error, do other programs work (those that are not network related)? With kind regards, Michel

Hello sfhutchi, Unfortunately INSTEON spec does not allow you to use the local ramp rate for the scene ramp rate. i.e. devices participating in a scene respond with the scene ram rate. If you want to use the local ramp rate, you must address the device specifically and not within a scene. With kind regards, Michel

Hi gadgetfreak, If noise, then the process is a little arduous. Basically, you must turn off suspicious devices (plasma tvs, battery chargers, CFLs, etc.) one at a time to see which one is causing the noise. And, once found, you will have to put that device on a FilterLinc. With kind regards, Michel

Hi Bernhard, Long time no see!!! Ok, the first thing I recommend is to checkout either of: TouchSwitch: http://forum.universal-devices.com/viewforum.php?f=49 ISY AJAX: http://forum.universal-devices.com/viewforum.php?f=55 In short, what you need to do is to use Javascript, retrieve all the nodes (by going through /rest/nodes), and then let the Javascript interact with ISY and the user with Javascript. With kind regards, Michel

Hi jwagner010, that's quite strange and thanks for reporting it. Would you please keep an eye on it and let me know if it happens again? gkouri, please try https://your.isy.ip.address as the URL and retry. justin.cool, yes, you do have the correct thermostats (firmware version>=91 is V2). With kind regards, Michel

Hi gadgetfreak, Thanks for the answers ... they will make the troubleshooting much easier. First of all, 11 seems way too low of a record count for the number of devices/scenes you have. So, the first thing I suggest is to do a File | Restore Modem (PLM). After you are done with this, check the record count again and make sure it's more than 11. For your installation, assuming 6 button KPLs, and 9 other devices, you should have at least 25 records in your PLM. Now, based on the scene test results, I do think that you have some signal issues as well. The first thing I recommend is to plug in one of the ApplianceLincs which fails right into the same strip as the PLM. If this solves the problem, then we would have to figure out if the problem is signal strength or noise. To test signal strength, if you have any Access Points, plug it right on top of the PLM and retest. If that does not help, then the issue is noise. With kind regards, Michel

Hello richardl007, I assume you are referring to a Switch/ToggleLinc, correct? The number represents the brightness of the backlight LED from off (0) to 255 brightest. With kind regards, Michel

Hello gadgetfreak! 1. I am a little unclear: do you also have the same problem if you use the KPL buttons to activate those scenes? 2. Please try Tools | Diagnosis | Scene Test ... this should give an indication of reliability between the PLM and ISY 3. Please use Tools | Diagnosis | Show PLM Links Table to get a list of records in your PLM. Once done, click on the Count button and let me know how many records you have in your PLM 4. Do you have any nodes with green 0101 icons? With kind regards, Michel

Hi guys, This was an issue with the ActionTec routers not accepting varying TCP window sizes. We put a workaround in firmware 2.7.12 to address this deficiency in ActionTec routers. If you do not have 2.7.15 installed, please do install it. With kind regards, Michel

Hello elite-rob, Unfortunately this feature is only available IF AND ONLY IF: 1. You have a V2 thermostat dongle (firmware version should be >91 or above) 2. You have 99i series I suspect you do not have a V2 thermostat dongle. With kind regards, Michel

sfhutchi, Our next milestone is ELK integration and some more minor bug fixes. Variables is on our list but I really cannot give a firm date. With kind regards, Michel

Hello mrohde, Please try https://your.isy.ip.address. If that also fails, you might want to ensure that ISY is in not in the blacklist in your firewall software. With kind regards, Michel

Hi justin.cool, Please checkout this post: http://forum.universal-devices.com/viewtopic.php?t=4556 We basically had to recompile the Admin Console and remove all Java 6 specific features. I am quite disappointed that one has to upgrade to Snow Leopard just to get a Java update ... With kind regards, Michel

Hi justin.cool, We are working on it right now. There are a few features that require 1.6 including network optimization, icon image for dialogs, table sorter, chart utilities, and many more. In the meantime, you can always try the older UIs, for instance 2.7.14 or 2.7.12 by going to: http://www.universal-devices.com/99i/2.7.12/admin.jnlp or http://www.universal-devices.com/99i/2.7.14/admin.jnlp and so on and so forth. With kind regards, Michel

Hello justin.cool, I do apologize for the inconvenience. The issue is that we need Java 6 functionality for the Admin Console and thanks to Apple, Java 6 32 bit support is only available on Snow Leopard (quite disappointing and frustrating). We will try to see if we can bypass (or even write our own code) for those functions that require Java 6 on MAC. With kind regards, Michel

I just wanted to THANK YOU ALL for help us with our alpha/beta releases. 2.7.15 would not have been possible without your help. With kind regards, Michel

Hi Illusion, If you have 2.7.15 already installed, then you do not have to do anything. Otherwise, it's totally up to you the method you choose. With kind regards, Michel

Hello all, Thanks to a lot of help and feedback from our user community, release 2.7.15 is now our official release. If you have 2.7.15 installed, you do not have to reinstall it again. Release notes may be found here: http://www.universal-devices.com/mwiki/ ... tes_2.7.15 Instructions 1. Please backup your ISY (File | Backup ISY) 2. Please download the firmware for your platform - please do not unzip a. ISY 26 - http://www.universal-devices.com/update ... nsteon.zip b. ISY 99 - http://www.universal-devices.com/update ... nsteon.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 - applet f. http://www.universal-devices.com/99i/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 9. General instructions (especially for adding V2 thermostats) for the new features in 2.7.7+ can be found here: http://forum.universal-devices.com/view ... hp?p=27368 Upgrading from 2.7.8 through 2.7.10 Upon reboot, ISY tries to migrate all configuration files to release 2.7.15 levels. This said, however, in the case of KeypadLincs, the following settings shall be lost (ISY will be out of synch with your devices) for those KPLs that were setup/configured in 2.7.8 or 2.7.9: a. Button toggle mode b. Button backlight c. Button groupings (in scenes or otherwise) d. Button mutual exclusivity As such, if you have setup any KPLs in 2.7.8 or 2.7.9, it's best to remove them from ISY, do a factory reset on them, add them back and reconfigure them. Alternatively - and you have not made massive changes using 2.7.8/9, you can restore your 2.7.7 backup (File | Restore ISY) and let ISY migrate everything. Thanks so very much for your help and support. With kind regards, Michel

Hello zachgoldberg, Long time ago we started with UPnP but due to a variety of issues (including security), we have moved away from UPnP and have instead concentrated on web services and REST. In short, you can find ISY using UPnP Discovery and you can Subscribe to it using UPnP subscription but the rest are all web services. With kind regards, Michel

Hi aLf, It does save all Network resources configuration files with the exception of web pages in the Web Server tab. Those have to be backed up separately. With kind regards, Michel