28/12/2025, 11:28:07
dans home assistant tu as ceci:
Events [/url]
[size=1]YAML
[/size]
Events [/url]
Tip
For automation triggers, it is recommended to use the knx.telegram trigger instead of
.
For automation triggers, it is recommended to use the knx.telegram trigger instead of
Code :
knx_eventCode :
knx:
event:
- address:
- "0/1/*"
- address:
- "1/2/*"
- "1/3/2-4"
type: "2byte_unsigned"
- address:
- "3/4/5"
type: "2byte_float"[size=1]YAML
[/size]
[size=1]Configuration Variables
Looking for your configuration file?
address list | string [size=1]Required[/size]
Defines a list of patterns for matching KNX group addresses. Telegrams with destination addresses matching one of the patterns are sent to the Home Assistant event bus as
[/size]
.
[size=1]type string | integer (Optional)[url=https://www.home-assistant.io/integrations/knx/#type]
Telegram payloads in
[/size]
events will be decoded using the configured type (DPT) for the addresses in the same block. The decoded value will be written to the event data
key. If not configured the
key will be
- the
key will still hold the raw payload (use this for DPT 1, 2, 3). All sensor types are valid types - see KNX Sensor (e.g., “2byte_float” or “1byte_signed”).
Looking for your configuration file?
address list | string [size=1]Required[/size]
Defines a list of patterns for matching KNX group addresses. Telegrams with destination addresses matching one of the patterns are sent to the Home Assistant event bus as
[/size]
Code :
knx_event[size=1]type string | integer (Optional)[url=https://www.home-assistant.io/integrations/knx/#type]
Telegram payloads in
[/size]
Code :
knx_eventCode :
valueCode :
valueCode :
NoneCode :
dataEvery telegram that matches an address pattern with its destination field will be announced on the event bus as a
Code :
knx_event event containing data attributes
- contains the raw payload data (e.g., 1 or “[12, 55]”).Code :
data
- the KNX group address the telegram is sent to as string (e.g., “1/2/3”).Code :
destination
- the direction of the telegram as string (“Incoming” / “Outgoing”).Code :
direction
- the KNX individual address of the sender as string (e.g., “1.2.3”).Code :
source
- the APCI service of the telegram. “GroupValueWrite”, “GroupValueRead” or “GroupValueResponse” generate a knx_event.Code :
telegramtype
- contains the decoded payload value ifCode :
value
is configured for the address. Will beCode :type
for “GroupValueRead” telegrams.Code :None

