Thermostat temperature range - intended setpoint value rejected as invalid

Hi,

a few months back, I moved all my YAML automations to GUI-style automations, which went well for the most part.
However, it appears that some of my heating automations broke.

I have an automation that turns down all the thermostats to their minimum value when I open a window.
In the GUI’s YAML editor, that specific part of the automation looks like this:

data:
  temperature: 4
action: climate.set_temperature
target:
  entity_id:
    - climate.danfoss_office
    - climate.danfoss_bedroom
    - climate.danfoss_bathroom
    - climate.danfoss_kitchen

When I try to run this action, I get an error from the GUI saying “Provided temperature 4.0 is not valid. Accepted range is 7 to 35”.
So far so good - 7 seems to be some kind of internal default as the thermostats can be set as low as 4.0°C.
So I have overridden the default with a customize_glob setting:

"climate.danfoss*":
  min_temp: 4.0
  [...]

which looks like it worked:

I’m still getting the same error when running the action from the GUI automation editor.
What did I miss?

Sebastian

1 Like

me too. 2024.8+2024.9.

Same issue for me. Have wifi floor termostats using 0-100 to adjust effect regulators.
Strange decision to set a hard limit on 5-35 for all thermostat types and ignoring min_temp and max_temp options if this is not a bug

Also hitting this issue

The min temp default value is 7.
Generic Thermostat - Home Assistant (home-assistant.io)

Sadly the GUI integration does not include all parameters which means you either have to settle with 7-35 degree range or set it up in yaml