Mqtt Hold mode gone away with 2022.9 used in climate thermostat

Hi to everybody.
With the 2022.9 update I get 5 warnings (one for each of my HVAC controller thermostat) and could not use them anymore.

The thermostat are all the same, just the name of topics is different, and I think the problem is the “hold” mode which my thermostat uses to understand if using internal scheduler or manual mode.

Hereafter are the configuration lines inside the configuration.yaml

climate: 
    - name: Corridoio
      unique_id: 1gf43d
      availability_topic: "corridoio/tele/LWT"
      payload_available: "Online"
      payload_not_available: "Offline"
      action_topic: "corridoio/stat/things/thermostat/properties/action"
      action_template: "{{value}}"
      temperature_command_topic: "corridoio/cmnd/things/thermostat/properties/targetTemperature"
      temperature_state_topic: "corridoio/stat/things/thermostat/properties/targetTemperature"
      temperature_state_template: "{{value}}"
      current_temperature_topic: "corridoio/stat/things/thermostat/properties/temperature"
      current_temperature_template: "{{value}}"
      mode_command_topic: "corridoio/cmnd/things/thermostat/properties/mode"
      mode_state_topic: "corridoio/stat/things/thermostat/properties/systemMode"
      mode_state_template: "{{value}}"
      fan_mode_command_topic: "corridoio/cmnd/things/thermostat/properties/fanMode"
      fan_mode_state_topic: "corridoio/stat/things/thermostat/properties/fanMode"
      fan_mode_state_template: "{{value}}"
      hold_command_topic: "corridoio/cmnd/things/thermostat/properties/holdState"
      hold_state_topic: "corridoio/stat/things/thermostat/properties/holdState"
      hold_state_template: "{{value}}"
      hold_modes: [ "scheduler", "manual","eco" ]
      payload_on: "ON"
      payload_off: "OFF"
      modes: [ "heat", "cool", "fan_only", "off" ]
      min_temp: 10
      max_temp: 35
      temp_step: 1
      precision: 0.5

Any help or suggestion will be VERY appreciated.

Breaking Change for MQTT

Hold and away are replaced with preset_mode

@tmjpugh
Thanks for your reply.
Do I just have to substitute the word “hold” with the word “preset_mode” in my config.yaml for it to work?

I will translate

hold_command_topic: "corridoio/cmnd/things/thermostat/properties/holdState"
hold_state_topic: "corridoio/stat/things/thermostat/properties/holdState"
hold_state_template: "{{value}}"
hold_modes: [ "scheduler", "manual","eco" ]

into this:

preset_mode_command_topic: "salotto/cmnd/things/thermostat/properties/holdState"
preset_mode_state_topic: "salotto/stat/things/thermostat/properties/holdState"
preset_mode_command_template: "{{value}}"
preset_mode_value_template: [ "scheduler", "manual","eco" ]

What about the current hold_modes: [ "scheduler", "manual", "eco"] ?
They should be the possible values for the dropdown list of modes, is it the preset_mode_value_template assumption I made correct?

Thanks again for your help

looks like that should just be:

preset_modes:
1 Like

Thanks, with last addition of preset.modes instead of preset_mode_value_template everything went back on track!