THERMOSTAT_SETPOINT never gets set.

[AJolly]

Setting thermostat_setpoint fails silently, It seems to only handle cooling_setpoint or heating_setpoint.

I also cant seem to set cooling_setpoint by itself (not sure if this is a HA issue or in integration issue)

[AJolly]

Theres just a lot of weirdness with climate entities: For example, if i set the hvac mode explicitly it works. if include it in a set temperature call, it does not.

  - alias: This works to set the mode
    data:
      hvac_mode: auto
    target:
      entity_id: climate.ac_right_thermo
      device_id: 732e8d2f9e2c3f5aa2f4764fb5863066
    continue_on_error: true
    action: climate.set_hvac_mode
  - alias: This does not set the mode
    data:
      target_temp_high: 80
      hvac_mode: auto
      target_temp_low: 59
      temperature: 79
    target:
      device_id: 732e8d2f9e2c3f5aa2f4764fb5863066
      entity_id: climate.ac_right_thermo
    continue_on_error: true

[jason0x43]

Sorry for taking a while to get back to you on this one.

The set_temperature command only sets temperature, and the specific temperature it sets depends on the current mode of the thermostat. If the current mode is heat+cool or auto, it will set the heating set point and/or cooling set point based on the range given to the command. If the current mode is cool or heat, it will set the cooling or heating set point to the temperature given to the command.

Setting upper and lower temperatures only really makes sense if the thermostat is dealing with a temperature range, whereas setting a specific target temperature only makes sense if the thermostat is either in heat or cool mode.

The command schema for set_temperature can accept an optional mode, so I can definitely see updating the command to support that.