WTH - Why are climate devices now limited to 7-30c range

A change a couple of months ago added some validation to the temperature on climate devices and has set an arbitrary range of 7-30c. This is a problem for me as I have several heaters that I use in frost protection mode, with a target of 3c. The range seems arbitrary and far too narrow, especially as it doesn’t seem configurable.

It looks like this has been resolved for the next release

2 Likes

That’s good to know - fingers crossed that also fixes the zigbee thermostats as well as the generic ones.

It’s not limiting, it’s a default which has been around since ClimateEntity was created. But now there is a validation so integrations needs to provide a proper range for it to work.
For example with generic_thermostat you could configure the thresholds even before, but only in yaml.

I’m not sure what you mean about it not being limiting - I used to be able to set those climate entities to 3c and they worked as expected; after an update a couple of months ago I can’t do that either via the UI or automation.