Jeff Kocur

I was able to determine why I was having trouble with multiple thermostats. In order for the scripts to work properly, it is mandatory to assign a unique label to each of Nest Devices (on the nest device or in the app). I noticed that "name" field in the scripts was blank. I had not populated the label when installing the Nests because the "where" was unique enough for me (Upstairs / Downstairs), but since I added the label, I now see that "name" is populated with the corresponding label and the EG scripts/macros now work properly. Incidentally, I still have a problem that the ISY for Eventghost plugin causes EG to lock up when I enable on a Windows 7 machine. Enabling the Nest Thermostat plugin does not cause the issue. I have the same results on two separate Windows 7 machines, but no issue on a Windows 8 machine. If anyone has any ideas how to fix this, I'd appreciate it since I'd prefer to use one of the Windows 7 machines to run EG. Thanks!

I have two nest thermostats. It appears that the values from the first thermostat are also being sent to ISY for the second thermostat. E.g, Ambient Temp for the first thermostat is 74. Ambient Temp for second thermostat is 73. but both variables in ISY are showing 74. I've set up two different state variables in ISY (15 & 16) and entered the 15 & 16 in the respective variables in the EG config. I also observed that the values for the first thermostat are sent to ISY more frequently than the second (it might be that the second thermostat values are only sent at startup). I'm just starting with this, so I may be missing something. Your assistance is appreciated!

One of my thermostats is v.0B and the other is v.0D. As previously mentioned, both exhibit the same behavior.

I have two of these thermostats and they both exhibit the same behavior. They both will not enter the Program Auto mode from an ISY program or the ISY admin console. I have confirmed that all other modes work fine on both thermostats from either an ISY program or the ISYadmin console. I'm now using scenes within my ISY programs to achieve my desired thermostat activitity and am not using the program auto mode so this isn't a problem for me. However, it does appear to be an issue. Thanks kck for confirming that I'm not crazy and that others have this issue too . I suspect its more widespread, but since most folks probably avoid the program auto mode it's probably not noticed. Thanks, Jeff

I recently received a new 2441TH Thermostat and noticed something strange when operating it from the admin console (or from within an ISY program). If I change the thermostat to thermostat mode "Program Auto" from the admin console or from an ISY program it does not enter the "Program Auto" mode. It remains in the mode that it was in prior to sending the "Program Auto" command. Changing to any other mode from the admin console works fine (Heat, Cool, Auto or Off). I can put the thermostat into Program Auto mode directly on the thermostat and the mode in the admin console gets updated with the correct mode (Program Auto). I have also found a work-around in that I can put the thermostat into "Program Auto" mode from an ISY program by sending Insteon command "Program Cool" or "Program Heat" from the program (This work-around only works in ISY programs. These modes (Program Heat and Program Cool) are not available in the admin console because I don't think they are actual modes supported by the 2441TH). Does anyone else experience the same problem? Thanks, Jeff