UniFi Access: scenario triggers and KNX group addresses

A UniFi Access event (doorbell, access granted or denied, entry or exit) can trigger a Link’nX scenario. The door’s gateway table also maps KNX group addresses to its unlocking and to its states: lock and door position.

Intended for administrators and installers. Keep in mind that an authorized access, the lock state and the physical position of the door are three different pieces of information.

Before you start

• The door is declared in Link’nX.
• The clocks of the Access controller and of the gateway are synchronized by NTP: an event dated more than 2 minutes ago is ignored.
• For KNX, the installer provides the group addresses from their ETS project; 1/2/3 is only a fictitious example.

Create a UniFi Access trigger

1. In the right project and the right gateway, open Triggers → Add → UniFi Access.
2. Fill in Name, then UniFi Access door.
3. Choose Event type: Doorbell, Access granted, Access denied, Access granted (entry) or Access granted (exit).
4. For the four access events, Access method offers All methods, NFC badge, Exit button (REX), Entry button (REN), Remote (app/API) and Mobile tap (Bluetooth). Leave All methods if you do not want to restrict the method. Doorbell does not display this filter.
5. Save with the floppy disk at the bottom right, wait for Success! and find the trigger in the list.
6. Add the trigger to the relevant scenario and save that scenario. To edit an existing trigger, follow trigger editing.

Choose the event and the access method

• The method describes the means of access, the event reports the direction: Exit button (REX) is a method, Access granted (exit) a direction.
• A single authorized access can trigger the general Access granted event and its entry or exit variant. When no direction is reported, do not infer an entry or an exit.
• These triggers do not count passages and do not provide a named history.
• Have support confirm the Entry button (REN) filter before you rely on it: depending on the hardware, the option may produce no usable event. Also have the expected behavior confirmed for several doors on the same device or for a particular method.

Map the door’s KNX commands and feedback

1. In the UniFi Access list, click the door’s two arrows, Gateway mode configuration.
2. In the Actions tab, check the DPT of each useful command, fill in its KNX group address and check Active.
3. Save with the floppy disk and wait for Données sauvegardées avec succès ! (Data saved successfully!) before changing tabs.
4. Open the second tab, marked with a speech bubble, and map the desired feedback in the same way.
5. Save this tab.

The common behavior (filter, activation, saving) is described in the gateway table guide. To disable a mapping, uncheck Active and save the tab.

All the points offered here use DPT 1.001:

Tab and point	Value 1	Value 0
Actions — Unlock (momentary)	Requests the temporary unlock	No locking request
Actions — Keep unlocked	Keeps the door unlocked	Requests the return to the schedule, which does not necessarily lock right away
Second tab — Lock state	Relay unlocked	To be interpreted with the state available on the controller
Second tab — Door position	Door open	Does not certify a closed door when the contact information is unknown or missing

Rules with a duration and the emergency are configured in the UniFi Access actions, not in these two KNX rows. In your KNX logic, do not replace a missing feedback with 0, and check how recent the last value is.

Check the result

• Trigger: reopen it to review the door, the event type and the method, then check that it is in the saved scenario. After a real event, look at the scenario history. An access trigger reports an access, not a movement of the door: for its physical position, use Door position.
• KNX: reopen the table to review the mappings. Then send a command from the bus, for example with the ETS group monitor, and watch the door. For feedback, send a read request on its address.

Troubleshooting

• The scenario does not trigger: check the selected door, the event type and the method, then the association with the scenario and its saving. If you switched to Doorbell, the method filter has disappeared. Do not replace the filter with another event at random.
• The scenario history shows the origin UniFi Access — event ignored (too old): check the NTP synchronization of the Access controller and of the gateway.
• A KNX feedback is missing: check the context, the door, the address, the DPT, the Active checkbox and the saving of the tab.

If the problem persists after these checks, write to support@can-nx.com with the expected event type or the KNX point concerned, the model and version, the context and the tests already done. Do not send any token or occupant data.

French labels: Type d’événement, Méthode d’accès, Toutes les méthodes, Badge NFC, Bouton sortie (REX), Bouton entrée (REN), À distance (app/API), Tap mobile (Bluetooth), État du verrou and Position de la porte.