How to Verify the Exact KNX Variant in a Mixed-Protocol Catalogue
A product family can include similar-looking versions for different protocols, markets or configurations. For a KNX project, the key question is not whether the family name or product photo mentions KNX. It is whether the exact orderable model being quoted is the KNX version, and whether its supporting product records match that model.
Use the steps below before adding a panel to a distributor catalogue, preparing a project shortlist or requesting a quotation.
1. Start with the order code, not the family name
Ask the supplier to identify the exact orderable code for the proposed KNX version. Record the manufacturer, brand, series, model code and any suffix that distinguishes a variant. If one family has KNX, RS-485, Zigbee or other versions, ask the supplier to identify each version separately in writing.
Do not treat a family name, shared product photograph or a generic “smart” label as proof that the quoted unit is a KNX device. If the quote only names a series, leave the protocol and exact model unconfirmed.
2. Match the model to KNX product evidence
Search the exact model and manufacturer in the KNX Certified Devices directory. Compare the record with the code on the supplier’s quotation or datasheet. Save the result URL or a dated record of what you checked, including any differences in spelling, suffix or manufacturer name.
If you cannot find a matching record, ask the manufacturer or supplier for the exact record or certification evidence tied to the quoted model. Do not infer a match from a similar-looking listing or a different model in the same series.
3. Request the ETS product data for that same model
Ask for the applicable ETS product entry or application program and confirm its product name, manufacturer and version against the proposed device. KNX describes ETS as importing product data from KNX manufacturers via application programs. The integrator should confirm that the file is the one intended for the selected device and project.
KNX guidance says unregistered devices are intended for testing and should not be used in real projects. If the product file or device status is unclear, pause project specification until the manufacturer and integrator resolve it.
4. Check whether the documents and images belong to the same variant
Ask for the current datasheet and installation instructions for the order code on the quote. Check that model identifiers agree across the quote, datasheet, ETS product data and any certification record. If the supplier provides a family brochure, ask which pages or image correspond to the exact KNX version.
Keep a separate line for every model that has a different protocol or order code. Do not reuse one variant’s dimensions, functions, wiring information, finishes or image as evidence for another variant unless the manufacturer confirms that the information applies to both.
5. Record the result in a model-level evidence table
- Manufacturer and brand: Record them as written in the current source document.
- Series and exact order code: Include the suffix or version shown on the quotation.
- Protocol stated by supplier: Preserve the supplier’s wording; clearly mark unconfirmed claims.
- KNX directory match: Save the exact record link, or note “not located — supplier confirmation requested.”
- ETS product data: Record the supplied file name/version and who confirmed the match.
- Supporting documents: Keep the datasheet and installation guide for the same order code.
- Image match: Record the image source and confirmation that it depicts the selected variant.
- Open questions: List conflicting codes, missing documents or unmatched details.
This table is an evidence log, not a certification in itself. Have the manufacturer confirm product identity and have the project integrator confirm that the applicable ETS data is suitable for the planned project.
If the model does not appear in the ETS Online Catalog
Check that you are looking at the relevant market and product language, then ask the manufacturer whether the product data is offered through the Online Catalog or as an individual file. KNX states that manufacturers manage their own products in the Online Catalog and that availability can depend on market and language. A missing result in one filtered view therefore needs follow-up; it is not enough to establish the product’s certification or registration status either way.
Common questions
Is a KNX logo or protocol label enough to verify a product?
No. Match the exact order code to manufacturer documents and the relevant KNX product record. Ask the manufacturer to clarify any discrepancy.
Does a product-family page prove that every variant is KNX?
No. A family may contain different model codes or protocol versions. Verify the exact code on the quotation and its supporting records.
Does a missing ETS Online Catalog result mean the device is not certified?
Not on its own. Check market and language filters and ask the manufacturer about product-data availability. Verify certification or registration against the relevant KNX product evidence for the exact device.
Who should confirm that the ETS file is correct for a project?
The manufacturer should identify the product data intended for the exact device; the KNX integrator should confirm the selected data and configuration for the project.
For a broader project checklist, read How to Specify a KNX Switch Panel. Distributors can also review how to build a KNX panel range, browse the BIGHOUSE panel collection, or send a distributor enquiry.