[Feature Request] Support Climate Sensor Attributes

[fschwarz86]

Hi there,

I'm using Homematic(IP) Local to connect my HomematicIP setup with HA. It exposes my heating controls as a climate sensor to HA and uses attributes for temperature, humidity etc:

hvac_modes:
  - auto
  - heat
  - 'off'
min_temp: 5
max_temp: 30.5
target_temp_step: 0.5
preset_modes:
  - boost
  - none
  - week_program_1
  - week_program_2
  - week_program_3
  - week_program_4
  - week_program_5
  - week_program_6
current_temperature: 22.8
temperature: 22.5
current_humidity: 42
hvac_action: idle
preset_mode: week_program_1
interface_id: ccu-HmIP-RF
address: 000CxxxxxDC437:1
model: HmIP-BWTH
entity_type: custom
value_state: valid
friendly_name: Fußbodenheizung Wohnzimmer
supported_features: 17

Unfortunately, this prevents me from setting up a Thermal Comfort device, as it requires a tempreature and humidity sensor. Theoretically, I could create a sensor from the attribute, however doing this 10 times is a bit cumbersome, hence my feature request.

Thanks for your time and consideration, Florian

[Torgrima]

Is it possible to use templating as an input parameter for the temperature in thermal_comfor?

{{ state_attr('climate.rebekka_thermostat', 'current_temperature') }}

[higbyk]

Not currently, but you can create a template sensor and use that entity.

[fschwarz86]

That would work, but that would require me to create ~10 template sensors and I was hoping to avoid that.

[bj00rn]

Facing this use case as well.

I see two possible approaches here

• Option 1: Add configuration option to provide an optional state attribute configuration to use when getting data from entity and use value from attribute in listener instead of state.
• Option 2: Add configuration to specify a template, and use async_track_template_result