You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Since Google brought me here and I've been working with these variables lately, some added context...
On UI7, the TemperatureSetpoint1_Cool and TemperatureSetpoint1_Heat variables still work and remain important IF you want to set separate Heat/Cool set points. This is especially important for AutoChangeOver thermostat modes. If you use the TemperatureSetpoint1 variable only, it will auto set the set point based on the active mode, but can produce some unexpected results with Auto mode. In Auto mode, using TemperatureSetpoint1 will set the thermostat SetPoint, BUT Heat and Cool set points will automatically be +/- 2 or 3 degrees.
I've also observed that, by default, info provided for Thermostat devices (using /data_request?id=sdata) only includes one set point for setpoint, heat, and cool. You do not get the separate values for heat/cool. To get the individual set points, must explicitly request TemperatureSetpoint1_Cool and TemperatureSetpoint1_Heat.
Hope this helps someone that follows Google here, too.
http://wiki.micasaverde.com/index.php/Luup_UPnP_Variables_and_Actions
NOTE: On UI7, urn:upnp-org:serviceId:TemperatureSetpoint1_Heat and urn:upnp-org:serviceId:TemperatureSetpoint1_Cool are obsolete.
These are replaced by "TemperatureSetpoint1" which affects the current mode. The Nest plugin does not appear to support this yet.
The text was updated successfully, but these errors were encountered: