Authentication NFC Code Touch

The Authentication NFC Code Touch function block is used to program an NFC Code Touch.

NFC tags and numerical codes can be assigned to users to grant access to a building or for various other applications.

Table of Contents


Inputs

Please Note: Status light inputs cannot be used with battery powered devices!

Abbreviation Summary Description
R Reset A pulse resets the function block and device
Continuous ON locks function block and device, access / authentication no longer possible, device will flash red
Ir Red Status Light Digital input makes the status LEDs on the device light up red
Ig Green Status Light Digital input makes the status LEDs on the device light up green
Ib Blue Status Light Digital input makes the status LEDs on the device light up blue
Iw White Status Light Digital input makes the status LEDs on the device light up white (all LEDs on)




Outputs

Abbreviation Summary Description Value Range
Q1-6 Output 1-6 Output pulses when permission granted. Outputs can be selected using the corresponding prefix 1-6.
Select the desired output number, confirm with the tick button, then enter access code or present NFC tag.
-
TQ Status Text Text Output - Providing the last authorisation details
The text is available until a new message replaces it. Observe relevant privacy laws
-
TQu Last Authorisation Identification of the last authorization (User ID if available, otherwise username, NFC tag or access code name).
The text is available until the next message replaces it.
-
TQo Last output Name or number of the last Output.
The text is available until the next message replaces it.
-
TQt Timestamp Date and time of last authorisation.
The text is available until it is replaced by the next message.
-
Qd Output - Denied Access Pulse when authentication is denied -
Qa Output - Authorised Access Pulse when authentication is successful -
AQs Active Output Analogue - Indicates the currently active Output (-1 for Denied) -1...∞
Qb Doorbell Digital Output doorbell: On for the duration bell is pressed -
Bsel Doorbell Preselection Doorbell pre-select: A number entered before ringing is displayed here. -1 is output if no pre-selection was entered. -1...9999
AC API Connector This connector is used to link several functions between devices and blocks. -




Parameters

Abbreviation Summary Description Unit Value Range Default Value
LBell Green doorbell button light Activates the doorbell button's green light. Not available with battery powered devices. This parameter is only visible in certain configurations. - - 0
Lbr Keypad illumination brightness Sets the brightness of the keypad illumination. Not available with battery powered devices. % 0...100 50
Tp ON duration of the output pulse Duration of the pulse on Outputs Qa, Qd, and Q1 - Q6. s 0...∞ 3
La Automatic keypad illumination Input automatically activates the keypad illumination at night (Daylight 30min) when on.
Activating the illumination manually using input Lon will override this setting.
Only available with NFC Code Touch Gen.1 devices. This parameter is only visible in certain configurations.
- - 0
Lon Manual keypad illumination Input activates the keypad illumination. Not available with battery powered devices. - - 0




Properties

Summary Description Value Range Default Value
Assigned Device The user must identify themselves on the selected device. The following devices can be selected:
NFC Code Touch Air
NFC Code Touch Tree
NFC Code Touch for Nano
- -
Edit access authorisations Click here to edit access permissions for users and independent NFC-tags/access codes - -
Number of Entries Maximum number of saved messages. 0...100 -
Allow Additional Preselections If activated, additional preselections from 7 to 9999 can be used. Activated preselections greater than 6 are output at the output AQs. With this option selected, a prefix must always be entered before each access code. - -
Two-Factor Authentication Two-factor authentication requires both an access code and an NFC tag within 30 seconds, in any order.
Tags and codes from different users can be combined, as long as both are valid.
Not available with battery powered NFC Code Touch Air Gen. 1 devices.
- -
NFC Confirms Entry When an NFC tag is placed on the reader, the pre-selection is automatically confirmed. When two-factor authentication is used, the code can also be confirmed this way. - -




Basic Configuration

First, the NFC Code Touch is paired.
The function block is then created automatically when the NFC Code Touch is dragged from the periphery tree to the programming page.

In the following example, output Q1 is used to open the front door. Output Q2 is used to control the garage door. The bell button on the NFC Code Touch activates output Qb, controlling a door chime:

The outputs names used in the user interface can be set the double-clicking the block or in the settings of the block:


Using NFC Tags

User-assigned NFC tags for access

It makes sense to assign NFC tags to all users that regularly access a building.
To do so, the users must first be created in the User and Rights Management.

To learn an NFC tag, first click on the function block or the corresponding NFC Code Touch, then click on Learn NFC Tag in the menu bar at the top:

This will open the NFC Monitor at the bottom of the Loxone Config window, and a cyan-coloured running light on the selected NFC Code Touch lets you know that the device is in NFC learning mode.
Hold the NFC tag directly to the reader, which is marked by the circle symbol at the bottom of the device.

The status LEDs on the device briefly light up green once the NFC tag is recognised and the tag is displayed in the monitor.
Select the entry in the monitor, name the tag and assign it to a user:

The NFC tag can then be handed over to the user.
Repeat this process for the NFC tags of the other users.

Only use encrypted NFC tags for access control.
These tags, e.g. the Loxone Smart Tags and Key Fobs are equipped with a MIFARE® DESFire® EV1 chip.

In addition, users need to have the right for the Authentication NFC Code Touch block in order to gain access.

When the learned tag is presented to the reader, output Q1 is activated by default. In order to activate outputs 2-6, the corresponding preselection number 2-6 must first be entered on the NFC Code Touch. Any output of the function block can be activated using this method.

Access can be restricted by creating access schedules in the User Management.

The user-assigned tags are valid at all NFC Code Touches in the project.

User-assigned NFC tags can also be learned via User Management in the user interface.

NFC tags not assigned to a specific user

If an NFC tag is not to be assigned to a specific user, assign the tag to an NFC Code Touch instead:

This option can be used to grant temporary or permanent access to visitors.
Once learned, these tags will be listed in the NFC tags tab of the function block.

You can define which output is to be activated by default and set a validity period.
Authorization can also be limited to certain outputs via the tick boxes:

In the above example, Tag 1 is authorised to activate any output of the function block, output Q1 being the default when no preselection is made. To activate outputs Q2-Q6, preselection is required.
Tag 2 activates output Q2 by default. When preselecting the number 3, output Q3 is activated. Tag 2 is not authorised to activate the remaining outputs.

This configuration is only suitable to a limited extent for regular access, since user-specific functions such as access schedules are not available.

Also, the tag is only valid on the NFC Code Touch to which it was assigned.

NFC Tag used as input

NFC tags can also be used directly as a digital input. They are created in the peripheral tree of the NFC Code Touch and can be used for any application:

The Authentication NFC Code Touch block is not required to use these inputs.
This configuration is not recommended for access control.


Using numeric codes

User-specific numeric access codes

A 2-8 digit numeric access code can be assigned to each user.
To do so, open the Authentication dialog in the properties of a user under Security:

In the New... field under Key Code enter a code for the user and confirm with OK:

The code can then be communicated to the user.
Repeat this process for the codes of the other users.

The same rules that apply to passwords also apply to access codes: as long as possible, as difficult to guess as possible.

In addition, users need to have the right for the Authentication NFC Code Touch block in order to gain access.

When the code is entered on the NFC Code Touch, output Q1 is activated by default. In order to activate outputs 2-6, the corresponding preselection number 2-6 must first be entered, followed by the tick button and then the code. Any output of the function block can be activated using this method.

Access can be restricted by creating access schedules in the User Management.

The user-assigned codes are valid on all NFC Code Touches in the project.

User-assigned codes can also be created via User Management in the user interface.

Numeric codes not assigned to a specific user

If a code is not to be assigned to a specific user, assign the code to an NFC Code Touch instead.
This option can be used to grant temporary or permanent access to visitors.

These codes can be added in the Access Codes tab of the Authentication NFC Code Touch function block, either in the properties or by double-clicking on the block.
Click on the Add button and enter the code:

The default output, authorisation for specific outputs and the validity period can also be set here, as previously described for the NFC tags.

This configuration is only suitable to a limited extent for regular access, since user-specific functions such as access schedules are not available.

Also, the code is only valid on the NFC Code Touch to which it was assigned.

A new code can also be assigned to the NFC Code Touch via the user interface of the function block.

Numeric code used as input

Numeric codes can also be used directly as a digital input. They are created in the peripheral tree of the NFC Code Touch and can be used for any application:

The Authentication NFC Code Touch block is not required to use these inputs.
This configuration is not recommended for access control.