I would appreciate some help understanding the Thermostat Controller 2.0 (TC) functionality. I have read the documentation available, unfornuately it is a bit thin in areas (i.e. Idle Method, Control Offset, hysteresis).
My intention is to take advantage of multiple temperature sensors at some point, but first I would like to get TC working together with Thermostat Scheduler 2.0. As the documentation states, I need to assocaiate the scheduler with the virtual controller that TC creates which I have done. I have disabled the schedule in the physical T-Stat i.e. I have put it in 'permanent hold' state to allow Hubitat to set mode, fan and setpoints. My intention is to have t-stat setpoints set in accordance with Hubitat modes as defined in Mode Manager.
Note: I operate in Celcius. None of the drivers and apps I work with offer an option for me to declare that although I have my hub settings set accordingly.
Here is a capture of the Nexia / Trane XL824 t-stat driver from HPM.
For my testing I have simply forced a change in the Mode from Day to Away. I am purposely using setpoints with a large variance thinking the offsets are not coming into play.
The Scheduler panel looks like this:
.
After the Mode change, the logs show the Scheduler acting as expected:
although the Controlled t-stat is not updating:
and it's log:
also the controlled t-stat has no Events of interest:
I don't believe the Nexia/Trane driver is at fault, since I note that if I have the Thermostat Schedule bypass the Thermostat Controller virtual controller the setpoints are passed through to the T-stat and acted upon successfully. The documentation advises against doing this but that is my way around the issue in the short term.
P.S. How significant is the metric issue with the Controller? Is there math going on it that makes it an oversimplification to simply be putting Celcius figures in prompts where Fahrenheit is implied?
Thanks in advance for any and all advise.
P.S. I am running one a C8 with build 24.0.1.151
