Michel Kohanim

Hello lpollis, My pleasure. Please do make sure to follow these instructions: 1. For best performance, please try factory resetting your ISY (removes everything you've already added) 2. Please add your devices using the first option (remove existing links). This will remove all existing links to other devices as well as to HouseLinc. So, please do this one section at a time to make sure everything works Please do not hesitate to contact us in case you run into any problems whatsoever. With kind regards, Michel

Hi elite-rob, This sounds a lot like a defective switch. With kind regards, Michel

Hi lpollis, I really think you should contact our tech support just to make sure your PLM is not the culprit here. From all your posts, all indications point to the known old-PLM issues (the PLM gets tired and does not respond). With kind regards, Michel

Hello lpollis, Long time no see! v4A is a PLM from more than 2 years ago and one which had major communications problems. The newest PLM version is 85 and much more stable and reliable. So, from the surface, I would assume the problem is your PLM. This said, however - and just to make sure you are going to have a good experience this time - may I humbly ask you to call our tech support M-F 9-5 and we'll diagnose the issues remotely for you. With kind regards, Michel

Hi Moshe, Yes: 1. Add your new device 2. Right mouse click on the defective device and then from the menu choose Replace with ... and then choose the device you added in step 1. With kind regards, Michel

Hi strahan001, If you are familiar with Web Services you can always use our WSDK (http://forum.universal-devices.com/viewtopic.php?t=2321) which is supported by ISY26. Perhaps you can test this out before upgrading to 99i especially if you do not need other module such as WeatherBug and Networking module. The migration is very simple: backup your ISY26 and restore it on your new units if you so choose to go this route. With kind regards,

Hi, I am so very sorry for we must have missed this one. I did reproduce the problem and I will have it added to our list. With kind regards, Michel

Hi strahan001, Unfortunately, the REST interface is only supported on 99i Series ... we do have an upgrade program at our store which you might want to checkout. With kind regards, Michel

Hello elite-rob, It's certainly possible that the switch is defective and you can surely RMA it. This said, however, please try one more test: Right mouse click on the device and then choose Restore Device. With kind regards, Michel

strahan001, I am so very sorry for the confusion. Unfortunately I do not know of any such solution. This said, however, if you have a little Javascript/HTML background, you can create your own by simply retrieving and formatting http://your.isy.ip.address/rest/nodes . With kind regards, Michel

Hello elite-rob, My pleasure. Now that you mention, do you have any FilterLincs? If this switch is in the vicinity of your home theater, I strongly recommend putting all your entertainment equipment on a FilterLinc. To test if this scenario works, unplug all your entertainment equipment. If no longer do you have the comm errors, then a Filter would fix the issue. If you still have the issue, then you might want to make sure that the neutral wire is not loose on the switch itself. With kind regards, Michel

Hello elite-rob, The first thing I would do is to check the log file, filter based on your Den Switch, and then furthermore filter based on the Type = -2. This will give you the times when ISY could NOT communicate with your Den switch. Please check and see if there are any patterns in the time when this happens. If there are no patterns, then it all likelihood you have a signal/noise issue. If there are any patterns, then we have to figure out what other device may be causing the noise. With kind regards, Michel

Hi Sean, Have you tried Touch Switch: http://forum.universal-devices.com/viewforum.php?f=49 With kind regards, Michel

Hi zoli, Please send an email to tech@universal-devices.com. We do have most of the Jewish holidays as ISY programs for the next 4 years. Happy New Year! With kind regards, Michel

Hi Jeff, Yes! In the Program Details Tab 1. Create a new Program 2. Click on the If 3. Click on the Schedule button in the middle of the screen 4. Uncheck the Daily checkbox. This gives you specific dates You can refine specific dates with days of the week by clicking on each desired day. Now, you can either use this program as a variable in other programs. OR, you could incorporate your logic at a Folder level in which case all the programs therein run IF and ONLY IF the condition of the folder is true. With kind regards, Michel

Hi bbb2008, There is an issue with the IOLinc's Relay where the status is not updated and which needs to be queried. But, for the sensor, this should work. Please do be kind enough to: 1. Ensure that you have our latest firmware (2.7.6) 2. Click on the Sensor node, at the bottom right, click on Set Options and ensure that you are not using momentary modes With kind regards, Michel

Hi aLf, This is quite odd. The first thing I would suggest is to do a Restore Device on "B". This will remove all the links that might be in that switch but not reflected in ISY. With kind regards, Michel

Hello rickerdo, You are very much correct: UPnP is only used for the initial discovery. This said, however, in cases where ISY is not assigned a static IP address, it's also used to broadcast IP changes so you would not have to know exactly what IP address your ISY has. In 2.7.7 and above (still alpha), we'll use the legacy NetBIOS over TCP to enable communicating with isy using http://isy ... but this will not work with more than one ISY on the network. Furthermore, some new computers may not have NetBIOS/TCP enabled. In any case, disabling UPnP is something that should be included in ISY. With kind regards, Michel

Hi Dodger, You can use ELK for security and Touch Switch (http://forum.universal-devices.com/viewforum.php?f=49) for Cameras and everything else. This said, however, except for full blown applications such as mControl or Home Seer, I am not sure if there are any windows programs which you are looking for. With kind regards, Michel

Hello snownh2o2, First of all, I am so very glad you posted to our forum. We've been trying to get a hold of you via email and all was bounced. I think the best thing to do would be to schedule a call with our tech support to go through this with you. Please call us at 818-631-0333 between 9:00 to 5:00 PDT. We usually get back to you within an hour. So, please make sure you call when you certain we can get a hold of you within an hour. With kind regards, Michel

Hi all, Please note that ISY recalculates schedules every time the time difference is more than the grace period. So, if your ISY goes back to 1941 and then after the next NTP it comes back to 2009, then ISY will automatically re-evaluate all the schedules. At the moment, I believe the problem is in the GUI itself as reported by Chuck and not in ISY. We are working on it. With kind regards, Michel

Hi Tim, You have gotten it correctly: one or more of the members of the scene for which your MS is the controller is not sending an ACK. I recommend the following: 1. Bring the Access Point closer to your MS 2. Restore responders in the scene one at a time and test With kind regards, Michel

Hi Chuck, In ISY there's no such a thing as program stack space. Every piece of object and memory is mapped out and there's absolutely no way for you to run out of memory without receiving a warning. This problem seems to be Admin Console related. Please check your email for instructions. With kind regards, Michel

Hi Rick, Unfortunately not but I think this is a good feature to add. As such, I am going to add it to our list. The only issue is that currently that's the only way clients (such as Interface Go, iLinc, mControl, IES touch screens) can find where ISY is. With kind regards, Michel

Hi Brian, thanks so very much. Please do keep and eye and let me know if you still get this error. Chuck had this error even with the North America NTP server and now he's trying our 2.7.7 alpha. With kind regards, Michel