@buckshome, Here’s what I see in developer tools > states:
Mine has the same behavior as yours (I think), so in a card I have both entities, like this:
If the mode is set to Heat, changing the Cooling Target Temp doesn’t have an effect. And vice versa, if the mode is set to Cool, changing the Heating Target Temp doesn’t do anything. Actually, changing either does update the value, but doesn’t have an effect on the “opposite” operation mode.
I’d sure love to see someone’s config that has a more streamlined card, either a standard card or state-card-tile or state-card-custom-ui or something. Anything more like the controls on an actual thermostat.
Fwiw, I’m running hass.io on a pi3 and am up to the latest version. It’s been working for me like this for months without having to change any type or ID. What may be complicating things for the OP and others up in this thread (possibly) is that this thermostat has several variations and all have the same CT-100 model number. There was/is one sold by Amazon (like mine) and one by Lowe’s a year or more ago and I think two or three others. They all had variations in their type and ID. I believe the same happened for the CT-101.