Allow climate.entity as temperature sensor input

[LinuxfarmerHH]

What is the feature?

After selection of the TRV itself, we can select a temperature sensor from the pulldown list. TRV's like Tuya 601 or MOES 368 do offer them as climate entity, like this.

"entities": [ { "entity_id": "climate.stu_moes_thermostat", "name": "_TZE200_cpmgn2cf TS0601"

It's there, by clicking the entity we can look at the measured temperature of the device. But Better Thermostate does not allow to choose climate. entities for the temp.

Additional Information

Hassio 11.1 on Raspi5, with Better Thermostate 1.3.0

[tk4arts]

That would be really nice. Or even better to make the external temperature sensor field optional. I have a smart thermostat in a room that I want to control using a better thermostat, but I do not have a separate temperature sensor in this room.

How much effort would it be to implement the temperature sensor as optional input?

Thanks for the highly appreciated feedback!

P.S. Amazing Integration!!!

[keksinc]

Hi, I figured out a workaround using the template integration, which is able to take an attribute from an existing entity and create a dedicated sensor from it. Add the following entry to your configuratin.yaml file:

template:
  - sensor:
      - name: "Living room HVAC temperature"
        unique_id: tmplHVACLivingTemperature
        unit_of_measurement: "°C"
        state_class: "measurement"
        device_class: "temperature"
        state: >
          {{ state_attr("climate.hvac_living","current_temperature") }}

make sure hvac_living is the name of your climate entity. Adjust name and uniqueid as you see fit. Afterwards you can use that sensor with BT, it will always follow the temperature reading from the TRV. Cheers..

[tirol3]

i am waiting this Moes BHT-006. i cant select temprature my thermostat moes 006. and i am selecting extra thermostat . extra thermostat getting target to start ha shows start heating but thermostat waiting internal temprature.