diff --git a/source/_integrations/knx.markdown b/source/_integrations/knx.markdown index af81920e408..fe56c434c70 100644 --- a/source/_integrations/knx.markdown +++ b/source/_integrations/knx.markdown @@ -164,7 +164,7 @@ The `knx.telegram` trigger can be used to trigger automations on incoming or out
-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 DPT (`type`) to decode the payload as it always relies on project data.
@@ -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