Changing desired/set temp when unit is off causes error

[ptruman]

I've noticed some use cases where family are wanting to set the temp before selecting the mode (i.e. heat/cool).
This is because the climate UI has the dial/buttons above the mode - so "not the integrations" fault.

If a unit is off, and someone tries to set temp, you get this:

Failed to call service climate/set_temperature. cannot access local variable 'min_temp' where it is not associated with a value_

Is it possible to store the last known set temp, and allow it to amended and "sent" to the unit when a mode is selected?
(using V1.1.8 of the integration via HACS)

[GastonHP]

I have the same issue!

[donkawechico]

Same here!

[ohshazbot]

So this is not the workflow I have, but I understand where y'all are coming from. One question I have is around handling for minimum temp, as some temperatures can only be achieved in certain modes. Do you think it's better to fail the operation entirely (so you get the notification about it) or for it to just round up the closest viable temperature.

Specific example of this (possibly the only one) is you cannot set temp below 18C unless you're heating, so if you plug it to 17C and then turn on cooling, would you rather get notified or have it just set the temp to 18C without any fanfare?