From c57406d343501eed9e23ea00f48ce1b23dfe7b69 Mon Sep 17 00:00:00 2001 From: ProfDrYoMan Date: Sun, 16 Jan 2022 18:02:48 +0100 Subject: [PATCH] Update HMIP-DLD documentation in homematic (#20671) --- source/_integrations/homematic.markdown | 5 +---- 1 file changed, 1 insertion(+), 4 deletions(-) diff --git a/source/_integrations/homematic.markdown b/source/_integrations/homematic.markdown index 13aae4ca482..7894d656670 100644 --- a/source/_integrations/homematic.markdown +++ b/source/_integrations/homematic.markdown @@ -450,7 +450,7 @@ lock: - platform: template name: Basedoor unique_id: basedoor - value_template: "{{ state_attr('homematic.ccu2', 'base_lock_status') }}" + value_template: "{{ is_state('sensor.lock_status', 'locked') }}" lock: service: homematic.set_device_value data: @@ -469,9 +469,6 @@ lock: {% endraw %} -To get the current value of the current lock status, you have to create a system variable (in the example above it is `base_lock_status`) and create a program on CCU, which updates the variable with every change of the Lock level to `true` for locked and `false` for unlocked. - - #### Detecting lost connections When the connection to your Homematic CCU or Homegear is lost, Home Assistant will stop getting updates from devices. This may happen after rebooting the CCU for example. Due to the nature of the communication protocol this cannot be handled automatically, so you must call *homematic.reconnect* in this case. That's why it is usually a good idea to check if your Homematic integrations are still updated properly, in order to detect connection losses. This can be done in several ways through an automation: