Skip to content

Link’nX KNX trigger: start a scenario on a group address

Link’nXAdministratorInstaller

Link’nX web: KNX trigger, manual entry or from imported ETS objects

The KNX trigger in Link’nX requests a scenario start when a KNX write carries the configured value on one of its group addresses. Only a write counts: a simple status read triggers nothing.

Intended for installers and administrators. To restrict a scenario according to a value or an upper or lower threshold, use the KNX condition instead: a condition alone does not create a trigger event.

  • You know the group addresses, their DPT and the expected trigger value.
  • To get ETS object suggestions, the project’s addresses are imported into Link’nX. Otherwise, enter the parameters manually.
  1. In Triggers, click Add, then choose KNX in Select a trigger type. To edit an existing trigger, open its name or its pencil icon.
  2. Fill in Name, required, 64 characters maximum.
  3. In Group Address, enter the main address: three numbers separated by slashes, from 0 to 31, from 0 to 7 and from 0 to 255. 1/1/1 is a fictitious format example.
  4. Fill in DPT, or search for its number, then select a suggestion. Choose the DPT that matches the data type of the address, not just an accepted format.
  5. Fill in Value according to this DPT, using the table below. The field must remain filled in when you save.
  6. Click the floppy disk icon at the bottom right, then follow the trigger save confirmations.
DPTValue entry
Starting with 1.Choose True (1) or False (0)
Starting with 16.Enter the expected text
Other numeric typesEnter the exact value to recognize, including 0 if that is the intended value

Several addresses can cause the same event. They are alternatives: a matching write on any one of them can request the scenario start, without all of them receiving the value at the same time.

  1. In the Additional group address section, click Add address.
  2. Fill in the new Group Address. Repeat if necessary. All these addresses use the same DPT and the same trigger value.
  3. Check each address. Remove immediately deletes the additional line from the form; the cross in a field clears it. Remove unnecessary lines and keep a valid main address.

If ETS objects are available in this context, you can speed up the entry:

  • In Name, search for an object’s name and choose the suggestion name --- address. The name, the main address and the DPT are then filled in; reread them before continuing.
  • In Group Address, search for an address or words from the name, then choose address --- name. The address and the DPT are copied; check the name of your trigger separately.
  • For an additional address, the suggestions take the chosen DPT into account. Check that all additional addresses actually use this DPT.

A search with no results may still concern an existing address: check the context and the DPT already chosen, then shorten the search. If you know the exact parameters, enter them manually.

Select the trigger in the scenario, check the conditions and the actions, then save and check the activation.

Successive writes carrying the same value can request several starts: this setting is not limited to a change of value.

Reopen the trigger to check the saved name, all the addresses, the DPT and the value. When the scenario’s actions can run safely, send the expected value to one of the addresses, for example with a push button or the ETS group monitor, then check the start in the history.

Message or symptomAction
Address with an incorrect patternCheck the three numbers and the slashes
Missing or malformed DPTRe-enter its exact number, for example in the format 1.001, without concluding that it suits your equipment
Value flagged requiredChoose the option or enter the expected number or text
The scenario does not startCheck the saved parameters, the trigger selection in the scenario, its conditions and its activation, then the history

Do not repeat test writes: they can command equipment. If you do not know the parameters, if the expected ETS suggestions are missing or if the result remains unexplained, contact support@can-nx.com with the context, the object or address concerned, the DPT, the expected value, the time and the checks already made.