Michel Kohanim

Hi Dan, This is good! Would you be kind enough to right mouse click My Programs, choose Find/Replace, and look for any other occurrences of D3 On or Off? I just want to make sure there are no other programs that are causing this issue. With kind regards, Michel

Hi Shawn, Excellent!!!! You see, at least we know that we are not getting status updates from the thermostat. This could be caused by two scenarios: 1. Access Point ... I doubt this is the case since you mentioned that you get the correct status for your setpoints when they are changed (even from the thermostat?) 2. Misconfiguration ... please note that if you added your thermostat in any mode other than OFF then this could certainly happen 3. You are not waiting long enough for the thermostat to send you the status. Usually for Fan and Heat/Cool calling events, the thermostat waits between 30 seconds to 2 minutes (haven't figured out exactly how long) to account for fluctuations You might want to remove the thermostat and add it back this time ensuring that it is indeed in the OFF mode when registering. If you don't mind, we'll address other issues when we have solved this one. With kind regards, Michel

Hi Nick, We could but, again, there's a difference between beta and official version. Based on the number of Beta users (less than 10% of the total users), it does not make sense to include development links to our releases. With kind regards, Michel

Hi jkraus, That's quite odd. Would you be kind enough to check the ISY table for R1 and see if there are any references to the KPL? If not, and if Compare is identical, then I must assume that the problem is R1. If possible, please do a factory reset on it and then a restore. With kind regards, Michel

Hi stevehoyt, I think the problem with your system is because of the initial Query which changes the status of all your devices and thus the programs get re-evaluated for those that have conditions dependent on that device. gfridland, Do you have any other programs dependent on this program? With kind regards, Michel

Hi dkaleita, Thanks so very much. I was thinking about the same thing ... DHCP lease should not be renewed every few seconds UNLESS that's what you have set for the lease time in your router. Since I do not see any more errors, I must suspect this to be at least one of the issues. Can you please check the DHCP lease time in your router? With kind regards, Michel

Hi apostolakis, In the program I was referring to, the condition was Anded with another condition. Please make sure that your condition is not Or-ed with another condition. With kind regards, Michel I am confused here. I have lots of programs listed as being "true" on the program summary page with time conditions even though it is not presently that time.

Hi AnthemAVM, You mentioned that this started happening after you installed WHS. If this is indeed the case: 1. Can you try an shutdown WHS, wait about 5 minutes, and let me know if the lights stop blinking 2. Is it at all possible another device on your network has the same IP address as ISY? With kind regards, Michel

Hi gfridland, Are you rebooting the system during those times +/- the grace period? Or, do they run regardless of the time. Furthermore, can you tell me whether or not you have Run at Reboot set for this program? With kind regards, Michel

Hi auger66, At a high level, you can use the status of programs as flags that can be used in other programs. Perhaps this example can better illustrate this concept: http://www.universal-devices.com/mwiki/ ... down_Timer With kind regards, Michel

Hi dansmith, The last runtime and finish time are accurate since the light level dropped to below 12 at 5:37 and thus the program was evaluated to FALSE and the Else path was run. So, those do not give us enough information to figure out why you got the flicker. What we need to do is to go to the log (Tools | Log) and check the activity for 5:37 PM and specifically, we need to know if anything else turned on and then off that unit. With kind regards, Michel

Hi Illusion, Ah ... in Java preferences, can you please make sure you click the option such that the application/applet runs in the browser's process and not its own process. This might explain the discrepancy between firefox and safari. ryarber, we are hoping to have an official release the next time around in which case the url becomes /99i (without any release versions). As such, I do note your request but must postpone it till after our official release. burakk, on MAC drag and drop does not work that's why you should use the Copy menu item. With kind regards, Michel

Hello dkaleita, First of all I do not think you are doing anything wrong. The bottom line is that ISY cannot contact your DNS server to resolve names to IPs. This could be ISY related (hardware) or network related. The first thing I would do is to use an IP address instead of pool.ntp.org (i.e. go to the command prompt, and type nslookup pool.ntp.org ). If this works it means that ISY can access the Internet but not the DNS server. Also, it would help a lot if you could look at your router's log and see if there is any traffic for your ISY, whether or not they are being blocked, and the reason code. With kind regards, Michel

Hi Paul, Quite interesting but, at the same time, the epitome of problems with all SWL 35s: randomly going bad and causing comm errors. If it were my installation, I would replace them all especially if you bought all of them at the same time and thus the likelihood of all of them being from the same manufacturing batch. With kind regards, Michel

Hi all, All devices with sense can report status changes. The main issue is that we get the same signal whether or not the device is turned OFF (locally) or the load has gone bad. For INSTEON there's no distinction between the two (unfortunately). With kind regards, Michel

Hi AnthemAVM, Unless the MEM/Error blinking lights are persistent (i.e. they do NOT go away) I would not worry about them. Now, did you move port 80 to 1501 or port 443 to 1501? With kind regards, Michel

Hi drw, I am so very sorry for the inconvenience. This should not have happened ... just to be in synch, would you be kind enough to upgrade to 2.7.13 which seems to be much more stable than 2.7.6? With kind regards, Michel

Hi sceaton, Would you be kind enough to check the following and let us know: 1. Ensure that your program is Enabled AND that you have V2 thermostats (V1 will not work) 2. Go to Program Summary so that you can see the status of programs. Then, please go to Tools | Diagnostics | Event Viewer and choose Level 3. 3. Cause your thermostat to call for Heat then: 1. Check out the traffic in the Event Viewer 2. If you see the events that change the mode to Call for Heat, then look at the program summary page and check the last runtime In short, we want to make sure that your ISY indeed receives that event. If it does not, then we have to figure out where the signal is lost. With kind regards, Michel

Hi Justin, I think the problem is that ISY does not know the version number (.00) of your KPLs and thus does not let you have a sub button control the load. Unfortunately, at this point, I must recommend the following: 1. Remove your KPL from ISY 2. Add it back using either of the following methods: -- Link Management | Start Linking ... then push and hold the set button on your KPL OR -- Link Management | Add New INSTEON Device and ensure that you are using Auto Discover (do not pick a device from the list) With kind regards, Michel

Hi illusion, First of all, there was indeed a problem with v1 thermostats providing the wrong setpoint. Second of all, it's always best to use either Heat or Cool setpoint (not just setpoint). And, finally, when the thermostat mode is Off, the setpoints change to 0 which causes your condition to be true. With kind regards, Michel

Hi bbconvert, Unfortunately not. Have you considered our REST interface? With kind regards, Michel

Hi bbconvert, Unfortunately not. You may want to consider third party interfaces such as InterfaceGo, TouchSwitch, ISY AJAX, ... With kind regards, Michel

Hello again, Thanks so very much for the detailed report. So, would you say that most of the issues are with controlling the load on the Dining Room KPL? If so, would you be kind enough to give me the firmware version as reported by ISY for this device? Also, have you tried to compare the links to this KPL vs. those in ISY? With kind regards, Michel

Hi stevehoyt, We are working on this issue. There was indeed a related bug but I am not convinced it would address all the issues. Still investigating. With kind regards, Michel

Hi Paul, Is is possible that some of them are on while others are off? The reason I asked for replacement is because I have never seen such a behavior nor has it ever been reported. So, if we make sure that they do not have the same brightness (either all off or all on), then that surely indicates a problem. If the compare is identical, then please do a factory reset on your KPL and do another restore. With kind regards, Michel