From 79a13f6d45e76b694f41a3f5e6104fb4fb900567 Mon Sep 17 00:00:00 2001 From: Matthias Merz Date: Fri, 8 Jan 2021 15:20:22 +0100 Subject: [PATCH] use correct attribute for valve position (#16118) "valve" reflects the VALVE_STATE, e.g. "ADAPTION_DONE" etc. --- source/_integrations/homematic.markdown | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/source/_integrations/homematic.markdown b/source/_integrations/homematic.markdown index b5768e51c32..57d428ac8f2 100644 --- a/source/_integrations/homematic.markdown +++ b/source/_integrations/homematic.markdown @@ -203,14 +203,14 @@ This does *not* affect the entities in Home Assistant. They all use their own co ### Reading attributes of entities -Most devices have, besides their state, additional attributes like their battery state or valve position. These can be accessed using templates in automations, or even as their own entities using the [template sensor](/integrations/template) component. Here's an example of a template sensor that exposes the valve state of a thermostat. +Most devices have, besides their state, additional attributes like their battery state or valve position. These can be accessed using templates in automations, or even as their own entities using the [template sensor](/integrations/template) component. Here's an example of a template sensor that exposes the valve position of a thermostat. ```yaml sensor: - platform: template sensors: bedroom_valve: - value_template: "{% raw %}{{ state_attr('climate.leq123456', 'valve') }}{% endraw %}" + value_template: "{% raw %}{{ state_attr('climate.leq123456', 'level') }}{% endraw %}" entity_id: climate.leq123456 friendly_name: 'Bedroom valve' ```