Yeah, like you said, it is not necessary, but it is a little jarring when I go to change the slider and the number that pops up in the bubble is like 5 degrees different than the actual temperature is, also, I like to think of the slider as a direct link to the hardware, so without it being tied directly to the change, it just feels broken. I just like everything to be tied on all sides to all changes so there is never a question as to what the temperature is.
Also, in future, who knows if they may change the slider so that it always shows the temperature instead of only when you tap on it, so this way you are future proofing your layout
One more thing, I’m not sure if you noticed this or not with the CT100 (but from what I gather this applies to all Z-Wave Thermostats), you can change the temperature manually on the thermostat even if the Operating Mode is set to Auto, but Z-Wave can not, and therefore Home Assistant can’t either, so if you have your Operating Mode set to Auto and you move the slider to change the temperature, the slider will reflect the new temperature, but the thermostat will not actually change temperature, so the Target Temperature will still show the old value.
Currently in my slider automation, not only am I making sure the new value is not the same as the thermostats temperature attribute, but I am also checking if the Operating Mode is set to Auto, and if it is, I set the slider back to the old value. So visually, you will move the slider, and it will just snap back to the where it was before. This lets me know that I have to change the operating mode to either Heat or Cool before I can use the slider to change the temperature. It is a little annoying though, because if it is in Auto mode, I have to change it to Heat or Cool, then change the temperature, and finally change it back to Auto.
A better workaround for me to avoid having to do 3 steps in order to change the temperature in Auto mode, is that I am going to remove the “Auto” option from the Operating Mode input_select and then programmatically create my own auto mode instead of using the Auto mode of the thermostat. I will do this by checking the current temperature, and if the target temperature I am setting it to is higher than the current temperature, I am going to make it first set the Operating Mode to Heat, and then change the temperature. And if the target temperature I am setting is lower than the current temperature, i am going to make it change the Operating Mode to Cool and then change the temperature.
Then I will have an additional automation monitoring the actual temperature, and if it goes above the target temperature and the current Operating Mode is Heat, it will change it to Cool, and if the actual temperature drops below the target temperature and the current Operating Mode is Cool, I will have it change to Heat.
It is a bit more work, basically recreating an entire Auto mode, but again, I like to be thorough and make everything work completely with each other in all scenarios