Add data point type option to knx.telegram trigger (#32782)

* Add data point type option to `knx.telegram` trigger

* tiny tweaks

---------

Co-authored-by: c0ffeeca7 <38767475+c0ffeeca7@users.noreply.github.com>
This commit is contained in:
Matthias Alphart 2024-05-22 00:06:48 +02:00 committed by GitHub
parent ef93f30767
commit 645543fce5
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194

View File

@ -164,7 +164,7 @@ The `knx.telegram` trigger can be used to trigger automations on incoming or out
<div class='note'>
This trigger is also provided as a device trigger by the `KNX Interface` device. It supports setting the options in the automation builder UI.
This trigger is also provided as a device trigger by the `KNX Interface` device. It supports setting the options in the automation builder UI, but doesn't support setting a specific <abbr title="data point type">DPT</abbr> (`type`) to decode the payload as it always relies on project data.
</div>
@ -173,6 +173,10 @@ destination:
description: A group address or a list of group addresses the trigger should listen on. If not set, or an empty list, the trigger will listen on all group addresses.
type: [string, list]
required: false
type:
description: If set, the payload will be decoded as given DPT in the trigger data. When not set, the DPT is sourced from project data. KNX sensor types are valid values [KNX Sensor](#sensor) (e.g., "2byte_float" or "percent").
type: [string, integer]
required: false
group_value_write:
description: If set to `false`, the trigger will not fire on GroupValueWrite telegrams.
type: boolean