Michel Kohanim

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

Hello Vortec4800, Yes, REST would be much easier to handle and it's something we are actively working on. It's surely much simpler than doing heavy web services calls. With kind regards, Michel

Hello Vortec4800, We do have a free Web Services library which you are welcome to use (simply send an email to support@universal-devices.com with your request). But, I think you are talking about a REST approach where everything is URL based. If so, we are working on it as it would make things much easier for smaller projects. With kind regards, Michel

Hi Bob, Please do be kind enough to check the On Level for this switch. Please make sure to airgap the switch if you make any changes. As far as NTP not working, please check the logs and look for -6000x error. If you find one, then ISY is having a hard time resolving pool.ntp.org to an IP address. With kind regards, Michel

Hello someguy, I cannot reproduce this issue here and I have 3 Motion Sensors. Would you be kind enough doing a Restore Device on your motion sensor? Also, when you click the set button manually, does the status change? With kind regards, Michel

Hello okane, Two possibilities: 1. You chose the 3rd option which brought along existing links 2. Some of your devices are i2 which previous versions did not support In both cases, please download the latest (2.6.13) and then do File->Restore Devices which, in effect, will remove all your links that are not recognized by ISY. With kind regards, Michel

Hi Bob, Motion sensors are NOT queryable because you will have to put them in Programming mode before you can communicate with them. This is actually a bug that we fixed! With kind regards, Michel I'm seeing the same thing. ISY-26, PLM v52. I upgraded from 2.6.12 directly. All three of the motion sensor devices show up with blank status and if I try to query any one of them, I get nothing. No messages in the log (set at level 2). I tried changing the advanced options to "Device Reported" and did a query of My Lighting and again, no entries in the log for the motion sensor. I'm also seeing the same behavior for the EZRain zones. All my other devices are queried just fine.

Hello Gary, Would you be kind enough to try http://www.universal-devices.com/99i . If this works, then please download again and reinstall. Hi Burak, I tested the motion sensor again and it works fine. Perhaps there's no motion??? Thanks so very much, With kind regards, Michel

Hi Burakk, Apologies for a VERY tardy reply; I must have missed your post. Your assumption is correct but that's not our experience. The values should not be sporadic: ISY works based on change only. So, by the virtue of having the program check the status of last run time of another program, you are effectively saying that you don't care about what happens within an hour. May I humbly suggest the following: 1. Remove the time constraint (since last time) 2. Change the condition to include a range (for instance, due point between 82 and 87) Please let me know. With kind regards, Michel

Hello wrj0, It might be something that treo itself is blocking. Perhaps it's using it for SNPP (default port is 444). Would you mind trying a different port such as 8443 or 40443? With kind regards, Michel

Hello wrj0, Apologies for a tardy reply. Yes, indeed a bug the root cause of which is that we did not create a one to one mapping between the unit type entries. This shall be fixed. Thanks so very much, With kind regards, Michel