Michel Kohanim

Hi George, Those error indicate one of the following: 1. ISY is not connected to the network ... in your case, this cannot be the issue since you can already connect to your ISY 2. For some reason your router is refusing to renew your DHCP lease ... if you can actually get to your system, then I would really not worry about this since ISY keeps asking for a lease renewal and will eventually get it With kind regards, Michel

Hi Kevin, Those files are the state files and not backup files. The backup file names have the following format: ISY-Backup.yyyy-mm-dd.hh.mm.ss.zip. Please ensure that the file is not actually backed up in the directory that you chose during backup. And finally, are you using Vista? With kind regards, Michel

Hi ryarber, If you have DHCP I would not change it. Can you tell me if you can synch with pool.ntp.org? Or, have you setup notifications and whether or not you get them delivered? With kind regards, Michel

Hi again, Thanks! Here's the link to errors: http://www.universal-devices.com/mwiki/ ... r_Messages -60001 = NTP Address Resolution Failed -60006 = NTP Server Not Responding Would you be kind enough to let me know what you are using for DNS server for your ISY? If you are using DHCP, you should be OK. But, if not, then, in all likelihood, the DNS setting is pointing to a server outside of your LAN and hence the issues. With kind regards, Michel

Hello Kevin, Can you post back name of these files? Back up should ALWAY - and without exceptions - produce a zip file. With kind regards, Michel

Hi smithjoy, Wait is interrupted if the condition becomes false. With kind regards, Michel

Hi ryarber, It should work. I just tested an IP address and it works fine. Questions: 1. Is your ISY on the same network as your router? 2. What do you see in your log. I am especially interested in errors with -6000x prefix With kind regards, Michel

Hi jcip, I am so very pleased to hear that everything is working out. Chris, 2.7.7 should solve this issue. With kind regards, Michel

Hi jcip, By brute force I mean: 1. You use Add New INSTEON Device 2. You do not use Auto Discover (you use the list and pick your device) In some cases, when #2 tries to get the firmware version from the device, the device does not respond back and thus 0.00. In some cases (such as motion sensors and triggerlincs) you do not have a choice but to use brute force. I doubt that the problems with your system are related to this. ISY uses firmware version only in a very few places and especially for KPLs to figure out what functions are supported. With kind regards, Michel

Hi jcip, I see the problem: you have added this KPL using brute force and unfortunately ISY was not able to retrieve its version number. Although quite painful, but may I humbly recommend the following: 1. Upgrade to 2.7.7 to ensure you have the most up to date device support 2. Remove your KPL from ISY and then add it back using New INSTEON Device | Auto Discover or Link Management | Start Linking I am so terribly sorry for the inconvenience. With kind regards, Michel

Hi jcip, Thanks for the info and yes it does make perfect sense in the following case: Your KPL is firmware 1.5 or below (about 2 years old) Only the newer KPLs allow for the load button to be controlled by a sub button. With kind regards, Michel

Hi Joe, Apologies for the inconvenience. Please try the following URL instead (at home): https://www.homeorchestrator.com/ssl/insteon/ With kind regards, Michel

JacquesB, Thanks so very much. This is indeed very important for security reasons. We are still trying to figure out why the IOLinc always returns the status of the relay and having this workaround helps a lot. With kind regards, Michel

Hi Mark, If your controller is a keypadlinc, then you can use the Non Toggle feature of any button from that KPL to either always turn a scene ON or OFF (non toggle). The catch is that you have to make sure you do not have any TOGGLE controllers in the same scene (such as SWLs, etc.). With kind regards, Michel

Hi jcip, Click on button C within that scene, look to your right and make sure the on level is NOT zero and ramp rate is not 9 minutes for button A (of the same KPL). With kind regards, Michel

Hi Jon, Our hosting is broken but, if you don't mind 2.7.7 alpha, it gets redirected to a different website which works. If you are interested, please send an email to support@universal-devices.com. With kind regards, Michel

Hi WayneW, If the change is only the PLM then there's no need to do restore devices; restore PLM changes the PLM id of all devices with the PLM id of the newly installed PLM. With kind regards, Michel

Hi fastbird1, Right mouse click on the desired program, choose Copy to Clipboard, and then right mouse click on this area where you are posting to and then choose Paste. With kind regards, Michel

Hi mpf541, Apologies for the inconvenience. When ISY starts, it automatically does a query of the system (unless you disable this feature in the Configuration/System tab in the bottom left corner box). Now, the main issue is that, unfortunately so, the IOLinc query ALWAYS returns the status of the relay instead of the sensor. This causes major issues after power failure since, in most cases, after power outage the relay is on (sometimes it does not hold its previous state) while the sensor is not shorted. We have already notified SH of this issue and we are tracking it. At the moment, the only thing I can suggest is the following: 1. Create an All Scene which excludes the IOLinc 2. In the Query All program, replace My Lighting with the All Scene 3. Create a new program which is run at start up and which CLOSES your garage door regardless of its state With kind regards, Michel

Hi jason|99, Good to hear. Yes, it is very possible. May I humbly recommend the perusal of our Wiki for Programming: http://www.universal-devices.com/mwiki/ ... e#Programs With kind regards, Michel

Hello unispeed, My pleasure. I am not sure why you could not reboot from the Configuration Tab. May I ask why you were trying to Restore? Restore should only be done when there system configuration is no longer equal to ISY's configuration. With kind regards, Michel

Hi fastbird1, If your camera can issue network commands, then you can immediately use our REST interface: http://forum.universal-devices.com/viewtopic.php?t=2252 If it has to be a batch file running on a computer, then you would have to use any of our WSDK, JSDK, and/or REST interface to create an application for your specific needs: http://forum.universal-devices.com/viewforum.php?f=2 With kind regards, Michel

Hi Mark, Apologies for the inconvenience. This is a known bug in 2.7.5 and 2.7.6 which has been fixed in 2.7.7 (http://forum.universal-devices.com/viewtopic.php?t=930). There's absolutely no harm done to your system ... all you have to do is to reboot your ISY. With kind regards, Michel

RLIKWARTZ, What URL are you using? It seems a lot like your use of 2.7.6 (or official URL) to access 2.7.7. Would you be kind enough to use either of the following: http://www.universal-devices.com/99i/2.7.7/admin OR http://www.universal-devices.com/99i/2.7.7/admin.jnlp With kind regards, Michel

Hi Xathros, I am going to test it again on our Ubuntu and let you know. RLIWARTZ, this is very strange indeed. Are you sure your cache has been cleared? With kind regards, Michel