heatingSetpoint vs thermostatSetpoint for capability "Thermostat"

⚙️ Custom Apps and Drivers
1

In looking through the docs and the example virtual thermostat source I cannot find any explanation about what the difference is for heatingSetpoint vs thermostatSetpoint for the Thermostat capability, can anyone shed some light on this topic?

Thanks

2

Typically, thermostats or at least their drivers track heatingSetpoint and coolingSetpoint separately, then the thermostatSetpoint attribute will show whichever setpoint is the one that actually matters at the moment based on the current thermostatMode (or the last one that did matter if it's off).

Here are the current states from an actual thermostat I have as one example:

  • coolingSetpoint : 78.0
  • heatingSetpoint : 60.0
  • humidity : 51
  • supportedThermostatFanModes : ["auto","on"]
  • supportedThermostatModes : ["off","heat","cool","emergency heat"]
  • temperature : 63.0
  • thermostatFanMode : auto
  • thermostatMode : heat
  • thermostatOperatingState : idle
  • thermostatSetpoint : 60.0
2 Likes
3

And I believe some thermostats will use the two hearing and cooling set points when in auto mode, if they have one. Along with some king of buffer, potentially.

4

My understanding is that the thermostatSetpoint attribute is needed only for Google Home integration compatibility.

1 Like
5

This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.