KNX scenarios and automations with Link’nX and Boss’nX
In Link’nX, a scenario combines triggers, optional conditions and a sequence of actions: a time, sunrise, a KNX telegram or an HTTP call starts it, then it writes to group addresses or controls devices. Link’nX functions control a KNX address based on two thresholds or after a period without telegrams. In Boss’nX, a supervision’s Time Programming and the component commands complete this path.
Solutions for your need
Section titled “Solutions for your need”| Need | Application | Guide |
|---|---|---|
| Compose a scenario from triggers, conditions and actions | Link’nX, Scenarios | Compose a scenario |
| Start at a set time or around sunrise or sunset | Link’nX, Timed and Sun event triggers | Timed trigger, sun event trigger |
| Start on a KNX telegram or when a URL is called | Link’nX, KNX and HTTP triggers | KNX trigger, HTTP trigger |
| Limit the start to days, times, dates, day or night, or a KNX value | Link’nX, Conditions | Create a condition |
| Write to group addresses, if needed generated from the ETS file | Link’nX, KNX actions | Prepare a KNX action, generate actions from ETS |
| Set the order of actions, their delays and the interruption of other scenarios | Link’nX, Wait cards and Interruption section | Order, delays and interruptions |
| Control an output based on two thresholds, for example on a temperature | Link’nX, Functions, Hysteresis type | Hysteresis function |
| Send a command after a period without telegrams | Link’nX, Functions, Presence detection type | Timeout without telegrams |
| Run an action or a scenario manually, then check its history | Link’nX, Actions and Scenarios | Run an action or a scenario, scenario history |
| Schedule times and conditions in a supervision | Boss’nX, Menu → Time programming | Create a schedule, set times and conditions |
| Control a datapoint or run a linked Link’nX action from a component | Boss’nX, component detail | Command buttons, run a Link’nX action |
Good to know
Section titled “Good to know”- A scenario’s triggers are combined with OR and its conditions with AND, in Link’nX as in Boss’nX. A condition alone does not start a scenario.
- A KNX trigger reacts to a write matching the configured address and value; a simple status read does not trigger it.
- The Wait delay of a card comes before that action. An interruption abandons the delayed actions of the targeted scenarios, without undoing those already performed.
- A saved and Enabled function controls its target without going through a scenario. Disabling it does not send an opposite command.
- Boss’nX Time Programming does not automatically include Link’nX scenarios; three permissions separate running, tuning and editing.
- A run message does not prove the physical result: check the status feedback.
Integrations add their own triggers and actions: see Lighting, blinds and shutters, Audio and multimedia and Security and video surveillance. See also HomeKit for export to the Home app and Pushover for notifications.
All Scenarios and commands guides
Section titled “All Scenarios and commands guides”Protocols, imports and monitoring
Section titled “Protocols, imports and monitoring”- Run a Link’nX scenario or action from a Boss’nX component
- KNX action in Link’nX: send values to group addresses
- Make a Link’nX scenario conditional on a KNX group address value
- Link’nX KNX trigger: start a scenario on a group address
Questions and troubleshooting
Section titled “Questions and troubleshooting”- Boss’nX command not working: troubleshooting and FAQ
- Actions in Link’nX: troubleshooting and frequently asked questions
- Link’nX KNX functions: troubleshooting and frequently asked questions
Scenarios and commands
Section titled “Scenarios and commands”- Control a Boss’nX datapoint: two states, option list or pulse
- Adjust a setpoint in Boss’nX: + and − buttons, typed value or slider
- Boss’nX scenario actions: commands, values, delays and order
- Boss’nX Time Programming: find, enable and run a scenario
- Create, edit or delete a Boss’nX Time Programming scenario
- Boss’nX scenario triggers: fixed time, sunrise, sunset and conditions
- Create, edit and duplicate an action in Link’nX
- Generate KNX actions from ETS group addresses in Link’nX
- Link’nX HTTP action: send a GET request from a scenario
- Create a Link’nX scenario: triggers, conditions and actions
- Repeat date periods every year in a Link’nX condition
- Limit a Link’nX scenario to specific date ranges
- Limit a Link’nX scenario to certain weekdays and months
- Create, edit and duplicate a Link’nX scenario condition
- Limit a Link’nX scenario to daytime or night-time based on the sun
- Limit a Link’nX scenario to a daily time range
- KNX functions in Link’nX: create, edit, enable or delete
- KNX hysteresis in Link’nX: command an output with two thresholds
- Send a KNX command after a period without telegrams in Link’nX
- Choose the KNX value sent by a Link’nX function based on its DPT
- Link’nX scenario history: find and filter scenario runs
- Test an action or run a scenario manually in Link’nX
- Trigger, condition and action details of a Link’nX scenario
- Save, edit or duplicate a Link’nX scenario
- Set the order, delays and interruptions of a Link’nX scenario
- Override the value of a KNX action in a Link’nX scenario
- Create, edit and duplicate a Link’nX scenario trigger
- Trigger a Link’nX scenario from an HTTP URL (GET webhook)
- Trigger a Link’nX scenario at sunrise or sunset
- Start a Link’nX scenario at a set time: Timed trigger