HTTP requests and KNX with Link’nX: actions and triggers
Link’nX uses HTTP in both directions. An HTTP action sends a GET request to the command URL of a device or service. An HTTP trigger provides a gateway URL: when an authorized system calls it, the associated scenarios can start. In a scenario, these items combine with KNX triggers, conditions and actions.
By application
Section titled “By application”HTTP is configured in the Link’nX automations.
| Need | Link’nX items | Guide |
|---|---|---|
| Command a device or service through its URL | HTTP action | Prepare an HTTP action |
| Start a scenario from an external system | HTTP trigger | Trigger a scenario from an HTTP URL |
| Send an HTTP request when a KNX group address receives the expected value | KNX trigger and HTTP action in a scenario | Create a KNX trigger |
| Command KNX group addresses when a call is received | HTTP trigger and KNX action in a scenario | Prepare a KNX action |
Where to start
Section titled “Where to start”- Prepare the HTTP item: the action with the full command URL, or the trigger with its endpoint name.
- If needed, prepare the KNX items: trigger, condition or action.
- Compose the scenario with these items, save it and check its activation.
- For a trigger, reopen it, copy the URL with Copy and configure the calling system to call it with GET.
- Run a deliberate test, then check the result on the installation and in the scenario history.
Good to know
Section titled “Good to know”- The HTTP action only sends a GET request. The form offers no other method, no request body and no separate authentication fields. The URL starts with HTTP or HTTPS, with no space before it.
- In the trigger, enter only the endpoint after the displayed prefix, with no slash. The calling system must reach the gateway at the displayed address; for access from another network or the Internet, ask support for the procedure.
- A trigger URL is private. If several scenarios use this trigger, one call may concern all of them.
- A manual run of the action calls the URL immediately: keep it for a test whose effect you know.
- Neither saving nor the response to the call confirms that the commands were executed: check the device and the history.
Hikvision cameras also send their events to Link’nX over HTTP: see Hikvision. For other automations, see Scenarios and commands and Link’nX.