KNX gateways

KNX gateway OEM — IP, Modbus, BACnet & Matter

The least glamorous product in the catalogue and the one that decides whether your system works on site: KNX IP interfaces, Modbus and BACnet bridges, DALI gateways, Matter bridges.

Discuss your spec How the program works

Stack selection & architecture

Certified KNX stack plus Modbus/BACnet/DALI/Matter stack, chosen for licence cost, long-term availability and update path.

Point mapping tooling

A configuration interface your integrators can actually use — CSV import, templates, and a searchable point list instead of a raw ETS parameter wall.

Stability & soak testing

72-hour to 4-week soak tests with fault injection: cable pull, power cycling, broadcast storms and reconnect behaviour logged.

Field update path

OTA or USB firmware update process, version policy and a documented rollback — so a bug found in year two is not a recall.

Program detail

How this product is actually built

A gateway is a promise that two protocols will keep talking for ten years. Most failures are not in the conversion table — they are in timing, reconnect behaviour, memory leaks after weeks of uptime, and firmware that nobody can update in the field.

We treat the gateway as a firmware product first: protocol stack selection, long-run stability testing, OTA update path and a documented point-mapping tool, then the enclosure and the label.

Protocols	KNX TP/IP, Modbus RTU/TCP, BACnet MS/TP and IP, DALI-2, M-Bus, Matter bridge (Thread/Wi-Fi)
Capacity	250–2,000 datapoints depending on platform; external memory for larger projects
Connectivity	Ethernet, Wi-Fi, RS-485, USB-C for service; PoE option
Management	Web UI, discovery (mDNS/UPnP), firmware update, diagnostic log export
Certification	CE, UKCA, RoHS; KNX certification; Matter certification via test house where applicable
Typical MOQ / lead time	From 200 pcs; 14–20 weeks including certification window

Questions

What brands ask before starting

Should we build our own gateway or rebadge an existing one?

For most brands under 5,000 units a year, rebadging a proven platform with custom firmware configuration is the better commercial decision. Building from scratch only pays when you need a protocol combination nobody sells, or when the gateway is the core of your system.

Can you do Matter?

Matter bridges are feasible, but certification is a real cost and the specification still moves. I will tell you honestly whether your timeline supports it, and propose a Thread/Zigbee + KNX bridge as an interim if it does not.

Who owns the firmware source?

For fully custom development, source code escrow is available at an agreed fee. For rebadged platforms, the source stays with the platform owner and you get configuration rights — this is normal and I will explain the trade-off in writing.

How do you test long-term stability?

Soak testing with fault injection: repeated power cycles, cable disconnects, malformed frames and broadcast storms, with memory and reconnect timing logged over at least 72 hours before a pilot batch is released.

Related programs

Products that usually ship together

Ready to put your brand on this product?

Send me your target market, rough volumes and the product you have in mind. I will come back with a feasibility view, a realistic landed cost and the certification route — before you spend anything on tooling.

Tell me about your product How the program works