Closed WallK closed 1 week ago
You can use scheduler to trigger any action. I think you are referring to the built-in action ‘heat’ which both sets the mode to heat and provides a setpoint. You can extend the actions which are available in the card using the yaml configuration, see https://github.com/nielsfaber/scheduler-card?tab=readme-ov-file#customize for instructions.
Yes, I was talking about default set of available actions, there is no "Set temperature" there
Thank you for pointing out the config options, I will play with it
I have investigated other devices in my house and found out that my bathroom floor thermostat will turn on if you change the temperature on it without specifying the mode of operation So maybe having "Change temperature" built-in action is a bad idea
I deliberately called the built-in action heat, since it will put your thermostat to heat (similarly there is an action cool). In the early days, scheduler would only change the setpoint, and I got lots of complaints from users that their thermostats didn't respond to the action (only setpoint was changed, the thermostat didn't decide to warm up). It's very hard to make a one-fits-all design, the default actions are meant to serve most users, users who have specific needs will have to add their own configurations.
I understand! The current implementation is very obvious as in it does what it says and that's the best solution for most users Thanks!
Is it possible to change temperature of the climate device without changing it's current mode?
Checklist
Proposal
As a user, I want to change the set temperature of my AC without changing it's state (mode of operation), so I can keep it on, off or in different mode using other automations
Additional info
When I create a schedule or a scheme -- I can't select temperature without choosing the mode of operation This forces AC to turn on on the temperature change, for example Calling climate.set_temperature with only temperature data does what I expect