Technically AVT is a dual setpoint heating-cooling thermostat, so the generic CurrentSetpoint (in service
urn:upnp-org:serviceId:TemperatureSetpoint1) is undefined. In strict UPnP, it’s value would depend on whatever the last set
Application value is in that service (via the
SetApplication action), which complicates matters even further.
The variables of the same name in
TemperatureSetpoint_Cool are the Vera way of expressing the heating and cooling setpoints, respectively, without the use of the
Application variable and its associated action. These are further mimicked by the AVT-specific variables
SetpointCooling, which were provided for clarity but frankly don’t add much (of that, or anything else).
AVT will attempt to track the generic CurrentSetpoint variable to the appropriate setpoint of the current operating mode, but it only does so when the thermostat enters that mode (e.g. when it starts cooling, it sets generic CurrentSetpoint to the current cooling setpoint; when it sets generic CurrentSetpoint to the current heating Setpoint). But until there’s a mode change (i.e. when the thermostat is idle), it retains whatever value it was last given.