I’m going to reiterate again a little louder for those in the back:
It is bad design if a change can be made inadvertently to something as important as the heat just by scrolling past the controls. If you find yourself using workarounds such as hiding the controls on a sub view, or custom integrations, it is an admission that something is not quite right.
And before someone brings the tried and true excuse of open source I’m going to put it out there now, Home Assistant has in my opinion long crossed the line from a tinker’s project into a paid product. 50$ a year to unlock full functionality means higher expectations.
I just gave an example. It’s not always HA’s fault, but many times it’s user’s one…
But, to go back to the problem: if i install and test a card that it’s not usefull to me (or dangerous…) i just delete it and use another one. It’s just not worthed to complain since nothing from user’s requests will be corrected or updated in a short time (if at all), as i see from history (among the worst example being changes in automations regarding folders organization).
As thermostat goes i personally i hate sliders, circles…. It’s too hard to precisely set a temperature. I only use + and - signs. With that you can accurately set desired temperature. And, it never happened to me yet that i did anything i didn’t want to (i use simple thermostat card for my climates).
I’ll agree that problems that should be resolved first, long before new functionality and features are even considered, are often ignored. Anyone else notice the annoying bug where you have to mash the back button on sub views just to get it to respond half the time? Yea that one drives me crazy. But at least that one is only annoying.
But it’s unacceptable for a change to be made so easily and by accident to something as important as the heat using the default, built in thermostat card. This is one I will not just shrug off and ignore. I will make noise.