Why not an option to use TRV temp sensor for those without external temp sensor

[radurambet]

First I have to say that the integration si GREAT , and there is one thing that NO OTHER integration coud do : Make your TRV Google Assistant 100% compatible.

So I am using this integration for the sole purpose of making my TRV's available to Google Home / Nest Displays.

I am using internal scheduling , everyting is perfect , in fact I am using Google Home for fine adjustments when I need something different than what TRV scheduling can provide.

The problem is that my TRV do not expose the internal temperature as an entity. It is in the climate entity but not a separate selectable entity (maybe I can hack that) . My suggestuion would be to allow usage of internal TRV temp sensor as there is a very good use case : Google Assistant/Home where this integration alone is just great. The external temp sensors would be a great addition but for an entire house is just too expensive and for some rooms (basement for example) makes no sense to invest in such a fine tuning temp solution.

Is it this feature available and missed by me ?

Still for making my TRV's Google compliant I can only have nice words about this integration.

[rhlgithubrhl]

I have a related question to that of @radurambet . I am using several remote Zigbee thermometers to get a better room temperature value, but what happens if any of these thermometers fail? Does the integration automatically revert to the local TRV temperature sensor? I am not clear of how this is accommodated in this integration. I like the high-level of control provided when using smart TRVs and HA but I must have a simple reversion mode. Again, this may already be a feature but I have not found any documentation specifically about it. Does anyone know how this situation is dealt with? Thanks.

[radurambet]

I have managed to find a way to make it work :

I have created a sensor template entity that reads the TRV temperature. So I have an independednt Temperature entity (not climate).
This entity I am using as a source temperature for Better Thermostat.

It is important though to set BT to use Target Temperature ant NOT offset as that second option messes around with temperature reading from the sensor.

You will ask what this is good for ? Well:

• It keeps Google Assistant perfect integration
• It uses heating protection of BT that manipulates target temperature way below the existing one and doing so forces TRV to close more rapidly than its existing PID alorithm (that is painfully slow and overshoots target temperature)
• Also does the same for heating by overshooting target temp for brief periods of time and then it calibrates automatically.

I could say that in this way even without external sensor this plugin makes any TRV a WAY BETTER thermostat.

I hope it helps others:

sensor:
  - platform: template
    sensors:
      moes_real_temp:
        friendly_name: "Moes TRV Real Temp"
        unit_of_measurement: "°C"
        device_class: "temperature"
        value_template: "{{ state_attr('climate.moes_trv', 'current_temperature') }}"

[wtom]

I just wanted to add, that I also played around with a sensor that was a mix of internal and external sensor.

For example: 30% internal temperature and 70% external.

What TRVs do you have and what are your settings?

[wtom]

@radurambet do you have some charts, how well it works? I think even the BT history chart is enough, because it shows when it's heating, target and current temperature.

[TheOpsMgr]

When you say "making my TRV's available to Google Home / Nest Displays." what exactly do you mean wrt to Nest?

I have a Nest 3rd gen thermostat and I'm not really clear on how best to use HA + BT + TRV + Nest together.