The recent improvements (Dec-23) to the thermostat card are great and I’d love to use it, but they are no use for anyone who’s heating set-up uses external temperature sensors, and I believe there are plenty of us.
My TRVs (Danfoss in my case) completely ignore their own temperature sensor, so it makes no sense to use the standard thermostat card, which only displays this value (and the value is typically 2-3c higher).
The options out there for external sensors are very limited. Because I much prefer a round dial control I’m making do with Dark Thermostat Card, which was last updated in 2021. The only other option I’m aware of is Simple Thermostat, which allows sensors to be added.
This issue was originally raised in 2021 and I raised again today… On both occasions it was closed because “it’s a back end issue”, which is unfortunate because this requirement/gap definitely has merit and should go somewhere. (AS an end user, all I can do is express the desired functionality and to point out how the two cards mentioned above have implemented it).
I’m using Danfoss TRVs too and experiencing the same problem.
As far as I understand the generic thermostat allows you to create a thermostat using temperature sensors and switches. This is not what I want : I want to be able to set the target temperatures on my TRV and rely on its internal regulation.
So basically, currently the solutions to displaying the external temperature in a dashboard seem to be :
create a climate template that remaps the original climate entity (brittle and lots of work) and use the official thermostat card
use a third-party card
I second @Wickedy123 on the idea that just being able to override the sensor that displays the current temperature would a nice addition to this card, and I don’t really understand @frenck 's comment about back/front responsabilities.
On a slightly related topic: Danfoss thermostats have two modes for changing the setpoint. The ‘regular’ one causes a massive burst of heat but there is a second method, the so-called ‘scheduled’ change setpoint that doesn’t do this.
I added this additional configuration to my zigbee2mqtt configuration.yaml file to change this default: