Michel Kohanim

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

Hi brad77, If you are using HTTPS, please do ensure that you've installed your own self signed certificate. Furthermore, you can try increasing the HTTP/S timeout values in ISY. Telnet to ISY, login, and issue CWT. With kind regards, Michel

Hi Illusion, This is great analysis; thanks so very much for providing this feedback. I am going to send this link to SmartHome engineering team .. I am sure they will find it quite useful. With kind regards, Michel

Hi ergodic, Yes, multiple login for the Java applet is a bug which is going to be fixed so that you would not have to login twice once logged into ISY. With kind regards, Michel

Hello Matt, Unfortunately All On/Off are INSTEON constructs and thus ISY's folders/scenes have no impact on them. In short, as soon as you add a device to ISY then it will respond to All On/Off scenes especially if it's part of a scene. What you might want to do is to create an All scene that does not include your ApplianceLinc for the waterfall. With kind regards, Michel

Hi Chuck, No, that's not what I am saying and I do apologize for the confusion. In ISY itself, all devices are linked to My Lighting and thus All On/Off works regardless of which folder they have been moved to. In short, beyond cosmetic effects, folders have no logical functions: nodes are either devices or scenes. With kind regards, Michel

Hi all, Thanks so very much for your patience. It would be great if you could tell me whether or not you have any of the following modules installed/integrated with your ISY: 1. Networking 2. Weatherbug 3. HomeSeer plugin Chuck has been kind enough to install our 2.7.7 alpha to see if there are any improvements. I'll keep everyone posted with the results. Thanks again and with kind regards, Michel

Hi Brian and Chuck, Would you be kind enough to try the following ntp servers and let me know if the probelm persists? 1.north-america.pool.ntp.org 2.north-america.pool.ntp.org 3.north-america.pool.ntp.org Please note that 1, 2, and 3 are all part of the URL. I am currently using: 1.north-america.pool.ntp.org With kind regards, Michel

Hi ergodic, LOL ... you might be right but - mostly from insurance purposes - we cannot take that risk especially since ISY integrates with ELK security system and can open/close garage doors (not just lights/thermostats). Now, is your wife using the IE/Firefox version or is she using the admin console? On IE/Firefox, isn't there an option to save the passwords? With kind regards, Michel

Hi reakhavoc, The condition is using "And" which means that if any of the conditions becomes false, then the program stops. I do not think this is what you want. Is it? With kind regards, Michel

Hello snownh2o2, Let me start backwards: 1. Yes, there's a command for All On/All Off: simply turn My Lighting on or off. 2. I do not recommend what you are doing (combination of programs and scenes) mostly because the impacts are not predictable. It's always best to figure out why scenes are not reliable and addressing the root causes. For instance, you might want to make sure you have Access Points plugged in correctly to bridge the phases Have you tried the Scene Test tool (Tools | Diagnostics | Scene Test)? With kind regards, Michel

Hello Donald, As Nick suggested, you will have to upgrade to 2.7.2 or above to use the REST interface. May I humbly suggest 2.7.6: http://forum.universal-devices.com/viewtopic.php?t=3007 With kind regards, Michel

Hello xd40, Only two possibilities: a. Either the signal is not getting from the PLM to your switch OR b. The switch is bad To test, if possible, move your switch (temporarily) very close to the PLM. If this works, then you know the problem is signal and not a defective switch. With kind regards, Michel

Hi Chuck, Yes, you can do this till nothing is left under My Lighting. The reason that you cannot delete My Lighting is because it's a root scene: when you want to do an All On/All Off, it's this scene which is called. In short, this is a system node to which all other nodes are attached. With kind regards, Michel

Hi jkraus, Yes, but I do not think you would want to do this: 1. You would have to make A controller and C responder in one scene 2. You would have to make C controller and A responder in the other scene 3. You will have to remove all mutex relationships Operations will be slower. I strongly recommend getting replacement KPLs and using INSTEON's native functionality. With kind regards, Michel