Michel Kohanim

Hi Joe, Is it really every few minutes? If it happens up to 10 times a day, I wouldn't worry about it at all. If it really happens every few minutes and continuously then there's surely something very wrong. With kind regards, Michel

Hi, There are two things that you must look for: 1. Loose neutral (I think it's white) wire 2. The load for these device might actually be the cause of all the issues With kind regards, Michel

Hi again, It is really not MobiLincs fault! MobiLinc is using ISY's APIs and therefore I have to assume that you have communications problems with those devices. Would you be kind enough to let me know the firmware version for your SWL Relay? If v35, then I bet that's the issue right there. If not, then we have to figure out why those devices do not respond reliably to scene commands. With kind regards, Michel

Hi dansmith, Good catch! Yes, indeed the program is re-evaluated every time an associated condition is changed. As far as D3 On, is it still happening? With kind regards, Michel

Hi gfridland, Apologies for a tardy reply as we were trying to reproduce this problem to no avail. As such, would you be kind enough to 1. Send a copy of your programs (My Programs | Export) to support@universal-devices.com 2. In the email, list the name of the programs that you think are causing the problem With kind regards, Michel

Hello sceaton, Apologies for a tardy reply. You are correct, I didn't notice that. If you are sure that you linked your thermostat at the OFF mode, then I have no choice but to suspect the thermostat dongle. This said, I am also wondering if you have thermostat from a batch with different firmware (this has happened before) ... As such, although I do recommend replacing your thermostat, I am going to keep an eye out for others with the same issue. With kind regards, Michel

Hi sceaton, But, indeed you are getting setpoint changes from the thermostat: Mon 03/22/2010 05:56:57 PM : [ 14 6 CC 1] CLISP 142 (Set point) Mon 03/22/2010 05:56:57 PM : [ 14 6 CC 1] CLISPC 154 (Cool set point) Mon 03/22/2010 05:56:57 PM : [ 14 6 CC 1] CLISPH 142 (Heat set point) Do these not get reflected in the Admin Console on the thermostat's main node? What are you are not getting is fan mode and the heat/cool calls. Is this the only thermostat you have? With kind regards, Michel

Hi Genstr, The fact that you get the second login prompt points to some networking issues. What firewall software do you have. Yes, LED brightness is supported for KPL 2D and above however the prerequisites are: 1. ISY Admin Console must report the version for your KPL as a number above 2D (not 00) 2. You must be using the latest URL ... using /99i will not work. So, please try http://www.universal-devices.com/99i/2.7.13/admin.jnlp I am more concerned about the double login and status issues. Please do let us know so that perhaps we could setup a tech support session to login to your computer and see what's causing all the issues. With kind regards, Michel

Hi Illusion, I verified this issue and it's now a bug that we'll fix for the next release. Apologies for the inconvenience. With kind regards, Michel

Hi bbconvert, The maximum number depends on your model number: 99i support 256 nodes=devices/scenes/folders, so, if you do not use any scenes at all, the total number of thermostats is 256/4 (nodes per thermostat)=64. If you have PRO series, then it would be 1024/4=256. With kind regards, Michel

Hi Justin, I am so very glad to hear it! You can remove the the KPL from ISY and it removes all the buttons from the associated scenes/folders automatically. This said, however, it would still take a long time to process all the communications. With kind regards, Michel

Hi johnmsch, Yes! Can you tell me what firewall software you are running on your computer? Also, you might want to try https://your.isy.ip.address (some firewalls are more lenient on https sites). With kind regards, Michel

Hi dkaleita, Thanks so very much for the update. This is indeed strange ... With kind regards, Michel

Hi Dodger, I am so very sorry to hear this. If the RX is lit all the time, then you are surely having a PLM issue. What you want to do is: 1. Unplug your PLM from the outlet, wait for a minute, and then plug it back in. If this does not solve the issue, then 2. Try using a different cable between the PLM and ISY, if this does not solve the issue, then 3. I strongly recommend getting a replacement PLM With kind regards, Michel

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