KNXnet/IP
 
Connection String Options
| Name | Type | Default Value | Required | Description | 
| Name | KNXNet/IP | |||
| Code | 
 | |||
| Maven Dependency | <dependency> <groupId>org.apache.plc4x</groupId> <artifactId>plc4j-driver-knxnetip</artifactId> <version>0.12.0</version> </dependency> | |||
| Default Transport | 
 | |||
| Supported Transports | 
 | |||
| Config options: | ||||
| 
 | STRING | Path to the  | ||
| 
 | STRING | Optional password needed to read the knxproj file. | ||
| 
 | INT | 3 | KNX Addresses can be encoded in multiple ways. Which encoding is used, is too not provided by the protocol itself so it has to be provided externally: 
 The default is 3 levels. If the  | |
| 
 | STRING | LINK_LAYER | Type of connection used to communicate. Possible values are: 
 | |
| Transport config options: | ||||
| 
 udp | ||||
| 
 | INT | -1 | Some connections require a UDP listener to listen on a fixed port. Use this configuration option in order to define the port number of the local port. | |
| 
 pcap | ||||
| 
 | FLOAT | 1.0 | Numeric value for changing the replay speed: - 1 = Normal speed (default) - 0 = Maximum speed - 0.5 = Half speed - 2 = Double speed | |
| 
 | BOOLEAN | false | Should the replay start at the beginning of the file as soon as the end is reached? - true = Automatically start again - false = Stop at the end (default) | |
| 
 | STRING | Filter expression used to filter out unwanted packets from the replay. | ||
| 
 | BOOLEAN | false | Should VLan packets be automatically unpacked? | |
| 
 | INT | -1 | When provided, filters all packets to let only packets matching this ethernet protocol-id pass. | |
| 
 raw | ||||
| 
 | BOOLEAN | If set to true, the transport will automatically resolve the MAC address for a given IP address (Allows connecting to a raw-socket device using the devices host-name or ip-address). | ||
| 
 | BOOLEAN | false | Should VLan packets be automatically unpacked? | |
| 
 | INT | -1 | When provided, filters all packets to let only packets matching this ethernet protocol-id pass. | |
Individual Resource Address Format
KNX Addresses usually have one of the following structures:
- 
3-level Address: {main-group(0-15)}/{middle-group(0-15)}/{sub-group(0-255)}
- 
2-level Address: {main-group(0-15)}/{sub-group(0-4095)}
- 
1-level Address: {sub-group(0-65535)}
Depending on the group-address-type configured in the connection string or defined in the knxproj-file configured by the knxproj-file-path connection string parameter, the corresponding address pattern has to be used.
However, when subscribing for events, each segment allows using of the wildcard character *.
If the addresses used in the KNX installation are structured, this way it is possible to, for example (depending on the scheme used):
- 
Collect all information for a given level of your building: 1//
- 
Collect all information for a given room: 2/4/*
- 
Collect all information about heating in all rooms: //50
| Don’t use wildcards when explicitly reading or writing data, this is only supported when subscribing to events. |