Marking requirements are defined in the corresponding product standards. In addition to these general requirements and as the KNX Trademark alone does not clearly identify the KNX transmission medium, the configuration mode, support for security and IoT, KNX specific labelling is needed.
Basic labelling requirements
- Each device shall be clearly identifiable as regards the physical medium and the implemented configuration mode.
- This basic requirement is certification relevant, i.e. verified and fixed in the test report by the accredited test lab.
Medium label
| KNX Medium | Label |
| TP1 | TP |
| PL110 | PL |
| RF | For labelling requirements for KNX RF devices, consult Volume 3/2/5. |
| IP | IP |
Configuration label
| KNX Configuration mode | Label |
| S-Mode | S |
| E-Controller | EC |
| E-LTE | EE |
| E-PB | EP |
Security label
| KNX Security label | Label |
| KNXnet/IP Secure | X (letter X) |
| KNX Data Security | X (letter X) |
| No security supported | no label required |
The extent of security that is offered by the product bearing the label shall be stated in the product data sheet.
IoT label
| KNX IoT Label | Label |
| KNXIoT 3rd Party API | IoT1 |
| KNXIoT Point API | IoT2 |
In the case where both interfaces are implemented in one device, naturally both labels can be used on the product.
The IoT labels already imply support of Security (by specification), hence an additional KNX IoT Secure label is not defined, neither do KNX IoT devices need to be additionally labelled with the X label.
Important notes with regard to labelling
- The place and the representation/design of the label on the product (front, back or sideways) may be decided by the manufacturer but may not be in conflict with the relevant trademark design rules, KNX trademark guidelines and/or product standards. As a rule of thumb, the labels should respect a sufficient distance so that they are not interpreted as part of the KNX trademark.
- If a device is a gateway connecting different media, the labels shall only be used if the respective media comply with the KNX requirements. For instance, if an S-Mode device connects TP1 with a proprietary RF solution, the RF label shall not be used. The device shall therefore only bear the TP and S-Mode label.
Hence, when a device offers an IP connection, it may only be labelled with the defined label “IP”, if it at least complies with the minimum KNX(net/)IP profile. In all other cases, the IP label shall not be used. - The availability of an ETS product data entry for a device does not necessarily imply that the device can be marked as an S-Mode device. For this, it is imperative that the device’s application (including the addresses assigned to it by ETS) can be downloaded into the device by ETS. Consequently, also manufacturer specific configuration methods do not entitle to use any of the defined configuration labels.
- For devices that implement the KNX IoT 3rd Party API, but where the IoT Gateway does not support KNX communication towards home and building networks, there is still the possibility for the manufacturer to have the API KNX certified. If tests are positive, the manufacturers may use the KNX IoT1 label, however may not use the KNX trademark itself.