Michel Kohanim

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

Hello Jim, Apologies for the inconvenience. I am sure you have already done all the steps outlined here: http://www.universal-devices.com/mwiki/ ... tart_Guide And, here's the step by step instruction on adding devices: http://www.universal-devices.com/mwiki/ ... g_a_Device I do recommend the perusal of the links here as well: http://www.universal-devices.com/mwiki/ ... w-To_Guide With kind regards, Michel

Hello wrj0, Thanks so very much for the update. It seems that lately the mobile phone manufacturers are advocating "reboot". This is what I cannot understand nor do I ever consider! I got my BlackBerry Storm a month ago and have had nothing but trouble with it (very slow/sluggish). In more than one occasion they told me "this is like a computer, you have to reboot it once in a while" ... umm? Finally, last week, they said it's something you put in there and, obviously, I told them whatever I put in there is supposed to be in there. To cut the long story short, they had me uninstall the whole operating system and reinstall and restore everything. I could understand that, once in a while, desperate measures should be taken but it would not be fair to cloak "real issues" with reboot and reinstall. It still does not work properly. I am getting a replacement but I have a feeling this is all software related. With kind regards, Michel

Hello Al, Thanks so very much for the update. You can always bookmark ISY's local IP address and thus you will never have to go to our website. But, for that to work flawlessly, you need to assign ISY a static IP address: http://www.universal-devices.com/mwiki/ ... IP_Address With kind regards, Michel

Hello Bruce, Would you be kind enough to try and remove it again. This is what happens: ISY tries 3 times for each command, and, if your RL is involved in many scenes, this is going to take a long time. Alternatively, you could let us log in remotely to your system to see what's going on. With kind regards, Michel

Hello RF_Burns, I do apologize for the inconvenience. Two questions: 1. What version of ISY firmware do you have? 2. Has it actually removed your faulty device? By the way, what is 2404 as I cannot find any reference to it in SmartHome. With kind regards, Michel

Hi someguy, The problem is communications between ISY and your motion sensor. Two questions: 1. How close/far is your PLM from your Access Point and your Access Point from your Motion Sensor? 2. How good is your battery? With kind regards, Michel Michel: when I "restore device" it gives me the frustrating "request failed". When I press the set button on the motion sensor, it toggles the lights, but it does NOT change the status readout in the ISY admin console.

Hi Mike, Yes, please do narrow it down! AD8BC, Thanks! I think Mike is going to troubleshoot for us and then I can be more certain. With kind regards, Michel

Hello Eric, My recommendation is to use the new ones on switch at a time. I am not yet convinced that the new SWLs are going to be trouble free. With kind regards, Michel

Hi Wayne, Thanks so very much ... as usual and customary with software, I cannot reproduce it here but I shall consider it a bug and will try to figure out what's causing this behavior. With kind regards, Michel Hi Michel, See the five steps I wrote in previous msg for the exact sequence. Yes as soon as I log into ISY (enter user name and password then press OK) I get the 'Request failed' error and another blank log in screen. So I have to log in twice, the second time there is no 'Request failed' error. Thanks, Wayne ps. No network magic software installed.

wrj0, Thanks so very much for the update! This is indeed quite interesting; perhaps the treo had the wrong useid/pwd in it? Would you be kind enough to keep and eye on it and let us know if you find any more anomalies? With kind regards, Michel

AD8BC and MikeB, Lately we have been receiving increasing amount of trouble tickets relating to SWL communications issues. These are related to V35 and V40 specifically whereby either you cannot communicate with them OR you do not get status responses from them. What version SWLs do you have? With kind regards, Michel

Hi Burak, I have not yet seen WB messages with missing information in them. If you are referring to what you see in the event viewer, that's because ISY does not send events if the value has NOT changed. Again, WB sends all the information ALL the time. With kind regards, Michel

Hi Wayne, are you saying that you get a Request Failed as soon as you get the Admin Console? Do you have Network Magic software installed on any computer on your network? With kind regards, Michel

Hello Walter, No because we realized it was not a bug. This is what happens: With i2, RL takes a little longer to program (sometimes more than 4 minutes) and thus your RL goes out of programming mode. What you need to do is either use i1 Only mode OR: sit next to your RL and after about 4 minutes, put your RL back into programming mode (the LED will stop blinking and you will not see any traffic). We have also noticed that with battery operated devices, battery charge level has a TREMENDOUS impact on how quickly i2 messages are processed. So, you might want to make sure you have a good battery. With kind regards, Michel

It should be couple of months because we need it for our own configurable web modules (you can reconfigure ISY's GUI). With kind regards, Michel