HS version: 4.2.13.0
Plugin version: 4.2.0.10
HS server OS: Win10 Pro
Thermostat model: RTH6580WF (2 ea.)
Data dump: attached
Log file: attached
Description of problem:
Used v.3 of the plugin for years without issue. Upgraded to v.4 recently and I *think* it worked initially although not certain. Two identical thermostats in vacation property, not used since before PI update to v.4 so no attempts to check or change tstat settings and not sure sure when problem arose. An event sets both thermostats' heat and cool setpoints and permanent hold (on) when we're arriving at the house. A second event does exactly the same with "eco" setpoints when we leave. Otherwise I seldom if ever interact with the plugin except for occasional version updates.
Updated PI to 4.2.0.10 this morning and saw HS features weren't updating properly. Opened PI config and credentials weren't entered (maybe missing since upgrade to v.4?). Added credentials and both tstats were immediately found. New HS devices/features weren't created--thankfully.
When I run one of the events to set all heat/cool setpoints, the HS features update to the new values and capi control entries are logged in HS as expected. No errors. But the updates never reach the cloud. Even after waiting through multiple update cycles, the HS features show the values entered by the event, even though the TCC app and web interface never reflect the new values. Only when I click "Update" on the Status feature do the HS features revert to the prior settings--i.e., the actual settings on the thermostat since the new values weren't received from the plugin.
I believe the trace log should reflect a run of each of the events described above. Thank you for looking into it.
Honeywell_tstat_dump.txt
HSPI_SKWARE_HW_WIFI_TSTAT.txt
Plugin version: 4.2.0.10
HS server OS: Win10 Pro
Thermostat model: RTH6580WF (2 ea.)
Data dump: attached
Log file: attached
Description of problem:
Used v.3 of the plugin for years without issue. Upgraded to v.4 recently and I *think* it worked initially although not certain. Two identical thermostats in vacation property, not used since before PI update to v.4 so no attempts to check or change tstat settings and not sure sure when problem arose. An event sets both thermostats' heat and cool setpoints and permanent hold (on) when we're arriving at the house. A second event does exactly the same with "eco" setpoints when we leave. Otherwise I seldom if ever interact with the plugin except for occasional version updates.
Updated PI to 4.2.0.10 this morning and saw HS features weren't updating properly. Opened PI config and credentials weren't entered (maybe missing since upgrade to v.4?). Added credentials and both tstats were immediately found. New HS devices/features weren't created--thankfully.
When I run one of the events to set all heat/cool setpoints, the HS features update to the new values and capi control entries are logged in HS as expected. No errors. But the updates never reach the cloud. Even after waiting through multiple update cycles, the HS features show the values entered by the event, even though the TCC app and web interface never reflect the new values. Only when I click "Update" on the Status feature do the HS features revert to the prior settings--i.e., the actual settings on the thermostat since the new values weren't received from the plugin.
I believe the trace log should reflect a run of each of the events described above. Thank you for looking into it.
Honeywell_tstat_dump.txt
HSPI_SKWARE_HW_WIFI_TSTAT.txt
Comment