The problem I’m running into is that although I can pick any single one of them to change a state of fan (Auto/On) or change the mode (Heating/Cooling/Auto/Off) the thermostat only accepts temperature setpoint changes when they are coming from the proper instance.
For example if I change operation mode to heat, only changes done when using climate.thermostat_heating will be accepted. Similarly if I change the operating mode to cool (doesn’t matter on which instance) to change the actual cooling setpoint I have to use climate.thermostat_cooling instance. Any temperature changes done using any of the remaining instances are ignored.
What am I doing wrong? Is there a way to have it handled nicely in Lovelace so my users only see one thermostat instance that always work?
I have a CT32 out in my garage. Same deal with the multiple entities. I only use it for heat so I’m able to use the heating climate control and hide all the extraneous climate entities and sensors. On the surface it appears to work well, however, the thermostat randomly sets the temp to either 62 or 70 degrees after a while. I think it might have something to do with the multiple entities. Either that or the thermostat is pretty buggy.
Watching to see what kind of replies you get here. I still have 3 weeks to return it if I can’t get it to stop acting up.
In my case the thermostats (I have 5 of them total) are dead solid, no issues with them working, only the issue with multiple entities and trouble changing setpoints.
Did you find a solution? I’m adding a new CT100 and am having the same issue of showing two thermostats, one for “Cooling” mode and one for “Heating” mode.
