Create, edit and duplicate a Link’nX scenario trigger
Link’nXAdministratorInstaller
Link’nX web: Triggers list, form as a full page or a panel depending on type and width
In Link’nX, a trigger is the event that requests a scenario start: a set time, sunrise or sunset, an HTTP call, a KNX write or an event from an integrated device. It is created in the Triggers list, then selected in one or more scenarios.
Intended for administrators and installers who prepare the events of their automations. First check the project and the gateway shown.
Create a trigger
Section titled “Create a trigger”- Open Triggers in the navigation, then Add. The page shows Trigger creation.
- Open Select a trigger type. The types are grouped, notably in Protocols and Schedule. Search a type… filters their names and accepts a search without accents. Click the desired type.
- Fill in Name: required, 64 characters maximum, not only spaces. For a KNX trigger, this field is in its specific form.
- Fill in the parameters of the chosen type, described in the guide given in the table below. If you change the type during creation, check its parameters again.
- Click the floppy disk in the round button at the bottom right. Wait for Success!, then find the trigger in the list.
If No matching type appears, no offered choice matches the search: clear it before concluding that a type is missing. The integration types offered may depend on the enabled options; do not change other parameters to make a choice appear.
Find the guide for each trigger type
Section titled “Find the guide for each trigger type”| Type or device | Guide |
|---|---|
| Timed | Trigger at a set time |
| Sun event | Trigger at sunrise or sunset |
| HTTP | Trigger from an HTTP URL |
| KNX | Trigger on a KNX group address |
| Intercoms and cameras | Local DoorBird events, 2N, Hikvision, Reolink, UniFi Protect |
| UniFi Access and UniFi Network | Access events and filters, Network presence |
| Somfy | Triggers on Somfy states |
Add the trigger to a scenario
Section titled “Add the trigger to a scenario”A trigger only takes effect once it is associated with a scenario. Creating it does not add it to any scenario: select it in the relevant scenario, then save that scenario.
Edit a trigger
Section titled “Edit a trigger”- In the list, open the trigger’s name or pencil. Trigger modification appears. Its Trigger type is read-only; the tooltip shows Impossible to modify the type when editing.
- Change its parameters, then click the floppy disk.
- If it is used by scenarios, the Scenario affected by this change: or Scenarios affected by this change: window shows their names. Review this list, then click SAVE to confirm the update, or CANCEL to return to the form.
- Wait for Updated!.
Before opening the editor, you can view the linked scenarios.
Duplicate a trigger
Section titled “Duplicate a trigger”- Open the row’s three dots, then Duplicate. The title Trigger duplication and the suffix — New Copy in the name identify the copy.
- Replace this name, check all the copied parameters, then save.
- Add the copy to the scenarios that must use it: it is a separate trigger.
Save before leaving the form
Section titled “Save before leaving the form”Depending on the screen width and the trigger type, editing or duplication may open in a panel next to the list.
- In the panel, Edit in full page opens the editor as a full page. No confirmation of unsaved changes is offered there: save before closing the panel, choosing another row or changing the layout.
- On the full page, leaving a modified form opens Unsaved changes: Cancel keeps the form, Don’t save discards the changes, Save attempts to save before leaving. If Save leaves you in the form of a trigger linked to scenarios, use its floppy disk, then confirm SAVE in the list of affected scenarios.
The sun event trigger guide covers the particular case of the shared location.
Check the result
Section titled “Check the result”After Success! or Updated!, find the trigger in the list and reopen it to review its name and parameters. Then check that it is selected in the scenarios that must use it.
Troubleshooting
Section titled “Troubleshooting”- Issue with field ‘Name’.: check the name and its length, especially after a duplication.
- SAVE does not confirm a change: also check the required fields of the type concerned.
- A type is still missing after clearing the search, a device is missing or the save does not go through: contact support@can-nx.com with the product, the context, the type and the message displayed.