VeltnovaVeltnovaContact us
Browse the wiki

2.1KNX basics for installers

Enable the KNX engine, import group addresses, bind objects, and test with the telegram monitor.

Veltnova talks to the KNX bus through the gateway's KNX bridge. In the Configurator you set up three things: the gateway's own KNX connection, your list of group addresses, and the bindings from dashboard objects to those addresses.

#1. Enable the KNX engine

In the right-hand panel, open the Server tab and select Engines > KNX. Turn Enabled on. The KNX Engine Properties page has three areas.

#Gateway KNXnet/IP Interface

  • KNX address: the gateway's individual address on the bus, written area.line.device, for example 1.1.250. Pick an address that is free on your installation.
  • ETS access through gateway: when enabled, ETS can discover and connect through the gateway. The extra options are KNXnet/IP routing, Discovery and ETS client addresses (how many tunnel addresses to offer, 1 to 32).

#Configurator Test Connection

This section is for your PC, not the gateway. It is used by the Run Test switch.

  • Connection Mode: Tunneling (direct to a KNX/IP interface) or Routing (multicast 224.0.23.12).
  • KNX/IP Address and Port (default 3671).
  • Configurator Physical Address: the individual address your PC uses on the bus (default 15.15.15). It must not clash with another device.
  • Search Interfaces: scans the network and lists the interfaces it finds. Click Select on one to fill in the address and use tunneling.

#Group Addresses

Click Import GA CSV to load your group address list, or Clear to remove it.

#2. Import the group addresses

Export your group addresses from ETS as CSV and import the file here. Then every group address field in the project offers autocomplete, showing each address as 1/1/1 - Name - DPT.

  • Use the ETS export 3/1 - three columns, Main/Middle/Sub group separated (or any other CSV format with an address column). The main and middle group names in that export are kept, so the picker below shows them.
  • Only three-level addresses (main/middle/sub, for example 1/2/10) are accepted.
  • The separator (semicolon, comma or tab) is detected automatically.
  • Recognised column headings include address, name, description and DPT. A file without a header row also works.
  • On success you will see Imported N KNX group addresses. The list is stored in the project.

#Browse the group addresses

A project with many group addresses is easier to search as a tree. Every group address field has a small Browse group addresses button at its right end. It opens a window with the main groups, the middle groups inside them and the addresses inside those, like the ETS group address view. Open the groups, select an address to see its name, datapoint type and description, then click Set (or double-click the address). The search box finds addresses by number, name or datapoint type and opens the matching groups. The button appears once a group address list has been imported. If your list was imported with an older Configurator, import the CSV again to get the group names.

You can always type an address by hand. The list is a convenience, not a requirement.

#3. Bind objects to group addresses

Select an object on a page and fill in its address fields. Most objects pair a control address with a status address, so the dashboard shows the real state of the device and not just the last command.

ObjectMain address fields
SwitchGroup Address, Status Group Address, and a Switching Type (for example "ON on pression, OFF on release" for a push button)
Dimmer LightGroup Address (switching), ON/OFF Group Feedback, 4-bit Dimming Group, Value Group, Value Feedback Group
Roller ShutterMove Group Up/Down, Stop / Step Group, Value Group (Position), Value Feedback Group (Position Feedback)
HVACOn/off and status, Actual Temperature Feedback Group, setpoint and setpoint feedback, mode and mode feedback, fan speed
Analog ValueValue Address and a KNX Data Type (DPT 5, 6, 7, 8, 9 or 14), plus min, max, factor, unit and decimals

For an Analog Value, choosing the right data type matters: it decides how the number on the bus is decoded. A temperature is usually DPT 9; a percentage is usually DPT 5.

#Publishing other values to KNX

Values that do not come from KNX can be published onto it. For Modbus datapoints, turn on Send value to KNX and give a group address and DPT (see Modbus devices and datapoints). Zigbee values can do the same.

#Test it

#Run Test

Switch on Run Test in the toolbar, then click a Switch or Dimmer on the canvas. The Configurator sends a real telegram from your PC through the Test Connection. A message such as "Set an ON/OFF group address for …" means that object has no address yet.

#Telegram monitor

The Configurator's own telegram monitor (Diagnostics > KNX Telegrams, button Start Monitor) lists the telegrams that reach the network, with the sender, the group address and the value. See Diagnostics. To watch the gateway's own view of the bus, or to send a test telegram, use the gateway console below.

#On the gateway

Once deployed, the gateway console (Monitor tab) shows live Bus Messages and has a Send Telegram form (group address, data type, value, Send and Read Group). It tests the gateway's own path to the bus, which is what the apps use. See Gateway console and logs.

Still stuck? Open a ticket from the support portal and mention the page you followed.