Michel Kohanim

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

Hello oronomus, What option are you using (Link Management->Advanced Options)? Please do be kind enough to do a Restore Device on the OutletLinc first and then on your Motion Sensor. You should not have to link them manually. With kind regards, Michel

Hello dougos2, Eric is 100% correct: I was referring to an ISY firmware to be available shortly. With kind regards, Michel

Hello upstatemike, Please do revert back to automatic, try and get two/three replacement units, and let me know. If you run into any problems with SH, please have them contact me. They have been extremely helpful in resolving our issues. With kind regards, Michel

Hi frustratednon-geek, Eric is 100% correct: Mutual Exclusivity is only applicable to local control (and not remote through commands). What you want to do is, assuming A and B are mutually exclusive 1. Create a scene for button A (responder) 2. Create a scene for button B (responder) 3. In your program, when you turn Scene 1 on, turn scene 2 off and vice versa With kind regards, Michel

Hello upstatemike, You could go to i1 mode only, do a restore on those devices that have comm problems, and then do your test. Although I agree with you that not all switches could be defective, but going to our service calls, forums, and what I hear I do think that you will experience the same exact issues as you are experiencing now (perhaps not now but in a few days). Please do keep me posted. With kind regards, Michel

RF_Burns, I do apologize for the inconvenience. I suppose you have ISY-26. 1. Step 1 is to install a reduced function code (thus no devices) so that you can install 2.6.13 2. The reason for invalid length issues is usually the firewall If you don't mind, please do the following: 1. Checkout our firewall section for solutions to most firewall issues http://forum.universal-devices.com/viewforum.php?f=3 2. Reboot your ISY and then Reinstall 2.6.0 3. Install 2.6.13 Please do keep me posted. With kind regards, Michel

Hello all: percy: Please do be kind enough to factory reset them (otherwise it's going to take a very long time) and then add them using Link Management->New INSETON Device, and then choose the Motion Sensor from the drop down list. gregoryx All you have to do is to make sure your RL is in programming mode continuously and while ISY is trying to program it. So, make sure you check your RL every 4 minutes or so to make sure it's still in programming mode IF and ONLY IF ISY is still programming it. dougos2 and Mike Verified bugs and already fixed for the next version. The problem ONLY happens if your mode is Auto and if you use Increment and Decrement. The problem is in the in thermostat firmware: In previous code base, there was a delay between the increment/decrement and subsequent queries. In this release, we have removed the delay and the thermostat GETS CONFUSED for some reason. Anyway, the fix also includes major performance enhancements which I am sure you'll find pleasing! With kind regards, Michel

Hello again, I suspect you are using the brand new KPLs and an older ISY firmware. Please upgrade to 2.6.13 if you have not done so. With kind regards, Michel

Hello JasonWPB, I am not sure why you would lose your manual links unless you try to do a restore on any one of those devices. We are going to restart the EZxxx devices as soon as we are sure our i2 is working properly. It's really a shame how these things tend to happen more often especially to those who are supporting SmartHome. With kind regards, Michel

Hello George, I am so very sorry for the problems you are experiencing. Please do send an email to support@universal-devices.com and we'll send you the instructions to get it up and running again. With kind regards, Michel

Hi someguy, You could use any input/output controllers with the dry contacts on any alarm system. What ELK provides is additional functionality such as being able to turn on/off your lights from the security keypad. EZIO2x4 - depending on the model (the older ones) - may also work fine. With kind regards, Michel

Hi Eric, Yes, I have upgraded to 4.7.0.75. They even had me reinstall the WHOLE operating system. Right now, it's even worse: 1. I can never manage to hold it at the right angle to have the keyboard show up correctly. In most cases, I get two keyboards 2. The back light starts flickering in the dark 3. On receiving calls, it goes to speaker phone by itself and then it reverts to handset by itself 4. And - I MUST TOTALLY AGREE WITH MIKE - making a phone call is the SLOWEST: the time it takes to load the keyboard is almost 3-5 seconds every time. A phone should be a phone! I will let you know if the replacement is any better. With kind regards, I got my new Blackberry Storm the first day it was released and it was terrible slow...etc. etc. However, I upgraded to the new revision when it came out a couple weeks ago and it has made a HUGE improvement. I have not had to reboot once since doing this. Did you update to 4.7.0.75 yet?

Hello someguy, I do very much apologize for the inconvenience. I know how frustrating it is to have to go through all these steps. As far as socket errors, that usually happens when your computer goes to standby or wireless connection is severed. "host", in this case, is your computer. Now, as far as the motion sensor: The reason it gets to 99% is because it's trying to wipe out all the records from the previous linking endeavor As this is the second case involving the same symptoms - and even though I cannot reproduce it with the three motion sensors I have here - with your permission, I would like to call you tomorrow (Friday) and go through this with you remotely ( I'd like to see the output of the event viewer). In my opinion, if you get status updates from all other devices, I don't think it can be anything but the motion sensor itself. Are these new sensors or the Beta sensors from SH? With kind regards, Michel