The Loxone NFC Code Touch Tree is used for access control and features an NFC reader and illuminated keypad on a glass surface.
Access control solution via NFC tags, available as key fobs, stickers or cards. Alternatively, a numeric code can be entered on the keypad.
Combining an NFC tag and a numeric code enables two-factor authentication. The keypad also features a freely programmable doorbell button and a checkmark button to confirm entries.
Table of Contents
- Mounting
- Commissioning
- Programming
- Operation
- LED states
- Change Sensitivity
- Inputs, Outputs, Properties
- Safety Instructions
- Documents
Mounting↑
Fasten the included plastic mounting frame to a flat surface or to a 68mm installation box.
An junction box is not required, but highly recommended, as it makes it much easier to tuck away connecting wires or a spare loop behind the device.
The NFC Code Touch can also be mounted using the single aluminum frame or in combination with the Intercom using the double aluminum frame, available separately.
Connect the power supply (orange/white plug-in terminal) and the tree data lines (green/white plug-in terminal).
A self-adhesive cover is included in the delivery to protect against water. It must be attached above the terminals once connected.
Two markings at the top edge of the housing help with positioning:
The NFC Code Touch is first inserted into the top of the frame and then snapped into place at the bottom. To release the device, pull firmly on the bottom to disengage the latch.
A suction cup can be used to detach the device from the aluminum frame.
Commissioning↑
Shortly after power-up, the right status LED will blink orange if the wiring is correct (connection to Tree Extension and Miniserver is established).
Then follow the pairing procedure on the Tree Interface.
Programming↑
The device is programmed and set up using the Authentication NFC Code Touch function block in Loxone Config.
Drag the NFC Code Touch from the periphery tree to the programming page to create the function block.
Only then can the device evaluate access codes and NFC tags and display them correctly via the LED status.
Operation↑
In order to gain access to a building, a paired NFC tag is held up to the NFC reader on the device. The tag is read and authorization is verified.
In order to authenticate using an access code, enter the numeric code on the keypad, followed by the checkmark.
If the authorization was successful, access is granted and the status LEDs light up green. As an example, the door can then be unlocked. If access is denied, the LEDs light up red.
Additional functions can be selected by entering a prefix.
To do so, first enter the prefix number set in the programming and then hold the NFC tag up to the reader.
When using a code, first enter the prefix, then confirm with the checkmark, followed by the access code.
After successful authorization, the function assigned to the prefix is activated.
If an unauthorized NFC tag or numeric code is attempted several times in succession, the device is locked for 2 minutes for further operation, including all keys. This protection prevents brute force attacks.
An authorized NFC tag can unlock the device before that time.
Programming also allows you to limit access via NFC tag or code to specific times, or set them up for one-time use.
More information can be found in the documentation of the Authentication NFC Code Touch function block.
Water on the surface of the NFC Code Touch can interfere with its operation. After the surface dries, the NFC Code Touch automatically re-calibrates and operates as usual.
LED states↑
A row of four LEDs at the top of the device actives during operation, and also indicates whether access was granted or denied.
The following table shows the possible LED states:
| LED display | Meaning |
|---|---|
| 4x white, counting down | Indicates the timeout after a digit was pressed. The next digit must be entered within this time. After the time has elapsed, the entered code is checked for authorization. |
| 4x green, fading out | Access granted or confirmation for bell button. In NFC learning mode: Tag was successfully detected |
| 4x red, fading out | Access denied, tag or code invalid, or not authorized. |
| 4x red, flashing fast, counts down slowly | Device is locked after repeated use of an unauthorized NFC tag or code, or by activation of the input (Off) of the function block. If an unauthorized NFC tag or incorrect code has been used 15 times in a row, the device is locked for 2 minutes. By using a valid tag, this lock can be ended early. Manual lock: Device is locked as long as the input (Off) of the block is active. |
| 4x cyan, running light from left to right | NFC learning mode is active. |
| 4x yellow, flashing | Error while reading NFC tag in learning mode. Try again, hold tag steady! The NFC monitor provides information on the cause of the error. |
| Individual | The 4 status LEDs can be controlled together via programming and display the primary colors. They are only displayed if no other status is currently active. |
| Only right LED active | Indicates the LED status of this Tree device. |
Change Sensitivity↑
In some settings, it may be necessary to change the sensitivity of the keypad using a device command or webservice command.
Each key can be addressed via a TH number:
THProx=Proximity (determines the general sensitivity for the first keypress only)
TH0=Key 1
TH1=Key 4
TH2=Key 7
TH3=Key 2
TH4=Key 5
TH5=Key 8
TH6=Key 3
TH7=Key 6
TH8=Key 9
TH9=Bell Button
TH10=Key 0
TH11=Checkmark
Each key has a certain value assigned to it. First this value has to be queried. Example for key 3:
http://<ip-miniserver>/dev/sys/wsdevice/<device-serialnumber>/get/TH6
The result for example is value 25. Make a note of this value so that you can restore it later.
You can now reduce the sensitivity by assigning a higher value:
http://<ip-miniserver>/dev/sys/wsdevice/<device-serialnumber>/store/TH6/26
To increase the sensitivity, select a lower number.
Numbers below 10 do not need a leading zero.
Finally, the change must be accepted by restarting the device:
http://<ip-miniserver>/dev/sys/wsdevice/<device-serialnumber>/Reboot
Change the sensitivity only in small steps as in the example. Check if the keys react accordingly. If the change is not sufficient, the command can be repeated with a higher/lower number.
Actuators↑
| Summary | Unit |
|---|---|
| API Connector | Text |
Diagnostic Inputs↑
| Summary | Description | Unit | Value Range |
|---|---|---|---|
| Online Status NFC Code Touch Tree | Indicates whether the device can be reached by the Miniserver. Diagnostics for Air devices Diagnostics for Tree devices Diagnostics for Extensions |
Digital | 0/1 |
Properties↑
| Summary | Description | Default Value |
|---|---|---|
| Monitor online status | When selected, you will be notified via System Status or the Mailer if the device is no longer available or goes offline. | - |
| Serial number | Specifies the serial number of the device. For Extensions: Enter 'Auto' to automatically pair an extension with unknown serial number. This can only be used if there is only one Extension of the same type. Save into the Miniserver, in order to pair the Extension. Afterwards the program must be loaded from the Miniserver to transfer the actual serial number of the Extension into the program. |
- |
| Device type | Tree device type | - |
| Audible confirmation | Audible confirmation on button press | - |
Safety Instructions↑
The installation must be carried out by a qualified technician in accordance with all applicable regulations.
Follow the installation instructions closely to guarantee protection against contact, water and dust.
For security reasons we strongly recommend that you only use encrypted NFC tags from Loxone for access control.