jeans/home-assistant.io
jeans/home-assistant.io
1
0
Fork 0
mirror of https://github.com/home-assistant/home-assistant.io.git synced 2025-07-15 05:16:49 +00:00
Code Issues Packages Projects Releases Wiki Activity

Update HMIP-DLD documentation in homematic (#20671)

Browse Source
This commit is contained in:
ProfDrYoMan 2022-01-16 18:02:48 +01:00 committed by GitHub
parent 992613aa97
commit c57406d343
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 1 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
source/_integrations/homematic.markdown
View File

@ -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: