I’ve been longing for an easier thermostat preset/mode setup depending on house conditions, hence proposing some improvements to the native thermostat shipped with HA.
Wished solution:
Individual thermostats being automatically managed and set by a centralized «house» mode, without the need of numerous automations and template inputs.
Action: So when centralized setting for building modes is set to Away, all associated presets are triggered.
I am aware of custom community integrations, like Better Thermostat and Versatile Thermostat, but those are adding quite a bit of unnecessary complexity to a solution that could preferably been embedded from the core.
You think your house is the right setup, but others have other house setups.
Some might have abither building, like a guest house, workshop or office, which also needs it separate away setting.
And the away mode should be able to handle away from the building only or away from the entire premise.
Some have extra floors and they would like to control them as a separate entity, like your house, but then still have a whole house that have controls the floors.
There are probably many more and each setup adds to the complexity of the code.
It will be a huge work to maintain and probably never include all the setups.
In general features that just is because an user is “lazy” will result in a lot of work for the code maintainers and it might also limit the flexibility of HA for users.
Thanks for taking the time to reply. Actually I think the cases you’re describing would work perfectly fine with the solution I’m proposing, ex. by adding more modes and the flexibility of having modes defined per area or per building/facility. Hence I find this to be not a contradiction but rather a simple tweak and enrichment.
I still think this would be very helpful to a large extent of HA users / people.
You see it as simple now, but you said your own setup required lots of helpers and automations.
This extra layer and features and differences require even more.
The code maintainers need to handle all those factors in the same code and that requires a lot of complex code to select the right setup whenever there is a fork between the setups.