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-19 15:26:59 +00:00
Code Issues Packages Projects Releases Wiki Activity

Fix KNX telegram trigger data (#34333)

Browse Source 
* Fix KNX telegram trigger data

and add example use in template

* escape template
This commit is contained in:
Matthias Alphart 2024-08-19 08:12:02 +02:00 committed by GitHub
parent 42a512a7dc
commit 9ffdf8c776
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
1 changed files with 17 additions and 13 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

30
source/_integrations/knx.markdown
View File

@ -213,12 +213,12 @@ In addition to the [standard automation trigger data](/docs/automation/templatin
- `trigger.dpt_sub` Destination group address sub datapoint type number - `trigger.dpt_sub` Destination group address sub datapoint type number
- `trigger.dpt_name` DPT value type name - see Sensor value types - `trigger.dpt_name` DPT value type name - see Sensor value types
- `trigger.payload` Raw telegram payload. DPT 1, 2, and 3 yield integers 0..255; other DPT yield lists of integers 0..255 - `trigger.payload` Raw telegram payload. DPT 1, 2, and 3 yield integers 0..255; other DPT yield lists of integers 0..255
- `telegram.source` Source individual address - `trigger.source` Source individual address
- `telegram.source_name` Source name - `trigger.source_name` Source name
- `telegram.telegramtype` APCI type of telegram - `trigger.telegramtype` APCI type of telegram
- `telegram.timestamp` Timestamp - `trigger.timestamp` Timestamp
- `telegram.unit` Unit according to group address DPT - `trigger.unit` Unit according to group address DPT
- `telegram.value` Decoded telegram payload according to DPT - `trigger.value` Decoded telegram payload according to DPT
| Template variable | Type | Project data required | | Template variable | Type | Project data required |
|----------------------------|-----------------------------|-----------------------| |----------------------------|-----------------------------|-----------------------|
@ -229,12 +229,12 @@ In addition to the [standard automation trigger data](/docs/automation/templatin
| `trigger.dpt_sub` | integer | yes | | `trigger.dpt_sub` | integer | yes |
| `trigger.dpt_name` | string | yes | | `trigger.dpt_name` | string | yes |
| `trigger.payload` | integer or list of integers | no | | `trigger.payload` | integer or list of integers | no |
| `telegram.source` | string | no | | `trigger.source` | string | no |
| `telegram.source_name` | string | yes | | `trigger.source_name` | string | yes |
| `telegram.telegramtype` | string | no | | `trigger.telegramtype` | string | no |
| `telegram.timestamp` | timestamp | no | | `trigger.timestamp` | timestamp | no |
| `telegram.unit` | string | yes | | `trigger.unit` | string | yes |
| `telegram.value` | any | yes | | `trigger.value` | any | yes |
For values that require project data: if the information was not found, or if no project file was provided, data will be set to `null`. For values that require project data: if the information was not found, or if no project file was provided, data will be set to `null`.
@ -242,6 +242,8 @@ For values that require project data: if the information was not found, or if no
Example automation configuration Example automation configuration
{% raw %}
```yaml ```yaml
- alias: Single group address trigger - alias: Single group address trigger
description: '' description: ''
@ -250,11 +252,13 @@ Example automation configuration
destination: 1/2/3 destination: 1/2/3
group_value_read: false group_value_read: false
outgoing: false outgoing: false
condition: [] condition: "{{ trigger.value == 0 }}"
action: [] action: []
mode: single mode: single
``` ```
{% endraw %}
Example trigger data Example trigger data
```yaml ```yaml