Shill,
Very interesting. After I first updated the plug-in to version l.25 I got a windows error box stating that Thermostat Plug-In has stopped running. Then I disabled the plug-in using the plug-in management page and re-enabled it again. Trace was off (info) and the plug-in was working pretty well. It seemed to update devices ok and when selecting new setpoints, etc. they would actually change and update. Then I turned trace on and devices would not update. Probably because of timing issues with the overhead of the trace log functions? Then the longer the plug-in was running, the worse it got. Devices wouldn't change and update properly and then I got another windows error box stating that the thermostat plug-in had stopped running. Tried to disable plug-in and re-enable plug-in and got more windows error boxes saying that the thermostat plug-in had stopped working. Seems the plug-in is having trouble retrieving data from the thermostat. It appears to connect ok to thermostat but maybe there is some timing setting that needs to be changed to allow more time to retrieve data from thermostat. Just a guess and probably not a good one. What is really problematic are the windows error boxes stating the thermostat plug-in has stopped working. Again there for a bit it was at least working. I also noted that when you increment the setpoint by +1 or -1 that it doesn't get updated properly. When the windows error boxes come up of course can't get log information and when trace log is active devices are not updating at all. Let me know what I can do to help you try and fix these issues. Are others having these issues too? Thanks much Shill !!!!!! For a bit there I thought it just might be fixed. Maybe it has to do with homeseer .435 update and it might help to check with homeseer to see if there are any changes they made that may affect plug-ins that they haven't told anyone about, especially the plug-in developers. I hope this information helps a bit......Rick
Very interesting. After I first updated the plug-in to version l.25 I got a windows error box stating that Thermostat Plug-In has stopped running. Then I disabled the plug-in using the plug-in management page and re-enabled it again. Trace was off (info) and the plug-in was working pretty well. It seemed to update devices ok and when selecting new setpoints, etc. they would actually change and update. Then I turned trace on and devices would not update. Probably because of timing issues with the overhead of the trace log functions? Then the longer the plug-in was running, the worse it got. Devices wouldn't change and update properly and then I got another windows error box stating that the thermostat plug-in had stopped running. Tried to disable plug-in and re-enable plug-in and got more windows error boxes saying that the thermostat plug-in had stopped working. Seems the plug-in is having trouble retrieving data from the thermostat. It appears to connect ok to thermostat but maybe there is some timing setting that needs to be changed to allow more time to retrieve data from thermostat. Just a guess and probably not a good one. What is really problematic are the windows error boxes stating the thermostat plug-in has stopped working. Again there for a bit it was at least working. I also noted that when you increment the setpoint by +1 or -1 that it doesn't get updated properly. When the windows error boxes come up of course can't get log information and when trace log is active devices are not updating at all. Let me know what I can do to help you try and fix these issues. Are others having these issues too? Thanks much Shill !!!!!! For a bit there I thought it just might be fixed. Maybe it has to do with homeseer .435 update and it might help to check with homeseer to see if there are any changes they made that may affect plug-ins that they haven't told anyone about, especially the plug-in developers. I hope this information helps a bit......Rick
Comment