Michel Kohanim

Hello Mr. Zulich, What operating system are you running? If Vista, please do make sure that you have Network Discovery on. If XP, then please make sure you see "Hide UPnP ..." on your left navigation bar. If you have communications problem with your devices, then I suspect noise. Is your PLM plugged into the same outlet as your computer, router, monitor, etc.? If so, you would want to put all those other devices on a FilterLinc. With kind regards, Michel

Hi Michael, I think that's an excellent idea. Perhaps as part of your user profile ... unfortunately, that feature does not exist and we do not develop the forum software. As such, the best thing to do would be to bookmark them locally. With kind regards, Michel

Hello RF_Burns, The first thing I suggest is to do a restore device (right mouse click on the SWL and click Restore Device) on your faulty SWL. There are also newer SWLs (600W versions only) which only work with i2 commands. So, perhaps, you would want to wait for 2.6.13 beta to see if that takes care of the problem. If not, then it's surely the switch. With kind regards, Michel

Hi MV, As to_lighter suggested, you could use a program. Or, you can convert your 6 button to 8 button KPL: 1. Take the set button out 2. Press and hold the A and H buttons ( you have to have extra buttons ) 3. Press the set button in and hold it for 3 seconds When you do this, you will have to remove the KPL from ISY and re add it. With kind regards, Michel

Hello MV, Unfortunately, you will have to remove and re-add it back. With kind regards, Michel

Hello upstatemike, To get the link tables: 1. Click on Start 2. Choose the device from the list 3. Click on OK I am still very interested in the device link table and ISY link table for that device. If they are different, then ISY is not restoring it properly. If they are the same then the problem is either the PLM or the Switch. With kind regards, Michel

Hello wrj0, When you change the unit measure in the module configuration, you should see that reflected in the programs (you might have to restore your Admin Console depending on what your system caches). So, the short answer is yes. With kind regards, Michel

Hi Tim, Thanks for the feedback. As far as motion sensors being undefined, the main problem is that the same category/sub category (identifying the device) is going to be used by another device. For us to manage the dev cat/sub cat changes means that we would have to maintain a list of all the changes (we went through this with KPL 8 button) which we are NOT always privy to. In any case, I do not recommending an upgrade till a complete and fully stable release. Hi Tom, You can always go back to release 2.6.8. To be 100% sure, you can also restore the backup you took in 2.6.8 and thus you'll be guaranteed to have the same behavior as you did in 2.6.8. Now, please make sure you are not using HL2 PLM for, if you do, NOTHING will work reliably. Hi someguy, I am not sure why that would be the case. Perhaps it's reporting as i2 but does not support i2 commands? With official 2.6.13 (tomorrow), you have the option of forcing ISY to treat everything as i1. Please test it and let me know if this works. With kind regards, Michel

Hello, We have had many reports that the new HL2 PLM does not work with ISY. We do not know why this is the case but we are trying to figure it out. As such, getting a free HL2 upgrade is always a good idea but please do NOT use its PLM with ISY unless you are ready to spend hours troubleshooting communications issues. With kind regards, Michel

Hi Dodger, Please do NOT delete everything as the problem you are experiencing will not be solved by deleting. What you might want to do is: 1. Reboot ISY 2. Wait a couple of minutes 3. Click on View and Refresh on your Network Dialog I am assuming you have Windows Vista. With kind regards, Michel

Hello someguy, my apologies for not responding to you sooner. This is what we have found for both Motion Sensor as well as RemoteLinc: When you are adding them to ISY and if you choose the first option (remove existing links), ISY tries to clean out whatever records that are still in those devices. With i1, this process took much less time than 4 minutes but with i2, this process is taking much longer. As such, both MS and RL will timeout and cannot communicate any more. One way to fix this using i2, is to factory reset them. This way, ISY is presented with a blank database and thus will not try to compact/clean it. This works 100% of the time with my RL and MS. Furthermore, we have learned (through trial and error) that when the battery is FULL, i2 operations are almost as quick as i1. With lower battery levels, i2 messages seem to take increasingly longer times. And, finally, heeding the advice of MikeB and Rand, we have added an option to disable i2 (globally). This can be used for temporarily disabling i2 operations and then reinstating them. Unfortunately, for Motion Sensor, you NEED i2. 2.6.13 should be available by Sunday. With kind regards, Michel I was getting this all the time. It seem to help when the motion sensor was placed very close to one of the access points while programming. I tried this and I still get "request failed". Here is what is interesting: It seems as though the changes that I try to make that end in "request failed" take affect. When I change the off-timer to 7 minutes, it works properly and when I link the sensor to a light, it turns on that light. it seems as though the system thinks it is't getting the job done, but it is. Michel: any ideas here?

Hello ctviggen, Please do call our tech support number and we'll be delighted to help you get it to work. With kind regards, Michel

Hi to_lighter, Java 1.6. If you wish, and you don't mind, you can send me your URL and credentials and I'll try to install it for you remotely using my PPPPCCCC! With kind regards, Michel Hi Michel, Same result with Safari or Firefox on multiple computers. Which version of Java is the ISY99 optimized for? Cheers!

Hello to_lighter, Apologies! The process is rather involved and something that we tested only once since you are the ONLY person who's willing to pay $14-400 per year for a certificate. So, this will have to wait till we test it more thoroughly and provide you with a list of service providers that we have the least amount of problems with. Do you have the same problem if you use Safari on another computer? With kind regards, Michel

Hello to_lighter, Thanks so very much. It seems that, yes, I am a glutton for punishment! First of all, you should put your external IP address when asked. Of course, the problems you are having have nothing to do with this. But, if you put our local IP address, you are going to have multiple certificate errors to deal with. Now, it seems that Firefox/Java and MAC do not like our Java applet. Do you have a PC that you can try this with? I think it has to do with the Java version you have on your MAC. With kind regards, Michel Thanks Michel, I have accepted the Legions of Bouncy Castle certificate. I am on a Mac, and have tried Safari and Firefox. Both give the same result. Any ideas? Cheers! Hi Michel, Does it matter what the original address is that I access? I type in my local IP address for the ISY (i.e. 10.0.1.209). Is this the correct way to start this process? Cheers!

Hi to_lighter, I do apologize for the inconvenience. Yes, if you would be kind enough to: 1. Look at the Java Console for any exceptions 2. Turn a few scenes on/off and then send me your log (for performance reasons, we flush the log after 32 entries) My email address is support@universal-devices.com. With kind regards, Michel Thanks Michel, I have accepted the Legions of Bouncy Castle certificate. I am on a Mac, and have tried Safari and Firefox. Both give the same result. Any ideas? Cheers!

Hello someguy, For clarification, you should also know that Motion Sensor is an RF device which goes to sleep mode. The only way you can communicate with RF devices that go to sleep mode is to put them into programming mode. As such, you will have to first click the set button on the MS till the light starts blinking and then retry. With kind regards, Michel

Hello to_lighter, If you do not see a dialog box notifying you of an impending reboot, then nothing worked. The most prevalent reason for this not working is perhaps you did not accept The Legions of Bouncy Castle certificate (the code that actually generates certificates). In order to do so, please: 1. Control Panel -> Java 2. Security-> Cerificates 3. Remove All With kind regards, Michel

Hello someguy, Yes, you can do it in ISY releases 2.6.12/13: 1. Click on one of the motion sensor nodes 2. In the right pane, at the bottom, you see a button called Set Options With kind regards, Michel

Hello Frank, Are you using 2.6.12? The motion sensor is not queried in this release. With kind regards, Michel

Hello scoobydawg, I am so happy to hear that all is working fine but I still strongly recommend a new PLM. With kind regards, Michel

Hi Rob, Perhaps you are doing File->Restore Devices and thus the reason it takes couple of hours. To restore a single KPL, you have to right mouse click and choose Restore Device. As Mike said, this should not take more than a few minutes. With kind regards, Michel Thanks Darrell and MikeB. I'll give it a whirl. The significant problem I always have with doing things like RESET/RESTORE is that it takes a couple of hours to replace all the links in the customer's switch(es). I go onsite to fix something and it takes hours....due to the number of links across the 87 Insteon devices. Too often, I have to test things, onsite, start a Link Table update process, then leave the residence. Then, log in by remote to see if it is finished. And/or update things..... Thanks, - Rob

Hello scoobydawg, I am so very sorry to hear about all the problems you are having. In some cases, when the power comes back on, the spike kills the PLM. I've seen this many times before but with different symptoms. Would you be kind enough getting a replacement PLM? Also, after a power outage, some other INSTEON devices fail and thus cause a lot of noise on the network. This will be quite tricky but with the help of Event Viewer you might be able to pinpoint the faulty device. With kind regards, Michel

Hello Andrew, Sincere apologies ... this post was somehow lost! Please do be kind enough to upgrade to 2.6.8 and let me know if you run into the same issue again. With kind regards, Michel

Hello upstatemike, If this is indeed a switch problem then I am worried that we are going to see more of this. Can you do me a favor: Check the Device Link Table and ISY Link Table for this switch and, if they are different, please send me both (we did this before but not with 2.6.13). With kind regards, Michel