Minimum Setpoint Deadband in the Thermostat dialog and card

[dbolger]

Hey there - I've been working on implementing the minimum setpoint deadband value into the Matter integration recently. While messing with the UI to test it, I think it would be interesting to integrate this value to show (or prevent) the user from ever entering a value within the deadband.

For example (pardon my mockup), when a user selects either the heat or the cool target temperature, a dynamic visual between the two temperature ranges will appear to show the user where the deadband lives.

On my thermostat, my minimum setpoint deadband is 3°F, meaning if I try to set the target cool temperature on the right to 73°F or 74°F, I will get an error. It's basically a 'dead zone', meaning these two target temperatures have to have 3°F of range between them.

[dbolger]

After some more thinking, the deadband would probably be the inverse of the image, where there's a 3°F buffer (or whatever the thermostat's minimum is) on each side of the temperature slider.

When the heat temperature is selected:

Cool temperature:

[karwosts]

I guess before the frontend could do this, there would need to be an attribute available in the climate entity that describes the properties of the deadband? I don't believe there is such a thing that the frontend could read. Have you considered raising this in home-assistant/architecture? ?

[dbolger]

I haven't raised it in the architecture side, but I have been playing with the implementation locally. I imagine it would be an optional attribute.

[dbolger]

I updated the description on my follow up mock-ups.