Michel Kohanim

Hi zyll, I am so very sorry to hear. There are a few cases where this could happen. Just to save you more frustration, I think it would be best to contact our support team so that we can figure out what's going on. In the meantime, please make sure: 1. You have version 3.2.6 installed -- a. Help | About -- b. http://your.isy.ip.address/rest/config 2. Check the number of links you have in your PLM With kind regards, Michel

Hi Paul, got your log ... will review shortly. With kind regards, Michel

Xathros, For some reason the validation routine does not work with GMT -5 and 40/80 lat/long. This might be something wrong with our validation routine but it's pretty basic. It only works with Central Time ( GMT -6). With kind regards, Michel

Hi jmed999, Please do make sure that you have the correct DNS settings under Configuration Tab | Network Settings. If you have configured your ISY with a static IP address, you might want to try DHCP or DHCP reservation since, some routers, do not allow DNS queries through if the IP is not assigned by them. With kind regards, Michel

Unfortunately not for INSTEON traffic since the system becomes quite slow. With kind regards, Michel

Hi ekuzmack, Yes, there is. Please do be kind enough to check our store front. With kind regards, Michel

Hello jmed999, Unfortunately that information is not available through INSTEON APIs. I do not understand the second question! With kind regards, Michel

Thanks Xathros. The problem is that ISY validates the longitude against the timezone. I suspect you are in Central Time so, you must use -6 for Timezone offset BEFORE trying to set the longitude. Also, in ISY, longitudes are positive. With kind regards, Michel

Hi hart2hart, I really have no explanations and trying to figure out how to reproduce to make sure it's not a bug in our firmware. I have tried every possible permutation and the only time I get crazy values is if the thermostat is in a scene (yours are not). I am quite concerned that that thermostat is sending bogus values. Any help/pointers would be extremely appreciated. With kind regards, Michel

Thank you Clarence ... With kind regards, Michel

Hi hart2hart, So, you have this problem with at least two of your thermostats. How about the third one? And, what's the difference between these two and the third? With kind regards, Michel

Hi Clarence, That does not make sense. When you rebooted ISY, did you notice the pattern of lights on the front of the unit? With kind regards, Michel

Hi bmiller, Please take a look here: http://www.universal-devices.com/mwiki/ ... PnP_Router Also, when you go to PortForward.com, choose your router from the list and you will find great explanation of what you need to put and where. In short, Private IP address MUST be the address of your ISY as reported by the Admin Console. With kind regards, Michel

Hello sanders2222, Please send your log to support@universal-devices.com (Tools | Log) as I do not see any excerpts. With kind regards, Michel

Hello hlaiii, Is it possible that you have the humidity reporting disabled? Also, do you have a humidity sensor on any of these devices? With kind regards, Michel

Hello Raynentye, Please send an email to sales@universal-devices.com. With kind regards, Michel

Hello hart2hart, It should happen at start up and then every polling interval increments. With kind regards, Michel

Hi hart2hart, That's not good. So, the programs were disabled but we still got those events. Looking at your events, I do not see anything prior to that event that could've caused the set point to jump to 107. i.e. nothing from ISY and nothing from the web. How many thermostats do you have? If more than one, does this happen on all? If not, what are the differences between them? With kind regards, Michel

Hello jesse.clauson, Thanks so very much for the update. Please do keep an eye and please note that restore should be the LAST thing you would do. In most cases, restore does not fix the actual problem. With kind regards, Michel

Hello hart2hart, Boy, this is not good at all. I do not see any entries indicating any type of command being sent from ISY (Web, Program, etc.) ... the status changed on its own. Is it possible that your thermostat has preconfigured programs/schedules? With kind regards, Michel

Hello sanders2222, This is quite odd. So, in short, the program stated the status to be true but the last runtime was not updated and the program did not run? And, you could not run any other program? If this is the case, then, could you actually turn on/off any other devices? If you look at your regular log, do you see any -2s? With kind regards, Michel

Hello deanryan, THANK YOU for sharing your experience. Not only it will help others but it will help our own tech support team. Thanks again and with kind regards, Michel

bmiller, Please do be kind enough to contact our support team so that we can figure out what's going on. What you are experiencing is not normal. With kind regards, Michel

Hello hart2hart, Last WB data is NOT stored anywhere ... only the polling interval! With kind regards, Michel

Hello hart2hart, Thank you. The problem is that I am not sure if this message is sent by the thermostat or by ISY. You see: Great Room / Great Room:Thermostat Thermostat Mode Cool Thu 2012/08/02 06:46:29 PM Program Log Great Room / Great Room:Thermostat Cool Setpoint 16â–‘ Thu 2012/08/02 06:46:31 PM System Log The question is: where is this message coming from? Based on the log entry, it's generated by the system. i.e. thermostat->PLM->ISY (system). This said, I am not convinced this to be the case If it's at all possible to reproduce this scenario, may I humbly ask you to open the Event Viewer on level 3 so that we can figure out where the message is coming from? Thanks and with kind regards, Michel