Michel Kohanim

Hello Charlie, This sounds very much like a bug. Would you be kind enough to send me your coordinates (including timezone, latitude, longitude)? Thanks and with kind regards, Michel

Hi aLf, First of all, it would be quite interesting if a device would - by itself - develop links to other devices. But, I've seen worse! Ok, factory reset: 1. Take the set button out and leave out for 10 seconds 2. Push and hold it in for 10 seconds Yes, please do restore with ISY and keep us posted. With kind regards, Michel

Hi aLf, Wow, a strange one. You mentioned that you looked at the event viewer and you could not see traffic for SW2. Did you notice any X10 messages? At the moment, I must agree with Mike: Factory reset and then restore just SW2 (the one that turns on randomly). With kind regards, Michel

Hi Rod, Please do help me understand: if ISY puts everything in a backup file, in a zip format, what difference does it make if you could edit the programs? Furthermore, if ISY is non-functioning, what value does this bring? With kind regards, Michel

Hello Rod, I have already responded to your email. Please do keep me posted. With kind regards, Michel

Hello Stowaway, Please try restoring the LampLinc. If this works, then the problem is a bug in LL where duplicate links are created. With kind regards, Michel

Hello Jim, Yes, it's quite possible especially on LLs, SWLs, and KPLs (the newer ones). Hi Erirc, the best place would be http://code.insteon.net but I think you can do a lot more valuable things with your time! With kind regards, Michel

Hello all, The bug is GUI related and has no impact on the correct functioning of your programs. With kind regards, Michel Jim, actually the day of the week is also incorrect today--it says Monday instead of Wednesday.

Hello Eric, We have to support i2 since new devices (such as Motion Sensors, Thermostats, new SWLs and KPLs) do not respond to PEEK/POKE and thus we can never write slave links in them. Therefore, ISY would not be able to program your scenes when you have a mixture of i1 and i2. The manual linking process between i1/i2 devices should continue to work since the writing of the db entries is done internally to each device and does not depend on the protocol. I am sure we'll eventually find all the issues and fix them especially now that SH is interested in the bugs we are seeing. Thanks so very much, With kind regards, Michel

Hi Michael, This has also been reported by others. If you don't mind, please do be kind enough to post your findings to: http://forum.universal-devices.com/view ... 5364#15364 With kind regards, Michel

Hello all, I am very pleased to let you know that SH is very interested in knowing about all the problems you may have with your devices. This topic is going to serve as the one place where SH can read/review problematic issues. To make this process effective, please follow these guidelines: 1. Please make sure that you do NOT post to this topic unless we are sure this is indeed an INSTEON issue 2. Please do NOT use this topic for interactions 3. Please be concise and provide the following information: --a. Description of the problem and the product type --b. Revision, Date Code, and Lot Numbers There should be 2 labels on the units that contain this information. One will have the product model number and date code, the other will have the revision and lot number. Thanks so very much, With kind regards, Michel

CJVann, If you are still having problems with creating scenes, perhaps it would be best to call our tech support and let us walk through it to pinpoint the problems. With kind regards, Michel

Hello Eric, Good question! 1. Close all your browser windows 2. Control Panel -> Java (on MAC, you might have to reboot your computer) 3. Settings->Delete Files (select all) With kind regards, Michel

Hello to_lighter, Please do not connect the PLM cable to the network and vice versa as you might damage your router. The best diagnosis tool, at the moment, is the status of your LEDs. With kind regards, Michel Thanks, Mine is a 99i Pro. There are two ethernet ports, one to the PLM and one to the network. There is no serial port. Plugging in the ethernet cable that usually leads to the PLM into my laptop did not work (the 99i does not even turn on in that case). Cheers!

Hello to_lighter, I am so very sorry to hear this. Would you be kind enough to let me know the status of the LEDs on the front? Is it possible that ISY is not on the network (bad cable)? If your programs are still running and if you have rebooted ISY, then the LEDs will provide great clues as to what could be going on. With kind regards, Michel Thanks Dave, It has a static IP on my network, and doesn't respond to telnet. Cheers!

Hello oronomus, I am so very sorry for all the troubles you are having. Before we conclude it's a bad sensor, would you be kind enough to do one last test: 1. Tools->Diagnostics->Event Viewer (Level 2) 2. Put your sensor in programming mode 3. Link Management -> New INSTEON Device 4. Choose Motion Sensor (at the bottom of the list) and hit Ok Please do send me the log (tech@universal-devices.com). Again, with sincere apologies for all the troubles you've been having. With kind regards, Michel

Hello gregoryx, The only thing you should worry about is that the RL goes out of programming mode every 4 minutes. Now, the difficult part is that with i2, the LED acts completely "irrationally" so, in some cases, you do not know if RL is out of programming mode or is it just in one of its moods. So, in short, you just have to press the Dim/Brigth button every 3.5 minutes to give yourself another 4 minutes. The other disadvantage of i2 is that it just eats up your battery during programming mode. So, I do recommend replacing your battery if communications become too intermittent. With kind regards, Michel

Hello CJVann, We'll try to get it to work by tomorrow night! Please do be kind enough to try the following: 1. On the devices that fail, please right mouse click and choose Restore Device. If this does not work, please: 2. Go to Link Management -> Advanced Options -> i1 Only If #2 works, please provide me with the: 1. Device Type 2. Device Version 3. On the back of the device (if you have access), you will see 3 labels. Please provide me with those I will provide this information to SmartHome for troubleshooting purposes. With kind regards, Michel

Redrox, Apologies ... as you can see from the amount of traffic on the forum, we're still trying to get our hands around INSTEON/i2. As such, EZxxx issues shall be addressed when we are comfortable with all i2 devices. With kind regards, Michel Hello Michel, you said there should be a solution within three weeks. This was posted 6 weeks ago. Are there any updates on this yet?

Hello Mr. Rufle, Your program seems correct. The problem might be due to some other program or controller which issues C13/Off. Do you have any other programs or controllers which might be interfering with this program? To copy and paste, right mouse click on your program and then choose Copy to Clipboard. With kind regards, Michel

Hello again! A stupid question: are you sure it has not already been added? If you don't mind, please do be kind enough to do the following: 1. Factory reset your RL 2. Turn on the Event Viewer at level 2 (Tools->Diagnostics->Event Viewer) 3. Add it to ISY ; make sure you check your RL lights for activity every 3 minutes 4. Send us the resulting log (support@universal-devices.com) Thanks so very much and with kind regards, Michel Hmmm... okay... maybe it's working, then. It only takes a minute or so for the progress bar to go away and the solid light on the RL goes back to flashing. Does that mean it's done? If so, where is the device represented in the UDI console software? How do I link it to things in the software? Correct. Not showing in the device tree at all. It is Rev 0.92 if that matters. It's pretty clear that ISY is talking to it - and appears to finish doing so... but nothing shows in the tree.

Hi Percy, thanks so very much for the vote of confidence. The short answer to your question is NO. The longer version is: it depends on SH deciding to change device categories/subcategories (has happened twice already) on their own without notifying developers. With kind regards, Michel

Michael, hello! Now, you have reached the point of no return since I have to explain to you how All On/Off works in INSTEON protocol: When receiving All On/Off, the devices turn on to the on level and at the ramp rate of the FIRST ever group they were linked to. So, what you have to do is to figure out what scene you created first for those 2 that do not come on and change the on level/ramp rate in that scene. With kind regards, Michel

Hi Rand, Already done and fixed! Thanks. Wayne, thanks for finding the bug. With kind regards, Michel

Hello RF_Burns, Thanks so very much for the update. I am very surprised that you had issues with Firefox since that's what I personally use 99% of the time. Are you sure you have the latest Java plugin for your FF? With kind regards, Michel